AMX179 was operating from MMTJ to MMMX on 2026-07-18. SkyMeter detected a go-around at Licenciado Benito Juarez International Airport (MMMX) on runway 05R at 22:03 UTC. Trace data at the event: 8447 ft AGL, 185 kt GS. METAR at the time reported 20 kt wind, 19 kt crosswind component, 12,875 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/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/5889 2026-07-15 14:00Z – 2026-07-28 04:00Z SFC–11,000 ft
20NM NE NOGALES, AZ, Wednesday, July 15, 2026 through Tuesday, July 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/6155 2026-07-16 16:00Z – 2026-07-23 23:00Z SFC–1,500 ft
0NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6156 2026-07-16 16:09Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6157 2026-07-16 16:15Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM NW BOERNE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6158 2026-07-16 16:23Z – 2026-07-23 23:00Z SFC–1,500 ft
3NM SW UVALDE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6217 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM W INGRAM, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6218 2026-07-16 18:17Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM SE KERRVILLE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6219 2026-07-16 18:18Z – 2026-07-23 23:00Z SFC–1,500 ft
1NM NW BOERNE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6220 2026-07-16 18:19Z – 2026-07-23 23:00Z SFC–1,500 ft
3NM SW UVALDE, TX, Thursday, July 16, 2026 through Thursday, July 23, 2026 UTC
View FAA NOTAM → - HAZARDS6/6186 2026-07-17 13:00Z – 2026-07-30 03:00Z SFC–11,000 ft
21NM NE DOUGLAS, AZ, Friday, July 17, 2026 through Thursday, July 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/6528 2026-07-17 19:40Z – 2026-07-24 05:00Z SFC–1,500 ft
CRYSTAL CITY, TX, Friday, July 17, 2026 through Friday, July 24, 2026 UTC
View FAA NOTAM → - SECURITY6/6542 2026-07-18 06:00Z – 2026-07-19 13:00Z SFC–17,999 ft
Libby AAF, AZ, Friday, July 17, 2026 through Sunday, July 19, 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
- 8447 ft AGL at event
- 185 kt ground speed
- 0 fpm vertical
- 20 kt wind
- 19 kt crosswind component
- 12,875 m visibility
- MMMX 151850Z 33003KT 8SM BKN020 22/09 A3045 NOSIG RMK 8/100 HZY CI VSBY LWR SW W FRMG CB NE SW
Flight context
- AMX179
- B38M
- MMTJ → MMMX
- 2026-07-18 22:03 UTC
- MMMX runway 05R
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