CEN14LA296

NTSB accident investigation · Bell 206B · Decatur, TX · June 17, 2014

Accident · Minor injuriesLimited investigationFinal report
Date
June 17, 2014, 15:00 local (20:00 UTC)
Place
Decatur, TX
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N536TBell 206B
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report June 1, 2015
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA Rotorcraft Directorate, FAA FSDO, FAA AVP-100, Rolls-Royce Corporation, Bell Helicopter, FAA Flight Safety
FAA report
20140617008589A
Case key
89462

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 improper recovery from a practice autorotation, which resulted in a hard landing.

Findings · 1

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.

Action: incorrect action performancePersonnel issues › Action/decision · Instructor/check pilotBell 206B: 11 casesAll aircraft: 1,386 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-rated student and flight instructor were conducting a helicopter proficiency flight. After about 2 hours of flight and completing a series of maneuvers, which included straight-in and 180-degee autorotations, the instructor began to demonstrate another 180-degree autorotation. The instructor reported that, when the helicopter was at 200 ft at the start of the approach, the rotor speed was in the mid to low section of the green band. At the beginning of the flare, he tried to roll in full throttle, but he felt resistance, and he didn't get the power restored in time. He then attempted to level the helicopter to avoid a tail strike. The pilot receiving instruction reported that the instructor was at the controls and that, when the helicopter was at 100 ft, he noticed that the rotor speed was at a minimum and that the rate of closure was slow. He thought they were going to be short, so he called for power and reached for the throttle to confirm it was fully on. The helicopter landed hard and slid to a stop just off the runway. Examination of the helicopter and throttle system did not reveal any abnormalities.

Factual narrative

On June 17, 2014, about 1500 central daylight time, a Bell 206B helicopter, N536T, made a hard landing at the Decatur Municipal Airport (KLUD), Decatur, Texas. The flight instructor and pilot rated student received minor injuries, and the helicopter was substantially damaged. The helicopter was registered to MBM Aviation Consultants, Inc., and operated by the Federal Aviation Administration (FAA) under the provisions of 14 Code of Federal Regulations Part 91 as a training flight. Visual meteorological conditions prevailed for the flight, which operated without a flight plan. The flight originated from the Fort Worth Alliance airport (KAFW), Fort Worth, Texas. The flight was planned as part of the agency's quarterly proficiency program for inspectors. The contract flight instructor, who was initially scheduled to fly, was not available to perform the flight. An FAA flight instructor was then scheduled, and flew in the morning with another FAA employee. The accident flight was the student's first flight with the FAA instructor, and the instructor's second flight of the day. The afternoon flight had a similar flight profile as the morning's flight and was estimated to last about 2.5 hours. The instructor and pilot rated student reported that they were about 2 hours into the proficiency flight, and had completed a series of maneuvers, which included straight-in and 180-degee auto rotations. To complete the flight objectives before proceeding back to KAFW, the instructor planned to demonstrate another 180-degree auto rotation. The instructor reported, the rotor speed was in the mid to low section of the green band, at 200 feet at the start of the approach. At the beginning of the flare, he tried to roll in full throttle, but felt resistance, and he didn't get the power restored in time. He then elected to level the helicopter, so the tail wouldn't hit first and roll the helicopter over. The helicopter touched down on the asphalt 100 feet short of the fix distance markers on runway 17. The pilot rated student, reported that on the last 180-degree auto rotation, the instructor was at the controls. At 100 feet on the approach, he noticed that the rotor speed was at a minimum and the rate of closure was slow. He felt they were going to be short, so he called for power and reached for the throttle to confirm it was full on. Another helicopter, which was in the airport traffic pattern, made a radio call to determine the position of the accident helicopter; the radio call, was not answered. They then noticed the helicopter on the ground, upright, just east of runway 17. The main rotor blades were not turning, the tail boom was missing just aft of the horizontal stabilizer and that there was a debris path, beginning about 400 feet before the 1,000 foot fixed distance markers. The NTSB, FAA, and technical representatives from the engine and airframe manufacturers responded to the accident site. Examination of the runway revealed a scar consistent with thetail boom impacting the runway first. The helicopter came to rest upright, partially off the runway, approximately 207 feet, from the first impact point. Numerous marks, consistent with the helicopter's landing skids were noted between the first scar and the helicopter. The helicopter was sitting on its landing skids, but leaning to the left. The tail boom had separated just aft of the stabilizer, the tail rotor gear box was torn from the tail boom. The transmission was tilted aft and had broken free of the driveshaft. Both main rotor blades had impact damage, consistent with striking the tail boom and horizontal stabilizer. The NTSB investigator demonstrated free movement of the throttle while the corresponding pointer movement at the FCU (Fuel Control Unit) was witnessed by the engine technical representative. An examination of the throttle system was conducted on June 19, 2014, by FAA maintenance inspectors. The inspection was conducted in accordance with Bell helicopter maintenance manual (BHT206 MM-1, chapter 76-00-00). No abnormalities were noted the throttle system and it met the manufacturer's instructions for continued airworthiness.

Aircraft

Registration
N536T
Reported as
Bell 206B
Category
Helicopter
Serial number
3195
Built
1980
Engine
Allison 250-C20 SER, 400 horsepower, turbo shaft
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Federal Aviation Administration
Registered owner
Mbm Aviation Consultants Inc
Airworthiness certificate
Standard, Normal
Departed
KAFW · Fort Worth, TX
Destination
KAFW · Fort Worth, TX
Airport
KLUD · Decatur Muncipal, runway 17, 4,000 × 60 ft, asphalt

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
57
Injuries
Minor
Airplane ratings
Single-engine land
Instrument ratings
Helicopter
Medical
Class 2
Last flight review
June 1, 2013
Seat
Left
Restraint
4-point
Flight hours
10,000 total
Role
Pilot
Age
47
Injuries
Minor
Certificate
Airline transport
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane, Helicopter
Medical
Class 2
Seat
Right
Restraint
4-point

Weather

Conditions
Visual (VMC) · Day
Wind
160° at 14 knots, gusting 20
Visibility
10 statute miles
Lowest ceiling
None
Temperature
86 °F, dew point 66 °F
Altimeter
29.93 inHg
Observed at
KLUD

Docket · 6

The files NTSB released with the investigation on April 6, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.7 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.