Air Flight Cessna 402B accident
Cessna 402B · Accident: total loss of engine power (non-mechanical) on approach
From Andros Town Airport (MYAF) to Fort Lauderdale Hollywood International Airport (FLL)
Event
- NTSB case
- MIA98LA019
- 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
- Charter & commuter
- 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 402B
- Aircraft type
- Cessna 402
- 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
- N69312
- Operator
- Air Flight
- Onboard fatalities
- Unknown
- Route
- From Andros Town Airport (MYAF), Andros TownTo Fort Lauderdale Hollywood International Airport (FLL), FL
- 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 135: Air Taxi & Commuter
- 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
- Destroyed
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 pilot was on approach for landing when the right main landing gear did not indicate that it was down. The pilot made a go-around and remained in left closed traffic performing emergency gear extension procedures with negative results. The pilot departed closed traffic and proceeded off shore to burn off fuel before attempting an emergency landing. A company airplane was dispatched to verify the landing gear position. The pilot started a straight in approach for landing five miles from the airport. The right engine started surging and quit. The left engine started surging one mile from the runway. He switched fuel tanks. The engine started and quit. He made a forced landing straight ahead and collided with runway approach lights about 1/4 mile from the end of the runway. The pilot stated he ran out of fuel.
Probable cause
The pilot's improper management of fuel resulting in a total loss of engine power on both engines due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA019
- Event ID
- 20001208X09218
- Case number
- MIA98LA019
- 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: 21b4d36c2b3ffda4c21502764cc15403a6d7a5df860f14b081b43e7fc05534d2; retrieved 2026-09-18T17:18:58.163Z.