Anchorage Radio Standard Operating Guidelines

Anchorage Radio Standard Operating Guidelines Anchorage ARTCC Effective: 1-October-2011 Created by: Kenneth Haught, 1067681 Anchorage Radio Standard Operating Guidelines Page 1 of 13

Contents Mission Statement Training Goals Position Details Airspace Definition Controller Requirements Applying for Certification Guiding Principles Network Regulations References Training Syllabus Approvals Letters of Agreement p3 p3 p3 p4 p5 p6 p7 p8 p8 p9 p10 p11 Anchorage Radio Standard Operating Guidelines Page 2 of 13

Mission Statement Welcome to the Anchorage Radio Flight Service Station (ZAN_FSS) position. This position is a non-radar position approved by the VATSIM Executive Committee, which requires special authorization under the regulations set forth in the Global Ratings Policy v2, located in the Executive Committee section of the VATSIM network. This designated area is classes as a Special Center and requires a minimum Controller1 rating to begin training. Further, the management of Anchorage ARTCC have set a minimum 50 hour minimum controlling time on a normal radar enroute position prior to accepting candidates for Oceanic Airspace (OCA) training. This can be waived in special circumstances by the Air Traffic Manager or his designee. The goal of this document is to provide you with the applicable procedures, policies, and information necessary to meet both VATSIM set goals for the airspace, as well as ensure that we continue to provide the highest quality controllers that is possible. You may find the new information to be challenging, as it requires a drastic change from the normal network center position that you have worked before. If you have any questions you may feel free to address them via email to the current Air Traffic Manager, which can be found on the Anchorage ARTCC website. Training Goals It is the goal of the OCA training department to provide all candidates with a concise and information rich training experience while ensuring they develop the necessary critical thinking skills required for a non-radar position. While working non-radar, controllers must at all times remain aware of time-based separation standards that far exceed those of a radar controlled airspace. Also complicating matters is the fact that typical radar services are not available to the controller, requiring the ability to accurately document and process written and verbal position reports from pilots. A large amount of patience is also expected from these controllers, due to the unfamiliarity of procedures typically encountered with VATSIM pilots in this area. In the following document you will find references to many sources, including FAA Order 7110.65 (version T is current as of this writing), the VATSIM Code of Conduct, VATSIM Code of Regulations, and miscellaneous ARTCC documents. At the end of this document you will find a list of these documents and resources made available for easy reference. Position Details Login Callsign Radio Name Frequency Voice Channel ZAN_FSS Anchorage Radio 127.55 rw.liveatc.net/zan_fss Anchorage Radio Standard Operating Guidelines Page 3 of 13

Airspace Definition The Anchorage Radio (ZAN_FSS) airspace currently consists of the airspace found east of FUKUOKA (RJDG) FIR, south of PETOPAVLOVSK-KAMCHATSKY (UHPP) FIR, north of OAKLAND OCEANIC (ZAK) ARTCC,and west of the 180 th parallel. It is shown as an image above. The vertical limits are defined as FL290 to FL600 inclusive. Anchorage Radio Standard Operating Guidelines Page 4 of 13

Controller Requirements The following requirements are set forth as minimums for controllers wishing to obtain a Special Center authorization for the Anchorage Flight Service Station position. All controllers who do not meet the following minimum requirements (exception item 3) shall be denied status until such time as they have corrected the issue. Merely meeting the minimum standards does NOT guarantee acceptance and certification to work the position. Final approval is made based on the applicants demonstrated abilities to correctly work the position with live VATSIM traffic to outlined competencies. The following requirements are set forth: 1. All applicants MUST currently possess a Controller1 rating or higher. 2. All Applicants MUST be a member in good standing of their current ARTCC, 1. This is defined as no outstanding disciplinary issues, and 2. currently meet or exceed the VATSIM EC policy for visiting or transferring controllers. 3. All applicants shall show (via the VATSIM STATS center) a minimum 50 hours of Enroute control time. 1. This is defined as a position ending in either _CTR or _FSS. 4. Applicants must speak and write basic English. 5. Applicants shall have sufficient experience with their preferred controller client. 1. At this time Anchorage Radio sector files are only available in.sct2 format for VRC. Persons wishing to use Euroscope do so on their own knowledge and ability as NO training or assistance will be provided by the ARTCC staff. Anchorage Radio Standard Operating Guidelines Page 5 of 13

