Cessna 150 stalled in strong and gusty winds

A Cessna 150 stalled shortly after taking off in strong and gusty wind conditions at Bacchus Marsh, north‑west of Melbourne, and was too low to recover before colliding with terrain, an ATSB investigation has concluded. 

On the morning of 22 October 2024, a solo pilot intended to fly the Cessna 150L single piston‑engine aircraft from Bacchus Marsh Aerodrome, to Lethbridge, Victoria.

After lining up on runway 27 in strong and gusting winds, the pilot began and then rejected a take‑off roll.

The pilot broadcast the rejected take‑off on the aerodrome’s common traffic advisory frequency, but did not provide any further information as to why the take‑off was rejected.

The pilot then returned to the end of runway 27 and began a second take‑off attempt.

After leaving the runway the aircraft climbed 150 ft, before pitching steeply nose‑up.

Witnesses then observed the nose, then the left wing, drop, before the aircraft entered a vertical descent and collided with terrain in a paddock beside the airfield.

The aircraft was destroyed, and the pilot was fatally injured.

An ATSB transport safety investigation did not identify any issues with the aircraft which could have contributed to the accident, and a post‑mortem examination did not find any evidence of pilot incapacitation or substances which could have affected their capacity to perform the flight.

The investigation concluded the aircraft was probably too slow on take‑off in the strong and gusty wind conditions, and that inputs made to counteract the crosswind increased the angle of attack of the left wing.

“These factors, combined with the wind conditions, increased the risk of a quick and unrecoverable stall,” ATSB Chief Commissioner Angus Mitchell said.

“The stall occurred too close to the ground for the aircraft to be recovered from.”

While an aerodynamic stall can occur at any airspeed, altitude or engine power setting, Mr Mitchell said this accident demonstrated why they are most hazardous during take‑off and landing, when the aircraft is close to the ground.

“When gusting conditions are present, pilots should consider waiting for more benign conditions,” he said.

“Guidance advises pilots to conduct their own testing in progressively higher winds to determine both their own capability and that of the aircraft.”

“If pilots judge weather to be suitable, they should consider climbing out at a higher airspeed to provide a buffer above their aircraft’s stall speed for detection and correction of an impending stall.”

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

Propeller strike of a taxiway edge light involving Beechcraft King Air B200C, VH-RFD, Hobart Airport, Tasmania, on 1 July 2025

Final report

Report release date: 05/12/2025

Investigation summary

What happened

At 1807 local time on the evening of 1 July 2025, a Royal Flying Doctor Service, Beechcraft King Air B200, registered VH-RFD, with 2 pilots and a paramedic on board, taxied at Hobart Airport, Tasmania, for a night flight to Launceston. As the aircraft taxied to conduct a 180° turn using the runway 30 turnaround pad, it struck a taxi light with the right propeller. The aircraft incurred damage to the propeller and a turnaround pad edge taxi light was also damaged.

After recognising the strike had occurred, the pilots reported it to air traffic control, returned to the parking apron and grounded the aircraft.

What the ATSB found

The ATSB found that the pilot flying subconsciously mistook the blue taxiway edge lights and double yellow line on the edge of the turning pad as taxi centreline guidance. This resulted in the pilot deviating from the marked taxiway centreline towards the runway edge light, resulting in the propeller strike.

The ATSB also found that the supervising pilot’s intervention did not occur in time to prompt the pilot flying to adjust the taxi route before impacting the edge light.

Safety message

All pilots are susceptible to human error. This incident highlights that pilots need to be vigilant and maintain an awareness of their location. 

The airport environment contains numerous visual aids, markings, signals and signs. Pilots must remain situationally aware of their location, traffic and intended ground tracks to avoid obstacles. When the taxiway is suitable for the aircraft type, it is usually safest to follow the yellow line when taxiing at night, in reduced visibility or at an unfamiliar aerodrome. 

Additionally, effective monitoring in a multi-crew environment is also paramount to aircraft safety. Bringing deviations to the early attention of the pilot flying promptly ensures the aircraft remains on a desirable track.

 

