San Juan CERAP. Standard Operation Procedures. Version 2.2 May 5th, Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR)

Size: px

Start display at page:

Download "San Juan CERAP. Standard Operation Procedures. Version 2.2 May 5th, Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR)"

Pauline Stephens
5 years ago
Views:

1 San Juan CERAP Standard Operation Procedures Version 2.2 May 5th, 2013 Welcome to San Juan CERAP (ZSU ARTCC, TJZS FIR) You are entering one of the most fascinating Combined Enroute Radar Approach Control facilities in the USA/Caribbean: the San Juan CERAP! You are more than welcome to be a part of our organization. If you follow this SOP and make part of your daily work at San Juan, we can say that you will grow to be a good controller much faster. Once again, Welcome.

2 Revisision Version 2.1 April 8 th, 2013 Version 2.2 May 5 th, 2013

3 Table of Contents 1.0 General Information and Procedures 1.1 VATSIM Documents 1.2 VATCAR Policies 1.3 ZSU Staff Positions 1.4 ZSU Minimum Hour Policy 1.5 San Juan Website 1.6 San Juan Training Program 1.7 FAA ICAO Operational Differences 1.8 Preferred Language between ATC and Pilots 1.9 Reference Material 2.0 Air Traffic Control Procedures 2.1 Checking VACANT ATC Positions 2.2 Clearance Delivery San Juan Princess Juliana Other Airfields 2.3 Ground Control San Juan Princess Juliana Other Airfields 2.4 Local Control San Juan Princess Juliana Other Airfields 2.5 Departure Control San Juan TRACON Princess Juliana TMA Other Airfields 2.6 Approach Control San Juan TRACON Princess Juliana TMA Other Airfields 2.7 Enroute Control 3.0 Approved ATC Positions & Squawk Codes

4 1.0 General Information and Procedures 1.1 VATSIM Documents All VATSIM members are required to understand the regulations within the VATSIM Documents listed below which are upheld by the San Juan CERAP Staff. VATSIM Code of Conduct VATSIM Code of Regulations VATSIM Transferring and Visiting Controller Policy VATSIM User Agreement VATSIM Privacy Policy 1.2 VATCAR Policies San Juan CERAP ATM / DATM / TA are required to understand the VATCAR Policies. These policies can be found by clicking here. 1.3 ZSU Staff Positions Below you will find the staff positions associated with the San Juan CERAP, as well as the s for each staff position. Air Traffic Manager (ATM)- atm@zsuartcc.org Deputy Air Traffic Manager (DATM) - datm@zsuartcc.org Training Administrator (TA)- ta@zsuartcc.org Events Coordinator (EC)- events@zsuartcc.org Facility Engineer (FE)- fe@zsuartcc.org Webmaster (WM)- webmaster@zsuartcc.org

5 1.4 ZSU Minimum Hour Policy Home Controllers: Home Controllers are required to provide ATC Services on an Approved ATC Position (see section 3.0) for a minimum of 5 hours per month. Failure to provide 5 hours for two (2) consecutive months will have the Controller listed as Inactive. Once listed Inactive; Controller will be required to perform an OTS (Over the Shoulder) test before being marked active again. Failure to provide a total of 30 hours within Six (6) months will have the Controller removed from the Roster. Controller is required to the Air Traffic Manager in the event he/she cannot perform the minimum required controlling hours per month. Visiting Controllers: Visiting Controllers are required to provide ATC Services on an Approved ATC Position (see section 3.0) for a minimum of five (5) hours per month. Visiting Controllers are under the agreement of this SOP and the Visiting SOP Leave of Absence: Home Controllers may request a Leave of Absence (LOA). LOAs shall be sent to the Air Traffic Manager. Upon Approval by the Air Traffic Manager and VATCAR1 - Division Director, Controller will be exempt from this policy (SOP Section 1.4) - More information on this policy here

