NTSB investigations: Lycoming IO-360-L2A, 2016

7 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

20092026
NTSB investigations: Lycoming IO-360-L2A, 2016 per year, 2009–2026: 34 cases
20093
20101
20121
20132
20142
20152
20167
20175
20184
20211
20222
20242
20251
20261

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\") = 2016
    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 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 GAA16CA421Accident · No injuriesData collectionFinal reportCessna 172 · Oak Island, NCThe pilot's failure to maintain pitch control during the landing flare, which resulted in a hard landing and substantial damage to the firewall.Aug 2, 2016 · N24447 · Substantial damageNTSB GAA16CA268Accident · No injuriesData collectionFinal reportCessna 172 · Newport News, VAThe student pilot's incorrect pitch control during the landing flare, which resulted in abnormal runway contact and a substantially damaged firewall.May 19, 2016 · N1724U · Substantial damageNTSB GAA16CA219Accident · No injuriesData collectionFinal reportCessna 172 · Mesa, AZThe student pilot's failure to maintain pitch control during the landing flare, which resulted in an abnormal runway contact, porpoise, nose gear collapse, runway excursion, and impact with terrain.May 2, 2016 · N509ND · Substantial damageNTSB GAA16CA188Accident · No injuriesData collectionFinal reportCessna 172 · Payson, AZThe student pilot's failure to maintain pitch control during the landing flare, resulting in the subsequent porpoise during landing and substantial damage to the firewall.Apr 6, 2016 · N5275S · Substantial damageNTSB GAA16CA187Accident · No injuriesData collectionFinal reportCessna 172 · Scottsdale, AZThe failure of the student pilot to maintain pitch control while landing, which resulted in a hard landing, loss of directional control, and runway excursion.Mar 6, 2016 · N6023V · 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 damage