CXY SOP: Difference between revisions

From New York ARTCC
VisualWikitext
(still massively WIP)
(Created page.)
Line 2: Line 2:
|Facility=Capital City ATCT
|Facility=Capital City ATCT
|Version=3
|Version=3
|Title=
}}
}}
Bookmarks: '''[[#Area at a glance|Top]] · [[#ATCT|CXY ATCT]] ( [[#Clearance Delivery|DEL]] | [[#Ground|GND]] | [[#Tower|TWR]])


== Area at a glance ==
== Area at a glance ==
{{leftright
|right-width=col-md-4
|right=
<div class="well">
__TOC__
</div>
|left-width=col-md-8
|left=
<div class="boxed">
{{{!}} class="table table-bordered table-hover"
! ICAO Code
! Airport Name
! Airspace
! IFR Beacon Code
! VFR Beacon Code
{{!}}-
{{!}} '''KCXY'''
{{!}} Capital City Airport
{{!}} D
{{!}} 6650 {{--}} 6657
{{!}} 0601 {{--}} 0677
{{!}}}
[[Image:MDT_TRACON.png|500px|right]]
; Purpose
:This document prescribes the procedures to be utilized for providing air traffic control services at the Capital City Air Traffic Control Tower (ATCT). The procedures described herein are supplemental to the New York ARTCC Basic Control Procedures and FAA Order JO 7110.65.


; Distribution
{| class="table table-sop table-sop-airports"
:This order is distributed to all New York ARTCC personnel.
|-
{{TableHeaders-Airports}}
|-
| {{TableRow-Airport
|Ident=KCXY
|Name=Capital City
|Class=D
|SqIFR=6650-6657
|SqVFR=0601-0677
}}
|}


; Procedural Deviations
{{Layout-PullRight
:Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. A situation may arise that is not adequately covered herein; in such an event use good judgment to adequately resolve the problem.
|[[Image:TraconOverview-MDT.png|500px|right]]
{{-}}
</div>
}}
}}
{{SOPBoilerplate
|Facility=the Capital City Airport Traffic Control Tower (ATCT)}}
===== Departure Sequencing =====
: Capital City is a satellite of '''Harrisburg International Airport'''. TRACON service to Teterboro is provided by Harrisburg ATCT/TRACON.
{{Layout-Clearfix}}


=== Operational Positions ===
=== Operational Positions ===


{{tabs
<tabber>
|uniqueid=positions
|-|CXY ATCT=
|label1=CXY ATCT
|content1=
{{{!}} class="table table-hover table-condensed no-border-top"
! Position
! Callsign
! Radio Name
! Frequency
! Identifier
{{!}}-
{{!}}Ground
{{!}}CXY_GND
{{!}}Capital City Ground
{{!}}121.900
{{!}}HJ
{{!}}-
{{!}}Tower
{{!}}CXY_TWR
{{!}}Capital City Tower
{{!}}119.500
{{!}}HH
{{!}}-
{{!}}ATIS
{{!}}KCXY_ATIS
{{!}}
{{!}}134.950
{{!}}
{{!}}}


|label2=MDT TRACON
{| class="table table-sop table-sop-operational-positions"
|content2=
|-
{{MDT TRACON Radar Positions}}
{{TableHeaders-OperPos}}
|-
| {{TableRow-OperPos
|PosDesc=Ground
|Callsign=CXY_GND
|RadioName=Capital City Ground
|Freq=121.900
|Ident=HJ
}}
}}
| {{TableRow-OperPos
|PosDesc=Tower
|Callsign=CXY_TWR
|RadioName=Capital City Tower
|Freq=119.500
|Ident=HH
}}
| {{TableRow-OperPos
|PosDesc=ATIS
|Callsign=KCXY_ATIS
|RadioName=
|Freq=134.950
|Ident=
}}
|}
|-|MDT TRACON=
{{Extract:OperPositions-MDT-TRACON}}
</tabber>


== ATCT ==
== ATCT ==
=== Clearance Delivery ===
=== Clearance Delivery ===
{{tabs
 
|uniqueid=CXY_DEL
<tabber>
|label1=<span class="changed">Valid Exits</span>
|-|Valid Exits=
|content1=
 
{{leftright
<div class="ny-pull-right" style="width: 35%">
|right-width=col-md-4
{| class="table table-sop table-sop-compact"
|right=
! Exit Gate
{{MDT Scratchpad}}
! Exit
|left-width=col-md-8
! Scratchpad
|left=
|-
[[File:MDT Exit Direction Chart.png|550px]]
| rowspan="2" | '''North (N)'''
;Notes
| GAAPP
<div class="changed">
| GAA
|-
| SEG
| SEG
|-
| rowspan="3" | '''Northeast (NE)'''
| ETX
| ETX
|-
| LVZ
| LVZ
|-
| FJC
| FJC
|-
| rowspan="3" | '''East (E)'''
| LRP
| LRP
|-
| PTW
| PTW
|-
| ARD
| ARD
|-
| '''Southeast (SE)'''
| DQO
| DQO
|-
| rowspan="9" | '''Southwest (SW)'''
| HAR
| HAR
|-
| BRNAN
| BRN
|-
| JST
| JST
|-
| VINSE
| VIN
|-
| THS
| THS
|-
| SCAPE
| SCA
|-
| GRAMO
| GRA
|-
| MRB
| MRB
|-
| EMI
| EMI
|-
| rowspan="2" | '''Northwest (NW)'''
| MCMAN
| MCM
|-
| PSB
| PSB
|-
|}
</div>
 
[[File:ExitGateDiagram-MDT.png|550px]]
 
 
===== Notes =====
# While strict exit direction points are not required at MDT, the guide above may come in handy for directing pilots to proper exits for departing the area.
# While strict exit direction points are not required at MDT, the guide above may come in handy for directing pilots to proper exits for departing the area.
# KIACK is only a valid exit if preceded by GAAPP. The route must therefore read <code>GAAPP KIACK...</code>
# KIACK is only a valid exit if preceded by GAAPP. The route must therefore read <code>GAAPP KIACK...</code>
# MCMAN is used for aircraft routed via V33/J64/Q62.
# MCMAN is used for aircraft routed via V33/J64/Q62.
# Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.
# Traffic filed via EMI to join J48 should be re-routed via <code>GRAMO VINNY EMI</code>.
</div>
 
}}
|-|Departure Frequency=


|label2=Departure Frequency
{| class="table table-sop"
|content2=
{{{!}} class="table table-bordered blue-header pull-right span3"
! Position
! Position
! Frequency
! Frequency
! {{!}} Code
! Code
{{!}}-
|-
{{!}} MDT_SW_APP
| MDT_SW_APP
{{!}} 124.1
| 124.100
{{!}} HK
| HK
{{!}}-
|-
{{!}} MDT_W_APP
| NY_W_CTR
{{!}} 124.1
| 132.175
{{!}} HK
| N34
{{!}}-
|-
{{!}} MDT_APP
| NY_CTR
{{!}} 124.1
| 125.325
{{!}} HK
| N56
{{!}}-
|}
{{!}} NY_CTR
{{!}} 125.32
{{!}} N56
{{!}}}
The table on the right lists the common frequencies used as departure frequency by CXY Clearance Delivery. The first available controller in this list should be handling departures.


Note that this table only serves as a guide. The actual departure frequency has to be determined based on coordination with the other online controllers.
Note that this table only serves as a guide. The actual departure frequency has to be determined based on coordination with the other online controllers.


If there is no other controller online that would accept departures from CXY, use UNICOM frequency (122.8).
|-|LOA Routes=
 
Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through letters of agreement (LOA). These routes have been added to the [[PRD|Preferred Route Database]].


|label3=LOA Routes
|content3=
Routing to certain airports in ZNY, ZDC and ZBW ARTCCs have been precoordinated through letters of agreement (LOA). These routes have been added to the [[PRD|Preferred Route Database]]. Therefore, PRD must be referenced for all departures.


|label4=<span class="changed">IFR Departures</span>
|-|IFR Departures=
|content4=
====Initial Altitude====
<div class="changed">
 
# The initial altitude for IFR departures of all types is 3,000’ whereas higher may be expected in 10 minutes after departure.
# The initial altitude for IFR departures of all types is 3,000' whereas higher may be expected in 10 minutes after departure.
# There is no published departure procedure out of Harrisburg. All aircraft must be cleared to their destination via radar vectors to a MDT exit.
# There is no published departure out of CXY. All aircraft must be cleared to their destination via radar vectors to a fix.
# Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.
# Traffic filed via EMI to join J48 should be re-routed via <code>GRAMO VINNY EMI</code>.
</div>
# Runways 8, 12 and 26 have Obstacle Departure Procedures (ODPs). ATC does not assign ODPs, but pilots may request to fly them. If they do, simply advise Local & Departure controllers of the request, but issue the IFR clearance as normal.
 
|-|VFR Departures=
=== ===


|label5=VFR Departures
# Capital City is a '''Class Delta''' airport. All VFR traffic must establish two-way radio communications.
|content5=
# CXY's proximity to MDT requires special attention to VFR aircraft:
Capital City is a '''[[VFR Operations#Airspace_Classification|Class Delta]]''' airport. All VFR traffic '''must''' establish two-way radio communications.
## Aircraft that will climb into the overlying MDT Class Charlie airspace (above 2,500'): Assign a '''MDT TRACON''' departure frequency and a discrete squawk code.
## Aircraft that will laterally enter the MDT Class Charlie surface area (at or below 2,500'): Assign a '''MDT Tower''' departure frequency and a discrete squawk code.
## Aircraft that will remain outside the MDT Class Charlie are handled with normal Class Delta procedures.
### If flight following services are requested, assign these departures a '''MDT TRACON''' departure frequency and squawk code.


See the [[VFR Operations#Class D VFR Operations|VFR Operations]] document for detailed explanation of applicable VFR procedures.
</tabber>
}}


=== Ground ===
=== Ground ===
<div class="boxed">
; Departure Sequencing
; Departure Sequencing
{{{!}} class="pull-right span4 table table-bordered table-condensed blue-header"
 
! class=nowrap {{!}} Exit Gate
<div style="width:40%; float:right;">
{| class="table table-sop table-sop-compact"
! class=nowrap | Exit Gate
! Exits
! Exits
{{!}}-
|-
{{!}}'''North'''
|'''North'''
{{!}}GAAPP, SEG
|GAAPP, SEG
{{!}}-
|-
{{!}}'''Northeast'''
|'''Northeast'''
{{!}}ETX, LVZ, FJC
|ETX, LVZ, FJC
{{!}}-
|-
{{!}}'''East'''
|'''East'''
{{!}}LRP, PTW, ARD
|LRP, PTW, ARD
{{!}}-
|-
{{!}}'''Southeast'''
|'''Southeast'''
{{!}}DQO
|DQO
{{!}}-
|-
{{!}} '''Southwest'''
|'''Southwest'''
{{!}}HAR, BRNAN, JST, VINSE, THS, SCAPE, GRAMO, MRB, EMI
|HAR, BRNAN, JST, VINSE, THS, SCAPE, GRAMO, MRB, EMI
{{!}}-
|-
{{!}} '''Northwest'''
|'''Northwest'''
{{!}}MCMAN, PSB
|MCMAN, PSB
{{!}}}
|}
Aircraft should be sequenced to depart in the following order:
</div>
#By alternating gate group.
 
#If not the above, then by alternating exit.
#Aircraft should be sequenced to depart in the following order:
#If not the above, then by aircraft type largest to smallest.
##By alternating gate group.
##If not the above, then by alternating exit.
##If not the above, then by aircraft type largest to smallest.
 
; Taxi Routes
#As the taxiway system is simple, there are no pre-defined routings.
#If inbound and outbound aircraft will come into conflict, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft. You may use conditional taxi instructions to accomplish this.


; Runway Ownership and Crossings
=== Tower ===
#Closed runways shall be owned by Ground Control. The only time runways will ever be closed is during events, and closures must be authorized by the TMU. We do not simulate runway closures on VATSIM during standard day-to-day operations.
#Transfer of runway ownership, between Ground Control and Local Control, shall be accomplished verbally (or textually).
#Ground Control is authorized to cross all active runways with coordination with Local Control.


; Intersection Departures and Usable Runway Lengths
<tabber>
#Since departures can come from multiple taxiways, the sequencing for intersection departures is a bit more involved as it will require Ground Control to properly push the strip to the tower controller in the correct order.
#For intersection departures, state the usable runway distance if that distance is not broadcast in the ATIS. Below is a list of usable runway lengths from common intersections. If the numbers are not divisible to 50, you must round them '''down''' to the nearest 50 feet before providing the information to the pilot.
#:{{phraseology|Runway two six at lima, taxi via alpha, lima. Runway two six at lima intersection departure, three thousand eight hundred and fifty feet takeoff distance available.}}


::{{{!}} class="table table-bordered table-condensed blue-header span8"
|-|Tower Procedures=
! 8 {{!}}{{!}} 12 {{!}}{{!}} 26 {{!}}{{!}} 30
{{!}}-
{{!}} '''F''' (3,550’) {{!}}{{!}} '''F''' (2,273') {{!}}{{!}} '''L''' (3,850’) {{!}}{{!}} '''H''' (2,750’)
{{!}}-
{{!}} '''H''' (2,600’) {{!}}{{!}} '''C''' (1,600') {{!}}{{!}} '''H''' (2,350’) {{!}}{{!}}  '''C''' (2,250')
{{!}}-
{{!}} '''L''' (1,100’) {{!}}{{!}}  '''H''' (1,100') {{!}}{{!}} '''F''' (1,400')  {{!}}{{!}} '''F''' (1,505')
{{!}}}
{{-}}


;Aircraft Movement
==== Tower Procedures ====
#As the taxiway system is simple, there are no pre-defined routings.
#Since there are no parallel taxiways, you may use each taxiway as a two-way road whereby aircraft may be taxied in the opposite direction on the same taxiway at the same time. When you do this, ensure that both aircraft are told to watch out for the other. This procedure is only available to single engine props during daylight hours as they are narrow enough to be able to fit two abreast.
#When the above is not available, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft. You may use conditional taxi instructions to accomplish this.
</div>


=== Tower ===
{{tabs
|uniqueid=CXY_TWR
|label1=Tower Procedures
|content1=
; Releases
; Releases
:Releases from Capital City Airport are on a per aircraft request basis unless blanket release is coordinated.  
* Releases from Capital City Airport are on a per-aircraft request basis unless blanket release is coordinated.


; Separation
; Separation
:The standard departure separation technique to be used is anticipated radar separation. When wake turbulence is a factor, use timed separation in accordance with {{7110|para=3-9-6|link=https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap3_section_9.html}}.
The standard departure separation technique to be used is anticipated radar separation. Only use timed separation if the pilot requests it.


; Radar
; Radar
:This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Harrisburg TRACON, this tower will NOT radar identify departing IFR aircraft and will instruct a departure to contact departure control once the aircraft appears to be clear of any traffic. It is imperative that tower controllers observe departing traffic turning towards the assigned heading before handing off. VFR aircraft can and '''must''' be radar identified to receive flight following within the tower's airspace, otherwise it is not necessary.
This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Harrisburg TRACON, this tower will NOT radar identify departing IFR aircraft and will instruct a departure to contact departure control once the aircraft appears to be clear of any traffic. It is imperative that tower controllers observe departing traffic turning towards the assigned heading before handing off.


;Aircraft Exiting the Runway
|-|Runway Selection=
:Arriving aircraft shall be issued a turn onto one of the taxiways adjacent to the landing runway to ensure the aircraft continues its taxi away from the runway exit. Handoff to Ground Control after the aircraft starts taxiing away from the active runway. Local Control will coordinate with Ground Control, as needed, to determine the traffic flow on the taxiways.


|label2=Runway Selection
=====Runway Selection=====
|content2=
; Runway Selection


{{{!}} class="span6 table table-bordered table-condensed blue-header"
{| class="table table-sop"
! rowspan=2 width="25%" {{!}} Wind Speed
! width="25%" | Wind Speed (kts)
! rowspan=2 width="25%" {{!}} Direction
! width="25%" | Direction (°M)
! colspan=2 width="50%" {{!}} Configuration
! width="15%" | Depart
{{!}}-
! width="15%" | Land
!  width="25%" {{!}} Depart
|-
! width="25%" {{!}} Land
|'''0-4'''
{{!}}-
|Any
{{!}}'''0-4'''
|26, 30
{{!}}Any
|26, 30
{{!}}26, 30
|-
{{!}}26, 30
| rowspan="2" | '''5+'''
{{!}}-
|350-170
{{!}} rowspan=2 {{!}} '''> 4'''
|8, 12
{{!}}350-170
|8, 12
{{!}}8, 12
|-
{{!}}8, 12
|171-349
{{!}}-
|26, 30
{{!}}171-349
|26, 30
{{!}}26, 30
|}
{{!}}26, 30
{{!}}}
{{-}}


; Notes
'''Notes'''
# Normal runway usage configurations are:
# Normal runway configurations are:
## '''West Operations:''' Runways 26 and 30.
##'''West Operations:''' Runways 26 and 30.
## '''East Operations:''' Runways 8 and 12.
##'''East Operations:''' Runways 8 and 12.
# Runway 12/30 is only ~3700’ feet long. Larger aircraft may have to use runway 8/26.
# If visibility is '''below 1 3/4 SM''', runway 8 must be used as it is the only runway with an ILS approach.
# If visibility is '''less than 1 3/4 SM''', runway 8 MUST be used as it is the only runway with an ILS Approach.
# CXY runway configuration is dependent on MDT. If MDT is on a west flow configuration, CXY must be on west flow as well.
# If visibility is '''less than 3/4 SM''', no instrument approaches are available. Aircraft CANNOT land at CXY.
 
# CXY runway configuration is dependent on MDT. For example, if MDT is on a west flow runway configuration, then CXY must be on west flow as well.
|-|Departure Heading (IFR)=
Assign IFR aircraft a heading listed in the table below, unless otherwise coordinated with the departure controller.
 
{| class="table table-sop"
! Runway !! Heading
|-
| 8
| 050
|-
| 12
| 200
|-
| 26
| Runway heading
|-
| 30
| 290
|}


|label3=Departure Heading (IFR)
|-|LAHSO=
|content3=
'''Land and Hold Short Operations'''
IFR aircraft must be assigned a heading listed in the table below, unless otherwise coordinated with the departure controller.
# Land and Hold Short Operations (LAHSO) may only be conducted for runway 26:
:{{phraseology|Fly heading (heading), wind (wind), runway (runway), cleared for takeoff.}}
## Hold short runway 12 / 30, ALD 3,450'
# LAHSO is only authorized when there exists at least 3 sm of visibility and 1,000' ceiling, and no windshear is reported.
|-|Missed Approach=


{{{!}} class="table table-bordered table-condensed blue-header margin-top span4"
'''Missed Approach Procedures'''
! Runway
! Heading
{{!}}-
{{!}} 8
{{!}} 050
{{!}}-
{{!}} 12
{{!}} 200
{{!}}-
{{!}} 26
{{!}} Runway Heading
{{!}}-
{{!}} 30
{{!}} 290
{{!}}}


|label4=LAHSO
<div style="float:right; width:40%; margin-left:1em;">
|content4=
{{{!}} class="span4 table table-bordered table-condensed blue-header margin-top margin-left pull-right"
{| class="table table-sop table-sop-compact"  
! Landing Runway
! width="20%" | Runway
! Hold Short Runway
! width="20%" | Heading
! Available Landing Distance
! width="20%" | Altitude
{{!}}-
|-
{{!}} 26
| 8
{{!}} 12 / 30
| Passing 1300, turn left heading 050
{{!}} 3,450'
| 3,000
{{!}}}
|-
;Land and Hold Short Operations
| 12
#Land and Hold Short Operations (LAHSO) may only be conducted for the runway 26, as specified in the table to the right.
| 200
#LAHSO is only authorized when there exits at least 3 miles of visibility and 1,000' ceiling, and no wind shear has been reported.
| 3,000
|-
|rowspan="2"| 26
| Runway heading
| 3,000
|-
|colspan="2"| <center>Except if RNAV 26 approach: ''Assign published missed''</center>
|-
| 30
| 290
| 3,000
|}


|label5=Missed Approach
</div>
|content5=
{{{!}} class="span4 table table-bordered table-condensed blue-header margin-top margin-left pull-right"
! Runway
! Missed Approach Instruction
{{!}}-
{{!}} 8
{{!}} Climb to 3000 feet and assign heading 050 leaving 1300 feet.
{{!}}-
{{!}} 12
{{!}} Assign heading 200 and climb to 3000 feet.
{{!}}-
{{!}} 26
{{!}} IFR aircraft on RNAV (GPS) Approach must be issued the published missed approach. Otherwise, assign runway heading and climb to 3000 feet.
{{!}}-
{{!}} 30
{{!}} Assign heading 290 and climb to 3000 feet.
{{!}}}
;Missed Approach Procedures
# Missed approaches or go-arounds must be issued the instructions listed on the table to the right prior to release to the TRACON frequency, unless otherwise coordinated with the TRACON controller.
# If the conditions are VMC (Visual Meteorological Conditions), then the Tower may keep the aircraft in the pattern and clear the aircraft for a visual approach in accordance with {{7110|para=7-4-3|link=https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap7_section_4.html}}. Use best judgement to determine whether to keep the aircraft in the pattern or not.
# Note: During VMC conditions VFR aircraft or IFR aircraft executing a go-around / missed approach should be retained in right closed traffic for Runway 8, if pilot concurs. If able, ensure aircraft starts crosswind prior to departure end of the runway. If unable, immediately coordinated with Harrisburg Departure Control. Issue any MDT traffic landing Runway 13 to the pilot, and wake turbulence advisories as necessary. If a conflict with MDT traffic appears imminent, turn aircraft as necessary to avoid a collision and coordinate immediately. Retain communication with the aircraft until coordination is completed.


;Additional Information
'''Additional Information'''
# Separation must be based on altitude initially during all missed approaches or go-arounds. Prior to issuing a climb to 3,000’, interval altitudes such as 2,000’ may be utilized to prevent converging targets from losing separation.
# Separation must be based on altitude initially during all missed approaches or go-arounds. Interval altitudes such as 2,000’ may be utilized to prevent converging targets from losing separation.
# In order to prevent increased workload on the TRACON, consider issuing missed approaches or go-arounds speed restrictions in accordance with FAA Order JO 7110.65.
# Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
# Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
# Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the headings and altitudes listed on the table if using them would compromise safety.
# Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the headings and altitudes listed on the table if using them would compromise safety.


|label6=VFR Procedures  
|content6=
; Airspace
|-|VFR Procedures=
[[File:MDTATCTWest.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in a '''West Flow'''.]]
[[File:MDTATCTEast.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in an '''East Flow'''.]]
=====Airspace=====


# Class [[VFR Operations#Airspace_Classification|DELTA]].
[[File:Airspace-MDT-WEST-ATCT.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in a '''West Flow'''.]]
[[File:Airspace-MDT-EAST-ATCT.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in an '''East Flow'''.]]
 
# Class Delta.
# The tower's delegated airspace in dependent on runway configuration (West Flow or East Flow). The airspace is depicted on the two diagrams to the right.
# The tower's delegated airspace in dependent on runway configuration (West Flow or East Flow). The airspace is depicted on the two diagrams to the right.
# Due to CXY ATCT being closely located to the MDT ATCT, the following procedures must apply between the towers:
# Due to CXY ATCT being closely located to the MDT ATCT, the following procedures must apply between the towers:
## MDT ATCT must coordinate with CXY ATCT any traffic that may impact the '''Area B''' portion of the CXY Class D Surface Area (reference the diagrams to the right).
## MDT ATCT must coordinate with CXY ATCT any traffic that may impact the '''Area B''' portion of the CXY Class D Surface Area (reference the diagrams to the right).
## CXY ATCT must coordinate with MDT ATCT any traffic that may impact the '''Area A''' portion of the CXY Class D Surface Area (reference the diagrams to the right), including right closed traffic to runway 26.
## CXY ATCT must coordinate with MDT ATCT any traffic that may impact the '''Area A''' portion of the CXY Class D Surface Area (reference the diagrams to the right), including right closed traffic to runway 26.
## VFR aircraft transitioning between CXY and MDT airports must be handled as closed traffic and kept within towers class D airspace '''without''' any handoff to the TRACON sectors.
## VFR aircraft transitioning between CXY and MDT airports must be handled as closed traffic and kept within Local's surface airspace '''without''' any handoff to the TRACON sectors.
 
=====Departures=====
 
Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow. If the VFR aircraft intend to receive flight following services from MDT TRACON, the following headings and procedures must apply prior to handoff:
 
{| class= "table table-sop"
! Runway !! Departure Instruction !! Releases
|-
| 8
| Heading 050 unless otherwise coordinated with TRACON
| Release Required
|-
| 12
| Right turn to 200 unless otherwise coordinated with TRACON
| Automatic Release
|-
| 26
| Heading 180 clockwise to 290 as close to on course as possible
| Automatic Release
|-
| 30
| Heading 180 clockwise to 290 as close to on course as possible
| Automatic Release
|}
 
=====Flight Following=====
 
Ensure VFR aircraft receiving flight following are transferred to MDT ATCT/TRACON in a timely manner.


; Departures
=====Over-flights=====
:Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow. If the VFR aircraft intend to receive flight following services from MDT TRACON, the following headings and procedures must apply prior to handoff:


:{{{!}} class="table table-bordered table-condensed blue-header margin-top span6"
Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary.
! Runway
! Departure Instruction
! Releases
{{!}}-
{{!}} 8
{{!}} Heading 050 unless otherwise coordinated with TRACON
{{!}} Release Required
{{!}}-
{{!}} 12
{{!}} Right turn to 200 unless otherwise coordinated with TRACON
{{!}} Automatic Release
{{!}}-
{{!}} 26
{{!}} Heading 180 clockwise to 290 as close to on course as possible
{{!}} Automatic Release
{{!}}-
{{!}} 30
{{!}} Heading 180 clockwise to 290 as close to on course as possible
{{!}} Automatic Release
{{!}}}


; Flight Following
''Note:'' The Susquehanna River is an excellent local landmark to help overflights navigate through the airspace. Additionally, it can be used to help deconflict local traffic with MDT.
:All aircraft should remain on the tower frequency unless the route of flight will or may impede the operations of MDT TRACON while operating inside the tower's delegated portion of the Class Delta, or the aircraft will leave the tower's delegated portion of the Class Delta.


; Over-flights
=====Pattern Work=====
:Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary.


; Pattern Work
Use the following as a guide for pilots wanting to perform pattern work at CXY.
:Use the following as a guide for pilots wanting to perform pattern work at CXY.
 
:{{{!}} class="span6 table table-bordered table-condensed blue-header"
<div style="float:left; width:60%">
! Runway
{| class= "table table-sop table-sop-compact"
! Direction
! Runway !! Direction
{{!}}-
|-
{{!}}'''8'''
|'''8'''
{{!}} Left
| Left
{{!}}-
|-
{{!}}'''12'''
|'''12'''
{{!}} Right
| Right
{{!}}-
|-
{{!}}'''26'''
|'''26'''
{{!}} Right
| Right
{{!}}-
|-
{{!}}'''30'''
|'''30'''
{{!}} Left
| Left
{{!}}}
|}
:NOTE: All props should be at 1,500’ and jets at 2,000’. Adjust these altitudes when necessary to avoid over-flights or normal IFR traffic flow.
</div>
}}
 
''Note:'' All props should be at 1,500’ and jets at 2,000’. Adjust these altitudes when necessary to avoid over-flights or normal IFR traffic flow.
 
</tabber>


== TRACON ==
== TRACON ==
TRACON services for Capital City Airport are provided by [[MDT SOP#TRACON|MDT TRACON]].
TRACON services for Capital City Airport are provided by MDT TRACON.


== Appendix ==
== Appendix ==
=== Changelog ===
=== Changelog ===
{| class="table table-bordered table-condensed blue-header"
{| class="table table-sop table-sop-compact"
! Change
! style="white-space: nowrap;" | Change &nbsp;
! Date
! style="white-space: nowrap;" | Date Published &nbsp;
! Description
! Description
|-
|-
Line 408: Line 449:
| 26 Aug 2024
| 26 Aug 2024
| Updated GRAMO VINNY EMI routing to J48.
| Updated GRAMO VINNY EMI routing to J48.
|-
| '''CHG3'''
| 9 Nov 2024
| Converted to new WIki format.
|}
|}

Revision as of 15:57, 9 November 2024

New York ARTCC
Standard Operating Procedure — Capital City ATCT

Rev. 3 — Revised: 2024-11-09

Area at a glance

ICAO Code Airport Name Airspace
KCXY Capital City D
Purpose
This document prescribes the procedures to be utilized for providing air traffic control services at the Capital City Airport Traffic Control Tower (ATCT). The procedures described herein are supplemental to the New York ARTCC Standard Operating Procedures and FAA Order JO 7110.65.
Distribution
This order is distributed to all New York ARTCC personnel.
Procedural Deviations
Exceptional or unusual requirements may dictate procedural deviations or supplementary procedures to this order. A situation may arise that is not adequately covered herein; in such an event use good judgment to adequately resolve the problem.


Departure Sequencing
Capital City is a satellite of Harrisburg International Airport. TRACON service to Teterboro is provided by Harrisburg ATCT/TRACON.


Operational Positions

Position Callsign Radio Name Frequency Identifier
Ground CXY_GND Capital City Ground 121.900 HJ
Tower CXY_TWR Capital City Tower 119.500 HH
ATIS KCXY_ATIS 134.950

Sector Callsign Frequency Identifier Combined Sector
Harrisburg (HAR) MDT_SW_APP 124.100 HK Primary TRACON
Lancaster (LRP) MDT_SE_APP 126.450 HS
Ravine (RAV) MDT_N_APP 118.250 HG
Reading RDG_APP 125.150 RX Covered by MDT TRACON 0000-0600 local time

Notes:

  • When RDG_APP is not staffed, MDT TRACON may provide top-down services at RDG regardless of local time.
  • When splitting MDT TRACON, split into HAR & LRP sectors first.

ATCT

Clearance Delivery

Exit Gate Exit Scratchpad
North (N) GAAPP GAA
SEG SEG
Northeast (NE) ETX ETX
LVZ LVZ
FJC FJC
East (E) LRP LRP
PTW PTW
ARD ARD
Southeast (SE) DQO DQO
Southwest (SW) HAR HAR
BRNAN BRN
JST JST
VINSE VIN
THS THS
SCAPE SCA
GRAMO GRA
MRB MRB
EMI EMI
Northwest (NW) MCMAN MCM
PSB PSB


Notes
  1. While strict exit direction points are not required at MDT, the guide above may come in handy for directing pilots to proper exits for departing the area.
  2. KIACK is only a valid exit if preceded by GAAPP. The route must therefore read GAAPP KIACK...
  3. MCMAN is used for aircraft routed via V33/J64/Q62.
  4. Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.
Position Frequency Code
MDT_SW_APP 124.100 HK
NY_W_CTR 132.175 N34
NY_CTR 125.325 N56
Note that this table only serves as a guide. The actual departure frequency has to be determined based on coordination with the other online controllers.

Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through letters of agreement (LOA). These routes have been added to the Preferred Route Database.

Initial Altitude

  1. The initial altitude for IFR departures of all types is 3,000' whereas higher may be expected in 10 minutes after departure.
  2. There is no published departure out of CXY. All aircraft must be cleared to their destination via radar vectors to a fix.
  3. Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.
  4. Runways 8, 12 and 26 have Obstacle Departure Procedures (ODPs). ATC does not assign ODPs, but pilots may request to fly them. If they do, simply advise Local & Departure controllers of the request, but issue the IFR clearance as normal.

  • Capital City is a Class Delta airport. All VFR traffic must establish two-way radio communications.
  • CXY's proximity to MDT requires special attention to VFR aircraft:
    1. Aircraft that will climb into the overlying MDT Class Charlie airspace (above 2,500'): Assign a MDT TRACON departure frequency and a discrete squawk code.
    2. Aircraft that will laterally enter the MDT Class Charlie surface area (at or below 2,500'): Assign a MDT Tower departure frequency and a discrete squawk code.
    3. Aircraft that will remain outside the MDT Class Charlie are handled with normal Class Delta procedures.
      1. If flight following services are requested, assign these departures a MDT TRACON departure frequency and squawk code.

    • Ground

    Departure Sequencing
    Exit Gate Exits
    North GAAPP, SEG
    Northeast ETX, LVZ, FJC
    East LRP, PTW, ARD
    Southeast DQO
    Southwest HAR, BRNAN, JST, VINSE, THS, SCAPE, GRAMO, MRB, EMI
    Northwest MCMAN, PSB
    1. Aircraft should be sequenced to depart in the following order:
      1. By alternating gate group.
      2. If not the above, then by alternating exit.
      3. If not the above, then by aircraft type largest to smallest.
    Taxi Routes
    1. As the taxiway system is simple, there are no pre-defined routings.
    2. If inbound and outbound aircraft will come into conflict, hold departures on the ramp until the inbound aircraft is clear of the outbound aircraft. You may use conditional taxi instructions to accomplish this.

    Tower

    Tower Procedures

    Releases
    • Releases from Capital City Airport are on a per-aircraft request basis unless blanket release is coordinated.
    Separation

    The standard departure separation technique to be used is anticipated radar separation. Only use timed separation if the pilot requests it.

    Radar
    This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Harrisburg TRACON, this tower will NOT radar identify departing IFR aircraft and will instruct a departure to contact departure control once the aircraft appears to be clear of any traffic. It is imperative that tower controllers observe departing traffic turning towards the assigned heading before handing off.
    Runway Selection
    Wind Speed (kts) Direction (°M) Depart Land
    0-4 Any 26, 30 26, 30
    5+ 350-170 8, 12 8, 12
    171-349 26, 30 26, 30

    Notes

    1. Normal runway configurations are:
      1. West Operations: Runways 26 and 30.
      2. East Operations: Runways 8 and 12.
    2. If visibility is below 1 3/4 SM, runway 8 must be used as it is the only runway with an ILS approach.
    3. CXY runway configuration is dependent on MDT. If MDT is on a west flow configuration, CXY must be on west flow as well.

    Assign IFR aircraft a heading listed in the table below, unless otherwise coordinated with the departure controller.

    Runway Heading
    8 050
    12 200
    26 Runway heading
    30 290

    Land and Hold Short Operations
    1. Land and Hold Short Operations (LAHSO) may only be conducted for runway 26:
      1. Hold short runway 12 / 30, ALD 3,450'
    2. LAHSO is only authorized when there exists at least 3 sm of visibility and 1,000' ceiling, and no windshear is reported.
    Missed Approach Procedures


    Runway Heading Altitude
    8 Passing 1300, turn left heading 050 3,000
    12 200 3,000
    26 Runway heading 3,000
    Except if RNAV 26 approach: Assign published missed
    30 290 3,000

    Additional Information

    1. Separation must be based on altitude initially during all missed approaches or go-arounds. Interval altitudes such as 2,000’ may be utilized to prevent converging targets from losing separation.
    2. Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
    3. Sound judgment must be exercised when dealing with go-arounds or missed approaches. Deviate as necessary from the headings and altitudes listed on the table if using them would compromise safety.
    Airspace
    Outline of the Harrisburg Tower airspace in a West Flow.
    Outline of the Harrisburg Tower airspace in an East Flow.
    1. Class Delta.
    2. The tower's delegated airspace in dependent on runway configuration (West Flow or East Flow). The airspace is depicted on the two diagrams to the right.
    3. Due to CXY ATCT being closely located to the MDT ATCT, the following procedures must apply between the towers:
      1. MDT ATCT must coordinate with CXY ATCT any traffic that may impact the Area B portion of the CXY Class D Surface Area (reference the diagrams to the right).
      2. CXY ATCT must coordinate with MDT ATCT any traffic that may impact the Area A portion of the CXY Class D Surface Area (reference the diagrams to the right), including right closed traffic to runway 26.
      3. VFR aircraft transitioning between CXY and MDT airports must be handled as closed traffic and kept within Local's surface airspace without any handoff to the TRACON sectors.
    Departures

    Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow. If the VFR aircraft intend to receive flight following services from MDT TRACON, the following headings and procedures must apply prior to handoff:

    Runway Departure Instruction Releases
    8 Heading 050 unless otherwise coordinated with TRACON Release Required
    12 Right turn to 200 unless otherwise coordinated with TRACON Automatic Release
    26 Heading 180 clockwise to 290 as close to on course as possible Automatic Release
    30 Heading 180 clockwise to 290 as close to on course as possible Automatic Release
    Flight Following

    Ensure VFR aircraft receiving flight following are transferred to MDT ATCT/TRACON in a timely manner.

    Over-flights

    Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary.

    Note: The Susquehanna River is an excellent local landmark to help overflights navigate through the airspace. Additionally, it can be used to help deconflict local traffic with MDT.

    Pattern Work

    Use the following as a guide for pilots wanting to perform pattern work at CXY.

    Runway Direction
    8 Left
    12 Right
    26 Right
    30 Left
    Note: All props should be at 1,500’ and jets at 2,000’. Adjust these altitudes when necessary to avoid over-flights or normal IFR traffic flow.

    TRACON

    TRACON services for Capital City Airport are provided by MDT TRACON.

    Appendix

    Changelog

    Change   Date Published   Description
    CHG1 25 Jun 2021 Initial release.
    CHG2 26 Aug 2024 Updated GRAMO VINNY EMI routing to J48.
    CHG3 9 Nov 2024 Converted to new WIki format.
    Retrieved from "https://wiki-dev.nyartcc.org/index.php?title=CXY_SOP&oldid=1284"