NTSB investigations: Piper PA-32R-300, WI
9 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
| 1976 | 1 |
|---|---|
| 1978 | 1 |
| 1979 | 1 |
| 1985 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1996 | 2 |
| 2007 | 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 c.\"eventStateOrRegion\" = 'WI' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'WI' AND c."eventCountry" = 'USA'
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 CHI08FA054Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Warrens, WIThe decision by the pilot to fly into known adverse weather, and the pilot's failure to maintain control of the airplane due to spatial disorientation. Contributing factors include the clouds and the night conditions.NTSB CHI96LA118Accident · No injuriesLimited investigationFinal reportCessna 310R · Marshfield, WIthe failure of the pilot of the PA-32R, N1030Q, to obtain identification of the Cessna 310R, N1835E, visually, and his inadequate visual outlook. A factor was the failure of both pilots to hear communications from each other.NTSB CHI96FA113Accident · 1 fatalField investigationFinal reportPiper PA-32 · Milwaukee, WIInadequate maintenance and inspection in that the Airworthiness Directive which applied to the fuel pump had not been complied with. A factor was the pilot was unable to reach land.NTSB CHI94FA048Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Antigo, WIthe failure of the pilot in command to maintain proper altitude.NTSB CHI90FA236Accident · 7 fatalField investigationFinal reportPiper PA-32R-300 · Watertown, WIInitiation of VFR flight into adverse weather and instrument meteorologial conditions. Factors which contributed to the accident were the adverse weather conditions and the pilot's self-induced pressure to maintain currency.NTSB CHI85LA286Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Appleton, WIAs the plt applied brakes during a full stop landing, the right brake failed. The plt then maneuvered the acft off the paved landing surface in an attempt to get it to roll to a stop. The right landing gear strut collapsed. The acft then slid into a fence and…NTSB CHI79FEP47Accident · No injuriesClosedPiper PA-32R · Burlington, WINTSB CHI78FEP41Accident · No injuriesClosedPiper PA-32 · Lakewood, WINTSB CHI77FEP07Accident · No injuriesClosedPiper PA-32R · Ashippun, WI