ERA18LA020

NTSB accident investigation · Bell 206 · Union City, TN · November 8, 2017

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
November 8, 2017, 11:40 local (17:40 UTC)
Place
Union City, TN · Church Yard
Injuries
3 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N275AEBell 206
Defining event
Landing: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Eastern Region Aviation
Parties
AIR EVAC EMS Inc., FAA / FSDO
FAA report
20171108018909A
Case key
96306

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 inadvertent slope landing and attempted recovery, which resulted in an incipient dynamic rollover, mast bumping, and separation of the main rotor.

Findings · 4

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.

Terrain: sloped/uneven terrainEnvironmental issues › Physical environment · Awareness of conditionBell 206L-3: 2 casesAll aircraft: 270 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotBell 206L-3: 8 casesAll aircraft: 9,295 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 pilot, flight nurse, and flight paramedic were conducting a flight for a public relations event. None of the three crewmembers had previously landed at this landing zone (LZ). A company flight nurse was on the ground at the LZ informing the flight crew of obstacles in the area. The pilot conducted a low reconnaissance and initiated a steep approach into the LZ. All obstacles were observed and called out by crewmembers as they continued the approach. The terrain appeared to the crew to be flat in all directions. The pilot began to set the helicopter on the ground from a stabilized hover. As the pilot lowered the collective to set the skids on the ground, the skid toes and the forward half of the skids made ground contact; however, from just aft of the pilot’s seat, the terrain sloped downward at a 10°-to-15° angle. Once the collective was lowered to the bottom stop, the helicopter rocked backwards to a tail-low attitude. The pilot and crew felt the tail stinger make ground contact and assumed that the tail rotor had impacted the ground. The pilot then applied upward collective and forward cyclic, which forced the front of the skid toes tightly against the terrain. The application of upward collective resulted in the helicopter entering an incipient dynamic rollover, aggressively rolling to a 45°-to-60° nose-low attitude. The pilot applied aft cyclic to counter the nose low attitude, and mast bumping occurred when the droop (static) stops came in to contact with the mast. The main rotor then separated from the mast and departed the helicopter. The circumstances of the accident are consistent with the pilot’s attempted recovery following a slope landing, which resulted in incipient dynamic rollover, mast bumping, and separation of the main rotor.

Factual narrative

