THY182 was operating from MMMX to MMUN (Cancún International Airport) on 2026-08-05. SkyMeter detected a diversion to Istanbul Airport (LTFM) on runway 34L at 07:04 UTC. Peak cruise altitude FL393, turnaround area near Lajes das Flores, PT. METAR at the time reported 0 kt wind, 9,994 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft
NEW YORK, NY, Monday, October 20, 2025 through Tuesday, October 20, 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 → - SECURITY6/4348 2026-03-08 07:00Z – 2026-11-01 06:59Z SFC–2,400 ft
GRAND FORKS AFB, ND, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM → - SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft
Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local
View FAA NOTAM → - SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft
St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 2026 Local
View FAA NOTAM → - HAZARDS6/6777 2026-07-19 19:05Z – 2026-08-20 07:00Z SFC–7,000 ft
10NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - HAZARDS6/6779 2026-07-19 19:09Z – 2026-08-20 07:00Z SFC–7,000 ft
20NM N ELY, MN, Sunday, July 19, 2026 through Thursday, August 20, 2026 UTC
View FAA NOTAM → - SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - HAZARDS6/1033 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft
25NM NW ELY, MN, Monday, August 3, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/1034 2026-08-03 10:00Z – 2026-08-10 02:00Z SFC–7,000 ft
13NM N ELY, MN, Monday, August 3, 2026 through Monday, August 10, 2026 UTC
View FAA NOTAM → - SECURITY6/0929 2026-08-03 12:30Z – 2026-08-08 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 3, 2026 through Saturday, August 8, 2026 Local
View FAA NOTAM → - VIP6/1212 2026-08-03 23:30Z – 2026-08-04 23:30Z SFC–4,999 ft
Middleburg, VA, Monday, August 3, 2026 through Tuesday, August 4, 2026 Local
View FAA NOTAM → - VIP6/0922 2026-08-04 15:30Z – 2026-08-04 20:30Z SFC–4,999 ft
Brownsville, TX, Tuesday, August 4, 2026 Local
View FAA NOTAM → - AIR SHOWS/SPORTS6/9616 2026-08-04 16:30Z – 2026-08-04 18:30Z SFC–16,000 ft
Rochester, NY, Tuesday, August 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/1483 2026-08-04 20:00Z – 2026-08-04 20:15Z SFC–7,500 ft
DEER RIVER, MN, Tuesday, August 4, 2026 UTC
View FAA NOTAM → - SECURITY6/1231 2026-08-05 05:00Z – 2026-08-07 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 5, 2026 through Friday, August 7, 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.
Pilot review data
- Runway 34L
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 9,994 m visibility
- LTFM 041150Z 04016KT 9999 BKN022 25/18 Q1016 NOSIG
Flight context
- THY182
- B789
- MMMX → LTFM
- 2026-08-05 07:04 UTC
- LTFM runway 34L
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