ERA23FA330 · Cessna P210 N
Cessna P210 N · Accident: loss of control in flight en route
From Sarasota Bradenton International Airport (SRQ) to Thomaston Upson County Airport (OPN)
Event
- NTSB case
- ERA23FA330
- 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
- Instrument Meteorological Cond
Cessna P210 N
- Aircraft type
- Cessna 210
- 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
- N210JT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), Sarasota, FLTo Thomaston Upson County Airport (OPN), Thomaston, GA
- Aircraft age
- About 43 years (built 1980)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- 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 purpose of the flight was for the pilot to return to his home airport. The pilot filed an instrument flight rules (IFR) flight plan and was cleared to the destination airport by air traffic control (ATC). While enroute, the controller advised the pilot of weather along the route of flight, and the pilot requested deviations around the weather, which were approved. About 7 minutes before the accident, the pilot requested an instrument approach to the destination airport. The controller asked the pilot if he could proceed direct to the initial approach fix for the requested approach, and he responded that he could after he passed an area of weather to his right. About 6 minutes before the accident, the controller instructed the pilot to turn to a heading of 080° when he was able. The pilot responded to the instruction but did not begin the turn. About 4 minutes, and 7 nautical miles, before the accident, the controller advised the pilot of heavy to extreme precipitation at his 2 o’clock position and 5 miles ahead. The pilot acknowledged, stating that he was beginning the turn; the pilot turned about 20° to the right and continued on a heading of about 340°. About 30 seconds later, and 1 nautical mile before the accident, the airplane began a right tightening and descending turn consistent with a loss of airplane control until the final track data point. The final seconds of flight track data and debris distribution were consistent with an in-flight breakup of the airplane. Postaccident examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures with the airplane or engine that would have precluded normal operation. All fracture surfaces and control cable fractures were consistent with overload failure. Although the approach control facility was not at its fully authorized staffing level at the time of the accident, sector staffing was in accordance with local and FAA directives and had no impact on the accident. The controller provided weather information to the pilot and suggested routing away from the depicted weather, and when the pilot did not appear to start a turn, the controller used plain language to explain the weather conditions. Had the pilot complied with the initial or secondary issuance of the turn to 080°, the airplane likely would not have entered the area of known convective activity that likely contributed to the loss of control and subsequent in-flight breakup. Information from preflight weather information providers did not show that the pilot received weather information from any of these sources before the accident flight. Had the pilot received a weather briefing, he likely would have observed that the planned route and time of flight were coincident with active convective SIGMETs and forecasted thunderstorms. The airplane was equipped with forward-facing weather radar that could be displayed on multiple instruments in the cockpit. Due to the damage the airplane sustained during the accident sequence the investigation was unable to determine whether the radar was operational or in use at the time of the accident. Had the pilot been using the onboard weather radar, he likely could have utilized it as another tool to assist in avoiding the convective activity.
Probable cause
The pilot’s continued flight into a known area of adverse weather, which resulted in the penetration of a severe thunderstorm, the pilot’s loss of airplane control, and the airplane’s subsequent in-flight breakup.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA330
- Event ID
- 20230810192838
- Case number
- ERA23FA330
- 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: 386417daa7685c6c280f17876af34d7c8f6f6a7b6e8358952ae3be0d01403222; retrieved 2026-09-15T08:04:38.867Z.