Crash of a Swearingen SA227DC Metro 23 in Lockhart River: 15 killed

Date & Time: May 7, 2005 at 1144 LT
Type of aircraft:
Operator:
Registration:
VH-TFU
Survivors:
No
Site:
Schedule:
Bamaga – Lockhart River – Cairns
MSN:
DC-818B
YOM:
1992
Flight number:
HC675
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
15
Captain / Total flying hours:
6071
Captain / Total hours on type:
3248.00
Copilot / Total flying hours:
655
Copilot / Total hours on type:
150
Aircraft flight hours:
26877
Aircraft flight cycles:
28529
Circumstances:
On 7 May 2005, a Fairchild Aircraft Inc. SA227DC Metro 23 aircraft, registered VH-TFU, with two pilots and 13 passengers, was being operated by Transair on an instrument flight rules (IFR) regular public transport (RPT) service from Bamaga to Cairns, with an intermediate stop at Lockhart River, Queensland. At 1143:39 Eastern Standard Time, the aircraft impacted terrain in the Iron Range National Park on the north-western slope of South Pap, a heavily timbered ridge, approximately 11 km north-west of the Lockhart River aerodrome. At the time of the accident, the crew was conducting an area navigation global navigation satellite system (RNAV (GNSS)) non-precision approach to runway 12. The aircraft was destroyed by the impact forces and an intense, fuel-fed, post-impact fire. There were no survivors. The accident was almost certainly the result of controlled flight into terrain; that is, an airworthy aircraft under the control of the flight crew was flown unintentionally into terrain, probably with no prior awareness by the crew of the aircraft’s proximity to terrain. Weather conditions in the Lockhart River area were poor and necessitated the conduct of an instrument approach procedure for an intended landing at the aerodrome. The cloud base was probably between 500 ft and 1,000 ft above mean sea level and the terrain to the west of the aerodrome, beneath the runway 12 RNAV (GNSS) approach, was probably obscured by cloud. The flight data recorder (FDR) data showed that, during the entire descent and approach, the aircraft engine and flight control system parameters were normal and that the crew were accurately navigating the aircraft along the instrument approach track. The FDR data and wreckage examination showed that the aircraft was configured for the approach, with the landing gear down and flaps extended to the half position. There were no radio broadcasts made by the crew on the air traffic services frequencies or the Lockhart River common traffic advisory frequency indicating that there was a problem with the aircraft or crew.
Probable cause:
Contributing factors relating to occurrence events and individual actions:
- The crew commenced the Lockhart River Runway 12 RNAV (GNSS) approach, even though the crew were aware that the copilot did not have the appropriate endorsement and had limited experience to conduct this type of instrument approach.
- The descent speeds, approach speeds and rate of descent were greater than those specified for the aircraft in the Transair Operations Manual. The speeds and rate of descent also exceeded those appropriate for establishing a stabilised approach.
- During the approach, the aircraft descended below the segment minimum safe altitude for the aircraft's position on the approach.
- The aircraft's high rate of descent, and the descent below the segment minimum safe altitude, were not detected and/or corrected by the crew before the aircraft collided with terrain.
- The accident was almost certainly the result of controlled flight into terrain.

Contributing factors relating to local conditions:
- The crew probably experienced a very high workload during the approach.
- The crew probably lost situational awareness about the aircraft's position along the approach.
- The pilot in command had a previous history of conducting RNAV (GNSS) approaches with crew without appropriate endorsements, and operating the aircraft at speeds higher than those specified in the Transair Operations Manual.
- The Lockhart River Runway 12 RNAV (GNSS) approach probably created higher pilot workload and reduced position situational awareness for the crew compared with most other instrument approaches. This was due to the lack of distance referencing to the missed approach point throughout the approach, and the longer than optimum final approach segment with three altitude limiting steps.
- The copilot had no formal training and limited experience to act effectively as a crew member during a Lockhart River Runway 12 RNAV (GNSS) approach.