Applying for Certification Persons meeting the above criteria who wish to apply for certification shall petition the Anchorage Air Traffic Manager. This should be done via email, and should include the following information: Applicant Name, VATSIM Controller ID (CID), Current VATSIM Rating, Current VATSIM FIR/ARTCC, Current EMAIL (should match your VATSIM email), Prior experience with non-radar or procedural airspace, Contact information for two (2) staff references (at least one must be your current ATM/DATM/TA). Once an application is received the applicant will be issued a written exam via the VATUSA Exam Center. The exam will be based on VATSIM, FAA, and local policies and practices and requires a minimum score of 80% for further consideration. If applicant is not successful at the exam at that time a thirty (30) day waiting period is imposed and a letter of intent (stating that the applicant is still interested in the OCA position) shall be submitted via email to the Anchorage Air Traffic Manager. If no such letter is received within 40 days of the failed exam attempt the applicants information shall be purged, and a complete application required should further interest be shown. On successful completion of the exam the applicants references will be contacted for training records and verification of applicant information. This process shall take no more then 10 days from completion of the exam, during which time the applicant should continue to study the available reference material in anticipation of their practical test/training period. Within forty-eight (48) hours of being accepted to the OCA training program they will be added to the Anchorage website in a dedicated OCA roster. At that time they may begin requesting training through the established website training system. Further action shall proceed via the Training Syllabus below. Anchorage Radio Standard Operating Guidelines Page 6 of 13

Guiding Principles The following principles shall serve as a general overview of operations within the designated airspace. All traffic controlled in the OCA shall be treated as if they are not visible on the client screen After some experience is gained this is possible by setting display filters and/or radar modes to hide most or all of the information. Controllers shall at all times be aware of separation standards as outlined in FAA Order 7110.65. This can be found in Chapter 8, section 9. In general the following apply. Lateral separation 30nm Vertical separation 1,000ft Controllers should keep in mind that although we strive for the most realistic Oceanic experience possible for both the controller and the pilot, certain limitations must be taken into consideration based on Network practices and policies. Due to this: All controllers shall at all times be prepared to offer services in text-only format should such be requested by the pilot. It is recommended that controllers become familiar with, and comfortable with, the OCA alias file for VRC. This will allow them to more easily process text requests and instructions than typing each item out manually. Please see the OCA files provided on the forums for this information. Controllers operating in the Alaska FSS area should keep in mind that due to server limitations it is necessary to keep open two (2) VRC windows to allow reception of any available ANC_CTR position and messages. For information on how to achieve this ask your OCA Instructor or Mentor All controllers shall take care not to set their visibility area in such as way as to cover high-traffic areas, specifically those areas of the western US coast. Modification of the approved OCA sector file is not permitted without express permission of the Anchorage Air Traffic Manager. Controllers should keep in mind that although the available information for pilots is abundant, many pilots have no experience with non-radar procedures. Due to this please exercise the utmost patience with members who do not know current procedures. All available tools should be used as needed, including use of a network Supervisor if necessary, however education should be used in preference to disciplinary actions. Anchorage Radio Standard Operating Guidelines Page 7 of 13

Network Regulations The following specific regulations apply to use of the FSS position and the ZAN_FSS callsign on the VATSIM network. For more regulations please see the appropriate VATSIM documents. VATSIM Code of Conduct Section A8(a) Except as provided for by part (b) of this section, a member is permitted to make only one connection at any one time under his or her account number (CID) to the VATSIM.net network. Multiple connections, either as a pilot, controller, or a combination of the two are not permitted. Section A8(b) does not apply for the ZAN_FSS position. Section C8 Voice is the preferred method of communication on VATSIM. However, not all pilots use voice to communicate with ATC. When using VATSIM, a controller must at all times be prepared to provide text-based air traffic control services to a pilot. Controllers must never restrict themselves to only working with voice capable pilots. Section C9 Controllers should not carry on private conversations between themselves, pilots, or other individuals on the active communication frequency, the ATC channel, or on the guard frequency (121.50). This interferes with providing ATC services to other pilots. The Guard frequency should only be utilized in cases of emergency and under no other circumstances. Per VATUSA General Division Policy, Section 2 the use of guard shall be prohibited at all times. Controllers found using this frequency shall have their Special Center authorization immediately revoked. References FAA Order 7110.65 http://www.faa.gov/documentlibrary/media/order/atc.pdf VATSIM Code of Conduct http://www.vatsim.net/network/docs/coc/ VATSIM Global Ratings Policy Document link not available. Available from this link. VATUSA General Division Policy http://www.vatusa.net/docs/vatusa_gen_div_policy.pdf Anchorage Radio Standard Operating Guidelines Page 8 of 13

