NTSB investigations: Lycoming 0-235 series, 2005

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

19822026
NTSB investigations: Lycoming 0-235 series, 2005 per year, 1982–2026: 468 cases
198233
198323
198433
198522
198627
198730
198835
198919
199015
199116
199211
199319
199417
199528
199614
199713
199813
199913
200012
200114
200211
20038
200411
200514
20067
200710

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\") = 2005
    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\" = 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 DFW06CA044Accident · No injuriesData collectionFinal reportChampion 7ECA · Fredericksburg, TXThe pilot's failure to maintain directional control on the landing roll-out. A factor was the crosswind.Dec 29, 2005 · N7569F · Substantial damageNTSB MIA06CA025Accident · No injuriesData collectionFinal reportPiper PA-12 · St. Petersburg, FLThe pilot's failure to maintain directional control during the landing roll resulting in substantial damage during a ground loop.Nov 12, 2005 · N2969M · Substantial damageNTSB CHI06CA017Accident · No injuriesData collectionFinal reportBellanca 7ECA · Cuba, MOThe pilot's failure to maintain directional control of the airplane during the landing roll.Oct 26, 2005 · N5065N · Substantial damageNTSB SEA05CA156Accident · No injuriesData collectionFinal reportPiper PA-20-115 · Weiser, IDThe pilot's failure to maintain directional control during the landing roll, and his application of excessive braking as the aircraft started to depart the side of the runway.Jul 30, 2005 · N7004K · Substantial damageNTSB SEA05CA154Accident · Minor injuriesData collectionFinal reportGrumman American AA1B · Camas, WAThe student pilot's failure to maintain aircraft control during landing roll. A contributing factor was the gusty cross-wind weather condition.Jul 28, 2005 · N9861L · Substantial damageNTSB SEA05CA150Accident · No injuriesData collectionFinal reportAmerican Champion 7ECA · Hailey, IDThe pilot's inadequate recovery from a bounced landing and his failure to maintain directional control during the landing roll. Factors include a crosswind, and soft terrain just off the side of the runway surface.Jul 23, 2005 · N16JE · Substantial damageNTSB SEA05CA148Accident · No injuriesData collectionFinal reportPiper PA-16 · Park City, MTThe failure of the pilot to maintain directional control of the airplane on the takeoff roll. Factors contributing to the accident included the loose gravel, ditch, and the fence.Jul 20, 2005 · N5942H · Substantial damageNTSB ATL05CA120Accident · No injuriesData collectionFinal reportGrumman American AA-1B · Durham, NCThe pilot's failure to maintain directional control. Factors were soft and wet terrain.Jul 3, 2005 · N100XX · DestroyedNTSB MIA05CA128Accident · No injuriesData collectionFinal reportCessna 152 · St. Augustine, FLThe failure of the student pilot to maintain directional control during the landing roll resulting in the on-ground encounter with wet grass and subsequent nose over.Jul 2, 2005 · N89073 · Substantial damageNTSB DFW05CA154Accident · No injuriesData collectionFinal reportCessna 152 · Marietta, OKThe pilot's failure to maintain directional control while executing a soft field take off. A factor was the prevailing dark night conditions.Jun 11, 2005 · N47962 · Substantial damageNTSB SEA05CA096Accident · No injuriesData collectionFinal reportPiper PA-12 · Snohomish, WAThe pilot's failure to maintain aircraft control during the landing roll on a sandbar which resulted in the aircraft nosing over.May 11, 2005 · N7755H · Substantial damageNTSB DFW05CA108Accident · No injuriesData collectionFinal reportAircraft Mfg & Dev. CH-2000 · Panhandle, TXThe student pilot's improper compensation for existing wind conditions. Contributing factors were the crosswind and inadequate supervision by the flight instructor.Apr 25, 2005 · N215LF · Substantial damageNTSB DFW05CA101Accident · No injuriesData collectionFinal reportCessna 152 · Stillwater, OKThe student pilot's failure to maintain directional control during landing.Apr 8, 2005 · N68472 · Substantial damageNTSB ATL05CA070Accident · No injuriesData collectionFinal reportCessna 152 · Goose Creek, NCThe student pilot's failure to maintain direction control, which resulted in a loss of control and collision with a berm.Mar 30, 2005 · N714TK · Substantial damage