NTSB investigations, CA
6 cases where the first occurrence was “Rotor failure/malfunction”.
Cases per year
| 1995 | 1 |
|---|---|
| 1998 | 3 |
| 2000 | 1 |
| 2002 | 1 |
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.\"eventStateOrRegion\" = 'CA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 132)
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."eventStateOrRegion" = 'CA' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 132) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 LAX02FA276Accident · 3 fatalField investigationFinal reportBell 222U · Nipton, CAThe main rotor blade separation while maneuvering for unknown reasons. A factor was the dark night condition.NTSB LAX00FA306Accident · 2 fatalField investigationFinal reportRobinson R22 Beta · Watsonville, CAThe divergence of the main rotor from its normal plane of rotation for an undetermined reason, which resulted in mast bumping and rotor contact with the fuselage.NTSB LAX98TA278Accident · No injuriesFinal reportAerospatiale SA316B · Porterville, CAThe pilot's failure to maintain adequate in-flight clearance between the bucket and trees resulting in the entanglement/separation of the long line and subsequent impact with and separation of the tail rotor assembly. A factor was the trees.NTSB LAX98FA236Accident · 3 fatalField investigationFinal reportSikorsky CH-54A · Yucca Valley, CAAn in-flight main rotor blade spar separation as a result of the pilot-in-command's decision to continue to fly the aircraft after it had failed an AD directed BIM check. Factors were the failure of the operator's chief pilot to maintain proper supervision…NTSB LAX98GA127Accident · 4 fatalFinal reportBell 205A-1 · Los Angeles, CAAn excessive bending load applied to the tail rotor blade assembly of an undetermined origin which produced a fatigue crack, the separation of the assembly, and a forced landing. Factors were the lack of suitable terrain to perform a forced landing, the…NTSB LAX95FA225Accident · Serious injuriesField investigationFinal reportHughes 369D · Highland, CAthe pilot's failure to verify the security of his passenger's cargo/personal belongings which departed the aircraft striking the tailrotor.