NTSB investigations: Lycoming TI0-540 series, 2006

5 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, 2006 per year, 1982–2026: 69 cases
19823
19834
19844
19856
19863
19871
19885
19891
19901
19913
19924
19934
19941
19951
19961
19974
19982
19992
20002
20012
20022
20031
20041
20055
20065
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\") = 2006
    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 CHI07LA002Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Marshall, MNThe failure of the nose gear to properly extend for undetermined reasons, which resulted in damage to the forward fuselage during landing.Oct 2, 2006 · N71TA · Substantial damageNTSB ANC06LA143Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Fairbanks, AKThe fracture of the aluminum alloy landing gear adapter assembly, which resulted in a loss of control during the landing roll.Aug 26, 2006 · N4466T · Substantial damageNTSB SEA06CA149Accident · No injuriesData collectionFinal reportMaule M-7-235C · Auburn, WAThe loss of directional control [not possible] during landing roll as a result of the disconnected tail wheel steering assembly [for undetermined reasons], which led to an inadvertent ground loop during the landing roll.Jul 26, 2006 · N15SN · Substantial damageNTSB NYC06CA080Accident · Serious injuriesData collectionFinal reportPiper PA23-250 · Morristown, NJThe pilot's premature shutdown of both engines, which resulted in a forced landing short of the runway. A factor was a landing gear malfunction indication for undetermined reasons.Mar 20, 2006 · N13878 · Substantial damageNTSB LAX06LA114Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Rancho Murieta, CAan electrical fault in the nose gear limit switch circuit, which lead to an intermittent failure of the landing gear extension system. Also causal was the pilot's failure to fully complete the emergency gear extension procedure. A factor in the accident was…Feb 14, 2006 · N9212P · Substantial damage