2 Jun 2015: BELL 206 L4 L4 — AIRWEST HELICOPTERS

2 Jun 2015: BELL 206 L4 L4 (N73AW) — AIRWEST HELICOPTERS

No fatalities • Dewey, AZ, United States

Probable cause

A total loss of engine power due to the failure of the No. 2 bearing, which resulted from a fractured separator.

— NTSB Determination

Accident narrative

On June 1, 2015, about 1948 mountain standard time, a Bell 206 L-4, N73AW, sustained substantial damage during an emergency landing following a loss of engine power, near Dewey, Arizona. The commercial pilot, the sole occupant of the helicopter, was not injured. The helicopter was registered to Air Medical Services LLC and operated by Airwest Helicopters as a Title 14 Code of Federal Regulations Part 91 ferry flight. Visual meteorological conditions prevailed and a company visual flight rules, company flight plan, was filed. The cross country flight, departed Valle Airport (40G), Grand Canyon, Arizona about 1905 with a planned destination of Glendale Municipal Airport (GEU), Glendale, Arizona.

The operator reported that several weeks prior to the accident, the helicopter's engine chip detector caution light momentary illuminated during a routine maintenance engine run. The engine was shut down and the magnetic chip detectors (MCDs) were examined. A small amount of debris, that was determined to be within the manufacturer's limits, was observed. The MCDs were cleaned and re-installed and then a 30-minute engine run was conducted. Afterward, no further debris was found and the helicopter was returned to service. During a subsequent flight, a couple of weeks later, the engine chip detector caution light momentary illuminated. The helicopter landed and the MCDs were once again inspected, and a small flake and metallic paste on the lower MCD was observed. The oil system was drained, flushed, changed, and a new filter was installed. A 30-minute ground engine run was accomplished, and the MCDs were inspected afterwards and free of debris. The helicopter was then flown about 30 minutes, to a location where an oil sample could be drawn from the original oil removed. The oil sample was sent out for analysis and the helicopter was not operated for about 2 weeks, while awaiting results. The oil analysis was received, and the operator was satisfied with the result of no metal detected, and attempted to ferry the helicopter back to its home base.

During the flight, the pilot reported observing a momentary illumination of a caution light that he could not identify, prior to it extinguishing. About 10 minutes later, the engine chip detector caution light briefly illuminated, while the helicopter was in cruise flight, about 750 ft above ground level. The pilot elected to make a precautionary landing and initiated a descent. During the descent, the engine chip detector light illuminated again and shortly thereafter, was followed by a loud bang. Immediately, the engine lost power and an emergency autorotation landing was accomplished. During the landing sequence, the main rotor blades struck the tail boom and resulted in substantial damage.

Postaccident examination of the helicopter, revealed control continuity with the cockpit controls to the engine and flight controls. Besides the tail boom damage, the remainder of the fuselage was relatively intact. Initial visual examination of the engine revealed no obvious damage. The inlet, exhaust section, and turbine blades, were clear of obstructions and observed to be undamaged. The engine was removed to facilitate an examination. The compressor could not be rotated by hand but the power turbine could be rotated by hand, with resistance. The magnetic chip detectors were removed and observed to have accumulated ferrous debris. The engine was shipped to Rolls-Royce for further examination.

The engine was examined and disassembled under the supervision of the National Transportation Safety Board, investigator-in-charge, at the Rolls-Royce facility near Indianapolis, Indiana. The compressor module was separated from the accessory gearbox by removing the compressor discharge tubes and the Compressor Turbine Drive Shaft (CT shaft). Thermal damage and cooked oil was observed on the CT shaft. The turbine module was removed for examination. On the first and second stages of the turbine, thermal and blade tip damage was observed. All the bearings were examined and were unremarkable, except for the No. 2 bearing.

The aft end of the compressor module revealed damage to the No. 2 bearing. The No. 2 bearing was fractured and exhibited thermal damage. Examination of the No. 2 bearing oil delivery tube revealed it was properly installed with no obvious blockage of the oil jets. The tube was removed and x-rayed for internal contamination of the oil passages with negative results. Further, the tube was flow checked and verified to flow oil at the specified rate.

The accessory gearbox was disassembled and observed to be intact and functional. Metal debris was observed throughout the gearbox. The oil pump screen, oil delivery tubes and engine mounted oil filter had minor contamination but no obstructions to flow.

A detailed examination of the No. 2 bearing revealed that its composition was consistent with the manufacture material types required. The bearing separator was fractured completely through both rails, at the forward and aft sides, of the bearing. All 10 of the ball bearings were retained in the separator, however half of them exhibited damage consistent with smearing and material transfer between the raceway and balls.

The No. 2 bearing is the primary means of support of the compressor impellor. Failure of the No. 2 bearing will allow the impellor to migrate forward, where it will eventually contact the compressor shroud. According to the manufacturer, only minor contact between the impeller and shroud is acceptable, however, examination of the compressor impellor revealed that the shroud and its vanes had considerable rubbing damage.

Contributing factors

  • cause Turbine section — Failure

Conditions

Weather
VMC, wind 210/06kt, 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.