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.
Hagerstown, MD
The student pilot was conducting her first solo flight, and stated that during the first landing, all three of the landing gear contacted the runway simultaneously, and the airplane began to porpoise. She aborted the landing and noted that the engine sounded "slightly rougher and much louder" during the climb-out. She also noted that the airplane "struggled" to climb to traffic pattern altitude. The second approach and landing was uneventful, and after disembarking the airplane, damage was noted to the propeller. Further examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies of the airplane that would have precluded normal operation.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
The student pilot was conducting her first solo flight, and stated that during the first landing, all three of the landing gear contacted the runway simultaneously, and the airplane began to porpoise. She aborted the landing and noted that the engine sounded "slightly rougher and much louder" during the climb-out. She also noted that the airplane "struggled" to climb to traffic pattern altitude. The second approach and landing was uneventful, and after disembarking the airplane, damage was noted to the propeller. Further examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies of the airplane that would have precluded normal operation.