Version O January 21, 2019

Similar documents
Albany ATCT Standard Operating Procedures

Burlington ATCT Standard Operating Procedures

Providence ATCT Standard Operating Procedures

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

Cape Area Airports Standard Operating Procedures

Denver ARTCC Colorado Springs ATCT & TRACON STANDARD OPERATING PROCEDURES

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

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

ERIE ATCT STANDARD OPERATING PROCEDURES

- Updated formatting - Re-drawn airspace delegation diagram

RALEIGH-DURHAM ATCT/TRACON STANDARD OPERATING PROCEDURES

ZTL ARTCC. Augusta Regional

Greenville Spartanburg International

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

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

Piedmont Triad International Airport

Cleveland ARTCC and Boston Virtual ARTCC Letter of Agreement

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

Charlotte - Douglas International Airport Traffic Control Tower

VATUSA C90 TRACON AND O HARE ATCT LETTER OF AGREEMENT

INTERNATIONAL VIRTUAL AVIATION ORGANISATION CANADIAN AIR TRAFFIC CONTROL PHRASEOLOGY ATC OPERATIONS DECEMBER 2016 BY: MATHIEU LAFLAMME

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

EFFECTIVE NOTAM KGON 10/06 SPECIAL FLIGHT PROCEDURES GROTON, CT

VATUSA Approval 3/21/18

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

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

PITTSBURGH ATCT STANDARD OPERATING PROCEDURES

October 4, 5, 6, 2007 Aircraft Arrival and Departure Procedures

Standard Operating Procedures

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

AIR TRAFFIC ROUTE CONTROL CENTER

Virtual Jacksonville Air Route Traffic Control Center Daytona Beach ATCT Standard Operating Procedures

Letter of Agreement by and between Jacksonville ARTCC and Miami ARTCC

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

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

vzny ARTCC & vzbw ARTCC

D01 TERMINAL RADAR APPROACH CONTROL

Boston Consolidated TRACON (A90) Standard Operating Procedures

UNIVERSITY OF ALABAMA FOOTBALL

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

9/23/2010 RDU B. Raleigh-Durham Air Traffic Control Tower. Standard Operating Procedures

IVAO Switzerland Division

Charlotte - Douglas International

EFFECTIVE KGON 10/06 SPECIAL FLIGHT PROCEDURES PILOT INFORMATION PACKET GROTON, CT

Anchorage ARTCC Phraseology Guide. Clearance Delivery Operations

Southern California TRACON and Lindbergh Tower LETTER OF AGREEMENT SUBJECT: INTER-FACILITY COORDINATION AND CONTROL PROCEDURES

SANTA FE MUNICIPAL AIRPORT (SAF) SANTA FE, NM

SECTION 4 - APPROACH CONTROL PROCEDURES

Jacksonville ARTCC. F11 TRACON Standard Operating Procedures

ATLANTA ARTC CENTER AND CHARLOTTE TOWER LETTER OF AGREEMENT

H O M E C O M I N G. NOTAM Aircraft Owners and Pilots Association (AOPA) Fly-In Frederick Municipal Airport (FDK) Frederick, MD

KTPF PETER O. KNIGHT AIRPORT TAMPA, FL 10/27 NOTAM SPECIAL FLIGHT PROCEDURES EFFECTIVE

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

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

VFR PHRASEOLOGY. The word IMMEDIATELY should only be used when immediate action is required for safety reasons.

EFFECTIVE NOTAM KOUN SPECIAL FLIGHT PROCEDURES 09/08 NORMAN, OK

ORDER MSY V. New Orleans. Standard Local Operating Procedures. Rev 3 December 7, 2011

Southern California Terminal Radar Approach Control and Ontario Airport Traffic Control Tower

FLIGHT STRIP MANAGEMENT - APPROACH LEVEL

Jax Navy Flying Club Course Rules

Northern Regional Training Scheme. EGBB Birmingham Airport Pilot s Guide. REVISION 1 (Monday, 30 January 2012)

VFR Arrival and Departure Procedures Rocky Mountain Airshow 2012 Rocky Mountain Metropolitan Airport (KBJC)

JACK EDWARDS NATIONAL AIRPORT (JKA) GULF SHORES, AL