Training Syllabus The following syllabus is set forth for training operations in the designated airspace. Exams A written exam consisting of material available in the FAA Order 7110.65, VATSIM Code of Conduct, and local policies shall be completed prior to any live training with an OCA Instructor or Mentor. A minimum score of 80% shall be considered a passing score. A practical OTS type exam will be conducted on the live VATSIM servers prior to the controller receiving authorization to work the designated airspace without an OCA Instructor or Mentor present. All students should be prepared for their first training session with VRC correctly configured, including the OCA sector and alias files loaded. Use of a POF file is optional, however to avoid client errors it is recommended to have one loaded. Client training will be limited to assistance with visibility settings and area specific tasks. Any questions regarding procedures or policies for the OCA airspace should be addressed to your OCA Instructor or Mentor during the session. You can expect 2-3 sessions of roughly 2 hours each prior to receiving your OCA practical exam. All practical exams shall be conducted by an OCA Instructor and will be carried out on the live VATSIM servers. A subjective grading system is used, with key points outlined below. Key Knowledge Points Be able to explain the key difference between procedural (i.e. OCA) airspace and that which is radar controlled. Application of basic separation standards as set forth in Guiding Principles above. Implications and procedures associated with connecting _FSS call-sign. Basic explanation and use of the Selective Calling (SELCAL) feature of VRC. Explain and demonstrate correct position report phraseology and formatting. Effective management of communication frequencies. Standard coordination with surrounding control areas (both procedural and radar). Associated network regulations and guidelines regarding controller activity. Anchorage Radio Standard Operating Guidelines Page 9 of 13

Also evaluated is the applicants ability to handle various traffic workloads and situations. All students, during the first training session, should expect a brief overview of the above topics from their OCA Instructor or Mentor prior to connecting to the servers. During the course of the training sessions the goal will be to positively reinforce the applicable policies and procedures while evaluating the students grasp of the subject material. Once the student has shown sufficient mastery of the subject material the OCA Mentor/Instructor should advise the student that they are due for their 'OTS' exam. At this time it is recommended that any final questions be asked by the student, as operational answers should not be given during the exam unless absolutely necessary. Plan on a minimum two (2) hour session for the OTS to allow for sufficient traffic opportunities, although a longer session is advised if traffic conditions are not optimal. If necessary a separate session can be scheduled to conduct the exam. During the exam the student should demonstrate the key knowledge points as outlined above, in addition to general controller disciple and professionalism. Any minor issues should be noted by the OCA Instructor/Mentor on the final training note for review. Major issues should be immediately addressed with the student, continued repetition of these events (or general lack of competency on the subject matters) should be cause for termination of the exam and referral to the Air Traffic Manager for review. All exam results shall be forwarded to the Air Traffic Manager for final review before OCA certification is granted. Approvals Local Kenneth Haught, Anchorage Air Traffic Manager VATUSA Tom Seeley, Western Region Air Traffic Director Anchorage Radio Standard Operating Guidelines Page 10 of 13

Letters of Agreement The following Letters of Agreement are set forth between Anchorage Radio (FSS) and the respective ARTCC/FIR managements. Anchorage ARTCC The following common procedures are defined for operations between FSS and Anchorage ARTCC (ZAN). ZAN FSS Operations Aircraft transitioning the ZAN/FSS boundary westbound shall be flight planned via one of the following entry points. MARCC (R338, G349) EPLOS (B932) NULUK (R220) OFORD (R580, R341) PINTT (G469) DRAPP (A342) CURVS (G344, G215) ADK (J115, R451, R336) ZAN shall determine an estimated time of crossing (ETC) for the above fixes and pass the following to FSS 15 minutes or 50nm (whichever is further) prior to the aircraft passing the fix. Also to be transferred is AC speed (in Mach), and altitude. An example exchange would be: ZAN to FSS DAL123 ETC is PINTT 2315z at FL360 M0.82 FSS to ZAN DAL123 entry at PINTT approved not before 2310z or after 2320z. ZAN to FSS KH (operating initials) ZAN shall be responsible for ensuring that the associated aircraft does not depart the entry fix prior to the entry time specified by FSS. Should the aircraft ETC change beyond the entry time specified ZAN shall immediately advise FSS of the new ETC time and relay an additional instructions to the aircraft. CONTINUED ON NEXT PAGE Anchorage Radio Standard Operating Guidelines Page 11 of 13

