NTSB investigations: Lycoming 0-320 series, 1995, FL
10 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 | 8 |
| 1966 | 17 |
| 1967 | 16 |
| 1968 | 16 |
| 1969 | 11 |
| 1970 | 15 |
| 1971 | 18 |
| 1972 | 13 |
| 1973 | 9 |
| 1974 | 15 |
| 1975 | 16 |
| 1976 | 11 |
| 1977 | 18 |
| 1978 | 16 |
| 1979 | 19 |
| 1980 | 21 |
| 1981 | 20 |
| 1982 | 17 |
| 1983 | 10 |
| 1984 | 15 |
| 1985 | 15 |
| 1986 | 15 |
| 1987 | 11 |
| 1988 | 11 |
| 1989 | 11 |
| 1990 | 10 |
| 1991 | 11 |
| 1992 | 16 |
| 1993 | 10 |
| 1994 | 13 |
| 1995 | 10 |
| 1996 | 11 |
| 1997 | 14 |
| 1998 | 12 |
| 1999 | 13 |
| 2000 | 18 |
| 2001 | 15 |
| 2002 | 12 |
| 2003 | 15 |
| 2004 | 19 |
| 2005 | 14 |
| 2006 | 13 |
| 2007 | 6 |
| 2008 | 16 |
| 2009 | 14 |
| 2010 | 6 |
| 2011 | 13 |
| 2012 | 9 |
| 2013 | 10 |
| 2014 | 11 |
| 2015 | 11 |
| 2016 | 13 |
| 2017 | 9 |
| 2018 | 19 |
| 2019 | 16 |
| 2020 | 10 |
| 2021 | 13 |
| 2022 | 11 |
| 2023 | 9 |
| 2024 | 10 |
| 2025 | 10 |
| 2026 | 11 |
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\") = 1995
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 ('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") = 1995
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 ('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 MIA96LA044Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bryceville, FLThe pilot's improper planning/decision. Factors relating to the accident were: the pilot's inaccurate evaluation of the weather conditions, the pilot becoming lost/disoriented, and the lack of braking action on wet grass during the precautionary landing.NTSB MIA96LA027Accident · No injuriesLimited investigationFinal reportPiper PA-23-150 · Ocala, FLThe failure of the pilot-in-command (CFI) of the Cessna, N210PW, to see and avoid the Piper, N2114P.NTSB MIA96LA021Accident · Serious injuriesLimited investigationFinal reportLynch Starduster SA-300 · Ormond Beach, FLThe pilot's failure to maintain adequate airspeed and control of the airplane resulting in an inadvertent stall and collision with the ground.NTSB MIA95LA235Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe failure of the pilot to maintain directional control during landing. Contributing to the accident was the crosswind.NTSB MIA95LA165Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lake Placid, FLTotal failure of the fuel vent system resulting in the total loss of engine power during cruise flight. Contributing to the accident was the inadequate inspection of the airplane during the last annual inspection for failure of the mechanic to identify that…NTSB MIA95LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Clearwater, FLThe pilot-in-command's improper remedial action after the aircraft porpoised during the landing flare and touchdown.NTSB MIA95LA108Accident · No injuriesLimited investigationFinal reportCessna 172M · Panacea, FLThe pilot's failure to attain the proper touchdown point during a forced landing to a runway. This resulted in the airplane rolling off the departure end of the runway, and subsequent on ground collision with a fence and a telephone booth. Contributing to the…NTSB MIA95FA105Accident · 1 fatalField investigationFinal reportPackard/Squire RV-4 · Davie, FLEngine fuel starvation due to the pilot's fuel mismanagement. A loss of control followed as the pilot inadvertently stalled the airplane while maneuvering for the forced landing.NTSB MIA95FA094Accident · 2 fatalField investigationFinal reportCessna 172N · Venice, FLIntentional VFR flight into IMC by the pilot-in-command, failure of the pilot to maintain aircraft control, spatial disorientation, and altitude inadequate for recovery following the in flight loss of control.NTSB MIA95LA090Accident · No injuriesLimited investigationFinal reportCessna 177 · Miami, FLThe pilot-in-command's/CFI improper supervision of the dual student during a simulated short field approach for landing. This resulted in an in-flight loss of control (inadvertent stall), and subsequent hard landing.