vzny ARTCC & vzbw ARTCC

Similar documents
Cleveland ARTCC and Boston Virtual ARTCC Letter of Agreement

RELEASE RECORD. Version Date Author Notes Dec 2006 SK Initial Release

Albany ATCT Standard Operating Procedures

Boston Center Standard Operating Procedures

BOSTON ARTCC (vzbw) STANDARD OPERATING PROCEDURE KALB) ALBANY APPROACH (ALB

Standard Operating Procedures

Version O January 21, 2019

Providence ATCT Standard Operating Procedures

Burlington ATCT Standard Operating Procedures

11/21/2008 ZDC-ZTL LOA Version 1. Letter of Agreement

Chapter 1 General Information

Standard Operating Procedures

ERIE ATCT STANDARD OPERATING PROCEDURES

VIRTUAL AIR TRAFFIC SIMULATION NETWORK NORTH AMERICA REGION - USA DIVISION vzkc KANSAS CITY ARTCC

New York ARTCC (ZNY) & Potomac TRACON (PCT)

VATUSA-VATNZ-VATPAC OCEANIC PARTNERSHIP OAKLAND OCEANIC FSS GENERAL SOP 1 OCT 2012

Letter of Agreement (LOA)

VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT

Letter of Agreement between Indianapolis & Washington Air Route Traffic Centers

Virtual Jacksonville Air Route Traffic Control Center Tallahassee ATCT Standard Operating Procedures

Greenville Spartanburg International

GENERAL OPERATING PROCEDURES FINLAND(GOP)

LETTER OF AGREEMENT. Between

ZTL ARTCC. Augusta Regional

ZTL ARTCC / CLT ATCT LETTER OF AGREEMENT. EFFECTIVE: July 10, SUBJECT: APPROACH CONTROL SERVICE

Cape Area Airports Standard Operating Procedures

ZTL ARTCC. Asheville Regional. Air Traffic Control Tower. Standard Operating Procedures AVL B. Effective: May 1, 2011

VATUSA CHICAGO ARTCC AND VATUSA INDIANAPOLIS ARTCC LETTER OF AGREEMENT EFFECTIVE: 10/15/2018 SUBJECT: INTERFACILITY COORDINATION

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

SEATTLE AIR ROUTE TRAFFIC CONTROL CENTER SEATTLE GLIDER COUNCIL LETTER OF AGREEMENT. EFFECTIVE: June 1, 2015

VATUSA Approval 3/21/18

Piedmont Triad International Airport

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

VATUSA CHICAGO ARTCC AND VATUSA INDIANAPOLIS ARTCC LETTER OF AGREEMENT EFFECTIVE: 01/01/2017 SUBJECT: INTERFACILITY COORDINATION

VATUSA PHOENIX TRACON and VATUSA PHOENIX ATCT LETTER OF AGREEMENT. SUBJECT: Interfacility Coordination Procedures

- Initial. - Added MCRAY and new PDC s. - General update. - Added ATIS frequency - Added gate diagram appendix - Typo fixes - Minor formatting changes

STANDARD OPERATING PROCEDURES (CLE SOP) December 3, 2016

- Updated formatting - Re-drawn airspace delegation diagram

VATUSA C90 TRACON AND O HARE ATCT LETTER OF AGREEMENT

ATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT

Virtual Air Traffic Simulation Network (VATSIM) United States Division Fort Worth vartcc (ZFW)

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

BOSTON ARTCC (vzbw) TRAINING SYLLABUS LEVEL: Center Controller (C1)

VATUSA CHICAGO ARTCC AND VATUSA MINNEAPOLIS ARTCC LETTER OF AGREEMENT

LETTER OF AGREEMENT BETWEEN DENMARK FIR AND SWEDEN FIR. VATSIM Scandinavia 4 April 2013

LETTER OF AGREEMENT 1. PURPOSE: 2. Cancellation: 3. vzdc Responsibilities, Arrivals: CAE MYR: FLO: CLT: 4. vzjx Responsibilities, Arrivals: RDU: FAY

Letter of Agreement. Between Jacksonville ARTCC and Virtual United States Navy Effective Date: Sept 1, 2008

VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

Charlotte - Douglas International Airport Traffic Control Tower

Oakland Air Route Traffic Control Center, Northern California Terminal Radar Approach Control, and Pacific Soaring Council LETTER OF AGREEMENT

VIRTUAL AIR TRAFFIC SIMULATION NETWORK UNITED STATES DIVISION. SUBJ: Phoenix (PHX) Air Traffic Control Tower (ATCT) Standard Operating Procedures

Jacksonville ARTCC. F11 TRACON Standard Operating Procedures

Standard Operating Procedures

FLIGHT ADVISORY NATIONAL SPECIAL SECURITY EVENT UNITED NATIONS GENERAL ASSEMBLY UNGA-67 SEPTEMBER 18, 2012 September 28, 2012

SECTION 6 - SEPARATION STANDARDS

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

PITTSBURGH ATCT STANDARD OPERATING PROCEDURES

Albuquerque Center Standard Operating Procedures

Updates rules applying to Test Corrections Page 6

D01 TERMINAL RADAR APPROACH CONTROL

Boston Consolidated TRACON (A90) Standard Operating Procedures

SOUTHERN CALIFORNIA TRACON STANDARD OPERATING PROCEDURES VIRTUAL AIR TRAFFIC SIMULATION NETWORK LOS ANGELES ARTCC

ALTIMETER SETTING PROCEDURES

New York ARTCC. ZNY Basic SOP. General Notes:

Chapter 6. Brize Radar, Speedbird 213 Heavy, request radar advisory. Speedbird 123 change call sign to BA 123

Object: LoA between the Barcelona FIR (LECB) and the Bordeaux FIR (LFBB)

Eastern Caribbean PIARCO Virtual FIR. PIARCO Control Zone (CTR)

AIRSPACE STRUCTURE. In aeronautics, airspaces are the portion of the atmosphere controlled by a country above its territory.

Denmark FIR and Sweden FIR

USE OF RADAR IN THE APPROACH CONTROL SERVICE

IVAO Switzerland Division

CHAPTER 5 SEPARATION METHODS AND MINIMA

Consider problems and make specific recommendations concerning the provision of ATS/AIS/SAR in the Asia Pacific Region LOST COMMUNICATION PROCEDURES

International Virtual Aviation Organisation. Letter of Agreement. between. and. Effective: 15/05/2017 Edition: 1

Letter of Agreement. between. and

HOUSTON AIR ROUTE TRAFFIC CONTROL CENTER VATSIM United States Division. Letter of Agreement. Revised: July 25, 2004 Effective: July 25, 2004

VIRTUAL UNITED STATES NAVY (VUSN) AND MIAMI CENTER (ZMA) LETTER OF AGREEMENT Effective: 06 JAN 2004

THE AREA CONTROL CENTRE (CTR) POSITION

LETTER OF AGREEMENT BETWEEN NORWAY FIR AND DENMARK FIR

Holland-America Line Pilot Briefing. December 14, bvartcc.com

Order ZNY B. Traffic Management Unit Standard Operating Procedures. December 1, 2010

WASHINGTON DULLES ATCT STANDARD OPERATING PROCEDURES

Letter of Agreement. IVAO Switzerland & France Divisions. 1. Purpose. 2. General procedures

IVAO Flight Operations Department Indonesia (ID) Division Procedures

Cleveland Air Route Traffic Control Center (ARTCC) - ZOB Basic Control Procedures Version 1.00 March 25, 2019

2 Purpose and Need. 2.1 The Need for the CLT OAPM Project Description of the Problem

LETTER OF AGREEMENT (LOA)

Letter of Agreement. between

Operating Procedures. For the Provision of Air Traffic Control Services. RAF Mount Pleasant EGYP. Falklands Islands. RAF Monte Agradable EGYP

VATSIM LOS ANGELES ARTCC STANDARD OPERATING PROCEDURES

LETTER OF AGREEMENT BETWEEN POLISH VACC AND SWEDEN FIR

Arash Yousefi George L. Donohue, Ph.D. Chun-Hung Chen, Ph.D.

The Anatomy of Delays:

CLEARANCE INSTRUCTION READ BACK

Anchorage Radio Standard Operating Guidelines

GNSS/RNAV Non- Radar Longitudinal Separation in the Caribbean

Charlotte - Douglas International

Standard Operating Procedures Atlanta Intl Airport (ATL) Air Traffic Control

MINIMUM FLIGHT ALTITUDES

Standard Operating Procedures (SOPs) for Arabian Control (OGCC)

Transcription:

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 between the Virtual Boston ARTCC (vzbw) and the Virtual New York ARTCC (v) 2. DISCLOSURE vzbw and v are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and shall never be used for actual flight or air traffic control operations. vzbw and v are not affiliated with the FAA in any manner. 3. GENERAL PROCEDURES: A. vzbw/v ATC shall at all times 1) Coordinate and resolve, in a practical manner that provides the smoothest experience to the pilot, all deviations from, and situations not addressed by, this document (e.g. nonstandard sectorization, holding, pilots unable to accept LOA routes, aircraft above/below LOA altitudes, etc.). 2) Ensure that all aircraft are at a 1X simulation rate prior to initiating handoff 3) Ensure that aircraft on the same route segment at the same altitude are separated by not less than 10 nm (steady or increasing) or other valued specified herein unless greater MIT separation is requested real-time by vzbw/v NOTE: Separation of less than 10 nm is permitted provided that the trailing aircraft has enough groundspeed to complete an overtake in adequate time and both are in level flight at different altitudes. 4) Ensure that handoff requests are made at least 10 nm prior to the relevant airspace boundary unless otherwise specified in this document. Handoff requests may be initiated up to 50 nm without prior coordination. 5) Ensure that all conflicts, imminent situations, and MIT separation issues are resolved prior to handoff, or the handoff may be subject to refusal. 6) Ensure that all scratchpad entries are cleared unless required to convey operational information (e.g..80 for assigned Mach number, H### for assigned heading) not coordinated by other means (e.g. private message, verbally, etc.). vzbw/v LOA 1 EFF: 01/05/2012

4. AIR TRAFFIC PROCEDURES: A. GENERAL 1) Without prior coordination, New York Center may: a. Turn aircraft 30 degrees left or right of track on contact b. Clear aircraft direct the following waypoints within vzbw Airspace SYR VOR (For aircraft filed/cleared J59 [PSB-SYR]) RKA VOR (For aircraft filed/cleared J190 [CFB-RKA]) HNK VOR (For aircraft filed/cleared J217 [ETG-HNK] or J49 [PSB-HNK]) c. Initiate a handoff to Boston Center (or subordinate facility, as appropriate) for any aircraft requesting VFR flight following services into vzbw Airspace 2) Without prior coordination, Boston Center may: a. Turn aircraft 30 degrees left or right of track on contact b. Clear aircraft direct the following waypoints within vzbw Airspace SAX VOR (For aircraft filed/cleared J77 or J80 [BAF-SAX]) LOLLY intersection (For aircraft filed/cleared IGN# STAR) CRANK intersection (For aircraft filed/cleared SHAFF# STAR or HELON# STAR) c. Initiate a handoff to New York ARTCC (or subordinate facility, as appropriate) for any aircraft requesting VFR flight following services into v Airspace B. ARRIVALS: 1) New York ARTCC shall: a. Descend aircraft according to the following table: Arr To cross At an altitude of and handoff KBOS KBDL KPVD KSYR BAWLL (KRANN# STAR) (ORW# STAR) ARTCC Boundary (ALB.GDM# STAR) At/maintain FL230 At/below FL310 Passing JFK VOR 10 nm from boundary DPK VOR At/below FL200 Prior to crossing DPK VOR RKA/HNK (SWEDE# STAR) HTO (JORDN# STAR) At/below FL270 At/below 15,000 and 250 KIAS 20 nm west of SEY At/maintain 11,000 HNK/DNY/RKA/CFB At/below FL200 ITH VOR/J95/V35 At/below 11,000 10 nm from boundary 10 nm from boundary 10 nm from boundary KALB ARTCC Boundary At/below FL240 10 nm from boundary vzbw/v LOA 2 EFF: 01/05/2012

2) Boston ARTCC shall: a. Descend aircraft according to the following table: Arr To cross At an altitude of and handoff KEWR CRANK (or SAX VOR) 7,000 / 250 (6,000 / 250) IGN VOR KJFK KLGA CCC VOR LOLLY 12,000 / 250 (Jets) 10 nm East of CCC VOR to NY 11,000 / 250 (Props) Approach FL200 IGN VOR to NY Center (to APP if CTR off) LOVES 6,000 PWL VOR NOBBI 8,000 PWL VOR BASYE 9,000 VALRE IGN 12,000 / 250 IGN VOR VALRE 8,000 VALRE C. DEPARTURES 1) New York ARTCC/TRACON shall: a. Initiate handoff of aircraft bound for KBOS 10 nm prior to MERIT or over BDR VOR climbing to 17,000 or lower assigned cruise altitude. b. Initiate handoff of aircraft bound to BETTE/HAPIE climbing to 11,000 10 nm prior to HAPIE and 5 nm prior to BETTE c. Initiate handoff of aircraft departing v entering vzbw airspace at other points (e.g. from KPOU, KSWF, KOXC, etc.) direct the first waypoint or established on route and climbing to the vertical limits of v airspace d. Route aircraft bound for KBOS according to the following table: Departure Type Altitude Route EWR / ISP / JFK / LGA and Satellites PHL and Satellites SWF / POU and Satellites RNAV Jets Non-RNAV Jets Props RNAV Jets Non-RNAV Jets Props Jets Below FL190 All Max FL230 FL190-FL250 11,000-17,000 Max FL230 MERIT ORW.KRANN# MERIT ORW.ORW# MERIT ORW.WOONS# or BDR V229 HFD V3 WOONS DITCH J225 JFK.KRANN# DITCH J225 JFK.ORW# DITCH V312 DRIFT V308 ORW.WOONS# STUBY CTR GDM.GDM# or PWL CTR GDM.GDM# vzbw/v LOA 3 EFF: 01/05/2012

