NTSB investigations: Piper PA-22-160, CO
8 cases on aircraft the registry lists as Piper PA-22-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
| 1965 | 1 |
|---|---|
| 1974 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1999 | 1 |
| 2009 | 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\" = 'CO' 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 ('7102214'))
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" = 'CO' 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 ('7102214'))
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 CEN09CA464Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Fort Collins, COThe pilot's failure to maintain directional control while landing in gusty, crosswind conditions.NTSB DEN00LA035Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-160 · Brighton, COThe pilot's not following preflight procedures, the starvation of fuel to the engine, and the lack of suitable terrain for a forced landing.NTSB DEN87LA214Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Greeley, CON8433D was being flown by the plt/owner with an instructor aboard for the purpose of up-dating the owner's flying proficiency. Several successful landings were made, then a wheel landing was initiated. After touchdown, the acft swerved to the left, departed…NTSB DEN87LA005Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Fort Morgan, COThe student plt had just been endorsed for his first supervised solo flt. He had successfully completed one landing and was attempting his second landing when the accident occurred. The plt said he lost directional control, touched down, and over corrected.…NTSB DEN85LA006Accident · Serious injuriesLimited investigationFinal reportPiper PA-22 · Rocky Ford, COAccording to the plt, at 150 to 200 ft AGL the acft was unable to continue the climb or maintain alt. During the forced landing rollout in a corn field the acft nosed over and came to rest inverted. Engine disassembly revealed no mechanical malfunctions. The…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…NTSB DEN75DTE03Accident · No injuriesClosedPiper PA-22 · Akron, CONTSB DEN66F0149Accident · No injuriesClosedPiper PA-22 · Fountain, CO