NTSB CAROL · Event
Event DEN03LA086
Aircraft involved
Probable cause & findings
the pilot's improper decision to land in the reported crosswind conditions, and his failure to maintain aircraft control. Contributing factors were the crosswind, rough terrain, airport stop sign, and fence.
Factual narrative
On May 23, 2003, at 2153 mountain daylight time, a Mooney M20K, N231JM, registered to and operated by the pilot, was substantially damaged when it impacted terrain during landing flare at Colorado Springs Municipal Airport, Colorado. The private pilot and two passengers sustained minor injuries. Night visual meteorological conditions prevailed, and no flight plan had been filed for the personal flight being conducted under Title 14 CFR Part 91. The flight originated from Scottsdale, Arizona, approximately 1800 Pacific daylight time. The Colorado Springs METAR (Aviation Routine Weather Report) that was in effect indicated the winds were from 130 degrees at 12 knots. The tower controller advised the pilot he could have the runway of his choice because the winds were variable. The pilot elected to land on runway 35R. When the pilot was on final approach for runway 35R, the controller advised the winds were variable between 080 and 090 degrees at 15 knots. According to the pilot, the airplane "received two large gusts from [the] right" during the landing flare. The first gust pushed the airplane to the left side of the runway, and he added power to go-around. The second gust hit the airplane and the pilot "found [they] were completely to the left of [the] runway." The engine was developing full power and the airplane was accelerating, but it would not climb. He felt something "clip" the airplane, causing it to veer left towards the northwest. The pilot then reduced power, shut off the fuel, and attempted to stop the airplane. The airplane traveled across rough terrain, struck a stop sign on the service road between runway 35R and Echo taxiway, then struck a 10 foot chain link perimeter fence, collapsing the landing gear, and came to rest 1/3-mile northwest from the runway. Three impact marks on each wing were the result of the collision with the fence: one inboard, another one-third of the way down the wing, and one at the tip of the wing. The vertical stabilizer struck a wire at the top of the fence and was torn. The local METAR reported the winds at 130 degrees at 12 knots. The tower controller advised the pilot he could have the runway of his choice because the winds were variable. The pilot elected to land on runway 35R. When the pilot was on final approach, the controller advised the winds were variable between 080 and 090 degrees at 15 knots. During the flare, the airplane encountered two wind gusts from the right. The first gust pushed the aircraft to the left side of the runway. The pilot added power to go around. The second gust pushed the airplane further left and off the runway. The engine was developing full power and the airplane was accelerating, but it would not climb. He felt something "clip" the airplane, causing it to veer left. The pilot then reduced power, shut off the fuel, and attempted to stop the airplane. The airplane traveled across rough terrain, struck a stop sign on the service road between the runway and a taxiway, then struck a 10-foot chain link perimeter fence, collapsing the landing gear. The airplane came to rest 1/3-mile northwest from the runway. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_DEN03LA086.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 ↗