NTSB investigations: Lycoming TI0-540 series, CO

8 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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, CO per year, 1982–2026: 8 cases
19821
19911
19921
19931
19971
19981
20001
20011

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\" = 'CO' 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 ('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\" = 130))
  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 DEN01LA132Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Grand Junction, COthe failure of the nose landing gear right drag brace (link assembly) due to fatigue.Jul 29, 2001 · N114SA · Substantial damageNTSB DEN01LA005Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Grand Junction, COTotal failure of the right forward inboard landing gear door hinge pin for undetermined reasons.Sep 27, 2000 · N159SW · Substantial damageNTSB FTW98IA361Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Denver, COA hydraulic failure due to a ruptured hydraulic line, preventing the extension of the nose and right main landing gear.Aug 18, 1998 · N66906 · Minor damageNTSB FTW97LA206Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Greeley, COunlatching of the left outboard engine cowling latches for undetermined reason(s), which allowed the left engine cowling to separate inflight and strike the vertical stabilizer.May 28, 1997 · N491SC · Substantial damageNTSB DEN93LA074Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Grand Junction, COFailure of the pilot in command to follow manual gear extension procedures. A factor was a total electrical failure.Jul 8, 1993 · N8967P · Substantial damageNTSB FTW92LA110Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Denver, COThe loss of hydraulic fluid due to a ruptured hydraulic line in the landing gear system.Apr 3, 1992 · N6460Y · Substantial damageNTSB DEN91FA065Accident · 1 fatalField investigationFinal reportPiper PA-31B-310 · Bennett, COIn-flight separation of the left engine cowl assembly that was not properly latched, and failure of the pilot to maintain minimum control speed, which resulted in his loss of aircraft control. Factors related to the accident were: an inadequate preflight…May 1, 1991 · N7407L · DestroyedNTSB DEN82DA110Accident · No injuriesFinal reportPiper PA-32RT-300T · Durango, COThe pilot reported that after taking off, dense white smoke began to fill the cockpit and seemed to come from under the instrument panel. He stated that the instruments were in the normal operating range, but the smoke became so dense that the visibility in…Jun 23, 1982 · N31912 · Substantial damage