No fatalities

1967-09-21: Vickers Viscount (EI-AKK) — Aer Lingus — Bristol-Lulsgate, United Kingdom

Bristol-Lulsgate, United KingdomLanding (descent or approach)

On September 21, 1967, a Vickers Viscount (registration EI-AKK) operated by Aer Lingus was involved in an aviation accident near Bristol-Lulsgate, United Kingdom during landing or approach. No fatalities were reported. Investigators recorded the probable cause as: The accident resulted from the pilot's decision to continue the approach after losing visual references below the critical height, followed by a low-altitude maneuver that caused the aircraft to strike the runway. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 6 related events involving the same aircraft type or operator are linked below.

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781239586Data APIEditorial standards
Aircraft registered EI-AKK
Aircraft registered EI-AKK. Photo: Joop van Bilsen for Anefo / CC0, via Wikimedia Commons

An aircraft experienced a loss of visual references during its final approach to runway 28, resulting in a ground loop and subsequent crash near the airport perimeter.

What happened

During an approach to Lulsgate Airport, the crew operated under deteriorating weather conditions. While initial forecasts for nearby Filton were favorable, visibility at Lulsgate dropped to 1,200 meters during the descent. The aircraft began its approach on a right-hand base leg, initially drifting left of the extended centerline before regaining the track. As the descent continued, the pilot reported that visual references to the horizon and ground were lost below 650 feet due to mist and a thin cloud layer.

While descending through 300 feet, the pilot identified the approach lights to the left and initiated a turn to align with the runway. During this maneuver, the aircraft's airspeed was reduced from 130 knots to approximately 112 knots. Although the pilot briefly lost sight of the lights, they chose to continue the descent based on the last reported visibility. Upon regaining visual contact, the aircraft was positioned over the left side of the runway and was not properly aligned with the centerline.

As the pilot attempted to correct the alignment during the flare, the number 4 propeller and the starboard wingtip made contact with the runway surface. The aircraft touched down on all wheels with significant lateral drift. In an attempt to overshoot the runway and avoid buildings on the northern perimeter, the pilot applied full power and retracted the undercarriage. However, the aircraft failed to accelerate normally, leading to a ground loop to the right. The aircraft eventually struck a fence tail-first. The incident resulted in 10 injuries, with three classified as serious.

Findings

  • The flight crew continued the approach after visual guidance was lost below the critical height.
  • An attempt to realign the aircraft with the runway centerline at an insufficient altitude led to the initial contact with the runway surface.

Probable cause

The accident resulted from the pilot's decision to continue the approach after losing visual references below the critical height, followed by a low-altitude maneuver that caused the aircraft to strike the runway.