Fatal NTSB investigations: Lycoming I0360 series, 1983
9 cases on aircraft whose registry engine model is Lycoming I0360 series. 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
| 1964 | 2 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1968 | 4 |
| 1969 | 2 |
| 1970 | 4 |
| 1971 | 1 |
| 1973 | 6 |
| 1974 | 6 |
| 1975 | 3 |
| 1976 | 5 |
| 1977 | 11 |
| 1978 | 11 |
| 1979 | 14 |
| 1980 | 12 |
| 1981 | 18 |
| 1982 | 7 |
| 1983 | 9 |
| 1984 | 6 |
| 1985 | 2 |
| 1986 | 6 |
| 1987 | 5 |
| 1988 | 8 |
| 1989 | 8 |
| 1990 | 3 |
| 1991 | 1 |
| 1992 | 6 |
| 1993 | 6 |
| 1994 | 4 |
| 1995 | 3 |
| 1996 | 4 |
| 1997 | 3 |
| 1998 | 7 |
| 1999 | 11 |
| 2000 | 6 |
| 2001 | 10 |
| 2002 | 9 |
| 2003 | 9 |
| 2004 | 12 |
| 2005 | 10 |
| 2006 | 10 |
| 2007 | 9 |
| 2008 | 5 |
| 2009 | 5 |
| 2010 | 6 |
| 2011 | 8 |
| 2012 | 6 |
| 2013 | 10 |
| 2014 | 11 |
| 2015 | 7 |
| 2016 | 5 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 8 |
| 2020 | 3 |
| 2021 | 6 |
| 2022 | 6 |
| 2023 | 4 |
| 2024 | 1 |
| 2025 | 6 |
| 2026 | 4 |
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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41515'))
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 NYC84FA032Accident · 2 fatalField investigationFinal reportBeech K35 · Stockholm, NJAt 1455 EST, a Beech K35 (bonanza), N106Q, & a Piper PA-34-200, N56670, collided while the acft were flying over the vicinity of the sparta VORTAC. The bonanza plt was on a local flt while the PA-34 was on multi-eng training flt. The student in the PA-34…NTSB CHI84FA027Accident · 2 fatalField investigationFinal reportMooney M20E · Newark, INThe acft had been recently purchased by the plt & this was the 2nd leg of a 3 leg trip which had originally departed hickory, NC. Two witnesses located about 5 mi sse of the accident site observed the acft. One witness stated the visibility was less than 1 mi…NTSB FTW84LAMS1Accident · 1 fatalFinal reportPiper PA-34-200 · Gulf Of MexicoThe acft disappeared on a flt over a part of the Gulf Of Mexico south of corpus christi in an area of thunderstorm activity. The storms were densely packed and it was considered unlikely that VFR flt could be conducted in the area. Theaccident acft was in…NTSB FTW83FA406Accident · 1 fatalField investigationFinal reportPiper PA 28R-200 · Copan, OKThe acft collided with an electric transmission line and burned during an emergency landing. The flt had been in progress only an hour when the plt lost his engine oil pressure and his engine failed. ATC gave him a heading to the nearest arpt but he could not…NTSB CHI83FA387Accident · 2 fatalField investigationFinal reportAerotek Pitts S-2A · Waukegan, ILWhile on a local flt, the acft crashed in lake Michigan about 1/2 mi from the shoreline. According to witnesses, it was flying over the water at about 100 ft, then pulled almost straight up to about 300 ft above the water, nosed over & went almost straight…NTSB DEN83FTG01Accident · 2 fatalFinal reportStolp SA750 · Harwood, NDThe acft impacted the ground in an inverted position in about a 30 degree nose down attitude. The acft was observed doing aerobatics with the last maneuver a spin. The acft spun to an out of sight position behind the trees and a crash was heard. The CFI on…NTSB CHI83FA213Accident · 1 fatalField investigationFinal reportMooney M-20-J-201 · Bloomington, ILPrior to the accident, a witness heard the acft, then saw it for a short time thru an opening in the clouds. In his opinion, it was heading directly into a thunderstorm, which concerned him. He said that rain was falling, and about 10 min later, the…NTSB FTW83FA149Accident · 3 fatalField investigationFinal reportPiper PA-34-200 · Kingston, OKThe acft rolled right after a premature liftoff due to a dip in the rwy. The acft continued to roll right until it impacted a 6 degree slope in a 100 degree nose down attitude. Investigation revealed that the right engine had suffered a power loss due to a…NTSB FTW83FA079Accident · 2 fatalField investigationFinal reportMooney M20E · Cushing, OKThe acft collided with a powerline during a low flt down a river. The acft impacted 3 high tension cables spanning the river. Witnesses said the acft was flying low and fast. The collision produced a sound 'like a gunshot' and the acft fell to the ground and…