NTSB CAROL · Event
Event FTW98LA224
Aircraft involved
Probable cause & findings
The pilot exceeded the crosswind capability performance of the aircraft, and his delayed response in initiating a go around. Factors were gusty, crosswind and tailwind conditions, and high density altitude.
Factual narrative
On May 16, 1998, at 1830 mountain daylight time, a Mooney M20F, N6444Q, settled onto the ground during a go-around from a balked landing at Telluride Regional Airport, Telluride, Colorado. The private pilot and sole occupant was not injured and the aircraft sustained substantial damage. Visual meteorological conditions prevailed for this cross-country flight which originated from Moscow, Kansas, at 1530. No flight plan was filed. According to the pilot's accident report, he contacted the airport for a weather advisory prior to landing and was told that the winds were favoring runway 9. He flew over the airport and noted the wind direction indicator favored runway 9 as the recommended runway. While on final approach, he added full flaps and established an approach speed of 90 mph. Prior to touchdown, he received another report on the radio that the wind had shifted to 220 degrees at 20 knots with gusts to 25 knots. Calculated density altitude at the time was 11,041 feet above mean sea level, and the angle between the runway and the wind was 130 degrees. Given the reported wind speed of 20 knots with gusts to 25 knots, the crosswind and tailwind component values fall off the wind component chart. The values at the chart limits are 12 knots and 10 knots respectively. (See attached wind component chart.) According to Mooney Aircraft Flight Test, the demonstrated cross wind component is 13 knots and there is no demonstrated tail wind component. According to witnesses, the airplane touched down and as it was rolling out, the "aircraft suddenly became airborne [about 35 feet] in a nose down configuration." The pilot applied full power and retracted the landing gear. He "flew the aircraft approximately half way down the runway at about 20 feet above the ground, 10 feet left of the runway," then hit the ground. According to the airport manager, the airplane bounced twice after landing. The pilot added power and raised the landing gear. The aircraft then struck taxiway A2, approximately 4,800 feet from the approach end of runway 9. He bounced once, then landed in a drainage ditch. According to the aircraft owners' manual, "the base leg should be flown at 90 mph. Upon turning final...the aircraft will glide hands-off at approximately 80 mph." Additionally, the manual states, "under no circumstances should the aircraft be allowed to touch down in a nose-low attitude or at too high an airspeed." Post accident examination of the aircraft revealed that the propeller was destroyed, and the wings and lower fuselage sustained substantial damage. According to the pilot, he contacted the airport for a weather advisory prior to landing and was told that the winds were favoring runway 9. Prior to touchdown, he received a report on the radio that the wind had shifted to 220 degrees at 20 knots with gusts to 25 knots. The airplane touched down and as it was rolling out, the aircraft became airborne. The pilot applied full power and retracted the landing gear. He flew the aircraft approximately half way down the runway at about 20 feet above the ground, hit the ground, bounced once, then landed in a drainage ditch. Calculated density altitude at the time was 11,041 feet above mean sea level, and the angle between the runway and the wind was 130 degrees. Given the reported wind speed of 20 knots with gusts to 25 knots, the crosswind and tailwind component values fall off the wind component chart. The values at the chart limits are 12 knots and 10 knots respectively. According to Mooney Aircraft Flight Test, the demonstrated cross wind component is 13 knots and there is no demonstrated tail wind component. The propeller was destroyed, and the wings and lower fuselage sustained substantial damage. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_FTW98LA224.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 ↗