Stampe SV4C crashes at Weybourne Airfield following runway misidentification

Casualties unknown • Weybourne (Muckleburgh) Airfield, Norfolk, GB

A private flight in a Stampe SV4C ended in an inverted crash at Weybourne Airfield after the pilot misidentified the available runways.

What happened

On 26 July 2008, a Stampe SV4C, registration G-BNYZ, was conducting a private flight to Weybourne (Muckleburgh) Airfield in Norfolk. This was the pilot's first visit to the airfield. During flight planning, the pilot consulted two different flight guides which provided conflicting information regarding the runway identifiers and lengths.

Following a forecast wind of 280º/5-6 kt, the pilot joined an extended downwind leg for a left-hand circuit to land on Runway 34. However, due to the conflicting data in the flight guides, the pilot unknowingly joined the circuit for Runway 03. Because this runway was significantly shorter than intended, the pilot had to perform a steep approach to clear nearby trees, resulting in a long float during the landing flare.

An initial go-around was attempted using a short-field technique. During this second approach, the landing roll exceeded the available distance, prompting a third go-around attempt. During this maneuver, the right lower wing and landing gear struck a concrete post supporting a barbed wire perimeter fence. The impact caused the ailerons to jam in a neutral position.

During the subsequent landing, the pilot experienced a loud bang and a jerk through the landing gear. The aircraft subsequently pitched over onto its back. The two persons on board sustained minor injuries.

The investigation

The AAIB examined the sequence of events and the pilot's use of flight information. The investigation established that the pilot had misidentified the runway layout due to discrepancies between the Pooleys and Lockyears flight guides. The investigation also looked into the mechanical state of the aircraft following the impact with the perimeter fence and the subsequent inversion.

Findings

  • The pilot misidentified the runways at the airfield due to conflicting descriptions of runway lengths and orientations in different flight guides.
  • The pilot attempted to land on a runway that was insufficient in length for the landing roll, particularly given the tailwind and downslope conditions.
  • The primary cause was the misidentification of the runway caused by inconsistent information in the consulted flight guides.

Probable cause

The pilot misidentified the runway at Weybourne Airfield because the flight guides consulted during planning provided conflicting information regarding runway lengths and designations, leading to an approach on a runway that was too short for the landing conditions.

Frequently asked questions

What happened in the 2008-07-26 Stampe SV4C accident near Weybourne (Muckleburgh) Airfield, Norfolk, GB?

A private flight in a Stampe SV4C ended in an inverted crash at Weybourne Airfield after the pilot misidentified the available runways.

What aircraft was involved and where did it happen?

The accident on 2008-07-26 involved a Stampe SV4C, registration G-BNYZ, at Weybourne (Muckleburgh) Airfield, Norfolk, GB.

What was the probable cause of the accident?

The pilot misidentified the runway at Weybourne Airfield because the flight guides consulted during planning provided conflicting information regarding runway lengths and designations, leading to an approach on a runway that was too short for the landing conditions.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.