NTSB investigations: Continental IO-360 series, 2006
13 cases on aircraft whose registry engine model is Continental IO-360 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 | 1 |
|---|---|
| 1965 | 11 |
| 1966 | 12 |
| 1967 | 17 |
| 1968 | 18 |
| 1969 | 16 |
| 1970 | 19 |
| 1971 | 15 |
| 1972 | 12 |
| 1973 | 12 |
| 1974 | 13 |
| 1975 | 20 |
| 1976 | 12 |
| 1977 | 17 |
| 1978 | 29 |
| 1979 | 20 |
| 1980 | 19 |
| 1981 | 13 |
| 1982 | 17 |
| 1983 | 10 |
| 1984 | 14 |
| 1985 | 12 |
| 1986 | 8 |
| 1987 | 11 |
| 1988 | 10 |
| 1989 | 10 |
| 1990 | 8 |
| 1991 | 9 |
| 1992 | 8 |
| 1993 | 13 |
| 1994 | 5 |
| 1995 | 11 |
| 1996 | 6 |
| 1997 | 9 |
| 1998 | 6 |
| 1999 | 9 |
| 2000 | 8 |
| 2001 | 12 |
| 2002 | 13 |
| 2003 | 12 |
| 2004 | 9 |
| 2005 | 17 |
| 2006 | 13 |
| 2007 | 6 |
| 2008 | 15 |
| 2009 | 12 |
| 2010 | 8 |
| 2011 | 11 |
| 2012 | 6 |
| 2013 | 9 |
| 2014 | 5 |
| 2015 | 8 |
| 2016 | 7 |
| 2017 | 6 |
| 2018 | 7 |
| 2019 | 11 |
| 2020 | 6 |
| 2021 | 3 |
| 2022 | 9 |
| 2023 | 7 |
| 2024 | 8 |
| 2025 | 8 |
| 2026 | 4 |
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\") = 2006
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17025', '17045'))
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") = 2006
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17025', '17045'))
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 DEN07FA022Accident · 1 fatalField investigationFinal reportCessna 337C · Alamogordo, NMThe pilot's incapacitation due to a heart attack while landing, which resulted in a loss of control and an on ground collision with objects.NTSB DEN06FA131Accident · 2 fatalField investigationFinal reportCirrus Design SR20 · Maybell, COThe pilot's improper in-flight planning and decision making resulting in an inadvertent encounter with severe icing conditions during cruise flight and subsequent loss of aircraft control. Contributing factors include the pilot's failure to obtain a weather…NTSB LAX06FA283Accident · 3 fatalField investigationFinal reportCessna 337G · Prescott, AZA loss of power in the rear engine for undermined reasons. Contributing to the accident was the pilot's failure to promptly and correctly configure the airplane for single engine flight, and to maintain an adequate airspeed, which resulted in a stall mush.NTSB CHI06CA279Accident · No injuriesData collectionFinal reportMeyers MAC-145 · Manistique, MIThe pilot not verifying the landing gear selector position prior to starting the taxi.NTSB LAX06LA232Accident · Minor injuriesLimited investigationFinal reportCessna R172K II · HagatnaThe failure of the number four connecting rod during takeoff-initial climb.NTSB CHI06LA212Accident · No injuriesLimited investigationFinal reportCessna R172K · Grand Rapids, MNThe pilot's failure to maintain control of the airplane during the landing. A factor associated with the accident was the gusty tailwind that prevailed.NTSB DEN06CA077Accident · No injuriesData collectionFinal reportCessna R172E (T-41C) · Albuquerque, NMthe pilot's failure to maintain aircraft control. A contributing factor was the wind gust.NTSB NYC06CA103Accident · No injuriesData collectionFinal reportMaule M-5-210C · Linville, VAThe pilot's improper decision to depart with a tailwind.NTSB DFW06LA101Accident · No injuriesLimited investigationFinal reportCirrus Design SR20 · Kerrville, TXThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for the forced landing.NTSB MIA06WA076Accident · 4 fatalForeign investigationCessna R172K · Cambita Garabit, Dominican RepublicNTSB MIA06LA067Accident · No injuriesLimited investigationFinal reportCirrus SR20 · Orlando, FLCatastrophic engine failure due to a low oil level brought about by excessive blow-by and cylinder detonation. Contributing factors in this accident were the inadequate instructions contained in Service Bulletin M89-9 and the ditch.NTSB DFW06LA060Accident · No injuriesLimited investigationFinal reportCessna 175 · Lindsay, OKThe hard landing was the result of the pilot's failure to maintain adequate airspeed while misjudging the altitude above the runway. Contributing factors were the inadequate quality of the manufacturer's engine-support bracket and the prevailing night…NTSB LAX06FA087Accident · 2 fatalField investigationFinal reportCirrus Design SR20 · Lancaster, CAThe student pilot's failure to maintain an adequate airspeed while maneuvering, and, the flight instructor's inadequate supervision of the flight. A factor in the accident was the strong tailwind encountered as the airplane turned from an upwind to a downwind…