The U.S. aircraft register, updated daily
Accidents · NTSB WPR15LA109 · Final report

Bell/Garlick UH 1H accident near Shelton, Washington, February 19, 2015

On February 19, 2015 at about 9:00 pm local time, a 1995 Bell/Garlick UH 1H (helicopter), registered N166DR, was substantially damaged in an accident during maneuvering (hover) near Shelton, Washington. It was an external-load flight under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The fatigue failure of the engine-to-transmission driveshaft adapter attachment bolt due to the application of inadequate torque on the bolt during assembly.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 19, 2015 · about 9:00 pm local time
Place
Shelton, Washington · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Bell/Garlick UH 1H, built 1995
Registration
N166DR · registry record · serial 66-16949
Damage
Substantial damage
Flight
External-load flight · agricultural flying rules (Part 137)

The NTSB's narrative final · quoted from the NTSB record

While the helicopter was in a hover and beginning to lift a 3,000-lb agricultural application container, the commercial pilot heard a "loud bang," followed by the low rotor warning horn. Ground crew were below the helicopter, so he pulled away from them, and the helicopter then yawed left. He was able to keep the helicopter level about 5 to 7 ft above ground level, and he then pulled the remaining collective pitch to touch down. The helicopter landed on uneven ground and subsequently rolled over onto its right side. During postaccident wreckage examination, the engine-to-transmission driveshaft adapter, which is the component between the engine output and the driveshaft, was found broken in multiple pieces. Further examination revealed thumbnail-shaped patterns and progressive crack arrest marks, consistent with fatigue, on the fracture surfaces. The bolt that attached the adapter to the mating coupling set had separated. The fracture surfaces on the bolt were generally flat with progressive crack arrest lines consistent with fatigue cracking. Given the sizes of the fatigue cracking areas on the components, it is likely that the attachment bolt separated first. Vibrations in the assembly caused by the separation of the bolt likely resulted in the numerous fatigue cracks in the driveshaft adapter. Thirty-four years before the accident, the manufacturer issued a technical bulletin, which addressed an issue with inadequate torque being applied on the attachment bolt during assembly and stated that excessive wear had been noted on the engine-to-transmission driveshaft adapter plug when engines were returned for overhaul. The bulletin noted that the wear resulted in the mating driveshaft adapter bottoming out on the antirotation tangs of the driveshaft adapter plug and causing a false torque of the bolt and wear and reduction gear damage. The bulletin identified a fix that involved reworking the driveshaft adapter spline and applying 160 to 200 inch-lbs of torque on the bolt. However, no evidence was found indicating that the recommended actions had been accomplished. The wear on the driveshaft adapter and mating washer could have been the result of an undertorqued bolt or been related to vibrations in the assembly, which resulted from the fatigue cracking of the bolt.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aircraft maintenance event during prior to flight
  2. Powerplant sys/comp malf/fail during maneuvering (hover) defining event
  3. Roll over during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft propeller/rotor › Main rotor drive › Engine/transmission coupling › Fatigue/wear/corrosion
  • cause Aircraft › Aircraft propeller/rotor › Main rotor drive › Engine/transmission coupling › Failure
  • cause Organizational issues › Development › Manufacture/production › (general) › Manufacturer

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
  • Flight time: 16,600 hours in all; 700 in this make and model; 15,800 as pilot in command
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 11,620.1 hours
  • Last inspection: approved inspection programme, January 16, 2014
  • Maximum gross weight: 9,500 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming T53-L-13 (turboshaft); 1,262 hours total
  • Operator: Northwest Helicopters LLC

The flight

  • Departed from: Shelton WA
  • Destination: Shelton WA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 230° at 10 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 8,000 ft; scat at 1,500 ft
  • Temperature: 54°F (12°C), dew point 48°F (9°C)
  • Altimeter: 30.21 inHg
  • Observation at 9:36 pm from KSHN, 7 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.