NTSB investigations: Lycoming TI0-540 series, 1999
26 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\") = 1999
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") = 1999
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 LAX00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Fallbrook, CAthe pilot's misjudged altitude and distance during a night landing approach, which resulted in an undershoot.NTSB MIA00LA049Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300T · Fort Lauderdale, FLThe failure of the pilot to maintain minimum flying airspeed, (Vso) during takeoff following a partial loss of engine power resulting in the aircraft stalling, an uncontrolled descent, and collision with trees. A factor in the accident was the failure of the…NTSB LAX00LA043Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Scottsdale, AZThe pilot's failure to follow the manufacturer's published emergency procedures for engine loss of power resulting in a forced landing in an open construction area where the airplane collided with a berm. A related factor was the loss of engine power in the…NTSB MIA00FA043Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Pelham, ALThe student pilot's decision to continue the visual flight rules flight into deteriorating visibility, and his failure to maintain altitude clearance with the terrain.NTSB FTW00FA035Accident · 4 fatalField investigationFinal reportPiper PA-24-260 · New Orleans, LAthe pilot's failure to maintain aircraft control which resulted in a stall/spin. A contributing factor was the dusk light condition.NTSB CHI00LA029Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Romulus, MIthe inadvertent wheels-up landing by the pilot.NTSB ANC00LA004Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Soldotna, AKAn in-flight collision with a bird.NTSB MIA99WA254Accident · No injuriesForeign investigationPiper PA-23-250 · Gustavia, WNNTSB MIA99LA265Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Naples, FLThe pilot's failure to perform manual gear extension procedures with a suspected unsafe landing gear indication which resulted in a collapse of the main landing gear on landing rollout. A factor in the accident was the pilot's lack of total experience in kind…NTSB CHI99LA316Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Osceola, WIthe pilot's improper preflight decision to attempt a takeoff with one engine inoperative.NTSB CHI99LA256Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Salina, KSthe inadequate preflight inspection by the pilot. Factors to the accident were fuel exhaustion and the operation of the aircraft with known deficiencies in equipment by the pilot.NTSB FTW99FA199Accident · 2 fatalField investigationFinal reportSmith, Ted Aerostar Aerostar 601P · Bethany, OKThe pilot's failure to maintain the minimum controllable airspeed. A factor was the disconnected rubber interconnect boot, which resulted in the partial loss of left engine power.NTSB ANC99LA097Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Mcgrath, AKThe pilot's improper management of the fuel supply, and subsequent fuel starvation. A factor in the accident was unsuitable terrain for a forced landing.NTSB DEN99FA123Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Magdalena, NMThe pilot's inadvertent flight into adverse weather and the subsequent in-flight breakup. Factors were the pilot's lack of experience in high altitude flying and the thunderstorm.NTSB FTW99LA178Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Houston, TXThe pilot's failure to maintain the proper descent rate during a forced landing, which resulted in a runway undershoot. Factors were the total loss of engine power for an undetermined reason and the dusk light conditions.NTSB FTW99LA175Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Cabot, ARThe flight instructor's failure to attain the proper touchdown point during the landing.NTSB NYC99LA139Accident · No injuriesLimited investigationFinal reportAero Commander 500S · Windsor Locks, CTHydraulic system contamination which prevented normal landing gear extension. A factor was the misjudged landing flare by the flying pilot.NTSB DEN99FA081Accident · 2 fatalField investigationFinal reportPiper PA-23E-250 · Tucumcari, NMThe pilot's inadvertent stall. A factor was the loss of power of one engine in the twin-engine airplane.NTSB ATL99LA088Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Dickson, TNThe loss of engine power due to undetermined reasons. A factor was uneven terrain.NTSB MIA99LA155Accident · 1 fatalLimited investigationFinal reportAero Commander 500B · Atlantic Ocean (Atlantic Ocean)an in-flight collision with water for undetermined reasons, due to the wreckage never being recovered from the water.NTSB LAX99LA149Accident · Minor injuriesLimited investigationFinal reportPiper PA-31 · Pacific Ocean (Pacific Ocean)An undetermined system malfunction in the right engine, which led to an increase in fuel usage beyond the pilot's planned fuel consumption rate and eventual fuel supply exhaustion.NTSB ANC99LA045Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Chevak, AKThe pilot's inadequate in-flight planning/decision, and his failure to attain the proper touchdown point on the runway. Factors in the accident were a tail wind condition, and the presence of snow and ice on the runway surface.NTSB ANC99LA043Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R · Fairbanks, AKThe loss of engine power due to the failure of maintenance personnel to properly torque a connecting rod bolt during an engine overhaul, and the subsequent disconnection of the connecting rod bolt and connecting rod.NTSB CHI99LA114Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Waterloo, IAthe pilot's failure to maintain directional control.NTSB MIA99LA103Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Mt. Vernon, GAThe pilot's improper flare that resulted in a hard landing in an open field. A factor was the high output flow of the fuel injector servo that resulted in a loss of engine power and the forced landing.NTSB NYC99LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Richmond, VAThe pilot's inadequate preflight planning/preparation which resulted in flight into icing weather conditions. A factor related to the accident was restricted visibility through the icy windshield during landing.