Long landing rollout — VXP564

KILG · 19

2026-08-17 03:42 UTC· KMCO → KILG· UMB BANK N A TRUSTEE· B738

▶ Replay 📊 Analyse

VXP564 (UMB Bank N A) was operating from KMCO to KILG on 2026-08-17. SkyMeter detected a long landing rollout at New Castle Airport (KILG) on runway 19 at 03:42 UTC. Trace data at the event: 65 ft AGL, 12 kt GS, 0 fpm vertical. METAR at the time reported 6 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)
  • SPACE OPERATIONS6/4810 2026-08-17 00:35Z – 2026-08-17 02:03Z SFC–180 ft

    Cape Canaveral, FL, Sunday, August 16, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/4819 2026-08-17 00:35Z – 2026-08-17 02:03Z SFC–180 ft

    Cape Canaveral, FL, 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 19
  • 65 ft AGL at event
  • 12 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KILG 170630Z AUTO 22004KT 10SM BKN070 22/18 A3027 RMK T02200180 MADISHF

Flight context

  • VXP564
  • UMB Bank N A
  • B738
  • KMCO → KILG
  • 2026-08-17 03:42 UTC
  • KILG runway 19

All events on this flight

Long landing rollout 03:42:13 UTC · KILG runway 19 · 65 ft AGL · 12 kt GS
Long landing rollout 03:42:13 UTC · KILG runway 19 · 65 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· KILG