Return to field — VOI3201

MMTJ · 09

2026-03-22 08:54 UTC· MMTJ → MMTJ· BANK OF UTAH TRUSTEE· A320

▶ Replay 📊 Analyse

VOI3201 (Bank of Utah) was operating from MMTJ to MMTJ (General Abelardo L. Rodríguez International Airport) on 2026-03-22. SkyMeter detected a return to field at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 09 at 08:54 UTC. Peak cruise altitude FL388, turnaround area near La Libertad, MX. 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, 9,656 m visibility. 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 →

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
  • 38825 ft AGL at event
  • 463 kt ground speed
  • 0 fpm vertical
  • Approach stability 69/100
  • 0 kt wind
  • 0 kt crosswind component
  • 9,656 m visibility
  • METAR MMTJ 231140Z 00000KT 6SM SKC 17/15 A2986 RMK SLP118 57006 975 HZY ST W S

Flight context

  • VOI3201
  • Bank of Utah
  • A320
  • MMTJ → MMTJ
  • 2026-03-22 08:54 UTC
  • MMTJ runway 09

All events on this flight

Return to field 08:54:47 UTC · MMTJ runway 09 · 38,825 ft AGL · 463 kt GS
Long landing rollout 14:46:28 UTC · MMTJ runway 27 · 492 ft AGL · 11 kt GS
Long landing rollout 14:46:28 UTC · MMTJ runway 27 · 492 ft AGL · 11 kt GS

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

SkyMeter · trace data observed via ADS-B· MMTJ