VATUSA CHICAGO ARTCC AND C90 TRACON LETTER OF AGREEMENT

CHICAGO MIDWAY INTERNATIONAL AIRPORT (KMDW) STANDARD OPERATING PROCEDURES

VATSIM MINNEAPOLIS ARTCC MINNEAPOLIS TRACON LETTER OF AGREEMENT

Northern Regional Training Scheme. EGNT Newcastle Aerodrome Pilot s Guide. REVISION 2 (Wednesday, 03 August 2011 at 15:51)

PHRASEOLOGY COMMON MISTAKES

2014 NOTAM Special Flight Procedures. Plymouth, MA Effective 12:00 Noon (Local) July 11, 2014 Until 6:00PM (Local) July 12, 2014

SID/STAR phraseology FAQ Canadian implementation April 27, 2017

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

2014 NOTAM Special Flight Procedures. Indianapolis, IN Effective 0600 EDST (Local) May 30, 2014 Until 2000 EDST (Local) May 31, 2014

ATMM. Air Traffic Management Manual. Air Traffic Management Manual VACC AUSTRIA LOVV ATMM Air Traffic Management Manual

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

JACKSONVILLE CENTER AND SAVANNAH TRACON. LETTER OF AGREEMENT EFFECTIVE: December 22, 2006

Standard Operating Procedures (SOPs) for BAGHDAD (ORBI)

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

RWY 24. Designator Route Remarks. All traffic shall initially climb to 4000FT QNH with climb gradient 3.3% MNM, unless instructed otherwise by ATC.

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

1.2 An Approach Control Unit Shall Provide the following services: c) Alerting Service and assistance to organizations involved in SAR Actions;

NATIONAL BUSINESS AVIATION ASSOCIATION (NBAA) CONVENTION

AOPA FLY-IN PACKET EFFECTIVE SPECIAL FLIGHT PROCEDURES SEPT BATTLE CREEK, MI W K KELLOGG AIRPORT (KBTL) PILOT INFORMATION

ATC Training Syllabus Philippines vacc Version 1.1 September 25, 2016

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

Chapter 6. Nonradar. Section 1. General DISTANCE

AOPA FLY-IN PACKET EFFECTIVE PILOT INFORMATION SPECIAL FLIGHT PROCEDURES SEPT 30-OCT 1 PRESCOTT, AZ ERNEST A LOVE FIELD AIRPORT (PRC)

THE TOWER CONTROL POSITION (TWR)

NOTAM. Aircraft Owners and Pilots Association (AOPA) Fly-In Colorado Springs Airport (COS) Colorado Springs, CO SPECIAL FLIGHT PROCEDURES

CHICAGOLAND SPEEDWAY NASCAR RACES

USE OF RADAR IN THE APPROACH CONTROL SERVICE

CLEARANCE INSTRUCTION READ BACK

MILWAUKEE MKE TRACON GEN. MITCHELL INTL AIRPORT (KMKE) MKE TRACON SATELLITE AIRPORTS STANDARD OPERATING PROCEDURES

Standard Operating Procedures

Standard Operational Procedures

GENERAL INFORMATION The aerodrome consists of three runways (04L-22R, 04R-22L, 12-30) and four aprons.

VATSIM JORDAN vacc QUICK REFERENCE HANDBOOK QUICK REFERENCE - STANDARD FORMATS FOR COMMUNICATION

WASHINGTON DULLES ATCT STANDARD OPERATING PROCEDURES

FSBREAK $100 Hamburger Fly in to KSAN

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

Jax Navy Flying Club Course Rules

Transcription:

Bradley ATCT and Y90 TRACON 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 O January 21, 2019 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 O January 21, 2019 Adds Opposite Direction Operations procedures Page 11 Version N September 8, 2018 Removes an incorrect statement about departure frequencies/handoffs from Chapter 4 Page 7 Version M February 11, 2018 Modifications to support A90/K90 merger Multiple 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 Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 1

