NTSB investigations: Lycoming IO-360-A1B6D, 1983
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
| 1971 | 1 |
|---|---|
| 1973 | 7 |
| 1974 | 4 |
| 1975 | 3 |
| 1976 | 10 |
| 1977 | 22 |
| 1978 | 8 |
| 1979 | 17 |
| 1980 | 8 |
| 1981 | 11 |
| 1982 | 11 |
| 1983 | 8 |
| 1984 | 6 |
| 1985 | 11 |
| 1986 | 12 |
| 1987 | 5 |
| 1988 | 14 |
| 1989 | 11 |
| 1990 | 3 |
| 1991 | 5 |
| 1992 | 5 |
| 1993 | 11 |
| 1994 | 6 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 3 |
| 1998 | 3 |
| 1999 | 7 |
| 2000 | 8 |
| 2001 | 7 |
| 2002 | 2 |
| 2003 | 5 |
| 2004 | 2 |
| 2005 | 7 |
| 2006 | 1 |
| 2007 | 8 |
| 2008 | 8 |
| 2009 | 4 |
| 2010 | 3 |
| 2011 | 4 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 2 |
| 2019 | 3 |
| 2020 | 9 |
| 2021 | 4 |
| 2022 | 5 |
| 2023 | 3 |
| 2025 | 3 |
| 2026 | 2 |
Where
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\") = 1983
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.
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") = 1983
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" DESCRun 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 DEN84LA026Accident · No injuriesLimited investigationFinal reportCessna 177RG · Durango, COThe acft ran off the right side of the rwy and collided with rwy lights during landing. The plt said he landed on the right side because the left side was being seal coated. Proper alignment was not maintained and the acft's right landing gear dropped off the…NTSB ATL83FA313Accident · Serious injuriesField investigationFinal reportCessna 177RGII · Atlanta, GAJust before rotation & during climbout from rwy 26L the eng started surging. The acft made a left turn, into the wind, & the student plt attempted to land on rwy 8R. The acft became misaligned, overshot the rwy, & made a hard landing in the grass about 200 ft…NTSB ANC83FA133Accident · No injuriesField investigationFinal reportCessna 177RG · Anchorage, AKDuring arrival, the acft was landed with the gear retracted. After touchdown, it slid appx 980 ft before coming to rest. The pilot stated that after he was cleared to land, he was looking for other VFR traffic & forgot to extend the gear. Reportedly, he did…NTSB ATL83IA234Incident · No injuriesIncident investigationFinal reportCessna 177RG · Ozark, ALWhile in cruise flight the engine failed to respond to throttle movement due to the throttle linkage being loose. Forced landing was made to a pasture.NTSB CHI83LA247Accident · No injuriesLimited investigationFinal reportCessna 177RG · Lansing, MIThe acft made a forced landing when the engine quit during the turn to final approach. Just prior to engine failure the pilot stated that he changed the fuel selector to what he believed to be the both tanks position but he actually turned it to the off…NTSB ANC83IA052Incident · No injuriesIncident investigationFinal reportCessna 177RG · Wasilla, AKThe pilot failed to extend the landing gear & the acft landed unintentional gear up.NTSB ANC83IA045Incident · No injuriesIncident investigationFinal reportCessna 177RG · Anchorage, AKThe acft was intentionally landed gear up due to a failure of the main landing gear actuator bearing. The bearing failed due to fatigue.NTSB LAX83FA091Accident · 3 fatalField investigationFinal reportCessna 177RG · Las Vegas, NVThe acft collided with a mountain during a night cross-country. The weather was VMC at takeoff but became IMC later nearthe mountains. A VFR flight plan was filed but never opened. The pilot continued flight into an area of known IMC conditions. He had…