Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 3, 2008 · Cessna 172M · N73594

Jefferson, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 3, 2008
Injury Outcomes
1 injury (1 minor injury)
Location
Jefferson, NC
Aircraft
Cessna 172M
Tail Number
N73594
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
NYC08CA269

The solo student pilot was practicing takeoffs and landings to a full stop in the Cessna 172M on runway 28. He stated that the automated weather station reported winds of 3 to 4 knots from 290 degrees. He completed three takeoffs and landings uneventfully, and taxied back for a fourth departure. The pre-takeoff checks were normal, and the pilot added power for the zero-flap takeoff. When the airplane speed was approximately 45 to 50 knots, the airplane "pulled hard to the left." The pilot aborted the takeoff by retarding the power. The airplane departed the left side of the paved runway surface, skidded through the grass, and descended an embankment, where it rolled over and came to rest inverted. The pilot shut down the airplane, and exited unassisted. There was no fire. The pilot had approximately 26 total hours of flight experience, and approximately 20 hours in the accident airplane. The pilot stated he thought there was a possible mechanical problem with the airplane, like a "detached rudder cable." The Federal Aviation Administration inspector did not examine the airplane for flight control continuity during his on-scene examination. The certificated flight instructor/owner, who was also the mechanic for the airplane, stated that he did not find any mechanical problems with the airplane after the accident.

NTSB Probable Cause

A loss of directional control during the takeoff roll for undetermined reasons. Contributing to the severity of the event was the descending embankment adjacent to the runway.

Full Narrative

The solo student pilot was practicing takeoffs and landings to a full stop in the Cessna 172M on runway 28. He stated that the automated weather station reported winds of 3 to 4 knots from 290 degrees. He completed three takeoffs and landings uneventfully, and taxied back for a fourth departure. The pre-takeoff checks were normal, and the pilot added power for the zero-flap takeoff. When the airplane speed was approximately 45 to 50 knots, the airplane "pulled hard to the left." The pilot aborted the takeoff by retarding the power. The airplane departed the left side of the paved runway surface, skidded through the grass, and descended an embankment, where it rolled over and came to rest inverted. The pilot shut down the airplane, and exited unassisted. There was no fire. The pilot had approximately 26 total hours of flight experience, and approximately 20 hours in the accident airplane. The pilot stated he thought there was a possible mechanical problem with the airplane, like a "detached rudder cable." The Federal Aviation Administration inspector did not examine the airplane for flight control continuity during his on-scene examination. The certificated flight instructor/owner, who was also the mechanic for the airplane, stated that he did not find any mechanical problems with the airplane after the accident.

Flight

Event TypeAccident
Event Time17:00 EDT
Nearest AirportAshe County Airport (0nm)
Runway28
Runway Length4293 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172M
Tail NumberN73594
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 25 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind290° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point54
Altimeter30.09 inHg
Observation Time21:02
Weather SourceWFAC

Appendix: Source Data