Crash of an IAI-1124A Westwind II off Norfolk Island

Date & Time: Nov 18, 2009 at 2156 LT
Type of aircraft:
Operator:
Registration:
VH-NGA
Flight Type:
Survivors:
Yes
Schedule:
Apia - Norfolk Island - Melbourne
MSN:
387
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3596
Captain / Total hours on type:
923.00
Copilot / Total flying hours:
1954
Copilot / Total hours on type:
649
Aircraft flight hours:
21528
Aircraft flight cycles:
11867
Circumstances:
On 18 November 2009, the flight crew of an Israel Aircraft Industries Westwind 1124A aircraft, registered VH-NGA, was attempting a night approach and landing at Norfolk Island on an aeromedical flight from Apia, Samoa. On board were the pilot in command and copilot, and a doctor, nurse, patient and one passenger. On arrival, weather conditions prevented the crew from seeing the runway or its visual aids and therefore from landing. The pilot in command elected to ditch the aircraft in the sea before the aircraft’s fuel was exhausted. The aircraft broke in two after ditching. All the occupants escaped from the aircraft and were rescued by boat.
Probable cause:
The pilot in command did not plan the flight in accordance with the existing regulatory and operator requirements, precluding a full understanding and management of the potential hazards affecting the flight. The flight crew did not source the most recent Norfolk Island Airport forecast, or seek and apply other relevant weather and other information at the most relevant stage of the flight to fully inform their decision of whether to continue the flight to the island, or to divert to another destination. The flight crew’s delayed awareness of the deteriorating weather at Norfolk Island combined with incomplete flight planning to influence the decision to continue to the island, rather than divert to a suitable alternate.
Final Report:

Crash of a Piper PA-31 Navajo Chieftain in Darwin

Date & Time: Feb 6, 2009 at 0840 LT
Operator:
Registration:
VH-TFX
Flight Phase:
Survivors:
Yes
Schedule:
Darwin – Maningrida
MSN:
31-8152143
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Darwin Airport, while in initial climb, one of the engine failed. The pilot declared an emergency and elected to return but eventually attempted to ditch the aircraft that came to rest in shallow water about 200 metres offshore. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Piper PA-31-350 Navajo Chieftain in Bathurst: 4 killed

Date & Time: Nov 7, 2008 at 2024 LT
Registration:
VH-OPC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Melbourne – Bathurst – Port Macquarie
MSN:
31-7952082
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2061
Aircraft flight hours:
11000
Circumstances:
On 7 November 2008, a Piper Aircraft Corp. PA-31-350 Chieftain, registered VH-OPC, was being operated on a private flight under the instrument flight rules (IFR) from Moorabbin Airport, Vic. to Port Macquarie via Bathurst, NSW. On board the aircraft were the owner-pilot and three passengers. The aircraft departed Moorabbin Airport at about 1725 Eastern Daylight-saving Time and arrived at Bathurst Airport at about 1930. The pilot added 355 L of aviation gasoline (Avgas) to the aircraft from a self-service bowser and spent some time with the passengers in the airport terminal. Recorded information at Bathurst Airport indicated that, at about 2012 (12 minutes after civil twilight), the engines were started and at 2016 the aircraft was taxied for the holding point of runway 35. The aircraft was at the holding point for about 3 minutes, reportedly at high engine power. At 2020, the pilot broadcast that he was entering and backtracking runway 35 and at 2022:08 the pilot broadcast on the common traffic advisory frequency that he was departing (airborne) runway 35. At 2023:30, the pilot transmitted to air traffic control that he was airborne at Bathurst and to standby for departure details. There was no record or reports of any further radio transmissions from the pilot. At about 2024, a number of residents of Forest Grove, a settlement to the north of Bathurst Airport, heard a sudden loud noise from an aircraft at a relatively low height overhead, followed shortly after by the sound of an explosion and the glow of a fire. A witness located about 550 m to the south-west of the accident site, reported seeing two bright lights that were shining in a constant direction and ‘wobbling’. There was engine noise that was described by one witness as getting very loud and ‘rattling’ or ‘grinding’ abnormally before the aircraft crashed. At 2024:51, the first 000 telephone call was received from witnesses and shortly after, emergency services were notified. The aircraft was seriously damaged by impact forces and fire, and the four occupants were fatally injured.
Probable cause:
From the evidence available, the following findings are made with respect to the collision with terrain involving Piper Aircraft Corp. PA-31-35 Chieftain, registered VH-OPC, 3 km north of Bathurst Airport on 7 November 2008 and should not be read as apportioning blame or liability to any particular organisation or individual.
Contributing safety factors:
• The aircraft descended at a steep angle before impacting the ground at high speed, consistent with uncontrolled flight into terrain.
Other key findings:
• Based on analysis of the available information, an airworthiness issue was considered unlikely to be a contributing factor to this accident.
• The investigation was unable to establish why the aircraft collided with terrain; however, pilot spatial disorientation or pilot incapacitation could not be discounted.
Final Report:

