NTSB investigations: Lycoming IO-540 series, 1997
16 cases on aircraft whose registry engine model is Lycoming IO-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 | 2 |
| 1966 | 1 |
| 1967 | 4 |
| 1968 | 1 |
| 1969 | 2 |
| 1970 | 3 |
| 1971 | 1 |
| 1972 | 3 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 1 |
| 1976 | 4 |
| 1977 | 3 |
| 1978 | 6 |
| 1979 | 7 |
| 1980 | 18 |
| 1981 | 10 |
| 1982 | 16 |
| 1983 | 17 |
| 1984 | 30 |
| 1985 | 20 |
| 1986 | 17 |
| 1987 | 15 |
| 1988 | 12 |
| 1989 | 11 |
| 1990 | 14 |
| 1991 | 14 |
| 1992 | 19 |
| 1993 | 24 |
| 1994 | 13 |
| 1995 | 14 |
| 1996 | 16 |
| 1997 | 16 |
| 1998 | 16 |
| 1999 | 28 |
| 2000 | 27 |
| 2001 | 32 |
| 2002 | 37 |
| 2003 | 30 |
| 2004 | 35 |
| 2005 | 30 |
| 2006 | 31 |
| 2007 | 34 |
| 2008 | 29 |
| 2009 | 19 |
| 2010 | 29 |
| 2011 | 22 |
| 2012 | 26 |
| 2013 | 21 |
| 2014 | 28 |
| 2015 | 19 |
| 2016 | 18 |
| 2017 | 28 |
| 2018 | 27 |
| 2019 | 16 |
| 2020 | 15 |
| 2021 | 27 |
| 2022 | 23 |
| 2023 | 24 |
| 2024 | 14 |
| 2025 | 18 |
| 2026 | 16 |
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 year(c.\"eventDate\") = 1997
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41530', '41585'))
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") = 1997
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41530', '41585'))
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 IAD98FA015Accident · 1 fatalField investigationFinal reportSocata TB-20 Trinidad · Roanoke, VALoss of engine power for undetermined reasons. A related factor was the low ceiling.NTSB MIA98FA040Accident · 3 fatalField investigationFinal reportCommander 114B · Cross City, FLVFR flight by the noninstrument-rated pilot into instrument meteorological conditions (IMC), and his failure to maintain control of the aircraft, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the terrain (tree,…NTSB NYC98LA033Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Johnstown, PAthe pilot's failure to maintain direction control of the airplane during the takeoff roll. Factors relating to this accident were: the crosswind condition, and snowbank.NTSB NYC98LA015Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Scottsville, VAimproper engine operation by undetermined person(s) that initiated gauling on the connecting rod, and led to its subsequent failure.NTSB CHI97FA293Accident · 2 fatalField investigationFinal reportKeaggy-David Skybolt · Adeline, ILThe pilot's failure to maintain aircraft control for undetermined reasons.NTSB ATL97LA123Accident · 1 fatalLimited investigationFinal reportJurka P51D Mustang · Fort Pierce, FLloss of engine power for undetermined reason(s); and failure of the pilot to maintain adequate airspeed, while starting to maneuver for an emergency landing, which resulted in loss of aircraft control (stall) and collision with terrain.NTSB LAX97LA281Accident · No injuriesLimited investigationFinal reportAerospatiale TB-20 · Borrego, CAThe pilot's inadequate compensation for the existing wind conditions and his subsequent failure to maintain runway alignment during the takeoff roll.NTSB FTW97LA284Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Pine Bluff, ARloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB FTW97LA263Accident · Serious injuriesLimited investigationFinal reportBronner Steen Skybolt · Brazoria, TXa fuel leak at a wobble pump fuel hose clamp, which resulted in loss of fuel and fuel exhaustion. A related factor was the lack of suitable terrain for a forced landing.NTSB SEA97LA140Accident · Minor injuriesLimited investigationFinal reportRepublic RC-3-1 · Monument Valley, UTthe pilot's inadequate preflight planing/preparation, and his failure to maintain sufficient altitude or clearance from the terrain. Factors relating to the accident included: high, gusty, variable winds, and terrain induced downdrafts.NTSB NYC97FA080Accident · 2 fatalField investigationFinal reportPiper PA-60-601P · Waterford, VAfailure of the pilot to follow the published instrument (IFR) approach procedure, by failing to maintain the minimum altitude for that segment of the approach.NTSB LAX97LA158Accident · 2 fatalLimited investigationFinal reportDevendorf Glassair GL25 · Congress, AZfailure of the pilot to recover from an inverted stall/spin prior to impact with the ground. The reason for the loss of control was not determined.NTSB NYC97LA072Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Vincentown, NJThe pilot's failure to maintain directional control, which resulted in an on ground loss of control. A contributing factor was a crosswind.NTSB MIA97LA123Accident · No injuriesLimited investigationFinal reportCumberland Skybolt · Smithfield, NCInstallation by a student mechanic of a counterweight retaining washer that did not meet engine manufacturers specifications resulting in partial separation of the counterweight, failure of the No.5 connecting rod adjacent to the counterweight, and seizure of…NTSB ATL97LA050Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Memphis, TNfailure of maintenance personnel to properly inspect (and repair) the brake assembly, which allowed a subsequent brake fluid leak and eventual fire.NTSB IAD97LA044Accident · No injuriesLimited investigationFinal reportAerospatiale TB-20 · University Park, PAthe pilot's inability to control the airplane due to a damaged/bent elevator control lever and resultant lack of elevator authority.