NTSB investigations: Piper PA-28-160, OK
12 cases on aircraft the registry lists as Piper PA-28-160. 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
| 1964 | 1 |
|---|---|
| 1965 | 4 |
| 1967 | 2 |
| 1968 | 1 |
| 1972 | 1 |
| 1975 | 1 |
| 1987 | 1 |
| 1994 | 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\" = 'OK' 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 ('7102806'))
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" = 'OK' 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 ('7102806'))
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 FTW94LA234Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Tulsa, OKThe loss of engine power for undetermined reasons. The lack of terrain suitable for a forced landing was a factor.NTSB FTW87LA138Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Norman, OKWhile performing a touch and go landing, the aircraft landed hard causing a vibration in the engine area, and some loss of rudder control. The pilot flew by the tower and the tower indicated everything looked ok. On landing roll the nose gear failed causing…NTSB FTW75DPJ05Accident · No injuriesClosedPiper PA-28 · Goldsby, OKNTSB FTW72DPJ30Accident · No injuriesClosedPiper PA-28 · Duncan, OKNTSB FTW69D0186Accident · Minor injuriesClosedPiper PA-28 · Stigler, OKNTSB FTW68F0161Accident · Minor injuriesClosedPiper PA-28 · Blackwell, OKNTSB FTW68D0002Accident · No injuriesClosedPiper PA-28 · Pawhuska, OKNTSB FTW66D0433Accident · No injuriesClosedPiper PA-28 · Stigler, OKNTSB FTW66F0162Accident · No injuriesClosedPiper PA-28 · Tulsa, OKNTSB FTW66F0047Accident · No injuriesClosedPiper PA-28 · Oklahoma City, OKNTSB UNK65X1352Accident · No injuriesClosedPiper PA-28 · Russell, OKNTSB UNK65X1073Accident · No injuriesClosedPiper PA28 · Elmore City, OK