2) Boston ARTCC shall: a. Route aircraft bound for N90 according to the following table: Destination Type Route KEWR KJFK KLGA KPHL Jets Props Jets Props Jets Props Jets Props BDL.SHAFF# BDL IGN FLOSI V213 SAX HFD V3 CMK V188 SAX PARCH CCC ROBER ORW V16 CCC ROBER BAF IGN.HAARP# BDL VALRE V157 HAARP BAF PWL V405 CASSH V123 HAARP SEY J121 BRIGS.JIMGE# (RNAV) SEY J121 BRIGS.VCN# SEY J121/V268 BRIGS.VCN# Don Desfosse Air Traffic Manager, Virtual Boston ARTCC Nicola Felini Air Traffic Manager, Virtual New York ARTCC ATTACHMENTS: 1. New York Center Standard Sectorization Scheme 2. N90 Kennedy Sectorization 3. N90 LaGuardia Sectorization 4. N90 Newark Sectorization 5. Boston Center Standard Sectorization Scheme vzbw/v LOA 4 EFF: 01/05/2012

ATTACHMENT 1: NEW YORK CENTER STANDARD SECTORIZATION SCHEME 1. General A. When New York Center is combined, it will be combined as NY_KND_CTR on frequency 125.32. B. Occasionally, major VATSIM events will necessitate multiple Center sectors (splits). These are typically coordinated and published (internally as well as to adjacent centers) prior to the event. The number and configuration of sectors opened shall be determined by the event coordinator and/or Traffic Management Unit Coordinator (TMC), with approval of the New York Air Traffic Manager (ATM). C. Sector splits may also be used for training purposes 2. Number of Splits A. Controllers shall work their airspace utilizing the minimum number of splits necessary to ensure positive and effective control over the aircraft under their control. It is very rare to need splits, and extremely rare to need more than 2 splits. B. The New York ATM, DATM, TA, or TMU has the authority to initiate, approve, or deny sector splits to effectively manage traffic conditions affecting v and neighboring facilities 3. Geographical Splits A. The most common split is for v is a Hi/Lo split. If traffic warrants, additional Hi/Lo or geographic splits may be utilized as traffic/workload warrants. The most common v splits are shown in Figures 1-4. 4. Typical Frequencies A. When New York Center is combined, it will be combined as NY_KND_CTR on frequency 125.32 B. Standard split frequencies are shown in Figures 1-4 vzbw/v LOA 5 EFF: 01/05/2012

