Go-around — VOI5610
MMTJ · 272026-04-05 06:54 UTC· MMMY → MMTJ· WILMINGTON TRUST CO TRUSTEE· A320
VOI5610 (Wilmington Trust) was operating from MMMY to MMTJ on 2026-04-05. SkyMeter detected a go-around at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 27 at 06:54 UTC. Trace data at the event: 765 ft AGL, 144 kt GS. METAR at the time reported 0 kt wind, 9,656 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 →
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 27
- 765 ft AGL at event
- 144 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 9,656 m visibility
- MMTJ 211140Z 27003KT 6SM OVC018 20/16 A2997 RMK SLP150 57004 904 8/5// HZY
Flight context
- VOI5610
- Wilmington Trust
- A320
- MMMY → MMTJ
- 2026-04-05 06:54 UTC
- MMTJ runway 27
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