Crash location | 42.483333°N, 114.483333°W |
Nearest city | Twin Falls, ID
42.562967°N, 114.460871°W 5.6 miles away |
Tail number | N63VP |
---|---|
Accident date | 20 May 2012 |
Aircraft type | Enstrom F28 |
Additional details: | None |
On May 20, 2012, about 0900 mountain daylight time, an Enstrom F-28F helicopter, N63VP, sustained substantial damage following a reported control malfunction and precautionary landing near the Twin Falls Airport (TWF), Twin Falls, Idaho. The private pilot, who was the sole occupant and registered owner of the helicopter, was not injured. Visual meteorological conditions prevailed for the cross-country flight, which was being conducted in accordance with 14 Code of Federal Regulations Part 91, and a flight plan was not filed. The flight departed Elko, Nevada about 0615 Pacific daylight time, with TWF being its intended destination.
In a report submitted to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported that on a flight a few days prior to the accident flight he noticed that the helicopter wanted to roll left without enough trim to neutralize the roll. The pilot stated that his prior experience indicated that this condition was indicative of a possible failure of the main rotor Lamiflex bearing, which generally preceded the failure by about 15 hours. The pilot added that during the preflight prior to the accident flight, he pulled the plastic covers on the [main] rotor bearing[s] to inspect their condition. He reported that bearing 1 showed no indication of a pending bearing failure, bearing 2 showed some indication that it was approaching failure, and that bearing 3 showed just minor indications that it was beginning to fail. The pilot concluded that based on his previous experience the trip could be safely flown. The pilot further reported that as he was approaching his destination, about 10 to 15 miles [south] of TWF and immediately after contacting the TWF air traffic control tower, a slight vibration started, which became progressively worse and at a rapid rate. He then notified the tower controller that he was experiencing a rotor bearing failure and thought that he could make the airport. The pilot stated that the situation then worsened to the point where he was unable to maintain control of the helicopter, and with only partial control he was unsure if he could safely get it on the ground. Now experiencing low-rotor rpm, the pilot lowered collective to recover rotor speed and subsequently made what he described as a “controlled crash landing.” The helicopter impacted the ground hard and in a nose low attitude, which resulted in the aircraft coming to an abrupt stop in an upright position and tilted slightly to its left. The tail boom and tail rotor assembly had both separated and were located about 30 to 40 feet to the right of the helicopter.
A Federal Aviation Administration (FAA) aviation safety inspector examined the helicopter on site and reported that the #2 main rotor Lamiflex bearing had failed, which resulted in the uncontrollable condition of the helicopter and the subsequent forced landing. The inspector further reported that not only was the helicopter not in compliance with its annual inspection requirement, but that it was also not in compliance with FAA Airworthiness Directive (AD) 94-17-15, which required initial and repetitive inspections for delamination of the main rotor feathering elastomeric Lamiflex bearing. The actions in the AD were intended to prevent failure of the Lamiflex bearing, abnormal vibrations in the airframe and flight control system, and subsequent loss of control of the helicopter.
The pilot's inability to maintain helicopter control during cruise flight due to the failure of the No. 2 main rotor Lamiflex bearing. Contributing to the accident was the pilot's decision to operate the helicopter with a known deficiency and the helicopter’s noncompliance with the mandatory scheduled inspection of the main rotor bearings.