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 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 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 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:

Crash of a Cessna 404 Titan II in Jandakot: 2 killed

Date & Time: Aug 11, 2003 at 1537 LT
Type of aircraft:
Operator:
Registration:
VH-ANV
Flight Phase:
Survivors:
Yes
Schedule:
Jandakot - Jandakot
MSN:
404-0820
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
16722
Captain / Total hours on type:
12345.00
Aircraft flight hours:
16819
Circumstances:
The aircraft took off from runway 24 right (24R) at Jandakot Airport, WA. One pilot and five passengers were on board the aircraft. The flight was being conducted in the aerial work category, under the instrument flight rules. Shortly after the aircraft became airborne, while still over the runway, the pilot recognized symptoms that he associated with a failure of the right engine and elected to continue the takeoff. The pilot retracted the landing gear, selected the wing flaps to the up position and feathered the propeller of the right engine. The pilot later reported that he was concerned about clearing a residential area and obstructions along the flight path ahead, including high-voltage powerlines crossing the aircraft’s flight path 2,400 m beyond the runway. The aircraft was approximately 450 m beyond the upwind threshold of runway 24R when the pilot initiated a series of left turns. Analysis of radar records indicated that during the turns, the airspeed of the aircraft reduced significantly below the airspeed required for optimum single-engine performance. The pilot transmitted to the aerodrome controller that he was returning for a landing and indicated an intention to land on runway 30. However, the airspeed decayed during the subsequent manoeuvring such that he was unable to safely complete the approach to that runway. The pilot was unable to maintain altitude and the aircraft descended into an area of scrub-type terrain, moderately populated with trees. During the impact sequence at about 1537, the outboard portion of the left wing collided with a tree trunk and was sheared off. A significant quantity of fuel was spilled from the wing’s fuel tank and ignited. An intense postimpact fire broke out in the vicinity of the wreckage and destroyed the aircraft. Four passengers and the pilot vacated the aircraft, but sustained serious burns in the process. One of those passengers died from those injuries 85 days after the accident. A fifth passenger did not survive the post-impact fire.
Probable cause:
Significant factors:
1. The material specification contained in the engineering order for replacing the pump bushing of the engine driven fuel pump (EDFP) fitted to the right engine was not appropriate.
2. High torsional loads between the EDFP’s spindle shaft and the sleeve bearing sheared the pump’s drive shaft during a critical phase of flight.
3. The reduction in fuel pressure was insufficient to sustain operation of the engine at the take-off power setting.
4. The loss of engine power occurred close to the decision speed with the landing gear extended while the aircraft was over the runway.
5. The pilot elected to continue the takeoff.
6. The aircraft was manoeuvred, including turns and banks, at low altitude resulting in a decrease in airspeed below that required to maximise one-engine inoperative performance.
7. The pilot was unable to maintain the aircraft’s altitude over terrain that was unsuitable for an emergency landing.
Final Report:

Crash of a Beechcraft B200C Super King Air in Coffs Harbour

