Final NTSB investigations: Lycoming IO-360-L2A, 2025

8 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

20012026
Final NTSB investigations: Lycoming IO-360-L2A, 2025 per year, 2001–2026: 391 cases
20012
20021
20037
200418
200513
200615
200722
200824
200920
201020
201121
201222
201314
201416
201512
201621
201724
201811
201914
202013
202120
202210
202315
202419
20258
20269

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\") = 2025
    AND c.\"completionStatus\" = 'Completed'
    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.

NTSB ERA26LA038Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Lynchburg, VAAn in-flight collision with a bird.Nov 10, 2025 · N708LU · Substantial damageNTSB 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.Oct 13, 2025 · N1206U · Substantial damageNTSB 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.Oct 6, 2025 · N677DM · Substantial damageNTSB 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.Aug 30, 2025 · N22998 · 2 aircraft · Minor damageNTSB ERA25LA306Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Baltimore, MDThe pilot’s inadequate landing flare at night, which resulted in a hard landing.Aug 17, 2025 · N6208C · Substantial damageNTSB 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.Feb 20, 2025 · N726ER · Substantial damageNTSB 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.Jan 29, 2025 · N1159K · Substantial damageNTSB 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.Jan 27, 2025 · N51387 · Substantial damage