LOA/PHL PNE: Difference between revisions

From New York ARTCC
m (Style Standards)
m ([email protected] moved page Draft:LOA/PHL PNE to LOA/PHL PNE without leaving a redirect: Publishing Draft to Main)
 
(No difference)

Latest revision as of 00:28, 8 July 2025

Letter of Agreement
Philadelphia TRACON (PHL) & Northeast Philadelphia Tower (PNE)
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 PNE.
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.

Northeast Philadelphia Departure Procedures

  • Northeast Philadelphia Tower shall instruct IFR departures to fly runway heading, maintain 2,000 feet, and expect (filed altitude) ten minutes after departure. Runway 1 IFR departures shall be assigned heading 330 degrees.
  • Philadelphia TRACON shall not turn an IFR departure below 2,000 feet unless prior coordination with Northeast Philadelphia tower is effected.

Northeast Philadelphia Arrival Procedures

Philadelphia TRACON shall:

  • Inform Northeast Philadelphia Tower of the first and last aircraft for each runway whenever a change of traffic flow is agreed upon.
  • Coordinate any approach other than that advertised in the ATIS by using scratchpad entries from Table 1.
NOTE: Use “VAP” in the scratchpad to indicate that an arrival is following traffic to the active runway.
  • Verbally (or textually) obtain approval for use of a runway not designated as active for arrivals. Coordinate each arrival that will approach from a nonstandard transfer point or will land on a non-standard arrival runway. Approval for these approaches may be granted for an individual aircraft, a series of aircraft, or for a specified time frame.
  • Ensure transfer of communications to tower NO later than the following points:
    • Instrument Approaches: The Final Approach Fix.
    • Visual Approaches: 5 miles from the airport.
  • Assume responsibility for separation of consecutive radar arrivals on the same final approach course until 3 NM from the runway threshold. When the weather is less than 1,500’ ceiling and 5 miles visibility, the radar controller shall assume responsibility to the runway threshold.
Table 1 - Scratchpad entries for PNE Approaches
Approach 6 15 24 33
ILS I24
Visual 06 15 24 33
RNAV GPS G06 G15 G24 G33

Northeast Philadelphia Tower shall:

  • Ensure that affected TRACON controllers are aware of the current ATIS code, runways in use, and approach information either by verbal (or textual) or automated coordination.
  • Verbally (or textually) advise of special changes in the airport configuration or weather.
  • Advise the departure controller as soon as practical of any missed approaches and go-arounds. When a missed approach or go-around will be re-sequenced by TRACON, stop departures and coordinate release of successive departures.
  • Assume responsibility for consecutive radar arrivals on the same final approach course within 3 NM of the landing threshold. At any time the tower cannot provide visual separation, advise the TRACON and the radar controller shall assume separation responsibility.
  • Request approval of all SVFR operations and shall advise when SVFR operations are completed. Northeast Philadelphia Tower is authorized to conduct SVFR operations at or below 1,500' MSL.