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.
Lancaster, OH
The student pilot reported that the purpose of the flight was to practice flight maneuvers. He recalled that upon conclusion of the maneuver practice, he made a normal approach to runway 28. He reported that during the landing flare he encountered a crosswind gust, the airplane floated, and the airplane landed hard. He recalled that after the hard landing, he was unsatisfied with his landing performance. The student pilot reported that he decided to takeoff, stayed in the pattern, landed with full flaps and more airspeed, and accomplished "a controlled, more smooth touchdown." However, when he showed up for his next flight three days later, he was informed that the airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies with the airplane during his flight that would have prevented normal flight operations. The meteorological aerodrome report at the accident airport about the time of the accident indicated the wind direction was out of 270 degrees true at 9 knots, gusting to 19 knots.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Not attained/maintained - C
The student pilot reported that the purpose of the flight was to practice flight maneuvers. He recalled that upon conclusion of the maneuver practice, he made a normal approach to runway 28. He reported that during the landing flare he encountered a crosswind gust, the airplane floated, and the airplane landed hard. He recalled that after the hard landing, he was unsatisfied with his landing performance. The student pilot reported that he decided to takeoff, stayed in the pattern, landed with full flaps and more airspeed, and accomplished "a controlled, more smooth touchdown." However, when he showed up for his next flight three days later, he was informed that the airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies with the airplane during his flight that would have prevented normal flight operations. The meteorological aerodrome report at the accident airport about the time of the accident indicated the wind direction was out of 270 degrees true at 9 knots, gusting to 19 knots.