NTSB investigations: Continental IO-360 series, 1993
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\") = 1993
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") = 1993
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 SEA94LA012Accident · No injuriesLimited investigationFinal reportCessna T-337E · Yamhill, ORThe pilot failed to attain the proper touchdown point. The tailwind was a factor.NTSB NYC94LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · Mt. Gilead, OHthe pilot's improper inflight decision to conduct a night landing at an airport without runway lights, and the subsequent misalignment with the runway and collision with an object.NTSB LAX94LA001Accident · No injuriesLimited investigationFinal reportCessna O-2A · Tucson, AZwas the partial loss of engine power during initial climb due to partial clogging of the engine's fuel injectors. Blockage of the fuel injectors was due to inadequate maintenance of the fuel system by contract maintenance personnel.NTSB BFO93FA178Accident · 1 fatalField investigationFinal reportMaule M-4-210C · Staunton, VAInadequate preflight by the pilot which resulted in inadequate altitude to clear the embankment during the initial climb. Factors in this accident were a tailwind on takeoff and rising terrain at the departure end of the grass airstrip.NTSB SEA93LA160Accident · Serious injuriesLimited investigationFinal reportCessna 337 · Jerome, IDThe pilot's improper fuel management procedures which resulted in fuel starvation. Factors include the pilot's lack of familiarity with this type aircraft, and rough/uneven terrain in the landing area.NTSB CHI93LA258Accident · No injuriesLimited investigationFinal reportMaule M4 · Tomahawk, WIthe pilot's improper recovery from a bounced landing.NTSB DEN93LA078Accident · No injuriesLimited investigationFinal reportCessna 172XP · Allen, TXFuel exhaustion induced power loss. A factor was the lack of suitable terrain for the forced landing.NTSB ANC93LA109Accident · No injuriesLimited investigationFinal reportMaule M4 · Iliamna, AKThe pilot in command's improper taxi speed. A factor in the accident was the rough water.NTSB CHI93LA229Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Point Lookout, MOThe pilot in command's failure to maintain proper glide path, and her failure to attain the proper touch down Point.NTSB SEA93LA114Accident · No injuriesLimited investigationFinal reportMaule M-4-210C · Moscow, IDThe inadequate visual lookout by the pilot and his failure to maintain clearance from electrical transmission wires. Factors relating to the accident were the sunglare and the presence of the wires.NTSB ANC93LA065Accident · No injuriesLimited investigationFinal reportCessna 172K · Rohn Roadhouse, AKThe pilot in command's inadequate compensation for the wind conditions and allowing the airspeed to go below stalling speed in the landing configuration.NTSB NYC93LA092Accident · No injuriesLimited investigationFinal reportCessna P337 · Holland, VAThe pilot's improper inflight planning during the approach for landing, resulting in a touchdown too FAR down the runway, and the subsequent collision with objects off the end of the runway.NTSB ATL93FA060Accident · Serious injuriesField investigationFinal reportCessna 337D · Nashville, TNThe pilot's failure to ensure an adequate fuel supply for the flight, which resulted in fuel exhaustion.