NTSB investigations: Piper PA-32R-301, FL
5 cases on aircraft the registry lists as Piper PA-32R-301. 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
| 1983 | 1 |
|---|---|
| 1984 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 2002 | 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\" = 'FL' 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 ('7103218'))
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" = 'FL' 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 ('7103218'))
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 ATL02LA149Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Ft. Lauderdale, FLPilot in command failed to maintain directional control of the airplane during the landing roll that resulted in a ground loop and the overload failure of the right main landing gear.NTSB MIA93LA042Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301 · Titusville, FLLoss of engine power during the downwind leg for undetermined reasons, poor in-flight planning/decision by the dual student, and inadequate supervision by the pilot-in-command (CFI).NTSB MIA91LA081Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Plant City, FLFailure of the pilot to maintain proper alignment during the landing roll, excessive rudder input, and loss of directional control resulting in the collapse of the right main landing gear.NTSB MIA85LA045Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Cross City, FLPlt stated that after touchdown as braking was initiated the acft began to pull to the left. Right brake was applied with no correcting effect. The acft ran off the left side of the runway and the landing gear collapsed. Post crash exam of brakes revealed no…NTSB MIA83LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32-301R · Near Vero Beach, FLThe acft collided with tree tops during a night flight but the pilot was able to maintain control and land at a nearby airport. According to the pilot he was on approach to fort pierce airport when the accident occurred. However according to some witnesses…