NTSB investigations: Lycoming TI0-540 series, CA

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

19832026
NTSB investigations: Lycoming TI0-540 series, CA per year, 1983–2026: 5 cases
19831
19921
19951
20011
20061

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\" = 'CA' 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\" = 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 LAX06CA084Accident · No injuriesData collectionFinal reportCessna T206H · Palo Alto, CAthe pilot's failure to maintain proper runway alignment, which resulted in a collision with multiple objects.Jan 8, 2006 · N531HP · Substantial damageNTSB 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 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 LAX92LA399Accident · No injuriesLimited investigationFinal reportPiper 601P · Bakersfield, CAThe pilot's selection of an inadequate altitude for an intentional low pass. Contributing to the accident was the dusk light conditions, and the pilots improper inflight planning and decision.Sep 20, 1992 · N711YM · Substantial damageNTSB LAX83FA185Accident · 6 fatalField investigationFinal reportPiper PA32-300 · Weaverville, CAThe acft was being flown to a uni-directional arpt with an instructor plt (CFI) in the right front seat & a student plt/prospective buyer in the left front seat. The rwy elevation was 2230 ft MSL at the south end & 2350 ft at the north end. North of the rwy,…Apr 9, 1983 · N15351 · Destroyed