NTSB investigations, 1998
5 cases where the first occurrence was “Propeller failure/malfunction”.
Cases per year
| 1994 | 6 |
|---|---|
| 1995 | 10 |
| 1996 | 7 |
| 1997 | 7 |
| 1998 | 5 |
| 1999 | 10 |
| 2000 | 9 |
| 2001 | 5 |
| 2002 | 2 |
| 2003 | 9 |
| 2004 | 1 |
| 2005 | 3 |
| 2006 | 3 |
| 2007 | 4 |
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\" = 131)
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" = 131) 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 FTW98FA392Accident · Serious injuriesField investigationFinal reportPiper PA-20-180 · Thornton, COThe separation of a propeller blade due to corrosion initiated fatigue, followed by the separation of several of the engine's mounts, and the subsequent inability of the pilot to control the aircraft. A contributing factor was the trees.NTSB ANC98LA131Accident · No injuriesLimited investigationFinal reportCessna 172 · Palmer, AKFatigue of the forward end of the engine crankshaft resulting in separation of the propeller assembly, and the operator's failure to comply with a required maintenance procedure. A factor was uneven terrain.NTSB ATL98LA108Accident · Serious injuriesLimited investigationFinal reportDean R. Fellows Vans RV-6 · Bainbridge, GAThe pilot's failure to properly modify the crankshaft per the manufacturers service instructions for installation of a fixed pitch propeller and to apply proper torque values to the propellers mounting bolts.NTSB FTW99LA025Accident · No injuriesLimited investigationFinal reportMooney M20C · Vernon, TXFatigue cracking of the propeller blade which originated from corrosion pitting on its camber side, resulting in the blade tip separation during cruise flight.NTSB NYC98IA106Incident · No injuriesIncident investigationFinal reportBeech 1900D · Syracuse, NYImproper maintenance which resulted in a cross threaded\ mistapped counterweight bolt hole, and the subsequent failure of the propeller counterweight clamp assembly. Also causal was the inadequate inspection of the counterweight clamp threads by maintenance…