LOA/PHL MDT RDG

Purpose

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

Scope

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

Table 1 - Departures from PHL to MDT/RDG

From	Types	Route	Altitude Restriction
PHL & Satellites (To MDT)	All	MXE V184 MXE V184 V469 DQO V469	4,000', 6,000' or 8,000'
		MXE295 LRP138	4,000'
		PTW V12 BOYER; MDT has control for right turns only	6,000' or 8,000'
		MXE V170 BOYER	6,000'
		DQO DQO319 LRP144	4,000'
	Overflights	MXE V474	4,000', 6,000' or 8,000'
PHL & Satellites (To RDG/LNS)	All RDG	Direct SHAPP RDG BUNTS V210 MXE334 HUMEL MXE334 HUMEL PTW PTW275 RDG LOC	4,000'
	All LNS	Direct LRP BUNTS V210 LRP PTW V143 LRP
	Overflights	BUNTS V210 V170 RAV MXE V170 RAV PTW V12 HAR PTW V12 V170 RAV

Table 2 - Departures from MDT/RDG to PHL

From	Types	Route	Altitude Restriction
MDT & Satellites	MXE Area Jets	V474 PADRE (RDV) V184 PADRE (RDV) LRP144 PADRE (RDV)	7,000'
	MXE Area Props		5,000'
	DQO Area Jets	V469 DQO LRP144 PADRE DQO	7,000'
	DQO Area Props		5,000'
	DOV Area Jets	V469 DQO V29 LRP144 PADRE DQO V29	7,000'
	DOV Area Props		5,000'
	ACY Area Jets V469	DQO OOD VCN LRP144 PADRE DQO OOD VCN	7,000'
	ACY Area Props		5,000'
RDG & Satellites	PHL, PTW Area, ARD Area, Overflights to WRI	V210 BUNTS or Direct BUNTS	5,000' (≥ 180 knots) 3,000' (< 180 knots)
	MXE Area, DQO Area, Overflights	TRAGG MXE V170 MXE	5,000' (PHL East Ops) 3,000' (PHL West Ops)

PHL TRACON Departure Procedures

• Departures from PHL TRACON to MDT/RDG TRACON
  • All aircraft shall be cleared to the destination airport via the routes and altitudes described in Table 1. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
    • PHL TRACON (radar position) may, without coordination, clear traffic landing MDT or CXY direct to the airport at 6,000' or clear overflight traffic routed via HAR VOR, direct HAR at 6,000'.

MDT/RDG TRACON Departure Procedures

• Departures from MDT/RDG TRACON to PHL TRACON
  • All aircraft shall be cleared to the destination airport via the routes and altitudes described in Table 2. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
    • “MXE Area” airports are defined as 40N, N99, and N57.
    • “DQO Area” airports are defined as 2N0, N01, 7N7, 27N, ILG, 17N, NJ74, ILG, EVY, 7N7, and 58M.
    • “PTW/ARD Area” airports are defined as 3NJ6, N54, N62, N75, 9N1, N10, PTW, N47, LOM, UKT, N70, DYL, NXX, PNE, and TTN.

PHL TRACON Arrival Procedures

• PHL TRACON Control Authority
  • Transfer of control on all aircraft shall be accomplished no later than the PHL/MDT or PHL/RDG common boundary.
  • Completion of radar handoff and transfer of communications constitutes authorization for descent and to turn aircraft up to thirty (30) degrees.
• Coordination
  • PHL TRACON shall advise MDT/RDG TRACON as to the direction of the runway operation at PHL.
• Traffic Management Restrictions
  • When either facility requires a restriction affecting more than one aircraft, coordinate any traffic management initiatives with Controller-In-Charge.
• VFR Procedures
  • Automated VFR handoffs are optional between facilities. No verbal coordination is required.
  • It is suggested that MSAW alerts (vSTARS) be inhibited on targets.
  • The receiving controller shall be responsible for obtaining all pertinent information.
  • Beacon codes need not be changed.

MDT/RDG TRACON Arrival Procedures

• MDT/RDG TRACON Control Authority
  • Transfer of control on all aircraft shall be accomplished no later than the PHL/MDT or PHL/RDG common boundary.
  • Completion of radar handoff and transfer of communications constitutes authorization for descent and to turn aircraft up to thirty (30) degrees.
• Coordination
  • RDG TRACON is not staffed; MDT shall provide the services assigned to RDG in the current PHL/RDG LOA.
• Traffic Management Restrictions
  • When either facility requires a restriction affecting more than one aircraft, coordinate any traffic management initiatives with Controller-In-Charge.
• VFR Procedures
  • Automated VFR handoffs are optional between facilities. No verbal coordination is required.
  • It is suggested that MSAW alerts be inhibited on targets.
  • The receiving controller shall be responsible for obtaining all pertinent information.
  • Beacon codes need not be changed.