NTSB CAROL · Event
Event WPR16LA075
Registry · N266RH
FAA Aircraft Registry record.
Make / Model
ROBINSON HELICOPTER R66
Year of manufacture
2009 · 7 years old at event
TCDS
R00015LA · ROBINSON HELICOPTER CO
Engine
ROLLS-ROYC 250-C300/A1 (300 hp)
Seats / Engines
5 seats · 1 engine
Last airworthiness date
20260105
ADS-B equipped
Yes — Mode-S A296C6
Registrant of record
ROBINSON HELICOPTER CO
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A vibration of the helicopter, which resulted in an autorotation to soft terrain and subsequent impact of the tail boom with the main rotor. The reason for the vibration could not be determined because postaccident examination revealed no malfunctions or anomalies that would have precluded normal operation.
Factual narrative
HISTORY OF FLIGHTOn February 23, 2016, about 1145 Pacific standard time, a Robinson R66, N266RH, sustained substantial damage to the tailboom following a precautionary autorotation at Zamperini Field Airport (TOA), Torrance, California. The pilot, the sole occupant, was not injured. The experimental (research and development category) test helicopter was registered to and operated by Robinson Helicopter Company (RHC) as a test flight under the provision of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the local flight that originated from TOA at 1145. The purpose of the flight was to test the auxiliary fuel system, low RPM horn, autopilot, and sprag clutch. The pilot reported that he had performed a takeoff to a hover, a hover taxi, and one hovering autorotation without incident. He then executed a maximum performance takeoff. About 200 feet above ground level, the pilot heard a noise and felt a momentary helicopter vibration. Subsequently, he performed an autorotation to a grassy area on the airfield. After the helicopter landed in soft grass with forward momentum, it experienced a fore and aft rocking motion, and the main rotor blades contacted the tailboom. AIRCRAFT INFORMATIONThe five-seat helicopter, serial number 0002, was manufactured in 2009. The operator reported that the helicopter's maximum gross weight was 2,700 pounds, and it weighed 2,047 at the time of the accident. The helicopter was powered by a 300-horsepower Rolls Royce 250-C300/A1 engine. The last annual maintenance inspection was conducted on October 15, 2015, at the total engine time of 363 hours. The airframe had a total of 400.04 hours at the time of the accident, as it had operated 20 hours since its last maintenance inspection. The engine was examined on March 4, 2016, at RHC, Torrance, California. AIRPORT INFORMATIONThe five-seat helicopter, serial number 0002, was manufactured in 2009. The operator reported that the helicopter's maximum gross weight was 2,700 pounds, and it weighed 2,047 at the time of the accident. The helicopter was powered by a 300-horsepower Rolls Royce 250-C300/A1 engine. The last annual maintenance inspection was conducted on October 15, 2015, at the total engine time of 363 hours. The airframe had a total of 400.04 hours at the time of the accident, as it had operated 20 hours since its last maintenance inspection. The engine was examined on March 4, 2016, at RHC, Torrance, California. TESTS AND RESEARCHA visual examination of the airframe components was conducted and no anomalies were found. There were no metal particles found in the oil filter and the chip detector. The Engine Monitoring Unit (EMU) data was downloaded and reviewed by a representative from Rolls-Royce. The EMU provided general information about the operation of the engine including time, cycles, faults and any exceedances of engine operating limits. The downloaded data corresponded to the entire accident flight. There were no exceedances noted in the data; however, at the time stamp 32.27.1 the power turbine (N2) peaked at 107.76% and the Torquemeter Oil Pressure (TMOP) peaked at 95.304% (275 ft/lbs). According to the Rolls Royce 300 Operational and Maintenance Manual, the limit for N2 is 110% for 15 seconds, and the torque limit during takeoff is 288 ft/lbs with a maximum transient of 430 ft/lbs. With no pre-accident anomalies noted with the engine, the engine was test run on the helicopter through various power settings. No anomalies were noted during the engine exam. The engine data was downloaded after the engine runs, and no faults were noted in the data. Following the engine run, the sprag clutch was inspected and it was revealed that the sprag clutch had moved between 45-90 degrees from its original position. The sprag clutch was then removed, and it was observed that it took about 550 pounds of torque to loosen the clutch assembly compared to the 300 pounds of torque used to tighten the clutch in the assembly process. The clutch was then inspected, and no anomalies were found. A review of the maintenance logbook revealed that the new Revision E sprag clutch had been installed on the helicopter before the accident flight. The Revision E sprag clutch was compared to the previously installed Revision D sprag clutch, and the wear patterns appeared normal and consistent with those observed in the Revision E clutch assembly. The complete engine report is appended to this accident in the public docket. The Pilot's Operating Handbook states that a vibration can be an indication of a drive system failure. However, a drive system failure is also accompanied by nose right or left yaw, and a decrease of the rotor RPM while N2 RPM increases. RHC Safety Notice SN-39, issued in July 2003, stated that an unusual vibration can indicate a main rotor blade crack. However, those vibrations are characterized as severe and the helicopter would be difficult to control. The commercial pilot was performing company flight testing in the helicopter. After performing an air taxi and a hovering autorotation, the pilot conducted a simulated maximum performance takeoff. About 200 ft above ground level, the pilot heard a noise and felt a momentary helicopter vibration. He subsequently performed a precautionary autorotation to a grass area on airport property. The pilot stated that the helicopter had forward speed during the landing and that the grass was soft; as a result, the helicopter entered a fore-aft rocking motion after touchdown, and the main rotor contacted the tail boom, resulting in substantial damage. Postaccident review of data from the engine monitoring unit revealed no anomalies, and an examination of the helicopter revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation; therefore, the reason for the noise and vibration could not be determined. 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).
- F Not determined-Not determined-(general)-(general)-Unknown/Not determined - F
- — Environmental issues-Physical environment-Terrain-Wet/muddy terrain-Not specified
Verbatim from NTSB's published report. Source file
NTSB_2016_WPR16LA075.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, maintenance, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
Browse the full corpus — academia portal ↗