Long landing rollout — UAL318

UAL318 (United Airlines) was operating from KDEN to KEUG on 2026-06-25. SkyMeter detected a long landing rollout at Mahlon Sweet Field (KEUG) on runway 16L at 19:45 UTC. Trace data at the event: 360 ft AGL, 4 kt GS, 0 fpm vertical. Approach stability score: 88/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 7 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.

• SECURITY6/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4159 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9461 2026-06-21 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9460 2026-06-21 14:00Z – 2026-07-04 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9504 2026-06-21 14:14Z – 2026-07-05 15:00Z SFC–10,500 ft

  10NM NE OGDEN, UT, Sunday, June 21, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9555 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9562 2026-06-22 12:00Z – 2026-07-04 04:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9582 2026-06-22 13:04Z – 2026-07-05 15:00Z SFC–10,500 ft

  29NM NW TOOELE, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9592 2026-06-22 13:29Z – 2026-07-05 15:00Z SFC–10,500 ft

  3.5NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9834 2026-06-22 19:21Z – 2026-07-05 15:00Z SFC–10,500 ft

  4NM SW SALT LAKE CITY, UT, Monday, June 22, 2026 through Sunday, July 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0278 2026-06-24 04:32Z – 2026-06-30 05:00Z SFC–8,000 ft

  16NM S ALTURAS, CA, Wednesday, June 24, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0276 2026-06-24 15:00Z – 2026-07-07 04:00Z SFC–10,500 ft

  4NM SW SALT LAKE CITY, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0613 2026-06-25 13:00Z – 2026-07-08 03:00Z SFC–14,500 ft

  27NM SW JACKSON, WY, Thursday, June 25, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• SPACE OPERATIONS6/0756 2026-06-25 16:25Z – 2026-06-26 05:00Z SFC–10,000 ft

  56 ZSE AIRSPACE BROTHERS, OR, Thursday, June 25, 2026 through Friday, June 26, 2026 UTC

  View FAA NOTAM →
• AIR SHOWS/SPORTS6/9764 2026-06-25 19:30Z – 2026-06-25 21:10Z SFC–17,999 ft

  Ogden, UT, Thursday, June 25, 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.

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