3 Nov 2015: BELL 407 — Air Evac EMS, Inc.

3 Nov 2015: BELL 407 (N496AE) — Air Evac EMS, Inc.

No fatalities • San Antonio, TX, United States

Probable cause

The failure of the No. 3 tail rotor adapter and shaft due to a loss of torque on the retaining nut. Contributing to the accident was the lack of a requirement to inspect the tail rotor assembly for security in the helicopter manufacturer's maintenance manual and the operator's approved aircraft inspection program.

— NTSB Determination

Accident narrative

On November 2, 2015, at 1923 central standard time, the pilot of a Bell 407, N496AE, made a forced landing at San Antonio International Airport (KSAT), San Antonio, Texas. The pilot, flight nurse, and paramedic were not injured. The helicopter was substantially damaged. The helicopter was registered to and operated by AirEvac EMS, Inc., (EVCA), O'Fallon, Missouri, under the provisions of 14 Code of Federal Regulations Part 135 as an on-demand air medical flight. Night visual meteorological conditions prevailed at the time of the accident, and no flight plan had been filed. The flight was originating from KSAT, and was destined for Northeast Methodist Hospital (XS83), San Antonio.

When the pilot lifted helicopter to a 3-foot hover, he heard a loud bang and the helicopter began an uncommanded right yaw. The pilot applied full left pedal, but this did not arrest the yaw. The pilot then lowered the collective and the helicopter touched down, rotating 270 degrees to the right before coming to a stop. Post-accident examination revealed substantial damage to the tail rotor spline, coupling, and hanger bearings.

Postaccident examination revealed the tail rotor could be manually rotated, but a grinding noise could be heard coming from the damaged no. 3 hanger bearing. The main rotor blades did not rotate in synchronization with the tail rotor blades. The #3 tail rotor shaft adapter and shaft splines were completely ground down, and the adapter and the tail rotor shaft connecting point had failed. There was evidence of excessive torsion, beyond its intended allowable tolerances. There was excessive grease on the hanger bearing. The aluminum adapter washer hole was elongated, consistent with of a loose through-bolt. There was a 1/8th inch gap between the adapter and the base of the hanger bearing, consistent with the adapter not being fully in contact with the bearing and potential stress within the adapter and shaft splines. The smaller, stainless steel washer was mushroom-shaped. The drive shaft through-bolt had worn threads.

On November 18 and 19, 2105, the tail rotor assembly was examined at the facilities of Able Engineering, Mesa, Arizona, under the auspices of an FAA aviation safety inspector from the Scottsdale, Arizona, FSDO. Bell Helicopters and AirEvac EMS also participated in the examination. The shaft, freewheeling unit and tail gear box were examined. No issues were noted except for the failed coupling and shaft. The retaining stud had migrated almost .025" outward and was very loose compared to the others, consistent with the loss of torque that would have allowed movement between the coupling and shaft and eventual failure.

After the examination, Air Evac EMS ordered an inspection of their entire Bell 407 fleet. Two helicopters were found to have loose tail rotor drive shafts. The drive shaft, carrier bearing, coupling, and spline from one of those helicopters were examined the next day. The retaining nut was loose. Torque was measured at 20 inch-pounds. Minimum torque is 30 to 50 inch-pounds. Tare was 5 to 0 inch-pounds. Stud extension was within millimeter limits. There was a slight motion between the coupling face and the face of the bearing. This motion had worn the coupling face and there was slight wear on some of the splines. In the Bell 407 Maintenance Manual and Air Evac EMS' AAIP, there is no requirement for the assembly to be inspected for security.

Contributing factors

  • cause Fatigue/wear/corrosion
  • cause Tail rotor drive shaft — Failure
  • factor Manufacturer
  • factor Operator

Conditions

Weather
VMC, wind 130/05kt, 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.