NTSB investigations: Piper PA-23-250, 1982
22 cases on aircraft the registry lists as Piper PA-23-250. 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 | 28 |
|---|---|
| 1965 | 40 |
| 1966 | 33 |
| 1967 | 41 |
| 1968 | 25 |
| 1969 | 34 |
| 1970 | 33 |
| 1971 | 27 |
| 1972 | 30 |
| 1973 | 32 |
| 1974 | 32 |
| 1975 | 20 |
| 1976 | 27 |
| 1977 | 24 |
| 1978 | 22 |
| 1979 | 29 |
| 1980 | 26 |
| 1981 | 13 |
| 1982 | 22 |
| 1983 | 17 |
| 1984 | 13 |
| 1985 | 20 |
| 1986 | 15 |
| 1987 | 15 |
| 1988 | 18 |
| 1989 | 8 |
| 1990 | 8 |
| 1991 | 15 |
| 1992 | 9 |
| 1993 | 12 |
| 1994 | 15 |
| 1995 | 17 |
| 1996 | 12 |
| 1997 | 8 |
| 1998 | 8 |
| 1999 | 6 |
| 2000 | 3 |
| 2001 | 3 |
| 2002 | 5 |
| 2003 | 7 |
| 2004 | 8 |
| 2005 | 12 |
| 2006 | 12 |
| 2007 | 3 |
| 2008 | 1 |
| 2009 | 1 |
| 2010 | 1 |
| 2011 | 2 |
| 2012 | 2 |
| 2013 | 6 |
| 2014 | 2 |
| 2015 | 1 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 3 |
| 2019 | 6 |
| 2020 | 5 |
| 2021 | 1 |
| 2022 | 2 |
| 2023 | 5 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 1 |
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.aircraft_model_code IN ('7102308'))
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.aircraft_model_code IN ('7102308'))
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 ATL83FA067Accident · Minor injuriesField investigationFinal reportPiper PA-23-250 · Johns Isle, SCThe plt stated both engs lost power after takeoff & the acft ditched in the stono river. No preimpact failure and/or malfunction of either eng could be found. The plt did not hold any airman certificate.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 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 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 LAX83LA016Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Sun City, CAThe pilot made a wheels up landing on hawn avenue in Sun City, CA and abandoned the aircraft. During the landing, both wing tips struck sign posts and were damaged. No fuel was found in the aircraft after it had crashed, but about 650 lbs of illegal drugs…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 LAX82FVW04Accident · Serious injuriesFinal reportPiper PA-23-250 · Panaca, NVThe plt encountered thunderstorm activity at 1900. The left fuel gauge was inop & he had no communication equipment. There was only one nav receiver operative, no instrument lights or slaved dg available. As it became darker he was unable to see the…NTSB CHI82DA346Accident · No injuriesFinal reportPiper PA-23-250 · Holland, MIPilot taxiing to takeoff collided with fuel pumps.NTSB FTW82FRG39Accident · 1 fatalFinal reportPiper PA-23-250 · Bandera, TXWhile returning from Mexico, the pilot landed at eagle pass, TX and cleared U.S. Customs. Without refueling or obtaining a weather briefing, he continued toward his home airfield at the flying l ranch near Bandera, TX. Local weather observations indicated…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 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 DEN82DA080Accident · No injuriesFinal reportPiper PA-23 · Erie, COThe aircraft lost power during takeoff climb and was landed straight ahead resulting in substantial damage. The fuel selector valve was hard to move and during tests moving it caused the engines to quit. Piper AD 80-18-10 warns that scott manufactured…NTSB FTW82DA151Accident · No injuriesFinal reportPiper PA-23-250T · Lake Dallas, TXThe pilot stated the landing gear indicated down and locked and the touchdown was normal. During the landing roll the gear retracted. During the slide down the runway the left engine caught on fire causing substantial damage to the aircraft. Examination by a…NTSB MIA82DA094Accident · No injuriesFinal reportPiper PA-23-250 · Jacksonville, FLImmediately after raising the gear handle during takeoff, the pilot heard a loud noise that he thought was an explosion. He aborted the takeoff and landed on the remaining runway without extending the gear. The loud noise occurred when the cabin door popped…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 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 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 LAX82FUJ25Accident · Serious injuriesFinal reportPiper PA-23-250 · Bagdad, AZThe pilot attempted to fly from phoenix to Bagdad, AZ under a low overcast. When it became obvious that weather conditions were too poor for a landing the pilot attempted to reverse direction and the aircraft struck high terrain.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 MIA82DA032Accident · Serious injuriesFinal reportPiper PA-23-250 · Okeechobee, FLThe aircraft owner and a friend were taken to a hospital emergency room with serious injuries at about 2115 local time. They stated that they had been attacked and robbed while hitch-hiking. On the next morning, the owner's aircraft was found where it had…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…