Robinson R22 Beta, VH-LDR

Factual Information

History of Flight

The pilot of a Robinson R22 Beta helicopter, together with a passenger acting as a spotter, was engaged in a mustering operation at a remote cattle station. The spotter reported that while transiting to another paddock, at a height of approximately 200 ft above ground level, the helicopter developed a lateral shudder. The shudder intensified and the pilot rapidly lost control of the helicopter as it shuffled to the right. The helicopter then impacted the ground in a nose down, slight right-bank attitude, with little forward speed. A member of the support ground team nearby heard the impact and went to the scene. The pilot and observer had egressed the helicopter and were found lying on the ground forward of the cockpit. The pilot died while enroute to hospital.

Wreckage examination

The helicopter fuselage was extensively damaged, and the tail boom severed. The fuselage sustained a downward and forward crushing of the right side of the cockpit area, and as a result the pilot received fatal injuries. The main rotor mast assembly separated in flight, damaging the engine firewall and both fuel tanks. Only one main rotor blade remained attached to the main rotor hub. That blade displayed impact damage; the result of striking and severing the tailboom. The other main rotor blade displayed a fracture at the blade root fitting. The matching separated main rotor blade section was discovered 105 metres from the crash site and had incurred minimal impact damage. The location of the blade suggested an in-flight separation. The main rotor mast assembly had failed in overload resulting from the out-of-balance condition experienced following separation of the blade.

The right fuel tank was found 20 metres from the fuselage and had minor impact damage. Approximately one litre of fuel was recovered from the tank. The tank had separated from the helicopter in flight. The tail rotor assembly with the severed tailboom attached was found 34 metres from the accident site. The tail rotor blades, and hub were intact. Both tail rotor blades displayed side compression bending loads. There was evidence of low tail rotor RPM at impact.

Weather

Witnesses reported the weather as unlimited visibility with some scattered cloud cover. Weather was not considered a factor in the circumstances of the accident.

Helicopter history

The helicopter had recorded 2,124.6 hours time in service (TIS). That total flight time was derived from the helicopter hour meter, as the pilot's logbook and helicopter maintenance release were incomplete. The last flight entered in the pilot's logbook was on 2 July 2000, 27 days prior to the accident. The last entry on the helicopter maintenance release was 4 July 2000, at 2,102.4 hours TIS, 25 days before the accident. Those were the hours at the time of release to service following a 100-hour inspection, completed on the same date and TIS. No flight entries had been made from that date until the time of the accident.

Helicopter operations

There was anecdotal evidence from witnesses who were familiar with the operation of the helicopter that suggested it might have been operating more hours than was being documented. A review of company and helicopter records was completed to substantiate helicopter operating hours. That review comprised analysis and comparison of company customer flight time and fuel invoices and helicopter spares usage versus recorded helicopter flight time. That evidence suggested the helicopter operating hours were being under-reported and supported the anecdotal evidence of the witnesses.

Personnel information

The pilot held a Commercial Pilot's Licence (Helicopter), R22 and R44 helicopter endorsements, and a valid class one medical certificate. He had recorded 662.5 hours total time in helicopters as of the last entry in his logbook. Of that total, 660.5 hours were in that type of helicopter. In the 90 days prior to the accident he had logged 95.6 hours flying that specific helicopter. The pilot's last flight review was completed on 9 June 2000. The pilot completed an R22 Helicopter Ground Awareness, Safety Awareness, and Flight Check course on 26 January 1997. He also completed a Low Flying training course on 11 June 1998.

Service life of the main rotor blade

The recorded TIS of the separated main rotor blade part number A016-2, serial number (S/N) 9278B, revision AG, derived from helicopter logbook entries, was 1,995.5 hours. The logbook annotated that the blade had accumulated 1,299.9 hours TIS when installed on 20 May 1998. The mandatory retirement time of the main rotor blade was 2,200 hours TIS. The manufacturer determined the retirement time/service life of the R22 blades using a formula developed from fatigue testing.

Related occurrence

Occurrence 199000089

A Robinson R22 helicopter involved in mustering was transiting from one parking area to a more open area to board a passenger. At an altitude of approximately 300 ft, witnesses heard a sharp crack and all engine and rotor noise ceased. The helicopter descended at a steep angle and impacted the ground. Witnesses removed the occupants before the post crash fire, which consumed the wreckage. Both occupants received fatal injuries. The on-site investigation revealed an in-flight separation of one main rotor blade. Analysis of the failed blade revealed a fatigue crack of the main rotor blade root fitting. It was established that the retirement time of the main rotor blade had been exceeded by a minimum of 257.2 hours. It was believed the hours entered in the helicopter logbook did not reflect the actual operating hours.

Safety action following occurrence 199000089

As a result of the investigation into Occurrence 199000089, a manufacturing anomaly of the R22 main rotor blade was discovered which related to load transfer through the rib root fitting. In April 1991, the Australian Transport Safety Bureau (then known as the Bureau of Air Safety Investigation) issued three recommendations:

1) Recommendation B/905/1021 suggested a review of the retirement time of the blade.

Civil Aviation Authority response to Recommendation B/905/1021:

A review was completed using information based on the true service time of the failed blade. The Civil Aviation Authority (CAA) released Airworthiness Directive AD/R22/31 in June 1990, mandating a 1,000-hour retirement time of the R22 main rotor blades until an acceptable method of inspection of the blade be developed to detect cracks in the rib root fitting. In June 1990, CAA Airworthiness Directive AD/R22/31 amendment 1 was released, increasing the retirement times to 1,500-hours pending the development of the inspection procedures.

2) Recommendation B/905/1021 also suggested that the CAA and the manufacturer develop an inspection technique for the blade to detect progressive fatigue failure of the in the area of the rib root fitting.

Additional Civil Aviation Authority response to Recommendation B/905/1021:

CAA Airworthiness Directive AD/R22/31 amendment 2 was released in March 1991, mandating an eddy current inspection for all blades which had exceeded 1,500 hours service life, with recurring inspection every 200 hours thereafter. That directive did not address blade part numbers and was addressed to all models fitted with main rotor blades up to and including S/N 5493.

