Long landing rollout — UAL1093

UAL1093 (United Airlines) was operating from KLAX to KFME on 2026-05-23. SkyMeter detected a long landing rollout at Tipton Airport (KFME) on runway 10 at 21:23 UTC. Trace data at the event: 147 ft AGL, 11 kt GS, 0 fpm vertical. METAR at the time reported 13 kt wind, 5 kt crosswind component, 11,265 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.

• SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

  Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

  View FAA NOTAM →
• HAZARDS6/0618 2026-05-15 13:00Z – 2026-05-28 04:00Z SFC–13,500 ft

  22NM NE RUIDOSO, NM, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0607 2026-05-15 14:00Z – 2026-05-28 04:00Z SFC–12,000 ft

  30NM SW NEPHI, UT, Friday, May 15, 2026 through Thursday, May 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0887 2026-05-16 18:37Z – 2026-05-30 04:00Z SFC–10,500 ft

  19NM SW TUCUMCARI, NM, Saturday, May 16, 2026 through Saturday, May 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1015 2026-05-18 00:28Z – 2026-06-01 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Monday, May 18, 2026 through Monday, June 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1358 2026-05-19 00:52Z – 2026-06-02 02:00Z SFC–10,000 ft

  5NM S CAMPO, CO, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1626 2026-05-19 22:38Z – 2026-06-02 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Tuesday, May 19, 2026 through Tuesday, June 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2366 2026-05-22 06:00Z – 2026-06-05 04:00Z SFC–10,000 ft

  12NM S PRESCOTT, AZ, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2354 2026-05-22 12:00Z – 2026-06-04 04:00Z SFC–15,500 ft

  22NM NE RUIDOSO, NM, Friday, May 22, 2026 through Thursday, June 4, 2026 UTC

  View FAA NOTAM →
• VIP6/2150 2026-05-22 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft

  CINCINNATI, OH, Friday, May 22, 2026 through Monday, May 25, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/1151 2026-05-22 23:00Z – 2026-05-24 06:00Z SFC–400 ft

  indianapolis, IN, Friday, May 22, 2026 through Sunday, May 24, 2026 UTC

  View FAA NOTAM →
• VIP6/2510 2026-05-23 12:00Z – 2026-05-23 23:00Z SFC–9,999 ft

  Sterling, VA, Saturday, May 23, 2026 Local

  View FAA NOTAM →
• SPACE OPERATIONS6/2194 2026-05-23 14:00Z – 2026-05-23 23:00Z SFC–15,500 ft

  94 ZLC AIRSPACE FAIRFIELD, UT, Saturday, May 23, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/1028 2026-05-23 15:00Z – 2026-05-25 22:00Z SFC–400 ft

  Charlottesville, VA, Saturday, May 23, 2026 through Monday, May 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2564 2026-05-23 20:35Z – 2026-05-26 16:00Z SFC–5,000 ft

  GARDEN GROVE, CA, Saturday, May 23, 2026 through Tuesday, May 26, 2026 UTC

  View FAA NOTAM →
• VIP6/2530 2026-05-23 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft

  CINCINNATI, OH, Saturday, May 23, 2026 through Monday, May 25, 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.

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