NTSB investigations: Piper PA-32RT-300T, AL
6 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
| 1982 | 1 |
|---|---|
| 1986 | 1 |
| 1999 | 1 |
| 2004 | 1 |
| 2020 | 1 |
| 2021 | 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.\"eventStateOrRegion\" = 'AL' 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" = 'AL' 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 ERA21FA133Accident · 2 fatalClass 3 · FieldFinal reportPiper PA32RT · Vinemont, ALA loss of engine power for reasons that could not be determined.NTSB ERA20LA212Accident · 2 fatalClass 3 · LimitedFinal reportPiper PA32RT · Selma, ALThe mechanic’s failure to clean the oil suction screen during the most recent maintenance, which resulted in oil starvation and subsequent total loss of engine power.NTSB ATL05LA007Accident · Serious injuriesLimited investigationFinal reportPiper PA-32RT-300T · Guntersville, ALTotal loss of engine power due to engine oil contamination, engine oil starvation, and multiple connecting rod bearing failures.NTSB MIA00FA043Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Pelham, ALThe student pilot's decision to continue the visual flight rules flight into deteriorating visibility, and his failure to maintain altitude clearance with the terrain.NTSB ATL86LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300T · Fort Deposit, ALShortly after takeoff smoke and flames entered the cockpit. The pilot returned to the airport and landed hard damaging the firewall. Examination of the aircraft revealed that the turbo charger exhaust clamp broke and allowed hot exhaust gases to ignite a fire…NTSB ATL82FKJ11Accident · Serious injuriesFinal reportPiper PA-32 · Muscle Shoals, ALDuring the approach the pilot stated that he could not extend the landing gear. At some point during the approach the aircraft broke out into VFR conditions. The pilot stated he had the airport in sight when the aircraft struck a 160,000 volt power line.…