NTSB investigations: Piper PA-22-160
6 cases on aircraft the registry lists as Piper PA-22-160, 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 |
|---|---|
| 1986 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 2005 | 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\" = 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 ('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" = 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 ATL06CA011Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Bennettsville, SCThe malfunction of the wheel brake assembly due to low fluid level that resulted in a loss of control during the landing roll.NTSB CHI92LA177Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Breezy Point, MNThe partial failure of the tail wheel assembly due to a fatigue fracture of an internal spring.NTSB NYC91LA240Accident · Minor injuriesLimited investigationFinal reportPiper PA-22 · Slippery Rock, PAThe on ground collision with a farm vehicle during landing roll out.NTSB DEN90LA187Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Springdale, ARPilot's loss of control of the aircraft, during landing, due to mechanical malfunction of the tailwheel assembly.NTSB LAX87LA022Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Big Bear City, CAThe acft veered off rwy 7 during landing roll. The plt indicated the acft veered to the right. There was a single rubber skid mark aprx 150 ft long found on the rwy. The wind was reported by another plt to be 'down the runway at 10-15 knots.' Examination of…NTSB DEN83LA144Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Brighton, COAfter entering the landing pattern, the plt noted binding of the aileron control system. Reportedly the aileron controls seemed to lock, so he used the rudders for directional control & landed in a plowed field. During the landing, the acft nosed over. An…