Long landing rollout — AMX423

MMJC · 04

2026-04-30 21:51 UTC· KMIA MMJC· B738

AMX423 was operating from KMIA to MMJC on 2026-04-30. SkyMeter detected a long landing rollout at Atizapan de Zaragoza Airport (MMJC) on runway 04 at 21:51 UTC. Trace data at the event: 7319 ft AGL, 16 kt GS. METAR at the time reported 2 kt wind, 2 kt crosswind component. 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)
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 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 04
  • 7319 ft AGL at event
  • 16 kt ground speed
  • 0 fpm vertical
  • 2 kt wind
  • 2 kt crosswind component

Flight context

  • AMX423
  • B738
  • KMIA → MMJC
  • 2026-04-30 21:51 UTC
  • MMJC runway 04

All events on this flight

Long landing rollout 21:51:31 UTC · MMJC runway 04 · 7,319 ft AGL · 16 kt GS
Long landing rollout 21:51:31 UTC · MMJC runway 04 · 7,319 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· MMJC