Fatal NTSB investigations: Lycoming I0360 series, 2002
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
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\") = 2002
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") = 2002
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 FTW03FA029Accident · 1 fatalField investigationFinal reportCirrus Design SR20 · Las Vegas, NMThe pilot's inadvertent flight into instrument meteorological conditions and failure to maintain clearance with the terrain. A contributing factor was the pilot's failure to obtain an updated preflight weather briefing.NTSB SEA02FA185Accident · 2 fatalField investigationFinal reportCessna 172S · Medford, ORTerrain clearance was not maintained during cruise flight. Dark night and mountainous terrain were factors.NTSB NYC02FA200Accident · 1 fatalField investigationFinal reportMooney M20E · West Creek, NJThe pilot's inadequate preflight inspection which failed to detect water-contaminated fuel, and his failure to maintain airspeed.NTSB FTW02FA262Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Chromo, COThe flight instructor's failure to maintain clearance with the mountainous terrain during the cross-country flight. A contributing factor was the dark night light conditions.NTSB LAX02FA288Accident · 3 fatalField investigationFinal reportMooney M-20E · Carlsbad, CAfailure of the pilots of both airplanes to maintain an adequate visual lookout and to see and avoid each other. A contributing factor was the failure of the controller to detect and resolve the conflict between the airplanes.NTSB CHI02FA262Accident · 3 fatalField investigationFinal reportPiper PA-28R-180 · Newaygo, MIThe altitude/clearance disregarded by the pilot and his ostentatious display. The wire and low altitude flight were a contributing factor.NTSB LAX02FA255Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Echo Summit, CAThe pilot's decision to continue the flight into the rising mountainous terrain, and subsequent failure to maintain clearance with the trees. Contributing factors were the rising mountainous terrain, and the high density altitude,NTSB IAD02FA086Accident · 2 fatalField investigationFinal reportCessna 172S · Plainville, CTAn in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…NTSB NYC02FA142Accident · 2 fatalField investigationFinal reportBeech C24R · Grindstone, PAThe pilot's inadequate in-flight planning/decision resulting in flight into adverse weather, and his failure to maintain aircraft control resulting in overstress of aircraft. A factor was the thunderstorm activity.