Collision with terrain

Collision with terrain involving Piper PA-25, VH-SEH, Seaview, Victoria, on 23 February 2022

Preliminary report

Preliminary report released 28 June 2022

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 23 February 2022, at about 0650 Eastern Daylight-saving Time,[1] the pilot of a Piper Aircraft Corporation PA-25-235/A9, registered VH-SEH, departed Leongatha Aerodrome, Victoria, for a positioning flight about 25 km north to a private landing area[2] at Seaview.

The aircraft landed at about 0700 in preparation for aerial spreading of superphosphate pellets. The loader driver[3] arrived shortly after, finding that the loader’s bucket had been pre-filled by the pilot. The loader driver transferred the superphosphate to the aircraft’s hopper with the pilot on board. The loader driver could not later recall how much superphosphate had been loaded.

The loader driver then parked the loader at the southern end of the landing area and prepared for the next load. A short time later, the pilot started the aircraft’s engine and remained at the southernmost point of the landing area for about 5 minutes.

Based on local weather observations and a video recording made by a nearby witness, the weather at the time of the accident was fine with the wind likely calm.

Data from an onboard GPS showed that the pilot commenced the take-off on the prepared runway strip at about 0711 (Figure 1). According to witnesses and the recorded video, the aircraft accelerated along the prepared strip and traversed the right section where the strip split into 2 directions. The aircraft briefly became airborne at a point at the end of the strip, where the terrain dropped away, before the outboard section of the aircraft’s left wing impacted trees. The aircraft rolled to the left, pitched down, and collided with terrain about 30 m north of the trees (Figure 2). The pilot was fatally injured and the aircraft was destroyed.

Figure 1: Landing area overview

Figure 1: Landing area overview

Source: ATSB

Figure 2: Landing area overview showing approximate lift-off point, impact with trees and ground impact point

Figure 2: Landing area overview showing approximate lift-off point, impact with trees and ground impact point

Source: ATSB

Context

Pilot information

The pilot held a valid class 1 aviation medical certificate and a commercial pilot licence (aeroplane), having completed a flight review on 30 October 2020 and a proficiency check on 11 November 2021. At the time of the accident, the pilot had about 12,350 hours total aeronautical experience.

The pilot was the operator’s owner and chief pilot.

Aircraft information

The aircraft was a Piper Pawnee PA-25-235/A9 with a 6-cylinder, normally-aspirated Textron Lycoming O-540-H2A5 engine driving a 2-blade McCauley Propellers 1A200/FA8452 fixed-pitch propeller (Figure 3).

Figure 3: Another Piper PA-25-235/A9 configured for agricultural spreading

Figure 3: Another Piper PA-25-235/A9 configured for agricultural spreading

Source: ATSB

The aircraft’s hopper could hold up to about 700 kg of superphosphate pellets, but its maximum permissible hopper load was 544 kg (considered a full load by the operator’s other pilots). There was a clear section in the cockpit to enable the pilot to see how much volume of product was in the hopper.

The exact volume or weight of superphosphate loaded into the aircraft’s hopper could not be determined. The operator’s other pilots reported that it was normal to take a full load of superphosphate on the first flight from a landing area unless weather and strip surface conditions were unfavourable. In these scenarios, the pilot could opt to take a half load as a first flight.

Landing area

The landing area was normally used for cattle grazing and was prepared as a landing area for aerial application operations once a year. The pilot had not operated from the landing area since 2019.

The prepared strip had been mowed into a ‘Y’ configuration by the pilot in the days before the accident. It consisted of mowed grass and the surface was rough from previous cattle movement in wet soil. The strip was about 360 m in length and followed the natural terrain, with a downwards then upwards slope before the terrain dropped steeply towards a stand of trees about 60 m from the northernmost end of the strip. The left of the ‘Y’ was oriented to the left of the trees and the right of the ‘Y’ was oriented directly towards the trees (Figure 4).

Figure 4: Runway strip Y intersection showing the left and right take-off options with the trees at the runway’s end

Figure 4: Runway strip Y intersection showing the left and right take-off options with the trees at the runway’s end

Source: ATSB

Site and wreckage

The ATSB conducted an on-site examination of the aircraft wreckage (Figure 5). The aircraft impacted the ground inverted with an angle of entry of about 50°. There were no evident pre-impact defects with the flight controls or aircraft structure, and external examination of the engine did not identify any obvious defects. The propeller damage was indicative of the engine driving the propeller with significant power at impact. Preliminary audio analysis of the witness video indicated that the engine was at or close to its maximum rotational speed throughout the take-off.

Figure 5: Wreckage of VH-SEH

Figure 5: Wreckage of VH-SEH

Source: ATSB

Further investigation

The investigation is continuing and will include:

  • pilot records
  • aircraft records
  • aircraft weight and balance
  • aircraft take-off performance
  • further analysis of the witness video recording and downloaded GPS data.

Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.

A final report will be released at the conclusion of the investigation.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. Eastern Daylight-saving Time (EDT): Coordinated Universal Time (UTC) + 11 hours.
  2. Landing area: a place, whether or not an aerodrome, where an aeroplane is able to take off and land.
  3. Loader driver: an operator of loading equipment to support aerial application operations.

Final report

Executive summary

What happened

On the morning of 23 February 2022, a Piper Aircraft Corporation PA-25-235/A9, registered VH‑SEH, was conducting agricultural spreading operations from a private landing area located near Seaview, Victoria. At 0711, the pilot commenced take-off for the first load of the day. The aircraft accelerated along the prepared strip and briefly became airborne. The outboard section of the aircraft’s left wing impacted trees and detached from the aircraft. The aircraft rolled to the left, pitched down, and collided with terrain. The pilot, who was the sole occupant, was fatally injured and the aircraft was destroyed.

What the ATSB found

The ATSB found that the take-off was attempted at an aircraft weight that likely did not permit sufficient performance to clear the trees at the end of the strip. Although the pilot had conducted take-offs using the Seaview runway strip in previous years, the increased height of trees at the northern end of the strip were found to have reduced safety margins to some extent.

It was also identified that engine power during take-off may have been slightly lower than normal. This may have been due to the water content of the air, carburettor ice, or the carburettor heat selector may have been inadvertently left on during the take-off. However, a conclusion regarding the existence of these scenarios could not be drawn with any certainty.

The ATSB also found that the pilot likely initiated a jettison of the hopper contents shortly after becoming airborne, but any effect this had on the aircraft’s performance was probably negligible.

Safety message

Aircraft operators and pilots are reminded of the hazards associated with operations from small landing areas that are not prepared as permanent runways. In any case, pilots should ensure aircraft loads are within specified limits, appropriate for the environmental conditions, and will result in the required performance to maintain safety margins.

The investigation

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

The occurrence

On 23 February 2022 at about 0650 local time, the pilot of a Piper Aircraft Corporation PA-25-235/A9, registered VH-SEH, departed Leongatha Aerodrome, Victoria, for a positioning flight to a private landing area[1] situated 25 km to the north in the locality of Seaview. The aircraft was reportedly carrying full fuel (170 L) prior to take-off.

The aircraft landed at about 0700 in preparation for the aerial spreading of superphosphate pellets. The pilot had been tasked to spread 41,000 kg of superphosphate fertiliser at 6 nearby properties. It was anticipated this would take about 80 loads and 8 hours to complete.

The loader driver[2] for the day’s activities arrived at the Seaview landing area at about 0705. On arrival, the loader driver found VH‑SEH parked with the engine stopped and the pilot out of the aircraft. The pilot had filled the loader’s bucket with superphosphate prior to the arrival of the loader driver.

The loader driver and the pilot had a short conversation and the pilot returned to the aircraft. The loader driver transferred the superphosphate to the aircraft’s hopper with the pilot on board the aircraft. The loader driver could not see how much superphosphate had been loaded into the bucket, and the weighing system in the loader only indicated weight at the time of filling the bucket.

The loader driver then parked the loader at the southern end of the landing area and prepared for the next load. A short time later, the pilot started the aircraft’s engine and remained at the southernmost point of the landing area for about 5 minutes.

Based on local weather observations and a witness’s video recording of the take-off, the weather at the time of the accident was fine with the wind likely calm. The loader driver described the weather conditions at the time as good.

According to witness reports, the pilot was wearing a 4-point harness and a helmet. Data from an onboard GPS device showed that the pilot commenced the take-off on the prepared runway strip at about 0711 (Figure 1).

The runway strip went downhill, and then uphill, where it branched into 2 sections. According to the 2 witnesses and the recorded video, the aircraft accelerated along the strip and traversed the right section where the strip divided.

The aircraft briefly became airborne at a point at the end of the strip where the terrain dropped away. The outboard section of the aircraft’s left wing then impacted trees and separated the left outboard section of wing. The aircraft rolled to the left, pitched down, and collided with terrain about 30 m beyond the trees (Figure 2). The pilot was fatally injured and the aircraft was destroyed.

Figure 1: Runway strip overview

Figure 1: Runway strip overview

Source: ATSB

Figure 2: End of runway strip and impact points

Figure 2: End of runway strip and impact points

 Source: ATSB

Context

Pilot information

The pilot held a valid class 1 aviation medical certificate and a commercial pilot licence (aeroplane), having completed a flight review and an aerial application proficiency check on 11 November 2021. At the time of the accident, the pilot had about 12,350 hours total aeronautical experience. The pilot was the owner and chief pilot of the aerial work operator, which conducted mostly aerial application activities.

The pilot was reported to be fit and healthy and there was no indication they were experiencing a level of fatigue known to affect performance. The post-mortem and toxicology examinations did not identify any indicators of incapacitation or substances that could have affected the pilot’s capacity to perform the flight.

Aircraft information

General information

The aircraft was a 2-seat Piper Pawnee PA-25-235/A9 with a 6-cylinder, normally aspirated Textron Lycoming O-540-H2A5 engine driving a 2-blade McCauley Propellers 1A200/FA8452 fixed-pitch propeller (Figure 3). This propeller was designed for increased efficiency during cruise compared with other propeller options, but also resulted in decreased climb performance and increased the take-off distance required. The propeller was first installed on the aircraft in March 2019.

Figure 3: A similar Piper PA-25-235/A9 configured for agricultural spreading

Figure 3: A similar Piper PA-25-235/A9 configured for agricultural spreading

Source: ATSB

The aircraft was originally manufactured as a single-seat PA-25-235 in 1974. In 1988, the aircraft was involved in an accident while conducting herbicide spraying near Deddick Park, Victoria. The outboard section of the right wing collided with a tree. The aircraft climbed steeply then descended in a nose-down attitude and impacted terrain.[3]

In 1989, the aircraft was rebuilt and converted to an ‘A9’ variant. This conversion included the installation of a second seat (in a side-by-side configuration), replacement of the fabric-covered wings with metal wings, the installation of a larger chemical hopper, and the fitment of a larger Lycoming O-540-H2A5 engine. Flying controls were on the left side.

The engine was last overhauled in March 2021, and the last periodic inspection was carried out in July 2021 with no defects recorded. At the time of the accident, the aircraft had accumulated 9,543.5 hours total time in service, and the engine had accumulated 159 hours since overhaul.

Aircraft hopper

The hopper was located between the instrument panel and the engine firewall. It was constructed from fiberglass and had a 544 kg maximum permissible load. Its volume (200 gallons, or 757 L) was sufficient to hold up to about 800 kg of superphosphate pellets. There was a clear section in the cockpit, with graduations in gallons, to enable the pilot to see how much volume of product was in the hopper.

The quantity of superphosphate on board the aircraft during the take-off could not be determined. Those familiar with the recent operating practices of the pilot of the accident flight reported that, if weather and strip surface conditions were favourable, it was normal for the pilot to take a full load of superphosphate on the first flight from a landing area. Otherwise, the pilot would normally opt to take a reduced load on a first flight. A typical reduced load for this pilot was reported as being about 400 kg.

The aircraft was fitted with an emergency hopper dump mechanism. The mechanism allowed a pilot to dump all or part of the hopper contents if the aircraft did not achieve the required performance. To do so, the pilot would push a button on the spread/dump lever (to enable the lever to move past a gate) and move the lever past the spread selection to the full forward position. This would fully open the hopper door located on the underside of the aircraft fuselage. A full load of superphosphate was expected to completely jettison in about 4 seconds. Dumping the hopper load would significantly, and almost immediately, reduce the aircraft’s weight and increase performance.

The total elapsed time from the aircraft becoming airborne to impacting the trees was 2 seconds.

Performance

The approved flight manual for VH‑SEH contained take-off performance charts that could be applied to calculate a performance-limited maximum take-off weight using aircraft and environmental parameters for a given flight. These charts included a wet or dry surface and long or short grass. Such charts had reduced applicability for landing areas with significant changes in slope, and rough surface conditions were not captured by the charts. The aircraft operator’s operations manual (OM) contained the responsibilities for company pilots. The OM stated:

In determining that an operation can be conducted safely, the pilot will consider:

 

a) carriage of heavier than manufacturers’ recommended weights

b) strip length and conditions, particularly in relationship to the performance parameters of the particular aircraft used by the Company

c) strip altitude and density altitude

d) wind speed and direction, especially any downwind component

e) obstacles

The OM also stated:

Pilots are responsible for the safety of the aircraft. Many accidents have loading as a causal factor. That is, the aircraft may have flown off the same landing area with the same load but slightly different environmental conditions. The decision to dump a load may be relatively cheap when compared to repairing an aircraft. The ability to dump the load is the last line of defence in the accident chain but it remains a very good defence and should be used as required. Pilots should make a conscious decision on each take off about how much load they will take and at what stage they will either abort take-off or dump the load in the event that the aircraft fails to become airborne at the expected time. To make this decision, pilots should have firmly in their mind where the aircraft should get airborne.

The ATSB undertook performance calculations using known and estimated aircraft and environmental information, including fuel and hopper loads. It was estimated that the aircraft was probably near the performance-limited maximum take-off weight for a level (no slope) strip the same length as the actual strip, without any load in the hopper. Using an estimated weight range for the hopper load of 400–544 kg, the aircraft would have been over the performance-limited maximum take-off weight for an equivalent-length level strip. This range of hopper loads would have resulted in a take-off weight of about 1,400–1,544 kg. The aircraft’s maximum take-off weight was 1,315 kg.

Carburettor heat

Carburettor icing occurs when water vapour freezes within an engine’s carburettor due to a decrease in temperature and pressure within the carburettor. The likelihood of carburettor icing increases with humidity and at partial power settings (for example, when idling). If ice accumulates within a carburettor, the flow of air to the engine (and, ultimately, available power) reduces.

A carburettor heat control was available in VH‑SEH. When selected, warm air was directed from a heat exchanger on the exhaust system to the carburettor inlet, melting any ice in the carburettor. The operator’s other pilots reported that it was standard practice to apply carburettor heat during ground operations, selecting it off just prior to commencing the take-off. The purpose of this practice was to prevent carburettor ice build-up during engine idling.

It was reported that the application of carburettor heat in VH‑SEH would result in a propeller speed reduction of about 100 RPM and, if inadvertently left on during take-off, would significantly increase the take-off distance required. Due to the level of damage, the ATSB could not determine the position of the carburettor heat control at the time of the accident or whether carburettor icing occurred during the take-off.

Water vapour and engine performance

High concentrations of water vapour within the air (a high relative humidity) can impact engine performance. The water vapour alters the fuel to air ratio, causing enrichment, as well as reducing the burning and cooling efficacy of the engine. This reduces the power output of engine and may increase the take-off distance required. The ATSB could not determine the relative humidity at the landing area at the time of the accident (see also Weather information).

Runway strip

The runway strip at Seaview was prepared annually for aerial agricultural operations by the operator of VH‑SEH. The prepared strip had been mowed into a ‘Y’ configuration by the pilot of the accident flight in the days before the accident. It consisted of mowed grass and the surface was hard and rough from previous cattle movements. The strip was at an elevation of about 1,100 ft above mean sea level (AMSL) and each branch provided about 360 m take-off and landing distance on the ground.

Take-offs were always conducted in the same direction due to the more downwards slope. In this direction, the strip followed the natural terrain, with a downwards then upwards slope before dropping steeply towards the stand of trees. The left branch was oriented to the left of the trees and the right branch was oriented directly towards the trees (Figure 4).

Figure 4: Runway strip ‘Y’ intersection showing the left and right branches with the trees at the runway’s end

 Runway strip ‘Y’ intersection showing the left and right branches with the trees at the runway’s end

Source: ATSB

The pilot had not operated from this strip for at least 2 years prior to the accident. It was reported that the trees at the end of the strip had grown about 3–10 ft during that time. The pilot was reportedly aware of the hazard presented by the trees, having commented on their growth over the years. In the days prior to the accident, the pilot had communicated their intent to use the right side of the prepared strip for the day’s operations. Another of the operator’s pilots reported preferring the left branch of the strip in order to avoid the trees. The reasons for the accident pilot’s preferred use of the right branch could not be determined.

Site and wreckage

The wreckage was located about 30 m north of the stand of trees at the northernmost end of the strip. The trees were about 90 ft in height above ground level (AGL). Damage to the trees indicated the left wing impacted the trees at a height of about 74 ft AGL. Examination of the accident site indicated the aircraft impacted the ground inverted with an angle of entry of about 50° with the left wing low, and came to rest about 8 m from the initial impact point. The cabin sustained significant damage (Figure 5). Significant curved compression damage was evident on the leading edge of the left wing consistent with tree impact damage (Figure 6).

Figure 5: Aircraft wreckage

Figure 5: Aircraft wreckage

Source: ATSB

Figure 6: Outboard section of left wing with tree impact damage

Figure 6: Outboard section of left wing with tree impact damage

Source: ATSB

The hopper door was open, and superphosphate had spilled from the hopper with most in the vicinity of the fuselage. Superphosphate was also found in smaller quantities near the initial impact point with the trees and scattered from halfway between the aircraft’s point of take-off to the wreckage site. The scattered pellets were consistent with a pilot-initiated release (and not post-impact scatter); however, it could not be determined if the mechanism had been activated in the spread or emergency dump position. The position of the spread/dump lever at the time of impact could not be determined.

Examination of the propeller, along with ground marks, indicated the propeller was rotating under power at the time of impact.

External examination of the engine did not identify any obvious defects. The engine tachometer displayed a needle ‘slap mark’[4] indicating about 2,240 RPM.[5] The throttle position at the time of impact could not be determined due to disruption of the controls.

There were no evident pre-impact defects with the aircraft structure and flight control continuity was confirmed as far as possible. The flap handle was in the top notch, indicating full flap. The operator’s other pilots reported that it was normal practice to apply full flap at the lift-off point, followed by a gradual reduction of flap setting as the aircraft climbed away.

ATSB analysis (based on estimates of the aircraft’s speed, impact angle and damage to the aircraft) indicated the impact forces for this type of accident would normally be expected to result in fatal injuries irrespective of any safety equipment worn.

Weather information

Recorded meteorological data for the landing area was not available. The weather conditions captured on the video recording made by a nearby witness included no cloud, visibility greater than 10 km and wind calm.

At the time of take-off, there was no fog at the landing area, there was a layer of fog in a nearby valley below the landing area. Given the proximity of the fog (saturated airmass), it indicates that conditions conducive with reduced engine performance and/or carburettor icing may have been present at the landing area. Recorded information

Accident video

The video recording captured by the witness was 30 seconds in length and commenced 6 seconds prior to the initiation of the take-off roll, ceasing 1 second after the aircraft impacted trees. No anomalies were evident in engine sound recorded on the video, such as rough running or power reduction during the take-off roll.

Audio spectrogram analysis of the video recording indicated that the aircraft’s propeller speed was likely about 2,357–2,587 RPM during the take-off roll, and this was maintained until the collision with the trees. The operator’s other pilots indicated that a typical propeller speed for VH‑SEH during take-off was about 2,500 RPM.

Global positioning system

A Tracmap Aviation TMA384 GPS device was recovered from the accident site and the stored data was downloaded. The data captured the aircraft’s arrival at the Seaview landing area, and the moments prior to take-off, but the device did not capture the subsequent take-off or the accident sequence. This was probably due to power supply disconnection during impact, preventing data being written to the memory card.

Safety analysis

The accident flight was the first load of the day and the aircraft had almost full fuel on board. Although the amount of superphosphate loaded onto the aircraft could not be determined, it was likely that the aircraft’s weight exceeded the performance-limited maximum take-off weight for the strip as well as the aircraft’s documented maximum take-off weight. This likely degraded the aircraft’s take-off performance significantly and contributed to the aircraft being unable to clear the stand of trees downslope of the lift-off point.

Additionally, the tachometer slap mark and the audio spectrogram analysis of the video recording indicated the power generated by the engine during the take-off may have been slightly lower than normal. No obvious defects were identified with the engine and the propeller was rotating under power at the time of impact. The relative humidity at the time of take-off could not be established. However, it is possible the aircraft’s engine performance was negatively impacted by the volume of water present within the air, affected by carburettor ice, or the carburettor heat selector may have been inadvertently left on during the take-off. Although these scenarios could explain a reduced propeller speed, there was insufficient evidence available to determine whether these events took place.

Although the pilot had conducted take-offs using the Seaview runway strip in previous years, the increased height of trees at the northern end of the strip had reduced safety margins to some extent. The aircraft struck the trees about 16 ft from the top, which meant that even without their estimated 3–10 ft extra height, there would not have been sufficient clearance for a safe take-off.

The investigation was unable to determine why the pilot elected to prepare, and use, a strip orientated directly towards the trees when an alternate take-off option was available.

A limited number of superphosphate pellets were found scattered between the aircraft’s point of take-off and the location where the aircraft impacted the ground. This indicated the pilot likely attempted to jettison the hopper contents around the time of becoming airborne. However, the effect this jettison would have had on the aircraft’s performance was probably insufficient for it to clear the trees, given that it would have had to gain about 16 ft in 2 seconds with some of the load still on board.

Findings

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

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

From the evidence available, the following findings are made with respect to the collision with terrain involving Piper PA-25, VH-SEH, near Seaview, Victoria, on 23 February 2022.

Contributing factors

  • The take-off was attempted at an aircraft weight that did not permit sufficient performance to clear a stand of trees downslope of the lift-off point. As a result, the aircraft impacted the trees and collided with terrain.

Other factor that increased risk

  • Although successful take-offs had been made using the prepared strip in previous years, the increased height of trees at the end of the strip reduced the safety margins over time.

Other findings

  • The pilot likely attempted to jettison the hopper contents shortly after becoming airborne. However, the jettison would have only been partially completed by the time the aircraft collided with the trees, and there had probably been insufficient time for the aircraft to gain enough height to clear them in the intervening period.

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • Bureau of Meteorology
  • operator, 2 of the operator’s other pilots and loader driver
  • Civil Aviation Safety Authority
  • Victoria Police
  • maintenance organisation
  • witness and witness video.

Submissions

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

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

  • the Civil Aviation Safety Authority
  • the operator.

A submission was received from a party familiar with the operator’s activities. The submission was reviewed and, where considered appropriate, the text of the report was amended accordingly.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2023

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

[1]     Landing area: a place, whether or not an aerodrome, where an aeroplane is able to take off and land.

[2]     Loader driver: an operator of loading equipment to support aerial application operations.

[3]     ATSB investigation 198801404, Piper PA25-235 (Pawnee), VH-SEH, "Deddick River" (24 km NE of Gelantipy) Victoria, 9 November 1988.

[4]     Needle slap mark: an imprint made on the gauge face by the instrument’s needle at time of impact.

[5]     The propeller speed prior to the aircraft impacting the terrain would have been higher than indicated by the slap mark due to the slowing of the engine during the impact sequence, as well as the angle of impact tending to push the needle left just before making the mark.

Occurrence summary

Investigation number AO-2022-008
Occurrence date 23/02/2022
Location 13.7 NM north of Leongatha
State Victoria
Report release date 19/01/2023
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Piper Aircraft Corp
Model PA-25-235/A9
Registration VH-SEH
Serial number 25-7405565
Aircraft operator Super Planes Pty Ltd
Sector Piston
Operation type Part 137 Aerial application operations
Departure point Seaview, Victoria
Destination Seaview, Victoria
Damage Destroyed

Drive shaft failure and loss of control involving Garlick Helicopters UH-1H, VH-UHX, 36 km north of Launceston, Tasmania, on 14 February 2022

Preliminary report

Preliminary report released 29 April 2022

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 pilot of a Garlick Helicopters UH-1H, registered VH-UHX, was tasked by the Tasmania Fire Service (TFS) to provide fire-fighting support to combat the ‘Labrina’ bushfire, centred approximately 34 km north of Launceston, Tasmania. Over the period 10‑13 February 2022, the pilot flew multiple aerial fire‑bombing operations over the fire-ground from a temporary staging area established along Pipers Brook Road. At the conclusion of each of these days the helicopter was flown to the south of Launceston and hangered at the pilot’s residence.

On 14 February 2022, at about 0833 Eastern Daylight‑saving Time,[1] the pilot departed toward the ‘Labrina’ fire-ground. Onboard GPS data showed that the helicopter tracked toward the staging area before diverting to the north-east sector of the fire-ground to conduct firebombing operations. Those operations were conducted using a water bucket attached underneath the cabin via a 140 ft long-line (the underslung bucket). After completing those sorties, the pilot returned to the staging area and landed, shutting down the helicopter at 0929.

At 1510, the pilot departed the staging area after receiving further tasking from TFS that a localised hot-spot had developed. The hot-spot had been identified by TFS fire commanders that were providing air attack supervision overhead the fire ground in an Airbus Helicopters AS350 helicopter, registered VH-RLR (designated Firebird 460). Onboard GPS data indicated that about 2 minutes after departure, VH-UHX entered a hover over a small dam where the pilot filled the underslung bucket.

Those onboard Firebird 460 observed VH-UHX approach the identified fire hot-spot and witnessed the release of the water load from the underslung bucket. The pilot of Firebird 460 recounted that the drop was unusual because the water missed the target (Figure 1). VH-UHX was then observed by those onboard Firebird 460 to commence a gradual left turn and track away from the staging area. Suspecting the pilot of VH-UHX was encountering an in-flight difficulty and wanting to avoid any potential conflict with the approaching helicopter, the pilot of Fireboard 460 initiated a climbing 360° turn away from VH-UHX.

A witness positioned at the staging area, who had also been monitoring VH-UHX, observed the pilot depart in the helicopter, fill the underslung bucket in a nearby dam and then track toward the hot-spot. On release of the water, the witness also identified that the load had missed the target. They then observed the helicopter commence a descending profile, enter a hover and then rapidly yaw twice, before descending from view below the tree line.

After completing the 360° turn the Firebird 460 pilot trailed VH-UHX and observed the helicopter descend toward an open paddock where it impacted the terrain. Throughout this monitoring phase, the Firebird 460 pilot did not detect any radio calls issued from VH-UHX. The Firebird 460 pilot landed adjacent to the wreckage and alighted along with the passengers to provide assistance. They reported that the helicopter was on its left side and was substantially damaged. A fuel-fed fire spread rapidly and despite attempts to extinguish the fire it was unable to be contained. Two other pilots who were positioned with their helicopters at the TFS staging area also responded to the emergency and proceeded to the accident site to supply aerial suppressant to the fire. The pilot of VH-UHX sustained fatal injuries and the helicopter was destroyed.

Figure 1: VH-UHX photographed by a witness onboard Firebird 460 completing the aerial water drop away from the identified hot-spot

picture1-ao-2022-006.png

Source: Rod Sweetnam, amended by ATSB

Wreckage and impact information

The helicopter wreckage was located in an open paddock near Pipers Brook Road, about 2.6 km north of the TFS staging area. It had been destroyed from exposure to ground impact forces and the subsequent fuel-fed fire. A survey of the accident site showed that the helicopter had impacted the ground along a westerly flight track. Ground scars at the site showed that the tail section made first contact with the ground, followed by the skids, main rotor blades and the cabin (Figure 2).

Almost the entire tail section, including the tail rotor gearbox, separated from the fuselage, and had come to rest a short distance from the main wreckage. Other items that separated from the helicopter included both main rotor blades, the battery and the landing skids. The furthest item from the accident site was the underslung bucket that remained attached to its long line. The bucket and line had been released from the helicopter prior to the ground impact and were positioned approximately 300 m from the wreckage.

Figure 2: Accident site

picture2-ao-2022-006.png

Source: ATSB

Aircraft information

The accident helicopter was manufactured as a UH-1H by Bell Helicopters in November 1965 for the United States (US) military and was converted by Garlic Helicopters for civilian application in November 2007 (Figure 3). The helicopter had a two-blade main rotor and two-blade tail rotor and was powered by a Honeywell Aerospace (formally Lycoming Engines) T53-L-703 turboshaft engine.

The helicopter was listed on the Australian Civil Aircraft Register as VH-UHX in September 2014. In October 2014, the Civil Aviation Safety Authority issued a Special Certificate of Airworthiness permitting the helicopter to be operated in the ‘restricted’ category for agricultural, forest, and wildlife conservation, firefighting, and slinging of external loads. An additional Special Certificate of Airworthiness was issued in May 2015 in the ‘limited’ category for the purpose of conducting adventure flights.

Maintenance records identified that the helicopter had accrued 6,785.6 hours total time in service while operating in the US. They further indicated that by 30 January 2022, the helicopter had accrued a total time in service of 7,746.0 hours.

Figure 3: VH-UHX at the Tasmania Fire Service staging area

picture3-ao-2022-006.png

Source: Jamie Davis

Recent maintenance

In December 2021, while completing fire-fighting operations at Sisters Beach, Tasmania, a defect associated with the 90° tail rotor gearbox required replacement of the gearbox and several components from the tail rotor drive system. Commencing 26 January and concluding 30 January 2022, a scheduled 150-hour airframe and engine inspection was conducted. An additional inspection of the engine’s axial compressor and its stator was performed that involved removal of the top half of the compressor case. On 13 February 2022, the day prior to the accident, a scheduled 25-hour main rotor blade inspection and airframe lubrication was completed at the pilot’s residence with no reported defects.

Further investigation

The investigation is continuing and will include consideration of the:

  • helicopter flight profile during the occurrence flight
  • engine, transmission, tail rotor gearbox and component examinations
  • witness reports, imagery and video footage
  • helicopter maintenance and its operational history
  • helicopter performance and emergency procedures
  • pilot’s qualifications, medical history, and experience
  • related occurrences in Australia and overseas.

An accredited representative from the US National Transportation Safety Board (NTSB) has been appointed to assist with 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.

A final report will be released at the conclusion of the investigation.

Acknowledgements

The ATSB acknowledges the support of the Tasmania Police Force, Tasmania Fire Service, and all parties that assisted the investigation team through the evidence collection phase 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.

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. Eastern Daylight saving Time (EDT): Coordinated Universal Time (UTC) + 11 hours.

Safety Advisory Notice

Read the Safety Advisory Notice: UH-1H helicopter main drive shaft failure

Final report

Executive summary

What happened

On 14 February 2022, the pilot of a Garlick UH-1H helicopter was supporting the Tasmania Fire Service (TFS) by providing aerial firebombing support to the Lebrina bushfire, in northern Tasmania. The pilot was requested by TFS to provide firebombing assistance to combat a spot fire that had flared up on the western flank of the fireground and at 1509 local time the pilot departed the TFS staging area. After transiting to a nearby dam and loading water into the underslung bucket, the pilot tracked toward the spot fire.

Witnesses observed the unexpected early release of water from the underslung bucket prior to reaching the target, before the helicopter tracked away from the location of the spot fire toward an open paddock. As the helicopter approached the paddock, the helicopter was observed to rotate rapidly before pitching steeply nose-down and descending. The helicopter collided heavily with terrain in a tail low, upright orientation before coming to rest on its left side. A post‑impact fire started in the engine bay, destroying the helicopter. The pilot received fatal injuries.

What the ATSB found

During the conduct of a firebombing operation, the helicopter’s engine-to-transmission main KAflex drive shaft partially failed and entered fail-safe mode. That resulted in the pilot jettisoning the water load from the underslung bucket and diverting toward clear ground. The failure was likely due to the fracture of a flex frame attaching bolt, or a flex frame element during the accident flight.

As the helicopter was slowing during a descent over clear ground, the KAflex subsequently completely failed, resulting in instantaneous loss of drive to the rotor system.   

Following loss of drive to the main rotor system, the pilot was unable to complete a survivable   autorotative descent and landing, probably due to a critical reduction in main rotor speed. 

What has been done as a result

Following the accident, the Civil Aviation Safety Authority released 2 updates to a previously released Airworthiness Bulletin on the subject of pre-flight inspection requirements for the KAflex drive shaft. The Airworthiness Bulletin recommended that maintainers and operators check the condition of all drive shaft hardware in addition to the pre-existing inspection requirements listed in the flight manual. The bulletin also provided further advice to operators and maintainers on potential operational aspects once a KAflex has entered fail-safe mode.

The ATSB released a safety advisory notice (SAN) in June 2022 to all operators of UH-1H helicopters advising of the circumstances surrounding the accident and that it involved failure of the KAflex driveshaft. The SAN advised operators of UH-1H helicopters to note the details of this accident and to look for the presence of red metallic residue or debris at the bolted connections, frame cracking, missing or damaged attaching hardware during all inspections of the KAflex driveshaft. Any identified defects should be notified to the Civil Aviation Safety Authority.

Additionally, the SAN also advised that operators should be aware of the KAflex manufacturer’s (Kamatics) concern regarding shafts for the UH-1H helicopter that may be fitted with legacy attachment hardware. Kamatics should be contacted if a shaft, serial number 0635 and below, is identified.

Richmond Valley Aviation, the maintainer and operator of the accident helicopter, advised that following the accident they removed all KAflex main transmission drive shafts from the helicopters that they maintained and replaced them with an alternate type of shaft that can be greased.

Kamatics advised that for KAflex shafts returned to their factory a teardown inspection will be completed to identify any evidence of fretting, cracked washers or any other undesirable defect in hardware items normally replaced during overhaul.

The Tasmania Fire Service advised that, since the accident they have completed the following agency safety actions in relation to their aviation operations:

  • Transitioned to the Tasmanian Government Radio Network to enable direct communications with other emergency service organisations, fire land managers and aircraft operators working at multi-agency incidents.
  • Conducted an inter-agency exercise to test the response to a rescue incident in remote and isolated areas. The exercise tested the TFS timelines, incident management command and control, communication links, processes and roles of each agency. A key outcome was that the notification procedures have been improved between TFS, Tasmania Police and the Ambulance Tasmania Air Rescue Aviation Unit.

Safety message

Pilots of UH-1H helicopters should note that if vibrations or noise from the transmission area rapidly increases or becomes severe during flight, it may signify that the KAflex drive shaft has entered fail‑safe mode and could imminently fail.

Significantly, the commencement of a distinct ‘howling’ or ‘shrieking’ noise is a key indication of a developing KAflex failure.

The ATSB strongly recommends that pilots land as soon as possible on detection of such symptoms. Of the UH-1H accidents that have occurred, complete failure of the drive shaft has typically occurred in just a few minutes leading to an emergency landing and significant damage to the helicopter. In addition, pilots should be aware that complete failure of the KAflex can unexpectedly lead to right yaw, which is contrary to indications of a loss of drive to the main rotor system detailed in the flight manual.

The ATSB also reminds UH-1H helicopter pilots, operators, and maintainers that fatigue cracking can occur on critical flight components. Particular vigilance should be applied during the daily or pre-flight inspections of the main transmission driveshaft because it represents an important opportunity to detect for defects such as cracks, and to identify evidence of loose or missing attachment hardware.

The occurrence

On 10 February 2022, a bushfire developed after a registered burn escaped containment lines near Pipers Brooke Road, north of Launceston, Tasmania (Figure 1). A multi-agency[1] response commenced work to contain the ‘Lebrina’ fire using fire tankers, bulldozers and helicopters performing aerial firebombing. The pilot of a Garlick Helicopters[2] UH-1H, registered VH-UHX, was tasked by the Tasmania Fire Service (TFS) to combat the fire, which by 13 February had burnt 1,662 hectares of bushland and forestry plantations.

Over the period 10–13 February 2022, the pilot flew multiple firebombing sorties over the fireground from a temporary staging area established by TFS on a private field adjacent to Pipers Brook Road. At the conclusion of each day’s activity the helicopter was flown to the south of Launceston and hangared at the pilot’s residence.

Figure 1: Accident location and the Lebrina fireground, Tasmania

Figure 1: Accident location and the Lebrina fireground, Tasmania

Source: Google Earth, annotated by the ATSB

On 14 February 2022, at about 0833 local time, the pilot departed their residence in VH-UHX and tracked toward the staging area. They then completed firebombing operations in the north‑eastern sector of the fireground. The tasking involved flying circuits between the fire boundary and a nearby dam, where an underslung water bucket was replenished with water. After completing several sorties, the pilot returned to the staging area and landed, shutting down the helicopter at 0929. The pilot remained at the staging area with other helicopter pilots, ground support and firefighting personnel.

At about 1455, 2 fire commanders, a TFS observer, and a pilot departed the staging area in an AS350 helicopter, registered VH-RLR (designated Firebird 460), to provide air attack supervision and to conduct an aerial survey of the fireground. Shortly after 1500, the personnel onboard Firebird 460 observed a rising plume of smoke in a region of unburnt vegetation on the western flank of the fireground. In response, they requested a firebombing helicopter attend the spot fire. 

The pilot received the TFS request and, at about 1509, departed the staging area in VH-UHX.  Witnesses at the staging area observed VH-UHX proceed to a small dam and hover, while the pilot filled the underslung bucket with water. The helicopter then departed and climbed toward the designated target (Figure 2).

The pilot and TFS personnel within Firebird 460 observed VH-UHX approach the spot fire and the release of the water load from the underslung bucket. The pilot of Firebird 460 recounted that the drop was unusual because they estimated the water had missed the target by ‘hundreds of meters.’ VH-UHX then commenced a gradual climbing turn to the left and tracked to the north‑west. To avoid any potential conflict with the now‑approaching helicopter, the pilot of Firebird 460 initiated a climbing 360° right turn, with those onboard losing sight of VH-UHX during the manoeuvre.

After completing the turn and regaining sight of VH-UHX, the Firebird 460 pilot recalled that the helicopter was now beyond the bushland and above an open paddock. They then witnessed the underslung longline and bucket fall to the ground and the helicopter descend rapidly. The pilot commented that VH-UHX appeared to be ‘diving toward the paddock’, in what they assessed was preparation for an emergency landing. Noting that the airspeed and descent rate for VH-UHX had increased, the pilot in Firebird 460 did not identify any slowing or flaring as the helicopter approached the ground and commented that their attention was also diverted to finding a suitable nearby landing site to provide assistance.

A passenger onboard Firebird 460 recalled irregular side-to-side movement of the tail section and a brief puff of white smoke emanate from the rear area of VH-UHX as it descended, prior to it colliding with terrain. They further commented that there did not appear to be any dust or debris from rotor wash that would normally be expected as VH-UHX approached the ground. Further, the Firebird 460 pilot did not hear any radio calls from the pilot of VH-UHX following the approach to the spot fire.

About 30 seconds after the collision, the pilot of Firebird 460 landed adjacent to the wreckage and alighted along with the TFS personnel. They reported that VH-UHX was on its left side and substantially damaged. Small fires had ignited in the surrounding grass and within the engine bay. The responders from Firebird 460 were unable to suppress the fire using handheld fire extinguishers. A nearby witness attended the site and connected a strap between their vehicle and the right skid of VH-UHX, however the helicopter was unable to be moved. The fire spread quickly and within a few minutes the wreckage was engulfed.

Two other pilots who were positioned with their helicopters at the TFS staging area responded to the emergency and proceeded to the accident site. They deposited multiple loads of water, however the fire was unable to be extinguished. The pilot of VH-UHX sustained fatal injuries and the helicopter was destroyed.

Figure 2: Key areas of the Lebrina fireground relative to the accident site

Figure 2: Key areas of the Lebrina fireground relative to the accident site

Source: Google Earth, annotated by the ATSB

Context

Additional witness information

A pilot-witness positioned at the Tasmania Fire Service (TFS) staging area had been monitoring VH-UHX, described seeing the pilot depart in VH-UHX, fill the underslung bucket at a nearby dam and then track toward the spot fire. They further identified that the water drop was conducted too high and too early, significantly missing the target. The helicopter was then observed to slow and commence a descending profile before completely rotating twice to the right about its vertical axis (yawing). The helicopter then pitched up and then down, before rapidly descending with a nose‑low pitch attitude.

Personnel onboard the air attack supervising helicopter (Firebird 460) captured several images and a short video of VH-UHX approaching the designated spot fire. One of the images showed the early release of water from the underslung bucket (Figure 3). The video file recorded by another passenger commenced in the moments after the water had been released and showed VH-UHX in a left turn (Figure 4). The video did not capture the yawing movement reported by the pilot-witness at the TFS staging area.

Another witness who was in their house near to the accident site recalled seeing VH-UHX in a descending approach. In their statement the witness reported hearing a screeching/roaring noise, with the helicopter observed to be descending in a left banking turn before moving out of sight.

Figure 3: VH-UHX releasing the underslung bucket contents at a considerable height and distance away from the spot fire (smoke plume)

Figure 3: VH-UHX releasing the underslung bucket contents at a considerable height and distance away from the spot fire (smoke plume)

The image was captured by a witness onboard Firebird 460. Metadata identified that the image had been captured at timestamp 1514:42

Source: Rod Sweetnam

Figure 4: VH-UHX in a left turn moments after the water release

Figure 4: VH-UHX in a left turn moments after the water release

This image is cropped from a video file captured by TFS personnel within Firebird 460 and shows the empty underslung bucket trailing VH-UHX

Source: Tasmania Fire Service, modified by ATSB

Aircraft information

General

The UH-1H ‘Huey’ helicopter was developed by Bell Helicopters in the 1960s as a military utility helicopter for the United States (US) Army. Records showed that the accident helicopter was manufactured in November 1965 (airframe serial number 64-13865). After ceasing US Army operations, surplus UH-1H helicopters were made available for civilian operations. Several organisations were authorised by the US Federal Aviation Administration (FAA) to convert ex‑military helicopters for civilian use. This included Garlick Helicopters Inc, who was the type certificate holder for this helicopter.

Operational arrangements

In September 2014 the helicopter was listed on the Australian civil aircraft register as VH‑UHX. In October 2014, the Civil Aviation Safety Authority (CASA) issued a special certificate of airworthiness permitting the helicopter to be operated in the restricted category to complete agricultural, forest, wildlife conservation, firefighting, and slinging of external loads. An additional special certificate of airworthiness was issued by CASA in May 2015 for the purpose of conducting adventure flights.[3]

The helicopter was purchased by its last owner in July 2020 to complete firefighting and slinging contracts. A pre-purchase inspection report completed on VH-UHX prior to the sale identified no airworthiness issues. The owner entered a contractual arrangement with Richmond Valley Aviation to operate and maintain the helicopter. Richmond Valley Aviation was in turn contracted to the National Aviation Firefighting Centre to provide on-call aerial firefighting capability using VH‑UHX.

The pilot, who was based in Tasmania, was contracted by Richmond Valley Aviation. The helicopter was re‑positioned to Tasmania in early 2021 where it was operated solely by the accident pilot.

Fuel

A 4,400 litre fuel storage tank was located at the pilot’s property where VH-UHX was hangared. This tank was used to replenish two 1,325 litre fuel storage tanks and four 205 litre drums on a refuelling truck. It was reported that VH-UHX had used drum fuel from the refuelling truck for the entirety of the Lebrina fire campaign tasking.

On the morning of 14 February, VH-UHX was fuelled from the refuelling truck that had been positioned at the TFS staging area. Fuel records indicated that 124 litres were added to the main tank of the helicopter, bringing the total fuel onboard to approximately 700 litres at the time of the final departure.

A sample of this fuel was obtained from the truck. Testing showed the sample was clear and slightly straw-coloured with no visible contaminants or indication of water. A visual inspection of all the fuel storage tanks similarly revealed no visible contaminants.

Water bucket

For firebombing applications, the helicopter used either 1,200 or 1,400 litre flexible buckets. The bucket was attached to the helicopter cargo hook via a 150 ft steel cable (longline). A push button switch mounted on the collective control was electrically connected to an air‑operated valve within the bucket that allowed the pilot to regulate the water release, including complete dumping of the water.

Cargo hook

VH-UHX was fitted with an equipment cargo hook that allowed external cargo to be released via an electrical switch on the pilot’s cyclic control grip. A switch on the forward section of the overhead console enabled the system to be armed and/or isolated. In addition, a foot-activated manual release lever was located between the tail rotor pedals. This release lever was used to jettison cargo in the event of an emergency or failure of the electrical release system. The ATSB was informed that the pilot sometimes isolated electrical control for the cargo hook. With the cyclic switch inoperative, the foot-activated manual lever was the only available option to release the external cargo.

Wreckage and impact information

Accident site

The helicopter wreckage was located in a grassy paddock near Pipers Brook Road, about 2.6 km north of the TFS staging area. The helicopter had been destroyed from ground impact forces and the subsequent fuel-fed fire (Figure 5). A survey of the accident site showed the wreckage to be orientated in a westerly direction (Figure 6).

Ground marks at the site showed that the tubular steel tail skid on the underside of the tail boom first contacted the ground, followed by the landing skids, main rotor blades and the cabin. After the initial ground strike, almost the entire tail section, including the tail rotor gearbox, separated from the fuselage, coming to rest a short distance beyond the main wreckage. Other items that separated from the helicopter included both main rotor blades, the battery and the landing skids. Three distinct ground scars identified where the main rotor blades struck the ground.

Figure 5: View of the fuselage and separated tail section at the accident site

Figure 5: View of the fuselage and separated tail section at the accident site

The Lebrina fireground was located beyond the foreground tree line at the perimeter of the paddock. The upper wire cutter guide, longline and water bucket were located further back toward the tree line.

Source: ATSB

Figure 6: Overhead view of the accident site

Figure 6: Overhead view of the accident site

Source: ATSB

The furthest items from the accident site were the tip from the upper wire cutter guide (located 220 m from the wreckage) and the underslung water bucket that remained attached to its longline (located 300 m from the wreckage) (Figure 7). Deformation to the fractured wire cutter guide was consistent with it being struck and projected by a main rotor blade.

Figure 7: Accident site showing the flight track of VH-UHX (red/green shaded area) and items that had liberated from the helicopter

Figure 7: Accident site showing the flight track of VH-UHX (red/green shaded area) and items that had liberated from the helicopter

Source: Google Earth, modified by ATSB

Engine examination

The helicopter was fitted with a Lycoming T53-L-703 turboshaft engine. The T53-L-703 consists of a single-spool five-stage axial compressor with the sixth-stage being a centrifugal flow compressor. The high-pressure turbine (gas producer) drives the compressor and accessory gearbox, while the low-pressure turbine (power turbine) drives the output gearbox to the main transmission drive shaft.

Examination of the wreckage identified that the main support mounts and forward trunnion mounts to the engine were still connected, however the supporting tubular frame had torn from the engine bay floor area during the impact. The engine was significantly damaged by the post-impact fire, resulting in destruction to the electrical looms, braided oil lines and the accessory gearbox. The engine fuel filter was removed from the engine and was found to be clear with no visual contaminants.

The power turbine was unable to be rotated. However, metallic material had solidified at numerous locations on the second-stage power turbine aerofoil surfaces indicating that metallic debris had passed through the combustion chamber while the engine was operating. Although absolute engine power levels were not able to be assessed the extent of internal compressor damage in combination with the ingested debris provided evidence that the engine was rotating at high speed during the impact sequence (Figure 8).

Internal inspection[4] of the compressor section identified that the compressor blades had been dislodged and bent against their normal direction of rotation. Debris was found throughout the compressor, including a piece of the main transmission drive shaft (KAflex coupling), multiple blade segments, inlet guide vanes and pieces of airframe structure (Figure 9).

Figure 8: Solidified metallic deposits were identified on the surfaces of the second stage power turbine

Figure 8: Solidified metallic deposits were identified on the surfaces of the second stage power turbine

Source: ATSB

Figure 9: Severe disruption occurred to all internal stages of the compressor (left) and the debris that was recovered from within the compressor (right)

Figure 9: Severe disruption occurred to all internal stages of the compressor (left) and the debris that was recovered from within the compressor (right)

The rectangular item in the right image is a piece from the main transmission drive shaft (KAflex)
Source: ATSB

Flight controls

The UH-1H flight control system is hydraulically assisted and actuated by conventional helicopter controls for both the pilot and co-pilot. Due to the extensive fuel-fed post-impact fire, most of the aluminium flight control components were destroyed leaving behind the steel componentry and connecting hardware. Of the recovered connecting hardware there was no evidence of missing fasteners or disconnections. 

Tail rotor control system

VH-UHX was fitted with composite tail rotor blades connected to a common yoke by a grip and pitch change bearings. The hub and blade assembly are mounted on the tail rotor shaft with a delta-hinge trunnion and a static stop to minimize rotor flapping. Heading control is accomplished by movement of the anti-torque pedals which are connected to the pitch control system through the tail rotor (90°) gearbox. A multi-segmented drive shaft provides power from the main transmission to a 42° gearbox then to the 90° tail rotor gearbox.

The tail rotor anti-torque pedals were partially identified; however, the majority of the system had been consumed by fire. Continuity to the extent possible was established through to the tail boom section. The tail rotor drive shaft displayed rotational scoring damage at various locations along its length. The composite tail rotor blades also displayed evidence of impact damage from a ground strike. The tail rotor gearbox had fractured through its mount at the end of the tail boom. There was no evidence of pre-existing damage to the separated tail rotor gearbox with no evidence of binding or internal seizure. Overstress features present on the gearbox mount fracture surfaces were consistent with ground impact.

Hydraulic system

The hydraulic system is used to minimise the force required by the pilot to move the cyclic, collective and pedal controls. Due to the extensive damage sustained to the helicopter from the post-impact fire, a detailed assessment of the hydraulic system components was not possible.

Fuel

Only partial remnants of a flexible fuel cell were identified within the wreckage. No fuel was recoverable from the aircraft for testing.

Transmission

The UH-1H main rotor transmission is mounted forward of the engine and connected to the power turbine shaft at the front end of the engine by the main transmission drive shaft (KAflex). A freewheeling unit (sprag clutch) within the transmission reduces drag on the main rotors following an engine power loss, enabling an autorotative landing.

The wreckage examination identified that the transmission had partially separated from its airframe mounts and was located on its left side. The mast had fractured during the impact sequence, liberating the rotor head and both main rotors. The freewheeling unit within the transmission housing was seized due to the extensive heat damage from the post-impact fire and unable to be moved. The post-impact fire consumed a large section of the transmission housing exposing the main bull gear. There was no observable pre-impact damage to the gear teeth.

Main transmission drive shaft

The main transmission drive shaft (KAflex) was identified at the accident site to have fractured into multiple pieces (Figure 10). One of those pieces was found within the compressor section of the engine. Due to the extent of impact and fire damage, several attachment bolts and portions of flexible frame elements from the coupling were unrecoverable. The KAflex components were retained for subsequent examination at the ATSB’s technical facilities in Canberra.

Figure 10: Burnt wreckage noting the forward section of the fragmented KAflex main transmission drive shaft

Figure 10: Burnt wreckage noting the forward section of the fragmented KAflex main transmission drive shaft

Source: ATSB

Recorded information

Flight data recorders

The helicopter was not fitted with a flight data recorder or cockpit voice recorder, nor was it required to be.[5]

GPS and other data

The helicopter was equipped with a Tracplus tracking system that recorded GPS positional information at 2-minute intervals. Due to the relatively low sampling rate, the Tracplus data provided general aircraft track information rather than high fidelity information about the accident flight. The Tracplus data identified that for the accident flight, the system had commenced recording at 1508:49, which corresponded with the pilot preparing to depart from the TFS staging area.

A Garmin 296 GPS system was recovered from the accident site. The GPS was retained by the ATSB for data recovery at the ATSB’s technical facilities in Canberra. The device recorded time, position, ground speed and barometric altitude at varying time intervals, ranging between 1‑15 seconds.

Those onboard the Firebird 460, also recorded imagery and video files throughout the flight. Data from those files provided timestamp and georeferenced information. The ATSB completed an analysis of the available recorded data during the accident flight (Figures 11 - 13).

Take-off, water pick-up and climb out

At about 1509, VH-UHX departed the staging area and proceeded to a dam approximately 1 km to the west. At 1512:50, the helicopter was slowed to a hover, indicating the underslung bucket was being filled with water. After about 30 seconds overhead the dam, the helicopter departed and climbed to an altitude of 1,100 ft above mean sea level (AMSL) while transiting to the spot fire.

Water drop

At 1514:11, a left descending turn was conducted toward the spot fire at an average descent rate of about 250 ft per minute. During this time, the helicopter was slowed from a ground speed of about 60 kt to 30 kt. An image taken at 1514:42 by a TFS member onboard Firebird 460 showed water being released from the underslung bucket. GPS data indicated that VH-UHX climbed about 30 feet around that time, consistent with the reducing weight of the underslung load.

Cruise descent, deceleration, and final climb

From 1514:52 to 1515:22 VH-UHX descended at an average rate of 400 feet per minute to an altitude of about 780 ft AMSL, while slowing from about 68 to 55 knots ground speed. The ground speed and the rate of descent of about 400 feet per minute indicated that this was a powered descent, based on the autorotational glide characteristics from the UH-1H helicopter flight manual. Based on the data, about 20 seconds into the descent, VH-UHX was established over open terrain.

Following this, UHX commenced a shallow climb up to an altitude of about 840 feet, with the track changing by about 20° to the right, and the ground speed reducing to about 36 knots. The data did not contain sufficient information to determine the rate of yaw or the pitching movements observed by the pilot-witness at the TFS staging area.

It was not possible to determine the precise location of the helicopter when the bucket was released. However, based on the recorded flight path and the location of the bucket, approximately 300 m to the east of the main wreckage, the ATSB estimated the earliest possible release point of the bucket was at 1515:31, when the helicopter was in a slight climb and the track had altered slightly to the right.

Recorded rapid descent

The final 2 data points (Figure 13) indicated that VH-UHX descended at a mean rate between 1,500 and 1,700 feet per minute, consistent with autorotation. Calculations indicated that the descent commenced at approximately 430 ft above the terrain. During this time, the horizontal ground speed component of the helicopter initially reduced to about 30 kt before increasing to about 50 kt. The final data point from the onboard GPS was recorded at 1515:45. The final data point from the Tracplus was transmitted at 1515:58 and was likely a post-collision system shutdown.

Figure 11: Garmin 296 track data showing the flight path of UHX during the accident flight

Figure 11: Garmin 296 track data showing the flight path of UHX during the accident flight

Source: Google Earth, annotated by ATSB

Figure 12:  Presentation of recorded data plotting altitude and groundspeed against local time

Figure 12:  Presentation of recorded data plotting altitude and groundspeed against local time

Key moments in the accident flight sequence of events are annotated

Source: ATSB

Figure 13:  Presentation of the final GPS data points from the accident flight plotting altitude and ground speed against local time

Figure 13:  Presentation of the final GPS data points from the accident flight plotting altitude and ground speed against local time

Source: ATSB

Aircraft performance

Weight and balance

The ATSB evaluated whether VH-UHX was operated within the allowable weight and balance limits during the accident flight. Weights considered for this assessment included the onboard equipment, approximately 700 litres of fuel, pilot weight, and the weight of water contained within the bucket. A load cell and onboard digital gauge allowed the amount of water in the bucket to be monitored and provided a means for the pilot to assure that the helicopter remained within weight limits.

Although it was not possible to determine the precise amount of water transferred into the bucket from the dam, the ATSB concluded that VH-UHX was likely operating below the maximum take-off weight and within the centre of gravity limits throughout the accident flight.

Emergency procedures

Total power loss vs drive shaft failure

Emergency procedures were described in Chapter 9 of the UH-1H Operator’s Manual. For an engine malfunction or complete power loss, the manual stated that:

a. The indications of an engine malfunction, either a partial or a complete power loss are left yaw, drop in engine rpm, drop in rotor rpm, low rpm audio alarm, illumination of the rpm warning light, change in engine noise.

Additionally, the manual detailed the following indications associated with a drive shaft failure:

A failure of the main driveshaft will be indicated by a left yaw (this is caused by the drop in torque applied to the main rotor), increase in engine rpm, decrease in rotor rpm, low rpm audio alarm (unmodified system), and illumination of the rpm warning light. This condition will result in complete loss of power to the rotor and a possible engine overspeed. If a failure occurs:
1. Autorotate.
2. EMER SHUTDOWN.

Comparing the 2 malfunctions, in the event of a drive shaft failure the helicopter will exhibit some of the symptoms listed above for an engine power loss. Specifically, reduction in rotor RPM, activation of the low RPM audio alarm and illumination of the warning light would be expected. However, there will be no drop in engine RPM. Rather the engine RPM will likely initially increase (with associated noise), due to the sudden unloading from the rotor system.

Contrary to the advice in the Operator’s Manual, in both this occurrence and a past occurrence involving failure of the drive shaft (see the section titled Other occurrences), the helicopter unexpectedly experienced right yaw.

The helicopter manufacturer advised the ATSB that if the transmission RPM decreased, both the main rotor and tail rotor RPM would also decrease. A decrease in tail rotor RPM would result in less tail rotor thrust and therefore a nose-right yaw could occur. They further advised that a reduction in main rotor RPM would result in a corresponding reduction in hydraulic system pressure, which may then result in increasing stiffness through the flight controls (including the hydraulically boosted pedals). An overcontrol application of right pedal could occur due to these changes in control feel.

Forced landing

A successful forced landing in a single-engine helicopter can only be achieved if the helicopter has sufficient energy in the rotor to achieve the required landing deceleration and touch down configuration. For single-engine helicopters, the height-velocity (H/V) diagram is established by the manufacturer at the time of certification. The diagram:

defines an envelope of airspeed and height above the ground from which a safe power-off or one engine inoperative (OEI) landing cannot be made (FAA,2014).

The UH-1H flight manual included the H/V diagram for UH-1H helicopters, including VH-UHX (Figure 14). When operating at low speed in the shaded (or ‘avoid’) area on the left side of the diagram, in the event of a power loss, a pilot may have insufficient height to accelerate to the speed required to autorotate successfully. Above a certain height above the ground, at least 500 ft for the UH-1H depending on the density altitude, it is possible for a pilot to achieve autorotation speed even from a high hover. In the shaded area on the lower right side of the diagram, the combination of faster airspeed and proximity to the ground provides limited reaction time for the pilot in the event of an engine power loss. The FAA Helicopter Flying Handbook (FAA, 2019), stated:

…the shaded areas should be avoided, as the pilot may be unable to complete an autorotation landing without damage.

The unshaded region of the diagram shows the combinations of airspeed and height above the ground that allows a pilot to successfully complete a landing in a full autorotation without requiring exceptional skill. At low heights (below about 10 ft) with low airspeed, such as a hover taxi, the helicopter is in a safe part of the H/V diagram. There, a pilot can use the kinetic energy from the rotor disc to cushion the landing with collective, converting rotational inertia to lift. An increase in height without a corresponding increase in airspeed puts the helicopter above a survivable un‑cushioned impact height, until a height is reached from which rotor inertia and gravitational potential energy can be converted to sufficient lift to reduce the vertical velocity at impact to a survivable value (FAA, 2019).

The US Federal Aviation Administration (2019) also stated that:

As the airspeed increases without an increase in height, there comes a point at which the pilot’s reaction time would be insufficient to react with a flare in time to prevent a high speed, and thus probably fatal, ground impact.

The ATSB evaluated the likelihood that VH-UHX should have been able to complete a safe landing after an engine failure. Figure 14 and Figure 15 show the recorded heights and speeds of the last 6 data points from the flight path data. This shows that for this phase of the flight, the helicopter was outside the avoid area of the height-velocity curve, indicating that an autorotative glide should have been possible with the nominal helicopter rotor rpm.

Figure 14: Data points from the onboard GPS noting time, airspeed (calculated) and height are overlaid on the UH-1H height-velocity helicopter performance diagram

Figure 14: Data points from the onboard GPS noting time, airspeed (calculated) and height are overlaid on the UH-1H height-velocity helicopter performance diagram

Source: Garlick Helicopters, annotated by the ATSB

Figure 15: The final data points from Figure 14 are overlaid against the final track of the helicopter

Figure 15: The final data points from Figure 14 are overlaid against the final track of the helicopter

The approximate position of the yawing (rotations), the longline and fire bucket, and the accident site are also shown.

Source: Google Earth, annotated by the ATSB

Autorotative glide

The ATSB evaluated the descent of VH-UHX between the final recorded data points and the accident site for the purpose of establishing if it had entered a stable autorotative glide during the last part of the flight.

The calculated glide ratio from the last 2 flight data points was approximately 1 to 3.6, with a rate of descent of between 1,500 and 1,700 feet per minute and a ground speed of about 50 knots. Published UH-1H autorotational glide characteristics indicated that for an airspeed comparable to 50 knots and main rotor rpm of 314 rpm, a glide ratio of 1 to 3.8 is predicted at a descent rate of 1,600 feet per minute. The actual main rotor rpm was not recorded in the flight data and could not be determined. Further, there were insufficient flight data points to establish if the flight had entered a steady descent at this stage. Therefore, although the actual and published glide characteristics appeared to be comparable for this phase of flight, it was not possible to determine if VH-UHX was in a stable autorotation at the nominal rpm at this point in the flight.

A 1 to 1 glide ratio was estimated between the final recorded flight data point and the initial ground impact location. This ratio was at least 3 times steeper than that indicated by the flight data and published glide characteristics predicted for a stable autorotation noted above. This is consistent with the actual aircraft track, ground speed and vertical trajectory being considerably different to the last 2 flight data points. The most likely explanation for this is that the vertical speed was increasing between the final data point and the collision with terrain.

Personnel information

General

The pilot was an Australian citizen who had flown in several countries and had experience on numerous helicopter types. The pilot held a current commercial pilot licence (helicopter) that was issued on 22 December 2000, and a current Class 1 aviation medical certificate. In addition, the pilot held a low-level operational rating issued on 5 January 2001, with endorsements for helicopter sling-load operations issued on 21 June 2004. All the flight ratings held by the pilot were current and valid at the time of the accident and the pilot had worked with the TFS for several years.

Flying experience

Their logbook showed an accumulation of more than 9,900 hours total aeronautical experience, mostly in helicopters. In the previous 30 and 90 days, the pilot had flown 75 and 146 hours respectively and almost all those hours were accumulated in the accident aircraft.

The pilot attained a type rating for the UH-1H, in addition to the Bell 204 and Bell 205, on 9 July 2014. At the time of the accident the pilot’s total flying experience on the Bell 204, Bell 205 and the UH-1H was approximately 814 hours.

The pilot had about 2,090 hours total experience in aerial firefighting. In the last 90 days, most of the flying performed by the pilot (132 of the 146 hours) related to firefighting activities in the accident aircraft, with 108 hours of firefighting sling load operations recorded.

Proficiency

The pilot’s most recent aircraft flight review was completed in a Bell 505 helicopter on 5 August 2021. The ATSB consulted the flight examiner from an earlier review[6] where the pilot completed their proficiency check in VH-UHX. For the longline operational component of the check, during which the pilot’s control of the aircraft was assessed, the examiner reported requiring the pilot to select a water source, collect the water in the fire bucket and choose a target.

When asked about the pilot’s management of abnormal and emergency situations, the examiner advised that autorotations were conducted at elevations of 500 ft and 1,000 ft. Simulated hydraulic or engine failures were conducted, as well as a jammed flight control (usually the left pedal).

In the event of an emergency, the examiner advised the ATSB that pilots were trained to ‘clean‑up’ the aircraft by jettisoning the longline and bucket. Though it was normal industry practise to release the bucket and longline during an in-flight emergency, the examiner advised that it was up to the pilot’s discretion when to complete that action.

At the conclusion of the proficiency check, the examiner recorded that the accident pilot was of a ‘high standard’ and had no concerns with the accident pilot managing an in-flight emergency.

Fatigue assessment

The ATSB assessed whether the pilot may have been fatigued at the time of the accident. The pilot’s start times, rest time available, accommodation, environmental factors and workload associated with the task were all reviewed.

From the evidence available, while there were some long days of firebombing leading up to the accident, based on the pilot’s sleep obtained and the hours worked on the day and during the 72 hours prior (Table 1), it is unlikely the pilot was experiencing a level of fatigue that would have affected their ability to safely operate the helicopter.

Table 1: 72-hour pilot history

Duty11 February 202212 February 202213 February 202214 February 2022
Flight time10106.51.0
Duty time11.510116.5

Survival aspects

Medical and pathological information

Post-mortem and toxicology reports were reviewed by the ATSB, with no natural disease or apparent toxicology identified. The post-mortem report concluded that the cause of death was a combination of head and thermal injuries.

Pilot seating

A flight manual supplement allowing the pilot in command to conduct operations from the left seat during external load operations was located in the recovered flight manual. The pilot was known to operate the helicopter from the left seat during firebombing operations. The pilot was located by first responders within their seat harness on the left side of the helicopter and had been wearing a flight helmet and flight suit. The left seat was fitted with a four-point harness, however, first responders were unable to advise whether the shoulder harness had been in use. Due to the significant vertical and horizontal loads, the resulting compression of the fuselage, and the post‑impact fire, the accident was not survivable.

Meteorological information

Meteorological reports and a private weather station within 5 km of the accident site indicated clear sky and light to moderate wind conditions. The air temperature at the accident site was estimated to range between 25°C and 29°C.

A pilot who was situated at the TFS staging area at the time of the accident described the weather as light winds from the east-north-east or the north-east and to be suitable for the helicopter firebombing operations.

Helicopter maintenance information

General

The logbook statement for VH-UHX specified that it was to be maintained in accordance with the Garlick Helicopters Inc. Instructions for Continued Airworthiness (ICA) report GH-H13WE-CA1H. The Garlick ICA report stated that the UH-1H helicopter-type was to be maintained in accordance with the US Army technical publications.

The US Army UH-1H maintenance schedule included a phased program that had a 900-flight hour cycle with intermediate 150-hour phases. There were also 25-hour and daily inspections.

The special certificate of airworthiness for VH-UHX stated:

The helicopter must at all times be operated in accordance with the UH-1H TM-55-1520-2010-10 and any approved Flight Manual Supplements associated with FAA or CASA approved modifications to the aircraft.
Recent scheduled maintenance

The helicopter’s maintenance records identified that the helicopter had accrued 6,786 hours total time in service while operated in the US. The records further indicated that by 30 January 2022, the helicopter had accrued a total time in service of 7,746.0 hours.

A scheduled 150-hour airframe and engine inspection was conducted by Richmond Valley Aviation between 26–30 January 2022. An additional inspection of the engine’s axial compressor and stators was performed requiring the removal of the top half of the compressor case. The compressor was washed and a linear actuator for the compressor guide vanes was replaced. In addition, the helicopter’s KAflex main drive shaft was removed and inspected. No defects were detected.

On 13 February 2022, the day prior to the accident, a scheduled 25-hour inspection that included a main rotor blade examination and airframe lubrication was completed by a licensed maintenance engineer at the pilot’s residence. The engineer recalled that no defects were identified during the inspection.

A partly burnt maintenance release was recovered from the wreckage. The document was issued on 30 January 2022 with an expiry of 30 January 2023, or 150 hours of operation from the time of issue, whichever occurred first. A signed entry on the document indicated that the daily inspection had been completed on 14 February 2022. There were no endorsements (defects) annotated on the maintenance release.

Flight time from 30 January 2022 was unable to be established due to fire damage. However, examination of the pilot’s flight records established that the helicopter had operated for 38 hours since the 150-hour phased inspection.

Unscheduled maintenance

In December 2021, while the pilot was completing firefighting operations at Sisters Beach, Tasmania, a defect associated with the 90° tail rotor gearbox was detected by the pilot. An attaching stud had reportedly loosened and contacted the upper part of the tail rotor drive shaft clamp. The helicopter was grounded until the gearbox and several components from the tail rotor drive system were replaced.

Richmond Valley Aviation reported that the KAflex drive shaft was scheduled for replacement due to the release of Federal Aviation Administration airworthiness directive (FAA AD) 2021-26-16, which became effective on 25 February 2022. The operator’s maintenance personnel advised that they had discussed the replacement of the KAflex with another type of greaseable drive shaft with the pilot and scheduled the replacement for the end of February 2022.

KAflex – main transmission drive shaft

General description

The KAflex main drive shaft for the UH-1H was manufactured by Kamatics Corporation (Kamatics). It was initially manufactured for the US Army in 1975 and was utilised as a direct replacement for the original Bell Helicopters driveshaft in their UH-1H fleet. The KAflex drive shaft is a flexible mechanical assembly that transmits torque from the engine output shaft to the input quill of the main rotor transmission. The drive shaft uses plates (flex frames) to accommodate relative movement between the engine and transmission. In normal operation, each flex frame transmits load from one bolt pair to the next bolt pair (Figure 16).

The drive shaft is designed with a fail-safe feature. Should an in-service fracture occur within the flex frame pack, or in the attaching hardware, the interconnect and end fitting are forced together. The resultant friction maintains drive between the engine and transmission. The off-centre and out-of-balance operation of the interconnect shaft causes vibrations, which signals that a partial failure has occurred and fail-safe mode is in operation (Figure 17). A pilot may be alerted to a shaft operating in fail-safe mode by increased noise and vibration.

Kamatics advised the ATSB that during qualification testing to demonstrate the fail-safe feature, a drive shaft demonstrated 21.5 minutes of continued powered operation when a flex-frame had been intentionally failed. The testing involved a short-term high-power operation (such as a climb or to manoeuvre to avoid an obstacle) followed by reduced power operation (such as flight in search of a landing site).

The testing did not consider a bolt failure and Kamatics advised a rapid decline of the shaft would result if a bolt failure were to occur.

KAflex maintenance

Kamatics reported that the US Army developed their own technical manuals and instructions for continued airworthiness for maintaining the KAflex drive shaft. It was to be inspected daily (pre‑flight) and during the phased-maintenance intervals. No life-limits were applied by the US Army to the drive shaft.

The US Army phased maintenance required the KAflex to be visually inspected after every 150 hours of operation. Specifically, the instructions listed the following statement and required maintainers to:

CAUTION: Do not attempt to loosen or tighten any hardware. Any reason for necessary part removal is cause for shaft replacement.
a. Visually inspect shaft for cracks.
b. Visually inspect shaft for nicks, dents, scratches and corrosion.
(1) superficial scratches
(2) damage to protective coating.

The 150-hour inspection did not explicitly state to check for red metallic residue or debris at the bolted connections. Kamatics advised that a check for fretting material could be an early indicator of a washer failure or joint movement from loose bolts.

The daily inspections were to be completed by the pilot and were listed in the operating procedures and manoeuvres section of the UH-1H flight manual.[7] The VH-UHX flight manual recovered from the accident site was severely damaged. It had been partially burned, and was fuel and water soaked, and was therefore incomplete. An exemplar flight manual was sourced that advised:

Main driveshaft – Check condition and security.

Figure 16: KAflex main transmission drive shaft

Figure 16: KAflex main transmission drive shaft

The main components of the drive shaft and their quantity are labelled

Source: CASA, annotated by the ATSB

Figure 17: KAflex – normal operation and fail-safe mode

Figure 17: KAflex – normal operation and fail-safe mode

Source: Kamatics Corporation, annotated by the ATSB

KAflex drive shaft part history

Component records for the drive shaft, serial number 0110, were provided by the manufacturer and showed that the KAflex (fitted to VH-UHX) had been released into service in 1978 as part number SKCP2180-1 to be operated and maintained by the US Army. The records further showed that in 1979, it had been returned to Kamatics for disassembly and the connecting hardware was changed over, being released as updated part number SKCP2281-103.

Throughout its history installed within the UH-1H helicopter, there was no specified life-limit or a time-between-overhaul for the KAflex. The shafts were operated and maintained on-condition and this maintenance practice continued when UH-1H helicopters were transferred to the civil register.

The maintenance organisation reported that the drive shaft hours had not been tracked because of the on-condition requirements associated with its service life. The KAflex was removed during the last scheduled phased inspection, approximately 39 hours prior to the accident. During that period of maintenance, the shaft was visually inspected prior to reinstallation into VH-UHX with no identified defects.

United States Federal Aviation Administration airworthiness directive

In 2018, Kamatics reported to the FAA their concern over several KAflex drive shaft failures that had occurred within UH-1H civil-operated helicopters. They identified that several variants of the KAflex were in extended use and had an unknown period of service. Prompted by those safety concerns, on 21 January 2022 the Federal Aviation Administration (FAA) issued airworthiness directive (AD) 2021-26-16, which became effective on 25 February 2022. The FAA AD advised that, if not addressed, an unsafe condition could result in the loss of engine power to the transmission and a subsequent loss of control of the helicopter.

The FAA AD required for operators to check the part number[8] and the total hours time-in-service of fitted drive shafts. A life-limit of 5,000 hours was also introduced by the FAA AD. If the drive shaft hours were unable to be verified through the maintenance records, the FAA AD required helicopter airframe total hours to be used as a measure of the overall drive shaft service life.

The FAA AD instructed that KAflex drive shafts with less than 5,000 hours service were able to be overhauled in accordance with FAA approved procedures. Additionally, shafts were to be removed from service if during visual inspection the following damage was identified:

  • broken, loose or missing hardware
  • bolt movement
  • fretting corrosion and fretting product
  • mechanical damage, nicks, indents or corrosion.

Examination of the KAflex from VH-UHX

A detailed metallurgical examination of the failed KAflex was completed at the ATSB’s technical facilities in Canberra. The drive shaft had fragmented into multiple pieces (Figure 18). The end fittings had remained attached to the engine and transmission, respectively, with the separated interconnect tube and fractured pieces of flex frame recovered from the burnt wreckage. As previously indicated, one of the flex frame segments was found in the compressor section of the engine. Several flex frame segments were unable to be located at the accident site.

The intense heat damage sustained from the post-accident fire consumed evidence of markings usually present on KAflex drive shafts, including a factory-applied serial number (ink-stamped onto each end fitting), and the factory-applied torque stripe (for each assembled nut and bolt). A permanent mechanical stamping onto the interconnect ‘SER NO 0110’ identified the drive shaft serial number, confirming its 1978 year of manufacture. 

Visual examination of the interconnect identified a portion at the end of the tube that had fractured with associated bell-mouth deformation. The fracture occurred where the transmission end fitting had resided during operation. A lip of material at the end of the interconnect tube had been rolled outward and the fracture surfaces smoothed, likely from sustained metal-to-metal frictional contact. The portion of the end fitting that resided within interconnect exhibited associated severe frictional damage to the shouldered portion of the coupling region (Figure 19). The ATSB noted the distinct similarity between this and other KAflex shafts that had entered fail-safe mode.

Kamatics technical data showed that the attachment hardware comprising the bolts, countersunk washers and the spacers were of the correct type for KAflex part number KCP2281-103. From that data it was established that of the recovered fragments there was 1 missing bolt from the engine portion of the drive shaft, and 3 missing bolts (and their nuts and washers) from the transmission portion of the drive shaft. Breakaway torque values were measured during disassembly of the KAflex for all remaining fasteners. None were shown to meet the assembly specifications, though it was identified that shaft had fragmented and had been exposed to a significant fire.

An additional missing washer from the transmission portion of the drive shaft was identified on an intact attachment bolt associated with a fractured flex frame (Figure 20). A red-coloured substance consistent with fretting product remained on the surfaces of the attachment bolt (associated with the missing washer) and the surrounding flex frame surfaces. Furthermore, 6 other countersunk washers had either radially cracked, or contained circumferential cracks (Figure 21). A metallurgical cross-section through one of the washers showed that angular cracks had initiated at the washer metallic coating, which had then penetrated into the steel substrate.

Detailed examination of the flex frame fracture surfaces was completed using an optical microscope and scanning electron microscope. Evident thermal damage to the surfaces of the damaged flex frames significantly damaged and/or obscured any possible fractographic evidence of the mechanism of failure. Similar thermal damage had occurred to washer / spacer attachment hardware. Many of the finer surface features on the flex frame fractures were completely or partially obscured from that thermal damage.

The results of ATSB’s technical examination were presented to Kamatics, the US National Transportation Safety Board, CASA and the operator’s maintenance personnel. Kamatics advised that the frictional damage sustained to the end fitting and corresponding fracture of the interconnect indicated that the shaft had entered fail-safe mode during operation.

Figure 18: KAflex prior to disassembly at the ATSB’s technical facilities

Figure 18: KAflex prior to disassembly at the ATSB’s technical facilities

Not all flex frame fragments or their attachment hardware were recovered at the accident site. One flex frame fragment was found in the compressor section of the engine.

Source: ATSB

Figure 19: Photographic montage of the KAflex showing damage sustained upon entering fail-safe mode

Figure 19: Photographic montage of the KAflex showing damage sustained upon entering fail-safe mode

The identification of severe frictional damage and fracture that had occurred to both the interconnect and the end fitting (transmission) indicated the shaft had entered fail-safe mode

Source: ATSB

Figure 20: Photographic montage identifying a missing washer and evidence of fretting product on the associated flex frame and its attachment hardware

Figure 20: Photographic montage identifying a missing washer and evidence of fretting product on the associated flex frame and its attachment hardware

Source: ATSB

Figure 21: Photographic montage of cracks (arrowed) in countersunk washers from the KAlex attachment hardware

Figure 21: Photographic montage of cracks (arrowed) in countersunk washers from the KAlex attachment hardware

The intact washer (left image) displaying a series of cracks (arrowed) was recovered from the flex frame shown at Figure 20

Source: ATSB

Other occurrences

The ATSB identified one occurrence in Australia and 6 in the US with similarities to this accident. Further details of the publicly available accident reports of these occurrences are contained at Appendix A of this report. In all cases, the fail-safe feature of the drive shaft performed as designed after fracture of a flex frame or attachment bolt, allowing continuous operation under load and time for the pilot to commence an emergency landing. Excluding VH‑UHX, the other accidents were non-fatal, however significant damage was sustained during some of the forced landings. To summarise:

  • Pilots became aware of a drive system problem due to increased noise i.e. a ‘howling’ or ‘shrieking’ sound and vibrations from the transmission area.
  • Once the main drive shaft has failed, stiffness through the flight controls may occur.
  • Once in fail-safe mode KAflex drive shafts transmitted operational power for just a few minutes, which was significantly less than the 21.5 minutes established during the Kamatics qualification testing (with the caveat that the testing did not consider a bolt failure and the associated rapid decline in the shaft).
  • Failures of the KAflex drive shafts were initiated by the fatigue cracking and eventual fracture of a flex frame, with a single reported instance of an attachment bolt fatigue fracture.
  • In each case, unique and deteriorating contact damage occurred to the interconnect and end fitting surfaces once the drive shaft entered fail-safe mode (Figure 22).
  • There was one other reported instance of a rapid nose-right yaw (rotation of the helicopter about its vertical axis), and associated loss of directional control prior to impact with the terrain, following the subsequent total failure of the drive shaft. That accident is documented in ATSB investigation AO-2019-070 and is also further discussed in Appendix A of this report.

The contributing factors that have been established from the investigation of other KAflex failures included:

  • unauthorised / inappropriate overhaul methods
  • operation with sustained misalignment of the helicopter drive system
  • drive shaft components being out-of-tolerance
  • high-frequency utilisation and heavy lifting operations
  • excessive wear due to loose attachment hardware (i.e. bolts).

Figure 22: A KAflex that entered fail-safe mode due to fatigue cracking of a flex frame element

Figure 22: A KAflex that entered fail-safe mode due to fatigue cracking of a flex frame element

Physical characteristics of fail-safe mode after complete failure of the drive shaft include severe frictional damage and bell-mouth (opening) deformation to the end fitting, along with associated frictional damage, deformation and eventual fracture of the interconnect.

Source: Kamatics Corporation

Safety analysis

Introduction

On 14 February 2022, the pilot of a Garlick UH-1H helicopter was supporting the Tasmania Fire Service (TFS) by providing aerial firebombing support to the Lebrina bushfire, northern Tasmania. At 1509 the pilot departed the local TFS staging area to extinguish a small spot fire in a region of unburnt vegetation on the western flank of the fireground. The helicopter was observed to unexpectedly miss the designated target with the underslung water load. It was then tracked toward an open paddock, losing directional control as it was slowed on approach to the paddock, before pitching steeply nose-down and colliding with terrain.

The following analysis details the factors that prevented the skilled and experienced pilot from conducting a survivable descent and landing. 

Technical failure

The ATSB considered possible reasons for the apparent premature release of water from the underslung bucket during the accident flight, which was captured in imagery by personnel onboard a nearby helicopter. Two eyewitnesses, who knew the accident pilot and also conducted aerial firefighting operations, observed the release of the water from an elevated height. Based on their knowledge of the operation and the accident pilot, who was well-regarded for precision water bombing operations, they considered that the off-target release of the water was unlikely to have been accidental.

Technical examination of the KAflex drive shaft identified definitive evidence of the disruption and disconnection of the KAflex coupling that transmitted engine drive torque to the transmission. Further, this disruption was characteristic with a torsional-induced breakout of the transmission‑side interconnect tube and the end fitting. Metallurgical evidence of high contact forces and severe surface friction damage was identified on both transmission coupling and the interconnect bore. This failure mode typically results from fatigue cracking and fracture of an interconnected flex frame or attachment bolt.

Of significance in this occurrence was the presence of fretting product (oxide dust/deposits) over a frame joint at the transmission coupling, together with extensive wear to the plain shank of the associated frame bolt. The attaching bolt was found to be intact but missing one of the washers. It is uncertain when the washer separated, however the presence of the fretting product indicated the flex frame joint at that location had been unstable for a significant period of operation.

The effects of post‑impact fire on the surfaces of the recovered flex frames significantly damaged and/or obscured any possible fractographic evidence of the mechanism of failure. Despite this, the extent of physical evidence around the general failure of the coupling was sufficient to conclude that the shaft had partially failed and entered fail-safe mode.

Considering pilot accounts from previously investigated occurrences, although drive is initially maintained when a KAflex enters fail-safe mode, this malfunction results in significant noise and increased vibration. It was therefore considered likely that the early water release while on approach to the spot fire and the diversion toward clear ground were deliberate actions taken by the pilot in response to activation of the fail-safe mode.

Emergency management

Analysis of the recorded flight data confirmed that, following the water release, an initial powered descent was conducted by the accident pilot toward the open field. However, the analysis also indicated that, as the helicopter was slowed and gently climbed over the open area, complete failure of the KAflex occurred. This resulted in an instantaneous and complete loss of drive to the rotor system. At that time, the helicopter was outside of the avoid area of the height-velocity envelope, indicating that a successful forced landing should have been possible. As the outcome was significantly more severe, the ATSB considered the factors that hampered management of the emergency.

Based on the observations of a pilot positioned at the staging area, the loss of drive to the rotor system was accompanied by an abrupt and significant right yaw. That direction of movement was consistent with the described helicopter behaviour following a previous KAflex drive shaft failure, but contrary to the expected left yaw detailed in the Flight Manual. This indicated that the reduction in rotor RPM following the sudden loss of drive may have disproportionately reduced tail rotor thrust.

In addition, Bell Helicopter reported that as the main transmission slowed, reduced pressure from the hydraulic system would lead to a stiffening of the flight controls, increasing the potential for the pilot to over control the anti-torque pedals to the tail rotor. Alternatively, given their proximity, it is possible that debris from the failing KAflex may have impacted the flight controls and/or the tail rotor drive shaft, and affected their operation. The degree of fire damage prevented an assessment of whether that occurred.

Irrespective of the reason for the right yaw, it may have led to an inappropriate pilot response (at least initially), as uncommanded right yaw is generally associated with a loss of tail rotor thrust, due to either a related mechanical failure or an aerodynamic loss of tail rotor effectiveness.

In addition to any potential uncertainty created by the yaw direction, as the engine was still operating when the KAflex drive shaft decoupled, the pilot was likely presented with unusual indications of simultaneous declining rotor RPM and increasing engine RPM due to the sudden unloading of the transmission and rotor system. Additionally, it was reported that the pilot operated the helicopter with the electrical hook release system deactivated. Therefore, release of the bucket and longline could only be achieved via the foot‑activated pedal, which would probably have delayed the response to the unexpected yaw.

In combination, these factors would have presented the pilot with a significant challenge to both troubleshoot and respond to the emergency.

Analysis of the flight data showed that, during the reported rotations immediately following the failure of the KAflex, VH-UHX continued a shallow climb for an 8 second period. Consequently, as there was no drive being provided to the rotor system during this time, significant drag on the main rotor would have reduced the rotor RPM. The helicopter was then observed to abruptly pitch down (which may have further degraded the rotor RPM) and descend steeply. This was followed by recovery of directional control by the pilot.

Mistiming of collective input by the pilot during the termination and landing was considered unlikely given their flying experience and previous demonstration of competency in conducting autorotative approaches. Further, ground scars showed that the helicopter was oriented in a pitch up attitude and tracking straight, indicating the helicopter was flared by the pilot prior to impact.

The ATSB concluded that, possibly exacerbated by insufficient height, the pilot was unable to recover the low RPM state during the unpowered descent. This limited their ability to decelerate and arrest the descent of the helicopter during the emergency landing, leading to high impact forces, and the subsequent post-impact fire.

Findings

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

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

From the evidence available, the following findings are made with respect to the collision with terrain involving Garlick Helicopters UH-1H, registered VH-UHX, that occurred 36 km north of Launceston, Tasmania on 14 February 2022.

Contributing factors

  • During the conduct of firebombing operations, the helicopter’s engine-to-transmission main KAflex drive shaft partially failed due to fracture of a flex frame attaching bolt, or a flex frame element and entered fail-safe mode. It is probable this resulted in the pilot jettisoning the water load from the underslung bucket and diverting toward clear ground.
  • As the helicopter was slowed during a descent over clear ground, the main drive shaft decoupled, probably at about the time the longline and underslung bucket were released. The failure resulted in an instantaneous loss of drive to the rotor system.
  • Following loss of drive to the main rotor system, the pilot was unable to complete a survivable autorotative descent and landing, probably due to a critical reduction in main rotor speed.

Safety issues and actions

Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. All of the directly involved parties are invited to provide submissions to this draft report. As part of that process, each organisation is asked to communicate what safety actions, if any, they have carried out to reduce the risk associated with this type of occurrences in the future.

Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. The ATSB has been advised of the following proactive safety action in response to this occurrence.

Proactive safety action taken by Civil Aviation Safety Authority

Action number:AO-2022-006-PSA-01
Action organisation:Civil Aviation Safety Authority
Action status:Closed

CASA released Issue 3 to Airworthiness Bulletin (AWB) 63-004 Kamatics Corporation KAflex Drive Shafts – UH-1H and Bell 407, on 28 June 2022. The purpose of the AWB was to alert operators and maintainers:

  1. That the approved Bell 407 Flight Manual did not adequately detail the pre-flight check inspection requirements with regard to checking the KAflex drive shaft for serviceability.
  2. To alert operators of 2 ATSB investigations involving UH-1H helicopters where the KAflex drive shafts had failed (ATSB investigation number AO-2019-070 and AO-2022-006).
  3. That the United States Federal Aviation Administration airworthiness directive AD 2021‑26-16 was applicable and imposed a 5,000 hour life-limit on the drive shaft.


Following review of the draft investigation report, on 5 March 2024, CASA released Issue 4 to AWB 63-004. Reflecting the advisory material contained in ATSB’s investigation report, Issue 4 of the AWB contained further advice to operators and maintainers on potential operational aspects once a KAflex has entered fail-safe mode.

Safety advisory notice to operators and maintainers of Garlick UH-1H helicopters

SAN number:AO-2022-006-SAN-01
SAN release date:15 June 2022

On 15 June 2022 the ATSB advised operators of UH-1H helicopters to note the details of this accident and to look for the presence of corrosion, fretting, frame cracking, missing or damaged attaching hardware during all inspections of the KAflex drive shaft. Any identified defects were to be notified to the Civil Aviation Safety Authority.

Additionally, operators should be aware of Kamatics’ concern of shaft serial numbers 0635 and below for the UH-1H helicopter that may be fitted with legacy attachment hardware. Kamatics should be contacted if a shaft in the affected serial number range is identified.

Proactive safety action taken by Tasmania Fire Service

Action number:AO-2022-006-PSA-02
Action organisation:Tasmania Fire Service
Action status:Closed

The Tasmania Fire Service (TFS) advised that, since the accident, they have completed the following agency actions in relation to their aviation and emergency response operations:

  • TFS has transitioned to the Tasmanian Government Radio Network to enable direct communications with other emergency service organisations, fire land managers and aircraft operators working at multi-agency incidents.
  • In November 2022, TFS conducted an inter-agency training exercise to test the response to a rescue incident in remote and isolated areas. The exercise tested the TFS timelines, incident management command and control, communication links, processes and roles of each agency. A key outcome was that the notification procedures have been improved between TFS, Tasmania Police and the Ambulance Tasmania Air Rescue Aviation Unit.

Proactive safety action taken by Kamatics

Action number:AO-2022-006-PSA-03
Action organisation:Kamatics
Action status:Closed

Kamatics advised that for KAflex shafts returned to their factory they will complete a teardown inspection to identify evidence of fretting, cracked washers or any other undesirable defect in hardware items normally replaced during overhaul.

Proactive safety action taken by Richmond Valley Aviation

Action number:AO-2022-006-PSA-04
Action organisation:Richmond Valley Aviation
Action status:Closed

Richmond Valley Aviation, the maintainer and operator of VH-UHX, advised that subsequent to the accident they removed all KAflex drive shafts from service in aircraft that they maintained. Additionally, to mitigate the potential risk of future main transmission drive shaft failures they have elected to use an alternate type of drive shaft that has a 600 hour / 12-month inspection and re‑grease interval.

In their response they identified that the couplings of the alternate drive shafts have external temperature indicators that can provide a warning to pilots / maintainers of potential problems before they escalate.

Glossary

ADairworthiness directive
AWBairworthiness bulletin
CASACivil Aviation Safety Authority
CASRCivil Aviation Safety Regulations
CVRcockpit voice recorder
FAAFederal Aviation Administration
FDRflight data recorder
IASindicated airspeed
ICAinstructions for continued airworthiness
NSTBNational Transportation Safety Board
RPMrevolutions per minute
TFSTasmania Fire Service

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Richmond Valley Aviation
  • the helicopter owner and manufacturer
  • Kamatics Corporation
  • Bureau of Meteorology
  • United States Federal Aviation Administration and National Transportation Safety Board
  • Tasmania Fire Service
  • Civil Aviation Safety Authority
  • witnesses
  • the aircraft maintainer
  • the pilot’s flight examiner
  • onboard recorded GPS data.

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:

  • Richmond Valley Aviation
  • the helicopter owner and manufacturer
  • Kamatics Corporation
  • United States Federal Aviation Administration and National Transportation Safety Board
  • Tasmania Fire Service
  • Civil Aviation Safety Authority
  • the aircraft maintainer
  • the pilot’s flight examiner
  • witnesses

Submissions were received from:

  • Richmond Valley Aviation
  • the helicopter manufacturer
  • Kamatics Corporation
  • National Transportation Safety Board
  • Tasmania Fire Service
  • Civil Aviation Safety Authority
  • the pilot’s flight examiner
  • a witness.

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

Appendix A: Related accidents and other investigations

During the course of this investigation, the ATSB became aware of similar accidents involving failure of KAflex main drive shafts. The United States (US) National Transportation Safety Board (NTSB) investigated and reported on 2 UH-1H accidents and the ATSB has previously investigated one other accident. Kamatics Corporation investigated 4 other failures and they can be contacted for details.

The relevant investigation reports are available at www.ntsb.gov and www.atsb.gov.au.

NTSB accident number SEA97LA126

On June 3, 1997, a Garlick UH-1H helicopter, collided with the terrain during a forced landing near Addy, Washington. The commercial pilot, who was the sole occupant, was not injured, but the aircraft sustained substantial damage. According to the pilot, they were about 30 minutes into the first logging cycle of the day and heading back to pick up another log load when the accident sequence began. The pilot heard a high-speed shredding sound with accompanying high‑frequency vibration.

The pilot immediately lowered the collective and released the underslung 150 foot longline. While transiting away from tall forest trees the sound and vibration rapidly worsened. The pilot heard a second loud noise and identified that the main rotor RPM began to decay, prompting an emergency landing.

The NTSB found that a number of the flex frames on the drive shaft had failed. The KAflex was sent to the NTSB materials laboratory, and their metallurgical examination identified evidence of pre-existing fatigue cracking on the fracture surfaces of a flex frame.

NTSB accident number WPR15LA178

The pilot of a UH-1H helicopter reported that on 31 May 2015, while manoeuvring the helicopter at low altitude during logging operations, a vibration and howling sound was detected coming from the transmission area. In response, the pilot immediately initiated a precautionary landing, however, the flight controls stiffened as the helicopter settled to the ground and the main rotor RPM reduced. The helicopter landed heavily.

The NTSB materials laboratory found multiple fractures had occurred to the KAflex drive shaft assembly. The KAflex failure was initiated by the fatigue cracking and fracture of an attachment bolt that secured the coupling assembly to the transmission shaft flange (Figure A1). No evidence of any material anomalies were found in the fractured bolt.

Figure A1: The KAflex entered fail‑safe mode following fatigue fracture of an attachment bolt, prior to total failure of the drive shaft

Figure A1: The KAflex entered fail‑safe mode following fatigue fracture of an attachment bolt, prior to total failure of the drive shaft

The interconnect and end fitting displayed characteristic contact features from entering fail-safe mode

Source: NTSB

ATSB investigation number AO-2019-070

On 7 December 2019, the pilot of a UH-1H helicopter was completing fire control aerial work. While hovering and preparing to uplift river water into the underslung bucket, the pilot heard a momentary ‘burring’ noise with a ‘buzzing’ vibration through the airframe. The pilot aborted the uplift and started to transition away from the hover when the noise and vibrations resumed. The pilot noted the intensity increased when the collective lever was raised.

The pilot radioed the firefighting personnel of the intention to land, released the bucket and longline, and tracked towards a clear area. The continuing noise indicated to the pilot that the condition of the helicopter was deteriorating. In response, the pilot elected to divert to a small clearing. On approach to the hover, at a height of about 10 ft, the helicopter commenced an uncontrolled rotational yaw to the right, which the pilot was unable to stop. The helicopter rotated about 180° from the approach heading before landing hard.

The ATSB’s metallurgical examination found that the KAflex drive shaft had failed due to the development of a fatigue crack in a flex frame that led to its fracture prior to the hard landing (Figure A2).

Figure A2: Fatigue cracking of a flex frame element led to the shaft entering fail-safe mode prior to total failure during operation

Figure A2: Fatigue cracking of a flex frame element led to the shaft entering fail-safe mode prior to total failure during operation

The interconnect and end fitting displayed characteristic contact features from entering fail-safe mode

Source: ATSB

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

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 Coat of Arms, ATSB logo, and photos and graphics in which a third party holds copyright, this publication is licensed under a Creative Commons Attribution 3.0 Australia licence.

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

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

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

[1] Tasmania Fire Service, Sustainable Timber Tasmania, Parks and Wildlife Service, State Emergency Service and Reliance Forest Fibre responded to the fire.

[2] Formerly a Bell Helicopters UH-1H.

[3] This type of flight uses a range of ex-military, historic and replica aircraft to offer adventure-style flights to the general public for a fee.

[4] The compressor section of the engine was examined using a flexible video borescope.

[5] Requirements relating to the fitment of flight recorders are detailed in Part 91 Manual of Standards (MOS), Division 26.9 Flight recording equipment.

[6] The proficiency check was completed on 11 December 2020.

[7] Department of the Army, Operator’s Manual, Army Model UH-1 H/V Helicopter, UH-1H TM-55-1520-210-10 section 8-19 Area 6 para 2.b

[8] Kamatics Corporation KAflex part number: SKCP2180-1, SKCP2281-1, SKCP2281-1R or SKCP2281-103

Occurrence summary

Investigation number AO-2022-006
Occurrence date 14/02/2022
Location 36 km north of Launceston
State Tasmania
Report release date 12/03/2024
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Garlick Helicopters Inc
Model UH-1H
Registration VH-UHX
Serial number 4572
Aircraft operator Richmond Valley Aviation
Sector Helicopter
Operation type Aerial Work
Departure point Pipers Brook Road, Tasmania
Damage Destroyed

Fuel starvation and collision with water involving Rockwell International 114, VH-WMM, 1 km north of Redcliffe aircraft landing area, Queensland, on 19 December 2021

Preliminary report

Preliminary report released 28 February 2022

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 19 December 2021, at about 0908 Eastern Standard Time,[1] a Rockwell International 114, registered VH-WMM, departed Redcliffe Aerodrome, Queensland, for a private scenic flight under visual flight rules. On board were the pilot and 3 passengers. The weather conditions were fine, with light winds from the east.

A number of witnesses located at the aerodrome, on the water in pleasure craft, and in other aircraft, observed VH-WMM (Figure 1). Witnesses at the aerodrome stated that, after VH-WMM took off from runway 07,[2] the landing gear was retracted and, a short time later, the engine ran rough for a brief period before stopping completely.

Another pilot was on their final approach for runway 07 and observed VH-WMM airborne. As that pilot was making their landing, they heard the pilot of VH-WMM broadcast on the radio that they were returning to the aerodrome.[3]

According to witnesses, the pilot of VH-WMM made 2 left turns, which were consistent with manoeuvring the aircraft back toward the western end of runway 07. During the return to the aerodrome, the pilot extended the landing gear. Description of the flight from the witnesses was consistent with controlled flight during this period.

As the aircraft neared the mangrove tree line to the north of the aerodrome, it was observed to descend and ditch into the water, about 170 m from the shoreline. During the ditching, the aircraft flipped over, coming to rest inverted in about 2 m of water.

Witnesses at the aerodrome and on board nearby boats, contacted emergency services and the Australian Volunteer Coast Guard. After being notified by one of the witnesses, a nearby vessel made its way to the aircraft, arriving about 5 minutes after the accident. The vessel’s occupants stated there was low visibility in the water and the fuselage was resting inverted on the seabed. This led to difficulty for first responders identifying how to open the aircraft doors.

The pilot of another aircraft flying overhead observed VH-WMM ditch in the water and contacted air traffic control (ATC) to advise them of the accident. That pilot remained overhead the accident site while boats arrived at the scene, and relayed information to ATC. A Coast Guard vessel arrived onsite; however, the crew were also unable to gain access into the aircraft’s cabin.

Queensland Police Service divers arrived a number of hours later, confirming that the pilot and 3 passengers had been fatally injured. The aircraft was destroyed. 

Figure 1: Redcliffe Aerodrome and VH-WMM approximate flight path and accident site

picture1-ao-2021-053.png

Source: Google Earth, annotated by the ATSB

Context

Pilot information

The pilot held a valid Private Pilot Licence (Aeroplane) with the last flight review in July 2021, and a Class 2 Aviation Medical Certificate, valid until February 2023. The pilot held single and multi‑engine aeroplane ratings and endorsements for manual propeller pitch control, retractable undercarriage and formation flying. At the time of the accident, the pilot had about 504 hours total aeronautical experience.

Aircraft information

General information

The Rockwell International 114 is a 4-seat, single-engine aeroplane with fully retractable landing gear. It is powered by a 6-cylinder Lycoming IO-540 fuel-injected engine, and is fitted with a 3-blade constant-speed propeller.

VH-WMM was manufactured in the United States in 1977 and was first registered in Australia in May 2013. The last periodic inspection was conducted on 7 July 2021. At the time of the accident, VH-WMM had accrued a total time in service of 3,431.4 hours and had flown about 11 hours since the last inspection.

The aircraft type has 2 doors for pilot and passenger access, one on each side at the front of the aircraft cabin (Figure 2).

Figure 2: VH-WMM

picture2-ao-2021-053.png

Source: Nathen Sieben, modified by the ATSB

Site and wreckage information

The wreckage was located about 1 km north of the Redcliffe Aerodrome, on a tidal flat (Figure 3). The accident occurred about 40 minutes before high tide, and the water depth at the time of the accident was about 2 m.

The aircraft had impacted the water in a slight nose-down and upright attitude with the landing gear in the extended position. After contacting the water, the aircraft flipped over in the direction of travel, resulting in the aircraft being inverted.

The impact had torn the engine from its mounts and there was structural damage to the fuselage underside and right wing. Fuel was leaking from the right underwing fuel vent, and a strong fuel smell was evident at the site. The flaps were in a retracted position at the time of the accident.

Figure 3: VH-WMM accident site at low tide

picture3-ao-2021-053.jpg

Source: ATSB

Wreckage examination

A marine salvage company recovered the aircraft the following morning on high tide and, after floating the wreckage to the Scarborough boat ramp, it was transported to a secure storage facility for a detailed examination (Figure 4). Removal of the rear fuselage and engine was carried out to necessitate transportation by road.

The examination revealed:

  • all components of the aircraft were accounted for at the accident site
  • no pre-impact defects were identified
  • a quantity of fuel was removed from the aircraft
  • the engine and propeller were able to be rotated.

Figure 4: VH-WMM recovered for examination

picture4-ao-2021-053.png

Source: ATSB

Further investigation

To date, the ATSB has:

  • recovered and examined the aircraft wreckage
  • conducted witness interviews
  • conducted a disassembly and examination of the engine
  • examined the maintenance history of the aircraft
  • examined security camera footage from the aerodrome.

The investigation is continuing and will include:

  • a disassembly of the propeller
  • testing of retained engine components
  • analysis of data recorded from onboard systems
  • a review of mobile phone footage.

Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.

A final report will be released at the conclusion of the investigation.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. Eastern Standard Time (EST) is Universal Time Coordinated (UTC) +10 hours.
  2. Runway number: the number represents the magnetic heading of the runway. In this case, 07 equates to 70°.
  3. Radio communications on the common traffic advisory frequency at Redcliffe Aerodrome were not recorded.

Final report

Executive summary

What happened

On the morning of 19 December 2021, a Rockwell Commander 114, registered VH-WMM, departed Redcliffe aircraft landing area, Queensland for a private flight. On board were a pilot and 3 passengers. Shortly after take-off, the engine lost power and the pilot elected to return to the airfield. During the return, the aircraft lost altitude and impacted the ocean before becoming inverted. The occupants were unable to escape the aircraft and were fatally injured, and the aircraft was destroyed.

What the ATSB found

The ATSB found that during preparation for the flight, a perceived engine problem distracted the pilot during the conduct of pre-take-off checks. After rectifying the issue, the pilot did not complete the remaining pre-take-off checks (including fuel tank selection) before departure. Before take-off when there was no time pressure (and during the inflight emergency when there was), checks and action items were only done by memory rather than using the pilot operating handbook or third‑party checklists also on board.

While stored in the hangar, most of the fuel moved into the right wing tank. The pilot would have been aware of the fuel imbalance from measuring fuel in both tanks via a dipstick before flight. However, it was likely that the fuel tank selection prior to take-off was to the left fuel tank only, which led to fuel starvation and engine stoppage soon after take-off.

The pilot, likely experiencing the effects of stress and time pressure following the engine power reduction and then stoppage, did not conduct initial emergency actions and attempted to return to the runway for landing. However, the pilot did not maintain glide speed, and the aircraft impacted shallow water prior to reaching the airfield. During the return to the airfield, the pilot had extended the undercarriage for the intended landing. This contributed to the aircraft inverting when it collided with water. This likely resulted in occupant disorientation and added difficulty in operating the exits, reducing their ability to escape.

It is very likely that the passengers did not receive information about the brace position or actions to be taken in the event of a ditching as part of the pre-flight briefing. In the limited time available inflight after the power loss, the pilot also did not provide an emergency briefing or any instructions to passengers prior to impact with the water.

While the pilot was primarily responsible for the operation of the aircraft exits in an emergency, seating a child, who may require assistance, adjacent to an exit instead of an adult meant that a less suitable passenger was available to operate the exit.

Safety message

Use of the approved aircraft checklists, taken from the pilot operating handbook, provides pilots with the appropriate checks to be conducted for the aircraft type. Having these readily available in a written form, for the preparation and conduct of a flight, provides pilots with the detailed normal and emergency checks specific to the aircraft type without having to rely on committing these to memory. This ensures that aircraft are operated in a way that meets aircraft flight manual requirements and limitations.

Distraction can impact proper procedural processes and lead to interruption and omission of safety critical elements before take-off. The habit of restarting an interrupted checklist from the beginning is a means of ensuring that all steps to be performed are done so in order and the checklist is complete.

Proper fuel management will ensure fuel supply to the engine(s) remains uninterrupted at all stages of flight. The ATSB publication, Avoidable Accidents No. 5 - Starved and exhausted: Fuel management aviation accidents (AR-2011-112) outlines strategies and key messages for fuel management.

Thorough pre-flight briefings of passengers on how to operate exits, the brace position and actions that might be required in a ditching or other forced landing are essential to increase post‑impact survivability. Additionally, as supported by guidance, pilots should consider who might be best to assist in the case of an emergency, and brief and seat them accordingly.

The ATSB SafetyWatch highlights the broad safety concerns that come out of our investigation findings and from the occurrence data reported to us by industry. One of the safety concerns is: Reducing the severity of injuries in accidents involving small aircraft. 

The investigation

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

The occurrence

On the morning of 19 December 2021, at the Redcliffe aircraft landing area, Queensland, a Rockwell International 114 aircraft, registered VH‑WMM, was being prepared for a local private flight under visual flight rules.[1] On board for the flight were the pilot and 3 passengers. The weather conditions and visibility were good, with light winds from the east.

Closed circuit television (CCTV) showed the pilot conducting a pre-flight inspection of the aircraft. This included draining a small amount of fuel from each fuel tank drain to check for any water contamination and using a dipstick to check the fuel tank quantity of each tank. 

A passenger video (see Appendix - Sequence of events) was recovered from a mobile phone which showed portions of the taxi, before take-off checks, and the accident flight. Several witnesses at the airfield, in boats near the airfield, and in other aircraft also observed the flight of VH-WMM (Figure 1).

Before the take-off, passenger video showed the pilot conducting before take-off checks (from memory) and did not show the use of any written checklists. While conducting the engine run-ups, the pilot perceived a technical difficulty with the aircraft, and the checks were paused. After notifying a ground crew member by phone, the pilot taxied back toward the ground crew who was walking towards the aircraft on the taxiway. The ground crew member recalled that through hand signals, the pilot identified the issue as misidentification of the mixture control for the propeller pitch control and communicated that they had identified and corrected the problem.

The pilot then taxied again for runway 07 without continuing or restarting the interrupted before take-off checks and continued direct to the runway holding point. The occupants of VH-WMM then discussed where other traffic was in the circuit, before entering and backtracking to the end of the runway. VH-WMM then turned and commenced the take-off at 0908 local time.

After take-off from runway 07,[2] the aircraft’s undercarriage and flaps were retracted, and 62 seconds later, while in a left climbing turn, the engine RPM started to fluctuate, followed by a large drop in engine power 3 seconds later. The (adult) passenger, seated on the rear-right side of the aircraft then asked the pilot about fuel coming out of the top of the right wing; however, the pilot did not respond to the question. The video also did not indicate the pilot conducting any engine troubleshooting activities. The pilot made 2 further left turns, which were consistent with manoeuvring the aircraft back toward the western end of runway 07 (Figure 1), and the stall warning sounded twice. About 17 seconds after the power reduction (1 minute 31 seconds after take-off), the engine stopped. 

Four seconds later, the video recorded the undercarriage warning bell followed by the stall warning. Based on the recorded sounds, it is likely the pilot responded by lowering the landing gear. Another pilot who was on final approach for runway 07 heard the pilot of VH-WMM broadcast on the radio that they were returning to the airfield.[3] 

Figure 1: Redcliffe aircraft landing area and VH-WMM approximate flight path and accident site

Figure 1: Redcliffe aircraft landing area and VH-WMM approximate flight path and accident site

Source: Google Earth, annotated by the ATSB

Over 24 seconds, the stall warning sounded another three times, followed by a turn directly toward the runway and then further stall warnings, two successive drops of the right wing and then the sounding of the ‘stall’ voice alert.

Three seconds later, as the aircraft neared the mangrove tree line to the north of the airfield, it contacted the water, about 170 m from the shoreline. The aircraft overturned and came to rest inverted in about 2 m of water. 

The pilot of another aircraft that was inbound to Redcliffe who had also heard the pilot of VH‑WMM make the returning to the airfield call, was alerted to the possibility of an accident from an unknown person on the radio upon arrival. After observing an aircraft in the water, the pilot contacted Brisbane air traffic control (ATC) to advise them of the accident. The pilot remained overhead the accident site while boats arrived at the scene and continued relaying information to ATC. 

Witnesses at the airfield and on nearby boats contacted emergency services and the Australian Volunteer Coast Guard. After being notified by a witness on a kayak, a nearby vessel made its way to the aircraft, arriving about 5 minutes after the accident. Following the impact with water, the inverted orientation of the aircraft meant that the door handles were submerged. First responders reported that it was difficult to locate the handles to open the doors from the outside. When inverted on the seabed in mud and silt, the upper door latches were also unable to be located. The disturbance of the mud/silt further reduced visibility of the exits and their operating handles. 

A coast guard vessel arrived onsite; however, the crew were also unable to gain access into the aircraft’s cabin. Queensland Police Service divers arrived at the aircraft about 2 hours after the accident. They observed the water to be about 1.5 m deep. Upon entering the water, police observed that visibility was very poor. The pilot’s door was shut and could not be opened. The right door was unlocked and slightly ajar, and police were able to open the door with some difficulty. The pilot and 3 passengers were fatally injured, and the aircraft was destroyed. 

Context

Pilot information

The pilot held a valid Private Pilot Licence (Aeroplane) and a Class 2 aviation medical certificate, valid until February 2023. The pilot held single and multi‑engine aeroplane ratings and endorsements for manual propeller pitch control, retractable undercarriage, and formation flying. At the time of the accident, the pilot had logged 334.3 hours in VH-WMM and had about 505 hours total aeronautical experience. 

The flight instructor who conducted the pilot’s last flight review in July 2021 stated that the pilot was assessed on engine failure after take-off. They also described that the assessed procedures on that review were similar to the accident flight, insofar as location of engine power loss and the actions that were to be taken as a result. During the flight review, the pilot had performed all actions to a satisfactory level.  

Pilot medical history

A review of the pilot’s Civil Aviation Safety Authority (CASA) medical file identified that the pilot had disclosed a hypertension condition and that they had been prescribed medication for it but did not list any other health issues or concerns.

Discussion with the pilot’s next-of-kin and general practitioner (GP) identified that the pilot was a long term, type 2 non-insulin dependent diabetic. The pilot had been prescribed medication for at least 10 years with medical records indicating tracked blood glucose readings back to January 2003, and an immediate family history of non-insulin dependent diabetes. The pilot had also been diagnosed with high cholesterol and had been prescribed medication for its treatment. The GP was also aware of a family history of heart disease. 

Of the last 3 CASA aviation medical examinations, the pilot had not declared their high cholesterol, diabetic status, and diabetes medication to their CASA designated aviation medical examiner (DAME), however had disclosed family history of both diabetes and heart disease to the DAME. Regarding the question in relation to diabetes on the pilot’s pre-examination medical history, the pilot indicated ‘unsure’, which was later changed by the DAME to ‘no’ during the examination.

Toxicology reports showed that the pilot of VH-WMM had detectable quantities of several substances, including a prescribed medication, paracetamol, and an over-the-counter sedating antihistamine. A carbon monoxide concentration of less than 5% was also detected in the analysis.

The ATSB sought advice from a specialist toxicologist regarding the potential effects the detected substances may have had on the pilot during the accident flight. The advice indicated that the level of antihistamine detected in the samples was low and suggested the drug had been used between 12 and 24 hours prior to the accident. They also reported that although the medication the pilot had been prescribed may have increased the sedating effects of the antihistamine, given the low levels detected it was unlikely there was any significant impairment of the psychomotor skills[4] required to fly an aircraft.

The specialist toxicologist also identified that there may have been an interaction between the multiple antihypertensive medications that the pilot had been prescribed[5] to lower blood pressure. However, from the passenger video it was noted that the pilot did not appear to be physically incapacitated, so it is very unlikely the pilot experienced any form of incapacitation prior to the accident.  

Aircraft information 

General information

The Rockwell International 114 is a 4-seat, single-engine aeroplane with fully retractable, trailing link undercarriage. It is powered by a 6-cylinder Lycoming IO-540 fuel-injected engine and is fitted with a 3-blade constant-speed propeller. Passenger and pilot access is by a door on each side of the aircraft cabin (Figure 2).

VH-WMM was manufactured in the US in 1977 and was first registered in Australia in May 2013. The last periodic inspection was conducted on 7 July 2021. At the time of the accident, VH-WMM had accrued a total time in service of 3,431.4 hours and had flown about 11 hours since the last inspection.

Figure 2: VH-WMM

Figure 2: VH-WMM

Source: Nathen Sieben, annotated by the ATSB 

Fuel system

The Rockwell 114 fuel system consists of 2 integral (wet wing)[6] fuel tanks, 1 in each wing, with a fuel gauge for each tank located in the cockpit. The fuel capacity is 132.5 L for each tank, with 128 L considered usable. Both fuel tanks supplied the engine through the fuel selector, gascolator,[7] electric fuel pump and an engine driven fuel pump. The fuel selector valve had 5 positions, which allowed the pilot to select OFF, LEFT, BOTH, RIGHT and OFF positions. 

The last refuelling of VH-WMM occurred before a flight on 16 October with an uplift of about 120 L of AVGAS, taking the total quantity to about full tanks. VH-WMM was then operated for about 2.2 hours over 2 flights, prior to the accident flight. On the day of the accident, the ATSB calculated that about 115 L of fuel remained on board, equivalent to about half tanks. 

CCTV at Redcliffe airfield showed that prior to the flight, the wings of VH-WMM were not level while parked on the tarmac. The right wing at the tip was about 60 cm lower than the left, indicating a fuel imbalance, where the right wing contained a greater fuel quantity than the left wing. The right-wing low condition indicated that fuel crossflow from the left to right fuel tanks may have occurred while VH-WMM was hangered. 

It is a known issue with the Rockwell International 114 that when the fuel selector is not placed in the OFF position when parked, fuel can flow from one tank to the other. Once a crossflow has started, the increasing fuel weight will also increase the lean of the aircraft, further promoting the fuel crossflow. This results in further uneven fuel distribution, and sometimes an overflow of fuel through the wing tank fuel vents when this imbalance fills one tank completely. The ‘local fix’ amongst the Rockwell 114 community to prevent the crossflow was to set the fuel selector to OFF when the aircraft was parked for an extended period of time. The possibility of fuel crossflow in VH-WMM was also known to the pilot. 

A review of the aircraft’s logbooks showed that in April 2011, a maintenance intervention was performed on the fuel system due to a crossflow defect occurring when the fuel selector was set to BOTH fuel tanks. The fuel selector position of VH-WMM was unknown prior to the day of the accident, however it is likely that it was not selected to the OFF position.

Undercarriage system

The Rockwell 114 is equipped with a hydraulically operated undercarriage. The aircraft is fitted with an undercarriage warning system. A switch is mounted on the throttle quadrant which connects to an undercarriage warning bell, activating whenever the throttle is brought to idle while the undercarriage is retracted. 

Stall warning

The Rockwell International 114 is fitted with an aural stall warning system, that provides an audible tone to indicate that the aircraft speed is slowing to a speed that it can no longer produce lift in flight.

On board video recorded the stall warning sounding 13 seconds after the engine experienced the large drop in power. The stall warning continued sounding intermittently throughout the remainder of the flight, indicating that the aircraft was only marginally maintaining airspeed above the stall speed. The stall warning horn activated multiple times during the final approach until impact with water. This indicates that the aircraft would have been within 3-4 kt of the straight and level flapless stall speed of about 63 kt.

VH-WMM was also fitted with a voice alert system. This unit was an electronic device which detected the activation of the existing aircraft stall and undercarriage warning systems. It was configured to place a voice warning directly into the pilot headset and through a built-in speaker in the unit itself. In this situation, a pilot who may not hear the aircraft-generated stall warning horns because of noise cancelling headsets, will have an electronic voice annunciation of the warning. 

A witness who had flown with the pilot previously described the system as functional and that it was an effective warning tool. The passenger video detected one annunciation of ‘stall’ from the built-in speaker, just prior to impact. It is unknown if the system was alerting the pilot through the headsets during the flight, however it is likely that the system was functioning, as other pilots who had been on board for previous flights had observed its operation.

Engine information

The engine fitted to VH-WMM was last overhauled in July 1998 and had accrued about 988 flight hours in operation. The overhaul schedule as listed in Lycoming Service Instruction SI 1009BE was 12 years or 2,000 hours, whichever occurred first.  

Although the engine had exceeded the calendar schedule of the manufacturer’s time between overhaul, this was permissible when the engine was maintained in accordance with the CASA on‑condition[8] requirements. At the last annual inspection in July 2021, the maintenance organisation had completed a piston engine condition report verifying the engine serviceability, which then permitted the engine to continue in service.

Site & wreckage information

Onsite examination

The wreckage was located about 1 km north of the Redcliffe airfield, on a tidal flat (Figure 3). The accident occurred about 40 minutes before high tide, and the water depth at the time of the accident was about 2 m. The aircraft impacted the water on a heading of about 218° in an upright, slight right-wing low, nose-down attitude, with the undercarriage in the extended position, and with the wing flaps retracted. 

Ground scars observed on the tidal flat indicated that after entering the water, the aircraft nose wheel and propeller contacted the seabed leading to the aircraft overturning, resulting in sudden deacceleration and the aircraft coming to rest inverted. Witnesses described the water directly around the aircraft to be murky due to the mud and silt seabed having been disturbed by the aircraft impact. The left door (pilot door) was in a closed and latched condition when the ATSB arrived onsite. The right door was found by police divers to be slightly ajar, and difficult to open during the recovery operation. 

Figure 3: VH-WMM accident site at low tide

Figure 3: VH-WMM accident site at low tide

Source: ATSB

The aircraft fuselage underside and right wing showed evidence of hydraulic[9] compression from impacting the water surface, and the engine had separated from the aircraft. The impact to the fuselage underside damaged the fuselage skins forward and aft of the wing main spar carry‑through, resulting in a large hole. The engine firewall had been punctured by the engine and the left rear side window was broken. The identified damage would have allowed water ingress into the fuselage. Fuel was visibly leaking from the right underwing fuel vent, and a strong fuel smell was evident at the site. 

Wreckage examination

The wreckage was recovered to a secure storage facility for a detailed examination. ATSB investigators established flight control continuity before the rear of the fuselage and empennage were separated to facilitate transport from the recovery point.  

A further flight control examination was performed with no defects noted. All components of the aircraft were identified and accounted for, and no pre-existing defects were noted with the airframe or engine.

Fuel system examination

Examination of the aircraft fuel system was carried out and found that the fuel selector was set to the LEFT tank at the time of the accident, and the auxiliary fuel pump was switched OFF. The gascolator was disassembled and contained water. After recovery of the wreckage, the fuel tanks’ contents were drained and consisted of:  

  • right wing: about 85 L of AVGAS recovered, with no visible water
  • left wing: about 25 L of water, with no visible AVGAS.
Engine & propeller examination

The engine and propeller displayed no pre-existing damage. The propeller damage was indicative of low rotational energy at the time of impact and exhibited damage to the blades and spinner due to impact with the seabed. The engine was externally examined, all components were accounted for, and the engine was able to be rotated. The engine was disassembled and examined at a CASA-approved engine overhaul facility under the supervision of the ATSB. The engine showed no evidence of pre-impact mechanical discontinuity or defects which would inhibit normal operation. 

Examination and testing of the engine fuel system was performed at a separate CASA-approved overhaul facility under ATSB supervision. Some system components had internal corrosion; however, this was most likely due to saltwater immersion. After removal of the corrosion, the system components tested correctly for operation. 

The fuel control unit (FCU) initially could not be tested. A disassembly of the FCU found internal corrosion within the regulating system and the centre body seal was found to be separated. The centre body seal was examined at the ATSB’s technical facilities in Canberra. ATSB determined that the internal seal separation had occurred when the FCU was disassembled for examination and was not a prior defect. 

Rockwell 114 procedures

Before take-off checklist 

At each critical phase of aircraft operation, pilots refer to checklists to guide them through specific items to configure the aircraft for the next planned phase of the flight. The Rockwell 114 pilot’s operating handbook (POH) [10] stated in 3 separate checklists,  ‘interior’, ‘before starting engine’, and ‘before take-off’ checklists, that the fuel selector valve is to be set to the BOTH position before the aircraft is ready for take-off.

Figure 4 shows the Rockwell 114 ‘before take-off’ checklist as detailed in the POH. Annotations highlight where the interruption occurred at the beginning of the accident flight, and the steps not completed as identified in the passenger video. The POH was located at the accident site at the rear of the pilot seatback, and passenger video showed that it was not accessed during the before take-off checks or during the flight.

Figure 4: Before take-off checklist

Figure 4: Before take-off checklist

Source: Rockwell 114 pilot’s operating handbook, annotated by the ATSB

Third-party checklists

CCTV footage showed the pilot passing a folder to the adult passenger who placed it into the rear of the pilot seatback prior to engine start. This folder was found on-site in the rear of the pilot seatback pocket and contained the third-party checklists inside. Both of these checklists had interpretations of the Rockwell 114 POH checklists and had differences to the approved manufacturer’s documentation. This included changes in the checklist sequence, and omissions of some elements including the absence of one of the fuel selector checks. 

CASA issued AC 91-22v2.0 Aircraft checklists, in November 2021 to provide guidance on establishing and using aircraft checklists and is derived from Civil Aviation Safety Regulation 91.095 Compliance with flight manual. This stated that any third-party checklists ‘must concisely convey each procedural step in correct sequence’ to ‘ensure aircraft are operated in a way that meets flight manual requirements and limitations.’ 

The US Federal Aviation Administration released a safety alert for operators (SAFO) 17006, in April 2017, warning pilots and operators of the risks of using commercially available and personally derived, third-party checklists. 

An acquaintance who had regularly flown with the pilot reported that the pilot would also use generic mnemonic checklists that had been committed to memory, instead of the POH or the third‑party checklists. The commonly used mnemonic covered some, but not all of the checks required by the POH checklist.  

Engine failure management

The Rockwell 114 POH emergency procedures checklist for an in-flight engine failure stated that the glide speed of 82 kt should be adopted, the auxiliary fuel pump selected on, mixture full rich, and the fuel selector be placed on the fuller tank to rectify possible fuel starvation. 

Maintaining the published glide speed in flight gives the optimal amount of lift for the least amount of drag, thereby giving the greatest glide distance for the amount of height lost during the descent.

Rockwell 114 ditching procedure 

A ditching is a controlled emergency landing on water. The Rockwell 114 POH ditching procedure identified that on approach to a ditching, the airspeed should be maintained at 82 kt. 

The procedure followed on to list: transponder (if installed) set to 7700, and a mayday call should be made. The emergency locator transmitter should be activated if installed, seats, seatbelts, shoulder straps and loose objects should be secured, flaps should be up, cowl flaps closed, and the undercarriage retracted. 

On final approach, flaps should be set to 20°, airspeed reduced to 74 kt, the undercarriage should remain retracted, and propeller set to high RPM. On touchdown, the elevator should be full aft, and the fuel selected to OFF.

Ditching guidance

In 2004 the ATSB made recommendation R20010258 which stated:

The Australian Transport Safety Bureau recommends that the Civil Aviation Safety Authority educate industry on procedures and techniques that may maximise the chances of survival of a ditching event. Part of that education program should include the development of formal guidance material of the type contained in the UK CAA General Aviation Safety Senses leaflet 21A Ditching.

In response to the recommendation CASA published CAAP 253-1(1) Ditching. This guidance was reissued in the form of AC 91-09 v1.0 and included but was not limited to the following safety advice about conducting a ditching:

For an aeroplane, it is likely to end up in a nose down vertical position after impact. Opening a forward door in these circumstances to escape may cause rapid water entry. Planning for this circumstance should include consideration of which exit might be opened prior to and after impact and briefing passengers on precautions when releasing seat belts. Any briefing should consider the prospect that the pilot may not be able to assist due to their prominent position where impact forces may be concentrated. An able-bodied passenger near an accessible exit would be the best resource for survivability in this situation.

The guidance also recommended unlatching a door prior to impact and providing passengers with a briefing, which included the brace position.[11]

Survival aspects

Passenger seating, exit location, and operation

The pilot (P) was seated in the front left seat location. The 3 passengers consisted of an adult and 2 children.[12] One child (C) was seated in the forward right seat next to the pilot and another child (C) was seated in the left-rear behind the pilot. The adult (A) passenger was seated in the rear‑right (Figure 5). Both aircraft doors were at the front row.

Figure 5: Seating positions

Figure 5: Seating positions

Source: Rockwell annotated by the ATSB

Figure 6 shows the aircraft doors, which were designed as both normal and emergency exits. Both doors had the same operation, which required 2 opening mechanisms to be manipulated, both when operating from inside or outside. One handle was located above the passenger/pilot head that needed to be rotated downwards to unlatch. The second handle was fitted to the forward lower part of the door and was a lever type arrangement, which was required to be pulled inwards to unlatch the 2 lower latches. Each door needed to be pushed outwards to open. There was no emergency jettison mechanism. 

Figure 6: Location of door interior operating handles

Figure 6: Location of door interior operating handles

Source: ATSB

CASA produced guidance for the allocation of passengers to exit row seats in multi-part advisory circular (AC) Passengers seated in emergency exit row seats for parts 121, 133 and 135 operators, however this AC was not applicable to private flights. 

In addition to passenger suitability, the AC identified risks associated with seating inappropriate persons at exits and recommended that operational procedures should be used to address this risk. 

Applicable risks included:

• exits being opened when they should not be e.g., a passenger opens the exit without assessing the outside conditions 

• operation of exits by passengers who are not aware of the instructions specific to that exit e.g. how to open, remove and discard the exit 

• passengers seated in an emergency exit row having an adverse reaction to the emergency due to inadequate briefings 

• passengers that are not suitably able-bodied, lacking the strength and ability to remove the exit, attempting to open the exit, and delaying or impeding an evacuation process. 

In addition, CASA guidance[13] identified that pilots should consider the possibility of incapacitation, and seat and brief an able-bodied person accordingly. However, passenger composition and operational considerations such as weight and balance must always be considered to determine passenger seat allocation. 

Pre-flight, exit and emergency briefings 

Civil Aviation Safety Regulations (CASR) 1998 Part 91 (General Operating and Flight Rules) manual of standards, Division 20.3 Passenger safety briefings and instructions which came into effect just prior to the accident on 2 December 2021,[14] required, among other things, that passengers be briefed on:

(f)    how and when to adopt the brace position;

(g)   where the emergency exits are, and how to use them;

(p)   the requirement that:

             (i)  passengers seated in emergency exit rows must be willing and able to operate the exit in the event of an emergency; and

            (ii)  such passengers must not have a condition that will cause them to obstruct the exit or hinder an emergency evacuation

While they had to be briefed, there was no legislative requirement to assess the suitability of a person[15] in an exit row for a private flight.

Guidance[16] on passenger safety briefings relevant for small aircraft operators included: 

  • to include the brace position in the pre-flight safety briefing
  • to advise passengers to adopt the brace position in an emergency
  • if the flight involves overwater operations, passengers are briefed on ditching procedures.
Briefings in practice

A witness who the accident pilot regularly flew with reported that the pilot would normally provide a briefing about the seatbelts and the operation of the aircraft exits. The instructor who assessed the pilot in their most recent flight review provided confirmation of consistent elements normally included in the pilot’s briefing.

The ATSB was unable to determine what information was provided to the passengers prior to flight on the day of the accident. Video footage captured during the emergency showed that the pilot did not provide an in-flight emergency briefing to passengers about the nature of the emergency or what actions to take.

Occupant injuries

A post-mortem examination of the pilot and passengers was conducted on behalf of the Queensland Coroner. The examination found all occupants had sustained injuries which may have caused some incapacitation but were insufficient to have been fatal. The reports found that the deaths were consistent with drowning. The report also detailed evidence of injuries consistent with being caused by wearing a harness or seatbelt.

Other information

Pilot medical requirements

As outlined above, of the last 3 CASA aviation medical examinations, the pilot had not declared their diabetic status or diabetes medication to their CASA designated aviation medical examiner (DAME).

The disclosure to DAMEs was required due to the nature of type 2 non-insulin dependent diabetes and its effect on aviation participants. The CASA Clinical practice guidelines for type 2 diabetes website stated their concerns:

Effect of aviation on [diabetes] condition:

• Difficulty with regular blood-sugar monitoring

• Irregular meal and sleep times

• Sedentary occupation

• Access to emergency sugar

Effect of [diabetes] condition on aviation:

• Overt incapacitation

- Cardiovascular event

- Cerebrovascular event

• Subtle incapacitation - end-organ damage

- Visual impairment (fields, low contrast sensitivity, colour)

- Impaired motor and sensory nerve function

- Impaired autonomic function (hypoglycaemia awareness). 

Pilots are permitted to hold a licence after a diabetes diagnosis. The CASA website further stated:

Type 2 diabetes is an aeromedically significant medical condition. Pilots and [air traffic] controllers who have been diagnosed with Type 2 Diabetes are required to ground themselves and notify this condition to their DAME.

In cases where the condition can be managed appropriately, and once cleared by the DAME, in accordance with the CASA guidelines, ongoing monitoring of the diabetes must be provided to CASA to prove that it is able to be managed and does not affect the pilot’s ability to fly. 

Safety analysis

Introduction

Shortly after take-off, VH-WMM likely experienced fuel starvation leading to a complete loss of engine power. During the attempted return to the airfield without power, the pilot did not maintain an adequate glide speed, and the undercarriage was extended, thereby reducing glide range, which resulted in the aircraft colliding with water before it reached the airfield and becoming inverted about 170 m from shore. 

This analysis will explore the power loss on take-off, flight planning and decision making of the pilot in command, and post impact survivability factors.

Checklist use

The passenger video identified that the pilot became distracted with a perceived engine problem during the before take-off checks and taxied back towards the groundcrew member. However, after realising that they had mis-identified the wrong engine control, the pilot then proceeded to the runway and conducted the take-off, without further completion of the required checks.

One essential aspect of the POH checklist stated that the fuel selector was to be set to BOTH. This ensures a positive supply of fuel can be delivered to the engine from both fuel tanks during take-off. There were two versions of the checklists on board the aircraft: the official aircraft POH included this item in 3 separate checklists, while the third-party checklists included it twice. While it is likely that the distraction affected the pilot’s completion of the ‘before take-off’ checklist items, the fuel selector was also not set to BOTH on the ‘interior’ or ‘before starting engine’ checks. 

Should a third-party checklist be used, it must be checked to ensure that it contains the correct information that is applicable for the aircraft being operated and that the checklist is verified against the approved POH checklists. The ATSB was advised that the pilot sometimes referred to the third-party checklists, however it is unlikely that the third-party checklists were referred to on the day of the accident as the folder containing the checklists were located in the pilot seat back pocket and not readily at hand.

The POH was carried on board the aircraft on the day of the accident, and the passenger video showed it was not referred to during the flight. 

On this basis, it is likely the pilot performed the before take-off checks from memory or used a mnemonic checklist to perform the before take-off checks which were ultimately interrupted. Before take-off, there is no time pressure (as there was inflight after the engine power loss), so there was opportunity to consult the written checklists to ensure all steps were completed. Conducting aircraft checks from items committed to memory can lead to checks being skipped or an assumption that a check has been completed when it has not. Also, when a checklist is interrupted, the habit of restarting from the beginning is a means of ensuring that all steps to be performed are done so in order and the checklist is complete.

Fuel imbalance

Analysis of CCTV imagery indicated it was likely that VH-WMM had a substantial quantity of fuel in the right wing, and that the pilot would have been aware of the imbalance after physically using a dipstick to check the aircraft fuel tanks during the pre-flight checks on the ground outside the hangar.

The fuel selector was found to be on the left tank after the accident and there was no video evidence of the pilot changing it during the flight. Therefore, the fuel selector was likely on the left tank during take-off. Due to the fuel imbalance, the left tank likely had minimal fuel to sustain engine operation during the climb out, which would result in the engine being starved of fuel, lose power, and begin to surge, and eventually stop. This is consistent with no fuel being found in the left tank after the accident. 

If the fuel selector was placed on BOTH tanks, then it is likely, even with one fuel tank having most of the fuel and the other almost empty, that fuel supply to the engine would remain unaffected. Excess fuel in the right tank may have led to the observed fuel coming from the right wing during the flight.

Therefore, with the aircraft’s remaining fuel supply most likely in the right tank, and with the fuel selector likely set to LEFT prior to take-off, the engine became starved of the available fuel supply in the aircraft’s right fuel tank, leading to the engine stopping. 

Engine power loss management

ATSB found that few, if any, initial emergency actions took place in response to the loss of engine power to rectify a possible fuel starvation as per the Rockwell 114 procedures. The aircraft had sufficient fuel for flight in the right wing, but the fuel selector was found to be selected to the now empty left tank, and the auxiliary fuel pump was off during the emergency. 

In addition, the pilot did not maintain the published glide speed of 82 kt as demonstrated by the numerous stall warnings that sounded repeatedly, indicating a speed within 3-4 kt of the straight and level flapless stall speed (63 kt). Airspeed management was made more difficult by the extension of the landing gear, which may have been an automatic reaction by the pilot in response to hearing the undercarriage warning bell sound while the pilot was managing the emergency.

Not maintaining the glide speed and the landing gear extension increased the vertical rate of descent and reduced the glide range of the aircraft. However, video evidence suggests the pilot continued with their initial plan to glide to the runway. In addition, the extended landing gear was an unfavourable configuration for the subsequent collision with water.

There was no available evidence to indicate that the pilot’s response (actions and inactions) to the emergency was affected by a medical issue, or similar factors. However, the pilot was making decisions during the emergency under a high level of stress and time pressure. A substantial amount of research has shown that people often do not make optimal decisions in such situations.

Some commonly reported effects of stress and/or time pressure include attentional narrowing, with people searching fewer information sources (Staal 2004) and focusing on cues that are perceived to be the most salient or threatening (Burian and others 2005, Wickens and Hollands 2000). Working memory and the ability to perform complex calculations is impaired (Burian and others 2005), and the ability to retrieve declarative knowledge (or facts) from long term memory is affected (Dismukes and others 2015). In addition, a person under stress and time pressure will generally consider fewer alternatives, and not be as systematic when evaluating alternatives (Dismukes and others 2015, Staal 2004).

Collision with water

It is likely that the pilot never intended to ditch the aircraft. Rather, the reduced speed of the aircraft below the glide speed, exacerbated by the undercarriage extension, led to a reduced glide range and inability to reach the runway at Redcliffe. The sounding of the ‘stall’ alert just before the collision indicates the aircraft could no longer maintain lift and the aircraft collided with water 3 seconds later. 

It is likely that under the stress of the situation, the pilot’s attention narrowed and their focus on landing back on the departure runway likely hampered their ability to consider a forced landing on water (ditching). Had the pilot recognised that the aircraft would not be able to glide to the runway, there was a brief opportunity (about 30 seconds) to attempt a controlled landing on water before the aircraft’s speed reduced to the stall speed.

If this had been the case, there were several actions the pilot would have had to remember (due to the limited time remaining) and complete to ensure a safe ditching. From the Rockwell 114 POH procedure, key actions were to ensure the undercarriage was retracted and the flaps were selected to 20° on the final approach to land on the water. 

Use of flap in the final stages of the ditching would have provided a reduced stall speed, therefore allowing the aircraft to touch down at a lower, controlled speed. Touching down on the water while not at the appropriate speed, and with the undercarriage extended, contributed to the aircraft inverting after colliding the water.

Further, although there was no reference in the POH to the pre-impact position of emergency exits (cabin doors) prior to a ditching, unlatching of cabin doors can allow quick egress from the aircraft after ditching. In this accident, given the brief opportunity available for such considerations, it was not considered feasible that all actions were possible. 

Due to the inverted orientation of the aircraft during the crash sequence and its submersion in murky water, the aircraft occupants were probably panicked, confused, and disorientated following the collision. Once the cabin filled with water, visibility would have been extremely low, which would have further reduced the likelihood of occupants being able to visually locate and operate the aircraft door handles. With the aircraft inverted, it is likely the occupants would have also been disoriented to the extent that it made opening the closed doors more difficult, reducing their ability to escape.

Pre-flight and emergency briefings 

Research has shown that more knowledgeable passengers perform better in an emergency (Meng-Yuan, 2014). It could not be determined what information was provided to the passengers prior to flight, however based on accounts from persons who had flown with the pilot previously, including their flight instructor, it is likely that any briefing given did not include any information about the brace position or what to do in the event of a ditching. This meant that the passengers were likely unaware of actions that may assist survival such as opening the aircraft door or adopting a brace position.   

Video footage recorded during the accident sequence showed that the pilot also did not provide passengers an in-flight emergency brief or instruct them on any actions they should take. This accident highlights the importance of providing instructions to passengers before a flight commences as often emergency situations are time limited and there may not be an opportunity to do so once something occurs.  

Providing information on the adoption of the brace position or how to, and when to open an emergency exit in a ditching situation will increase the likelihood of passengers taking appropriate action in an emergency. 

Passenger seating and emergency exit operation

Post-mortem examinations identified that the occupants of the aircraft were not fatally injured during the accident sequence. There was no readily available assistance nearby the accident site, and therefore the occupants would have had to extricate themselves from the aircraft.

The 2 emergency exits available to the occupants were more accessible to persons seated in the front of the aircraft. The exits required manipulation of both a handle on the door and a latch at the top. For the rear passengers, it is likely that they would have had difficulty (particularly with their seatbelt on) to reach the latch at the top of the door if required to operate the exit. The rear seat occupants would have also been restricted in accessing the doors and exiting the aircraft due to the presence of the front seat occupants. 

After the accident, police divers were unable to open the pilot’s left door, and only opened the other (right) door with difficulty. For the injured pilot and right front seat occupant of VH-WMM, who was a child, it is highly unlikely they would have had the post-accident capability to open the doors. The right door was observed unlocked and ajar by police divers following the collision, suggesting the possibility that an attempt had been made to open the door.

Guidance suggests that pilots should determine the most appropriate person to assist in an emergency and to brief that person accordingly, therefore, in this case, seating a child who has less physical and mental capability rather than an adult next to an exit, meant that the most suitable person (the adult) was not in the best position to assist themselves and others in the event of an emergency. 

Diabetes

The pilot had been diagnosed with type 2 non-insulin dependent diabetes which was managed with prescription medication by the pilot’s GP. A review of the pilot’s CASA aviation medical information indicated that this significant medical condition was disclosed in the pilot medical history as ‘unsure’ to the CASA DAME in the previous 3 aviation medical renewals, all of which were changed to ‘no' at the DAME examination prior to submission to CASA.

It was important to note that having type 2 non-insulin dependent diabetes did not mean that this condition would be an immediate disqualification of the pilot’s licence. However, due to the aeromedically significant nature of diabetes, it was important for this to be fully disclosed with the pilot’s DAME and to CASA. Without this interaction, it was a missed opportunity for the pilot’s condition to be monitored at a safe level required to exercise the privileges of a pilot’s licence. 

Findings

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

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

From the evidence available, the following findings are made with respect to the fuel starvation and collision with terrain involving a Rockwell International 114, VH-WMM, 1 km north of Redcliffe aircraft landing area, Queensland, on 19 December 2021. 

Contributing factors

  • An unsafe condition was created by not referring to the approved checklists in the pilot operating handbook. Checklists located in the pilot operating handbook would have prompted the pilot on 3 occasions to set the fuel selector to BOTH prior to take-off.
  • A perceived engine problem distracted the pilot during the conduct of pre-take-off checks. After rectifying the issue, they did not complete the remaining pre-take-off checks (including fuel tank selection) before departure.
  • A fuel imbalance and likely an incorrect fuel tank selection prior to take-off, led to fuel starvation and engine stoppage soon after take-off.
  • The pilot, likely experiencing the effects of stress and time pressure following the engine power reduction and then stoppage, did not conduct initial emergency actions and attempted to return to the runway for landing but did not maintain glide speed, and the aircraft impacted shallow water prior to reaching the airfield.
  • During the return to the airfield, the pilot extended the undercarriage, contributing to the aircraft inverting when it collided with water. This likely resulted in occupant disorientation, difficulty in operating the exits, and reduced their ability to escape.

Other factors that increased risk

  • It is very likely that the passengers did not receive pre-flight information about the brace position or what to do in the event of a ditching. In the limited time available inflight after the power loss, the pilot also did not provide an emergency briefing or any instructions to passengers prior to impact with the water.
  • While the pilot was primarily responsible for the operation of the aircraft exits in an emergency, seating a child, who may require assistance, adjacent to an exit instead of an adult meant that a less suitable passenger was available to operate the exit if required.
  • The pilot had a diagnosed type 2 diabetic condition and did not directly declare this to the DAME during multiple medical renewals. 

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Civil Aviation Safety Authority
  • Queensland Police Service
  • Australian Volunteer Coast Guard
  • accident witnesses
  • CCTV footage
  • passenger mobile phone recordings
  • the pilot’s general practitioner
  • the pilot’s designated aviation medical examiner
  • the flight review instructor
  • maintenance organisation

References

Australian Government 2021, AC 91-22 Aircraft checklists v2.0, Civil Aviation Safety Authority, Canberra, ACT, viewed 18 December 2023, < AC 91-22 v2.0 - Aircraft checklists (casa.gov.au)>

Australian Government 2022, Type 2 Diabetes - Non-insulin dependent - Low risk of hypoglycaemia, Civil Aviation Safety Authority, Canberra, ACT, viewed 7 February 2022, < Type 2 Diabetes - Non-insulin dependent - Low risk of hypoglycaemia | Civil Aviation Safety Authority (casa.gov.au)>

Australian Government 2023, Avoidable Accidents No. 3 - Managing partial power loss after take-off in single-engine aircraft, Australian Transport Safety Bureau, Canberra, ACT, viewed 8 February 2022, < Avoidable Accidents No. 3 - Managing partial power loss after take-off in single-engine aircraft | ATSB

Australian Government 2023, AC 91-09 Ditching v1.0, Civil Aviation Safety Authority, Canberra, ACT, viewed 25 January 2022, < AC 91-09 v1.0 - Ditching (casa.gov.au) >

Australian Government 2023, Part 91 (General Operating and Flight Rules) Manual of Standards 2020, Civil Aviation Safety Authority, Canberra, ACT, viewed 25 January 2022, Part 91 (General Operating and Flight Rules) Manual of Standards 2020 (legislation.gov.au)

Australian Government 2023, Passenger safety information, Civil Aviation Safety Authority, Canberra, ACT, viewed 25 January 2022, < Multi-Part AC 91-19, AC 121-04, AC 133-10, AC 135-12 and 138-10 - Version 1.1 (casa.gov.au)>

Australian Government 2023, Passenger safety information, Federal Register of Legislation, Canberra, ACT, viewed 24 January 2022, <Civil Aviation Order 20.16.3 - Air service operations - Carriage of persons (02/12/2004) (legislation.gov.au)>

Burian BK, Barshi I & Dismukes K 2005, The challenge of aviation emergency and abnormal situations, National Aeronautics and Space Administration Technical Memorandum NASA/TM-2005-213462. 

Casner SM, Geven RW & Williams RT 2013, ‘The effectiveness of airline pilot training for abnormal events’, Human Factors: The Journal of the Human Factors and Ergonomics Society, vol. 55, pp.477-485.

Chaiken, S. R., Kyllonen, P. C., & Tirre, W. C. (2000). Organization and components of psychomotor ability. Cognitive Psychology, 40(3), 198-226.

Dismukes RK, Goldsmith TE & Kochan JA 2015, Effects of acute stress on aircrew performance: Literature review and analysis of operational aspects, National Aeronautics and Space Administration Technical Memorandum NASA/TM-2015-218930.

United States Government 2017, Safety Concerns with Using Commercial Off-the-Shelf (COTS) or Personally Developed Checklists, Federal Aviation Administration, Washington, DC, viewed 10 January 2024, < SAFO 17006: Safety Concerns with Using Commercial Off-the-Shelf (COTS) or Personally Developed Checklists (faa.gov)>

Kahneman D 2011, Thinking, fast and slow, Allen Lane London.

Klein G 1998, Sources of power: How people make decisions, Massachusetts Institute of Technology.

Landman A, Groen EL, van Passen VV, Bronkhorst AW & Mulder M 2017, ‘The influence of surprise on upset recovery performance in airline pilots’, The International Journal of Aviation Psychology, vol. 27, pp.2–14.

Lycoming Engines 2021. Service Instruction No 1009BE Time Between Overhaul (TBO) Schedules, viewed 7 December 2021, Lycoming Engines <Service Instruction No. 1009 BE | Lycoming>. 

Meng-Yuan, L. 2014, An evaluation of an airline safety education program for elementary school children. Evaluation and Program Planning, Science Direct, viewed 21 January 2023, < An evaluation of an airline cabin safety education program for elementary school children - ScienceDirect>

Precision Airmotive Corporation 20200, Training Manual RSA Fuel Injection System, viewed 6 June 2023, <15-812_b.pdf (precisionairmotive.com)>

Precision Airmotive Corporation 2020, RSA Fuel Injection system schematic wallchart, viewed 24 March 2022, < precisionairmotive.com/wp-content/uploads/2019/06/WALLCHART_rsa.pdf>

Staal MA 2004, Stress, cognition, and human performance: A literature review and conceptual framework, National Aeronautics and Space Administration Technical Memorandum NASA/TM-2004-212824.

Wickens CD & Hollands JG 2000, Engineering psychology and human performance, 3rd edition, Prentice-Hall International Upper Saddle River, NJ.

Wikipedia 2023, Rockwell Commander 112/114 family, viewed 14 January 2022, Wikipedia < Rockwell Commander 112 - Wikipedia>

Submissions

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

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

  • the Civil Aviation Safety Authority
  • the National Transportation Safety Board
  • the pilot’s last flight review flight instructor
  • the pilot’s ground crew member
  • medical subject matter experts.

Any submissions from those parties was reviewed and, where considered appropriate, the text of the draft report was amended accordingly.

Appendix

Sequence of events

The sequence of events below lists the key activities and audio from the passenger recorded video. This recording was started at 0902 and 25 seconds. The time listed in the table below is added to this time stamp. The video began during the taxi back toward the ground crew after the perceived engine problem.

Table 1: Sequence of events from accident flight video 

Time (m:ss) from recording startTime (m:ss) after take-off commencementActivityComment
1:50 Stop at holding pointDiscussing location of other traffic
2:18 WMM enters and backtracks runway 07 
3:00 – 3:21 Take-off  
3:300:09Undercarriage retractsMotor heard during gear retraction
3:560:35Left turnAircraft over water
4:050:44Engine RPM decreasePilot reduces power after take-off
4:090:48Flaps seen retractingCaptured on video
4:150:54Left turnWMM now about 90° to runway heading
4:321:11Engine RPM fluctuatingDistinct rise and fall of engine RPM
4:351:14Large drop in engine RPM 
4:381:17Passenger asks pilot about fuel coming out of right-wing fuel cap 
4:38 & 4:421:17 & 1:21Two left turnsWMM now on downwind leg to airfield
4:48 & 4:51 1:27 & 1:30Stall warning sounds 
4:521:31Engine stopsDistinct ‘whomp’ sound from engine, usually heard when a piston engine stops
4:561:35Undercarriage warning bell followed by stall warning‘Click’ sound, followed by a wind noise. Gear extension most likely set here.
5:021:41Pilot speakingRadio call for return to runway
5:18, 5:20 & 5:241:57, 1:59, & 2:03Stall warning sounds 
5:252:04WMM turns directly toward runway 
5:26 to 5:402:05 to 2:19Stall warning multiple sounds 
5:402:19Right wing drops 
5:422:21

Right wing drops

Electronic voice calls “stall”

Aircraft stall warning remains on

Electronic voice is an alert from the Voice Alert System – heard only once
5:452:24Aircraft impacts water 

Source: ATSB based on passenger mobile phone recording

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2024

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

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

[2]     Runway number: the number represents the magnetic heading of the runway. In this case, 07 equates to 70°.

[3]     Radio communications on the common traffic advisory frequency at Redcliffe Aerodrome were not recorded.

[4]     Psychomotor skills refer to the co-ordination of perception and action and require either complex perceptual discrimination or a complex motoric response (Chaiken and others, 2000).

[5]     Records showed that the pilot had been prescribed 4 antihypertensive medications and had regularly been dispensed these medications in the months before the accident. Only 1 of these medications was detected in the toxicology analysis, however the type of analysis conducted would not detect the other 3 medications. 

[6]     Wet wing – the wing structure forms an integral fuel tank instead of a bladder or metal fuel tank. 

[7]     Gascolator – a fuel filter fitted at the lowest point of the fuel system.

[8]     On-condition: Performed only when the condition of an item demands, instead of at scheduled intervals.

[9]     Hydraulic: in this context is the deformation of the aircraft skin around its structural members (such as ribs). This deformation occurs by the action of water on the aircraft skin during the accident sequence.

[10]    While Rockwell uses the term pilot’s operating handbook, other manufacturers, and generic terms may include aircraft flight manual, flight manual, owner’s handbook, operating manual, or owner’s manual.

[11]    Brace position – adopted for ditching or crash-landing; shoes removed, bent forward with arms protecting head.

[12]    A child as defined by CASA is a person who has turned 2 but has not turned 13.

[13]    Civil Aviation Advisory Publication (CAAP) 253-1(1) Ditching (2004) now AC Ditching (2021).

[14]    The previous CAO 20.16.3 Air service operations - carriage of persons required that passengers be briefed to determine if they were willing and able if seated in emergency exits and CAO 20.11 Emergency and life-saving equipment and passenger control in emergencies required briefing on the location of the emergency exits, but not how to use them and did not include the brace position.

[15]    A suitable person has been defined in the CASA dictionary as someone that is reasonably fit, strong, and able to assist with the rapid evacuation of the aircraft in an emergency; and would not, because of a condition or disability, including an inability to understand oral instructions, hinder other passengers during an evacuation of the aircraft in an emergency or the aircraft’s crew in carrying out their duties in an emergency.

[16]    CASA guidance publications Cabin safety bulletin 12 - General aviation passenger briefings (2018), Civil Aviation Advisory Publication (CAAP) 253-1(1) Ditching (2004) now AC Ditching (2021), and Multi-part AC Passenger Safety Information (2021).

Occurrence summary

Investigation number AO-2021-053
Occurrence date 19/12/2021
Location 1 km north of Redcliffe Aerodrome
State Queensland
Report release date 14/03/2024
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Rockwell International
Model 114
Registration VH-WMM
Serial number 14229
Aircraft operator Private
Sector Piston
Operation type Private
Departure point Redcliffe Aerodrome
Destination Redcliffe Aerodrome
Damage Destroyed

Collision with terrain involving Kavanagh E-240 Balloon, VH-LUD, near Yamanto, Queensland, on 8 October 2021

Final report

Executive summary

What happened

On 8 October 2021, a Kavanagh Balloons E-240 balloon, registered VH-LUD and operated by Floating Images Aust. Pty Ltd was conducting a morning scenic flight about 45 km south‑west of Brisbane, Queensland. On board was a pilot and 9 passengers. About 55 minutes into the flight, the pilot commenced a descent to locate a suitable landing area. During the descent, the balloon entered an area of localised fog where visibility reduced to 10 m.

The pilot continued the descent into the fog until a tree was observed in the path of the balloon. The pilot attempted to avoid the tree by initiating a climb, but the balloon collided with, and came to rest on the side of the tree, damaging the lower part of the balloon envelope. The pilot subsequently climbed the balloon off the tree and above the fog. The flight continued to an uneventful landing in a nearby paddock that was clear of fog. There were no injuries.

What the ATSB found

The ATSB found that, contrary to the visual flight rules visibility requirement, the pilot entered an area of reduced visibility in which the visibility was 10 m. This did not allow sufficient time to complete an avoidance manoeuvre when an obstacle was observed, as a result the balloon collided with a tree and the balloon envelope was damaged.

Safety message

In some circumstances, balloons are permitted to fly in significantly lower visibility than other types of aircraft. While this is mainly due to their inherently low flight speed, it also considerably reduces the available time to see obstacles. Additionally, as balloons can only manoeuvre vertically and significant time may be required to transition from a descent to a climb, they have limited capability to avoid obstacles.

Therefore, to reduce the collision risk if a balloon enters an area of visibility less than that permitted by the visual flight rules, pilots should ensure that an immediate recovery is commenced.

The investigation

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

The occurrence

On 8 October 2021, the pilot of a Kavanagh Balloons E-240 balloon, registered VH-LUD, was preparing for a morning scenic charter flight for 9 passengers from a location 45 km south‑west of Brisbane, Queensland. The pilot reported releasing a small helium balloon from the Ipswich Visitor Information Centre, located about 6 km to the east of RAAF Base Amberley (Figure 1), at 0425 Eastern Standard Time,[1] to observe wind speed and direction. The pilot also checked the wind observations recorded at the nearby RAAF Base, which were variable[2] at 3 knots.

Following an assessment, via the observation balloon, that the wind was from the west‑north‑west, the pilot planned the flight to commence at Rosewood Golf Club with an intent to track south-east, to the south of RAAF Base Amberley, and continue towards Yamanto (Figure 1). The pilot commented that there was no fog present at the departure time.

The 9 passengers arrived at the Ipswich Visitor Information Centre at about 0425 and they were taken to Rosewood Golf Club. The passengers were briefed on the 3 stages of balloon flying: inflation, flight, and landing. The pilot then inflated the balloon, and the passengers were boarded.

Although the pilot planned the flight in non-controlled Class G airspace[3] around RAAF Base Amberley, they made a telephone call to RAAF Amberley air traffic control and left a message on their answering machine with details of the balloon flight. The pilot reported that this was in case RAAF Amberley airspace became active during the period of the balloon flight and the airspace reverted to military Class C airspace[4] (see the section titled Airspace).

The balloon took off at around 0520 and tracked towards the east-south-east as expected from the wind observations. The pilot reported clear skies with some localised fog present to the south‑east of the RAAF base. The pilot estimated the fog to be from the surface to a height of 500 ft.

Figure 1: Flight path of VH-LUD

Flight path of balloon

Source: Google Earth, annotated by the ATSB

After about 55 minutes of flight time the pilot commenced a descent to visually identify and select a suitable landing area. As the balloon descended below 1,000 ft the wind backed[5] to a south‑westerly. As a consequence of that wind change, the balloon began tracking north-east towards the previously‑identified fog bank (Figure 2).

The pilot approached the fog expecting to be able to maintain visual requirements for landing. However, upon entering the fog, the pilot recalled observing that it was significantly thicker than they expected or had flown in before with visibility of about 10 m. The pilot continued to descend at approximately 200 feet per minute into the fog until they sighted a tree directly ahead of them. In response, the pilot immediately commenced burning on all 3 burners to arrest the descent and transition to a climb, but the balloon collided with the tree at a speed of about 4 knots. The balloon came to rest on the side of the tree at a height of about 60 ft above the ground.

Figure 2: Descent of VH-LUD to Yamanto

Flightpath of balloon

Source: Google Earth, annotated by the ATSB

The pilot continued operating the burners and the balloon commenced a climb away from the tree. The pilot climbed the balloon until they were out of the fog and conducted an uneventful landing in a nearby paddock, clear of the fog. There were no injuries to the pilot or passengers, however multiple sections of the lower portion of the balloon envelope required repair or replacement due to damage by tree branches. The balloon returned to service 7 days later.

Context

Pilot experience

The pilot held a Civil Aviation Safety Authority (CASA) Commercial Pilot Licence (Balloon) that was issued in January 1995. At the time of the occurrence the pilot had accrued a total flying time of 2,904 hours with approximately 2,000 hours on type. The pilot held a current CASA class 2 aviation medical certificate.

The pilot also held a CASA Maintenance Authority to conduct maintenance on the Kavanagh balloon.

Balloon information

VH-LUD was a Kavanagh Balloons E-240 manned free balloon manufactured as serial number E24-527 in 2016 by Kavanagh Balloons Australia Pty Ltd. The E‑240 balloon has an envelope capacity of 240,000 cubic feet and a maximum take-off weight of 2,000 kg. It is powered by three burners connected to two independent fuel systems. At the time of the occurrence VH‑LUD had accumulated a total time of 492.8 hours in service.

Flight conditions

The pilot obtained weather observations, noting isolated fog was forecast and that the wind was variable at 3 knots. The pilot also commented that if there was visible fog at their nearby residence prior to departure, as a general practice they would reschedule the flight.

An Amberley terminal area forecast (TAF) was issued at 0209 EST for the 24 hours from 0300 with an amendment issued at 0318 (Figure 3). A further TAF was issued at 0515, about the same time the balloon took off. All 3 forecasts predicted variable winds at 3 knots and a 30% probability of fog, in which visibility would reduce to 500 m.

Figure 3: RAAF Amberley terminal area forecast

NOTAM

Source: Airservices Australia, annotated by the ATSB

Airspace requirements

RAAF Base Amberley is surrounded by Class G non-controlled airspace, which allows aircraft to operate without air traffic control (ATC) permission. This airspace becomes military Class C when the air traffic control tower is active. Permission is required from Amberley ATC to operate in Class C airspace. At the time of the flight, the air traffic control tower was not active, therefore, Class G airspace procedures applied.

The pilot reported telephoning RAAF Base Amberley air traffic control and leaving a message on their answering machine with the balloon flight details. The pilot had conducted this process for a number of years. The pilot also reported monitoring the Amberley common traffic advisory frequency for traffic during the flight.

In Class G airspace, the required visibility for a balloon operating below 1,500 ft above ground level and clear of cloud, is 5,000 m. However, a balloon operating below 500 ft above ground level and beyond 10 NM of an aerodrome with an approved instrument approach procedure only requires 100 m visibility.

On this occasion, as this flight was conducted within 10 NM of RAAF Base Amberley, an aerodrome having approved instrument approach procedures, the balloon was required to maintain at least 5,000 m visibility and remain clear of cloud irrespective of its operating height.

Balloon performance

The pilot reported that at the time the tree was observed the balloon was descending at a rate of about 200 feet per minute and was flying at a velocity of about 4 knots. As soon as the pilot saw the tree, they commenced burning on all three burners.

The pilot stated the balloon took 20-30 seconds to arrest the descent and commence climbing. The pilot reported the balloon ‘settling’ on the side of the tree in a slow speed collision.

Damage to balloon

The balloon envelope consisted of a total of 460 sewn panels in a combination of four differing sizes. A total of 19 panels were damaged during the occurrence. These panels were either repaired or replaced by the operator in accordance with the Kavanagh Balloons maintenance manual.

Safety analysis

The RAAF Base Amberley TAF listed a 30% probability that fog would be present in the area, in which visibility would be 500 m. The pilot reported that during flight preparation there was no fog present. During the flight, fog was observed in a localised area to the south-east of RAAF Base Amberley.

The flight was conducted in Class G airspace within 10 NM of the RAAF Base. Due to the RAAF Base having an approved instrument approach procedure, the balloon operating under the visual flight rules was required to remain clear of cloud and maintain a minimum visibility of 5,000 m.

The pilot commenced a descent with the intention of locating a suitable landing area. During this descent, the wind backed, and the balloon began tracking towards the area of localised fog. Instead of remaining above the localised fog and descending in the clear air beyond, the pilot continued the descent and entered the fog believing that adequate visibility would exist for the landing. The visibility subsequently reduced to 10 m.

The pilot observed a tree, and in an attempt to prevent a collision, lit the burners to transition to a climb. However, due to the 20-30 seconds required before the descent could be arrested and a climb commence, there was insufficient time for the tree to be avoided due to the limited visibility. Given the climb performance of the balloon, even if the circumstances around the airspace allowed for the flight to be conducted in visibility conditions down to 100 m, the collision would still have occurred.

After the collision, the pilot climbed the balloon off the tree and up into clear air. The balloon was then flown to the edge of the localised fog and an uneventful landing was carried out.

Findings

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

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

From the evidence available, the following finding is made with respect to the collision with terrain involving Kavanagh E-240 Balloon, VH-LUD, at Yamanto, Queensland.

Contributing factors

  • Contrary to the visibility requirement for visual flight rules flight, the pilot entered an area of fog that did not permit sufficient time to see and avoid obstacles. As a result, the balloon collided with a tree, damaging the balloon's envelope.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • the pilot of VH-LUD
  • Civil Aviation Safety Authority
  • RAAF Base Amberley air traffic control.

Submissions

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

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

  • the pilot of VH-LUD
  • Civil Aviation Safety Authority.

Submissions were received from:

  • the pilot of VH-LUD
  • Civil Aviation Safety Authority

The submissions from those parties were reviewed however, they did not result in any amendment to the text of the draft report.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

[1]     Eastern Standard Time (EST): Coordinated Universal Time (UTC) + 10 hours

[2]     Variable: used when the forecasting of mean wind direction is not possible. Usually due to low wind velocity.

[3]     Class G: This airspace is not subject to air traffic control (ATC). Both instrument flight rules and visual flight rules aircraft are permitted and neither require ATC clearance.

[4]     Class C airspace: Controlled airspace surrounding major airports. Both instrument flight rules and visual flight rules aircraft are permitted, but pilots must obtain a clearance to operate and maintain continuous radio contact with air traffic control.

[5] Backed: A counter‑clockwise shift in the wind direction.

Occurrence summary

Investigation number AO-2021-042
Occurrence date 08/10/2021
Location Near Yamanto
State Queensland
Report release date 01/11/2022
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Serious Incident
Highest injury level None

Aircraft details

Manufacturer Kavanagh Balloons
Model E-240
Registration VH-LUD
Serial number E240-527
Aircraft operator FLOATING IMAGES AUST. PTY LTD
Sector Balloon
Operation type Part 131 Balloons and hot air airships
Departure point Rosewood Qld
Destination Yamanto Qld
Damage Minor

Collision with terrain involving Cessna A150M, VH-CYO, 5 km west-south-west of Peachester, Queensland, on 23 June 2021

Preliminary report

Preliminary report released 21 September 2021

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

Two private pilots contracted an aerobatics instructor to provide aerobatic flight training. On the morning of 23 June 2021, the three pilots gathered at the Sunshine Coast Airport, Queensland, for a pre-flight briefing. The briefing contained theoretical information about spin[1] training and recovery techniques, which were intended for the practical component of the aerobatic flights that day. The pilots had hired a Cessna A150M Aerobat, registered VH-CYO, from the Sunshine Coast Aero Club for the practical flight training.

At 1103 Eastern Standard Time,[2] VH-CYO took off from the Sunshine Coast Airport, with the instructor and one of the student aerobatic pilots on board. The flight was being conducted under visual flight rules (VFR), and visual meteorological conditions existed during the flight.

The aircraft departed to the south-west and climbed to about 6,000 ft above mean sea level (AMSL) (Figure 1). It arrived at the area intended to conduct aerobatics about 20 minutes after departure.

Figure 1: VH-CYO flight track radar data showing take-off point and accident site

VH-CYO flight track radar data showing take-off point and accident site

Source: Google Earth, annotated by the ATSB

Figure 2 shows recorded radar data for the last 3 minutes of the flight. It indicates that, within the last 90 seconds, the aircraft turned left, decelerated while maintaining altitude, and then descended rapidly. Shortly after, at about 1122, the aircraft impacted terrain. The aircraft was destroyed and the two occupants were fatally injured.

Figure 2: VH-CYO last 3 minutes of recorded flight data viewed from the left and above

VH-CYO last 3 minutes of recorded flight data viewed from the left and above

Radar positions (depicted by green pins) were recorded every 5 seconds. The last two points depicted without pins were predictive in nature and were not considered to be accurate. Source: Google Earth, annotated by the ATSB

The aircraft was reported missing by a member of the aero club at about 1515 EST. A subsequent search found the wreckage in bushland near Peachester several hours later.

Context

Aircraft information

The Cessna 150 is a high wing, two-seat, single piston engine aeroplane designed for flight training. The Cessna A150M Aerobat model was designed to conduct aerobatic training.

VH-CYO was manufactured in 1976 and first registered in Australia in 1995. It had been owned by the Sunshine Coast Aero Club since March 2021.  

Recorded information

The aircraft flight path was derived from primary[3] and secondary[4] surveillance radar data recorded by Airservices Australia. The data included the aircraft’s position with a time stamp and altitude at 5-second intervals. A groundspeed can be derived by calculating the distance travelled over a known time period.

Each of the green pins in Figure 2 depicts a recorded radar position. The recording stopped at about 1,200 ft AMSL, most likely due to the aircraft descending below radar coverage.

Site and wreckage examination

The accident site was located in a dense stand of trees, about 400 ft AMSL. The trees stood about 15–20 m high and straddled a creek line in a band about 50 m wide, with open areas of farmland on either side (Figure 3).

Figure 3: Area of accident site

Area of accident site

Source: Google Earth, annotated by the ATSB

The wreckage trail extended about 50 m from the initial tree impact point, until the final piece of wreckage, oriented in an east-west direction. There were several notable tree impact points, including trees that had been broken in half or completely felled by the impact forces.

Calculations of the tree impact damage heights indicated the final flight path angle was a descent of about 13°. The main wreckage came to rest at the base of a tree that was struck at a height of about 10 m.  

The aircraft structure was significantly disrupted as a result of impacting several trees (Figure 4).

Figure 4: Aircraft main wreckage at the base of a large tree that was struck

Aircraft main wreckage at the base of a large tree that was struck

Source: ATSB

The ATSB conducted an examination of the aircraft wreckage. This examination identified that:

  • the disruption to the aircraft and foliage, coupled with the length of the wreckage trail, indicated that the aircraft had significant forward speed at impact
  • the flaps were in the retracted position
  • the aircraft had no evident pre-impact defects with the flight controls or aircraft structure
  • the aircraft was intact prior to impact with terrain
  • the engine had no obvious defects upon external examination
  • the throttle setting was captured at an idle position during the accident sequence
  • the propeller rotational damage signatures were minimal, indicating a low power setting.

Ongoing investigation

The investigation is continuing and will include:

  • interviews with parties involved with the operation of the aircraft
  • further analysis of the radar data
  • examination of the pilots’ qualifications, experience, and medical/recent history
  • assessment of the aircraft’s flight performance characteristics
  • assessment of spin training requirements and practices
  • examination of aircraft maintenance and operational records
  • processes surrounding the use of flight notes or a nominated SARTIME to highlight expected arrival/return times so that aircraft are identified as overdue in a timely manner.

Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.

A final report will be released at the conclusion of the investigation.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2021

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. A spin is a sustained spiral descent of a fixed-wing aircraft, with the wing’s angle of attack beyond the stall angle.
  2. Eastern Standard Time (EST) was Coordinated Universal Time (UTC) + 10 hours.
  3. Primary radar returns are produced by radar transmissions that are passively reflected from an aircraft and received by the radar antenna. The received signal is relatively weak and provides only position information, not the aircraft’s altitude.
  4. Secondary radar returns are dependent on a transponder in the aircraft replying to an interrogation from a ground station. An aircraft with its transponder operating is more easily and reliably detected by radar and, depending on the mode selected by the pilot, the aircraft’s pressure altitude is also displayed to the air traffic controller.

Final report

Executive summary

What happened

On 23 June 2021, a Cessna A150M Aerobat, registered VH-CYO, departed from the Sunshine Coast Airport, Queensland, with an instructor and student pilot on board. The purpose of the aerobatic training flight was to introduce and practice spin entry and recovery techniques.

The aircraft climbed to about 6,000 ft above mean sea level and arrived at the area intended to conduct aerobatics about 20 minutes after departure. Radar data showed that the aircraft then entered into a left spin that continued for about 55 seconds until the aircraft impacted terrain. The instructor and student were fatally injured, and the aircraft was destroyed.

What the ATSB found

Forward movement of the aircraft and the low angle of entry indicated that the aircraft was most likely in the process of recovering from the spin when it impacted with trees.

Examination of the aircraft did not identify any mechanical defect. However, the aircraft was significantly disrupted and therefore functionality of the flight controls was unable to be fully assessed. Pre- and post-accident medical information did not identify any underlying conditions in either pilot that may have contributed to the accident.

The aerobatics instructor was experienced in conducting spins, primarily in the Pitts Special aircraft type. However, it was likely that they had no experience in spinning a Cessna A150 Aerobat or any similar variant. The instructor’s theoretical spin training provided to the aerobatic student pilot (and another student at the same time) did not include instruction on the recovery technique as prescribed in the Aerobat pilot’s operating handbook (POH). Further, the ATSB established that it was likely the instructor intended to practice 2 spin recovery techniques. One of those techniques, broadly known as the Mueller/Beggs recovery method, has been shown to not recover a Cessna A150 Aerobat established in a spin to the left. The other method known as PARE, aligned closely with the aircraft’s POH and, if utilised, it would recover the aircraft from a spin.

The ATSB was unable to ascertain which of the recovery technique(s) was being utilised at the various stages of the spin recovery preceding the accident. For this reason, the ATSB was unable conclude if the use of an inappropriate recovery technique contributed to the accident.

What has been done as a result

The ATSB has issued a Safety Advisory Notice SAN (AO-2021-025-SAN-001) for aerobatic pilots and aerobatic instructors who conduct spins utilising the Mueller/Beggs spin recovery method, to raise awareness of its limitations.

Safety message

Although the reason for the accident could not be fully established, the investigation identified that one of the spin recovery methods that was to be practiced on the day of the accident would most likely not recover the Cessna A150M Aerobat from a spin.

This investigation presents a timely reminder that pilots should review the pilot’s operating handbook of the aircraft type that they intend to operate. Prior to intentionally spinning an aircraft, pilots should obtain instruction and/or advice in spins and recovery techniques from an instructor who is fully qualified and current in spinning that model. Further, aerobatic pilots and instructors should be aware and also teach the Meuller/Beggs method of spin recovery advantages, but most importantly its limitations in that it will not recover all aircraft types from a spin.

The occurrence

Aerobatics instructional flights

Two private pilots (students), who were members of the Sunshine Coast Aero Club, contracted an aerobatics instructor to provide aerobatic flight training in the aero club’s Cessna A150M Aerobat (Aerobat), registered VH-CYO. That training included theoretical and practical training aspects.

As the instructor did not work at the aero club, the aero club’s chief flying instructor (CFI) conducted a check flight with the instructor in the Aerobat to assess the instructor’s ability. The CFI was not rated in aerobatics, and the check flight was limited to an assessment of the instructor’s general handling and area knowledge. The CFI stated that the instructor performed the flight to a high standard and concluded that the instructor had the requisite skill and knowledge to conduct the flight training in the aero club’s Aerobat.

The students hired the aero club’s Aerobat for the practical flight training. The training was split into 2 days, commencing on the 16 June 2021. On that day 4 flights were undertaken, with 2 one-hour flights per student. The students undertook theoretical and practical instruction on:

  • stall recovery techniques
  • stall turns
  • loops
  • barrel rolls
  • aileron rolls.

It was reported that, during the practical flight phase on that day, the instructor demonstrated each of the manoeuvres before handing control to the student.

Pre-flight briefing on the day of the accident

On the morning of 23 June 2021, the 2 students and the instructor continued the aerobatics training from Sunshine Coast Airport, Queensland, commencing with pre-flight theoretical instruction on spin training. The briefing contained information about:

  • what is a spin[1]
  • inverted and upright spins
  • what is a spiral dive[2]
  • difference between a spin and a spiral dive
  • the Mueller/Beggs emergency spin recovery method
  • the PARE method for spin recovery.

One of the students indicated that, during the pre-flight briefing, they were not instructed on what recovery method was recommended in the Aerobat Pilot’s Operating Handbook (POH), or that it closely aligned with the PARE method. Further, they were instructed on the advantages of the Mueller/Beggs method, but not on its limitations; namely, if the Mueller/Beggs method was utilised on an Aerobat, the aircraft would not recover from a spin to the left (see Aerodynamic spins).

Both students were instructed to write down the 2 spin recovery methods on a piece of paper for reference in flight when the practical component of the spin recovery was to be undertaken. One of the students indicated that they believed they were going to utilise both methods of spin recovery during their flight instruction. The first method written down on both students’ spin recovery notes was the Mueller/Beggs method.

Accident flight

At 1103 Eastern Standard Time,[3] VH-CYO took off from the Sunshine Coast Airport, with the instructor and one of the aerobatic student pilots on board. The flight was being conducted under visual flight rules (VFR), and visual meteorological conditions existed during the flight. The accident flight was the first of 4 one-hour flights intended for that day (2 per student).

The aircraft departed to the south-west and climbed to about 6,000 ft above mean sea level (AMSL). Radar data showed that the aircraft arrived at the area intended to conduct aerobatics about 20 minutes after departure (Figure 1).

Figure 1: VH-CYO flight track radar data showing take-off point and accident site

figure 1
figure 1

Source: Google Earth, annotated by the ATSB

Figure 2 shows recorded radar data for the last 3 minutes of the flight. It indicated that, within the last 90 seconds, the aircraft conducted a 180° left turn, decelerated while maintaining altitude, and then descended rapidly, with the point of decent beginning at 5,800 ft above ground level (AGL). That manoeuvring was indicative of the planned entry into a spin.

At about 1122, 55 seconds after the initiation of the spin, the aircraft impacted terrain. The aircraft was destroyed, and the 2 occupants were fatally injured.

Figure 2: VH-CYO last 3 minutes of recorded flight data viewed from the left and above

ao-2021-025-figure-2.png

Source: Google Earth, annotated by the ATSB

Figure 2 shows recorded radar data for the last 3 minutes of the flight. It indicated that, within the last 90 seconds, the aircraft conducted a 180° left turn, decelerated while maintaining altitude, and then descended rapidly, with the point of decent beginning at 5,800 ft above ground level (AGL). That manoeuvring was indicative of the planned entry into a spin.

At about 1122, 55 seconds after the initiation of the spin, the aircraft impacted terrain. The aircraft was destroyed, and the 2 occupants were fatally injured.

  1. Spin: a sustained spiral descent of a fixed-wing aircraft, with the wing’s angle of attack beyond the stall angle.
  2. Spiral dive: a steep descending turn with the aircraft in an excessively nose-down attitude and with the airspeed increasing rapidly.
  3. Eastern Standard Time (EST) was Coordinated Universal Time (UTC) + 10 hours.

Context

Pilot information

Instructor

Experience and qualifications

The instructor held a valid commercial pilot licence (aeroplane) that was issued on 10 August 2017. The licence included the following ratings and endorsements:

  • single engine aeroplane class rating
  • manual propeller pitch control, design feature endorsement
  • aeroplane formation, spinning and aerobatics (low level) flight activity endorsement
  • flight instructor rating with grade 2, spinning, formation (aeroplane) and aerobatics training endorsements
  • aeroplane formation, spinning and aerobatics flight activity endorsements.

The instructor had their own aviation company that predominantly conducted aerobatic joy flights and instructional flights in the company’s 2 Pitts Special aircraft. The ATSB had access to the pilot’s logbook information up to 16 February 2020, at which point the instructor had accumulated 1,112.3 flight hours. The information in those logbooks indicated that the instructor had about 100 hours of flight experience in a Cessna 152 (a similar, non-aerobatic variant of the Aerobat), but none of that recorded experience was aerobatic in nature.

In the week prior to the accident, the instructor provided information to the Sunshine Coast Aero Club that they had about 100 hours experience in the Cessna 152. However, there was no mention of experience in the Cessna A150 Aerobat. The provided information was consistent with the information in the instructor’s logbook.

The ATSB was informed that, in recent times, the instructor had been utilising cloud-based pilot logbook software to record flight experience. The ATSB was unable to gain access to the cloud-based system.

The instructor’s initial and ongoing aerobatics training was conducted in the Pitts Special aircraft. Apart from the instruction flights in VH-CYO during the week prior to the accident, the ATSB was unable to identify any previous aerobatic experience in the Cessna A150 Aerobat or any other similar Cessna variants.

The person who conducted the aerobatics training to give the instructor a rating for aerobatics, and a rating to instruct in aerobatics, stated that they informed the instructor of the limitations in the Mueller/Beggs method during their initial aerobatics training. All of the practical flying training aspects were conducted in a Pitts Special.

Medical information and recent history

The instructor held a current class 1 medical certificate with no restrictions, and the accompanying medical records did not indicate any underlying medical issues at the time of the accident.

The instructor was reported to be fit and well on the day of the accident. There were no issues identified in the post-accident medical and toxicological results (including carbon monoxide) that may have affected the instructor’s operation of the aircraft.

Aerobatic student

Experience and qualifications

The aerobatic student pilot held a valid private pilot licence (aeroplane) that was issued on 13 June 2010. They also held a single-engine aeroplane class rating, and manual propeller pitch control and retractable undercarriage design feature endorsements. The student had a total of 248.5 flight hours experience.

The student had conducted an introductory aerobatic flight in an American Champion Aircraft Corp 8KCAB with an instructor in December 2014. That flight did not include spins.

Medical information and recent history

The aerobatic student pilot held a current class 2 medical certificate with no restrictions, and the accompanying medical records did not indicate any underlying medical issues at the time of the accident. The student was reported to be well rested and in good spirits on the morning of the accident. There were no issues identified in the post-accident medical and toxicological results (including carbon monoxide) that may have affected the student’s operation of the aircraft.

Operator information

The Sunshine Coast Aero Club was located at the Sunshine Coast Airport. At the time of the accident, the aero club had about 100 members and 3 aircraft: 2 Recreational Aviation Australia (RAAUS) registered Sling 2 aircraft and a Cessna A150 Aerobat (Aerobat), registered VH-CYO.

The Aerobat was recently purchased with the intent to conduct aerobatic instructional flights for its members. At the time of the accident, the aero club did not have a Civil Aviation Safety Regulation (CASR) Part 141 certificate to conduct flight training in a VH registered aircraft, nor was it required for an instructor to conduct spin or aerobatics flight training. There were no aerobatics-trained instructors at the aero club.

The aero club sought the assistance of a contracted aerobatics instructor to conduct the aerobatic flight training, utilising the instructor’s own flight training approval. The first aerobatic flight training conducted by the aero club utilising VH-CYO was the week prior to the accident with the flight instructor who was on board the accident flight.   

Aircraft information

General information

The Cessna 150 is a high-wing, 2-seat, single piston engine aeroplane designed for flight training. The Aerobat was a slightly modified model that was designed to conduct basic aerobatic training. The type of manoeuvres approved in the Aerobat Pilot’s Operating Handbook (POH) included spins.

VH-CYO

VH-CYO (Figure 3) was manufactured in 1976 and first registered in Australia in 1995. It had been owned and operated by the Sunshine Coast Aero Club since March 2021. However, it had not been utilised for aerobatics until the week prior to the accident.

Figure 3: VH-CYO Cessna A150M Aerobat

ao-2021-025-figure-3.jpg

Source: Simon Coates

Maintenance information

The aircraft had a current certificate of airworthiness, certificate of registration, and maintenance release with no outstanding maintenance, or defects listed.

Subsequent to the accident, it was reported to the ATSB that the right-side radio push-to-talk switch had a defect which prevented radio calls from that position. Therefore, all calls had to be made from the headset and microphone plugged into the left-side jack point. It was also reported that the defect did not affect the intercom between pilots.

Rudder stop modification

The Cessna 150 and 152 series aircraft had a mandatory rudder stop modification identified as Single Engine Bulletin (SEB) 01-1. The Service bulletin was also mandated by Federal Aviation Administration Airworthiness Directive (AD) 2009-10-09 and therefore automatically mandated in Australia. The purpose as stated in the bulletin was as follows:

To provide an enhanced rudder stop, bumper, doubler and attachment hardware designed to assist in preventing the possibility of the rudder overriding the stop bolt during full left and/or right operation of the rudder.   

 VH-CYO had the rudder stop modification incorporated at the time of the accident.

Weight and balance

The aircraft’s published maximum take-off weight (MTOW) according to the Pilot Operating Handbook was 727.3 kg (1,600 lb). The aircraft’s weight for the accident flight was estimated to be about 14.3 kg over the MTOW on departure and about 7.1 kg overweight at the time of the accident.

Taking into consideration the aircraft’s calculated weights at take-off, and at the time of the accident, a centre of gravity (CG) calculation could not be carried out, as the aircraft’s weight was outside that of the published CG calculation limits (Figure 4). As the aircraft was over the MTOW, the data was extrapolated outside of the chart limits to get an estimate of the CG location at the time of the accident. The extrapolated value placed the CG aft of mid-range, but well forward of the aft limit.

Figure 4: Estimated weight and balance

ao-2021-025-figure-4.jpg

Source: Cessna, annotated by the ATSB

Recorded information

The aircraft flight path was derived from primary[4] and secondary[5] surveillance radar data recorded by Airservices Australia. The data included the aircraft’s position with a time stamp and altitude above mean sea level (AMSL) at 5-second intervals.

Figure 5 shows the last 90 seconds of flight with the spin entry beginning about 55 seconds before impact with terrain. The decent rate varied between data points, with an average descent rate of about 5,000 ft/min. The radar returns stopped at about 1,200 ft above mean sea level (AMSL), which was 800 ft above ground level (AGL) at the accident site. That was most likely due to the aircraft descending below radar coverage.

The last 2 recorded data points without pins were considered to be predictive and not an accurate representation of the aircraft position.

Figure 5: Radar data with timestamp, airspeed, altitude and vertical decent rate labelled

ao-2021-025-figure-5.png

Source: Google Earth, annotated by the ATSB

Site and wreckage examination

The accident site was located in a dense stand of trees that stood about 15–20 m high and straddled a creek line in a band about 50 m wide, with open areas of farmland on either side (Figure 6).

Figure 6: Area of accident site

ao-2021-025-figure-6.png

Source: Google Earth, annotated by the ATSB

The wreckage trail extended about 50 m from the initial tree impact point, until the final piece of wreckage, oriented in an east-west direction. There were several notable tree impact points, including trees that had been broken in half or completely felled by the impact forces. Calculations of the tree impact damage heights indicated the final flight path angle was a descent of 12.8° (Figure 7).

Figure 7: Final flight path angle of entry

ao-2021-025-figure-7.png

Source: ATSB

The main wreckage came to rest at the base of a tree that was struck at a height of about 10 m. The aircraft structure was significantly disrupted as a result of impacting several trees (Figure 8).

Figure 8: Aircraft main wreckage at the base of a large tree that was struck

ao-2021-025-figure-8.png

Source: ATSB

The ATSB conducted an examination of the aircraft wreckage. The examination identified that:

  • the disruption to the aircraft and foliage, coupled with the length of the wreckage trail, indicated that the aircraft had significant forward speed at impact
  • the flaps were in the retracted position
  • the aircraft had no evident pre-impact defects with the flight controls or aircraft structure
  • the aircraft was intact prior to impact with terrain
  • the engine had no obvious defects upon external examination, was free to rotate and had compression on all 4 cylinders
  • the throttle setting was captured at an idle position (full out and bent to one side) during the accident sequence
  • the propeller rotational damage signatures were minimal, indicating a low power setting
  • both seats were in the full aft position.

Survivability aspects

General information

During the accident sequence, the cockpit area was completely disrupted due to significant impacts with trees, leading to the occupants’ liveable space being compromised. For this reason, it was considered unlikely that the accident was a survivable event.  

Flight notes and tracking overdue arrivals

The CASR Part 91 Manual of Standards (MOS) stated that for some types of visual flight rules (VFR) flights a pilot was required to submit a flight plan, nominate a SARTIME for arrival, or leave a flight note with a responsible person. These included air transport flights, a flight over water, a flight in a designated remote area, or a flight at night proceeding beyond 120 NM from the departure aerodrome. In other cases, a pilot could elect to submit a flight plan, nominate a SARTIME or leave a flight note.

If a flight note was left with a responsible person, then that person had to be over 18 years old, have access to at least 2 operative telephones, and satisfy the pilot that they know how to contact the Joint Rescue Coordination Centre (JRCC) and will do so immediately in the event that the pilot’s flight was overdue.

In summary, a flight note was not formally required for flights similar to that conducted in VH-CYO on the day of the accident. However, flight notes or another method of identifying if an aircraft is overdue is highly recommended.

The ATSB was informed that the Sunshine Coast Aero Club had a method of tracking estimated arrival times. That method involved instructors informing the aero club administration of estimated arrival times and aircraft movements. The ATSB noted that the instructor of VH-CYO did not inform the aero club administration about the estimated time of the aircraft’s return. It was considered likely that the instructor, being a contractor who had not worked with the aero club before, was not informed or aware that it was the aero club procedure to do so.

The aircraft accident occurred at 1122. It was scheduled to return to refuel at about 1200, and it was reported missing at about 1515 by the aero club chief pilot when the second student raised concerns about the aircraft not returning from its flight.

The post-mortem reports for the pilots indicated that the occupants’ chances of survival would not have improved if the location of the wreckage was identified sooner.

Emergency and personal locator beacons

The aircraft was not fitted with a fixed emergency locator transmitter (ELT), nor was it required to be under the current regulations. 

ATSB research into the effectiveness of ELT’s in aviation accidents (AR-2012-128) stated that:

Data from the ATSB database show that ELTs function as intended in about 40 to 60 per cent of accidents in which their activation was expected. Records of the Australian Maritime Safety Authority’s SAR incidents shows that search and rescue personnel were alerted to aviation emergencies in a variety ways including radio calls and phone calls, and that ELT activation accounted for the first notification in only about 15 per cent of incidents. However, these ELT activations have been directly responsible for saving an average of four lives per year.

A personal locator beacon (PLB) was identified on the accident site in an area that was away from and not likely to be located by the occupants of the aircraft (if they had survived the impact). The beacon was in date and passed a self-function test to indicate that it was serviceable.

The ATSB research report also mentioned PLBs with the following suggestion:

…carrying a personal locator beacon (PLB) in place of or as well as a fixed ELT will most likely only be beneficial to safety if it is carried on the person, rather than being fixed or stowed elsewhere in the aircraft.

Aerodynamic spins

General description

An aerodynamic spin is a sustained spiral descent in which an aircraft’s wings are in a stalled condition, with one wing producing more lift than the other. This difference in lift sustains the rotation and keeps the aircraft in the spin. The nose angle can also vary considerably. In a fully developed, upright, left spin, an aircraft will simultaneously roll to the left while yawing to the left, making a vertical corkscrew path through the air. A spinning aircraft will descend more slowly than one in a vertical or spiral dive and it will also have a lower airspeed, which may oscillate.

Intentional spins are normally entered from a stall in straight and level flight, with the reduction in power, the application of full back elevator and full rudder in the intended direction of rotation at the moment of stall.

When entering a spin, an aircraft’s motion through the air is irregular at first. This is known as the incipient phase of the spin. Though the nature of the incipient spin is heavily dependent on the aircraft type and the manner of entry, recovery may be more rapid and require less control input in this stage compared with recovery from a developed spin. After a number of rotations and depending on the aircraft type, loading, and control inputs, an aircraft in an incipient spin may then settle into a regular rotating descent, known as a developed spin. A spin may steepen (nose-down) or flatten (nose more horizontal) as it continues, potentially requiring different recovery techniques. Figure 9 shows the various stages from spin entry until recovery.

Figure 9: Various stages of a spin and recovery

ao-2021-025-figure-9.png

Source: New Zealand Civil Aviation Authority, Spin avoidance and recovery

Recommended practices in preparation for spin

The CASA Flight Instructor Manual: Aeroplane stipulated:

The aeroplane must be clear of inhabited areas and normally in an area designated for the practice of such exercises. In addition, it should be at a height sufficient to ensure recovery by 3,000FT above ground level. The pre-spinning check will vary from aeroplane to aeroplane but will normally be similar to that used as a pre-stalling check in that particular aeroplane. In most aeroplanes flaps and undercarriage must be retracted during both the spin and spiral. … In all cases a 360° turn to ensure that all is clear around and below should be carried out immediately prior to commencing each exercise.

The information stipulated in the flight instructor’s manual was commonly referred to by the acronym HASELL, which is:

  • Height – sufficient to recover by 3,000 ft AGL
  • Airframe – wheels up / flaps up / CG ok / trim set
  • Security – seat belt tight / no loose items in aircraft or pockets
  • Engine – temperature and pressure / carburettor heat / mixture / fuel quantity and selection
  • Location – aerobatic area / no built-up area or public gathering within 600 m / forced landing fields available
  • Lookout – 360° turn or wingover.

Spin recovery techniques

Aircraft manufacturer spin recovery information

There was information provided by the aircraft manufacturer on spin recovery in 2 sections of the Cessna A150M Aerobat POH. This information was the same in each section, and the spin recovery technique stated that:

Should an inadvertent spin occur, the following procedure should be used:

1). Retard throttle to idle position.

2). Place ailerons in neutral position.

3). Apply and hold full rudder opposite to the direction of rotation.

4). Just after the rudder reaches the stop, move the control wheel briskly forward far enough to break the stall. Full down elevator may be required at aft centre of gravity loadings to assure optimum recovery.

5). Hold these control inputs until rotation stops.

6). As the rotation stops, neutralise rudder and make a smooth recovery from the resulting dive.

It also stated that:

Variations in basic airplane rigging or in weight and balance due to installed equipment or cockpit occupancy can cause differences in behaviour, particularly in extended spins. These differences are normal and will result in variations in the spin characteristics and in recovery lengths for spins of more than 3 turns. However, the above recovery procedure should always be used and will result in the most expeditious spin recovery.

Cessna also provided further information in a document tilted Spin Characteristics of Cessna Models 150, A150, 152, A152, 172, R172 and 177. Apart from reiterating the recovery procedure provided in the POH, it also stated information including:

Basic Guidelines for Intentional Spins

1). Know your aircraft thoroughly.

2). Prior to doing spins in any model aircraft, obtain thorough instruction in spins from an instructor fully qualified and current in spinning that model.

PARE spin recovery method

The PARE spin recovery method is generic and typical of most light single engine aircraft types. PARE is an acronym that stands for:

  • Power, idle
  • Ailerons, neutral (and flaps up)
  • Rudder, full opposite to the spin direction and held in that position
  • Elevator, forward

Hold these inputs until rotation stops, then:

  • Rudder, neutral
  • Elevator, easy pull to straight and level or climbing attitude.

A comparison between the Cessna A150 Aerobat recovery method and the PARE method indicated there was little difference between the 2 methods, with the exception that the Cessna method emphasised the use of the term ‘briskly’ in regards to the forward movement of the elevators, and that full forward elevator may be required.

Mueller/Beggs (emergency) spin recovery technique

The Mueller/Beggs recovery technique, sometimes referred to as the emergency spin recovery technique, was documented in an aerobatic article written by an aerobatic pilot, Eric Mueller, in the 1980s. The article stated that it was a technique designed to recover a Pitts Special aerobatic aircraft from an upright or inverted spin, even if the pilot was disorientated. The technique is as follows:

1. Power off

2. Remove your hands from the stick

3. Apply full opposite rudder

4. Neutralise the rudder and recover to level flight.

Another aerobatic pilot, Gene Beggs, popularised the recovery technique in a series of articles. Beggs’ reference manual titled Spins in the Pitts Special stated:

With this method you can quickly and easily recover from any spin in the Pitts Special. It is easy to remember and execute even if you are frightened or confused; furthermore, it is not necessary to know whether the spin is upright or inverted, the recovery is the same in either case.

In the Beggs course notes for advance spin recovery, the frequently asked questions section stated:

The question I hear most is “Will the emergency spin recovery work on all aircraft?” No, not exactly! Although I have found it works beautifully in the vast majority of cases, there are rare exceptions. You may occasionally encounter a spin mode in some aircraft in which you must physically apply nose-down elevator. This is extremely rare, and I assure you it will never happen in a Pitts Special.

A newsletter titled Spinoffs written by Beggs in 1985 indicated that the author was informed by another pilot that a Cessna A150 Aerobat would not recover using the emergency recovery method (Meuller/Beggs method). Beggs decided to conduct some spin testing in a standard Cessna 150. The following is a summary of that testing:

  • The aircraft would recover using the emergency recovery technique (hands off) in fully developed spins to the right.
  • The aircraft would not recover using the emergency recovery technique in fully-developed spins to the left, no matter how many turns the aircraft was allowed to do.
  • If the elevator was pushed forward briskly during the emergency recovery technique to the left, the aircraft would always recover promptly in one additional turn with pitch attitude almost perfectly vertically down.
  • In spins both to the right and left, the use of opposite aileron (out spin aileron) would produce a recovery from the spin. This was opposite to the results obtained in all other aircraft types (that had been previously spun by Beggs).
  • In the Cessna 150, the use of in-spin aileron always increased the rate of rotation and steepened the pitch attitude. This was also opposite to the results obtained in all other aircraft types.

Beggs stated having conducted thousands of emergency spin recoveries in numerous aircraft types. The Cessna 150 was one of the very few aircraft that required the application of full forward elevator to recover.

Regulatory requirements and guidance

The CASR Part 61 MOS, Volume 2, Section 6, Unit FAE-8 – Spinning, described the skills and knowledge required to execute and recover from an upright spin.

Unit FAE-8, element 4, titled underpinning knowledge, stated that the following items were required to be imparted to students:

(o) standard spin entry and recovery techniques for the aircraft being flown;

(p) number of turns normally required for spin recovery in the aeroplane type;

(r) Mueller-Beggs spin recovery action and limitations on its application

(s) ‘g’ and any other limitations applicable to spinning for the aeroplane type.

The Civil Aviation Aeronautical Publication (CAAP) 155-1(0) Aerobatics was issued in 2007. In relation to spin recovery, it stated:

Modern aerobatic aircraft designs normally have predictable spin characteristics and respond to the standard spin recovery technique. However, older aircraft and non-certificated or amateur built aircraft may have special characteristics which require particular recovery procedures. Therefore, pilots need to be familiar with, and practised in, the spin recovery procedure specified for the particular aircraft type.

It also stated:

Spin recovery procedures will vary between aircraft types and situations. The aircraft flight manual should be the final authority for spin recovery procedure…

The CAAP also discussed the Mueller/Beggs spin recovery method. The ATSB requested CASA’s interpretation on the Mueller/Beggs spin recovery limitations referenced in the MOS. It stated:

Civil Aviation Advisory Publication (CAAP) 155-1(0) – Aerobatics, published January 2007 provides guidance to pilots on aerobatics operations. Section 7 - Risk management and TEM includes subsection 7.24 Mueller-Beggs Spin Recovery, which describes the Mueller-Beggs recovery technique and associated limitations. There is also reference to the techniques in the underpinning knowledge sections of the Units of competency in Appendix A of the CAAP from which the MOS references were drawn.

As stated in 7.24.1, the main limitation, as is that it is known, is the technique is not effective in a number of aircraft types. 7.24.4 advises pilots to determine the extent to which the technique has been tested and found to be reliable in a particular aircraft type. It also states pilots wishing to test the procedure should also be familiar with the normal spin recovery procedure specified for the type. While 7.24.5 states the technique is not recommended, it may prove to be useful in the event a pilot becomes disoriented.

Based on the above information CASA’s opinion of the limitations of the Mueller-Beggs technique are:

1. Application of the technique may not be effective for the aircraft in which the training is conducted,

2.Use of the technique will likely delay the recovery from the spin and consequently increase the height lost, perhaps to a point recovery cannot be achieved,

3. The technique might be in conflict with the aircraft manufacturer’s recommended technique.

Reference to the technique is included in the CAAP to make pilots aware of its existence as an alternative recovery technique. In the event they become disoriented from high rates of rotation, which can be encountered in an upright or inverted spin, the technique might effect a recovery if other recovery techniques applied are unsuccessful.

Associated with a range of regulatory changes in December 2021, the CAAP was removed from the CASA website in January 2022.[6]

In April 2020, CASA issued Advisory Circular AC 61-16 v1.0 (Spin avoidance and stall recovery training). In addition to a variety of other guidance, it stated:

Before selecting an aircraft for stalling or spinning training, consult with the manufacturer and other users to establish what manoeuvres are safe to conduct, including steep turns, stalls, stalls with a wing drop and spinning.

It also stated that, prior to spinning any aircraft, pilots should:

- Comply with aircraft flight manual weight and balance and manoeuvre limitations, placards and, if provided, procedures and advice for each intended manoeuvre…

- Obtain thorough instruction in spins from an instructor fully qualified and current in spinning that model…

- Enter each spin at a high altitude. Plan recoveries to be completed well above the minimum legal altitude…

- Conduct all spin entries and recoveries in accordance with the procedures recommended by the manufacturer...

In the guidance for instructors, it stated:

- Ensure the aircraft is operated in accordance with the aircraft flight manual limitations and entry and recovery procedures for manoeuvres including stalling and spinning…

- Recognise and avoid the potential for negative training with a clear understanding of what the desired training outcome is for the lesson. The latent effects of negative training can stay with a pilot throughout their career…

The effects of centre of gravity on spins

The CASA Flight Instructor Manual: Aeroplane included a section for spins and how it is affected by the CG. It stated:

The effect of the position of the Centre of Gravity (CG) must be pointed out to the student if movement of this position within the limits laid down has a great effect on the spinning characteristics of the aeroplane. Normally a forward CG results in a steeper spin with a high rate of descent. A forward CG makes recovery much easier and may even prevent a spin altogether, resulting in a spiral dive. An aft CG tends to flatten the attitude resulting in a lower rate of descent. The recovery action to be taken when an aeroplane is spinning in a flat attitude is the same as the normal recovery technique with respect to the actual control movements. However, in the flat spin case it is essential to ensure that full control movement is applied in the recovery action and that this is maintained if necessary, for a much longer period than normal. In some aeroplanes it takes many turns to recover from a flat spin.

Related occurrences

Cessna A150 Aerobat (VH-CYO), Cairns, Australia, December 1995

The ATSB received a report from a previous pilot of VH-CYO about an incident that occurred in the aircraft involving a flat spin. The incident occurred near Cairns Airport in December 1995. A summary of that event was as follows:

  • On the day of the incident, the aircraft (VH-CYO) was being operated as an aerobatic aircraft with a student and instructor on board. The purpose of the day’s instructional flights was stalls, spins and spin recoveries.  
  • On the day of the training sequence, air traffic control (ATC) clearance was obtained to operate between 5,000 ft and 3,000 ft AMSL.   
  • The spin training exercise commenced at 5,000 ft and consisted of showing recovery, student follow through, and finally student completing the entry and recovery. 
  • As a final exercise, the student was instructed to commence the spin at about 5,000 ft, to allow the ‘spin’ to fully develop and recover from the spin when instructed.   
  • The instruction to recover was given at about 4,300 ft and the student was observed to apply the correct Cessna A150 POH recovery technique. However, the aircraft failed to recover from the spin. The instructor took control of the aircraft and applied the POH spin recovery method, but the aircraft failed to recover from the spin. 
  • As the aircraft descended towards the cleared level of 3,000 ft, the instructor believed the aircraft would not respond to the POH recovery method and may had entered a flat spin. The instructor attempted to force the nose down by commencing a backwards and forwards full deflection of the elevator motion. That action did not assist, so the instructor coordinated full throttle acceleration to elevator deflection with the thought that it might assist in getting a nose-down attitude. 
  • The instructor regained some control of the aircraft as it passed 1,000 ft, with the aircraft exiting the spin and entering a spiral dive. At approximately 700 ft, recovery from the resulting dive was completed, ATC was advised that the aircraft had flown below the minimum specified altitude, and a clearance was obtained to return to Cairns Airport. 

A subsequent engineering inspection, which included a check of the aircraft rigging, did not identify any defects.   

The instructor of the 1995 flight advised the ATSB that, after some consideration, they believed that the issue was most likely one of a rear centre of gravity in the loading of the aircraft. The instructor stated that they were 182 cm and about 85 kg, with the student being at least 188 cm and about 90–95 kg.  Both seat positions were adjusted to the rear stop and the fuel load was from memory sufficient for about 3.0 hours total. 

The instructor of the 1995 flight stated that they had spoken to 2 other pilots, who had detailed that, while conducting spinning together in another C150, they had experienced difficulty in exiting a planned spin, and their experience seemed to have been very similar to what the instructor encountered. 

Cessna 152 accident, Concord, United States, 29 January 2018

A Cessna 152 aircraft, registered N93316, lost control and impacted terrain, fatally injuring the pilot. A subsequent inspection of the aircraft identified that one of the rudder cables had failed and the other had frayed to a point where about 50% of the strands had fractured.[7]

  1. Primary radar returns are produced by radar transmissions that are passively reflected from an aircraft and received by the radar antenna. The received signal is relatively weak and provides only position information, not the aircraft’s altitude.
  2. Secondary radar returns are dependent on a transponder in the aircraft replying to an interrogation from a ground station. An aircraft with its transponder operating is more easily and reliably detected by radar and, depending on the mode selected by the pilot, the aircraft’s pressure altitude is also displayed to the air traffic controller.
  3. CASA advised that the CAAP was intended to be replaced by AC 61-18 Aerobatics.
  4. National Transportation Safety Board investigation WPR18FA075

Safety analysis

Introduction

Radar data indicated that, while being used to conduct spin training, the Cessna A150 Aerobat (VH-CYO) entered a spin at 5,800 ft above ground level and the spin was not fully recovered before the aircraft impacted terrain. Site and wreckage examination indicated that the aircraft had significant forward velocity, a low angle of entry, and the throttle was captured in the idle position. Those items of evidence indicated that the aircraft was most likely in the initial stages of recovery from the spin when the aircraft impacted terrain.

In previous training with the student on board, the instructor had demonstrated each manoeuvre before handing control to the student. The accident occurred during the first manoeuvre of the training session, and the ATSB was unable to ascertain which of the 2 pilots (instructor or student) was controlling the aircraft at various stages of the spin and for the initiation of the recovery.

This analysis discusses several possible reasons for the aircraft not being fully recovered from a spin before impacting terrain. These include:

  • mechanical failure
  • flight control obstruction
  • aft centre of gravity and flat spin
  • pilot incapacitation
  • interference with the controls
  • incorrect recovery technique.

Potential scenarios to explain absence of recovery from spin

Mechanical failure

A failure of the aircraft structure, the flight control system, or a rudder locking past the rudder stops have contributed to aircraft accidents in the past. However, examination of the aircraft structure and flight controls of the aircraft did not reveal any pre-impact defects. The aircraft also had a modification incorporated to prevent the rudder-stop locking issue that had contributed to some previous Cessna 150 accidents.

Further, there was evidence that the aircraft was in the early stages of recovery from the spin, which indicated that whatever had delayed the recovery had been overcome prior to impacting terrain.

Overall, it was considered unlikely that some type of mechanical failure of the flight controls contributed to the accident. However, due to the disruption and displacement of the wreckage, the ATSB was unable to completely rule out the possibility of a mechanical issue.

Flight control obstruction

Aircraft accidents have previously occurred where foreign object obstruction has led to flight controls becoming locked, preventing the pilots from controlling their aircraft. If an object had locked the controls of VH-CYO, the initial stages of the recovery evident before impact with terrain would indicate that the controls became unlocked, or more controllable, during the final stages of the descent.

The examination of the aircraft did not reveal any issues in relation to flight control locking due to foreign object fouling. However, due to the disruption and displacement of the wreckage, the ATSB was unable to rule out the possibility of a flight control obstruction, but it was considered to be unlikely.  

Aft centre of gravity and flat spin

The further aft the aircraft’s centre of gravity is, the more difficult it may be to lower the nose in order to recover from a spin. In this case, the aircraft was slightly over the maximum allowable take-off weight (MTOW) for the entire flight. Regarding the aircraft loading and centre of gravity (CG), and after interpolating the data (as the aircraft was outside its weight limit), it was considered to be within the desired CG range, trending towards aft of nominal.

It is possible that the spin entry or recovery actions created a flat spin, where the nose was comparatively high compared to a normal spin (with the nose slightly down). This can be exacerbated by an aft CG and can make the aircraft slower to respond to recovery techniques. Previous incidents in the same aircraft type have shown that flat spins can be very difficult to recover, even when the appropriate recovery technique is applied for an extended period.

In summary, it is possible that the aircraft entered a flat spin that was unable to be fully recovered, and that the aft CG may have exacerbated the difficulty in recovering from the spin. However, there was insufficient evidence to conclude that this occurred.

Pilot incapacitation

Both of the pilots were reported to be well at the time of the accident, and the pre and post-accident medical information did not identify any conditions or issues with either pilot that may have contributed to the accident. Also, as previously noted, the aircraft was most likely in the initial stages of recovery from the spin when the aircraft impacted terrain. Accordingly, the ATSB considered it unlikely that pilot incapacitation contributed to the accident.

Interference with the controls

The Cessna A150 Aerobat is a dual control aircraft. If an inexperienced pilot were to ‘freeze’ at the controls or make other inappropriate flight control inputs, it may be difficult for the instructor to regain control of the aircraft.

As previously noted, it was not possible to ascertain which of the 2 pilots (instructor or student) was controlling the aircraft at various stages of the spin and for the initiation of the recovery. In addition, during the previous week, the student conducted steep turns, stall recovery, loops, and barrel and aileron rolls. The student had also done a small amount of aerobatics several years before the accident and had a reasonable amount of flight experience. Overall, none of the available evidence indicated that the student was susceptible to freezing at the controls or making other inappropriate flight control inputs.

Incorrect recovery technique

The instructor owned, was trained on, and had significant aerobatic experience in the Pitts Special aerobatic aircraft. However, the ATSB could not identify any aerobatic experience for the instructor in the Cessna A150 Aerobat or similar variants, apart from the previous week’s instructional activities with the same students. That training did not include spin entry and recovery techniques.

The aircraft manufacturer’s guidance document on spin characteristics stipulated that, if the instructor was unfamiliar with the aircraft type’s spin characteristics, then they should obtain thorough instruction in spins from an instructor qualified and current in spinning that particular model aircraft. The Civil Aviation Safety Regulation (CASR) Part 61 Manual of Standards (MOS) stated that underpinning knowledge for spin training included the standard spin entry and recovery techniques for the aircraft being flown. Other CASA guidance highlighted the importance of being familiar with the spin recovery method specific to the aircraft type. However, the ATSB could not identify if the instructor had sought additional information about the Aerobat’s spin characteristics. It is possible that, due to the instructor’s general familiarity and experience on a similar, non-aerobatic variant (the Cessna 152), they did not consider that recovery techniques successfully utilised on other aircraft types would not work equally as effectively on the Cessna A150 Aerobat.

The theoretical spin recovery training conducted by the instructor on the morning of the accident included 2 recovery methods; namely the PARE and Mueller/Beggs methods. The PARE method was closely aligned with (but not exactly the same as) the method described in the Cessna A150 Aerobat Pilot’s Operating Handbook (POH) and the Cessna guidance document. The Mueller/Beggs method has proven to be a very effective method of spin recovery in most aircraft types, though there are a few aircraft types that will not recover using this method. The Cessna A150 Aerobat and similar variants are aircraft types that most likely will not recover from a spin to the left, as was the case in this accident.

The Part 61 MOS stated that the instructor should teach the students the method of recovery in the aircraft type that they will be operating in. It also stated that the limitations of the Mueller/ Beggs method should also be discussed. However, according to the second student who received the theoretical instruction, the instructor did not highlight to the student’s what recovery method was recommended in the POH, or that the Aerobat would not recover utilising the Mueller/Beggs technique.

Further, the instructor informed the students to write down both methods of recovery (Mueller/Beggs and PARE) on a piece of paper for reference during the flight. The second student was of the firm belief that they would be conducting both methods of spin recovery in the Aerobat, with the first method written down being the Mueller/Beggs method.

The ATSB considered it likely that the instructor was not aware or did not recall that the Aerobat would not recover utilising the Mueller/Beggs method in a spin to the left. Further, the evidence indicates that the instructor intended to utilise both methods of recovery in 2 separate spin sequences on the accident flight.

If the Mueller/Beggs method was being used for the first exercise, it would provide a viable explanation of the accident sequence. However, based on the available evidence, the ATSB was unable to establish if the Mueller/Beggs method was being utilised at the time of the accident, or if it contributed to the delayed recovery time.

Survival aspects

Management of overdue aircraft

Due to the nature of the impact, the accident was not survivable. However, the investigation noted that there were potential areas for improvement that could be relevant in other situations.

The Sunshine Coast Aero Club had a common practice for flight instructors to log an estimated arrival/return time with the aero club’s administrator prior to departing for a flight. However, that procedure was not utilised on the day of the accident. The ATSB considered it likely that the contracted flight instructor was not informed of the procedure and therefore did not inform the administrator of their estimated time for return. As a consequence, the aero club did not discover that the aircraft was overdue for some time, and subsequently reported the aircraft missing about 3 hours after it was due to return.

Although there is no regulatory requirement to do so for many types of flights under the visual flight rules, a standardised method to identify if an aircraft is missing would decrease the amount of time for the Joint Rescue Coordination Centre to be notified and for a subsequent search for the aircraft to commence.

Emergency locator transmitter and portable locator beacons

The aircraft was not fitted with a fixed emergency locator transmitter (ELT). Although a fixed ELT is not a regulatory requirement, they are an effective safety feature that have been shown to significantly reduce the amount of time between an aircraft accident and identifying the location of the aircraft by search and rescue.

A portable locator beacon (PLB) was identified in an area away from the aircraft occupants that would not likely have been located without an extensive search. Carrying a PLB would be much more beneficial to safety if it is carried on the person, rather than being fixed or stowed elsewhere in the aircraft.

Findings

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

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

From the evidence available, the following findings are made with respect to the collision with terrain accident involving Cessna A150 Aerobat registered VH-CYO on 23 June 2021.

Contributing factors

  • While the student and instructor were conducting aerobatic spin training starting at 5,800 ft above ground level, for reasons that could not be established, the aircraft did not fully recover from a spin before impact with terrain.

Other factors that increased risk

  • It is likely that the aerobatics instructor had no flight experience conducting spinning and/or spin instruction in the Cessna A150 Aerobat or similar variants. It was also considered probable that they did not seek advice from an experienced aerobatic instructor on the A150 type about the aircraft’s spin characteristics.
  • The spin training theory provided by the instructor to the 2 aerobatics students was generic in nature and did not highlight the limitations of the Mueller/Beggs spin recovery technique or provide guidance on the method recommended in the Cessna A150 Pilot’s Operation Handbook, as stipulated in the Civil Aviation Safety Authority aerobatic instruction procedures and guidance material.
  • It was likely that the aerobatics instructor intended to practice the Mueller/Beggs method of spin recovery during the accident flight in the Cessna A150 and was likely unaware that the aircraft type was one of the few types that would not recover from a spin to the left utilising that technique.
  • On the day of the accident the aircraft operator was not utilising a flight following procedure to identify if an aircraft was overdue, nor were they required to under the current regulations. Therefore, the overdue aircraft was not identified and reported as missing for 3 hours after it was due to return.

Other findings

  • The aircraft structure and flight controls were examined, and no pre-impact defects were identified.
  • It could not be determined which pilot was controlling the aircraft during the various stages of the accident flight and spin recovery.
  • The aircraft was not fitted with a fixed emergency locator transmitter, nor was one required by the regulations. Fixed emergency locator transmitters have been shown to be an effective safety feature to reduce the amount of time taken to identify an aircraft’s location, even if the occupants are incapacitated.

Safety actions

Safety Advisory Notice

Safety advisory notice to aerobatic pilots and instructors

SAN number:

AO-2021-025-SAN-001


The ATSB strongly encourages all aerobatic pilots and aerobatics flight instructors to be aware:

  • the Mueller/Beggs method of spin recovery does not recover all aircraft types from a spin
  • the Mueller/Beggs spin recovery method limitations should be emphasised during spin theory training
  • the Mueller/Beggs method of spin recovery will not recover a Cessna A150 Aerobat or similar variants from a spin in some circumstances
  • they should review the pilot’s operating handbook of the aircraft type that they intend to operate for the recommended spin recovery technique
  • prior to doing spins in any model aircraft, they should obtain instruction and/or advice in spins from an instructor who is fully qualified and current in spinning that model.

Glossary

AC                  

Advisory circular

AGL                

Above ground level

AMSL               

Above mean sea level

ATC                

Air traffic control

CAAP              

Civil aviation advisory publication

CASA              

Civil Aviation Safety Authority

CASR              

Civil Aviation Safety Regulations

CFI                 

Chief flying instructor

CG              

Centre of gravity

ELT                 

Emergency locator transmitter

IAS         

Indicated airspeed

MOS               

Manual of standards

MTOW            

Maximum take-off weight

PARE              

Spin recovery method that is generic and typical of most light single engine aircraft types

PLB                 

Personal locator transmitter

POH                

Pilot operating handbook

VFR                

Visual flight rules

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • Sunshine Coast Aero Club
  • student pilot who underwent theoretical and practical training with the instructor
  • the instructor’s aerobatics instructor
  • Civil Aviation Safety Authority
  • Queensland Police Service
  • aerobatic subject matter experts
  • Airservices Australia.

References

ATSB Research Investigation AR-2012-128, The effectiveness of emergency locator transmitters in aviation accidents.

New Zealand Civil Aviation Authority (2014) Spin avoidance and recovery.

Experimental Aircraft Association Inc. (1985) ‘Spinoffs-Gene Beggs’, International Aerobatic Club Sport Aerobatics Magazine.

Beggs G (2001) Aerobatics with Beggs: Spins in the Pitts Special (A guide and reference manual for aerobatic instructors and students).

Submissions

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

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

  • the Sunshine Coast Aero Club
  • the student pilot
  • the instructor’s aerobatic instructor
  • the Civil Aviation Safety Authority (CASA)
  • the aircraft manufacturer.

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

Purpose of safety investigations & publishing information

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

Occurrence summary

Investigation number AO-2021-025
Occurrence date 23/06/2021
Location 5 km WSW of Peachester, Queensland
State Queensland
Report release date 10/08/2022
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model A150M
Registration VH-CYO
Serial number A1500655
Aircraft operator Sunshine Coast Aero Club Pty. Ltd.
Sector Piston
Operation type Flying Training
Departure point Sunshine Coast, Queensland
Destination Sunshine Coast, Queensland
Damage Destroyed

Technical review of the Transportation Safety Board of Canada's investigation A19Q0109 - Main rotor blade failure in flight, Robinson R44, C-FJLH, 10 July 2019

Summary

Following the publication of the Transportation Safety Board of Canada’s report on their investigation of this accident, a directly involved party to that investigation requested the Board reconsider some of its findings as to causes and contributing factors.

Accordingly, the Board requested the assistance of the Australian Transport Safety Bureau in conducting an independent review of the investigation report; specifically, the role of the main rotor blades in this occurrence based on the available evidence and technical analysis conducted by the TSB Engineering Laboratory.

In support of this request and to ensure the protection of any sensitive information provided, the ATSB has initiated an external investigation under the Transport Safety Investigation Act.

Final

What happened

On 10 July 2019, a Robinson Helicopter Co model R44 helicopter, registered C-FJLH, with two persons on board, collided with terrain near Lac Valtrie, Quebec, Canada. Both persons died as a result of the accident.

The Transportation Safety Board of Canada (TSB) investigated the accident and released a public report on 31 March 2021 (A19Q0109). Subsequently, the helicopter manufacturer (Robinson) formally requested that the TSB reconsider its reported findings in relation to the role of the helicopter's main rotor blades (specifically the localised disbonding of the lower aerofoil skin of one blade) in the development of the accident.

ATSB involvement

In support of this request, on 13 May 2021, the TSB Chair formally requested assistance from the ATSB Chief Commissioner in the conduct of an independent review of the TSB report’s findings relating to the main rotor blades' role in the accident. Supporting materials were provided, including the TSB's laboratory report on the blade examination and, with the permission of the helicopter manufacturer, the submissions it provided on the laboratory, draft and public reports.

To support the review and ensure appropriate protections were afforded to the information provided, the ATSB commenced an External Aviation investigation (AE-2021-019) under the Australian Transport Safety Investigation Act 2003 (TSI Act). As such, all information received from the TSB was classified as Restricted Information in accordance with Section 60 of the TSI Act.

Investigation outcomes

The ATSB has completed its review of the TSB investigation and provided detailed feedback to the TSB management and Board under the provisions of s.62 of the TSI Act.

As such, all inquiries regarding the outcomes of this review should be directed to the Transportation Safety Board of Canada via their website: General enquiries - Transportation Safety Board of Canada (tsb.gc.ca)

Occurrence summary

Investigation number AE-2021-019
Occurrence date 10/07/2019
Location Near Lac Valtrie, Quebec, Canada
State International
Report release date 31/08/2021
Report status Final
Investigation level Short
Investigation type External 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 R44
Registration C-FJLH
Serial number 2044
Sector Helicopter
Operation type Private
Departure point Lac de la Bideire, Quebec, Canada
Destination Sainte-Sophie, Quebec, Canada
Damage Destroyed

Loss of control and collision with terrain involving Cessna R172K, VH-DLA, near Sutton, New South Wales, on 13 April 2021

Preliminary report

Preliminary report released 4 June 2021

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 13 April 2021 at about 1324 Eastern Standard Time,[1] the pilot of a Cessna R172K aircraft registered VH-DLA (DLA), departed Canberra Airport, Australian Capital Territory with an observer on board to conduct power line survey work to the north of Sutton, New South Wales.

At 1622 DLA crossed Tallagandra Lane (Figure 1) and proceeded with survey work concentrating on power lines servicing properties to the east of the lane. Following the completion of two orbits, at 1624, the pilot initiated a right turn, and tracked to the north‑east.

Witnesses in the area described the aircraft flying low above the trees before commencing a left banking turn followed by a steep descent and collision with terrain. The witness reports indicated that a loss of control and entry into a spin preceded the ground impact. The pilot and the observer were fatally injured.

Analysis of recorded Garmin GPS and OzRunways flight data identified that the last Garmin GPS data point at 1624:48 showed the height of the aircraft to be about 164 feet above ground level and about 115 metres from the wreckage. The final OzRunways data point at 1624:50 was about 80 metres from the accident site.

Figure 1: Garmin GPS and OzRunways flight tracks shown relative to the accident site

picture1-ao-2021-016.png

Image description: DLA flight paths – Garmin data is primarily referenced due to its higher sample rate and increased vertical accuracy. The final segment of OzRunways data is included as it provided the closest data point to the accident site. Source: Google, with Garmin GPS and OzRunways data, annotated by the ATSB

Context

Wreckage and impact information

The wreckage was located in an open field about 30 metres east of Tallagandra Lane, and about 10 km to the north-west of Sutton. There was little spread of wreckage with few parts liberated in the accident sequence. Larger items, including the propeller and the right undercarriage leg were found next to the fuselage. Items from the luggage locker were located within 5 metres of the initial impact point. The most distant item from the main wreckage was the aircraft battery which was found near the edge of Tallagandra Lane.

Examination of the wreckage showed that the aircraft impacted the ground in a near vertical, nose down attitude.

Aircraft information

DLA was a single engine, Cessna R172K aircraft. It was manufactured in the United States in 1977 with serial number R1722809 and first registered in Australia in 1978.

Further investigation

To date, the ATSB has:

  • examined the wreckage
  • collected items for further examination
  • interviewed witnesses
  • retrieved flight‑related electronic data
  • collected weather data from the Bureau of Meteorology
  • interviewed the operator.

The investigation is continuing and will include further examination and analysis of:

  • the aircraft flight path, including analysis of recorded flight data
  • pilot qualifications, experience and medical history
  • pilot flight and duty periods
  • aircraft weight and balance
  • aircraft maintenance records
  • flight survey operational procedures.

Should a critical safety issue be identified during the course of the investigation, the ATSB will immediately notify relevant parties so appropriate and timely safety action can be taken.

A final report will be released at the conclusion of the investigation.

Acknowledgements

The ATSB acknowledges the assistance of the New South Wales Police Force in supporting the ATSB on‑site investigation team through the evidence collection phase of the operation.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2021

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1.  
    1. Eastern Standard Time (EST): Coordinated Universal Time (UTC) + 10 hours.

Final report

Safety summary

What happened

In the early afternoon of 13 April 2021, a Cessna R172K aircraft registered VH-DLA (DLA) departed Canberra Airport, Australian Capital Territory, with a pilot and observer onboard to conduct powerline survey work to the north of Sutton township, New South Wales.

About 3 hours into the flight, while conducting powerline inspection in the vicinity of Tallagandra Lane, nearby witnesses observed the aircraft flying low above the trees before commencing a left turn that continued in to a steep descent and collision with terrain. The pilot and the observer were fatally injured, and the aircraft was destroyed.

What the ATSB found

The ATSB found that while manoeuvring to align the aircraft to inspect a powerline, the aircraft aerodynamically stalled and entered a spin at a height that was insufficient for recovery prior to the collision with terrain.

What has been done as a result

Following the accident, the operator amended the training and checking section of their Operations Manual to incorporate Threat and Error Management (TEM) and Situational Awareness (SA) training modules for powerline low‑level survey operations. The amendments enhanced existing topics in the operator’s crew resource management training and stipulated learning outcomes and assessment criteria specific to TEM and SA.

The operator also advised that they intended to introduce an airspeed ‘manoeuvre margin’ to take in to account the increased stall speed associated with steep turns.

Finally, the operator plans to modify their aircraft to include an angle of attack indicator to supplement the installed stall warning and a g‑meter with recording and data download capability to enable post flight review.

Safety message

This accident highlights the need for pilots to manage airspeed and bank angle to minimise the risk of an aerodynamic stall. This is particularly important when operating in close proximity to the ground, such as during take-off, landing and when conducing low-level air work, as recovery may not be possible.

The investigation

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

The occurrence

On 13 April 2021 at 1324 Eastern Standard Time,[1] a Cessna R172K aircraft registered VH-DLA (DLA) departed Canberra Airport, Australian Capital Territory, with a pilot and observer onboard to conduct powerline survey work to the north of Sutton township, New South Wales.

At 1622 DLA crossed Tallagandra Lane (Figure 1) and the observer proceeded to inspect powerlines servicing properties to the east of the lane. Following the completion of two orbits, the pilot initiated a right turn and tracked to the north‑north‑east.

Witnesses in the area described that, following the right turn, the aircraft was flying low above the trees before commencing a left turn that continued into a steep descent and collision with terrain. The witness reports, including one from an experienced pilot, were consistent with a loss of control and entry into a spin preceding the ground impact. The pilot and the observer were fatally injured and the aircraft was destroyed.

Analysis of the final segment of recorded Garmin GPS[2] and OzRunways[3] flight data (see the section titled Recorded data) identified that the last Garmin GPS data point at 1624:48 showed the height of the aircraft was about 164 ft above ground level (AGL) about 115 metres from the accident site. The final OzRunways data point, recorded at 1624:50, was about 80 metres from the accident site and indicated that the aircraft was about 80 ft AGL (Figure 1).

Figure 1: Recorded flight path data shown relative to the accident site

Figure 1: Recorded flight path data shown relative to the accident site

Image description: DLA flight path – Garmin data is primarily referenced due to its higher sample rate and increased vertical accuracy. The final segment of OzRunways data is included as it provided the closest data point to the accident site.

Source: Google, with Garmin GPS and OzRunways data, annotated by the ATSB

Context

Pilot information

The pilot of VH-DLA (DLA) held a Commercial Pilot Licence (Aeroplane) issued in December 2019. The pilot also held a single engine aeroplane class rating, and a manual propeller pitch control design feature endorsement. The pilot completed a low-level aeroplane operational rating on 28 November 2019, valid for 2 years, and a single‑engine flight review on 15 March 2021, valid until 31 March 2023.

The pilot held a Class 2 Aviation Medical Certificate issued by the Civil Aviation Safety Authority, without medical restrictions, which was valid until 1 November 2023.

The operator’s records indicated the pilot had a total flying experience of 968.8 hours to the last recorded flight on 12 April 2021, of which about 572 hours were in the Cessna 172. In the previous 90 days, the pilot had flown 164.6 hours on type, and in the previous 30 days the pilot had flown 66.4 hours on type.

The pilot completed the operator’s low-level proficiency check on 9 February 2021 and was issued with a low-level, aerial survey certificate of competency to conduct powerline inspections without supervision. The pilot’s accumulated flight time conducting powerline survey work, following the operator’s approval, was about 135 hours.

Workload and fatigue

The operator had identified that aerial powerline survey work could be fatiguing for pilots and observers. To manage this, the operator applied work time limitations for pilots with fewer than 200 hours of powerline survey experience. Those pilots were limited to 6 hours of survey flight time per day with flights, conducted in sorties of 2‑3 hours duration.

After having 2 days off, the pilot had ferried the aircraft from Albury, New South Wales on the day prior to the accident and then logged about 5 hours of survey flight time over two sorties. On the day of the accident, the pilot had flown an earlier survey sortie of 1.3 hours duration and had been flying for about 3 hours when the accident occurred.

In flight, it was normal practice for the observer to direct the pilot to fly a pre-prepared route while the observer inspected the powerlines. To facilitate the observer’s work, the pilot was required to make constant changes to the aircraft’s heading and power setting to manoeuvre the aircraft into the optimum position for the observer. This resulted in a higher sustained pilot workload than that involved in flying an aircraft in straight and level flight. The operation of the aircraft at low level and relatively slow speeds also left little room for error. Research has shown that when an individual has to detect specific types of targets or stimuli over an extended period, their performance will decrease (Wickens and Hollands 2000).

The ATSB considered the effect of the sustained attention to flight parameters over the final sortie, but there was insufficient evidence to establish whether the pilot was affected by a level of fatigue that may have impacted their performance.

Post-mortem examination

The post-mortem and toxicology examinations did not identify any indicators of incapacitation or substances that could have affected the pilot’s capacity to perform the flight.

Aircraft information

DLA was a single engine, Cessna R172K aircraft. It was manufactured in the United States in 1977 with serial number R1722809 and was first registered in Australia in 1978. It was a four-seat, high-wing aircraft, with a non-retractable tricycle undercarriage. The aircraft was powered by a Teledyne Continental Motors IO-360, six-cylinder, fuel‑injected piston engine, driving a two-blade, constant speed propeller.

A maintenance release for the aircraft was issued following the completion of scheduled inspections on 2 March 2021 for day VFR[4] operations, at an aircraft time in service of 16,488.5 hours. There were no open defects recorded on the maintenance release and no outstanding or overdue maintenance was noted.

The aircraft’s maintenance records also showed that in the 6 months prior to the accident, DLA’s:

  • pitot static system had been checked for leaks
  • pressure altimeter had been checked for serviceability
  • fuel quantity system had been calibrated.

The airspeed indicator was tested in October 2018 and found to be serviceable. At the time of the accident, the instrument had accumulated 283 hours, time-in-service.

A weight and balance assessment identified that, at the time of the accident, the aircraft’s weight was about 979 kg, 178 kg below the aircraft’s maximum gross weight limit of 1157 kg, and the aircraft’s centre of gravity was within limits.

Aircraft stall and spin behaviour

The Pilot’s Operating Handbook for the Cessna R172K specified that, depending on the aircraft’s centre of gravity position, at its gross weight limit and with 10° of flap selected, the aircraft would stall[5] at between 41‑43 knots indicated air speed. The altitude loss during recovery from a wings level stall could be up to 160 ft.

A spin can result when an aircraft simultaneously stalls and yaws.[6] The yaw can be initiated by rudder application or by yaw effects from a range of factors that include aileron deflection, torque (engine power setting) and engine/propeller effects. A spin is characterised by the aircraft following a downward, corkscrew path and requires significantly more altitude for recovery compared to a wings level stall. The Cessna R172K Pilot’s Operating Handbook specified that at least 1,000 ft should be allowed for a one turn spin and recovery.

Further, should a stall occur during a turn, the aircraft’s behaviour becomes dependent on which wing stalls first. That is, it is possible for the upper wing to stall resulting in the aircraft rolling and yawing in the opposite direction to the turn.

Wreckage and impact information

The accident site was located about 10 km to the north-west of the township of Sutton in an open field about 30 metres east of Tallagandra Lane. From the accident site, the terrain sloped up to the north‑west by about 240 ft over a distance of about 600 m. The terrain dipped slightly to the east of the site, dropping about 50 ft over a distance of about 500 m.

Most of the aircraft wreckage was located next to the initial impact point. Larger items, including the propeller and the right undercarriage leg were found next to the fuselage. Items from the luggage locker were located within five metres of the aircraft’s initial impact point. The most distant item from the main wreckage was the aircraft battery which was found near the edge of Tallagandra Lane. The limited spread of wreckage indicated that the aircraft impacted the terrain with little horizontal speed.

Examination of the wreckage showed that the aircraft impacted the ground in a near‑vertical, nose‑down attitude. Damage signatures on the wing leading edges indicated that the right wing impacted the terrain first. The outboard section of the right wing, leading edge, near the tip was slightly deflected up, which was consistent with the aircraft spinning to the right at impact.

Compression damage to the forward fuselage reduced the available cabin space. While the occupants were secured with 4-point harnesses, the accident was non‑survivable.

Site and wreckage examination did not identify any aircraft defects that could have contributed to the accident and there was no evidence of birdstrike.

It was noted that the aircraft’s wing flaps were extended. Assuming a correctly rigged flap system, examination of the flap actuator screw jack extension determined that the flaps were set in the down position, at 18-20°.

Inspection of the aircraft’s stall warning system established that, other than damaged tubing attributed to the accident sequence, the warning horn sounded when suction was applied. The system was therefore considered serviceable prior to the accident.

Operational information

Powerline survey

The role of the observer was to coordinate the powerline survey work. The observer monitored the survey’s progress on a map depicting the electrical distribution network and directed the pilot to the sections of powerline to be inspected (Figure 2). The map was marked with warnings and cautions associated with network specific features and areas to avoid (no-fly areas) associated with dwellings, livestock and/or hazardous features.

The sequence in which the survey progressed was a combination of the flight crew’s pre‑departure planning and in-flight variations as determined by the observer. The pilot would fly the aircraft in response to the observer’s directions provided it was safe to do so. The observer would photograph any observed powerline defects and annotate their location on the distribution network map.

Figure 2: Aircraft flight path and electrical powerline network in the vicinity of the accident site

Figure 2: Aircraft flight path and electrical powerline network in the vicinity of the accident site

Source: Google, with operator supplied powerline network distribution map, and Garmin GPS and OzRunways data, annotated by the ATSB

To provide the right‑seat observer with the best opportunity to detect defects, the pilot would position the aircraft to keep the powerline to the right of the observer, at a height of about 150 ft above ground level and 150 ft horizontally from the powerline. According to the operator, the speed of the aircraft would preferably be maintained above 70 kt to maintain a margin above the aircraft’s stall speed and slow enough for the observer to note defects. The operator further advised that during survey operations the aircraft flaps were normally set at 10°.

The operator’s Aircrew Operational Procedures Manual instructed pilots that when surveying T‑Offs,[7] from a main distribution line that may require significant manoeuvring, the pilot should initiate a partial orbit of 270° commencing in the opposite direction to the T-Off orientation (Figure 3).

Figure 3: Powerline survey T-Off positioning manoeuvre (partial orbit)

Figure 3: Powerline survey T-Off positioning manoeuvre (partial orbit)

Source: Oberon Aviation Services and annotated by the ATSB

This was a standard re-positioning procedure that would result in a lower bank angle and wing load factor[8] while orientating the aircraft in the direction of the target T‑Off.

With respect to aircraft aerodynamics, the wing load factor or g-force on the wings varies with the angle of bank in a level turn and has a direct influence on the aircraft stall speed. Specifically, as the angle of bank increases, the load factor and the stall speed of the aircraft also increases.

To turn, an aircraft must roll in the desired direction, which increases the aircraft's angle of bank. Turning flight lowers the wing's vertical lift component. To compensate (and prevent the aircraft from descending), the lift force must be increased by pulling back on the control yoke to increase the angle of attack of the wings. If the angle of attack reaches a critical angle, loss of lift and increased drag occurs, and the wing will aerodynamically stall.

Final flight segment

On completing the survey work to the east of Tallagandra Lane, the pilot conducted a turn to the north-north-east and momentarily tracked parallel to the main distribution line that ran beside the lane (Figure 4). Based on flight path data and progress notations on the electrical network distribution map, the next powerline to be surveyed was the branch to the north-west which departed the main distribution line near the accident site.

 Figure 4: VH-DLA flight path in the vicinity of the accident site

Figure 4: VH-DLA flight path in the vicinity of the accident site

Source: Google, with operator supplied powerline network distribution map, and Garmin GPS and OzRunways data, annotated by the ATSB

The operator advised the ATSB that the standard procedure to establish the aircraft to survey that branch would have been for the pilot to conduct a partial right orbit through 270° prior to intercepting the powerline. However, the witness accounts indicated that the aircraft banked left towards the branch immediately before the accident. The operator was unable to provide advice as to why the orbit manoeuvre was not performed at this point. Flight path data showed the pilot had performed the 270⁰ partial orbit manoeuvre in similar situations earlier in the flight.

The ATSB considered whether the final turn may have been an evasive action by the pilot to avoid birdlife, however there was insufficient evidence to determine if that may have influenced the turn.

Meteorological information

The forecast meteorological conditions for the Canberra Airport area indicated winds from the north-west at 12-14 kt and no cloud below 5,000 ft AGL. Visibility was forecast to be 10 km or greater. The METAR[9] for Canberra Airport issued at 1600 was consistent with the forecast conditions, with recorded wind from the west-north-west at 10 kt with visibility of 10 km or greater and a temperature of 18⁰ Celsius.

Witnesses in the accident area reported that visibility was unlimited, and there was little to no wind.

Recorded data

DLA was not equipped with a flight data or cockpit voice recorder, nor was it required to be. Flight path data from the OzRunways application and Airservices Australia secondary surveillance radar was provided to the ATSB. Data was also retrieved from an on-board Garmin Aera 500 GPS and a Garmin GPSMAP 60Cx portable GPS unit for analysis.

Speed and position data from the Garmin 60Cx unit was used in the analysis of the aircraft’s movement as it offered better resolution and was recorded at a higher sampling rate than the other sources.

Due to a gap in data between DLA’s final recorded GPS position and the accident site, data from previous turns was used to estimate the performance of the aircraft during the final turn where the loss of control occurred.

Estimated values for speed, bank angle and stall margin during the final turn were derived from the analysis of data associated with a selection of turns conducted during the day’s flying. Turns with a distinct radius, generally through greater than 90° were identified and selected for analysis. Turns that displayed an irregular radius or inconsistent data points were excluded from the analysis. The final group of 19 turns that were analysed included all five turns prior to the accident turn, plus selected turns at various points earlier in the flight. The group also included three turns that met the selection criteria and related to the flight conducted earlier in the day.

Indicative values of DLA’s airspeed, angle of bank and stall margin were derived (Table 1). To facilitate the analysis, it was assumed that each turn was coordinated, at a constant altitude and at a constant speed. The aircraft weight and a wing flap position of 18° were also factored into the analysis.

The ATSB acknowledged the difference between the forecast winds and the local wind conditions observed by the witnesses. However, the analysis assumed nil wind speed as it was not possible to incorporate large changes in aircraft direction in the calculations. In order to assess the aircraft’s performance, it was also necessary to convert the Garmin GPS ground speed data to calibrated airspeed by correcting for density altitude.

Table 1: Flight path data analysis

Time[10]Time to accidentSpeed (kt)[11]Angle of bank (deg)Normal load factor (g)[12]Calculated stall speed (kt)[13]Stall margin (kt)
1053:14[14]5:31:3872411.335517
1101:12145:23:4053331.19521
1119:02145:05:5068341.215216
1421:092:03:4364361.235212
1445:521:39:0061301.165110
1456:201:28:3265421.345411
1544:210:40:3158381.26526
1547:350:37:1757401.30534
1608:070:16:4562321.185012
1610:370:14:1558441.38544
1618:060:06:4669241.094821
1618:480:06:0479461.445524
1620:450:04:0778331.205028
1621:020:03:5069351.235118
1622:520:02:0075311.165025
1623:110:01:4160311.165010
1623:450:01:0757341.20507
1624:170:00:3560311.175010
1624:450:00:0756331.19506

For DLA’s final turn after its last recorded Garmin GPS position at 1624:48, and assuming that the speed of the aircraft did not vary from the previous turn, the analysis indicated that DLA was likely being manoeuvred in a 50° banked turn to the left and was flying at a speed that was very near to the stall speed (Table 2).

In contrast to the other analysed turns, the load factor during the final turn was also found to be the highest and had the lowest stall margin that was demonstrated in the other turns. Had the wind direction and strength been similar to conditions recorded at Canberra Airport the stall margin in the final turn would have been greater.

Table 2: Estimated values for DLA’s speed, bank angle and stall margin during the final turn

Time

 

Time to accidentSpeed (kts)Angle of bank (deg)Normal load factor (g)Calculated stall speed (kts)Stall margin (kts)
1624:500:00:0256[15]50[16]1.5657-1

Operator’s response to the accident

Following the accident, the operator amended their Operations Manual (Training and Checking) to incorporate Threat and Error Management (TEM) and Situational Awareness (SA) training modules as applicable to low-level, powerline survey operations. The amendments enhanced existing topics in the operator’s crew resource management training and stipulated learning outcomes and assessment criteria specific to TEM and SA.

The TEM module was intended to assist pilots and observers with the identification and management of threats associated with:

  • weather
  • operational considerations (including terrain, density altitude and power network complexity)
  • aircraft performance
  • time pressures
  • decision making
  • Go-No Go and escape options.

The SA training aimed to increase the maintenance of situation awareness as it related to the:

  • obstacle environment
  • aircraft performance and energy management
  • speed and manoeuvre management (continual management and monitoring of aircraft attitude, critical airspeeds and balance).

It was intended that the training would be initially delivered to the operator’s Training and Checking pilots who, in turn, would deliver briefings to pilots and observers at a standard equivalent to that of a flight instructor. An additional aircraft handling or ‘fly safe’ check will be conducted on all pilots and observers prior to the start of each powerline survey season.

The operator also provided detail of intended amendments to their low-level procedures to implement an airspeed ‘manoeuvre margin’ that will take in to account the increased stall speed associated with steep turns. The manoeuvre margin will be calculated by the pilot, and independently verified by the observer before each flight as part of the crew’s risk assessment procedure and recorded in the daily operations diary. For the pilot’s and observer’s in-flight reference, the minimum manoeuvre airspeed will be temporarily marked on the airspeed indicator.

Further, the operator plans to modify their aircraft to include an angle of attack indicator and a g‑meter with recording and data download capability. The instruments will supplement the aircraft’s stall warning device by providing additional warning of an impending stall. A record of the maximum and minimum in-flight readings will be downloaded post flight for review by the Chief Pilot.

Other occurrences

Between 2011 and 2021, the ATSB investigated 21 fatal accidents involving piston engine aeroplanes flown in visual meteorological conditions that involved a loss of control and collision with terrain. While none of the 21 accidents involved aircraft engaged in powerline survey work, 11 involved single engine aeroplanes that aerodynamically stalled at a height from which recovery was probably impossible before ground contact.

Safety analysis

Introduction

The pilot and observer onboard VH-DLA (DLA) were conducting powerline survey work to the north of Sutton, New South Wales. Following the completion of two orbits over properties to the east of Tallagandra Lane, the pilot initiated a right turn and tracked to the north‑north‑east. The aircraft was then observed by witnesses to commence a left turn to the north‑west followed by a steep descent and ground impact. Witness observations and wreckage characteristics were consistent with a loss of control and entry into an aerodynamic spin prior to the collision with terrain.

The ATSB found that the pilot was qualified to conduct low-level powerline survey work and was suitably rested to conduct the task. Further, while acknowledging that powerline survey work was more demanding on pilots than other flight activity, there was insufficient evidence to indicate that the sustained workload created a level of fatigue that affected the pilot’s performance.

Site and wreckage examination did not identify any aircraft defects that may have contributed to the accident. This analysis will examine possible reasons for, and the nature of, the manoeuvring that preceded the accident.

Manoeuvre to the north-west

Following the turn to the north-north-east, the pilot would likely have been receiving directions from the observer based on progress of the survey work, which was being monitored with reference to the electrical network distribution map.

The ATSB established that, on completion of the turn, the T-Off immediately to the left of DLA’s track linking a relatively short section of powerline to the north‑west was likely chosen as the next section to be surveyed. The witness reports and flight data indicated that a direct turn towards that T-Off was initiated, rather than the partial orbit advocated by the operator. While the reason for this could not be established, a review of the manoeuvring prior to the accident indicated that partial orbits had been previously used to position the aircraft parallel to other branch lines.

Significantly, the direct turn towards rising terrain probably resulted in a higher bank angle/wing load factor, and therefore a higher stall speed, than aligning the aircraft via a partial orbit.

Loss of control

From the recorded data and witness accounts, DLA transitioned from a level, right turn to the north-north-east into a tighter, possibly climbing, left turn. From the ATSB’s analysis of the turns conducted by the pilot earlier in the flight, it was estimated that the final turn was likely conducted at a comparatively high angle of bank and closer to the stall speed of the aircraft.

As the manoeuvre continued, the aircraft likely exceeded the critical angle of attack for the wing, causing the wing to stall. While no fault was identified with the aircraft’s stall warning system, had the manoeuvring been relatively dynamic, there may only have been a small time interval between the activation of the warning and the actual stall.

Analysis of the recorded flight data identified that the aircraft had been operated relatively close to the stall speed during previous turns without a consequential loss of control. However, from the available evidence it was not possible to determine why control was maintained during those earlier turns.

Following the stall, the aircraft entered a steep, nose down aerodynamic spin that continued until the collision with terrain. The reason for the lower airspeed than used in the majority of the previous turns could not be determined however it may have been the result of deceleration associated with manoeuvring and/or initiation of a climb due to approaching rising terrain. Although the wind appears to have been relatively light, it could also not be ruled out that the aircraft encountered some turbulence in the lee of the rising ground that may have contributed to the accident.

The collision point was to the north-west of DLA’s last recorded flight position and adjacent to the T‑Off. When the aircraft entered the spin, it was significantly below the required height above ground specified by the aircraft manufacturer for recovery from a spin.

Findings

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

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

From the evidence available, the following findings are made with respect to the loss of control and collision with terrain involving Cessna R172K, registered VH-DLA near Sutton, New South Wales on 13 April 2021.

Contributing factors

  • While manoeuvring to align the aircraft to inspect a powerline, control of the aircraft was lost at a height that was insufficient for recovery prior to the collision with terrain.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Airservices Australia
  • Bureau of Meteorology
  • Civil Aviation Safety Authority
  • OzRunways
  • the operator
  • the aircraft manufacturer
  • recorded data from the portable GPS unit in the aircraft
  • a number of witnesses.

References

FAA 2016, Airplane Flying Handbook, FAA-H-8083-3B, U.S. Department of Transportation, OK 73125

Wickens CD & Hollands JG, 2000, Engineering psychology and human performance, 3rd edition, Prentice-Hall International Upper Saddle River, NJ

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:

  • Civil Aviation Safety Authority
  • the operator.

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. Eastern Standard Time (EST): Coordinated Universal Time (UTC) + 10 hours.
  2. GPS: Global Positioning System. A satellite-based radionavigation system.
  3. OzRunways: An electronic flight bag application providing subscriber flight information and navigation service.
  4. 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.
  5. Aerodynamic stall: occurs when airflow separates from the wing’s upper surface and becomes turbulent. A stall occurs at high angles of attack, typically 16⁰ to 18⁰, and results in reduced lift.
  6. Yawing: the motion of an aircraft about its vertical or normal axis
  7. T-Off: A junction in the power line distribution network branching from a main line.
  8. Load factor: the ratio of the aerodynamic force on the aircraft to the gross weight of the aircraft.
  9. METAR: a routine aerodrome weather report issued at routine times, hourly or half-hourly.
  10. Local time at midpoint of turn.
  11. Calibrated airspeed assuming nil wind.
  12. Assumed a steady level coordinated turn,
  13. Calculated from a MTOW, wings level, 18° of flap, stall speed of 50 kt (calibrated airspeed).
  14. Prior flight.
  15. No recorded data. Assumed from previous turn.
  16. Calculated from an assumed arc starting tangential from the last known point to the accident location.

Occurrence summary

Investigation number AO-2021-016
Occurrence date 13/04/2021
Location near Sutton
State New South Wales
Report release date 25/02/2022
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Cessna Aircraft Company
Model R172K
Registration VH-DLA
Serial number R1722809
Aircraft operator Oberon Air Pty Ltd
Sector Piston
Operation type Aerial Work
Departure point Canberra, Australian Capital Territory
Destination Canberra, Australian Capital Territory
Damage Destroyed

Collision with terrain involving Robinson R22 Beta II, VH-HKC, 87 km north of Hughenden Aerodrome, Queensland, on 11 February 2021

Final report

Executive summary

What happened

On the evening of 11 February 2021, the pilot of a Robinson R22 Beta II helicopter, registered VH‑HKC was conducting a private flight near his property,110 km NNW of Hughenden, Queensland. During the flight, the weather conditions in the direction of his return to the homestead deteriorated. While avoiding weather, the pilot landed at an adjacent property to refuel and obtain directions. The pilot however continued flying away from their homestead arriving at another station about 24 minutes later. After refuelling, and 5 minutes prior to last light in dark night conditions, the pilot departed in a northerly direction. When the helicopter became overdue and unable to be contacted, a search for the helicopter was commenced. The following morning, the pilot was found fatally injured and the helicopter destroyed adjacent to an unsealed road 36 km from their Reedy Springs station.

What the ATSB found

The ATSB found that the pilot of VH-HKC, who did not hold a night visual flight rules (VFR) rating, instrument rating or had night flying experience, continued flying towards his destination in a remote area after last light.

Planning, operational and navigational decisions made by the pilot before and during the flight did not adequately address the risk of visual flight into dark night conditions. Notably, the pilot had a number of opportunities to discontinue the flight before last light when he refuelled his helicopter at other stations in the area.

The pilot continued flying through the period of civil twilight into astronomical twilight then, in dark night conditions and without local ground lighting, inadvertently allowed the VFR-only equipped helicopter to descend into terrain.

The ATSB found that the pilot likely navigated at low-level over a sealed road in poor light conditions which likely resulted in the helicopter contacting a powerline. Failure of the powerline resulted in a loss of ground lighting in the direction of flight. Then, shortly after turning onto an unsealed road in overcast, moonless conditions the helicopter departed the road after a bend in the road before flying over open grassland and colliding with trees and terrain in a left bank, nose-down attitude.

Safety message

This accident highlighted the inherent high risk of night flying in remote areas due to the absence or degradation of the visual references for establishing an aircraft’s attitude and position. This risk is increased when night flying is attempted by pilots without night VFR or instrument flying qualifications. To avoid disorientation and the possibility of loss of control of their aircraft, day VFR pilots need to plan to arrive at their destination at least 10 minutes before last light and to have a realistic alternate plan if it becomes apparent that an intended flight cannot be completed in daylight.

The ATSB has previously published material as part of safety publication Avoidable Accidents No 7 - Visual flight at night accidents. The information contained in this document and supporting material is reiterated on release of this report.

The investigation

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

The occurrence

On the morning of the accident, 11 February 2021, the pilot was briefly visited at their Reedy Springs homestead, Queensland, by close family members who were moving cattle by truck to an adjacent property. They advised that they may visit again later during their return journey if time allowed, although stormy weather in the area might prevent this. At 1600 Eastern Standard Time[1] the pilot started getting anxious when his family members had not arrived at the station as expected.

Departure from Reedy Springs Station

The weather in the area was reported as overcast with occasional showers. At 1715, during a clearing in the weather, the pilot departed the homestead in their Robinson R22 Beta II helicopter, VH-HKC, to search in an area near Cargoon Station, about 23 km east of the Reedy Springs homestead. The pilot was reported as leaving the homestead in a hurry.

Flight to Camden Park Station

At 1827, VH-HKC arrived at Camden Park Station, which is 35 km west-south-west of Cargoon and 18 km south-west of Reedy Springs.

On arrival at Camden Park Station, the pilot flew at low level over the entrance road towards the homestead, landing beneath a powerline (Figure 1). The pilot advised the owner he was lost, looking for Reedy Springs and that the helicopter’s low fuel[2] light was on.

Figure 1: Photo from 1829 EST - VH-HKC and pilot following arrival at Camden Park Station, property powerline indicated and southerly cloud conditions visible

Figure 1: Photo from 1829 EST - VH-HKC and pilot following arrival at Camden Park Station, property powerline indicated and southerly cloud conditions visible

Source: Camden Park Station owner, modified by the ATSB

The owner of Camden Park assisted the pilot to refuel the helicopter to full and provided directions for return to Reedy Springs to the north. The pilot appeared confused, disoriented and ‘bushed’ and appeared to not believe the directions provided. The owner offered to contact the pilot’s son at Pretty Plains Station[3] to confirm the directions, the pilot responded that he would be fine and not to worry about it. The helicopter departed Camden Park at about 1835 and headed south towards Hughenden, the direction described as a line of dark, low cloud by the Camden Park owner (Figure 1). Following VH-HKC’s departure the owner rang both the pilot’s spouse at Reedy Springs and a son who lived at Pretty Plains advising of the situation. The son, also a Robinson R22 pilot advised they couldn’t depart to try to find their father since it was raining at Pretty Plains (Figure 2).

Flight to Wongalee Station

At 1910, VH-HKC arrived at Wongalee[4] Station about 61 km south of Camden Park. The average ground speed in a direct line from Camden Park was calculated to be about 58 kt (106 km/h). The pilot spoke to a building contractor working at the property saying he had been avoiding storms and landing at stations. The pilot asked the contractor if it was Wongalee Station. When confirmed, the pilot flew to the hangar and was assisted to refuel the helicopter.[5] The contractor, unaware of the pilot’s intended destination, offered the pilot a meal and overnight accommodation. The pilot declined. The contractor observed that the pilot was disoriented although not anxious. At about 1920, after refuelling, VH-HKC departed Wongalee to the north in the direction of a storm (Figure 2).

Figure 2: VH-HKC accident flight - known locations and general direction of travel

Figure 2: VH-HKC accident flight - known locations and general direction of travel

Source: Google Earth, modified by the ATSB

Flight over Kennedy Developmental Road – Collision with powerline

Kennedy Developmental Road (Highway 62) was a remote unlit road heading north from Wongalee Station (Figure 2), recently sealed with side and centreline markings (Figure 3). The road was described by the contractor at Wongalee Station as not a busy road. The road was unlit.

Ergon Energy reported that at about 1954 EST, a high voltage powerline,[6] strung 6.8 m above the Kennedy Developmental Road (KDR), [7] 68 km north of Wongalee Station by road, was tripped. The poles supporting the wire on either side of the road were found bent towards the north and inwards with the easterly pole snapped near the base. The 3-strand single wire was broken directly above the road (Figure 3). The break in the line resulted in loss of power  to nearby Mount Sturgeon and Pretty Plains Stations. This meant exterior and station lighting in the area was then not available to assist the pilot of VH-HKC.

Based on the nature and location of the wirestrike and accident location it was very likely that the pilot was initially flying above the sealed Kennedy Developmental Road (marked with a centreline and sidelines) then the unsealed Pretty Plains to Camden Park Road and using these roads for navigation to his intended destination. Both of these roads were in a remote rural area and not illuminated by street lighting.

Figure 3: Powerline above the Kennedy Developmental Road showing location of break and direction of supporting pole movement

Figure 3: Powerline above the Kennedy Developmental Road showing location of break and direction of supporting pole movement

Source: Queensland Police Service, modified by ATSB

Search and rescue - Collision with terrain

When VH-HKC did not arrive at Pretty Plains or Reedy Springs that evening, search and rescue authorities were alerted. The helicopter was located the following morning, 8 km north-east of the broken powerline and 160 m south of the unsealed Pretty Plains Camden Park Road (Figure 4). This location was 11 km by road from the powerline break and 4.5 km west of the Pretty Plains homestead. The pilot was fatally injured and the helicopter was destroyed.

Figure 4: Aerial view of accident site showing Pretty Plains Camden Park Road

Figure 4: Aerial view of accident site showing Pretty Plains Camden Park Road

Source: Queensland Police Service, modified by ATSB

Context

Pilot information

Qualifications and experience

The flight was conducted as a private category operation under the visual flight rules (VFR).[8] The pilot held a Civil Aviation Safety Authority (CASA) Private Pilot Licence (Aeroplane) that was first issued in 1960. This license was converted to Part 61 on 29 January 2020. The pilot was not rated for instrument flying or night VFR operations.

The pilot’s family reported that he had undertaken pre-license helicopter training in Cairns many years ago, however, the pilot’s license was not endorsed for helicopter operations.

The pilot had owned and operated two helicopters and had been flying helicopters for over 40 years. As the sole owner and pilot of VH-HKC, he had accrued flying time of 1,870.2 hours since 2006.

Recent history

The pilot flew VH-HKC almost exclusively over his Reedy Springs property using the helicopter for mustering cattle, attending to fences and water infrastructure maintenance. The only time the pilot left the property was for helicopter maintenance at Charters Towers.

Medical information

The pilot held a Class 2 medical valid until 19 July 2021, and his most recent aviation medical examination was on 15 July 2019. Restrictions on the certificate were for distance vision correction to be worn and reading correction to be available.

The pilot was described as a very fit and aware 82-year-old. The pilot had well-managed Crohn’s disease and had recently developed asthma following a chest infection. The pilot used medication for treatment of the condition as well as an asthma reliever and preventer.

The witness at Wongalee Station observed the pilot as ‘not puffing or panting’ on the day of the accident. The pilot’s glasses and a Ventolin (asthma) inhaler were located at the accident site.

The pilot’s autopsy identified that salbutamol (Ventolin) was not detected in the toxicology examination. In response to a suggestion that the pilot may have suffered an asthma attack prior to the accident the autopsy reported ‘there were…no features that could confirm a serious acute exacerbation of asthma.’

In response to a concern on whether a recent head injury whilst shopping in Charters Towers (described below) potentially contributed to the circumstances of his death, it was reported that ‘there were no features of significant recent (pre-crash) head injury identified at autopsy, although…difficult to completely exclude subtle pre-existing head injury’.

Events prior to the accident flight

In the two weeks leading up to the accident the pilot was in Townsville, Queensland. On 10 February 2021, the day before the accident, the pilot travelled about 350 km by road from Townsville to his homestead at Reedy Springs cattle station. During the journey, the pilot visited a Charters Towers hardware store. At about 1342, closed circuit television video footage recorded the pilot falling backwards to the ground when attempting to dismount from the tray of a utility vehicle. The pilot stood up from the fall within 10 seconds, before briefly talking to another customer and driving from the carpark. The pilot arrived at Reedy Springs at 1600 and reported he had lost balance on the utility vehicle and fell backwards onto concrete. He reported hitting the back of his head on the tyre of an adjacent vehicle in the carpark but did not have a lump on their head. After unpacking the vehicle, the pilot had a 30-minute rest before dinner at 1900. The pilot retired at about 2130 and had a normal night’s sleep.

On the day of the accident, the pilot woke about 0600 and then had a normal day, working around the Reedy Springs homestead eating both morning tea and lunch.  

Aircraft information

VH-HKC was a Robinson R22 Beta II helicopter manufactured in the USA in August 2004. Initial registration of VH-HKC to the pilot was effective from February 2006. At the time of the accident, the helicopter had completed 1870.2 hours in service, and was certified for day VFR flight only. The last 100-hourly inspection was completed on 3 December 2020 at 1858.9 hrs, 11.3 hours prior to the accident, with all maintenance requirements completed.

The helicopter was equipped with two landing lights installed in the nose of the aircraft just below the canopy, and UHF/ VHF radios. In addition, it had an inertia reel lap/sash restraint fitted to the only installed seat.[9] R22 helicopters are not fitted with a wire strike protection system (cable cutter) on the front of the helicopter.

Recorded information

No flight plan was submitted by the pilot. VH-HKC was not visible on recorded radar data and no communications from the helicopter were recorded by Airservices Australia. The aircraft had no onboard recording equipment. The pilot carried a satellite phone and a dual frequency (406/121.5 MHz) personal locator beacon on the aircraft. Neither of these communication devices were activated.

Accident site information

The ATSB did not attend the accident site. The following is based on an assessment of accident site photos and statements provided by Queensland Police Service.

The area near the accident site was open grassland and grassland with trees. The initial impact point was coincident with the tree line at the edge of an open grassy area about 160 m south of the unsealed Pretty Plains Camden Park Road. The site was 4.5 km west of the Pretty Plains Homestead. The wreckage trail extended in a south-westerly direction of over an area of about 50 m long and 20 m wide.

Figure 5: Overview of VH-HKC accident site

Figure 5: Overview of VH-HKC accident site

Source: Queensland Police Service, modified by ATSB

Both landing gear skid tubes were broken off at the initial impact point just prior to the main cabin impact crater evident in the soft ground (Figure 5), with main rotor blade strikes forward and to the left of the area of impact. The impact captured the airspeed indication at 38 kt (70 km/h) and the vertical speed indication at -870 ft/min (-16 km/h). This correlated to a flight path angle of 13 degrees nose-down with a groundspeed of 37 kt (68 km/h).

Figure 6: Initial impact location

Figure 6: Initial impact location

Source: Queensland Police Service, modified by ATSB

The tail rotor gearbox, blades and empennage were located close to the initial impact. The remainder of the tail boom remained attached to the main fuselage which was 27 m further along the wreckage trail (Figure 5 and Figure 6). The engine was located at the end of the wreckage trail (Figure 6).

Figure 7: Overview of accident site

Figure 7: Overview of accident site

Source: Queensland Police Service, modified by ATSB

One main rotor blade separated during the impact sequence; the other blade remained attached to the hub at the main wreckage. Both blades were deformed in a manner indicative of powered rotation on impact. The wreckage trail and damage pattern were consistent with a high-energy nose-down impact, likely in a left skid-low attitude.

The front landing skid cross tube and shattered Perspex canopy, both of which are common wirestrike locations, were unable to be examined for evidence of a wirestrike.

R22 Wirestrike collisions

A review of the ATSB occurrence database showed a number of occurrences where a Robinson R22 helicopter had contacted a powerline that did not result in damage or collision with terrain. Of these occurrences, 22% resulted in nil or minor damage to the helicopter and the pilot was able to continue with no loss of control.

Weather and environmental information

Storms

Witnesses at Reedy Springs, Camden Park and Wongalee Stations reported storms and rain in the area during the time of the flights. An image taken at 1756 at Camden Park (Figure 8) captured the prevailing conditions.

Figure 8: Image taken at Camden Park and captioned ‘Another storm is coming’ sent via WhatsApp at 1756 EST about 30 minutes before VH-HKC arrival at Camden Park

Figure 8: Image taken at Camden Park and captioned ‘Another storm is coming’ sent via WhatsApp at 1756 EST about 30 minutes before VH-HKC arrival at Camden Park

Source: Camden Park Station owner

The storm clouds to the south were evident at the time of the pilot’s arrival at Camden Park (Figure 1). The pilot reported to at least one witness that they had been avoiding storms. The Bureau of Meteorology satellite infrared imagery shows the presence of clouds and storms in the area of the route taken by the pilot (Figure 9). The white and purple-blue colours in Figure 9 represent a scale of cloud-top temperatures. The colder the cloud-tops, the higher they are.[10] The red and orange patches in Figure 9 were overlaid lightning strike data.[11] The image indicated that there was lightning in the discrete storm cells over Northern Queensland in the vicinity of VH-HKC and also showed the purple colour relating to the very high cumulonimbus cloud tops associated with the storms.

Figure 9: Satellite Infrared imagery[12] at 1830 showing extent of clouds and storms in the area visited by VH-HKC

Figure 9: Satellite Infrared imagery[12] at 1830 showing extent of clouds and storms in the area visited by VH-HKC

Source: Bureau of Meteorology, modified by the ATSB

Light conditions[13]

On 11 Feb 2021 the moon phase at Wongalee Station was a waning crescent with 1% of the moon's visible disk illuminated. Moonset was at 1851 and sunset was at 1902.[14] For aviation purposes, night is defined as the period of darkness commencing at the ‘end of evening civil twilight’,[15] also known as last light. The pilot landed at Wongalee Station at 1910, 15 minutes prior to last light.[16] VH-HKC departed Wongalee at 1920 EST during the period of civil twilight, about 5 minutes prior to last light (Figure 10).

Figure 10: Regions of twilight relative to VH-HKC location at Wongalee Station 1920 EST

Figure 10: Regions of twilight relative to VH-HKC location at Wongalee Station 1920 EST

Source: in-thy-sky.org/twilghtmap

The end of evening nautical twilight[17] was 1951. At this time, it was dark. Both the collision with the powerline on Kennedy Developmental Road and collision with terrain adjacent to the Pretty Plains Camden Park Road occurred in the period of astronomical twilight[18] (Figure 11).

Figure 11: Regions of twilight relative to VH-HKC accident location at 2000 EST

Source:in-thy-sky.org/twilghtmap

The flight involving the collisions was conducted during astronomical twilight, moonless and in overcast conditions (no starlight) in a remote area with limited terrestrial lighting. This was considered to be a dark night with minimal light available. The collision with the powerline exacerbated the situation by extinguishing the Pretty Plains Station terrestrial lighting in the direction of travel.

Visual flight rules requirements

A VFR flight must not be conducted at night, unless the pilot in command is authorised under CASR Part 61 to conduct a flight under the instrument flight rules (IFR) or at night under the VFR and the aircraft is appropriately equipped for flight at night or under the IFR.,..[19],[20] A pilot who does not hold a night visual flight rules rating or an instrument rating must not depart unless the estimated arrival time for the destination (or alternate) is at least 10 minutes before last light allowing for any required holding. [21]

Risks of flying in areas of reduced visual cues

Night flying in remote areas is an inherently high-risk operation due to the absence or degradation of the visual references for establishing an aircraft’s attitude and position. This risk is increased to unacceptable levels when night flying is attempted by pilots without night VFR or instrument flying qualifications.

The attempt to continue to the intended destination in fading or absence of daylight in this case, might have been reinforced by the availability of a well-marked but unlit road that could to some extent compensate for the navigational difficulties usually associated with degraded visibility. The pilot reportedly did not have any previous night flying experience.

The ATSB has previously highlighted the risk associated with VFR flight in dark environmental conditions. The ATSB Avoidable accidents booklet, ‘Visual flight at night accidents: What you can’t see can still hurt you’ (AR-2012-122) describes that on average between 1993 and 2012, there were nearly two accidents per year as a result of visual flight at night. Importantly, accidents at night tend to be unforgiving, with 75% of these accidents resulting in fatal outcomes. For the accidents during night visual conditions, half involved a loss of aircraft control, most likely due to the influence of perceptual illusions caused by the lack of visual cues. The other half involved controlled flight into terrain, where the pilot probably did not know of the terrain’s proximity immediately before impact. Nearly all of these accidents occurred on dark nights.

Similar occurrences

AO-2011-087

On the evening of 27 July 2011, the owner-pilot of a Robinson R22 helicopter was conducting a local flight from Big Rock Dam to Brooking Springs homestead near Fitzroy Crossing, Western Australia. The pilot was reported missing and the wreckage of the helicopter was located the following day, 14 km north-west of Fitzroy Crossing township. The helicopter was seriously damaged and the pilot sustained fatal injuries.

The pilot was attempting to fly visually at low level on a dark night in an area that did not contain any local ground lighting. About halfway into the flight, the pilot inadvertently allowed the helicopter to develop a high rate of descent, resulting in a collision with terrain.

The ATSB investigation found that the pilot was operating at night without the appropriate training or qualification in a helicopter that was not suitably equipped. An examination of the helicopter found no evidence of any pre-existent defects or anomalies.

AO-2014-144

On the afternoon of 25 August 2014, the pilots of two Robinson R22 helicopters were ferrying the helicopters from Yeeda to Springvale via a refuelling stop at Leopold Downs, within the Kimberley region of Western Australia. The pilot who was ahead by about 10 NM (18 km) arrived at Springvale about 40 minutes after last light but the pilot of the second helicopter did not arrive as expected.

A search using helicopters began early the next morning and the overdue helicopter was found in a seriously damaged state, close to the intended track and 25 NM (46 km) west of Springvale. The pilot had been fatally injured.

The ATSB found that the pilot, who did not hold a night visual flight rules (VFR) rating or instrument rating, continued flying towards the destination after last light (end of civil twilight), then in dark night conditions without local ground lighting, inadvertently allowed the helicopter to descend into terrain.

AO-2016-031

On 7 April 2016, the pilots of two Robinson R22 helicopters flew from Mossman, Queensland to various fishing locations to the north with a passenger in each helicopter. Late in the afternoon, the pilots commenced the direct return flight to Mossman. However, the pilots encountered weather and winds that slowed their progress and required them to refuel at Cooktown.

The pilots departed Cooktown at last light intending to track via the coast to Mossman. As the flights progressed, the light available from the sun continued to decrease and there was no moon. There were also patches of cloud and rain in the general area.

Shortly after passing Cape Tribulation, in dark night conditions, one of the helicopters collided with the sea. The passenger was injured in the accident but was able to reach the shore and notify emergency services. Unaware of the accident, the occupants of the other helicopter continued to Mossman. A search was initiated and the missing helicopter was located on 9 April 2016 in about 400 m offshore in about 10 m of water. The pilot was not located.

The ATSB found that the pilot, who was only qualified to operate in day-VFR conditions, departed on a night flight and continued towards the destination in deteriorating visibility until inadvertently allowing the helicopter to descend into water.

These fatal collisions all involved pilots of R22 helicopters attempting to fly visually at low-level on dark nights in areas that did not contain any local ground lighting.

Safety analysis

The speed of the impact in a nose-down, left-skid-low attitude indicated that the pilot collided with terrain with substantial energy. This, along with the helicopter rotor damage, were consistent with delivery of engine power to the rotors and at least some control. The following analysis examines the circumstances of the occurrence to identify the contributing factors and any safety implications.

Flying at low-level and collisions

Powerline

The timing and physical appearance of the severed powerline on the Kennedy Development Road was consistent with contact with the helicopter. The distance from Wongalee Station to the severed powerline along the Kennedy Development Road was about 68 km, which was consistent with a speed of about 64 kt (119 km/h) had the pilot been following the road. It was likely that in the dark conditions, the pilot navigated by following the road centreline illuminated by the helicopter’s landing lights.

Assuming the pilot was aware he had flown through a powerline, it should have served as an additional warning that he was flying with reduced visibility and risked a collision with terrain at this time.

Terrain

VH-HKC collided with terrain after departing from flight shortly after a bend above the unsealed and unmarked Pretty Plains Camden Park Rd. The pilot was almost certainly using this road for navigation. In the absence of ground lighting and a poor reflective surface after leaving the road, therefore losing his visual reference, the pilot left the SE heading road and flew at low-level over open grassland in a SE direction with a line of trees to the left until inadvertently descending into terrain at a speed of about 37 kt on a flight path angle of about 13 degrees nose down. The collision occurred at about 2000 EST which was in the period of astronomical twilight (after dark).

Operation at night

The pilot’s family advised that the pilot avoided flying at night and predominantly only flew over their own property. CASA flight crew licensing information showed that the pilot did not hold a night VFR or instrument rating. The logbook for VH-HKC confirmed that the helicopter was not certified for instrument flight rule (IFR) or night VFR operations and was not equipped with suitable instruments for this type of operation.

Within 5 minutes of departure from Wongalee, the pilot was flying at night, with no illumination being provided by the moon or stars. There was very minimal terrestrial lighting with the roads unlit and homesteads sparsely located. The remote Kennedy Development Road carries a low level of traffic. A collision with a powerline over the road occurred 29 minutes after last light (1954) and the collision with terrain about 35 minutes after last light (2000). In such conditions and in particular after the loss of power to local stations as a result of the cut powerline, the available visual references for establishing an aircraft’s attitude and position were degraded or absent.

The conditions on 11 February 2021 were particularly dark after departure from Wongalee Station. It was after moonset and sunset with the moon only 1% illuminated and in overcast weather. The flight after this time continued through the entire periods of civil and nautical twilight.

In very dark conditions such as rural areas, the skills needed to fly an aircraft at night are vastly different to day VFR flights, and may even exceed the capabilities of some pilots trained in night VFR operations.

Pilot’s operational decision making and opportunities to discontinue flight

The pilot did not assess that weather conditions in the vicinity of Reedy Springs and Cargoon were unsuitable for flight in a helicopter only equipped for flight under the visual flight rules (VFR). The pilot’s decision to depart Reedy Springs during a clearing in the weather was made in a hurry and without consideration of an alternate plan. The pilot subsequently became lost and close to fuel exhaustion before flying at low-level under powerlines at Camden Park Station.

The pilot did not consider suggestions at both Camden Park and Wongalee stations to discontinue his flight. Despite arriving at the familiar Wongalee Station within the prescribed 15 minutes before last light, the pilot elected to continue to his destination, likely by navigating at low-level, using a sealed highway. The pilot continued flying despite colliding with a powerline above the highway and flying into the night in dark conditions without the assistance of ground lighting.

The pilot also had opportunities to land the helicopter at a safe location and communicate by satellite phone or activate the personal locator beacon to obtain assistance.

The decisions that the pilot made both before departing Reedy Springs and during the flight both at Camden Park and Wongalee Station, including importantly, the decision to continue towards his destination despite offers of accommodation and attempts at discouraging continuing flight resulted in the pilot flying in dark night conditions where the eventual collision with terrain would have been difficult to avoid.

No helicopter endorsement

CASA flight crew licensing information indicated that the pilot’s license was not endorsed for helicopters. The pilot had considerable experience flying helicopters over many years but predominantly over his own familiar property during day visual meteorological conditions. At the time of the accident the pilot was operating outside the regulations without a helicopter endorsement and in night conditions.

Findings

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

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

From the evidence available, the following findings are made with respect to the collision with terrain in dark night conditions involving Robinson R22 Beta II helicopter, registered VH-HKC, which occurred 87 km north of Hughenden, Queensland on 11 February 2021. The findings should not be read as apportioning blame or liability to any particular organisation or individual.

Contributing factors

  • While attempting to fly visually at low level, on a dark night without local ground lighting, the pilot inadvertently allowed the helicopter to descend, resulting in a collision with terrain.
  • The pilot was operating at night without the appropriate night flying qualification or experience, in a helicopter that was not suitably equipped for night operations.
  • The pilot continued flying towards the intended destination after last light (end of civil twilight), then in dark night conditions without local ground lighting despite opportunities available to discontinue the flight.

Other factors that increased risk

  • The pilot made a decision to depart on the flight without prior planning. A number of operational and navigational decisions made by the pilot during the flight did not adequately address the risk of visual flight into dark night conditions.
  • It was very likely that the helicopter struck a powerline above the Kennedy Developmental Road while flying at low-level in poor light.

Other (key) findings

  • The pilot held a private pilot's license for aeroplane operations, however, was not endorsed for helicopter operations.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • Civil Aviation Safety Authority
  • Queensland Police Service (Hughenden Police and Townsville Forensic Crash Unit)
  • the next-of-kin of the pilot
  • witnesses from Camden Park and Wongalee Stations, Queensland
  • Ergon Energy, Queensland
  • the maintainer of VH-HKC
  • Robinson helicopters

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:

  • Civil Aviation Safety Authority
  • Queensland Police Service (Hughenden Police and Townsville Forensic Crash Unit)
  • the next-of-kin of the pilot
  • witnesses from Camden Park and Wongalee Stations, Queensland
  • Ergon Energy, Queensland

Submissions were received from;

  • Civil Aviation Safety Authority
  • Queensland Police Service (Hughenden Police and Townsville Forensic Crash Unit)

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

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2023

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

[1]     Eastern Standard Time (EST) was Coordinated Universal Time (UTC) + 10 Hours

[2]     The low fuel light illuminated when there was10 litres of fuel remaining

[3]     Pretty Plains Station was the residence of a son of the pilot

[4]     Wongalee Station, subject to building works at the time of the accident was the residence of another son of the pilot

[5]     This required 15-20 litres of Avgas to fill the tanks which was done with the engine running

[6]     The tripped powerline was a 19.1 kV single-wire earth return (SWER) transmission line supplying single-phase electrical power to homesteads in the area including Mt Sturgeon, Pretty Plains and Camden Park Stations. This event was recorded and reported by Ergon Energy

[7]     Locally known as Hann Highway with sealing and line marking of the road (from The Lynd to Hughenden) completed in 2017 under the Federal Government Northern Australia Roads Program

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

[9]     The other seat had been removed from the aircraft by the pilot.

[10]    The following scale is used for the IR imagery (purple=coldest, dark grey=warmest).

[11]    The red patches represent lightning strikes which occurred in the 10 minutes prior to the image time, and the orange dots for strikes recorded in the period 10 to 30 minutes prior to the image.

[12]    Reedy Springs (R) Wongalee (W) Hughenden (H) and Mt Sturgeon (S) marked on map. Location of VH-HKC at time of image denoted by the helicopter icon.

[13]    Geoscience Australia maintains sunrise, sunset and twilight times and moon/ sun elevation angle on their website at Astronomical Information | Geoscience Australia (ga.gov.au) with a link to the United States Naval Observatory for moon phase data.

[14]    Sunset is defined 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.

[15]    When the sun is 6° below an ideal horizon. At this time, in the absence of moonlight, artificial lighting or adverse meteorological conditions, the illumination is such that large objects can be seen but no detail is discernible.

[16]    Last light at Wongalee Station on 11 Feb 2021 was 1925.

[17]    When the sun is 12° below an ideal horizon. At this time in the absence of moonlight, artificial lighting or adverse atmospheric conditions, it is dark for normal practical purposes.

[18]    When the sun is 18°below an ideal horizon. At this time the illumination due to scattered light from the Sun is less than that from starlight and other natural light sources in the sky.

[19]    Aeronautical Information Publication Enroute 1.2 Visual Flight Rules 28 Feb 2019.

[20]    Night means the period between the end of evening civil twilight and the beginning of the following morning civil twilight.

[21]    Aeronautical Information Publication Enroute 1.2 Visual Flight Rules 28 Feb 2019.

Occurrence summary

Investigation number AO-2021-006
Occurrence date 11/02/2021
Location 87 km north of Hughenden Aerodrome
State Queensland
Report release date 09/02/2023
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
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-HKC
Serial number 3666
Sector Helicopter
Operation type Private
Departure point Wongalee Station, Qld
Destination Reedy Springs Station, Qld
Damage Destroyed

Loss of control and collision with terrain involving DJI Inspire 2, remotely piloted aircraft, Darling Harbour, Sydney, New South Wales, on 15 January 2021

Final report

Safety summary

What happened

On the morning of 15 January 2021, a DJI Inspire 2 remotely piloted aircraft (RPA) was being used for aerial photography and videography above Cockle Bay in Darling Harbour, Sydney. A short time after take-off the RPA unexpectedly accelerated away from the pilot. The pilot attempted to control the RPA and arrest its movement however, the aircraft was unresponsive to control inputs. The aircraft continued to accelerate to its maximum speed while flying away from the operator and towards nearby buildings. A short time later the RPA struck, and shattered, the window of a hotel adjacent to Darling Harbour. An occupant of the hotel received minor injuries from flying glass and the RPA was destroyed.

What the ATSB found

The ATSB found that shortly after take-off for the second flight of the day, the compass on the RPA failed due to electromagnetic interference. This resulted in the aircraft becoming unresponsive to control inputs leading to the collision with a building. Although not triggered in this occurrence, the failure of the compass also disabled the Failsafe return to home function. Thus, the failure of the compass had the two-fold effect of rendering the aircraft uncontrollable while simultaneously disabling the failsafe designed to prevent a fly away occurrence. 

Although not contributory to this occurrence, the ATSB also found the pilot did not follow the operator’s emergency procedures or comply with the regulators operational permissions to fly in restricted airspace.

What has been done as a result

Following a review of this occurrence, the manufacturer updated the user manuals of a number of products, including the Inspire 2. These changes provide additional guidance to users regarding the use of the fully manual attitude flight mode in the event of compass interference.

Safety message

While the reliability of Remotely Piloted Aircraft (RPA’s) is generally high, they are not infallible. Occurrences reported to the ATSB indicate that RPA fly-away occurrences are not rare. It is therefore important that pilots ensure they are familiar with and well drilled in emergency procedures, as well as being proficient in flying in all flight modes. In the case of an RPA fly‑away, whether it be due to a compass failure or loss of signal, there may only be a few seconds in which a pilot can take avoiding action. In the event of a compass failure, switching to the fully manual attitude flight mode may assist regaining control of the RPAS. Whereas, following a loss of signal to the RPA, the last remaining risk control to prevent a fly away are built-in design features such as the Failsafe Return to Home.

Remote pilots are also reminded that adhering to operational guidelines and limitations remains important for ensuring the safe operation of RPAs. This is particularly true in populated areas, where risks are potentially elevated. Adhering to the limitations and guidance provided by the regulator will ensure these risks remain as low as reasonably practicable.

The occurrence

On the morning of 15 January 2021, the pilot of a DJI Inspire 2 remotely piloted aircraft (RPA) arrived at Darling Harbour, New South Wales (Figure 1) for the commencement of aerial work operations. The operator had been contracted to conduct aerial photography and videography in the Cockle Bay area within Darling Harbour.

Figure 1: Accident location

ao-2021-001-pic-1.jpg

Source: Google Earth, annotated by ATSB

After being advised by the client that the subject was ready, the pilot set-up the RPA on the Cockle Bay marina (Figure 2) and conducted pre-flight checks. Pre-flight checks included checking for software updates, ensuring that GPS satellites were acquired, and checking the home point was set to the take-off location. It was reported that the first flight of the day commenced at about 1030 Eastern Daylight‑save Time[1] and lasted about 20 minutes.

Photographs and video of the subject were captured, and the RPA returned for an uneventful landing. The client advised that there would be an hour before the subject would be ready again, so the RPA was packed away. After receiving advice from the client advised that the subject would shorty be ready for photography, the RPA was once again set up. Fully‑charged batteries were installed, and the pre-flight checks were again conducted.

Figure 2: Area of operations

ao-2021-001-pic-2.jpg

Source: Google Earth, annotated by ATSB

The second flight for the day was reported to have commenced at about 1145. The pilot reported taking-off the RPA and climbing to about 10 m. During this time the RPA’s retractable legs were raised. The pilot recalled pitching the RPA towards the subject and within about 5 m of travel the RPA had pitched over to about 30°‑ 40° and accelerated quickly. The pilot realised the behaviour of the RPA was abnormal and attempted to control the RPAS and stop it pitching however the control inputs from the pilot had no effect on the RPA and it continued to accelerate in the same direction.

The pilot reported that when the RPA was about 30 m away the screen on the transmitter froze then subsequently went black. As the RPA continued to fly away the pilot lost sight of it. Having realised the RPA had flown away, the pilot made phone calls to report the matter to the operator’s chief pilot and chief executive officer. The pilot then initiated a search for the RPA and was subsequently notified by the company’s chief pilot that the aircraft had collided with a hotel on the far (western) side of Darling Drive. The pilot proceeded to the hotel to brief hotel staff and New South Wales Police Force officers, before returning to Darling Harbour to complete the job using a back-up RPA.

__________

  1. Eastern Daylight saving Time (EDT): Coordinated Universal Time (UTC) + 11 hrs.

Context

Aircraft details

General details

The Remotely piloted Aircraft (RPA) was a SZ Da-Jiang Innovations (DJI) Technology Co Ltd Inspire 2 (Figure 3).

Figure 3: DJI Inspire 2, shown in landing configuration

ao-2021-001-pic-3.jpg

Source: DJI

The Inspire 2 is part of DJI’s professional product line and is designed for aerial photography and cinematography. The aircraft is a quadcopter measuring 42.7 cm in length, 31.7 cm in height and 42.5 cm in width (without propellers). The aircraft is constructed with a magnesium aluminium composite shell and carbon fibre arms holding the motors and landing struts. During flight these arms are raised to allow unobstructed viewing from the camera suspended by the gimbal below the aircraft. With both batteries and all four propellers (but without the gimbal or camera) the Inspire 2 weights 3.44 kg and it has a maximum take-off weight is 4.25 kg. The Inspire 2 has a maximum flight time of between 23 and 27 minutes, depending on the payload, and has a maximum speed of 94 km/h.

Flight sensors

The inspire 2 was fitted with a Vision System and Infrared[2] Sensing System. The Vision System consisted of two forward facing optical sensors and two downward facing ultrasonic sensors. The Infrared Sensing System comprised two upwards facing infrared sensors. These systems were utilised in certain flight modes (see the Flight modes section) for positioning and obstacle avoidance. The Assisted Braking from Obstacle Sensing function used these sensors to actively aerodynamically brake when obstacles were detected around the aircraft. However, this function was only effective at aircraft speeds up to 50 km/h.

Flight modes

The Inspire 2 could be flown in three different flight modes, P-mode (Positioning), A-mode (Attitude), and S-mode (Sport).

P-mode was the most automated of the three modes. In this mode the Global Positioning System (GPS), as well as the anti-collision sensors, were used to assist stability and navigation. This mode also made use of the aircraft’s failsafe features (detailed in the following section).

S-mode maximised the aircraft’s agility and speed while still using GPS for positioning. In this mode a number of the aircraft’s safety features, such as the forward and downward vision systems, were disabled. As a result, the ability for the aircraft to sense and avoid obstacles was not available in S-mode.

A-mode was effectively a fully manual mode that could be used when neither the GPS nor the Vision System were available. In this mode the aircraft could not position or auto brake and, due to the lack of GPS positioning, the aircraft’s position was also affected by wind. The manual stated that the aircraft would switch into A-mode in the following two instances:

Passive: When there is weak GPS signal or when the compass experienced interference where the Vision System is unavailable.

Active: Users toggle the flight mode switch to A-mode.

The pilot reported normally using P-mode, including on the day of the occurrence.  

Return to Home function

The Inspire 2 had three types of return to home (RTH) functions that could return the aircraft back to the last recorded home point; Smart RTH, Low Battery RTH and Failsafe RTH.

  • Smart RTH could be activated by either using the RTH button on the remote controller or taping the RTH button in the DJI GO 4 application.
  • Low battery RTH would be automatically activated when the batteries are depleted to a point that may affect the safe return of the aircraft.
  • The Failsafe RTH was designed to automatically return the aircraft to its home point in the event of a loss of controller signal. For this feature to work the home point was required to be set and the compass functioning normally. If these conditions were met, the Failsafe RTH would activate if the controller signal was lost for more than 3 seconds.
Compass

The Inspire 2 was fitted with a single magnetic field sensor compass. The compass fed data to the Internal Measurement Unit (IMU), which was used for flight control.

Wreckage and accident site information

The aircraft struck a window of a hotel on the western side of Darling Drive. The impact site was approximately 330 m from the take-off location. The impact of the aircraft shattered the window, causing an ingress of glass into the room however, the aircraft did not penetrate the window.

The sole occupant of the room sustained minor injuries from the flying glass and the aircraft was destroyed, coming to rest on a balcony below the window. The glass used in the window was 10.38 mm bronze‑laminated glass, compliant with Australian Standard 1288.

Meteorological information

The pilot reported that the weather on the day was fine for RPA flying. That assessment was consistent with Bureau of Meteorology observations which, at 0900, indicated that the temperature was 21.9 °C with 80 per cent relative humidity and no rain. The wind speed was observed at Fort Denison (3 km north‑east of Darling Harbour) at 15 km/h from the south-south-west.

Additional information

Recorded flight data

Flight data logs were recovered from the RPA transmitter by the operator and supplied to the ATSB. Flight data logs were also recovered from a Secure Digital (SD) card mounted on-board the aircraft. Data from the penultimate flight (Figure 4) showed that the aircraft commenced the flight at 1048 from the Cockle Bay Marina and climbed to about 24 m above ground level (AGL).

Figure 4: Recorded flight data for the penultimate flight

ao-2021-001-pic-4.jpg

Source: Google Earth, annotated by ATSB

The aircraft was then manoeuvred within Cockle Bay before rising to 70 m (230 ft) AGL at the northern end of the bay. The aircraft was then flown over shore to a position above the Harbourside shopping mall before descending for landing at the take-off location. The flight time for the first flight was just over 17 minutes.

Data recorded from the incident flight is shown in Figure 5. Data recovered from the controller (shown in green in Figure 5) showed the aircraft taking off at 1140, again from the Cockle Bay Marina and initially climbing to about 20 m AGL.

Figure 5: Recorded flight data of the incident flight

ao-2021-001-pic-5.jpg

Source: Google Earth, annotated by ATSB

The aircraft then proceeded in a westerly direction towards the centre of Cockle Bay. Within about 8 seconds of take-off, and having only traversed about 5 m, the aircraft’s pitch increased to about 24° nose down and the aircraft quickly accelerated. The direction, altitude and pitch remained largely consistent as the aircraft continued to accelerate westward.

The last data point recorded by the controller was 184 m from the take-off location, as the aircraft approached the western side of Cockle Bay. At this point the aircraft was at 26 m AGL and travelling at its maximum speed of 94 km/h.

Data recovered from the aircraft (shown in red in Figure 5) is consistent with the controller data with regard to heading and speed. The slight off-set in altitude data is likely due to one data set using GPS altitude and the other using barometric altitude. The RPA data shows the aircraft continuing at its maximum speed at a relatively stable heading and altitude for another 150 m until it impacted a building on the western side of Darling Drive.

Operational information

Restricted airspace operations

The area of operation was classified as a restricted area by the Civil Aviation Safety Authority (restricted area R405A). Sub regulation 101.065 (3) of the Civil Aviation Safety Regulations (CASR) 1998, required that the controlling authority must provide a written statement to an RPA operator of the conditions of entry to a restricted area. The operator applied for this permit, and one was provided by CASA. Some of the conditions of the permit were:

  • the radius of operation was to be within a 30-metre radius of a vessel at the location as shown in Figure 6
  • operations were to be between the surface and 90 feet above surface level (ASL)
  • operations were not permitted within 30 metres of the shoreline of Cockle Bay and not within 30 metres of, or over, any vessel not directly associated with the RPA operation, or in such a way that the master of a vessel had to take avoiding action.

Figure 6: Operational restrictions for operations within restricted area R405A.

ao-2021-001-pic-6.jpg

Source: Operator

Additionally, the permit did not exempt the RPA operator from the general conditions applicable to all RPA operators, that an RPA must not be operated:

  • beyond visual line-of-sight
  • over a populous area
  • within 30 metres of any person not directly associated with the RPA operation.
Emergency procedures

The operator’s operational procedures document provided guidance for actions to take in the event of a flyaway or visual loss of an RPA.

Fly Away or Visual Loss of RPA - Where an RPA is experiencing loss of control or is visually lost, all attempts shall be made to regain control or initiate the Return To Home procedure. Should these attempts fail perform a combined stick movement to shut-down the motors with due regard for the location of the RPA so as not to increase the risk of collision with persons or property. The Controller will shout warning to people or use radio where necessary. The shut-down timing is crucial to control the RPA termination point within a safe area before the aircraft has the possibility to fly beyond the area of operation into areas over people/property etc. In the event of an uncontrolled Fly Away, the RPA will be deemed unserviceable pending inspection by the Maintenance Controller.

The pilot made a number of attempts to control the RPA through use of the control sticks, without effect. However, they had no recollection of using the Smart return to home function or the emergency engine shutdown procedure.

Related occurrences

A review of the ATSB’s aviation occurrence database revealed that in the 4 years between 2017 and 2020, 1,165 occurrences have been reported to the ATSB involving an RPA aircraft type. In this time, 94 occurrences were classified as a Data link (UAS) occurrence type. The

described this occurrence type as:

The partial or complete loss of transmission and/or reception of digital information from an unmanned aerial system.

55 (59 %) of the 94 Data link occurrences involved a DJI aircraft. However, it should be noted that DJI are the market leader for RPAS and, as such, they represent a significant proportion of RPAS flying in Australia. Outcomes for these occurrences varied, depending on whether the aircraft crashed immediately, flew away, or auto-landed (either on land or in water).

  • 43 of the 55 (78 %) were associated with a collision with terrain, while another two involved a ditching and seven resulted in missing aircraft.
  • 42 of the 55 (76 %) were classified as an accident, with the remainder classified as an incident
  • Nealy all of the 55 data link occurrences resulted in some level of damage to the aircraft, with 29 (53 %) of the 55 occurrences resulting in the aircraft being lost or destroyed. Another 12 occurrences resulting in substantial damage and 10 with minor damage.
  • Of the 55 DJI aircraft involved in a Data link occurrence, 32 of the RPA’s were in the Phantom product line, with 13 in the Matrice, 6 Mavic and 4 Inspire.

These aircraft varied in size between about 0.75 kg and 9 kg, with maximum speeds between about 65 and 94 km/h. The user manuals for all these aircraft types described the Failsafe Return to Home Function.

__________

  1. The part of the electromagnetic spectrum contiguous to the red end of the visible spectrum, comprising radiation of greater wavelength than that of red light.

Safety analysis

Loss of control

Shortly after take-off for the second planned flight from the Darling Harbour area on 15 January 2021, the pilot reported that the Inspire 2 remotely piloted aircraft (RPA) initiated an uncommanded pitch‑down and acceleration. The aircraft remained unresponsive to control inputs as it continued to accelerate westwards, towards the Harbourside shopping mall.

Before the aircraft left Cockle Bay the screen on the pilot’s transmitter that showed the camera image froze and then went black. Flight data recovered from the transmitter showed that about 8 seconds into the flight, the pitch of the aircraft increased significantly, followed shortly by an increase in speed. The aircraft continued to accelerate to its maximum speed of 94 km/h before recording of the flight data ceased 184 m from the take-off location.

Controller signal

The manufacturer advised that the data transmission system for the Inspire 2 had two independent channels, one for data upload and one for data download. Therefore, it was possible for one signal to be lost while maintaining the other. Analysis of the flight data log undertaken by the manufacturer showed a number of control inputs made by the pilot were received by the RPAS for the duration of the entire flight. Thus, the manufacturer advised that the upload signal (from the controller to the RPAS) was maintained for the entire flight.

Despite these control inputs being received by the RPAS, the flight data in Figure 5 shows that the aircraft did not appear to respond to these inputs, as it continued at roughly the same heading, speed and altitude until it collided with the building.  

Compass failure

Analysis undertaken by the manufacture indicated that at the time the aircraft took-off the compass was functioning normally. However, about a second after take-off the compass was subjected to strong magnetic interference. From this point the compass started sending spurious information to the internal measurement unit (IMU). A short time later the IMU accelerometer measurements became unstable leading to the loss of directional control.

Failsafe Return to Home

The Inspire 2 had a Failsafe Return to Home (RTH) function, which was designed to prevent a flyaway occurrence in the event of a loss of controller signal. The user manual described three prerequisites for this feature to function properly. Specifically, the:

  • home point must be set
  • compass must be functioning
  • controller loss of signal must exist for more than three seconds.

In this occurrence the pilot had no control authority over the aircraft, and the signal download link ceased. Despite this, the signal upload link was maintained and therefore the failsafe RTH was not triggered. Additionally, about 1 second after take-off when the compass failed, the failsafe RTH was rendered inoperable as it relies on a functioning compass.

Flight modes

The Inspire 2 manual stated that the aircraft would switch to A-Mode if the compass suffered from interference, but only when the Vison System was unavailable. In this occurrence, despite the compass failure, the Vision System remained available, and therefore the flight mode was not automatically switched to A-Mode. As A-Mode does not rely on the compass or GPS, the manufacturer advised that if the flight mode was switched to A-mode, control of the aircraft could have been regained. 

Operational requirements

Permissions provided by the Civil Aviation Safety Authority to fly an RPA in restricted area R405A came with a number of operational restrictions. These included:

  • operating in an area 30 m in radius within Cockle Bay
  • operating between the surface and 90 ft (27.4 m)
  • operating within 30 m of the shoreline of Cockle Bay.

Other general conditions applicable to all RPA operators included not flying over a populous area and not flying within 30 m of any person not directly associated with the RPA operation. Flight data recovered from the transmitter showed the pilot exceeded a number of these limitations by flying up to 70 m (230 ft) as well as flying over the Cockle Bay shoreline and over the Harbourside shopping mall.

Emergency procedures

The operator’s emergency procedures in the event of a fly away recommended attempting to regain control of the RPA or initiating a RTH. If these failed, the recommendation was to initiate an emergency motor shutdown.

Although the pilot made a number of attempts to control the RPA through use of the control sticks, the pilot did not recall using the Smart RTH feature or the emergency engine shutdown procedure. However, given that the compass had failed the Smart RTH would not have worked anyway. Additionally, given that the pilot had no control authority over the aircraft, it is unclear whether the emergency motor shutdown commands would have been acted on by the RPA.

Findings

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

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

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

From the evidence available, the following findings are made with respect to the Loss of control and collision with terrain, Inspire 2 (PRA), Darling Harbour New South Wales, on 15 January 2021.

Contributing factors

  • Shortly after take-off the compass failed rendering the aircraft uncontrollable, disabling the Return to Home function and resulting in the collision with a building.

Other factors that increased risk

  • The pilot in command did not follow the emergency procedures outlined in the operations manual and did not comply with the operating limitations outlined in the Civil Aviation Safety Authority approval.

Glossary

AGL                 Above ground level

CASA               Civil Aviation Safety Authority

CASR               Civil Aviation Safety Regulations

DJI                   Da-Jiang Innovations

GPS                 Global Positioning System

RPA                 Remotely Piloted Aircraft

RPAS               Remotely Piloted Aircraft System

RTH                 Return to Home

SD                   Secure Digital

Safety action

Safety action not associated with an identified safety issue

Whether or not the ATSB identifies safety issues in the course of an investigation, relevant organisations may proactively initiate safety action in order to reduce their safety risk. The ATSB has been advised of the following proactive safety action in response to this occurrence.

Additional safety action by SZ Da-Jiang Innovations (DJI) Technology Co Ltd

The manufacturer has advised that they have updated the user manuals of a number of products, including the Inspire 2. These changes provide additional guidance to users regarding the use of the fully manual attitude flight mode in the event of compass interference.

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • pilot of the accident flight
  • Sky Monkey Pty. Ltd.
  • Civil Aviation Safety Authority
  • New South Wales Police Force
  • SZ Da-Jiang Innovations (DJI) Technology Co Ltd
  • Bureau of Meteorology
  • recorded data from the RPAS.

References

Civil Aviation Safety Authority (CASA), Civil Aviation Safety Regulation (CASR) 1998 Part 101

Sky Monkey Operations manual, operational procedures and safe work method statement.

DJI Inspire 2 user manual

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:

  • Civil Aviation Safety Authority
  • Sky Monkey Pty. Ltd
  • the pilot of the accident flight
  • SZ Da-Jiang Innovations (DJI) Technology Co Ltd
  • Australian Federal Police

Submissions were received from:

  • Civil Aviation Safety Authority
  • Sky Monkey Pty. Ltd
  • SZ Da-Jiang Innovations (DJI) Technology Co Ltd
  • Australian Federal Police.

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

Purpose of safety investigations & publishing information

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2022

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

Occurrence summary

Investigation number AO-2021-001
Occurrence date 15/01/2021
Location Darling Harbour
State New South Wales
Report release date 23/06/2022
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level None

Aircraft details

Model Inspire 2
Registration 09YDFAL0040942
Serial number 09YDFAL0040942
Aircraft operator Sky Monkey Pty Ltd
Sector Remotely piloted aircraft
Operation type Aerial Work
Departure point Darling Harbour, New South Wales
Destination Darling Harbour, New South Wales
Damage Destroyed

Partial power loss and collision with terrain involving Dynaero MCR-01 VLA, VH-SIP, near Serpentine Airfield, Western Australia, on 28 December 2020

Preliminary report

Preliminary report released 15 March 2021

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 28 December 2020, at about 1438 Western Standard Time,[1]a Dynaero MCR-01, registered VH-SIP, departed Serpentine Aerodrome, Western Australia, to conduct a check flight after maintenance (Figure 1). The pilot was the sole occupant on board.

The pilot had conducted one previous check flight in VH-SIP earlier that afternoon, and was conducting the post-maintenance checks with a number of ground crew, including licensed aircraft maintenance engineers.

Witnesses reported that, on the second flight from runway 09,[2]audible changes in the aircraft engine noise, and a noticeable change in aircraft performance at about 300 ft above ground level. They observed the aircraft slow and begin a left turn. Further change in the engine noise were heard before VH-SIP was observed to continue the left turn. Shortly after, the left wing dropped, and the aircraft entered a steep, nose-down rotating descent. The pilot was unable to recover control of the aircraft before impacting terrain.

Figure 1: Flight path derived from witness reports and accident site location

Flight path derived from witness reports and accident site location

Source: Google Earth, annotated by the ATSB

The witnesses at the aerodrome were able to quickly get to the accident site to render assistance, however the pilot had sustained fatal injuries. The aircraft was destroyed.

Site and wreckage examination

The accident site was located in relatively flat and open farmland (Figure 2), about 200 m east of the threshold of runway 23 at Serpentine aerodrome. The ATSB conducted an examination of the site and wreckage, and identified that the:

  • ground impact marks indicated that the aircraft had impacted terrain nose-down, upright, rotating to the left
  • flaps were in the retracted position.

No pre-impact defects were identified with flight controls or aircraft structure. The aircraft’s single fuel tank had ruptured and a quantity of fuel had leaked into the soil. There was no fire.

Several items were recovered from the site for further examination, including:

  • a damaged GPS unit
  • various instruments
  • fuel system components including the fuel flow indicator
  • the engine
  • the propeller.

Figure 2: Accident site

Source: ATSB

Further investigation

Electronic instrumentation will be examined at the ATSB’s technical facility in Canberra. The engine and propeller will be examined under ATSB direction by manufacturer representatives.

The investigation is continuing and will include:

  • interviews with witnesses involved with the accident and operations the previous day
  • analysis of the downloaded data from the fuel flow meter and other electronic devices
  • examination of the recovered components
  • review of the pilot’s qualifications, experience and medical history
  • assessment of the aircraft’s flight performance characteristics
  • examination of aircraft maintenance and operational records.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2021

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

__________

  1. Western Standard Time (WST): Coordinated Universal Time (UTC) + 8 hours.
  2. Runway number: the number represents the magnetic heading of the runway.

Final report

Executive summary

What happened

On 28 December 2020, at about 1438 local time, a Dynaero MCR-01 VLA, registered VH-SIP, departed Serpentine Airfield, Western Australia, to conduct a post-maintenance check flight. At about 300 ft above ground level, the engine began to run rough, however continued to operate. The pilot commenced a turn to the left, and the aircraft appeared to decelerate in a nose-high attitude without gaining height. Shortly after, the aircraft was observed to aerodynamically stall, pitch nose-down, and impact terrain. The pilot, who was the sole occupant, was fatally injured, and the aircraft was destroyed.

What the ATSB found

The ATSB found that multiple tasks in the aircraft’s return to service after a significant period of inactivity were not adequately carried out, and that the left carburettor of the aircraft’s engine was missing a component and contained a significant amount of contamination. This likely resulted in over-fuelling of the carburettor at a low power setting, and likely produced subsequent engine rough running at high power settings.

The pilot was unfamiliar with the aircraft and engine type, which increased the risk of not being able to adequately manage an inflight emergency. During the partial power loss on take-off, the pilot turned the aircraft in a likely attempt to land on another runway, when the aircraft stalled.

The ATSB found that the pilot had probably consumed a significant amount of alcohol the night before the accident, which increased the risk of post-alcohol impairment.

Safety message

Ongoing maintenance of an aircraft’s fuel system is essential to ensure fault-free operation of its engine. In particular, the reliability of carburettors is dependent on their condition, and by following the manufacturer’s maintenance requirements and service bulletins.

The ATSB encourages pilots to review and practice the conduct of a pre-take off safety brief before each flight, and highlights the importance of preparedness for possible emergencies on take-off leading to an off-airfield landing. The ATSB further encourages pilots to review the recommended partial power loss procedure in the aircraft pilot operating handbook if available, and cautions against turning back towards the runway unless in controlled situations where sufficient altitude exists. Further information can be found in the ATSB booklet, Avoidable Accidents No.3: Managing partial power loss after take-off in single engine aircraft AR-2010-055.

Pilots transferring from one type of aircraft to another are reminded that there is as much risk in moving to lower performance aircraft, as there is moving to higher performance aircraft. The ATSB encourages pilots to manage this transition using a risk-based approach such as Federal Aviation Administration (FAA) advisory circular AC90-109A – Transition to Unfamiliar Aircraft (U.S. Department of Transportation Federal Aviation Administration, 2015).

This accident is also a reminder that blood-alcohol can persist the day after significant alcohol consumption, and the residual effects of alcohol may impair performance, especially in demanding and time critical situations.

The occurrence

Overview

On 28 December 2020, at about 1438 local time, a Dynaero MCR-01 VLA, registered VH-SIP, departed Serpentine aircraft landing area (ALA), Western Australia, to conduct a post-maintenance check flight. At about 300 ft above ground level, the engine began to run rough, however continued to operate. Shortly after, the aircraft was observed to aerodynamically stall,[1] pitch nose-down, and impact terrain. The pilot, who was the sole occupant, was fatally injured, and the aircraft was destroyed.

Aircraft return to service

Post-maintenance flight checks

On 27 December 2020, the new owner and a flight instructor were a conducting post-maintenance check flight of VH-SIP at Serpentine ALA, after undergoing maintenance after an extended period of inactivity (see Return to service tasks). As they departed from runway 05[2] on climb, at about 200–300 ft above ground level (AGL), the engine lost power and began to run rough. The instructor, who was the pilot in command, reported that they lowered the nose and reduced power, which cleared the rough running and allowed the aircraft to continue flight. There was sufficient power available to continue a reduced climb and conduct a circuit back onto runway 05.

The instructor recalled they then initiated a missed approach on short final approach to runway 05 and commenced a full power climb. While the aircraft engine power initially responded, rough running was again experienced at about 200–300 ft AGL. The instructor again reduced power, cleared the rough running, and conducted a slow climb before making a final landing back on runway 09. Both occupants identified the smell of fuel in the cockpit at the time.

The instructor, the new owner and several other people including the pilot of the accident flight (pilot) assisted a licenced aircraft maintenance engineer (LAME) with troubleshooting the engine rough running that afternoon. Numerous engine-runs were conducted on the ground with multiple witnesses stating that they were able to replicate the rough running and partial power loss during the static full power tests on the ground, both with and without the electric fuel pump assistance. The owner stated that the engine seemed to run smoother with the electric fuel pump on, however engine coughing and rough running was replicated on all of the full power runs to varying degrees. Other witnesses recalled the engine stopping when the throttle was reduced after the engine runs, one capturing the stoppage on video.

Engine troubleshooting

To try and diagnose the problem, basic fuel system troubleshooting was conducted by another LAME on behalf of the original LAME, who was no longer at the airfield. This included the draining and cleaning of the fuel filter on direction of the original LAME by phone. A witness described the contaminants within the fuel drain sample and filter as a significant amount of ‘brown gunk’. The engine troubleshooting continued until early evening, when the aircraft was then hangered for the night with the original LAME scheduled to conduct troubleshooting on the aircraft the next day.

The owner and instructor made the decision to return back to Queensland without the aircraft and have the aircraft ferried over when the rectification work was completed. The pilot, who was known to the LAME, volunteered to ferry VH-SIP from Serpentine to Queensland after working with the LAME to correct the engine problem. The owner accepted the offer before departing Serpentine Airfield back to Perth.

Evening activities

That evening, the local aero club held a dinner at the airfield (see social function). Witnesses confirmed that the pilot attended the event, retiring to their accommodation at about 0200 the following morning.

Accident flight

On 28 December 2020, the pilot and LAME met at the airfield at about 1100. The LAME did not recall the pilot was any different to usual, however did remark that the pilot was consuming significant amounts of water. The pilot assisted the LAME with the running of the engine and mentioned that they had never flown an aircraft as small or light before and had not operated a Rotax engine previously. Subsequently, the LAME explained the absence of a mixture control, use of ignition systems and the operation of the electric inflight adjustable propeller.

The LAME removed the aircraft cowls and inspected the engine compartment for a fuel leak before replacing a newly installed mechanical engine driven fuel pump with the old pump to test positive fuel flow without any blockages as part of the troubleshooting sequence. The LAME identified that the fuel flow increased with the activation of the electric fuel pump.

The pilot conducted a troubleshooting check flight in VH-SIP at about 1415, with the support of a number of ground crew including several LAMEs. On return from the first flight, the pilot reported that the engine was not developing full power (5,500 RPM),[3] and was not able to produce much greater than 4,000 RPM. The LAME provided an additional brief to the pilot on the use of the automatic propeller system and requested further ground runs of the engine.

At about 1438, the pilot conducted a further post-maintenance troubleshooting flight from runway 09 (Figure 1). The LAME stated that they expected the aircraft operation to be a high-speed ground run. At about 300 ft AGL, witnesses described audible changes in the aircraft engine noise, and observed a noticeable change in aircraft performance. They observed the aircraft visibly slow and begin a left turn. Further change in the engine noise was heard before the aircraft was described to commence another left turn towards runway 23. At about 200 ft AGL, witnesses described the left turn beginning to tighten and the aircraft visibly slowing with a nose-high attitude. At about 150 ft AGL, the aircraft’s left wing dropped and the aircraft entered a steep rotating descent to the left. The pilot was unable to recover control of the aircraft before it impacted with terrain.

Figure 1: Aircraft’s flight path and accident site location

Figure 1: Aircraft’s flight path and accident site location

Source: Google Earth, modified by the ATSB

Context

Pilot information

Licencing

The pilot held an air transport (Aeroplane) pilot licence. This licence was for single and multi-engine aircraft, with endorsements for tailwheel aircraft, manual propeller pitch change, gas turbine engines, pressurisation and for aircraft with retractable undercarriage.

Aeronautical experience

General experience

The pilot’s logbook showed a total flying experience of 5,999.8 hours, up to the last recorded flight on 31 November 2019, when the pilot ceased airline flying with a carrier in the US, before moving back to Australia.

Aircraft specific experience

The majority of the pilot’s total flight time was conducted in multi-engine, piston and turbine aircraft operations. However, since the pilot’s return to Australia, they had conducted a tailwheel design feature endorsement, an aeroplane flight review, and a number of private flights of the local aeroclub aircraft based at Serpentine ALA.

Although the pilot had considerable experience, a review of the pilot’s logbook records found that they had not previously flown Rotax-powered aircraft or the Dynaero MCR-01 VLA.

Medical

The pilot held a valid class 1 and class 2 medical certificate, with the last examination conducted on 23 January 2020. The pilot’s class 2 medical was valid until 23 January 2022 and included restrictions requiring the wearing of distance vision correction and additionally, that reading correction must also be available whilst exercising the privileges of the licence.

Recent history

The night before the accident, a number of airfield members met for an informal social dinner at the clubhouse facilities. It was reported that a number of people attended the dinner, and that alcohol was consumed as part of the social event. Witnesses reported seeing the pilot drinking alcohol during the dinner, 1 witness recalled that the pilot engaged in a ‘fairly heavy’ drinking session consuming a significant quantity of alcohol. The witness recalled the pilot being in a good state of mind, being exceptionally chatty and, later on, recalled them stating that the pilot was ‘really drunk’.

The social function ended at about 0130 on the morning of the accident. Another witness recalled seeing the pilot shortly before driving home from the airport at about 0147, but did not believe that the pilot was significantly impaired by alcohol at that time. The pilot’s quantity and quality of sleep could not be determined.

Post-mortem and toxicology

A post-mortem indicated that the cause of death was due to multiple injuries that were sustained as a result of the collision with terrain. Toxicology indicated low levels of carbon monoxide, consistent within normal levels, and did not detect any common drugs. Toxicology did not detect levels of alcohol within either blood or urine samples.

Aircraft information

General

The Dynaero MCR-01 VLA is a low-wing, high performance, experimental amateur-built aircraft. It was supplied in kit form and VH-SIP was constructed for the education and recreation of the previous owner. The Dynaero MCR-01 VLA was promoted as suitable for cross-country flying, with an airspeed range from 56 to 200 kt. It could be operated between +3.8 g and -1.5 g,[4] however aerobatic flight and intentional spinning of the aircraft were prohibited.

Airworthiness and maintenance history

The aircraft was constructed from a kit and had a special certificate of airworthiness issued on 15 May 2003, and was first flown on 22 May 2003. The aircraft was powered by a horizontally opposed, 4-cylinder, dual carburettor, Rotax 912 ULS-FR, that was manufactured in May 2002.

On 6 November 2003, the canopy of VH-SIP shattered while the aircraft was in flight. This led to a loss of control and the aircraft entering a spin at altitude. After recovering controlled flight, the pilot conducted a forced landing into a paddock, which resulted in significant damage to the aircraft. VH-SIP was repaired over a period of about 18 months, and during this time, the carburettors were removed, cleaned and refitted. The aircraft was returned to service in April 2005.

Among other work carried out on the aircraft, the logbook recorded that, in September 2006, the carburettors were again cleaned and refitted. The aircraft did not fly between November 2009 and November 2013 (4 years). In August 2013, the original owner conducted maintenance on the aircraft for the last time. The aircraft was flown on 4 occasions in 2014, and then was inactive for over 5 years.

On 13 January 2019 the aircraft logbook indicated that work had been conducted on the fuel system and carburettors of VH-SIP, including a new fuel drain valve, removal and cleaning of the carburettors, the installation of new idle jets, O rings and new carburettor float bowl gaskets. Oil and oil filter replacements were also carried out, and the fuel system was flushed with 10 L of aviation gasoline (AVGAS) before being ground run.

In 2020, the aircraft was offered for sale. A pre-purchase inspection was undertaken on 22 May 2020 by a Recreational Aviation Australia Level 2 maintenance engineer on behalf of a prospective buyer. The engineer did not consider the aircraft to be in an airworthy condition due to contaminants in the carburettors, unactioned carburettor float service bulletins, and the mandatory rubber component replacement requirements had not been carried out. Subsequently, the condition of the aircraft was reported to the prospective buyer and the sale did not proceed.

The licenced aircraft maintenance engineer (LAME) at Serpentine ALA was contacted by another prospective buyer in early December 2020 to conduct a pre-purchase inspection before the aircraft was due to be auctioned. The LAME advised the prospective owner that they considered the aircraft to be in good condition, however it would require an annual inspection. Several days later the LAME was contacted by the buyer and advised of the successful acquisition of the aircraft and requested that the LAME carry out the work required to issue a maintenance release. The last entry in the aircraft maintenance log was on 27 December 2020, the day prior to the accident. It showed the most recent work conducted by the LAME.

Engine preservation and return to service

Preservation and storage requirements apply to aircraft engines fitted to an aircraft, as well as uninstalled engines. The Rotax operator’s manual had preservation and storage requirements for long out-of-service periods that were required to be repeated every year the engine was inactive. This included inhibiting the engine both internally and externally and covering all of the engine’s openings to protect it from dirt and humidity. The line maintenance manual limited the storage period for engines to 24 months, and if this period had been exceeded, the engine required overhaul.

The engine manufacturer had an aircraft engine return to service schedule for Rotax 912 engines after a prolonged period or during preservation. These requirements included conducting the normal 100-hour inspection before flight if the engine has been preserved for greater than 12 months.

Return to service tasks

At the request of the new owner, the LAME performed the return to service over a period of several days. The LAME recalled that, during this work, the floats were removed from the carburettor bowls and weighed for discrepancies, refitted, and a carburettor balance was conducted. The LAME also recalled conducting a fuel calibration by draining and replacing the fuel at set increments to ascertain if the fuel quantity markings were correct. Additional work carried out included a periodic inspection, instrument and systems checks, a compression test, engine idle adjustment, and engine ground runs.

Logbook entries detailed that the airframe was inspected in accordance with the Dynaero schedule and considered airworthy along with entries stating:

  • the propeller was inspected and found to have nil defects evident
  • the engine was inspected in accordance with the BRP-Rotax 912 maintenance manual and CASA AD/ENG/4 with nil defects evident
  • service bulletins for the flaps, main landing gear attach, trim tab attach, and canopy attach were carried out
  • pitot-static leak tests
  • engine-driven fuel pump was replaced
  • the 5-year carburettor rubber part and coolant hose replacement was carried out in addition to fitting a new fuel pump and spark plugs.

A maintenance release was issued by the LAME on 27 December 2020 at an aircraft time in service of 439.3 hours. There were 3 endorsements on the maintenance release:

  • an engine oil and filter change at 489.3 hours
  • a periodic inspection by 539.3 hours or 26 December 2021
  • the oil and fuel hoses to be changed by February 2021.

The LAME recalled that the oil and fuel hose replacement entry had been added because the required parts were not available to be sourced and therefore could not be fitted during the aircraft’s return to service.

The other required parts were supplied by the engine importer directly to the LAME in mid-December 2020. Some of these parts were replaced during the return to service, however a few unused parts in their original packaging were found in the aircraft at the accident site.

After the aircraft was returned to service, it underwent a number of other maintenance troubleshooting checks the day prior to, and the morning of the accident. These checks included the removal and replacement of key parts, such as the refitting the original time-expired engine‑driven fuel pump for troubleshooting purposes, however these changes were not documented.

The pilot also conducted several ground runs along runway 09 before becoming airborne and conducting a circuit.

Fuel

The aircraft operated on AVGAS and had the capacity to carry 79 L of usable fuel, in one 80 L main tank. The aircraft was reportedly refuelled prior to the proposed departure from Serpentine ALA the day before the accident, and the new owner estimated that about 60-65 L would have been on board at the time of the accident. ATSB investigators confirmed a strong smell of fuel at the accident site.

Weight and balance

Weight and balance information retrieved from the accident site indicated the aircraft had an empty weight of 261 kg and a maximum take-off weight of 490 kg. The difference left about 229 kg of useable payload for the pilot and fuel. Weight and balance calculations placed the centre of gravity towards the forward limit of the envelope, and within limits.

Amateur-built aircraft

Pilots and passengers of experimental aircraft in Australia accept the risk that the aircraft may not meet the same airworthiness safety standards as certified aircraft, and operate these aircraft on the basis of informed participation.[5] Most amateur-built aircraft are constructed in Australia for the owners education and leisure, however in time many are sold to other private operators.

Operating limitations

Aircraft operating limitations were contained within the aircraft flight manual and the relevant stall airspeed limitations are detailed in Table 1.

Table 1: Stall speeds at 400 kg maximum take-off weight

Bank angle0° flaps,[6] power off, knots indicated airspeed (KIAS)10° flaps, power off, KIAS25° flaps, power off, KIAS
585144
30º625347
60º817262

The flight manual also described the recommended glide speed of the Dynaero MCR‑01 VLA of 70 KIAS with a 13.4:1 glide ratio,[7] indicating that the Dynaero MCR-01 VLA has a higher glide speed compared to many other low inertia aircraft in a similar weight category.

Aerodynamic stall speeds considerably increase beyond a 30° angle of bank turn (Table 1). Pilots should be aware these of characteristics during emergency manoeuvring.

The Dynaero MCR-01 VLA flight manual indicates the emergency procedure for an engine failure after take-off (Figure 2). Specifically mentioned, for engine failures immediately after take-off, is not to attempt a 180° turn to return to the runway.

Figure 2: Engine failure on take-off procedure

Figure 2: Engine failure on take-off procedure

Source: Dynaero MCR-01 VLA flight manual

Meteorological information

Bureau of Meteorology graphical area forecast for the Serpentine local area indicated that at the time of the accident, that visibility was greater than 10 km with nil significant weather issues. However, moderate turbulence was expected below 10,000 ft over land in thermals and dust devils.

At about the time of the accident, Jandakot Airport, about 30 km to the north of Serpentine, recorded an easterly wind of about 13 kt with visibility greater than 10 km and no significant cloud or weather.

Witnesses at the airfield described the weather as a ‘belting easterly’ and similar to the previous day with hot, dry and windy conditions.

Wreckage information

Site and wreckage examination

The accident site was located in relatively flat and open farmland (Figure 3), about 200 m east of the threshold of runway 23 at Serpentine ALA. The ATSB conducted an examination of the site and wreckage and identified:

  • ground impact marks indicated that the aircraft had impacted terrain nose-down, upright and with left rotation
  • flaps were in the retracted position.

No pre-impact defects were identified with flight controls or aircraft structure. The fuel tank, located between the cockpit and engine compartment, had ruptured and a quantity of fuel had leaked into the soil. There was no pre- or post-accident fire.

A damaged GPS device, instrumentation including a fuel flow indicator, the engine, propeller, and fuel lines, were recovered from the accident site for further technical examination by the ATSB.

Figure 3: Accident site

Accident site

Source: ATSB

Engine examination

The engine was disassembled and examined at a Civil Aviation Safety Authority (CASA) approved engine overhaul facility under the supervision of the ATSB. Apart from impact damage, the main engine components were generally in good condition.

Testing and dis-assembly of the carburettors and fuel system identified:

  • the left carburettor was missing a clip that attached the float needle valve to the float hinge bracket
  • corrosion was identified in both carburettor bowls and on both sets of carburettor floats
  • significant corrosion deposits were found on the float needle valve, seat and on the valve tip
  • carburettor floats were the incorrect type
  • the right carburettor float guide pin was bent, causing float contact with side of carburettor bowl
  • fuel line internals were perished and brittle with splitting at the securing end.

Further details relating to the engine teardown can be found in Appendix B – Engine examination.

Partial power loss

Partial power loss on take-off

The ATSB booklet, Avoidable Accidents No.3: Managing partial power loss after take-off in single engine aircraft (AR-2010-055) (Australian Transport Safety Bureau, 2013), describes partial engine power loss as a situation when the engine provides less power than commanded by the pilot, but more power than idle thrust:

This kind of power loss is more complex than a complete failure, and it can be much harder to stay ahead of the aircraft. The pilot is thrust into a situation where the engine is still providing some power; however, the power may be unreliable, and the reliability may be difficult to assess. As a result, pilots are uncertain about the capabilities of their aircraft, and what their options are.

Partial engine power loss can range from providing very little power to almost full power, with varying levels of reliability of the remaining engine power. When faced with a partial power loss, pilots should not try to diagnose the engine problems at the expense of maintaining aircraft control.

On take-off, once the aircraft climbs to a point where it does not have enough runway to land straight ahead, but is not high enough to safely return to the aerodrome for a landing, it has reached a ’no return’ to the runway decision point (Figure 4). From this point, until the aircraft climbs to a height allowing safe return to the runway, the pilot is faced with conducting a forced landing beyond the prepared surface of the airfield. Decisions made by the pilot in command can be critical to the safety of flight at this point. 

Figure 4: No return decision point

Figure 4: No return decision point

Source: Google Earth, modified by the ATSB

In the event of any emergency during critical phases of flight, such as below 200 ft above ground level (AGL) on take-off in a single engine aircraft without runway remaining, pilots should focus on the priorities of:

  • Aviate: maintain glide speed and assess whether the aircraft is maintaining, gaining or losing height to gauge aircraft performance
  • Navigate: fly the aircraft to make a landing, if height and power are limited, then an into wind landing, 30° left or right of the centreline is a safer option
  • Communicate: Mayday call as appropriate.
Pre-take-off safety brief

The pre-take-off safety brief is a verbal and mentally prepared response, through the pre-visualisation of an emergency on take-off and is generally conducted once all engine run-ups are complete and prior to entering the runway. The brief mentally prepares a pilot with pre-programmed responses to possible unexpected events during this critical phase of flight when decision making time is short.

These anticipated actions in response to certain stimuli, assist pilots in making better decisions in accepting emergency circumstances and safely managing emergencies, especially when an off-airfield landing may be the safest option.

The briefing should include the pilot in command’s intentions in the event of an engine related problem during the take-off roll and after take-off, both with runway remaining and without. This formulates pre-existing mental models of possible actions should an emergency arise. 

A pre-take off safety brief should include:

  • consideration of the runway in use, it’s length, surface, boundary fencing and possible forced landing areas beyond the runway, including terrain and obstacles
  • wind direction and strength, which will indicate the safest into wind turning options to safely maintain airspeed and provide a lower groundspeed in case of a forced landing beyond the airfield boundary
  • consideration of required height and direction of turn, to conduct a turn back to the runway

The ATSB Avoidable Accidents booklet provides sound guidance to pilots on this subject and concludes that:

Generally speaking, if you self-brief your plan of action just before flight, you have more chance of ‘staying ahead’ of the aircraft and being able to concentrate on flying.

The turn back

The turn back is described as the conduct of an emergency manoeuvre to reverse the direction back towards the take-off runway, to either conduct a landing on the reciprocal runway or to land at another runway at the original departure point.

During this critical time, the pilot must assess four main considerations for the safe conduct of a turnback:

  • Is the height sufficient to safely turn the aircraft back to the runway?
  • Is there remaining power available to continue to climb or maintain height?
  • Can a safe airspeed be maintained during the turn, taking into account the increased stall Speed associated with an increased angle of bank to prevent aerodynamic stall?
  • assuming that the engine may fail at any time, is the remaining power reliable?

The ATSB Avoidable Accidents booklet noted:

A turnback requires accurate flying during a period of high stress to prevent a stall and possibly a spin occurring. If an aerodynamic stall and or spin occurs, given that these circumstances are likely to be at low level, there is little likelihood of a successful recovery.

There are many scenarios where it might be considered inappropriate to conduct a turnback. For example, consideration should be given to additional hazards such as other aircraft, obstacles, an unfavourable wind component, increased stall risk during a low-level turn and surrounding terrain.

Pilot decision making during partial power loss

The ATSB Avoidable Accidents booklet also detailed influences on decision making affecting pilots:

The course of action chosen following such a partial power loss after take-off can be strongly influenced by the fact that the engine is still providing some power, but this power may be unreliable. As the pilot, you may also have a strong desire to return the aircraft to the runway to avoid aircraft damage associated with a forced landing on an unprepared surface.

Based on an analysis of partial power loss accidents after takeoff, the booklet further noted that pilot decision making is also influenced by the amount of power loss experienced. In situations where power loss is substantial, pilots are more likely to recognise this as being close to a complete loss of power and typically conduct a forced landing outside of the runway environment. However, if the remaining power is sufficient to continue climb, albeit at a reduced rate, pilots were able to take advantage of increased options, such as a continuing a circuit or conducting a turn back towards the runway.

However, the ATSB identified a period between these 2 areas that represented a region of heightened uncertainty (Figure 5). In this region, excess power was not available to climb but there was sufficient power to prevent appreciable descent, resulting in a period of flight uncertainty where the aircraft may not be able to maintain height without bleeding off airspeed, eventually resulting in the aircraft slowing to maintain or gain height and increasing the risk of aerodynamic stall.

Figure 5: Region of heightened uncertainty during partial power failures on take-off

Figure 5: Region of heightened uncertainty during partial power failures on take-off

Source: ATSB

The ATSB identified that 8 out of 9 partial power loss accidents resulting in fatal injuries occurred with mid-range power loss. Inconsistent power or engine surging from high to low RPM present complex problems to the pilot. Inability to maintain height with partial power loss usually leads to aircraft stall and loss of control, mostly resulting in collision with terrain.

Transition to unfamiliar aircraft

General competency

In order for a pilot to operate a different aircraft type already covered by their licence category and class rating, they need only be satisfied that they are competent under Civil Aviation Safety Regulation (CASR) 1998.

CASR 61.385 Limitations on exercise of privileges of pilot licences – general competency requirement stated:

(1) The holder of a pilot licence is authorised to exercise the privileges of the licence in an aircraft only if the holder is competent in operating the aircraft to the standards mentioned in the Part 61 Manual of Standards for the class or type to which the aircraft belongs, including in all of the following areas:

(a) operating the aircraft’s navigation and operating systems;

(b) conducting all normal, abnormal and emergency flight procedures for the aircraft;

(c) applying operating limitations;

(d) weight and balance requirements;

(e) applying aircraft performance data, including take-off and landing performance data, for the aircraft.

Guidance on transition

While no definitive Australian guidance provided advice on the transition of pilots to unfamiliar aircraft, the Federal Aviation Administration (FAA) advisory circular AC90-109A – Transition to Unfamiliar Aircraft (U.S. Department of Transportation Federal Aviation Administration, 2015) is a widely recognised and utilised publication providing a sound basis to consider the hazards of transitioning to unfamiliar types of aircraft, whether certified or experimental.

The AC recognises the importance of providing guidance to pilots transitioning between aircraft types, or to experimental aircraft with differing design features to high performance and complex aircraft. It recommends that pilots’ should develop a training strategy (Figure 6) for mitigating the risks of operation of an unfamiliar aircraft type.

The FAA AC recommend that:

Prior to flying an unfamiliar airplane, all pilots should review the hazards and risks outlined in this AC, and complete the training recommended before operating the airplane. Accident data has shown that there is as much risk in “moving down” in performance as “moving up.” For example, consider a pilot who has substantial experience in high-performance corporate, airline, or military airplanes. The knowledge and skills used to safely fly at high speeds, high altitudes, and over long flights will, by themselves, not prepare the pilot for the challenges of a low-inertia, high-drag airplane.

Figure 6: FAA recommended airplane transition training approach

Figure 6: FAA recommended airplane transition training approach

Source: FAA AC90-109A

The guidance recommends firstly that pilots should consider undertaking flight training with a qualified flying instructor in the proposed transition aircraft, the same make and model or an aircraft that exhibits the same design features or characteristics of the transition type. If instruction is unavailable, seek another experienced pilot to conduct a familiarisation flight; however, if unwilling, at least discuss the differences and expected characteristics of the transition aircraft.

The guidance further recommended that pilots take a risk management approach to formally identify the hazards and mitigate any known or elevated risks identified.

These may include:

  • specific type training in the transition aircraft or similar type/design features
  • safety equipment such as helmets, fire extinguishers or parachute
  • condition, maintenance and history of the transition aircraft
  • review of aircraft operating limitations
  • plan transition flights to conservatively build up manoeuvres and aircraft experience
  • conducting initial flights in benign weather conditions

Fitness for flight

Regulatory requirements

CASA identifies that any amount of alcohol in your body may affect a pilot’s fitness to safely operate an aircraft.

Subparagraphs 91.520(2)(b)(i), (ii) and subregulation 91.520(5) of CASR outlines a crew member for a flight (pilot) commits an offence if they consume alcohol at any time during the period of 8 hours ending when the flight begins, or if a test of a body sample of the crew member to determine the level of alcohol in the sample was taken at the time of carrying out the duty (and) the test reveals that the permitted level for alcohol (within the meaning of Part 99) is exceeded.

Part 99 of CASR defines –

permitted level means:

  • (a)    for a testable drug—a level of the drug specified in subregulation (2A) for the purposes of this paragraph; and
  • (b)   for alcohol—a level of alcohol of less than 0.02 grams of alcohol in 210 litres of breath.


This means pilots should give considerable and reasonable thought to the amount and rate of alcohol consumption in order to determine if residual alcohol levels may affect cognitive functions, such as decision making, reduced attention and physical ability during the intended flight.

Post alcohol impairment

Post-alcohol impairment (PAI) has been defined as performance impairment after alcohol is no longer detectable. While the performance decrement of pilots under the influence of alcohol is well known and documented, the effect of post-alcohol impairment, commonly known as a ‘hangover’, is less tangible.

Although pilots must not operate an aircraft within 8 hours of the consumption of alcohol, a pilot’s ability to make normal and emergency decisions may be impaired even after the blood alcohol concentration (BAC) has returned to zero.

Research conducted for the ATSB (Newman, 2004) into alcohol and human performance highlighted that:

In simple terms, alcohol impairs human performance…

It has detrimental effects on cognitive functions and psychomotor abilities. Risk taking behaviour may result, and a full appreciation of the consequences of a planned action may not be possible… Adverse effects can also persist the day after alcohol ingestion, with reductions in alertness, concentration and vestibule-ocular function, and increases in anxiety all being reported…

Alcohol has been shown to impair registration, recall, and organisation of information, leading to increased reaction times and/or a greater number of errors…

…performance has also been found to suffer most when an unexpected or unanticipated event occurs.

A study found that 14 hours after alcohol ingestion leading to a BAC of at least 0.10%, pilots performed much worse at a flight simulator task at a time when their BAC had returned to 0 (Yesavage & Leirer, 1986). Pilot performance was measured and found worse on almost every level, with detriments to precision and accuracy being highlighted. It was also found that pilots were not able to accurately judge their own degree of impairment and concluded that such performance effects would still be measurable sometime after 14 hours.

The ATSB study (Newman, 2004) also found that:

The alcohol-induced impairment of cognitive performance becomes more evident when the nature of the flying task becomes more complex and demanding, such as in an emergency situation. A pilot suffering from the effects of post-alcohol impairment may not handle such a high-workload emergency appropriately, due to reduced attention, a slower rate of information processing, increased reaction time, and poor decision-making. All of these could ultimately result in an accident.

Safety analysis

Introduction

On 28 December 2020, the pilot of a Dynaero MCR-01 VLA, registered VH-SIP, was conducting post-maintenance troubleshooting check flights at Serpentine Airfield, Western Australia. While at about 300 ft above ground level (AGL), on the second flight for the day, the engine began to run rough. Shortly after, and while most likely attempting to return to the airfield, the aircraft’s left wing was observed to drop, the nose pitched down, rotate to the left, and impact terrain.

This analysis will explore airworthiness considerations pertaining to VH-SIP, its return to service, the pilot’s experience on the aircraft type and its effect on emergency management, and the effects of post-alcohol impairment.

Return to airfield and stall

A partial power loss occurred at about 300 ft AGL on take-off from runway 09. Although alternative ‘off-runway’ landing areas were available, the pilot elected to continue flight while manoeuvring the aircraft towards the eastern end of runway 15. 

Manoeuvring an aircraft to return to the airport during critical periods of the initial climb, with inconsistent and unreliable power output, significantly increases risk.

With a combination of turning downwind, marginal power and performance, potentially an attempt to maintain altitude, probably led to the aircraft decelerating. During a further left turn towards runway 15, this decrease in airspeed likely resulted in the left-wing stall at about 200 ft AGL, that did not afford the pilot an opportunity to successfully recover.

Airworthiness of VH-SIP

Return to service

VH-SIP had 3 periods of inactivity, about 18 months, 4 years, then 5 years. There was no record in the logbooks for VH-SIP to indicate its engine had been preserved, however the logbook states the carburettors were cleaned on 3 occasions, with the most recent being in January 2019.

The requirement to replace time-limited components every 5 years was partially carried out. Some of the fuel lines that were not replaced were found to be in poor condition when examined at the overhaul facility after the accident. However, it could not be determined if this contributed to the engine rough running prior to, and on the day of the accident.

Engine defects and partial power loss

The preliminary examination of the engine at the accident site, and the subsequent engine examination at an overhaul facility did not identify any pre-impact mechanical defects. However, both carburettors were found to contain contamination, most likely forming during the aircraft’s extended periods of inactivity.

This contamination that was not rectified prior to the aircraft being released for service, or during the subsequent troubleshooting of the engine rough running. Additionally, there was no record of the fuel system being inspected and cleaned in accordance with the manufacturer’s requirements when carburettor contamination has been identified.

The flooding that was observed during multiple tests of the left carburettor, was the result of significant contamination on its float needle valve and seat. Given the amount of contamination, the left carburettor was likely flooding prior to the accident, and as carburettor flooding is known to result in fuel odour, would have been the likely source of the reported fuel smell.

It’s possible the contamination in both carburettors, along with the absence of the clip that attached the float needle valve to the float hinge bracket, resulted in the rough running of the engine at high power settings.

Ongoing maintenance of an aircraft’s fuel system is essential to ensure fault-free operation of its engine. In particular, the reliability of carburettors is dependent on their condition, and by following the manufacturers maintenance requirements and service bulletins.

Unfamiliarity with aircraft type

Although experienced in passenger transport operations and heavier multi-engine aircraft, the pilot was not as experienced in flying lighter general aviation aircraft, with even less experience in very light, low inertia aircraft such as the Dynaero MCR-01 VLA.

The safe conduct of post maintenance flights and troubleshooting of aircraft systems requires pilot familiarity and experience in the aircraft type, its design features and its normal and emergency operating parameters.

Although appropriately licenced, the pilot had never flown a Dynaero MCR-01 VLA previously and had limited experience with low inertia aircraft, as well as the engine and the propeller type fitted to VH-SIP.

The conduct of a post maintenance flight with limited pilot experience and knowledge in the aircraft and its systems, increased the likelihood that the pilot would be unable to effectively manage any in-flight emergency.

Post alcohol impairment

Post-alcohol impairment is of particular importance in aviation. While regulations require a minimum time between drinking and flying, there is considerable evidence that pilot performance may be impaired for much longer periods. Post-alcohol impairment can increase the potential for spatial disorientation for up to 48 hours. While a pilot may be legally able to fly eight hours after drinking, the residual effects of alcohol may seriously impair their performance when they need it most, such as during an emergency.

Witness accounts of reported alcohol consumption the night before the accident, increased the likelihood that the pilot would have been experiencing some level of post alcohol impairment that may have contributed to reduced cognitive function which could have affected the pilot’s decision making during the partial power loss after take-off.

Findings

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

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

From the evidence available, the following findings are made with respect to the partial power loss and collision with terrain involving, Dynaero MCR-01 VLA, VH-SIP near Serpentine Airfield, Western Australia, on 28 December 2020.

Contributing factors

  • Shortly after take-off, the engine experienced a partial power loss. The pilot turned the aircraft to the left most likely in an attempt to return for landing.
  • At about 200 ft above ground level, with low airspeed and no flap selected, the left wing aerodynamically stalled. This resulted in the aircraft entering into an upright spin, at an altitude that limited an effective recovery.
  • Multiple tasks in the aircraft’s return to service after a significant period of inactivity were not carried out adequately before the aircraft was released to service.
  • The left carburettor contained contamination that likely resulted in flooding at low power, and rough running at high power settings.
  • The pilot did not adequately manage the risk of transitioning to an unfamiliar aircraft type, further increasing the risk of not being able to adequately manage in-flight emergencies during post maintenance flights.

Other factors that increased risk

  • The pilot had probably consumed a significant amount of alcohol the night before the accident, which increased the risk of post-alcohol impairment.

Glossary

AGL                  Above ground level

ALA                  Aircraft Landing Area

ATSB                Australian Transport Safety Bureau

AVGAS             Aviation gasoline

BAC                 Blood alcohol concentration

CASA               Civil Aviation Safety Authority

FAA                  Federal Aviation Administration

GPS                 Global positioning system

KIAS                 Indicated airspeed

LAME               Licenced aircraft maintenance engineer

PAI                   Post alcohol impairment

RPM                 Revolutions per minute

VFR                  Visual flight rules.

Sources and submissions

Sources of information

The sources of information during the investigation included the:

  • witnesses that operated the aircraft the day before the accident flight
  • Civil Aviation Safety Authority
  • Western Australian Police Service
  • aircraft manufacturer
  • engine manufacturer
  • maintenance organisation
  • Airservices Australia
  • Bureau of Meteorology
  • accident witnesses
  • video footage of VH-SIP the day before the accident flight and other photographs and videos.

References

Australian Transport Safety Bureau. (2013). Avoidable Accidents No. 3 Managing partial power loss after takeoff in single-engine aircraft. Canberra: Australian Transport Safety Bureau.

Newman, D. G. (2004). Alcohol and Human Performance from an Aviation Perspective: A Review. Canberra: Australian Transport Safety Bureau.

U.S. Department of Transportation Federal Aviation Administration. (2015, July 06). AC 90-109A Transition to Unfamiliar Aircraft. Washington DC: U.S. Department of Transportation Federal Aviation Administration.

Yesavage, J. A., & Leirer, V. O. (1986). Hangover effects on pilots 14 hours after alcohol ingestion: a preliminary report. American Journal of Psychiatry, 1546-1550.

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:

  • Civil Aviation Safety Authority
  • the Bureau d'Enquêtes et d'Analyses pour la sécurité de l'aviation civile
  • engine manufacturer
  • a LAME witness
  • the aircraft owner
  • maintenance organisation.

Submissions were received from:

  • Civil Aviation Safety Authority
  • A LAME witness.
  • the Bureau d'Enquêtes et d'Analyses pour la sécurité de l'aviation civile

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

Appendices

Appendix A – Sequence of events

Sequence of events

Source: ATSB

Appendix B – Engine examination

The engine was disassembled and examined at a Civil Aviation Safety Authority (CASA) approved engine overhaul facility under the supervision of the ATSB.

Some impact damage was identified; however, the main engine components were found generally in working order.

Review of the engine systems found that the left carburettor was missing a clip that attached the float needle valve to the float hinge bracket (Figure B 1 and Figure B 2). During multiple tests under controlled conditions, the left carburettor flooded[8] repeatably. It was later determined that this was likely due to the presence of significant amounts of corrosion on the float needle valve, its seat, and a deposit on the on the valve tip (Figure B 3).

Figure B 1: Carburettor components

Figure B 1: Carburettor components

Source: BRP-Rotax, modified by the ATSB

Additionally, both carburettor float bowls were contaminated. The floats fitted to both carburettors were the original type (Figure B 4), which were required to be replaced as part of a mandatory service bulletin. Pre-service bulletin floats could lose buoyancy and increase the likelihood of carburettor flooding, also characterised by the presence of fuel odour. 

The float bowl of the right carburettor was also contaminated, and one of the float guide pins was bent, causing a float to contact the side of the bowl.

A number of fuel lines were destructively inspected. The internal surfaces in some fuel lines were perished and had become brittle, compromising the security of their end fittings. Some of the fire sleeves covering the fuel lines had marks where securing clamps had previously been removed.

Figure B 2: VH-SIP left carburettor condition

Figure B 2: VH-SIP left carburettor condition

Source: ATSB

Figure B 3: VH-SIP left carburettor float needle valve and seat

Figure B 3: VH-SIP left carburettor float needle valve and seat

Source: ATSB

Figure B 4: Left carburettor float condition

Figure B 4: Left carburettor float condition

Source: ATSB, BRP-Rotax, modified by the ATSB

Carburettor contamination

ATSB technical analysis found that the contamination on the left carburettor float needle valve showed that it was corrosion, and the deposit on the valve tip was a carbon-based material. The contamination in the bowls of both carburettors was considered a likely corrosion by-product from the bowls.

The engine manufacturer advised the ATSB that faultless function of the engine could not be guaranteed if contaminants were found in the carburettor bowls. Corrosion on the float needle valve, and the absence of the clip that attaches the float needle valve to the float hinge bracket further increased the risk that the engine would not satisfactorily perform. The engine manufacturer also advised that the deposit on the left carburettor float needle valve could cause flooding and engine rough running at low power settings.

Service bulletins from the manufacturer recommended that if any contamination was found within the carburettor bowl, that the entire fuel system must be inspected and cleaned.

Purpose of safety investigations

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

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

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

Terminology

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

Publishing information 

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2023

image_5.png

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

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

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

[2]     Runway number: the number represents the magnetic heading of the runway.

[3]     Engine revolutions per minute.

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

[5]     Informed participation relies on the premise that before you take part or pay for an activity that you are fully aware of the potential risks and consequences.

[6]     Inboard trailing edge wing sections controlled by the pilot that protrude into the airflow to produce lift and drag, commonly used during take-off, landing and slow flight.

[7]     The glide ratio of an aircraft is the distance of forward travel divided by the altitude lost in that distance.

[8]     Overfilling the float chamber of carburettor.

Occurrence summary

Investigation number AO-2020-065
Occurrence date 28/12/2020
Location Serpentine Airfield
State Western Australia
Report release date 08/03/2023
Report status Final
Investigation level Defined
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Collision with terrain
Occurrence class Accident
Highest injury level Fatal

Aircraft details

Manufacturer Amateur Built Aircraft
Model DYN-AERO MCR01VLA
Registration VH-SIP
Serial number 225
Sector Piston
Operation type General Aviation
Departure point Serpentine Airfield, Western Australia
Destination Serpentine Airfield, Western Australia
Damage Destroyed