ZDC LOA: Difference between revisions
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
|ZTL | |ZTL | ||
|Washington ARTCC | |Washington ARTCC | ||
| | |1 February 2024 | ||
|} | |} | ||
'''Scope:''' | |||
This agreement is made by and between Jacksonville ARTCC (herein ZJX) and Washington ARTCC (herein ZDC) of the United States Division of the Virtual Air Traffic Simulation Network (herein VATSIM). | |||
'''Purpose:''' | '''Purpose:''' | ||
This agreement | This agreement is made by and between Jacksonville ARTCC (herein ZJX) and Washington ARTCC (herein ZDC) of the United States Division of the Virtual Air Traffic Simulation Network (herein VATSIM). | ||
''' | '''Cancellation:''' This LOA cancels any pre-existing LOA between ZJX and ZDC. This LOA shall become the agreement in use on the effective date. | ||
== [[General Responsibilities]] == | == [[General Responsibilities]] == |
Revision as of 17:53, 17 January 2024
ARTCC Information
ARTCC Code | ARTCC Name | Effective Date |
---|---|---|
ZTL | Washington ARTCC | 1 February 2024 |
Scope: This agreement is made by and between Jacksonville ARTCC (herein ZJX) and Washington ARTCC (herein ZDC) of the United States Division of the Virtual Air Traffic Simulation Network (herein VATSIM).
Purpose: This agreement is made by and between Jacksonville ARTCC (herein ZJX) and Washington ARTCC (herein ZDC) of the United States Division of the Virtual Air Traffic Simulation Network (herein VATSIM).
Cancellation: This LOA cancels any pre-existing LOA between ZJX and ZDC. This LOA shall become the agreement in use on the effective date.
General Responsibilities
ZJX delegates to ZDC the responsibility for ATC service as depicted.
Both ARTCCs should make all efforts to ensure adequate or better (10-15 MIT) sequencing and separation prior to any and all handoffs.
Both ARTCCs should make all efforts to ensure that handoffs occur at least 10 nm from the agreed border. Handoff requests may be initiated up to 50 nm without prior coordination.
Both ARTCCs shall announce details of internal delegation (splitting) upon sign-on where both ARTCCs are online.
General Procedures
The receiving ARTCC has control for beacon code changes.
Each ARTCC shall route/restrict aircraft in accordance with Attachment C, additionally:
-With regards to aircraft landing within 60 miles of the boundary shall enter the receiving ARTCC’s airspace AOB FL230, and the receiving ARTCC shall have control for descent and turns.
ZJX may clear aircraft direct ILM without prior approval.
ZDC may clear aircraft direct CRE, FLO without prior approval.<br,
Standard Routing
Departure Airport | Arrival Airport | Routing (Segment) | Conditions |
---|---|---|---|
ALL | MCO | North Ops: ... LPERD SNFLD# South Ops: .... LPERD GTOUT# |
JET |
ALL | CHS | BLAMO AMYLU# | JET |
ALL | JAX | CHS ESENT LUNNI# | JET |
Departure Airport | Arrival Airport | Routing (Segment) | Conditions |
---|---|---|---|
ALL | MCO | North Ops: ... LPERD SNFLD# South Ops: .... LPERD GTOUT# |
JET |
ALL | DCA | DWYTE J165 NKKIE WAVES CAPSS# | JET |
ALL | DCA | CHS J79 SBY LAFLN DEALE# | JET OVFLW/ALTN*** |
ALL | DCA | CHS V437 FLO V157 FAY RIC IRONS# | NON-RNAV |
ALL | IAD | J207 RDU BZNGA DORRN CAVLR# | JET |
ALL | IAD | J207 RDU DORRN WIGOL# | JET OVFLW/ALTRN*** |
ALL | IAD | J207 RDU FAK COATT# | NON-RNAV |
ALL | BWI | J79 TYI THHMP RAVNN# | JET |
ALL | BWI | CHS J79 SBY LAFLN MIIDY# | JET OVFLW/ALTRN |
- In high volume traffic scenarios, ZJX TMU or ZDC TMU may request additional routing requirements.
- These routes should only be used when requested by ZJX TMU or ZDC TMU or their designee.
Standard Altitude Restrictions
Arrival Airport/Area | Altitude Restriction | Note |
---|---|---|
RDU | BOUNDARY AOB FL210 | JURDI/TENNI FL210 |
FAY | BOUNDARY AOB 15k, FOR 11k | H/O TO FAY ATCT |
ILM | BOUNDARY AOB 15k, FOR 11k | H/O TO ILM ATCT |
Arrival Airport/Area | Altitude Restriction | Note |
---|---|---|
CAE | BOUNDARY AOB FL220 | N/A |
MYR | BOUNDARY AOB 11k | H/O TO MYR ATCT, AUTO P/O APPVED |
FLO | BOUNDARY AOB 5k | H/O TO FLO ATCT, AUTO P/O APPVED |