FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA164 · Piper PA-28-181

23 Mar 2009 · Firebaugh, CA, United States

Piper PA-28-181 · Accident: fuel exhaustion en route

From Palm Springs International Airport (PSP) to Reid-Hillview Airport of Santa Clara County (RHV)

Report a problem

Event

NTSB case
WPR09LA164
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-181

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
N1857H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Springs International Airport (PSP), Palm Springs, CATo Reid-Hillview Airport of Santa Clara County (RHV), San Jose, 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
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 › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported departing with about 45 gallons of fuel onboard. She initiated a climb to 10,500 feet, and turned on course direct to the destination airport. About 3 1/2 hours into the flight, she checked the fuel gauges, and estimated that there was enough fuel remaining for about 1 hour 10 minutes of flight. About 15 minutes later the engine stopped producing power. The pilot observed one of the gauges was now reading empty, so she switched to the other tank; the engine then regained power, and she diverted to an alternate airport. During the landing approach, the engine then lost power again, and the pilot performed a forced landing in a plowed field. The airplane sustained substantial damage to the right wing during the accident sequence. Post accident inspection revealed that both tanks were intact and absent of fuel. No obvious sources of a fuel leak were noted. The pilot reported encountering strong headwinds during the flight, and further stated that she was not comfortable with the leaning procedure for the airplane type.

Probable cause

A total loss of engine power due to fuel exhaustion as a result of the pilot's inadequate fuel planning and monitoring.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA164
Event ID
20090324X62944
Case number
WPR09LA164
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2009-03-24.
  • API snapshot SHA-256: 912d7c82df5d05799be54302610aa9fce04c524fd800e2490f283c029e8bc311; retrieved 2026-09-15T10:52:18.155Z.