NTSB investigations: Lycoming IO-360-L2A, 2023
15 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\") = 2023
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") = 2023
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 ANC24LA010Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Kapolei, HIThe first pilot’s failure to maintain a stabilized approach, in gusty crosswind conditions, in an environment favoring wake turbulence.NTSB ERA24LA057Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Social Circle, GAAn encounter with a downdraft while maneuvering at low altitude, which resulted in a collision with a fence.NTSB ERA24LA033Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · Orlando, FLA partial loss of engine power during initial climb after takeoff for undetermined reasons.NTSB CEN24LA036Accident · No injuriesClass 3 · LimitedFinal reportTextron 172S · Erie, COA partial loss of engine power while maneuvering at a low altitude due to a stuck exhaust valve.NTSB CEN23LA430Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · West Bend, WIThe pilot’s inadequate landing flare that resulted in a hard landing and impact with the runway.NTSB CEN23LA394Accident · Minor injuriesClass 4 · LimitedFinal reportTextron 172S · Englewood, COAn in-flight collision with multiple geese during initial climb.NTSB CEN23LA348Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Philadelphia, PAThe pilot receiving instruction’s failure to maintain control during a go-around. Contributing to the accident was the flight instructor’s inadequate supervision of the flight.NTSB WPR23LA298Accident · No injuriesClass 4 · LimitedFinal reportCessna 152 · Long Beach, CAThe flight instructor’s inattention during ground operations, which resulted in unintentional movement of the airplane and ground collision with another airplane.NTSB WPR23LA253Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Novato, CAThe pilot's failure to maintain directional control of the airplane during the landing roll for a touch and go, which resulted in a collision with terrain.NTSB WPR23LA210Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Prescott, AZThe pilot’s improper landing flare, which resulted in an aerodynamic stall. Contributing to the accident was his delayed decision to initiate a go-around.NTSB WPR23LA199Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Casa Grande, AZAn in-flight separation of the throttle linkage, which resulted in a loss of throttle control. Contributing to the accident was maintenance personnel’s failure to follow the maintenance manual inspection procedure for the throttle cable assembly.NTSB CEN23LA179Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Englewood, COThe pilot’s decision to adjust his seat during taxi, which resulted in his seat sliding aft, and subsequent loss of directional control.NTSB CEN23LA175Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Brookings, SDThe student pilot’s failure to maintain pitch and directional control during the takeoff roll. Contributing to the accident, was the student pilot’s delay in relinquishing control of the airplane and the instructor's delayed reaction before the loss of…NTSB WPR23FA172Accident · 1 fatalClass 3 · FieldFinal reportCessna 172S · Los Angeles, CAThe pilot’s failure to maintain clearance with the hilly terrain resulting from his loss of situational awareness due to the deteriorating weather conditions as he descended to approach his destination airport.NTSB CEN23LA102Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Limon, COThe pilot’s failure to maintain directional control during the takeoff roll.