NTSB investigations: Lycoming IO-360-L2A, FL

6 cases on aircraft whose registry engine model is Lycoming IO-360-L2A, where the defining event was Abnormal runway contact. 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

20132026
NTSB investigations: Lycoming IO-360-L2A, FL per year, 2013–2026: 6 cases
20132
20162
20211
20221

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\" = 'FL' 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\" = '090'))
  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 ERA23LA017Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Sanford, FLThe pilot's unstable approach, which resulted in a hard landing and impact with a runway threshold light. Also causal was the flight instructor’s failure to take remedial action to prevent the hard landing.Oct 4, 2022 · N455ER · Substantial damageNTSB ERA22LA065Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Palm Coast, FLThe student pilot’s improper landing flare and subsequent improper recovery from a bounced landing, resulting in a hard landing and substantial damage to the lower fuselage and firewall.Nov 14, 2021 · N61237 · Substantial damageNTSB GAA17CA104Accident · No injuriesData collectionFinal reportCessna 172 · Palm Coast, FLThe student pilot’s improper landing flare, which resulted in a hard landing and porpoise.Dec 24, 2016 · N1289Y · Substantial damageNTSB GAA16CA114Accident · No injuriesData collectionFinal reportCessna 172 · Merritt Island, FLThe student pilot's improper flare which resulted in a porpoise, runway excursion, and nose over.Jan 31, 2016 · N35079 · Substantial damageNTSB ERA14CA078Accident · No injuriesData collectionFinal reportCessna 172S · Miami, FLThe pilot's improper flare during a gusty, crosswind landing.Dec 24, 2013 · N17223 · Substantial damageNTSB ERA13CA395Accident · No injuriesData collectionFinal reportCessna 172S · Fort Lauderdale, FLThe student pilot’s failure to apply power to go-around following a bounced landing resulting in abnormal runway contact and collapse of the nose landing gear.Aug 29, 2013 · N6065P · Substantial damage