NTSB investigations: Lycoming 0-320 series, 1992, OR
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 | 7 |
|---|---|
| 1965 | 10 |
| 1966 | 5 |
| 1967 | 6 |
| 1968 | 9 |
| 1969 | 6 |
| 1970 | 1 |
| 1971 | 6 |
| 1972 | 13 |
| 1973 | 9 |
| 1974 | 3 |
| 1975 | 6 |
| 1976 | 6 |
| 1977 | 5 |
| 1978 | 5 |
| 1979 | 9 |
| 1980 | 6 |
| 1981 | 5 |
| 1982 | 9 |
| 1983 | 2 |
| 1984 | 4 |
| 1985 | 2 |
| 1986 | 5 |
| 1987 | 3 |
| 1988 | 3 |
| 1989 | 4 |
| 1990 | 3 |
| 1991 | 4 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 4 |
| 1995 | 7 |
| 1996 | 6 |
| 1997 | 5 |
| 1998 | 3 |
| 1999 | 7 |
| 2000 | 5 |
| 2001 | 4 |
| 2002 | 4 |
| 2003 | 5 |
| 2004 | 8 |
| 2005 | 8 |
| 2006 | 5 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 4 |
| 2010 | 6 |
| 2011 | 2 |
| 2012 | 3 |
| 2014 | 1 |
| 2015 | 4 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 3 |
| 2022 | 5 |
| 2023 | 1 |
| 2024 | 2 |
| 2025 | 1 |
| 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\") = 1992
AND c.\"eventStateOrRegion\" = 'OR' 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") = 1992
AND c."eventStateOrRegion" = 'OR' 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 SEA93LA009Accident · Minor injuriesLimited investigationFinal reportMorrisey Shinn 2150A · Dallas, ORFailure to maintain airspeed. Factors include an improper fuel selector setting, and fuel starvation.NTSB SEA92LA166Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Sisters, ORThe improper use of flight controls by the PIC during an aborted takeoff. Factors relating to the accident were the unfavorable wind (windshift) encountered during takeoff ground roll, the tailwind and high da weather conditions.NTSB SEA92LA090Accident · No injuriesLimited investigationFinal reportCessna 172N · Parkdale, ORThe pilot's failure to use the proper touchdown point for landing. A factor relating to the accident was the soft dirt runway surface.NTSB SEA92LA035Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Newberg, ORA poorly planned final approach. Factors in the accident were: proper glidepath was not maintained and inadequate remedial action.