CEN17LA271

NTSB accident investigation · Piper PA 32-300 · Rushville, IN · July 5, 2017

Accident · No injuriesLimited investigationFinal report
Date
July 5, 2017, 14:40 local (18:40 UTC)
Place
Rushville, IN
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N112DEPiper PA 32-300
Defining event
Enroute: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed · report February 26, 2019
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA
FAA report
20170705009969A
Case key
95592

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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 · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Engine controls: power leverAircraft › Aircraft power plant · Incorrect service/maintenancePiper PA-32-300: 2 casesAll aircraft: 95 casesProbable cause
Performance/control parameters: powerplant parametersAircraft › Aircraft oper/perf/capability · Attain/maintain not possiblePiper PA-32-300: 1 caseAll aircraft: 81 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Piper PA 32-300 (301)
Category
Airplane
Serial number
32-7940044
Built
1979
Airframe hours
6,396.45
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
52
Injuries
None
Certificates
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

Docket · 2

The files NTSB released with the investigation on March 15, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 926 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.