NTSB investigations: Lycoming O&VO-360 series, 2002, FL
3 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 | 4 |
|---|---|
| 1965 | 10 |
| 1966 | 12 |
| 1967 | 7 |
| 1968 | 8 |
| 1969 | 5 |
| 1970 | 5 |
| 1971 | 8 |
| 1972 | 5 |
| 1973 | 7 |
| 1974 | 9 |
| 1975 | 3 |
| 1976 | 3 |
| 1977 | 7 |
| 1978 | 7 |
| 1979 | 8 |
| 1980 | 6 |
| 1981 | 10 |
| 1982 | 3 |
| 1983 | 5 |
| 1984 | 3 |
| 1985 | 7 |
| 1986 | 7 |
| 1987 | 4 |
| 1988 | 8 |
| 1989 | 2 |
| 1990 | 6 |
| 1992 | 2 |
| 1993 | 8 |
| 1994 | 5 |
| 1995 | 4 |
| 1996 | 4 |
| 1997 | 4 |
| 1998 | 9 |
| 1999 | 6 |
| 2000 | 3 |
| 2001 | 11 |
| 2002 | 3 |
| 2003 | 6 |
| 2004 | 6 |
| 2005 | 6 |
| 2006 | 5 |
| 2007 | 6 |
| 2008 | 6 |
| 2009 | 5 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 4 |
| 2014 | 6 |
| 2015 | 4 |
| 2016 | 4 |
| 2017 | 8 |
| 2018 | 3 |
| 2019 | 4 |
| 2020 | 3 |
| 2021 | 4 |
| 2022 | 3 |
| 2023 | 2 |
| 2024 | 3 |
| 2025 | 6 |
| 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\") = 2002
AND c.\"eventStateOrRegion\" = 'FL' 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") = 2002
AND c."eventStateOrRegion" = 'FL' 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 ATL02FA162Accident · 2 fatalField investigationFinal reportAmerican General AA-5B · Zephyrhills, FLThe pilots continued visual flight into instrument conditions (fog), and subsequent collision with a tree and a residence.NTSB ATL02LA085Accident · Minor injuriesLimited investigationFinal reportPitts S1C · Gainesville, FLThe pilot's failure to maintain clearance from the ground during an attempted go-around.NTSB ATL02FA051Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Vero Beach, FLThe flight's encounter with isolated severe to extreme turbulence that resulted in an in-flight breakup of the airplane and subsequent impact with terrain.