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

June 30, 2010 · Cessna 172S · N6064R

Chesapeake, VA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 30, 2010
Injury Outcomes
No injuries (1 uninjured)
Location
Chesapeake, VA
Aircraft
Cessna 172S
Tail Number
N6064R
Operator
Horizon Flight Center
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA10CA363

During a preflight inspection of the airplane, a certificated flight instructor discovered substantial damage to the underside of the fuselage and reported it to the flight school. Upon further examination, substantial damage to the firewall was also found. Two days before the damage was discovered, the accident airplane underwent a routine phase inspection. The maintenance personnel who examined the airplane for the phase inspection did not report any damage at that time. According to flight school records, there were three flights between the maintenance inspection and the damage report. The first two flights, which occurred later on the same day as the phase inspection, were dual-instructional flights. The third flight, which occurred the next day, and the day before the damage was discovered, was a student pilot solo cross country flight. Interviews conducted by Federal Aviation Administration inspectors with the pilots of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the student pilot did not observe the damage prior to his solo flight.

NTSB Probable Cause

Personnel issues-Action/decision-Action-Incorrect action performance-Not specified - C

Full Narrative

During a preflight inspection of the airplane, a certificated flight instructor discovered substantial damage to the underside of the fuselage and reported it to the flight school. Upon further examination, substantial damage to the firewall was also found. Two days before the damage was discovered, the accident airplane underwent a routine phase inspection. The maintenance personnel who examined the airplane for the phase inspection did not report any damage at that time. According to flight school records, there were three flights between the maintenance inspection and the damage report. The first two flights, which occurred later on the same day as the phase inspection, were dual-instructional flights. The third flight, which occurred the next day, and the day before the damage was discovered, was a student pilot solo cross country flight. Interviews conducted by Federal Aviation Administration inspectors with the pilots of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the student pilot did not observe the damage prior to his solo flight.

Flight

Event TypeAccident
Event Time12:00 EDT
Nearest AirportChesapeake Regional Airport (0nm)
Runway05
Flight Plan FiledUnknown
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172S
Tail NumberN6064R
Aircraft CategoryAir
DamageSubstantial
OperatorHorizon Flight Center
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-L2A · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 1 · Unknown

Conditions

ConditionsVMC
LightDaylight
WindCalm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0

Appendix: Source Data