NTSB investigations: Lycoming IO-540 series, 2024
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\") = 2024
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") = 2024
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 CEN25LA059Accident · No injuriesClass 3 · LimitedFinal reportCessna 182T · Pearland, TXThe AA-5 pilot’s failure to maintain separation from the 182T during approach and landing, which resulted in a ground collision during the landing roll. Contributing to the accident was the failure of the AA-5’s electrical system, which prevented the AA-5…NTSB CEN25FA019Accident · 4 fatalClass 2 · FieldFinal reportRobinson R44 · Houston, TXThe pilot’s failure to maintain clearance from a lighted radio tower during a visual night flight. Contributing to the accident was the air traffic controller’s failure to issue a safety alert notifying the pilot of the flight’s unsafe proximity to the tower.NTSB CEN25LA018Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-32R-301 · Van, TXThe mechanic’s improper maintenance of the engine’s air induction scat duct, which collapsed during the flight and resulted in a loss of engine power.NTSB CEN24LA378Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32 · Caro, MIA total loss of engine power due to maintenance personnel’s failure to properly tighten the fuel supply line B-nut at the fuel servo.NTSB CEN24LA376Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Pierz, MNThe pilot’s inadequate fuel management which resulted in the loss of engine power due to fuel starvation.NTSB GAA24WA285Accident · 2 fatalClass 4 · ForeignPiper PA-23-250 · Nassau, BahamasNTSB ANC24LA055Accident · No injuriesClass 4 · LimitedFinal reportGippsland GA-8 · Tuntutuliak, AKThe pilot's failure to maintain directional control during takeoff after an encounter with a gusting wind, which resulted in a wing strike.NTSB WPR24LA166Accident · No injuriesClass 4 · LimitedFinal reportThomas J Spencer RV-10 · Snohomish, WAThe pilot’s failure to attain a proper touchdown point during landing with a tailwind which resulted in a runway overrun.NTSB ERA24LA240Accident · Serious injuriesClass 4 · LimitedFinal reportAero Commander Callair A-9B · Zebulon, NCA total loss of engine power while maneuvering due to fuel starvation.NTSB WPR24LA146Accident · Minor injuriesClass 3 · LimitedFinal reportRobert Sterling 4P · Lake Havasu City, AZA loss of engine power during initial climb due to fuel vapor lock. Contributing to the accident was the incorrect installation of the ancillary fuel supply system components.NTSB ERA24FA176Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-32R-301 · Knoxville, TNThe pilot’s decision to depart into an area of instrument meteorological and icing conditions, which resulted in loss of airplane control and a subsequent in-flight breakup.NTSB CEN24LA155Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-32-301 · Sullivan, MOA bearing failure that resulted in fatigue failure of the crankshaft and a subsequent total loss of engine power.NTSB WPR24LA111Accident · Minor injuriesClass 4 · LimitedFinal reportPiper Aerostar 601P · Grass Valley, CAThe pilot’s failure to maintain directional control in a gusting wind condition.NTSB ANC24LA013Accident · No injuriesClass 3 · LimitedFinal reportRobinson Helicopter R44 II · Glacier View, AKA sudden stoppage of the tail rotor for unknown reasons, which resulted in the tortional overload failure of the tail rotor driveshaft.