Fuel starvation

Fuel starvation and forced landing involving Cessna 310R, VH-DAW, about 5 km south-east of Derby Airport, Western Australia, on 20 June 2023

Final report

Report release date: 30/04/2025

Investigation summary

What happened

On 20 June 2023, a Cessna 310R, registered VH-DAW and operated by Broome Aviation, was being flown on an air transport operation with a pilot and one passenger from Broome Airport to Turkey Creek, Western Australia (WA) and return. On the return flight, the pilot planned to stop at Derby Airport, to refuel.

On the return flight from Turkey Creek to Derby, the aircraft’s right engine began surging while being supplied from the auxiliary fuel tank. The pilot changed the tank selection to the right main tank, which had little fuel remaining. The right engine began surging a second time and the pilot determined there was enough fuel in the left main tank to sustain both engines to Derby. The pilot then selected the right engine to cross feed from the left main fuel tank.

Ten minutes later, both engines began surging. The pilot, assessing they had a dual engine fuel starvation, began switching fuel tanks searching for any remaining fuel. Unable to stop the engine surging, the pilot extended the landing gear and banked into a right turn with the intention of landing on the Derby Highway. During the turn, the right wing of the aircraft contacted a tree causing the aircraft to turn 180° and come to an abrupt stop on the edge of the highway.

The pilot sustained serious injuries, and the passenger sustained minor injuries. The aircraft was substantially damaged. 

What the ATSB found

The occurrence

The ATSB found that the planned flight from Broome to Turkey Creek and return to Derby with the required fixed reserve and contingency fuel could not be achieved without refuelling the aircraft en route. In addition, the pilot did not intend to use all the available fuel in the auxiliary tanks and did not take this into consideration in their pre-flight planning, further reducing the amount of fuel available. Also, the aircraft fuel gauges did not indicate accurately.

The ATSB also found that the pilot inadvertently did not select the fuel supply to the right engine to the right auxiliary fuel tank during the first leg of the journey and did not manage the fuel in accordance with the pilot's operating handbook requirements. This resulted in the depletion of fuel in the main tanks to a level where continuous engine operation could not be maintained.

Further, after the fuel in the right main fuel tank had been used, the pilot did not divert the aircraft to the closest airport, select the left engine to the left auxiliary fuel tank, or maintain altitude to increase their safety margin. Additionally, the pilot was not wearing an upper torso restraint during the forced landing resulting in the pilot receiving serious head injuries during the collision.

The pilot also had a lack of understanding of the aircraft fuel planning, fuel management and emergency procedures, and due to a lack of consolidation training and limited to no operational oversight these issues were not detected.

Operator oversight

The ATSB also found that during the 8-month period from November 2022 until the accident, Broome Aviation provided its pilots transitioning to operating the Cessna 310 with limited supervision, guidance and support, including management of the fuel system. In addition, aircraft defects were not being written on the maintenance release, leading to several defects not being rectified or managed.

Further, Broome Aviation pilots experienced pressure to not report aircraft defects on maintenance releases, and many pilots also experienced or observed pressure from company management to conduct flights in aircraft with defects that they considered made the aircraft unsafe for flight.

Finally, Broome Aviation’s operations manual did not include a procedure for recording in‑flight fuel calculations. As a result, pilots adopted varying methods for fuel monitoring, leading to reduced assurance of accurate in‑flight fuel management.

Civil Aviation Safety Authority oversight

The ATSB identified that, following a complaint by a former Broome Aviation pilot regarding management pressure on pilots to operate unserviceable aircraft, the Civil Aviation Safety Authority (CASA) conducted a level 2 surveillance activity on the operator in early June 2023 with a key scope element being to evaluate the complaint. In addition, CASA received further complaints after the accident, that were also added to a level 1 surveillance activity in August 2023. However, the surveillance activity and the associated reports did not assess the subject of the complaints.

Additionally, CASA approved a head of flying operations (HOFO) for Broome Aviation in early December 2022 via an abbreviated assessment as they had already been assessed for another operator and due to an expectation that it was an interim appointment. The person subsequently remained in the position for a much longer period and, when this situation was identified by CASA, the HOFO’s ability to continue undertaking the position when returning to work for another operator full time as a line pilot and alternate HOFO was not fully assessed.

What has been done as a result

Broome Aviation updated its operations manual to the new format exposition in response to Civil Aviation Safety Authority (CASA) findings during a level 1 surveillance audit. It now outlines an in‑flight fuel management procedure. 

The operator now has both a full-time HOFO and an alternative HOFO, who is also the Safety Manager. The new HOFO reported that all company pilots are fully aware that they are available to address questions or concerns. The operator has also modified its check and training system, implementing a revised check and training procedure and updated documentation to facilitate the tracking of pilot training and competency in line with current Civil Aviation Safety Regulations (CASR).

The new HOFO has changed the defect reporting process to ensure all defects are reported to either the HOFO or the alternative HOFO, and where required noted on the MR. The operator is now using maintenance releases to systematically document defects, ensuring that issues with aircraft in the fleet are properly tracked and addressed.  

Finally, Broome Aviation has implemented a safety management system in line with the current CASR in relation to a CASA audit finding. Monthly safety meetings are now being held to address safety concerns.

Safety message

Accidents involving fuel mismanagement are an ongoing aviation safety concern. In addition to the importance of ensuring there is sufficient fuel prior to, and during, flight, this occurrence reinforces the need to:

  • be fully familiar with the aircraft’s fuel system and capacity
  • conduct a thorough pre-flight inspection, including verification of the fuel quantity
  • ensure the appropriate tank selections are made
  • ensure all aircraft documentation and placarding is up to date and readily available.

This accident and many other previous accidents demonstrate the importance of pilots having knowledge of the aircraft type and its systems, especially when faced with an abnormal situation. Operators, as part of their safety management processes, should provide the opportunity for skill consolidation during and following the initial training on a new aircraft type to reduce safety risk during this transition. This is particularly relevant for types with increased complexity compared to those a pilot has previously flown.

Pilots have a vital role in ensuring maintenance personnel are aware of all aircraft defects to enable prompt rectification and compliance with aviation regulations. This includes documenting aircraft defects on the maintenance release (MR) accurately and without omission. Failing to record defects compromises aircraft airworthiness and safety, placing crew, passengers, and operations at unacceptable risk.

Pilots who perceive serious risks, such as defects not being addressed, management pressure to operate defective aircraft, or being discouraged from documenting defects on the MR, are urged to report these concerns through their organisation’s safety management system (SMS). The SMS is designed to provide a structured and confidential channel for reporting safety issues to enable investigation and resolution.

If internal reporting channels are ineffective or unavailable, pilots are encouraged to report safety concerns confidentially to either the Civil Aviation Safety Authority’s confidential reporting system (Reporting illegal behaviour | Civil Aviation Safety Authority) or the ATSB’s REPCON scheme (REPCON – Aviation Confidential Reporting Scheme | ATSB). These reporting systems ensure the identity of individuals is protected, while enabling critical safety issues to be addressed. Accurate reporting of safety concerns and occurrences is essential to preventing accidents and fostering a strong safety culture.

 

The occurrence

Overview 

On 20 June 2023, a Cessna 310R, registered VH-DAW and operated by Broome Aviation, was being prepared for an instrument flight rules (IFR)[1] air transport operation with a pilot and one passenger from Broome Airport, Western Australia (WA) to Turkey Creek, WA. On the return flight, the pilot planned to stop at Derby Airport to refuel before returning to Broome Airport (Figure 1).

Figure 1: VH-DAW flight plan

Figure 1: VH-DAW flight plan

Source: Google Earth, annotated by the ATSB

Broome to Turkey Creek

At Broome Airport, the pilot completed flight planning, using software provided by the operator. They then completed the pre-flight checks of the aircraft, including visually confirming all 4 fuel tanks (see the section titled Fuel system) were full. The pilot then delivered a safety briefing to the passenger, which included the use of seatbelts, the location of the emergency locator transmitter (ELT) and the first aid kit.

The aircraft departed Broome at 0542 local time. The pilot supplied fuel to both engines from the main fuel tanks for 60 minutes before selecting the auxiliary fuel tanks. They advised that after 30 minutes, they reselected the main tanks and continued to Turkey Creek. 

The pilot indicated that when switching between fuel tanks, they recorded the duration of usage for each tank and calculated the anticipated fuel consumption on a printed flight plan as the operator did not have a formal inflight fuel log. 

The aircraft landed at Turkey Creek at 0744. The pilot shut down the engines and left both fuel selectors on the main tanks position. The pilot did not check the total remaining fuel on the gauges at that time. Both the pilot and the passenger left the runway strip for approximately 6 hours. The pilot recalled being able to see the aircraft from the building in which they were waiting for the passenger to complete their business.

Turkey Creek to Derby

Upon returning to the aircraft, the pilot completed a fuel quantity check by dipping the main tanks with a dipstick. They recalled that the left main tank had 110 L of fuel, which was in line with what they expected (see the section titled Pre-flight fuel plan). However, the right main tank contained only approximately 70 L of fuel. The pilot turned on the aircraft battery to compare the dipstick readings to the fuel gauge readings and reported that both main tank fuel gauge indications correlated with the dipstick readings. Upon checking the auxiliary tank gauges, the pilot noted the right auxiliary tank gauge was indicating full, 40 L more fuel than expected, and the left was indicating as expected. Due to the design of the auxiliary fuel tanks, the amount of fuel contained in the tank can only be visually verified when the tank is full. The pilot stated they did not visually confirm the fuel level in the auxiliary tanks at that time as they assumed both auxiliary tanks had been used during the flight to Turkey Creek. 

The pilot assumed the difference in fuel distribution between the tanks may have been due to an internal fuel leak from the right main tank to the right auxiliary tank, while they were on the ground at Turkey Creek, which they reported had occurred on a previous occasion (see the section titled Main to auxiliary tank fuel leak). However, the pilot was confident there was enough fuel on board, between all 4 fuel tanks, to fly the second leg of the flight to Derby Airport based off an expected 1.5 hour flight time. The pilot used these revised fuel quantity figures for pre-flight fuel planning and filled in the relevant sections of the journey log. At 1333, the pilot started the engines, taxied out to the runway and at about 1339 departed Turkey Creek with the main tanks selected. 

At about 1439, the pilot switched from main fuel tanks to the auxiliary tanks. Approximately 10 minutes later, the pilot changed the fuel tank selection for the left engine to run off the left main tank. The pilot kept the right engine selected to the right auxiliary tank due to the extra 40 L of fuel they had detected during the pre-flight fuel check. Due to belief that they could only draw fuel for 45 minutes from the auxiliary fuel tanks (see the section titled Limited fuel draw from auxiliary tanks), the pilot calculated there was approximately 30 minutes of fuel available for use in the right auxiliary tank.

At about 1454, (15 minutes after they had selected the right auxiliary fuel tank), the right engine began surging. Unsure why they were unable to run the right engine on the right auxiliary tank for longer, the pilot reselected the right main fuel tank, which resolved the surging. The pilot advised that, as the autopilot had difficulty maintaining altitude (see the section titled Autopilot), they selected it to OFF when the engine issues began. Ten minutes later, the right engine began to surge again. The pilot switched back to the right auxiliary fuel tank, however the surging continued. Now at the top of descent for Derby, the pilot deliberated 2 options: shut down the right engine and fly asymmetrically or crossfeed the right engine to the left main tank and run both engines off the left main tank. 

After checking the fuel gauges, the pilot determined there was enough fuel in the left main tank (approximately 45 L) to run both engines to Derby. The pilot then selected the right engine to crossfeed from the left main fuel tank and referred to the quick reference handbook for engine failure in flight checklist to determine a possible cause for the surging. 

Figure 2: VH-DAW flight path

Figure 2: VH-DAW flight path

1. Change from main tanks to auxiliary tanks; 2. Change the left engine from auxiliary tank to main tank; 3. Right engine surge – changed the right engine to right main tank; 4. Right engine surge – crossfeed right engine off left main tank; 5. Inbound call for Derby Airport; 6. Dual engine surge; 7. Mayday call; 8. Accident site. Source: Google Earth, annotated by the ATSB

At 1511, the pilot made an inbound call for Derby Airport on the common traffic advisory frequency. Both engines began surging 3 minutes later. The pilot, assessing they had dual engine fuel starvation, selected the fuel pumps to HIGH and began switching fuel tank selections, searching for any remaining fuel. They advised that after they selected each tank, they waited for a response however, there was no improvement. The pilot advised that the engines did not stop but they could not maintain altitude. 

At 1516:40 the passenger began video recording the flight due to its ‘apparent turbulence’, capturing the engines surging. The recording concluded about 30 seconds later, as the pilot initiated a MAYDAY[2] call to Brisbane Centre air traffic control, stating ‘dual engine failure, suspected engine fuel starvation and I have to put it down on the road’. Brisbane Centre acknowledged the MAYDAY, requested the pilot activate their ELT on landing, and requested details on the number of people on board. The pilot did not respond. 

The pilot alerted the passenger to the emergency and told them to brace for impact. Approximately 30 seconds later, the pilot extended the landing gear and banked into a right turn with the intention of landing on the Derby Highway. However, during the turn the right wing of the aircraft hit a tree causing the aircraft to turn 180⁰ and come to an abrupt stop on the edge of the highway. 

Upon landing, the pilot was temporarily rendered unconscious. The passenger called emergency services and a local passerby stopped to help the pilot and passenger. The passenger recalled the area smelling of fuel when stepping out of the aircraft. 

The pilot sustained serious facial injuries and the passenger sustained minor injuries. The aircraft was substantially damaged. 

Context

Pilot information

Qualifications and experience

The pilot held a commercial pilot licence (aeroplane), issued in December 2020. They also held a multi-engine aircraft (MEA) class rating (issued on 21 June 2021), and an MEA command instrument rating (issued/renewed on 27 August 2021).  

At the time of the accident, the pilot had about 776 hours of total flying experience, with about 613 hours as pilot in command and 43.4 hours as pilot in command of MEA. 

The pilot joined the operator in July 2022, commencing operations on the Cessna 210 (C210). After a period of induction and flying in command under supervision (ICUS), the pilot completed a proficiency check with the substantive[3] head of flying operations (HOFO) (see the section titled Head of flying operations) on the C210 and then commenced passenger air transport operations as pilot in command.

Prior to joining the operator, the pilot had accumulated a total of 37.6 hours on MEA, of which 35 hours were dual day flying and 2.6 hours were dual night flying, completed during the pilot’s initial MEA flight training in 2019. Up until that time, the pilot’s MEA experience had all been gained on the Piper Seminole (PA-44).

In November 2022, the pilot and other pilots from the operator hired an external instructor, at their own expense, to complete instrument proficiency checks (IPCs) on MEA, using VH-DAW. CASA did not require pilots to have a type‑specific endorsement for the Cessna 310 (C310).

By the end of November 2022, the pilot had completed online theory training relating to the basic operation of the C310 and IFR theory, including a Civil Aviation Safety Authority (CASA) MEA questionnaire. On this assessment, the pilot had incorrectly stated the size of the C310 auxiliary tanks (see the section titled Fuel system), and the requirement to use the main tanks for 60 minutes prior to using the auxiliary tanks (see the section titled Fuel management). In mid‑December 2022, when the external instructor visited the organisation for the flight component of the IPC, the instructor assessed the MEA questionnaire using the aircraft’s pilot’s operating handbook (POH). They later advised that they noted the errors, and while they did not correct the answer on the questionnaire, they discussed the correct answers with the pilot.

The pilot’s C310 IPC training included general handling skills, stalls, turns, circuit operations, instrument approaches, asymmetric training, and an outline of how the auxiliary tanks were used. The auxiliary tanks were used for no more than 10 minutes during the first flight. The pilot obtained their IPC on 16 December 2022. The instructor noted that, although fuel management was not explicitly covered during the IPC flights, they had an expectation it would be covered during the organisation’s line training. 

In total, the pilot gained approximately 8.1 hours ICUS on the C310 by the end of December 2022 (Table 1). The pilot then returned to flying the C210 for the operator. 

A check-to-line flight on the C310 was planned to be conducted during a passenger-carrying air transport operation on 21 March 2023, however this flight was cancelled due to a hydraulic malfunction with the aircraft. A shorter, non-air transport operation, check-to-line flight was subsequently conducted by the interim[4] HOFO on 25 March 2023, 130 days after their IPC was issued. The pilot had not flown the C310 in the interim.

The check-to-line flight with the interim HOFO covered various operational aspects, however it was focused on ensuring the pilot was proficient flying under the IFR. The pilot could not recall completing emergency procedures during this flight or using the auxiliary fuel tanks. The pilot was assessed as competent in all areas. At the end of the check-to-line flight, the pilot had accrued 10.5 hours ICUS on the C310.

Table 1: Pilot ICUS hours

DateLocationFlight typeFlight time
12/12/2022Halls Creek → BroomeICUS (air transport operation)2.0
13/12/2022Broome → BroomeICUS (IPC)1.8
14/12/2022Broome → BroomeICUS (IPC)1.9
15/12/2022Broome → BroomeICUS (IPC)1.2
16/12/2022Broome → BroomeICUS (IPC)1.2
25/04/2023Broome → Derby → Broome

ICUS

Check-to-line

2.4

After completing the check-to-line flight, the pilot alternated between operating the C210 and the C310, accumulating 37 hours on the C210 and 43.4 hours on the C310 prior to the accident. At the time of the accident, the pilot had 53.9 hours experience on the C310, including 43.4 hours in the 90 days prior to the accident. 

Recent history

In the 7 days prior to the day of the accident, the pilot completed flights on 14 June (4.6 hours flight time), 15 June (1.9 hours flight time), and 17 June 2023 (5.1 hours flight time). The pilot was rostered off duty on 18 and 19 June. They were within the operator’s flight and duty limitations for maximum cumulative flight and duty times in the 7 days prior to the accident (20 June). 

The pilot reported that, on the evening of 19 June, they retired to bed at 2030, woke up at 0300 and began their pre-flight duties at 0500. The pilot noted that they went to bed earlier than normal, due to the early start time, but could not fall asleep straight away. It is likely they obtained about 5–6 hours of sleep.

The operator’s operations manual[5] detailed that, when starting between 0500–0559, pilots had a maximum available flight duty period (FDP) of 9 hours. Due to the pilot being on the ground at Turkey Creek for 6 hours, the operator reported they had organised a suitable sleeping accommodation for the pilot to allow for a split shift. This arrangement allowed the pilot’s FDP to be extended by 4 hours. The pilot was unaware of this facility, stating the operator had never previously given them suitable sleeping accommodation during a long day shift, only when needing to stay overnight. The pilot reported they waited for the client in an air‑conditioned room and had an adequate amount of food. 

The pilot reported that they felt somewhat rested during the day of the accident flight and recalled that, although they had gone to bed early, they had not fallen asleep straight away. Based on the available information, the ATSB concluded that the early wake-up time and long duty day were problematic but, overall, there was insufficient evidence to conclude that the pilot was experiencing a level of fatigue known to affect performance.

Medical information

The pilot held a class 1 aviation medical certificate that was current to 3 May 2024. This specified a requirement for the pilot to wear distance vision correction. The pilot stated that they did not have any medical concerns or issues in the period prior to the accident.

Aircraft information

The Cessna 310R is a twin-engine, low-wing, 6-seat, unpressurised aircraft equipped with retractable landing gear and powered by 2 Continental IO-520 piston engines. VH-DAW was manufactured in the United States and first registered in Australia in 1975. Broome Aviation became the registration holder on 12 July 2011.

Fuel system

The C310 fuel system consists of 2 sets of fuel tanks in the wings – main and auxiliary, that supply fuel to each engine independently. Two fuel selectors, one for each engine, are installed on the floor between the pilot seats. These allow selection of main fuel, auxiliary fuel, crossfeed and fuel shutoff (Figure 10). The selector allows fuel to flow from the selected fuel tank to the engine‑driven fuel pump for the selected engine. Figure3 shows the layout of the standard fuel system installed in the aircraft.

Figure 3: VH-DAW Fuel System

Figure 3: VH-DAW Fuel System

1. VH‑DAW was fitted with both optional auxiliary tanks, totalling 31.5 US gallons on each side; 2. The aircraft did not have the optional low level fuel light fitted. Source: C310 POH, annotated by the ATSB

Main tanks

The 2 main fuel tanks for the C310 are integrally‑sealed aluminium tanks located on each wing tip. Each main tank holds 189 L (50 United States (US) gallons) of usable fuel, with approximately 7.5 L of unusable fuel. There are 2 fuel pumps in each main tank, the first (auxiliary fuel pump) is used to provide fuel pressure to prime the engine for start or to provide fuel pressure during an engine‑driven fuel pump failure. The second (transfer pump), operates continuously during flight and allows the transfer of fuel from the nose section to the centre section of the main tank, where the fuel outlet is positioned. The transfer pumps are on the same electrical circuit as the left landing light. The main tanks are vented to atmosphere and if overfilled, fuel will be vented overboard through these vents.

Auxiliary tanks

The auxiliary fuel tanks are bladder‑type tanks and are located in the outboard section of each wing. Each auxiliary tank holds 119 L (31.5 US gallons) of usable fuel. The POH stated that fuel could be drawn from the auxiliary tanks during cruise flight only. 

Engine-driven fuel pump

Each engine had an engine‑driven fuel pump that contained a bypass, which continuously returned excess fuel and vapour to their respective main tank.

Fuel management

The POH stated:

If auxiliary fuel tanks are to be used, select main fuel for 60 minutes of flight (with 40-gallon auxiliary tanks) or 90 minutes of flight (with 63-gallon auxiliary tanks). This is necessary to provide space in the main tanks for vapor and fuel returned from the engine-driven fuel pumps when operating on auxiliary fuel. If sufficient space is not available in the main tanks for this diverted fuel, the tanks can overflow through the overboard fuel vents.

It also stated:

Since part of the fuel from the auxiliary tanks is diverted back to the main tanks instead of being consumed by the engines, the auxiliary tanks will run dry sooner than anticipated; however, the main tanks endurance will be increased by the returned fuel. The total usable fuel supply is available during cruise flight only. An engine failure or engine driven fuel pump failure results in the auxiliary fuel on the side of the failure to be unusable.

It was recommended that auxiliary fuel was used until either exhausted or the flight phase had reached the top of descent. When questioned by the ATSB, neither the engine nor aircraft manufacturer could provide a fuel flow rate to calculate how much fuel was being returned to the main tank when the auxiliary tank was selected. The POH also advised ‘operation of the auxiliary fuel tanks near the ground (below 1,000 ft) is not recommended’.

The pilot advised that to simplify fuel management, they routinely used the main tanks for 60 minutes on each segment of a flight before selecting auxiliary tanks. They did not mention the reasoning behind using 60 minutes rather than the expected 90 minutes associated with the larger auxiliary fuel tanks (as fitted to VH‑DAW) detailed in the POH. Other pilots within the organisation who flew the C310 also reported using the 60-minute timeframe.

Fuel flow gauge

The fuel flow gauge indicated the approximate fuel consumption of each engine in pounds per hour. The POH stated that the gauge dial is ‘marked with arc segments corresponding to proper fuel flow for various power settings and is used as a guide to quickly set the mixtures. The gauge has markings for take-off and climb, and cruise power settings for various altitudes.’

The pilot advised that they used the fuel flow gauge while leaning the engines to determine the engines were receiving the appropriate fuel flow and to ensure the flow was stable after changing fuel tanks. The pilot reported that this process was completed during the accident flight on all tank changes.

Fuel quantity gauge

One fuel quantity gauge was located above the right-side control column and indicated the weight of the fuel (in both US gallons and pounds) for the left and right fuel tanks on the display. The gauge showed the fuel quantity for the selected tanks (either main or auxiliary) and the fuel quantity in the non-selected tanks could be displayed through the use of a toggle switch below the gauge. There were also 2 yellow indicator lights (one for each side), these illuminated when the auxiliary tank on the selected side was selected (see Figure 7).

The aircraft was not equipped with the optional independent low fuel warning lights for the main fuel tanks. 

Vortex generators

VH-DAW was fitted with 88 vortex generators located on the wings and vertical fin with additional strakes mounted on the outboard of each engine nacelle. The Supplemental Type Certificate (STC) for this modification included various amendments to the limitations and performance, including reduced stall and VMCA[6] speeds, and allowed for an increased operating weight. 

Site and wreckage

Accident site

The ATSB did not attend the accident site. The site was attended by members of the Western Australia (WA) Police Force on 20 June 2023 and by the aircraft operator the following day. The site inspection was recorded by the police and the video footage was provided to the ATSB, along with photographs taken on the day of the accident (Figure 4).

Figure 4: Accident site

Figure 4: Accident site

Source: Western Australia Police Force

The wreckage was located on the edge of the road in an area of low foliage, approximately 2.8 NM (5.2 km) east-south-east of Derby Airport. The left main tank and right auxiliary tank were ruptured during the accident sequence. 

The left auxiliary tank was reported by the operator as being intact and found to contain about 20 L of fuel, while the right main tank contained negligible amounts of fuel. As both wings displayed visible damage (Figure 5), the ATSB was unable to verify if fuel had leaked from the fuel tanks following the ground collision. The propellers on both engines were not in the feathered position. 

Figure 5: Left and right wing damage

Figure 5: Left and right wing damage

Top image – left wing; bottom image – right wing. Source: Western Australia Police Force, annotated by the ATSB

While reviewing the video footage taken by the police onsite, the left landing light circuit breaker was found to have tripped. The ATSB could not verify if this occurred due to ground impact forces or during the flight. 

The operator arranged for the wreckage to be transported to a non-secure storage area at Broome Airport, which required the wings and one horizontal stabiliser to be separated from the fuselage. 

ATSB examination 

On 30 June 2023, the ATSB examined the wreckage focusing on the aircraft fuel system, particularly the right wing, both auxiliary fuel tanks, and the fuel quantity indicating system (FQIS). Despite the disruption during the accident sequence and transportation, no pre-existing defects or fuel system anomalies were identified. The following key components were retained for further examination and testing:

  • right and left auxiliary interconnect check valves
  • right and left vapour return check valves
  • right fuel selector mains inlet port
  • right fuel selector auxiliary inlet port
  • FQIS indicator and signal conditioner.

Detailed technical examination of these components identified the following defects in 3 components, which likely existed prior to the accident:

  • right fuel selector – main tank inlet valve did not seal when closed (i.e. when not selected ON)
  • the check valve in the right auxiliary tank outlet bleed return line (interconnecting the inboard and outboard fuel cells) did not seal in the reverse flow direction
  • the right vapour return line (engine driven fuel pump to main tank) check valve did not seal in the reverse flow direction.

Testing of the check valve in the right auxiliary tank vent outlet bleed return line in the reverse direction identified a small leak. However, the testing indicated that the leak rate was significantly less than that required to allow fuel to have transferred from the main tank to the auxiliary tank while the aircraft was on the ground at Turkey Creek in the quantities reported by the pilot.

Civil Aviation Safety Authority (CASA) Airworthiness Bulletin (AWB) 28-010 stated that if this valve was leaking, it could allow the engine‑driven fuel pump to draw air into the fuel system resulting in either engine surging or loss of power. It was reported that this is most likely to occur when the auxiliary tank quantity was less than about half full.

The differential pressure applied to the check valve during testing was likely far lower than expected operating pressures. Therefore, it is possible that during engine operation with the auxiliary fuel tank selected, as the fuel quantity reduced, the increased system pressure affected the leak rate and resulted in an increased reverse flow. This may allow the engine driven fuel pump to draw air in sufficient quantity to effect engine performance.

