NTSB investigations: Piper PA-36-285, KS
6 cases on aircraft the registry lists as Piper PA-36-285. 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
| 1980 | 1 |
|---|---|
| 1984 | 1 |
| 1987 | 1 |
| 1997 | 1 |
| 2000 | 1 |
| 2013 | 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\" = '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 ('7103610', '7103611'))
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 ('7103610', '7103611'))
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 CEN13LA280Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-285 · Galena, KSThe loss of engine power due to improper maintenance by an unknown individual that led to the degradation and deterioration of the No. 2 piston, which was undetected because of overdue maintenance.NTSB CHI00LA243Accident · 1 fatalLimited investigationFinal reportPiper PA-36-285 · Osborne, KSThe unsuitable terrain for landing encountered by the pilot during the forced landing. Factors were the failure of the number four piston and cylinder, the soft terrain, and the main landing gear overload and subsequent collapse.NTSB CHI97LA217Accident · No injuriesLimited investigationFinal reportPiper PA-36-285 · Hill City, KSthe sustained partial loss of engine power due to low compression on one cylinder and the rough, uneven terrain.NTSB MKC87DCQ03Accident · 1 fatalFinal reportPiper PA-36 · Nickerson, KSAfter a swath run to the east, the acft was observed to pull up & begin turning back to the west. The witness then saw a big cloud of smoke. She did not see spray coming from the acft drg the last swath run, although her vision was limitedby foliage & bldgs.…NTSB MKC84LA258Accident · No injuriesLimited investigationFinal reportPiper PA-36-400 · Hill City, KSThe plt cleared some power lines and descended to spray a sunflower field. The acft descended until it contacted the flowers with the landing gear. The tall flowers destroyed the leading edges of the acft wings and the landing gear. The drag slowed the acft…NTSB MKC80DCQ21Accident · No injuriesClosedPiper PA-36 · Kanorado, KS