Fuel starvation

Boeing 717-200, VH-VQC

Safety Action

Local safety action

Engine/EEC manufacturer

On 25 October 2002, the engine manufacturer issued worldwide communication WW/20032/1/25-10-002 informing operators and airframe and engine technical representatives of the in-flight shutdown event and the fault codes witnessed.

On 27 November 2002, the engine manufacturer issued worldwide communication WW/20032/2/27 Nov. 02 updating the operators and airframe and engine technical representatives of the in-flight shutdown event investigation. That communique informed of the testing of the Fuel Metering Unit and EEC.

On 20 December 2002, the engine manufacturer issued Notice to Operators (NTO) number 54 advising operators of the in-flight shutdown events and of engine restart procedures in the event of an engine shutdown without abnormal engine indications. That communique also advised of harness installation procedures, review of the fault codes and recommended interrogation of the multi-function control display unit (MCDU) at intervals of 50 flight hours.

The engine manufacturer further advised that they will be incorporating a software upgrade of the EEC to version 7.0, which will include an improvement to remove the possibility for certain intermittent failures to trigger a 'health lane' degradation without triggering the corresponding maintenance message.

The Operator

Following the return to service of the aircraft after the 4 October 2002 event, the operator implemented a MCDU interrogation procedure on the incident aircraft for a period of three days. The MCDU stored fault codes were reviewed at the end of each day of flying. The procedure was similar to that subsequently recommended by the engine manufacturer in NTO 54 issued on 20 December 2002. The maintenance history of the right engine was also reviewed as far back as its installation on the aircraft, which occurred on 3 August 2002.

Following the 24 November 2002 event, the operator carried out similar actions as completed after the 4 October 2002 event. The maintenance history of the aircraft was reviewed as far back as the last A check in September 2002. The MCDU review procedure was expanded to cover all aircraft in the fleet. The operator initiated review procedure was superseded on 27 November 2002 by an interim health check procedure developed by the engine manufacturer. This procedure required MCDU fault codes to be reviewed after every 25 to 30 sectors.

Australian Civil Aviation Safety Authority

On 29 November 2002, the Australian Civil Aviation Safety Authority (CASA) issued a directive to the operator to review all fault codes at the end of each day's flying for the occurrence aircraft until further notice.

On 6 December 2002, CASA relaxed the MCDU review requirement for VH-VQC to every port with engineering support available.

On 16 January 2003, CASA issued a request to the operator requiring reviews additional to NTO 54. That action included a review of fault codes at the end of each day's flying for all operator aircraft, with the incident aircraft logged fault codes being reviewed after each sector where engineering support was available. They further expanded the review of fault codes after each sector where engineering support was available to include all operator B717 aircraft.

CASA has subsequently advised the ATSB that the operator has commenced the following program to ensure continued airworthiness of the fleet:

- The MCDU is to be interrogated for EEC faults after each flight into a manned port. Recurring faults identified in NTO 54 should result in replacement of the EEC.

- Fault codes and corrective actions are to be reported to CASA.

- EECs are to be modified per RRD SB-BR700-73-900316.

- One modified EEC is to be installed, in turn, on each aircraft in the fleet.

- Once a modified EEC has been installed, its reliability is to be monitored by continuing the MCDU interrogation after each flight to a manned port for two weeks. Once the reliability is established, MCDU interrogation can be extended to service check intervals.

- Modification of both the EECs, and confirmation of their reliability through MCDU interrogation described above constitutes the corrective actions after which the MCDU interrogations can revert to service check intervals.

- All EECs returned to the manufacturer are to be upgraded and the entire fleet is scheduled to be modified not later than the first quarter of 2004.

RECOMMENDATIONS

Recommendation 20030032

As a result of this investigation, the Australian Transport Safety Bureau recommends that the German Airworthiness Authority, Luftfahrt-Bundesamt issue an airworthiness directive to mandate compliance with Rolls-Royce Deutschland Ltd and Co KG Service Bulletin SB-BR700-73-900316.

Recommendation 20030037

As a result of this investigation, the Australian Transport Safety Bureau recommends that the United States Federal Aviation Administration liaise with the German Airworthiness Authority, Luftfahrt-Bundesamt to develop and issue an airworthiness directive to mandate compliance with Rolls-Royce Deutschland Ltd and Co KG Service Bulletin SB-BR700-73-900316.

Significant Factors

  1. The right engine EEC sustained a failure of both channels of an independent two-channel system, resulting in an in-flight engine shutdown with no prior indications to the flight crew.



 

Analysis

During climb following take-off, the right engine electronic engine controller (EEC) removed electrical power from the engine fuel-control metering valve, which was spring loaded into the closed position. Following loss of the electrical signal, the valve closed resulting in fuel starvation and engine shutdown. The loss of electrical signal to the engine fuel-control metering valve was the result of a dual channel failure of the EEC. The dual channel failure was believed to be the result of:

the failure of channel A because of checksum anomalies of the electrically erasable/programmable read-only memory and

the failure of channel B as a result of electrical intermittences, caused by the loss of signal path resulting from solder joint fractures of the resistors of the analog interface module circuit board.

Examination of other fleet EECs has confirmed the fracturing anomaly of the solder joints of the resistors of the analog interface module circuit board. The effect of the solder joint fracturing on the function of the EEC appears to be loss of signal path on the circuit board and eventual 'health lane' degradation of the unit leading to a shutdown of that channel.

Fracturing of one or more resistor solder joints on both channels of the EEC simultaneously could lead to the loss of system redundancy in the EEC and a subsequent in-flight shutdown of the engine. The possibility of a successful engine restart could be difficult to predict. The crack propagation rate of the resistor solder joint fracture, and the amount required for signal loss is as yet unknown. Therefore, probability calculations for reliability rates of the units may be inaccurate. Compliance to Service Bulletins SB-BR700-73-101401 (SB-BR715/73-009), SB-BR700-73-101404 (SB-BR715/73-010) and SB-BR700-73-900316 was not mandatory.

Factual Information

Flight recorder data

Data reviewed following the flight confirmed that approximately 3 minutes after full power application for takeoff, the fuel flow to the right engine dropped to zero, resulting in the subsequent in-flight shutdown of the engine.

Component history

Documentation provided by the operator annotated that the EEC part number 114E6112G119, serial number LHBR0141, had accumulated 426.7 hours time since new, 393 cycles since new, and had been installed on 2 August 2002. The unit had been modified to software version 6.1 (the most recent version).

Electronic engine controller

The EEC was a two-channel (A and B) electronic unit with system redundancy. It controlled, among other items, engine start sequencing, power requirements, operating temperature, turbine speeds, fuel flow, engine monitoring, and automatic relight. It contained fault detection, storage, and readout capabilities, all stored on an electrically erasable/programmable read-only memory (EEPROM) located on a computer board assembly. The EEPROM provided a history for troubleshooting purposes of any fault event within the EEC or associated control systems by logging a fault code of the event. Those fault codes were then stored until intentionally cleared during maintenance action. The distinct two channels in the unit ensured that should one channel fail, the other would assume control and monitoring of the engine. The transfer of control and monitoring of the engine to one EEC would not necessarily signify that other items controlled by the non-controlling channel would not function. The EEC also provided an electrical signal for opening the engine fuel-control metering valve (normally closed) upon engine starting, which was spring loaded to the closed position.

Component testing

The EEC and FMU units were shipped to the respective component manufacturer's facilities for testing under the supervision of the United States of America (USA) National Transportation Safety Board. Representatives from the aircraft, EEC and engine manufacturers were also present for the testing. Testing of the FMU revealed no anomalies.

EEC serial number LHBR0141 testing

During environmental stress screening of the EEC (a high-speed scan of the faults over a temperature cycle alternating from -55 to +74 degrees C), failures of the Channel A EEPROM were recorded when the internal temperature of the EEC was at -2 degrees C or colder. Test procedures used to test new units for acceptance, also revealed faults of the Channel A EEPROM at temperatures below -55 degrees C. However, initial testing of the EEC could not duplicate the dual channel failure (A and B) that would have been required to sustain the reported in-flight shutdown.

The Channel A EEPROM was sent to the manufacturer for detailed examination. Examination indicated that a phenomenon called a 'single bit flip' had occurred within the used memory section area of the input/output microprocessor of the unit. The input/output microprocessor memory was configured with positively charged hexadecimal binary 1s occupying unused memory sections. The 'single bit flip' phenomena was a result of unused sections of the microprocessor memory becoming negatively charged binary zeros, resulting in checksum failures and 'health lane' degradation of the EEC. Checksum failures are the result of discrepancies of the internal self-check program, which sums the values of all memory blocks.

Follow up vibratory testing of the EEC confirmed a failure of Channel B. Further examination indicated fracturing of solder joints at five resistors on the analog interface module circuit board of Channel B.

Other Australian fleet occurrences

On 24 November 2002, while on the downwind leg for landing at Hobart, another crew of the same aircraft reported that the left engine 'spooled down'. The crew reported that they did not see any caution advisories prior to the power decrease. The crew then completed a single engine landing. Following the event, the operator's maintenance personnel conducted troubleshooting of the left engine and noted one fault code related to the EEC (not listed in maintenance documentation) logged on the MCDU memory. The engine was inspected and ground run, both at idle and at a high power setting. The engine started and operated normally. The EEC and FMU were replaced after conferring with the engine manufacturer. Further engine ground runs were completed and the aircraft was deemed to be serviceable.

Documentation provided by the operator recorded that the EEC part number 114E6112G119, serial number LHBR0148, had accumulated 4,686.4 hours and 4,311 cycles since new. The unit had been modified to software version 6.1.

The engine manufacturer advised that a visual inspection of the unit revealed fracturing of the soldier joints of six resistors of Channel A and four resistors of the Channel B analog interface module circuit boards.

Other overseas occurrence

On 30 November 2002, a USA operator's Boeing 717-200 was on climb at FL 280 when it sustained an in-flight shutdown of the right engine. Following the event, EEC part number 114E6112G119, serial number LHBR0093, which had accumulated approximately 6,700 hours time since new was examined. That examination revealed fracturing of the solder joints at five resistors of Channel A and ten resistors of the Channel B analog interface module circuit board.

Solder joint fracturing

The engine manufacturer reported that the anomaly of fracturing or cracking of the resistor solder joints was believed to have resulted from thermal cycle induced stress due to differential thermal expansion between the printed circuit board and the resistor. They further reported that identical resistor packages were utilised on the installation of both channels within the EEC and that the solder joint fracturing anomaly could affect a total of seven resistors per channel of each EEC. Five of these resistors were assessed as being capable of contributing to the top-level failure events analysed in the unit system safety assessment.

Service bulletin history

On 20 December 2002, the engine manufacturer issued Service Bulletin SB-BR700-73-101401. That bulletin referenced compliance with the EEC manufacturer's Service Bulletin SB-BR715/73-009 also released 20 December 2002, which gave instructions for the repair of several specific resistors on the analog interface module circuit board. That repair would attach the resistors to the board and connect them to the original solder pad by 'flying leads'. This would then eliminate any mechanical stress on the resistors. Compliance time of that bulletin was at the next shop visit of the EEC for repair, or as arranged by the EEC manufacturer and was not mandatory.

On 17 January 2003, the engine manufacturer issued Service Bulletin SB-BR700-73-101404. That bulletin referenced compliance with the EEC manufacturer's Service Bulletin SB-BR715/73-010 also released on 17 January 2003, which gave instructions for a software modification of the processor communication's modules (A3, A4) with new input/output software to change the fill pattern of the unused areas of the EEPROM memory from hexadecimal binary 1s to binary 0s, thereby reducing the possibility of checksum failures. Compliance time of that bulletin was at the next shop visit of the EEC for repair, or as arranged by the EEC manufacturer.

On 20 February 2003, the engine manufacturer issued Service Bulletin SB-BR700-73-900316 advising the fleet operators of a numbers of inspections and modifications to improve the reliability rates of the EEC. The bulletin listed a total of ten service bulletins issued by either the engine or EEC manufacturer, which the engine manufacturer recommended be incorporated at the earliest opportunity without affecting flight schedule. Incorporation of these modifications required a return of the component to the engine manufacturer.

None of those service bulletins were mandated through the issuing of an airworthiness directive from either the USA Federal Aviation Administration or the German Airworthiness Authority.

Summary

The crew of the Boeing 717-200 aircraft reported that during the climb from Launceston airport, while passing 7,000 ft above sea level, the right engine sustained an uncommanded in-flight shutdown. The R ENG RPM LO alert was observed followed by the RH SYS FAIL advisory. The crew reported that they did not see any caution advisories prior to the shutdown. The ENGINE FAIL/SHUTDOWN INFLIGHT checklist was actioned and the crew completed a single engine landing.

Following the event, the operator's maintenance personnel interrogated the multi-function control display unit (MCDU) and carried out a right engine electronic engine controller (EEC) fault review check. A return to service check, a dry motoring run and an engine idle run were carried out with no faults found. A further EEC fault review was carried out and several fault codes were noted in the memory. These related to electronic faults listed for a FADEC SYSTEM FAULT [full-authority digital engine control] and EEC BOX FAULT [electronic engine controller]. After conferring with the engine manufacturer, the EEC and the fuel-metering unit (FMU) were removed for further testing. After replacement of those units, an EEC return to service and an FMU leak check were carried out. At the request of the engine manufacturer, engine ground runs were carried out and the aircraft was deemed to be serviceable.

Occurrence summary

Investigation number 200204444
Occurrence date 04/10/2002
Location 11 km N Launceston, (VOR)
State Tasmania
Report release date 30/06/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 717
Registration VH-VQC
Sector Jet
Operation type Air Transport High Capacity
Departure point Launceston, TAS
Destination Sydney, NSW
Damage Nil

Hughes Helicopters 369E, VH-HJT

Safety Action

Australian Search and Rescue is considering the promotion of a means of communication between rescue helicopters and personnel on the ground.

The ATSB will monitor and publish any subsequent action on the ATSB website.

Significant Factors

The helicopter engine lost power at a critical stage of flight.

The pilot was unable to conduct a successful autorotation landing.

Analysis

The impact damage to the right fuel cell bladder and extended periods of ground running during the day's operations prevented the investigation from determining an accurate fuel consumption. The investigation determined that a landing on sloping ground should have affected both the fuel quantity indicator and fuel low level advisory light equally. An indicated fuel quantity of 100 lbs (86.9 lbs useable) and coincident illumination of the fuel low level advisory light, both reported by the pilot, could not be explained.

Technical examination of the helicopter's fuel indicating system established that illumination of the fuel low level advisory light coincided with 35 lbs (21.9 lbs useable) indicated on the fuel quantity indicator. At the company flight planning fuel consumption rate of 176 lbs per hour, 21.9 lbs of useable fuel would likely have equated to a flight time of approximately 7 minutes. In that case, a reported departure from Lake Nameless Hut at 1515 hours would have likely resulted in engine fuel starvation at about 1522 hours.

Technical examination of the helicopter and engine revealed no anomalies. Therefore, the helicopter was considered capable of normal flight prior to the occurrence. The amount of fuel onboard the helicopter, less than that expected by the pilot, likely resulted in unporting of the fuel cell fuel supply hose, and engine fuel starvation during the turn to land at Tom Whitely's Hut. Due to impact rupture damage of the right main fuel cell, an accurate fuel quantity remaining could not be measured.

The pilot reported that the autorotation landing was normal and that contact with a wire rotated the aircraft through 180 degrees. As there was no evidence of helicopter contact with the fence prior to, or during the initial ground impact, the investigation concluded that the fence did not contribute to the accident sequence.

Ground impact marks indicated a relatively steep approach with low forward ground speed. Examination of the Height Velocity Diagram indicated that, at the pilot reported height of 200 ft above ground level, and airspeed in autorotation of 65 kts, a successful autorotation landing should have been possible. Impact damage indicated that the autorotation landing was unsuccessful. It was therefore likely that the pilot's estimate of height and airspeed at the time the rotor speed decreased was less than actual. In that case, the helicopter may have been at a height and airspeed from which a successful autorotation landing would be difficult to perform.

The pilot reported that he had minimal recent experience on the Hughes 369E helicopter type and had practised autorotation landings in an Augusta 119 Koala helicopter type during the previous week. While it cannot be discounted, the investigation could find no evidence to indicate that lack of type-specific recency, or contradicting cross-type pilot handling, contributed to the unsuccessful autorotation landing.

While the pilot reported asking the passengers to confirm the security of their seat belts prior to take off for the occurrence flight, the passengers reported that headsets were not worn during that flight. The ambient cockpit and other noise as the passengers boarded the engine-running helicopter may have prevented them from hearing any direction from the pilot. The front seat passengers were ejected forward of the helicopter during the impact sequence. The front seat passengers' seat belts, shoulder harnesses and attachment points exhibited no evidence of damage, or having been forced by impact forces. Therefore, it was unlikely that the front seat passengers were wearing seat belts at the time of impact.

