NTSB investigations: Piper PA-32RT-300
7 cases on aircraft the registry lists as Piper PA-32RT-300, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 1 |
|---|---|
| 1988 | 1 |
| 1994 | 1 |
| 1999 | 1 |
| 2001 | 2 |
| 2002 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103215')
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\" = 230))
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 ('7103215')
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" = 230))
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 IAD03FA019Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Bastian, VAThe pilot's failure to maintain an adequate altitude above terrain. Factors in the accident were the dark night conditions and the low cloud ceiling.NTSB NYC01LA120Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300 · Ithaca, NYThe pilot's failure to follow the published instrument approach procedure.NTSB MIA01FA107Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Concord, NCAn in-flight collision with terrain for undetermined reasons.NTSB ATL99FA048Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Cartersville, GAIn flight collision with terrain for undetermined reasons.NTSB MIA94FA067Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Sugarloaf Key, FLWas the failure of the pilot-in-command to perform a visual lookout and maintain his altitude. Contributing to the accident was the dark night, over water, visual descent.NTSB NYC88LA217Accident · 1 fatalLimited investigationFinal reportPiper PA-32RT-300 · Wellsboro, PAThe pilot attempting a takeoff in an over grossed aiarcraft in high density altitude and flew off the end of the runway into high grass.NTSB CHI82DA256Accident · No injuriesFinal reportPiper PA-32RT · Mackinac, MIAircraft landed wheels up. No malfunction of the landing gear system could be found.