CXY SOP

New York ARTCC

Standard Operating Procedure — Capital City ATCT

Rev. 3 — Revised: 2026-06-24

Area at a glance

ICAO Code	Airport Name	Airspace
KCXY	Capital City Airport	D

Purpose

This document prescribes the procedures to be utilized for providing air traffic control services at Capital City Air 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

CXY ATCTMDT TRACON

Position	Callsign	Radio Name	Frequency	Identifier
Ground	CXY_GND	Capital City Ground	121.900
Tower	CXY_TWR	Capital City Tower	119.500	1X
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

Valid ExitsDeparture FrequencyLOA RoutesIFR DeparturesVFR Departures

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.

• Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.

Position	Frequency	Code
MDT_SW_APP	124.100	1H
NY_CTR	125.325	C56

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.

If there is no other controller online that would accept departures from CXY, use UNICOM frequency (122.8).

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 Preferred Route Database. Therefore, PRD must be referenced for all departures.

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

1. Traffic filed via EMI to join J48 should be re-routed via GRAMO VINNY EMI.

Capital City is a Class Delta airport. All VFR traffic must establish two-way radio communications. See the VFR Operations document for detailed explanation of applicable VFR procedures.

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:

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.

Runway Ownership and Crossings

1. 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.
2. Transfer of runway ownership, between Ground Control and Local Control, shall be accomplished verbally (or textually).
3. Ground Control is authorized to cross all active runways with coordination with Local Control.

Intersection Departures and Usable Runway Lengths

1. 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.
2. 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.

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

1. As the taxiway system is simple, there are no pre-defined routings.
2. 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.
3. 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.

Tower

Tower ProceduresRunway SelectionDeparture Heading (IFR)LAHSOMissed ApproachVFR 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. When wake turbulence is a factor, use timed separation in accordance with FAA Order JO 7110.65 para 3-9-6.

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.

Aircraft Exiting the Runway

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.

Runway Selection

Wind Speed	Direction	Configuration
		Depart	Land
0-4	Any	26, 30	26, 30
> 4	350-170	8, 12	8, 12
	171-349	26, 30	26, 30

Notes

1. Normal runway usage configurations are:
   1. West Operations: Runways 26 and 30.
   2. East Operations: Runways 8 and 12.
2. Runway 12/30 is only ~3700' feet long. Larger aircraft may have to use runway 8/26.
3. If visibility is less than 1 3/4 SM, runway 8 MUST be used as it is the only runway with an ILS Approach.
4. If visibility is less than 3/4 SM, no instrument approaches are available. Aircraft CANNOT land at CXY.
5. 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.

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

PHRASEOLOGY
Fly heading (heading), wind (wind), runway (runway), cleared for takeoff.

Runway	Heading
8	050
12	200
26	Runway Heading
30	290

Landing Runway	Hold Short Runway	Available Landing Distance
26	12 / 30	3,450'

Land and Hold Short Operations

1. Land and Hold Short Operations (LAHSO) may only be conducted for the runway 26, as specified in the table to the right.
2. LAHSO is only authorized when there exists at least 3 miles of visibility and 1,000' ceiling, and no wind shear has been reported.

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

1. 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.
2. 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 para 7-4-3. Use best judgement to determine whether to keep the aircraft in the pattern or not.
3. 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

1. 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.
2. 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.
3. Coordinate with TRACON as soon as possible and hand off when Local Control traffic is not a factor.
4. 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 towers class D 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

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

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.

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.