SEA92LA012 · Piper PA28-161
Alpine Aviation Piper PA28-161 · Accident: total loss of engine power (non-mechanical) on approach
From Bullfrog Basin Airport (U07) to Provo Municipal Airport (PVU)
Event
- NTSB case
- SEA92LA012
- 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
- Visual Meteorological Cond
Piper PA28-161
- Aircraft type
- Piper PA28
- 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
- N8379V
- Operator
- Alpine Aviation
- Onboard fatalities
- Unknown
- Route
- From Bullfrog Basin Airport (U07), BULLFROG BASIN, UTTo Provo Municipal Airport (PVU), Provo, UT
- 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
- Approach · VFR pattern final
- 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
- Pilot in command › Became lost/disoriented, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A NIGHT CROSS COUNTRY FLIGHT, THE PILOT WAS UNAWARE THAT THE AIRPLANE HAD DRIFTED OFF COURSE UNTIL THE ESTIMATED TIME OF ARRIVAL AND THE AIRPORT WAS NOT IN SIGHT. THE AIRPLANE WAS IN THE AIR AN EXTRA 45 MINUTES WHEN THE PILOT SPOTTED AN AIRPORT. REALIZING THE FUEL WAS LOW, THE PILOT TURNED TOWARD THE AIRPORT. ENROUTE, ONE FUEL TANK WAS EXHAUSTED OF FUEL. THE PILOT SWITCHED TO THE OTHER FUEL TANK AND WHILE ON FINAL APPROACH, THE REMAINING FUEL TANK WAS EXHAUSTED OF FUEL AND THE ENGINE LOST POWER. UNABLE TO REACH THE RUNWAY, THE AIRPLANE WAS LANDED SHORT AND COLLIDED WITH THE TERRAIN.
Probable cause
FUEL EXHAUSTION DUE TO THE PILOT'S INATTENTION AND BECOMING LOST. A FACTOR TO THE ACCIDENT WAS THE NIGHT CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA012
- Event ID
- 20001212X18397
- Case number
- SEA92LA012
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-10-14.
- API snapshot SHA-256: 33786c7be15e175dcc5c53a24abdcb6bcd5c80c6ac7400543561805b0308d0d4; retrieved 2026-09-21T23:24:39.971Z.