NTSB investigations: Piper PA-32R-300, AZ
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
| 1977 | 1 |
|---|---|
| 1979 | 3 |
| 1987 | 1 |
| 2006 | 1 |
| 2009 | 1 |
| 2010 | 1 |
| 2017 | 1 |
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.\"eventStateOrRegion\" = 'AZ' 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" = 'AZ' 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 GAA17CA126Accident · No injuriesData collectionFinal reportPiper PA32R · Fort Mohave, AZThe pilot's failure to extend the landing gear for landing.NTSB WPR10FA287Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Eagar, AZThe pilot's operation of the aircraft outside of the manufacturer’s specified performance limitations, which resulted in the pilot's failure to maintain clearance from buildings and terrain during takeoff initial climb.NTSB WPR10LA051Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Tucson, AZA loss of engine power for undetermined reasons.NTSB ANC06LA021Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Winslow, AZThe presence of a foreign material/substance in the fuel system, which partially blocked the fuel flow divider, and resulted in a loss of engine power during takeoff-initial climb, and an emergency landing. A factor associated with the accident was unsuitable…NTSB LAX87LA245Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Tucson, AZAt the end of a business flt, the plt extended the landing gear and noted that the left main landing gear indicated that it was not down and locked. The plt activated the emergency landing gear extension which still indicated it was not down. While on final…NTSB LAX80FA114Accident · 2 fatalClosedPiper PA-32R · Safford, AZNTSB LAX79DUJ78Accident · No injuriesClosedPiper PA-32R · Long Mesa, AZNTSB LAX79FUJ56Accident · No injuriesClosedPiper PA-32R · Douglas, AZNTSB LAX77DUK06Accident · No injuriesClosedPiper PA-32 · Marble Canyon, AZ