Boston Center Standard Operating Procedures

Size: px

Start display at page:

Download "Boston Center Standard Operating Procedures"

Veronica Jemimah Farmer
5 years ago
Views:

These procedures are approved for use as defined by the Boston Virtual ARTCC Administration Team only.

1 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. For more information about Boston Virtual ARTCC, visit Boston Center Standard Operating Procedures Version F November 8, 2018 bvartcc.com

2 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 F November 8, 2018 Updates airspace delegation with ZNY as result of an LOA change Page 20 Version E August 22, 2018 Version D inadvertently removed certain ZNY LOA procedures. These procedures have been added back in this version Page 16 Version D July 18, 2018 Updates ZNY/N90 handoff procedures Page 16 Air Traffic Control: Boston Center Standard Operating Procedures Page 1

Chapter 1: General 1.1 Purpose This SOP prescribes facility-specific procedures for Boston Center. 1.2 Airspace a. Boston Center (ZBW) is responsible for all controlled airspace (i.e., up to FL600) within the ARTCC that is not being provided services by another controller.

3 Chapter 1: General 1.1 Purpose This SOP prescribes facility-specific procedures for Boston Center. 1.2 Airspace a. Boston Center (ZBW) is responsible for all controlled airspace (i.e., up to FL600) within the ARTCC that is not being provided services by another controller. b. Center controllers shall be comfortable and competent with all procedures for coordination with the adjacent ARTCCs/FIRs, including ZNY, ZDC, ZOB, CYUL, CZYZ, and CZQM, including knowledge of, and proficiency with, the Letters of Agreement (LOA) in place with adjacent centers. This document contains a summary of required LOA information. c. ZBW airspace contains several shelves that apply with ZBW TRACONs, the N90 TRACON, and adjacent ARTCCs/FIRs. Airspace delegation is included in the appendices. Air Traffic Control: Boston Center Standard Operating Procedures Page 2

4 1.3 ATIS Procedures a. If CTR decides to publish an ATIS, the ATIS shall normally be published for KBOS. When a KBOS ATIS is already published, CTR may decide to publish an ATIS at one other facility if it is operationally advantageous to do so. 1.4 Separation a. ZBW has a waiver allowing for the following reduced separation between aircraft: (1) At or below FL230 3 miles b. All wake turbulence restrictions continue to apply. 1.5 Datablock Formatting a. For aircraft climbing to an altitude lower than the flight planned altitude: (1) If the altitude is consistent with an LOA or SOP procedure, no entry. (2) If the altitude is non-standard or not contained within this LOA, a temporary altitude reflecting the cleared altitude. b. For aircraft descending to meet an issued crossing restriction, a temporary altitude with the applicable crossing altitude. c. For aircraft descending to an assigned altitude, no temporary altitude is used, and the filed/planned altitude is amended to the new cleared/assigned altitude. d. Scratchpad entries shall only be used if specific control instructions differing from SOP/LOA have been issued. These instructions shall be verbally coordinated unless standing verbal coordination has been effected. (1) Indicated speeds (e.g., S210, S270+ ) (2) M for Mach speed restrictions (e.g., M81, M78+ ) (3) H for heading assignments (e.g., H230, H15L (fifteen degrees left of track)) e. When an aircraft is leaving our ARTCC and the adjacent facility is offline, remove any scratchpad entries and temporary altitudes. Air Traffic Control: Boston Center Standard Operating Procedures Page 3

