SEA03LA177 · Piper PA-28-180
Piper PA-28-180 · Accident: partial loss of engine power (non-mechanical) en route
From Skypark Airport (BTF) to S67 · Nampa, ID
Event
- NTSB case
- SEA03LA177
- 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-180
- 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
- N33170
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Skypark Airport (BTF), Bountiful, UTTo S67 · Nampa, ID
- 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
- Partial 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
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
As the airplane passed over the last airport on its route of flight where fuel was available, the pilot determined he was doing good on time and had plenty of fuel to reach his destination. On its final approach to the destination airport, and after having run out of fuel in one tank, the pilot switched over to the other tank. As the second tank's contents became exhausted, the pilot, in an attempt to keep the engine running, switched back and forth between tanks a couple of times; however, this proved unsuccessful and the aircraft's fuel supply was now entirely exhausted. Seeing that he would not make the runway, the pilot landed in a field just short of the runway. The lower right wing was substantially damaged as a result of an upward compression deformation of the wing structure.
Probable cause
The pilot's inadequate in-flight decision by failing to refuel while en route, resulting in fuel exhaustion and the loss of engine power. A factor was the unsuitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03LA177
- Event ID
- 20030922X01571
- Case number
- SEA03LA177
- 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: 653c1f4f78920ff510e8822b35537862dda211473a0e1a07ddf9c8aca1134c5f; retrieved 2026-09-22T08:40:02.905Z.