WPR19LA063 · Piper PA22 160
Piper PA22 160 · Accident: fuel exhaustion en route
From Kingman Airport (IGM) to Glendale Municipal Airport (GEU)
Event
- NTSB case
- WPR19LA063
- 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
- 1 · 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
- Unknown
Piper PA22 160
- Aircraft type
- Piper PA22
- 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
- N9227D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kingman Airport (IGM), Kingman, AZTo Glendale Municipal Airport (GEU), Glendale, AZ
- Aircraft age
- About 61 years (built 1958)
- 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
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was conducting a cross-country flight with one passenger onboard. According to the passenger’s sister, at 1001, her sister sent her a text, which stated that she and the pilot had taken off and were heading to an airport about 50 miles to the south to obtain fuel. The investigation was unable to determine whether the pilot obtained fuel at this airport. At 1038, while at the second airport, the passenger telephoned a relative and stated that they would take off shortly for the destination airport. Although the actual departure time from the second airport could not be determined, the sister stated that she expected the airplane to arrive at the destination airport about 1130. By 1215, the sister called the local Sheriff’s Office and search and rescue to locate the airplane because it was overdue. First responders found the airplane, which had impacted trees and came to rest inverted in a ravine in a park about 10 miles south of the second airport. The pilot was seriously injured, and the passenger was fatally injured. The pilot reported to the first responders that the airplane experienced an electrical failure and he tried to turn around, however the engine lost power. Almost all the airplane components remained attached to the wreckage. The propeller damage signatures were consistent with a complete lack of engine power at impact. Examination of the airframe, engine, and propeller revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.
First responders did not note the presence of any fuel on scene. The airplane was equipped with two separate fuel tanks, one in each wing. Each tank had a dedicated filler neck with a removable cap. Neither fuel cap was found at the accident site or in the recovered wreckage. There was no evidence of the caps being installed at impact. The wreckage evidence was consistent with a loss of engine power due to fuel exhaustion. The absence of the fuel caps likely resulted in the fuel being siphoned overboard during flight. Aside from the absence of fuel caps and fuel, no evidence was found of any other preimpact mechanical malfunctions or failures that would have precluded normal operation. It is likely that, when the pilot stopped at the second airport to obtain fuel, he did not put the fuel caps back on the airplane; whether he actually obtained fuel or not could not be determined because it was likely all siphoned out during the flight.
The pilot was hospitalized for several days, and a review the pilot’s postaccident hospital records revealed that he had diabetes and used an insulin pump, which was corroborated by a review of his previous medical records. However, insufficient evidence was found to determine whether the pilot was impaired due to diabetic complications at the time of the accident. Thus, whether the pilot's diabetes or some other medical factor contributed to the accident could not be determined. Several attempts were made to obtain a statement from the pilot however he refused to provide any information to the investigation.
Probable cause
The student pilot's failure to secure the fuel caps, which led to the fuel being siphoned overboard, fuel exhaustion, and the total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19LA063
- Event ID
- 20190113X75353
- Case number
- WPR19LA063
- 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, cause areas. 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: 24790b54818a6c5b88c2cc183ad72a53eb3a87a84e627c7df493fc62df26706e; retrieved 2026-09-15T06:52:58.350Z.