The investigation

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

The occurrence

At 1807 local time on 1 July 2025, a Beechcraft King Air B200, registered VH-RFD, operated by the Royal Flying Doctor Service (RFDS) with 2 pilots and a paramedic on board, commenced taxiing at Hobart Airport, Tasmania. The intended destination for this flight was Launceston Airport. It was dark, with little to no moonlight, and good visibility.

The pilot flying (PF) was operating under the guidance of a supervisory pilot (SP), prior to their final line check,[1] which was scheduled in 2 shifts time. The PF occupied the left‑hand side control seat in the cockpit. The SP, who was also designated pilot in command (PIC),[2] occupied the right-hand control seat. 

At 1810, the aircraft entered runway 30 to backtrack[3] so that the full runway length could be used for take-off (Figure 1).

Figure 1: Taxi route

Picture showing the taxi route during the occurrence.

Source: Google Earth, annotated by the ATSB 

The pilots reported that a common technique for taxiing and turning the King Air B200 is to make a wide arc turn to reduce stress on undercarriage components.

During taxi, the PF steered the aircraft away from the centreline taxiway ground markings, toward the right runway edge, approximately 100 m prior to the runway threshold (Figure 1, label 1). This manoeuvre was to position the aircraft for a 180° turn via the runway turnaround pad (a wide, paved area that allows room for aircraft to reverse taxi direction).

The pilot reported that they subconsciously mistook the blue taxiway edge lights and double yellow line on the edge of the turning pad as taxi centreline guidance. This subsequently resulted in positioning the aircraft to the far right of the turning pad, aligning the aircraft with the double yellow line runway edge light rather than the single yellow line. A reconstructed visual perspective, replicating what the pilot may have seen is shown in Figure 2. 

Figure 2: Reconstructed pilot view, approaching and entering the turnaround pad

Picture reconstructing the pilots visual perspective, as they approached the turning node.

These images were taken post-occurrence. The height of the camera was lower than the pilot’s sightline during the incident. Source: Hobart Airport, annotated by the ATSB 

The wide turn taken by the PF was consistent with what was expected by the SP. As the aircraft approached the right side of the turnaround pad, the SP recalled that they were waiting for the PF to turn the aircraft as it came into the proximity of a taxiway edge light. Once the SP identified that the aircraft was close to the edge light, the SP advised the PF. However, before the PF could steer away from the light, the right propeller struck it (Figure 1, label 2). 

Suspecting the aircraft had struck the light, the PF requested from air traffic control (ATC) clearance to conduct a further ground inspection to assess for damage (Figure 1, label 3 and label 4). 

The pilot then confirmed with ATC that the aircraft had struck the light (Figure 3) and advised that they would need to return to the apron. 

Figure 3: Blue pad edge light damage

Picture of damaged taxi light and replacement taxi light.

Source: Hobart Airport, annotated by the ATSB

After shutting down the aircraft, the pilots inspected the aircraft and identified damage to the right-hand side propeller (Figure 4).

Figure 4: Propeller damage

Picture showing damage to right propeller after striking the taxi light.

Source: RFDS

Context

Pilot information

Pilot flying 

The PF held a commercial pilot (aeroplane) license and a valid class 1 aviation medical certificate. They reported a total flying time of about 4,920 hours with about 76 of those being on the King Air B200, having joined the RFDS in April 2025. They reported completing 5 previous flights to Hobart prior to the occurrence, as part of their line training under supervision. All except one of those flights involved the runway 30 threshold being displaced, and they did not utilise the turnaround pad. 

Prior to joining the RFDS, the pilot had held training and examining approvals as well as key management positions at another operator. 

Prior to the incident, the SP had assessed the PF as capable and their flying standard was reflective of that of a candidate approaching their final check. 

Supervisory pilot

The SP held an air transport pilot (aeroplane) license and a valid class 1 medical. They reported a total flying time of 11,848 hours with 4,876 of these hours being on the King Air B200. They also held a management pilot role.[4]

