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.
Grand Forks, ND
The accident occurred during the student pilot's second landing on his first solo flight. He stated that the airplane was on a stabilized approach as it crossed over the runway threshold at 63 knots. He reduced engine power and began to flare as the airplane was abeam the Precision Approach Path Indicator (PAPI) system. He reported that the landing flare was "somewhat short" and that the airplane landed hard on its main landing gear. He reduced his back pressure on the control yoke and the nose wheel contacted the runway. The airplane then bounced several times, alternating between the nose and main landing gear, before stabilizing on a landing rollout. A postaccident inspection of the aircraft revealed the lower engine firewall and forward floorboards were substantially deformed. The student pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C
The accident occurred during the student pilot's second landing on his first solo flight. He stated that the airplane was on a stabilized approach as it crossed over the runway threshold at 63 knots. He reduced engine power and began his landing flare as the airplane was abeam the Precision Approach Path Indicator (PAPI) system. He reported that the landing flare was "somewhat short" and that the airplane landed hard on its main landing gear. He reduced his backpressure on the control yoke and the nose wheel contacted the runway. The airplane then bounced several times, alternating between the nose and main landing gear, before stabilizing on a landing rollout. An after-flight inspection revealed the lower engine firewall and forward floorboards were substantially deformed. The student pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane.