NTSB investigations: Continental IO-360 series, 2002
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
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\") = 2002
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") = 2002
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 DEN03LA022Accident · No injuriesLimited investigationFinal reportMaule M-4-210 · Creede, COthe pilot's inadequate compensation for wind. Contributing factors are the crosswind and the pilot's lack of experience.NTSB NYC03LA007Accident · Minor injuriesLimited investigationFinal reportCirrus Design SR-20 · Point Pleasant, WVAn inadvertent collision with wildlife. A factor in the accident was wildlife having access to the runway environment.NTSB SEA02LA181Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Shaw Island, WAThe pilot's failure to adequately compensate for ambient wind conditions. Factors include the pilot's misjudgment of distance/altitude, gusting crosswinds, and trees growing near the edge of the airstrip.NTSB SEA02LA179Accident · No injuriesLimited investigationFinal reportCessna R172K · Salmon, IDFailure to maintain airspeed while on approach which resulted in an aerodynamic stall and hard landing.NTSB MIA02LA165Accident · Serious injuriesLimited investigationFinal reportCessna T337D · Fort Pierce, FLThe pilot's misjudgment of the fuel supply, and subsequent fuel exhaustion.NTSB DEN02LA087Accident · No injuriesLimited investigationFinal reportCessna R172K · Monticello, UTthe student pilot's failure to maintain aircraft control during landing flare, which resulted in a hard landing. Contributing factors include the porpoise and subsequent bounced landing and the student pilot's lack of total experience.NTSB CHI02LA220Accident · No injuriesLimited investigationFinal reportCessna R172K · Flushing, MIA loss of engine power for undetermined reasons. Contributing to the accident was the wet runway.NTSB LAX02TA207Accident · No injuriesFinal reportCessna 337C · Big Bear City, CAThe loss of engine power due to fuel starvation.NTSB FTW02LA182Accident · No injuriesLimited investigationFinal reportCessna R172K · Llano, TXthe pilot's failure to refuel the airplane, which resulted in fuel exhaustion and a forced landing.NTSB NYC02LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-200 · Gettysburg, PAThe pilot's failure to accurately compute takeoff performance and his failure to establish a positive climb resulting in a collision with trees.NTSB LAX02LA145Accident · No injuriesLimited investigationFinal reportMaule M-4-210C · Reno, NVThe inadvertent activation of the parking brake and locking of the right brake. A contributing factor was the pilot's operation of the aircraft with a known malfunction of the right brake system.NTSB MIA02LA085Accident · 1 fatalLimited investigationFinal reportGrote Cruiser TR-4 · Pembroke Pines, FLthe pilot-in-command delayed initiating a go-around and failed to obtain sufficient altitude to clear obstacles at the departure end of the airport which resulted in an in-flight collision with power lines.NTSB MIA02LA057Accident · Serious injuriesLimited investigationFinal reportCessna R172E · River Ranch, FLThe reported loss of engine power due to undetermined reasons. Contributing factors in the accident were an improper flap setting, excessive landing speed, and terrain consisting of berms.