Chapter 1: Overview 1.1 Quick Reference Sheets a. BDL_DEL (121.75) Initial Altitude for IFR Aircraft: 4,000 Altitude Restriction for VFR Departures: 2,500 Departure Procedures: BDL# SID, radar vectors to (FIX), CSTL# SID (HI), GEDIC/SHERL Transition CPDLC Available (use.pdcm to include top altitude in the CPDLC message) b. BDL_GND (121.90) Taxi Routes: Refer to Appendix 4. Use caution when Runway 1/19 is active when taxiing aircraft on taxiway Charlie to prevent runway incursions. Parking: There are two FBOs located on different sides of the airport. Coordinate with BDL_TWR to obtain parking information from arriving aircraft to avoid unnecessary runway crossings. c. BDL_TWR (120.30) Airspace: Flow-specific; generally, 4,000 within departure corridor, 2,500 along the arrivals. See Page 7 for airspace breakdowns. Runways: At least two runways shall be open at all times when possible. Calm Wind Configuration: Land/Depart Runways 6 and 33 (wind less than 5 kts). ATIS: Digital. Real-world ATIS: 860-386-3570. Departure Headings: Assign the departure headings shown on Page 9. Missed Approach: Runway Heading, 3,000. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 2

d. BDL_APP (123.95/127.22) Airspace: Video map lateral boundaries to 10,000 MSL. Route / Procedure Altitude Handoff DPK STAR 11,000 MAD STELA STAR 11,000 STELA GDM V229 WITNY 4,000-10,000' GDM HFD BDL 5,000'-9,000' Boundary ILS Approach Frequency/Course FAF / Altitude ILS 6 111.1 058 HUNEE / 1,800 ILS 24 111.1 238 MOTEL / 2,100 ILS 33 108.55-328 HOMEY / 1,800' 1.2 General a. This document outlines the air traffic control procedures and responsibilities for controllers working positions at BDL ATCT and/or Y90 TRACON. b. The following callsigns and frequencies shall be used when working positions at BDL ATCT or Y90 TRACON: Identifier Position Frequency VOX Channel BDL_DEL Clearance Delivery 121.75 BDL_121.750 BDL_GND Ground Control 121.90 BDL_121.900 BDL_TWR Local Control 120.30 BDL_120.300 BDL_B_APP Bristol Radar 123.95 Y90_123.950 BDL_F_APP Final Vector 127.220 Y90_127.220 BDL_H_APP Hartford Radar 127.800 Y90_127.800 BDL_W_APP West Departure Radar 125.35 Y90_125.350 BDL_E_APP Worcester Radar 119.000 Y90_119.000 BDL_ATIS ATIS 118.150 N/A c. Except when split, Y90 shall use frequency 123.95. BVA Bradley ATCT and Y90 TRACON 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. (a) Departures landing in Y90 shall be issued 3,000' as a final altitude. 2. Assign all VFR departures at or below 2,500' or lower requested altitude. b. VFR Aircraft: 1. VFR aircraft shall be assigned an altitude, departure frequency, and squawk. Maintain VFR at or below 2,500' until advised. Departure frequency 125.35, squawk 5421. 2. All Special VFR (SVFR) departures shall be restricted at or below 2,000. c. IFR Aircraft: 1. Departure Frequency is based on the aircraft s initial fix. Aircraft filed over MAD, HFD (including the CSTL SID), ORW, GON, PUT and PVD will go to Bristol Radar on 123.950, while aircraft filed over CTR, EEN, MOBBS, PWL, VAPER, VEERS should be assigned West Departure Radar (125.350). 2. Clearances may be issued by CPDLC. 3. The BDL# is the primary SID. This SID shall be inserted into the flight plan. Cleared to (destination) via the BDL# Departure, radar vectors (first fix), then as filed 4. Aircraft cleared via the CSTL# SID shall be assigned a transition (GEDIC or SHERL), and both the SID and transition shall be included in the flight plan. Cleared to (destination) via the CSTL# Departure, SHERL Transition, then as filed 5. Aircraft unable a SID shall be cleared via the corresponding BDL# departure procedure heading. The BDL# shall be included in the flight plan. Cleared to (destination) via fly heading 075, radar vectors PUT, then BVA Bradley ATCT and Y90 TRACON 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. For the purposes of runway crossings, all runways, with the exception of Runway 1/19, shall be considered active at all times unless specifically advised by Local Control. c. 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. Taxiway J between S and R is restricted to wingspans less than 170. 5. Except for taxi, Runway 1-19 is available for aircraft with wingspans less than 79 only. For fixed-wing aircraft, Runway 1 is restricted to departures only. For fixed-wing aircraft, Runway 19 is restricted to arrivals only. d. Intersection Departures: e. 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 Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 5

