NTSB investigations: Lycoming IO-540 series, FL

7 cases on aircraft whose registry engine model is Lycoming IO-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

19842026
NTSB investigations: Lycoming IO-540 series, FL per year, 1984–2026: 7 cases
19841
19862
20021
20052
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\" = 'FL' 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 ('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\" = 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 MIA06CA131Accident · No injuriesData collectionFinal reportCessna 182S · Fort Myers, FLThe pilot's failure to maintain control during the landing rollout during gusting wind conditions, which resulted in the airplane veering off the runway.Aug 17, 2006 · N250CS · Substantial damageNTSB MIA05CA099Accident · No injuriesData collectionFinal reportPiper PA32-301 · Brooksville, FLThe pilot-in-command failure to maintain directional control during takeoff after landing, which resulted in the airplane exiting the runway.Apr 28, 2005 · N146SW · Substantial damageNTSB MIA05CA053Accident · No injuriesData collectionFinal reportLee Harold Swarthout Velocity Xlrg · Daytona Beach, FLThe failure of the pilot-in-command to maintain directional control of the airplane during the landing roll resulting in the on-ground collision with a fence and a ditch.Jan 21, 2005 · N121HS · Substantial damageNTSB MIA02LA097Accident · No injuriesLimited investigationFinal reportCessna 206H · Sarasota, FLThe pilot's failure to maintain compensation for surface wind conditions resulting in excessive taxi speed, a loss of control while taxiing, an excursion off the taxiway, collision with a concrete pad, and a nose over.May 22, 2002 · N24013 · Substantial damageNTSB MIA87LA055Accident · Minor injuriesLimited investigationFinal reportMaule M-7-235 · Ocala, FLThe acft dragged a wing during lndg according to the plts statement. The acft came to rest beside the rwy. The plt said he lost control of the acft due to a fuel imbalance. After the accident the left wing tip tank was found full of fuel. According to the…Dec 22, 1986 · N151CD · DestroyedNTSB MIA86LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Melbourne, FLThe plt stated that on his landing rollout he lost control of the acft & veered off the left side of rwy 9L collapsing the nose gear.Jan 24, 1986 · N2947U · Substantial damageNTSB MIA85LA045Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Cross City, FLPlt stated that after touchdown as braking was initiated the acft began to pull to the left. Right brake was applied with no correcting effect. The acft ran off the left side of the runway and the landing gear collapsed. Post crash exam of brakes revealed no…Nov 25, 1984 · N8248D · Substantial damage