Collision with terrain

Collision with terrain at night involving Robinson R22 Beta II, VH-LYD, 25 km south-south-east of Kowanyama, Queensland, on 9 October 2025

Final report

Report release date: 06/05/2026

Investigation summary

What happened

On the evening of 9 October 2025, a Robinson R22 Beta II helicopter, registered VH‑LYD, was being operated by MDH Pty Ltd (MDH) 25 km south-south‑east of Kowanyama, Queensland. 

The helicopter left Rutland Plains at around 1845 to guide ground vehicles tackling a bushfire. At around 1920 the pilot told the ground crew that it was getting too dark and set off to return to Rutland Plains Station. 

Staff at the station lit the helipad for the arrival of the pilot. When the pilot did not return to the station, staff raised the alarm. 

The following morning, the helicopter wreckage was found. The helicopter had collided with terrain. The pilot of VH-LYD was fatally injured in the accident, and the helicopter was destroyed.

What the ATSB found

The ATSB found that the pilot operated the helicopter at night. The helicopter was not equipped, and the pilot was unqualified, for flight at night. However, it was normal for company R22 pilots to exceed the limits of last light. 

Instead of observing the legal limits, pilots chose their own limits, despite none of the company’s R22 pilots being qualified for night flight and none of its R22 helicopters being equipped for night flight. ATSB analysis of historical flight tracking data showed that on 39 occasions in the previous 6 months MDH pilots had flown beyond the legal minimums into night. Flying after last light was a tolerated and unmanaged risk on MDH properties.

In addition, the ATSB found that MDH did not require pilots to formally assess risk and did not provide tools or training to do so. This limited the ability of the company and its pilots to identify and understand operational hazards and their consequences.

What has been done as a result

MDH now requires its pilots to determine the official time of last light and has made it a clear responsibility of the pilot and the station manager to ensure aircraft are on the ground before last light. 

Additionally, pre-flight planning now includes consideration of fatigue, including rest and duty times, and consideration of risk assessment criteria.

MDH has also implemented a pilot mentoring scheme to assist, mentor and supervise MDH pilots during aerial mustering operations. This includes a pre-season low level risk assessment and standardised mustering workshop, the first of which took place in March 2026.

Safety message

This accident is the fourth fatal accident of this type in the last 5 years. Flying after last light without appropriate equipment and qualifications is an unsafe practice. The acceptance of this activity is leading pilots to fatal accidents.

The ATSB’s Avoidable Accidents No 7 - Visual flight at night accidents provides further discussion about these practices and how they have contributed to accidents. The requirement to operate under daylight conditions, and plan to land 10 minutes before last light, provides a reliable method for ensuring there are sufficient external visual references available to safely operate an aircraft. 

Pilots and the companies or landowners they work for, or contract to, must work together to avoid flight at night by unqualified, unequipped pilots. Development of risk management practices in any organisation should be an ongoing activity. It should develop an ability across all parties to document operational risks and codify learnings from operations.

 

The occurrence

On the evening of 9 October 2025, a Robinson R22 Beta II helicopter, registered VH‑LYD, was being operated by MDH Pty Ltd (MDH) at Rutland Plains, a cattle property in northern Queensland on the Gulf of Carpentaria (Figure 1). 

Figure 1: Area of operation

A satellite view showing the location of Rutland Plains on the Gulf of Carpentaria.

Source: Queensland Globe

The pilot started the day’s flying just after 0600, aerial mustering in an area about 40 km south‑west of another company‑owned property, Dunbar Station, Queensland. In the afternoon, the pilot travelled to Rutland Plains to collect a colleague and conduct aerial reconnaissance for another muster planned for the following day. After leaving their colleague, the pilot flew to a nearby location to collect parts for equipment needed for the planned muster at Rutland Plains. 

At around 1730, on the way to collect the parts, the pilot spotted a bushfire around 25 km south-south‑east of Rutland Plains station. The pilot advised crew at the station via radio and ground vehicles were dispatched to control the fire. Crew at the station recalled that after returning to Rutland Plains with the parts, the pilot flew to the fire to assist in guiding the ground vehicles through tracks and fences to the flame front. 

The pilot and helicopter were limited to daytime operations. The pilot departed Rutland Plains for the fire at around 1845. The time of last light (the beginning of nighttime) at Rutland Plains on 9 October was 1852. 

At around 1920, the pilot was providing airborne assistance to ground crew controlling the fire. Around that time the pilot announced over the radio that it was getting too dark, and the pilot needed to return to Rutland Plains. Hearing this, the crew at the station lit the helipad with the headlights of a vehicle to assist the pilot on their return. 

At around 1935, crew at the station checked to see if the pilot had landed. Discovering that the helicopter had not returned, they tried contacting the pilot by radio. When radio contact was unsuccessful, they escalated the non-arrival within the company and sought information from a satellite tracking system on board the helicopter to establish its location. Tracking had stopped at 1929 around 7.5 km south-south‑east of the station (Figure 2). 

Figure 2: Fire location and VH-LYD track

Satellite view showing track of VH-LYD to and from the fire ground.

Source: Google Earth, BoM and SPOT Trace tracking data

Station crew conducted a ground search while company management contacted emergency services and the Joint Rescue Coordination Centre. A coordinated air search began just after midnight. 

The following morning, helicopter wreckage was found by a station crew member from Rutland Plains and a helicopter pilot from a neighbouring property. VH-LYD had collided with terrain around 1.5 km north of the last satellite tracking point. The pilot was fatally injured in the accident, and the helicopter was destroyed by impact forces.    

Context

Pilot information

The pilot held a valid Private Pilot Licence (Helicopter) (PPL(H)), which was issued in February 2023 and a mustering endorsement issued in April 2023. The pilot held a class 2 medical certificate which was valid to 31 August 2026.

The pilot commenced work in ground-based cattle operations with MDH Pty Ltd (MDH) in 2017 and transitioned to an aerial mustering role. The pilot had accumulated around 2,000 to 2,500 hours of flight time. 

In November 2024, the pilot attended a Robinson Helicopter Company safety course. On 16 January 2025 they underwent a biannual helicopter flight review. In March 2025 the pilot attended an MDH leadership conference. In June 2025 the pilot completed refresher training and check flights in mustering techniques. There was no record of the pilot being trained or qualified to operate under night visual flight rules (NVFR) [1],[2] (see Night flight regulatory requirements). 

It could not be determined if the pilot experienced a level of fatigue that would have impaired performance or decision‑making at the time of the accident (see Fatigue).

Helicopter information

VH-LYD was a Robinson Helicopter Company R22 Beta II helicopter, serial number 4471 (Figure 3). It was powered by a Textron Lycoming, O-360-J2A, 4-cylinder piston engine. VH-LYD was manufactured in the United States on 12 February 2010 and first registered in Australia on 19 May 2010. It was equipped and maintained to a day VFR standard. Its last 100-hourly maintenance was conducted on 24 September 2025. At the time of the accident VH-LYD had accumulated approximately 14,645 hours total time in service. 

Figure 3: Exemplar Robinson Helicopter Company R22

An R22 helicopter with doors removed flying over wooded terrain.

Note: This exemplar image has been digitally altered by the ATSB. Source: MDH Pty Ltd

The R22 had 2 seats, with the pilot flying from the right seat, and each seat was fitted with a seatbelt and inertia reel shoulder strap. VH-LYD did not have doors fitted at the time of the accident. 

Maintenance records and wreckage inspection both showed that VH-LYD was not equipped with instruments necessary for flight at night (see Night flight regulatory requirements). 

Recorded information

The helicopter 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 transmitted from a SPOT Trace[3] satellite tracking unit fitted to the helicopter, which could be used by MDH personnel to track the location of the helicopter during flight. The unit provided 5-minute time-stamped updates on the helicopter’s location, speed and altitude. The recorded data captured the accident flight until shortly before the impact with terrain.

The SPOT Trace units were fitted to all MDH R22 helicopters, and the ATSB sourced the preceding 6 months of fleet data for analysis purposes. The data covered 596 days of helicopter operation across 4 helicopters (see Night flight data analysis).

Wreckage and impact information

The ATSB did not attend the accident site. The site was mapped, documented and assessed by a team from the forensic crash unit of the Queensland Police Service (QPS). QPS recovered the wreckage of VH-LYD to a secure location in Cairns, Queensland, where it was examined by 2 ATSB investigators. 

Site photographs and wreckage inspection indicate that VH-LYD was moving at high speed, around 90 degrees off track, at the time of the collision with terrain (Figure 4). The helicopter was significantly damaged by tree and ground impacts with the main rotor and transmission assembly separating from the helicopter. There were no pre-accident defects identified, and the engine was driving the main and tail rotor system at the time of the collision. The impact with terrain was not considered to be survivable.

Figure 4: VH-LYD accident site

An R22 helicopter with doors removed flying over wooded terrain.

Source: Queensland Globe, Queensland Police Service, annotated by the ATSB

Meteorological and environmental information

Weather 

A Bureau of Meteorology (BoM) aviation weather forecast for Kowanyama Airport (located around 20 km north‑west of Rutland Plains) for 9 October related the possibility of thunderstorms. Meteorological conditions recorded by the BoM weather station at Kowanyama Airport included distant lightning from around 1530, indicating that thunderstorms were reported within 30 NM (55 km) but not at the airport. Cloud developed through the day, with periods of scattered to broken cloud between 6,000 ft and 9,000 ft. No cloud was detected at Kowanyama Airport at the time of the accident.

No rainfall was detected throughout the day, and the wind had shifted from a variable easterly in the morning to a south-westerly wind of 6 kt from around 1730. Around that time the accident pilot reported to a colleague at Rutland Plains that dry storms[4] were building in the area, and that there was smoke, indicating a bushfire. 

A witness who heard the departure of VH-LYD stated that on last light, shortly after the time the pilot departed Rutland Plains for the fire, cloud covered the area though there was still a visible horizon. 

Light 

The period between sunset[5] and the geometric centre of the Sun’s disk reaching 6° below the horizon is called civil twilight (Figure 5). The end of civil twilight is otherwise known as last light. For aviation purposes last light is the boundary between night and day. The period when the geometric centre of the Sun is between 6° and 12° below the horizon is called nautical twilight. After that time, it is ordinarily, for all practical purposes, dark. This is especially so in areas devoid of artificial lighting.

Figure 5: Limits of day and night relative to the position of the Sun

A graphic showing the limits of day and night as defined by passage of the Sun and specifically its distance below the horizon.

Source: Geoscience Australia, ATSB

The time of last light was readily available for any location in Australia from Airservices Australia’s national aeronautical information processing system (NAIPS). It could also be calculated using tables published in the aeronautical information package (AIP) at GEN Section 2.7 – First light and last light computations(Airservices Australia, 2024) or via Geoscience Australia’s calculator on its website.  

On 9 October 2025 at the location of the accident near Rutland Plains Station, Queensland, sunset was 1831, the end of civil twilight was 1852 and the end of nautical twilight was 1917. Celestial illumination would have been limited by cloud and there was no moonlight as a waning gibbous[6] moon would not rise until 2045. 

Smoke

The 6 kt (10.8 km/h) south-westerly wind, though light, is likely to have kept smoke away from the pilot’s return track to Rutland Plains Station. Moreover, the pilot was unlikely to have approached the fire through smoke, and the pilot departed the fire on a reciprocal track.

Operational information

Operator overview

MDH Pty Ltd was one of Australia’s largest beef cattle operations. It was a family business that owned 14 properties covering 3.36 million hectares. MDH’s aircraft and pilots were spread over Queensland and managed from Brightlands Station just south of Cloncurry, Queensland. 

At the time of the accident MDH owned and operated 4 Robinson R22 helicopters, 1 Robinson R44 helicopter and 6 fixed wing aircraft. It had operated Robinson R22 helicopters since 1985. The chief pilot stated that at the time of the accident none of its R22 helicopters were equipped for night flight.

MDH had 4 helicopter pilots flying the R22s. Three of the pilots had Private Pilot Licences (Helicopter) and one had a Commercial Pilot’s Licence (Helicopter). All were endorsed for low‑level flight and mustering and none held a night visual flight rules rating.[7] 

The helicopters were being operated by paid employees, aerial mustering for commercial beef cattle operations. As the helicopters were company‑owned, and were being operated over private land, those operations were conducted as limited aerial work operations under Part 138 of Civil Aviation Safety Regulations (CASR), which do not require the issue of an aerial work certificate by CASA. Part 91 of the Civil Aviation Safety Regulations (CASR) (2025b) also applied unless a specific requirement of Part 138 disapplied it. This meant MDH had to comply with the requirements of CASR Part 138 with respect to pilot fatigue and risk management of operations.

Operator procedures and oversight

