NTSB investigations: Lycoming IO-360-L2A, CA
45 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
| 2003 | 1 |
|---|---|
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2007 | 5 |
| 2008 | 5 |
| 2009 | 3 |
| 2011 | 2 |
| 2013 | 2 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 2 |
| 2017 | 5 |
| 2018 | 1 |
| 2020 | 1 |
| 2022 | 1 |
| 2023 | 3 |
| 2025 | 2 |
| 2026 | 3 |
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\" = 'CA' 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" = 'CA' 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 WPR26LA222Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172S · Death Valley, CAThe pilot’s failure to maintain airspeed and encounter with a tailwind while landing on a rough runway, which resulted in a runway overrun and subsequent nose over.NTSB WPR26LA220Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Morgan Hill, CAAn in-flight collision with a bird.NTSB WPR26LA164Accident · Serious injuriesClass 3 · LimitedPreliminary reportCessna 172S · Pacoima, CAOn April 20, 2026, about 1107 Pacific daylight time, a Cessna 172S airplane, N2126F, sustained substantial damage when it was involved in an accident near Whiteman Airport (WHP), Pacoima, California. The pilot was seriously injured. The airplane was operated…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 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 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 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 WPR22LA123Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · San Carlos, CAThe pilot’s improper landing flare which resulted in a bounced landing.NTSB WPR20LA256Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · San Jose, CAThe airplane’s collision with a bird while maneuvering in the airport traffic pattern.NTSB GAA18CA294Accident · No injuriesData collectionFinal reportCessna 172 · Palo Alto, CAThe pilot’s improper landing flare, which resulted in a hard landing.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 GAA17CA573Accident · No injuriesData collectionFinal reportCessna 172 · Chino, CAAn in-flight collision with a bird while on downwind.NTSB GAA17CA470Accident · No injuriesData collectionFinal reportCessna 172 · Carlsbad, CAThe student pilot’s improper landing flare in gusting wind conditions.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 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 GAA16CA416Accident · No injuriesData collectionFinal reportCessna 172 · Palm Springs, CAThe student pilot's failure to maintain directional control during an aborted landing, which resulted in a runway excursion and a nose over in rough terrain.NTSB WPR16LA063Accident · No injuriesLimited investigationFinal reportCessna 172S · San Diego, CAThe failure of the flight instructor of the other airplane to maintain awareness while parked on the ramp with the engine operating, which resulted in impact with the parked airplane.NTSB WPR16LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172S · San Jose, CAThe pilot's failure to maintain directional control during the landing roll at night, which resulted in a runway excursion.NTSB WPR15FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172S · Davenport, CAUndetermined because the airplane was not located.NTSB GAA15CA018Accident · No injuriesData collectionFinal reportCessna 172S · Camarillo, CAThe pilot involved and the phase of flight when the damage occurred were not determined.NTSB WPR15LA025Accident · No injuriesLimited investigationFinal reportCessna 172S · Santa Monica, CAThe separation of a section of a propeller blade due to fatigue cracking. Contributing to the accident was the operator’s failure to comply with the manufacturer’s maintenance and inspection instructions.NTSB WPR15CA028Accident · No injuriesData collectionFinal reportCessna 172 - S · Hawthorne, CAThe pilot's improper flare which resulted in a loss of aircraft control and subsequent hard landing.NTSB WPR14CA351Accident · No injuriesData collectionFinal reportCessna 172S · Santa Ynez, CAThe student pilot's inadequate flare and loss of aircraft control during landing, which resulted in multiple bounces.NTSB WPR13CA332Accident · No injuriesData collectionFinal reportCessna 172S · Santa Barbra, CAThe pilot's inadequate landing flare, which resulted in a hard landing.NTSB WPR13LA286Accident · No injuriesLimited investigationFinal reportCessna 182T · San Diego, CABoth pilots’ failure to maintain a proper visual lookout while taxiing during nighttime conditions, which resulted in an on-ground collision.NTSB WPR11CA472Accident · No injuriesData collectionFinal reportCessna 172R · Napa, CAThe student pilot's improper flare, which resulted in a hard landing.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 WPR09CA461Accident · No injuriesData collectionFinal reportCessna 172S · San Carlos, CAThe student pilot's failure to maintain clearance with a fence post during taxi.NTSB WPR09LA145Accident · Serious injuriesLimited investigationFinal reportCessna 172R · Oceanside, CAA total loss of engine power in flight due to the fatigue failure of the No. 4 cylinder.NTSB WPR09LA098Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Oceanside, CAA defective alternator wire splice that resulted in an intermittent electrical system malfunction and erroneous fuel gauge readings, and, a loss of engine power for an undetermined reason.NTSB WPR09CA273Accident · No injuriesData collectionFinal reportCessna 172S · Compton, CAThe pilot's improper flare and inadequate recovery from a bounced landing.NTSB LAX08FA301Accident · Serious injuriesField investigationFinal reportCessna 172S · Fullerton, CAThe pilot's failure to follow the takeoff checklist and verify the proper flap setting before takeoff.NTSB LAX08LA191Accident · 2 fatalLimited investigationFinal reportCessna 172S · Oceanside, CAFailure of the pilot to regain airplane control during an intentional stall/spin maneuver.NTSB LAX08CA102Accident · No injuriesData collectionFinal reportCessna 172S · Gualala, CAThe pilot's decision not to use all of the available runway, his premature rotation and failure to obtain and maintain an adequate airspeed to continue the takeoff that resulted in a stall/mush, an aborted takeoff, a runway overrun, and a collision with…NTSB LAX08CA124Accident · No injuriesData collectionFinal reportCessna 172S · San Luis Obispo, CAThe pilot's inadequate landing flare, resulting in a hard landing. Contributing to the accident was the gusty wind condition.NTSB SEA08CA052Accident · No injuriesData collectionFinal reportCessna 172S · Fullerton, CAThe pilot's failure to maintain clearance while taxiing. Contributing to the accident was the pilot's diverted attention.NTSB LAX08FA023Accident · 1 fatalField investigationFinal reportCessna 172S · Palm Springs, CAThe flight instructor's failure to maintain sufficient airspeed to avoid a stall during takeoff-initial climb, and his impairment from alcohol.NTSB SEA07CA243Accident · No injuriesData collectionFinal reportCessna 172S · Bakersfield, CAThe student pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in a collision with a taxiway sign.NTSB LAX07CA199Accident · No injuriesData collectionFinal reportCessna 172S · Santa Barbara, CAthe pilot's failure to maintain directional control.NTSB SEA07CA120Accident · No injuriesData collectionFinal reportCessna 172R · Livermore, CAThe pilot's improper flare during landing.NTSB LAX06CA174Accident · No injuriesData collectionFinal reportCessna 172S · Madera, CAthe pilot's failure to maintain directional control during the landing rollout.NTSB LAX05LA118Accident · No injuriesLimited investigationFinal reportCessna 172S · Thermal, CAthe student pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control.NTSB LAX04CA130Accident · No injuriesData collectionFinal reportCessna 172S · Riverside, CAthe pilot's inadequate visual lookout, which resulted in his failure to maintain proper alignment with the taxiway. Factors in the accident were the dusk lighting conditions and pilot not understanding the ground control taxi clearance.NTSB LAX04LA060Accident · No injuriesLimited investigationFinal reportCessna 172S · Watsonville, CAloss of engine power for undetermined reasons.