LAHSO Distance: 6,000 FedEx Bombardier Signature FBO UPS LAHSO Distance: 5,850 TacAIR FBO LAHSO Distance: 4,550 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 6

Chapter 4: Local Control a. Local Control is authorized to provide Class C services in the delegated airspace shown below: b. Runway selection: 1. When the wind is less than five knots, the calm wind configuration shall be to land and depart Runways 6 and 33. At all other times, use the two runways most aligned with the wind. 2. All advertised runways may be used for departures and arrivals without further coordination with radar. 3. Runway 1 may not be used for arrivals; Runway 19 may not be used for departures. c. Runway changes: BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 7

1. Coordinate with all affected BDL/Y90 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 Y90 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 Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 8

2. Departure heading: (a) LC shall assign the following headings to departing aircraft: Flow Departure Runway Direction 1 Heading All Runway 6 Westbound 075 All Runway 6 Eastbound 095 24/33 Runway 24 Westbound, including ORH and DREEM 280 or 300 24/33 Runway 24 Eastbound 240 or 220 24/33 Runway 33 Eastbound 220 24/33 Runway 33 Westbound 310, 330, 350 24/15 Runway 24 Westbound 280 24/15 Runway 24 Eastbound, including ORH and DREEM 240 or 220 24/15 Runway 15 Westbound 280 24/15 Runway 15 Eastbound 150, 170 6/15 Runway 15 Eastbound 130, 150 6/15 Runway 15 Westbound, including ORH and DREEM 030 6/33 Runway 33 Westbound 310, 330, 350 6/33 Runway 33 Eastbound 100 (b) Departures from Runway 24 cleared via VEERS, MOBBS, CTR, VAPER, EEN, BAF and CEF shall be assigned heading 280. Heading 300 may be used to establish initial departure separation. (c) Departures from Runway 24 cleared via ORH and DREEM on the 24/33 flow shall be assigned heading 280. Heading 300 may be used to establish initial departure separation. (d) For all IFR missed approaches, assign runway heading and 3,000. When conflicting traffic is involved, issue control instructions to establish and maintain separation. Any heading toward the departure side of the airport 1 Eastbound and westbound departures are determined by the location of the first fix (or, if direct an airport, the destination airport) relative to the Runway 6/24 centerline. Westbound means Northwest of the centerline. Eastbound means southeast of the centerline. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 9

e. Arrival procedures: may be used as appropriate, and coordinated with the appropriate overlying radar facility. (e) VFR traffic that will leave the traffic pattern shall be assigned runway heading. 1. All aircraft executing an unintentional missed approach shall be assigned to fly the runway heading and to climb and maintain 3,000 feet. (a) Coordinate with the appropriate radar sector and hand off the aircraft as soon as possible. (b) Automatic releases are canceled until otherwise advised by the radar controller. 2. Practice Approaches f. Traffic patterns: (a) Aircraft executing practice approaches shall be handed off to Radar no later than the missed approach point. (b) Coordinate with the appropriate Radar sector to determine missed approach instructions to be issued to an aircraft conducting practice approaches. (c) If no instructions are received before the aircraft reaches the missed approach point, handle the aircraft as an unintentional missed approach and coordinate with radar. 1. Generally, aircraft remaining in the pattern should not be assigned a discrete squawk code. This prevents Radar from mistakenly tracking the target, and prevents Conflict Alerts from going off. g. VFR operations: 1. VFR aircraft transiting the KBDL Class C airspace at or below 3,000 may be assigned the Runway 1 transition or Runway 19 transition (appropriate direction of flight). The transition is used for north-south aircraft who then transit the airspace along the centerline of Runway 1-19. When issuing this transition to aircraft above 2,000, coordinate with the overlying radar controller to ensure separation is maintained with IFR aircraft. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 10

