Diversion — AAL758
MMSM · 04C2026-02-26 21:50 UTC· MMMX → KCLT· WILMINGTON TRUST CO TRUSTEE· B38M
AAL758 (Wilmington Trust) was operating from MMMX to KCLT (Charlotte Douglas International Airport) on 2026-02-26. SkyMeter detected a diversion to Felipe Angeles International Airport (MMSM) on runway 04C at 21:50 UTC. Peak cruise altitude FL386, turnaround area near Saint Tammany, US. Approach stability score: 93/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 7 kt wind, 7 kt crosswind component, 8,047 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft
South Padre Island, TX, Tuesday, May 6, 2025 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 04C
- 7358 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 93/100
- 7 kt wind
- 7 kt crosswind component
- 8,047 m visibility
- MMSM 021546Z 35003KT 5SM SCT020 BKN200 17/15 A3027 RMK 8/508 HZY AC
Flight context
- AAL758
- Wilmington Trust
- B38M
- MMMX → KCLT
- 2026-02-26 21:50 UTC
- MMSM runway 04C
All events on this flight
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