NTSB investigations: Bellanca 17-30A, 2000
8 cases on aircraft the registry lists as Bellanca 17-30A. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1969 | 1 |
|---|---|
| 1970 | 2 |
| 1971 | 2 |
| 1972 | 5 |
| 1973 | 8 |
| 1974 | 12 |
| 1975 | 9 |
| 1976 | 8 |
| 1977 | 15 |
| 1978 | 7 |
| 1979 | 6 |
| 1980 | 10 |
| 1981 | 6 |
| 1982 | 5 |
| 1983 | 5 |
| 1984 | 6 |
| 1985 | 6 |
| 1986 | 5 |
| 1987 | 4 |
| 1988 | 6 |
| 1989 | 4 |
| 1990 | 3 |
| 1991 | 5 |
| 1992 | 7 |
| 1993 | 3 |
| 1994 | 5 |
| 1995 | 4 |
| 1996 | 6 |
| 1997 | 5 |
| 1998 | 4 |
| 1999 | 4 |
| 2000 | 8 |
| 2001 | 4 |
| 2002 | 6 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 4 |
| 2006 | 2 |
| 2007 | 3 |
| 2008 | 3 |
| 2009 | 1 |
| 2010 | 1 |
| 2011 | 3 |
| 2012 | 2 |
| 2013 | 3 |
| 2014 | 5 |
| 2015 | 2 |
| 2016 | 4 |
| 2017 | 5 |
| 2019 | 3 |
| 2020 | 1 |
| 2021 | 2 |
| 2022 | 2 |
| 2023 | 3 |
| 2024 | 4 |
| 2025 | 1 |
| 2026 | 2 |
Where
Latest 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 x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220433'))
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 x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220433'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 NYC01LA044Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Zanesville, OHThe pilot's failure to follow the restart procedures published in the approved flight manual(AFM). Factors were his failure to follow the fuel management procedures published in the AFM, which resulted in fuel starvation.NTSB IAD01LA016Accident · Serious injuriesLimited investigationFinal reportBellanca BL-17-30A · Union, CTpilot's mismanagement of the available fuel supply, which resulted in a loss of engine power due to fuel starvation.NTSB DEN00LA174Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30A · Las Cruces, NMThe pilot's failure to maintain lateral clearance with terrain. Factors were the confined area used for takeoff, and the high vegetation alongside the road.NTSB FTW00FA208Accident · 2 fatalField investigationFinal reportBellanca 17-30A · Houston, TXthe loss of engine power for an undetermined reason during maneuvering. Contributing factors were the dark night light conditions and the lack of suitable terrain for the forced landing.NTSB MIA00LA199Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30A · Albany, GAThe dual student's failure to purge the fuel lines of air after a fuel tank was run dry on the previous flight and the failure of the electric fuel boost pump on or low position due to a loose wire which resulted in failure of the engine due to air in the…NTSB CHI00FA145Accident · 2 fatalField investigationFinal reportBellanca 17-30A · Taylor, MOflight into known adverse weather conditions and the altitude/clearance not maintained by the pilot. An additional cause was the improper in-flight planning/decision by the pilot. Contributing factors were the weather below approach/landing minimums, night…NTSB IAD00LA028Accident · No injuriesLimited investigationFinal reportBellanca B17-30A · Shenandoah, VAthe pilot's failure to maintain control during landing roll-out. A factor was the pilot's lack of total experience.NTSB ATL00FA019Accident · 2 fatalField investigationFinal reportBellanca BL-17-30A · Monteagle, TNThe pilot's failure to adequately evaluate weather conditions that resulted in the continuation of visual flight into instrument weather conditions and the subsequent collision with trees.