NTSB investigations: Continental IO-520 series, 2005, CA
10 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
| 1965 | 10 |
|---|---|
| 1966 | 8 |
| 1967 | 17 |
| 1968 | 7 |
| 1969 | 8 |
| 1970 | 9 |
| 1971 | 6 |
| 1972 | 9 |
| 1973 | 13 |
| 1974 | 7 |
| 1975 | 11 |
| 1976 | 8 |
| 1977 | 17 |
| 1978 | 16 |
| 1979 | 23 |
| 1980 | 10 |
| 1981 | 7 |
| 1982 | 10 |
| 1983 | 9 |
| 1984 | 12 |
| 1985 | 4 |
| 1986 | 3 |
| 1987 | 2 |
| 1988 | 4 |
| 1989 | 3 |
| 1990 | 8 |
| 1991 | 4 |
| 1992 | 8 |
| 1993 | 3 |
| 1994 | 2 |
| 1995 | 9 |
| 1996 | 7 |
| 1997 | 7 |
| 1998 | 4 |
| 1999 | 4 |
| 2000 | 2 |
| 2001 | 3 |
| 2002 | 6 |
| 2003 | 3 |
| 2004 | 7 |
| 2005 | 10 |
| 2006 | 8 |
| 2007 | 6 |
| 2008 | 7 |
| 2009 | 7 |
| 2010 | 3 |
| 2011 | 4 |
| 2012 | 5 |
| 2013 | 4 |
| 2014 | 2 |
| 2015 | 2 |
| 2016 | 1 |
| 2017 | 8 |
| 2018 | 3 |
| 2019 | 5 |
| 2020 | 4 |
| 2021 | 2 |
| 2022 | 1 |
| 2023 | 3 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 5 |
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\") = 2005
AND c.\"eventStateOrRegion\" = 'CA' 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") = 2005
AND c."eventStateOrRegion" = 'CA' 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 LAX06FA075Accident · 3 fatalField investigationFinal reportBeech V35A · Valley Center, CAthe pilot's failure to maintain an adequate airspeed margin following a loss of engine power in the takeoff initial climb, resulting in a stall/spin. While the laboratory tests indicated the presence of an unknown biological contaminant in the fuel manifold…NTSB LAX06FA066Accident · 2 fatalField investigationFinal reportBeech 36 · Livermore, CAThe pilot's failure to maintain the appropriate glidepath alignment during an instrument landing system approach, resulting in collision with terrain. A contributing factor to the accident was the failure of the air traffic controllers to issue a minimum safe…NTSB LAX06LA065Accident · No injuriesLimited investigationFinal reportBeech F33A · La Verne, CAthe failure of the pilot of the other aircraft to comply with his air traffic control clearance and line up for the proper runway, and his failure to maintain an adequate visual lookout, which resulted in his in-flight collision with the Cessna airplane.NTSB LAX06FA031Accident · 1 fatalField investigationFinal reportBeech F33A · Geyserville, CAthe pilot's failure to maintain an adequate terrain clearance altitude profile during the descent that resulted in controlled flight into terrain.NTSB LAX06CA008Accident · No injuriesData collectionFinal reportBellanca 17-30A · Riverside, CAThe failure of the steering control rod during an unknown phase of the accident flight that resulted in the unavailability of steering control upon landing.NTSB LAX05LA317Accident · No injuriesLimited investigationFinal reportCessna A185F · Tracy, CAloss of engine power for undetermined reasons.NTSB LAX05CA287Accident · No injuriesData collectionFinal reportCessna A185E · San Andreas, CAthe pilot's failure to maintain directional control of the airplane upon encountering a dust devil during the takeoff roll.NTSB LAX05LA237Accident · No injuriesLimited investigationFinal reportCessna A188B · Bishop, CAthe failure of the tailwheel mount during the landing roll, which resulted in a ground loop.NTSB LAX05LA140Accident · Serious injuriesLimited investigationFinal reportBeech 35-C33A · Paso Robles, CAthe separation of the number 4 engine cylinder due to improperly torqued cylinder hold down nuts. A finding in this accident was the lack of a shoulder restraint system in the airplane, which contributed to the occupants' injuries.NTSB LAX05FA108Accident · No injuriesField investigationFinal reportCessna 210L · Oxnard, CAA pinhole leak in the fuel pressure line during the takeoff roll that was ignited by an electrical arc associated with wires adjacent to the fuel line. A contributing factor in the accident was the failure of maintenance personnel to comply with a…