There was no evidence of defects in the auxiliary tank inlet valve of the right fuel selector or the corresponding check valves from the left fuel system. The left fuel selector was not implicated in the occurrence and was therefore not tested.

The FQIS indicator and signal conditioner were not tested or examined due to difficulty finding a facility capable of testing the signal conditioner. Although testing may have established the serviceability status of these individual components, aircraft accident damage prevented operational testing of the whole system. As such, evidence provided by pilots that the FQIS system was not indicating correctly was relied upon (see section titled Fuel gauge displays).

Aircraft maintenance

Maintenance release 

A maintenance release (MR) is required to be carried on an aircraft as an ongoing record of the aircraft’s time-in-service and airworthiness status. The operator’s system of maintenance stated that the MR was valid for 200 hours in service or 12 months from issue, with inspections to be completed at 50, 100, 150 and 200 flight hours. 

A daily inspection was required to be carried out and the MR signed to show the inspection had been completed, prior to the first flight of the day. The inspection and certification could be made by any pilot licenced to fly the aircraft, or an appropriately licenced aircraft maintenance engineer. After the last flight of the day and before the aircraft was next flown, the total daily flight time was required to be entered and the progressive total time in service recorded.

The MR is also used to record any maintenance which is due on the aircraft prior to the next periodic inspection, or any defects[7] detected. 

The last periodic maintenance inspection was carried out on 11 May 2023 at 150 flight hours. At that time the aircraft total time in service was 18,630 hours. The aircraft had flown 30 hours since this inspection with no defects recorded. The only maintenance issue recorded on the MR was a hydraulic leak in the right main brake, which was rectified and signed off by a maintenance engineer on 24 April 2023. 

The ATSB interviewed all 5 pilots who had flown the operator’s C310 during the period from December 2022 to June 2023, as well as other pilots who flew the operator’s C210s. Most of the pilots interviewed stated they were encouraged not to write any defects with aircraft on the MRs. These pilots recounted that if any defects were documented on a MR, they would be reprimanded by the CEO and face a reduction in flight hours on the subsequent roster. 

The pilots also reported that the interim HOFO (see the section titled Head of flying operations) exhibited more willingness for defects to be documented on the MR, however they firstly required assurance that the reported matter was a legitimate defect. The pilots had mixed views on the stance of the substantive HOFO, with 3 noting they had been told not to write defects on the MRs. Two pilots stated they had attempted to implement a ‘snag’ recording system as an alternate method of recording defects, however this was never adopted.

Most pilots advised that, to circumvent what they assessed as a restriction on using the MRs to record defects, they utilised a group chat to communicate specific issues they had encountered on different aircraft in the fleet. They also noted they found it easier to directly communicate with engineers in the maintenance facility if they had any issues after they completed a flight. This approach usually resulted in minor defects getting fixed immediately. 

The substantive HOFO stated they were unaware of any ongoing defects with the operator’s C310 and were unaware of any instances of the CEO reprimanding pilots due to the recording of defects on the MRs. They also stated that, on occasion, pilots deviated from the standard documented procedure for defect reporting (see the following section titled Defect reporting process). 

The interim HOFO also noted that any defects with aircraft in the fleet should have been reported to them and put on the MR, although even if this was not the case then pilots could go straight to the engineers in the maintenance facility to get the matters rectified. In relation to the C310, the HOFO stated the aircraft fuel gauges ‘weren’t fabulous’, however they did not offer an explanation why this was not written up on the MR. They reported being unaware of any other aircraft defects.

The chief engineer advised that all defects would be reported to them by either the HOFO or the CEO using the operator’s defect reporting process. Contrary to the process advised by the pilots, the chief engineer advised that as Broome Air Maintenance was not a part of Broome Aviation, all rectification work had to be requested, and that pilots were not permitted to bypass the request. 

The CEO stated that if there was a defect with an aircraft, they would have expected the pilots to follow the company’s policy regarding defects and write them on the MR. When asked about the C310, the CEO recalled having no knowledge of any defects with the aircraft other than the autopilot not holding altitude. No reason was provided as to why this was not written on the MR. The CEO reported that the fleet were maintained to a high standard and that if a pilot found a defect on an aircraft it would be delt with accordingly. They dismissed the reports they would reprimand pilots for reporting defects, noting they were ‘pedantic’ about maintenance. 

Defect reporting process

The operator’s operations manual outlined a formal process to report deficiencies detected between periodic inspections, which stated:

Line pilots shall report any deficiencies to the [head of flying operations] HOFO, [head of maintenance control] HAMC and CEO via email; verbal or text message notification may be used as a secondary notification method where appropriate or required.

Once an email was received from a pilot, the process required the HOFO to liaise with the HAMC to determine the steps to investigate and rectify the deficiency. The substantive HOFO advised that if a pilot were to call with an issue, if required, the HOFO would tell the pilot to endorse the issue on the MR and then the HOFO would follow up with engineering personnel.  

The chief engineer reported that they did not use the maintenance release to record defects. Rather, if defects were identified either by the operator or by the maintenance organisation, these defects would be rectified and recorded in the aircraft’s Broome Air Maintenance (BAM) worksheets. The ATSB inspected the aircraft logbooks and was unable to identify any unscheduled maintenance. The last unscheduled maintenance recorded in the logbooks was dated 2017.

The interviewed pilots stated that if they detected an aircraft defect, it was easier to talk directly to individual engineers in the maintenance facility, as they were usually in the hangar when returning from a flight and it was more likely to be dealt with.

Reported aircraft issues

The operator’s pilots reported multiple issues with the aircraft to the ATSB, including:

  • inaccurate fuel gauge displays
  • an internal fuel leak from the right main tank to the right auxiliary tank
  • limited fuel draw from the auxiliary tanks
  • engine surging
  • inability of the autopilot to accurately maintain an assigned altitude
  • significant tail flutter. 

During an interview with the ATSB, the chief engineer reported that, to their knowledge, the aircraft was fully serviceable with no issues identified. They also advised they were not aware of the issues raised by the pilots.

Fuel gauge displays

Fuel calibration cards are aircraft specific and used to enable an accurate assessment of fuel quantity. The aircraft’s dual indicating fuel quantity gauge was last tested and calibrated on 24 June 2020. Pilots reported that the main tank calibration card was disregarded as it was considered inaccurate. 

There was no fuel calibration card relating to the auxiliary tanks. The ATSB was unable to confirm if the auxiliary tank calibration had occurred as there was no record in the maintenance worksheets or the aircraft logbook of the results. There was no regulatory requirement to record the results of a fuel gauge calibration test.  

The next due date to test and recalibrate the fuel gauges was expected to be in June 2024 in compliance with the CASA Civil Aviation Order (CAO) 100.5 General requirements in respect of maintenance of Australian Aircraft – 2011 and the operator’s system of maintenance. 

Pilots who operated the aircraft reported that the fuel gauges displayed significant inaccuracies when the tanks were full. Specifically, when the main tanks were full, the right main tank display would exceed full scale deflection, while the left main tank display would under‑read by approximately 64 L (105 lbs) (Figure 6). 

Figure 6: VH-DAW main tank fuel gauges

Figure 6: VH-DAW main tank fuel gauges

Left image – expected fuel gauge indications for main tanks when full; right image – the reported fuel gauge indications for main tanks when full. Source: Braden Blennerhassett (Air Manager), edited by the ATSB

It was reported that, as fuel was used during the fight, the displays became progressively more accurate, however there was still a large discrepancy between the displays (Figure 7). The expectation was that, when the fuel tank selection was changed from main to auxiliary or vice versa, both sides would be changed at the same time.

Figure 7: VH-DAW main tank fuel gauge indications after supplying the engines for the same time

Figure 7: VH-DAW main tank fuel gauge indications after supplying the engines for the same time

Both the left and right main tanks had been used for the same amount of time during the flight. Source: Pilot of VH-DAW, annotated by the ATSB

It was reported that when the gauge was selected to the auxiliary tank display, there was also a discrepancy when the tanks were full, although the difference was not as significant as that observed with the main tank display. It was reported that the display for the left auxiliary tank under‑read by approximately 9 L (15 lb), while the display for the right auxiliary tank under‑read by approximately 36 L (60 lb) (Figure 8). Pilots did not indicate that the accuracy of the auxiliary tank gauge displays improved during use. However, it was noted that the auxiliary tanks were never used below about 12 L.

Figure 8: VH-DAW auxiliary tank fuel gauges

Figure 8: VH-DAW auxiliary tank fuel gauges

Left image – expected fuel gauge display for auxiliary tanks when full; right image – reported fuel gauge display for auxiliary tanks when full. Source: Braden Blennerhassett (Air Manager), edited by the ATSB

The fuel gauge inaccuracy was reported to be widely known by pilots and informally reported to individual engineers in the maintenance facility, however the defect was not recorded on the aircraft’s MR. Pilots reported that maintenance personnel informed them that the external organisation capable of fixing the gauges indicated that new sensors were needed, and that the process of fixing the gauge was lengthy and the necessary parts were costly and so it was unlikely it would be completed. The CEO stated they were unaware of any issues with the fuel gauges.  

The pilots advised that they adopted a time-based approach to track the amount of fuel in each tank during flight, noting there was no other guidance from the interim HOFO or senior management on how to manage the fuel quantity. Pilots stated that the most accurate way to ensure the known quantity of fuel on board prior to take-off was to depart Broome with full main and auxiliary tanks and, where possible, fill the main tanks to full when flying intermediate sectors.  

The aircraft minimum equipment list (MEL) allowed 1 display on the gauge to be inoperative[8] providing a reliable means was established to ensure that the fuel quantity on board met the requirements for the intended flight.

Main to auxiliary tank fuel leak

The pilot of the accident flight and the supervisor of their first ICUS flight reported there were occasional instances where, having been fully refuelled, the right main tank would be missing approximately 10–30 L of fuel the following day. They further advised that when this occurred, the right auxiliary tank would overflow when the fuel cap was removed (Figure 9). This led the pilots to suspect a fuel leak between the right main and auxiliary tanks.

Figure 9: Auxiliary fuel tank overflowing on morning inspection

Figure 9: Auxiliary fuel tank overflowing on morning inspection

Source: Previous operator pilot, annotated by the ATSB

This issue was informally reported to maintenance staff, but not recorded on the MR. The CEO reported being unaware of the issue. After the initial report, the reporting pilot noted that engineers in the maintenance facility were unable to identify a fuel leak. Although the issue reportedly recurred, it was not further reported.

Limited fuel draw from auxiliary tanks

The pilot of the accident flight stated that the auxiliary fuel tanks could only supply the engines for 40–45 minutes before surging occurred. They noted that their initial understanding of the limited fuel draw came from the supervisor of their first ICUS flight. They further advised observing this limitation on their first solo passenger-carrying flight in the aircraft.

This issue was informally reported to individual engineers in the maintenance facility by the supervising pilot, and they recalled that maintenance was unable to identify a cause. The pilot of the accident flight assumed that since the issue had been reported previously, it had been addressed by maintenance. However, both the CEO and the chief engineer advised being unaware of the issue. 

Other pilots stated that around the 40-minute mark while using auxiliary tanks, the aircraft’s engines would lightly surge before regaining power. They would then continue to use the fuel from the auxiliary tanks until about 12 L remained, before changing to the main tanks. The HOFO reported there were no issues when using the auxiliary tanks. 

Engine surging

Multiple pilots recalled that the engines would surge during flight. The pilot of the accident flight and one other pilot noted the surging generally occurred when operating on auxiliary tanks, which they attributed to the limited fuel draw issue. 

Other pilots also recalled the engines surging however, they could not confirm which tanks were selected at the time. These surges were described as minor and intermittent, typically ceasing after a few seconds and did not require the fuel pumps to be selected ON.

The engine surging had been reported to individual engineers in the maintenance facility verbally and had not been documented on the MR. Both the CEO and the chief engineer advised that they were unaware of this issue. 

Autopilot altitude hold

According to pilots who operated VH-DAW, the aircraft’s autopilot maintained an accurate heading, however, despite pre-flight testing of the system reportedly consistently indicating that the autopilot was fully operational, it could not maintain an assigned altitude. There was no evidence or record that this issue was formally or informally reported to the engineers in the maintenance facility, and the chief engineer advised not being aware of the issue. However, the issue was known to the organisation’s CEO, at the time of the occurrence.

An autopilot was considered inoperative if it was unable to maintain both altitude and heading. The aircraft MEL allowed continued operation with the autopilot inoperative under any one of the following conditions:

  • if flight was operated under IFR rules for RPT, charter[9] or aerial work, the aircraft was equipped with dual controls and had 2 control seats, with one control seat occupied by the pilot in command of the aeroplane and the other seat occupied by a person holding a commercial pilot (aeroplane) licence with an endorsement on the aircraft and an instrument rating
  • if the flight was operated under IFR rules with a single pilot for RPT, charter or aerial work, the flight was within the period of 3 days commencing on the day on which the autopilot became inoperative provided only one capability of the autopilot system was unserviceable
  • the flight was operated under VFR rules
  • the flight was operated for a private flight.

Elevator flutter

Pilots reported the presence of a known elevator flutter[10] on the aircraft, which was attributed to the installation of vortex generators on the elevator. This flutter resulted in challenging handling characteristics at low speeds, particularly during take-off and landing. 

The engineers in the maintenance facility had conducted an extensive investigation into the issue in 2018, including the removal and reinstallation of the vortex generators. They concluded that the flutter did not impose stress on the airframe, and the aircraft was returned to service on 13 August 2018. The vibration defect was raised again on the MR on 20 October 2022 and cleared by maintenance personnel on 4 November 2022. There was no information regarding what was completed during the November sign‑off. The pilot of the accident flight stated that the elevator flutter was still present, although not noted on the accident flight.  

Aircraft placarding

The fuel selectors had plaques stating the amount of fuel in each tank in US gallons. On inspection, it was noted that the auxiliary tank capacity for both sides incorrectly indicated that small auxiliary tanks (20 US gallons) were fitted to the aircraft (Figure 10). 

Figure 10: VH-DAW fuel selector plaques

Figure 10: VH-DAW fuel selector plaques

Source: Operator, annotated by the ATSB

This contradicted the usable fuel decals next to each filler cap on the airframe, which identified that the auxiliary tanks held 119 litres (31.5 US gallons) (Figure 11). 

Figure 11: VH-DAW fuel decals

Figure 11: VH-DAW fuel decals

Source: ATSB

Just above the fuel selector plaques, there was a requirement for a plaque specifying how long to operate on the main tanks when first taking off with full tanks. For a C310 with the larger auxiliary tanks, the plaque was required to include:

Use main tanks for takeoff, landing and first 90 minutes of flight.

This plaque was missing from the aircraft (Figure 12). 

Figure 12: VH-DAW internal placards relating to the fuel system

Figure 12: VH-DAW internal placards relating to the fuel system

Top image – VH-DAW internal fuel placarding; bottom image – exemplar internal fuel placarding. Source: Top image – ATSB; bottom image – Textron, annotated by the ATSB

All aircraft placarding was required to be checked under the aircraft system of maintenance every 200 hours for security, presence and legibility. There was no requirement to check the validity of the information presented on the placards. The aircraft had five 200‑hourly maintenance events in the last 5 years, the last being August 2022. 

The fuel selector placards had last been replaced on 24 October 2008, prior to the aircraft being registered to Broome Aviation. The installed placards were the incorrect part number and as such displayed the incorrect size of the auxiliary tanks. The ATSB was unable to determine if the plaque relating to the 90 minutes on mains had been removed previously or never installed. 

The pilot of the accident flight was unaware that any of the plaques were incorrect, noting that they had not discussed it with the instrument proficiency check (IPC) instructor (see the section titled Qualifications and experience) or HOFO. 

Fuel management

Pre-flight fuel plan

The flight plan used by the pilot on the day of the occurrence was destroyed during the accident and was not recorded by the operator’s planning software. During the draft report review process the pilot advised that they had recently found a copy of the flight plan, which they provided to the ATSB. The plan (Figure 13), generated by the flight planning software, showed a zero fuel margin. The pilot stated that they did not input the expected winds for the flight as they were unaware how to. Additionally, they recalled that all their previous flight planning had been conducted with nil wind. 

Figure 13: Accident flight fuel plan

Figure 13: Accident flight fuel plan

Source: The accident pilot

A pre-flight fuel plan was created using the operator’s software (Figure 14). The flight plan software used a 120 L/h fuel burn for cruise and 150 L/h for climb. These figures were extracted from the POH performance tables using the typical operating conditions encountered for different phases of flight when flying out of Broome Airport.[11]

The known winds on the day of the occurrence were used. The fuel plan showed that the aircraft could not legally fly with the required reserves on the return flight to Derby.

Figure 14: Example fuel plan based off reported winds for each sector of the occurrence flight

Figure 14: Example fuel plan based off reported winds for each sector of the occurrence flight

Trip T – Trip total less taxi fuel; Contin – Contingency fuel (15% of expected trip total); F. Reserve – Fixed reserve; Fuel R – Fuel required for next leg including contingency and fixed reserve; Margin – Endurance subtracting fuel required; Endce – Endurance. Source: Operator, annotated by the ATSB

The ATSB also generated a fuel plan based on the pilot’s understanding of the amount of fuel they could use from the auxiliary tanks. The analysis used:

  • the flight times calculated by the operator’s software
  • the pilot’s standard use of 40 minutes from the auxiliary tanks
  • 1.5 x fuel burn rate[12] – the extra fuel was diverted to the main tanks.

This resulted in approximately 120 L of fuel being available for use from the auxiliary tanks (40 L plus the redraw of 20 L = 60 L from each auxiliary tank). Therefore, the pilot’s perceived total available fuel onboard when all tanks were full was 498 L (main tanks 378 L + auxiliary tanks 120 L). As shown in Table 2, such a plan indicated there was insufficient fuel onboard to conduct the flight without fuel starvation. 

Table 2: Fuel calculation comparison

 ATSB calculated Leg 1ATSB calculated Leg 2
Start fuel498 L241L
Trip fuel (climb + cruise + taxi)257 L251 L
Expected remaining fuel onboard at destination241 L-10 L
Contingency fuel37 L36 L
Fixed fuel reserve90 L90 L
Fuel margin114 L-136 L

A previous pilot of the C310 indicated that when flying the same route, on the return leg they would refuel the aircraft at Halls Creek, another base for the operator, as it was 77 NM south-west of Turkey Creek. They would then fly directly from Halls Creek to Broome. This flight route ensured they had enough fuel to complete the flight with reserves intact.

Previous flight

The pilot recalled completing the same flight 4 weeks prior to the occurrence. They stated that they had landed at Derby and refuelled the aircraft for the final leg back to Broome. A retrospective fuel log was created using the known winds on that day and the pilot’s reported timing of the fuel tank changes (Table 3). The ATSB also calculated the average fuel burn for the aircraft during this flight using the fuel added to refuel the aircraft to full after the flight which showed the aircraft used an average of 124 L/h.

The operator’s standard 12 L taxi fuel was used for the first leg of the flight. Due to the prevailing wind, the first leg from Broome to Turkey Creek was recorded as having a duration of 126 minutes, requiring the pilot to use the auxiliary tanks for 40 minutes (66 L draw from auxiliary tanks and 22 L returned to the main tanks on both sides). 

The flight time from Turkey Creek to Derby was recorded as 90 minutes. Due to the assumed auxiliary tank issue and having used the auxiliary tanks for 40 minutes on the first leg, the pilot would have likely used main tanks for the entire leg. It is highly probable that the pilot landed at Derby with 21 L of useable fuel remaining in each of the main tanks, equating to about 15 minutes of remaining engine operation before fuel exhaustion. 

Table 3: Retrospective fuel log of previous flight Broome – Turkey Creek – Derby on 25 May 2024 

FUEL LOG

Broome – Turkey Creek

Phase

Left

Right

AuxiliaryMainMainAuxiliary
Taxi Broome119189189119
Departure Broome119183183119
Change to auxiliary tanks119123123119
Change to main tanks5914314359
Estimated fuel on landing5911711759

Turkey Creek – Derby

Taxi Turkey Creek5911711759
Departure Turkey Creek5911111159
Estimated fuel on landing59212159

Fuel quantity analysis of the accident flight

The ATSB obtained flight data that was transmitted at regular intervals from a V2 Flight Tracker, which had been installed on the aircraft. A retrospective fuel log for the Turkey Creek to Derby leg (Table 4) was created using:

  • the pilot’s recalled amount of fuel in each tank on startup
  • the pilot’s recollection of when they completed tank changes
  • the operator’s average fuel consumption rate of 120 L/h
  • a conservative estimate of fuel return (0.5 multiplier) to the main tanks when using auxiliary tanks
  • a conservative estimate of fuel draw from the left main tank (2.5 multiplier) and return to the right main tank (0.5 multiplier) when cross feeding the right engine.

As such, it is only indicative of the fuel on board in each tank at each change of tank and at the time of the dual engine surging. 

Table 4: Retrospective fuel log of remaining fuel in aircraft from Turkey Creek to the point of the dual engine surge using 120 L/h

FUEL LOG

Turkey Creek – Dual engine surge

Phase

Left

Right

AuxiliaryMainMainAuxiliary
1336:  Taxi Turkey Creek (used 6 L each side)7411070119
1339:  Departure Turkey Creek7410767119
1439:  Change to auxiliary tanks74444119
1449:  Change left auxiliary to main tank5949 (44+5)9 (4+5)104
1454:  Change right auxiliary to main tank594412 (9+3)97
1504:  Cross feed left main tank5934297
1514:  Dual engine surging5997 (2+5)97

At the point of dual engine surge, it is estimated that the left main tank had approximately 9 L of fuel remaining.

The aircraft manufacturer stated that if the engines were surging while on the main tanks and there were no other issues with the fuel system and fuel available in the auxiliary tanks, the pilot should have been able to use the remaining fuel in the auxiliary tanks to regain full power. At the point of the dual engine surge, the left auxiliary tank had approximately 59 L and the right had approximately 97 L available. 

The same calculations were completed using the pilot’s average fuel consumption rate of 124 L/h (see the section titledOperator fuel flow check). Those calculations (Table 5) indicated that about 6 L of fuel remained in the left main fuel tank (supplying both engines) at the point of the dual engine surging.

Table 5: Retrospective fuel log of remaining fuel in aircraft from Turkey Creek to dual engine surge using the pilot’s average 124 L/h

FUEL LOG Turkey Creek – Dual engine surge

Phase

Left

Right

AuxiliaryMainMainAuxiliary
1336:  Taxi Turkey Creek (used 6 L each side)7311070119
1339:  Departure Turkey Creek7310464119
1439:  Change to auxiliary tanks73422119
1449:  Change left auxiliary to main tank5848 (42+6)8 (2+6)104
1454:  Change right auxiliary to main tank584210 (8+2)96
1504:  Crossfeed left main tank5832196
1514:  Dual engine surging5865 (1+4)96
Operator fuel planning requirements

Pre-flight

The operator’s procedures required the pilot to complete pre-flight fuel planning using the available electronic flight planning software. However, if the flight planning software was not available, the pilots were required to calculate the fuel required for the flight using the fuel flow guidelines for the aircraft. 

The operations manual outlined the fuel figures, specific to the C310, to be used when manually completing fuel planning. The guidelines did not contain a fuel flow rate for climb. However, they did include a block (total) fuel margin of 47 L which was to be available for each sector. The operator advised they were not aware of where the margin of 47 L figure had originated from. The electronic flight planning software did not include this 47 L margin fuel when calculating fuel requirements. 

To confirm the amount of fuel on board prior to flight, the operator’s fuel policy required pilots to visually confirm the fuel quantity in each tank using a dip or drip stick when possible, then compare this to the flight plan and fuel gauges. If there was a discrepancy more than an allowable margin with the fuel gauges the pilots were required to inform the HAMC and/or HOFO to determine the possible cause. The allowable margin quantity was not listed in the operator’s fuel policy. 

Inflight

The operator’s procedures required pilots to recalculate fuel in flight at 2 specific points:

  • when reaching cruise
  • if required to divert.

The procedures outlined that once reaching cruise altitude pilots should: 

calculate the remaining quantity of fuel on board for the proposed destination. This must be equal to or above the legal minimum final reserve quantity. If this is not the case, consider using more conservative fuel power settings, change cruise level for more favourable winds or divert to an alternative. 

The procedure did not stipulate if this calculation was required to be recorded on any documentation, nor did it outline any requirement for a fuel crosscheck. Additionally, the operator did not have a fuel log or method of monitoring fuel during the flight.

If the pilot was required to divert, inflight fuel replanning was to be carried out using the fuel flow guidelines for the aircraft. 

A previous pilot for the operator stated there was no standardised method of completing inflight fuel logs and it was based on pilot preference. They further reported a ‘feeling’ that the organisation had not had any fuel starvation events due to ‘luck’.

Post-flight

The operator’s procedures recommended that pilots conduct a fuel gauge check against the value on the fuel totaliser at the completion of a flight. However, the operator stated that none of its aircraft were fitted with a fuel totaliser. Additionally, the quantity of fuel used was to be checked against the expected burn from the flight plan. 

Pilots were required to complete the fuel documentation, including recording on the journey log and manifest the amount of fuel at shutdown. The manifest did not provide the option to indicate the remaining fuel in each tank. 

Operator fuel flow check

The operator reported that pilots were required to enter the amount of fuel consumed and flight time after each flight into the organisation’s data recording software. The program created a monthly report, which outlined the fuel flow rate for each flight, segregated by aircraft.

The substantive HOFO used this information to determine the average fuel flow for each aircraft, and which pilot completed each flight. If there was an unexpected trend for a particular pilot, the substantive HOFO would use this to discuss how the pilot was configuring the aircraft’s fuel system during flight. If the trend was over multiple pilots, the HOFO would liaise with maintenance to determine the cause.

The substantive HOFO noted there was no indication that the aircraft was burning more than the expected 120 L/h however, they could not confirm if this process was being completed by the interim HOFO while they were on leave. ATSB analysis of the pilot’s flight times and fuel uplift over the previous 10 flights indicated the aircraft was using 124 L/h on average. 

Regulatory requirements

Pre-flight fuel planning

According to Civil Aviation Safety Regulation (CASR) Part 135 Australian air transport operations – smaller aeroplanes section 135.205 operators are required to provide pilots with an exposition which provides comprehensive tools, procedures, and guidance for effective pre-flight fuel planning. The exposition must outline step-by-step instructions for calculating fuel requirements to ensure compliance with Australian regulations and operational safety.

According to CASR Part 135.D.6 and the Manual of standards (MOS) Part 135 7.04, pilots must have access to resources for determining fuel needs for each phase of the flight, including:

  • taxi fuel
  • trip fuel
  • holding fuel
  • destination alternate fuel
  • contingency fuel
  • final reserve fuel

There should also be a process outlining:

  • fuel calculations
  • determining and recording fuel quantities – pre-flight
  • recording fuel quantities.

To support these calculations, operators must provide tools such as flight planning software, fuel calculation tables, or automated planning systems. Operators are also responsible for ensuring that pilots are trained to use these resources effectively and can adjust their fuel requirements based on dynamic operational factors, such as deteriorating weather or delays.

Part 135 manual of standards (MOS) Section 7.03 (2) required that the pilot in command must consider the effect of the relevant meteorological reports and forecasts when determining the quantity of useable fuel.

