Fatal NTSB investigations: Lycoming I0360 series, 2001
10 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\") = 2001
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") = 2001
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 NYC02FA044Accident · 1 fatalField investigationFinal reportRaytheon BE-23-B24R · Armonk, NYThe pilot's failure to maintain aircraft control.NTSB IAD02FA024Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Milford, CTThe pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.NTSB SEA02LA012Accident · 1 fatalLimited investigationFinal reportThurston Pitts S-1S · Eatonville, WAThe pilot's unsuccessful corrective action (recovery) from an inverted spin. A contributing factor was the pilot's encounter with the inverted spin maneuver.NTSB CHI02FA001Accident · 1 fatalField investigationFinal reportEnstrom F-28A · Attica, MIThe reported loss of engine power due to fuel exhaustion during cruise flight, the pilot not performing an autorotation, the pilot not maintaining rotor RPM during his emergency descent, and the pilot not maintaining control of the helicopter. A factor was…NTSB NYC01FA217Accident · 2 fatalField investigationFinal reportCessna 172SP · Matawan, NJThe pilot's failure to maintain runway alignment during the initial climb. Factors were the pilot's failure to perform a go-around, the pilot's lack of flight experience in nighttime conditions, the nighttime conditions, and a tailwind.NTSB LAX01LA281Accident · 2 fatalLimited investigationFinal reportJohnson Lancair 360 · Placerville, CAIn-flight loss of control for undetermined reasons.NTSB NYC01FA172Accident · 1 fatalField investigationFinal reportBeech A23-24 · Bridgeville, DEThe pilot's incapacitation, which resulted in a loss of aircraft control while maneuvering. A factor was the FAA Aeromedical Certification Division's inadequate certification/approval of the pilot's medical certificate. Findings were the pilot's inappropriate…NTSB IAD01FA053Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Afton, VAThe pilot's loss of consciousness due to a medical condition, which resulted in his failure to maintain control of the airplane and subsequent impact with rising terrain.NTSB CHI01FA089Accident · 4 fatalField investigationFinal reportPiper PA-28R-201 · Webb Lake, WIthe pilot not maintaining altitude/clearance from the trees during takeoff. Factors were the trees, transmission wire, and the dark night.NTSB MIA01FA060Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Bethel, NCthe pilot's failure to maintain control of the airplane due to spatial disorientation, which resulted in an in-flight collision with power lines and the subsequent impact with terrain. A factor in this accident was: the pilot's lack of recent instrument…