3) Recommendation B/905/1021 furthermore suggested that the helicopter manufacturer address the load transfer anomalies.

Robinson Helicopter Company response to Recommendation B/905/1021:

The manufacturer reviewed their procedures and made process specification revisions to eliminate those anomalies.

The accident main rotor blade (S/N 9278B) had not been eddy current inspected, as the directive was not applicable by serial number. The procedural changes and process specification revisions implemented by the manufacturer eliminated the requirement for the eddy current inspection.

Analysis

The failure mode in the main rotor blade was identical to the failure mode documented in Occurrence 199000089 (in excess of 2,200 hours TIS), and on manufacturer tested-to-failure blades (in excess of 2,200 hours TIS). The under-reporting of helicopter flight time probably resulted in an actual service life of the failed main rotor blade in excess of the manufacturers stated limits. There has been a history of main rotor blade failures of the R22 main rotor blade during its evolution. Those events have led to a series of modifications to address the anomalies discovered. Exceeding the service life of a dynamic component such as a main rotor blade will exacerbate the possibility of undetected catastrophic component failure.

Significant Factors

The main rotor blade incurred a fatigue-related in-flight separation failure.

Summary

The pilot of a Robinson R22 Beta helicopter, together with a passenger acting as a spotter, was engaged in a mustering operation at a remote cattle station. The spotter reported that while transiting to another paddock, at a height of approximately 200 ft above ground level, the helicopter developed a lateral shudder. The shudder intensified and the pilot rapidly lost control of the helicopter as it shuffled to the right. The helicopter then impacted the ground in a nose down, slight right-bank attitude, with little forward speed. A member of the support ground team nearby heard the impact and went to the scene. The pilot and observer had egressed the helicopter and were found lying on the ground forward of the cockpit. The pilot died while enroute to hospital.

Occurrence summary

Investigation number 200003267
Occurrence date 29/07/2000
Location 30 km S Yarromere Station
State Queensland
Report release date 19/11/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22
Registration VH-LDR
Serial number 1336
Sector Helicopter
Operation type Aerial Work
Departure point Yarromere Station, QLD
Destination Yarromere Station, QLD
Damage Destroyed

British Aerospace Plc BAe 146-100, VH-NJR

Summary

Early in the take-off run, the handling pilot of the BAe 146 heard a slight noise, followed by a loss of RPM and power on the number 2 engine. The pilot stopped the take-off at approximately 60 kts and returned the aircraft to the gate. The crew of another aircraft waiting at the runway holding point, reported seeing flames in the number 2 engine jet pipe.

An engine examination by the aircraft operator revealed that the engine fan assembly was not rotating. The operator removed the engine and forwarded it to the manufacturer in the USA for examination and repair. The Australian Transport Safety Board requested the National Transportation Safety Board of the USA to supervise the examination and provide a report to the Bureau.

The examination revealed that extensive damage to the engine had resulted from two first stage turbine blades separating, due to fatigue cracks emanating from the blade trailing edges near the blade platform.

The engine manufacturer advised that they had developed a corrective action for fatigue failure of first stage turbine blades, as contained in Service Bulletin ALF/FL 502/507 72-1043 of 11 January 1999, and revised on 3 September 1999. The manufacturer recommended that the service bulletin be complied with at the next access to the affected parts.

The first stage turbine was last accessible in February 1999, during a hot section inspection carried out by the engine manufacturer. There is no record indicating that the service bulletin was complied with at that time. The manufacturer offered no explanation for not incorporating the service bulletin.

Occurrence summary

Investigation number 200003188
Occurrence date 30/07/2000
Location Canberra, Aero.
State Australian Capital Territory
Report release date 01/12/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-NJR
Serial number E 1152
Sector Jet
Operation type Air Transport High Capacity
Departure point Canberra ACT
Destination Brisbane Qld
Damage Nil

Cessna P206C, VH-EFA

Significant Factors

  1. The pilot departed Margaret Bay later than planned without the certainty that the flight could be completed in the required daylight conditions.
  2. The pilot continued flight in weather conditions for which he was not currently qualified.
  3. The pilot continued flight in weather conditions for which the aircraft was not adequately equipped.
  4. The pilot, after receiving radar navigation assistance, was unable to see the runway lights.
  5. The pilot possibly experienced spatial disorientation and loss of control while manoeuvring the aircraft in darkness and poor weather without adequate visual cues.

Analysis

Planning for the flight had ensured compliance with the regulations but provided little or no margin for any delay or poor weather. Despite the narrow margins, there was no evidence of any contingency planning. Although primary responsibility for the safety of the flight rested with the pilot, lack of additional guidance or alternative arrangements, did not provide an opportunity to influence the pilot's subsequent actions. In this instance the pilot considered diverting to Mareeba but, because that did not offer a better alternative, he continued flying toward Cairns rather than landing at Cooktown. It is possible that concerns for the injured passenger and the perishable cargo may have influenced the pilot's judgement and in-flight decision making.

Lack of recent exposure to that type of charter flying may have also affected the judgement and decision-making skills displayed by the pilot. The type of operational decision-making required of a charter pilot was significantly different from the type of decisions required during instructional duties and may have accounted for the pilot's expressed anxiety about undertaking the flight. It could also account for the chief pilot's assessment of the pilot's decision-making ability being inconsistent with that displayed on that occasion.

The pilot's decision to depart Margaret Bay approximately 20 minutes later than the planned latest time of departure was based on his assumption that more favourable winds at a higher altitude might allow an arrival at Cairns before last light. That decision was significant to the development of the accident sequence. The 1520 departure from Margaret Bay meant that the planned flight would arrive at Cairns seven minutes after last light. The GPS navigation unit could have provided the pilot with an estimate for Cairns that would have confirmed that a landing at Cairns before last light was unlikely. The pilot's decision to continue, especially after he received advice that weather conditions at Cairns had deteriorated below VMC, was even more crucial to the outcome. Continued flight in darkness and non-VMC weather conditions ultimately created the circumstances conducive to the accident.