MDH did not have, and was not required to have, a CASR Part 138 aerial work certificate for the R22 operations. Therefore, it was not required to provide the Civil Aviation Safety Authority (CASA) with a complete operations manual covering all requirements of the regulations for its proposed operations.

Instead of an operations manual detailing how operations were to be conducted, MDH had limited manuals and procedures for helicopter operations. An induction handbook for pilots carried information on administration and basic instructions with respect to flight operations. A statement at the head of the document required pilots to observe all applicable laws and rotorcraft flight manual limitations.

Pilots stated that the document matched their operations, and that the expectation of pilots not breaching regulations was observed. MDH held pre-season[8] safety meetings with the pilots. The last was 21 March 2025 in Brightlands. The meetings would cover operational elements, as well as a review of the pilot induction material to refresh procedures.

MDH had a senior pilot who was positioned in the induction handbook as the chief pilot. They were to be contacted for aircraft and pilot issues. The chief pilot stated that oversight of the pilots was conducted, when possible, by the chief pilot or another senior manager, though they were most often not co-located with the pilots.

The chief pilot would roster pilots by date, helicopter and location and build in rest days. They would also ensure that pilots’ tasks remained solely associated with flying. Ordinarily pilots would start at first light, but it was left to the pilots as to when their duty would end. Days rostered were documented and retained by the company, but duty hours worked by pilots were not. 

The chief pilot acknowledged that there were occasions whereby pilots would have to use the helicopter for as long as possible and into twilight. They stated that they expected pilots to minimise their exposure to flight at night by landing near vehicles to get a lift home, or by staying at alternative accommodation. The chief pilot provided an example of setting this expectation to a pilot in mid-August 2025 after they exceeded last light by 35 minutes. 

They also stated that pilots would assess whether there was enough light to continue flight, and the decision was at the sole discretion of the pilot. MDH’s pilots concurred with this, and all stated that the pilot in command was solely responsible for the operation of the helicopter and had final say in all decisions related to the operation of their helicopter. 

There was one mention of daylight in the MDH induction handbook for pilots which concerned ferrying of aircraft. It stated:

A decision has to be made by the pilot if the daylight does not permit making the scheduled property in the afternoon to stay at a property and notify [management] that they did not make it.

Flight at night
Night flight AIP instructions and CASA guidance material

The CASA (2025f) Visual flight rules guide carried information on the regulations and requirements pertaining to night visual flight rules. It was a useful starting point for pilots and operators to ensure night flight was appropriately managed. In addition, advisory circular (AC) 61-05 Night VFR rating (CASA, 2022) was an important supporting document to the regulations and related notable hazards of night flight. 

Untrained (and therefore unauthorised) pilots were not allowed to conduct flight at night. AIP ENR Section 1.2 – Visual Flight Rules, paragraph 1 Flight Rules, sub paragraph 1.1 The Visual Flight Rules (VFR), sub sub paragraph 1.1.2 stated:

1.1.2 Unless the pilot in command is authorised under CASR Part 61 to conduct a flight under the IFR or at night under the VFR and the aircraft is appropriately equipped for flight at night or under the IFR, a VFR flight must not be conducted at night.

The appropriate equipment mentioned was listed in CASR Part 91 manual of standards (MOS) (CASA, 2021). This included specific equipment such as:

  • equipment for displaying the rotorcraft’s attitude
  • radio communications system equipment
  • navigation systems equipment, such as an approved GNSS
  • navigation and cockpit lighting.

Furthermore, there were rules about fuel reserves, alternate aerodromes, and calculating and flying above lowest safe altitudes. Additionally, AC 139.R-01 v3.1 (CASA, 2024a) carried guidelines for helipad dimensions and markings for night operations which were in excess of those required for operations by day.

AIP ENR Section 1.2 – Visual Flight Rules, paragraph 1 Flight Rules, sub paragraph 1.1 The Visual Flight Rules (VFR), sub sub paragraph 1.1.3 stated:

1.1.3 For pilots not authorised to fly at night, it is recommended that they plan to arrive at the later of the destination aerodrome or alternate aerodrome at least 10 minutes before last light (allowing for any required holding).

The AIP instructions and associated CASA guidance material clearly indicate that the regulations precluded an untrained or unequipped pilot from flying at night. Additionally. there was a clear intention that pilots aim to land at least 10 minutes before last light (10 minutes before end of civil twilight). 

Operator’s night flight practices

The ATSB interviewed 3 company R22 pilots and the chief pilot about practices related to night flight. 

MDH did not roster pilots to fly after last light. To do so was against regulations. However, pilots reported that the requirement to land before last light was not always observed. They stated that while they would not plan to land after last light, at times, operational needs led them to do so. 

On occasion, depending on the location and behaviour of the cattle, a muster could take longer than planned. In some locations where a holding yard was available, it was possible to re-plan and stop work without losing effort. Additionally, the option existed to land at the yards and return to the station in a vehicle rather than flying back to a station in fading light. However, that could delay the start of the following day’s muster and leave less time to manage overruns the next day.

In locations where cattle could not be held, ending the job before cattle were yarded up could lead to the loss of a day’s work. While there was no reported pressure on pilots to continue, pilots reported that they would do so rather than undo a day’s work. Exceeding last light was an accepted part of operations and pilots could make their own decisions about whether the light remaining was enough to finish the job and fly home. 

The actual time of last light and 10-minute buffer was not used in pilot assessments, and pilots did not use the time of last light to delineate between night and day. Instead, pilots would weigh environmental factors such as sunset, cloud and available horizon against their own tolerance for risk. The distinction became one between dark with a discernible horizon and fully dark.

From time-to-time emergencies, such as fires, could crop up and require input or oversight from a pilot in a helicopter. There was no expectation on the part of MDH that pilots would fly after last light, no matter the reason. At the same time, it was reported that in an environment where the pilots were most often unsupervised, no-one would prevent a pilot from doing so. Individual accountability in pilot decision‑making was reported to be the only determining factor.

Night flight data analysis

The SPOT Trace data for MDH’s 4 R22 helicopters for the 6 months preceding the accident was analysed by the ATSB to identify night flight practices. The data was pruned to remove any points that did not indicate flight, then differenced with the time of civil twilight for that location. Matches close to last light were further refined by measuring the distance to the next spot and calculating time available to destination.

The tracking data (Figure 6) showed that in the 6 months preceding the accident, the 4 company helicopters operated on 596 days. Of the 596 days of operation, company helicopters were flown after last light on 39 occasions, around 6.5% of days of operation across the 4 helicopters. The level of exceedance ranged from under a minute up to 1 hour 34 minutes, with the average exceedance being 17 minutes. Eight of the late flights, including the accident flight, extended beyond nautical twilight. 

Figure 6: Latest time flown after last light for 39 flights in company R22 helicopters

Latest time flown after last light for 39 flights in company R22 helicopters

Source: SPOT Trace data

The largest exceedance of around 1 hour 34 minutes after last light took place in July 2025 in the vicinity of Mount Windsor Station, Queensland. While cloud cover is not known, the moon rose at 1404 and was approaching three quarters full at an altitude of 70° when the helicopter landed. 

Operational risk management
Risk management regulatory requirements

MDH, as a limited aerial work operator, was required to comply with CASR 138.370 which required risk assessment and mitigation. 

MDH had to ensure that, before beginning a task, a pilot had assessed the risk of an operation (Part 138 MOS 13.05). The pilot had to ensure that the operation could be conducted without unacceptable safety risk (Part 138 MOS 13.02). 

Part 138 MOS at 13.04 instructed pilots to take specific notice of:

(a) the operation and its particular characteristics;

(b) the location of the operation and its particular characteristics;

(c) the aircraft to be used in the operation, its particular characteristics, and its performance;

(d) the qualifications and experience of the crew members to be used in the operation;

(e) the hazards, external to the aircraft, that may be met in the course of the operation.

Advice on risk management was available to operators in AC 138-05 v3.0 Aerial work risk management (2025a). It stated:

For limited aerial work operations, a risk assessment and mitigation process must be undertaken by the pilot in command (PIC) before an operation is conducted… 

It is incumbent upon the operator … to ensure these procedures are carried out.

Annex A to AC 138-05 v3.0 was titled Sample risk assessment process - limited aerial work operator. It explained how to implement risk management to meet the requirements of the Part 138 Manual of Standards.

Operator’s risk management practices

MDH’s primary use of helicopters was aerial mustering. This activity was supported by training and operational documents. MDH provided training in aircraft knowledge, operational techniques and safety, which was suitable for conduct of its operations.

It had also outlined a pre-mustering assessment which pilots could use to discuss and manage mustering operations. The document contained some collected knowledge of hazards and prompts to identify powerlines and brief ground crew on safety around helicopters. However, it was essentially a task management document and did not address identification and management of risk. 

The flight planning section of the pilot induction handbook also prompted identification of threats with respect to reconnaissance of known local hazards such as powerlines and dead trees. While this applied to managing safety during a flight, it did not constitute risk management. Risk management was where a pilot and organisation could decide if an operation could be conducted within the organisation’s safety performance criteria (CASA, 2025d).   

The pilot induction handbook also contained a section called risk management which was a high-level outline of the pilots’ responsibilities with respect to weather, fatigue, mustering, aircraft handling, and sightseeing. It outlined some associated hazards but did not discuss risk management as an activity and no risk management plans were present. Specifically, there were no defined limits or organisational tolerance for risk. Additionally, there were no apparent tools or support for company pilots to formally identify and manage risks, to ensure that an operation could be conducted without unacceptable safety risk. This limited the guidance and support available to pilots undertaking novel or infrequently encountered activities such as fire spotting. 

Fatigue management
Fatigue management regulatory requirements

As a limited aerial work operator CASR 138.150 required MDH to have a system for managing crew fatigue that met the requirements of the Part 138 Manual of Standards. The Part 138 MOS at 6.02 required compliance with an element of Civil Aviation Order 48.1. That element at paragraph 16.1 of CAO 48.1 put the onus on a pilot to not carry out a task if at any point during that task, they were likely to be fatigued.

The requirement for MDH was then to ensure that pilots had knowledge and frameworks to understand and measure fatigue and to support pilot decision‑making around fatigue. 

While MDH was not required to comply with the rules for daylight aerial work operations from appendix 5A of CAO 48.1, it serves as useful guidance. CASA CAO 48.1 plain English guide (CASA, 2025c) stated:

• The maximum flight duty period (FDP) that can be assigned in 1 day is 14 hours.

• Following an FDP, you must be off duty for at least 10 hours.

• You cannot be assigned an FDP that starts 30 minutes before the start of morning civil twilight (MCT) or that ends later than the end of evening civil twilight (ECT).

• An FDP cannot be extended beyond the end of ECT, unless it is necessary to complete the duties associated with the last daylight flight.

The final provision was to allow a pilot to complete ground-based work after landing, not to continue flight. 

Further guidance was available to flight crew members (FCM) in Civil Aviation Advisory Publication (CAAP) 48-01 (CASA, 2024b). Advice on meeting that requirement warned:

3.1.1.3 Reduced alertness may impact judgement. To manage the potential for poorer judgment and decision making associated with a fatigued FCM, CASA recommends involving a non-fatigued individual along with multiple methods for measuring alertness to assist the FCM when assessing fitness to fly.

Operator’s fatigue management practices

The pilot induction handbook contained advice to pilots on fatigue and stated:

Fatigue, or tiredness, can often be an issue in mustering operations where early mornings and long days are involved. Fatigue can have a profound effect on the performance of the mustering crew. Due to the high level of concentration required by the PIC, fatigue can set in earlier for the PIC than for the other crew members.

The accident pilot’s flight and duty times for the 7 days leading up to the accident are captured in Table 1. 

Table 1: Pilot’s previous 7 days flight and duty

Date

Activity

Duty [1]

Flight Hours [2]

Start

End

Total Hours [2]

3/10/2025Time off    
4/10/2025Travel10:0015:30

5.5

4.1

5/10/2025Time off  

 

 
6/10/2025Muster6:3618:27

11.9

5.2

7/10/2025Muster5:5414:56

9.0

8.2

8/10/2025Muster5:4519:47

14.0

10.3

9/10/2025Muster / Fire5:4219:29

13.8

11.3

   Totals

54.2

39.1

[1] A record of duty time was not available for the pilot. Duties have been calculated by adding 30 minutes to the beginning and end of flight time to allow for pre and post flight activities.

[2] Total duty hours and flight hours are related in decimals of an hour

Source: Pilot’s roster and satellite tracking data from VH-LYD

In the 72 hours prior to the accident the pilot had flown 29.8 hours and completed an estimated 36.8 hours of duty. In the 2 days leading up to the accident the pilot had flown 21.6 hours and conducted an estimated duty of 27.8 hours. On both days the pilot’s duty exceeded daylight hours, with flight on 8 and 9 October being conducted at night. Additionally, the rest period between the duties was likely less than 10 hours. 

