ERA22FA161
2022-03-19 · Dahlonega, Georgia, United States · Fatal · 1 aircraft · Status: Completed
Airport 9A0
Aircraft involved
Probable cause & findings
The pilot’s delay in initiating a go-around and his failure to maintain airplane control during the initial climb, which resulted in the exceedance of the airplane’s critical angle of attack and an aerodynamic stall.
Factual narrative
HISTORY OF FLIGHTOn March 19, 2022, about 1852 eastern daylight time, a Cessna 172H, N1410F, was substantially damaged when it was involved in an accident near Dahlonega, Georgia. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Review of automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane departed Athens Ben Epps Airport (AHN), Athens, Georgia, about 1817. According to the ADSB data, witness reports, and a video from an off-airport security camera, the airplane flew a straight-in approach to runway 33 at Lumpkin County-Wimpy’s Airport (9A0), Dahlonega, Georgia. Two witnesses stated that the airplane approached “fast” with the flaps retracted. ADS-B data showed that the groundspeed was about 85 knots. The airplane touched down on the runway and bounced twice on its nose landing gear. When the airplane was toward the end of the runway, the engine noise increased, and the airplane began a climbing left turn to clear trees, which was followed by the sound of impact. The airplane wreckage was located in a residential yard beyond the end of the runway. PERSONNEL INFORMATIONThe pilot obtained his private pilot certificate about 1 year before the accident and had accumulated about 94 hours of total flight experience at the time of the accident. METEOROLOGICAL INFORMATIONThe weather reporting station nearest to the accident site, about 20 nautical miles southeast, reported winds from 290° at 13 knots, gusting to 22 knots. Given the runway orientation, wind from 290° would have resulted in a left quartering headwind for the pilot’s straight-in approach. Witnesses at the airport reported “calm,” “very light,” or “little to no" wind about the time of the accident, with one noting that the pilot may not have known that “the winds blowing earlier in the day had died down.” No evidence indicated that the pilot received a weather briefing before the flight. WRECKAGE AND IMPACT INFORMATIONThe wreckage came to rest upright oriented on a magnetic heading of about 120°. Both wing tanks were breached, and a strong smell of fuel was present at the accident site. A 65-ft debris path was observed along a magnetic heading of 270°. the debris path began with tree scars that were at a height of about 50 ft. A branch recovered along the debris path exhibited a 45° cut with gray paint transfer. A crater that was about 3 ft long, 2ft wide, and 1 ft deep was observed along the debris path about 10 ft from the wreckage. The wreckage remained intact. Both wings exhibited leading-edge damage; the left wing exhibited more damage outboard. The flaps and ailerons remained attached to their respective wing. The empennage remained intact and was canted to the left; it was undamaged except for left horizontal stabilizer leading-edge damage. Flight control continuity was confirmed from all flight control surfaces to the cabin area. Measurement of the flap actuator corresponded to flaps in the retracted position. Measurement of the elevator trim jackscrew corresponded to a 10° trim-tab-up position; the trim wheel in the cockpit was set at the neutral/takeoff position. The cockpit area was crushed. GPS data were recovered from a ForeFlight application on the pilot’s iPad. The engine remained attached to the airframe, and the propeller remained attached to the engine. Both propeller blades exhibited chordwise scratching and leading-edge gouging. The propeller was able to be rotated by hand. Crankshaft, camshaft, and valve train continuity were confirmed, and thumb compression was attained on all cylinders. Both magnetos were rotated by hand and produced spark at all leads. The carburetor was disassembled, and its components remained intact. Examination of the engine revealed no preimpact mechanical malfunctions. FLIGHT RECORDERSA copy of the security video footage was forwarded to the National Transportation Safety Board Vehicle Recorders Laboratory, Washington, DC (for more information, see Video Study in the public docket for this accident). The pilot obtained his private pilot certificate about 1 year prior to the accident and had accumulated a total flight experience of approximately 94 hours at the time of the accident. Toward the end of the cross-country flight, the pilot flew a straight-in approach to a valley airport. The airplane made a highspeed approach (about 95 knots true airspeed) with the flaps retracted. Witnesses reported that the airplane touched down and bounced twice on its nose landing gear. When the airplane was toward the end of the runway, engine noise increased, and the airplane began a climbing left turn to clear trees. The airplane subsequently impacted terrain. Postaccident examination of the wreckage revealed no preimpact mechanical malfunctions. The debris path and impact signatures were consistent with an aerodynamic stall. Based on the evidence, the pilot likely made a delayed decision to perform a go-around after touchdown and exceeded the airplane’s critical angle of attack as the airplane began the climbing left turn to avoid trees. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- — Personnel issues-Action/decision-Action-Delayed action-Pilot
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded
- — Personnel issues-Experience/knowledge-Experience/qualifications-(general)-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2022_ERA22FA161.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 (stall, go-around). All research papers
- NASA NTRS 2023 · Reprint (Version printed in journal) Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft
The NASA Emergency Locator Transmitter Survivability and Reliability project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (E…
- NASA NTRS 2019 · Conference Paper Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM) Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- 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…