NTSB investigations, 1995
4 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\") = 1995
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") = 1995 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 CHI95FA320Accident · No injuriesField investigationFinal reportBell 230 · Ann Arbor, MIthe manufacturer's inadequate quality control which led to a fatigue failure of the tail rotor blade.NTSB LAX95TA328Accident · Serious injuriesFinal reportMcdonnell Douglas 369D · Pearl City, HIThe pilot's failure to secure his cargo/personal belongings which departed from the aircraft and struck the tail rotor.NTSB FTW95LA303Accident · No injuriesLimited investigationFinal reportBell 206B · West CameronThe disconnect of the tail rotor drive system for undetermined reasons. Factors were the pilot's inability to maintain directional control, and the lack of suitable terrain for the forced landing.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.