VIV7400 was operating from MMTJ to MMMY on 2026-09-03. SkyMeter detected a go-around at General Mariano Escobedo International Airport (MMMY) on runway 12 at 18:40 UTC. Trace data at the event: 1702 ft AGL, 154 kt GS. METAR at the time reported 4 kt wind, 1 kt crosswind component, 11,265 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/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/9244 2026-08-30 20:00Z – 2026-09-06 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Sunday, August 30, 2026 through Sunday, September 6, 2026 UTC
View FAA NOTAM → - HAZARDS6/9262 2026-08-31 13:00Z – 2026-09-15 02:00Z SFC–6,000 ft
12NM NW ROCKSPRINGS, TX, Monday, August 31, 2026 through Tuesday, September 15, 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 12
- 1702 ft AGL at event
- 154 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
- 11,265 m visibility
- MMMY 160240Z 09015KT 7SM FEW200 31/21 A3001 RMK SLP144 52023 920 8/008 HZY ISOL AC
Flight context
- VIV7400
- A20N
- MMTJ → MMMY
- 2026-09-03 18:40 UTC
- MMMY runway 12
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