While the fatigue regulations of an aerial work certificate holder did not apply to MDH, by way of example, this was outside of the fatigue limits for aerial work under day visual flight rules documented in Appendix 5A of CAO 48.1. 

It was reported that the pilot’s accommodation was suitable for rest. Although the pilot had worked 2 long days leading up to the accident, the rest period earlier in the week potentially protected the pilot from an accumulation of fatigue. It is not possible to determine whether the pilot experienced a level of fatigue that would have impaired performance or decision‑making at the time of the accident.

Human factors

Fatigue

Fatigue can impact pilots in various ways. It can affect decision‑making, and CASA (2025e) states that fatigue at the end of a day, shift or flight, can lead people to persevere with a chosen course of action or ignore information which could contradict a decision to continue. Fatigue can diminish the ability of the eye to focus (Robson, 2008). It can also increase the risk of spatial disorientation, and lead to delayed response times as well as a range of pilot errors (ATSB, 2013). 

Spatial disorientation

For day VFR pilots, spatial orientation is being aware of how they are orientated and moving in space with reference to external objects such as the surface of the Earth (Young, 2003). Spatial disorientation is loss of that awareness, ordinarily due to a loss of visual information, leading to an inability to correctly interpret aircraft attitude, altitude or airspeed in relation to the Earth or other points of reference (ATSB, 2013).  

The mechanisms of spatial disorientation and dangers of flight at night, which by its very nature reduces available visual information, is discussed in detail in ATSB report Avoidable Accidents No.7 Visual flight at night accidents: what you can’t see can still hurt you (AR-2012-122) (ATSB, 2013). 

Young (2003) describes the sensory systems that support spatial orientation. They include:

  • The visual system (sight) tells us where things are and what is present. It makes use of peripheral vision to detect self-motion relative to objects and the ground. The central vision can detect objects of known size and character to provide distance and closing information.
  • The vestibular system (balance and orientation organs in the ears) is the primary system for sensing body motion relative to gravity and acceleration. It supports the muscle commands that keep our eyes and head stable and keep us upright relative to gravity.
  • Proprioception (the sense of movement) helps to sense orientation and acceleration through pressure on the skin. It will also generate an accurate estimate of the current position of the body to plan movements and predict the outcome of future actions (Tuthill & Azim, 2018).

Sight provides around 80% of the information, and the balance organs and sense of movement, providing around 10% of the information each, are prone to illusions and misinterpretation. 

Poor visual cues are a feature of almost all spatial disorientation accidents. There are several well-known illusions that can affect pilots at night (ATSB, 2013): 

  • Somatogravic, the brain cannot differentiate between acceleration and a pitch-up event. In the absence of visual cues, the pilot can easily confuse the two states. A pilot response to an incorrect sensation can increase the confusion.
  • Somatogyral, the pilot’s vestibular system responds to angular acceleration. Without visual cues, this can lead to an incorrect understanding of an aircraft’s angle of bank in a turn or level flight. In the absence of external visual cues, successful orientation relies on the use of appropriate flight instruments.
  • Autokinesis is the phenomenon of a single point of light (a star or light from a distant station) appearing to move randomly in the visual field.
  • Blackhole approach involves an approach to land at night where there is nothing to see between the aircraft and the intended landing site. The absence of peripheral visual cues, especially below the aircraft, can lead pilots to perceive the aircraft is high and initiate an aggressive descent to correct their perceived approach path. The result can be landing short or impacting terrain.

The helicopter manufacturer also highlighted the dangers of disorientation specific to rotary wing operations. Safety notice SN-18 in the Robinson Helicopter Company Pilot’s Operating Handbook for the R22 stated:

Flying a helicopter in obscured visibility due to fog, snow, low ceiling, or even dark night can be fatal. Helicopters have less inherent stability and much faster roll and pitch rates than airplanes. Loss of the pilot’s outside visual references, even for a moment, can result in disorientation, wrong control inputs, and an uncontrolled crash.

Related events

Accidents involving flight at night in an unequipped Robinson R22 by pilots unqualified for night flight are frequently repeated in Australia. Common features related in the accident investigation reports in Table 2 are summarised below. 

Table 2: Investigations into similar events

Investigation numberTitle
AO-2023-058VFR into smoke on a dark night and collision with terrain involving Robinson R22, VH‑DLD
AO-2022-057Collision with terrain involving Robinson Helicopter Company R22 Beta, VH‑LOS
AO-2021-006Collision with terrain involving Robinson R22 Beta II helicopter, VH‑HKC
AO-2016-031Collision with water in dark night conditions involving Robinson R22, VH‑YLY
AO-2014-144Collision with terrain involving Robinson R22, VH‑YPC
AO-2011-087 Collision with terrain, VH-YOL
AO-2011-051Controlled flight into water, VH‑RUR

All these events involved pilots who were not qualified to fly at night. In addition, in all but one accident (AO-2014-144), the helicopters were unequipped for night flight. There was a general acceptance by pilots involved in these accidents that being unqualified and unequipped was not an impediment to flying at night. 

One investigation report (AO-2014-144) noted that the pilot planned on landing with sufficient sunlight. In all other cases the flights were intentionally conducted after last light, or pilots did not discontinue the flight when presented with an opportunity to do so. In 2 accidents (AO-2023-058 and AO-2021-006), pilots departed locations with available accommodation into dark night conditions.

Many of the investigations related to hazards that would be easily detected or inconsequential in daytime but become difficult to detect and far more serious at night. Environmental conditions such as smoke (AO‑2023‑058) and cloud and rain (AO‑2022‑057, AO‑2021‑006, AO‑2016‑031, and AO‑2011‑051) were common features. Furthermore, in 3 of the accidents (AO‑2011‑087, AO‑2014‑144, and AO‑2016-031), lights inside the cabin from sources such as GPS, instrument lights and warning lights, were noted to interfere with vision outside of the helicopter by producing glare on the windscreen.

Several workarounds to support these activities were implemented by the pilots involved. These included turning off equipment to reduce glare (AO-2016-031 and AO-2014-144), flying at low level in an attempt to find ground references (AO-2023-061, AO-2021-006, and AO-2011-087), and lighting the helipad with vehicle headlights in anticipation of a late arrival (AO-2023-058).

All of the accidents took place while travelling between locations, as opposed to while conducting aerial work. All resulted in a high-speed collision with terrain or water and all but one of the accidents (AO-2011-051) resulted in fatal injuries.

Safety analysis

Flight at night

Witness statements and tracking data for VH-LYD on the night of the accident showed it was moving after last light and beyond nautical twilight. The last movement of VH-LYD was recorded at 1929, 37 minutes after last light (end of civil twilight at 1852) and 12 minutes after nautical twilight (1917) (Figure 7). Moonrise would not happen until 2045. The combination of cloud obscuring celestial light from stars, no artificial lighting on the ground, and no moonlight meant it was almost certainly very dark. This made the pilot susceptible to spatial disorientation and loss of control of the helicopter.

Figure 7: VH-LYD night flight

VH-LYD night flight

Source: SPOT Trace, ATSB

The pilot of VH-LYD did not have a night rating, and while there was evidence of the pilot previously operating at night, the pilot had not demonstrated competence or capability as part of a flight review or flight test. 

The wreckage inspection showed it was highly unlikely that any mechanical failure of the helicopter contributed to the accident. The inspection also showed that VH-LYD did not have equipment required for flight at night such as an artificial horizon. 

The extra risks inherent in visual flight at night are from reduced visual cues, and the consequent risk of spatial disorientation (ATSB, 2013). The accident site analysis showed that VH-LYD collided with a tree at high speed while travelling perpendicular to the direction required to reach Rutland Plains. While it is not possible to determine the exact nature of the disorientation affecting the pilot, being off track and too low at high speed indicated that the pilot was very likely disorientated and without visual references at the time of collision with terrain. 

Contributing factor

The pilot flew at night but was not qualified to fly at night and the helicopter was not equipped to be flown at night.

Contributing factor

It is very likely that the pilot became spatially disorientated, resulting in collision with terrain.

Organisational acceptance

Risk management and decision‑making

The Civil Aviation Safety Regulations (CASR) Part 138 manual of standards explained that MDH Pty Ltd (MDH) had to ensure the pilot assessed that the operation could be conducted without unacceptable safety risk for the pilot and people on the ground in the context of the task. The accident occurred on the transit back from fire spotting and directing ground crew at night. 

There was no evidence of a risk assessment being conducted or of risk assessment tools or training being made available to the pilot. To align with the manual of standards, the assessment would have had to include the aircraft used in the operation and the qualifications of the pilot. MDH did not have trained pilots or suitably equipped helicopters available. Had a risk analysis been conducted, mitigating the risk of the operation involving an untrained pilot in an unequipped helicopter at night was not possible without cancelling the flight. 

Company pilots were making decisions about operations without input from the organisation, peers or risk management tools. The high level of pilot autonomy was reflected in interviews with the chief pilot, company pilots and employees. The consensus was that it was a pilot’s decision to fly and there was a position amongst pilots that it was not the place of others to tell a pilot to fly or not fly. 

While the pilots reported no pressure to fly after last light, they stated that they would fly beyond last light to complete a task and not lose a day’s work for a mustering team. Pressure on decision‑making can come from various sources without being overt. Bearman and Bremner (2016) wrote that:

  • Situational pressure can lead people to pursue a particular goal.
  • People internalise values of the organisation they work for and value decisions that benefit the organisation.
  • Social pressure can influence decisions to optimise the impression we present to others.

Perhaps due to situational and social pressure, the pilot of VH-LYD elected to use the helicopter to support fire operations after last light, and that was accepted by the pilot’s colleagues. This was consistent with accepted practices within their working environment. 

Other factor that increased risk

MDH did not require its R22 pilots to formally assess risk and did not provide tools or training to do so. This limited the ability of the company and those pilots to identify and understand operational hazards and their consequences. (Safety issue)

Awareness of flight after last light

In MDH’s environment of animal management in remote areas, teams need to be flexible and be able to improvise solutions. Autonomy of crew is a large part of that. They also need to make best use of the resources available, and a helicopter is a valuable resource. Practices such as flying beyond last light, which is an unsafe practice, can develop to become normal operations. Especially if it provides positive outcomes without negative repercussions (CASA, 2017). 

Analysis of 6 months of tracking data for 4 company R22 helicopters showed that over a combined total of 596 days of operation, on 39 occasions pilots landed after last light.  There was evidence of exceedances in all company R22 helicopters. The average exceedance was just over 15 minutes. Combining the tracking data with pilot rosters showed that 3 of the accident pilot’s colleagues had flown after last light, reportedly for operational reasons.

The company was aware that the pilots were not trained nor equipped for flight at night and aware that last light was not always observed. The chief pilot stated that there were times that helicopters would be needed to be used as long as possible. Instead of observing the limits of last light, pilots would judge the available light by sight and operate to their own level of comfort. 

Relying on individual pilot decision‑making is reflective of the Part 91 flight operations, however, the context for these flights were primarily aerial mustering and related aerial work activities for commercial cattle farming.

While these were considered limited aerial work operations by the regulations, MDH had the ability to influence pilots and set an organisational tolerance for risk. By ignoring an actual time for last light, a distinct and easy to measure limit became ambiguous and inconsistent. The company limit was not that pilots should observe last light, rather that they should not push on into the dark. However, MDH did not provide oversight or definition of this and expected pilots to manage it themselves. 

Not preventing the activity normalised the deviation from a safe envelope of operations and indicated an acceptance of flight after last light. The only limit to the non-compliance became an individual pilot’s tolerance for risk. This meant the practice could easily extend to later times and different activities.

For the pilot of VH-LYD on 9 October 2025, flying at night to assist in firefighting was likely an easy step to take, especially in the absence of a formal consideration of risk. It is not possible to discern the factors that combined in the pilot’s decision‑making about the flight. Neither is it possible to separate that decision‑making from the general acceptance of flight after last light or the influence of the operating environment.

Within the operation, limited oversight and the absence of risk management, combined with an acceptance of flight after last light, created an increased and unmitigated risk of an accident at night by an untrained pilot in an unequipped company helicopter on MDH properties.

Contributing factor

