ERA17LA293
2017-08-21 · Guntersville, Alabama, United States · None · 1 aircraft · Status: Completed
Airport 8A1
Current FAA registration · N73929
- Make / Model
- CESSNA 172N
- Year of manufacture
- 1976 · 41 years old at event
- Engine
- LYCOMING 0-320 SERIES (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19760927
- ADS-B equipped
- Yes — Mode-S A9EF3A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control on takeoff.
Factual narrative
On August 21, 2017, about 1430 central daylight time, a Cessna 172N, N73929, sustained substantial damage during takeoff from the Guntersville Municipal Airport (8A1), Guntersville, Alabama. The private pilot was not injured. The airplane was registered to a private corporation and operated by Henderson Aviation. Visual meteorological conditions prevailed for the flight that was being conducted as a Title 14 Code of Federal Regulations Part 91 flight. A visual flight rules flight plan was filed for the personal flight that was destined for the Tom B. David Airport (CZL), Calhoun, Georgia.The pilot stated that he departed CZL earlier that day and flew direct to 8A1, where he planned to do a touch-and-go landing and then return to CZL. He stated that he made a normal landing on runway 07, but when the nose wheel touched down, the airplane began to shake. The shaking dissipated as the airplane slowed down. The pilot then raised the flaps, turned off the carburetor heat and applied full throttle to take off. As the airplane began to accelerate, it veered sharply to the left and departed the runway. The pilot was unable to stop the left turn even with full right rudder applied and the airplane traveled down a slope and into brush. The pilot called the operator of the airplane, who called the airport for assistance to have the airplane towed back on to the runway. The airplane was inspected by a mechanic, who determined that it was not "severely" damaged; thus, the pilot decided to fly the airplane back to CZL. The pilot elected to perform one touch-and-go landing at CZL before returning to 8A1. He said the takeoff and landing were normal, but when he added engine power to takeoff again, the airplane again veered left off the runway even with full right rudder applied. The nose wheel struck an object, which resulted in damage to the engine mounts, propeller, and airframe. According to the operator, after the first incident, he talked to the mechanic at 8A1 and it was determined that there was no damage to the airplane and no mechanical issues were identified with the nose-wheel. The operator offered to come pick the pilot up if he did not want to fly the airplane back to Georgia, but the pilot declined. A short while later, the operator received a text message that the airplane had gone off the runway again and was more heavily damaged. The operator then flew to Guntersville and picked up the pilot. The operator said that the airplane had no previous mechanical problems with steering or with the nose wheel. The airplane was a "daily rental" and flew regularly. The operator, who was also a flight instructor, flew with the pilot after the accident and performed 7-9 takeoffs and landings without incident. The pilot held a private pilot certificate with a rating for airplane single-engine land. He reported a total flight experience of 119 hours, of which 16 hours were in the same make and model as the accident airplane. The pilot's last Federal Aviation Administration (FAA) third-class medical certificate was issued on April 26, 2017. The weather at Albertville Regional Airport (8A0), Albertville, Alabama, about 11 miles south of the accident site, at 1435, was reported as wind from 190° at 3 knots, visibility 10 miles, clouds broken at 5,000 ft, temperature 31° C, dew point 25° C, and an altimeter setting of 30.15 inches of mercury. During the takeoff roll after a touch-and-go landing, the airplane veered sharply to the left and departed the runway. The private pilot was unable to stop the left turn, even with full right rudder applied, and the airplane traveled down a slope and into brush. The airplane was recovered and inspected by a local mechanic, who spoke with the operator and determined that the airplane was not substantially damaged and that there were no mechanical issues with the nosewheel. The pilot subsequently chose to take off and then perform a touch-and-go landing before flying the airplane back to his home airport. He stated that the takeoff and landing were normal, but when he added power to take off again, the airplane veered left off the runway, even with full right rudder applied. The nosewheel struck an object, which resulted in damage to the engine mounts, propeller, and airframe. According to the operator, the airplane had no previous mechanical problems with steering or the nosewheel. Because the airplane had no previous records of problems with steering or the nosewheel, the mechanic did not find any mechanical issues after the first runway excursion, and the pilot was able to successfully take off before the touch-and-go, it is likely that the pilot failed to maintain directional control on takeoff. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- — Environmental issues-Physical environment-Object/animal/substance-(general)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2017_ERA17LA293.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 (runway excursion). 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.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.