NTSB investigations: Lycoming IO-360-A1B6D, 1992
5 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
Open the mapLatest 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\") = 1992
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") = 1992
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 DEN92LA059Accident · No injuriesLimited investigationFinal reportCessna 177RG · Gunnison, COThe pilot's failure to maintain directional control. Factor(s) included: fuel exhaustion and the misjudging of fuel consumption calculations.NTSB LAX92LA190Accident · No injuriesLimited investigationFinal reportCessna 177RG · Mammoth Lakes, CAThe pilot-in-command's inaccurate weather evaluation, his improper setting of the mixture control, and his failure to maintain proper climb airspeed. Factors related to the accident were: high density altitude, unfavorable wind with mountain wave activity and…NTSB SEA92LA068Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Scappoose, ORThe loss of engine power, cause undetermined. A factor relating to the accident was the lack of suitable terrain for a forced landing.NTSB DEN92LA037Accident · No injuriesLimited investigationFinal reportCessna 177RG · Durango, COA total loss of power due to a mechanical failure of the engine. Factors were: rough and uneven snow covered terrain.NTSB CHI92LA073Accident · No injuriesLimited investigationFinal reportCessna 177RG · Indianapolis, INEngine loss of power for undetermined reasons. The lack of suitable terrain for a forced landing was a factor.