NTSB investigations: Lycoming 0-320 series, 2000, CO
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 | 6 |
| 1966 | 9 |
| 1967 | 9 |
| 1968 | 15 |
| 1969 | 14 |
| 1970 | 15 |
| 1971 | 10 |
| 1972 | 6 |
| 1973 | 9 |
| 1974 | 14 |
| 1975 | 9 |
| 1976 | 11 |
| 1977 | 10 |
| 1978 | 12 |
| 1979 | 10 |
| 1980 | 8 |
| 1981 | 9 |
| 1982 | 7 |
| 1983 | 10 |
| 1984 | 6 |
| 1985 | 6 |
| 1986 | 2 |
| 1987 | 6 |
| 1988 | 9 |
| 1989 | 7 |
| 1990 | 6 |
| 1991 | 13 |
| 1992 | 8 |
| 1993 | 5 |
| 1994 | 5 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 9 |
| 1998 | 7 |
| 1999 | 10 |
| 2000 | 4 |
| 2001 | 7 |
| 2002 | 11 |
| 2003 | 3 |
| 2004 | 8 |
| 2005 | 3 |
| 2006 | 5 |
| 2007 | 5 |
| 2008 | 6 |
| 2009 | 3 |
| 2010 | 2 |
| 2011 | 2 |
| 2012 | 3 |
| 2013 | 5 |
| 2014 | 3 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 10 |
| 2019 | 1 |
| 2020 | 4 |
| 2021 | 2 |
| 2022 | 2 |
| 2023 | 1 |
| 2024 | 4 |
| 2025 | 5 |
| 2026 | 3 |
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\") = 2000
AND c.\"eventStateOrRegion\" = 'CO' 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") = 2000
AND c."eventStateOrRegion" = 'CO' 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 DEN01LA034Accident · No injuriesLimited investigationFinal reportBarackman Vans RV-6 · Springfield, COTotal failure of the right hand flap control rod due to construction procedures/directives not being followed by the builder.NTSB DEN01LA024Accident · No injuriesLimited investigationFinal reportCessna 172P · Leadville, COthe student pilot's failure to maintain directional control during landing roll. A contributing factor was the snow bank next to the runway.NTSB DEN00LA129Accident · No injuriesLimited investigationFinal reportCessna 172N · Durango, COThe pilot prematurely flaring the airplane for landing, resulting in a hard landing, followed by an inadvertent pilot-induced porpoise and loss of directional control. A factor was the fence.NTSB DEN00LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Collins, COOn ground loss of control resulting in collision with airport markings due to inadequate compensation for wind conditions during landing roll. Factors were inaccurate in flight planning by landing with a tail wind component and lack of total pilot experience.