NTSB investigations: Piper PA-22-108, SD
7 cases on aircraft the registry lists as Piper PA-22-108. 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
| 1966 | 1 |
|---|---|
| 1970 | 1 |
| 1976 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1998 | 1 |
| 2000 | 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\" = 'SD' 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 ('7102204'))
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" = 'SD' 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 ('7102204'))
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 CHI00FA288Accident · 2 fatalField investigationFinal reportPiper PA-22-108 · Custer, SDThe pilot not maintaining clearance from the tree. Factors relating to this accident were the pilot's inadequate preflight planning and preparation, the high density altitude, the inadequate rate of climb, the pilot's improper in-flight decision to fly into…NTSB CHI98LA235Accident · 1 fatalLimited investigationFinal reportPiper PA-22-108 · Spearfish, SDthe pilots improper preflight planning, which failed to detect the fuel selector positioned on the left fuel tank, which had insufficient fuel, resulting in fuel starvation, and the loss of engine power.NTSB DEN88LA183Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Hoven, SDThe private plt and his wife were going to make a local flight in their airplane at 0215. The plt said he hand- propped the acft and moved to enter the cabin as the engine started. The acft began to move, and his wife pulled the parking brake lock, which…NTSB DEN87LA133Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Milbank, SDThe private plt and a pax were on a local flt. On climb out, at about 50 feet AGL, the engine had partial pwr loss. The plt landed straight ahead in a field and made a successful forced landing. On roll out, the nose wheel fell into a hole and the acft nosed…NTSB MKC77DTK01Accident · No injuriesClosedPiper PA-22 · Huron, SDNTSB MKC71DDQ08Accident · No injuriesClosedPiper PA-22 · Chamberlain, SDNTSB MKC67D0293Accident · No injuriesClosedPiper PA-22 · Spearfish, SD