NTSB investigations: Lycoming IO-540 series, 2005
30 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\") = 2005
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") = 2005
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 ATL06LA027Accident · No injuriesLimited investigationFinal reportPiper PA32-300 · Maiden, NCThe total loss of engine power due to the failure of the No. 5 main bearing due to overheating for undetermined reasons.NTSB MIA06WA035Accident · 4 fatalForeign investigationPiper PA-23-250 · South Caicos, Turks & Caicos IslandsNTSB DEN06CA027Accident · No injuriesData collectionFinal reportMaule M-7-235 · Moriarty, NMthe pilot's failure to maintain directional control during the landing. Contributing factors included the pilot's inadequate in-flight decision making and the high velocity, gusty winds.NTSB LAX06FA054Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Kingsburg, CAThe pilot's in-flight decision to continue VFR flight into instrument meteorological conditions during descent, which resulted in an in-flight collision with trees and terrain. Fog, low ceiling, and obscuration were factors.NTSB DFW06CA033Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Bixby, OKThe loss of engine power due to water contamination and corrosion in both gascolators due to improper maintenance. A factor was the lack of suitable terrain for the forced landing.NTSB NYC06FA034Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Burlington, VTThe pilot's failure to follow the published instrument flight procedure, which resulted in an in-flight collision with terrain. Factors in the accident were the local air traffic controller's inadequate monitoring of the MSAW system, and his delayed…NTSB LAX06CA039Accident · No injuriesData collectionFinal reportCessna 182T · Livermore, CAsubstantial damage to the airplane during unknown phase of flight for undetermined reasons.NTSB DFW05CA250Accident · No injuriesData collectionFinal reportRobinson R44 · Batesville, TXThe pilot's failure to maintain rotor rpm and his subsequent encounter with settling with power.NTSB CHI05CA270Accident · No injuriesData collectionFinal reportCessna 182S · Waukesha, WIThe misjudged flare by the pilot.NTSB IAD05CA143Accident · No injuriesData collectionFinal reportMaule MT7-235 · Capon Bridge, WVThe pilot's misjudged distance/speed which resulted in an overrun and a subsequent impact with trees.NTSB DEN05CA138Accident · No injuriesData collectionFinal reportRobinson R44 II · Jackson, WYthe pilot's failure to maintain aircraft control during initial takeoff climb resulting in an uncontrolled descent and impact with terrain. A contributing factor was the pilot's encounter in settling with power.NTSB ATL05LA154Accident · 2 fatalLimited investigationFinal reportSamson Seawind 3000 · Wrightsville Bh, NCThe pilot's improper preflight decision to attempt night VFR flight into IMC, which resulted in an inflight encounter with weather and the pilot's subsequent loss of control of the airplane due to spatial disorientation.NTSB IAD05FA125Accident · 2 fatalField investigationFinal reportPiper PA-32R-301 · West Chester, PAThe pilot's improper decision to abort the landing after the airplane contacted the runway. A factor in the accident was the pilot's failure to ensure the landing gear was extended during the landing.NTSB IAD05LA123Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Smoketown, PAA loss of engine power during the climb for undetermined reasons, resulting in a forced landing.NTSB DFW05LA193Accident · 1 fatalLimited investigationFinal reportZivko Aeronautics Edge 540-T · Denison, TXThe pilot's failure to maintain control of the airplane while performing aerobatics. A contributing factor was the low altitude.NTSB ANC05CA102Accident · No injuriesData collectionFinal reportPiper PA-32-301 · Karluk, AKA collision with a deer on the runway during the landing roll, which resulted in substantial damage to the tail of the airplane.NTSB ATL05LA126Accident · 1 fatalLimited investigationFinal reportEllsworth Sky Bolt · Cumming, GAThe pilot's improper fuel management while maneuvering resulting in a total loss of engine power due to fuel starvation.NTSB ATL05LA103Accident · 1 fatalLimited investigationFinal reportRutherford Seawind 3000 · Sarasota, FLMaintenance personnel failure to secure throttle linkage on the carburetor which resulted in loss of engine power and a collision with a building.NTSB MIA05CA099Accident · No injuriesData collectionFinal reportPiper PA32-301 · Brooksville, FLThe pilot-in-command failure to maintain directional control during takeoff after landing, which resulted in the airplane exiting the runway.NTSB DFW05CA072Accident · No injuriesData collectionFinal reportRobinson R44 II · Woodward, OKthe pilot's encounter with adverse weather conditions.NTSB LAX05CA147Accident · No injuriesData collectionFinal reportMaule MA-7-235C · Borrego Springs, CAthe pilot's failure to maintain directional control.NTSB DEN05FA066Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Broomfield, COthe pilot's failure to maintain aircraft control during landing. Contributing factor's included the quartering tailwind, and the pilot's inadequate in-flight decision making.NTSB MIA05FA085Accident · 2 fatalField investigationFinal reportCommander 114-B · Venice, FLThe pilot's in-flight loss of control during takeoff/initial climb over the water at night due to spatial disorientation. A related factor was the night conditions.NTSB NYC05FA053Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Coatesville, PAThe pilot's inadequate remedial action during an engine failure, which resulted in a loss of airplane control. A factor was the pilot's improper fuel management, which resulted in fuel starvation to one engine, and its subsequent loss of engine power.NTSB ANC05FA039Accident · Serious injuriesField investigationFinal reportPiper PA-32-300 · Dunnellon, FLThe improper installation of the bolt that connects the throttle linkage to the fuel control arm by an unknown maintenance person, which resulted in a loss of the bolt, a loss of engine rpm control, and subsequent forced landing and collision with trees.NTSB ANC05FA038Accident · Serious injuriesField investigationFinal reportAero Commander 500-S · San Juan, PRThe fuel truck operator's improper refueling of a gasoline engine powered airplane with jet (turbine) fuel, and the pilot's inadequate preflight, which resulted in a loss of power in both engines and subsequent collision with trees. Factors associated with…NTSB ATL05LA049Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Concord, NCThe loss of engine power due to the failure of the fuel pump which resulted in fuel starvation.NTSB SEA05LA042Accident · No injuriesLimited investigationFinal reportMaule M-7-260 · Port Angeles, WAThe pilot's improper flare. Factors contributing to the accident included the pilot's improper approach and the glassy water condition.NTSB MIA05CA053Accident · No injuriesData collectionFinal reportLee Harold Swarthout Velocity Xlrg · Daytona Beach, FLThe failure of the pilot-in-command to maintain directional control of the airplane during the landing roll resulting in the on-ground collision with a fence and a ditch.NTSB ATL05LA039Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Polkton, NCA loss of engine power due to the failure of the engine-driven fuel pump, which resulted in fuel starvation.