Diversion — VOI3181

1CA6 · 15

2026-03-03 17:28 UTC· MMHO → 1CA6· WELLS FARGO TRUST CO NA TRUSTEE· A320

VOI3181 (Wells Fargo Trust Co NA) was operating from MMHO to MMTJ (General Abelardo L. Rodríguez International Airport) on 2026-03-03. SkyMeter detected a diversion to On the Rocks Airport (1CA6) on runway 15 at 17:28 UTC. Peak cruise altitude FL372, turnaround area near Puerto Peñasco, MX. Approach stability score: 30/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 1 kt wind, 1 kt crosswind component. 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 15
  • 0 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 30/100
  • 1 kt wind
  • 1 kt crosswind component

Flight context

  • VOI3181
  • Wells Fargo Trust Co NA
  • A320
  • MMHO → 1CA6
  • 2026-03-03 17:28 UTC
  • 1CA6 runway 15

All events on this flight

Diversion 17:28:32 UTC · 1CA6 runway 15 · 0 ft AGL · 120 kt GS
Unstable approach 17:26:33 UTC · 1CA6 runway 33 · 3,771 ft AGL · 197 kt GS
Diversion 17:28:32 UTC · 1CA6 runway 15 · 0 ft AGL · 120 kt GS
Unstable approach 17:26:33 UTC · 1CA6 runway 33 · 3,771 ft AGL · 197 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· 1CA6