CEN10FA063 · Piper PA-31T2
Piper PA-31T2 · Accident: loss of control in flight en route
From Charlevoix Municipal Airport (CVX) to Seneca County Airport (16G)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10FA063
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-31T2
- Aircraft type
- Piper PA-31
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N85EM
- Operator
- Tiffin Aire
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Charlevoix Municipal Airport (CVX), Charlevoix, MITo Seneca County Airport (16G), Tififn, OH
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · descent
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff in the pressurized twin-engine airplane, the pilot was cleared to climb and maintain 16,000 feet. The pilot reported passing through instrument conditions with heavy snow and that he cleared the tops of the clouds at 7,000 feet. The pilot was then cleared to climb and maintain flight level (FL) 230. Radar data showed the airplane's altitude and course varied throughout the flight after having reached FL 230. Several times during the flight the air traffic controller questioned the pilot regarding his altitude and/or course. Each time the pilot responded that he was at the correct altitude and/or course. The radar data showed that after each of these conversations, the airplane would return to the assigned altitude and/or course. The controller then informed the pilot that, because radar showed the airplane’s altitude fluctuating between FL 224 and FL 237, he was going to have to descend out of positive controller airspace. The pilot acknowledged this transmission. The controller instructed the pilot to descend to 17,000 feet. The last transmission from the pilot was when he acknowledged the descent. Radar data showed that one minute later the airplane was at FL 234. During the last minute and 12 seconds of radar data, the airplane reversed its course and descended from FL 233 to FL 214, at which time radar data was lost. Witnesses reported hearing loud engine sounds and seeing the airplane in a spiraling descent until ground impact. Postaccident inspection of the engines did not identify any anomalies that would have precluded normal operation. Most of the fuselage was consumed by fire; however, flight control continuity was established. Given the pilot’s experience and the flight’s altitude and course variations the investigation considered that the pilot may have suffered from hypoxia; however, due to the postimpact fire the functionality of the airplane’s pressurization system could not be observed and no conclusive determination could be made that the pilot was impaired.
Probable cause
A loss of aircraft control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10FA063
- Event ID
- 20091204X30446
- Case number
- CEN10FA063
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 22c65b2806c0264bb7c6dd0d13335febb9a1438ba1c8f09dbef2f361dedf2a51; retrieved 2026-09-13T20:35:06.693Z.