Crash of a Gippsland GA8 Airvan in the Buckingham Bay: 1 killed

Date & Time: Oct 16, 2008 at 0945 LT
Type of aircraft:
Registration:
VH-WRT
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Elcho Island – Mata Mata – Muthamul –Nyinyikay – Rurruwuy – Elcho Island
MSN:
GA8-01-005
YOM:
2001
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1300
Captain / Total hours on type:
300.00
Aircraft flight hours:
4750
Circumstances:
On the morning of 16 October 2008, a Gippsland Aeronautics GA8 Airvan, registered VH-WRT, was being operated on a freight charter flight from Elcho Island and return, Northern Territory. At about 1230, it was realised that the aircraft was missing. A witness reported seeing the aircraft during the early stages of the flight and, shortly afterwards, a column of dark black smoke rising from the eastern side of the Napier Peninsula. On 17 October 2008, items of wreckage from the aircraft were found in the south-western part of Buckingham Bay. The pilot, who was the sole occupant of the aircraft, and the main wreckage of the aircraft have not been found. After consideration of the available evidence, the investigation was unable to identify any factor that contributed to the accident.
Probable cause:
Following a review of the available evidence covering:
• Witness information,
• The pilot's fatigue and health,
• The airworthiness of the aircraft,
• Aircraft fuel,
• The weather affecting the flight, and
• The aircraft’s loading and weight and balance,
The investigation was unable to identify any factors that may have contributed to the accident. From the evidence available, the following findings are made with respect to the missing aircraft at Buckingham Bay, Northern Territory on 16 October 2008 involving Gippsland Aeronautics GA8 Airvan aircraft, registered VH-WRT. They should not be read as apportioning blame or liability to any organisation or individual. No contributing safety factors were identified.
Other safety factors:
• The main vertical net and the throwover net were not used to restrain the cargo.
• The full jerry cans were not secured in the aircraft cabin.
• At the time of departure, the aircraft’s centre of gravity (c.g) was probably to the rear of the permitted c.g limit that was published in the Aircraft Flight Manual.
• There was no record that the pilot lodged a flight notification for the flight with Airservices Australia.
Final Report:

Crash of a Gippsland GA8 Airvan in Cooinda

Date & Time: Sep 9, 2008 at 1500 LT
Type of aircraft:
Operator:
Registration:
VH-KNE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cooinda - Cooinda
MSN:
GA8-08-128
YOM:
2008
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot was completing a local post maintenance test flight at Cooinda Airport. Shortly after takeoff, while in initial climb, the engine failed. The pilot attempted an emergency landing in the bush but the aircraft collided with a telephone pole and came to rest. The pilot escaped with minor injuries and the aircraft was damaged beyond repair.
Probable cause:
Engine failure for unknown reasons.

Crash of a Piper PA-31-310 Navajo Chieftain in Mount Isa

Date & Time: Jul 17, 2008 at 0915 LT
Type of aircraft:
Operator:
Registration:
VH-IHR
Flight Type:
Survivors:
Yes
Schedule:
Century Mine - Mount Isa
MSN:
31-8012077
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
469
Captain / Total hours on type:
30.00
Circumstances:
On 17 July 2008, at approximately 0915 Eastern Standard Time1, the pilot of a Piper Navajo PA-31 aircraft, registered VH-IHR, was en route from Century Mine, Qld to Mt Isa, Qld when the left engine lost power. The pilot transmitted an urgency broadcast (PAN) to air traffic control (ATC). A short time later, the right engine also lost power. The pilot then transmitted a distress signal (MAYDAY) to ATC stating his intention to carry out an off-field emergency landing. The aircraft impacted terrain 22 km north of Mt Isa, about 4 km from the Barkly Highway, in relatively flat, sparsely wooded bushland (Figure 1). The pilot, who was the sole occupant, sustained serious injuries.
Probable cause:
From the evidence available, the following findings are made with respect to the fuel starvation event and should not be read as apportioning blame or liability to any particular organisation or individual.
- The pilot did not monitor outboard fuel tank quantity during the flight.
- The pilot incorrectly diagnosed the engine power losses.
- The aircraft was not in the correct configuration for the forced landing.
Final Report:

