CEN23FA190 · Beech E-90
Beech E-90 · Accident: loss of control in flight on approach
From University Oxford Airport (UOX) to Drake Field (FYV)
Event
- NTSB case
- CEN23FA190
- 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
Beech E-90
- Aircraft type
- Beechcraft E-90
- 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
- N522MJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From University Oxford Airport (UOX), Oxford, MSTo Drake Field (FYV), Fayetteville, AR
- Aircraft age
- About 50 years (built 1973)
- 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
- Approach · IFR initial approach
- 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
- Personnel issues › Action/decision
- 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 airplane was being flown to another airport for maintenance work on the autopilot system. Before the flight, the pilot and an avionics technician discussed a roll issue with the airplane’s autopilot and the pilot was advised not to use the autopilot until the issue was resolved. The avionics technician further advised the pilot to wait for good weather to make the flight, but the pilot reportedly had a function back home that he wanted to attend later, on the day of the accident.
Recorded flight track data indicated that most of the flight was uneventful until the airplane began its descent toward the intended destination. During the descent, the airplane encountered overcast clouds that continued to the end of the flight. The pilot was subsequently cleared for an instrument approach to the destination airport. While maneuvering on the approach, the airplane descended below its assigned altitude and the controller issued a low-altitude alert to the pilot. The airplane briefly climbed before it entered a descending right turn that continued to the end of the recorded data.
Calculations based on recorded flight data revealed the airplane was descending over 15,000 feet per minute shortly before impact. The airplane impacted the ground near the final recorded flight track data point, in a near vertical attitude, and was fragmented. Examination of the airplane, engines, and systems did not reveal any preimpact anomalies that would have precluded normal flight.
Based on the available information, the pilot likely was not using the autopilot due to the known issue with the system and, as a result, was hand flying the airplane during the instrument approach. The pilot likely was accustomed to flying the airplane with the automation that the autopilot provided rather than by hand in single-pilot instrument meteorological conditions (IMC). Based on the recorded flight path, it is likely that the pilot became spatially disoriented and lost control of the airplane while intercepting the final approach course for the instrument approach. In addition, the pilot allowed his self-imposed pressure to influence his decision to complete the flight in less-than-ideal weather conditions without a functional autopilot.
Although ethanol was detected in liver and muscle tissue, it is likely that some, or all, of the detected ethanol was from postmortem production. Thus, it is unlikely that ethanol contributed to the accident. Tadalafil, salicylic acid, famotidine, atenolol, and irbesartan were detected in liver and muscle tissue, but it is unlikely that these substances contributed to the accident.
Probable cause
The pilot’s poor preflight decision to depart into known instrument meteorological conditions (IMC) without a functional autopilot system, which resulted in spatial disorientation and his failure to maintain aircraft control while flying in IMC during the instrument approach. Contributing to the accident was the pilot’s self-imposed pressure to conduct the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA190
- Event ID
- 20230517174548
- Case number
- CEN23FA190
- 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, coordinates, cause areas. 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: 4c239e7e9c391ffae445de407cd30c61d2ed61d9adba42e970f9b98a1192f8af; retrieved 2026-09-15T08:00:06.102Z.