Engine failure and subsequent takeoff accident involving Piper PA-32-260

Casualties unknown • Rejected take-off after emergency landing, Piper PA-32-260, near Den Burg, NL

A demonstration of engine failure procedures during a sightseeing flight led to an engine shutdown and a subsequent failed takeoff attempt on a field near Texel.

What happened

On June 27, 2002, a Piper PA-32-260, registration PH-LMR, was conducting a 30-minute sightseeing flight near Den Burg (Texel) with a pilot and five passengers. While flying at 1,500 feet, a passenger inquired about engine failure procedures. To demonstrate, the pilot engaged the carburetor heat and reduced power to idle. Following a brief glide, the pilot attempted to restore power, but the engine RPM began to fluctuate and the engine subsequently failed.

After attempting several restarts and checking fuel selectors and pumps, the pilot performed an emergency landing in a grassy field. During the taxiing process, the pilot attempted a new takeoff from the same field. Although the engine restarted and the pilot believed sufficient power was available, the aircraft failed to reach rotation speed. The aircraft transitioned from the grass into a potato field characterized by furrows running perpendicular to the takeoff direction. In an attempt to avoid a ditch at the edge of the field, the pilot applied flaps and attempted to climb, but the main landing gear struck the edge of the ditch, causing it to break off and bringing the aircraft to a halt. There were no injuries among the six occupants, though the aircraft sustained significant damage.

The investigation

The investigation focused on the cause of the initial engine failure and the factors contributing to the failed takeoff. Investigators examined the fuel system of the Piper PA-32-260, which utilizes four separate tanks managed via a four-position selector switch. This system requires the pilot to switch tanks regularly to maintain lateral balance, a design feature that increases pilot workload and the risk of fuel mismanagement.

Findings

  • The initial engine failure was likely caused by the pilot depleting the currently selected fuel tank during the demonstration of engine failure procedures.
  • There is a delay in fuel delivery and carburetor replenishment when switching to a new tank, which contributed to the shutdown.
  • The decision to attempt a takeoff was influenced by the presence of passengers.
  • The combination of the field's length, the condition of the terrain (medium-length grass and potato field furrows), and the total weight of the six occupants prevented the aircraft from achieving the necessary airspeed for a safe departure.

Probable cause

The engine failure was likely caused by the pilot inadvertently exhausting the fuel in the active tank during a demonstration of engine failure procedures, while the subsequent takeoff accident resulted from insufficient runway length and high rolling resistance due to terrain and weight.

Frequently asked questions

What happened in the null aircraft accident near Rejected take-off after emergency landing, Piper PA-32-260, near Den Burg, NL?

A demonstration of engine failure procedures during a sightseeing flight led to an engine shutdown and a subsequent failed takeoff attempt on a field near Texel.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, at Rejected take-off after emergency landing, Piper PA-32-260, near Den Burg, NL.

What was the probable cause of the accident?

The engine failure was likely caused by the pilot inadvertently exhausting the fuel in the active tank during a demonstration of engine failure procedures, while the subsequent takeoff accident resulted from insufficient runway length and high rolling resistance due to terrain and weight.

Loading the flight search…