NTSB investigations: Bell 212
5 cases on aircraft the registry lists as Bell 212, where the first occurrence was “Airframe/component/system failure/malfunction”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1983 | 1 |
|---|---|
| 1992 | 1 |
| 1999 | 1 |
| 2000 | 2 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "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 ('1181420')
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"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
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 ('1181420')
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" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB LAX00FA130Accident · 1 fatalField investigationFinal reportBell 212 · Snelling, CAthe in-flight separation of the main rotor mast while in cruise flight following a mast bumping event. The reason for the mast bumping event was not determined.NTSB DEN00LA045Accident · Serious injuriesLimited investigationFinal reportBell 212 · Mt Pleasant, UTFailure of the main rotor mast due to fatigue that resulted from inadequate quality assurance during the manufacturing process.NTSB MIA00FA030Accident · 2 fatalField investigationFinal reportBell 212 · Philadelphia, MSThe failure of the pilot and company maintenance personnel during preflight and periodic inspections to identify the signs of fretting and looseness in the "red" main rotor blade pitch change horn to main rotor blade grip attachment, resulting in the…NTSB FTW92FA077Accident · 1 fatalField investigationFinal reportBell 212 · Morgan City, LAThe inflight separation of the main rotor system as results of the main rotor static stop contacting the mast for undetermined reasons.NTSB LAX83FA277Accident · 2 fatalField investigationFinal reportBell 212 · Goleta, CAThe plt stated that as he approached the oil rig & reduced power to start his descent from 500 ft, the tail rotor (t/r) pedals began to vibrate. The vibrations became worse with a further reduction of power to reduce airspeed. The plt then planned a descent…