In effect, the selection process employed to contract the operator for the day's operation included an informal risk assessment. Risk assessments represent a valuable safety tool. They can range from an informal experiential and environmental audit, similar to that conducted by the coordinator of the Western Tiers operation, to an in-depth analysis of all hazards likely to affect the operation of an aviation system. That analysis includes consideration of the likelihood of an identified hazard to an operation, and the possible consequence to the aviation system resulting from that hazard occurring.

A more formal and inclusive risk assessment, conducted by all participants in the Western Tiers operation, could have enhanced the overall safety of that operation. Some of the risks to the operation, and possible risk treatments that might have been considered by the interacting participants in the operation were:

Pilot experience. The pilot's reported unfamiliarity with the area of operations and lack of recency in the Hughes 369E helicopter type could have been mitigated by a more extensive orientation and check flight and briefing procedure. That process could also have included appraising the coordinator of the operation of the pilot's background and lack of local experience.

Fuel reserve. The 10-minute fixed reserve authorised for external load operations in the company Operations Manual likely maximised flexibility and payload during such operations. However, the operation in the Western Tiers involved the movement of external loads and carriage of passengers in an at times inhospitable area, by a pilot unfamiliar with that area. In that case, modifiers to the company 10-minute fixed reserve may have been pertinent, and the company charter minimum fuel requirements been more relevant to the operation.

Flight following. The operation was conducted in an at times inhospitable and remote area of north-western Tasmania. There was scope for a more formal flight following procedure to decrease rescue agency response time and optimise the safety of the operation overall. Available flight following options included formal employment of a monitored flight and details schedule by the participants in the Western Tiers operation, regular radio contact between the pilot and Air Traffic Services, or the nomination of a SARTIME by the pilot.

The departure of the rescue helicopter from the accident site, without landing, was reported by the survivors to have adversely affected their morale, and confidence in their subsequent rescue. They were not aware that the ground rescue party was enroute to their location. A means of communication from the rescue helicopter to personnel on the ground may have prevented that decline in survivor morale and confidence.

Summary

The Hughes 369E helicopter, with the pilot the sole occupant, departed Strahan aerodrome at 0815 hours Eastern Standard Time (EST) for charter operations in the Western Tiers area of north-western Tasmania. Multiple flights were required from a base at Lake Mackenzie to a number of dispersed mountain hut locations. The flights involved transport of varying amounts of external loads and personnel, and included extensive periods on the ground with the helicopter engine running.

At approximately 1500 hours the pilot conducted a flight with an external load from Lake Mackenzie to Lake Nameless Hut. He then landed to embark three passengers for transfer to another hut. Two of the passengers occupied the remaining two front seats and the third passenger occupied the cabin right rear seat. The pilot reported that, while on the ground, the fuel low level advisory light had momentarily illuminated, but that he attributed that illumination to the distribution of fuel in the tank due to the slope of the ground. At that time, he reported also noting 100 lbs (86.9 lbs useable) of fuel indicated on the fuel quantity indicator. At 1515 hours, the helicopter departed Lake Nameless Hut for Tom Whitely's Hut, which was located approximately 5 km to the north-east. A passenger reported that, during that flight, a caution advisory light had illuminated. The investigation could not confirm the identity of that light. Having overflown the hut landing area, the pilot initiated a left descending turn to the south prior to commencing an approach to land.

The pilot reported that at 1524 hours, as the helicopter descended through about 200 ft above ground level (AGL), and at a speed of 70 kts, the main rotor speed decreased and the engine auto reignition advisory light illuminated. Assessing that the engine had lost power, the pilot reported that he initiated an autorotation to land. He stated that "...the aircraft landed normally, although heavily". He reported that, after the initial ground contact, the aircraft was "...suddenly rotated through 180 degrees". That rotation was reported by the pilot to be as a result of entanglement with an unseen "...little wire or whatever hooked the aircraft".

The helicopter was destroyed by impact forces. There was no fire. The pilot and three passengers sustained serious injuries.

Wreckage information

The helicopter impacted the ground heavily on the rear of the right landing skid, collapsing it and separating the left landing skid. The fuselage impact ground scar measured about 2 m in length. The main rotor blades struck the ground and severed the tail boom. The helicopter came to rest about 7 m and bearing 200 degrees magnetic from the initial impact point, facing the direction from which it had approached, and lying on a fence line. There were no ground impact scars between the fuselage impact ground scar and the helicopter's final position. The right side rear fuselage floor area sustained severe impact damage and the right fuel cell bladder was ruptured.

The forward section of the cockpit was destroyed during the impact sequence. The two front seat passengers were ejected from the helicopter, in the direction of flight. On-site inspection found the pilot's and passengers' seat belts and attachment points intact and that the pilot's shoulder harness was separated at the harness-to-inertia reel strap buckle. There was no evidence that the passengers' seat belt buckles had received damage due to impact forces. The pilot and front seat passengers' seat structure was deformed and wrinkled. Information from the helicopter manufacturer indicated that a vertical impact force loading of the airframe in excess of 10 g would have been required to deform the seat structure in that manner.

The investigation determined that there was minimal rotation of the tail rotor driveshaft at ground impact. That was confirmed by the lack of any impact or rotary damage to the tail rotor blades. The engine output driveshaft was separated at the driveshaft lobes and displayed little or no rotation at the time of separation.

The external load long-line was found attached to the cargo hook. There was no evidence that the long-line had snagged on the ground, other obstacles or the helicopter prior to impact.

An old wire and timber post fence was located in the vicinity of the accident site. The fence was about 1 m high and aligned about 050/230 degrees magnetic. The fence was laterally displaced about 3.5 m from the initial impact point. The fence posts and wire exhibited no evidence of having been contacted prior to, or during the helicopter's initial ground impact.

Testing of components

Analysis of the helicopter fuel system determined that a common fuel-sending unit activated the fuel quantity indicator and fuel low level advisory light. The fuel-sending unit, fuel quantity indicator and fuel low level warning system were removed from the helicopter and tested. Testing indicated that those components were serviceable in accordance with the manufacturer's maintenance manual. The fuel low level advisory light illuminated at 35 lbs fuel indicated on the fuel quantity indicator, in accordance with the manufacturer's maintenance manual. Testing, disassembly and inspection of the engine fuel pump, fuel control unit, fuel nozzle, bleed valve and power turbine governor, revealed no anomalies.

Meteorological information

The Bureau of Meteorology Area Forecast, valid at the time of the accident, indicated Visual Meteorological Conditions with moderate southerly winds. The pilot and passengers reported bright, sunny conditions and a light and variable southerly wind.

Personnel information

The pilot in command held an Air Transport Pilot (Helicopter) Licence, a Command Multi-Engine Instrument Rating and was endorsed on the Hughes 369E helicopter type. At the time of the occurrence, the pilot had accumulated a total of 3,565 flying hours, including 74.0 hours on type. He had flown 34 hours in the previous 90 days, of which 5 hours was on type. He was reported to be fit and well rested prior to the flight.

On the afternoon prior to the occurrence, the pilot completed a 0.5 hour proficiency check flight with the company Chief Pilot, in accordance with the company Operations Manual and CAO 20.11 appendix 4. It was reported that the check flight did not include external load or autorotation sequences. The pilot reported that he had significant prior external load experience, conducted in several helicopter types. He was unsure when he last practised an autorotation in the Hughes 369E. He reported, however, that he had completed autorotation and other emergency training in an Augusta 119 Koala helicopter about one week prior to the occurrence, and in a Bell 205 helicopter about one month prior to the occurrence.

Helicopter information

The maintenance release was current and there were no outstanding maintenance requirements. A routine 100-hourly engine inspection was carried out on 25 May 2002. Post-accident technical examination of the engine and wreckage indicated that the helicopter was capable of normal operation prior to the occurrence.

The gross weight of the helicopter at the time of impact was estimated to be within the authorised maximum operating and Height Velocity Diagram weight limits. The longitudinal and lateral centres of gravity were estimated to be within published flight manual limits. Helicopter performance was estimated to be sufficient for both in and out-of-ground effect flight.

Fuel planning/loading

The company Operations Manual stated a flight planning fuel consumption rate of 100 L (176 lbs) per hour for the Hughes 369 type. Charter helicopter fuel planning was required to include the provision of 20 minutes fixed and 15 per cent variable reserve. However, a reduction to a 10-minute fixed reserve was authorised for helicopter external load operations. That amounted to 42.4 lbs (29.3 lbs useable) indicated on the fuel quantity indicator at the company planning fuel consumption rate.

The pilot reported that the company Chief Pilot suggested a planning fuel consumption rate of 200 lbs per hour and that 100 lbs (86.9 lbs useable) indicated on the helicopter fuel quantity indicator equated to about 15 to 20 minutes flying time. He stated that, throughout the day's operations, he maintained a fuel log indicating an average fuel consumption of approximately 200 lbs per hour. The ground search and rescue party reported that, on arrival at the accident site, they collected paper and other loose items in the immediate vicinity of the wreckage. Those papers and items were secured in a large bag left at the accident site. The pilot's log was not recovered from that bag of items.

The pilot reported that a total of 280 L of fuel was added to the helicopter during the day using the operator's drum fuel stock and hand rotary fuel pump located at Lake Mackenzie. That amount of fuel was based on the pilot's understanding that approximately 280 turns of the rotary pump were made during the day's refuels and that pump output was 1 L per turn. He reported that he visually checked the fuel quality after each refuel. Post-accident examination of the remaining company drum fuel stock confirmed that it was JetA1 and did not reveal any contamination. Post-accident testing of the hand rotary pump used to refuel the helicopter determined an actual pump output of 0.7 L per turn.

Operational information

The helicopter flight manual stated that the fuel low level advisory light illuminated when approximately 35 lbs of fuel (21.9 lbs useable) remained in the fuel tank. The manual further stated that illumination of the fuel low level advisory light required the pilot to 'land as soon as possible', which was defined as:

Execute a power-on approach and landing to the nearest safe landing area that does not further jeopardise the aircraft or occupants.

A warning was included in the flight manual that, with the fuel low level advisory light illuminated:

Sideslips may cause fuel starvation and result in unexpected power loss or engine failure.

The flight manual also contained a Height Velocity Diagram that represented combinations of altitude and airspeed from which "a successful autorotation landing would be difficult to perform". Those figures were calculated at mean sea level, over a smooth hard surface and on a standard day (15 degrees C temperature, 1013.2 mb atmospheric pressure). The manual mandated adjustment to the helicopter gross weight limits, as a function of density altitude, in order for the Height Velocity Diagram to remain applicable. The pilot reported that he entered autorotation from a descending left turn at approximately 200 ft AGL. While the speed of the helicopter as the pilot rolled out of the turn could not be accurately determined, the pilot reported that he established 65 kts in the autorotation descent.

Organisational information

The Civil Aviation Safety Authority (CASA) had conducted regular surveillance audits of the company since issuing the company with an Air Operator's Certificate. The last on-site audit was conducted on 6 July 2001 and a remote audit was conducted on 30 January 2002. Those audits did not indicate any safety deficiencies.

The Civil Aviation Safety Authority approved company Operations Manual directed that "...all operating personnel associated directly with..." the company were to observe the "...instructions, procedures and information contained in..." the manual. The Manual also directed that "...all company personnel associated with piloting and flight line management..." must sign the signature sheet in the master copy of the Operations Manual "...as evidence of having read, understood and agreed to apply the procedures and data contained in it". The occurrence pilot was employed by the operator on a "standard day" contract, and was therefore required to comply with the provisions of the Operations Manual, but was not required to sign the master copy of the Manual.

The coordinator for the Western Tiers operation reported that there was no formal contract in place with the operator for the day's operations and no formal audit of prospective helicopter support organisations by the charter client. It was reported that the operator was contracted for the day based on extensive previous experience operating with the charter client and the statewide experience of its pilots. The occurrence pilot had not previously flown in the Western Tiers area of Tasmania.

Survival information

The pilot reported that a flight operations brief was conducted with personnel present at Lake Mackenzie prior to commencement of the day's operations. That brief included operating around the Hughes 369E helicopter and the operation of the aircraft doors and safety belts. The pilot also reported that, prior to takeoff for the occurrence flight, he had asked the passengers to confirm their seat belts were secure. Passengers reported that they were not wearing headsets during that flight.

Flight notification details for the flight were not submitted to Airservices Australia, nor was there any requirement to do so. There was no formal flight-following process undertaken by the operation. The pilot reported that radio communications with Air Traffic Services (ATS) had not been possible. The pilot reported making a Mayday broadcast on the forestry service channel following the reported engine power loss. That broadcast was not reported as having been received by any station.

Prior to being noted overdue, the pilot had departed Lake Mackenzie for Lake Nameless with an external load and was to return to Lake Mackenzie. At about 1600 hours, the helicopter was reported overdue to the operator by the coordinator of the Western Tiers operation. The operator then alerted Melbourne ATS of the overdue helicopter. At 1652 hours, ATS alerted Australian Search and Rescue (AusSAR). The pilot reported manually activating the Emergency Locator Transmitter (ELT) shortly after 1700 hours. AusSAR directed an aircraft to the area to conduct a beacon search at 1715 hours. That aircraft flight crew made the initial detection of the ELT signal on 121.5 MHz at 1720 hours. The ELT signal was first detected by the COSPAS/SARSAT satellite constellation at 1756 hours.

At about 1900 hours, a rescue helicopter from Hobart located the wreckage and survivors. A number of attempts were made to land at the accident site. Low cloud and fog prevented the landing and the rescue helicopter departed for Launceston airport to refuel. The survivors reported that departure of the helicopter resulted in a marked decrease in their morale.

The ground search and rescue party arrived at the accident site at 2338 hours. The four survivors required treatment for varying degrees of hypothermia and spinal and other injuries. They were transported from the site by rescue helicopter and arrived at Launceston General Hospital by 0516 hours on 29 May 2002.

Occurrence summary

Investigation number 200202442
Occurrence date 28/05/2002
Location Western Tiers
State Tasmania
Report release date 26/02/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer Hughes Helicopters
Model 369
Registration VH-HJT
Serial number 0134E
Sector Helicopter
Operation type Charter
Departure point Lake Nameless, TAS
Destination Tom Whiteley's Hut, TAS
Damage Destroyed

Beech Aircraft Corp 76, VH-TTB

Safety Action

Company safety action

The company has undertaken to provide a fuel tank dipstick for the aircraft.

CASA safety action

Prior to this incident, the Civil Aviation Safety Authority (CASA) had released an NPRM (Notice of Proposed Rule Making), which, in part, deals with precautions before flight and fuel management, as part of the review of the Civil Aviation Regulations. CASA's intent is to introduce regulations that are simple and unambiguous.

The NPRM document contained the following proposed regulations:

'91.180 Precautions before flight

1. The pilot in command of an aircraft must, before flight, inspect the aircraft and review all factors relevant to the safety of the flight that can reasonably be assessed before departure.

2. When reviewing factors likely to affect the safety of the flight, the pilot in command of an aircraft must take such action as is reasonable to ensure that, before take-off, all of the following requirements are met:

k) sufficient fuel is on board the aircraft for it to land at the end of the flight with the required fuel reserves still on board;

l) the quantity of fuel in the aircraft's fuel tank or tanks has been checked by visual inspection or by 2 different methods.'

Significant Factors

  1. The pilot did not establish the actual fuel quantity on board the aircraft prior to departure.
  2. The aircraft fuel tanks contained insufficient fuel for the planned flight.
  3. The right fuel quantity gauge transmitter unit was inoperative.



 

Analysis

The checks conducted by the pilot prior to the flight were inadequate to the extent that the pilot significantly over-estimated the quantity of fuel available for the flight.

The right engine failed due to insufficient fuel in the right tank while the aircraft was in a climb attitude. However, the pilot was apparently confused by the indications of the failure, as evidenced by his attempts to feather the propeller, but then continued with the propeller windmilling, on the assumption that some power was still available. This was despite readily available indications that the engine had failed. The pilot's apparent confusion was probably due to insufficient recurrent training in emergency procedures relevant to the aircraft type.

The pilot apparently over-relied on the tachometer and manifold pressure gauge indications, but lacked an understanding of those indications. Had the pilot recognised that the engine was not producing power, he may have persisted with his attempts and feathered the propeller. This would have increased the aircraft's performance by significantly reducing drag and should have permitted a greater degree of safety for the subsequent return to Essendon.

When the pilot manipulated the throttle lever of the failed engine as part of his engine failure confirmation checks, he should have realised that the engine had lost all power. The yawing of the aircraft as the pilot moved the pitch lever towards the feather position, due to reduced propeller drag, should also have provided a strong indication that the engine had failed.

With marginal aircraft performance, the pilot passed two suitable airfields and rather than divert to Moorabbin, continued to Essendon. This may suggest that fatigue, and possibly a desire to minimise inconvenience to the passengers and the operator adversely affected the pilot's judgement.

