NTSB investigations: Lycoming 0-540 series, 2003

6 cases on aircraft whose registry engine model is Lycoming 0-540 series, where the first occurrence was “Loss of control - on ground/water”. 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 0-540 series, 2003 per year, 1982–2026: 84 cases
19827
19837
19843
19857
19862
19873
19883
19892
19903
19912
19924
19931
19944
19952
19964
19974
19982
19996
20012
20022
20036
20042
20052
20063
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\") = 2003
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41532')
      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\" = 260))
  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 ATL03LA123Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Greenville, NCThe pilot's failure to maintain directional control after an aborted landing and subsequent collision with an airport runway sign.Aug 4, 2003 · N6JH · Substantial damageNTSB MIA03LA145Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Fort Pierce, FLThe pilot's failure to maintain directional control of the airplane during landing roll resulting in collision with trees after the airplane departed the runway.Jul 20, 2003 · N5224Y · Substantial damageNTSB SEA03LA120Accident · No injuriesLimited investigationFinal reportMaule M-5-235C · Moses Lake, WAAn improper flare which resulted in a bounced landing during landing. The pilot's failure to maintain aircraft control and soft terrain were factors which eventually led to the aircraft nosing over.Jun 28, 2003 · N8070 · Substantial damageNTSB ATL03LA110Accident · No injuriesLimited investigationFinal reportPiper PA-28-236 · Hatteras, NCThe pilot's failure to maintain directional control during the landing roll. A factor was a go-around not performed.Jun 21, 2003 · N9234Z · Substantial damageNTSB DEN03LA080Accident · No injuriesLimited investigationFinal reportMaule MX-7-235 · Watkins, COthe pilot's failure to maintain directional control of the aircraft during the landing roll out. Contributing factors were the unlocked tailwheel.Apr 14, 2003 · N44UG · Substantial damageNTSB MIA03CA091Accident · No injuriesData collectionFinal reportMaule M-5-235C · Jay, FLThe failure of the pilot to perform a go-around after bouncing following touchdown, resulting in the airplane nosing over during the landing roll.Mar 27, 2003 · N366X · Substantial damage