Fatal NTSB investigations: Lycoming TI0-540 series, 2008
11 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
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\") = 2008
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") = 2008
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 CEN09FA099Accident · 1 fatalField investigationFinal reportPiper PA-32R · North Canton, OHThe pilot’s inappropriate control inputs as a result of spatial disorientation, which led to an aerodynamic stall and loss of control. Contributing to the accident were the pilot's decision to conduct flight into known icing conditions, ice accumulation that…NTSB CEN09WA091Accident · 2 fatalClass 5 · ForeignPiper PA46 · Baden, AustriaNTSB LAX08FA286Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Las Vegas, NVA loss of power in the right engine due to an in-flight fuel-fed fire in the right engine compartment that, while the exact origin could not be determined, was likely related to the right engine-driven fuel pump, its fuel supply line, or fitting. Contributing…NTSB LAX08FA203Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Mount Charleston, NVThe pilot's failure to maintain clearance from mountainous terrain and his selection of a cruise altitude that provided inadequate terrain clearance. Contributing to the accident were the high density altitude and the rapidly rising terrain.NTSB DEN08FA114Accident · 2 fatalField investigationFinal reportAero Commander 500S · Linwood, KSThe pilot-in-training inadvertently shutting off both engine fuel control valves causing a loss of power in both engines, and the pilot's failure to maintain control of the airplane resulting in a stall. Contributing to the accident was the chief pilot's…NTSB MIA08FA115Accident · 3 fatalField investigationFinal reportCessna T206H · Cedar Key, FLThe pilot’s failure to maintain clearance from the water during a dark night approach to a coastal airport.NTSB DEN08WA094Accident · 2 fatalForeign investigationPiper PA-46-350P · Léguillac-de-l'Auche, FranceNTSB NYC08WA173Accident · 8 fatalClass 5 · ForeignPiper PA-31-310 · Maiquetia, VenezuelaOn April 28, 2008, about 1425 coordinated universal time (UTC), a Piper PA-31-310, N6463L, was destroyed during impact with residences, shortly after takeoff from Aeropuerto Internacional Del Centro Simon Bolivar (SVMI), Maiquetia, Venezuela. The certificated…NTSB MIA08FA094Accident · 2 fatalField investigationFinal reportMooney M20M · Midlothian, VAThe pilot’s improper control inputs resulting from spatial disorientation.NTSB DFW08FA056Accident · 1 fatalField investigationFinal reportAero Commander 500B · Tulsa, OKThe pilot's loss of control due to spatial disorientation and the pilot exceeding the design/stress limits of the aircraft. Factors contributing to the accident were the pilot's reported gyro problem, the dark night conditions , and prevailing instrument…NTSB ANC08MA038Accident · 6 fatalMajor investigationFinal reportPiper PA-31-350 · Kodiak, AKThe failure of company maintenance personnel to ensure that the airplane's nose baggage door latching mechanism was properly configured and maintained, resulting in an inadvertent opening of the nose baggage door in flight. Contributing to the accident were…