NTSB CAROL · Event
Event CEN12LA234
Aircraft involved
Probable cause & findings
The pilot's decision to land with a direct tailwind, which resulted in a loss of directional control, and his subsequent decision to attempt a go-around so late in the landing roll, which resulted in a stall.
Factual narrative
On April 4, 2012, at 1340 mountain daylight time, a Cessna Corvalis LC41-550FG, N1178L, registered to Performance by Design of Tuscon, Arizona, sustained substantial damage when it veered off runway 09 after landing at the Telluride Municipal Airport (TEX), Telluride, Colorado. The private pilot and his three passengers were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight operated under the provisions of 14 Code of Federal Regulations Part 91. The flight originated at 1200 from Flagstaff, Arizona, and Telluride was its destination. After an uneventful cross country flight, the pilot announced his intention to enter a right base for runway 9, even though there was a slight tailwind. He said that he had studied the airport the night before and felt that runway 9 was the best approach and landing for the field even with a slight tailwind. The pilot stated that after crossing over the numbers, the airplane floated longer than he anticipated and touched down just before the 3,000 foot marker. The touchdown was straight and centered. The pilot felt comfortable that he had plenty of runway to safely bring the airplane to a stop and was expecting a smooth and straight rollout. Soon after touchdown, the airplane pulled to the left and the pilot responded by applying brakes with more pressure on the right brake. The airplane corrected slightly, so he eased off the brakes. The airplane was still pulling left so he repeated the process of right dominated braking but the airplane continued to pull left. At this point, the pilot realized that he was not going to be able to keep the airplane on the runway. He considered locking the brakes up and riding it out but felt that he could execute a go-around. As the pilot advanced the throttle and eased back on the control stick, the engine did not respond. The airplane nosed up, stalled, and came down off the left side of the runway. The pilot and all 3 passengers exited the airplane uninjured. The reported wind at TEX about 5 minutes prior to the accident was from 270 at 12 knots, gusting to 16 knots.
METAR
KTEX 041935Z AUTO 27012G16KT 10SM CLR 10/M09 A3005 RMK AO2 FAA inspection of the airplane at the airport confirmed substantial damage to the integral composite main spars. Additionally, all three landing gear had sheared from the airplane during the accident sequence. Examination of the flight controls and brake system did not show any preexisting mechanical malfunction or abnormalities. After an uneventful cross-country flight, the pilot announced to air traffic control his intention to enter the traffic pattern on right base leg for runway 9, even though there was a slight tailwind. After crossing over the numbers, the airplane floated longer than the pilot anticipated and touched down just before the 3,000-foot marker. The touchdown was straight and centered. The pilot felt comfortable that he had plenty of runway to safely bring the airplane to a stop and was expecting a smooth and straight rollout. Soon after touchdown, the airplane pulled to the left, and the pilot responded by applying brakes, with more pressure on the right brake. The airplane corrected slightly, and he eased off the brakes. The airplane was still pulling left, so he repeated the process of right-dominated braking, but the plane continued to pull left. At this point, the pilot realized that he was not going to be able to keep the airplane on the runway. He considered locking up the brakes and “riding it out” but thought that he could execute a go-around. According to the pilot, he advanced the throttle and eased back on the control stick, and the engine did not respond. The airplane nosed up, stalled, and came down off the left side of the runway. Examination of the flight controls and brake system did not show any preexisting mechanical malfunction or failures that would have precluded normal operation. The reason for the engine’s lack of response, as reported by the pilot, when he tried to initiate a go-around could not be verified. It is unknown whether a go-around with normal throttle response so late in the landing/rollout sequence could have prevented the accident. The reported wind at the airport about 5 minutes before the accident was from 270 degrees at 12 knots, gusting to 16 knots. Since the pilot landed on runway 9, the airplane would have encountered a direct tailwind of at least 12 knots, not taking into account the reported 16-knot gusts. It is likely that the tailwind influenced the airplane’s pull to the left after touchdown. 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-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
- — Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Contributed to outcome
- 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_CEN12LA234.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 (stall, 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 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- 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…
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
Browse the full corpus — academia portal ↗