WPR24LA012 · Piper PA-46-310P
Livengood Leasing Piper PA-46-310P · Accident: fuel exhaustion during initial climb
From Chandler Municipal Airport (CHD) to Ak-Chin Regional Airport (A39)
Event
- NTSB case
- WPR24LA012
- 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 PA-46-310P
- Aircraft type
- Piper PA-46
- 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
- N4380D
- Operator
- Livengood Leasing
- Onboard fatalities
- Unknown
- Route
- From Chandler Municipal Airport (CHD), Chandler, AZTo Ak-Chin Regional Airport (A39), Maricopa, AZ
- Aircraft age
- About 38 years (built 1985)
- 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 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that the purpose of the flight was for the accident airplane to be photographed by another pilot from a different airplane. The pilot stated that he believed there were 35 gallons of fuel onboard the airplane based on the airplane’s flight logs. He was unable to visually verify the actual fluid quantity in the tanks during the preflight inspection because of the design of the tanks and the lower quantity of fuel (below the fuel filler). During the initial climb, at an altitude of about 1,500 ft above ground level (agl), the engine exhibited a partial loss of power. The pilot performed a 180° turn in an attempt to return to the airport. The airplane was unable to maintain sufficient altitude and touched down in a dirt area about 500 ft short of the runway.
Shortly after the accident, about 0.5 gallon of fuel was drained from each wing tank. The airplane’s fuel gauges indicated that the fuel tanks were empty and the engine monitor indicated that 32 gallons remained. Both wings and their respective fuel tanks were not breached; there was no evidence of a fuel leak or blue staining on the airframe.
A post-accident examination revealed only trace amounts of fuel throughout the system and the boost pumps sounded to be operating normally.
The engine monitoring system requires manual input by the pilot for the “Fuel Remaining.” The displayed indication of 32 gallons remaining was based on pilot-entered values and was not consistent with the airplane’s fuel quantity gauges, which indicated that no fuel was onboard.
A review of the data from the engine monitoring system revealed that following takeoff, the engine was operating normally for about two minutes. Thereafter, engine power decreased and was not restored. Fuel flow data from the transducer indicated residual flow around 2 to 3 gallons per hour, consistent with air and fuel droplets moving through the engine-driven and electric boost pumps, which is indicative of fuel starvation or exhaustion.
The last occasion the fuel tanks were topped off to full was 7-8 months before the accident and the fuel quantities thereafter could not be definitively determined, nor could the fuel loss from evaporation be quantified. Because the fuel system did not appear to be breached and only trace amounts of fuel were found in both independent fuel tanks, it is likely the fuel quantity was inadequate, resulting in air entering in the system, leading to a partial loss of power. The pilot believed the likely erroneous fuel-remaining calculations from the pilot-entered fuel quantities rather than visually confirming the quantity or verifying with the airplane’s fuel gauges.
Probable cause
The pilot’s failure to adequately confirm the fuel quantity before departure, resulting in fuel exhaustion and a partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA012
- Event ID
- 20231011193233
- Case number
- WPR24LA012
- 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, 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: 988a76a9b638098c134e5defbdffc61b869050195f05d3321e7e0e562220fa0f; retrieved 2026-09-16T18:12:55.082Z.