In-flight fuel management

The Part 135 MOS Section 7.05 (2) required that the exposition outline a process for regular inflight fuel checks, which required the pilot to:

  • determine the amount of fuel remaining
  • analyse planned fuel consumption against actual consumption
  • determine there is sufficient fuel on board
  • calculate the amount of fuel expected to remain at the destination. 

According to the CASA Advisory circular 1-02 V4.1 Exposition and operations manual fuel policy guidance Annex D, the exposition should detail what maximum discrepancy between the actual fuel on board (gauge / visual) and calculated (journey log) figure is tolerable, noting that industry practice is a maximum of 3% discrepancy.

Part 135 MOS section 7.03 required that operators must provide pilots with aircraft‑specific fuel consumption. This could be sourced from the aircraft/engine manufacturer or taken from recent historical consumption records. Operators should also require pilots to document any significant deviations in fuel consumption or incidents involving fuel advisories or emergencies. This data enables operators to analyse and improve fuel planning and management procedures. 

In addition, Part 135 MOS section 7.06 required that operators must also ensure that the exposition outlines clear procedures for pilots to follow in the event of a low-fuel situation, including:

  • a minimum fuel state
  • emergency fuel situation.

Finally, operators should regularly review and update their operational manuals to reflect lessons learned from safety reports and audits, ensuring continuous improvement in fuel management practices.

Operator requirements for training, experience and consolidation on new aircraft types

Induction and minimum qualifications

The operator’s operations manual stated that recruited pilots were to meet the following minimum requirements:

  • commercial pilot licence with no medical restrictions[13]
  • current Australian medical certificate
  • pass of a pre-employment check flight with the HOFO or a delegate.

Once inducted, a new pilot would learn the routes with existing pilots before being checked to line by the HOFO. 

The operator’s operations manual stipulated 5 minimum requirements for a pilot in command of the C310 (Table 6).

Table 6: Operator’s 5 minimum requirements for operating the C310

Requirement numberMinimum requirements
15 hours on type for VFR operation
210 hours on type for IFR operation
3Minimum of 750 total flying hours
4Minimum 20 hours in command on MEA for VFR operation
5A multi engine command instrument rating if flying IFR.

The HOFO was required to conduct a check-to-line flight and, if successful, the pilot would be cleared to conduct air transport operations as pilot in command on the new type. The substantive HOFO stated that generally it would be expected that multiple ICUS flights would occur with either the HOFO or a supervisory pilot before a check-to-line would be conducted. The CEO reported that generally 15–20 hours on type would be sufficient to conduct line operations as pilot in command. 

During the draft review process, the CEO reported that the calibre of pilots coming through from flight schools was lower than previously experienced, noting that a lot of the organisation’s time was spent getting pilots up to commercial standard.

After completing the check-to-line flight, the pilot of the accident flight had accrued a total flying time of 740.5 hours. The operator received an exemption from the operator’s insurer for the pilot to undertake air transport operations in the C310 without meeting the specified minimum requirement of 750 hours. 

Under CASR 61.650, pilots were required to have completed an IPC in the previous 12 months to fly a multi-engine aircraft under the IFR. The IPC must also be done in a multi-engine aircraft of the same category. The substantive HOFO noted that, once a pilot was checked to line, there was no follow up or specific oversight on their operating capabilities until their next proficiency check in 12 months, in line with the CASR requirements and the operations manual, which stated:

If flying under the IFR, pilots are required to conduct an Instrument Proficiency Check with an authorised Flight Examiner prior to one (1) year from the last day of the month in which it was issued (IFR operations).

There were no specific regulatory requirements for Broome Aviation to provide additional consolidation flights for pilots transitioning to the C310 as, at the time of the accident, the operator was operating under CASA exemption 87/21.[14] 

In December 2021, Civil Aviation Safety Regulation (CASR) Part 135 (Australian air transport operations – smaller aeroplanes) commenced. It introduced more stringent requirements for flight crew training and checking for operators conducting air transport operations. However, operators could operate under the exemption that applied to a significant proportion of the previous small charter sector. This meant the operator was not required to conduct line training, a check-to-line, or complete proficiency checks, other than to ensure those proficiency checks and flight reviews mandated by Part 61 of CASR were carried out on their flight crew members.

Supervisory pilots

The CASA‑AMC/GM Part 119 - Australian air transport operators - certification and management v 2.3 noted that some operators have diverse fleets and there are scenarios where the HOFO may not be qualified on every aircraft type or in every role/function performed under its air operator’s certificate (AOC). In this case, operators can elect to use a structure where another pilot is identified to complete that position. In the case of Broome Aviation, the substantive HOFO conducted the check and training for the C210, in addition to nominated supervisory pilots, but for the MEA this position was covered by supervisory pilots. The operator required that supervisory pilots had:

  • a minimum of 20 hours total time on type
  • completed training with the HOFO or nominated person (with such training including the use of the line training and check forms)
  • met the relevant recency or proficiency requirements to act as pilot in command
  • been nominated, in writing, by the operator to be supervisory pilot and recorded as a named supervisory pilot.

The operator’s supervisory pilot register had not been updated since 1 December 2021. The register contained the name of one pilot who had been approved to conduct supervisory flights for the C310, however this pilot left the operator while the substantive HOFO was on leave. A second pilot had been listed as a supervisory pilot for the C210. The substantive HOFO stated that the second pilot had been assessed to conduct supervisory flights for the C310, however the register had not been updated to include this information. This pilot (detailed below as ‘Pilot 1’) also left the operator while the substantive HOFO was on leave.

During the period between December 2022 and June 2023, 7 pilots flew the operator’s C310, including one who had completed the training but had not been checked to line. Multiple pilots stated that training and guidance on the C310 during this period was limited. Of the 7 pilots:

  • Pilot 1 – was a senior pilot for the operator who was signed off as a supervisory pilot for the C310. They conducted the check-to-line for Pilot 2. Pilot 1 left the operator at the end of December 2022 and returned for 3 weeks at the end of February 2023.
  • Pilot 2 – completed no ICUS flights prior to completing a check-to-line flight in November 2022 that lasted 1.1 hours. The pilot was not formally signed off as a supervisory pilot on the C310, although they had extensive instructional time on MEA, prior to assisting with ICUS flights. The pilot left the operator at the end of February 2023.
  • Pilot 3 – completed 2 ICUS flights, one with the interim HOFO (3.7 hours) and 1 with Pilot 2 (1.6 hours), before completing a check-to-line (1.5 hours) with the interim HOFO a week later in February 2023. The pilot left the operator at the end of March 2023.
  • Pilot 4 (pilot of the accident flight) – completed 1 ICUS flight with Pilot 2 and 4 IPC flights with the external instructor on the aircraft. They were subsequently checked to line in April 2023, 130 days after their last flight in the aircraft, by the interim HOFO.
  • Pilot 5 – completed 3 IPC flights with the external instructor and completed no ICUS flights. They were checked to line in May 2023, 162 days after their last flight in the aircraft, by the interim HOFO.
  • Pilot 6 – completed 3 IPC flights with the external instructor and had not completed any ICUS flights since.
  • Pilot 7 (interim HOFO) – completed their check-to-line with Pilot 1 (3.6 hours) in December 2022 and completed 1 IPC flight with the external instructor.

At the time of their check-to-line, multiple pilots who conducted C310 operations for the operator during the period from November 2022 to June 2023, did not meet the operator’s minimum requirements 1, 2 and 3 detailed in Table 7. All pilots met requirements 4 and 5. The pilot of the accident flight and Pilot 5 both had limited experience flying MEA (under 50 hours), having not flown another MEA type outside of flight training. 

Table 7: Compliance with operator’s minimum requirements on the C310 at the time of check-to-line

PilotMinimum 5 hours on type for VFR operationMinimum 10 hours on type for IFR operationMinimum of 750 total flying hours
Pilot 2NoNoYes
Pilot 3YesNoYes
Pilot 4 (pilot of the accident flight)YesYesNo
Pilot 5YesNoNo
Pilot 7 (Interim HOFO)NoNoYes

Pilot 1 was excluded as their check-to-line was completed prior to November 2022. Pilot 6 was excluded as they had not completed a check-to-line for the operator.

Multiple pilots reported that they had limited training on the C310 and anticipated completing additional ICUS flights before being checked to line. Three pilots assessed that they were tasked with operating the aircraft without adequate training on the fuel system. They expressed concerns about the limited training noting the C310 had a complex fuel system. Multiple pilots reported learning the systems while conducting operational flights.

Emergency procedures

The POH included emergency procedures for inflight engine failure, which included a requirement to check:

  • fuel flow rate
  • fuel selector positions
  • fuel quantity. 

After the second surging event on the right engine, the pilot crossfed the left main tank to the right engine and referred to the quick reference handbook. This handbook outlined the ‘engine failure during flight’ checklist. The pilot stated that they referred to the checklist to determine whether any actions could be taken to address the surging, noting that the engine had not completely failed. There was no checklist to address engine surging. 

At this point in the flight, the aircraft was located between 2 nearby diversion airstrips of Kimberley Downs Station, located approximately 5 NM to the south‑east, and Meda Station located approximately 16 NM west (Figure 15). The pilot noted they were familiar with the location of the airstrips, however they had never operated from them and were unaware on their suitability and condition. The pilot stated that because of these unknowns that they believed the only suitable airstrip was Derby Airport. 

Figure 15: Diversion locations

Figure 15: Diversion locations

The pilot did not consider diverting to RAAF Base Curtin. Source: Google Earth, annotated by the ATSB

The flight data indicated that the pilot initiated their descent from 10,000 ft at the normal top of descent position, while continuing to track towards Derby Airport, at an average descent rate of 400 ft/min. Approximately 3 minutes into this descent, the pilot crossfed the right engine from the left main tank. 

Engine surging

When surging occurred in both engines, the pilot noted that it appeared to be from fuel starvation. The aircraft manufacturer noted that in the event of simultaneous engine power losses or surging, the engine ’Airstart’ checklist could be actioned twice, as only one engine should be restarted at a time. Additionally, the ‘FORCED LANDINGS (Complete Power Loss)’ checklist should be used if pilots were unable to regain power. 

The pilot continued tracking to Derby Airport while switching fuel tanks, attempting to draw any remaining fuel. The manufacturer noted that the certification rule, at the time of the aircraft’s certification, required multi-engine aircraft to regain full power and fuel pressure within 20 seconds after switching from an empty tank to a full tank in level flight. The aircraft tracking data indicated that at an altitude of approximately 4,500 ft the descent rate increased to 1,500 ft/min. The aircraft travelled approximately a further 5.5 NM over approximately 3 minutes before a forced landing was conducted (Figure 16). 

Figure 16: Aircraft altitude variation with distance to Derby Airport 

Figure 16: Aircraft altitude variation with distance to Derby Airport

4. Right engine surge – crossfeed right engine off left main tank; 5. Inbound call for Derby Airport; 6. Dual engine surge; 7. Mayday call; 8. Accident site. Source: ATSB

When the pilot determined they would be conducting a forced landing, they declared a MAYDAY to ATC. The aircraft was at an altitude of approximately 700 ft. The pilot later advised they had insufficient time to complete any checklist items after the MAYDAY call, however they lowered the landing gear as they were aiming to land on the Derby Highway as it was assessed as the best available option. There were approximately 30 seconds between the MAYDAY transmission and the forced landing.

Survivability

Safety briefing

The operator had a safety briefing video for the C310. The video outlined the:

  • use of:
    • doors
    • seatbelts
    • emergency exits
  • location of:
    • life vests
    • safety briefing card
    • emergency supplies
    • installed emergency locator transmitter (ELT)

The pilot noted there were 2 main differences between the aircraft and the information in the video. The location of the emergency supplies was in the nose of the aircraft rather than the wing cargo locker, and the ELT was portable rather than installed (see the section below titled Emergency locator transmitter).

This was the second time the passenger had flown in VH-DAW with the pilot. The passenger noted that on the first time flying in the aircraft they were shown a safety briefing video. On this occasion they were not shown the video and instead were given a briefing while at the aircraft. They recalled the briefing outlined the information regarding the emergency exits and seatbelts, noting there were other topics covered that they could not recall. The passenger recalled that they did not read the safety card while in the aircraft as they flew frequently. The safety card contained information on how to adopt the brace position.

When the passenger was asked to brace by the pilot, they stated they were unsure how to brace properly in the aircraft and reverted to their knowledge of the brace position for larger commercial aircraft. 

Seatbelts and upper torso restraints

The pilot seat was fitted with a lap belt and upper torso restraint (UTR),[15] consistent with the regulatory requirements. The pilot stated that they would not wear the UTR portion of the harness during cruise as it limited their ability to view the gauges on the opposite side of the cockpit. The UTR was only worn during take-off and landing. The pilot stated that during the emergency, they did not put on the UTR. The pilot sustained severe facial injuries and a loss of consciousness when the aircraft collided with terrain.

The passenger’s seat was fitted with a lap belt. This was worn by the passenger during the emergency and forced landing. The passenger received minor injuries, including bruising around the abdomen due to the lap belt.

Emergency locator transmitter

The aircraft was fitted with a portable emergency locator transmitter (ELT).[16] The pilot recalled that on first flying the aircraft they had checked the expiry date of the ELT and noted it was out of date. The portable ELT was subsequently replaced prior to the aircraft’s next flight. 

The safety briefing video showed an automatic installed ELT[17] within the aircraft. The pilot noted that during pre-flight briefing with the passenger they explained the location of the ELT was different to the safety briefing video, however they did not explain the process to activate it. 

The CASR Part 135 MOS required aircraft that were flown more than 50 NM from the departure aerodrome to carry an automatic ELT. However, this requirement was not applicable to the aircraft until 2 December 2023. Prior to then, the aircraft was operating under regulation 252A of the Civil Aviation Regulations, and subsection 6 of Civil Aviation Order 20.11, which permitted either a portable ELT or an installed ELT in the aircraft.

Due to the pilot being rendered unconscious during the accident sequence, the portable ELT was not activated. The passenger contacted emergency services while still in the aircraft using their phone, identifying the accident location from a passerby who stopped to help. 

Operator and management information

Overview

Broome Aviation was re-issued an air operator’s certificate (AOC) on 11 November 2022, to conduct operations under CASR Part 135 ‑ Australian air transport operations – smaller aeroplanes, allowing single and multi-engine piston and single engine turbine air transport operations. At the time of the accident, it operated the following Cessna aircraft:

  • 7 x C210 (single-engine piston)
  • 1 x C310 (multi-engine piston)
  • 1 x C404 (multi-engine piston)
  • 1 x C208 (single-engine turbine).

In addition to a head of flying operations (HOFO), the operator had 7 seasonal pilots in a combination of full-time and casual positions.

Figure 17: Operator’s organisational structure

Figure 17: Operator’s organisational structure

Source: Broome Aviation

Chief executive officer

The CEO held the positions of flight operations manager[18] and head of maintenance control (HAMC) (Figure 15).[19] They also owned and operated Broome Air Maintenance (BAM). This maintenance facility performed all the maintenance on the Broome Aviation fleet. The facility’s personnel comprised a chief engineer, who was registered as a licenced aircraft maintenance engineer (LAME), and aircraft maintenance engineers (AMEs). The chief engineer began working at BAM in October 2022. 

The interim HOFO stated that the CEO had a hands-on approach to the organisation, stating that the CEO would generally create the roster for the pilots, which the interim HOFO would check and approve. The chief engineer stated the CEO would also be the final authority of any maintenance conducted on an aircraft. 

The Broome Aviation operations and maintenance manuals contained contradictory information relating to the person nominated in the HAMC position. In the operations manual, the chief engineer of BAM was incorrectly listed as the HAMC, whereas the maintenance manual accurately listed the CEO in the position. The CEO later stated that the chief engineer of BAM was filling a dual role of both chief engineer and HAMC, however this was not communicated to CASA and was not the understanding of the chief engineer.

Head of flying operations

During the period from December 2022 to June 2023, the HOFO position underwent a temporary change. The substantive HOFO took a period of leave, during which a new person assumed the position on an interim basis.[20]

The interim HOFO was employed as a full-time, permanent pilot for another operator (operator 2), which was also based in Broome and only conducted operations in Cessna 208 aircraft. Operator 2 was independent of Broome Aviation. The interim HOFO began to work with Broome Aviation in November 2021 as a casual pilot during operator 2’s off season. They recommenced casual work with Broome Aviation on 13 November 2022, again during operator 2’s off season. 

In late November, Broome Aviation asked them if they were willing to fill the position of HOFO to cover the leave period of the substantive HOFO. Having agreed, their application was submitted to CASA on 25 November 2022 (see the section titled Head of flying operations assessment).

The interim HOFO was assessed for the HOFO position by CASA on 7 December 2022 and subsequently approved for that position on 12 December 2022. On the same day, a handover was completed with the substantive HOFO. CASA was informed that the handover had been completed. The interim HOFO was also assessed by CASA (18 November 2022) and approved for the position of ‘alternate’ HOFO with operator 2 in January 2023 (see the section titled Requirements for an alternate HOFO).

At the time of their appointment to the Broome Aviation HOFO position, the interim HOFO held a commercial pilot licence (aeroplane), issued in early 2008, with single and multi-engine aircraft (MEA) class ratings. They had a total flying experience of 5,049 hours, of which approximately 135 hours were on MEA (Table 8). They had flown the C310 once prior to their HOFO assessment, which was a check-to-line flight in VH-DAW on 3 December 2022.

Table 8: Interim HOFO flight hours prior to assessment

Single-engine

ICUS

Dual

Command

DayNightDayNightDayNight
184.31.4158.913.94,542.413.3

Multi-engine

13.93.831.71.576.47.9

The interim HOFO completed an IPC for MEA, in a different aircraft type, on 2 December 2021. It was renewed in the C310 during the external instructor visit to the operator in December 2022. Prior to conducting supervisory or check flights with Broome Aviation pilots, the interim HOFO had gained 20 hours flight time on the C310. This met the operator’s minimum requirements for supervisory pilots. 

Table 9: Interim HOFO Cessna 310 flight hours

DateLocationFlight typeFlight time
03/12/2022Broome → Port Hedland → BroomeCheck-to-line (Charter)3.6
07/12/2022Assessment completed with CASA for HOFO position
12/12/2022Assumed position of HOFO
14/12/2022Broome → Halls Creek → Fitzroy Crossing → BroomeCharter5.7
16/12/2022Broome → BroomeMEA IPC1.1
12/01/2023Broome → BroomeCharter2.2
15/01/2023Broome → Derby → Fitzroy Crossing → Mount Barnett → Fitzroy Crossing → Derby → BroomeCharter4.3
26/01/2023Broome → Port Hedland → BroomeCharter (ICUS for another pilot)3.7
16/02/2023Broome → Derby → BroomeCheck-to-line for another pilot1.5
25/04/2023Broome → Derby → BroomeCheck-to-line for the pilot of the accident flight2.4

The interim HOFO stated that they expected to occupy the position until the end of February 2023, when they were to return to operator 2 and the substantive HOFO was expected to return from leave. This time period was agreed to by operator 2, with the understanding that all flight and duty times for either operator would be recorded in both operators’ systems to ensure flight and duty limits were not exceeded. The interim HOFO stated they were unaware they had been approved and appointed by CASA in the ‘HOFO’ position and assumed they were in the ‘alternate HOFO’ position for Broome Aviation. They advised they only became aware that they were the appointed HOFO during a CASA level 2 surveillance activity (see the section titled Level 2 surveillance – 20 June 2023). 

Oversight of operations

Although the assessment CASA completed of the interim HOFO was for a period of one month, they did not contact the operator at the end of this period to consider if the assessment was still appropriate.

At the end of February 2023, the interim HOFO was told that the substantive HOFO’s return would be delayed until the end of June 2023. They advised that they discussed remaining as acting HOFO with the Broome Aviation CEO, however their duties would need to be reduced. These duties were subsequently reduced to check and training, confirmation of rosters (arranged by the CEO), and general availability for pilots requiring assistance. CASA was not informed of this change. The interim HOFO stated that their main responsibility after this time was with operator 2. 

At the beginning of March 2023, the interim HOFO completed a 2-week flight instructor rating course for MEA in Darwin, which was funded by operator 2. Following its completion, the interim HOFO then recommenced full-time work with operator 2. They stated that they were still contactable for any pilots at Broome Aviation who needed assistance and noted that 2 ‘senior’ pilots were available during this time (one of these pilots being the pilot of the accident flight). 

In March 2023, the management of operator 2 identified that the interim HOFO was still conducting flights for Broome Aviation. In response, they were advised to cease working for Broome Aviation as that work would affect their flight and duty times as they were also in the alternate HOFO position for operator 2. Operator 2’s management was unaware that the interim HOFO continued to conduct flights and remained the HOFO for Broome Aviation after the discussion in March 2023. 

While at Broome Aviation, the interim HOFO checked 3 pilots to line on the C310. The interim HOFO had accumulated 23.1 hours on the C310 prior to conducting the check-to-line flight on the pilot of the accident flight. They recalled that, even though they had recently received their instructor rating for MEA at that time, they did not feel comfortable simulating single engine emergencies. 

The interim HOFO stated that, after the pilot of the accident flight was checked-to-line, they followed up with them after their first couple of flights. The interim HOFO expressed no concern about the pilot’s operation of the C310 and noted the pilot had not contacted them in relation to issues or questions about the aircraft. The accident pilot confirmed they never contacted the interim HOFO regarding the C310, noting: 

I didn’t feel comfortable contacting the HOFO with 310 questions … this was due to their very minimal type knowledge and support within the entire company, so I sought advice from outside the company from more experienced pilots on the 310.

During the 4-month period from March to June 2023, the interim HOFO recorded 33.85 duty hours at Broome Aviation, however they noted that they would often ‘drop in’ after completing flights for operator 2 and did not formally record all the time spent at Broome Aviation. The CEO later advised that the HOFO was available in the afternoons for discussions with pilots however, none of the pilots made use of that opportunity. Comparatively, the interim HOFO recorded 458 duty hours at operator 2 during this period and reported they flew full‑time for the operator, while also conducting check and training for its pilots. 

At the time of the accident, the interim HOFO had been in the HOFO position for Broome Aviation for 7 months. A week after the accident flight, the substantive HOFO returned to the operator.

Pilots flying for Broome Aviation stated that, when contacting the interim HOFO between March and June 2023 they would not get an immediate response, noting that the HOFO’s priority was flying for operator 2. The pilot of the accident flight stated that they would generally reach out to another pilot (who had recently left Broome Aviation) for guidance on the C310 rather than the interim HOFO.

Multiple pilots reported that the CEO would monitor each flight using the operator’s online tracking system. If any deviations in flight time or route occurred, the pilot would receive a ‘barrage’ of foul language, be accused of not considering the monetary implications for the organisation, and then face threats of loss of flight hours or potential termination of employment. By contrast, the CEO stated they had little interaction with the pilots as their office was located at the maintenance facility, which was on the opposite side of the airport. They also stated that all communications about aircraft maintenance would be directly from the HOFO. 

The interim HOFO reported that, after completing a day’s duties at operator 2, they would pass through Broome Aviation to check the operations for the day. They recalled they would have general conversations with pilots and considered them to be close friends as well as work colleagues. However, the pilots the ATSB spoke to stated that, during this period, they received little to no guidance on flight operations (for all aircraft types). 

The substantive HOFO stated that they primarily spent the workday in their office and generally interacted with pilots while they were completing paperwork. Most interactions involving questions or issues occurred over the phone. They also reported that the CEO, whose office was located at the hangar, had more frequent face-to-face interactions with the pilots, often seeing them before and after their flights.

Safety management system 

CASR Part 119 (119.190), which commenced on 2 December 2021, included a requirement for an operator conducting operations under CASR Part 135 (Australian air transport operations – smaller aeroplanes) to have a safety management system (SMS). However, at the time of the accident the operator was operating under exemption EX87/21 and was not required to have met the SMS requirement. This exemption applied to a significant proportion of the small charter sector and was not specific to this operator. Despite that, Broome Aviation was required to have completed an SMS implementation plan and submitted the plan to CASA by 4 April 2023. The operator had not completed that process at the time of the accident.

The operator’s nominated safety officer was a line pilot. They left the operator at the end of December 2022 and returned to complete a short 3-week stint at the end of February 2023. The operator did not nominate a new safety officer after this pilot left the organisation and they were not required to do so, as there was no regulatory requirement for them to have one.

While not required, the operator did not have a formal incident or hazard reporting system, or a means of identifying the development of hazardous trends. Interviews with various staff members indicated that, although there were safety meetings involving pilots to identify safety risks, these meetings had not been held since the arrival of the interim HOFO.

Organisational pressures

The ATSB interviewed the 5 pilots who conducted Cessna 310 operations for the operator during the period November 2022 to June 2023, as well as 2 other pilots. During interviews, most of these pilots revealed events in which they were reprimanded or challenged by the CEO, or they witnessed similar treatment to other pilots, for declining a flight due to a maintenance concern. Many pilots stated they had experienced pressure from the CEO to complete flights with aircraft they considered unairworthy. 

They stated they were worried about the consequences, such as employment termination or the hindering of their career progression, if they did not complete those flights. Pilots also stated that they felt pressure to ‘get the job done’, with one pilot stating: 

…it was always like you just have to do the job. You have to do the job. It's not anything to do with safety or if you have the training for it either…

During the draft report review process, the CEO acknowledged that at times they had reprimanded and challenged pilots. However, they stated that this was in response to pilot actions that they considered imposed unnecessary financial and/or reputational cost on the company.

Complaints received by CASA from pilots and a passenger (see the section titled Complaints to CASA) stated multiple concerns for the safe operation of aircraft. One complaint by a former pilot stated:

… operational pressure from the organisation and their management is forcing pilots to make unsafe decisions in flight. A report to CASA is better than trying to reason with the company. The mentality of not only managers but also the owner isn't conducive to safe aviation practices.

Senior management stated they were unaware of any instances where pilots were reprimanded for not flying an aircraft considered to be unserviceable. All stated that, if there was a defect with an aircraft, the operator’s stance would be to get it rectified before another flight was completed.  

During interviews, former pilots expressed concerns for the operator’s future, and one stated: 

I knew that either I was going to be involved in something that I shouldn't be or that an incident was going to happen. 

Most of the pilots the ATSB spoke to who had left the organisation stated their decision to leave was based on aircraft maintenance issues and/or the unacceptable treatment they received as pilots from senior management.

Civil Aviation Safety Authority oversight 

Head of flying operations assessment

Position requirements

Under the CASRs, the HOFO must meet specific requirements, including holding appropriate qualifications, demonstrating substantial operational experience, and having a thorough understanding of regulatory obligations. The HOFO is responsible for overseeing operational standards, managing safety and compliance frameworks, providing leadership to flight crews, and ensuring that all activities align with organisational and regulatory expectations.

Specifically, CASR sub regulation 119.140(1) stated that: 

The head of flying operations of an Australian air transport operator must safely manage the flying operations of the operator.

CASR 119.135 required the HOFO to:

• hold a pilot type or class rating for a type or class of aircraft that is used to conduct a significant proportion of the operator’s air transport operations

• have at least 500 hours flight time on a type of aeroplane that is the same as, or substantially similar to the type of aeroplane used to conduct a significant proportion of the operator’s Australian air transport operations

• have at least 6 months experience in the conduct or management of air operations conducted under an AOC or equivalent foreign authorisation.