Flying after last light by pilots without night ratings, in R22 helicopters not equipped for night flight, was a tolerated and unmanaged risk on MDH properties. This increased the risk of an accident in a company R22 at night. (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 collision with terrain at night involving Robinson R22 Beta II, VH-LYD, 25 km south-south-east of Kowanyama, Queensland, on 9 October 2025.

Contributing factors

  • The pilot flew at night but was not qualified to fly at night and the helicopter was not equipped to be flown at night.
  • It is very likely that the pilot became spatially disorientated, resulting in collision with terrain.
  • Flying after last light by pilots without night ratings, in R22 helicopters not equipped for night flight, was a tolerated and unmanaged risk on MDH properties. This increased the risk of an accident in a company R22 at night. (Safety issue)

Other factors that increased risk

  • MDH did not require its R22 pilots to formally assess risk and did not provide tools or training to do so. This limited the ability of the company and those pilots to identify and understand operational hazards and their consequences. (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 are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out or are 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.

Accepted practice of exceeding last light

Safety issue number: AO-2025-063-SI-01

Safety issue description: Flying after last light by pilots without night ratings, in R22 helicopters not equipped for night flight, was a tolerated and unmanaged risk on MDH properties. This increased the risk of an accident in a company R22 at night.

Risk assessment not implemented

Safety issue number: AO-2025-063-SI-02

Safety issue description: MDH did not require its R22 pilots to formally assess risk and did not provide tools or training to do so. This reduced the ability of the company and those pilots to identify and understand operational hazards and their consequences.

Glossary

ACAdvisory circular
AIPAeronautical information publication
CAAPCivil Aviation Advisory Publication
CAOCivil Aviation Order
CASACivil Aviation Safety Authority
CASRCivil Aviation Safety Regulations
FCMFlight crew member
FDPFlight duty period
MOSManual of standards
NVFRNight visual flight rules
PICPilot in command
QPSQueensland Police Service
VFRVisual flight rules

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • MDH Pty Ltd
  • employees of MDH Pty Ltd
  • accident witnesses
  • Civil Aviation Safety Authority
  • Queensland Police Service
  • Robinson Helicopter Company
  • maintenance organisation for VH-LDY
  • Bureau of Meteorology
  • recorded data from tracking units on company aircraft. 

References

Airservices Australia. (2024). AIP Australia Part 1- General. online: Airservices Australia Retrieved from www.airservicesaustralia.com/aip/aip.asp

ATSB. (2013). Avoidable Accidents No. 7 Visual flight at night accidents: What you can’t see can still hurt you. (AR-2012-122). Canberra, ACT

Bearman, C., & Bremner, P. (2016). Don't just do something, stand there! National Emergency Response, 29(4), 12-17. 

CASA. (2017, 15 May 2017). Safety in mind: Normalisation of deviance. Flight Safetyhttps://www.flightsafetyaustralia.com/2017/05/safety-in-mind-normalisation-of-deviance/

CASA. (2021). Part 91 (General Operating and Flight Rules) Manual of Standards 

2020. Canberra, ACT: Civil Aviation Safety Authority

CASA. (2022). AC 61-05 v1.1 Night VFR rating. Canberra: Civil Aviation Safety Authority

CASA. (2024a). AC 139.R-01 v3.1 Guidelines for Heliports - Design and Operation. Canberra: Civil Aviation Safety Authority

CASA. (2024b). Civil Aviation Advisory Publication (CAAP) 48-01 v3.3. Canberra: Civil Aviation Safety Authority

CASA. (2025a). AC 138-05 v3.0 Aerial work risk management (D25/124220). Canberra, ACT: Civil Aviation Safety Authority

CASA. (2025b). CASR Part 91, General operating and flight rules - Plain English Guie v5.1. Canberra, ACT: Civil Aviation Safety Authority

CASA. (2025c). Civil Aviation Order 48.1 Fatigue Management Plain English Guide. Civil Aviation Safety Authority 

CASA. (2025d). Safety behaviours: human factors for pilots 4th edition Resource booklet 8 Threat and error management. Civil Aviation Safety Authority. https://www.casa.gov.au/sites/default/files/2021-06/safety-behaviours-human-factor-for-pilots-8-threat-error-management.pdf

CASA. (2025e). Safety behaviours: human factors for pilots 4th edition Resource booklet 9 Human information processing. Civil Aviation Safety Authority. 

CASA. (2025f). Visual Flight Rules Guide (8.2 ed.). Civil Aviation Safety Authority. 

Flight Safety Foundation. (2025). Operational Risk Assessment. In Basic Aviation Risk Standard Aerial Mustering. Flight Safety Foundation. 

Liu, Y., Tian, J., Martin-Gomez, A., Arshad, Q., Armand, M., & Kheradmand, A. (2024). Autokinesis Reveals a Threshold for Perception of Visual Motion. Neuroscience, 543, 101-107. https://doi.org/10.1016/j.neuroscience.2024.02.001

Robson, D. (2008). Night Flight (2nd ed.). Aviation Theory Centre. 

Tuthill, J. C., & Azim, E. (2018). Proprioception. Current Biology, 28(5), R194-R203. https://doi.org/10.1016/j.cub.2018.01.064

Young, L. R. (2003). Spatial orientation. In P. S. Tsang, Vidulich, M.A. (Ed.), Principles and practice of aviation psychology (pp. 69-113). LEA Publishers. 

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:

  • MDH Pty Ltd
  • Cloncurry Air Maintenance
  • Civil Aviation Safety Authority
  • Bureau of Meterology
  • Queensland Police Service

Submissions were received from: 

  • MDH Pty Ltd
  • Civil Aviation Safety Authority
  • Bureau of Meterology.

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

Purpose of safety investigations

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

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

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

About ATSB reports

ATSB investigation reports are organised with regard to international standards or instruments, as applicable, and with ATSB procedures and guidelines.

Reports must include factual material of sufficient weight to support the analysis and findings. At all times the ATSB endeavours to balance the use of material that could imply adverse comment with the need to properly explain what happened, and why, in a fair and unbiased manner.

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

CC BY logo

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]     A night VFR rating ensures a pilot has the knowledge and skills necessary to safely operate and navigate an aircraft under visual flight rules at night.

[2]     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.

[3]     The SPOT Trace system allowed users to set tracking intervals and view the tracker’s GPS coordinates online in real time.

[4]     A dry storm is a thunder storm that produces lightning but precipitation does not reach the ground. 

[5]     Geoscience Australia defines sunset as the instant in the evening under ideal meteorological conditions, with standard refraction of the Sun's rays, when the upper edge of the Sun's disk is coincident with an ideal horizon.

[6]     A waning gibbous moon phase is the period between full moon and half-moon. 

[7]     A night VFR rating ensures a pilot has the knowledge and skills necessary to safely operate and navigate an aircraft under visual flight rules at night.

[8]     In the north of Australia, cattle mustering ordinarily takes place in the dry season, from around April to November.

Occurrence summary

Investigation number AO-2025-063
Occurrence date 09/10/2025
Occurrence time and timezone 1929 Australian Eastern Standard Time
Location 25 km south-south-east of Kowanyama
State Queensland
Report release date 06/05/2026
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation phase Final report: Dissemination
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 Beta
Registration VH-LYD
Serial number 4471
Aircraft operator MDH Pty Ltd
Sector Helicopter
Operation type Part 91 General operating and flight rules
Activity General aviation / Recreational-Aerial work-Observation and patrol
Departure point Rutland Plains Aircraft Landing Area, Queensland
Destination Rutland Plains Aircraft Landing Area, Queensland
Injuries Crew - 1 (fatal)
Damage Destroyed

Loss of control and collision with terrain involving Pilatus PC-6, VH-XAA, 2.5 km north of Moruya Airport, New South Wales, on 27 September 2025

Summary

The ATSB is investigating a collision with terrain involving a Pilatus Aircraft Ltd PC-6, registered VH-XAA, 2 km north of Moruya Airport, New South Wales, on 27 September 2025.

While returning to Moruya Airport following the completion of a skydiving drop, the aircraft collided with terrain. The pilot sustained fatal injuries.

The ATSB deployed a team of transport safety investigators to the accident site with experience in aircraft operations, maintenance and engineering.

As part of the evidence collection phase of the investigation, ATSB investigators will examine the aircraft wreckage and other information from the accident site, examine operator procedures, interview witnesses and any involved parties, and examine maintenance records and any 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 that appropriate safety action can be taken.

Preliminary report

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 27 September 2025, the pilot and owner of a Pilatus PC-6/B2-H4 aircraft, registered VH-XAA and operated by Jump Aviation for SKYONE Moruya Heads parachuting organisation, was conducting parachute operations over Moruya Airport, New South Wales. After conducting 8 successful parachute drops, at 1348:58 local time, the pilot broadcast on the common traffic advisory frequency (CTAF)[1] that they were taxiing for runway 04[2] to conduct the next flight. On board were 8 parachutists and the pilot. The pilot was wearing the fitted 4-point restraint and an emergency parachute in accordance with company procedures.

At 1351:08, the pilot broadcast that the aircraft was airborne off runway 04, for an upwind departure and on climb to flight levels (FL)[3] for parachute operations. During the climb to the planned drop between FL 140 and 150, several parachutists reported feeling a bump and hearing the stall warning[4] activate momentarily, passing about 10,000 ft. 

At 1400:52, the pilot broadcast on the CTAF that they were 4 minutes to a parachute drop, then advised the same to Melbourne Centre air traffic control. Recorded data showed the ‘jump run’ tracked in a northerly direction about 2 km west of Moruya Airport runway 36, in a gradual descent between FL 150 and 140. The parachutists reported that the jump run was normal, and all the parachutists exited successfully. At 1406:15, the pilot broadcast that the parachutists had exited and the aircraft was on descent. 

Several witnesses on the ground observed the aircraft enter a steep nose-down dive, rotating left before pitching[5] up and rolling[6] right. Recorded data showed the aircraft initially descended from FL 140 at about 5,000 fpm, but approaching FL 120, the descent rate increased significantly. The last recorded automatic dependent surveillance‑broadcast (ADS-B) data position was at 1407:26 and 7,425 ft, descending at about 15,000 fpm (Figure 1). The aircraft subsequently impacted trees and terrain about 2 km north of Moruya Airport. The pilot sustained fatal injuries, and the aircraft was destroyed.

Figure 1: VH-XAA flight track and accident site

Figure shows the flight path of VH-XAA and accident site and the location of Moruya Airport.

Source: Google Earth, annotated by the ATSB 

Context

Pilot

The pilot held a private pilot licence (aeroplane) with the last flight review conducted in August 2025, and a class 2 aviation medical certificate, valid until June 2027. The pilot held the appropriate ratings and endorsements for the flight. In addition, the pilot held aerobatics and spin endorsements and jump pilot authorisation. At the time of the accident, they had about 11,690 hours total aeronautical experience. In the previous 90 days, they had flown 135.2 hours, most of which were conducting parachuting operations in Cessna 206 and 208 aircraft. 

The pilot’s logbook recorded an endorsement for the Pilatus PC-6 (required by the then Civil Aviation Regulations) in 1998. The ATSB was unable to access some of the pilot’s logbooks to confirm how many hours they had logged flying the Pilatus PC-6 prior to purchasing VH‑XAA from New Zealand (NZ). Between 22 and 24 August 2025, the pilot and an instructor flew the aircraft from Auckland, NZ, to Dubbo, New South Wales, logging 19.5 hours of flight time. The pilot then recorded 2 hours operating the aircraft to Moruya on 12 September 2025. From 20 to 24 September 2025 inclusive, the pilot recorded 9.7 hours in the aircraft conducting parachute operations. At the start of the accident morning, the pilot had logged 31.2 hours in VH-XAA.

The pilot was an experienced parachutist and had been a member of the Australian Parachute Federation (APF)[7] since 1987. On 30 June 2025, the pilot reported having conducted 17,000 jumps. The pilot held numerous parachuting qualifications including senior instructor and a Certificate F, which was the highest certificate issued by the APF. The pilot was the senior pilot of Jump Aviation and the chief parachute instructor of the parachuting operator SKYONE Moruya Heads – a group member of the APF. 

Aircraft

General information

VH-XAA was a Pilatus Aircraft PC-6/B2-H4, short take-off and landing utility aeroplane with fixed landing gear (Figure 2). It was powered by a Pratt & Whitney Canada PT6A-27 turbine engine and a Hartzell Propellers HC-B3TN-3D 3-bladed propeller. The aircraft was not approved for aerobatic manoeuvres including spins. 

Figure 2: VH-XAA when operating in New Zealand as ZK-MCK

VH-XAA when operating in New Zealand as ZK-MCK.

Source: Richard Currie, modified by the ATSB

It was manufactured in Switzerland in 1980 and issued serial number 809. The aircraft had been used for parachute operations in New Zealand (NZ) since 1982. As such, the passenger seats, copilot seat and copilot control stick had been removed. Additionally, a skydiving step and hand hold had been installed.  

A 7,000 hour/14-year ‘complete overhaul’ maintenance activity was performed in NZ and finalised on 14 August 2025. During the maintenance activity, the horizontal stabiliser electric trim actuator was removed and overhauled by the manufacturer in the United States. 

The aircraft was added to the Australian civil aircraft register on 15 August 2025, and a special flight permit[8] was issued to allow the aircraft to be flown from NZ to Australia. After the pilot ferried the aircraft to Australia, a certificate of airworthiness was issued for VH-XAA on 19 September 2025. At the time of the accident, VH-XAA had accrued 13,594.5 hours total time in service.

Doors

The aircraft had a door on each side of the cockpit for pilot and copilot access, which were fitted with a jettison system. Figure 3 shows the Pilatus PC-6 airplane flight manual[9] (AFM) procedure for emergency opening of the cockpit doors: 

Figure 3: Cockpit doors emergency opening checklist

Pilatus PC-6 airplane flight manual procedure for cockpit door emergency opening'

Source: Pilatus PC-6 airplane flight manual

The aircraft cabin had a sliding door on the right side, which was used for parachutists to exit, and 2 hinged doors on the left side, which were fitted with an emergency jettison system. The sliding door had a mechanism to open it from inside the aircraft, but it could not be locked open. Parachutists reported that, on the day of the accident, the pilot had landed with the sliding door open on some flights and closed on others. Although it was not identified at the accident site, several parachutists reported that there was a fishing gaffer hook on a pole onboard the aircraft that the pilot used to close the sliding door in flight from the pilot’s seat. 

Key speeds

The AFM included the following key speeds:

  • never exceed speed (VNE)[10] 151 kt
  • manoeuvring speed (VA)[11] 119 kt
  • maximum speed with the sliding door open 119 kt
  • stalling speeds at a gross weight of 2,800 kg, power off and 0° angle of bank including:
    • 58 kt calibrated airspeed[12] (KCAS) with flap retracted
    • 52 KCAS with landing flap extended. 
Horizontal stabiliser electric trim system

The aircraft was fitted with a horizontal stabiliser electric trim system, designed to move the entire horizontal stabiliser to adjust the pitch trim of the aircraft and balance the aerodynamic forces to reduce the pilot control forces on the elevator. The system (Figure 4), consisted of:

  • a dual motor (main and alternate motors) electrically‑operated linear trim actuator
  • a 3-position spring-loaded trim switch, located on the control column grip
  • a relay located on the firewall
  • an interrupt system incorporating a guarded switch on the instrument panel shelf and an alternate trim control system with a 3-position spring-loaded trim switch (Figure 5)
  • an electrically‑operated trim position indicator on the upper left side of the instrument panel.

Figure 4: Schematic of horizontal stabiliser trim system 

Schematic of the horizontal stabiliser trim system, showing the trim actuator, trim switch, relay, trim position indicator and interrupt switch system.

Source: Pilatus PC-6 Illustrated Parts Catalogue, modified and annotated by the ATSB

Figure 5: Instrument panel shelf horizontal stabiliser trim switches 

Pilatus electric interrupt switch panel showing the guarded interrupt switch and the alternate trim control switch as fitted to VH-XAA

Source: Supplied and Pilatus PC-6 AFM, annotated by the ATSB

The AFM included the following procedure (Figure 6) in the event of a trim runaway:[13]

Figure 6: Horizontal stabiliser trim runaway emergency procedure

Pilatus PC-6 airplane flight manual of the emergency procedure for horizontal stabiliser trim runaway.

Source: Pilatus PC-6 airplane flight manual

The AFM included the following procedure (Figure 7) for jammed trim actuators:

Figure 7: Jammed horizontal stabiliser trim actuator emergency procedure

Pilatus PC-6 airplane flight manual procedure for jammed trim actuators.

Source: Pilatus PC-6 airplane flight manual

The AFM also included the following procedure (Figure 8) for loss of elevator control:

Figure 8: Loss of elevator control emergency procedure

Pilatus PC-6 airplane flight manual procedure for loss of elevator control.

Source: Pilatus PC-6 airplane flight manual

Beta mode

The AFM described beta mode as ‘operation of the propeller used in flight to achieve fast deceleration and high rates of descent’. The AFM stated:

In the beta range, the propeller blades are set at a low positive pitch angle to provide a braking effect for steep controlled descents. When operating in the beta mode, the propeller pitch angle is controlled by power lever movement between the lift detent and the point where constant speed operation becomes effective. 

NOTE

BETA MODE is provided in descent at airspeeds below 100 KIAS [kt indicated airspeed] with the POWER lever near or at the detent. Only small movements of the POWER lever are necessary to change rate of descent or airspeed. Approaches in full BETA MODE (POWER lever at detent) are not permitted at airspeeds below 1.3 Vs.[14]

Meteorological information 

The Bureau of Meteorology aerodrome forecast for Moruya Airport, issued at 1109 on 27 September 2025 included wind from 090° at 5 kt, which was expected to change to 310° and become gusty between 1200 and 1300. The grid point wind and temperature chart showed the forecast winds:

  • at 10,000 ft from 270° at 42 kt
  • at FL 140 from 270° at 51 kt. 

The Bureau of Meteorology had also issued SIGMETs[15] for severe turbulence below 8,000 ft and mountain waves from 4,000 ft to FL 320 in an area that included Moruya Airport, between 1100 and 1500. 

The conditions recorded in the METAR[16] at Moruya Airport at 1400 included wind from 130° at 6 kt, visibility greater than 10 km, temperature 22°C, and QNH[17] 1,007 hPa. 

Recorded data

The ATSB conducted preliminary analysis of the aircraft’s 3-dimensional position information recorded in the ADS-B data for the 9 flights on 27 September 2025, the last of which was the accident flight. The positional data was interpolated between recorded positions and a trajectory analysis conducted to estimate other flight performance and handling parameters. The analysis was based on the forecast wind and an estimated aircraft weight of 1,587 kg (3,500 lb). For most of the flights, there was no recorded ADS‑B data below about 4,000 ft above mean sea level. 

A comparison of the following key parameters for the 9 flights was conducted for the descent following parachute drop from about FL 140: 

  • altitude
  • descent rate
  • estimated calibrated airspeed
  • estimated pitch and roll angles.  

For flights 1–5, 7 and 8, the values of these parameters were similar. In those 7 flights, the descent commenced at an airspeed of about 55–70 KCAS, with an initial nose-down pitch of about 30° and either a right or left roll of about 30° (on flight 4 the roll angle was possibly up to 50°). The maximum descent rate for these 7 flights was between about 5,500 and 8,000 fpm. 

On flight 6, the descent was initiated slightly slower, at about 54 KCAS, which increased within 10 seconds to about 145 KCAS, coincident with a maximum momentary descent rate of about 14,000 fpm, a steep (70°) pitch down in conjunction with a substantial roll right.

The descent on the accident flight (flight 9) was initiated at about 53 KCAS from 14,200 ft to a nose-down pitch of about 25°, with a 60° right roll. The aircraft briefly reduced pitch slightly before nosing vertically down (about 90°) in a left roll, reaching a maximum descent rate of over 20,000 fpm. The aircraft then pitched up to a shallow climb and into a roll of more than 120°. From the data it could not be confirmed whether this manoeuvre was conducted upright or inverted. Passing about 9,600 ft, the airspeed reduced to 125‍–‍130 KCAS before increasing again. The last recorded position, passing about 8,000 ft indicated the aircraft had accelerated to 173 KCAS, with a final descent rate above 15,000 fpm (Figure 9).

 Figure 9: Preliminary plot of key parameters from the accident flight descent

Preliminary plot of key parameters from the accident flight descent

Due to the aircraft’s manoeuvring, the roll information may be inaccurate. Local time was UTC+10 hours. Source: ATSB

Site and wreckage

The wreckage site was about 2.5 km north (and slightly west) of the northern end of the Moruya Airport runway 36. ATSB examination showed that the right wing struck a tree on the eastern side of George Bass Drive and separated from the fuselage, before the aircraft collided with trees on the western side of the road and subsequently impacted terrain in a nose-down inverted attitude (Figure 10). The outer section of the right wing landed on the road but was moved clear by members of the public shortly after the accident. 

Figure 10: Overview of VH-XAA accident site

Overhead view of accident site showing direction of travel, trees struck and location of the main wreckage

Source: ATSB

The examination identified: 

  • there was fuel remaining and no post-impact fire occurred
  • all major components of the aircraft were at the site, indicating there was no in-flight breakup
  • the propeller had indications that the engine was producing power at impact
  • there were no indications of any pre-impact mechanical anomalies that would have precluded normal engine operation
  • the pilot’s 4-point restraint was undone, and the pilot was almost certainly not in the pilot seat at the time of impact
  • the horizontal stabiliser trim actuator was found in the full nose-down position (Figure 11).

Figure 11: Horizontal stabiliser trim actuator showing trim position

Image showing the horizontal stabiliser trim actuator and trim rod at full nose down position.

Source: ATSB

Further investigation

To date, the ATSB has: 

  • interviewed witnesses and involved parties
  • obtained pilot and aircraft documentation
  • analysed recorded data
  • reviewed recorded audio transmissions
  • assessed the accident site and examined the aircraft wreckage.

The investigation is continuing and will include further examination of:

  • the horizontal stabiliser trim system
  • recorded flight data
  • aircraft configuration, maintenance and documentation
  • operational procedures and documentation
  • pilot training records
  • survivability and opportunity for egress
  • other similar occurrences. 

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 would like to acknowledge the assistance of the NSW Police Force, Fire and Rescue NSW, and first responders.

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]     Common traffic advisory frequency (CTAF): a designated frequency on which pilots make positional broadcasts when operating in the vicinity of a non-controlled aerodrome or within a broadcast area.

