Go-around — SWA4129
KPHX · 07R2026-07-16 01:55 UTC· KDAL → KPHX· SOUTHWEST AIRLINES CO· B737
SWA4129 (Southwest Airlines) was operating from KDAL to KPHX on 2026-07-16. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 07R at 01:55 UTC. Trace data at the event: 2177 ft AGL, 160 kt GS. METAR at the time reported 30 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/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft
DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4009 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4019 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z
DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC
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/3966 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7079 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - SECURITY6/7078 2026-06-27 01:07Z – 2026-07-21 06:59Z SFC–400 ft
Mesa, AZ
View FAA NOTAM → - SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - SECURITY6/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft
Frisco, TX
View FAA NOTAM → - HAZARDS6/2884 2026-07-04 17:45Z – 2026-07-18 03:00Z SFC–13,800 ft
35NM NW SILVER CITY, NM, Saturday, July 4, 2026 through Saturday, July 18, 2026 UTC
View FAA NOTAM → - SECURITY6/4573 2026-07-14 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft
Dallas, TX, Tuesday, July 14, 2026 through Sunday, July 19, 2026 Local
View FAA NOTAM → - SECURITY6/6784 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Denton, TX
View FAA NOTAM → - SECURITY6/6841 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Fort Worth, TX
View FAA NOTAM → - SECURITY6/6849 2026-07-15 13:07Z – 2026-07-21 04:59Z SFC–400 ft
Irving, TX
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 07R
- 2177 ft AGL at event
- 160 kt ground speed
- 0 fpm vertical
- 30 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KPHX 162151Z 06017KT 10SM FEW027 BKN045 BKN060 OVC130 27/21 A2998 RMK AO2 PK WND 06027/2101 SLP133 CB DSNT N-S SHRA DSNT N-NE T02670206 $
Flight context
- SWA4129
- Southwest Airlines
- B737
- KDAL → KPHX
- 2026-07-16 01:55 UTC
- KPHX runway 07R
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