Go-around — AAL2058
KPHX · 262026-07-27 22:15 UTC· KMCI → KPHX· WILMINGTON TRUST CO TRUSTEE· B738
AAL2058 (Wilmington Trust) was operating from KMCI to KPHX on 2026-07-27. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 26 at 22:15 UTC. Trace data at the event: 1415 ft AGL, 158 kt GS. METAR at the time reported 11 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.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- HAZARDS6/5450 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/5451 2026-07-14 04:00Z – 2026-07-29 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Tuesday, July 14, 2026 through Wednesday, July 29, 2026 UTC
View FAA NOTAM → - HAZARDS6/6360 2026-07-17 04:00Z – 2026-07-30 04:00Z SFC–15,000 ft
9NM SW PUEBLO, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6395 2026-07-17 12:00Z – 2026-07-30 04:00Z SFC–13,000 ft
14NM N CORTEZ, CO, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6567 2026-07-18 13:00Z – 2026-08-01 04:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Saturday, July 18, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6736 2026-07-19 12:00Z – 2026-08-01 03:00Z SFC–16,000 ft
16NM W MONTICELLO, UT, Sunday, July 19, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/6876 2026-07-20 13:00Z – 2026-08-03 04:00Z SFC–16,000 ft
7NM SW DEL NORTE, CO, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/8008 2026-07-23 12:00Z – 2026-08-01 03:00Z SFC–12,000 ft
16NM W MONTICELLO, UT, Thursday, July 23, 2026 through Saturday, August 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/8010 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft
19NM NE OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/8012 2026-07-23 12:00Z – 2026-08-12 04:00Z SFC–16,500 ft
1NM N OURAY, CO, Thursday, July 23, 2026 through Wednesday, August 12, 2026 UTC
View FAA NOTAM → - HAZARDS6/8554 2026-07-26 12:00Z – 2026-08-10 03:00Z SFC–12,000 ft
16NM W MONTICELLO, UT, Sunday, July 26, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/9104 2026-07-27 16:25Z – 2026-07-28 03:00Z SFC–14,500 ft
14NM N LOS ALAMOS, NM, Monday, July 27, 2026 through Tuesday, July 28, 2026 UTC
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 26
- 1415 ft AGL at event
- 158 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPHX 162051Z COR 07020G29KT 10SM VCTS SCT034 BKN049CB BKN060 OVC130 26/21 A2997 RMK AO2 PK WND 04031/2040 WSHFT 1954 LTG DSNT ALQDS SLP130 VIS NW 3 OCNL LTGCGIC VC NW-N TS VC NW-N MOV N CB DSNT ALQDS 60015 T02560211 53003
Flight context
- AAL2058
- Wilmington Trust
- B738
- KMCI → KPHX
- 2026-07-27 22:15 UTC
- KPHX runway 26
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