Piper PA28 accident near Middlebury, Vermont, December 23, 2016
On December 23, 2016 at about 4:45 pm local time, a 1978 Piper PA28, registered N31202, was substantially damaged in an accident during initial climb near Middlebury, Vermont (Middlebury State 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 improper decision to return to the airport following a partial or complete loss of engine power during takeoff initial climb and his failure to maintain sufficient airspeed while maneuvering, which resulted in exceedance of the critical angle of attack and an aerodynamic stall.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 23, 2016 · about 4:45 pm local time
- Place
- Middlebury, Vermont · Middlebury State · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28 161, built 1978 · all PA28s on the register
- Registration
- N31202 · no longer on the register · serial 28-7816552
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane had not been flown recently, and, before the personal flight, the private pilot cleared snow from the airplane's wings, charged the airplane's battery, and preheated the engine. He then performed a preflight inspection and drained the fuel tanks. The pilot taxied the airplane to the runway and departed. A witness reported that, during the initial climb, the airplane's wings "wagged," then the engine "skipped" and then "went back to normal." Another witness reported that he heard the engine "sputtering" and saw the airplane make a 180° turn back toward the runway. Both witnesses stated that the airplane then quickly descended. The observations of the witnesses are consistent with the pilot losing control of the airplane while attempting to return to the runway following a partial or complete loss of engine power. Examination of the airframe and engine revealed no anomalies that would have precluded normal operation with the exception of the right fuel cap, which remained seated but its gasket exhibited cracking. Although there was no contamination noted in the fuel system during the engine examination, it is possible that water had leaked through the cracked fuel cap gasket and was not completely drained during the pilot's preflight inspection. Then, following the wings being "wagged," the remaining water entered the fuel system and resulted in a partial or total loss of engine power. In response to the power loss, the pilot attempted to return to the runway; however, during the turn, the pilot failed to maintain sufficient airspeed, which resulted in the airplane exceeding its critical angle of attack and entering an aerodynamic stall. The pilot's decision to return to the runway was contrary to FAA guidance that recommended continuing straight ahead following an engine failure on takeoff. The pilot did not hold a medical certificate and had a history of seizures. However, it is unlikely that the pilot had a seizure at the time of the accident as he was taking the medication levetiracetam to prevent seizures, and a seizure would have led to sudden incapacitation, which is inconsistent with the witness observations that indicate an intentional return to the airport. The pilot had been maintained on levetiracetam since 2010 without a complaint about somnolence; therefore, it is unlikely his use of this medication contributed to the accident. Tramadol was identified only in the pilot's urine, which indicated it was used many hours to days before the accident and was no longer present at impairing levels at the time of the accident. Overall, there was no evidence of a medical condition or medication that contributed to the circumstances of this accident.
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
- Loss of engine power (partial) during initial climb defining event
- Loss of control in flight during maneuvering
- Collision with terrain or object (not controlled flight into terrain) during maneuvering
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 750 hours in all
- Medical certificate: Class 3
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 8,582 hours
- Last inspection: annual inspection, June 14, 2016; 10 hours since
- Maximum gross weight: 1,502 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 1,800 hours total
- Fire on the ground
- Operator: PC Air Ventures LTD
The flight
- Departed from: 6B0 Middlebury VT at 4:45 pm
- Destination: 6B0 Middlebury VT
- Flight plan: none
- Runway 19, 2,500 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 180° at 11 knots, gusting 14
- Visibility: 10 statute miles
- Sky: scat at 3,200 ft
- Temperature: 37°F (3°C), dew point 27°F (-3°C)
- Altimeter: 30.26 inHg
- Observation at 4:35 pm from 6B0
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on June 13, 2018. 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, 10 pages | View Download |
| 2 | Most Recent Fueling Record | PDF, 1 page | View Download |
| 3 | Maintenance Log Excerpts | PDF, 6 pages | View Download |
| 4 | Pilot Operating Handbook Excerpts | PDF, 7 pages | View Download |
| 5 | Weather Observations | PDF, 2 pages | View Download |
| 6 | Wreckage Diagram | PDF, 2 pages | View Download |
| 7 | Investigative Photographs | PDF, 8 pages | View Download |
| 8 | Statement of Party Representatives to NTSB Investigation | PDF, 14 pages | View Download |
| 9 | Pilot Toxicological Report | PDF, 1 page | View Download |
| 10 | FAA Safety Team - Aircraft Control After Engine Failure on Takeoff | PDF, 2 pages | View Download |
| 11 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
