NTSB investigations: Lycoming IO-360-A1B6D, 1993
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\") = 1993
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") = 1993
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 FTW94FA057Accident · 3 fatalField investigationFinal reportCessna 177RG · Van Horn, TXThe pilot exceeded the design stress limits of the aircraft after a loss of control which resulted from VFR flight into instrument meteorological conditions. Factors were the weather, the pilot's lack of instrument training and experience, and his failure to…NTSB LAX94LA068Accident · No injuriesLimited investigationFinal reportCessna 177RG · Santa Monica, CAThe pilot's failure to attain the proper touchdown point and improper recovery from a bounced landing.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.NTSB ATL93LA154Accident · No injuriesLimited investigationFinal reportCessna 177RG · Valdosta, GAThe pilot's inadequate evaluation of inflight weather conditions which resulted in the inflight encounter with severe turbulence and subsequent overstress of the airframe.NTSB LAX93LA340Accident · No injuriesLimited investigationFinal reportCessna 177RG · Cameron Park, CAThe pilot's failure to assure that the landing gear was down and locked. Factors relating to this accident were the alternator failure due to a broken wire and the low battery output.NTSB CHI93LA310Accident · No injuriesLimited investigationFinal reportCessna 177RG · Emporia, KSThe pilot's selection of unsuitable terrain.NTSB CHI93LA284Accident · No injuriesLimited investigationFinal reportCessna 177RG · Columbus, INthe pilot in command's failure to maintain proper clearance. A factor involved in this accident is the pilot in command's failure to maintain a proper glidepath.NTSB BFO93WA141Accident · 4 fatalForeign investigationCessna 177RG · Marseille, FranceNTSB ATL93LA074Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Concord City, NCThe failure of the pilot to maintain control of the aircraft and his delayed decision to execute a go around. A factor in the accident was the strong gusty wind condition.NTSB LAX93LA163Accident · No injuriesLimited investigationFinal reportCessna 177RG · Imperial, CAThe flight's encounter with a dust devil.NTSB BFO93LA056Accident · No injuriesLimited investigationFinal reportCessna 177RG · Corry, PAFailure of the pilot to maintain runway alignment during the landing roll. Factors related to the accident were: darkness, the pilot's lack of visual cues due to the runway lights being obscured by the plowed snow, and failure of airport personnel to issue a…