VIV3206 was operating from MMVR to MMMY on 2026-07-20. SkyMeter detected a go-around at General Mariano Escobedo International Airport (MMMY) on runway 12 at 18:35 UTC. Trace data at the event: 2797 ft AGL, 153 kt GS. METAR at the time reported 4 kt wind, 1 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)- 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 → - HAZARDS6/6693 2026-07-18 20:01Z – 2026-07-23 05:00Z SFC–5,000 ft
BROWNSVILLE, TX, Saturday, July 18, 2026 through Thursday, July 23, 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
- 2797 ft AGL at event
- 153 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 1 kt crosswind component
- 12,875 m visibility
- MMMY 151240Z 06004KT 8SM BKN015 25/22 A3009 RMK 8/500
Flight context
- VIV3206
- A321
- MMVR → MMMY
- 2026-07-20 18:35 UTC
- MMMY runway 12
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