NTSB investigations: Cessna 172N, MN
31 cases on aircraft the registry lists as Cessna 172N. 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
| 1978 | 2 |
|---|---|
| 1979 | 1 |
| 1980 | 1 |
| 1981 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1986 | 1 |
| 1987 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 1995 | 2 |
| 1998 | 1 |
| 1999 | 2 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 1 |
| 2006 | 1 |
| 2008 | 1 |
| 2017 | 1 |
| 2020 | 1 |
| 2023 | 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 ('2072434'))
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 ('2072434'))
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 CEN23LA400Accident · No injuriesClass 4 · LimitedFinal reportCessna 172N · Eden Prairie, MNThe pilot’s failure to maintain directional control during a landing with a left crosswind.NTSB CEN21LA003Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Hinckley, MNThe airplane’s impact with deer while landing.NTSB CEN18LA056Accident · No injuriesLimited investigationFinal reportCessna 172N · Maple Lake, MNThe pilot’s failure to maintain directional control while landing, which resulted in a runway excursion.NTSB CHI08CA069Accident · No injuriesData collectionFinal reportCessna 172N · South St. Paul, MNThe student pilot's failure to maintain directional control of the airplane during the landing roll. Contributing to the accident were the snow-covered runway and the gusty wind conditions.NTSB CHI07CA006Accident · No injuriesData collectionFinal reportCessna 172N · Grand Rapids, MNThe student pilot's misjudged landing flare and improper recovery from the bounced landing which led to the failure of the nose landing gear. The overload failure of the nose landing gear was a factor.NTSB CHI05CA034Accident · No injuriesData collectionFinal reportCessna 172N · Lakeville, MNThe pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.NTSB CHI03LA163Accident · No injuriesLimited investigationFinal reportCessna 172N · Anoka, MNThe pilot's failure to attain the proper touchdown point, and his failure to maintain directional control. Contributing factors were the pilot's lack of experience, and the runway sign.NTSB CHI03FA086Accident · 3 fatalField investigationFinal reportCessna 172N · Foley, MNThe pilot's continued visual flight into instrument meteorological conditions which led to spatial disorientation and subsequent impact with the ground. Contributing factors was the pilot's lack of instrument rating, the pilot's disregard of the preflight…NTSB CHI02LA175Accident · No injuriesLimited investigationFinal reportCessna 172N · Minneapolis, MNThe pilot did not maintain clearance from the vehicle while taxiing. A factor was the fuel truck.NTSB CHI99LA224Accident · No injuriesLimited investigationFinal reportCessna 172N · Faribault, MNthe pilot's failure to maintain directional control of the airplane during the takeoff ground run.NTSB CHI99LA188Accident · No injuriesLimited investigationFinal reportCessna 172N · Cloquet, MNa fire which initiated from an undetermined origin.NTSB CHI98LA331Accident · No injuriesLimited investigationFinal reportCessna 172N · Detroit Lakes, MNAn inadequate preflight inspection by the pilot which resulted in fuel exhaustion and subsequent loss of engine power.NTSB CHI95LA195Accident · No injuriesLimited investigationFinal reportCessna 172 · St Cloud, MNThe pilot's improper inflight planning/decision, which resulted in continued flight into adverse weather. Factors relating to the accident were: the thunderstorm outflow, and inadequate weather evaluation by the pilot.NTSB CHI95LA110Accident · No injuriesLimited investigationFinal reportCessna 172 · Nevis, MNthe loss of engine power due to a blockage caused by ice. A factor in the accident was the snow.NTSB CHI94LA296Accident · No injuriesLimited investigationFinal reportCessna 172 · Anoka, MNthe pilots decision to attempt a landing ahead of the approaching thunderstorm, and his failure to maintain directional control. A factor was the gusting crosswind ahead of the storm.NTSB CHI93LA065Accident · No injuriesLimited investigationFinal reportCessna 172N · Warren, MNThe student pilot's failure to maintain directional control.NTSB CHI92FA201Accident · 4 fatalField investigationFinal reportCessna 172N · St Paul, MNInadequate visual lookout by the pilots of both airplanes, which resulted in their failure to see-and-avoid conflicting traffic, and failure of the relieving controllers to use the radar display to identify and sequence an airplane entering the pattern.…NTSB CHI92LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Bemidji, MNInadequate preflight planning and preparation by the pilot in command, the non performance o fan emergency procedure and not maintaining a positive rate of climb on behalf of the pilot in command. Factors contributing to the accident were the pilot in…NTSB CHI91LA084Accident · No injuriesLimited investigationFinal reportCessna 172N · Rochester, MNInadequate compensation or wind conditions, and failure to maintain directional control by the pilot. Factors related to the accident are lack of total experience, and the crosswind conditions.NTSB CHI90FA252Accident · 1 fatalField investigationFinal reportCessna 172N · Pine City, MNThe pilot's misjudgement of the fuel supply, and his failure to maintain adequate airspeed. A factor was the pilot's lack of experience in the make and model of aircraft.NTSB MKC89LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Grand Rapids, MNThe pilot's failure to adequately compensate for the crosswind conditions. Contributing to the accident were the gusty crosswind conditions.NTSB CHI87LA205Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Perham, MNThe pilot was landing on a farm field to the east. The nearest wx station was reporting wind from 220 at 5 KTS. The pilot said after touchdown his speed was too fast to stop so he elected to abort the landing. During climbout the acft struck trees and crashed.NTSB CHI87FA083Accident · 4 fatalField investigationFinal reportCessna 172N · Fergus Falls, MNFollowing a 1.5 hour personal flight at night, the aircraft crashed into the side of a low hill near the destination airport. Although the pilot had a total of 6 hours of night time, most of his solo night time was during this last flight. Hazy VFR conditions…NTSB CHI86LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · St. Cloud, MNThe plt was diverting into galesburg due to bad weather at his original destination. Following an ILS approach at galesburg he spotted the rwy at '200 ft plus' off to his right. He then 'side-stepped' to the right but touched down in a crabbed angle. He…NTSB CHI83LA201Accident · No injuriesLimited investigationFinal reportCessna 172 · Austin, MNThe acft ran off the right side of the rwy during landing flare. The right wing tip struck the ground and the acft cartwheeled. The wind was reported as from 010 degrees at 25 KTS gusting to 33 KTS.NTSB CHI82DA269Accident · No injuriesFinal reportCessna 172N · Isle, MNThe pilot was on a cross-country flight and began an approach to a private airstrip. He reported that the weather conditions were good with light turbulence. About 100 ft from the threshold, the aircraft began to settle and the pilot added power. However, the…NTSB CHI82FA014Accident · 3 fatalClosedCessna 172 · Wolf Lake, MNNTSB CHI81FER10Accident · No injuriesClosedCessna 172N · Excelsior, MNNTSB MKC79FER25Accident · No injuriesClosedCessna 172 · Sabin, MNNTSB MKC78FA066Accident · 2 fatalClosedCessna 172N · Blaine, MNNTSB MKC78DER25Accident · No injuriesClosedCessna 172N · Crookston, MN