CASA’s acceptable means of compliance and guidance material (AMC/GM) Part 119 - Australian air transport operators - certification and management v 2.3 outlined recommended minimum hours and experience for a HOFO based on the size and complexity of the operator. For an operator with more than one MEA, such as Broome Aviation, CASA recommended that a HOFO have a minimum of:

• 1,000 hours total flight time

• 200 hours in command of MEA. 

Requirements for an alternate HOFO

Under CASR 119.205, there was a requirement for the operator’s exposition to list the qualifications, responsibilities, and names of key personnel. There was also a requirement to list the names of each person authorised to carry out the responsibilities of the position when the substantive position holder was absent from the position or unable to carry out their responsibilities. These authorised persons were referred to as alternate key personnel. 

If an operator wanted to change the specific individual in the alternate key position, CASA approval was required, due to this being considered a significant change. Once approved, this should lead to the insertion of the nominated person into the operator's exposition as an alternate key position holder. Operators working under CASA exemption EX82/21, including Broome Aviation, were not required to name alternate key personnel in the exposition, even if they had an alternate.

The AMC stated that small operators with limited personnel may nominate alternate HOFOs employed by another operator, provided they detailed in their exposition how the alternate HOFO would perform the position effectively. The requirements for an alternate HOFO were the same as the HOFO position. In addition, the alternate HOFO had to have a direct relationship with the operator and sufficient capacity to fulfill their duties. It also stated that dual responsibilities for multiple operators were unlikely to meet this standard. 

The operator’s operations manual stated that an alternative HOFO must be approved by CASA. It also stated that:

• a handover form must be completed prior to the transfer of the responsibilities from the HOFO to the alternate HOFO

• the alternate HOFO could not be the acting HOFO of any other operation while acting as the HOFO for Broome Aviation

• the alternative HOFO could only perform the duties of the HOFO during the specified period they had been nominated to act as HOFO

• CASA be informed within 7 days of the transfer being completed. 

Assessment process

CASA’s HOFO suitability assessment was a formal process designed to evaluate a candidate’s suitability for the position of HOFO in a CASR Part 135 operator. It aimed to ensure the individual had the necessary qualifications, operational experience, and management skills to oversee flight operations safely and in compliance with CASA regulations. The assessment begins with a review of the candidate’s documentation, including licences, flight experience, and familiarity with the operator’s aircraft and procedures. CASA also examined the candidate’s knowledge of relevant regulations, operational procedures, and safety management principles.

The assessment included an interview where CASA evaluated the candidate’s understanding of key areas such as CASA regulations (Parts 135, 91, and 119), the operator’s exposition and procedures, SMS implementation, and human factors. The candidate was also required to demonstrate the ability to manage compliance, oversee pilot performance, and respond effectively to safety-critical situations. Leadership and decision-making skills were also a focus, as the HOFO must manage teams, promote a strong safety culture, and ensure the organisation adheres to all operational requirements.

The assessment may have also required a practical demonstration of the candidate’s ability to implement operational procedures and manage risk. Based on the assessment, CASA determined whether the candidate was fit for the position or if further experience was needed.

Applicant 1

In October 2022, the operator submitted an application to CASA for its HOFO position, replacing the substantive HOFO as they advised they were resigning from the key personnel position of HOFO for medical reasons on 17 October. It also submitted a change to its operations manual to replace the substantive HOFO with the proposed HOFO candidate. This applicant had 2,327 flight hours with 1,009 multi engine hours, however they did not have any air transport experience and had not been a HOFO with any other operator.

This application was assessed on 14 November 2022 and the CASA flight operations inspector (FOI) deemed the applicant unfit for the position due to:

  • limited experience in air transport operations
  • not meeting the 500-hour requirement on aircraft substantially similar to those primarily operated by the operator
  • an assessment, based on previous dealings with the CEO, that an experienced HOFO was required to ensure pilots were managed professionally and the operation was safe and efficient.

On 21 November, CASA advised the operator that the applicant was unsuitable. In internal CASA correspondence, the FOI noted that the application was to replace the substantive HOFO who would be on leave and would be returning at the end of April 2023. The FOI stated concern for continuity of the operation over this period. 

The substantive HOFO continued in the role in a limited capacity. 

Applicant 2

On 19 July 2022, operator 2 applied to CASA for approval of an alternate HOFO position, with the applicant who was later approved to be Broome Aviation’s interim HOFO being the nominated candidate (Table 10). This application was assessed by the same FOI mentioned in the section above on 18 November 2022. When requested, CASA could not locate the assessment form completed on applicant 2 for this position. The FOI later stated that they had expected to complete a flight test for the interim HOFO during this original assessment, however an internal CASA decision was made that it would be a desktop assessment only.

Following the rejection of its first applicant, Broome Aviation submitted an application for an alternate HOFO position on 25 November 2022, with the interim HOFO being the nominated candidate and an expectation that this person would be acting in the HOFO position for a limited period. This application included changes to the operations manual to update the positions. The same FOI completed this assessment and stated that, because they had recently assessed the applicant as an alternate HOFO for operator 2, the process could be expedited as many of the assessment elements had previously been covered. 

The assessment for the interim HOFO for Broome Aviation was completed by the FOI on 7 December 2022. The documentation stated that the assessment was for an ‘alternate’ HOFO position, with a time limitation of 1 month. It was also noted that the applicant had taken leave from their original operator to fulfill this position.  

The FOI advised that the 1-month timeframe was due to their understanding that the substantive HOFO would be travelling overseas for this time and would be returning to the operator. However, there was also email evidence indicating that the FOI knew the substantive HOFO would be on leave until April 2023. In discussions with the ATSB, the FOI stated the 1‑month period was the primary timeframe considered for this applicant and as a result they were not assessed in their:

  • check and training experience
  • MEA experience
  • ability to conduct oversight, if working for 2 operators.

On 12 December, CASA formally issued the approval for the applicant to become the HOFO rather than as requested and stated in their own paperwork, the alternate HOFO for Broome Aviation. The updated operations manual specified the applicant was appointed in the alternate HOFO position, instead of the CASA‑approved position of HOFO. It did not change the nominated person for the HOFO position, even though they were on leave for a significant time. There was no explanation in the operations manual of how the alternate HOFO would manage this position if they returned to their original operator. The manual amendment was accepted by CASA. The FOI advised that the operations manual was accepted as the change was for a short time and they did not expect the operator to resubmit the manual when the substantive HOFO returned.

Table 10: HOFO assessment timeline

DateEventOperator
19/07/22Request for applicant to be alternate HOFO Operator 2
18/11/22Applicant assessmentOperator 2
25/11/22Request for applicant to be alternate HOFO Broome Aviation
07/12/22Applicant assessmentBroome Aviation
12/12/22CASA approval for HOFO positionBroome Aviation
24/01/23CASA approval for alternate HOFO positionOperator 2

CASA stated that a key personnel position did not come with a time limitation, although one could be imposed by the operator and outlined in its exposition.[21] If this was the case, CASA would note the time limitation on its assessment of the applicant and place a note on file in the CASA system. While CASA’s assessment of the interim HOFO was based on a 1-month period, no note was placed on file.  

In February 2023, while preparing for a level 2 surveillance activity, a regulatory oversight flight operations inspector (RO FOI) identified that the interim HOFO had been assessed for the position on the basis of performing that position for one month, however they were still acting in this position 3 months after the assessment had been completed.

The RO FOI contacted the interim HOFO to discuss the situation and was advised that the substantive HOFO would be on leave until June 2023 and the interim HOFO had been conducting HOFO duties. They also were advised that the interim HOFO would be recommencing seasonal work with operator 2 at the beginning of March 2023, with the intention of continuing with Broome Aviation as HOFO on a ‘remote basis’. The RO FOI ensured the interim HOFO was aware of their own requirements for fatigue management, discharge of responsibilities and general oversight of Broome Aviation activities while working with the other operator. 

The RO FOI noted that, although there was nothing legislatively preventing this arrangement under CASR Part 119, it was unorthodox and created a level of concern. There was no reassessment of the interim HOFO in relation to their duties, as the RO FOI assumed a full assessment had been completed during the other FOI’s previous assessment in December 2022. 

Complaints to CASA

The CASA Surveillance Manual 15.1 required that when CASA received a complaint about an operator, it be classified as a class A–C occurrence and action be taken if it was assessed as class A or B (Table 11). A class A assessment required instigation of a level 2 unscheduled investigation, while a class B assessment could be investigated or added as an item in an upcoming surveillance.   

Table 11: CASA complaint occurrence classes and follow‑up action

ClassOccurrence eventSurveillance typeAction Type
A - CriticalComplete loss/failure of the aviation system(s), or a destructive failure, impacting directly on the safe operation of the aircraft

Level 2 – Unscheduled – Occurrence Investigation Request – Desktop

Follow-up (possible Level 2 – Unscheduled –Occurrence investigation Request – Site)

A level 2 unscheduled occurrence investigation request – site surveillance type event is scheduled to be completed.
B - SeriousA partial loss/failure of the aviation system(s), potentially impacting on the safe operation of the aircraft

Level 2 – Unscheduled – Occurrence investigation Request – Desktop

OR

Level 2 – Unscheduled – Occurrence investigation Request – Site

Independent desktop and/or site visit may be required depending on the history of the operator

If no immediate follow up is determined to be required, the event must be followed up during the next scheduled surveillance event.

C - MinorDegradation of the aviation system(s) or part thereof, not impacting directly on the safe operation of the aircraft.

If follow up action is to be taken

Level 2 – Unscheduled Occurrence Investigation Request – Desktop

Generally, no further action is required

In November 2022, CASA received a complaint about Broome Aviation relating to operational issues. The complainant stated that: 

there was an oppressive culture at the organisation, based on bullying and pressure from the CEO that ‘preys on junior pilots’. 

It also detailed instances of:

  • pilots being forced to fly aircraft at night with unserviceable instruments
  • pilots being advised to fly outside legal operational requirements
  • comments made to pilots to ignore issues or defects with aircraft. 

This information was passed to the CASA surveillance team, where the RO FOI followed up on the complaint by talking to the complainant in February 2023. Although evidence, including copies of text messages, was supplied to CASA, the RO FOI explained to the complainant the importance of reporting an incident (either via the company reporting system or the CASA confidential system), with specific details, at the time it occurred. They also outlined the legal obligations of a pilot in command to record aircraft defects correctly.

After discussing the matter with the complainant, the RO FOI assessed the complaint was either indicative of a ‘disgruntled’ former employee, or there was a cultural issue at the operator. The complaint was added to the scoping document for a June 2023 surveillance activity (see the section titled Level 2 surveillance – 20 June 2023), and assessed as a class B. 

There was no documentation outlining if the complaint was followed up after the audit. 

CASA stated that the complaint it received in November 2022 did not provide sufficient specific information to act upon. The supplied text messages were not considered to be fully contextualised, clear, or related to specific events where additional evidence could be sought. 

Following the accident on 20 June 2023, CASA received 2 more complaints. The first complaint was from a pilot who stated that there was operational pressure from management forcing pilots to make unsafe decisions in flight. The complainant stated that they had witnessed this firsthand. No specific examples were provided. The second complaint was from a passenger who stated that on a charter flight from Broome, the twin-engine aircraft experienced a technical fault, and the pilot was instructed by management to continue the flight.

The scope of these complaints was added to a level 1 audit scheduled to be completed in August 2023 (see the section titled Level 1 audit – August 2023). 

There was no indication in any of the CASA documentation that the complaints received were followed up during or after either surveillance event. 

CASA stated that complaints regarding the safety culture of an organisation that did not have a safety management system (SMS) were difficult to assess, and there was no guidance given to inspectors on what to specifically assess. As such, an assessment, if completed, would be subjective to the person completing it. An in-depth assessment of an organisation’s culture required people to be prepared to talk about specific events or actions to ensure the context of the situation was fully understood. 

Surveillance activities

A level 1 CASA audit was a detailed evaluation that assessed an aviation organisation's compliance with regulatory and safety standards. Such an audit encompassed various aspects of the organisation’s operations, including:

  • the SMS
  • operational control
  • maintenance
  • airworthiness
  • training
  • competency
  • regulatory adherence.

It involved a sample of operational aspects, often including extensive documentation reviews, interviews, and inspections. It aimed to identify both systemic issues and specific non-compliance or safety concerns. Any findings from a level 1 audit required the organisation to implement corrective actions to enhance safety and ensure continuous compliance with aviation regulations. The audit was typically scheduled at regular intervals or when there was a significant change in the organisation’s operations, such as new certifications, major incidents, or regulatory changes. The last level 1 audit on Broome Aviation prior to the accident was conducted on 19 October 2018.

A level 2 CASA surveillance activity was a more focused evaluation conducted to examine specific areas of an organisation's operations. This type of surveillance was typically less comprehensive than a level 1 audit and entailed an examination of aspects such as operational procedures, training programs, or maintenance practices. This surveillance was often conducted in response to a specific incident, identified risks, previous audit findings, or as part of ongoing surveillance and monitoring efforts. The last level 2 surveillance activity on Broome Aviation prior to the accident was conducted on 19 August 2018.

Level 2 surveillance – 20 June 2023

At the beginning of March 2023, the CASA surveillance team approved a level 2 surveillance activity on the operator. This was initiated as a result of:

  • the complaint received by CASA in November 2022 regarding allegations of operational pressures placed on flight crew by the CEO
  • the process surrounding the assessment and appointment of a temporary HOFO while the substantive HOFO was on leave. 

The surveillance was scoped to cover both topics and involved a site visit conducted by the RO FOI on 14 June 2023, 6 days before the accident. The scoping did not outline how the complaint received by CASA would be assessed during the surveillance and the surveillance report was finalised on 11 July 2023.

During the surveillance, discussions were held with the interim HOFO regarding their position and level of oversight of operations, noting they were working full time for another operator at that stage. It was concluded that the interim HOFO was providing a level of oversight and interaction with personnel, and this was achieved via:

  • regular discussions with crew
  • oversight of schedules and flight and duty via the organisation’s systems
  • conduct of company proficiency flights / line and remedial training with flight crew
  • some limited formal governance meetings.

The surveillance report noted that no documentation could be supplied to demonstrate that both informal and formal meetings were being conducted during the interim HOFO’s time in the position. CASA issued a safety observation to Broome Aviation to review and update the content of its operations manual to include the governance processes utilised by the HOFO and establish a method and database to record such meetings and their outputs.

CASA reviewed the documentation surrounding the interim HOFO’s flight and duty times at both organisations and assessed that these complied with regulatory requirements.  

The RO FOI advised the ATSB that they had concerns about the level of oversight the interim HOFO was providing for Broome Aviation during the time they were concurrently employed as an alternate HOFO at another local operator. They noted the interim HOFO’s view of the position seemed to revolve around being there for a short time. This concern was not documented on the final audit report. 

The final surveillance report contained no mention of the November 2022 complaint and how it was assessed during the surveillance activity, and there was no other documentation to explain why the complaint was not mentioned in the report. The RO FOI stated that the complaint gave little information around the specifics of the incident, making it hard to check while at the operator. 

When asked if any of the pilots were interviewed regarding the topic of operational pressures, the FOI stated they witnessed pilots coming in and out of the office area while they were conducting the meeting with the interim HOFO and ‘everyone seemed happy’. They also recalled there was no indication there was anything out of the ordinary that would have made them want to talk to any of the pilots. The RO FOI stated that it was generally possible to find a way of talking to pilots during surveillance activities and they had done so on previous occasions (with other operators), but did not see the need to do so on this occasion. There was no indication the operator’s management was aware of the complaint at the time the audit was conducted.

CASA’s processes required that this surveillance report was submitted to the RO FOI’s manager for approval prior to the audit being finalised. The absence of any content about the complaint, one of the 2 reasons for the surveillance activity, was not addressed during the approval process.

Level 1 audit – August 2023

A level 1 audit on the operator was conducted in August 2023. The audit’s scope originally covered:

  • airworthiness assurance
  • data and documentation
  • operational support systems
  • safety assurance
  • safety risk management.

It was subsequently expanded to include aspects associated with the apparent circumstances of the C310 accident, focusing on the fuel policy, flight planning, and training, and the 2 further complaints submitted to CASA on the operational pressures placed on flight crew. The audit team consisted of 3 inspectors, and included a site visit conducted on 28 August.

The audit found multiple issues with the operator’s operations manual. It noted that, although it met the basic requirements, it had not been updated in accordance with legislative changes. It also noted that the operations manual was not compliant with CASR Part 91/135 fuel and flight planning requirements. 

The audit also identified that there was a general weakness with regard to the content and detail of the operations manual, in particular the policy and procedure surrounding the induction, operational training and release to line of junior pilots. The RO FOI stated that, due to the operator sitting under exemption 87/21, the requirements for meeting a training and checking system were not in place at the time. This situation meant no safety finding could be issued regarding the weaknesses in training and checking.

The audit found that, although the operations manual had an extensive section relating to operational use of maintenance releases (MRs), some references were either no longer valid or current legislative references were missing. It also found that Broome Aviation was no longer following the process for monitoring MRs and MELs that it had outlined in its maintenance control manual (MCM). The MRs of aircraft current at the time were not reviewed during this audit. 

Previous level 1 audit

During the previous level 1 audit in October 2018, an airworthiness inspector noted various deficiencies with an aircraft during a ramp inspection. These deficiencies had not been entered into the MR or other aircraft documentation. The operator was given a list of these deficiencies in the surveillance report. No other aircraft or MRs were inspected during this event. 

After the FOI was informed about the deficiencies on the aircraft, they identified that pilots’ maintenance training was not being conducted in accordance with the MCM or the operations manual. CASA recommended the operator undertake an educational program to provide guidance for the pilots in the following areas:

  • conducting accurate pre-flight inspections
  • entering defects into maintenance releases
  • checking for any potential items that could pose a risk to flight
  • correct use of maintenance releases.

CASA confirmed that Broome Aviation completed this educational program with all pilots who were employed at the time.

Related occurrences

Numerous fuel management and fuel starvation incidents and accidents have previously been investigated by the ATSB, including:

  • Engine power loss and forced landing involving Pilatus Britten-Norman Islander BN-2A VH‑WQA, Moa Island, Queensland on 3 October 2022 (AO-2022-046)
  • Fuel starvation event involving Cessna 310, VH-JQK, near Sunshine Coast Airport, Queensland, on 18 August 2022 (AO-2022-040)
  • Cessna C310R, VH-HCP, 3 km east of Newman Airport on 26 January 2001 (200100348)

The ATSB found that pilot understanding of, and management of aircraft fuel systems played a crucial role in these occurrences.

Safety analysis

Introduction

On the return leg of a flight from Turkey Creek to Derby, Western Australia, the pilot encountered dual engine surging. The pilot, assessing this was due to fuel starvation, began switching fuel tanks to utilise any remaining fuel. With no resolution, the pilot initiated a MAYDAY call to Brisbane Centre air traffic control, alerted the passenger to the emergency, and told them to brace for impact. During the subsequent forced landing, the right wing of the aircraft hit a tree causing the aircraft to turn 180⁰ and come to an abrupt stop on the edge of the highway.

The pilot sustained serious facial injuries, and the passenger sustained minor injuries. The aircraft was substantially damaged.  

This analysis firstly considers the pilot’s fuel management during both the first and second leg of the flight, the response to the emergency, and survivability aspects relating to the injuries of those onboard. It also discusses contextual factors that potentially influenced the pilot’s performance during this period.

The analysis then discusses several other safety factors identified during the investigation related to pilot training and consolidation, operator oversight, organisational aspects and regulatory oversight. These factors either contributed to the accident, or increased aviation safety risk more generally.

The safety factors are discussed under the following topics:

  • management of fuel
  • response to the emergency
  • factors influencing pilot performance
  • defect reporting
  • legibility and accuracy of aircraft internal placards
  • survival aspects
  • operational pressures
  • regulatory oversight.

Management of fuel

Pre-flight planning

Pre‑flight planning is vital to ensure there is sufficient fuel for all phases of the flight. This includes accounting for fuel required for taxi, take-off, climb, cruise, descent, landing and the required fuel reserves.

The pilot used the operator’s flight planning software to plan the flight, however they did not know how to input forecast winds and reported that they routinely planned using nil wind. The operator also provided a manual system that would have enabled the pilot to accurately plan the fuel requirements for the flight. A pilot in command is required to ensure the relevant meteorological forecasts are considered when determining the quantity of fuel required for a flight.

Taking into account the known environmental conditions and the aircraft’s fuel consumption, if the pilot had used the available wind data, the flight plan would have identified to the pilot that the planned flight from Broome to Turkey Creek and return to Derby with the required fixed reserve and contingency fuel could not be achieved without refuelling the aircraft en route.

Pilot perception of fuel available in the auxiliary tank 

The pilot conducted all their flights in the Cessna 310 (C310) with the assumption that the auxiliary tanks could not be used for longer than 45 minutes without the engines surging and so used the auxiliary tanks for 40 minutes. While it is likely that this behaviour was due to the reverse leak in the right auxiliary tank check valve, the ATSB was unable to conclusively determine if this was the reason for the engine surging reported by the pilot on the day of the accident.

As a result, the pilot had not intended to use all the usable fuel on board, reducing their actual endurance. However, this was not reflected during flight planning. 

Contributing factor

The planned flight from Broome to Turkey Creek and return to Derby with the required fixed reserve and contingency fuel could not be achieved without refuelling the aircraft en route. In addition, the pilot did not intend to use all the available fuel in the auxiliary tanks and did not take this into consideration in their pre-flight planning, further reducing the amount of fuel available.

Broome to Turkey Creek

On assessing the remaining fuel following arrival at Turkey Creek, the pilot reported that it was unevenly distributed, with the right auxiliary tank full and less than expected in the right main tank. The ATSB considered the following possibilities to account for this reported distribution:

  • the pilot did not switch the right main tank to the right auxiliary fuel tank en route to Turkey Creek
  • the fuel leaked from the main tank to the auxiliary fuel tank on the ground at Turkey Creek.

Testing of the right auxiliary tank check valve indicated that, although there was a leak through the tank vent outlet bleed return line check valve, it is unlikely this leak was large enough to have resulted in the 40 L discrepancy the pilot experienced on the day of the occurrence. In addition, it is very unlikely that the amount of fuel that leaked would have been equal to the amount of fuel which would have been used if the pilot had selected the auxiliary tank during this leg of the flight. As such it was assessed that it was more likely that the pilot did not select the auxiliary tank on the right side during the flight.

This resulted in the pilot having full fuel in the right auxiliary fuel tank at Turkey Creek and 40 L of fuel less in the right main tank than the pilot expected.

Upon returning to the aircraft and completing pre‑flight checks, the pilot did not visually confirm the right auxiliary tank was full. As the fuel gauges in the aircraft were known to be inaccurate, a visual inspection of the auxiliary tank would have verified if it was full.

Return flight leg

The pilot routinely flew the aircraft with the main tanks selected for 60 minutes after take-off on each leg of a flight, rather than the 90 minutes detailed in the pilot’s operating handbook (POH) for the larger tanks fitted to VH‑DAW. While the pilot advised this was how they simplified inflight fuel management, that practice increased the risk of fuel being vented overboard from the main tanks. 

When the pilot switched from the main tanks to the auxiliary tanks on the second leg of this flight, it is likely the right main tank had only approximately 4 L of fuel remaining, and the left main tank had approximately 44 L remaining.

The ATSB could not establish why the right engine reportedly surged when selected to the right auxiliary tank, as there should have been approximately 97 L of fuel in the tank, and the reported issue with the check valve occurred when the fuel level in the auxiliary tank was approximately half (60 L). 

When the pilot reselected the right main tank in response to the surging, the amount of fuel contained in the tank would have increased to approximately 12 L due to the fuel returned when using the auxiliary tank. After a further 10 minutes, the right engine again surged, this time most likely due to fuel starvation, resulting in pilot crossfeeding to the left main tank, which also had minimal fuel at that stage. 

Fuel calculations conducted by the ATSB determined that when the right engine was crossfed to also draw fuel from the left main tank there was approximately 34 L of fuel left in that tank. About 10 minutes later, the engines began surging as the fuel in the left main tank was reduced to approximately 9 L of useable fuel. While it could not be determined why that quantity was insufficient to maintain continuous power, supply issues associated with an inoperative transfer pump (due to the observed tripped circuit breaker) and/or debris and other contaminants in the bottom of the fuel tank were possibilities.

Contributing factor

It is likely that the pilot did not utilise the right auxiliary fuel tank during the first leg of the journey and did not manage usage from the main fuel tanks in accordance with the pilot's operating handbook. This resulted in the depletion of fuel in the main tanks to a level where continuous engine operation could not be maintained.

Continued operation with defective fuel gauges

Multiple pilots who flew the aircraft stated that the fuel gauges did not indicate the correct amount of fuel in both the main and auxiliary tanks. Multiple pilots recalled that the gauges would become more accurate as fuel was burnt, however images of the gauge after flights indicated there was a still a large disparity between the 2 sides. The reading for both the main tanks and the auxiliary tanks were determined to be significantly out of tolerance and did not show an accurate amount of fuel on board for most of the flight. 

Accurate fuel gauges are crucial in an aircraft to ensure precise monitoring of fuel levels throughout the flight, directly impacting safety and operational efficiency. They provide the pilot with real-time information about the quantity of usable fuel, allowing for informed decision-making during critical phases of flight, such as when a diversion is required or in an emergency. Although the pilot was aware that the fuel gauges were unreliable, they relied on the indicated readings at multiple points in the flight.

CASA guidance stated that an operator’s exposition should detail the maximum allowable discrepancy between the actual fuel on board (gauge / visual) and calculated (journey log) figure, noting that industry practice was a maximum of 3% variation. This percentage was not outlined in the operations manual, and the gauge defects were not recorded on the maintenance release. 

However, the ATSB assessed that the gauge display defect did not contribute to the accident as the pilot was able to assess the fuel quantities in the fuel tanks throughout the flight. 

Other factor that increased risk

The aircraft fuel gauges did not indicate accurately.

Operator’s procedures for fuel management

Pre-flight

A review of Broome Aviation’s pre-flight planning software identified that it did not include the 47 L block (total) fuel margin required under the operator’s fuel policy. It did however have a fixed fuel flow rate for climb of 150 L/hr. Conversely, the documented fuel planning figures to be used for manual fuel calculations did not include a fuel flow rate to use for climb. Although the operator was unaware of where the 47 L requirement originated from, the ATSB assessed that the margin it provided would cover the additional fuel flow used during climb, despite not being originally intended for that purpose. 

Inflight

Broome Aviation’s operations manual required pilots to conduct an inflight fuel check when reaching cruise or if needing to divert. It did not contain guidance on:

  • conducting fuel checks at regular time intervals
  • assessing fuel burn rates
  • verifying the remaining fuel relative to the reserves required for contingencies, alternate routing, and final reserve fuel
  • the maximum allowable discrepancy between the actual fuel on board (gauge / visual) and calculated (journey log) figure.

This resulted in pilots using a variety of procedures. 

Under the Civil Aviation Safety Authority (CASA) Manual of Standards (MOS) 135 Part 7, operators are required to outline inflight fuel management procedures. CASA’s Advisory Circular (AC) 91-15 Guideline for aircraft fuel requirements stated that pilots should have 2 sources of fuel values to crosscheck the available fuel on board. While the operator’s pilots were using a time‑based approach to their fuel calculations in flight, they did not have a viable crosscheck as the fuel gauge was inaccurate. A crosscheck process mitigates the reliance on a single source of information and ensures that any fuel related issues, such as high burn rates or fuel system defects, are promptly detected and managed, reducing the risk of fuel exhaustion. 

