NTSB investigations: Lycoming IO-360-L2A, 2011
21 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
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\") = 2011
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") = 2011
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 WPR12CA038Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student pilot's inadequate directional control during takeoff.NTSB ERA12LA066Accident · No injuriesLimited investigationFinal reportCessna 172S · Fort Lauderdale, FLThe Cessna 172 flight instructor and student pilot's inadequate visual lookout and failure to maintain clearance from the stationary Cessna 182.NTSB OPS12IA041Incident · No injuriesIncident investigationFinal reportCessna 172S · Daytona Beach, FLThe departing pilot's incorrect runway selection and non-compliance with an air traffic control clearance. Contributing to the incident was the air traffic controller's inadequate monitoring of the departing aircraft to ensure that the pilot complied with the…NTSB ERA11CA516Accident · No injuriesData collectionFinal reportCessna 172S · Westminster, MDThe pilot's inadequate recovery from a bounced landing, which resulted in a loss of airplane control. Contributing to the accident was the pilot's improper approach airspeed for a short-field landing.NTSB WPR11CA472Accident · No injuriesData collectionFinal reportCessna 172R · Napa, CAThe student pilot's improper flare, which resulted in a hard landing.NTSB ERA11CA490Accident · No injuriesData collectionFinal reportCessna 172R · Naples, FLThe student pilot's improper flare, which resulted in a hard landing and subsequent loss of directional control.NTSB WPR11CA440Accident · No injuriesData collectionFinal reportCessna 172 · Phoenix, AZThe pilot's failure to maintain directional control during the landing roll.NTSB CEN11CA624Accident · No injuriesData collectionFinal reportCessna 172S · Bemidji, MNThe student pilot's improper flare, which resulted in a hard landing.NTSB WPR11LA362Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Syracuse, UTThe failure of the maintenance technicians who installed the engine to properly tighten the fuel injection servo to a spider supply line, which caused a loss of engine power due to fuel starvation.NTSB WPR11LA284Accident · No injuriesLimited investigationFinal reportCessna 172S · Palo Alto, CAA total loss of engine power for undetermined reasons during the landing approach over unsuitable terrain.NTSB WPR11LA266Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Mount Pleasant, UTThe pilot’s failure to determine the airplane’s fuel quantity before takeoff, which resulted in a loss of engine power due to fuel exhaustion.NTSB ERA11CA343Accident · No injuriesData collectionFinal reportCessna 172S · Covington, GAThe pilot's failure to maintain directional control during takeoff.NTSB CEN11CA392Accident · No injuriesData collectionFinal reportCessna 172S · Cortez, COThe pilot's failure to maintain aircraft control while landing in gusty crosswind conditions.NTSB CEN11LA386Accident · No injuriesLimited investigationFinal reportCessna 172S · Grand Forks, NDThe flight instructor’s delayed remedial action to the student pilot’s bounced landing and subsequent loss of aircraft control.NTSB WPR11LA201Accident · No injuriesLimited investigationFinal reportCessna 172S · Payson, AZThe pilot's decision to conduct a touch-and-go arrival during his first flight to a high elevation airport, which resulted in an improper mixture adjustment and a partial loss of engine power for the takeoff and attempted climbout.NTSB ERA11CA244Accident · No injuriesData collectionFinal reportCessna 172S · Saint Petersburg, FLThe failure of the student pilot to maintain directional control during a touch-and-go landing.NTSB ERA11FA146Accident · 2 fatalField investigationFinal reportCessna 172S · New Smyrna Beach, FLThe flight instructor's failure to recognize or implement adequate remedial action to counter the effects of spatial disorientation. Contributing to the accident was the spatial disorientation experienced by one or both pilots.NTSB ERA11CA147Accident · No injuriesData collectionFinal reportCessna 172S · Daytona Beach, FLThe pilot's inadequate flare that resulted in a hard landing.NTSB ERA11CA132Accident · No injuriesData collectionFinal reportCessna 172S · St. Petersburg, FLThe student pilot's failure to maintain directional control while attempting to turn the airplane onto a taxiway after landing.NTSB CEN11CA171Accident · No injuriesData collectionFinal reportCessna 172R · Shreveport, LAThe student pilot's loss of directional control during the landing.NTSB ERA11FA118Accident · 2 fatalField investigationFinal reportCessna 172S · North Myrtle Beach, SCThe pilot's loss of airplane control during a missed approach due to spatial disorientation.