ERA10LA023

NTSB accident investigation · Mcdonnell Douglas Helicopter 369E · Winnsboro, SC · October 19, 2009

Accident · No injuriesLimited investigationFinal report
Date
October 19, 2009, 14:30 local (18:30 UTC)
Place
Winnsboro, SC
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N502SLMcdonnell Douglas Helicopter 369E
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed · report May 28, 2010
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO, Rolls-Royce
FAA report
20091019025969A
Case key
74931

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Engine controls: power leverAircraft › Aircraft power plant · Incorrect use/operationMcdonnell Douglas Helicopter 369E: 1 caseAll aircraft: 95 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

During an instructional flight while in a three-foot hover, the certified flight instructor (CFI) applied right anti-torque pedal input with the intention of simulating loss of tail rotor thrust while in a hover. The student correctly reduced throttle and both occupants agree that the helicopter contacted the ground. While neither occupant agrees as to who applied throttle control, throttle control input was applied and the helicopter became airborne with slow main rotor rpm. The CFI took the controls and attempted to cushion the landing, but the helicopter landed hard. There were no reported preimpact failures or malfunctions. After the accident the engine was placed in a test cell and operated to full power with no evidence of failure or malfunction.

Factual 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 somemovement. 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.

Aircraft

Registration
N502SL
Reported as
Mcdonnell Douglas Helicopter 369E
Category
Helicopter
Serial number
0244E
Airframe hours
4,961
Engine
Allison 250-C20B, 420 hp, turbo shaft
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Sc Law Enforcement Division
Registered owner
Sc Law Enforcement Division
Airworthiness certificate
Standard, Normal
Last inspection
Annual · September 10, 2009
Departed
2SC6 · Columbia, SC
Destination
FDW · Winnsboro, SC
Airport
FDW · Fairfield County Airport

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Flight instructor
Age
35
Injuries
None
Certificates
Commercial, Private
Airplane ratings
Single-engine land
Instrument ratings
Helicopter
Medical
Class 2, Without waivers/limitations
Seat
Right
Flight hours
2,150 total · 600 in this make and model · 2,050 as pilot in command · 80 in the last 90 days · 30 in the last 30 days
Role
Student pilot
Age
47
Injuries
None
Certificate
Commercial
Medical
Class 2, Without waivers/limitations
Last flight review
February 25, 2009
Seat
Left
Flight hours
1,766 total · 362 in this make and model · 859 as pilot in command · 53 in the last 90 days · 22 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
320° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
61 °F, dew point 30 °F
Altimeter
30.28 inHg
Observed at
FDW

Docket · 7

The files NTSB released with the investigation on March 9, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 26.8 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.