Long landing rollout — GXA6163
KHRL · 132026-01-01 00:55 UTC· UMB BANK NA TRUSTEE· A320
GXA6163 (UMB Bank NA) was inbound to KHRL on 2026-01-01. SkyMeter detected a long landing rollout at Valley International Airport (KHRL) on runway 13 at 00:55 UTC. Trace data at the event: 42 ft AGL, 4 kt GS, 0 fpm vertical. Approach stability score: 81/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 5 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/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 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 13
- 42 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- Approach stability 81/100
- 5 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KHRL 290852Z AUTO 14006KT 10SM CLR 26/24 A2981 RMK AO2 SLP093 T02610244 58010
Flight context
- GXA6163
- UMB Bank NA
- A320
- 2026-01-01 00:55 UTC
- KHRL runway 13
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