NTSB investigations: Lycoming 0-320 series, NV

7 cases on aircraft whose registry engine model is Lycoming 0-320 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 0-320 series, NV per year, 1982–2026: 7 cases
19822
20001
20032
20041
20051

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 c.\"eventStateOrRegion\" = 'NV' 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 ('41508')
      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 LAX05LA318Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Pioche, NVcontrolled flight into mountainous terrain due to the pilot's inadequate preflight planning and preparation and his inadequate in-flight decisions, which created a low fuel state emergency situation that led directly to the CFIT during flight assist efforts…Sep 26, 2005 · N5031T · Substantial damageNTSB LAX04FA137Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Jean, NV!!This case was modified January 31, 2006!! the pilot's failure to maintain adequate clearance with the rising terrain, while maneuvering at low altitude in a mountainous area.Feb 16, 2004 · N9199Z · DestroyedNTSB LAX03LA294Accident · No injuriesLimited investigationFinal reportCessna 172N · Pahrump, NVthe pilot's failure to maintain altitude/clearance from the mountainous terrain while maneuvering, which resulted in an in-flight collision with terrain.Sep 21, 2003 · N6548D · Substantial damageNTSB LAX03FA100Accident · 2 fatalField investigationFinal reportCessna 172N · Ely, NVthe pilot's failure to maintain adequate terrain clearance while flying in a box canyon.Feb 23, 2003 · N9885J · Substantial damageNTSB LAX00TA212Accident · Minor injuriesFinal reportPiper PA-18-150 · Austin, NVLoss of engine power caused by a fuel soaked float pontoon causing an over rich fuel/air mixture, in a critical phase of flight.Jun 1, 2000 · N4872A · Substantial damageNTSB LAX83LVW02Accident · No injuriesFinal reportPiper PA-28-161 · Beatty, NVThe pilot landed on a 1700 long strip at the elevation of about 3500 ft MSL. He elected to takeoff to the north in calm wind conditions and avoid sun glare off the cover of his engine and on the windshield. He stated that soft field procedures were used in…Dec 19, 1982 · N8154X · Substantial damageNTSB LAX82DA060Accident · No injuriesFinal reportCessna 172M · Carson City, NVThe aircraft struck an 18 inch high frozen snow bank that a snow plow had left stretched across the approach end of runway 09. The pilot not able to see the snow bank due to fresh fallen snow. The right main gear was sheared off and the aircraft slid to a…Jan 22, 1982 · N13083 · Substantial damage