7 Aug 2012: BELL 214ST — BELL HELICOPTER TEXTRON INC

7 Aug 2012: BELL 214ST (N409SB) — BELL HELICOPTER TEXTRON INC

No fatalities • Avalon, TX, United States

Probable cause

Maintenance personnel’s failure to properly torque the retaining nut and install the cotter pin that secured the helicopter’s tail rotor counterweight bellcrank. Contributing to the accident was the lack of detailed maintenance records that documented previous maintenance actions.

— NTSB Determination

Accident narrative

On August 7, 2012, about 0845 central daylight time, a Bell 214ST helicopter, N409SB, experienced a loss of tail rotor authority near Avalon, Texas. The commercial and airline transport pilots were not injured during the precautionary landing, and the helicopter was substantially damaged. The helicopter was owned and operated by Bell Helicopter, Textron, Inc. Fort Worth, Texas, under the provisions of 14 Code of Federal Regulations Part 91 as a research and development flight. Day visual meteorological conditions prevailed for the local flight which operated without a flight plan. The local flight originated from the Arlington Municipal Airport (KGKY), Arlington, Texas at 0815.

According to the pilots the purpose of the flight was to collect data on the helicopter's rotor system. During the flight test, the helicopter completed a right turn and as they were setting up for another test condition, the pilot's heard a "bang," and felt the helicopter yaw. The pilot of the chase aircraft reported that something had departed the tail of the helicopter. The accident pilots then initiated an autorotation to a nearby field; however, helicopter yawed, rolled right, and came to rest on its side.

The helicopter, the tail rotor gear box, and tail rotor blades were recovered and transported back to a Bell facility. Representatives from the NTSB, Federal Aviation Administration (FAA), and Bell Helicopter, then examined the helicopter and components at the manufacturer's facility.

The tail rotor's 90-degree gear box was broken in two; one of the mast's two counterweight bellcranks and associated hardware were missing (and not located/recovered from the accident site); the remaining counterweight bellcrank remained attached. Examination of the remaining counterweight bellcrank, revealed that the assembly was in place, but "loose". The dustcap/grease cover for the remaining counterweight bellcrank was removed, exposing the castellated nut. The examination found that the nut's cotterpin was missing.

Both tail rotor blades' attachments remained in place; both blades had separated outboard of their respective attachments. On the side with the missing counterweight bellcrank, impact marks consistent with the size and shape of a counterweight bellcrank, were found on the edge and base of its associated tail rotor blade, as well as on the right side of the helicopter. The rotor blade was torn in two, with the separation starting near the impact marks at the base of the blade.

Since the accident helicopter was used to collect data on a new rotor system, the tail rotor blades and components had been removed to install test instrumentation. A review of the helicopters' maintenance workbook revealed the temporary re-installation of the instrumented tail rotor section. However, the maintenance entry was not specific as to whether the reinstallation of the instrumented tail rotor assembly was conducted as an assembly or as individual components. The mechanics installing the instrumented tail rotor treated the unit as a complete sub-assembly and not as individual components. The difference meant that the individual components were not assembled or inspected, prior to or after installation onto the helicopter.

The helicopter was on its third flight after the reinstallation of the instrumented tail rotor system and had accumulated about 2.8 flight hours, before the accident.

Contributing factors

  • cause Tail rotor drive shaft — Failure
  • cause Maintenance personnel
  • factor Operator

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, 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.