NTSB investigations: Lycoming IO-360-L2A, AZ

8 cases on aircraft whose registry engine model is Lycoming IO-360-L2A, where the defining event was Loss of control on ground. 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

20112026
NTSB investigations: Lycoming IO-360-L2A, AZ per year, 2011–2026: 8 cases
20112
20122
20131
20142
20191

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 c.\"eventStateOrRegion\" = 'AZ' 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')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '230'))
  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 GAA19CA225Accident · No injuriesData collectionFinal reportCessna 172 · Scottsdale, AZThe pilot's improper rudder inputs and failure to maintain directional control during landing with a crosswind, which resulted in a runway excursion and impact with a runway sign.Apr 20, 2019 · N6023V · Substantial damageNTSB WPR15CA018Accident · No injuriesData collectionFinal reportCessna 172 - R · Lake Havasu, AZThe pilot's failure to maintain directional control during the landing roll, which resulted in a runway excursion and impact with terrain.Oct 23, 2014 · N1590W · Substantial damageNTSB WPR15CA004Accident · Minor injuriesData collectionFinal reportCessna 172S · Sedona, AZThe pilot's failure to maintain airplane control during the landing roll out.Oct 5, 2014 · N2179L · Substantial damageNTSB WPR13LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Phoenix, AZThe student pilot's excessive directional control inputs during the takeoff roll and the flight instructor's delayed and ineffective corrective actions, which resulted in the loss of airplane control.Apr 4, 2013 · N2166K · Substantial damageNTSB WPR12CA232Accident · No injuriesData collectionFinal reportCessna 172S · Page, AZThe pilot's failure to maintain directional control during the landing flare.May 27, 2012 · N21718 · Substantial damageNTSB WPR12CA171Accident · No injuriesData collectionFinal reportCessna 172S · Prescott, AZThe pilot's inadequate compensation for a crosswind during takeoff, which resulted in a loss of directional control.Apr 12, 2012 · N17304 · Substantial damageNTSB WPR12CA038Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student pilot's inadequate directional control during takeoff.Nov 12, 2011 · N24350 · Substantial damageNTSB WPR11CA440Accident · No injuriesData collectionFinal reportCessna 172 · Phoenix, AZThe pilot's failure to maintain directional control during the landing roll.Sep 8, 2011 · N5275S · Substantial damage