NTSB investigations: Lycoming IO-360-A1B6D, 1989
11 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\") = 1989
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") = 1989
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 MIA90LA030Accident · No injuriesLimited investigationFinal reportCessna 177RG · Mims, FLA worn throttle control assembly that had failed.NTSB LAX90LA035Accident · Serious injuriesLimited investigationFinal reportCessna 177RG · Van Nuys, CAThe incorrect installation of the engine cowl and baffle seals during the installation of the engine following an overhaul.NTSB ATL90LA019Accident · No injuriesLimited investigationFinal reportCessna 177RG · Albertville, ALThe failure of maintenance personnel to properly inspect the magneto during a recent annual inspection.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.NTSB LAX89LA323Accident · No injuriesLimited investigationFinal reportCessna 177RG · Tucson, AZA loss of engine power due to the pilot's improper use of the aircraft's powerplant controls. A contributing factor was the pilot's limited experience in a Cessna 177RG.NTSB MIA89FA219Accident · 2 fatalField investigationFinal reportCessna 177RG · Janice, MSThe in flight loss of control by the non instrument rated pilot after encountering instrument meteorological conditions resulting in the airplane spiraling into a wooded area.NTSB DEN89LA183Accident · No injuriesLimited investigationFinal reportCessna 177RG · Brighton, COFailure of the landing gear down lock, which allowed the landing gear to collapse during the landing.NTSB LAX89LA208Accident · No injuriesLimited investigationFinal reportCessna 172N · Sacramento, CAThe pilot of the other aircraft displayed poor judgement when he elected to continue taxiing in the runup area when visual lookout could not be maintained.NTSB ATL89LA128Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Barnwell, SCThe pilot's poor in-flight planning/decision in continuing flight to the destination airport without refueling which resulted in fuel exhaustion. Unfavorable winds and inadequate fuel consumption calculations were contributing factors.NTSB CHI89FA058Accident · No injuriesField investigationFinal reportCessna 177RG · Rockford, ILThe inadequate servicing of the hydraulic fluid by maintenance personnel and the pilot's failure to extend the landing gear manually.NTSB ATL89IA104Incident · No injuriesIncident investigationFinal reportCessna 177RG · Savannah, GAFatigue-induced fracture of the main landing gear actuator rod end.