Unstable approach — VXP532

KTPA · 10

2026-06-06 01:27 UTC· KILG → KTPA· UMB BANK NA TRUSTEE· B738

VXP532 (UMB Bank NA) was operating from KILG to KTPA on 2026-06-06. SkyMeter detected a low approach-stability score at Tampa International Airport (KTPA) on runway 10 at 01:27 UTC. Trace data at the event: 1107 ft AGL, 149 kt GS. METAR at the time reported 2 kt wind, 16,093 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/9784 2026-05-16 12:00Z – 2026-06-12 22:00Z SFC–400 ft

    Moyock, NC, Saturday, May 16, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

    Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 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/3970 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    White Sulphur Springs, WV, 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/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/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    CHARLOTTE, 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/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/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4380 2026-06-01 13:00Z – 2026-06-06 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, June 1, 2026 through Saturday, June 6, 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 10
  • 1107 ft AGL at event
  • 149 kt ground speed
  • 0 fpm vertical
  • 2 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KTPA 150053Z 04003KT 10SM CLR 28/18 A3004 RMK AO2 SLP172 T02780178

Flight context

  • VXP532
  • UMB Bank NA
  • B738
  • KILG → KTPA
  • 2026-06-06 01:27 UTC
  • KTPA runway 10

All events on this flight

Unstable approach 01:27:32 UTC · KTPA runway 10 · 1,107 ft AGL · 149 kt GS
Unstable approach 01:27:32 UTC · KTPA runway 10 · 1,107 ft AGL · 149 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· KTPA