Fatal NTSB investigations: Lycoming IO-360-A1B6D

7 cases on aircraft whose registry engine model is Lycoming IO-360-A1B6D, 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19862026

Fatal NTSB investigations: Lycoming IO-360-A1B6D per year, 1986–2026: 7 cases
1986	1
1988	1
1989	1
1991	1
1993	1
2003	1
2005	1

Where

Open the map

Latest cases

Query with SQL

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."highestInjuryLevel" = 'Fatal' AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41593') 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

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41593')
      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.

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."highestInjuryLevel" = 'Fatal'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41593')
    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

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB SEA05FA169Accident · 3 fatalField investigationFinal reportCessna 177RG · Cascade, IDThe pilot's failure to maintain clearance from a stand of conifer trees during low altitude maneuvering in mountainous terrain. Factors include the mountainous/hilly terrain, gusty winds, a high density altitude, and maneuvering at a low altitude.Aug 13, 2005 · N2082Q · Destroyed NTSB LAX03FA161Accident · 2 fatalField investigationFinal reportCessna 177RG · Ely, NVthe airplane collided with terrain for undetermined reasons.May 22, 2003 · N8034G · Substantial damage NTSB LAX94FA004Accident · 4 fatalField investigationFinal reportCessna 177RG · Petaluma, CAVFR flight by the pilot(s) into instrument meteorological conditions (IMC), and failure to maintain a proper altitude and/or clearance from terrain, while approaching the destination airport. Factors related to the accident were: the low ceiling and terrain.Oct 3, 1993 · N45022 · Destroyed NTSB SEA91FA183Accident · 4 fatalField investigationFinal reportCessna 177RG · Salmon, IDImproper inflight planning and decision by the pilot, and his failure to maintain sufficient altitude and clearance from mountainous/hilly terrain.Jul 22, 1991 · N1573H · Destroyed NTSB SEA89FA180Accident · 2 fatalField investigationFinal reportCessna 177RG · Nyssa, ORFailure of the pilot to attain sufficient altitude before flying over mountainous/hilly terrain. Factors related to the accident were: dark night, rising/mountainous terrain, and probable impairment from a prescription drug.Sep 29, 1989 · N8055G · Destroyed NTSB LAX88FA314Accident · 1 fatalField investigationFinal reportCessna 177RG · San Luis Obispo, CAPilots erroneous interpretation of his missed approach clearance, and, his performance of the published missed approach procedure for the santa maria ILS instead of the San Luis Obispo localizer.Sep 8, 1988 · N33283 · Destroyed NTSB ANC86FA130Accident · 3 fatalField investigationFinal reportCessna 177RG · Hinchinbrook Is, AKAt 1323 adt, the plt rprtd near Hinchinbrook island & requested clearance for an ndb-a apch to the cordova mile 13 arpt. About 3 min later, cordova fss provided clearance for the apch 'from over Hinchinbrook.' Radar data showed that the acft flew to the…Aug 19, 1986 · N52137 · Substantial damage