FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA132 · Bell Helicopter Textron 206 L1

1 Feb 2017 · Carson City, NV, United States

Bell Helicopter Textron 206 L1 · Accident: dynamic rollover during landing

From Carson Airport (CXP) to Carson Airport (CXP)

Report a problem

Event

NTSB case
GAA17CA132
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bell Helicopter Textron 206 L1

Aircraft type
Bell 206
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N519EH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Carson Airport (CXP), Carson City, NVTo Carson Airport (CXP), Carson City, NV
Aircraft age
About 37 years (built 1980)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Dynamic rollover
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor on the controls of the high skid-equipped-landing-gear helicopter reported that he was the pilot-in-command (PIC). The PIC reported that he and another flight instructor were performing simulated emergency procedures during the flight. He reported that he attempted to demonstrate a simulated fixed-pitch (right stuck antitorque pedal) emergency procedure. He reported that, during the maneuver, the nose of the helicopter was about 40° nose right of centerline. He reduced the throttle, and the nose corrected to about 20° nose right of centerline. The helicopter touched down on taxiway delta with minimal forward airspeed, and it then bounced about 5 ft above the ground and yawed right about 1 3/4 turns. The helicopter touched down a second time about 65 ft south of the taxiway centerline and rolled onto its left side. The helicopter sustained substantial damage to the firewall, main rotor drive system, and tail rotor drive system.

A METAR at the time of the accident reported that the wind was from 110° at 08 kts. The flight instructor seated in the right seat reported that the wind at the time of the accident was from 090° at 08 kts.

When the PIC was asked by the National Transportation Safety Board investigator-in-charge if he placed the collective in the full-down position after touchdown or if he increased the collective after the initial touchdown, he responded that he could not remember. When asked if he applied full left pedal to combat the right yaw, he said that he did not because the event happened quickly.

According to the Federal Aviation Administration Helicopter Flying Handbook (FAA-8083-21A), the Helicopter Instructor's Flying Handbook (FAA-8083-4), and Advisory Circular (AC) 90-95 "Unanticipated Rapid Right Yaw in Helicopters," the loss of tail rotor effectiveness is a critical, low-speed aerodynamic flight characteristic that can result in an uncommanded rapid yaw rate that does not subside of its own accord and, if not corrected, can result in the loss of aircraft control.

AC 90-95, Section 7.d.3. (page 7), defines flight characteristics and wind azimuths and states that the tail rotor vortex ring state occurs when the wind is from 210° to 330°.

1. Winds within this region will result in the development of the vortex ring state of the tail rotor.

AC 90-95, Section 10, "Recommended Recovery Techniques," (page 8), states:

a. If a sudden unanticipated right yaw occurs, the pilot should perform the following:

(1) Apply full left pedal. Simultaneously, move cyclic forward to increase speed. If altitude permits, reduce power.

(2) As recovery is effected, adjust controls for normal forward flight.

b. Collective pitch reduction will aid in arresting the yaw rate but may cause an increase in the rate of descent. Any large, rapid increase in collective to prevent ground or obstacle contact may further increase the yaw rate and decrease rotor rpm.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

Probable cause

The pilot-in-command’s delayed remedial action to arrest the right yaw after the bounced landing while operating in a flight regime conducive to the loss of tail rotor effectiveness, which resulted in a roll-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA132
Event ID
20170207X62252
Case number
GAA17CA132
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-02-02.
  • API snapshot SHA-256: 6bbc1b7a06ac0435ae9ac17a1c91f8c18ea9c929492192b4fb6e672dc754f523; retrieved 2026-09-16T05:00:01.097Z.