6 1.5 San Juan Website The website is a great tool for a controller. This website will have all of our files, policies, regulations, and operating charts that are available to you as the controller. Before you can access this website, you must obtain a login, which can be done by registering when you first join. All registration is mandatory of all controllers in San Juan which ensures Controller gets all the appropriate files for performing ATC San Juan Training San Juan CERAP Training consists of Hands on Learning and Reading. Training may be conducted in a Group or One-on-One. All Controllers will receive the same fair training from our Staff to ensure success in each Virtual Controller Career. 1.7 Basic FAA ICAO Operational Differences San Juan CERAP operates primarily under FAA Regulations with the exception of Princess Juliana TMA St Maarten which follows FAA Phraseology / ICAO Phraseology and ICAO Procedures. St Maarten Quick Info: Transition Altitude: 5,000ft Transition Level: FL065 (6,500ft) Basic examples of the differences between FAA and ICAO: FAA: Altimeter, Line up and Wait, Taxi to and Hold Short of rwy # via... ICAO: QNH, Line up rwy #, Taxi to Holding Point {designator} runway # A more detailed list of difference can be found here A list of ICAO Phraseology can be found here Terms FAA: Federal Aviation Administration ICAO: International Civil Aviation Organization

7 1.8 Preferred Language between ATC and Pilots Preferred language between ATC and Pilots is English although a Spanish Speaking Pilots may communicate in Española only if the Controller can understand the Pilot and vice versa. 1.9 Material References The Following Documents are considered part of of Operations / Airspace in which can be used as a reference; SJU_Suppl.pdf SXM_Suppl.pdf San_Juan_Visiting_Controllers_Policy.pdf TJSJ+Transitions-Renewal.pdf All Letter of Agreements with surrounding FIR Airspaces; All Documents are located on the San Juan Website 2.0 Air Traffic Control Procedures 2.1 Checking VACANT ATC Positions and Logging on Prior to logging on an ATC Position; All Controllers should view VATSPY, Serv Info or logon as an Observer to check and see if any controllers are online. Note: VATSPY or Serv Info may not be current. Attempting to log onto the Network on a Position and VRC says Callsign in Use ; Connecting Controller should find a different position to log onto that he/she has endorsements for or wait until the position is vacant. After connecting on a Position, Controller shall announce they are online via ATC Chat ( / message ): Example: San Juan Center Online , Online or to some effect so others know you're online

8 2.2 Clearance Delivery The Clearance Delivery position is the most important in an Air Traffic Control line-up. This person is responsible for ensuring the proper route, altitude, and flight plan information prior to issuing a clearance, as well as handing off the aircraft San Juan - Initial: 5,000ft San Juan uses a typical FAA clearance to issue IFR clearances. All o f the departure procedures can be found on the Quick Reference Card, found on the website. After a clearance has been issued and read back by the pilot, the Clearance Delivery controller is to state - "Readback correct. Contact Ground on when for Push and Start." Princess Juliana - Initial: 4,000ft Princess Juliana does not have a Clearance Delivery controller. However, all of the departure procedures can be found on the Quick Reference Card, found on the website. A Princess Juliana Clearance shall be issued as - "DAL011, Cleared to San Juan airport via radar vectors JUICE. Maintain 4,000, squawk 4107." After a clearance has been issued and read back by the pilot, the controllers are to state - "Readback correct. Advise ready for push and start." Lowest ATC position within the Juliana TMA is Tower Other Airfields - Initial: 5,000ft All other airfields, so long as they are not within the Juliana TMA should be issued a typical FAA clearance, and treated as a typical FAA departure. Airfields that are within the Juliana TMA should refer to Section for clearance, readback instructions and initial altitude.

9 2.3 - Ground Control Ground Control is responsible for taking an aircraft from the ramp, to the active departure runway, as well as taking an arrival from the runway, to the ramp in a safe manner. Ground control does not control the ramp area on the FAA airfields, however, on ICAO airfields, ground control is in control of the ramp as well San Juan San Juan airport has a few taxiway differences than what is currently on the sector file. To issue a proper taxi clearance, please become familiar with the current taxiways, which can be found on the airport diagram, by clicking here Princess Juliana Note: Juliana does not have a ground Controller Aircrafts that are an Airbus A320 / Boeing 737-x / similar (Class 1 &2 Aircrafts) or smaller may taxi via Ramp, Alpha Heavy Aircrafts (Class 3 & Super) must taxi via Ramp, Charlie, Runway 10, lineup expect immediate departure. Please note for any Pilot that does not have the FlyTampa scenery, they do not have direct access to taxiway Alpha. Pilot must taxi Charlie, Runway 10, Bravo, Alpha Other Airfields All aircraft at any other airfield should be issued a taxi clearance that will expedite their departure time. We want them to navigate the easiest, and fastest route on the ground. A controller shall use his/her best judgment, and airport diagrams to determine whether or not an aircraft can navigate a particular taxiway Local Control Local Control is responsible for issuing takeoff and landing clearances, as well as ensuring separation and handling VFR aircraft throughout the airspace. Local Control controls all the runways at any airfield, whether active or not. This person is also responsible for issuing an ATIS each time a new weather report is released. This facility does not track aircraft data tags.

