Gear-up forced landing following engine power loss

Casualties unknown • Minneapolis, MN, US

A pilot performed a gear-up forced landing after experiencing a substantial loss of engine power immediately following landing gear retraction.

What happened

Following a normal preflight and engine run-up, the pilot of a Cessna (type not specified in source) was cleared for takeoff. After advancing the throttle to 1,270 pounds of torque and releasing the brakes, the aircraft reached 85 knots, rotated, and achieved a positive rate of climb. The pilot then retracted the landing gear.

Immediately after the wheels were up, the engine experienced a substantial loss of power, described by the pilot as feeling like an engine running on half its cylinders. The pilot reduced power to idle and focused on returning the aircraft to the runway. The aircraft performed a gear-up forced landing. After touching down, the pilot activated the emergency fuel cutoff, traveled across a taxiway, and came to rest approximately 100 yards past said taxiway. The pilot then shut off the battery and exited through the rear door. The aircraft sustained substantial damage.

The investigation

The engine had 183 hours since new. Although the pilot reported a propeller overspeed warning during a flight prior to the accident, the tach generator was replaced following this incident; subsequent testing of the removed tach generator showed no discrepancies. A teardown inspection of the engine failed to identify any malfunctions or failures capable of causing the power loss.

Investigators examined both the primary and overspeed propeller governors. The primary governor's airbleed system reset-eccentric screw featured non-standard lockwire and the torque sealant had been removed. On the overspeed governor, the inside of the speed setting hex screw lacked torque sealant, and the external sealant was cracked. Bench testing revealed that the overspeed governor was set to a lower RPM than the primary governor, meaning it was controlling the system. Flight tests using these specific settings indicated propeller RPM was limited between 96-97% and stabilized quickly.

Probable cause

The investigation focused on the improper calibration of the propeller governors, specifically that the overspeed governor was set to a lower RPM than the primary governor, effectively controlling the system.

Frequently asked questions

What happened in the 2004-01-19 Piper PA-46-500TP accident near Minneapolis, MN?

A pilot performed a gear-up forced landing after experiencing a substantial loss of engine power immediately following landing gear retraction.

What aircraft was involved and where did it happen?

The accident on 2004-01-19 involved a Piper PA-46-500TP, registration N1968W, at Minneapolis, MN.

What was the probable cause of the accident?

The investigation focused on the improper calibration of the propeller governors, specifically that the overspeed governor was set to a lower RPM than the primary governor, effectively controlling the system.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20040123X00101. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.

Loading the flight search…