Although Broome Aviation’s operations manual did not include a procedure for recording inflight fuel calculations, the pilot completed an inflight fuel record every time they switched tanks. When the right engine surged the second time and crossfeed to the left main tank was selected, the pilot correctly assessed the amount of fuel remaining in the left main tank. They did not however accurately assess the remaining flight duration to Derby and the associated fuel required to fly that distance, considering that the right engine would be returning fuel to the right main tank.

The operations manual also gave little guidance on decision-making frameworks to address fuel‑related issues during flight, nor did it outline clear protocol for pilots to follow in the event of a low-fuel situation, including notification to air traffic services. 

Post-flight

The operator’s post‑flight cross check methods could not be completed as there was no fuel totaliser on board the aircraft and the fuel gauges were inaccurate. As such, the remaining fuel at the end of the flight was based on the pilot’s fuel calculations or a visual check by the pilots, which was not required by the operator in the post‑flight process.

Consequently, an accurate record of the fuel remaining in the aircraft was not being documented for the next pilot, nor was it being accurately entered into the operator’s data recording software for fuel flow checks. The pilots were working around this issue by ensuring the fuel tanks were full prior to every flight. 

Other factor that increased risk

Broome Aviation’s operations manual did not include a procedure for recording inflight fuel calculations. As a result, pilots adopted varying methods for fuel monitoring, leading to reduced assurance of accurate fuel management. (Safety issue)

Response to the emergency

After crossfeeding the right engine to the left main fuel tank, the pilot was confident that the available fuel was sufficient to reach Derby. They did not consider diversion to an alternate airstrip as they were unfamiliar with the condition and suitability of the nearby airstrips. They also did not consider the option of changing the left engine fuel selection to the left auxiliary fuel tank. This would have increased the fuel available in the left tank via the extra fuel return. 

In addition, as the aircraft had passed the pilot’s planned top of descent, they initiated a 400 ft/minute descent reducing the available glide altitude. Maintaining the aircraft's potential energy (altitude) is crucial for extending an aircraft's range during an engine failure, providing more landing options and time to manage the emergency effectively.

Contributing factor

After the usable fuel in the right main fuel tank had been exhausted, the pilot did not divert the aircraft to the closest airport, select the left engine selection to the left auxiliary fuel tank, or maintain altitude to increase the safety margin.

Recognising the stress induced by an emergency, indecision during an engine power loss situation reduces the time available for a pilot to plan and conduct an effective forced landing. Delays caused by prolonged troubleshooting, uncertainty over the severity of the issue, or hesitation in selecting a course of action consumes valuable altitude.

Once both engines began surging, the pilot identified that the left main tank had been drained of fuel and began to switch tanks in an attempt to utilise any remaining fuel. This included attempting to gain fuel from the main tanks a second time. Although the aircraft’s certification stipulated that power must be restored to the engines within 20 seconds in level flight if fuel was depleted from a tank, this requirement applied to level flight conditions and not during a descent phase. In a descent, the restoration of power, potentially extended beyond the 20 second threshold due to gravitational effects and reduced pressure in the fuel system.

At this point, only the auxiliary tanks had enough fuel to sustain engine power, but these tanks did not have fuel pumps to supply fuel to the engines. Textron advised that if the engines remained operating and the auxiliary tanks had been selected, the fuel could have been drawn from these tanks via the engine‑driven fuel pumps. As detailed above, it could not be established why the engines did not continue to operate at that stage as a small quantity of usable fuel remained in the left main tank.

There were 3 minutes between the start of the engine surging and the pilot's MAYDAY transmission. In this timeframe, a pilot who was experienced on the C310 would have had sufficient time to shut down and secure both engines (including feathering the propellers) and establish a glide approach. However, the pilot had limited familiarity with the aircraft fuel system, limited practical emergency procedure training on the C310, and the fuel gauges were faulty. As such, it is likely they struggled to methodically cycle through the fuel tanks while monitoring for engine response under the pressure of an unfolding emergency. During this time, the pilot also opted to continue to track towards Derby Airport, which increased the distance to the highway landing site, and delayed making a MAYDAY broadcast. 

While acknowledging that if the pilot had been able to re‑supply the engine/s with fuel and restart at least one of them, they could have continued to Derby, the delay associated with the multiple tanks selections ultimately compromised the safety and control of the forced landing. 

Factors influencing pilot performance

A review of the pilot’s activity in the days leading up to the accident identified an early wake-up time and long duty day. However, there was insufficient evidence to conclude that the pilot was experiencing a level of fatigue known to affect performance prior to, or during, the flight. The ATSB examined in detail the potential effects of experience and consolidation of skills around fuel planning and fuel management on the development of the accident.

Pilot experience and consolidation on the Cessna 310

Acquiring new skills, such as learning to fly a new aircraft type, requires training and practice. As the amount of experience on the aircraft increases, generally a pilot’s proficiency will improve, and performing tasks will become more automated and require less attention or mental resources (Wickens and others 2015, Stothard and Nicholson 2001). Prolonged gaps when flying an aircraft type have been known to affect skills, such as familiarity with specific aircraft systems, aircraft handling, and emergency procedures. 

After completing their IPC on the C310 in December 2022, the pilot had a 130-day gap before their check-to-line flight in April 2023. This limited the opportunity for skill retention on the aircraft. 

In addition, as the interim HOFO did not conduct any flights with the pilot that involved the use of auxiliary fuel tanks, there was no opportunity for the HOFO to see that the pilot was limiting their use of fuel from the auxiliary tanks to 40 minutes and the implications this had for fuel planning. Similarly, there was no opportunity to observe that the pilot was only using the main tanks for 60 minutes on every departure. The pilot also only began flying the C310 operationally after the interim HOFO had returned to their original operator. While the interim HOFO recalled discussing the pilot’s first flights with them, the pilot advised they only discussed operation of the aircraft with a pilot who had left the organisation.

Contributing factor

The pilot had limited understanding of the aircraft fuel planning and inflight fuel management, but due to a lack of consolidation training and limited to no operational oversight these issues were not detected by the operator.

Operator continued oversight and guidance

Pilots at Broome Aviation reported that the interim HOFO was unavailable most of the time between March and June 2023 due to their second job. Although the interim HOFO advised that they were available for any calls and were at the operator’s premises every day informally, the overall impression of pilots was that they were learning on their own and that they received little to no guidance on the operation of the C310. 

In addition, the interim HOFO’s recorded flight and duty times indicated that, although they reported that they visited the operator often, there was limited available time to oversee the operation. CASA personnel noted they had concerns about this aspect, and stated they received limited evidence to prove appropriate oversight was being conducted. During a surveillance event conducted shortly after the accident, CASA issued a safety observation to the operator to update the contents of its operations manual to include governance processes to record interactions between the HOFO and the operator’s flight crew.

At the time of the accident, as the operator was operating under an exemption from some Civil Aviation Safety Regulations (CASR) Part 135 (Australian air transport operations – smaller aeroplanes) requirements, there were no specific regulatory requirements for them to provide additional consolidation flights for pilots transitioning to the C310. For many types of transitions, such as to a new single engine aircraft type, consolidation may not be necessary. However, when moving from single-engine to relatively complex multi-engine aircraft, a period of consolidation flights is an effective risk mitigator. 

The operator had limited processes in place to ensure pilots with low time and experience on the C310 had the opportunity to effectively consolidate their skills prior to (or after) being checked to line. The substantive HOFO stated that they expected pilots new to the C310 to have completed multiple ICUS flights prior to a check-to-line flight. However, coincident with the substantive HOFO being on leave, several senior pilots left the organisation and the interim HOFO returned to work for their original operator. In combination this left limited capacity to supervise pilots.

Pilots who flew the C310 for the operator between November 2022 and June 2023 reported receiving limited training on the aircraft prior to being checked to line, noting they had expected to have completed more ICUS flights. Of the 7 pilots the ATSB contacted regarding C310 operations, 2 pilots reported they received less than the 5 hours required by the operator to fly under VFR, prior to being checked to line. Most pilots were checked to line with less than 10 hours on type.  The pilot of the accident flight and one other casual pilot had limited MEA experience prior to being checked to line, having only flown one other MEA type, which was during their flight training.

Additionally, the interim HOFO had limited hours on MEA and the C310 prior to assuming the position at Broome Aviation. They accumulated a further 57 hours of MEA operation, including 23 hours on the C310, prior to checking the pilot of the accident flight to line. However, it is likely the interim HOFO’s limited experience on the aircraft type impacted the depth and accuracy of operational guidance provided to pilots during line checks, as well as the ongoing oversight of their flying performance.

Due to the relatively complex fuel system on the C310, pilots transitioning to the aircraft type require a thorough understanding of the system’s layout, managing fuel during normal and abnormal operations, and recognising potential problems. While this knowledge can be obtained via ground‑based study of the system, supervised practice helps ensure pilots develop the necessary skills and confidence to operate the system safely and effectively in all conditions. Most pilots who flew the C310 received little to no guidance on its fuel system.

Contributing factor

During the 8-month period from November 2022 until the accident, Broome Aviation provided its pilots transitioning to operating the Cessna 310 with limited supervision, guidance and support, including management of the fuel system. (Safety Issue)

Defect reporting

Recording defects on a maintenance release (MR) allows for the timely identification, assessment, and rectification of issues that could impact an aircraft’s performance or safety. This process ensures that maintenance personnel have a clear understanding of any outstanding defects requiring attention, thereby reducing the risk of oversight or miscommunication during maintenance activities. It also records important information for pilots operating the aircraft.

Furthermore, documenting defects on a MR creates an auditable maintenance history, which is essential for tracking repairs, modifications, and inspections over the lifecycle of the aircraft. This documentation is also a regulatory requirement, ensuring compliance with regulatory standards. 

There were aircraft defects that had not been recorded on the MR, including inaccurate fuel gauges and a partially‑unserviceable autopilot. Although the operator had a process for pilots to report defects, this had generally not been followed by the pilots. The pilots advised that they would often talk to individuals in the maintenance facility after a flight about any defects or issues they had noted. Through this process, straightforward defects would likely be rectified but nothing would be written on the MR. However, defects requiring longer maintenance time and multiple parts, they reported being advised by maintenance personnel that the operator would not pay for the defect to be rectified and so consequently were not reporting them. 

This situation meant that when the pilot of the accident flight encountered defects, such as the engine surging, they did not report the concern. Consequently, this reduced the likelihood that the interim HOFO would become aware of the issue and arrange for it to be resolved, or at least communicated to the company pilots.

Of the serviceability‑related issues raised by the pilots, the fuel gauges and the autopilot were assessed to have been inoperable at the time of the flight. The interim HOFO did not themselves report the gauge defects or encourage the pilots to do so.

Contributing factor

Aircraft defects were not written on the maintenance release, leading to several defects not being rectified or managed. (Safety Issue)

Legibility and accuracy of aircraft internal placards

The fuel selector placards fitted to VH‑DAW were incorrectly labelled, with both placards indicating that the aircraft was fitted with the smaller auxiliary tanks. In addition, the placard stating that the main fuel tank should be used for 90 minutes after take-off was missing and some of the internal fuel-related placards within the cockpit of the aircraft were partially illegible. 

The ATSB determined that these issues likely did not contribute to the occurrence as the pilot was aware the aircraft had the larger auxiliary tanks, and the pilot did not notice the discrepancy between the size of the tanks and the placard. Despite that, in aircraft like the C310 with specific fuel usage requirements, fuel placarding plays a critical role in ensuring accurate operation of the fuel system.

Survival aspects

Upper torso restraints

A substantial body of research has demonstrated that wearing upper torso restraints (UTRs) in small aircraft significantly reduces the severity of injuries compared to wearing only a lap belt. In particular, UTRs reduce the risk of head, neck and upper body injuries, associated with the person’s upper body flailing forward. An NTSB study published in 2011 found that when wearing a lap belt only, a pilot was 49% more likely to receive a serious or fatal injury, compared to those wearing both the lap belt and UTR. 

The pilot of VH-DAW was not wearing the aircraft’s sash-type upper torso restraint (mounted above the pilot’s left shoulder) at the time of the accident. The pilot received significant injuries, when they impacted the dash of the C310. 

That injury outcome was consistent with the findings of previous ATSB investigations, which found that pilots or passengers in the front seats of small aeroplanes and helicopters have not always worn the available UTRs, exacerbating the severity of their injuries in many accidents (for example, ATSB investigations 199800442, 200605133, AO-2010-053, AO-2012-083, AO-2012-142, AO-2016-074, and AO-2022-027).

It is very likely that the severity of pilot’s head injuries would have been reduced if they had been wearing the available UTR.

Contributing factor

The pilot was not wearing an upper torso restraint during the accident flight, resulting in the pilot receiving avoidable serious head injuries during the collision.

Emergency locator transmitter

The CASR Part 135 Manual of Standards required aircraft that were flown more than 50 NM from the departure aerodrome to carry an automatic emergency locator beacon (ELT), however at the time of the accident there was an exemption for the aircraft to operate with a portable ELT.

A portable ELT requires manual activation during an emergency landing and on this occasion the pilot was rendered unconscious during the accident sequence and the passenger did not know the exact location of the portable ELT. Therefore it is very likely that if a forced landing of similar severity had occurred in a more remote location, notification of the accident to emergency services would have been significantly delayed. That in turn may have led to a more severe outcome for the aircraft’s occupants. 

Research conducted by the ATSB in 2013, A review of the effectiveness of emergency locator transmitters in aviation accidents identified that while automatic ELTs only activated in 40–60% of accidents in which their activation was expected, they were directly responsible for saving an average of 4 lives per year.

Operational pressures

An effective safety culture relies on open communication channels, where employees can report hazards or errors without fear of reprisal. In this case, pilots reported to the ATSB that they experienced pressure from individuals in senior management to avoid recording defects on the MR, particularly those that could lead to operational delays, and pressure to conduct flights with aircraft that they considered were unsafe for flight. The sample involved several pilots selected by the ATSB based on them performing similar roles to the pilot involved in this accident. All the information they provided was consistent with similar concerns also reported to CASA by other pilots, together with a related complaint from a passenger. 

The pressure the pilots reported experiencing led to them regularly flying aircraft with defects. With regards to the C310, pilots developed an understanding that it was normal and approved practice to conduct flights in an aircraft with inaccurate fuel gauges, an autopilot incapable of holding altitude and engines prone to surging. 

In addition, the pressure the pilots reported experiencing probably led to them being less likely to formally report defects or discuss them with senior management as they had developed an understanding that they would not be remedied.

Based on the available evidence, management personnel were not fully aware of all the aircraft defects that the pilots were managing. If the defects had been formally reported through the defect reporting process, it is more likely they would have been discussed and, if they could not be rectified, then a more considered approach developed to manage the problem. For example, the issue around fuel supplied from the auxiliary fuel tanks would probably have been investigated further, or a mitigation put in place. 

A study completed on the factors influencing the decision‑making of commercial pilots flying in outback Australia found that it was common for them to feel pressured to make risky decisions and commit ‘violations’ due to threat of employment termination. It also noted that career ambition was an important factor, with pilots seeking to build flight time for future employment with major airlines, leading them to take risks while flying (Michalski and Bearman, 2014). The extent to which this situation exists within the small aircraft air transport sector is difficult to determine, however the evidence from this investigation indicates that it existed within this operator. 

Contributing factor

Broome Aviation pilots experienced pressure not to report aircraft defects on maintenance releases, and many pilots also experienced or observed pressure from individuals within the company management to conduct flights in aircraft with defects that they considered made the aircraft unsafe for flight. (Safety Issue)

Regulatory oversight

The purpose of regulatory oversight is to ensure operators are meeting regulatory standards and to monitor the ongoing safety, health and maturity of the operators. This oversight is comprised of both regulatory services activities and surveillance activities.

CASA response to complaints

CASA received a complaint in November 2022 regarding operational issues at Broome Aviation. This complaint was included in the scope of a level 2 surveillance activity conducted by CASA in June 2023, the week prior to the accident. The CASA regulatory oversight flight operations inspector (RO FOI) determined there was no reason to question pilots regarding the complaint after noting the pilots seemed ‘happy’. This perception occurred in an open environment where the FOI, the interim HOFO and the CEO were present with the pilots. 

As CASA noted, complaints regarding the safety culture of an organisation that does not have a safety management system (SMS) can be difficult to assess. Interviews with pilots can provide valuable information, but the usefulness of that information can be limited if only a small sample size was used (and confidentiality could not be maintained), or corroboration from some form of documentary evidence could not be identified. Although there are clearly challenges with examining these types of topics during surveillance activities, on this occasion it appears an important opportunity was missed when the RO FOI did not discuss these concerns with any of the current pilots or bring it to the attention of the operator.

When the surveillance report was submitted by the RO FOI to their supervisor, the RO FOI was not questioned as to why the complaint had not been assessed, even though it was a key reason for the surveillance activity. This was a second missed opportunity for CASA to assess the safety culture within the operator.

When CASA received 2 further complaints after the accident, it had a further opportunity to examine operational issues which encompassed all 3 complaints. Although the complaints were added to the scoping of the level 1 audit in August 2023, the contents of the audit report indicated that they were again not investigated. 

Acknowledging CASA’s difficulty with assessing the safety culture of such an organisation, there were multiple pilots within the organisation who could have provided valuable insights given their extended time and familiarity with the operator. Engaging with these individuals during either of the surveillance activities would have allowed CASA to gather a broader perspective and determine whether the reported organisational issues were systemic or simply reflective of dissatisfaction from potentially disgruntled former employees. As demonstrated during this investigation, there were widespread concerns about these matters within the pilot group. 

Contributing factor

Following a complaint by a former Broome Aviation pilot regarding management pressure on pilots to operate unserviceable aircraft, CASA conducted a level 2 surveillance activity on the operator in early June 2023 and following further complaints, a level 1 audit in August 2023, with key scope elements being to evaluate the complaints. Despite that, the surveillance activities and the associated reports did not assess the subject of the complaints. 

Head of flying operations assessment

Broome Aviation’s interim HOFO was firstly assessed by CASA for the position of alternate HOFO for another operator (operator 2) and then again for the position of alternate HOFO for Broome Aviation. CASA was unable to provide documentation outlining the specific elements discussed during the first assessment, so it was not possible to confirm what was specifically covered during that process.

The retention of assessment records ensures accountability and transparency in the evaluation process, including a documented trail of decisions. This transparency is important to ensure that any regulatory approval by CASA is supported by clear, justifiable, and objective assessments. Such records also assist CASA with future assessments of the same candidate.

In this case, this first assessment was used as a basis for CASA’s alternate HOFO assessment of the same candidate for Broome Aviation 19 days later, enabling the process to be expedited. The FOI specified that this assessment was for the alternate HOFO position, however the approval given was for the HOFO position. Although CASA advised that the assessment process for an alternate HOFO and a HOFO position was the same, the FOI noted that they did not complete a full assessment of the applicant’s experience due to the expected short timeframe of the appointment. 

In addition, although no time limitations for a HOFO position could be recorded on the official approval, CASA accepted Broome Aviation’s operations manual, which nominated the substantive HOFO as the HOFO and the newly assessed HOFO in the alternate HOFO position. The operations manual also did not outline how the alternate was going to manage the dual positions while being employed for operator 2 conducting check and training for its pilots and full-time flying, and fulfil the HOFO duties for Broome Aviation. CASA was aware that the substantive HOFO would be on leave and the alternate HOFO would be the acting HOFO. 

CASA did not contact the operator at the end of the month despite only assessing the HOFO for one month. When the operator was advised that the substantive HOFO was extending their leave beyond April, they did not advise CASA of the change in circumstances within 7 days as required.

Upon discovering in February 2023 that the interim HOFO had been conducting the role for longer than the timeframe considered in the assessment, the CASA RO FOI discussed the matter with the interim HOFO. However, CASA did not re-assess the suitability of the interim HOFO to act for an extended period, and to ensure that the interim HOFO was available to effectively oversee Broome Aviation pilots when they returned to operator 2 in March 2023. 

The dual arrangement of a pilot serving as HOFO for one operator and full‑time line pilot for another, posed challenges with:

  • operational priorities
  • workload management
  • operational oversight
  • compliance with regulatory requirements.

In this instance, the interim HOFO reduced their flying duties at Broome Aviation to return to flying and conduct check and training for operator 2. The reduction resulted in the interim HOFO having reduced oversight of Broome Aviation pilots during the March–June 2023 period.

Under CASR regulations, key personnel must demonstrate the capacity to discharge their responsibilities fully and effectively. CASA emphasised that it is ‘highly unlikely’ for key personnel to meet this requirement when performing similar duties for multiple operators simultaneously. If this dual arrangement is pursued, the second operator must clearly outline in its exposition how a HOFO will fulfill their responsibilities. This includes ensuring sufficient availability and capability to respond promptly to operational demands. Although in this case CASA personnel stated concern for the operation and oversight of Broome Aviation at the time, the 4-month period in which the interim HOFO was working for both operators resulted in Broome Aviation effectively having little oversight of its pilots. 

Contributing factor

The Civil Aviation Safety Authority approved a head of flying operations (HOFO) for Broome Aviation in early December 2022 via an abbreviated assessment due to an expectation that it was an interim appointment, and they had already been assessed. The person subsequently remained in the position for a much longer period. When this was identified by CASA, it did not fully assess the HOFO’s ability to continue undertaking the position when returning to work for another operator full time as a line pilot and alternate HOFO.

Findings

ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition ‘other findings’ may be included to provide important information about topics other than safety factors. 

Safety issues are highlighted in bold to emphasise their importance. A safety issue is a safety factor that (a) can reasonably be regarded as having the potential to adversely affect the safety of future operations, and (b) is a characteristic of an organisation or a system, rather than a characteristic of a specific individual, or characteristic of an operating environment at a specific point in time.

These findings should not be read as apportioning blame or liability to any particular organisation or individual.

From the evidence available, the following findings are made with respect to the fuel starvation and forced landing involving Cessna 310R, VH-DAW, about 5 km south‑east of Derby Airport, Western Australia on 20 June 2023..

Contributing factors

  • The planned flight from Broome to Turkey Creek and return to Derby with the required fixed reserve and contingency fuel could not be achieved without refuelling the aircraft en route. In addition, the pilot did not intend to use all the available fuel in the auxiliary tanks and did not take this into consideration in their pre-flight planning, further reducing the amount of fuel available.
  • It is likely that the pilot did not utilise the right auxiliary fuel tank during the first leg of the journey and did not manage usage from the main fuel tanks in accordance with the pilot's operating handbook. This resulted in the depletion of fuel in the main tanks to a level where continuous engine operation could not be maintained
  • After the usable fuel in the right main fuel tank had been exhausted, the pilot did not divert the aircraft to the closest airport, select the left engine selection to the left auxiliary fuel tank, or maintain altitude to increase the safety margin.
  • The pilot had limited understanding of the aircraft fuel planning and in‑flight fuel management, but due to a lack of consolidation training and limited to no operational oversight these issues were not detected by the operator.
  • During the 8-month period from November 2022 until the accident, Broome Aviation provided its pilots transitioning to operating the Cessna 310 with limited supervision, guidance and support, including management of the fuel system. (Safety Issue)
  • Aircraft defects were not written on the maintenance release, leading to several defects not being rectified or managed. (Safety Issue)
  • The pilot was not wearing an upper torso restraint during the accident flight, resulting in the pilot receiving avoidable serious head injuries during the collision.
  • Broome Aviation pilots experienced pressure not to report aircraft defects on maintenance releases, and many pilots also experienced or observed pressure from individuals within the company management to conduct flights in aircraft with defects that they considered made the aircraft unsafe for flight. (Safety Issue)
  • Following a complaint by a former Broome Aviation pilot regarding management pressure on pilots to operate unserviceable aircraft, CASA conducted a level 2 surveillance activity on the operator in early June 2023 and following further complaints, a level 1 audit in August 2023, with key scope elements being to evaluate the complaints. Despite that, the surveillance activities and the associated reports did not assess the subject of the complaints.
  • The Civil Aviation Safety Authority approved a head of flying operations (HOFO) for Broome Aviation in early December 2022 via an abbreviated assessment due to an expectation that it was an interim appointment, and they had already been assessed. The person subsequently remained in the position for a much longer period. When this was identified by CASA, it did not fully assess the HOFO’s ability to continue undertaking the position when returning to work for another operator full time as a line pilot and alternate HOFO. 

Other factors that increased risk

  • The aircraft fuel gauges did not indicate accurately.
  • Broome Aviation’s operations manual did not include a procedure for recording inflight fuel calculations. As a result, pilots adopted varying methods for fuel monitoring, leading to reduced assurance of accurate fuel management. (Safety issue)

Safety issues and actions

Central to the ATSB’s investigation of transport safety matters is the early identification of safety issues. The ATSB expects relevant organisations will address all safety issues an investigation identifies. 

Depending on the level of risk of a safety issue, the extent of corrective action taken by the relevant organisation(s), or the desirability of directing a broad safety message to the aviation industry, the ATSB may issue a formal safety recommendation or safety advisory notice as part of the final report.

All of the directly involved parties were provided with a draft report and invited to provide submissions. As part of that process, each organisation was asked to communicate what safety actions, if any, they had carried out or were planning to carry out in relation to each safety issue relevant to their organisation. 

Descriptions of each safety issue, and any associated safety recommendations, are detailed below. Click the link to read the full safety issue description, including the issue status and any safety action/s taken. Safety issues and actions are updated on this website when safety issue owners provide further information concerning the implementation of safety action.

In-flight fuel management

Safety issue number: AO-2023-029-SI-01

Safety issue description: Broome Aviation’s operations manual did not include a procedure for recording inflight fuel calculations. As a result, pilots adopted varying methods for fuel monitoring, leading to reduced assurance of accurate fuel management.

Organisational pilot supervision

Safety issue number: AO-2023-029-SI-02

Safety issue description: During the 8-month period from November 2022 until the accident, Broome Aviation provided its pilots transitioning to operating the Cessna 310 with limited supervision, guidance and support, including management of the fuel system.

Aircraft defect recording

Safety issue number: AO-2023-029-SI-03

Safety issue description: Aircraft defects were not written on the maintenance release, leading to several defects not being rectified or managed.

Organisational pressure

Safety issue number: AO-2023-029-SI-04

Safety issue description: Broome Aviation pilots experienced pressure not to report aircraft defects on maintenance releases, and many pilots also experienced or observed pressure from individuals within the company management to conduct flights in aircraft with defects that they considered made the aircraft unsafe for flight.

Glossary

