NTSB investigations: Lycoming 0-235 series, 2001

7 cases on aircraft whose registry engine model is Lycoming 0-235 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-235 series, 2001 per year, 1982–2026: 159 cases
198210
19838
19844
19853
19865
19874
19885
19891
19905
19918
19926
19933
19943
19953
19963
19977
199810
19995
20009
20017
20024
20039
200411
200510
20065
200711

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 ('41505')
      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 FTW02LA046Accident · No injuriesLimited investigationFinal reportCessna 152 · Perry, TXThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for a forced landing.Nov 30, 2001 · N95565 · Substantial damageNTSB MIA02LA036Accident · Serious injuriesLimited investigationFinal reportGrumman American AA-1C · Pompano Beach, FLThe failure of the pilot-in-command to maintain airspeed (Vs), while maneuvering for an emergency landing, resulting in an inadvertent stall and subsequent in-flight collision with terrain. A contributing factor in the accident was the loss of engine power…Nov 29, 2001 · N9515U · Substantial damageNTSB FTW02LA042Accident · No injuriesLimited investigationFinal reportCessna 152 · New Braunfels, TXthe loss of engine power due to carburetor icing conditions while in cruise flight. A contributing factor was the lack of suitable terrain for the ensuing forced landing.Nov 22, 2001 · N48941 · Substantial damageNTSB CHI02FA033Accident · 2 fatalField investigationFinal reportZenair CH2000 · Wentzville, MOThe improper selection of the fuel selector which resulted in fuel starvation and subsequent engine failure. Factors were the unsuitable terrain for the forced landing encountered by the pilot and the night light condition.Nov 16, 2001 · N33ZA · DestroyedNTSB NYC02LA021Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Roanoke, VAThe failure of the pilot ensure the proper position of the fuel selector which resulted in fuel starvation. Factors were the improper placement of the fuel selector valve tank index, and the improper in-flight decision of the pilot to change tanks in…Nov 3, 2001 · N5207Z · Substantial damageNTSB CHI01LA198Accident · Minor injuriesLimited investigationFinal reportPiper PA-12 · Stillwater, MNThe loss of engine power for undermined reasons and the unsuitable terrain encountered during the forced landing. Additional factors included the power line and the trees.Jul 7, 2001 · N78495 · Substantial damageNTSB FTW01LA078Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Oklahoma City, OKthe loss of engine power during the initial takeoff climb for an undetermined reason, which resulted in a forced landing. A contributory factor to the accident was the lack of suitable terrain for the forced landing.Mar 14, 2001 · N757GP · Destroyed