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.
Dublin, TX
The pilot reported that, during landing, the gyroplane was too high above the runway. He attempted to "cushion the landing" by forcing the nose up as he "gunned the engine a couple of times." The fluctuations in torque caused the gyroplane to turn right, and he corrected with hard, left rudder application. Because the gyroplane was configured with the front wheel mechanically linked to the rudder for directional control, the front wheel was turned completely left, which resulted in the gyroplane turning "violently" left upon touching down hard and then rolling onto its right side. The gyroplane sustained substantial damage to the main rotor drive system and the empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation and that the accident was caused by pilot error.
The pilot's improper landing flare and failure to maintain lateral control, which resulted in a hard landing, loss of directional control, and subsequent roll-over.
The gyroplane pilot reported that during landing, the gyroplane was too high above the runway. He attempted to, "cushion the landing" by forcing the nose up as he, "gunned the engine a couple of times." The fluctuations in torque turned the nose of the gyroplane to the right, and he corrected with a hard-left rudder application. He recalled that the additional thrust from the engine gunning, increased the gyroplanes airspeed. The gyroplane was configured with the front wheel being mechanically linked to the rudder for directional control. When the gyroplane touched down, the pilot's hard left rudder application was also a hard-left turn input. The gyrocopter landed hard and rolled on to its side. The pilot reported that this accident was caused by pilot error. The nearest METAR was 12 NM to the northeast and reported that about the time of the accident the wind was from 170° at 4 knots. The pilot landed on runway 33 and would have produced a left quartering tailwind during the landing. The gyroplane sustained substantial damage to the main rotor drive system and the empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation.