Go-around — SWA3208

SWA3208 (Southwest Airlines) was operating from KPDX to KPHX on 2026-06-17. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 26 at 04:09 UTC. Trace data at the event: 1314 ft AGL, 152 kt GS. METAR at the time reported 10 kt wind, 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.

• SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

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

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

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

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

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

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

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

  PORTLAND, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Portland, OR, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  GOLETA, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVINE, 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/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/5894 2026-06-05 20:31Z – 2026-06-19 02:00Z SFC–10,000 ft

  38NM SE TWIN FALLS, ID, Friday, June 5, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5936 2026-06-06 03:00Z – 2026-06-19 02:00Z SFC–7,500 ft

  27NM SE TWIN FALLS, ID, Saturday, June 6, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6225 2026-06-09 14:00Z – 2026-06-21 02:00Z SFC–10,500 ft

  31NM SW NEPHI, UT, Tuesday, June 9, 2026 through Sunday, June 21, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6827 2026-06-09 17:15Z – 2026-06-22 02:00Z SFC–10,000 ft

  9NM SW TOOELE, UT, Tuesday, June 9, 2026 through Monday, June 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6965 2026-06-10 14:00Z – 2026-06-22 03:00Z SFC–10,000 ft

  9NM SW TOOELE, UT, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft

  Manhattan Beach, CA

  View FAA NOTAM →
• HAZARDS6/8214 2026-06-14 17:34Z – 2026-06-17 07:00Z SFC–400 ft

  3.8NM NW TRACY, CA, Sunday, June 14, 2026 through Wednesday, June 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8547 2026-06-16 02:03Z – 2026-06-30 03:00Z SFC–6,000 ft

  3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8596 2026-06-16 14:45Z – 2026-06-17 14:00Z SFC–11,000 ft

  58NM S ST. GEORGE, UT, Tuesday, June 16, 2026 through Wednesday, June 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8709 2026-06-16 17:25Z – 2026-06-29 00:15Z SFC–6,000 ft

  3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Monday, June 29, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7949 2026-06-17 01:00Z – 2026-06-17 10:00Z SFC–3,000 ft

  San Francisco, CA, Tuesday, June 16, 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.

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