NTSB CAROL · Event
Event SEA01LA088
Aircraft involved
Probable cause & findings
A system failure for undetermined reasons while on final approach. The pilot's failure to maintain control of the aircraft was a factor.
Factual narrative
On May 10, 2001, at 1952 Pacific daylight time, a Maule M-7-235, N5669S, registered to and operated by the private pilot as a 14 CFR Part 91 personal flight, collided with the terrain short of runway 34 at Snohomish County (Paine Field), Everett, Washington. Visual meteorological conditions prevailed at the time and no flight plan was filed. The aircraft was substantially damaged and the private pilot was not injured. The flight originated from Lopez Island, Washington, about 20 minutes prior to the accident. During a telephone interview and subsequent written statement, the pilot reported that prior to contact with the tower, he checked the winds via ATIS. ATIS reported the wind from 34 degrees at six knots. The pilot then contacted the tower and was given clearance for left traffic to land on runway 34 left. The pilot reported that he performed the pre-landing checklist and set speed and flaps for landing. The pilot reported that while on final approach to runway 34, the aircraft began to drift to the left and he applied right rudder control, however the aircraft continued to drift. The pilot then applied aileron control, which also had no effect. The pilot reported that he eventually applied full right rudder and aileron control as the aircraft made a left circular turn. The pilot stated that he elected to go-around to try and remedy the problem. Power was added which resulted in the aircraft yawing to the left even with full right rudder and aileron control inputs. The aircraft was now in a steady 15 to 20 degree left turn. The pilot stated that he had no directional control and opted to land the aircraft off airport. During this turn, the left wing continued to drop and the aircraft lost altitude. The pilot located an open field and landed the aircraft left wing low and nose down. A Federal Aviation Administration Inspector from the Seattle, Washington, Flight Standards District Office responded to the accident site and later followed up when the aircraft was recovered from the accident site. The inspector reported that he inspected the flight control system, but did not find evidence of a mechanical failure or malfunction. The pilot reported that while on final approach for landing, the aircraft began to drift to the left. The pilot corrected with rudder control, however, the aircraft continued to drift. The pilot also applied aileron input, however, the aircraft continued to drift to the left and begin a left circular turn. The pilot elected to go-around to try and remedy the problem. Power was added which resulted in the aircraft yawing to the left even with full right rudder and aileron control inputs. The pilot reported that he had no directional control and opted to land the aircraft off airport. During this turn, the left wing continued to drop and the aircraft lost altitude. The pilot located an open field and landed the aircraft left wing low and nose down. A Federal Aviation Administration Inspector responded to the accident site and later followed up when the aircraft was recovered from the accident site. The inspector reported that he inspected the flight control system, but did not find evidence of a mechanical failure or malfunction. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_SEA01LA088.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