NTSB investigations: Cessna 172P
46 cases on aircraft the registry lists as Cessna 172P, 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 | 8 |
| 1984 | 2 |
| 1985 | 2 |
| 1986 | 2 |
| 1987 | 2 |
| 1988 | 1 |
| 1989 | 2 |
| 1990 | 2 |
| 1991 | 2 |
| 1992 | 6 |
| 1993 | 2 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 2 |
| 2002 | 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 ('2072436')
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 ('2072436')
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 ATL06CA123Accident · No injuriesData collectionFinal reportCessna 172P · Chester, SCThe CFI's failure to initiate a go-around when he noticed the flight was high and fast during the approach resulting in the flight landing long, overrunning the runway, and colliding with trees. Factors in the accident were a tail wind and a wet runway.NTSB MIA06CA032Accident · No injuriesData collectionFinal reportCessna 172P · Hialeah, FLThe failure of the CFI to perform a go-around following a long landing resulting in overrun, on ground encounter with soft terrain, and subsequent nose over.NTSB SEA04LA081Accident · No injuriesLimited investigationFinal reportCessna 172P · Battle Ground, WAThe student pilot's misjudgment of distance and his failure to do a go-around. Also causal was the instructor's inadequate supervision of the flight. Factors include gusty crosswinds, the dual student's failure to adequately compensate for those winds, a wet…NTSB CHI02LA280Accident · No injuriesLimited investigationFinal reportCessna 172P · Sturtevant, WIThe proper touchdown point not attained and the approach speed not obtained/maintained by the pilot.NTSB SEA01LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Waldron Island, WAThe pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.NTSB LAX01LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Half Moon Bay, CAA local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.NTSB NYC99LA137Accident · No injuriesLimited investigationFinal reportCessna 172 · Ravenna, OHThe pilot-in-command's failure to maintain aircraft control during landing.NTSB LAX99LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Death Valley, CAThe pilot's use of an excessive approach reference speed and his misjudged distance/speed relationship to the runway, which resulted in a landing overrun. The pilot's failure to execute a timely go-around was also causal.NTSB CHI98LA254Accident · No injuriesLimited investigationFinal reportCessna 172P · Abilene, KSThe student pilot's failure to plan his approach so as to be able to stop the airplane on the runway, and the instructor pilot's delay in taking control of the airplane, so as to correct the student's mistake. A factor contributing to this accident was the…NTSB CHI97LA189Accident · No injuriesLimited investigationFinal reportCessna 172P · Fowlerville, MIfailure of the pilot to either attain proper touchdown point for landing or go around while he had sufficient airspeed and runway remaining.NTSB FTW96LA300Accident · No injuriesLimited investigationFinal reportCessna 172P · Owasso, OKInadequate maintenance by maintenance personnel resulting in inoperative brake system during an aborted takeoff. A factor was the downhill runway condition.NTSB SEA96LA056Accident · No injuriesLimited investigationFinal reportCessna 172P · Cashmere, WAthe pilot's selection of the wrong runway for landing, by not observing a procedure to land uphill during calm wind conditions, and his subsequent failure to retract the flaps during landing roll, as recommended by the airplane's short-field landing…NTSB ATL95LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Brownsville, TNThe pilot's improper in-flight decision to land on the wet, sod runway, and his failure to use all of the available runway for landing.NTSB ANC93LA142Accident · No injuriesLimited investigationFinal reportCessna 172 · Black Rapids, AKThe pilot's improper in-flight planning/decision, and his delay in taking remedial action. Factor was the rough, uneven terrain.NTSB ATL93LA129Accident · No injuriesLimited investigationFinal reportCessna 172 · Summerdale, ALThe pilot's failure to attain the proper touchdown point.NTSB FTW93LA060Accident · No injuriesLimited investigationFinal reportCessna 172P · Little Rock, ARThe certified flight instructor's failure to attain the proper touchdown point.NTSB NYC93LA051Accident · No injuriesLimited investigationFinal reportCessna 172 · Andover, NJThe pilot's failure to abort the landing which resulted in a overrun of the runway. Contributing was the pilot's misjudgement of distance and an improper touchdown point.NTSB CHI93LA003Accident · No injuriesLimited investigationFinal reportCessna 172P · Kokomo, INThe pilot's delayed remedial action.NTSB MIA92LA157Accident · No injuriesLimited investigationFinal reportCessna 172P · Valkaria, FLExcessive airspeed on final approach by the pilot in command resulting in failure to attain the proper touchdown point and running off the runway colliding with a tree.NTSB CHI92LA172Accident · No injuriesLimited investigationFinal reportCessna 172 · Wheeling, ILThe pilot's improper approach to landing. Related factors are the thunderstorm and the excessive airspeed.NTSB BFO92LA066Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Caldwell, NJThe pilot's improper IFR operation. Contributing was the pilot's lack of recent instrument flight time.NTSB NYC91LA210Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sandusky, OHThe pilot initiated an emergency landing when the engine RPM went to zero due to a broken tachometer cable. He did not attain the proper touchdown point and overran the end of the runway.NTSB CHI91LA139Accident · No injuriesLimited investigationFinal reportCessna 172 · Detroit, MIThe proper touchdown point was not attained and the pilot failed to perform a go around. A factor related to the accident was the tailwind condition in which the pilot was attempting to land.NTSB LAX90LA287Accident · No injuriesLimited investigationFinal reportCessna 172P · Coalinga, CAThe failure of the student pilot to accurately interpret the wind sock, and his inadvertent attempt to perform a downwind landing.NTSB CHI90LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Newark, ILImproper planning/decision by the pilot. The wet condition of the grass runway was a related factor.NTSB SEA89LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Alderwood Manor, WAImproper planning/decision by the pilot. The tailwind and high obstructions were related factors.NTSB CHI89LA081Accident · No injuriesLimited investigationFinal reportCessna 172D · Ottawa, ILStudent pilot's continuing an approach to landing beyond the point where she could bring the aircraft to a controlled stop on the remaining runway surface.NTSB NYC88LA223Accident · No injuriesLimited investigationFinal reportCessna 172P · Freeport, PAThe plt said that he had landed on the 2268 ft long, sod strip on several previous occasions. He said there was a right crosswind at about 6 KTS. The acft was too high and go-arounds were made following the first two approaches. On the third approach, the…NTSB ATL88LA062Accident · No injuriesLimited investigationFinal reportCessna 172P · Columbus, OHAt 1343 EST, the student plt contacted apch ctl & asked for lndg info. He was adzd to continue VFR for rwy 31. When he contacted the tower at 1347, the wind was fm 200 deg at 13 KTS. Tower psnl gave him the choice of rwy 31 or 28L; he elected to lnd on rwy…NTSB ATL87LA176Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Marion, NCThe acft overran the rwy end while the student plt was attempting a no-flap ldg. The acft impacted a berm at the end of the rwy and subsequently came to rest in a creek. The student plt reported that the acft had initially touched down about mid-field on the…NTSB MIA86LA254Accident · No injuriesLimited investigationFinal reportCessna 172P · Live Oak, FLThe student plt stated that after he landed on a wet rwy, he was unable to stop & the acft continued off the end. Before stopping, the acft collided with a fence. According to the operator, the student had landed well beyond the normal touchdown area of the…NTSB DEN86LA218Accident · No injuriesLimited investigationFinal reportCessna 172P · Albuquerque, NMAccording to the instructor (CFI), the student was making a practice landing when a sudden windshift occurred. He rprtd that when they were on the downwind for their 5th landing, the wind was from the wsw, but just before the landing, it changed to a…NTSB MKC85LA148Accident · No injuriesLimited investigationFinal reportCessna 172B · Valley Center, KSThe pilot had been flying with his young son as passenger during daylight hours. He went solo to get current at night. After two full stop landings, he thought the yoke felt heavy for the trim setting he usually used but he started a takeoff anyway. Halfway…NTSB LAX85LA292Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Glendale, AZWhen the plt realized he was low during final apch to a landing, he erroneously decided not to use full flaps instead of adding power, vref was high and the landing was 3/4 of the way down the 2400 ft rwy. Believing he had sufficient room to takeoff again,…NTSB NYC84LA296Accident · No injuriesLimited investigationFinal reportCessna 172P · Manville, NJAcft swerved on rwy before rotation and climbed aprx 10 feet before settling back on the rwy. Plt aborted the takeoff but was unable to stop before end of rwy.NTSB LAX84LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Pacoima, CADuring the overflight of the uncontrolled field, both plts noticed that the wind tee indicated rwy 12 as the landing direction. During landing, the acft floated & touched down about 2/3 down the rwy. The acft struck a fence & trees at the end of the rwy.…NTSB LAX83LA457Accident · No injuriesLimited investigationFinal reportCessna 172P · Glendale, AZReportedly, the plt landed long. He then applied braking action & 1 wheel locked. At that point, the acft was still going too fast to stop on the remaining rwy & there was insufficient rwy to go around. The plt steered the acft off the end of the rwy & it…NTSB LAX83LA418Accident · No injuriesLimited investigationFinal reportCessna 172P · Glendale, AZThe student & his instructor plt had made 2 takeoffs & landings, then the instructor deplaned & the student prepared to takeoff on a solo flt. According to the student, he made the pretakeoff checks, which included setting the trim. As the acft accelerated…NTSB FTW83LA397Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Worth, TXThe acft ran off the end of the rwy during landing and collided with a fence. It was reported that the solo student plt was high and fast during his approach to the 2500 ft strip for landing. The touchdown was long and led to the overrun. The wind was calm.…NTSB NYC83LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Westville, NYDuring arrival, the plt landed in light rain on a wet sod rwy with light & variable wind conditions. He reported that he touched down on the 1st third of the rwy, but witnesses said that the acft landed past the midfield point. Subsequently, the plt was…NTSB NYC83LA205Accident · No injuriesLimited investigationFinal reportCessna 172 · Atlantic City, NJThe acft landed long and fast, ran off the end of the rwy & collided with a fence.NTSB ANC83LA115Accident · No injuriesLimited investigationFinal reportCessna 172P · Mckinley Park, AKThe plt stated that he was unable to locate the windsock. While on final for rwy 16 'things' did not feel right, but he continued into a long, fast tailwind landing. As he neared the end of the rwy he deliberately groundlooped the acft to avoid going over a…NTSB CHI83LA217Accident · No injuriesLimited investigationFinal reportCessna 172 · Mchenry, ILThe acft went off the departure end of runway 09 during landing and nosed over. The weather as reported by the operator,was scattered clouds, more than 5 miles visibility and winds calm. Runway 09 had been in use all day. The pilot stated that his approach…NTSB SEA83LA075Accident · No injuriesLimited investigationFinal reportCessna 172 PII · Snohomish, WAThe plt stated he misjudged the approach to land and landed on the last 1/3 of the runway. Brakes were applied during landing roll but the acft rolled off the end of the runway, struck a ditch with the nosewheel and came to rest inverted.NTSB SEA82DA062Accident · No injuriesFinal reportCessna 172N · Lisabuella, WAThe pilot landed on a freshly mowed, grass runway. He reported that he had a left crosswind at 10 gusting 15 knots. The aircraft touched down at about 1/3 of the way down the runway. About 450 ft from the departure end, the brakes were applied. However, the…NTSB SEA82DA023Accident · No injuriesFinal reportCessna 172P · Sinclair Island, WAThe airport was a privately owned strip approximately 1200 ft in length. About the last 25 percent of runway 33 was angled approximately 30 degrees to the right. Tth runway was considered unidirectional with landings normally made to the north/northwest and…