Long landing rollout — VXP543
KILG · 192026-06-15 00:44 UTC· KFLL → KILG· UMB BANK NA TRUSTEE· B738
VXP543 (UMB Bank NA) was operating from KFLL to KILG on 2026-06-15. SkyMeter detected a long landing rollout at New Castle Airport (KILG) on runway 19 at 00:44 UTC. Trace data at the event: 66 ft AGL, 9 kt GS, 0 fpm vertical. METAR at the time reported 8 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)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3971 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4001 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4005 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/5839 2026-06-11 09:45Z – 2026-06-14 22:30Z
WASHINGTON, DC, Thursday, June 11, 2026 through Sunday, June 14, 2026 UTC
View FAA NOTAM → - AIR SHOWS/SPORTS6/6230 2026-06-11 16:45Z – 2026-06-15 03:30Z SFC–2,500 ft
Washington, DC, Thursday, June 11, 2026 through Monday, June 15, 2026 UTC
View FAA NOTAM → - VIP6/7533 2026-06-14 12:00Z – 2026-06-14 23:00Z SFC–9,999 ft
Sterling, VA, Sunday, June 14, 2026 Local
View FAA NOTAM → - HAZARDS6/8209 2026-06-14 14:58Z – 2026-06-17 00:15Z SFC–1,500 ft
13NM NW MOUNT PLEASANT, SC, Sunday, June 14, 2026 through Wednesday, June 17, 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
- 66 ft AGL at event
- 9 kt ground speed
- 0 fpm vertical
- 8 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KILG 182251Z 34008KT 10SM SCT060 26/17 A3006 RMK AO2 SLP179 T02610172 PNO $
Flight context
- VXP543
- UMB Bank NA
- B738
- KFLL → KILG
- 2026-06-15 00:44 UTC
- KILG runway 19
All events on this flight
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