FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA095 · Cessna 172

28 Jan 2023 · Hooker, OK, United States

Cessna 172 · Accident: VFR encounter with IMC en route

From Meadow Lake Airport (FLY) to Liberal Mid-America Regional Airport (LBL)

Report a problem

Event

NTSB case
CEN23FA095
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 172

Aircraft type
Cessna 172
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
N6482B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Meadow Lake Airport (FLY), Colorado Springs, COTo Liberal Mid-America Regional Airport (LBL), Liberal, KS
Aircraft age
Not recorded
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
VFR encounter with IMC
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 › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The non-instrument-rated pilot completed a cross-country flight on the morning of the accident in visual meteorological conditions. By the time he departed on what appeared to be a return flight to the airport of origin, weather conditions had deteriorated, and the forecast at the destination airport included 5 statute miles visibility, mist, and a broken ceiling at 800 ft above ground level (agl). Flight track information indicated that, about 2 hours after departure and about one hour after sunset, the airplane entered a decreasing-radius, 720° descending left turn from an altitude of about 4,500 ft mean sea level (msl). The airplane briefly resumed level flight at an altitude of about 3,300 ft msl before track data was lost in the vicinity of the accident site, about 16 nautical miles from the destination airport. Postaccident examination of the airplane did not reveal any preimpact anomalies. Review of weather conditions revealed that, about the time of the accident, the destination airport and another nearby airport both reported an overcast ceiling of 500 ft agl. Review of a model atmospheric sounding for the accident site indicated an overcast cloud layer from about 3,700 ft through 4,900 ft, the presence of icing below about 5,000 ft, and the potential for turbulence between about 10,000 ft and 4,400 ft, including extreme turbulence around 5,000 ft. There was no record of the pilot obtaining a weather briefing from an access-controlled source before departing on the accident flight. Toxicological testing of the pilot detected the synthetic opioid tramadol and its metabolites. Tramadol use may impair psychomotor functioning likely to be important in the performance of complex, divided-attention tasks such as flying. Opioid use can influence judgement and behavior and has been reported to increase the risk of spatial disorientation in pilots. In addition, opioid users have been shown to have decision-making deficits when compared to non-users. Given that the pilot did not hold an instrument rating, and his most recent recorded simulated instrument and night flight experience was about 10 years before the accident, the pilot was susceptible to the development of spatial disorientation while operating in night instrument meteorological conditions. The airplane’s decreasing-radius, descending turns depicted on ADS-B data just before the accident are consistent with the known effects of spatial disorientation. The extent to which his use of tramadol contributed to the loss of control or his decision to depart on or continue the flight into deteriorating weather conditions could not be determined based on the available information.

Probable cause

The pilot’s decision to depart and continue the visual flight rules flight into night instrument meteorological conditions, which resulted in spatial disorientation and a loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA095
Event ID
20230129106645
Case number
CEN23FA095
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, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-01-29.
  • API snapshot SHA-256: d03be32b87bf7e41521c413207878b857dd5df31e9360c5b699e60b54b19e367; retrieved 2026-09-15T07:56:25.965Z.