NTSB investigations: Lycoming O&VO-360 series, 1997, CA
4 cases on aircraft whose registry engine model is Lycoming O&VO-360 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 | 21 |
|---|---|
| 1965 | 21 |
| 1966 | 28 |
| 1967 | 26 |
| 1968 | 13 |
| 1969 | 12 |
| 1970 | 11 |
| 1971 | 18 |
| 1972 | 10 |
| 1973 | 7 |
| 1974 | 12 |
| 1975 | 9 |
| 1976 | 9 |
| 1977 | 10 |
| 1978 | 17 |
| 1979 | 11 |
| 1980 | 12 |
| 1981 | 11 |
| 1982 | 10 |
| 1983 | 10 |
| 1984 | 10 |
| 1985 | 13 |
| 1986 | 13 |
| 1987 | 10 |
| 1988 | 5 |
| 1989 | 7 |
| 1990 | 5 |
| 1991 | 5 |
| 1992 | 2 |
| 1993 | 7 |
| 1994 | 4 |
| 1995 | 7 |
| 1996 | 6 |
| 1997 | 4 |
| 1998 | 8 |
| 1999 | 6 |
| 2000 | 10 |
| 2001 | 7 |
| 2002 | 10 |
| 2003 | 13 |
| 2004 | 10 |
| 2005 | 15 |
| 2006 | 15 |
| 2007 | 5 |
| 2008 | 9 |
| 2009 | 2 |
| 2010 | 6 |
| 2011 | 3 |
| 2012 | 4 |
| 2013 | 7 |
| 2014 | 2 |
| 2015 | 5 |
| 2016 | 6 |
| 2017 | 2 |
| 2018 | 8 |
| 2019 | 2 |
| 2020 | 3 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 4 |
| 2024 | 1 |
| 2025 | 4 |
| 2026 | 1 |
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\") = 1997
AND c.\"eventStateOrRegion\" = 'CA' 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 ('41514'))
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") = 1997
AND c."eventStateOrRegion" = 'CA' 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 ('41514'))
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 LAX98LA035Accident · No injuriesLimited investigationFinal reportBeech C23 · Corona, CAThe loss of engine power for undetermined reasons. A factor was the rough terrain that resulted in a nose over during the landing roll.NTSB LAX97FA328Accident · 4 fatalField investigationFinal reportBeech C23 · Torrance, CAThe failure of the pilot to attain and maintain adequate airspeed during the initial takeoff climb, which resulted in a stall/spin and subsequent collision with a building.NTSB LAX97LA314Accident · Serious injuriesLimited investigationFinal reportHallam RV-6 · Woodlake, CAfailure of the pilot to accurately determine the quantity of fuel onboard the airplane before flight, and subsequent loss of engine power due to fuel starvation, which resulted in a forced landing.NTSB LAX97LA095Accident · No injuriesLimited investigationFinal reportCessna 172RG · Corona, CAFailure of the pilot in command to follow the airplane's before landing checklist and verify the landing gear was fully extended before landing. Factors in the accident were anxiety and diversion of the pilot's attention due to fuel gauge readings.