NTSB investigations: Lycoming I0360 series, CA

8 cases on aircraft whose registry engine model is Lycoming I0360 series, where the first occurrence 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

19922026
NTSB investigations: Lycoming I0360 series, CA per year, 1992–2026: 8 cases
19922
20001
20011
20021
20041
20051
20071

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\" = 'CA' 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 ('41515')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 200))
  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 SEA07CA182Accident · No injuriesData collectionFinal reportCessna 172S · Long Beach, CAThe pilot's improper recovery from a bounced landing which resulted in an inadvertent stall and a hard landing. The crosswind was a factor.Jun 25, 2007 · N137RJ · Substantial damageNTSB LAX05CA207Accident · No injuriesData collectionFinal reportCessna 172R · Santa Maria, CAthe student pilot's improper flare and recovery from a bounced landing.Jun 12, 2005 · N2384L · Substantial damageNTSB LAX04CA215Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Galt, CAthe pilot under instruction's failure to maintain an adequate airspeed on final and misjudged flare, which resulted in stall/mush and hard landing. The certified flight instructor's inadequate supervision and failure to initiate timely remedial action were…Apr 25, 2004 · N169JP · Substantial damageNTSB LAX02LA129Accident · No injuriesLimited investigationFinal reportPiper PA28R-200 · Redlands, CAThe pilot failed to compensate for the wind condtions when he encountered an updraft followed by a downdraft.Mar 20, 2002 · N5060T · Substantial damageNTSB LAX01LA203Accident · No injuriesLimited investigationFinal reportMooney M20J · Jackson, CAFailure of the pilot to maintain proper airspeed for landing and airplane control with an existing crosswind. A contributing factor was the distraction of the pilot by a yelling passenger.Jun 9, 2001 · N4235H · Substantial damageNTSB LAX00LA110Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200 · Big Bear City, CAThe pilot's selection of a final approach airspeed in variance with the manufacturer's recommendations, which was too slow for the gusty and variable crosswind conditions, which resulted in a stall/mush and a hard landing.Feb 27, 2000 · N15202 · Substantial damageNTSB LAX93LA049Accident · No injuriesLimited investigationFinal reportMooney M20J · Santa Ana, CAThe pilot's improper landing flare, his improper bounced landing recovery technique, and his inadvertent entry into a stall mush condition.Nov 21, 1992 · N4766H · Substantial damageNTSB LAX92FA196Accident · 2 fatalField investigationFinal reportBeech A23-24 · Corona, CA1) The flying pilot's improper landing flare which resulted in a hard landing and significant damage to the aircraft empennage flight controls, 2) the flying pilot's decision to initiate a go around with the obvious serious damage to the aircraft, and 3) the…May 2, 1992 · N666CM · Destroyed