Crash of a Swearingen SA227AC Metro III off Sydney: 1 killed

Date & Time: Apr 9, 2008 at 2327 LT
Type of aircraft:
Operator:
Registration:
VH-OZA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Sydney – Brisbane
MSN:
AC-600
YOM:
1984
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4873
Captain / Total hours on type:
175.00
Aircraft flight hours:
32339
Aircraft flight cycles:
46710
Circumstances:
On 9 April 2008, at 2325 Eastern Standard Time, a Fairchild Industries Inc. SA227-AC (Metro III) aircraft, registered VH-OZA, departed Sydney Airport, New South Wales on a freight charter flight to Brisbane, Queensland with one pilot on board. The aircraft was subsequently observed on radar to be turning right, contrary to air traffic control instructions to turn left to an easterly heading. The pilot reported that he had a ‘slight technical fault’ and no other transmissions were heard from the pilot. Recorded radar data showed the aircraft turning right and then left, followed by a descent and climb, a second right turn and a second descent before radar returns were lost when the aircraft was at an altitude of 3,740 ft above mean sea level and descending at over 10,000 ft/min. Air traffic control initiated search actions and search vessels later recovered a small amount of aircraft wreckage floating in the ocean, south of the last recorded radar position. The pilot was presumed to be fatally injured and the aircraft was destroyed. Both of the aircraft’s on-board flight recorders were subsequently recovered from the ocean floor. They contained data from a number of previous flights, but not for the accident flight. There was no evidence of a midair breakup of the aircraft.
Probable cause:
Contributing Safety Factors:
- It was very likely that the aircraft’s alternating current electrical power system was not energised at any time during the flight.
- It was very likely that the aircraft became airborne without a functioning primary attitude reference or autopilot that, combined with the added workload of managing the ‘slight technical fault’, led to pilot spatial disorientation and subsequent loss of control.
Other Safety Factors:
- The pilot’s Metro III endorsement training was not conducted in accordance with the operator’s approved training and checking manual, with the result that the pilot’s competence and ultimately, safety of the operation could not be assured. [Significant safety issue].
- The chief pilot was performing the duties and responsibilities of several key positions in the operator’s organisational structure, increasing the risk of omissions in the operator’s training and checking requirements.
- The conduct of the flight single-pilot increased the risk of errors of omission, such as not turning on or noticing the failure of aircraft items and systems, or complying with directions.
Final Report:

Crash of a PAC Cresco 08-600 near Tully: 1 killed

Date & Time: Aug 16, 2007 at 1513 LT
Type of aircraft:
Registration:
VH-XMN
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Ingham - Tully
MSN:
036
YOM:
2002
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Total fatalities:
1
Captain / Total flying hours:
397
Captain / Total hours on type:
138.00
Circumstances:
The pilot was ferrying the aircraft under the visual flight rules (VFR) from the operator’s base at Tully, Qld to Ingham and return. The flights, conducted in the private category without passengers, were to allow aircraft maintenance to be conducted at Ingham. The flight from Tully to Ingham was conducted in the morning, with no reported difficulties. At 1454 Eastern Standard Time, the pilot departed Ingham on the return flight to Tully. The aircraft did not arrive at Tully. It was not until the next day that the pilot and aircraft were reported missing. Australian Search and Rescue (AusSAR) was notified and a search, based on the last air traffic control radar observed position of an unidentified aircraft from a replay of recorded radar data together with witness reports from the area, was initiated. Searchers located the aircraft wreckage on the morning of 18 August. The aircraft had impacted mountainous terrain in a state forest 24 km south of Tully. The pilot was fatally injured and the aircraft was destroyed.
Probable cause:
Contributing safety factors:
• The aircraft probably entered an area of weather that deteriorated below visual meteorological conditions and for which the pilot was not experienced or qualified.
• The pilot probably became unsure of his position in poor visibility, leading to controlled flight into terrain, fatally injuring the pilot and destroying the aircraft.
Other safety factors:
• The aircraft had not been configured for poor visibility operations, possibly increasing the pilot’s difficulty in navigating.
• The pilot did not submit any form of flight notification such as a SARTIME or Flight Note, as required for a flight in a designated remote area, resulting in a delay to the search and rescue response.
• The operator did not have procedures to provide assurance that a search and rescue would be initiated in a timely way if one of their aircraft did not arrive at the planned destination. [Safety issue]
• As a result of damage to the emergency locator beacon antenna, the beacon did not alert search and rescue organisations to the aircraft accident.
Final Report:

