23 Jun 2011: HILLER UH12E — Central Valley Aviation Inc.

23 Jun 2011: HILLER UH12E (N99579) — Central Valley Aviation Inc.

No fatalities • Hanford, CA, United States

Probable cause

The separation of the tail rotor drive gear shaft due to torsional fatigue of its threaded portion, which resulted in a loss of tail rotor control.

— NTSB Determination

Accident narrative

On June 23, 2011, about 0400 Pacific daylight time, a Hiller UH-12E, N99579, sustained substantial damage during a hard landing following a loss of tail rotor control near Hanford, California. The helicopter was registered to and operated by Central Valley Aviation Inc., Selma, California, under the provisions of 14 Code of Federal Regulations Part 91. The commercial pilot, sole occupant of the helicopter, was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the positioning flight that was originating at the time of the accident.

During a telephone conversation, the pilot reported that upon completing a night time aerial application on a nearby field, he landed the helicopter on a platform that was mounted on a truck to refuel the helicopter and refill the chemical hopper. Following refueling operations, the pilot conducted a quick pre-flight inspection to look over the helicopter. Upon inspection of the transmission, the pilot observed a small oil leak originating where the tail rotor drive shaft attaches to the transmission. The pilot said that following a discussion with his boss, they decided to reposition the helicopter from the platform onto the ground so they could perform a more detailed examination of the oil leak. The pilot stated that following a normal engine start, he began to lift the helicopter off the platform and heard a "growling" sound originating from the transmission, followed by an immediate loss of tail rotor control. The pilot said that the helicopter immediately began to rotate to the right as he rolled the throttle off and lowered the collective. Subsequently, the helicopter landed hard onto the ground adjacent to the truck.

Postaccident examination of the helicopter by a Federal Aviation Administration (FAA) inspector and a representative from Hiller Aircraft revealed that the tail boom exhibited structural damage. One of the two tail rotor blades was separated at the blade root. The tail rotor gear shaft was found separated from the tail rotor drive shaft coupling. The gear shaft was found separated into two pieces at the threaded portion of the shaft. The gear shaft and tail rotor drive shaft coupling were removed from the wreckage and sent to the NTSB Materials Laboratory, Washington, D.C. for further examination.

An NTSB senior metallurgist reported that the external gears on the gear shaft and mating internal gears on the coupler showed no evidence of deformation damage. The gear shaft was fractured at the threaded portion. A nut and cotter pin remained attached to the fractured portion of the threaded area of the gear shaft. Bench binocular microscope examination of the thread fragment revealed the fracture face contained a twist fracture pattern consistent with torsion separation. A light brown region was found on one side of the fracture that extended between the root portion of the thread and an area located approximately 0.08 inch below the thread. The areas outside of the dark brown region exhibited a metallic luster. The fracture also showed ratchet marks typical of fatigue cracking that emanated from multiple origins at the root portion of the thread. The ratchet marks extended all around the thread. Scanning electron microscope examination of the thread fragment revealed the fracture face in the areas within the ratchet marks showed striation-like features and the twist fracture pattern at the center of the fracture showed striation-like features consistent with torsional-fatigue. For further details of the metallurgical examination, see the Materials Laboratory Factual Report within the public docket.

The pilot reported that the last annual inspection was conducted on the helicopter on June 14, 2011, at a total airframe time of 10,485-hours. No maintenance records for the helicopter were recovered during the course of the investigation. The amount of flight time on the tail rotor gear shaft was undetermined. A representative from Hiller Aircraft reported that the tail rotor gear shaft is subject to a 1,200 hour overhaul which includes magnetic particle inspection of the part.

Contributing factors

  • cause Fatigue/wear/corrosion
  • cause Attain/maintain not possible

Conditions

Weather
VMC, wind 330/08kt, 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.