NTSB investigations: Piper PA-32RT-300T
6 cases on aircraft the registry lists as Piper PA-32RT-300T, where the first occurrence was “Loss of engine power”. 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
| 1991 | 1 |
|---|---|
| 1992 | 1 |
| 1994 | 2 |
| 2002 | 1 |
| 2006 | 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 ('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\" = 350))
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" = 350))
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 DEN06LA045Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Manhattan, KSA loss of engine power due to the intermittent grounding of the left magneto "P" lead, causing the fuel controller to search and the engine to surge then lose power, and the pilot's failure to attain proper runway alignment. Contributing factors were the…NTSB CHI03LA023Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Longville, MNThe loss of engine power for undetermined reasons and the unsuitable terrain/landing area encountered by the pilot during a forced landing. The low altitude at the time of power loss was a contributing factor.NTSB FTW95FA069Accident · 1 fatalField investigationFinal reportPiper PA-32RT · San Antonio, TXThe loss of engine power for undetermined reasons. A factor related to the accident was: the lack of a suitable area for the forced landing.NTSB FTW94LA120Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Englewood, COA loss of power for undetermined reasons. A factor was the lack of suitable terrain for the forced landing.NTSB LAX92LA239Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Chino, CAThe loss of engine power for undetermined reasons. The pilot's misjuding the flare was a factor.NTSB MIA92LA040Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Daytona Beach, FLTotal loss of engine power for undetermined reasons.