NTSB investigations: Lycoming 0-320 series, 2015, FL
11 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
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\") = 2015
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") = 2015
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 GAA16CA096Accident · No injuriesData collectionFinal reportCessna 172 · Punta Gorda, FLThe student pilot's failure to maintain obstacle clearance while taxiing on the ramp, resulting in a collision with an object.NTSB ERA16FA074Accident · 2 fatalField investigationFinal reportHinton Paul M RV 4 · Greenville, FLThe pilot's decision to initiate the flight into known adverse weather conditions, in an airplane that was not approved for instrument flight, which resulted in an encounter with instrument meteorological conditions and his subsequent spatial disorientation…NTSB GAA16CA073Accident · No injuriesData collectionFinal reportCessna 172N · Boca Raton, FLThe pilot's failure to maintain directional control during the landing touchdown resulting in a runway excursion, a collision with an object, and an impact with terrain.NTSB ERA16LA055Accident · Serious injuriesLimited investigationFinal reportRobinson R22 · Venice, FLThe flight instructor's failure to maintain control of the helicopter during an autorotation, which resulted in a hard landing.NTSB ERA16LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Miami Beach, FLA total loss of engine power for reasons that could not be determined because the airplane was not recovered from the ocean after the ditching.NTSB ERA15LA318Accident · No injuriesLimited investigationFinal reportCessna 172K · Chiefland, FLThe partial loss of engine power during cruise flight for reasons that could not be determined because a postaccident airframe and engine examination and engine test run revealed no evidence of mechanical malfunctions or failures.NTSB GAA15CA214Accident · No injuriesData collectionFinal reportCessna 172N · Miami, FLThe student pilot's failure to maintain pitch control resulting in a hard landing and damage to the airplane firewall.NTSB GAA15CA111Accident · No injuriesData collectionFinal reportCessna 177 · Clewiston, FLThe pilot's improper level off and flare in crosswind conditions, which resulted in a loss of control and hard landing.NTSB GAA15CA049Accident · No injuriesData collectionFinal reportCessna 172M · Clearwater, FLThe pilot's excessive airspeed during landing, which resulted in abnormal runway contact, a runway excursion, and substantial damage to the airplane.NTSB ERA15CA196Accident · No injuriesData collectionFinal reportCessna 172P · Sebastian, FLThe pilot's misjudged airspeed and glidepath, which resulted in a landing area overshoot and runway excursion.NTSB ERA15FA109Accident · 2 fatalField investigationFinal reportPiper PA-23 · Lakeland, FLAn in-flight loss of control for reasons that could not be determined during postaccident investigation; the loss of control likely occurred during a simulated loss of power in the right engine during an instructional flight.