CEN24LA370 · Piper PA-25-235
Piper PA-25-235 · Accident: fuel exhaustion en route
From Webber Falls, OK to Webber Falls, OK
Event
- NTSB case
- CEN24LA370
- 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
Piper PA-25-235
- Aircraft type
- Piper PA-25
- 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
- N6548Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Webber Falls, OKTo Webber Falls, OK
- Aircraft age
- About 62 years (built 1962)
- 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 137: Agricultural
- 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
- 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
- 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
- Tree(s)
- 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
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 was returning from his third aerial application flight of the day when the engine sputtered and lost all power. While attempting to land, the left wing collided with trees and the airplane cartwheeled. The wings and fuselage were substantially damaged. Postaccident examination of the airplane revealed that the fuel tank contained no fuel. The fuel system was intact, and no leaks were noted. The pilot reported there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. He reported that he reloaded chemicals and but forgot to refuel the airplane. He stated he spent about 10 minutes on the ground before the accident flight and that he could have slowed down and given more attention to refueling.
Probable cause
The pilot’s inattention to refueling during turn-around operations which resulted in a loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA370
- Event ID
- 20240927195215
- Case number
- CEN24LA370
- 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: 6dac0e8bb44d08cfa3bffbdbe33c9af01b77c463497ba01b6f6d62c731780fe7; retrieved 2026-09-16T19:19:32.382Z.