5 Jul 2011: HUGHES 500D — Soloy Helicopters LLC

5 Jul 2011: HUGHES 500D (N315SH) — Soloy Helicopters LLC

No fatalities • McGrath, AK, United States

Probable cause

A fatigue fracture of the governor-to-fuel control Pc line, which resulted in a partial loss of engine power.

— NTSB Determination

Accident narrative

On July 4, 2011, about 1915 Alaska daylight time, a Hughes 500D (369D) helicopter, N315SH, sustained minor damage following a partial loss of engine power and subsequent emergency landing, about 3 miles southwest of McGrath, Alaska. The helicopter was operated as a visual flight rules (VFR) on-demand charter flight under the provisions of 14 CFR Part 135. The helicopter was operated by Soloy Helicopters LLC., Wasilla, Alaska. The airline transport pilot and two passengers were not injured. Visual meteorological conditions prevailed, and VFR company flight following procedures were in effect. The main rotor blades were damaged during the emergency landing.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), on July 4, the operator's president/director of operations reported that the helicopter was being used for a crew change at a remote mine site, about 15 miles southwest of McGrath. He said that as the pilot began a gradual descent to the McGrath Airport, the engine sound changed abruptly, which was immediately followed by the engine out audio horn, and a red engine out annunciator light. The pilot entered an emergency autorotation, turned the helicopter left, and selected a mostly open area that contained some trees as an emergency landing site. During the descent, the helicopter's main rotor blades struck several small trees as it touched down on the uneven, tundra-covered terrain.

The helicopter was equipped with a Rolls-Royce 250-C20 series engine.

A postincident inspection of the helicopter's engine revealed a fractured Pc (pneumatic) line on the engine governor. According to the engine manufacturer, the Pc line provides compressed air (bleed air) from the compressor to the fuel control and governor units, and if it becomes disconnected or breached, the engine will roll back to an idle, or near idle condition.

During a follow-up telephone conversation with the NTSB IIC on March 28, 2012, the operator's president/director of operations reported that he had recently leased the incident helicopter, and a new Pc line was installed by the owner. He said that the new Pc line was installed on April 28, 2011, and it had accumulated 233.7 hours before the incident. He noted that the Pc line had not been removed by his maintenance personnel.

During the manufacturing process, the Pc line is bent and manipulated to specific drawing specifications, allowing the rigid Pc line to be connected to the threaded compression T fitting on the engine governor and a threaded compression fitting on the engine fuel control.

The fractured Pc line was sent to the NTSB's Materials Laboratory for examination. A senior Safety Board metallurgist reported that the separated Pc line displayed evidence of fatigue cracking that emanated from the flared portion of the line. In use, a B-nut and sleeve seals the flared portion of the line to the threaded T fitting on the engine governor. The fracture surface was found within the sleeve, and adjacent to the flared radius of the Pc line.

The Safety Board metallurgist noted that the Pc line met the metallurgical material specifications, but his examination revealed a bend in a normally straight portion of the line, which would have placed stress on the Pc line when installed. It could not be determined when or how the bend occurred. A copy of the Safety Board metallurgist's report is included in the public docket for this incident.

Contributing factors

  • Contributed to outcome
  • cause Fatigue/wear/corrosion

Conditions

Weather
VMC, wind 050/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.