Unstable approach — AMX030

SAEZ · 35

2026-09-02 02:02 UTC· MMMX → SAEZ· UMB BANK NA TRUSTEE· B789

▶ Replay 📊 Analyse

AMX030 (UMB Bank NA) was operating from MMMX to SAEZ on 2026-09-02. SkyMeter detected a low approach-stability score at Ministro Pistarini International Airport (SAEZ) on runway 35 at 02:02 UTC. Trace data at the event: 1018 ft AGL, 150 kt GS. METAR at the time reported 9 kt wind, 9 kt crosswind component, 9,994 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. 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 35
  • 1018 ft AGL at event
  • 150 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 9 kt crosswind component
  • 9,994 m visibility
  • SAEZ 161800Z 07011KT CAVOK 14/03 Q1023 NOSIG

Flight context

  • AMX030
  • UMB Bank NA
  • B789
  • MMMX → SAEZ
  • 2026-09-02 02:02 UTC
  • SAEZ runway 35

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