NTSB investigations: Lycoming 0-235 series, NC

8 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

19842026
NTSB investigations: Lycoming 0-235 series, NC per year, 1984–2026: 8 cases
19842
19871
19891
20001
20041
20052

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 c.\"eventStateOrRegion\" = 'NC' AND c.\"eventCountry\" = 'USA'
    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 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 ATL05CA021Accident · No injuriesData collectionFinal reportCessna 152 · Rocky Mount, NCThe pilot's improper landing flare, and improper recovery from a bounced landing.Nov 6, 2004 · N49196 · Substantial damageNTSB MIA00LA085Accident · No injuriesLimited investigationFinal reportCessna 152 · Louisburg, NCThe improper recovery from the bounced landing by the pilot-in-command for his failure to apply power and inadvertent stall by the pilot-in-command resulting in a hard landing. A contributing factor was the total lack of experience of the pilot-in-command.Feb 7, 2000 · N69174 · Substantial damageNTSB ATL89DMG04Accident · No injuriesFinal reportWittman, S.J. W-8 · Washington, NCPilot inadvertently stalled the airplane.Jul 17, 1989 · N74849 · Substantial damageNTSB ATL87LA264Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Winston Salem, NCThe student pilot was performing touch and go landings as part of his supervised solo training. The aircraft landed hard and bounced twice before coming to rest with a collapsed nose gear. Examination of the airframe disclosed extensive crushing damage to the…Sep 27, 1987 · N2488C · Substantial damageNTSB ATL85LA015Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Charlotte, NCDuring attempted go-around from a bounced landing, the plt allowed the acft to drift off center line and into trees paralling the runway. Directional control was compromised by low flying speed.Oct 20, 1984 · N2388V · Substantial damageNTSB ATL84LA162Accident · No injuriesLimited investigationFinal reportCessna 152 · Greensboro, NCThe student reported that he flared too high & the acft bounced about 4 times after which it left the rwy. The nose gear collapsed as it contacted mud beside the rwy.May 5, 1984 · N757AS · Substantial damage