A2260/26 / notams.coredoes.dev

!! NOT FOR OPERATIONAL USE !! data may be stale, incomplete, or wrong

number	A2260/26 REPLACE
location	OIIX
begin	2026-10-11 11:58 UTC (22h ago)
end	2027-01-09 20:30 UTC (in 89d)
CADS id	5437704
CADS seq	13050808
CADS msg	NMS_ID_1791720214316000

raw text:

TEHRAN FIR RESUMED NORMAL OPERATION, OVERFLIGHT OPERATION IN 
TEHRAN FIR IS SUBJECT TO FOLLOWING CONDITIONS: 
- ATS SURVEILLANCE SERVICE WILL BE PROVIDED ABOVE FL285 SUBJECT TO 
  RADAR COVERAGE,
- NON ATS SURVEILLANCE SEPARATION MINIMA (50 NM) FOR TRAFFIC ON 
  SAME TRACK, SAME DIRECTION AND SAME LEVEL WILL BE APPLIED ON 
  THE FOLLOWING TRANSFER OF CONTROL POINTS: 
  IMLOT, GABKO, PATAT, ORSAR, DASUT, ELIDU, RAGAS, MIDSI, OBTAR, 
  ALSER, PATIR, NANPI, TULAX, PAXAT, RAGET, BOXIX, ALRAM, BONAM, 
  DASIS, AGINA, DULAV, MAGRI, PARSU, PAMTU, SOKAM AND RANRU,
- LARGER SEPARATION MAY BE APPLIED WITHIN TEHRAN FIR,
- INBOUND TRAFFIC SHALL CONTACT TEHRAN ACC 5 MIN PRIOR TO FIR 
  BOUNDARY FOR IDENTIFICATION,
- OUTBOUIND TRAFFIC SHALL ESTABLISH COMMUNICATION WITH NEXT 
  ACC 5 MIN PRIOR TO FIR BOUNDARY,
- FLIGHTS SHALL HAVE OPERATIONAL ACAS,
- FLIGHTS SHALL RETAIN THE LAST ASSIGNED SSR CODE, IF CODE HAS NOT 
  BEEN ASSIGNED, USE SQUAWK 2000 UNTIL FURTHER INSTRUCTION BY ACC.

icao text:

 A2260/26 NOTAMR A1306/26 Q)OIIX/QAFXX//E/000/999/ A)OIIX B)2610111158 C)2701092030EST E)TEHRAN FIR RESUMED NORMAL OPERATION, OVERFLIGHT OPERATION IN  TEHRAN FIR IS SUBJECT TO FOLLOWING CONDITIONS:  - ATS SURVEILLANCE SERVICE WILL BE PROVIDED ABOVE FL285 SUBJECT TO    RADAR COVERAGE, - NON ATS SURVEILLANCE SEPARATION MINIMA (50 NM) FOR TRAFFIC ON    SAME TRACK, SAME DIRECTION AND SAME LEVEL WILL BE APPLIED ON    THE FOLLOWING TRANSFER OF CONTROL POINTS:    IMLOT, GABKO, PATAT, ORSAR, DASUT, ELIDU, RAGAS, MIDSI, OBTAR,    ALSER, PATIR, NANPI, TULAX, PAXAT, RAGET, BOXIX, ALRAM, BONAM,    DASIS, AGINA, DULAV, MAGRI, PARSU, PAMTU, SOKAM AND RANRU, - LARGER SEPARATION MAY BE APPLIED WITHIN TEHRAN FIR, - INBOUND TRAFFIC SHALL CONTACT TEHRAN ACC 5 MIN PRIOR TO FIR    BOUNDARY FOR IDENTIFICATION, - OUTBOUIND TRAFFIC SHALL ESTABLISH COMMUNICATION WITH NEXT    ACC 5 MIN PRIOR TO FIR BOUNDARY, - FLIGHTS SHALL HAVE OPERATIONAL ACAS, - FLIGHTS SHALL RETAIN THE LAST ASSIGNED SSR CODE, IF CODE HAS NOT    BEEN ASSIGNED, USE SQUAWK 2000 UNTIL FURTHER INSTRUCTION BY ACC.

downloads:

raw AIXM 5.1 XML
GeoJSON not available (no coordinates)

!! NOT FOR OPERATIONAL USE !! data may be stale, incomplete, or wrong