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

Bell 206B accident near Rockville, Idaho, May 26, 2017

On May 26, 2017 at about 4:44 pm local time, a 1976 Bell 206B (helicopter), registered N24FS, was substantially damaged in an accident during maneuvering (low-alt flying) near Rockville, Idaho. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The in-flight failure of the engine-to-transmission drive shaft due to a fatigue fracture of one of the KAflex flex frames caused by a loose bolt, which resulted in a total loss of engine power and a subsequent hard landing.

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

What the record shows

Date
May 26, 2017 · about 4:44 pm local time
Place
Rockville, Idaho · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Bell 206B B, built 1976 · all 206Bs on the register
Registration
N24FS · no longer on the register · serial 2040
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

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

The commercial pilot reported that, while conducting an aerial application flight, he performed a 180° turn at an altitude of about 40 to 50 ft above ground level and heard a growling noise, which was followed by the sound of a loud bang and a subsequent loss of power. The pilot lowered the collective, likely to initiate an autorotation to a nearby open field, and the helicopter landed hard. Postaccident examination of the helicopter airframe and engine revealed that the middle portion of the engine-to-transmission drive shaft was separated between the engine and transmission KAflex couplings. No additional evidence of any preexisting mechanical malfunction was observed. Metallurgical examination of the shaft and couplings revealed that the shaft had failed from a pair of fatigue cracks at a bolt hole in one element of the flexure coupling (flex frame). This bolt hole exhibited rotational wear severe enough to cause material loss on one face of the bolt hole wall. This circular-wear depression was consistent with repeated rotational contact with an adjacent washer. It is likely that, once the fatigue cracks at the bolt hole propagated deeply enough, the remaining flexure element cross-section fractured from overstress. The failure of this flexure element led to multiple and subsequent overstress failures in other flexure elements, eventually compromising the entire drive shaft assembly. The circular-wear depression and the longitudinal wear inside the flexure element bolt hole were both consistent with a loose bolt assembly. Because the bolt assembly was loose, the washer would have been able to rub on the flexure element. In addition, the bolt shaft would have been able to rub or gouge the inner wall surfaces of the bolt hole. The bolt and associated washer were not located in the wreckage. None of the maintenance performed on the helicopter about 1 month before the accident involved the flex frame bolt assemblies, so the investigation could not determine how one of the bolts became loose.

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. Sys/Comp malf/fail (non-power) during maneuvering (low-alt flying) defining event
  2. Off-field or emergency landing during maneuvering (low-alt flying)
  3. Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying)

The NTSB's findings

  • cause Aircraft › Aircraft propeller/rotor › Main rotor drive › Engine/transmission coupling › Fatigue/wear/corrosion
  • Personnel issues › Task performance › Maintenance › Installation › Other/unknown

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 11,884 hours in all; 150 in this make and model; 60 in the last 90 days; 40 in the last 30 days; 11,712 as pilot in command; 1,800 on instruments
  • Last flight review: March 21, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 15,427.4 hours
  • Last inspection: annual inspection, January 6, 2017; 31 hours since
  • Maximum gross weight: 3,201 lb
  • Landing gear: fixed
  • Engine: Allison 250-C20 SER (turboshaft); 0 hours total
  • Operator: Paulys Helicopter Services INC

The flight

  • Departed from: Rockville ID at 4:39 pm
  • Destination: Rockville ID
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 43°F (6°C)
  • Altimeter: 29.89 inHg
  • Observation at 4:55 pm from KMAN, 28 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

10 documents, released by the NTSB on October 4, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

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.