NTSB investigations: Lycoming I0360 series, 2002

9 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, 2002 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\") = 2002
    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 NYC03LA032Accident · No injuriesLimited investigationFinal reportCessna 172S · Akron, OHThe pilot's improper flare which resulted in a hard landing.Dec 26, 2002 · N782SP · Substantial damageNTSB CHI03LA075Accident · No injuriesLimited investigationFinal reportCessna 172S · Tea, SDThe student pilot's improper flare. The pilot's lack of experience and diverted attention were factors.Dec 24, 2002 · N692SP · Substantial damageNTSB MIA03LA004Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-200 · Cullman, ALthe pilot-in-command's (CFI) delayed remedial action, and improper recovery from a bounced landing, resulting in a hard landing, and impact with a parked airplane.Oct 9, 2002 · N22DB · Substantial damageNTSB CHI02LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Boyne Falls, MIThe pilot's improper flare during landing.Sep 21, 2002 · N784SA · Substantial damageNTSB ATL02LA166Accident · No injuriesLimited investigationFinal reportCessna 172S · Immokalee, FLThe student pilot's improper flare at touchdown resulted in a hard landing while performing an off-airport precautionary landing after the inadvertent activation of the autopilot.Sep 6, 2002 · N827SP · Substantial damageNTSB NYC02LA161Accident · No injuriesLimited investigationFinal reportCessna 172RG · Rochester, NYThe pilot's improper flare and recovery from a bounced landing. A factor in the accident was the slow response time of the airspeed indicator.Aug 12, 2002 · N888RG · Substantial damageNTSB DEN02LA088Accident · No injuriesLimited investigationFinal reportCessna 172S · Englewood, COthe instructor's inadequate supervision of the flight and his premature raising of the flaps, resulting in a hard landing.Aug 4, 2002 · N238SP · Substantial damageNTSB MIA02LA091Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLthe pilot misjudged the landing flare, resulting in a hard landing, and damage to the airplane.Apr 28, 2002 · N786SP · 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 damage