h. Opposite Direction Operations (ODO): 1. The following cutoff points have been established as measured from the arriving aircraft s threshold, when conducting ODO: (a) An arrival aircraft and a departure: 10 miles (b) An arrival and an arrival: 10 miles when the first arrival crosses the runway threshold. (c) TWR is responsible for ensuring compliance with the applicable cutoff points between a departure and an arrival. (d) APP is responsible for ensuring compliance with the applicable cutoff points between an arrival and an arrival. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 11

Chapter 5: Radar Sectors a. Frequency: 1. When all positions are consolidated: (a) Y90 will use frequency 123.95, with a voice channel of Y90_123.950. 2. The following splits can be staffed: (a) Bristol Radar (BDL_B_APP), with a voice channel of Y90_123.950. (b) Final Vector (BDL_F_APP), with a voice channel of Y90_127.220. (c) Hartford Radar (BDL_H_APP), with a voice channel of Y90_127.800. (d) West Radar (BDL_W_APP), with a voice channel of Y90_125.350. (e) Worcester Radar (BDL_E_APP), with a voice channel of Y90_119.000. (f) When a split is in effect, the airspace split shall be coordinated between controllers. The dashed lines on the radar video map depict various airspace splits, including a final box. b. Departures: 1. All IFR departures from BDL will be assigned a heading within the departure corridor and climbing to 4,000. 2. Do not alter the initial assigned heading issued by the Tower until the aircraft has left 3,000 or has passed 3nm from the departure end of the runway, unless the departure is destined to turn away from another runway or there is only one active runway. 3. When appropriate, climb departing aircraft to 10,000 or lower filed altitude. 4. Initiate an automated handoff to the appropriate ZBW sector upon the departure being cleared on course and ensured free of traffic conflicts. 5. Issue transfer of radio communications to the appropriate ZBW sector upon passing 6,000-7,000, or within 10NM of the airspace boundary, as appropriate. 6. 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 Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 12

Chapter 6: Interfacility Coordination a. Airspace delegation overview: BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 13

b. BOS and Y90: 1. Control on contact: (a) For turns 30 degrees either side of track, except if the aircraft will land in the receiving controller s airspace, in which case turns up to 90 degrees. 2. GLYDE V270 CTR and GLYDE V292 BAF aircraft can be cleared direct CTR or BAF provided the traffic will enter Y90 over or south of DREEM. 3. Y90 must coordinate with BOS for approaches to Hopedale (1B6). 4. BOS has control for descent to 4,000 for Bedford Sector arrival traffic after the traffic has passed DREEM. 5. Delegated Airspace: BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 14

c. 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 Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 15

d. N90 TRACON and Y90 TRACON: 1. Control on contact: (a) For turns up to 30 degrees. (b) N90 for descent for BDR/HVN and OXC arrivals within 5nm of boundary. 2. Y90 to N90: (a) Y90 may clear: (1) V1 traffic direct MAD. (2) Traffic direct CMK. (3) Turbojet aircraft landing EWR (and surrounding airports) via HFD V3 CMK V623 SAX when the route is requested by the pilot. (b) Issue the following preferred routes: Destination Route Altitudes SWF, POU, MSV, MGJ HFD PWL or V405 PWL 4,000 EWR & SATS V3 V229 (single eng.) 6,000 LGA, HPN, DXR V1 4,000 / 6,000 / 8,000 ISP, JFK, and similar V1 4,000 HVN, BDR Direct 4,000 3. N90 to Y90: (a) Handoff traffic landing HFD at 5,000 or 7,000. These aircraft may be issued direct HFD. (b) Issue the following preferred routes: Destination Route Altitudes BAF, CEF, ORH V405 BAF 5,000 BDL, HFD, MMK PWL R-111 5,000 BDL, BAF, CEF CMK V419 5,000 / 7,000 / 9,000 HFD, MMK, ORH CMK V3 5,000 / 7,000 / 9,000 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 16

4. Airspace delegation: e. PVD ATCT and Y90 TRACON: 1. Control on contact: (a) For descent (not below 5,000 ) and turns up to 30 degrees. 2. Clear arrivals via vectors or direct destination, with the following exceptions: (a) Y90 to PVD: (1) GON area arrivals from ZBW through Y90 to cross the Y90/PVD boundary at or below 9,000, descending to 7,000. (2) PVD airport arrivals via HFD limited to at or below 7,000. (b) PVD to Y90: (1) Traffic landing ORH should be delivered via PUT at even altitudes. 3. Overflight aircraft may be cleared direct to the first fix in adjacent airspace depicted in the flight plan except traffic routed via V1..V14 shall enter PVD on V14. 4. Traffic overlying PVD via HFD shall be limited to 7,000 and 9,000. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 17

