NTSB investigations: Bell 412
5 cases on aircraft the registry lists as Bell 412, 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
| 1982 | 1 |
|---|---|
| 1987 | 1 |
| 1989 | 1 |
| 1991 | 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 ('1182202')
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 ('1182202')
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 FTW91FA155Accident · 1 fatalField investigationFinal reportBell 412 · Garden BanksOverheating and subsequent failure of the number one tail rotor hanger bearing for an undeterined reason, and failure of the tail rotor drive shaft.NTSB FTW91IA143Incident · No injuriesIncident investigationFinal reportBell 412 · Rowan MidlandThe mechanic's failure to assemble the tail rotor drive shaft correctly and the subsequent failure of the tail rotor drive shaft. A factor was the lack of inspection procedures for offshore maintenance.NTSB ANC89FA069Accident · Minor injuriesField investigationFinal reportBell 412 · Girdwood, AKA main rotor flight control bolt (part number 20-057-6-38D) came out of its rod end bearing while in flight due to the bolt being improperly torqued during maintenance.NTSB FTW88FA036Accident · Serious injuriesField investigationFinal reportBell 412 · Galveston, TXThe acft landed hard in the gulf of Mexico during an autorotation that was entered following the separation of the 90 degree gearbox. The gearbox (with tail rotor blades) separated due to an imbalance. However, the gearbox was not recovered during the…NTSB FTW83IA053Incident · No injuriesIncident investigationFinal reportBell 412 · Intercoastal Ci, LAWhile in cruise flight, the pilots heard a loud pop and felt a severe cyclic control vibration. An immediate precautionary landing was made. An examination revealed that there was a fatigue crack in the trailing edge of the blue, main rotor yoke flexure, pn…