Fatal NTSB investigations: Lycoming TI0-540 series, 1982
15 cases on aircraft whose registry engine model is Lycoming TI0-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 |
|---|---|
| 1966 | 3 |
| 1968 | 5 |
| 1969 | 3 |
| 1970 | 1 |
| 1971 | 4 |
| 1972 | 6 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 4 |
| 1976 | 5 |
| 1977 | 6 |
| 1978 | 14 |
| 1979 | 12 |
| 1980 | 16 |
| 1981 | 13 |
| 1982 | 15 |
| 1983 | 13 |
| 1984 | 9 |
| 1985 | 7 |
| 1986 | 9 |
| 1987 | 10 |
| 1988 | 6 |
| 1989 | 8 |
| 1990 | 2 |
| 1991 | 8 |
| 1992 | 6 |
| 1993 | 8 |
| 1994 | 8 |
| 1995 | 3 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 6 |
| 1999 | 6 |
| 2000 | 6 |
| 2001 | 14 |
| 2002 | 17 |
| 2003 | 12 |
| 2004 | 16 |
| 2005 | 12 |
| 2006 | 13 |
| 2007 | 7 |
| 2008 | 11 |
| 2009 | 10 |
| 2010 | 9 |
| 2011 | 8 |
| 2012 | 14 |
| 2013 | 7 |
| 2014 | 12 |
| 2015 | 10 |
| 2016 | 5 |
| 2017 | 4 |
| 2018 | 7 |
| 2019 | 6 |
| 2020 | 7 |
| 2021 | 6 |
| 2022 | 7 |
| 2023 | 9 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 6 |
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\") = 1982
AND c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533'))
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") = 1982
AND c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533'))
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 MIA83FA046Accident · 3 fatalField investigationFinal reportPiper PA-601P · Valparaiso, FLTwo minutes after takeoff the plt reported a loss of the left eng. He was immediately cleared for a landing at eglin afb. While maneuvering for a landing the left eng & wing separated from the acft. The eng was separated from the wing & showed evidence of in…NTSB LAX83FUJ04Accident · 1 fatalFinal reportPiper PA-32-300 · Douglas, AZThe plt was observed to crash shortly after takeoff. Witnesses stated it had been snowing off & on. The plt's blood alcohol level was 228 mg%.NTSB ATL83FA041Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Culpepper, VAAbout 16 min after takeoff the plt reported to ARTCC that he had lost the artificial horizon, gyro & vacuum pump. Radio & radar contact was lost shortly thereafter. Examination of the vacuum pump failed to reveal a pre-impact failure or malfunction. The acft…NTSB ATL83AA029Accident · 1 fatalFinal reportPiper PA-31-350 · Brevard, NCAfter a missed approach at asheville the flt was cleared to the greenville-spartanburg arpt at greer,SC. Enroute to greer radar contact was lost. In response to a query from atlanta ARTCC the plt verified his position as being on the 235 deg radial of…NTSB FTW83FPM04Accident · 2 fatalFinal reportPiper PA23-250 · 8 Miles Se Bris, OKThe acft departed at 2220 with a planned enroute stop at holdenville, OK. 55 minutes later the acft crashed approximately 8.5 miles from its original departure point. Witnesses describe the wx as very bad due to heavy rain & fog.NTSB NYC83FA004Accident · 1 fatalField investigationFinal reportTed Smith 601P · Augusta, MEPilot lost control of his aircraft during low altitude maneuvers to align the aircraft for landing. The low ceiling and rising terrain around the airport influenced the pilots decisions to make tight turns at low altitude. The aircraft was stalled and rolled…NTSB MIA83FA017Accident · 8 fatalField investigationFinal reportPiper PA-31 · Missing Acft (Atlantic Ocean)The flt departed anguilla at 0803 ast. At 0805 the plt radioed st. maarten & filed a VFR flt plan to st. thomas. The flt plan showed a direct route of flt at 4,500 ft MSL with a time enroute of 45 min. The flt failed to arrive at the destination. Search…NTSB MIA83LA012Accident · 2 fatalLimited investigationFinal reportPiper PA-32-300 · Near St. CroixThe non-instrument rated pilot departed st Croix, VI at about 2000 local time on a VFR flight to san juan, PR. The weather was VFR, but it was a dark night. The aircraft failed to arrive at its destination and a search was initiated. About 10 miles northwest…NTSB MIA83FA006Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Lake Placid, FLAircraft was transporting marijuana and during an attempted road landing at Lake Placid collided with wires which damagethe landing assembly. Aircraft continued on to north about 4 miles and ditched in a lake. The aircraft sank with both occupants and cargo.NTSB LAX82FUG17Accident · 1 fatalFinal reportPiper PA-32R-301T · San Gorgonio, CAThe acft crashed into the south face of mount San Gorgonio at approximately 8,300 ft MSL. It appeared the acft was in level flt & at a high speed at impact. Witnesses in the area reported the weather was VFR.NTSB MIA82FA120Accident · 1 fatalField investigationFinal reportPiper P-60-601P · Titusville, FLShortly after takeoff witnesses observed the acft in a steep left bank descending until it crashed approximately 1200 ftnw of the departure end of the rwy. According to the pax the initial climb distracting the attention of the plt who lostcontrol of the acft…NTSB ATL82FA047Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Lambsburg, VAThe aircraft was on an air taxi flight to transport 2 prisoners and was to be operated on a VFR flight plan in VFR conditions only. Prior to takeoff, the pilot had obtained 12 weather briefing. In 2 of the briefings, VFR flight was not recommended. At about…NTSB NYC82FA029Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Newburgh, NYAt 2234 the plt was issued a vector to the initial approach fix for the ILS rwy 9 apch. He was also issued the followingwx "...stewart weather thirty minutes ago is estimated one thousand overcast six miles in light rain and haze." At 2238 the plt was advised…NTSB ATL82FKQ10Accident · 1 fatalFinal reportPiper PA-23-250 · Mccomb, MSBefore taking off from jackson, MS, the pilot received a weather briefing by radio and filed an IFR flight plan to Mccomb, MS. During arrival at Mccomb, the weather was IFR with an indefinitely obscured ceiling at zero ft, visibility 1/2 mile in fog, wind 160…NTSB FTW82FRG21Accident · 1 fatalFinal reportPiper PA-31 · Port Mansfield, TXThe aircraft crashed and burned about 1/2 mile from the approach end of runway 12. A witness reported that "the plane just fell" while the pilot was making a sharp turn. An estimated 1500 lbs of marijuana was on board.