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.
Concord, CA
During an emergency response to a roadside accident site, the helicopter experienced an in-flight collision with a tree that resulted in a main rotor strike. The Director of Flight Operations reported that the pilot had chosen a landing spot that had a tree on the southwest (SW) side of the road and a tree on the northeast (NE) side of the road. As the pilot came to a hover over the landing site, he was looking left and forward up the road to confirm that the area was secure. As he was looking toward the left front, he heard a discernable noise change from the rotor system, although there was no change in aircraft handling or any abnormal instrument indications. He looked to the right and observed that he was closer to the NE tree than he wanted to be. He then observed a broken branch on the NE tree. After a normal shut down, a visual inspection showed damage to the outer three to five inches of the trailing edge of the three main rotor blades.
The pilot's failure to maintain clearance from an object during hover. Trees were a factor.
During an emergency response to a roadside accident site, the helicopter experienced an in-flight collision with a tree that resulted in a main rotor strike. The Director of Flight Operations reported that the pilot had chosen a landing spot that had a tree on the southwest (SW) side of the road and a tree on the northeast (NE) side of the road. As the pilot came to a hover over the landing site, he was looking left and forward up the road to confirm that the area was secure. As he was looking toward the left front, he heard a discernable noise change from the rotor system, although there was no change in aircraft handling or any abnormal instrument indications. He looked to the right and observed that he was closer to the NE tree than he wanted to be. He then observed a broken branch on the NE tree. After a normal shut down, a visual inspection showed damage to the outer three to five inches of the trailing edge of the three main rotor blades.