[2]     Moruya Airport had 2 sealed runways, 18/36 and 04/22. The runway number represents its magnetic heading. 

[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). FL 140 equates to 14,000 ft.

[4]     A stall warning system provides the pilot with advance warning of an impending aerodynamic stall.

[5]     Pitching: the motion of an aircraft about its lateral (wingtip-to-wingtip) axis.

[6]     Rolling: the movement of an aircraft about its longitudinal axis.

[7]     The APF is the peak body for the administration and representation of Australian Sport Parachuting.

[8]     Special Flight Permit (SFP): issued to allow the operation of an aircraft that does not meet its airworthiness requirements but under certain circumstances, and for a particular intended purpose, the aircraft may still be capable of safe flight.

[9]     Airplane flight manual (AFM): a manual that is part of the certification basis of the aircraft, containing the operating limitations within which the aircraft is considered airworthy, and any other information required for the safe operation of the aircraft, including all amendments and supplements for that manual.

[10]    Never exceed speed (VNE): the indicated airspeed which, if exceeded, may result in structural damage to the aircraft, normally represented by a red line on the airspeed indicator.

[11]    Manoeuvring speed (VA): the maximum speed at which a pilot can make full or abrupt control movements without causing structural failure of the aircraft. 

[12]    Calibrated airspeed: indicated airspeed corrected for air speed indicator system errors.

[13]    Pitch trim runaway is an uncontrolled movement of the aircraft’s trim system causing uncommanded nose-up or nose‑down pitch.

[14]    Vs - Stall speed or minimum steady flight speed for which the aircraft is still controllable.

[15]    SIGMET: a concise description of the occurrence or expected occurrence, in an area over which area meteorological watch is maintained, of specified phenomena which may affect the safety of aircraft operations. 

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

[17]    QNH: the altimeter barometric pressure subscale setting used to indicate the height above mean seal level.

Occurrence summary

Investigation number AO-2025-058
Occurrence date 27/09/2025
Location 2.5 km north of Moruya Airport
State New South Wales
Report release date 12/11/2025
Report status Preliminary
Anticipated completion Q1 2026
Investigation level Short
Investigation type Occurrence Investigation
Investigation phase Evidence collection
Investigation status Active
Mode of transport Aviation
Aviation occurrence category Collision with terrain, Loss of control
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Pilatus Aircraft Ltd
Model PC-6/B2-H4
Registration VH-XAA
Serial number 809
Aircraft operator Jump Aviation Pty Ltd
Sector Turboprop
Operation type Part 105 Parachuting
Departure point Moruya Airport, New South Wales
Destination Moruya Airport, New South Wales
Damage Destroyed

Collision with terrain involving Robinson R22 Beta, VH-RDL, Bankstown Airport, New South Wales, on 3 October 2025

Summary

The ATSB is investigating a collision with terrain involving a Robinson R22, registered VH‑RDL, at Bankstown Airport, New South Wales, on 3 October 2025.

During training operations, the aircraft collided with terrain and was subsequently destroyed. One occupant was fatally injured and the other person received serious injuries.

The ATSB deployed a team of transport safety investigators to the accident site with experience in operations, maintenance and engineering. Several components were recovered from the accident site for more detailed examination.

The ATSB has commenced the examination and analysis of the initial evidence collected.

