NTSB investigations, 2000
9 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\") = 2000
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") = 2000 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 IAD01FA015Accident · No injuriesField investigationFinal reportBeech F90 · Lynchburg, VAImproper rigging of both propeller assemblies by maintenance personnel, which resulted in the inadvertent feathering of both propellers after takeoff. Factors included a lack of rigging experience in airplane make and model by maintenance personnel, unclear…NTSB SEA01LA023Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Stevensville, MTFatigue of the right propeller blade resulting in an in-flight separation of the blade tip. A contributing factor was the improper maintenance procedure.NTSB FTW01LA005Accident · 2 fatalLimited investigationFinal reportHolt Thorpe T-18C · Imperial, TXthe failure of the propeller blade due to fatigue, which originated from a corrosion crack. A contributory factor was the pilot/owner's failure to ensure that the propeller was overhauled at the manufacturer's recommended interval.NTSB FTW00LA242Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Corsicana, TXthe in-flight separation of the propeller blade, which resulted from intergranular corrosion and fatigue cracking.NTSB MIA00LA225Accident · No injuriesLimited investigationFinal reportCessna 421A · Homewood, MSThe inadequate installation of the right propeller by the mechanic for his failure to properly torque the eight nuts resulting in fatigue failure of the studs and separation of the right propeller during cruise flight. Findings in the investigation were 1)…NTSB FTW00LA197Accident · No injuriesLimited investigationFinal reportBushby Midget Mustang · Tulsa, OKThe in-flight separation of the propeller spinner. A factor was the lack of suitable terrain for the precautionary landing.NTSB DEN00IA133Incident · No injuriesIncident investigationFinal reportDiamond Aircraft Industries 20C-1 · Spanish Fork, UTThe company maintenance personnel's inadequate torquing procedures of the propeller attachment bolts which resulted in the fatigue failure of the propeller attachment bolts and the in-flight separation of the propeller.NTSB DEN00FA092Accident · Minor injuriesField investigationFinal reportSwearingen SA226TC · Denver, COpropeller blade fatigue failure due to stress corrosion.NTSB SEA00LA068Accident · No injuriesLimited investigationFinal reportPZL-Bielsko SZD-45A Ogar · Libby, MTA crack in the propeller blade that developed into a complete separation of the blade.