Go-around — AAL3086
KPHX · 262026-06-12 15:53 UTC· KBNA → KPHX· BANK OF UTAH TRUSTEE· A321
AAL3086 (Bank of Utah) was operating from KBNA to KPHX on 2026-06-12. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 26 at 15:53 UTC. Trace data at the event: 2324 ft AGL, 148 kt GS. METAR at the time reported 5 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/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z
TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Stillwater, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NORMAN, OK, 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/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
OKLAHOMA CITY, OK, 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/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
Tulsa, OK, 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/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 → - HAZARDS6/6780 2026-06-10 13:00Z – 2026-06-22 04:00Z SFC–10,000 ft
14NM E FLAGSTAFF, AZ, Wednesday, June 10, 2026 through Monday, June 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7455 2026-06-11 05:00Z – 2026-06-25 05:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Thursday, June 11, 2026 through Thursday, June 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/7863 2026-06-12 14:00Z – 2026-06-24 05:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Friday, June 12, 2026 through Wednesday, June 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/7894 2026-06-12 14:43Z – 2026-06-25 04:00Z SFC–14,000 ft
80NM N SILVER CITY, NM, Friday, June 12, 2026 through Thursday, June 25, 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
- 2324 ft AGL at event
- 148 kt ground speed
- 0 fpm vertical
- 5 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KPHX 181051Z 09004KT 10SM CLR 27/21 A2994 RMK AO2 SLP122 T02670206 $
Flight context
- AAL3086
- Bank of Utah
- A321
- KBNA → KPHX
- 2026-06-12 15:53 UTC
- KPHX runway 26
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