NTSB investigations: Lycoming IO-360-L2A, UT
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
| 2006 | 1 |
|---|---|
| 2007 | 2 |
| 2008 | 1 |
| 2009 | 1 |
| 2011 | 2 |
| 2015 | 1 |
| 2017 | 1 |
| 2021 | 1 |
| 2026 | 2 |
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 c.\"eventStateOrRegion\" = 'UT' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'UT' AND c."eventCountry" = 'USA'
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 WPR26FA294Accident · 1 fatalClass 3 · FieldPreliminary reportTextron 172S · Provo, UTOn August 7, 2026, about 1549 mountain daylight time, a Textron Aviation Inc. 172S, N1842E, was substantially damaged when it was involved in an accident near Provo, Utah. The flight instructor sustained serious injuries, and the pilot undergoing instruction…NTSB WPR26FA232Accident · 1 fatalClass 3 · FieldPreliminary reportCessna 172 · Willard, UTOn June 23, 2026, at about 2247 mountain daylight time, a Cessna 172S, N387AF, was destroyed when it was involved in an accident near Willard, Utah. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91…NTSB WPR21FA211Accident · 2 fatalClass 3 · FieldFinal reportTextron 172S · Eden, UTThe flight instructor’s improper aeronautical decision-making, which led to an encounter with a downdraft at a low altitude in mountainous terrain and resulted in the instructor’s loss of airplane control and an impact with terrain.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 GAA15CA026Accident · No injuriesData collectionFinal reportCessna 172S · Vernal, UTThe student pilot's failure to maintain attitude control during landing flare.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 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 WPR09CA275Accident · No injuriesData collectionFinal reportCessna 172S · Tooele, UTThe pilot's failure to maintain directional control during landing.NTSB LAX08LA179Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Beaver, UTThe pilot's failure to attain and maintain an adequate airspeed during the initial climb as a result of his inadequate preflight planning and improper use of the mixture control. Contributing to the accident were the tailwind and high density altitude.NTSB LAX07CA202Accident · No injuriesData collectionFinal reportCessna 172S · Spanish Fork, UTThe pilot's misjudged landing flare resulting in a porpoise and hard touchdown.NTSB LAX07CA185Accident · Minor injuriesData collectionFinal reportCessna 172S · Wendover, UTThe pilot's failure to maintain directional control during the landing roll.NTSB SEA07LA013Accident · No injuriesLimited investigationFinal reportCessna 172S · Richfield, UTThe student pilot's inability to compensate for the gusty crosswinds during the initial part of the landing roll, which resulted in a loss of control and a noseover. Factors associated with the accident are gusty crosswinds, and a mound/berm of dirt alongside…