SEA91FA025 · Piper PA31
Piper PA31 · Accident: total loss of engine power (non-mechanical) en route
From Provo Municipal Airport (PVU) to Seattle Paine Field International Airport (PAE)
Event
- NTSB case
- SEA91FA025
- 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
- 0
- 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
- Instrument Meteorological Cond
Piper PA31
- Aircraft type
- Piper PA31
- 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
- N13UW
- Operator
- Bramwell, Steven T · private individual
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Seattle Paine Field International Airport (PAE), Everett, WA
- 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 · cruise
- 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; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, poor
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A CROSS COUNTRY FLIGHT, THE PILOT FAILED TO PLAN FOR THE EFFECTS OF KNOWN ADVERSE WEATHER, INCLUDING STRONG WINDS ALOFT AND MOUNTAIN WAVE ACTIVITY. THE PILOT OVERFLEW SEVERAL POSSIBLE FUEL STOPS, CONTINUING ON TOWARD THE DESTINATION UNTIL THE FUEL WAS EXHAUSTED. THE AIRPLANE COLLIDED WITH HEAVILY WOODED TERRAIN AFTER THE LOSS OF POWER TO BOTH ENGINES.
Probable cause
FUEL EXHAUSTION DUE TO INADEQUATE PREFLIGHT PLANNING AND PREPARATIONS, AND POOR INFLIGHT PLANNING AND DECISIONS. THE PILOT ELECTED TO FLY INTO KNOWN ADVERSE WEATHER CONDITIONS, AND DID NOT CALCULATE FUEL CONSUMPTION FOR THE PLANNED FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA91FA025
- Event ID
- 20001212X24696
- Case number
- SEA91FA025
- 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. 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: cb42eae4f2bbf973b07f67060d5d165c5d9a8efcd6b60c990768d6937aeccc80; retrieved 2026-09-21T15:33:00.904Z.