FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL89LA039 · Cessna 172

17 Nov 1988 · Pikeville, KY, United States

Cessna 172 · Accident: total loss of engine power (non-mechanical) on approach

From Hagerstown Regional Richard A Henson Field (HGR) to Pikeville, KY

Report a problem

Event

NTSB case
ATL89LA039
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 172

Aircraft type
Cessna 172
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
N2840Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hagerstown Regional Richard A Henson Field (HGR), Hagerstown, MDTo Pikeville, KY
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
Approach
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 › In-flight planning/decision, improper
  • Pilot in command › Refueling, not obtained

Approximate · Estimated position: the centre of Pikeville, KY, the place the record names. Not the accident site.

NTSB narrative

THE PILOT HAD FLOWN ABOUT 3.7 HOURS AND WAS ABOUT 2 MILES FROM HIS DESTINATION AIRPORT WHEN THE ENGINE STOPPED AND HE WAS FORCED TO LAND IN A SWAMP. THE PILOT HAD TOPPED OFF THE ACFT SO THAT IT CONTAINED 42 GALLONS OF FUEL (38 GALLONS OF USABLE FUEL). THE WRECKAGE EXAMINATION INDICATED THAT THE FUEL SYSTEM WAS TOTALLY VOID OF FUEL. THE PILOT DID NOT ATTEMPT TO LAND AT ANOTHER AIRPORT TO REFUEL EVEN THOUGH THE FLIGHT CAME WITHIN 5 MILES OF AN AIRPORT WHERE THERE WAS FUEL AVAILABLE. THE PILOT FAILED TO PROPERLY COMPUTE HIS FUEL CONSUMPTION FOR THE EXISTING HEADWIND CONDITIONS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL89LA039
Event ID
20001213X27201
Case number
ATL89LA039
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 1988-11-18.
  • API snapshot SHA-256: c742499416384481730132e0a99c4af377361f59837ed08575c3593671231371; retrieved 2026-09-23T08:20:40.840Z.