Friday, April 8, 2016

Bell 206-L4, N73AW, registered to Air Medical Services LLC and operated by Airwest Helicopters: Accident occurred June 01, 2015 in Dewey, Arizona -and- Accident occurred April 04, 2016 in Supai, Coconino County, Arizona

The National Transportation Safety Board did not travel to the scene of this accident.

Additional Participating Entities: 
Federal Aviation Administration / Flight Standards District Office; Scottsdale, Arizona
Bell Helicopter; Fort Worth, Texas
Rolls Royce Corporation; Indianapolis, Indiana
Airwest Helicopters; Glendale, Arizona 

Aviation Accident Factual Report - National Transportation Safety Board:  https://app.ntsb.gov/pdf

Investigation Docket - National Transportation Safety Board: https://dms.ntsb.gov/pubdms

Registered Owner: Air Medical Services LLC 
Operator:  Airwest Helicopters

http://registry.faa.gov/N73AW 

NTSB Identification: WPR15LA177 
14 CFR Part 91: General Aviation
Accident occurred Monday, June 01, 2015 in Dewey, AZ
Aircraft: BELL 206 L4, registration: N73AW
Injuries: 1 Uninjured.

NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

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.

Aviation Accident Final Report - National Transportation Safety Board: https://app.ntsb.gov/pdf

Investigation Docket - National Transportation Safety Board:   https://dms.ntsb.gov/pubdms


Aviation Accident Data Summary - National Transportation Safety Board:  https://app.ntsb.gov/pdf

NTSB Identification: GAA16CA179
14 CFR Part 133: Rotorcraft Ext. Load
Accident occurred Wednesday, April 06, 2016 in Supai, AZ
Probable Cause Approval Date: 06/01/2016
Aircraft: BELL 206, registration: N73AW
Injuries: 1 Minor.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The pilot reported that he was performing external load long line hauling operations with a helicopter and was on a return leg with two empty nets. During the approach to a hilltop helipad, the pilot reported that he performed a normal approach, rather than a long line approach. Subsequently, the 100 foot long line snagged on a ridgeline and the helicopter jerked in an uncontrollable turn to the right, touched down right skid first, and rolled over. The pilot reported that he forgot that the long line was still attached.

The tail boom was substantially damaged. 

The pilot did not report any mechanical malfunctions or failures with the helicopter that would have precluded normal operation. 

The operator submitted two operator/ owner safety recommendations to the National Transportation Safety Board investigator-in-charge. First, the operator revised the normal operation checklist. The revised checklist included a new "CARGO HOOK – CHECK" in both the BEFORE TAKEOFF and DESCENT AND LANDING checklist. Second, the chief pilot provided a copy of a memorandum to all employees that directs the use of an observer, when available, to observe the takeoff and landings and communicate any unsafe condition to the pilot via radio communication or hand signals.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's decision to fly a normal approach and forgetting that the long line remained attached to the helicopter, which resulted in the line snagging on a ridgeline, a loss of lateral control, and a rollover.

No comments: