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 10, 2023 · Cessna 172M · N20268

Marysville, CA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
August 10, 2023
Injury Outcomes
No injuries (2 uninjured)
Location
Marysville, CA
Aircraft
Cessna 172M (1972)
Tail Number
N20268
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR23LA315

The flight instructor reported that during an instructional flight, he was conducting a high-speed taxi exercise on the runway with a student pilot, to work on rudder control. He instructed the student to remain at or below 50 mph and that they would begin slowing the airplane about 1,000 ft from the departure end of the runway. About halfway down the length of the runway, the instructor noticed that the airspeed seemed high, and he informed the student that they needed to decrease the airplane’s speed; however, the airplane continued to accelerate. When the instructor told the student to begin their deceleration, the airplane did not decelerate as expected. As the airplane overran the runway, the instructor took the flight controls and elected to take off. The airplane was flown to the originating airport, where substantial damage to the horizontal stabilizer and elevator was discovered during postflight inspection, which resulted from impact with a runway end light during the runway excursion. The instructor reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.

NTSB Probable Cause

The flight instructor’s failure to monitor the airplane’s speed during a high-speed taxi, resulting in a runway excursion.

Full Narrative

The flight instructor reported that during an instructional flight, he was conducting a high-speed taxi exercise on the runway with a student pilot, to work on rudder control. He instructed the student to remain at or below 50 mph and that they would begin slowing the airplane about 1,000 ft from the departure end of the runway. About halfway down the length of the runway, the instructor noticed that the airspeed seemed high, and he informed the student that they needed to decrease the airplane’s speed; however, the airplane continued to accelerate. When the instructor told the student to begin their deceleration, the airplane did not decelerate as expected. As the airplane overran the runway, the instructor took the flight controls and elected to take off. The airplane was flown to the originating airport, where substantial damage to the horizontal stabilizer and elevator was discovered during postflight inspection, which resulted from impact with a runway end light during the runway excursion. The instructor reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.

Flight

Event TypeAccident
Event Time14:05 PDT
Nearest AirportYuba County (0nm)
Runway32
Runway Length6007 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

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

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 17 · Third Class · None
Crew 2Age 60 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point59 F
Altimeter29.93 inHg
Observation Time13:53
Weather SourceWFAC

Appendix: Source Data