20 Jul 2018: Bell 206 B

20 Jul 2018: Bell 206 B (N325CT) — Unknown operator

No fatalities • Todd Mission, TX, United States

Probable cause

The passenger’s inadvertent interference with the tail rotor pedals, which resulted in a loss of helicopter control during takeoff and the subsequent impact with terrain.

— NTSB Determination

Accident narrative

On July 20, 2018, about 1215 central daylight time, a Bell 206B, N325CT, sustained substantial damage when it was involved in an accident near Todd Mission, Texas. The private pilot and one passenger sustained minor injuries and two passengers sustained no injury. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

After flying in the local area and refueling, the pilot landed on a grass field to facilitate the passengers switching their seat positions in the helicopter. During the seat-switching process, the pilot reduced the throttle to the flight idle position. After the passengers switched seats and secured their restraint systems, with one passenger stationed in the front left seat, and two passengers stationed in the cabin, the pilot increased the throttle to 100 percent and lifted the helicopter off from the field.

A review of accident sequence video footage shows that the helicopter began to rotate right during the takeoff. The pilot reported that about 10 ft above ground level with about 5 kts of forward airspeed and a heading of about 270°, the helicopter spun four 360° revolutions to the right. The pilot reported she applied full left pedal with no response from the helicopter. During the loss of control sequence, the pilot observed the torque gauge "jump" and she heard a "whining" noise emit from the engine. Prior to the impact with terrain, the pilot reduced the throttle to the flight idle position. The left skid impacted the ground, the helicopter rolled to the left, and came to rest on the left side of the fuselage. The pilot executed an emergency shutdown and the occupants egressed from the helicopter without further incident.

The helicopter sustained substantial damage to the main rotor system, the fuselage, the tailboom, and the tail rotor system. A postaccident examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.

The helicopter had the cyclic, collective, and the two tail rotor pedals installed in the left side of the helicopter. The pilot reported that she briefed all of the passengers about not touching any of the flight controls. The passenger in the front left seat was asked if he had his feet on top of the tail rotor pedals as a footrest. He stated "that or on the floor," and then stated that he was not sure. The passenger further reported that the pilot did give a passenger safety briefing about not touching any of the flight controls.

Postaccident testing was conducted in a Bell 206B flight training device. Wind conditions were replicated for the accident site. The National Transportation Safety Board (NTSB) investigator-in-charge (IIC) rested his feet on top of the tail rotor pedals for two flight iterations with no force applied and with medium force applied. When the Bell chief training pilot (CTP) attempted to takeoff for both iterations, the helicopter started to immediately rotate to the right. The CTP had a hard time maintaining directional control due to the interference of the feet on the tail rotor pedals.

The NTSB IIC also placed the tips of his feet on the floorboards up against the tail rotor pedals. When the CTP attempted to takeoff for the third iteration, the helicopter started to immediately rotate to the right. The CTP had a hard time maintaining directional control due to the interference of the feet up against the tail rotor pedals.

A review of the Bell 206B rotorcraft flight manual found no guidance regarding the carrying of passengers in the cockpit and the interference of flight controls.

The Federal Aviation Administration Helicopter Flying Handbook (FAA-H-8083-21B) discusses operations when carrying passengers in the cockpit and states, "If possible, remove front passenger flight controls and ensure all passenger personal items, such as cameras and mobile phones are secure."

Contributing factors

  • cause Unintentional use/operation
  • cause Passenger
  • cause Attain/maintain not possible

Conditions

Weather
VMC, wind 220/05kt, 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.