19 Oct 2009: MCDONNELL DOUGLAS HELICOPTER 369E — SC LAW ENFORCEMENT DIVISION

19 Oct 2009: MCDONNELL DOUGLAS HELICOPTER 369E (N502SL) — SC LAW ENFORCEMENT DIVISION

No fatalities • Winnsboro, SC, United States

Probable cause

The flight instructor's failure to monitor the simulated emergency procedure, resulting in a hard landing. Contributing to the accident was the intentional throttle application by one of the flightcrew.

— NTSB Determination

Accident narrative

On October 19, 2009, about 1430 eastern daylight time, a McDonnell-Douglas 369E helicopter, N502SL, registered to South Carolina Law Enforcement Division (SLED), was landed hard at the Fairfield County Airport (FDW), Winnsboro, South Carolina. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 instructional flight. The helicopter was substantially damaged and the certified flight instructor (CFI) and rotorcraft- rated student (student) were not injured. The flight originated from the SLED Heliport (2SC6), Columbia, South Carolina, about 1400.

The student stated that after departure the flight proceeded to FDW where he executed two normal approaches. After the second, he hover taxied to a grassy area south of runway 04/22, where he and the CFI noted the wind direction and discussed the next maneuver to be performed which was loss of tail rotor thrust while in a hover. The briefing before the maneuver included the proper recovery procedure which was to slowly reduce throttle control. While in a three foot hover the CFI announced that he was initiating the loss of tail rotor thrust and the helicopter began slowly yawing to the right. The student initiated recovery by reducing throttle and while in a two foot hover the CFI instructed him to regain the entry altitude of three feet. The student increased collective control which reduced rotor rpm and induced another right yaw. He then reduced throttle which caused the rotor rpm to deteriorate further resulting in the helicopter descending. He increased collective control to remain airborne while the helicopter slowly yawed to the right. The CFI instructed him not to let the helicopter contact the ground and he continued to apply up collective while the helicopter continued yawing to the right. As he was applying up collective he felt the CFI grasp the cyclic and collective controls and heard the rotor rpm and engine noise increase. He later stated that while it is not clear to him which of them applied power, he was fairly certain that he did not. The helicopter began a rapid right yaw possible landing briefly then becoming airborne while yawing 360 degrees and climbing to an estimated height of 10 to 20 feet above ground level. The CFI attempted to hover then announced he was rolling the throttle to idle. The helicopter then began a rapid descent, landed hard, and rolled towards the left side. He and the CFI initiated the emergency shutdown procedures and exited the helicopter.

The CFI stated that he briefed the student on the emergency procedure to be performed (loss of tail rotor thrust) and also the proper response which would be to slowly reduce throttle and cushion the landing with collective control. The CFI initiated the maneuver by applying right anti-torque pedal input and the student responded by decreasing throttle. As the rotation stopped the helicopter settled and made contact with the ground with some movement. The student was uncomfortable with the touchdown and applied throttle control. Though his (CFI’s) hands were on the flight controls he was not guarding the throttle closely enough to arrest the quick application of throttle. The helicopter became airborne and began yawing very quickly to the right which was not corrected by left anti-torque pedal input. He closed the throttle which stopped the right yaw but at that point the helicopter was 7 to 10 feet and rotor rpm was insufficient to maintain flight. He applied collective and forward cyclic to cushion the landing but the helicopter landed hard causing the left skid gear to collapse.

The National Transportation Safety Board (NTSB) Pilot/Operator Aircraft Accident/Incident Report submitted by the operator indicated there was no mechanical failure or malfunction.

Following the accident the engine was removed from the helicopter, sent to the manufacturer’s facility to be functionally tested. With Federal Aviation Administration oversight the engine was ran and found to operate normally.

The emergency procedures for loss of tail rotor thrust while in a hover, specified in the flight manual, indicate to place the twistgrip in the ground idle position and to perform a hovering autorotation.

Contributing factors

  • factor Incorrect use/operation
  • cause Instructor/check pilot
  • factor Flight crew

Conditions

Weather
VMC, wind 320/04kt, 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.