NTSB investigations: Piper PA-32R-301
5 cases on aircraft the registry lists as Piper PA-32R-301, where the first occurrence was “Overrun”. 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
| 1983 | 2 |
|---|---|
| 1985 | 1 |
| 1993 | 2 |
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103218')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103218')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340))
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 NYC94LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-301T · Norwood, MAThe pilot's delay in aborting the takeoff which resulted in a overrun of the runway. Factors were a snow covered runway, takeoff speed not attained, brakes not used, and a ditch.NTSB CHI93LA330Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Point Lookout, MOThe pilot's failure to attain the proper touchdown Point.NTSB NYC85LA170Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Provincetown, MADuring arrival, the acft was vectored for an ILS rwy 7 apch which was made with a tail wind. On his 1st attempt, the plt made a missed apch & was vectored for another ILS. After making a 2nd apch, he landed. The plt stated that while he was landing, he…NTSB CHI83LA280Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Minneapolis, MNThe acft ran off the end of the rwy and collapsed the nose gear during an aborted takeoff. The acft exceeded the maximum gross weight for takeoff by 190 lbs. Decision to abort was made about 2/3 of the way down the rwy. Braking was good and deceleration…NTSB ANC83LA031Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Wainwright, AKThe aircraft ran off the departure end of the runway during landing. A passenger stated that the aircraft touched down at about mid-field at a higher than normal airspeed and bounced once before sliding off the end of the runway. The gravel runway was covered…