NTSB investigations: Piper PA-32R-300, 1994
10 cases on aircraft the registry lists as Piper PA-32R-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
| 1965 | 1 |
|---|---|
| 1975 | 1 |
| 1976 | 9 |
| 1977 | 15 |
| 1978 | 22 |
| 1979 | 13 |
| 1980 | 12 |
| 1981 | 12 |
| 1982 | 7 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 4 |
| 1986 | 5 |
| 1987 | 7 |
| 1988 | 6 |
| 1989 | 10 |
| 1990 | 6 |
| 1991 | 7 |
| 1992 | 4 |
| 1993 | 8 |
| 1994 | 10 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 7 |
| 1998 | 2 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 4 |
| 2005 | 1 |
| 2006 | 6 |
| 2007 | 1 |
| 2008 | 5 |
| 2009 | 6 |
| 2010 | 7 |
| 2011 | 3 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 2 |
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\") = 1994
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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") = 1994
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213'))
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 SEA95FA031Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Grantsville, UTThe VFR pilot's attempt to continue the flight into instrument meteorological conditions, and his failure to maintain altitude/clearance with mountainous terrain.NTSB ATL94FA171Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · Glenville, NCThe fatigue failure of #4 intake valve. A factor was hilly terrain.NTSB BFO94FA140Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Roanoke, VAThe disconnection of the throttle cable from the throttle arm on the fuel injector servo.NTSB NYC94LA105Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Put-In-Bay, OHThe pilot's inadequate control and failure to maintain directional control which resulted in collision with a sign.NTSB BFO94LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Seven Springs, PAThe pilot's failure to attain adequate airspeed and his premature liftoff which resulted in a stall mush and collision with trees.NTSB BFO94LA070Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Bedford, PAThe pilot's failure to maintain the proper descent rate which resulted in an undershoot of the runway.NTSB BFO94FA066Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · Salem, OHVFR flight by the pilot into instrument meteorological conditions (IMC), his loss of aircraft control due to spatial disorientation, and exceeding the design stress limits of the aircraft. Factors related to the accident were: darkness, the adverse weather…NTSB BFO94LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Berlin, NJThe pilot not maintaining clearance from obstacles (trees) during final approach which resulted in a collision with a tree and a subsequent uncontrolled descent until colliding with the ground.NTSB MIA94FA069Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Vicksburg, MSFailure of the pilot-in-command to maintain the proper glidepath while on a straight in approach resulting in the inflight collision with trees short of the runway. Contributing to the accident was the dark night condition.NTSB BFO94LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Norfolk, VAFatigue failure of the engine mounting bolt which resulted in loss of engine power and subsequent on ground collision with the terrain.