NTSB investigations, WI
34 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 2 |
| 1984 | 3 |
| 1985 | 3 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 3 |
| 1990 | 1 |
| 1991 | 1 |
| 1993 | 2 |
| 1994 | 2 |
| 1995 | 2 |
| 1997 | 2 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2007 | 3 |
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\" = 'WI' 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" = 'WI' 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 CHI07CA231Accident · No injuriesData collectionFinal reportBeech A36 · Sturtevant, WIThe pilot's improper decision to land with a tailwind, which resulted in an overrun during landing rollout. Factors contributing to the accident include the dirt pile and the tailwind.NTSB CHI07LA135Accident · No injuriesLimited investigationFinal reportCessna 414A · Sturgeon Bay, WIWorn brakes which resulted in an overrun during landing. A fence was a factor.NTSB CHI07CA117Accident · Minor injuriesData collectionFinal reportNeal Anderson Comp Air 6 · Sturtevant, WIThe pilot's failure to obtain a proper touchdown point, which resulted in a runway over run and subsequent nose-over of the aircraft, and the pilot's improper weather evaluation to land with a quartering tailwind. Factors contributing to the accident were a…NTSB CHI03LA225Accident · No injuriesLimited investigationFinal reportBeech C23 · Madison, WIThe dual student's delay in executing the aborted takeoff. Also causal was the pilot-in-command's delayed remedial action.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 CHI01LA315Accident · No injuriesLimited investigationFinal reportCessna 182M · Marshall, WIThe pilot misjudged his altitude and airspeed and landed long. A factor was the wet grass.NTSB CHI98LA019Accident · No injuriesLimited investigationFinal reportPiper J3L-65 · Reeseville, WIfailure of the normal braking system, due to a low level of brake fluid. Factors relating to the accident were: inadequate inspection of the aircraft by other maintenance personnel, the pilot's failure to check the brakes after brake maintenance/inspection,…NTSB CHI97LA112Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Wautoma, WIthe pilot's improper use of the throttle. Factors were a crosswind and soft terrain.NTSB CHI95LA317Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Lyons, WIThe pilot's lack of experience in the type of operation being conducted, the pilot not maintaining the proper airspeed while on final approach to landing, and a delayed decision to abort the landing.NTSB CHI95LA070Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Cottage Grove, WIThe pilot's selection of unsuitable terrain/runway for landing. Factors related to the accident were: the unfavorable wind, icy runway condition, and snowbank at the end of the runway.NTSB CHI94LA326Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Brookfield, WIthe commercial pilot's poor planning/decision making. A related factor is the wet, grass runway selected for landing.NTSB CHI94LA268Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Lone Rock, WIthe pilot's failure to attain a proper touchdown point on the runway.NTSB CHI93LA122Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-180 · Lyons, WIThe pilot's use of an unsuitable runway.NTSB CHI93LA062Accident · Minor injuriesLimited investigationFinal reportBeech A36 · Milwaukee, WIFailure of the pilot to perform an aborted landing and failure to select a proper touchdown point on the runway.NTSB CHI91LA072Accident · No injuriesLimited investigationFinal reportPiper J3C-65 · Springbrook, WIThe pilot's attempt to takeoff with a strong gusty tailwind.NTSB CHI90LA189Accident · No injuriesLimited investigationFinal reportMitsubishi MU-300 · Milwaukee, WIThe pilot's delayed determination of traction or braking action until too little runway remained to go around or to employ alternate means of activiating the brakes. Contributing to the accident was the overservicing of the main gear struts.NTSB CHI90LA015Accident · No injuriesLimited investigationFinal reportCessna 207 · Dodgeville, WIPilot's improper planning/decision and his delay in deciding to go around. Factors related to the accident were: the unfavorable wind conditions, the pilot's visual perception on the crowned runway, his misjudgement of speed and remaining distance on the…NTSB CHI89LA194Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Mt. Horeb, WIThe pilot's failure to follow proper procedures for breaking-in new brakes and the excessive touchdown speed. Contributing factors were the worn brakes.NTSB CHI89LA051Accident · No injuriesLimited investigationFinal reportCessna 182A · Baldwin, WIFailure of the pilot to go around when he landed long with too much speed for the conditions. Factors related to the accident were: the pilot's excessive airspeed, his failure to attain the proper touchdown point, the crosswind, snowy/icy runway conditions,…NTSB CHI88LA224Accident · Serious injuriesLimited investigationFinal reportCessna 182RG · Dodgeville, WIWhile attempting to land on a runway with wind gusts and a quartering tailwind, the pilot failed to adequately judge and compensate for the wind conditions. The aircraft landed long, and the pilot was unable to bring the aircraft to a stop before the end of…NTSB CHI88LA148Accident · Minor injuriesLimited investigationFinal reportCessna 182M · Menomonee Falls, WINTSB CHI88LA070Accident · No injuriesLimited investigationFinal reportCessna 172A · Crivitz, WIThe aircraft did not accelerate as anticipated by the pilot, who was attempting to takeoff from a wet sod strip. The pilot elected to abort the takeoff, however was unable to stop on the remaining runway, exited the departure end, struck a snow bank and nosed…NTSB CHI87LA222Accident · No injuriesLimited investigationFinal reportCessna 150H · Sparta, WIThe plt was taking off on his pvt strip in a prevailing 12 kt x-wind that was vrbl & blowing fm a 'lull' to 18 KTS. He said the strip was located near an l-shaped ridge which attenuated the general wind flow. Also, he said the 1900' sod strip sloped downhill…NTSB CHI86LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Dodgeville, WIAccording to the pilot, his brakes failed and he was unable to stop before going off the end of the runway and over a 30 foot embankment. During an inspection, the brakes and braking system were found to be free of any defects and in proper working order.…NTSB CHI86FEP06Accident · No injuriesFinal reportPatton Pitts S-1C · Hartford, WIThe plt was on an aerobatic competition flt. He reported that after finishing a sequence of aerobatic maneuvers, he returned to the rwy to land. During the landing, the acft was high on final apch & touched down to FAR down the 2100 ft rwy. It then contd off…NTSB CHI85LA341Accident · No injuriesLimited investigationFinal reportCessna 172H · Whitewater, WIAccording to the plt he planned to use max performance takeoff procedures out of the owner's manual for the takeoff. After brake release the acft began to roll down the sod rwy. Acceleration continued, but according to the plt, his airspeed increase seemed…NTSB CHI85LA320Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Franklin, WIThe pilot used a shortfield takeoff and the acft would not fly. The plt aborted the takeoff and landed on the end of therwy, overrunning the rwy and striking a ditch. The plt reported engine RPM normal and the acft was under max gross takeoff weight.NTSB CHI85LA183Accident · No injuriesLimited investigationFinal reportCessna 152 · Broadhead, WIThe plt stated that during arrival, he entered a traffic pattern for what he thought, according to his directional gyro, was rwy 9. Rwy 9 was 2500 ft long; however, he landed on rwy 3, which was 1520 ft long. During the landing, the plt was unable to stop on…NTSB CHI84LA267Accident · No injuriesLimited investigationFinal reportCessna 152 · Park Falls, WIThe plt reported that during his preflt run-up, everything seemed normal. Using short field takeoff procedures, he rotated at 40 KTS & reached an alt of about 10 ft AGL. However, he stated that the acft did not want to accelerate to the best angle of climb…NTSB CHI84LA154Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Kenosha, WIThe plt stated he mistook the ATIS reported winds of 020 deg at 21 KTS as 210 deg at 20 KTS. After executing the VOR rwy 14 apch, he continued to land on rwy 14. There was standing water on the rwy. While landing with a tail wind, the acft hydroplaned & ran…NTSB CHI84LA136Accident · No injuriesLimited investigationFinal reportCessna 402C · Kenosha, WIThe acft ran off the rwys end after the plt landed downwind to avoid flying through a 'wall of precipation'. During the rollout in slush the brakes froze. The nose gear settled in mud and collapsed.NTSB CHI83LA367Accident · No injuriesLimited investigationFinal reportPiper PA-22-160 · Franksville, WIThe acft was intentionally groundlooped as the acft was not stopping at the runways end. The pilot said the brakes malfunctioned. The mechanic who worked on the acft after the accident said brakes were available even though brake fluidwas low. The mechanic…NTSB CHI83LA188Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Platteville, WIDuring arrival, the plt entered the traffic pattern to land on rwy 27 in x-wind conditions. The rwy was 2200 ft long & was wet from light rain. After making 2 go-arounds, a landing was made on the 3rd apch. The plt reported that the braking was poor to nil.…NTSB CHI82DA100Accident · Minor injuriesFinal reportPiper PA-28-236 · Dodgeville, WIThe student pilot was at the controls during the landing approach. The approach was to an upsloping runway, but with a tailwind component. The aircraft was landed long. It continued off the end of the runway and collided with a ditch. The instructor reported…