The pilot elected to remain at low-level, below the cloud and in sight of the coast. Although the pilot had previously held an instrument rating, he was not trained to fly an ILS approach. He did not have any recent instrument flight time and probably lacked the confidence to climb the aircraft into cloud and to a safe altitude above terrain. Tracking visually along the coast resulted in a flight path that was not aligned with the extended runway centre line and denied the pilot the opportunity of using approach lighting, in the reduced visibility, for guidance to the runway. Light reflected from the aircraft's landing light beam in the rain and mist may have also prevented the pilot from seeing the runway lights during the unsuccessful approach attempts.

Anxiety produced by the delayed departure, deteriorating weather conditions and darkness, would have combined to increase the pilot's level of stress. The likelihood of fatigue affecting the pilot's cognitive and motor skills due to the mental and physical demands of flying the aircraft, especially in the latter stages of the flight, may have been considerably increased. High stress levels, fatigue and lack of external visual reference most likely contributed to the pilot experiencing spatial disorientation and subsequent loss of control.

The circumstances of the accident were consistent with the pilot experiencing spatial disorientation and subsequent loss of control while manoeuvring the aircraft in darkness and poor weather without adequate visual cues.

Factual Information

History of the flight

The pilot of a Cessna C206 was conducting a charter flight in accordance with the visual flight rules (VFR) from Margaret Bay to Cairns with a passenger and a cargo of live seafood. The flight was reported to have departed Margaret Bay at 1520 EST. At 1719 the Brisbane Daintree sector controller broadcast, on the area frequency, the amended Cairns terminal area forecast and the trend type forecast that indicated visual meteorological conditions (VMC) did not exist. Six minutes later, when the aircraft was estimated to have been northwest of Cooktown, the pilot requested the weather conditions at Mareeba. The controller informed the pilot of the automatic weather observing system information for Mareeba and said that he would attempt to obtain a cloud cover report from an overflying aircraft. The pilot was not informed of that information nor did he subsequently request it. At 1813 he reported at Cape Tribulation, 51 NM north of Cairns, and revised his estimate for Cairns to 1838. That estimate was 10 minutes after last light for Cairns. Shortly after, a pilot on the airstrip at Wonga Beach, about 38 NM north of Cairns, sighted the lights of an aircraft tracking coastal toward Cairns. That observer estimated that the aircraft was flying at an altitude of 100 ft and in visibility reduced to less than 1 NM in heavy rain and approaching darkness.

At 1824, four minutes before last light, the pilot contacted Cairns approach and reported that the aircraft was 33 NM north of Cairns. After the pilot confirmed that his operations were normal the approach controller advised him of the aerodrome terminal information service (ATIS) weather at Cairns. The controller asked the pilot if he was able to remain in sight of the coast and if he was capable of flight in instrument meteorological conditions (IMC). The pilot advised that he had the coast in sight and that he was not capable of flight in IMC. The controller subsequently issued the pilot with a clearance to follow the coast not above 1,000 ft and remain in VMC. Although the pilot had not declared an emergency, the controller recognised the potential danger and declared an uncertainty phase.

Radar data from the time the aircraft was identified north of Cairns showed that the aircraft tracked east of the coast at altitudes varying between 200 and 600 ft. During that time the approach controller provided the pilot with cloud and visibility information reported by pilots conducting instrument approaches to runway 15 at Cairns. He monitored the progress of the flight and provided the pilot with distance and groundspeed information. He also offered the pilot radar headings to establish the aircraft clear of terrain and position the aircraft for an approach to runway 15. The approach controller requested that the aerodrome controller select the approach lighting to maximum illumination. The pilot, in response to a query by the approach controller, advised that he had his landing lights on during the approach.

The Cairns meteorological observation at 1830 recorded a visibility of 2,500 m in rain showers with scattered stratus cloud at 300 ft and broken cumulus at 1,800 ft. A pilot making an instrument approach to Cairns ahead of the C206 reported the main cloud base as 1,100 ft with lower patches of cloud. He reported seeing the approach lights at 4 NM and the runway lights at 1 NM. The aerodrome controller estimated that the visibility at the time the C206 was making its approach was 1,500 m in heavy rain.

When the C206 was almost overhead the airport the pilot reported that he was unable to see the runway lights, so the controller instructed him to make a left orbit for a second landing attempt. The aerodrome controller saw the aircraft descend from 400 ft to approximately 100 ft during the turn and activated the crash alarm because he thought an accident was imminent. He selected omni-directional runway lighting to aid detection. The pilot's second approach was also unsuccessful and again the aircraft was seen to lose altitude while turning left. The approach controller then directed the pilot to take up a northerly heading, away from obstacles and terrain. He intended to position the aircraft for a third approach along the extended runway centre line so that the pilot would be better positioned to use the approach lighting for guidance to the runway. That flight path took the aircraft over the water off Machans Beach. At 1851, on the third attempt to approach and land and while being radar vectored onto a left base leg to runway 15, the aircraft disappeared from radar 2 NM north-north-east of Cairns.

Witnesses at Machans Beach reported seeing the lights of an aircraft flying at low-level offshore. They described seeing the lights rotate in a manner consistent with the aircraft rolling steeply to the left and disappearing from view in rain and mist. One witness reported hearing a faint sound of impact. Airport rescue and firefighting services had been alerted nearly one minute before the aircraft disappeared from radar. Despite the inclement conditions, an air and sea search of the area was conducted by the Cairns based search and rescue helicopter and rescue craft from the airport rescue and firefighting service. At 2050, searchers found the body of the passenger and debris in the water near the reported accident site. The following day some personal items and debris from the aircraft were found. Damage to the recovered aircraft parts suggested that the aircraft had impacted the water heavily and the accident was not survivable.

Air, sea and coastal searches continued over the next few days, including the use of airborne electronic detection equipment, but neither the pilot nor the main aircraft wreckage was found. On 9 November, 3 months after the accident, wreckage was sighted approximately 4 km offshore. Divers recovered parts from the underwater wreckage that were later identified as belonging to the accident aircraft.

Flight planning

