Fatal NTSB investigations: Lycoming TI0-540 series, AK
6 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
| 1990 | 1 |
|---|---|
| 1993 | 1 |
| 1997 | 1 |
| 2008 | 1 |
| 2019 | 1 |
| 2026 | 1 |
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 c.\"eventStateOrRegion\" = 'AK' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'AK' AND c."eventCountry" = 'USA'
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 ANC26FA091Accident · 4 fatalClass 3 · FieldPreliminary reportPiper PA-24-260 · Seldovia, AKOn August 26, 2026 about 1317 Alaska daylight time, a Piper PA-24-260 airplane, N9485P, was substantially damaged when it was involved in an accident near Seldovia, Alaska. The pilot and three passengers were fatally injured. The airplane was operated as a…NTSB ANC20FA007Accident · 3 fatalClass 3 · FieldFinal reportPiper PA-31-350 · Cooper Landing, AKThe pilot’s failure to maintain clearance from terrain during gusty wind and reduced visibility night conditions.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…NTSB ANC97FA097Accident · 4 fatalField investigationFinal reportPiper PA-32 · Skagway, AKjamming/failure of the left magneto impulse coupling, which stopped rotation of the magneto gear, and resulted in subsequent shearing of the accessory intermediate idler gear. Factors relating to the accident were: the lack of suitable terrain for a forced…NTSB ANC93FA134Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Atigun Pass, AKThe pilot-in-command's intentional VFR flight into instrument meteorological conditions and his unfamiliarity with the geographical area. Factors were the rain and fog.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.