<AIXMBasicMessage gml:id="NMS_ID_1758719909152683"><gml:boundedBy xsi:nil="true"/><hasMember><event:Event gml:id="Event_1_1758719909152683"><gml:identifier codeSpace="urn:uuid:">16dd9178-e670-4248-a720-aa9bc7c5826e</gml:identifier><gml:boundedBy xsi:nil="true"/><event:timeSlice><event:EventTimeSlice gml:id="Event_TS_1_1758719909152683"><gml:validTime><gml:TimePeriod gml:id="Event_TS_TP_1_1758719909152683"><gml:beginPosition>2024-01-13T23:00:00.000Z</gml:beginPosition><gml:endPosition indeterminatePosition="unknown"/></gml:TimePeriod></gml:validTime><aixm:interpretation>BASELINE</aixm:interpretation><aixm:sequenceNumber>1</aixm:sequenceNumber><aixm:correctionNumber>0</aixm:correctionNumber><event:scenario>6000</event:scenario><event:textNOTAM><event:NOTAM gml:id="NOTAM_1_1758719909152683"><event:series>A</event:series><event:number>42</event:number><event:year>2024</event:year><event:type>N</event:type><event:issued>2024-01-12T17:56:00.000Z</event:issued><event:affectedFIR>PAZA</event:affectedFIR><event:selectionCode>QXXXX</event:selectionCode><event:minimumFL>180</event:minimumFL><event:maximumFL>600</event:maximumFL><event:location>ZAN</event:location><event:effectiveStart>202401132300</event:effectiveStart><event:effectiveEnd>PERM</event:effectiveEnd><event:text>ARCTIC CTA/FIR IS SUBJECT TO THE FOLLOWING MANDATORY
REQUIREMENTS: A. COMMUNICATIONS. 1. ALL FLTS, WITH THE EXCEPTION OF
THOSE ENTERING THE FIR EB OVER PILUN OR LISKI, MUST MAKE MANDATORY
POSITION REPORTS UPON ENTERING THE CTA/FIR VIA CPDLC OR GANDER HF
VOICE. PILUN AND LISKI TFC REPORT VIA VHF AS DIRECTED OR VIA CPDLC.
2. ALL FLTS MUST MAINTAIN A LISTENING WATCH ON THE CURRENT GANDER HF
RADIO FREQUENCY WHILE TRANSITING THE CTA/FIR UNLESS A SATISFACTORY
SELCAL CHECK HAS BEEN COMPLETED WITH GANDER RADIO.  B. ROUTING. 1.
FLTS ENTERING OR EXITING ANCHORAGE ARTCC FIR N OF 73N MUST FILE OVER
A NAMED FIR BOUNDARY POINT  2. PILUN. W OR EB FLTS FILE A POINT OVER
OR S OF 7230N14100W AND EB FLTS MUST ALSO FILE OVER OR N OF
7200N15700W. 3. LISKI. W OR EB FLTS MUST FILE OVER OR S OF TAYTA AND
EB FLTS MUST ALSO FILE OVER OR S OF 7100N15700W. QUESTIONS
CONCERNING THESE REQUIREMENTS MAY BE REFERRED TO ZAN TFC MANAGEMENT
AT 907-269-1108.</event:text><event:lowerLimit>FL180</event:lowerLimit><event:upperLimit>FL600</event:upperLimit><event:translation><event:NOTAMTranslation gml:id="NT02_1758719909152683"><event:type>OTHER:ICAO</event:type><event:formattedText><html:div xmlns:html="http://www.w3.org/1999/xhtml">&lt;pre&gt;
A0042/24 NOTAMN
Q) PAZA/QXXXX////180/600/
A) PAZA
B) 2401132300
C) PERM
E) ARCTIC CTA/FIR IS SUBJECT TO THE FOLLOWING MANDATORY
REQUIREMENTS: A. COMMUNICATIONS. 1. ALL FLTS, WITH THE EXCEPTION OF
THOSE ENTERING THE FIR EB OVER PILUN OR LISKI, MUST MAKE MANDATORY
POSITION REPORTS UPON ENTERING THE CTA/FIR VIA CPDLC OR GANDER HF
VOICE. PILUN AND LISKI TFC REPORT VIA VHF AS DIRECTED OR VIA CPDLC.
2. ALL FLTS MUST MAINTAIN A LISTENING WATCH ON THE CURRENT GANDER HF
RADIO FREQUENCY WHILE TRANSITING THE CTA/FIR UNLESS A SATISFACTORY
SELCAL CHECK HAS BEEN COMPLETED WITH GANDER RADIO.  B. ROUTING. 1.
FLTS ENTERING OR EXITING ANCHORAGE ARTCC FIR N OF 73N MUST FILE OVER
A NAMED FIR BOUNDARY POINT  2. PILUN. W OR EB FLTS FILE A POINT OVER
OR S OF 7230N14100W AND EB FLTS MUST ALSO FILE OVER OR N OF
7200N15700W. 3. LISKI. W OR EB FLTS MUST FILE OVER OR S OF TAYTA AND
EB FLTS MUST ALSO FILE OVER OR S OF 7100N15700W. QUESTIONS
CONCERNING THESE REQUIREMENTS MAY BE REFERRED TO ZAN TFC MANAGEMENT
AT 907-269-1108.
F) FL180
G) FL600
&lt;/pre&gt;</html:div></event:formattedText></event:NOTAMTranslation></event:translation></event:NOTAM></event:textNOTAM><event:extension><fnse:EventExtension gml:id="ext_01_1758719909152683"><fnse:classification>INTL</fnse:classification><fnse:accountId>PAZA</fnse:accountId><fnse:airportname>ANCHORAGE (ARTCC),AK.</fnse:airportname><fnse:originID>PAZA</fnse:originID><fnse:lastUpdated>2024-01-12T17:56:00.000Z</fnse:lastUpdated><fnse:icaoLocation>PAZA</fnse:icaoLocation></fnse:EventExtension></event:extension></event:EventTimeSlice></event:timeSlice></event:Event></hasMember></AIXMBasicMessage>