NTSB investigations: Lycoming TI0-540 series, 1995

5 cases on aircraft whose registry engine model is Lycoming TI0-540 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

19822026
NTSB investigations: Lycoming TI0-540 series, 1995 per year, 1982–2026: 69 cases
19824
19833
19845
19854
19864
19871
19882
19892
19901
19914
19922
19942
19955
19962
19981
19991
20003
20016
20022
20032
20047
20052
20062
20072

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\") = 1995
    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\" = 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 ATL96LA024Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Monroe, NCThe pilot's inadequate planning and failure to follow operating procedures resulted in his descent below the decision height while on final approach.Dec 19, 1995 · N4219T · Substantial damageNTSB LAX96FA050Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Fullerton, CAthe pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the pilot-in-command's self-induced pressure to get to work.Nov 20, 1995 · N888JK · DestroyedNTSB FTW95FA363Accident · Serious injuriesField investigationFinal reportPiper PA-32R-300 · Wichita Falls, TXthe pilot's failure to maintain airspeed while diverting attention to an open cargo door. A factor was the pilot's inadequate preflight inspection.Aug 26, 1995 · N9296K · DestroyedNTSB FTW95LA311Accident · No injuriesLimited investigationFinal reportBellanca 17-31ATC · Hico, TXThe pilot's failure to attain the proper touchdown point and the delayed go-around.Jul 23, 1995 · N500BT · Substantial damageNTSB SEA95LA039Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · La Grande, ORFailure of the pilot to maintain proper altitude/clearance from higher terrain that was located near the airport. Factors related to the accident were: low ceiling, fog, false/incorrect indication of the NDB, failure of other personnel to properly issue a…Jan 21, 1995 · N36PB · Substantial damage