Contributing factors relating to Transair processes:
- Transair's flight crew training program had significant limitations, such as superficial or incomplete ground-based instruction during endorsement training, no formal training for new pilots in the operational use of GPS, no structured training on minimising the risk of controlled flight into terrain, and no structured training in crew resource management and operating effectively in a multi-crew environment. (Safety Issue)
- Transair's processes for supervising the standard of flight operations at the Cairns base had significant limitations, such as not using an independent approved check pilot to review operations, reliance on passive measures to detect problems, and no defined processes for selecting and monitoring the performance of the base manager. (Safety Issue)
- Transair's standard operating procedures for conducting instrument approaches had significant limitations, such as not providing clear guidance on approach speeds, not providing guidance for when to select aircraft configuration changes during an approach, no clear criteria for a stabilised approach, and no standardised phraseology for challenging safety-critical decisions and actions by other crew members. (Safety Issue)
- Transair had not installed a terrain awareness and warning system, such as an enhanced ground proximity warning system, in VH-TFU.
- Transair's organisational structure, and the limited responsibilities given to non-management personnel, resulted in high work demands on the chief pilot. It also resulted in a lack of independent evaluation of training and checking, and created disincentives and restricted opportunities within Transair to report safety concerns with management decision making. (Safety Issue)
- Transair did not have a structured process for proactively managing safety related risks associated with its flight operations. (Safety Issue)
- Transair's chief pilot did not demonstrate a high level of commitment to safety. (Safety Issue)

Contributing factors relating to the Civil Aviation Safety Authority processes:
- CASA did not provide sufficient guidance to its inspectors to enable them to effectively and consistently evaluate several key aspects of operator management systems. These aspects included evaluating organisational structure and staff resources, evaluating the suitability of key personnel, evaluating organisational change, and evaluating risk management processes. (Safety Issue)
- CASA did not require operators to conduct structured and/or comprehensive risk assessments, or conduct such assessments itself, when evaluating applications for the initial issue or subsequent variation of an Air Operator's Certificate. (Safety Issue)

Other factors relating to local conditions:
- There was a significant potential for crew resource management problems within the crew in high workload situations, given that there was a high trans-cockpit authority gradient and neither pilot had previously demonstrated a high level of crew resource management skills.
- The pilots' endorsements, clearance to line operations, and route checks did not meet all the relevant regulatory and operations manual requirements to conduct RPT flights on the Metro aircraft.
- Some cockpit displays and annunciators relevant to conducting an instrument approach were in a sub-optimal position in VH-TFU for useability or attracting the attention of both pilots.

Other factors relating to instruments approaches:
- Based on the available evidence, the Lockhart River Runway 12 RNAV (GNSS) approach design resulted in mode 2A ground proximity warning system alerts and warnings when flown on the recommended profile or at the segment minimum safe altitudes. (Safety Issue)
- The Australian convention for waypoint names in RNAV (GNSS) approaches did not maximise the ability to discriminate between waypoint names on the aircraft global positioning system display and/or on the approach chart. (Safety Issue)
- There were several design aspects of the Jeppesen RNAV (GNSS) approach charts that could lead to pilot confusion or reduction in situational awareness. These included limited reference regarding the 'distance to run' to the missed approach point, mismatches in the vertical alignment of the plan-view and profile-view on charts such as that for the Lockhart River runway 12 approach, use of the same font size and type for waypoint names and 'NM' [nautical miles], and not depicting the offset in degrees between the final approach track and the runway centreline. (Safety Issue)
- Jeppesen instrument approach charts depicted coloured contours on the plan-view of approach charts based on the maximum height of terrain relative to the airfield only, rather than also considering terrain that increases the final approach or missed approach procedure gradient to be steeper than the optimum. Jeppesen instrument approach charts did not depict the terrain profile on the profile-view although the segment minimum safe altitudes were depicted. (Safety Issue)
- Airservices Australia's instrument approach charts did not depict the terrain contours on the plan-view. They also did not depict the terrain profile on the profile-view, although the segment minimum safe altitudes were depicted. (Safety Issue)

