LAX04LA143 · Piper PA-28-180
Piper PA-28-180 · Accident: loss of engine power on approach
From Fullerton Municipal Airport (FUL) to O68 · Mariposa, CA
Event
- NTSB case
- LAX04LA143
- 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
- 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-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
- N5205L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fullerton Municipal Airport (FUL), Fullerton, CATo O68 · Mariposa, 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
- Approach
- 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
- Loss of engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
All engine power was lost during an approach for landing and the airplane collided with a berm during a forced landing on soft terrain. The pilot had departed for the planned 2.5-hour-long flight with partially full fuel tanks. No mechanical malfunctions were experienced during the climb or cruise portion of the flight. The engine did not sputter or backfire. Approaching the destination airport, the engine suddenly lost all power. The pilot repositioned the fuel selector to the opposite fuel tank, and engine power was restored. However, about 1 minute later all engine power was again lost, at which point the airplane was approximately 4 miles from the airport. The airplane was subsequently examined by a Federal Aviation Administration (FAA) inspector. He reported observing 4 and 8 gallons of fuel in the left and right wings' fuel tanks, respectively. The gascolator bowl was devoid of foreign material. The engine was test run and it operated normally. According to the FAA's type certificate data sheet, the airplane's unusable fuel was only 2.2 pounds (about 1/3-gallon). The cause of the engine power loss was not determined.
Probable cause
The total loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04LA143
- Event ID
- 20040304X00262
- Case number
- LAX04LA143
- 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, coordinates. 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: 985ae7d3a10c4d3a0d373dca01856eb262897fe2f60ae96552fc0b7cfe31a0ca; retrieved 2026-09-21T19:17:14.315Z.