NTSB investigations: Cessna 172N
66 cases on aircraft the registry lists as Cessna 172N, 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 | 7 |
|---|---|
| 1983 | 6 |
| 1984 | 7 |
| 1985 | 3 |
| 1986 | 1 |
| 1987 | 2 |
| 1988 | 5 |
| 1989 | 4 |
| 1990 | 2 |
| 1991 | 3 |
| 1992 | 2 |
| 1993 | 5 |
| 1994 | 1 |
| 1995 | 3 |
| 1996 | 1 |
| 1997 | 1 |
| 1999 | 3 |
| 2000 | 2 |
| 2002 | 1 |
| 2003 | 4 |
| 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 ('2072434')
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 ('2072434')
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 NYC06CA196Accident · No injuriesData collectionFinal reportCessna 172N · Windsor, NHThe pilot's delay in aborting the takeoff, which resulted in an overrun and subsequent collision with trees. A factor in the accident was the tailwind.NTSB NYC05CA073Accident · No injuriesData collectionFinal reportCessna 172N · Wellington, OHThe pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.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 MIA04CA005Accident · Minor injuriesData collectionFinal reportCessna 172N · Everglades City, FLThe pilot's improper preflight planning/preparation which resulted in the airplane's gust lock being left installed, which resulted in the airplane not being able lift off during the takeoff roll, and damage to the airplane when it overran the runway and…NTSB CHI03LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · La Monte, MOThe pilot's misjudgment of speed and distance resulting in an overrun of the runway.NTSB SEA03LA084Accident · No injuriesLimited investigationFinal reportCessna 172 N · Center Island, WAThe pilot did not attain the proper touchdown point during landing. The pilot's diverted attention, deer near the runway, and trees were factors.NTSB MIA03LA098Accident · No injuriesLimited investigationFinal reportCessna 172N · Foxworth, MSThe failure of the pilot to perform a go-around, his failure to attain the proper touchdown point, and his delay in applying the normal brakes resulting in his inability to stop the airplane and subsequent on-ground collision with a fence.NTSB MIA02LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Pickens, SCThe pilot's improper preflight planning/preparation that resulted in the airplane's gust lock being left installed which resulted in a loss of control during the takeoff roll and damage to the airplane when it exited the departure end of the runway and…NTSB CHI00LA146Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Plainwell, MIthe pilot exceeded the proper touchdown point during the landing. Factors associated with the accident were the fence and the ditch which the airplane contacted.NTSB NYC00LA109Accident · No injuriesLimited investigationFinal reportCessna 172 · North Adams, MAThe pilot's failure to obtain the proper touchdown point. A factor was a tailwind.NTSB FTW00LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Pineville, LAThe student pilot's misjudgment of distance/speed during approach resulting in his failure to attain the proper touchdown point.NTSB MIA99LA259Accident · No injuriesLimited investigationFinal reportCessna 172N · Moontown, ALThe pilot's decision to land on a runway with a quartering tailwind, his failure to obtain the proper touchdown point on the runway, and his delay in aborting the takeoff phase of a touch and go landing, resulting in the aircraft overrunning the runway,…NTSB NYC99LA066Accident · No injuriesLimited investigationFinal reportCessna 172N · Berlin, NJThe pilot in command's failure to obtain the proper touch down point on the runway, and failure to perform a go-around. A factor relating to the accident was a sudden wind shift.NTSB LAX97LA199Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAthe student pilot's misunderstanding of the controller's clearance during an aborted touch-and-go landing.NTSB CHI96LA302Accident · No injuriesLimited investigationFinal reportCessna 172 · Greenwood, ILthe pilot's failure to obtain a proper touchdown point.NTSB FTW95LA386Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Kerrville, TXthe pilot's inadequate preflight preparation and his failure to use all the available runway. A factor was the dark night.NTSB LAX95LA266Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Carlsbad, CAThe pilot's poorly planned approach, misjudged distance/altitude, and failure to make a go-around. The pilot inadvertently becoming lost and disoriented was a factor in this accident.NTSB BFO95LA054Accident · No injuriesLimited investigationFinal reportCessna 172N · Head Waters, VAthe pilot's poor planning/decision making in the attempted departure. Contributing factors are the wet, recently mowed grass airstrip, and the embankment/downhill grade encountered during the aborted takeoff.NTSB CHI94LA171Accident · No injuriesLimited investigationFinal reportCessna 172N · Mackinac Island, MIExcessive airspeed and a failure to attain the proper touchdown point on the runway. Factors related to the accident were the wet runway and the fence which was contacted.NTSB LAX94LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAThe pilot's delayed decision to abort the takeoff and improper use of the airplane's throttle.NTSB SEA94LA033Accident · No injuriesLimited investigationFinal reportCessna C-172N · Idaho Falls, IDThe pilot's failure to attain the proper touchdown point. Factors include tailwind conditions and an airport perimeter fence.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB CHI93LA196Accident · No injuriesLimited investigationFinal reportCessna 172N · St. James, MIThe pilot landed too long on a wet runway.NTSB BFO93LA091Accident · No injuriesLimited investigationFinal reportCessna 172N · Petersburg, OHThe pilot's failure to attain the proper touchdown point while attempting to land on a wet grass strip, and his failure to perform a go around. The wet grass runway was a factor.NTSB ATL93LA005Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Apex, NCThe pilot's improper in-flight planning and his inadequate compensation for wind conditions, which resulted in the overrun of the runway. Factors were the tail wind conditions, and the downhill, grass runway.NTSB NYC92LA084Accident · No injuriesLimited investigationFinal reportCessna 172N · New Madison, OHThe pilot's failure to attain a proper touchdown point. Contributing to the accident was the pilot inadequately planned his approach and his failure to perform a go-around.NTSB LAX91LA404Accident · No injuriesLimited investigationFinal reportCessna 172 · Cottonwood, AZThe pilot-in-command's delay in raising the flaps and the subsequent inadvertent stall/mush.NTSB DEN91LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Watkins, COThe pilot selected the wrong runway and landed with a tailwind.NTSB CHI91LA166Accident · No injuriesLimited investigationFinal reportCessna 172N · Chicago, ILThe pilot in command (student)'s improper judgement of the proper touchdown point. A factor contributing was the pilot in command's delaying an aborted landing.NTSB SEA90LA134Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Yamhill, ORThe pilot's failure to retract the flaps during go-around.NTSB DEN90LA126Accident · No injuriesLimited investigationFinal reportCessna 172 · Boulder, COThe pilot's failure to touch down at the proper point, his misjudgment of the distance required for takeoff following the touch and go, and his delayed decision to abort the takeoff.NTSB ATL90LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridgeland, SCThe pilot misjudged the airspeed and failed to attain the proper touchdown point.NTSB NYC89LA214Accident · No injuriesLimited investigationFinal reportCessna 172N · Bayport, NYThe pilot's misjudging speed and distance resulting in his overshooting the landing and running off the end of the runway.NTSB LAX89LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Eureka, CAThe improper in-flight planning by the instructor pilot when he allowed the private pilot student to land long. Additionally, the instructor delayed remedial action until the runway overrun was inevitable.NTSB FTW89LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · Marietta, OKFailure of the pilot to select the proper runway, which resulted in a downwind landing and an overrun of the runway. The gusty tailwind, ditch, and railing (fence) were factors.NTSB SEA89LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Oregon City, ORThe pilot was landing his aircraft on a very wet 1,170 foot grass runway. The pilot was not able to stop the aircraft before it collided with a fence at the end of the runway. According to the manufacturers performance figures, under the given temperature and…NTSB MKC89LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · West Memphis, ARThe pilot said he was unable to activate the runway lights on the designated frequencies during a night personal flight. He attempted to land without the aid of the runway lights, and touched down on the FAR end of the runway subsequently running off the end…NTSB ANC88LA082Accident · No injuriesLimited investigationFinal reportCessna 172 · Healy, AKThe commercial pilot/flight instructor was attempting to land at a private turf airstrip when she reportedly encountered the outflow from a thunderstorm located about one mile away. She elected to continue with the landing and touched down with a greater than…NTSB SEA88LA096Accident · No injuriesLimited investigationFinal reportCessna 172N · Anacortes, WAAfter overflying the intended seaplane base landing area. The pilot, who had logged only 1 hour of fixed wing time in the previous 90 days, misjudged the necessary downwind leg length and landed with insufficient surface distance available to stop the…NTSB ATL88LA160Accident · No injuriesLimited investigationFinal reportCessna 172N · Gilbert, SCThe airplane overran rwy 23 during ldg and nosed over. The plt reported that he attempted to abort the ldg after initially landing long on the rwy. As the airplane began to climb however, he realized that it would not clear obstacles located past the end of…NTSB CHI87LA226Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Frankfort, ILThe student plt was on a flt with 2 pax aboard. He rprtd that drg a ngt lndg, the acft bounced & ballooned. He added pwr to fly the acft back down to the rwy, but it bounced & ballooned again. By this time, the acft was about halfway down the rwy.…NTSB MKC87LA073Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Halstead, KSThe PIC rptd lndg long on a 2600 ft sod rwy. During the lndg roll, the PIC rptd encountering a tailwind. The closest fss at wichita, 20 mi fm the accident arpt, rptd no significant wind chg during this period, the PIC, knowing that he had landed long and…NTSB ATL86LA101Accident · No injuriesLimited investigationFinal reportCessna 172N · Advance, NCWhile on final apch to rwy 27,plts vision restricted by sun glare. Plt indicated that he was high & fast and landed too long to allow go around. Overran runway, nose gear mired and acft nosed over.NTSB BFO86LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Annapolis, MDThe plt crossed mid-field, and entered a left down wind for rwy 30. He then checked wind direction, completed a base leg, and entered final apch. After reducing his airspeed, the acft 'floated' prior to touching down aprx 600 ft short of mid-fld. The plt…NTSB MKC85LA127Accident · No injuriesLimited investigationFinal reportCessna 172 · Curtis, NEThe plt stated he misread the windsock and made a downwind landing resulted. The acft overran the end of the grass rwy and nosed over when the nose gear contacted a plowed fld. The arpt operator reported the winds were from 180 degs at 18 KTS when the landing…NTSB MIA85LA154Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Myers, FLPlt stated that on takeoff ground run from a turf runway he felt severe vibration in the nose gear and lifted it off the ground. As he did he thought he felt a loss of engine power an aborted the takeoff. Before the aircraft could be stopped it overran the…NTSB ATL85LA003Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Gold Hill, NCThe plt was uable to raise UNICOM for wind advisories and was unable to find the wind sock to aid in rwy selection. He did see some smoke on the ground which indicated calm winds. During his flare the acft floated about halfway down the rwy, touched down and…NTSB CHI85LA008Accident · No injuriesLimited investigationFinal reportCessna 172N · Youngstown, OHAfter returning to the arpt, the plt entered the pattern for a x-wind landing. He made 3 go-arounds while attempting to land. On the 4th apch, the acft touched down, then became airborne again. The plt decided 'to much time had passed to make another…NTSB CHI84LA277Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lansing, ILThe acft ran off the end of the rwy into a ditch during landing. The plt said that his landing speed was 'well above normal touchdown speed.' He had made one approach before the accident and went around because he was 'landing long.' There were no reported…NTSB MIA84LA191Accident · No injuriesLimited investigationFinal reportCessna 172N · Miami, FLThe plt said he had 'cross channeled' his radios & was having communication problems. He decided to land at the opa-locka west arpt. The acft was landed downwind & after overrunning the end of the rwy, it collided with terrain & was damaged.