Other factors relating to Transair processes:
- Transair's flight crew proficiency checking program had significant limitations, such as the frequency of proficiency checks and the lack of appropriate approvals of many of the pilots conducting proficiency checks. (Safety Issue)
- The Transair Operations Manual was distributed to company pilots in a difficult to use electronic format, resulting in pilots minimising use of the manual. (Safety Issue) Other factors relating to regulatory requirements and guidance
- Although CASA released a discussion paper in 2000, and further development had occurred since then, there was no regulatory requirement for initial or recurrent crew resource management training for RPT operators. (Safety Issue)
- There was no regulatory requirement for flight crew undergoing a type rating on a multi-crew aircraft to be trained in procedures for crew incapacitation and crew coordination, including allocation of pilot tasks, crew cooperation and use of checklists. This was required by ICAO Annex 1 to which Australia had notified a difference. (Safety Issue)
- The regulatory requirements concerning crew qualifications during the conduct of instrument approaches in a multi-crew RPT operation was potentially ambiguous as to whether all crew members were required to be qualified to conduct the type of approach being carried out. (Safety Issue)
- CASA's guidance material provided to operators about the structure and content of an operations manual was not as comprehensive as that provided by ICAO in areas such as multi-crew procedures and stabilised approach criteria. (Safety Issue)
- Although CASA released a discussion paper in 2000, and further development and publicity had occurred since then, there was no regulatory requirement for RPT operators to have a safety management system. (Safety Issue)
- There was no regulatory requirement for instrument approach charts to include coloured contours to depict terrain. This was required by a standard in ICAO Annex 4 in certain situations. Australia had not notified a difference to the standard. (Safety Issue)
- There was no regulatory requirement for multi-crew RPT aircraft to be fitted with a serviceable autopilot. (Safety Issue)

Other factors relating to Civil Aviation Safety Authority processes:
- CASA's oversight of Transair, in relation to the approval of Air Operator's Certificate variations and the conduct of surveillance, was sometimes inconsistent with CASA's policies, procedures and guidelines.
- CASA did not have a systematic process for determining the relative risk levels of airline operators. (Safety Issue)
- CASA's process for evaluating an operations manual did not consider the useability of the manual, particularly manuals in electronic format. (Safety Issue)
- CASA's process for accepting an instrument approach did not involve a systematic risk assessment of pilot workload and other potential hazards, including activation of a ground proximity warning system. (Safety Issue) Other key findings An 'other key finding' is defined as any finding, other than that associated with safety factors, considered important to include in an investigation report. Such findings may resolve ambiguity or controversy, describe possible scenarios or safety factors when firm safety factor findings were not able to be made, or note events or conditions which 'saved the day' or played an important role in reducing the risk associated with an occurrence.
- It was very likely that both crew members were using RNAV (GNSS) approach charts produced by Jeppesen.
- The cockpit voice recorder did not function as intended due to an internal fault that had developed sometime before the accident flight and that was not discovered or diagnosed by flight crew or maintenance personnel.
- There was no evidence to indicate that the GPWS did not function as designed.
- There would have been insufficient time for the crew to effectively respond to the GPWS alert and warnings that were probably annunciated during the final 5 seconds prior to impact with terrain.
Final Report:

Crash of a Swearingen SA227AC Metro III near Stratford: 2 killed