Summary

The pilot had planned to conduct a charter flight, with three passengers, from Essendon to Latrobe Valley, Vic. in a twin engine Beech Duchess aircraft. The pilot reported that he arrived at the Essendon airport about 90 minutes prior to the scheduled departure, carried out the daily inspection on the aircraft and submitted an instrument flight rules flight notification. He checked the aircraft maintenance release and the company fuel log that included the aircraft's last flight four days earlier. The pilot reported that he checked the two fuel quantity gauge readings which indicated a half-full tank and a slightly less than half full tank. He then visually checked the contents of the tanks relative to the '30 US gallon' metal tabs that are visible through the filler opening. He estimated that the fuel tanks contained a total of about 200 litres, but did not confirm this, as a fuel tank dipstick was not provided for that aircraft. The pilot's flight plan indicated that 128 litres of fuel, including reserves, would be required for the flight.

During the climb to the planned altitude of 7,000 ft, the right engine's power reduced. The pilot concluded that, from the engine tachometer reading of 1,500 revolutions per minute, and the manifold pressure indications, the right engine had partially failed. He carried out engine failure confirmation checks, but as the propeller pitch lever was very stiff, was unable to place it in the feather position. The pilot later reported that, during manipulation of the pitch lever, the aircraft had yawed significantly. Therefore, he decided to reset the right engine controls to a cruise setting because partial power was preferable to no power.

The aircraft was unable to maintain altitude so the pilot decided to return to Essendon. He requested an air traffic clearance from the Melbourne Approach air traffic controller (ATC) when the aircraft was about 50 NM east of Essendon. After receiving a clearance, and as he turned onto a westerly heading, the aircraft descended into cloud. At the pilot's request, ATC provided headings for the pilot to track further to the south to avoid the higher terrain on the direct track to Essendon. Lowest safe altitude (LSALT) is a published or pilot calculated minimum altitude that ensures terrain clearance during flight in instrument flight conditions. Flight below an LSALT altitude is only permissible during visual meteorological conditions or while conducting a published instrument approach. When the aircraft descended below the LSALT, ATC advised that a diversion to the closer Moorabbin airport, which was to the south east of Essendon and to the south of the aircraft, was available. That option would have allowed the aircraft to track over lower terrain and would have minimised the track distance over the Melbourne suburbs. However, the pilot decided to return to Essendon, where the operator's maintenance facilities were located and the passengers could be transferred to another company aircraft. After descending through the next LSALT step while in cloud, the aircraft descended into visual conditions about 21 NM east of Essendon at about 2,500 ft. The aircraft continued to descend until it stabilised in almost level flight at about 1,500 ft. The pilot then tracked direct to Essendon and carried out a visual approach and landing.

The pilot had bypassed two other suitable airfields, Lilydale and Coldstream, approximately 10-15 NM to the right of his track. The Civil Aviation Safety Authority (CASA) Civil Aviation Orders (CAO) 20.6 permitted the pilot of an aircraft with a failed engine to fly past a suitable aerodrome if another suitable aerodrome was available nearby and the pilot assessed that the aircraft could be flown safely to that aerodrome.

Company engineering inspection of the aircraft found that the right fuel tank, that was supplying the right engine when it lost power, contained no fuel. The right fuel quantity gauge transmitter unit was corroded and seized in a position that resulted in the gauge always indicating half-full. It was possible to feather the right propeller, although the pitch control was stiff.

The control cable and the fuel tank sender unit were subsequently replaced. The pilot commented that he had conducted a feather check as part of the pre-takeoff checks and although the right pitch lever was stiff to operate, he was satisfied that the propeller feathering mechanism was operating satisfactorily. The pilot later commented that the engine had failed due to fuel starvation and that he had not recognised the symptoms of a piston engine failure. He reported that he did not notice the reduced fuel pressure to the right engine until after the aircraft descended into visual conditions.

The aircraft's pilots operating handbook cautioned pilots against attempting to determine the inoperative engine by reference to the tachometers or the manifold pressure gauges and stated that those instruments often indicated near normal readings after an in-flight engine failure.

The pilot had recently resumed employment with the operator. He began his career with the operator and had flown as a first officer on F-27 turboprop aircraft for four years. He then obtained employment with a regional airline for two years as a first officer on turboprop aircraft, and had just completed line training as first officer on a jet aircraft when that airline suspended operations.

The day before the incident, the pilot had completed a 12-hour tour of duty, including 8.1 hours of flight time completing a co-pilot endorsement on a business jet. The two days prior to that had been spent on ground duties. He had 6-8 hours rest overnight at home and had risen early on the day of the occurrence. The pilot reported that he was tired on the day of the occurrence and that he had felt similarly for some time. He had been on duty for 16 consecutive days or a total of 159.4 hours duty time, primarily in a capacity unrelated to his employment as a pilot. Those additional duties were reflected in the pilot's recorded duty times.

The pilot had logged about 3,600 hours total flight time, including 600 hours in command on piston-engine aircraft. Those command hours consisted of about 200 hours twin-engine, of which 25 were in Duchess aircraft. All his other flying had been in turboprop and jet aircraft. During the three months preceding the incident, the pilot had flown approximately 70 hours, but had only flown the Duchess for three hours during that time.

The pilot's work/rest history for the four weeks prior to the incident was examined using a computerised fatigue algorithm developed by the Centre for Sleep Research, University of South Australia. The results indicated that the pilot was probably experiencing moderate levels of fatigue in the week leading up to, and on the day of the incident.

Occurrence summary

Investigation number 200200047
Occurrence date 17/01/2002
Location 93 km SE Melbourne, Aero.
State Victoria
Report release date 23/01/2003
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Beech Aircraft Corp
Model 76
Registration VH-TTB
Serial number ME-359
Sector Piston
Operation type Charter
Departure point Essendon, VIC
Destination La Trobe Valley, VIC
Damage Nil

Cessna 210N, VH-LMX

Safety Action

Verification of the actual fuel quantity during pre-flight inspection would have alerted the pilot to the amended state of fuel quantity on board the accident aircraft. CASA produced an Advisory Circular in September 2001 on fuel planning as guidance for operators and pilots to help ensure correct pre-flight planning procedures and that aircraft carry sufficient fuel to safely complete each flight.

The fitment of upper body restraints to the passenger seat belt systems may have reduced the exposure to some of the serious injuries incurred in this accident. Recommendation R19980281 arising from occurrence 199802830, dated 26 July 1998, was previously made to CASA to address this perceived deficiency with regard to upper body restraints. In response to this recommendation, CASA issued a Discussion Paper `Proposed Airworthiness Directive, General Series - Upper Torso Restraints for Occupants in Small Aircraft' explaining the intention to introduce such a requirement and inviting comment by the industry. The public comment period closed 01 March 2002 and CASA is now considering these comments prior to promulgation of the AD.

The Bureau's response to that action was RESPONSE STATUS: MONITOR. The ATSB will continue to monitor the CASA action and any further correspondence will be published on the ATSB website www.atsb.gov.au.

Analysis

Fuel quantity calibration and indication

Although the aircraft fuel gauges differed between left and right tanks for a given scale marking, this was compensated for by having a calibration correction card fitted to the aircraft. It is not uncommon to have such discrepancies between multiple gauges in the same aircraft and should not have been a factor in this accident.

As a back up measure the aircraft also carried a dipstick, which was usually locally manufactured by the maintenance organisation. It could be used by the pilot to verify the actual fuel quantity on board before or between flights. The dipstick found at the crash site, although not calibrated specifically for the accident aircraft, should have given a reliable enough reading to alert the pilot to the 80L discrepancy in the fuel quantity on board; if it had been used. Passengers did not see the pilot verify the fuel quantities at Rawlinna, either visually or by using the dipstick. It could not be determined if the pilot verified the actual fuel quantity on board, visually or by dipstick prior to departing Kalgoorlie but, considering the incorrect trip log annotation of 160L in each tank, it is unlikely that he did.

The fuel that rescuers observed leaking onto the front seat occupant and which had pooled under the aircraft, probably came from the disrupted fuel lines around the fuel tank selector in the first instance and later augmented by the right door pillar supply line from the right tank that was severed during the rescue. As the residual fuel in the left tank was not able to feed to the fuel selector supply lines, the fuel remaining in the left tank only approximated to the unusable amount, as published in the POH, for that tank.

The selected position of the yellow segment of the auxiliary fuel pump switch as observed at the accident site, was consistent with emergency checklist action following an inflight engine power loss or vapour purge.

The fuel selector was found selected to the right tank. The fuel pump switch and fuel selector position observations were considered in conjunction with the pilot's trip log notes showing that the flight immediately prior to the power loss was conducted on the left tank. If the pilot had conducted the emergency checklist actions, as seems likely based on the auxiliary fuel pump switch selection, then he had selected the fuel selector to the opposite tank. The evidence was consistent with a power loss while operating from the left fuel tank and a probable attempted engine re-start after changing fuel tank selection to the right tank.

In flight engine restart

The radio call made by the pilot gave the aircraft height of about 800ft above ground level (AGL) at the time the engine lost power. This would have provided gliding time of approximately one minute in the flaps up configuration recommended by the POH; and used by the pilot. This short interval after the engine power loss may have been insufficient for the pilot to successfully complete an in-flight engine re-start drill.

Fuel tank exhaustion - fuel supply starvation

The aircraft fuel usage annotations recorded in the trip fuel log by the pilot showed that he had started his fuel calculations with 80L more fuel than was on-board. The annotations also showed that the left tank had been used for taxi and take off on both flight sectors that day. Take-offs were the periods of highest fuel demand by the engine and in accordance with the POH, should have been conducted from the fullest tank. The trip fuel log showed that, on departure from Rawlinna, the right tank contained the most fuel and, therefore, should have been used for that take off.

Whether prolonged taxi or extended use of climb power using the left tank took place could not be verified and the possibility of additional fuel usage from the left tank during these periods could not be ruled out.

The pilot's fuel usage annotations showed that he calculated the aircraft had used approximately 69L from the left tank and 70L from the right tank in total for both sectors that day, up to the last hand written entry for the fuel tank selection change at 1345. Using the operator's average fuel consumption figure for this aircraft, a further 28L needed to be used from the left tank by the time that the engine lost power; approximately 1413. If the tank selections were correctly carried out as annotated by the pilot, the total fuel burn from the left tank would have been around 97L, which should have left approximately 23L remaining in that tank. The tank was observed, at the accident site, to contain approximately half a litre of (unusable) fuel. It could not be positively determined why only unusable fuel remained in the left fuel tank.

The previous accident in 1995 demonstrated, that on at least one other occasion, this aircraft's left fuel tank contents could be exhausted after one hour and 40 minutes of operation from a `tabs level' fuel quantity. Flight time of the Kalgoorlie accident flight, while operating on fuel supplied only from the left tank, was estimated to have totalled approximately one hour and 37 minutes. It was therefore possible that the contents of the left tank may have also been exhausted on the Kalgoorlie, Rawlinna, Kalgoorlie flight in this period of time.

Operations with low-fuel quantity

The trip fuel log revealed that the pilot would have expected to have 40L more fuel remaining in each tank at the time the engine lost power. Consequently, he may not have considered a low fuel state as a possible cause for the engine power loss.

Flying in turbulence with a low fuel state can also lead to uncovering of the fuel outlets in the fuel tanks. If the pilot had correctly carried out the tank changes noted in the trip log, the left tank should have had approximately 23L of fuel remaining when the engine lost power; which equated to about an eighth of a tank. If such a quantity was present in the reported turbulent conditions, then the possibility of unporting the fuel outlets could not be ruled out.

Summary

The low fuel-state of the left tank alone, or in combination with the forecast turbulence, probably caused the engine to lose power.

In the absence of evidence of a mechanical failure leading to engine loss of power, the most likely cause of the engine loss of power was associated with fuel supply starvation or exhaustion.

The presence of a vehicle on the road appeared to have caused the pilot to initiate a sudden pull back on the flight controls that led to a loss of control and subsequent impact with the ground.

Factual Information

The pilot of a Cessna 210 Centurion was tasked to fly three passengers from Kalgoorlie WA to Rawlinna WA and return.

The aircraft departed Kalgoorlie at 0804 Western Standard Time for Rawlinna with the flight proceeding without incident. The trip fuel log showed that the pilot believed that the aircraft arrived in Rawlinna with approximately 106L remaining in the left tank and 130L remaining in the right tank. The aircraft was not refuelled at Rawlinna.

Two passengers watched the pilot prepare for the return journey from Rawlinna. They reported that the pilot appeared to do a walk around the aircraft and one passenger stated that although he saw the pilot `check things at the front, wingtips and tail', the pilot did not check the fuel tanks in the wings. At approximately 1250, the flight departed for Kalgoorlie. One of the passengers recalled that, shortly after reaching a cruise altitude of about 4,000ft, the pilot appeared to become agitated and was checking something on the floor between the seats. This concerned the passenger, but after a few minutes, the pilot settled down and the passenger assumed that whatever had been a concern, was resolved. The fuel selector is located on the floor between the two front seats.

One passenger with recollection of the remainder of the flight from Rawlinna, stated that it appeared routine up until the engine lost power while the aircraft was approaching Kalgoorlie. (Due to the serious nature of the head injuries sustained in the accident by all of the passengers, their recollections of the flight prior to the engine power loss were very fragmented.)

At approximately 1413, the pilot was heard to broadcast a distress call including the aircraft altitude of 2,000 ft above sea level and his intention to land on a road. During the landing attempt, the passenger in the right front seat observed a car appear in the landing path. The passenger reports of what occurred after the car appeared were consistent with the pilot attempting to climb the aircraft to avoid the car and subsequently losing control of the aircraft during the manoeuvre.

The driver of the car and his wife saw the aircraft pass silently overhead as it crossed the road in a southerly direction. When it impacted the ground, the car driver's wife said that it appeared to `really bury in' before it was obscured by a large cloud of dust.

The driver immediately called emergency services and then he and his wife attempted to render assistance to the occupants. The pilot was fatally injured while the passengers were seriously injured.

Wreckage information

The aircraft impacted the ground in a left wing low, nose-down attitude. Examination of the aircraft found the left and right fuel tanks intact, but the fuel system plumbing was disrupted by cabin distortion at the fuel tank selector valve under the floor. The fuel line to the firewall mounted filter strainer and engine was broken and the strainer was destroyed during the accident impact sequence. The forward door pillar had been severed on the right side of the aircraft by hydraulic cutters used during the rescue effort to free the trapped front seat passenger. The examination of the fuel tank selector revealed that the right fuel tank was selected at impact.

Fuel had poured on to the right front seat occupant during the rescue and had continued for a considerable amount of time after the accident. No fuel remained in the right tank when it was examined by the investigation team on site. The rescuers said that they had not observed fuel to leak from the left wing onto the ground at any time. The aircraft's left wing low attitude uncovered the engine fuel supply lines at the inboard end of the tank and, as a result prevented the remaining left tank contents escaping through the damaged connections to the fuel selector. Less than half a litre of clean fuel remained in the outboard section (lowest point) of the left tank compartment and was considered to approximate the unusable amount for the tank. A sample of the Avgas, which was normal green colour, was taken from the aircraft and inspected at the accident site. It was free of any water or particles in suspension and visible contaminants. The fuel uplift for the flight was from the Kalgoorlie aerodrome. This fuel supply was tested by the supplier and found to be within correct specification.

The left-wing vent line was also clear of the remaining contents and did not appear to have been capable of allowing the remaining contents to drain off through the left-wing tip vent due to the syphon effect. The fuel contractor's log showed that there were multiple deliveries from the same batch of fuel to other aircraft operating from Kalgoorlie airport coincident with the delivery to VH-LMX. The bureau found no reports of fuel related problems with any of these other aircraft.

The fuel system components were bench tested and found to be capable of normal operation within the manufacturer's parameters. The wreckage, engine and component examinations found no evidence of pre-existing mechanical defects with the aircraft or its systems, that would have prevented normal operation of the aircraft prior to the accident.

Fuel pump switch

The auxiliary fuel pump switch is a two-segment split rocker type mechanism. The right half was colour-coded yellow and the left half red. The yellow half was marked START, with the upper position as ON and was used for normal start and some minor vapour purging if required. It was usually selected OFF for normal flight. In the event of an engine driven fuel pump failure in cruise flight, the yellow switch selected to ON should have provided, through a micro-switch arrangement, sufficient fuel for normal engine operation. The red half of the switch was marked EMERG (emergency) with its upper position marked as HI. This red switch was used in the event of an engine driven fuel pump failure during take-off or high-power operation and also extreme vapour purging. When the auxiliary fuel pump switch was removed and examined the yellow segment was found in the ON position.

A fuel dipstick with graduated markings on it was found in the baggage compartment of the aircraft. It was marked C210M VH-WXC and had the following graduations: LEFT FULL, 140, 100, 60, 30 with identical graduations and the word RIGHT on the reverse side of the stick. A check of the type certificate data sheet revealed that the C210N (accident aircraft) was fitted with identical type and capacity fuel tanks to the C210M.

