NTSB investigations: Lycoming TI0-540 series, 1995
27 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\") = 1995
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."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 ATL96LA024Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Monroe, NCThe pilot's inadequate planning and failure to follow operating procedures resulted in his descent below the decision height while on final approach.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 LAX96FA050Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Fullerton, CAthe pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the pilot-in-command's self-induced pressure to get to work.NTSB NYC96FA012Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Atlantic Ocean (Atlantic Ocean)a total loss of left engine power as a result of an in-flight separation of the #2 cylinder. The cylinder separated due to high stress fatigue cracking of the cylinder hold down studs and the #3 main bearing thru-studs. Factors in this accident were: improper…NTSB BFO96IA012Incident · No injuriesIncident investigationFinal reportPiper PA-23 · Beckley, WVan in-flight fire (behind the right side of the instrument panel), which occurred for undetermined reason(s).NTSB CHI95LA300Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Osage Beach, MOthe student pilot's misjudgement of distance and speed during the landing and failure to attain the proper touchdown point.NTSB FTW95FA363Accident · Serious injuriesField investigationFinal reportPiper PA-32R-300 · Wichita Falls, TXthe pilot's failure to maintain airspeed while diverting attention to an open cargo door. A factor was the pilot's inadequate preflight inspection.NTSB CHI95LA283Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Ironwood, MIthe pilot's failure to maintain control of the airplane during the aborted takeoff. A factor was the partial loss of engine power for an undetermined reason.NTSB LAX95LA292Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Truckee, CAA failure in the aircraft electrical system, and the pilot's failure (or inability) to extend the landing gear with the emergency extension system. A factor relating to the accident was: the pilot's decision to continue the flight with a known deficiency.NTSB FTW95LA311Accident · No injuriesLimited investigationFinal reportBellanca 17-31ATC · Hico, TXThe pilot's failure to attain the proper touchdown point and the delayed go-around.NTSB LAX95LA251Accident · No injuriesLimited investigationFinal reportMooney M-20-M · Santa Monica, CAthe pilot's improper remedial action during an aborted takeoff due to an improperly installed pitot line to the airspeed indicator.NTSB MIA95LA170Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Winstonville, MSPoor preflight planning/preparation and clearance not maintained by the pilot in command.NTSB MIA95LA166Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Orlando, FLUnknown.NTSB MIA95LA156Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Atlantic Ocean (Atlantic Ocean)Loss of engine power for an undetermined reason(s).NTSB CHI95LA196Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Columbia, MOA loose (or missing) nut and clip for the bottom magneto stud, due to inadequate maintenance, and fatigue failure of the magneto housing flange, which restulted in an oil leak, engine compartment fire, and a forced landing. A factor relating to the accident…NTSB CHI95LA192Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Peru, ILthe pilot's failure to maintain directional control of the airplane while landing. A factor in the accident was the runway light.NTSB LAX95LA194Accident · Serious injuriesLimited investigationFinal reportAero Commander 500S · Santa Barbara, CAthe inadequate visual lookout by both pilots and their failures to maintain adequate separation from each other while taxiing in a non-movement area.NTSB CHI95LA234Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Michigan City, INreason for the occurrence was undetermined.NTSB ANC95LA050Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Dillingham, AKThe pilot's inadequate preflight planning and preparation. Factors associated with the accident are: the dispatcher's decision to dispatch a multi-engined airplane to a short, soft airstrip, and inadequate company management oversight/surveillance.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.NTSB CHI95LA086Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Minneapolis, MNan inadequate windshield deicing system for the inflight icing encountered, airframe icing, and the pilot's inability to maintain a proper descent rate. Factors associated with this accident were an inadequate weather forecast and icing conditions.NTSB FTW95LA113Accident · 1 fatalLimited investigationFinal reportPiper PA-32-300 · Howard, COThe pilot's flight into known adverse weather over mountainous terrain at an inadequate altitude to recover from turbulence/downdraft. Factors related to the accident were: inadequate preflight planning/preparation by the pilot, his inadequate weather…NTSB LAX95LA092Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Buckeye, AZa loss of engine power for undetermined reasons.NTSB SEA95LA044Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Salem, ORFuel starvation due to inadequate supervision of the dual student by the pilot-in-command when the dual student improperly adjusted the fuel selector position.NTSB SEA95LA039Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · La Grande, ORFailure of the pilot to maintain proper altitude/clearance from higher terrain that was located near the airport. Factors related to the accident were: low ceiling, fog, false/incorrect indication of the NDB, failure of other personnel to properly issue a…NTSB ANC95LA029Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Akiak, AKThe partial loss of engine power due to an erratic spark plug.NTSB FTW95LA085Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Brownsville, TXThe fuel starvation loss of engine power due to the pilot's improper use of the fuel tank selector. Factors were the pilot's qualification and the lack of suitable terrain for landing.