NTSB investigations: Piper PA-32-301
11 cases on aircraft the registry lists as Piper PA-32-301, where the first occurrence was “Loss of control - on ground/water”. 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 | 2 |
|---|---|
| 1985 | 3 |
| 1994 | 2 |
| 1996 | 1 |
| 2005 | 2 |
| 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 ('7103207')
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\" = 260))
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 ('7103207')
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" = 260))
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 CHI06CA103Accident · No injuriesData collectionFinal reportPiper PA-32-301 · Grayslake, ILThe pilot failed to compensate adequately for the crosswind condition and failed to maintain directional control during the landing roll. Contributing factors included the crosswind, the narrow runway, soft ground, and the ditch.NTSB LAX05CA307Accident · No injuriesData collectionFinal reportPiper PA-32-301 · Reno, NVthe pilot's inadequate compensation for wind conditions and failure to maintain directional control. Contributing factors to the accident were the gusting quartering tail wind conditions.NTSB MIA05CA099Accident · No injuriesData collectionFinal reportPiper PA32-301 · Brooksville, FLThe pilot-in-command failure to maintain directional control during takeoff after landing, which resulted in the airplane exiting the runway.NTSB CHI96LA086Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Marion, INthe pilot's failure to maintain directional control during landing.NTSB FTW94LA305Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Nacogdoches, TXThe pilot's inadequate compensation for crosswind during landing rollout. A factor was the variable crosswind.NTSB LAX94LA107Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-301 · Truckee, CAThe pilot's failure to maintain directional control, delay in his remedial action, and failure to raise the flaps. The snow covered runway was a factor in this accident.NTSB LAX86LA060Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · San Jose, CAAfter completing a personal flight the plt landed the acft. Upon touchdown on the 8899 ft-long by 150 ft-wide rwy the plt failed to maintain directional control of the acft. There was a 70 deg, 8 kt. Right x-wind. The acft overran the runway's edge, entered a…NTSB MKC85LA200Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Fredericktown, MOThe plt reports that he lost directional control during the landing roll. The acft swerved off the side of the rwy, down an embankment and collided with a fence. The landing and brake system were examined by a mechanic after the accident and no evidence of a…NTSB CHI85LA085Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Wheeling, ILThe low time pilot with six POB was ld at dark night light saw showers and icy patches on runway during rollout the acft entered a skid with nose cocked to the left the left main gear failed outboard and the acft exited the left side of the rwy the left wing…NTSB MKC84LA028Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Kearney, NEDuring the landing roll, the plt held the nosewheel off while slowing down, and used right rudder to compensate for a reported x-wind condition. As soon as the nosewheel touched down, the acft veered to the right. It went off the right side of the rwy, the…NTSB ATL84LA003Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Sewanee, TNThe acft collided with trees during landing roll. The plt has recounted several variations of the accident from locked brakes (parking) to a flat left tire with full right rudder to maintain directional control. There was a left tire skid mark from touchdown…