NTSB investigations, MO
37 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 3 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1987 | 6 |
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1993 | 3 |
| 1995 | 1 |
| 1997 | 1 |
| 1998 | 2 |
| 1999 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 4 |
| 2004 | 1 |
| 2005 | 2 |
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\" = 'MO' 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" = 'MO' 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 CHI05FA059Accident · No injuriesField investigationFinal reportLearjet 35A · Kansas City, MOThe contaminated runway conditions during landing. Contributing factors were the operation of the airplane without thrust reversers, flight to the planned alternate airport not performed by the flightcrew, and the insufficient runway information. Additional…NTSB CHI05CA054Accident · No injuriesData collectionFinal reportCessna 152 · Stockton, MOthe pilot's failure to attain the proper touchdown point, which resulted in an overrun. Contributing factors were the tailwind and dusk light conditions.NTSB CHI04CA239Accident · No injuriesData collectionFinal reportCessna 150H · Golden, MOThe pilot's misjudgment of speed and distance. A factor was the tires positioned at the end of the runway.NTSB CHI03LA316Accident · Minor injuriesLimited investigationFinal reportCessna 182P · Versailles, MOThe pilot touched down with excessive airspeed. Factors associated with the accident were the trees, the wet runway, the wet grass that the airplane traveled onto, and the ditch which the airplane contacted.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 CHI03LA158Accident · No injuriesLimited investigationFinal reportCessna 152 · Owensville, MOThe pilots delayed attempt to perform an aborted takeoff and subsequent overrun. Contributing factors to the accident were the fence and the ditch.NTSB CHI03LA123Accident · No injuriesLimited investigationFinal reportBeech 95-C55 · Point Lookout, MOFailure of the pilot to maintain control of the aircraft. Contributing factors were the sudden windshift to a tailwind, the wet runway surface, the lack of available runway overrun area and the rocky, descending embankment.NTSB CHI02LA123Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Viburnum, MOThe pilot's improper short field takeoff planning and procedure. The takeoff weight above the maximum gross weight and the hill were contributing factors.NTSB CHI02LA096Accident · No injuriesLimited investigationFinal reportCessna 170A · Gainesville, MOThe pilot's misjudgment of distance/altitude and his failure to perform a go-around.NTSB CHI01LA299Accident · No injuriesLimited investigationFinal reportBeech 58P · Theodosia, MODiminished braking action due to standing water on the runway. A factor associated with the accident was the ditch which the airplane contacted.NTSB CHI01LA031Accident · No injuriesLimited investigationFinal reportCessna 172 · Carrollton, MOthe misjudged touchdown point by the pilot. Factors were the runway lights not on, the dark night, and the plowed field.NTSB CHI00LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Fulton, MOthe pilot's poor inflight planning which resulted in exceeded the proper touchdown point on the runway. A factor associated with the accident was the ditch that the airplane contacted.NTSB CHI99LA306Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Salem, MOThe pilot in command misjudging the touchdown point.NTSB CHI99LA018Accident · No injuriesLimited investigationFinal reportCessna 172 · Creve Coeur, MOthe pilot misjudged his altitude and airspeed during landing. A related factor was the dark night conditions.NTSB CHI98LA191Accident · Minor injuriesLimited investigationFinal reportBeech 23 · Excelsior Spr, MOthe inadequate preflight planning by the pilot in command and exceeding the maximum gross weight for the aircraft. A factor was the berm.NTSB CHI97LA049Accident · No injuriesLimited investigationFinal reportGates Learjet LR35 · Kansas City, MOthe flightcrew's excessive airspeed and failure to attain a proper touchdown point on the runway. Factors were: the fog, wet runway, tailwind and improper procedures by the flight crew.NTSB CHI95LA300Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Osage Beach, MOthe student pilot's misjudgement of distance and speed during the landing and failure to attain the proper touchdown point.NTSB CHI94LA033Accident · Minor injuriesLimited investigationFinal reportCessna 172I · Moberly, MOthe failure of the pilot-in-command to use all of the available runway.NTSB CHI93LA330Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · Point Lookout, MOThe pilot's failure to attain the proper touchdown Point.NTSB CHI93LA261Accident · No injuriesLimited investigationFinal reportBeech F33A · Kahoka, MOThe pilot's premature liftoff. The soft runway condition was a factor.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 MKC89LA125Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Bolivar, MOImproper planning/decision by the pilot and his delay in aborting the takeoff. Contributing factors were the tall grass, inadequate runway maintenance, and trees.NTSB MKC88LA063Accident · No injuriesLimited investigationFinal reportBeech C23 · Sullivan, MOWhen the PIC arrived at his destination, during a personal cross country flight, he circled the unfamiliar arpt three times, observing trees on both ends, and a crosswind of about 60 degrees to the active runway. After landing, and during the ldg roll out, he…NTSB MKC88LA009Accident · No injuriesLimited investigationFinal reportGrumman American AA5B · Branson, MODuring a lndg on a 3600 ft strip, the acft touched down long. The acft ran off the departure end of the rwy and collided with the terrain causing substantial damage to the acft. Witnesses said they could not find any skid marks along the path taken by the…NTSB MKC87LA184Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Ozark, MODuring a ldg, the acft touched down long, ran off the end of the airstrip and struck a fence and then a ditch. The rwy was 2100 feet long, downsloping, and the grass surface was wet.NTSB MKC87LA146Accident · No injuriesLimited investigationFinal reportCessna 152 · Columbia, MOThe instructor and the student were making a landing on a short grass runway. The instructor stated they landed fast and were not able to stop. He considered a go-around but decided sufficient runway did not remain to perform the go-around. The airplane…NTSB MKC87LA171Accident · No injuriesLimited investigationFinal reportCessna TU206G · West Plains, MODuring ldg phase of operation, PIC was unable to stop the acft before striking a fence on the overrun. Plt stated a rain shower had just passed through which left the dirt surface slick and muddy. He stated that he was unable to obtain effective braking due…NTSB MKC87LA065Accident · No injuriesLimited investigationFinal reportBeech BE-58 · Houston, MOThe airplane was on an IFR flight plan and five miles from the airport, the airplane broke out of the clouds and proceeded VFR to the airport. It was a dark night and light rain was falling. The pilot stated he flew over the airport twice looking for a wind…NTSB MKC87LA052Accident · No injuriesLimited investigationFinal reportBeech B-35 · Butler, MOThe PIC flew a traffic pattern that placed him landing long to the rwy at Butler, MO. The PIC perceived an eng failure prior to attempting a go-around and activated the fuel boost pump and advanced the throttle. The PIC rptd the eng faultered and quit. The…NTSB MKC86LA118Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Bolivar, MOThe pilot stated he thought he could get airborne from the turf field although it was wet, soft, and muddy. After rolling some distance, he decided he would have to fly through powerlines or trees so he aborted. The airplane ran past the end of the runway,…NTSB MKC86LA039Accident · No injuriesLimited investigationFinal reportCessna 182RG · Wentzville, MOThe pilot stated that he winds were calm when he made the tou long, on the runway, attempted a go around and ran off the end of the runway into a field when the airplanefailed to get airborne.NTSB MKC85LA101Accident · No injuriesLimited investigationFinal reportPiper PA-46 · Osage Beach, MOThe plt landed the acft mid-field on the 3205 ft rwy, the acft landing speed was higher than normal and a decision was made to continue the landing instead of going around for another attempt. The plt applied brakes & the acft skidded off the rwy. The plt…NTSB MKC84LA248Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Branson, MOExcessive airspeed caused the acft to float about halfway down the rwy prior to touchdown. A go-aground was initiated with the addition of power but the plt then elected to attempt to stop due to low airspeed and minimal rwy remaining. The plt then applied…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 MKC83LA145Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Point Lookout, MODuring arrival, the plt contacted the arpt UNICOM & was advised that the wind was variable 190 to 210 deg at 10, gusting 15 KTS. The 1st apch was made at 95 mph with full flaps. The plt said wind shear, near the end of the rwy, was encounter, so a go-around…NTSB MKC83LA143Accident · No injuriesLimited investigationFinal reportPiper PA-28-236 · Cedarcreek, MODuring arrival, the plt flew over the strip, then circled to land. As he was flaring to land, he saw 2 deer on the rwy. He initiated a go-around, but decided he was too slow & that there was not enough rwy left. He reduced the power & touched down, but was…NTSB MKC82DA176Accident · No injuriesFinal reportPiper PA-28-161 · Point Lookout, MODuring arrival, the UNICOM had recommended that runway 11 be used. However, the student pilot landed on runway 29 with a quartering tail wind. According to witnesses, the aircraft touched down about, 2800 ft beyond the approach end of the runway, then it slid…