NTSB CAROL · Event
Event GAA17CA325
Registry · N6193B
FAA Aircraft Registry record.
Make / Model
CESSNA 182A
Year of manufacture
1957 · 60 years old at event
Engine
CONT MOTOR O-470 SERIES (230 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19570326
ADS-B equipped
Yes — Mode-S A812F0
Registrant of record
CONNECTICUT PARACHUTISTS INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s unstabilized approach and failure to go around in rainy, gusting crosswind conditions, which resulted in a runway overrun. Contributing to the accident was the pilot’s self-induced pressure to land due to the deteriorating weather conditions.
Factual narrative
According to the pilot, he landed the airplane on the 1,800-foot asphalt runway in the rain at 70 miles per hour with full flaps. He reported that on final, he had considered a go-around due to wind and weather, but "we were low, slow, and 130 pounds below maximum gross weight with very dynamic wind conditions at the time and there are apartment buildings about 400 yards beyond the end of runway 19." During the landing, he touched down with a right crosswind, about 600 feet beyond the runway threshold. He recalled that he, retracted the flaps, and pulled the control wheel all the way aft to put as much weight as possible on the main wheels, but he "felt our ground speed was fast and we must have a tailwind." He applied heavy braking, and as the end of the runway approached, he applied full left rudder to avoid a gully that was just beyond the end of the runway. The airplane exited the end of the runway and veered to the left. The airplane entered the gully and impacted vegetation. The airplane sustained substantial damage to the right-wing spar and aileron. The nearest METAR was 10 nautical miles east of the accident site, and reported that the wind was from 270° at 13 knots and gusting to 20 knots. The visibility was 10 statute miles with light rain. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot noted that the accident could have been prevented by initiating a go-around after he realized that he could not land in the beginning of the first 1/3 of the runway. He noted that the approaching rain and wind condition added personal pressure to land before conditions deteriorated. Additionally, he reported that under normal, dry conditions, heavy braking was required to prevent an overrun. According to the pilot, he landed the airplane on the 1,800-ft-long asphalt runway in the rain at 70 mph with full flaps. He reported that, on final, he had considered conducting a go-around due to wind and weather, but "we were low, slow, and 130 pounds below maximum gross weight with very dynamic wind conditions at the time and …apartment buildings about 400 yards beyond the end of runway 19." During the landing, he touched down with a right crosswind, about 600 ft beyond the runway threshold. He recalled that he retracted the flaps and pulled the control wheel all the way aft to put as much weight as possible on the main wheels, but he "felt our ground speed was fast and we must have a tailwind." He applied heavy braking, and as the end of the runway approached, he applied full left rudder to avoid a gully that was just beyond the end of the runway. The airplane exited the end of the runway and veered left. The airplane entered the gully and impacted vegetation. The airplane sustained substantial damage to the right-wing spar and aileron. The nearest METAR was 10 nautical miles east of the accident site, and it reported that the wind was from 270° at 13 knots, gusting to 20 knots. The visibility was 10 statute miles with light rain. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot noted that the accident could have been prevented by initiating a go-around after he realized that he could not land in the first third of the runway. He noted that the approaching rain and wind conditions added personal pressure to land before conditions deteriorated. Additionally, he reported that under normal, dry conditions, heavy braking was required to prevent an overrun. 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-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Rain-Effect on equipment - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Aircraft capability-Landing distance-Capability exceeded - C
- F Personnel issues-Psychological-Personality/attitude-Motivation/respond to pressure-Pilot - F
- — Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Effect on operation
- — Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Effect on operation
Verbatim from NTSB's published report. Source file
NTSB_2017_GAA17CA325.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, unstabilized approach). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
Utilizing Deep Learning to Predict Unstabilized Approaches for General Aviation Aircraft
Unstabilized approaches pose a major hazard for general aviation aircraft. In the period from 2009 to 2019, 3,257 general aviation accidents occurred during the landing phase of flight in which loss o…
- 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.
Browse the full corpus — academia portal ↗