NTSB investigations: Lycoming 0-235 series, 2004

7 cases on aircraft whose registry engine model is Lycoming 0-235 series, where the first occurrence was “Loss of control - in flight”. 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, 2004 per year, 1982–2026: 233 cases
19828
198319
198418
19857
198613
198710
19889
198915
19909
19918
19927
19934
19947
199510
19966
19976
19983
199910
200010
20017
200210
20037
20047
20059
200610
20074

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\") = 2004
    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\" = 250))
  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 CHI04LA285Accident · Minor injuriesLimited investigationFinal reportPiper PA-12 · Perham, MNThe dual student's improper compensation for the crosswind condition and his subsequent failure to maintain control of the airplane. An additional cause was the flight instructor's inadequate remedial action. A contributing factor was the crosswind condition.Sep 29, 2004 · N7977H · Substantial damageNTSB CHI04CA266Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Hurdland, MOThe pilot's failure to maintain proper airspeed and directional control during the takeoff and his failure to properly abort the takeoff after the encountered tailstrike. A factor to the accident was the stall/mush encountered during the attempted takeoff and…Sep 18, 2004 · N8275W · Substantial damageNTSB ANC04FA102Accident · 2 fatalField investigationFinal reportPiper PA-12 · Koliganek, AKThe pilot's failure to maintain adequate airspeed while on approach to land, which resulted in an inadvertent stall and an uncontrolled descent.Sep 4, 2004 · N2899M · DestroyedNTSB FTW04LA174Accident · Minor injuriesLimited investigationFinal reportGrumman AA-1 · Gordonville, TXThe pilot's premature lift-off and his failure to abort the takeoff. Contributing factors were the soft and muddy runway conditions and the unfavorable winds.Jul 4, 2004 · N6241L · Substantial damageNTSB FTW04LA138Accident · No injuriesLimited investigationFinal reportCessna 172 · Decatur, TXThe student pilot's failure to follow the flight instructor's instructions and relinquish the controls, and the flight instructor's delay in initiating a go-around.May 24, 2004 · N5302E · Substantial damageNTSB NYC04CA121Accident · No injuriesData collectionFinal reportCessna 152 · Pottstown, PAThe student pilot's failure to maintain directional control during landing, and the flight instructor's delayed remedial action.May 6, 2004 · N94577 · Substantial damageNTSB LAX04FA167Accident · 1 fatalField investigationFinal reportPiper PA-38-112 · Jean, NVThe student pilot's failure to regain control of the aircraft following an upset due to the disconnected primary right aileron control cable. The failure of the company maintenance personnel to detect and correct the improperly secured turnbuckle fitting at…Mar 19, 2004 · N2421D · Destroyed