NTSB investigations: Piper PA-22-160
5 cases on aircraft the registry lists as Piper PA-22-160, where the first occurrence was “Nose over”. 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
| 1982 | 1 |
|---|---|
| 1989 | 1 |
| 1995 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102214')
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\" = 300))
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 ('7102214')
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" = 300))
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 CHI00LA106Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Saint Joseph, MOthe pilot's inadequate compensation for the wind condition. A factor to the accident was the high winds.NTSB SEA98LA137Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Pacific City, ORThe pilot's improper compensation for wind conditions (landing with a tail wind.) Related factors were tail wind conditions, a short runway, and diminished brake system effectiveness.NTSB SEA96LA018Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Seeley Lake, MTThe pilot's selection of unsuitable terrain for landing. The snow covered runway was a factor.NTSB LAX89LA148Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Lancaster, CAImproper planning/decision by the pilot. Strong/gusty winds contributed to the accident.NTSB NYC82DA202Accident · No injuriesFinal reportPiper PA-22-160 · Tunkhannock, PADuring a landing in calm wind conditions, the aircraft was high on final approach, so the pilot added flaps and slipped the plane to lose altitude. He touched down about 1000 ft down the 2000 ft runway. He reported that after landing, he applied the brakes,…