Skip to content

Atlas / NTSB / WPR10LA298

NTSB CAROL · Event

Event WPR10LA298

2010-06-18 Hillsboro, Oregon, United States Airport · KHIO None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

A partial loss of engine power while on approach for undetermined reasons.

Factual narrative

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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Aircraft-Aircraft power plant-Power plant-(general)-Malfunction - C
  • C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C

Verbatim from NTSB's published report. Source file NTSB_2010_WPR10LA298.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