LAX94LA164 · Piper PA-24-250
Piper PA-24-250 · Accident: total loss of engine power (non-mechanical) en route
From Yuma International Airport / Marine Corps Air Station Yuma (YUM) to Fresno Yosemite International Airport (FAT)
Event
- NTSB case
- LAX94LA164
- 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N7541P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yuma International Airport / Marine Corps Air Station Yuma (YUM), Yuma, AZTo Fresno Yosemite International Airport (FAT), Fresno, CA
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel starvation; 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
- Pilot in command › Emergency procedure, not followed
- Pilot in command › Fuel boost pump selector position, not used
- Pilot in command › Fuel supply, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OCCUPYING THE RIGHT FRONT SEAT ALLOWED THE ENGINE TO SUSTAIN A TOTAL LOSS OF POWER DUE TO FUEL STARVATION. WHILE EXECUTING THE EMERGENCY CHECK LIST, THE PILOT DID NOT TURN ON THE ELECTRICAL FUEL PUMP AS REQUIRED. THE ENGINE OPERATED NORMALLY DURING THE POSTACCIDENT RUN-UP.
Probable cause
THE PILOT'S IMPROPER USE OF THE FUEL SUPPLY WHICH ALLOWED THE ENGINE TO SUSTAIN FUEL STARVATION, AND HIS FAILURE TO FOLLOW THE EMERGENCY CHECKLIST BY NOT USING THE ELECTRICAL FUEL BOOST PUMP. THE ENGINE FUEL STARVATION WAS A FACTOR IN THIS ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA164
- Event ID
- 20001206X00935
- Case number
- LAX94LA164
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 7eff86cbdf2ca096679664c593f8078dbbf4b45fffe22a6eaff0d70f0d3ab5db; retrieved 2026-09-21T22:41:21.156Z.