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.
Charlottesville, VA
According to the pilot, he established a "crab angle to track" the centerline of the runway and maintained about 70 knots on the final leg of the traffic pattern. He pulled the throttle to idle, began to flare the airplane, and the airplane touched down on the main wheels first. It became airborne again, touched down on the runway, and "bounced" a third time. Then, during the landing roll, the pilot was instructed by the air traffic controller to taxi to the ramp area. As the pilot attempted to maneuver the airplane, he realized that the nose landing gear was "rough" to handle. He notified air traffic control that he was having trouble with the landing gear, and the airplane was towed off the runway. During the accident sequence, the airplane incurred substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind reported at the airport around the time of the accident was calm.
The pilot's inadequate landing flare, which resulted in a bounced landing and substantial damage to the firewall.
According to the pilot, he established a "crab angle to track" the centerline of the runway and maintained about 70 knots on the final leg of the traffic pattern. He pulled the throttle to idle, began to flare the airplane, and the airplane touched down on the main wheels first. It became airborne again, touched down on the runway, and "bounced" a third time. Then, during the landing roll, the pilot was instructed by the air traffic controller to taxi to the ramp area. As the pilot attempted to maneuver the airplane, he realized that the nose landing gear was "rough" to handle. He notified air traffic control that he was having trouble with the landing gear, and the airplane was towed off the runway. During the accident sequence, the airplane incurred substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind reported at the airport around the time of the accident was calm.