NTSB investigations: Lycoming IO-360-A1B6D, 1995

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

19712026
NTSB investigations: Lycoming IO-360-A1B6D, 1995 per year, 1971–2026: 328 cases
19711
19737
19744
19753
197610
197722
19788
197917
19808
198111
198211
19838
19846
198511
198612
19875
198814
198911
19903
19915
19925
199311
19946
19958
19966
19973
19983
19997
20008
20017
20022
20035
20042
20057
20061
20078
20088
20094
20103
20114
20123
20132
20141
20152
20161
20173
20182
20193
20209
20214
20225
20233
20253
20262

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\") = 1995
    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'))
  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 BFO96LA017Accident · No injuriesLimited investigationFinal reportCessna 177RG · College Park, MDthe main landing gear retracted for undetermined reasons.Nov 2, 1995 · N2132Q · Substantial damageNTSB LAX96LA029Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Madera, CAFuel exhaustion due to the pilot's improper preflight planning and failure to ensure that adequate fuel was onboard to complete the flight. Darkness was a related factor.Oct 30, 1995 · N4110C · Substantial damageNTSB SEA95LA185Accident · 1 fatalLimited investigationFinal reportCessna 177RG · Thompson, UTthe pilot's continued flight into instrument meteorological conditions, and his failure to maintain altitude and clearance from the mountainous terrain. Factors contributing to the accident were the fog, low ceilings, and downdraft.Aug 20, 1995 · N1930Q · DestroyedNTSB CHI95LA263Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Delavan, WIthe pilot's failure to assure an adequate amount of fuel was available for the flight. A factor was the improperly installed fuel level transmitter.Aug 8, 1995 · N9055J · DestroyedNTSB SEA95FA103Accident · 2 fatalField investigationFinal reportCessna 177RG · Kent, WAThe pilot's misjudgment of distance and altitude during the approach. Factors in the accident were the dusk light condition and the shadows.May 20, 1995 · N9ER · DestroyedNTSB LAX95LA187Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Oakland, CAThe pilot's poor preflight planning/preparation by exceeding the airplane certificated maximum allowable takeoff gross weight and failure to abort the takeoff in a timely manner. The ditch was a factor in this accident.May 14, 1995 · N34938 · DestroyedNTSB FTW95FA150Accident · 1 fatalField investigationFinal reportCessna 177RG · Dalhart, TXThe pilot's VFR flight into IMC conditions and the ensuing spatial disorientation. Factors were the pilot's self-induced pressure to reach his destination, his failure to obtain a weather briefing for the flight, and the weather conditions.Mar 30, 1995 · N35917 · DestroyedNTSB FTW95FA111Accident · 1 fatalField investigationFinal reportCessna 177RG · Larkspur, COThe pilot's decision to continue VFR flight into instrument meteorological conditions after being advised that VFR flight was not recommended. The weather and dark night were factors in the accident.Feb 9, 1995 · N33MR · Destroyed