SEA07LA071 · Piper PA-28-140
Piper PA-28-140 · Accident: loss of engine power while maneuvering
From Eugene Airport (KEUG) to Eugene Airport (KEUG)
Event
- NTSB case
- SEA07LA071
- 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
- N5547F
- Operator
- Justin J. Hall · private individual
- Onboard fatalities
- Unknown
- Route
- From Eugene Airport (KEUG), Eugene, ORTo Eugene Airport (KEUG), Eugene, OR
- 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
- Maneuvering
- 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
- Loss of engine power
- 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
- 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
- Reason for occurrence undetermined
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, who was flying between 800 and 1,000 feet above the trees in mountainous/hilly terrain, decided to add power and start a climb up the valley he was in. Just as he added power, the aircraft's engine rpm dropped from about 2,300 to about 1,800 to 1,900 rpm. At that point, he applied full carburetor heat, moved the mixture to full rich, and checked to make sure the fuel selector was in the correct position. According to both the pilot and his passenger, these remedial actions did not help the situation, and the engine rpm stayed near 1,800 rpm. Because the terrain was rising and the aircraft could not maintain altitude, and because they were already very low, the pilot made the decision to attempt a forced landing in the densely forested snow-covered mountainous terrain. While attempting the landing, the aircraft struck a number of trees, and then impacted the snow-covered ground in an inverted position. A post-accident inspection of the airframe, systems, and engine did not reveal evidence of any pre-impact anomalies or malfunctions that would have precluded the engine from operating at full power.
Probable cause
The loss of a significant amount of engine power for undetermined reasons. Factors include no suitable place in which to make an emergency landing, and densely forested, mountainous/hilly terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07LA071
- Event ID
- 20070309X00267
- Case number
- SEA07LA071
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-03-06.
- API snapshot SHA-256: 6273b5127e76e7f4d70725a42f91cf526ef95ee02506d4f6dea3d2ec390f7f33; retrieved 2026-09-21T08:50:30.548Z.