Go-around — SWA672

KPHX · 07L

2026-06-28 11:49 UTC· BANK OF UTAH TRUSTEE· B38M

SWA672 (Bank of Utah) was inbound to KPHX on 2026-06-28. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 07L at 11:49 UTC. Trace data at the event: 3381 ft AGL, 188 kt GS. METAR at the time reported 6 kt wind, 5 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

    Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

    CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

    Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

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

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 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 07L
  • 3381 ft AGL at event
  • 188 kt ground speed
  • 0 fpm vertical
  • 6 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KPHX 171858Z 12003G16KT 10SM SCT033 BKN055 BKN085 BKN160 BKN270 29/21 A3005 RMK AO2 T02940211 $

Flight context

  • SWA672
  • Bank of Utah
  • B38M
  • 2026-06-28 11:49 UTC
  • KPHX runway 07L

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· KPHX