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 25, 2010 · Cessna 172S · N387AF

Frederick, MD

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 25, 2010
Location
Frederick, MD
Aircraft
Cessna 172S
Tail Number
N387AF
Operator
Frederick Flight Center
Aircraft Damage
Substantial
NTSB Number
ERA10CA468

During a Phase III inspection of the airplane, the Director of Maintenance for the operator noticed that the airplane's firewall was damaged. The damage was reported to the nearest Federal Aviation Administration (FAA) Flight Standards District Office, and verified by the FAA. The damage occurred between the Phase II and Phase III inspection. The airplane had flown 48.2 hours since the Phase II inspection. According to the FAA, the damage was a result of a hard landing. The purpose of the flight and composition of the flight crew was not determined. In addition, the date, actual location, and time of the accident were not determined.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C

Full Narrative

During a Phase III inspection of the airplane, the Director of Maintenance for the operator noticed the firewall was damaged. The damage was reported to the nearest Federal Aviation Administration (FAA) Flight Standards District Office, and verified by the FAA. The damage occurred between the Phase II and Phase III inspection. The airplane had flown 48.2 hours since the Phase II inspection. According to the FAA, the damage was a result of a hard landing. The purpose of the flight and composition of the flight crew was not determined. In addition, the date, actual location, and time of the accident were not determined.

Flight

Event TypeAccident
Event Time12:00 EDT
Nearest AirportFreerick Municipal Airport (0nm)
Runway05
Runway Length5220 ft
Runway Width100 ft
Flight Plan FiledUnknown
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

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

People & Injuries

Fatal0
Serious0
Minor0
Uninjured0
Total0
Crew 1Age 1 · None
Crew 2Age 1

Conditions

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

Appendix: Source Data