ERA19LA095 · Cessna 150 F
Cessna 150 F · Accident: fuel exhaustion en route
From Suffolk Executive Airport (SFQ) to Suffolk Executive Airport (SFQ)
Event
- NTSB case
- ERA19LA095
- 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
Cessna 150 F
- Aircraft type
- Cessna 150
- 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
- N6789F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Suffolk Executive Airport (SFQ), Suffolk, VATo Suffolk Executive Airport (SFQ), Suffolk, VA
- Aircraft age
- About 53 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
- Fuel exhaustion
- 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 was performing a post-maintenance test flight. The mechanic who conducted the maintenance reported that the pilot performed about 30 minutes of ground testing before departure. The pilot then remained in the airport traffic pattern and conducted several landings before departing the area to conduct maneuvers for about 30 minutes. The pilot reported that, following the maneuvers, the airplane had a complete electrical failure, and, shortly thereafter, the engine lost total power. He performed a forced landing into a marsh, during which the airplane sustained substantial damage.
About 1 cup of fuel was drained from the fuel system. Both wing fuel tanks were empty of fuel, and there were no signs of fuel leakage. Examination of the engine did not reveal any anomalies that would have prevented normal operation. The reason for the reported electrical failure was not determined; however, given the available information, it is likely that the loss of engine power was the result of fuel exhaustion.
Probable cause
A total loss of engine power due to fuel exhaustion, which resulted from the pilot's improper fuel planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19LA095
- Event ID
- 20190204X30039
- Case number
- ERA19LA095
- 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. 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: 8a5220d139e0e54ae691245edb25a72ab3d7baa2c7f01993579ecbe8cb708fc7; retrieved 2026-09-16T08:34:49.188Z.