NTSB investigations: Lycoming IO-540 series, 1990
14 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
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\") = 1990
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") = 1990
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 ANC91LA015Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Kongikank, AKThe pilot in command's failure to maintain airspeed during approach resulting in an inadverrtent stall annd uncontrolled descent into the ground.NTSB CHI91FA031Accident · 4 fatalField investigationFinal reportPiper PA-32-RT300 · Gaylord, MIThe pilot's failure to maintain adequate terrain clearance. Factors which contributed to the accident were: the dark night, adverse weather conditions, and the pilot's overconfidence in continuing VFR flight into these conditions.NTSB BFO91LA015Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Milton, KYThe in-flight failure of both engines due to the pilot's mismanagement of the fuel system.NTSB NYC90FA215Accident · 4 fatalField investigationFinal reportPiper PA-32RT-300 · Montgomery, NYAn inadequate preflight by the pilot which resulted in a power loss due to fuel exhaustion.NTSB CHI90DCQ01Accident · Minor injuriesFinal reportPiper PA 36-300 · Mingo, KSInadequate airspeed resulting in a stall/mush being encountered by the PIC. Contributing factors were a tailwind and a load jettison not performed.NTSB MIA90LA173Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Hattiesburg, MSFailure of the pilot in command to attain adequate airspeed prior to liftoff during an attempted takeoff. The pilot then lost control of the airplane in flight. The pilot also delayed in his decision to abort the takeoff.NTSB SEA90LA147Accident · Minor injuriesLimited investigationFinal reportLake LA-250 · Rawlins, WYPilot's improper planning/decision, and his misjudgement of the aircraft's climb capability in conditions of high density altitude and unanticipated atmospheric conditions. The high density altitude and rising terrain were related factors.NTSB CHI90LA195Accident · No injuriesLimited investigationFinal reportMaule M-5-235C · East Tawas, MIThe private pilot's failure to maintain adequate control of the aircraft after touchdown.NTSB LAX90DVG12Accident · Serious injuriesFinal reportE.J. Novotny Steen Skybolt · Fall River Mill, CALoss of power for undetermined reasons.NTSB SEA90LA120Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Island Park, IDPilot's failure to maintain directional control, while attempting a soft-field takeoff. The crosswind was a related factor.NTSB LAX90DUA01Accident · Minor injuriesFinal reportHomebuilt JP-350-1 · Torrance, CAThe aircraft collision with the ground after the pilot experienced a loss of engine thrust due to propeller overspeed condition. Contributing to the accident was the pilot's improper servicing of the propeller hub that allowed the overspeed to occur.NTSB MKC90LA112Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Little Rock, ARThe failure of the powerplant due to a sheared timing gear. Contributing factors were unsuitable terrain and restricted vision due to fog.NTSB FTW90DQG02Accident · No injuriesFinal reportBellanca BL-DW-1 · Petersberg, TXLoss of directional control as the result of an encounter with a dust devil.NTSB LAX90LA108Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-300 · Sacramento, CAAn inadvertent collision with a large bird during the hours of darkness while in the landing pattern.