NTSB investigations: Lycoming 0-320 series, IA

6 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “In flight collision with object”. 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

19872026
NTSB investigations: Lycoming 0-320 series, IA per year, 1987–2026: 6 cases
19871
19901
19921
19931
19981
19991

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\" = 'IA' 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 ('41508')
      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\" = 220))
  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 CHI99FA284Accident · 1 fatalField investigationFinal reportBellanca 7GCAA · Titonka, IAThe low altitude maneuver attempted and altitude/clearance not being maintained by the pilot, which resulted in an impact with a pine tree. A factor to the accident was the pine tree.Aug 8, 1999 · N5033G · DestroyedNTSB CHI98LA252Accident · Serious injuriesLimited investigationFinal reportPiper PA28-151 · Anthon, IAThe pilot-in-command's improper preflight planning, preparation and fuel management resulting in an unscheduled landing and impact with a pole.Jul 15, 1998 · N1473X · Substantial damageNTSB CHI93FA103Accident · 4 fatalField investigationFinal reportPiper PA-28-140 · Newton, IAVFR flight into IMC conditions. Factors related to the accident were fog, and the pilot's lack of total instrument time.Mar 6, 1993 · N1646J · DestroyedNTSB CHI93LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Ames, IAThe pilot exceeded the aircraft's maximum gross weight limitation which resulted in the failure to obtain a proper climb rate after takeoff.Nov 5, 1992 · N16231 · Substantial damageNTSB MKC90LA092Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-150 · Eldora, IAImproper planning/decision by the pilot, and his failure to maintain clearance from obstructions during the approach to land. Factors related to the accident were: the aircraft's low fuel level, darkness, the pilot's selection of the wrong airport/runway, the…Apr 21, 1990 · N1680P · Substantial damageNTSB MKC87LA076Accident · No injuriesLimited investigationFinal reportCessna 172 · Muscatine, IAThe grass runway was 1300 feet long. The wind was 90 degrees cross at 5 knots, gusts to 20 KTS. The instructor said they had a wind shift and then they hit a soft spot near the end of the runway which slowed them. The elevator and stabilizer caught on a…Apr 5, 1987 · N79179 · Destroyed