No fatalities

Aircraft Mishap at Lulsgate During Instrument Approach (EI-AKK)

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 was caused by an attempt to align the aircraft with the runway at too low a height following the commander's incorrect decision to continue the approach when visual guidance became obscured below critical height. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 7 related events involving the same aircraft type or operator are linked below.

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

An aircraft attempted an instrument approach to runway 28 at Lulsgate, struck the runway during a low altitude alignment turn, and crashed through a fence after an aborted go-around, injuring ten occupants.

Background and Weather Conditions Dublin weather was not available for Lulsgate at departure, though conditions at Filton, 10 miles north, were above company minima. Near Strumble, updated weather indicated 3/8 cloud at 1,000 ft and 1,500 m visibility with sun dispersing mist. The latest report before final approach showed northerly winds at 8-10 kt, QFE 979, QNH 1001, and 1,800 m visibility in mist, though it later deteriorated to 1,200 m during the approach. During the approach to runway 28, the aircraft initially drifted left of the extended centerline. The commander reported the air was calm and achieved precise altitudes and track. However, a drift to the right became apparent during the final segment. Radar controllers provided left heading corrections from 287° to 275°, but the aircraft remained right of centerline. At half-mile, the controller stated the aircraft was well right and should overshoot if the runway was not in sight. The commander noted visual reference was maintained until about 650 ft, after which a thin layer of cloud and mist required an instrument approach. While descending through 300 ft, the commander saw approach lights to his left. To align with them, he applied 400 of flap and reduced power to slow the aircraft from 130 kt to approximately 112 kt. Contact with the lights was lost for several seconds, but the commander continued the approach, confident the runway lights would appear. The lights came into view with the aircraft over the left-hand side of the runway. During the flare, the commander attempted to turn onto the centerline. Unaware at the time, the starboard wing tip and No. 4 propeller struck the runway. The aircraft touched down on all wheels with considerable port drift. The commander initiated an overshoot action, applying full power and retracting the undercarriage. As airspeed fell below 100 kt, the aircraft failed to accelerate normally and began heading toward buildings on the northern perimeter. To avoid these obstructions, the commander flew the aircraft onto the ground. The aircraft touched down starboard wing first, ground-looped right, and crashed tail-first through a fence. Ten passengers were injured, three seriously. No fire occurred, and the accident happened at 0759 hours.

Probable cause

The accident was caused by an attempt to align the aircraft with the runway at too low a height following the commander's incorrect decision to continue the approach when visual guidance became obscured below critical height. A crash landing became necessary during an attempted overshoot after the aircraft had touched the ground and sustained damage during a turn at a low height.