ERA17FA313 · Cirrus Design Corp SR20
Cirrus Design Corp SR20 · Accident: loss of control in flight en route
From Delaware Coastal Airport (GED) to Fleming Mason Airport (FGX)
Event
- NTSB case
- ERA17FA313
- 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
- 2 · 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
Cirrus Design Corp SR20
- Aircraft type
- Cirrus SR20
- 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
- N135CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Delaware Coastal Airport (GED), Georgetown, DETo Fleming Mason Airport (FGX), Flemingsburg, KY
- Aircraft age
- About 17 years (built 2000)
- 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 · cruise
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before departing on the instrument flight rules cross-country flight, the instrument-rated private pilot received an official weather briefing which included the latest Significant Meteorological Information (SIGMET) valid along the proposed route of flight. While en route at 8,000 ft mean sea level (msl), the controller provided a vector to the pilot to deviate around weather. The pilot accepted the deviation and turned the airplane; shortly thereafter, he reported that the airplane was in an area of moderate-to-heavy precipitation. Several minutes later, the pilot reported that the airplane was clear of the precipitation; he requested and was cleared to resume the on-course heading. The controller subsequently observed the radar return associated with the airplane descending rapidly from 8,000 ft to 5,000 ft before radar contact was lost. Review of the airplane's flight track data showed the airplane descending in a left turn, then making a sharp right turn followed by a sharp left turn; there were no further communications received from the pilot. The wreckage was significantly fragmented, consistent with a high-energy impact and trees in the vicinity of the accident site displayed angular cuts consistent with propeller contact. There was no evidence of mechanical malfunctions or anomalies that would have precluded normal operation.
A cold frontal boundary just west of the accident site provided a moderately unstable environment for the formation of thunderstorms along the route of flight. Review of weather information indicated that the pilot was operating in instrument meteorological conditions and likely turbulence associated with the thunderstorm activity. These conditions are known to be conducive to the development of spatial disorientation. Additionally, the airplane's series of descents and changes in direction before being lost from radar and the evidence of a high-energy impact are consistent with the known effects of spatial disorientation and a subsequent loss of control.
Probable cause
The pilot's loss of airplane control due to spatial disorientation while flying in instrument meteorological conditions in the vicinity of adverse weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17FA313
- Event ID
- 20170907X62615
- Case number
- ERA17FA313
- 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: 2c0be7b1b6e99a524bfaf51af8bd4c13fe21fdedb36c90b87f90bdfea82b6ed2; retrieved 2026-09-15T06:15:32.174Z.