Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
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.
Easton, MD
The student pilot was conducting supervised solo flights. While landing, he "accidentally" struck the runway with the propeller. The airplane was then taxied to the ramp area, and secured. According to the student pilot's flight instructor, who was supervising the solo flights, the airplane appeared to flare too high and began to porpoise.
The student pilot's improper flare, which resulted in a hard landing.
On February 12, 2004, at 1705 eastern standard time, a Cessna 172N, N734AT, was substantially damaged while landing at the Easton Airport (ESN), Easton, Maryland. The student pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight conducted under 14 CFR Part 91. According to the student pilot, he was conducting supervised solo flights. While landing on runway 22, he "accidentally" struck the runway with the propeller. The airplane was then taxied to the ramp area, and secured. According to the student pilot's flight instructor, who was supervising the solo flights, the airplane appeared to flare too high and began to porpoise. Examination of the wreckage by a Federal Aviation Administration inspector revealed substantial damage to the firewall.