21 Jul 2020: MCDONNELL DOUGLAS 600 N

21 Jul 2020: MCDONNELL DOUGLAS 600 N (N208MP) — Unknown operator

No fatalities • Thompson Falls, MT, United States

Probable cause

A partial loss of engine power for reasons that could not be determined based on available evidence.

— NTSB Determination

Accident narrative

On July 21, 2020, at 0558 Pacific daylight time, a McDonnell Douglas 600N helicopter, N208MP, was substantially damaged when it was involved in an accident near Thompson Falls, Montana. The pilot was not injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 rotorcraft external load operation. The pilot stated that, as he was on an approach to the landing zone, he lowered the collective to start a vertical descent to land. At that time, the engine and rotor speeds suddenly decreased, the helicopter yawed to the left and started to settle. As the helicopter was approaching the ground fast, the pilot increased the collective to use the remaining engine power to cushion the landing. The helicopter impacted the ground, and the pilot rolled the throttle to idle, but noticed that engine speed and rotor rpm gauges were below the normal idle parameters. When he rolled the throttle to off, he heard a grinding "metal-to-metal" noise, and the rotor blades stopped spinning almost immediately. A postaccident examination revealed the N1 system turned smoothly and was continuous from the compressor to the starter/generator and first-stage turbine wheel. The N2 system turned smoothly and was connected to the aircraft power train. Foreign object damage (FOD) was not observed on the compressor impeller blades or compressor inlet and the inlet barrier filter system was intact and free of debris. The fourth-stage turbine wheel was normal in appearance when viewed from the exhaust collector. The first-stage turbine nozzle and blades were viewed via borescope with no abnormalities observed. The engine mounted fuel filter bowl retained about 1/3 bowl of fuel, which was normal in smell and appearance. The fuel filter element presented no obvious contamination. All the fuel lines from the airframe to the engine were flow-checked with no obstructions noted. The engine electronic control unit (ECU), which retains data in nonvolatile memory, was downloaded during the wreckage examination. The ECU includes an incident recorder function, which begins capturing engine and input parameters upon trigger actuation and records a line of data (“record”) every 1.2 seconds. The initial incident recorder triggering event was “low rotor RPM” (Nr Droop), which fell below the 92% threshold. Then, within 3 seconds, the incident recorder captured the “Flameout” and “Ng Low” triggers. According to the data, the FADEC system attempted to re-light the engine for the next 53 seconds until the throttle was rolled to cut-off; however, the engine did not restart. The engine was transported to an inspection facility and installed on a calibrated test stand. After the engine was warmed up for about 5 minutes, the power was gradually increased to the takeoff setting, where the observed power was 680 shaft horsepower (shp). No unusual vibration was noted. Several accelerations and decelerations were achieved followed by testing of the anti-ice system and bleed valve, all of which were within specification. A full power calibration protocol was achieved resulting in a maximum predicted take-off rating of 664 shp at standard day conditions, with no anomalies noted. The fuel nozzle was removed and inspected. The inlet screen was normal in appearance and not obstructed. The fuel hose was installed in a test bench and 600 pounds per hour of fuel was flowed through the hose to check for leaks. No leaks were observed.

Contributing factors

  • Aircraft power plant

Conditions

Weather
VMC, wind 280/03kt, 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.