NTSB investigations: Lycoming TI0-540 series, 2001

6 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, 2001 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\") = 2001
    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 LAX02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Groveland, CAThe pilot's collision with an unobserved animal that entered the active runway during the dark nighttime when the pilot's visibility was diminished.Dec 14, 2001 · N4328B · Substantial damageNTSB FTW02LA052Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Duncan, OKThe pilot's descent below the minimum descent altitude, and his failure to maintain obstacle clearance. Contributing factors were the below approach/landing minimum weather, the dark night conditions, and the inoperative REIL's.Dec 13, 2001 · N127CA · Substantial damageNTSB DEN01FA161Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Pagosa Springs, COthe flight crews' intentional low altitude flight, and failure to maintain obstacle clearance.Sep 24, 2001 · N161RB · DestroyedNTSB CHI01FA312Accident · Serious injuriesField investigationFinal reportPiper PA-32R-301T · Downers Grove, ILthe improper preflight planning/preparation and the short field take off/procedure not followed by the pilot. Contributing factors were the airplane's forward center of gravity, the variable gusting wind and improper weight and balance calculations by…Sep 7, 2001 · N81557 · DestroyedNTSB FTW01LA158Accident · 1 fatalLimited investigationFinal reportPiper PA-32R-300 · Belle Chase, LAthe pilot's failure to maintain clearance with a utility pole while maneuvering. Contributing factors were the pilot's impairment due to alcohol intoxication and the night light conditions.Jul 4, 2001 · N5883V · DestroyedNTSB CHI01LA076Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Fulton, MOthe pilot not maintaining altitude/clearance from the power line during the circling approach. Factors were the power transmission wire, the plowed field, and that the pilot's lookout was not possible through the built up ice on the windshield.Jan 31, 2001 · N6754Y · Substantial damage