RDG SOP

New York ARTCC

Standard Operating Procedure — Reading ATCT and MDT TRACON RDG Area

Rev. 3 — Revised: 2026-06-24

Area at a glance

ICAO Code	Airport Name	Airspace
KRDG	Reading Rgnl/Carl A Spaatz Field	D

Purpose

This document prescribes the procedures to be utilized for providing air traffic control services at Reading Air Traffic Control Tower (ATCT) and any of the positions within the Reading Terminal Radar Approach Control (TRACON) and the airports it serves. 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

RDG ATCTMDT TRACON

Position	Callsign	Radio Name	Frequency	Identifier
Ground	RDG_GND	Reading Ground	121.950
Tower	RDG_TWR	Reading Tower	119.900	1G
ATIS	KRDG_ATIS		127.100

ATCT

Clearance Delivery

Valid ExitsDeparture FrequencyLOA RoutesIFR DeparturesVFR Departures

{

Note:

While strict exit direction points are not required at RDG, the guide above may come in handy for directing pilots to proper exits for departing the area.

Position	Frequency	Code
MDT_R_APP	125.150	1R
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 RDG Ground. 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 RDG, 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.

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 procedure out of Reading. All aircraft must be cleared to their destination via radar vectors to a RDG exit.

Reading 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	ETX, FJC, RAV
South	LRP, MXE, PTW

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 tree one at delta, taxi via bravo, delta. Runway tree one at delta intersection departure, tree thousand seven hundred and fifty feet takeoff distance available.

13	31	18	36
C (5,050')	J (5,400')	D (4,200')	A (4,900')
F (3,900')	18/36 (5,200')	G (2,600')	B (3,950')
D (2,500')	D (3,750')	E (2,250')	13/31 (3,050')
	F (2,350')		E (2,800')
	E (2,900')		G (2,450')

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 Reading are automatic unless the RDG TRACON requests individual releases.

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.

Radar

This tower uses a DBRITE radar only and is not certified for any approach control services. By agreement with Reading 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	13	13
> 4	040-219	13	13
	220-039	31	31

Notes

1. Runway 18/36 can be used if it is advantageous or if the winds are severe enough to warrant it's use. It can also be used if a pilot requests it.

Departure Heading (IFR) IFR aircraft must be given runway heading, unless otherwise coordinated with the departure controller.

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

Landing Runway	Hold Short Runway	Available landing distance
13	18/36	5,200'
18	13/31	3,050'

Land and Hold Short Operations

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

Missed Approach Procedures

1. Missed approaches or go-arounds shall be instructed to fly the published missed approach procedure prior to release to the TRACON frequency.
2. Missed approaches or go-arounds may, in lieu of the published missed approach procedure, be instructed to fly runway heading and be issued an altitude of 3,000' prior to release to the TRACON frequency.
3. 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. Use best judgement to determine whether to keep the aircraft in the pattern or not.

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 previous headings and altitudes if using them would compromise safety.

Airspace

1. Class DELTA.
2. The tower owns 3,000' and below within a 5 mile radius of the airport.

Departures

Aircraft should be given the most expeditious way out of the airspace, which should be away from the IFR flow.

Flight Following

All aircraft should remain on the tower frequency unless the route of flight will or may impede the operations of RDG 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

1. All aircraft wanting to perform pattern work at RDG, must be assigned left closed traffic.
2. All single engine props should be at 1,400', twins and jets at 1,900'. Adjust these altitudes when necessary to avoid over-flights or IFR traffic flow.

TRACON

General InformationAirspace DelegationVideo MapLetters of Agreement

Callsign

1. Whenever a controller handles a departure, they must use the radio name "Reading Departure" when referring to themselves on frequency.
2. Whenever a controller handles an arrival or enroute traffic, they must use the radio name "Reading Approach" when referring to themselves on frequency.
3. If talking to other controllers via land line, refer to yourself as the sector name for which you are controlling.

Coordination

Procedures contained in Letters of Agreement must apply at all times unless prior verbal (or textual) coordination between facilities has been affected otherwise.

Position Combining/Decombining

Coordinate prior to combining/decombining pertinent positions within facilities with any affected controllers.

Point Outs

When using an automated point out, verbal (or textual) approval must be obtained before an aircraft may enter another controller's airspace. An automated point out not accompanied by a verbal or textual description does NOT constitute a valid point out.

Separation Minima

Minimum radar separation between aircraft must be at least three miles (intra-TRACON) or five miles (TRACON-Center) constant or increasing when transfer of control is accomplished. Other factors such as wake turbulence separation and miles-in-trail requirements may increase this minimum.

Conflicting Flows

When the facilities for which the LOA pertains to must use conflicting traffic flows, they shall do so alternately, governed by traffic volume and delays at each airport or airspace.

Airports and LandmarksWaypoints and Airways

ABE/MDTMDTZNY

Letter of Agreement

Allentown TRACON (ABE), Harrisburg TRACON (MDT) & Reading TRACON (RDG)

Rev. 1 – April 7, 2020

Purpose

This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Allentown TRACON (ABE), Harrisburg TRACON (MDT) & Reading TRACON (RDG).

Scope

The procedures contained herein must apply unless prior coordination is effected.

Disclosure

vZNY and any other facilities mentioned in this document are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and must never be used for actual flight or air traffic control operations. vZNY and any other facility mentioned in this document are not affiliated with the FAA in any manner.

General Procedures

1. Transfer of Control Procedures:
   1. Transfer of control on all aircraft must be accomplished no later than the ABE/MDT or ABE/RDG common boundary.
   2. Completion of radar handoff and transfer of communications constitutes authorization for descents and to turn aircraft up to thirty (30) degrees within 10 miles of the ABE/MDT or ABE/RDG common boundary. RDG has additional control for turns not greater than 45 degrees for aircraft on V93 only.
   3. If a beacon code is not compatible on handoff, the receiving facility may change the beacon code when in contact with the aircraft, without coordination.
2. VFR Procedures:
   1. Automated VFR handoffs are optional between facilities. No verbal coordination is required.
   2. It is suggested to inhibit MSAW alerts (vSTARS client) on all targets.
   3. The receiving controller must be responsible for obtaining all pertinent information.
   4. Beacon codes do not need to be changed.
3. Coordination Procedures:
   1. Regardless of which facility requests an altitude or route change, which will affect additional sectors in the adjacent facility's area, each facility must be responsible to complete all necessary internal coordination, e.g., the ABE controller must be responsible for coordination with all appropriate ABE sectors.
4. Reading TRACON Operations Hours:
   1. During those periods when RDG is not in operation (0000-0600 local time), MDT must provide the services assigned to RDG in this LOA.

ABE TRACON to MDT/RDG TRACON

1. All aircraft from ABE TRACON to MDT/RDG TRACON must be cleared to the destination airport via the routes and altitudes described in Attachment 1. Routes and altitudes other than those depicted in this LOA must be on an APREQ basis.
2. Traffic from ABE airspace may be given direct RAV or SEG without coordination.
3. Traffic from ABE airspace with a destination airport within MDT or RDG TRACON may be given direct without coordination.

MDT/RDG TRACON to ABE TRACON

1. All aircraft from MDT/RDG TRACON to ABE TRACON must be cleared to the destination airport via the routes and altitudes described in Attachment 1. Routes and altitudes other than those depicted in this LOA must be on an APREQ basis.
2. Traffic from MDT/RDG airspace may be given direct ETX, FJC or STW without coordination.

       Attachment 1 — From ABE to MDT/RDG
       [Show]

From	To	Route Via	Altitude Restriction
ABE & ABE Sats	MDT & MDT Sats	V6 / V30 / V39 / V93/ V162 / V276	6,000' or 8,000'
	RDG	Radar Vectors	4,000'
		V93 DUMMR	4,000' or 6,000'; traffic handed off at 6,000' must be descended by RDG prior to adjacent airspace boundaries.
	RDG Overflights	V93	4,000' or 6,000'; traffic handed off at 6,000' must be descended by RDG prior to adjacent airspace boundaries.
		V30 / V39 / V162	4,000'
		Direct FLOAT or LRP	4,000'

       Attachment 1 — From MDT/RDG to ABE
       [Show]

From	To	Route Via	Altitude Restriction
MDT & MDT Sats	ABE & ABE Sats	V6 FJC or V39 ETX	7,000'
	Overflights	V6 / V30 / V39 / V93 / V162	7,000'
RDG	ABE & ABE Sats (except 1N7)	ETX	3,000' or 5,000'
	1N7	FJC STW	3,000' or 5,000'
	Overflights	Direct FJC or ETX / V93 / V93 SNOWY	5,000'

       Attachment 2 — Area Airport Listings
       [Show]

Area	Abbreviation	Satellite Airport Codes
Allentown Satellite	ABE Sats	XLL, N43, N53, 22N, 1N7, N40, N85, 69N, 7N8, 9N1
Harrisburg Satellite Airports	MDT Sats	CXY, LNS, MUI, THV, ZER, SEG, N68, N71, N76, N79, N94, 9D4

Letter of Agreement

Harrisburg TRACON (MDT) & Reading TRACON (RDG)

Rev. 1 – September 18, 2020

Purpose

This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Harrisburg TRACON (MDT) and Reading TRACON (RDG).

Scope

The procedures contained herein must apply unless prior coordination is effected.

Disclosure

vZNY and any other facilities mentioned in this document are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and must never be used for actual flight or air traffic control operations. vZNY and any other facility mentioned in this document are not affiliated with the FAA in any manner.

Procedures

1. General
   1. Aircraft must be cleared to the destination airport via routes and altitudes as described below.
   2. Radar hand-off and transfer of communication must be accomplished prior to aircraft entering the receiving facility's airspace.
   3. RDGT hours of operation are 0600-2400 local. MDTT provides services for RDGT's airspace at all other times.
   4. RDGT has the responsibility to make all the necessary notifications regarding the transfer of airspace.
2. Reading Traffic
   1. MDTT must descend traffic to 5000, within RDGT's airspace, after acceptance of a hand-off by RDGT. Reading arrivals may be level at 3000.
   2. Reading arrivals must be routed direct or on a heading to RDG, OUTLT, or HUMEL.
   3. RDGT has control of Reading arrivals for descent and turns of 45 degrees or less.
   4. Aircraft routed over ETX, FJC, STW or BUNTS may be given direct ETX, FJC, STW or BUNTS respectively without prior coordination.
3. Harrisburg Traffic
   1. MDTT has control of departures from RDGT for climb to requested altitude upon transfer of communications.
   2. Aircraft from RDGT must be routed direct SEG, RAV, HWANG, LRP or on a heading to join V12, V499, or V162 east of HWANG. If HAR is in the route of flight and the final altitude is at or below 8000 feet, RDGT may assign aircraft departing from the Reading Airport direct HAR.
   3. MDTT has control of MUIR arrivals for descent and turns up to 45 degrees upon transfer of communications.
4. Lancaster Airport Traffic
   1. MDTT has control of Lancaster (LNS) arrivals for descent and turns up to 45 degrees upon transfer of communications.
   2. MDTT is responsible for all releases at LNS.
   3. MDT must hand off all LNS departures on a heading to the assigned airway/fix prior to the transfer of communications. Departures need not be level at 5000 feet prior to the airspace boundary.
   4. MDTT may approve a departure from RWY 08 or RWY 13 released directly to RDGT.
      1. LNS Tower must coordinate the release from RDGT.
      2. LNS Tower must assign the departure an initial altitude of 3000, routing into RDGT's airspace, and RDGT's departure frequency.
   5. RDGT must coordinate with MDTT and provide advance information to LNS Tower before clearing an aircraft for an approach to RWY 26.
   6. RDG departures destined for LNS that will be handed off to MDTT must be at 4000, unless coordinated otherwise.
   7. All aircraft pointed-out to RDGT must remain clear of a 5NM radius of RDG airport unless specifically coordinated.

       Attachment 1 — Route Description and Procedure — From RDG Area
       [Show]

Destination	Route	Frequency*	Altitude
MDT/CXY	V12	126.45	40
MDT/CXY	V162	118.25	40
LNS	LRP/LNS	126.45	40
OVERFLIGHT	V30, V162, V170, V276	118.25	40
OVERFLIGHT	V12, V39, V93, V143, V210, V457, V499, T295	126.45	40

∗ This is the normal configuration for a 3 sector operation. For all aircraft, the frequency when on a 2 sector operation is 126.45 (LRP) and for 1 sector operation 124.1 (HAR).

Note: MDTT owns 030-SFC and 060-080 in area "A"

       Attachment 2 — Route Description and Procedure — From HAR Area
       [Show]

Destination	Route	Frequency	Altitude
MDT/CXY	V12	126.45	40
RDG	Direct or on a heading to RDG, OUTLT, or HUMEL	125.15	30/50
OVERFLIGHT	All routes except V12/V143	125.15	50

Note: MDTT owns 030-SFC and 060-080 in area "A"

Letter of Agreement

Reading TRACON (RDG) & New York ARTCC (ZNY)

Rev. 1 – September 18, 2020

Purpose

This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Reading TRACON (RDG) and New York ARTCC (ZNY).

Scope

The procedures contained herein must apply unless prior coordination is effected.

Disclosure

vZNY and any other facilities mentioned in this document are affiliated with the Virtual Air Traffic Simulation (VATSIM) network. The procedures outlined in this document are intended exclusively for use in the VATSIM flight simulation environment and must never be used for actual flight or air traffic control operations. vZNY and any other facility mentioned in this document are not affiliated with the FAA in any manner.

Delegation of Authority

New York Center delegates to Reading Tower authority and responsibility for control of IFR arrival, departure and tower enroute aircraft in controlled airspace within the Approach Control area depicted herein.

Procedures

1. Departure aircraft requesting routes north of the Reading Airport must be cleared by the N92 controller. All other departure aircraft must be cleared by the N26 controller.
2. The Center shall advise Tower when departure clearances will be on approval basis only. The implementation of the Severe Weather Avoidance Plan (SWAP) automatically cancels silent clearances.

       Attachment 1 — Reading Tower Approach Control Area
       [Show]