Albany ATCT Standard Operating Procedures This air traffic control procedural document is provided for virtual air traffic control in the ZBW ARTCC of the VATSIM network only. It is not for real-world ATC use. These procedures are approved for use as defined by the Boston Virtual ARTCC Administration Team only. Version J September 12, 2017 For more information about Boston Virtual ARTCC, visit www.bvartcc.com. bvartcc.com /BVARTCC @BVARTCC
Version Log & Changes from Previous Version Changes from the previous three versions are listed at the top of every SOP. Changes within the document are emphasized with a vertical blackline beside changed text. Version J September 12, 2017 Adds requirement to insert ALB# departure into flight plans when using PDCs Page 4 Version I October 17, 2016 Clarifies procedures for clearing departing aircraft on course Page 15 Version H September 30, 2016 Updates document formatting All Using this Document The information contained in Chapter 1 is knowledge material that all controllers should be familiar with. The other information in this SOP is designed as additional resource material for controllers who wish to apply extra realism within this airspace. It is not required knowledge for practical exams or on-network controlling, as the OTS Exam Evaluation Standards still act as the primary reference document for practical exams. Controllers are encouraged to review the additional resource material in Chapter 2 onward at their leisure and apply it at their discretion. BVA Albany ATCT Standard Operating Procedures Page 1
Chapter 1: Overview 1.1 Quick Reference Sheets a. ALB_DEL (127.50) Initial Altitude for IFR Aircraft: 4,000 Altitude Restriction for VFR Departures: 3,000 Departure Procedures: ALB#, radar vectors to (FIX) CPDLC Available (use.pdcm to include top altitude in the CPDLC message) b. ALB_GND (121.70) Taxi Routes: Due to the simple taxiway system, there are no pre-established preferred taxi routes. c. ALB_TWR (119.50) Airspace: 5nm from KALB from surface to 2,000 MSL. Calm Wind Configuration: Land/Depart Runways 1 and 28. ATIS: Digital. Departure Headings: Runway heading (as assigned in SID) unless split is in operation, in which case assign the following headings: Runway Departures Missed Approach 1 040 (East) / 340 (West) / Rwy Heading 19 160 (East) / 220 (West) / Rwy Heading 10 110 (All) Runway Heading 3,000 28 250 / 310 / Runway Heading (Any) BVA Albany ATCT Standard Operating Procedures Page 2
d. ALB_APP (132.82/118.05/127.15) Airspace: Video map lateral boundaries to 10,000 MSL. Route / Procedure Altitude Handoff V487 CANAN 11,000 and below Boundary CAM 11,000 and below Boundary V270 CTR or V146 11,000 and below CTR V130 11,000 and below STELA From the West 11,000 and below Boundary ILS Approach Frequency/Course FAF / Altitude ILS 1 109.50 011 FLEIG / 1,900 ILS 19 109.50 191 HAUKY / 1,600 1.2 General a. This document outlines the air traffic control procedures and responsibilities for controllers working positions at ALB ATCT. b. The following callsigns and frequencies shall be used when working positions at ALB ATCT: Identifier Position Frequency VOX Channel ALB_DEL Clearance Delivery 127.50 ALB_127.500 ALB_GND Ground Control 121.70 ALB_121.700 ALB_TWR Local Control 119.50 ALB_119.500 ALB_E_APP Approach (East Radar) 132.82 ALB_132.820 ALB_W_APP Approach (West Radar) 118.05 ALB_118.050 ALB_F_APP Approach (Final Vector) 127.15 ALB_127.150 KALB_ATIS ATIS 120.45 ALB_120.450 c. Except when split, ALB APP shall use frequency 132.82. BVA Albany ATCT Standard Operating Procedures Page 3
Chapter 2: Clearance Delivery a. Altitude Assignments: 1. Assign all IFR departures 4,000, or lower requested altitude. Aircraft shall expect requested altitude ten (10) minutes after departure. 2. Assign all VFR departures at or below 3,000' b. VFR Aircraft: c. SVFR: 1. VFR aircraft shall be assigned the appropriate altitude, departure frequency, and discrete squawk code. Maintain VFR at or below 3,000' until advised. Departure frequency 132.82, squawk 5421. 1. All Special VFR (SVFR) departures shall be instructed to maintain SVFR at or below 2,000 feet. d. IFR Aircraft: 1. Clear IFR aircraft via the appropriate preferred routing. 2. Clearances may be issued by CPDLC. 3. The ALB# SID is the primary SID. This SID shall be inserted into the flight plan. Cleared to (destination) via the ALBANY (#) Departure, radar vectors (first fix), then as filed. 4. Aircraft unable a SID shall be cleared via the corresponding ALB# departure procedure heading. The ALB# shall be included in the flight plan. Cleared to (destination) via fly runway heading, radar vectors (first fix), then as filed. BVA Albany ATCT Standard Operating Procedures Page 4
Chapter 3: Ground Control a. Ground Control is responsible for the movement of aircraft on all airport movement areas, excluding any active runway(s). b. Taxiway and Run-up Restrictions: 1. As much as possible, assign departure runways consistent with direction of flight to avoid crossing traffic. 2. Ensure that all aircraft read back hold short instructions and that a transfer control point has been established. 3. Direct aircraft requesting engine run-ups to the holding pads of each runway. 4. Use of Taxiway D east of Runway 1/19 is limited to aircraft less than 12,500 lbs. c. Intersection Departures: d. Parking: 1. Coordinate all intersection departures with Local Control and provide intersection departure aircraft with available takeoff distance from the assigned intersection. 1. There are many different ramp locations located on different parts of the airport. Ensure that you know where an arrival is taxiing to before issuing taxi instructions to reduce the possibility of a runway incursion. BVA Albany ATCT Standard Operating Procedures Page 5
LAHSO Distance: 3,757 Million Air FBO LAHSO Distance: 4,150 BVA Albany ATCT Standard Operating Procedures Page 6
Chapter 4: Local Control a. Local Control is authorized to provide Class C services within the area extending 5nm from KALB, upwards from the surface to 2,000 feet, and on all active runways. b. Runway selection: 1. Runway 1 is the primary runway in a calm wind configuration, while Runway 28 is the alternate runway. At all other times, use the runway most aligned with the wind. 2. Two runways must be active at all times. 3. All advertised runways may be used for departures without further coordination with radar. Radar will coordinate any arrivals to the secondary runway that cannot land to hold short of the primary runway. c. Runway changes: 1. Coordinate with all affected ALB positions when weather forces a runway change to determine the optimal runway(s) to open. 2. When one currently active runway will remain open after the change, minimize delay to traffic by using that runway exclusively while the runway change is in progress. d. Departures: 1. Releases: (a) All IFR aircraft that will land within ALB airspace require a release from radar before issuance of takeoff clearance. All others do not require a specific release. (b) Releases may be accomplished by verbal or textual coordination. (c) Releases are valid for a period of three minutes. BVA Albany ATCT Standard Operating Procedures Page 7
e. Departure heading: 1. TWR shall assign all fixed wing departures runway heading per the ALB#. 2. If an APP split is active, a heading will be provided, dependent on direction of flight as shown in the table below. These assigned headings do not require coordination with APP: Runway Departures 1 040 (East) / 340 (West) / Rwy Heading 19 160 (East) / 220 (West) / Rwy Heading 10 Runway Heading (All) 28 250 / 310 / Runway Heading (Any) 3. NOTE: All aircraft requesting Flight Levels will be vectored to the ALB340R 25DME fix for separation with aircraft on descent to N90. Apply a tower assigned heading in relation to this fix rather than the first waypoint on the flight strip. 4. The limits of the departure corridor are also displayed on the video map, depicted by two symbols at each limit of the corridor. 5. LC may also assign optional headings within the corridor if no TRACON split is active. These headings should be consistent with the route of flight and must also be consistent with headings issued if a split were active. 6. VFR traffic that will leave the traffic pattern shall be assigned runway heading. f. Arrival procedures: 1. All aircraft executing an unintentional missed approach shall be assigned to fly the runway heading and to climb and maintain 3,000 feet. 2. Coordinate with the appropriate radar sector and hand off the aircraft as soon as possible. 3. Automatic releases are canceled until otherwise advised by the radar controller. g. Traffic patterns: 1. Aircraft remaining in the pattern should not normally be assigned a discrete squawk code. BVA Albany ATCT Standard Operating Procedures Page 8
Chapter 5: Radar Sectors a. Frequency: b. Airspace: 1. When all positions are consolidated: (a) APP will use frequency 132.82, with a voice channel of ALB_132.820. 2. The following splits can be staffed: (a) East Radar (ALB_E_APP), with a voice channel of ALB_132.820. (b) West Radar (ALB_W_APP), with a voice channel of ALB_118.050. (c) Final Vector (ALB_F_APP), with a voice channel of ALB_127.150. 3. When staffed, ALB_F_APP has control for the airspace immediately surrounding the localizer, in a 20nm semi-circle centered around Albany airport SFC-4000'. 1. ALB APP has jurisdiction over aircraft within its airspace from the surface to 10,000 unless otherwise coordinated. c. Departures: 1. Vector all turbojets departing KALB/KSCH requesting flight levels and flight planned over ARNII, PAYGE, SYR, SAX, CMK, JFK, IGN, DBABE or JEFFF to the vicinity of the ALB343025 fix. Hand these aircraft to CTR on the appropriate heading and coordinate with CTR that the aircraft are on a heading. CTR will issue on course passing approximately 14,000. 2. Vector all aircraft requesting 11,000 feet MSL or above and flight planned over DNY, RKA, GGT or UCA direct to or in the vicinity of the CEDOR intersection, then on course. 3. Traffic permitting, the departure controller shall instruct VFR aircraft to proceed on course and/or climb to their requested altitude. Proceed on course, maintain appropriate VFR altitudes. BVA Albany ATCT Standard Operating Procedures Page 9
d. Arrivals: 1. When a split is active, both controllers shall coordinate which position shall work final vectors to Runways 1/19 and the transfer control point for final vectors. ALB_W_APP defaults to this position unless otherwise coordinated. 2. Handoffs of ALB arrivals to ALB_F_APP should be initiated as soon as practical after a runway has been assigned. This gives Final more awareness of the location and volume of arrival traffic. 3. Do not take any action to establish approach sequence at ALB without coordination with ALB_F_APP. For example, do not instruct an ALB arrival to join the localizer for an active runway without coordination with ALB_F_APP. 4. Aircraft assigned other than the active runway(s) or other than the primary approach (ILS) may have this information displayed in their scratchpad prior to handing off to Final. e. Intrafacility Coordination: 1. Traffic landing ALB should be handed to ALB_F_APP between 4,000' and 5,000'. During periods of heavy traffic, arrivals should also be assigned 210 knots or less, or as directed by ALB_F_APP. 2. ALB_F_APP has control (on contact) for turns up to 90, descent, and speed reduction on all traffic landing ALB. 3. Transfer communications of ALB arrivals to ALB_F_APP as soon as practical to allow them to be fit into the traffic flow. Do not retain an ALB arrival on frequency when no longer required. 4. Coordinate with ALB_F_APP to determine how missed approaches will re-enter Final airspace. f. Approaches to Intersecting Runways: 1. When approaches are being conducted to intersecting runways (Runway 1/19 and Runway 10/28), ensure that the following is met: (a) Arrivals shall be staggered so that if both aircraft executed a go around, the trailing aircraft would be at least 1nm from the runway threshold when the lead aircraft is directly over the intersection of the two runways. BVA Albany ATCT Standard Operating Procedures Page 10
2. LAHSO: (b) Ensure that aircraft are transferred to ALB_TWR prior to reaching a point 5nm from KALB. (c) Assuming a no-wind condition and equal ground speeds, attempt to establish the trailing aircraft at a point 2nm further from the airport than the leading aircraft. Be sure to take into account upper wind when assigning final approach speeds and spacing. (a) LAHSO operations are authorized on the following runways: (1) Rwy 01: Hold Short 10/28. Distance available 4150. (2) Rwy 28: Hold Short 01/19. Distance available 3750. (b) Co-ordinate all LAHSO operations with ALB_TWR. BVA Albany ATCT Standard Operating Procedures Page 11
Chapter 6: Interfacility Coordination a. Airspace delegation overview: BVA Albany ATCT Standard Operating Procedures Page 12
b. ALB ATCT and Y90 TRACON: 1. Control on Contact: (a) ALB has control for turns and descent west of V93 for approaches to PSF and 1B1 upon communications transfer. (b) Except as described above, each facility has control on contact for turns up to 30 degrees. 2. Route traffic via any appropriate preferred route. Altitudes assigned shall be appropriate for direction flight. 3. Consistent with the flight plan, traffic may be cleared direct to the first NAVAID within the receiving facilities airspace without prior coordination. 4. Y90 to ALB: (a) Verbally coordinate any aircraft operating at and below 4,000, except for operations at GBR. 5. Delegated airspace: BVA Albany ATCT Standard Operating Procedures Page 13
c. ALB ATCT and N90 TRACON: 1. ALB to N90: (a) Traffic landing at LIB area airports (SWF, POU, MSV, MGJ, 06N, 44N, 46N, N69, N82, 20N) shall be routed via V123 TRESA at 4,000. (b) Traffic landing all other N90 airports (including JFK/LGA/EWR) shall be routed via V157 IGN at 4,000. 2. N90 to ALB: d. ALB ATCT and ZBW: (a) Traffic landing within the Albany TRACON shall be routed via V157 ATHOS at 5,000. (b) All ALB overflight traffic with a final altitude at or below 10,000 shall be routed via PWL021 HIDAL V487 CANAN at 5,000. 1. Control on contact: (a) ALB has control for descent on aircraft landing KGFL when the aircraft is within 10NM of the boundary. (b) ALB has control of arriving aircraft for turns of up to 45 degrees when the aircraft is within the lateral confines of TRACON airspace. (c) ZBW has control for turns of up to 45 degrees above 4,000 feet, on contact. 2. ZBW to ALB: (a) Traffic routed to KALB or KSCH shall cross 30nm from the ALB VORTAC at 11,000. (b) Traffic routed to any other airport within ALB ATCT shall be manually coordinated. (c) VFR aircraft may be handed off automatically without the need for manual coordination. (d) Traffic may be cleared direct to the ALB VORTAC. BVA Albany ATCT Standard Operating Procedures Page 14
3. ALB to ZBW: (a) ALB shall clear all departures on course and issue a climb to 10,000 or lower cruise altitude before transferring communications to ZBW, except as described in sub-paragraph (b) below. (b) ALB shall vector all aircraft requesting flight levels to the vicinity of the ALB343R 25DME fix to allow time for climb. This ensures separation with aircraft descending into N90 airspace. (c) ALB shall ensure that aircraft in-trail on the same route are handed off to Center with 10nm constant spacing or at least 5nm and increasing. BVA Albany ATCT Standard Operating Procedures Page 15
Chapter 7: Appendices 7.1 Approach Control Airspace Running West Radar as Final 1/19: BVA Albany ATCT Standard Operating Procedures Page 16
Running East Radar as Final 1/19: BVA Albany ATCT Standard Operating Procedures Page 17
Three-Way Split, Landing Runway 1: BVA Albany ATCT Standard Operating Procedures Page 18
Three-Way Split, Landing Runway 19: BVA Albany ATCT Standard Operating Procedures Page 19
Three-Way Split, Landing Runway 28: BVA Albany ATCT Standard Operating Procedures Page 20
7.2 Intersection Departure Distances BVA Albany ATCT Standard Operating Procedures Page 21