Date & Time: May 3, 2005 at 2214 LT
Type of aircraft:
Operator:
Registration:
ZK-POA
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Auckland – Blenheim
MSN:
AC-551B
YOM:
1983
Flight number:
AWO023
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6500
Captain / Total hours on type:
2750.00
Copilot / Total flying hours:
2345
Copilot / Total hours on type:
70
Aircraft flight hours:
29010
Aircraft flight cycles:
29443
Circumstances:
The crew requested engine start at 2128 and Post 23 taxied for runway 23R at about 2132. The flight data recorder (FDR) showed that during the taxi a left turn through about 320° was made in 17 seconds. Post 23 departed at about 2136 with the first officer (FO) the pilot flying (PF). The planned cruise level was flight level (FL) 180 but the cockpit voice recorder (CVR) showed that in order to get above turbulence encountered at that level the crew requested, and were cleared by air traffic control (ATC), to cruise at FL220. The autopilot was engaged for the climb and cruise. There were 2 CVR references to the crew’s use of the de-icing system to remove trace or light icing from the wings. CVR comments also indicated that stars were visible, and that the aircraft’s weather radar was serviceable. At 2159 ATC cleared Post 23 to track from near New Plymouth very high frequency (VHF) omni-directional radio range (VOR) direct to Tory VOR at the northeast end of the Marlborough Sounds, and at 2206 ATC transferred Post 23 to Christchurch Control. The CVR recorded normal crew interaction and aircraft operation, except that climb power remained set for about 15 minutes after reaching cruise level in order to make up some of the delay caused by the late departure. At about 2212:28, after power was reduced to a cruise setting and the cruise checks had been completed, the captain said, “We’ll just open the crossflow again…sit on left ball and trim it accordingly”. The only aircraft component referred to as “crossflow”, and operable by a flight deck switch or control, was the fuel crossflow valve between the left and right wing tanks. The captain repeated the instruction 5 times in a period of 19 seconds, by telling the FO to, “Step on the left pedal, and just trim it to take the pressure off” and “Get the ball out to the right as far as you can …and just trim it”. The FO sought confirmation of the procedure and said, “I was being a bit cautious” to which the captain replied, “Don’t be cautious mate, it’ll do it good”. Nine seconds later the FO asked, “How’s that?”. The Captain replied, “That’s good – should come right – hopefully it’s coming right.” There was no other comment at any time from either pilot about the success or otherwise of the fuel transfer. During this time, the repeated aural alert of automatic horizontal stabiliser movement sounded for a period of 27 seconds, as the stabiliser re-trimmed the aircraft as it slowed from the higher speed reached during cruise at climb power. Forty-seven seconds after opening the crossflow, the captain said, “Doesn’t like that one mate… you’d better grab it.” Within one second there was the aural alert “Bank angle”, followed by a chime tone, probably the selected altitude deviation warning. Both pilots exclaimed surprise. After a further 23 seconds the captain asked the FO to confirm that the autopilot was off, but it was unclear from the CVR whether the captain had taken control of the aircraft at that point. The FO confirmed that the autopilot was off just before the recording ended at 2213:41. The bank angle alert was heard a total of 7 times on the CVR before the end of the recording. During the last 25 seconds of radar data recorded by ATC, Post 23 lost 2000 ft altitude and the track turned left through more than 180°. Radar data from Post 23 ceased at 2213:45 when the aircraft was descending through FL199 about 1700 metres (m) southeast of the accident area. Commencing at 2213:58, the ATC controller called Post 23 three times, without response. He then initiated the uncertainty phase of search and rescue for the flight. The operator had a flight-following system that displayed the same ATC radar data from Airways Corporation of New Zealand (ACNZ). The operator’s dispatcher noticed that the data for Post 23 had ceased and, after discussing this with ACNZ, he advised the operator’s management. There were many witnesses to the accident who reported noticing a very loud and unusual noise. Some, familiar with the sound of aircraft cruising overhead on the New Plymouth – Wellington air route, thought the noise was an aircraft engine but described it as “high-revving” or “roaring”. Witnesses A were located about 3 kilometres (km) south of the southernmost part of the track of Post 23 as recorded by ATC radar, and about 6 km south of the accident site. They described going outside to identify the cause of an intense noise. As they looked northeast and upwards about 45°, they saw an orange-yellow light descending through broken cloud layers at high speed. A “big burst” and 3 or 4 separate fireballs were observed “just above the horizon” about 5 km away. No explosion was heard. The biggest fireball lasted the longest time and was above the others. The night was dark and it had been drizzling. Witness B, almost 7 km to the northeast of the accident site, observed light and dark cloud patterns moving towards the northwest. She thought the moon caused the light variation; however moonrise was almost 3 hours later. This witness also first observed a fireball below the cloud at an elevation of about 6°. She described it as “a big bright circle” followed by 2 smaller fireballs that fell slowly. No explosion was heard. Witness C, who was less than 1000 m from the aircraft’s diving flight path, described seeing the nose section falling after an explosion “like a real big ball of fire”. The wings were then seen falling after a smaller fireball that was followed by a third small fireball. The witness said it was a still night, with no rain at that time, and the fireballs were observed below the lowest cloud. The fireballs illuminated falling wreckage and cargo. Witness D, also less than 1000 m from the accident site, described parts of the aircraft falling, illuminated by the fireball. Witnesses generally agreed that the first and biggest fireball was round and orange, and then shrank away. Descriptions of the smaller fireballs varied, but were usually of a more persistent, streaming flame that fell very steeply or straight down. A large number of emergency service members and onlookers converged on the accident area. Those who got within about 1000 m of the scene reported a strong smell of fuel. The first item of wreckage was located at about 2315. The main wreckage field was on hilly farmland 7 km northeast of Stratford at an elevation of approximately 700 ft.
Probable cause:
Findings are listed in order of development and not in order of priority.
- The flight crew was appropriately licensed and rated for the aircraft, and qualified for the flight.
- The captain was experienced on the type and the operation, and approved as a line training captain, while the FO was recently trained and not very experienced on the type.
- The aircraft had a valid Certificate of Airworthiness and records indicated that it had been maintained in accordance with its airworthiness requirements. There were no relevant deferred
maintenance items prior to dispatch of the accident flight.
- Although the aircraft had been refuelled in one tank only, it probably took off with the fuel balanced within limits.
- Some fuel imbalance led the captain to decide to carry out further fuel balancing while the aircraft was in cruising flight.
- The captain’s instructions to the FO while carrying out fuel balancing resulted in the aircraft being flown at a large sideslip angle by the use of the rudder trim control while the autopilot was engaged.
- The FO’s reluctance to challenge the captain’s instruction may have been due to his inexperience and underdeveloped CRM skills.
- The autopilot probably disengaged automatically because a servo reached its torque limit, allowing the aircraft to roll and dive abruptly as a result of the applied rudder trim.
- The crew was unable to recover control from the ensuing spiral dive before airspeed and g limits were grossly exceeded, resulting in the structural failure and in-flight break-up of the aircraft.
- The in-flight fire which occurred was a result of the break-up, and not a precursor to it.
- The applied rudder trim probably contributed to the crew’s inability to recover control of the aircraft.
- The crew’s other control inputs to recover from the spiral dive were not optimal, and contributed to the structural failure of the aircraft.
- The flying conditions of a dark night with cloud cover below probably hindered the crew’s early perception of the developing upset.
- The AFM limitation on use of the autopilot above 20 000 ft should have led to the crew disconnecting it when climbing the aircraft above that altitude.
- The crew’s non-observance of this autopilot limitation probably did not affect its performance, or its automatic disengagement.
- If the aircraft had been manually flown during the fuel-balancing manoeuvre, the upset would probably have not occurred.
- The operator should detail the in-flight fuel balancing procedure as a written SOP for its Metro aircraft operation.
- The AFM for the SA 226/227 family of aircraft should include a limitation and warning that the autopilot must be disconnected while in-flight fuel balancing is done, and should include a procedure for in-flight fuel balancing.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 in Bimin: 2 killed

