Long landing rollout — GTI8920

SAEZ · 11

2026-04-02 19:21 UTC· MM28 SAEZ· ATLAS AIR INC· B744

GTI8920 (Atlas AIR) was operating from MM28 to SAEZ on 2026-04-02. SkyMeter detected a long landing rollout at Ministro Pistarini International Airport (SAEZ) on runway 11 at 19:21 UTC. Trace data at the event: 49 ft AGL, 12 kt GS, 0 fpm vertical. Approach stability score: 82/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 2 kt wind, 1 kt crosswind component, 9,994 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)
  • HAZARDS6/2698 2026-01-19 09:00Z – 2026-12-18 21:00Z SFC–5,000 ft

    VIEQUES, PR, Monday, January 19, 2026 through Friday, December 18, 2026 UTC

    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 11
  • 49 ft AGL at event
  • 12 kt ground speed
  • 0 fpm vertical
  • Approach stability 82/100
  • 2 kt wind
  • 1 kt crosswind component
  • 9,994 m visibility
  • SAEZ 221200Z 25008KT 9999 FEW017 08/03 Q1023 NOSIG

Flight context

  • GTI8920
  • Atlas AIR
  • B744
  • MM28 → SAEZ
  • 2026-04-02 19:21 UTC
  • SAEZ runway 11

All events on this flight

Long landing rollout 19:21:27 UTC · SAEZ runway 11 · 49 ft AGL · 12 kt GS
Long landing rollout 19:21:27 UTC · SAEZ runway 11 · 49 ft AGL · 12 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· SAEZ