Providence 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. For more information about Boston Virtual ARTCC, visit www.bvartcc.com. Providence ATCT Standard Operating Procedures Version J July 18, 2018 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 July 18, 2018 Clarifies the combined frequency for PVD_APP is 123.67 Multiple Version I February 11, 2018 Modifications to support A90/K90 Merger Multiple Version H December 13, 2017 Adds section on Intrafacility Coordination Modifies sectors and frequencies Page 15 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 Providence ATCT Standard Operating Procedures Page 1

Chapter 1: Overview 1.1 Quick Reference Sheets a. PVD_DEL (126.65) Initial Altitude for IFR Aircraft: 4,000 (jet) or 2,000 (prop) Altitude Restriction for VFR Aircraft: 2,000 Departure Procedures: Radar vectors to (FIX) b. PVD_GND (121.90) Preferred Taxi Routes: See Ground Control chapter. c. PVD_TWR (120.70) Airspace: 3nm from KPVD from surface to 2,000 MSL. Calm Wind Configuration: Land/Depart Runway 5 or 23 in calm wind configuration (crossing runway only in strong winds). Runway 5 when KBOS landing north. ATIS: Digital. Real-world ATIS: 401-737-3215. Departure Headings: Runway Turbojet Non-Turbojet North: South: Closest Hdg to On Course: Missed Approach 5 360 080 280-100 Rwy Hdg, 2,100 16 220 180 140-260 Rwy Hdg, 2,000 23 280 160 140-300 Rwy Hdg, 2,000 34 330 330 280-100 Rwy Hdg, 2,100 d. PVD_APP (123.67/125.75/119.45/128.70/133.85/127.90) Airspace: Video map lateral boundaries to 10,000 MSL, except the A90 (8,000, or 6,000 when Runway 4 is in use at KBOS) and K90 (surface to 3,000) shelves. Route/Procedure Altitude Handoff JORDN 11,000 Boundary WIPOR 11,000 Boundary ILS Approach Frequency/Course FAF/Altitude ILS 5 109.30 047 CUTSI / 2,000 ILS 23 109.30 227 CUSKA / 1,900 ILS 34 111.50 337 BEVIN / 1,900' BVA Providence ATCT Standard Operating Procedures Page 2

1.2 General a. This document outlines the air traffic control procedures and responsibilities for controllers working positions at PVD ATCT. b. The following callsigns and frequencies shall be used when working positions at PVD ATCT: Identifier Position Frequency VOX Channel PVD_DEL Clearance Delivery 126.65 PVD_126.650 PVD_GND Ground Control 121.90 PVD_121.900 PVD_TWR Local Control 120.70 PVD_120.700 PVD_APP Consolidated 123.67 PVD_123.670 PVD_DEP Departure Radar 123.67 PVD_123.670 PVD_F_APP Arrival Radar 127.90 PVD_127.900 PVD_N_APP Rhody 133.85 PVD_133.850 PVD_S_APP JUMPR 125.75 PVD_125.750 PVD_SW_APP Groton 119.45 PVD_119.450 PVD_B_APP New Bedford 128.70 PVD_128.700 KPVD_ATIS ATIS 124.20 N/A c. Except when split, PVD APP shall use frequency 123.67. BVA Providence ATCT Standard Operating Procedures Page 3

