FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22LA236 · Bell 206B

24 Jun 2022 · Merced, CA, United States

Bettencourt Flying Service Bell 206B · Accident: system/component malfunction/failure (non-power) while maneuvering

From Atwater, CA to an unrecorded destination

Report a problem

Event

NTSB case
WPR22LA236
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bell 206B

Aircraft type
Bell 206
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N915B
Onboard fatalities
Unknown
Route
From Atwater, CATo not recorded
Aircraft age
About 50 years (built 1972)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 137: Agricultural
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering · low-altitude flying
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he was on an agricultural spray run. He had just performed a 180° turn and, about six feet above ground level (agl), he felt a vibration. He then felt a “snap” and the helicopter began to rotate left. He applied right pedal, entered an autorotation, and attempted to decrease the airspeed. He tried to perform a run-on landing in the 4-ft-tall corn, but upon touchdown, the helicopter rolled up on its nose and the main rotor blades severed the tail boom.

A postaccident examination revealed that the KAflex driveshaft was separated and there were several sheared bolts and pieces of the KAflex located underneath the engine. Subsequent metallurgical examination determined that the failure of the KAflex coupling resulted from fatigue observed in two flex plate segments and an adjacent attachment bolt, indicating these components were the initial points of failure. The fatigue cracking initiated at areas adjacent to wear and material loss. With the fracture of flex plates and bolts, the interconnect and end fitting could rotate, resulting in the assembly failure. One flex plate and bolt exhibited more fatigue, suggesting longer crack propagation and earlier fracture, while thumbnail cracks on a second flex plate indicated incipient propagation when other components failed in overstress.

The bolt and flex plate with fatigue features showed severe wear and loss of cross-sectional area, potentially concentrating stress at these locations. Although the investigation could not determine which fractured first, the joint had become loose, likely due to wear over time or inadequate assembly/maintenance. Most of the fractured bolts did not have discernable fracture features, likely lost to post fracture wear and battering. Visual inspections during maintenance might reveal a loose bolt, but fatigue cracks in these components would be more difficult to detect, leading to rapid propagation in rotary aircraft parts.

Probable cause

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 power to the transmission and a subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22LA236
Event ID
20220628105378
Case number
WPR22LA236
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 94f2eedb0168b9c80de346e5b2c92921500ae63125953971ba92fe0a77630514; retrieved 2026-09-16T15:23:56.455Z.