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.
Daytona Beach, FL
The pilot of the helicopter reported that while flying at an indicated altitude around 200 to 300 ft, while on approach to land at an off-airport landing zone, he saw a black “drone” [unmanned aerial system (UAS)] in front of his windscreen. He attempted to avoid the UAS but was unable and the UAS impacted the main rotor resulting in substantial damage to a main rotor blade. The pilot reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation. The UAS operator reported that he was conducting operations over a construction site. The area was inside of the class C airspace of a nearby airport and the UAS operator was using a Federal Aviation Administration Certificate of waiver or authorization (COA) that had been previously obtained by the construction company who hired him. The UAS operator reported that he was flying at an altitude of 180 ft, and that before the flight he had not realized that this altitude was above the maximum altitude of 150 ft imposed by the COA. The COA also required the UAS operator to notify the air traffic control tower at the nearby airport at least 15 minutes prior to the proposed start time of any operations. The UAS operator stated, and a review of contact records by the air traffic control tower confirmed, that no call was received from the UAS operator notifying them of the operation. Additionally, the drone operations manager for the construction company who contracted the UAS operator reported that the operator was supposed to check in with the on-site supervisor before conducting operations and stated that this did not happen on the day of the accident.
The UAS operator’s failure to operate within the limitations of the COA that he was using to operate inside class C airspace, which resulted in a collision between the UAS and the helicopter.
The pilot of the helicopter reported that while flying at an indicated altitude around 200 to 300 ft, while on approach to land at an off-airport landing zone, he saw a black “drone” [unmanned aerial system (UAS)] in front of his windscreen. He attempted to avoid the UAS but was unable and the UAS impacted the main rotor resulting in substantial damage to a main rotor blade. The pilot reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation. The UAS operator reported that he was conducting operations over a construction site. The area was inside of the class C airspace of a nearby airport and the UAS operator was using a Federal Aviation Administration Certificate of wavier or authorization (COA) that had been previously obtained by the construction company who hired him. The UAS operator reported that he was flying at an altitude of 180 ft, and that before the flight he had not realized that this altitude was above the maximum altitude of 150 ft imposed by the COA. The COA also required the UAS operator to notify the air traffic control tower at the nearby airport at least 15 minutes prior to the proposed start time of any operations. The UAS operator stated, and a review of contact records by the air traffic control tower confirmed, that no call was received from the UAS operator notifying them of the operation. Additionally, the drone operations manager for the construction company who contracted the UAS operator reported that the operator was supposed to check in with the on-site supervisor before conducting operations and stated that this did not happen on the day of the accident.