10 2.4.1 San Juan - Class C San Juan Local must handle all aircraft in the Class C airspace. All aircraft transitioning the Class C airspace must have an issued squawk code between 1201 and The two VFR transitions that can be used are the Tango, and the River transition. When an aircraft has squawked the transition code, the tower must tell them he/she is radar contact at the listed altitude, and tell him to transition the San Juan Class C airspace via either the Tango or River transition. Example - N123A - Tower, N123A request transition San Juan Class C airspace. Tower - N123A, Squawk N123A - Squawk Tower - N123A, Radar contact, 1,700. Cleared into the San Juan Class C airspace via the Tango transit ion, maintain 2,500. Report clear of the Class C airspace. N123A - Roger. Will report clear. N123A - Clear of the Class C airspace. Tower - N123A, Radar services terminated. Squawk 1200, maintain VFR. Frequency change to advisory approved. Traffic Pattern Information - Runway 08 - Left Runway 26 - Right Runway 10 - Right Runway 28 - Left Departure Heading Information - ACONY 1, CRSTL 1, GANBO 1, JAWS 9 - Runway 10/08 - Heading 350 Runway 26/28 - Heading 280 GLAD A2, VERMA 5 - Runway 10/08 - Heading 020 Runway 26/28 - Heading 280 HAMAR 1 - Runway 10/08 - Runway Heading Runway 26/28 - Not Authorized JETTS 1 - Runway 10/08 - Heading 080 Runway 26/28 - Heading 280

11 ANGRA 1 - Runway 10/08 - Not Authorized Runway 26/28 - Runway Heading Princess Juliana - Class C Princess Juliana Local must handle all aircraft in the Class C airspace. All basic Class C airspace requirements apply. Traffic Pattern Information - Runway 10 - Right Runway 28 - Left Departure Heading Information - Runway 10 East /Northeast - Heading 140 West /Northwest - Heading 250 South - Heading 180 Note - All headings issued must have the word RIGHT within the heading issuance. Note - If Aircraft has filed SID, Instruct Aircraft to fly Departure as published Note - Local shall not hand aircraft off until they have made the turn and have achieved a positive climb Other Airfields All other airfields have their own airspace and airport information. Controllers controlling those airfields are responsible for knowing the airspace class, the procedures, terrain, and airport surface Departure Control Departure control is responsible for taking the aircraft from the departure runway, and getting them on course to their enroute route San Juan - Ceiling: 10,000ft San Juan departures will be handed off from tower on the headings listed above for the Local Controller. From there, it is the departure controllers responsibility to radar identify the aircraft and issue vectors and altitudes to ensure the aircraft remains clear of other aircraft, as well as begins to track his/her own course. This facility is not to be opened unless traffic warrants, or there is an event. This facility should initiate a radar handoff to center while the aircraft is climbing through 7,500ft

12 2.5.2 Princess Juliana - Ceiling: 15,000ft Juliana Departure Position is not authorized to be used at any time. See Section Other Airfields - Ceiling: Varied All other airfields that are FAA shall have a departure ceiling of 10,000ft and all Departure Controllers for those positions shall follow section All other airfields that are ICAO shall have a departure ceiling of 15,000ft (FL150) and all Departure Controllers for those positions shall follow section Approach Control Approach control is responsible for taking the aircraft from the enroute environment, and getting them on approach, and final for a landing runway San Juan San Juan approach shall receive aircraft from Center at about 11,000ft. Prior to such hand off, San Juan approach shall be ready to issue runway and the procedure to the runway in which the pilot can expect. If the aircraft is on a STAR, the Approach Controller is not required to vector them until the last fix, or the second or third to last fix, whichever the controller deems necessary. The most popular procedure is either visual, or ILS for runways 08 and 10. Aircraft should be vectored and issued descents appropriately. It is to be noted that there is terrain on the south

