FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA05LA048 · Piper PA-28-140

9 Feb 2005 · Superior, MT, United States

Piper PA-28-140 · Accident: total loss of engine power (non-mechanical) en route

From Three Rivers, MT to Mineral County Airport (9S4)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
SEA05LA048
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-140

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
N6399W
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Three Rivers, MTTo Mineral County Airport (9S4), Superior, MT
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 starvation
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

  • Pilot in command › Fuel management, improper
  • Pilot in command › Planning/decision, inadequate

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 elected to make an unscheduled landing due to what he perceived as a low fuel state, as both fuel gages were indicating less than one-quarter full. While maneuvering in the traffic pattern to afford another airplane on the runway adequate time to depart, the airplane's engine began to run rough, then lost power completely. The pilot went through the checklist to restart the airplane, and nearing the end of the runway power was restored, but only briefly; the engine failed a second time and there was no attempt to restart it. A clearing was located in which to land and after touching down and rolling out, the nose gear impacted a berm, which resulted in the nose gear failing aft causing substantial damage to the firewall. During the recovery process approximately one quart of fuel was observed in the right tank and 5.5 gallons in the left tank; the fuel selector was positioned in the LEFT TANK position. The pilot said he thought the fuel selector was in the Right Tank position prior to the engine quitting, however, couldn't say for sure if he moved it to the LEFT TANK position when the engine quit. A post accident examination revealed no preimpact failures or malfunctions which would have precluded normal operation.

Probable cause

A loss of engine power due to the pilot's inadequate planning/decision and improper fuel management, which resulted in fuel starvation. A contributing factor was the berm.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA05LA048
Event ID
20050216X00202
Case number
SEA05LA048
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: 36acf427ec198a063decfe65a3961f47fc586a45e968fe7a4c1623c6c632a0ed; retrieved 2026-09-22T06:17:12.023Z.