Long landing rollout — SKW4665
KBIS · 312026-08-08 01:07 UTC· KDEN → KBIS· UNITED AIRLINES INC· E75L
SKW4665 (United Airlines) was operating from KDEN to KBIS on 2026-08-08. SkyMeter detected a long landing rollout at Bismarck Municipal Airport (KBIS) on runway 31 at 01:07 UTC. Trace data at the event: 1673 ft AGL, 5 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft
83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft
33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC
View FAA NOTAM → - SECURITY6/1983 2026-08-07 06:01Z – 2026-08-17 05:59Z SFC–400 ft
Sturgis, SD, Friday, August 7, 2026 through Sunday, August 16, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 31
- 1673 ft AGL at event
- 5 kt ground speed
- 0 fpm vertical
- 6 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KBIS 162052Z AUTO 12010KT 10SM OVC055 18/11 A3017 RMK AO2 RAB1957E06 SLP224 P0000 60000 T01830111 56020
Flight context
- SKW4665
- United Airlines
- E75L
- KDEN → KBIS
- 2026-08-08 01:07 UTC
- KBIS runway 31
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data