# NTSB CEN17LA271: Piper PA 32-300, N112DE, Rushville, IN, July 5, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 5, 2017, 14:40 local (18:40 UTC) - Place: Rushville, IN - Coordinates: 39.868057, -85.754997 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.8681&lon=-85.7550&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report February 26, 2019 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 95592 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN17LA271 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95592/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95592 - Page: https://openairdocs.org/ntsb/CEN17LA271 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine controls: power lever](https://openairdocs.org/ntsb-findings/01057603): Aircraft › Aircraft power plant · Incorrect service/maintenance (probable cause); cases with it: [Piper PA-32-300, 2 cases](https://openairdocs.org/ntsb-findings/01057603/cases.md?model=7103212), [All aircraft, 95 cases](https://openairdocs.org/ntsb-findings/01057603/cases.md) - [Performance/control parameters: powerplant parameters](https://openairdocs.org/ntsb-findings/01062050): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-findings/01062050/cases.md?model=7103212), [All aircraft, 81 cases](https://openairdocs.org/ntsb-findings/01062050/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [Piper PA-32-300, 10 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=7103212), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) ## Analysis 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. ## 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. ## Aircraft - Registration: [N112DE](https://openairdocs.org/deregistered/N112DE-2018-03-15), registration cancelled 2018-03-15, S/N 32-7940044, built 1979 (OpenAirDocs) - Reported make and model: PIPER PA 32-300 (301) - Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32-7940044 - Year built: 1979 - Airframe hours: 6396.45 - Engines: Lycoming IO-540-K1G5 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 24, 2017, 12 hours before - Departed: KFWA, Fort Wayne, IN - Destination: KJVY, Jeffersonville, IN - Flight plan: VFR - Equipment: Stall warning system, Auto-pilot, Electronic flight bag or handheld device, Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 52; injuries: none; flight engineer, airline transport, flight instructor, military; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review April 11, 2017; seat: right; restraint: 3-point; flight hours: 7,158 total, 619 in this make and model, 4,490 as pilot in command, 107 in the last 90 days, 24 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 130° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 66 °F - Altimeter: 30.09 inHg - Observed at: KGEZ, 18 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20170705009969A](https://openairdocs.org/incident/20170705009969A), Jul 5, 2017: Piper PA-32-300, Milroy, IN, Substantial damage. On July 5, 2017 at approximately 1400 eastern standard time, 1.8 miles north of Milroy, IN, a 1979 PA32-300 with 3 souls on board landed in a wheat field. The… ## Docket (2 files) The files NTSB released with the investigation on March 15, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95592. 926 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 874 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460842&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation - FAA (item 2, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40460843&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20FAA-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.