Long landing rollout — BACN01

KBLV · 14R

2026-08-19 20:31 UTC· KMCN KBLV· GLEX

BACN01 was operating from KMCN to KBLV on 2026-08-19. SkyMeter detected a long landing rollout at Scott AFB/Midamerica Airport (KBLV) on runway 14R at 20:31 UTC. Trace data at the event: 429 ft AGL, 6 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 1 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)
  • SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

    Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

    View FAA NOTAM →
  • UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft

    Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/5153 2026-08-18 05:00Z – 2026-08-20 09:30Z SFC–17,999 ft

    Macon, GA, Tuesday, August 18, 2026 through Thursday, August 20, 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 14R
  • 429 ft AGL at event
  • 6 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KBLV 160455Z 00000KT 10SM CLR 25/25 A3009 RMK AO2A SLP187 T02490245 RVRNO VISNO RWY32L $

Flight context

  • BACN01
  • GLEX
  • KMCN → KBLV
  • 2026-08-19 20:31 UTC
  • KBLV runway 14R

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