NTSB investigations: Piper PA-32R-301T
10 cases on aircraft the registry lists as Piper PA-32R-301T, where the first occurrence was “In flight collision with object”. 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
| 1987 | 1 |
|---|---|
| 1988 | 1 |
| 1989 | 1 |
| 1994 | 1 |
| 2000 | 1 |
| 2001 | 2 |
| 2003 | 1 |
| 2004 | 2 |
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 ('7103220', '7103221')
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\" = 220))
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 ('7103220', '7103221')
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" = 220))
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 SEA04LA180Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Picabo, IDThe pilot's failure to set the propeller control for takeoff performance needed to outclimb obstacles. The pilot's failure to use the checklist, trees, and a fence are contributing factors.NTSB FTW04CA061Accident · No injuriesData collectionFinal reportPiper PA-32R · Poynor, TXThe pilot's failure to maintain aircraft control while on final approach. A factor was the downdraft.NTSB LAX03LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Paulden, AZthe pilot's failure to attain and maintain the proper climb airspeed. The high density altitude condition was a factor.NTSB LAX02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Groveland, CAThe pilot's collision with an unobserved animal that entered the active runway during the dark nighttime when the pilot's visibility was diminished.NTSB CHI01FA312Accident · Serious injuriesField investigationFinal reportPiper PA-32R-301T · Downers Grove, ILthe improper preflight planning/preparation and the short field take off/procedure not followed by the pilot. Contributing factors were the airplane's forward center of gravity, the variable gusting wind and improper weight and balance calculations by…NTSB NYC00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Harpswell, MEwas the improper decision of the pilot to depart at night, from an unlighted runway with no visual references to obstructions on the sides of the runway. Factors were the dark night conditions, and the lack of runway side lights.NTSB LAX94FA157Accident · 3 fatalField investigationFinal reportPiper PA-32R-301T · Napa, CAthe pilot's selection of an en route descent altitude profile inadequate to clear all terrain along his intended flight path, and, his inadvertent VFR flight into IMC conditions. Factors in the accident were the dark night lighting conditions and the obscured…NTSB FTW89FA137Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Celina, TXImproper planning/decision by the pilot. Related factors were: failure of the pilot to use all of the available runway area, the runway/terrain conditions, and obstructions/power lines beyond the departure end of the runway.NTSB MIA88LA193Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Lake Wales, FLDuring takeoff from the grass strip, the left main landing gear and wingtip collided with runway lights & a fencepost. The acft was slow to climb. After clearing trees at the departure end of the rwy, the acft descended below treetop level, then continued to…NTSB MKC88FA019Accident · 2 fatalField investigationFinal reportPiper PA-32R · Fayetteville, ARThe airplane was cleared to land while on downwind. Tower saw lights and said airplane appeared to be flying around hill north of airport. Investigation revealed airplane had turned left and impacted trees below the top of the hill.