NTSB investigations: Lycoming IO-540 series, 1983
17 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\") = 1983
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") = 1983
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 ANC84LA023Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Barrow, AKThe plt stated that shortly after reaching cruise altitude the eng failed. A forced landing was made on tundra covered by encrusted snow & ice nad the gear collapsed. During the on-scene investigation the fuel injector was found to allow only a small amount…NTSB MKC84LA028Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Kearney, NEDuring the landing roll, the plt held the nosewheel off while slowing down, and used right rudder to compensate for a reported x-wind condition. As soon as the nosewheel touched down, the acft veered to the right. It went off the right side of the rwy, the…NTSB CHI84LA039Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Ypsilanti, MIThe acft was struck by a truck as it taxied on the ramp after landing. The fire department reported the truck left a 25 ft skid mark as it came out from an area of parked acft and struck N47519.NTSB ATL84LA004Accident · No injuriesLimited investigationFinal reportMaule M-6-235 · Elberta, ALThe plt took off with a passenger, who was also a plt, but was not performing as such on this flt. After returning to the arpt, the plt landed on the north-south rwy. He stated that during the landing roll, he encountered a x-wind that caused the acft to…NTSB ATL84LA003Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Sewanee, TNThe acft collided with trees during landing roll. The plt has recounted several variations of the accident from locked brakes (parking) to a flat left tire with full right rudder to maintain directional control. There was a left tire skid mark from touchdown…NTSB NYC83FA254Accident · 3 fatalField investigationFinal reportBellanca 17-31ATC · Provincetown, MAThe acft crashed in cape cod bay during a night x-country flt. Two sections of wooden wing identified as from the same make and model as the missing acft were recovered from the bay during the 3 days following the flt of the acft. Other identified parts of…NTSB MIA83FA202Accident · 5 fatalField investigationFinal reportRockwell 114A · Ebro, FLShortly after takeoff the plt advised departure control that he was going around clouds & that there was no activity on his onboard storm scope. Several minutes later radar contact was lost. The acft had broke up in flight. Although VMC prevailed at the…NTSB CHI83LA373Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Wheeling, ILThe pilot stated that he taxied southeast on runway 12L, then turned to taxi northwest on runway 34. During the turn, the left main gear went off the runway and into a hole in the sod. The width of runway 12L is 50 ft and the width of runway 34 is 100 ft. the…NTSB SEA83LA138Accident · No injuriesLimited investigationFinal reportEagle DW-1 · Bliss, IDAccording to the plt, he was returning to a road to land & reload chemicals for aerial application. He stated that the right main tire went flat during flt due to a puncture. During the landing roll-out, the acft veered to the right & nosed over.NTSB CHI83LA280Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Minneapolis, MNThe acft ran off the end of the rwy and collapsed the nose gear during an aborted takeoff. The acft exceeded the maximum gross weight for takeoff by 190 lbs. Decision to abort was made about 2/3 of the way down the rwy. Braking was good and deceleration…NTSB NYC83FA087Accident · 6 fatalField investigationFinal reportPiper PA-32RT-300 · Wellsville, NYJust prior to this flt, the plt had flown from hornell, NY to Wellsville, NY. Before departing hornell, he radioed that the vacuum annunciator light was on, & during a run-up, the suction gauge read zero. Ground personnel advised that with this problem, the…NTSB MIA83LA111Accident · No injuriesLimited investigationFinal reportPiper PA-60-601P · Tampa, FLThe aircraft departed runway 18L at Tampa intl airport. Shortly after takeoff the pilot reported to the control tower that the main cabin door was open and requested landing instructions. The pilot stated he was holding the door and trying to fly the aircraft…NTSB CHI83FA138Accident · No injuriesField investigationFinal reportPiper PA-601P · Wheeling, ILAfter making an ILS approach to rwy 16, the plt was cleared to circle and land on rwy 34. As he turned final, he was to the west side of the runway and was too high to land, so he made a left turn-around back to rwy 34. Tower personnel turned the rwy lights…NTSB ATL83LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Leonardtown, MDPilot did not maintain alignment during takeoff and collided with a pile driver. The aircraft was then landed gear up inan adjacent field. The wind was calm and there was no known reason for failure to maintain runway alignment.NTSB ANC83LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Nondalton, AKThe plt reported that during a landing on an ice & snow covered rwy, the braking was poor & he was using pumping actions while applying the brakes. Reportedly, when the acft was about half way down the rwy, the left brake lost all pressure. At about the same…NTSB ANC83LA031Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Wainwright, AKThe aircraft ran off the departure end of the runway during landing. A passenger stated that the aircraft touched down at about mid-field at a higher than normal airspeed and bounced once before sliding off the end of the runway. The gravel runway was covered…NTSB MIA83LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32-301R · Near Vero Beach, FLThe acft collided with tree tops during a night flight but the pilot was able to maintain control and land at a nearby airport. According to the pilot he was on approach to fort pierce airport when the accident occurred. However according to some witnesses…