NTSB investigations: Piper PA-32-300, 1983
15 cases on aircraft the registry lists as Piper PA-32-300. 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
| 1967 | 13 |
|---|---|
| 1968 | 13 |
| 1969 | 15 |
| 1970 | 24 |
| 1971 | 23 |
| 1972 | 22 |
| 1973 | 22 |
| 1974 | 29 |
| 1975 | 31 |
| 1976 | 29 |
| 1977 | 23 |
| 1978 | 34 |
| 1979 | 23 |
| 1980 | 28 |
| 1981 | 17 |
| 1982 | 20 |
| 1983 | 15 |
| 1984 | 11 |
| 1985 | 23 |
| 1986 | 10 |
| 1987 | 12 |
| 1988 | 19 |
| 1989 | 25 |
| 1990 | 8 |
| 1991 | 12 |
| 1992 | 13 |
| 1993 | 17 |
| 1994 | 11 |
| 1995 | 10 |
| 1996 | 10 |
| 1997 | 13 |
| 1998 | 11 |
| 1999 | 10 |
| 2000 | 12 |
| 2001 | 12 |
| 2002 | 11 |
| 2003 | 10 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 9 |
| 2007 | 5 |
| 2008 | 6 |
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 7 |
| 2013 | 2 |
| 2014 | 4 |
| 2015 | 5 |
| 2016 | 4 |
| 2017 | 4 |
| 2018 | 11 |
| 2019 | 4 |
| 2020 | 7 |
| 2021 | 2 |
| 2022 | 12 |
| 2023 | 8 |
| 2024 | 9 |
| 2025 | 3 |
| 2026 | 3 |
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.aircraft_model_code IN ('7103212'))
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.aircraft_model_code IN ('7103212'))
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 MIA84FA048Accident · Serious injuriesField investigationFinal reportPiper PA-32-300 · Vero Beach, FLShortly after takeoff from rwy 29L the eng began to lose power. A turn back to the arpt was made when the eng quit & the acft struck trees & bushes about 350 ft short of rwy 11L. Teardown of the eng & fuel injector system revealed that the injector for the #5…NTSB MKC84LA037Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Garnett, KSWhile enroute pilot was running the acft using the right main fuel tank. He switched to the left to balance the load and the engine quit about 10 seconds after being switched. The pilot could not restart the engine and a forced landing was made in a field.…NTSB ATL83LA344Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Blairsville, GAThe plt reported that during the run-up before takeoff, he noted that the right brake was not firm, but he elected to continue the flt. While cruising, he checked the brake & reportedly, no pressure was available. The remainder of the flt was routine until…NTSB LAX83LA401Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Bermuda Dunes, CAThe acft encountered a downdraft during short final & touched down in sandy terrain a few feet short of the rwy. The right main landing gear failed as the acft struck the end of the asphalt rwy. The plt had been advised over UNICOM of a possible wind shear…NTSB CHI83LA356Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Ligonier, INThe plt report that when he landed on a wet, grass rwy, the acft slid off the wet sod & hit a ditch while on the landing roll. No mechanical malfunctions were reported.NTSB ANC83LA097Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Quinhagak, AKAt about 50-70 ft AGL the eng quit. The acft landed about 1,500 ft off the end of the rwy. The plt stated the acft had been refueled from 50 gal drums immediately prior to the flt. The fuel in the right tip tank contained enough water to have caused eng…NTSB LAX83FA260Accident · 2 fatalField investigationFinal reportPiper PA-32 300C · Buckeye, AZThe acft collided with a utility pole about 36 ft AGL less than a mile north of a private dirt airstrip. The acft had departed scottsdale municipal arpt at about 0045. The accident occurred at about 0200 aproximately 4 miles west of Buckeye,AZ. A witness…NTSB LAX83FA185Accident · 6 fatalField investigationFinal reportPiper PA32-300 · Weaverville, CAThe acft was being flown to a uni-directional arpt with an instructor plt (CFI) in the right front seat & a student plt/prospective buyer in the left front seat. The rwy elevation was 2230 ft MSL at the south end & 2350 ft at the north end. North of the rwy,…NTSB CHI83FA156Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Miltona, MNPrior to separting, the plt was advised of low ceilings & poor visibility over the entire proposed route & was advised that VFR flt was not recommended. In a discussion with persons at fergus falls, MN, he stated that he was going to follow the highway. About…NTSB LAX83LA165Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gorman, CAEncountering clouds enroute the plt descended to fly through the teton pass. After confirming a VFR check point, he commenced a climb. Shortly thereafter the acft struck a powerline.NTSB ANC83LA055Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Pedro Bay, AKThe acft collided with trees during an attempted go-around after an aborted landing on a frozen lake. The pilot landed toward the village and found the braking action on the snow covered ice was non existent. A go-around was attempted but not enough altitude…NTSB LAX83LA094Accident · No injuriesLimited investigationFinal reportPiper PA-32 · So. Lake Tahoe, CAThe takeoff was initiated downwind on runway 36, which was 8544 ft long and was wet. The field elevation was 6264 ft. the aircraft was observed by tower personnel to rotate about 3000 ft down the runway, then climb to about 50 ft AGL. The pilot elected to…NTSB ANC83FA037Accident · Minor injuriesField investigationFinal reportPiper PA-32-300 · Kasilof, AKThe plt reported that as the acft begun to climb after takeoff, the engine lost power momentarily & the RPM dropped from 2650 to 2500. He started to abort the takeoff, and commented to the passengers, 'we're going to have to put her down.' At about the time…NTSB CHI83FA086Accident · Minor injuriesField investigationFinal reportPiper PA-32-300 · Monroe, WIWhile cruising at 4,000 ft MSL the eng quit. During a forced landing on rolling farm terrain both main landing gear separated. The acft then slid through a barbed wire fence & caught fire. Metallurgical examination revealed a fatigue failure of the idle set…NTSB LAX83FUG13Accident · 3 fatalFinal reportPiper PA-32-300 · Palm Springs, CAThe acft crashed during takeoff at the end of the runway after the engine lost power. After he was cleared for takeoff the pilot started down the runway. At the runways end according to a surviving passenger the pilot said we are in trouble. He called the…