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.
Decker, IN
According to the certified flight instructor, during the training flight he retarded engine power while the airplane was on the downwind leg of the traffic pattern, in order to simulate an engine failure. During the flare for the simulated forced landing, the main rotor blade of the gyroplane struck the ground, and it rolled over on its left side. The pilot reported there were no mechanical failures or malfunctions of the gyroplane.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C
The flight instructor reported that during the training flight, he retarded engine power during the downwind leg of the traffic pattern in order to simulate an engine failure. During the flare for the simulated forced landing the main rotor blade of the gyroplane struck the ground directly behind the aircraft which resulted in the gyroplane rolling over on its left side. The pilot reported no mechanical failures or malfunctions of the gyroplane prior to the accident. The aircraft received substantial damage which included a bent keel, a bent/broken rotor mast, a damaged main rotor blade, empennage damage, a cracked cabin, and a broken propeller.