ATL83LA287 · Cessna 150
Cessna 150 · Accident: total loss of engine power (non-mechanical) en route
From Batesburg, SC to TRENTON, SC
Event
- NTSB case
- ATL83LA287
- 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 150
- 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
- N18188
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Batesburg, SCTo TRENTON, SC
- 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 · cruise
- 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 supply, inadequate
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT BEFORE TAKING OFF, HE PREFLIGHTED THE ACFT & ESTIMATED THAT 6 GAL OF FUEL WAS ON BOARD. ACCORDING TO HIM, THE ENGINE LOST POWER APRX 30 MIN AFTER TAKEOFF & HE WAS UNABLE TO RESTART IT. DURING A FORCED LANDING, HE INTENTIONALLY GROUND LOOPED THE ACFT TO AVOID COLLIDING WITH A FENCE. DURING THE GROUND LOOP, THE NOSE GEAR FAILED. THE ACFT WAS EQUIPPED WITH A 26 GAL FUEL SYS OF WHICH 3.5 GAL WAS UNUSABLE. NORMAL FUEL CONSUMPTION WAS BETWEEN 7.0 & 3.2 GAL/HR. THE PLT REPORTED PROBABLE MISCALCULATION OF FUEL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LA287
- Event ID
- 20001214X43626
- Case number
- ATL83LA287
- 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: 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: cf71d2172f58f0161c8374521c4a38dfa42238a4fdee5fa8d7372ac28df71a3f; retrieved 2026-09-23T21:43:44.612Z.