WPR24LA134 · Bell 206L-3
Premier Rotors Bell 206L-3 · Accident: system/component malfunction/failure (non-power) while maneuvering
From Modesto City Co-Harry Sham Field (MOD) to Tracy Municipal Airport (TCY)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR24LA134
- 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 206L-3
- 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
- N17592
- Operator
- Premier Rotors
- Onboard fatalities
- Unknown
- Route
- From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo Tracy Municipal Airport (TCY), Tracy, CA
- 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 · 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 propeller/rotor
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a pipeline inspection flight, the pilot and passenger of the accident helicopter heard a loud noise, followed by a shudder and an uncontrolled descent. The pilot was unable to stop the helicopter’s descent with collective control inputs and he completed a forced landing into an orchard, which resulted in substantial damage to the tailboom. Postaccident examination of the helicopter revealed fractures in the upper and lower arms of the cylinder extension to the collective control servo. All the linkages and securing hardware for the collective control system were in place. Metallurgical examination revealed the collective servo arm fractured due to fatigue cracking that had initiated in the lower cylinder extension arm at corrosion pits along the inside surface. Once the crack had propagated through more than 80% of the arm’s cross section, the remainder carrying the loads fractured from overstress. The upper arm also fractured from fatigue initiating at corrosion pits along the radii at the forward and aft ends of the open section in the middle of the arm. Composition testing determined that the elements in the corrosion pitting were consistent with compounds found in marine environments. The helicopter had been periodically flown about 50 nm from salt water. However, the undamaged cyclic servo had also been installed in the accident helicopter at the same time as the collective servo. It is unclear why the cylinder extension arms of the collective servo failed, and the cyclic servo cylinder extension arms remained intact, both having been exposed to the same environmental conditions; the extension arms for both the collective and cyclic servos were contained within a protective housing above the cockpit. The fracture surfaces were also examined to count the fatigue striations and correlate the fatigue crack growth with the 59 hours that the helicopter operated with newly installed composite blades. However, the number and pattern of crack arrest features could not be linked to any specific loading events, and the linking of the individual striations to the two-vibrations-per-blade revolution was inconsistent with the 59-hour propagation time. Therefore, the fatigue crack initiation or propagation could not be attributed to the blade installation.
Probable cause
A loss of collective control authority due to fatigue failure of the collective servo cylinder extension arms from corrosion pitting.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA134
- Event ID
- 20240429194163
- Case number
- WPR24LA134
- 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, coordinates, 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: 72ccf707605951c8fc095fc3784936e33acd0eac0d5623e73ccf6b6709670a6d; retrieved 2026-09-16T18:42:23.071Z.