FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA004 · Bell 206B

1 Oct 2022 · Fresno, CA, United States

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

Report a problem

Event

NTSB case
WPR23LA004
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
N284CA
Operator
Lasen
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
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 91: General Aviation
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
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 propeller/rotor

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

NTSB narrative

During a post-maintenance operational check flight, the pilot and mechanic heard a loud crack/pop sound, followed by the helicopter spinning to the right. The pilot initiated an autorotation, and the helicopter subsequently impacted a tree and landed hard, which resulted in a rollover and substantial damage to the helicopter

Postaccident examination of the helicopter revealed that the No. 4 segmented tail rotor drive shaft failed due to disbonding of the splined adapter from the tail rotor drive shaft tube, which resulted in a loss of tail rotor drive to the tail rotor gearbox and subsequent loss of directional control of the helicopter. Once the disbond occurred, the splined adapter continued to turn under power while the drive shaft tube slowed down, further damaging the disbonded surfaces, which prevented identification of a reason for the disbond.

The operator accomplished the recurrent proof-load test on their bonded segmented drive shafts, as outlined by Bell Alert Service Bulletin (ASB) No. 206-20-139, a total of 4 times since release of the ASB, with no anomalous findings. The ASB specified that within the next 75 flight hours or 3 months after release of the bulletin, and every 300 flight hours or 12 months thereafter, operators should conduct a visual inspection of the bond line of the bonded adapters, apply an index mark on each bonded adapter, and conduct a proof-load test using a bonded shaft tool. The operator had last performed the proof-load test about 77.7 hours before the accident. Accordingly, the frequency of the proof-load test in the ASB, which was subsequently required by Transport Canada Airworthiness Directive (AD) No. 2022-33 and Federal Aviation Administration (FAA) AD No. 2023-06-05, may not be adequate in discovering an impending failure of a bonded adapter. Testing by Bell on exemplar bonded segmented drive shafts, in support of the development of the proof-load testing (preceding issuance of the ASB), showed that a drive shaft [with a serviceable bond] would yield in excess of 200% applied torque, and that yielding of the shaft tube occurs first. Based on a review of the operator’s proof-load testing tools, the operator was using the correct tooling. Additionally, there was no evidence the operator applied excessive torque on the bonded segmented drive shafts during the recurrent proof-load tests. Therefore, the operator’s continuing maintenance and performance of the proof-load tests on the bonded segmented drive shafts were likely not a factor in this accident.

Metallurgical examination of the bonded tail rotor drive shaft found that the splined adapter tapered thin wall did not meet its thickness requirements; however, it’s likely this was not the sole factor in the disbond. The segmented drive shafts are not life limited and therefore are not required to be tracked after manufacture; accordingly, the age and time in service of the accident drive shaft could not be determined.

Probable cause

The disbond of a tail rotor drive shaft splined adapter, which resulted in a loss of tail rotor drive and a subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA004
Event ID
20221003106044
Case number
WPR23LA004
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: 3ef99db76f57e3d297a35906510d273bb30fe40ffc02e31fd8bcdb83328ef537; retrieved 2026-09-16T16:09:49.030Z.