Long landing rollout — UAL323
KDEN · 35R2026-06-22 01:57 UTC· UMB BANK NA TRUSTEE· B738
UAL323 (UMB Bank NA) was inbound to KDEN on 2026-06-22. SkyMeter detected a long landing rollout at Denver International Airport (KDEN) on runway 35R at 01:57 UTC. Trace data at the event: 5364 ft AGL, 5 kt GS. Approach stability score: 86/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 14 kt wind, 13 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/7480 2026-06-11 12:00Z – 2026-06-23 03:00Z SFC–9,500 ft
24NM SW CHADRON, NE, Thursday, June 11, 2026 through Tuesday, June 23, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/5706 2026-06-11 14:00Z – 2026-06-23 04:00Z SFC–400 ft
Omaha, NE, Thursday, June 11, 2026 through Tuesday, June 23, 2026 UTC
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 35R
- 5364 ft AGL at event
- 5 kt ground speed
- 0 fpm vertical
- Approach stability 86/100
- 14 kt wind
- 13 kt crosswind component
- 16,093 m visibility
- KDEN 170153Z 21005KT 10SM BKN120 OVC220 21/11 A3032 RMK AO2 SLP206 T02060111
Flight context
- UAL323
- UMB Bank NA
- B738
- 2026-06-22 01:57 UTC
- KDEN runway 35R
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