NTSB investigations: Cessna 172P, WY
7 cases on aircraft the registry lists as Cessna 172P. 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
| 1980 | 1 |
|---|---|
| 1982 | 2 |
| 1983 | 1 |
| 1991 | 1 |
| 1994 | 1 |
| 1997 | 1 |
Where
Latest 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\" = 'WY' 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 ('2072436'))
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" = 'WY' 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 ('2072436'))
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 SEA97FA076Accident · 1 fatalField investigationFinal reportCessna 172P · Burlington, WYloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB SEA94LA130Accident · Minor injuriesLimited investigationFinal reportLatter Christen Eagle II · Jackson Hole, WYThe failure of the pilot of the christen eagle ii, N246RL, to see and avoid the Cessna 172, N62463, and the pilot of the christen eagle ii diverting his attention from operation of his airplane.NTSB SEA91LA112Accident · No injuriesLimited investigationFinal reportCessna 172P · Alva, WYThe pilot's overconfidence in his personal ability, overconfidence in the aircraft's ability. Contributing to the accident was the engine failure.NTSB DEN83FA116Accident · 2 fatalField investigationFinal reportCessna 172P · Lander, WYAt noon on 5/21/83, the plt departed riverton, WY on a flt to ogden, ut to transport a minister back to riverton for a wedding. After arriving at ogden, he obtained a wx briefing for the return flt. He was warned of possible thunderstormactivity, turbulence,…NTSB DEN82DA204Accident · No injuriesFinal reportCessna 172 · Rock Springs, WYAccording to the pilot, a strong gust of wind lifted the aircraft during the landing and power was applied for a go-around. Another gust of wind forced the aircraft off the runway into the dirt next to the runway. When the aircraft departed the runway, the…NTSB DEN82FTC04Accident · 1 fatalFinal reportCessna 172P · Osage, WYThe aircraft departed gillette, Wyoming on a pipeline patrol mission. This was the pilot's first pipeline patrol over the line that he was patrolling. During the flight, the aircraft struck three powerlines and crashed. The passenger stated that he saw the…NTSB DEN81FTC05Accident · No injuriesClosedCessna 172 · Rock Springs, WY