Skip to content

Atlas / NTSB / CEN17LA271

NTSB CAROL · Event

Event CEN17LA271

2017-07-05 Rushville, Indiana, United States None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

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.

Factual 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

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

Verbatim from NTSB's published report. Source file NTSB_2017_CEN17LA271.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