LOA/PHL N90

Letter of Agreement

Philadelphia TRACON (PHL) & New York TRACON (N90)

Rev. 1 - 1 Jan 2011

Purpose

This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Philadelphia TRACON (PHL) and New York TRACON (N90).

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.

---

PHL TRACON Departure Procedures

Table 1 - Departures from PHL to N90

From	To	Route	Altitude / Restriction
PHL Area	LGA	RBV V123 PROUD	8,000' / None
	EWR	V123 RBV	7,000' / Jets & Turboprops
		ARD V214 METRO	5,000' / Pistons
	EWR Satellites	JAIKE# Arrival	Leaving 9,000' for 7,000' / Jets
		V3	Leaving 9,000' for 7,000' / Turboprops
	N51 / SMQ / 47N / 39N	V3 SBJ	4,000' / None

• Departures from PHL TRACON to N90 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.
  • IFR traffic to JFK Area airports at or below 8,000' will be handed off to the Center or TRACON controller that provides service to the sectors listed below, in that order:
    • WRI Approach
    • N90 CAMRN sector
  • IFR traffic to JFK Area airports above 8,000' will be handed off to the Center or TRACON controller that provides service to the sectors listed below, in that order:
    • New York Center
    • N90 CAMRN sector
  • IFR traffic to LGA Area airports at or below 8,000' will be handed off to the Center or TRACON controller that provides service to the sectors listed below, in that order:
    • WRI Approach
    • N90 EMPYR sector
  • IFR traffic to LGA Area airports above 8,000' will be handed off to the Center or TRACON controller that provides service to the sectors listed below, in that order:
    • New York Center
    • N90 EMPYR sector
  • IFR traffic to EWR Area airports at or below 4,000' will be handed off to the Center or TRACON controller that provides service to N90 Approach METRO sector
  • IFR traffic to EWR Area airports above 4,000' will be handed off to the Center or TRACON controller that provides service to N90 Yardley sector

N90 TRACON Departure Procedures

Table 2 - Departures from N90 to PHL

From	To	Route	Altitude / Restriction
EWR / LGA	PHL N Area	SBJ ARD	4,000' / None
	PHL N & S Area	SLONE HAYER	4,000' / RNAV Helicopters

• Departures from N90 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.

PHL TRACON Arrival Procedures

• PHL TRACON Control Authority
  • Transfer of control on all aircraft shall be at least 2.5 miles from the PHL/N90 common boundary.
• Coordination
  • Regardless of which facility requests an altitude or route change, which will affect additional sectors in the adjacent facility's area, each facility shall be responsible to complete all necessary internal coordination, e.g., the PHL controller shall be responsible for coordination with all appropriate PHL sectors.
• 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.

N90 TRACON Arrival Procedures

• N90 TRACON Control Authority
  • Transfer of control on all aircraft shall be at least 2.5 miles from the PHL/N90 common boundary.
• Coordination
  • Regardless of which facility requests an altitude or route change, which will affect additional sectors in the adjacent facility's area, each facility shall be responsible to complete all necessary internal coordination, e.g., the N90 controller shall be responsible for coordination with all appropriate N90 sectors.
• 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.