Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 5, 2017 · Piper PA 32-300 301 · N112DE

Rushville, IN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 5, 2017
Injury Outcomes
No injuries (3 uninjured)
Location
Rushville, IN
Aircraft
Piper PA 32-300 301 (1979)
Tail Number
N112DE
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN17LA271

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.

NTSB 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.

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.

Flight

Event TypeAccident
Event Time14:40 EDT
Nearest Airport0nm
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA 32-300 301
Tail NumberN112DE
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-K1G5 · Reciprocating · 300
Seats6

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 52 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind130° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F
Altimeter30.09 inHg
Observation Time18:53
Weather SourceWFAC

Appendix: Source Data