Long landing rollout — SWA2506
KISM · 152026-08-15 16:27 UTC· KOKC → KISM· UMB BANK NA TRUSTEE· B738
SWA2506 (UMB Bank NA) was operating from KOKC to KISM on 2026-08-15. SkyMeter detected a long landing rollout at Kissimmee Gateway Airport (KISM) on runway 15 at 16:27 UTC. Trace data at the event: 85 ft AGL, 22 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 3 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/4962 2026-08-13 18:15Z – 2026-08-20 18:00Z SFC–2,000 ft
YOUNGSPORT, TX, Thursday, August 13, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/3174 2026-08-15 11:00Z – 2026-08-17 02:00Z SFC–400 ft
Memphis, TN, Saturday, August 15, 2026 through Monday, August 17, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/3355 2026-08-15 11:00Z – 2026-08-17 02:00Z SFC–400 ft
Memphis, TN, Saturday, August 15, 2026 through Monday, August 17, 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 15
- 85 ft AGL at event
- 22 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KISM 170630Z AUTO 04004KT 10SM CLR 26/23 A3016 RMK T02600230 MADISHF
Flight context
- SWA2506
- UMB Bank NA
- B738
- KOKC → KISM
- 2026-08-15 16:27 UTC
- KISM runway 15
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