NTSB investigations: Lycoming IO-320 series, 1997
5 cases on aircraft whose registry engine model is Lycoming IO-320 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 | 17 |
|---|---|
| 1965 | 21 |
| 1966 | 34 |
| 1967 | 35 |
| 1968 | 25 |
| 1969 | 20 |
| 1970 | 33 |
| 1971 | 28 |
| 1972 | 34 |
| 1973 | 32 |
| 1974 | 27 |
| 1975 | 21 |
| 1976 | 20 |
| 1977 | 19 |
| 1978 | 36 |
| 1979 | 19 |
| 1980 | 22 |
| 1981 | 17 |
| 1982 | 17 |
| 1983 | 13 |
| 1984 | 18 |
| 1985 | 12 |
| 1986 | 15 |
| 1987 | 18 |
| 1988 | 10 |
| 1989 | 11 |
| 1990 | 9 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 5 |
| 1994 | 3 |
| 1995 | 5 |
| 1996 | 10 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 9 |
| 2000 | 11 |
| 2001 | 11 |
| 2002 | 13 |
| 2003 | 13 |
| 2004 | 10 |
| 2005 | 8 |
| 2006 | 12 |
| 2007 | 15 |
| 2008 | 10 |
| 2009 | 13 |
| 2010 | 10 |
| 2011 | 13 |
| 2012 | 7 |
| 2013 | 10 |
| 2014 | 10 |
| 2015 | 7 |
| 2016 | 4 |
| 2017 | 8 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 10 |
| 2021 | 9 |
| 2022 | 10 |
| 2023 | 9 |
| 2024 | 5 |
| 2025 | 6 |
| 2026 | 6 |
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\") = 1997
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509'))
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") = 1997
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509'))
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 CHI98LA072Accident · 1 fatalLimited investigationFinal reportPiper PA-30/A · Hastings, NEThe pilot's improper IFR procedure, by which he failed to maintain minimum descent altitude. Fog, a low ceiling, and night condition were a contributing factor.NTSB FTW97LA368Accident · No injuriesLimited investigationFinal reportBellanca 7KCAB · Englewood, COfailure of the right main landing gear due to multiple fatigue cracks.NTSB LAX97LA310Accident · No injuriesLimited investigationFinal reportBingelis Falco F.8L · Watsonville, CAthe pilot's misjudgment of distance and speed on final approach, leading to a landing undershoot.NTSB CHI97LA247Accident · No injuriesLimited investigationFinal reportChampion 7KCAB · Hampshire, ILthe pilot's failure to maintain directional control of the airplane during landing, and his excessive use of brakes, which resulted in a nose over. Factors relating to the accident were: the crosswind condition, and the pilot's lack of experience in the make…NTSB MIA97LA080Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Sarasota, FLthe pilot's failure to maintain clearance from obstacles.