AMX421 was operating from KMIA to MMMX on 2026-07-12. SkyMeter detected a go-around at Licenciado Benito Juarez International Airport (MMMX) on runway 05R at 00:44 UTC. Trace data at the event: 8454 ft AGL, 198 kt GS. METAR at the time reported 15 kt wind, 7 kt crosswind component, 14,484 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/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/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft
Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local
View FAA NOTAM → - HAZARDS6/3381 2026-07-08 05:00Z – 2026-07-16 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Wednesday, July 8, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/3895 2026-07-08 13:50Z – 2026-07-16 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Wednesday, July 8, 2026 through Thursday, July 16, 2026 UTC
View FAA NOTAM → - HAZARDS6/3374 2026-07-09 13:00Z – 2026-07-15 05:00Z SFC–10,000 ft
BROWNSVILLE, TX, Thursday, July 9, 2026 through Wednesday, July 15, 2026 UTC
View FAA NOTAM → - SECURITY6/3226 2026-07-11 18:00Z – 2026-07-12 03:00Z SFC–3,000 ft
Miami, FL, Saturday, July 11, 2026 through Saturday, July 11, 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 05R
- 8454 ft AGL at event
- 198 kt ground speed
- 0 fpm vertical
- 15 kt wind
- 7 kt crosswind component
- 14,484 m visibility
- MMMX 171241Z 34008KT 9SM BKN020 16/11 A3044 NOSIG RMK 8/500 HZY ISOL AC AND CI
Flight context
- AMX421
- B39M
- KMIA → MMMX
- 2026-07-12 00:44 UTC
- MMMX runway 05R
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