Long landing rollout — UAL520

KISM · 15

2026-07-31 02:05 UTC· UNITED AIRLINES INC· B39M

▶ Replay 📊 Analyse

UAL520 (United Airlines) was inbound to KISM on 2026-07-31. SkyMeter detected a long landing rollout at Kissimmee Gateway Airport (KISM) on runway 15 at 02:05 UTC. Trace data at the event: 96 ft AGL, 13 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 4 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/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft

    16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/8418 2026-07-27 12:30Z – 2026-08-01 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, July 27, 2026 through Saturday, August 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9092 2026-07-30 05:00Z – 2026-07-31 09:30Z SFC–17,999 ft

    Macon, GA, Thursday, July 30, 2026 through Friday, July 31, 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 15
  • 96 ft AGL at event
  • 13 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KISM 171256Z VRB06KT 10SM CLR 27/22 A3016 RMK AO2 SLP213 T02720222 $

Flight context

  • UAL520
  • United Airlines
  • B39M
  • 2026-07-31 02:05 UTC
  • KISM runway 15

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· KISM