Go-around — AAL3057

AAL3057 (Wilmington Trust) was operating from KCLT to KPHX on 2026-08-30. SkyMeter detected a go-around at Phoenix Sky Harbor International Airport (KPHX) on runway 26 at 04:23 UTC. Trace data at the event: 1937 ft AGL, 191 kt GS. METAR at the time reported 17 kt wind, 17 kt crosswind component, 2,414 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.

• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft

  26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7422 2026-08-24 14:30Z – 2026-09-08 05:00Z SFC–12,500 ft

  26NM NE RUIDOSO, NM, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft

  21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8069 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–14,000 ft

  26NM SE ALBUQUERQUE, NM, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8445 2026-08-26 20:55Z – 2026-09-09 02:00Z SFC–5,500 ft

  1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8590 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft

  Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local

  View FAA NOTAM →
• HAZARDS6/8684 2026-08-28 14:00Z – 2026-09-03 02:30Z SFC–14,000 ft

  28NM SE ALBUQUERQUE, NM, Friday, August 28, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8829 2026-08-28 15:45Z – 2026-09-11 02:00Z SFC–5,500 ft

  4NM NW MINERAL WELLS, TX, Friday, August 28, 2026 through Friday, September 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8888 2026-08-28 23:05Z – 2026-09-12 03:00Z SFC–14,000 ft

  28NM SE ALBUQUERQUE, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8889 2026-08-28 23:25Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Friday, August 28, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9082 2026-08-29 13:00Z – 2026-09-12 04:00Z SFC–13,500 ft

  15NM SW LAS VEGAS, NM, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9129 2026-08-29 15:15Z – 2026-09-12 02:00Z SFC–5,500 ft

  4NM NW MINERAL WELLS, TX, Saturday, August 29, 2026 through Saturday, September 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9134 2026-08-29 15:46Z – 2026-08-31 03:00Z SFC–13,000 ft

  42NM SE SHOW LOW, AZ, Saturday, August 29, 2026 through Monday, August 31, 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.

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