NTSB investigations: Lycoming 0-320 series, 2017

8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the defining event was Hard landing. 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

20082026
NTSB investigations: Lycoming 0-320 series, 2017 per year, 2008–2026: 133 cases
200815
200910
20108
201110
201213
20135
20149
20156
20165
20178
20185
20194
20209
20215
20227
20232
20243
20255
20264

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\") = 2017
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508')
      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\" = '092'))
  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 GAA18CA097Accident · No injuriesData collectionFinal reportCessna 172 · Monroe, MIThe student pilot’s improper yaw control during the landing flare and the flight instructor’s failure to take remedial action, which resulted in a hard landing.Dec 21, 2017 · N4491R · Substantial damageNTSB GAA17CA540Accident · No injuriesData collectionFinal reportCessna 172 · Lynchburg, VAThe pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing.Sep 16, 2017 · N5396D · Substantial damageNTSB ERA17LA319Accident · No injuriesLimited investigationFinal reportCessna 172 · Gulf Shores, ALThe pilot's improper landing flare, which resulted in a hard landing.Aug 23, 2017 · N97116 · Substantial damageNTSB CEN17LA324Accident · No injuriesLimited investigationFinal reportPiper PA 18-150 · Sweetwater, TXThe pilot's improper landing flare, which resulted in a hard landing and the overstress failure of the right main landing gear.Aug 18, 2017 · N82912 · Substantial damageNTSB GAA17CA357Accident · No injuriesData collectionFinal reportBellanca 7GCBC · Edgewood, NMThe pilot's decision to take off with a gusting tailwind, which resulted in a loss of pitch control during the initial climb and a subsequent hard landing and loss of directional control.Jun 21, 2017 · N88237 · Substantial damageNTSB CEN17LA341Accident · Serious injuriesLimited investigationFinal reportPiper PA-28 · Ray, MIThe pilot's failure to maintain a proper approach speed, which resulted in in a hard landing and a runway excursion. Contributing to the accident was the pilot's decision to fly the airplane without an instructor onboard.May 27, 2017 · N5584U · Substantial damageNTSB GAA17CA180Accident · No injuriesData collectionFinal reportCessna 172 · Naples, FLThe pilot’s failure to maintain pitch control, which resulted in a hard landing.Feb 17, 2017 · N737RT · Substantial damageNTSB GAA17CA111Accident · No injuriesData collectionFinal reportCessna 172 · Hollywood, FLThe student pilot’s improper landing flare in gusting crosswind conditions, which resulted in a hard landing.Jan 7, 2017 · N907WA · Substantial damage