SEA06LA044 · Piper PA-28-181
Piper PA-28-181 · Accident: total loss of engine power (non-mechanical) en route
From King County International Airport - Boeing Field (BFI) to Redding Municipal Airport (RDD)
Event
- NTSB case
- SEA06LA044
- 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-181
- 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
- N35681
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo Redding Municipal Airport (RDD), Redding, CA
- 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
- 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
The pilot reported that he had obtained a weather briefing prior to departure and noted headwinds for the route of flight. The pilot calculated fuel endurance via the pilot operating handbook for cruise flight and utilizing a 65% power setting. The intended route of flight was estimated to take four hours and 30 minutes. The pilot reported that the manual indicated that for this power setting, the aircraft was capable of five hours and 15 minutes with a 45 minute reserve. While en route, the headwind was higher than the pilot expected. The pilot opted to divert to the southwest in an attempt to increase the airspeed. An altitude increase by several thousand feet was necessary for terrain clearance. The airspeed did not increase and the pilot opted to divert to another airport for landing as the flight now approached four hours with an estimated 45 minutes to an hour to go. While en route to the alternate airport, the engine rpm started to decrease at about four hours and 25 minutes into the flight. The pilot reported the emergency to air traffic control and set-up for an off-airport landing. When the pilot broke out of the cloud layer, he noted that he would not make the airport and performed a landing to a creek. During the descent, the aircraft collided with trees before coming to rest in the creek bed. During the wreckage recovery, the wing fuel tanks were intact. Approximately three gallons for fuel were drained from the fuel system. The engine was later prepared for an engine run. The engine was started and ran with no anomalies noted.
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. Trees and no suitable terrain for the landing were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06LA044
- Event ID
- 20060122X00113
- Case number
- SEA06LA044
- 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: aeeeea10c30624e1f2aeb1b5792e9daca6c4cc0a9c89ab681e1521b195dcd53e; retrieved 2026-09-22T05:09:43.425Z.