Cessna 210L N2246S
21 December 2020 · Midway, Georgia, United States · Fatal
Summary
On 21 December 2020 at about 01:11 local time, a Cessna 210L registered N2246S was involved in an accident near Midway, Georgia, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 01:11
- Classification
- Accident
- Location
- Midway, Georgia, United States
- Nearest airport
- Eagle Neck (1GA0)
- Coordinates
- 31.7185, -81.3193
- Aircraft
- Cessna 210L
- Registration
- N2246S
- Category
- Airplane
- Year built
- 1976
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Swainsboro → Shellman Bluff
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night
- NTSB number
- ERA21LA085
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 210 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 4 Oct 2020 | Cessna 210 | Cedaredge, Colorado, United States | Soaring 210 LLC | Serious injuries | - |
| 26 Aug 2020 | Cessna 210 | Chino, California, United States | - | No injuries | - |
| 26 Oct 2020 | Cessna 210 | Lubbock, Texas, United States | - | Fatal | 1 |
| 5 Mar 2020 | Cessna 210 | Needles, California, United States | - | Minor injuries | - |
| 19 Sep 2020 | Cessna 210 | Criterion, South Africa | - | Unknown | - |
| 13 Feb 2019 | Cessna 210 | Belém City, State of Pará, Brazil | Alex Sampaio Da Silva | Fatal | 1 |
All 2,022 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 3 May 2020 | Mooney M20K | Athens, Georgia, United States | - | No injuries | - |
| 27 Jun 2020 | Ayres S2R | Perry, Georgia, United States | - | No injuries | - |
| 5 Oct 2020 | Champion 8KCAB | Ellijay, Georgia, United States | - | Minor injuries | - |
| 9 May 2020 | Cessna 402 | Hampton, Georgia, United States | Handel International, LLC | Minor injuries | - |
| 25 Oct 2020 | Grumman AA5 | Baxley, Georgia, United States | Baxley Aviation LLC | Minor injuries | - |
| 17 Aug 2020 | Cessna 182 | Savannah, Georgia, United States | F3EA Inc. | No injuries | - |