VOI7731 was operating from KORD to MMLO (Del Bajío International Airport) on 2026-08-06. SkyMeter detected a diversion to General Mariano Escobedo International Airport (MMMY) on runway 12 at 13:33 UTC. Peak cruise altitude FL384, turnaround area near Marion County, US. Approach stability score: 69/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 0 kt wind, 11,265 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 Local
View FAA NOTAM → - 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/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 →
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
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 69/100
- 0 kt wind
- 0 kt crosswind component
- 11,265 m visibility
- MMMY 161741Z 10011KT 7SM FEW020 BKN200 32/20 A3015 RMK SLP188 52002 931 8/508 HZY
Flight context
- VOI7731
- A320
- KORD → MMMY
- 2026-08-06 13:33 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