29 Dec 2012: BELL 407 — MED TRANS CORP

29 Dec 2012: BELL 407 (N534MT) — MED TRANS CORP

No fatalities • Big Lake, TX, United States

Probable cause

The loss of engine power due to the fatigue failure of the outer combustion case at the fuel nozzle port. Contributing to the accident was the operator’s failure to conduct the recommended routine inspections of the outer combustion case.

— NTSB Determination

Accident narrative

On December 29, 2012, at 1148 central standard time, a Bell 407 helicopter, N534MT, was substantially damaged during a hard landing at Reagan County Airport (E41), Big Lake, Texas. The pilot, flight nurse, flight paramedic, and patient were not injured. The helicopter was registered to and operated by Med-Trans Air Medical Transport under the provisions of 14 Code of Federal Regulations Part 135 as a non-scheduled domestic passenger flight. Visual meteorological conditions prevailed for the flight, which operated on a company visual flight rules flight plan. The flight originated from Fort Stockton, Texas, at 1114, and was en route to the Shannon Medical Center Heliport (03TS), San Angelo, Texas.According to the written statement provided by the pilot, the helicopter was in cruise flight, at an altitude of 1,500 feet mean sea level, when helicopter suddenly yawed 10 degrees to the right. The pilot was able to control the yaw and subsequently heard an audio alarm. He observed a RPM warning light and a 2 to 3 percent decrease in RPM for the engine and rotor. As the pilot began to scan his flight controls and instruments, the "check instrument segment" illuminated, and the measured gas temperature gauge began to flash and display a reading of "E 920."

The pilot stated that all other engine indications were in normal ranges; however, the entire crew agreed that they should land. The pilot slowed the helicopter to about 80 knots, prepared for a running landing, and continued to cross-check his instruments and prepare for an autorotation if necessary. As the helicopter crossed the threshold to the runway, he smelled "a burning grease or oil product" but did not observe smoke or fire. The flight nurse reported an increase in temperature at her crew station.

At 10 to 15 feet above ground level and 20 knots, the engine "quit." The pilot responded by moving the throttle to idle and increasing the collective pitch. The helicopter "fell vertically" and hit the ground hard. During the impact the skids spread out horizontally and the main rotor blades flexed down and severed the tail boom.

During the post-accident examination of the engine, three fractures in the outer combustion case, around the fuel nozzle port, were observed. Two of the three fractures originated at the intersection of the circumferential weld that joined the reinforcing ring to the main skin. The third fracture ran adjacent to the reinforcing ring to the main skin interface. All three fractures exhibited signatures consistent with high cycle fatigue. The welds and material on the outer combustion case were to engineering specifications.

Further examination of the two fractures, which originated from the reinforcing ring to the main skin, exhibited darker heat tinting consistent with this area being open during engine operation. The darker tinting was not observed in the third fracture. In addition, investigators documented contact between the aft firewall on the engine bay and the fuel spray nozzle.

Investigators established that the operator was not conducting the post-flight and scheduled maintenance inspections of the outer combustion case as recommended by Rolls Royce in M250-C47B Operations and Maintenance Manual.

The examination of the remaining engine sections revealed no anomalies. An examination of the airframe revealed evidence of contact between the aft firewall of the engine bay and the engine's fuel spray nozzle. The examination of the remaining airframe and related systems revealed no anomalies.

Contributing factors

  • cause Combustion section — Failure
  • factor Not serviced/maintained

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.