Date & Time: Feb 22, 2005 at 1343 LT
Operator:
Registration:
P2-MFQ
Survivors:
Yes
Schedule:
Tabubil - Bimin
MSN:
174
YOM:
1968
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On approach to Bimin-Wobagen Airport runway 30, the twin engine aircraft lost height and crashed in a wooded area. Both pilots (New Zealand citizens) were killed instantly and all 11 other occupants were injured, some seriously. They walk away to the village to find help and receive care. The aircraft has a single 11/29 grass/dirt runway located at an altitude of 1,767 metres and offer a 10° slope. Runway 29 is for landing only and runway 11 for takeoff only.

Crash of a Cessna 421C Golden Eagle III in El Questro: 2 killed

Date & Time: Aug 30, 2004 at 1200 LT
Operator:
Registration:
HB-LRW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
El Questro – Broome
MSN:
421C-0633
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2128
Captain / Total hours on type:
975.00
Aircraft flight hours:
3254
Circumstances:
On 30 August 2004, shortly before 1200 Western Standard Time, the owner-pilot of a twin-engine Cessna Aircraft Company 421C Golden Eagle (C421) aircraft, registered HB-LRW, commenced his takeoff from runway 32 at El Questro Aircraft Landing Area (ALA). The private flight was to Broome, where the pilot intended resuming the aircraft delivery flight from Switzerland to Perth. The available documentation indicated that the flight segments en route to Australia had all been to international or major aerodromes. The pilot of a Cessna Aircraft Company 210 (C210) and his two passengers in the runway 32 parking area witnessed the takeoff. Those witnesses reported that the C421 pilot carried out a pre-flight inspection of the aircraft prior to boarding for the takeoff. During that inspection, he was observed preparing for, and conducting a fuel drain check under the left wing, and to have removed some weed-like material from the right main wheel. He then loaded a small amount of personal luggage into the aircraft cabin, before he and the sole passenger boarded. The C210 pilot witness, who reported having observed a number of twin-engine aircraft operations at another aerodrome, did not comment on the nature of the pilot's start and engines run-up checks. The passenger witnesses reported that the pilot of the C421 made a number of unsuccessful attempts to start the left engine, before reverting to starting the right engine. He then started the left engine and moved the aircraft clear of the C210 in order to conduct his engine run-up checks. The passenger witnesses reported that during those checks they heard a 'frequency vibration' as the C421 pilot manipulated the engines' controls. The witnesses at the parking area reported that the C421 pilot taxied the aircraft onto the runway and applied power to commence a rolling takeoff. They, together with a hearing witness located to the north of the ALA indicated that the engines sounded 'normal' throughout the takeoff. Witnesses who observed the takeoff reported that the aircraft accelerated away 'briskly'. The pilot witness stated that the take-off roll and lift-off from the runway appeared similar to other twin-engine aircraft takeoffs that he had observed. The witnesses at the parking area also stated that, shortly after lift-off from the runway, the aircraft banked slightly to the left at an estimated 10 to 15 degrees angle of bank and drifted left before striking the trees along the side of the runway and impacting the ground. There was no report of any objects falling from the aircraft, or of any smoke or vapour emanating from the aircraft during the takeoff. The aircraft was destroyed by the impact forces and post-impact fire. The pilot and passenger were fatally injured.
Probable cause:
For reasons that could not be determined, the aircraft commenced a slight left angle of bank and drifted left after lift-off at a height from which the pilot was unable to recover prior to striking trees to the left of the runway.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 near Ononge: 2 killed

