NTSB investigations: Lycoming TI0-540 series, 1996

5 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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 TI0-540 series, 1996 per year, 1982–2026: 69 cases
19824
19843
19855
19863
19874
19885
19893
19903
19915
19921
19931
19941
19952
19965
19972
19991
20002
20014
20023
20045
20052
20064
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 year(c.\"eventDate\") = 1996
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533')
      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\" = 351))
  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 MIA97FA031Accident · 1 fatalField investigationFinal reportPiper PA32-300D · Reform, ALa complete loss of engine power due to a total failure of both magnetos, and the failure of the pilot-in-command to insure that the airplane was airworthy. The dark night and unsuitable terrain were factors.Dec 6, 1996 · N8603N · DestroyedNTSB ATL96LA128Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Georgetown, SCfailure of maintenance personnel to comply with an airworthiness directive, requiring periodic magneto inspections; inadequate annual inspection of the airplane by (other) maintenance personnel; and subsequent failure of the impulse coupling in the left…Sep 19, 1996 · N9VM · Substantial damageNTSB NYC96LA118Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Williamstown, NJinadequate maintenance, which resulted in a failure of the magneto housing hold-down flange, a disconnect of the magneto from the engine, and loss of engine power. The obstruction (fence post) in the emergency landing area was a related factor.Jun 1, 1996 · N8186G · Substantial damageNTSB ATL96TA047Accident · Minor injuriesFinal reportPiper PA-32-300 · Windermere, FLthe use of improper connecting rod bolts, failure of the overhaul facility to record the correct overhaul date on the work orders for the stored connecting rod assemblies, and subsequent failure of the connecting rod bolts.Feb 13, 1996 · N8951N · Substantial damageNTSB CHI96FA113Accident · 1 fatalField investigationFinal reportPiper PA-32 · Milwaukee, WIInadequate maintenance and inspection in that the Airworthiness Directive which applied to the fuel pump had not been complied with. A factor was the pilot was unable to reach land.Jan 17, 1996 · N3326Q · Destroyed