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.
Melbourne, FL
The student pilot was on the first leg of his initial solo cross-country flight. He was initially cleared for an approach to runway 9R at the destination airport, with a surface wind reported from 110° at 13 knots. After reporting a 7-mile final for runway 9R, tower controller directed him to land on runway 5. During landing, as the nose wheel touched down, the airplane “weathervaned” to the right. He abruptly added left rudder, which resulted in the airplane’s wheels “side drift[ing]” to the right and he lost control of the airplane. The airplane departed the runway to the right, eventually coming to rest in a grassy area adjacent to the runway. The right wing and upper fuselage were substantially damaged during the runway excursion. The pilot reported that there were no preaccident mechanical malfunctions or failures of the airplane that would have precluded normal operation. Following the accident, the flight school that operated the airplane reminded its students that when they are switched from a runway with a headwind to one with a crosswind, it is acceptable to decline an air traffic control request if students are uncomfortable with it.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained
The student pilot was on the first leg of his initial solo cross-country flight. He was initially cleared for an approach to runway 9R at the destination airport, with a surface wind reported from 110° at 13 knots. After reporting a 7-mile final for runway 9R, tower controller directed him to land on runway 5. During landing, as the nose wheel touched down, the airplane “weathervaned” to the right. He abruptly added left rudder, which resulted in the airplane’s wheels “side drift[ing]” to the right and he lost control of the airplane. The airplane departed the runway to the right, eventually coming to rest in a grassy area adjacent to the runway. The right wing and upper fuselage were substantially damaged during the runway excursion. The pilot reported that there were no preaccident mechanical malfunctions or failures of the airplane that would have precluded normal operation. Following the accident, the flight school that operated the airplane reminded its students that when they are switched from a runway with a headwind to one with a crosswind, it is acceptable to decline an air traffic control request if students are uncomfortable with it.