NTSB investigations: Piper PA-32RT-300T, TX
15 cases on aircraft the registry lists as Piper PA-32RT-300T. 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
| 1979 | 1 |
|---|---|
| 1980 | 2 |
| 1983 | 1 |
| 1985 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1994 | 1 |
| 1997 | 1 |
| 2015 | 1 |
| 2017 | 1 |
| 2019 | 1 |
| 2022 | 3 |
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.\"eventStateOrRegion\" = 'TX' 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 ('7103216'))
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" = 'TX' 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 ('7103216'))
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 CEN22LA413Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32RT · Bulverde, TXThe partial loss of engine power due to excessive carbon deposits that resulted in one or more stuck exhaust valves.NTSB CEN22LA344Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA-32RT-300T · Dallas, TXMaintenance personnel’s inadequate maintenance of the magneto, which resulted in a loss of engine ignition, a loss of engine power, and a subsequent forced landing.NTSB CEN22LA307Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32RT-300T · Frankston, TXThe pilot’s delayed aborted takeoff that resulted in a runway overrun and impact with terrain.NTSB CEN19LA076Accident · Minor injuriesLimited investigationFinal reportPiper PA32RT · Pflugerville, TXThe pilot's fuel mismanagement and his improper use and placement of the fuel selector, contrary to operating procedures, which resulted in a partial loss of engine power due to fuel starvation.NTSB CEN18LA017Accident · No injuriesLimited investigationFinal reportPiper PA 32RT-300T · Port Mansfield, TXThe pilot’s improper landing flare, which led to a hard landing and the subsequent collapse of the nosewheel landing gear due to the overstress failure of the nosewheel landing gear trunnion casting.NTSB CEN15LA149Accident · No injuriesLimited investigationFinal reportPiper PA 32RT-300T · Lubbock, TXThe pilot's delayed decision to abort the takeoff after the airplane did not lift off as expected due to an inaccurate airspeed indication and tailwind condition, which resulted in a subsequent runway overrun.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 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 FTW91LA047Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300T · Leander, TXThe pilot's failure to maintain a proper descent rate during the final approach.NTSB FTW90FA177Accident · Serious injuriesField investigationFinal reportPiper PA-32RT-300T · Addison, TXFatigue failure of the throttle cable. Factors related to the accident were: darkness and objects (fence and utility poles) in the emergency landing area.NTSB FTW85LA273Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Brownsville, TXWhile practicing touch-and-go landings the plt allowed the acft to descend below the proper glide slope while on final apch. The acft impacted a power line aprx 1000 ft short of the rwy and crashed on the side of a drainage ditch levee. The elevation of the…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 FTW80DPD48Accident · No injuriesClosedPiper PA-32 · Decatur, TXNTSB FTW80FQD05Accident · No injuriesClosedPiper PA-32 · El Paso, TXNTSB FTW79DQD11Accident · No injuriesClosedPiper PA-32 · Kent, TX