NTSB CAROL · Event
Event SEA00LA081
Aircraft involved
Probable cause & findings
An inadequately planned approach. Misjudging distance/altitude and improper remedial action were factors.
Factual narrative
On April 30, 2000, about 1215 Pacific daylight time, a Piper PA-28-140, N4413X, registered to and operated by the pilot as a 14 CFR Part 91 personal flight, landed short of the runway at Stark's Twin Oaks Airpark, Hillsboro, Oregon, and collided with a dirt bank. Visual meteorological conditions prevailed at the time and no flight plan was filed. The private pilot, the sole occupant, was not injured. The airplane was substantially damaged. The flight originated from Tillamook, Oregon, about 45 minutes prior to the accident. In a written statement, the pilot reported that he aborted the first landing because he thought that he was too high. While on the downwind leg for the second approach, the pilot realized that he was misreading the altimeter, and that his altitude was actually 500 to 600 feet MSL, when he should have been at 1,100 feet MSL (pattern altitude). The pilot applied full power to climb back up to pattern altitude, reaching 1,100 feet at the point where he turned to the base leg. The pilot reported that at any other airport he would have gone around again, however, he felt that the Twin Oaks environment discouraged go-arounds, and opted to continue the approach. The pilot stated that while on final approach, the airplane crossed the river and an open field and began to sink. The pilot reported that he would have used power to correct, however, he thought that he already had enough airspeed (70 mph), and "just pulled the nose up hoping to get a few feet altitude and reduce my airspeed. The airplane was ready to land though and I struck the bank in front of the runway..." The aircraft touched down short of the runway and collided with the dirt bank. The nose gear was pushed aft, damaging the underside of the engine and firewall. The pilot reported that his first attempt to land was aborted because he thought that he was too high. During the second attempt, while on final approach, the airplane began to sink after passing over an open field. The pilot stated that he would have used power to correct, however, he thought that he already had enough airspeed and just pulled the nose up, hoping to get a few feet of altitude and reduced airspeed. The aircraft touched down short of the runway and collided with a dirt bank. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_SEA00LA081.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 ↗