NTSB investigations: Continental IO-360 series, 2003
12 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
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.\"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") = 2003
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 DEN04LA029Accident · No injuriesLimited investigationFinal reportMaule M-4-210 · Elbert, COthe pilot's failure to maintain directional control of the airplane. A contributing factor was his inexperience in aircraft type.NTSB DEN03LA140Accident · No injuriesLimited investigationFinal reportCessna 337F · Las Cruces, NMLack of adequate power from the rear engine for undetermined reasons and the pilot's failure to maintain aircraft control during take-off. A contributing factor to the accident was the low altitude.NTSB SEA03CA162Accident · No injuriesData collectionFinal reportCessna R172K · Idaho Falls, IDThe pilot's failure to see and avoid a parked aircraft while taxiing.NTSB SEA03LA137Accident · Serious injuriesLimited investigationFinal reportCirrus Design SR-20 · Fish Haven, IDThe pilot's failure to maintain terrain clearance while maneuvering. Rising terrain, an inadvertent raising of the flaps for unknown reasons, and low altitude were factors.NTSB LAX03CA219Accident · No injuriesData collectionFinal reportStinson 108-3 · St. Johns, AZthe pilot's inadequate compensation for the gusting and shifting wind conditions, which resulted in a failure to maintain directional control and a ground loop. The gusting and shifting wind conditions were factors in the accident.NTSB ANC03FA061Accident · 2 fatalField investigationFinal reportCessna 172 · Skagway, AKThe pilot's continued visual flight into instrument meteorological conditions, which resulted in an in-flight collision with mountainous terrain. Factors associated with the accident were low ceilings, rain, and fog.NTSB DEN03TA103Accident · No injuriesFinal reportCessna R172E · Albuquerque, NMthe student pilot's inadvertent encounter with the jet blast and the subsequent inability to maintain aircraft control.NTSB CHI03LA135Accident · No injuriesLimited investigationFinal reportCessna R172K · Kirksville, MOThe pilot's improper in-flight decision to land with a tailwind and failure to perform an aborted landing, resulting in the pilots decision to control the aircraft off of the right edge of the runway to avoid obstructions. Contributing factors were the…NTSB NYC03LA091Accident · No injuriesLimited investigationFinal reportCessna 172K · Burnham, PAThe pilot's failure to maintain directional control during the takeoff roll.NTSB CHI03LA110Accident · No injuriesLimited investigationFinal reportMaule M-5-210C · Ironwood, MIThe pilot's inadvertent ground loop on landing. A contributing factor was the ditch.NTSB IAD03LA036Accident · 1 fatalLimited investigationFinal reportCessna R172K · Richmond, VAThe passenger's failure to remain clear of the propeller. Factors included the passenger's recent use of marijuana, the pilot's inadequate pre-flight inspection, and the night lighting conditions.NTSB SEA03FA026Accident · No injuriesField investigationFinal reportCessna 172K · Gig Harbor, WAThe loss of engine power in the climb due to the fracture of the number seven engine crankshaft cheek due to the propagation of a fatigue crack initiation point. Factors include a vehicle pulling onto the road that the pilot selected for his forced emergency…