NTSB CAROL · Event
Event WPR12LA384
Aircraft involved
Probable cause & findings
The pilot’s delay in executing a go-around, which resulted in a runway overrun. Contributing to the accident were the pilot’s failure to establish the proper glidepath and airspeed on final approach and his improper use of flaps during the go-around.
Factual narrative
On August 31, 2012, about 1610 mountain standard time, a Cessna 182R, N5458N, sustained substantial damage during a runway overrun while landing at St. Johns, Arizona. The private pilot, the sole occupant, received minor injuries. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the personal cross-country flight, which had originated from Dalhart, Texas, about 3 hours before the accident. A flight plan had not been filed. The pilot said that he started his traffic pattern higher than recommended due to his high density altitude concerns. He said his final approach was longer than normal and his speed was fast. He put the flaps down full and raised the nose to bleed off more airspeed. A witness on the ground said the airplane passed the midfield intersection and was still quite high off the runway. The witness said the accident pilot appeared to be performing a go-around. But then the airplane descended to the runway and touched down with about 3/4 of its length behind him. The pilot said that he realized that the airplane was high, fast, and long for a normal landing. He decided to go around. He applied full power; he reduced flaps by 10 degrees, and the airplane started to climb. However, the airplane then began to descend; "it was sort of mushing out of the sky." He reduced the engine power, landed, and began heavy braking. A witness on the ground said that he observed black smoke coming from the main landing gear tires after the airplane touched down. The airplane departed the end of the runway and went through the airport's perimeter fence. The airplane came to rest on its nose with the right wing strut bent, and both wings bent and wrinkled. After he exited the airplane, the pilot discovered that the flaps were fully retracted. The airplane's manufacturer published a Pilot's Operating Handbook, which states that after the throttle is moved to full power for a go-around, the wing flaps shall be retracted from 40 to 20 degrees. The pilot stated that he had just purchased this particular airplane 4 days earlier. He said he practiced two full stop landings and takeoffs, but he did not practice any go-arounds. The pilot stated that the accident might have been avoided if he had practiced go-arounds with incremental raising of the flaps, or stopped the approach and exited the traffic pattern when he realized he was too high. The pilot reported that the airplane was high and fast on final approach for landing, so he lowered the flaps to 40 degrees and raised the nose to slow down. The pilot then decided to go around, so he applied full power and raised the flaps to 30 degrees. The airplane began to climb, but then it started descending. The pilot reduced the engine power, landed the airplane, and applied heavy braking. The airplane subsequently overran the end of the runway and went through the perimeter fence. After he exited the airplane, the pilot found the flaps fully retracted. The airplane's Pilot Operating Handbook stated that go-arounds should be performed with the flaps at 20 degrees. Further, the pilot should have performed a go-around when he first noticed that the airplane was too high and fast on the final approach. 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-Action-Delayed action-Pilot - C
- F Personnel issues-Task performance-Use of equip/info-Use of policy/procedure-Pilot - F
- F Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - F
Verbatim from NTSB's published report. Source file
NTSB_2012_WPR12LA384.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 ↗