NTSB investigations: Lycoming IO-360-L2A, 2017
24 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\") = 2017
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") = 2017
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 GAA18CA085Accident · No injuriesData collectionFinal reportCessna 172 · Park Rapids, MNThe student pilot’s improper landing flare, which resulted in the propeller striking the ground.NTSB GAA18CA046Accident · No injuriesData collectionFinal reportTextron 172 · Columbus, OHThe student pilot’s improper landing flare, which resulted in a porpoise.NTSB GAA18CA045Accident · No injuriesData collectionFinal reportCessna 172 · Trenton, NJThe pilot’s improper landing flare, which resulted in a bounced landing.NTSB GAA18CA044Accident · No injuriesData collectionFinal reportCessna 172 · Bonners Ferry, IDThe pilot’s failure to see and avoid power lines while maneuvering at a low altitude.NTSB WPR18LA039Accident · No injuriesClass 3 · LimitedFinal reportCessna 172R · Redding, CAThe fatigue separation of the crankshaft due to a fatigue fracture, which resulted in a total loss of engine power and a subsequent off-airport landing and impact with a fence.NTSB WPR18LA002Accident · No injuriesLimited investigationFinal reportCessna 172S · Tonopah, NVThe pilot's failure to enrich the mixture during the descent, as required by the Pilot's Operating Handbook (POH), and his subsequent failure to follow the POH emergency procedures, which resulted in an excessively lean fuel/air mixture and subsequent loss of…NTSB GAA17CA573Accident · No injuriesData collectionFinal reportCessna 172 · Chino, CAAn in-flight collision with a bird while on downwind.NTSB CEN17LA311Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Wellston, OHThe failure of a connecting rod small end bushing, which resulted in a loss of engine power.NTSB GAA17CA482Accident · No injuriesData collectionFinal reportCessna 172 · Kearney, NEThe pilot’s failure to maintain directional control of the airplane during the landing roll, which resulted in a runway excursion.NTSB GAA17CA470Accident · No injuriesData collectionFinal reportCessna 172 · Carlsbad, CAThe student pilot’s improper landing flare in gusting wind conditions.NTSB ERA17LA261Accident · 1 fatalLimited investigationFinal reportCessna 172 · Danbury, CTThe pilot's exceedance of the airplane's critical angle of attack during initial climb, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's decision to operate the airplane above its maximum gross weight, which likely reduced…NTSB GAA17CA479Accident · No injuriesData collectionFinal reportCessna 172 · Santa Ana, CAA hard landing and propeller strike for reasons that could not be determined based on the available evidence.NTSB GAA17CA389Accident · No injuriesData collectionFinal reportCessna 172 · Shreveport, LAThe student’s improper landing flare, which resulted in a hard landing.NTSB GAA17CA337Accident · No injuriesData collectionFinal reportCessna 172 · Ravenna, OHThe flight instructor's failure to perform a go-around during final approach, which resulted in an aerodynamic stall and a hard landing. Contributing to the accident was the flight instructor's failure to brief the student pilot on the positive transfer of…NTSB GAA17CA351Accident · No injuriesData collectionFinal reportCessna 172 · Lawrence, KSThe student pilot's incorrect control application during landing after a simulated engine failure, which resulted in a hard, bounced landing, and the flight instructor's delayed action to perform a go-around in gusting wind conditions.NTSB GAA17CA327Accident · No injuriesData collectionFinal reportCessna 172 · Tooele, UTThe student pilot’s failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle of attack during an attempted go-around, which resulted in an aerodynamic stall.NTSB GAA17CA300Accident · No injuriesData collectionFinal reportCessna 172 · Clarksville, TNThe pilot’s unstabilized approach and improper landing flare, which resulted in a hard, porpoised landing.NTSB GAA17CA283Accident · No injuriesData collectionFinal reportCessna 172 · Atlanta, GAThe student’s incorrect use of the go-around procedure, which resulted in an aerodynamic stall, and the flight instructor’s delayed remedial action.NTSB GAA17CA229Accident · No injuriesData collectionFinal reportCessna 172 · San Marcos, TXThe student pilot’s improper landing flare, which resulted in a hard landing.NTSB GAA17CA163Accident · No injuriesData collectionFinal reportCessna 172S · St Petersburg, FLThe student pilot’s overcompensation of right rudder pedal application during the landing roll, which resulted in a loss of directional control and impact with runway signage and a fence.NTSB CEN17FA111Accident · 2 fatalField investigationFinal reportCessna 172S · Berthoud, COThe failure of the pilots to apply prompt and/or correct flight control inputs to adequately recover from the intentional aerodynamic spin.NTSB CEN17CA140Accident · No injuriesData collectionFinal reportCessna 172R · Cahokia, ILA hard landing for reasons that could not be determined based on the available evidence.NTSB WPR17FA063Accident · 1 fatalField investigationFinal reportCessna 172 · Ramona, CAThe flight instructor's failure to ensure that adequate clearance from terrain was maintained after performance of a simulated engine failure maneuver, which resulted in controlled flight into terrain.NTSB GAA17CA122Accident · No injuriesData collectionFinal reportCessna 172 · Punta Gorda, FLThe student pilot’s failure to maintain proper pitch control, which resulted in a hard, bounced landing.