SFC-170 SFC-80 SFC-FL230 When one Center position is manned: NY_KND_CTR (B-56) on 125.32 controls all of New York Center Figure 1: New York Center Airspace Combined vzbw/v LOA 6 EFF: 01/05/2012

C D B A E With two center controllers online, a High/Low split is in effect: NY_ARD_CTR (B-55) on 134.60 A, B, C, and D sectors SFC-FL240 (outlined in blue) E sector SFC-FL230 (filled in blue) NY_KND_CTR (B-56) on 125.32 A, B, C, and D sectors >FL240 (filled red) Figure 2: New York Center Most Common Two Way Split (Hi/Lo) vzbw/v LOA 7 EFF: 01/05/2012

C D B A E With three centers online, a High Low/Low split is in effect: NY_ARD_CTR (B-55) on 134.60 B sector SFC-FL240 (outlined in blue) E sector SFC-FL230 (filled in blue) NY_PTO_CTR (D-92) on 124.62 A, C, and D sectors SFC-FL240 (outlined in green) NY_KND_CTR (B-56) on 125.32 A, B, C, and D sectors >FL240 (filled red) Figure 3: New York Center Most Common Three Way Split (Hi/Lo/Lo) vzbw/v LOA 8 EFF: 01/05/2012

C D B A E With four centers online, a High/High Low/Low split is in effect: NY_ARD_CTR (B-55) on 134.60 B sector SFC-FL240 (outlined in blue) E sector SFC-FL230 (filled in blue) NY_PTO_CTR (D-92) on 124.62 A, C, and D sectors SFC-FL240 (outlined in green) NY_KND_CTR (B-56) on 125.32 B sector >FL240 (filled red) NY_MIP_CTR (D-75) on 128.57 A, C, and D sectors >FL240 (filled light blue) Figure 4: New York Center Most Common Four Way Split (Hi/Hi/Lo/Lo) vzbw/v LOA 9 EFF: 01/05/2012

