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

7 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the first occurrence was “Loss of control - in flight”. 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, 2000 per year, 1982–2026: 203 cases
19829
19837
19848
19857
19868
19874
198811
19894
19905
19913
19924
19934
199410
19956
19966
19979
19988
19997
20007
20019
200211
200316
200413
200512
20067
20078

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\") = 2000
    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\" = 250))
  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 FTW01LA039Accident · No injuriesLimited investigationFinal reportRobinson R22 · Sunnyvale, TXThe flight instructor's inadequate supervision of his student and his failure to maintain control of the helicopter. Factors were the student pilot allowing the airspeed and main rotor RPM to get too low during the simulated emergency.Dec 17, 2000 · N7187W · Substantial damageNTSB DEN00FA169Accident · Serious injuriesField investigationFinal reportPiper PA-28-180 · Englewood, COthe pilot's failure to maintain aircraft control, which resulted in a collision with terrain. A contributing factor was the high-density altitude weather condition.Sep 11, 2000 · N2190R · DestroyedNTSB IAD00LA081Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Headwaters, VAPilot's failure to maintain aircraft control during take-off, which resulted in a stall.Sep 7, 2000 · N15275 · Substantial damageNTSB NYC00LA207Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Norwood, MAthe pilot's improper bounced landing recovery. A factor was the pilot's lack of total flight experience.Jul 16, 2000 · N2176T · Substantial damageNTSB LAX00LA129Accident · No injuriesLimited investigationFinal reportRobinson R22B · San Diego, CAThe pilot's selection of an inadequate takeoff area which precluded his ability to remain in ground effect until entering translational lift and resulted in his failure to maintain main rotor rpm.Mar 11, 2000 · N7078B · Substantial damageNTSB MIA00LA089Accident · No injuriesLimited investigationFinal reportBeech 76 · Salisbury, NCThe flight instructors inadequate supervision of a dual student who attempted a go around using one engine which resulted in loss of control and impact with the ground.Feb 10, 2000 · N2007K · Substantial damageNTSB NYC00LA072Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Alton Bay, NHThe pilot's failure to maintain control of the airplane during takeoff which resulted in an inadvertent stall. A factor in the accident was the pilot's inadequate compensation for the wind conditions.Feb 5, 2000 · N6577P · Substantial damage