NTSB investigations: Continental IO-360 series, 1989
10 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\") = 1989
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") = 1989
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 FTW90LA014Accident · No injuriesLimited investigationFinal reportCessna T-337G-P · Laredo, TXDouble engine failure due to fuel exhaustion. The fuel exhaustion was caused by incorrect inflight fuel consumption calculations and one inaccurate fuel quanity gauge. Contributing to the accident was the dark night restriction to visibility.NTSB FTW89LA162Accident · No injuriesLimited investigationFinal reportCessna 172K · Midlothian, TXThe failure of the pilot to compensate for the crosswind condition, which resulted in a loss of directional control and collision with a tree.NTSB CHI89LA172Accident · No injuriesLimited investigationFinal reportCessna T-337D · Howell, MIThe pilot's poor preflight planning and inaccurate fuel consumption calculations. Contributing factor was maintenance personnel's not performing correct calibration of fuel gages.NTSB ANC89LA181Accident · 4 fatalLimited investigationFinal reportCessna R172K · Anchorage, AKUndetermined.NTSB SEA89LA142Accident · No injuriesLimited investigationFinal reportCessna 172E · Yerington, NVThe pilot's failure to maintain adequate airspeed during a landing go-around in high density altitude conditions.NTSB FTW89FA073Accident · 4 fatalField investigationFinal reportCessna 172XP · Hondo, TXThe pilot's decision to depart into known adverse weather and his lack of instrument training and experience.NTSB NYC89LA109Accident · No injuriesLimited investigationFinal reportCessna 172XP · Vineland, NJThe pilot's misjudgement of speed & distance during landing which resulted in the proper touchdown point to be exceeded. The runway conditions were contributing factors.NTSB NYC89LA098Accident · Minor injuriesLimited investigationFinal reportCessna 337 · Bethel, NYImproper planning/decision by the pilot concerning his fuel management, which resulted in fuel exhaustion due to an inadequate supply of fuel. The false indication from the fuel quantity gage(s), dark night, and trees were considered to be factors.NTSB LAX89LA079Accident · No injuriesLimited investigationFinal reportMaule M-5-210C · Calexico, CAA binding brake system torque plate. Factors related to the accident were: inadequate maintenance by other maintenance personnel, and operation of the airplane with a known efficiency by the pilot.NTSB MIA89LA061Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Margate, FLFailure of the engine driven oil pump due to foreign object(s), which resulted in oil starvation and subsequent engine failure. Factors related to the accident were: dark night and trees in the emergency landing area.