5 1.6 Splitting Boston Center a. When Boston Center is combined, it will be as BOS_CTR on frequency b. Prior to splitting Boston Center, at least the Boston Core Area of A90 shall be staffed. c. The most common geographical split is East/West (2WAY E/W). Another less common split is 2WAY N/S. A three-way split (W/E/SW) is often used during busy events to separate ROBUC arrival traffic from BOS-N90 aircraft. d. If an operational advantage will be gained, the airspace may also be split High/Low using the same geographic boundaries. e. The most common geographical ZBW splits are shown below. Any time ZBW is split, controllers shall brief control for each sector and sector altitudes. The following items shall be coordinated: (1) With adjacent Center sectors: airspace and altitudes, control on contact, preapproved coordination, ownership of unstaffed TRACONs (2) With underlying TRACONs: sectors and airspace (3) With adjacent facility controllers: sectors and airspace f. Do not assume that adjacent facility controllers or underlying TRACON controllers will be familiar with published ZBW splits. Center controllers are encouraged to use the images in this document when briefing underlying and adjacent facilities. g. As a standard, and unless otherwise depicted: (1) All Low (L) sectors own surface (or TRACON ceiling) to FL230 (2) All High (H) sectors own FL240 to FL600 Air Traffic Control: Boston Center Standard Operating Procedures Page 4

6 1.7 Available Splits (a). Two-Way Geographical Split (E/W), both sectors high-low: (i). Area 4 is GDM36 to FL230, PARSO16 above. A90 departures go to GDM36. (b). Two-Way Geographical Split (N/S), both sectors high-low: Air Traffic Control: Boston Center Standard Operating Procedures Page 5

(c). Three-Way Geographical Split: (i). Areas 1, 2, and 3 are normally consolidated as DXR19. This sector handles ROBUC and JFK arrival traffic. (ii). In Areas 1-2, DXR19 owns up to FL270. (iii).

7 (c). Three-Way Geographical Split: (i). Areas 1, 2, and 3 are normally consolidated as DXR19. This sector handles ROBUC and JFK arrival traffic. (ii). In Areas 1-2, DXR19 owns up to FL270. (iii). In Area 3, DXR19 owns up to FL230. PARSO16 owns the airspace above DXR19. (iv). Area 4 is GDM36 to FL230, PARSO16 above. A90 departures go to GDM36. (v). If unstaffed, PVD shall be on PARSO16 and Y90 shall be on by GDM36. Air Traffic Control: Boston Center Standard Operating Procedures Page 6

(vi). For heavy BOS arrival traffic situations, Areas 2-3 may be split off from Area 1. In this case, Areas 2-3 will be DXR19 (BOS_A_CTR on 134.00).

In this case, CLIPPER32 will own to FL270 in Area 1, and FL240+ in Area 3.

8 (vi). For heavy BOS arrival traffic situations, Areas 2-3 may be split off from Area 1. In this case, Areas 2-3 will be DXR19 (BOS_A_CTR on ). Area 1 will be consolidated on PARSO16: (vii). When operationally advantageous, JFK arrival traffic can be sectored off from the southwest sector. In this case, CLIPPER32 will own to FL270 in Area 1, and FL240+ in Area 3. PARSO16 shall handoff JFK-ENE traffic at FL340, and JFK- PLYMM traffic at FL320 to CLIPPER32. GDM36 will cover ROBUC arrivals, owning up to FL270 in Area 2, and to FL230 in Area 3. PARSO16 will own above FL280 in Area 1. Air Traffic Control: Boston Center Standard Operating Procedures Page 7

9 (d). Three-Way Geographical Split with a High Sector: (i). Areas 1, 2, and 3 are normally consolidated as DXR19. This sector handles ROBUC and JFK arrival traffic. (ii). In Areas 1-2, DXR19 owns up to FL270. (iii). In Area 3, DXR19 owns up to FL230. (iv). BOS46 owns all airspace above FL240 except in Areas 1 and 2, where BOS46 has control above FL280. (v). Area 4 is GDM36 to FL230, PARSO16 above. A90 departures go to GDM36. (vi). If unstaffed, PVD shall be on PARSO16 and Y90 shall be on by GDM36. Air Traffic Control: Boston Center Standard Operating Procedures Page 8

(vii). For heavy BOS arrival traffic situations, Areas 2-3 may be split off from Area 1. In this case, Areas 2-3 will be DXR19 (BOS_A_CTR on 134.00).

When operationally advantageous, JFK arrival traffic can be separated from the southwest sector. In this case, CLIPPER32 will own to FL270 in Area 1, and FL240+ in Area 3.

