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

February 16, 2020 · Cessna 172 M · N1126U

Rochester, NY

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 16, 2020
Injury Outcomes
No injuries (2 uninjured)
Location
Rochester, NY
Aircraft
Cessna 172 M (1976)
Tail Number
N1126U
Operator
Schubert Brothers Aviation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA20CA102

The pilot reported that, during his preflight inspection, he noted several anomalies. He added that the right rudder pedal was not functioning properly before the flight during taxi; however, he decided to go ahead with the flight. After takeoff, he reconsidered the flight and returned to the airport. While on approach to landing, the airplane was hard to control, so he chose to troubleshoot the control issue in the air and initiated a go-around. The airplane lifted off the runway and began to climb but then rapidly rolled right and then left and then impacted terrain. In addition, the pilot stated he lost directional control due to a rudder anomaly during a flight in the airplane several weeks earlier. A Federal Aviation Administration inspector who examined the airplane reported that the wings had sustained substantial damage. Postaccident examination of the rudder control system revealed no evidence of any preaccident mechanical failures or malfunctions that would have precluded normal operation.

NTSB Probable Cause

The pilot's failure to maintain airplane control during a go-around. Contributing to the accident was the pilot’s decision to take off after perceiving a rudder issue during taxi operations.

Full Narrative

The pilot reported that, while on approach to landing, the airplane was hard to control, so he elected to troubleshoot the control issue in the air and initiated a go-around. The airplane lifted off the runway and began a climb, but rapidly rolled to the right, then left and impacted terrain. The pilot further described that the right rudder pedal was not functioning properly prior to the flight during taxi and that he had difficulty maintaining directional control during the approach. In addition, the pilot stated he lost directional control due to a rudder anomaly during a flight in the airplane that occurred several weeks prior. A Federal Aviation Administrator inspector examined the airplane after the accident and confirmed that the airplane's wings had been substantially damaged during the accident. A postaccident examination of the rudder control system revealed no evidence of a pre accident mechanical failure or malfunction that would have precluded normal operation.

Flight

Event TypeAccident
Event Time11:30 EST
Nearest AirportGreater Rochester Intl (1nm)
Runway25
Runway Length4000 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 M
Tail NumberN1126U
Aircraft CategoryAir
DamageSubstantial
OperatorSchubert Brothers Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 -E2D · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 68 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind250° @ 9 kt
Visibility10 sm
CeilingOvercast 1500 ft
Temperature / Dew Point36 C / 28 C
Altimeter30.04 inHg
Observation Time16:52
Weather SourceWFAC

Appendix: Source Data