f. ZBW ARTCC and Y90 TRACON: 1. Control on contact: (a) Y90 for turns not to exceed 30 degrees within 5nm of the boundary. (b) ZBW at or above 5,000 for turns not to exceed 30 degrees within 5nm of the boundary. 2. ZBW to Y90: (a) Traffic routed via the STELA STAR shall cross STELA at 11,000. (b) Traffic routed via the DPK STAR shall cross MAD at 11,000. (c) BDL, BAF, and CEF arrivals via IGN V58 JUDDS shall be cleared to enter BDL TRACON at 7,000 or 9,000. (d) N90 departures may be cleared via PWL PWL111 BRISS to enter BDL TRACON at 7,000 or 9,000. (e) BDL arrivals from the northeast (EEN, GDM, CLOWW) can enter BDL TRACON between 4,000 10,000. (f) Y90 arrivals from the east or southeast shall cross 35 NM west of BDL at 11,000. 3. Y90 to ZBW: (a) Y90 shall clear all departures on course and issue a climb to 10,000' or lower cruise altitude before transferring communications. (b) Y90 departures to VEERS shall be issued direct VEERS from on or north of a BDL-VEERS line. (c) RNAV-equipped aircraft flight planned over THUMB may be issued direct THUMB provided the aircraft is east of a BDL-HFD line. BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 18

Chapter 7: Intrafacility Coordination a. Bristol Radar (BR) 1. Control BDL departures filed over MAD, HFD (including the CSTL SID), ORW, GON, PUT and PVD, as well as DREEM traffic on a runway 15/24 flow only. 2. Handoff BDL arrivals to FV at or descending to 5,000. 3. Be permitted control on contact for descent to 8,000 for enroute aircraft. b. West Departure (WD) 1. Control BDL departures filed over CTR, EEN, MOBBS, PWL, VAPER, VEERS, as well as DREEM traffic on all flows except a runway 15/24 flow. 2. Handoff BDL arrivals to FV at or descending to 5,000. 3. Vector BDL VFR arrivals to enter FV outside to 10nm range mark. 4. Handoff departures from BAF/CEF/7B2 landing BDL to FV at or below 5,000. 5. When BDL is on any runway 33 flow, verbally coordinate a point out as necessary with BDL LC for instrument approaches to runway 2 at BAF and runway 5 at CEF. c. Hartford Radar (HR) 1. Control HFD, MMK, IJD. d. Worcester Radar (OR) 1. When on a runway 6 flow, BDL arrivals operating below 5,000 must be vectored to enter Hartford Radar airspace, at least 10nm south of BDL. e. Final Vector (FV) 1. In a runway 15/24 flow, restrict BDL IFR arrivals from the southwest or while on left downwind to AOA 5,000 until northeast of the runway 15 centerline f. When on any runway 24 flow, do not descend below 4,000 until southeast of CEF runway 5/23 centerline BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 19

g..airspace Delegation 1. Runway 6-15 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 20

2. Runway 6-33 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 21

3. Runway 15-24 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 22

4. Runway 24-33 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 23

Chapter 8: Appendices 1.1 Intersection Departure Distances a. Taxiway Intersections Rwy Length Int Distance Int Distance Int Distance Int Distance 1 4,268 F 2,850 6 9,507 V 7,300 S 6,400 K 5,300 H 2,450 15 6,487 J 5,400 C 4,250 P 2,550 19 Not available for departures 24 9,510 H 7,050 K 4,150 S 3,050 V 2,200 33 6,846 E 5,450 P 4,250 C 2,500 J 1,400 b. Runway Intersections Rwy Length Int Distance Int Distance 6 9,507 15/33 6,150 1/19 3,000 15 6,487 6/24 4,800 24 9,510 1/19 6,500 15/33 3,300 33 6,846 6/24 2,000 BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 24

1.2 Preferred Taxi Routes BVA Bradley ATCT and Y90 TRACON Standard Operating Procedures Page 25