- Date
- February 23, 2016, 11:45 local (19:45 UTC)
- Place
- Torrance, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N266RHRobinson Helicopter R66
- Defining event
- Maneuvering: Miscellaneous/other
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 20, 2017
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Robinson Helicopter, FAA FSDO
- FAA report
- 20160223007729A
- Case key
- 92758
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
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.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Factual narrative
The 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. On 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. A 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 theengine 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.
Aircraft
- Registration
- N266RH
- Reported as
- Robinson Helicopter R66 (NO SERIES)
- Category
- Helicopter
- Serial number
- 0002
- Built
- 2009
- Airframe hours
- 400.04
- Engine
- Rolls-Royce 250-C300/A1, 300 horsepower, turbo shaft
- Damage
- Substantial damage
- Flight
- Flight test · Part 91
- Operator
- Robinson Helicopter Co
- Registered owner
- Robinson Helicopter Co
- Airworthiness certificate
- Special, Experimental (Special)
- Last inspection
- Annual · October 15, 2015
- Departed
- TOA · Torrance, CA
- Destination
- TOA · Torrance, CA
- Airport
- TOA · Zamperini Field
- Equipment
- Auto-pilot, Electronic primary flight display
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 45
- Injuries
- None
- Certificates
- Flight instructor, Commercial
- Airplane ratings
- Single-engine sea
- Instrument ratings
- Airplane, Helicopter
- Medical
- Class 2, With waivers/limitations
- Last flight review
- April 23, 2014
- Seat
- Right
- Flight hours
- 1,750 total · 200 in this make and model · 1,650 as pilot in command · 30 in the last 90 days · 15 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 84 °F, dew point 36 °F
- Altimeter
- 30.01 inHg
- Observed at
- KTOA
Docket · 12
The files NTSB released with the investigation on April 10, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.2 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.