NTSB investigations: Lycoming TI0-540 series, 2016
21 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 | 9 |
|---|---|
| 1965 | 27 |
| 1966 | 32 |
| 1967 | 49 |
| 1968 | 48 |
| 1969 | 47 |
| 1970 | 48 |
| 1971 | 63 |
| 1972 | 45 |
| 1973 | 51 |
| 1974 | 62 |
| 1975 | 46 |
| 1976 | 52 |
| 1977 | 58 |
| 1978 | 68 |
| 1979 | 65 |
| 1980 | 57 |
| 1981 | 55 |
| 1982 | 47 |
| 1983 | 40 |
| 1984 | 46 |
| 1985 | 43 |
| 1986 | 43 |
| 1987 | 35 |
| 1988 | 33 |
| 1989 | 32 |
| 1990 | 16 |
| 1991 | 30 |
| 1992 | 30 |
| 1993 | 25 |
| 1994 | 26 |
| 1995 | 27 |
| 1996 | 31 |
| 1997 | 23 |
| 1998 | 22 |
| 1999 | 26 |
| 2000 | 36 |
| 2001 | 43 |
| 2002 | 46 |
| 2003 | 37 |
| 2004 | 41 |
| 2005 | 44 |
| 2006 | 49 |
| 2007 | 32 |
| 2008 | 33 |
| 2009 | 28 |
| 2010 | 34 |
| 2011 | 23 |
| 2012 | 31 |
| 2013 | 27 |
| 2014 | 25 |
| 2015 | 31 |
| 2016 | 21 |
| 2017 | 21 |
| 2018 | 22 |
| 2019 | 20 |
| 2020 | 29 |
| 2021 | 18 |
| 2022 | 28 |
| 2023 | 31 |
| 2024 | 15 |
| 2025 | 18 |
| 2026 | 19 |
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\") = 2016
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") = 2016
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 ERA17LA034Accident · No injuriesLimited investigationFinal reportPiper PA32 · Bartow, FLA total loss of engine power during approach for reasons that could not be determined because engine examinations did not reveal any evidence of mechanical malfunctions or failures that would have precluded normal operation.NTSB CEN17LA031Accident · No injuriesLimited investigationFinal reportPiper PA 28-236 · Lexington, MOA total loss of engine power during takeoff for reasons that could not be determined based on available information.NTSB CEN17LA019Accident · Serious injuriesLimited investigationFinal reportBellanca 17-31A · Mc Alester, OKA total loss of engine power during initial climb due to fuel starvation.NTSB ERA17LA006Accident · No injuriesLimited investigationFinal reportPiper PA24 · Hollywood, ALA failure of the fuel tank selector valve in a partially closed position, which resulted in fuel starvation to the engine and a total loss of engine power.NTSB GAA17CA007Accident · No injuriesData collectionFinal reportCessna T182 · Galesburg, ILThe pilot's improper landing flare, which resulted in a bounced, hard landing.NTSB ERA16LA331Accident · Minor injuriesLimited investigationFinal reportPiper PA32RT · Camden, SCA total loss of engine power due to the improper torqueing of the magneto, which led it to its malfunctioning in flight.NTSB CEN16LA375Accident · No injuriesLimited investigationFinal reportPiper PA 32R-300 · Grants, NMA loss of engine power for reasons that could not be determined based on the available information.NTSB ERA16FA289Accident · 6 fatalField investigationFinal reportPiper PA 31 · Northport, ALA total loss of power in both engines due to fuel starvation as a result of the pilot's fuel mismanagement, and his subsequent failure to follow the emergency checklist. Contributing to the pilot's failure to follow the emergency checklist was his lack of…NTSB ERA16LA258Accident · 1 fatalLimited investigationFinal reportPiper PA24 · Westwood, MAThe pilot's improper fuel management, which resulted in exhaustion of the fuel in the selected fuel tank and a total loss of engine power due to fuel starvation.NTSB ERA16FA215Accident · 2 fatalField investigationFinal reportPiper PA31 · State College, PAThe pilot's decision to continue an unstabilized instrument approach in instrument meteorological conditions, which resulted in controlled flight into terrain.NTSB GAA16CA278Accident · No injuriesData collectionFinal reportPiper PA24 · Wadsworth, OHThe pilot's inadvertent power reduction during landing, which resulted in a runway undershoot, collision with the runway threshold, nose and right main landing gear collapse, and runway excursion.NTSB CEN16LA192Accident · No injuriesLimited investigationFinal reportCessna T206H · New Roads, LAThe pilot’s failure to maintain directional control during the landing roll.NTSB CEN16LA186Accident · No injuriesLimited investigationFinal reportPiper PA 32R · Alpine, TXThe engine’s decreased performance due to high-density altitude conditions and a partially obstructed fuel injector nozzle. Contributing to the pilot's decision to perform an off-field landing was the anomalous high exhaust gas temperature reading.NTSB GAA16CA223Accident · No injuriesData collectionFinal reportCessna T206 · Jasper, TXThe pilot's failure to maintain pitch control during the landing flare, which resulted in abnormal runway contact, a nose wheel landing gear collapse, and runway excursion.NTSB GAA16CA222Accident · No injuriesData collectionFinal reportPiper PA32RT · Gainesville, GAThe pilot's failure to maintain an appropriate descent rate during the landing flare in gusty crosswind conditions, which resulted in a hard landing, left main landing gear collapse, and runway excursion.NTSB ERA16FA169Accident · 1 fatalField investigationFinal reportPiper PA32 · Boone, NCThe pilot's delayed decision to conduct a go-around following an unstabilized landing approach and his subsequent failure to maintain clearance from trees near the end of the runway.NTSB ERA16LA142Accident · Minor injuriesLimited investigationFinal reportPiper PA 23-250 · Danville, VAThe pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.NTSB WPR16LA073Accident · Minor injuriesLimited investigationFinal reportCessna T206H · Billings, MTThe pilot’s failure to attain a proper flare during landing in gusting wind conditions and low-level wind shear, which resulted in a hard landing and a subsequent loss of directional control.NTSB GAA16CA126Accident · No injuriesData collectionFinal reportPiper PA31 · Newport, RIAn inadvertent collision with birds during final approach at night.NTSB WPR16FA059Accident · 2 fatalField investigationFinal reportPiper PA 24-260 · Santa Rosa, CAThe pilot’s failure to maintain airplane control during an instrument approach in night instrument meteorological conditions, which resulted in a collision with terrain. Contributing to the accident was the pilot’s lack of recent experience in night…NTSB GAA16CA107Accident · Minor injuriesData collectionFinal reportPiper PA 46 · Ottawa, KSThe flight crews encounter with un-forecasted freezing rain resulting in an uncontrolled descent, forced landing, and substantial damage to the airplane's firewall, and forward pressure bulkhead.