Execstar Aviation Cessna 402B accident
Cessna 402B · Accident: total loss of engine power (non-mechanical) on approach
From Page Field (FMY) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- MIA99LA136
- 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
- N744MA
- Operator
- Execstar Aviation
- Onboard fatalities
- Unknown
- Route
- From Page Field (FMY), Fort Myers, FLTo Fort Lauderdale Executive Airport (FXE)
- 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
- Substantial
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on approach to land the left engine surged and lost power. The pilot switched the left engine fuel selector to another fuel tank and the engine restarted. A short time later the left engine surged and lost power again. The pilot switched the left engine fuel selector to the right main fuel tank and the engine again restarted. A short time later the left engine quit again and he shutdown the engine and feathered the propeller. A short time later the right engine surged and lost power. He shut down the right engine and feathered the propeller. He then made a forced landing in a field and during landing rollout the aircraft's left wing collided with a tree. A fire erupted in the left wing area. Post crash examination showed the right main fuel tank was empty. The right auxiliary fuel tank contained 2.5 gallons. The left main fuel tank contained one half gallon of fuel and the left auxiliary tank was ruptured. The pilot operating handbook stated that the main fuel tanks had one gallon unusable fuel and the auxiliary fuel tanks had one half gallon of unusable fuel.
Probable cause
A loss of engine power due to fuel exhaustion and the pilot in command's failure to ensure that the aircraft had adequate fuel to complete the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA136
- Event ID
- 20001205X00537
- Case number
- MIA99LA136
- 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: 8297cde04a89cdd96f2aef9831515b4009d87479db5157002a2d4feb6003d8ac; retrieved 2026-09-18T16:57:08.340Z.