Mid-air collision at RNAS Yeovilton involving Starduster and Wasp helicopter

Casualties unknown • RNAS Yeovilton, Somerset, GB

A private flight in a Starduster Too collided with a training Westland Wasp helicopter during approach at RNAS Yeovilton, resulting in serious injuries to the pilot.

What happened

On 5 March 2011, a Starduster Too SA300, registration G-STOO, was performing a left-hand approach to Runway 04 at RNAS Yeovilton. At the same time, a Westland Wasp HAS1, registration G-BZPP, was conducting a training flight. The Wasp was executing its fifth circuit following a simulated hydraulic failure and was in a low hover approximately 150 metres beyond the runway threshold.

As the Wasp began its final descent, the crew experienced a vibration and an uncommandable rightward yaw. This caused the helicopter to roll left, resulting in the main rotor blades striking the ground. The impact caused the left undercarriage to collapse and the aircraft to tip forward. Simultaneously, the pilot of the G-STOO collided with the rear of the G-BZPP. The impact caused the Starduster to crash on the runway, where the pilot sustained serious head injuries.

The investigation

The investigation examined the communication and operational procedures of the Yeovilton Flying Club (YFC). It was established that the pilot of the G-STOO believed he was the only powered aircraft operating, as he had not been informed that another club aircraft would be flying. While the pilot had attempted to contact aircraft on the glider frequency and the Tower frequency, he received no response.

Regarding the G-BZPP, the crew was unaware of the Starduster's presence until the moment of impact. The investigation found that the helicopter's radio was tuned to the Ground frequency rather than the Tower frequency. Furthermore, the co-pilot's transmission key was found to be faulty, which prevented intended transmissions from being recorded on the Tower frequency.

Findings

  • The pilot of the G-STOO was unaware of the Wasp's presence because the Wasp was operating on a different frequency and the pilot had not received updated traffic information.
  • The pilot of the G-STOO had not been notified that another aircraft would be participating in the circuit.
  • The Starduster pilot's seat harness was only partially restraining him at the time of the collision.
  • Inadequate radio frequency coordination and communication procedures were the primary factors leading to the lack of separation between the two aircraft.

Probable cause

The collision occurred because the pilot of the Starduster was unaware of the Wasp's presence due to a lack of communication regarding the presence of other aircraft and the use of different radio frequencies.

Frequently asked questions

What happened in the 2011-03-05 Starduster Too SA300 and Westland Wasp HASI accident near RNAS Yeovilton, Somerset, GB?

A private flight in a Starduster Too collided with a training Westland Wasp helicopter during approach at RNAS Yeovilton, resulting in serious injuries to the pilot.

What aircraft was involved and where did it happen?

The accident on 2011-03-05 involved a Starduster Too SA300 and Westland Wasp HASI, registration G-STOO and, at RNAS Yeovilton, Somerset, GB.

What was the probable cause of the accident?

The collision occurred because the pilot of the Starduster was unaware of the Wasp's presence due to a lack of communication regarding the presence of other aircraft and the use of different radio frequencies.

Loading the flight search…