NTSB investigations, 1998
8 cases where the first occurrence was “Rotor failure/malfunction”.
Cases per year
| 1994 | 1 |
|---|---|
| 1995 | 4 |
| 1996 | 3 |
| 1997 | 2 |
| 1998 | 8 |
| 1999 | 2 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 4 |
| 2003 | 5 |
| 2004 | 4 |
| 2005 | 2 |
| 2006 | 2 |
| 2007 | 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 year(c.\"eventDate\") = 1998
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 year(c."eventDate") = 1998 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 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 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 SEA98LA160Accident · Minor injuriesLimited investigationFinal reportMcDonnell Douglas 369D · Oso, WAThe separation of the 90 degree gearbox and tail rotor assembly for undetermined reasons followed by the inability of the pilot-in-command to maintain control of the rotorcraft.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 SEA98LA124Accident · Minor injuriesLimited investigationFinal reportHiller UH-12E · Eltopia, WAFatigue of the control rotor blade spar and failure of the maintenance inspector to follow the procedures set forth in the airworthiness directive.NTSB ATL98LA065Accident · No injuriesLimited investigationFinal reportSchweizer 269C · San Juan, PRThe pilot's failure to adequately secure the cargo strap which became entangled in the tail rotor, leading to a loss of the tail rotor control. This was followed by an improperly executed emergency procedure and an in-flight collision with the ground. A…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…