NTSB investigations: Lycoming 0-540 series, 2001

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

19822026
NTSB investigations: Lycoming 0-540 series, 2001 per year, 1982–2026: 82 cases
19825
19835
19841
19855
19861
19871
19901
19913
19923
19931
19945
19952
19964
19974
19992
20003
20016
20029
20035
20046
20053
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\") = 2001
    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\" = 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 LAX02LA050Accident · No injuriesLimited investigationFinal reportCessna R182 · Santa Maria, CAInadequate maintenance and inspection of the engine dual magneto that resulted in a loss of engine power during a critical phase of flight, and the subsequent undershoot forced landing in soft terrain.Dec 17, 2001 · N7317X · Substantial damageNTSB MIA02LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Evans, GAThe pilot's improper fuel management and failure switch to the other fuel tank which had fuel available prior to the engine ceasing to operate, which resulted in fuel starvation and damage to the airplane during an off-airport landing.Nov 20, 2001 · N6688P · Substantial damageNTSB MIA02LA017Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Peachtree City, GAThe pilot’s attempted operation of the aircraft with known deficiencies in the engine ignition system resulting in failure of the engine due to ignition system failure and damage to the airplane during the subsequent forced landing.Nov 16, 2001 · N8183P · Substantial damageNTSB LAX02LA022Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Avalon, CAthe total loss of engine power during departure climb for undetermined reasons.Nov 4, 2001 · N3516W · Substantial damageNTSB MIA01LA145Accident · No injuriesLimited investigationFinal reportPiper PA-25-235 · Spartanburg, SCThe pilot's improper fuel management resulting in a total loss of engine power due to fuel exhaustion, forced landing, and subsequent in-flight collision with trees and terrain. Contributing to the accident was an unidentified pilot's failure to yield the…May 27, 2001 · N6667Z · Substantial damageNTSB LAX01LA097Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Petaluma, CAFailure of non-airframe and powerplant mechanic/certificated owners to properly install a new mixture cable that became entangled in the nose landing gear during its extension for landing, resulting in a loss of engine power.Feb 14, 2001 · N8286P · Substantial damage