Crash of a Rockwell Shrike Commander 500S in Clonbinane: 2 killed

Date & Time: Jul 31, 2007 at 2000 LT
Operator:
Registration:
VH-YJB
Flight Phase:
Survivors:
No
Site:
Schedule:
Melbourne – Shepparton
MSN:
500-3299
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2342
Captain / Total hours on type:
970.00
Aircraft flight hours:
4558
Circumstances:
At 1946 Eastern Standard Time on 31 July 2007, a Rockwell International Aero Commander 500S, registered VH-YJB (YJB), departed Essendon Airport, Vic. on a business flight to Shepparton that was conducted at night under the instrument flight rules (IFR). On board were the pilot and one passenger. At 1958, while in the cruise at 7,000 ft above mean sea level (AMSL) in Class C controlled airspace, radar and radio contact with the aircraft was lost simultaneously by air traffic control when it was about 25 NM (46 km) north-north-east of Essendon. The air traffic controller declared a distress phase after a number of unsuccessful attempts to contact the pilot. At 2003, the Operations Director at Melbourne Centre declared the aircraft as probably lost and advised AusSAR. A search was commenced using a helicopter and an aeroplane in addition to ground search parties. No emergency locator transmitter signal was reported. At 2147, aircraft wreckage was located by a searching aircraft in timbered ranges near Clonbinane, approximately 50 km north of Melbourne. At about 2200, a ground search party confirmed that the wreckage was that of YJB and that there were no survivors. The flight was arranged to take the company owner, who was also a licensed aircraft maintenance engineer (LAME), to Shepparton to replace an unserviceable starter motor in another of the operator‟s aircraft. The pilot, who had landed at Essendon at 1915 from a previous flight in another of the operator‟s aircraft, was tasked to fly the owner to Shepparton. The pilot transferred to YJB, which had previously been prepared for flight by another company pilot. At 1938, while taxiing for takeoff, the pilot advised the aerodrome controller of the intention to conduct the IFR flight, adding, „…and request a big favour for a submission of a flight plan, with an urgent departure Essendon [to] Shepparton [and] return‟. The aerodrome controller did not have the facilities for processing flight notifications and sought the assistance of a controller in the Melbourne air traffic control centre. There were no eyewitnesses to the accident. Residents living in the vicinity of the accident site were inside their homes and reported difficulty hearing anything above the noise made by the wind and the foliage being blown about. One of the residents reported hearing a brief, loud engine noise. Another resident thought the noise was that of a noisy vehicle on the road. The noise was described as being constant, „…not spluttering or misfiring‟ and lasted for only a few seconds. Some of those residents near the accident site reported hearing and feeling an impact only moments after the engine noise ceased. The aircraft was seriously damaged by excessive in-flight aerodynamic forces and impact with the terrain. The vegetation in the immediate vicinity of the main aircraft wreckage was slightly damaged as the aircraft descended, nearly vertically, through the trees. The pilot and passenger were fatally injured.
Probable cause:
Structural failure and damage:
From the detailed examination and study of the aircraft wreckage undertaken by ATSB investigation staff, it was evident that all principal structural failures had occurred under gross overstress conditions i.e. stresses significantly in excess of the physical strength of the respective structures. The examination found no evidence of pre-existing cracking, damage or material degradation that could have appreciably reduced the strength of the failed sections, nor was there any indication that the original manufacture, maintenance or repair processes carried out on the aircraft were in any way contributory to the failures sustained.

Breakup sequence:
From the localised deformation associated with the spar failures, it was evident that the aircraft had sustained a large negative (downward) loading on the wing structure. That downward load resulted in the localised bending failure of the wing around the station 145 position (145” outboard of the aircraft centreline). The symmetry of both wing failures and the absence of axial twisting within the fuselage section suggested that the load encountered was sudden and well in excess of the ultimate strength of the wing structure. Based upon the witness marks on both wing under-surfaces and the crushing and paint transfer along the leading edges of the horizontal stabilisers, it was concluded that after separating from the inboard structure, both wings had moved aft in an axial twisting and rotating fashion; simultaneously impacting the leading edges of both horizontal tailplanes. Forces imparted into the empennage structure from that impact subsequently produced the rearward separation of the complete empennage from the fuselage. The loss of the left engine nacelle fairing was likely brought about through an impact with a section of wing leading edge as it rotated under and to the rear. The damage sustained by all of the aircraft‟s control surfaces was consistent with failure and separation from their respective primary structure under overstress conditions associated with the breakup of the aircraft. There was no evidence of cyclic or oscillatory movement of the surfaces before separation that might have suggested the contribution of an aerodynamic flutter effects.

