Go-around — AAL3055

KMIA · 09

2026-06-05 13:32 UTC· KDFW KMIA· AMERICAN AIRLINES INC· A321

AAL3055 (American Airlines) was operating from KDFW to KMIA on 2026-06-05. SkyMeter detected a go-around at Miami International Airport (KMIA) on runway 09 at 13:32 UTC. Trace data at the event: 1879 ft AGL, 138 kt GS. METAR at the time reported 10 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)
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/2644 2026-05-27 11:00Z – 2026-06-12 22:00Z SFC–400 ft

    Brunswick, GA, Wednesday, May 27, 2026 through Friday, June 12, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    TAMPA, FL, 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/4059 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4068 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4380 2026-06-01 13:00Z – 2026-06-06 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, June 1, 2026 through Saturday, June 6, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft

    22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC

    View FAA NOTAM →
  • SPACE OPERATIONS6/4176 2026-06-05 07:08Z – 2026-06-05 12:00Z SFC–180 ft

    Cape Canaveral, FL, Friday, June 5, 2026 Local

    View FAA NOTAM →
  • SPACE OPERATIONS6/4178 2026-06-05 07:08Z – 2026-06-05 12:00Z SFC–180 ft

    Cape Canaveral, FL, Friday, June 5, 2026 Local

    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 09
  • 1879 ft AGL at event
  • 138 kt ground speed
  • 0 fpm vertical
  • 10 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KMIA 181553Z 10013G18KT 10SM TS SCT020CB BKN035 BKN250 31/24 A3004 RMK AO2 TSB42 SLP172 OCNL LTGICCG NE-SE TS NE-SE MOV W T03110239

Flight context

  • AAL3055
  • American Airlines
  • A321
  • KDFW → KMIA
  • 2026-06-05 13:32 UTC
  • KMIA runway 09

All events on this flight

Go-around 13:32:31 UTC · KMIA runway 09 · 1,879 ft AGL · 138 kt GS
Go-around 13:32:31 UTC · KMIA runway 09 · 1,879 ft AGL · 138 kt GS

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

SkyMeter · trace data observed via ADS-B· KMIA