Long landing rollout — VXP525

KILG · 19

2026-07-27 00:18 UTC· KLAL KILG· UMB BANK N A TRUSTEE· B738

VXP525 (UMB Bank N A) was operating from KLAL to KILG on 2026-07-27. SkyMeter detected a long landing rollout at New Castle Airport (KILG) on runway 19 at 00:18 UTC. Trace data at the event: 65 ft AGL, 10 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 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/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft

    2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC

    View FAA NOTAM →
  • VIP6/8360 2026-07-24 19:00Z – 2026-07-26 23:00Z SFC–4,999 ft

    Middleburg, VA, Friday, July 24, 2026 through Sunday, July 26, 2026 Local

    View FAA NOTAM →
  • VIP6/8425 2026-07-26 11:30Z – 2026-07-26 22:30Z SFC–9,999 ft

    Sterling, VA, Sunday, July 26, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/8779 2026-07-26 18:03Z – 2026-08-02 01:30Z SFC–1,300 ft

    16NM NE LAKE CITY, FL, Sunday, July 26, 2026 through Sunday, August 2, 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 19
  • 65 ft AGL at event
  • 10 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KILG 162151Z 18007KT 10SM CLR 26/20 A3029 RMK AO2 SLP257 T02610200 PNO $

Flight context

  • VXP525
  • UMB Bank N A
  • B738
  • KLAL → KILG
  • 2026-07-27 00:18 UTC
  • KILG runway 19

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