The company was contracted to fly cargoes of live seafood, reported to be valued at up to $18,000 per flight, from Margaret Bay to Cairns. On the day of the accident, two company aircraft were scheduled to make the flight. Those flights were normally flown by instrument rated pilots. Regulations allowed cargo flights in single engine aircraft to be conducted in accordance with instrument flight rules (IFR) and at night. That allowed greater planning flexibility when tide levels dictated later departure times from Margaret Bay. Although both aircraft were equipped for flight in accordance with IFR only one had an autopilot. A serviceable autopilot was a requirement for single-pilot IFR. As only one instrument rated pilot was available it was decided that he should fly the auto-pilot equipped aircraft while the accident pilot flew the C206.

Careful planning was necessary to ensure that the aircraft piloted by the non-instrument rated pilot could conduct the flight in accordance with VFR. Flights to Margaret Bay were planned to arrive and depart during periods when tide levels below 1.8 m permitted use of the beach as a landing area. On the day of the accident there were two periods when tide levels were less than 1.8 m, one early to mid morning and the other from 1340 that afternoon. The earlier period was considered impractical. A first light departure from Cairns would not have allowed an arrival at Margaret Bay early enough to complete a normal turnaround on the beach before the advancing tide. The customer also preferred the later arrival time which just made possible a normal turnaround and return flight to Cairns in daylight. The pilot had determined 1500 as the latest time he could safely depart Margaret Bay for an arrival at Cairns before last light.

Boat crewmembers were sometimes transported to Margaret Bay on the flights. Regulations governing the carriage of passengers in single, reciprocating-engine aircraft required the flights to be conducted in accordance with day VFR. On 3 August a passenger was to be flown to Margaret Bay. Additionally, the customer requested that an injured deck hand on the boat be flown to Lockhart River while the transfer of cargo from the boat to the beach was being carried out. The deck hand had severed the tip of a finger the previous day. Although not requiring urgent medical attention he was anxious to get to hospital where it was reported that arrangements had been made to have the severed part of his finger sewn back. Overnight accommodation at Lockhart River had been arranged for the injured deck hand and a reservation made for him on the next day's scheduled flight to Cairns. The aircraft operator advised that the flight was not possible because the additional flying time to Lockhart River and return would not have ensured arrival back at Cairns before last light. Instead, the operator and the customer agreed to limit the volume of cargo in the C206 and fly the passenger direct to Cairns.

Delayed departure from Margaret Bay

Arrival of the aircraft was signalled to the crew of the fishing boat by circling overhead. When alerted, the crew commenced packing the live seafood into tubs in preparation for air transport to Cairns. Loading and transfer from the boat to the aircraft took longer than normal. Witnesses reported that the pilot appeared to be extremely agitated and was visibly distressed about the delay but he had expressed the belief that more favourable winds at a higher altitude might enable him to make up the lost time. The pilot of another VFR aircraft on the beach at that time reported that he estimated there was inadequate daylight for his return to Cairns with the existing wind conditions and elected to remain overnight. He had suggested the same course of action to the accident pilot but reported that the accident pilot had made up his mind to return to Cairns that day. Logistically, a landing at Cooktown would have taken surface transport over eight hours for the return journey from Cairns. The consequences of that action would have delayed treatment to the injured passenger and risked the loss of the perishable cargo.

Pilot experience

The pilot held a commercial pilot licence and a valid Class 1 medical certificate. He had accumulated 13,157 hours flight experience during 22 years of active employment in general aviation. Most of his flying experience was flight instruction and he held a current Grade 1 Instructor Rating. In 1991 he qualified for a Command Instrument Rating endorsed for non-directional beacon (NDB) approaches only. He had not renewed the rating after its expiry on 30 April 1993. The only recent instrument flight the pilot recorded were practice NDB approaches on a synthetic procedure trainer in preparation for revalidation of his lapsed instrument rating. In the 90 days prior to the accident he had logged 6.6 hours of night flying that included a navigation training flight and a check flight with the Chief Pilot.

During the 12 months preceding the accident the pilot had recorded 515 hours of which 35 hours were charter flying. Nearly all of that charter flying consisted of short local scenic and aerial work flights. Although the pilot had not flown to Margaret Bay for some time, he was familiar with the York Peninsula area. The 72-hour history of the pilot did not reveal any circumstances that would have affected his ability to perform his duties. The family of the pilot reported that he was unusually anxious about undertaking the flight and had expressed concern about the available time frame for the flight. The chief pilot, who was responsible for rostering pilots, described the pilot as reliable and possessing sound judgement. He described the pilot's decision to continue the flight in darkness and poor weather as uncharacteristic.

Aircraft and equipment

It was not possible to determine if there was any aircraft defect that may have contributed to the accident sequence. Examination of the small amount of wreckage that was recovered indicated that the aircraft engine was developing some power at the time of impact. Inspection of the aircraft's maintenance documentation showed that the required maintenance had been certified as completed. Pilots who flew the aircraft before the accident flight reported that it had been serviceable. The aircraft was certified for flight in accordance with the instrument flight rules (IFR). An entry on the duplicate copy of the maintenance release stated that there was no autopilot fitted and that for IFR operation in accordance with Civil Aviation Order (CAO) 20.18 subsection 4.1B (ie, Charter or Airwork), two instrument rated pilots were required. The duplicate copy of the maintenance release also noted that no Emergency Locator Transmitter (ELT) was installed. The aircraft was equipped with a VHF omni-directional radio range (VOR) receiver, incorporating glideslope information that enabled instrument landing system (ILS) approaches to be flown and automatic direction finding (ADF) radio navigation aids. The pilot had borrowed a portable hand-held Global Positioning System (GPS) satellite navigation unit for the flight and had mounted it on top of the instrument panel. The unit also displayed tracking and groundspeed information.

Weather

The forecast obtained by the pilot that morning indicated that VMC could be expected along the planned route but with visibility reduced to 2,000 m in isolated areas of drizzle, showers and smoke. The Cairns terminal area forecast (TAF) issued at 0825 forecast VMC with showers of rain but no further deterioration until 2000; well after the planned arrival at Cairns. At 1328 the Cairns TAF was amended to include an intermittent (INTER) deterioration in conditions below VMC from 1600. An INTER is used to indicate changes expected to occur frequently for periods of less than 30 minutes duration, with conditions fluctuating almost constantly, between the times specified in the forecast. The amended Cairns TAF also included a temporary (TEMPO) deterioration in conditions from 2000. TEMPO is used to indicate changes in prevailing conditions expected to last for a period of less than one hour in each instance. A further amendment to the Cairns TAF was issued at 1531 that forecast a visibility reduced to 9,000 m in showers and patches of low cloud with a base of 800 ft. A TEMPO period from 1800 forecast visibility reduced to 2,000 m in showers with patches of low cloud at 300 ft. This was the forecast broadcast by the controller at 1719, while the aircraft was estimated to be north-west of Cooktown.

