CEN21FA376 · SOCATA TBM 700 A
SOCATA TBM 700 A · Accident: loss of control in flight en route
From Erie-Ottawa International Airport (PCW) to Cincinnati Municipal Airport Lunken Field (LUK)
Event
- NTSB case
- CEN21FA376
- 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
SOCATA TBM 700 A
- Aircraft type
- Socata TBM-700
- 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
- N700DT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Erie-Ottawa International Airport (PCW), Port Clinton, OHTo Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OH
- Aircraft age
- About 23 years (built 1998)
- 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
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was performing a short cross-country flight, which was his third solo flight in the high-performance single-engine airplane. The airplane departed and climbed to 20,000 ft mean sea level (msl) before beginning to descend. About 8 minutes before the accident, the airplane was southbound, descending to 11,000 ft, and the pilot established communications with air traffic control (ATC). About 4 minutes later, the controller cleared the pilot to descend to 10,000 ft msl and proceed direct to his destination; the pilot acknowledged the clearance. While descending through 13,000 ft msl, the airplane entered a descending left turn. The controller observed the left turn and asked the pilot if everything was alright; there was no response from the pilot. The controller’s further attempts to establish communications were unsuccessful. Following the descending left turn, the airplane entered a high speed, nose-down descent toward terrain. A witness observed the airplane at a high altitude in a steep nose-down descent toward the terrain. The witness noted no signs of distress, such as smoke, fire, or parts coming off the airplane, and he heard the airplane’s engine operating at full throttle. The airplane impacted two powerlines, trees, and the terrain in a shallow descent with a slightly left-wing low attitude. Examination of the accident site revealed a long debris field that was consistent with an impact at a high speed and relatively shallow flightpath angle. All major components of the airplane were located in the debris field at the accident site. Examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. A performance study indicated the airplane entered a left roll and dive during which the airplane exceeded the airspeed, load factor, and bank angle limitations published in the Pilot’s Operating Handbook (POH). An important but unknown factor during these maneuvers was the behavior of the pilot and his activity on the flight controls during the initial roll and dive. The pilot responded normally to ATC communications only 98 seconds before the left roll started. It is difficult to reconcile an alert and attentive pilot with the roll and descent that occurred, but there is insufficient information available to determine whether the pilot was incapacitated or distracted during any part of the roll and dive maneuver. Although all the available toxicological specimens contained ethanol (the alcohol contained in alcoholic drinks such as beer and wine), the levels were very low and below the allowable level for flight (0.04 gm/dl). While it is possible that some of the identified ethanol had been ingested, it is also possible that all or most of the identified ethanol was from sources other than ingestion (such as postmortem production). In either case, the levels were too low to have caused incapacitation. It is therefore unlikely that any effects from ethanol contributed to the circumstances of the accident. There was minimal available autopsy evidence to support any determination of incapacitation. As a result, it could not be determined from the available evidence whether medical incapacitation contributed to the accident.
Probable cause
The pilot’s failure to arrest the airplane’s left roll and rapid descent for reasons that could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21FA376
- Event ID
- 20210820103733
- Case number
- CEN21FA376
- 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, coordinates, cause areas. 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: 90ffccb533531939c6865dd035233a3be5b46e1d48064115f955c5131e684eae; retrieved 2026-09-15T07:33:25.345Z.