Long landing rollout — VOI3047

MMTJ · 27

2026-08-08 07:13 UTC· MMTJ → MMTJ· A321

▶ Replay 📊 Analyse

VOI3047 was operating from MMTJ to MMTJ on 2026-08-08. SkyMeter detected a long landing rollout at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 27 at 07:13 UTC. Trace data at the event: 492 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 3 kt wind, 2 kt crosswind component, 11,265 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. 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/2553 2026-08-08 06:00Z – 2026-08-09 13:00Z SFC–17,999 ft

    Libby AAF, AZ, Friday, August 7, 2026 through Sunday, August 9, 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
  • 492 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 3 kt wind
  • 2 kt crosswind component
  • 11,265 m visibility
  • MMTJ 170640Z 24007KT 7SM OVC024 21/16 A3005 RMK 8/5// HZY

Flight context

  • VOI3047
  • A321
  • MMTJ → MMTJ
  • 2026-08-08 07:13 UTC
  • MMTJ runway 27

All events on this flight

Long landing rollout 07:13:42 UTC · MMTJ runway 27 · 492 ft AGL · 4 kt GS
Long landing rollout 07:13:42 UTC · MMTJ runway 27 · 492 ft AGL · 4 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