# NTSB investigations: Bell 222: Airframe/component/system failure/malfunction

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB LAX03IA252](https://openairdocs.org/ntsb/LAX03IA252.md): Bell 222 · Salinas, CA · Incident · No injuries · Incident investigation · Final report · Jul 30, 2003 · N29KH · No damage
  > The fatigue failure (fracture) of the right forward transmission lift link during cruise flight, which resulted in a severe vibration and an emergency landing.
- [NTSB CHI98FA323](https://openairdocs.org/ntsb/CHI98FA323.md): Bell 222 · Spencer, IA · Accident · 3 fatal · Field investigation · Final report · Aug 21, 1998 · N30SV · Destroyed
  > The below standard (loose) fit of the 'white' swashplate outer ring pin resulting in fatigue and subsequent separation of the pin, and ultimately the in-flight breakup of the rotorcraft. A factor was the manufacturer's dissemination of the pin which did not…
- [NTSB FTW86FA016](https://openairdocs.org/ntsb/FTW86FA016.md): Bell 222A · Charenton, LA · Accident · No injuries · Field investigation · Final report · Oct 17, 1985 · N5013H · Substantial damage
  > The helicopter had just completed a phase two check, twenty minutes into the flight the occupants heard a loud noise and a severe one-to-one vibration ensued. A successful emergency landing was performed. Examination revealed that one swash plate drive link…
- [NTSB FTW83IA084](https://openairdocs.org/ntsb/FTW83IA084.md): Bell 222 · Houston, TX · Incident · No injuries · Incident investigation · Final report · Jan 11, 1983 · N23021 · No damage
  > The helicopter developed a severe vibration while in flt. The pilot executed an emergency landing with no further acft damage. An examination of the acft revealed that the walking beam assembly located between the swash plate and rotor pitch link had failed.…

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1182122')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=1182122&occurrence=130

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.