MIA98LA024 · Douglas DC-3C
Douglas DC-3C · Accident: total loss of engine power (non-mechanical) on approach
From Gulfport Biloxi International Airport (GPT) to West Memphis Municipal Airport (AWM)
Event
- NTSB case
- MIA98LA024
- 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
- Instrument Meteorological Cond
Douglas DC-3C
- Aircraft type
- Douglas DC-3
- 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
- N59316
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Gulfport Biloxi International Airport (GPT), Gulfport, MSTo West Memphis Municipal Airport (AWM), West Memphis, AR
- 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 › Fuel management, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The PIC stated he was established on an instrument approach when the left engine fuel pressure dropped to zero and the engine quit. He moved the fuel selector to the right rear fuel tank and the engine started. He continued the approach for about 2 miles when the right engine quit followed by the left engine. He made a forced landing to a sand bar. Examination of the airplane revealed the fuel tanks were not ruptured and the fuel tanks were empty.
Probable cause
The pilot-in-command's improper management of fuel resulting in a total loss of engine power on both engines during an instrument approach due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA024
- Event ID
- 20001208X09221
- Case number
- MIA98LA024
- 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 1997-11-07.
- API snapshot SHA-256: 9fd60df92f6110ddeb4f23499ada82d05b6a73188f7341afa5ad6935180a0da3; retrieved 2026-09-22T18:12:51.784Z.