Engine failure during flight testing leads to forced landing of X'Air Falcon

Casualties unknown • Near Ham, Taunton, Somerset, GB

A flight test involving a 2g manoeuvre resulted in an engine failure and subsequent forced landing near Ham, Somerset, due to fuel starvation.

What happened

On 18 March 2004, a X'Air Falcon 133(1), registration G-CCNL, was conducting flight testing near Ham, Taunton, Somerset. The mission involved a BMAA test pilot attempting to collect position error correction data and measure stick forces during a 2g Vmax descending turn. While the aircraft was maintaining the required 2g load for approximately six seconds, the engine ceased operation and failed to restart despite throttle inputs.

The crew, having planned the manoeuvre over a large field, attempted a forced landing into the wind. However, the discovery of power lines crossing the field prevented them from orbiting to find a safer landing spot or flying beneath the wires. To lose altitude quickly, the crew performed a side-slip. During the final approach, the aircraft's airspeed was higher than the crew realized, as the wing-mounted pitot-static system was underreading. This caused the aircraft to float during the flare, touching down with only 60 metres of runway remaining. The aircraft ultimately struck a boundary hedge at approximately 10 kt, resulting in no injuries but causing slight damage to the landing gear.

The investigation

The investigation focused on why the engine failed during the high-load manoeuvre and why the approach speed was misjudged. Investigators examined the aircraft's pitot-static system and the carburettor design. It was noted that the pilot was accustomed to a cockpit-mounted system, which is more accurate, whereas the wing-mounted system used during this flight was prone to underreading.

Regarding the engine, the investigation identified a mechanical issue within the PHBE36HS carburettor. The twin floats in the single fuel bowl were connected to the same arm, preventing independent movement. During the high-g turn, this configuration allowed the fuel level in the bowl to drop below the level required to feed the fuel jet.

Findings

  • The engine failure was caused by fuel starvation resulting from a carburettor float level issue.
  • The interconnected twin-float arm design allowed the fuel level to fall too low during extreme manoeuvres.
  • The pilot misjudged the approach speed because the wing-mounted pitot-static system underread the actual airspeed.
  • The presence of power lines restricted the crew's ability to execute a safer landing pattern.

Probable cause

The engine failure was caused by fuel starvation during a 2g manoeuvre due to a design flaw in the carburettor float arm, which was compounded by an approach speed error caused by an underreading pitot-static system.

Frequently asked questions

What happened in the 2004-03-18 X'AIR FALCON 133(1) accident near Near Ham, Taunton, Somerset, GB?

A flight test involving a 2g manoeuvre resulted in an engine failure and subsequent forced landing near Ham, Somerset, due to fuel starvation.

What aircraft was involved and where did it happen?

The accident on 2004-03-18 involved a X'AIR FALCON 133(1), registration G-CCNL, at Near Ham, Taunton, Somerset, GB.

What was the probable cause of the accident?

The engine failure was caused by fuel starvation during a 2g manoeuvre due to a design flaw in the carburettor float arm, which was compounded by an approach speed error caused by an underreading pitot-static system.

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.