4 Dec 2016: BELL OH 58A NO SERIES — CITY OF SACRAMENTO

4 Dec 2016: BELL OH 58A NO SERIES (N916PD) — CITY OF SACRAMENTO

No fatalities • Sacramento, CA, United States

Probable cause

The failure of the vertical stabilizer due to fatigue.

— NTSB Determination

Accident narrative

On December 4, 2016, about 2100 Pacific standard time, a Bell OH-58A helicopter, N916PD, sustained substantial damage to the vertical stabilizer during a flight near, Sacramento, California. The pilot and observer were not injured. The helicopter was operated as a public flight. The pilot and observer reported noticing the vertical stabilizer damage after the completion of a routine patrol flight, during the post-flight inspection. The vertical stabilizer was bent downwards away from the tail rotor. The pilot further reported that the flight was flown at a cruise altitude of 600-700 ft above ground level, and no turbulence or any other unusual flying conditions were encountered. The helicopter's damaged vertical stabilizer was removed and shipped to the National Transportation Safety Board (NTSB) Materials Laboratory for examination. The data plate of the vertical stabilizer showed part number (P/N) 206-022-113-3. The examination revealed that the inboard side of the vertical stabilizer, inboard skin, was fractured above the attachment holes. The upper portion of the fin remained partially attached by the outboard skin. A drilled hole was located about 1 ¼ inch from the edge of the inboard skin. The skin fracture aft of the drilled hole intersected the lower side of the hole at a tangent and the fracture forward of the hole extended radially outward from the hole. Examination of the lower surface using a scanning electron microscope revealed striations consistent with fatigue. The fatigue features in the skin emanated from a primary origin located at the trailing edge of the skin. A secondary origin was located at the forward side of the drill hole and the fatigue features extended to about 2 ½ inches of the inboard skin. Cracks in the inboard, near the attachment holes of the vertical stabilizers installed on OH-58 Helicopters were a known issue to the U.S. Army. According to U.S. Army Aviation and Missile Command Technical Manual TM 55-1520-228-PMD, the daily inspection checklist included an inspection of the inboard of the vertical stabilized for cracks originating from the four attachment inserts. The inspection was implemented in 2003 via Aviation Safety Action Message (ASAM) OH—58-03-ASAM-6, after a service failure of the vertical stabilizer. The ASAM applied to fin assembly P/N 206-022-113-1 and P/N 5790032-501. Additionally, the ASAM applied to fin assembly P/N 206-022-113-3. Alert Service Bulletin (ASB) 206-26 published in December 18, 1972, addressed the cracks in the inboard skin near the attachment bolts of vertical stabilizers installed on Bell Helicopter model 206 and TH-57A helicopters. The ASB applied to vertical fin P/Ns 206-020-113-5, -7 and -9. According, to a Bell representative, the vertical stabilizer part numbers mentioned in the alert were very similar to the vertical stabilizer installed on the OH-58 helicopter, but the part numbers were different due to minor differences. The ASB 206-26, required visual inspections of the inboard skin for cracks in the attachment area immediately upon receipt and subsequently at 25-hour intervals. ASB 206-26 was superseded by ASB 206-01-731, dated January 9, 1973, which affected the same helicopter but required the first inspection within 25 hours after receipt and the subsequent inspections at 25-hour intervals. Accomplishment of Service Letter (SL) 206-203, terminated the requirement for the repetitive inspections for crack in the inboard skin of vertical stabilizer, required by the ASB. In SL 206-203, dated December 18, 1972, vertical stabilizers were modified or repaired by installing a doubler on the interior skin in the area of the attachment holes. Cracks in the vertical stabilizer longer than 3 ½ inches were considered unrepairable and unairworthy. Since the helicopter was acquired from the United States military as surplus, the operator would inherit the type certificate holder responsibilities. Therefore, the operator would be responsible for the engineering, continued airworthiness, and other associated safety information pertaining to the helicopter. The operator was unaware that the maintenance vendor that provided support to the helicopter, was not aware of a past U. S. Army ASAM, and therefore, was not accomplishing daily inspections of the vertical fin attachment area for cracks.

Contributing factors

  • cause Fatigue/wear/corrosion

Conditions

Weather
VMC, vis 5sm

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.