Date & Time: Jul 29, 2004 at 1030 LT
Operator:
Registration:
P2-MBA
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Port Moresby - Ononge
MSN:
353
YOM:
1973
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
While descending to Ononge, the crew encountered poor weather conditions and decided to divert to the Yongai Airfield located about 27 km northeast of Ononge. Few minutes later, while cruising at an altitude of 2,286 metres in clouds, the twin engine aircraft struck the slope of a mountain. Rescuers arrived on scene a day later. The loadmaster was seriously injured while both pilots were killed.
Probable cause:
Controlled flight into terrain.

Crash of a Piper PA-31T Cheyenne II near Benalla: 6 killed

Date & Time: Jul 28, 2004 at 1048 LT
Type of aircraft:
Registration:
VH-TNP
Survivors:
No
Site:
Schedule:
Bankstown – Benalla
MSN:
31-7920026
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
14017
Captain / Total hours on type:
3100.00
Aircraft flight hours:
5496
Circumstances:
At 0906 Eastern Standard Time on 28 July 2004, a Piper Aircraft Corporation PA31T Cheyenne aircraft, registered VH-TNP, with one pilot and five passengers, departed Bankstown, New South Wales on a private, instrument flight rules (IFR) flight to Benalla, Victoria. Instrument meteorological conditions at the destination necessitated an instrument approach and the pilot reported commencing a Global Positioning System (GPS) non-precision approach (NPA) to Benalla. When the pilot had not reported landing at Benalla as expected, a search for the aircraft was commenced. Late that afternoon the crew of a search helicopter located the burning wreckage on the eastern slope of a tree covered ridge, approximately 34 km southeast of Benalla. All occupants were fatally injured and the aircraft was destroyed by impact forces and a post-impact fire.
Probable cause:
Significant factors:
1. The pilot was not aware that the aircraft had diverged from the intended track.
2. The route flown did not pass over any ground-based navigation aids.
3. The sector controller did not advise the pilot of the divergence from the cleared track.
4. The sector controller twice cancelled the route adherence monitoring alerts without confirming the pilot’s tracking intentions.
5. Cloud precluded the pilot from detecting, by external visual cues, that the aircraft was not flying the intended track.
6. The pilot commenced the approach at an incorrect location.
7. The aircraft’s radio altimeter did not provide the pilot with an adequate defence to avoid collision with terrain.
8. The aircraft was not fitted with a terrain awareness warning system (TAWS).
Final Report:

Crash of a Beechcraft B200 Super King Air off Papeete

Date & Time: Apr 16, 2004 at 1450 LT
Operator:
Registration:
F-OHJL
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Papeete - Papeete
MSN:
BB-1592
YOM:
1997
Location:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Papeete-Faaa on a local post maintenance flight with one engineer and one pilot on board. Shortly after takeoff, while in initial climb, the pilot informed ATC about control problems and elected to return. Unable to maintain control, he decided to ditch the aircraft few hundred metres offshore. The aircraft sank by a depth of 21 metres and both occupants were able to swim to shore.

Crash of a Rockwell Shrike Commander 500S near Hobart: 1 killed

