LAX03IA252 · Bell 222
Bell 222 · Incident: airframe, component or system failure en route
From Hollister, CA to Salinas Municipal Airport (SNS)
Event
- NTSB case
- LAX03IA252
- 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
- Incident
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Charter & commuter
- 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 222
- Aircraft type
- Bell 222
- 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
- N29KH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hollister, CATo Salinas Municipal Airport (SNS), Salinas, 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 135: Air Taxi & Commuter
- 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
- En route · cruise
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Miscellaneous rotorcraft, transmission support tube/attchmnt › Fatigue
- Miscellaneous rotorcraft, transmission support tube/attchmnt › Fractured
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial helicopter pilot reported that while in cruise flight, the helicopter developed a severe vibration. The vibration was so extreme that he was not able to read any of his flight instruments. He declared an emergency, started a slow descent, and made a run-on landing to a dirt field. A post-incident inspection revealed that the right forward transmission lift link had failed at the lower rod end assembly. The failure point was in the threaded area of the rod end. The total time on the failed part (p/n 222-331-626-105) was 3,890.8 hours total time since new. The lift link assembly was the original part installed on the incident helicopter. The lift link assembly was shipped to the National Transportation Safety Board, Materials Laboratory and forwarded to Bell Helicopters for further analysis. It was determined that the link fracture was a result of fatigue in a thread root of the lower elastometric rod end bearing housing. No material discrepancies or deficiencies were found in the rod end bearing housing.
Probable cause
The fatigue failure (fracture) of the right forward transmission lift link during cruise flight, which resulted in a severe vibration and an emergency landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03IA252
- Event ID
- 20030820X01372
- Case number
- LAX03IA252
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, damage. 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: 34b1208460ec7000c66cd09abfc00bde0cedab616a3936db27af571735518ec7; retrieved 2026-09-18T15:43:34.710Z.