NTSB investigations, 2001
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\") = 2001
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") = 2001 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 SEA02LA003Accident · Minor injuriesLimited investigationFinal reportEllsberg One Design · Bend, ORthe separation of a propeller counterweight mounting bracket due to incorrect mounting bolt torque. Factors include significant powerplant vibration during the forced landing, no suitable landing area, and soft terrain next to the narrow road on which the…NTSB NYC01LA221Accident · No injuriesLimited investigationFinal reportde Havilland DHC-94 Moth Minor · Farmington, PAThe in-flight separation of a propeller blade, which resulted in a forced landing to unsuitable terrain. A factor related to the accident was the plowed field.NTSB CHI01IA246Incident · No injuriesIncident investigationFinal reportAir Tractor AT-401 · Kenesaw, NEThe propeller blade fatigue leading to its tip separating during an aerial application. Factors were no suitable terrain for an emergency landing, high vegetation, and soft terrain encountered during the emergency landing.NTSB CHI01LA222Accident · Minor injuriesLimited investigationFinal reportDruine Turbulent D-31 · Lebanon, INThe pilot not maintaining aircraft control while maneuvering during initial climb. Factors to the accident were the improperly serviced propeller that resulted in a pitch setting that was insufficient for normal flight.NTSB DEN01LA085Accident · Minor injuriesLimited investigationFinal reportBoyd Young Kolb Mark III · Brigham City, UTthe pilot's misjudged landing flare, which resulted in a hard landing. A factor was the propeller tip separation due to foreign object damage.