NTSB investigations: Lycoming 0-320 series, 2004, SC
4 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 | 5 |
|---|---|
| 1965 | 1 |
| 1966 | 7 |
| 1967 | 3 |
| 1968 | 8 |
| 1969 | 4 |
| 1970 | 2 |
| 1971 | 4 |
| 1972 | 3 |
| 1973 | 4 |
| 1974 | 5 |
| 1975 | 4 |
| 1976 | 3 |
| 1977 | 2 |
| 1978 | 2 |
| 1979 | 2 |
| 1980 | 1 |
| 1981 | 1 |
| 1982 | 1 |
| 1983 | 2 |
| 1984 | 1 |
| 1985 | 3 |
| 1986 | 3 |
| 1987 | 6 |
| 1988 | 2 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 5 |
| 1992 | 3 |
| 1993 | 1 |
| 1994 | 4 |
| 1995 | 2 |
| 1997 | 6 |
| 1998 | 6 |
| 1999 | 2 |
| 2001 | 2 |
| 2002 | 4 |
| 2003 | 1 |
| 2004 | 4 |
| 2005 | 2 |
| 2006 | 1 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 5 |
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 5 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 2 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 3 |
| 2023 | 1 |
| 2024 | 1 |
| 2025 | 2 |
| 2026 | 1 |
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\") = 2004
AND c.\"eventStateOrRegion\" = 'SC' 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") = 2004
AND c."eventStateOrRegion" = 'SC' 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 ATL05CA019Accident · Serious injuriesData collectionFinal reportCessna 172N · Columbia, SCThe pilot's inadequate preflight planning of fuel required for the flight, which resulted in fuel exhaustion and subsequent loss of engine power.NTSB ATL04CA184Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Mount Pleasant, SCGround collision with an animal (deer) during an attempted takeoff.NTSB ATL04LA088Accident · No injuriesLimited investigationFinal reportCessna 172N · Columbia, SCThe pilot's inadequate in-flight planning/decision, which resulted in fuel exhaustion. The pilot's preflight planning and uneven terrain were contributing factors.NTSB ATL04LA074Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Summerville, SCThe pilot's inadequate start procedure, which resulted in a run-away airplane.