Loss of control

Loss of control during marine pilot transfer operations involving Agusta A109E, VH-XUM and bulk carrier Star Coral, about 200 km north-east of Mackay, Queensland, on 25 February 2025

Final report

Report release date: 29/07/2025

Investigation summary

What happened

On the morning of 25 February 2025, an Agusta A109E helicopter was conducting a marine pilot transfer operation on the inbound bulk carrier Star Coral at Blossom Bank pilot boarding ground, about 200 km north‑east of Mackay, Queensland.

At 0901 local time, during take‑off from the ship with 2 pilots on board, the helicopter developed severe vibrations. The pilots discontinued the take-off but their attempts to recover control of the helicopter were unsuccessful. The helicopter came to rest in an upright position on the helideck, having spun more than 90° counterclockwise from its initial heading, and sustaining substantial damage. The pilots and ship’s crew were unharmed.

What the ATSB found

The investigation did not identify any airworthiness issues with the helicopter and it was considered that the loss of control was not attributable to a mechanical issue. 

The ATSB found that the vibration was likely the result of the helicopter entering ground resonance, a phenomenon that dissipates when airborne, while it was in the process of departing from the ship. The discontinuation of the take‑off, after the onset of the vibration, probably resulted in the loss of control and subsequent damage to the helicopter.

What has been done as a result

The operator has added new guidelines on ground resonance to its procedures. The guidelines include procedures for recognising and recovering from ground resonance and feature case studies and video resources for training purposes. 

The operator has also developed an updated procedure for training and checking flight briefings that will include confirming the roles of each pilot, procedures for transferring aircraft control between pilots, and actions to be followed in the event of an actual emergency.

Safety message

The occurrence highlights the dangers of ground resonance, a potentially catastrophic phenomenon that can occur in helicopters with fully articulated rotor systems. Typically, the onset of ground resonance is sudden and if the pilot does not take immediate corrective action, a loss of control can rapidly occur. 

The occurrence also highlights the importance of proper coordination between a helicopter’s pilots when responding to abnormal or emergency situations. This is particularly pertinent for situations where the pilot flying is not the pilot in command. Ideally, the pilots’ individual roles and responsibilities for emergency response and flying duties should be well established prior to the flight. 

 

The investigation

The ATSB scopes its investigations 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, the ATSB conducted a limited-scope investigation 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

At about 0730 local time on 25 February 2025, the 229 m bulk carrier Star Coral arrived at the Blossom Bank pilot boarding ground, about 200 km north‑east of Mackay, Queensland (Figure 1). The ship waited to embark a coastal marine pilot by helicopter for its inbound transit of the Great Barrier Reef via Hydrographers Passage.[1] It was in ballast and bound for Hay Point to load coal. 

Figure 1: Blossom Bank pilot boarding ground and Hydrographers Passage

A chart showing the location of  Blossom Bank pilot boarding ground, Hydrographers Passage, Mackay and Hay Point

Source: Australian Hydrographic Office, annotated by the ATSB

Meanwhile, at Mackay Airport, a twin‑engine Agusta A109E helicopter, operated by Flyon Helicopters and registered VH‑XUM (XUM), with 2 pilots on board, embarked the marine pilot scheduled to conduct the ship’s pilotage. The marine pilot transfer (MPT) flight to Star Coral was the first scheduled for the helicopter and its pilots that day. These flights were normally conducted as a single‑pilot operation. However, on this occasion, the pilot flying, a pilot recently engaged by the operator under its ‘in‑command‑under supervision’ (ICUS)[2] program, was under the supervision of a company check pilot (pilot supervising). 

The pilots’ plan was to transfer Star Coral’s marine pilot and then proceed to a nearby outbound ship to collect its marine pilot for return to Mackay.

At 0759, the helicopter departed Mackay Airport under the control of the pilot flying. En route, the pilots established communication with Star Coral’s master via VHF[3] radio. The master advised that the ship was rolling about 3° on its inbound heading due to a 2 m south‑easterly swell. Subsequently, the pilots requested the master to reposition the ship on a heading[4] of 270° to reduce rolling. At 0853, the pilot flying landed the helicopter on the ship’s helideck, situated on the number 5 cargo hold hatch cover (Figure 2). The marine pilot exited the helicopter and proceeded to the ship’s bridge. 

Figure 2: Landing position of VH-XUM aboard Star Coral

An image showing the helideck location on Star Coral with a separate diagram showing the heading of the helicopter while on the ship, relative to the ship and wind.

This figure is a representation of the helicopter’s orientation relative to the wind during the take‑off. Source: Flyon Helicopters and Star Coral, annotated by the ATSB

Meanwhile, the helicopter remained on the helideck at flight idle[5] while its pilots radioed the outbound ship’s pilot to coordinate the transfer. After some discussion, the pilots elected to keep the helicopter on the deck of Star Coral until the outbound ship had departed the compulsory pilotage area.

After about 5 minutes, as the 2 ships were about to pass each other, the helicopter pilots began conducting their pre‑take‑off checks. The pilots observed a 20 to 28 knot headwind (relative to the helicopter) and noted that the ship was rolling less than 2°. The pilot flying conducted a brief for a performance category 1[6] take‑off, which involved establishing the helicopter in a hover 35 ft above deck height before departing. Both pilots later recalled that everything seemed normal as the take‑off checks were completed. 

At about 0900, the pilot flying raised the collective[7] and observed the engine torques increasing through 50%. The pilot flying recalled the aircraft became light on its oleos as though it was ‘right at the point of lifting off’. Meanwhile, the pilot supervising was observing the outbound ship passingA few seconds later, both pilots felt a sudden and substantial vibration. 

The pilot supervising immediately looked down at the controls and recalled that the pilot flying was holding the cyclic[8] in an abnormally aft position. Concerned that the main rotor might have struck the tail boom, the pilot supervising decided to assume control of the helicopter and took hold of the cyclic and collective unannounced. Meanwhile, the pilot flying was still attempting to lift off, unaware of the pilot supervising’s decision to take control. The pilot supervising recalled that the pilot flying had centred the cyclic and ‘must have’ lowered the collective by the time the pilot supervising took hold of the controls. In contrast, the pilot flying stated that the pilot supervising rapidly lowered the collective after the vibration started, causing the aircraft to descend from being light on its oleos and bounce heavily on the helideck.

Moments later, the cyclic became uncontrollable as the vibrations suddenly worsened into a violent, vertical oscillation of the airframe. The pilot supervising tried to stabilise the helicopter but was unable to control the cyclic movement. Subsequently, the pilot supervising elected to shut down the engines. 

The pilot supervising initially struggled to reach the engine mode switches (located on the centre console) due to the severe vibrations but subsequently managed to shut down engine number 2. The vibrations slightly eased and moments later, they were able to also shut down engine number 1. The vibration dissipated and the helicopter came to rest in an upright position on the helideck, having spun more than 90° counterclockwise from its initial heading. The sequence, from the attempted take‑off to shut‑down occurred within a period of about one minute.

Soon after, the pilots exited the wreckage and inspected the damage. The tail rotor was separated from the helicopter and had come to rest on the main deck between cargo hatches 4 and 5. Items of debris, including main rotor fragments, laid scattered on the deck along with some hydraulic fluid pooled beneath the substantially damaged fuselage (Figure 3).  

Figure 3: Helicopter wreckage 

A photo of the helicopter wreckage on the deck of the bulk carrier, Star Coral

Source: Star Coral

Apart from a thumb sprain to the pilot supervising and some bruising to both pilots’ upper leg areas, where they had been struck by the cyclic, neither were significantly injured and no‑one on board Star Coral was injured.

Context

Helicopter information

The helicopter was an Agusta A109 E variant, manufactured in 2006 and issued serial number 11684. It was registered in Australia in 2006 and began services under the operator’s Air Operator’s Certificate (AOC) in 2023. 

The Agusta A109E is a multipurpose helicopter equipped with 2 Pratt & Whitney PW206‑C turbine engines. It has a fully articulated 4‑blade main rotor system, a 2‑blade tail rotor and retractable tricycle landing gear. Able to carry up to 7 occupants, it has a maximum allowable take‑off weight of 2,850 kg. 

The helicopter was able to perform flight performance class 1 operations by adherence to Category A procedures[9]. While the helicopter was normally operated from the right crew seat, it was fitted with dual controls. A left seat‑approved pilot in command (PIC) was permitted to occupy either seat during training flights. Each set of controls could not be operated independent of the other. 

The helicopter’s wreckage was recovered from the ship 2 days after the incident and transported to a secure hangar at Mackay Airport. Prior to its removal, photographs of the wreckage and the accident area were taken. There were no indications that the main rotor or tail rotor had struck any part of the ship during the accident. 

Based on its inspections, the operator advised that no engine faults or exceedance alarms had been recorded by the helicopter’s electronic engine management systems. Additionally, no faults or defects had been reported by any of XUM’s pilots or maintainers leading up to the occurrence flight. 

Post-accident activities

There was no recorded flight data available to determine the flight control inputs and their effect on the motion of the helicopter during the occurrence.[10] The pilots’ accounts, a witness statement from the master of Star Coral and photographs of the wreckage were the main sources of evidence. 

The ATSB also sought the manufacturer’s input for this occurrence. The manufacturer advised that its preliminary assessment of the available evidence suggested that the helicopter damage appeared consistent with a ground resonance phenomenon (see the section titled Ground resonance).

The licenced maintenance organisation for XUM carried out an examination of the wreckage at the Mackay hangar. On advice from the manufacturer, the examination included inspection of specific components commonly associated with ground resonance. These included main rotor dampers, landing gear struts and tyres. The operator advised the ATSB that the inspection did not identify any airworthiness issues that may have contributed to the occurrence. The operator did not provide the inspection report or findings to the manufacturer for its assessment.

Pilot flying 

The pilot flying obtained a New Zealand commercial helicopter licence (CPL) in 2011 and started flying commercially in 2014. They converted their CPL over to an Australian CPL in 2016 and held a grade 2 flight instructor rating and a class 1 aviation medical certificate. They had experience flying both single and twin-engine helicopters in various operations. Prior to joining the operator’s in‑command‑under‑supervision (ICUS) program in September 2024, they had no previous experience on the A109E, or with marine pilot transfers (MPT). 

Under the ICUS program, the pilot was required to accrue 200 hours on the A109E before they could be assessed to fly the helicopter unsupervised on daytime VFR[11] MPT operations. At the time of the occurrence, the pilot had completed the operator’s training requirements and accrued around 50 hours flight time on the A109E. They had also been cleared to conduct unsupervised MPT operations on single‑engine Eurocopter AS350 helicopters.

Pilot supervising

The pilot supervising was the operator’s head of flying operations and held an air transport pilot (helicopter) licence, issued in 2014, and a class 1 aviation medical certificate. They were approved under the operator’s training and checking system to conduct check and supervision flights on the A109E.

The pilot supervising had been flying helicopters for 26 years in various operations and had accumulated over 10,000 hours flying time, including 3,800 hours in the A109E. They first started MPT operations in 2007 and commenced working with the operator in December 2016.   

Star Coral

Star Coral was built in 2009 by Jansu Newyangzi Shipbuilding, China, registered in The Bahamas and classed with Bureau Veritas. The ship was owned by Panormos Shipping, The Bahamas, and managed and operated by Charterwell Maritime, Greece. 

At the time of the occurrence, the 229 m ship had a mean draught of 6.51 m and the helideck height was about 18 m above the waterline.   

In a written witness statement, the master reported that:

• shortly after the helicopter started to take off, it began to pound on the helideck before it spun and the tail rotor separated

• during the sequence, the helicopter became airborne for no more than 2 seconds.

Ground resonance

Ground resonance can be defined as a vibration of large amplitude resulting from a forced or self‑induced vibration of a helicopter in contact with the ground.[12] The phenomenon is normally associated with helicopters equipped with fully articulated main rotor systems consisting of 3 or more rotor blades. It is more common on helicopters with sprung landing gear than those with skids. Typically, ground resonance occurs during landing, take‑off and ground manoeuvres.[13]

In fully articulated rotor systems, drag hinges allow each blade to advance or lag in the plane of rotation to compensate for the stresses caused by the acceleration and deceleration of the rotor hub. Such rotor systems are typically fitted with lead‑lag dampers to limit the extent of this movement and help prevent excessive vibrations. However, if for any reason one or more of the blades assumes a dragged position different to the others, the blades will move out of phase and the rotor will become imbalanced, transmitting an oscillation throughout the entire airframe.[14]

The risk of ground resonance arises when the unbalanced forces in the rotor system cause the fuselage to oscillate on its landing gear at or near its natural frequency. Ground resonance will occur if the helicopter’s damping systems are unable to compensate for the oscillation.[15] Unless corrective action is taken, the amplitude of the oscillation will increase until the helicopter becomes uncontrollable.[16] Ground resonance can also be induced when the helicopter is in light contact with the ground, if the landing gear oscillation frequency is in sympathy with the rotor head vibration.[17]

Ground resonance is commonly precipitated by the helicopter making hard or asymmetric contact with the ground, landing on a slope or sudden control movements by the pilot.[18] It can also result from other factors such as improper blade balancing and tracking, or damage to any of the blades.[19] Hard contact with the ground by some part of the landing gear when the main rotor is in an unbalanced state can further aggravate the condition.[20]

Additionally, improper maintenance of the helicopter’s main rotor and fuselage damping systems, or incorrect tyre pressures, can induce or worsen ground resonance.[21]

Flight control inputs that may induce ground resonance typically involve sudden control movements or a mishandling of the cyclic that causes the fuselage to bounce.[22]

The helicopter manufacturer advised that the application of certain cyclic commands, such as extreme aft cyclic input, could theoretically reduce the main rotor damper effectiveness in respect to the damping action on the blades’ regressive lead‑lag dynamic.

Recovery technique

The onset of ground resonance can be recognised by a rocking motion or oscillation of the fuselage while on the ground.[23] The United States Federal Aviation Administration (FAA) Helicopter Handbook[24] documented 2 widely accepted recovery techniques: 

• if the condition arises when there is insufficient rotor speed for take‑off, the only option is to lower the collective to reduce the pitch of the blades. The rotor rpm[25] should also be reduced as soon as possible.[26]

• If the rotor speed is in the normal operating range for flight, the Helicopter Handbook recommends lifting the helicopter off the ground to allow the rotor blades to rephase themselves automatically. 

Additionally, the FAA cautioned that:

If a pilot lifts off and allows the helicopter to firmly re‑contact the surface before the blades are realigned, a second shock could move the blades again and aggravate the already unbalanced condition. This could lead to a violent, uncontrollable oscillation.  

In practice, a pilot experiencing ground resonance typically has seconds to identify the condition and take corrective action. 

Similar occurrences

The ATSB reviewed several investigation reports relating to previous A109E accidents attributed to ground resonance. The incidents reviewed occurred outside of Australia between 2006 and 2025 and the contributing factors were found to be operational. Technical factors which may have caused or exacerbated ground resonance were not identified. 

Details of the previous incidents bear similarity to the occurrence involving XUM, particularly in respect to subsequent damage to the helicopter (Figure 4). 

Figure 4: Previous occurrences of ground resonance involving the Agusta A109E

Four separate images showing damaged Agusta A109 helicopters after experiencing ground resonance in previous accidents.

Source: Leonardo Helicopters

Flight manual procedures

The A109E rotorcraft flight manual (RFM) listed fault conditions and corrective actions for emergencies and malfunctions that might occur during take‑off.

The RFM included the caution below for ground resonance within the normal flight procedure for take‑off. This was not part of the emergency and malfunction procedures.

The normal take-off procedure from the helicopter's flight manual

The RFM procedure for ground resonance was consistent with recovery techniques published by the FAA. The RFM reference to the helicopter being ‘free of ground resonance’ was intended to indicate  that, like all helicopters, the A109E was designed and certified to applicable standards so that the rotor and fuselage systems do not vibrate at the same frequency under normal conditions.   

Operator procedures

As an AOC holder, the operator maintained a CASA‑approved[27] operations manual/exposition[28] to promulgate general policy and standardised procedures for MPTs on the A109E. The version of the operations manual current at the time of the occurrence was issued by the operator in November 2023.

Ground resonance

The operator’s normal procedures and emergency checklists for the A109E were derived from the RFM and did not contain any procedures related to ground resonance. 

Crew coordination in response to abnormal situations

While MPT flights were predominantly conducted by a single pilot, the helicopter was certified for operations with either a single pilot or 2 pilots. In either case, the normal procedure and emergency checklists remained the same, except that 2‑pilot checklist procedures were to be based on challenge and response. 

Normal handover and takeover procedures provided that:

In the case where the pilot flying (PF) is not the PIC and the PIC determines that the PF is not maintaining adequate control of the aircraft, the PIC may elect to take control, in which case they will signal their intention by saying ‘I have control’ upon which the PF will immediately relinquish control and the roles will reverse.

In abnormal or emergency situations, the PIC was responsible for ensuring the aircraft was flown and kept under control. The operations manual emphasised the importance of cockpit resource management (CRM) standards throughout the situation, in accordance with the below procedure:

The emergency and abnormal situation procedure from the operations manual

Note: In the above procedures PM stands for ‘pilot monitoring’, NR refers to main rotor speed and IAS means indicated airspeed. 

In the context of rapidly escalating emergencies such as ground resonance, pilots have limited time to perform the procedure. 

Pilot in command responsibility during training flights

As the holder of a certificate that authorised air transport and aerial work operations, the operator was required to have in place a training and checking system (TACS). A training and checking manual (TACM) sets out policies and procedures for conducting training flights. It provided that a check pilot supervising ICUS training was to be the PIC. Check pilots were to ensure that pilots involved in training exercises were made aware of who was acting as the PIC through proper handover of control procedures. 

While an ICUS pilot might be considered the PIC for flight‑time logging purposes, the pilot supervising was deemed the PIC and responsible for the safety of the flight. The TACM stated that in the event of an actual emergency during flight training:

If the flight examiner or check pilot deems it necessary to take physical control of the aircraft at any stage after the occurrence of the emergency, then they shall do so in accordance with the hand‑over and take‑over procedures specified in the Operations Manual - Hand over and take‑over procedures.

The flight examiner or check pilot must be prepared and ready to assume physical control of the aircraft at any stage, particularly during critical manoeuvres such as during take‑off and landing.

As such, beyond the normal handover of control procedures, there were no special provisions in the TACM for the allocation of PIC responsibility and PF duties during ICUS flights. 

Briefings

For 2‑pilot operations or training flights, the operator’s procedures did not require pilots to brief who would assume PF duties in the event of an abnormal or emergency situation during critical phases of flight. 

Operational limits

Under the operator’s operations manual, the A109E was permitted to conduct daytime MPT operations up to a wind strength of 30 knots, with a maximum crosswind of 20 knots. The operational limit for ship’s pitch was 4° up and 2° down while the maximum permissible roll was 4°. The manufacturer did not have input into these operator‑defined limits. 

The pilots reported that the conditions at the time of the occurrence (20‍–‍28 knot headwind, 2° roll and minimal pitching) were within the operator’s limits for MPTs.

Safety analysis

Prior to the accident, VH‑XUM (XUM) made an uneventful landing on Star Coral and remained on the deck for several minutes without incident. There was no evidence that the helicopter was operating abnormally or experienced any instability during this period. 

Examination of the accident site did not reveal any evidence to suggest that the occurrence resulted from the main rotor or tail rotor striking the ship. Star Coral’s master reported that the tail rotor separated after the helicopter started contacting on the deck, indicating that contact with the tail boom by the main rotor was a consequential rather than causative factor. 

In that context, it is most likely that the helicopter encountered ground resonance. Assessment of the damage to the helicopter following the occurrence revealed significant similarities to that seen in previous A109E incidents attributed to this phenomenon. 

It is well established that ground resonance only arises when the helicopter is in contact with the ground. Both pilots asserted that the helicopter did not become airborne prior to the vibrations while the master reported that it became airborne for about 2 seconds. However, it is more likely this occurred after the vibration worsened and the helicopter started rebounding on the helideck. 

The exact cause of the vibration could not be determined. The possibility of causative operational factors such as flight control inputs or environmental factors could not be ruled in or out. 

Similarly, while the operator’s post‑accident inspection of the helicopter (including examination of its rotor and fuselage damping systems) did not reveal any apparent defects, causative technical factors could not be discounted.

However, the sudden lowering of the collective after the onset of the vibration likely aggravated the situation. The helicopter was almost certainly light on its oleos when the vibration began. Therefore, a sudden lowering of the collective would have caused the helicopter to come down firmly on the helideck. The United States Federal Aviation Administration (FAA) Helicopter Handbook describes that such an impact when the rotor is already in an unbalanced state can cause the rotor blades to move further out of phase, resulting in violent uncontrollable oscillations. This description is consistent with the occurrence sequence described by the pilots and the master. 

The pilots’ accounts of who lowered the collective differed. The recollection of the pilot flying that their intention was to lift the helicopter off the deck in response to the vibration was not consistent with a lowering of the collective. In contrast, the pilot supervising did not immediately identify the source of the vibration and later shut down the engines, believing the main rotor may have struck the tail boom. In this context, lowering of the collective would be a natural and expected response. Therefore, it is most likely that the pilot supervising lowered the collective while the pilot flying was attempting to lift the helicopter off the helideck.

In isolation, the immediate responses taken by each pilot following the sudden onset of the significant vibration were understandable. However, since the helicopter’s rotor speed was in the normal operating flight range, continuation of the take‑off would probably have resulted in the vibration dissipating (as detailed in the FAA Helicopter Handbook).

The operator had adequate procedures for responding to abnormal and emergency situations. However, the rapidly escalating nature of this occurrence meant that there was virtually no time to implement them. There was no requirement for the pilots to conduct a pre‑flight or pre‑take‑off brief about who would assume flying duties in the event of an emergency on take‑off. Therefore, the normal procedures for handover and takeover of control were assumed to apply.

However, the time between observing the vibrations and the loss of control severely limited the time available for a formal transfer of control between the pilots. As a result, neither of these procedures were followed and each pilot responded to the situation separately. 

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 loss of control during marine pilot transfer operations, involving an Agusta A109E, VH‑XUM and bulk carrier Star Coral, about 200 km north‑east of Mackay, Queensland, on 25 February 2025.

Contributing factors

  • During take‑off, the helicopter likely experienced ground resonance, resulting in the rapid onset of significant vertical oscillations through the airframe.
  • Discontinuing the take‑off after the onset of the vibration, with the rotor speed in the flight range, probably resulted in the loss of control and substantial damage to the helicopter.

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. The ATSB has been advised of the following proactive safety action in response to this occurrence. 

Safety action by Flyon Helicopters 

Following this occurrence, the helicopter’s operator, Flyon Helicopters, established ground resonance guidelines for its pilots. Forming part of its exposition, the guidelines were purposed to raise awareness of ground resonance and provide information about how to recognise and respond to the phenomenon. They included response procedures and featured case studies and video resources. The procedures were to be implemented into the operator’s training framework for new and current pilots. 

Flyon Helicopters advised the ATSB that it also planned to implement an additional briefing procedure in its training and checking manual (TACM). The briefing is to be conducted by the training or checking pilot prior to any training or checking flight. It will include:

  • the objectives and scope of the flight, including the intended lesson plan or sequence
  • the training/checking outcomes
  • the roles of each pilot, including the allocation of aircraft command responsibility
  • procedures for transferring aircraft control between pilots
  • actions to be followed in the event of an actual emergency
  • procedures to be used in the simulation of emergencies
  • procedures for the conduct of unusual operations
  • the method to be used to simulate instrument flight conditions, if required
  • human factors/non‑technical stills and threat and error management.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the pilots and operator of VH-XUM
  • the master and manager of Star Coral
  • the helicopter manufacturer, Leonardo Helicopters

References

Lemmens Y, Troncone E, Dutré S, Olbrechts T. (2012). Identification of Helicopter Ground Resonance with Multi-body Simulation28th International Congress of the Aeronautical Sciences

United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 - Helicopters

Salini S N, Haradev G S, Ranjith M. (2020). Ground Resonance: Nonlinear Modelling and Analysis, 6th Conference on Advances in Control and Optimization of Dynamical Systems (ACODS), India

United States Federal Aviation Administration. (2019). Helicopter Flying Handbook

Schafer J. (1980). Helicopter Maintenance

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 pilots and operator of VH-XUM
  • the master and manager of Star Coral
  • the ship’s flag State administration, The Bahamas
  • the helicopter manufacturer, Leonardo Helicopters
  • Agenzia Nazionale per la Sicurezza del Volo (ANSV)
  • Civil Aviation Safety Authority
  • Australian Maritime Safety Authority 

Submissions were received from:

  • the pilots of VH-XUM
  • the ship’s flag State administration, The Bahamas
  • the helicopter manufacturer, Leonardo Helicopters
  • Agenzia Nazionale per la Sicurezza del Volo (ANSV)

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

 Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     Hydrographers Passage provides a deep-water shipping route through the Great Barrier Reef between Blossom Bank pilot boarding ground, near the entrance to the passage, and the Cumberland Islands, north-east of Mackay. Pilotage is compulsory through Hydrographers Passage for ships over 70 m, as well as for loaded oil and chemical tankers and gas carriers, irrespective of size.

[2]     In-command-under-supervision (ICUS) generally refers to a pilot who is acting as the pilot in command (PIC) for a flight under the supervision of a more experienced pilot.

[3]     Very high frequency.

[4]     All ship’s headings are reported in degrees true. 

[5]     Flight idle refers to the lowest engine power setting that allows the aircraft to maintain stable operations during flight. A flight idle setting when the helicopter is on the ground allows for the engine(s) to go to higher power settings faster and facilitate take-off when collective pitch is raised. 

[6]     Performance Class 1 (PC1) refers to operations for which, in the event of a critical engine failure, performance is available to enable the helicopter to safely continue the flight to an appropriate landing area.

[7]     Collective: a primary helicopter flight control that simultaneously affects the pitch of all blades of a lifting rotor. Collective input is the main control for vertical speed.

[8]     Cyclic: a primary helicopter flight control that is similar to an aircraft control column. Cyclic input tilts the main rotor disc, varying the attitude of the helicopter and hence the lateral direction.

[9]     Category A (CAT A) operations were those where, in the event of an engine failure, the helicopter has adequate performance to safely continue or reject the take-off or landing.

[10]    The aircraft type involved was not required under regulations to carry a cockpit voice recorder (CVR) or flight data recorder (FDR). 

[11]    Visual flight rules.

[12]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters. 

[13]    Lemmens Y, Troncone E, Dutré S, Olbrechts T. (2012). Identification of Helicopter Ground Resonance with Multi-body Simulation, 28th International Congress of the Aeronautical Sciences.

[14]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters.

[15]    Salini S N, Haradev G S, Ranjith M. (2020). Ground Resonance: Nonlinear Modelling and Analysis, 6th Conference on Advances in Control and Optimization of Dynamical Systems (ACODS), India.

[16]    United States Federal Aviation Administration. (2019). Helicopter Flying Handbook. 

[17]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters.

[18]    ibid.

[19]    ibid.

[20]    United States Federal Aviation Administration. Helicopter Flying Handbook, 2019.

[21]    Schafer J. Helicopter Maintenance, 1980.

[22]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters.

[23]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters.

[24]    United States Federal Aviation Administration. Helicopter Flying Handbook, 2019.

[25]    Revolutions per minute. 

[26]    United Kingdom Ministry of Defence, AP3456 Central Flying School Manual of Flying Vol 12 – Helicopters.

[27]    Civil Aviation Safety Authority.

[28]    ‘Exposition’ is a term used in some regulatory domains for a document or set of documents that describe how an organisation will comply with all applicable legislative requirements, and how they will manage the safety of their operations. An exposition is broadly equivalent to an operations manual in other domains.

Occurrence summary

Investigation number AO-2025-009
Occurrence date 25/02/2025
Location 200 km north-east of Mackay
State Queensland
Report release date 29/07/2025
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control
Occurrence class Accident
Highest injury level None

Aircraft details

Manufacturer Agusta, S.p.A, Construzioni Aeronautiche
Model A109E
Registration VH-XUM
Serial number 11684
Sector Helicopter
Operation type Part 138 Aerial work operations
Departure point Mackay Airport, Queensland
Destination Mackay Airport, Queensland
Damage Substantial

Ship details

Name Star Coral
IMO number 9477854
Flag The Bahamas
Departure point Tianjin, China
Destination Hay Point, Queensland

Airframe overspeed involving Diamond DA40, VH-EQF, 63 km east of Kingaroy Airport, Queensland, on 12 February 2025

Final report

Report release date: 06/06/2025

Investigation summary

What happened

At 1520 on 12 February 2025, an instructor and student departed from Brisbane West Wellcamp Airport, Queensland for a training flight in a Diamond DA40 aircraft, registered VH-EQF and operated by Flight Training Adelaide.

At 1649, as the instructor and student were conducting stall and upset recovery training at an altitude of about 6,300 ft above mean sea level, the instructor took control of the aircraft. Acting on impulse and without providing a briefing to the student, the instructor attempted a wingover.

During the attempted wingover, the bank angle quickly exceeded the aircraft’s 60° bank angle limitation before continuing beyond inverted and the aircraft’s pitch became steeply nose down. During the recovery, the speed increased beyond the aircraft’s never exceed airspeed (VNE). The flight was completed without further incident and the aircraft landed at Wellcamp at 1726.

What the ATSB found

The ATSB found that the instructor attempted a wingover manoeuvre for which they had not been trained. During the manoeuvre, the aircraft was rolled through 360°, exceeding the aircraft's 60° bank angle limit and the aircraft exceeded VNE by 20 knots.

What has been done as a result

Following the incident, Flight Training Adelaide issued an internal notice to instructors and students restricting the conduct of non-training syllabus manoeuvres. The notice advised that prior to such manoeuvres being conducted, prior permission must be obtained from the Head of Operations or Deputy Head of Operations.

A presentation was also provided to instructors on the importance of personal limitations and effective decision‑making to ensure safe operations.

Safety message

This incident underlines that pilots should not attempt unfamiliar manoeuvres without first receiving appropriate training. Effective training reduces the likelihood of mishandling and also prepares a pilot to respond appropriately should a manoeuvre deviate from the intended flightpath.

While the aircraft was not damaged during this incident, it is important that all exceeded limitations are entered onto the maintenance release and reported quickly to ensure the aircraft is inspected before further flight. This will ensure that other pilots are not exposed to the risk of operating a damaged aircraft.

 

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

At 1520 local time on 12 February 2025, an instructor and student departed from Brisbane West Wellcamp Airport, Queensland for a training flight in a Diamond DA40 aircraft, registered VH-EQF and operated by Flight Training Adelaide. The flight intended to track via Gatton and Sunshine Coast Airport before conducting stall and upset recovery training near Jimna and then returning to Brisbane West Wellcamp Airport (Figure 1).

Figure 1: Overview of flight

A satellite image of the area of the flight overlaid with the recorded flightpath. The turning points for the flight are annotated.

Source: Google Earth, annotated by the ATSB 

At 1649, as the instructor and student were conducting the stall and upset recovery training at an altitude of about 6,300 ft above mean sea level (AMSL), the instructor took control of the aircraft. Acting on impulse, and without providing a briefing to the student, the instructor attempted a wingover manoeuvre (see the section titled Wingover). The instructor pitched the aircraft down to increase speed before pitching the aircraft up and beginning a rapid left roll at 120 kt indicated airspeed. At the same time, the instructor began reducing engine power.

The roll quickly exceeded the aircraft’s 60° bank angle limitation (see the section titled Aircraft details) and the instructor continued applying a roll input. As the roll angle exceeded 90°, the pitch angle dropped below the level attitude and the airspeed began increasing. The aircraft then rolled beyond inverted, the aircraft’s pitch became steeply nose down, and the instructor reduced power to idle to begin recovery from the dive. 

The instructor was aware of the risk of exceeding the aircraft’s maximum G[1] limitation and so slowly increased the pitch attitude as speed continued increasing. At 1649:56, the speed increased beyond the never exceed speed[2] of 178 kt, and 3 seconds later reached a maximum of 198 kt. The instructor continued the recovery from the dive and at 1650:02, the aircraft reached a minimum recorded altitude of 4,159 ft AMSL before a climb was commenced. At 1650:04, the speed reduced below 178 kt.

The instructor then climbed the aircraft back up to an altitude of about 5,000 ft and the student advised the instructor of the speed exceeding 178 kt. The instructor then conducted an inspection of the airframe visible from the cabin and did not identify any defects. They then handed control of the aircraft back to the student to continue the flight. About 3 minutes after the incident, another stall recovery training manoeuvre was completed. The rest of the flight was conducted normally, with the student flying the aircraft. At 1726 the aircraft landed at Wellcamp.

The instructor reported that, after landing, they thought about the attempted wingover, but also had to focus on preparation for another flight. The instructor confirmed that no bookings were scheduled for the aircraft that evening, however they did not mark the aircraft as unavailable or endorse its maintenance release at that time. The instructor then completed an evening of night flying in another aircraft. Later at home they recognised that the incident needed to be reported to the operator and intended to do so the next morning.

Early the next morning, the instructor marked the aircraft as unserviceable in the operator’s booking system. The instructor also contacted the operator’s training manager and had the aircraft’s maintenance release endorsed to prevent further flights.

Context

Instructor and student details

The instructor held a commercial pilot licence (aeroplane) and class 1 aviation medical certificate. The instructor had 930 hours of flying experience, of which 900 hours were in the DA40, with 120 hours accrued in the previous 90 days. 

The instructor had completed spin recovery training but had not completed any other aerobatics training and did not hold an aerobatics endorsement. The instructor had previously been in a DA40 where a wingover had been demonstrated, but the instructor had not received training in conduct of the manoeuvre.

The student held a student pilot licence (aeroplane) and class 1 aviation medical certificate and had about 125 hours of flying experience.

The ATSB found no indicators that the instructor or student were experiencing a level of fatigue known to adversely affect performance.

Aircraft details

The Diamond Aircraft Industries DA40 is a 4-seat, low-wing, fixed-tricycle-undercarriage aircraft with a single reciprocating engine driving a variable pitch 2-bladed propeller (Figure 2). The never exceed speed (VNE) of 178 kt was not to be exceeded for any operation in the aircraft.

Figure 2: VH-EQF

Figure 2: VH-EQF

Source: Mitch Coad, modified by ATSB

The DA40 was certified to operate in the normal and utility categories and was not certified for aerobatics. The utility category had a maximum weight limit of 980 kg. For all operations above that weight, the aircraft could be operated in the normal category only. At the time of the incident, the aircraft weighed 1,111 kg. 

The aircraft’s airplane flight manual stated that when operated in the normal category, the maximum positive load factor was 3.8 G and approved manoeuvres were limited to:

1) All normal flight manoeuvres;

2) Stalling (with the exception of dynamic stalling); and

3) Lazy Eights, Chandelles, as well as steep turns and similar manoeuvres, in which an angle of bank of not more than 60° is attained.

The manual also cautioned that aerobatics, spinning, and flight manoeuvres with more than 60° of bank were not permitted when operating in the normal category. When operating the aircraft in the utility category, the bank angle limitation was 90°. All other manoeuvre limitations were unchanged.

Wingover

The wingover manoeuvre involves a combination of pitching up and banking of the aircraft to effect a change in heading. It can be conducted at varying angles of bank and pitch to turn through different angles of heading change. For a typical 180° heading change wingover, the aircraft is descended slightly to accelerate before the aircraft is pitched up to commence a climb, followed by a left or right turn. During the turn, the pitch is reduced below level to commence descending. The angle of bank is then reduced to exit the manoeuvre in the opposite direction, at the same altitude as commencement and with wings level.

A lazy eight is a pair of wingovers of 180° heading change made in succession and in opposite directions. The resulting flightpath resembles a horizontal figure of 8 (Figure 3).

Figure 3: Lazy eight manoeuvre

A pictorial representation of the lazy 8 manoeuvre.

Source: United States Federal Aviation Administration Airplane Flying Handbook

Aerobatics

The Civil Aviation Safety Authority defined aerobatics as:[3]

aerobatic manoeuvres, for an aircraft, means manoeuvres of the aircraft that involve:

 (a) bank angles that are greater than 60°; or

 (b) pitch angles that are greater than 45°, or are otherwise abnormal to the aircraft type; or

 (c) abrupt changes of speed, direction, angle of bank or angle of pitch.

Incident reporting and post-incident inspection

Following the flight, the instructor identified that the aircraft was not scheduled to be used further that evening. However, the aircraft’s maintenance release was not endorsed, and the aircraft was not made unavailable until early the following morning. 

Upon being advised of the exceedance, the aircraft manufacturer required that the aircraft undergo a minimum of a major structural inspection. This inspection found that the aircraft was not damaged during the incident. 

Meteorology and terrain

The incident manoeuvre was conducted in clear visual meteorological conditions. 

At 1700, 11 minutes after the incident, the Bureau of Meteorology (BoM) automatic weather station at Kingaroy Airport, 63 km west of the incident recorded the wind as 4 kt from 060° magnetic. There was no recorded cloud and visibility was greater than 10 km.

The ground level elevation beneath the aircraft during the incident was about 1,400 to 1,650 ft AMSL.

Recorded data

The aircraft was equipped with Garmin G1000 instrumentation that recorded the incident (Figure 4).

Figure 4: Recorded data from VH-EQF

Figure 4: Recorded data from VH-EQF

Altitudes are above mean sea level. Source: ATSB

The manoeuvre commenced at 1649:29 with a slight descent and acceleration from an altitude of 6,297 ft AMSL. The left roll then commenced at 1649:47 at an airspeed of 120 kt, a pitch angle of 11° nose up and the bank angle reached 79° left one second later. At the same time engine power began reducing. 

A second later, at 1649:49, the pitch attitude reduced below the level attitude and the bank angle reached 111° left before the aircraft rolled beyond inverted (180° roll) 2 seconds later. At that time, the pitch angle was 33° nose down and the engine power was reduced to idle as the aircraft accelerated through 122 kt.

At 1649:53, 6 seconds after the roll commenced, the aircraft had rolled through 271° and was now in a right 89° bank, and the pitch angle had reached 59° nose down, with the speed rapidly increasing past 149 kt. Three seconds later, the speed increased beyond the never exceed speed (VNE) of 178 kt and continued increasing. At 1649:56, with the nose still pitched down 19° and the wings now level, the speed reached a maximum of 198 kt. At the same time, the recorded G level increased to a maximum of 1.42 G. Speed then began to reduce and 3 seconds later, the aircraft reached a minimum recorded altitude of 4,159 ft AMSL, about 2,600 ft above the ground. Another 5 seconds later, at 1650:04, the speed reduced back below VNE.

Safety analysis

During stall and upset recovery training, the instructor took control of the aircraft and, without briefing the student, attempted a wingover. A wingover, being essentially half of a lazy eight, was a permitted manoeuvre in the aircraft provided the angle of bank did not exceed 60° (flight manual limitation) and the pitch angle remained less than 45° (aerobatic definition limitation). However, the instructor had not been trained in this manoeuvre and did not increase pitch sufficiently before applying a rapid roll input that quickly exceeded the aircraft’s bank angle limitation. As the aircraft rolled, it began pitching down rapidly and as the roll passed beyond inverted, the pitch angle became steeply nose down. 

The instructor responded to the nose down attitude by reducing power to idle but then prioritised minimising G load during the recovery from the dive. Although the instructor achieved this aim, with a maximum recorded G value of 1.42 G, well below the 3.8 G maximum, by not increasing pitch more positively, the aircraft’s speed increased rapidly and significantly exceeded the never exceed speed. Exceeding this limitation risked structural damage or failure.

The instructor then recovered from the incident and re-established normal flight before then conducting a visual inspection of the visible airframe. Control was then handed back to the student and a further stall recovery exercise was conducted. The continuation of the planned flight indicated that the risk associated with the incident and the potential for undetected damage and control issues was not fully recognised. However, the aircraft landed without further incident.

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 airframe overspeed involving Diamond DA 40, VH-EQF, 63 km east of Kingaroy Airport, Queensland on 12 February 2025.

Contributing factors

  • During a training flight, the instructor attempted a wingover manoeuvre for which they had not been trained.
  • During the manoeuvre, the aircraft pitched steeply nose down and was rolled through 360°, exceeding the aircraft's 60° bank angle limit. During the subsequent recovery, the aircraft exceeded its never exceed airspeed by 20 knots.

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. The ATSB has been advised of the following proactive safety action in response to this occurrence

Proactive safety action by Flight Training Adelaide

Action number:AO-2025-007-PSA-01
Action organisation:Flight Training Adelaide

Flight Training Adelaide issued an internal notice to instructors and students restricting the conduct of non-training syllabus manoeuvres. The notice advised that prior to such manoeuvres being conducted, prior permission must be obtained from the Head of Operations or Deputy Head of Operations.

A presentation was also provided to instructors on the importance of personal limitations and effective decision‑making to ensure safe operations.

 

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the instructor and student
  • Flight Training Adelaide
  • Civil Aviation Safety Authority
  • the aircraft manufacturer
  • recorded data from VH-EQF. 

References

United States Federal Aviation Administration (2021), Airplane Flying Handbook (FAA-H-8083-3C) Chapter 10 (p.10-6).

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:

  • Flight Training Adelaide
  • the instructor and student
  • Civil Aviation Safety Authority

Submissions were received from:

  • Flight Training Adelaide
  • the instructor and student

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

 

[1]      G load: the nominal value for acceleration. In flight, G load represents the combined effects of flight manoeuvring loads and turbulence and can have a positive or negative value.

[2]      VNE (Never Exceed Speed): the speed limit that may not be exceeded at any time. The calculation of this speed is driven by structural or aerodynamic limitations; however, control system flutter is typically one limitation that factors heavily into the calculation of VNE.

[3]      Civil Aviation Safety Regulations Part 91 – Dictionary, Part 1 - Definitions

Occurrence summary

Investigation number AO-2025-007
Occurrence date 12/02/2025
Location 63 km east of Kingaroy Airport
State Queensland
Report release date 06/06/2025
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Airframe overspeed, Loss of control
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Diamond Aircraft Industries
Model DA40
Registration VH-EQF
Serial number 40.806
Aircraft operator Flight Training Adelaide Pty Ltd
Sector Piston
Operation type Part 142 Integrated and multi-crew pilot flight training
Departure point Brisbane West Wellcamp Airport, Queensland
Destination Brisbane West Wellcamp Airport, Queensland
Damage Nil

Loss of control involving Robinson R22 Beta, near Brunette Downs Station, Northern Territory, on 24 January 2025

Occurrence Briefs are concise reports that detail the facts surrounding a transport safety occurrence, as received in the initial notification and any follow-up enquiries. They provide an opportunity to share safety messages in the absence of an investigation. Because occurrence briefs are not investigations under the Transport Safety Investigation Act 2003, the information in them is de-identified. 

What happened

On 24 January 2025, at about 1338 local time, the pilot of a Robinson R22 helicopter was conducting cattle‑mustering operations near Brunette Downs Station, Northern Territory. The pilot was the sole occupant onboard and the helicopter’s doors had been removed. Weather conditions were clear, with a temperature of about 38°C. During mustering, the pilot landed in the open flat ground behind the cattle to rehydrate. The collective[1] was in the full down position while the engine remained at 100% RPM and the pilot held the cyclic[2] between their legs with no flight control frictions engaged.

As the pilot took a sip from their water bottle, they felt the helicopter shake. They then put the bottle down, but the left skid was at this point already a few inches off the ground. They then tried to correct the tilt with left cyclic and reached for the collective, but the helicopter continued to roll to the right. When the helicopter rolled through about 45 degrees the pilot attempted to stop the roll by placing their right foot outside the helicopter and pushing against the ground. The main rotor then contacted the ground, followed by the engine stopping and the aircraft coming to rest on its right side (Figure 1), with the pilot’s right foot trapped underneath the fuselage.

Figure 1: The occurrence R22 helicopter

Figure 1: The occurrence R22 helicopter

Source: Operator supplied              

The pilot was able to extricate their foot out from underneath the helicopter, closed the fuel mixture control and switched off the battery master as they exited.

The helicopter was substantially damaged in the accident, with damage to the right skid, fuselage, main rotor assembly, drive belts, fuel tanks and gearbox.

Safety action

The operator has published a notice to its pilots reminding them to take the following precautions on each landing, no matter how short the time on the ground:

  • Make sure all parts of the skids are firmly on the ground and the helicopter is stable.
  • Collective set full down, governor off, engine RPM back to idle or 75%, cyclic neutral with friction on. Collective strap or friction always applied when the helicopter is on the ground and keep feet on the pedals.
  • Be aware of possible dust devils[3] in the area, these may be hard to see in the wet season as there is no dust or grass present to indicate their location.
  • Pilots are to report any cases where the collective rises on its own so any potential technical issues can be investigated and corrected.

Safety message

Helicopter pilots conducting mustering operations will be regularly landing for short periods of time for various reasons, including rehydration. Good airmanship requires that the helicopter is in a safe and stable condition before releasing the controls, including reducing RPM to idle and making sure the collective is in the full down position with the control frictions applied. This will reduce the risk of the helicopter inadvertently becoming airborne in case of disturbances from environmental conditions.

Once started, dynamic rollover will develop quickly and cannot be stopped by application of opposite cyclic control alone. Even with full opposite cyclic applied, there is insufficient control authority to arrest the roll once it is developed, as the main rotor thrust vector and its moment arm serves to accelerate the roll. Quickly reducing collective pitch is the most effective way to stop dynamic rollover from developing.

The R22 Pilot's Operating Handbook includes a safety notice (SN-9) which provides advice about how to avoid dynamic rollover situations.

About this report

Decisions regarding whether to conduct an investigation, and the scope of an investigation, are based on many factors, including the level of safety benefit likely to be obtained from an investigation. For this occurrence, no investigation has been conducted and the ATSB did not verify the accuracy of the information. A brief description has been written using information supplied in the notification and any follow-up information in order to produce a short summary report, and allow for greater industry awareness of potential safety issues and possible safety actions.

[1]     Collective: a primary helicopter flight control that simultaneously affects the pitch of all blades of a lifting rotor. Collective input is the main control for vertical velocity.

[2]     Cyclic: a primary helicopter flight control that is similar to an aircraft control column. Cyclic input tilts the main rotor disc, varying the attitude of the helicopter and hence the lateral direction.

[3]     Dust devils are visible as wind vortices lifting dust from the surface with diameters usually less than one hundred metres but can extend up to a few thousand feet. They are a common occurrence throughout inland Australia, especially during the warmer months, and are dangerous to aircraft during take-off and landing (Source: Bureau of Meteorology)

Occurrence summary

Mode of transport Aviation
Occurrence ID AB-2025-005
Occurrence date 24/01/2025
Location Near Brunette Downs Station
State Northern Territory
Occurrence class Accident
Aviation occurrence category Loss of control
Highest injury level Minor
Brief release date 17/02/2025

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 Beta
Sector Helicopter
Operation type Part 138 Aerial work operations
Departure point Brunette Downs Aircraft Landing Area, NT
Destination Brunette Downs Aircraft Landing Area, NT
Damage Substantial

Loss of control and collision with terrain involving Aérospatiale (Airbus Helicopters) AS332L1, N368EV, 41 km north-north-west of Hay Aerodrome, New South Wales, on 22 November 2024

Summary

The ATSB is investigating an accident involving an Airbus Helicopters AS332L1, registration N368EV, 41 km north-north-west of Hay aerodrome, New South Wales on 22 November 2024. The aircraft was conducting a ferry flight from Broken Hill to Albury when it collided with terrain. One crew member sustained fatal injuries and the other sustained serious injuries.

The ATSB is conducting the examination and analysis of evidence collected.

To date, the ATSB investigation has:

  • completed the accident site activities and wreckage assessment
  • interviewing the flight crew and witnesses
  • recovered tail rotor components for detailed examination
  • inspected tail rotor components in conjunction with representatives from the French BEA and Airbus Helicopters

For the tail rotor components recovered from the accident site, the ATSB is awaiting information from an external party and is unable to further progress the investigation until that third party input has been received. The work of the external party is to include a detailed assessment of the bearing assemblies associated with the tail rotor components and an analysis of the grease that was in use at the time.  A timeline for the completion of the work is currently unavailable. As a result, the investigation has been deferred.

A final report will be released at the conclusion of the investigation. Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties, so that appropriate safety action can be taken.

Preliminary report

Report release date: 28/01/2025

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 22 November 2024, at about 0828 local time, an Aérospatiale (Airbus Helicopters) AS332L1 Super Puma helicopter, registered N368EV, departed Broken Hill Airport, New South Wales for Albury with one pilot and a passenger on board. The flight was the final leg of a repositioning flight from Kuala Lumpur, Malaysia that started on 17 November 2024. The helicopter was being positioned at Albury for use as an aerial firefighting asset over the summer period.

At about 0955, while cruising at about 3,500 ft above mean sea level, the pilot noted a high frequency vibration through the airframe that was also apparent to the passenger. In response, the pilot lowered the collective control[1] and began a descent, noting that Hay aerodrome was about 22 NM (41 km) from their location. Recorded data showed the helicopter was descended at about 1,500 ft/min with an indicated airspeed of about 115 kt.

In interview with the ATSB, the pilot reported that, during the descent, they heard a loud thud, which was immediately followed by an uncommanded yaw[2] to the left. To control the yaw, the pilot established an autorotation[3] then indicated that they reduced the throttles to idle, however, inadvertently reduced the no 2 engine throttle beyond the idle gate position resulting in the engine shutting down. 

With the reduction in power, the uncommanded yaw ceased, and the pilot initiated a straight-in approach towards the open fields below. On approaching the ground, the pilot reported that, during the final flare with reduced airspeed, application of the collective control[4] to cushion the landing resulted in the helicopter yawing again. 

At about 0958, the helicopter landed heavily, initially impacting terrain in an upright attitude but facing in the opposite direction of flight, before rolling onto its right side. The emergency locator transmitter was activated in the impact and there was no post-impact fire. The pilot and passenger survived the impact but were seriously injured. The passenger, who was seated in the forward cabin, succumbed to their injuries. The helicopter was destroyed. 

Context

Pilot information

The pilot held a United States Department of Transportation - Federal Aviation Administration  Airline Transport Pilot Certificate (issued in 2023), with the necessary ratings to fly the helicopter. The pilot also held a Medical Certificate First Class, issued in November 2024.  The pilot also held an Australian-issued Commercial Pilot Licence (issued 2016) with an AS322 type rating.

The pilot completed AS332 type rating training in April 2023 and had about 8,000 hours total aeronautical experience at that time. Since completing the training, the pilot had logged about 400 hours flight time on the AS332. The pilot reported completing annual recurrent training on the AS332 in May 2024.

Helicopter information

General information

The AS332L1 Super Puma is a utility helicopter developed and initially produced by Aérospatiale, and subsequently manufactured by successor companies Eurocopter and Airbus Helicopters. N368EV was manufactured in 1988 by Aérospatiale with the serial number 2179. The helicopter was fitted with 2 Turbomeca Makila 1A1 turboshaft engines. 

The helicopter was registered in the United States and was issued a Certificate of Airworthiness by the Department of Transportation - Federal Aviation Administration in the transport category on 26 January 2011. The type certificate holder was Airbus Helicopters.

At the time of the accident, the helicopter had accrued about 28,323 hours total time in service. 

Tail rotor system

The AS332 tail rotor system comprises a 5-bladed tail rotor assembly that rotates in a counter‑clockwise direction. The tail rotor blades mount to the tail rotor hub and are driven by the tail gearbox via the inclined tail rotor shaft. 

Tail rotor blade pitch control occurs in response to the pilot’s tail rotor pedal inputs via mechanical connection to the servo control. The servo control actuates a pitch change control rod located within the hollow tail rotor shaft and is connected to the pitch change control plate. The pitch change control plate is mounted to and supported by a splined sleeve that slides laterally in a guide located within the tail rotor shaft (Figure 1 and Figure 2).

Figure 1: Tail rotor gearbox and related components

Figure 1: Tail rotor gearbox and related components

Source: Airbus Helicopters, annotated by the ATSB

Meteorological information

The Bureau of Meteorology’s forecast conditions for Broken Hill and Albury airports were described as CAVOK[5] for the duration of the flight. Recorded weather observations for Hay aerodrome showed the mean wind speed varying between 12 kt and 15 kt from the north around the time of the accident.  

The pilot reported that, following the departure from Broken Hill, and while cruising at about 3,500 ft, they were experiencing smooth flying conditions and had a tailwind of about 10⁠–⁠15 kt. 

Recorded data

The helicopter was not fitted with a cockpit voice recorder or flight data recorder. A recent modification included the installation of a helicopter usage and monitoring system from which preliminary flight data was extracted by the ATSB.            

The helicopter was also equipped with a Tracplus RockAIR portable tracking device. Additional navigational equipment was retained for further examination.

Wreckage and impact information

The helicopter impacted grass covered, flat terrain, in a slight left side down, but generally upright attitude facing about 320° (magnetic). The fuselage and belly sections were heavily compressed during the impact sequence, with the aft fuselage structure collapsing, resulting in the tail boom striking the ground. The tail boom ground strike then resulted in the vertical fin, with the tail gearbox and horizontal stabiliser attached, to separate from the tail boom. Following the ground contact and compression damage to the fuselage and tail boom, the helicopter rolled onto its right side. The wreckage was contained within the immediate area of the impact point and minimal forward projection of debris was noted. 

The landing gear was found in the down position with the nose and left main gear sustaining significant damage. The compression of the belly resulted in considerable release of fuel from the fuselage belly tanks. The cabin‑fitted ferry fuel tanks were dislodged from the floor mounts in the impact but remained intact.

During the impact sequence, fractures occurred on the main and tail rotor systems, including an associated loss of blade material consistent with a ground strike. However, each of the blades remained securely attached to their respective attachment point.

Examination of the wreckage found that the tail rotor pitch change control plate was detached from the tail rotor gearbox assembly and was the likely reason for the uncommanded yaw. Closer examination showed that the splined sleeve supporting the pitch change control plate had fractured at the mounting flange and the pitch change control rod was also fractured (Figure 2).

Figure 2: Tail rotor assembly with separation of pitch change control plate from gearbox

Figure 2: Tail rotor assembly with separation of pitch change control plate from gearbox

Source: ATSB

Component examination

Introduction

The fractured splined sleeve was examined at the ATSB’s technical facilities in Canberra, in the presence of representatives from the French Bureau d'Enquêtes et d'Analyses and Airbus Helicopters. 

The manufacturer advised that the splined sleeve had no safe life limit,[6] and its serviceability was determined by on-condition maintenance requirements. The continuation in service of the component was contingent on the absence of corrosion or surface scratches as determined by visual inspection at specified intervals. 

Component examination 

Following the removal of its surface protective coating, the splined sleeve was identified as part number AS332A33 0070.20. The sleeve’s serial number was also identified to assist with determining the component manufacturing history. 

Initial examinations of the fracture surface found that a fatigue crack had propagated around the majority of the splined sleeve’s circumference, leading to fracture of the sleeve in the section adjacent to the pitch change control plate mount flange. Further examination is to be conducted to determine the crack origin and identify the factors contributing to the cracking (Figure 3).

Figure 3: Separation of the pitch change control plate mount flange from the splined sleeve

Figure 3: Separation of the pitch change control plate mount flange from the splined sleeve

Source: ATSB

Safety action

In response to this accident, Airbus Helicopters published safety related information, which included:

  • Safety Information Notice 4082-S-64 on 29 November 2024 that highlighted tail rotor assembly maintenance tasks, specific to inspection and lubrication requirements.
  • Alert Service Bulletin ASB AS332-64-20-003 on 23 December 2024 that specified an inspection for defects of the splined sleeve radius area of the control plate mount flange.

Further investigation

To date, the ATSB has:

  • examined the wreckage
  • collected items of evidence from the accident site
  • collected pilot and aircraft records
  • conducted interviews with relevant parties
  • liaised with Airbus Helicopters and the French Bureau d'Enquêtes et d'Analyses 
  • conducted a preliminary examination of the splined sleeve.

The investigation is continuing and will include:

  • a further review and detailed examination of the splined sleeve
  • examination of the tail gearbox and components
  • an assessment of accident survivability aspects
  • a review of helicopter records and loading aspects 
  • a review of the pilot’s qualifications and experience
  • analysis of recorded data.

A final report will be released at the conclusion of the investigation. 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. 

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     Collective: a primary helicopter flight control that simultaneously affects the pitch of all blades of a lifting rotor. Collective input is the main control for vertical velocity. Raising or lowering the collective also increases or decreases engine power to maintain rotor RPM as the rotor drag changes.

[2]     Yawing: the motion of an aircraft about its vertical or normal axis.

[3]     Autorotation: Autorotation is a condition of descending flight where, following engine failure or deliberate disengagement, the rotor blades are driven solely by aerodynamic forces resulting from rate of descent airflow through the rotor. The rate of descent determined mainly by airspeed.

[5]     Ceiling and visibility okay (CAVOK): visibility, cloud and present weather are better than prescribed conditions. For an aerodrome weather report, those conditions are visibility 10 km or more, no significant cloud below 5,000 ft, no cumulonimbus cloud and no significant weather.

[6]     Safe life limit: An airworthiness limitation that is applied to life limited parts, which have a predetermined lifespan after which they must be replaced to ensure safety.

Occurrence summary

Investigation number AO-2024-060
Occurrence date 22/11/2024
Occurrence time and timezone 11:45 Australian Eastern Daylight Time
Location 41 km north-north-west of Hay Aerodrome
State New South Wales
Report release date 28/01/2025
Report status Preliminary
Investigation level Short
Investigation type Occurrence Investigation
Investigation phase Examination and analysis
Investigation status Deferred
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control, Transmission and gearbox
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Aerospatiale Industries
Model AS332L1
Registration N368EV
Serial number 2179
Aircraft operator Forest Air Helicopters (AUST) Pty Limited
Sector Helicopter
Operation type Part 91 General operating and flight rules
Activity General aviation / Recreational-Other general aviation flying-Ferry flights
Departure point Broken Hill Airport, New South Wales
Destination Albury, New South Wales
Injuries Crew - 1 (Serious), Passengers - 1 (fatal)
Damage Substantial

Loss of control and collision with terrain involving a Morgan Cougar Mk1 aircraft, VH-LDV, 19 km north-north-west of West Sale Airport, Victoria, on 16 November 2024

Final report

Report release date: 19/01/2026

Investigation summary

What happened

On 16 November 2024, an amateur-built experimental certificate Morgan Cougar Mk 1 aircraft, registered VH-LDV, with a pilot and 2 passengers on board, departed from West Sale Airport, Victoria for a local area flight. The aircraft collided with terrain in a paddock it was orbiting around, about 19 km north-north-west of West Sale Airport, 17 minutes after departure. The aircraft was destroyed, and the 3 occupants were fatally injured.

The pilot was operating a VH-registered aircraft with a Recreational Pilot Licence (RPL), issued by CASA in recognition of the pilot holding a Recreational Pilot Certificate (RPC), issued by Recreational Aviation Australia (RAAus). 

What the ATSB found

The aircraft entered an accelerated aerodynamic stall while in a steep turn at a low speed and height from which it was too low to recover (about 220 ft above ground level). The pilot had a reported history of conducting steep turns at low heights, and on occasions at low speeds, and had low flying hours in the aircraft and no transition training. Therefore, it was likely that the pilot was not aware of the stall characteristics of the aircraft and that it might depart controlled flight in an abrupt and unexpected manner. 

The pilot’s history also included several counselling sessions they had received from members of the local aviation community in response to risky flying activities. However, no official reports were submitted to authorities and therefore no follow-up action was ever initiated.

A review of the pilot’s examination history revealed several errors about aerodynamic stalling in exams conducted during 2024 and it was concluded that the pilot likely had inadequate knowledge of the relationship between angle of bank, load factor and stall speed. Additionally, the investigation found several instances of irregular practices in training and exams at the Adventure Flight Training (AFT) school, which included the pilot’s exams, and concluded that those management practices likely contributed to the pilot’s inadequate knowledge.

RAAus administered the examination system, and it was found to have inadequate controls to mitigate the practices at AFT. When RAAus uncovered the problems at AFT in 2024, they issued a safety related suspension (SRS) notice against the chief flying instructor of AFT, which resulted in the cessation of operations in August 2024. 

After the accident, RAAus issued another SRS against the AFT graduates for potential knowledge deficiencies. However, when CASA were advised of this action, they did not follow-up to verify if any of those graduates also held a CASA licence granted based on holding an RAAus RPC which had been suspended. It was subsequently found that 2 members held a CASA-issued licence, granted based on their suspended RPCs.

Furthermore, the accident aircraft was found to have design deficiencies, which contributed to the severity of the occupants’ injuries. They included a lack of energy attenuation in the landing gear and seating, and the installation of a fuel tank between the engine and instrument panel that ruptured and caused the post-crash fire. In addition, it was likely that car seatbelts were fitted and the front seatbelts failed in the accident, which resulted in the front seat occupants being ejected from their seats. 

Finally, it was found that the CASA advisory circular for amateur-built experimental certificate aircraft provided recommendations to address some aspects of aircraft crashworthiness, which included seatbelts. However, it did not address energy attenuation or fuel tank installation. In addition, while it provided safety recommendations for pilots conducting flight testing, it did not recommend transition training for new owners of these aircraft.   

What has been done as a result

RAAus commenced a digital systems redevelopment project with scoping of user requirements completed in 2023, which includes their learning management system. This incorporates the implementation of an online exam system. RAAus are also progressing the re-drafting of several key documents in their Exposition, which includes updates to the following:

  • flight operations manual to contain greater clarity around the conduct of RAAus examinations
  • occurrence and complaints handling manual to include a description of the process for handling a safety related suspension for an individual if their membership has lapsed
  • syllabus of flight training to include further development of the stalling element of the syllabus. 

CASA has implemented a more robust process to ensure that all reports received that relate to suspension, variation or cancellation of authorisations issued by an approved self‑administering organisation will include a review of CASA records to determine if the reported individual also holds a ‘same-in-substance’ CASA-issued authorisation. If so, the holder’s qualifications will be subject to review through the CASA Coordinated Enforcement Process.  

Safety message

The investigation revealed a trend in risky flying behaviour by the accident pilot, which was likely compounded by inadequate knowledge from a flight training school that had developed irregular practices in the delivery of training and had inadequate supervision. While many people knew of the pilot’s risky flying behaviour and had attempted to counsel them, there was no evidence that any of the incidents were reported to authorities, and the counselling efforts were ultimately unsuccessful. 

The ATSB has previously advocated for witnesses, particularly those within the aviation industry, to report any concerns regarding unsafe behaviours through mechanisms such as confidential reporting systems (see AO-2019-027). The ATSB re-iterates this previous safety message.

CASA has published recommended guidance for amateur-built experimental certificate aircraft. While this publication is directed at those who design, build and flight test these aircraft, the safety precautions should be read by new owners and considered equally applicable to them.

Safety Watch logo

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. In this accident the lack of energy attenuation and location of the fuel tank in the design of the aircraft and the likely fitment of car seatbelts all increased the risk to occupants in the event of a ground collision. 

Summary video

 

The occurrence

At 1730 local time on 16 November 2024, an amateur-built Morgan Cougar Mk 1 aircraft, registered VH-LDV, with a pilot and 2 passengers on board, departed from West Sale Airport, Victoria for a local area flight. The pilot was seated in the front left seat, and the passengers were seated in the front and rear right seats. A review of Airservices Australia automatic dependent surveillance-broadcast (ADS-B) data identified that the aircraft conducted a left turn on departure and tracked 15 km north of West Sale Airport to the town of Maffra, where they arrived overhead at about 1736 (Figure 1).

Figure 1: Accident flightpath with key timings and locations

Accident flightpath with key timings and locations

Sources: Airservices Australia and Google Earth, annotated by the ATSB

The aircraft made a series of turns overhead the town of Maffra for about 4 minutes. At 1740, the aircraft departed from overhead Maffra and tracked about 11 km west towards Tinamba West. The aircraft conducted a right-hand turn overhead a property at Tinamba West, which belonged to relatives of the aircraft occupants, before commencing a series of left-hand turns (orbits) around a point about 1 km to the south-east of the property over open paddocks (Figure 2). 

On the second orbit, the aircraft made a low pass along the Macalister River, adjacent to where several witnesses, which included 2 adults, were located. The 2 adults later stated that they had witnessed the aircraft conduct 2 orbits past their location before the accident. They reported the second pass along the river was lower than the first, such that they could both see the occupant in the rear seat, and that the aircraft sounded normal.

Figure 2: Orbits and the location of witnesses

Orbits and the location of witnesses

Sources: Airservices Australia and Google Earth, annotated by the ATSB

A closed-circuit television (CCTV) camera, located about 700 m north-north-east of the accident site, captured the aircraft entering a left turn towards the camera on its third orbit (Figure 3 [1]). During the turn the angle of bank increased to a steep turn attitude (Figure 3 [2]) before the nose of the aircraft pitched down and the aircraft descended in the left turn behind trees (Figure 3 [3]). 

Figure 3: CCTV footage of final turn

CCTV footage of final turn

Images subject to visual distortion (fisheye lens effect). Source: Victoria Police, annotated by the ATSB

One of the witnesses reported that, as the aircraft approached them for a third pass, it did a hard left turn and then appeared to be falling and not gliding towards the ground, as though it did not have enough speed. They reported that the wings levelled after the turn and it landed very hard on its belly and immediately caught fire. The second witness saw it bank hard left and fall out of the sky but did not see the collision. The 3 occupants were fatally injured, and the aircraft was destroyed.

Context

Accident site and wreckage

Overview

The aircraft impacted flat and open terrain at an elevation of about 130 ft and produced a ground scar on a track of 315° T (Figure 4). The length of the wreckage trail was 30.3 m from the first ground scar to the propeller spinner, with the fuselage resting on a heading of 303° T. Impact analysis indicated the aircraft struck the ground in a slight left wing low and close to level pitch attitude, which was consistent with the witness report of the collision.

Figure 4: Accident site

Accident site

Source: ATSB

There was a delta-shaped fuel spray and debris pattern along the wreckage trail. A fuel‑fed fire occurred after the ground impact, however, most of the fire damage to the aircraft was confined to the fuselage within the area bounded by the firewall,[1] aft bulkhead (behind rear seats) and the inboard sections of the wings (Figure 5). The engine and propeller were also affected by the post‑impact fire, but to a lesser extent than the fuselage. The wings and tailplane (except the rudder) remained attached to the fuselage. The rudder was found in the wreckage trail. 

Figure 5: Fire damage to the aircraft

Fire damage to the aircraft

Source: ATSB

The engine remained attached to the firewall, which had separated from the fuselage, and the 3-bladed propeller hub was attached to the engine. There was considerable disruption between the engine and airframe. One substantially fire-damaged carbon fibre propeller blade was attached to the hub and the other 2 propeller blades, which were not fire‑affected, had separated at their roots and were found fragmented within the debris field.

Aircraft inspection
Engine and propeller

The 2 witnesses to the accident sequence provided different accounts of the noise of the aircraft just prior to the collision. One reported that the aircraft sounded normal before the final turn and then went quiet, whereas the other witness reported no change in the sound of the aircraft during the accident sequence. 

The intake manifolds, carburettors, drive belts, oil hoses, and fuel lines were heavily damaged by the post-impact fire. The left carburettor was damaged beyond assessment, and the right carburettor was found with the throttle valve in the idle position. However, the carburettor throttle valve is spring loaded to idle, so the as-found position was not considered a reliable indicator of its position in flight.

The number 1 cylinder head was removed for inspection and was found to be lubricated and did not exhibit any signs of distress. The other cylinders could not be accessed due to impact damage. The engine oil filter and oil sump magnetic plug were inspected, and no metallic debris was identified.

The turbocharger compressor scroll was found separated from the turbocharger and directly below the turbocharger assembly. The scroll exhibited an overstress failure, with fracture surfaces but no scoring. Several turbocharger compressor vanes exhibited bending in the opposite direction of rotation, which indicated the compressor was running at impact (Figure 6).

Figure 6: Rearward bending of turbocharger compressor vanes

Rearward bending of turbocharger compressor vanes

Source: ATSB

The propeller hub was secured to the engine output flange by 6 bolts and concentric locating pins. The hub was removed for inspection and very slight ovalisation of all 6 of the locating pins’ hub-side holes in the direction of rotation was noted. 

Two of the propeller blades fractured at the blade root and separated from the hub, leaving the propeller root sections still clamped in the hub. The carbon fibre remnants on the root sections indicated tearing and separation of the blades in the opposite direction to rotation. 

One of the propeller blade root hubs was relatively unbent and the following blade root hub (in the direction of rotation) exhibited rearward bending. This suggested a loss of propeller energy between consecutive blade ground strikes and the possibility that the first blade to separate was being driven by engine power.

The use of non-metallic propeller blades increased the uncertainty in the engine power assessment. However, in combination with the turbocharger compressor damage it was concluded that the engine was operating at impact, but the power level could not be determined. 

Flight controls

Primary aircraft flight controls were of the direct acting cable, pushrod, and bellcrank type with a dual yoke control installed for elevator and aileron control. The wing flaps were electrically powered and found in the retracted position. The flaps could not be tested due to damage.

Rudder, elevator, and aileron controls were free to move about their full range. Several control cables were found severed and were inspected for signs of pre-impact failure. No wear, bird-caging, fretting, or other indications of damage were noted on the cables, and it was concluded that all these cables failed from overstress during the ground collision.

The rudder separated from the vertical stabiliser and was found in the wreckage trail. The mounting hardware was found, and the fracture surfaces of the flight control attachment points were consistent with an overstress failure.

While ATSB investigators were handling the yoke controls for inspection and photography, the chainring, which was part of the aileron control, separated under gravity from its bearings and support frame (Figure 7). However, given that they were not found separated, and that the aircraft attitude was recovered towards wings-level before the collision, it was concluded that the controls did not separate in-flight. The chainring and bearings were retained for further examination at the ATSB technical facility and details of that examination are provided in Appendix A – Examination of the flight controls.

Figure 7: Chainring separation from bearings and support frame

Chainring separation from bearings and support frame

Source: ATSB

Fuel system

The aircraft fuel system consisted of a 55 L fiberglass tank in each wing, located aft of the main spar, and a 90 L fibreglass main tank between the instrument panel and the firewall. Fuel could be transferred from the wing tanks to the main tank via an electric transfer pump. The engine feed was from the main tank, via a fuel filter and 1 of 2 electric pumps.

The wing fuel tanks were found empty and relatively undamaged. The main tank was completely consumed by the impact and fire, along with significant parts of the surrounding fuselage. This was consistent with the flight fuel carried in the main tank.

Undercarriage

The undercarriage was a fixed tricycle gear, with a single-piece fibreglass strut supporting both main wheels, and a castering, spring lever nose wheel. The main and nose gear were found in the wreckage trail and their separation from the airframe was consistent with multiple overstress failures of the attachments at impact. The main gear assembly exhibited no evidence of permanent deformation or absorption of energy. 

Seats and restraints

The aircraft was designed and built with 2 front seats and a 2-place rear bench-seat arrangement. The front seats were found in the wreckage, and their rear mountings were attached to the fuselage seat frame aluminium angle cross-member. The steel bolts used to mount the rear of the seats to the aluminium angle were present and fastened. The forward steel cross-member for the front seats was bowed forward (Figure 8). The right seat pan was retained by the seat back and appeared to have collapsed onto the main wing spar,[2] located underneath the front seats. The left front seat pan had separated from its seat back and was found in front of the seat frame forward cross-member.

Figure 8: Aircraft seat frame, wing spar and seats

Aircraft seat frame, wing spar and seats

Source: ATSB

Both front seatbelt latch plates were found separated from their buckles and their associated harnesses were destroyed by the fire (Figure 9). The rear seats and seatbelts were destroyed by the post‑impact fire. However, the seatbelt latch plate for the rear seat occupant was found in its buckle.

Figure 9: Aircraft seatbelt latch plates

Aircraft seatbelt latch plates

Source: ATSB

Instruments and avionics

The aircraft was fitted with:

  • a Dynon Skyview SV-D1000 avionics unit, which provided a primary flight display with a navigation display and engine instruments display
  • a 2-channel autopilot system
  • analogue airspeed, oil pressure, altimeter, turn/slip and vertical speed instruments.

The instrument panel and instruments were found together in the wreckage, forward of the front seats and behind the engine firewall. All instruments and the panel were destroyed by the impact and fire. However, the Dynon unit was retained by the ATSB for examination (see the section titled Flight path analysis).

Meteorological information

The Bureau of Meteorology provided 30-minute METAR[3] recordings for the East Sale Airport, located about 30 km south-east of the accident site. At 1730, the temperature was 26°C and the wind was 17 kt from 090° T. The visibility was greater than 10 km and no cloud was detected. Similar conditions were recorded at 1800. A local weather station about 4 km north of the accident site recorded the weather data at 5-minute intervals. Table 1 presents the temperature, mean wind and wind gust data recorded at 1745 and 1750 by the local weather station.

Table 1: Local weather station recordings

Time

Temperature (°C)

Wind speed (kt)

Wind gust (kt)

Wind direction (°T)

1745

27.5

6.2

8.0

124

1750

27.3

6.4

12.8

122

Flight path analysis

The aircraft was fitted with a Dynon Skyview SV-D1000 avionics unit, with the capability to record various flight path parameters. The unit was recovered from the accident site and examined at the ATSB facilities. The memory chip was recovered from the internal memory unit and read. However, due to the extensive thermal exposure beyond the specifications of the chip, the data was corrupted and not usable.

Airservices Australia ADS-B data was obtained for the flight path analysis. The data included altitude in 25 ft increments and groundspeed with timings, which were combined with the CCTV camera footage for flight path analysis. A mean wind speed of 6 kt and wind gust speed of 12.8 kt from 124° T were used to calculate a range of estimated calibrated airspeeds (CAS) for each data point.

A trend over the last 3 minutes was noted with the aircraft generally descending from a recorded altitude of 850 ft above mean sea level (AMSL) to 275 ft AMSL, with a low pass at 97 ft above ground level (AGL) during the second left orbit overhead the Macalister River. The groundspeed varied over the last 3 minutes from 103 kt to 71 kt, with a gradual and almost continuous reduction in speed below that recorded during the previous orbit speeds over the last 30 seconds of the flight.

The final turn started at 1746:52 at 64 kt (67–74 kt CAS) and 269 ft AGL. The nose drop observed in the CCTV footage during the final turn, followed by a rapid descent, was indicative of an aerodynamic stall[4] in a steep turn. The stall likely occurred at 1746:59 at 56 kt (59–65 kt CAS) and 221 ft AGL. After the stall there was an abrupt reduction in altitude and increase in speed, consistent with initiation of a stall recovery (Figure 10).

Figure 10: Plot of ADS-B data and CAS calculations

Plot of ADS-B data and CAS calculations

Source: ATSB

The final turn was of a tighter radius than the previous orbits and analysis of the radius of this turn indicated it was consistent with a turn to align with the Macalister River and would have required an average angle of bank of 45° in a steady coordinated turn. The turn radius appeared to reduce during the turn at a relatively constant speed, which would have required an increase in the angle of bank and load factor. For about the last minute of flight, the aircraft was operating below a height of 500 ft, which was the minimum height applicable to this portion of the flight, as prescribed in Civil Aviation Safety Regulation (CASR) 91.267. Further description of each orbit is provided in Appendix B – Flight path description.

Aircraft information

General information

The aircraft was an amateur-built Morgan Cougar Mk 1, registered VH-LDV, issued with a special certificate of airworthiness under the designation: experimental certificate. It was a 4-seat, piston-engine aircraft with a maximum take-off weight of 800 kg. The aircraft was fitted with a Rotax 912 ULS 4-cylinder turbocharged engine and 3-bladed composite (carbon fibre) propeller. The aircraft’s builder sold it to a syndicate of 3 pilots, which included the accident pilot, on 5 November 2024, with its manufacture date recorded as 2013 and with 136.9 airframe hours.

The aircraft build started in May 2013 and the experimental certificate for Phase 1 flight testing was issued by a Civil Aviation Safety Authority (CASA) delegate in December 2015. The experimental certificate for Phase 2, completion of the test flying phase, was issued by the same CASA delegate in April 2017. 

Amateur-built experimental aircraft

According to the CASA advisory circular (AC) 21-10 v4.3: Experimental certificates, an experimental certificate may be issued for the purpose of operating amateur-built aircraft, and it does not attest to the airworthiness of the aircraft. CASA AC 21.4(2): Amateur-built experimental aircraft – certification (published in 2000) stated:

An amateur-built aircraft is an aircraft, the major portion of which has been fabricated and assembled by a person or persons who undertook the construction project solely for their own education or recreation. 

Amateur builders should call upon persons having experience with aircraft construction techniques…to inspect particular components…prior to closure and to conduct other inspections as necessary.

The AC required an authorised person, or CASA, to only inspect the aircraft once prior to the initial test flight and the inspection should establish that:

the aircraft is registered and marked in accordance with the requirements

the aircraft meets the major portion rule

the weight and balance data is available and the aircraft has been correctly weighed

the engine(s) and flight controls operate properly

the pitot static system and associated instruments operate properly.

Note: The person carrying out the inspection is not responsible for the integrity of the design or construction of the amateur-built experimental aircraft, nor for the identification of any structural design or construction deficiencies — responsibility for the design, construction and integrity of the aircraft rests with the amateur builder. 

In accordance with CASA AC 21.4(2), the builder maintained a build-log that detailed the progressive build of the aircraft with photographs and notes. The builder consulted with the designer during the initial build and with both the designer and the CASA delegate for subsequent modifications. The designer of the aircraft was deceased prior to the accident. 

Weight and balance

The maximum take-off weight published in the aircraft logbook was 800 kg and the centre of gravity limits were between 2,263 mm and 2,537 mm aft of the datum. The aircraft was reweighed 2 days prior to the accident, which involved transferring all fuel remaining in the wing tanks into the main tank. The transfer process resulted in empty wing tanks and a full main tank.

The weight and balance for start-up and at the time of the accident were calculated and found to be within the published limits. 

Builder modifications to the design

The aircraft builder reported to the ATSB that they made several modifications to the original design, consulting with the CASA delegate and designer about the changes. They reported that under the original design, aileron and elevator control was via a stick, with a linear relationship between stick and control surface movement across the full range. However, the stick control required large inputs for small movements of the control surfaces, felt sloppy and was designed with components bolted to the floor in a manner that exposed them to interference from the occupants. 

After a taxiing accident in 2019, the builder incorporated modifications, which included a new engine (Rotax) and propeller, yoke controls and roller bearings to eliminate lateral movement (play) in the horizontal stabilator control tube. The builder noted improved climb and cruise performance after the modifications, but reported the greatest improvement was in flight handling. 

Following the modifications, the roll, pitch and yaw motions were described as ‘smooth, linear and predictable… There was no slop in the control system and this resulted in the aircraft being responsive without being twitchy.’ The autopilot actuators provided additional resistance and a heavier feel to the original design. The builder reported no noticeable changes to the stall speed or aircraft reaction during a stall after these modifications but recovery from a stall was reported to be quicker than previous. 

Aircraft stall warning and characteristics
Stall warning

While not published in the pilot operating handbook (POH), the aircraft was fitted with a stall warning system incorporated into the Dynon avionics unit. The documentation for the unit stated that it provided an audio alert as the angle of attack increased, which started as an intermittent tone and increased in frequency as the angle of attack increased, until it became a continuous tone at the critical angle of attack.[5]

There were 3 options in the settings for how early the intermittent tone activated. The ATSB could not determine what was set or if a calibration flight was conducted. The builder reported that they believed it was factory set and one of the new owners reported they believed there was an angle of attack indicator but no audible stall warning. They further stated that they had not conducted any of their own verification/calibration flights before the accident.

Stall characteristics

The stall characteristics were described in the POH as having about a 10 kt buffet warning before a slow nose drop at the stall until flying speed was regained. The POH’s published ‘straight and level’ clean indicated stall speed was 37 kt. However, after construction, the aircraft was subject to 40 hours of restricted flying operations under Phase 1 of its experimental certificate, which included stall testing. The results from Phase 1 testing were recorded in the aircraft logbook, which indicated the stall speed was found to be 38 kt. 

The builder described the aircraft handling characteristics approaching the straight and level clean stall as ‘a mush’ with no sudden nose‑down pitching moment. However, they reported that during a 30° angle of bank left turn, the aircraft started to stall at about 42 kt and then suddenly pitched nose-down with a left yaw. The aircraft was quickly recovered but the builder was reportedly surprised by the different response to a stall in a turn to what was experienced in straight and level flight and hypothesised that a greater angle of bank might exacerbate the response.

The following table presents the indicated stall speeds and load factors in level coordinated turns from wings level to 75° angle of bank and up to a load factor[6] of 3.86, noting the published manoeuvring limit for the aircraft was 4G. The manoeuvring stall speed was calculated by multiplying the 1G stall speed by the square root of the load factor.

Table 2: Calculated stall speeds for increasing angle of bank and load factor

Bank angle

Load factor (G)

Stall speed (37 kt)

Stall speed (38 kt)

Stall speed (42 kt)

0

1.00

37

38

-

30

1.15

40

41

42

45

1.41

44

45

46

60

2.00

52

54

55

70

2.92

63

65

67

75

3.86

73

75

77

The builder recalled discussing various types of stalls, including accelerated stalls, with the aircraft designer. However, the designer recommended against the builder testing these characteristics unless accompanied by either the designer or an experienced instructor. The builder did not conduct any stall testing additional to that detailed above.

Stall testing for amateur-built aircraft

In AC 21.4(2), CASA ‘strongly urged’ builders to ‘make detailed reference to the U.S. FAA [Federal Aviation Administration] Advisory Circular AC 90-89, “Amateur-Built Aircraft Flight Testing Handbook”, prior to their flight programs commencing, and follow the guidance provided.’ In accordance with the FAA AC, for straight and level stall testing, the aircraft should be slowed towards the expected stall speed at 1 kt per second and the stall warning should occur about 5 kt before the stall. 

The FAA AC stated that a sharp wing drop during stall testing could be regarded as the onset of spin autorotation, and the recommended corrective action is reducing power, full opposite rudder, and lowering the nose to the horizon or below. The guidance for flight testing of accelerated stalls provided the following description:

An accelerated stall is not a stall reached after a rapid deceleration. It is an in-flight stall at more than 1 G, similar to what is experienced in a steep turn or a pull up.

The accelerated stall is based on a closure rate between the aircraft speed and stall speed. Standards for type certified aircraft have historically[7] used a closure rate of 3‍–‍5 kt per second for testing accelerated stall characteristics or required a minimum load factor for the test conditions (Gratton, 2015). 

A turning manoeuvre is often used for the accelerated stall testing, which can affect the aircraft response. According to Gratton (2015), low wing aircraft tend to roll into the turn during a turning stall and high wing aircraft tend to roll out of the turn. Consequently, certification authorities have historically placed roll limits on the acceptable response of an aircraft during a turning or accelerated stall (Gratton, 2015). Therefore, accelerated stall flight testing may not be recommended for an amateur-built aircraft and the notes within the accelerated stall section of the FAA AC contained the following advice:

Do not attempt this or any other extreme maneuver unless the designer or kit manufacturer has performed similar tests on a prototype aircraft identical to the amateur-builder’s aircraft.

Of note, the reference from Gratton (2015) that low wing aircraft tend to roll into the turn during a turning stall, will, in combination with a nose down pitch, produce a nose low unusual attitude to the pilot. While the correct recovery technique from a conventional stall is to apply power as soon as the wings are unstalled, the standard recovery technique from a nose low unusual attitude is to close the throttle, roll wings level and then pull up (CASA, 2007).

Transition training

Purchase of the aircraft

The builder sold the aircraft due to medical issues that made it difficult for them to inspect and operate the aircraft and inhibited their ability to egress from the aircraft in an emergency. Consequently, the builder did not accompany any potential buyers on their trial flights. The inspections and trial flights of the aircraft occurred at Whyalla Airport, South Australia, and the syndicate that purchased the aircraft were the second interested buyers.

The builder reported that the first interested buyer had about 800 hours experience on slower aircraft, which included experimental kit-built aircraft. The buyer conducted a trial flight accompanied by a more experienced pilot who advised them against the purchase due to the performance difference from their previous aircraft. The accompanying pilot reported to the builder that the buyer was used to flying 80 kt aircraft, not 130 kt aircraft.

The syndicate that purchased the aircraft consisted of a recreational pilot certificate (RPC) holder and 2 Recreational Aviation Australia (RAAus) instructors. The instructors each held a CASA-issued recreational pilot licence (RPL) with navigation endorsement, and one of them was the accident pilot. They arrived together at Whyalla Airport in another light aircraft as the second prospective buyers. 

The syndicate conducted several trial flights at Whyalla, and the builder briefed them on the aircraft logbook and the POH but could not recall the specific details of what was covered. The builder believed the syndicate members were going to study the POH the night before their departure from Whyalla and the builder made themselves available the following day to answer any questions but could not recall if any were asked. The syndicate members signed the sale agreement on 5 November 2024 and departed from Whyalla with the aircraft on 6 November. 

The builder had no recollection of discussing the aircraft’s banked stall characteristics with them and had never received such a brief themselves in the past when introduced to a new aircraft. They did not advise the syndicate to seek transition training or recommend aerial work exercises as part of their familiarisation process. The builder was aware that 2 of the syndicate members held instructor qualifications with RAAus in addition to CASA licences. Therefore, the builder (who was not an instructor themself) did not think it was necessary to advise them about flight training matters.

One of the syndicate members was concerned about the aircraft’s centre of gravity with rear seat passengers and they agreed to have it reweighed before conducting any of their own verification flights. This was done at West Sale Airport on 14 November 2024, and no significant changes were recorded by the weight and balance organisation.

As the aircraft was in the single-engine class rating of less than 1,500 kg, the syndicate’s RPL-qualified pilots were able to fly the aircraft without additional flying training or qualifications. The ADS-B data history for the aircraft revealed about 7.7 hours were flown by the syndicate from 4 November 2024 until the accident flight, which included 4.5 hours of ferry flights from Whyalla to Moama, New South Wales, and from Moama to West Sale. There were also several check flights associated with rectifying a blocked fuel strainer. While the accident pilot had received dual transition training for other aircraft, which included the Bristell and Pitts Special, this was not undertaken on the accident aircraft.

One of the syndicate members reported that they didn’t think the pilot had the opportunity to do any aerial work exercises in the aircraft before the accident and they suspected that the pilot may not have appreciated the heavier aircraft, in which they had low flying hours. The other syndicate member reported that the pilot had limited flying experience in the aircraft and suspected that the pilot did not understand the risks of what they were doing with respect to steep turns, load factor and the associated effect on stall speed.

CASA flight testing and training advice

CASA AC 21.4(2) included recommended safety precautions for the flight-testing phase, emphasising that:

  • a graduated process of familiarisation should be followed, starting with the ground handling characteristics of the aircraft before attempting flight operations
  • emergency equipment and personnel should be available before the first flight
  • ‘Violent or aerobatic manoeuvres should not be attempted until sufficient flight experience has been gained to establish that the aircraft is satisfactorily controllable throughout its normal range of speeds and manoeuvres.’

The minimum qualifications required for the Phase 1 flight testing was a CASA-issued private pilot licence (PPL) with the appropriate endorsements.

CASA AC 21.4(2) also stated that ‘Flight training will be permitted under certain circumstances, i.e. type endorsement training and training given in the aircraft to its owner.’ A separate section addressed the maintenance aspects for new owners, which prohibited them from certifying for maintenance, and that it must be certified by a Licenced Aircraft Maintenance Engineer (LAME) when no longer owned by the builder. However, there was no recommendation for new owners to seek transition training or for designers or builders to recommend buyers conduct transition training.

ATSB aviation research investigation

The ATSB aviation research report 

AR-2007-043(2) (4.26 MB)

Amateur-built aircraft Part 2: Analysis of accidents involving VH-registered non-factory-built aeroplanes 1988-2010, was published in 2013. It included findings related to the accident and injury rates (with implications for the crashworthiness of these aircraft) and the experience of pilots involved in these accidents, as follows:

Amateur-built aircraft had an accident rate three times higher than comparable factory-built certified aircraft conducting similar flight operations between 1988 and 2010. The fatal and serious injury accident rate was over five times higher in amateur-built aircraft, in particular due to relatively more serious injury accidents. 

The pilots of amateur-built aircraft involved in accidents were significantly more experienced overall than factory-built aircraft accident pilots. However, they were significantly less experienced on the aircraft type that they were flying at the time of the accident.

A quarter of accidents were from loss of aircraft control.

The safety action section of the report included initiatives from the Sport Aircraft Association of Australia (SAAA), as follows:

Working with the Civil Aviation Safety Authority (CASA) to provide a legal framework for better training in amateur-built aircraft.

Working with CASA to allow a legal framework for suitably qualified pilots to give instruction in amateur-built aircraft both for the aeroplane flight review (AFR) and transition training for pilots (post-phase one).

The SAAA subsequently produced a Flight Training and Safety Manual supported by their Flight Safety Advisor program. However, a pilot operating an experimental aircraft needed to be a member of SAAA to access these resources.

Federal Aviation Administration advisory circular

In 2012, the United States National Transportation Safety Board published a safety study on The Safety of Experimental Amateur-Built Aircraft (NTSB/SS-12/01). Their study found that pilots who did not seek training were over‑represented in accidents, and that accidents involving loss of control could be reduced with transition training. This led to a recommendation for the FAA to develop resources for transition training and encourage builders and new owners to complete the training.

In 2015, the FAA published AC 90-109(A) Transition to unfamiliar aircraft. The purpose of the FAA AC was ‘to help plan the transition to any unfamiliar fixed-wing airplanes, including type-certificated (TC) and/or experimental airplanes.’ The AC stated that ‘accidents resulting from loss of aircraft control or situational awareness frequently result from pilot unpreparedness for challenges presented by the aircraft’ and provided recommendations for training experience based on aircraft performance and handling characteristics. It contained an extensive section on stall characteristics, which included the following points:

There are no rules for stall behavior with experimental airplanes.

Some experimental airplanes can be flown in a carefree manner with the stick all the way back, while others can depart controlled flight dramatically without any perceptible warning.

Since amateur-built airplanes are built by individuals, there can be a wide variation in the stall behavior of identical models.

Receive training in your airplane on stall avoidance and recovery from a qualified instructor, preferably with recent experience in the make and model.

Periodically practice stall avoidance, entry, and recovery at a safe altitude after you have received enough instruction to feel comfortable. Stall recognition and recovery should not be self-taught. Your first experience should not come from an inadvertent stall that catches you by surprise.

The appendices of the FAA AC provided a list of families of aircraft, based on their characteristics, with examples of experimental aircraft within each family. The accident aircraft was described to the ATSB as being responsive by the builder and very responsive by one of the syndicate members. Appendix 3 of the FAA AC was for aircraft with rapid flight control response, and it included the following information:

There are many more experimental airplanes that may look more like type-certificated (TC) airplanes, but they actually have light control forces and/or very quick maneuvering response. The hazard of light forces and rapid response is that without some level of training, the pilot may over-control the airplane.

Best Training. The best training is accomplished in the specific airplane the pilot intends to fly with a well-qualified instructor who has recent experience in the specific make and model.

In this case, the accident pilot had conducted transition training on the Pitts Special aircraft with an instructor who also had experience with the Morgan Cougar Mk 1 aircraft, though not the accident aircraft. The instructor’s experience with the Morgan Cougar included flying them and modifying them to improve their handling qualities. This offered the accident pilot an opportunity to undertake transition training for the Morgan Cougar Mk 1 that would have been consistent with the ‘best training’ model recommended in FAA AC 90-109(A).

Crashworthiness and survivability

Occupant positions and injuries

The seating configuration during the flight was the pilot in the front left seat, a passenger in the front right seat and a second passenger in the rear right seat. A full autopsy was conducted on the pilot, and a computed tomography scan and external examination was conducted on the 2 passengers at the Victorian Institute of Forensic Medicine. Toxicology analysis of blood was conducted for all occupants.

The examinations for all occupants revealed extensive non-survivable blunt force trauma injuries to the head, chest and lumbar spine. Examination of the pilot indicated that they were deceased prior to the fire. Toxicology results found no ethanol, common drugs or poisons, and carboxyhaemoglobin (an indicator of carbon monoxide exposure) was not detected.

CREEP methodology

The CREEP methodology used for analysing the crashworthiness and survivability of aircraft accidents is based on:

  • Container – maintain a liveable volume
  • Restraint – retain the occupants in their seats and the seats to the airframe
  • Energy attenuation – minimise the transmission of forces to the occupants
  • Environment (local) – minimise the lethality of the cockpit and cabin to flailing injuries
  • Post-crash factors – egress and minimise the risk of drowning, fire and fumes.
Container

The occupied cabin area of the aircraft was visible, though significantly damaged from fire and the underside compromised from the ground impact. The outline of the cabin was discernible and displayed dynamic deformation of the structure supporting the front seats and the main spar located underneath the front seats, which is discussed further in the following sections.

Restraint

The pilot and front right seat passenger were ejected from their seats during the accident, and their seatbelt latch plates were found separated from their respective buckles. The rear seat occupant appeared to have remained restrained and was found in the rear right seat location with their seatbelt latch plate attached to the buckle. The pilot was seen wearing a 3-point harness in videos taken during the accident flight. Therefore, it was considered very likely that all 3 occupants were wearing their seatbelts.

According to the build log, the front seats were from a Toyota Prado motor vehicle, and the seatbelts were connected to the seat mounts and airframe with their shoulder straps extending from centre to outboard, where the buckles were located. Regarding seatbelts, AC 21-4(2) para 7.3 stated:

It is strongly recommended that US [United States] FAA [Federal Aviation Administration] Technical Standard Order (TSO) approved or equivalent seat belts be installed along with approved shoulder harnesses. 

According to the build log, the builder conducted load testing of the seat belts in accordance with FAA AC 23-4 Static strength substantiation of attachment points for occupant restraint system installations. This involved the application of a simulated 4G load (400 kg) downwards and forwards to test the seats and seatbelt attachments, which they passed. The TSO specified the minimum performance standards were those in the Society of Automotive Engineers Aerospace Standard AS 8043 (1986), which included the following information:

Pelvic Restraint: A torso restraint system shall provide pelvic restraint whether or not an upper torso restraint is used. Pelvic restraint shall not incorporate emergency locking retractors (inertia reels).

Release: A torso restraint system shall be provided with a single buckle having a single motion release which is readily accessible to the occupant to permit easy and rapid egress by the occupant from the assembly. The buckle release mechanism shall be designed to minimize the possibility of inadvertent release.

A review of car and aircraft seatbelt images revealed a general difference between the design. Car seatbelt latch plates are threaded through the strap connected from the shoulder to the pelvic anchor point on the shoulder strap side. The inertia reel applies the tension, and emergency locking under acceleration, when the latch plate is inserted in the buckle on the opposite side. Therefore, the pelvic restraint (lap belt) incorporates an inertia reel because it is part of the upper torso restraint mechanism. 

The aircraft builder confirmed that this was the design of the front seatbelts fitted to the aircraft and that they were probably car seatbelts. The inertia reel was located at the shoulder anchor point on the inboard side of the seats and the shoulder strap extended down to the inboard pelvic anchor point with the latch plate threaded through the strap. The inertia reels at the shoulder anchor points provided the tension and emergency locking under acceleration for the front seat occupants.  

Seatbelts can fail due to overload, which is why strength tests are conducted, and they can also fail to perform a required function, such as restrain the occupant during a collision. Roberts et al. (2007) described 3 known failure modes associated with car seatbelt design as follows:

  • inadvertent unlatching when the buckle is unlatched due to occupant flailing contact with the release button during an accident
  • false latching when the buckle fails to engage completely, but gives the user the impression that it is properly fastened due to its partial engagement
  • inertial unlatching when the buckle unlatches due to inertial forces resulting from impacts and the associated impulse accelerations during planar collisions and rollovers, which is an example of a component failing to perform a required action.
Energy attenuation

All 3 occupants had fractures of the lumbar spine and the 2 front seat occupants both had crush fractures of the fifth lumbar (L5) vertebra. According to Shanahan (2004) light fixed‑wing aircraft provide little crushable structure to attenuate collision forces. However, 2 areas where energy attenuation can be incorporated into the design are the landing gear and seating. The main landing gear for the Morgan Cougar aircraft was a rigid single-piece structure with the wheel axles attached to the structure. It separated on impact and there were no oleos for energy attenuation incorporated into the design. 

The rear seats were upholstered 4 mm plywood mounted to the cross-members. The front seats were car seats, which were attached to cross-members and had the main wing spar underneath them. The front right seat pan was found collapsed onto the wing spar and the left seat pan had separated and was found forward of the front seat frame structure. None of the seats incorporated any recognisable form of energy attenuation.

According to Stech and Payne (1969), the G-loading strength of the L5 vertebra for a 160 lb (72.6 kg) male is around 25G. The 25G limit was acknowledged by Shanahan (2004) with the following caveat:

However, poorly designed seats can produce spinal fracture in impacts as low as 8-10G. Typically, spinal fractures in low to moderate velocity crashes are caused by mounting seats above rigid panels or other non-frangible objects such as batteries and from mounting relatively rigid seats directly on bulkheads or over beams. In the first case, seats collapse onto unyielding objects causing the occupants to experience excessive vertical accelerations. In the latter case, rigid bulkheads or structural members transmit excessive forces from the ground directly to the seat occupants. 

According to Taylor and Moorcroft (2023) from the FAA Civil Aerospace Medical Institute, special energy attenuating seats are used to provide a controlled deceleration over a vertical stroking distance to keep aircraft crash loads within human tolerance. While there are many methods to achieve a controlled deceleration, some of the simplest and lightest methods include collapsible sheet metal boxes for the seat pan structure and/or the use of rate sensitive foams for the seat pan cushion.

CASA AC 21.4(2) para 7.3 recommended safety considerations for the design of the cockpit and seatbelts to reduce injuries to the pilot and passengers in the event of an accident. It also strongly recommended the use of FAA TSO seatbelts and shoulder harnesses. However, there was no recommendation for the designer or builder to consider energy attenuation for the occupants, specifically the energy attenuation of seating.

Environment (local)

The local environment was not considered to be a significant contributing factor in this accident due to the severity of the occupants’ spinal injuries (indicative of excessive vertical forces) and because the front seat occupants were ejected from their seats. In addition, CASA AC 21-4(2) para 7.3 recommended the ‘delethalization’ of the cockpit as follows:

The design of the cockpit or cabin of the aircraft should avoid, or provide for padding on, sharp corners or edges, protrusions, knobs and similar objects which may cause injury to the pilot or passengers in the event of an accident.

Post-crash factors

The aircraft was designed with a main fuel tank located between the engine firewall and the instrument panel. This made it susceptible to crushing forces in an impact and presented a risk of fuel spray onto the occupants and onto the engine as an ignition source, which occurred in the accident. The fire damage to the aircraft was centred on the cabin and engine area with die-back of the grass evident in a diamond pattern from the initial impact to the point of rest.

The builder modified the original design to incorporate wing fuel tanks in the design, located aft of the main wing spar. The modified wing tanks were not compromised by the collision. The importance of fuel tank location on post-crash survival was described in Johnson et al. (1980 and 1989) Aircraft Crash Survival Design Guide Volume V – Aircraft Postcrash Survival as follows:

The location of the flammable fluid-carrying tank in an aircraft is of considerable importance in minimizing the postcrash fire hazard from a tank installation. The location must be considered with respect to occupants, ignition sources, and probable impact areas.

Greater distance between occupants and fuel supply tends to increase escape time in the event of a fire because it reduces the likelihood of fuel entering the occupied area. Also, the tank should be kept away from probable ignition sources… Another important consideration is the location of tanks with respect to probable impact damage. Accident histories show repeated tank ruptures and consequent fires…, indicating the tank’s high degree of vulnerability to damage from surrounding structures.

As much aircraft structure as possible should be allowed to crush before the tanks themselves are exposed to direct contact with obstructions.

CASA AC 21.4(2) para 7.4 recommended reducing the risk of fire hazard, and the inclusion of a fireproof firewall between the engine compartment and the cabin. However, it did not recommend or advise on how to incorporate crashworthiness into the design of the fuel system.

Pilot information

Qualifications

The pilot held a:

  • Recreational Pilot Licence (Aeroplane) (RPL-A), issued by CASA on 6 August 2024, with a single-engine aeroplane class rating and manual propeller pitch control endorsement
  • Class 2 aviation medical certificate, issued in June 2024.

The RPL licence was granted in recognition of the pilot holding a recreational pilot certificate (RPC) with RAAus in accordance with Civil Aviation Safety Regulation (CASR) 61.480. In addition, the pilot held an RAAus-issued instructor rating and had accumulated 506.8 hours according to their last logbook entry, dated 7 August 2024. 

Flight training
Recreational aviation flight training

The pilot started flying training with RAAus at Adventure Flight Training (AFT) school in Moama, New South Wales, on 11 April 2022 for their RPC. The pilot passed their RPC flight test on 20 September 2022, and was endorsed with passenger carriage later in 2022, and with navigation and formation in 2023. All flight tests and endorsements were conducted and certified by the AFT chief flying instructor (CFI).[8] 

On 8 May 2023, the pilot started their RAAus instructor training at AFT and passed their instructor flight test at Bendigo, Victoria, on 7 July with an external testing officer. The pilot started delivering instructional flights at AFT on 16 July 2023.

On 19 December 2023, the pilot passed their senior instructor flight test with the AFT CFI and on 3 January 2024, the CFI endorsed the pilot’s logbook with the entry ‘meets the requirements for senior instructor rating iaw RAAus syllabus of flight.’ However, the pilot had not completed the theory exam requirement to be a senior instructor and their rating for senior instructor was not issued by RAAus.

General aviation flight training

The pilot’s logbook had entries for the following general aviation training flights in 2024:

  • On 5 June, the pilot started dual flying training in the Pitts Special aerobatic biplane at Latrobe Valley and recorded 0.7 hours.
  • On 6 June, the pilot successfully completed a flight review of 2.5 hours duration with a controlled airspace/aerodrome endorsement in a Cessna 152 (a flight review was required to exercise the privileges of a CASA RPL, which was issued in August).
  • On 6 June, the pilot recorded a further 0.5 hours of dual flight training in the Pitts Special.
  • On 1 July, the pilot recorded 3.1 hours of dual aerobatics training in the Pitts Special.

While the ATSB was informed that the pilot’s flying in the Pitts Special was for the purpose of an aerobatics endorsement, the flight training school (FTS) where the pilot conducted their RPL flight review did not have them enrolled for an aerobatics endorsement. In addition, CASA reported that they did not have an aerobatics endorsement record for the pilot. The ATSB reviewed the pilot’s flight training records for the Pitts Special and concluded that the activities were consistent with transition training onto the Pitts Special, which included stalls and spins, and not an aerobatics course.

The ATSB spoke to a member of a local aerobatics team, who knew the accident pilot, and they confirmed there had been discussions about the possible use of the accident pilot to ferry their Pitts Special aircraft to an airshow at the end of August 2024. However, the pilot did not meet the minimum experience requirements for insurance purposes and the plan was cancelled.

On 9 November 2024, a general aviation flight instructor and RAAus CFI conducted a check flight with the accident pilot at the Echuca Aero Club in the club’s Piper Archer aircraft. This was a requirement to be able to hire the aircraft. The instructor conducted a standard aerial work check flight with the pilot and did not identify any deficiencies in flying skills. 

Theory examinations
Recreational aviation theory examinations

The pilot’s logbook had a record of aviation theory examinations (exams) in accordance with the following table:

Table 3: Pilot's theory exams

DateTheory exam
31 May 2022Pre-solo
20 June 2022Air legislation
29 June 2022Basic aeronautical knowledge
13 August 2022Radio
13 August 2022Human factors
4 December 2022Navigation theory [includes meteorology theory]
21 May 2023RAA instructor rating

The AFT CFI was recorded as the delegate for all of the pilot’s theory exams in their logbook. Another AFT instructor reviewed the exams recorded in the pilot’s logbook and reported that:

  • the theory exams were conducted online and unsupervised
  • the correct answers to all questions were revealed after the first attempt so that any incorrect answers could be corrected with a second attempt
  • no knowledge deficiency reports were provided. 

The ATSB reviewed the software used by AFT to conduct the theory exams and found that the settings allowed multiple attempts and revealed all the correct answers in a report provided to the candidate.

PPL(A)-equivalent examination

To become a senior RAAus instructor, a candidate must pass either the RAAus PPL(A) (aeroplane) equivalent exam, or the CASA PPL(A) exam. The RAAus PPL(A)-equivalent exam was a multi-choice exam in which each question had 4 options to select from. 

On 3 January 2024, RAAus received the pilot’s application for upgrade to senior instructor, certified by the AFT CFI as the examiner, with a copy of the pilot’s instructor exam from 21 May 2023 attached. This exam was completed using the AFT online system. The ATSB did not find a record of the initial response to this application but based on the available evidence, it is likely that RAAus staff identified that the incorrect exam had been submitted in support of the application and reported this to the AFT CFI.

On 12 January 2024, the pilot completed the RAAus PPL(A)-equivalent exam using the AFT online system and a pass mark of 94% was recorded. However, the marking rubric for this exam had not been provided to AFT as this exam was marked by RAAus staff. As no marking rubric was provided, the AFT exam software provider had set answer ‘A’ as the default correct answer to all questions for this exam and notified the AFT CFI of this action. The accident pilot had selected answer ‘A’ to 47/50 questions.

When a copy of the pilot’s exam was provided to RAAus and re-marked it was identified that the actual result for the accident pilot’s exam was 26% (13/50).

On 29 January 2024, RAAus sent an email to the AFT CFI to report the result and express their concern about the result and the process used to mark the exam. They also notified the CFI that the pilot’s application for senior instructor would not be processed and that the pilot would:

  • need to complete another PPL(A)-equivalent exam
  • continue to require direct supervision (in-person) when instructing.
Re-attempt of PPL(A)-equivalent exam

On 24 February 2024, an external CFI[9] supervised the pilot’s re-attempt of the RAAus PPL(A)-equivalent exam at Moama Airfield. This CFI reported that the pilot arrived with a copy of the exam paper questions and that after the exam was completed, the CFI submitted it to RAAus for marking. They did not follow up as to how the pilot obtained a copy of the exam paper. Instead, they passed the information on to RAAus, who also did not enquire how the pilot had obtained the exam questions.

The AFT CFI reported that they believed the pilot had taken a blank answer sheet and not a copy of the exam paper to the exam. The answer sheet is a document with a table for the candidate to annotate the answer to each question. However, the pilot annotated their answer to each question on a copy of the exam paper, not an answer sheet, and it was this exam paper that was certified by the supervising external CFI and submitted to RAAus for marking.

The second exam result, marked by RAAus, was 76% (37/50), which was less than the required pass mark of 80%. This was the same exam paper, with the same questions and answers, that the pilot had previously attempted in January.

Pilot exam outcomes

The RAAus PPL(A)-equivalent exam included 3 questions about aerodynamic stalling, including about factors that change the 1G level flight stalling speed. For the pilot’s attempt on 12 January 2024, the pilot selected answer A to all 3 questions and they were all marked correct. However, 2 were correct and 1 was incorrect according to the RAAus marking rubric. 

For the pilot’s re-attempt on 24 February 2024, the pilot changed all 3 answers with the result that 1 was correct and 2 were incorrect. While the pilot correctly answered one question that the stall speed increases in a steep turn, they incorrectly answered another question about the relationship between angle of bank, load factor and stall speed.

On 29 February 2024, RAAus sent an email to the AFT CFI to report the failed second exam attempt by the pilot. On this occasion they stated:

Of more concern is the type of errors made, which include several stalling questions and poor Part 91 regulatory understanding among other items. I understand you have already spoken to [the pilot] and advised [them] of this, but I will call [them] to discuss as well.

RAAus expressed concern about the reported preparation process of reviewing current exam papers which ‘could be considered an attempt at rote learning of questions rather than developing a deeper understanding of the underpinning knowledge required of a RAAus Senior Instructor.’ RAAus reiterated previous comments they had made, that the pilot should re-attempt the exam ‘only after appropriate study of aviation textbooks and regulatory references.’ 

The ATSB noted other incorrect questions of concern for an instructor, in addition to the questions about stalling and Part 91 regulations identified by RAAus. They included knowledge of the instruments affected by a blocked static pressure system and the interpretation of an aerodrome weather forecast. The questions about stalling and pressure instruments were in the RPC syllabus, and knowledge of weather forecasts and reports were in the navigation endorsement syllabus. At the time they were attempting the PPL(A)‑equivalent exam, the pilot was delivering instruction for both syllabi. 

The ATSB queried RAAus as to whether they had considered imposing any restrictions or limitations on the pilot’s instructor rating after the second exam result, noting their concern about the pilot’s knowledge deficiencies. RAAus responded that by not processing the pilot’s upgrade to senior instructor, the pilot was required to remain under the direct supervision of a CFI, which was their risk management strategy until the pilot’s knowledge deficiencies could be addressed.

A copy of the 29 February 2024 email sent from RAAus to the AFT CFI appeared on the accident pilot’s RAAus member file. However, the pilot’s member file did not include any record of a follow-up about the exam result or progress towards completing any further attempts. Phone call records indicated that a follow-up from RAAus to the pilot did occur on 29 February 2024, but the details of the call could not be recollected. 

Commercial pilot theory examinations

Instead of studying the CASA PPL theory, the pilot started studying for their CASA aeroplane commercial pilot licence (CPL-A) theory component, which consisted of 7 exams. The pilot attempted and passed their first CPL-A exam on the subject of aircraft general knowledge (CSYA) with a result of 93% on 10 July 2024. The knowledge deficiency report (KDR) had 3 items listed, which indicated a score of 37/40 questions answered correctly. 

On 25 July 2024, the pilot attempted, and failed, the CPL-A aerodynamics exam (CADA) with a result of 63%. The KDR had 15 items listed, which indicated a score of 25/40. The incorrect answers were from a range of topics that included 2 questions on stalling. The 2 incorrect answers on stalling included the effect of using ailerons when approaching and during the stall, and the effect of manoeuvring on the level flight stall indicated airspeed.

On 7 August 2024, the pilot re-attempted the CPL-A aerodynamics exam and passed with a result of 75%. There were 10 items in the KDR, which indicated a score of 30/40. The 2 CPL-A aerodynamics exam KDRs included 3 errors in each of the topics of stalling, stability and control (longitudinal, lateral and directional), and control surface feature. Other items on the KDRs included:

  • the lift and drag formulae
  • dynamic pressure
  • basic forces on an aircraft in level flight
  • factors affecting turn performance
  • angle of attack required for various flight situations.

Risky flying behaviour and counselling

Background

During the investigation the ATSB interviewed the AFT CFI and associates of the pilot, including:

  • 2 other instructors from AFT
  • 3 AFT RPC graduates from Moama
  • the airport operator, who was also a local aerobatic pilot
  • a local general aviation instructor and RAAus CFI. 

Each of them recalled experiencing instances of risky flying behaviour involving the accident pilot, or knowledge of this behaviour and counselling. The ATSB also interviewed RAAus staff to determine if they had received any reports of the pilot engaged in risky flying behaviour.

Risky flying behaviour

A fellow AFT instructor from Moama, who was also a syndicate member in the purchase of the aircraft, reported that the accident pilot had a history of conducting low and slow steep turns. While they had steep turn flying training experience themselves, they were accustomed to entering a steep turn from cruise airspeed and were concerned about the pilot’s practice of entering steep turns at slow speed. They had experienced this personally as a passenger with the pilot, as they were co-owners of a Jabiru aircraft, and were aware of reports of similar instances from the pilot’s students. 

The instructor had also witnessed the pilot conduct dumbbell turns in the circuit with students in light wind conditions. This involved the pilot conducting a reversal turn shortly after take-off to land on the reciprocal runway for student landing practice, rather than completing a full circuit between landings. They suspected the pilot had learned this from the AFT CFI as they had previously witnessed the CFI conduct this same manoeuvre in light wind conditions.

The other member of the syndicate in the purchase of the aircraft was an AFT RPC graduate from Moama in 2024. While they had conducted their RPC at AFT, they did not fly with the pilot until near the end of their flying training, at which point they were doing most of the flying. They did not observe any risky flying behaviour from the pilot but were advised by others at the school that the pilot had previously received counselling for risky flying behaviour.

Another fellow AFT instructor reported that the pilot could fly an aircraft well but ‘pushed the limits’. They recalled an example of a private flight in the pilot’s Jabiru, in which the pilot held the aircraft on the runway as it accelerated significantly beyond the take-off speed and then performed a pull-up into a steep climb. They stated that they immediately asked the pilot to lower the nose.

During the same flight, the pilot reportedly conducted low-level steep turns and a swooping manoeuvre over a friend on the ground. The instructor reported that they repeatedly verbally intervened throughout the flight, and that they didn’t like how the pilot was flying and asked them to stop and return to the airport after about 30 minutes.

Another AFT RPC graduate from Moama reported that during a local recreational flight on 1 November 2024 in the pilot’s Jabiru, which had a stall airspeed of 45 kt, the pilot conducted a low-speed steep turn overhead a friend driving a tractor. The combination of low speed and steep angle of bank made them feel uncomfortable and they assessed that the aircraft did not have sufficient lift for the manoeuvre. The pilot reportedly noticed their discomfort and told them not to worry as they were still at 60 kt (airspeed). ADS-B data recorded a minimum groundspeed of 57 kt during this turn. 

The AFT graduate had previously conducted their RPC pre-check flight with the pilot in August 2023, which included stalls and steep turns in a Topaz aircraft with a stall speed of 44 kt. They reported that the steep turns demonstrated by the pilot then were at least 60° angle of bank, which made them feel uncomfortable and they noted that the pilot appeared to be pushing the aircraft to its limits in a confident manner.

Another RPC graduate interviewed by the ATSB had transferred from the CASA-issued PPL system to the RAAus-issued RPC system and completed their flying training with AFT at Moama. Three days prior to the accident, the pilot invited them on a local area private flight in the accident aircraft. During the flight, the pilot reportedly turned off the transponder and conducted a low-level, high-speed pass over a friend’s house, followed by a wingover.[10] The pilot then demonstrated the responsiveness of the aircraft by conducting a series of level steep turns. The witness reported that the angle of bank was more than 60° and felt like 70–75°, which they described as ‘knife-edge stuff’.

Counselling

The Moama Airfield operator and local aerobatic pilot knew the accident pilot from the AFT school at Moama. The operator had taken the pilot flying in their own aerobatic aircraft and found them to be a very enthusiastic young aviator. Their impression was that the pilot was attracted to the sport aviation side of the industry. In September 2024, the operator was contacted by the AFT CFI about reports of unsafe flying, which included instances of low-level flying and manoeuvring overhead a local football match. 

The airfield operator investigated the reports and found that it was likely the accident pilot who had been conducting steep turns overhead the Moama football ground during a match. They approached the pilot in late September and stressed the need for them to fly respectfully and emphasised staying above the minimum requirements and not to orbit overhead properties. They thought that the pilot accepted the counselling in a positive manner.

A local general aviation instructor and RAAus CFI, who was involved in establishing an FTS near Moama, also received a report that the pilot had been observed conducting aerobatics overhead a local football match. They responded to the reporter that the pilot would not be allowed to instruct for the school with that flying behaviour. The pilot subsequently contacted the CFI and visited them on the afternoon of 1 November 2024 to discuss the reported incident. The pilot was reportedly adamant that they had not conducted aerobatics overhead the football match but acknowledged that they had conducted steep turns overhead the match. 

At the time of the visit, the CFI had also heard reports that the pilot had been conducting dumbbell turns in the circuit with students. Consequently, they used the visit from the pilot as a counselling opportunity, specifically pointing out that a solo student might try to imitate the pilot’s flying and lose control of the aircraft. The CFI thought that the pilot accepted the counselling in a positive manner. 

The AFT CFI reported to the ATSB that prior to the cessation of AFT operations in August 2024, they had regularly engaged in coaching and counselling sessions with the pilot. However, after they ceased AFT operations, they received multiple calls from members of the local community raising concerns about a Jabiru aircraft flying in a manner perceived to be unsafe. While the pilot was not confirmed, the context of the reports led them to believe that the flights were operated by the accident pilot.

The AFT CFI reported that several weeks prior to the accident they had a candid conversation with the pilot and urged them to continue flying safely and responsibly. They stressed that the pilot needed to be even more alert and disciplined without direct oversight. However, as they were no longer responsible for formal oversight of the pilot, they elected to contact others who could potentially mentor the pilot. This included the Moama Airfield operator.

RAAus advised the ATSB that, prior to the accident, they had not received any reports or complaints about the pilot’s flying behaviour, nor were they aware of the pilot receiving any counselling. However, following the accident, they received a report from the AFT CFI that they had been managing the pilot’s behaviour. 

RAAus interrogated their occurrence management system for any complaints involving unidentified aircraft and/or pilots in the Moama region and found none. They stated that if they had received a report of an instructor involved in risky flying behaviour, there would have been a ‘fairly swift response’ because they would not want the individual working as an instructor, and potentially indoctrinating students to that behaviour.

Recreational Aviation Australia

Structure

Recreational Aviation Australia (RAAus) is a CASR (Civil Aviation Safety Regulation) Part 149 approved self-administering aviation organisation (ASAO). In 2025, RAAus had 14–15 full time employees in the following areas:

  • flight operations
  • maintenance and airworthiness
  • safety
  • finance
  • information technology
  • administration. 

According to the RAAus website, they had 10,000+ members in 2025, and were the largest administrator of pilots, maintainers and aircraft in Australia.

RAAus were authorised by CASA to conduct their activities in accordance with their approval certificate, the Part 149 Manual of Standards and their approved Part 149 Exposition. As a sport aviation organisation, RAAus was oversighted by the CASA Sport and Recreation Aviation Branch (CASA Sport). 

The structure of RAAus, with their key personnel in accordance with their Exposition, is depicted in Figure 11.

Figure 11: Recreational Aviation Australia structure

Recreational Aviation Australia structure

Source: Recreational Aviation Australia

The RAAus Part 149 approval certificate authorised RAAus to administer several aviation administration functions and their sub-functions. The function of relevance to the ATSB’s investigation was Part 149 Flight Training Organisations:

Administer a person that conducts flight training, or flight tests, in relation to a Part 149 aircraft.

The sub-functions were listed as follows:

1. Assessing a person’s organisation, and its procedures, practices, personnel and facilities to determine whether the person is capable of conducting flight training, or flight tests, in relation to the aircraft

2. If satisfied as mentioned in paragraph 1, issuing an authorisation to the person to conduct the activities specified in the authorisation

3. Assessing whether a person to whom the ASAO has issued an authorisation continues to be capable of conducting the activities covered by the authorisation

4. Approving aeronautical examinations that may be conducted by a Part 149 flight training organisation to assess candidates undertaking flight training.

Flight training schools 

In 2025, there were about 160 RAAus flight training schools (FTSs). Student pilots, converting pilots and pilot certificate holders could only undertake flight training with an RAAus FTS approved by the RAAus Head of Flight Operations (HFO). An FTS could only operate when a CFI was approved in accordance with the RAAus flight operations manual (FOM). The FOM also required FTS instructors to be directly supervised by the CFI, or another senior instructor approved by RAAus, with indirect (remote) supervision of senior instructors permitted.

In February 2022, RAAus published version 1.1 of their Recreational Aviation Advisory Publication on instructor supervision requirements. This was published to address the enquiries RAAus had received from their members about the instructions in the FOM. Direct supervision of instructors was in-person and was required to be provided by the CFI or approved senior instructor. The intention of the direct supervision requirement was to ensure the supervisor was physically present at the location where the training was conducted to provide continuing mentoring and development for their instructors.

The CFI oversight responsibilities included 90-day check flights of their instructors and 12‑monthly check flights of their senior instructors, which were called standards and proficiency checks. To become a CFI, an individual was required to progress through the qualifications of RPC, instructor and senior instructor. A senior instructor could be appointed to supervise an FTS in the CFI’s absence if they met the requirements of the RAAus FOM and were approved by the HFO. 

Flight training school exams

Each RAAus FTS qualification had a flight test and one or more associated theory exams. The theory exams were written by RAAus and sent to the FTS CFIs via email. For each exam, answer sheets were provided for the candidates to record their answers to a selection of multiple-choice exam questions. The syllabi for the theory exams were published in the RAAus syllabus of flight training. 

Before accessing the exams, each CFI was required to sign a declaration acknowledging that they had read the conditions of use and would ensure the necessary processes had been implemented at their FTS. The declaration included:

Multiple Choice Examinations. These are not to be distributed and/or reproduced electronically and must be stored securely. 

The FTSs were provided with the marking rubric for each exam and were responsible for marking, filing and recording of the results of each exam. The exception to this was the upgrade from instructor to senior instructor for which the exam requirement was either the CASA PPL(A) exam or the RAAus PPL(A)-equivalent exam. RAAus marked the PPL(A)-equivalent exam and did not provide the FTSs with the marking rubric for it. Prior to 2023, RAAus did not require proof of completion of any exams. In 2023, the RAAus instructor upgrade form was amended to require proof of exam completion for the upgrade to senior instructor only. 

Flight training school oversight 

The RAAus Exposition included an audit program to fulfill sub-functions 1 and 3 of their Part 149 Flight Training Organisations function. Sub-function 1 was for the assessment to issue FTS status while sub-function 3 was for the monitoring of the FTS, which was required to be conducted at least once in every 2-year period.

The RAAus audit activities included:

  • desktop
  • onsite
  • special purpose audits
  • health checks
  • periodic reviews
  • renewals.

The CFI was the only individual from the FTS who was required to be in attendance for an onsite audit and was interviewed as part of the audit process. Other staff members could be interviewed on an opportunity basis, but students were not interviewed as part of a routine audit. 

Given the large number of FTSs and the limited number of RAAus staff available for oversight, RAAus developed a risk and audit matrix to determine the type and frequency of audit activity. The matrix produced a performance indicator (PI) score for each authorisation holder. The RAAus audit manual provided the following statement for FTSs assessed as higher risk:

Where resourcing permits, authorisation holders who fall within the highest 10 PI [performance indicator] scores shall only be eligible for an on-site audit and should be scheduled within the following 6 months. 

When an authorisation holder within the highest 10 PI scores was scheduled for an onsite audit, the audit team would identify other authorisation holders within the local area who would also be audited during the visit.

Occurrence management system 

RAAus had an occurrence and complaints management system (OCMS) database supported by an occurrence and complaints handling manual (OCHM). According to the OCHM:

Any person may report a safety concern or confidential complaint relating to an RAAus member and aircraft. A confidential occurrence may be lodged through the RAAus Occurrence and Complaint Management System (OCMS).

Apart from those OC [occurrences] that are resolved immediately by front line staff, all OC will trigger an informal assessment.

An informal assessment will be made to obtain and assess sufficient information to determine the most appropriate course of action, including the possibility of a Safety Related Suspension [SRS] if a serious safety situation is indicated.

The OCHM described the SRS as follows:

Temporary suspension of a member’s privileges, through imposing an SRS, is a risk management strategy that will be considered if:

a. the potential risk (to self, other RAAus members, members of the public, the organisation or the effective conduct of the investigation) posed by the member continuing to fly, or maintain aircraft, is significant; and/or

b. the potential risk to others posed by the member cannot reasonably be managed in any other manner.

The AM [Accountable Manager], HAM [Head of Airworthiness and maintenance] or HFO may decide to impose an SRS on a member.

The OCHM provided the following examples of an SRS:

a. enhanced supervision requirements

b. temporary suspension of certificates

c. temporary revocation or restriction of privileges.

In accordance with CASR 149.425 and the RAAus Exposition, RAAus was required to submit a written report to CASA within 7 days of taking formal compliance or enforcement action. This was described in the RAAus formal inquiry process.

RAAus advised that mandatory notification to CASA was not required following an SRS because it was part of their informal assessment process and not their formal inquiry process. However, they could notify CASA of an SRS at their own discretion if they considered it prudent, although there was no continuing reporting requirement associated with this.

The outcome from an informal assessment could include a requirement for remedial action to be completed prior to lifting an SRS. If an individual’s membership lapsed with an active SRS, the requirements remained in place, flagged in their RAAus member profile, and were to be completed prior to exercising the privileges of their RPC if they decided to reactivate their RAAus membership.

Adventure Flight Training

Background

The AFT CFI became a member of RAAus in December 2008 and was issued with an RPC in December 2009, instructor rating in April 2017 and senior instructor rating in July 2018. On their senior instructor upgrade submission to RAAus, the examiner certified that the ground theory component was satisfactorily completed, although proof of completion of the ground theory was not required and not provided. Proof of a current medical certificate was required and provided. 

As previously described, the theory component for the upgrade to senior instructor could be met by either passing the CASA PPL(A) exam or submitting the RAAus PPL(A)‑equivalent exam for marking by RAAus. In the case of the AFT CFI’s senior instructor upgrade, RAAus reported that the answer sheet for the PPL(A)-equivalent exam was not received with the upgrade submission and that it was likely their administration staff believed that the CASA PPL(A) exam had been completed instead. The CFI reported to the ATSB that for their senior instructor upgrade, the RAAus PPL(A)‑equivalent exam was done, submitted and approved.

The CFI was issued with a certificate of approval for their FTS on 11 June 2019. This followed an FTS inspection report in May 2019 at the nominated location of Riddell Airfield (Riddell), Victoria, and was initially to provide training for the issue of an RPC. The first 3 RPC candidates were required to be independently assessed by an RAAus‑nominated examiner. 

In October 2021, RAAus issued the CFI with temporary approval for instructor training IT(T). This required the first 3 candidates for their instructor rating to be independently assessed by an RAAus-nominated examiner before the temporary approval could be lifted. In May 2022, RAAus conducted an onsite audit of AFT at Riddell. 

RAAus records indicated that on 6 March 2023, the primary location for AFT became Moama. In August 2024, RAAus imposed an SRS on the CFI, which suspended their CFI approval and senior instructor qualification. Subsequently, the CFI elected to cease the FTS operations and later sold AFT. 

Practices at Riddell Airfield 

As part of the investigation, the ATSB interviewed the AFT CFI, 2 AFT instructors who were peers of the accident pilot, and several AFT RPC graduates from Riddell and Moama Airfields, all of whom knew the CFI and the accident pilot. 

The interviews with those who had trained at Riddell indicated that AFT operations appeared to be consistent with the RAAus Exposition for an FTS, which was the situation when AFT was audited by RAAus in May 2022. One RPC graduate from Riddell reported that it was a more positive learning environment than they had previously experienced in general aviation.

The CFI would deliver the theory during the classroom lesson, then demonstrate the manoeuvre in-flight before handing over control and directing them how to fly the manoeuvre. Theory exams were paper-based using the exam papers provided by RAAus, which were supervised, marked and debriefed by the CFI. 

However, what also emerged from the interviews was a difference in the FTS practices between Riddell in the period 2019–2023 and Moama in the period 2022–2024.

Onsite audits 

In May 2019, RAAus conducted an initial FTS inspection at Riddell, and an FTS inspection report was completed by the RAAus delegate. No non‑compliances or rectifications were recorded on the report. At the time, there were no satellite flight training facilities and therefore the requirement for inspections of these facilities was recorded as not applicable on the report. 

The next onsite audit of AFT was conducted at Riddell by RAAus in May 2022, at which time Moama was recorded as a satellite facility. That audit only occurred by virtue of AFT being at the same airfield as another FTS at Riddell being audited due to their PI being in the top 10. RAAus reported that, prior to that audit, AFT was ranked about 20 based on their PI score. 

RAAus reported that during the 2022 audit they checked the records of student exam results but would not have checked the exam papers (answer sheets) themselves. One member of the audit team recalled a discussion with the CFI about the use of an online exam system as part of a broader discussion about how to improve the administration of the FTS. They did not believe an online exam system was in use, and they did not review or approve one. 

The 2022 audit report included a reference to checking exam results but no reference to the use, or discussion, of an online exam system. RAAus reported that they had declined requests by FTSs to use online systems because it conflicted with the CFI declaration to not distribute the exams in either electronic or paper form.

On review of the draft report, the CFI maintained that RAAus did approve their online exam system and that they demonstrated it to 2 of the auditors during the 2022 audit. They further reported that during the audit they reported that exams were completed and stored electronically and demonstrated this in accordance with the respective audit checklist item. However, the auditor’s annotation on the 2022 audit report next to this item indicated ‘Cloud based (Google Drive)’ and did not include reference to the online exam software platform.

The audit resulted in 2 required corrective actions and 5 observations with associated recommendations. The AFT CFI responded to the corrective actions required and observations, which were accepted by RAAus. A copy of the audit closure report with the accepted supporting evidence was sent to the CFI in August 2022. 

RAAus reported that, depending on findings, an FTS did not automatically move to the bottom of the PI score list after an audit. In this instance, because of the structure of AFT and the non-compliances identified during the audit, their rank moved from about 20 to approximately 100 (of about 160 FTSs at the time).

Chief flying instructor conduct

In May 2020, RAAus investigated a close proximity event involving the AFT CFI, which their risk matrix indicated was a potentially catastrophic event. The CFI denied involvement in the event and reportedly provided RAAus with a copy of their flight path history for the day of the incident. However, the RAAus investigation confirmed it was the CFI’s aircraft and that they were aboard at the time. RAAus subsequently issued a formal letter of reprimand to the CFI for not reporting the event and denying their involvement.

In August 2020, the initial cadre of AFT RPC candidates were ready for assessment, and an independent examiner was nominated by RAAus. The examiner assessed the first candidate and reported to RAAus that the flight component of the test went smoothly but the candidate’s theory knowledge was ‘not as good as it could have been’. The examiner recommended the candidate do further theory practice exercises. 

RAAus correspondence indicated that following the independent assessment of the first AFT RPC candidate, the CFI conducted the flight tests for the 2 other RPC candidates, instead of having them assessed by the nominated examiner as required. When RAAus challenged the CFI about this matter, they alleged that the examiner had lost control of the aircraft during the flight test with their candidate. This allegation was later challenged by the examiner and the CFI provided RAAus and the examiner with a retraction.

On review of the draft report, the CFI denied that they had made this allegation and reported that the student had told them the examiner was flying out of balance. Therefore, the CFI decided to request another examiner with experience on that aircraft type conduct the checks. 

In December 2020, RAAus lifted the RPC testing restriction on the CFI with an administrative assessment in place. This allowed them to conduct the flight tests for the recommendation of an RPC but required them to provide RAAus with each candidate’s completed training records when the RPC recommendation paperwork was submitted.

In November 2021, about a month after RAAus issued the CFI with their instructor training temporary approval (IT(T)), the CFI advised RAAus they were starting a full-time IT course at Moama Airfield. Like the first 3 RPC candidates, the first 3 candidates for the instructor rating were required to be independently assessed.

In April 2023, the CFI reported to RAAus that their first 3 instructor candidates had been independently assessed and requested removal of their temporary IT status. However, the examiner on this occasion (different from the previous RPC examiner discussed above) reported that the candidates were not prepared for their instructor briefing session despite the preparation advice the examiner had provided to the CFI for their candidates. 

The examiner also reported that there were additional administration preparation deficiencies, which led them to conclude that the CFI had not taken the time to check the process requirements. Consequently, in May 2023, RAAus notified the CFI that they would need to remain under a temporary IT approval status until a further 2 candidates could be assessed by the same examiner. The RAAus records indicate that the temporary IT approval was never lifted. 

Practices at Moama Airfield
Pre-flight video briefs

The accident pilot started flight training with AFT at Moama in April 2022 with operations temporarily moving to Echuca, Victoria, during the flooding of Moama in late 2022. Staff and students interviewed by the ATSB who attended Moama from late 2022 through to the closure in August 2024 reported that no pre-flight briefings or post-flight debriefings were delivered for RPC candidates. Instead, the CFI had produced a short in-flight video for each of the RPC flight training elements, which demonstrated how the manoeuvres were to be flown, and candidates reported they had to pay a subscription fee to access AFT flight training videos for pre-flight briefing material. 

On review of the draft report, the CFI reported that the videos were gradually introduced from 12 July 2023 to 22 July 2024. Therefore, the videos were not used for the delivery of training to the accident pilot, which they reported was delivered in-person.

The CFI reported that the videos were only introductory material and not the pre-flight briefing material. However, the CFI’s position was contradicted by the Moama AFT instructor staff and students interviewed by the ATSB. Additionally, the ATSB noted that the syllabus used by AFT staff included the following items:

Confirm student has watched the relevant video briefing and understood the concepts

Remind students to login to AFT members page and watch next video

According to RAAus, their Exposition did not prohibit an FTS from implementing pre-flight video briefings in lieu of in-person pre-flight briefs. However, RAAus advised being unaware of the videos prior to suspending the CFI in August 2024. RAAus learnt about the videos from interviews with AFT members about the practices at the FTS. However, they were then told by the CFI that access to the videos was no longer available and therefore, RAAus reported they were unable to assess whether the content of the videos was adequate. 

The ATSB interviewed an RAAus CFI, who was also a CASA flight instructor, and who had reviewed one of the videos. They reported that they didn’t think the video met the quality required for a pre-flight brief. Another RAAus CFI, who had reviewed several of the videos for the AFT CFI, reported to the ATSB that they had been led to believe that they were the pre-flight briefing material and that they were inadequate due to deficiencies in the quality of instruction presented.

They noted that, while the AFT CFI was projecting a friendly demeanour in the videos, it was often at the expense of technical errors and an adequate demonstration. For example, the reviewer noted the stalling video did not include any reference to the effect of load factor on stall speed and reference to checks and limits were often omitted in the various videos. 

The ATSB obtained copies of 12 of the AFT videos from elements of the RPC syllabus, one produced in 2020 and the remainder in 2023. This evidence was consistent with a report the ATSB received from a Moama AFT instructor that they were already receiving video briefs when they started flying training in late 2022. They ranged in length from 2 minutes and 15 seconds to 7 minutes and 30 seconds. Of specific interest to the ATSB investigation was the aerodynamic stalling video, which was of 6 minutes duration.

In that video, the CFI demonstrated the reduced effectiveness of flight controls near the stall by applying full left then full right rudder and instructed the use of rudder to level the aircraft if a wing drop occurred. The risk of inducing a spin from large rudder applications near the stall was not mentioned. By contrast, the CASA flight instructor manual for aeroplanes explained these points in its chapters on stalling and spinning as follows:

Emphasize that if a wing drops, rudder is used to prevent yaw into the direction of the lowered wing. The wing is raised with aileron when it is un-stalled.

An aeroplane is made to spin, whether accidentally or deliberately, by faulty use of the controls particularly the rudder.

During the stalling video, the CFI explained that lowering the flap for the configured stall demonstration would ‘thicken’ the wing, and that the thicker the wing, the slower they could fly. The manufacturer’s website for the demonstration aircraft stated that it had a slotted flap. A slotted flap is a design feature used to control the boundary airflow layer and increase the camber of the wing. Lowering the flap increases the maximum coefficient of lift (and drag) for the wing, thereby allowing the aircraft to fly and stall at a lower airspeed and is part of the basic lift formula. 

At the start of the video, and in accordance with the RAAus syllabus of flight element of stalling, the CFI demonstrated the pre-manoeuvre checks. However, there was no reference to flap limiting speeds for the configured stall and no demonstration of post loss of control checks after recovery from any of the stalls. The RAAus syllabus of flight included ‘airframe limitations’ as a competency requirement within the element of stalling.

Demonstration of stall at greater than 1G

For the RAAus RPC syllabus, stall exercises were limited to straight and level, clean and configured stalls, with and without wing drops, which were covered in the AFT video. However, the RPC theory syllabus did require a thorough understanding of the relationship between load factor and stall speed and the instructor syllabus included demonstration of stall entry at greater than 1G (critical angle of attack exceeded at a higher airspeed). In the AFT stalling video, the CFI directed the viewer’s attention to the lower stall speed when the flap was lowered for a configured stall, but a higher stall speed, and what contributes to a higher stall speed, was not demonstrated or discussed. 

The CFI reported that the demonstration of stall entry greater than 1G was conducted in training, but the 2 AFT instructors interviewed by the ATSB reported they did not conduct this manoeuvre during their training. One of the instructors reported that they were unaware of the effect of load factor on stall speed at the time of the accident and that both themself and the accident pilot were trained in stalling by the AFT CFI for their instructor course. Therefore, they believed the accident pilot would not have covered this topic either. Their main concern with the load factor applied by the accident pilot during steep turn manoeuvres was the potential for a structural failure.

While the CFI reported that the ‘greater than 1G stall manoeuvre’ was taught as a turning stall during training, they were unable to recall the parameters used for the demonstration. The AFT records for their instructor training courses included comments about clean stalls, configured stalls and wing drops. However, there were no references to a stall at greater than 1G.

The AFT RPC student records indicated that the element ‘critical angle of attack exceeded at a higher airspeed’, was assigned a competency code on 46 out of 55 occasions. This was despite it not being in the RPC syllabus and the AFT instructors interviewed by the ATSB reporting that they had never done it in training themselves or with a student. One instructor explained that the competencies for each flight were accessed during the flight with a portable electronic device, such as a smartphone, and that on a small screen, instructors might have only registered the start of the competency, which stated ‘critical angle of attack exceeded…’, without either registering or understanding the meaning of the rest of the competency, which stated ‘…at a higher airspeed’. 

Online exams

The AFT instructor interviewed by the ATSB, who started flying training with AFT at Riddell Airfield, reported that they followed the RAAus paper-based exam system, as previously described, and that they had no experience with an online exam system. However, the other instructor interviewed by the ATSB, who started at Moama Airfield (Echuca during the floods), conducted their exams at home, unsupervised using their own login to the AFT online exam system. This was the same process described by the AFT RPC graduates from Moama interviewed by the ATSB. 

The CFI reported that the online exam system was set up in response to the COVID lockdown period and was approved by RAAus. The setup of the system entailed the CFI providing a copy of each exam paper and marking rubric to the software platform provider for loading onto their platform. The exception was the RAAus PPL(A)-equivalent exam, which was marked by RAAus and therefore no marking rubric was provided. The CFI reported that the software provider loaded answer A as the default correct response to all questions for the PPL(A)-equivalent exam and notified them of this action.

The AFT cohort who used the online exam system paid a subscription to access the exams and were notified by the CFI or their instructor when they were due to complete an exam. The CFI was the administrator for the online system and reported that the security protocols prevented anyone else from downloading or printing a copy of an exam paper. As the administrator, the CFI included settings which allowed 2 attempts at each exam and revealed the correct answers to all questions in the exam report, provided after the first attempt. 

One of the Moama RPC graduates reported there was no study direction before an online exam and that the staff expected they would pass each exam on a second attempt if required. This graduate reported there were no classroom lessons, in addition to no in‑person pre-flight briefs, and the lack of theory education caused them progression problems and learning difficulties with some of the technical aspects. 

Another Moama RPC graduate, who had prior non-aviation teaching experience, believed the online exams were open-book as they were unsupervised. Consequently, they used their flight training reference books during exams, supported by online searches for any questions they could not find the answer to in their books.

They did not pass their first attempt at the basic aeronautical knowledge exam but received all the correct answers in their exam report, which they photographed and used for their second attempt. They did not receive any classroom lessons or pre-flight briefings at AFT and reported that they felt the learning experience was substandard.

The RPC graduate had 2 attempts at the basic aeronautical knowledge exam on the same day recorded in the AFT exam records, with a score of 100% for both attempts. One of the AFT instructors reported to the ATSB that the exam scores were manually entered and might not have represented the actual results. Of the 146 entries in the AFT exam records, from April 2021 to July 2024, there were no failures.

Deficient instructor supervision

As previously described, on 19 December 2023, the AFT CFI conducted the senior instructor flight test for the accident pilot and incorrectly submitted the upgrade application to RAAus with a copy of the pilot’s May 2023 instructor exam, which had been conducted online. On 3 January 2024, the CFI certified in the pilot’s logbook that they met the requirements for the senior instructor rating in accordance with the RAAus syllabus of flight. The pilot subsequently took the RAAus PPL(A)-equivalent exam online on 12 January 2024. 

The pilot scored 94% (47/50), noting answer A was the default correct answer for all questions, and which the CFI reported that they were aware of. The CFI then submitted a copy of this exam to RAAus, noting that they reported that they were the only one who could download the exams from their online platform. 

In late January, RAAus notified the CFI of the pilot’s failure assessment for the PPL(A)‑equivalent exam, that the pilot’s upgrade to senior instructor would not be processed and that the pilot would continue to require direct supervision as an instructor. However, in January 2024, the CFI left the FTS for extended travel around Australia throughout the calendar year 2024. 

Prior to leaving, the CFI enquired with another RAAus CFI if that person could hold a temporary CFI position for them while they were away. However, they were told by that person that they could not attend the FTS in Moama and were therefore unable to comply with the direct supervision requirements for the AFT instructors. There was no reference in the AFT CFI’s RAAus member record of their absence from their FTS and RAAus reported they had no knowledge that the CFI had departed from the area and left their instructors without direct supervision.

The accident pilot’s last logbook entry was an AFT instructional flight on 7 August 2024 and their last check flight with the CFI was their senior instructor flight test on 19 December 2023. There were no entries in 2024 for a standards and proficiency check from the CFI, which was required every 90 days. 

The AFT training records indicated that the CFI was at the FTS until at least 11 January 2024 and returned to deliver training for several days in February, May and June of 2024. One of the AFT instructors reported they didn’t get a check flight from the CFI during one of the visits, which concerned them as they considered themself and the other instructors at AFT to be relatively ‘green’.

The other AFT instructor reported that the flights they conducted with the CFI during this period were ferry flights between Melbourne and Moama when the CFI visited the FTS to deliver training. The 3 AFT instructors all qualified in 2023one in early 2023, the accident pilot in mid-2023 and the third in late 2023.

Examination conduct

As previously described, the accident pilot unsuccessfully re-attempted the PPL(A)‑equivalent exam on 24 February 2024. At the end of February, RAAus emailed the CFI the result from the pilot’s second attempt at the exam and their concern about the type of errors made. They also advised the CFI that it was critical for the CFI to also complete the PPL(A) exam as they had delivered the instructor training for the accident pilot and RAAus could not confirm that the CFI had previously completed the PPL(A) exam. 

In response, the CFI reported to RAAus that it was their intent to complete a PPL(A) course and the CASA PPL(A) exam. RAAus noted this but also committed to revising their PPL(A)‑equivalent exam by the end of March as an alternative pathway. In late March, RAAus requested an update from the CFI on their progress towards attempting the PPL(A) exam. The CFI reported that both they and the accident pilot were enrolled in a course but could not provide an estimated completion date. 

On 2 July the CFI submitted a completed exam paper to RAAus for the same version of the PPL(A)-equivalent exam that the accident pilot had failed in February (2022 version). However, RAAus noted that their policy for exam conduct, published at the front of the exam paper, was not followed. Specifically, a supervisor for the exam was required to be appointed by RAAus, the exam answer sheet should have been used instead of the exam paper, and the supervisor should have submitted the exam to RAAus for marking, rather than the candidate (the CFI themself). 

RAAus communicated the problems they identified to the CFI, and they subsequently received a copy of the exam answer sheet, with a supervisor’s signature dated 4 July. The answer sheet provided was marked by RAAus and scored as a pass (88%). RAAus prepared a knowledge deficiency report with the pass result for the CFI and annotated the exam location as ‘Supervised via zoom (possibly at Moama)’. 

On 8 July, RAAus followed up with the certifying supervisor on several points, which included:

Their instructor approval had lapsed in January and therefore their supervisory privileges had also lapsed.

How were they given approval to supervise the exam as the policy document states that the RAAus HFO makes these arrangements?

Exams require direct supervision, which is in-person, whereas the use of Zoom indicated indirect supervision.

The supervisor’s certification date of 4 July was 2 days after the exam paper was submitted to RAAus.

There was no record of answers to these queries, but RAAus subsequently concluded that the CFI’s exam result was invalid. At the end of July, they communicated to the CFI that either the CASA PPL(A) or a new RAAus PPL(A)-equivalent exam needed to be taken prior to 16 August 2024. 

The CFI notified RAAus on 7 August that they would attempt the PPL(A)-equivalent exam if it could be facilitated for them in Far North Queensland. This was arranged for 8 August with a copy of a new RAAus PPL(A)-equivalent exam (2024 version). The 2024 exam paper comprised 60 questions, of which 50 were the same, or similar, to the 2022 version. The CFI scored 77% (46/60), which was below the required pass mark of 80%. 

The CFI reported to the ATSB that other CFIs had told them that they too could not pass the 2024 version exam paper, and the CFI did not believe the exam had been validated and therefore should not have been used. They provided a specific example of a navigation question they believed was marked as incorrect because they used a protractor rather than the ‘1-in-60’ rule to calculate their answer to a heading correction question. However, the ATSB identified that it was possible to derive the correct answer using either method. 

The ATSB also noted that the CFI provided the same incorrect answer as the accident pilot to a question about the relationship between angle of bank, load factor and stall speed. They had both selected the answer with the correct stall speed but the incorrect load factor. The RAAus syllabus of flight training contained the references for the navigation and stall speed questions.

The marking of the CFI’s answer sheet revealed there were 13 incorrect answers in the first 50 questions (7 in common with the accident pilot) and 1 incorrect answer in the 10 additional questions. Consequently, if only the 50 questions from the 2022 version exam were marked, the score would have been 74% (37/50) and remained below the pass mark. 

Safety related suspensions

On 9 August, RAAus notified the CFI of the failed exam result and that the exam had been crosschecked by 2 independent staff. They then issued an immediate SRS, suspending the CFI’s senior instructor rating, which was required for a CFI approval. To remove the SRS, the CFI was required to supply RAAus with evidence of a pass result for the CASA PPL(A) exam. RAAus reported to the ATSB that they were prepared to arrange for a temporary CFI for AFT in the interim, but the CFI decided to cease FTS operations and later sold AFT.

On 13 August, RAAus notified CASA of their implementation of the SRS for the AFT CFI and that the matter was currently under review. The notification to CASA included:

  • RAAus identification of incorrect marking of a PPL(A)-equivalent exam for a senior instructor candidate, which raised questions about the CFI’s theoretical knowledge
  • advice of the CFI’s failed attempt at the PPL(A)-equivalent exam, with a conclusion that they therefore did not meet the theoretical knowledge requirement for the senior instructor rating and would need to provide evidence of a pass for the CASA PPL(A) exam. 

On 11 November, RAAus notified the AFT CFI that they had completed an informal assessment as per the OCHM and did not believe a formal inquiry was necessary. They reiterated that the remedial action required was the completion of the CASA PPL(A) exam. However, by that time the CFI’s membership had lapsed. RAAus reported to the ATSB that the remedial action requirement would remain flagged in the system in the event that the CFI elected to re-activate their membership and have their senior instructor rating reinstated.

Following the accident, on 19 December 2024, RAAus issued an SRS notice to all RPC graduates from AFT who did not hold a CASA PPL(A) licence or higher. This was due to non-compliances with the conduct and supervision of exams, which meant they could not verify that former students met the theoretical knowledge requirements for the issue of an RPC. 

Civil Aviation Safety Authority

Surveillance events

The CASA Sport and Recreation Branch (CASA Sport) conducted a Level 1 surveillance event of RAAus at their premises between 12–14 April 2023, and a Level 2 surveillance event at their premises between 3–5 September 2024. Prior to 2023, the previous audit was a Level 1 surveillance event on 4 May 2019. The ATSB obtained a copy of the previous 2 audit reports (2023 and 2024) of RAAus by CASA.

The May 2019 audit resulted in 1 finding and 6 observations. The April 2023 audit resulted in 4 findings and 7 observations. The 4 findings related to the elements of airworthiness and listing of aircraft and were not relevant to the ATSB’s investigation. However, one observation of relevance from the 2023 audit was for the element of Evaluation of Authorisation Holders, as follows:

The processes for the regular evaluation of holders of certain authorisations to ensure compliance with the requirements set out in the ASAO’s policies and procedures require additional development. 

As this was an observation, no response was required from, or provided by, RAAus. The September 2024 audit of RAAus followed their notification to CASA Sport of the SRS issued against the AFT CFI and the introduction to the audit report stated:

The auditors sampled the systems and elements relating to RAAus' oversight of flight training schools with the respective key personnel and the RAAus Accountable Manager. Emphasis was placed on reviewing:

• the integrity of their training/testing system which leads to the granting of pilot authorisations,

• governance and process including consistency,

• oversight of training and examining,

• safety assurance including the reliability of information provided by examiners.

CASA Sport raised 2 observations from the audit for competency-based training, and interpretation of manuals, which were both against the element of Flight Operations (Pilot Authorisations). No responses were required or provided to the observations. The observation about competency-based training had a similar theme to the 2023 audit observation about compliance issues and stated:

Current updates to the Flight Operations Manual (Version 8) places significant reliance on CFIs and Examiners applying competency-based training and testing outcomes. However, one of the highest individual non-compliances identified from the RAAus Risk and Audit Matrix Occurrence Tracker records has been deficiencies in the FTS applying and recording competency-based training outcomes (assessing and recording competence and rectifying deficiencies). 

The non-compliances found by RAAus auditors during the audits of FTSs - with more than 30% of the RAAus FTS surveillance events (conducted between Dec 2021 and August 2024) showing a non-compliance in relation to assessing and recording competencies - may suggest a level of guidance regarding competency-based training for FTS may be required.

Pilot examination office 

The CASA pilot online examination system is called the pilot examination office (PEXO). The key personnel in the daily operations of an examination centre are the registrar and invigilator. A registrar is responsible for making the booking of exams for candidates and an invigilator is responsible for the direct supervision of the candidates for their exams. An individual may hold both the registrar and invigilator positions.

Registrars, invigilators and examination centres must be authorised by CASA and the approval for FTSs to conduct exams is limited to PPL and the private instrument flight rating (PIFR). Therefore, a candidate for a commercial pilot licence, which is a requirement to instruct for the issue of a pilot licence, would need to pass their higher‑level theory exams at an examination centre independent of their FTS.[11]

The registrar, invigilator and candidate each have their own unique password, which limits their access within the system to their specific functions. CASA records access and usage of the PEXO system and provides an e-learning module for the system users (registrars, invigilators and candidates). They also undertake surveillance of examination centres, which may, or may not, be conducted with advance notice. 

The exams are accessed by connection to the CASA server during an examination. When an exam is started, the questions and associated answers will be generated from a database of questions, and a timer will count down. The program will automatically close the exam when the time has expired or if the candidate selects ‘End’ exam and ‘logout’. After the candidate selects ‘End’ exam, it will be automatically submitted for marking and the result recorded against the candidate. The invigilator login is needed to recover the result and the associated knowledge deficiency report for the candidate. 

Granting of a Recreational Pilot Licence

Under CASR Part 61.480, CASA can grant an RPL to an individual on the basis of them holding a pilot certificate, granted from certain organisations, which included RAAus. In this scenario, the applicant is taken to have passed the aeronautical knowledge examination and flight test for the licence and associated aircraft category rating issued.

The applicant is also taken to have met the requirements for the aircraft class rating and design feature endorsements for which the applicant is permitted by their pilot certificate to act as the pilot in command. However, they must successfully complete a flight review for their class rating in order to exercise the privileges of their rating. In the case of the accident pilot, this was a single-engine aeroplane class rating.

Mandatory reporting and enforcement process
Background 

Under CASR Part 149.425, RAAus have mandatory reporting requirements to CASA Sport in accordance with their Exposition and the circumstances prescribed by 149.425. If RAAus reported to CASA Sport that they had revoked or suspended a member’s qualification(s), then the matter could be referred by CASA Sport to the CASA Coordinated Enforcement Process (CEP), which is described in the CASA Enforcement Manual.

Under the CEP, the matter is referred to the Coordinated Enforcement Meeting (CEM) where it is allocated to an investigator to investigate and provide a report to the CEM for discussion on whether to proceed with action. The participants in the CEM have a range of options, which include, but are not limited to, the following:

  • no action
  • education
  • counselling
  • direct the person to undertake examinations
  • suspend authorisations pending completion of a practical or theoretical examination
  • varying, suspending or revoking a licence, endorsement or rating.   
Response to RAAus safety related suspension notices 

On 19 December 2024, RAAus issued an SRS notice to all RPC graduates from AFT who did not hold a CASA PPL(A) licence or higher. The notice explanation included the following:

RAAus has identified non-compliance with respect to the conduct and supervision of exams conducted by students at Adventure Flight Training. Based on the evidence available, RAAus is unable to verify that all former students of Adventure Flight Training met the required theoretical knowledge standards required for the issue of a Recreational Pilot Certificate with RAAus. 

Due to the potential for this finding to result in a risk to aviation safety, RAAus has implemented a safety related suspension (SRS) on your Recreational Pilot Certificate (RPC), effective immediately, pending the conduct of an assessment to confirm that your theoretical knowledge meets the expected standard required to maintain an RPC.

On 20 December, RAAus notified CASA Sport of the implementation of the SRS following their ongoing investigation into how AFT was being managed. Their notification to CASA did not include the names of the affected members, but did include the following explanation:

It has been identified that some students undertook RAAus exams using an online system from their home address without the supervision of an instructor. Further, it has been identified that the system used to sit exams online allowed the student to update incorrect answers and resubmit the exam to achieve a successful pass mark.

The process for the affected members to remove their SRS included passing the RAAus converting pilot exam (a requirement for a pilot licence holder applying for an RAAus RPC) under the supervision of an FTS CFI or senior instructor. The exam supervisor also had the discretion to require additional theoretical assessments and one of the AFT instructors subject to the SRS reported to the ATSB that in addition to the converting pilot exam, they were also required to complete the RAAus instructor exam. The instructor also reported to the ATSB that they held a CASA-issued RPL (issued in recognition of their RPC) but CASA had not contacted them about continued exercising of the privileges of their CASA-issued licence.

CASA reported that they recorded all information provided by RAAus in their records management system but no follow‑up was conducted with RAAus to identify the specific members affected. RAAus reported that they elected to voluntarily provide the initial SRS (August 2024) about the AFT CFI to CASA as it involved a higher approval holder. When the AFT graduates’ SRS was implemented in December, RAAus considered that it would be prudent to notify CASA due to the number of pilot certificate holders involved.  

The ATSB obtained a list of the affected members from RAAus, about 7 months after the SRSs were issued, and requested CASA review it against their RPL records. It was identified that 3 affected members held a CASA-issued RPL, granted based on their RAAus RPC, which included 2 at the time the SRS was issued.

Two of those 3 members addressed the SRS within a month of its issue. The third had not addressed it and their RAAus membership had lapsed, which meant that they continued to hold a CASA RPL without restrictions, while their RPC was suspended and would not be lifted unless they re-activated their membership. 

Safety analysis

Introduction

On 16 November 2024, an amateur-built experimental certificate Morgan Cougar Mk 1 aircraft, registered VH-LDV, with a pilot and 2 passengers on board, departed from West Sale Airport, Victoria, for a local area flight. The aircraft collided with terrain in a paddock 19 km north-north-west of West Sale Airport about 17 minutes after departure and shortly after commencing a series of orbits. The aircraft was destroyed and the 3 occupants fatally injured. 

This analysis will discuss the factors that contributed to the accident sequence, including the loss of control and the pilot’s knowledge deficiencies and history of risky flying behaviour. It will also discuss the management of the Adventure Flight Training (AFT) school and the Recreational Aviation Australia (RAAus) examination system. 

In addition, the analysis will examine the aircraft’s occupant restraints, aircraft design and guidance material from the Civil Aviation Safety Authority (CASA) advisory circular for amateur-built experimental certificate aircraft and transition training guidance for buyers of these aircraft. Finally, it will discuss the CASA Sport and Recreation Aviation Branch management of suspension notices received from RAAus.

Accident sequence

Loss of control

Analysis of the final 3 minutes of the flightpath revealed the aircraft’s speed and height were decreasing as it flew a series of turns and orbits. When the aircraft commenced the final turn, the groundspeed and height above the ground had reduced from 103 kt and 716 ft, to 64 kt and 269 ft. Using the recorded local mean and gust wind, the estimated calibrated airspeed was in the region of 67–74 kt at the start of the final turn. The groundspeed reduced to 56 kt during the final turn as the turn radius tightened and analysis of this turn indicated a steep turn with an average 45° angle of bank required for the observed flight path.

A closed-circuit television camera at a nearby farm recorded the aircraft enter the final turn with an angle of bank consistent with a steep turn manoeuvre. The aircraft then pitched nose down at an estimated airspeed of 59–65 kt and height of about 220 ft. Witnesses reported that the aircraft appeared to fall from the sky, and the recorded data indicated an abrupt reduction in altitude and increase in speed. The witness accounts, recorded data, and camera footage were consistent with a loss of control due to an aerodynamic stall.

Wreckage examination found the aircraft attitude was recovering towards straight and level just prior to impact and that the engine was operating at impact. This indicated that it was very unlikely that a mechanical fault contributed to the accident. The amount of engine power at impact could not be determined and the ATSB could not rule out the possibility that the pilot retarded the power lever towards idle in response to the loss of control, which would be the expected response to a nose-low unusual attitude.

The final turn started 7 seconds prior to the stall, at which time the aircraft was estimated to be 29–36 kt above the flight test recorded stall speed of 38 kt in straight and level flight. For a stall to occur in 7 seconds after starting the turn, it required a closure rate of 4–5 kt per second to the stall speed, which was consistent with an accelerated stall at a load factor of 2.5–3G. 

The ATSB could not determine the stall warning system settings, or if an audible stall warning would have been activated prior to the stall event. However, the stall occurred in a steep turn at a height that was insufficient for recovery.

Contributing factor

The aircraft entered an accelerated stall in a steep turn with insufficient height to recover, resulting in a collision with terrain.

Knowledge deficiencies

Shortly after the accident, the ATSB was contacted by an AFT instructor who was a colleague of the accident pilot. They advised being unaware of the effect of angle of bank and load factor on stall speed. The accident pilot was trained at the same flight training school (FTS) as the reporting pilot for their recreational pilot certificate (RPC) and instructor rating, prompting an examination of the accident pilot’s knowledge of aerodynamics. 

On review of the accident pilot’s last RAAus exam, the ATSB found that they failed the exam on 2 consecutive attempts. On the pilot’s second attempt, the incorrect answers included 2 questions about stalling, one of which included the relationship between angle of bank, load factor and stall speed. While the pilot’s answer had the correct stall speed for the nominated angle of bank, they had the incorrect load factor. However, it is the load factor generated by manoeuvring flight that affects the stall speed and not the angle of bank. Therefore, the pilot was missing the critical link in the relationship – how the load factor is derived from the angle of bank in a level turn, and how the stall speed is derived from that load factor.

The pilot’s incorrect answers resulted in RAAus expressing their concern about the pilot’s knowledge of aerodynamic stalling when they notified the AFT chief flying instructor (CFI) of the result. The question about load factor and stall speed in a turn was listed in the RAAus syllabus of flight as an item that required a thorough understanding at the RPC level and the exam had been submitted for the pilot’s upgrade from instructor to senior instructor. As the pilot had failed this exam twice, a new exam was required to be completed, and the pilot started a CASA commercial pilot licence theory course. 

From early June to early July 2024, the pilot conducted flight training in a Pitts Special aerobatic aircraft. Several parties reported to the ATSB that this was for the purpose of an aerobatics endorsement. The syllabus for an aerobatics endorsement included the effect of load factor on stall speed. However, the flight training records indicated it was transition training and not training for an aerobatics endorsement. While an aerobatics endorsement included a list of underpinning knowledge requirements, which included the relationship between load factor and stall speed, it was not required to be taught for transition training.

In late July, the pilot failed their first attempt at the CASA commercial pilot licence aerodynamics exam, which included an incorrect answer to the effect of manoeuvring on stall speed. This indicated the pilot’s previous misunderstanding of this topic had not been corrected. However, only the knowledge deficiency reports were retrievable by CASA and not the exam questions and answers, which limited the analysis of these exams. A comparison of the 2 subjects the pilot completed revealed they achieved a high pass result for aircraft general knowledge, but a fail result followed by a low pass result for aerodynamics. This indicated that the pilot found learning the aerodynamic aspects of flight challenging, which was consistent with the concerns previously expressed by RAAus.

The RAAus syllabus for an instructor included demonstrating a stall entry at greater than 1G (critical angle of attack is exceeded at a higher airspeed), which could have addressed the misunderstandings that the pilot held from their RPC theory. While the AFT CFI reported that this training was conducted, the 2 AFT instructors interviewed by the ATSB reported that it was not done and the ATSB found no comments in any of the AFT instructor training records to indicate that it was completed. Therefore, the ATSB concluded that it likely was not done and that the pilot’s knowledge of the relationship between load factor and stall speed was likely deficient at the time of the accident, which contributed to them manoeuvring the aircraft close to the stall speed. 

Contributing factor

It was likely that the pilot had an inadequate understanding of the relationship between angle of bank, load factor and stall speed, which contributed to the pilot not fully understanding the risk of conducting slow steep turns.

Pilot flying history and aircraft characteristics

The ATSB interviewed several pilots from AFT who were either colleagues of the accident pilot (fellow instructors) or were RPC graduates from the FTS. They all had experience flying with the accident pilot and 2 of them were syndicate members with the pilot in the purchase of the accident aircraft. One of the syndicate members reported they did not experience any risky flying practices with the pilot but was aware that the pilot had received counselling for such flying.

The ATSB identified that several people, including pilots, fellow instructors and CFIs had been counselling the pilot leading up to the accident, including 3 counselling sessions in the 2 months prior to the accident.

In between the counselling sessions in the last 2 months, there were 3 reported instances of risky flying activities by the pilot. It was therefore likely that no individual involved in counselling the pilot had full knowledge of their behaviour and the counselling sessions did not achieve their intended purpose.

While the safety concerns were discussed with the pilot, no reports were submitted to RAAus and therefore no official action was ever taken. It is possible that there was a reluctance to submit official reports after providing counselling, as this action could make the reporter identifiable and result in a loss of trust between the reporter and their community.  

Other factor that increased risk

The pilot was counselled about unsafe flying practices but was not reported to any authority and therefore no official follow-up action was ever initiated.

Two fellow AFT instructors each had experiences with the pilot conducting low level steep turns at high and low speeds and had both advocated to the pilot to manoeuvre their aircraft less aggressively. One of the RPC graduates also experienced the pilot manoeuvring the aircraft aggressively during their pre-RPC check flight in 2023 and conducting a slow speed steep turn overhead a tractor during a private flight in November 2024, 15 days prior to the accident. These reports related to RAAus Topaz and Jabiru aircraft, which both had higher published stall speeds than the Morgan Cougar aircraft. This likely led to an expectation by the pilot that similar manoeuvres could be safely conducted in the Morgan Cougar.

The Morgan Cougar was an amateur-built experimental certificate aircraft, which was subject to a 40-hour flight testing period that included stall testing. However, the stall testing was predominantly limited to 1G clean and configured stalls. The builder was able to recollect one instance of a left turn stall at 30° angle of bank. In this case, the aircraft stalled in a sudden and unexpected manner compared with the 1G stall response, and the builder hypothesised that a stall at a greater angle of bank could exaggerate this effect.

The description provided by the builder was consistent with the warning from the United States (US) Federal Aviation Administration (FAA) that there are no rules for the stall behaviour of an experimental aircraft, and that they can depart controlled flight dramatically without any perceptible warning.

The designer of the Morgan Cougar recommended the builder not attempt accelerated stall testing alone, and this was not done, so the responsiveness of the aircraft to this scenario was unknown. However, the accident pilot invited an AFT RPC graduate for a familiarisation flight in the Morgan Cougar 3 days prior to the accident flight, which the passenger described to the ATSB as for the purpose of demonstrating the responsiveness of the aircraft. During the flight, the pilot demonstrated manoeuvring the aircraft at 70–75° angle of bank, which the passenger described as ‘knife-edge stuff’ and would have required a load factor in the region of 3–4G.

According to the FAA, aircraft with light control forces and/or rapid response are susceptible to overcontrolling by pilots who have not received any type-specific training. Furthermore, low wing aircraft tend to roll into the turn during a turning stall. A stall in a turn will increase the height loss during recovery, as the recovery requires a rolling motion followed by a pitching motion, and therefore, the further the aircraft has to be rolled to restore wings level flight, the greater the height loss.

The syndicate members signed the sale agreement on 5 November, 11 days prior to the accident. However, the builder was unable to accompany them on any familiarisation flights and did not discuss the turning stall behaviour of the aircraft with them. Furthermore, it was concluded from interviews and review of ADS-B data that none of the members had completed any transition training on the aircraft. Therefore, it was very unlikely that the pilot was aware of the specific response of the aircraft in a turning and/or accelerated stall scenario, which was very likely different to the 1G stall and different to the approach to stall and post-stall response of aircraft the pilot had delivered RPC training in at AFT. 

Contributing factor

The pilot had a reported history of conducting low flying and slow steep turns and was likely unaware that, while the accelerated stall characteristics of the accident aircraft were unknown, there were indications that it would be abrupt.

Adventure Flight Training school management

Demonstration of stall at greater than 1G

The RAAus instructor syllabus module for aerodynamic stalling included a stall entry at greater than 1G sequence. This was for the instructor candidate to demonstrate exceeding the aircraft’s critical angle of attack at a higher speed than the 1G stall speed. While this was not part of the RPC syllabus, the instructor syllabus required the demonstration to be performed by the instructor to a high degree of accuracy. However, the AFT instructors interviewed by the ATSB reported that this manoeuvre was not taught on their instructor course and their training records did not include any instructor comments to indicate that it had been completed.

The AFT CFI reported that the stall entry at greater than 1G was taught as a turning stall manoeuvre but could not recall any of the performance parameters for it. Furthermore, the AFT records indicated that a competency code was routinely assigned to their RPC candidates for this manoeuvre as part of their stalling training. Once again, there were no comments within the instructor remarks to indicate that it was taught to those members who had a competency code assigned.

Based on this evidence, the ATSB concluded that this competency was likely not taught at AFT and that the competency code was probably misunderstood.

Instructor supervision

Within the RAAus FTS system, instructors required direct supervision from either their CFI or an approved senior instructor. The purpose of this was to provide continuing mentoring and development of the FTS instructors. The level of supervision could be reduced to indirect (remote) for a senior instructor. However, except for the CFI, none of the AFT instructional staff had progressed to senior instructor. The accident pilot attempted to upgrade to senior instructor in early 2024 but failed the required theory exam component.

When RAAus communicated the pilot’s exam result to the AFT CFI on 29 February 2024, they included their concern about the pilot’s knowledge of aerodynamic stalling and the requirement that the pilot remain under direct supervision. However, the AFT instructors reported to the ATSB that their CFI left the FTS for a trip around Australia in early 2024, with occasional return visits. This was supported by another CFI who had been asked, but declined, to supervise the FTS by the AFT CFI in their absence.

RAAus reported to the ATSB that they were not aware of the AFT CFI’s extended absence from their FTS.

Consequently, the AFT instructors were not under direct supervision for the majority of 2024, even though they had all only received their instructor ratings in 2023. Of note, the instructor who had qualified first, in early 2023, reported to the ATSB that they were all relatively inexperienced as instructors and they did not always conduct a check flight with the CFI during their return visits. This was supported by the accident pilot’s logbook, in which there were no check flights with the AFT CFI recorded in 2024. The fact that the AFT CFI had asked an external CFI to supervise the FTS indicated they were aware of their supervision requirements but ultimately did not comply with them.

Pre-flight video briefings

The RPC graduates from AFT Moama in 2023 and 2024 reported that they did not receive any classroom tutorials or in-person pre-flight briefs. Instead, they had to pay a subscription fee to access a series of flight training videos in which the CFI demonstrated the manoeuvres to be flown for each element of the RPC syllabus. While the CFI stated that the videos were not the pre-flight briefing, the AFT instructors reported that they represented the entirety of the pre-flight briefing, with no in-person pre-flight briefs delivered. 

The use of this medium was not prohibited by the RAAus Exposition, but RAAus had not reviewed the material and therefore had no knowledge of the adequacy of instruction presented. Two RAAus CFIs who had reviewed the videos reported that the quality of instruction in these videos was inadequate as the sole source of pre-flight briefing material.

Within the video sequence for stalling, the AFT CFI demonstrated large rudder inputs near the stall speed and instructed the use of the rudder to level the attitude if a wing drop occurred. The risk of inducing a spin, as described in the CASA flight instructor manual for aeroplanes, was not acknowledged.

Additionally, during the stall demonstrations, the CFI omitted flap limiting speeds for the configured stall and did not demonstrate post-loss of control checks to confirm there was no overspeed or overstress of the flap. If flap is subjected to damage from an overspeed or overstress, further damage and control problems can occur if an attempt is made to retract the flap. In the case of an aircraft with a retractable landing gear, the landing gear could become stuck if an attempt to retract it is made after overspeed damage has occurred.

The stalling video also revealed incorrect terminology by the CFI for their explanation of the effect of lowering flap. This related to the basic lift formula, which should have been taught and reinforced throughout the syllabus. 

While all these discrepancies may have been low risk in the demonstration aircraft, they introduced the potential for negative learning[12] in the lesson, which could be later applied in other aircraft types. The report from one of the AFT instructors, that they believed the accident pilot had copied the CFI in performing dumbbell reversal turns upwind in the circuit to expedite practice landings with students, indicated that negative learning was likely occurring at AFT. 

A component of the instructor assessment was the in-person delivery of a pre-flight brief and post-flight debrief. However, this was not practiced by the staff at Moama after they passed their instructor rating because of the use of pre-flight video. The Moama RPC graduates reported that the lack of access to in-person tutorials and pre-flight briefs contributed to learning difficulties for their flight training and theory exams. The delivery of pre-flight briefs is also important for instructor development because the practice requires them to explain how the theory of flight will be applied in the lesson, check their student’s knowledge, and answer impromptu questions about the topic. It is also the time to discuss any hazards associated with the flight and ensure the student and instructor have a shared understanding of how the lesson will be conducted.

The report from one of the instructors after the accident that they were not aware of the relationship between angle of bank, load factor and stall speed, which is part of the RPC syllabus, may have been the result of knowledge decay because they were not required to deliver briefings. The substitution of video briefs for in-person pre-flight briefs was likely at the expense of both student and instructor development.

Online exams

The AFT CFI introduced an online exam platform used at the Moama Airfield school, for which their students and staff were provided with a login. The ATSB discussed the use of online exams with an instructor and RPC graduate who completed their exams at Riddell Airfield, and they both reported they followed the RAAus paper-based exam process and had no knowledge of the online platform.

The RPC graduates from Moama were prompted by the CFI or staff when they needed to complete a theory exam, which was done online and without supervision. The CFI setup the exams so that 2 attempts could be made and the correct answers to all questions were revealed in the exam report after the first attempt. Consequently, one of the graduates who failed the basic aeronautical knowledge exam on their first attempt photographed all the questions with the correct answers identified and passed the exam on their second attempt. More generally, the online exam setup likely created an attitude from the staff at AFT that candidates would naturally pass the exam on a second attempt if needed. Significantly, there were no failure results from 146 exams in the AFT exam records over a 3-year period.

The accident pilot’s first attempt at the RAAus private pilot licence (aeroplane) (PPL(A)) equivalent exam was completed using the AFT online platform. The software provider had informed the CFI that answer ‘A’ was set as the default correct answer to all questions as they were not provided with the marking rubric. The pilot had used this platform previously for their instructor exam in May 2023 and, given that the other instructor from Moama was aware of how the system was setup, it was very likely that the pilot was also aware of the settings. Consequently, the pilot’s selection of answer ‘A’ to 47/50 questions, the majority of which were technically incorrect, indicated that they were answering to the marking system and not the questions. 

The pilot’s selection of answers may have resulted from the exam report providing the correct answers after a failed first attempt or from the CFI informing the pilot of the default correct response. In either case, the CFI reported that as the administrator, they were the only person who could download a copy of the exam. Therefore, they would have known the result for the exam they submitted to RAAus was almost certainly incorrect based on the default marking. 

Contributing factor

The Adventure Flight Training school management practices did not provide the required level of supervision, training and assurance that their graduates had achieved the required level of aeronautical knowledge and understanding for the qualifications they received. (Safety issue)

Recreational Aviation Australia examination system

The RAAus Exposition, approved by CASA under CASR Part 149, provided a basic overview of their examination system. Multiple-choice exams were provided and the FTSs were to store them securely and not reproduce or distribute them. The exams were distributed to the FTSs via email after each respective CFI had signed a declaration that the exams would be stored securely and not be reproduced or distributed. Candidates for theory exams were provided with an exam answer sheet on which they recorded their answer to each question. All exams were required to be supervised, marked, debriefed and the results recorded and retained by the FTS, with the exception that the RAAus PPL(A)-equivalent exam was to be marked by RAAus. There was no documented exam failure management process.

The RAAus instructor application form indicated that the upgrade to senior instructor was the only time that proof of successful exam completion was required to be provided, which was a change introduced in 2023. Prior to 2023, RAAus did not require proof of completion of any exams for the issue of a qualification or endorsement. In each case they accepted the certification from the examiner that the theory component was met. However, this did not necessarily confirm the examiner had sighted the exam and their certification could be based on the record of result provided by the FTS. The RAAus Exposition required the FTSs to be able to provide exam results on request and RAAus reported that it was the record of exam results that they inspected at audit and not the exam answer sheets. 

Consequently, the AFT CFI was able to progress through their instructor and senior instructor upgrade to CFI approval and the establishment of the AFT FTS, all without providing proof to RAAus that they had completed the associated theory exams. After the FTS was established, the CFI setup a system for online exams that could be completed by AFT members as open-book assessments without supervision. Further, all correct answers were revealed after the first attempt, and the exam could be immediately retaken. This non-compliant system likely existed throughout 2023, unnoticed by RAAus, as AFT’s use of an online platform only came to their attention in January 2024. The accident pilot had used the platform for their instructor exam in May 2023, but proof of completion of the instructor exam was not required to be provided to RAAus. 

The CFI’s upgrade to senior instructor was investigated by RAAus in early 2024 after they discovered the accident pilot’s PPL(A)-equivalent exam failure. They were unable to confirm with the examiner for the CFI’s senior instructor upgrade that the associated exam was done. The setup of the AFT online exam system, and the CFI’s subsequent submission of an exam and certification of remote supervision by a former instructor 2 days after the exam was submitted, all suggested a cultural malaise towards the theory examination requirements. 

The ATSB’s review of the RAAus examination system and the situation that unfolded at AFT, indicated that the only risk control evident in the theory examination system was the CFI declaration to not reproduce or distribute exams. The only effective oversight of exams by RAAus was the marking of the PPL(A)-equivalent exam, as the other oversight activities appeared to be limited to the records of exam results. 

The situation at RAAus contrasted with the CASA examination system, which had multiple controls in place for the access to and conduct of exams, supported by surveillance of the examination centres, which could be unannounced. CASA also had restrictions in place for the exams that could be hosted by an FTS, such that a candidate for an instructor rating would have to conduct some of their theory exams at an examination centre independent of their FTS. 

In 2025, there were a significant number of RAAus FTSs and members, estimated at 160 and 10,000+ respectively based on information from their website. This presented a significant risk management challenge for the integrity of their pilot examination system, particularly noting that their pilots could use their RPC to obtain a CASA licence. Considering the size and complexity of their operation, and what unfolded at AFT as described previously, the ATSB concluded that the RAAus examination system, as described in their Exposition, did not include sufficient controls to prevent the system from being exploited.

Contributing factor

The Recreational Aviation Australia pilot theory examination system did not incorporate sufficient risk controls to ensure that their examination processes were followed as intended and their members had achieved the minimum required knowledge in accordance with the syllabus of flight training. (Safety issue)

Restraint failure

The front seat occupants were ejected from their seats in the accident and the ATSB found the seatbelt latch plates separated from their buckles. However, no evidence was found to indicate the seatbelts were susceptible to false latching, and they were subjected to load testing by the builder. Other mechanisms by which a car seatbelt can fail to perform its function include inadvertent unlatching from occupant flailing in an accident and inertial unlatching. Inertial unlatching is a known phenomenon with car seatbelts in rollover accidents, when they are subjected to vertical accelerations.

The CASA advisory circular guidance for amateur-built experimental certificate aircraft (AC 21.4(2)) recommended that seatbelts comply with the US FAA Technical Standard Order approval for seatbelts. However, the builder did not believe they complied with the recommended standard and that the design was consistent with car seatbelts.

The ATSB reviewed pre-accident photographs of the interior of the aircraft and found the design of the seatbelts was consistent with car seatbelts and inconsistent with aircraft seatbelts. While the release of the front seatbelts would have contributed to the injuries sustained by the front seat occupants, the fatal injuries were likely the result of the ground impact.

Other factor that increased risk

The aircraft’s front seats were likely fitted with car seatbelts, which unlatched in the accident and resulted in the front seat occupants being ejected from their seats. While this exposed them to additional injuries, the fatal injuries were likely from the aircraft-ground impact.

Aircraft design and guidance

Energy attenuation

The pathologist reported that all occupants experienced non-survivable, blunt-force trauma injuries. However, the front seat occupants had a common vertebral crushing injury that was not found on the rear seat occupant. A likely source of the discrepancy between the front and rear seat occupant injuries was the location of the front seats above the main wing spar, as per the original design.

There are different mechanisms in which energy attenuation can be incorporated into design, but light aircraft are generally limited to the landing gear and seating. Poorly designed seats can produce spinal fractures in ground impacts as low as 8–10 G. In this situation, an unyielding structure, such as a main wing spar, can transmit a force to the occupant of the seat in excess of the ground impact force and the occupant will suffer injuries greater than those expected from the impact. 

Neither the landing gear nor seating of the accident aircraft appeared to include consideration of crashworthiness in the design. The landing gear separated at impact and did not incorporate any stroking mechanism to absorb vertical energy, and the seating did not incorporate energy attenuation into the design. These 2 design deficiencies contributed to the severity of injuries to the occupants. However, the injuries indicated a minimum force experienced by the occupants and not the actual force they experienced. Therefore, it could not be concluded if a design change would have reduced the forces experienced to a survivable level. Despite that, the ATSB noted that similar accident scenarios in type-certified aircraft have been survivable.

Energy attenuating seat designs, such as stroking mechanisms, deforming box structures and rate-sensitive seat bottom cushions can all play a role in reducing the lumbar load experienced by the occupant in an accident. While there is no requirement for amateur-built aircraft to address this issue, it may be feasible for energy absorbing features to be incorporated into the design of some aircraft. 

The CASA advisory circular guidance for amateur-built experimental certificate aircraft (AC 21.4(2)) recommended the delethalization of the cockpit and installing approved seatbelts but was silent on the issue of energy attenuation for the landing gear and seating. However, a 2013 ATSB aviation research report on amateur-built aircraft accidents found they resulted in a higher rate of fatal and serious injuries than factory‑built and certified aircraft. This indicated that the amateur-built industry could benefit from additional guidance in this area. However, as the CASA AC is guidance material and the recommendations may not be practicable for all builders to implement, it has not been raised as a safety issue. 

Crashworthiness of the fuel system

The pathologist’s examination of the pilot indicated they were deceased prior to the post‑crash fire. However, the wreckage examination revealed a near total destruction of the cabin area by fire, while the extremities of the aircraft were relatively undamaged by fire. This was despite the collision occurring in a relatively level attitude in an open paddock with no penetrating objects. 

The main fuel tank was carrying the flight fuel, and it was installed between the instrument panel and the engine firewall, as designed. This made it susceptible to rupturing in a collision and spraying fuel over the engine and occupants, which occurred in the accident. However, the wing fuel tanks installed aft of the main spar, which were a builder modification, were found intact and provided greater separation of the fuel load from the engine and occupants than the main tank. 

The susceptibility of fuel tanks to rupturing in an accident is not new and there have been published recommended design standards to address this for light aircraft since at least 1980 (Johnson et al. 1980 and 1989). They included guidance for the location of fuel tanks, which should consider the location of occupants, ignition sources and probable impact areas. They recommended fuel tanks be located such that as much aircraft structure as possible can crush before the tanks are exposed to direct contact with obstructions.  

The CASA advisory circular guidance for amateur-built experimental certificate aircraft (AC 21.4(2)) recommended reducing the risk of fire hazard. However, the specific design recommendations were limited to the inclusion of a fireproof firewall between the engine compartment and the cabin. It did not recommend or discuss how to incorporate crashworthiness into the design of the fuel system, and specifically the considerations for the location of fuel tanks. 

Given the susceptibility of aircraft fuel tanks to rupturing and the detrimental effect that it can have on post-crash survival, the ATSB concluded that the amateur-built industry could benefit from additional guidance in this area. However, as discussed previously, the CASA AC for amateur-built experimental certificate aircraft is guidance material and the recommendations may not be practicable for all builders to implement. Therefore, it has not been raised as a safety issue.

Other factor that increased risk

The aircraft design did not incorporate energy attenuation in the landing gear and seating and located the fuel tank between the engine firewall and instrument panel, which resulted in a post-crash fire. While these factors increased the severity of the injuries to the occupants, it could not be determined if design changes would have made them non-fatal.

Other factor that increased risk

The Civil Aviation Safety Authority guidance material for amateur-built experimental aircraft did not recommend consideration of the crashworthiness of seating and fuel tank installation. These characteristics within the design of the aircraft increased the risk of occupant injuries in an accident.

Transition training guidance

The accident pilot was a member of a syndicate of 3 pilots who purchased the aircraft on 5 November 2024, 11 days before the accident. While the pilot and another member of the syndicate held instructor ratings, they were for RAAus-registered aircraft, which were 2‑seat aircraft with a maximum take‑off weight of 600 kg. The accident aircraft was a 4‑seat amateur-built experimental certificate aircraft on the CASA register with a maximum take‑off weight of 800 kg.

None of the syndicate pilots were qualified to instruct on this aircraft and none of them met the minimum licence requirements to conduct Phase 1 flight testing, which required a PPL(A) as a minimum. However, they could pilot the aircraft with an RPL as the Phase 1 flight testing of the aircraft was completed by the builder before they purchased it.

In the 11 days after the syndicate purchased the aircraft, ADS-B data recorded 7.7 hours of flying, the majority of which were ferry flights. While the accident pilot likely did most of the flying in the aircraft, the other syndicate members reported that it was unlikely that any aerial work training flights were conducted. One of the syndicate members was concerned about the weight and balance of the aircraft and they had agreed not to conduct any verification flights before the aircraft could be reweighed, which occurred 2 days prior to the accident. In addition, the builder had not conducted any familiarisation flights with them and had not recommended any aerial work exercises for them. Therefore, the ATSB concluded that the pilot had not received any transition training in the aircraft.

A 2013 ATSB aviation research report on amateur-built aircraft accidents found the pilots involved in accidents were significantly more experienced overall than factory-built aircraft accident pilots. However, they were significantly less experienced on the aircraft type that they were flying at the time of the accident, and a quarter of the accidents were from loss of control. 

Previously, in 2012, the US National Transportation Safety Board published a report, which found that pilots who did not seek training for their experimental amateur-built aircraft were overrepresented in accidents. They reported that accidents involving loss of control could be reduced with transition training, which led to a recommendation to the FAA to develop resources for transition training and encourage builders and new owners to complete the training.

The FAA published AC 90-109(A) Transition to unfamiliar aircraft, in 2015. The AC stated that ‘accidents resulting from loss of aircraft control or situational awareness frequently result from pilot unpreparedness for challenges presented by the aircraft’ and provided recommendations for training experience based on aircraft performance and handling characteristics. The AC included an extensive discussion about the variety of stall characteristics that amateur-built aircraft can exhibit and recommended stall avoidance and recovery training from a qualified instructor. 

The FAA AC included a ‘Best Training’ recommendation, which is accomplished in the specific aircraft the pilot intends to fly with a qualified instructor who has recent experience in the same make and model. The accident pilot had previously conducted transition training on the Pitts Special aircraft with an instructor who also had experience with the Morgan Cougar Mk 1 aircraft. Therefore, the ‘best training’ model recommended by the FAA in their AC was an option the syndicate could have pursued.

The CASA advisory circular guidance for amateur-built experimental certificate aircraft (AC 21.4(2)), included recommended safety precautions for the flight-testing phase, which emphasised a graduated process. The purpose of this was for the pilot to learn the behaviour of the aircraft near the centre of the flight envelope before pushing the aircraft out towards the predicted boundary of the envelope. As stated in the AC, ‘Violent or aerobatic manoeuvres should not be attempted until sufficient flight experience has been gained to establish that the aircraft is satisfactorily controllable throughout its normal range of speeds and manoeuvres.’ Despite these recommended precautions for pilots in the flight-testing phase, there were no recommendations for new owners to seek transition training or for sellers to recommend buyers conduct transition training.

The recommended precautionary approach to the flight testing in Phase 1 could equally apply to a new owner of an amateur-built experimental certificate aircraft. Therefore, the ATSB concluded that the amateur-built industry could benefit from further guidance in this area. However, the CASA AC for amateur-built experimental certificate aircraft is guidance material, which may not be practicable to follow in all circumstances, such as a single-seat unique design aircraft. Therefore, it has not been raised as a safety issue.

Other factor that increased risk

The pilot had not conducted transition training and the Civil Aviation Safety Authority guidance material for amateur-built experimental aircraft did not include a recommendation for new owners to receive transition training.

Civil Aviation Safety Authority management of suspension notices

An individual must be a member of RAAus to exercise the privileges of their RPC. Pilots can then use their RPC, issued by RAAus, to obtain a CASA-issued RPL without completing either a CASA pilot exam or flight test, although a CASA flight review was required to exercise the privileges of the RPL. RAAus is an approved self-administering aviation organisation under Civil Aviation Safety Regulation (CASR) 149, which imposes reporting requirements to CASA under CASR 149.425. The reporting line is from RAAus to the CASA Sport and Recreation Aviation Branch (CASA Sport).

The RAAus mandatory reporting requirements to CASA are detailed in their Exposition, specifically in their occurrence and complaints handling manual (OCHM) under the Formal Inquiry process. However, the RAAus Exposition has a safety related suspension (SRS) notice as a risk management tool within the Informal Assessment process. As the SRS sits within the Informal Assessment process, and is not enforcement action, it does not require notification to CASA. However, RAAus, at their own discretion, can notify CASA that they have issued an SRS where they believe the circumstances warrant such notification. 

In August 2024, RAAus elected to notify CASA of the SRS issued against the AFT CFI because of the position the person held within RAAus. In December 2024, they notified CASA that an SRS was issued against the graduates of AFT because of the number of pilot certificate holders involved. However, the accident pilot had never been issued with an SRS despite their previous exam failures and flying history, and therefore, there was never any cause for CASA to receive a notification about the pilot.

On receipt of the RAAus AFT SRS notifications, CASA Sport entered the details into the CASA records management system, but no further action was taken. CASA had a process for follow-up of notifications, which was their Coordinated Enforcement Process (CEP), detailed in their enforcement manual. Within the CEP an investigator could be appointed to make preliminary enquiries and report findings to the Coordinated Enforcement Meeting for consideration. 

After the ATSB received the details of the persons affected by the SRS issued to the graduates of AFT and their CASA licence status, it was found that 2 members also held RPLs at the time their SRSs were issued. In both cases, their RPL was granted based on their RPC which was subsequently suspended by the SRS. The ATSB spoke to one of those individuals, who reported that nobody from CASA had contacted them, but they had acted immediately to complete the remedial actions to have their SRS lifted. However, the second individual’s membership with RAAus had lapsed and they had not had their SRS lifted when the ATSB received the list of affected persons about 7 months after the SRSs were issued. RAAus confirmed that in this case the individual’s membership profile is flagged to address the remedial action if they re-activate their membership and that there were no continuing reporting requirements to CASA beyond the initial notification.

Consequently, an individual could continue to exercise the privileges of a licence issued by CASA based on holding an RPC while their RPC was suspended. This revealed a missing link within CASA’s internal process for handling the notification of an SRS, with no mechanism in place to ensure CASA Sport forwarded relevant information from the SRS to the CASA CEP for review.

Other factor that increased risk

The Civil Aviation Safety Authority (CASA) Sport and Recreation Aviation Branch did not have a process in place to verify if individuals subject to a suspension from a self-administering organisation held a CASA licence and to ensure the information was provided to the CASA Coordinated Enforcement Process for review. (Safety issue)

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 loss of control and collision with terrain involving a Morgan Cougar Mk1 aircraft, registered VH‑LDV, 19 km NNW from West Sale Airport, Victoria, on 16 November 2024. 

Contributing factors

  • The aircraft entered an accelerated stall in a steep turn with insufficient height to recover, resulting in a collision with terrain.
  • It was likely that the pilot had an inadequate understanding of the relationship between angle of bank, load factor and stall speed, which contributed to the pilot not fully understanding the risk of conducting slow steep turns.
  • The pilot had a reported history of conducting low flying and slow steep turns and was likely unaware that, while the accelerated stall characteristics of the accident aircraft were unknown, there were indications that it would be abrupt.
  • The Adventure Flight Training school management practices did not provide the required level of supervision, training and assurance that their graduates had achieved the required level of aeronautical knowledge and understanding for the qualifications they received. (Safety issue)
  • The Recreational Aviation Australia pilot theory examination system did not incorporate sufficient risk controls to ensure that their examination processes were followed as intended and their members had achieved the minimum required knowledge in accordance with the syllabus of flight training. (Safety issue)

Other factors that increased risk

  • The pilot was counselled about unsafe flying practices but was not reported to any authority and therefore no official follow-up action was ever initiated.
  • The aircraft design did not incorporate energy attenuation in the landing gear and seating and located the fuel tank between the engine firewall and instrument panel, which resulted in a post-crash fire. While these factors increased the severity of the injuries to the occupants, it could not be determined if design changes would have made them non-fatal.
  • The aircraft’s front seats were likely fitted with car seatbelts, which unlatched in the accident and resulted in the front seat occupants being ejected from their seats. While this exposed them to additional injuries, the fatal injuries were likely from the aircraft‑ground impact.
  • The Civil Aviation Safety Authority guidance material for amateur-built experimental aircraft did not recommend consideration of the crashworthiness of seating and fuel tank installation. These characteristics within the design of the aircraft increased the risk of occupant injuries in an accident.
  • The pilot had not conducted transition training and the Civil Aviation Safety Authority guidance material for amateur-built experimental aircraft did not include a recommendation for new owners to receive transition training.
  • The Civil Aviation Safety Authority (CASA) Sport and Recreation Aviation Branch did not have a process in place to verify if individuals subject to a suspension from a self-administering organisation held a CASA licence and to ensure the information was provided to the CASA Coordinated Enforcement Process for review. (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 invited to provide submissions to this draft report. 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.

Adventure Flight Training school management

Safety issue number: AO-2024-058-SI-01

Safety issue description: The Adventure Flight Training school management practices did not provide the required level of supervision, training and assurance that their graduates had achieved the required level of aeronautical knowledge and understanding for the qualifications they received.

Recreational Aviation Australia examination system

Safety issue number: AO-2024-058-SI-02

Safety issue description: The Recreational Aviation Australia pilot theory examination system did not incorporate sufficient risk controls to ensure that their examination processes were followed as intended and their members had achieved the minimum required knowledge in accordance with the syllabus of flight training.

Civil Aviation Safety Authority management of suspension notices

Safety issue number: AO-2024-058-SI-03

Safety issue description: The Civil Aviation Safety Authority (CASA) Sport and Recreation Aviation Branch did not have a process in place to verify if individuals subject to a suspension from a self‑administering organisation held a CASA licence and to ensure the information was provided to the CASA Coordinated Enforcement Process for review.

Safety action not associated with an identified safety issue

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. The ATSB has been advised of the following proactive safety action in response to this occurrence.

Additional safety action by Recreational Aviation Australia

  • The draft rewrite of the Recreational Aviation Australia (RAAus) occurrence and complaints handling manual (OCHM) has been updated to include a description of the process for handling a safety related suspension (SRS) for an individual whose membership has lapsed.
  • The draft rewrite of the Recreational Aviation Australia (RAAus) syllabus of flight training has been updated to include further development of the stalling element of the syllabus.

Glossary

ACAdvisory circular
ADS-BAutomatic dependent surveillance-broadcast
AGLAbove ground level
AFTAdventure Flight Training
AMSLAbove mean sea level
CASCalibrated airspeed
CASACivil Aviation Safety Authority
CASRCivil Aviation Safety Regulations
CCTVClosed-circuit television
CEPCoordinated enforcement process
CFIChief flying instructor
FAAFederal Aviation Administration (United States)
FOMFlight operations manual
FTSFlight training school
KDRKnowledge deficiency report
NTSBNational Transportation Safety Board (United States)
OCHMOccurrence and complaints handling manual
OCMSOccurrence and complaints management system
PEXOPilot examination office. The CASA online theory examination system.
PIPerformance indicator
POHPilot operating handbook
RAAusRecreational Aviation Australia
RPCRecreational Pilot Certificate
RPLRecreational Pilot Licence
SRSSafety related suspension
USUnited States

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • accident witnesses
  • the aircraft builder
  • Airservices Australia
  • Bureau of Meteorology
  • chief flying instructors from Recreational Aviation Australia
  • Civil Aviation Safety Authority
  • the former chief flying instructor from Adventure Flight Training
  • former instructors and pilot graduates from Adventure Flight Training
  • Recreational Aviation Australia
  • Victorian Institute of Forensic Medicine
  • Victoria Police
  • video footage of the accident flight.

References

Australian Transport Safety Bureau (2013) 

AR-2007-043(2) (4.26 MB)

(AR-2007-043(2)), accessed 30 May 2025.

Civil Aviation Safety Authority (2000) Amateur-built experimental aircraft – certification (Advisory Circular 21.4(2)), accessed 13 May 2025.

Civil Aviation Safety Authority (2007) Flight instructor manual: aeroplane, accessed 26 March 2025.

Civil Aviation Safety Authority (2022) Experimental certificates (Advisory Circular 21-10 v4.3), accessed 13 May 2025.

Federal Aviation Administration (1986) Static strength substantiation of attachment points for occupant restraint system installations (Advisory Circular 23-4), accessed 24 June 2025.

Federal Aviation Administration (1993) Technical Standard Order: C22g, safety belts (TSO C22g), accessed 24 June 2025.

Federal Aviation Administration (2015) Amateur-built aircraft and ultralight flight testing handbook (Advisory Circular AC 90-89B), accessed 20 May 2025.

Federal Aviation Administration (2015) Transition to unfamiliar aircraft(Advisory Circular 90-109(A)), accessed 3 July 2025.

Society of Automotive Engineers (1986) Aerospace standards: Torso restraint systems (SAE AS 8043), accessed 24 June 2025.

Taylor AM and Moorcroft DM (2023) Seat and occupant response in energy absorbing seats (Civil Aerospace Medical Institute DOT/FAA/AM-23/17), accessed 22 May 2025.

Gratton G (2015) Initial airworthiness: determining the acceptability of new airborne systems, Springer, London.

Johnson NB et al. (1989) Aircraft Crash Survival Design Guide Volume V – Aircraft Postcrash Survival (USAAVSCOM TR 89-D-22E), accessed 3 July 2025.

National Transportation Safety Board (2012) The Safety of Experimental Amateur-Built Aircraft (NTSB/SS-12/01), accessed 28 March 2025.

Payne R and Stech E (1969) Dynamic models of the human body (Aerospace Medical Research Laboratory AMRL-TR-66-157), accessed 3 July 2025.

Roberts et al. (2007) ‘Failure analysis of seat belt buckle inertial release’, Engineering failure analysis, 14(6):1135-1143.

Shanahan DF (28-29 October 2004) Basic Principles of Crashworthiness: Pathological Aspects and Associated Biodynamics in Aircraft Accident Investigation. Madrid, Spain: RTO-EN-HFM-113, accessed 3 July 2025.

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 aircraft builder
  • Civil Aviation Safety Authority
  • the former chief flying instructor from Adventure Flight Training
  • Recreational Aviation Australia. 

Submissions were received from:

  • Civil Aviation Safety Authority
  • the former chief flying instructor from Adventure Flight Training
  • Recreational Aviation Australia. 

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

Appendices

Appendix A – Examination of the flight controls

Introduction

Examination of the flight control system chainring and bearings included a photographic review of the chainring at the wreckage site and as installed in the aircraft pre-accident, which was behind the instrument panel (Figure 12). 

Figure 12: Location and movement of chainring

Location and movement of chainring

Source: ATSB

The part that transmitted roll control from either yoke to the ailerons consisted of 2 chainrings welded together around a hexagonal nut to form one part, hereafter referred to as the ‘chainring’ (Figure 13). The chainring was supported by an inner and outer bearing attached to a support frame. Two grub screws located in threaded holes through the nut were present to secure the chainring to a bearing. 

Figure 13: Front chainring facing pilot (left) and rear chainring facing engine (right)

Front chainring facing pilot (left) and rear chainring facing engine (right)

Source: ATSB

Examination and findings

It was noted that the chainring hexagonal nut appeared to be centrally located on the bearings (Figure 14 left) before the controls were disturbed for onsite examination and that the chainring only separated from the bearings when it was disturbed. Pre- and post‑accident photographs of the flight controls and measurement of the clearance between the chainring and the support frame indicated that the 2 grub screws could only have engaged with the outer bearing (Figure 14 right). 

Figure 14: Location of bolt relative to hexagonal nut (left) and bearings (right)

Location of bolt relative to hexagonal nut (left) and bearings (right)

Source: ATSB

The examination found that the 2 grub screws were not proud of the hexagonal nut inner diameter (Figure 15 [1, 2]) and they had an angular separation of 117° (Figure 15 [3]). The inner bearing and the outer bearing (Figure 15 [4]) were examined, cleaned and re‑examined. No witness marks from the grub screws were identified. The grub screws (Figure 15 [5, 6]) were examined, cleaned and re-examined and no bearing witness marks were identified. Therefore, ATSB examination could not confirm that the grub screws retained the chainring to either bearing.

Figure 15: Condition of grub screws and outer bearing

Condition of grub screws and outer bearing

Source: ATSB

Appendix B – Flight path description

Introduction

The end-of-flight analysis was divided into sections based on the manoeuvring of the aircraft, which have been annotated on the supporting figures. It started with a right turn, followed by a reversal into a left turn followed by 2 full orbits. A third left orbit commenced inside of the second orbit, which led to the stall and collision with terrain. Airservices Australia ADS-B data was used, and altitudes are recorded in 25 ft increments. The last 3 data points, considered unreliable, were inconsistent with the observed CCTV and were potentially predicted points that were not updated prior to the collision.[13] The calibrated airspeed (CAS) range was calculated by the ATSB using a 6 kt mean wind and 12.8 kt wind gust from 124° T recorded at a local weather station 4 km north of the accident site. 

End of flight description

With reference to Figure 16:

  • At the start of the right turn (RH turn – yellow) at 1744:17, the aircraft recorded a groundspeed of 98 kt (87‍–‍91 kt CAS) and an altitude of 825 ft (683 ft AGL). Altitude was maintained through the turn, but groundspeed (and estimated CAS) reduced.
  • The first orbit (First orbit – blue) started at 75 kt groundspeed (78‍–‍85 kt CAS) and an altitude of 825 ft (689 ft AGL) and the aircraft descended about 250 ft during the orbit.
  • The second orbit (Second orbit – orange) started at 82 kt groundspeed (84‍–‍89 kt CAS) and an altitude of 575 ft (442 ft AGL). During the orbit, the aircraft descended and conducted a low pass (Low pass) at 97 kt groundspeed (89‍–‍92 kt CAS) and an altitude of 225 ft (97 ft AGL).
  • A brief straight section (cyan) started at 69 kt groundspeed (72‍–‍79 kt CAS) and an altitude of 400 ft (267 ft AGL) and reduced to 64 kt groundspeed (67‍–‍74 kt CAS) at the start of the final turn (Turn – magenta) at 1746:52.
  • In the final turn at 1746:59 (Stall), the groundspeed reached a minimum of 56 kt (59‍–‍65 kt CAS) at an altitude of 350 ft (221 ft AGL) as the turn radius tightened and an average of 45° angle of bank was required for this turn radius.
  • The last reliable data point was recorded at 1747:02 and indicated a groundspeed of 71 kt (69 kt CAS) at an altitude of 275 ft (143 ft AGL). The abrupt descent and increase in speed were consistent with a conventional stall response.

In the accompanying Figure 17, the start of the right turn (RH turn), start of the first orbit (First orbit), start of the second orbit (Second orbit), low pass (Low pass), start of the final turn (Turn) and stall (Stall) are annotated. The lowest speeds were recorded on the segment from the final turn to the stall, which was also the segment with the smallest turn radius. 

Figure 16: Accident flight path

Accident flight path

Source: Airservices Australia, annotated by the ATSB

Figure 17: Plot of ADS-B data and CAS calculations with the start of each orbit

Plot of ADS-B data and CAS calculations with the start of each orbit

Source: ATSB

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

 

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     Firewall: a fire-resistant bulkhead that separates the engine compartment from the cockpit or cabin area.

[2]     There was a main spar for each wing, which were bolted together underneath the seats to form one continuous main spar.

[3]     METAR: a routine report of meteorological conditions at an aerodrome. METAR are normally issued on the hour and half hour.

[4]     Aerodynamic stall: occurs when airflow separates from the wing’s upper surface and becomes turbulent. A stall occurs at high angles of attack, typically 16° to 18°, and results in reduced lift.

[5]     Maximum coefficient of lift prior to the wing stalling.

[6]     Load factor is the ratio of the lift of an aircraft to its weight and is also referred to as the G load.

[7]     Reference has been made to historical standards as they were prescriptive and in some cases these standards are now performance-based, which can make current standards more difficult to use for comparisons.

[8]     The Adventure Flight Training school ceased operations in August 2024 and was later sold. All references to the AFT CFI in this report are to the CFI from the inception of the school in June 2019 to August 2024.

[9]     This was a different CFI to the CFI who conducted the pilot’s instructor flight test.

[10]    A coordinated positive G pitching and rolling manoeuvre.

[11]    The reference to independence assumes the FTS and examination centre are independent businesses.

[12]    For this report, negative learning is the interference of new leaning with the correct knowledge and/or skills to perform a task and can be detrimental to future task performance compared with no learning.

[13]    The Kalman Filter algorithm used in global navigation satellite systems uses past data to predict future positions.

Preliminary report

Report release date: 18/12/2024

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

At 1730 local time on 16 November 2024, an amateur-built Morgan Cougar Mk 1 aircraft, registered VH-LDV (LDV), with a pilot and 2 passengers onboard, departed from West Sale Airport, Victoria for a flight over the local area. Flightradar24 data indicated the aircraft conducted a left turn on departure and tracked 8 NM (15 km) north of West Sale Airport to the town of Maffra. The aircraft arrived overhead Maffra shortly after 1736 where LDV made a series of turns overhead the town for about 4 minutes. At 1740, the aircraft departed from overhead Maffra and tracked about 6 NM (11 km) west-north-west towards Tinamba West (Figure 1).

The aircraft conducted a right-hand turn overhead a property at Tinamba West, which belonged to relatives of the aircraft occupants, before commencing a series of left-hand turns (orbits) around a point about 1 km to the south-east of the property over open paddocks. The last data point was at 1747, after LDV had commenced a third left-hand orbit, which recorded the aircraft at an altitude of 450 ft at a groundspeed of 60 kt on a track of 073° True (T). 

A closed-circuit television (CCTV) camera, located about 700 m north-north-east of the accident site, captured LDV in a left turn towards the camera. Subsequently, the nose of the aircraft pitched down and the aircraft descended in the left turn behind trees (Figure 2). About 14 seconds later a plume of dark smoke rose up above the trees. The 3 occupants were fatally injured in the accident and the aircraft was destroyed.

Context

Local weather data

A local weather station, about 4 km north of the accident site, recorded the following temperature and wind velocity information at 1745 and 1750 on the day of the accident:

Table 1: Local weather data

Time

Temperature (°C)

Wind speed (kt)

Wind gust (kt)

Wind direction (°T)

1745

27.5

6.2

8.0

124

1750

27.3

6.4

12.8

122

Accident site

The aircraft impacted flat and open terrain at an elevation of about 130 ft and produced a ground scar on a track of 315° T (Figure 3). The length of the wreckage trail was about 30 m from the first ground scar to the propeller spinner, with the fuselage resting on a heading of 303° T. There was a diamond-shaped fuel spray and debris pattern along the wreckage trail.

Fuel was ignited after the ground impact, however, most of the fire damage to the aircraft was confined to the fuselage within the area bounded by the firewall, aft bulkhead (behind rear seats) and the inboard sections of the wings. The wings and tailplane (except the rudder) remained attached to the fuselage. The engine was attached to the firewall and the 3-bladed propeller was attached to the engine. One propeller blade was attached to the hub and the other 2 propeller blades had separated at their roots but were found within the debris field.

Figure 1: Accident flightpath with key timings and locations

Figure 1: Accident flightpath with key timings and locations

Source: Flightradar24 and Google Earth, annotated by the ATSB

Figure 2: CCTV footage of final turn

Figure 2: CCTV footage of final turn

Images subject to visual distortion (fisheye lens effect).

Source: Victoria Police, annotated by the ATSB

Figure 3: Accident site

Figure 3: Accident site

Source: ATSB

Further investigation

To date, the ATSB has:

  • examined the accident site
  • retrieved hardware and avionics from the wreckage
  • collected witness statements, CCTV and drone footage, local weather data, pilot licencing and medical information and aircraft records.

The investigation is continuing and will include:

  • examination and analysis of the avionics unit and aircraft hardware
  • a review of aircraft records, including design and certification standards
  • a review of witness reports
  • interviews with key personnel.

A final report will be released at the conclusion of the investigation. 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. 

Acknowledgements

The ATSB acknowledges the support provided by Victoria Police during the onsite investigation phase.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

 

Occurrence summary

Investigation number AO-2024-058
Occurrence date 16/11/2024
Location 19 km north-north-west of West Sale Airport
State Victoria
Report release date 19/01/2026
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Amateur Built Aircraft
Model Morgan Aero Works Cougar Mk1
Registration VH-LDV
Serial number 6
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point West Sale Airport, Victoria
Destination West Sale Airport, Victoria
Damage Destroyed

Loss of control and collision with terrain involving Cessna 150L, VH-EYU, Bacchus Marsh aircraft landing area, Victoria, on 22 October 2024

Final report

Report release date: 10/07/2025

Investigation summary

What happened

On the morning of 22 October 2024, the pilot of a Cessna Aircraft Company 150L, registered VH‑EYU, was conducting a private flight from Bacchus Marsh aircraft landing area, Victoria. Strong and gusting winds were present. After commencing a take-off roll, the pilot rejected the take-off, before taxiing back to the same runway for a second take‑off.

On the second take-off, the aircraft became airborne and climbed to about 150 ft above the runway, before it pitched steeply nose-up, then the nose dropped suddenly, followed by the left wing dropping. The aircraft then entered a vertical descent, rotating approximately 270° before colliding with terrain. The pilot, who was the sole occupant of the aircraft, was fatally injured, and the aircraft was destroyed. 

What the ATSB found

The ATSB found that shortly after take-off, in strong and gusty wind conditions, the aircraft stalled at a height too low to recover before colliding with terrain. It is probable that the aircraft was too slow on take-off into those conditions, and that inputs made to counteract the crosswind increased the angle of attack of the left wing. These factors, combined with the wind conditions, increased the risk of a quick and unrecoverable stall.

Safety message

While an aerodynamic stall can occur at any airspeed, at any altitude, and with any engine power setting, it is most hazardous during take-off and landing when the aircraft is close to the ground. When gusting conditions are present, pilots should consider waiting for more benign conditions. Guidance advises pilots to conduct their own testing in progressively higher winds to determine both their own capability and that of the aircraft. 

Maintaining the aircraft’s attitude and correcting any change in attitude due to wind gusts during climb, is vital to ensure the critical angle of attack is not exceeded. Reducing the angle of attack by lowering the aircraft nose at the first indication of a stall is the most important immediate response for stall avoidance and recovery. 

Pilots must understand and recognise the conditions which make stall more likely and the symptoms of an approaching stall so they can act to prevent a stall before an unrecoverable condition develops. If pilots judge the weather to be suitable, they should consider climbing out at a higher airspeed to provide a buffer above their aircraft’s stall speed for detection and correction of an impending stall. 

 

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 morning of 22 October 2024, at the Bacchus Marsh aircraft landing area (ALA), Victoria, a Cessna Aircraft Company 150L aircraft, registered VH‑EYU, was being prepared for a private flight under visual flight rules[1] to Lethbridge ALA, Victoria, about 35 km to the southwest. The weather conditions at the time were described as having strong, variable and gusty winds with a temperature of about 27°C.

Closed circuit television (CCTV) showed the pilot arriving for their flight at about 1000. Later, at about 1047, another CCTV camera located at a flying school, recorded the aircraft taxiing to the fuel bowser. After fuelling, the pilot drained a fuel sample from the aircraft fuel tanks and checked the sample. The pilot, who was the sole occupant, climbed in, then started the aircraft and taxied to a run‑up area[2] and performed engine run-up and flight control checks. They then taxied toward runway 27[3] for take‑off (Figure 1).

At about 1110 local time, a common traffic advisory frequency[4] (CTAF) recording captured the pilot stating that they were commencing their take‑off roll. Shortly after, the pilot transmitted another radio call stating that they were rejecting the take‑off. There was no further information provided by the pilot to explain why the take‑off was rejected. 

The rejected take-off attracted the attention of witnesses who were now observing VH‑EYU. The pilot taxied the aircraft off the runway and returned to the end of runway 27. At 1114, the pilot commenced a second take‑off roll.

The witnesses included a flight instructor. They identified that the aircraft appeared unstable after take-off. The CCTV showed the right wing dipping twice during this take‑off, with the pilot levelling the aircraft each time. The flight instructor stated that at about 50 ft, the aircraft pitched up quickly, before the nose was pushed down again.

After the aircraft had passed the runway intersection and reached an altitude of about 150 ft, it pitched steeply upward, before the nose and then the left wing rapidly dropped. The aircraft entered a nose down vertical descent to the left, rotating approximately 270° before colliding heavily with terrain. After the collision, personnel from the flying school attended the accident site and found the pilot fatally injured. The aircraft was destroyed. 

Figure 1: Bacchus Marsh ALA and VH‑EYU approximate flight path (yellow) and accident site

View of Bacchus Marsh ALA showing the runways and approximate flight path of VH-EYU and the accident site. Also shows the CCTV and its field of view, witness and windsock locations.

Source: Google Earth, annotated by the ATSB

Context

Pilot information

The pilot commenced their flight training in July 2019 and held a recreational pilot licence (aeroplane), which was issued on 14 November 2023. They held a single engine aeroplane class rating. The pilot also held navigation, controlled aerodrome, controlled airspace and flight radio endorsements which were issued on 19 April 2024. 

Overall, the pilot had accumulated about 184 hours total aeronautical experience, of which 71.9 hours were in the Cessna 152 and 3.8 hours in the Cessna 150.

The pilot joined Bacchus Marsh Aero Club on 19 August 2024 and had completed 3 club check flights with an independent instructor during September and October 2024. Since joining the club, the pilot had flown a total of 20.1 hours in Cessna 172, Cessna 152 and Cessna 150 aircraft. They had also flown 3.3 hours in a Cessna 152 the previous day. 

The pilot held a Class 2 aviation medical certificate issued by the Civil Aviation Safety Authority, without medical restrictions, which was valid until 19 March 2026.

Post-mortem examination 

The post-mortem and toxicology examinations did not identify any indication of incapacitation or substances that could have affected the pilot’s capacity to perform the flight.

Aircraft information

The Cessna 150L is a high wing, all-metal, 2‑place, single‑engine aircraft with a fixed tricycle landing gear. It is powered by a 4‑cylinder Teledyne‑Continental O‑200‑A engine, driving a 2‑blade fixed‑pitch propeller. VH‑EYU (Figure 2) was manufactured in the United States in 1974 and first registered in Australia in May 1974. It had been owned by the Bacchus Marsh Aero Club since December 2023. 

The aircraft was fitted with a stall warning horn on the left wing, which produces an audible signal to the pilot when the wing is approaching its critical angle of attack (AoA). The Cessna 150L’s stated stall speed in take‑off configuration with wings level was 48 kt.[5]

No crosswind limitation was published in the C150 L model owner’s manual. There was only a need for the manufacturer to demonstrate crosswind capability up to 8.5 kt (20% of the stall speed in a landing configuration). While it is possible that the aircraft may be capable of meeting the controllability standard in higher winds, this had not been established by the manufacturer.

Figure 2: VH-EYU

Photo of VH-EYU, provided by Bacchus Marsh Aero Club.

Source: Bacchus Marsh Aero Club

Recent maintenance history

The last 100‑hour periodic maintenance inspection was conducted on 19 January 2024. At the time of the accident, VH‑EYU had accrued a total time in service of 8,962.3 hours. Maintenance records also showed that since January, the following maintenance had been performed:

  • a 50-hour/6-month oil and filter change
  • the left brake was serviced
  • the flap position indicator spring was replaced.

The aircraft had flown about 36.3 hours since the last scheduled maintenance which was conducted on 21 April 2024. There were no open defects recorded on the maintenance release and no outstanding or overdue maintenance was noted. 

Aerodrome information

Bacchus Marsh aircraft landing area (ALA) was located about 6.5 km south of Bacchus Marsh, Victoria. It consisted of 2 sealed runways, 01/19 in a north‑south direction and 09/27 in the east‑west direction. The ALA was home to the Bacchus Marsh Aero Club, a pilot training school and several gliding clubs, as well as several privately owned aircraft. 

The ALA was in non‑controlled Class G airspace. Aircraft operating in the area did not require clearance and a common traffic advisory frequency (CTAF) was available for pilot‑to‑pilot communication. 

Bacchus Marsh Aero Club

Bacchus Marsh Aero Club operated several single-engine aircraft that were available to hire for approved club members, including the Cessna 150, 152, 172 and 182 models. Due to its status of being a private flying club and to satisfy insurance purposes, the club had a procedure in place for an independent flight instructor to conduct flight checks on new members prior to them being approved to fly club aircraft. 

Site information 

The accident site was in a barley field, 205 m south of the runway 27 centreline and to the west of runway 19/01 (Figure 1). The fuselage was orientated to the north. Ground impact marks were directly under the wreckage indicating no forward momentum. The damage signatures showed that the aircraft had impacted the field in a steep nose down attitude with the initial ground contact at the leading edge of the left wing. Severe disruption of the cockpit area, wing assembly and rear fuselage had occurred from the impact (Figure 3).

Figure 3: VH-EYU at the accident site

View of VH-EYU wreckage, highlighting the wing, fuselage and cockpit damage.

Source: ATSB

Wreckage examination

The ATSB’s examination of the wreckage did not identify any evidence of pre‑existing faults, flight control issues or engine issues and there was no evidence of birdstrike. 

All components were accounted for at the accident site. The right fuel tank had ruptured, while the left tank remained intact. A quantity of fuel was removed from the aircraft fuel tank for onsite testing and was found to be clean and clear of contaminants. Fuel was removed from the carburettor, which was also tested with no water or contaminants found.

The wings and centre fuselage roof section had separated and moved forwards as a result of the impact. Portions of the airframe were removed by first responders prior to ATSB examination, and these were photographed prior to removal. The stall warning horn on the left wing was damaged in the accident sequence and could not be tested for functionality. The flaps were noted to be retracted, which is the position required in the normal take‑off checklist. 

An examination of the seat rails showed that the pilot seat was locked into position and had not moved prior to the accident.

The engine and propeller displayed no pre‑existing damage. The engine was externally examined, and all components were accounted for. The engine was able to be rotated which indicated no significant internal damage had occurred. 

The propeller and flange had fractured from the engine crankshaft and there was evidence of rotation on the fracture surfaces. The propeller displayed minor rotational scoring and rearward bending which was indicative of low rotational energy at the time of impact. 

The throttle control in the cockpit was set at a low power position and had been bent upwards during the impact sequence. 

Survival aspects

The pilot had been wearing a lap/sash seat belt during the accident flight. The extent of the damage to the occupiable space of the aircraft cabin meant that the impact was not considered survivable.

Aircraft stall and spin behaviour 

Aerodynamic stalls

An aerodynamic stall is a rapid decrease in lift and increase in drag caused by the separation of airflow from the wing’s upper surface. A stall occurs when the angle of attack[6] exceeds the wing’s critical angle of attack,[7] resulting in the disruption to the smooth airflow over the wing. This can ordinarily occur at angles of around 16° (Figure 4). Due to the sudden reduction in lift from the wing and rearward movement of the centre of lift, an uncommanded nose‑down pitch ensues. 

The US Federal Aviation Administration (FAA) Airplane Flying Handbook (2021) states that:

• Impending Stall—an impending stall occurs when the AOA causes a stall warning but has not yet reached the critical AOA. Indications of an impending stall can include buffeting… or aural warning.

• Full Stall—a full stall occurs when the critical AOA is exceeded. Indications of a full stall are typically that an uncommanded nose down pitch cannot be readily arrested and may be accompanied by an uncommanded rolling motion... 

The FAA Airplane Flying Handbook (2021) also states that for an impending stall the pilot should:

…immediately reduce AOA once the stall warning device goes off, if installed, or recognizes other cues such as buffeting. The pilot should hold the nose down control input as required to eliminate the stall warning. Then level the wings maintain coordinated flight, and then apply whatever additional power is necessary to return to the desired flightpath.

Figure 4: Effect of increasing angle of attack leading to a stall condition

View of VH-EYU wreckage, highlighting the wing, fuselage and cockpit damage.

Source: CASA AvSafety, annotated by the ATSB

Aerodynamic spins

A spin can result when an aircraft simultaneously stalls and yaws.[8] The yaw can be initiated by rudder application (through manipulation of the rudder pedals) or by yaw effects from a range of factors that include aileron deflection, torque, wind and engine/propeller effects. A spin is characterised by the aircraft following a downward, corkscrew path and requires significantly more altitude for recovery compared to a wings level stall.

The spin recovery procedure stated in the Cessna 150L handbook was:

For recovery from an inadvertent or intentional spin, the following procedure should be used.

• retard the throttle to idle position

• apply full rudder opposite to the direction of rotation

• after one-fourth turn, move the control wheel forward of neutral in a brisk motion

• as rotation stops, neutralize rudder and make a smooth recovery from the resulting dive. 

Application of aileron in the direction of the spin will greatly increase the rotation rate and delay the recovery. Ailerons should be held in a neutral position throughout the spin and the recovery. Intentional spins with flaps extended are prohibited.

To recover from the spin, the pilot requires sufficient height to conduct the procedure and fly away. During the initial stages of a take‑off, there is insufficient height to perform these actions. 

Control input in a crosswind

In a crosswind, to prevent uncommanded roll, the pilot must turn the control yoke into wind. This will move the ailerons to change the relative angle of attack of each wing (Figure 5). The aileron on the into‑wind wing (right in this case) will move up, create a lower angle of attack and produce less lift. The aileron on the downwind wing (left in this case) will move down, creating a higher angle of attack and more lift. Therefore, resisting the rolling moment created by the crosswind.

Figure 5: Effect of aileron use on angle of attack

Figure shows how the camber of a wing changes with aileron deflection and the effect this has on angle of attack. The left wing shows the camber with neutral aileron. The middle wing represents the low wing in a turn and shows that as the aileron is deflected up, the camber of the wing decreases producing a lower angle of attack. The right wing represents the high wing in a turn and shows that as the aileron is deflected downwards, the camber of the wing increases producing a higher angle of attack.

Source: Flight Safety Australia

Guidance

The FAA Airplane Flying Handbook (2021) states for take‑off in gusty conditions that:

During take-offs in a strong, gusty wind, it is advisable that an extra margin of speed be obtained before the airplane is allowed to leave the ground. A take-off at the normal take-off speed may result in a lack of positive control, or a stall, when the airplane encounters a sudden lull in strong, gusty wind, or other turbulent air currents. In this case, the pilot should allow the airplane to stay on the ground longer to attain more speed, then make a smooth, positive rotation to leave the ground.

A Civil Aviation Safety Authority publication AC 91‑02 v1.2 – Suitable places to take‑off and land, and the FAA publication Personal minimums for wind both identify that is the responsibility of the pilot in command to consider the winds and determine if the aircraft can be operated safely in the prevailing conditions. The FAA publication advises pilots to conduct their own testing in progressively higher winds to determine both their own capability and that of the airframe.

Meteorological information

Forecast weather

The planned flight from Bacchus Marsh to Lethbridge was within the Victoria graphical area forecast (GAF)[9] region. The Bureau of Meteorology issued a GAF which included the Bacchus Marsh area, at 0900 on 22 October 2024, and was valid from 1000‍–‍1600. The forecast indicated visibility greater than 10 km and no cloud. A Grid Point Wind and Temperature Forecast was issued by the Bureau of Meteorology at 0525 on 22 October 2024. No wind and temperature was available in the Bacchus Marsh area below 5,000 ft. 

The Bureau of Meteorology issued aerodrome forecasts (TAF)[10] and meteorological aerodrome reports (METAR)[11] for Melbourne, Essendon, Avalon and Ballarat airports. A special meteorological report (SPECI)[12] was also issued, which highlighted that a significant wind gust had been recorded. 

There was no record that the pilot had used any personal login to access weather forecasts prior to their flight, from any official sources. It is unknown if the pilot had checked a forecast via other sources which did not require accounts for access.

Nearby airport weather

The actual weather at Bacchus Marsh ALA was not recorded and not available. However, forecasts and observation reports were available for nearby airports. Table 1 shows the recorded winds at Melbourne Airport leading up to the accident. Melbourne Airport is about 38 km on a bearing of 78° True (° T) from Bacchus Marsh. 

Table 1: Wind speed and direction recorded at Melbourne Airport

ReportTime (local)Bearing ° TWind speed (kt)Time before accident
METAR10000102274 minutes
SPECI100702021, gusting to 3267 minutes
METAR10300202044 minutes
METAR11000102014 minutes

Source: Bureau of Meteorology 

Table 2 shows the recorded winds at Ballarat Airport leading up to the accident. Ballarat Airport is about 59 km on a bearing of 293° T from Bacchus Marsh.

Table 2: Wind speed and direction recorded at Ballarat Airport

ReportTime (local)Bearing ° TWind speed (kt)Time before accident
METAR10003601374 minutes
METAR10303601344 minutes
METAR11003601014 minutes
METAR113036014-16 minutes

Source: Bureau of Meteorology 

Windsock indication

Figure 6 shows VH-EYU taxiing to the runway threshold in the opposite direction but parallel to the take‑off direction. The visible opening of the orange windsock in the background indicates headwind and crosswind components for take‑off.

Figure 6: VH-EYU taxiing prior to second take‑off

VH-EYU taxiing prior to second take-off with the gliding club windsock in the background showing the strong winds at the time.

Source: Supplied

Witness observations of the weather

A number of witnesses described the temperature to be ‘very hot’ (27°C) with strong and gusting winds at the time of the accident. The winds were changing in strength (15–30 kt) and direction (between runways 27 and 01) (Figure 7). A flight instructor, who was an eyewitness to the accident stated that they had cancelled a student’s flight which was to occur later in the day due to the gusty conditions. 

FlySto data from a Cessna 172

A Cessna 172 was flying nearby at the time of the accident and landed at Bacchus Marsh ALA 10 minutes after the accident. Data from the aircraft was uploaded to FlySto.[13] This data recorded the average wind from ground level up to 3,600 ft over a 40‑minute period. The wind direction varied between 262° T and 335° T and at speeds from 6–32 kt. At the time of the accident, this aircraft was located 14 km (8 NM) to the south of Bacchus Marsh ALA and had recorded a 27 kt wind from 290° T while on descent. The temperature recorded upon landing was 29°C.

A component of this data will be normal changes in wind speed and direction due to changes in altitude. For this reason, the average winds referenced in FlySto cannot be used to determine exact conditions at ground level at the time of the accident. 

Figure 7: Witness observation (red arc) and recorded data from FlySto (orange arc), showing approximate wind directions and speeds around time of VH‑EYU take‑off

Witness observation (red arc) and recorded data from FlySto (orange arc), showing approximate wind directions and speeds around time of VH-EYU take-off.

Source: Google Earth, annotated by the ATSB

CCTV and witness video

CCTV recorded the pilot’s arrival at the airport, refuelling, engine run‑up and control checks, and both take‑off runs. All videos showed evidence of strong and gusting winds creating movement in nearby trees and grass. Pitot cover flags on parked aircraft and clothing of people on the apron were observed flapping in the wind. The videos also captured wind noise varying with gusts.

A gliding club located to the east of the ALA had erected a small windsock, which was observed to be moving erratically with the varying wind strength and directions. The witness video provided, showed this windsock to be a smaller commercially available item. Due to its design, it did not meet the standards[14] for wind direction indicators and therefore was not able to provide any information of wind speed. 

Recorded information

CTAF recording

CTAF recordings provided the standard radio transmissions made by the pilot. The recordings also captured the engine sounds each time a transmission was made and showed that the engine sounded normal throughout the duration of the recordings. 

The pilot sounded calm during transmission and voiced no concern with the engine or aircraft after the first rejected take‑off and subsequent return for the second take‑off. 

Aircraft data

The aircraft was not equipped with either a cockpit voice recorder or a flight data recorder, nor was it required to be. Further, there was no active flight tracking equipment or other devices fitted to the aircraft to provide parameters from the accident flight. 

CCTV

The ATSB conducted frame‑by‑frame analysis of the CCTV of the second take‑off. This analysis showed that the groundspeed of the aircraft was 42 kt when the aircraft became airborne.

Related occurrences

AO-2014-023: Cessna 150G, VH-RXM, Loss of control during initial climb, 18 February 2014, Moorabbin Airport

An instructor and student pilot were conducting a trial instructional flight. The aircraft departed with a 3‍–‍4 kt tailwind. The student was operating the aileron and elevator controls, with the instructor operating the rudder. During the initial climb, the student continued to apply back pressure to the control column resulting in a reduction in optimal airspeed, and a higher‑than‑normal aircraft nose attitude. As the instructor attempted to rectify the aircraft’s profile, the right wing dropped, and the aircraft began to descend. 

The instructor’s efforts to recover the aircraft to a normal climb attitude were not successful, and the right side of the aircraft struck the ground. The aircraft bounced, then came to a halt on its left side. The instructor and student egressed through the right door, and both sustained minor injuries. The aircraft was substantially damaged.

NTSB Docket WPR21LA255 Cessna 150L, N1972L, Collision during take‑off, 30 June 2021, Mud Lake Airport (1U2), Terreton, Jefferson County, Idaho, United States

The pilot reported that, upon landing, they saw a crop duster aircraft descending for a short base for landing on the opposite runway. The pilot initiated a go around with the flaps still extended and with a high-density altitude. The aeroplane attained an altitude of about 50 to 100 ft above ground level when the aeroplane stalled, and the left wing dropped. The pilot attempted to recover but did not have enough height before the aeroplane collided with the ground. The aeroplane nosed over and came to rest inverted. The wings and fuselage were substantially damaged. The pilot and passenger sustained serious injuries.

Safety analysis

While there was no evidence that the pilot accessed official weather forecasts on the day of the accident, the pilot may have consulted informal sources, and they were able to experience the weather at Bacchus Marsh prior to departure. Through the movement of the distant windsock, vegetation, pitot covers on parked aircraft and the clothing of people in view of CCTV and video, it was evident that strong gusting winds were present. Noise on the audio track of CCTV also showed gusts were occurring. 

This supported observations of witnesses at the airfield of the conditions throughout the day and at the time of the accident. It is almost certain the wind conditions would have also been evident to the pilot at the time of take‑off. While no weather recording equipment was available at Bacchus Marsh, the evidence available allowed for an estimate of wind varying from west to north at speeds from around 10 kt gusting to 30 kt.  

There was no evidence of problems with the aircraft. The CCTV showed the pilot conducting pre‑take‑off run-up and control checks prior to the first take‑off. Witnesses and analysis of engine sound from CTAF broadcasts from VH‑EYU confirmed that the engine sounded normal. Additionally, post‑accident examination of the aircraft found no evidence of pre‑accident damage which would have affected the flight. 

There was no stated or discernible reason for the first rejected take‑off. The pilot gave no indication of an aircraft serviceability issue in their radio calls. They did not conduct any additional engine run‑up checks or stop the aircraft to perform any exterior airframe inspection. After exiting the runway, the aircraft was taxied without delay to runway 27 for the second take‑off.

On the second take‑off, CCTV analysis showed the groundspeed of the aircraft was 42 kt when the aircraft became airborne. Based on witness observation and the Cessna 150 measurements, the ATSB estimates the aircraft likely had an airspeed of over 50 kt, marginally faster than the 48 kt stall speed of the aircraft. At that time, crosswind was likely to be around 15 kt. 

Witnesses identified and CCTV footage showed that the aircraft’s attitude was unstable after becoming airborne. This indicates that the aircraft was affected by the strong, variable and gusting headwind and crosswind components as the pilot attempted the second take‑off. These uncommanded wind‑driven movements would require constant aircraft attitude adjustments by the pilot.

The flight instructor’s observation of the steep pitch‑up and controlled lowering of the nose which occurred at around 50 ft is consistent with the pilot manipulating the controls to avoid the aircraft descending back onto the runway and to maintain a suitable airspeed and take-off profile. The second uncorrected steep pitch‑up which occurred at around 150 ft, and the subsequent dropping of the left wing and nose resulting in entry into a left incipient spin, was consistent with a fully developed stall and loss of control in flight. This, in turn, was consistent with evidence of the accident site, in which the aircraft wreckage was confined to a small area, with evidence of a high vertical impact and low forward speed. 

In this accident, it is almost certain that, after take‑off and at low level, the aircraft was subjected to a strong and gusting wind. The nature of the prevailing winds increased the likelihood of a drop in airspeed during a phase of flight where the aircraft was flown at a high angle of attack, leading to an impending stall condition. 

It is possible that the impending stall period was very short due to gust strength and the pitch‑up movement created conditions for aerodynamic stall. Further, as the airspeed at take‑off was likely only a few knots higher than the stall speed, there was minimal buffer to account for any sudden drop of wind strength. The evidence indicates that the angle of attack of the wings increased beyond the critical angle, the left wing of the aircraft aerodynamically stalled, and the aircraft entered the incipient phase of a spin. The stalling of the left wing indicates that the angle of attack on the left wing was higher than that on the right. This is likely due to control inputs to counteract a crosswind from the right.

The actions that take place when the aircraft enters a spin require the pilot to retard the throttle. The throttle position in the aircraft was found in a low power setting, which was likely due to the pilot responding to the aircraft entering the incipient phase of a spin. Because the aircraft stalled at a height of about 150 ft, there was insufficient height to recover before the aircraft collided with terrain. 

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 finding is made with respect to the loss of control and collision with terrain involving Cessna 150L, VH-EYU, at Bacchus Marsh aircraft landing area, Victoria, on 22 October 2024. 

Contributing factors

  • It is probable that the aircraft was too slow on take‑off for the strong and gusty wind conditions and significant crosswind, meaning there was minimal buffer to manage an impending stall.  Shortly after take‑off, the aircraft stalled at a height too low to recover, resulting in a collision with terrain. 

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Bacchus Marsh Aero Club
  • Civil Aviation Safety Authority
  • Victoria Police
  • the maintenance organisation for VH-EYU
  • Airservices Australia
  • Bureau of Meteorology
  • Peninsula Aero Club
  • Oxford Aviation Academy
  • TVSA Pilot Training
  • witnesses
  • video footage of the accident flight and other videos taken on the day of the accident
  • recorded CTAF communications. 

References

Civil Aviation Safety Authority 2019, Strong and gusty winds, Civil Aviation Safety Authority, Canberra, ACT Strong and gusty winds | Flight Safety Australia

Civil Aviation Safety Authority 2020, Advisory Circular AC 61-16v1.0, Civil Aviation Safety Authority, Canberra, ACT, https://www.casa.gov.au/spin-avoidance-and-stall-recovery-training

Civil Aviation Safety Authority 2020, Part 139 (Aerodromes) Manual of Standards 2019, Civil Aviation Safety Authority, Canberra, ACT, Part139_(Aerodrome)_MOS.pdf pp 196-198.

Civil Aviation Safety Authority 2019, Rudder, ailerons, stalls and spins, Civil Aviation Safety Authority, Canberra, ACT Rudder, ailerons, stalls and spins | Flight Safety Australia

Civil Aviation Safety Authority 2022, Stalls in the circuit, Civil Aviation Safety Authority, Canberra, ACT Stalls in the circuit | Flight Safety Australia 

Civil Aviation Safety Authority 2022, Advisory Circular AC 91-02v1.2, Civil Aviation Safety Authority, Canberra, ACT https://www.casa.gov.au/guidelines-aeroplanes-mtow-not-exceeding-5-700-kg-suitable-places-take-and-land pp21-22.

Civil Aviation Safety Authority 2024, AvSafety: Preventing a stall at low level, Civil Aviation Safety Authority, Canberra, ACT, Preventing a stall at low level

Federal Aviation Administration 2021, Airplane Flying Handbook (FAA-H-8083-3C), Federal Aviation Administration, Washington DC Airplane Flying Handbook 

National Transportation Safety Board 2015, NTSB Safety Alert 19 / Prevent Aerodynamic Stalls at Low Altitude, National Transportation Safety Board, Washington DC NTSB Safety Alert 19 / Prevent Aerodynamic Stalls at Low Altitude

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 Civil Aviation Safety Authority
  • the Bacchus Marsh Aero Club
  • the National Transportation Safety Board.

Any submissions from those parties were reviewed and, where considered appropriate, the text of the draft report was amended accordingly.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

[2]      Run-up area: a designated area of an airfield where pilots can perform functional pre-flight checks of aircraft systems.

[3]      Runway number: the number represents the magnetic heading of the runway. In this case, ‘27’ represents a magnetic heading of 270°.

[4]      Common traffic advisory frequency (CTAF): radio frequency on which pilots monitor and use to make positional broadcasts when operating within a 10 NM radius of the airport.

[5]      The Cessna 150L Owner’s Manual lists all speeds in miles per hour. 

[6]      Angle of attack: the acute angle between the chord line of the airfoil and the direction of the relative wind.

[7]      Critical angle of attack. the angle of attack at which a wing stalls regardless of airspeed, flight attitude, or weight.

[8]      Yaw: the motion of an aircraft about its vertical or normal axis.

[9]      Graphical Area Forecast (GAF): provides information on weather, cloud, visibility, icing, turbulence and freezing level in a graphical layout with supporting text.

[10]    Aerodrome Forecast (TAF): a statement of meteorological conditions expected for the specified period of time in the airspace within 5 nautical miles (9 km) of the aerodrome reference point.

[11]    METAR (Meteorological Aerodrome Report) is a routine aerodrome weather report issued at half hourly time intervals. The report ordinarily covers an area of 8 km radius from the aerodrome reference point.

[12]    SPECI: a special report of meteorological conditions, issued when one or more elements meet specified criteria significant to aviation.

[13]    FlySto is a web-based application that allows for upload and interpretation of flight data from a range of avionics devices.

[14]    The standards for windsocks are outlined in Part 139 Aerodrome Manual of Standards, which provides information for windsocks and their interpretation.

Preliminary report

Report release date: 16/12/2024

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 22 October 2024, at about 1110 local time, the pilot of a Cessna 150L registered VH‑EYU, commenced the take-off roll on runway 27[1] at Bacchus Marsh airfield, Victoria (Figure 1). Shortly after, the pilot made a radio call stating that they were rejecting the take‑off. The aircraft was then taxied off the runway and returned to the threshold of runway 27, where at 1114 the pilot recommenced the take-off.

Several witnesses at the airfield observed the second take-off and identified that, during its initial climb, the aircraft attitude pitched steeply upward. Witnesses described that the left wing dropped rapidly. The aircraft then entered a vertical descent, rotating approximately 270° before colliding heavily with terrain. The pilot (who was the sole occupant) sustained fatal injuries and the aircraft was destroyed. There was no post-impact fire. 

Figure 1: Bacchus Marsh airfield and VH-EYU accident location

Figure 1: Bacchus Marsh airfield and VH-EYU accident location

Source: Google Earth, annotated by the ATSB

Context

Pilot information

The pilot held a Recreational Pilot Licence (Aeroplane) and a Class 2 Aviation Medical Certificate, valid until March 2026. The pilot held a single engine aeroplane rating, and navigation endorsement. At the time of the accident, the pilot had about 184 hours total aeronautical experience, of which 3.8 hours were in Cessna 150 aircraft. 

Aircraft information

The Cessna 150L is a high wing, all-metal, 2-place, single-engine aircraft with a fixed tricycle landing gear. It is powered by a 4-cylinder Teledyne-Continental O-200-A engine, driving a 2-blade fixed-pitch propeller. The aircraft was manufactured by Cessna in the United States in 1974 and first registered in Australia in May 1974. It had been owned by the Bacchus Marsh Aero Club since December 2023 (Figure 2).

The last 100-hour periodic maintenance inspection was conducted on 19 January 2024. At the time of the accident, it had accrued a total time in service of 8,962.3 hours. The aircraft had flown about 34 hours since the last scheduled maintenance which was conducted on 21 April 2024. There no known defects documented on the aircraft maintenance release.

Figure 2: VH-EYU

Figure 2: VH-EYU

Source: Bacchus Marsh Aero Club

Aerodrome information

Bacchus Marsh airfield is located about 6.5 km south of Bacchus Marsh, Victoria, Australia. It is an aircraft landing area (ALA) consisting of 2 sealed north/south (01/19) and east/west (09/27) runways. The airfield was primarily used by the Bacchus Marsh Aero Club, a pilot training school and several gliding clubs. 

Bacchus Marsh Aero Club

Bacchus Marsh Aero Club operates several high wing single-engine aircraft available to hire for approved club members, including the Cessna 150, 152, 172 and 182. The pilot joined the club on 19 August 2024 and subsequently completed check rides with an instructor on 13 September, 27 September and 4 October 2024.

Site information 

ATSB investigators first attended the accident site on 23 October 2024. The aircraft had impacted into a barley field 205 m south of the runway 27 centreline and was orientated toward the north. The damage signatures confirmed that it had impacted the field in a steep nose down attitude. Severe disruption of the cockpit area, the wing assembly and rear fuselage had occurred from the impact (Figure 3).

Figure 3: VH-EYU at the accident site near to the airfield runways

Figure 3: VH-EYU at the accident site near to the airfield runways

Source: ATSB

Wreckage examination

The ATSB conducted a preliminary examination of the aircraft wreckage in the field, then moved the wreckage to a secure hangar for detailed examination. The examinations identified:

  • no evidence of pre-impact defects with the flight controls or structure
  • all components were accounted for at the accident site
  • the engine was able to be rotated and there were no obvious defects upon external examination
  • the throttle setting was at idle position (low power)
  • rotational damage signatures to the propeller were minimal which indicated a low engine power setting at the time of the impact
  • the propeller and flange had fractured from the engine crankshaft.

A quantity of fuel was removed from the aircraft for onsite testing and was found to be clean and clear of contaminants. 

Meteorological information

Forecast

The Bureau of Meteorology (BoM) issued a graphical area forecast that included the Bacchus Marsh area, at 0900 on 22 October 2024, that was valid from 1000–1600. The forecast indicated visibility greater than 10 km and no cloud. 

Witness observations of the weather

Witnesses at Bacchus Marsh airfield described the wind at the time of the accident as strong and gusty, changing in direction and strength. A flight instructor stated that they had cancelled a student’s flight due to the increasingly gusty conditions which were present on the day. 

Meteorological observations 

There was no BoM aerodrome weather information specifically for Bacchus Marsh, but the ATSB obtained meteorological observations for the surrounding areas of Melbourne, Essendon, Avalon and Ballarat airports (Figure 4).

Figure 4: Location of Bacchus Marsh airfield relative to nearby aerodrome weather forecast locations

Figure 4: Location of Bacchus Marsh airfield relative to nearby aerodrome weather forecast locations

Source: Google Earth, annotated by the ATSB

Table 1 shows the recorded winds in meteorological aerodrome reports (METAR)[2] and special meteorological reports (SPECI)[3] issued between 1000 and 1200 on 22 October 2024. The wind direction is in degrees true[4] rounded to the nearest 10 degrees. The wind direction and speed are the mean values over 10 minutes, and the gust is the maximum wind speed over a 2-minute period.

Table 1: Aerodrome wind observations

TimeMelbourneEssendonAvalonBallarat
1000010° 22 kt360° 15 kt020° 8 kt360° 13 kt
1007[1]020° 21 kt gusting to 32 kt   
1020[1] 360° 17 kt gusting to 27 kt  
1030020° 20 kt360° 16 kt360° 10 kt360° 13 kt
1100010° 20 kt360° 18 kt330° 12 kt360° 10 kt
1130010° 19 kt360° 15 kt350° 12 kt360° 14 kt
1200010° 17 kt360° 15 kt350° 11 kt360° 16 kt

[1] SPECI

Further investigation

To date, the ATSB has:

  • examined the aircraft wreckage
  • conducted witness interviews
  • reviewed common traffic advisory frequency recordings
  • reviewed CCTV footage and mobile phone footage
  • obtained weather information.

The investigation is continuing and will include:

  • further review of the pilot’s experience, qualifications and training
  • further review and analysis of recorded CCTV and mobile phone footage
  • further analysis of the weather conditions
  • examination of the aircraft maintenance history.

A final report will be released at the conclusion of the investigation. 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. 

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     Runway number: the number represents the magnetic heading of the runway. In this case, 27 represents a magnetic heading of 270°.

[2]     METAR: a routine aerodrome weather report issued at half hourly time intervals.

[3]     SPECI: a special aerodrome weather report issued only when meteorological parameters meet specific criteria.

[4]     The magnetic variation at Bacchus Marsh was 11° east.

Occurrence summary

Investigation number AO-2024-053
Occurrence date 22/10/2024
Location Bacchus Marsh aircraft landing area
State Victoria
Report release date 10/07/2025
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model 150L
Registration VH-EYU
Serial number 15075559
Aircraft operator Bacchus Marsh Aero Club
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Bacchus Marsh, Victoria
Destination Bacchus Marsh, Victoria
Damage Destroyed

Loss of control and collision with terrain involving Robinson R44, King Leopold Ranges, Western Australia, on 22 June 2024

Occurrence Briefs are concise reports that detail the facts surrounding a transport safety occurrence, as received in the initial notification and any follow-up enquiries. They provide an opportunity to share safety messages in the absence of an investigation. Because occurrence briefs are not investigations under the Transport Safety Investigation Act 2003, the information in them is de-identified. 

What happened

On 22 June 2024 at about 0915 local time, a Robinson R44 was conducting a scenic flight with a pilot and 2 passengers onboard, over the King Leopold Ranges, Western Australia. While in a slow downwind cruise of 30 kt at about 500 feet above ground level, the pilot detected a loss of tail rotor effectiveness as well as a loss of rotor RPM. They attempted to correct and continue flight, however, were unable to maintain height and performed an emergency landing over rocky terrain. The helicopter landed flat on both skids, however skidded down a slope on the left side and rolled to the left, impacting a rock ledge. The helicopter was substantially damaged (Figure 1).

Figure 1: Helicopter accident site

Figure 1: Helicopter accident site

Safety message

Pilots are reminded of the effect of density altitude on aircraft performance. Robinson Helicopter Company (RHC) pilot operating handbooks provide performance charts to assist pilots with planning flights. These include a density altitude chart and out-of-ground effect hover ceiling chart to provide an expectation of aircraft performance during flight. Operators are encouraged to conduct periodic reviews with pilots on aircraft performance and limitations in a range of weather conditions.

Pilots must be prepared to respond immediately to a low RPM warning and ensure they are familiar with the power curve and associated airspeeds for their particular helicopter. 

RHC advises pilots of their piston-engine helicopters to roll on the throttle while lowering the collective lever and, during forward flight apply aft cyclic as per the low RPM recovery procedure. 

The RHC website provides training videos for higher risk flight conditions, including several presentations on rotor energy management which could be beneficial to pilots during their initial training, upgrades and flight reviews.

Pilots are encouraged to review low RPM rotor stall RHC (SN-24), aerial survey and photo flights RHC (SN-34) and unanticipated yaw RHC (SN-42) in the Robinson Helicopter Company Safety Notices.

About this report

Decisions regarding whether to conduct an investigation, and the scope of an investigation, are based on many factors, including the level of safety benefit likely to be obtained from an investigation. For this occurrence, no investigation has been conducted and the ATSB did not verify the accuracy of the information. A brief description has been written using information supplied in the notification and any follow-up information in order to produce a short summary report, and allow for greater industry awareness of potential safety issues and possible safety actions.

Occurrence summary

Mode of transport Aviation
Occurrence ID AB-2024-030
Occurrence date 22/06/2024
Location Near Leopold Downs
State Western Australia
Occurrence class Serious Incident
Aviation occurrence category Loss of control
Highest injury level None
Brief release date 05/09/2024

Aircraft details

Manufacturer Robinson Helicopter Co
Model R44 II
Sector Helicopter
Operation type Part 133 Air transport operations - rotorcraft
Departure point Mount Hart Station Aircraft Landing Area, WA
Destination Mount Hart Station Aircraft Landing Area, WA
Damage Substantial

Collision with terrain involving Oficinas Gerais de Material Aeronautico DHC-1 MK 22 Chipmunk, VH-POR, at Jandakot Airport, Western Australia, on 26 April 2024

Final report

Report release date: 25/03/2025

Investigation summary

What happened

On 26 April 2024, the pilot (who was the sole occupant) of a DHC‑1 MK 22 Chipmunk, registered VH‑POR, taxied for take‑off from Jandakot Airport, Western Australia for a private flight. A witness took photographs of the aircraft taxiing past, which showed the engine cowl latches on the left side had not been secured.

After the aircraft took off, another witness near the runway recalled seeing something ‘flapping’ on the aircraft. This witness, and witnesses in a nearby building looking through a window, observed the aircraft turn to the left at low height near the end of the runway. The pilot declared a MAYDAY, and camera footage showed the aircraft’s angle of bank increasing and the aircraft descending before colliding with terrain.

An instructor, with a student pilot who had just landed, taxied to a position adjacent to the accident site to provide assistance. The pilot was initially treated onsite by Royal Flying Doctor Service personnel before being transported to hospital. Later, the pilot succumbed to injuries.

What the ATSB found

Prior to commencing taxi, the pilot did not detect that the engine cowl latches on the left side had been left unfastened. After take-off, the cowl was free to open and close in flight. Witness reports and camera footage show the engine cowl was opening and closing until the aircraft collided with terrain.

While likely distracted by the flapping engine cowl and experiencing a high cognitive workload, the pilot made a MAYDAY call while commencing a low‑level turn, likely in an attempt to return to land. During the turn, the aircraft’s angle of bank increased, and the aircraft aerodynamically stalled and collided with terrain.

When the aircraft collided with terrain, the upper structure between the front and rear cockpits, corresponding to the attach point for the front cockpit shoulder harness, was torn away from its mountings. Most noteworthy, all 12 rivets (6 per side) that attached the structure to the mountings had sheared. ATSB examination of the rivets using metallurgical equipment found that all of the rivets were of a non-conforming type, and half were estimated to be about one-third of the specification strength. This compromised the crashworthiness of the aircraft, however, the effect on survivability in this accident could not be determined.

What has been done as a result

To advise DHC‑1 Chipmunk maintainers and owners of the importance of ensuring modifications are carried out to the required specification, the ATSB issued a safety advisory notice (AO‑2024‑013‑SAN‑01) on 11 September 2024.

The Portuguese Office for the Prevention and Investigation of Accidents in Civil Aviation and Rail (GPIAAF) published information from the ATSB’s safety advisory notice (AO-2024-013-SAN-01) in its Civil Aviation Quarterly Bulletin Publication (issue QB 03/2024) in October 2024.

Safety message

This accident illustrates the importance of pre-flight preparation to reduce the likelihood of an abnormal occurrence. In addition, pilots are reminded of the hazards that can lead to loss of control events, such as high angles of bank, especially at low heights, which should be avoided to reduce the risk of a stall/spin accident.

The modification carried out on the accident aircraft significantly compromised its crashworthiness. Maintainers and owners are reminded that when making modifications to any aircraft, that they are carried out to the required specification, or during maintenance returned to that specification.

 

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 26 April 2024, the pilot (who was the sole occupant) of a DHC‑1 MK 22 ‘Chipmunk’, registered VH‑POR, commenced taxi for take-off at Jandakot Airport, Western Australia for a private flight. The weather was clear, with the wind about 10 kt from the north‑west.

A witness on the southern apron took photographs of the aircraft taxiing past, which show the engine cowl latches on the left side were oriented vertically[1] (Figure 1).

Figure 1: VH‑POR taxiing for take-off

Figure 1: VH‑POR taxiing for take-off

The gap at the rear edge of the cowl is normally present when the cowl is closed fully. Image source: Witness, annotated by the ATSB

The pilot continued to taxi to the end of runway 24L and at 1313 was given clearance to take off. Camera footage recorded the aircraft commencing its take-off roll and becoming airborne about halfway along the runway’s length (Figure 2).

Figure 2: Approximate flight path

Figure 2: Approximate flight path

Image source: Google Earth, annotated by the ATSB

One witness, located at the run-up bay, recalled seeing something ‘flapping’ on the aircraft during the take-off. This witness, and witnesses in a nearby building looking through a window, observed the aircraft turn to the left at low height near the end of runway 24L. There were no reports of an abnormal engine sound. At 1314:24, the pilot made a radio call stating ‘papa oscar romeo papa oscar romeo MAYDAY MAYDAY MAYDAY’.[2]

The camera footage showed the aircraft’s angle of bank increasing and the aircraft descending before colliding with terrain.

A camera at a building about 180 m to the south‑east of the accident site recorded the engine cowling on the left side opening and closing in the seconds prior to the aircraft’s collision with terrain (Figure 3). 

Figure 3: VH-POR showing engine cowl open

Figure 3: VH-POR showing engine cowl open

Image source: Supplied, annotated by the ATSB

An instructor with a student pilot who had just landed recalled seeing the aircraft’s engine cowl open and the collision with terrain. The instructor and student taxied to a position adjacent to the accident site to provide assistance. The pilot was initially treated onsite by Royal Flying Doctor Service personnel before being transported to hospital. The pilot succumbed to injuries 3 days later.

Context

Pilot information

The pilot was issued a private pilot licence (aeroplanes) by the United Kingdom Civil Aviation Authority in 1977. The pilot was issued with an Australian private pilot licence (aeroplanes) in 1978 and held a current Civil Aviation Safety Regulation Part 61 Private Pilot (Aeroplane) Licence. The pilot held a valid class 2 civil aviation medical certificate with no restrictions and was required to wear vision correction when flying. 

The pilot had no reported significant medical conditions. Toxicology and post-mortem examination reports were not available at the time of publication. 

At the time of the accident, the pilot had accumulated about 330 hours total aeronautical experience. In the 12 months prior to the accident, the pilot had flown about 5 hours, 3.5 hours of which was in VH‑POR. The pilot completed a flight review in December 2023, and their last flight prior to the accident was in January 2024. Both flights were in VH-POR.

Aircraft information

General information

The DHC-1 MK 22 Chipmunk is a 2 seat, low-wing aircraft constructed predominantly from light aluminium alloy with fabric covered wings and control surfaces. The aircraft was designed for ab initio military flight training. The Chipmunk was manufactured in Canada, the United Kingdom, and Portugal. 

VH‑POR was manufactured in Portugal under licence by Oficinas Gerais de Material Aeronautico[3] (OGMA) in 1958 as a DHC-1 MK 20, and later modified to MK 22 specifications.[4] It was powered by a 4 cylinder de Havilland Gipsy Major 10 MK 2 engine driving a fixed-pitch wooden propeller. The aircraft operated in service with the Portuguese Air Force before being operated privately in the United States from 1979. It was first registered in Australia in 2010, and the accident pilot had been the registration holder since 2018. 

A periodic inspection and minor maintenance tasks were carried out on 22 March 2024. At the time of the accident, the aircraft had accumulated 2,082 flying hours.

Engine cowl

Access to the engine is via a cowling door on either side. The cowl doors are hinged at the top and fastened by 2 latches at the bottom of each cowl. The latches are attached to the lower engine cowl and when in the vertical position pass through holes on the cowling doors (Figure 4, left). To fasten the cowl, the latches are pulled outboard, further compressing a pre‑compressed spring, and turned aft (1/4 turn) to the horizontal position. Releasing the latch then fastens the cowl. The latches are held in place by the spring and prevented from unfastening by a tab (Figure 4, right). There was no evidence of pre‑impact damage to the engine cowl latches fitted to VH‑POR (see Wreckage and impact information).

Figure 4: DHC-1 Chipmunk cowl latch detail (exemplar aircraft, left side shown)

Figure 4: DHC-1 Chipmunk cowl latch detail (exemplar aircraft, left side shown)

Image source: Supplied, annotated by the ATSB

Fuel line priming and carburettor flooding

A number of actions are required to start the engine of a DHC-1 Chipmunk, including to ensure the lines from the fuel pumps to the carburettor have been filled with fuel (primed). This is accomplished by the use of a hand lever on the rear fuel pump which is accessed via an opening on the left engine cowl. After this is accomplished, the carburettor is flooded[5] using a pull-wire that is accessed via another opening on the left engine cowl. The left engine cowl can be opened to allow direct access instead of using the access openings to perform these actions.

Crashworthiness modification

Modification H.268

The upper structure between the front and rear cockpits of the DHC-1 Chipmunk, corresponding to the attach point for the front cockpit shoulder harness, had 2 mountings, called gussets (Figure 5 and Figure 6).

Figure 5: DHC-1 Chipmunk cockpit showing gusset and shoulder harness locations (exemplar aircraft)

Figure 5: DHC-1 Chipmunk cockpit showing gusset and shoulder harness locations (exemplar aircraft)

Image source: Alan K. Radecki, annotated by the ATSB

Figure 6: Modification H.268 gusset and rivet location (left side shown)

Figure 6: Modification H.268 gusset and rivet location (left side shown)

Image source: ATSB, de Havilland Support Ltd, annotated by the ATSB

In October 1966, modification H.268 was issued[6] to strengthen this structure. The modification was classified as ‘desirable’, and was applicable to DHC-1 Chipmunk marks 20 (which included Portuguese-manufactured aircraft), 21, 22, 22A and 23. The modification replaced the original aluminium alloy gussets with high-tensile steel. The modification required the forward row of rivets attaching the structure to the gussets to be part number SP85 mushroom head rivets, and the rear row to be part number AS2230 countersunk rivets. Later testing by the manufacturer subjected the front cockpit shoulder harness of a modified aircraft to a 22 G load, with no failures. 

Information on the ATSB examination of relevant components of VH‑POR is presented in Wreckage and impact information.

Technical news sheet 154

On 29 March 1966, in the United Kingdom there was a fatal accident involving a DHC-1 MK 22 Chipmunk, registered G‑ARME. Following the investigation into the accident, Hawker Siddeley[7] issued technical news sheet TNS 154 in May 1967. Compliance with TNS 154 was classified as ‘mandatory’, to be carried out prior to 31 July 1967. The heading indicated that it was applicable to ‘CT(C1)’ series aircraft, meaning those in civilian (non-military) service. TNS 154 also stated that it was for English production Chipmunk aircraft. The ATSB was advised by de Havilland Support Ltd (DHSL) that since the 1990s, the Portuguese Air Force and military operators of DHC-1 Chipmunks in the United Kingdom have been briefed when new technical news sheets were issued.

The procedure to fulfil TNS 154 is summarised as follows. After gaining access to the gussets securing the upper structure between the front and rear cockpits to the fuselage, dimensional checks (diameter and edge distance) were to be made on the 3 bolt holes in each gusset. If either criterion was not met, the aircraft was required to have modification H.268 embodied. Additionally, each gusset was to be inspected for the presence of the correct number of securing rivets.

Applicability to Portuguese manufactured DHC-1 Chipmunks

All Chipmunk aircraft manufactured in Portugal had been originally built to MK 20 specifications. When issued in 1966, modification H.268 was applicable to Portuguese manufactured MK 20 Chipmunks and remained applicable when those aircraft were converted to MK 22 (civilian) specifications. When issued in 1967, TNS 154 was not applicable for MK 20 (military) aircraft but became applicable to any aircraft modified to MK 22 (civilian) specifications.

The available Portuguese records for VH‑POR did not include entries for modification H.268 or TNS 154. The records did however show that various modifications and civilian TNS inspection requirements had been carried out when VH-POR was operating in Portuguese Air Force service.

The aircraft manufacturer (OGMA) advised that it had no record of being advised about modification H.268 by Hawker Siddeley, and that it had received technical news sheet TNS 154 in 1997.

Additionally, the ATSB were advised[8] that the Portuguese Air Force held no records for aircraft serial number OGMA 44 (VH‑POR). However, of the 6 remaining DHC-1 Chipmunk aircraft still operating in Portuguese Air Force service in 2025, records indicate that:

  • no aircraft have records of modification H.268 being embodied
  • records showed inspections in accordance with TNS 154, and that modification H.268 was not needed.
Australian airworthiness requirements

In 1966, the Australian Department of Civil Aviation (DCA) issued airworthiness advisory circular AAC 1‑3 Chipmunk aircraft – crashworthiness. This document outlined 3 modifications that were considered by the DCA as ‘highly desirable’. The modifications were for the installation of inertia reel shoulder harnesses, energy absorbing seat inserts, and for the modification of the front cockpit shoulder harness mount point structure. For the latter, AAC 1‑3 stated that:

The structural shell which carries the front shoulder harness attachment is in itself quite rigid, but fails by tearing at its attachment to the aircraft upper longerons when subjected to a high load applied through the shoulder harness. A sheet aluminium alloy doubler running from the shoulder harness attach point down to the longeron bolts and using existing rivets and bolts will provide the reinforcement desired.

This modification could be seen in historical photographs of DHC-1 Chipmunk aircraft in Royal Aero Club service in Australia.

In response to TNS 154, an Australian airworthiness directive, AD/DHC-1/18, was issued in August 1967 and mandated that compliance to TNS 154 was required before 1 January 1968. In 2008, AD/DHC-1/18 was cancelled on the basis that ‘as all affected aircraft would have been inspected and modified by now, this AD is no longer required.’ 

VH-POR crashworthiness modification

No records from the aircraft’s time in the United States were available for examination. Maintenance records from the time the aircraft was registered in Australia were available to the investigation, along with incomplete records from the aircraft’s service in Portugal. There was no record available showing whether modification H.268 or the requirements of technical news sheet TNS 154 having been carried out on VH‑POR. Examination by the ATSB of the aircraft showed that modification H.268 had been embodied (the relevant mountings, or gussets, were steel as required by H.268) at an unknown time, and with non-conforming rivets (see Rivet examination).

Aerodrome information

Jandakot Airport is a certified, controlled airport. It had 3 asphalt runways:

  • 06R/24L[9] (1,150-m long)
  • 06L/24R (in parallel with 06R/24L and 1,392-m long)
  • 12/30 (1,508-m long).

The accident flight took off from runway 24L, which was only available from sunrise to sunset, and at all times the circuit direction was left (turns made in the circuit were to the left). 

Wreckage and impact information

General information

The wreckage had been relocated to a secure hangar on Jandakot Airport prior to the arrival of ATSB investigators. Further, the accident site had been decontaminated after the wreckage was relocated due to a significant fuel spill. Therefore, a detailed survey of the impact location was not possible. However, in addition to the 2 cameras showing the flight and accident, the ATSB obtained photographs of the site provided by first responders.

The ATSB examined the wreckage in the hangar. All major aircraft components were accounted for, and the propeller showed evidence that the engine was running at impact. The engine control pushrods in the engine compartment had been fractured by impact forces. Flight control continuity was established. The wing flaps were assessed to have likely been in the retracted position at the time of impact, which is a permissible setting for take-off.

Damage to the engine cowl latches was indicative of the latches being correctly fastened on the right side but unfastened on the left at the time of impact. The engine cowls and latches were otherwise undamaged.

Cockpit structure

The ATSB found that on impact the upper structure between the front and rear cockpits, corresponding to the attach point for the front cockpit shoulder harness, was torn away from its mountings (Figure 7). All 12 rivets (6 per side) that attached the structure to the mountings had sheared. 

Figure 7: Detached upper structure showing harness attach point and location of sheared rivets

Figure 7: Detached upper structure showing harness attach point and location of sheared rivets

Upper structure has been placed in position for the photograph and is representative of its position immediately post-accident. Image source: ATSB, de Havilland Support Ltd (detail), annotated by the ATSB

Rivet examination

The gussets fitted to VH‑POR were steel, rather than aluminium alloy, which indicated that modification H.268 had been embodied. This modification also required the use of part number SP85 and AS2230 rivets. Both types were required to be manufactured to British standard L.86, which was an aluminium alloy that included copper and magnesium.[10] The standard also specified that the rivets were to be anodised (a surface treatment) and coloured violet.

The sheared rivets and coatings from VH‑POR were examined and tested by the ATSB using metallurgical equipment. It was determined that:

  • The material composition of the rear row of rivets (countersunk) was consistent with pure or near-pure aluminium[11] and therefore a non-conforming specification. Testing indicated a significant reduction in strength, estimated to be about one-third of the strength of the specification rivets.
  • The material composition of the forward row of rivets (mushroom head) was consistent with an alloy consistent with L.86. The rivets were coated with a gold-coloured chromate conversion coating instead of violet anodising. ATSB testing indicated that the strength of the rivets met or exceeded literature values for L.86 alloy.

The presence of the non-conforming rivets significantly reduced the integrity of the structure retaining the front cockpit restraint, and thereby compromised the crashworthiness of the aircraft. This non-conforming modification may be present in other Chipmunk aircraft, in which case it would likely affect survivability in an accident.

To advise DHC‑1 Chipmunk maintainers and owners of the importance of carrying out this modification to the required specification, the ATSB issued a safety advisory notice (AO‑2024‑013‑SAN‑01) on 11 September 2024.

Survival aspects

The ATSB attempted to determine the impact velocity and deceleration imparted on the aircraft’s structure during the accident. As there was no recorded data[12], calculations of deceleration during the impact were made using estimates of the aircraft’s velocity and angle of impact. Additionally, assumptions were required in the analysis resulting in a wide range of possible outcomes across the established threshold for human tolerance. As a result, the ATSB was unable to definitively determine whether the impact accelerations were within or exceeded the levels considered tolerable for human survival. 

Similarly, it was not possible to determine whether the longitudinal force was greater than the force that the restraints were known to withstand in testing (22 G) and therefore not possible to determine whether the correct rivets would also have failed had they been fitted.

Flight path analysis

The pilot’s handbook and pilot’s notes for the Chipmunk state that normal take-off speed is 45 kt, climb speed is 70 kt, and stall speed is 47 kt with the wing flaps up. The ATSB estimated from camera footage of the accident flight that the aircraft’s angle of bank increased to about 55° during its turn while maintaining about 130 ft, immediately prior to the descent (Figure 8). It was not possible to accurately estimate its airspeed at this time.

Figure 8: VH-POR angle of bank during left turn after take-off

Figure 8: VH-POR angle of bank during left turn after take-off

Image source: Supplied, annotated by the ATSB

The aerodynamic stall[13] speed of aircraft in a steady turn increases appreciably with an angle of bank greater than 30°, and at angles greater than 45° there is a rapid increase in stall speed. At 55° angle of bank, stall speed is increased by about 32%. The Chipmunk’s stall speed in a 55° steady turn while maintaining level flight would have therefore been about 62 kt.

Guidance on manoeuvring at low level

The 2024 Civil Aviation Safety Authority information card Preventing a stall at low level (2405.4903) provided tips for pilots including:

Manoeuvring at low level increases the chances of a low-level stall.

Remember that turns and any application of ‘G’ will increase the stall speed – sometimes dramatically.

Try to avoid using more than 30 degrees of bank in the circuit. Use coordinated controls.

The 2010 ATSB educational publication Avoidable Accidents No. 3 - Managing partial power loss after take-off in single-engine aircraft (AR-2010-055) noted that:

A turnback requires accurate flying during a period of high stress to prevent a stall and possibly a spin occurring. If an aerodynamic stall and or spin occurs, given that these circumstances are likely to be at low level, there is little likelihood of a successful recovery. With careful management and by being aware of the hazards that can lead to loss of control events, the risk of being involved in a stall/spin accident can be reduced.

During a non-normal or emergency event in-flight, and particularly in a critical phase of flight such as initial climb and final approach, there can be a high cognitive workload placed on the pilot. In such a situation, a pilot’s hierarchical priorities are to ensure the aircraft remains in controlled flight, navigate (such as to a suitable landing area) and, if time permits, communicate the nature of the emergency to air traffic control enabling them to respond appropriately. These hierarchical priorities are colloquially known as ‘aviate, navigate, communicate’.

Related occurrences

The ATSB was advised by DHSL of an occurrence in the United Kingdom where the left engine cowl of a DHC-1 Chipmunk opened in flight. The pilot of that aircraft reported that by sideslipping[14] the aircraft, the cowling slammed shut until the aircraft was straightened for touchdown when it opened again. The aircraft landed safely, and there was no reported damage to the cowling.

Additionally, a DHC-1 Chipmunk subject matter expert advised the ATSB of 3 other occurrences in Australia involving a Chipmunk where the left cowl opened in flight. The ATSB was able to obtain formal investigation records about one of these accidents (described below). On the other 2 occasions there were no reported issues with performance or controllability, and both aircraft landed safely. There was minor damage to the left cowl on one aircraft.

Accident involving DHC-1 MK 10 Chipmunk, VH-RFW at Bull Creek, Western Australia on 19 September 1959

On 19 September 1959, the pilot of a DHC‑1 MK 10 Chipmunk, registered VH‑RFW, had difficulty recovering from a spin during aerobatic manoeuvres and entered a dive, during which the left engine cowl opened then slammed shut. The investigation report did not state whether the cowl stayed shut or opened again. When the pilot applied power to return to Perth Airport, the engine did not respond, and the throttle lever was reportedly loose. The pilot elected to land at an emergency airstrip at Bull Creek. During landing the pilot inadvertently approached downwind and the aircraft overshot the runway, collided with trees and caught fire. The pilot survived and was treated for burns in hospital. The investigation found that the left engine cowl had been unfastened, and had damaged the throttle linkage as it slammed closed in flight.

Safety analysis

Engine cowl latches

In preparing the aircraft for flight, it is possible that the fuel line priming and carburettor flooding functions were carried out by opening the left engine cowl, rather than via the openings on it, and that the cowl was then left unsecured. Alternatively, the cowl might have been opened for another reason or left unfastened from previous activities. In any case, the pilot did not detect that the engine cowl latches on the left side had been left unfastened prior to boarding the aircraft and commencing taxi. After take-off, the cowl was free to open and close in flight.

Left turn after take-off

This accident, and the 1959 accident involving VH‑RFW, demonstrate that the engine cowl being free to open and close in‑flight can be hazardous. However, while by no means a benign event, there were 2 anecdotally reported occasions involving DHC-1 Chipmunks where the left engine cowl was not secured. With these, there were no reported performance or controllability issues, and the aircraft were able to be recovered safely. Nevertheless, in this case the engine cowl began flapping after take-off, and the pilot would have been likely distracted and experiencing a high cognitive workload while managing the in-flight emergency.

From the available evidence, there were no indications of pre-impact defects, configuration issues (other than the cowl being unfastened), or controllability issues. There were no engine issues, and it is very likely the aircraft’s engine controls had not been damaged in a similar way to the accident involving VH‑RFW. The reason for the pilot commencing a left turn after take-off could not be determined, though it is possible that the pilot was attempting to recover by conducting a circuit and returning to Jandakot Airport.

During the turn the pilot made a MAYDAY call, and the aircraft’s angle of bank then increased until reaching about 55°. The rapid increase in stall speed associated with higher angles of bank resulted in the aircraft aerodynamically stalling at a height where recovery was not possible. 

While the pilot was appropriately licenced and had completed a flight review using VH‑POR about 4 months prior to the accident, the extent to which the pilot’s limited recent experience influenced their actions could not be established.

Non-conforming rivets and survivability

On an unknown date, potentially many years previously, rivets that did not conform to the design specification had been fitted to the mountings between the front and rear cockpits. Importantly, the attach point for the front cockpit shoulder harness was attached to this structure. Testing indicated a significant reduction in strength in half of the rivets (the aft 3 rivets on both sides), estimated to be about one-third of the strength of the specification rivets. 

During the accident, all of the rivets securing the structure failed. However, it was not possible to establish whether the correct rivets would also have failed, and the impact deceleration alone may have been above expected human tolerance. Therefore, it was not possible to establish whether the presence of non-conforming rivets affected survivability in this instance. Regardless, the presence of non-conforming rivets was a latent threat to the aircraft’s crashworthiness and reduced the likelihood of an accident being survivable. 

As complete records for the aircraft were not available, it was not possible to determine where or when the rivets had been installed. The 6 DHC-1 Chipmunk aircraft still operating in Portuguese Air Force service had been inspected but not modified, and this likely occurred after the aircraft manufacturer (OGMA) received TNS 154 in 1997. It is therefore likely that VH‑POR had not been inspected under TNS 154 in Portugal prior to 1979 when the aircraft was privately registered in the United States, and modification H.268 was likely carried out some time later. While the existing rivets would have been replaced when the H.268 modification was made, some or all may have been replaced again later.

This non-conforming modification may be present in other Chipmunk aircraft, in which case it would likely affect survivability in an accident.

Australian airworthiness directive

The Australian airworthiness directive relating to TNS 154, AD/DHC-1/18, was issued when the aircraft operating in Australia had been manufactured in England, and therefore meeting the stipulated applicability for TNS 154. The airworthiness directive was cancelled in 2008 (before VH‑POR was first registered in Australia) on the expectation that all aircraft by that time had been inspected and modified. Read strictly, the cancellation did not account for the possibility that an aircraft could have been inspected, met the dimensional criterion, and therefore not modified in accordance with H.268.

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 collision with terrain involving Oficinas Gerais de Material Aeronautico DHC-1 MK 22 Chipmunk, VH‑POR at Jandakot Airport, Western Australia on 26 April 2024.

Contributing factors

  • The pilot did not detect that the engine cowl latches on the left side had been left unfastened prior to commencing taxi. After take-off, the cowl was free to open and close in flight.
  • During a low level, high angle of bank turn, and while the pilot was likely distracted by the flapping engine cowl and experiencing a high cognitive workload, the aircraft aerodynamically stalled and collided with terrain.

Other factors that increased risk

  • Rivets that did not conform to the design specification had been fitted to mountings between the front and rear cockpits and significantly reduced the integrity of the structure retaining the front cockpit restraint. This compromised the crashworthiness of the aircraft; however, the effect on survivability in this accident could not be determined.

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.  The ATSB has been advised of the following proactive safety action in response to this occurrence.

Safety advisory notice to DHC-1 Chipmunk maintainers and owners

SAN number:AO-2024-013-SAN-01
SAN release date:11 September 2024

The ATSB advises DHC-1 Chipmunk maintainers and owners to be aware that fitment of non‑conforming rivets where the upper structure between the front and rear cockpits attaches to the gussets on either side could significantly compromise the crashworthiness of the aircraft.

Those conducting work on aircraft must ensure modifications are carried out to the required specification, or during maintenance returned to that specification.

Proactive safety action taken by the GPIAAF

Action number:AO-2024-013-PSA-01
Action organisation:Gabinete de Prevenção e Investigação de Acidentes com Aeronaves e de Acidentes Ferroviários (GPIAAF)
Action status:Closed

The Portuguese Office for the Prevention and Investigation of Accidents in Civil Aviation and Rail (GPIAAF) published information from the ATSB’s safety advisory notice (AO-2024-013-SAN-01) in its Civil Aviation Quarterly Bulletin Publication (issue QB 03/2024) in October 2024.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Air Accidents Investigation Branch (United Kingdom)
  • Airservices Australia
  • Civil Aviation Safety Authority
  • de Havilland Support Ltd
  • Gabinete de Prevenção e Investigação de Acidentes com Aeronaves e de Acidentes Ferroviários (Portugal)
  • National Archives of Australia
  • OGMA Indústria Aeronáutica de Portugal
  • Portuguese Air Force
  • Royal Aero Club of Western Australia
  • Western Australia Police Force
  • accident witnesses
  • camera footage of the accident flight and other photographs taken on the day of the accident
  • subject matter experts.

Acknowledgement

The ATSB would like to acknowledge the significant assistance provided by multiple DHC-1 Chipmunk subject matter experts during the onsite investigation phase and evidence collection activities.

References

Hurt, Jr., H.H. (1965). Aerodynamics for naval aviators (NAVAIR 00-80T-80) University of Southern California, United States.

National Archives of Australia B638, 6/659/133 - Accident at Bulls [sic] Creek on 19/9/1959: DHC‑1 A/C: VH‑RFW [includes photographs and plans], 1959 - 1960.

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:

  • Air Accidents Investigation Branch (United Kingdom)
  • Civil Aviation Safety Authority
  • De Havilland Aircraft of Canada Limited
  • de Havilland Support Ltd
  • Gabinete de Prevenção e Investigação de Acidentes com Aeronaves e de Acidentes Ferroviários (Portugal)
  • Royal Aero Club of Western Australia
  • Transport Safety Board of Canada.

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]      See Engine cowl.

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

[3]      Currently known as OGMA Indústria Aeronáutica de Portugal.

[4]      The DHC-1 MK 20 was the export version of the original MK 10 manufactured for military service in the United Kingdom. For civilian use, aircraft were modified to MK 22 and other specifications.

[5]      Flooding fills the carburettor float bowl by depressing its float and overriding the float’s normal function which is to shut off fuel flow to the carburettor bowl when it reaches a set level.

[6]      Modification H.268 was amended in March 1967.

[7]      Hawker Siddeley was the type certificate holder at the time.

[8]      The Portuguese Office for the Prevention and Investigation of Accidents in Civil Aviation and Rail (GPIAAF) established contact with the Portuguese Air Force on the ATSB’s behalf and provided a response.

[9]      Runway numbering: represents the magnetic heading closest to the runway orientation (for example, runway 24L is oriented 236º magnetic).

[10]    International equivalences were Alloy Designation 2117, US specification AMS7222, and European specification ENAW-AlCu2.5Mg).

[11]    The composition was not determined exactly; there was >99% aluminium with some alloying iron and silicon, consistent with 1000-series aluminium, although the specific alloy could not be determined.

[12]    The aircraft was not fitted with flight or engine recording devices, and there was no requirement to do so.

[13]    Aerodynamic stall occurs when airflow separates from the wing’s upper surface and becomes turbulent. A stall occurs at high angles of attack, typically 16˚ to 18˚, and results in reduced lift.

[14]    Sideslipping is a manoeuvre in which controls are deliberately crossed, for example to sideslip to the left, the aircraft is banked to left while right rudder is applied.

Preliminary report

Report release date: 04/07/2024

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 26 April 2024, the pilot (who was the sole occupant) of a DHC‑1 MK 22 Chipmunk, registered VH‑POR, commenced taxi for take-off at Jandakot Airport, Western Australia for a private flight. The weather was clear, with the wind about 10 kt from the north‑west.

A witness on the southern apron took photographs of the aircraft taxiing past, which show the engine cowl latches on the left side were oriented vertically[1] (Figure 1).

Figure 1: VH‑POR taxiing for take-off

Figure 1: VH‑POR taxiing for take-off

The gap at the rear edge of the cowl is normally present when the cowl is closed fully.

Image source: Witness, annotated by the ATSB.

The pilot continued to taxi to the end of runway 24L and at 1313 was given clearance to take off. Camera footage recorded the aircraft commencing its take-off roll and becoming airborne about halfway along the runway’s length (Figure 2).

Figure 2: Approximate flight path

Figure 2: Approximate flight path

Image source: Google Earth, annotated by the ATSB.

One witness, located at the run-up bay, recalled seeing something ‘flapping’ on the aircraft during the take-off. This witness, and witnesses in a nearby building looking through a window, observed the aircraft roll to the left at low height near the end of runway 24L. There were no reports of an abnormal engine sound. At 1314:24, the pilot made a radio call stating ‘papa oscar romeo papa oscar romeo MAYDAY MAYDAY MAYDAY’.[2]

The camera footage showed the aircraft’s angle of bank increasing and the aircraft descending before colliding with terrain. A camera at a building about 180 m to the south‑east of the accident site recorded the engine cowling on the left side opening and closing in the seconds prior to the aircraft’s collision with terrain (Figure 3).

Figure 3: VH-POR showing engine cowl open

Figure 3: VH-POR showing engine cowl open

Image source: Supplied, annotated by the ATSB.

An instructor with a student pilot who had just landed recalled seeing the aircraft’s engine cowl open and the collision with terrain. The instructor and student taxied to a position adjacent to the accident site to provide assistance. The pilot was initially treated on‑site by Royal Flying Doctor Service personnel before being transported to hospital. Later, the pilot succumbed to injuries.

Context

Pilot information

The pilot was issued a private pilot licence (aeroplanes) by the United Kingdom Civil Aviation Authority in 1977. The pilot was issued with an Australian private pilot licence (aeroplanes) in 1978 and held a current Civil Aviation Safety Regulation Part 61 Private Pilot (Aeroplane) Licence. The pilot held a valid class 2 civil aviation medical certificate with no restrictions and was required to wear vision correction when flying. 

The pilot had no reported significant medical conditions. Toxicology and post-mortem examination reports were not available at the time of publication. 

At the time of the accident, the pilot had accumulated about 330 hours total aeronautical experience.

Aircraft information

General information

The DHC-1 MK 22 Chipmunk is a 2 seat, low-wing aircraft constructed predominantly from light aluminium alloy with fabric covered wings and control surfaces. The aircraft was designed for ab initio military flight training. 

VH-POR was manufactured in Portugal under licence by Oficinas Gerais de Material Aeronautico (OGMA) in 1958. It was powered by a 4 cylinder de Havilland Gipsy Major 10 MK 2 engine driving a fixed-pitch wooden propeller. It was first registered in Australia in 2010 and the accident pilot had been the registration holder since 2018. 

A periodic inspection and minor maintenance tasks were carried out on 22 March 2024. At the time of the accident, the aircraft had accumulated 2,082 flying hours.

Engine cowl

Access to the engine is via a cowling door on either side. The cowl doors are hinged at the top and fastened by 2 latches at the bottom of each cowl. The latches are attached to the lower engine cowl and when in the vertical position pass through holes on the cowling doors (Figure 4, left). To fasten the cowl, the latches are pulled outboard, further compressing a pre‑compressed spring, and turned clockwise (1/4 turn) to the horizontal position. Releasing the latch fastens the cowl and the latches are held in place by the spring and prevented from turning counterclockwise by a tab (Figure 4, right).

Figure 4: DHC-1 Chipmunk cowl latch detail (exemplar aircraft)

Figure 4: DHC-1 Chipmunk cowl latch detail (exemplar aircraft)

Image source: Supplied, annotated by the ATSB.

Wreckage and impact information

The wreckage had been relocated to a secure hangar on Jandakot Airport prior to the arrival of ATSB investigators. Further, the accident site had been repatriated due to a significant fuel spill after the wreckage was relocated. Therefore, a detailed survey of the impact location was not possible. However, in addition to the 2 cameras showing the flight and accident, the ATSB obtained photographs of the site provided by first responders.

The ATSB examined the wreckage in the hangar. All major aircraft components were accounted for, and the propeller showed evidence that the engine was running at impact. Flight control continuity was established, and the wing flaps were assessed to have likely been in the retracted position at the time of impact.

Damage to the engine cowl latches was indicative of the latches being correctly fastened on the right side and unfastened on the left.

Further investigation

To date, the ATSB has:

  • examined the wreckage
  • recovered aircraft components associated with occupant restraints
  • interviewed relevant parties and eyewitnesses
  • collected aircraft, pilot, airport, and operator documentation
  • conducted preliminary analysis of video recordings and ATC transmissions.

The investigation is continuing and will include further:

  • examination of the aircraft components
  • review of aircraft and pilot documentation
  • analysis of the aircraft flight path, and impact forces.

A final report will be released at the conclusion of the investigation. 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. 

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     See Engine cowl.

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

Occurrence summary

Investigation number AO-2024-013
Occurrence date 26/04/2024
Location Jandakot Airport
State Western Australia
Report release date 25/03/2025
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Aircraft preparation, Collision with terrain, Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer De Havilland Canada/De Havilland Aircraft of Canada
Model DHC-1 MK 22
Registration VH-POR
Serial number OGMA 44
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Jandakot Airport, Western Australia
Destination Jandakot Airport, Western Australia
Damage Substantial

Loss of control and collision with terrain involving Beechcraft E55, VH-OMD, Cowra Airport, New South Wales, on 11 April 2024

Final report

Report release date: 22/08/2024

Executive summary

What happened

On 11 April 2024, a flight instructor and student pilot were conducting a dual training flight under the instrument flight rules in a Beechcraft E55 aircraft, registered VH-OMD and operated by Fly Oz. The aircraft departed from Cowra Airport, New South Wales, and conducted instrument approaches to Goulburn and Canberra Airports, before returning to Cowra. 

As the aircraft tracked over the Cowra non-directional beacon (NDB) to conduct a practise instrument approach to runway 15, the instructor simulated a failure of the left engine by moving the mixture lever to the idle cut-off position. The student continued the approach with the left engine inoperative and the propeller windmilling, then joined the circuit for runway 33 on the crosswind leg. 

During the landing flare, the instructor initiated a go-around. The aircraft rapidly yawed and rolled to the left and impacted the ground in an almost vertical nose-down attitude before coming to rest inverted. The flight crew sustained minor injuries and the aircraft was substantially damaged. 

What the ATSB found

The ATSB found that the instructor moved the left engine mixture lever to idle cut-off to simulate an engine failure over the navigation aid, and it was likely that they unintentionally did not subsequently move the lever to rich and ensure the engine was restarted and available for instant use, when attempting to set zero thrust on the downwind leg of the circuit. As a result, the instructor initiated a go-around below the minimum control speed, unaware the left engine was inoperative, resulting in an asymmetric loss of control.

The ATSB also found that Fly Oz's asymmetric training procedure involved failing one engine using the mixture control without confirmation the engine was subsequently restarted, rather than reducing throttle to simulate zero thrust in accordance with the Beechcraft E55 Airplane Flight Manual. The use of the throttle to simulate an engine failure ensures the engine is available for immediate use, whereas using the mixture control increased the risk of an undetected inoperative engine during descent and landing, and the associated loss of control. 

What has been done as a result

Fly Oz amended its multi-engine training to simulate engine failures only using throttle at any height. It has also taken the following proactive safety action:

  • Following a simulated engine failure, zero thrust is to be set immediately after the student has completed the engine failure drills.
  • The instructor standardisation manuals were being updated to include a requirement that both the student and instructor confirm that the pitch, power and mixture controls are set back to normal 2‑engine configuration during checks on final. This is now a call out item, ensuring that both pilots are satisfied with the correct settings.

Safety message

In conventional twin-engine aeroplanes, loss of power on one engine can lead to a loss of directional control and an accident if there is insufficient height above the ground to recover. 

Aircraft manufacturers’ procedures for one engine inoperative training should be followed in the first instance. In this case, the manufacturer required the throttle be used to simulate an engine failure. In addition to the manufacturer’s procedures, Civil Aviation Safety Authority guidance recommended using the throttle rather than the mixture to simulate an engine failure when at low level – such as asymmetric instrument approaches. This ensures power can quickly be restored if needed. 

Accidents as a result of engine malfunctions in twin-engine aeroplanes are rare, but often fatal. As such, training to manage one engine inoperative flight is important, but should not introduce unnecessary risks.

 

The occurrence

On 11 April 2024, a student pilot and flight instructor were conducting a dual instructional flight in a Beechcraft E55 aircraft, registered VH-OMD and operated by Fly Oz. The flight was the student’s third multi-engine aeroplane navigation exercise. The flight was to be conducted under the instrument flight rules,[1] from Cowra, New South Wales (NSW), to Canberra, Australian Capital Territory, and return. As the flight was conducted almost entirely in visual meteorological conditions,[2] the student wore a view limiting device or ‘hood’, to simulate flying in cloud or poor visibility. 

OzRunways[3] flight path data showed that the aircraft departed Cowra Airport at 1156 local time. En route to Canberra, the student conducted an instrument approach[4] to Goulburn Airport, NSW, but did not land there. The student then conducted an instrument approach to Canberra, landed and taxied to the general aviation apron. After a short break, and without shutting down the engines, the aircraft departed Canberra Airport at 1323 via a standard instrument departure. The aircraft climbed to 10,000 ft above mean sea level (AMSL), tracked via waypoint AVBEG and commenced a descent when 35 NM from Cowra (Figure 1).

Figure 1: VH-OMD track from Cowra to Goulburn, Canberra and return via AVBEG

Figure 1: VH-OMD track from Cowra to Goulburn, Canberra and return via AVBEG

Source: OzRunways data overlaid on Google Earth, annotated by the ATSB

At 1404, the aircraft passed over the Cowra non-directional beacon (NDB)[5] at about 3,600 ft AMSL (2,600 ft above ground level) and commenced the NDB approach to runway 15. The instructor then simulated an engine failure, by pulling the left engine mixture control lever to the idle cut-off position. In that position, no fuel would flow from the injectors to the engine, but the magnetos would continue generating spark, and the propeller blades would windmill[6] unless feathered.[7]

In response, the student conducted initial engine failure checks and identified that the left engine was inoperative. At that time, the flight crew did not complete the operator’s one engine inoperative procedure to either feather the left propeller or set zero thrust to simulate a feathered propeller (see the section titled Simulated one engine inoperative – Fly Oz procedures). The flight path data showed that, consistent with the simulated left engine failure, the aircraft deviated left of the published outbound track, and tracked outbound on the published inbound track for about 2 minutes, before starting to correct to the right (Figure 2).

Figure 2: VH-OMD track overlaid on published Cowra NDB approach 

Figure 2: VH-OMD track overlaid on published Cowra NDB approach

Source: OzRunways and Airservices Australia data overlaid on Google Earth, annotated by the ATSB

About 4 minutes after passing over the NDB, the aircraft commenced a left inbound turn and was established within the required 5° tolerance of the published inbound track about 5 NM from the threshold of runway 15. 

The Cowra Airport common traffic advisory frequency (CTAF) was not recorded. However, the student reported making the standard radio calls, including broadcasting when inbound and on downwind, and using the word ‘asymmetric’ in their calls to alert others that they were practising one engine inoperative procedures. The instructor reported communicating with the pilots of 2 other aircraft operating in the circuit at the time. Those 2 aircraft were operating on runway 33, which was the most into wind runway. To sequence with the circuit traffic, the instructor advised the student they were now ‘visual’ and could lift the hood and track to join the crosswind leg of the circuit for runway 33.

The instructor thought that they had set zero thrust either when inbound on the instrument approach or on the downwind leg of the circuit, and recalled first asking the student whether they wanted zero thrust set. However, the student recalled prompting the instructor to set zero thrust on downwind. The instructor reported that their normal procedure for setting zero thrust was to bring the propeller pitch lever to the feather detent, then push the mixture lever forward to rich and gradually move the left throttle lever forward until the manifold pressure gauge read about 10 inches Hg.[8] The instructor reported that, although they usually moved the engine/propeller controls slowly, there would be a detectable yaw[9] associated with returning power to the inoperative engine. 

The student and instructor both reported that the student’s normal downwind checks included checking both mixture levers were in the fully rich position, but neither could recall when the checks were done. The student recalled extending the landing gear either just before, or when turning onto, the base leg of the circuit. Neither the instructor nor the student recalled when the student extended the approach (15°) stage of flaps. After turning onto final, the student reported completing their pre-landing checks by pushing both pitch levers forward to the full fine position, checking they had 3 green lights, which indicated the landing gear was down and locked, and electing not to extend full (30°) flap for landing. 

A review of recorded flight data identified that the aircraft crossed the runway threshold at 1416:01 aligned with the runway centreline. The instructor reported that the student commenced the flare[10] a bit high and therefore directed them to add some power to cushion the landing. The instructor further reported that when the student added power, the aircraft immediately yawed significantly to the left such that it was no longer aligned with the runway. In response, the instructor called for a go-around. The student could not recall being asked to add power and reported that the main landing gear touched down on the runway before the instructor initiated the go-around. However, the instructor recalled that the wheels did not touch down and that the go-around commenced about 30–50 ft above the runway. 

OzRunways data showed that the aircraft started to deviate left of the runway centreline at 1416:14 at 69 kt ground speed, but there was insufficient recorded information to determine whether or not it touched down prior to that occurring. The instructor reported taking control of the aircraft from the student and verifying that both throttle levers were fully forward. Assessing that the yaw was due to left rudder input by the student, the instructor called for the student to let go of the controls and applied right rudder, but was unsuccessful in regaining control of the aircraft. A witness facing away from the runway heard what they assessed as one engine power up and turned to see the aircraft 10–20 ft above the runway, pitched 10–12° nose-up, and in a rapid left roll (Figure 3).

Figure 3: VH-OMD track along the runway, accident site and witness location 

Figure 3: VH-OMD track along the runway, accident site and witness location 

Source: OzRunways data overlaid on Google Earth, annotated by the ATSB

The aircraft collided with the ground in a nearly vertical nose-down attitude and came to rest inverted (Figure 4). The student and instructor sustained minor injuries and it is possible that their recollection of events may have been affected by trauma associated with the collision. The aircraft was substantially damaged. 

Figure 4: VH-OMD accident site

Figure 4: VH-OMD accident site

Source: Cowra Council

Context

Personnel information 

The student was enrolled in Fly Oz’s commercial pilot licence (aeroplane), multi-engine aeroplane class and command instrument rating integrated flight training course. At the time of the accident, the student held a private pilot licence (aeroplane) and had accrued 247 hours of flying time, 11 of those in VH-OMD (all in the last 90 days), with 7 hours recorded as instrument flight time.

The instructor held a commercial pilot licence (aeroplane), with multi-engine aeroplane class and command instrument ratings, which they had attained at Fly Oz. The instructor had accrued 850 hours of flying time, of which 82.8 were in VH-OMD (70.3 of those in the last 90 days and 43.5 hours recorded as instrument flight time). 

Aircraft information 

General

VH-OMD was a Beechcraft E55 (serial number TE-970), manufactured in the United States (US) in 1974 and first registered in Australia in 1990. Fly Oz was not the registered operator[11] of VH‑OMD but hired the aircraft and had been using it for training and charter operations for about 6 months. 

The aircraft was powered by 2 Continental IO-520-C 6-cylinder, horizontally‑opposed, fuel‑injected engines rated at 285 hp at 2,700 RPM and fitted with 2 Hartzell 3-bladed full‑feathering constant speed propellers (PHC-C3YF-2UF). 

The maintenance release[12] current on the accident day showed that the aircraft was approved to operate under instrument flight rules and charter categories. The maintenance release was issued on 9 April 2024 with an aircraft total time in service of 4,622.1 hours. Since then, 2 flights totalling 8.8 hours flight time had been conducted prior to the accident day. There were no recorded defects or outstanding maintenance.

The aircraft departed with a take-off weight of 2,190 kg and operated within the approved weight and balance envelope during the flight, at mid-range centres of gravity. 

Fuel system

The fuel system included multiple individual fuel cells with a total capacity of 651 L. The fuel cells had elastomeric liners capable of tolerating large deformation without rupture. In an impact, this reduced the likelihood of an explosive fuel-air mist compared with unlined metal tanks. The fuel selector was an OFF-ON-CROSSFEED arrangement for each engine with the selector panel located on the floor.

Each engine had a 2-speed electric (auxiliary) fuel boost pump, which could be selected at HIGH pressure, OFF or LOW pressure. High was used for providing fuel pressure to prime the engine before start and provided near maximum engine performance should the engine‑driven pump fail. The airplane flight manual (AFM) stated that the ‘high pressure position should not be selected while the engine is operating except in the event of engine driven pump failure since the high pressure mode supplies a greater pressure than can be accepted by the injector system for a reduced power condition’. 

Front seats and restraints

The front seats were fitted with 4-point restraints, each consisting of 2 lap straps connected to the seat frame and 2 shoulder harness straps connected via a Y belt to an inertia reel attached to the upper cabin structure. The inertia reel was designed with a locking device that would secure the shoulder straps in the event of sudden forward movement or impact. The seats could be adjusted forward or aft, with the seat guides sliding along 3 seat rails: 2 main (aft) and 1 centre (forward) (Figure 5). The seat is retained at the desired adjustment by a spring-loaded locking pin engaging in one of the forward centre rail holes. Shims could be added to the inside of the guide to ensure locking pin alignment.

Figure 5: Seat rails

Figure 5: Seat rails

Left seat position depicted in image, right seat rails identical. Source: ATSB and Beechcraft, annotated by ATSB

Meteorological information 

The Bureau of Meteorology graphical area and grid point wind and temperature forecasts covering Cowra Airport for the accident time predicted primarily clear skies, visibility greater than 10 km and a light northerly wind. 

Consistent with the forecasts, Cowra Airport’s recorded meteorological conditions[13] at 1400 included wind at 3 kt from 010°, and at 1430 the wind was 5 kt from 310°. At both those times, there was no cloud, the temperature was 21 °C and QNH 1019 hPa.[14] 

Recorded data

OzRunways[15] data from the student’s electronic flight bag application contained aircraft track, altitude and ground speed. The ATSB also obtained flight data from the aircraft’s Garmin electronic flight instrument (EFI), which included 40 data parameters. Figure 6 shows key parameters from the EFI data, with the following observations.

From 1404:07, after passing over the NDB, there were heading changes, yaw (evident as lateral accelerations) and a sudden left roll[16] followed by a 10–15 kt reduction in airspeed, consistent with a left engine power loss. 

Between about 1408:12 and 1409:27, during the turn from the outbound to the inbound tracks of the NDB instrument approach, the aircraft descended, climbed and descended again, at vertical speeds exceeding 1,000 fpm. During that period the airspeed varied between about 120–150 kt, with left roll angles up to 34°. 

The aircraft was on the downwind circuit leg between about 1413:26 and 1414:14, during which time there were no significant changes in lateral acceleration, roll, heading or performance (speed or height). 

The aircraft crossed the runway threshold at 1416:01 at 98 kt airspeed aligned with the runway centreline. The last position recorded by the EFI was at 1416:09, at which time the aircraft’s nose had pitched[17] up 6.5°, the airspeed had reduced to 79 kt and the ground speed was 77 kt, indicating a 2 kt headwind. The OzRunways recorded ground speed at the same time was 76 kt. 

The OzRunways data showed the aircraft started to deviate left of the runway centreline at 1416:14 at 69 kt ground speed, which would equate to an airspeed of about 71 kt for the same headwind component. The final OzRunways data point recorded before the fence, where the impact with terrain occurred, was at 1416:18 at a ground speed of 65 kt. 

Figure 6: Selected parameters from the Garmin electronic flight instrument 

Figure 6: Selected parameters from the Garmin electronic flight instrument 

Source: ATSB analysis of Garmin data

Site and wreckage 

The aircraft impacted the ground nose-down and inverted about 75° from the horizontal, resulting in crushing of the 2 m‑long nose structure (Figure 7). It collided with a fence and came to rest about 66 m left of the runway centreline and about 700 m beyond the runway threshold. The landing gear was extended, and the flaps were in the approach position. 

Both engines had folded backwards around the wing leading edge, which pulled the engine control cables such that the engine control levers were no longer representative of the pre‑impact positions. Damage to the wing leading edge resulted in fuel leaking, but there was no post-impact fire. The aircraft departed with full fuel, and had approximately 400 L of fuel remaining on board at impact. Both fuel selectors were set to ON. Flight control continuity was established. 

Figure 7: Impact damage to VH-OMD

Figure 7: Impact damage to VH-OMD

Source: Supplied, annotated by the ATSB

The left propeller flange fractured resulting in the propeller assembly detaching from the engine crankshaft and coming to rest spinner-down embedded in the dirt. The propeller manufacturer advised that the damage to the blades was consistent with the propeller either windmilling or not rotating at impact. The left spinner was indented with the counterweight, showing that the propeller was in fine pitch and not feathered. 

The right propeller remained attached to the right engine with evidence of being driven by significant engine power. Fence wire was wrapped around the engine and propeller, which had dug into the ground and first responders reported evidence of dirt having been flung from the hole by the rotating blades. 

Examination of the left engine found no evidence of mechanical failure or any pre‑existing fault. The fuel filters and air induction system were clear. The spark plugs were removed with no evidence of fouling from oil or carbon deposits and there were no visible defects with the ignition leads. Borescope examination of the cylinders found no damage or abnormal appearance of the internal surfaces. The fuel distributor manifold was empty of fuel and the diaphragm was undamaged. When electrical power was applied to the starter motor, the engine turned over normally with no evidence of loss of compression in the cylinders. 

The 2 front (crew) seats had separated from their track assemblies, although the shoulder harness inertia reels of both seats remained attached to the upper cabin structure. The instructor and student remained partially secured in their seats via the lap straps attached to the seat frame, The instructor came to rest in their seat outside the aircraft cabin following the opening of the cabin door during the accident sequence. 

Damage and distortion to the seat rails and seat guides was consistent with forward and right forces sustained during the impact sequence. Both seats’ centre rails exhibited distortion and smearing on the forward edge from the locking pins being forced from their rail holes. The left seat locking pin was bent rearward, and the right seat alignment pin had sheared. Figure 8 shows spreading of one of the seat guides and the associated damage to the seat rails.

Figure 8: Spreading of one seat guide (left) and associated damage to the rails (right)

Figure 8: Spreading of one seat guide (left) and associated damage to the rails (right)

Source: ATSB

A post-impact photograph showed the left engine auxiliary pump in the high position (Figure 9). However, as the entire panel had come adrift, there was dirt adjacent to the switch, and most of the switches in the row beneath it had broken off, its post-impact position was not considered reliable evidence of its position at the time of the accident. The switch panel location was also consistent with injury to the student’s knee. Additionally, the student reported that the pump had been used only for priming prior to engine start then confirmed to be off and not used again during the flight. The metal fuel pump switches were also by design unlikely to be confused with the smaller plastic light switches in the row below and inadvertently selected. It was therefore unlikely to have been on prior to the accident.

Figure 9: Panel showing post-impact switch positions and disruption

Figure 9: Panel showing post-impact switch positions and disruption

Source: Fly Oz, annotated by the ATSB

Asymmetric flight

Asymmetric control 

In conventional light twin-engine aeroplanes with one engine inoperative, asymmetric thrust will cause the aeroplane to yaw (rotate about its vertical axis) towards the inoperative engine. As a secondary effect of yaw, it will also roll. The yawing needs to be countered by deflection of the rudder and a small aileron deflection to raise the inoperative engine’s wing, in order to maintain balanced flight. At maximum power on the operative engine, the amount of rudder deflection needed increases as airspeed reduces, to a minimum control speed, below which the rudder is unable to maintain directional control. 

Below the minimum control speed, the pilot must reduce power on the operative engine to reduce the asymmetric force, and/or lower the aircraft nose to increase airspeed, to prevent a loss of control. If directional control is lost, the aircraft will yaw and then roll and descend rapidly. Controlled flight may be recovered if enough height is available, by reducing power and lowering the nose. 

Minimum control speed

The Civil Aviation Safety Authority’s (CASA) Civil Aviation Advisory Publication (CAAP) 5.23‑1(2) Multi-engine aeroplane operations and training, defined minimum control speed (VMC) as:

a speed that is associated with the maintenance of directional control during asymmetric flight. If the pilot flies below this speed the tail fin and rudder are unable to generate enough lift to prevent the aircraft from yawing. If uncorrected, the yaw causes roll, the nose drops, the aircraft rapidly assumes a spiral descent or even dive, and if the aircraft is at low altitude, it will impact steeply into the ground. This type of accident is not uncommon in a multi-engine aircraft during training or actual engine failure.

There is both a ground value (VMCG) and an airborne value (VMCA), but for simplicity, VMC usually refers to VMCA. The VMC is designated by the red radial on the airspeed indicator. The AFM specified VH-OMD’s VMCA as 79 kt indicated airspeed. That value is determined by US Federal Aviation Regulations (FAR) as the minimum airspeed at which it is possible to recover directional control of the aircraft within 20° heading change, and thereafter maintain straight flight, with no more than 5° of bank toward the operating engine following the sudden failure of one engine with:

  • take-off power on both engines
  • rearmost allowable centre of gravity
  • flaps in the take-off position
  • propeller windmilling in take-off pitch configuration. 

However, the actual VMC will vary depending on the configuration, conditions and pilot technique (FAA, 2021). The CASA CAAP 5.23-1(2) stated that flight tests conducted in a Cessna Conquest aircraft, which had a published VMC of 91 kt, found that if the wings were held level instead of the inoperative engine wing raised 5°, the actual minimum control speed was 115 kt – an increase of 24 kt. Other light twin-engine aeroplanes would similarly show an increase in actual minimum control speed without bank towards the operative engine. The American Bonanza Society Air Safety Foundation advised that in Baron aircraft types (including the E55), actual VMC is about 15 kt higher than the published VMC if the wings are held level instead of the inoperative engine wing raised, and the slip/skid ball remains centred instead of deflected towards the operative engine.  

At speeds below the actual VMC, with one engine inoperative and the other at take-off power, the aircraft will lose directional control – yaw, roll towards the inoperative engine and descend steeply. 

Best rate of climb one engine inoperative airspeed

The best rate of climb speed with one engine inoperative (single-engine) (VYSE) is denoted by a blue line on the airspeed indicator and therefore also known as ‘blue-line speed’. It represents the single-engine best rate of climb speed at maximum weight. The AFM for VH-OMD specified the VYSE was 99 kt. Pilots often use blue-line speed as a safety margin above VMC for initiating a simulated engine failure and assume that if blue-line speed is maintained, there is sufficient margin above VMC to prevent an asymmetric loss of control. 

Simulated one engine inoperative 

Aircraft manufacturer’s procedures

The AFM emergency procedures section included the following procedure titled Determining inoperative engine

The following checks will help determine which engine has failed.

1. DEAD FOOT – DEAD ENGINE. The rudder pressure required to maintain directional control will be on the side of the good engine. 

2. THROTTLE. Partially retard the throttle for the engine that is believed to be inoperative; there should be no change in control pressures or in the sound of the engine if the correct throttle has been selected. AT LOW ALTITUDE AND AIRSPEED THIS CHECK MUST BE ACCOMPLISHED WITH EXTREME CAUTION. 

Do not attempt to determine the inoperative engine by means of the tachometers or the manifold pressure gages. These instruments often indicate near normal readings. 

The AFM further described the following procedure titled Simulated one engine inoperative:

Zero thrust (simulated feather)

Use the following power setting (only one engine at a time) to establish zero thrust. Use of this power setting avoids the difficulties of restarting an engine and preserves the availability of engine power. 

The following procedure should be accomplished by alternating small reductions of propeller and then throttle, until the desired setting has been reached. 

Propeller lever – RETARD TO FEATHER DETENT

Throttle lever – SET 12 in. Hg MANIFOLD PRESSURE

NOTE: This setting will approximate zero thrust using recommended one-engine inoperative climb speeds. 

Fly Oz procedures

Fly Oz provided a document detailing its simulated engine failure procedure for the Beechcraft E55 aircraft. The procedure was for the instructor to reduce the mixture on one engine to idle cut‑off when above 1,000 ft. Once a student completed the initial checks, identified and verified the inoperative engine, the flight crew must decide whether to ‘fix’ the engine (if en route), or ‘feather’ the engine (‘at critical stages of flight’). If they elect to feather the engine:

… the student will articulate to the instructor which engine they determine has failed and the instructor will set zero thrust. 

Fly Oz also provided a copy of their Multi Engine Training Approval Standardisation Manual, which it advised was written for operating Beechcraft Model 76 Duchess aircraft, but was also applicable to the Beechcraft E55. The manual included an Engine failure recovery sequence, describing the 3 stages of a student’s mastery in handling an engine failure. For that sequence, the instructor was to ‘fail an engine by closing the mixture’ [their emphasis]. This was followed by completing the ‘engine out checks’, identifying and verifying the failed engine, then either feathering or troubleshooting to ‘fix’ the failed engine. That procedure did not mention its applicability to asymmetric instrument approaches.

The standardisation manual also had an Asymmetric circuits one engine inoperative procedure, which included 2 notes:

• Never fail an engine below 500 ft AGL.

• Always use the throttle to fail engines in the circuit so you can immediately add power if required. 

For that procedure, the instructor was to set zero thrust once the student had identified the correct engine to feather by touching the corresponding pitch lever. The asymmetric circuit procedure also mentioned conduct of an instrument approach and stated:

During an instrument approach a power setting of 20”MP [manifold pressure] with gear down should provide similar performance to the standard 15”MP with both engines operating. Gear should remain down if performance can be adequately maintained.

Additionally, the student or instructor was to include in the radio transmissions that they were ‘asymmetric’ to ‘allow other pilots to keep a safe distance and not try and push in on you in the circuit’.

Fly Oz also provided the ATSB with a copy of the Beechcraft Pilot Proficiency Program Instructor Standards Manual (American Bonanza Society, 2020), which it reported provided best practice guidance for operating the aircraft. The manual stated not to use the mixture to simulate an engine failure in single engine aircraft types. However, it did not stipulate how to simulate an engine failure in multi-engine aeroplanes, and included the following guidance on simulating zero thrust:

set the throttle to 10-12” MP, minimum governing RPM and mixture for ~ 6-7 GPH.  

Fly Oz advised the ATSB that it was common industry practice in both flight training and CASA flight testing to use the mixture to shut down an engine particularly when above circuit height. They further advised that their interpretation of the Beechcraft E55 AFM was that it did not specify how a simulated engine failure should be initiated. 

Guidance material

The US Federal Aviation Administration (FAA) publication Flying light twins safely (P-8740-066) advised pilots to ‘become thoroughly familiar with the AFM/POH recommended procedures’. Further, it recommended that simulated engine failures below 3,000 ft above ground level (AGL) should be accomplished by smoothly retarding the throttle (FAA, 2008). This was reiterated in the FAA’s Airplane Flying Handbook (FAA-H-8083-3C), Chapter 13: Transition to multiengine airplanes, which stated: 

The FAA recommends that all in-flight simulated engine failures below 3,000 feet AGL, be introduced with a smooth reduction of the throttle. Thus, the engine is kept running and is available for instant use, if necessary. Smooth throttle reduction avoids abusing the engine and possibly causing damage. 

The handbook also advised that the AFM/POH takes precedence, and that for engines equipped with dynamic crankshaft counterweights, it was essential to make throttle reductions smoothly. 

The United Kingdom Civil Aviation Authority’s Aeronautical Information Circular (Pink) 2008-P-064 also advised pilots to refer to the engine manufacturer’s recommendations for simulating engine failures. It recommended that engine failures after take-off ‘should be simulated only by reducing power and never by complete shutdown of the engine until recommended minimum heights at paragraph 9.4 have been achieved’. The referenced paragraph 9.4 recommended minimum safe heights for complete shutdown of power plants for training purposes of 3,000 ft AGL for twin engine piston and turboprop aeroplanes with a maximum take-off weight not exceeding 5,700 kg. 

Transport Canada’s Instructor Guide – Multi-engine class rating (TC, 2010), stated:

Actual engine shutdowns for training purposes are not recommended, as the training value is not worth the added safety risk and abuse of engines and airframe… 

Simulate the engine failure by reducing the throttle to idle, while calling out "simulated". Complete the engine failure drill in accordance with the [pilot’s operating handbook] POH or the procedures outlined on the previous page. 

When these checks have been completed, and you are ready to simulate feathering the propeller, adjust the manifold pressure and rpm to simulate by setting zero thrust. Consult the POH for zero thrust power settings prior to flight. Complete the engine securing items by referring to the appropriate emergency checklist.

The CASA CAAP 5-23-1(2) Multi-engine aeroplane operations and training advised instructors to consult the aircraft flight manual or pilot’s operating handbook for the recommended method of simulating an engine failure. It recommended:

Do not simulate an engine failure using procedures that may jeopardise the restoration of power. It is not recommended to simulate an engine failure at low level by selecting the mixture to idle cut-off or turn the fuel selector off. These procedures would be more appropriate at higher altitude. 

Further, the CAAP stated:

6.5.4 Slowly closing the throttle is one of the methods used to simulate an engine failure. Although selecting idle cut-off may be kinder to an engine, the engine or aircraft manufacturer may not permit it. So slowly closing the throttle to idle or zero thrust is unlikely to harm the engine and allows for immediate restoration of power. 

6.8.1 Flight instructors often simulate an engine failure by rapidly closing the throttle or moving the mixture control to idle cut-off. The latter method should never be used at low altitude.

American Bonanza Society Air Safety Foundation recommendation

The American Bonanza Society Air Safety Foundation recommended multi-engine instructors simulate an engine failure by smoothly reducing the throttle to idle, then block throttle movement on the simulated inoperative engine while the pilot receiving instruction (PRI) completes actions from the POH Engine failure in flight checklist. When the PRI gets to the checklist item ‘Propeller – Feather’, the instructor takes over the power controls and sets zero thrust in accordance with the BE55 POH/AFM.

The American Bonanza Society Air Safety Foundation recommended not simulating engine failure by turning off the fuel selector or pulling the mixture control to cutoff, consistent with FAA guidance.

Lycoming service bulletin

In April 1987, engine manufacturer Lycoming issued Service Bulletin No. 245D, Dynamic counterweight system detuning, which affected 9 Lycoming 6-cylinder engine models. The service bulletin explained that when the inertia force on an engine (which increases with engine speed), or the expansion force (manifold pressure), is suddenly changed, the engine counterweight system can ‘detune’. Damage to the counterweights, rollers and bushings could result, culminating in engine failure.   

The service bulletin listed 4 operating conditions that could cause the counterweight system to detune: rapid throttle operation, high engine speed and low manifold pressure, excessive speed and power, and propeller feathering. The bulletin stated:

To avoid detuning during simulated engine failure, use the mixture control to shut off the engine and leave the throttle in normal open position until the engine has slowed down because of lack of fuel. 

Fly Oz reported being unaware of the bulletin at the time of the accident. Additionally, Fly Oz reported that its procedures had been written for the Beechcraft 76 (Duchess) aircraft type, which were fitted with 4-cylinder Lycoming O-360 engines, and therefore not affected by the service bulletin. Finally, VH-OMD was not fitted with Lycoming engines and there was no comparable service bulletin or known issue associated with Continental engines.

Checklists

The student’s normal checklists are listed in the following tables. 

Table 1: Downwind checklist

ItemAction
BrakesPressure and off
UndercarriageDown
MixtureRich
FuelOn and sufficient
InstrumentsIndicating normally
SwitchesAs required
Hatches and harnessesSecure 

Table 2: Final checklist

ItemAction
PitchFull fine
UndercarriageDown and 3 greens
FlapAs required
FuelSufficient for a go-around

Workload

The student described the flight as ‘quite busy’, that they were ‘learning a lot of things’, and ‘a little overwhelming but normal for that stage of flying’. The student rated their workload on final as moderate (about 6/10). 

The instructor described that the student had been performing really well that day, asymmetric work and checks were good, and overall the student was a good pilot. The instructor also assessed that the student ‘got a bit distracted on the outbound’ leg of the approach, was a ‘little slow’ getting established on the inbound track, and there was some distraction due to circuit traffic operating on the opposite runway. The instructor reported that the student was ‘wrestling’ the aircraft on inbound or downwind, which prompted the instructor to ask whether the student wanted zero thrust set. 

The instructor rated their workload as moderate (5/10) and reported that for every landing, they had their seat fully forward, feet on the pedals and was alert and ready to intervene if necessary. 

Survivability

The student sustained a cut under the chin, a small fracture in the right hand, and lacerations to the left knee. The instructor had a deep laceration to the chin and one arm and bruising to the knees. Both sustained additional cuts and bruises, including bruising from the lap belt and shoulder harnesses. 

The certification basis of the aircraft was US Civil Air Regulation 3. The certification standards required that for a standard weight person (77 kg), the seat must withstand flight, ground, and emergency load conditions. For the seats, the critical conditions were 9 G forward, 3 G upwards and 1.5 G sideways, with the seat attachments to withstand 133% of those requirements.  

ATSB analysis of the wreckage and accident site found that the impact deceleration likely exceeded 30 G in a principally forward direction. This significantly exceeded the 9 G forward requirement and the 12 G requirement for the seat attachments. The stable collapse of the airframe structure forward of the occupants aided their survivability.

Similar occurrences

ATSB occurrences

The ATSB occurrence database contained 16 twin-engine aeroplane loss of control occurrences during simulated engine failures since 1978. Two of those occurred in the last 10 years and resulted in fatal accidents in which the loss of control resulted from a simulated engine failure using a method and/or height contrary to manufacturers’ guidance. Key findings of these 2 investigations are as follows.

Loss of control and collision with terrain involving Cessna 441, VH-XMJ, 4 km west of Renmark Airport, South Australia on 30 May 2017 (AO-2017-057

The flight departed Adelaide, South Australia, at about 1524 local time and flew to the Renmark area for exercises related to the check flight, followed by a landing at Renmark Airport. After a short period of time running on the ground, the aircraft departed from runway 25 at about 1614.

The ATSB determined that, following a simulated failure of one of the aircraft’s engines at about 400 ft above the ground during the take‑off from Renmark, the aircraft did not achieve the expected single engine climb performance or target airspeed. As there were no technical defects identified, it is likely that the reduced aircraft performance was due to the method of simulating the engine failure, pilot control inputs or a combination of both.

It was also identified that normal power on both engines was not restored when the expected single engine performance and target airspeed were not attained. That was probably because the degraded aircraft performance, or the associated risk, were not recognised by the pilots occupying the control seats. Consequently, about 40 seconds after initiation of the simulated engine failure, the aircraft experienced an asymmetric loss of control.

The single engine failure after take‑off exercise was conducted at a significantly lower height above the ground than the 5,000 ft recommended in the Cessna 441 pilot’s operating handbook. This meant that there was insufficient height to recover from the loss of control before the aircraft impacted the ground. The 3 occupants were fatally injured.

The operator’s training and checking manual procedure for simulating an engine failure in a turboprop aircraft was inappropriate and increased the risk of asymmetric control loss.

Loss of control and collision with terrain involving Angel Aircraft Corporation 44, VH-IAZ, near Mareeba Airport, Queensland, on 14 December 2019 (AO-2019-072)

On 14 December 2019, 2 pilots were conducting a private flight in an Angel Aircraft Corporation Model 44 aircraft, registered VH-IAZ, at Mareeba, Queensland. An instructor seated in the right pilot seat was conducting a flight review of the pilot (and aircraft owner) in the left seat.

After the aircraft took off from Mareeba Airport, witnesses reported hearing one of the engines hesitating and backfiring, accompanied by a sooty smoke trail from the right engine. The aircraft operated in the training area until returning to the airport circuit area. Witnesses observed the aircraft touch down on the runway, accelerate and take off again. After take-off, the aircraft climbed to about 100–150 ft above ground level before entering a right descending turn. The aircraft was airborne for about 20 seconds before witnesses observed it rolling rapidly to the right and impacting terrain in a cornfield 475 m north of the runway. The pilots sustained fatal injuries and the aircraft was destroyed. 

The ATSB found that shortly after take-off, the flight instructor very likely conducted a simulated failure of the right engine in environmental conditions and a configuration in which the aircraft was unable to maintain altitude with one engine inoperative. Power was not immediately restored to the right engine to discontinue the exercise and the pilots were unable to maintain altitude or heading, particularly with the aircraft banked towards the inoperative engine. The pilots did not reduce power and land ahead, as required by the Airplane Flight Manual, resulting in a loss of directional control and roll. The loss of control occurred at a height too low to recover and the aircraft impacted terrain.

United States occurrences

A search of the US National Transportation Safety Board’s (NTSB) database for investigations involving twin engine aeroplanes, with the words ‘engine’ and ‘simulated’ in the probable cause text, yielded 37 investigations since February 1989,13 of which occurred in the last 10 years. Two of those provide some context relevant to this occurrence:

Piper PA-34, N88AG, Miami, Florida, US on 11 September 2018 

The flight instructor in the multi-engine aeroplane reported that the pilot under instruction was conducting a simulated instrument approach in visual flight rules conditions. The instructor placed the left engine fuel selector in the ‘off’ position to simulate an engine out, and the pilot under instruction initiated the left engine failure procedure by placing the engine and propeller levers in a simulated feathered zero-thrust configuration. The instructor became distracted by traffic and failed to place the left engine fuel selector back to the ‘on’ position. 

With full flaps and the landing gear extended and while about 250 ft above ground level, the instructor terminated the simulated instrument approach and instructed the pilot to land visually; however, the airspeed decreased below safe limits, and the instructor directed the pilot to increase the airspeed. The pilot increased power on both engines; however, the left engine power did not increase, and the aeroplane rolled to the left about 45°. The instructor took the controls and applied right aileron and rudder, but the aeroplane settled down in a level attitude in a shallow lagoon on the left side of the runway.

Probable cause: The pilot under instruction’s failure to maintain the twin-engine airplane’s minimum control airspeed with one engine inoperative and the flight instructor’s distraction when reconfiguring the airplane following the simulated engine failure, which resulted in no power being available to the left engine and a loss of control during landing when the throttles were advanced to increase airspeed.

Cessna 402C, N2714B, Hyannis, Massachusetts, US on 26 April 2021 

A flight instructor and a new-hire trainee pilot were practising instrument approach procedures in the multi-engine aeroplane. On climb-out, the flight instructor reduced power on the left engine to simulate an engine failure on take-off. The pilot then ran the memory items for an engine failure, which included turning the left engine auxiliary fuel boost pump to high. They then conducted an instrument approach. When the aircraft was about 50 ft above the runway, the flight instructor called for a 2-engine go-around. The pilot brought both throttles to full power and retracted the flaps and gear. The flight instructor reported that the aircraft yawed left, and the airspeed was about 80 kt, well under the aircraft’s best single engine rate of climb speed of 95 kt. The flight instructor took control of the aircraft and called for the gear to be extended. The aircraft landed hard and the nose and left main landing gear collapsed, resulting in substantial damage to the left engine and wing. Prior to exiting the aircraft, the pilot turned the left engine auxiliary boost pump from the high position to the off position.

The flight instructor reported that turning the boost pump to high while the engine was still operating could flood the engine with excess fuel and cause it to lose power. The instructor reported that they normally reminded pilots not to turn the pump to high during a simulated engine failure in flight, but neither flight crewmember recalled it being mentioned during the accident flight. Post-accident examination of the left engine revealed no mechanical discrepancies that would have precluded normal operation. As a result, it was most likely that when the boost pump was turned to high, it flooded the engine with excess fuel, resulting in loss of engine power while attempting to go around. 

Probable cause: The flight instructor’s failure to confirm the position of the left engine’s auxiliary fuel boost pump switch during a simulated engine out procedure, which resulted in an excess amount of fuel in the engine and subsequent partial loss of power during a go-around/rejected landing. Contributing to the accident was the flight instructor’s failure to maintain control of the airplane, which resulted in a hard landing.

Engine control standardisation

VH-OMD was certified to the 1956 US Civil Air Regulations. The NTSB special study General Aviation Accidents involving fuel starvation 1970–1972 identified design-associated and pilot‑associated factors that influenced or caused ‘operational problems’ in fuel starvation accidents. As a result, the NTSB issued several recommendations. One was for the FAA to issue an advisory circular including ‘to warn certificated flight instructors of the danger associated with simulation of emergency engine failure by positioning the fuel selector valve to “off” or the mixture control to “idle cutoff”’. Another recommendation, A-74-38, was for the FAA ‘to amend the regulations to include specifications for standardizing powerplant control location, visual and tactile appearance, and mode of actuation’.

In 1976, in response to NTSB recommendation A-74-38 regarding fuel control standardization, the US General Aviation Manufacturers Association (GAMA) proposed to the FAA changes to FAR 23.777 through 23.781. It prescribed left to right throttle, propeller and mixture controls, landing gear to the left of the throttle or pedestal centreline, and flap to the right, and included recommended shapes and colours (Figure 10). The FAA’s General aviation (FAR 23) cockpit standardization analysis (FAA-NA-77-38) recognised that ‘increased standardization of cockpit systems can reduce cockpit workload, reduce the potential for habit interference when transitioning to another type aircraft, and provide for application of the best and most error‑resistant designs’ (FAA, 1978).

However, regarding the subsequent FAR amendment 23–33 1986, the FAA stated, ‘that color of control knobs is not a safety issue and will not adopt the proposed color requirement’. As a result, the recommended black throttle control knob and blue propeller control knob standard was not incorporated into FAR 23. A mixture lever was considered an ‘emergency control’ and therefore under FAR 23.1555(e)(2) must be red. The landing gear lever (left) and flap lever (right) requirement was incorporated in FAR 23.777 (f) and (g)). 

Figure 10: Recommended control standardisation shapes and colours

Figure 10: Recommended control standardisation shapes and colours

Source: US Federal Aviation Administration 

Figure 11 is a post-accident photo of VH-OMD’s engine control levers, which are all black, the throttle pair is in the middle and each pair has different shaped knobs. Additionally, the landing gear selector was to the right of the centre console and the flaps to the left. As VH-OMD was certified prior to the standardisation requirements, it was not required to comply with subsequent FARs.

In this case, as the instructor primarily flew VH-OMD, and it was the only twin engine aeroplane the student had flown (other than a simulator), habit interference was unlikely. However, the lack of colour differentiation in the levers, and particularly not having red mixture control levers, may have reduced the opportunity for rapid visual identification of the mixture lever position. 

Figure 11: VH-OMD engine control levers

Figure 11: VH-OMD engine control levers

Source: Fly Oz, annotated by the ATSB

Safety analysis

Introduction 

When overhead the Cowra Airport navigation aid at the commencement of an instrument approach, at about 2,600 ft above ground level, the instructor simulated a failure of the left engine. After the student conducted the instrument approach and had visually established the aircraft on final approach to the runway, the instructor initiated a go-around at a low height above the runway. Control of the aircraft was lost as it rapidly yawed and rolled left and impacted the ground in an almost vertical nose-down attitude, before coming to rest inverted. 

Wreckage examination determined that the left engine was not producing power and the right engine was making significant power at impact. Additionally, there was no evidence of any defect in the left engine or airframe that could have contributed to the accident.

The following analysis will consider why the left engine was not operating at impact and why the go‑around was attempted with one engine inoperative. Additionally, operational procedures associated with simulated engine failures and related risk controls, including their potential to influence future operations will be discussed.

Left engine not restarted

The instructor followed their normal method of simulating an engine failure in accordance with the operator’s stated procedure for the aircraft type by moving the left engine mixture control lever to the idle cut-off position, thereby rendering the engine inoperative. 

The required response was for the student to maintain directional control of the aircraft and complete the engine failure checks. Once the student had identified which engine was inoperative, they were to either complete troubleshooting checks to ‘fix’ the failed engine when en route or feather the propeller at a critical stage of flight.

In a training scenario, once the student had identified the inoperative engine correctly, the instructor would normally set zero thrust to simulate a feathered propeller. Their process for setting zero thrust included returning the mixture control to full rich, thereby restarting the engine. However, for reasons that could not be determined, zero thrust was not set at that stage, the mixture remained at idle cut-off with the left propeller windmilling. 

The windmilling propeller increased drag and the likelihood of a loss of control, particularly during the left turn towards the inoperative engine. Although the student did not report experiencing a high workload, the approach was not flown within prescribed tolerances and included significant changes in airspeed and altitude. Given the benign weather and light winds at the time, these deviations were likely a result of pilot handling, not environmentally induced. The subsequent improvement in tracking accuracy evident when the aircraft turned to join the circuit, was consistent with the student lifting the hood and resuming flight with external visual reference.

Whether the instructor or student prompted the setting of zero thrust could not be resolved. Given that the instructor recalled setting zero thrust either on inbound or downwind and the student recalled this occurred on downwind, downwind was considered more likely as it was consistent with both recollections. There was no change in heading or increase in performance evident in the recorded data to indicate power was restored to the left engine on downwind, although any such change may have been negligible at the relatively low power settings.

As the manifold pressure would essentially read normally with the propeller windmilling, the stated practice of the instructor of moving the throttle lever forward to achieve the target manifold pressure for setting zero thrust would not confirm the engine was operating. It was for this reason that the Beechcraft E55 Airplane Flight Manual (AFM) cautioned against using manifold pressure indications to assess engine power. In the context of this accident, the observed (and expected) variation of manifold pressure with throttle movement supported an assessment that the engine had been restarted and was capable of normal operation.   

Prompting and attempting to set zero thrust on downwind may have interrupted the student’s completion of the downwind checks, which should have included moving both mixture levers to the full rich position. Additionally, the student did not complete the previous checklist item of extending the landing gear, electing to defer doing so until turning onto the base leg and potentially interrupting the checklist flow. As the student had broadcast that they were operating in asymmetric configuration, they were not anticipating the conduct of a go-around. There was no check conducted by either crewmember, or required by procedure, that would verify the engine had restarted and was making power.

The initial small increase in power to the right engine and associated yaw prior to the go-around, as reported by the instructor, was not evident in the data. However, the recorded data showed the aircraft veered off the runway within 3 seconds of the initial deviation from the runway centreline, and the yaw and roll continued to impact. This was consistent with significant asymmetric thrust due to the left engine being inoperative, as evidenced by the absence of rotation when the propeller blades subsequently impacted the ground.

As there was also no evidence of any engine failure mechanism and although the mixture lever position prior to impact could not be determined, the ATSB found that the left mixture lever likely remained in the idle cut-off position from shortly after commencing the instrument approach and the engine was unintentionally not restarted. 

Go-around and loss of control

The instructor was unaware they had not returned power to the left engine, and therefore when they instructed the student to commence a go-around, it was based on a belief that symmetrical power was available. This misunderstanding meant the instructor's initial actions in response to the left yaw were to verify the throttle levers were fully forward and to call for the student to let go of the controls, while attempting to correct with rudder. At that stage the only way to avoid the loss of control would have been to reduce power on the right engine and land. 

The last recorded airspeed from the electronic flight instrument data, prior to the yaw was 79 kt, which was the published minimum control speed (VMC). The OzRunways data showed the ground speed reduced another 7 kt before the yaw commenced, and the airspeed likely similarly reduced. Additionally, the actual VMC may have been higher, as the wings were probably levelled for landing, rather than having the inoperative engine wing raised 5°, as required to achieve the optimum published VMC. As the aircraft was almost certainly below actual VMC when the go-around commenced, there was insufficient rudder authority to maintain control, and the loss of control occurred at a height too low to recover. 

The low height at which the loss of control commenced, estimated to be about 20 ft above the runway, and the crushing of the aircraft’s structure on impact, contributed to the accident’s survivability. The impact forces exceeded the certification requirements of the seats, which detached from their rails, but the flight crew were initially restrained by 4-point harnesses. Significantly, as the aircraft was fitted with fuel cells, despite disruption to the wing leading edge and fuel slowly leaking post impact, there was no explosive fuel-air misting or post-impact fire.  

Fly Oz simulated engine failure procedure

The Beechcraft E55 AFM included a procedure for simulating one engine inoperative. The procedure was to set zero thrust, which involved retarding the propeller lever to the feather detent and the throttle lever to set 12 inches of manifold pressure. The flight manual stated that the purpose of the procedure was to ‘avoid difficulties of restarting an engine and preserve the availability of engine power', which would be associated with cutting off the mixture and/or selecting the fuel off. 

Fly Oz’s procedure for simulating an engine failure in the Beechcraft E55 aircraft was to move the mixture to idle cut-off to simulate an engine failure, when above 1,000 ft, which was contrary to the AFM procedure to use throttle. It was also contrary to guidance not to use mixture to simulate engine failures when below 3,000 ft above ground level from the aviation regulators in the United States, United Kingdom, and Canada. The Australian Civil Aviation Safety Authority’s guidance did not specify a height below which mixture cut-off should not be used. However, it advised not to simulate an engine failure ‘using procedures that may jeopardise the restoration of power’. Further, that slowly closing the throttle allows for immediate restoration of power.

As the conduct of an asymmetric instrument approach may include one or more legs of a circuit and end in a landing, there is a potential need for immediate restoration of power close to the ground. Therefore, the use of throttle to simulate an engine failure for conduct of an instrument approach could be inferred from the CASA guidance. The guidance also included the need to consult the aircraft flight manual for the manufacturer’s recommended method of simulating an engine failure.

Fly Oz’s Multi Engine Training Approval Standardisation Manual also included a procedure to simulate an engine failure that involved moving the mixture to idle cutoff. However, consistent with the AFM, it also contained a procedure that stipulated the use of throttle to simulate engine failures in the circuit (under which it included the conduct of asymmetric instrument approaches). Fly Oz stated that, while the manual had been written for a different aircraft type, it provided a description of the procedure applicable to VH-OMD. Despite that, on the day of the accident the instructor used the Fly Oz Beechcraft E55 specific procedure in use at the time and simulated the engine failure using the mixture control. That procedure did not contain a requirement or process to verify the engine was subsequently restarted and available for instant use.

This likely resulted in the inoperative engine being undetected by the flight crew, while operating at low power during the approach and landing. Ultimately this resulted in the loss of control during initiation of a go-around.

The ATSB occurrence database held 2 fatal accidents in the last 10 years that resulted from a loss of control following a simulated engine failure using a method and/or height contrary to guidance. Although there was no data available for the number of simulated engine failures conducted and by what method, the frequency of loss of control accident types and likelihood of fatality indicated that these posed a significant risk. 

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 loss of control and collision with terrain involving Beech E55, VH-OMD, at Cowra Airport, New South Wales on 11 April 2024.  

Contributing factors

  • The instructor moved the left engine mixture lever to idle cut-off to simulate an engine failure overhead the navigation aid, and it was likely that they unintentionally did not subsequently move the lever to rich and ensure the engine was restarted and available for instant use.
  • The instructor initiated a go-around below the air minimum control speed unaware the left engine was inoperative, resulting in an asymmetric loss of control.
  • Fly Oz's asymmetric training procedure involved failing one engine using the mixture control without confirmation the engine was subsequently restarted, rather than reducing throttle to simulate zero thrust in accordance with the Beechcraft E55 Airplane Flight Manual. This increased the risk of undetected asymmetric operation during descent and landing and the associated loss of control. (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.

Operator’s procedure to use mixture to simulate engine failure

Safety issue number: AO-2024-011-SI-01 

Safety issue description: Fly Oz's asymmetric training procedure involved failing one engine using the mixture control without confirmation the engine was subsequently restarted, rather than reducing throttle to simulate zero thrust in accordance with the Beechcraft E55 Airplane Flight Manual. This increased the risk of undetected asymmetric operation during descent and landing and the associated loss of control.

Safety action not associated with an identified safety issue

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. The ATSB has been advised of the following proactive safety action in response to this occurrence.
Additional safety action by Fly Oz

Fly Oz has taken the following proactive safety action:

  • Following a simulated engine failure, zero thrust is to be set immediately after the student has completed the engine failure drills.
  • The instructor standardisation manuals were being updated to include a requirement that both the student and instructor confirm that the pitch, power and mixture controls are set back to normal 2‑engine configuration during checks on final. This is now a call out item, ensuring that both pilots are satisfied with the correct settings.

Glossary

AFMAirplane Flight Manual
AGLAbove ground level
AIPAeronautical information publication
AMSLAbove mean sea level
CAAPCivil Aviation Advisory Publication
CASACivil Aviation Safety Authority
CTAFCommon traffic advisory frequency
EFIElectronic flight instrument 
FAA(US) Federal Aviation Administration
FARFederal Aviation Regulations
METARMeteorological conditions at an aerodrome
NDBNon-directional beacon
NSWNew South Wales
NTSB(US) National Transportation Safety Board
QNHThe altimeter barometric pressure subscale setting used to indicate the height above mean seal level
TISTime in service
USUnited States

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the flight instructor and student pilot
  • the maintainer of VH-OMD
  • Fly Oz
  • Civil Aviation Safety Authority
  • New South Wales Police Force
  • the aircraft, propeller and engine manufacturers
  • Bureau of Meteorology
  • OzRunways
  • accident witnesses
  • photographs and videos taken on the day of the accident and for subsequent examination
  • recorded data from the GPS unit on the aircraft.

References

American Bonanza Society, BPPP Instructor Standards Manual, Revision 10, July 2020. 

Civil Aviation Safety Authority, Civil Aviation Advisory Publication 5.23-1(2) Multi-engine aeroplane operations and training, September 2015.  

Federal Aviation Administration, Airplane Flying Handbook, FAA-H-8083-3C, 2021. Accessed 10 May 2024: Airplane Flying Handbook | Federal Aviation Administration (faa.gov)

Federal Aviation Administration, Flying light twins safely, FAA-P-8740-66 (2008). Accessed 19 May 2024: FAA_P-8740-66.pdf (faasafety.gov)

Lycoming Service Bulletin No. 245 D Dynamic Counterweight System Detuning, 10 April 1987. Accessed 10 May 2024: Service Bulletin No. 245 D | Lycoming

Transport Canada, Instructor Guide: Multi-engine class rating, Second edition, October 2010. Accessed 19 May 2024: Microsoft Word - TP11575E.doc (canada.ca)

United Kingdom Civil Aviation Authority, Aeronautical Information Circular, 64/2008 (Pink 142) 17 July 2008. Accessed 10 May 2024: Pink 142.qxp (ead-it.com)

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 instructor and student pilot
  • Fly Oz
  • Civil Aviation Safety Authority
  • the maintainer of VH‑OMD
  • American Bonanza Society Air Safety Foundation
  • the aircraft, engine and propeller manufacturers. 

Submissions were received from:

  • the flight instructor and student pilot
  • Fly Oz
  • Civil Aviation Safety Authority
  • American Bonanza Society Air Safety Foundation.

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]     Instrument flight rules (IFR): 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). Procedures and training are significantly more complex as a pilot must demonstrate competency in IMC conditions while controlling the aircraft solely by reference to instruments. IFR-capable aircraft have greater equipment and maintenance requirements.

[2]     Visual Meteorological Conditions (VMC): an aviation flight category in which visual flight rules (VFR) flight is permitted – that is, conditions in which pilots have sufficient visibility to fly the aircraft while maintaining visual separation from terrain and other aircraft.

[3]     OzRunways is an electronic flight bag application that provides navigation, weather, area briefings and other flight information. It provides the option for live flight tracking by transmitting the device’s position and altitude.

[4]     Instrument approach procedure: A series of predetermined manoeuvres by reference to flight instruments that provides specified protection from obstacles.

[5]     NDB: a ground-based radio transmitter that provides a reference point to navigate by.

[6]     Windmilling: a rotating propeller being driven by the airflow rather than by engine power, and results in increased drag at normal propeller blade angles.

[7]     Feathering: the rotation of propeller blades to an edge-on angle to the airflow to minimise aircraft drag following an in‑flight engine failure or shutdown.

[8]     Manifold pressure gauge measures the absolute pressure in the intake manifold of an engine, expressed in inches of mercury (in. Hg). Normal operating range (green arc) was 15 to 29.6 in. Hg.

[9]     Yawing: the motion of an aircraft about its vertical or normal axis.

[10]    Flare: the final nose-up pitch of a landing aeroplane used to reduce the rate of descent to about zero at touchdown.

[11]    A registered operator is responsible for airworthiness and maintenance control of the aircraft (CASA).

[12]    Maintenance release: an official document, issued by an authorised person as described in Regulations, which is required to be carried on an aircraft as an ongoing record of its time in service (TIS) and airworthiness status. Subject to conditions, a maintenance release is valid for a set period, nominally 100 hours TIS or 12 months from issue.

[13]    METAR: a routine report of meteorological conditions at an aerodrome. METAR are normally issued on the hour and half hour. Winds use true north as the reference. 

[14]    QNH: the altimeter barometric pressure subscale setting used to indicate the height above mean seal level.

[15]    OzRunways is an electronic flight bag application that provides navigation, weather, area briefings and other flight information. It also provides the option for live flight tracking by transmitting the device’s position and altitude.

[16]    Rolling: the movement of an aircraft about its longitudinal axis.

[17]    Pitching: the motion of an aircraft about its lateral (wingtip-to-wingtip) axis.

Occurrence summary

Investigation number AO-2024-011
Occurrence date 11/04/2024
Location Cowra Airport
State New South Wales
Report release date 22/08/2024
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control, Runway excursion
Occurrence class Accident
Highest injury level Minor

Aircraft details

Manufacturer Beechcraft
Model E55
Registration VH-OMD
Serial number TE-970
Aircraft operator Fly Oz Cowra
Sector Piston
Operation type Part 141 Recreational, private and commercial pilot flight training
Departure point Cowra Airport, New South Wales
Destination Cowra Airport, New South Wales
Damage Substantial

Pilot incapacitation, loss of control and collision with terrain involving Gulfstream 695A, VH-HPY, 55 km south-east of Cloncurry Airport, Queensland on 4 November 2023

Final report

Report release date: 19/06/2025

Investigation summary

What happened

On the morning of 4 November 2023, a Gulfstream 695A, registered VH‑HPY, was being operated by AGAIR on an instrument flight rules flight from Toowoomba to Mount Isa, Queensland. On board the aircraft were the pilot and 2 camera operators. The purpose of the flight was to conduct line scanning of fire zones located north of Mount Isa. 

About 1 hour and 50 minutes into the flight, while the aircraft was in cruise at flight level 280, air traffic control (ATC) lost radio contact with the pilot. Over the following 30 minutes, ATC made multiple attempts to re‑establish contact, including using alternate frequencies and relaying messages via other aircraft in the vicinity. VH-HPY was observed diverging from track and ATC declared an uncertainty phase for the aircraft.

About 20 minutes later, ATC called the pilot’s mobile telephone, and a brief conversation took place. During the conversation, the pilot’s speech was observed as slow and flat. In response, ATC upgraded the aircraft’s status to an alert phase and initiated their hypoxic pilot emergency procedures. About 10 minutes later, the crew of a nearby aircraft was able to establish contact with the pilot, having been requested to do so by ATC. The alert phase was downgraded to an uncertainty phase and, a short time later, ATC re-established direct contact with the pilot. The uncertainty phase was cancelled 1 minute later.

The pilot confirmed that their oxygen system was operating normally, and they were issued a clearance to undertake line scanning north of Mount Isa. Over the following 4 minutes, the pilot repeated the clearance from ATC 4 times, seeming uncertain about the status of the clearance. The radio recordings during this period indicate that the pilot’s rate and volume of speech had substantially lowered from earlier communications and was worsening. The pilot’s final radio transmission displayed the slowest speaking rate of all their communications during the flight and contained stuttering and operational mistakes. Air traffic control did not attempt to re‑establish contact with the pilot until about 18 minutes later, however no further responses from the pilot were received. 

A short time later, the aircraft departed controlled flight, initially entering a descending anticlockwise turn with an increasing rate of descent. At about 10,500 ft, the aircraft likely transitioned into an aerodynamic spin, with a subsequent average rate of descent of about 13,500 ft/min. The aircraft collided with terrain 55 km south-east of Cloncurry. The 3 occupants were fatally injured, and the aircraft was destroyed by impact forces and a fuel-fed post-impact fire.

What the ATSB found

The ATSB found that the aircraft had a long-term intermittent defect with the pressurisation system that would manifest as a reduced maximum attainable cabin differential pressure. The defect was known about by senior AGAIR management who attempted to have the defect rectified. However, they did not formally record the defect, communicate it to the safety manager, undertake a formal risk assessment of the issue, or provide explicit procedures to pilots for managing it. 

Instead, AGAIR management personnel participated in and encouraged the practice of continuing operations in the aircraft at a cabin altitude that required the use of oxygen, without access to a suitable oxygen supply. This included the pilot of the accident flight, with emails and historical flight data indicating they had a pattern of normalised deviation from safe operating practices by continuing to operate the aircraft when the pressurisation system was defective. In these situations, the pilot was found to have managed the effects of hypoxia by undertaking short descents to lower altitudes and use of the aircraft’s oxygen system, which was designed for emergency use only.

It was identified that during the accident flight the pressurisation system probably did not maintain the required cabin altitude, and the pilot probably continued the flight using the aircraft’s oxygen system, which was unsuitable for this purpose. The pilot’s speech, as captured by air traffic control recordings, demonstrated significant and progressive impairment while the aircraft was operating at about flight level 280. This impairment was consistent with altitude hypoxia, which almost certainly significantly degraded the pilot’s ability to safely operate the aircraft.

While the aircraft was in cruise, both power levers were probably reduced without a descent being initiated, resulting in a progressive reduction of airspeed. The aircraft then entered a descending anticlockwise turn with an increasing rate of descent. At around 10,500 ft control input(s) were almost certainly made, probably an attempt to recover, that transitioned the aircraft from a high‑speed descent to an unrecoverable spin condition that continued until the impact with terrain. 

It was found that the AGAIR head of flying operations (HOFO) did not communicate critical safety information about the known intermittent pressurisation defect when they were phoned by air traffic control about concerns that the pilot was impacted by hypoxia around 37 minutes before the collision. This took place at a time when air traffic control could have taken action to instruct the pilot to descend to a safe altitude. 

Air traffic control personnel involved therefore had no knowledge of the aircraft pressurisation defect from that phone call, and without establishing with the pilot why they had not responded to ATC broadcasts for 1 hour and 13 minutes, they likely reduced their vigilance about hypoxia after being told by the pilot that operations were normal. Consequently, ATC did not re-identify the possibility of hypoxia during the subsequent progressive deterioration of the pilot’s speech. Additionally, the air traffic control ‘hypoxic pilot emergency checklist’ contained no guidance on ceasing the emergency response, which increased the risk of inappropriately downgrading the response during a developing hypoxic scenario. 

It was also identified that AGAIR Gulfstream 690 and 695 aircraft were operated with known defects without being recorded on the aircraft’s maintenance releases, likely as a routine practice. This issue had been reported to CASA in 2019 and a surveillance event was conducted in response. The scope of the surveillance event did not include a crosscheck of maintenance releases against the aircraft logbooks, limiting the ability to determine whether any non-reporting and improper deferral of defects had been taking place at that time.

What has been done as a result

AGAIR amended the organisation’s procedural documentation to provide greater detail on the delegation of management responsibilities, maximum cabin altitude requirements, defect reporting, and the capture of cabin pressure information as part of daily aircraft flight and fuel logs. 

AGAIR also incorporated pressurisation, oxygen and line scanning hazards within the organisation’s hazard register. AGAIR has also contracted a continuing airworthiness management organisation and appointed a new head of aircraft airworthiness maintenance control to monitor defect reporting. 

While the ATSB recognises the changes implemented by AGAIR to date, the actions taken do not address the matters raised relating to effective operational control. The HOFO was responsible for ensuring the operation was compliant with aviation legislation and conformed to company standards. However, the ATSB found multiple instances where these requirements were not met. AGAIR has not addressed how the organisation intends to assure future legislative and procedural compliance by line pilots and management personnel. As such, the ATSB has issued a formal safety recommendation to AGAIR to initiate an independent review of their organisational structure and oversight of operational activities to assure ongoing effective operational control by management.

Airservices Australia advised that it is in the process of conducting a review of the hypoxia in-flight emergency response checklist.

Safety message

This accident highlights the dangers of operational practices that intentionally circumvent critical safety defences. The acceptance of these actions at an individual and organisational level normalises that behaviour and exposes the operation to an unnecessarily increased level of risk. 

This accident also underscores the insidious and deadly potential of altitude hypoxia, and pilots need to be alert to this significant hazard when operating at high altitude. Life support and emergency alerting systems are often the final line of defence against hypoxic incapacitation, and they should only be used in accordance with the manufacturer’s procedures. 

Summary video

 

The occurrence

Overview

On the morning of 4 November 2023, a Gulfstream 695A, registered VH‑HPY, was being operated by AGAIR on an instrument flight rules[1] flight from Toowoomba to Mount Isa, Queensland, with the callsign ‘birddog 370’. On board the aircraft were the pilot and 2 camera operators. The purpose of the flight was to conduct line scanning[2] of fire zones located north of Mount Isa. The flight had been contracted by Queensland Fire and Emergency Services and was conducted as an aerial work operation.

While the aircraft was in cruise at flight level[3] (FL) 280, air traffic control (ATC) radio contact with the pilot was unable to be maintained. ATC made multiple attempts to re-establish radio communications, but these were initially unsuccessful. ATC also declared an uncertainty phase for the aircraft, later upgrading it to an alert phase. After about 1 hour, the crew of a Royal Australian Air Force (RAAF) aircraft was able to make radio contact with the pilot, and ATC re-established communications a short time later. The alert and uncertainty phases were subsequently cancelled.

A series of radio communications were exchanged between the pilot and ATC, during which the pilot was issued a clearance to undertake line scanning north of Mount Isa. The pilot did not respond to any further calls from ATC. The aircraft departed controlled flight and at 1427 (local time) collided with terrain 55 km south-east of Cloncurry (Figure 1). The 3 occupants were fatally injured, and the aircraft was destroyed.

Figure 1: Flight path overview 

Figure 1: Flight path overview

Source: Google Earth, annotated by the ATSB

Departure, climb and cruise

At 1055 on the morning of the accident flight, the aircraft departed Toowoomba Airport with the pilot being provided an ATC clearance for the flight to track to Mount Isa. The pilot was initially cleared by ATC to climb to FL160 and was then issued further instruction to continue the climb to the planned cruise of FL280. The pilot made a brief personal phone call at about 1103 (see Telecommunications), and the aircraft reached FL280 at 1120:30 (Figure 2).

Figure 2: Plot of changes in aircraft altitude and the sequence of radio communication events throughout the accident flight from 1045–1300  

 

Plot of changes in aircraft altitude and the sequence of radio communication events throughout the accident flight from 1045–1300

Position information including altitude and time was obtained from ADS-B data that was broadcast from VH-HPY. Source: ATSB

At 1126:55 the flight was transferred to, and the pilot established radio communication with, the controller responsible for the Simpson region on the frequency 126.0 MHz (see Airspace). 

At 1141:12, the pilot contacted the controller and requested clearance to descend to FL150. The requested clearance was provided and, a short time later, the aircraft started to descend. The initial rate of descent reached about 3,900 feet per minute (ft/min), but this slowed as the aircraft continued to descend. At 1151:49, the aircraft levelled off at FL150. At 1157:43, the pilot contacted the controller again and requested clearance to climb back to FL280, which was approved. Shortly after, the aircraft began to climb.

At 1210:19, the Simpson region controller requested the pilot change their radio communication frequency to 122.3 MHz, to maintain radio contact with ground equipment as the aircraft flew further west. The pilot established radio communication on the new frequency and reported to the controller that the aircraft was on climb to FL280. At 1221:49, the aircraft levelled off at FL280. 

At 1245:51, the Simpson region controller requested the pilot change their radio communication frequency to 122.1 MHz as the aircraft continued its journey to the northwest. This change was acknowledged by the pilot, but the controller did not receive radio communications from the flight on the newly-assigned frequency. 

Initial loss of radio communications

Between 1247:51 and 1317:48, the Simpson region controller made 12 separate radio broadcasts attempting to re-establish radio communication with the pilot. The controller also attempted to contact the pilot on high frequency radio, and by relaying messages via the flight crew of a passenger transport aircraft that was operating in the vicinity of VH-HPY. 

During this time the controller identified that VH-HPY was diverging from track, by about 2 km laterally, and the shift manager (SM) was informed (see Air traffic services). At 1318:20, ATC declared an uncertainty phase (INCERFA)[4] (see Emergency phases) and the air traffic management director (ATMD) was made aware of the developing situation (Figure 3). 

Figure 3: Sequence of ATC actions and communication events between 1300–1430

Plot of changes in aircraft altitude and the sequence of radio communication events throughout the accident flight from 1300–1430

Position information including altitude and time was obtained from ADS-B data that was broadcast from VH-HPY. Source: ATSB

At 1337:46, the ATMD attempted to contact the pilot using the mobile telephone number listed on the flight plan, but the pilot did not answer the call. At 1338:36, the pilot returned the ATMD’s phone call, and they had a brief conversation during which the pilot advised that they had ‘no joy’ on radio frequency 122.4 MHz, rather than the instructed frequency of 122.1 MHz (see Telecommunications). The ATMD determined that the pilot’s speech was ‘slower’ than normal and ‘flat’, and these concerns were shared with the SM at the conclusion of the call. At 1340:00, the INCEFRA was upgraded to an alert phase (ALERFA)[5] (see Emergency phasesand the hypoxic pilot in-flight emergency response (IFER) checklist was initiated (see Hypoxic pilot procedures). 

At 1340:15, the controller commenced radio broadcasts to the pilot as part of the IFER hypoxia checklist. These transmissions included the instructions:

- Oxygen, oxygen, oxygen, descend to one zero thousand feet. 

At the same time, the ATMD called the pilot’s mobile phone, but the pilot did not answer. The ATMD left a voicemail message requesting the pilot check their oxygen and call back ATC. 

At 1341:11, the crew of a RAAF aircraft that was in the vicinity of VH-HPY offered to assist the controller to contact the pilot. The controller agreed and a short time later the RAAF crew reported hearing a broken transmission, possibly from VH-HPY, but they were unable to establish contact with the pilot.

At 1341:31, the pilot of VH-HPY transmitted a radio broadcast on frequency 122.1 MHz, providing callsign, flight level, and radio frequency, but the controller was unable to re-establish 2-way communications. Between 1341:31 and 1350:51, the controller continued to broadcast instruction for the pilot to descend the aircraft to 10,000 ft. The controller also attempted further relays via other aircraft in the vicinity of VH‑HPY on various frequencies, including the international air distress frequency 121.5 MHz. 

At about 1348:00, ATC sent 2 text messages to the pilot’s mobile phone and an email requesting they check their oxygen and pressurisation and contact them on frequency 122.1 MHz. No response was received. 

Re-establishment of radio communications

At 1349:13, the crew of the RAAF aircraft advised the controller that they had heard a ‘weak’ transmission from the pilot of VH-HPY on frequency 118.6 MHz. In response, the controller requested the crew of the RAAF aircraft make another broadcast to include the statement ‘oxygen, oxygen, oxygen descend to one zero thousand feet’. The crew of the RAAF aircraft made 2 such broadcasts and, at about 1350, they established contact with the pilot of VH-HPY. 

During this time, the ATMD and SM telephoned the AGAIR head of flying operations (HOFO), advising that contact had been lost with the pilot of VH-HPY and that they suspected the pilot was potentially affected by hypoxia (see Telecommunications).

At 1350:50 the crew of the RAAF aircraft relayed to the controller that VH‑HPY was ‘ops normal’ and maintaining FL280. ATC subsequently downgraded the ALERFA to an INCERFA. At 1351:08, the controller requested that the RAAF crew instruct the pilot to call ATC on frequency 123.95 MHz. At 1351:59, the controller re-established radio communications with the pilot of VH‑HPY on this frequency and the pilot reported ‘ops normal’. About 1 minute later, ATC cancelled the INCERFA phase.

Between 1352:08 and 1357:34, several communications took place between the controller and the pilot. During this time, and 2 minutes after ATC had cancelled the INCERFA phase, the controller asked the pilot ‘just confirm your oxygen system is ops normal’, to which the pilot responded ‘affirm’. The controller later recalled that they had asked about the oxygen system because they had concerns there was a potential hypoxia event and wanted the pilot to look at the oxygen system in case there was a problem. The ATMD recalled that they requested the controller query the status of the oxygen system as a ‘surety check’. The controller recalled that the pilot’s speech at that time was ‘clear and concise’, and they were satisfied with the pilot’s delivery of speech.

At 1357:34, the pilot was provided with an ATC clearance to undertake operations near Mount Gordon. ATC communication recordings showed that the pilot confirmed the clearance at 1357:43, and then twice requested confirmation that the controller had copied their clearance readback (1359:26 and 1400:15). The controller then responded at 1400:19, advising the pilot that the communications were at low strength and could the pilot adjust their microphone. The pilot replied at 1400:57 and the controller then confirmed they had received the pilot’s confirmation of the clearance. At 1401:23 the pilot then confirmed the clearance again. The controller recalled that, during this time, a lot of activity took place near their console related to the status of the aircraft (see Simpson region controller divided attention). 

The radio recordings indicate that the pilot’s rate and volume of speech had substantially decreased from earlier communications and were worsening. During the radio transmission that commenced at 1401:23 the pilot had difficulty pronouncing the location ‘Cloncurry’ and they incorrectly stated the airwork would take place near ‘Mount Ball’, which was then corrected to ‘Gordon’. 

At 1419:19, the controller requested the pilot change frequency to 122.4 MHz, but no response was received. Between 1419:19 and 1427:15 the controller attempted to contact the pilot 8 times without receiving a response.

Departure from controlled flight

Recorded data indicated that, at 1423:20, the aircraft’s airspeed began to reduce from a cruise airspeed of about 236 KTAS.[6] At 1425:25, the airspeed had decreased to about 138 KTAS and the aircraft departed controlled flight (see Flight performance analysis). The aircraft initially entered a descending anticlockwise[7] turn with an increasing rate of descent. At an altitude of about 10,500 ft, the aircraft transitioned into a tight clockwise helical descent, likely an aerodynamic spin,[8] with a subsequent average rate of descent of about 13,500 ft/min (Figure 4). 

Figure 4: Flight path of VH-HPY during the descent from FL280

Flight path of VH-HPY during the descent from FL280.

Source: Google Earth, annotated by the ATSB

Two witnesses at a nearby mining facility observed the aircraft descending in a nose-down, clockwise, corkscrew motion and described hearing a ‘whirring’ noise. The witnesses recalled that motion momentarily stopped part way down, before re-entering the nose-down corkscrew descent.

At about 1427:15, the aircraft collided with terrain 55 km south-east of Cloncurry. The 3 occupants were fatally injured, and the aircraft was destroyed by impact forces and a fuel-fed post-impact fire.

Context

Personnel information

Pilot
Aeronautical experience 

The pilot held an air transport pilot licence (aeroplane) and a commercial pilot licence (helicopter), issued in February 2005 and August 2009, respectively. At the time of the accident, the pilot had accumulated about 4,900 hours total aeronautical experience, which included about 3,200 hours operating turboprop, jet, and high-performance Royal Australian Air Force (RAAF) military aircraft. This included unpressurised aircraft with supplemental oxygen systems (Pilatus PC-9) and pressurised aircraft (Beechcraft B200 and Learjet L35/36). Training records provided by the RAAF indicated the pilot had completed 2 altitude chamber training exercises,[9] one in 1995 and the second in 2019.

Gulfstream 695A training and experience

In August 2023, the pilot commenced work with AGAIR. They had not previously flown a Gulfstream 695A. 

On 15 August 2023, the pilot undertook Gulfstream 695A training and completed a flight review the following day. This training was arranged by AGAIR, and undertaken in VH-HPY, but the training and review were conducted by an independent training provider. 

During the training, the pilot demonstrated competent use of the aircraft systems including management of the pressurisation system. The pilot also conducted a simulated depressurisation scenario from FL150, which involved the use of oxygen and an emergency descent. The training notes made by the instructor about the pilot’s performance during this activity stated:

Emergency descent - best initiated with roll, using the secondary effect (yaw) to pitch the nose down to the required attitude without causing negative load factor. 

The training and flight review were completed within 2.9 hours of flight time and the pilot was assessed by the instructor as competent to operate the aircraft type as pilot in command (PIC). The pilot commenced flying as PIC for AGAIR on 28 September 2023 and they were initially supervised by the AGAIR chief operating officer (COO) over ‘3 or 4 flights’ (see AGAIR chief operating officer actions). There was no training file kept on the pilot’s performance during the supervised flights. 

In the 3 months after starting with the operator until the accident, they had accumulated a total of about 102 hours flight time, all flying VH-HPY mostly undertaking line scanning flights from Toowoomba.

After review of the draft ATSB investigation report the operator provided a record indicating the pilot of the accident flight completed a ‘line check’ flight in VH-HPY on 9 August 2023 with the AGAIR head of flying operations (HOFO). 

Medical information

The pilot held a class 1 aviation medical certificate that was issued on 27 February 2023 and was valid at the time of the accident. Their certificate had a restriction requiring reading correction to be available while exercising the privileges of their licence. The pilot’s aviation medical records were provided for the period 2022–2023 and their general practitioner records were provided for the period 2021–2023. Overall, these records indicated no significant medical conditions or abnormal physical findings. 

At the time of the accident, the pilot was taking medication for high cholesterol. In 2019 they underwent a coronary angiography, which showed no calcium and no soft plaque formation. The pilot had also visited a cardiologist in December 2021 due to family history, and undertook a stress electrocardiogram in November 2022, which identified no issues. In April 2023, the pilot injured their Achilles tendon and underwent surgical repair. The injury was reported to the Civil Aviation Safety Authority (CASA) on 18 April 2023, and the pilot was cleared to resume flying duties on 22 May 2023. The pilot was reported to have recovered well from their Achilles injury. Overall, the pilot was reported to have been fit, active and healthy, with no known stressors. 

Recent history

The pilot had 8 duty free days prior to the commencement of their most recent period of duty. This period started on 1 November 2023. They conducted a 1.3 hour flight from Essendon, Victoria, to Hay, New South Wales, on 1 November, and a 3.7 hour flight from Hay to Toowoomba on 2 November.

The pilot was reported to have gone to bed at around 2030–2100 the night prior to the accident and was known to wake early and undertake morning exercise. The collision with terrain occurred mid-afternoon after they had been flying about 3.5 hours that day. The ATSB reviewed their recent work-rest history and based on the available evidence, it was considered very unlikely that the pilot was experiencing a level of fatigue known to adversely affect performance.

Camera operator 1
Aeronautical experience

Camera operator 1 joined AGAIR in July 2021. They were not employed as a pilot by the organisation, but they held a commercial pilot licence (aeroplane), issued in February 2020. At the time of the accident, they had about 434 hours total aeronautical experience, including 72 hours on multi-engine piston aircraft.

Medical

Camera operator 1 held a class 1 aviation medical certificate that was issued on 14 November 2022 with no restriction. The medical certificate was valid at the time of the accident. Their aviation medical records were provided for the period 2021–2022. These examinations indicated no significant medical conditions or abnormal physical findings. Camera operator 1 was reported to be in ‘very good health’ with no known medical conditions.

Camera operator 2 
Aeronautical experience

Camera operator 2 was a United States citizen who had experience in the construction and operation of the imaging system fitted to VH-HPY (see Aerial survey camera system). They joined AGAIR in October 2023, and had conducted 5 line scanning flights in VH-HPY prior to the accident flight. They did not hold a flight crew licence, but they had received about 4 hours instructional flight training in the year prior to the accident. 

Medical

Camera operator 2 did not hold an aviation medical certificate, nor were they required to. They were reported to be ‘very healthy’ with no known medical conditions.

Post-mortem and toxicology 
Autopsy results

The post-mortem examinations determined that the occupants of the aircraft had sustained multiple injuries during impact that proved fatal. The results of the examinations did not indicate any significant natural disease that could have contributed to the accident. However, the examinations were limited due to the nature of the impact and resulting fire. There were no indications that the occupants of the aircraft had inhaled products of combustion.

Toxicology results

Toxicology testing was conducted and no drugs were detected, however the validity of the testing was degraded due to changes that occur post-mortem. Alcohol and carbon monoxide testing could not be completed using the samples obtained. 

Aircraft information

General information

The Gulfstream 695A is a high-wing, pressurised, twin-engine aircraft powered by 2 Garrett TPE331-10-511K turboprop engines. The aircraft was designed as a business and personal aircraft with seating capacity of up to 11 people.

The accident aircraft, serial number 96051, was manufactured in 1982 and in January 1983 commenced operations in South Africa. During this time the aircraft’s air conditioning system was replaced with an approved alternative system.[10] In 2014, prior to the aircraft being exported to Australia, the aircraft underwent refurbishment, which included a new avionics suite and interior, and the aircraft was repainted. Additionally, the original Dowty Rotol propellers were replaced with Hartzell propellers under a supplemental type certificate.[11]

The aircraft was first registered in Australia as VH-HPY on 11 November 2014. Its registration was held by AGAIR since 14 September 2016 and was initially used for birddog flights[12] (Figure 5). 

The aircraft was configured with 2 crew seats, 4 passenger seats, and a bench seat in the rear. The last periodic inspection was completed on 1 November 2023. At this time, the aircraft had accumulated 7,566.1 hours total time in service.

Figure 5: VH-HPY August 2023

Figure 5: VH-HPY August 2023

Source: Cameron Marchant

Aircraft systems
Aerial survey camera system

To expand its operational capabilities, AGAIR elected to modify VH-HPY to undertake aerial surveys of natural disasters such as bushfire and flood by fitting an Overwatch Imaging TK‑7 camera system. 

To modify the aircraft, AGAIR engaged an approved aircraft design organisation to prepare the engineering order,[13] and the installation was carried out by General Aviation Maintenance (GAM). Work on the modification began in June 2021 and had been partially completed when the aircraft recommenced operations in August 2021. In November 2021, VH‑HPY returned to GAM and the modification was completed and certified on the maintenance release.[14] The engineering order, associated drawings, and a flight manual supplement specific to VH-HPY, were approved by the aircraft design organisation in February 2022.

Pressurisation system

Generally, aircraft that are intended to be operated at altitudes over 10,000 ft are equipped with a pressurisation system. As the aircraft climbs, the air pressure outside the cabin decreases, and at the same time the aircraft’s pressurisation system maintains the pressure inside the cabin to a level that allows normal breathing (without the use of supplemental oxygen). The environment maintained by the pressurisation system is known as the cabin altitude. The difference between the pressure inside the cabin and the pressure outside the cabin is known as cabin differential pressure. Pressurised aircraft have a stipulated maximum differential pressure because of the loads that pressurisation places on an aircraft’s fuselage.

The Gulfstream 695A is pressurised by ducting air from both engines (known as bleed air) into the cabin and controlling its flow overboard via outflow safety valves to maintain the desired cabin pressure. The source of bleed air can be selected within the cockpit. A cabin pressure controller, also located within the cockpit, is used to manage the cabin pressure from take-off, through climb, cruise, and descent. The controller also prevents exceedance of the maximum differential pressure of 6.8 psi (see Appendix A – Gulfstream 695A systems information). The Gulfstream 695A is certified to operate up to 35,000 ft above mean sea level. At this altitude, and at the maximum differential pressure, the cabin altitude would be 9,600 ft. The pilot’s operating handbook (POH) requires the pilot to ‘limit flight altitude to maintain 10,000 ft cabin altitude’ should the cabin altitude exceed the selected value.

Figure 6: VH-HPY cockpit layout 

Figure 6: VH-HPY cockpit layout

Note: Image captured prior to the accident. Source: Cameron Marchant, annotated by the ATSB

The Gulfstream 695A is fitted[15] with a cabin altitude visual and aural warning system that activates when the cabin altitude is at or above 11,000 ft (±500 ft) (Figure 6). When activated, ‘CABIN ALT’ illuminates in red on the glareshield annunciator panel and flashes for 10–20 seconds before remaining steady. This is accompanied by an aural tone that pulses 6 times per second. The aural warning can be silenced by pressing a button on the left engine power lever (see Appendix A – Gulfstream 695A systems information).

In the event of illumination of the ‘CABIN ALT’ annunciator, accompanied by the aural warning tone, the POH requires the pilot to don their oxygen mask, verify passengers were receiving oxygen, and initiate a descent to 12,000 ft or below (Figure 7).

Figure 7: Cabin altitude annunciator emergency procedure

Figure 7: Cabin altitude annunciator emergency procedure

Source: Ontic

Oxygen system

The Gulfstream 695A is equipped with an oxygen system that provides life support in the event of an emergency. The POH states that:

The airplane is equipped with a high pressure, gaseous oxygen system which provides supplemental breathing oxygen to the crew and passengers in the event of cabin depressurization during high altitude operation, or in the event cabin air becomes contaminated. The system will provide oxygen for sufficient time to permit a planned descent to an altitude where supplemental oxygen is no longer required.

Oxygen is stored in a cylinder located in the rear fuselage and, when full, can supply oxygen to 3 people for about 29 minutes. The cylinder is full when filled to 1,800 psi. The passenger oxygen system switch is recessed into the sidewall on the right side of the cockpit, alongside a cylinder pressure gauge for the aircraft oxygen system (see Appendix A – Gulfstream 695A systems information).

The pilot and copilot oxygen masks are designed for rapid donning and are positioned on hooks immediately behind the pilot and copilot seats for ease of access. The masks incorporate a microphone for radio communications. Passenger oxygen masks are stowed in containers at various locations in the cabin lining above the passenger seats (see Appendix A – Gulfstream 695A systems information). 

Autopilot

The autopilot fitted to VH-HPY was a Collins AP-106 and it was integrated with the aircraft’s instruments. The Collins AP-106 is a 3-axis system that stabilises the aircraft about its roll, pitch, and yaw axes. The system can operate in various modes including pitch hold, heading, navigation, approach, back-course, altitude, and indicated airspeed. Both pilot and copilot control wheels have an autopilot release switch (see Appendix A – Gulfstream 695A systems information). 

A subcomponent of the autopilot system, the trim servo monitor, has fault detection and diagnostic capabilities that automatically disengage the autopilot if a discrepancy or malfunction is detected. One such potential fault condition is the exceedance of threshold voltages within a servo as it works against an aerodynamic or mechanical force. 

The ATSB interviewed 3 pilots who had previously flown VH-HPY for AGAIR. Two pilots described the autopilot as being unreliable at times. One recalled that the autopilot would not hold altitude well and would ‘chase’ the target by +/- 100 ft. Another recalled that the system would be fine in smooth air, but if the aircraft experienced turbulence that required multiple control inputs, the autopilot would disconnect without any prior indication after about 10 minutes. Another pilot regarded the autopilot favourably. Maintenance records for VH‑HPY show multiple instances of autopilot defects and subsequent rectifications.

Engine controls

The Gulfstream 695A engines are controlled from the cockpit using a power lever and a condition lever for each engine. The autopilot does not interface with the engine controls.

Radios

The aircraft was fitted with very high frequency (VHF) and high frequency (HF) radios, along with an additional communication unit for birddog flights and a satellite phone. Pilots wore headsets with boom microphones and were able to transmit by pressing a thumb-operated button on the outboard grip of each control wheel. Handheld microphones were also stowed on each control column.

On the day of the accident, routine communications between air traffic control and VH-HPY were via VHF. VHF radio is limited to ‘line of sight transmissions’, with communication range increasing with aircraft altitude.

Maintenance history
Recent maintenance

The ATSB reviewed the maintenance records for VH-HPY. This included records from when the aircraft was operating in South Africa (from 1983 to 2014) and the Australian records (from 2014 to 2023).

The last maintenance activity prior to the accident was carried out by General Aviation Maintenance (GAM) at Essendon Airport, Victoria, in late October 2023. The work carried out was predominately scheduled maintenance along with some minor defect rectifications. The maintenance provider also carried out checks on the left and right engine bleed air valves after being informed by the AGAIR chief operating officer (COO) that the pressurisation system was malfunctioning (see Aircraft pressurisation defects). The aircraft was released for service on Wednesday 1 November 2023, 3 days prior to the accident flight. The maintenance provider advised that after the first flight, the pilot who accepted the aircraft called and reported to them that the aircraft systems including pressurisation were working normally.

Aircraft pressurisation defects

In 2011, while the aircraft was operating in South Africa, the cabin door seal was replaced to address a pressurisation issue. In 2013 a defect was recorded where the maximum cabin differential pressure of 6.8 psi could not be reached. It was determined that cabin air was leaking from the cabin doorstep area, and this was rectified. Correspondence showed that, when preparing the aircraft to be exported to Australia, the aircraft was not capable of attaining the maximum cabin differential pressure. Significant work was carried out to rectify the issue, including major component replacements, and the cabin interior was removed for access to seal the fuselage.

When VH-HPY was purchased by AGAIR in 2016, maintenance was then provided by GAM at Essendon Airport. The aircraft was reportedly difficult to pressurise when it arrived, which was identified to be because of a leak from a sub-component of the pressurisation system known as a volume tank. Additionally, to address the pressurisation issue a few minor cabin leaks were repaired. A pilot who had flown VH-HPY when it initially entered service with AGAIR recalled that its pressurisation system did function, however if the aircraft rate of climb was high, the pressurisation system would malfunction.

Two of the pilots who had previously flown VH-HPY for AGAIR recalled intermittent pressurisation issues, where the aircraft would not pressurise higher than 2 psi differential pressure. The third pilot reported the pressurisation was okay but had noticed the high rate of climb issue. The unreliability of the pressurisation system reportedly could be managed by selecting the maximum flow of bleed air to the cabin (which can be used at any time except take-off and landing), and by turning the cabin heating up. Additionally, it was also reported that pressurisation seals in the cockpit for the rudder controls were known to leak, and during a flight in late August 2020, the seal dislodged and depressurised the aircraft. On 4 August 2023, the AGAIR HOFO said to GAM that the pressurisation system was working ‘perfectly’.

On 16 October 2023, the pilot of the accident flight emailed the AGAIR COO stating that the pressurisation of VH-HPY was ‘stuck on 2.0 differential for [a] prolonged period’ and because they needed to operate at FL280, they had ‘used a bit of oxygen’ (see Pilot of the accident flight actions). According to the Gulfstream 695A POH, operating at FL280 with a differential pressure of 2.0 psi will result in a cabin altitude of 19,800 ft. The email also requested the aircraft oxygen cylinder be refilled by a maintenance provider at Toowoomba, Queensland where the aircraft was based at the time. Records from the maintenance provider showed that the oxygen cylinder was serviced (refilled) from 1,000 psi to 1,700 psi on 18 October 2023 (see Appendix A – Gulfstream 695A systems information).

On 22 October 2023, the pilot of the accident flight emailed the AGAIR COO and chief executive officer (CEO), who also held the positions of HOFO and head of aircraft airworthiness maintenance control (HAAMC), advising them of issues relating to the pressurisation system of VH-HPY. The email stated there was ‘no change…same cycles and fixes’. The defect was described in the email as the cabin differential being stuck at 2.2 psi (see Pilot of the accident flight actions). 

On 27 October 2023, the AGAIR COO operated the aircraft as PIC and captured a video that showed the aircraft at FL280 with a cabin altitude of 19,000 ft (see AGAIR chief operating officer actions). The COO attempted to ascertain why the pressurisation system was malfunctioning by using the bleed air selector (see Appendix A – Gulfstream 695A systems information) to shut off engine bleed air from each engine in turn. When the pilot selected ‘RIGHT CLOSE’, there was no change in cabin altitude, or when ‘BOTH OPEN’ was re-selected. When ‘LEFT CLOSE’ was selected, the cabin vertical speed indicator showed the cabin altitude climbing at 2,000 ft/min. 

The video was sent to the maintenance provider and the aircraft was flown to their facility on 29 October 2023 for scheduled maintenance. The left and right engine bleed air valves were removed and functionally checked in-house before being refitted to the aircraft. The maintenance provider reported that no faults were found during the valve functional checks or when the pressurisation system was later checked on the ground. The maintenance provider stated that, prior to the completion of maintenance, the aircraft oxygen system was refilled. A maintenance release was issued on 1 November 2023 and the aircraft re-entered service.

Service letters to address cabin leaks

In September 2008, the then type certificate holder for the Gulfstream 695A, and other aircraft in the series, issued 2 service letters with guidance for addressing cabin pressurisation leaks. Service letter 382 was for aircraft in the series that were pressurised ‘to the floor’, while service letter 383 was for aircraft that were pressurised ‘to the skin’. Service letter 383 was applicable to the Gulfstream 695A and it stated:

A recurring problem in pressurized Twin Commanders is maintaining cabin pressure when flying at high altitude. This publication is presented in an effort to standardize the procedure for sealing the known and most significant leakage areas.

The service letter advised that to establish a leakage rate, the aircraft was to be pressurised on the ground using either the engines or with a pressurisation unit. Aircraft that exceeded the maximum allowable leakage rate required rectification. The service letter identified the locations where the most significant leaks occur and provided detailed instructions to address them.

Operations with unserviceable pressurisation system components

The Gulfstream 695A POH contains a minimum required equipment list (MREL) detailing components and systems that must be operable for the aircraft to be considered airworthy. It also lists components and systems that can be inoperable provided that certain operating limits were followed. For inoperative pressurisation system components, the MREL operating limitation requires the aircraft to be only operated unpressurised (see Supplemental oxygen legislative requirements).

Recording of aircraft defects
Requirements

The maintenance release document used for VH-HPY was a standard Civil Aviation Safety Authority (CASA) form 918. The document was used to identify the maintenance release period of validity, list scheduled maintenance due in that period, and to record the hours flown along with landings and pressurisation cycles.[16]

Another principal function of the maintenance release was to record defects and major damage that occurred during the maintenance release period of validity and show the actions taken to rectify them. Part 4B of the Civil Aviation Regulations 1988 did not make a distinction between minor and major defects. However, major defects were defined as:

… those that have caused, or that could cause either: a primary structural failure, a control system failure, an engine structural failure, or a fire. 

Parties required to make entries (known as endorsements) on the maintenance release for defects or damage included the holder of the certificate of registration, the operator, and the flight crew. When a defect was endorsed on the maintenance release, the aircraft was not able to be flown until a formal assessment and deferral of the defect was carried out, or an entry was made to ‘clear’ the original endorsement (known as a clearing endorsement). Clearing endorsements were generally made by approved maintenance personnel, and in accordance with approved data such as the aircraft maintenance manual.

The AGAIR operations manual (OM) required the PIC to record defects and their symptoms on the aircraft’s maintenance release. The PIC was then required to liaise with the HAAMC, who would in turn liaise with the maintenance provider to determine what action was required.

Provision was given in the OM to defer defects that ‘do not impinge on the airworthiness of the aircraft’. Examples of this were given in the manual:

...the Pilot-in-command must consider whether or not the defect will render the aircraft unserviceable for a particular category or type of operation. For instance an unserviceable landing light would not render the aircraft unserviceable for day VFR operations but would render it unserviceable for night operations.

…some minor defects such as paint scratches or dents in the structure would not normally impinge on airworthiness whereas cracks in a wing spar certainly would.

The OM contained provision for the use of minimum equipment lists (MEL) supplied by the aircraft manufacturer. Prior to their use by AGAIR, an MEL was required to be approved by CASA, specific to a particular aircraft and operator. The MEL[17] provisions stated in the Gulfstream 695A POH were not approved for use with VH‑HPY at the time of the accident.[18]

Unapproved recording of defects

Some defects that were identified on VH‑HPY and another AGAIR aircraft, VH‑LVG, were recorded using unofficial means to the operator or maintenance provider. On 21 April 2021, the AGAIR HOFO emailed GAM requesting various tasks to be carried out on VH‑HPY, VH‑LVG, and VH‑LMC when the aircraft arrived for maintenance. The email also listed defects on each of the aircraft. None of the 4 defects listed for VH‑HPY in the email had been entered on the relevant maintenance release. Other examples included emails from the pilot of the accident flight to AGAIR managers describing a pressurisation defect with VH‑HPY (see Recording of pressurisation defects), and an internal GAM email listing defects on VH‑LVG.

The ATSB interviewed pilots who had flown VH‑HPY for AGAIR. One pilot recalled that defects would be communicated by phone to GAM. Other pilots recalled that defect lists were compiled to be rectified during the aircraft’s next scheduled maintenance. 

The ATSB reviewed a total of 15 expired maintenance releases14 that had been retained with the maintenance logbooks from VH-HPY. These maintenance releases dated from November 2014 when VH‑HPY was first registered in Australia. Of these maintenance releases, 13 were from when the aircraft commenced operations with AGAIR in September 2016, and defect entries had been made on 6 of these. The defect entries had been predominately made by the maintenance provider, and the remaining 7 maintenance releases were either blank or had entries for scheduled maintenance activities.

Recording of pressurisation defects

After VH-HPY sustained an in-flight depressurisation in August 2020, an entry for the defect and a clearing endorsement was made by a licensed aircraft maintenance engineer (LAME) on the maintenance release. 

Of the remaining known instances of pressurisation defects, there were no relevant entries on the aircraft’s maintenance releases (Table 1).

Table 1: Recording of known pressurisation defects affecting VH‑HPY since 2016

Date and defect description Approved recordUnapproved recordRectification
2016 – difficult to pressuriseNo defect recorded on the maintenance release or in the airframe logbook.UnknownVolume tank found leaking, minor cabin leaks repaired
Circa 2016 – system not functioning correctlyNo defect recorded on the maintenance release or in the airframe logbook.UnknownMaintenance action (if any) unknown
Multiple instances over an unspecified time of the cabin not pressurising past 2 psi differentialNo defects recorded on the maintenance release or in the airframe logbook.UnknownMaintenance action (if any) unknown
17 July 2018 – temperature modulating valve stuck, no auto temperature control

No defect recorded on the maintenance release.

Entries for defects in the airframe logbook and on GAM internal worksheets.

UnknownTemperature modulating valve and cabin temperature sensor replaced
25 June 2019 – left and right engine bleed air shut-off valve connectors corroded

No defect recorded on the maintenance release.

Entries for defects in the engine logbooks and on GAM internal worksheets.

UnknownConnectors replaced
19 June 2020 – cabin de‑pressurisation circuit breaker unserviceable

No defect recorded on the maintenance release.

Entries for defects in the engine logbooks and on GAM internal worksheets.

UnknownCircuit breaker replaced
26 August 2020 – cockpit rudder control seal dislodged resulting in cabin de‑pressurisationEntry for defect and clearing endorsement made on maintenance release by a LAME.UnknownRudder control boot replaced
17 November 2021 – troubleshooting a pressurisation defectNo defect recorded on the maintenance release or in the airframe logbook.GAM invoice for the work carried outSystem checks, testing of temperature modulating valve, sensors, and cleaning and bench testing of mass flow valve
16–22 October 2023, multiple instances of cabin not pressurising beyond the 2 psi differentialNo defects recorded on the maintenance release or in the airframe logbook.Pilot of the accident flight emailed AGAIR managers (on 2 occasions) stating the nature of the defect and that they were using oxygenMaintenance action (if any) unknown
27 October 2023 – Cabin not pressurising beyond the 2.4 psi differentialNo defect recorded on the maintenance release. Removal, testing, and reinstallation of the left and right engine bleed air valves captured under a scheduled maintenance task (bleed air system leak check).Prior to the aircraft’s arrival at the maintenance facility, another pilot sent a video in-flight showing the performance of the pressurisation system along with a text message to the maintenance providerLeft and right engine bleed air valves removed, functionally checked, and refitted

Meteorological information

Meteorological records[19] from the Bureau of Meteorology (BoM) at the time of the accident were reviewed by the ATSB. This predicted westerly winds at 40 kt, temperature −30°C, with no significant nearby weather events at FL280.

Meteorological conditions were also recorded by the BoM automatic weather station at Cloncurry Airport (55 km north-west of the collision location). At 1430 the surface wind was 6 kt from 190° true, visibility greater than 10 km, no detected cloud, temperature 40°C, dew point 2°C, and no rainfall since 0900.

Recorded data 

The aircraft was not fitted with a flight data recorder or a cockpit voice recorder, nor was it required to be. During the accident flight, data was being transmitted by the automatic dependent surveillance broadcast (ADS-B) and Mode S transponder[20] equipment fitted to the aircraft. Flight data was also being broadcast from a TracPlus[21] unit fitted to the aircraft, which could be used by the fire services and AGAIR to track the location of the aircraft during flight. A navigational application (OzRunways) was installed on a tablet computer on board the aircraft and that device also broadcast flight data. The OzRunways data was recorded at 5 second intervals. The parameters captured from all systems were: time, aircraft position, GPS and pressure (barometric) altitude, altitude rate of change, groundspeed, and heading.

Navigation system

A Garmin GTN-750 navigation system was recovered from the accident site and transported to the ATSB Canberra technical facility. Examination of the unit identified that it was not recording flight data. 

ADS-B data

The ADS-B data provided the highest reporting frequency (~0.5 seconds), and altitude was reported to the nearest 25 ft. This data was captured from shortly after departure until the aircraft descended to about FL240 during its final descent (Figure 8). 

Figure 8: Altitude profile of the accident flight throughout its duration with key moments (phases) displayed

Altitude profile of the accident flight throughout its duration with key moments  (phases) displayed.

The blue trace represents pressure altitude and the green trace represents GPS altitude. Source: ATSB

Pressure and global positioning system altitude discrepancy

The ADS-B data that was broadcast from the aircraft during the accident flight contained a discrepancy between the pressure altitude and the GPS altitude (Figure 8).[22] At the start of the second cruise phase, the broadcast pressure altitude was 28,000 ft while the GPS altitude was 29,400 ft. At the end of the second cruise phase (approximately 2 hours later), the broadcast pressure altitude was 28,050 ft while the GPS altitude was 29,750 ft. The difference in pressure and GPS altitudes over the entire flight varied with altitude and flight time and is shown on a scatter plot below (Figure 9).

Figure 9: Scatter plot of pressure and GPS altitude discrepancy with altitude (left) and over time (right)

Scatter plot of pressure and GPS altitude discrepancy with altitude (left) and over time (right)

Source: ATSB

When the above data was corrected for local barometric pressure and GPS ellipsoid modelling, the difference in altitudes at the end of the second cruise phase of flight was about 1,400 ft. The GPS altitudes from ADS-B, OzRunways and TrackPlus, which had independent GPS sources and data processing, were broadly aligned over the entire flight, and it is therefore likely that the pressure altitude was reading low and the aircraft was likely flying at FL294 (i.e. the actual position of the aircraft was likely higher than indicated). The reason for the discrepancy could not be determined, although a static source leak inside the cabin could not be discounted. 

Initial descent to FL150

At 1141:12, while at FL280, the aircraft commenced a descent to FL150. The aircraft’s flight profile during this period was erratic with a fluctuating rate of descent that peaked to about 4,200 ft/min. The aircraft’s heading remained steady during the descent. The aircraft then maintained FL150 for a period of about 6 minutes before climbing back to FL280. No reason for the descent was provided to air traffic control and it was not part of the submitted flight plan. The AGAIR COO stated there was no operational reason for the descent to occur.

Flight performance analysis

General

The ADS-B, OzRunways and TrackPlus position and groundspeed data, combined with aircraft performance data, forecast conditions, and actual environmental conditions, were used to formulate likely aircraft performance during the flight. The engine power (maximum continuous power (MCP)), knots true airspeed (KTAS), knots calibrated airspeed (KCAS),[23] and vertical speed was calculated at points in time during the initial cruise, initial descent and the secondary cruise (Table 2). 

Table 2: VH-HPY performance assessment

PhaseMaximum Continuous Power setting (MCP %)True airspeed (KTAS)Calibrated airspeed (KCAS)Vertical speed (ft/min)

Initial cruise

 

48246  -N/A
Initial descent to FL150 (period from 27,500 ft–24,500 ft)25190 to 340185 to 230-3,000 to -4,200
Secondary cruise46257  -

N/A

 

Source: ATSB

Trajectory analysis was used to estimate the likely pitch angle, angle of attack, roll angle, speed, and rate of descent for the deceleration and loss of control phases of the flight.

Deceleration phase

Commencing at 1423:20, the deceleration phase of the flight was assessed from 10 seconds after the transition from cruise until the start of the left descending turn (Figure 10). Over this 2‑minute period, the altitude reduced from 28,040 ft to 27,840 ft, with an initial vertical descent rate of 78 ft/min, increasing to 120 ft/min. However, over this same loss of altitude, a more substantial loss of airspeed occurred with a linear airspeed reduction from 236 KTAS (148 KCAS) to 138 KTAS (86 KCAS). This descent performance was estimated to require a power setting of about 25% MCP.

Figure 10: Deceleration phase

Figure 10: Deceleration phase

Source: ATSB

The aircraft stall speed at maximum weight was 78.6 KCAS. The corrected stall speed at the calculated operating weight of the aircraft was about 74 KCAS, 12 kt lower than the calibrated airspeed at the end of the assessed period. It was calculated that the aircraft had approximately 25% MCP applied at the end of the descent, which would slightly decrease the stall speed, giving further margin from the stall. 

The minimum control speed in the air (VMCA)[24] for the aircraft was documented to be 95 KCAS. However, this speed assumes one engine inoperative with the other at MCP. Assuming in this instance one engine failed inoperative, and the other engine remained at half power (that is, total aircraft power at 25%), the minimum control speed was calculated to have been approximately 67 KCAS. This was below the power off stall speed for the aircraft weight and below the recorded minimum speed. Thus, a minimum control speed departure was excluded as a potential reason for the flight profile of the aircraft.

Loss of control

The reliability of the ADS-B data diminished as the aircraft entered the descending left turn. However, trends in the data were able to be identified. At 1425:26 and an airspeed of about 78 KCAS, the aircraft entered a left roll. The roll rate was initially about 10 degrees per second (°/s), slowing to 0°/s 14 seconds later whereby the aircraft had rolled to approximately 75° left angle of bank. The angle of attack (AoA)[25] was estimated to stay reasonably constant over this period at around 8°, indicating a fixed elevator position. However, it was calculated from the data that the aircraft pitched to about 20° nose down due to the fixed AoA and excessive roll angle allowing the nose to drop. 

At 1425:40, the aircraft’s heading had turned through 85° and it had accelerated to about 106 KCAS. From this point, over the following 10 seconds, the angle of bank was estimated to reduce to around 45° and the nose-down pitch change slowed until it stabilised about 30° nose down all while the calculated AoA remained constant at around 8°. During this period, the aircraft’s heading turned through a further 100° and the speed increased to about 189 KCAS. The diameter of the turn was approximately 700 m (Figure 11). 

Figure 11: Deceleration and loss of control

Figure 11: Deceleration and loss of control

Source: ATSB

Because of the extreme attitude of the aircraft from this time on, the ADS‑B data and TrackPlus data became unreliable, likely due to the angle of the onboard antenna and reflected signals. The last reliable ADS‑B position information occurred at 1425:50 and at 25,500 ft standard barometric altitude and 189 KCAS. Only horizontal ADS-B position information remained valid for another 5 seconds, by which point the aircraft had turned through a ~270° track angle and crossed back through its original track. 

From this point, to about 10,500 ft, all data sources became unreliable and sporadic and no conclusions about flight path or attitude could be made. However, the data indicated an average vertical speed of about −19,500 ft/min, or 192 kt vertical speed, during the period from about 25,000 ft to 10,500 ft. 

At about 10,500 ft, the OzRunways altitude data stabilised and provided an average vertical descent rate of 13,500 ft/min. The final data point was at 1427:15 at an altitude of 1,800 ft. 

Wreckage and impact information 

Accident site

The aircraft was destroyed by the impact with terrain and a subsequent fuel-fed post-impact fire (Figure 12). The ATSB conducted an onsite examination of the aircraft wreckage. The ground impact marks and wreckage position indicated that the aircraft impacted terrain upright with a shallow, nose-down attitude with little forward momentum. Immediately surrounding the wreckage, numerous landscape features (a tree and termite mounds) remained upright and had not been disturbed by the aircraft impact or its liberated debris (Figure 13). The compression and displacement of the aft fuselage relative to the engines, the displacement of the inboard wing section and the aircraft nose, showed that the aircraft was rotating clockwise on impact with the terrain, which was highly indicative of a spin. 

Figure 12: Overview of the accident site

Figure 12: Overview of the accident site

Source: Queensland Police, annotated by the ATSB

Figure 13: Heavily disrupted and burnt remnants of the wreckage at the accident site 

Figure 13: Heavily disrupted and burnt remnants of the wreckage at the accident site

The surrounding landscape features (termite mounds and a tree) remained upright and were not disturbed from the impact. Source: ATSB

All major aircraft components were accounted for at the accident site. The disruption to the airframe from the impact and the subsequent fire damage limited the extent to which the aircraft could be examined. The oxygen cylinder fitted to the aircraft was located in the wreckage and its associated components had been significantly fire damaged, precluding any assessment of the oxygen system’s serviceability prior to the accident. Additionally, the components comprising the pressurisation system were unable to be assessed due to the extent of damage sustained.

Engines

Both engines had been significantly damaged by the post-impact fire, limiting the extent to which they could be examined. However, the low-pressure compressor of each engine was observed to have rotational damage, indicating that the engines were operating at impact.

Propeller assemblies

Both propellers were examined and photographed by the ATSB at the accident site. Assistance was sought from Hartzell Propeller personnel to interpret the photographic evidence. They advised that there were multiple indications to identify that the engines were operating and estimated them to be at a low to moderate power setting. These indications included blade bending (in multiple planes), twisting, fractures (including multiple blade tip fractures), chordwise scoring and rotational gouges. Additionally, blades from both propellers had separated from their hubs at the shanks, and internal components were fractured.

Crew locations

The pilot was found toward the front of the cabin, camera operator 1 was behind and to the left of the pilot, and camera operator 2 was behind and to the right of the pilot. However, the impact with terrain caused significant compressional damage to the cabin area of the fuselage and the location of the crew as found within the wreckage may not be indicative of their seated location during the flight. 

Fire 

Witnesses from a nearby mine site who observed the aircraft during its descent did not report any indications of fire until the aircraft collided with the ground, after which a fireball and rising smoke plume were visible. A fuel-fed fire persisted after the impact, which consumed most of the aircraft wreckage. The fire was extinguished by responders from the mine site.

Survivability

The impact with terrain was not survivable. 

Hypoxia

General

Hypoxia is a state where there is a deficient supply of oxygen in the blood, tissues and cells sufficient to cause an impairment of body functions. The human central nervous system demands about 20% of all inhaled oxygen to supply the brain. Any reduction in oxygen supply to the body will impact brain function, with higher reasoning portions affected first (US Federal Aviation Administration 2015). Severe exposure to hypoxia can result in the rapid deterioration of most bodily functions and, eventually, death (Gradwell 2016).

Hypoxia can result from a variety of factors including respiratory and cardiovascular deficiencies, blood disorders, pharmaceuticals and toxic substances, and a reduction in the oxygen tension in the arterial and capillary blood. The latter factor is known as altitude hypoxia, hypobaric hypoxia, or hypoxic hypoxia, and it is the most common form of oxygen deficiency in aviation (Gradwell 2016).

Altitude hypoxia

Within aviation, the typical cause of altitude hypoxia is the low oxygen tension of inhaled gas (air) associated with exposure to altitude. On ascent, as barometric pressure reduces, breathing ambient air will result in a reduction of the partial pressure and the molecular content of oxygen within the lungs. The result is an inadequate oxygen supply to the arterial blood and decreased oxygen available to the tissues (Gradwell 2016). 

Clinical features of altitude hypoxia

The clinical features of altitude hypoxia are described in Table 3. In general, the greater the altitude, the more overt and serious the features of hypoxia will be. Except for a possible headache, nausea or dizziness, a pilot is unlikely to experience other uncomfortable symptoms (US Federal Aviation Administration 2015). A loss of self-criticism usually results in a person remaining unaware of their deterioration in performance and, consequently, the presence of hypoxia. It is this insidious nature that makes the condition a significant hazard in aviation (Gradwell 2016). 

As noted in the table, although there is minimal impact below 10,000 ft, research has shown impaired task performance (with individuals unaware of their impairment) at cabin altitudes below 15,000 ft. With reference to the effect of altitude hypoxia on the performance of pilots, studies have shown an increase in procedural errors (Nesthus and others 1997), reduced flight profile accuracy (Steinman and others 2017), and reduced awareness of the environment (Steinman and others 2021). 

Table 3: Clinical features of altitude hypoxia 

AltitudeClinical features
Below 10,000 ft
  • Performance of well-learned and practised tasks generally is preserved
  • Short-term and long-term memory impairment at altitudes above 8,000 ft
10,000 ft–15,000 ft
  • Impaired task performance with subjects frequently unaware of impairment
  • Increased short-term and long-term memory impairment
  • Increased light sensitivity impairment
  • Severe generalised headache, nausea and dizziness
  • Physical capacity markedly reduced
15,000 ft–20,000 ft
  • Higher mental processes and neuromuscular control negatively affected
  • A loss of critical judgment and willpower
  • A loss of self-criticism, resulting in the subject usually being unaware of any deterioration in performance or the presence of hypoxia
  • Thought processes are slowed and mental calculations become unreliable
  • Reaction time increases
  • Psychomotor performance grossly impaired
  • Marked changes in emotional state are common. This may include a disinhibition of basic personality traits and emotions with an individual becoming elated or euphoric or pugnacious and morose
  • Occasionally, an individual may become physically violent
  • Hyperventilation may occur
  • Light-headedness, visual disturbances (including tunnelling of vision)
  • Reduced auditory acuity
  • Paraesthesia of the extremities and lips
  • Decreased muscular coordination with loss of the sense of touch
  • Physical exertion greatly increases the severity and speed of onset of symptoms and signs and may lead to unconsciousness
Above 20,000 ft
  • Comprehension and mental performance decline rapidly
  • Myoclonic jerks of the upper limbs
  • Unconsciousness occurs with little or no warning
  • Convulsions
  • Death

Source: Gradwell (2016)

Time of useful consciousness

The time of useful consciousness (TUC) is the interval between a person being exposed to a reduction in oxygen tension of the inhaled air to the time when they experience a specified degree of performance impairment (Gradwell 2016). It can also be considered the time after which an individual is no longer capable of taking appropriate corrective action to resolve the situation (for example, the use of oxygen and/or a descent to a lower altitude). The TUC does not denote the time to the onset of unconsciousness (US Federal Aviation Administration 2015).

The TUC at various altitudes is presented in Table 4. However, TUC is subject to considerable variation based on an individual’s general physical fitness, age, degree of training and previous experiences of hypoxia (Gradwell 2016). It is also affected by the rate of ascent, with a faster ascent resulting in a shorter TUC. For example, during a rapid depressurisation to altitudes between 25,000 ft and 43,000 ft, the TUC is reduced by about 50% (US Federal Aviation Administration 2015). 

Table 4: Time of useful consciousness at various altitudes

AltitudeTime of useful consciousness 
18,000 ft20–30 minutes
22,000 ft10 minutes
25,000 ft3–5 minutes
28,000 ft2.5–3 minutes
30,000 ft1–2 minutes
35,000 ft 30 seconds–1 minute

Source: US Federal Aviation Administration (2015)

Principal aviation causes

Within the aviation context, the principal causes of altitude hypoxia are: 

  • climbing to high altitudes without the use of supplemental oxygen
  • failure of the supplemental oxygen system, or oxygen set to an inadequate concentration and/or pressure
  • depressurisation of the cabin at a high altitude (Gradwell 2016).
Post-mortem indicators of altitude hypoxia

Altitude hypoxia rarely leaves any indications that would be detectable at a post-mortem examination.

Supplemental oxygen legislative requirements 

The Civil Aviation Safety Regulation (CASR) part 91 (general operating and flight rules) manual of standards 2020 required flight crew[26] to use supplemental oxygen:

  • for any period exceeding 30 minutes when the cabin pressure altitude was continuously at least FL125 but less than FL140
  • for any period when the cabin pressure altitude was at least FL140.

For passengers, an oxygen supply was required to be available for the entire period for any time when the cabin pressure altitude was at least FL150. Additionally, an aircraft was required to carry sufficient oxygen to meet the above requirements, and the oxygen was required to be made available through an oxygen dispensing unit in accordance with the supply requirements for that level.

Without affecting the above requirements, the same legislation also required a pressurised aircraft that was flown at an altitude of FL250 or more to have:

  • at least 10 minutes oxygen supply for flight crew, even if the entire period of relevant flight was less than 10 minutes
  • at least 10 minutes oxygen supply for passengers after descending below FL250 even if the entire period of relevant flight was less than 10 minutes.

The oxygen system fitted to VH-HPY complied with the legislative requirements to have a 10‑minute supply when operating the aircraft at FL250 or higher when pressurised. However, as described in Aircraft systems, the oxygen system for Gulfstream 695A aircraft was for emergency purposes (depressurisation, smoke and fumes etc) and not for the purpose of conducting normal operations (also see Appendix A – Gulfstream 695A systems information).

Operational information

Tasking

The flight had been contracted by Queensland Fire and Emergency Services (QFES) and the crew had been tasked to conduct line scanning of 10 areas of interest in Northern Queensland. The line scanning activity was to take place over 2 days, 4–5 November 2023, with the crew overnighting in Townsville, Queensland on 4 November.

Flight plan

The submitted flight plan stated the aircraft would depart Toowoomba Airport and climb to FL280. It would then fly at FL280 overhead Winton, Cloncurry, and Mount Gordon respectively, and conduct aerial work operation (line scanning) near Mount Gordon for a period of 40 minutes. The aircraft was then planned to land at Mount Isa, before travelling on to Townsville later that day (Figure 14).

Figure 14: Planned route

Figure 14: Planned route

Source: Google Earth, annotated by the ATSB

Fuel 

The aircraft had been refuelled on 3 occasions in the 3 days prior to the accident and had flown about 5 hours. However, the quantity of fuel on board the aircraft when the accident flight departed could not be determined from the records available. 

AGAIR line scanning 
History of line scanning operations

AGAIR commenced line scanning operations around early 2022, following the fitment of the TK-7 Overwatch camera to VH-HPY. VH-HPY was the only aircraft within the AGAIR fleet equipped to undertake the activity. The service was initially provided on an ‘ad-hoc’ basis and in 2023 AGAIR secured a ‘call when needed’ contract with QFES. The AGAIR COO operated as pilot in command of all AGAIR line scanning flights until the pilot of the accident flight commenced operations in September 2023.

Line scanning procedures

The AGAIR OM contained a generic section on aerial photography, but it did not contain specific procedures for the conduct of line scanning operations. 

The pilot of the accident flight had developed draft line scanning procedures for inclusion in the AGAIR OM. These procedures contained a section on tasking, which included information on the altitude line scanning operations were to be conducted. It stated:

The altitude missions are flown will depend on mission specifics. As a general guide for missions where a high coverage area is priority, the preference is to conduct scans as high as possible. This will ensure maximum coverage from the system while minimising the requirements for a high number of passes.

The tasking process will require refining with the clients’ requirements for considerations of weather and terrain. The imagery is affected by cloud and therefore this will dictate what height is feasible for the best product. 

Generally, F200 to F280 is the most effective for large area coverage imaging. The lowest feasible altitude is 5000 ft AGL though this will be dependent on the size of the area. Large areas at this level will require a high number of passes and produce a very large volume of data.

The pilot of the accident flight had emailed the draft procedures to the AGAIR COO on 10 October 2023, but they were not incorporated into the AGAIR OM at the time of the accident.

Line scanning practices

The normal flight profile, as explained by senior AGAIR management personnel, was for line scanning operations to be conducted at FL200‍–‍FL280 as the resolution of the thermal images was not impacted by increased altitude. Consequently, the higher the aircraft flew the greater the swath[27] of the images and the more ground area could be captured in one pass, resulting in increased efficiency of data acquisition.

However, thermal imagery could be affected by cloud and, depending on the cloud coverage, may require the aircraft to descend below cloud level to conduct imaging. In those scenarios, the lower limit for the operation of the camera was about 5,000 ft. 

The ATSB was advised by the AGAIR COO that transit flights to and from the fire area could be flown at any level, but transiting at FL280 would result in improved fuel efficiency in comparison to lower levels. The aircraft was also used for low level ‘birddog’ activities, where it was flown less frequently at higher altitudes.

A review of VH-HPY flights into or out of Toowoomba Airport over the period 4 September 2023–4 November 2023 indicated that 70% of flights involved a cruise at FL280. Since commencing operations with AGAIR, the pilot of the accident flight had flown 24 flights in VH-HPY as PIC, 19 of which were flown at FL280.

Operations at high cabin pressure altitudes
AGAIR chief operating officer actions

During interview, the AGAIR COO stated that they occasionally experienced the intermittent defect with VH-HPY’s pressurisation system while conducting line scanning operations. They recalled 2 occasions where they had continued the climb while the pressurisation system was defective and used oxygen.

The earlier event occurred about 12 months prior to the accident, where the COO recalled continuing the climb while the pressurisation system was defective. They recalled using the aircraft oxygen system, attaining the cruise level, and rectifying the defect by increasing the cabin heat.

The most recent example occurred on 27 October 2023, 8 days prior to the accident, during a line scanning flight from Toowoomba with the COO, as pilot in command, and camera operator 2 on board. The COO used their phone to video the cockpit indications of the defect. The video captured the aircraft in cruise at FL280, with a cabin differential of 2.2 psi and a cabin altitude of about 19,000 ft (Figure 15). There was no audible cabin alarm on the video’s audio.

Figure 15: Inflight cockpit indications captured on video footage 27 October 2023

Inflight cockpit indications captured on video footage 27 October 2023

Source: ATSB

The COO stated that, on that occasion, the pressurisation system defect had manifested during climb, but they elected to continue to their cruise altitude of FL280 as they hoped the system would rectify itself after a short time. They stated that they maintained FL280, while using the aircraft’s emergency oxygen system as a supplemental oxygen supply, for a period of about 20 minutes before the pressurisation system ‘probably’ started working again. They also stated that they silenced the cabin altitude alerting system using the inhibit button located near the power levers. The defect was not entered in the aircraft’s maintenance release, but the occurrence was communicated directly to the maintenance provider via text message with the accompanying video (see also Recent maintenance).

The text message sent from the COO to the maintenance provider included the statement:

this was at F280 with a cabin of F200 and diff 2.2, O2 will need a top off please sir [emoji], got the job done

The COO provided line scanning training to the pilot of the accident flight in late September 2023. The COO recalled that they experienced the pressurisation defect during one of these training flights, and in that instance, they stopped at FL160 until the system functioned correctly. They recalled the advice they gave the pilot of the accident flight on the management of the pressurisation system defect was to ‘do what’s sensible and safe’. 

Pilot of the accident flight actions

Documents sourced during the investigation indicated that the pilot of the accident flight had operated VH‑HPY at a cabin altitude that exceeded FL140 on several occasions. The documentation included:

  • An email sent by the pilot of the accident flight on 16 October 2023 to the AGAIR COO stated:

HPY pressurisation stuck on 2.0 differential again for prolonged period.  We needed F280 to complete the trip and thus used a bit of Oxygen.   Pretty normal for HPY as we discussed and the pressurisation has generally been good. Oxy is still good, but we may need to do this profile again on and off.   We have checked with [provider] and he has Oxygen if and when we need it. Is there anything specific re filling Oxygen on HPY that I need to be aware of? Aiming to run it down to below 500 psi and then taxi to [provider] and take it back up to around 1300-1500psi.

On the same day, the AGAIR COO replied to the pilot of the accident flight’s email, stating that they would send the pilot the relevant process from the maintenance manual so that it could be given to the maintenance provider in Toowoomba. The aircraft’s oxygen cylinder was refilled on 18 October 2023 (see Recent maintenance)

  • An operational risk assessment (ORAT) was completed by the pilot of the accident flight on 2 November 2023 for a flight that took place on 16 October 2023. This ORAT likely related to the flight referred to in the email sent by the pilot on 16 October 2023 (see the above dot point). The ORAT stated:

Pressurisation stuck on 2.0 differential for extended period. F280 required for mission completion. Oxygen used. Not abnormal and pressurization returned to regular differential after 3.0 hour. 

The ORAT was a tool used by AGAIR flight and operations crew to assess the risk associated with any assigned flight duty or task. The procedures for the use of the tool stated that ‘flight crew shall use the ORAT for all day-to-day operations’. The ORAT for the flight on 16 October had been assigned a total hazard score of ‘4 – normal operations’ and there was no accompanying safety report submitted (see Safety management system). It had been allocated to the AGAIR head of flying operations (HOFO) for approval. Records indicate the HOFO accessed and approved the ORAT on the evening of 6 November 2023. 

  • An email sent by the pilot of the accident flight on 22 October 2023 to the AGAIR COO, copying in the AGAIR HOFO, included the following statement:

Pressurisation - No change. Same cycles and fixes. The issue is that we are spending most of our time at F280. This means in a 80 hour month (last month), the accumulative effect of high cabin altitudes is a factor. Both myself and [camera operator 1] have had some symptoms during this rotation. This is mitigated by use of Oxygen, lower altitudes when able and the usual fixes of climbing and descending etc. However given the rate of effort and the altitude, the risk of decompression sickness and hypoxia should not be normalised. As we all know if the diff gets stuck at 2.2 then you generally spend around 90 mins at Cabin Alt of 19000 if F280 is mission essential. This can be mitigated operationally if we can’t fix the pressurisation.

  • On the same day, the AGAIR HOFO responded to the pilot of the accident flight’s email stating:

Thanks [name of pilot of the accident flight] for the update. Yes, QFES have definitely embraced the program and are utilising the service well. Many thanks to you and [name of camera operator 1] for keeping it going over the last few weeks. We are getting great feedback and preparing for sustained operations over the summer.

The AGAIR COO did not respond to the pilot of the accident flight’s email.

AGAIR head of flying operations actions

The AGAIR HOFO, who was also the CEO and HAAMC, occasionally flew VH-HPY and had experienced the pressurisation defect for themselves.[28] The HOFO recalled that, in these circumstances, they ceased the climb and flew the aircraft at a lower level. The HOFO had not recorded the defect with the pressurisation system in the aircraft maintenance release following these flights, and they could not recall why they had not done so.

During interview with the ATSB, the HOFO stated that, in the event that the pressurisation system became defective, they had instructed pilots to cease the climb and operate at a safe level. They stated that they were not aware of any pilots that had continued to operate VH-HPY at FL280 with the pressurisation system defective. 

When queried about the email sent by the pilot of the accident flight on 22 October 2023, which detailed the continued operation at FL280 with a cabin altitude of 19,000 ft, the HOFO stated that they had read the pilot of the accident flight’s email as being what ‘would’ happen, rather than what ‘was’ happening. Other than the short email response from the HOFO, where they thanked the pilot and camera operator for ‘keeping it going over the last few weeks’, the HOFO did not contact the pilot to discuss the content of the email. The HOFO explained this was because they were not involving themselves into the operational aspects as they had passed the day-to-day management of the line scanning operation to the AGAIR COO, and that the pilot of the accident flight reported to the COO (see Organisational information). 

Documents sourced during the investigation indicated that the HOFO had attempted to acquire a supplemental oxygen system from a supplier on 22 October 2023. The initial enquiry to the supplier stated:

We are doing high altitude (28,000 ft AGL) operations in our Turbine Commander aircraft where we are spending 4 to 5 hours at this altitude. The aircraft is pressurised but the cabin altitude can be 10,000 feet or more so we are looking for a simple portable system to supplement oxygen for a crew of two. We would like to utilise the existing built in oxygen system in the aircraft and optimise the flow to get maximum time between needing to refill the aircraft bottle. Are you able to help us with this?

On 31 October 2023, the HOFO requested the supplier provide:

one Aerox portable oxygen complete setup – 2 users – E cylinder please. Could you include 6 canulas and one pulse oximeter

The accident occurred before the equipment was supplied. The HOFO subsequently ‘postponed’ the request on 9 November 2023.

Camera operator 1 information

Camera operator 1 had communicated to their family, during casual conversation, that there was an issue with VH-HPY’s pressurisation system that would occasionally manifest. They informed their family that the aircraft had oxygen on board, and they had ‘workarounds’ to deal with the issue.

Historical flight track data

The TrackPlus data for VH-HPY over the period 26 March 2022–2 November 2023 was analysed to identify similar flight profiles to the accident flight. A total of 132 flights took place within this period. Flights with a possible operational requirement were excluded and 8 flights were identified as involving a similar unexplainable descent to a lower flight level for a short period of time before returning to a cruise altitude. The first of these flights took place on 30 September 2023. The pilot of the accident flight was the PIC of 7 of the flights, the COO was the PIC of the eighth flight on 24 October 2023 (Table 5).

Table 5: Previous flight profiles similar to the accident flight were identified from 30 September 2023 to 24 October 2023

DatePilot in commandFlight timeProfile
30 Sep 2023Pilot of the accident flight2 hr 50 min
Flight profile from 30 Sep 2023
15 Oct 2023Pilot of the accident flight4 hr 14 min
Flight profile from 15 Oct 2023
16 Oct 2023Pilot of the accident flight5 hr 27 min
Flight profile from 16 Oct 2023
19 Oct 2023Pilot of the accident flight4 hr 54 min
Flight profile from 19 Oct 2023
20 Oct 2023Pilot of the accident flight4 hr 57 min
Flight profile from 20 Oct 2023
21 Oct 2023Pilot of the accident flight5 hr 30 min
Flight profile from 21 Oct 2023
22 Oct 2023Pilot of the accident flight3 hr 12 min
Flight profile from 22 Oct 2023
24 Oct 2023AGAIR COO4 hr 50 min
Flight profile from 24 Oct 2023

Aerodynamic stalls and spins 

Aerodynamic stalls
Overview

An aerodynamic stall is a rapid decrease in lift and increase in drag caused by the separation of airflow from the wing’s upper surface. A stall occurs when the angle of attack[29] exceeds the wing’s critical angle of attack,[30] resulting in the disruption to the smooth airflow over the wing. 

Accelerated stalls

At the same gross weight, configuration, centre of gravity location, power setting, and environmental conditions, an aircraft will consistently stall at the same airspeed provided the aircraft is at +1 g.  However, the same aircraft will stall at a higher airspeed when subject to an acceleration greater than +1 g. This type of stall is called an ‘accelerated stall’, and they may occur inadvertently during an improperly executed turn or a pullout from a steep dive (US Federal Aviation Administration 2021).

Accelerated stalls tend to be more aggressive than unaccelerated +1 g stalls and may put the aircraft in an unexpected attitude. Failure to execute an immediate recovery may result in a spin or other departure from controlled flight(US Federal Aviation Administration 2021).

Aerodynamic spins
Overview

An aerodynamic spin is a sustained descent in which one or both of an aircraft’s wings are in a stalled condition. During a spin, an aircraft rotates around its vertical axis affected by different lift and drag forces on each wing, descending due to gravity, rolling, yawing, and pitching in a corkscrew path (US Federal Aviation Administration 2021). A spinning aircraft will descend more slowly than one in a vertical or spiral dive and it will have a lower airspeed, which may oscillate. The pitch angle can also vary considerably from significant pitch down to a relatively flat attitude. 

Entry, development and recovery

A spin may be entered intentionally or unintentionally, from any flight attitude if the aircraft has sufficient yaw while at the stall point. An aircraft may yaw for a variety of reasons including incorrect rudder application, adverse yaw created by aileron deflection, engine or propeller effects, and windshear (US Federal Aviation Administration 2021).

Initially the aircraft will enter an incipient spin phase where the aircraft starts rotating, but aerodynamic and inertial forces have not achieved a balance. This phase may take 2–4 turns to develop as the airspeed slows and stabilises (Figure 16). A fully developed spin occurs when the aircraft’s angular rotation rate, airspeed and vertical speed are stabilised in a flight path that is nearly vertical and the spin is in equilibrium (US Federal Aviation Administration 2021).

Recovery from a spin occurs when rotation ceases and the angle of attack of the wings is decreased below the critical angle of attack. To do so, a pilot is required to apply control inputs to disrupt the spin equilibrium (US Federal Aviation Administration 2021). 

Figure 16: Spin development and recovery

Figure 16: Diagram of spin development and recovery

Source: US Federal Aviation Administration (2021)

Gulfstream Commander 695A spin recovery 

The Gulfstream Commander 695A POH prohibited intentional spinning and stated that no spin tests had been conducted. Certification standards for this class of aircraft do not require spin testing to be conducted. However, the POH did contain instructions for recovery should the aircraft inadvertently enter an incipient spin. It stated:

If a spin is entered inadvertently, immediately move control column full forward, apply full rudder opposite to the direction of the spin and reduce power to FLT IDLE. These three actions should be done as near simultaneously as possible. Hold this control position until rotation stops, then neutralize all controls and execute a smooth pullout. Ailerons should be neutral during recovery. Airspeed may reach VMO before full recovery.

Despite this guidance, the relatively large lateral/polar moment of inertia created by the wing‑mounted engines during a fully developed spin would make recovery of the aircraft inherently difficult and possibly improbable.

Telecommunications 

General

All telecommunications made and received by Airservices Australia were recorded. Information related to telecommunications made by other parties was sourced from mobile devices, carrier data and interviews.

Telephone call – pilot and a family member

At 1102, while the aircraft was on climb to FL280, the pilot returned a missed telephone call that they had received from a family member 13 minutes earlier. The AGAIR OM stated that mobile phones could only be used by the pilot during the cruise phase of flight. The return call lasted 3 minutes and 30 seconds. The family member recalled that during the call the pilot sounded focused, happy and logical. Before ending the call, the pilot advised they would call the family member again once they landed. 

Telephone calls – pilot and Airservices Australia personnel

At 1337:46, the Airservices Australia air traffic management director (ATMD) attempted to contact the pilot via mobile phone, however the call went unanswered. At 1338:36, the pilot returned the ATMD’s call, and they had a short conversation that lasted 34 seconds (Table 6). 

Table 6: Transcript from the recording of telephone conversation between the pilot and the ATMD 

Elapsed time (mm:ss)IndividualRecorded audio
00:01ATMD[unintelligible]
00:05ATMDHello [pilot of the accident flight’s name]
00:07Unknown[sound of breathing]
00:10ATMDHello
00:11ATMD[unintelligible]
00:15ATMDHello [pilot of the accident flight’s name] you there
00:20Unknown[sound of breathing]
00:21PilotYeah, I’ve got you. Maintaining FL280. No joy 122.4
00:29ATMD122.1 please, 122.1 please [pilot of the accident flight’s name]
00:34Pilot Roger that, 122.1

Source: Airservices Australia

At 1340:15, the ATMD attempted to call the pilot’s mobile phone again, but the pilot did not answer. The ATMD left a voicemail message stating:

Hi [pilot of the accident flight’s name]. Could you ring air traffic control back again please. [Name of pilot of the accident flight] please ring air traffic control back again on this number. Check your oxygen, oxygen, oxygen, oxygen.

The pilot did not return the ATMD’s call.

Telephone call – Airservices Australia personnel and the AGAIR head of flying operations

At 1350, the ATMD contacted the AGAIR HOFO by phone to advise that ATC had lost contact with VH-HPY, and they suspected the pilot may be suffering from hypoxia (see Appendix B – Transcript – Telephone call between Airservices Australia personnel and the AGAIR head of flying operations).

The conversation lasted nearly 6 minutes during which the ATMD passed the telephone handset to the shift manager (SM), who discussed ATC’s concerns regarding the loss of communications, the pilot’s ‘slow response’ via telephone, the aircraft diverging from track, the ATC ‘oxygen’ calls, and ATC’s instructions for the aircraft to descend. The HOFO was placed on hold for a total duration of 66 seconds. During the conversation ATC regained communication with the pilot and the HOFO was advised that contact had been re-established. The HOFO was also advised that the pilot had confirmed operations were normal and that ATC believed the aircraft was safe.

During the phone conversation, the HOFO advised ATC that the aircraft was on flight tracking, confirmed the level of the aircraft as expected, advised ATC that they believed the flight looked normal, and asked if there were any communication issues in the area. The HOFO did not advise the ATMD or SM that the aircraft had a known intermittent pressurisation defect. The HOFO advised the ATSB that it did not occur to them to pass this information on during the telephone call.  

During interview with the ATSB, the SM stated that their perception of what was going on may have changed had information such as a history of problems with the aircraft pressurisation or about the pilot had been communicated during the telephone conversation.

Speech analysis from the accident flight 

General

As part of the investigation into a Beechcraft King Air 200 accident in 2000, the ATSB obtained expert analysis to determine whether that pilot’s speech and related behaviour was affected by hypoxia (see Related occurrences). A review of research conducted as part of that investigation found that pilots experiencing hypoxia will have a slower speech rate (syllables per second), a slower response time to ATC transmissions, a slowing of the pilot’s coordination of microphone pressing/speaking (in which the pilot allows more ’dead’ time on the radio channel before and after speaking), and slurring of speech. 

There is also a tendency to activate the microphone without speaking, particularly when more adversely affected, and eventually stop responding. Although the fundamental frequency of speech (or pitch) can be an indicator of workload or stress, there is evidence that it tends to remain unchanged in situations involving hypoxia.

During the investigation into the accident involving VH-HPY, the ATSB requested a speech analysis expert, who had previous experience conducting analysis of hypoxia events, conduct an examination of the pilot’s speech and related behaviour during the accident flight to determine if the pilot was affected by hypoxia. The analysis involved comparing the pilot’s communications at lower altitudes against their communications at higher altitudes. 

The analysis used both subjective and computational evaluations of the speech samples. Subjective evaluation provided observations of operational errors, quality and clarity of speech, and the number of syllables spoken. Computational evaluation was used to measure response time to ATC transmissions, the time from the commencement of transmission to the commencement of speech, speaking rate (syllables per second), and fundamental frequency (or pitch).

The speech samples used to perform the analysis consisted of:

  • 5 radio statements made by the pilot at lower altitudes 
    (3 below 10,000 ft on the initial climb and 2 at FL150 after the first descent)[31]
  • 20 radio statements made by the pilot at higher altitudes[32] 
    (4 at FL280 in first cruise, 2 on climb to second cruise and 1 just after establishing the second cruise at FL280, and then 13 from 55 minutes later at FL280 during the second cruise).
Analysis

The analysis found that, compared to when at lower altitudes, at higher altitudes, the pilot:

  • took significantly longer to respond to ATC communication (2.9 seconds compared to 1.1 seconds)[33]
  • spoke at a significantly slower rate (5.9 syllables per second compared to 7.4 syllables per second)[34]
  • took slightly longer to begin speaking after they commenced a transmission (0.59 seconds compared to 0.26 seconds)[35],[36]
  • displayed no change in their average speech fundamental frequency (99.6 Hz compared to 99.8 Hz)
  • made operational errors, especially in their later communications, such as providing a callsign twice, failing to provide a callsign, and referring to an incorrect location
  • spoke unclearly, especially in their later communications, including stuttering toward the end of their communications (which became pronounced in their final communication). 

During the later series of communications (1341:31 to 1401:23), the pilot’s speaking rate became significantly slower (5.1 syllables per second) than their earlier speech at higher altitudes (7.3 syllables per second).[37] The pilot’s final communication displayed the slowest speech of all their communications during the flight (2.81 syllables per second). There was also one occasion when the pilot appeared to unkey and then rekey the microphone when speaking (1359:26) and one occasion when the microphone was keyed but the pilot did not speak (1400:27). 

There appeared to be some improvement in the pilot’s speech while the aircraft spent a short time at FL150 compared to their speech during the initial cruise at FL280, with a more rapid response to the controller, a more rapid response after commencing transmission, a faster speaking rate, and clear and accurate communication. However, only limited samples were available to compare these 2 periods. 

The analysis concluded that the speech samples provide evidence of significant and progressive impairment once the pilot reached FL280, including errors, slowed responses, misarticulations and, eventually, a failure to respond. Overall, the analysis determined that, although the pattern of symptoms could be consistent with a variety of environmental and medical issues, their correlation with altitude strongly indicated impairment by hypoxia.

Air traffic services 

Overview

Airservices Australia was the responsible authority for the provision and administration of civil air traffic services in Australia. The stated objectives of the organisation’s air traffic services, as contained in the Manual of Air Traffic Services,[38] were to: 

a) prevent collisions between aircraft;

b) prevent collisions between aircraft on the manoeuvring area and obstructions on that area;

c) expedite and maintain an orderly flow of air traffic;

d) provide advice and information useful for the safe and efficient conduct of flights; and

e) notify appropriate organisations regarding aircraft in need of search and rescue aid, and assist such organisations as required.

Service types

Airspace in Australia was separated into different classes that were either controlled (class A, class C, class D, and class E) or non-controlled (class G). Different services were offered to aircraft that operated in these airspace classes, based on the flight rules the aircraft was operating under. These services included ATC (en route, approach, and aerodrome), flight information, and alerting. These services were provided by air traffic controllers located at specific aerodromes or 1 of the 2 air traffic control centres located in Melbourne, Victoria and Brisbane, Queensland.

At the time of the accident, the aircraft was operating in class A airspace and received an en route control service from a controller located in the Brisbane ATC centre. 

Airspace

Brisbane Centre was responsible for providing air traffic services to aircraft operating within the Brisbane flight information region (Figure 17). The Brisbane airspace was further divided into smaller volumes of airspace, called regions, with assigned air traffic controllers. 

Figure 17: Flight information regions

Figure 17: Flight information regions

Source: Airservices Australia, annotated by the ATSB

While the aircraft was on climb to its cruise level of FL280, the aircraft transitioned into an area of airspace defined as the ‘Simpson’ region, where it spent the remainder of the flight. The Simpson region covered an area of about 2 million km2 from the ground level to FL285. Its border started about 160 km inland from the east coast of Queensland and included central and north Queensland, parts of the Northern Territory, and sections of the Torres Strait (Figure 18). 

Figure 18: Brisbane flight information region (Simpson region airspace highlighted)

Figure 18: Brisbane flight information region (Simpson region airspace highlighted)

Source: Airservices Australia, annotated by the ATSB

The airspace was ‘dynamic’ and could be divided into smaller sectors, depending on the volume or complexity of aircraft traffic, with a controller assigned to each sector. Within the region, the lower level of class A and class E (controlled) airspace was FL245 and FL125 respectively. 

At the time of the accident, the air traffic activity within the Simpson region was low, and the airspace was ‘fully combined’ meaning the whole of the Simpson region was being controlled by one controller. 

Also present within the Brisbane Centre at the time was a shift manager (SM), who was responsible for the oversight of the Simpson region’s controllers, and the air traffic management director (ATMD), who had overall responsibility for both the Brisbane and Melbourne airspace.

Air traffic control personnel
Simpson region air traffic controller

There were 2 air traffic controllers who managed VH-HPY while it was within the Simpson region airspace:

  • controller 1 had responsibility for the region for 90 minutes and managed most of the loss of communications and hypoxia response
  • controller 2 had responsibility for the region for 15 minutes during the period while controller 1 was in break.

All references to the ‘Simpson region controller’ contained herein refer to controller 1. They joined Airservices in 2012 and had about 9 years experience as an en route controller, all within the Brisbane Centre. 

Shift manager

The SM joined Airservices Australia in 2004. Their experience included about 7 years as an area radar controller, 2 years as an operations manager, and 9 years as a SM.

Air traffic management director

The ATMD’s experience included about 27 years as an en route controller, 3 years as a SM, 2 years as an operations manager, and 1 year as an ATMD. 

Emergency phases

Emergency phases were declared by ATC in instances where there was concern for the safety of an aircraft and its occupants. The procedures for the declaration of emergency phases for aircraft were contained in the Manual of Air Traffic Services and included:

  • An uncertainty phase (INCERFA) which was declared by ATC when uncertainty existed as to the safety of an aircraft and its occupants. The scenarios under which an INCERFA could be declared included a failure of a pilot to report to ATC 30 minutes after being assigned a frequency change.
  • An alert phase (ALERFA) which was declared when apprehension existed as to the safety of an aircraft and its occupants. 

Emergency phases could be upgraded when air traffic control became ‘aware of additional factors that warrant greater apprehension’. This included:

• following an uncertainty phase declared because of failure to report, subsequent communications checks or inquiries to other relevant sources fail to reveal any news of the aircraft; [or]

• information has been received which indicates that the operating efficiency of an aircraft has been impaired to the extent that the safety of the aircraft may be affected.

If an aircraft was subject to an ALERFA declaration and the situation was relieved, but not to the extent that normal operations had been resumed, ATC could downgrade the ALERFA to an INCERFA.

If an aircraft was subject to an emergency phase and had resumed normal operations, or had landed safely, then ATC would cancel the phase and advise relevant units and agencies.

Hypoxic pilot procedures

The procedures to be applied by ATC in the case of specific in-flight emergencies were contained in the Airservices In-Flight Emergency Response (IFER) checklist. This included the actions to take if ATC suspected a pilot was potentially impacted by hypoxia.

The IFER checklist for a suspected hypoxic pilot scenario included the information to be passed to the pilot, the actions to take should escalation be required, and the instructions to issue the pilot to initiate a descent (Figure 19).

Figure 19: Airservices Australia IFER hypoxia checklist

Figure 19: Airservices Australia IFER hypoxia checklist

Source: Airservices Australia

Supplemental procedures associated with all types of in-flight emergencies were also contained within the ‘normal operations resumed’ section of the Airservices Australia IFER Management Abnormal Operations manual. This section stated:

Extensive experience, both in Australia and overseas, shows that crews often try to down-play problems when communicating with [air traffic control]. Furthermore, what may be normal as far as the crew is concerned may still preclude the operational system from operating normally.

This section also stated:

If there is the slightest doubt about the continuing safety of the aircraft, it is prudent to continue with the IFER even if at a low key.

Airservices noted this manual was considered training material and reported that controllers do not use it when they are plugged into the console, rather, they only use the IFER Checklist.

Simpson region controller divided attention

Between 1357:43 and 1401:36, the pilot repeated the clearance from the controller 4 times, and twice requested confirmation that the Simpson controller had copied their clearance readback. During this time the Simpson region controller recalled that a lot of activity took place in the vicinity of their console to do with the previously-held concerns for the aircraft’s safety. This included questions from those located near the console. Additionally, during that 3 minute 53 second period there were 3 transmissions made by 2 other aircraft within the Simpson region. The controller responded to both aircraft without delay.

Organisational information

General

At the time of the accident, AGAIR held an air operator’s certificate issued by CASA on 19 May 2020, valid until 30 November 2023, which authorised ‘charter operations’ (CASR part 135) and ‘aerial work operations’ (CASR part 137 and 138). It also held a CASR part 141 flight training certificate that was valid until 28 February 2025. 

AGAIR operated a mixed fleet of aircraft that comprised 3 Gulfstream 690 and 695, 2 Cessna C525, 9 Air Tractor AT802, a Cessna C337 and a Beech Baron. Its main base of operations was located at Stawell Airport, Victoria. AGAIR also had an aerial application (crop spraying) base located at Hay Airport, New South Wales (NSW).

AGAIR provided aerial application services to south-western NSW. It also had contracts to provide aerial services to fire agencies in Queensland, NSW and Western Australia. AGAIR engaged a mixture of permanently‑employed and seasonal pilots to complete aerial application and aerial fire operations.

Organisational structure

The chief executive officer (CEO) was the sole owner of the organisation. In addition to the CEO role, they also held the CASA‑approved positions of head of flying operations (HOFO) and head of aircraft airworthiness and maintenance control (HAAMC). The CEO worked from the AGAIR base at Stawell Airport. The approved organisational structure was documented in the AGAIR operations manual (OM) (Figure 20). 

Figure 20: AGAIR organisational structure

Figure 20: AGAIR organisational structure

Source: AGAIR

The AGAIR organisational structure depicted all flight crew reporting to the head of training and checking. However, this role was vacant at the time of the accident, as was the head of operations (flight training) position. The CEO stated that the organisation did not have an approved training and checking system, and that they (as HOFO) were undertaking aspects of the role until the organisation received its approval. However, neither the unapproved nature of the training and checking system or the additional training and checking activities undertaken by the HOFO were captured in the AGAIR OM.

The defined responsibilities of the HOFO included:

• The implementation of company policy and ensuring that all company air operations are conducted in full compliance with the Civil Aviation Act 1988, CASRs and CAOs

• Monitoring operational standards, maintaining training and checking records and supervising the training and checking of flight crew

• The allocation of aircraft appropriate to the planned task

The AGAIR OM also stated that the HOFO ‘in exercising any responsibility may delegate to other members of the company certain duties’. The CEO/HOFO stated that they had passed operational control of the line scanning activities to the chief operating officer (COO). This included flight crew reporting, and that the pilot of the accident flight reported to the COO at the time of the accident. This was not reflected in the approved organisational structure, and the AGAIR OM did not contain defined responsibilities for the COO role. 

During interview, the COO confirmed their role included the oversight of the line scanning operations in VH-HPY, which involved overseeing the installation and testing of the camera equipment, mission planning, and client management. 

Safety management system

Introduction

CASA defined a safety management system (SMS) as:

…a systematic approach based on managing risk through setting goals, capturing data, measuring performance and system refinement for managing safety risks. An SMS is woven into the fabric of an organisation that enables effective risk based decision-making processes across the business where risks are identified and continuously managed to an acceptable level.

At the time of the accident, AGAIR was required to have submitted an SMS implementation plan to CASA, but it was not required by aviation legislation to have an approved SMS or safety manager (see SMS implementation). 

Outsourced safety management function

At the time of the accident, AGAIR outsourced its safety management functions to an entity named AVIARC. It provided AGAIR with a nominated safety manager and oversaw the development, implementation and ongoing management of the SMS. This contractual arrangement commenced in mid-2021. 

The nominated safety manager was located at the AVIARC office in Red Hill, Queensland. They attended the AGAIR Stawell and Hay bases about 2 times a year, with most of the safety management work undertaken remotely. An online database, which was accessible by AGAIR and AVIARC personnel, was used for occurrence reporting and the ongoing management of safety functions.

SMS implementation

On 25 November 2022, AVIARC, on behalf of AGAIR, submitted a nomination for a safety manager, safety management manual (SMM) (issue 1 revision 1 dated November 2022), and SMS implementation plan to CASA. At the time of the accident, neither the SMM nor the nomination for safety manager had been assessed by CASA. CASA stated that no assessment had taken place as neither were required to have been submitted. Additionally, AGAIR had not specifically applied to be an early SMS adopter or completed the appropriate application submission for the approval of the safety manager.

The implementation plan submitted to CASA outlined the phased implementation of the SMS. In the supporting letter to CASA, the nominated safety manager stated that:

the Agair Safety Management System is ‘Present’ and ‘Suitable’ in every aspect, and also ‘Operational’ and ‘Effective’ in many others. 

The AGAIR SMS implementation plan did not contain specific timeframes for the implementation of each phase other than to state:

the entire plan may take several years to reach full implementation.

The most recent revision to the AGAIR safety management system took place in June 2023 (SMM issue 4 revision 1), and this version was implemented at the time of the accident. 

System effectiveness
Overview

The ATSB reviewed the AGAIR SMS as implemented at the time of the accident. This involved the review of safety data recorded over the period 2019–2023. Although it was found that AGAIR did have the basic elements necessary to capture and manage operational hazards at the time of the accident, many of these elements were partially implemented, did not meet current defined safety objectives, or contained deficiencies that may have impacted system efficacy. 

The nominated safety manager stated that they were unaware of the intermittent pressurisation defect with VH-HPY, or the practice of operating the aircraft at a hazardous cabin altitude. The AGAIR CEO/HOFO confirmed that they had not raised the pressurisation issue with the safety manager either directly or during the various safety management meetings.

Safety management meetings

The AGAIR SMS had 4 levels of safety meetings:

  • executive safety review meetings
  • safety action group meetings
  • base safety meetings in both Stawell Airport and Hay Airport locations
  • CEO touchpoint meetings.

In the 3 years prior to the accident, AGAIR had conducted 14 safety action group meetings, 14 base safety meetings and 8 CEO touchpoint meetings. The minutes from these meetings did not contain any reference to the pressurisation issue involving VH-HPY or the continued risk of operating the aircraft at a hazardous cabin altitude. No executive safety review meetings had taken place. The AGAIR safety manager advised the ATSB that the content of the executive safety review was captured by the CEO touchpoint meetings.

Hazard and occurrence reporting

Interviews with AGAIR personnel and emails sourced during the investigation indicate that at least 8 current or previous AGAIR personnel had awareness of a pressurisation issue with VH-HPY over a period ranging from 1 month to greater than 2 years prior to the accident. Additionally, at least 4 current AGAIR personnel had awareness of the practice of operating the aircraft with an excessive cabin altitude over a period ranging from 1 month to greater than 12 months prior to the accident.

In the 5 years prior to the accident, a total of 62 reports had been submitted into the AGAIR reporting system. Thirty-four of these were work health safety (WHS) or non-operational reports including injuries and infrastructure issues. A total of 28 of the submitted reports related to aviation safety matters including wildlife and airspace issues (Figure 21). There were no instances of either the pressurisation issue or the continued operation of the aircraft with that defect raised within the system. 

Figure 21: AGAIR hazard and occurrence reporting data from years 2019 to 2023

Figure 21: AGAIR hazard and occurrence reporting data from years 2019 to 2023

Source: ATSB

The reporting target defined within the AGAIR SMM at the time of the accident was 24 reports per year. However, it was unclear if this target was to also include non-operational reports. Regardless of the composition, this reporting target had not been achieved. A review of CEO touchpoint meeting minutes found that the 2 meetings conducted prior to the accident in September 2023 and October 2023 both referenced a low reporting rate. Other than stating the ‘CEO will encourage pilots to report on issues via usage of the ORAT’ it was unclear what, if any, action had been taken to improve reporting following these meetings. The safety manager had promulgated 4 messages to AGAIR personnel regarding reporting during the period October 2022 to September 2023, but these predated the 2 CEO touchpoint meetings.

During interview with the ATSB, the CEO/HOFO recalled that they always encouraged personnel to submit issues into the safety management system. They also stated that they had not entered the intermittent pressurisation defect into the SMS themselves, nor had they given thought about doing so. During interview with the ATSB, the safety manager stated that both the intermittent defect and the continued operation of the aircraft should have been reported into the SMS.

Hazard register

AGAIR had a hazard register that contained 268 identified hazards across the various activities conducted by the organisation. There were no instances of either the pressurisation issue or the continued operation of the aircraft with such a defect raised within the register. There was also no reference to the operation of pressurised aircraft or line scanning operations within the register.

Internal audits

AGAIR had conducted 19 internal audits in the 5 years prior to the accident. This was composed of 9 WHS or non-operational audits and 10 operational audits. Ninety per cent of the completed audits resulted in no findings and there were no instances of either the pressurisation issue or the continued operation of the aircraft having been identified. No audit of the line scanning operation had been conducted. 

A review of the internal audits by the ATSB found that most of the operational audits were completed by the department owner, for example aircraft fleet audits conducted by the HOFO and HAAMC, in contradiction to the documented procedures contained within the AGAIR SMM current at the time that stated:

the AGAIR SMS audit processes are conducted by persons and departments independent of the functions being audited. … For Internal audits, where an independent auditor is not available, AGAIR can retain the services of a third-party auditor. 

The SMM also stated:

AGAIR uses ‘normal operations’ monitoring methods, to gather hazard information from the normal daily routine workflow. This may include Line Operations Safety Auditing (LOSA), and/or Normal Operations Safety Surveys (NOSS) conducted by the ASM [safety manager] or delegate, on a randomly continuous basis as opportunity arises during the normal course of business.

No LOSA or NOSS had been conducted in the 5 years prior to the accident. 

Management of change

The AGAIR safety management manual current at the time contained procedures for the management of change and stated ‘AGAIR adheres to a policy of systematic change management’. The triggers for the initiation of the change management process included:

• addition of new aircraft type, or more of the same aircraft type

• introduction of new equipment and/or operational procedures

• organisational restructure

• new types of operation

• changes to key personnel

• restructure of operational departments

• acquisition of equipment

• change in customer base.

In the 5 years prior to the accident, no change management activities had been documented. 

Training and education

SMS training was recorded as current for all involved AGAIR personnel at the time of the accident.

Regulatory oversight

Civil Aviation Safety Authority 
Overview

CASA was responsible, under the provisions of Section 9 of the Civil Aviation Act 1988, for the safety regulation of civil air operations in Australia and of Australian aircraft outside of Australia. This included issuing certificates, licences, registrations and permits, and conducting comprehensive aviation industry surveillance. 

The primary means CASA used to oversight authorisation holders[39] were:

  • regulatory service activities (for example, assessing applications for the issue or variation to an authorisation holder’s approvals)
  • surveillance events.
Surveillance events

CASA undertook surveillance of an authorisation holder to assess the safety performance and compliance with regulatory requirements. This surveillance could be initiated:

  • based on a planned schedule
  • in response to outside events such as accidents or complaints
  • by a regulatory service task
  • as part of a national campaign focused on a particular industry sector. 

There were 2 levels of surveillance undertaken by CASA. A level 1 event was usually structured to assess an authorisation holder’s system capabilities. These were large surveillance activities that often took place over several days and involved a multi-disciplinary team. A level 2 event was a less formal activity that was usually shorter in duration and was often focused on the verification of a process in practice. Both levels of surveillance could be conducted onsite or by desktop assessment.

Surveillance events were scoped to assess defined areas of an authorisation holder’s approved activities. Determining the scope of surveillance events incorporated elements of judgment by CASA staff in assessing risk and was informed by a range of information including previous surveillance events, and other safety data related to an authorisation holder. The effectiveness of the associated process(es) would then be assessed using a variety of techniques including process sampling. The limitations of process sampling included that a deficiency could exist within an area outside the defined scope of a surveillance event, that a process might not be sampled to the breadth or depth needed to uncover an issue, or that a process containing an issue might not be sampled at all.

At the conclusion of a surveillance event, CASA would issue a report and any identified findings to the authorisation holder. These findings were classified as:

  • safety alerts – used to raise an immediate safety concern regarding a serious breach
  • safety findings – used for the purposes of identifying a breach of a legislative provision or a provision of the authorisation holder’s written procedures
  • aircraft survey reports – used to provide the registered operator of an aircraft with notice of a potential or actual aircraft defect
  • safety observations – used to identify latent conditions resulting in system deficiencies that, while not constituting a legislative or procedural breach, have the potential to result in such a breach if not addressed, or potential areas for improvement in safety performance.

An authorisation holder was required to respond to all findings except for safety observations. If issues identified in a finding were not addressed, the authorisation holder could be subject to regulatory enforcement action, which involved CASA exercising specific legislative powers to alter the legal rights or obligations of the authorisation holder. 

Authorisation holder performance indicator 

The authorisation holder performance indicator (AHPI) tool was an assessment of an authorisation holder completed periodically by CASA. The tool was used until June 2022. The questionnaire covered factors associated with an authorisation holder’s management, organisation, operations, and regulatory history. An overall value was then given, which resulted in the authorisation holder being assigned to either category 1 (higher level surveillance focus required) or category 2 (normal surveillance level appropriate).

AGAIR pre-accident regulatory services

Regulatory service activities of note provided to AGAIR between November 2018–November 2023 included:

  • variation to the system of maintenance for VH-HPY (2019)
  • renewal of the air operator’s certificate (2020)
  • initial issue of a CASR part 141 flight training certificate (2020)
  • renewal of the CASR part 141 flight training certificate (2022)
  • voluntary suspension of the CASR part 141 flight training certificate (2023).
AGAIR pre-accident surveillance 2018–2023  
Overview

There were 6 AHPI assessments undertaken on AGAIR during 2018‍–‍2022. All assessments resulted in AGAIR being assigned with category 2 (normal level of surveillance appropriate). 

During November 2018–November 2023, AGAIR was also subject to 6 authorisation holder surveillance events (Table 7). This was composed of one level 1 event and 5 level 2 events that included surveillance associated with the variation to the manufacturer’s maintenance schedule for VH‑HPY (January 2019), renewal of the air operator’s certificate (April 2020), and regulatory service tasks. AGAIR had not been subject to any regulatory enforcement action in the 5 years prior to the accident. Further details on 2 surveillance events of note during that period, events 18876 and 18981, are provided in the following sections. 

Table 7: AGAIR surveillance events

Event No.DateLevelSite visitArea covered
18876January 2019Level 2 NoVariation to the manufacturer’s maintenance schedule
18981May 2019Level 2 YesPilot duty times and airworthiness
19501April 2020Level 2 NoAOC renewal
23298February 2021Level 2 NoAircraft proximity event during fire suppression activities
25581October 2021Level 2 YesFirefighting operations
23888June 2022Level 1 YesPart 141 flight training
Surveillance event 18876 (January 2019)

In January 2019, AGAIR applied to CASA for a one-off approval to vary the validity period for the maintenance release inspection for VH-HPY from 165 hours to 180 hours. At the time of the application, the aircraft had accumulated 6,521.2 hours, with the maintenance release valid for 150 flight hours (up to 6,512.9 hours). However, the maintenance schedule also permitted a non‑cumulative planning tolerance of an additional 15 hours (up to 6,527.9 hours). CASA subsequently granted AGAIR’s request. 

Subsequent CASA review of the maintenance release identified that VH‑HPY had operated 8.3 hours beyond the 150-hour validity period of the maintenance release at the time of the application to CASA and a safety finding was raised. However, CASA acknowledged that the aircraft was still within the 15-hour planning tolerance published in the manufacturer’s maintenance schedule.

AGAIR responded to the safety finding, stating that the organisation had misinterpreted the allowable 15 hour ‘grace’ period within the system of maintenance which required a logbook statement and the maintenance release show the actual expiry time of 165 hours rather than 150 hours. An amended logbook statement for VH‑HPY was provided to CASA in May 2019 and the finding was acquitted by CASA in October 2019.

Surveillance event 18981 (May 2019)

In February 2019, CASA received correspondence from the New South Wales (NSW) Rural Fire Service (RFS)[40] that contained concerns raised by an AGAIR pilot. The concerns raised by the pilot included: 

  • ‘numerous ongoing maintenance issues’ with 2 aircraft used by AGAIR,[41] VH‑LVG (an Rockwell Commander 690A) and VH‑CLT (a Rockwell Commander 690B)[42]
  • senior AGAIR personnel providing conflicting advice to pilots on the continuation of operations with aircraft defects that (according to the reporting pilot) impacted the safety of operations ‘on a daily basis’
  • deferring the rectification of aircraft defects that impacted the safety of operations
  • non-compliant flight and duty rostering practices affecting pilot fatigue. 

The concerns raised by the pilot did not contain any information on specific defects, other than reference to an issue with the air conditioning system of VH-LVG, which the pilot indicated had resulted in a very hot and fatiguing cockpit environment and resulting in tablets used as electronic flight bags (EFBs) entering thermal shutdown. 

In response to the raised concerns, CASA initiated an onsite level 2 surveillance event that took place in May 2019. The surveillance was scoped to assess airworthiness control, crew scheduling and authorised activities. The surveillance team was composed of a flying operations inspector (FOI) and an airworthiness inspector (AWI). The surveillance event was conducted over a single day at AGAIR’s Stawell Airport facility and, according to the surveillance report and subsequent interviews with the involved AWI, the event involved:

  • interviews with the CEO (chief pilot and HAAMC) and a senior pilot
  • a review of flight and duty time records, AGAIR operations manual, and the current maintenance release for VH-LVG[43]
  • a non-intrusive, visual inspection of VH-LVG, and an Air Tractor.

The surveillance report, issued to AGAIR, stated:

The aircraft maintenance release for VH-LVG, Rockwell Turbo Commander 690B was reviewed and found to have no defects noted from operating pilots regarding any safety of flight issues. The release appeared to be managed correctly.

As a result of the surveillance, CASA issued AGAIR one safety finding and 3 observations (Table 8). The finding related to flight and duty rest requirements, which was one of the issues the pilot had raised with the NSW RFS.

Table 8: Surveillance event 18981 findings

CASA No.Finding typeTitleOverview
721910Safety findingPilot flight and duty timesThe senior pilot was found to have exceeded flight and duty rest requirements
817396Safety observationOperational improvementsRecommendation to implement a Civil Aviation Safety Regulation (CASR) part 141, and to incorporate the organisation’s safety management system into the operations manual
817421Safety observationCross hire agreementSuggested recommendations to improve cross hire contractual agreements[44]
817425Safety observationSupplier engagementSuggestion to develop a process that captured quality assurance activities conducted on maintenance suppliers

The ATSB reviewed the surveillance file and interviewed the AWI who undertook the May 2019 surveillance activity. The surveillance file contained limited information about the planning and actual conduct of the surveillance, and the FOI involved was no longer working for CASA and was not interviewed. 

The AWI recalled that they had not themselves been in contact with the reporting pilot, and was unsure whether others at CASA had done so. There were no records on the surveillance file to indicate whether CASA contacted the pilot who wrote to the NSW RFS to assist in the planning for the event. However, usual practice was for CASA to make contact before any surveillance event was approved, so such a record may not have been stored in the surveillance file. The ATSB was unable to contact this pilot.

The AWI recalled that it was generally the approach that when conducting surveillance activities of authorisation holders that were involved in firefighting activities, the events were scheduled outside of the peak fire season to minimise the operational impacts to the holder from these activities. 

At the time of the surveillance event, the AWI recalled that they had no previous interactions with AGAIR or GAM. Further, the AWI recalled that CASA’s approach to the surveillance was to determine if there was validity to the pilot’s complaint. The AWI advised that both aircraft inspected were in good condition. The historical (expired) maintenance releases and the aircraft logbooks were located at the aircraft’s maintenance provider (GAM) facility at Essendon Airport, Victoria, and were not reviewed. The AWI recalled that there was no evidence from their visit to suggest that there was activity going on that was not being documented, and nothing to indicate additional surveillance was necessary. 

The ATSB was unable to determine if the safety finding related to pilot flight and duty times had been acquitted based on the available records.

ATSB review of VH-LVG maintenance records

The ATSB undertook a review of the maintenance records for VH-LVG from December 2014–April 2023. This included a crosscheck of the information contained within historical maintenance releases and the information contained within the aircraft airframe, engine, and propeller logbooks.

The maintenance release current at the time the AGAIR pilot raised their concerns, very likely the same maintenance release reviewed by the AWI during the surveillance event, contained 2 annotated items within the defects section. Both had been entered by a licenced aircraft maintenance engineer (LAME) on 11 February 2019:

  • ‘TRAFFIC PROCESSOR REQ SERVICE’
  • ‘RUDDER TRIM IND FLICKERING’. 

These defects had been rectified during unscheduled maintenance endorsed on 15 and 27 February 2019. 

Of the 7 maintenance releases that were valid from December 2014 to May 2019, 5 had no defect entries. Further ATSB examination identified about 10 entries of unscheduled work recorded in the airframe logbook with the characteristics of defects that could have appeared during operations and been identifiable by pilots. It was not determined whether these defects had been knowingly deferred.

This work was carried out during scheduled 150-hourly checks. Most of these defects were minor with the exception of one entry that related to the right engine oil pressure indicating system. 

AGAIR post-accident surveillance 

In response to the accident involving VH-HPY, CASA conducted a level 2 surveillance event (number 28544) of AGAIR in January 2024 at Avalon Airport, Stawell Airport, and Essendon Airport, Victoria. The surveillance was scoped to assess airworthiness assurance and airworthiness control, crew scheduling and authorised activities, and it was completed over 3 days. Personnel from one of AGAIR’s maintenance providers, GAM, were also interviewed as part of the surveillance event. The surveillance team was composed of 2 AWIs. One safety alert, 5 safety findings and 2 safety observations were issued to AGAIR (Table 9).  

The primary issue identified by CASA was AGAIR operating its Gulfstream 690 and 695 aircraft (VH-HPY, VH-LVG and VH-LMC) with known defects not recorded on the maintenance release and operating these aircraft with scheduled maintenance overdue. 

CASA reported that the related findings were primarily supported by evidence from crosschecking the maintenance releases and aircraft logbook certifications. Additional supporting information also included personnel interviews and an internal GAM email record from March 2023 listing numerous defects provided to them by an AGAIR pilot. CASA did not conduct a review of the entire history of each aircraft, but issues were identified for VH-LVG and VH-LMC between the years 2022 and 2023. A more in-depth review was conducted on VH-HPY since it was involved in the accident, and this review identified issues that existed between the years 2018 and 2023. 

AGAIR provided CASA with responses to the safety alert and safety findings. These responses were under assessment at the time of publication.

Table 9: Surveillance event 28544 findings

CASA No.Finding typeTitleOverview
732015Safety alertNon-recording of aircraft defectsAGAIR were operating their Gulfstream 690 and Gulfstream 695 aircraft with known defects not recorded on the maintenance release. CASA required AGAIR to have these aircraft inspected by an approved maintenance organisation before further flight 
732082Safety findingAircraft registered operator and cross-hire agreementsAGAIR were not the registered operator of 7 aircraft used by the organisation and there were no cross-hire agreements in place
732083Safety findingNon recording of defects on the aircraft maintenance releaseAircraft logbooks contained defects that were not recorded on the aircraft maintenance release
732084Safety findingOperating an aircraft with scheduled maintenance required on the maintenance release part 1AGAIR operated aircraft with maintenance due on part 1 of the maintenance release
732085Safety findingOperating aircraft with non-permissible defects on the maintenance releaseAGAIR operated an aircraft with a non-permissible defect on the maintenance release
732086Safety findingPilot maintenanceAGAIR pilots were found to have conducted unauthorised aircraft maintenance 
828000Safety observationControl of minimum equipment listsAGAIR were not permitted to use a minimum equipment list issued to AGAIR logistics
827999Safety observationCompliance with engineering ordersAGAIR operated VH-HPY while the engineering order for the TK-7 camera was not approved
GAM pre-accident surveillance 2018–2023

There were 3 AHPI assessments undertaken on GAM between 2018 and 2022. All assessments resulted in GAM being assigned with category 2 (normal level of surveillance appropriate). 

Between November 2018–November 2023, GAM was subject to one surveillance event that was conducted in May 2023. The CASA surveillance team was composed of 2 AWIs and one safety systems inspector. The event was conducted onsite at GAM’s Essendon Airport facility over 2 days. Three safety observations were issued to GAM related to non-destructive testing and safety assurance improvements. 

GAM post-accident surveillance 

Following the post-accident surveillance of AGAIR, CASA conducted a level 2 surveillance event (number 28605) of GAM onsite at its Essendon Airport facility over 2 days in April 2024. The surveillance team was composed of 2 AWIs, and the scope included approved maintenance organisation operations, data and documents, and maintenance activity. Six safety findings and 2 observations were raised as a result (Table 10). 

The primary issue that CASA identified was that GAM had not appropriately managed the conduct of aircraft modifications on 2 Gulfstream 695A aircraft. This included the installation of the TK-7 camera system on VH-HPY.

GAM provided CASA with responses to the safety findings. These responses were under assessment at the time of publication. 

Table 10: Surveillance event 28605 findings

CASA No.Finding typeTitleOverview

732426

 

Safety finding

 

Certification for aircraft maintenance to be made in the aircraft logbook in accordance with the aircraft log book instructions & CASA Schedule 6Some certifications were not placed or recorded in aircraft logbooks

732427

 

Safety findingAircraft maintenance to be carried out in accordance with approved dataSome modifications were undertaken to aircraft (including VH-HPY) that were released to service prior to the approval of the engineering order 

732428

 

Safety findingCertification of maintenance in accordance with system of certificationSome modifications were undertaken to aircraft (including VH-HPY) without raising a worksheet package or meeting certification requirements
732429Safety findingCo-ordination of maintenance A modification to VH-HPY was certified by a licenced aircraft maintenance engineer who was not authorised to certify for all the maintenance undertaken

732430

 

Safety findingManagement and compliance with engineering ordersSeveral aircraft (including VH-HPY) were released to service with maintenance due

732431

 

Safety findingAircraft returned to service without certification for maintenanceTwo aircraft (including VH-HPY) were released to service with uncertified maintenance or maintenance required

828315

 

Safety observation

 

Reviewing legislative maintenance requirementsGAM certified for maintenance tasks which were not applicable to the aircraft under legislation

828316

 

Safety observationAircraft modification instructions for continued airworthinessEngineering order instructions for continued airworthiness had not been complied with (including VH-HPY)

Related occurrences

The ATSB occurrence database contained 6 other serious incidents and accidents that were investigated involving pilot incapacitation due to altitude hypoxia.

Pilot incapacitation involving Raytheon Aircraft Super King Air 200, VH‑OYA, 72 km east of Edinburgh Airport, South Australia, on 21 June 1999 (ATSB investigation 199902928)

On 21 June 1999, a Raytheon Aircraft Super King Air 200, VH-OYA, departed Edinburgh, South Australia for Oakey, Queensland with 1 pilot and 2 passengers. One of the 2 passengers, who was also a pilot but not qualified to operate the aircraft type, occupied the co-pilot seat. The other passenger was seated in the cabin. All 3 occupants were serving RAAF personnel.

As the aircraft reached the cruise level of FL250, the controller contacted the pilot, indicating that the aircraft was not maintaining the assigned track. The pilot acknowledged this transmission. A short time later the passenger in the co-pilot seat noticed that the pilot was repeatedly performing the same task to do with GPS programming. The controller advised the pilot again that the aircraft was still off track, however the pilot did not reply to this transmission. Shortly after this, the pilot lost consciousness. The passenger in the co-pilot seat took control of the aircraft and commenced an emergency descent. The other passenger then unstowed the pilot's oxygen mask and took several breaths of oxygen from it before fitting it to the unconscious pilot. Neither passenger donned an oxygen mask during the incident. The pilot recovered consciousness during the descent, and once they had regained situation awareness, resumed control of the aircraft and carried out an uneventful landing.

The investigation concluded that both bleed air switches were inadvertently selected to ENVIR OFF during the climb. It was also found that the cockpit warning system did not adequately alert the pilot to the cabin depressurisation, and the oxygen mask deployment doors were incorrectly orientated during installation so that the masks would not automatically deploy when required. The ATSB also identified that hypobaric training did not provide an effective defence to ensure that the pilot or passengers would identify the onset of hypoxia.

Pilot and passenger incapacitation involving Beech Super King Air 200, VH‑SKC, Wernadinga Station, Queensland, on 4 September 2000 (ATSB investigation 200003771)

On 4 September 2000, a Beech Super King Air 200 aircraft, VH-SKC, departed Perth, Western Australia on a charter flight to Leonora with 1 pilot and 7 passengers on board. Shortly after the aircraft had climbed through its assigned altitude, the pilot’s speech became significantly impaired and they appeared unable to respond to ATC instructions. Open microphone transmissions over the next 8 minutes revealed the progressive deterioration of the pilot towards unconsciousness and the absence of any sounds of passenger activity in the aircraft. No human response of any kind was detected for the remainder of the flight. Five hours after taking off from Perth, the aircraft impacted terrain and was destroyed. There were no survivors.

The investigation concluded that the incapacitation was probably a result of altitude hypoxia due to the aircraft being fully or partially unpressurised and the occupants not receiving supplemental oxygen. Due to the extensive nature of the damage to the aircraft caused by the impact with the ground, and because no recording systems were installed in the aircraft (nor were they required to be), the investigation could not determine the reason for the aircraft being unpressurised, or why the pilot and passengers did not receive supplemental oxygen.

Uncontrolled flight into water involving Cessna 208B, VH-FAY 260 km north-east of Narita International Airport, Japan, on 27 September 2018 (ATSB investigation AO-2018-065)

The pilot of a Cessna 208B aircraft, registered VH-FAY, was contracted by the aircraft operator to ferry VH-FAY from Jandakot Airport, Western Australia to Mississippi, United States. On the morning of 27 September 2018 local time, the aircraft departed Saipan International Airport, Northern Mariana Islands, for a planned flight to New Chitose Airport, Hokkaido, Japan. After climbing for about an hour, the aircraft levelled off at FL220. 

After 2 hours 20 minutes flight time, the pilot contacted Tokyo radio flight information service at the first mandatory reporting position. The aircraft passed the next reporting point at the same altitude, 1 hour 20 minutes later, but the pilot did not contact Tokyo radio as expected. Tokyo radio made repeated attempts to communicate with the pilot, without success. Having received no communications from the pilot for 4.5 hours, 2 Japan Air Self-Defense Force aircraft intercepted VH-FAY. The pilot did not manoeuvre the aircraft in response, in accordance with international intercept protocols. 

After about 30 minutes, the Japan Air Self-Defense Force pilots observed VH-FAY descend into cloud. The aircraft descended rapidly and disappeared from radar less than 2 minutes later. Within 2 hours, search and rescue personnel located the aircraft’s rear passenger door. No other aircraft wreckage was located and the pilot was not found.

The ATSB found that while the aircraft was in the cruise on autopilot, the pilot almost certainly became incapacitated and did not recover. About 5 hours after the last position report, without pilot intervention to select fuel tanks, the aircraft’s engine stopped, likely due to fuel starvation. This resulted in the aircraft entering an uncontrolled descent into the ocean. The cause of incapacitation could not be determined. While a medical event could not be ruled out, the pilot was operating alone in an unpressurised aircraft at 22,000 ft and probably using an unsuitable oxygen system, which increased the risk of hypoxia.

Depressurisation event involving a Metro 3, VH-SEF, 93 km south-south-east of Narrabri Airport, New South Wales, on 23 September 2012 (ATSB investigation AO-2012-127)

On the evening of 23 September 2012, a Metro 3 aircraft, VH-SEF, departed Narrabri, New South Wales on a scheduled passenger flight to Sydney with 2 pilots and 7 passengers. During the climb, the captain began to feel unwell and their symptoms worsened as the climb progressed. The captain used the aircraft’s oxygen supply and noted that their symptoms started to improve. The captain requested the first officer check the cabin altitude, but before they could respond, the cabin altitude warning light illuminated at a cabin altitude of 17,000 ft. An emergency descent to 10,000 ft was subsequently performed.

The flight crew later found that the aircraft’s pressurisation system would not pressurise the cabin in automatic mode, and manual mode resulted in an erratic cabin altitude. Once the aircraft had landed, the pressurisation system was tested with no fault found. The cabin altitude warning switch was found to be out of tolerance and replaced. At the time of the incident, there was no routine maintenance regime for the cabin altitude warning system.

Flight crew incapacitation involving a Reims F406, VH-EYQ, near Emerald Airport, Queensland, on 1 August 2014 (ATSB investigation AO-2014-134)

On the morning of 1 August 2014, a Reims Aviation F406 aircraft, VH-EYQ, departed Emerald, Queensland, on an aerial survey task with a pilot and navigator on board. The aircraft was fitted with an oxygen system to allow unpressurised operations above 10,000 ft. 

During the climb, the pilot turned on the aircraft oxygen supply, and then connected and donned their oxygen mask. The pilot then monitored their blood oxygen saturation level on an oxygen pulse meter as the aircraft continued to climb. During the climb to FL245, at a level of about FL180, the pilot noticed that their blood oxygen saturation level had fallen significantly.

The pilot attempted to increase the amount of oxygen they were receiving, while continuing to climb, by adjusting their oxygen system controller. During this period, the pilot’s accuracy when controlling the aircraft deteriorated and their speech became slurred. The navigator encouraged the pilot to maintain control and descend, and ATC prompted the pilot to ensure they were receiving an adequate supply of oxygen. The pilot eventually identified that their oxygen fitting had disconnected. The fitting was reconnected by the pilot, after which the pilot made a controlled descent before landing at Emerald.

Pilot incapacitation involving Cessna 208B, VH-DQP, near Brisbane Airport, Queensland, on 2 July 2020 (ATSB investigation AO-2020-032)

On the afternoon of 2 July 2020, the pilot of a Cessna 208B aircraft, VH-DQP, was conducting a ferry flight from Cairns, Queensland to Redcliffe. After encountering unforecast icing conditions and poor visibility due to cloud, the pilot climbed from 10,000 ft to 11,000 ft. Later, ATC attempted to contact the pilot regarding the descent into Redcliffe but no response was received from the pilot at that time, or for the next 40 minutes. During this time, ATC, with the assistance of pilots from nearby aircraft, made further attempts to contact the pilot. When the aircraft was about 111 km south-south-east of the intended destination, communications were re-established. The pilot was instructed by ATC to land at Gold Coast Airport. The pilot tracked to the Gold Coast and landed.

The ATSB found that the pilot was likely experiencing a level of fatigue due to inadequate sleep the night before, and leading up to the incident, and consequently fell asleep during the flight. Further, operating at 11,000 ft with intermittent use of supplemental oxygen likely resulted in the pilot experiencing mild hypoxia. This likely exacerbated the pilot’s existing fatigue and contributed to the pilot falling asleep.

Safety analysis

Introduction 

On the morning of 4 November 2023, a Gulfstream 695A, registered VHHPY, was tasked to conduct line scanning of fire zones north of Mount Isa, Queensland. On board the aircraft were the pilot and 2 camera operators. 

About 1 hour and 50 minutes into the flight, while the aircraft was in cruise at flight level (FL) 280, air traffic control (ATC) radio contact with the pilot was lost. ATC made multiple attempts to contact the pilot, leading ATC to declare an uncertainty phase for the aircraft. Following a brief telephone conversation with the pilot, where the pilot’s speech was detected to be ‘slow’ and ‘delayed’, ATC upgraded the status to an alert phase and initiated their hypoxia emergency procedures.

About 10 minutes later, radio contact with the pilot was re-established via the crew of a Royal Australian Air Force aircraft, then directly with ATC. The alert phase was downgraded to an uncertainty phase and, a short time later, ATC cancelled the uncertainty phase.

The pilot confirmed with ATC that their oxygen system was operating normally, and they were subsequently issued a clearance to undertake line scanning north of Mount Isa. The pilot made a final radio transmission at 1401:23. Commencing at 1419:19, ATC attempted to repeatedly contact the pilot, but they did not respond to any further radio calls.

At 1426 the aircraft entered a descending anticlockwise turn with an increasing rate of descent. At an altitude of about 10,500 ft, the aircraft likely transitioned into an aerodynamic spin, with a subsequent average rate of descent of about 13,500 ft/min. The aircraft collided with terrain at about 1427, with the wreckage located 55 km south-east of Cloncurry Airport. The 3 occupants were fatally injured, and the aircraft was destroyed by impact forces and a fuel-fed post-impact fire.

This analysis first examines pilot impairment and the accident sequence, and then discusses the maintenance, organisational, air traffic control and regulatory oversight aspects involved.

Altitude hypoxia

The pilot’s speech, as captured by ATC recordings, demonstrated significant and progressive impairment while the aircraft was operating at about FL280. This included errors, slowed responses, misarticulations, and eventually a failure to respond to radio calls.

The pilot’s medical history and the post-mortem examination contained no indications of a pre‑existing medical condition that could have resulted in their impairment. Additionally, camera operator 1 held a commercial pilot licence, with experience flying twin-engine aircraft, and they would likely have been able to operate the aircraft had the pilot experienced a medical event. 

The content of the pilot’s radio transmissions at FL280 were consistent with altitude hypoxia. The vocal symptoms exhibited by the pilot varied significantly with altitude, noticeably improving when the aircraft descended to FL150, then worsening again when the aircraft returned to FL280. These symptoms progressively worsened when the flight was continued at FL280. The pilot’s final radio transmission included an incorrect location reference, stuttering, and the slowest speaking rate of all transmissions.

The effects of altitude hypoxia worsen as pressure altitude increases and over the duration of exposure, and include impairment of cognitive skills, impaired psychomotor coordination, reduced reaction times and loss of consciousness. From the evidence available, further elaborated on below, it is almost certain that during the flight the pilot experienced hypoxia symptoms that degraded their ability to operate the aircraft, and it is possible that the pilot also experienced some loss of consciousness.

The ATSB also identified that the aircraft was likely higher than indicated by the barometric data transmitted by the automatic dependent surveillance broadcast (ADS-B) transponder. During cruise at FL280 it is likely that the actual altitude of the aircraft was at about 29,400 ft, which would have further exacerbated the effects of altitude hypoxia.

Contributing factor

The pilot's ability to safely operate the aircraft was almost certainly significantly degraded by the onset of altitude hypoxia.

Accident sequence

Power reduction

About 4 minutes prior to the accident, when VH-HPY was about 67 km south-east of Cloncurry Airport, the aircraft entered a very shallow descent from FL280, and its airspeed began to decay at a linear rate. Over a period of 2 minutes the airspeed reduced from about 148 to 86 knots calibrated airspeed. 

The flight plan route, and ATC clearance current at the time, was for the aircraft to track to a location near Mount Gordon to undertake line scanning. Both the flight to this location and line scanning were to be conducted at FL280. Consequently, there was no planned operational reason for the aircraft to initiate a descent at the location where the deceleration commenced. 

The linear deceleration, combined with the shallow descent, was estimated to require a reduction in engine power settings to about 25% maximum continuous power (MCP). This value was consistent with the power setting calculated to be used by the pilot earlier in the flight when the aircraft undertook a descent from FL280 to FL150, and significantly less than the 46–48% MCP setting that was calculated to have been used by the pilot during cruise. 

It is possible that, as the aircraft neared Cloncurry, the pilot reduced the power with the intention of undertaking a similar manoeuvre. Overall, there was insufficient evidence to determine why the power levers were reduced during the flight. However, the pilot’s ability to manage the aircraft systems (such as not disengaging the autopilot), or communicate their intentions to ATC, would probably have been impacted by the effects of altitude hypoxia, resulting in the pilot not initiating the descent correctly.   

Contributing factor

While in cruise at flight level 280, both power levers were probably reduced without an appropriate descent rate being initiated, resulting in a progressive reduction of airspeed.

Departure from controlled flight

The flight data, in conjunction with the wreckage composition and witness observations, indicate the aircraft had entered a stable spin by about 10,500 ft that continued until impact with terrain. 

There was no hazardous weather forecast for the area and the wreckage composition was not consistent with an in-flight breakup with all major components accounted amongst the wreckage at the accident site. While the quantity of fuel onboard the aircraft could not be established, the engine and propeller indications, flight performance data, witness reports, and large post-impact fuel-fed fire were consistent with the engines operating and producing power at impact. 

The aircraft wreckage was surrounded by an undamaged tree and termite mounds, indicating a near vertical trajectory, and the aircraft’s angle of entry was shallow and upright. The aft fuselage was compressed and displaced on the windward side, and the aircraft nose was displaced to the left, indicating clockwise rotation at impact. 

Several possibilities for the aircraft’s departure from controlled flight were examined.

Stall

An aerodynamic stall was examined as a possible mechanism for the aircraft’s departure from controlled flight. However, this scenario was considered unlikely as the calculated stall speed of the aircraft at the time was about 74 kt calibrated airspeed (KCAS), 12 kt less than the calculated airspeed of the aircraft. Additionally, it was calculated that the aircraft engines were producing about 25% MCP, which would effectively decrease the stall speed and result in a further increased margin above the stall. 

Inoperative engine

An inoperative engine resulting in an inability to maintain directional control was also considered and excluded as a mechanism for the departure from controlled flight. While the minimum control speed air (VMCA) for the aircraft was 95 KCAS, the minimum control speed decreased to approximately 67 KCAS when the 25% MCP engine power was applied to the scenario (assuming half the lateral thrust and thus half the yaw moment). This speed was 19 kt less than the speed of the aircraft. 

Both engines had internal damage indicating they were operating at the time of impact. The damage present on both propellers showed multiple indications that the engines were probably operating at a low to moderate power at the time of impact, further reducing the likelihood of such a scenario. 

Autopilot disengagement

The autopilot trim servo monitor had fault detection and diagnostic capabilities that would automatically disengage the autopilot if it detected an exceedance of threshold voltages within a servo as it worked against an aerodynamic or mechanical force. It is possible that the threshold voltage of the elevator/elevator trim servo was exceeded as the angle of attack increased and, as a result, the autopilot disengaged, and the aircraft began a slow roll to the left. However, no data existed that captured the resistance values within these servos and, consequently, an accurate calculation of the conditions present within the autopilot system could not be achieved. 

Emergency descent

The flight data was consistent with the pilot’s training notes for the execution of an emergency descent which stated, ‘best initiated with roll, using the secondary effect (yaw) to pitch the nose down to the required attitude without causing negative load factor.’ It is therefore possible that the pilot manually disconnected the autopilot and initiated the descent manoeuvre, while managing the effects of altitude hypoxia. It is also possible, albeit less likely, that one of the camera operators may have manually disconnected the autopilot in response to the hypoxic scenario. 

Regardless of the mechanism for the initial departure from controlled flight, the manoeuvre progressed to a high-speed descent with an average vertical speed of about 19,500 ft/min (192 kt vertical). Prior to the aircraft passing 10,500 ft the aircraft transitioned from a high-speed regime to a slow, below stall speed spin. There were 2 scenarios that would likely result in such a transition. They were a pull out of a near vertical dive or spiral dive, without overstressing the airframe to: 

  • a climbing attitude allowing the speed to decay to around stall before an uncoordinated entry into the spin; or
  • an entry to an accelerated stall due to high ‘g’ acceleration, possibly while attempting to roll wings level. 

The first scenario is unlikely due to there being no evidence of climbing flight in the flight data. 

From an almost certain hypoxic state, with rapid descent into increasing air density and pressure, and with increasing wind noise and possibly airframe buffet, the pilot likely became more aware of their situation and attempted to manoeuvre the aircraft by pulling out of the dive. In a vertical dive pull out, stall speed will increase with normal acceleration. If yaw or roll was present at the time of the stall, it would likely have resulted in the aircraft entering an unintentional spin condition that continued until the aircraft impacted terrain.

Furthermore, being a twin-engine aircraft, spin recovery is not probable due to the relatively large lateral/polar moment of inertia created by the wing-mounted engines. The flight manual contained a section on spin recovery, but it also stated that no spin testing had been conducted.

Contributing factor

The aircraft entered a descending anticlockwise turn with an increasing rate of descent. At about 10,500 ft, control input(s) were almost certainly made, probably an attempt to recover, that transitioned the aircraft from a high-speed descent to a spin condition that was likely unrecoverable and which continued until the impact with terrain.

VH-HPY pressurisation defect and continued operations at high altitude

Pressurisation defect

The aircraft had a pressurised cabin that was designed to permit the aircraft to operate up to a service ceiling of 35,000 ft without the occupants requiring supplemental oxygen. The aircraft was also fitted with an oxygen system, to be used in the event of an emergency such as a cabin depressurisation, that allowed the pilot to make a planned descent to a safe altitude.

However, the aircraft had a known, long-term, unresolved intermittent pressurisation system defect that would occasionally limit the maximum attainable cabin differential to about 2.2 psi. The normal operating cabin differential was about 6.6 psi. The pressurisation defect was known by AGAIR management personnel and pilots, as well as engineering staff at the operator’s maintenance facility (General Aviation Maintenance). This included the AGAIR head of flying operations (HOFO), chief operating officer (COO) and the pilot of the accident flight. While the defect had not been recorded on the maintenance release, nor entered into the AGAIR hazard and occurrence reporting system (SMS), raised at safety meetings or reported to the external safety manager, attempts had been made by GAM engineers to resolve the defect, but these attempts were unsuccessful. 

The defect would manifest during climb, indicated by a low value on the cabin differential gauge, which would give the pilot operating the aircraft the opportunity to cease the climb at a level that would maintain a safe cabin altitude (typically less than 10,000 ft). If the climb was continued, and the cabin altitude exceeded 11,000 ft (± 500 ft), the pilot would be alerted to the unsafe cabin altitude by an aural warning, which could be silenced by the pilot, and a flashing annunciator that would continue for 10–20 seconds and then remain illuminated until the cabin altitude was below the 11,000 ft threshold. In this instance, the pilot’s operating handbook (POH) required the pilot to don an oxygen mask and initiate a descent to 12,000 ft or below.

The POH required the aircraft to be operated unpressurised if a pressurisation system component was inoperative. The aircraft was fitted with an oxygen system, but it was for emergency use only to allow the pilot to make a controlled descent to a safe altitude in the event of a depressurisation or cabin air contamination event. Consequently, with the pressurisation system defective, the aircraft was required by aviation legislation to be operated no longer than 30 minutes continuously between FL125 and less than FL140, or it could be operated indefinitely at a level below FL125.

Pilot actions during previous flights

AGAIR normally conducted line scanning as a single pilot operation along with one camera operator on board. The flights were typically flown at FL280 as it provided for a wide camera swathe and increased fuel economy. Recorded data shows that about 70% of all VH-HPY flights into and out of Toowoomba during 4 September 2023–4 November 2023 involved a cruise at FL280. However, the associated operational procedures (in draft at the time of the accident) permitted line scanning to take place at any altitude at or above 5,000 ft. While management and draft procedures noted FL280 provided the best efficiency for both transiting and scanning, there was no specific requirement for the flights to be conducted only at FL280. 

The pilot of the accident flight undertook their first line scanning flight as pilot in command on 28 September 2023 and flew 24 flights as PIC of VH‑HPY, 19 of which involved a cruise at FL280. Over this period, the pilot sent a series of emails to AGAIR management personnel that described a practice of continuing to operate VH-HPY at FL280 while the pressurisation system was defective. In one such email, the pilot stated that they were regularly spending 90 minutes at a cabin altitude of 19,000 ft while operating at FL280. 

The time of useful consciousness (TUC) at 19,000 ft without a supplemental supply of oxygen could be as low as 18 minutes. To mitigate the risk of hypoxia, the pilot described using the aircraft’s oxygen system for non-emergency use. The oxygen system was designed for emergency use only, and for continuous flight at a cabin altitude of 19,000 ft, the pilot and crew were legally required to use an appropriate oxygen system, that is, a system designed for continued use over the duration of the flight.

The pilot of the accident flight also communicated a practice of conducting brief descents to a lower level as an additional means of managing the effects of hypoxia. A review of flight data revealed that the pilot had conducted similar short descents during 7 flights in the lead-up to the accident. No normal or approved operational requirement for these descents could be established. 

The emails sent by the pilot, and the VH-HPY historical flight data, indicate the pilot had a pattern of normalised deviation from safe operating practices by continuing to operate the aircraft at FL280 when the pressurisation system was defective. However, the pilot was not alone in the practice of continuing to operate the aircraft at FL280 while the pressurisation system was defective (see Organisational influences). These flights were conducted without access to a suitable oxygen supply, significantly increasing the risk of altitude hypoxia induced incapacitation.

The concept of ‘normalisation of deviance’ describes the desensitisation to risk experienced by individuals or groups who repeatedly deviate from safe operating practices, within a high-risk environment, without encountering negative consequences. A prominent feature of the normalisation of deviance is the desensitisation process, where frequent deviant actions result in the practice’s normalisation and perceived standardisation within everyday operations. This sets a new precedent for what is considered tolerable and establishes a new normal from which further deviations may occur. In the absence of intervention (for example, an independent audit), this cycle of deviance is disrupted only when the behaviour results in an undesirable outcome such as an accident (Sedlar and others 2022).

Contributing factor

The pilot had a normalised practice of operating VH-HPY with a cabin altitude that required the use of supplemental oxygen. These flights were conducted without access to a suitable oxygen supply, significantly increasing the risk of altitude hypoxia induced incapacitation.

Pilot actions during accident flight

As previously noted, the pilot’s speech and related behaviour while the aircraft was at FL280 demonstrated significant and progressive impairment that was consistent with altitude hypoxia. Within the aviation context, the principal causes of altitude hypoxia are: 

  • ascent to high cabin altitude without the use of supplemental oxygen
  • failure of the supplemental oxygen system, or oxygen set to an inadequate concentration and or pressure, while at high cabin altitude
  • depressurisation of the pressure cabin at high altitude (Gradwell 2016).

In addition, and as previously stated, the pilot of the accident flight had a normalised practice of operating VH-HPY at FL280 with the pressurisation system defective, resulting in a cabin altitude of 19,000 ft. The pilot’s strategies for mitigating the effects of hypoxia during these flights was to undertake descents to lower flight levels for a short period of time and use of the aircraft oxygen system for non-emergency use.

During the accident flight, at about 1141, the pilot undertook a descent to FL150 for a period of about 6 minutes, before climbing back to FL280. The descent was not part of the submitted flight plan and there was no operational reason for the descent to occur. The descent, which was consistent with the pilot’s practice for hypoxia management, almost certainly indicates that the aircraft's pressurisation system did not attain the required cabin altitude.

Although the aircraft cabin altitude at FL280 was not recorded and had not been reported by the pilot during the accident flight, if the aircraft pressurisation system defect manifested as it had done on previous flights, the cabin altitude at FL280 would have been about 19,000 ft. The TUC at 19,000 ft could be as low as 18 minutes, however the aircraft had been in cruise for about 90 minutes when the pilot made their final radio transmission. Although TUC is dependent on individual factors, the extended period beyond the calculated TUC may indicate that the pilot used the oxygen system for non-emergency use during cruise, as they had also done during previous flights.

The oxygen system included 2 rapid-donning masks in the cockpit and drop‑down masks within the cabin. It is unclear how these masks may have been used with 3 occupants on board the aircraft. There was one cylinder that provided oxygen to the cockpit and cabin masks which was refilled during the maintenance activity that took place 4 days prior to the accident. The aircraft had flown 2 flights since the refill so the amount of oxygen contained within the cylinder when the aircraft departed could not be determined. However, assuming the cylinder was at 1,800 psi at the time of departure from Toowoomba Airport, it was calculated that the cylinder contents would be depleted after about 29 minutes if used by 3 occupants, depending on flow rates. 

This time period is significantly less than the time the aircraft spent in cruise at FL280 up to the pilot’s final radio transmission. It is possible that the aircraft cabin altitude was less than 19,000 ft but still within the hypoxic range, or the crew may have been using the oxygen system intermittently, or highly diluted, to manage the acute symptoms of hypoxia. Such a scenario would be highly unsafe as the symptoms and signs of hypoxia, on acute exposure to altitudes greater than 15,000 ft when breathing air, include a loss of critical judgment and willpower, with the subject usually unaware of any deterioration in performance or the presence of hypoxia. In this scenario, the pilot may have eventually lost the self-awareness required to identify the symptoms of hypoxia and take appropriate corrective action to resolve the situation. 

The oxygen system panel, which included the cylinder pressure gauge for the aircraft oxygen system, was recessed into the sidewall on the right side of the cockpit out of the pilot’s direct field of view. Consequently, it is also possible that the oxygen within the cylinder was eventually exhausted by the 3 occupants, without their awareness, resulting in a similar outcome. 

Contributing factor

The aircraft's pressurisation system probably did not attain the required cabin altitude when operating at flight level 280 during the accident flight. The pilot probably knowingly continued the flight with a cabin altitude that required the use of supplemental oxygen, without access to a suitable oxygen supply.

Organisational influences

Normalisation of deviance
Chief operating officer

The AGAIR chief operating officer (COO), who oversighted the line scanning operations, occasionally experienced VH-HPY’s intermittent pressurisation system defect while flying as pilot in command. On at least 2 occasions the COO continued to operate VH-HPY with a cabin altitude that required the use of oxygen, without access to a suitable oxygen supply.

On 16 October 2023, the pilot of the accident flight sent the COO an email stating that they were operating the aircraft with a high cabin altitude while using the aircraft’s oxygen system and, consequently, the oxygen cylinder needed to be refilled. The COO responded to the email by providing procedures to facilitate the refilling of the oxygen cylinder, but the hazardous practice of continuing to operate the aircraft with an excessive cabin altitude was not addressed. 

The COO was a senior AGAIR manager, and their actions (and inactions) had the potential to influence the operational standards of other pilots and crew, and set the risk appetite for the operation. Their practice of continuing to operate the aircraft and allowing it to be operated at FL280 with the pressurisation system defective exposed the aircraft’s occupants to significant risk of hypoxic induced incapacitation. In doing so, the COO likely normalised the deviation from the POH and civil aviation legislation and communicated the acceptance of such non-compliant practices by senior AGAIR management.

Head of flying operations 

The AGAIR head of flying operations (HOFO), who was also the owner, chief executive officer (CEO), and head of airworthiness and aircraft maintenance control (HAAMC), stated to the ATSB that they were aware of the intermittent pressurisation defect, but they were not aware of any pilots who had continued to operate the aircraft at FL280 with the pressurisation system defective. This was despite the HOFO having received and responded to an email from the pilot of the accident flight on 22 October 2023 that outlined the practice of operating the aircraft with a cabin altitude of 19,000 ft while using the aircraft oxygen system. The response from the HOFO to the email included the statement ‘thanks for keeping it going’. Such a response would have been reasonably perceived by the pilot of the accident flight as encouraging their practice of continuing to operate the aircraft at an excessive cabin altitude, and inappropriate use of the oxygen system.

The HOFO stated that they interpreted the email as being what ‘would’ happen rather than what ‘was’ happening. However, if the HOFO’s premise that they interpreted the email content as hypothetical is to be accepted, then it would be reasonable to expect that the HOFO would have immediately advised the pilot of the accident flight not to apply such a hazardous operational practice. However, the HOFO’s email response contained no such advice, and they did not contact the pilot by any other means to discuss the content of the email. 

The HOFO stated that they had not provided any operational advice to the pilot following the email as they had passed operational control of the line scanning activity to the COO. This included reporting lines for the pilot of the accident flight. The COO also received the same email from the pilot of the accident flight on 22 October 2023, but they did not reply or contact the pilot to discuss its content.

Contributing factor

The AGAIR aircraft VH-HPY pressurisation system could not reliably attain the required cabin altitude during flight due to a known, long-term, unresolved intermittent defect. AGAIR management personnel were aware of the defect and, through a combination of inaction, encouragement and, in some instances direct involvement, permitted the aircraft to continue operations at an excessive cabin altitude. (Safety issue)

Operational control

The COO had oversight of the line scanning operation. However, the approved organisational structure, as contained within the AGAIR operations manual (OM), did not reflect this arrangement. Instead, the COO role was depicted as having responsibility for ground support equipment and personnel, customers and suppliers only. There were no defined responsibilities for the COO contained within the AGAIR OM, nor any procedures specific to line scanning operations, making it unclear exactly what the COO’s role entailed. 

The AGAIR OM permitted the HOFO to delegate ‘certain duties’ to company personnel, but the responsibility remained the HOFO’s. Consequently, the undocumented delegation of duties associated with the line scanning activities to the COO did not absolve the responsibility of the HOFO to ensure these activities were:

  • compliant with aviation legislation
  • conducted by pilots who conformed to company standards
  • undertaken in an aircraft that was appropriate for the planned task.

The HOFO had long-term awareness of the pressurisation defect and had experienced the issue themselves while flying the aircraft. However, at no time had the HOFO (or the COO):

  • recorded the pressurisation defect on the aircraft maintenance release or required other pilots to do so
  • provided explicit procedures to pilots for managing the defect
  • communicated the ongoing issue to the AGAIR safety manager
  • submitted a hazard or occurrence report
  • conducted or requested a formal risk assessment of the issue.

In the days leading up to the accident, both the HOFO and the COO were advised that the pilot of the accident flight was operating VH-HPY at a hazardous cabin altitude without access to a suitable oxygen supply. However, neither the HOFO nor the COO exercised effective operational control to address the significant safety implications of the activity. Instead, the HOFO and the COO’s combination of inaction, direct involvement and, in some instances facilitation and encouragement of the activities, resulted in a hazardous, ongoing practice.

Contributing factor

AGAIR management exercised ineffective operational control over the line scanning activities. As a result, the ongoing intermittent pressurisation defect was not formally recorded, the issues with the aircraft were not communicated to the AGAIR safety manager, and the hazardous practice of operating the aircraft at a cabin altitude that required the use of supplemental oxygen, without access to a suitable oxygen supply, was allowed to continue. (Safety issue)

Aircraft defects not recorded

The AGAIR operations manual contained policy and procedures to formally manage defects that were identified while an aircraft was in service. These procedures required the defect to be recorded on the aircraft’s maintenance release, and then communicated to the HAAMC, who would in turn liaise with the maintenance provider. Collectively, defects could then be appropriately managed, drawing upon approved data such as the POH, the aircraft maintenance manual and the relevant legislative requirements.

Records of defects and the actions taken to rectify them can provide a means to measure their effectiveness, and to help focus any further action if required. Similarly, the recording of defects on the maintenance release can provide a means for flight crews to readily assess any defects the aircraft may have had, and what rectifications were made. Flight crews could then anticipate further issues, brief other crew members, flight plan accordingly if needed, and proactively prepare for the defect should it re-occur.

Likely as a routine practice, evidenced from the records for VH‑LVG (a Gulfstream 690), and VH‑HPY (a Gulfstream 695A) and from interviews conducted during the investigation, AGAIR was managing defects in a simplified, but unapproved manner. This practice was similar to the approved method in that defects were sometimes communicated to the HAAMC or the maintenance provider by means such as email or text messages. However, defects were not always recorded on the maintenance release, and communication of defects sometimes occurred just prior to the aircraft arriving at the maintenance facility. This practice was likely to have been occurring for some time. As discussed below in CASA surveillance events, an AGAIR pilot reported concerns in 2019 that included the management of aircraft defects. 

Although similar, this routine practice removed risk controls that were in place to ensure that defects were managed for the safe operation of the aircraft. The issues affecting the pressurisation system of VH‑HPY did not mean that the aircraft could not be flown. The controls in place for safe operation in this case would require the aircraft be flown unpressurised, and at a suitable altitude. To operate the aircraft with an unserviceable or underperforming pressurisation system would have required an appropriate level of scrutiny by the pilot in command, the HOFO/HAAMC, the maintenance provider and, if needed, CASA.

The logbooks for the aircraft prior to 2014 when it was operating in South Africa showed that the pressurisation system was underperforming on multiple occasions, and detailed the actions taken to rectify the issue. Since 2014, and with the exception of an entry for a depressurisation event in August 2020, no instances of pressurisation defects occurring with VH-HPY had been recorded on the aircraft’s maintenance release. These defects were known to those operating and maintaining the aircraft, and any transfer of information relating to those defects was by informal means, such as orally, or electronically (email, text messages). Should an independent review of the aircraft’s history be required, it would be limited by the absence of defect endorsements relating to the aircraft’s pressurisation system from 2014 onwards.

When the pressurisation system in VH‑HPY was underperforming, the aircraft was sometimes operated with cabin altitudes above 10,000 ft by using the oxygen system for general operations rather than its intended function (that is, for use in an emergency situation). As previously discussed, this was known to the pilot of the accident flight, the HOFO/HAAMC, the COO, and on one occasion, the maintenance provider. While the Gulfstream 695A POH refers to the oxygen system as ‘supplemental’, it is unambiguous in that the oxygen system is for use in an emergency, providing sufficient oxygen to descend to an altitude where oxygen is no longer required.

Aircraft defects are sometimes minor, with limited or no operational impact. However, the operational impact of defects relating to VH-HPY’s pressurisation system was unnecessarily more significant because the defects were accepted by the pilot of the accident flight, the HOFO/HAAMC, and the COO, and then managed using the aircraft’s oxygen system, rather than rectified or, in the interim, conducting flights safely at lower altitudes. A full understanding of the operational impact of the defects was in part limited by their absence from the aircraft’s maintenance release. In turn, such records would have assisted in analysing the nature and frequency of the defects, and for corrective actions to be carried out by the appropriate persons, and in accordance with published data.

Other factor that increased risk

AGAIR Gulfstream 690 and 695 aircraft were operated with known defects without being recorded on the aircrafts’ maintenance release, likely as a routine practice. For VH-HPY, the absence of documented historical information limited the ability to assess the operational impact of the pressurisation defect and the effectiveness of maintenance rectification activities. (Safety issue)

Air traffic control

Pressurisation information not communicated to air traffic control

While VH-HPY was still in flight, the Airservices Australia air traffic management director (ATMD) and shift manager (SM) spoke with the AGAIR HOFO by telephone to advise that ATC had lost radio communications with VH-HPY for an extended period. 

During the telephone conversation, which lasted nearly 6 minutes, the HOFO was advised that the pilot had exhibited symptoms of hypoxia, and that ATC had initiated ‘oxygen’ radio calls. The HOFO was also informed that ATC had subsequently regained direct communication with the pilot, who had confirmed operations were normal, and that ATC no longer had concerns for the aircraft and that the emergency phases had been cancelled. 

At no point during the telephone conversation did the HOFO advise the ATMD or SM that the aircraft had a known intermittent pressurisation defect as it did not occur to them to do so. It is possible the HOFO did not perceive a need to provide this information once they were advised that communications had been re-established with the pilot.

The telephone conversation to AGAIR was a missed opportunity to communicate critical safety information about the aircraft, that was directly relevant to the conversation, at a time when ATC could have taken further action to instruct the pilot to descend to a safe altitude. 

Contributing factor

The AGAIR head of flying operations did not communicate critical safety information about the known intermittent pressurisation defect on VH-HPY when they were phoned by air traffic control about concerns that the pilot may be impacted by hypoxia.

Air traffic controller actions

During the initial loss of communication while the aircraft was at FL280, the ATMD was able to speak briefly with the pilot via mobile telephone. The ATMD identified that the pilot’s speech during the conversation was slow and flat. This information was passed to the SM and Simpson region controller (controller), who also noted that the aircraft was slightly off track. As a result, the SM determined that the pilot may have been suffering from hypoxia and they initiated the hypoxic pilot emergency procedures and escalated the aircraft’s status to an alert phase.

That hypoxia assessment was likely correct given the analysis of the pilot’s speech indicated a progressive deterioration that was consistent with altitude hypoxia. Consequently, the initiation of the hypoxic pilot emergency procedures was the appropriate response.

Over the following 10 minutes, the controller attempted to get the pilot to descend the aircraft, as instructed by the hypoxic pilot emergency procedure, using the phrase ‘oxygen, oxygen, oxygen descend to one zero thousand feet’. They also made multiple attempts to contact the pilot on different frequencies and relayed messages via other aircraft within the vicinity of VH-HPY. At the same time, the ATMD attempted to call the pilot’s mobile phone again, and sent 2 text messages, but the pilot did not respond. Eventually, a crewmember on board a Royal Australian Air Force (RAAF) aircraft established contact with the pilot, followed by ATC a short time later. 

While ATC held significant concern for the aircraft and its occupants during the loss of communication period, their concerns were de-escalated over a period of 2 minutes after the pilot contacted the RAAF crew resulting in ATC downgrading and cancelling the emergency phases. This de-escalation occurred without querying why the pilot had not responded to ATC broadcasts for 1 hour and 13 minutes. 

The hypoxic pilot emergency procedures contained an instruction for the controller to advise the pilot to ‘check oxygen system and connections’ and ‘check pressurisation’. About 2 minutes after the cancellation of the uncertainty phase, the controller asked the pilot to ‘just confirm your oxygen system is ops normal’, to which the pilot responded ‘affirm’. No further actions from the hypoxic pilot emergency procedures were undertaken while the pilot was in communication with ATC. The controller recalled the pilot’s speech was ‘clear and concise’, but this was not consistent with the speech analysis that indicated a deterioration in the pilot’s speech at that time.

The pilot was subsequently provided with an ATC clearance to undertake the line scanning operations near Mount Gordon, but over the following 4 minutes the pilot repeated the clearance from the controller 4 times, seeming uncertain about the status of the clearance. They twice requested confirmation that the controller had copied their clearance readback. The radio recordings during this period indicate that the pilot’s speech rate had substantially lowered from earlier communications and was becoming worse. The controller recalled a lot of activity taking place in the vicinity of their console at that time, which included questions regarding the status of the aircraft. 

The pilot’s final radio transmission displayed the slowest speaking rate of all their communications during the flight and contained stuttering and operational mistakes. However, the controller did not re-identify the possibility of hypoxia. At the time of the accident, the Simpson region was ‘fully combined’ with one controller responsible for the entire region of about 2 million square kilometres. While the traffic density was described as low, the controller and the SM had been heavily tasked with attempts to regain communications with VH-HPY for an extensive period while also communicating with other aircraft within the region. 

Although no reason for the loss of communication had been established, the pilot had confirmed that the aircraft’s oxygen system was operating normally, and routine radio communications had been re-established. These factors, combined with ATC having no knowledge of the aircraft’s pressurisation system defect as the AGAIR HOFO had not communicated this information during their telephone conversation, likely resulted in the ATC personnel involved reducing their vigilance about hypoxia. Consequently, the controller did not identify the deterioration in the pilot’s speech and, in a return to normal operations, did not attempt to contact the pilot until about 18 minutes later. The pilot did not respond to any further calls from ATC and the aircraft impacted terrain a further 6 minutes later.   

Contributing factor

After being told by the pilot that operations were normal, controllers likely reduced their vigilance about hypoxia and did not re-identify the possibility of hypoxia during the subsequent progressive deterioration of the pilot’s speech.

Air traffic control hypoxia emergency procedures

At the time of the accident, the procedures to be used if a controller suspected a pilot may be suffering from hypoxia were contained in the Airservices Australia in-flight emergency response checklist (IFER) procedure (ATS-PROC-0062). The IFER hypoxia checklist contained a list of symptoms that could indicate a pilot was impacted by hypoxia, and the actions to take when managing the aircraft. This included advising the pilot:

• Check oxygen system and connections

• Check pressurisation

When confirmed and checked - if no change or condition worsens, act immediately to descend the aircraft.

The likely symptoms and signs of hypoxia, on acute exposure to altitudes greater than 15,000 ft when breathing air, include a loss of critical judgment and willpower. Because of the loss of self‑criticism, the subject is usually unaware of any deterioration in performance or the presence of hypoxia (Nicholson and Rainford 2000). Consequently, a reliance on a pilot’s response to queries regarding the status of the aircraft oxygen and pressurisation systems would probably yield an unreliable response if the pilot were impacted by hypoxia.

Additionally, the IFER hypoxia checklist contained no instructions for a controller to follow when standing down the emergency response and resuming normal operations. In contrast the Airservices Australia IFER management abnormal operations manual, which was used for training and information, did contain material, albeit limited, regarding the transition to normal operations after any type of inflight emergency. This included the statements:

• Extensive experience, both in Australia and overseas, shows that crews often try to down‑play problems when communicating with [air traffic control]. Furthermore, what may be normal as far as the crew is concerned may still preclude the operational system from operating normally

• If there is the slightest doubt about the continuing safety of the aircraft, it is prudent to continue with the IFER even if at a low key

The information contained within the IFER management abnormal operations manual was directly relevant to the hypoxic scenario involved during the accident flight, but the information was not integrated within the IFER hypoxia checklist, which is the document used by controllers during operations.

When designing emergency and abnormal checklists, human performance capabilities and limitations under high stress and workload should influence the design and content. Attention should be given to the structure of these checklists to ensure that directions and information are complete, clear, and concise (Burian et al 2005). As the advice regarding the transition to normal operations was contained in a different document which likely relied on a controller recalling it from memory, the IFER hypoxia checklist was not complete and did not provide adequate guidance to controllers for the process to follow when ceasing the emergency response. This omission increased the risk that the emergency response could be inappropriately downgraded during a developing hypoxic scenario.

Other factor that increased risk

The Airservices Australia hypoxic pilot emergency checklist did not contain guidance on ceasing the emergency response. This increased the risk that a controller may inappropriately downgrade the emergency response during a developing hypoxic scenario. (Safety issue)

CASA surveillance events

The available evidence indicated that CASA's oversight of AGAIR and GAM was broadly appropriate for the type and size of operations. There were 7 surveillance events from 2019 to 2023, including 4 site visits, and CASA issued various findings as a result.

In May 2019, CASA undertook a level 2 surveillance event of AGAIR to examine concerns reported by an AGAIR pilot, about non-compliant flight and duty rostering practices, and the management of aircraft defects involving 2 aircraft of a similar type to VH-HPY – VH-LVG and VH‑CLT. The latter concerns were about the deferral of defects that (according to the reported concerns) impacted the safety of operations ‘on a daily basis,’ and conflicting advice being given to pilots on the continuation of operations with such known defects. 

Had non-compliant maintenance practices been taking place at the time, and been discovered by CASA in its response to the reported concerns, this would potentially have been an opportunity to influence the way the operator managed aircraft defects, such as the pressurisation issue in VH‑HPY, in the intervening 4 years before the accident. Accordingly, the ATSB sought to determine the extent to which the concerns were valid, and the appropriateness and effectiveness of the CASA response at the time.

The approach used by CASA to conduct the surveillance was, according to the surveillance team’s airworthiness inspector (AWI), intended to determine whether there was any validity to the pilot’s concerns. The ATSB did not determine whether CASA contacted the complainant pilot prior to the surveillance commencing; this would be an important step to clarify the context and specifics of the raised concerns and help direct the surveillance activities. 

The on-site surveillance included:

  • a physical inspection of 2 aircraft, including VH-LVG, which was one of the 2 aircraft that the correspondent had mentioned in their report as having maintenance problems
  • review of the current VH-LVG maintenance release
  • interviews with management personnel.

As a result of the surveillance activity, the pilot’s concern about flight and duty times was partially substantiated (the senior pilot was found to have exceeded flight and duty time requirements) and a safety finding to AGAIR was issued on this. 

On the maintenance aspects of the surveillance event, CASA made no findings, and the 2 maintenance-related observations did not directly indicate any problems with inappropriately deferred maintenance. In effect, based on the information sampled, CASA (at the time) found no evidence that defects with a significant effect on aircraft safety were not being managed appropriately or that pilots were being given conflicting advice on the continuation of operations. 

The ATSB assessment of maintenance records for VH‑LVG from December 2014–May 2019 showed 10 entries indicating unscheduled defect rectification that had been carried out during scheduled maintenance, and which had the characteristics of defects that could have appeared during operations and been identifiable by pilots (in which case they should have been recorded on the maintenance release). The absence of entries on recent historical (expired) maintenance releases up to May 2019 indicates that, during this period, some defects were likely not being recorded on the maintenance release when in service, and were only being rectified when the aircraft arrived for scheduled maintenance. However, only one of the defects was of a type that could have had an effect on the safety of flight (an engine oil pressure indicating system defect). In addition, defects may have been reported through a means other than through the maintenance release or detected during scheduled maintenance. 

The ATSB identified these entries by crosschecking the content of each maintenance release against the aircraft logbooks. The historical maintenance releases and aircraft logbooks were at a different facility to that visited by CASA for the May 2019 surveillance event, and this type of crosschecking activity was not scoped or undertaken as part of that event. 

Crosschecking maintenance releases, logbooks and maintenance worksheets can identify discrepancies or deficiencies in defect reporting, maintenance action tracking, or certification of work performed. This process also helps identify potential issues such as undocumented rectifications, improper deferral of defects, or systemic lapses in maintenance record-keeping, all of which can have implications for continued airworthiness and regulatory compliance. Any problems found can then lead to further evidence gathering regarding an organisation’s defect management practices (for example, directly from employed pilots).

The post-accident activities undertaken by CASA and the ATSB were influenced by facts and circumstances that were learnt after the accident involving VH-HPY. Consequently, the focus and depth of these activities could be directed towards areas of particular relevance to the accident, notably potential non-compliant defect management practices. The May 2019 surveillance did not have the same advantage. At the time this surveillance was conducted, AGAIR had no recent history of regulatory enforcement action or identified need for a higher level of surveillance, and there was limited detail within the pilot’s concern about specific defects or safety of flight issues. CASA also issued a safety finding and 3 observations as a result of the activity; although this enhanced the credibility of the AGAIR pilot’s reported concerns, it also indicates that the surveillance did improve safety within the chosen area of focus.

In summary, given the areas of concern raised by the complainant pilot, the scope of the surveillance event limited the extent of the evidence relating to defect management that was collected. This consequently limited the surveillance team’s ability to determine whether any non‑reporting and improper deferral of defects had been taking place at that time. While there was likely some degree of non-compliant defect management practices at AGAIR in 2019, all but one of the likely non-reported defects were minor in nature (the other was an oil pressure indicating system, which does not present an immediate risk to flight). Accordingly, even if CASA had identified these likely non-reported defects, it is unclear whether there would have been sufficient evidence available for CASA to identify maintenance practices as a broad organisational concern. 

Other finding

A 2019 Civil Aviation Safety Authority surveillance event of AGAIR triggered by concerns reported by an AGAIR pilot, including delayed rectification of airworthiness issues, did not include a crosscheck of maintenance releases against the aircraft logbooks, which limited the surveillance team’s ability to determine whether any non-reporting and improper deferral of defects had been taking place at that time. 

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 pilot incapacitation, loss of control and collision with terrain involving Gulfstream 695A, VH-HPY, 55 km south-east of Cloncurry Airport, Queensland on 4 November 2023.

Contributing factors

  • The pilot's ability to safely operate the aircraft was almost certainly significantly degraded by the onset of altitude hypoxia.
  • While in cruise at flight level 280, both power levers were probably reduced without an appropriate descent rate being initiated, resulting in a progressive reduction of airspeed.
  • The aircraft entered a descending anticlockwise turn with an increasing rate of descent. At about 10,500 ft, control input(s) were almost certainly made, probably an attempt to recover, that transitioned the aircraft from a high-speed descent to a spin condition that was likely unrecoverable and which continued until the impact with terrain.
  • The pilot had a normalised practice of operating VH-HPY with a cabin altitude that required the use of supplemental oxygen. These flights were conducted without access to a suitable oxygen supply, significantly increasing the risk of altitude hypoxia induced incapacitation.
  • The aircraft's pressurisation system probably did not attain the required cabin altitude when operating at flight level 280 during the accident flight. The pilot probably knowingly continued the flight with a cabin altitude that required the use of supplemental oxygen, without access to a suitable oxygen supply.
  • The AGAIR aircraft VH-HPY pressurisation system could not reliably attain the required cabin altitude during flight due to a known, long-term, unresolved intermittent defect. AGAIR management personnel were aware of the defect and, through a combination of inaction, encouragement and, in some instances direct involvement, permitted the aircraft to continue operations at an excessive cabin altitude. (Safety issue)
  • AGAIR management exercised ineffective operational control over the line scanning activities. As a result, the ongoing intermittent pressurisation defect was not formally recorded, the issues with the aircraft were not communicated to the AGAIR safety manager, and the hazardous practice of operating the aircraft at a cabin altitude that required the use of supplemental oxygen, without access to a suitable oxygen supply, was allowed to continue. (Safety issue)
  • The AGAIR head of flying operations did not communicate critical safety information about the known intermittent pressurisation defect on VH-HPY when they were phoned by air traffic control about concerns that the pilot may be impacted by hypoxia.
  • After being told by the pilot that operations were normal, controllers likely reduced their vigilance about hypoxia and did not re-identify the possibility of hypoxia during the subsequent progressive deterioration of the pilot’s speech.

Other factors that increased risk

  • AGAIR Gulfstream 690 and 695 aircraft were operated with known defects without being recorded on the aircraft’s maintenance releases, likely as a routine practice. For VH‑HPY, the absence of documented historical information limited the ability to assess the operational impact of the pressurisation defect and the effectiveness of maintenance rectification activities. (Safety issue)
  • The Airservices Australia hypoxic pilot emergency checklist did not contain guidance on ceasing the emergency response. This increased the risk that a controller may inappropriately downgrade the emergency response during a developing hypoxic scenario. (Safety issue)

Other finding

  • A 2019 Civil Aviation Safety Authority surveillance event of AGAIR triggered by concerns reported by an AGAIR pilot, including delayed rectification of airworthiness issues, did not include a crosscheck of maintenance releases against the aircraft logbooks, which limited the surveillance team’s ability to determine whether any non-reporting and improper deferral of defects had been taking place at that time.

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.

Normalisation of deviance

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

Safety issue description: The AGAIR aircraft VH-HPY pressurisation system could not reliably attain the required cabin altitude during flight due to a known, long-term, unresolved intermittent defect. AGAIR management personnel were aware of the defect and, through a combination of inaction, encouragement and, in some instances direct involvement, permitted the aircraft to continue operations at an excessive cabin altitude.

Operational control

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

Safety issue description: AGAIR management exercised ineffective operational control over the line scanning activities. As a result, the ongoing intermittent pressurisation defect was not formally recorded, the issues with the aircraft were not communicated to the AGAIR safety manager, and the hazardous practice of operating the aircraft at a cabin altitude that required the use of supplemental oxygen, without access to a suitable oxygen supply, was allowed to continue.

 

Safety recommendation description: The ATSB recommends AGAIR initiates an independent review of their organisational structure and oversight of operational activities to assure ongoing effective operational control by management.

Aircraft defects not recorded

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

Safety issue description: AGAIR Gulfstream 690 and 695 aircraft were operated with known defects without being recorded on the aircrafts’ maintenance release, likely as a routine practice. For VH-HPY, the absence of documented historical information limited the ability to assess the operational impact of the pressurisation defect and the effectiveness of maintenance rectification activities. 

Air traffic control hypoxia emergency procedures 

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

Safety issue description: The Airservices Australia hypoxic pilot emergency checklist did not contain guidance on ceasing the emergency response. This increased the risk that a controller may inappropriately downgrade the emergency response during a developing hypoxic scenario. 

Glossary

ADS-BAutomatic dependent surveillance broadcast  
AGLAbove ground level
AHPIAuthorisation holder performance indicator
AoAAngle of attack
AOCAir operator’s certificate
ATCAir traffic control
ATMDAir traffic management director
ATSBAustralian Transport Safety Bureau 
AWIAirworthiness inspector
BoMBureau of Meteorology
CASACivil aviation safety authority
CASRCivil aviation safety regulation
CEOChief executive officer
COOChief operating officer
FL Flight level
GAM General Aviation Maintenance
GPS Global positioning system
HAAMCHead of aircraft airworthiness control
HF High frequency
HOFOHead of flying operations
IFERIn-flight emergency response
IFRInstrument flight rules
KCASCalibrated airspeed
KTASTrue airspeed
LAME Licensed aircraft maintenance engineer
MCPMaximum continuous power
MEL Minimum equipment list
MREL Minium required equipment list
OM Operations manual
PICPilot in command
POHPilot operating handbook
QFES Queensland Fire and Emergency Services
SMShift manager
SMMSafety management manual
SMSSafety management system
TUCTime of useful consciousness
VFRVisual flight rules
VHF Very high frequency
VMCAMinimum control (in the air) airspeed
VMOMaximum operating limit speed

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the next-of-kin of the pilot and both camera operators
  • the pilot’s general practitioner
  • AGAIR
  • Airservices Australia
  • Bureau of Meteorology
  • Civil Aviation Safety Authority
  • witnesses
  • pilots who had previously operated VH-HPY
  • General Aviation Maintenance
  • a Gulfstream 695A training provider
  • Jetfix aircraft maintenance personnel
  • oxygen system provider
  • Ontic
  • OzRunways
  • TrackPlus
  • the previous owner of the aircraft
  • Hartzell Propellers Inc
  • Queensland Fire and Emergency Services
  • Queensland Police Service
  • a speech analysis specialist
  • National Transportation Safety Board
  • Defence Flight Safety Bureau 

References

Gradwell, D. & Rainford, D. (2016). Ernsting’s aviation and space medicine (5th ed). Boca Raton, FL, US: Taylor & Francis Group

Sedlar, N. Irwin, A. Martin, D. & Roberts, R. (2022). A qualitative systematic review on the application of the normalization of deviance phenomenon within high-risk industries. School of Psychology, William Guild Building, University of Aberdeen, Aberdeen, UK. & Aberdeen Business School, Robert Gordon University (RGU), Aberdeen, UK.

US Federal Aviation Administration. (2015). Aircraft operations at altitudes above 25,000 feet mean sea level or mach numbers greater than .75. Advisory Circular 61-107B

US Federal Aviation Administration. (2021). Airplane Flying Handbook FAA-H-8083-3C. Chapter 5: Maintaining Aircraft Control: Upset Prevention and Recovery Training. Retrieved 14, January 2025 

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 next-of-kin of the pilot and both camera operators
  • AGAIR
  • General Aviation Maintenance
  • Civil Aviation Safety Authority
  • Queensland Fire and Emergency Services
  • oxygen system provider
  • previous pilots who had flown VH-HPY
  • National Transportation Safety Board
  • a speech specialist
  • Airservices Australia
  • Airservices Australia air traffic management director
  • Airservices Australia shift manager
  • Airservices Australia controller
  • Hartzell Propellers Pty Ltd
  • Ontic
  • a 695A training provider
  • Defence Flight Safety Bureau. 

Submissions were received from:

  • the next-of-kin of the pilot
  • Airservices Australia
  • Airservices Australia air traffic management director
  • Airservices Australia shift manager
  • AGAIR
  • Civil Aviation Safety Authority
  • oxygen system provider
  • a 695A training provider

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

Appendices

Appendix A – Gulfstream 695A systems information

Pressurisation system
Gulfstream 695A pressurisation system

The Gulfstream 695A is pressurised by ducting air from both engines (known as bleed air) into the cabin and controlling its flow overboard via outflow safety valves to maintain the desired cabin pressure. The source of bleed air can be selected within the cockpit to be via both engines, via the left or right engine, or selected off. The selector directs power to close the relevant engine bleed air valve or valves, which are opened pneumatically when the engines are operating (Figure A1 and Figure A2).

Figure A1: VH-HPY cockpit layout 

Figure A1: VH-HPY cockpit layout

Note: Image captured prior to the accident. Source: Cameron Marchant, annotated by the ATSB

Figure A2: Bleed air selector in VH-HPY

Figure A2: Bleed air selector in VH-HPY

Note: Image captured prior to accident. Source: Cameron Marchant, annotated by the ATSB

A cabin pressure controller is set by flight crew to maintain cabin pressure from take-off, through climb, cruise, and descent. A rate of change knob in its ‘nominal’ position controls the cabin altitude rate of change (or vertical speed) to 500 ft/min and can be set from a minimum of 50 ft/min to a maximum of 3,000 ft/min. The cabin altitude knob is used to set the desired cabin altitude (up to 10,000 ft) and has an inner scale that shows the corresponding aircraft altitude that can be flown without exceeding the aircraft’s maximum differential pressure. The adjacent indicators for the cabin show the cabin altitude, differential pressure, and the cabin’s vertical speed (Figure A3).

Figure A3: Pressurisation controls and indicators fitted to VH-HPY

Figure A3: Pressurisation controls and indicators fitted to VH-HPY

Note: Image captured prior to the accident. Source: Cameron Marchant, annotated by the ATSB

The cabin pressure controller also prevents the cabin differential pressure from exceeding the maximum differential pressure of 6.8 psi. The Gulfstream 695A is certified to operate up to 35,000 ft above mean sea level. At this altitude, and at the maximum differential pressure, the cabin altitude would be 9,600 ft.

The maximum differential pressure is prevented from being exceeded by the outflow safety valves, though if the aircraft continued to climb there would be a corresponding climb in the cabin altitude.

Visual warning system

The cabin altitude visual warning system is limited[45] to a single caption on the glareshield annunciator panel. The caption, ‘CABIN ALT’ is coloured red when illuminated, meaning that immediate corrective action is required (Figure A4).  When the cabin altitude of the aircraft is at or above 11,000 ft (± 500 ft), ‘CABIN ALT’ flashes for 10–20 seconds and is accompanied by an aural warning. After 10–20 seconds the annunciator remains on until the cabin altitude is below 11,000 ft.

Figure A4: Cockpit of VH-HPY showing annunciator panel cabin altitude warning light

Figure A4: Cockpit of VH-HPY showing annunciator panel cabin altitude warning light

Note: Image captured prior to the accident. Source: Cameron Marchant and Ontic (inset), annotated by the ATSB

Aural warning system

The cabin altitude aural warning system produces a tone that pulses 6 times per second. The aural warning is triggered when the cabin altitude exceeds 11,000 ft. The aural warning can be silenced by pressing a button on the left engine power lever (Figure A5).

Figure A5: Cabin altitude aural warning silencing button

Figure A5: Cabin altitude aural warning silencing button

Source: Ontic, annotated by the ATSB

Oxygen system
Overview

The Gulfstream 695A is equipped with an oxygen system that provides life support in the event of an emergency. The POH states that:

The airplane is equipped with a high pressure, gaseous oxygen system which provides supplemental breathing oxygen to the crew and passengers in the event of cabin depressurization during high altitude operation, or in the event cabin air becomes contaminated. The system will provide oxygen for sufficient time to permit a planned descent to an altitude where supplemental oxygen is no longer required.

Aviator’s dry breathing oxygen[46] is stored in a cylinder located in the rear fuselage and, when full, can supply oxygen to 3 people for about 29 minutes. The passenger oxygen system switch (Figure A6) is recessed into the sidewall on the right side of the cockpit, alongside a cylinder pressure gauge for the aircraft oxygen system.

Figure A6: VH-HPY cockpit oxygen gauge and passenger oxygen switch

Figure A6: VH-HPY cockpit oxygen gauge and passenger oxygen switch

Note: Image captured prior to accident. Source: Cameron Marchant annotated by the ATSB

Crew oxygen masks

The pilot and copilot oxygen masks are designed for rapid donning and are positioned on hooks immediately behind the pilot and co-pilot seats for ease of access. The masks incorporate a diluter control, a purge control, a flow indicator, and a microphone for radio communications (Figure A7).

Figure A7: Crew and passenger oxygen masks

Figure A7: Crew and passenger oxygen masks

Source: Ontic, annotated by the ATSB

When required in an emergency, and if the aircraft is operating below 20,000 ft, the oxygen mask diluter control is selected by the pilot to the normal position. Oxygen flows to the mask on demand (when the wearer inhales) and is mixed with cabin air. The flow of oxygen stops when the wearer exhales. The dilution of oxygen with cabin air helps to conserve stored oxygen.

When required in an emergency, and if the aircraft is operating above 20,000 ft, the oxygen mask diluter control is selected by the pilot to the 100% position. Oxygen flows to the mask on demand (when the wearer inhales) at a 100% concentration. The flow of oxygen stops when the wearer exhales.

The oxygen inlet line to the mask has a flow indicator, which is green when oxygen is flowing and red when there is no flow. The oxygen inlet lines are attached to the aircraft oxygen system via a coupling. When the aircraft is not flying, the mask oxygen inlet line couplings are disconnected to prevent possible leakage, and the passenger oxygen system switched off at the passenger oxygen system control panel.

Passenger oxygen masks

Passenger oxygen masks are stowed in containers at various locations in the cabin lining above the passenger seats. The mask assemblies consist of a mask cup, a bag that incorporates a flow indicator, and a lanyard which is attached to a pin.

The passenger oxygen switch has 3 positions – OFF, AUTO, and ON. When the switch is selected to AUTO, and when the cabin altitude reaches 11,000 (±500) ft, the passenger oxygen masks will drop from their containers and the oxygen lines to them will become pressurised. When selected ON, and regardless of cabin altitude, the passenger oxygen masks will drop from their containers and the oxygen lines to them will be pressurised. 

After dropping from their containers, the passenger masks are suspended by their lanyard. When a passenger dons their mask, this action pulls on the lanyard, and thereby the pin, which initiates a constant flow of oxygen to the mask. The flow of oxygen shuts off automatically when the cabin altitude decreases to 8,000–10,000 ft. Selecting the passenger oxygen switch to OFF also shuts off the flow of oxygen.

Oxygen system servicing and duration

When required, aircraft oxygen cylinders are serviced (refilled) with aviator’s dry breathing oxygen by trained personnel using specialist equipment. The aircraft cylinder is full when filled to 1,800 psi. 

The Gulfstream 695A POH provides a table to calculate the duration of on-board oxygen, should it be required in an emergency (Figure A8). Duration is calculated by determining the oxygen cylinder pressure and the number of people on board the aircraft. The duration of on-board oxygen with 3 people on board and with a full oxygen cylinder should be just over 29 minutes.

Figure A8: Oxygen system duration table

Figure A8: Oxygen system duration table

Source: Ontic, annotated by the ATSB

Autopilot

The autopilot fitted to VH-HPY was a Collins AP-106 and it was integrated with the aircraft’s instruments. The Collins AP-106 is a 3-axis system that stabilises the aircraft about its roll, pitch, and yaw axes. The autopilot roll servo acts on the aircraft’s ailerons, a pitch servo acts on the aircraft’s elevators, and an additional pitch servo provides a trim function. A servo acts on the rudder for yaw dampening[47] which can be operated independently of the autopilot.

The autopilot operates in its ‘attitude’ function when engaged and no mode is selected. This function incorporates a pitch hold mode. The autopilot operates in its ‘guidance’ function when engaged and a mode is selected on the mode control panel, which is located on the centre pedestal below the pressurisation controls. Heading (HDG), navigation (NAV), approach (APP), and back-course (B/C) are lateral modes that receive commands from the aircraft’s instruments. Altitude (ALT) and indicated airspeed (IAS) are vertical modes and are used to hold a selected altitude or airspeed. A pitch hold mode is operational when no vertical modes are selected. The autopilot can be biased manually via a control adjacent to the mode control panel. 

Both pilot and co-pilot control wheels have thumb-operated buttons that interrupt the autopilot when pressed to allow the aircraft to be hand flown. Both control wheels have autopilot release switches, and the pilot control wheel has a thumb-operated pitch trim switch.

A subcomponent of the autopilot system, the trim servo monitor, has fault detection and diagnostic capabilities that automatically disengage the autopilot if a discrepancy or malfunction is detected. One such potential fault condition is the exceedance of threshold voltages within a servo as it works against an aerodynamic or mechanical force. 

Appendix B – Transcript – Telephone call between Airservices Australia personnel and the AGAIR head of flying operations

Elapsed timeIndividualAudio details
00:00:02

AGAIR HOFO

ATMD

Hello [HOFO’s name], speaking.

G'day [HOFO’s name], my name is [ATMD’s name] I'm with the Air Services Australia air traffic Control.

00:00:09

AGAIR HOFO

ATMD

Oh yes.

I'm up in Brisbane.

00:00:11ATMDIs Birddog 370 as in HPY one of yours?
00:00:16AGAIR HOFOYes.
00:00:18ATMDOK, just be advised, we finally got comms with [the] aircraft. The aircraft was subject to uncertainty phase.
00:00:24ATMDThe aircraft is up at FL290. There's a suspicion that the aircraft or the pilot may be succumbing or be under lack of oxygen, hypoxic at this time. We've just got a response from a third party. We are. We have attempted to get phone messages, voice.
00:00:46ATMD

He did respond at one stage. He did respond to a frequency to call. We're just trying to ascertain whether his status because he was out of comms. But just stand by one. 

[AGAIR HOFO placed on hold]

00:00:58AGAIR HOFOYes, yeah. 
00:01:14AGAIR HOFO[Expletive]. [Expletive]. What are these [unintelligible] doing. This is not good. [Expletive]
00:02:05ATMDAll right, we've got the pilot back. He umm, actually went to alert, ahh, a SAR phase, but he seems to now to be umm coherent with the controller and just requesting to continue on with his air work. So we're just trying to ascertain why he was out of comms and ahh his lack of responses. So just hang on a sec. I’ll. Standby.
00:02:29

Unknown

Unknown

Unknown

I’ve got the C [statement stops].

Yeah.

Okay.

00:02:38Shift managerHey, is this [HOFO’s name]?
00:02:39AGAIR HOFOYeah.
00:02:40Shift manager

Hello, it's [shift manager’s name]. I'm the duty shift manager. I'll just give you a quick rundown where we got to with Birddog 370.

So we did just put an alert phase on it after it firstly didn't acknowledge a frequency transfer. Went for half an hour of us trying to get hold of the aircraft then drifted off route and when we tried phoning on a mobile phone there was quite a slow response to it.

So we we were just concerned there might be an oxygen issue in the aircraft. So we issued an an oxygen alert and told the aircraft to descend and have subsequently established contact through it relayed by another aircraft and confirmed ops normal.

00:03:15

Shift manager

AGAIR HOFO

So we've cancelled all our phases and happy the aircraft is safe.

Right. Okay, yes, look, thanks for err, I'm just, I'm just having a look on my tracking information now. Err, I see there he's tracking at 290. Ummm.

00:03:32Shift managerThey're currently at flight level 280.
00:03:39AGAIR HOFOTwo, yeah. Two eight, I got GPS altitude.
00:03:41Shift managerYeah, yeah.
00:03:43AGAIR HOFOErr, track looks normal to me.
00:03:45Shift manager

Yeah it does it. However what we saw maybe 10 minutes ago is it began diverging from route for a while just after we'd made a phone call where the the speech perhaps what [?] mobile phone in the aeroplane but the person on that phone call didn't think their speech sounded quite right.

So all those things combined together caused us some concern that we figured the safest thing to do is to try and get the aircraft to descend if it responded, it obviously didn't hear us anyway, but we subsequently we're happy that it's safe.

00:04:17AGAIR HOFOOkay, yeah, look, thanks. Thanks for keeping me informed on that. But is that a, is that an area where you have experienced comms issues?
00:04:26Shift manager

Not, not in particular. I think it was just a a frequency transfer that didn't end up going right, which on it's own, we'd just sit there and watch it because we could see it in ADSB coverage. So we knew the aircraft was flying.

But it's just when those other things began adding to it, each of which on its own is not necessarily a giant thing with the combination of them, we just figure, it's better to be more suspicious than be wondering afterwards.

00:04:54AGAIR HOFOYeah, No, absolutely. Yeah, yeah, absolutely. And thank you for for alerting me as well. But yeah, like, I've got GPS tracking on the aircraft and I can, I can see from what I can see, operations look normal. But I understand exactly what you're saying.
00:05:15Shift manager

Yeah. Yeah. And the thing, you know, The thing is, guess if the aircraft's on autopilot and there's been an oxygen issue, it would look exactly like that for the next, you know, until it got to Mount Isa.

So.

00:05:22AGAIR HOFO

Yeah. Well, exactly. Yeah. Yes. But no.

Well, anyway, if you've if you've reestablished communication and things sound normal, well, that's a yeah.

00:05:31Shift managerLook, we've had it relayed through a military transport that's a couple of hundred miles away and that they're happy that they've got an ops normal call from the aircraft. And we believe this reestablished contact direct with our controller. So, yeah, so we're happy and we've cancelled all the phases.
00:05:46AGAIR HOFOOkay, Thank you. Thank you for that.
00:05:48Shift managerOkay. Thank you, [HOFO’s name].
00:05:49Shift manager Bye. bye
00:05:49AGAIR HOFOOkay, bye, bye.

Source: Airservices Australia

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

[2]      A photographic technique that used a specialised camera system to capture images of the ground for purpose of fire detection, monitoring and mapping which was an aerial work operation under CASR Part 138.

[3]      Flight level: at altitudes above 10,000 ft in Australia, an aircraft’s height above mean sea level is referred to as a flight level (FL). FL370 equates to 37,000 ft.

[4]      Uncertainty phase (INCERFA): an emergency phase declared by the air traffic services (ATS) when uncertainty exists as to the safety of an aircraft and its occupants.

[5]      Alert Phase (ALERFA): an emergency phase declared by the air traffic services when apprehension exists as to the safety of the aircraft and its occupants.

[6]      True airspeed (KTAS): the aircraft’s true speed though the air. This can be calculated/estimated from groundspeed by correcting for actual/forecast wind speed and direction.

[7]      Directions given are from a top-down perspective.

[8]      Aerodynamic spin: sustained spiral descent of a fixed-wing aircraft, with the wing’s angle of attack beyond the stall angle.

[9]      Military training that uses a hypobaric chamber to aid with the recognition of altitude hypoxia symptoms. 

[10]    The original Sundstrand system was replaced with an Enviro system.

[11]    A supplemental type certificate (STC) authorises alteration to an aircraft, engine, or other item operating under an approved type certificate for the state of manufacture.

[12]    The birddog is an intelligence-gathering aircraft, used to assess the fireground, determine the best flight path and then lead the air tankers across the fireground and show them where to drop with a smoke generator. It is crewed by a birddog pilot and air attack supervisor.

[13]    Engineering orders are documents that detail modifications, production of parts, or design changes to aircraft and are approved by authorised persons.

[14]    Maintenance release: an official document, issued by an authorised person as described in Regulations, which is required to be carried on an aircraft as an ongoing record of its time in service (TIS) and airworthiness status. Subject to conditions, a maintenance release is valid for a set period, generally 100 or 150 hours TIS or 12 months from issue.

[15]    System specifications for the Gulfstream 695A changed as the aircraft was produced and the specification of any given aircraft is identified by its serial number. This section describes the system specifications for VH-HPY.

[16]    A pressurisation cycle is one complete sequence of pressurising an aircraft.

[17]    For the Gulfstream 695A this is known as a minimum required equipment list (MREL).

[18]    The MEL for VH-HPY had been approved for AGAIR Logistics as the registered operator, and at the time of the accident the aircraft was being operated by AGAIR Pty Ltd.

[19]    Grid point wind and temperature and SIGWX charts.

[20]    A receiver/transmitter which transmits an automatic reply upon receiving an interrogation request.

[21]    A real-time GPS tracking and data reporting system.

[22]    Airservices Australia systems utilised the ADS-B pressure altitude data to display aircraft level information to air traffic controllers.

[23]    Speed definitions:

  • Groundspeed – is the aircraft's speed across or relative to the ground and has been derived from GPS based position and time.
  • True airspeed – is the aircraft’s true speed through the air. This can be calculated/estimated from groundspeed by correcting for actual/forecast wind speed and direction.
  • Calibrated airspeed – is the aircraft’s speed through the air once non-standard atmosphere (or atmosphere of the day) effects are applied to true airspeed. For high-speed aircraft (> Mach 0.5) this also includes applying air compressibility effects. Calibrated airspeed determines the aircraft’s flight and engine performance.

[24]    VMCA: Minimum control (in the air) airspeed below which, with one engine inoperative and the other engine/s at MCP and the aircraft banked at 5° away from the inoperative engine, directional control of the aeroplane can no longer be maintained. 

[25]    Angle of attack: the acute angle between the chord line of the airfoil and the direction of the relative airflow.

[26]    A crew member who is a pilot or flight engineer assigned to carry out duties essential to the operation of an aircraft during flight time. 

[27]    Area of the Earth’s surface imaged by the camera sensor. 

[28]    The HOFO last flew VH-HPY as pilot in command on 18 August 2023.

[29]    Angle of attack: the acute angle between the chord line of the airfoil and the direction of the relative wind.

[30]    Critical angle of attack: the angle of attack at which a wing stalls regardless of airspeed, flight attitude, or weight.

[31]    Some measures had less samples - Response time to ATC transmissions had 3 samples.

[32]    Some measures had less samples - Response time to ATC transmissions had 14 samples, time from the commencement of transmission to the commencement of speech had 18 samples, and fundamental frequency had 16 samples.

[33]    Statistically significant t(14) = 2.09, p<0.05.

[34]    Statistically significant t(23) = 1.51, p < 0.05.

[35]    There were also 3 cases at higher altitudes where the pilot appeared to be late at keying the microphone after they had already begun to speak. 

[36]    The difference was not statistically significant.

[37]    Statistically significant t(18) = 3.50, p<0.01.

[38]    The Manual of Air Traffic Services is a joint document of Defence and Airservices and is based on the rules published in Civil Aviation Safety Regulations Part 172 – Manual of Standards and International Civil Aviation Organization standards and recommended practices, combined with rules specified by Airservices and Defence.

[39]    The holder of an authorisation under the Civil Aviation Act 1988 or the associated aviation regulations to undertake a particular activity (for example aircraft operators and maintenance providers).

[40]    The NSW Rural Fire Service (NSW RFS) was a large volunteer fire service. The members provide fire and emergency services to approximately 95 percent of NSW.

[41]    AGAIR was the registered operator of VH-LVG, but not VH-CLT. The registered operator was responsible for the continuing airworthiness and maintenance control of the aircraft.

[42]    Both aircraft types are in the same family as VH-HPY (a Gulfstream 695A).

[43]    In May 2019, the maintenance release for VH‑LVG was valid between September 2018–September 2019 and had about 28 flying hours remaining.

[44]    With regard to this observation, the surveillance report stated: ‘Several aircraft are leased to the AOC and have cross hire agreements in place. On review of the agreements they lack clarity on the airworthiness responsibilities managed by the HAAMC. A more airworthiness focused contractual agreement would ensure each aspect of the continuing airworthiness has clearly assigned responsibilities.’

[45]    This model of aircraft did not have master warning lights, which are common on other aircraft types and were fitted to later model Gulfstream 695A aircraft.

[46]    Aviator’s dry breathing oxygen is manufactured to strict specifications for use in aircraft and cannot be substituted with other types (such as medical or industrial grade oxygen).

[47]    A yaw damper is a device that applies rudder correction in order to reduce the lateral oscillations of an aircraft motion, with both rolling and yawing components (Dutch roll).

Preliminary report

Report release date: 07/02/2024

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 4 November 2023, a Gulfstream 695A, registered VH-HPY, was being operated by AGAIR on an instrument flight rules[1] flight from Toowoomba, Queensland to Mount Isa. On board the aircraft were the pilot and 2 camera operators. The purpose of the flight was to conduct aerial photography of fire zones located north of Mount Isa. The flight had been contracted by Queensland Fire and Emergency Services and was conducted as an aerial work operation.

At about 1055 local time, the aircraft departed Toowoomba Airport. The pilot was provided with an air traffic control clearance to track to Mount Isa. They were initially cleared to climb to flight level[2] (FL) 160, and then were issued further instructions to continue the climb to the planned cruise of FL 280. The pilot made a brief personal phone call at about 1106, and the aircraft reached FL 280 at 1120:30 (Figure 1).

Figure 1: Flight path overview

Figure 1: Flight path overview

Source: Google Earth, annotated by the ATSB

At 1141:12, the pilot contacted the controller and requested clearance to descend to FL 150. The requested clearance was provided and, a short time later, the aircraft started to descend. The initial rate of descent reached about 3,900 feet per minute (ft/m), but this slowed as the aircraft continued to descend. At 1151:49, the aircraft levelled off at FL 150. At 1157:43, the pilot contacted the controller again and requested clearance to climb back to FL 280, which was approved. Shortly after, the aircraft began to climb.

At 1210:19, the flight was transferred to, and the pilot established radio communication with, the controller responsible for the Simpson region[3] on a frequency of 126.0 MHz. The pilot reported to the controller that the aircraft was on climb to FL 280. At 1221:49, the aircraft levelled off at FL 280.

At 1245:51, the controller requested the pilot change frequency to 122.1 MHz, to maintain radio contact within range of ground equipment. This change was acknowledged by the pilot, but the Simpson region controller did not receive radio communications from the flight on the newly assigned frequency.

Between 1247:51 and 1340:15 the Simpson region controller made 15 separate radio broadcasts attempting to re-establish radio communication with the pilot. The controller also attempted to contact the pilot on HF (high frequency) radio and by relaying messages via other aircraft that were operating in the same area as VH-HPY.

At 1318:20, the controller declared an uncertainty phase (INCERFA)[4] for the aircraft.

At 1341:31, the pilot called the Simpson region controller on 122.1 MHz, providing callsign, flight level and radio frequency, but the controller was unable to re-establish two-way communications. Between 1341:31 and 1350:51 the controller continued attempts to contact the pilot. This included further attempted communication relays via aircraft in the vicinity of VH-HPY on various frequencies including the international air distress frequency of 121.5 MHz. At 1350:51 a crewmember on board a Royal Australian Air Force (RAAF) Alenia C-27J Spartan aircraft was able to establish contact with the pilot on 118.6 MHz.

At 1351:08, the controller requested that the RAAF crewmember instruct the pilot to call them on 123.95 MHz. At 1351:59, the controller re-established radio communications with the pilot of VH‑HPY on this frequency. The pilot confirmed the aircraft was maintaining FL 280 and was ‘ops normal’. Between 1352:08 and 1357:34 several communications took place between the controller and the pilot during which the pilot advised the aircraft’s oxygen system was operating normally. The pilot informed the controller that the aircraft was tracking direct to Cloncurry and then on to an area near Mount Gordon to undertake airwork.

At 1357:34, the pilot was provided with an air traffic control clearance to undertake operations near Mount Gordon. Between 1357:43 and 1401:36 the pilot repeated the clearance from the controller 4 times, seeming uncertain about the status of the clearance. Although a formal speech analysis has not been undertaken at this stage, radio recordings during this period indicate that the pilot’s rate and volume of speech had substantially lowered from earlier communications and was worsening. During the last radio transmission, which commenced at 1401:23, the pilot seemingly had difficulty pronouncing the location ‘Cloncurry’ and they incorrectly stated the airwork would take place near ‘Mount Ball’, which was then corrected to ‘Gordon’.

At 1419:22, the controller requested the pilot change frequency to 122.4 MHz, but no response was received. Between 1420:05 and 1427:20 the controller attempted to contact the pilot 8 times without receiving a response.

The aircraft was not fitted with a cockpit voice recorder or flight data recorder. However, flight data was transmitted to ground stations by aircraft/navigational equipment (see Recorded information). This data indicated that at 1420:50 the aircraft’s groundspeed began to reduce from a cruise groundspeed of about 225 kt (417 km/h), while heading and altitude remained steady. At 1425:25, the groundspeed had decreased to about 104 kt (193 km/h) and the aircraft departed controlled flight. The aircraft initially entered a descending anticlockwise[5] turn with an increasing rate of descent. At an altitude of about 10,000 ft, the aircraft transitioned into a tight clockwise helical descent, likely an aerodynamic spin,[6] with a subsequent average rate of descent of about 13,500 ft/m (Figure 2).

Figure 2: Oblique view of the aircraft’s flight path during the descent from FL 280

Figure 2: Oblique view of the aircraft’s flight path during the descent from FL 280

Source: Google Earth, annotated by the ATSB

Two witnesses at a nearby mining facility observed the aircraft’s descent and described hearing a ‘whirring’ noise and seeing it descending in a nose-down clockwise corkscrew motion. The witnesses recalled the aircraft’s motion momentarily abated partway down, before it re-entered the nose-down corkscrew descent.

At about 1427:20, the aircraft collided with terrain 30 NM (56 km) south-east of Cloncurry. The 3 occupants were fatally injured, and the aircraft was destroyed by impact forces and a fuel-fed post-impact fire.

Context

Pilot information

The pilot held a valid class 1 aviation medical certificate and an air transport pilot licence (aeroplane). At the time of the accident, the pilot had about 4,800 hours total aeronautical experience. This included about 3,200 hours operating turbine/jet aircraft including the Beechcraft B200, Learjet L35/36, and several high-performance military aircraft.  The pilot commenced employment with the aircraft operator in September 2023.

Camera operator information

Camera operator 1 joined the aircraft operator in July 2021. They were not employed as a pilot by the organisation, but held a valid class 1 aviation medical certificate and commercial pilot licence (aeroplane). At the time of the accident, they had about 434 hours total aeronautical experience, including 72 hours on multi-engine piston aircraft. The ATSB has not yet determined whether camera operator 1 was in the second pilot’s seat at the time of the accident.

Camera operator 2 was a United States citizen who had experience in the construction and operation of the imaging system. They joined the aircraft operator in October 2023.

Aircraft information

The Gulfstream 695A is a high-wing, pressurised, twin-engine aircraft powered by 2 Garrett TPE331-10-511K turboprop engines, and is fitted with a system to provide oxygen to the occupants in the event of a depressurisation at high altitudes. The aircraft was designed as a business and personal aircraft with seating capacity of up to 11 depending on configuration. The aircraft, serial number 96051, was manufactured in 1982 and first registered in Australia as VH‑HPY on 11 November 2014. Its registration was held by AGAIR from 14 September 2016.

In 2021, VH-HPY was fitted with a long-wave infrared imaging system to carry out aerial photography of fire zones.

The aircraft’s most recent scheduled maintenance was completed on 1 November 2023, and at that time it had accrued 7,566.1 hours total time in service. Work carried out included the 150 hourly inspection and the rectification of minor defects.

Site and wreckage information

The ATSB conducted an on-site examination of the aircraft wreckage. The aircraft came to rest in flat, open bushland and was destroyed by a significant post-impact fire (Figure 3). The post‑impact fire damage limited the extent to which pre-impact defects could be identified, however from the evidence available:

  • all major aircraft components were accounted for at the point of impact
  • the impact marks and wreckage position indicated that the aircraft impacted terrain upright with a shallow, nose down attitude and with little forward momentum, indicative of a spin
  • both engines and propellers had indications that the engines were running at impact.

It was not possible to determine the operability of the aircraft’s pressurisation and oxygen systems.

Figure 3: Overview of the accident site

Figure 3: Overview of the accident site

Source: Queensland Police, annotated by the ATSB

Weather information

Preliminary examination of meteorological records for the accident area indicated that the conditions present at FL 280 at the time of the accident were likely a westerly wind at 40 kt, with no significant weather events nearby.

At 1430, about 3 minutes after the aircraft collided with terrain, the Bureau of Meteorology (BoM) automatic weather station at Cloncurry, 56 km north-west of the collision location, recorded the surface wind as 6 KT from 190° true, visibility greater than 10 km, no detected cloud, temperature 40°, dew point 2°, and no rainfall since 0900 local time.

Recorded information

During the flight, data was being transmitted by the aircraft’s automatic dependent surveillance broadcast (ADS-B) equipment. This data, recorded at intervals of less than 1 second, captured the aircraft’s position and altitude shortly after departure from Toowoomba until the aircraft had descended to about FL 240 during its final descent. Flight data was also being transmitted from a navigational application on a tablet onboard the aircraft. From 1346:01 to 1427:15 this data, recorded at 5-second intervals, captured the aircraft’s position, altitude, groundspeed and heading.

All radio communications made and received by Airservices Australia throughout the entirety of VH-HPY’s flight were recorded.

A Garmin GTN-750 navigation system was recovered from the accident site and transported to the ATSB’s Canberra technical facility. Examination of the unit indicated that it was not recording flight data.

Further investigation

To date, the ATSB has:

  • examined the wreckage and accident site
  • examined the Garmin GTN750 navigation system recovered from the accident site
  • interviewed relevant parties
  • collected radio communication, aircraft traffic surveillance data, and navigational application data
  • collected aircraft, pilot, crew and operator documentation.

The investigation is continuing and will include further analysis of:

  • the pilot’s speech during radio communications, including an examination of hypoxia indicators[7]
  • meteorological information
  • maintenance records, including those of the aircraft’s pressurisation and oxygen systems, and airworthiness procedures
  • operational procedures and documentation
  • flight data and air traffic surveillance data
  • pilot and crew training and medical records.

A final report will be released at the conclusion of the investigation. 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.

Acknowledgement

The ATSB would like to acknowledge the significant assistance provided by the Queensland Police Service 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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

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

[2] At altitudes above 10,000 ft in Australia, an aircraft’s height above mean sea level is referred to as a flight level (FL). FL 280 equates to 28,000 ft.

[3] An area covering the central and western parts of Queensland.

[4] A situation where uncertainty exists as to the safety of an aircraft and its occupants. In this instance, an uncertainty phase is declared when a pilot fails to report to air traffic control 30 minutes after a frequency change.

[5] Directions given are from a top-down perspective.

[6] A sustained spiral descent of a fixed-wing aircraft, with the wing’s angle of attack beyond the stall angle.

[7] Hypoxia is the result of a lack of oxygen to the body tissues. The most common type of hypoxia in aviation is altitude (hypobaric) hypoxia, which can be prevented by pressurising the aircraft or by breathing supplemental oxygen. Symptoms can be insidious and include sleepiness, drowsiness, slurred and slowed speech, confusion, and impaired cognition and decision making.

Occurrence summary

Investigation number AO-2023-053
Occurrence date 04/11/2023
Location 55 km south-east of Cloncurry Airport
State Queensland
Report release date 19/06/2025
Report status Final
Investigation level Systemic
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Flight crew incapacitation, Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Gulfstream Aerospace Corp
Model 695A
Registration VH-HPY
Serial number 96051
Aircraft operator AGAIR Pty Ltd
Sector Turboprop
Operation type Part 138 Aerial work operations
Departure point Toowoomba Airport, Queensland
Destination Mount Isa Airport, Queensland
Damage Destroyed