Recorded rainfall data indicated that rainfall intensity at Cairns airport for that day was greatest between 1800 and 1900.

VFR considerations

The Aeronautical Information Publication stated that day VFR flights must not depart from an aerodrome unless the Estimated Time of Arrival (ETA) for the destination or alternate is at least 10 minutes before last light, after allowing for any required holding. Calculations based on aircraft performance and forecast winds gave a planned time interval of 3 hours 15 minutes. That meant that a departure from Margaret Bay at 1520 would result in an ETA for Cairns of 1835, seven minutes after last light. The amended Cairns TAF with the INTER requirement, broadcast by the controller at 1719, would have necessitated an arrival at Cairns no later than 1748 in order to meet the requirements for VFR flight. Pilots of VFR aircraft faced with similar circumstances were taught, as part of their training, to make an in-flight diversion to another destination while weather and daylight permitted. Weather conditions at Cooktown that afternoon were reported to be VMC.

Operational control

Operational control was defined as the exercise of authority over the initiation, continuation, termination or diversion of a flight, in the interest of the safety of an aircraft.

Prior to January 1992 the then Civil Aviation Authority through its specialist air traffic services personnel provided a comprehensive operational control service. Pilots of VFR flights proceeding more than 50 NM were required to submit flight plan information that was checked by controllers to ensure compliance with regulations and operational requirements. Operations controllers with access to current weather and NOTAM information monitored all flights to ensure that pilots were aware of significant changes to weather and other operational factors that may affect the safety of the flight. That information was transmitted through the aeronautical communications network to a pilot and, when considered necessary, an appropriate response sought. In extreme cases, pilots could be directed to land or be diverted to ensure the safety of the flight.

Following a review of that service, changes to Australian regulations were made to more closely align with international regulations. Those changes resulted in the withdrawal of the operational control service and greater responsibility for the safe conduct of a flight to the pilot in command. In effect that meant that operational control was exercised by a pilot complying with regulations, standard operating procedures as published in company Operations Manuals and by displaying sound airmanship.

The Civil Aviation Safety Authority (CASA), in its program of regulatory reform, intends to require air transport (incorporating what is currently termed charter) operators to establish and maintain a method of supervision of operations. If accepted, the changes would require operators to state in their Operations Manual the means by which operational control is to be exercised. It is envisioned that such regulation would cover at least a description of responsibilities concerning the initiation, continuation, termination or diversion of each flight and include specific information to pilots on suitable alternate aerodromes and the means of updating weather and NOTAM information.

Decision-making

In the manual "Aeronautical Decision Making for Commercial Pilots" developed for the United States Federal Aviation Administration (FAA), the point is made that charter pilots often have to balance commercial considerations against safety and compliance with regulations. In doing so they can be subjected to pressures from management, clients and passengers more attuned to non-safety related issues such as economy and expediency. Those people may assume that the pilot will resist these pressures if there is any "real" danger and respond appropriately to avoid disaster. Conversely, pilots can be persuaded, even to the detriment of safety, by the knowledge that a decision contrary to the wishes of the customer or management may incur economic penalties that could adversely affect commercial viability and hence their employment. Pilots who regularly fly in such environments become used to recognising those conflicting demands and practicing their decision-making skills.

The importance of good pilot decision-making skills was recognised by the Civil Aviation Safety Authority. In 1996 decision-making as a topic was included in the Human Performance and Limitations section of the Day VFR Syllabus (Aeroplanes) of the Aeronautical Knowledge requirements for pilots. The requirements included a knowledge of the basic concepts of decision making including the influence of employer pressure, the desire to get the task done, workload management, work overload and currency. That knowledge requirement was not made retrospective. Transport Canada introduced a similar requirement for commercial pilots engaged in multi-crew operations to complete a "once only" pilot decision-making course. Following an accident in 1998 involving a high-performance single-engine turbine aircraft, the Canadian Transportation Safety Board recommended that the requirement be extended to all pilots engaged in commercial operations.

Risk management

Identifying hazards and developing contingency plans to avoid or mitigate their effect is a risk management strategy used by safety-conscious individuals or organisations to reduce risk. The transport of perishable cargo from a remote beach landing site presented additional hazards to that of normal charter operations. The company had addressed the hazards associated with landing and taking off from beaches by determining tide heights that permitted adequate runway width and by additional beach take-off and landing training for pilots. Flights made under the IFR were not as likely to be delayed or diverted and reduced the risk of losing valuable cargoes because of the perishable nature of the live seafood. However, use of VFR aircraft and pilots increased the possibility of weather or daylight affecting an assured arrival.

The VFR pilot of the other aircraft engaged in the transport of live seafood from Margaret Bay to Cairns had identified risks associated with his operation and taken precautions to avoid them. He had fitted a marine high frequency channel to his aircraft's radio to permit direct communication with the fishing boat crew. That enabled him to advise them of his arrival so that they could prepare for the transfer of cargo and avoid delay. He also forewarned the crew of his latest time of departure of 1445 and his alternative arrangements for an overnight stay should the deadline not be met. Importantly, when the boat crew failed to meet the deadline he implemented his contingency plan and flew to a nearby island where he remained overnight, returning the next day as arranged, to collect the cargo and fly it to Cairns. That was the course of action he had suggested to the pilot of the C206 on the beach at Margaret Bay.

The Civil Aviation Safety Authority, in a discussion paper issued in May 2000, proposed changes for certification of commercial air transport operators (incorporating charter) that included an obligation for those operators to introduce an accident prevention and flight safety program incorporating risk management processes and hazard identification.

Occurrence summary