Date & Time: May 15, 2003 at 0833 LT
Operator:
Registration:
VH-AMR
Flight Type:
Survivors:
Yes
Schedule:
Sydney – Coffs Harbour
MSN:
BL-126
YOM:
1985
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18638
Captain / Total hours on type:
460.00
Circumstances:
The aircraft impacted the sea or a reef about 6 km north-east of Coffs Harbour airport. The impact occurred immediately after the pilot initiated a go-around during an instrument approach to runway 21 in Instrument Meteorological Conditions (IMC) that included heavy rain and restricted visibility. Although the aircraft sustained structural damage and the left main gear detached, the aircraft remained airborne. During the initial go-around climb, the aircraft narrowly missed a breakwater and adjacent restaurant at the Coffs Harbour boat harbour. Shortly after, the pilot noticed that the primary attitude indicator had failed, requiring him to refer to the standby instrument to recover from an inadvertent turn. The pilot positioned the aircraft over the sea and held for about 30 minutes before returning to Coffs Harbour and landing the damaged aircraft on runway 21. There were no injuries or any other damage to property and/or the environment because of the accident. The aircraft was on a routine aeromedical flight from Sydney to Coffs Harbour with the pilot, two flight nurses, and a stretcher patient on board. The flight was conducted under instrument flight rules (IFR) in predominantly instrument meteorological conditions (IMC). During the descent, the enroute air traffic controller advised the pilot to expect the runway 21 Global Positioning System (GPS) non-precision approach (NPA). The pilot reported that he reviewed the approach diagram and planned a 3-degree descent profile. He noted the appropriate altitudes, including the correct minimum descent altitude (MDA) of 580 ft, on a reference card. A copy of the approach diagram used by the pilot is at Appendix A. The aerodrome controller advised the pilot of the possibility of a holding pattern due to a preceding IFR aircraft being sequenced for an instrument approach to runway 21. The controller subsequently advised that holding would not be required if the initial approach fix (SCHNC)2 was reached not before 0825. At about 0818, the aerodrome controller advised the pilot of the preceding aircraft that the weather conditions in the area of the final approach were a visibility of 5000 m and an approximate cloud base of 1,000 ft. At 0825 the aerodrome controller cleared the pilot of the King Air to track the aircraft from the initial approach fix to the intermediate fix (SCHNI) and to descend to not below 3,500 ft. The published minimum crossing altitude was 3,600 ft. About one minute later the pilot reported that he was leaving 5,500 ft and was established inbound on the approach. At 0828 the pilot reported approaching the intermediate fix and 3,500 ft. The controller advised that further descent was not available until the preceding aircraft was visible from the tower. At 0829 the controller, having sighted the preceding aircraft, cleared the pilot of the King Air to continue descent to 2,500 ft. The pilot advised the controller that he was 2.2 NM from the final approach fix (SCHNF). At that point an aircraft on a 3-degree approach slope to the threshold would be at about 2,500 ft. The controller then cleared the pilot for the runway 21 GPS approach, effectively a clearance to descend as required. The pilot subsequently explained that he was high on his planned 3-degree descent profile because separation with the preceding aircraft resulted in a late descent clearance. He had hand flown the approach, and although he recalled setting the altitude alerter to the 3,500 ft and 2,500 ft clearance limits, he could not recall setting the 580 ft MDA. He stated that he had not intended to descend below the MDA until he was visual, and that he had started to scan outside the cockpit at about 800 ft altitude in expectation of becoming visual. The pilot recalled levelling the aircraft, but a short time later experienced a 'sinking feeling'. That prompted him to go-around by advancing the propeller and engine power levers, and establishing the aircraft in a nose-up attitude. The passenger in the right front seat reported experiencing a similar 'falling sensation' and observed the pilot's altimeter moving rapidly 'down through 200 ft' before it stopped at about 50 ft. She saw what looked like a beach and exclaimed 'land' about the same time as the pilot applied power. The pilot felt a 'thump' just after he had initiated the go-around. The passenger recalled feeling a 'jolt' as the aircraft began to climb. Witnesses on the northern breakwater of the Coffs Harbour boat harbour observed an aircraft appear out of the heavy rain and mist from the north-east. They reported that it seemed to strike the breakwater wall and then passed over an adjacent restaurant at a very low altitude before it was lost from sight. Wheels from the left landing gear were seen to ricochet into the air and one of the two wheels was seen to fall into the water. The other wheel was found lodged among the rocks of the breakwater.During the go-around the pilot unsuccessfully attempted to raise the landing gear, so he reselected the landing gear selector to the 'down' position. He was unable to retract the wing flaps. It was then that he experienced a strong g-force and realised that he was in a turn. He saw that the primary attitude indicator had 'toppled' and referred to the standby attitude indicator, which showed that the aircraft was in a 70-degree right bank. He rapidly regained control of the aircraft and turned it onto an easterly heading, away from land. The inverter fail light illuminated but the pilot did not recall any associated master warning annunciator. He then selected the number-2 inverter to restore power to the primary attitude indicator, and it commenced to operate normally. The pilot observed that the left main landing gear had separated from the aircraft. He continued to manoeuvre over water while awaiting an improvement in weather conditions that would permit a visual approach. About 4 minutes after the King Air commenced the go-around, the aerodrome controller received a telephone call advising that a person at the Coffs Harbour boat harbour had witnessed an aircraft flying low over the harbour, and that the aircraft had '…hit something and the wheel came off'. The controller contacted the pilot, who confirmed that the aircraft was damaged. The controller declared a distress phase and activated the emergency response services to position for the aircraft's landing. Witnesses reported that the landing was smooth. As the aircraft came to rest on the runway, foam was applied around the aircraft to minimise the likelihood of fire. The occupants exited the aircraft through the main cabin door.
Probable cause:
This occurrence is a CFIT accident resulting from inadvertent descent below the MDA on the final segment of a non-precision approach, fortunately without the catastrophic consequences normally associated with such events. The investigation was unable to conclusively determine why the aircraft descended below the MDA while in IMC, or why the descent continued until CFIT could no longer be avoided. However, the investigation identified a number of factors that influenced, or had the potential to influence, the development of the occurrence.
Final Report:

Crash of a De Havilland DHC-2 Beaver off Whitsunday Island

