LAX84LA016 · Piper PA-28-180
Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) on approach
From LHU · LAKE HAVASU CTY, AZ to Yuma, AZ
Event
- NTSB case
- LAX84LA016
- 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-28-180
- Aircraft type
- Piper PA-28
- 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
- N9560J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From LHU · LAKE HAVASU CTY, AZTo Yuma, AZ
- 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
- Approach · VFR pattern final
- 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 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
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT STATED THAT PRIOR TO DEPARTING LAKE HAVASU CITY HE VISUALLY INSPECTED THE FUEL TANKS & OBSERVED THAT BOTH TANKS WERE SLIGHTLY LESS THAN 1/2 FULL. BASED ON THIS OBSERVATION HE THOUGHT THE ACFT HAD 20-30 GALS OF FUEL WHICH WOULD BE SUFFICIENT FOR THE FLT. UPON REACHING BLYTHE, CA HE REALIZED HE WAS LOW ON FUEL BUT BELIEVED HE HAD SUFFICIENT FUEL TO REACH YUMA. THE ENG QUIT DUE TO FUEL EXHAUSTION 2 MI FROM DESTINATION. THE PLT ATTEMPTED TO LAND ON AN INTERSTATE HWY. INITIAL TOUCHDOWN WAS MADE IN A STEEP LEFT BANK BECAUSE OF TRAFFIC & THE PRESENCE OF A BRIDGE OVER-CROSSING. THE ACFT COLLIDED WITH A SMALL RELECTOR POLE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84LA016
- Event ID
- 20001214X44883
- Case number
- LAX84LA016
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 58b7e2ea72bc3a926682e45534d1ec83c280611cc460bbd206b71c9cc242b054; retrieved 2026-09-23T21:12:32.307Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. The narrative states the pilot "BELIEVED HE HAD SUFFICIENT FUEL TO REACH YUMA" and "THE ENG QUIT DUE TO FUEL EXHAUSTION 2 MI FROM DESTINATION" near Yuma, AZ; the destination was not recorded.