VIRTUAL AIR TRAFFIC SIMULATION NETWORK CARIBBEAN DIVISION ZSU SAN JUAN CERAP ORDER SJU 7110.1T SUBJ: San Juan Luis Muñoz Marín International Airport Air Traffic Control Tower Standard Operating Procedures This order prescribes standard operating procedures for use by San Juan CERAP personnel providing air traffic control services. It is supplemental to FAAO 7110.65, FAAO 7210.3 and the Letters of Agreement with other facilities. All operational personnel are required to be familiar with the provisions of this order that pertain to their responsibilities. Neither FAAO 7110.65, nor our local order ZSU 7110.4U will cover all situations. With the knowledge from the provisions in these directives, controllers are still required to exercise their best judgment in handling those situations that are not covered. Alex Long Air Traffic Manager San Juan CERAP
RECORD OF CHANGES CHANGE EFFECTIVE DATE DESCRIPTION
TABLE OF CONTENTS RECORD OF CHANGES... 2 TABLE OF CONTENTS... 3 CHAPTER 1. GENERAL... 4 1.1 TRANSFER OF CONTROL POINT (TCP)... 4 1.2 VIDEO MAPS AND SCOPE ALIGNMENT/SETTINGS... 4 1.3 BEACON CODE ALLOCATION & ASSIGNMENTS... 4 1.4 ALTITUDE/SPEED ASSIGNMENTS... 4 1.5 AUTOMATED TRANSFER OF RADAR IDENTIFICATION... 4 1.6 SECTOR/FACILITY IDENTIFIERS... 5 1.7 WEATHER... 5 CHAPTER 2. FLIGHT DATA/CLEARANCE DELIVERY... 6 SECTION 1. GENERAL... 6 SECTION 2. AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS)... 6 4.2.2 ATIS FORMAT:... 6 SECTION 3. FLIGHT PLAN/CLEARANCES/INSTRUCTIONS... 7 2.3.1 VFR DEPARTURES... 7 2.3.2 IFR DEPARTURES... 7 2.3.3 PREFERENTIAL ROUTES FOR SJU... 8 CHAPTER 3. GROUND CONTROL... 10 SECTION 1. GENERAL... 10 3.1.1 GENERAL... 10 SECTION 2. COORDINATION... 10 3.2.1 COORDINATION... 10 3.2.2 OPERATIONS... 10 CHAPTER 4. LOCAL CONTROL... 13 SECTION 1. GENERAL... 13 4.1.1 GENERAL... 13 SECTION 2. DEPARTURE RELEASE COORDINATION... 13 4.2.1 DEPARTURE RELEASES... 13 4.2.2 INITIAL DEPARTURE HEADINGS... 14 a. Initial Departure Headings... 14 4.2.3 COORDINATION... 15
CHAPTER 1. GENERAL 1.1 TRANSFER OF CONTROL POINT (TCP) The TCP is defined as the sector or position boundary unless otherwise specified. 1.2 VIDEO MAPS AND SCOPE ALIGNMENT/SETTINGS Video Maps must be set to display the sectors entire area of radar control jurisdiction and a reasonable distance beyond that area. Select appropriate video maps based upon current operations and sectorizations. Correct range and radar stations must be set for all positions. 1.3 BEACON CODE ALLOCATION & ASSIGNMENTS POSITION BEACON CODE RANGE SJU FD/CD 4101 4177 SJU GND 4141 4155 SJU TWR 4156 4177 SJU APP 4178 4227 SJU CTR 4228 4277 1.4 ALTITUDE/SPEED ASSIGNMENTS All aircraft must be at appropriate altitude for direction of flight. All radar sectors must display the current assigned altitude on the FDB at all times. 1.5 AUTOMATED TRANSFER OF RADAR IDENTIFICATION All controllers shall enable strips are automatically pushed to the appropriate controller when handoff is initiated. FDB shall be clean and correct for each aircraft prior to initiation of handoff.
1.6 SECTOR/FACILITY IDENTIFIERS SECTOR FACILITY ID R 5 F R 1 W R 9 N R 2 I R 3 U R 4 Q R 6 R R 7 G R 8 J STXT XC STXG XG SJUT LC SJUG GC STTT ST STTG SG SIGT D SXMT XT SXMA XA MIAC M ZMO Z 1.7 WEATHER SAN JUAN APPROACH (SJU/SIG) San Juan weather information for SJU and SIG must be displayed in the weather window at all times. SAN JUAN APPROACH (RVR/STT/STX) San Juan weather information for RVR, STT, and STX must be displayed in the weather window at all times. SAN JUAN ENROUTE San Juan weather information for SJU, STT, STX, and SXM must be displayed in the weather window at all times.
CHAPTER 2. FLIGHT DATA/CLEARANCE DELIVERY SECTION 1. GENERAL 2.1.1 GENERAL POSITION ID: CD STARS ID: SJF PRIMARY FREQUENCY: 126.400 SECTION 2. AUTOMATIC TERMINAL INFORMATION SERVICE (ATIS) 4.2.1 vatis application will be the preferred method of ATIS broadcast. Include in the ATIS content all items in JO 7110.65, as appropriate. 4.2.2 ATIS FORMAT: a. AIRPORT NAME b. INFORMATION ATIS CODE (ex: INFORMATION ALPHA). c. CURRENT ZULU TIME. (ex: ONE TWO FIVE ZERO ZULU.) d. WIND (ex: ONE TWO ZERO AT THREE). e. VISIBILITY AND PERTINENT OBSCURATIONS (ex: VISIBILITY ONE ZERO). f. SKY CONDITIONS (ex: SIX THOUSAND SCATTERED) g. TEMPERATURE AND DEW POINT (ex: TEMPERATURE TWO NINER, DEWPOINT TWO FOUR) h. ALTIMETER (ex: ALTIMETER TWO NINER EIGHT TWO) i. APPROACH TYPE IN USE (ex: DME, LOCALIZER, VOR, RNAV, VISUAL, AND ILS APPROACHES IN USE.) j. LANDING AND DEPARTING RUNWAYS (ex: LANDING AND DEPARTING RUNWAYS EIGHT, AND TWO SIX) ADDITIONAL REMARKS: k. SIMULTANEOUS APPROACHES TO PARALLEL AND INTERSECTING RUNWAYS ARE IN USE. l. SIMULTANEOUS APPROACHES IN USE. m. LOW LEVEL WIND SHEAR ADVISORIES IN EFFECT. n. VFR AIRCRAFT SAY DIRECTION OF FLIGHT. o. NOTICES TO AIRMEN ADDITIONAL REMARKS: p. READBACK ALL RUNWAY HOLD SHORT INSTRUCTIONS. q. READBACK ALL RUNWAY HOLD SHORT INSTRUCTIONS AND ASSIGNED ALTITUDES. r. UPON RECEIPT OF YOUR ATC CLEARANCE READBACK ONLY YOUR CALLSIGN AND TRANSPONDER CODE UNLESS YOU HAVE A QUESTION. s. VERIFY YOUR ASSIGNED STANDARD INSTRUMENT DEPARTURE WITH CLEARANCE DELIVERY WHEN READY TO PUSH AND TAXI.
t. OPERATE TRANSPONDER ON MODE CHARLIE ON ALL TAXIWAYS AND RUNWAYS. u. ADVISE ON INITIAL CONTACT, YOU HAVE INFORMATION (INFORMATION ATIS CODE). SECTION 3. FLIGHT PLAN/CLEARANCES/INSTRUCTIONS 2.3.1 VFR DEPARTURES a. Record the following information into a flight progress strip: i. Aircraft ID ii. Type Aircraft iii. Requested Altitude (Corrected for direction of travel) iv. Destination Airport or Direction of Flight b. All VFR aircraft departing SJU shall be assigned a discrete squawk code, and aircraft who will be departing the pattern are to be issued a departure frequency. c. Push strip to next appropriate controller once completed with all FD/CD tasks and aircraft has been advised to contact the next appropriate controller. 2.3.2 IFR DEPARTURES a. Assign Turbojets in accordance with the following: i. Assign IFR turbojet aircraft a Departure Procedure and, when necessary, an altitude, and frequency ii. For departure not processed via a SID, route fix by fix via radar vectors iii. Aircraft filing NO DP/SID, or those that refuse an approved Departure Procedure, shall be issued a clearance that will route the aircraft along an approved Departure Procedure (SID) routing, through an approved departure gate, to the next appropriate fix in the flight planned route, and then as filed.
b. Assign Props and Turboprops in accordance with the following: i. SNGRA (RNAV) & HAMAR (RNAV) are restricted to Props and Turboprop aircraft ONLY, but may utilize JAAWS, CRSTL, VERMO & JETSS. ii. Prop and Turboprops are prohibited from utilizing the ACONY, GLADA, and GANBO departure procedures c. Turbojet and Turboprop aircraft are to be assigned an initial altitude of 5,000 and instructed to expect requested cruise altitude/flight level 10 minutes after departure. Clearance Delivery shall ensure all cruise altitudes are correct for direction of flight according to NEODD SWEVEN. d. Push strip to next appropriate controller once completed with all FD/CD tasks and aircraft has been advised to contact the next appropriate controller. 2.3.3 PREFERENTIAL ROUTES FOR SJU a. FD/CD controllers must ensure that all departures are cleared via the respective departure gates. DEPARTURE GATES GATE FILED ROUTE ROUTE VERMO L455/L456/L459 OR NORTHBOUND SJU VERMO DP OR GLADA DP./. JAAWS R507/G431/A555 OR NORTHWEST BOUND SJU JAAWS DP OR ACONY DP./. BQN B520/RTE2 WESTBOUND SJU DDP B520 BQN./. SJU RTE2 BQN./. MAZ G633 WESTBOUND SJU DDP G633 MAZ./. CRSTL FAJAR/JETSS **A300/G431/G432/L455/L458 SOUTHBOUND ***G633/G449/A555/R888 OR B520 EASTBOUND SJU RTE9** OR CRSTL DP OR GANBO DP./. *SJU RTE2 OR JETSS DP OR HAMMR DP./.
i. *Aircraft over flying PJM airspace at or below 150 route via SJU RTE2 STT A638 PJM ii. *Aircraft landing PJM airspace route via SJU RTE2 STT A638 PJM OR SJU JETSS DP SLUGO A638 PJM. iii. Aircraft over flying TNCM TCA must be cleared via SJU.RTE6.STT. A638/B520, as appropriate. iv. **Aircraft flying A300 route via SJU.RTE9.MIGHT.A300 v. ***Aircraft flying G449 Route Via RTE2 COY..ANADA vi. ****Aircraft flying G633/A555/R888 route via SJU.RTE2.COY or SJU.JETSS DP. COY vii. During periods where TJSJ is on west operations: Aircraft landing or over flying STT must be cleared via SJU.RTE6.STT then as filed. viii. Aircraft filed over COY must be cleared via: SJU RTE 7 TUUNA RTE4 COY then as filed.
CHAPTER 3. GROUND CONTROL SECTION 1. GENERAL 3.1.1 GENERAL POSITION ID: GC STARS ID: SJG PRIMARY FREQUENCY: 121.900 SECTION 2. COORDINATION 3.2.1 COORDINATION a. Initiate coordination for runway crossing or temporary use of all or any portion of active runways directly with LC. b. GC shall verbally coordinate with LC for intersection/inactive runway departures. c. To reduce delays, instruct aircraft to contact or monitor tower frequency as soon as practical. 3.2.2 OPERATIONS a. To allow for high speed turnoffs from the runways, maintain clearance on taxiways S and H, between S3 & S7 and H6 & H5. b. Pushback clearances are required for aircrafts at gates A 1 thru A 7, G3 thru G9, G11, G15, G17, G19, G18, G, 25, G27, G29, G39, G32 thru G41 (See Figure 3.2.2 1 for gate diagram). These gates pushback onto active taxiways. If a pushback request is received from aircraft located on the INTERIOR of the alley, issue pushback advisories only. Do not clear or imply that an aircraft is cleared for pushback.
Figure 3.2.2 1
c. Gate Hold is a procedure designed to hold aircraft at the gate or other ground location whenever departure delays exceed or are anticipated to exceed 15 minutes. The Tower SC/CIC has the responsibility to initiate Gate Hold Procedures. When Gate Hold Procedures are initiated, perform the following: i. On initial contact, and if delays are expected, issue an engine start time and/or delay information. ii. Advise the pilot to monitor the frequency. iii. Record the engine start time in Box 12 of the flight progress strip. iv. Unless modified by Flow Control instructions, sequence departing aircraft according to the initial call up time. v. Re sequence aircraft that are not ready to taxi at the assigned time. vi. On initial contact, and if no delays are expected, instruct the aircraft to advise when ready to push back or taxi.
CHAPTER 4. LOCAL CONTROL SECTION 1. GENERAL 4.1.1 GENERAL POSITION ID: LC STARS ID: SJT PRIMARY FREQUENCY: 132.050 SECTION 2. DEPARTURE RELEASE COORDINATION 4.2.1 DEPARTURE RELEASES Request a release for aircraft by stating the word REQUEST followed by the Departure Transition/Procedure and the word PROP, BOEING SEVEN FIVE SEVEN (B757), or HEAVY as appropriate. EXAMPLE Request COY Prop. Request JETSS Heavy. Request STT. Request GLADA B757 Optionally, a blanket and/or a rolling release may be put into place by using the following procedures a. Blanket Release A blanket release is a release permission that does not require the local controller to request a release for each departure. To request a blanket release, use the following procedures EXAMPLE LC: Request SJU DEP Release AR/DR: Released, 5 MIT, RJ LC: 5 MIT, JH The arrival/departure controller can request a mile in trail restriction on continuous departures using the same transitions
b. Rolling/Boundary Release A rolling/boundary release allows a local controller to release the aircraft, but upon rolling/exiting their control, to inform the departure controller of the transition and if needed, type. To request a rolling boundary, use the following procedures EXAMPLE LC: Request SJU R/B Release AR/DR: Released, KE LC: Released, OX 4.2.2 INITIAL DEPARTURE HEADINGS a. Initial Departure Headings Runway 10/08 Preferred Departure Heading is 080 Runway 26/28 Preferred Departure Heading is 280 If aircraft is utilizing a departure procedure, utilize the following headings per the appropriate procedure: i. ACONY, CRSTL, GANBO, JAAWS Runway 10/08 350 Runway 26/28 280 ii. GLADA, VERMO Runway 10/08 020 Runway 26/28 280 iii. HAMAR Runway 10/08 080 Runway 26/28 280 iv. JETTS Runway 10/08 080 Runway 26/28 280 v. SNGRA Runway 10/08 080 Runway 26/28 280
4.2.3 COORDINATION a. Missed Approach/Go Around Instructions b. Taxiway Usage During VFR weather conditions and when visual separation can be applied between departing and arriving aircraft, use the following procedures for aircraft executing a missed approach/go around: In the event of a missed approach/go around, LC shall accomplish the following: 1. Assign turbojet and turboprop/prop aircraft NOT on an instrument approach executing a go around on Runway 08 or 10, climb to 2,000. 2. Assign turbojet and turboprop/prop aircraft NOT on an instrument approach executing a go around on Runway 26 or 28, climb to 3,000. 3. Assign aircraft flying an instrument approach procedure (IAP) to fly the missed approach as published 4. Advise aircraft to contact appropriate DEP/APP controller. i. Provide taxi instructions, as appropriate to arriving aircraft when clearing the active runways per JO 7110.65. ii. Unless LC can ascertain when an arrival is clear of the landing runway, LC shall retain communications with arriving aircraft until the pilot reports clear of the runway.