Findings
The following statements are a summary of the verified findings made during the progress of the aircraft wreckage structural examination and analysis:
- All principal failures within the aircraft wings, tailplanes and empennage had occurred as a result of exposure to gross overstress conditions.
- The damage sustained by the aircraft wreckage was consistent with the aircraft having sustained multiple in-flight structural failures.
- The damage sustained by the aircraft wreckage was consistent with the structural failure sequence being initiated by the symmetric, downward bending failure of both wing sections, outboard of the engine nacelles.
- Breakup and separation of the empennage was consistent with having been initiated by impact of the separated outboard wings with the leading edges of the horizontal stabilisers.
- There was no evidence of material or manufacturing abnormalities within the aircraft structure that could be implicated in the failures and breakup sustained.
- There was no evidence of service-related degradation mechanisms (such as corrosion, fatigue cracking or environmental cracking) having affected the aircraft structure in the areas of failure.
Final Report:

Crash of a Beechcraft 200 Super King Air in Perth

Date & Time: Apr 9, 2007 at 1703 LT
Operator:
Registration:
VH-SGT
Survivors:
Yes
Schedule:
Perth - Mount Hale
MSN:
BB-73
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 9 April 2007, at 1703 Western Standard Time (WST), the main landing gear from a Beech Super King Air 200 aircraft, registered VH-SGT, collapsed on landing at Perth airport. Approximately two hours earlier, the aircraft was chartered to fly from Perth to Mount Hale, WA when shortly after takeoff from Perth the aircraft experienced a malfunction of the landing gear system. The main wheels and nose gear had become jammed and were unable to fully retract when selected up by the pilot. The pilot completed the emergency checklist actions contained in the Aircraft Flight Manual, but was unable to retract or extend the gear using either the automated control or the manual emergency system. The pilot then requested assistance from a passenger to operate the manual emergency extension system. The landing gear remained jammed despite the additional force applied to the lever from the passenger. The pilot contacted air traffic services and requested further assistance from company engineering personnel to visually assess the extension state of the landing gear. Two aerodrome passes were completed throughout the troubleshooting exercise and the pilot remained in radio contact with both groups during this phase. Following the flyovers and after holding over Rottnest Island at 5,000 ft for a period of approximately two hours, the pilot flew the King Air back to Perth airport. With the gear still jammed in the partially retracted position, both the left and right main landing gear assemblies collapsed after the aircraft touched down on Runway 24. The aircraft was substantially damaged as a result of the collapse (Figure 1). The airport Rescue and Fire Fighting (RFF) services and other relevant agencies had been alerted and were waiting in response when the King Air landed. No injuries were sustained by the pilot or any of the nine passengers on board.
Probable cause:
From the evidence available, the investigation revealed that two major system components had failed which could have prevented the Beechcraft Super King Air 200 landing gear from properly retracting after takeoff. The following findings with respect to those failed landing gear system components should not be read as apportioning blame or liability to any particular organisation or individual.
Contributing safety factors:
• The left torque tube support bearing had not been lubricated and had seized due to the accumulation of dirt and grit contaminants that had migrated from the external service environment and into the bearing.
• The geared components within the right main landing gear actuator prematurely failed.
Other safety factors:
• The aircraft manufacturer’s maintenance manual contained insufficient instruction or guidance for operators and maintainers of Super King Air 200 aircraft for the lubrication of the landing gear torque tube support bearings.
Other key findings:
• Both component assemblies were integral to the function and normal operation of the Super King Air 200 mechanical landing gear system. A break down of either component assembly would have prevented any attempt by the pilot to retract or extend the aircraft’s main landing gear. However, while either failure could have produced the landing gear difficulties sustained, the investigation was not able to determine which mechanism was the principal contributor to the event.
• The investigation was unable to conclusively establish why the geared components within the right main landing gear actuator had prematurely failed.
• The lower thrust bearing within the right main landing gear actuator had been correctly installed.
Final Report: