Skip to content

Atlas / NTSB / DEN03LA086

NTSB CAROL · Event

Event DEN03LA086

2003-05-23 Colorado Sprngs, Colorado, United States Airport · COS Minor 1 aircraft Status: Completed

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 ↗.

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.

Browse the full corpus — academia portal ↗