ATTACHMENT 2: NEW YORK TRACON KENNEDY SECTORIZATION LENDY Sector To NY_CAM_APP on 127.4 ROBER Sector To NY_RBR_APP on 125.7 11 13 TEB VOR 1 10 9 9a 7 8 12 2 LGA 3 6 14 4 5c 5b 30 5a 180/ABV ZBW150/ABV 17a 17 19 ZBW 130/ABV 140/ABV 29 20 28 18 21 24 22 23 CCC VOR 25 26 16 ZBW070/ABV ISP 060/BLO 15 CAMRN Sector To NY_CAM_APP on 127.4 With one Approach Controller online: Approach services are combined under NY_CAM_APP on 127.4 With multiple Approach Controllers online, sectorization can be as above: CAMRN/LENDY Sector - NY_CAM_APP on 127.4 ROBER Sector NY_RBR_APP on 125.7 vzbw/v LOA 10 EFF: 01/05/2012

ATTACHMENT 3: NEW YORK TRACON LAGUARDIA SECTORIZATION NOBBI Sector (Below ~50) To NY_NBI_APP on 126.4 40 44 45 42 46 29 39 CMK 2 3 1 4 5 6 20 11 30 41 32 31 HPN 35 36 33 34 37 21 22 LGA 13 23 24 12 19 26 18 14 25 15 17 16 38 27 47 28 7 8 9 10 HARRP Sector (~90 to ~30) To NY_HRP_APP on 120.8 NOBBI Sector (Below ~40) To NY_NBI_APP on 126.4 7a With one Approach Controller online: Approach services are combined under NY_HRP_APP on 128.80 With multiple Approach Controllers online, sectorization can be as above: HAARP Sector - NY_HRP_APP on 120.8 NOBBI Sector NY_NBI_APP on 126.4 vzbw/v LOA 11 EFF: 01/05/2012

