13 May 2011: MD HELICOPTER 369D — Airlift Helicopters of Alaska, Inc.

13 May 2011: MD HELICOPTER 369D (N124AL) — Airlift Helicopters of Alaska, Inc.

No fatalities • Columbia, CA, United States

Probable cause

The loss of power transmission to the main rotor for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation of the helicopter.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On May 13, 2011, at 0917 Pacific daylight time, an MD Helicopter (MDHI) 369D, N124AL, made an off airport forced landing near Columbia, California. Airlift Helicopters of Alaska, Inc., was operating the helicopter under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The airline transport pilot and one passenger were not injured; the helicopter sustained substantial damage to the tail rotor section. The cross-country ferry flight departed Fresno, California, at an undetermined time with a planned destination of Reno, Nevada. Visual meteorological conditions prevailed, and no flight plan had been filed.

The pilot stated that the helicopter was in cruise flight at 12,500 feet mean sea level (msl) over mountainous terrain. The engine remained running, but power stopped being transmitted to the main rotor system. He performed an autorotation to an open area. During the landing, the tail rotor sustained damage to both blades as they went through about 1 foot of snow. He reported that after landing, the engine was still running, but not spinning the main rotor blades.

Post Accident Examination

Investigators from the airframe and engine manufacturers (MDHI and Rolls-Royce, respectively) examined the helicopter under the supervision of a Federal Aviation Administration (FAA) inspector at the operator’s facility in Reno on May 26, 2011. Their complete reports are part of the public docket. Pertinent excerpts follow. No anomalies were identified with the airframe or engine that would have precluded normal operation.

Airframe

Lateral, longitudinal cyclic and collective main rotor control linkage continuity was established throughout the full range of movement from the cockpit controls to the upper flight controls and to the rotor hub. The anti-torque flight control pedal brackets fractured on both sides at a bracket on the rudder pedal support frame. From that point, there was linkage continuity to a bellcrank where the bellcrank end and control rod end bearing had broken off. Manipulation of the bellcrank caused the applicable changes to the tail rotor blade pitch settings.

No anomalies were identified with the fuel system.

Battery power was supplied to the cockpit and instrument panel. All appropriate warning lights illuminated, and on test all segments functioned. There were no chip lights illuminated. The engine reignition system, N2 rpm control (beep switch) to the power governor, and the lateral and longitudinal trim actuators were functional.

The main transmission rotated freely by hand. Drive to the tail rotor output pinion and driveshaft was present. Transmission oil was observed in the sight gauge, and both chip detectors were clean. The over-running clutch was functional. Both forward and aft KAFLEX drive shaft couplings were intact, and exhibited no visible damage.

Engine

The engine was an Allison Model 250-C20B gas turbine engine, serial number CAE 831345. Initial inspection revealed that the compressor rotated freely, and was continuous to the starter generator gearshaft. The N2 power turbine rotor turned freely by hand, and was continuous to the power turbine output. No engine anomalies were noted.

The engine was shipped for follow-up examination to the Rolls-Royce facility in Indianapolis, Indiana. The examination took place on July 18, 2011, under the supervision of an FAA inspector from the Indianapolis Flight Standards District Office.

The engine was placed into a test stand; it was run through an as-received test run schedule, and met all tested parameters. It started, accelerated to ground idle normally, and then advanced to takeoff power successfully. The compressor bleed valve closed within specifications, and the acceleration from flight autorotation to takeoff test was performed successfully. The anti-ice system, governor droop test, and engine vibrations were within specifications. Five selected performance calibrations were completed, and the calculated performance was 506 shaft horsepower (SHP) versus the 420 per the model specifications.

Conditions

Weather
VMC, wind 360/06kt, 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.