Investigation number 200003233
Occurrence date 03/08/2000
Location 4 km NNE Cairns, Aero.
State Queensland
Report release date 20/12/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category VFR into IMC
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 206
Registration VH-EFA
Serial number P2060425
Sector Piston
Operation type Charter
Departure point Margaret Bay, QLD
Destination Cairns, QLD
Damage Destroyed

British Aerospace Plc BAe 146-100 , VH-NJV

Summary

While cruising at FL240 in instrument meteorological conditions, on a flight from Brisbane to Townsville, the crew of a BAe 146 noticed the amber engine vibration (ENG VIBN) annunciator had illuminated. The engine thrust management system (TMS) was configured to 830 degrees Celsius in turbine gas temperature (TGT) mode, and all engine and airframe anti-ice systems were selected ON at the time.

A check by the crew revealed the number 1 engine vibration indication to be at 1.5 units, a reading that was outside the Manufacturer's prescribed limits. All other engine indications were normal. The crew disconnected the TMS and shut down the number 1 engine. The crew then decided to return to Brisbane.

Shortly after, the ENG VIBN annunciator again illuminated and the number 3 engine vibration indicator showed 1.5 units, with all other engine indications normal. The number 3 engine power lever was then retarded to below 80%. The ENG VIBN annunciator extinguished, and the indicated vibration level dropped to approximately 0.5 units.

During descent, the operation of the number 3 engine was monitored with nothing abnormal noted, and an uneventful one engine inoperative landing was subsequently carried out.

The pilot later reported that the weather conditions in the area were conducive to intake icing, with the possibility that the aircraft was flying through moderate freezing rain at the time of the incident.

A maintenance investigation carried out by the operator following the incident, discovered water ingress into the number 3 engine vibration transducer, in the lower fan cowling area. This has been known to result in erroneous vibration instrument indications in the past. No other mechanical defect was discovered that would have resulted in the vibration in either engine. Following the completion of operational tests, the aircraft was returned to service. The vibration has not recurred.

The ATSB investigation concluded that the indicated engine vibrations were consistent with a build up of ice on the fan areas of engines 1 and 3 while the aircraft was being flown in icing conditions. This conclusion is reinforced by the report from the pilot in command that the engine vibrations subsided as engine RPM was reduced, and did not return when the number 3 engine RPM was increased when clear of the icing conditions. The vibration indications on the number 3 engine may have been further affected by the water ingress into the area of the vibration transducer.

Occurrence summary

Investigation number 200003155
Occurrence date 27/07/2000
Location 185 km NW Brisbane, Aero
State Queensland
Report release date 22/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Abnormal engine indications
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-NJV
Serial number E1002
Sector Jet
Operation type Air Transport High Capacity
Departure point Brisbane Qld
Destination Townsville Qld
Damage Nil

Messerschmitt BK117 B-2, VH-BKZ

Summary

The pilot of a BK117 helicopter reported that while in a gentle climb at about 4,600 feet during a post maintenance test flight, the helicopter suddenly pitched nose-up. The indicated airspeed decreased to zero and the helicopter then pitched nose-down to a slightly inverted attitude. After descending about 2,000 feet, the pilot regained control and landed safely.

Inspection of the helicopter systems by the company maintenance personnel could not find any reason for the sudden loss of control.

A Bureau of Meteorology area forecast, issued on the day of the incident, indicated severe turbulence below 10,000 feet. The forecast also included increasing westerly wind speeds ranging from 30 knots at 2,000 feet to 45 knots at 10,000 feet. The actual weather report for the area that the helicopter was operating in, indicated westerly wind speeds increasing from 35 knots at 2,000 feet to 50 knots at 7,000 feet. These conditions are conducive to mountain wave and rotor activity.

A rotor is a large air mass rotating about a substantially horizontal axis. It is generated in the lee of a mountain or sharp ridge in strong wind conditions.

The helicopter was operating on the lee side of a mountain range when the pilot experienced the rapid loss of control. It is probable that the helicopter encountered a rotor.

Occurrence summary

Investigation number 200003143
Occurrence date 17/07/2000
Location 9 km E Warragamba Dam, (VTC Check Point)
State New South Wales
Report release date 03/05/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Loss of control
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Messerschmitt-Bolkow-Blohm
Model BK117
Registration VH-BKZ
Serial number 7213
Sector Helicopter
Operation type Aerial Work
Departure point Bankstown, NSW
Destination Bankstown, NSW
Damage Substantial

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

Kawasaki 47G3B-KH4, VH-JWZ

Safety Action

Local Safety Action

Following this occurrence the operator issued a notice to all company pilots about the correct technique for measuring the contents of the fuel tank. In addition, the company discontinued its policy of employing part-time relieving pilots at bases which were staffed by a single full-time pilot.

Significant Factors

  1. The pilot used an incorrect technique to dip the helicopter's fuel tank and consequently overestimated the fuel on-board.
  2. The helicopter operator had not advised the pilot of the change in method for measuring the fuel quantity with the new wooden dip stick.
  3. The pilot did not detect the discrepancy between the dip stick reading, the physical level of fuel contained in the tanks and the reading from the cockpit fuel gauge.
  4. The helicopter fuel log contained ambiguous entries which the pilot used to resolve the discrepancy between the incorrect dip stick reading and the fuel quantity recorded on completion of the previous day's flying.
  5. The helicopter was being flown with insufficient fuel to complete the flight.

Summary

The pilot was conducting a series of scenic charter flights in a Kawasaki KH4 helicopter and had already completed several flights during the morning. The pilot reported that he departed on a 30-minute scenic flight and had been airborne for about 25 minutes when the engine suddenly failed. At the time the of the engine failure the helicopter was flying 500 ft above ground level, about 2 NM north-west of the planned landing area. The pilot immediately lowered the collective control for the main rotor and entered an auto-rotative descent.

During the descent the pilot assessed that the helicopter could not safely reach a clearing to the south-west and manoeuvred to land in lightly timbered terrain. During the landing flare the tail rotor was reported to have struck the branches of a tree and the helicopter tipped forward before landing in a slight nose-down attitude. Damage to the tail rotor blades, main rotor mast, right front landing skid, VHF radio aerial and landing light was reported. The pilot and the two passengers did not report being injured.