To date, the ATSB investigation has:

  • examined the aircraft wreckage and other information from the accident site
  • retrieved operator procedures
  • conducted interviews with the surviving pilot, witnesses and other involved parties.
  • reviewed pilot records
  • reviewed maintenance records and video evidence.
  • reviewed air traffic control communications.

The continuing investigation will include:

  • analysis of the audio signatures captured by the recording camera
  • further analysis of physical evidence retrieved from the accident site
  • interview with Bankstown tower air traffic control.

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

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 3 October 2025, a Robinson R22 Beta helicopter, registered VH‑RDL and operated by Bankstown Helicopters,[1] was conducting a training flight at Bankstown Airport, New South Wales. On board the helicopter was a flight instructor, seated in the left seat, and a student pilot in the right seat. The flight instructor was the pilot in command (PIC), however, as it was a training flight, the student pilot was in the seat normally reserved for the PIC. 

The helicopter departed the main helicopter pad (Figure 1) at about 1328 local time. The plan for the flight was to conduct circuits[2] on runway 29. The student pilot stated to the ATSB that they had planned and prepared to conduct a lesson on practice forced landings. However, due to the weather, the instructor changed the lesson to circuits. Due to the windy conditions on the day, the instructor demonstrated the first circuit, with the student pilot following them on the flight controls.[3]

At about 1329, the instructor made a downwind position radio broadcast and was cleared by Bankstown Tower air traffic control for a ‘stop and go’ on the main pad. In interview with the ATSB, the student pilot recalled that, during the downwind leg of the circuit, the helicopter dropped suddenly and they noticed the revolutions per minute (RPM) reduce but could not recall if this was engine or rotor RPM (see section Helicopter information). The student also recalled hearing a whistling noise prior to the RPM reduction. Following the sudden drop and RPM reduction, the student recalled that the instructor kept their hands on the controls and continued to fly the aircraft while attempting an autorotation,[4] and they could not recall the instructor changing any switch positions.  

Dashcam video taken from a parked car captured the helicopter tracking along its flight path, before conducting a turn back into wind toward the airport. The video showed that the helicopter was flared[5] as it approached the ground, likely in an attempt to reduce the rate of descent. The helicopter impacted trees, before colliding with the rear of a car and the ground, coming to rest on its left side. The instructor was fatally injured, and the student was seriously injured. The helicopter was destroyed. 

Figure 1: Estimated flight path

An image showing the Bankstown Airport layout. The ATSB has annotated the position of the Bankstown ATC Tower, main helicopter pad, and accident site location.

Source: Airservices Australia, annotated by the ATSB

Context

Pilot information

The instructor held a Commercial Pilot (Aeroplane) Licence (CPL-A) issued July 1998, and a Commercial Pilot Licence (Helicopter) (CPL-H) issued July 2012. They also held a Grade 1 flight instructor rating for helicopter operations. 

The instructor began employment with the operator of VH-RDL in November 2024. Paperwork completed when joining indicated that the instructor had around 877 hours experience on fixed-wing aircraft, and 1,071 hours in helicopters. The instructor’s logbook indicated that, as of September 2025, they had a total helicopter flying experience of 1,131 hours, which included 993 hours as PIC. 

The instructor held a class 2 aviation medical certificate, which was current at the time of the accident. To exercise the privileges of a commercial pilot’s licence, pilots normally required a class 1 aviation medical. However, under Civil Aviation Safety Authority (CASA) General Exemption CASA EX28/23, commercial pilots with a class 2 medical certificate can fly commercial flights without passengers if the aircraft’s maximum take-off weight is less than 8,618 kg. This included flight training.[6] 

Video evidence showed the instructor was completing pre-flight duties in the office at approximately 0630. Their first flight of the day commenced at 0700 with a hover lesson. This was followed by another general handling instructional flight at 0830. All flights were conducted in VH­‑RDL.

The student pilot had approximately 33 hours of flight experience. They did not yet hold a pilot’s licence.

Helicopter information

VH-RDL was a 2-seat Robinson Helicopter Company R22 Beta, serial number 1498, powered by a 4-cylinder Lycoming O-320-B2C engine. The helicopter was manufactured in the United States in 1990 and placed on the Australian aircraft register on 16 April 2002. Bankstown Helicopters had been the registered operator of VH-RDL since 22 February 2024.

The helicopter had a combined engine and rotor RPM tachometer, which was positioned on the right side of the dashboard in front of the student pilot (Figure 2). The left side of the tachometer showed the engine RPM and the right side showed the rotor RPM. The position of the tachometer required the instructor to look across the dashboard to see the instrument.

Figure 2: VH-RDL engine and rotor RPM tachometer

An image of the aircraft's dashboard showing the engine and rotor RPM gauge.

Source: ATSB

Meteorological information

During taxi, the student pilot reported they had received information ‘golf’ from the automatic terminal information service (ATIS).[7] The information indicated that runway 29 was in use, mechanical turbulence was present on short final, the wind was 220° at 18 kt with a crosswind up to 20 kt, conditions were CAVOK,[8] the temperature was 24°C and QNH[9] 1014 hPa.

The ATSB obtained Bureau of Meteorology weather observations for Bankstown Airport taken at 1-minute intervals, which showed:

  • at 1328, the wind was 278° T (true) and 265° M (magnetic) at 18.1 kt
  • at 1329, the wind was 269° T (256° M) at 18.1 kt
  • at 1330, the wind was 270° T (257° M) at 16.9 kt.

The operator’s alternate chief pilot, who was also instructing that day, had cancelled their flights as they assessed the weather to be challenging for their student’s experience level and the environmental conditions would have likely not resulted in useful learning for them.

Operational information

The operator advised the ATSB that their normal pre-landing checks in the Robinson R22 Beta, performed on the downwind leg of the circuit, included the following:

  • warning/caution lights – out
  • rpm (engine and rotor) – in the green
  • temperatures and pressures – in the green
  • fuel – sufficient for go around
  • battery – charging
  • carburettor heat – on
  • hatches and harnesses – secure.

Wreckage information

The helicopter wreckage was contained within a relatively small accident site, with only minor wreckage spread and limited forward projection of debris. This indicated that the helicopter impacted the car and ground with a low forward speed. There was no post‑impact fire. The ATSB’s wreckage examination found that:

  • there was sufficient fuel on board the helicopter to sustain continued engine operation
  • damage identified in the main rotor system was consistent with low energy flight, as also indicated by the dashcam and the observed spread of the wreckage
  • there was no evidence of pre-existing defects with the flight control system
  • the pitot system was checked and considered to be serviceable prior to the collision with terrain
  • inside the aircraft, the key switches were found in the following positions:
    • fuel selector – on
    • fuel mixture – rich
    • carburettor heat – on
    • master switch – off
    • magnetos – off

A witness to the accident confirmed that they had switched the master to the off position to secure the helicopter and make it safe. The ATSB was unable to establish how the magnetos came to be in the off position.

It was determined by the ATSB that the engine was intact, and all components were present. Examination of the engine by the ATSB on site identified an absence of physical damage expected of an engine that was operating (rotating) at the time of impact with terrain. The engine examination also found:

  • Evidence of an exhaust gas leak between the exhaust riser mount flange/exhaust gasket surfaces of the no 4 cylinder. The leak was attributed to deformation of the flange that created space between the flange and the gasket (Figure 3). This leak was located directly above the carburettor heat intake scoop opening.
  • Deposits of exhaust gas products were present on the no 2 and no 4 cylinder ignition leads that were routed beside the no 4 cylinder exhaust riser.

Figure 3: Exhaust leak found during the onsite inspection

The helicopter's engine with a close-up of the area where the exhaust riser mount flange meets the exhaust gasket surface. The image points our an exhaust leak.

Source: ATSB

Survivability information

First responders and witnesses stated that the instructor and student had their seatbelts on. Neither of them was wearing a helmet and nor were they required to. 

Further investigation

To date, the ATSB has:

  • examined the wreckage and other information from the accident site
  • obtained operator procedures
  • conducted interviews with the student, witnesses and other involved parties
  • reviewed the pilot records
  • reviewed the helicopter maintenance records
  • examined the dashcam video
  • reviewed air traffic control communications.

The investigation is continuing and will include:

  • an analysis of the audio signatures captured by the dashcam video
  • further analysis of physical evidence including the exhaust system components retrieved from the accident site
  • a review of the PIC’s experience performing autorotations in all helicopter types and specific to the Robinson R22 Beta
  • a review of both the helicopter manufacturer and operator’s procedures for conducting autorotations.

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.

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

CC BY logo

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]     Bankstown Helicopters was operated under Civil Aviation Safety Regulation Part 141 as an approved flight training organisation based at Bankstown Airport, New South Wales.

[2]     Circuits: a circuit is the specified path to be flown by aircraft operating in the vicinity of an aerodrome. It comprises upwind, crosswind, downwind, base and final approach legs. It creates an orderly flow of traffic from take-off to landing and assists pilots with positioning the aircraft on final at the appropriate altitude and distance from the landing area to make a stabilised approach.

[3]     Following on the controls: it is common for students to learn by having their hands and feet on the controls while the instructor manipulates them. This can help students to learn how much input to use for certain controls and when they are appropriate. Students have their hands on the controls but are not making inputs.

[4]     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 is determined mainly by airspeed.

[5]     Flaring: the final nose-up pitch of a landing helicopter used to reduce the rate of descent and forward airspeed to about zero at touchdown, it can also increase the rotor RPM during an autorotation.

[7]     Automatic terminal information service (ATIS): provides routine airport and weather information to arriving and departing aircraft by means of continuous and repetitive broadcasts. ATIS information is prefixed with a unique letter identifier and is updated either routinely or when there is a significant change to weather and/or operations.

[8]     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 other significant weather.

[9]     QNH: the altimeter barometric pressure subscale setting used to indicate the height above mean sea level.

Occurrence summary

Investigation number AO-2025-059
Occurrence date 03/10/2025
Location Bankstown Airport
State New South Wales
Report release date 17/12/2025
Report status Preliminary
Anticipated completion Q3 2026
Investigation level Short
Investigation type Occurrence Investigation
Investigation phase Examination and analysis
Investigation status Active
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 Beta
Registration VH-RDL
Serial number 1498
Aircraft operator Bankstown Helicopters Pty Limited
Sector Helicopter
Operation type Part 141 Recreational, private and commercial pilot flight training
Departure point Bankstown Airport, New South Wales
Destination Bankstown Airport, New South Wales
Damage Destroyed

Collision with terrain involving a Robinson R22 Beta II, 100 km north of Cloncurry, Queensland, on 6 September 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

At about 0625 local time on 6 September 2025, the pilot and sole occupant of a Robinson R22 helicopter departed Cloncurry Airport, Queensland, to conduct commercial aerial mustering operations about 100 km north of Cloncurry. At about 0830 the pilot identified a small mob of cattle under trees in a dry creek bed. Attempting to move the stock, the pilot turned the aircraft downwind and recalled the aircraft descended during the turn. While attempting to arrest the rate of descent the pilot increased power as they attempted to avoid a dead tree which they estimated was about 6–8 m high. However, as the aircraft was already at maximum power the pilot was unable to gain sufficient height and the helicopter collided with the tree.

The pilot recalled the tree penetrated the windscreen and that the helicopter began to rotate. The helicopter then impacted terrain on its left side, temporarily rendering the pilot unconscious. The aircraft came to a stop in a dry creek bed about 20 m from the impact tree. The helicopter sustained substantial damage: the tail rotor and horizontal stabiliser separated from the main fuselage during the accident sequence and were located in close proximity to the tree (Figure 1).

Figure 1: Occurrence aircraft 

Robinson R22 on its left side in a dry creek bed. The image shows damage to the fuselage and main rotor system. The tail rotor assembly was removed in the accident sequence.

Source: LifeFlight, modified by the ATSB

After regaining consciousness, the pilot recalled they were held in their seat by the seatbelt and freed themselves from the wreckage. They contacted nearby ground crew on motorcycles via two-way radio to request assistance. The operator advised that the onboard tracking and phone records showed the pilot then called the operator about 15 minutes after the impact with the tree.

The pilot had been wearing a helmet which sustained minor damage. The pilot sustained serious injuries that included cracked vertebrae and was airlifted to Mount Isa hospital later that morning. 

The 2014 CASA aerial mustering sector risk profile identified some of the key risks during aerial mustering operations stating:  

The aerial mustering sector is hazard rich due to the inherent characteristics of the operation, such as very low level flying, high workload, negative effects from weather, obstacles such as power lines, trees, and terrain, pilot distraction, small power margins, and extended time operating within the shaded area of the height/ velocity diagram (‘deadmans curve’). In some parts of Australia, military aircraft may intrude into airspace above cattle stations which could cause airborne conflict. Pilot training, supervision and mentoring play an important role in developing pilot skills to manage aerial mustering manoeuvres.

Safety message

