NTSB investigations: Cessna R172K, MN
7 cases on aircraft the registry lists as Cessna R172K. 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
| 1976 | 1 |
|---|---|
| 1979 | 1 |
| 1982 | 1 |
| 1985 | 1 |
| 1996 | 1 |
| 2006 | 1 |
| 2020 | 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\" = 'MN' 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 ('2072431'))
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" = 'MN' 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 ('2072431'))
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 CEN20CA188Accident · No injuriesClass 4 · Data collectionFinal reportCessna R172 · Lino Lakes, MNThe pilot's loss of directional control during takeoff with a crosswind.NTSB CHI06LA212Accident · No injuriesLimited investigationFinal reportCessna R172K · Grand Rapids, MNThe pilot's failure to maintain control of the airplane during the landing. A factor associated with the accident was the gusty tailwind that prevailed.NTSB CHI96LA093Accident · No injuriesLimited investigationFinal reportCessna 172 · Worthington, MNProgressive failure of the engine, beginning with failure of the left magneto, which resulted in preignition or detonation, a burned hole in the #3 piston, subsequent oil exhaustion, and failure of the #1 and #2 connecting rods.NTSB CHI85LA333Accident · No injuriesLimited investigationFinal reportCessna 172XP · Int'L Falls, MNThe acft veered hard to the rt & collided with the water during takeoff at about 45 mph. It was discovered that the left float failed and allowed the left float to turn rt and go under the rt float.NTSB CHI83LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · Sacred Heset, MNWhile on a flight to photograph farms, the engine lost power and the pilot was unable to get it restarted. An emergency landing was made in a bean field that was soft from recent rains. Shortly after touchdown, the aircraft nosed over. After the accident,…NTSB MKC79FA055Accident · 2 fatalClosedCessna 172XP · Intl Falls, MNNTSB MKC76DER93Accident · No injuriesClosedCessna 172 · Crane Lake, MN