NTSB investigations: Lycoming IO-360-L2A, 2015
12 cases on aircraft whose registry engine model is Lycoming IO-360-L2A. 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
| 2001 | 2 |
|---|---|
| 2002 | 1 |
| 2003 | 7 |
| 2004 | 18 |
| 2005 | 13 |
| 2006 | 15 |
| 2007 | 22 |
| 2008 | 24 |
| 2009 | 20 |
| 2010 | 20 |
| 2011 | 21 |
| 2012 | 22 |
| 2013 | 14 |
| 2014 | 16 |
| 2015 | 12 |
| 2016 | 21 |
| 2017 | 24 |
| 2018 | 11 |
| 2019 | 14 |
| 2020 | 14 |
| 2021 | 20 |
| 2022 | 10 |
| 2023 | 15 |
| 2024 | 19 |
| 2025 | 13 |
| 2026 | 16 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41597'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41597'))
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 WPR16LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172S · San Jose, CAThe pilot's failure to maintain directional control during the landing roll at night, which resulted in a runway excursion.NTSB GAA16CA048Accident · No injuriesData collectionFinal reportCessna 172 · Mesa, AZThe pilot's failure to maintain pitch control during landing, resulting in a porpoise, and firewall damage.NTSB ERA16LA008Accident · 1 fatalLimited investigationFinal reportCessna 172S · Seville, FLThe airplane’s encounter with a downdraft, and the pilot's decision to maneuver the airplane at a low altitude and airspeed, which provided insufficient time and altitude to recover before impacting terrain.NTSB GAA15CA140Accident · No injuriesData collectionFinal reportCessna 172 - S · Traverse City, MIThe student pilot's failure to maintain pitch control during the landing, resulting in a hard landing.NTSB GAA15CA241Accident · No injuriesData collectionFinal reportCessna 172 · Upperville, VAAn inflight bird strike, which resulted in wing spar damage.NTSB GAA15CA179Accident · No injuriesData collectionFinal reportCessna 172R · Addison, TXThe student pilot's failure to maintain pitch control during the landing touchdown, resulting in a hard landing.NTSB WPR15FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172S · Davenport, CAUndetermined because the airplane was not located.NTSB GAA15CA064Accident · No injuriesData collectionFinal reportCessna 172S · Daytona Beach, FLThe landing airplane pilot's failure to maintain directional control during landing, which resulted in a runway excursion and ground collision with a taxiing airplane.NTSB GAA15CA046Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe pilot's failure to maintain airplane control, resulting in a hard landing.NTSB GAA15CA026Accident · No injuriesData collectionFinal reportCessna 172S · Vernal, UTThe student pilot's failure to maintain attitude control during landing flare.NTSB GAA15CA018Accident · No injuriesData collectionFinal reportCessna 172S · Camarillo, CAThe pilot involved and the phase of flight when the damage occurred were not determined.NTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.