Piper PA34 accident near Anderson, Indiana, May 5, 2019
On May 5, 2019 at about 12:30 pm local time, a Piper PA34, registered N999CR, was substantially damaged in an accident during initial climb near Anderson, Indiana (Anderson Muni-Darlington Field). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The loss of left engine power due to an incorrectly adjusted fuel servo and the airplane's nose up trim which resulted in the airplane steep climb, loss of airspeed, and aerodynamic stall and subsequent impact with terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 5, 2019 · about 12:30 pm local time · cases in 2019
- Place
- Anderson, Indiana · Anderson Muni-Darlington Field · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA34 220T · all PA34s on the register
- Registration
- N999CR · no longer on the register · serial 3449143
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot planned to ferry the twin-engine airplane to another airport for the annual maintenance inspection. Several witnesses saw the airplane's departure. Two of the witness reported that the airplane engines didn't sound "normal". Several witnesses reported that the airplane appeared to pitch up, before stalling. A video from the airport's security camera revealed that the airplane appeared to climb steeply; the airplane's wings rocked back-and-forth, and the airplane disappeared out of view. When the airplane reappeared in the camera's view, the airplane was in a descent with the left wing low. The airplane collided with terrain and the airplane cabin area was largely destroyed by the impact. Examination of the airplane found the stabilator trim actuator screw was near its maximum nose up setting. The left engine was removed from the airframe and tested in the engine manufacturers test cell. The engine test run reveled the engine did not produce full rated horsepower and on occasions produced black exhaust which was indicative of a rich fuel air mixture. The fuel servo was replaced with a new unit and the engine was able to produce rated horsepower. Further examination of the original fuel servo showed that the control linkage (rod and link assembly), was installed incorrectly. The accident is consistent with loss of power on the left engine due to an incorrectly installed fuel servo and an excessive nose up trim setting, which resulted in steep climb angle, a loss of airspeed, and an aerodynamic stall.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Aircraft maintenance event during prior to flight
- Loss of engine power (partial) during initial climb
- Aerodynamic stall/spin during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Personnel issues › Task performance › Maintenance › (general) › Not specified
- factor Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel controlling system › Malfunction other cases naming the engine
- Aircraft › Aircraft systems › Flight control system › Aileron tab control system › Incorrect use/operation other cases naming the flight controls
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 100 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 1,819.3 hours
- Last inspection: annual inspection, July 7, 2017; 27.8 hours since
- Landing gear: retractable
- Engine 1: Continential TSIO-360 (piston); 1,792 hours total
- Engine 2: Continential TSIO-360 (piston); 0 hours total
- Operator: Spc Leasing LLC
The flight
- Departed from: AID Anderson IN
- Destination: HHG Huntington IN
- Flight plan: none
- Runway 36, 3,399 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 020° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 48°F (9°C), dew point 46°F (8°C)
- Altimeter: 29.90 inHg
- Observation at 12:35 pm from AID
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 5 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – Wreckage Path
Photo 2 – Accident Airplane
Photo 3 – Engine, readied for test cell
Photo 4 - Fuel servos; accident servo (left), exemplar servo (right)
Photo 5 – Pitch trim Photos – Piper Aircraft CompanyThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
13 documents, released by the NTSB on June 26, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Witness Statements | PDF, 9 pages | View Download |
| 2 | Pilot Statement | PDF, 1 page | View Download |
| 3 | Airplane Owner | PDF, 2 pages | View Download |
| 4 | FAA Inspector Witness | PDF, 2 pages | View Download |
| 5 | Site Overview | PDF, 1 page | View Download |
| 6 | Engine Display | PDF, 1 page | View Download |
| 7 | Maintenance Records | PDF, 5 pages | View Download |
| 8 | Engine Exam Email | PDF, 1 page | View Download |
| 9 | Memo - Seat | PDF, 1 page | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 11 | Ferry Permit | PDF, 4 pages | View Download |
| 12 | Photos | PDF, 5 pages · our copy | View Download |
| 13 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 2 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N999CR the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N999CR: not on the register today · the record of its deregistration
- Piper PA-34 Seneca 997 registered today · the model family and its accident history
- Piper 44,843 aircraft on the register
- Engine: Continential TSIO-360 · as the NTSB recorded it
- Engine: Continential TSIO-360 · as the NTSB recorded it
- Anderson Regional · nearest airport
- Huntington Municipal · bound for
- Accidents and incidents in Indiana 1,367 since 1982 · 179 in the last ten years
- Indiana 5,705 aircraft registered
- Other NTSB records under N999CR 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN19FA135.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