Chapter 2: Clearance Delivery a. Altitude Assignments: 1. Assign jet IFR departures an initial altitude of 4,000. 2. Assign non-jet IFR departures an initial altitude of 2,000 3. All departures shall expect requested altitude ten (10) minutes after departure. 4. There are no IFR SIDs available. High altitude departure gates are PUT and PVD180 to JUMPR. Aircraft not flying preferred routes and with filed altitudes above 10,000 shall be cleared via a high altitude departure gate unless otherwise coordinated. 5. When split, all aircraft departing PVD shall be instructed to contact Departure 123.67. 6. Departures to KBOS: (a) Jet departures: cleared via WOONS at 5,000 or 7,000. (b) Non-jet departures: cleared via WOONS# arrival at 5,000 or 7,000. 7. Assign all VFR departures at or below 2,000' or lower requested altitude. 8. All Special VFR departures must be instructed to maintain SVFR at or below 1,500. b. VFR Aircraft: 1. VFR aircraft shall be assigned the appropriate altitude, departure frequency, and discrete squawk code. Maintain VFR at or below 2,000' until advised. Departure frequency 128.70, squawk 5421. BVA Providence 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). Ground Control does not have jurisdiction of movement while aircraft are in the northeast, northwest, or terminal ramps. Northstar Aviation FBO and Cargo BVA Providence ATCT Standard Operating Procedures Page 5

b. The following preferred taxi routes shall be used when practical: BVA Providence ATCT Standard Operating Procedures Page 6

Chapter 4: Local Control a. PVD_TWR is authorized to provide Class C services within the area extending 3nm from KPVD, upwards from the surface to 2,000 feet. b. Runway selection: 1. Runway 5 or Runway 23 should be used in calm wind conditions. This runway is strongly preferred for noise abatement. Use the crossing runway only when conditions warrant its use, or when requested by an aircraft for operational reasons. 2. Base the runway selection on the KBOS flow. Runway 5 is strongly preferred if Boston is landing northeast. 3. Runway 5 shall be used when the weather is below CAT I minimums. c. Departures: 1. IFR Departure heading: (a) LC shall assign fixed-wing turbojet departures one of the two headings listed below for the corresponding departure runway: Runway North Dep. Heading South Dep. Heading 5 360 080 16 220 180 23 280 160 34 330 330 (b) If the headings above are used for turbojet aircraft, the assignment does not need to be coordinated. BVA Providence ATCT Standard Operating Procedures Page 7

(c) Non-jet departures shall be assigned a coordinated heading closest to on course based on the table below in the takeoff clearance. The heading may be included in the aircraft s scratchpad with blanket coordination with PVD_APP or the relevant overlying facility. Runway Non-Jet Departure Corridor 5 Heading 280 through 100 inclusive 16 Heading 140 through 260 inclusive 23 Heading 140 through 300 inclusive 34 Heading 280 through 100 inclusive 2. Non-jet VFR departures shall be assigned runway heading. Jet VFR departures shall be assigned a heading coordinated with PVD_DEP. 3. VFR closed traffic operations shall be left closed traffic for all runways. d. Unplanned Missed Approach/Go-Around Procedures 1. VFR aircraft executing a go-around may be kept in the local traffic pattern. 2. When no conflicting traffic is involved, IFR aircraft shall be issued the following instructions in the event of an unplanned missed approach or go-around: (a) Runway 5 or 34: runway heading, maintain 2,100. (b) Runway 23 or 16: runway heading, maintain 2,000. BVA Providence ATCT Standard Operating Procedures Page 8

Chapter 5: Radar a. Frequency: 1. When all positions are consolidated: (a) APP will use frequency 123.67, with a voice channel of PVD_123.670. 2. The following splits can be staffed: (a) JUMPR (PVD_S_APP), with a voice channel of PVD_125.750. (b) Groton (PVD_SW_APP) with a voice channel of PVD_119.450. (c) New Bedford (PVD_B_APP), with a voice channel of PVD_128.700. (d) Arrival Radar (PVD_F_APP), with a voice channel of PVD_127.900. (e) Rhody (PVD_N_APP), with a voice channel of PVD_133.850. (f) Departure Radar (PVD_DEP), with a voice channel of PVD_123.670. Departures: 3. For noise abatement, aircraft must be retained on their Tower-assigned heading until the prescribed point in the table below: Runway Heading Until Heading Until 5 360 3 DME 080 3 DME 16 220 3 DME 180 3 DME 23 280 3 DME 160 5 DME or PVD180 34 330 3 DME 330 4 DME 4. Once past noise abatement restrictions, aircraft can be instructed to proceed on course. 5. When appropriate, climb departures to 10,000, lower requested altitude, or sector vertical limit, whichever is lowest. 6. Initiate automated handoff to appropriate ZBW sector when departing aircraft is cleared on course and ensured free of any potential traffic conflicts. 7. Issue transfer of radio communications to appropriate ZBW sector upon passing 6,000-7,000 feet or within 10NM of APP/CTR boundary, as appropriate. BVA Providence ATCT Standard Operating Procedures Page 9

