NTSB investigations, 1996
7 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\") = 1996
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") = 1996 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 FTW96LA350Accident · Minor injuriesLimited investigationFinal reportHardy Quickie Q-200 · Hudson, COdelamination of a propeller blade. A factor relating to the accident was: the terrain condition in the emergency landing area (soft/sandy berm and ditch).NTSB CHI96FA278Accident · 1 fatalField investigationFinal reportLancair 320 · Fond Du Lac, WIthe fatigue in the propeller flange with soft material and oversized lightening holes. A factor was the pilot's inability to maintain control of the aircraft due to the exceeded weight and balance which led to a stall/spin.NTSB FTW96LA318Accident · Minor injuriesLimited investigationFinal reportSteward Breezy · Owasso, OKthe pilot's failure to secure his cargo prior to departure. A factor was the lack of suitable terrain available for the forced landing.NTSB ANC96LA096Accident · No injuriesLimited investigationFinal reportBeech 18 · Fairbanks, AKThe malfunction of the propeller control unit on the right engine.NTSB MIA96LA173Accident · No injuriesLimited investigationFinal reportPiper PA-23-150 · Knoxville, TNFatigue failure of the blade No. 1 hub arm of the left propeller.NTSB LAX96LA142Accident · Minor injuriesLimited investigationFinal reportTaylorcraft DC-65 · Fremont, CAthe in-flight separation of a portion of one wooden propeller blade due to undetected dry rot in the wood fibers.NTSB BFO96LA038Accident · No injuriesLimited investigationFinal reportErcoupe 415-C · Hurlock, MDinadequate inspection by maintenance personnel which failed to detect a fatigue crack, and resulted in an in-flight crankshaft fracture and propeller assembly separation. A related factor was the deep snow encountered during the subsequent forced landing.