Emergency locator transmitter

The aircraft was fitted with an emergency locator transmitter that activated upon impact. The transmission was received and logged by the Australian search and rescue organisation (AUSSAR) for 2hrs 39 mins before local police disabled the transmitter.

Pilot information

The pilot held a valid Australian commercial pilot licence and command instrument rating. He held a valid Class 1 medical certificate and did not require vision correction while operating an aircraft. At the time of the accident the pilot had accrued a total of 1,087 hours flying experience with 317.5 hours on the Cessna 210. From interviews and postmortem results, no evidence was found that the pilot had any personal or medical problems that may have adversely impinged on his ability to conduct the flight.

Survival

The nose-down, left wing low attitude of the aircraft as it impacted the ground exposed the left front seat occupant (the pilot) to the full force of the impact.

The passengers sustained numerous serious injuries in the form of fractures to legs, upper bodies and heads as well as injuries to internal organs. The leg injuries probably occurred when the floor was forced in an upward direction during the impact sequence. The floor movement also released the anchor points for the front seats. The middle row right seat remained fixed to its mounts. The middle left seat remained fixed by its rear mounts and forward left mount but with the front right mount partially released. There were no upper body restraint systems fitted to the passenger seat row positions in the aircraft, nor were any required to be. The upper body and head injuries sustained by all occupants were probably due to upper torso flailing contact with interior structure and objects. The front seat positions were fitted with upper body restraints. The effectiveness of the front seat restraint systems was compromised by the loss of integrity of the seat to floor attachments. The rearward movement of the engine firewall during the impact sequence may also have reduced the front seat survival space between front seat occupants and control panel structures; which would have increased exposure to injury.

Weather

The weather forecast for the day was for fine conditions, but with thunderstorm activity expected in the Kalgoorlie area during the afternoon after the flight. Other pilots reported experiencing some heavy turbulence in the area during the day and the operator's Chief Pilot remarked it was, `the first really rough day of the season'. The passengers recalled that, for the portions of the flight that they could remember, there was some turbulence but remarked that it was not unusually rough.

Aircraft fuelling

The afternoon before the charter flight, the aircraft operator requested the fuel contractor to fill the aircraft tanks (capacity 160L in each of two tanks) `to the tabs', which equated to a fuel quantity of approximately 120L in each fuel tank. The fuel request form was normally faxed to the fuel depot during the afternoon, but as no request had been received by the time he was due to commence fuelling tasks, the fuel contractor obtained the request sheet by walking to the aircraft operator's office and retrieving the original. The contractor noted that the sheet had been amended by the use of white-out correction fluid and that the original request entered had been for full tanks. It could not be positively determined if the pilot had sighted this fuel quantity request sheet.

Company pre-flight briefing

Some months after the accident, a director of the company stated that he spoke to the pilot in the afternoon prior to the accident flight. This conversation covered the task briefing for the following day and included the fuel load as being `to the tabs'. If this was so, the weight and balance calculations made by the pilot for the flight, in which a `full fuel' quantity was used and showed that the aircraft was close to maximum take-off weight, did not reflect any knowledge that he had received the `fill to tabs' fuel information. The director could not confirm whether the pilot assimilated this information at the time he talked to him.

Aircraft service history

The aircraft had been maintained in accordance with the relevant Civil Aviation Regulations and Orders. The aircraft had a valid maintenance release at the time of the accident with no maintenance overdue. Because a fuel quantity system calibration was required by the Civil Aviation Safety Authority (CASA) every three years as part of an airworthiness directive (AD), a calibration had been carried out six months prior to the accident in accordance with the AD. The gauge calibration results recorded in the aircraft logbook were as follows:

Left 10/46, 20/83, 30/117, 40/167, F/169 (Gallons/Litres)
Right 10/38, 20/65, 30/100, 40/145, F/164 (Gallons/Litres)

The aircraft fuel gauges, calibrated in US Gallons, were within the required parameters but the quantities differed between the left and right tanks for a given scale marking. This was compensated for by having a calibration correction card fitted to the aircraft. The calibration recordings in the logbook did not include a value for E (empty). However, the calibration card fitted to the aircraft stated that for E indication on the gauge, the tanks were to be read as empty.

A review of the aircraft's history revealed that, when being operated by its previous owner on the east coast, it had been involved in a similar accident in 1995 when it was force landed due to engine power loss. The aircraft had also taken off with the fuel tanks filled `to the tabs', and on that occasion it was estimated that the pilot had operated the aircraft for approximately 1 hour and 40 minutes when the engine lost power. The left fuel tank was used for the entire flight and when examined at the accident site, it was found to be empty.

Flight trip log

A company trip fuel log for the flight was found at the accident site. This log was being used by the pilot to record flight times and fuel usage from each tank for the flight. It had the following annotations:

PlaceTimeLeftRight
KG0804160160

 
34130160

 
04130130
RAW0928106130
RAW1250106130

 
0591130

 
13459190

The trip fuel log noted that the fuel tanks contained 160L in each tank on departure from Kalgoorlie.

The take-off from Kalgoorlie had been conducted using fuel from the left tank. The trip fuel log indicated that the aircraft had consumed 54 litres from the left tank and 30 litres from the right tank during the flight to Rawlina. Additionally, the log indicated that the pilot elected to remain on the left tank for the taxi, pre-take-off checks, take-off and departure from Rawlinna thereby carrying out both take-offs using fuel from the left tank. The pilot recorded an initial use of 15L from the left tank on departure from Rawlinna, followed by 40L from the right. At 13:45 WST he changed the selection to the left tank. About 28 minutes later, the engine lost power.

Pilots Operating Handbook (POH)

The aircraft was fitted with a placard that provided information in the form of a checklist in the event of major fuel flow fluctuations and/or engine power surges. Additionally, the POH provided expanded procedures for inflight engine restarts and excessive fuel vapour in the fuel system. The POH also noted that if the propeller is windmilling, the engine will start automatically within a few seconds. If the propeller has stopped (possible at lower speeds), turn the ignition switch to START, advance the throttle slowly from idle, and (at higher altitudes) lean mixture from full rich.

The POH went on to indicate that with fuel quantities of less than a quarter tank, prolonged uncoordinated turns or slips should be avoided as it might uncover the fuel tank supply outlets and starve the engine of fuel.

Engine out glide distance

The MAYDAY transmission made by the pilot placed the aircraft at a height of 800 ft above ground level. This height, according to the Maximum Glide graph in the POH, equated to approximately 1.2 NM, or approximately one minute of glide time from the time at which the engine lost power to the impact point.

Occurrence summary

Investigation number 200105446
Occurrence date 14/11/2001
Location 10.7 km ESE Kalgoorlie/Boulder, Aero.
State Western Australia
Report release date 16/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 210
Registration VH-LMX
Serial number 21063509
Sector Piston
Operation type Charter
Departure point Rawlinna, WA
Destination Kalgoorlie, WA
Damage Destroyed

Bell 206B(III), VH-SVW

Safety Action

As a result of this occurrence, the Australian Transport Safety Bureau issues the following safety recommendation:

Recommendation 20020030

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority review the adequacy of the continuing airworthiness requirements for seat belts and shoulder harnesses to ensure that they maintain applicable design standards throughout their service life, when installed in Australian registered aircraft and helicopters.

Analysis

Aerial firefighting operations are typically conducted in heavily forested, remote areas with water sources readily accessible to the helicopters for rapid refilling and turn-around times. Pilots experience high workloads and are susceptible to task saturation during firefighting external load flights and may fly multiple flights during a short period of time. Pilots may rely on the helicopter fuel gauge more so than during, for example, a cross-country flight where fuel consumption may be calculated using fuel burn versus time. Helicopter fuel gauges are subject to variations in roll and pitch attitudes, which make an accurate indication difficult.

The investigation found no evidence to suggest that the helicopter was not serviceable at the time of the accident. If the forward boost pump circuit breaker had been disengaged during the flight, the fuel pressure/load meter gauge should have indicated a low reading and the associated BOOST PUMP caution advisory light should have illuminated. The investigation could not conclusively determine how, or when, the forward boost pump circuit breaker became disengaged.

The pilot's shoulder harness failed because of deterioration of the material of the harness. The harness had remained in service even though the material had degraded, as there were no existing requirements to determine the serviceability of the harness following installation.

The investigation determined that the fuel supply to the helicopter's engine was interrupted, resulting in engine surging and subsequent flameout.

Summary

The Bell Jetranger 206B (III) helicopter was engaged in aerial firefighting operations utilising an external water bucket and staging out of a nearby national park campground. The pilot reported that he started flying at approximately 0750 EST after completing a pre-flight check of the helicopter which included draining the fuel sump, inspecting the fuel and confirming 106 L or 27.9 United States Gallons (USG) of total indicated fuel. At approximately 0825, while engaged in water bucket operations, he discussed his fuel status with other company pilots on a common radio frequency and noted 38 L (10 USG) of indicated fuel remaining. He finished a swath run of the fire area, dropping water and then decided to complete one more swath run before returning to refuel.

Approaching the fire line, the helicopter entered a left turn at approximately 200 ft above ground level (AGL). The pilot reported that the helicopter was buffeted by strong turbulence, which caused the helicopter to yaw left and go out of trim. He reported that the engine power then began surging and, subsequently, an engine flameout occurred. He continued the left turn, jettisoned the water and initiated a power-off autorotation to a heavily wooded area.

During the autorotation, the helicopter's main rotor blades contacted nearby trees, damaging the blades and displacing the main rotor transmission. The helicopter then came to rest on its right side, on a 45 degree slope. The pilot exited the helicopter and was picked up by another company helicopter and transported to hospital for observation. The pilot suffered minor injuries and the helicopter was substantially damaged. There was no evidence of any in-flight or post-accident fire.

The pilot reported that he had no recollection of any illuminated caution advisory lights during or prior to the event, or of the position of the switches and circuit breakers of the fuel boost pumps. He stated that he followed flight manual checklists when starting the helicopter and preparing for takeoff.

Wreckage examination

The helicopter sustained damage to the main rotor blades and controls, main rotor transmission, transmission to engine driveshaft, tail rotor driveshaft, pilot's perspex and right side forward fuselage. Examination of the engine revealed no external damage or damage to the compressor.

Fuel system examination and background

After the helicopter was repositioned upright, the fuel gauge indicated approximately 19 L (5 USG). The fuel in the fuel tank was examined and appeared to slightly cover the base of the fuel boost pumps. Examination of the airframe fuel filter revealed full fuel in the filter bowl and no contamination. Examination of the engine fuel filter revealed a small amount of fuel and no contamination. The forward fuel boost pump circuit breaker was noted as disengaged.

Unusable fuel was defined as, `Fuel that cannot be used in flight with wings level and at cruise angle of attack (or nose 3 degrees up)'. Of the total fuel on board, 4 L (1 USG) were unusable. Upon removal from the accident site, the helicopter's fuel system was drained and 23.5 L (6.2 USG) of fuel were removed. The fuel correction card annotated, `gauge indicates 38 L (10 USG) for an actual of 45.6 L (12 USG)'. The fuel correction card values were verified by adding measured amounts of fuel.

An option on that model helicopter was a FUEL LOW caution advisory light that illuminated with approximately 76 L (20 USG) of total fuel remaining. The helicopter was not equipped with that advisory light. It was equipped with two electrically operated submerged fuel boost pumps located in the fuel cell and connected in parallel to the engine's fuel supply line. Those pumps were located on the helicopter's centre-line. Both boost pumps were examined following the accident and they were determined to be serviceable.

Fuel consumption

According to the operator's operations manual, the fuel consumption rate of the Bell 206B (III) helicopter was 110 L (28.9 USG) per hour. In the 35 minutes of operating time that the pilot reported prior to the accident, approximately 64 L (16.8 USG) of fuel should have been consumed, leaving approximately 30.8 L (8.1 USG) of useable fuel remaining. That amount should have been sufficient for approximately 17 minutes of engine operating time.

Engine auto-reignition

The helicopter was not fitted with an optional engine auto-reignition system. Because of the low height AGL at the time of the engine surging and flameout, the pilot did not have an opportunity to attempt a manual restart of the engine.

Engine testing

The Rolls-Royce Allison model 250-C20B engine, serial number CAE 840551, was removed from the helicopter and transported to an engine test cell for testing. Following motoring and priming, the engine started on the first attempt with Turbine Operating Temperatures, N1 (gas generator speed) and N2 (power turbine speed) values within normal operating parameters. Engine deceleration and acceleration tests were conducted in order to simulate power changes experienced during flight. The results of the testing indicated that the engine was serviceable at the time of the accident.

Helicopter manoeuvring in turns and flight manual requirements

During coordinated turns, centrifugal force acting on the helicopter and fuel tank causes the fuel to collect evenly in the bottom of the fuel tank. It is then available for pick up by the fuel boost pumps at the boost pump inlets and through to the inlet of the main fuel supply line and to the engine. During uncoordinated turns, centrifugal force may not displace the fuel to the bottom of the tank evenly and instead fuel sloshing may take place.

The helicopter's flight manual contained a warning regarding flight with one fuel boost pump inoperative. It stated, `Due to possible fuel sloshing in unusual attitudes or out of trim conditions and one or both fuel boost pumps inoperative, the unusable fuel is ten [US] gallons'.

Component testing

The forward fuel boost pump circuit breaker was removed and tested. Aircraft system 28 DC voltage was applied and varying amperes were introduced to the circuit breaker in an attempt to determine its serviceability. The circuit breaker operated normally up to its rated 10 ampere rating with no anomalies noted.

Pilot's shoulder harness

The pilot's left shoulder harness had broken and separated at a point just forward of and below the pilot's shoulder. The manufacturer's date stamped on the harness belt was March 1973. The pilot's seat belt had an inspection tag attached with the inspection date 11/99 annotated. Details of the inspection were not annotated in the helicopter's documentation.

Pilot shoulder harness testing

The pilot's left shoulder harness was sent to an independent belt and harness testing and repair organisation for testing. The webbing was identified as MIL-T-50368 Type IV, 2 inch Nylon Webbing, rated at 2,000 pounds strength. The rated assembly strength of the harness assembly was 1,500 pounds. Testing revealed that the webbing failed at a value of 391 pounds, or less than 20 percent of the original strength of the material. Factors contributing to the loss of original strength were ageing related to ultraviolet light exposure, abrasion damage and contamination by turbine oil.

Seat belt and shoulder harness standards

Australian Civil Aviation Order (CAO) Part 108, Section 108.42, contained specifications for aircraft safety belts (seat belts), harnesses (shoulder harnesses) and inertia reels manufactured in Australia. Contained within CAO Part 108, Section 108.42 was a reference to Technical Standard Order (TSO)-C22g, which specified minimum performance standards of aircraft seat belts when new.

CAO Part 108, Section 108.42, also contained a reference to British Air Registration Board (ARB)/Civil Aviation Authority (CAA) Specification Number four (issue two). That document specified minimum performance standards for British manufactured aircraft shoulder harnesses when new and was not applicable to equipment manufactured in the United States of America (USA) such as the separated harness in this occurrence.

The Australian Civil Aviation Safety Authority (CASA) Airworthiness Directive, AD/RES/29 amendment 1, mandated identification of aircraft seat belts to indicate that the part was an item approved by the manufacturer. Part of that directive mandated appropriate identification to demonstrate compliance with CAO Part 108, Section 108.42.

The helicopter was manufactured in 1979 in the US under the requirements of the US Federal Aviation Administration (FAA), Federal Aviation Regulations. FAA Technical Standard Order (TSO)-C22g (amended 1993) outlined minimum performance standards for aircraft seat belts when new. TSO-C114 (initial issue 1987) outlined minimum performance standards for aircraft torso restraints (shoulder harnesses) when new. Prior to 1987, there were no requirements for shoulder harnesses. Only TSO-C22 was in effect when the occurrence helicopter was manufactured.

At the time of the occurrence, there were no requirements to confirm compliance to applicable design standards of shoulder or seat belt harnesses while in service, or to specifically identify shoulder harnesses.

Occurrence summary

Investigation number 200104604
Occurrence date 24/09/2001
Location 5 km W Kurrajong Heights
State New South Wales
Report release date 24/09/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Bell Helicopter Co
Model 206
Registration VH-SVW
Serial number 2814
Sector Helicopter
Operation type Aerial Work
Departure point Bilpin Area, NSW
Destination Bilpin Area, NSW
Damage Substantial

Boeing 717-200, VH-AFR

Safety Action

Local safety action

