FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA145 · Mooney M20E

2 Apr 2024 · Alpine, AR, United States

Mooney M20E · Accident: system/component malfunction/failure (non-power) en route

From Heber Springs Municipal Airport/Charlie Evans Field (HBZ) to Tyler Pounds Regional Airport (TYR)

Report a problem

Event

NTSB case
CEN24LA145
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
0 · 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

Mooney M20E

Aircraft type
Mooney M20
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
N86UM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Heber Springs Municipal Airport/Charlie Evans Field (HBZ), Heber Springs, ARTo Tyler Pounds Regional Airport (TYR), Tyler, TX
Aircraft age
About 58 years (built 1966)
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
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Environmental issues › Physical environment
  • Personnel issues › Task performance

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

NTSB narrative

During cruise flight in a gradual descent, the airplane’s two carbon monoxide (CO) detectors began alerting. The pilot closed the cabin panel vent and opened a small cockpit window and 4 overhead vents. The pilot’s concern “turned to intense worry and fear as [he] noticed a feeling of lethargy and confusion, sort of slow motion coupled with graying peripheral vision.” He attempted to open the cabin door but was unsuccessful. The pilot decided not to continue the flight to the nearest airport, which was about 30 miles from his position; he shut down the engine and performed a forced landing to a field. The pilot reported that after he shut down the engine, his symptoms gradually dissipated, and he did not lose consciousness. During the forced landing, the airplane impacted unsuitable terrain, nosed over, and sustained substantial damage to the forward fuselage. After the accident, the pilot took a photograph of his iPad, which displayed, “Caution, Sentry CO level is 79 ppm.” Postaccident examination of the airplane revealed the exhaust pipe contained an existing repair weld that had multiple cracks. The cracks contained engine oil and exhaust soot deposits, indicating the cracks existed before impact. In addition, a cabin air scat tube displayed residual engine oil, black soot, and missing material in an area next to the exhaust pipe repair weld. The exhaust cracks and damaged scat tubing would have allowed exhaust gases to enter the airplane cabin. The cabin air system contained a junction box, and two of three outlet ducts were covered with sections from an aluminum beer can and hose clamps. The sections of the aluminum beer can were not approved components. The last inspection of the airplane occurred just over 9 months before the accident; the investigation was not able to determine how long the exhaust cracks and damaged tubing may have been present. The pilot’s carboxyhemoglobin level of 1% that was measured less than 2 hours after the accident indicates that he was unlikely to have been experiencing CO poisoning during the off-airport landing or during his reported symptoms. Physiological responses to acute stress likely contributed to those symptoms. Although the pilot did not likely experience CO poisoning, the CO alerts, cracked exhaust pipe, and damaged cabin air tubing indicate he likely was exposed to abnormally high CO concentrations in the cockpit air during the accident flight. Whether CO exposure leads to CO poisoning depends on exposure magnitude and duration, which is why pilots are encouraged to take early protective action when exposure is suspected.

Probable cause

The improper maintenance of the cabin air and exhaust system which resulted in a cracked exhaust pipe and damaged cabin air tubing, and the subsequent elevated carbon monoxide levels in the cockpit and a forced landing to unsuitable terrain after the pilot suspected carbon monoxide poisoning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA145
Event ID
20240402194020
Case number
CEN24LA145
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, 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: 7ca06fd6e407a0f4273dd45b1752321380794f8fcb64e6260a5fdfde2bd96df7; retrieved 2026-09-16T18:38:10.283Z.