ERA24LA022 · Mooney M20E
Mooney M20E · Accident: fuel contamination during initial climb
From Dade Collier Training and Transition Airport (TNT) to North Perry Airport (HWO)
Event
- NTSB case
- ERA24LA022
- 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 M20E
- Aircraft type
- Mooney M20
- 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
- N1953Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dade Collier Training and Transition Airport (TNT), Miami, FLTo North Perry Airport (HWO), Hollywood, FL
- Aircraft age
- About 59 years (built 1964)
- 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
- Initial climb
- Defining eventThe 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
- Fuel contamination
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Before the flight, the pilot requested that 20 gallons of fuel be added to each wing. A total of 40 gallons of fuel was then added to the airplane. He conducted a preflight inspection and reported sumping “both main tanks after fueling” and, once inside the airplane, he “sumped both [fuel] lines from [the] interior valve.” When the pilot started the engine, he did so with the fuel selector on the right fuel tank. All indications were normal, and, after taxiing and completing his preflight checklist, he turned on his electric boost pump, took off, and flew to a different airport where he conducted a touch-and-go landing. After the touch-and-go, he then flew back to the departure airport. During the descent for landing, he configured the airplane for landing and made sure that the electric boost pump was on and that the fuel selector handle was set. The pilot then realized that he had been flying on the right fuel tank for about an hour and had not switched fuel tanks, so he switched to the left fuel tank to balance the fuel load, as he was close to the final approach for the runway. Upon touchdown, the pilot decided to perform a touch-and-go. When the airplane was about 150 feet above ground level, the propeller rpm started to slow drastically. The pilot then banked the airplane to the left to come back to the airport and the propeller stopped turning completely. He then declared an emergency, checked that the landing gear was still down and locked, and after seeing traffic on a nearby roadway, performed a forced landing to a grassy area next to a sidewalk that looked clear. The airplane struck a fence during the forced landing and the airplane’s fuselage and wings were substantially damaged. A witness who observed the pilot preparing his airplane at the departure airport for the flight reported that he did not witness the pilot sump either wing fuel tank for water despite the aircraft “being parked for at least a month or two.” Later, as the airplane was going into a nose-up attitude after the touch-and-go, he heard the engine back firing as it was making a shallow left turn. Postaccident examination of the wreckage revealed no evidence of any preimpact mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. However, water was found throughout the fuel system, including in the left and right fuel tanks, the fuel selector valve sump drain/strainer, the fuel distribution manifold, and the fuel servo. A sample of fuel from the fuel truck used to service the airplane before the accident flight showed no evidence of water or contamination. Since the airplane was serviced with 40 gallons of fuel before the flight, and the pilot reported that the airplane had 40 gallons of fuel on board at takeoff, it is likely that the airplane would have had little to no fuel in the tanks before being refueled. Accordingly, the water present was likely the result of condensation in the fuel tanks, which can happen inside a less-than-full fuel tank when a temperature difference occurs between the walls of the fuel tank and the air in the tank, causing water droplets to form on the inside of the tank. This accumulation of water within the fuel system was not detected by the pilot during his preflight inspection and likely resulted in the loss of engine power.
Probable cause
The pilot's inadequate preflight inspection, which resulted in a total loss of engine power due to fuel contamination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA022
- Event ID
- 20231026193311
- Case number
- ERA24LA022
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. 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: 9ae220b9d11836c3ce8b08615e92d6a9c40aaecb3d25a2d7d664faa739edd39e; retrieved 2026-09-16T18:15:18.535Z.