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.
Delta, UT
According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17 "because other traffic was using runway 17 even though winds were 050° at 3 knots." He reported that, as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nosewheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur." The student pilot departed the airport and accomplished two approaches and a landing at a third airport before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking. The student pilot reported that he could have prevented the accident by performing a go-around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe that would have prevented normal operation.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17; "because other traffic was using runway 17 even though winds were 050° at 3 knots". He reported that as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nose wheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur." The student pilot departed the airport, and accomplished two approaches and a landing at a third airport, before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking. The student pilot reported that he could have prevented the accident by performing a go around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe prior to the landing that would have prevented normal flight operation.