Fatal NTSB investigations
10 cases where the first occurrence was “Rotor failure/malfunction”.
Cases per year
| 1996 | 1 |
|---|---|
| 1997 | 1 |
| 1998 | 4 |
| 1999 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2004 | 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.\"highestInjuryLevel\" = 'Fatal'
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."highestInjuryLevel" = 'Fatal' 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 SEA05FA019Accident · 2 fatalField investigationFinal reportRobinson R22 Beta · Arlington, WAThe divergence of the main rotor from its normal plane of rotation for an undetermined reason, resulting in rotor contact with the aircraft's left windscreen. The failure of the door pins to be installed was a factor.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 FTW99FA192Accident · 3 fatalField investigationFinal reportMBB BK-117-B2 · Fresno, TXthe loss of control during approach due to the corrosion of the T-T strap which resulted in fatigue cracking and subsequent separation of the strap and main rotor blade from the helicopter.NTSB CHI98FA313Accident · 1 fatalField investigationFinal reportHiller FH-1100 · Dewitt, MIThe rotor failure/malfunction due to debonding of the tail rotor blade. Also causal was the inadequate maintenance inspection of the aircraft by the company and the improper maintenance procedure by other maintenance personnel.NTSB IAD98FA092Accident · 1 fatalField investigationFinal reportAustin Revolution Mini 500 · Northampton, PAthe improper maintenance adjustment and the failure to properly torque the pitch-change link barrel by the owner/builder which resulted in main rotor to tailboom contact and main rotor separation.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 SEA97LA117Accident · 1 fatalLimited investigationFinal reportHiller UH-12E · Miltonfreewater, ORThe main rotor blade separated due to fatigue. Factors were: an Airworthiness Directive was not properly performed, and inadequate inspection of the main rotor blades.NTSB LAX96LA315Accident · 1 fatalLimited investigationFinal reportBell 47-G4A · Guamloss of tail rotor control due to improper maintenance.