Long landing rollout — AMX186

MMTJ · 27

2026-08-10 06:07 UTC· MMMX → MMTJ· B738

▶ Replay 📊 Analyse

AMX186 was operating from MMMX to MMTJ on 2026-08-10. SkyMeter detected a long landing rollout at General Abelardo L. Rodríguez International Airport (MMTJ) on runway 27 at 06:07 UTC. Trace data at the event: 479 ft AGL, 4 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 1 kt crosswind component, 12,875 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/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
  • 479 ft AGL at event
  • 4 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 1 kt crosswind component
  • 12,875 m visibility
  • MMTJ 161453Z 24005KT 8SM FEW020 OVC025 20/16 A3002 RMK SLP168 52014 919 8/5// BINOVC HZY

Flight context

  • AMX186
  • B738
  • MMMX → MMTJ
  • 2026-08-10 06:07 UTC
  • MMTJ runway 27

All events on this flight

Long landing rollout 06:07:26 UTC · MMTJ runway 27 · 479 ft AGL · 4 kt GS
Long landing rollout 06:07:26 UTC · MMTJ runway 27 · 479 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