NTSB investigations: Lycoming 0-320 series, 2017, FL
9 cases on aircraft whose registry engine model is Lycoming 0-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 | 7 |
|---|---|
| 1965 | 8 |
| 1966 | 17 |
| 1967 | 16 |
| 1968 | 16 |
| 1969 | 11 |
| 1970 | 15 |
| 1971 | 18 |
| 1972 | 13 |
| 1973 | 9 |
| 1974 | 15 |
| 1975 | 16 |
| 1976 | 11 |
| 1977 | 18 |
| 1978 | 16 |
| 1979 | 19 |
| 1980 | 21 |
| 1981 | 20 |
| 1982 | 17 |
| 1983 | 10 |
| 1984 | 15 |
| 1985 | 15 |
| 1986 | 15 |
| 1987 | 11 |
| 1988 | 11 |
| 1989 | 11 |
| 1990 | 10 |
| 1991 | 11 |
| 1992 | 16 |
| 1993 | 10 |
| 1994 | 13 |
| 1995 | 10 |
| 1996 | 11 |
| 1997 | 14 |
| 1998 | 12 |
| 1999 | 13 |
| 2000 | 18 |
| 2001 | 15 |
| 2002 | 12 |
| 2003 | 15 |
| 2004 | 19 |
| 2005 | 14 |
| 2006 | 13 |
| 2007 | 6 |
| 2008 | 16 |
| 2009 | 14 |
| 2010 | 6 |
| 2011 | 13 |
| 2012 | 9 |
| 2013 | 10 |
| 2014 | 11 |
| 2015 | 11 |
| 2016 | 13 |
| 2017 | 9 |
| 2018 | 19 |
| 2019 | 16 |
| 2020 | 10 |
| 2021 | 13 |
| 2022 | 11 |
| 2023 | 9 |
| 2024 | 10 |
| 2025 | 10 |
| 2026 | 11 |
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\") = 2017
AND c.\"eventStateOrRegion\" = 'FL' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508'))
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") = 2017
AND c."eventStateOrRegion" = 'FL' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508'))
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 WPR18LA040Accident · Minor injuriesLimited investigationFinal reportPiper PA-28 · Odessa, FLA loss of engine power due to fuel starvation as a result of the pilot's inadequate planning and in-flight fuel management. Contributing to the accident was the pilot’s failure to follow proper procedures after the loss of engine power.NTSB GAA18CA064Accident · No injuriesData collectionFinal reportCessna 172 · Pompano, FLThe pilot’s improper landing flare, which resulted in a porpoise.NTSB ERA17LA242Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Key Biscayne, FLThe nearly complete blockage of the right fuel tank strainer with organic material, which resulted in fuel starvation and the subsequent total loss of engine power. Contributing to the fuel starvation was the pilot receiving instruction’s and the flight…NTSB GAA17CA348Accident · No injuriesData collectionFinal reportPiper PA 16 · Palatka, FLThe pilot’s failure to maintain directional control during the landing.NTSB ERA17CA208Accident · No injuriesData collectionFinal reportPiper PA23 · Cedar Key, FLThe pilot's failure to stop the airplane within the available runway after conducting the approach and landing with a tailwind.NTSB ERA17LA160Accident · No injuriesLimited investigationFinal reportCessna 172 · Yankeetown, FLA total loss of engine power for reasons that could not be determined because postaccident examination of the engine revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation.NTSB ERA17LA128Accident · No injuriesLimited investigationFinal reportPiper PA28 · Tampa, FLA collapsed engine induction duct, which resulted in restricted air flow to the engine and a subsequent loss of engine power. Contributing to the accident was the operator's failure to ensure that the correct induction duct was installed.NTSB GAA17CA180Accident · No injuriesData collectionFinal reportCessna 172 · Naples, FLThe pilot’s failure to maintain pitch control, which resulted in a hard landing.NTSB GAA17CA111Accident · No injuriesData collectionFinal reportCessna 172 · Hollywood, FLThe student pilot’s improper landing flare in gusting crosswind conditions, which resulted in a hard landing.