Date & Time: Feb 19, 2004 at 1643 LT
Operator:
Registration:
VH-LST
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Hobart – Devonport
MSN:
500-3111
YOM:
1971
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
371
Captain / Total hours on type:
40.00
Circumstances:
The aircraft commenced taxying at Hobart for a Visual Flight Rules (VFR) ferry flight to Devonport. The pilot, who was the sole occupant, reported a departure time of 1643 to air traffic control, with an intention to climb to 8,500 ft and to fly a track of 319 degrees magnetic. Due to following traffic, the pilot was required to report leaving specific altitudes. At 1646, the pilot reported leaving 4,500 ft, and was advised that air traffic services were terminated. The acknowledgement of that call was the last communication heard from the pilot. At about 1800, the operator’s staff at Devonport advised the Hobart base that the aircraft had not arrived. The operator advised AusSAR and the Hobart air traffic control tower, and organised company search aircraft from both Hobart and Devonport. The non-flying occupant of the Hobart search aircraft sighted the wreckage at about 1930. Shortly after, a search and rescue helicopter arrived at the accident site. The pilot of the aircraft was found fatally injured in the wreckage. The wreckage was located 58 km from Hobart airport on a bearing of 320 degrees magnetic. Based on predictions of aircraft performance and the distance of the accident site from Hobart, the estimated time of the accident was 1656. There were no eyewitnesses to the accident. Aircraft flight profile The aircraft was not equipped with a flight data recorder or cockpit voice recorder, nor was it required to be. As such, and given that the aircraft was operating outside of radar coverage, there was no recorded flight profile information available. The pilot was not required to report cruising at 8,500 ft and there was no evidence to confirm that the aircraft had reached that altitude. However, based on the normal climb and cruise performance, forecast winds and the radio broadcasts made by the pilot, the aircraft should have reached an altitude of 8,500 ft approximately 35 km from Hobart at about 1651, which was 5 minutes prior to the estimated time of the accident at 1656.
Probable cause:
The trajectory analysis provided the ATSB with a high degree of confidence with respect to the aircraft altitude and speed at the time of the in-flight breakup. The aircraft’s speed could have readily accelerated to Vne during a rapid descent from the nominated cruise altitude of 8,500 ft to the break-up altitude of around 3,150 ft. At such a speed, a relatively small control input force or gusts encountered in the longitudinal (pitch) axis of the aircraft could have resulted in the symmetrical downward wing overloading and failure that occurred. There is no compelling evidence to support any one reason for the departure of the aircraft from the cruise altitude into a high speed dive type situation. However, there are a number of factors that provide some weight to the possibility of a flight upset related to operation of the autopilot. These factors include:
• The lack of any reference in the operations manual to the installation of a Bendix FCS-810 autopilot in LST and the lack of information in the operations manual on the operation of the FCS-810 autopilot
• The pilot’s relative inexperience in the operation of the particular autopilot system fitted to LST
• The operating characteristics of the autopilot system fitted to LST
• The illegible nature of the Aircraft Flight Manual supplement pertaining to the limitations and operating procedures for the autopilot system fitted to LST
• The autopilot controller pitch command wheel being found at the accident site in the maximum nose-down position
• Both elevator trim tabs being found at the accident site at or close to the maximum nose-down trim position. However, it is not possible to discount other explanations for the departure from cruise flight, including a runaway pitch-trim condition, pilot incapacitation, the effects of mountain waves and/or severe turbulence, or a combination of any of the above. On the evidence available to the investigation, it was not possible to conclusively determine the circumstances that led to the aircraft descending at speed to the altitude at which the in-flight breakup occurred.
Final Report:

Crash of a Cessna 208 Caravan I off Green Island

