Fatal NTSB investigations: Lycoming TI0-540 series, 1985
7 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\") = 1985
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") = 1985
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 LAX86FA069Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Newport Beach, CAThe plt contacted coast TRACON (terminal radar control) & requested VFR traffic advisories to torrence. At aprx 0747 psthe declared an emergency, said the eng had quit & requested vectors to the john wayne/orange county arpt. The controllerprovided a hdg to…NTSB LAX86LA033Accident · 3 fatalLimited investigationFinal reportPiper PA-32R-301T · San Diego, CAThe flt departed in VFR conditions after a wx briefing which indicated that clear skies and unrestricted visibilty existed and were forecasted at the destination airport. On arrival the plt requested and received clearance for an instrument apch. When the flt…NTSB NYC86FA027Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Landisburg, PAThe non-instrument rated pilot took off on a VFR crosscounty flight with no weather briefing. He flew into an area of adverse weather including low clouds, fog, drizzle & haze. The aircraft impacted near the top of a 2100 ft high hill in forested terrain.NTSB MIA86FA012Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Pensacola, FLAfter takeoff acft headed to destination arpt located 4 miles south. When aprx two miles out, the plt turned back to the departure arpt. Witnesses reported the acft was in a shallow descent, low and fast when it collided with trees and exploded about 1400 ft…NTSB BFO85FA067Accident · 2 fatalField investigationFinal reportBellanca 17-31A · Woodbridge, VAThe acft departed saratoga springs, NY, en route to manassas, VA. Wx was VFR and as the acft approached gaithersburg, MD, at 2132 LCL the plt contacted dulles apch for vectors through the area to manassas. The acft was issued a heading to manassas. Shortly…NTSB MKC85FA089Accident · 2 fatalField investigationFinal reportPiper PA-24-260 · Wakeeney, KSOn a x-country flt from dodge city, KS, to hill city, KS, the plt encountered IFR wx conditions around Wakeeney, KS. The IFR conditions were not forecast for his area of flt. A 2000 CST observation at hill city, KS, was indicating IFR conditions existing aprx…NTSB ATL85FA146Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Dundee, MSPlt obtained three preflight wx briefings then filed IFR using an assumed name. Routine communications until 2117 CST when pilot reported in a cell and said he wanted to make a 180 degree turn. Cleared for right turn. Radar and comm contact with aircraft lost…