SEA06FA007 · Piper PA-28-140
Piper PA-28-140 · Accident: loss of control in flight during landing
From Seattle Paine Field International Airport (PAE) to King County International Airport - Boeing Field (BFI)
Event
- NTSB case
- SEA06FA007
- 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
- 3 · 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
- N5FN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Seattle Paine Field International Airport (PAE), Everett, WATo King County International Airport - Boeing Field (BFI), Seattle, 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
- Landing · flare/touchdown
- 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 control in flight
- 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
- Stall/mush; 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
- Pilot in command › Aborted landing, performed
- Pilot in command › Airspeed, inadequate
- Pilot in command › Airspeed, not maintained
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 had two Experimental Aircraft Association (EAA), Young Eagle participants on board. Event organizers said the airplane was scheduled to land at Paine Field to allow the two Young Eagle participants to exchange seats, and then return to Boeing Field. Video cameras, at Paine Field, show the airplane crossing the threshold of runway 16L, the right wing rising up, and the airplane touching down approximately 200 feet from the end of the runway. A black skid mark was found on the left side of the runway; another skid mark parallel to and 10 feet left of the first mark, started 20 feet later, in the grass. The two parallel marks veered left until both marks were in the grass. The marks in the grass then proceeded parallel to the runway, and a third skid mark was observed between the first two. On taxiway F-2 [which was perpendicular to runway 16L and the skid marks], a 36 inch long silver score mark was found, which was parallel to the three skid marks in the grass [wreckage examination found the airplane's tailskid assembly had been ground down]. Approximately 20 feet off the F-2 taxiway, an airport breakaway sign was broken from its mounts, and a black tire mark was found in the center of it. Next, the pilot transmitted to the ATC controller: "Paine Tower, Cherokee 5FN, something there happened, I don't know not sure what it doesn't feel right. Can you see my wheels?" Tower responded with: "Cherokee 5FN roger, we're looking, [your] wheels appear normal." The pilot said: "I'm at a steep angle at full power [and] hardly climbing." Tower asks: "Are your flaps up?" The pilot: "[The] flaps are up." Witnesses reported seeing the airplane depart on the runway heading, but at a very low altitude. One witness said that the airplane never got higher than 100 to 150 feet, and "he [the pilot] kept pulling the nose up at a very steep angle (about 45 degrees) and then push the nose down. I never saw him push the nose down enough to gain much air speed. I thought he was going to stall it at least once above the runway. I saw him go through this cycle 4 or 5 times before he went out of sight behind the hangar." Another witness said "he was not gaining altitude. The plane was pitching up and down. I watched it fly over some trees, then it started losing altitude and it disappeared behind the trees." Three witnesses working near the crash site reported hearing "a loud snap of breaking tree tops." One of these witnesses said he saw the airplane's right wing hit the trees, and the airplane spun right and went nose first to the ground. A postimpact fire ensued.
Probable cause
The pilot's inadequate airspeed during his aborted landing takeoff/climb which lead to a series of stall/mushes and subsequent impact with trees. Contributing factors were the pilot's loss of aircraft control during his initial landing approach and his immediate departure from the runway after touching down, his aborted landing attempt and subsequent impact with an airport sign, and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06FA007
- Event ID
- 20051026X01728
- Case number
- SEA06FA007
- 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: 3cfd63eb2b92cdfec509db02bdcbcafccbd22ef0d7000f0d0a2181499497b9ac; retrieved 2026-09-20T17:49:01.796Z.