ACAdvisory circular
AMC Acceptable means of compliance
AME Aircraft maintenance engineer
AOCAir operators’ certificate
AWBAirworthiness Bulletin
BAMBroome Air Maintenance
CAOCivil Aviation Order
CASA Civil Aviation Safety Authority
CASRCivil Aviation Safety Regulation
CEOChief executive officer
ELTEmergency locator transmitter
FDPFlight duty period
FOIFlight operations inspector
FORFlight operations regulations
FQISFuel quantity indicating system
GMGuidance material
HAMCHead of maintenance control
HOFOHead of flying operations
ICUSIn command under supervision
IFRInstrument flight rules
IPCInstrument proficiency checks 
LAMELicenced aircraft maintenance engineer
MCMMaintenance control manual
MEAMulti engine aircraft
MELMinimum equipment list
MOSManual of standards
MRMaintenance release
POHPilot operating handbook
RO FOIRegulatory oversight flight operations inspector
RPTRegular public transport
SMSSafety management system
SOMSystem of maintenance
STCSupplement type certificate

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the pilot and passenger of the accident flight and multiple other company pilots
  • the head of flying operations at the time of the accident
  • the operator and substantive head of flying operations of Broome Aviation
  • Civil Aviation Safety Authority (CASA)
  • Western Australia Police Force
  • Textron Aviation
  • the maintenance provider for VH-DAW (Broome Air Maintenance)
  • the maintenance tracking provider and logbook controller for Broome Aviation (Avtrac Maintenance Tracking)
  • Airservices Australia
  • video footage of the accident flight and other photographs and videos taken on the day of the accident
  • recorded data from the GPS unit on the aircraft.

References

National Transportation Safety Board 2011, Airbag performance in general aviation restraint systems, Safety Study NTSB/SS-11/01.

Stothard C & Nicholson R 2001, Skill acquisition and retention in training: DSTO support to the army ammunition study, Defence Science and Technology Organisation, report DSTO-CR-0218.

Wickens CD, Hollands JG, Banbury S & Parasuraman R 2013, Engineering psychology and human performance, 4th edition, Pearson Boston, MA.

Submissions

Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report. 

A draft of this report was provided to the following directly involved parties:

  • the pilot
  • other pilots interviewed during the investigation
  • Broome Aviation
  • Civil Aviation Safety Authority
  • Textron Aviation
  • National Transport Safety Bureau
  • Broome Air Maintenance

Submissions were received from: 

  • the pilot
  • other pilots interviewed during the investigation
  • Broome Aviation
  • Civil Aviation Safety Authority
  • Textron Aviation
  • Broome Air Maintenance

The submissions were reviewed and, where considered appropriate, the text of the report was amended accordingly.

Purpose of safety investigations

The objective of a safety investigation is to enhance transport safety. This is done through: 

  • identifying safety issues and facilitating safety action to address those issues
  • providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.

It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.

Terminology

An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.

Publishing information

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Commonwealth Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this report is licensed under a Creative Commons Attribution 4.0 International licence.

The CC BY 4.0 licence enables you to distribute, remix, adapt, and build upon our material in any medium or format, so long as attribution is given to the Australian Transport Safety Bureau. 

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.

[1]      Instrument flight rules (IFR) are a set of regulations that permit the pilot to operate an aircraft in instrument meteorological conditions (IMC), which have much lower weather minimums than visual flight rules (VFR).

[2]      MAYDAY: an internationally recognised radio call announcing a distress condition where an aircraft or its occupants are being threatened by serious and/or imminent danger and the flight crew require immediate assistance.

[3]      The substantive HOFO held the position with the operator prior to December 2022 and after June 2023. 

[4]      The interim HOFO held the position from December 2022 to June 2023.

[5]      Broome Aviation was in a transitional state to the Civil Aviation Safety regulations Parts 119 and 135 requirements and still used a document known as an operations manual rather than the exposition required by the new regulations.

[6]      VMCA: the minimum speed, while in the air, that directional control can be maintained with one engine inoperative.

[7]      An imperfection that impairs the structure, composition, or function of an object or system of an aircraft or component.

[8]      Inoperative: an item for a flight of an aircraft is inoperative if, due to a defect, the item, or a function of the item, does not accomplish its intended purpose, or consistently function within the operating limits or tolerances mentioned in the approved design for the item or the flight manual for the aircraft.

[9]      Under previous legislation, air transport operations were split into regular public transport (RPT) and charter flights.

[10]    Elevator flutter: refers to an uncontrolled, rapid oscillation or vibration of the elevator control surface. This phenomenon can occur due to aerodynamic forces, structural dynamics, or a combination of factors.

[11]    The Cessna 310R POH detailed numerous fuel flow rates for specific power settings.

[12]    This was a conservative rate of fuel burn as the engine manufacturer could not give an expected fuel return rate as this was dependent of the engine power used and the conditions on the day. 

[13]    Medical restriction, as defined by the operator, was any condition that required the carriage of an additional flight crewmember.

[14]    CASA EX87/21 was an exemption instrument providing certain operators with deferrals from specific requirements of the Flight Operation Regulations particularly concerning safety management systems, human factors principles & non‑technical skills, and training & checking. The deferrals applied to certain operators only and were subject to conditions.

[15]    Upper torso restraint: a shoulder strap or harness. A shoulder strap, when paired with a lap belt, effectively makes the occupant’s restraint similar to the seatbelt on modern cars.

[16]    Portable ELT: An emergency locator transmitter that is manually activated by a pilot or passenger when in distress.

[17]    Automatic fixed ELT: An emergency locator transmitter that is permanently attached to the aircraft and designed to stay attached even after a crash to aid Search and Rescue (SAR) teams in locating a crash site.

[18]    Flight operations manager: plans, coordinates and controls all operational activities of all aircraft movement.

[19]    HAMC: monitors and records aircraft hours, cycles and equipment maintenance and other information relevant to maintenance scheduling. Coordinates defect rectification and unscheduled maintenance activities. Reviews Airworthiness Directives for applicability and compliance.

[20]    Under CASR Part 119.080(1)(c) – Conditions of an Australian air transport AOC, the operator was required to fill the HOFO position at all times and the person fulfilling the role was to be approved by CASA (whether the permanent HOFO, a permanent alternate HOFO, or a person temporarily filling the position as an interim HOFO).

[21]    Broome Aviation did not have an exposition at this time – the time limitation should have been stated in the operations manual.

Occurrence summary

Investigation number AO-2023-029
Occurrence date 20/06/2023
Location About 5 km south-east of Derby Airport
State Western Australia
Report release date 30/04/2025
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Forced/precautionary landing, Fuel starvation
Occurrence class Accident
Highest injury level Serious

Aircraft details

Manufacturer Cessna Aircraft Company
Model 310R
Registration VH-DAW
Serial number 310R0148
Aircraft operator Broome Aviation Pty Ltd
Sector Piston
Operation type Part 135 Air transport operations - smaller aeroplanes
Departure point Turkey Creek Aircraft Landing Area, Western Australia
Destination Derby Airport, Western Australia
Damage Substantial

Fuel starvation and ditching involving Piper PA-28, VH-FEY, 15 km north-west of Jandakot Airport, Western Australia, on 20 April 2023

Final report

Report release date: 28/11/2023

Executive summary

What happened

On 20 April 2023, a Piper PA-28-181 ‘Archer’ aircraft, registered VH-FEY, departed Carnarvon, Western Australia for a private flight with the owner-pilot and 2 passengers on board. The aircraft initially proceeded to Geraldton to drop off one of the passengers before continuing to Jandakot (Perth). Based on the conduct of previous similar flights, and the aircraft departing Carnarvon with full fuel tanks, the pilot considered there was sufficient fuel remaining for the return journey to Jandakot and did not refuel at Geraldton.   

The pilot departed Geraldton and tracked to Jandakot via the generally direct route aligned with the coast, which was essentially the reciprocal of the track flown the day before. After cruising at 5,500 ft, the pilot descended to 4,000 ft then 2,000 ft, because of airspace restrictions.  

At about 10 km north of Fremantle, as the pilot was tracking coastal over water, engine power subsided to idle power over a couple of seconds then recovered to cruise power. In response, the pilot selected the mixture control to full RICH and carburettor heat to ON. (The electric fuel pump was already selected ON.)

Engine power then subsided and recovered a number of times over a period of about 2 minutes. There were no indications of a mechanical failure and the pilot looked at the instruments but was unable to recall any indications after the event.

The pilot was unable to maintain height and decided to turn into wind for a forced landing on the adjacent beach but there were a number of people on the beach. Instead, the pilot decided to ditch the aircraft in the ocean as close to shore as possible.

As they were approaching the water, the pilot tried to hold the nose up as far as possible. A main wheel contacted the water and the aircraft skipped along the surface for a few seconds. Then the right wing dropped rapidly, consistent with a stall, and dug into the water, quickly stopping the aircraft. Water gushed up over the front of the aircraft and windscreen.

The pilot and passenger exited the aircraft uninjured and swam to shore.

What the ATSB found

The pilot departed Carnarvon with sufficient fuel for the intended flight to Jandakot via Geraldton but did not carry out regular fuel quantity checks in accordance with regulatory guidance or keep a written log of the fuel consumed from each tank during the flight.  

During cruise at 1,900 ft, engine power subsided to low power then returned to normal power. This occurred a number of times, probably because of a lack of usable fuel in the selected (right) tank.

The pilot responded to the engine power anomalies by carrying out some of the emergency procedures but did not select the other (left) tank, which contained usable fuel. Consequently, engine power was not restored, and the pilot carried out a forced ditching into the ocean near a beach.

Prior to the first departure from Geraldton on the day of the occurrence, the pilot drained a significant amount of water from both fuel tanks (that had been refuelled to full the night before) and from the fuel strainer. The aircraft was subsequently operated for over 6.5 hrs with a refuelling at Carnarvon without any symptoms of fuel contamination and it is unlikely that there was a significant amount of water remaining in the fuel.

The engine had been in service for 28 years since overhaul and 13 years since a bulk strip, which was more than double the recommended time before overhaul of 12 years. However, given no engine defects were identified and the required maintenance was carried out, this was not identified as a factor in that occurrence.   

Safety message

Fuel management

EFB and GPS technology have enhanced flight planning and navigation capability, but pilots are still required to carry out in-flight fuel quantity checks at regular intervals. These should include a cross check of all available data, including fuel quantity indications, and be recorded. For aircraft with separate tank selections, it is advisable to monitor the fuel consumed, and fuel remaining, for each tank.  

Although the fuel gauges in older light aircraft can be unreliable and should not be the sole source of fuel quantity information, they are an essential component in fuel management processes. As such, they should be maintained in a serviceable condition with regular pre-flight and post-flight validation against known fuel quantities. If a fuel gauge indicates an unexpectedly low fuel quantity, the pilot should consider that to be a valid indication and act accordingly, until the anomaly is resolved.   

Emergency procedures

Relative to a complete engine power loss, an intermittent or partial engine power loss is an ambiguous condition that can disrupt pilot implementation of emergency procedures. Unless there is an obvious solution, pilots should prepare for a complete engine power loss and follow the applicable procedures to optimise recovery of engine power.             

If pilots might be required to ditch in case of an emergency, they should be familiar with the applicable procedures in the POH, as available, and/or generic guidance produced by national aviation authorities.

Engine time before overhaul

Although continued private operation is conditionally permitted for aeroplane engines that have exceeded the recommended calendar time before overhaul, operators should consider the length of the extension, modification status, and associated risk of failure.

 

The investigation

Decisions regarding the scope of an investigation are based on many factors, including the level of safety benefit likely to be obtained from an investigation and the associated resources required. For this occurrence, a limited-scope investigation was conducted in order to produce a short investigation report and allow for greater industry awareness of findings that affect safety and potential learning opportunities.

The occurrence

The owner-pilot of a Piper PA-28-181 ‘Archer’ aircraft, registered VH-FEY, planned to conduct a flight from Jandakot to arrive in Carnarvon, Western Australia (WA) on 20 April 2023 to observe an eclipse of the sun at about 1130 local time, then return to Jandakot. This was a private operation under the visual flight rules.[1]

Previous flights

On the day before the eclipse, the pilot with one passenger on board, departed Jandakot Airport at 1416 and tracked to Geraldton Airport. The pilot landed at 1617 and parked in the general aviation area. Soon after arrival, the aircraft was attended by a refueller and Avgas tanker which replenished both fuel tanks (65 L added). The pilot and passenger then left the airport for their overnight accommodation.

At 0806 the next day, the pilot and 2 passengers arrived at the aircraft. The pilot advised that during the preflight inspection, water and a number of solid particles were visible in fuel samples drained from both tanks and the fuel strainer (gascolator). A number of fuel drains were carried out until the samples were free of water. The pilot estimated that the total amount of water drained from the aircraft fuel system was in the order of 500 ml.  

Although the pilot was concerned about the amount of water that had been drained from the fuel system, they considered that the system was free of water and there should be no effect on the aircraft. The pilot conducted the usual engine run ups, did not identify any problems, and departed for Carnarvon at 0831.

The aircraft tracked direct towards Carnarvon and climbed to 6,500 ft. At about 90 NM (170 km) from Carnarvon, the pilot diverted to Shark Bay aerodrome, landing at 1020. The aircraft departed Shark Bay at 1031 and tracked to Carnarvon, landing at 1108. Engine operation during both sectors was reported as normal.              

Both fuel tanks were replenished by a refueller and Avgas tanker (81 L added). The pilot and 2 passengers experienced the eclipse and obtained lunch near the airport. When the pilot carried out a fuel drain on return to the airport, there was no water found in the samples from the tanks but there was a small amount of water drained from the fuel strainer.

At 1239, the aircraft departed Carnarvon with the pilot and 2 passengers for Jandakot via Geraldton to drop off a passenger. The aircraft track was generally direct to Geraldton and the average cruise altitude was 7,500 ft. The pilot joined the circuit at 1452 and landed at 1455. Engine operation during the flight was reported as normal.                  

The occurrence flight

After a quick stop without refuelling, the pilot and 1 passenger boarded for the flight to Jandakot. The pilot recalled that as they advanced the throttle at the start of the take-off roll, there was an unusual ‘cough’ from the engine. Given it was a long runway and the engine reached full power, the pilot continued the take-off roll while monitoring the engine. It sounded normal and the temperatures and pressures were in the green operating ranges, so the pilot continued the take‑off.

The pilot departed Geraldton at 1513 to track to Jandakot via the generally direct route aligned with the coast, similar to the reciprocal track flown the day before. To take advantage of a forecast tailwind, the pilot climbed to cruise at 5,500 ft.  

At 1559, the pilot began descent to about 4,000 ft to avoid restricted airspace near Lancelin. A further descent to 2,000 ft was initiated at 1612.

By 1632, the aircraft had reached 2,000 ft and was crossing the coast near Ledge Point (120 km north-north-west of Jandakot Airport) to track coastal over water. For the next 30 minutes the aircraft proceeded down the coast at about 2,000 ft.

The pilot advised the ATSB that they were just about to make a routine radio transmission about 10 km north of Fremantle for any traffic in the area, when engine power subsided to idle power over a couple of seconds then recovered to cruise power. (A descent, heading change, and groundspeed reduction were recorded at 1705.)   

In response, the pilot selected the mixture control to full RICH and carburettor heat to ON. The electric fuel pump was already selected ON.

Engine power then subsided and recovered several times over a period of about 2 minutes. The pilot recalled there was no roughness or indications of a mechanical failure, and it seemed like the engine was responding to the throttle being moved (without any throttle movement).  

The pilot tried different throttle settings for 20–30 seconds without any reported effect. The pilot recalled looking at the engine instruments and thinking of the need to look at the fuel quantity indicators but after the occurrence could not recall any indications.    

At this stage, the aircraft had descended to about 1,200 ft and the pilot assessed that the aircraft would not be able to reach Jandakot Airport, which was about 18 km to the south-east. The pilot also decided against trying to reach the Swan River, which was about 4 km to the south‑south‑east and on the other side of a built-up area.

Now at about 1,000 ft, the pilot observed that they were not far from Leighton Beach. Considering that the surface wind was coming from the north-east, the pilot decided to turn into wind and land on the beach (Figure 1). During the turn however, the pilot noticed there were people all over the beach and that the plan was unworkable.

Instead, they decided to ditch the aircraft in the ocean as close to shore as possible to minimise their swimming distance. The pilot recalled trying to line up with the crest of the waves in accordance with generic ditching guidance.    

At 500 ft, the pilot realised that no one had been advised of the emergency and made a MAYDAY call to Melbourne Centre. Shortly afterwards, the passenger asked if the door should be unlatched, and this was carried out.  

By the time the turn had been completed, at about 300 ft, the engine had completely lost power and the propeller stopped turning shortly afterwards. The last data point was recorded at 1709.      

Figure 1: Aircraft track from engine fluctuations to ditching

Figure 1: Aircraft track from engine fluctuations to ditching

Source: Google Earth (Annotated by the ATSB)

The pilot recalled that as they were approaching the water, they tried to hold the nose up as far as possible to prevent the nosewheel contacting first and flipping the aircraft forward. When about 20–30 ft above the water the stall warning activated. To the pilot that meant the airspeed was probably about 50 kt or less but they were watching the water and did not look at the air speed indicator.

With the stall warning still going, a main wheel contacted the water and the aircraft skipped along the surface for a few seconds. Then the right wing dropped rapidly consistent with a stall and dug into the water, quickly stopping the aircraft. Water gushed up over the front of the aircraft and windscreen.

Figure 2: VH-FEY ditching touchdown

Figure 2: VH-FEY ditching touchdown

Source: Image extracted from Channel 9 News footage

The pilot and passenger were not injured and got out of the aircraft to stand on the wing. Some people swam out from shore to check if they were okay. When the aircraft began to sink after a couple of minutes, they swam to shore.

Context

Pilot information

The pilot began flight training in August 2020 and was issued with a private pilot licence (aeroplane) in November 2021 and a commercial pilot licence (aeroplane) (CPL(A)) in September 2022. To gain the flying experience required for a CPL(A), the pilot acquired VH-FEY in March 2022 and operated the aircraft on several long flights within WA. At the time of the occurrence, the pilot’s total flying experience was 360 hours.  

The pilot held a Class 1 Medical certificate that was due to expire on 2 May 2023. This specified a requirement for the pilot to wear distance vision correction.    

Meteorology

The ATSB obtained aviation meteorological information from the Bureau of Meteorology.  

From the initial graphical area forecast (GAF) for southern Western Australia on the day of the occurrence (valid 1300 to 1900 local time), visibility was forecast to be greater than 10 km, except where it was 4,000 m due to isolated smoke south of Kalbarri. In a later issue of the GAF, the area of isolated smoke had contracted to potentially affect the flight south of Ledge Point, 65 NM (120 km) north of Jandakot.

The low-level grid point wind and temperature (GPWT) forecast issued at 0837 on 20 April 2023, indicated that at 1500, the following winds were expected at 5,000 ft and 7,000 ft respectively:

  • Carnarvon to Geraldton from the north-east at 12 kt and 16 kt  
  • Geraldton to Jandakot from the north and north-west at 6 kt and 10 kt.

On 20 April 2023, at 1700 (5 minutes before the engine power loss), the automatic weather station at Swanbourne (5 km east of the engine power loss position) recorded the surface wind from the east at 5 to 8 kt. The recorded temperature was 23.8° and dewpoint 6.6°. When plotted on the Carburettor icing probability chart produced by CASA, the result was serious icing – descent power. 

To ascertain the risk of water contamination due to rainfall, the ATSB accessed records of daily weather observations for Jandakot and Geraldton. At Jandakot, in the 4 weeks prior to the occurrence, a total of 67.6 mm of rain was recorded over 12 days. At Geraldton, there was no rain recorded on 19 and 20 April 2023.

Aircraft and systems

The Piper Aircraft Corporation manufactured the PA-28-181 aircraft in the United States in 1975. It was first registered in Australia in 1977.

The aircraft was powered by a Lycoming O-360-A4M piston engine and fixed pitch propeller.

A metal tank in each wing contained 24 US Gals (90 L) of usable fuel. Fuel was piped from the single outlet of each tank to a 3‑position fuel selector (OFF/LEFT/RIGHT) located on the left side‑panel (forward of the pilot’s seat), then to the fuel strainer, fuel pumps, and carburettor.  

Normal operating procedures

The PA-28-181 Pilot’s Operating Handbook, issued in 1975 and last updated in 2019, advised that the fuel system should be drained daily prior to first flight and after refuelling to avoid accumulation of water or sediment. To drain the lines from the tanks, the tank selector is switched from each tank in turn, and the fuel strainer drain valve open.  

In normal operation, the electric fuel pump was to be selected ON before take-off and deselected on reaching the desired altitude. Then, for approach and landing, the electric fuel pump was to be selected ON. It was also recommended that the electric fuel pump be selected ON while changing fuel tank selection. Otherwise, the electric fuel pump should normally be OFF so that any malfunction of the engine-driven fuel pump was immediately apparent.      

The POH advised that, to keep best lateral trim for the flight, fuel should be used alternately from each tank at 1-hour intervals. It further recommended that one tank be used for 1 hour after take‑off, then the other tank used for 2 hours before returning to the first tank. At that point, the first tank will contain approximately 1.5 hrs of fuel and the second tank approximately 0.5 hr. There was a caution to not run tanks completely dry in flight.       

To reduce fuel consumption in cruise, the POH recommended that the mixture should be leaned above 5,000 ft and at pilot discretion at lower altitudes when 75% or less power was being used. Leaning was carried out by pulling the mixture control back until the engine operation became rough then advancing it until smooth running was restored.

If an exhaust gas temperature gauge was fitted, as it was to VH-FEY, the Lycoming Operator’s Manual recommended leaning to 150°F on the rich side of peak EGT for maximum power cruise or to peak EGT for best economy cruise.        

Operational practices

The pilot confirmed that their usual practice was to change fuel tank selection every hour and that this was prompted by the fuel gauge indicating 10 US Gals had been consumed. In practice, when starting with full tanks, the first and second tank changes would be when each tank indication was 20 US Gals in turn and the third and fourth at 10 US Gals.

Although the fuel gauges were calibrated a few months before the occurrence and were not reported as defective, the pilot did not rely on the gauges and considered them to only be a guide. To establish fuel on board, the pilot used a dipstick before or after flight. The pilot did not verify the accuracy of the fuel gauges by cross referencing the quantities with dipstick or refuelling figures.      

The pilot advised that the mixture was left in RICH until top of climb then leaned to a setting that was slightly rich of peak EGT and was producing smooth engine operation. For descent, the pilot’s practice was to keep the mixture leaned and adjust as required to keep the engine smooth.

When the pilot operated the aircraft at higher altitudes and leaned the mixture as much as possible, the average fuel consumption rate calculated post-flight was consistently 30 L/hr. If operating at lower altitudes without leaning, the aircraft used more fuel.

The pilot reported that, based on the advice of an experienced instructor, their practice was to select the electric fuel pump ON for the entire flight to avoid any power interruptions if the engine‑driven pump failed.

Management of the flight

The pilot advised that a few days before a flight they usually used an EFB application to calculate estimates of flight times. Prior to departure from Jandakot, a flight plan was compiled manually as per their usual practice.   

During the flight to Carnarvon via Geraldton and Shark Bay, the pilot did not consistently use the flight plan/navigation log or look at the map. The pilot advised that this was unnecessary because they were familiar with the route, having conducted the flight multiple times.   

For the return flight to Jandakot, the pilot advised that they did not compile a flight plan or maintain a fuel log. After each of the previous flights from Carnarvon, the pilot had dipped the tanks and measured about 50–60 L remaining so expected that to be the outcome unless there was a strong headwind. As the flights from Jandakot to Carnarvon had consumed a total of 146 L, and there was no extensive ground running or stopover at Shark Bay on the return journey, the pilot expected that the fuel consumed on the return would be less than that figure. In that case, the fuel remaining on arrival at Jandakot was expected to be more than 34 L.     

The pilot was monitoring progress of the flight using the EFB application.

Fuel quantity analysis

The ATSB obtained flight data that was transmitted at regular intervals from the on-board EFB application to the associated server via the mobile phone network. That data allowed for calculation of flight times[2] and in combination with refuelling records, the average[3] fuel consumption rate for the previous sectors.   

On the first sector from Jandakot to Geraldton, the approximate fuel consumption rate was calculated as 32 L/hr (based on a flight time of 123 minutes and fuel add of 65 L). This flight was preceded by extended ground running so the consumption rate based on the flight time might have been marginally lower.

On the second flight from Geraldton to Carnarvon via Shark Bay, the average fuel consumption rate was calculated as 33 L/hr (based on a combined flight time of 147 minutes and fuel add of 81 L). This fuel consumption rate was applied to the return flight from Carnarvon because it was conducted in similar conditions.     

The combined flight time from Carnarvon to Geraldton then to the engine power loss was 4 hrs and 15 minutes. At 33 L/hr, the estimated fuel burn was 140 L. Therefore, when the engine lost power, the estimated fuel on board was 40 L (Full fuel at Carnarvon: 180 L).

To establish the approximate distribution of fuel as the flight progressed from Carnarvon, the ATSB compiled a fuel log based on the pilot’s recollection of the fuel tank selections. From the flight data, the ATSB identified the time that the aircraft was at the pilot-nominated locations to identify an approximate time for each tank change. That data was inserted into the fuel log to retrospectively track the fuel burn and fuel on board as the flight progressed (Table 1).

Table 1: Retrospective fuel log for Carnarvon – Geraldton – Engine power loss

Table 1: Retrospective fuel log for Carnarvon – Geraldton – Engine power loss

1 Take-off at Carnarvon on right tank

2 At about bottom end of Shark Bay switched to left tank

3 At about Kalbarri switched back to right tank

4 Landed at Geraldton on right tank

5 Start, taxi, and take-off at Geraldton on left tank

6 At about Cervantes switched to right tank

7 Engine power loss (right tank)

8 Estimated usable fuel remaining in right tank

The ATSB notes that the retrospective fuel log is based on an average fuel consumption rate and approximate timing of tank changes. As such, it is only indicative of the fuel on board in each tank at each change and at the time of the engine power loss. (If the left tank had been selected for 11 minutes more over the 2 periods of use, the left/right fuel balance would be 40/0 L.)      

The pilot believed that the right fuel gauge was showing just under 10 US Gals remaining when it was selected before the occurrence (at 1610), but was not certain of this after the occurrence. Based on the retrospective fuel log and fuel calibration figures (Table 2), the right fuel gauge would have indicated between the 5 and 10 US Gals markings.

After the occurrence, the pilot estimated that when the engine loss occurred there was about 40 L (or 10 US Gals) in the left tank and 15–20 L in the right tank.  

If the flight had continued without the engine power loss, operation for the additional flight time of approximately 15 minutes would have consumed a further 8 L (at 33 L/hr). In that case the total fuel on board after landing would have been about 32 L, which equated to an hour of flight time.  

Fuel management guidance

CASA provided guidelines for aircraft fuel requirements in Advisory Circular AC 91-15 v1.1. The following information is adapted from the AC and selected for applicability to Day VFR operation of a light aircraft, such as a Piper PA-28-181.

Pilots were advised to operate in accordance with known or estimated fuel consumption data. This could be sourced from the aircraft/engine manufacturer or taken from recent historical consumption records.

The usable fuel required at the commencement of a Day VFR flight consisted of the taxi and trip fuel expected to be consumed, and final reserve fuel (30 minutes operation at 1,500 ft above aerodrome elevation) to be protected until landing. It was expected that additional fuel would be carried for contingencies.  

According to the AC, the pilot must determine the amount of usable fuel on board before commencing a flight. Unless fuel quantity can be assured and verified (for example, full tanks), pilots should use the best available cross-check process. Those checks applicable to aircraft without ‘fuel consumed indicators’ were:

  • after refuelling and having regard to any recorded post-flight fuel quantities, a check of the cockpit fuel quantity indications or visual readings against the refuelling uplift readings
  • when a series of flights is undertaken by the same pilot and refuelling is not carried out at intermediate stops, checking of the cockpit fuel quantity indications against computed fuel on board.

