NTSB investigations: Lycoming 0-235 series, 2005

11 cases on aircraft whose registry engine model is Lycoming 0-235 series, where the first occurrence was “Hard landing”. 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: 251 cases
198220
198322
198425
198512
19864
198720
198814
198912
19906
19917
19925
19938
19945
19956
199610
19978
19986
19997
20007
20017
20027
20037
20045
200511
20067
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\") = 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\" = 200))
  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 ATL06CA018Accident · No injuriesData collectionFinal reportCessna 152 · Durham, NCThe pilot's improper flare on landing flare touchdown resulting in a hard landing and collapse of the nose gear.Nov 5, 2005 · N5144L · Substantial damageNTSB MIA06CA012Accident · No injuriesData collectionFinal reportCessna 152 · Titusville, FLThe student pilot's inadequate recovery from a bounced landing resulting in substantial damage to the airplane.Oct 28, 2005 · N49005 · Substantial damageNTSB DFW05CA224Accident · No injuriesData collectionFinal reportCessna 152 · Tulsa, OKThe pilot's improper recovery from a bounced landing. A contributing factor was the dark night conditions.Aug 29, 2005 · N4670B · Substantial damageNTSB DFW05CA218Accident · No injuriesData collectionFinal reportCessna 152 · Bridgeport, TXThe pilot's inadequate compensation for wind conditions, and the flight instructor's delayed remedial action during a crosswind landing resulting in a loss of directional control.Aug 20, 2005 · N6459M · Substantial damageNTSB LAX05CA238Accident · No injuriesData collectionFinal reportCessna 152 · Rio Vista, CAthe student pilot's inadequate recovery from a bounced landing and his failure to maintain directional control of the airplane during landing rollout. A contributing factor was the student's failure to divert to an airport with less severe crosswind…Jul 18, 2005 · N68475 · Substantial damageNTSB ATL05CA134Accident · No injuriesData collectionFinal reportAircraft Mfg & Dev. CH2000 · Winston-Salem, NCThe student pilot's misjudged flare and his improper recovery from a bounced landing resulting in a stall and hard landing.Jul 18, 2005 · N240AM · Substantial damageNTSB NYC05CA112Accident · No injuriesData collectionFinal reportCessna 152 · Greenville, PAThe student pilot's improper flare, and inadequate recovery from a bounced landing, which resulted in a nose gear collapse while landing.Jun 23, 2005 · N46541 · Substantial damageNTSB DFW05CA164Accident · No injuriesData collectionFinal reportCessna 152 · Burneyville, OKThe students pilot's improper flare and his failure to maintain directional control of the airplane. A contributing factor was the bounced landing.Jun 16, 2005 · N93206 · Substantial damageNTSB ATL05CA097Accident · No injuriesData collectionFinal reportCessna 152 · Fort Payne, ALThe intentional unauthorized use of a stolen aircraft by an unqualified person which resulted in a hard landing and substantial damage to the airplane.Jun 16, 2005 · N5527M · Substantial damageNTSB CHI05CA107Accident · No injuriesData collectionFinal reportWhittman Tailwind · Lyndon, KSThe pilot improper recovery from a bounced landing, and his inadequate compensation for a tailwind, which resulted in a loss of control and subsequent collision with the ground. Contributing to the accident was the pilot's selection of a wrong runway, the…Apr 27, 2005 · N74849 · Substantial damageNTSB DFW05CA097Accident · No injuriesData collectionFinal reportCessna 152 · Shawnee, OKThe pilot's improper landing flare and his inadequate recovery from a bounced landing. A factor was the prevailing crosswind.Apr 2, 2005 · N5086Q · Substantial damage