CEN12LA113
2011-12-26 · St. Paul, Minnesota, United States · None · 1 aircraft · Status: Completed
Airport STP
Aircraft involved
Probable cause & findings
The pilot's decision to land on a runway with a gusting, quartering tailwind and his inadequate compensation for the wind, which resulted in a hard landing.
Factual narrative
On December 26, 2011, about 1400 central standard time, a Cessna 182J, N2618F, sustained substantial damage as a result of a hard landing on runway 14 at the St. Paul Downtown Airport (STP), St. Paul, Minnesota. The private pilot, the sole occupant, was not injured. The airplane was registered to and operated by the Mentone Flying Club under the provisions of the 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident and no flight plan was filed. The flight departed from the Rice Lake Regional Airport (RPD), Rice Lake, Wisconsin, and was en route to STP. The pilot reported that he made two visual approaches to runway 27 at STP. On the first approach he executed a planned go-around. On the second, he planned to make a full stop landing; however, during the landing flare, a gust of wind caused the airplane to drift so he performed another go-around. The pilot decided to change runways for the next landing attempt, and he elected to land on runway 14; although the STP air traffic controller informed the pilot that the wind was from 230 degrees. The pilot reported that he continued the visual approach and was on glideslope, airspeed, and centered on the runway as he approached the runway landing zone. He reported that he encountered a “big” gust of wind during the landing flare. The airplane landed hard on its nose on the runway centerline about 500 – 1000 feet from the runway threshold. The postaccident inspection of the airplane revealed that the airplane’s firewall was bent. The pilot reported that there was no mechanical malfunction or failure of the airplane. At 1405, the surface weather observation at STP was: wind 240 degrees at 19 knots gusting to 26 knots; 10 miles visibility; sky clear; temperature 11 degrees Celsius; dew point -6 degrees Celsius; altimeter 29.71. Although the tower air traffic controller informed the pilot that the wind was from 230 degrees, the pilot elected to land on runway 14 instead of runway 27. He reported that the visual approach was stabilized as he approached the runway landing zone. However, the airplane encountered a gust of wind during the landing flare and landed hard on its nose on the runway centerline about 500 to 1,000 feet from the runway threshold. Postaccident examination of the airplane revealed that the firewall was bent. The pilot reported that there was no mechanical malfunction or failure of the airplane. Five minutes after the accident, the reported surface wind was 240 degrees at 19 knots gusting to 26 knots. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Action/decision-Action-Incorrect action selection-Pilot - C
- — Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Contributed to outcome
- — Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2011_CEN12LA113.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- 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…