Return to field — GXA6152

KHRL · 31

2026-08-02 12:55 UTC· KHRL → KHRL· UMB BANK NA TRUSTEE· A320

▶ Replay 📊 Analyse

GXA6152 (UMB Bank NA) was operating from KHRL to KHRL (Valley International Airport) on 2026-08-02. SkyMeter detected a return to field at Valley International Airport (KHRL) on runway 31 at 12:55 UTC. Peak cruise altitude FL415, turnaround area near Krebs, US. METAR at the time reported 0 kt wind, 16,093 m visibility. 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 →
  • SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 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 31
  • 41530 ft AGL at event
  • 486 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KHRL 171052Z 35004KT 10SM CLR 24/23 A3006 RMK AO2 SLP177 T02440233

Flight context

  • GXA6152
  • UMB Bank NA
  • A320
  • KHRL → KHRL
  • 2026-08-02 12:55 UTC
  • KHRL runway 31

All events on this flight

Return to field 12:55:39 UTC · KHRL runway 31 · 41,530 ft AGL · 486 kt GS
Long landing rollout 18:27:11 UTC · KHRL runway 17R · 39 ft AGL · 3 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· KHRL