NTSB investigations: Piper PA-32R-300, KS
7 cases on aircraft the registry lists as Piper PA-32R-300. 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
| 1978 | 1 |
|---|---|
| 1981 | 1 |
| 1986 | 1 |
| 1996 | 1 |
| 2002 | 1 |
| 2008 | 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.\"eventStateOrRegion\" = 'KS' 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 ('7103213'))
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" = 'KS' 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 ('7103213'))
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 DFW08CA236Accident · No injuriesData collectionFinal reportPiper PA-32R-300 · Augusta, KSA loose oil line that resulted in a total loss of engine oil, causing the engine to cease.NTSB DFW08LA133Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Emporia, KSA total loss of engine power due to fuel starvation as a result of a blocked fuel outlet caused by the peeling off of a previously approved fuel tank sealer.NTSB CHI02LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Beaumont, KSThe pilot's inadequate preflight planning and his failure to abort the takeoff when he realized the aircraft was not accelerating as expected. The wet and muddy turf runway was a contributing factor.NTSB CHI97LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Garnett, KSthe pilot's improper in-flight planning/decision, including a delay in proceeding to an alternate airport after encountering fog during a night approach, which resulted in loss of engine power due to fuel exhaustion.NTSB MKC86LA047Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Lawrence, KSThe plt stated he mistook an ice and snow covered area for a taxiway and turned off past the actual taxiway. The acft struck a snowbank which collapsed the nosegear. The blue taxiway light was out. This light marks the edge of taxiway. The taxiway was free of…NTSB MKC81DCQ14Accident · No injuriesClosedPiper PA-32R · Osborne, KSNTSB MKC78FCQ13Accident · Serious injuriesClosedPiper PA-32R · Wichita, KS