NTSB investigations: Piper PA-32RT-300T
5 cases on aircraft the registry lists as Piper PA-32RT-300T, where the first occurrence was “Loss of engine power(total) - nonmechanical”. 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 |
|---|---|
| 1990 | 1 |
| 1994 | 1 |
| 1996 | 2 |
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 ('7103216')
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\" = 353))
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 ('7103216')
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" = 353))
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 CHI96LA333Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Chicago, ILthe pilot's improper fuel management, which resulted in fuel starvation and loss of engine power. A factor relating to the accident was: the pilot's improper flare during the forced landing.NTSB FTW96LA302Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Rogers, ARfuel exhaustion due to the pilot's failure to refuel. Factors were the below landing minimums weather conditions and the lack of suitable terrain for the forced landing.NTSB LAX94LA377Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · San Mateo, CAA deteriorated magneto grounding ('P' lead) and failure of maintenance personnel to detect this condition when the engine was reinstalled in the airframe after overhaul. The lack of suitable terrain for the forced landing was a factor.NTSB SEA90LA174Accident · No injuriesLimited investigationFinal reportPiper PA-32-300RT · Glenrock, WYFuel exhaustion resulting from the pilot's inadequate preflight planning/preparation. Unsuitable terrain was a factor related to the accident.NTSB BFO88FA060Accident · No injuriesField investigationFinal reportPiper PA-32RT-300T · Cambridge, MDThe pilot had departed ocean city, MD aprx 20 minutes after takeoff when nearing the chesapeake bay at an alt of 3000 ft MSL, a total loss of engine power was experienced. The plt attempted to restart the engine to no avail and a forced landing was made in a…