Go-around — AAL3172
KPHX · 262026-08-14 03:29 UTC· KMIA → KPHX· WILMINGTON TRUST CO TRUSTEE· B738
AAL3172 (Wilmington Trust) was operating from KMIA to KPHX on 2026-08-14. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 26 at 03:29 UTC. Trace data at the event: 1530 ft AGL, 156 kt GS. METAR at the time reported 3 kt wind, 3 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)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft
Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local
View FAA NOTAM → - SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft
Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local
View FAA NOTAM → - SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft
SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - HAZARDS6/0749 2026-08-01 15:00Z – 2026-08-14 03:00Z SFC–13,000 ft
13NM S SAFFORD, AZ, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/2568 2026-08-06 14:22Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2575 2026-08-06 15:06Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/2747 2026-08-07 12:00Z – 2026-08-14 03:00Z SFC–14,000 ft
24NM SE ALBUQUERQUE, NM, Friday, August 7, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - HAZARDS6/3249 2026-08-10 15:17Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/3405 2026-08-10 16:03Z – 2026-08-20 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Monday, August 10, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3199 2026-08-12 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 12, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - SECURITY6/3974 2026-08-13 05:00Z – 2026-08-15 09:30Z SFC–17,999 ft
Macon, GA, Thursday, August 13, 2026 through Saturday, August 15, 2026 Local
View FAA NOTAM → - HAZARDS6/4962 2026-08-13 18:15Z – 2026-08-20 18:00Z SFC–2,000 ft
YOUNGSPORT, TX, Thursday, August 13, 2026 through Thursday, August 20, 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
- 1530 ft AGL at event
- 156 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KPHX 161451Z 13007KT 10SM SCT080 SCT100 SCT170 BKN230 32/20 A2994 RMK AO2 SLP119 TCU DSNT W-N T03170200 53020 PNO $
Flight context
- AAL3172
- Wilmington Trust
- B738
- KMIA → KPHX
- 2026-08-14 03:29 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