AMX174 was operating from MMMX to MMTJ on 2026-07-15. SkyMeter detected a go-around at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 09 at 19:23 UTC. Trace data at the event: 1070 ft AGL, 183 kt GS. METAR at the time reported 11 kt wind, 2 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)- 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 →
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
- 1070 ft AGL at event
- 183 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- COR MMTJ 151942Z 28014KT 10SM BKN200 26/18 A3010 RMK 8/009 TCU E
Flight context
- AMX174
- B38M
- MMMX → MMTJ
- 2026-07-15 19:23 UTC
- MMTJ runway 09
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