NTSB investigations: Cessna 172M
51 cases on aircraft the registry lists as Cessna 172M, where the sequence of events included Runway excursion. 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
| 2008 | 3 |
|---|---|
| 2010 | 2 |
| 2011 | 2 |
| 2012 | 4 |
| 2013 | 1 |
| 2014 | 7 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 5 |
| 2018 | 3 |
| 2019 | 2 |
| 2020 | 2 |
| 2021 | 4 |
| 2022 | 5 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 2 |
| 2026 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
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 CEN26LA138Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Solon Springs, WIThe pilot’s loss of directional control during landing, which resulted in a runway excursion and collision with terrain.NTSB ANC26LA008Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Palmer, AKThe student pilot’s failure to maintain directional control during the landing roll.NTSB CEN25LA230Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Wichita, KSThe student pilot’s failure to maintain directional control during the takeoff that resulted in a runway excursion.NTSB ERA24LA270Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Hernando, FLThe pilot’s inadvertent throttle input during landing which resulted in a runway overrun.NTSB ERA23LA375Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Winston-Salem, NCThe pilot’s loss of directional control upon landing which resulted in substantial damage to the left wing and left horizontal stabilizer.NTSB WPR23LA315Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Marysville, CAThe flight instructor’s failure to monitor the airplane’s speed during a high-speed taxi, resulting in a runway excursion.NTSB CEN23LA154Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Terrell, TXThe student pilot’s failure to maintain directional control during landing and the flight instructor’s delayed remedial response.NTSB ERA23LA043Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172M · Roberta, GAThe pilot’s failure to maintain a stabilized approach speed on landing, which resulted in a runway excursion and collision with logs.NTSB CEN22LA445Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Monticello, IAThe pilot’s failure to maintain a proper approach airspeed and glidepath which resulted in a long landing and his inability to stop the airplane on available runway and the subsequent runway excursion.NTSB WPR22LA356Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Superior, MTThe pilot’s excessive airspeed during a landing, which resulted in a runway overrun and collision with terrain.NTSB WPR22LA194Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · East Sound, WAThe pilot's failure to attain a proper touchdown point which, resulted in a runway overrun and collision with trees.NTSB ERA22LA113Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Waynesboro, VAThe student pilot’s loss of directional control while landing.NTSB CEN21LA392Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Olive Branch, MSThe pilot’s failure to maintain directional control of the airplane during landing with a direct crosswind that resulted in an impact with terrain.NTSB ERA21LA198Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Fredericksburg, VAThe student pilot reported that, during the landing roll, he applied brakes and the airplane veered right. He was unable to correct back to the centerline or brake effectively; the airplane exited the runway and struck an embankment before coming to rest. The…NTSB ERA21LA168Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Crystal River, FLThe student pilot’s inadequate compensation for a crosswind during landing, which resulted in a loss of directional control and a runway excursion.NTSB CEN21LA120Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Clare, MIThe pilot’s failure to maintain directional control during landing that resulted in a runway excursion and impact with terrain.NTSB ERA20CA235Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Chesapeake, VAThe student pilot's improper landing flare and failure to recover from the ensuing bounced landing, which resulted in a runway excursion.NTSB CEN20CA154Accident · No injuriesData collectionFinal reportCessna 172 · Ft Worth, TXThe student pilot’s failure to maintain a stabilized approach and the flight instructor's delayed remedial action to initiate a go-around, which resulted in a runway overrun and impact with runway lights and fences.NTSB ERA19TA192Accident · No injuriesClass 3Final reportCessna 172 · Stafford, VAThe pilot’s failure to maintain directional control while landing in gusting crosswind conditions, which resulted in a runway excursion.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 WPR19TA034Accident · Minor injuriesClass 3Final reportCessna 172 · Colorado Springs, COThe pilot's decision to perform a touch-and-go landing at a high-density altitude airport, with a tailwind, and on an upsloping runway, which resulted in decreased airplane performance and the airplane’s inability to become airborne within the available…NTSB GAA18CA141Accident · No injuriesData collectionFinal reportCessna 172 · Show Low, AZThe flight instructor’s failure to maintain directional control during the landing roll in gusting crosswind and tailwind conditions.NTSB GAA18CA135Accident · No injuriesData collectionFinal reportCessna 172 · Broomfield, COThe pilot’s failure to maintain directional control of the airplane during the landing roll in gusting wind conditions.NTSB GAA18CA005Accident · No injuriesData collectionFinal reportCessna 172 · Black River Falls, WIThe pilot’s failure to maintain directional control during landing in gusting crosswind conditions.NTSB GAA17CA556Accident · No injuriesData collectionFinal reportCessna 172 · Gallatin, TNThe student pilot’s improper landing flare, which resulted in a bounced landing.NTSB GAA17CA341Accident · No injuriesData collectionFinal reportCessna 172 · Galena, IDThe pilot's exceedance of the airplane’s critical angle of attack, which resulted in a power-on stall and subsequent loss of airplane control.NTSB GAA17CA186Accident · No injuriesData collectionFinal reportCessna 172 · Hillsboro, ORThe pilot's failure to maintain directional control during the landing roll in quartering tailwind conditions.NTSB CEN17LA082Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Hobart, INThe pilot's failure to abort the landing when he recognized the airplane was traveling too fast, which resulted in impact with trees off the end of the runway.NTSB GAA17CA080Accident · No injuriesData collectionFinal reportCessna 172 · Woodbine, NJThe student pilot's improper landing flare, which resulted in a porpoised landing.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 GAA15CA049Accident · No injuriesData collectionFinal reportCessna 172M · Clearwater, FLThe pilot's excessive airspeed during landing, which resulted in abnormal runway contact, a runway excursion, and substantial damage to the airplane.NTSB CEN15CA097Accident · No injuriesData collectionFinal reportCessna 172M · Marquette, MIThe pilot did not maintain directional control during takeoff on the snow and ice covered runway in gusting crosswind conditions.NTSB WPR15CA069Accident · No injuriesData collectionFinal reportCessna 172M · ObyanThe student pilot's loss of airplane control during the landing flare in gusting wind conditions.NTSB ERA15CA033Accident · No injuriesData collectionFinal reportCessna 172M · Apopka, FLThe student pilots improper landing flare which resulted in a hard landing and loss of aircraft control. Contributing to the accident was the flight instructor's delayed remedial actions.NTSB ERA14LA448Accident · No injuriesLimited investigationFinal reportCessna 172M · Leesburg, FLThe flight instructor’s delayed remedial action and his subsequent loss of directional control during landing on a wet runway for reasons that could not be determined because postaccident examination of the airplane revealed no anomalies.NTSB ERA14CA352Accident · No injuriesData collectionFinal reportCessna 172M · Chatham, MAThe pilot's failure to maintain directional control during takeoff, resulting in a runway excursion and collision with trees.NTSB WPR14CA155Accident · No injuriesData collectionFinal reportCessna 172M · Anacortes, WAThe pilot's improper application of brakes during the landing roll resulted in a runway excursion and nose over.NTSB ERA14CA169Accident · No injuriesData collectionFinal reportCessna 172M · Knoxville, TNThe student pilot's failure to maintain directional control during the takeoff roll, which resulted in a collision with an obstacle.NTSB WPR14CA122Accident · No injuriesData collectionFinal reportCessna 172M · Ramona, CAThe student pilot's inadequate flare and failure to maintain directional control during landing, which resulted in a runway excursion and collision with terrain.NTSB ANC14LA011Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethel, AKThe pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.NTSB ERA12CA481Accident · No injuriesData collectionFinal reportCessna 172M · Hammond, NYThe pilot’s failure to maintain directional control of the airplane while landing in gusting wind conditions.NTSB ERA12CA270Accident · No injuriesData collectionFinal reportCessna 172M · Pottstown, PAThe pilot’s inadequate recovery from a bounced landing, which resulted in a loss of control.NTSB ERA12CA211Accident · No injuriesData collectionFinal reportCessna 172M · Mayaquez, PRThe pilot did not maintain control of the airplane while landing in crosswind conditions.NTSB WPR12CA079Accident · No injuriesData collectionFinal reportCessna 172M · Richland, WAThe student pilot's improper landing flare and inadequate directional control during landing.NTSB ERA11CA273Accident · No injuriesData collectionFinal reportCessna 172M · Suchez, GAThe failure of the pilot to initiate a go-around and his excessive airspeed on the final landing approach.NTSB ERA11CA138Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's loss of directional control during the landing rollout, resulting in a runway excursion.NTSB CEN10CA158Accident · No injuriesData collectionFinal reportCessna 172M · Waupaca, WIThe student pilot's failure to maintain directional control while taking off in gusting winds.NTSB ANC10LA013Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethel, AKThe pilot's failure to maintain directional control of the airplane during takeoff.NTSB ANC09CA010Accident · No injuriesData collectionFinal reportCessna 172M · Girdwood, AKThe pilot's decision to attempt to take off on a snow-covered runway. Contributing to the accident was the snow-covered runway.NTSB ERA09CA010Accident · No injuriesData collectionFinal reportCessna 172 · Naples, METhe pilot's failure to maintain directional control of the airplane during takeoff. Contributing to the accident was the wet condition of the grass runway.