The U.S. aircraft register, updated daily
Accidents · NTSB ERA17LA293 · Final report

Cessna 172 accident near Guntersville, Alabama, August 21, 2017

On August 21, 2017 at about 7:30 pm local time, a 1976 Cessna 172, registered N73929, was substantially damaged in an accident during takeoff near Guntersville, Alabama (Guntersville Muni - Joe Starne airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain directional control on takeoff.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 21, 2017 · about 7:30 pm local time · cases in 2017
Place
Guntersville, Alabama · Guntersville Muni - Joe Starne · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 N, built 1976 · all 172s on the register
Registration
N73929 · registry record · serial 17267753
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control on ground during takeoff defining event
  2. Runway excursion during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during takeoff

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • Environmental issues › Physical environment › Object/animal/substance › (general) › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 119 hours in all; 16 in this make and model; 16 in the last 90 days; 60 as pilot in command
  • Last flight review: May 9, 2017
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 8,697.4 hours
  • Last inspection: annual inspection
  • Maximum gross weight: 2,299 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total

The flight

  • Departed from: 8A1 Guntersville AL at 7:30 pm
  • Destination: CZL Calhoun GA
  • Flight plan: VFR
  • Runway 07, 5,005 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 190° at 3 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,000 ft
  • Temperature: 88°F (31°C), dew point 77°F (25°C)
  • Altimeter: 30.14 inHg
  • Observation at 7:35 pm from 8A0, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 6 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on December 11, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N73929 the same tail number, which may have belonged to a different aircraft at the time

1990-03-07MIA90LA080 · accident near Clearwater, FL · substantial damage · minor injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA17LA293.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.