10 (vii). For heavy BOS arrival traffic situations, Areas 2-3 may be split off from Area 1. In this case, Areas 2-3 will be DXR19 (BOS_A_CTR on ). Area 1 will be consolidated on PARSO16 at FL230 and below. BOS46 owns all airspace above FL240 except in Area 2, where BOS46 has control above FL280. (viii). When operationally advantageous, JFK arrival traffic can be separated from the southwest sector. In this case, CLIPPER32 will own to FL270 in Area 1, and FL240+ in Area 3. BOS46 shall handoff JFK-ENE traffic at FL340, and JFK- PLYMM traffic at FL320 to CLIPPER32. GDM36 will cover ROBUC arrivals, owning up to FL270 in Area 2, and to FL230 in Area 3. BOS46 owns all airspace above FL240 except in Areas 1 and 2, where BOS46 has control above FL280. Air Traffic Control: Boston Center Standard Operating Procedures Page 9

11 (e). Four-Way Geographical Split: (i). DXR19 controls Area 2, and Area 3 up to FL230 for ROBUC traffic. (ii). CLIPPER32 controls Area 1 and Area 3 above FL240 for JFK arrival traffic. (iii). PARSO16 shall handoff JFK-ENE traffic at FL340, and JFK-PLYMM traffic at FL320 to CLIPPER32. (iv). Area 4 is GDM36 to FL230, PARSO16 above. A90 departures go to GDM36. (v). If unstaffed, PVD shall be on PARSO16 and Y90 shall be on by GDM36. Air Traffic Control: Boston Center Standard Operating Procedures Page 10

12 (f). Four-Way Geographical Split with a High Sector: (i). DXR19 controls Area 2 up to FL270 and Area 3 up to FL230 for ROBUC traffic. (ii). CLIPPER32 controls Area 1 and Area 3 above FL240 for JFK arrival traffic. (iii). BOS46 controls all airspace above FL240 in Areas 4-6. In Areas 1-2, BOS46 controls above FL280. BOS46 has no control in Area 3. BOS46 shall handoff JFK-ENE traffic at FL340, and JFK-PLYMM traffic at FL320 to CLIPPER32. (iv). Area 4 is GDM36 to FL230, PARSO16 above. A90 departures go to GDM36. (v). If unstaffed, PVD shall be on PARSO16 and Y90 shall be on by GDM36. Air Traffic Control: Boston Center Standard Operating Procedures Page 11

13 Chapter 2: Airport Operations 2.1 BOS and Satellite Operations Routing a. Clear jet aircraft that have RNAV capability and an updated navigation database via an RNAV STAR (ROBUC, JFUND, OOSHN) as filed or appropriate to the route of flight. b. Clear non-jet aircraft, non-rnav aircraft, and aircraft without a current navigation database via a conventional STAR (ORW, GDM, or WOONS) as filed or appropriate to the route of flight. The ORW STAR parallels the ROBUC STAR, and the GDM STAR parallels the JFUND STAR. The WOONS STAR is used for non-jet aircraft arriving from the southwest. c. For aircraft that are not able to fly any of the arrival procedures, attempt to assign a route that closely matches the lateral path of the appropriate STAR. Do not allow these aircraft to fly an outdated arrival procedure. (1) Arrivals via GDM: (route) ALB GDM LOBBY. Instruct aircraft to cross LOBBY intersection as prescribed on GDM STAR. (2) Arrivals via ORW: (route) JFK PVD (if able, KRANN) (a). Aircraft able KRANN: (i). Instruct to cross KRANN at 11,000 and 270 knots, unless landing 4L/R in which case cross PVD at 11,000 and 250 knots (ii). Aircraft unable KRANN should be instructed to depart PVD on a 075 heading and be given a manual descent to reach KRANN at and 250 knots (b). Other arrivals: Route appropriate to direction of flight. Coordinate with other controllers as necessary. d. Note that all arrival procedures except the WOONS and GDM STARs are restricted to turbojet aircraft only. Non-jet aircraft should file the WOONS arrival, GDM arrival, or another route. Arrival Procedures a. On descend via STARs into A90, ZBW shall assign descend via and the primary runway transition. ZBW shall assign the database a temporary altitude of 111. b. On all other STARs or routes, ZBW shall issue or descend to the crossing restrictions below. Air Traffic Control: Boston Center Standard Operating Procedures Page 12