ATTACHMENT 4: NEW YORK TRACON NEWARK SECTORIZATION North Arrival Handoff to 60 To NY_NOA_APP on 120.15 ZEEBO (50 and below) To NY_ZBO_APP on 123.77 With one Approach Controller online: Approach services are combined under NY_ARD_APP on 128.55 With multiple Approach Controllers online, sectorization can be as above: North Arrival Sector - NY_NOA_APP on 120.15 ZEEBO Sector NY_ZBO_APP on 123.77 vzbw/v LOA 12 EFF: 01/05/2012

ATTACHMENT 5: BOSTON CENTER STANDARD SECTORIZATION SCHEME 1. General A. When Boston Center is combined, it will normally be combined as BOS_CTR on frequency 134.700. The Event Coordinator / Controller in Charge (CiC) of an event, the Boston Air Traffic Manager, Deputy Air Traffic Manager or Training Administrator may approve specific requests to operate on another valid vzbw Center frequency; such approvals are one-time approvals to be limited to one session. B. Occasionally, major VATSIM events will necessitate multiple Center sectors (splits). These are typically coordinated and published (internally as well as to adjacent centers) prior to the event. The number and configuration of sectors opened shall be determined by the event coordinator and/or Boston Controller in Charge (CiC), with approval of the Boston Air Traffic Manager (ATM). C. Sector splits may also be used for training purposes 2. Number of Splits A. Controllers shall work their airspace utilizing the minimum number of splits necessary to ensure positive and effective control over the aircraft under their control. It is very rare to need splits, and extremely rare to need more than 2 splits. B. The Boston Controller in Charge shall have authority to initiate, approve, or deny sector splits to effectively manage traffic conditions affecting vzbw and neighboring facilities 3. Geographical Splits A. The most common geographical split is North/South (N/S). Another, less common, split is East/West (E/W). If traffic warrants, ordinal (NE/SE/SW/NW) splits may also be used. Combinations, such as a three-way split (e.g. NW/SW/E) may also be utilized as traffic/workload warrants. If an operational advantage will be gained, the airspace may also be split High/Low, using altitudes defined in this section. The most common vzbw splits are shown in Figures 6-8. 4. Altitudes A. Low: Surface to FL239 B. High: FL240 to FL600 5. Typical Frequencies A. When Boston Center is combined, it will normally be combined as BOS_CTR on frequency 134.700 B. Standard split frequencies are shown in Table 1 vzbw/v LOA 13 EFF: 01/05/2012

