GAA15CA137 · Piper PA 24
Celebrations Aviation Piper PA 24 · Accident: fuel exhaustion en route
From Battle Lake Municipal Airport (00MN) to Oelwein Municipal Airport (OLZ)
Event
- NTSB case
- GAA15CA137
- 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 24
- Aircraft type
- Piper PA-24
- 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
- N5152P
- Operator
- Celebrations Aviation
- Onboard fatalities
- Unknown
- Route
- From Battle Lake Municipal Airport (00MN), Battle Lake, MNTo Oelwein Municipal Airport (OLZ), Oelwein, IA
- Aircraft age
- About 57 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 · 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during a cross-country flight, "the airplane had a complete loss of engine power", and that he made several attempts to restart the engine that were unsuccessful. The pilot made a forced landing in a field where the airplane came to rest after impacting terrain. A post-accident inspection by Federal Aviation Administration Aviation Safety Inspectors revealed that the airplane did not have any usable fuel remaining in its tanks at the time of impact, and that the fuel tanks were undamaged. The airplane sustained substantial damage to the wings, and fuselage.
The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's inadequate pre-flight fuel planning resulting in fuel exhaustion and a collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA137
- Event ID
- 20150625X72945
- Case number
- GAA15CA137
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-06-25.
- API snapshot SHA-256: 1307eb9a428d03ffd6d34c0d6f7f6fca474685806d385b2be4fd892dc90ee9d9; retrieved 2026-09-16T02:27:37.180Z.