ERA25LA006 · Piper PA24 250
Piper PA24 250 · Accident: fuel exhaustion en route
From George T Lewis Airport (CDK) to Fort Lauderdale Executive Airport (FXE)
Event
- NTSB case
- ERA25LA006
- 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
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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
Piper PA24 250
- Aircraft type
- Piper PA24
- 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
- N12RD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From George T Lewis Airport (CDK), Cedar Key, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FL
- Aircraft age
- About 66 years (built 1958)
- 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 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
- 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 pilot reported that he departed on the first of two legs of a cross-country flight with full main fuel tanks (30 gallons each, 28 gallons useable). The first leg of the 1 hour and 45-minute flight was uneventful, and the engine performed normally during the flight. The airplane was not refueled after the completion of the first leg, so he checked his fuel both visually and with the fuel gauges. During the cruise portion of the return flight, he noted a partial loss of engine power, with rpm dropping to between 1,000 and 1,200. He initiated the checklist procedures for a partial power loss, declared an emergency with air traffic control, and power was briefly restored. The engine rpm again dropped, and since the closest airport was too far away, he executed a forced landing to a sugar cane field about 1 hour and 18 minutes into the return flight. The pilot stated that the airplane should have had about 2 hours of fuel remaining when the engine lost power. Federal Aviation Administration inspectors responded to the accident site and examined the wreckage; they confirmed substantial damage to the airframe. The fuel system was examined at the scene. The auxiliary wingtip fuel tanks and main fuel tanks contained no quantifiable fuel. The main fuel tanks were not ruptured, and there was no evidence of fuel leakage outside the airplane. The fuel strainer was undamaged and was empty of fuel. After recovery of the wreckage, the engine was prepared for a test run. The engine started on the first attempt and was eventually run up to 2,000 rpm before the run was concluded. Impact damage to the propeller prevented a run at a higher rpm. Also, the fuel tanks were filled with water to check for leaks; no leaks were noted. The pilot reported that the main tanks were “topped” with 8.7 gallons of fuel prior to the first leg of the trip. Prior to this servicing, the tanks were reportedly filled 26 days before the accident, and the pilot stated that his son flew the airplane for three touch-and-go landings after this refueling. Automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane was airborne for 1 hour and 2 minutes and taxied a total of 18 minutes on this flight. Estimated fuel burn for a flight of this duration was about 15 gallons. Therefore, it is unlikely that the pilot initiated the cross-country trip with a full fuel load, and it is possible that he perceived his main fuel tanks to be completely full before beginning the first leg when they were not. The pilot’s operating handbook for the airplane stated that, due to several factors, many fuel cells do not hold their full rated capacity.
Probable cause
The pilot’s failure to initiate the cross country flight with an adequate fuel supply, resulting in a loss of engine power and forced landing due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA006
- Event ID
- 20241013195302
- Case number
- ERA25LA006
- 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: b094f4d3dee625796f605f6a1ce6365cae23bf92574472b5561904bb4bc00a40; retrieved 2026-09-16T19:22:24.377Z.