NTSB investigations: Piper PA-32R-301T
6 cases on aircraft the registry lists as Piper PA-32R-301T, 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
| 1986 | 1 |
|---|---|
| 1996 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2006 | 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 ('7103220', '7103221')
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 ('7103220', '7103221')
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 DFW07CA047Accident · No injuriesData collectionFinal reportPiper PA 32R 301T · Crystal Beach, TXThe pilot's touchdown too far down the runway resulting in an overrun. Factors were the wet grass runway and the trailer.NTSB LAX06CA193Accident · No injuriesData collectionFinal reportPiper PA-32R-301T · Gualala, CAthe pilot's misjudged distance and speed, which resulted in a runway overrun. A contributing factor was the hump in the runway.NTSB CHI01LA010Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Tecumseh, MIThe pilot was unable to rotate the aircraft during takeoff for undetermined reasons. A factor associated with the accident was the soft terrain, which the airplane encountered during the aborted takeoff.NTSB LAX99LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Apple Valley, CAThe pilot's inadvertent use of the aircraft's brakes while using the rudder pedals to maintain directional alignment during the takeoff roll.NTSB CHI97LA028Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-301T · Lansing, ILthe pilot's improper planning/decision, and his failure to go around, while there was still sufficient runway remaining. The unfavorable wind condition was a related factor.NTSB MIA87LA032Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Cedar Key, FLThe plt stated that he was not able to see the lighted wind sock from 1000 ft as he was unfamiliar with its location. The acft landed downwind on the rwy & was unable to stop before running off the end. A 15 to 20 kt tailwind was present at the time. The plt…