The helicopter operator reported there was no mechanical reason for the loss of engine power and that fuel exhaustion may have contributed to the engine's loss of power. Approximately half a litre of AVGAS was recovered from the fuel tanks at the accident site and there was no obvious damage to the fuel system. Standard company policy required the pilot to ensure the helicopter carried enough fuel to complete the planned flight, plus an extra 20-minute fixed fuel reserve.

The pilot was a part-time employee of the helicopter operator and would relieve the full-time pilot, usually one day a week. He had been employed on this basis for approximately three months. The operator reported the recent replacement of the calibrated dip stick used to measure the fuel tank contents had contributed to the circumstances of the fuel exhaustion.

The original dip stick was a hollow calibrated hard-plastic tube and was the dip stick supplied by the helicopter manufacturer for dipping the fuel tanks. The tank contents were measured by inserting the dip stick diagonally into the tank, passing it through a hole in the tank baffle and then placing a finger over a small hole at the top of the dip stick. This would cause fuel to be trapped inside the tube, allowing the dip stick to be removed from the tank and reading of the tank contents against a graduated scale.

To ensure the plastic dip stick was inserted at the correct angle, two metal pins protruded from either side, near the top of the dip stick. These pins would rest on the fuel filler neck and ensured the fuel quantity could be measured consistently. Cracks in the plastic tube had made the dip stick ineffective for measuring the tank contents and the helicopter operator had recently replaced it with a wooden dip stick.

The new wooden dip stick had been calibrated to measure the fuel quantity when inserted almost vertically into the tank, without passing through the hole in the tank baffle. Using this technique had the advantage of restricting the angle at which the dip stick could be inserted into the tank and when correctly applied, would not cause large errors in measuring fuel quantity.

On the day of the accident, the pilot reported that he had used the new wooden dip stick for the first time. He had used the same technique to dip the fuel as he had been instructed to use with the original plastic dip stick. He was not aware that this method for measuring the fuel quantity was only valid when using the original manufacturer's supplied dip stick.

This had resulted in the pilot inserting the wooden dip stick into the tank at an oblique angle, passing through the tank baffle and resting on the tank bottom. This technique could result in a significant over estimation of tank contents. The pilot reported that he had not been advised of the change in method for dipping the tanks using the new dip stick, although he previously had used similar dip sticks on other models of helicopter.

The pilot reported that on the day of the accident, he had first dipped the fuel tanks during the daily inspection conducted prior to the first flight of the day. During this inspection, he detected a discrepancy with the helicopter's fuel log, where the closing figure from the previous days flying did not appear to match the reading he obtained from the tank dip. In trying to resolve this discrepancy, the pilot reviewed other entries in the fuel log and noticed what he believed was another similar discrepancy from the day before. With this discrepancy in mind, he elected to proceed on the basis that his dip of the tank was accurate. The pilot continued to over estimate the quantity of fuel contained in the tanks during subsequent dips of the tank.

The operator subsequently reported the pilot had misread the fuel log and there was no discrepancy. The investigation reviewed the calculations of the aircraft's hourly fuel consumption, which supported the accident pilot's interpretation of the entry in the fuel log for the day before the accident. It was not possible to further address this ambiguity or to determine positively what figure had been entered in the fuel log.

The operator did not have a policy for resolving discrepancies with fuel log entries and relied on the pilot using the dip stick to check the fuel quantity before confirming this reading with a visual check of the tank contents. The operator reported that all pilots were trained to verify dip stick readings using this method and that the tank contents could be seen through the opening of the filler neck. This figure would then be verified against the indications of the fuel gauge and the information contained in the aircraft fuel log. The pilot reported that he was not in the practice of making a visual check of the tank contents and he relied on the reading he obtained from the fuel dipstick as being the quantity contained in the tanks. He could not recall being instructed in the technique of comparing dipstick readings with a visual assessment of the tank contents during his training. The pilot did not detect any discrepancy between the fuel quantity measured using the dip stick and the readings from the cockpit fuel gauge. The investigation was unable to verify the apparent training discrepancy.

The pilot fuelled the helicopter twice on the day of the accident. Before the first flight of the day, 40 litres had been added and another 105 litres was added later that morning. The pilot estimated that when the engine failed, the helicopter had flown about 1-hour 25-minutes since the last refuelling. Based on information supplied to the investigation, it was likely the fuel tanks contained between 30 and 50 litres before the first flight of the day and between 25 and 35 litres before departing on the accident flight.

The pilot reported that he had been monitoring the fuel consumption by crosschecking the fuel gauge indications with readings obtained from the dip stick. However, he did not detect the critically low fuel level before he departed on the accident flight. It was also likely the fuel level was critically low on completion of the first flight of the day.

Contributing to the circumstances of the fuel exhaustion was the ambiguity with the fuel log entry from the previous day's flying. The pilot's relatively low-level of experience on this helicopter type and his employment status as a part-time relieving pilot had possibly contributed to his reliance on a dip stick reading to resolve the discrepancy with the helicopter's refuelling log.

Occurrence summary

Investigation number 200003056
Occurrence date 18/07/2000
Location 4 km NW EI Questro, (ALA)
State Western Australia
Report release date 03/08/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel exhaustion
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Kawasaki Heavy Industries
Model 47
Registration VH-JWZ
Serial number 2108
Sector Helicopter
Operation type Charter
Departure point EI Questro Station WA
Destination EI Questro Station WA
Damage Substantial

Piper PA-28R-201, VH-PRF

Summary

A British Aerospace 146 (BAe 146) was arriving at Alice Springs from the north-east and was instructed by air traffic control to make a visual approach to runway 12 via a left circuit.

A Piper Cherokee Arrow (Arrow) was also arriving at Alice Springs on a flight from Coober Pedy and was instructed to track via visual flight rule route "VFR Route 6". That route tracked via the Stuart Highway, south-west of the aerodrome. As the aircraft passed Mount Polhill (20 NM from the aerodrome) the pilot was cleared to track via the gaol and to then make a visual approach to runway 06.

