| 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 |
(→Tower) |
m (Style standards + missing Missed procedures) |
||
| Line 180: | Line 180: | ||
|-|LOA Routes= | |-|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 | Routing to certain airports in ZNY, ZDC and ZBW ARTCCs is pre-coordinated through [[LOA|letters of agreement (LOA)]]. These routes have been added to the [[PRD|Preferred Route Database (PRD)]]. | ||
| Line 259: | Line 259: | ||
|-|Runway Selection= | |-|Runway Selection= | ||
=====Runway Selection===== | ===== Runway Selection ===== | ||
{| class="table table-sop" | {| class="table table-sop" | ||
| Line 290: | Line 290: | ||
|-|Departure Heading (IFR)= | |-|Departure Heading (IFR)= | ||
===== Departure Heading (IFR) ===== | |||
Assign IFR aircraft a heading listed in the table below, unless otherwise coordinated with the departure controller. | Assign IFR aircraft a heading listed in the table below, unless otherwise coordinated with the departure controller. | ||
| Line 308: | Line 311: | ||
|} | |} | ||
|-|LAHSO= | |-|LAHSO= | ||
===== Land and Hold Short Operations ===== | |||
# Land and Hold Short Operations (LAHSO) may only be conducted for runway 26: | # Land and Hold Short Operations (LAHSO) may only be conducted for runway 26: | ||
## Hold short runway 12 / 30, Available Landing Distance 3450' | ## Hold short runway 12 / 30, Available Landing Distance 3450' | ||
| Line 316: | Line 321: | ||
|-|Missed Approach= | |-|Missed Approach= | ||
===== Missed Approach Procedures ===== | |||
<div style="float:right; width:40%; margin-left:1em;"> | <div style="float:right; width:40%; margin-left:1em;"> | ||
| Line 346: | Line 350: | ||
</div> | </div> | ||
# 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 {{Reference7110|chapter=7|section=4|reference=7-4-3}}. 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''' | ||
| Line 356: | Line 365: | ||
|-|VFR Procedures= | |-|VFR Procedures= | ||
=====Airspace===== | ===== Airspace ===== | ||
[[File:Airspace-MDT-WEST-ATCT.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in a '''West Flow'''.]] | [[File:Airspace-MDT-WEST-ATCT.png|400px|thumb|right|Outline of the Harrisburg Tower airspace in a '''West Flow'''.]] | ||
| Line 369: | Line 377: | ||
## 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. | ## 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===== | ===== 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: | 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: | ||
| Line 393: | Line 401: | ||
|} | |} | ||
=====Flight Following===== | ===== Flight Following ===== | ||
Ensure VFR aircraft receiving flight following are transferred to MDT ATCT/TRACON in a timely manner. | Ensure VFR aircraft receiving flight following are transferred to MDT ATCT/TRACON in a timely manner. | ||
=====Over-flights===== | ===== Over-flights ===== | ||
Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary. | Allow overflight aircraft to cross over the numbers of the active runway. Make sure to give traffic advisories as necessary. | ||
| Line 425: | Line 433: | ||
</div> | </div> | ||
{{Layout-Clearfix}} | |||
''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. | ''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. | ||
| Line 430: | Line 439: | ||
== TRACON == | == TRACON == | ||
TRACON services for Capital City Airport are provided by MDT TRACON. | TRACON services for Capital City Airport are provided by [[MDT SOP|MDT TRACON]]. | ||
== Appendix == | == Appendix == | ||
Revision as of 02:07, 13 January 2026
Rev. 3 — Revised: 2026-01-13
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.
Operational Positions
| 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
- 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
GAAPP KIACK... - 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.
| Position | Frequency | Code |
|---|---|---|
| MDT_SW_APP | 124.100 | HK |
| NY_W_CTR | 132.175 | N34 |
| NY_CTR | 125.325 | N56 |
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 (PRD).
Initial Altitude
- 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 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. - 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.
- Aircraft that will climb into the overlying MDT Class Charlie airspace (above 2,500'): Assign 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 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 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 |
- Aircraft should be sequenced to depart in the following order:
- 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.
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
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
- Normal runway configurations are:
- West Operations: Runways 26 and 30.
- East Operations: Runways 8 and 12.
- If visibility is below 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.
Departure Heading (IFR)
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
- Land and Hold Short Operations (LAHSO) may only be conducted for runway 26:
- Hold short runway 12 / 30, Available Landing Distance 3450'
- 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 |
| **RNAV 26 approach: Assign published missed | ||
| 30 | 290 | 3,000 |
- 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 FAA Order JO 7110.65 § 7-4-3. 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
- 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.
- 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.
Airspace


- 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.
- 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).
- 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 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 |
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. |
