Extract:LOAs-RDG

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]