b. Arrivals: 1. Aircraft on a STAR: (a) JORDN2 (RNAV): Handed off at HTO crossing JORDN at and maintain 11,000. (b) WIPOR2 (RNAV): Handed off no less than 10NM from WIPOR, crossing WIPOR at 11,000. 2. Unless operationally necessary (i.e., traffic, airspace, etc.), IFR turbojet and turboprops weighing 12,500 lb. or more must maintain at or above 5,000 until established within the descent airspace indicated in the applicable video map. 3. For noise abatement, jet aircraft will intercept the Runway 34 final approach course prior to crossing the Rocky Point Beach shoreline (4 DME from the PVD VORTAC). 4. IFR Arrivals shall be assigned no lower than 5,000 until separation can be assured with IFR departures. 5. Arrivals must be transferred to TWR prior to 3nm from the airport or prior to the final approach fix unless otherwise coordinated. Arrivals must not be transferred to TWR prior to 10nm from PVD. When being transferred, arrivals must be below 5,000. c. Practice Approaches: 1. Practice approach aircraft remaining at PVD must be issued the following climb out instructions by PVD_APP prior to transfer of control to TWR: (a) Non-jet aircraft: (1) Runway 5: Heading 100 (2) Runway 23: Heading 300 (3) Runway 34: Heading 100 (4) Runway 16: Heading 140 (b) Jet aircraft shall be placed on a noise abatement heading that is consistent with the heading assignment for jet aircraft. (c) Practice approach not remaining at PVD shall be treated as departures. 2. Standard separation services must be provided to VFR aircraft conducting practice instrument approaches at PVD, OQU, EWB, and GON when Tower is online (or being covered/provided by PVD_APP). BVA Providence ATCT Standard Operating Procedures Page 10

Chapter 6: Interfacility Coordination a. Airspace delegation overview: b. PVD ATCT and ACK: 1. Control on contact: (a) For turns up to 30 degrees either side of track, except traffic at or above 5,000 may not be descended below 5,000. 2. ACK shall handoff arrivals requesting an instrument approach to PVD via direct FFF (Plymouth NDB) at or below 3,000. 3. Traffic inbound EWB shall be handed off at or below 3,000. 4. Workload permitting, handoff EWB arrival traffic on a 10nm base leg for the landing runway. BVA Providence ATCT Standard Operating Procedures Page 11

