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

July 29, 2020 · Cessna 172 N · N6705E

Hudson, NY

Overview

Report Status
Probable Cause
Event Type
Accident
Date
July 29, 2020
Injury Outcomes
No injuries (1 uninjured)
Location
Hudson, NY
Aircraft
Cessna 172 N (1978)
Tail Number
N6705E
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA20CA269

The pilot, who had not flown for the three months preceding the accident, was flying the airplane for the first time since its annual inspection had been completed. Following an uneventful preflight inspection and flight to another airport, he landed the airplane at a third airport and back-taxied for departure. After traveling a short distance down the runway during the takeoff, the pilot reported that the airplane began yawing to the left. The pilot attempted to compensate for the left yaw by applying right rudder, but the left yaw continued. He then applied full right rudder but was unable to center the airplane and it departed the left side of the runway. The pilot then reduced engine power as the airplane proceeded over the downward sloping terrain off the side of the runway and into an area of dense vegetation and small trees. The airplane came to rest in the vegetation and both wings and the forward portion of the fuselage were substantially damaged. A postaccident examination of the airplane’s ailerons, rudder, and brake systems revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that the wind was light and variable about the time of the accident. Given this information, it is likely that the pilot lost directional control of the airplane during the takeoff attempt, which resulted in a runway excursion.

NTSB Probable Cause

The pilot's failure to maintain directional control during the takeoff, which resulted in a runway excursion and impact with vegetation.

Full Narrative

The pilot, who had not flown for the three months preceding the accident, was flying the airplane for the first time since its annual inspection had been completed. Following an uneventful preflight inspection and flight to another airport, he landed the airplane at a third airport and back-taxied for departure. After traveling a short down the distance down the runway during the takeoff, the pilot reported that the airplane began yawing to the left. The pilot attempted to compensate for the left yaw by applying right rudder, but the left yaw continued. He then applied full right rudder but was unable to center the airplane and it departed the left side of the runway. The pilot then reduced engine power as the airplane proceed over the downward sloping terrain off the side of the runway and into an area of dense vegetation and small trees. The airplane came to rest in the vegetation and both wings and the forward portion of the fuselage were substantially damaged. A postaccident examination of the airplane’s ailerons, rudder, and brake systems revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that the wind was light and variable about the time of the accident. Given this information, it is likely that the pilot lost directional control of the airplane during the takeoff attempt, which resulted in a runway excursion.

Flight

Event TypeAccident
Event Time14:00 EDT
Nearest AirportColumbia County (0nm WNW)
Runway21
Runway Length5350 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 N
Tail NumberN6705E
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 87 · Basc · None

Conditions

ConditionsVMC
LightDaylight
Wind250° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59
Altimeter29.93 inHg
Observation Time17:54
Weather SourceWFAC

Appendix: Source Data