ATL90LA137 · Cessna 150L
Cessna 150L · Accident: total loss of engine power (non-mechanical) en route
From Triangle North Executive Airport (LFN) to an unrecorded destination
Event
- NTSB case
- ATL90LA137
- 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
- 0
- 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 150L
- 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
- N1408Q
- Operator
- Nolen, Jack R. · private individual
- Onboard fatalities
- Unknown
- Route
- From Triangle North Executive Airport (LFN), LOUISBERG, NCTo not recorded
- 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 · descent
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel consumption calculations, inaccurate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT THE AIRPLANE WAS FUELED FOLLOWED BY A CROSS COUNTRY FLIGHT. HIS FLIGHT PLANNING INDICATED THAT THE FLIGHT WOULD REQUIRE 2.5 HOUS. AFTER 3.5 HOURS THE AIRPLANE WAS ABOUT 8 MILES SHORT OF THE DESTINATION. HE STATED THE INCREASED TIME WAS BECAUSE OF HEADWINDS. HE DID NOT INDICATE THE MIXTURE SETTING USED DURING CRUISE. WHILE DESCENDING FOR LANDING THE ENGINE SPUTTERED, CAUGHT, & QUIT. A FORCED LANDING RESULTED IN A COLLISION WITH A FENCE. THERE WERE NO MECHANICAL MALFUNCTIONS REPORTED. ABOUT ONE GALLON OF FUEL WAS FOUND IN THE TANKS WHEN THE AIRPLANE WAS RECOVERED. LATER THE ENGINE WAS OPERATED. THE ONLY ANOMALY NOTED DURING THE ENGINE OPERATION WAS AN INDICATION OF A VERY RICH MIXTURE.
Probable cause
THE PILOT'S INACCURATE FUEL CONSUMPTION CALCULATIONS WHICH RESULTED IN FUEL EXHAUSTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90LA137
- Event ID
- 20001212X23330
- Case number
- ATL90LA137
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-06-24.
- API snapshot SHA-256: 1d683cb8e749340d05aa6d8b7336027ba5dcec4b47d9b9579fa49997bea195ac; retrieved 2026-09-23T05:48:40.415Z.