NTSB investigations: Cessna 172M
49 cases on aircraft the registry lists as Cessna 172M, where the first occurrence was “Overrun”. 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
| 1982 | 2 |
|---|---|
| 1983 | 6 |
| 1984 | 2 |
| 1985 | 1 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 2 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 6 |
| 1992 | 2 |
| 1993 | 5 |
| 1995 | 1 |
| 1997 | 2 |
| 1998 | 3 |
| 1999 | 4 |
| 2000 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 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.\"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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340))
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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340))
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 ATL06CA065Accident · No injuriesData collectionFinal reportCessna 172 M · Griffin, GAThe pilot's failure to achieve the proper touchdown point, which resulted in an overrun of the runway, collision with an embankment, and subsequent nose over.NTSB ANC05CA147Accident · No injuriesData collectionFinal reportCessna 172 · Anchorage, AKThe pilot's misjudgment of distance/speed during landing, which resulted in an overrun, a loss of directional control, and a nose over during the landing roll.NTSB SEA04LA096Accident · No injuriesLimited investigationFinal reportCessna 172M · Vernonia, ORThe instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway.NTSB ATL03LA067Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Savannah, GAThe pilot misjudged the landing distance, landed with excessive airspeed, did not attempt a go-around resulting in the airplane going off the overrun, and colliding with trees.NTSB CHI00LA259Accident · No injuriesLimited investigationFinal reportCessna 172M · Harbor Springs, MIthe pilot's long touchdown, and inadequate braking to stop on the runway. Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.NTSB SEA00LA010Accident · No injuriesLimited investigationFinal reportCessna 172M · Mackay, IDThe pilot's failure to land at the proper touchdown point. Factors include a wind gust, a grass runway, and a drop-off into rough terrain at the end of the runway.NTSB NYC99LA174Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Hamburg, NYThe pilot's improper recovery from a bounced landing. A related factor was the lack of experience in make and model.NTSB NYC99LA094Accident · No injuriesLimited investigationFinal reportCessna 172M · Lumberton, NJThe pilot's misjudgment of altitude and distance which resulted in a runway overrun.NTSB CHI99LA118Accident · No injuriesLimited investigationFinal reportCessna 172M · New Hudson, MIThe pilot's misjudgment of speed and distance and his failure to execute a go-around. A related factor was the crosswind.NTSB NYC99LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Cumberland, MDThe pilot's decision to land, instead of performing a go-around.NTSB NYC98LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · Westminster, MDthe pilot's misjudgment of distance and speed during the approach/landing, and his delay in initiating a go-around. The quartering tailwind was a related factor.NTSB IAD98LA020Accident · No injuriesLimited investigationFinal reportCessna 172M · Blue Bell, PAThe pilot's failure to attain the proper touchdown point, and his failure to make a go-around, while there was sufficient runway remaining.NTSB ATL97LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Athens, TNthe pilot's failure to initiate a go-around. The pilot's misjudged approach was a factor.NTSB ATL97LA076Accident · No injuriesLimited investigationFinal reportCessna 172M · Perry, GAthe pilot misjudged his distance/airspeed during the approach to land, and touched down long on the runway.NTSB FTW95LA110Accident · No injuriesLimited investigationFinal reportCessna 172M · Boulder, COThe pilot's premature rotation.NTSB CHI93LA332Accident · No injuriesLimited investigationFinal reportCessna 172M · Lincoln, NEthe pilot's failure to attain the proper touchdown point.NTSB MIA93LA119Accident · No injuriesLimited investigationFinal reportCessna 172M · Ochopee, FLThe pilot's poor judgement in attempting the takeoff from the parking ramp when a 12,000-FT runway was available.NTSB ANC93LA052Accident · No injuriesLimited investigationFinal reportCessna 172M · Kasigluk, AKThe pilot's improper planning/decision and delay in aborting the takeoff. Factors related to the accident were: loose gravel on the surface of the runway and the snowbank (berm) on the overrun (stopway).NTSB FTW93LA104Accident · No injuriesLimited investigationFinal reportCessna 172M · Overbrook, OKThe pilot's failure to assure that the elevator trim was properly set for takeoff and his delay in aborting the takeoffNTSB NYC93LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Valley Point, WVThe failure of the pilot to make a rejected landing when the airplane failed to decelerate properly. A factor related to the accident was the failure of the pilot to close the throttle upon touchdown.NTSB BFO92LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Amelia, VAThe pilot's misjudgement of distance and altitude that resulted in an landing overrun and collision with an embankment. Contributing was failure to initiate a go around and inadequate supervision.NTSB CHI92LA121Accident · No injuriesLimited investigationFinal reportCessna 172M · Osage Beach, MOThe pilot-in-command's failure to use all th eavailable runway and his misjudgment of the proper touchdown point during landing.NTSB DEN91LA087Accident · No injuriesLimited investigationFinal reportCessna 172M · Keenesburg, COThe pilot's misjudging the approach, and disregard of wind conditions. Factors were: a tailwind condition and the pilot's anxiety.NTSB SEA91LA141Accident · No injuriesLimited investigationFinal reportCessna 172-M · Salem, ORThe pilot's poor in-flight decision and his failure to select a proper touchdown point. Factors include a wet runway, soft terrain and high vegetation.NTSB ATL91LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Knighdale, NCFailure of the pilot to attain the proper touch down point on the runway and/or perform a go-around.NTSB CHI91LA169Accident · No injuriesLimited investigationFinal reportCessna 172M · Cadillac, MIThe pilot-in-command's maintaining excessive airspeed through the landing touchdown which resulted in overrunning the runway.NTSB NYC91LA119Accident · No injuriesLimited investigationFinal reportCessna 172M · Bloomvale, NYThe pilot's delay in aborting the takeoff.NTSB NYC91LA091Accident · No injuriesLimited investigationFinal reportCessna 172M · Leroy, NYThe hard landing made by the pilot. Factors relating to the accident were the decision of the pilot to land on the runway despite the runway lighting system being partially inoperative, and the lack of experience of the pilot at night.NTSB LAX90LA334Accident · No injuriesLimited investigationFinal reportCessna 172M · Orovada, NVThe pilot's failure to initiate a go-around. His lack of recent experience in type of operation, (landings), and the inadvertent ground loop were factors in the accident.NTSB LAX90LA237Accident · No injuriesLimited investigationFinal reportCessna 172M · El Cajon, CAThe pilot-in-command's failure to abort the landing after touchdown past the touchdown zone.NTSB LAX90LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Redding, CAThe pilot's decision not to use full flaps which resulted in a long landing on a wet runway.NTSB CHI89LA121Accident · No injuriesLimited investigationFinal reportCessna C172M · Wadsworth, OHPilot's poor planning/decision making during the approach and landing phase of flight, which resulted in a long landing and runway overrun.NTSB NYC89LA117Accident · No injuriesLimited investigationFinal reportCessna 172M · Palmyra, PAThe pilot misjudged the airspeed and distance during the landing.NTSB CHI88LA216Accident · No injuriesLimited investigationFinal reportCessna 172M · Kelley'S Island, OHShortly after crossing the runway threshold on final approach, the pilot experienced a wind shift and elected to attempt a go-around. The pilot discontinued the attempted go-around when he judged that he would be unable to clear trees located at the departure…NTSB BFO88LA038Accident · No injuriesLimited investigationFinal reportCessna 172M · Fayetteville, WVThe pilot landed long and with excessive airspeed, which resulted in an overrun of the runway. Inadequate inflight planning is a contributing factor.NTSB ATL87LA080Accident · No injuriesLimited investigationFinal reportCessna 172M · Lexington, NCThe plt reported that he had transitioned to a visual approach, following a simulated radar approach to the rwy using vectors and descent info supplied by an instrument-rated safety plt in the rt seat. The safety plt was the plt's former instructor. The plt…NTSB FTW86LA162Accident · No injuriesLimited investigationFinal reportCessna 172M · Mineola, TXThe inboard brake pads were worn to such a degree that metal to metal contact was occurring. This greatly reduced the aircraft's braking ability. After landing the pilot was unable to stop the aircraft upon the 3225 foot runway. The aircraft ran through a…NTSB NYC86LA151Accident · No injuriesLimited investigationFinal reportCessna 172 · Arcade, NYThe pilot landed on a wet runway that sloped slightly downhill. He stated that the aircraft touched down about 800 feet down the runway in winds that were from the west at 1 to 3 mph. The brakes were ineffective on the wet turf. Subsequently, the aircraft…NTSB ATL85LA211Accident · No injuriesLimited investigationFinal reportCessna 172 M · Statesville, NCWhile en route, the plt encountered reduced visibility & had difficulty finding the airstrip. His 1st apch to land was high & he made a go-around. The plt landed on his 2nd attempt, but was unable to stop on the wet grass rwy. He delayed attempting a…NTSB SEA85LA029Accident · No injuriesLimited investigationFinal reportCessna 172M · Sultan, WAAn overrun occurred on the 2,000 foot airstrip due to excess approach and landing speed. A light coating of snow was present on the grass runway and the pilot neglected to raise the flaps adding to a longer landing roll and making braking less effective. A 5…NTSB MKC84LA204Accident · No injuriesLimited investigationFinal reportCessna 172M · Colt, ARThe pilot stated that he made his final approach to the rwy at 70 mph and the aircraft floated when he flared for touchdown. He continued to state that after acft touched down, insufficient runway remained to stop before overrunning the runway and impacted a…NTSB MKC84LA007Accident · No injuriesLimited investigationFinal reportCessna 172M · Blairstown, MOThe plt reported that after he started to takeoff, the acft had rolled aprx 1500 ft when he felt the airspeed was not sufficient, so he aborted. He was unable to stop on the remaining rwy. Before stopping, the acft went thru a shallow ravine. Subsequently,…NTSB NYC83LA250Accident · No injuriesLimited investigationFinal reportCessna C172M · Dover, DEThe acft ran off the end of the rwy, groundlooped, and collided with a tree during an effort to avoid a blast fence. The landing, made at night with touchdown occurring too FAR down the rwy. An approach had already been abandoned due to excessive airspeed,…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 CHI83LA396Accident · No injuriesLimited investigationFinal reportCessna 172 · Princeton, ILThe turf rwy was wet from recent rains. The plt stated that during takeoff, the acft had accelerated to near the rotation speed when it was slowed by a soft spot in the rwy near mid field. At the same point, an upslope portion of the rwy was encountered & the…NTSB NYC83LA145Accident · No injuriesLimited investigationFinal reportCessna 172M · Block Island, RIThe plt reported that during a landing, the brakes failed & he was unable to stop on the rwy. The acft ran off the end & came to rest in bushes with substantial damage. According to the plt, the outboard pressure plate & lining had separated from each brake.…NTSB MIA83LA142Accident · No injuriesLimited investigationFinal reportCessna 172M · Arcadia, FLThe plt reported that on his approach to land, his speed was higher than normal & the acft touched down well past the normal touchdown point. He was unable to stop on the remaining rwy. The acft went off the end of the rwy & collided with a ditch. The plt…NTSB CHI82DA330Accident · No injuriesFinal reportCessna 172 · Winchester, ILThe pilot elected to land on a 1600 ft grass strip with a crosswind of about 5 KTS. He reported that he crossed the fence at about 60 KTS with 15 deg of flaps, then touched down about 400 ft down the runway. During the landing roll, he saw he would be unable…NTSB NYC82DA154Accident · No injuriesFinal reportCessna 172M · Savage, PAAfter a cross country flight, the aircraft approached a 1900 foot landing strip for landing. After a fly-over to check the area, an approach to land ended in a go-around. On the second approach, the pilot was high and fast. He slipped the aircraft to lose…