NTSB investigations: Piper PA-22
6 cases on aircraft the registry lists as Piper PA-22, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 1 |
|---|---|
| 1987 | 1 |
| 1989 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2002 | 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 ('7102202')
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\" = 130))
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 ('7102202')
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" = 130))
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 SEA02LA061Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Friday Harbor, WAThe failure of the brake system during the landing roll. An intentional ground loop and a dirt bank were factors.NTSB SEA99LA103Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Billings, MTThe separation of the left main landing gear shock strut for undetermined reasons.NTSB ATL98LA102Accident · No injuriesLimited investigationFinal reportPiper PA-22 · New Bern, NCThe failure of the inner cable of the carburetor heat cable assembly that prevented the application of carburetor heat. Factors were conditions favorable for the formation of carburetor ice.NTSB FTW89LA111Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Austin, TXThe failure of the aircraft brake system. Factors include high tail wind.NTSB CHI87DEV03Accident · No injuriesFinal reportPiper PA-22 · Roanoke, ILAfter developing an oil leak the pilot elected to make a precautionary landing. The aircraft encountered rough terrain on touchdown and collapsed the nose gear and nosed over. The pilot and one passenger reported no injuries, however the aircraft was…NTSB NYC83LA222Accident · No injuriesLimited investigationFinal reportPiper PA-22 Tripacer · Butler, PAThe acft ran off the rwy into a 4 ft ditch and nosed over while taxiing. The plt said the 'brakes gave way' while he wastaxiing down rwy 17 after landing. When he realized the brakes were not holding he shut off the engine by the mixture control. To avoid…