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.
Hillsboro, OR
As the pilot was approaching the destination airport after a local flight, the helicopter's engine rpm began to fluctuate between 100 percent and 60 percent. Although lowering the collective and manipulating the throttle temporarily increased the rpm, it began to fluctuate again, with the rpm decreasing. After the low rotor rpm warning horn and light activated, the pilot made the decision to perform an autorotation to a nearby open field. The helicopter touched down on the skids and subsequently rolled over onto its side. Prior to the accident, the helicopter's engine had been reportedly experiencing rpm fluctuations. A postaccident examination was performed on the engine and the magnetos and governor underwent further analysis. No evidence was found of an anomaly or malfunction that would have prevented the engine from producing normal power.
Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
On June 18, 2010, about 2045 Pacific daylight time, a Robinson R-22 Beta helicopter, N2548S, impacted the terrain during an autorotational landing about one-half mile south of Portland-Hillsboro Airport, Hillsboro, Oregon. The private pilot and his passenger were not injured, but the helicopter, which was owned and operated by Hillsboro Aviation, sustained substantial damage to its rotor system and its fuselage. The local 14 Code of Federal Regulations Part 91 personal pleasure flight, which departed Portland-Hillsboro Airport about 38 minutes prior to the accident, was being operated in visual meteorological conditions. No flight plan had been filed. According to the pilot, who was executing a visual flight rules (VFR) approach to the airport, when he was about one mile from the helicopter landing pad, the helicopter's engine rpm suddenly began fluctuating between 60 and 100 percent. He therefore lowered the collective and rolled on the throttle, which initially seemed to help. But soon thereafter the condition resumed, with the rpm fluctuating to even lower levels, resulting in the activation of the rotor low rpm warning horn and light. Seeing that he was not going to be able to make it to the landing pad, the pilot elected to do an autorotational landing to a nearby open field. Although the helicopter initially touched down on the skids, it subsequently rolled over onto its side, and the rotating main rotor blades impacted the terrain. According to the pilot, earlier on the same day the helicopter was written up for fluctuating engine rpm, but Hillsboro Aviation maintenance personnel were unable to determine the cause of the fluctuation or to duplicate the reported problem. A post-accident inspection of the engine and the rotor control system was directed and monitored by the Federal Aviation Administration (FAA). As part of that process the magnetos and the engine rpm governor were sent out for further inspection and analysis. The inspection and testing process did not find any evidence of an anomaly or malfunction that would have kept the engine and rotor from producing and maintaining 100 percent rpm.