NTSB investigations: Piper PA-32RT-300T
10 cases on aircraft the registry lists as Piper PA-32RT-300T, 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1990 | 3 |
| 1993 | 1 |
| 1997 | 1 |
| 2003 | 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\" = 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 ('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" = 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 ATL04IA028Incident · No injuriesIncident investigationFinal reportPiper PA-32RT-300T · Fayetteville, NCFlight control elevator attachment turnbuckle corrosion and fracture resulting in the loss of aircraft control in flight.NTSB FTW98LA055Accident · Minor injuriesLimited investigationFinal reportPiper PA-32RT-300T · Midlothian, TXfatigue failure of the #2 cylinder fuel injection line in an area where the line was previously damaged, which resulted in an in-flight engine compartment fire and a forced landing. Related factors were: the previous damage of the fuel injector line, and the…NTSB BFO93FA167Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Marshall, VAAn inadequate annual inspection of the airplane and non-compliance with airworthiness directives by company maintenance personnel.NTSB ANC90LA173Accident · 2 fatalLimited investigationFinal reportPiper PA-32RT-300T · Glacier Island, AKUndetermined mechanical failure(s) that resulted in loss of engine power, smoke in the cockpit, and a subsequent emergency descent for a forced landing (ditching) at sea. The lack of suitable terrain for a forced landing was a related factor.NTSB SEA90FA129Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Prineville, ORThe failure of the left intermediate exhaust pipe, in-flight engine fire and smoke in the cockpit, resulting in impairment of the pilot and his subsequent loss of control.NTSB DEN90LA054Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Provo, UTImproper installation by maintenance personnel and fatigue failure and leakage of the left intermediate exhaust pipe, which resulted in an in-flight fire in the engine compartment. Contributing factors were: inadequate service bulletin provided by the…NTSB MIA85FA202Accident · Minor injuriesField investigationFinal reportPiper PA-32RT-300T · Pembroke Pines, FLThe acft experienced a complete in flt loss of his prop after departure from north perry arpt hollywood FL due to a fatigue failure of the prop hub. The fatigue cracking was due to residual stress resulting from deformation of the material in the hub ass'yNTSB CHI85LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Bloomington, INPlt stated that while in cruise flt, the acft nose pitched down abruptly. Plt disengaged the autopilot and noted vacuum system was inoperative. Flt continued on manual control without further incident until late final approach at destination. When flaps were…NTSB FTW83LA305Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Port Mansfield, TXAccording to the plt, the nose gear position light flickered & the nose gear unsafe light illuminated, just prior to rotation. He reportedly aborted the takeoff at that time, but was unable to stop before going off the end of the rwy at 65 to 70 KTS. As the…NTSB DEN82DA110Accident · No injuriesFinal reportPiper PA-32RT-300T · Durango, COThe pilot reported that after taking off, dense white smoke began to fill the cockpit and seemed to come from under the instrument panel. He stated that the instruments were in the normal operating range, but the smoke became so dense that the visibility in…