14 A90 STARs STAR / Route Type Location Instruction Remark Coordination Landing BOS and Applicable Satellites CON TOMIE LWM BOS Any CON 11,000 Cruise Alt 110 GDM GDM-15 Turbojet LOBBY 11,000 Non-Jet LOBBY 9,000 Turbojet LOBBY 8,000 Landing Runway 15 Non-Jet LOBBY 7,000 All a/c 5nm in-trail Temp Alt crossing Restriction JFUND Turbojet ALB Descend via Temp Alt 111 ORW ORW-4 Turbojet KRANN PVD 11, KIAS 11, KIAS Temp Alt 110 ORW-15 Turbojet PVD 11,000 ROBUC Turbojet Before FEXXX Descend via Issue direct ROBUC or PROVI if traffic permits Temp Alt 111 JEWIT 11, KIAS Temp Alt 110 WOONS Non-Jet 7,000 Landing BOS WOONS 3,000 Landing OWD, 1B9, GHG Temp Alt 070 OOSHN Turbojet AJJAY or ENE Descend via Temp Alt 111 DCT SCUPP Any SCUPP 11, KIAS if landing Runway 27 Temp Alt 110 ENE PSM STEVO Any ENE 11,000 Temp Alt 110 Air Traffic Control: Boston Center Standard Operating Procedures Page 13

15 STAR / Route Type Location Instruction Remark Coordination Landing MHT POPPP Any POPPP 9,000 Temp Alt 090 ROZZE Turbojet ALB Descend via Temp Alt 111 DCT MHT Any Border AOB 7,000, descending to 5,000 Landing BED Cruise Alt 050 DREEM Any GASSE 5,000 Temp Alt 050 BLATT (ORW Trans) AOB 11,000 GRAYM Any DVANY (HFD Trans) AOB 11,000 Temp Alt 050 ZELKA Turbojet or Turboprop GASSE (All) 5,000 ALB Descend via Temp Alt 111 Air Traffic Control: Boston Center Standard Operating Procedures Page 14

16 2.2 ZBW Other Facility STARs Landing STAR / Route Type Location Instruction KACK DEEPO1 NEWBE1 DCT DEEPO Any DEEPO 11,000 DPK Any DPK FL190 MAD 11,000 KBDL STELA Any SWEDE AOB FL230 CAM 17,000 ALB 15,000 STELA 11,000 JORDN RNAV JORDN 11,000 HTO R-070 to join PVD R-195 Non-RNAV 20nm NE of HTO 11,000 HINGZ FL290 KPVD WIPOR RNAV NELIE 20nm NW AOB FL210 WIPOR 11,000 ORW V130 MINNK Non-RNAV 10nm prior to ORW 11,000 V188 GON MINNK Non-RNAV GON 11,000 KPWM SCOGS RNAV SCOGS 11,000 CDOGG RNAV CDOGG 11,000 KALB Any Border 11,000 All Other Airports KBGR Border 11,000 11,000 KBTV Border 11,000 11,000 KSYR Border 11,000 11,000 Air Traffic Control: Boston Center Standard Operating Procedures Page 15

