NTSB investigations: Lycoming IO-360-L2A, 2025
13 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\") = 2025
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") = 2025
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 ERA26LA038Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Lynchburg, VAAn in-flight collision with a bird.NTSB WPR26LA047Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172S · Lancaster, CAOn November 9, 2025, about 1205 Pacific daylight time, a Cessna 172S, N5199J, sustained substantial damage when it was involved in an accident near Lancaster, California. The pilot and passengers were not injured. The airplane was operated as a Title 14 Code…NTSB ERA26LA014Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · North Lauderdale, FLA total loss of engine power due to a fuel delivery system leak, which allowed air to enter the fuel system. The source of the leak could not be determined based on the available evidence.NTSB ERA26LA003Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · West Milford, NJThe pilot’s failure to adequate clearance from obstacles while maneuvering during the landing approach and the instructor pilot’s delayed remedial action, which resulted in the airplane contacting a tree and terrain.NTSB ERA25LA331Accident · No injuriesClass 4 · LimitedFinal reportCessna 150 · Farmingdale, NYThe Cessna 150 pilot’s decision to taxi in front of an oncoming Cessna 172, which resulted in a ground collision. Contributing to the accident was the Cessna 150 pilot’s momentary distraction, which delayed his recognition of the impending collision.NTSB WPR25FA264Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172S · Los Banos, CAOn August 26, 2025, about 1905 Pacific daylight time, a Cessna 172S, N5203H, was destroyed when it was involved in an accident near Los Banos, California. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part…NTSB ERA25LA306Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Baltimore, MDThe pilot’s inadequate landing flare at night, which resulted in a hard landing.NTSB ERA25LA281Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 172S · Kissimmee, FLOn July 30, 2025, at 11:28 eastern daylight time, a Cessna 172S, N121CW, was substantially damaged when it was involved in an accident near Kissimmee, Florida. The private pilot and flight instructor were uninjured. The airplane was operated as a Title 14…NTSB WPR25LA211Accident · Serious injuriesClass 3 · LimitedPreliminary reportCessna 172S · Sisters, OROn July 13, 2025, about 1106 Pacific daylight time, a Cessna 172S, N787LF, was substantially damaged when it was involved in an accident near Sisters, Oregon. The flight instructor was seriously injured, and the student pilot and pilot rated passenger…NTSB ERA25LA132Accident · No injuriesClass 3 · LimitedPreliminary reportTextron 172 · New Smyrna Beach, FLOn March 1, 2025, about 1138 eastern standard time, a Cessna 172S, N923EP, was substantially damaged when it was involved in an accident near New Smyrna Beach, Florida. The flight instructor and student pilot were not injured. The airplane was operated as a…NTSB WPR25LA105Accident · No injuriesClass 4 · LimitedFinal reportTextron 172S · Cottonwood, AZThe pilot undergoing instructions’ loss of aircraft control during landing, and the flight instructor’s failure to promptly intervene.NTSB ERA25LA118Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Kennesaw, GAThe student pilot’s failure to maintain an appropriate glide path and the flight instructor’s inadequate monitoring of the landing approach, which resulted in the airplane contacting the ground short of the runway.NTSB CEN25LA088Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Air Force Academy, COThe pilot’s failure to maintain airplane control during final approach after encountering an unexpected windshear.