NTSB investigations: Lycoming IO-540 series, 2004

6 cases on aircraft whose registry engine model is Lycoming IO-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 IO-540 series, 2004 per year, 1982–2026: 62 cases
19822
19832
19853
19862
19871
19882
19891
19912
19931
19942
19954
19964
19971
19983
19995
20001
20015
20026
20046
20052
20064
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 ('41530', '41585')
      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 NYC05CA037Accident · No injuriesData collectionFinal reportPiper PA-32RT-300 · Johnstown, NYThe pilot's inadequate in-flight planning/decision which resulted in airframe ice with subsequent degradation of aircraft performance, and inadequate airspeed during the landing flare.Dec 29, 2004 · N300WE · Substantial damageNTSB CHI04FA215Accident · 1 fatalField investigationFinal reportJorgensen Velocity XL-RG · Belvidere, KSThe non-instrument rated pilot's VFR flight into known instrument meteorological conditions and his failure to maintain aircraft control which resulted in an inverted flat spin, in-flight breakup, and explosion.Aug 7, 2004 · N190J · DestroyedNTSB DEN04LA086Accident · Minor injuriesLimited investigationFinal reportEagle DW-1 · Circleville, UTthe encounter with severe turbulence during aerial application and the pilot's inability to maintain aircraft control resulting in the in-flight collision with terrain. A contributing factor was the low altitude.Jun 7, 2004 · N8805D · DestroyedNTSB NYC04FA136Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Leominster, MAThe pilot's failure to follow instrument flight procedures resulting in a collision with trees. A factor related to the accident was the low cloud ceiling, and dark night.Jun 2, 2004 · N21072 · DestroyedNTSB ATL04FA093Accident · 3 fatalField investigationFinal reportCessna 182S · North Augusta, SCThe pilot's failure to maintain control of the airplane due to spatial disorientation, which resulted in an uncontrolled descent and subsequent in-flight collision with trees and the ground.Apr 12, 2004 · N364ME · Substantial damageNTSB NYC04FA092Accident · 6 fatalField investigationFinal reportPiper PA-32R-301 · Harlan, KYThe pilot's improper decision to continue VFR flight into IMC conditions and his failure to maintain terrain clearance, which resulted in controlled flight into terrain. Factors were night, snow and a low ceiling.Mar 22, 2004 · N8173U · Destroyed