13 side of San Juan Field, so the recommended vector is north of the airport, to arrive west of the airfield Princess Juliana Juliana approach shall receive aircraft from Center at specified waypoint altitudes as listed from the QRC. If Aircrafts Flight Plan does not cross a designated waypoint, Center will handoff to Juliana Approach within 5-10 NM from Approach Boundary at or below FL090 - FL130. Prior to such hand off, Princess Juliana approach shall be ready to issue runway and the procedure to the runway in which the pilot can expect. If the aircraft is on a STAR, the Approach Controller is not required to vector them until the last fix, or the second or third to last fix, whichever the controller deems necessary. The only STAR procedure is ULUBA 1 Arrival. Under ICAO Regulations, the procedure must be flown as published. If an Aircraft is not flying the ULUBA 1 Arrival, vectors may be used to have the aircraft fly a Visual Approach. If the Pilot objects to a Visual Approach. Controller should have knowledge of VOR Approaches which have published charts as well. It is to be noted that there is terrain on the east side of Princess Juliana Other Airfields Approach Controllers working TRACON for other airfields are responsible for knowing the procedures, runways, and terrain of that airfield Enroute Control Enroute is the Center controller. This person is responsible for ensuring separation of aircraft in their cruise environment. All en route controllers should have knowledge of all airports procedures, as well as facility procedures that are listed above. Descent altitudes to cross fixes are listed on the Quick Reference Card. Those altitudes need to be followed at all times, unless requested otherwise by ZSU Approach controller, adjacent FIR Approach Or Center Controller.

14 3.0 Approved ATC Positions The following positions with corresponding call signs and Frequencies are Approved ATC Positions by the Air Traffic Manager which are followed by Real World Charts ATC Positions with a * are authorized for event use ATC Positions with a * are authorized when traffic warrants the position Position Name Position Callsign Position Frequency ATIS San Juan ATIS TJSJ_ATIS St. Thomas ATIS TIST_ATIS St. Croix ATIS TISX_ATIS Borinquen ATIS TJBQ_ATIS Clearance Delivery San Juan Delivery SJU_DEL Ground Borinquen Ground TJBQ_GND San Juan Ground SJU_GND St. Thomas Ground TIST_GND St. Croix Ground TISX_GND

15 Tower Borinquen Tower TJBQ_TWR San Juan Tower SJU_TWR Juliana Tower TNCM_TWR Isla Grande Tower TJIG_TWR St. Croix Tower TISX_TWR St. Thomas Tower TIST_TWR Wallblake Tower TQPF_TWR Beef Island Tower TUPJ_TWR ATC Positions with a * are authorized for event use ATC Positions with a * are authorized when traffic warrants the position Approach / Departure San Juan Approach SJU_APP San Juan Approach* SJU_E_APP* San Juan Approach* SJU_W_APP* San Juan Departure* SJU_DEP* Juliana Approach TNCM_APP

16 Center San Juan Center SJU_E_CTR San Juan Center* SJU_N_CTR* San Juan Center* SJU_S_CTR* San Juan Center* SJU_E_CTR* San Juan Center* SJU_W_CTR* ATC Positions with a * are authorized for event use ATC Positions with a * are authorized when traffic warrants the position Squawk Codes TJSJ - San Juan TJBQ - Borinquen TQPF - Wallblake TIST - St. Thomas TUPJ - Beef Island TNCM - Juliana TISX - St. Croix TJIG - Isla Grande SOP Authorized by: Toby Turlington Air Traffic Manager San Juan CERAP

ERIE ATCT STANDARD OPERATING PROCEDURES

ORDER ERI ATCT 7110.10I ERIE ATCT STANDARD OPERATING PROCEDURES August 1, 2014 VATUSA CLEVELAND ARTCC VIRTUAL AIR TRAFFIC SIMULATION NETWORK VIRTUAL AIR TRAFFIC SIMULATE NETWORK UNITED STATES DIVISION