NTSB investigations: Lycoming IO-360-A1B6D, 2000

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, 2000 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\") = 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 ('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 LAX01LA062Accident · No injuriesLimited investigationFinal reportCessna 177RG · San Carlos, CAA loss of engine power for undetermined reasons during an extended downwind leg in the landing pattern.Dec 21, 2000 · N2102Q · Substantial damageNTSB CHI01LA035Accident · No injuriesLimited investigationFinal reportCessna 177RG · Wautoma, WIthe deer that traveled onto the runway and contacted the airplane. Factors associated with the accident were the night light conditions and the light snow that was falling.Nov 18, 2000 · N8027G · Substantial damageNTSB NYC00LA253Accident · No injuriesLimited investigationFinal reportCessna 177RG · Elmer, NJThe instructor's failure to take remedial action.Sep 7, 2000 · N2156Q · Substantial damageNTSB FTW00LA258Accident · No injuriesLimited investigationFinal reportCessna 177RG · Mountain Home, ARThe failure of the landing gear to extend due to the empty hydraulic reservoir.Sep 7, 2000 · N2035Q · Substantial damageNTSB CHI00FA123Accident · 1 fatalField investigationFinal reportCessna 177RG · Watertown, SDthe pilot failed to maintain aircraft control due to spatial disorientation. Factors relating to the accident were the dark night, clouds, and rain.Apr 27, 2000 · N1978Q · DestroyedNTSB MIA00FA126Accident · 1 fatalField investigationFinal reportCessna 177RG · Chipley, FLThe failure of the pilot to maintain runway alignment during the initial climb from the grass airstrip. Also, the excessive pull-up by the pilot and inadvertent stall. Findings in the investigation were 1) in-flight collision with the tops of trees and 2) the…Apr 3, 2000 · N1997Q · Substantial damageNTSB NYC00LA103Accident · Serious injuriesLimited investigationFinal reportCessna 177RG · Renick, WVThe pilot's improper weather evaluation, and subsequent improper decision to fly into forecast and known icing conditions that exceeded the capability of the airplane to maintain flight. A factor was the icing conditions.Mar 28, 2000 · N1830Q · Substantial damageNTSB MIA00FA117Accident · 1 fatalField investigationFinal reportCessna 177RG · Columbia, SCThe PIC's inadequate planning and preparation resulting in refueling not being performed and the subsequent fuel exhaustion and forced landing into trees. A factor in the accident was the erratic operation of the right fuel tank quantity indicating system.Mar 22, 2000 · N1556H · Destroyed