Aerial stock mustering involves operating in an inherently hazardous environment – aircraft are manoeuvred at very low level, close to obstacles. Low‑level operations in small helicopters often result in minimal available power margins because reduced airspeeds and abrupt manoeuvring of the helicopter both require additional power. When the helicopter’s power required is greater than the power available, the aircraft is unable to maintain height and can cause the pilot to attempt to apply additional collective[1] pitch. The result is a reduction in rotor RPM and therefore further loss of altitude. Also, low‑level flight reduces the time available for pilots to apply corrective techniques to restore rotor RPM and level flight. 

Several Robinson Helicopter Safety Notices discuss the risks involved with low rotor RPM and are available on its website robinsonheli.com.

Operators and pilots of Robinson R22 and other smaller helicopters, especially those used for low-level aerial work such as mustering, are encouraged to review the causes, effects and recovery techniques for low rotor RPM and ensure they avoid low rotor RPM situations at low level in environments where obstacles may present a significant hazard.

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]     The collective control changes the pitch angle of all main rotor blades.

Occurrence summary

Mode of transport Aviation
Occurrence ID AB-2025-045
Occurrence date 06/09/2025
Location 100 km north of Cloncurry
State Queensland
Occurrence class Accident
Aviation occurrence category Collision with terrain
Highest injury level Serious
Brief release date 07/10/2025

Aircraft details

Manufacturer Robinson Helicopter Co
Model R22 Beta
Sector Helicopter
Operation type Part 138 Aerial work operations
Departure point Cloncurry Airport, Queensland
Destination Cloncurry Airport, Queensland
Damage Substantial

Wirestrike and collision with terrain involving a Eurocopter AS 350, 10 km east of Holbrook Airport, New South Wales, on 3 September 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 the morning of 3 September 2025, a Eurocopter AS 350 was conducting agricultural spraying operations in the Holbrook, New South Wales, area. 

In preparation for the second run for the day, the pilot conducted a hazard reconnaissance of a 14‑hectare paddock and identified wires to the west, a road to the east and livestock in the corners of neighbouring paddocks. 

The helicopter was fitted with a GPS navigational system which also featured a wire detection system designed to alert the pilot when the aircraft is approaching a mapped wire. The wire was correctly mapped in the aircraft GPS system.

Once spraying operations had commenced, the pilot reported that they were focusing on the spray as well as the stock in the neighbouring property which was at the end of their run. This resulted in them losing sight of the already identified wires in the spraying run overshoot area. Shortly after the dispensing had been completed, the pilot entered the neighbouring paddock and saw the wires. However, with little time to respond, the helicopter’s skids struck a wire resulting in damage to the tail rotor. The helicopter then began vibrating violently and rotated to the left, entering multiple 360° turns before it collided with terrain, rolled onto its right side and caught fire. The pilot was able to exit the passenger door of the helicopter and sustained minor burn injuries. The helicopter was destroyed by post-impact fire (Figure 1). 

Figure 1: Post-impact damage

This image shows the post-impact damage to the helicopter, destroyed by fire.

Source: NSW Police

Safety message

Despite the hazard assessment and the systems in place to warn about the wires, in this occurrence the distraction of the stock in the neighbouring paddocks diverted the pilot’s attention resulting in them losing sight of the wires.

Research by the ATSB has shown that 63% of pilots were aware of the position of the wire before they struck it.[1]

In association with the Aerial Application Association of Australia (AAAA), the ATSB released an educational booklet, Wirestrikes involving known wires: A manageable aerial agriculture hazard (AR-2011-028). This booklet contains details of multiple wirestrike accidents, lessons learned, and a number of strategies to help agricultural pilots manage the ongoing risk of wirestrikes during spraying operations. The booklet notes that focusing attention on non‑operational tasks or focusing on operational tasks at the wrong time can affect pilots’ hazard avoidance, detection and reaction times, and that all pilots, no matter the level of experience, can get distracted.

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]     ATSB research and analysis report B2005/0055, Wire-strike Accidents in General Aviation: Data Analysis 1994 to 2004, available at www.atsb.gov.au.

Occurrence summary

Mode of transport Aviation
Occurrence ID AB-2025-044
Occurrence date 03/09/2025
Location 10 km east of Holbrook Airport
State New South Wales
Occurrence class Accident
Aviation occurrence category Collision with terrain, Wirestrike
Highest injury level Minor
Brief release date 01/10/2025

Aircraft details

Manufacturer Eurocopter
Model AS 350 B3
Sector Helicopter
Operation type Part 138 Aerial work operations
Departure point New Holbrook, New South Wales
Destination New Holbrook, New South Wales
Damage Destroyed

Collision with terrain involving Alexander Schleicher AS 33 Me, VH-8SP, near McCaffrey Field, Queensland, on 30 July 2025

Summary

The ATSB is assisting Gliding Australia with an investigation into a collision with terrain involving Alexander Schleicher AS 33 Me, registration VH-8SP, near McCaffrey Field, Queensland, on 30 July 2025.

During glider towing operations, after the glider was released, it collided with terrain, resulting in fatal injuries to the pilot.

In response to this accident, Gliding Australia commenced an investigation. As part of its investigations, Gliding Australia requested technical assistance from the ATSB to examine components from the accident.

To facilitate this support and to provide the appropriate protections for the information, the ATSB initiated an investigation under the Transport Safety Investigation Act 2003.

Any enquiries relating to the investigation should be directed to Gliding Australia.

Occurrence summary

Investigation number AE-2025-003
Occurrence date 30/07/2025
Location Near McCaffrey Field
State Queensland
Investigation type External Investigation
Investigation phase Evidence collection
Investigation status Active
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Runway excursion and collision with terrain involving a Cessna 180, Borroloola Aerodrome, Northern Territory, on 19 August 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 19 August 2025, a Cessna 180 with a tailwheel landing gear was approaching runway 20 at Borroloola Aerodrome, Northern Territory, in variable, moderate crosswind conditions. There were 2 pilots and 1 passenger on board. Just after touchdown, the aircraft turned into the wind and started to veer left off the runway. The pilot in command initiated a go-around and as the aircraft began to lift off, it continued drifting off the runway. 

The left wheel struck a mound of dirt beside the runway and the wheel departed the aircraft, causing the aircraft to rotate, collide with the ground and skid sideways, subsequently striking a concrete culvert before coming to rest (Figure 1). The aircraft was substantially damaged during the accident, however the 3 people on board were uninjured.

Figure 1: Aircraft damage

Figure 1: Aircraft damage

Source: Borroloola Aerodrome operator

Safety message

This accident provides a reminder for pilots to be prepared to conduct a missed approach, particularly in tailwheel aircraft during crosswind conditions. Tailwheel aircraft have less directional stability on the ground due to the location of the centre of gravity behind the main wheels. They are more susceptible to the effects of crosswind and the tail can have a tendency to swing sideways on the ground. They require more active input to maintain directional control and any yaw needs to be corrected immediately as it can quickly lead to a large swing and potential loss of control. If conditions during approach are challenging, an early go-around can provide an opportunity to reassess the landing options and make a reasoned decision about whether to attempt another approach and plan for how to manage the conditions.

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-2025-042
Occurrence date 19/08/2025
Location Borroloola Aerodrome
State Northern Territory
Occurrence class Accident
Aviation occurrence category Collision with terrain, Runway excursion
Highest injury level None
Brief release date 22/09/2025

Aircraft details

Manufacturer Cessna Aircraft Company
Model 180J
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Wally’s Airstrip, Katherine, Northern Territory
Destination Borroloola Aerodrome, Northern Territory
Damage Substantial

Ditching involving a Just Aircraft SuperSTOL XL, 155 km north-west of Cooktown Airport, Queensland, on 14 August 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 14 August 2025, a Just Aircraft SuperSTOL XL amateur-built aircraft departed from Weipa, Queensland, for a flight to Cooktown. The pilot was the sole person on board and the flight was planned to proceed via Coen with a subsequent refuelling stop, if required, using fuel carried in a container on board the aircraft. After leaving Coen, the pilot determined that refuelling was required and selected an off-airfield landing location near Bathurst Bay where, after an aerial inspection of the selected area, the pilot made an uneventful landing at the mouth of a river.

At around 1630, after refuelling and having inspected the intended take-off strip area for suitability, the pilot commenced the take-off. The pilot later reported that, shortly after clearing the ground, the aircraft encountered a strong crosswind gust from the left and the aircraft yawed forcefully into the wind. Directional control and climb performance of the aircraft was rapidly lost and the pilot ditched the aircraft in the shallow river to the left of the strip end (Figure 1). The pilot was uninjured and able to evacuate the aircraft and swim to the shore, however the aircraft became partially submerged (Figure 2) and was substantially damaged by water ingress.

Figure 1: Overview of take-off strip and accident location

Figure 1: Overview of take-off strip and accident location

Source: Google Earth, annotated by the ATSB

Figure 2: Aircraft final location after being moved by incoming tide, partially submerged 

Figure 2: Aircraft final location after being moved by incoming tide, partially submerged

Source: Pilot supplied

Safety message

Take-offs and landings away from established aerodromes and aircraft landing areas (ALAs) can present challenges and significantly increased risks for operating crew. In this instance, while the pilot was operating an aircraft designed and equipped for such off‑field work, the presence of obstacles and hazards close to the chosen strip reduced the options available to the pilot for a safe recovery or landing after the wind gusts and controllability issues were encountered. 

Pilots should also consider the shielding effects of any elevated terrain surrounding planned take-off areas and consider the potential effects of abrupt wind changes and windshear once the aircraft outclimbs the terrain.

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-2025-040
Occurrence date 14/08/2025
Location 155 km north-west of Cooktown Airport
State Queensland
Occurrence class Accident
Aviation occurrence category Collision with terrain, Loss of control, Weather - Other
Highest injury level None
Brief release date 19/09/2025

Aircraft details

Manufacturer Just Aircraft
Model SuperSTOL XL
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Bathurst Bay, Queensland
Destination Cooktown Airport, Queensland
Damage Substantial

Collision with terrain involving Air Tractor AT-802, VH-ODX, 17 km north of Cummins Town aerodrome, South Australia, on 8 September 2025

Summary

The ATSB is investigating a collision with terrain involving an Air Tractor AT-802, registration VH‑ODX, 17 km north of Cummins Town aerodrome, South Australia, on 8 September 2025.

During aerial agricultural spraying operations, the aircraft collided with terrain resulting in substantial damage. The pilot was fatally injured.

The ATSB has commenced the examination and analysis of the initial evidence collected.

To date, the ATSB has examined the site and wreckage, conducted interviews, collected documentation, and recovered recorded data from the accident flight.

A preliminary report, which detailed factual information established during the evidence collection phase, was released on 23 October 2025 (see the adjacent tab).

The investigation is continuing and will include review and analysis of the:

  • recorded data
  • aircraft documentation
  • operational records
  • pilot medical records, qualifications and their experience
  • aerial application standard practices
  • safety equipment.

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

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 8 September 2025, at about 0937 local time, the pilot in command (and sole occupant) of an Air Tractor AT‑802A agricultural aircraft, registered VH‑ODX and operated by Aerotech Australasia,[1] departed from the Cummins Town aerodrome, South Australia. The pilot ferried the aircraft to a private airstrip approximately 22 km to the north that was to be used as a supply point for the day’s aerial spraying activities. 

Having diverted slightly right of the direct track to overfly the first field to be sprayed that morning, the pilot arrived at the supply airstrip at 0946 where they were met by the loader.[2] The tasking for the day was the aerial application of 13 loads of fungicide and insecticide across 2 wheat fields (‘Field 1’ and ‘Field 2’ in Figure 1).

The aircraft was loaded with chemical and, at 1005, the flight departed for application of the first load in a field about 11 km to the south‑south‑east. Recorded data from the aircraft identified the field was sprayed in a north‑south racetrack pattern[3] until the hopper was emptied, before returning to the supply airstrip. This operation was repeated 3 times. 

Electrical powerlines spanned the fields of the property being sprayed. The first field featured a 19 kV single‑wire earth return powerline crossing the southern section in an east‑west direction (Figure 1 and Figure 2). The data showed that the pilot flew mostly under this powerline but occasionally flew over it where there was a power pole, or, where the powerline merged close to the edge of the field.

Figure 1: Fields that were sprayed (outlined in orange) and the surrounding powerline network (yellow lines)

Figure 1: Fields that were sprayed (outlined in orange) and the surrounding powerline network (yellow lines)

SWER – Single‑wire earth return. Source: Look up and Live website, annotated by the ATSB

Figure 2: 19 kV single-wire earth return powerline in one of the fields being sprayed

19kV Single wire earth return powerline

Source: ATSB

