ERA21LA085 · Cessna 210L
Cessna 210L · Accident: controlled flight into terrain/object (CFIT) en route
From Emanuel County Airport (SBO) to Eagle Neck Airport (1GA0)
Event
- NTSB case
- ERA21LA085
- 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
- 0
- 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 210L
- 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
- N2246S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Emanuel County Airport (SBO), Swainsboro, GATo Eagle Neck Airport (1GA0), Shellman Bluff, GA
- Aircraft age
- About 44 years (built 1976)
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot departed on a visual flight rules (VFR) flight into night instrument meteorological conditions (IMC) to an airport that was not equipped with any instrument approach procedures. Automatic dependent surveillance-broadcast (ADS-B) data showed that, in the final minutes of the accident flight, the pilot turned toward the airport, descended below the reported overcast cloud layer, and flew at altitudes between 100 to 300 ft mean sea level at groundspeeds of 100 to 115 knots. While descending, the airplane impacted 80-100 ft tall pine trees about 5 nautical miles from the destination airport. The pilot’s son reported that the pilot used a GPS and an app on his personal electronic device (PED) in which he had “built a flight path” into the destination airport. It was customary for the pilot to use this app and descend to pattern altitude or below cloud level, then continue to the airport by reference to the ground and the app. Postaccident examination of the airplane revealed no preimpact mechanical anomalies that would have precluded normal operation. The distribution of the wreckage indicated that the airplane impacted terrain in a near-level attitude with high forward velocity. There was no indication that the pilot obtained a weather briefing before departure; however, he did discuss the poor weather conditions at the destination airport with his son via text message and stated that he would check the weather before he departed. Although the pilot was instrument rated, he chose to fly VFR in low instrument flight rules (IFR) conditions over a dark swamp into an airport with no instrument approach procedures rather than file an IFR flight plan to an airport with an instrument approach. The pilot was expected at work at a nearby hospital emergency room the next morning, and it is likely that his desire to be at work contributed to his decision. Although conditions were conducive to the development of spatial disorientation, the airplane’s low impact angle was more consistent with controlled flight into terrain rather than a loss of control due to spatial disorientation. The extremely low altitude and moderate speeds at which the pilot was operating under the impoverished visual conditions at the time of the accident, and his reported use of a PED for navigation and hazard avoidance, would have made precise altitude control challenging given the division of attention and workload required. Given the impoverished visual conditions, low altitude, and the distance from the airport, the pilot likely would have had difficulty identifying the airport environment. He may have been attempting to locate the airport and lost awareness of the airplane’s altitude as it continued to descend until it impacted trees.
Probable cause
The pilot's intentional visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain. Contributing to the accident was the pressure to complete the flight to work in an emergency room.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA085
- Event ID
- 20201221102445
- Case number
- ERA21LA085
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-12-21.
- API snapshot SHA-256: a848adcfe931d414baf12277b741d116f2cd46cd28d0a7ea388cfd12a72c3253; retrieved 2026-09-15T07:23:52.686Z.