NTSB investigations: Lycoming TI0-540 series, CA

6 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “Loss of engine power”. 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

19852026
NTSB investigations: Lycoming TI0-540 series, CA per year, 1985–2026: 6 cases
19851
19871
19922
20012

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\" = 'CA' 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 ('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\" = 350))
  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 LAX01FA207Accident · No injuriesField investigationFinal reportPiper PA-46-350P · Stockton, CAa loss of engine power for undetermined reasons. Also causal was the inadequate supervision of the flight by the CFI for allowing a simulated emergency maneuver to continue below an altitude which would not allow for recovery contingencies.Jun 14, 2001 · N70SL · DestroyedNTSB LAX01LA166Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Napa, CAThe pilot-in-command's failure to verify the fuel supply before flight, and his improper fuel management, that resulted in fuel starvation and loss of engine power during takeoff climb resulting in a forced landing and collision with ground obstacles.May 6, 2001 · N8710P · Substantial damageNTSB LAX92LA299Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Shafter, CAThe pic's poor preflight planning and the pic's and flight instructor/passenger's failure to use the emergency checklist. The loss of engine power due to fuel starvation was a factor in the accident.Jul 16, 1992 · N327PL · Substantial damageNTSB LAX92LA239Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Chino, CAThe loss of engine power for undetermined reasons. The pilot's misjuding the flare was a factor.Jun 9, 1992 · N31961 · Substantial damageNTSB LAX87LA182Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Lincoln, CAThe aircraft collided with a ditch after a loss of pwr during t/o climb at aprx 350 to 400 ft AGL. The plt described the loss of pwr as 'like taking the throttle and pulling off in a rapid motion.' He noticed during his preflt check that the fuel in the right…Apr 19, 1987 · N15259 · Substantial damageNTSB LAX85LA143Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Hayward, CAWhile the instructor plt (CFI) & student were practicing landings, the eng lost power during the initial climb of the 4th touch-&-go at aprx 30 to 40 ft AGL. The CFI took control of the acft & attempted to land on the remaining rwy. However, the acft…Feb 16, 1985 · N4186W · Substantial damage