NTSB investigations: Lycoming TI0-540 series, 1995, FL
3 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 |
|---|---|
| 1965 | 3 |
| 1966 | 1 |
| 1967 | 4 |
| 1968 | 5 |
| 1969 | 2 |
| 1970 | 1 |
| 1971 | 2 |
| 1972 | 5 |
| 1973 | 6 |
| 1974 | 2 |
| 1975 | 2 |
| 1976 | 3 |
| 1977 | 3 |
| 1978 | 5 |
| 1979 | 6 |
| 1980 | 9 |
| 1981 | 4 |
| 1982 | 4 |
| 1983 | 5 |
| 1984 | 10 |
| 1985 | 9 |
| 1986 | 10 |
| 1987 | 8 |
| 1988 | 4 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 3 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 3 |
| 1995 | 3 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 2 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 4 |
| 2002 | 6 |
| 2003 | 6 |
| 2004 | 3 |
| 2005 | 9 |
| 2006 | 2 |
| 2007 | 1 |
| 2008 | 5 |
| 2009 | 3 |
| 2010 | 2 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 2 |
| 2020 | 3 |
| 2021 | 2 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 3 |
| 2025 | 3 |
| 2026 | 1 |
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\") = 1995
AND c.\"eventStateOrRegion\" = 'FL' AND c.\"eventCountry\" = 'USA'
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") = 1995
AND c."eventStateOrRegion" = 'FL' AND c."eventCountry" = 'USA'
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 MIA96LA055Accident · No injuriesLimited investigationFinal reportPiper PA-46 · Fort Myers, FLThe failure of the pilot-in-command to maintain directional control. Contributing to the accident was the inadequate amount of rudder input to compensate for engine torque during takeoff.NTSB MIA95LA166Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Orlando, FLUnknown.NTSB MIA95LA098Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Venice, FLFailure of the globe GC-1B (swift) pilot to see the Piper PA-23 in time to avoid a collision, and the Piper PA-23 pilot's delay in initiating remedial action to avoid the collision.