Unstable approach — XBAEX

XBAEX was inbound to MMAN on 2026-07-19. SkyMeter detected a low approach-stability score at Del Norte International Airport (MMAN) on runway 20 at 00:54 UTC. Trace data at the event: 2555 ft AGL, 162 kt GS. Approach stability score: 41/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 14 kt wind, 14 kt crosswind component, 16,093 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.

• 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 →
• HAZARDS6/6693 2026-07-18 20:01Z – 2026-07-23 05:00Z SFC–5,000 ft

  BROWNSVILLE, TX, Saturday, July 18, 2026 through Thursday, July 23, 2026 UTC

  View FAA NOTAM →
• SPACE OPERATIONS6/5295 2026-07-18 22:15Z – 2026-07-19 00:15Z SFC–999 ft

  Starbase, TX, Saturday, July 18, 2026 through Saturday, July 18, 2026 Local

  View FAA NOTAM →
• SPACE OPERATIONS6/5369 2026-07-18 22:30Z – 2026-07-19 00:54Z SFC–999 ft

  Starbase, TX, Saturday, July 18, 2026 through Saturday, July 18, 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.

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