NTSB investigations: Lycoming 0-320 series, 1999, UT
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 | 3 |
|---|---|
| 1965 | 2 |
| 1966 | 2 |
| 1967 | 2 |
| 1968 | 4 |
| 1969 | 5 |
| 1970 | 3 |
| 1971 | 2 |
| 1972 | 1 |
| 1973 | 1 |
| 1974 | 2 |
| 1975 | 4 |
| 1976 | 4 |
| 1977 | 1 |
| 1978 | 2 |
| 1979 | 3 |
| 1980 | 5 |
| 1981 | 3 |
| 1982 | 1 |
| 1984 | 2 |
| 1985 | 4 |
| 1986 | 4 |
| 1987 | 1 |
| 1988 | 4 |
| 1990 | 2 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 4 |
| 1994 | 2 |
| 1995 | 2 |
| 1996 | 3 |
| 1997 | 4 |
| 1998 | 3 |
| 1999 | 3 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 5 |
| 2003 | 2 |
| 2004 | 5 |
| 2006 | 2 |
| 2007 | 3 |
| 2008 | 5 |
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 1 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 2 |
| 2021 | 3 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 2 |
| 2025 | 1 |
| 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\") = 1999
AND c.\"eventStateOrRegion\" = 'UT' 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") = 1999
AND c."eventStateOrRegion" = 'UT' 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 DEN00LA014Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Bullfrog, UTThe pilot-in-command's failure to maintain directional control of the aircraft during landing roll. Factors were the pilot's lack of total experience in type of aircraft and the fence.NTSB DEN99FA120Accident · 4 fatalField investigationFinal reportPiper PA-22-150 · Roy, UTThe pilot inadvertently allowing the aircraft to enter a stall during initial climb following takeoff. Factors were high density altitude and gross weight which exceeded the maximum.NTSB DEN99LA082Accident · No injuriesLimited investigationFinal reportRich RV3-A · Bountiful, UTThe pilot's inadequate preflight planning, and the subsequent fuel exhaustion during the flight. Factor was the airplane's inaccurate fuel gauge.