CEN20LA379 · Cirrus SR22 Undesignat
Cirrus SR22 Undesignat · Accident: loss of control in flight en route
From Muskogee-Davis Regional Airport (MKO) to Pickens County Airport (LQK)
Event
- NTSB case
- CEN20LA379
- 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
- 4 · 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
Cirrus SR22 Undesignat
- Aircraft type
- Cirrus SR22
- 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
- N733CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Muskogee-Davis Regional Airport (MKO), Muskogee, OKTo Pickens County Airport (LQK), Pickens, SC
- Aircraft age
- About 19 years (built 2001)
- 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
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The noninstrument-rated pilot and three passengers departed on a visual flight rules (VFR) cross-country flight in dark night visual meteorological conditions. The pilot established contact with air traffic control and requested VFR flight-following to the destination airport; shortly thereafter, the controller provided a 20° right turn around an area of precipitation ahead of the airplane. The pilot acknowledged and flew the suggested heading for a short time before he turned left toward the area of precipitation. When queried by the controller, the pilot replied that he was returning to the departure airport; however, the pilot did not establish a heading toward the airport. When queried again, the pilot stated that, “the wind caught me” and that he was correcting the airplane’s heading. Shortly thereafter, the airplane began a turning descent and radar contact was lost, about 6 minutes after the pilot’s initial contact with air traffic control. The wreckage was found the next day in wooded terrain. Examination did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. Based on flight track and weather information, the pilot likely encountered instrument meteorological conditions and turbulence when the airplane flew in close proximity to an area of convective activity as depicted on radar just before the accident. The pilot’s inability to respond positively to ATC-provided vectors and maintain altitude before the turning descent is consistent with the pilot experiencing spatial disorientation. The pilot’s inability to maintain aircraft control under those conditions was likely exacerbated by the presence of frequent lightning. Although the pilot obtained a weather briefing for the accident flight about 17 hours before the planned departure time, there were no records to indicate that he obtained updated weather information, which would have reflected increased potential for convective activity along the planned route. The pilot purchased the airplane about 8 months before the accident and received transition training in the airplane, which included use of the avionics suite. Instructors who flew with the pilot in the accident airplane reported that the installed avionics was “old technology” and “not easy to use.” Although the airplane was equipped with an autopilot, the extent to which the pilot may have used the autopilot during the accident flight could not be determined. Review of the pilot’s logbook indicated that he did not meet recency of experience requirements to carry passengers at night. Toxicology testing of the pilot revealed the presence of ethanol; however, it is most likely that some or all of the identified low concentration of ethanol was from sources other than ingestion. Thus, the identified ethanol did not contribute to this accident.
Probable cause
The noninstrument-rated pilot’s continued flight into dark night instrument meteorological conditions which resulted in spatial disorientation and a subsequent loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA379
- Event ID
- 20200905X11000
- Case number
- CEN20LA379
- 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-09-05.
- API snapshot SHA-256: 6a71cf3d6df719037b9423b065391f38848450809249c5a2c769d66756638472; retrieved 2026-09-15T07:19:24.102Z.