NTSB investigations, OR
31 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 3 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 4 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 2 |
| 1990 | 2 |
| 1991 | 2 |
| 1992 | 2 |
| 1993 | 1 |
| 1994 | 2 |
| 1996 | 2 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 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\" = 'OR' 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" = 'OR' 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 SEA04LA096Accident · No injuriesLimited investigationFinal reportCessna 172M · Vernonia, ORThe instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway.NTSB SEA03CA138Accident · No injuriesData collectionFinal reportBeech F90 · Sunriver, ORThe pilot's misjudgment of distance while landing, which resulted in a runway overrun. Factors include rough uneven terrain and a tailwind.NTSB SEA02LA152Accident · No injuriesLimited investigationFinal reportBeech B35 · Halfway, ORThe pilot's delay in initiating an aborted takeoff and his failure to establish climb out of ground effect. Contributing factors were the high aircraft weight and high density altitude as well as the fence and berm, which the aircraft struck.NTSB SEA00LA125Accident · No injuriesLimited investigationFinal reportCessna 172I · Sandy, ORThe pilot's failure to attain the proper touchdown point for landing, and his failure to go around from the improperly executed approach. Factors included the pilot's failure to attain the proper glidepath on the approach, a short landing runway, and…NTSB SEA96LA098Accident · No injuriesLimited investigationFinal reportConsolidated-Vultee BT-13A · Brookings, ORthe pilot's misjudgment of distance/speed during the approach to landing, his failure to attain a proper touchdown point for landing, and his failure to perform a go-around, while there was sufficient runway and airspeed remaining. The tailwind was a related…NTSB SEA96LA087Accident · No injuriesLimited investigationFinal reportNanchang CJ-6A · Molalla, ORthe pilot's failure to adequately plan the approach, and his misjudgment of distance and speed during the landing. The wet runway was a related factor.NTSB SEA94LA216Accident · No injuriesLimited investigationFinal reportCessna 170B · Redmond, ORProper touchdown point was not attained. A factor to the accident was inadequate remedial action.NTSB SEA94LA155Accident · No injuriesLimited investigationFinal reportCessna 150L · Hubbard, ORDelayed in flight planning/decision.NTSB SEA94LA012Accident · No injuriesLimited investigationFinal reportCessna T-337E · Yamhill, ORThe pilot failed to attain the proper touchdown point. The tailwind was a factor.NTSB SEA92LA178Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Pacific City, ORThe pilot selected the wrong runway relative to the wind and then delayed in aborting the landing. The tailwind was a factor.NTSB SEA92LA166Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Sisters, ORThe improper use of flight controls by the PIC during an aborted takeoff. Factors relating to the accident were the unfavorable wind (windshift) encountered during takeoff ground roll, the tailwind and high da weather conditions.NTSB SEA91LA141Accident · No injuriesLimited investigationFinal reportCessna 172-M · Salem, ORThe pilot's poor in-flight decision and his failure to select a proper touchdown point. Factors include a wet runway, soft terrain and high vegetation.NTSB SEA91FA057Accident · 3 fatalField investigationFinal reportCessna 182J · Glendale, ORThe pilot's failure to use all available runway for this landing, aggravated by his failure to initiate a go-around after misjudging the proper touchdown point and landing with a tailwind.NTSB SEA90LA134Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Yamhill, ORThe pilot's failure to retract the flaps during go-around.NTSB SEA90LA056Accident · Minor injuriesLimited investigationFinal reportPiper PA-28 · Yamhill, ORThe pilot's failure to use the proper touchdown point for landing. The tailwind was a factor related to the accident.NTSB SEA90LA015Accident · No injuriesLimited investigationFinal reportCessna 182P · Hillsboro, ORFailure of the pilot to attain the proper touchdown point or go around while there was still sufficient runway and speed remaining. The tailwind was a related factor.NTSB SEA89LA069Accident · No injuriesLimited investigationFinal reportCessna 182 · Arlington, ORThe student pilot touched down too FAR down the runway to allow him to stop before running into a trailer.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 SEA89LA020Accident · No injuriesLimited investigationFinal reportGates Learjet 25B · Bend, ORThe pilot visually inspected the runway while making a low pass. He reported afterward that he saw no evidence of ice or snow on the runway. The copilot called UNICOM but was told, while the aircraft was on short final, that the winds were calm and the…NTSB SEA88LA079Accident · Minor injuriesLimited investigationFinal reportMooney M20E · The Dalles, OROn arrival, plt found destination obscured by unforecast fog, held briefly, then diverted to an alternate airport. On arrival at alt in darkness, plt did not know freq (UNICOM) to activate rwy lights. Plt made low pass to acquire rwy environment as fuel state…NTSB SEA87LA087Accident · No injuriesLimited investigationFinal reportCessna 310L · Chiloquin, ORThe aircraft departed the end of the runway during landing roll. The aircraft then went down an embankment and through a fence. The right main gear collapsed with the aircraft turning 90 degrees before coming to rest. A tailwind was present during landing.…NTSB SEA87LA015Accident · Minor injuriesLimited investigationFinal reportMooney M20D · Hillsboro, ORThe pilot elected to land with a 12 to 15 knot tailwind. An excessive ground speed resulted with an overshoot. The pilot elected to go-around too late and once the go-around was attempted the aircraft struck trees at the departure end of the runway at about…NTSB SEA85LA200Accident · No injuriesLimited investigationFinal reportCessna 180A · Buxton, ORThe pilot misjudged his touchdown point on the 1,000 foot airstrip and had an excess of airspeed. And overrun occurred and the aircraft went down an embankment. At the time of touchdown, there was only about 4 KTS of headwind available.NTSB SEA85LA141Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · North Plains, ORAn overrun occurred due to excess speed and touching down 1/4 of the way down the 2100 foot glider strip. The aircraft rolled onto two foot high alfalfa where it then nosed over. The pilot previously landed gliders on the gliderport but never an engine…NTSB SEA85LA093Accident · No injuriesLimited investigationFinal reportLake Buccaneer · Dexter, ORThe acft bounced during touchdown several times while attending to land on the water. The acft was too close to a dam to make a go-around. The acft then struck the dam head on.NTSB SEA85LA063Accident · No injuriesLimited investigationFinal reportTaylorcraft F19 · Gaston, ORThe plt was attempting a precautionary landing onto a 1000 foot private grass airstrip due to a noise outside the acft which was heard inflt. The plt was landing to the east with a right quartering tailwind of 5 to 10 knots. An overrun occurred and the plt…NTSB SEA84LA112Accident · No injuriesLimited investigationFinal reportCessna 188B · Shedd, ORWhile landing on a 1600 ft ag strip, the plt realized he had too much speed. However, there were power lines at the departure end of the strip, so he elected not to attempt a go-around. He intentionally ground looped the acft to avoid a ditch & road at the…NTSB SEA83LA098Accident · No injuriesLimited investigationFinal reportCessna 172-I · Wasco, ORThe acft went off the departure end of the runway during landing and groundlooped in a plowed field. The pilot landed in a 27 kt quartering tailwind. The acft rolled onto a freshly harrowed field. The nose wheel caught the dirt and veeredto the left and the…NTSB SEA83LA021Accident · No injuriesLimited investigationFinal reportCessna U206 · Cove, ORPilot landed on icy runway and slid 1200 feet into the river.NTSB SEA83LA003Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Newberg, ORDuring a local flight, the pilot made 3 landings on a 2860 ft runway at sportsman airpark. He then landed on a 2300 ft turf runway at chehalem airport in light and variable wind conditions. While landing at chehalem, the aircraft rolled beyond the departure…NTSB SEA82DA071Accident · No injuriesFinal reportCessna 180K · Jordan Valley, ORThe aircraft landed 1/3 of the way down the runway and continued off the end into a fence. The pilot stated that the wet sod runway surface hindered adequate braking.