Fatal NTSB investigations: Lycoming TI0-540 series
11 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1993 | 2 |
| 1998 | 1 |
| 2001 | 1 |
| 2002 | 2 |
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 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')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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 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')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 CHI02FA292Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Ankeny, IAThe pilot applied an excessive angle of bank and failed to maintain terrain clearance. An additonal factor was the pilot's attention being diverted.NTSB SEA02GA053Accident · 3 fatalFinal reportPiper PA-31 · Atlanta, IDThe pilot's failure to maintain aircraft control while in cruise flight which resulted in the in-flight separation due to overload of the spar at the right wing root. Hypoxia was a factor.NTSB CHI02FA042Accident · 2 fatalField investigationFinal reportMooney M20M · Evansville, INThe fatigue failure of the turbocharger exhaust band clamp and aircraft control not possible by the pilot due to the fire.NTSB FTW98FA325Accident · 1 fatalField investigationFinal reportCommander 114TC · West Jordan, UTA brittle fracture of the clamp that joins the exhaust pipe to the turbocharger. The pipe separated and hot exhaust gases escaped into the engine compartment. The engine lost power due to the high heat vaporizing fuel in the fuel line. Factors were inadequate…NTSB ATL94FA029Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Covington, GASpatial disorientation experienced by the pilot, resulting in his failure to maintain aircraft control. Factors were the total failure of the engine driven vacuum pump, and the night, cloud conditions prevailing at the time of the accident.NTSB BFO93FA167Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Marshall, VAAn inadequate annual inspection of the airplane and non-compliance with airworthiness directives by company maintenance personnel.NTSB DEN91FA065Accident · 1 fatalField investigationFinal reportPiper PA-31B-310 · Bennett, COIn-flight separation of the left engine cowl assembly that was not properly latched, and failure of the pilot to maintain minimum control speed, which resulted in his loss of aircraft control. Factors related to the accident were: an inadequate preflight…NTSB ANC90LA173Accident · 2 fatalLimited investigationFinal reportPiper PA-32RT-300T · Glacier Island, AKUndetermined mechanical failure(s) that resulted in loss of engine power, smoke in the cockpit, and a subsequent emergency descent for a forced landing (ditching) at sea. The lack of suitable terrain for a forced landing was a related factor.NTSB MIA88FA201Accident · 1 fatalField investigationFinal reportSmith, Ted Aerostar Aerostar 600 · Catano, PRAs the acft was taxiing for takeoff, witnesses noted the l rear baggage door was unlocked & hanging down. A warning was relayed to the plt via the twr, but by then the acft was airborne & the plt had rprtd a control prblm. Drg lift-off, theacft pitched up…NTSB FTW83FA415Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Huffman, TXThe acft collided with the ground in a high speed dive and totally disintegrated. Impact created a 7' crater and material blew out for 100 yards. The engines were recovered at the 14 ft level in the crater. The acft took off at 2215 from baytown TX. At 2334…NTSB ATL83FA041Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Culpepper, VAAbout 16 min after takeoff the plt reported to ARTCC that he had lost the artificial horizon, gyro & vacuum pump. Radio & radar contact was lost shortly thereafter. Examination of the vacuum pump failed to reveal a pre-impact failure or malfunction. The acft…