ERA23FA087 · Mooney M20B
Rainwater Farms Mooney M20B · Accident: fuel starvation en route
From Perry Houston County Airport (PXE) to Bessemer Airport (EKY)
Event
- NTSB case
- ERA23FA087
- 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
- 1 · 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
Mooney M20B
- 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
- N74586
- Operator
- Rainwater Farms
- Onboard fatalities
- Unknown
- Route
- From Perry Houston County Airport (PXE), Perry, GATo Bessemer Airport (EKY), Bessemer, AL
- Aircraft age
- About 61 years (built 1961)
- 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 · cruise
- 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 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
- 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
The airplane was on an instrument flight rules flight and in cruise flight at 6,000 ft mean sea level (msl) when the pilot declared “mayday” and reported to air traffic control that the airplane’s engine was running rough. The controller subsequently provided a heading toward the closest airport about 11 nautical miles (nm) away, and upon turning left toward the airport, the pilot announced that the engine had regained power. The pilot elected to continue with the diversion and indicated that he was in instrument meteorological conditions (IMC). The controller continued to provide course guidance and advised the pilot of the weather conditions at the airport, which included an overcast ceiling at 800 ft above ground level. About four minutes after reporting that engine power had been restored, the pilot reported to the controller that he was, “engine out.” Radar contact was lost, and the airplane impacted trees and terrain about 5 nm from the diversion airport. Postaccident examination of the airframe and engine revealed no evidence of preimpact mechanical failures or malfunctions that would have precluded normal operation. The wing fuel tank bladders appeared intact. While there was evidence of fuel leakage from the left wing fuel vent, the right wing remained clean with no evidence of fuel leakage or fuel blighting in the area surrounding the wing. About 18 gallons of fuel was drained from the left fuel tank, while the right tank was found empty. No fuel was found in the fuel hoses and fuel system components. The fuel selector was found positioned to the right wing tank. The airplane was fueled with 22.2 gallons of fuel the day before the flight. The pilot’s phone contained a picture of a fuel receipt for about 38 gallons from the morning of the accident; however, the airplane registration number on this receipt did not match the accident airplane, and this purchase could not be definitively correlated to the accident airplane. Therefore, the total amount of fuel onboard the airplane at the time of departure on the accident flight could not be determined. Based on fuel consumption rates published in the pilot’s operating handbook, the airplane likely consumed about 10.15 gallons of fuel between engine start to the pilot’s first mayday call. If the airplane was fueled to capacity before takeoff, and the pilot had operated exclusively from the right fuel tank during the accident flight, about 17.25 gallons of fuel should have remained in the right tank at the time of the loss of engine power. That the right fuel tank was intact and empty at the accident site suggests the airplane was not fully fueled at the time of departure. A witness recalled the pilot stating before the accident flight that he hoped the airplane was already fueled so that he could get started on his pre-flight checks, indicating that he may have been in a rush to depart. The witness stated that the employee at the airport told him that the airplane was “fueled and ready.” The extent of the pilot’s preflight inspection could not be determined based on the available information. The pilot had flown the accident airplane make and model for the first time the day before the accident flight, for about one hour. The pilot had received about one hour of ground instruction from the owner before the flight, but did not receive any flight training in the accident airplane. Although the pilot’s logbook indicated that he had 18 total hours of experience in actual instrument meteorological conditions (IMC), the date of the last entry was 100 days before the accident flight, and the pilot’s instrument currency and proficiency could not be determined. The pilot sent a text message to a friend after the flight that occurred the day before the accident asking if he needed to switch fuel tanks during flight, indicating that the pilot lacked basic knowledge of the airplane’s fuel system. Additional text messages between the pilot and another friend indicated that the airplane’s autopilot was inoperative. Based on all available information, the circumstances of the accident are consistent with a total loss of engine power due to fuel starvation. Hand-flying the airplane without the aid of a functional autopilot in IMC would have significantly increased the pilot’s workload, particularly while troubleshooting a developing engine issue in an airplane in which he was unfamiliar. This task saturation may have resulted in the pilot forgetting to switch fuel tanks prior to and following the initial engine roughness. Additionally, the low cloud ceiling in the area of the accident site would have left the pilot with little time to locate a suitable landing area for a forced landing.
Probable cause
A total loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA087
- Event ID
- 20221213106451
- Case number
- ERA23FA087
- 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: d7eb1094e2b84837badb7908fdde200165549aa0ea117cdf72ccc75750720f49; retrieved 2026-09-15T07:55:14.008Z.