LOA/PHL DOV: Difference between revisions

From New York ARTCC
(finish conversion, add images)
m ([email protected] moved page Draft:LOA/PHL DOV to LOA/PHL DOV without leaving a redirect: Publishing Draft to Main)
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
}}
}}


; Departure Procedures
=== Departure Procedures ===


** Departures from PHL TRACON to DOV RAPCON
==== Departures from PHL TRACON to DOV RAPCON ====
*** All aircraft shall be cleared to the destination airport via the routes and altitudes described in this LOA. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
* All aircraft shall be cleared to the destination airport via the routes and altitudes described in this LOA. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
*** DOV arrivals and overflights (see '''Attachment 1''' for more details) shall be routed via one of the following routes at 6,000' (overflights) or 4,000' (DOV arrivals):
* DOV arrivals and overflights (see '''Attachment 1''' for more details) shall be routed via one of the following routes at 6,000' (overflights) or 4,000' (DOV arrivals):
**** OOD V157
** OOD V157
**** DQO V29
** DQO V29
**** Direct ENO
** Direct ENO
*** BWI or DCA arrivals shall be routed via one of the following routes at 6,000' or 4,000':
* BWI or DCA arrivals shall be routed via one of the following routes at 6,000' or 4,000':
**** ENO V268 BAL (BWI)
** ENO V268 BAL (BWI)
**** ENO V16 CHOPS V308 OTT (DCA)
** ENO V16 CHOPS V308 OTT (DCA)
** Departures from DOV RAPCON to PHL TRACON
*** All aircraft shall be cleared to the destination airport via the routes and altitudes described in '''Attachment 1 - Table 1'''. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
*** DOV shall be responsible for correct routing on aircraft flying northbound that will enter the ZNY structure (9,000' and above).


; Arrival Procedures
==== Departures from DOV RAPCON to PHL TRACON ====
* All aircraft shall be cleared to the destination airport via the routes and altitudes described in '''Attachment 1 - Table 1'''. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
* DOV shall be responsible for correct routing on aircraft flying northbound that will enter the ZNY structure (9,000' and above).


** Control Authority
=== Arrival Procedures ===
*** Transfer of control on all aircraft shall be accomplished no later than the PHL/DOV common boundary.
*** Completion of radar handoff and transfer of communications constitutes authorization to:
**** For PHL TRACON: Turn aircraft up to thirty degrees and descend to 4,000'.
**** For DOV RAPCON: To turn aircraft up to thirty degrees.
**** Change of beacon code if the beacon code differs from that of the receiving facility.
** 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.
*** The receiving controller shall be responsible for obtaining all pertinent information.
*** Beacon codes need not be changed.
** BLARE Area
*** The BLARE Area depicted in '''Attachment 2''' is delegated to DOV at and between 4,000' and 6,000'. If needed by PHL, it may be recalled by agreement of the Controller-In-Charge.


<showhide title="Attachment 1 – Route Depiction, Area of Jurisdiction, and Procedures Chart">
==== Control Authority ====
* Transfer of control on all aircraft shall be accomplished no later than the PHL/DOV common boundary.
* Completion of radar handoff and transfer of communications constitutes authorization to:
** For PHL TRACON: Turn aircraft up to thirty degrees and descend to 4,000'.
** For DOV RAPCON: To turn aircraft up to thirty degrees.
** Change of beacon code if the beacon code differs from that of the receiving facility.
 
==== 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.
* The receiving controller shall be responsible for obtaining all pertinent information.
* Beacon codes need not be changed.
 
=== BLARE Area ===
* The BLARE Area depicted in '''Attachment 2''' is delegated to DOV at and between 4,000' and 6,000'. If needed by PHL, it may be recalled by agreement of the Controller-In-Charge.
 
=== Attachment 1 - Route Depiction, Area of Jurisdiction, and Procedures Chart ===
 
<showhide title="Route Depiction, Area of Jurisdiction, and Procedures Chart">
{{Layout-PullLeft|[[Image:Airspace-PHL-DOV-Routes.png|600px]]}}
{| class="table table-sop"
{| class="table table-sop"
|+ '''Table 1 - Departures from DOV to PHL'''
|+ '''Table 1 - Departures from DOV to PHL'''
Line 72: Line 79:
| 5,000'
| 5,000'
|}
|}
[[Image:Airspace-PHL-DOV-Routes.png|500px]]
{{Layout-Clearfix}}
</showhide>
</showhide>


<showhide title="Attachment 2 – BLARE Area Chart">
=== Attachment 2 – BLARE Area Chart ===
[[Image:Airspace-PHL-DOV-BLARE-Area.png|500px]]


[[Image:Airspace-PHL-DOV-BLARE-Area-RW.png|500px]]
<showhide title="BLARE Area Chart">
<div style="display:flex;">
[[Image:Airspace-PHL-DOV-BLARE-Area.png|600px]]
 
[[Image:Airspace-PHL-DOV-BLARE-Area-RW.png|600px]]
</div>
</showhide>
</showhide>


<showhide title="Attachment 3 – Satellite Airports">
=== Attachment 3 – Satellite Airports ===
 
<showhide title="Satellite Airports">
{{Extract:PHL-Satellites}}
{{Extract:PHL-Satellites}}
</showhide>
</showhide>

Latest revision as of 17:40, 2 July 2025

Letter of Agreement
Philadelphia TRACON (PHL) & Dover RAPCON (DOV)
Rev. 1 - 23 Apr 2015
Purpose
This agreement prescribes transfer of control procedures, radar handoff procedures, route/altitude assignments, and delegation of airspace between Philadelphia TRACON (PHL) and Dover RAPCON (DOV).
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.

Departure Procedures

Departures from PHL TRACON to DOV RAPCON

  • All aircraft shall be cleared to the destination airport via the routes and altitudes described in this LOA. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
  • DOV arrivals and overflights (see Attachment 1 for more details) shall be routed via one of the following routes at 6,000' (overflights) or 4,000' (DOV arrivals):
    • OOD V157
    • DQO V29
    • Direct ENO
  • BWI or DCA arrivals shall be routed via one of the following routes at 6,000' or 4,000':
    • ENO V268 BAL (BWI)
    • ENO V16 CHOPS V308 OTT (DCA)

Departures from DOV RAPCON to PHL TRACON

  • All aircraft shall be cleared to the destination airport via the routes and altitudes described in Attachment 1 - Table 1. Routes and altitudes other than those depicted in this LOA shall be on an APREQ basis.
  • DOV shall be responsible for correct routing on aircraft flying northbound that will enter the ZNY structure (9,000' and above).

Arrival Procedures

Control Authority

  • Transfer of control on all aircraft shall be accomplished no later than the PHL/DOV common boundary.
  • Completion of radar handoff and transfer of communications constitutes authorization to:
    • For PHL TRACON: Turn aircraft up to thirty degrees and descend to 4,000'.
    • For DOV RAPCON: To turn aircraft up to thirty degrees.
    • Change of beacon code if the beacon code differs from that of the receiving facility.

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.
  • The receiving controller shall be responsible for obtaining all pertinent information.
  • Beacon codes need not be changed.

BLARE Area

  • The BLARE Area depicted in Attachment 2 is delegated to DOV at and between 4,000' and 6,000'. If needed by PHL, it may be recalled by agreement of the Controller-In-Charge.

Attachment 1 - Route Depiction, Area of Jurisdiction, and Procedures Chart

Route Depiction, Area of Jurisdiction, and Procedures Chart [Show]

Table 1 - Departures from DOV to PHL
From Types Route Altitude Restriction
DOV and Satellites Departures Requesting >FL180 MXE J110 7,000'
PHL Arrivals Direct DQO 7,000'
PHL Satellites and Overflights ENO V29 DQO or Direct DQO 5,000' or 3,000'
Landing EVY Direct 3,000'
All Direct ENO 3,000'
EWR Satellites V29 MXE V3 SBJ 5,000'

Attachment 2 – BLARE Area Chart

BLARE Area Chart [Show]

Attachment 3 – Satellite Airports

Satellite Airports [Show]
Area Abbreviation Satellite Airport Codes
Philadelphia Area North PHLN CKZ, DYL, LOM, PNE, PTW, TTN, UKT, N10, N47, 3NJ6, 9N1
Philadelphia Area South PHLS EVY, ILG, MQS, OQN, N57, NJ74, 17N, 58M, 7N7
ARD Area 3NJ6, CKZ, DYL, UKT, PNE, TTN
PTW/DQO Area OQN, 7N7, 58M, PTW, MQS, N10, ILG, N47, N57, LOM, EVY