As a result of their investigation, the engine manufacturer:

  1. Revised the status of the FMU fault codes raising the code rectification priority from Long-Term Dispatch (LTD) to Short-Term Dispatch (STD). This is to both ensure crew awareness of critical nature faults and to shorten the period of continued service with such fault codes to 10 days (or 150 hours).
  2. Initiated a software change to change the EEC response to RAM parity errors to prevent the repeated multiple resets experienced by EEC channel B during this event.
  3. Issued an aircraft maintenance manual change to introduce a check for EEC FMU faults while the engine is running as part of the FMU installation task.

In addition, the airframe manufacturer:

Issued aircraft maintenance manual revision 73-21-03 dated July 01/2001, to publish item 3 above.

ATSB safety action

As a result of the investigation, the Australian Transport Safety Bureau issued the following recommendations.

R20010251

The Australian Transport Safety Bureau recommends that the Australian Civil Aviation Safety Authority ensure that all Boeing 717-200 aircraft on the Australian Register are fitted with a flight recorder system that complies with the requirements of all applicable Australian Civil Aviation Orders.

R20010252

The Australian Transport Safety Bureau recommends that the Australian Civil Aviation Safety Authority review flight recorder start/stop logic for all types in the Australian fleet where a type acceptance certificate has been issued to ensure that the aircraft meets the requirements of the Australian Civil Aviation Orders.

R20010253

The Australian Transport Safety Bureau recommends that the Australian Civil Aviation Safety Authority ensure that all aircraft entering the Australian Register be subject to appropriate scrutiny to ensure that the aircraft complies with the requirements of the Australian Civil Aviation Regulations and Civil Aviation Orders.

The investigation also identified safety deficiencies relating to the Boeing 717-200 emergency procedures checklist for ENGINE FAIL/SHUTDOWN IN FLIGHT and ENGINE RESTART IN FLIGHT.

Any responses or subsequent recommendations resulting from these safety deficiencies will be published on the Australian Transport Safety Bureau website, www.atsb.gov.au

Analysis

Electronic Engine Controller

Prior to the occurrence, the fuel metering unit fault codes were logged on the electrically erasable/programmable read-only memory of the electronic engine controller, possibly because of a loose connection at the harness or connector. It is likely that the codes were still logged on the EEPROM at the time of the event, resulting in the degraded condition of channel A.

When the in-flight shutdown occurred, the EEC was performing primarily on Channel B. When Channel B experienced the RAM parity errors and the subsequent repeated multiple resets, the EEC reverted to Channel A for primary control of the engine. As Channel A was degraded by the pre-existing FMU electrical fault codes present, neither channel was able to control the engine. The fuel-control metering valve, which is spring loaded into the closed position, then closed following signal loss, resulting in fuel starvation and engine shutdown.

In-flight engine restart

As the aircraft's indicated airspeed varied during the event from 235 knots to 270 knots, it is possible that the fluctuating airspeeds resulted in the low N2 values witnessed. The DFDR discrete signals did not include a discrete signal for the engine starter switch or the engine starter air valve, therefore their activation could not be confirmed. The faults present in the EEC would have prevented any attempt by the crew to restart the engine with the start switch, as the starter air valve would not have opened to allow bleed air for engine rotation. The engine manufacturer stated that a successful start could only have been achieved had the EEC received a "power" reset (circuit breakers pulled and reseated). Fuel switch resets would not have cleared the problem. Consequently, the flight crew's attempt or attempts at a restart could not have succeeded.

Flight Data Recorder

The Boeing 717 flight recorder installation operated so that when the aircraft taxied to a holding point and the park brake was set, the Flight Data Recorder stopped recording until the park brake was released. Essential information relating to the operation of the aircraft would not be recorded. The loss of recorded information may impede an air safety investigation and preclude an accurate determination.

Summary

A Boeing 717 aircraft was in a left turn holding pattern, descending through flight level 230, when the right engine shut down. The flight crew actioned the emergency procedures and attempted, unsuccessfully, to restart the engine. They notified air traffic control of the problem, then requested and received a vectored straight-in approach and landing.

Following the event, the operator's maintenance personnel conducted troubleshooting of the right engine. Several fault codes were noted in the computer memory, which related to Channel A of the electronic engine controller (EEC). A maintenance records check found that the right engine fuel metering unit (FMU) had been replaced approximately 50 flight hours prior to the event. At the time of the event, there were no maintenance manual requirements for an EEC stored faults check following an engine run after replacement of the FMU. Maintenance personnel noted, then cleared, the fault codes from the computer memory and the engine was successfully test run. They then chose to remove both the right engine FMU and the EEC for further testing. The EEC unit was sent to the engine manufacturer for bench testing and operating on a test bed engine.

Component testing

The FMU manufacturer's testing found no faults in the unit. Initial testing of the EEC by the engine manufacturer could not duplicate, on the test bed engine, the dual channel failure and subsequent shutdown. Analysis of the fault codes recorded by the operator's technicians following the event confirmed that several FMU electrical related fault codes were pre-existing on Channel A of the EEC at the time of the occurrence. When the engine manufacturer repeated the testing with the recorded fault codes entered into Channel A of the EEC, and simulated loss of Channel B, they successfully repeated the dual channel failure and resulting engine shutdown.

Electronic engine controller

The electronic engine controller was a two-channel (Channels A and B) electronic unit with system redundancy. It controlled, among other items, engine start sequencing, power requirements, operating temperature, turbine speeds, fuel flow, engine monitoring, and automatic relight. It contained fault detection, storage, and readout capabilities, all stored on an electrically erasable/programmable read-only memory (EEPROM) located on a computer board assembly. The EEPROM provided a history for troubleshooting purposes of any fault event within the EEC or associated control systems by logging a fault code of the event. Those fault codes were then stored until intentionally cleared during maintenance action. The distinct two-channels in the unit ensured that should one channel fail, the other would assume control and monitoring of the engine. Testing by the engine manufacturer revealed that repeated random access memory (RAM) parity errors in Channel B of the EEC resulted in repeated multiple resets of the channel. Those repeated resets had proven to result in a loss of Channel B functionality.

Engine rotation during restart attempts

Following the event, the flight crew stated that they could not obtain a windmilling engine N2 (gas generator RPM) value of 14% as required in the emergency procedures for restart of the engine. They stated that the maximum engine N2 witnessed was 8%.

The engine manufacturer recommended a 14% N2 value (approximately 2,380-RPM) at fuel introduction during engine starting procedures. That allowed a cooler start and prevented engine deterioration. The value of 8% N2 for the ALL ENGINE FLAMEOUT emergency windmilling procedure was based on the minimum engine-driven fuel pump pressure to open the engine pressurising valve. The airframe manufacturer reported that windmilling flight tests were successfully demonstrated at airspeeds as low as 240 knots with N2 windmilling rotor speeds as low as 8%.

The airframe manufacturer estimated that at a stable condition of 10,000 ft altitude, and 250 knots indicated airspeed, the occurrence engine should have exceeded 10% N2 before engine start switch engagement. Their review of the digital flight data recorder (DFDR) revealed no evidence of N2 increase as would be seen with engine starter engagement. The airframe manufacturer reported that their understanding was that the anomalies experienced during the event would have prevented the starter air valve opening during the restart attempts.

Flight data recorder

Examination of the recording indicated that the aircraft arrived at the destination and then departed on another flight to the north. The reported ground runs had not been recorded, as required by Civil Aviation Order (CAO) 20.18 Section 6 paragraph 6.6.

Australian CAO 20.18 Section 6 paragraph 6.6 stated, "The operator of an aircraft which is required by this section to be equipped with recorders shall take action to ensure that during ground maintenance periods the recorders are not activated unless the maintenance is associated with the flight data recording equipment or with the aircraft engines."

Australian CAO 20.18 Section 6 paragraph 6.3 stated, "Where an aircraft is required to be so equipped by this section, the flight data recorder system shall be operated continuously from the moment when the aircraft commences to taxi under its own power for the purpose of flight until the conclusion of taxiing after landing."

The intent of the Australian legislation was that when an aircraft commenced taxiing under its own power for the purpose of flight, the flight data recorder (FDR) would record until the aircraft was parked at the conclusion of the flight. That action ensured a continuous record of aircraft operation was maintained for the duration of the flight.

Subsequent Enquiries made to Boeing Long Beach Division, the aircraft manufacturer, revealed that when the aircraft park brake was set, the FDR would cease recording. Boeing Long Beach Division stated that the FDR would begin recording by two methods. The first "normal" recording mode activated when either fuel shutoff switch was set to run and the park brake was released. The second "maintenance" recording mode was activated by accessing a FDR RUN command via the Multifunction Control Display Unit.

Aircraft Australian certification

The Boeing 717-200 was issued a Type Acceptance Certificate in accordance with Civil Aviation Regulation, (CAR) 21.29A which allowed Type Certificate acceptance for imported aircraft certified by the National Airworthiness Authority (NAA) of a recognised country, in this case the United States of America. The Boeing 717-200 aircraft may not comply with the appropriate Australian Civil Aviation Regulations and associated Orders.

Occurrence summary

Investigation number 200100477
Occurrence date 03/02/2001
Location 19 km N Melbourne, Aero.
State Victoria
Report release date 24/12/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 717
Registration VH-AFR
Serial number 55062
Sector Jet
Operation type Air Transport High Capacity
Departure point Sydney, NSW
Destination Melbourne, VIC
Damage Nil

Cessna 310R, VH-HCP

Factual Information

At about 1930 Western Standard Time1 on 26 January 2001, a Cessna 310R aircraft, VH-HCP, departed Kiwirrkurra, Western Australia (WA), for Newman. The flight was conducted at night under the visual flight rules (VFR), with one pilot and three passengers on board. The aircraft was operated by the Air Support Unit (ASU) of the WA Police Service and had been used to transport police officers from Newman to Kiwirrkurra earlier that day.

The aircraft arrived in the circuit area at Newman at about 2150 for a landing on runway 23. Witnesses at the aerodrome heard the engines start to 'cough and splutter'. Soon after, the aircraft collided with the ground about 3 km to the east of Newman aerodrome. The four occupants sustained fatal injuries. Impact forces destroyed the aircraft.

The investigation determined that both of the aircraft's engines failed due to fuel starvation,2 prior to impact with the ground. There was no evidence of a technical malfunction or of an in-flight fuel leak. From the information available, the investigation calculated that the aircraft probably had about 165 L of useable fuel at impact. Approximately 30 L of fuel was recovered from the aircraft's auxiliary fuel tanks and it was probable that fuel had leaked from these tanks post-impact.

The investigation identified a number of factors that had contributed to the circumstances of the accident. These factors included operational events on the night of the accident, local conditions associated with the circumstances of the operational events, the defences that were used to manage risk, and organisational conditions that influenced the effectiveness of the defences.

Operational events and local conditions

The investigation identified a number of deficiencies associated with the pilot's pre-flight preparation and conduct of the flight. There was no evidence that he had obtained a weather forecast, considered the need for extra fuel, or submitted the appropriate flight notification and he had exceeded the maximum duty period permitted by the Civil Aviation Safety Authority (CASA) under Civil Aviation Order 48. Also, the flight was not operated in accordance with required procedures for VFR flights conducted at night, with respect to contingencies for runway lighting and provision for flight to an alternate aerodrome. The investigation concluded that these factors suggested that the pilot had probably not identified, or fully considered, the hazards associated with the flight. A number of physiological factors such as fatigue, dehydration, and a lack of recent nutrition could also have affected his performance. The pilot was probably experiencing self-imposed pressure to conduct the flight.

The fuel starvation of the engines was probably the result of inadequate techniques used by the pilot to monitor and manage the consumption of fuel from the aircraft's fuel tanks. This had resulted in a low quantity of fuel in the main fuel tanks at the time the engines failed. The investigation could not determine the sequence of events that led to the low quantity of fuel in the main tanks. It was possible that the pilot had inadvertently omitted to use the auxiliary tanks, had used the auxiliary tanks for an unusually short period of time, or made some other type of error with the tank selections during the flight. Regardless of what fuel tank selections were made during the flight, the pilot had probably not detected the critically low quantity of fuel in the main tanks towards the end of the flight. The investigation could not find any evidence that the pilot had used structured techniques to monitor the quantity of fuel consumed from the aircraft's tanks during the flight. This could have affected his ability to successfully detect and resolve abnormal indications from the aircraft's fuel gauges.

The pilot experienced a difficult set of circumstances in which to respond to the initial and subsequent engine failure. Those circumstances included a lack of significant external visual reference due to the dark night conditions, the limited height available at circuit altitude and the pilot's skill level in handling emergency situations in multi-engine aircraft. He did not maintain control of the aircraft following the engine failures.

The pilot held a commercial pilot (aeroplane) licence and was rated to fly single-engine aircraft at night under the VFR. He did not hold a valid rating to fly multi-engine aircraft at night, although he probably thought that he had been issued with such a rating following a flight test conducted by the ASU chief pilot. However, the chief pilot was not authorised by CASA to conduct flight tests to issue night VFR ratings. The investigation could not find any objective evidence to indicate that the occurrence pilot had received recent training to control a multi-engine aircraft solely by reference to the aircraft flight instruments following a simulated engine failure, or that this ability had been tested prior to, or after the issue of, the (invalid) multi-engine night VFR rating.

Defences and organisational conditions

The investigation concluded that the processes used by the ASU for training in, and supervision of, fuel planning and fuel management were deficient. This probably contributed to the occurrence pilot not using structured procedures and techniques that could have provided him with a greater level of awareness of his fuel situation during the flight.

Deficiencies were also found with the ASU training and checking of night operations. Pilots did not receive recurrent checking of their performance during night operations. The ASU had not fully recognised the risks of remote area night operations and did not have effective defences to manage those risks.

The ASU chief pilot had been provided with minimal training, guidance and professional development to effectively perform his duties. His performance in several safety critical areas was not monitored and resulted in a series of failures in the overall system of safety management at the ASU. Senior management of the WA Police Service assumed that the regulatory relationship between the ASU and CASA provided adequate assurance that the ASU's operations were conducted to an appropriate standard. However, CASA prioritised its surveillance activities, utilising available resources to achieve surveillance targets for operations carrying fare-paying passengers. Organisations holding an aerial work Air Operator's Certificate (AOC), such as the ASU, were allocated a lower priority when planning surveillance tasks and therefore CASA had not performed any significant assessment of the ASU's fixed-wing operation during recent years.

A number of the ASU's safety defences exceeded minimum regulatory requirements. However, the overall safety management system did not have the capacity to ensure the safety of operations in the wide range of circumstances that could reasonably be anticipated. Insufficient management processes existed to ensure that adequate defences were in place at the operational level to provide an assurance of flight safety.

The WA Police Service provided limited guidance for the ASU to develop safety management processes. The ASU management was expected to develop such processes, and a heavy emphasis was placed on the ASU chief pilot to ensure the safety of flight operations. Although he was a key person within the organisation with defined legal responsibilities, he had not been adequately prepared for this role, and the WA Police Service had no procedures to ensure that the chief pilot was supervising operations to an appropriate safety standard. Many of the deficiencies detected with the ASU's system of safety management had existed for many years, but the WA Police Service did not have a system to identify safety deficiencies in operational areas.

As a result of this accident, the ASU implemented a number of changes to the conduct of its operations. These included: the introduction of a new operations manual; a new training and checking manual; revised procedures for management of fuel by the ASU's pilots; appointment of a safety manager within the ASU; implementation of a hazard identification and communication program; and introduction of procedures to supervise remotely-based pilots. The WA Police Service also formally recognised the chief pilot position in the organisational structure of the service and implemented a reform process to improve pilot and crew selections, training, flight risk management, fatigue management, professionalism, external crosschecking and validation of the ASU systems against industry best practice.

Other issues

At the time of the accident, the relevant aviation regulations permitted flight at night under the VFR at times when pilots may have had insufficient external visual reference to control the aircraft using external visual cues. Under such conditions, the pilot would have been required to control the aircraft using the flight instruments. However, the training and currency requirements for VFR operations at night placed minimal emphasis on flight under such conditions. There was no formal advisory material linked to these requirements to help pilots identify higher risk situations or otherwise encouraging the use of various risk mitigation strategies.

