FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA245 · Piper PA-31-350

28 May 2013 · Page, AZ, United States

Piper PA-31-350 · Accident: fuel exhaustion en route

From Gainesville Municipal Airport (KGLE) to Page Municipal Airport (KPGA)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR13CA245
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-31-350

Aircraft type
Piper PA-31
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
N969BD
Onboard fatalities
Unknown
Route Narrative disagrees
From Gainesville Municipal Airport (KGLE), Gainsville, TXTo Page Municipal Airport (KPGA), Page, 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
En route · descent
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

  • Personnel issues › Psychological

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

NTSB narrative

The pilot stated that he and four passengers were about 4.5 hours into the flight and about 10 nm from their destination when the left low boost light illuminated. About 20 seconds later the left engine quit, and the pilot feathered the propeller. After about 1 minute the right low boost light illuminated, and 20 seconds later, the right engine quit. The pilot feathered the right propeller and proceeded to execute a forced landing in the desert 5 miles east of the intended destination. During the accident sequence the right engine separated from the airplane and the left wing buckled, resulting in substantial damage to the airplane. The pilot reported that the airplane had ran out of fuel, and that there were no preimpact mechanical failures or malfunctions that would have precluded normal operation.

Probable cause

A loss of engine power during cruise flight due to fuel exhaustion. Contributing to the accident was the pilot's improper fuel planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA245
Event ID
20130528X22514
Case number
WPR13CA245
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. 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: f155465598fe67b525b64456d7dbb3c70f379659ded3e5456f76cc8d9de096ad; retrieved 2026-09-15T21:40:25.823Z.