The AC cautioned that fuel gauges, particularly on smaller aircraft, may be unreliable. Therefore, placing sole reliance on a fuel quantity gauge to assess fuel quantity and not cross-checking fuel quantity from a second source, increases the risk of being unable to determine actual fuel remaining should the fuel quantity indication system become faulty.

In-flight fuel management was described as continual validation of planning assumptions that influence fuel usage and required fuel reserves. As part of in-fight fuel management, the pilot must ensure that fuel quantity checks are carried out at regular intervals to:

  • compare planned fuel consumption and actual fuel consumption
  • determine the amount of usable fuel remaining
  • determine whether the usable fuel remaining is sufficient
  • determine the amount of usable fuel expected to be remaining when the aircraft lands at the destination aerodrome.

In-flight fuel quantity checks must include a reconciliation of the fuel remaining indicated from available aircraft fuel quantity indication systems and these should also be checked to confirm fuel balance and fuel tank quantity.

It was implied that the in-flight fuel checks would be recorded in some way such as flight plan or fuel log written entry, to allow a time-based reference to previous in-flight fuel checks for trend identification.

In all instances, it was highly recommended that the post-flight fuel quantity be determined and recorded.  

Aircraft maintenance

The last periodic maintenance inspection was carried out in October 2022. At that time the aircraft total time in service was 7,421.3 hours.

Recent maintenance certified on 10 February 2023 included calibration of the fuel quantity indication system. The results were recorded in the aircraft logbook and on a placard above the fuel gauges (Table 2). For each increment marked on the gauges as US gallons, there is a corresponding figure for usable fuel in litres. In the brackets are the figures from the previous calibration carried out on 28 December 2018.

Table 2: Fuel calibration record VH-FEY

Gauge (US Gals)E5101520Full
Left (L)035 (35)60 (55)73 (60)83 (75)93 (86)
Right (L)026 (30)53 (50)69 (60)78 (70)89 (86)

The ATSB notes that when each fuel gauge indicated 5 US Gals during the calibration process, the right tank contained 26 L and left tank contained 35 L. At the average fuel consumption rate of 33 L/hr (utilised in the retrospective fuel log), this equated to 47 minutes and 63 minutes flying time respectively. So, for the same fuel gauge indication of 5 US Gals, the right tank would yield 16 minutes less flying time than the left.    

A review of the aircraft logbooks found 2 entries for removal and reinstallation of the right fuel tank in 1989 and 1993. These were the only records that could be associated with installation of a non‑conforming outlet fitting to the right fuel tank (see the section titled Wreckage recovery and examination).    

The engine was last overhauled and installed in 1995 when the aircraft total time in service was 5,972.9 hours. As of the last periodic inspection, the engine had been operated for 1,449 hours and 28 years since overhaul.

In 2010, the engine was removed, bulk stripped, and reinstalled. Since then, and up to the last periodic inspection, the aircraft had been operated for 426 hours and 13 years.

Since the bulk strip in 2010, the carburettor had been repaired, and various components such as the engine driven fuel pump and magnetos had been replaced or overhauled.   

The engine manufacturer issued a service instruction that specified time between overhaul (TBO) schedules. It included:

  • All engine models were to be overhauled within 12 calendar years of the date they first entered service or of last overhaul.
  • For the Lycoming O-360 type fitted to VH-FEY, the operating-hour TBO was 2,000 hours.

Although the engine had exceeded the calendar time TBO period, the registered operator (owner-pilot) of VH-FEY continued to operate the aircraft. This was permissible for private category operations when the engine was maintained in accordance with the Civil Aviation Safety Authority (CASA) ‘on-condition’ maintenance requirements. At the last annual inspection in October 2022, the maintenance organisation had fulfilled those requirements by completing a piston engine condition report that verified engine serviceability.

Wreckage recovery and examination

Prior to initiation of ATSB investigation

The aircraft was recovered from the ocean to the nearby beach by a salvage company. Disassembly of the aircraft for transport was supervised by a licensed aircraft maintenance engineer (LAME) with the support of the salvage company. They related the following details:   

  • both fuel tanks were full of fluid
  • the fuel tank drains were not leaking
  • there was a distinctive smell of Avgas when the right fuel cap was removed
  • the contents of both fuel tanks were drained from each standard drain point into an empty semi-transparent intermediate bulk container (IBC)
  • on completion of draining tank contents into the container there was a demarcation between the upper 25–35 mm of fluid and the remainder below
  • the fluid in the upper layer was consistent with Avgas and the lower level was sea water.

Based on the estimated depth of the upper layer of fluid in the IBC, the quantity of Avgas drained from the fuel tanks was in the order of 30–42 L. It was not possible to differentiate between the amount of fuel drained from the left and right tanks. The container was subsequently used for recovery of other fluids by the salvage operator so no further information about fuel tank contents was available.      

The wings and stabilator were removed and the aircraft was then transported along the beach to storage at the salvage operator’s yard.   

ATSB examination

The ATSB initiated an investigation on 2 May 2023 and carried out examinations of the engine and aircraft fuel system at the storage facility. Forward of the firewall, this included:

  • basic engine condition and mechanical continuity
  • fuel strainer, engine driven fuel pump and carburettor
  • air filter, airbox and carburettor heat mechanism
  • magneto-engine timing and spark plugs
  • exhaust and muffler
  • oil filter

No engine defects were identified. The fuel strainer contained primarily sea water with a small amount of Avgas. The gauze filter was about 10–15% occluded by an unidentified white paste. The carburettor bowl was drained and was all sea water.

The carburettor, engine driven fuel pump, magnetos, and oil filter were removed for further examination. This was carried out and, other than saltwater residue, there were no defects or anomalies, and the components were probably serviceable at the time of the occurrence.

Examination of the aircraft fuel system was focussed on the right fuel tank assembly and fuel line to the selector. The right tank outlet fitting did not incorporate a ‘finger’ strainer, which was a non‑conformance with the fuel system data in the PA-28 parts catalogue. This outlet fitting was a different type to the conforming left tank outlet. No foreign object or evidence of contamination was found in the right tank.

Figure 3: VH-FEY Fuel tank outlet fittings - left with finger strainer and right without finger strainer

Figure 3: VH-FEY Fuel tank outlet fittings - left with finger strainer and right without finger strainer

Source: ATSB

The ATSB considered the absence of a finger strainer in the only outlet from the right tank increased the risk of foreign object obstruction to fuel flow from the tank. This scenario would require an object of about the size of the internal diameter of the outlet fitting, which was stepped from 10 mm to 7 mm. Given there were no foreign objects found in the tank and no openings in the tank that would allow migration of any objects post-ditching, this scenario was considered highly unlikely. In addition, the aircraft manufacturer advised that there were no service difficulty reports or occurrences associated with the finger strainer (72091-000).

The fuel line from the right tank through the fuel selector to the fuel strainer was unobstructed. No defects were identified in the fuel selector, which was in the right tank position consistent with the pilot account.   

The fuel sender unit was removed from the right tank and was in good condition. Given the immersion in sea water and removal of the wings it was not feasible to functionally test the fuel quantity indication system.

Although the wing flaps had been removed as part of the recovery operation, fuselage damage indicated the flaps were retracted during the ditching. This was consistent with the LAME’s recollection and the pilot’s account.     

Geraldton Airport related

In response to the pilot account of significant water drained from the aircraft fuel system at Geraldton Airport on the morning of 20 April 2023, the ATSB sought information about possible sources of contamination at the airport.

The airport refueller advised that the usual quality checks were carried out to the tanker on the morning of 19 April 2023 and this was supported by their records. There was no report of water and the refueller advised that there was no history of this occurring.

The ATSB contacted the operator of an aircraft refuelled before VH-FEY who advised that no water had been detected from the post-refuelling fuel drains and normal operation was experienced on the subsequent flight.         

Geraldton Airport is a security-controlled airport that required authorised access to airside areas. One of the CCTV cameras at the terminal was directed towards the aircraft parking area utilised by the pilot of VH-FEY.

The ATSB requested CCTV data for the period from aircraft arrival on the 19 April 2023 to departure on 20 April 2023. Due to the timing of the data recovery, data for 19 April 2023 was unavailable. The CCTV available from 0804 on 20 April 2023 showed the pilot and passengers arriving at the aircraft, some pre-flight activity, and the aircraft being taxied for take-off. Although the resolution was not high, there was evident movement that was consistent with the pilot making multiple fuel drains.                     

Emergency procedures – Engine power loss and forced landing

The pilot’s operating handbook (POH) for VH-FEY included emergency procedures for in-flight engine power loss and landing without engine power. There was no specific procedure or guidance in the POH for partial power loss or ditching. The text of the emergency procedures for engine power loss in flight is reproduced with revised formatting for readability in a report context:

ENGINE POWER LOSS IN FLIGHT
Fuel selector - switch to tank containing fuel
Electric fuel pump – ON
Mixture – RICH
Carburettor heat – ON
Engine gauges – check for indication of cause of power loss
Primer – check locked
If no fuel pressure indicated, check tank selector position to be sure it is on a tank containing fuel
If power is not restored prepare for power off landing.
Trim for 87 MPH IAS (76 KTS IAS)

When the pilot responded to the engine fluctuations, the first item was overlooked and the fuel selector remained on the right tank throughout the engine power loss sequence. The pilot explained that during initial flight training in a Cessna 172 they had memorised a ‘flow’ for practice forced landings that started at the centre of the aircraft (including fuel selector) then moved left. However, the pilot had not considered the implication of that method for the PA-28-181. So, in this case, the pilot had started in the middle but did not reach the left-mounted fuel selector because attention was diverted to preparing for the forced landing.

The text of the emergency procedures for a power off landing is reproduced below with revised formatting for readability in a report context:

POWER OFF LANDING
Locate suitable field
Establish spiral pattern 1000 ft. above field at downwind position for normal landing approach
When field can be easily reached slow to 76 MPH IAS (66 KTS IAS) for shortest landing
Touchdowns should normally be made at lowest possible airspeed with full flaps
When committed to landing:
Ignition – OFF
Master switch – OFF
Fuel selector – OFF
Mixture - idle cut-off
Seat belt and harness - tight

In the safety tips section of the POH, pilots were advised:

In an effort to avoid accidents, pilots should obtain and study the safety-related information made available in FAA publications such as regulations, advisory circulars, Aviation News, AIM, and safety aids.

The AIM reference in the POH safety tips was to the Aeronautical Information Manual published by the Federal Aviation Administration (FAA) in the United States. This addressed ditching procedures and is referenced in the next section.  

The aircraft manufacturer advised the ATSB that they were not aware of any significant risks if pilots applied the Power Off Landing procedure in the POH to a ditching. Given the wide range of forced landing scenarios in different environments, the aircraft manufacturer considered that it was not feasible to define an emergency procedure for each one. In addition, the general information about emergency procedures in the POH indicated that emergency procedures were not intended to replace pilot training or provide information that is the same for all aircraft.

Under the certification standards[4] applicable to light aircraft such as the Piper PA-28-181, there was a requirement for information concerning normal, abnormal, emergency procedures, and other pertinent information necessary for safe operation, to be provided. In the case of single‑engine aircraft, this included the procedures, speeds, and configuration for a glide following engine failure and subsequent forced landing. There was no specific requirement for a ditching procedure. 

The General Aviation Manufacturer’s Association (GAMA) issued specification No. 1 for pilot’s operating handbook released in February 1975 (the PA-28-181 POH was released in August 1975) and revised it in 1996. This document specified that procedures should be provided for forced landings under various conditions, including ‘ditching, for aircraft with extended overwater flight capability’.

Ditching guidance and training

FAA

In the emergency procedures chapter of the FAA AIM, there were various diagrams showing best heading in relation to primary swell, secondary swell, and wind. The manual specified a successful aircraft ditching was dependent on 3 primary factors in the following order of importance:

1. Sea conditions and wind
2. Type of aircraft
3. Skill and technique of the pilot   

In addition to detailed guidance about evaluation of sea conditions and selection of relative heading, the manual advised that:

Touchdown should be at the lowest speed and rate of descent which permit safe handling and optimum nose up attitude on impact. Once first impact has been made, there is often little the pilot can do to control a landplane.    
CASA

In the Australian context, CASA provided advice to operators of issues relevant to ditching an aeroplane through Advisory Circular 91-09 Ditching. This addressed preparation, selection of ditching area and direction of approach, and conduct of the actual ditching. The information provided was consistent with that in the FAA AIM.

If no type-specific guidance was available, the AC recommended that:

… the gear remain up, the flaps full, and speed at a minimum. In all cases, the desired configuration should be adopted at a safe height and the aeroplane trimmed to allow concentration on selection of the touchdown point.

For selection of touchdown point, the AC included the following points:

  • if there is no manufacturer guidance, select an attitude for minimum sink rate
  • wings level with the water surface on top of or on the back of a swell, not on the face of a swell
  • no yaw if possible; straighten nose if crosswind exists, but avoid lowering a wing.
Other aircraft POH

For comparison, the ATSB reviewed the POHs for 2 light single-engine aircraft that included ditching procedures: Cessna 172 and Gippsland Aeronautics GA8. The POHs specified power (if available) to achieve 300 ft/min rate of descent, and approach direction relative to wind and sea state. Touchdown was at descent attitude, without flare and/or at slowest practical speed.    

Pilot training

Pilot training in Australia was carried out in accordance with the Part 61 manual of standards (MOS). The competency standards for the ‘Manage abnormal situations – single-engine aeroplanes’ unit included elements and performance criteria for ‘Perform forced landing (simulated)’ in response to a simulated complete engine failure, and simulated partial engine failure.

For both scenarios, pilots were expected to identify the engine power loss condition, perform immediate or recall actions, and optimise aircraft performance. A landing area was to be selected, taking into account that a partially failed engine might fail completely, with an appropriate flight path. Pilots were to perform emergency procedures, as time permitted, and advise air traffic services or other agencies. If engine power was not restored, the pilot was to land the aircraft ensuring the safest outcome.  

Ditching was not referenced in the elements and performance criteria, but it was listed as one of the underpinning knowledge requirements.

The pilot advised that information about ditching had been gained from flight training and reading books.    

Other occurrences – Australia

Fuel starvation and forced landing

Fuel starvation and forced landing is a common occurrence type. The following occurrence was selected for the similarity of the engine power loss symptoms to the same type of aircraft.

ATSB AO-2017-094 Fuel starvation and forced landing involving Piper PA-28-181, VH-BDB, near Bankstown, New South Wales on 19 September 2017

The pilot believed that the aircraft fuel tanks were full and intended to conduct a 30–40 minute flight on the left tank. However, the aircraft had not been refuelled since the previous flight and contained about 25 L (35 minutes flying time) in the left tank and about 55 L (78 minutes flying time) in the right tank.

After about 30 minutes flight time, engine power started to fluctuate, and became progressively worse. The pilot conducted engine failure checks but did not change the fuel tank selection. Then the engine sustained a total loss of power and the pilot conducted a forced landing. There was no fuel found in the left tank.       

Ditching

The ATSB carried out a search of its database for occurrences that were categorised as a ditching. The ATSB identified 78 occurrences in the previous 50 years, including 11 fatal accidents that resulted in 21 fatalities.[5]

Of the fatal accidents, 2 involved twin-engine aircraft (including Piper Chieftain, VH-MZK near Whyalla on 31 May 2000) and 2 involved loss of control of single-engine aircraft. The remaining 7 fatal accidents involved single-engine aircraft in controlled ditchings.     

Apart from this occurrence involving VH-FEY, there were 5 other ditchings involving the PA-28 aircraft type, including 1 fatal ditching in a river near Bankstown in 1977. There were insufficient details to establish the method of ditching, however, the aircraft overturned on landing and sank immediately.

Extended time between overhauls (TBO)

ATSB AO-2020-060 Engine failure and collision with terrain involving S.E.D.E. Morane-Saulnier MS.893A, VH-UQI, on 6 November 2020.

During cruise, the engine began running rough then failed. The pilot conducted a forced landing in an open area but the aircraft impacted trees and caught fire. The pilot was seriously injured.

The ATSB found that the engine had sustained a catastrophic mechanical failure due to separation of a piston connecting rod. The engine had not been overhauled since 1997 and the aircraft had not been operated for an extended period, which was identified as a contributing factor.  

Safety message: This investigation is a timely reminder for aircraft owners and maintainers to be cognisant of the manufacturer’s service information which ensures that the serviceability of engine and airframe systems are maintained to the highest standards. This includes strict monitoring of on-condition items, and that replacement of some parts may be warranted to ensure continued and safe operation. Consideration should also be given to preservation of the engine and its systems, should an aircraft be infrequently utilised.

Other occurrences – Outside Australia

The ATSB identified the following occurrences involving ditching of a Piper PA-28-181 aircraft:

NTSB ERA16LA109 Fuel exhaustion involving Piper PA-28-181, N29099, near Port Jefferson, New York on 20 February 2016

During a night flight with a flight instructor, student pilot, and 2 passengers on board, the engine lost power. The flight instructor diverted to land along a shoreline but, unable to see it in the darkness, decided to ditch close to where he judged the shoreline to be from house lights. The instructor held the aircraft off the water as long as possible to avoid a touchdown with excessive speed and the risk of nosing over. All of the occupants evacuated the aircraft and there were no reports of any impact-related injuries. Three of the occupants were rescued but one of the passengers did not survive.

BEA 2020-0243 Piper PA-28-181 Archer II, N5352F, off the coast of the isle of Guadeloupe on 4 July 2020

During a ferry flight the engine lost power. Although the in-flight power loss procedures was carried out, engine power could not be restored. The pilot approached without wing flaps and trimmed the aircraft slightly nose up to ditch parallel to the swell. The pilot and passenger were uninjured and were rescued by helicopter.

Safety analysis

Fuel management

Effective fuel management is a key factor in safe completion of a flight. Pilots are required to plan, uplift, then manage fuel, to ensure that an aircraft is landed with not less than the required reserve fuel on board. 

For the return journey from Carnarvon to Jandakot, the pilot did not compile a flight or fuel plan. The pilot explained that the route was familiar and from experience estimated there would be about 50–60 L usable fuel (more than 1.5 hrs flying time) remaining at Jandakot. Also, the pilot expected that the fuel consumed on the return journey would be less than the total of 146 L consumed between Jandakot and Carnarvon. Based on full fuel of 180 L at Carnarvon, this equated to more than 34 L (about 1 hr flying time) remaining on arrival at Jandakot.      

Although the pilot departed Carnarvon and subsequently Geraldton with sufficient fuel on board for the intended flight, the pilot did not keep a fuel log during the flight. Without progressive recording in a fuel log (or equivalent), calculation of the fuel remaining in each tank would have been based on recollection of the timing of tank changes and retrospectively calculating fuel consumed and fuel remaining in each tank.  

The pilot’s practice was to change tanks using the fuel gauge indications as a prompt, which equated to 1-hour time intervals. These intervals were consistent with the POH and were generally effective at maintaining lateral balance and simplifying fuel management. However, the ATSB fuel calculations for the journey from Carnarvon show that some of the intervals were less than 1 hour and the requirement to land and take-off on the fullest tank could disrupt simple rule‑based fuel management.      

In summary, EFB and GPS technology have enhanced flight planning and navigation capability, but pilots are still required to carry out in-flight fuel quantity checks at regular intervals. These should include a cross check of all available data, including fuel quantity indications, and be recorded. For aircraft with separate tank selections, it is advisable to monitor the fuel consumed, and fuel remaining, for each tank. 

Engine power loss

About 15 minutes before arriving at Jandakot, engine power subsided to low power then returned to normal power. This type of fluctuation continued for about 2 minutes with insufficient power to maintain level flight. Shortly before the ditching the engine stopped completely.    

The ATSB considered all of the potential reasons for the engine power loss, which can be broadly categorised as:

  • engine and associated systems defect
  • carburettor ice
  • fuel contamination
  • fuel starvation.

Although the aircraft had sustained impact damage and been submerged, the engine and associated systems were not significantly affected. The ATSB confirmed mechanical continuity of the engine and found that key engine components such as carburettor, magnetos, engine-driven fuel pump and electric fuel pump were not defective.

According to the CASA carburettor icing probability chart, the conditions were conducive to carburettor ice at descent power. Given the engine was at cruise power, carburettor icing produces a continuous engine power loss until cleared, and the pilot applied carburettor heat early in the sequence, the symptoms are not consistent with carburettor icing.

The pilot identified an unusual amount of water in the fuel during the pre-flight inspection at Geraldton on the morning of the occurrence. There was no evidence that the fuel tanker had introduced the water during refuelling the previous afternoon and there was no rain recorded at Geraldton while the aircraft was parked overnight. The ATSB was unable to resolve this anomaly.  

Given the pilot had continued the fuel drains until water was no longer present in the samples and the pilot had operated for a further 6.7 hours, including another refuelling, it is unlikely that a significant amount of water was present in the tanks when the engine power loss occurred.

Submersion of the aircraft and infiltration of the fuel system by sea water prevented an accurate assessment of fuel quantity in each tank, although observations of the fluid drained from the tanks indicated there had been sufficient fuel on board for completion of the flight.      

At the time of the engine power loss, the right tank was selected and the ATSB estimated that the fuel remaining in the right tank was 6 L. Due to imprecise information this was indicative and does not preclude a lower amount. In addition, there were no engine or aircraft fuel system defects, and the symptoms were consistent with other occurrences where fuel starvation was verified. Although water contamination could not be ruled out, the ATSB found that the engine power loss was probably because of a lack of usable fuel in the selected (right) tank.

This condition, categorised as fuel starvation, could have been rectified by changing the fuel tank selector from the right tank to the left tank that contained sufficient fuel to continue the flight to Jandakot.    

Emergency procedures

If fuel starvation is recognised, the pilot can remedy the situation without recourse to emergency procedures. Otherwise, the pilot is required to apply the emergency procedures from memory and/or with reference to the written procedures.  

The pilot responded to the engine power anomalies by selecting the mixture to RICH and carburettor heat to ON. The electric fuel pump was already selected ON because of the pilot’s method of usage and that selection was not changed. Although continuous use of the electric fuel pump was contrary to the POH, this was not a factor in the occurrence.              

Those immediate actions, conducted from memory, were in accordance with the engine power loss in flight procedure in the POH. However, the pilot did not action the first item, which was:      

Fuel selector - switch to tank containing fuel

The pilot attributed this to the ‘flow’ or sequence that had been learned for a different aircraft type and not adapted to the configuration of the PA-28-181, combined with limited time to complete the sequence. For pilots who fly different aircraft types, use of a checklist mnemonic that can safely be applied across those types will reduce vulnerability to negative transfer of type-specific flows or sequences. Ready access to the written procedure is an option but is often not practicable in a single-pilot time-critical context.

Compared to a complete engine power loss, an intermittent or partial engine power loss is an ambiguous condition that does not conform to standard training scenarios and can disrupt pilot implementation of emergency procedures. Unless there is an obvious solution, pilots should prepare for an imminent complete engine power loss and follow the applicable procedures to optimise recovery of engine power.            

Engine power was not restored, and the pilot was required to conduct a forced landing. The pilot made a sound decision to carry out a ditching adjacent to the beach rather than landing on the populated beach with the high risk of injury.  

By applying the POH guidance for a power off landing and generic ditching guidance, the pilot conducted a controlled ditching with minimal damage and no injuries. This outcome was assisted by favourable sea conditions.

The ATSB noted that the POH did not contain any procedures for ditching and considered whether this was a factor that increased risk.

For light aircraft such as the Piper PA-28-181, there was no requirement for the aircraft manufacturer to provide a ditching procedure and they advised that they were not aware of any significant risks if the Power Off Landing procedure was applied to a ditching. By contrast, some aircraft manufacturers did include ditching procedures.

As referenced in the PA-28-181 POH, the Aeronautical Information Manual published by the Federal Aviation Administration (FAA) addressed ditching procedures in some detail. And in the Australian context, CASA provided guidance in Advisory Circular AC 91-09 Ditching.

Training for ditching has obvious limitations and it was not referenced in the elements and performance criteria of the ‘Perform forced landing (simulated)’ competency standard. As one of the underpinning knowledge requirements, it is expected that on completion of pre-licence training, pilots would have an awareness of aircraft-specific and/or generic ditching procedures.   

As indicated by the other occurrence information, the impact forces associated with a ditching are generally survivable, provided the pilot does not lose control of the aircraft before entering the water. As demonstrated in this occurrence, it is assumed that where there are no aircraft-specific ditching procedures, pilots conducting a ditching will apply power off landing procedures and generic training/guidance. Although aircraft-specific ditching procedures are an advantage there is no evidence that the absence of such procedures for the Piper PA-28 type significantly increases the risk of ditching.

In summary, if pilots might be required to ditch in case of an emergency, they should be familiar with the applicable procedures in the POH, as available, and/or generic guidance produced by national aviation authorities.

Extended TBO

The ATSB noted that since the last overhaul, the engine had been in service for 28 years, which was more than double the recommended time before overhaul of 12 years. This was mitigated to some extent by a bulk strip 13 years before the occurrence and various component changes.

Given there were no engine defects, and the required maintenance was carried out, the extended TBO was not identified as a factor in this occurrence.

Nevertheless, the ATSB recently found that in November 2020, a Lycoming 0-360 engine sustained a catastrophic mechanical failure due to separation of a piston connecting rod. The engine had not been overhauled since 1997 and the aircraft had not been operated for an extended period, which was identified as a contributing factor.

Although continued private operation is conditionally permitted for aeroplane engines that have exceeded the recommended calendar time before overhaul, operators should consider the length of the extension, modification status, and associated risk of failure.

Findings

ATSB investigation report findings focus on safety factors (that is, events and conditions that increase risk). Safety factors include ‘contributing factors’ and ‘other factors that increased risk’ (that is, factors that did not meet the definition of a contributing factor for this occurrence but were still considered important to include in the report for the purpose of increasing awareness and enhancing safety). In addition, ‘other findings’ may be included to provide important information about topics other than safety factors. 

These findings should not be read as apportioning blame or liability to any particular organisation or individual.

From the evidence available, the following findings are made with respect to the fuel starvation and ditching involving Piper PA-28-181, registered VH-FEY, on 20 April 2023.

Contributing factors

  • The pilot departed Carnarvon with sufficient fuel for the intended flight to Jandakot via Geraldton but did not carry out regular fuel quantity checks in accordance with regulatory guidance or keep a written log of the fuel consumed from each tank during the flight. 
  • During cruise at 1,900 ft, engine power subsided to low power then returned to normal power. This occurred a number of times, probably because of a lack of usable fuel in the selected (right) tank.
  • The pilot responded to the engine power anomalies by carrying out some of the emergency procedures but did not select the other (left) tank that contained usable fuel. Consequently, engine power was not restored, and the pilot carried out a forced landing/ditching into the ocean near a beach.

Other findings

  • Prior to the first departure from Geraldton on the day of the occurrence, the pilot drained a significant amount of water from both fuel tanks (that had been refuelled to full the night before) and from the fuel strainer. The aircraft was subsequently operated for over 6.5 hrs with a refuelling at Carnarvon without any symptoms of fuel contamination and it is unlikely that there was a significant amount of water remaining in the fuel.
  • The engine had been in service for 28 years, which was more than double the recommended time before overhaul (TBO) of 12 years. Given there were no engine defects, and the required maintenance was carried out, the extended TBO was not identified as a factor in the occurrence.

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • owner-pilot of the accident flight
  • maintenance organisation for VH-FEY
  • aircraft manufacturer
  • video footage of the accident flight and other photographs and videos taken on the day of the accident
  • recorded data transmitted from the EFB application on the aircraft.