The process used by CASA to approve the appointment of the ASU chief pilot did not detect his (or the operator's) limited knowledge of system safety concepts, nor did it provide any assurance that he understood the extent of his role and responsibilities as chief pilot. That also extended to the manner by which the chief pilot received his CASA approval as a training and checking pilot.

Some of the deficiencies associated with the ASU's procedures and management processes may have been able to be detected during the completion of a CASA periodic inspection. The investigation could not determine why those deficiencies were not detected during earlier periodic inspections, during reviews of documentation associated with checklist completion for the reissue of an AOC, and at other times CASA staff had contact with the ASU.

CASA has recently modified its surveillance planning to ensure that all operators are subject to a recertification audit prior to the reissue of an AOC. CASA is also progressively working on its capacity to identify organisations requiring additional surveillance activity on the basis of risk.

CASA has proposed a number of regulatory changes in the area of General Operating and Flight Rules that relate to fuel planning and fuel management.

While acknowledging the significant safety action underway, the ATSB has issued three additional recommendations concurrently with the release of this report. The recommendations cover: the provisions for the disposition of fuel reserves in fuel tanks to be used during the approach and landing; operational requirements and guidance material for pilots conducting VFR flight in dark night conditions; and required qualifications and/or competencies for chief pilots, with particular reference to management and system safety issues.

1 Australian Western Standard Time is UTC +8 hours.

2 Fuel starvation refers to an event where fuel is not being supplied to the engines, but useable fuel is available in at least one of the aircraft's fuel tanks.

Summary

At about 1930 Western Standard Time on 26 January 2001, a Cessna 310R aircraft, VH-HCP, departed Kiwirrkurra, Western Australia (WA), for Newman. The flight was conducted at night under the visual flight rules (VFR), with one pilot and three passengers on board. The aircraft was operated by the Air Support Unit (ASU) of the WA Police Service and had been used to transport police officers from Newman to Kiwirrkurra earlier that day.

Occurrence summary

Investigation number 200100348
Occurrence date 26/01/2001
Location 3 km E Newman, Aero.
State Western Australia
Report release date 23/10/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 310
Registration VH-HCP
Serial number 310R0849
Sector Piston
Operation type Aerial Work
Departure point Kiwirrkurra, WA
Destination Newman, WA
Damage Destroyed

Bell 206L-3, VH-FFI

Safety Action

The ATSB is undertaking a special study into accidents and incidents resulting from fuel exhaustion and/or starvation. The study is based on accidents resulting from fuel starvation and fuel exhaustion, primarily between 1991 and 2000, but will also consider data back to 1981. The aims of the study are:

  1. to consider accident rates by operation type from 1981 to 2000, and to identify high risk areas;
  2. to identify significant factors underlying the accidents and to compare them with factors identified in earlier research; and
  3. to develop recommendations to reduce the risk and severity of accidents.

The research is expected to be completed and a report published in the second half of 2002.

In relation to the sleep inertia aspects of the investigation, ATSB issued the following Safety Advisory Notices on 15 April 2002:

SAN 20010244

The Australian Transport Safety Bureau alerts all operators in the transport industry, particularly those involved in extended-hours operations, to the possibility of crew members suffering sleep inertia and suggests that operators take steps to mitigate the effects of sleep inertia. The steps should not include subjecting employees to sleep deprivation.

SAN 200100245

The Australian Transport Safety Bureau suggests that the Civil Aviation Safety Authority alert all aviation industry operators to the possibility of sleep inertia impairing performance, particularly that of flight and maintenance crews.

SAN 20020035

The Australian Transport Safety Bureau suggests that the Civil Aviation Safety Authority ensure that operators have strategies in place to mitigate the effects of sleep inertia as part of their fatigue management systems.

The occurrence is one of several that the ATSB believes indicate possible safety deficiencies in aerial work operations, in particular, classification of certain types of passenger-carrying operations. As a result of the ongoing investigation into occurrence BO/200100348 near Newman, WA on 26 January 2001, the ATSB issued the following recommendation on 7 September 2001:

R20010195

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority consider proposing an increase in the operator's classification, and/or the minimum safety standards required, for organisations that transport their own employees and similar personnel (for example contractors, personnel from related organisations, or prisoners, but not fare-paying passengers) on a regular basis. This recommendation applies to all such operations, regardless of the take-off weight of the aircraft involved.

On 1 February 2002, the Civil Aviation Safety Authority (CASA) provided the following response:

"As you are aware, CASA is presently reviewing the standards contained within the existing Civil Aviation Regulations (CARs) and Civil Aviation Orders (CAOs) with regard to the classification of operations. The input and recommendations contained within the Air Safety Recommendation R20010195 will be taken into consideration and addressed as part of this Project.

"The outcome of the review will determine which category employees (and similar personnel such as contractors) are placed and the standards that will apply to their transportation in aircraft."

The ATSB has classified this response as Monitor pending the outcome of the CASA review.

Any safety output resulting from the investigation into occurence BO/200100348 will be published on the ATSB website www.atsb.gov.au.

Significant Factors

  1. The helicopter departed Rockhampton with insufficient fuel to carry out the intended flight, and the pilot was apparently unaware of this until some point during the return flight.
  2. By the time the helicopter arrived at Marlborough, thick fog had formed in the area, preventing a landing at the normal landing site.
  3. The pilot did not attempt to divert from Marlborough to look for a fog-free landing site.
  4. While manoeuvring in preparation for an approach to an alternative landing site, the engine lost power, possibly due to interruption of its fuel supply.
  5. Darkness and thick fog, possibly aggravated by the illuminated "Nightsun", denied the pilot visual reference with the ground.
  6. The investigation was unable to determine why the pilot was unable to carry out a safe landing following the loss of engine power.

Analysis

Pilot aspects

The helicopter departed Rockhampton with 500 lb of fuel. This was insufficient to enable it to fly to Yarandoo and return to Rockhampton, which was the pilot's original intention. Whether the pilot miscalculated his fuel requirements or did not consider them at all, could not be established. It was clear by his decision to divert to Marlborough that he became aware of his fuel state during the return flight. His radio transmission to CAPCOM at 0126 reporting his estimate for Rockhampton as 0210 (by which time the helicopter would have exhausted all its fuel) suggested that he was unaware of his inadequate fuel state at that time. He would most probably have become aware of the deficiency when the warning light indicating 45 minutes of fuel remaining, illuminated shortly thereafter.

The pilot might have been unaware of the amended area forecasts including fog, but if he was aware, he may not have considered fog to be a problem, as he intended to return to Rockhampton. However, he may have become concerned after deciding to divert to Marlborough.

A total of 19 minutes elapsed between the helicopter's initial arrival over Marlborough and the accident. During that time, the pilot made three attempts to position the helicopter for an approach to the sports field and one attempt to position for an approach to the road intersection. There is no evidence to indicate whether the pilot had considered leaving Marlborough to seek a fog-free landing site.

Although the pilot did not fly on a full-time basis, he had successfully undergone a flight review 9 days before the accident. In the light of the flight review and the short flights since the check, the pilot's knowledge of all procedures should have been current. The reason the pilot did not ensure that the helicopter carried sufficient fuel for the intended flight, could not be determined.

Any possible effects of medical conditions on the pilot's performance could not be assessed. Aviation medical opinion was that given the presence of advanced ischaemic heart disease, coupled with high levels of stress, the possibility that the pilot suffered an incapacitating medical event before impact could not be ruled out. Similarly, the possibility that the pilot may have had distracting chest pain, even early in the flight, cannot be ruled out. If the pilot had suffered severe chest pain during the attempt to land at Marlborough, he might have attempted an immediate landing and lost control of the aircraft.

If the pilot had been asleep at the time of the CAPCOM call, he would need to have woken, dressed, proceeded to the CHRS hangar, prepared for departure and departed, all in a 14 minute period. Although it cannot be confirmed, the pilot might have been affected by sleep inertia during the pre-departure period and the early stage of the flight. If the pilot had been affected by sleep inertia or had been suffering any chest pain during the pre-departure period, his ability to prepare for the flight might have been degraded. However, if sleep inertia had been present, the pilot would probably have recovered from its effects during the outbound sector of the flight.

If a lipid analysis of the pilot's blood had been completed in 1997 and its results provided to CASA, it is likely that the pilot would have been required to undergo a cardiovascular risk assessment. Due to the inconclusive finding from the autopsy and the absence of recent medical evidence, the investigation was unable to determine if the pilot's medical condition contributed to the accident.

Fuel

Fuel consumption calculations indicate that the helicopter had 125 lb of fuel remaining on arrival overhead Marlborough. Of this, 116 lb of fuel would have been useable. At the endurance consumption rate of 230 lb/h, 116 lb of fuel would have enabled 30 minutes flying.

Assuming that the pilot flew the helicopter for endurance during the 19-minute period between arrival over Marlborough at 0144 and the accident at 0203, the aircraft would have consumed 73 lb of fuel. This would have left a useable fuel load of 43 lb at the time of impact, permitting a theoretical 11 minutes of further flying.

Approximately 22.5 L of fuel (40 lb total, 31 lb useable), sufficient for 8 minutes flying, was drained from the wreckage and there was no evidence of fuel spillage or fire. To be useable, all this fuel would have had to be contained in the rear tank. However, the fuel was removed from all three tanks and the interconnecting fuel lines. If fuel in the forward tanks had not transferred to the rear tank, the remaining flight time would have been less than 8 minutes.

Advice from experienced helicopter pilots was that, in order to obtain an unobstructed view of a landing area ahead and below, a pilot seated in the right-side pilot seat could place a helicopter in an uncoordinated nose-left, right-banked flight attitude. In an attempt to obtain the best view that he could of his potential landing site, the pilot might have placed the helicopter into uncoordinated flight. Alternatively, while manoeuvring the helicopter, he might have inadvertently placed it into an uncoordinated turn. With the low fuel level remaining in the rear tank, an uncoordinated flight condition might have unported the fuel outlets at the bottom of the rear tank. That could have led to air being drawn into the fuel line that supplied the engine, causing the engine to lose power. The pilot would then have been faced with conducting an approach in autorotation in adverse conditions.

"Nightsun"

In thick fog and darkness, it is unlikely that the pilot would have been able to execute a safe approach in autorotation and a safe landing. If the "Nightsun" had been illuminated during the autorotation, as one witness suggested, the visibility problems would have been aggravated due to the light reflected from the fog droplets leading to virtual "whiteout" conditions.

Engine

The apparent non-illumination of the ENG OUT warning light following the power loss might have been due to a very short time between loss of engine power and impact. That time might have been insufficient for the gas producer RPM to reduce to the 55% +/- 3% RPM range required to illuminate the warning light.

Factual Information

On 23 July 2000 at 2326 EST, the pilot of a Bell 206L-3 Longranger helicopter was called by the Rockhampton Ambulance Service Communications (CAPCOM) and requested to transport Queensland Ambulance Service (QAS) personnel to a patient located on "Yarandoo", a property approximately 90 NM northwest of Rockhampton. CAPCOM records revealed that the helicopter departed Rockhampton at 2340. The flight was conducted under the night visual flight rules (NVFR).

After arrival at the property, a decision was made to transport the patient (a child) and his mother to the Rockhampton Hospital. On board for the return flight to Rockhampton were the pilot in command, a crewman-paramedic, an intensive-care paramedic, the child and the child's mother. Throughout the flight, the pilot was in radio communication with CAPCOM.

At 0114 hours Eastern Standard Time (EST), the pilot reported departure from Yarandoo and at 0126, passed an estimate for Rockhampton "10 minutes past the hour". At 0132, the pilot reported that "because of a fairly high fuel burn rate", he was going to divert from his present position direct to Marlborough and that he estimated Marlborough in about 10 minutes. He asked that CAPCOM arrange road transport to Rockhampton for the patient, his mother and the intensive-care paramedic. In response, CAPCOM directed a Marlborough-based ambulance vehicle to deploy to the Marlborough state school sports field to meet the helicopter.

Fog had formed at Marlborough before the helicopter arrived. At 0141, the pilot called the officer in charge of the Marlborough-based ambulance vehicle, now deployed to the school sports field, and asked him to switch on all of the vehicle's external flashing lights. The ambulance officer replied that the vehicle's lights were on and that visibility on the ground was "about the length of a football field".

The helicopter arrived overhead the sports field at 0144. The pilot could see the vehicle when the helicopter was directly overhead, but the fog was sufficiently thick to deny the pilot any slant visibility of ground objects. The pilot then switched the "Nightsun" searchlight on, and made two further attempts to initiate an approach to the sports field, without success. At 0154, the pilot asked the ambulance officer to reposition the ambulance vehicle to the northern intersection of the Bruce Highway and Perkins Road, which was illuminated by overhead orange lights. The pilot said that he could see the cross-pattern of lights and that he would use the cross as an approach reference. At 0159, the pilot informed the ambulance officer that he would aim his approach to the centre of the cross-pattern, and asked the ambulance officer to check the road going west from the intersection for aerial cables that could become a hazard during the final approach. A witness reported that throughout that time, the helicopter's "Nightsun" searchlight remained illuminated.

At 0201, the ambulance officer informed the pilot that visibility was about 5 m. The pilot replied, but the reply could not be understood. At 0203 and again one minute later, the ambulance officer called the pilot but received no reply. Around that time, he heard a sound consistent with a ground impact.

At 0206, a Marlborough resident arrived at the intersection and told the ambulance officer that he believed the helicopter had crashed. State Emergency Service volunteers, the Queensland Police Service officer at Marlborough, the ambulance officer and several residents immediately began to search for the accident site. About one hour later, two residents searching in fog with 20 m visibility located the accident site. The helicopter had been destroyed, and all occupants had received fatal injuries.

Wreckage examination

On-site examination of the wreckage revealed that the helicopter had struck the ground in a steep nose-down attitude while in a left bank. After striking the ground, the helicopter had rolled forward and come to rest inverted. The entire forward section of the fuselage back to the rear cabin bulkhead was destroyed in the impact sequence.

During the impact sequence the tail boom, with the tail rotor and tail rotor gearbox still attached, failed and bent downwards relative to the fuselage. The main rotor gearbox and engine had separated from the deck attachment and transmission mounting points but both remained with the wreckage. The main engine-to-transmission drive-shaft coupling had been pulled out at the transmission end. There was no evidence of torque twisting or bending along the shaft. The outer coupling and inner male drive gears showed little evidence of damage. No significant torque twisting was evident at the separation points. The type and degree of damage to the tail rotor blades indicated that their energy state at impact was low. The twist grip throttle control mounted on the pilot's collective pitch lever, was badly bent and had been overwound in the impact sequence, preventing determination of its pre-impact position. Damage to the engine, the main and tail rotor assemblies and drive systems was consistent with the engine delivering little or no power at impact.

The caution/warning panel was removed for laboratory examination. Four warning lights, ROTOR LOW RPM, TRANS CHIP, BATTERY RLY and TRANS OIL TEMP were missing from the panel and were not recovered from the wreckage. Inspection of the filaments of the recovered warning lights indicated that the FUEL LOW and LITTER DOOR OPEN lights were illuminated at impact, the GEN FAIL, L/FUEL PUMP and R/FUEL PUMP lights filament status were inconclusive, and all other light filaments indicated that they were not illuminated at impact.

The FUEL LOW light should illuminate when 50 - 75 lb of useable fuel remains. The ENG OUT warning light should illuminate when the RPM of the gas producer reduces to 55% +/-3%.

The engine was removed from the wreckage and later set up in an engine test cell. In the test, the engine started immediately and accelerated to idle speed normally. After normal heat-soaking, the engine was accelerated normally to 35% torque. The test run was carried out using all the accessories that were fitted to the engine in service before the accident. The test indicated that there was no technical fault in the engine that would have prevented it from producing power before impact.

Damage to all other helicopter systems was consistent with impact damage. The wreckage examination did not reveal any pre-impact technical fault that could have contributed to the accident. The maintenance records for the helicopter showed compliance with all applicable airworthiness directives, and all required maintenance had been carried out.

Fuel system examination

The entire fuel system, including both main and auxiliary fuel cells, remained intact. All fuel lines were clear of obstructions and were intact, apart from one fracture between a bulkhead and the engine; that fracture was assessed as impact damage. There was no evidence of fuel spillage or any fuel smell in the wreckage. The main fuel line to the airframe filter and from the filter to the engine contained very little fuel. The airframe filter contained a small quantity of clean fuel in the bottom of the bowl. The filter was clean with no visible contaminants present.

The main fuel cell was opened for examination and to determine the quantity of fuel remaining. A total of 22.5 L of fuel was drained from the three fuel tanks, revealing a maximum useable fuel load of 17.5 L. There was some green/brown sedimentary growth at the bottom of the main fuel cell and some small clumps of the growth on the cell walls. The growth was confined to the rear fuel tank. There was no evidence of the growth in the fuel lines, filters or remainder of the fuel system. The "finger filter" on the fuel control unit was removed for inspection, and found to be free of any contamination.

A sample of the fuel was taken from the rear tank and sent for specialist analysis, which confirmed that the fuel conformed to the density specifications and was free of water and contaminants.

Pilot

The pilot held a Commercial Pilot Licence (Helicopter) and a Commercial Pilot Licence (Aeroplane) with a Night Visual Flight Rules Rating. He had 3,928 flying hours of which 3,185 were on helicopters, including almost 50 hours on the Bell 206L-3 (Longranger). He was a former military pilot whose military flying experience included 968 hours on Bell 206 (Kiowa) and 2,059 hours on Bell 47 (Sioux) helicopters. As a military pilot, he had held a command instrument rating, but his rating was no longer valid.

The pilot was employed as a relief pilot, working tours of full-time duty with the operator as the need arose. He had completed previous tours of duty in September and October 1997, February 1998, April 1998, October 1998, February 1999 and September 1999, totalling 43 flights. Between tours of duty, he did not fly. Nine days before the accident, while preparing for his current tour of duty, he underwent a flight review with the operator's chief pilot. The flight review included day and night emergency procedures. On the day following the flight review, he flew a short NVFR flight, and on the following day, he flew a short day flight. For the next five days until 0700 on the day of the accident, he had been off duty.

The pilot was not a permanent resident of Rockhampton, having taken up temporary residence there during his tours of duty. He had been living in a house near the operator's hangar since his arrival in Rockhampton on 14 July. He had completed flights on 15, 16, and 17 July and had then been off duty until 23 July when he assumed duty at 0700. During that day he remained on standby at the house of which he was the sole occupant. He was reported to have spent the day quietly and to have retired to bed early in the evening.

The pilot assumed the standby duty from the operator's senior pilot at 0700 on 23 July. The senior pilot reported that he informed the pilot, amongst other things, that the helicopter was fully serviceable and that it had 500 lb of fuel on board. The senior pilot reported that he then offered to brief the pilot on any aspect of aircraft systems, but the pilot replied that he had covered the operation of the Global Positioning System and the "Shadin" electronic fuel management system in discussions with the chief pilot, and that he was satisfied with his understanding. The senior pilot also showed the pilot the weather forecast covering the previous night and warned the pilot to expect fog during his shift.

The pilot had undergone an annual medical examination on 8 June 2000, and was assessed as medically fit to Class 1 standard, with a requirement to wear prescription spectacles for vision correction. However, he had been required to provide a blood lipid analysis for his 1997 medical renewal. There was no evidence that this analysis was completed at the required time, but the pilot's designated aviation medical examiner (DAME) had written a letter to the Civil Aviation Safety Authority (CASA) dated 19 May 1997, stating that the pilot's lipids had been analysed in 1995 and were found to be normal, but provided no figures to substantiate the finding.

Post mortem histology indicated that the pilot had severe calcific artherosclerosis (otherwise called coronary artery disease) with a maximum narrowing, although difficult to assess, estimated to be at least 50%. The post mortem also found a "localised area of scarring and myofibre hypertrophy, consistent with ischaemia". The histology indicated coronary vessel disease (narrowing of the arteries causing a degree of blockage) of long standing. The changes were indicative of long-term effects (progressing over many years) of nutrient starvation to focal areas of the heart muscle, caused by significant narrowing of the critical coronary vessels responsible for supplying oxygenated blood to those areas.

The pilot had previously rejected flights that he considered involved unjustified risk. These decisions had given the operator's chief pilot confidence in the pilot's judgement, and were key factors in the operator's decision to employ him.

Weather

The Bureau of Meteorology issued an amended area forecast for Area 44 at 1852 on 23 July. The amended forecast covered the period from 230900 Universal Co-ordinated Time (UTC) (231900 EST) to 232300 UTC (240900 EST) and included isolated smoke areas with scattered fog patches along the coast and ranges from 1400 UTC (midnight EST) to 2200 UTC (240800 EST). The Bureau issued a second amended forecast for Area 44 at 2147. That forecast covered the period from 231130 UTC (232130 EST) to 232300 UTC (240900 EST) and included isolated smoke areas and isolated fog patches, tending scattered along the coast and ranges from 1500 UTC (240100 EST) to 2130 UTC (240730 EST). (Area 44 is bounded approximately by the coastal areas from just south of Rockhampton to just north of Townsville, inland to Emerald in the south, thence north-west along a line approximately parallel to the coast and about 250 km inland.)

By the time the helicopter arrived at Marlborough, extensive areas of fog had formed. The ambulance officer at Marlborough estimated the horizontal visibility in the fog from "the length of a football field" at the school sports ground initially, down to 5 m at the intersection of the Bruce Highway and Perkins Road by the time of the accident.

The Bureau of Meteorology reported that the temperature profiles obtained on the day before and on the day after the accident, plus a pilot report at 2100 UTC (0700 EST), indicated that the top of some fog patches could have been up to 2,000 ft above mean seal level (AMSL). The altitude of the top of the fog over Marlborough at the time of the accident was not determined but observation of fog patches in the area on the day after the accident indicated that the top of the fog was about 300 ft above ground level (AGL). Above the top of the fog, there was little or no cloud. [Marlborough is 80 m (approximately 260 ft) AMSL.]

Whether the pilot was aware of the amended area forecasts could not be established.

Fuel management

In addition to the standard fuel management system, the helicopter had been fitted with a "Shadin" electronic fuel management system. The system provided information to the pilot, such as flight time remaining, fuel used and fuel remaining in addition to fuel flow. According to its manufacturer, the system had an accuracy of +/- 2% or better. The pilot received information through a two-window instrument and a flashing warning light placarded CAUTION - ABOUT TO USE RESERVE FUEL. The warning light was programmable to illuminate at a given flight-time remaining, and had been programmed to illuminate when the usable fuel remaining was sufficient to sustain 45 minutes of flight at the prevailing fuel flow.

The operator's procedure was to leave the helicopter on standby with 500 lb of fuel, approximately two-thirds of a full fuel load, in the tanks. When the operator received a task, the pilot would calculate the required fuel load and the maximum fuel load the aircraft could carry given the configuration and payload for the task.

Section B2 of the company Operations Manual, para. 904, "Fuel Management" stated that "Fuel consumption planning is to be based on a minimum of 250 pounds per hour [lb/h] [Long Ranger] and 180 pounds per hour [lb/h] [Jet Ranger] regardless of weight, altitude and temperature. This figure may be adjusted in flight after completion of a fuel flow check to confirm actual consumption." For planning purposes, the operator used a fuel consumption of 250 lb/h when flying for range below 5,000 ft with the "Nightsun" fitted, and 230 lb/h when flying for endurance.

The helicopter's last flight before the day of the accident took place on 22 July; two days previously. After that flight, the helicopter was refuelled to 500 lb in accordance with the operator's normal procedure. The operator confirmed that the most recent fuel delivery to the operator also took place 2 days before the accident, after the last 500 lb refuelling. The operator's underground fuel tanks plus six jerrycans kept in the hangar, were full indicating that no additional fuel above the standby load of 500 lb had been added to the helicopter's tanks before its departure on the accident task.

The helicopter departed Rockhampton at about 2340 EST and the pilot reported on final approach for Yarandoo at 0039, approximately 1 hour after departure. During the flight the helicopter would have consumed approximately 250 lb of fuel. The pilot reported departure from Yarandoo bound for Rockhampton at 0114, updated his estimate for Rockhampton at 0126, and reported his decision to divert to Marlborough at 0132. The helicopter arrived overhead Marlborough at 0144, after a 30 minute sector and subsequently calculated to have consumed approximately a further 125 lb of fuel. Thus about 375 lb of fuel would have been consumed after departure from Rockhampton, leaving approximately 125 lb of fuel remaining on arrival at Marlborough.

By the time the pilot reported his intention to divert to Marlborough, the helicopter had flown for 78 minutes, representing a fuel consumption of about 325 lb. At that time, approximately 175 lb of fuel would have remained, representing 42 minutes of flight time available. It is likely that the flashing light in the "Shadin" fuel management system, which was set to illuminate when 45 minutes of fuel remained, had illuminated some minutes earlier, and that the pilot had used the intervening period to decide to divert, to determine his new destination, and in consultation with the paramedics, to determine the further ambulance services required for the patient.

The flight to Yarandoo and return to Rockhampton would have required about 120 minutes of flight time, consuming 500 lb of fuel. The company's operating procedures specified a fuel reserve of 30 minutes for night operations, so the task required a minimum fuel load of 625 lb. Configured for the task, the helicopter could have been loaded with up to 675 lb of fuel to depart Rockhampton at maximum gross weight.

Queensland Ambulance Service (QAS) tasking

Chapter 31 of the Queensland Ambulance Service Operations Manual "Aeromedical Operations" detailed all procedures for the operation of aeromedical services and the persons or agencies responsible for each step.

Paragraph 3150 of that chapter "Activation Process" detailed each step between receipt of a request for QAS assistance and completion of a flight followed by local area transfer of a patient to a medical facility. The District Communications Centre (DCC) (in this case CAPCOM) normally received the request and, generally in consultation with the clinical co-ordinator (a designated medical officer who determines the medical resource requirements for the task), would activate the aircraft and crew. On this occasion, a medical consultation was not obtained. However in retrospect, medical officers stated that they agreed with the decision to task the helicopter. Sub-para. (d) of para. 3150 stated:

"The District Communications Centre will then consult the pilot or service provider to establish the feasibility of the flight, i.e. weather, aircraft suitability, etc."

The decision to fly is made by the pilot. In discussion, DCC staff emphasised that they never questioned a pilot's decision not to fly. Further, it was normal practice in Rockhampton that when considering an aero-medical operation, DCC staff did not inform a pilot of the details of a task, thus avoiding any undue pressure on the pilot to fly. On this occasion, normal procedure was followed and the pilot accepted the task.

Classification of operations

At the time of the accident, CASA classified aircraft operations in accordance with the type of flight being conducted. Operators that carry fare-paying passengers (regular public transport and charter) are required to meet higher regulatory standards and receive a higher level of surveillance from CASA than other types of operators. Emergency Medical Service Operations, and Search-and-Rescue operations are classed as "aerial work" operations.

CASA has undertaken a project on Classification of Operations Policy. Civil Aviation Safety Regulation (CASR) 133, entitled "Air transport and aerial work operations (rotorcraft)" has been included within the project. Among other matters, the project is considering:

  1. aircraft certification requirements and crew (including supernumery crew) training requirements for aerial work operations;
  2. introducing performance requirements for helicopters in line with similar requirements for aeroplanes;
  3. introducing rules specific to certain types of aerial work operations;
  4. re-introducing minimum fuel requirements; and
  5. the issue of "persons directly involved" (including patients whose travel has been requested by a medical officer and an escort, usually a member of the patient's immediate family) travelling on aerial work flights.

CASR 133 is expected to be available from October 2002.

Sleep inertia

Sleep inertia refers to a feeling of disorientation, mental dullness or sluggishness that occurs after awakening from a period of sleep. In broad terms, sleep inertia may affect mood, memory, attention, concentration, cognitive processing, performance accuracy and reaction time. It is a recognised state of transition from sleep to wakefulness.

A variety of factors can influence the effect of sleep inertia on performance. When awakening from sleep normally, the effect of sleep inertia is believed to last for less than 5 minutes. When abruptly awoken, the effects have been identified as typically lasting up to 30 minutes, with some research indicating that performance can be impaired for over 1 hour.

Occurrence summary

Investigation number 200003130
Occurrence date 24/07/2000
Location 1 km NW Marlborough (Kenela Park)
State Queensland
Report release date 16/05/2002
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Bell Helicopter Co
Model 206
Registration VH-FFI
Serial number 51367
Sector Helicopter
Operation type Aerial Work
Departure point Yarandoo Station, QLD
Destination Marlborough, QLD
Damage Destroyed

Cessna 402C, VH-NMQ

Safety Action

Several safety deficiencies were identified during the initial phase of the investigation. Local safety action was agreed to and addressed by the operator prior to publication of the final report. Those safety actions were as follows:

Issue of company Maintenance Alert MA/C400/2, which required a detailed inspection and functional check of the fuel selector system of all the operator's Cessna 402C aircraft.

A second Alert MA/C400/2 amendment 1, was issued a short time later after the initial fleet inspection found that the fuel selector valves for a second aircraft were out of synchronisation with the selector indicator. This alert detailed further inspection and rectification instructions.

The operator has undertaken to re-examine the company operations manual with a view to improving the guidance information on fuel planning and reserves.

The operator has agreed to re-examine the need for the cross-feed and shut-off checks. If they are considered necessary, then a procedure to ensure that the desired outcome is achieved will be devised and introduced.

The operator's maintenance controller has introduced procedures to ensure that all trip records are now vetted daily. Any endorsement item considered to have the potential to affect the safety of flight will now be subject to immediate maintenance rectification.

The operator has amended and amplified the incident and accident reporting section of the company Policy and Procedures Manual to better reflect the correct reporting procedures.

The Operator has introduced the Daniel System Australia, Integrated Aviation Software (IAS) in the company's electronic maintenance control system. This software has the ability to monitor and identify repetitive defects. The company Maintenance Control manual Vol 1, section 9 has been changed to reflect the changed procedures.

Analysis

The fuel selector system defect need not have led to a situation in which the safety of the flight was not assured.

The problem was recognised by the pilot early in the flight, and, despite attempts to resolve it, was confirmed when about mid-way. Consequently, without fuel from the right tank, there was insufficient fuel available for the planned flight fuel requirement, let alone the required reserve fuel. The pilot considered that a landing at an alternate aerodrome may have been necessary. However, the need to maintain adequate reserve fuel to ensure safety of the flight was apparently not recognised. As the flight progressed, the quantity of fuel required was assessed only in the context of a direct approach and landing at Darwin.

After landing, the fuel gauge indicated that the left tank contained about 20 lb of unusable fuel. The pilot had therefore made the decision to overfly an alternate aerodrome when in reality, only about 20 lb (or about 6 minutes) of fuel was available.

Maintenance oversight of the aircraft was inadequate. This is evidenced by:

  • the number of reported occurrences of fuel system problems; and
  • the deferral of rectification of 3 such problems because they were regarded as "not major defect".

The repetition of reports and the request entered on the maintenance release to "please report further", suggest that the focus of maintenance rectification action was deficient.

The late reporting of the occurrence to the ATSB and to the operator's maintenance controller arose through breakdowns in the operator's reporting procedures following staff changes.

Summary

History of the flight

The pilot of a Cessna 402C aircraft, VH-NMQ, was conducting a scheduled passenger service from Tindal to Darwin, with 4 passengers.

During the climb to the planned cruise altitude of 8,000 ft, the fuel quantity gauges indicated that fuel was being consumed from the left tank only. At the top of climb, the fuel gauges indicated 100 lb in the left tank and 200 lb in the right tank. Once established in the cruise the pilot tried to balance the fuel load by positioning the left fuel selector to allow the left engine to be supplied with fuel from the right tank.

Approaching the midway point between Tindal and Darwin, the fuel gauges confirmed that the imbalance remained. The pilot assessed that sufficient fuel was available to continue to Darwin. As the flight approached the last suitable alternate aerodrome, the pilot calculated that 13 lb of fuel was needed to reach Darwin from that point, based on the current consumption rate. The left fuel tank gauge showed 40-lb remaining.

The pilot requested and was given a direct approach to runway 29. During the landing roll the left engine stopped, and the right engine stopped soon after the aircraft cleared the runway. The fuel quantity gauges showed 20 lb for the left tank and 200 lb for the right tank.

The operator's ground support staff then towed the aircraft to the terminal area where the passengers disembarked normally.

The aircraft had flown from Darwin for Tindal the previous day with 650 lb of fuel on board. The pilot's navigation log showed that 365 lb was required for the flight from Tindal to Darwin. This comprised 230 lb flight fuel (59 minutes), 100 lb fixed reserve (30 minutes), 25 lb variable reserve fuel, and 10 lb taxi fuel. The navigation log also showed the total fuel on-board at Tindal before departure for Darwin was 385 lb. The pilot reported that before departure from Tindal, the aircraft fuel quantity gauges showed 185 lb in the left tank and 200 lb in the right. The pre-flight check of the fuel cross-feed was normal.

A landing at an alternate aerodrome was not considered necessary, as the pilot had calculated sufficient fuel was available to continue to Darwin, and was conscious of the operating schedule for the aircraft. However, company management stated that there was no instruction or pressure on pilots in this regard.

The pilot held a current commercial pilot licence, a command multi-engine instrument rating a valid medical certificate, and had logged 2,454 hours aeronautical experience. This included 150 hours on Cessna 402C aircraft. The pilot's last proficiency check was on 8 March 2000.

On the day of the occurrence, 5 May 2000, the pilot did submit an incident report to the operator. However, due to a breakdown in the operator's reporting procedures following staff changes, the ATSB was not notified of the occurrence until 15 May. As a result, it was unable to conduct an examination of the fuel selector system fitted to NMQ before the aircraft was returned to service.

Background

The then Civil Aviation Authority of Australia issued Civil Aviation Advisory Publication No: 234-1 (0) in March 1991. It provided advice about the quantity of fixed reserve fuel to be carried, and noted the use of fixed reserve fuel was limited to unplanned manoeuvring in the vicinity of the destination aerodrome. It further noted that fixed reserve fuel would normally be retained in the aircraft until the final landing.

The operator's fuel policy stated that in all foreseeable circumstances an aircraft should complete a flight with at least the fixed reserve fuel intact. The standard fixed reserve for the operator's Cessna 402C fleet was 100 lb of fuel for 30 minutes of flight.

Cessna 402C Fuel Selector System

The two fuel selector controls are attached to the cabin floor between the pilot and co-pilot seats. The selectors enable the fuel selector valves, located behind the engine firewalls, to be positioned to the corresponding tank, crossfeed, or off. The arrow-shaped ends of the selector control handle points to the position on the selector placard that corresponds to the control valve position. Each handle connects directly to a gearbox located under the floor. Cables connect each gearbox to their respective fuel selector valve.

An inspection by the maintenance provider in Darwin confirmed that the pilot had positioned the right fuel selector handle to the right tank. However, the cable connecting the gearbox to the fuel selector valve did not position the valve to the right tank.

The right fuel selector gearbox was removed, the selector gearing adjusted and the selector cable re-rigged. The aircraft was returned to service after the fuel selector system was ground tested.

The Pilot's Operating Handbook for the aircraft contained a description of the fuel system and it's operation. In the Normal Procedures section of the handbook, pilots were cautioned that they should "Feel for (the) detent" when placing the fuel selector at the desired position.

Maintenance action

The operator's maintenance controller was located at Alice Springs. A sub-contract maintenance provider conducted maintenance at Darwin. The operator's maintenance controller was not advised of the occurrence until 23 May, and was therefore unable to specify extra inspection procedures for the operator's Cessna 402C fleet until that time. The maintenance controller issued maintenance alert MA/C400/2 on 25 May. It was applicable to all Cessna 402C aircraft used by the operator and its associate company, and required a detailed inspection of the fuel selector system. These checks were to be conducted at each scheduled inspection until the requirements were included in the operator's System of Maintenance.

During one such check of the fuel selector system on another of the company aircraft, VH-TZH, the screws securing the selector cable lever arm/travel stop to the sector gear were found to be loose. This allowed the travel stop to slide under the base-plate and the sector gear to move beyond the end of its travel, resulting in loss of synchronisation between the selector handle and the selector valve.

The operator immediately issued an amendment to maintenance alert MA/C400/2 that included photographs of the defective fuel selector on TZH. The alert specified that the selector gearbox was to be checked if the fuel selector valve was found not synchronised with the selector indicator. During the investigation the fuel selectors of two other of the operator's Cessna 402C aircraft were found to lack an effective detent.

At the time of the occurrence, the maintenance release for NMQ contained an annotation arising from a previous report of uneven fuel consumption from the left tank. Examination of the fuel system related maintenance documentation for the aircraft revealed 17 events since December 1999. Seven involved reports of the aircraft using more fuel from the left tank than the right when the fuel selectors were correctly positioned. There was one report of greater fuel usage from the right tank. The rectification section for four of the entries stated that the fuel selector system was re-rigged. The reported defect for three of the entries was annotated "not major defect" and transferred to the deferred defects list. The fuel related defect entry for the 18 April 2000 stated "fuel not feeding correctly. Fuel noted to be crossfeeding some fuel in level flight - report further".

The last reference to fuel transfer problems, prior to the incident, was on 20 April. The endorsement on the trip record stated "both engines draw fuel from the left tank only". The rectification section of the record noted the fuel selector valve was removed, lubricated, refitted and pressure tested. The selector cable was re-rigged, and the system operated satisfactorily during ground testing.

Fuel system pre-flight checks

The fuel system pre-flight checks specified in the operator's Cessna 402C Operations Manual differed from the procedures specified in the manufacturer's Pilot's Operating Handbook.

The operator's standard operating procedures required pilots to operate the fuel supply cross feed for 60 seconds to verify normal operation. Also, pilots were to ensure normal operation of the fuel valves by positioning the fuel selectors to the off position to observe a decrease in fuel flow. Following these checks, pilots were to position the fuel selectors to the main tanks.

The manufacturer's Pilot's Operating Handbook did not specify checks for crossfeed operation or positioning the fuel selectors to the off position to observe a decrease in fuel flow.

The pilot did not move the fuel selectors to the off position as part of the pre-flight checks. This was because the Fleet Manager had advised his intention to amend the pre-flight check to delete the requirement. The pilot reported awareness of the need to feel for the detent when moving the fuel selectors, and was confident the detent was achieved during the pre-flight check.

On 16 May the operator issued a memo on the occurrence to its Cessna 402 pilots, and included new instructions for pre-flight operation of the fuel selector. The memo cancelled the previous requirement for pilots to position the fuel selectors to the off position to confirm a decrease in fuel flow.

Occurrence summary

Investigation number 200001827
Occurrence date 05/05/2000
Location Darwin, Aero.
State Northern Territory
Report release date 23/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Cessna Aircraft Company
Model 402
Registration VH-NMQ
Serial number 402C0451
Sector Piston
Operation type Air Transport Low Capacity
Departure point Tindal, NT
Destination Darwin, NT
Damage Nil

Beech Aircraft Corp D55, VH-ILM

Safety Action

Local Safety Action

As a consequence of this and other accidents where the integrity of the occupant restraint system has not met design specifications, the Civil Aviation Safety Authority has informed the Australian Transport Safety Bureau that it is developing educational material for the aviation industry about the adequacy of maintenance to safety harness attachments. The information would also emphasise the responsibilities of aircraft owners, maintenance personnel and pilots, in providing the designed level of protection to aircraft occupants.

Significant Factors

1. The pilot was not adequately prepared to fly the assigned instrument approach in IMC.

2. The pilot did not change the fuel tank selection when fuel from the auxiliary tanks was exhausted.

3. The pilot's shoulder harness upper attachment was not correctly installed.

Analysis

The circumstances of this accident were consistent with the pilot not being adequately prepared for an instrument approach in IMC. The pilot did not meet recency requirements for an NDB approach and was not qualified to make a GPS instrument approach. IFR pilots are required to consider their instrument flight currency before attempting flight in IMC. The amended Bankstown forecast obtained by the pilot at Warren should have alerted him to the possibility of an approach in IMC. The proximity of controlled airspace did not provide the pilot with the option of flying a cloud break procedure from a radar vector as intended. Subsequently, the pilot's decision not to divert when advised by the controller to expect an NDB approach led to the distraction from his normal flying duties and forgetting to select the main fuel tanks for the approach and landing.

The abrupt track change and subsequent excessive rate of descent at 17 NM from Sydney, as recorded by radar, was consistent with the pilot attempting to descend below the cloud base through a break in the cloud. Such a manoeuvre, below the minimum safe altitude, posed a significant risk of collision with obstructions or the ground.

The pilot's upper body restraint attachment failed due to an incorrect and weak installation. The investigation was unable to determine the circumstances of this installation but it was likely that it had remained undetected by maintenance personnel for a considerable period of time. The incorrect installation was not an obvious defect and maintenance personnel had no means of readily referencing the relevant installation information for comparison.

Summary

History of the flight

The pilot hired a Beechcraft D55 Baron aircraft for travel associated with business commitments and submitted an instrument flight rules (IFR) flight plan from Bankstown to Warren and return. The flight to Warren proceeded normally. The pilot obtained an amended forecast before the return flight. The forecast indicated instrument meteorological conditions (IMC) for his arrival. Accordingly, he replanned via Bathurst in anticipation of an instrument arrival procedure to Bankstown.

The pilot departed Warren at 1628 ESuT and at 1705 reported 20 NM north west of Bathurst at 9,000 ft. That placed the aircraft inside controlled airspace without a clearance. The pilot was subsequently issued a clearance along the planned track. Approaching Bankstown the pilot encountered IMC and requested a Bankstown Radar Two arrival, anticipating a cloud break procedure from a radar vector. However, due to the missed approach flight path of that procedure conflicting with Sydney airspace requirements, the Sydney departures (west) controller, after determining that the pilot did not want the GPS approach, advised the pilot to expect a clearance for the Runway 11C Radar/Bankstown NDB/Sydney DME instrument approach. The pilot acknowledged the instruction. The approach controller subsequently observed the aircraft on radar to the right of the assigned approach track. He advised the pilot that he was right of track and cleared him to leave controlled airspace tracking to Bankstown along that procedure.

The pilot contacted Bankstown tower and advised that he was flying the Bankstown Runway 11C Global Positioning System (GPS) approach. The tower controller, who had been expecting the aircraft to be on a Runway 11C Radar/Bankstown NDB/Sydney DME approach, queried the pilot as to which approach he was using. The pilot confirmed that he was flying the GPS approach.

Recorded radar data showed that the aircraft had closely tracked the Runway 11C GPS approach path to a point 17 NM from Sydney, heading about 120 degrees at 2,500 ft. The aircraft then turned left to a heading of about 065 degrees and descended to 600 ft. The descent rate during that period was between 2,200 and 3,400 ft per minute. The aircraft then turned right to about 240 degrees and climbed to 1,100 ft. The minimum altitude for that segment of the approach profile was 1,400 ft. The Sydney departures (west) controller observed the aircraft on radar and advised the Bankstown tower controller. A short time later, the tower controller heard the transmission 'India Lima Mike emergency emergency'. Subsequent transmissions from the tower controller to the pilot went unanswered.

A witness, located approximately 2.5 km east of the accident site, reported seeing an aircraft pass overhead on a westerly heading with its engines surging before stopping. Other witnesses saw an aircraft apparently attempting to land in a nearby field. They described its approach as steep and slow. The aircraft descended into a grass-covered gully and impacted the ground. The impact collapsed the extended landing gear and the aircraft, although otherwise intact, was substantially damaged. The pilot, who was the sole occupant, received severe head and facial injuries.

Witnesses described weather conditions at the time of the accident as overcast with light rain falling and visibility estimated to have been between 3 and 5 km.

The pilot later stated that he had not previously flown a Runway 11C Radar/Bankstown NDB/Sydney DME instrument approach. Although he had acknowledged the controller's instructions for the approach to Bankstown, his intention had been to descend to the lowest safe altitude (LSALT) on that track and, if not in visual contact with the ground, to climb and divert to Bathurst. He reported that when he was not visual at 600 ft he commenced a climbing right turn onto a reciprocal track with the intention of diverting.

The pilot reported that after initiating the climbing turn onto a westerly heading, the left engine failed. He carried out the initial actions for engine failure but did not check the fuel selection at that time. He reported that checking the fuel selection was an item of his memorised trouble checks that in a multi-engine aircraft are performed after the initial actions and prior to feathering and securing the failed engine. However, before commencing the trouble checks the right engine failed and the pilot discontinued any further checks. He broadcast an emergency radio transmission and concentrated on controlling the aircraft. When clear of cloud, he manoeuvred the aircraft to avoid some towers and positioned the aircraft for a landing ahead, clear of houses and power lines.

The pilot later stated that he had intended to change from the auxiliary fuel tanks to the main tanks before commencing the approach. However, anxiety at having to fly an unfamiliar approach in IMC had distracted him and he had forgotten to change tanks. The pilot had not referred to either the approach or landing checklists that each included a check of the fuel tank selection.

Pilot experience, qualifications and recency

The pilot held a Commercial Pilot Licence and a valid Class 2 Medical Certificate. His Command Instrument Rating was endorsed for ILS, LLZ, VOR and NDB approaches. A log book entry on 24 May 1996 certified him as competent to use the GPS for en route navigation only. His total instrument flight time was 129 hours. No instrument flight time was recorded in the 90 days prior to the accident. His instrument rating renewal on 13 April 1999 had included an NDB approach. He had subsequently recorded an NDB approach, in flight, on 13 August 1999 and had made two practice NDB approaches in a ground procedure trainer on 20 September 1999. Recent experience requirements in Civil Aviation Orders Part 40.2.1 specified that the holder of a command instrument rating must not carry out an NDB approach in IMC unless in the preceding 90 days the holder has flown that type of approach either in flight or in a synthetic flight trainer.

At the time of the occurrence the pilot was operating under the privileges of a Command Instrument Rating (Multi-engine). On 10 March 2000 the Civil Aviation Safety Authority promulgated Civil Aviation Order 40.2.3 "Private IFR Rating" that allowed private pilots who had received appropriate training to fly in IMC under conditions less strict than those required for an instrument rating. The Private IFR Rating specified a flight review at intervals of two years. Civil Aviation Advisory Publication 5.13-1(0) Private IFR Rating recommended that recent experience requirements of the command instrument rating be used for guidance as to instrument flight time and instrument approaches.

The pilot had recorded 45.7 hours on the Beechcraft Baron type. His initial Baron endorsement training was undertaken in the B58 model but all his recent time on type was in the D55 model.

Fuel system and management

The D55 Baron fuel system consisted of a separate main and auxiliary tank in each wing. A selector for each fuel system was located on the floor between the front seats. The selector had four positions marked OFF, AUX, MAIN and CROSSFEED. A placard on the fuel selector directed pilots to use the auxiliary tanks in level flight only. The Pilot's Operating Handbook advised pilots to preplan fuel and fuel tank management before the actual flight and to utilize the auxiliary tanks only in level cruise flight. The last item of the descent checklist was "Fuel Selector Valves - MAIN".

Single fuel quantity indicators for both the left and right fuel systems were mounted on the pilot's lower panel. A toggle switch on the electrical sub-panel enabled selection of the quantity indication for either the main or auxiliary tanks.

The later model Beechcraft B58 Baron has a single tank in each wing, simplifying fuel selection and fuel quantity indication.

Wreckage examination

Examination of the wreckage did not reveal any pre existing defect that may have contributed to the accident sequence. There was no fuel in the auxiliary tanks. Approximately 170 litres of Avgas was recovered from the main tanks. The fuel selectors and the fuel quantity gauge switch were selected to the auxiliary tank positions. The wing flaps were not extended.

The aircraft was certified for IFR flight and was equipped with a GPS receiver that met the requirements for conducting GPS non-precision approaches. Documentation found in the wreckage included a set of current approach charts but the investigation was unable to determine which approach chart the pilot had used for the approach.

Shoulder harness attachment

The upper attachment of the pilot's shoulder harness failed during the accident sequence. The harness had no inertia reel and required manual adjustment. The pilot reported that he had been unable to adjust the shoulder harness as firmly as he desired. Examination of the upper attachment found that the installation was not in accordance with the approved modification and the bolt had pulled through the window pillar (see photos Fig. 1 and 2 below). The attachment for the right seat shoulder harness conformed to the approved modification.

Figure 1: Photograph of the failed shoulder harness attachment showing (above) where the bolt had pulled through the pillar.

aair200000893_001.jpg

Figure 2: Photograph of the bolt and harness end fitting.

aair200000893_002.jpg

Attachments for the shoulder harnesses had been installed in January 1973. This was carried out to comply with Airworthiness Directive AD /GENERAL/28 "Safety Belt and Harness Installations" that was issued in May 1972. The AD required an additional, single, shoulder strap to be fitted to the front cockpit seats of all Australian registered aircraft. The aircraft's logbook indicated compliance with the AD in accordance with an approved design drawing.

Figure 3: Cross-section through pilot's window pillar as appeared on the approved modification drawing.

aair200000893_003.jpg

Figure 4: Cross-section through pilot's window depicting the installation as found on VH-ILM.

aair200000893_004.jpg

The investigation was unable to determine how and when this attachment was altered. Maintenance records showed that since modification the aircraft had been resprayed and the pilot's side window panel had been replaced. Either procedure may have required removal and reinstallation of the attachment. The attachment in the aircraft, as depicted in the diagram at Fig. 4, was significantly weaker than the approved method of attachment shown in the diagram at Fig. 3, thereby reducing the protection provided by the design. The fact that it was an incorrect installation may not have been apparent to maintenance personnel. The approved installation drawings were held by the organisation that originally performed the modification and were not readily available for reference by subsequent maintenance personnel.

Maintenance personnel normally referred to the illustrated parts catalogue for identifying correct components and assemblies. That catalogue, produced by the aircraft manufacturer, did not incorporate modifications by other than the aircraft manufacturer. As such, the modification of the shoulder harness installation did not appear in the catalogue. Approved maintenance data, as required under Civil Aviation Regulation CAR 2A, provided guidance as to the information and documentation required to assist licenced aircraft maintenance engineers (LAMEs) to carry out aircraft maintenance, including modifications.

Civil Aviation Regulation 50A entitled "Aircraft Log Book" stated in part;

"…the holder of the Certificate of Registration for an Australian aircraft must:

(a) keep a log book for the aircraft, and
(b) make the log book available, and other documents referred to in the log book, available to CASA and to persons engaged in maintenance on the aircraft…."

Investigation into a fatal floatplane accident at Calabash Bay, NSW on 26 July 1998 (Occurrence 199802830) also found incorrectly fitted seat belt attachments. The report noted that failure of these attachments might have contributed to the severity of injury to the occupants. In both the Calabash Bay accident and this occurrence, aircraft had been found to have been operated with incorrectly attached restraint systems.

Occurrence summary

Investigation number 200000893
Occurrence date 13/03/2000
Location 15 km WNW Bankstown, Aero.
State New South Wales
Report release date 27/09/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer Beech Aircraft Corp
Model 55
Registration VH-ILM
Serial number TE-750
Sector Piston
Operation type Business
Departure point Warren, NSW
Destination Bankstown, NSW
Damage Destroyed