Date & Time: Mar 6, 2003 at 1615 LT
Type of aircraft:
Operator:
Registration:
VH-AQV
Flight Type:
Survivors:
Yes
Schedule:
Hamilton Island - Whitsunday Island
MSN:
1257
YOM:
1958
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1757
Captain / Total hours on type:
50.00
Circumstances:
The pilot was conducting a charter positioning flight from Hamilton Island Marina to Whitehaven Beach, Whitsunday Island. At approximately 1615LT, pilot was landing the aircraft towards the south, about 600 metres off the beach, to avoid mechanical turbulence associated with terrain at the southern end of Whitehaven Beach. He reported that the approach and flare were normal, however, as the aircraft touched down on the right float, the aircraft swung sharply right and then sharply left. The left wing contacted the water, and the aircraft overturned. The pilot exited the upturned aircraft through the left rear passenger door and activated a 121.5 MHz distress beacon.
Probable cause:
The wind strength and sea state at the time of the occurrence were not ideal for floatplane operations, particularly given the pilot's relative lack of experience in open water operations. In comparison, it was unlikely the non-standard floats contributed significantly to the development of the accident. The loss of directional control suggests a lower than ideal pitch attitude at touchdown, a configuration which reduces a floatplane's directional stability. The pilot's use of a distress beacon for search and rescue purposes was appropriate, however the timeliness of his rescue from the upturned aircraft can be attributed to the effectiveness of the company's flight monitoring system and subsequent search and rescue actions.
Final Report:

Crash of a Cessna 207 Skywagon in Cradle Mountain

Date & Time: Nov 7, 2002 at 1404 LT
Registration:
VH-EHL
Flight Type:
Survivors:
Yes
Schedule:
Cradle Mountain - Cradle Mountain
MSN:
207-0141
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
730
Captain / Total hours on type:
180.00
Circumstances:
The Cessna 207 aircraft (C207) was engaged on a sightseeing flight from Cradle Mountain, to Lake St. Clair and return. On board were the pilot and 4 passengers. The flight departed Cradle Mountain at approximately 1310 ESuT and tracked direct to Lake St Clair at 7000 ft due to turbulence. The aircraft then returned to Cradle Mountain. At approximately 1404, as the aircraft was approaching the airfield, the pilot configured the aircraft for a straight in approach to strip 02. The pilot had selected two stages of flap, and had reduced power to approximately 19 inches of manifold pressure. He reported that at approximately half a mile from the airfield the engine stopped without any prior warning. After completing trouble checks, the pilot became aware that the aircraft would not reach the airfield. He then manoeuvred the aircraft towards an open area on his right while broadcasting a MAYDAY call. Melbourne air traffic control acknowledged this call. The pilot then completed additional trouble checks and changed the fuel tank selection, but the engine failed to respond. The aircraft touched down heavily on the main wheels and slid approximately 40 metres before coming to a stop. During the touchdown and subsequent ground slide, the nose wheel detached from the aircraft, the propeller was damaged and the right wing was partially separated from the airframe. After the aircraft stopped the pilot checked the passengers and discovered that two of them had suffered serious injuries.
Probable cause:
The pilot reported that he had completed a daily inspection of the aircraft earlier in the morning. That inspection included assessing the fuel quantity on board the aircraft and completing a fuel drain and water check. Both of these checks did not reveal any problem with the fuel. The pilot estimated that there was approximately 185 litres of fuel on board the aircraft, 90 litres in the right tank and 95 litres in the left tank. The aircraft had last been refuelled the day previously from drum stock. The aircraft had completed two flights since that refuelling with no problems being reported. The engineers that recovered the aircraft reported that there was approximately 30 litres of fuel in the left tank and approximately 100 litres of fuel in the right tank. The C207 aircraft has a fuel selector in the cockpit that allows the pilot to supply fuel to the engine from either the right tank or the left tank, but not from both tanks simultaneously. The pilot reported that he conducted the flight with the fuel selector switched to the left tank. He also reported that he did not move the selector during the flight and only moved it to the right tank as part of his trouble checks when the engine failed. The pilot reported that he did not complete flight or fuel plans for the flight, but operated on previous knowledge from other flights. A post occurrence analysis of the weather indicated that the winds at 7000 feet were as forecast. Post flight analysis of the flight revealed that the aircraft would have required 57 litres of fuel to complete the flight, which included allowances for taxi and climb. The engine was sent by the owner to an engine overhaul facility for testing. The ATSB did not attend the testing of the engine. The engine was fitted to the test cell in the condition as removed from the aircraft. The engine was started and test run in accordance with the engine manufacturer's overhaul manual. The engine ran normally and all temperature and pressure limits were within normal ranges. The investigation was unable to determine why the engine failed to operate normally in the latter stages of the flight.
Final Report: