CEN18LA314

NTSB accident investigation · Airbus EC 130 T2 · Mullen, NE · August 3, 2018

Accident · Serious injuriesLimited investigationFinal report
Date
August 3, 2018, 15:30 local (21:30 UTC)
Place
Mullen, NE
Injuries
1 serious, 1 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N130TGAirbus EC 130 T2
Defining event
Maneuvering: Loss of tail rotor effectiveness
Weather
Visual (VMC) · Day
Status
Completed · report November 19, 2019
Report
Approved by Office Director
NTSB office
Central Region
Parties
Federal Aviation Administration, Safran Helicopter, Airbus Helicopters, BEA
FAA report
20180803009829A
Case key
97995

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 pilot’s inadequate and incorrect antitorque pedal application during a tight, decelerating turn downwind, which resulted in a loss of yaw control.

Findings · 2

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.

Performance/control parameters: prop/rotor parametersAircraft › Aircraft oper/perf/capability · Not attained/maintainedAirbus Helicopters EC 130 T2: 1 caseAll aircraft: 182 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

The private pilot reported that he was approaching a golf course to survey a potential landing area when, during a left turn, the helicopter experienced a loss of tail rotor effectiveness. He stated that he added right pedal and eventually full right pedal to counter the rotation without success. The helicopter impacted the ground, which resulted in substantial damage to the main rotor and fuselage. Parametric data recovered from an onboard recorder showed that the left turn tightened in radius and that both the groundspeed and airspeed decreased during the turn. The left yaw rate increased rapidly as the helicopter entered the downwind portion of the turn. The cockpit image recorder captured the pilot applying a slight right pedal input during the onset of the left yaw, followed by his improper left pedal input that remained until ground impact. There was no evidence of mechanical malfunctions or failures with the helicopter that would have precluded normal operation. The left yaw would likely have been arrested had the pilot applied adequate and correct antitorque pedal when the yaw first started.

Factual narrative

On August 3, 2018, about 1530 mountain daylight time, an Airbus EC 130 T2 helicopter, N130TG, lost control while maneuvering near the Dismal River Golf Club, southwest of Mullen, Nebraska. The private pilot was not injured, and the passenger sustained serious injuries. The helicopter sustained substantial damage. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no Federal Aviation Administration (FAA) flight plan had been filed for the flight. The personal flight departed Alliance, Nebraska, about 1430, and was en route to Mullen, Nebraska. According to the pilot, he was approaching the golf course with the intention of surveying a possible landing site. The pilot reported the weather was clear and breezy with 15 to 20 knots of wind from the southeast. The pilot stated that during the left turn, with an airspeed between 40 and 60 knots, he encountered a loss of tail rotor effectiveness. The pilot stated that he initially added right pedal during the first ½ of the turn and increased it to full right pedal for the remainder of the rotation. The pilot stated that he accepted responsibility for putting the helicopter into that flight situation and in the future, he needed to perform higher, faster, and wider turns. According the FAA inspector who responded to the accident, the main rotor and fuselage were substantially damaged during the impact. An examination of the helicopter and its systems revealed no mechanical anomalies that would have precluded normal operations. The helicopter was equipped with an Appareo Vision 1000 image, audio, and data recorder. The recorder was not damaged and was sent to the National Transportation Safety Board Vehicle Recorders Division in Washington, DC, for examination and data recovery. Parametric data from the accident flight was extracted and is available in the public docket for this accident. The details surrounding the data recovered are contained in the specialist's factual report in the public docket for this investigation. The Appareo Vision 1000 provided a field of view over the pilot's shoulder and forward to the instrument panel, including a partial view outside the helicopter windshield. The flight controls, except for the collective control, were also visible. Only the video events associated with the accident flight were viewed. The helicopter entered a right turn around a group of buildings. A flagpole visible in the video indicated that the winds were out of the south; the flag was mostly unfurled, and the flag was fully visible. After one right turn, the helicopter started a left turn around the same group of buildings. As the turn begins to tighten in radius the helicopter starts to descend. The ground speed showed a decreasing trend with an indicated airspeed of 30 knots. The heading changed to north, the ground speed decreased, and the airspeed indicator displayed 0 knots. As the helicopterturned to a downwind condition, a left yaw rate rapidly increased and was not arrested, resulting in a loss of yaw control. At the moment of control loss, the nose was down 18° at which time the pilot made an aft stick input and slight right pedal input, about 1 inch forward of the left pedal. As the yaw continued to develop, the pilot made a left pedal input; this input remained until ground impact. The helicopter rotated 1.25 times from the time of loss of control until ground impact. According to the FAA Rotorcraft Flying Handbook – Unanticipated yaw is the occurrence of an uncommanded yaw rate that does not subside of its own accord and, which, if not corrected, can result in the loss of helicopter control. In February 2005, Eurocopter released Service Letter No. 1673-67-04 "Reminder concerning the YAW axis control for all helicopters in some flight conditions" and specifically addressed the operational differences between the Fenestron and the conventional tail rotor. In July 2019, Airbus Helicopters released Safety Information Notice No. 3297-S-00 "Unanticipated left yaw (main rotor rotating clockwise), commonly referred to as LTE" and specifically addressed the characteristics of the unanticipated yaw, and how pilots can respond to avoid or reduce the effect of the unanticipated yaw.

Aircraft

Registration
N130TG
Reported as
Airbus EC 130 T2
Category
Helicopter
Serial number
8320
Built
2016
Engine
TurboMeca Arriel 2D, turbo jet
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Departed
KAIA · Aliance, NE
Destination
Mullen, NE
Equipment
Stall warning system, Video recording device, ADS-B, Auto-pilot, Electronic multifunction display, Onboard weather

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

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
61
Injuries
None
Certificate
Private
Medical
Class 3, With waivers/limitations
Seat
Left
Restraint
4-point
Flight hours
212.5 total · 193.8 in this make and model · 80.1 as pilot in command · 112.9 in the last 90 days · 44.5 in the last 30 days · 6 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
180° at 9 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
88 °F, dew point 64 °F
Altimeter
26.89 inHg

Docket · 5

The files NTSB released with the investigation on August 19, 2019, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.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.