17 2.3 Adjacent ARTCC STARs and LOA Procedures Arrival Procedure A/C Type Wpt. Instruction Handoff Cleveland Center KROC N/A All Boundary Lowest usable FL Boundary KBUF or KIAG N/A All Boundary At or below FL270, descending FL240 Boundary IAD J59 All Boundary At or below FL300 Boundary YYZ, YTZ, YKZ N/A All Boundary At or below FL320 Boundary Arrival A/C Type Route Segment Remarks KDCA Jet Non-RNAV Jet RNAV Washington Center J174 ZIZZI ATR085 ATR V308 BILIT J75 MXE CLIPR# J174 ZIZZI ATR085 ATR V308 LAFLN DEALE# Overload RNAV KDCA or KADW Non-Jet J174 ZIZZI ATR085 ATR V308 OTT FL240 FL280 KADW Jet J174 ZIZZI ATR085 ATR V308 OTT KBWI Jet Non-RNAV Jet RNAV J174 ZIZZI ATR085 ATR V308 BILIT J75 MXE NUGGY TRISH# Arrival Direction Route Altitude CYUL CYOW CYMX CYHU Montreal Center In-Trail with DCA/BWI From the South CARTR# EBDOT at 11,000 From the West DAVDA IMPAC# AOB FL280 From the East BUGSY DEANS# AOB FL220 From the South CYRIL DEANS# CYRIL at 11,000 From the West ART CYRIL DEANS# AOB FL280 Any LATSS EBDOT DUNUP or DCT EBDOT EBDOT at 11,000 CYFJ Any N/A AOB FL280 Arrival CYFC, CYSU, CYQI, CYCL CYHZ Moncton Center Restriction Cross the boundary at or below FL280. Arrivals via YSC or BGR direct or vectored to YZX NDB then flight plan route. RNAV-capable arrivals routed via FUNDY1 arrival (EBONY or ALLEX) and PEGGY1 (via TUSKY or ELERY) Air Traffic Control: Boston Center Standard Operating Procedures Page 16

18 Arrival Procedure A/C Type Wpt. Instr. Handoff New York Center PHL North Sats, WRI J121 or V139 Any Boundary AOB 16,000 Boundary ACY, PHL, WRI, and Sats DNY (SPUDS) FL190+ HARVA FL190 Boundary J121 (BRIGS/VCN) FL190+ Boundary FL200 ZNY if open, V268/V308/DRIFT Non-jet Boundary AOB 16,000 or ZDC DOV J121 Any Boundary AOB FL220 Boundary AVP LAAYK or LVZ Any Boundary AOB 14,000 Boundary BWI / DCA Above FL240 via J75 Boundary FL Boundary Boundary IAD / Sats HYPER Turbo Boundary FL Boundary J49 or PRIVO Non-Turbo Boundary AOB FL300 Boundary HNK V576 or CFB V423 FQM Turboprop Boundary AOB FL220 Boundary PIT / Sats HNK Any HNK FL280 Boundary Arrival Procedure A/C Type Wpt. Instr. Handoff Frequency New York TRACON NOTE: The Frequency column presents the appropriate N90 sector for handoffs. The frequencies are presented in the order of precedence. The bold frequency indicates the most common handoff (as normally sectors are consolidated to this frequency). N90 sometimes combines the entire TRACON to one position. If the entire TRACON is combined, the handoff shall be initiated to the consolidated position. JFK ROBER PARCH Direct ROBER Turbojet CCC 15nm E ROBER 12, KIAS 10nm east of 12,000 CCC 250 KIAS LOVES Multiple LOVES 6,000 Boundary IGN 250+ IAS LOLLY FL200 LOLLY N2K N2G N3H N2K N2G N N N2G BDR FRG HVN PWL Prop LOVES 6,000 PWL Multiple Multiple LOVES 6,000 PWL N3H N2K N2G Air Traffic Control: Boston Center Standard Operating Procedures Page 17

