Fatal NTSB investigations: Lycoming TI0-540 series, 2003
12 cases on aircraft whose registry engine model is Lycoming TI0-540 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 | 1 |
|---|---|
| 1966 | 3 |
| 1968 | 5 |
| 1969 | 3 |
| 1970 | 1 |
| 1971 | 4 |
| 1972 | 6 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 4 |
| 1976 | 5 |
| 1977 | 6 |
| 1978 | 14 |
| 1979 | 12 |
| 1980 | 16 |
| 1981 | 13 |
| 1982 | 15 |
| 1983 | 13 |
| 1984 | 9 |
| 1985 | 7 |
| 1986 | 9 |
| 1987 | 10 |
| 1988 | 6 |
| 1989 | 8 |
| 1990 | 2 |
| 1991 | 8 |
| 1992 | 6 |
| 1993 | 8 |
| 1994 | 8 |
| 1995 | 3 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 6 |
| 1999 | 6 |
| 2000 | 6 |
| 2001 | 14 |
| 2002 | 17 |
| 2003 | 12 |
| 2004 | 16 |
| 2005 | 12 |
| 2006 | 13 |
| 2007 | 7 |
| 2008 | 11 |
| 2009 | 10 |
| 2010 | 9 |
| 2011 | 8 |
| 2012 | 14 |
| 2013 | 7 |
| 2014 | 12 |
| 2015 | 10 |
| 2016 | 5 |
| 2017 | 4 |
| 2018 | 7 |
| 2019 | 6 |
| 2020 | 7 |
| 2021 | 6 |
| 2022 | 7 |
| 2023 | 9 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 6 |
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\") = 2003
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 ('41533'))
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") = 2003
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 ('41533'))
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 MIA04FAMS1Accident · 1 fatalMissing aircraftFinal reportPiper PA-32-300 · Missing, BahamasUndetermined.NTSB ATL04FA016Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Cordesville, SCThe pilot's failure to maintain adequate airspeed, which resulted in an inadvertent stall and subsequent uncontrolled descent into trees and the ground. A factor was physical impairment.NTSB LAX04FA001Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Corona, CAfailure of the turbocharger exhaust clamp due to a pre-existing weld crack, which allowed the release of high temperature exhaust gasses in the engine compartment, causing an in-flight fire.NTSB SEA03FA173Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Warm Lake, IDThe pilot's failure to maintain adequate airspeed during final approach resulting in a stall/spin. Contributing factors were the rapidly rising terrain and trees.NTSB MIA03FA167Accident · 2 fatalField investigationFinal reportPiper PA-31 · Clearwater, FLThe failure of the flightcrew to maintain airspeed (Vs) resulting in an inadvertent stall, uncontrolled descent, and in-flight collision with the ground.NTSB ATL03FA114Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Scottsboro, ALThe pilot's improper fuel management which resulted in a loss of engine power due to fuel starvation and subsequent impact with trees.NTSB LAX03FA166Accident · 4 fatalField investigationFinal reportRockwell 114 · Bishop, CAThe pilot's failure to maintain an adequate airspeed while maneuvering close to the ground over mountainous terrain in a high density altitude environment near the upper performance capability of the airplane, which resulted in an inadvertent stall/mush into…NTSB ATL03FA089Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Calhoun, GAThe pilot's failure to obtain a preflight weather briefing, which would have indicated that MVFR to IFR conditions prevailed over the route with embedded thunderstorms and rain, and his decision to continue VFR flight into instrument meteorological…NTSB NYC03FA061Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Monterey, MAThe pilot's improper decision to attempt a visual flight rules (VFR) flight in marginal VFR weather conditions over mountainous terrain, which resulted in an in-flight collision with trees. Factors in this accident were clouds and night light conditions.NTSB ATL03FA049Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Sylvania, GAThe pilot's decision to conduct VFR flight into instrument meteorological conditions, and his failure to maintain obstacle clearance. Related factors were the guy wire and the fog.NTSB MIA03LA061Accident · 4 fatalLimited investigationFinal reportPiper PA-23-250 · Miami, FLThe non instrument-rated pilot-in-command's improper inflight planning/decision, and continued VFR flight into instrument meteorological conditions, which resulted in a loss of control during descent, and impact with water.NTSB LAX03FA076Accident · 2 fatalField investigationFinal reportPiper PA-60-601P · Scottsdale, AZthe pilot's failure to maintain an adequate altitude clearance from mountainous terrain. Contributing factors were dark night conditions, mountainous terrain, and the pilot's diverted attention.