NTSB CAROL · Event
Event SEA00LA041
Aircraft involved
Probable cause & findings
The pilot's improper decision to attempt a go-around, then attempt to stop on the wet grass. Factors include variable winds, the pilot's inadequate compensation for the winds conditions, his inadequate recovery from a bounced landing, wet grass along the side of the runway, and a residence near the edge of the runway surface.
Factual narrative
On January 31, 2000, approximately 1530 Pacific standard time, a Cessna 177, N3433T, collided with a personal residence during a balked landing at Harvey Airfield, Snohomish, Washington. The private pilot received serious injuries, his passenger received minor injuries, and the aircraft, which was owned by a friend of the pilot, was destroyed by a post-impact fire. The CFR Part 91 pleasure flight, which departed Skagit Regional Airport, Burlington, Washington, about 30 minutes prior to the accident, was operating in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to both the pilot and his pilot-rated passenger, while they were on final approach to runway 14, the wind seemed to shift about the time the aircraft crossed over the 22 foot-high wires just off the north end of the runway. As a result of the wind shift, the aircraft's rate of descent increased and the pilot added power. According to the pilot, there might have been a delay in engine response, but the passenger reported that the engine responded normally. According to the pilot, as the aircraft approached the runway surface, he began the landing flare, but not soon enough to properly arrest the rate of descent prior to contacting the runway surface. The aircraft then hit the runway hard, bounced back into the air, and began drifting to the left. According to the passenger, the pilot added partial power when the aircraft ballooned, but pulled the throttle to idle as the aircraft touched down on the grass along the northeast side of the runway. With about 1,500 feet of grass surface remaining on which to stop, the pilot put the flaps in the full-up position, turned off the carburetor heat, and added full power in an effort to abort the landing. Both the passenger and a number of other witnesses said that the pilot then pulled the nose of the aircraft up so high that the tiedown tang under the tail was digging into the dirt. Since the aircraft did not lift off as soon as the pilot thought it should, he told the passenger to "give me flaps," and the passenger moved the flaps to the 10 degree position. Soon thereafter, the pilot partially reduced power, moved the flaps back to the full-up position, and added full power again. Within a few seconds of adding power this second time, the pilot realized that the aircraft might not clear the fence at the southeast end of the airport property or the cars on the road just beyond the fence. He therefore brought the power to idle and tried to turn to the right away from the hangars that were under construction just off his left wing tip. This resulted in the aircraft heading toward the residence near the end of the runway. The pilot applied hard breaking, but due to the slippery wet grass he was unable to stop the aircraft prior to it contacting the house. After colliding with the house, the aircraft caught fire. Both the pilot and the passenger reported that the engine was running smooth with no evidence of coughing, backfiring, or missing. The FAA inspector who responded to the scene reported that he saw no evidence that would lead him to believe there had been an engine malfunction or flight control anomaly. While on short-final to a full-stop landing, the wind shifted and the aircraft's rate of descent increased. The pilot corrected with partial power, but did not initiate the landing flare soon enough to keep the aircraft from hitting the runway hard enough to bounce back into the air. After ballooning back into the air, the aircraft started drifting sideways and touched down in an open grassy area alongside the runway. Although the power was at idle at that point, and the pilot had ample room to bring the aircraft to a stop on the grass, he elected to abort the landing. After adding power and trying to get the aircraft to lift off using two different flap settings, the pilot elected to abort the go-around because he thought he might not clear obstacles ahead. During his attempt to stop the aircraft on the wet grass, it slid into a residence just off to the side of the southeast end of the runway. After impacting the house, both the residence and the aircraft caught on fire. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_SEA00LA041.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 ↗