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.
Jacksonville, FL
According to the student pilot, he was performing his second solo flight in the traffic pattern. During the flare on the first landing, the airplane porpoised on the runway, resulting in the nose wheel impacting the runway three times, oscillating harder each time. After the first landing, an air traffic controller contacted the flight school to inform them of the porpoised landing. The student pilot completed three more landings, taxied back to the ramp, and exited the airplane. The first assessment of the airplane revealed no obvious damage, and it was flown two more times before another examination of the airplane by the operator revealed substantial damage to the firewall. According to a Federal Aviation Administration inspector, there were no preexisting mechanical anomalies with the airplane.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
According to the student pilot, he was performing his second solo flight in the pattern. During the flare on the first landing, the airplane porpoised on the runway, resulting in the nose wheel impacting the runway three times, oscillating harder each time. After the first landing, an air traffic controller contacted the flight school to inform them of the porpoised landing. The student pilot completed three more landings, taxied back to the ramp, and exited the airplane. The first assessment of the airplane revealed no obvious damage, and it was flown two more times before another examination of the airplane by the operator revealed substantial damage to the firewall. According to a Federal Aviation Administration inspector, there were no preexisting mechanical anomalies with the airplane.