NTSB investigations: Cessna 172M, MN
41 cases on aircraft the registry lists as Cessna 172M. 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
| 1974 | 1 |
|---|---|
| 1975 | 1 |
| 1976 | 3 |
| 1977 | 6 |
| 1978 | 4 |
| 1979 | 1 |
| 1980 | 2 |
| 1982 | 1 |
| 1983 | 1 |
| 1989 | 2 |
| 1990 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2005 | 2 |
| 2007 | 1 |
| 2010 | 1 |
| 2012 | 2 |
| 2013 | 1 |
| 2015 | 1 |
| 2017 | 1 |
| 2019 | 2 |
| 2023 | 1 |
| 2024 | 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 ('2072418'))
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 ('2072418'))
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 CEN24LA168Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172M · Clearbrook, MNThe pilot’s delayed use of carburetor heat which resulted in the loss of engine power due to carburetor icing.NTSB CEN24LA072Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Red Lake, MNThe pilot’s inadequate landing surface evaluation and failure to stop the airplane on the frozen lake, which resulted the airplane continuing into a crack in the ice.NTSB CEN20LA042Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Rush City, MNThe total loss of engine power due to fuel starvation because the student pilot failed to reposition the fuel mixture control to full rich before takeoff.NTSB GAA19CA118Accident · No injuriesData collectionFinal reportCessna 172 · Appleton, MNThe student pilot’s loss of directional control while landing on an ice-covered runway, which resulted in a loss of directional control, and his failure to attain sufficient airspeed during a subsequent aborted landing, which resulted in a nose-over.NTSB CEN18FA011Accident · 2 fatalField investigationFinal reportCessna 172M · Ramsey, MNThe pilot's decision to fly along the river at a low altitude contrary to applicable regulations and safety of flight considerations which resulted in the impact with the power lines. Contributing to the accident was the pilot's inability to see the and avoid…NTSB CEN16CA070Accident · No injuriesData collectionFinal reportCessna 172 · Rush City, MNThe student pilot did not maintain directional control of the airplane and applied excessive right rudder during landing.NTSB CEN13CA272Accident · No injuriesData collectionFinal reportCessna 172M · Thief River Falls, MNThe pilot’s failure to maintain clearance from the power line while on approach to landing.NTSB CEN13CA112Accident · No injuriesData collectionFinal reportCessna 172M · Eveleth, MNThe student pilot’s improper landing flare, which resulted in a hard nosewheel landing.NTSB CEN13LA088Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Rochester, MNThe pilot’s spatial disorientation during the instrument approach in night, instrument meteorological conditions, which resulted in the airplane descending below decision height and impacting terrain outside the lateral limits of the localizer. Contributing…NTSB CEN10CA576Accident · No injuriesData collectionFinal reportCessna 172M · Belle Plaine, MNThe pilot's loss of directional control due to an encounter with soft terrain while landing.NTSB CHI08CA030Accident · No injuriesData collectionFinal reportCessna 172M · Duluth, MNThe pilot's inadequate compensation for wind conditions during the landing approach. Contributing to the accident was the crosswind weather condition.NTSB CHI06CA004Accident · Minor injuriesData collectionFinal reportCessna 172M · Lake Elmo, MNThe pilot's inadequate recovery from a bounced landing, which resulted in an overload failure of the nose landing gear. Contributing to the accident was a loss of engine power due to fuel exhaustion as a result of inadequate preflight planning by the pilot.NTSB CHI05CA152Accident · No injuriesData collectionFinal reportCessna 172M · Rochester, MNThe pilot flared improperly and failed to recover from a bounced landing.NTSB CHI01LA127Accident · No injuriesLimited investigationFinal reportCessna 172M · Eveleth, MNThe pilot's inadequate compensation for the crosswind conditions which resulted in the loss of aircraft control. Factors associated with the accident were the gusty crosswind condition, the pilot's lack of experience, and the trees which were contacted.NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Brainerd, MNThe visual lookout not obtained/maintained by the pilot of the other aircraft. Contributing factors were the unicom frequency not selected and the traffic advisory not issued by the pilot of the other aircraft. An additional factor was the aircraft moving on…NTSB CHI96LA256Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Backus, MNthe pilot's failure to maintain adequate altitude and his abrupt maneuver to avoid the tree tops. The dark night was a factor.NTSB CHI95FA307Accident · 1 fatalField investigationFinal reportCessna 172M · Orr, MNthe pilot misjudged the landing flare. Factors associated with the accident were the visual illusion caused by the glassy smooth water condition and the forward center of gravity.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 CHI91LA057Accident · No injuriesLimited investigationFinal reportCessna 172M · Austin, MNThe pilot-in-command (student)'s failure to properly evaluate and compensate for gusty wind condiitons and to maintain directional of the aircraft during initial climb. Contributing was the student pilot's lack of total experience and wind gusts.NTSB MKC89LA186Accident · No injuriesLimited investigationFinal reportCessna 172 · Clear Lake, MNThe pilot's improper decision in attempting to land with inadequate visual cues which precluded identification of a correct runway alignment. A suitable alternative airport was readily available.NTSB MKC89LA157Accident · No injuriesLimited investigationFinal reportCessna 172 · Crystal, MNAircraft control was not maintained by the pilot in command, due to an improper landing flare which resulted in several bounces. The landing gear failed in overload during the bounced landing.NTSB CHI83LA409Accident · No injuriesLimited investigationFinal reportCessna 172M · Grand Marais, MNThe plt took off from the departure point after an unexpected 1/2 hr delay. By the time he arrived at his destination, it was dark. No rwy lighting sys was installed, so someone at the arpt drove a car to rwy 27 to light up the approach end with the head…NTSB CHI82DA044Accident · No injuriesFinal reportCessna 172 · Anoka, MNThe pilot was practicing touch and go landings. He reported that on his last landing, the wind pushed him toward the right side of the runway. The right main gear encountered snow and pulled the aircraft further to the right into a drift beside the runway.…NTSB CHI80DER53Accident · No injuriesClosedCessna 172 · Fosston, MNNTSB CHI80FA041Accident · 4 fatalClosedCessna 172K · Big Fork, MNNTSB MKC79FA030Accident · 2 fatalClosedCessna 172M · Grand Marais, MNNTSB MKC78DER89Accident · No injuriesClosedCessna 172M · Hibbing, MNNTSB MKC78FER69Accident · No injuriesClosedCessna 172 · Ada, MNNTSB MKC78DER48Accident · Minor injuriesClosedCessna 172M · Halstad, MNNTSB MKC78DER34Accident · No injuriesClosedCessna 172 · Montevideo, MNNTSB MKC78FER15Accident · No injuriesClosedCessna 172M · St.Agusta, MNNTSB MKC78FER02Accident · No injuriesClosedCessna 172 · Afton, MNNTSB MKC77DER86Accident · No injuriesClosedCessna 172 · Sanborn, MNNTSB MKC77FA036Accident · 1 fatalClosedCessna 172M · Henning, MNNTSB MKC77DER36Accident · No injuriesClosedCessna 172 · Erskine, MNNTSB MKC77FER24Accident · No injuriesClosedCessna 172 · Backus, MNNTSB MKC77DER06Accident · No injuriesClosedCessna 172 · Monticello, MNNTSB MKC76DES02Accident · Minor injuriesClosedCessna 172 · Dodge Center, MNNTSB MKC76DER99Accident · No injuriesClosedCessna 172 · Mahnomen, MNNTSB MKC75FER40Accident · No injuriesClosedCessna 172M · Eden Prairie, MNNTSB MKC74DER33Accident · No injuriesClosedCessna 172M · Forrest Lake, MN