NTSB investigations: Lycoming O&VO-360 series, 2002

8 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the first occurrence was “In flight collision with terrain/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 O&VO-360 series, 2002 per year, 1982–2026: 98 cases
19825
19834
19848
19855
19866
19874
19881
19891
19905
19933
19948
19952
19962
19972
19984
19992
20004
20014
20028
20034
20045
20057
20063
20071

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\") = 2002
    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')
      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\" = 230))
  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 NYC03LA029Accident · Serious injuriesLimited investigationFinal reportRobinson R-22 · Suffolk, VAThe pilot's inadequate visual lookout while landing, which resulted in a collision with an embankment.Dec 12, 2002 · N9444Y · Substantial damageNTSB SEA02FA180Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Yellow Pine, IDThe pilot's failure to maintain clearance from trees. A factor was trees south of the departure end of the runway.Sep 25, 2002 · N7027W · DestroyedNTSB DEN02FA089Accident · 4 fatalField investigationFinal reportMooney M20A · Marysvale, UTthe pilot's poor in-flight decision to fly so close to the ridge (looking for animals). Contributing factors were the mountainous terrain condition, the downdraft weather conditions in high mountains, and the high density altitude weather condition.Aug 9, 2002 · N1088B · DestroyedNTSB FTW02FA222Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Gypsum, COThe pilot's failure to perform remedial action and maintain clearance with the rising mountainous terrain. Contributing factors were the pilot's poor planning/decision, the rising terrain, and the high density altitude.Aug 1, 2002 · N6444J · DestroyedNTSB LAX02FA200Accident · 2 fatalField investigationFinal reportGrumman American AA-5B · Santa Paula, CAthe pilot's attempted VFR flight into instrument conditions and failure to maintain clearance with the terrain.Jun 7, 2002 · N13GT · DestroyedNTSB ATL02LA085Accident · Minor injuriesLimited investigationFinal reportPitts S1C · Gainesville, FLThe pilot's failure to maintain clearance from the ground during an attempted go-around.Apr 15, 2002 · N91GD · Substantial damageNTSB CHI02LA101Accident · Minor injuriesLimited investigationFinal reportBeech C23 · Kahoka, MOThe improper soft field takeoff/procedure by the pilot. Contributing factors were the night condition and the inadequate planning/decision by the pilot.Apr 5, 2002 · N2258L · DestroyedNTSB SEA02LA026Accident · Minor injuriesLimited investigationFinal reportRobinson R22 Beta · Renton, WAThe flight instructor's failure to ensure that adequate altitude/clearance above the ground was maintained during hovering flight, resulting in an inadvertent ground contact and subsequent loss of control of the helicopter. A factor was the flight…Jan 11, 2002 · N7185A · Substantial damage