NTSB investigations: Lycoming TI0-540 series, 2004

6 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “In flight encounter with weather”. 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, 2004 per year, 1982–2026: 65 cases
19824
19833
19842
19853
19862
19873
19881
19894
19901
19923
19932
19942
19952
19961
19992
20002
20012
20024
20035
20046
20056
20062
20073

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\") = 2004
    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\" = 240))
  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 FTW04FA208Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Burnet, TXThe pilot's continued flight into known adverse weather, VFR flight into instrument meteorological conditions, and his failure to maintain control of the airplane due to spatial disorientation. A contributing factor was the cloudy weather.Aug 7, 2004 · N927RP · DestroyedNTSB NYC04FA170Accident · 5 fatalField investigationFinal reportPiper PA-32R-301T · Wheeling, WVThe pilot's failure to maintain terrain clearance while executing an instrument approach. A factor was the night instrument meteorological conditions.Jul 19, 2004 · N7710M · DestroyedNTSB MIA04FA100Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Baker, FLThe flight crew's inadvertent flight into thunderstorms resulting in the design limits of the airplane being exceeded, loss of aircraft control and subsequent in-flight breakup. A factor in the accident was the lack of required advisory by ATC about a radar…Jun 21, 2004 · N54134 · DestroyedNTSB ANC04LA059Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Goodnews, AKThe pilot's inadequate weather evaluation which resulted in an in-flight encounter with severe turbulence, and his exceedence of the design stress limits resulting in overstress of the wings. A factor contributing to the accident was the presence of…May 23, 2004 · N4105D · Substantial damageNTSB LAX04FA177Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Ukiah, CAThe non-instrument rated pilot's flight intentional flight into instrument meteorological conditions during takeoff-initial climb, which resulted in spatial disorientation, a subsequent loss of aircraft control, and an uncontrolled descent into terrain. A…Apr 4, 2004 · N4130D · DestroyedNTSB ANC04LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-31-350 · Koyukuk, AKThe pilot's continued flight into adverse weather conditions, and his failure to maintain clearance from terrain, which resulted in an in-flight collision with terrain. Factors associated with the accident were fog and whiteout weather conditions.Jan 2, 2004 · N45008 · Substantial damage