Date & Time: Feb 8, 2004 at 1610 LT
Type of aircraft:
Operator:
Registration:
VH-CYC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cairns - Cairns
MSN:
208-0108
YOM:
1986
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5333
Captain / Total hours on type:
211.00
Circumstances:
The aircraft, with two pilots on board, was being operated for pilot type endorsement training. Air Traffic Control (ATC) had cleared the pilots to conduct upper level air work between 4,000 and 5,000 ft above mean sea level (AMSL) within a 5 NM radius of Green Island, Queensland. Following the upper level air work, the crew requested, and were granted a clearance for, a simulated engine failure and descent to 2,000 ft. The pilot in command (PIC) reported that while completing the simulated engine failure training, he had retarded the power lever to the FLIGHT IDLE stop and the fuel condition lever to the LOW IDLE range, setting a value of 55% engine gas generator speed (Ng). The pilot under training then set the glide attitude at the best glide speed (for the operating weight) of about 79 knots indicated airspeed (KIAS). The PIC then instructed the pilot under training to place the propeller into the feathered position, and maintain best glide speed. The PIC reported that he instructed the pilot under training to advance the emergency power lever (EPL) to simulate manual introduction of fuel to the engine. According to the PIC, he then noticed that there was no engine torque increase, with the engine inter-turbine temperature (ITT or T5) and Ng rapidly decreasing, and a strong smell of fuel in the cockpit. While the pilot under training flew the aircraft, the PIC placed the ignition switch to the ON position and also selected START on the engine starter switch. He then reportedly placed the EPL to the CLOSED position, the propeller to the UNFEATHERED position and the fuel condition lever to the IDLE CUTOFF position to clear the excess fuel from the engine. The PIC reported that they then increased the aircraft airspeed to 120 KIAS, at which point he reintroduced fuel into the engine by advancing the fuel condition lever. He reported that following these actions, the strong fuel smell persisted. As the aircraft approached 1,500 ft, the PIC broadcast a MAYDAY, informing ATC that they had a 'flameout' of the engine and that they were going to complete a forced landing water ditching near Green Island. While the pilot under training flew the aircraft, the PIC placed the propeller into the feathered position, closed the fuel condition lever to the IDLE CUTOFF position and turned off the starter and ignition switches. They then completed a successful landing in a depth of about 2 m of water near Green Island. The pilots evacuated the aircraft without injury. The aircraft, which sustained minor damage during the ditching, but subsequent substantial damage due to salt water immersion, was recovered to the mainland. Following examination of all connections and control linkages, the engine was removed for examination under the supervision of the Australian Transport Safety Bureau (ATSB) at the engine manufacturer's overhaul facility. The engine trend monitoring (ETM) data logger was also removed from the aircraft for examination.
Probable cause:
The following factors were identified:
1. The pilots of CYC were conducting in-flight familiarization training using the emergency power lever. That procedure was not contained in the aircraft manufacturer's pilot operating handbook.
2. The engine manufacturer's documentation contained information on the use of the emergency power lever, which did not preclude the use of the emergency power lever for in-flight familiarization training.
3. The engine sustained a flameout at an altitude above mean sea level from which reignition of the engine was not successfully completed.
4. Erosion of the first-stage compressor blades would have reduced the aerodynamic efficiency of the compressor blades.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) off Byron Bay: 2 killed

Date & Time: Jan 27, 2004 at 1335 LT
Operator:
Registration:
VH-WRF
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Coolangatta - Coolangatta
MSN:
61-0497-128
YOM:
1978
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7127
Captain / Total hours on type:
308.00
Copilot / Total flying hours:
283
Copilot / Total hours on type:
3
Circumstances:
The Ted Smith Aerostar 601 aircraft, registered VH-WRF, departed Coolangatta at 1301 ESuT with a flight instructor and a commercial pilot on board. The aircraft was being operated on a dual training flight in the Byron Bay area, approximately 55 km south-south-east of Coolangatta. The aircraft was operating outside controlled airspace and was not being monitored by air traffic control. The weather in the area was fine with a south-easterly wind at 10 - 12 kts, with scattered cloud in the area with a base of between 2,000 and 2,500 ft. The purpose of the flight was to introduce the commercial pilot, who was undertaking initial multi-engine training, to asymmetric flight. At approximately 1445, the operator advised Australian Search and Rescue that the aircraft had not returned to Coolangatta, and that it was overdue. Recorded radar information by Airservices Australia revealed that the aircraft had disappeared from radar coverage at 1335. Its position at that time was approximately 18 km east-south-east of Cape Byron. Search vessels later recovered items that were identified as being from the aircraft in the vicinity of the last recorded position of the aircraft. Those items included aircraft checklist pages, a blanket, a seat cushion from the cabin, as well as a number of small pieces of cabin insulation material. No item showed any evidence of heat or fire damage. No further trace of the aircraft was found.
Probable cause:
Without the aircraft wreckage or more detailed information regarding the behaviour of the aircraft in the final stages of the flight, there was insufficient information available to allow any conclusion to be drawn about the development of the accident. Many possible explanations exist. The fact that no radio transmission was received from the aircraft around the time radar contact was lost could indicate that the aircraft was involved in a sudden or unexpected event at that time that prevented the crew from operating the radio. The speed regime of the aircraft during the last recorded data points indicated that airframe failure due to aerodynamic overload was unlikely. The nature of the items from the aircraft that were recovered from the ocean surface indicated that the aircraft cabin had been ruptured during the accident sequence.
Final Report: