NTSB investigations, 2003
5 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\") = 2003
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") = 2003 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 SEA04LA018Accident · Serious injuriesLimited investigationFinal reportBell 47G-3B-2 · Monmouth, ORFatigue failure of a tail rotor blade during hover operations.NTSB FTW04TA012Accident · Minor injuriesFinal reportHughes OH-6A · Eagle Pass, TXThe failure of the aft segment of the tail rotor drive shaft for undertermined reasons. A contibuting factor was the lack of suitable terrain for the foced landing.NTSB CHI03LA217Accident · No injuriesLimited investigationFinal reportEnstrom F-28C · Waverly, IAThe main rotor blade push-pull rods being corroded, sustaining fatigue, and separating in cruise and the main rotor blade contacting the tail boom during the emergency landing. Factors were the diminished aircraft control and the vibrations encountered during…NTSB FTW03TA156Accident · No injuriesFinal reportBell 407 · Franklin, LAThe loss of tail rotor effectiveness due to the inadequate maintenance performed by other company personnel.NTSB FTW03LA104Accident · No injuriesLimited investigationFinal reportBell 206L-3 · Kingsland, TXThe loss of tail rotor drive as a result of a blanket coming in contract with the tailrotor blades, after the aft cargo door was left unsecured. Contributing factors were the lack of suitable terrain for the forced landing, and the failure of the medical…