NTSB investigations: Lycoming TI0-540 series, 1982
47 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 | 9 |
|---|---|
| 1965 | 27 |
| 1966 | 32 |
| 1967 | 49 |
| 1968 | 48 |
| 1969 | 47 |
| 1970 | 48 |
| 1971 | 63 |
| 1972 | 45 |
| 1973 | 51 |
| 1974 | 62 |
| 1975 | 46 |
| 1976 | 52 |
| 1977 | 58 |
| 1978 | 68 |
| 1979 | 65 |
| 1980 | 57 |
| 1981 | 55 |
| 1982 | 47 |
| 1983 | 40 |
| 1984 | 46 |
| 1985 | 43 |
| 1986 | 43 |
| 1987 | 35 |
| 1988 | 33 |
| 1989 | 32 |
| 1990 | 16 |
| 1991 | 30 |
| 1992 | 30 |
| 1993 | 25 |
| 1994 | 26 |
| 1995 | 27 |
| 1996 | 31 |
| 1997 | 23 |
| 1998 | 22 |
| 1999 | 26 |
| 2000 | 36 |
| 2001 | 43 |
| 2002 | 46 |
| 2003 | 37 |
| 2004 | 41 |
| 2005 | 44 |
| 2006 | 49 |
| 2007 | 32 |
| 2008 | 33 |
| 2009 | 28 |
| 2010 | 34 |
| 2011 | 23 |
| 2012 | 31 |
| 2013 | 27 |
| 2014 | 25 |
| 2015 | 31 |
| 2016 | 21 |
| 2017 | 21 |
| 2018 | 22 |
| 2019 | 20 |
| 2020 | 29 |
| 2021 | 18 |
| 2022 | 28 |
| 2023 | 31 |
| 2024 | 15 |
| 2025 | 18 |
| 2026 | 19 |
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\") = 1982
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."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 NYC83LA043Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Fall River, MAOn short final & aligned with the rwy lights the plt cancelled his IFR flt plan with approach control. The acft landed on the rwy which had the middle third of its width covered with 6-8 inches of snow. The outer thirds were plowed but icy.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 ATL83IA053Incident · No injuriesIncident investigationFinal reportPiper PA-23-250 · Washington, DCThe pilot reported that he had 3 green lights after extending the landing gear. During landing roll, the left main ldg gr collapsed for an undetermined reason. The landing gear handle was found in the down position.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 FTW83LA034Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · El Paso, TXWhile on a business cross country flight the fuel pressure began dropping with a subsequent drop in power. The pilot attempted to reduce manifold pressure to keep the engine running. Approximately 3-5 miles from El Paso airport the pilot landed on the desert.…NTSB FTW83LA032Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Houston, TXThe aircraft struck a tree when the pilot was landing on a road. After tree impact, the aircraft spun around and crashed on the road sliding into a culvert and a telephone pole. The aircraft had been stolen and two occupants were observed to exit the aircraft…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 ANC83LA004Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Anchorage, AKShortly after departure the flt received radar vectors placing it near a VFR reporting point located 4 mi past the departure end of rwy 32 & 2 mi east of the rwy centerline. Traffic advisories were issued by approach control indicating a beoing 747 climbing…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 ATL83FA003Accident · Minor injuriesField investigationFinal reportPiper PA-31-310 · Dyersburg, TNAt 30 mi north of the destination, the inboard side of the right eng cowl popped loose & began vibrating severely, the plt was concerned that the cowling would break loose & strike the vert of horiz stabilizer so he feathered the r eng. Atthis point, the arpt…NTSB ATL82DA286Accident · No injuriesFinal reportPiper PA-32RT-300T · Athens, GAThe pilot initiated an intersection takeoff with 1400 ft of runway remaining. After starting the takeoff, he elected to abort; however, the aircraft continued off the end of the runway and collided with obstacles. The performance charts showed that a 3000 lb…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 ATL82DA284Accident · No injuriesFinal reportPiper PA-31 · London, KYThe aircraft was on a flight from palm beach, FL to London, KY. Five miles short of runway 23 at London, both engines quit and the aircraft made a forced landing. Post crash examination revealed less than one gallon of fuel on board.NTSB ANC82DA080Accident · No injuriesFinal reportPiper PA-32 · Near Dillingham, AKThe pilot began taking off down slope in calm wind conditions with six passengers on board. Reportedly, the 1380 ft runway was mostly dry, but was muddy in places, except the last 100 ft contained standing water. The aircraft had barely lifted off prior to…NTSB LAX82DA296Accident · No injuriesFinal reportAero Commander 500S · Sacramento, CAPax/plt in right seat inadvertently raised gear instead of flaps.NTSB DEN82DA146Accident · Minor injuriesFinal reportPiper PA-23C-250 · Gunnison, CODuring takeoff, the pilot was distracted by inbound traffic and delayed retracting his gear. At the same time, the engines were not synchronized and he was having difficulty getting them to sound good. He then noticed that a fire had started in the vicinity…NTSB ATL82DA193Accident · Minor injuriesFinal reportPiper PA-32-300 · Westminster, MDWhile on a cross-country flight, the pilot elected to make an unscheduled stop at a unfamiliar airport to check the en route weather. He circled the airport and thought the wind indicated favored runway 31, but later, he found that the wind was calm. No…NTSB NYC82DA145Accident · No injuriesFinal reportPiper PA-23-250 · Ludlow, VTThe pilot stated that during the landing, he encountered wind shear and the aircraft touched down about two feet short of the runway. He reported a 30 degree slope at the lip of the runway. All of the landing gear failed. The aircraft slid off the runway and…NTSB NYC82FA134Accident · No injuriesField investigationFinal reportPiper PA-31 · Bennington, VTWhile on approach to land, the pilot noticed the aircraft's gear warning lights were out and the circuit breakers were tripped. The pilot advised operations and started a fly-by when he noticed a fire in the left engine. The pilot feathered the left engine…NTSB DEN82DA110Accident · No injuriesFinal reportPiper PA-32RT-300T · Durango, COThe pilot reported that after taking off, dense white smoke began to fill the cockpit and seemed to come from under the instrument panel. He stated that the instruments were in the normal operating range, but the smoke became so dense that the visibility in…NTSB MKC82DA108Accident · No injuriesFinal reportCallair A-9B · Ulysses, KSThe pilot was on a spray flight over an area of sand hills. While dropping flags to help determine the wind on the surface, he encountered unfavorable wind conditions and a sudden loss of lift. He applied full power, but was unable to recover from the mushing…NTSB ANC82DA049Accident · No injuriesFinal reportPiper PA-32-300 · Near Ekwok, AKThe pilot made a forced landing when power would not develop more than 1500 rmp. Takeoff and climb had been normal up to 1000 feet when the engine began to lose power. Since not enough power was available to continue flight a landing was made in the tundra.…NTSB DEN82FTK04Accident · No injuriesFinal reportCallair A-9B · Sioux Falls, SDThe eng quit & the plt landed in an adjacent field after first hitting a wooded fence. An inspectin of the bendix fuel servo unit, model PSA-10ED-1, revealed that the fuel diaphragm stem, pn 2539806, had failed.NTSB ATL82FID10Accident · No injuriesFinal reportPiper 24-260 · Lexington, VAThe aircraft overran a 1500 wet, sod, downhill runway and collided with a ditch off the end of the runway. The collision collapsed the landing gear, bent the prop, and buckled the fuselage. The pilot reported the wind was 180 degrees at 5 to 10 knots.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 CHI82FA157Accident · Minor injuriesField investigationFinal reportPiper PA-32-300 · Milwaukee, WIEngine failure forced pilot to land in an open plowed field. Aircraft collided with wires but a successful landing was made. Oil pump gear tooth had failed.NTSB ANC82DA032Accident · No injuriesFinal reportPiper PA-32 · Akiachak, AKThe pilot began taking off on a soft runway with a left quartering crosswind. He stated that he was unable to get enough speed on the soft mud for a safe takeoff. He cut the power to abort, but was unable to stop on the remaining runway. The plane continued…NTSB MIA82DA103Accident · No injuriesFinal reportPiper PA-31-350 · Miami, FLThe pilot was taxiing to gate H-2 to pick up a charter passenger when the aircraft and a vehicle collided. The pilot reported that about five seconds before impact, he saw the vehicle approaching from his ten o'clock position. He applied the brakes, but the…NTSB MIA82DA091Accident · No injuriesFinal reportPiper PA-32R · Moca, PRThe pilot landed on an unlighted grass strip at night with a load of marijuana. During the landing, the plane continued off the strip and into a sugar cane field.NTSB ATL82DA094Accident · No injuriesFinal reportPiper PA-32-301T · Lexington Park, MDThe pilot stated that while decelerating through approximately 50 knots on landing rollout he lowered the nose. The nose gear collapsed after encountering a soft spot on the runway.NTSB CHI82DA081Accident · No injuriesFinal reportPiper PA-23 250 · Grand Marais, MNAfter clearing trees located approximately 1000 feet from the end of the runway the pilot reduced power and added flaps in an attempt to land close to the approach end. The aircraft struck a snowbank on short final for the snow covered runway 27.NTSB CHI82DA077Accident · No injuriesFinal reportSmith Aerostar 600 · Elyria, OHDuring takeoff on an icy runway, the pilot lost directional control after rolling a few hundred feet. He reported that the plane was sliding left and was below VMC, so he retarded the throttles. The plane struck a snowbank beside the runway and was…NTSB DEN82FA034Accident · No injuriesField investigationFinal reportPiper PA-23 · Mitchell, SDAs the pilot approached sioux falls he received information that it was below minimums, so he started to divert. As he passed over sioux falls he could see Mitchell, SD, which appeared to be clear, therefore, he elected to land there. It continued to look…NTSB CHI82DA050Accident · No injuriesFinal reportPiper PA-31-310 · East Saint Loui, ILThe aircrew did not key the approach lights on during the first ILS approach at night. Therefore, a missed approach was made. On the second approach, the lead-in lights were visible from over one mile. However, the visibility was much worse at touchdown,…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 DEN82DA028Accident · Serious injuriesFinal reportPiper PA-32 · Rock Springs, WYThe aircraft departed vernal,ut at 1810 MST after refueling. During the VFR flight the pilot reported to Rock Springs fss that he was 20 miles south and was given current weather and runway in use. No other transmissions were received. The aircraft struck a…NTSB ATL82FKJ11Accident · Serious injuriesFinal reportPiper PA-32 · Muscle Shoals, ALDuring the approach the pilot stated that he could not extend the landing gear. At some point during the approach the aircraft broke out into VFR conditions. The pilot stated he had the airport in sight when the aircraft struck a 160,000 volt power line.…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.NTSB SEA82DA017Accident · No injuriesFinal reportPiper PA-31-350 · Spokane, WAAfter arriving in the Spokane area, a full ILS was commenced. It was terminated about 200 ft above the decision height with a missed approach. The aircraft was vectored for a second ILS. During the last 400 ft of this approach, about 3/4 to one inch of mixed…NTSB CHI82FA025Accident · No injuriesField investigationFinal reportPiper 23-250 · Wheeling, ILShortly after takeoff the pilot noticed a loss of oil pressure on both engines and initiated a left turn back to the airport. During landing the aircraft departed the right side of runway 12, collided with, and substantially damaged two Cessna 150'S and…