NTSB investigations: Lycoming I0360 SER A&C, 1993
11 cases on aircraft whose registry engine model is Lycoming I0360 SER A&C. 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
| 1966 | 1 |
|---|---|
| 1967 | 1 |
| 1969 | 3 |
| 1970 | 2 |
| 1971 | 1 |
| 1972 | 3 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 1 |
| 1976 | 8 |
| 1977 | 9 |
| 1978 | 5 |
| 1979 | 5 |
| 1980 | 8 |
| 1981 | 6 |
| 1982 | 18 |
| 1983 | 11 |
| 1984 | 12 |
| 1985 | 9 |
| 1986 | 13 |
| 1987 | 13 |
| 1988 | 9 |
| 1989 | 6 |
| 1990 | 12 |
| 1991 | 7 |
| 1992 | 6 |
| 1993 | 11 |
| 1994 | 5 |
| 1995 | 9 |
| 1996 | 6 |
| 1997 | 7 |
| 1998 | 9 |
| 1999 | 16 |
| 2000 | 10 |
| 2001 | 25 |
| 2002 | 25 |
| 2003 | 29 |
| 2004 | 32 |
| 2005 | 23 |
| 2006 | 19 |
| 2007 | 21 |
| 2008 | 12 |
| 2009 | 16 |
| 2010 | 17 |
| 2011 | 23 |
| 2012 | 13 |
| 2013 | 14 |
| 2014 | 11 |
| 2015 | 10 |
| 2016 | 19 |
| 2017 | 16 |
| 2018 | 14 |
| 2019 | 7 |
| 2020 | 11 |
| 2021 | 10 |
| 2022 | 7 |
| 2023 | 6 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 7 |
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\") = 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 ('41511'))
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 ('41511'))
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 CHI94LA054Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Lacon, ILThe pilot misjudged the landing flare. Factors related to the accident were: the dark night, the pilot's lack of recent night experience, and the failure of the airplane's electrical system.NTSB BFO94FA017Accident · 1 fatalField investigationFinal reportPiper PA-28RT-201 · Ravenna, OHThe pilot attempted to fly the airplane with known deficiencies in the attitude indicator and became spatially disoriented during the takeoff climb. Factors in the accident were the low ceiling, night conditions, and an inaccurate attitude indicator.NTSB SEA93LA172Accident · No injuriesLimited investigationFinal reportBeech 76 · Portland, ORJamming of the nose landing gear assembly and the pilot-in-command not maintaining the proper glidepath during the nose gear up landing.NTSB LAX93LA314Accident · No injuriesLimited investigationFinal reportMooney M20J · King City, CAthe pilot's loss of directional control during the takeoff ground roll due to the inadvertent interference with the controls by a passenger.NTSB CHI93LA285Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Crookston, MNThe pilot in command's delayed in-flight decision. A factor to the accident is the pilot in command's failure to attain a proper touchdown point.NTSB ANC93LA118Accident · No injuriesLimited investigationFinal reportLake LA4 · Turner Lake, AKPilot-in-command misjudged the landing flare on a glassy water landing. A factor in the accident was the glassy water condition.NTSB NYC93LA108Accident · Serious injuriesLimited investigationFinal reportMooney M20J · New Haven, CTThe loss of airplane control as a result of the pilot encountering spatial disorientation. Factors in this accident were the low ambient light conditions and the lack of runway end identifier lightsNTSB CHI93LA174Accident · Minor injuriesLimited investigationFinal reportLake LA-4-200 · Springport, MIA partial loss of engine power for undetermined reasons.NTSB BFO93LA067Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Willimantic, CTFailure of the pilot to follow emergency procedures to ensure that the gear was locked. A factor related to the accident was the total electrical failure and the construction site located beside the runway.NTSB DEN93LA037Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Eckert, COThe pilot-in-command's failure to maintain adequate clearance from the truck during the landing. Factors which contributed to the accident were: the pilot's poor judgement in attempting the operation, and the driver's poor judgement in not vacating all…NTSB CHI93LA076Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Streator, ILThe pilot's failure to perform a go-around. The tailwind and the pilot's selection of the downwind runway were factor.