Long landing rollout — SWA1523

KPWK · 24

2026-08-12 19:38 UTC· KDCA → KPWK· BANK OF UTAH TRUSTEE· B737

▶ Replay 📊 Analyse

SWA1523 (Bank of Utah) was operating from KDCA to KPWK on 2026-08-12. SkyMeter detected a long landing rollout at Chicago Executive Airport (KPWK) on runway 24 at 19:38 UTC. Trace data at the event: 606 ft AGL, 12 kt GS. METAR at the time reported 10 kt wind, 7 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)
  • VIP6/2748 2026-08-08 14:00Z – 2026-08-16 22:00Z SFC–4,999 ft

    THURMONT, MD, Saturday, August 8, 2026 through Sunday, August 16, 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 24
  • 606 ft AGL at event
  • 12 kt ground speed
  • 0 fpm vertical
  • 10 kt wind
  • 7 kt crosswind component
  • 16,093 m visibility
  • KPWK 161852Z 04008KT 10SM FEW029 BKN036 BKN110 22/18 A3033 RMK AO2 SLP267 T02170183 $

Flight context

  • SWA1523
  • Bank of Utah
  • B737
  • KDCA → KPWK
  • 2026-08-12 19:38 UTC
  • KPWK runway 24

All events on this flight

Long landing rollout 19:38:01 UTC · KPWK runway 24 · 606 ft AGL · 12 kt GS
Diversion 19:38:02 UTC · KPWK runway 24 · 0 ft AGL · 0 kt GS
Diversion 19:38:02 UTC · KPWK runway 06 · 641 ft AGL · 120 kt GS
Long landing rollout 19:38:01 UTC · KPWK runway 24 · 606 ft AGL · 12 kt GS

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