19 Arrival Procedure A/C Type Wpt. Instr. Handoff Frequency New York TRACON NOBBI Prop NOBBI 8,000 PWL LGA EWR and Sats HAARP 250+ IAS BASYE 8,000 VALRE Via IGN-VALRE Any VALRE 8,000 VALRE SHAFF FLOSI V489 COATE Runway 16 in use Multiple CRANK 7,000 EWR props; Sats all types Any 5nm prior to CRANK LEMOR 6,000 Boundary Direct FARAN Join loc. at 4,000 Boundary VALRE Turbo VALRE 6,000 Boundary NOBBI Non-Turbo NOBBI 6,000 Boundary N1V N4A N4P N4S N4U N4A N4P N1X N1V HPN SWF ISP Via HTO from E Jet HTO 11,000 Boundary N3B N3H RICED Any RICED 9,000 Boundary N2K N2G BOUNO Jet DPK 15, KIAS Boundary N3Z N3H N2K N2G Direct TRESA or Jet TRESA 6,000 Boundary N5H HUD STAR N5D FILPS Jet FILPS 7,000 Boundary N2G J121/V268 HTO SARDI Any SARDI 7,000 Boundary N3H N2K N2G LOVES 250+ IAS LOVES 6,000 Boundary NELIE RNAV Boundary 8,000 Boundary N3B N3H N2K N2G Air Traffic Control: Boston Center Standard Operating Procedures Page 18

20 2.4 Departures from Uncontrolled or ZBW Tower Controlled Airports (veram) a. At the time a clearance is issued for an aircraft departing an uncontrolled airport, or releasing an aircraft from a tower controlled airport that ZBW provides terminal services for (e.g., KLEB): (1) Issue a DM message (2) Start a full data block at the departure airport with: (a). Interim altitude if different than requested altitude (b). In the free-text scratchpad, the clearance void time of the flight (note: if the flight is a PRP flight, PRP shall be used instead of the clearance void time) Air Traffic Control: Boston Center Standard Operating Procedures Page 19

21 Chapter 3: Appendixes 3.1 Airspace Delegation a. West (ZNY and ZOB) The floor altitude of ZBW control will be shown for each of these sectors when the Static Text is enabled in VRC. Air Traffic Control: Boston Center Standard Operating Procedures Page 20

Typically, if consolidated, N90 will be on NY_CAM_APP on 128.12. However, N90 may sometimes consolidate on a different callsign.

22 b. West (Handoffs to N90) The N90 area is often consolidated. ZBW controllers are encouraged to check the Controller Information published by N90 controllers to determine which sectors are active. Typically, if consolidated, N90 will be on NY_CAM_APP on However, N90 may sometimes consolidate on a different callsign. If the applicable N90 sectors are offline, aircraft are transferred to ZNY. Aircraft entering N90 airspace at or below 10,000 not covered by the tables above shall be transferred to: Air Traffic Control: Boston Center Standard Operating Procedures Page 21

23 c. North (ZUL) The airspace at and below 6,000 is delegated to Boston Center as shown below: Air Traffic Control: Boston Center Standard Operating Procedures Page 22

24 3.2 ZBW Positions, Sector IDs, and Frequencies The following list is provided for reference purposes. In all cases, the Vox Channel for any position will be ZBW_, followed by the 7-digit frequency entry (i.e., ZBW_ ). Sector High/Low Frequency Sector High/Low Frequency Area A Area D ART08 Low MLT01 High UCA09 High AUG02 High RKA10 Super High SURREY15 Low ALB22 Low PARSO16 Low HNK23 Low ACK17 Low/High DNY24 High CAPE18 Low/High Area B Area E GDM36 Low SWF05 Low CON37 Low PWL06 Low ATHENS38 High CTR07 Low CAM39 High DXR19 Low MPV52 Low IGN20 High PLB53 High CANAN21 Low Area C HTO31 High CLIPPER32 Low ERICK33 Low PVD34 Low BOS46 High BOSOX47 Low SOUTHIE49 High Air Traffic Control: Boston Center Standard Operating Procedures Page 23

25 3.3 Real-World ZBW Splits Low Altitude Air Traffic Control: Boston Center Standard Operating Procedures Page 24

26 3.4 Real-World ZBW Splits High Altitude Air Traffic Control: Boston Center Standard Operating Procedures Page 25

vzny ARTCC & vzbw ARTCC

vzny ARTCC & vzbw ARTCC Effective: 06 May 2007 Amended: 05 January 2012 Letter of Agreement v ARTCC & vzbw ARTCC 1. PURPOSE This agreement defines the necessary pre-defined air traffic control procedures and coordination responsibilities