On November 8, 2017, about 1140 central standard time, a Bell 206L-3 helicopter, N275AE, was substantially damaged when it was involved in an accident in Union City, Tennessee. The pilot, flight nurse, and flight paramedic sustained minor injuries. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 positioning flight. The helicopter, operated by Air Evac EMS Inc, departed for a public relations event at the Obion County Emergency Communications District 911 Center. The pilot was shown the requested landing zone (LZ), which was across the street from the center next to a church, and was instructed to land where other pilots had previously landed. A company employee located at the LZ had a portable radio programmed to the company channel. Upon his arrival at the LZ, he notified the crew of the helicopter that the LZ was secure and asked them to launch at 1124. About 1135, he heard the pilot transmit his flight plan. About 3 minutes later, the helicopter flew over the LZ. The company employee transmitted that he was directly underneath them and asked if they saw his red truck, located where the helicopter was supposed to land; however, he did not receive a response. He observed the helicopter flying a high and low reconnaissance utilizing left hand turns and watched the helicopter turn for final approach to the church parking lot, adjacent to where he was located. He advised the pilot over the radio that the helicopter was clear of wires and again received no response. The helicopter descended onto a steep grassy slope, catching the front third of the skid on top of the slope. As more weight was placed on the skids, the tail boom rapidly descended toward the ground and the stinger embedded into soft mud close to an asphalt driveway. The company employee thought he observed the tail rotor strike the mud. At this point, the sound of the engine changed, and the tail boom rose into the air at what the company employee estimated to be 60°. There was an "explosively loud bang" and the airframe slammed violently back down onto the slope. At this point, the helicopter began to shake violently from left to right, and the main rotor separated from the mast. The pilot reported that he was unfamiliar with the LZ and had discussed the area with the company employee, who described to him where there were powerlines along the road bordering the LZ and showed him where other pilots had landed in the past. He also thought he understood him to say that the parking lot at the LZ could be used as well. As he approached the LZ, he made radio contact with the company employee, who advised that the LZ was clear. He performed a low reconnaissance and determined that the best approach would be to the northwest. On final approach, he called out trees to the flight paramedic and wires along the road to the flight nurse. When he was on short final, the flight paramedic called out clear of trees, and wires mid-skid. A brief time later, the flightnurse and flight paramedic both called clear of wires and clear to come down. Due to the steep approach he had performed to clear the trees and wires, the pilot decided to land in the parking lot. As he moved toward the lot, electrical wires running from poles on the lot came into view. He called out wires, stopped, and decided he could land on the grass just south of the lot. As the helicopter settled to the ground, he felt the skids touch down and began to lower the collective. The helicopter’s tail continued to fall, and he increased collective to stabilize it; but, the tail continued downward, and he felt the helicopter sliding backwards. He added more collective and felt two "thumps." Thinking that his tail rotor had contacted something, he added forward cyclic and began to reduce power. The tail of the helicopter rose rapidly. He then applied aft cyclic, and the tail came back down. The helicopter began shaking violently and rocking back and forth. He shut off the fuel, the helicopter came to a stop, and the occupants egressed. Examination of the accident site revealed that the helicopter touched down on level ground with the front portion of the skids; however, just aft of the pilot’s seat, the ground sloped down about 10° to 15°. Ground scars from the skids and lower wire strike assembly were present, which coincided with the position of the helicopter’s nose and touchdown point. A ground scar was also present, which coincided with the position of the tail stinger. After striking wires, the main rotor traveled across the street and came to rest on the lawn of the county emergency communications center. Examination of the helicopter revealed that the main rotor had separated from the main rotor shaft just below the rotor head, and the droop (static) stops had been damaged. The fairing over the transmission was crushed and broken, the tail stinger was bent upwards, and the upper tail fin was bent to the right. The tail boom was also bent to the right and almost completely separated just aft of the cabin area. The rear crossover tube for the landing skids was bent, and the crossover tube was pushed up into the right side of the lower fuselage. Both windscreens were broken.

Aircraft

Registration
N275AE
Reported as
Bell 206 (L3)
Category
Helicopter
Serial number
51186
Built
1986
Airframe hours
13,103
Engine
Rolls Royce M250-C30P, 374 horsepower, turbo shaft
Damage
Substantial damage
Flight
Other work use · Part 91
Operator
Air Evac Ems Inc
Registered owner
Air Evac Ems Inc
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · October 24, 2017
Departed
None · Troy, TN
Destination
Lawn · Union City, TN
Flight plan
Company VFR
Airport
Lawn · None
Equipment
Electronic flight bag or handheld device, Auto-pilot, ADS-B, Satellite tracking device, Electronic primary flight display

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 · 3

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
51
Injuries
Minor
Certificate
Commercial
Airplane ratings
Single-engine land
Instrument ratings
Helicopter
Medical
Class 2, Without waivers/limitations
Last flight review
November 1, 2016
Seat
Right
Restraint
4-point
Flight hours
2,687 total · 2,327 in this make and model
Role
Cabin crew
Injuries
Minor
Seat
Right
Restraint
3-point
Role
Cabin crew
Injuries
Minor
Seat
Rear
Restraint
3-point

Weather

Conditions
Visual (VMC) · Day
Wind
30° at 8 knots, gusting 13
Visibility
10 statute miles
Lowest ceiling
None
Temperature
54 °F, dew point 41 °F
Altimeter
30.20 inHg
Observed at
UCY, 4 nm away

Docket · 7

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