MIA99LA100 · Mooney 20G
Gulf Coast Airways Mooney 20G · Accident: total loss of engine power (non-mechanical) en route
From Naples Municipal Airport (APF) to an unrecorded destination
Event
- NTSB case
- MIA99LA100
- 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
Mooney 20G
- Aircraft type
- Mooney 20
- 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
- N3588X
- Operator
- Gulf Coast Airways
- Onboard fatalities
- Unknown
- Route
- From Naples Municipal Airport (APF)To not recorded
- 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
- En route · climb to cruise
- 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 starvation
- 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 › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was in the traffic pattern and the pilot was practicing touch-and-go landings and takeoffs. The pilot reported that he had completed a touch-and-go on runway 14, and on climb out was assigned a right hand traffic pattern. On crosswind the airplane's engine lost complete power. The pilot said, '...I pitched down and tried to restart the engine, on either tank using both the starter and windmilling.' He attempted to make a forced landing to a golf course, but decided on a road, because there were people on the golf course. The airplane landed on the road gear up, heading southbound, skidded forward, and the right wing struck two mailboxes. The airplane continued forward striking a tree, and separating a portion of the right wing. Examination of the wreckage revealed that there was no fuel in the right main tank. No fuel was found in the carburetor, and the fuel selector was found in the 'OFF' position. About 10 gallons of fuel were found in the left tank. The left fuel system operated without discrepancies, and fuel flowed from the tank. No broken fuel lines were found, and the engine displayed no discrepancies. The airplane flew 1.7 hours before the flight on March 6, 1999. The airplane was last refueled on February 11, 1999. The FAA inspector wrote in his report, '...subsequent fuel calculations revealed that at the time of the accident, the right fuel tank would have been empty of usable fuel.' In addition the pilot said, '...that when the engine failed...that he had been flying on the right tank for approximately 45 minutes prior to the accident. He also stated that he tried to select the left fuel tank but it is possible that he may have selected the 'Off' position inadvertently.'
Probable cause
the pilot's improper procedure by not placing the fuel selector on the tank with the most fuel, which resulted in fuel starvation and a off airport forced landing. Contributing factors in this accident were the pilot's inadequate pre-flight and in-flight planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA100
- Event ID
- 20001205X00362
- Case number
- MIA99LA100
- 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: de5993d9d9f22a0d8756b350b6d71a07cd4e72a48f7a65e870aa3ffc08b3acf7; retrieved 2026-09-22T15:45:16.765Z.