NTSB investigations: Piper PA-23-250, 1985
20 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\") = 1985
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") = 1985
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 LAX86LA047Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Ukiah, CAWhile en route to sonoma county arpt, santa rosa, CA, the plt became concerned about the acft fuel state. The plt elected to divert to Ukiah arpt, Ukiah, CA, and while en route the acft experienced total pwr loss due to fuel starvation. During the forced…NTSB NYC86LA044Accident · Minor injuriesLimited investigationFinal reportPiper Aztec · North Adams, MAThe flight departed albany new york under VFR conditions and picked up IFR clearance to pittsfield, MA. The pilot flew the approach until reaching VFR under a cloud layer at about 2500 ft. continuing VFR toward no. Adams at an altitude of 2000 ft, the pilot…NTSB NYC86LA040Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · West Point, NYThe acft was returning to university park arpt after passengers were dropped off at waterbury oxford arpt. Aprx 20 minutes into the flt, the acft collided with two birds. The left wing tip was damaged along with a portion of a section of the left wing 3 1/2…NTSB LAX86LA046Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Tustin, CAThe plt's mechanic performed a pre-purchase inspection of the acft. No malfunctions were detected with the fuel system, & the mechanic informed the plt that the acft was overall 'in good condition.' Later in the day the plt purchased the acft, & after…NTSB ATL86FA026Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Chester, SCWitnesses at the accident site estimated the ground visibility to be 100 yds or less. The instrument rated plt on the 32 NM flt had not filed a flt plan even though he had obtained a wx briefing from fss. The acft collided with the steel cables atop steel…NTSB DEN86FA020Accident · 1 fatalField investigationFinal reportPiper PA-230-250 · Englewood, COThe plt had new avionics and autopilot system installed in the acft prior to the accident. Ntap data indicated that the acft did not attain the assigned alt of 8200 ft prior to reaching the outer marker. The acft did not get established on the localizer…NTSB NYC86FA027Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Landisburg, PAThe non-instrument rated pilot took off on a VFR crosscounty flight with no weather briefing. He flew into an area of adverse weather including low clouds, fog, drizzle & haze. The aircraft impacted near the top of a 2100 ft high hill in forested terrain.NTSB MIA86FA012Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Pensacola, FLAfter takeoff acft headed to destination arpt located 4 miles south. When aprx two miles out, the plt turned back to the departure arpt. Witnesses reported the acft was in a shallow descent, low and fast when it collided with trees and exploded about 1400 ft…NTSB LAX86LA008Accident · 2 fatalLimited investigationFinal reportPiper PA-23-250 · Santa Barbara, CAOn oct. 3, 1985, pipter PA-23-250 crashed into the pacific ocean while on an air sampling flt near Santa Barbara, CA. The ac was destroyed and the two plts were fatally injured. The flt was to be flown along a predermined route utilizing loran navaids. The ac…NTSB MIA85LA198Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Atlantic Ocean (Atlantic Ocean)The plt reported that during an overwater flt, a fire began in the front section of the acft while he was cruising at 10,500 ft. he radioed his position on the emergency freq (121.5 mhz) & squawked an emergency code (7700) on his transponder. Subsequently, he…NTSB MIA85IA182Incident · No injuriesIncident investigationFinal reportPiper Aztec PA-23-250 · Vero Beach, FLWhile in the traffic pattern, the cfi's attention was diverted as he attempted to assist ATC with some radio frequency info. While being so distracted, he permitted the student to land the acft with the gear up.NTSB MIA85LA151Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Miami, FLThe plt stated that he permitted a non-plt pax to close the cabin door & he, the plt did not check it. Shortly after liftoff the landing gear was retracted & the door popped open. The pax turned in his seat to close the door & bumped the yoke forcing the acft…NTSB NYC85LA108Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Clarion, PAThe purpose of the flight was to position the aircraft at pittsburgh, PA. During the takeoff roll at buffalo, two to three short power surges in the no. 1 engine were experienced but the pilot decided not to abort and continued to destination. The aircraft…NTSB FTW85FA137Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Foss, OKInflt fire at rear of lft eng caused by fitting of inlet fuel line to eng driven fuel pump being more than 1 & 1/2 turns from finger tight plt was A&P mech and did maint on a/c and had helped install lft eng 19.8 hrs prior to accident . Lft wing separated…NTSB MIA85FA112Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Jacksonvile, FLThe single eng land, pvt plt had an instrument rating, but had no rating to fly multi-eng acft. While on an illegal flt with marijuana on board, he contacted jacksonville apch control & advised that he could not see the ground due to dense ground fog, the…NTSB MIA85LA108Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Brunswick, GAThe plt stated that his takeoff roll was normal, but just before he rotated, the nose gear collapsed. No determination could be made as to the nature of the malfunction during a post crash exam & retraction test of the landing gear.NTSB ATL85LA103Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Reidsville, GAThe acft was found burning in the woods by the foresty service. No persons or baggage were found. The date, time & cause of the accident is unknown. Suspected drug related activity. According to FAA records, the acft was not officially registered. It had been…NTSB MKC85FA059Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Hot Springs, ARPilot had been cleared for an ILS approach to Hot Springs, Arkansas. After he crossed the initial approach fix, he said he was going to climb back above the clouds for just a second. He climbed 500 feet in the next 12 seconds, then started a fast descent. The…NTSB MIA85FA089Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Key Largo, FLThe aircraft crashed into the waters of the atlantic ocean and sank nose first into 15 feet of water. On impact the 25 bales of marijuana located in the cabin of the aircraft shifted forward and pinned the pilot and passenger in the aircraft. No usable fuel…NTSB FTW85LA099Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Addison, TXThe plt stated that on touchdown, the acft veered left & went off the edge of the 30' wide rwy. The nose gear then collapsed in soft terrain before the plt could get the acft back on the rwy surface. At 1900 CST, the wind was from 360 deg at 30 gusting 40 KTS.