Long landing rollout — SCX3001

US-11535 · 22

2026-06-25 23:05 UTC· KLAS ?· BANK OF UTAH TRUSTEE· B738

SCX3001 (Bank of Utah) had departed KLAS on 2026-06-25. SkyMeter detected a long landing rollout at US-11535 (US-11535) on runway 22 at 23:05 UTC. Trace data at the event: 590 ft AGL, 5 kt GS. Approach stability score: 47/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 3 kt wind, 2 kt crosswind component. 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)
  • SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

    STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

    TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

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

    Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/8795 2026-06-17 15:00Z – 2026-06-29 04:00Z SFC–11,000 ft

    58NM S ST. GEORGE, UT, Wednesday, June 17, 2026 through Monday, June 29, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/8796 2026-06-17 15:00Z – 2026-06-29 04:00Z SFC–11,500 ft

    65NM SE CEDAR CITY, UT, Wednesday, June 17, 2026 through Monday, June 29, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9124 2026-06-18 14:00Z – 2026-07-01 04:00Z SFC–15,000 ft

    10NM N LOS ALAMOS, NM, Thursday, June 18, 2026 through Wednesday, July 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9269 2026-06-18 19:00Z – 2026-06-30 04:00Z SFC–11,000 ft

    39NM NW MESQUITE, NV, Thursday, June 18, 2026 through Tuesday, June 30, 2026 UTC

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

    46 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

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

    39 NM NW MESQUITE, NV, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9457 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft

    39 NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/9458 2026-06-21 13:00Z – 2026-07-04 04:00Z SFC–12,000 ft

    37NM NW MESQUITE, NV, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/0608 2026-06-25 13:00Z – 2026-07-09 03:00Z SFC–14,000 ft

    15NM W LOS ALAMOS, NM, Thursday, June 25, 2026 through Thursday, July 9, 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 22
  • 590 ft AGL at event
  • 5 kt ground speed
  • 0 fpm vertical
  • Approach stability 47/100
  • 3 kt wind
  • 2 kt crosswind component

Flight context

  • SCX3001
  • Bank of Utah
  • B738
  • 2026-06-25 23:05 UTC
  • US-11535 runway 22

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

SkyMeter · trace data observed via ADS-B· US-11535