CEN19FA210 · Beech A36
Beech A36 · Accident: loss of engine power (total) en route
From Smyrna Airport (MQY) to Bolingbrook's Clow International Airport (1C5)
Event
- NTSB case
- CEN19FA210
- 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
- Visual Meteorological Cond
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N1809S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Smyrna Airport (MQY), Smyrna, TNTo Bolingbrook's Clow International Airport (1C5), Bolingbrook, IL
- Aircraft age
- About 38 years (built 1981)
- 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 engine power (total)
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during a cross-country flight, while in cruise altitude at 3,000 ft mean sea level, the engine lost power. He subsequently performed a forced landing to a muddy wheat field. Examination at the site revealed that the left and right main fuel tanks were intact; the left tank was empty and the right tank contained about 25 gallons. The wing tip tanks were breached during the accident, but burns in the field were indicative of fuel being in the wing tip tanks at the time they were breached. The fuel selector was found in the left tank position.
Further examination revealed that the fuel line from the fuel selector to the engine-driven fuel pump contained no fuel. A test run of the engine revealed no anomalies. Given the absence of fuel in the left tank, the position of the fuel selector at the accident site, and the engine's nominal performance during a postaccident test run, it is likely that the engine consumed all of the available fuel in the left fuel tank, which resulted in fuel starvation and a subsequent total loss of engine power.
Probable cause
A total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19FA210
- Event ID
- 20190706X03014
- Case number
- CEN19FA210
- 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: 6f77bf2a6230d96aa061abc45b3cc00e7652657d695071da72fe8f909fc26f47; retrieved 2026-09-15T07:01:25.526Z.