CZYZ TORONTO CTR CYUL MONTREAL CTR ZOB CLEVELAND CTR BOS_CTR 134.700 CYQM MONCTON CTR NEW YORK CTR ZDC FL240+ NEW YORK OCEANIC Figure 5: Boston Center Airspace Combined vzbw/v LOA 14 EFF: 01/05/2012

CZYZ TORONTO CTR CYUL MONTREAL CTR ZOB CLEVELAND CTR BOS_N_CTR 128.320 CYQM MONCTON CTR NEW YORK CTR BOS_S_CTR 126.220 ZDC FL240+ NEW YORK OCEANIC Figure 6: Boston Center Two-Way (North/South) Split vzbw/v LOA 15 EFF: 01/05/2012

CZYZ TORONTO CTR CYUL MONTREAL CTR ZOB CLEVELAND CTR BOS_NW_CTR 128.320 BOS_E_CTR 128.050 CYQM MONCTON CTR NEW YORK CTR BOS_SW_CTR 126.220 ZDC FL240+ NEW YORK OCEANIC Figure 7: Boston Center Three Way (NW/SW/E) split vzbw/v LOA 16 EFF: 01/05/2012

CZYZ TORONTO CTR CYUL MONTREAL CTR ZOB CLEVELAND CTR BOS_NW_CTR 128.320 BOS_NE_CTR 128.050 CYQM MONCTON CTR NEW YORK CTR BOS_SW_CTR 126.220 BOS_SE_CTR 128.750 ZDC FL240+ NEW YORK OCEANIC Figure 8: Boston Center Four Way Ordinal Split vzbw/v LOA 17 EFF: 01/05/2012

Position Callsign Description Frequency Vox Channel BOS_CTR Fully Combined 134.700 ZBW_134.700 BOS_N_CTR N/S Two-Way Combined 128.320 ZBW_128.320 BOS_S_CTR 126.220 ZBW_126.220 BOS_E_CTR E/W Two-Way Combined 128.050 ZBW_128.050 BOS_W_CTR 128.320 ZBW_128.320 BOS_NW_CTR Three-Way 128.320 ZBW_128.320 BOS_SW_CTR 126.220 ZBW_126.220 BOS_E_CTR 128.050 ZBW_128.050 BOS_HN_CTR N/S Two-Way Hi/Low 128.320 ZBW_128.320 BOS_LN_CTR 134.700 ZBW_134.700 BOS_HS_CTR 126.220 ZBW_126.220 BOS_LS_CTR 128.750 ZBW_128.750 BOS_HE_CTR E/W Two-Way Hi/Low 128.050 ZBW_128.050 BOS_LE_CTR 128.750 ZBW_128.750 BOS_HW_CTR 128.320 ZBW_128.320 BOS_LW_CTR 134.700 ZBW_134.700 BOS_NE_CTR Four-Way Ordinal 128.050 ZBW_128.050 BOS_SE_CTR 128.750 ZBW_128.750 BOS_SW_CTR 126.220 ZBW_126.220 BOS_NW_CTR 128.320 ZBW_128.320 Table 1: Boston Center Standard Frequency Usage vzbw/v LOA 18 EFF: 01/05/2012