During the fourth run, the pilot completed spraying the first field, including a clean‑up run[4] along the south fence line. They then transited 5 km north and commenced spraying the second field in an east-west racetrack pattern. The pilot applied 2 loads of chemical (runs 5 and 6) to that field. Each run took between 19 minutes and 28 minutes to apply, with the pilot then returning to the supply airstrip for the aircraft to be replenished with chemical and fuel as required.

Two 19 kV single‑wire earth return powerlines were positioned in the second field and measured to be around 12 m above the ground. A north‑south powerline bisected the field, and the other powerline ran partially to the east along the northern border (Figure 3 in orange) of the field and partially to the west‑south‑west crossing the north‑west corner of the field. The recorded data showed the pilot mostly flew the aircraft under the north‑south powerline running perpendicular to the spray pass direction, except where the powerline ran adjacent to the edge of the field, where they flew over the powerline.

At about 1307, the pilot departed the supply point and continued spraying the second field. A further 9 passes were completed and approximately 16 minutes into the run, while heading west on pass 10, the pilot flew under the north‑south powerline. At this point, the west‑south‑west powerline crossed the north‑south powerline 40 m to the north (Figure 3). That spray run also aligned with a power pole on the west‑south‑west powerline, 240 m beyond the north‑south powerline. Recorded data showed the aircraft conducted a right turn underneath the second power line after which it collided with terrain at 1323. The aircraft wreckage came to rest on a farm road about 150 m beyond the second power line.

Figure 3: Final pass within field 2 showing the flight path (in blue) and accident site relative to the power lines and poles (the yellow lines and circles respectively)

Figure 3: Final pass within field 2 showing the flight path (in blue) and accident site relative to the power lines and poles (the yellow lines and circles respectively)

Source: Google Earth Pro, annotated by the ATSB

The emergency locator transmitter from the aircraft had activated, and the signal was received by the Joint Rescue Coordination Centre which contacted Airservices Australia and the operator. Call logs from the operator indicated that they were notified at 1328 by the coordination centre that the aircraft’s emergency locator transmitter had activated. Personnel from the operator and a local farm worker responded and found the aircraft wreckage at 1338. The pilot was fatally injured and the aircraft was substantially damaged. There was no fire. There were no known witnesses to the accident.

Context

Pilot information

The pilot held a Commercial Pilot (Aeroplane) Licence with a single-engine aeroplane class rating. The pilot had 3,623 hours total aeronautical experience, of which 1,243 hours were conducting agricultural aerial application and 941 hours were on the AT‑802 aircraft type. The pilot also held aerial application (with firefighting endorsement) and low-level ratings. In addition, the pilot held a gas turbine design feature endorsement, and numerous piston and turbine type ratings. 

The pilot held a valid class 2 aviation medical certificate with their class 1 medical certificate not being renewed when it expired in November 2023. For the operation being conducted, only a class 2 medical certificate was required.[5] It was reported that the pilot appeared well rested and fully alert for the flight.

Aircraft information

VH-ODX was an Air Tractor Incorporated AT-802A single-seat low-wing tailwheel, fixed landing gear aircraft manufactured in the United States in 2006. It was powered by a Pratt & Whitney Canada PT6A-67AG turboprop engine. It was first registered in Australia in August 2006. The aircraft was configured for aerial spraying, with the spray boom fitted under each wing, aft of the trailing edge, and extending about three-quarters of the wingspan (exemplar shown in Figure 4).

Figure 4: Exemplar AT-802 showing spray boom installation

Figure 4: Exemplar AT-802 showing spray boom installation

The above image has been modified to remove the registration and other markings. Source: ATSB

The current maintenance release was issued on 30 July 2025. On the day of the accident, the maintenance release indicated the aircraft had 5,595.4 hours recorded as the total time in service. 

The aircraft was fuelled from 2 stainless steel transport tanks located on the loader’s truck, which included a single-point filter. A fuel sample, taken from the tanks at Cummins Town aerodrome on 10 September 2025, was observed to be free from water and contaminants.

Meteorological information

The Bureau of Meteorology operated a weather station at Cummins Town aerodrome, 17 km to the south of the accident site, which recorded wind and temperature at 30‑minute intervals. Around the time of the accident, the recorded winds were 11 kt from the west and the temperature was 19°C.

The loader reported the weather at the time of the accident to be clear and sunny with a light westerly breeze.

Wreckage and impact information

Witness marks matching the right wheel, right spray boom and right wingtip indicated they had passed through the approximately 0.5‍–‍1.0 m high wheat crop 260 m prior to the accident site, with the right wheel running along the ground for about 22 m (Figure 5). The crop markings started on a heading of 264° (magnetic) and finished just beyond the west‑south‑west powerline on a heading of 273° after about 125 m. The markings showed that the aircraft was in a significant right skid. Later in the crop markings, the right aileron also left a mark indicating a significant down (left roll) deflection. 

Another crop and ground scar from the aircraft had been produced 88 m beyond the initial markings that continued to the wreckage (‘Impact with terrain’ to ‘Aircraft wreckage’ labels in Figure 5). Numerous indicators such as component locations in the debris field, orientation of wheat strands caught in the aircraft structure, and damage signatures to the airframe indicated the aircraft impacted terrain in an inverted orientation, left wing first at a near wings‑level and nose‑down attitude.

Figure 5: Crop witness marks at the accident site 

Figure 5: Crop witness marks at the accident site

Source: ATSB

All major aircraft components were accounted for at the accident site (Figure 6). There was no evidence of pre‑impact defects with the flight controls or aircraft structure. The propeller assembly separated from the engine during the impact sequence and was located on the farm road, about 18 m behind the front of the fuselage. Two propeller blades had ejected from the propeller hub and one blade had fractured mid‑length. The damage sustained to the propeller assembly was consistent with the engine operating at the time of the ground impact. The wing integral fuel tanks had ruptured during the accident sequence. A residual aroma from spilled fuel was detected at the accident site that persisted for several days. 

Figure 6: VH-ODX wreckage

Figure 6: VH-ODX wreckage

Source: ATSB

Recorded information

A TracPlus RockAIR portable tracking device had been fitted to the aircraft and was recovered from the accident site. The device was transferred to the ATSB’s technical facilities in Canberra, Australian Capital Territory, where it was interrogated. The recorded data provided the aircraft’s position, altitude, speed and track angle data at 1‑second intervals up until the time of the accident (Figure 7). The data showed the take‑off from Cummins Town aerodrome, the transit to and from the supply airstrip and the completed spray runs in fields 1 and 2. Location and time parameters from the flight data were correlated to identify that the accident occurred at 1323:40.

Figure 7: TracPlus RockAIR broadcast data for VH-ODX on 8 September 2025

Figure 7: TracPlus RockAIR broadcast data for VH-ODX on 8 September 2025

Source: TracPlus RockAIR broadcast data on Google Earth Pro, annotated by the ATSB

To assist with aerial application tasks, a Tabula AirVision agricultural application system was fitted to the aircraft. The system had the capability to record parameters such as position and application information. It could also provide live fleet tracking. The unit was recovered from the aircraft and retained by the ATSB for further investigation.

A Perkins Data Acquisition Alarm Monitor was recovered from the aircraft and retained by the ATSB for further investigation. A Replay XD 1080 video camera mount in the cockpit was also recovered. Data extracted from unit contained about 30 GB of good quality video, however, the last recording was from 2016.

Further investigation

To date, the ATSB has examined the site and wreckage, conducted interviews, collected documentation, and recovered recorded data from the accident flight.

The investigation is continuing and will include review and analysis of the:

  • recorded data
  • aircraft documentation
  • operational records
  • pilot medical records, qualifications and their experience
  • aerial application standard practices
  • safety equipment.

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 would like to acknowledge the assistance of the South Australia Police during the onsite stages of the investigation.

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

CC BY logo

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]     The flight was conducted under Part 137 of the Civil Aviation Safety Regulations (aerial application operations).

[2]     Loader: the term used to denote ground support personnel whose functions include assisting with mixing chemicals, loading and dispatching the aircraft.

[3]     Racetrack pattern: the application pattern that involves making successive overlapping loops across a field.

[4]     Pilots delay the commencement of spraying and prematurely shut off spraying at the end of a field to ensure the chemical does not get applied to an adjacent field. A clean‑up run is a spray pass perpendicular to the predominant direction along the edge of a field to ensure crop near that fence line has appropriate coverage.

[5]     Civil Aviation Safety Authority exemption EX28/23, in effect at the time of the accident, exempted the pilot from needing to hold a class 1 aviation medical certificate for aerial application flights such as the accident flight. The exemption was subject to the pilot holding a class 2 medical certificate.

Occurrence summary

Investigation number AO-2025-053
Occurrence date 08/09/2025
Location 17 km north of Cummins Town aerodrome
State South Australia
Report release date 23/10/2025
Report status Preliminary
Anticipated completion Q2 2026
Investigation level Short
Investigation type Occurrence Investigation
Investigation phase Examination and analysis
Investigation status Active
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Air Tractor Inc
Model AT-802A
Registration VH-ODX
Serial number 802A-0243
Aircraft operator Aerotech Australasia Pty Ltd
Sector Turboprop
Operation type Part 137 Aerial application operations
Departure point Cummins Town aerodrome, South Australia
Destination Cummins Town aerodrome, South Australia
Damage Substantial

Partial wheels up landing involving a Lancair IV amateur-built aircraft, Orange Airport, New South Wales, on 4 August 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 4 August 2025, an amateur-built Lancair IV departed Orange Airport, New South Wales, at 0652 local time, intending to fly to Bankstown Airport.

During cruise, the aircraft sustained an electrical system failure, resulting in numerous electrically driven systems failing. The pilot then made the decision to conduct an air return to Orange Airport, rather than continue the flight towards Bankstown. 

Orange Airport consists of primary runway 11/29 which is 2,213 m long and is a sealed surface with a secondary runway 04/22 which is a 964 m long unsealed surface. 

Due to the electrical malfunction, several systems of the aircraft were impacted, including the landing gear and VHF radio communication systems. The pilot used their mobile phone to communicate with a ground station to aid in facilitating their arrival at Orange Airport. 

As the landing gear system is electrically controlled and hydraulically operated, due to the electrical failure, the primary method of the gear extension was not functional. 

During the initial approach to the primary runway, the pilot manually selected the landing gear ‘down’ to extend the landing gear. Once manually selected ‘down’, the undercarriage extension indicator showed that only the nose gear had locked ‘down’, indicating (green), with the main gear, not indicating that it had ‘locked’ down (Figure 1).

Figure 1: Generic representation of landing gear selection

Picture showing a generic representation of landing gear selection positions and indications in cockpit.

Source: ATSB representation of landing gear selection and indication. May not be indicative to type of aircraft.

The pilot proceeded to conduct several low passes of the runway to try to ascertain the condition of the landing gear with people on the ground. 

However, after not being able to confirm the gear was fully down and locked, the pilot then made the decision to conduct a precautionary landing on the non-sealed cross strip, runway 04.

The pilot conducted the approach and landed, however on touchdown the main undercarriage legs collapsed, and the aircraft slid on the nosewheel (front of the aircraft) and rudder (rear of the aircraft) before coming to rest at the fence at the end of the runway. 

The aircraft incurred some minor damage (Figure 2) to the wingtip and elevator with no injuries to the pilot.

Figure 2: Damage to aircraft

Picture of damage to the aircraft post-occurrence.

Source: Operator, annotated by the ATSB

Subsequent engineering inspections found the electrical system had failed due to a defective voltage regulator.

Safety message

This occurrence illustrates that a good knowledge of aircraft systems coupled with sound decision‑making can help facilitate a positive outcome to an emergency.

Aircraft rely on hydraulic or electrical systems to extend and retract the landing gear. Should any component in these systems fail, pilots may be left with no choice but to manually extend the undercarriage or potentially execute a wheels-up landing.

Applying a structured and proactive approach to identifying and managing threats and errors, influences the safety of the flight.

In this instance, the pilot was able to identify the aircraft system failure and make several calculated risk-based decisions to manage the emergency. This was achieved by using various resources at their disposal, such as their mobile phone, to seek ground assistance in the absence of normal VHF radio. 

In emergency situations, pilots need to utilise all the available resources at their disposal. Maintaining a degree of flexibility and adapting to select the most appropriate landing area can minimise risk, limit damage and maximise survivability. 

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-2025-039
Occurrence date 04/08/2025
Location Orange Airport
State New South Wales
Aviation occurrence category Collision with terrain, Diversion/return, Electrical system, Landing gear/indication, Runway excursion, Wheels up landing
Highest injury level None
Brief release date 08/09/2025

Aircraft details

Manufacturer Amateur Built Aircraft
Model Lancair IV
Sector Piston
Operation type Part 91 General operating and flight rules
Departure point Orange Airport, New South Wales
Destination Bankstown Airport, New South Wales
Damage Minor