NTSB investigations: Lycoming 0-235 series, 1998, FL

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

19642026
NTSB investigations: Lycoming 0-235 series, 1998, FL per year, 1964–2026: 379 cases
19646
19657
19673
19683
19701
19715
19725
19733
19742
19753
19766
19774
197811
19793
19809
198111
198216
198311
198411
19859
19868
198712
19886
198914
19909
199113
19926
19937
199413
199510
19965
19978
19987
199911
20007
20017
20028
20035
20043
20058
20067
200710
20087
20096
20106
20112
20125
20131
20141
20153
20165
20176
20188
20196
20204
20212
20241
20253

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\") = 1998
    AND c.\"eventStateOrRegion\" = 'FL' 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'))
  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 ATL99FA016Accident · 1 fatalField investigationFinal reportCessna 152 · Daytona Beach, FLAn interior cabin fire of undetermined origin. A factor was the power lines impacted during the emergency descent.Nov 14, 1998 · N48882 · Substantial damageNTSB MIA99LA033Accident · No injuriesLimited investigationFinal reportCessna 152 · Coral Springs, FLThe delay by the pilot to obtain proper assistance after becoming lost/disoriented resulting in total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot's lack of total experience.Nov 12, 1998 · N65611 · Substantial damageNTSB MIA99LA032Accident · No injuriesLimited investigationFinal reportCessna 152 · Miami, FLThe loss of engine power due to a connecting rod failure for undetermined reasons. Contributing to the accident was the unsuitable terrain encountered during the forced landing.Nov 12, 1998 · N48013 · Substantial damageNTSB ATL98LA082Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Boynton Beach, FLThe pilot's inadequate preflight planning that resulted in a loss of engine power due to fuel exhaustion.Jun 13, 1998 · N46129 · Substantial damageNTSB ATL98LA058Accident · No injuriesLimited investigationFinal reportCessna 152 · La Belle, FLthe student pilot's inadequate compensation for wind conditions and failure to maintain directional control of the airplane. The gusty crosswind condition was a related factor.Mar 15, 1998 · N49551 · Substantial damageNTSB MIA98LA074Accident · No injuriesLimited investigationFinal reportCessna 152 · Orlando, FLThe CFI's improper planning and decision to taxi behind a multi-engine airplane conducting an engine run-up.Feb 8, 1998 · N89051 · Substantial damageNTSB MIA98LA050Accident · No injuriesLimited investigationFinal reportCessna 152 · Everglades City, FLthe pilot's inadequate compensation for wind conditions and failure to properly flare the airplane, which resulted in a hard landing and overload failure of the nose gear. The unfavorable wind conditions were related factors.Jan 2, 1998 · N757VT · Substantial damage