Aircraft information

The Beechcraft King Air B200 is a pressurised, low-wing, twin turbine-engine aircraft with retractable landing gear. The aircraft had a certified maximum take-off weight of 5,667 kg and could be flown by a single pilot. The aircraft, serial number BL-171, was manufactured in the United States in 2014 and subsequently registered in Australia on 14 August 2014. The Royal Flying Doctor Service of Australia (South Eastern Section) had been the registered operator of the aircraft since August 2014. 

Airport information

Hobart Airport is a certified airport consisting of one runway. Runway 12/30 was aligned north-west to south-east and was 2,727 m long and 45 m wide. The aircraft movement areas could accommodate aircraft with a wingspan of up to 36 m (such as a Boeing 737).

There were line markings and lights on the runway and turnaround pad to guide pilots in turning and lining up their aircraft for departure (Figure 5). The markings and design appeared to be consistent with the requirements of the Civil Aviation Safety Authority Part 139 Manual of Standards.

Figure 5: Illustrations (top) and photograph (bottom) of lights and line guidance at the turnaround pad

Illustration showing location of lights and markings at runway turnaround pad.

Source: Hobart Airport and Google Earth, annotated by the ATSB

RFDS operational induction 

When a new pilot joins the RFDS, the operator carries out a structured induction and training program. Initially, a new pilot undertakes type/class training on the King Air B200 which includes an instrument proficiency check (IPC[5]). Following this training, the new pilot conducts line training flights in the presence of an RFDS supervisory pilot. 

The objective of supervised line operations (line training) is to prepare the new pilot for single pilot, unsupervised line operations. The required training outcomes for the new pilot are: 

  • obtaining the required operational experience
  • exposure to and gaining experience of the RFDS’s line operations
  • gaining knowledge of the routes and aerodromes used by the AOC.

Whenever an SP occupies one of the pilot seats, they will be the PIC. These policies and procedures are outlined within the RFDS training and checking systems manual. 

Training and supervising methodology 

Many training methodologies apply the principle of allowing the student to recognise an error and self-correct. This established technique allows the student a chance, and time, to correct themselves, prior to intervention by the instructor or supervisor.

The US Federal Aviation Administration (FAA) Aviation Instructor’s Handbook (2020), which is a recommended reference document for the Civil Aviation Safety Authority’s pilot instructor rating exam, also references this instructional technique. It notes:

Correction of learner errors does not include the practice of taking over from learners immediately when a mistake is made. Safety permitting, it is frequently better to let learners progress part of the way into the mistake and find a way out.

The SP commented that retrospectively, they could have been more assertive and prompter in their intervention once they recognised the proximity of the aircraft to the light.

Safety analysis

Misinterpretation of taxiway/runway visual guidance

While backtracking, the pilot flying (PF) deviated to the right of track in preparation to conduct a wide left turn using the turnaround pad. Making a wide arc turn was a common technique used by pilots for taxiing and turning the King Air B200. As they turned into the turnaround pad, the PF mistakenly manoeuvred the aircraft to align with the blue taxiway edge lights and 2 yellow (edge line) markings. A pilot would normally rely on taxiing guidance of a single yellow line (and green lights), on a taxiway. 

The PF was experienced, having held numerous approvals (training and management). However, in this instance, they reported that they subconsciously mistook the taxiway edge lights and double yellow line on the edge of the turning pad as taxi guidance. Observational audit methodologies, such as the Line Operations Safety Audit (LOSA) have demonstrated that crews make on average between one and five errors per flight sector (Thomas & Petrilli, 2004). 

Supervisor pilot delayed intervention

The SP monitored the PF’s taxiing path as the aircraft deviated toward the right edge of the runway. This path was initially as expected by the SP reflecting normal operations for turning around using the turnaround pad. 

The SP instructed the PF to correct their track when in proximity to the pad edge light, however due to the limited time available and proximity, a strike between the right propeller and taxi light still occurred. 

The SP held the belief that the PF was capable, and this assessment may have contributed to delayed intervention, affecting their level of attention when monitoring the taxi path.

