NTSB CAROL · Event
Event WPR13CA024
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control during an attempted go-around, which resulted in a runway excursion.
Factual narrative
The private pilot/co-owner of the tailwheel-equipped airplane overflew the non-towered, paved airport to determine the wind conditions, which he determined to be from the northwest at about 6 to 8 knots. He then flew a traffic pattern for landing on runway 26, which was 75 feet wide. During the landing flare the airplane began to drift left of the runway centerline, and at touchdown, the tail of the airplane swerved to the left. The pilot unsuccessfully attempted to correct the airplane's path, and then initiated a go-around. He reported that after adding full power for the go-around, the airplane was headed to the right, at an angle that he estimated to be about 45 degrees from the runway alignment. Before the airplane could become airborne, it exited the right side of the runway and struck a low earthen berm. The impact resulted in damage, and the end of the takeoff attempt. The airplane came to rest upright, with the right main landing gear fracture-separated from the fuselage. Additional damage included a bent propeller, a crushed nose cowl, crush damage to the lower fuselage, and bending and crush damage to both wings. Neither the pilot nor his passenger was injured, and both exited via the right-side cabin door. There was no fire. There was no recorded meteorological data for the accident airport, but review of meteorological data from an airport about 10 miles north of the accident airport indicated conditions similar to what the pilot reported. According to the pilot, he had a total flight experience of approximately 2,000 hours, including about 30 hours in the accident airplane make and model in the past 30 days. The pilot stated that there were no mechanical deficiencies or failures that contributed to the accident, but that he was uncertain as to exactly why he lost directional control. The private pilot/co-owner of the tailwheel-equipped airplane overflew the non-towered, paved airport to determine the wind conditions, which he determined to be from the northwest about 6 to 8 knots. He then flew a traffic pattern for landing on runway 26. During the landing flare the airplane began to drift left of the runway centerline, and at touchdown the tail of the airplane swerved to the left. The pilot unsuccessfully attempted to correct the airplane's path then initiated a go-around. He reported that after adding full power for the go-around, the airplane was headed to the right, at an angle that he estimated to be about 45 degrees from the runway alignment. Before the airplane could become airborne, it exited the right side of the runway and struck a low earthen berm. The airplane came to rest upright, with the right main landing gear fractured and separated from the fuselage. Additional damage included a bent propeller, a crushed nose cowl, crush damage to the lower fuselage, and bending and crush damage to both wings. There were no recorded meteorological data for the accident airport, but review of meteorological data from an airport about 10 miles north indicated conditions similar to those reported by the pilot. The pilot reported approximately 2,000 hours of a total flight experience, including about 30 hours in the accident airplane make and model in the past 30 days. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation and that he was uncertain why he lost directional control. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2012_WPR13CA024.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 (runway excursion, 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.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- 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.
Browse the full corpus — academia portal ↗