NTSB CAROL · Event
Event SEA04LA096
Aircraft involved
Probable cause & findings
The instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway.
Factual narrative
On May 29, 2004, at 1005 Pacific daylight time, a Cessna 172M, N5440H, impacted a fence post after departing the end of a turf/grass runway during a simulated forced landing at Vernonia Municipal Airport, Vernonia, Oregon. The certified flight instructor and his student were not injured, but the aircraft, which is owned and operated by Twin Oaks Airpark, sustained substantial damage. The 14 CFR Part 91 instructional flight, which departed Starks Twin Oaks Airpark one hour earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation. According to the instructor pilot, who failed to submit a NTSB Form 6120.1/2, he was performing a simulated engine out forced landing as a demonstration for his student. As he neared the approach end of the 2,940 foot grass strip, the aircraft's airspeed was faster than he desired, and during the flare, it began to float further down the runway than where he had planned to touch down. He said that because of the excess airspeed, he was unable to get the aircraft to touch down until approximately 1,000 feet down the runway. After touchdown, he attempted to stop the aircraft before it reached the end of the runway, but since he had landed on the wet grass, he was unable to get it stopped before the aircraft went off the far end. After departing the runway, the aircraft collided with a nearby fence post. The instructor pilot, who was performing a simulated engine out forced landing as a demonstration for his student, allowed the aircraft's airspeed to remain too fast while on final approach to the 2,940 foot grass strip. Because the airspeed was faster than he desired, during the flare, the aircraft began to float further down the runway than where he had planned to touch down. The instructor pilot was unable to get the aircraft to touch down until approximately 1,000 feet down the runway. After touchdown on the wet grass, he attempted to stop the aircraft before it reached the end of the runway, but he was unable to do so before the aircraft went off the far end. After departing the runway, the aircraft collided with a nearby fence post. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_SEA04LA096.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 ↗