NTSB investigations, SC
21 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 3 |
|---|---|
| 1983 | 1 |
| 1984 | 3 |
| 1986 | 3 |
| 1988 | 1 |
| 1989 | 2 |
| 1993 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 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.\"eventStateOrRegion\" = 'SC' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE 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."eventStateOrRegion" = 'SC' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 ATL05CA068Accident · No injuriesData collectionFinal reportCessna 310J · Union City, SCThe pilot's delay in aborting the landing. A contributing factor was the pilot's failure to maintain directional control.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 MIA01LA156Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Bennettsville, SCThe pilot failure to obtain the proper touchdown point on the runway resulting in the airplane landing long, over running the runway, colliding with a telephone pole separating the right wing, and coming to rest in the parking lot of a restaurant.NTSB MIA01LA022Accident · No injuriesLimited investigationFinal reportHorne Bowers Flybaby · Greer, SCA runway overrun as a result of the pilot's failure to maintain proper approach speed and landing touch down point.NTSB MIA98LA167Accident · No injuriesLimited investigationFinal reportNorth American T-28B · Spartanburg, SCThe pilot's misjudgment of speed and distance, and his delay in the use of brakes. Contributing to the accident was a thunderstorm, a wet runway, the pilot's self-induced pressure, and his inadequate inflight planning/decision.NTSB MIA97LA088Accident · Minor injuriesLimited investigationFinal reportLearjet LR35 · Greenville, SCThe pilot-in-command's failure to achieve the proper touchdown point on a known wet runway, resulting in a subsequent overrun and on ground collision with a ditch.NTSB ATL93LA088Accident · Serious injuriesLimited investigationFinal reportExtra 300 · Ridge Springs, SCThe pilot's failure to determine the landing distance required for a landing on a wet sod runway, which resulted in the overrun of the landing area and the collision with a treeNTSB ATL90LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridgeland, SCThe pilot misjudged the airspeed and failed to attain the proper touchdown point.NTSB ATL89LA117Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Timmonsville, SCThe pilot's failure to remain aware of the local wind conditions. Additionally, he executed the approach and landing with excessive speed, combined with a tailwind, which resulted in the runway overrun.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 ATL86LA172Accident · No injuriesLimited investigationFinal reportBeech BE-58 · Dillon, SCDuring landing roll, the plt reported, the rwy surface was wet and he was unable to stop the acft before departing the paved surface. According to published landing procedures, the plt would have needed aprx 1439 ft of paved surface for the landing roll. The…NTSB ATL86LA152Accident · No injuriesLimited investigationFinal reportForney F-1 · Abbeville, SCThe student plt reported that the acft's brake system was inoperative during ldg rollout. The acft ran off the end of the rwy end into a trash pile and collided with pine logs.NTSB ATL86IA093Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-9-31 · Charleston, SCThe acft landed on rwy 15 at 2357 EST. The rwy was wet from heavy rain & thunderstorms. Braking was ineffective and the acft failed to stop. The capt steered rt into the mud to the rt side of the overrun. Post accident review of the flt data recorder showed…NTSB ATL84LA279Accident · No injuriesLimited investigationFinal reportBeech 58 · Laurens, SCThe acft ran off the end of the rwy during landing. The plt reported that he started using brakes to stop the acft but it veered to the right. Examination by maintenance revealed that the left brake disc, p/n 164-06100, had failed at the mount flange.NTSB ATL84LA206Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Summerville, SCThe acft touched down 1500 ft past the approach end of the 4000 ft wet sod rwy. 10 degrees of flaps were used. Brakes were applied but at 3000 ft down the rwy the plt realized he would be unable to stop the acft before it collided with a deep ditch at the end…NTSB ATL84LA122Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Newberry, SCThe plt had executed a go-around from an approach to rwy 4 due to a crosswind & gusty wind conditions. While on downwindhe observed that the wind was favoring rwy 10. He overshot the approach end of rwy 10 & executed another go-around. Upon observing that he…NTSB ATL83LA336Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Ridgeland, SCThe acft overran the rwy and collided with a ditch during landing. The weather was VMC with the winds light and variablethe pilot said he found himself high as he crossed the rwy threshold. The acft reportedly floated before touchdown. The pilot used maximum…NTSB ATL82DA262Accident · No injuriesFinal reportGrumman AA5B · Darlington, SCWind shifted to tailwind as pilot was landing. He considered a go-around because of speed but thought he could stop. As he went off the end the wing collided with a tree.NTSB ATL82DA056Accident · No injuriesFinal reportPiper PA-28-161 · Ridgeland, SCAfter touching down on the first 1/3RD of the 3100 foot runway the pilot stated that he lost his brakes. The aircraft went off the departure end of the runway down a 25 foot embankment and turned over. Examination of the wheel brake system including pushing…NTSB ATL82DLG09Accident · No injuriesFinal reportCessna 152 · Grantiteville, SCThe pilot was unable to find the airport at his intended destination. He saw another airport and elected to land. A no-flap approach was made to rwy 24 with a north wind. The aircraft touched down about 500 feet from the departure end and then became airborne…