ATL87FA017 · Cessna 210L
Cessna 210L · Accident: loss of engine power on approach
From 2A3 · Bessemer, AL to Montgomery Regional (Dannelly Field) Airport (MGM)
Event
- NTSB case
- ATL87FA017
- 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
- 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 210L
- Aircraft type
- Cessna 210
- 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
- N59034
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2A3 · Bessemer, ALTo Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, AL
- 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 · IFR final 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
- Loss of engine power
- 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
- Wire, static
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Estimated position: the centre of Montgomery, AL, the place the record names. Not the accident site.
NTSB narrative
THE ACFT WAS FLOWN FOR SLIGHTLY LESS THAN 3 HRS ON AN INSTRUCTIONAL FLT. THE ACFT WAS REPORTEDLY NEARLY FULL OF FUEL BEFORE TAKEOFF. CAPACITY IS 89 GALS. AT MAX CONSUMPTION OF 22 GPH THE ACFT SHOULD HAVE STILL HAD FUEL AVAILABLE WHEN THE ENG QUIT. DURING THE FORCED LNDG THE ACFT COLLIDED WITH POWER LINES AND THE GROUND ABOUT 1 MILE FORM THE RWY. THE ENG WAS TEST RUN SATISFACTORILY AFTER THE ACC. THE ACFT HAD LAIN IN AN INVERTED POSITION OVERNITE BEFORE THE INSPECTION WHICH SHOWED ONLY A FEW OUNCES OF FUEL IN THE ACFT. THE CFI STATED THAT THE FULLEST TANK WAS SELECTED PRIOR TO THE LAST TAKEOFF.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL87FA017
- Event ID
- 20001213X35087
- Case number
- ATL87FA017
- 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: d6774a04d9f1ae32a08c4acdcf60a9b256a4932d28440cdd0150f569a183f5d5; retrieved 2026-09-21T04:20:21.870Z.