The SP adhered to the recognised training techniques in the FAA Aviation Instructor’s Handbook, by allowing the PF a degree of latitude prior to their intervention. However, this action resulted in the SP delaying the intervention and advising the PF of the proximity of the pad edge light, leaving insufficient time to avoid the light. 

The SP recognised, retrospectively, that if they had recognised the proximity of the aircraft to the light earlier, they would have been more assertive and more prompt in their intervention. 

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 propeller strike of a taxiway edge light involving Beechcraft King Air B200C, VH-RFD, at Hobart Airport, Tasmania, on 1 July 2025. 

Contributing factors

  • The pilot flying misinterpreted the markings and lights at the turnaround pad. This resulted in the pilot taxiing too close to the taxiway edge light, resulting in a propeller striking the light.
  • The supervising pilot did not allow enough time to prompt the pilot flying to adjust the taxi route, for the intervention to be effective.

Sources and submissions

Sources of information

The sources of information during the investigation included:

  • pilot flying and pilot supervising
  • Royal Flying Doctor Service, South Eastern Section
  • Hobart Airport
  • Civil Aviation Safety Authority
  • Airservices Australia
  • Bureau of Meteorology
  • Flightradar24.

References

Federal Aviation Administration. (2020). Aviation Instructors Handbook. U.S. Department of Transport.

Thomas , M. J., & Petrilli, R. M. (2004). Error Management Training: An investigation of expert pilots’ error management strategies. Adelaide: Centre for Applied Behavioural Science.

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:

  • pilot flying
  • pilot supervising
  • Royal Flying Doctor Service, South Eastern Section
  • Hobart Airport
  • Airservices Australia
  • Civil Aviation Safety Authority.

A submission was received from Hobart Airport. 

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.

About ATSB reports

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

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

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

Publishing information

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

Published by: Australian Transport Safety Bureau

© Commonwealth of Australia 2025

Title: Creative Commons BY - Description: Creative Commons BY

Ownership of intellectual property rights in this publication

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

Creative Commons licence

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

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

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

[1]    A line check is the final pilot’s assessment after line training. After a successful final line check, the pilot is released to a normal line flying operation. See also RFDS operational induction.

[2]    The pilot in command (PIC) of an aircraft is the person aboard an aircraft who is ultimately responsible for its operation and safety during flight.

[3]    Backtrack. To taxi on a runway-in-use, in the opposite direction to the aircraft’s take-off or landing direction.

[4]     Management Pilot means a pilot assigned to management duties

[5]    An instrument proficiency check assesses flying skills and operational knowledge, ensuring the capability to exercise the privileges to conduct a flight under the IFR.

Occurrence summary

Investigation number AO-2025-034
Occurrence date 01/07/2025
Location Hobart Airport
State Tasmania
Report release date 05/12/2025
Report status Final
Investigation level Short
Investigation type Occurrence Investigation
Investigation status Completed
Mode of transport Aviation
Aviation occurrence category Ground strike
Occurrence class Incident
Highest injury level None

Aircraft details

Manufacturer Beechcraft
Model B200C
Registration VH-RFD
Serial number BL-171
Aircraft operator Royal Flying Doctor Service (South Eastern Section)
Sector Turboprop
Operation type Part 135 Air transport operations - smaller aeroplanes
Departure point Hobart Airport, Tasmania
Destination Launceston Airport, Tasmania
Damage Minor

Avalon Airshow accident preliminary report

Video footage from an onboard GoPro camera is aiding the ATSB’s investigation of an aerobatic flight display accident at the Avalon Airshow in March, a preliminary report details.

The Sky Aces display team, comprising four Pitts type aerobatic aircraft operated by Paul Bennet Airshows, was conducting a display during the Australian International Airshow at Avalon Airport, Victoria on the afternoon of 28 March 2025.

One of the aircraft, a Pitts S1‑11X, was performing a solo manoeuvre away from the other three, when it impacted a grassed area to the west of the runway, opposite to the public viewing areas and grandstands.

