Piper PA-38-112 accident near Madison, Indiana, June 16, 2016
On June 16, 2016 at about 4:06 pm local time, a 1978 Piper PA-38-112, registered N2412D, was substantially damaged in an accident during initial climb near Madison, Indiana (Madison Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain a proper climb rate after takeoff and the subsequent collision with transmission line structures.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 16, 2016 · about 4:06 pm local time · cases in 2016
- Place
- Madison, Indiana · Madison Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-38-112, built 1978 · all PA-38-112s on the register
- Registration
- N2412D · no longer on the register · serial 38-79A0300
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot had departed the airport in visual meteorological conditions, when, about ½ mile from the departure end of the runway, the airplane collided with a power transmission line support structure that was about 80 ft tall. The airplane was destroyed by impact forces and a postimpact fire. There were no known witnesses to the accident, but a witness who saw the airplane take off stated that its altitude was low during the initial climb. Postaccident examination of the airframe and engine revealed no mechanical malfunctions or anomalies that would have precluded normal operation. In the months before the accident, the pilot flew with a flight instructor on two separate occasions for a flight review. The instructor stated that the pilot's skills were "very rusty" and that the pilot had difficulty controlling the airplane's airspeed, pitch, and landing flare. The instructor did not endorse the pilot for a flight review and recommended that he receive additional dual instruction; however, it is unknown if the pilot followed this recommendation because his personal logbook was not located after the accident. Given the lack of preimpact mechanical anomalies, it is likely that the pilot did not maintain an appropriate climb rate after takeoff, which resulted in collision with the power line structure.
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
- Controlled flight into terrain or object (CFIT) during initial climb defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Personnel issues › Experience/knowledge › Training › Recurrent instruct/training › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Last inspection: annual inspection, February 6, 2016
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-235-L2C (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: IMS Madison IN at 4:05 pm
- Flight plan: none
- Runway 21, 5,000 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 68°F (20°C)
- Altimeter: 29.82 inHg
- Observation at 4:12 pm from IMS, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
8 documents, released by the NTSB on June 27, 2017. 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 | Airframe and Engine Examination | PDF, 4 pages | View Download |
| 2 | Record of Conversation and Statements | PDF, 3 pages | View Download |
| 3 | Fuel Record | PDF, 1 page | View Download |
| 4 | Maintenance Records | PDF, 14 pages | View Download |
| 5 | Toxicological Report | PDF, 1 page | View Download |
| 6 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 7 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 8 | Photographs | PDF, 11 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N2412D: not on the register today · the record of its deregistration
- Piper PA-38 Tomahawk 442 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming O-235-L2C 84 aircraft carry this series today · as the NTSB recorded it
- Madison Regional · nearest airport
- Accidents and incidents in Indiana 1,367 since 1982 · 179 in the last ten years
- Indiana 5,705 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN16FA220.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.