When the BAe 146 was on final approach the crew sighted the Arrow approximately 1 NM ahead and descending through their level. They commenced a go-around and manoeuvred to the right to ensure that they passed behind that aircraft.

The pilot of the Arrow had misinterpreted some of the controller's instructions and had tracked for a circuit because he was not set up for a straight-in approach. However, in carrying out that action he had not informed the controller of his change of plan and his inability to carry out the instructions received.

Although the controller was looking for the Arrow in order to provide a visual service, he did not see the aircraft because the pilot had been tracking in a direction that the controller was not expecting.

Occurrence summary

Investigation number 200003093
Occurrence date 17/07/2000
Location 12 km SSW Alice Springs, Aero.
State Northern Territory
Report release date 16/10/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Separation issue
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-28
Registration VH-PRF
Serial number 28R-7837078
Sector Piston
Operation type Private
Departure point Cooper Pedy, SA
Destination Alice Springs, NT
Damage Nil

Aircraft details

Manufacturer British Aerospace
Model BAe 146
Registration VH-JJX
Serial number E2127
Sector Jet
Operation type Air Transport High Capacity
Departure point Cairns, QLD
Destination Alice Springs, NT
Damage Nil

Boeing 737-33A, VH-CZW

Summary

During completion of routine fuel sampling, before the first flight of the day, maintenance personnel reported finding a red/ brown liquid present in the fuel sample removed from the Boeing 737 aircraft. An inspection of the aircraft's fuel system was carried out with no blockage of filters or other safety of flight issues related to the contamination found.

Testing of the fuel recovered indicated no fungal (cladisporium resinae) species. However, there was a heavy load of bacteria (pseudomonas) present in the water layer, with a related film between the water and fuel layers. The contamination was not believed to be aircraft created but fuel source related. Operators held meetings with fuel company representatives, CASA, and the ATSB attempting to determine the origin of the contamination. Fuel company representatives contacted their refineries but none reported abnormal water drains. Mapping of the fuel supplied to the aircraft reported as contaminated was completed by the operator with no common fuel upload origin point defined.

Research identified several past similar events in Australia. One such event in 1962 was experienced on Boeing 707 aircraft and was believed related to sulphonates in the fuel combining with trace levels of transition metals (including iron). Similar events, reported in 1996 and 1997, were believed to have been caused by the reaction of a complex of naphthenic/ sulphonic acids with transition metals (including iron).

Despite intensive investigation of this event, the source of the contamination could not be established and sporadic reports of contaminated fuel samples persist. This contamination was not related to the aviation gasoline (AVGAS) contamination reported in December 1999, as analysis confirmed no presence of Ethylene Diamine.

Occurrence summary

Investigation number 200003034
Occurrence date 21/07/2000
Location Adelaide, Aero.
State South Australia
Report release date 22/01/2001
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel contamination
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 737
Registration VH-CZW
Serial number 23832
Sector Jet
Operation type Air Transport High Capacity
Departure point Adelaide, SA
Destination Melbourne, Vic.
Damage Nil

Boeing 767, VH-ZXC

Safety Action

The crew viewed the QAR data for reference and were debriefed by the operator's Flight Safety Department. Details of the incident were promulgated to other crew and the operator indicated the Flight Safety Department is actively monitoring the situation in regard to tail strikes.

Analysis

Boeing data (Airliner, Jul-Sep 1994) suggests the most common factors in takeoff tail strike events are excessive rotation rate and early rotation. In this particular incident, ground contact was slight, resulting in removal of paint from the tail skid. The tail skid performed its intended function, that is, providing a contact barrier which protects the aft fuselage against takeoff tail strikes. It is considered that the inexperience of the handling pilot and the gusty crosswind conditions contributed to the tail strike incident

Summary

The crew of an aircraft waiting for clearance to taxi across an active runway observed a departing Boeing 767-300 scrape its hydraulic tail bumper during rotation. This information was then relayed to the pilot in command of the departing aircraft who elected to continue the flight in accordance with the non-normal checklist. Maintenance personnel inspected the aircraft when it arrived in Sydney and determined the strike was minor. A repaint of the skid was all that was required for the aircraft to continue in service.

A second officer undergoing promotional training to first officer was the handling pilot during the incident. This was the fourth sector of line training and the take-off was conducted during a moderately gusty 15 kt wind. The crosswind component was estimated to be in the order of 8-13 kts. Take-off and initial climb performance depend on rotating at the correct airspeed and proper rate, to the rotation target attitude. Early, rapid or over-rotation may cause aft fuselage contact with the runway. Aft fuselage contact will occur at a pitch attitude of 9.8 degrees on the 767-300 with the wheels on the runway and landing gear oleos extended. For optimum take-off and initial climb performance, a smooth continuous rotation is initiated at the calculated rotation speed (VR) to the rotation target attitude. Rotation should be smooth and at an average pitch rate of 2 to 3 degrees per second. A 10 degree body attitude will be achieved in approximately 3 to 5 seconds with all engines operating, and liftoff will occur at a pitch attitude of 8 to 9 degrees. When the rotation rate is greater than 3 degrees per second, the minimum tail clearance decreases, and may result in contact with the ground. The minimum tail skid clearance on a normal take-off is approximately 61 cm and occurs after liftoff. This is a consequence of the aircraft geometry and the dynamic forces that are acting after rotation has been initiated.

Analysis of Quick Access Recorder (QAR) data for this incident indicated that rotation commenced at an airspeed approximately 5 kts above the calculated VR. The recorded data also showed the pitch attitude of the aircraft during liftoff did not exceed the attitude that would result in aft fuselage contact. However, the aircraft was subject to a rapid rotation during much of the liftoff period. A maximum pitch rate of 4.6 degrees per second occurred one quarter of a second after main landing gear liftoff, coinciding with minimum tail clearance.

Occurrence summary

Investigation number 200003037
Occurrence date 21/07/2000
Location Melbourne, Aero.
State Victoria
Report release date 01/08/2000
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Ground strike
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer The Boeing Company
Model 767
Registration VH-ZXC
Sector Jet
Operation type Air Transport High Capacity
Departure point Melbourne, VIC
Destination Sydney, NSW
Damage Nil