Long landing rollout — SPAR13

KBLV · 32L

2026-08-23 21:15 UTC· KADW → KBLV· B737

▶ Replay 📊 Analyse

SPAR13 was operating from KADW to KBLV on 2026-08-23. SkyMeter detected a long landing rollout at Scott AFB/Midamerica Airport (KBLV) on runway 32L at 21:15 UTC. Trace data at the event: 436 ft AGL, 2 kt GS, 0 fpm vertical. METAR at the time reported 9 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)
  • VIP6/5889 2026-08-20 21:15Z – 2026-08-23 21:15Z SFC–4,999 ft

    Cincinnati, OH, Thursday, August 20, 2026 through Sunday, August 23, 2026 Local

    View FAA NOTAM →
  • VIP6/6737 2026-08-23 12:00Z – 2026-08-23 22:30Z SFC–9,999 ft

    Sterling, VA, Sunday, August 23, 2026 Local

    View FAA NOTAM →
  • VIP6/6937 2026-08-23 20:07Z – 2026-08-23 21:15Z SFC–4,999 ft

    Cincinnati, OH

    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 32L
  • 436 ft AGL at event
  • 2 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KBLV 161321Z COR 08003KT 10SM SCT100 BKN200 25/25 A3023 RMK AO2A SLP236 $ COR 1335

Flight context

  • SPAR13
  • B737
  • KADW → KBLV
  • 2026-08-23 21:15 UTC
  • KBLV runway 32L

All events on this flight

Long landing rollout 21:15:33 UTC · KBLV runway 32L · 436 ft AGL · 2 kt GS
Long landing rollout 21:15:33 UTC · KBLV runway 32L · 436 ft AGL · 2 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· KBLV