FSS ZAN Operations Aircraft transitioning the ZAN/FSS boundary eastbound shall be flight planned via one of the following exit points. OFORD (R341) PINTT (A590,G469) DRAPP (A342) CURVS (G344, G215) ADK (J115, R451, R336) FSS shall, upon receiving the position report from the exiting aircraft, relay the aircraft call sign, exit point, ETC, altitude, and speed to ZAN. In turn, ZAN shall assign and relay a squawk code to FSS for the aircraft. An example is below: FSS to ZAN DAL321 exiting OCA at PINTT, ETC 0325z at FL350 M.80. ZAN to FSS ZAN copies. Squawk 7224. FSS to ZAN KH (operating initials) FSS will then advise the pilot of his assigned squawk code and give frequency change instructions. FSS to Pilot DAL321, when crossing PINTT contact Anchorage Center on frequency 132.3 squawking 7224. Ten minutes prior to PINTT frequency change approved. Upon successful contact with the pilot ZAN shall notify FSS of receipt of communication from the pilot via either PM or voice notice. Should successful transfer of communication not be received by ZAN at ETC+0:05 FSS shall attempt to ascertain if the pilot is available via SELCAL or Vox/Txt on OCA frequency. The outcome of the contact attempt shall be made known to ZAN, and if contact is not established it will be the responsibility of ZAN to initiate contact procedures via the.contactme command. All situations not specifically covered by this or other governing documents shall be coordinated on a case-by-case basis between the affected facilities. The guiding documents for these interactions shall be FAA Order 7110.65 available above in the References section. Authorized 1-October-2011 Kenneth Haught, 1067681 Anchorage Air Traffic Manager Anchorage Radio Standard Operating Guidelines Page 12 of 13

Tokyo Radio (RJDG) The following common procedures are defined for operations between FSS and Tokyo Radio (RJDG). The following minimum separation standards shall be maintained for aircraft transiting the common border. Vertical: 1000ft Lateral: 30NM RJDG to FSS Operations Aircraft transiting the FSS/RJDG boundary eastbound shall be routed via one of the following entry routes. PASRO (A590) AKISU (R591) CUTEE (G344) RJDG shall as soon as practical after receiving an ETC from the aircraft transfer the following information to FSS: Aircraft call sign, entry fix, ETC for fix, altitude, and speed in Mach. FSS will then determine whether the aircraft can safely enter at the expected time and speed, or advise RJDG if other instructions are necessary. In the event FSS cannot accommodate the aircraft due to traffic and/or separation concerns RJDG shall be responsible for maintaining control of the aircraft and ensuring that a breach of airspace does not occur until such time as FSS is able to accept control of the aircraft (usually accomplished via an entry time. FSS to RJDG Aircraft transiting the FSS/RJDG boundary westbound shall be routed via one of the following exit routes. NIPPI (R220) OMOTO (R580) AKISU (R591) CUTEE (G344) FSS shall as soon as practical after receiving an ETC from the aircraft transfer the following information to RJDG: aircraft callsign, exit fix, ETC for fix, altitude, and speed in Mach. RJDG will then determine whether the aircraft can safely enter at the expected time and speed or advise FSS if additional restrictions are necessary. In the event RJDG cannot accommodate the aircraft due to traffic and/or separation concerns FSS shall be responsible for maintaining control of the aircraft and ensuring that a breach of airspace does not occur until such time as RJDG is able to accept control of the aircraft (usually accomplished via an entry time. In the event that a situation occurs that is not covered by this agreement is shall be the responsibility of the controllers to resolve the matter in a mutually acceptable way. The guiding document for FSS shall be FAA Order 7110.65. Authorized 1-Oct-2011 Kenneth Haught, Anchorage Air Traffic Manager Keisuke Yamane, VATSIM Japan Division Director Anchorage Radio Standard Operating Guidelines Page 13 of 13