The aircraft created a 95 m ground scar and debris trail in a south‑south‑westerly direction, before coming to rest upright, facing north, almost opposite to the direction of the impact sequence.

The pilot was seriously injured but was provided first aid before being flown to hospital. 

“On being notified of the accident, the ATSB immediately commenced an investigation, with investigators arriving onsite early the following morning to ensure their evidence collection and accident site mapping activities minimised disruption to the airshow flying display,” ATSB Chief Commissioner Angus Mitchell said.

“After it was examined in situ, the aircraft wreckage was transported to a secure hangar on the airport where investigators conducted a thorough engineering examination that found – to the extent possible – no evidence of any control or airframe issues before the accident.”

Mr Mitchell emphasised that the ATSB’s preliminary report does not include findings or analysis, which will be contained in the final report.

Among the evidence gathered is footage from a forward‑facing GoPro camera from the cockpit of the aircraft, which recorded the accident.

It shows the altimeter indicating 100 ft above runway height at the start of the ‘triple avalanche’ manoeuvre – a basic loop with three snap rolls at the top of the loop.

“The pilot had started this manoeuvre at approximately 200 ft above ground level during previous training flights,” Mr Mitchell noted.

Before the camera’s view was blocked by the pilot’s body position, the footage showed the altimeter indicating a height of 700–800 ft just before the aircraft reached its peak altitude, prior to the snap rolls. This was below the pilot's reported normal minimum altitude for commencing the snap rolls of 1,000 ft.

During the back half of the loop, after the snap rolls, the pilot was unable to arrest the rate of descent before the aircraft impacted the ground.

Mr Mitchell said as the investigation continued it would further review video recordings of the accident flight, and consider preparations for the display, as well as aircraft maintenance records and other components recovered from the accident site.

“The investigation is also reviewing display preparations, survivability factors, and the emergency response plan in place at the airport and for the event,” he added.

Read the preliminary report: Collision with terrain involving Pitts S1-11X, VH-PVX, Avalon Airport, Victoria, on 28 March 2025

Crew injury in the engine room of RTM Weipa, off Gove, Northern Territory, on 23 June 2025

Summary

The ATSB is investigating an incident in which a crewmember was injured in the engine room of the bulk carrier, RTM Weipa, off Gove, Northern Territory, on 23 June 2025.

At about 0900 local time, while the ship was at anchor, the crew were carrying out routine maintenance work on the main engine, when the traversing motor of the overhead gantry crane detached from its mounting and fell near a crewmember, resulting in minor injuries.

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

To date, the ATSB investigation has included:

  • interviewing the vessel's crew and operators
  • communications with the crane equipment manufacturer
  • a preliminary analysis of the equipment condition
  • reviewing the crew and operator's statements
  • reviewing the equipment schematics and operation procedures
  • reviewing the vessel's operational history and associated shipboard procedures.

The continuing investigation will include further examination and analysis of:

  • procedural documentation
  • operational documentation
  • maintenance records
  • equipment design
  • related occurrences.

A final report will be published at the conclusion of the investigation. Should a critical safety issue be identified at any time during the investigation, the ATSB will immediately notify the operators of the ship and the port, and other relevant parties so that appropriate and timely safety action can be taken.

Occurrence summary

Investigation number MO-2025-006
Occurrence date 23/06/2025
Occurrence time and timezone 09:00 Eastern Australia Standard Time
Location Port of Gove
State Northern Territory
Report status Pending
Anticipated completion Q2 2026
Investigation level Short
Investigation type Occurrence Investigation
Investigation phase Examination and analysis
Investigation status Active
Mode of transport Marine
Marine occurrence category Equipment
Highest injury level Minor

Ship details

Name RTM Weipa
IMO number 9341938
Ship type Bulk Carrier
Flag Singapore
Classification society Lloyd's Register
Owner Rio Tinto Shipping Asia Pte
Manager ASP Ship Management Pty Ltd
Destination Port of Gove, Northern Territory
Injuries Crew - 1 (Minor)