On 6 June 2023, the cabin crew of a QantasLink Boeing 717-200 aircraft, registered VH-NXM and operated by National Jet Systems, noticed a transient chlorine odour during the climb out of Sydney Airport, New South Wales. The cabin crew reported dizziness, mild discomfort described as pressure increasing in their head, and a metallic taste. The flight crew were advised, and the operator’s cabin air quality event procedure was completed.
About 76 minutes later, when the aircraft was on approach to Hobart Airport, Tasmania, the flight crew noticed a chlorine odour coming from the flight deck air-conditioning vents, lasting about 10 seconds. Shortly after, the captain noticed the onset of hypoxia-like symptoms and assessed themselves as unfit to continue as pilot flying.
The captain handed over pilot flying duties to the first officer and continued in the role of pilot monitoring for the remainder of the flight. The first officer, who was not experiencing any symptoms at that stage, continued the approach.
Shortly before landing, the first officer noticed that their reaction to an aircraft deviation was slowed and they started to experience cognitive difficulties. The landing was completed without further incident. After shutdown, both pilots reported a persistent headache, the captain also experienced ongoing symptoms of confusion and lethargy and attended a local hospital for medical tests.
What the ATSB found
The ATSB found that while the National Jet Systems’ cabin air quality events procedure captured the recording/reporting of odours, post-flight care of crew and maintenance actions, it did not consider the possible application of the smoke/fumes procedure or incapacitation procedure. As a result, there was an increased risk of flight crew being adversely affected by such an event during a critical stage of flight.
It was also identified that although National Jet Systems had procedures for recognition and management of pilot incapacitation, the associated training did not include the identification and response to subtle physical or cognitive incapacitation.
What has been done as a result
On 16 June 2023,National Jet Systems issued a Safety Action Notice (NJS-SAN-2023-018) reminding flight crews to consider supplemental oxygen use and the declaration of a PAN in response to a cabin air quality event.
On 2 March 2024, National Jet Systems advised the ATSB of the following safety actions taken as a result of this occurrence:
The flight crew recurrent simulator training syllabus had been updated to include in‑seat instruction specific to pilot incapacitation, followed by a practical exercise donning oxygen masks and conducting an approach, landing, and taxiing to the gate while using oxygen.
A review of smoke/fumes checklist and simulator training was undertaken.
Learnings from this occurrence have been incorporated into the newly‑introduced company A220 aircraft smoke/fumes, hypoxia, and incapacitation procedures.
A review of hypoxia training material to include specific reference to histotoxic hypoxia was undertaken, with draft content awaiting input from the Qantas chief medical officer.
Aircrew emergency procedures documentation and training pertaining to the recognition and management of crew incapacitation have been updated to include subtle and cognitive incapacitation.
Safety message
Airborne contaminants may result in the rapid onset of incapacitation, which although possibly subtle, can significantly affect the safety of flight. Physical or cognitive incapacitation can occur for many reasons and may be difficult for others, or even the sufferer of, to detect and respond to.
Flight crews should therefore be alert to the potential hazards posed by odours and fumes and not hesitate to use supplemental oxygen. The use of oxygen is a proven mitigating action in the case of environmental hazards and its rapid use ensures flight crews’ physical and mental capacity is maintained.
The occurrence
On 6 June 2023, a QantasLink Boeing 717-200 aircraft operated by National Jet Systems as QF1541 and registered VH-NXM, was conducting a scheduled passenger flight from Sydney, New South Wales to Hobart, Tasmania. On board were the captain as pilot flying (PF), first officer as pilot monitoring (PM),[1] 3 cabin crew and 54 passengers.
The aircraft departed Sydney at about 1943 local time and during the climb, the 2 cabin crew members at the front of the cabin detected a strong chlorine odour in the area of the forward galley, which was unnoticed by the flight crew. The cabin crew advised the flight crew of the odour, and once established in the cruise, the captain sought further information in accordance with company cabin air quality event procedure. The forward cabin crew reported dizziness, a feeling of pressure in the head, and a metallic taste, but that the odour had gone, and the symptoms were not increasing. The cabin crew member at the rear of the aircraft reported no odours or symptoms and stated that none of the passengers had complained of odours or appeared to be experiencing discomfort. The 2 affected cabin crew assessed themselves as fit to continue the flight. As a result, the captain elected to continue the flight to Hobart.
At about 2108, about 10 NM from Hobart Airport (Figure 1) and at an altitude of about 4,000 ft, the captain noticed a chlorine odour, which they assessed as coming from the flight deck air‑conditioning gasper vents. The first officer noticed the odour shortly after the captain but neither the captain nor first officer experienced any effects at this time. The captain and first officer reported that the odour was transient and disappeared after about 10 seconds.
About 30 seconds later, while the flight crew were configuring the aircraft for landing[2] on runway 30, the captain noticed quickly developing adverse effects on vision, mental capacity, and movement, and self-assessed as unable to safely fly the aircraft. The captain later described the symptoms as fogginess of thought, confusion, deteriorating situational awareness, weakness and tingling in the arms and legs, and narrowing of vision. The captain indicated their intention to transfer control of the aircraft to the first officer by stating ’your controls’. At that time the first officer noticed that the captain looked pale but did not appear incapacitated.
Figure 1: VH-NXM track showing approach to Hobart Airport and key events
Source: Google earth and Flight radar. Annotated by the ATSB
When about 8.5 NM from the runway at an altitude of about 3,250 ft, the first officer took over the role of PF. At the same time, the captain communicated that they were able to continue as PM with the assistance of the first officer. The first officer noted that the captain correctly actioned the commands to lower the flaps and landing gear to configure the aircraft for landing. The first officer was not experiencing negative symptoms at that stage and, as the odour was not detectable, assessed that emergency oxygen was not required.
Shortly after, the first officer noticed that the captain was struggling to read the checklist and was tripping over words, but managed to self-correct and read back air traffic control calls correctly. The first officer visually monitored the captain’s condition and ensured that no inadvertent contact was made with the flight controls.
At about 3 NM from the runway and an altitude of 1,000 ft, the first officer noted that the captain, as PM, had not made the required ‘stable’ call to confirm the aircraft was stabilised on the approach. The first officer prompted the captain with a call of ‘1,000 feet’, and the captain responded with ‘stable’. The first officer confirmed that the aircraft was stable and continued the approach. The first officer considered making a PAN[3] call, but assessed it was unnecessary due to the immediacy of landing.
At about 100 ft above the runway elevation, the first officer experienced difficulties keeping the aircraft lined up with the runway centreline. The first officer reported that the aircraft was drifting to the right of the centreline, and that their reactions to correct the drift were slower than normal. The first officer also reported feeling ‘hazy’, however these difficulties were not communicated to the captain at that time.
At about 2113, the aircraft landed at Hobart Airport and was taxied to a parking bay. The flight crew was assessed by a company medical doctor via teleconference, during which the doctor observed that the captain’s speech was noticeably affected, consistent with impairment. This resulted in the captain attending hospital for further testing.
The 2 forward cabin crew later reported the same smell on landing and again both felt similar mild symptoms. The first officer also reported a dull headache post‑flight, which lasted about 2 days.
Context
Personnel information
Flight crew information
The captain and first officer each held an air transport pilot (aeroplane) licence with a multi-engine command instrument rating and a class 1 aviation medical certificate.
At the time of the occurrence, the captain had accrued 10,670 flying hours with 5,780 of those on the Boeing 717-aircraft type. The first officer had accrued 6,984 flying hours, of which 1,614 were on the Boeing 717-aircraft type.
Post-flight medical tests
Several samples of the captain’s blood were analysed after the event to identify exposure to any toxins. The initial blood sample taken several hours after the aircraft landed found the carbon dioxide (CO2) level was slightly elevated and carbon monoxide (CO) was within the normal range. A second sample taken about an hour later showed that the levels of CO and CO2 had reduced.
Due to the time between the event and the first blood sample, and the low levels of CO and CO2 measured, the blood test results were considered to be inconclusive. The presence of an elevated CO2 level indicated the possibility of exposure to that gas, but the time, magnitude and source of the exposure could not be determined.
The first officer attended hospital the next morning for precautionary blood tests, the results showed no elevated levels of CO or CO2.
Aircraft information
Aircraft air-conditioning and pressurisation system
On Boeing 717 aircraft, pressurisation and temperature control is achieved by using bleed air from both engines. The hot, pressurised air is cooled by 2 independent pressurised air-conditioning kits (PACKs) and distributed to the flight deck and cabin. Cabin pressure is controlled by a single out‑flow valve, which is automatically modulated to open to decrease cabin air pressure and closed to increase cabin air pressure as required throughout the phases of a flight (Figure 2).
Figure 2: Simplified Boeing 717 normal air distribution
Source: Boeing. Modified and annotated by the ATSB
Typically, the left engine and left PACK are used to supply air to the flight deck and forward galley area, and the right engine and right PACK are used to supply the passenger cabin. Although, if required, either the left or right system can supply the air pressure and temperature control requirements of the entire aircraft.
The aircraft does not use recirculated cabin air, therefore air within the aircraft is completely replaced by the incoming air before being dumped overboard via the outflow valve. By controlling the flow of air through the outflow valve, the system regulates cabin air pressure throughout all phases of flight. In normal operation, pressurised air is sourced from the engine bleed air ducts, however for emergency operation, outside ram air can be selected to supply the PACKs which bypasses the engines and relies on aircraft forward movement to provide pressure.
Condensation is removed from the conditioned air by 2 independent water separators located at each PACK output manifold. Air entering the water separator is made to rotate by vanes in the inlet ducting. Centrifugal force causes the heavy water droplets to move to the outside of the separator and is collected by a coalescer bag and collector assembly, the water is then directed overboard, and the dry air continues through the system (Figure 3). The coalescer bags can be cleaned or replaced as required to prevent the build-up of contaminants and odours in the system.
Source: Boeing. Modified and annotated by the ATSB
During normal operation, the system automatically controls aircraft air temperature and pressure to maintain the optimum environment inside the aircraft for comfort and safety. If required, the flight crew can manually control system temperature, airflow, and PACK bleed air source, as well as manually control aircraft pressurisation. In both manual and automatic modes, the system is protected from overheat or freezing by a series of temperature control switches and sensors.
On the incident flight, the air-conditioning and pressurisation system was operating in automatic mode, with the left PACK supplying the flight deck and forward galley area, and the right PACK supplying the passenger cabin and rear galley.
Aircraft supplementary oxygen systems
Crew emergency oxygen system
Supplemental oxygen systems are provided to supply breathable oxygen in the case that the aircraft air is not capable of supporting respiration, either due to loss of air (oxygen) pressure or environmental contaminants. They can also be used as first aid to maintain blood oxygen levels in the case of medical emergency.
The flight deck oxygen system supplies oxygen to the flight crew in the case of an emergency. The system consists of a pressurised oxygen cylinder, 3 full face masks – one located at each of the captain, first officer, and observer seated positions – and a distribution system. A single, high‑pressure gaseous oxygen supply cylinder supplies oxygen to all 3 flight deck masks.
The masks are located in stowage containers at each flight crew location. Removal of the mask from the container aligns supply valves and supplies oxygen to the mask. An inflatable harness ensures that quick donning is possible by a range of users. Integrated goggles afford protection to the eyes from smoke or other airborne irritants, and a regulator allows manual selection of oxygen supply modes for various requirements (Figure 4).
Source: Boeing. Modified and annotated by the ATSB
In an emergency, the pilot removes the mask from the container by grasping and pulling on the protruding regulator. The harness is inflated by squeezing 2 buttons on either side of the regulator, allowing the user to don the mask in a downward sweeping motion. Releasing the buttons deflates the harness and pulls the mask onto the pilot’s face resulting in an airtight seal between the mask and face. Oxygen supply mode is selected by way of a rotary knob on the front of the regulator to suit the emergency, and communication is enabled by an integrated dynamic microphone. The donning of the mask is designed to be completed quickly with one hand and without the need for further adjustment.
Additional portable oxygen systems, including breathing equipment, are located throughout the cabin and flight compartment, and are intended for use in medical emergencies or unexpected cabin depressurisation.
Flight crew procedures for oxygen system
Specific National Jet Systems policy and procedures for the use of supplementary or emergency oxygen by crews were dependent on the emergency.
Following a loss of cabin pressure at altitude, emergency oxygen was expected to be used promptly without the need to reference written procedures. The automatic, immediate response was required to ensure that the risk of hypoxia[4] was not realised, which might affect the flight crew’s cognitive ability and safety of flight.
Smoke, fire, or fumes on the flight deck also required an automatic response with regards to oxygen use, however the definition of smoke and fumes requiring a response rested with the flight crew’s judgement of the hazard. The procedure detailed in the Quick Reference Handbook involved the use of supplemental oxygen by the flight crew, descent to 9,000 ft, and the removal of the smoke or fumes by ventilation. National Jet Systems advised that that procedure was considered inappropriate for cabin air quality (CAQ) events (see the section titled Cabin air quality events) and it had never been used by their crews in response to a CAQ event.
The National Jet Systems Emergency Procedures Manual stipulated the administration of oxygen by a cabin crew member responding to a pilot incapacitation event, inferring that total incapacitation had occurred and the pilot was unable to apply oxygen themselves.
Lastly, the National Jet Systems B717 Pilot Handbook – Checklist procedures stated:
Crew oxygen masks must be donned and communications established when their use is required. This includes but is not limited to:
Loss of cabin pressure.
Prior to the discharge of any fire extinguisher in or near the flightdeck.
Contamination, (smoke).
The concentration of fumes or odours, either present or anticipated on the flight deck.
National Jet Systems' annual recurrent training in the use of oxygen in flight included both theory and practical assessments in the flight simulator. The training was designed to validate flight crews’ response to a loss of cabin pressure and smoke/fumes on the flight deck.
Crew use of oxygen
In this event, oxygen was not used by the cabin or flight crew. The cabin crew did not consider themselves incapacitated, and their symptoms were mild and short-lasting. During the in-flight discussion between the flight and cabin crew regarding the departure CAQ event, the captain reminded the cabin crew to use oxygen if their symptoms persisted.
The captain reported at the time they first experienced symptoms, they did not assess themselves as incapacitated and therefore there was no requirement for a go-around or declaration of a PAN, and that a go-around would have exacerbated the situation as it would have significantly extended the airborne exposure time. The captain reported that this was a CAQ event and although oxygen was available, they did not correlate flight crew use of supplemental oxygen with a CAQ event response.
At the time the captain handed over control of the aircraft, the first officer’s focus was on configuring the aircraft for landing, and the welfare of the captain. The first officer reported that they did not think oxygen was required considering the smell had ceased and symptoms were not being experienced. Further, the first officer did not consider that the captain was incapacitated as they were performing the pilot monitoring role, albeit with some prompting.
The crew reported that they had infrequently practised donning the mask during practical training. The captain further reported that in their last simulation, the mask tended to fog up, and that communicating was more difficult with it on.
The Qantas chief medical officer reported that the use of supplemental oxygen would have prevented further ingestion of any airborne contaminants present. Furthermore, had the contaminant been CO or CO2, use of oxygen was the only method able to provide rapid improvement in the crew’s condition.
Cabin air quality events
Sources of cabin air quality events
Modern aircraft air-conditioning and pressurisation systems are complex and involve significant variables in pressures, temperatures, and operating environments. Several major studies have been completed by authorities worldwide to assess the quality of cabin air and determine the source of contaminants. To date, the consensus is that aircraft cabin air quality is typical of indoor environments and considered safe. However, concerns have been raised about the possibility of contaminants which may contribute to long and/or short-term health effects. Cabin air contaminants are more likely to be detected during take-off or landing (EASA 2017).
In the 12 months preceding the incident flight, the operator recorded 28 CAQ events on Boeing 717 aircraft, 19 of which resulted in mild symptoms such as nausea, headaches, or irritated eyes or throat in the crew. Eleven of the 28 events involved reported odours during take‑off/climb and again during descent/landing. None of the recorded events affected safety of flight and were therefore categorised as innocuous by the operator.
Generally, and not specific to the Boeing 717 aircraft, known possible causes of CAQ issues include:
engine oil introduced into the airpath by leaking internal engine or auxiliary power unit compressor seals
hydraulic oil or exhaust gases introduced into the airpath from external aircraft sources
dirty or defective water separator bags or components
build-up of contaminants within the air-conditioning packs or ducting
the use of aircraft cleaning or de-icing chemicals, inadvertently introduced into the airpath
introduction of bio-effluents into the airpath in flight
external environment airborne fumes, gases or pollution
fumes from internal cabin or cargo compartment sources.
Routine inspections and maintenance of known sources of odours and fumes were conducted to reduce CAQ events. Additionally, these sources often guided the immediate action of maintenance crews in response to a CAQ event. However, the source of reported odours or fumes were often not determined.
Recent VH-NXM cabin air quality reports and maintenance
In the 6 days prior to the incident flight on 6 June 2023, maintenance records for VH-NXM documented other reports of cabin air quality issues (Table 1).
Forward and aft cabin crew report rotten garbage smell following application of take-off thrust, lasting 5 minutes.
Both coalescer bags replaced and cleanout of the high‑pressure ducting with auxiliary power unit bleed air carried out.
1 Flight
No CAQ Issues
2 June 2023
4 Flights
No CAQ Issues
4 June 2023
1 Flight
Chlorine smell was reported at the forward and aft galleys and the flight deck during take-off for between 3-5 minutes. Cabin crew reported mild symptoms (dizziness and shaking). The flight was diverted to Sydney.
System inspected for signs of oil leaks. Ground functional check carried out; no odours detected on ground.
1 Flight
No CAQ Issues
5 June 2023
2 Flights
No CAQ Issues
6 June 2023
1 Flight
No CAQ Issues
Incident Flight
In response to the incident flight, the following maintenance actions were completed:
inspection of air conditioning/pressurisation system ducting and associated hardware for evidence of oil or other contaminants, or unserviceability
inspection of both PACKs and water separator drain lines
inspection and replacement of both PACK coalescer bags
cleanout/burnout of pneumatic high-pressure ducting
standard troubleshooting post cabin air quality event to locate sources of oil or hydraulic fluid that may have inadvertently entered the airpath
ground testing and flight testing with particulate and air quality analysers onboard
inspection of oil replenishment records to identify notable consumption or loss
inspection of both aft toilet chemical injection systems.
The reported CAQ event could not be replicated on the ground or air by maintenance crews, therefore a definitive source of the chlorine odour was not determined.
National Jet Systems Cabin Air Quality events procedure
The National Jet Systems in-flight procedure in response to CAQ events was divided into 2 sections.
Section 1 was designed to record details of the event such as odour strength and description, time and duration of the event, and aircraft configuration at the time of the event. This was primarily intended to assist ground maintenance crews in the identification and rectification of faults during post-flight maintenance.
Section 2 was used in the case of reported crew or passenger physical symptoms resulting from the fumes event. This was to ensure post-flight medical care of crew and passengers if required, and to enable consistent recording of events and their impact on crew or passengers.
On the incident flight, both sections of the procedure were completed, and the operator was notified of the occurrence prior to arrival into Hobart.
Flight crew incapacitation
Symptoms and causes of incapacitation
Pilot incapacitation may be obvious or subtle, with symptoms ranging from total loss of function or consciousness to minor impacts on perception or executive function. Management of obvious incapacitation involves crew reacting to overt observable action or inaction. However, subtle incapacitation requires recognition of sometimes fleeting outward symptoms and reacting in a way that does not further degrade safety of flight (ICAO 2012).
The majority of reported pilot incapacitation events are caused by gastrointestinal upset, most commonly attributed to food poisoning (ATSB 2007). This type of incapacitation is characterised by clear outward symptoms and well-established responses by the crew.
Another source of pilot incapacitation is hypoxia. Hypoxia is caused by the interference in delivery of oxygen to the body. This can be the result of low oxygen pressure due to altitude, displacement of oxygen in the air by airborne contaminants, interference of oxygen in the blood due to toxins such as carbon monoxide, or restriction of blood flow due to rapid decompression, cold environment, or medical events (FAA 1991). The symptoms of hypoxia range, depending on the magnitude and speed of the source, from mild discomfort and subtle incapacitation to unconsciousness. In all cases the immediate application of supplemental oxygen will reverse the symptoms of hypoxia.
The symptoms of subtle incapacitation include degraded decision making, perception, awareness of surroundings, vision, motor control and coordination, concentration, behaviour, or memory. Symptoms can be fleeting or long lasting and difficult for others to detect; moreover, it is possible for the person experiencing the symptoms to be unaware of their presence.
This difficulty in detection is what constitutes the primary risk of this type of incapacitation, and as one of the first symptoms experienced affects cognition, it can be difficult or impossible for the person experiencing the incapacitation to recognise or respond to appropriately. Minor levels of incapacitation may be rationalised by the person suffering symptoms or by those observing; for example, difficulty maintaining altitude might be attributed to a lack of recent exposure to aircraft manual control (ICAO 2012).
Another consideration when discussing pilot incapacitation is the effect of stress on flight crews during a non-normal event, which is amplified if the event takes place during a critical stage of flight (NASA 2015):
Situational stress can adversely affect the cognition and skilled performance of pilots, as well as experts in other domains. Emergencies and other threatening situations require pilots to execute infrequently practiced procedures correctly and to use their skills and judgment to select an appropriate course of action, often under high workload, time pressure, and ambiguous indications, all of which can be stressful.
The Qantas chief medical officer asserted that the effect of stress can cause a physiological response (including hyperventilation) which is difficult to differentiate from symptoms caused by any external physical sources. In fact, the stress response itself can increase anxiety resulting in a feedback loop and severe distress for the sufferer, manifesting as physical incapacitation.
Flight crew procedures and training for crew incapacitation events
The National Jet Systems pilot incapacitation procedure involved the unaffected pilot using a cabin crew member to assist the flight crew by securing the incapacitated pilot in their seat and away from flight controls, and the application of first aid if required. The primary purpose of the procedure was to prevent inadvertent interference with the safe flight of the aircraft and to provide medical aid if necessary. The use of oxygen was stipulated in the context of first aid, if required.
Flight and cabin crews underwent recurrent practical training and assessment in the conduct of incapacitation procedures. Specific pilot incapacitation training at National Jet Systems was conducted at:
Boeing 717 Command Upgrade Training (one segment dedicated to pilot incapacitation during a simulator session)
annual practical emergency procedures training (one practical segment dedicated to pilot incapacitation, conducted with flight crew and cabin crew as a combined group, in an aircraft or synthetic trainer)
initial and 4-yearly Boeing 717 Pilot Low Visibility Procedures Take-Off Training (one exercise dedicated to a pilot incapacitation event during take-off).
The National Jet Systems Aircraft General Operating Policy & Procedure, section 5.4.8 Flight crew/cabin crew incapacitation, stated:
When a Flight Crew member becomes incapacitated in flight, as a minimum, a PAN should be declared and the aircraft should be landed at the nearest suitable airport … Any apparent incapacitation of flight crew or cabin crew should not go unnoticed.
Flight crew members should be alert to the possibility of sudden or subtle incapacitation of an operating Flight Crew member, particularly during take-off and landing manoeuvres. To protect against subtle incapacitation, Flight Crew members are required to acknowledge supporting calls. Acknowledgement is normally the word “Checked”.
National Jet Systems’ training syllabus also included relevant recurrent human factors and threat and error management training.
Two communication rule
Modern passenger aircraft use 2-pilot crews to share workload and provide redundancy in an emergency. Duties are clearly defined and split between pilot flying (PF) and pilot monitoring (PM). While the PF and PM duties can be performed by the captain or first officer, the captain retains authority on the aircraft. However, safe operation relies on the first officer monitoring the captain’s actions and challenging or intervening if necessary.
Roles are clearly defined between the PF and PM, in part to ensure that a breakdown in the system can be quickly recognised. While the PM generally handles radio calls, checklists, and monitors the status of the aircraft and PF, the PF ensures that the PM completes the appropriate checklist, checklist items and radio calls, and the PF responds with an appropriate call, usually ‘checked’. This is known as the ‘two communication rule’ and is widely used because an error or absence of a call will quickly indicate a system problem, or issue with a flight crew member (ICAO 2012).
The two communication rule is reliant on a culture on the flight deck typified by a low flight deck authority gradient[5] and a high level of situation awareness. Understanding of what should be happening at any given phase of flight is critical to the effectiveness of the rule, the adherence to standard operating procedures is therefore a key component to enable crews to quickly identify subtle incapacitation in others (ICAO 2012).
The National Jet Systems B717 Pilot Handbook, Section 11.1.1 Standard Phraseology, stated:
… The absence of a standard callout at the appropriate time may indicate a malfunction of an aircraft system or indication, or indicate the possibility of incapacitation of the other pilot.
Similar occurrences
Between 2013 and 2023, the ATSB recorded 205 flight crew incapacitation occurrences, 7 were related to cabin air quality, of which 2 took place on commercial passenger jet aircraft.
The following are summaries of notable CAQ incident investigations.
United Kingdom Air Accident Investigations Branch Airbus A320-232 G‑EUYB 09-20
On 23 September 2019, the flight crew of an Airbus A320-232 detected an odour described as a sweaty sock smell while climbing through about 10,000 ft after departing Zurich Airport. The co‑pilot stated that they had experienced similar odours on the aircraft type before but described this instance as much stronger than previously experienced. The odour lasted about 30 seconds. The crew discussed options and elected to continue the flight; the flight crew's previous experience suggested that if the smell was going to reoccur it was most likely to occur when thrust was reduced for descent so, during the cruise, they discussed their actions if the smell returned and reviewed the SMOKE/FUMES/AVNCS SMOKE checklist.
The crew detected strong acrid fumes on the flight deck while on approach to London Heathrow Airport, United Kingdom. They enacted their plan and donned oxygen masks, declared a PAN, and completed the landing.
After landing, the copilot removed their mask to check for the continued presence of the odour. It was still present, so the flight crew shut down both engines, opened the flight deck windows, and started the auxiliary power unit. Shortly after, the copilot became nauseous and vomited out the flight deck window. A cabin crew member came onto the flight deck to assist and noted a chemical smell on the flight deck. They also confirmed that there were no smells or reports of illness in the cabin.
Both flight crew attended hospital, but results were not published.
The Air Accident Investigations Branch conducted a test of the aircraft air conditioner systems on the ground with engines, auxiliary power unit, and ground power. No odours or defects were identified. A comprehensive inspection and associated aircraft systems was carried out, and no sources of the fumes was identified.
The report concluded:
While it has not been possible to positively identify the compound that was responsible for the fumes and odours experienced in G-EUYB, or any of the other recent events, a number of common factors have been identified. The majority of events occurred after the aircraft had been parked or operated in precipitation. The fumes become apparent during the later stages of the descent, sometimes preceded by a minor event during the climb phase. The generation of fumes appears to be transient; they dissipate rapidly and leave no detectable trace. No link between changes to engine power or changes in other system settings and the generation of fumes was identified.
In some cases, the presence of fumes has resulted in physiological reactions which have interfered with a flight crew member’s ability to carry out their normal duties. However, by following the smoke and fume checklist, and donning oxygen masks the flight crew were able to ensure the continued safety of the aircraft.
French Bureau d’Enquêtes et d’Analyses (BEA) 2017-0658 Airbus A320 EC‑HQJ
On 17 November 2017, the pilots of an Airbus A320 complained of an unpleasant smell and irritations while taxiing behind a Cessna Citation prior to departure from Geneva-Cointrin Airport, Sweden. During the initial climb the crew experienced nausea and dizziness, which became progressively worse as the flight continued.
During the cruise, the captain donned their supplemental oxygen mask and reported an improvement of symptoms. A short time later, the first officer donned their supplemental oxygen mask due to worsening symptoms, a PAN was declared, and the aircraft diverted to Marseilles‑Provence Airport, France. The flight crew remained on oxygen for the remainder of the flight and landed without further incident.
Blood samples were taken, and tests showed no signs of carbon monoxide poisoning, but no other toxicological tests were carried out on the blood samples. Nausea and dizziness were reported for several days following. Hair samples were taken from the flight crew and analysed, but the analysis did not find substances in quantities corresponding to a one-off significant exposure in relation with the event.
Inspection of both aircraft involved identified no relevant defects or causes of contaminated air.
The reported concluded:
Despite the wide range of actions undertaken, the investigation was not able to factually identify what caused the flight crew’s symptoms and physical discomfort. The hypothesis of them having inhaled an excessive quantity of carbon monoxide, contained in exhaust gases emanating from the Cessna Citation which had been in front of the A320, is consistent with the information collected and can explain the symptoms observed (dizziness and nausea). Nitrogen oxide and sulphur oxide compounds present in exhaust gases may also have contributed to the acrid and irritating odours smelt while taxiing. However, it cannot be excluded that the crew were intoxicated by another substance which either quickly disappeared or which was not specifically searched for in the samples taken from the aeroplane as to date, not identified, even in the most recent studies.
Toxic substances were searched for in the hair samples using the most effective, innovative techniques to date. The BEA believes that the use of these techniques on matrices such as saliva, blood or urine, sampled as quickly as possible after the symptoms, and in particular as soon as possible after landing, would increase the chances of detecting a wider range of potentially toxic substances.
Swedish Accident Investigation Board RL 2001:41e BAE 146-200 SE-DRE
On 12 November 1999, the crew of a British Aerospace BAe 146-200 were scheduled to carry out 3 return flights between Stockholm and Malmö, Sweden.
During the first flight, a cabin crew member experienced a faint feeling. On the second flight cabin crew members experienced an odd pressure in the head, nasal itching, ear pain, and the feeling of ‘moon walking’. The issue was discussed with the pilots on both occasions, and on both occasions the pilots reported feeling no symptoms.
On the third flight, the cabin crew again reported discomfort similar to the preceding flights, but more pronounced. On descent to Malmö Airport, the copilot suddenly became nauseous and donned their oxygen mask. After about 10 seconds, the captain also became nauseous and donned their oxygen mask. After a few seconds on oxygen, the copilot started to feel better, however the captain’s condition continued to deteriorate. The captain reported feeling dizzy, and having difficulty with physiological motor response, simultaneity, and in focusing. The captain started to feel better after breathing oxygen for several minutes, and the landing was completed without further incident.
No medical examinations were performed after the incident.
A comprehensive technical investigation was conducted to attempt to determine a source of foul air. This included cabin air quality tests during test flights, bleed air analysis during a test run of an engine with an identified oil leak in an engine test cell, and dismantling and inspection of the engine. Despite these efforts, a definitive explanation for the incident was not identified.
The report concluded:
Air samples taken during engine testing and aircraft test flights provided no indication of what/which chemical substances caused the symptoms.
No technical fault that can explain the incident has been found.
The location of the customer bleed port for the air-conditioning system is not optimal on the engine type.
Knowledge is lacking concerning modern lubrication oils’ characteristics at very high pressure and temperatures and their effect on human health.
Instructions are lacking concerning how crews shall act during flight when suspicion arises about contaminated cabin air.
Safety analysis
Introduction
During climb, the 2 cabin crew members in the forward galley smelt a chlorine odour and experienced associated mild symptoms, which abated after a short time, before returning again on landing. The air-conditioning system was in the normal configuration so that bleed air from the left engine and pressurised air-conditioning kit was distributed to the flight deck and forward galley, while the right side supplied the passenger cabin. Although left-side air was also being distributed to the flight deck, the flight crew did not detect odour during the climb. The crew treated the odour as a cabin air quality (CAQ) event and conducted the associated reporting actions.
Later in the flight, on approach to Hobart Airport, the flight crew noticed a chlorine odour and the captain experienced the rapid onset of symptoms of incapacitation, including cognitive impairment. The captain handed over pilot flying duties to the first officer and assumed the responsibilities of pilot monitoring.
Just before landing, the first officer reported feeling some symptoms of incapacitation but due to the proximity to landing and perceived difficulties of donning the oxygen mask, the first officer assessed that supplemental oxygen was likely to increase the risk to safety of flight. A go-around was considered, but the first officer assessed that continuing the landing was the safest overall course of action. Both flight crew members were partially incapacitated during the landing and subsequent taxi to the parking bay.
The odour and symptoms were consistent with that experienced earlier by the cabin crew, albeit with the flight crew experiencing more serious effects. The reason for the captain experiencing more debilitating effects slightly earlier than the first officer and for the cabin crew’s symptoms being subjectively milder, could not be determined. Whether a stress response to a non-normal situation in a high workload phase of flight exacerbated or contributed to the symptoms experienced by the flight crew on the incident flight was also not determined. The same aircraft had a reported CAQ event 2 days prior to the incident, in which cabin and flight crew smelt chlorine and only the cabin crew reported any symptoms, which were mild. Following the 6 June 2023 occurrence, maintenance engineers conducted an inspection of the aircraft to identify a source of the odours, none were found, and the event was not able to be reproduced on the ground or during a subsequent test flight.
Cabin air quality events procedure
Based on occurrences recorded by the ATSB and the aircraft operator, most CAQ events are short-lived and benign, with exposed crew experiencing no or mild symptoms. However, in rare cases the effects can be more serious and affect the safety of flight. Crew incapacitation may be partial or complete, and symptoms can range from the obvious, such as vomiting or loss of consciousness, to the subtle, such as mild cognitive impairment, or difficulty executing a task. In accordance with the operator’s procedures, the appropriate response depended on the extent of the effects experienced by the crew.
The history of reported CAQ events not impacting safety of flight likely influenced the intent of the operator’s CAQ event procedure, which detailed steps to report an event to assist in post-flight maintenance activities, and to assess an affected individual’s fitness to continue or return to duty. In response to the transient odour and symptoms reported during climb by the cabin crew, the flight crew completed the CAQ event procedure. Although the CAQ event procedure did not require consideration of supplemental oxygen, the captain reminded the affected cabin crew members to use supplemental oxygen if required. The CAQ event procedure did not require crews to consider actions in the event flight crews were affected by airborne contaminants.
The operator’s emergency procedure for smoke/fumes and the pilot handbook included that crew oxygen masks must be donned when concentration of fumes or odours were detected or anticipated on the flight deck. However, when the flight crew experienced the chlorine odour and more serious symptoms, they assessed it was a transient CAQ event rather than a fumes event and therefore were not required to use supplemental oxygen. Additionally, the captain’s first symptoms were likely cognitive impairment, which may have affected their judgement regarding the need for supplemental oxygen. If cognitive incapacitation is due to hypoxia or environmental contaminants, the window of opportunity to recognise and react to it can be very small before more significant cognitive effects impair decision making.
According to the operator’s medical officer, use of supplemental oxygen can have operational challenges but will not cause harm. Its use prevents further inhalation of contaminated air, preventing symptoms from worsening. In particular, it reverses the effects of hypoxia, including exposure to carbon monoxide and dioxide, and is also useful in the case of many medical emergencies.
National Jet Systems’ record of CAQ events showed 28 reported events in the 12 months prior to the incident flight, often during descent/landing preceded by events during take-off and climb. Eleven of the 28 events reported symptoms such as nausea/vomiting, headache, dizziness, or discomfort of the eyes and throat, but none of these effects impacted the safety of flight. The potential for a recurrence in the same flight was not considered in the CAQ event procedure. Additionally, the procedure did not include consideration of a CAQ issue leading to a fumes or incapacitation event.
As a result, the crew were unprepared for the subsequent fumes and incapacitation event, which occurred at a critical phase of flight, and did not use oxygen to significantly reduce the risk of both flight crew becoming partially incapacitated. The effectiveness of such preparation was demonstrated in a 2019 incident investigated by the United Kingdom Air Accident Investigations Branch. In that incident, following a mild transient CAQ event during the climb, the flight crew reviewed their smoke/fumes procedure, and discussed and planned to use oxygen if an event recurred. As a result, the flight crew quickly donned oxygen and declared a PAN when they detected fumes on approach.
Pilot incapacitation training
Multiple studies have identified gastrointestinal illness caused by food poisoning as the most common cause of pilot incapacitation. This finding has shaped pilot incapacitation training and procedures to ensure that the most prominent threat is adequately covered. The most salient features of food poisoning are obvious symptoms, the ability for the sufferer to communicate their distress, and ability to retain cognitive capacity. Training in recognition and response of pilot incapacitation has also been focused on the immediately hazardous effects of sudden and total incapacitation. The operator’s training in the use of supplemental oxygen for incapacitation focused on response to these events and did not encompass precautionary use of supplemental oxygen, or oxygen use during critical stages of flight.
The captain self-assessed as being unable to continue as pilot flying and handed over the duty to the first officer in accordance with the operator’s procedures, but did not communicate the severity of the difficulties experienced to the first officer. Although the captain knew and understood the symptoms and response to hypoxia, at the time, likely due to cognitive impairment, the captain did not recognise the hypoxia-like symptoms or identify supplemental oxygen as an appropriate response.
The National Jet Systems pilot incapacitation training focused on responding to overt or obvious incapacitation rather than the response to subtle incapacitation. The operator’s policy manual specified the flight crew’s absence of a standard call, or an acknowledgement of a standard call, as an indicator of pilot subtle incapacitation. In this case the first officer recognised that the captain had missed the stable approach call required at 1,000 ft altitude, and prompted the captain who then made the correct call.
Without the benefit of formalised training in the response to partial or cognitive incapacitation, and due to the absence of symptoms experienced by the first officer at that time, the first officer continued the landing without the use of supplemental oxygen. Additionally, the first officer assessed that the operator’s pilot incapacitation procedure and requirement to broadcast a PAN call were inappropriate in this event, as the captain was not completely incapacitated, and the aircraft was close to landing. While the proximity to landing limited the opportunity for the first officer to take any further action, the absence of training in management of subtle physical or cognitive incapacitation increased the risk of both flight crew members becoming impaired and unable to safely continue the flight.
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 flight crew incapacitation involving Boeing 717-200, VH-NXM on approach to Hobart Airport, Tasmania on 6 June 2023.
Contributing factors
The flight crew noticed a chlorine odour during the approach to Hobart Airport. Shortly after, the captain experienced the rapid onset of symptoms of incapacitation, resulting in them handing over pilot flying duties to the first officer.
Just before landing, the first officer experienced symptoms of incapacitation, specifically slowed reaction time. Due to the impending landing, and perceived difficulties of donning the mask, supplemental oxygen was considered but not used. A go‑around was also considered but rejected following an assessment that continuing the landing was the safest course of action.
National Jet Systems’ cabin air quality events procedure focused on the recording/reporting of odours, post-flight care of crew and maintenance actions. However, it did not consider the possible application of the smoke/fumes procedure, or incapacitation procedure. As a result, there was an increased risk of flight crew being adversely affected by such an event during a critical stage of flight.(Safety issue)
Other factors that increased risk
Although National Jet Systems had procedures for recognition and management of pilot incapacitation, the associated training did not include the identification and response to subtle physical or cognitive incapacitation. (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 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.
National Jet Systems cabin air quality event procedures
Safety issue description: National Jet Systems’ cabin air quality events procedure focused on the recording/reporting of odours, post-flight care of crew and maintenance actions. However, it did not consider the possible application of the smoke/fumes procedure, or incapacitation procedure. As a result, there was an increased risk of flight crew being adversely affected by such an event during a critical stage of flight.
National Jet Systems pilot incapacitation training
Safety issue description:Although National Jet Systems contained procedures for recognition and management of pilot incapacitation, the associated training did not include the identification and response to subtle physical or cognitive incapacitation.
Glossary
CAQ Cabin air quality
CO Carbon monoxide
CO2 Carbon dioxide
PACK Pressurised air-conditioning kit
PF Pilot flying
PM Pilot monitoring
Sources and submissions
Sources of information
The sources of information during the investigation included:
the flight crew
National Jet Systems
Qantas chief medical officer
aircraft QAR data
Boeing Aircraft Company
Airservices Australia
Bureau of Meteorology.
References
Australian Transport Safety Bureau. (2007) Pilot Incapacitation: Analysis of Medical Conditions Affecting Pilots Involved in Accident and Incidents. 1 January 1975 to 31 March 2006. B2006/0170
Dismukes, K., Goldsmith, T. & Kochan, J. (2015). Effects of acute stress on aircrew performance: Literature review and analysis of operational aspects. National Aeronautics and Space Administration. (NASA) Report: NASA/TM-2015–218930.
European Aviation Safety Agency. (2017) CAQ Preliminary cabin air quality measurement campaign. EASA_REP_RESEA_2014_4
Federal Aviation Administration. (1991) Civilian training in high altitude flight physiology (FAA) Report: DOT/FAA/AM-91/13
International Civil Aviation Organisation. (2012). Manual of Civil Aviation Medicine (3rd ed.) ICAO Doc 8984, Montréal.
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 flight crew
National Jet Systems
Civil Aviation Safety Authority
Boeing Aircraft Company
Qantas chief medical officer
United States National Transportation Safety Board
Submissions were received from:
the incident flight captain
National Jet Systems
Boeing Aircraft Company
Qantas chief medical officer
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
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]Pilot Flying (PF) and Pilot Monitoring (PM): procedurally assigned roles with specifically assigned duties at specific stages of a flight. The PF does most of the flying, except in defined circumstances; such as planning for descent, approach and landing. The PM carries out support duties and monitors the PF’s actions and the aircraft’s flight path.
[2]Configuring for landing includes lowering wing flaps and slats, lowering landing gear and arming the speed brake.
[3]PAN: an internationally recognised radio call announcing an urgency condition which concerns the safety of an aircraft or its occupants but where the flight crew does not require immediate assistance.
[4]Hypoxia: is a physical state where sufficient oxygen is not available for the body to sustain life either due to low blood oxygen levels, or inadequate blood supply to the body.
[5]Authority gradient: the authority relationship between the captain and first officer. For example, in the case of a domineering captain and an unassertive first officer, the gradient is considered high.
Occurrence summary
Investigation number
AO-2023-026
Occurrence date
06/06/2023
Location
Hobart Airport
State
Tasmania
Report release date
16/04/2024
Report status
Final
Investigation level
Defined
Investigation type
Occurrence Investigation
Investigation status
Completed
Mode of transport
Aviation
Aviation occurrence category
Flight crew incapacitation
Occurrence class
Serious Incident
Highest injury level
Minor
Aircraft details
Manufacturer
The Boeing Company
Model
717-200
Registration
VH-NXM
Serial number
55094
Aircraft operator
National Jet Systems Pty Ltd
Sector
Jet
Operation type
Part 121 Air transport operations - larger aeroplanes
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).
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
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.
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.
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.
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).
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.
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 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).
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
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.
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.
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
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.
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.
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).
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).
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
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.
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
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.
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
Auxiliary
Main
Main
Auxiliary
Taxi Broome
119
189
189
119
Departure Broome
119
183
183
119
Change to auxiliary tanks
119
123
123
119
Change to main tanks
59
143
143
59
Estimated fuel on landing
59
117
117
59
Turkey Creek – Derby
Taxi Turkey Creek
59
117
117
59
Departure Turkey Creek
59
111
111
59
Estimated fuel on landing
59
21
21
59
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
Auxiliary
Main
Main
Auxiliary
1336: Taxi Turkey Creek (used 6 L each side)
74
110
70
119
1339: Departure Turkey Creek
74
107
67
119
1439: Change to auxiliary tanks
74
44
4
119
1449: Change left auxiliary to main tank
59
49 (44+5)
9 (4+5)
104
1454: Change right auxiliary to main tank
59
44
12 (9+3)
97
1504: Cross feed left main tank
59
34
2
97
1514: Dual engine surging
59
9
7 (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
Auxiliary
Main
Main
Auxiliary
1336: Taxi Turkey Creek (used 6 L each side)
73
110
70
119
1339: Departure Turkey Creek
73
104
64
119
1439: Change to auxiliary tanks
73
42
2
119
1449: Change left auxiliary to main tank
58
48 (42+6)
8 (2+6)
104
1454: Change right auxiliary to main tank
58
42
10 (8+2)
96
1504: Crossfeed left main tank
58
32
1
96
1514: Dual engine surging
58
6
5 (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.
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 number
Minimum requirements
1
5 hours on type for VFR operation
2
10 hours on type for IFR operation
3
Minimum of 750 total flying hours
4
Minimum 20 hours in command on MEA for VFR operation
5
A 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
Pilot
Minimum 5 hours on type for VFR operation
Minimum 10 hours on type for IFR operation
Minimum of 750 total flying hours
Pilot 2
No
No
Yes
Pilot 3
Yes
No
Yes
Pilot 4 (pilot of the accident flight)
Yes
Yes
No
Pilot 5
Yes
No
No
Pilot 7 (Interim HOFO)
No
No
Yes
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.
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
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.
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
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
Day
Night
Day
Night
Day
Night
184.3
1.4
158.9
13.9
4,542.4
13.3
Multi-engine
13.9
3.8
31.7
1.5
76.4
7.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.
Check-to-line for the pilot of the accident flight
2.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:
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.
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.
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
Class
Occurrence event
Surveillance type
Action Type
A - Critical
Complete loss/failure of the aviation system(s), or a destructive failure, impacting directly on the safe operation of the aircraft
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 June2023), 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.
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.
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 pilotidentified 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.
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.
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.
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.
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
AC
Advisory circular
AMC
Acceptable means of compliance
AME
Aircraft maintenance engineer
AOC
Air operators’ certificate
AWB
Airworthiness Bulletin
BAM
Broome Air Maintenance
CAO
Civil Aviation Order
CASA
Civil Aviation Safety Authority
CASR
Civil Aviation Safety Regulation
CEO
Chief executive officer
ELT
Emergency locator transmitter
FDP
Flight duty period
FOI
Flight operations inspector
FOR
Flight operations regulations
FQIS
Fuel quantity indicating system
GM
Guidance material
HAMC
Head of maintenance control
HOFO
Head of flying operations
ICUS
In command under supervision
IFR
Instrument flight rules
IPC
Instrument proficiency checks
LAME
Licenced aircraft maintenance engineer
MCM
Maintenance control manual
MEA
Multi engine aircraft
MEL
Minimum equipment list
MOS
Manual of standards
MR
Maintenance release
POH
Pilot operating handbook
RO FOI
Regulatory oversight flight operations inspector
RPT
Regular public transport
SMS
Safety management system
SOM
System of maintenance
STC
Supplement 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
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
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).
[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
This preliminary report details factual information established in the investigation’s early evidence collection phase and has been prepared to provide timely information to the industry and public. Preliminary reports contain no analysis or findings, which will be detailed in the investigation’s final report. The information contained in this preliminary report is released in accordance with section 25 of the Transport Safety Investigation Act 2003.
The occurrence
On the afternoon of 16 June 2023, a Cessna 210L, registered VH-FTM, taxied for a passenger air transport flight[1] from Groote Eylandt Airport, Northern Territory to Ngukurr Airport with a pilot and 5 passengers on board.
At about 1347:57, the pilot commenced the take-off from runway 10, using the full length of the runway. The surface wind at the time was recorded as south-southeast at 8–12 kt.
Based on the pilot recollection and flightpath data recorded on board the aircraft, the aircraft became airborne at about the midway point of the 1,903 m long runway. Shortly after becoming airborne, at an altitude of about 100 ft, the pilot noted engine surging accompanied by fuel flow fluctuations. The pilot continued to climb the aircraft straight ahead with a recorded ground speed of about 83 kt. At about 1349:35, and at an altitude of about 400 ft, the pilot made a broadcast on the Groote Eylandt Airport common traffic advisory frequency (CTAF) advising that they would be returning to Groote Eylandt Airport. At the same time, the pilot commenced a left turn and continued to climb to an altitude of about 500 ft (Figure 1).
Source: OzRunways and Google Earth annotated by the ATSB
At about 1349:58, the pilot had a brief discussion on the Groote Eylandt Airport CTAF with another pilot that was in the area advising that the aircraft had fuel flow issues.
Shortly after 1350:00, the aircraft began to descend with a recorded ground speed of about 104 kt. The aircraft passed diagonally over the runway near the threshold for runway 28, and made a right turn to fly parallel to the runway while continuing to descend.
The aircraft was captured by a security camera and continued to descend while tracking parallel to runway 28. A minute later, the aircraft flew past the end of runway 28 at an altitude of about 100 ft and a ground speed of about 91 kt.
The aircraft was captured by a second security camera as it touched down in a clear grassed area about 500 m west of the threshold for runway 10. The aircraft continued along the ground for about 120 m with a recorded groundspeed of 87–62 kt before hitting an embankment on the eastern side of a culvert (Figure 2). The aircraft traversed the culvert and then struck a larger embankment on the western side. The aircraft flipped and came to rest inverted on a mine service road (Figure 3).
The pilot and passengers exited the aircraft prior to the arrival of first responders. Four passengers received serious injuries while the pilot and 1 passenger sustained minor injuries. The aircraft was substantially damaged.
The pilot held a valid class 1 aviation medical certificate and a commercial pilot licence (aeroplane), having completed a flight review on 8 March 2023. At the time of the accident, the pilot had about 320 hours total aeronautical experience, including about 47 hours flying the Cessna 210L, and had commenced employment with the aircraft operator in May 2023.
Aircraft information
The Cessna 210L is a high-wing, all-metal, unpressurised aircraft with a retractable landing gear. The accident aircraft had a single Continental IO-520 reciprocating piston engine driving a constant-speed propeller. The aircraft, serial number 21061159, was manufactured in 1976 and was first registered in Australia in May 1976. Its last periodic inspection was completed 15 February 2023, and it had accrued 17,001.4 hours total time in service.
Prior to departure, the aircraft was loaded with 240 L of fuel (120 L in each of the two wing tanks).
Airport information
Groote Eylandt Airport was located about 1 km north of the town of Angurugu on Groote Eylandt, Northern Territory. The airport had an elevation of 53 ft above mean sea level and a single sealed runway, orientated in a 095°–275° magnetic direction, which was 1.903 km long. Groote Eylandt Airport was located within non-controlled Class G airspace and had a designated common traffic advisory frequency on which pilots were required to make positional broadcasts when operating within the vicinity of the airport.
Site and wreckage
The ATSB conducted an on-site examination of the aircraft wreckage. The aircraft initially struck the larger embankment on the western side of the culvert in an upright attitude. The culvert was located about 700 m to the west of the threshold for runway 10. The impact resulted in the detachment of the nose wheel and the right lateral displacement of the engine assembly. The aircraft then rotated vertically, pivoting at the nose, before coming to rest inverted (Figure 5).
All major sections of the aircraft’s structure were accounted for at the accident site. Flight control continuity was established where possible and wing flaps[2] were assessed to have likely been in the retracted position at the time of impact, rather than in the landing position. The landing gear was in the extended position and propeller damage was indicative of low rotational power at the time of impact.
Fuel was found spilled at the accident site and fuel samples were taken at various points throughout the fuel system. These samples showed no evidence of contamination with water. Fuel system components were examined and found to be free from contamination or obstruction.
review of airport documentation and the runway end safety area
analysis of flight path information from video recordings and flight data.
Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.
A final report will be released at the conclusion of the investigation.
Acknowledgements
The ATSB would like to acknowledge the significant assistance provided by the Northern Territory Police Force during the on-site investigation phase and initial evidence collection activities.
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
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,
[1] The flight was operated under Civil Aviation Safety Regulations Part 135 (Air transport operations - smaller aeroplanes).
[2] A movable surface on the trailing edge of a wing that, when extended, increases both lift and drag and reduces the stall speed. Flaps are extended to improve take-off and landing performance.
Final report
Executive summary
What happened
On the afternoon of 16 June 2023, a Cessna 210L, registered VH‑FTM and operated by Katherine Aviation, commenced a take‑off from runway 10 at Groote Eylandt Airport, Northern Territory with a pilot and 5 passengers on board.
Shortly after becoming airborne, at an altitude of 100 ft, the pilot reported that the engine began to surge, accompanied by fuel flow fluctuations. During the attempted turn back and landing, the aircraft passed diagonally over the runway then touched down in a clear grassed area outside the airport boundary. The aircraft continued along the ground for about 120 m and hit an embankment. The aircraft flipped and came to rest inverted on a service road.
Three passengers received serious injuries while the pilot and 2 passengers sustained minor injuries. The aircraft was substantially damaged.
What the ATSB found
The ATSB found that the engine mixture control was probably not set to full rich prior to commencing the take-off, resulting in reduced power and unanticipated engine behaviour. Likely surprised by the partial power loss, compounded by limited Cessna 210 experience, the pilot took no action to resolve the situation and did not effectively manage the attempted landing. The pilot’s take-off safety self-brief, and the aircraft operator’s documented example brief, did not include the actions to be taken in the event of a partial power loss. Additionally, the pilot had not completed weight and balance calculations for the flight and the aircraft departed 10 kg over the maximum take-off weight.
The ATSB also identified that the aircraft was likely being operated with a time-expired engine-driven fuel pump. Although the pump was unlikely to have contributed to the partial power loss, its time in service increased the likelihood of failure.
Additionally, the aircraft did not have, and was not required to have, upper torso restraints fitted to the rear passenger seats. Although any effect this had on the occupants’ injuries could not be determined, this increased the likelihood of serious injury in an accident.
What has been done as a result
On 17 June 2023, CASA issued a safety alert to Katherine Aviation that required the organisation to conduct a fleet-wide check of all time-lifed components that were either fitted or about to be fitted to the aircraft. The safety alert was issued following the identification of the time-expired engine-driven fuel pump fitted to VH-FTM. On 22 June 2023, Katherine Aviation completed the check and identified several further defects. In response, the organisation agreed to implement a maintenance incident reporting system and discontinue the cross hire of aircraft to reduce engineering workload.
Safety message
This accident highlights the challenges pilots face when dealing with unfamiliar situations during critical phases of flight. Operators can manage these challenges by documenting known operational scenarios and ensuring pilots are thoroughly trained before undertaking line operations.
Pilots can mitigate the risk by familiarising themselves with aircraft systems and the operational environment. Additionally, forward planning, such as a well-structured take-off safety brief, increases situation awareness, reduces mental workload under stress, and increases the prospect of a safe and well-managed outcome in the event of an emergency.
The ATSB research publication, Avoidable Accidents No.3: Managing partial power loss after take-off in single engine aircraft (AR-2010-055) provides further guidance.
Additionally, the ATSB SafetyWatch highlights the broad safety concerns that come out of our investigation findings and from the occurrence data reported to us by industry. One of the safety concerns is reducing the severity of injuries in accidents involving small aircraft which includes the fitment and use of seatbelts with upper torso restraints.
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
On the afternoon of 16 June 2023, a Cessna 210L, registered VH-FTM and operated by Katherine Aviation, taxied for a passenger air transport flight[1] from Groote Eylandt Airport to Ngukurr Airport, Northern Territory with a pilot and 5 passengers on board.
The weather at the time was recorded as a surface wind from south–southeast at 8–12 kt, no cloud, air temperature of 27°C, and visibility greater than 10 km.
At about 1347:57, the pilot commenced the take-off from near the threshold of runway 10. The pilot recalled setting the mixture to full rich prior to commencing the take-off. The pilot recalled looking at the gauge following the application of full throttle at the commencement of the take-off and noted no anomalies at that time. The pilot recalled that at take-off power the gauge should read about 130 lb/h (82 L/h).[2]
Recorded data showed that the aircraft became airborne at about the midway point of the 1,903‑metre runway (Figure 1). Shortly after becoming airborne, at an altitude of about 100 ft, the pilot noted engine surging accompanied by fuel flow fluctuations. The pilot assessed that there was insufficient runway remaining ahead of the aircraft to attempt a landing and elected to continue to climb the aircraft straight ahead with a perceived partial power loss. At this time, the recorded groundspeed was about 84 kt (accounting for wind, airspeed was about 89 kt), and the rate of climb was about 500 ft per minute.
The pilot recalled retracting the landing gear as the aircraft passed the end of the runway, and selecting flaps up once the aircraft had climbed above trees located about 800 m beyond the end of runway 10. They rememberedbeing ‘startled’ by the situation and could not recall completing initial engine trouble checks (see Actions to address fuel flow fluctuations). The pilot assessed there were no landing options ahead of the aircraft to conduct a landing and they elected to return to the airport to land on runway 28.
At about 1349:35, 45 seconds after the aircraft became airborne, and at an altitude of about 400 ft, the pilot made a broadcast on the Groote Eylandt Airport common traffic advisory frequency (CTAF) advising that they would be returning to Groote Eylandt Airport. At the same time, the pilot commenced a left turn and the aircraft continued to climb.
At about 1349:50, the pilot levelled off the aircraft at a height of about 500 ft. At about 1349:58, the pilot had a brief discussion on the Groote Eylandt Airport CTAF with another pilot advising that the aircraft had fuel flow issues.
The pilot noted ‘decreased engine performance.’ The pilot did not recall looking at the engine and fuel system instrumentation after levelling off, or taking action to restore engine performance, as they were focusing on avoiding an aerodynamic stall. At this time the aircraft had a calculated airspeed of about 94 kt, about 29 kt faster than the calculated stall speed of the aircraft.
Source: OzRunways and Google Earth, annotated by the ATSB
At about 1350:15, the pilot likely initiated a descent, descending to about 100 ft over the next 40 seconds (an average of 600 -fpm). The aircraft descended with a recorded average groundspeed of about 104 kt and reduced engine power. At about 1350:30 the pilot initiated a right turn.
At 1350:37 the aircraft passed diagonally over the runway near the threshold for runway 28 at a height of about 250 ft. At this location there was about 1,700 m of runway remaining to the aircraft’s right.
The pilot recalled trying to position the aircraft to land on runway 28 but remembered getting ‘further and further away’. They considered conducting a go-around, but believed the engine did not have sufficient performance to safely undertake the manoeuvre. The pilot recalled revising their intentions and aimed to touch down in a clear grassed area about 500 m beyond the threshold for runway 10, just beyond the airport boundary.
The aircraft continued the right turn and flew almost parallel to the runway. Recorded data showed that the pilot likely advanced the throttle, increasing engine power, as the aircraft descended through 200 ft, and the recorded descent rate then slowed to about 400 fpm.[3] The aircraft descended through 100 ft next to the eastern half of the runway and continued parallel to it about 50 m to the left of the runway centreline. The pilot could not recall when the landing gear was lowered.
The aircraft was recorded by a security camera as it continued to descend while tracking parallel to runway 28. At 1351:10, the aircraft flew past the end of runway 28 at a height of about 100 ft and a groundspeed of about 91 kt. At the same time, the engine power was reduced to idle.
The aircraft was recorded by a second security camera as it touched down in the clear grassed area. The aircraft continued along the ground for about 120 m and collided with an embankment on the eastern side of a culvert, outside of the aerodrome boundary, at about 62 kt (Figure 2). The aircraft traversed the culvert and then struck a larger embankment on the western side, flipped, and came to rest inverted on a service road (Figure 3).
The pilot and passengers exited the aircraft prior to the arrival of first responders. Three passengers received serious injuries while the pilot and 2 passengers sustained minor injuries (see Occupant restraints and injuries). The aircraft was substantially damaged, and there was no fire.
Context
Pilot information
The pilot held a valid class 1 aviation medical certificate and a commercial pilot licence (aeroplane), and last completed a flight review on 8 March 2023. At the time of the accident, the pilot had about 320 hours total aeronautical experience, including about 47 hours flying the Cessna 210.
The pilot commenced employment with Katherine Aviation in May 2023 with no prior commercial aviation experience. The pilot underwent 18.7 hours flying the Cessna 210 in May 2023 as pilot in command under supervision prior to passing a standard proficiency check on 29 May 2023. The check flight included 2 exercises for engine failure after take-off that were recorded as having been conducted to ‘high standard’. A review of the pilot’s training records identified no ongoing competency issues.
The pilot reported not feeling fatigued at the time of the accident.
Operator information
Katherine Aviation was a Civil Aviation Safety Regulation (CASR) Part 135 and 138 approved operator with 8 operational bases located throughout the Northern Territory, including Groote Eylandt. Katherine Aviation ceased operations in December 2023 and CASA cancelled both its CASR Part 135 and 138 approvals at the request of the organisation.
Airport information
Groote Eylandt Airport is located about 1 km north of the town of Angurugu on Groote Eylandt, Northern Territory. The airport has an elevation of 53 ft above mean sea level and a single sealed 1.9 km long runway, orientated in a 095°–275° magnetic direction (Figure 4). Groote Eylandt Airport was located within non-controlled Class G airspace and had a designated common traffic advisory frequency on which pilots were required to make positional broadcasts when operating within the vicinity of the airport.
Figure 4: Groote Eylandt Airport and surrounding area
Source: ATSB
Aircraft information
General aircraft information
The Cessna 210L is a high-wing, all-metal, unpressurised aircraft with a retractable landing gear. The accident aircraft, serial number 21061159, was manufactured in 1976 and was first registered in Australia in May 1976. It had a single Continental IO-520 fuel injected reciprocating piston engine driving a McCauley Propellers 3 blade constant-speed propeller.
The operator’s system of maintenance required a periodic inspection to be carried out every 200 flying hours or 12 months and the last periodic inspection was completed on 15 February 2023. It had flown 124.8 hours since the inspection and accrued 17,001.4 hours total time in service. The aircraft carried a current maintenance release with no defects recorded.
Previous power loss occurrence
In March 2023, a pilot of VH-FTM reported a drop in fuel flow and a partial power loss while taking off from Bickerton Island Airport, Northern Territory. The pilot rejected the take-off and grounded the aircraft. A licensed aircraft maintenance engineer (LAME) drained a small quantity of water from the fuel tanks, carried out an engine ground run, and could not reproduce the defect. It was reported that no endorsements were made on the maintenance release due to the limited work carried out.
Engine run-up checks
On the day of the accident, the pilot conducted 4 flights in VH-FTM during the morning and recalled no issues with the aircraft’s performance. The pilot recalled undertaking engine run‑up checks on the first flight of the day and did not identify any abnormalities. They did not undertake engine run‑up checks for the accident flight, and there was no requirement to do so in the operator’s procedures.
Fuel system
The aircraft was fitted with 2 internal fuel tanks, one in each wing, with a combined capacity of 340 L total (336 L useable). The aircraft was refuelled prior to the accident flight, with records indicating the aircraft departed Groote Eylandt Airport with 240 L of fuel (120 L in each of the tanks). The pilot recalled checking the fuel for water following refuelling and identified no contamination.
Engine mixture settings
The IO-520 engine mixture is set by the pilot to control the ratio of air to fuel delivered to the engine’s cylinders. This affects engine power and fuel usage, among other things. The following description is summarised from several sources including Schwaner (1991), Robson (2014) and Federal Aviation Administration (2023).
If a take-off was commenced with the mixture control in the ‘ground lean’ position (at lower airport elevations), it would result in a disproportionately low fuel component of the air-fuel ratio.[4] Indications of this, compared to a take-off with the mixture control set to full rich, include reduced fuel flow as less fuel is delivered to the engine cylinders. Additionally, as the fuel component of the air-fuel ratio reduces, there is less unburnt (cooling) fuel within the exhaust gas, so exhaust gas temperatures[5] (EGTs) increase, peaking at the stoichiometric (chemically maximised)[6] ratio.
If the fuel component of the air-fuel ratio is reduced beyond the stoichiometric ratio, EGTs begin to reduce again as there is less fuel available for combustion. Peak power generally occurs at a richer setting than at peak EGT.
Rough running can also be a symptom of an excessively lean air-fuel ratio.
Engine mixture settings for ground operations and take-off
The aircraft operator required ground operations to be undertaken with the engine leaned[7] to a ‘ground lean’ setting. The operator’s instructions stated:
Once the engine is started and RPM is stable lean the engine using the mixture control until a rise in RPM is observed. Lean further to achieve a slight RPM drop. Approximately a 10‑20 RPM drop is appropriate (“GROUND LEAN”).
The pilot was then required to advance the mixture control to full rich[8] prior to commencing the take-off in accordance with the operator and aircraft manufacturer instructions.
Fuel vaporisation
In high-temperature and/or high-altitude conditions, liquid fuel in a fuel system can boil, creating vapour. This can cause rough running or reduce available power, and when very severe, prevent fuel from reaching the engine (a condition called vapour lock).
The use of an auxiliary fuel pump, upstream of the vapour, can alleviate these effects. The Cessna 210L pilot’s operating handbook required the auxiliary fuel pump to be switched to ‘LO’ (low) for engine start and then off again. It advised that if the engine does not start, the pilot can switch the auxiliary fuel pump to ‘HI’ (high) momentarily to ‘clear [fuel] vapor from lines’.
According to experts in discussions with the ATSB, vaporisation that does not reach vapour lock can produce significant drops in fuel flow rates, but these tend to be erratic and intermittent and there is not a drop to a consistently low flow rate. It would often manifest on engine start as either trouble starting or immediate rough running. In an aircraft like the Cessna 210, the vapour will ultimately clear, including some returned to the fuel tanks from fuel pump oversupply.
Cessna service information letter (SIL) SE 79-25 (April 1979) Fuel flow stabilization provided information to aid pilots in the recognition and management of fuel vapor accumulation that could occur within the aircraft’s fuel system.[9] It stated that:
…indications of fuel vapor accumulation are fuel flow gauge fluctuations greater than 1 gal/h [equivalent to 3.8 L/h or 6 lb/h]. This condition with leaner mixtures or with larger fluctuations may result in power surges.
It went on to state that ‘fuel vapor indications are most likely to appear during climb and the first hour of cruise on each tank especially when operating at higher altitudes or in unusually warm temperatures.’
A supplement to SIL SE 79-25, released in June 1979, provided aircraft owners with a recommended procedures placard and a ‘special procedure card’ to be placed in the aircraft. The placard procedures to follow in the event of fuel flow fluctuations/power surges were:
• AUX FUEL PUMP — ON, ADJUST MIXTURE
• SELECT OPPOSITE TANK
• WHEN FUEL FLOW STEADY, RESUME NORMAL OPERATIONS
The placard was located on the right side of the instrument panel in VH-FTM but the procedure card was not found after the accident. Checking and setting the mixture control is a common step in diagnosing and resolving fuel flow fluctuations/power surges in light piston-engine aircraft.
The pilot did not recall receiving training on the actions to take in the event of fuel flow fluctuations and was not aware of the placard on board VH-FTM.
Weight and balance
The pilot weighed[10] each passenger and their baggage prior to the flight and entered these weights onto the aircraft manifest. However, the pilot did not complete the weight and balance calculations for the flight as they perceived there to be ‘time pressure’ to depart.
The ATSB calculated that, at the time of take-off, the aircraft had a gross weight of 1,734 kg, 10 kg above the maximum take-off weight. The baggage compartment had been loaded with 62 kg of baggage and equipment,[11] which was 8 kg above the 54 kg maximum compartment weight limitation. The aircraft was calculated to be within take-off balance limits.
Normal landing distance
At a gross weight of about 1,734 kg, flaps 30°, and the prevailing weather and environmental conditions at the time, the aircraft required a ground roll landing distance of about 268 m.
Take-off safety (self) brief
The pilot’s take-off safety brief[12] included actions to be taken in the event of a problem (not specifically defined) that might be encountered on the runway, airborne with runway remaining, or airborne without runway remaining. However, having commenced operations from the airport only 11 days prior to the accident, the pilot reported not being very familiar with the potential landing areas when departing using runway 10. Neither the pilot’s take-off safety brief, nor the aircraft operator’s documented example brief, contained the actions to be taken in the event of a partial power loss.
Site and wreckage
Accident site
The ATSB conducted an on-site examination of the aircraft wreckage. The aircraft initially struck an embankment on the eastern side of the culvert before impacting a larger embankment on the western side in an upright attitude. The culvert was located about 700 m to the west of the threshold for runway 10. The impact resulted in the detachment of the nose wheel and the right lateral displacement of the engine assembly. The aircraft then rotated vertically, pivoting at the nose, before coming to rest inverted (Figure 5).
All major sections of the aircraft’s structure were accounted for at the accident site. Flight control continuity was established where possible and the wing flaps[13] were retracted. The landing gear was extended and propeller damage was indicative of the engine running at low power at the time of impact. Fuel system components were examined and found to be free from contamination or obstruction. The ATSB took fuel samples at various points throughout the aircraft’s fuel system that showed no evidence of contamination with water.
Engine examination
Under observation by the ATSB, the engine was disassembled and examined at a Civil Aviation Safety Authority (CASA)-approved engine overhaul facility. The engine condition was consistent with its recorded time in service since overhaul, and no internal or external defects were identified that may have contributed to the fuel flow fluctuations and engine surging reported by the pilot.
Engine-driven fuel pump
The engine-driven fuel pump produces metered fuel pressure to the engine. In April 2022, the aircraft was under maintenance following a period of inactivity. It was reported that the engine could not be started and that a time-expired fuel pump was fitted for troubleshooting purposes. The engine could then be started, and the aircraft was released to service without replacing the pump with one that was not time‑expired. The operator reported that they suspect the time‑expired fuel pump was still fitted at the time of the accident.
After the accident, the fuel pump was bench tested, disassembled, and examined at a CASA-approved component overhaul facility under the supervision of the ATSB. The fuel pump functioned normally, however, testing of the low-pressure flow (applicable to the pressure at idle RPM) was limited by accident damage. When disassembled and examined, the pump had wear consistent with its age but was otherwise in good condition.
The pilot was using an electronic flight bag (EFB) application on a tablet throughout the flight. Data recovered from this application captured flight parameters every 5 seconds. Additionally, the aircraft was fitted with a J.P. Instruments EDM-900 engine data management system. Data recovered from this unit captured engine parameters every 6 seconds throughout the accident flight and 2 previous flights on the same day.
The groundspeed, fuel flow, and altitude information from the EFB and EDM-900 is depicted in Figure 6. The data indicates that:
On application of full throttle by the pilot (A), the fuel flow reached a mean of about 66 L/h (104lb/h), about 33 L/h less than recorded at take-off power on previous flights that day (Figure 7).
After the aircraft became airborne, the fuel flow increased to about 81 L/h for 1 data point (B) then fluctuated in the range 59-69 L/h, with an average of 66 L/h, before reducing significantly during the first part of the descent (C).
The fuel flow increased again to the previous level at around 200 ft (D), before being reduced to idle (E) when the aircraft was beside the runway, about 250–500 m from the eastern end.
Figure 6: VH-FTM groundspeed, fuel flow, height and heading data
Source: ATSB
Engine RPM fluctuated consistently with the EGTs and other parameters. The EGTs on the accident flight were found to be around 119 °F (48 °C) hotter than recorded at take-off power on previous flights that day (Figure 7).
Figure 7: VH-FTM take-off fuel flow and average EGT for flights on 16 June 2023
VH-FTM had three rows of seats, with two seats per row. The pilot, who was seated in the front left seat, received minor lacerations to their lower body. The front right seat passenger received serious injuries, including to the head, limbs, and abdomen, and spinal fractures. Two of the passengers seated in the rear of the aircraft received serious injuries including to the limbs and head. The remaining 2 passengers in the rear received minor injuries.
The front 2 seats were each fitted with a lap belt and one upper torso restraint (UTR). The rear seats were fitted with lap belts only with no UTRs. This was consistent with part 90.105 of the Civil Aviation Safety Regulations 1998 (CASR) which only required the front row seats to be fitted with an approved safety harness comprising a lap belt and at least one shoulder strap (restraint). Currently, small aeroplanes manufactured after 12 December 1986 and helicopters manufactured after 17 September 1992 are required to have UTRs fitted for all seats.
In 2019, the ATSB released the following safety advisory notice to operators of small aeroplanes and helicopters, and safety recommendation to the Civil Aviation Safety Authority (CASA):
: The Australian Transport Safety Bureau strongly encourages operators and owners of small aeroplanes manufactured before December 1986 and helicopters manufactured before September 1992 to fit upper torso restraints to all seats in their aircraft (if they are not already fitted).
AO-2017-005-SR-027: The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority consider mandating the fitment of upper torso restraints (UTRs) for all seats in small aeroplanes and helicopters, particularly for those aircraft (a) being used for air transport operations and/or (b) for those aircraft where the aircraft manufacturer has issued a mandatory service bulletin to fit UTRs for all seats (or such restraints are readily available and relatively easy to install).
In response to the safety recommendation, CASA acknowledged that fitting UTRs had merit, and that it encouraged operators to do so, but it did not support the mandatory fitment of UTRs for all seats in small aeroplanes and helicopters.
Partial power loss after take-off in single-engine aircraft
Partial engine power loss is more complex and more frequent than a complete engine power loss. The ATSB report Managing partial power loss after take-off in single-engine aircraft (AR‑2010‑055) identified 242 reported occurrences between 2000 and 2010 involving single-engine aircraft sustaining a partial engine power loss after take-off. The report stated that after take-off, a partial power loss is 3 times more likely in a light single-engine aircraft than a complete engine failure. In two-thirds of these occurrences, the pilot turned back toward the aerodrome.
When the amount of power lost is close to that experienced with a complete loss, the pilot is likely to identify the severity of the situation readily and take action similar to that expected for a total power loss. At the other end of the spectrum, where the remaining engine power allows the aircraft to climb, more options are available to the pilot, such as climbing slowly into the circuit or carefully turning back to the aerodrome (Figure 8).
Figure 8: Conceptual uncertainty by amount of power loss
Source: ATSB
A turn back requires accurate flying during a period of likely high stress. According to the ATSB report AR-2010-055, a take-off safety brief gives pilots a much better chance of maintaining control of the aircraft, and helps the pilot respond immediately. Considerations include planning for rejecting a take-off, landing immediately within the airport, landing beyond the airport, and conducting a turnback towards the airport.
The ATSB’s research suggested that the following initial actions should be performed when responding to a partial loss in power:
Maximise height and distance — climb at the manufacture’s recommended ‘best rate’ or ‘best angle’ speeds depending on the aircraft and location.
Time permitting, conduct basic initial engine trouble checks in accordance with the aircraft manufacturer’s advice.
Fly the aircraft to make a landing. If a turn is conducted, be mindful that an increase in elevator input to maintain a desired descent path will reduce the margin to the stall. Having a planned minimum turning height is also recommended, with CASA suggesting a minimum height of 200 ft above ground level.
Below the minimum turning height, if continued climb to a safer altitude is possible, it should be done with level wings. With insufficient remaining power to climb, landing ahead is the only option.
Re-assess landing options throughout any manoeuvres.
Land the aircraft.
Safety analysis
Introduction
Shortly after becoming airborne, at an altitude of about 100 ft, the engine fuel flow increased to 81 L/h for 1 data point, then fluctuated around an average of 66 L/h with a range of about 10 L/h. This is consistent with the pilot’s recollection of fuel flow fluctuations (as would have been indicated on the gauge at the time). Exhaust gas temperatures (EGTs) were also around 48 °C hotter than recorded at take-off power on previous flights that day.
Although there are a range of potential reasons for surging (RPM fluctuations), the much lower average fuel flow and hotter EGTs than on previous flights are strongly indicative of an issue with the fuel supply.
An inspection of the aircraft wreckage did not identify any engine, fuel system, or other mechanical factors that may have led to the partial power loss. The pilot noted no engine performance issues during earlier flights that day, there was sufficient fuel on board the aircraft, and no fuel contamination was apparent.
The engine driven fuel pump fitted to the aircraft had likely exceeded its overhaul life. However, when tested it functioned normally and was likely doing so at the time of the accident.
Engine performance
Power loss, fuel flow fluctuations and surging
The partial power loss was likely due to the engine mixture control being incorrectly set at the commencement of take-off. This resulted in an air-fuel ratio that was too lean and manifested as reduced power and unanticipated engine behaviour.
The EDM-900 engine data management system data is consistent with this scenario and indicated that on application of full throttle, the average fuel flow attained during take-off was about 66 L/h. This was about 33 L/h less than other take-offs that day. The fuel flow indications were consistent with a reduced fuel component of the air-fuel ratio, where less fuel is being delivered to the cylinders, and would have resulted in reduced engine power. The exhaust gas temperatures (EGTs) were also found to be around 48°C hotter than recorded at take-off power on previous flights that day. The hotter EGTs were also consistent with a reduced fuel component of the air-fuel ratio where there is less unburnt (cooling) fuel within the exhaust gas, resulting in increased EGTs.
The operator required ground operations to be undertaken with the mixture control set to a ‘ground lean’ setting. For take-off, both the operator and aircraft manufacturer procedures then required the mixture control to be set to ‘full rich’. Combined with the recorded data, it is therefore probable that the mixture control, which is used to adjust the air-fuel ratio, was left in the ‘ground lean’ position for take-off.
There were no indications of mechanical failure with the engine or fuel system, and no contaminants were present within the fuel tested. Consequently, these factors were considered unlikely to have contributed to the power loss. Fuel vaporisation was also considered unlikely to have been present during the flight. While fuel vaporisation can produce significant variation in fuel flow rates, and consequently the fuel component of the air-fuel ratio, the effect on fuel flow would likely be erratic and intermittent and not a consistent reduction as captured by the EDM-900 data.
Reasons for probable incorrect mixture control settings
The pilot reported perceiving time pressure to depart and this, coupled with their relative inexperience flying the Cessna 210, may have contributed to the pilot overlooking the mixture control setting prior to take-off. Although the pilot recalled setting the mixture control to full rich, the accuracy of a person’s memory about a sequence of events involving a serious incident or accident can be affected by a range of factors including workload, the complexity of the events, the pace at which the events occur, and interference from other sequences of events that may occur before and after the sequence of interest (Davis 2001).
Pilot actions
Initial response
The pilot recalled looking at the aircraft’s fuel flow gauge on the application of full throttle and noted no anomalies. However, the gauge would likely have been indicating the significantly reduced fuel flow. Had the pilot identified this indication at this early stage, or during the take-off, the take-off could have been aborted while the aircraft was still on the runway.
Once airborne and having determined that they could not land on the remaining runway or cleared area beyond the runway, the pilot’s initial actions to fly the aircraft at a safe speed and continue to gain altitude were appropriate and consistent with the ATSB’s previous guidance on the management of a partial power loss.
The aircraft was 10 kg over the aircraft’s maximum take-off weight and this likely reduced the aircraft’s climb performance. Nevertheless, recorded data indicates the aircraft was able to achieve a rate of climb of about 500 ft per minute at about 89 kt.
Having levelled off, the aircraft spent about 25 seconds at 500 ft which would have provided sufficient time to conduct initial engine troubleshooting actions such as those placarded on the instrument panel (which would prompt a mixture adjustment and likely resolved the problem). The recorded fuel flow fluctuations exceeded the amount for which the actions were required. However, the pilot reported being ‘startled’ by the situation and was focused ‘on not stalling the aircraft’, although there was a significant margin above the stall speed.
An unexpected event, such as a partial power loss during take-off, can result in the cognitive-emotional response commonly defined as ‘surprise’. Surprise can be described as a combination of physiological, cognitive, and behavioural responses which can include an inability to comprehend and analyse, a failure to recall appropriate operating practices, freezing, and a loss of situation awareness (Rivera et al. 2014). It is likely that the pilot was impacted by the effects of surprise following the partial power loss and this, compounded by their relative inexperience flying the Cessna 210, resulted in the omission of the engine trouble checks.
Return to the airport
The pilot recalled being unfamiliar with emergency landing options beyond the airport and elected to conduct a left turn to return to the airport to land on runway 28. The aircraft passed diagonally over the runway near the threshold for runway 28, at an altitude of about 250 ft, while descending. At that time, there was about 1,700 m of runway to the aircraft’s right.
Considering the ideal response from this point, it was likely possible to decrease power, extend flap, lower landing gear and establish a controlled descent, for example, with a rate of descent of no greater than 1,000 fpm. This would allow a descent from 250 ft to near ground level in about 15 seconds. In this time, without reducing speed, the aircraft would cover about 800 m distance, with sufficient runway left to flare, land, and stop. Reducing speed (while maintaining a safe buffer above the stall) would provide more time and distance to descend and align the aircraft with a suitable landing surface.
The pilot recalled diverging from the runway, and made a limited attempt to correct the lateral deviation, instead revising their landing plan for a cleared area beyond the airport boundary. From this point, a successful forced landing would be more likely with reduced speed. However, once it was apparent that a landing could be completed, the aircraft was not fully configured for a forced landing by lowering flap, resulting in the aircraft landing further along the selected landing location and at a higher touchdown speed. The lack of aircraft control inputs to realign with the runway and the misconfiguration of the aircraft for landing were likely a result of the continued effects of surprise.
Take-off safety brief
The pilot’s take-off safety brief did not include the landing options beyond the airport or the actions to take in the event of a partial power loss. The aircraft operator’s example brief also did not include these elements. Had the brief included these aspects, the pilot would have been better prepared to manage the situation and likely less affected by surprise.
Time-expired engine-driven fuel pump
A time expired fuel pump had been fitted to the aircraft in April 2022 for troubleshooting purposes and was likely still fitted to the aircraft at the time of the accident. While the pump functioned normally during post-accident testing, its internal components had wear consistent with the pumps time in service. Operation of components in excess of the stated overhaul periods increases their likelihood of failure, and therefore safe operation of the aircraft.
Occupant injuries
While the front seats were fitted with lap belts and shoulder straps, the rear seats were fitted with lap belts with no upper body restraints. The rear seats were not required by regulation in this instance.
The occupants in the front and rear seats received several upper body injuries between them. The liveable space in the aircraft was compromised by significant damage to the cockpit and cabin areas. This made it more likely that the aircraft occupants, particularly their upper bodies, would come into contact with the aircraft structure during the accident sequence even had upper torso restraints been fitted and used. However, upper torso restraints can significantly reduce the risk of injury, compared to lap belts only, by minimising the flailing of the upper body and the potential of impacts involving the head and upper body.
Weight and balance
Although the pilot weighed each passenger and their baggage prior to the flight and entered these weights onto the aircraft manifest, the pilot did not complete the weight and balance calculations for the flight as they perceived there to be time pressure to depart. The ATSB later calculated that the aircraft was 10 kg over the maximum take-off weight. While this would have had a slight effect on the aircraft’s performance, if weight and balance is not confirmed by finalising the calculations there is a risk of a more significant effect.
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 partial engine power loss and collision with terrain involving Cessna 210L VH-FTM, near Groote Eylandt Airport, Northern Territory on 16 June 2023:
Contributing factors
The pilot probably did not set the engine mixture control to full rich prior to commencing the take-off as required by the operator and manufacturer procedures. This resulted in an incorrect air-fuel ratio (too lean) which manifested as a partial power loss with unanticipated engine behaviour.
Likely surprised by the partial power loss, the pilot did not attempt to troubleshoot the issue by checking the mixture control setting and did not effectively manage the aircraft’s flightpath during the attempted landing on runway 28.
Other factors that increased risk
The pilot’s take-off safety brief (self-brief), and the aircraft operator’s documented example brief, did not contain the actions to be taken in the event of a partial power loss.
The aircraft was likely being operated with a time-expired engine-driven fuel pump, increasing the likelihood of its failure.
The aircraft did not have, and was not required to have, upper torso restraints fitted to the rear passenger seats, increasing the likelihood of serious injury in an accident.
The pilot did not complete the weight and balance calculations for the flight as they perceived there to be time pressure to depart, and the aircraft was 10 kg over the maximum take-off weight.
Safety actions
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future. ATSB has so far been advised of the following proactive safety action in response to this occurrence.
Safety action addressing time-lifed components
On 17 June 2023, CASA issued a safety alert to Katherine Aviation that required the organisation to conduct a fleet wide check of all time-lifed components that were either fitted or about to be fitted to the aircraft. The safety alert was issued following the identification of the time-expired engine-driven fuel pump fitted to VH-FTM. On 22 June 2023, Katherine Aviation completed the check and identified several further defects. In response, the organisation agreed to implement a maintenance incident reporting system and discontinue the cross hire of aircraft to reduce engineering workload.
Sources and submissions
Sources of information
The sources of information during the investigation included:
pilot of the accident flight
Katherine Aviation
Civil Aviation Safety Authority
United States National Transportation Safety Board
Northern Territory Police Force
Bureau of Meteorology
maintenance organisation for VH-FTM
Groote Eylandt Airport
first responders
McLarens Aviation, acting for the insurer
security camera footage of the accident flight
recorded data from aircraft’s EDM-900 unit.
References
Australian Transport Safety Bureau. (2013). Avoidable accidents no. 3: Managing partial power loss after take-off in single-engine aircraft (AR-2010-055). Canberra, Australia.
Davis, D., & Follette, W. C. (2000). Foibles of witness memory for traumatic/high profile events. J. Air L. & Com., 66, 1421.
Federal Aviation Administration. (2023). Pilot’s Handbook of Aeronautical Knowledge. U.S.
Rivera, J., Talone, A. B., Boesser, C. T., Jentsch, F., & Yeh, M. (2014). Startle and surprise on the flight deck: Similarities, differences, and prevalence. In Proceedings of the human factors and ergonomics society annual meeting (Vol. 58, No. 1, pp. 1047-1051). Sage CA: Los Angeles, CA: SAGE Publications.
Robson, D. (2014). Basic Aeronautical Knowledge including Human Factors (3rd ed). Brisbane, Qld, Australia: Aviation Theory Centre.
Schwaner, J. (2017). Sky Ranch engineering manual: Operation, failure, repair, piston aircraft engines (2nd ed). Aircraft Technical Book Company LLC.
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, and parties with an involvement:
pilot of the accident flight
Katherine Aviation
Civil Aviation Safety Authority
United States National Transportation Safety Board
McLarens Aviation, acting for the insurer
Submissions were received from McLarens Aviation.
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
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]The flight was operated under Civil Aviation Safety Regulations Part 135 (Air transport operations - smaller aeroplanes).
[2]The fuel flow gauge was located on the lower centre of VH-FTM’s instrument panel and depicted fuel flow in lb/h.
[3]The recorded data was rounded to the nearest 100 ft, and showed no change in altitude for 15 seconds.
[4] The air-fuel ratio refers to the ratio of the weight of air to that of the fuel when the mixture is delivered to the engine cylinders. This ratio is crucial for determining the efficiency of combustion and, consequently, the power output of the engine.
[5]The temperature of the exhaust gases at the exhaust manifold.
[6]The stoichiometric ratio, or chemically correct mixture (CCM), is the chemically perfect air-fuel ratio that would theoretically result in the consumption of all oxygen and fuel during combustion.
[7]The manipulation of the cockpit mixture control resulting in the reduction of the fuel component of the air-fuel ratio provided to the combustion cylinders.
[8]Full rich only applies at lower-elevation aerodromes (below 3,000 ft), which includes Groote Eylandt Airport.
[9]Fuel vapour accumulation can result in vapour lock, which prevents the supply of fuel due to bubble(s) of vapour in the fuel lines.
[10]VH-FTM carried passenger and cargo weighing scales that had been recently calibrated.
[11]Baggage and equipment were weighed by the ATSB at the accident site.
[12]A self-brief undertaken by the pilot of a single-pilot operation prior commencing take‑off.
[13] A movable surface on the trailing edge of a wing that, when extended, increases both lift and drag and reduces the stall speed. Flaps are extended to improve take-off and landing performance. The Civil Aviation Safety Authority publication Flight Instructor Manual (Aeroplane) states that when landing without flaps ‘the descent path may be flatter, making judgment more difficult…Due to the absence of drag there may be a longer float period’.
Occurrence summary
Investigation number
AO-2023-028
Occurrence date
16/06/2023
Location
Groote Eylandt Airport
State
Northern Territory
Report release date
13/08/2024
Report status
Final
Investigation level
Short
Investigation type
Occurrence Investigation
Investigation status
Completed
Mode of transport
Aviation
Aviation occurrence category
Engine failure or malfunction
Occurrence class
Accident
Highest injury level
Serious
Aircraft details
Manufacturer
Cessna Aircraft Company
Model
210L
Registration
VH-FTM
Serial number
21061159
Aircraft operator
Katherine Aviation Pty Ltd
Sector
Piston
Operation type
Part 135 Air transport operations - smaller aeroplanes
On 4 May 2021, at 1130 Wallis and Futuna Time, the pilot of a De Havilland DHC-6-300 aircraft, F-OCQZ reported a reduction in engine power on approach to Point Vele Airport, Territory of the Wallis and Futuna Islands.
The French Bureau d'Enquêtes et d'Analyses pour la sécurité de l'aviation civile (BEA) is investigating this occurrence. As part of the investigation, engine number 2 was shipped to an Australian maintenance facility for further examination, and the BEA requested appointment of an Accredited Representative from the ATSB.
To facilitate this request, the ATSB initiated an external investigation under the provisions of the Transport Safety Investigation Act 2003.
Engine examination reports were provided to the BEA by the Australian maintenance facility, at which point ATSB investigation support was completed. Should further assistance be required, the investigation will be reopened.
Occurrence summary
Investigation number
AE-2021-006
Occurrence date
04/05/2021
Location
Point Vele Airport, Territory of the Wallis and Futuna Islands
State
International
Investigation type
Accredited Representative
Investigation status
Completed
Aircraft details
Manufacturer
De Havilland Canada/De Havilland Aircraft of Canada
Between June 2023 and April 2024, 3 misaligned take-offs at Perth Airport, Western Australia, were reported to the ATSB. Each incident occurred before first light and involved the pilots inadvertently lining the aircraft up with the edge lighting, rather than the centreline, on runway 06 prior to take-off.
On 12 June 2023, a Virgin Australia Airlines Boeing 737-800 aircraft, registered VH-IWQ, was being operated on a regular passenger transport flight from Perth, Western Australia, to Sydney, New South Wales. During the take-off roll, the flight crew identified that the aircraft was aligned with the left edge lights of the runway and manoeuvred to the centreline. The flight continued without further incident. A subsequent aircraft and runway inspection did not find any damage.
On 10 August 2023, a Western Sky Aviation Cessna Conquest 441, registered VH‑NSA, was being operated on a passenger charter flight from Perth to Southern Cross, Western Australia. During the take-off roll, the pilot detected an impact with the aircraft. After take‑off, the pilot returned to Perth and a subsequent inspection found no aircraft damage, but identified several damaged runway edge lights.
On 4 April 2024, VH‑NSA was again operating a passenger charter flight from Perth to Southern Cross. During the take-off roll, the pilot (different to the previous incident) heard an unusual noise but believed it originated from inside the cabin. As all engine indications were normal, they continued the departure. A runway inspection conducted by the aerodrome operator later that morning found several damaged runway edge lights. The pilot identified minor damage to the propeller on the right engine after returning to Perth Airport.
What the ATSB found
The ATSB found that, in all 3 incidents, when entering runway 06 from taxiway V, the pilots taxied past the turn onto the centreline and lined the aircraft up along the runway edge lighting on the far side of the runway to where they entered. In each incident, as the pilots believed they had correctly aligned the aircraft with the runway centreline, they commenced the take-off.
Several factors known to increase the risk of a misaligned take-off in the dark were identified as present in all 3 incidents. In terms of the runway environment, there was an unlit and unmarked extended pavement area on each side of runway 06, which made the runway appear wider. In relation to the available airport lighting, the lead-on lights from taxiway V continued across the taxiway to the other side, meaning there was limited guidance when taxiing to the runway’s centreline; recessed edge lights at the start of runway 06 could be mistaken for centreline lighting, and there was limited ambient airport lighting around taxiway V and runway 06 to enhance visibility. The taxi lighting on one of the aircraft was reported by the pilots as being of limited benefit. Additionally, the required runway markings were reported by 2 of the incident pilots to be difficult to see at night.
One factor specific to the flight crew in incident 1 was their attention was diverted to completing pre-take-off tasks and their take-off clearance while lining up on the runway. This divided their attention between the flight deck and the monitoring of the external environment.
The ATSB also identified differences in how the pilots responded to the misaligned take‑off. In the first incident, the flight crew identified that they had lined up in the incorrect position, manoeuvred the aircraft onto the centreline, and continued the take-off and flight. The pilot of the second incident detected an impact during the take-off roll and decided to conduct a return to Perth for further inspection. The pilot of the third incident was not aware the aircraft was misaligned on the runway edge and damage to the propeller blade was not detected until several flights later.
What has been done as a result
After the incidents in August 2023 and April 2024, Western Sky Aviation distributed notices to its flight crew that included strategies to check runway alignment prior to take‑off, including the use of an electronic flight bag aerodrome chart and integrated landing systems, where available.
Perth Airport requested an update to the Aeronautical Information Publication supplement, effective November 2023, to identify a misaligned take-off hotspot on runway 06, and highlight to pilots that runway 06 did not have centreline lighting and that there was extra pavement on either side of the runway. The En Route Supplement Australia was updated to reflect the misaligned hotspot area in March 2024. Further, in works to repaint the runway markings, completed in April 2024, Perth Airport also painted chevrons on the extra pavement on either side of runway 06 to delineate this area from the useable runway to assist pilots with determining their position prior to commencing take-off.
Following the incident in June 2023, Virgin Australia Airlines completed a number of safety actions, including:
added caution notes to its Perth Airport supplementary port information about centreline misidentification on runway 06
revised the before take-off procedure to reallocate tasks earlier in the taxi to reduce flight crew workload during line-up.
developed case studies involving this event, which were incorporated into non‑technical skills training.
Safety message
The features of airport runways and taxiways can vary, and the combination of these features or lack of guidance to assist pilots to navigate or confirm their aircraft’s position can increase the risk of runway misalignments. Further, this can be exacerbated at night‑time where the amount of visual information available is markedly reduced. These reduced visual cues can affect pilots even when they are familiar with the airport. It is important for all pilots to thoroughly brief themselves with the local conditions to increase their awareness of the environment. Pilots are also encouraged to report any circumstances where they believe they may have conducted a misaligned take-off, to limit the risk to their aircraft and others subsequently using the same runway. This would also allow aerodrome operators to identify any trends or emerging misaligned take-off hotspots to consider mitigations.
Summary video
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 occurrences
Between June 2023 and April 2024, 3 misaligned take-off events occurred at Perth Airport, Western Australia. Each incident occurred prior to first light and involved the pilots inadvertently lining the aircraft up with the runway 06 edge lighting, rather than the centreline, prior to take‑off.
Incident 1
On the morning of 12 June 2023, the captain and first officer (FO) of a Virgin Australia Airlines Boeing 737-800, registered VH-IWQ, prepared for a regular passenger transport flight from Perth, Western Australia, to Sydney, New South Wales.
At 0600 local time, the aircraft was pushed back from the bay and the captain switched on the aircraft navigation lights and logo lights. The FO obtained a taxi clearance from air traffic control, and the captain switched on the taxi lights before taxiing the aircraft to runway 06 using taxiway ‘V’ (Figure 1).[1] Around 12 minutes later, as they approached the holding point[2] on taxiway V from the south, the FO reported to the controller that they were ‘ready’ [for take-off]. At this time, the flight crew commenced the ‘before take-off’ procedure (see Incident 1 Virgin Australia procedures). When they arrived at the holding point, the captain turned off the taxi light to avoid stunning the flight crew of another aircraft on the opposite taxiway.
At 0616, after the controller provided a line-up clearance, the flight crew taxied the aircraft onto runway 06 and switched on the taxi lights, landing lights, and strobe lights. Prior to entering the runway, the flight crew recalled crosschecking the runway number to assist with positioning the aircraft, as per the procedure. The captain did not recall whether there were lead-on lights to the runway.[3]
The FO reported that the markings that would lead into the runway centreline were not followed but believed the captain was trying to maximise the take-off distance on the runway. The captain reported in interview that maximising take-off distance was their general practice. The FO also recalled that they were completing the line-up scan inside the flight deck during the turn onto the runway. Recorded flight data showed the aircraft was taxied past the runway centreline and lined up on the left edge lights of runway 06 (Figure 1). Both flight crew believed they were lined up on the runway centreline lights.
At 0616:50, as the aircraft was lined up, the controller issued a take-off clearance to the flight crew, and the FO focused on preselecting the next radio frequency for departure. At this time, the captain handed over control of the aircraft to the FO, who was the designated pilot flying[4] for the sector. At 0617:18, the captain set take-off thrust. In interview later, the FO reported that, during the commencement of the take-off roll they noticed a raised edge light and realised the aircraft was lined up on the runway edge. In response, they manoeuvred the aircraft toward the centreline as evidenced by the right rudder pedal input at 0617:20. Shortly after, at 0617:24 the aircraft was aligned with the runway centreline. The FO recalled asking the captain to confirm whether to continue with the take-off, which the captain confirmed as they believed they were above the take‑off decision speed.[5]
Figure 1: Overhead of Perth Airport and showing the aircraft’s line up on runway 06 with key events during the take-off for incident 1
Taxi and take‑off roll during the departure is shown in green. Source: APS Aerospace Flight Animation System based on flight data recorder from the aircraft, annotated by the ATSB
The continuation of the take-off and departure was normal. Once airborne, the flight crew discussed the incident. As they believed they did not strike the runway lights they decided to continue the flight and reported the incident after arriving in Sydney around 4 hours later. After the incident, a runway inspection was conducted, which identified no damage to the runway lights. The operator completed an engineering inspection and found there was no damage to the aircraft.
Incident 2
On the morning of 10 August 2023, the pilot of a Cessna 441 aircraft, registered VH-NSA and operated by Western Sky Aviation, prepared for a passenger charter flight from Perth to Southern Cross, Western Australia.
At around 0500, when at a parking bay at the terminal, the pilot completed the taxi checklist, which included switching on the navigation light, taxi light, and beacon light. In interview later, the pilot commented that the environment appeared dark, even with the aircraft lighting on. At 0508, the pilot received a taxi clearance from air traffic control and taxied to taxiway V towards runway 06.
The pilot recalled that, while at the northern runway holding point, lights from what they assumed to be another aircraft stunned them, affecting their vision. Three minutes later, at the runway holding point, the pilot was cleared to line up and wait on runway 06 until another aircraft had departed. Prior to entering the runway, the pilot completed the line‑up checklist, which included switching on the anti‑collision lights and landing lights.
Air traffic control recorded data showed that the aircraft taxied past the centreline of the runway and lined up along the right edge lighting (Figure 2). During interview, the pilot recalled that the runway markings were ‘scuffed’ and difficult to see, but they believed they were lined up on the runway centreline lighting. They also noticed ‘plenty’ of runway to their right and reported not realising there were no centreline lights on runway 06.
At 0512, the aircraft was cleared for take-off. During the take-off roll, the pilot heard an impact outside the aircraft and suspected a birdstrike had occurred. The pilot decided they were above the rejected (decision) take-off speed so continued with the take-off, but manoeuvred the aircraft to the left, toward the centreline. After the aircraft was airborne, the pilot contacted air traffic control to request a return to Perth. A runway inspection identified damage to several runway edge lights. There was no damage to the aircraft.
Figure 2: Overhead of Perth Airport showing the aircraft’s line up and take-off on runway 06 for incident 2
Taxi and take‑off roll during the departure is shown in red. Source: Google Earth, annotated by the ATSB
Incident 3
On the morning of 4 April 2024, VH-NSA was again prepared for a passenger charter flight from Perth to Southern Cross, Western Australia. During preparation, the pilot[6] reviewed the relevant Notices to Airmen[7] that stated, due to runway resealing works the centreline lights on taxiway V, the runway 24 to taxiway V lead-off lights, and taxiway V stop bar[8] were unserviceable. Temporary blue edge lighting was provided on taxiway V while the resealing work was completed.
At around 0500, while at the parking bay at the terminal, the pilot completed their taxi checklist, which included switching on the navigation light, taxi light, and beacon light. In interview, the pilot commented that they felt the aircraft lights did not appear to illuminate the environment well, so they switched the lights off and on again to confirm their operation. At 0509, the pilot taxied to taxiway V, noting that the northern corner between taxiway V and runway 06 appeared darker than usual, and there was little ambient light in the area.
At 0519, the pilot called ‘ready’ [to take off] to air traffic control and 2 minutes later received a clearance to line up on runway 06. Prior to entering the runway, the pilot completed the line‑up checklist, which included switching on the anti-collision lights and landing lights. To assist with runway alignment, the pilot reported that they would normally taxi between the runway number and the gap between the threshold markings (see Markings). The pilot reported they lined up with a white line, which they assumed was the runway centreline marking. They also recalled that the runway markings appeared to be ‘scuffed’ and were difficult to see. They also checked for the runway edge lights on both sides and believed they were aligned with the runway centreline.
Air traffic control recorded data showed that the aircraft taxied past the runway centreline and lined up along the edge lighting on the right side of the runway (Figure 3). At 0523, air traffic control issued the take-off clearance. During the take-off roll, the pilot reported hearing a noise and believed that the sound originated within the cabin, so continued the take-off. They also reported that they checked their engine indications, which were normal. The pilot departed and completed the planned flight.
Figure 3: Overhead of Perth Airport showing the aircraft’s line up and take-off on runway 06 for incident 3
Taxi and take‑off roll during the departure is shown in orange. Source: Google Earth, annotated by the ATSB
The pilot conducted a flight back to Perth from Southern Cross and then flights from Perth to Cue and return. After each of these flights, the pilot conducted a walk around the aircraft. This involved the pilot using the torch from their phone when conducting the aircraft inspection in the dark. The first inspection was conducted in the dark, and the others were during daylight. The inspection involved the pilot walking in a clockwise direction around the aircraft and included an examination of the propellers for damage. A checklist was reviewed afterwards to ensure all the components were checked.
Later in the morning, Perth Airport contacted the operator to advise that several runway edge lights were damaged, which they determined were coincident with the aircraft’s departure based on recorded departures and closed-circuit television footage. At 1208, the aircraft returned to Perth and during the walk around inspection, the pilot noticed damage to one propeller blade on the right engine (Figure 4).
Figure 4: Damage to propeller blade on right engine
Source: Operator
Context
Pilot information
All the pilots held the appropriate licences and qualifications to conduct their respective flights. ATSB analysis of sleep and roster information obtained from each of the pilots found that, despite the early morning departure time, there was a low likelihood any individual was experiencing a level of fatigue known to adversely affect performance.
The ATSB also considered whether pilot familiarity with the airport played a role in the incidents. Both pilots involved in the first incident were based in Sydney. The captain last operated from Perth one month prior to the incident, while the FO last operated from Perth one week prior. The pilots involved in the second and third incidents were both employed by a Perth-based operator, and therefore familiar with the airport. The operator reported that the third incident pilot was advised of the hazards around runway 06 during their line training.
Environmental conditions
During interview, all the pilots described the lighting conditions during the taxi to the runway as dark. Information from Geoscience Australia found that the first incident occurred around 1 hour prior to sunrise and the second and third incidents occurred around 1.5 hours prior to sunrise. All the incidents occurred before morning civil twilight, also known as first light.[9]
Perth Airport information
Runways
Perth Airport has 2 runways, 03/21 and 06/24 (Figure 5). Both runways are 45 m wide but runway 06/24 is shorter than 03/21. All pilots involved in the incidents reported that runway 03/21 was the runway they would use most frequently on departure.
Prior to the construction of taxiway V in 2012, there was a turning bay at the beginning of runway 06 to allow pilots to backtrack their aircraft and line-up to use runway 06. As a result, extra pavement remained on either side of the runway. The width of this extra pavement was 34 m from either side of the runway edge at the widest part, which is where each of the aircraft were aligned. The extra pavement tapers, where the widest part was closest to the runway end. At the time of each of the incidents, this extra pavement was not lit or marked, and there was no regulatory requirement to do so.
Taxiway V crossed the end of runway 06 and could be used to enter the runway from either the right (south) or left side (north). The flight crew from the first incident entered runway 06 from the right of taxiway V, and lined up on the left edge lights, while the pilots from the second and third incidents entered from the left and lined up on the right edge lights.
Figure 5: Perth Airport runways
Source: Google Earth, annotated by the ATSB
Lighting
The Civil Aviation Safety Regulations Part 139 Manual of Standards (MOS) for Aerodromes stated the requirements for runway and taxiway lights and markings for Australian airports.
Runway centreline lights
When installed, runway centreline lights were inset in the runway, and would be white and omnidirectional, apart from lights towards the end of the runway, which were required to be red.
Runway 03/21 was fitted with centreline lights (Figure 6). Runway 06/24 did not have centreline lights, and was not required to as per MOS 139.
Runway edge lights
The MOS stipulated that a permanent runway edge lighting system was required to be installed on runways intended for use at night. The edge lighting system should be comprised of 2 parallel rows of lights, equidistant from the runway centreline. The lights may be elevated (raised) or recessed (inset) and would be situated along the declared edge of the runway to delineate the area available to pilots for landing and take-off at night in reduced visibility. Consistent with the MOS requirements, the runway 06/24 edge lights were white (Figure 6 shows these lights for runway 03). The first 2 edge lights on runway 06 were inset into the runway, and the remainder of the lights were elevated (Figure 7).
Figure 6: Runway centreline lights and edge lights on runway 03
Source: Perth Airport, annotated by the ATSB
Figure 7: Runway 06 edge lighting (left side)
Source: Perth Airport, annotated by the ATSB
Taxiway centreline lights
The MOS also stated that, where taxiway centreline lights were used for both runway exit and runway entry purposes, the colour of the lights viewed by the pilot must be green for entering the runway and alternately green and yellow for exiting the runway. Taxiway V had lights from the centreline of the runway to the centre of the taxiway (Figure 8). These lights were alternating yellow and green unidirectional lights visible only when exiting the runway, known as lead-off lights. Lights visible when entering the runway were known as lead-on lights. Taxiway V did not have lead-on lights that joined from the taxiway to the runway centreline, but there were green bi-directional taxiway centreline lights spanning across the runway threshold in the middle of taxiway V (Figure 8 top and bottom).
Figure 8: Runway centreline lights (top), view from the runway centreline of runway 06 (middle) and view from taxiway V holding point, facing towards the opposite side of the taxiway (bottom)
Source: Google Earth (top image) and Perth Airport (middle and bottom images), all images annotated by the ATSB
Markings
MOS 139 stipulated the characteristics of aerodrome markings, including runway and taxiway markings. Runway markings were required to be white (on paved runways) and included runway designation, runway threshold, centreline markings, and edge markings (also known as side-stripe markings). Runway designation markings were the 2-digit runway number, determined from the approach direction, indicating the magnetic heading of the runway. Runway threshold markings identified the beginning of the runway that was available for landing and take-off using ‘piano key’ markings. They consist of a white line across the width of the runway and a series of white longitudinal stripes of uniform dimensions. Runway centreline markings were a line of uniformly spaced stripes and gaps that identify the centre of the runway and provide the pilot alignment guidance during take-off and landing. Runway edge markings were required to be continuous white lines on both sides of the runway. Taxiway markings were required to be yellow and provided on all sealed, concrete or asphalt taxiways for continuous guidance between the runway and the apron.[10]
Runway 06 had runway markings as per the MOS requirements. The runway edge markings were an unbroken white line and centreline markings were broken white lines. The markings were painted with non-reflective paint. There was no regulatory requirement to use reflective paint for runway markings. All taxiways including taxiway V had continuous yellow taxi centreline markings (Figure 9).
Figure 9: Runway markings on Runway 06 (as of March 2023)
Source: Perth Airport, annotated by the ATSB
Alternate runway markings to assist with visibility
There was no requirement for runway markings to be painted using reflective markings in Australia, but other countries use reflective paint to increase visibility and contrast in the dark. For example, the International Civil Aviation Organization recommended that aerodromes where operations take place at night, pavement markings should be made with reflective materials to enhance the visibility of markings. The United States Federal Aviation Administration (FAA) includes the use of retroreflective airport markings with glass beads in paint to improve conspicuity of markings at night, during low visibility conditions or when the pavement is wet. The Federal Aviation Administration also stated that runway shoulder stripes may be used to supplement runway edge stripes to identify pavement areas contiguous to the runway sides that are not intended for use by aircraft. Runway shoulder stripes were to be painted yellow.
Air traffic control information
Airservices Australia provided the ATSB with the air traffic control data for each of the incidents. The data included a recording of the tower controller’s screen from the Advanced Surface Movement Guidance and Control System, which showed the position of aircraft and ground vehicles. For all 3 of the incidents, the recording showed the respective incident aircraft lining-up and taking off from the edge of runway 06.
When asked whether a tower controller could detect misaligned take-offs, Airservices Australia advised that the scale setting and margin of error on the screens may make it difficult for controllers to detect a misaligned take-off. Further, the tower controller’s role was to look outside, and they may not be using the screen to check the runway alignment of an aircraft.
Operational information
Incident 1
Virgin Australia procedures
The Virgin Australia Policy and Procedures Manual stated that during take-off, flight crew must:
Use all available cues to ensure the aircraft is on the correct runway (including runway numbers, localizer, etc)
Ensure the take-off roll is only commenced when the aircraft is aligned.
The Flight Crew Operations Manual included as part of the ‘before take-off’ procedure a runway verification check, which included runway take-off position (Figure 10).
Figure 10: Excerpt of the ‘before take-off’ procedure
Source: Virgin Australia
Take-off decision speed
Based on the airspeed calculations for the flight on the take-off and landing card, the decision speed (V1) was 139 kt. The flight data showed that, when the aircraft was manoeuvred from the runway edge to the centreline, the groundspeed was 44 kt. As there were no significant winds in the area at the time affecting the aircraft’s speed, it was likely that a rejected take-off could have occurred.
Incidents 2 and 3
The pilots from the 10 August 2023 and 4 April 2024 incidents recalled that they would use the runway markings, including the centreline and runway threshold markings, to assist with alignment. They would also check that the runway edge lights were on either side of the aircraft when lining up on the runway.
Misaligned take-offs
Previous research
When pilots taxi and take-off during daylight conditions, they normally have a wide range of visual cues by which they can navigate and verify their location. At night, however, the amount of visual information available is markedly reduced. Pilots rely more on the taxiway and runway lighting patterns presented to them and what can be seen in the field of the aircraft’s taxi and landing lights.
In 2010, the ATSB published a research report titled Factors influencing misaligned take‑offs at night (AR-2009-033) which reviewed several Australian and international occurrences. The report identified several factors that increased the risk of a misaligned take-off. The most prevalent factors that contributed included environmental factors such as the physical layout of the runway and/or airport. Examples included a wide runway and/or extra pavement near the runway or confusing taxiway marking and/or lighting, such as recessed lighting at the runway’s edge and/or the absence of centreline lighting.
Areas of additional pavement around the taxiway entry and runway threshold area can provide erroneous visual cues at night and pilots can believe that they are in the centre of the runway when they are actually lined up on the edge. Recessed (inset) lighting, particularly at the taxiway entry to the runway, was often quoted as an influencing factor in reports relating to lining up incorrectly. Centreline lighting, when it was present, was always recessed to allow aircraft to safely travel over the centreline during take-off. However, runways will often have recessed lights at the runway edge where the taxiway meets the runway. Therefore, recessed runway edge lighting can act as confirmation that the flight crew have lined up on the centreline, when this is not actually the case. Similarly, the degradation of airport markings can provide erroneous cues to the pilots of the aircraft’s position on the runway.
The next most common factors were human factors such as flight crew distraction (divided attention). Divided attention results in a focus inside the flight deck at the expense of monitoring the external environment. An example was flight crew performing checklist items or setting power/checking instruments/readings. Completing checklists were a normal and necessary part of the departure, however, can be a distraction during a critical time, such as while lining up. Another factor was a lack of familiarity with the runway at night, as it can present an additional demand during taxi and line-up.
The last group of factors were operational factors, such as air traffic control clearances, which can provide a distraction to flight crew depending on the timing. They can also contribute to, precipitate, and/or exacerbate the presence or impact of other factors such as workload, distraction, or a lack of visual cues to assist the crew in lining up the aircraft on the runway centreline.
Previous safety recommendations
Previous investigations conducted by the United Kingdom Air Accident Investigation Branch (UK AAIB) and Dutch Safety Board, involving misaligned take-off incidents in 2015 and 2018 respectively, have included safety recommendations to the International Civil Aviation Organization (ICAO). These recommendations proposed that ICAO should develop runway design standards that would prevent pilots misidentifying runway edge lighting as centreline lighting. ICAO reviewed these safety recommendations and determined that guidance included in the Procedures for Air Navigation Services (PANS) – Aerodromes (Doc 9981) provided strategies to address misaligned take-offs. The guidance included considerations for aerodrome operators, such as conducting safety assessments as part of the risk management process. An example of an item to be considered in this process was aerodrome/runway layout.
In 2021, the Global Action Plan for the Prevention of Runway Excursions was published and included addressing misaligned take-off incidents. Specifically, the report stated there should be measures for preventing visual confusion during line-up between runway edge and centreline lights leading to misalignment with the runway centreline. The measures should also take into account the effects of low visibility and runway contamination and the effect of using various light colours and patterns to differentiate the runway centreline and edge lighting systems.
Related occurrences
A review of the ATSB occurrence database found 3 reported incidents of misaligned take-offs in the 5 years prior to April 2024. These incidents, along with 2 similar international incidents are as follows.
On 20 April 2021, at 1854 local time, the pilot of a Fairchild SA227 aircraft taxied at Townsville Airport for a freight charter flight to Brisbane, Queensland. While lining up for take-off on runway 01, air traffic control advised that the aerodrome QNH[11] had changed. During this time, the pilot became aware that the aircraft had deviated from the lead-on line and started correcting the turn to realign with the centreline. During the take-off roll, the aircraft struck a runway edge light resulting in minor damage to the propeller.
A number of factors that contributed to the misaligned take-off included the wider paved section at the end of the runway, no centreline lights on the runway, recessed edge lighting, and taxiway lead-on lights not visible when entering the runway. It was also found that there was reduced visibility prior to departure due to the rain and time of day.
On 21 July 2023, at 0109 local time, the pilot of a Piper PA-31 aircraft taxied at Essendon Fields Airport, Victoria for a freight charter flight to Bankstown, New South Wales. After reading back their clearance from air traffic control and accepting the departure from runway 26, the aircraft was taxied and prepared for take-off. The pilot was completing checklists, which required attention to be focused within the aircraft. After commencing the take-off run, the pilot heard multiple loud noises, rejected the take-off and exited the runway. Inspection of the aircraft upon return to the apron identified a damaged main landing gear tyre and brake calliper. An inspection of the runway found damage to multiple runway lights and foreign object debris scattered across the runway.
On 13 May 2024, at 0537 local time, the pilot of an Aero Commander 500-S aircraft taxied for departure at Brisbane Airport on a regular scheduled freight flight. The aircraft was cleared for a departure from runway 01 at the intersection of taxiway A7, the pilot taxied to this holding point. While turning onto the runway, the pilot inadvertently lined up along the left side runway edge lighting instead of the runway centreline. During the take‑off roll, the pilot recognised the aircraft was left of the centreline and took corrective action to reposition the aircraft on the runway. The underside of the aircraft had minor damage and several runway lights were also damaged.
The brief highlighted the complexity of the intersection with multiple lead-off lines into the runway as well the runway touchdown zone markings near the runway centreline markings that were both broken white lines.
German Federal Bureau of Aircraft Accident Investigation BFU20-0251-EX
On 27 April 2020, at 0353 local time, the flight crew of a ATR72-212 aircraft prepared for take-off on a freight flight from Cologne Airport, Germany, to Sofa Airport, Bulgaria, in the dark. After receiving their taxi clearance, the flight crew taxied the aircraft to the centreline of runway 24 towards the turn pad (paved area next to the runway for turning) for runway 06 (the reciprocal runway). The flight crew completed the before take-off checklist during taxi. At this time, the flight crew heard a sound in the cockpit and determined it was from the captain’s bag falling from the chair. When the turn pad was reached the aircraft initially followed the yellow taxiway markings to turn 180°. The captain completed the turn and aligned the aircraft with the row of lights ahead, believing they were the centreline lights. During the take-off roll, the flight crew felt and heard an impact to the aircraft, so the captain aborted the take-off. The aircraft had minor damage to the nose landing gear and propeller blades.
Factors identified that contributed to the misaligned take-off related to the runway environment and distraction. The runway edge marking on the turn pad was a broken white line, which was similar to the centreline markings. Due to the viewing angle from the cockpit to the runway edge and centreline lighting they were difficult to differentiate, especially in the dark without any other visual refences. The width of the turn pad including the runway was also identified as a factor. Another factor was flight crew distraction during the turn due to determining the sound in the cockpit. The report had a safety recommendation (07/2020) to ICAO:
The International Civil Aviation Organization (ICAO) should modify the standard recommendations regarding runway edge lighting in Annex 14 Volume 1 Aerodrome Design and Operations to ensure clear distinction of other airport lightings (sic).
Transportation Safety Board of Canada investigation A23F0062
On 16 February 2023, at 1817 local time, the flight crew of a Boeing 737 aircraft taxied to runway 01R in Nevada, United States, to Edmonton, Canada, on a scheduled passenger flight. The flight crew taxied the aircraft along the taxiway centreline until reaching the right runway edge marking, turned to the right and entered and lined up with what was believed to be the runway centreline. The aircraft took off while aligned with the right edge of runway 01R, and its nosewheel contacted 8 runway edge lights. During the take‑off roll, both the flight crew heard sounds and felt vibrations but believed it was the runway centreline lights. The flight crew were unaware of the misaligned take-off and the flight was continued. The aircraft had minor damage to the right tyre on the nose landing gear and there was damage to several runway lights.
The investigation identified several factors that contributed to the misaligned take-off. The factors included the high workload between the flight crew at the time of departure where the FO was focused on a task within the cockpit and the captain’s perceived time pressure to depart. Other factors included the visual cues in the runway environment. The taxiway centreline lighting on the taxiway used for departure terminated at the runway edge markings and the runway did not have centreline lighting.
Safety analysis
Runway environment resulting in the misaligned take-off
On runway 06, there was extra pavement on either side of the runway where each aircraft lined up for take-off. As there were no markings or lighting to delineate this area, there were no visual cues to assist the pilots to identify the extra pavement was adjacent to the runway. Consequently, this area likely appeared to be an extension of the usable runway. This was consistent with the pilot’s observation in incident 2 where they reported seeing ‘plenty’ of runway to their right when lined up on the right runway edge.
Although the runway had all the required markings in accordance with regulations, they were reported by 2 of the pilots as being difficult to see at night and were ‘scuffed’, thereby reducing the contrast and visibility of the markings. It was also noted that, while not required, reflective paint was not used for the markings to improve conspicuity at night.
While there were taxiway centreline markings, there were no lead-on lights from the taxiway to the runway centreline. Although there were lead-off lights, these were unidirectional and designed to only be visible when exiting the runway. Therefore, at night, the pilots had limited cues to assist them while navigating from the taxiway to ensure they would turn the aircraft into the centre of the runway.
Runway 06 did not have centreline lighting. However, the first 2 edge lights on either side were white and inset within the runway, which were the same characteristics for centreline lighting. Given that all the pilots indicated they would use runway 03/21 more frequently for take‑off, which was fitted with centreline lights, this potentially influenced them misidentifying the edge lights as centreline lights.
The pilots of the 2 incidents operating the Cessna 441 also commented that although the aircraft lighting was switched on, the environment appeared dark. One of these pilots also reported that there was limited ambient lighting at the intersection of taxiway V to runway 06. The combination of the reduced visual cues and runway features that can be misidentified may have also given the impression that the aircraft were aligned with the runway centreline and increased the risk of a misaligned take-off. These characteristics were evident in many previous similar investigations.
Consistent with the ATSB’s research, the extra pavement area, the absence of lead-on lights and runway centreline lights, and some degraded markings, were all factors that influence misaligned take-offs at night, where visual information may be markedly reduced. A combination of these factors in each incident supported the pilots’ belief that the aircraft were correctly aligned with the centreline when they were positioned on the runway edge lighting. Confirmation bias is the tendency for people to seek information and cues that confirm the tentatively held hypothesis or belief (Wickens et al 2022). As they believed they were correctly aligned with the runway centreline, the pilots in each occurrence commenced the take-off roll.
Flight crew focus of attention
In incident 1, the flight crew divided their attention between pre-take off tasks being completed in the flight deck and monitoring the environment. Additionally, the flight crew also received their take-off clearance during the turn onto the runway, requiring the FO to communicate with air traffic control. While these are normal and a required part of the departure, they can divert the flight crew’s attention away from the external environment at a critical time, such as while lining up. Barshi and others (2009) state that during busy periods, it is easy for attention to be absorbed in one task, which can divert attention from other important tasks, such as monitoring.
Pilots’ response to the misaligned take-off
The pilots’ responses to each misaligned take-off incident were different. During the take‑off roll, the flight crew in the June 2023 incident identified that they had lined up on the runway 06 edge lighting and manoeuvred the aircraft toward the centreline and continued the take-off. However, believing they had not struck the runway lights, the misalignment of the take-off was not reported to the operator or to airport personnel until the flight had arrived in Sydney, around 4 hours later. Although the subsequent aircraft and runway inspections did not identify any damage, there was the risk that unrecognised debris could have affected the safety of other aircraft using the same runway or the flight continuing with unknown damage.
The pilot in the August 2023 incident detected an impact during take-off, though did not initially notice the aircraft was aligned with the runway edge lighting. As they had detected a problem, the pilot returned to the airport to ensure there was no damage to the aircraft and provided the opportunity for a runway inspection to occur to check for damage. The pilot’s decision was important as damage to the aircraft (which was carrying passengers) and debris on the runway can affect flight safety.
The pilot in the April 2024 occurrence did not identify they had lined up the aircraft on the runway edge lighting and subsequently completed multiple flights. As a result of the misaligned take-off, the aircraft had sustained damage to the right propeller and several runway lights were damaged, which was not detected until later that day. Damage from a foreign body impact to a propeller blade could lead to gouges, dents and deformation, or cracks and blade failure if left undetected (Federal Aviation Administration 2005), although in this instance there was no reported effect on flight from the sustained damage.
Overall, misaligned take-offs can increase the risk of damage to aircraft and lighting given that raised runway lighting, unlike recessed runway lighting, is more likely to sustain an impact. Given the risk, it is important to promptly communicate the incident, for example to air traffic control or airport personnel, to provide the opportunity for inspections to be conducted. The outcome of these inspections allows pilots to make more informed decisions on whether to continue the flight, return or divert to a closer location.
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 3 misaligned take-off occurrences on runway 06 at Perth Airport, Western Australia.
Contributing factors
On runway 06 at Perth Airport, features of the runway environment included extra pavement, degraded markings, and reduced lighting. As a result, the pilots in 3 separate occurrences misidentified this runway's edge lighting for centreline lighting and commenced take-off from this position.
During the turn onto the runway in incident 1, the flight crew were focussed on completing pre-take off tasks within the flight deck, and communicating with the air traffic controller about their take-off clearance. These actions diverted their attention away from monitoring their position on the runway.
Other factors that increased risk
After the misaligned take-offs, the 3 pilots responded differently. This increased the risk of damage, to aircraft or runway lighting, remaining undetected.
Safety actions
Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future. The ATSB has so far been advised of the following proactive safety action in response to this occurrence.
Safety action by Perth Airport Pty Ltd
After the first 2 misaligned take-off incidents, Perth Airport submitted a notice to Airservices Australia requesting an update to the Aeronautical Information Publication about the misaligned take-off risk on runway 06. Subsequently, this update was included in an Aeronautical Information Publication supplement H78/23 effective November 2023 containing an update to the ground and movement charts for Perth Airport. The new aerodrome chart highlighted there was a ‘misaligned take-off hot spot’[12] at the intersection of taxiway V and runway 06. The supplement detailed that runway 06 had wider shoulders due to previously being used as a turn pad, had no centreline lights, and that, when lining-up on the runway from taxiway V, pilots should ensure that the aircraft was aligned with the runway centreline. In March 2024, Airservices Australia updated the En Route Supplement Australia to reflect this change.
Perth Airport conducted airport works in late March to early April 2024 to repaint all markings on the runway and taxiway. As part of this work, they also painted chevron markings on the extra pavement next to runway 06 to prevent future misalignment.
Safety action by Western Sky Aviation
As a result of the incident on 10 August 2024, the operator issued a notice to aircrew to highlight the importance of vigilance by confirming the nominated runway position. For runways with an instrument landing system (ILS), the operator encouraged pilots to line up and tune the ILS and dial up the course to check the course deviation indicator is centred. For runways with no ILS (such as runway 06), the operator encouraged pilots to crosscheck the runway heading with the GPS position of the aircraft overlaid on the aerodrome map display in the OzRunways software on tablets in the aircraft.
After the April 2024 incident, a second notice to aircrew was distributed, emphasising the importance of situational awareness with runway identification when preparing for take‑off. The notice specified that pilots must confirm they are on the runway centreline and ensure the runway number is identified, either through the runway markings or association with the heading displayed by an aircraft instrument. For night take-offs specifically, pilots were instructed to self-brief the expected runway to familiarise with the specific characteristics of the runway such as whether it has centreline lighting or not, and to ensure that they have both the sides of the runway lighting visual before commencing the take-off roll.
Safety action by Virgin Australia Airlines
Virgin Australia Airlines added caution notes to its Perth Airport supplementary port information about centreline misidentification on runway 06 due to the environment, such as no centreline lighting during night or in poor visibility conditions. They also revised the before take-off procedure to reduce flight crew workload during line‑up by reallocating items (setting the weather radar) to earlier in the taxi. Finally, case studies involving this event were incorporated into non-technical skills training.
Sources and submissions
Sources of information
The sources of information during the investigation included:
pilots from the 3 incidents
Virgin Australia Airlines
Western Sky Aviation
Perth Airport
Airservices Australia.
References
Airservices Australia. (2023). A pilot’s guide to runway safety, Airservices Australia.
Australian Transport Safety Bureau. (2010). Factors influencing misaligned take-off occurrences at night, Australian Transport Safety Bureau, Australian Government.
Barshi, I., Loukopoulos, L.D. and Dismukes, R.K. (2009). The multitasking myth: Handling complexity in real-world operations. Ashgate Publishing.
Civil Aviation Safety Authority. (2019). Part 139 Manual of Standards for Aerodromes, Civil Aviation Safety Authority, Australian Government.
Federal Aviation Administration. (2005). Advisory Circular AC20-37E Aircraft Propeller Maintenance, US Department of Transportation, United States.
Wickens, C.D., Helton, W.S., Hollands, J.G., and Banbury, S. (2022). Engineering psychology and human performance, 5th edn, Routledge, doi: 10.4324/9781003177616.
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:
pilots from the 3 incidents
Virgin Australia Airlines
Western Sky Aviation
Perth Airport
Airservices Australia
Civil Aviation Safety Authority.
Submissions were received from:
a pilot from one of the incidents
Virgin Australia Airlines
Western Sky Aviation
Perth Airport
Civil Aviation Safety Authority.
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.
About ATSB reports
ATSB investigation reports are organised with regard to international standards or instruments, as applicable, and with ATSB procedures and guidelines.
Reports 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.
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
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]Runway number: the number represents the magnetic heading of the runway (for example, runway 06 is orientated 60º magnetic). The runway identification may include L, R or C as required for left, right or centre. Runways 06/24 were reciprocal runways.
[2]Holding point: designated point for holding on airfield, especially before entering active runway.
[3]Lead-on lights: green unidirectional taxiway centreline lighting that extends into the runway.
[4]Pilot flying (PF) and pilot monitoring (PM): procedurally assigned roles with specifically assigned duties at specific stages of a flight. The PF does most of the flying, except in defined circumstances, such as planning for descent, approach and landing. The PM carries out support duties and monitors the PF’s actions and the aircraft’s flight path. On the Boeing 737, the captain taxis the aircraft as the steering is on the left side.
[5]Take-off decision speed (V1): the critical engine failure speed or decision speed required for take-off. Engine failure below V1 should result in a rejected take off; above this speed the take-off should be continued.
[6]The pilot in incident 3 was a different pilot to incident 2.
[7]Notice to Airmen (NOTAM): a notice distributed by means of telecommunication containing information concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential to personnel concerned with flight operations.
[8]Stop bars are a series of unidirectional red lights embedded in the pavement, at right angles to the taxiway centreline, at the associated runway holding point. They are intended to provide additional protection of runway/taxiway intersections to reduce runway incursions.
[9]First light: when the centre of the sun is at an angle of 6° below the horizon before sunrise. At this time the horizon is clearly defined but the brightest stars are still visible under clear atmospheric conditions.
[10]Apron: large paved area of airfield for such purposes as: loading and unloading of aircraft; aircraft turnaround operations; aircraft modification, maintenance or repair; any other approved purpose other than flight operations.
[11]QNH: the altimeter barometric pressure subscale setting used to indicate the height above mean sea level.
[12]Hot spot: a location on an aerodrome movement area with a history of potential risk of collision or runway incursion, and where heightened attention by pilots / drivers is necessary.
Occurrence summary
Investigation number
AO-2023-027
Occurrence date
12/06/2023
Location
Perth Airport
State
Western Australia
Report release date
20/11/2025
Report status
Final
Investigation level
Short
Investigation type
Occurrence Investigation
Investigation status
Completed
Mode of transport
Aviation
Aviation occurrence category
Collision with terrain, Runway excursion
Occurrence class
Incident
Highest injury level
None
Aircraft details
Manufacturer
The Boeing Company
Model
737-8SA
Registration
VH-IWQ
Serial number
44225
Aircraft operator
Virgin Australia Airlines Pty Ltd
Sector
Jet
Operation type
Part 121 Air transport operations - larger aeroplanes
Departure point
Perth Airport, Western Australia
Destination
Sydney Airport, New South Wales
Aircraft details
Manufacturer
Cessna Aircraft Company
Model
441
Registration
VH-NSA
Serial number
441-0087
Aircraft operator
Western Sky Australia Pty Ltd
Sector
Turboprop
Operation type
Part 135 Air transport operations - smaller aeroplanes
The Australian Transport Safety Bureau (ATSB) has commenced a transport safety investigation into an accident involving a Cessna 210 single-engine charter aircraft with a pilot and five passengers on board at Groote Eylandt, Northern Territory, on Friday afternoon.
As reported to the ATSB, during take-off the aircraft experienced engine issues and the pilot attempted to return to Groot Eylandt. During approach, the aircraft collided with terrain and came to a rest inverted.
The ATSB is preparing to deploy a team of transport safety investigators with experience in aircraft operations and maintenance, to conduct an examination of the aircraft wreckage and accident site.
Investigators will also obtain and review any recorded data, weather information, pilot, passenger and witness reports, and aircraft operator procedures and maintenance records.
Any relevant components will be recovered to be transported to the ATSB’s technical facilities in Canberra for further examination.
The ATSB will publish a final report, detailing contributing factors and any identified safety issues, at the conclusion of the investigation.
However, should any critical safety issues be identified at any stage during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate safety action can be taken.
The ATSB is investigating the collision between a semitrailer truck and a train near Katherine, Northern Territory, on 14 June 2023.
At 1055 local time, the truck, travelling in an easterly direction, entered the Florina Road level crossing into the path of Aurizon train 2AD1 travelling from Adelaide, South Australia to Darwin, Northern Territory. The collision between the lead locomotive and trailer of the truck resulted in the derailment of two locomotives, crew car and several trailing wagons from the train. The locomotives, several trailing wagons and the trailer from the truck were destroyed. The crew of 2AD1 sustained minor injuries and were transported to hospital. The truck driver was uninjured.
The final report has been drafted and is undergoing internal review to ensure the report adequately and accurately reflects the evidence collected, analysis, and agreed findings.
The final report will be published at the conclusion of the investigation. Should any critical safety issues be identified at any stage during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate safety action can be taken.