References

Advisory Circular AC 91-09 v1.0 Ditching, Civil Aviation Safety Authority, November 2021. 

Advisory Circular AC 91-15 v1.1 Guidelines for aircraft fuel requirements, Civil Aviation Safety Authority, September 2021.

Pilot’s Operating Handbook Piper Cherokee Archer II PA-28-181 REPORT VB-760 Issued 15 August 1975, Revised 1 April 2019.

Submissions

Under section 26 of the Transport Safety Investigation Act 2003, the ATSB may provide a draft report, on a confidential basis, to any person whom the ATSB considers appropriate. That section allows a person receiving a draft report to make submissions to the ATSB about the draft report.

A draft of this report was provided to the following directly involved parties:

  • owner-pilot of the accident flight
  • maintenance organisation for VH-FEY
  • aircraft manufacturer
  • Civil Aviation Safety Authority

A submission was received from the:

  • owner-pilot of the accident flight

The submission was reviewed and, where considered appropriate, the text of the report was amended accordingly.

Purpose of safety investigations

The objective of a safety investigation is to enhance transport safety. This is done through:

  • identifying safety issues and facilitating safety action to address those issues
  • providing information about occurrences and their associated safety factors to facilitate learning within the transport industry.

It is not a function of the ATSB to apportion blame or provide a means for determining liability. At the same time, an investigation report must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner. The ATSB does not investigate for the purpose of taking administrative, regulatory or criminal action.

Terminology

An explanation of terminology used in ATSB investigation reports is available here. This includes terms such as occurrence, contributing factor, other factor that increased risk, and safety issue.

Publishing information 

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2023

image_5.png

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.

The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.

[1] Visual flight rules (VFR): a set of regulations that permit a pilot to operate an aircraft only in weather conditions generally clear enough to allow the pilot to see where the aircraft is going.

[2] The flight times referenced in this section are derived from the take-off and landing times recorded in the flight data. If flight times were derived from other data such as engine start to engine stop, the calculated fuel consumption rate may be different, but the results would be the same.       

[3] This is sometimes referred to as block fuel consumption rate and does not identify climb or other phases of flight for calculations at different rates. In the context of the operation type and imprecision of the available data, this was considered suitable for purposes of the investigation.

[4] The Piper PA-28 type was originally certified to CAR 3 in 1956. When the PA-28-181 was certified in 1975, the CAR 3 requirements were supplemented by certain provisions of Part 23 of the Federal Aviation Regulations. So, the current version of FAR 23 was referenced.    

[5] The ATSB notes that the database search was for indicative purposes only and data quality may vary over the search period.

Occurrence summary

Investigation number AO-2023-021
Occurrence date 20/04/2023
Location 15 km north-west of Jandakot Airport
State Western Australia
Report release date 28/11/2023
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-28-181
Registration VH-FEY
Serial number 28-7690006
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Carnarvon Aerodrome, Western Australia
Destination Jandakot Aerodrome, Western Australia
Damage Substantial

Fuel starvation and forced landing involving Piper PA-28, VH-BDB, 15 km west-south-west of Bankstown Airport, New South Wales, on 19 September 2017

Final report

Report release date: 13/02/2018

What happened

On 19 September 2017, at about 1504 Eastern Standard Time,[1] the pilot of a Piper PA‑28‑181 aircraft, registered VH-BDB (BDB), conducted a forced landing about 15 km west-south-west of Bankstown Airport, New South Wales. In addition to the pilot, there was one passenger on board. The pilot received minor injuries and the passenger was uninjured. The aircraft was substantially damaged.

On 15 September, the pilot made a booking to hire an aircraft from Bankstown Airport for a return flight to Wollongong with one passenger, for the time period 1200–1500. The booking was made with the flight school where the pilot had recently completed his private pilot licence and had flown the PA-28 aircraft type. The purpose of the planned flight was for the pilot to accrue command hours towards his commercial pilot licence.

On 19 September, after arriving at the flight school and finalising his flight plan, the pilot was advised that the booked aircraft was unserviceable and the booking was changed to 1230–1530 with an alternate aircraft. The alternate aircraft returned at about 1240–1250 from the previous booking and was then refuelled to full. The pilot conducted his pre-flight inspection and elected to start the flight with a few circuits at Bankstown Airport before departing to Wollongong with the passenger. While conducting the circuits, the aircraft became unserviceable and the pilot returned the aircraft to the flight school.

The school then offered the pilot BDB. The pilot agreed to take BDB, but decided to conduct a local training area flight due to the time delays associated with the aircraft changes. The pilot reported that he conducted a pre-flight inspection of BDB. He believed the aircraft had full fuel on board on departure and planned to fly for only 30–40 minutes. Therefore, he did not intend to change the fuel tank selector during the flight from the tank selected at take-off (refer to section titled Fuel management).

At about 1430, the pilot and passenger departed for a local training flight, with a planned return time of about 1500. At about 1500, as the aircraft was approaching the waypoint 2RN for return to Bankstown, the pilot noticed the engine was fluctuating a couple of hundred revolutions per minute. The pilot elected to track via Camden to avoid overflying built-up areas with what he believed to be an engine problem. After turning towards Camden, the pilot selected the electric fuel pump on, but the engine fluctuations became worse. The pilot then performed his engine failure immediate checks, which involved checking the fuel pump, mixture, oil temperatures and pressures, switches for the magnetos, and throttle for response.

After the pilot completed his immediate checks, there was a total loss of engine power, at which time the aircraft was at an altitude of about 700 ft above ground level. The pilot identified a field out to his left, made a MAYDAY[2] call to Bankstown air traffic control, and briefed his passenger to secure himself for the landing.

There was moderate turbulence, which resulted in fluctuating airspeed and intermittent stall[3] warning activations during the approach. Considering the conditions, low altitude and the location of the fuel tank selector, the pilot felt that attempting to change fuel tanks would have diverted his attention from flying the aircraft at a critical time. Therefore, the pilot focused his attention on not stalling the aircraft while executing the forced landing, and did not conduct any further checks.

After the aircraft touched down, the pilot concentrated on keeping it straight over the rough ground until it ran through a fence at the end of the field and stopped when the right wing struck a tree. The pilot activated the emergency locator transmitter and directed his passenger to stand about 30–40 m behind the aircraft. After the pilot exited the aircraft, he activated his personal locator beacon and made a phone call to emergency services as he could see fuel leaking from the right wing. Emergency services arrived within about 20 minutes and made the accident site safe.

Fuel management

Fuel system

The PA-28-181 aircraft has two fuel tanks, one in each wing, and a fuel gauge located in the cockpit for each tank. A three position fuel selector is located on the lower left side of the cockpit with the positions OFF, LEFT and RIGHT. The rate of fuel consumption in-flight is about 42 L/h and each tank held a total of 90 L. The last fuel system calibration was 19 February 2014.[4] The calibration check found the fuel tanks were empty when the fuel gauges indicated zero. When the fuel gauges indicated 5 USG,[5] the left tank held 17 L and the right tank held 16 L. When the fuel gauges indicated 10 USG, the left tank held 33 L and the right tank held 35 L.

Pilot’s instruction and practices

The pilot’s flying school reported that they teach pilots that fuel gauges are not always accurate. Therefore, if a fuel tank(s) was not full during the pre-flight inspection, a dip-stick located in the aircraft was used to check the tank(s) contents. For in-flight fuel management and aircraft balance, the pilot was taught to change the fuel selector between the LEFT and RIGHT tank at 30-minute intervals. Consequently, the pilot managed fuel in-flight based on flight time, rather than with reference to the fuel gauges.

In the event of a loss of engine power, the pilot was taught to complete the entire emergency checklist procedure provided there was sufficient height and/or time available. However, if he believed the loss of power had occurred in a time critical situation, then he should prioritise flying and safely landing the aircraft in lieu of conducting checks.

Operator’s report

The operator reported that, at the completion of the previous flight, BDB had about 25 L in the left tank and about 55 L in the right tank. The local fuel agent used by the operator also reported that BDB was not refuelled before the flight.

Aircraft inspection

A representative of the insurance company examined the aircraft about 3 hours after the forced landing. That examination found the fuel selector in the LEFT tank position (Figure 1) and no usable fuel in the left tank, which was not breached. The right tank, which was breached, was about one quarter full. The aircraft wreckage was recovered to facilities on 21 September and further inspections were conducted on 26 September. The inspections found no fuel in the engine fuel lines, and about 20 ml and 40 ml of fuel in the fuel filter bowl drain valve and carburettor respectively.

Figure 1: Aircraft fuel tank selector

Figure 1: Aircraft fuel tank selector

Source: Insurance assessor, modified by the ATSB

Quick reference handbook

The flight school had a published quick reference handbook for the PA-28 aircraft, which included an abnormal procedure for engine roughness and an emergency procedure for engine power loss in flight. The engine roughness procedure started with carburettor heat on, followed by adjusting the mixture, electric fuel pump on, switching fuel tanks, checking engine gauges and magnetos. The engine power loss in flight procedure started with switching fuel tanks, electric fuel pump on, mixture to full rich, carburettor heat on, check engine gauges and fuel primer.

Safety analysis

Believing the aircraft had full fuel on board, the pilot intended to conduct the 30-40 minute flight on the left fuel tank. It was more likely than not that the pilot believed the fuel quantity on board was full at the start of the flight due to his inspection of another aircraft earlier in the day. However, BDB was not refuelled prior to the flight and had about 35 minutes of fuel available in the left tank and about 78 minutes in the right tank. Despite having sufficient fuel on board for the planned flight, when returning to Bankstown, the engine lost power due to fuel starvation associated with use of the left fuel tank. This resulted in a forced landing.

While the pilot conducted some initial checks before the engine completely lost power, he omitted to change fuel tanks, which likely would have prevented the subsequent loss of engine power. Once the aircraft experienced a total loss of power, the pilot found himself in a time-critical situation in challenging flying conditions and therefore prioritised flying the aircraft in lieu of conducting further checks.

Findings

These findings should not be read as apportioning blame or liability to any particular organisation or individual.

  • The pilot had refuelled another aircraft to full earlier in the day, which he more likely than not misattributed to the fuel state of VH-BDB.
  • The loss of engine power was due to fuel starvation associated with the left fuel tank, which resulted in the pilot conducting a forced landing.

Safety message

Fuel starvation and exhaustion events continue to be reported to the ATSB. It is therefore important for pilots to continue to educate themselves on the risks and controls associated with fuel management.

Methods for cross-checking fuel on board before flight are published by the Civil Aviation Safety Authority in Civil Aviation Advisory Publication 234-1: Guidelines for aircraft fuel requirements.

Case studies for pilots to learn about fuel management related accidents have been published by the ATSB in Avoidable Accidents No. 5 – Starved and exhausted: Fuel management aviation accidents. 

About this report

Decisions regarding whether to conduct an investigation, and the scope of an investigation, are based on many factors, including the level of safety benefit likely to be obtained from an investigation. For this occurrence, a limited-scope, fact-gathering investigation was conducted in order to produce a short summary report, and allow for greater industry awareness of potential safety issues and possible safety actions.

Publishing information

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2018

image_5.png

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.

The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.

__________

  1. Eastern Standard Time (EST): Coordinated Universal Time (UTC) + 10 hours.
  2. MAYDAY: an internationally recognised radio call announcing a distress condition where an aircraft or its occupants are being threatened by serious and/or imminent danger and the flight crew require immediate assistance.
  3. Aerodynamic stall: occurs when airflow separates from the wing’s upper surface and becomes turbulent. A stall occurs at high angles of attack, typically 16˚ to 18˚, and results in reduced lift.
  4. The calibration check interval is 48 months in accordance with Civil Aviation Order 100.5. The fuel quantity gauges must be checked with the aircraft positioned to simulate the normal level flight attitude, which may be different to the aircraft attitude on the ground. A placard must be displayed in the fuel gauge scale errors exceed +/- 5% of the nominal fuel tank capacity.
  5. 1 United States Gallon (USG) = 3.8 L.

Occurrence summary

Investigation number AO-2017-094
Occurrence date 19/09/2017
Location 15 km west-south-west of Bankstown Airport
State New South Wales
Report release date 13/02/2018
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-28-181
Registration VH-BDB
Serial number 2843425
Aircraft operator Vectra Holdings
Sector Piston
Operation type Private
Departure point Bankstown Airport, New South Wales
Destination Bankstown Airport, New South Wales
Damage Substantial

Fuel management issue involving a PA31-350, VH-HJH, 19 km north of Goulburn Airport, New South Wales, on 12 October 2015

Final report

Report release date: 28/01/2016

What happened

On the morning of 12 October 2015, the pilot completed flight planning, then prepared a PA-31-350 (Piper Chieftain) aircraft, registered VH-HJH, for an aerial survey flight in the southern highlands area of New South Wales. As the flight was to be conducted at 10,000 ft above mean sea level, the pilot also discussed airspace requirements with both Sydney and Canberra Air Traffic Control (ATC) units. Due to potential conflicts with jet traffic at that level, ATC requested the pilot delay the departure from Bankstown, New South Wales, for a few minutes.

Prior to departure, the pilot delivered a safety briefing to the client’s three personnel who would be on board the flight. The pilot reported spending extra time briefing one of the group (Passenger 3) who had not flown in a light aircraft before.

After departure from Bankstown, at about 1300 Daylight Standard Time (EDT), ATC initially provided vectors to the pilot, then cleared the aircraft to the first of many planned waypoints in the area. The pilot reported that both towering cumulus (TC) and cumulus (CU) clouds were beginning to form in the area, and this produced some turbulence, but nothing substantial. However, the pilot remained concerned about Passenger 3, seated at the rear of the aircraft, who appeared to find the conditions difficult to tolerate.

The pilot’s workload remained high. Apart from the pre-planned waypoints, additional ‘landmarks’ were being relayed to the pilot from the client’s operator on the ground. The pilot had to check the landmarks on the chart, translate these requests into usable GPS coordinates, and then enter them into the GPS unit. The pilot then requested an amended clearance from ATC. The pilot visually manoeuvred the aircraft around cloud, and kept the aircraft as ‘smooth’ as possible, so that the survey operators on board could gain the necessary data from their equipment. The pilot also continued to monitor the wellbeing of the passengers, and in particular, passenger 3.

The aircraft was fitted with a main tank (inboard) and an auxiliary tank (outboard), for each of the two engines. As was the pilot’s normal routine, they kept a very detailed fuel log, and continually cross-checked the fuel flow, fuel used, and time remaining in each of the four fuel tanks. The power settings required for the survey were less than normal cruise performance settings.

As the plan was to return to Bankstown at the completion of the survey, the pilot kept a continual awareness of the slowly deteriorating weather there. The pilot reported that the potential alternates of Camden, Goulburn, Canberra and Bathurst remained as options. Thunderstorms were now developing in the Sydney Basin area, although Camden Airport automatic terminal information service (ATIS) still advised of clear conditions at that location. One of the passengers (Passenger 1), seated behind the pilot, discussed the thunderstorms and their impact on the flight with the pilot. As the pilot had kept a detailed fuel log and awareness of the surrounding weather, they were able to reassure the passenger that there was plenty of fuel available to complete the survey and, if necessary, divert to an alternate should a return Bankstown not be possible.

After a little over 2 hours, the clients had almost completed their work, and the pilot prepared to fly to the last waypoint before the return to Bankstown. The weather in the immediate area had now deteriorated even further, and the pilot reported having to divert off track to avoid thunderstorms, although all the alternates remained viable options.

As the pilot was about to make a scheduled fuel tank change from the auxiliary (outboard) tanks to the main tanks, the pilot again checked the fuel log. There was 16 minutes of fuel remaining in the left auxiliary tank (slightly more in the right auxiliary)

The pilot momentarily reflected on the weather versus fuel situation. As the weather between the aircraft’s current location and Bankstown had deteriorated even further, the pilot elected to alter their original plan, and keep the auxiliary tanks selected in order to use another few minutes of the remaining 16 minutes of fuel. This would leave the maximum fuel available in the main tanks. The main tanks in this aircraft are required to be selected during the descent, approach and landing, and, in this case, a possible diversion to an alternate.

During this period, as the pilot diverted around large banks of cloud to keep the aircraft in clear weather and discussed the necessity to fly to the last waypoint with passenger 1, the left auxiliary tank ran dry and the engine surged. This temporary asymmetric situation caused the aircraft to yaw. The pilot reacted immediately and changed the fuel selectors to the main tanks. The engine responded, and power was restored.

The pilot then continued with the remainder of the flight and landed without incident back at Bankstown Airport. At the time of landing, all reserves were intact with ample fuel remaining.

Pilot comments

In hindsight, the pilot reported that the decision to run the last few minutes from the auxiliary tanks may have not been necessary, and probably over-conservative. There had been no operational pressure for them to deviate from the scheduled fuel selection plan. The pilot reported that, due to the combination of distractions, they did not notice the low fuel warning light come on. This may have been further influenced by the amount of light in the cockpit at the time perhaps ‘dimming’ the effect of the red warning light situated on the instrument panel near the compass.

The pilot reported that this was a ‘non-standard’ high workload flight, coupled with deteriorating weather. Although the pilot had over 7,500 flying hours, with about 400 hours on Chieftain aircraft, they found themselves momentarily ‘caught out’. However, due to the aircraft’s altitude at the time, and the pilot’s quick reaction, there was no danger to the aircraft or the occupants.

The pilot also debriefed all passengers when on the ground.

Operator comments

The Chief Pilot advised that the pilot followed all company fuel planning procedures as outlined in the company operations manual. There are no procedures in the manual to advise pilots when they must change tanks to prevent a fuel starvation event. The aircraft landed with 279 litres of fuel, from a total of 690 litres of useable fuel. This equates to 104 minutes, less reserves, using the consumption rate of 160 litres per hour.

The Chief Pilot advised of the importance of regular enroute checks, particularly in a distracting environment.

Safety message

In this incident, the pilot followed all the key suggestions in the ATSB’s Avoidable Accident Series No 5 – Starved and exhausted: Fuel management aviation accidents. These being that they knew

  • exactly how much fuel was on board
  • how much / what rate fuel was being consumed
  • the aircraft fuel system and kept a detailed fuel log of the four tanks during flight.

However, a high workload, deteriorating weather, and untimely distractions led to a change of a planned procedure and an unplanned outcome of temporary fuel starvation of the left engine.

Another ATSB investigation involving fuel starvation resulted in a more serious outcome, with the aircraft substantially damaged. In that accident, the pilot was also distracted from their scheduled fuel management due to weather; however, the aircraft was at significantly lower altitude. Due to the delayed engine response at low level, the pilot had to conduct a forced landing through fog. The investigation (AO-2015-042) can be found on the ATSB website.

Aviation Short Investigations Bulletin Issue 46

About this report

Decisions regarding whether to conduct an investigation, and the scope of an investigation, are based on many factors, including the level of safety benefit likely to be obtained from an investigation. For this occurrence, a limited-scope, fact-gathering investigation was conducted in order to produce a short summary report, and allow for greater industry awareness of potential safety issues and possible safety actions.

Publishing information 

Released in accordance with section 25 of the Transport Safety Investigation Act 2003

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2016

image_5.png

Ownership of intellectual property rights in this publication

Unless otherwise noted, copyright (and any other intellectual property rights, if any) in this report publication is owned by the Commonwealth of Australia.

Creative Commons licence

With the exception of the Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

Creative Commons Attribution 3.0 Australia Licence is a standard form licence agreement that allows you to copy, distribute, transmit and adapt this publication provided that you attribute the work.

The ATSB’s preference is that you attribute this publication (and any material sourced from it) using the following wording: Source: Australian Transport Safety Bureau

Copyright in material obtained from other agencies, private individuals or organisations, belongs to those agencies, individuals or organisations. Where you wish to use their material, you will need to contact them directly.

Occurrence summary

Investigation number AO-2015-120
Occurrence date 12/10/2015
Location Goulburn Airport north 19 km
State New South Wales
Report release date 28/01/2016
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-31-350
Registration VH-HJH
Serial number 31-7752127
Sector Piston
Operation type Aerial Work
Departure point Bankstown, New South Wales
Destination Bankstown, New South Wales
Damage Nil

Fuel starvation involving a Piper PA-32-260, VH-BMU, Wandong, Victoria, on 22 October 1993

Summary

The aircraft departed West Sale with full fuel tanks. The pilot initially intended to track over the mountains to Albury but was unable to do so due to cloud cover. He then decided to track via the Kilmore gap, this course of action allowing the flight to proceed over lower terrain. While the aircraft was flying through the Kilmore Gap the engine suddenly stopped.

At the time, the aircraft was less than a thousand feet above the ground. The pilot changed fuel tanks and turned on the electric fuel pump but was unable to restart the engine. The aircraft hit trees initially and then made heavy contact with the ground. All occupants evacuated the wreckage and there was no post-crash fire.

A detailed inspection of the wreckage was carried out and no mechanical fault was found that could have contributed to the engine failure. However, from that inspection it was evident that the engine had been starved of fuel. It was determined that the right tip tank had been selected from when the aircraft took off until the engine failed. The time interval from take-off to the engine stopping was approximately 60 minutes which is consistent with the time to fuel exhaustion of a tip tank for this aircraft.

Significant Factors

The following factors were considered relevant to the development of the accident:

1. The pilot did not exercise sound fuel management procedures.

2. When the engine stopped, there was insufficient altitude/time available to restart the engine before the aircraft struck trees.

Occurrence summary

Investigation number 199303393
Occurrence date 22/10/1993
Location Wandong
State Victoria
Report release date 03/08/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-32-260
Registration VH-BMU
Sector Piston
Departure point West Sale, VIC
Destination Albury, NSW
Damage Destroyed

Fuel starvation involving a Cessna 310R, VH-LYD, Yarrawonga, Victoria, on 2 October 1993

Summary

Soon after take-off, on initial climb, the left engine lost power because the mechanical fuel pump failed. The pilot feathered the left propeller and landed safely back at Yarrawonga.

Significant Factor

The following factor was considered relevant to the development of the incident:

1. The engine driven mechanical fuel pump failed in flight.

Occurrence summary

Investigation number 199303246
Occurrence date 02/10/1993
Location Yarrawonga
State Victoria
Report release date 26/10/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Fuel starvation
Occurrence class Incident

Aircraft details

Manufacturer Cessna Aircraft Company
Model 310R
Registration VH-LYD
Sector Piston
Departure point Yarrawonga VIC
Destination Wangaratta VIC
Damage Nil

Fuel starvation involving a Beech Aircraft Corp A36, VH-KMT, Leigh Creek, South Australia, on 28 August 1993

Summary

The aircraft lost power shortly after take-off. A successful forced landing was made in a field adjacent to the strip. An inspection of the aircraft disclosed that a hose directing cooling air to the fuel injector manifold was kinked restricting the amount of cooling air available at the manifold. It is suspected that the manifold overheated and vapourised the fuel causing the loss of power experienced by the pilot.

Occurrence summary

Investigation number 199302706
Occurrence date 28/08/1993
Location Leigh Creek
State South Australia
Report release date 19/06/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction, Forced/precautionary landing, Fuel starvation
Occurrence class Incident

Aircraft details

Manufacturer Beech Aircraft Corp
Model A36
Registration VH-KMT
Sector Piston
Departure point Leigh Creek SA
Destination Mildura VIC
Damage Minor

Fuel starvation involving a Piper PA-31, VH-NNN, Oodnadatta, South Australia, on 9 July 1993

Summary

The aircraft departed Oodnadatta with 6 persons onboard. About 15 minutes into the flight, as it reached top of climb at 7000 feet, the fuel pressure to the right hand engine decreased and the engine backfired. The pilot turned the fuel boost pump on, but the engine failed to respond. The propeller was feathered. The aircraft was unable to maintain altitude and the pilot decided to return to Oodnadatta and advised Flight Service of his intentions.

The landing at Oodnadatta had to be made on runway 13 as the other runway was closed due to soft, wet surface. Runway 13 had a crosswind component of about 15 knots at the time and the pilot experienced some difficulty in aligning the aircraft with the runway on final approach. Suffering from some apprehension, and concentrating on the approach and landing, the pilot neglected to extend the landing gear.

Occurrence summary

Investigation number 199302017
Occurrence date 09/07/1993
Location Oodnadatta
State South Australia
Report release date 11/03/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction, Fuel starvation
Occurrence class Accident

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-31
Registration VH-NNN
Sector Piston
Operation type Private
Departure point Oodnadatta SA
Destination Noccundra SA
Damage Substantial

Fuel starvation involving a Socata TB-20, VH-JTB, 25 km north of Bindook, New South Wales, on 25 June 1993

Summary

The pilot reported that during cruise he noticed fuel flow fluctuations on both digital and analog fuel flow indicators. This was followed by power fluctuations which progressively worsened.

The pilot had decided to carry out a precautionary landing into a clear area he had located, when the engine failed completely. A power off landing was carried out into a small clearing in mountainous terrain approximately 4,000 ft AMSL.

Relevant Factors

  • Fuel starvation led to an engine power loss.
  • The cause of the fuel starvation was not determined.

Occurrence summary

Investigation number 199301884
Occurrence date 25/06/1993
Location 25 km north of Bindook
State New South Wales
Report release date 19/06/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction, Forced/precautionary landing, Fuel starvation
Occurrence class Accident

Aircraft details

Manufacturer SOCATA-Groupe Aerospatiale
Model TB-20
Registration VH-JTB
Sector Piston
Operation type Flying Training
Departure point Cowra NSW
Destination Bankstown NSW
Damage Substantial

Fuel starvation involving a Robinson R22 Beta, VH-HLK, 35 km north of Halls Creek, Western Australia, on 7 May 1993

Summary

The pilot was positioning the aircraft so that a left-handed shooter could take aim and shoot from the left seat. The aircraft was at about 40 feet above ground level and with minimal forward speed when the engine suddenly began running roughly and, after several back-fires, stopped. The pilot was unable to enter auto-rotation, and the aircraft landed heavily. The main rotor struck and severed the tail boom, and the aircraft skids were flattened during the impact.

Inspection of the wreckage revealed that the fuel selector was partially closed and that insufficient fuel, for normal operation, was able to reach the engine. An assessment of the sequence of events indicates that it is probable that, as the shooter was positioning the rifle for the shot, its butt made contact with the unprotected fuel selector lever and moved it to the partially closed position. The height at which the engine failure occurred prevented the pilot from cushioning the landing.

Safety Action

During the initial stages of the investigation, the Bureau issued Interim Recommendation IR930075 to the Civil Aviation Authority. It recommended:

That the Civil Aviation Authority advise R22 operators of the possibility for unintentional movement of the rear bulkhead mounted fuel selector and consider implementing a requirement for fuel selector protection to minimise inadvertent operation.

They subsequently advised that the Authority was in agreement with the recommendation and had issued an appropriate letter to all R22 operators on the matter. The Robinson Helicopter Company had also been advised of the accident and would be forwarded a copy of the letter.

Occurrence summary

Investigation number 199301252
Occurrence date 07/05/1993
Location 35 km north of Halls Creek
State Western Australia
Report release date 11/03/1994
Report status Final
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Engine failure or malfunction, Fuel starvation
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 Beta
Registration VH-HLK
Sector Helicopter
Operation type Aerial Work
Departure point Palm Well WA
Destination Palm Well WA
Damage Substantial