Long landing rollout — VOI3352

MMTJ · 27

2026-08-22 15:21 UTC· A320

VOI3352 was inbound to MMTJ on 2026-08-22. SkyMeter detected a long landing rollout at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 27 at 15:21 UTC. Trace data at the event: 494 ft AGL, 16 kt GS, 0 fpm vertical. Approach stability score: 63/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 4 kt wind, 1 kt crosswind component, 16,093 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/6976 2026-08-22 06:00Z – 2026-08-23 13:00Z SFC–17,999 ft

    Libby AAF, AZ, Friday, August 21, 2026 through Sunday, August 23, 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
  • 494 ft AGL at event
  • 16 kt ground speed
  • 0 fpm vertical
  • Approach stability 63/100
  • 4 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • MMTJ 170040Z 26007KT 10SM FEW015 23/15 A2999 RMK 8/500 HZY

Flight context

  • VOI3352
  • A320
  • 2026-08-22 15:21 UTC
  • MMTJ runway 27

All events on this flight

Long landing rollout 15:21:57 UTC · MMTJ runway 27 · 494 ft AGL · 16 kt GS
Long landing rollout 15:21:57 UTC · MMTJ runway 27 · 494 ft AGL · 16 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