5. Traffic overflying PVD ATCT airspace shall be at 6,000 or above, except V374 traffic. 6. PYM Arrival Procedures c. PVD ATCT and BOS: (a) PVD has responsibility for all instrument approaches at KPYM. (b) ACK may issue visual approaches to aircraft originating within ACK airspace provided aircraft will remain clear of PVD airspace. (1) A point-out must be approved before the approach clearance and after IFR cancellation. (c) PVD will issue all instrument approach clearances. 1. Control on contact: 2. PVD shall: 3. BOS shall: (1) PVD shall verbally coordinate all PYM arrivals prior to issuing an approach clearance. (2) PVD shall issue 118.2 (or if, Martha's Vineyard Radar is staffed, 133.75) as a missed approach or IFR cancellation frequency. (a) For turns up to 30 degrees either side of track. (b) For BOS, to descend traffic landing BOS to 6,000 and control to turn these aircraft to the right 30 degrees or to the left to heading 360, after passing WOONS intersection. (a) Handoff BOS jet arrivals to the appropriate BOS_APP sector no less than 5nm from the border at 5,000 7,000 or as previously coordinated. (b) When approaches to Runway 23 are in use, use caution to assure that any aircraft being vectored remain at least 1.5nm from the airspace border. (a) Transfer aircraft landing PVD cleared or vectored direct PVD at 4,000. (b) Coordinate with PVD when Runway 4R is active at BOS to activate Area 4R, allowing BOS arrivals to be descended through the PVD/A90 shelf to an altitude no lower than 6,000. BVA Providence ATCT Standard Operating Procedures Page 12

4. Delegated Airspace: (a) During standard operations, the airspace is split as shown below. PVD_APP can request control of Area 23 SFC-040 from A90. d. PVD ATCT and Y90: (b) When Boston is landing 4R, A90 will request control of Area 4R. PVD_APP controls to 6,000, and A90 has control at or above 7,000. 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 Providence ATCT Standard Operating Procedures Page 13

e. PVD_APP and N90: 1. Control on contact: f. PVD_APP and ZBW: (a) Beacon changes, descent, and turns up to 30 degrees either side track. (b) PVD for traffic landing GON for descent to 5,000 and turns direct GON. 1. Control on contact: (a) Turns up to 30 degrees either side of track. 2. EWB departures routed via PUT are not required to be climbed above 10,000 by CTR until passing 10nm northwest of the PVD VORTAC due to conflicts with arrival traffic to BOS passing over the PVD VORTAC. 3. ZBW Shall: (a) Route PVD and PYM arrivals: (1) Via ORW V130 MINNK or the WIPOR STAR to cross 10nm prior to ORW (WIPOR intersection) at 11,000. Transfer aircraft at or prior to 10nm from ORW (WIPOR). (2) Via V188 GON MINNK to cross GON at 11,000. Transfer aircraft prior to crossing V16. (3) From the southwest, south of V34: a. RNAV via JORDN MINNK or the JORDN STAR, to cross JORDN at 11,000. Transfer aircraft at or prior to JORDN. b. Non-RNAV arrivals via HTO R-070 to join PVD R-195, and cross 20nm northeast of HTO at 11,000. Transfer aircraft at or prior to 20nm northeast of HTO. (b) Route BOS non-turbojet arrivals and south satellite arrivals via WOONS (RNAV aircraft may be cleared direct JEWIT). These arrivals shall be handed off to PVD_APP at 11,000 prior to JEWIT. (c) Route N90 arrivals via ORW BOROS CCC or the NELIE STAR to cross 10nm prior to ORW at 11,000, and transfer aircraft to PVD_APP at or prior to 10nm of ORW. BVA Providence ATCT Standard Operating Procedures Page 14

Chapter 7: Intrafacility Coordination 7.0 Runway 5/34 Flow a. Sectors BVA Providence ATCT Standard Operating Procedures Page 15

7.1 Runway 23 Flow a. Sectors BVA Providence ATCT Standard Operating Procedures Page 16

7.2 Arrival Sectors a. PVD arrivals from Groton Radar (GR) and JUMPR Radar (JR) must be routed as listed below for sequencing by Arrival Radar (AR). Once traffic is no longer a factor, transfer the aircraft to AR as soon as practical. 1. Runway 05 2. Runway 23 3. Runway 16 4. Runway 34 (a) Traffic from JR routed MINNK direct PVD. (b) Traffic from GR vectored on a heading for a 15nm final. (a) Traffic from JR routed MINNK direct PVD. (b) Traffic from GR vectored on a right downwind. (a) Traffic from JR routed MINNK direct PVD. (b) Traffic from GR vectored on a heading through the arrival corridor for a right downwind. (a) Traffic from JR vectored on a heading to a 12nm final. (b) Traffic from GR routed direct PVD. b. All IFR turbojet and turboprops weighing 12,500 lb or more must maintain at or above 5000 until established in the descent area airspace. c. When Runway 05 or 34 is the advertised landing runway, AR has control for turns and descent for PVD, OQU, UUU and EWB arrivals on contact from GR or JR sectors. BVA Providence ATCT Standard Operating Procedures Page 17