NTSB investigations: Lycoming 0-320 series, 2001, NC
3 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 | 5 |
| 1967 | 6 |
| 1968 | 5 |
| 1969 | 4 |
| 1970 | 3 |
| 1971 | 13 |
| 1972 | 10 |
| 1973 | 8 |
| 1974 | 11 |
| 1975 | 9 |
| 1976 | 3 |
| 1977 | 3 |
| 1978 | 8 |
| 1979 | 7 |
| 1980 | 3 |
| 1981 | 7 |
| 1982 | 2 |
| 1983 | 6 |
| 1984 | 3 |
| 1985 | 2 |
| 1986 | 5 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 7 |
| 1990 | 3 |
| 1991 | 1 |
| 1992 | 3 |
| 1993 | 5 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 4 |
| 1999 | 1 |
| 2000 | 5 |
| 2001 | 3 |
| 2002 | 7 |
| 2003 | 5 |
| 2004 | 3 |
| 2005 | 1 |
| 2006 | 4 |
| 2007 | 4 |
| 2008 | 3 |
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 4 |
| 2020 | 4 |
| 2021 | 3 |
| 2022 | 1 |
| 2023 | 4 |
| 2024 | 6 |
| 2025 | 1 |
| 2026 | 5 |
Where
Latest 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\") = 2001
AND c.\"eventStateOrRegion\" = 'NC' 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") = 2001
AND c."eventStateOrRegion" = 'NC' 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 ATL02LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Goldsboro, NCThe student pilot's failure to maintain directional control during a touch-and-go landing.NTSB MIA01LA219Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Wilgrove, NCThe failure of maintenance personal to properly reconnect the throttle-cable-to carburetor attachment, resulting in a throttle cable disconnection while in the landing pattern, and collision with trees. A factor in the accident was the failure of the pilot to…NTSB MIA01LA125Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Chapel Hill, NCThe loss of engine power for undetermined reasons during takeoff, resulting in an inflight collision with trees during the subsequent emergency landing. A factor in the accident was the lack of suitable terrain to conduct an emergency landing.