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

9 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the first occurrence was “In flight collision with object”. 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, 2003 per year, 1982–2026: 92 cases
19825
19834
19844
19853
19862
19875
19882
19894
19905
19912
19932
19944
19953
19961
19972
19984
19993
20002
20015
20026
20039
20044
20053
20065
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\") = 2003
    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\" = 220))
  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 FTW04FA037Accident · 2 fatalField investigationFinal reportPiper PA-28-181 · Sugar Land, TXThe pilots failure to maintain clearance with powerlines during a VFR approach. Contributing factors were the prevailing dark night conditions,and the high winds.Dec 10, 2003 · N47413 · DestroyedNTSB NYC04LA007Accident · 1 fatalLimited investigationFinal reportPiper PA-28-180 · Cheswold, DEThe pilot's failure to maintain a proper glide path to the runway, and his failure to maintain obstacle clearance which resulted in an in-flight collision with an unlit utility pole. Factors related to the accident were the unlit utility pole, and the dark…Oct 12, 2003 · N5320L · Substantial damageNTSB NYC03LA198Accident · Serious injuriesLimited investigationFinal reportMooney M20A · Rockford, OHThe pilot's failure to maintain the proper altitude/clearance, which resulted in an in-flight collision with a utility wire. The owner's improper decision to allow the airplane to be operated by an uncertificated pilot was also causal.Sep 9, 2003 · N1072B · DestroyedNTSB DEN03LA108Accident · Minor injuriesLimited investigationFinal reportPiper PA 28-180 · Green River, UTpilot's improper preflight planning and failure to maintain obstacle clearance. Contributing factors include improper short field takeoff procedures and the high vegetation at the end of the runway.Jun 19, 2003 · N2537R · Substantial damageNTSB NYC03LA124Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Aurora, NYThe pilot's failure to obtain the proper climb rate.Jun 8, 2003 · N560FL · Substantial damageNTSB FTW03LA168Accident · No injuriesLimited investigationFinal reportRobinson R-22 Beta · Encinal, TXThe pilot's failure to maintain clearance from a tree. A contributing factor was the pilot's diverted attention.Jun 8, 2003 · N854WT · Substantial damageNTSB LAX03LA172Accident · No injuriesLimited investigationFinal reportPiper PA-44-180 · Livermore, CAthe pilots acceptance of a clearance meant for another aircraft. Contributing to the accident was the failure of departure controller to detect the pilot's incorrect read back and the controllers improper radio technique, which increased the chances of call…May 30, 2003 · N3060K · Substantial damageNTSB NYC03FA113Accident · 1 fatalField investigationFinal reportPiper PA-28-180 · Bruceton Mills, WVThe pilot's intentional decision to continue visual flight into instrument meteorological conditions, and his failure to maintain obstacle clearance which resulted in the airplane striking a guy wire on the communications antenna. A factor was the fog.May 21, 2003 · N55995 · DestroyedNTSB NYC03LA087Accident · No injuriesLimited investigationFinal reportRobinson R-22B · Waterford, PAThe pilot's inadequate visual lookout which resulted in the collision with the wire. Factors in the accident were the concealment of the poles by trees, the lack of contrast between the wire and grass field.Apr 20, 2003 · N7192M · Substantial damage