NTSB investigations: Lycoming O&VO-360 series, 2001, MI

5 cases on aircraft whose registry engine model is Lycoming O&VO-360 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 O&VO-360 series, 2001, MI per year, 1964–2026: 159 cases
19642
19653
19669
196711
19685
19696
19707
19718
19724
19736
19741
19756
19766
19775
19784
19792
19803
19813
19822
19831
19853
19862
19903
19912
19925
19932
19942
19953
19961
19971
19981
19992
20015
20022
20056
20062
20082
20091
20101
20122
20134
20141
20151
20172
20192
20221
20233
20241
20251
20261

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\") = 2001
    AND c.\"eventStateOrRegion\" = 'MI' 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 ('41514'))
  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 CHI01LA304Accident · No injuriesLimited investigationFinal reportBeech C23 · St. Helen, MIThe pilot's failure to attain the proper airspeed which resulted in a premature lift-off and subsequent stall/mush. A factor to the accident was the fence.Sep 3, 2001 · N9310S · Substantial damageNTSB CHI01LA266Accident · No injuriesLimited investigationFinal reportGrumman AA-5B · Beaver Island, MIThe pilot misjudged the approach and landing, and his failure to abort the landing. Factors associated with the accident were the trees at the approach end of the runway and the sand/gravel pit that the airplane traveled into.Aug 5, 2001 · N4545T · Substantial damageNTSB CHI01LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Brooklyn, MIThe proper touchdown point exceeded, all of the available runway not used, and aircraft control not being maintained by the pilot during the landing. Factors to the accident were the pilot mistaking the taxiway for the runway, the pilot not performing a…Jun 24, 2001 · N8210Z · Substantial damageNTSB CHI01LA081Accident · No injuriesLimited investigationFinal reportCessna 172RG · Troy, MIthe excessive touchdown airspeed and the directional control not maintained by the pilot. The snow bank was a contributing factor.Feb 3, 2001 · N369ER · Substantial damageNTSB CHI01LA106Accident · No injuriesLimited investigationFinal reportCessna 172RG · Sunfield, MIThe pilot's inadequate preflight preparation and the unsuitable terrain for takeoff encountered. Factors included the slushy runway and the snowbank.Jan 31, 2001 · N6448V · Substantial damage