NTSB investigations: Continental IO-520 series, 2003, TX
3 cases on aircraft whose registry engine model is Continental IO-520 series. 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
| 1964 | 2 |
|---|---|
| 1965 | 3 |
| 1966 | 6 |
| 1967 | 9 |
| 1968 | 5 |
| 1969 | 8 |
| 1970 | 5 |
| 1971 | 5 |
| 1972 | 4 |
| 1973 | 6 |
| 1974 | 13 |
| 1975 | 10 |
| 1976 | 11 |
| 1977 | 11 |
| 1978 | 8 |
| 1979 | 9 |
| 1980 | 15 |
| 1981 | 13 |
| 1982 | 10 |
| 1983 | 3 |
| 1984 | 7 |
| 1985 | 4 |
| 1986 | 4 |
| 1987 | 6 |
| 1988 | 5 |
| 1989 | 7 |
| 1990 | 4 |
| 1991 | 5 |
| 1993 | 5 |
| 1994 | 3 |
| 1995 | 9 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 3 |
| 1999 | 1 |
| 2000 | 6 |
| 2001 | 6 |
| 2002 | 3 |
| 2003 | 3 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 4 |
| 2007 | 5 |
| 2008 | 2 |
| 2009 | 6 |
| 2010 | 6 |
| 2011 | 5 |
| 2012 | 6 |
| 2013 | 4 |
| 2014 | 7 |
| 2015 | 4 |
| 2016 | 3 |
| 2017 | 2 |
| 2018 | 6 |
| 2019 | 2 |
| 2020 | 4 |
| 2021 | 4 |
| 2022 | 2 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 2 |
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\") = 2003
AND c.\"eventStateOrRegion\" = 'TX' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17032'))
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") = 2003
AND c."eventStateOrRegion" = 'TX' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17032'))
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 FTW03CA201Accident · No injuriesData collectionFinal reportCessna 210D · San Antonio, TXThe pilot's failure to comply with the checklist resulting in a wheels up landing. Contributing to the accident was self-induced pressure.NTSB FTW03LA129Accident · Minor injuriesLimited investigationFinal reportBeech V35B · Fort Worth, TXA loss of engine power due to corrosion and contamination of the fuel system, and the partially blocked fuel lines and nozzles.NTSB FTW03LA075Accident · No injuriesLimited investigationFinal reportCessna 401 · Mc Allen, TXThe pilot's failure to manually extend the landing gear to the full down and locked position. A contributing faction was a loss of electrical power, which resulted in the failure of the landing gear to extend.