29 Jul 2020: AMERICAN EUROCOPTER AS350 B3

29 Jul 2020: AMERICAN EUROCOPTER AS350 B3 (N755AE) — Unknown operator

2 fatalities • Pioche, NV, United States

Probable cause

The pilot’s failure to maintain altitude from terrain and subsequent loss of helicopter control due to entanglement of the external load cable with the tail rotor.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn July 29, 2020, about 1000 Pacific daylight time, an American Eurocopter Corp. AS350B3 helicopter, N755AE, was destroyed when it was involved in an accident near Pioche, Nevada. The pilot and passenger were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 positioning flight. The pilot landed the helicopter in mountainous terrain in order to survey a job site. The purpose of the accident flight was to reposition the helicopter to the nearby fuel truck to refuel before beginning external load operations. A witness reported that he dropped the pilot and passenger at the helicopter before the accident flight and saw a cable that was laid out on the ground in front of the helicopter. The pilot stated to him that the cable was 70 feet long. The witness left the pilot and passenger at the helicopter and drove away; shortly thereafter, he received a phone call about smoke in the vicinity and learned that the helicopter had crashed. The helicopter came to rest in heavily treed terrain on its right side. There was no evidence of a postimpact fire. The helicopter was equipped with a long line cargo hook system. About 21 ft of steel long line cable impacted the main rotor blades and was found entangled in the separated tail rotor. (see Figure 1.) The separated cable end exhibited a broomstrawed appearance and evidence of red paint transfer.

Figure 1. Photo of tail rotor wrapped with cable One tail rotor blade remained attached to the tail rotor; the other blade was not located. The tail boom was broken off and partially attached at the lower aft bulkhead by control cables. The tail rotor drive shaft was separated and found near the main wreckage. Both horizontal stabilizers remained attached to the tail boom. The main rotor blades remained attached to the rotor head but were broken midspan and exhibited multiple impact signatures. Main rotor blade skin material was found near the main wreckage. Flight control continuity was established from the cockpit to the main rotor head and tail rotor system through separations consistent with impact damage. The aft tail cone was separated just forward of the vertical fin; the vertical fin remained attached. The assembly was found about 365 ft from the main wreckage. The tail cone and vertical fin trailing edge exhibited abrasions consistent with cable contact. (see Figure 2.)

Figure 2. Tail cone and vertical fin displaying cable abrasions The engine remained attached to the helicopter by the front and rear supports and displayed little impact damage. All fuel, oil, air, and electrical connections remained intact. The gas generator and free turbine turned freely when rotated by hand. The axial compressor displayed minor foreign object debris (FOD) damage. Oil was present inside the exhaust pipe. Proper freewheel operation was confirmed. The rear tail rotor drive short shaft separated from the drive flange on the freewheel shaft. The flector group connecting the two was torsionally splayed. The Module 5 reduction gearbox displayed signatures consistent with engine operation at the time of main rotor impact. The reduction gearbox and accessory gearbox chip detectors were found clean. The engine data recorder was removed from the helicopter and downloaded at the manufacturer. Data from the accident flight indicated that the engine was placed in flight, then reduced to idle near the end of the recording. During this sequence, the main rotor speed decayed below that necessary to maintain lift. The data displayed no anomalies that would have precluded normal flight.

Contributing factors

  • Altitude — Not attained/maintained
  • Pilot
  • Related operating info

Conditions

Weather
VMC, 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, 40,000+ 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.