IAD02LA051 · Piper PA-28-151
Piper PA-28-151 · Accident: total loss of engine power (non-mechanical) en route
From UCA · Utica, NY to Rickenbacker International Airport (LCK)
Event
- NTSB case
- IAD02LA051
- 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-151
- 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
- N75303
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From UCA · Utica, NYTo Rickenbacker International Airport (LCK), Columbus, OH
- 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
- 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
- Fluid, fuel › Exhaustion
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
With a demonstrated fuel consumption rate of about 10 gallons per hour, the airplane departed on a return cross-country flight with a full 50-gallon fuel load, of which, 48 gallons was usable. The airplane encountered a headwind that averaged 36 knots, and the pilot changed altitude several times in search of more favorable wind. After 4.6 hours of flight, the engine stopped producing power. During the subsequent forced landing, the pilot declared to ATC that he had "run out of fuel." The airplane touched down on a highway where it nosed over. Examination of the airplane at the scene revealed no odor of fuel and no evidence of fuel spillage. The airplane was recovered, and a can of fuel was plumbed into the airplane's fuel system. The engine started immediately, and ran smoothly without interruption. The pilot did not update his weather briefing while the airplane was serviced, or at anytime during the return flight.
Probable cause
The pilot's exhaustion of his fuel supply. A factor in the accident was the pilot's inadequate preflight planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02LA051
- Event ID
- 20020530X00775
- Case number
- IAD02LA051
- 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: 85906f8b3e7bb08524e215d4ce7449738448a3762a743facdee236d384e20b80; retrieved 2026-09-22T10:56:04.664Z.