NTSB investigations: Lycoming I0360 series, 2004

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

19822026
NTSB investigations: Lycoming I0360 series, 2004 per year, 1982–2026: 82 cases
19823
19834
19842
19851
19873
19903
19911
19925
19931
19941
19951
19962
19975
19983
19995
20004
20017
20029
20034
20048
20056
20061
20073

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\") = 2004
    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 DEN04LA150Accident · No injuriesLimited investigationFinal reportCessna 172S · Broomfield, COthe pilot's improper flare, and the flight instructor's inadequate supervision of the pilot.Sep 30, 2004 · N802SP · Substantial damageNTSB DEN04LA127Accident · No injuriesLimited investigationFinal reportCessna 172S · Carlsbad, NMthe student pilot's inadequate flare resulting in a hard landing. A contributing factor was the tailwind conditions.Aug 19, 2004 · N849SP · Substantial damageNTSB IAD04CA038Accident · No injuriesData collectionFinal reportPiper PA-28R-180 · Eliot, METhe pilot's failure to maintain airspeed above stall which resulted in a hard landing and collapse of the landing gear. Also causal was the flight instructor's inadequate supervision.Aug 17, 2004 · N4631J · Substantial damageNTSB CHI04CA222Accident · No injuriesData collectionFinal reportMooney M20J · Huntington, INThe pilot's inadequate flare and unsuccessful recovery from a bounced landing, and the pilot's and flight instructor's failure to maintain directional control and airspeed during the subsequent aborted landing, which resulted in a stall. A factor was the…Aug 11, 2004 · N201AM · Substantial damageNTSB CHI04CA241Accident · No injuriesData collectionFinal reportCessna 172R · Olathe, KSThe student pilot flared too high and failed to recover from a bounced landing.Aug 5, 2004 · N458CM · Substantial damageNTSB CHI04CA165Accident · No injuriesData collectionFinal reportCessna 172S · Fishers, INThe pilot's inadequate remedial actions after an inadequate landing flare and subsequent hard landing. Additional causes were the pilot-induced porpoise and the collapse of the nose landing gear.Jun 26, 2004 · N229ME · 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 NYC04CA070Accident · No injuriesData collectionFinal reportCessna 172R · Batavia, OHThe student pilot's improper flare and improper recover from a bounced landing, which resulted in a hard landing.Feb 16, 2004 · N121UC · Substantial damage