N112DE Piper PA 32-300 accident

NTSB CEN17LA271 · 2017-07-05 · Rushville, IN

Docket — crew, injuries and powerplant

Summary

The airline transport pilot and two passengers were on a cross-country flight. While the airplane was descending, the pilot attempted to level off, but the engine did not respond to his throttle input. The pilot decided to divert and began troubleshooting the engine. The pilot could decrease engine power with throttle movement but could not restore engine power with throttle movement. Subsequently, the throttle would not advance past three-fourths of the distance to full throttle application, and the airplane was unable to maintain its altitude. Because the airplane would be unable to reach a nearby airfield, the pilot performed a forced landing to a field, during which the airplane's firewall was substantially damaged. Postaccident examination of the airplane found that the throttle control arm was improperly fastened, resulting in throttle arm slippage, which precluded proper control of the engine. It could not be determined if the throttle arm was improperly fastened during the airplane's last annual inspection, which occurred about 3.5 months before the accident. The airplane had accumulated 12 hours of flight time since the inspection.

Full narrative

On July 5, 2017, about 1440 eastern daylight time, a Piper PA-32-300 airplane, N112DE, performed a forced landing near Rushville, Indiana. The airline transport-rated pilot and two passengers were not injured, and the airplane was substantially damaged. The airplane was registered to Four Aces Escardrille LLC and operated by a private individual under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which operated on a visual flight rules flight plan. The flight originated from Fort Wayne, Indiana, at 1312, and was en route to Jeffersonville, Indiana.According to information provided by the pilot, while descending in altitude, the pilot leveled off and the engine did not respond to his throttle input. The pilot selected a diversion airfield and began troubleshooting the engine. The engine would decrease engine power with throttle movement but would not restore engine power when throttle was added. After troubleshooting the engine, the throttle would not advance past ¾ throw and the airplane was unable to maintain its altitude. Unable to make any nearby airfield, the pilot performed a forced landing to a field. The airplane's firewall was damaged during the forced landing.

Examination of the airplane found that the throttle control arm was improperly fastened resulting in throttle arm slippage. It could not be determined if the throttle arm was improperly fastened during the last annual.

Probable cause

The pilot’s inability to properly control engine power because of an improperly installed throttle control arm, which resulted in a partial loss of engine power and led to a forced landing. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
130
Wind speed (kt)
6
Temperature (F)
84
Distance from field
0.0

Aircraft

RegistrationMakeModelDamageFAR part
N112DE PIPER PA 32-300 SUBS 091

Sequence of events

#OccurrencePhase
1 Enroute Loss of engine power (partial) defining Climb

Findings

Finding
Aircraft-Aircraft power plant-Engine controls-Power lever-Incorrect service/maintenance cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Powerplant parameters-Attain/maintain not possible cause