NTSB investigations: Piper PA-32R-301T
4 cases on aircraft the registry lists as Piper PA-32R-301T, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1988 | 1 |
|---|---|
| 1993 | 1 |
| 1995 | 1 |
| 2000 | 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 ('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\" = 130))
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" = 130))
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 LAX00LA112Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Coalinga, CAThe failure of the landing gear for undetermined reasons to go into the locked position after the pilot conducted a manual and emergency gear extension. A factor in the accident was the undetermined failure of the electrical system.NTSB LAX95LA292Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Truckee, CAA failure in the aircraft electrical system, and the pilot's failure (or inability) to extend the landing gear with the emergency extension system. A factor relating to the accident was: the pilot's decision to continue the flight with a known deficiency.NTSB ATL94FA029Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Covington, GASpatial disorientation experienced by the pilot, resulting in his failure to maintain aircraft control. Factors were the total failure of the engine driven vacuum pump, and the night, cloud conditions prevailing at the time of the accident.NTSB CHI88LA170Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Chicago, ILDuring climbout after takeoff, the pilot experienced an engine fire and diverted to Chicago's midway airport for an emergency landing. The pilot executed emergency procedures, shut down the engine, the fuel supply, and all electrical load. When the pilot knew…