NTSB investigations: Lycoming IO-540 series, 1994
13 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\") = 1994
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") = 1994
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 MIA95FA037Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Sylvan Springs, ALPoor in-flight planning/decision by the pilot-in-command for failure to deviate to an alternate airport after encountering icing conditions in an airplane not certificated for flight in icing conditions. Also, failure of the pilot to maintain altitude…NTSB NYC95FA042Accident · 1 fatalField investigationFinal reportPiper PA-60-600 · Colonie, NYFailure of the pilot to maintain control of the aircraft, possibly from falling asleep.NTSB FTW94LA305Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Nacogdoches, TXThe pilot's inadequate compensation for crosswind during landing rollout. A factor was the variable crosswind.NTSB FTW94LA283Accident · 2 fatalLimited investigationFinal reportWalton Skybolt · Collinsville, OKThe pilot's failure to maintain airspeed resulting in an inadvertent stall.NTSB CHI94LA255Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Marshalltown, IAA partial loss of engine power for undetermined reasons.NTSB CHI94LA218Accident · No injuriesLimited investigationFinal reportCallair A9B · Minot, NDthe pilot's failure to maintain clearance from the wheat field. A factor was the turbulence.NTSB ATL94LA126Accident · Serious injuriesLimited investigationFinal reportGreen Starduster TOO · Chattanooga, TNThe pilot's failure to maintain aircraft control, resulting in an inadvertent stall, and collision with terrain.NTSB LAX94LA253Accident · No injuriesLimited investigationFinal reportSchumacher Swearingen SX-300 · Kingman, AZthe pilot's inadvertent raising the flaps during a go-around attempt. A factor in the accident was the gusty crosswind condition.NTSB ANC94LA068Accident · No injuriesLimited investigationFinal reportMaule M6-235 · Bethel, AKThe pilot's failure to maintain directional control during landing.NTSB LAX94LA225Accident · Serious injuriesLimited investigationFinal reportStaudacher 300S · Chandler, AZThe operation of the engine at an RPM setting that exceeded the original design specifications and resulted in the failure of the no. 5 connecting rod bearing.NTSB ATL94FA075Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Smithville, TNThe pilot's failure to obtain recent weather information to avoid flight into icing conditions. Factors in the accident were: management-induced pressure and the icing conditions.NTSB BFO94LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Norfolk, VAFatigue failure of the engine mounting bolt which resulted in loss of engine power and subsequent on ground collision with the terrain.NTSB MIA94FA067Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Sugarloaf Key, FLWas the failure of the pilot-in-command to perform a visual lookout and maintain his altitude. Contributing to the accident was the dark night, over water, visual descent.