| Date
|
Revision
|
Items Revised
|
| 20 April 2023
|
A
|
Removal of DARBS# and LZARD#; MAATY crossing for TPA is 11,000. 280Kts if South. BANGZ# is BANGZ at 10,000.
|
| 7 September 2023
|
B
|
No Stacks to and From, ZJX/ZMA Control when other offline, Crossing Restrictions at Multiple Airfields
|
| 11 December 2023
|
C
|
F11 Departure DTA information updated.
|
| 26 February 2024
|
D
|
Additional restrictions for aircraft landing in ZJX and TPA border crossing over the gulf updated.
|
| ARTCC Code
|
ARTCC Name
|
Effective Date
|
| ZMA
|
Miami ARTCC
|
15 July 2020
|
Purpose:
This Letter of Agreement, establishes a set of agreed upon air traffic control procedures between ZJX and
ZMA. This LOA also defines the limitations and coordination expectations of both ZJX/ZMA facilities, and
is supplementary to the procedures in FAA Order 7110.65, VATSIM policies and procedures, ZJX/ZMA
ARTCC policies and procedures, and any other relevant governing document.
Distribution:
This agreement is made by and between Jacksonville ARTCC (herein ZJX) and Miami ARTCC (herein
ZMA) of the United States Division of the Virtual Air Traffic Simulation Network.
When tower services are being provided at KMCO, ZJX shall advise the relevant ZMA controller(s) of the runway configuration currently in use at KMCO. (1)
When tower services are being provided at KTPA, ZMA shall advise the relevant ZJX controller(s) of the runway configuration currently in use at KTPA. (2)
Note:
(1)Including any of TPA_TWR, TPA_APP, or MIA_CTR.
(2)Including any of MCO_TWR, MCO_APP, or JAX_CTR.
General
The below sections outline conditions under which one ARTCC may control aircraft within the other’s airspace while they are offline. The using controller may retain, or initiate, radar identification and/or communications with aircraft outside their airspace, but only as described below. If the “owning controller later connects to the network, the using controller must immediately relinquish control and communications with the aircraft to the owning controller, unless otherwise approved by the owning controller.
F11 Area Arrivals
If Miami Center (MIA_CTR) is offline, ZMA authorizes ZJX to use any Miami Center airspace reasonably deemed necessary to sequence and/or descend aircraft inbound to the F11 TRACON, not to exceed 100nm5
from the relevant airspace boundary.
TPA Area Arrivals
If Jacksonville Center (JAX_CTR) is offline, ZJX authorizes ZMA to use any Jacksonville Center airspace reasonably deemed necessary to sequence and/or descend aircraft inbound to the TPA TRACON, not to exceed 100nm from the relevant airspace boundary.
Other Inbound Aircraft
When one facility is offline, the other may initiate radar identification and/or communications with inbound aircraft in the other’s airspace, not to exceed 50nm prior to the relevant airspace boundary.
- Unless otherwise requested by ZMA, ZJX shall assign RNAV capable aircraft an appropriate RNAV SID, and shall be established on the SID before entering the ZMA airspace.
- Non-RNAV aircraft who are not able to fly an RNAV SID shall be vectored toward the Departure Transition Area (DTA) by F11 and transferred to ZMA on a heading. EXCEPTION: Departures via the ATLAS DTA when MLB VOR is in the flight plan shall be cleared to MLB VOR by F11 before transferring to ZMA.
- F11 departures via TPSTR/ATLAS/CUSSR shall be delivered to ZMA climbing to 14000 or lower and ZMA shall have control for climb on contact.
- The MLBSO West and MLBSO East DTAs may only be used for departing traffic from MLB COF COI TIX XMR TTS or X21.
- ZMA shall have control for turns, on contact, for all F11 departure traffic.
Aircraft on or east of Q77/V267 shall be cleared northbound at ODD altitudes and southbound at EVEN altitudes. Aircraft west of Q77/V267 shall be cleared northbound at EVEN altitudes and southbound at ODD altitudes.
When ZMA Sector 02 (HOBEE) is online, ZJX shall ensure all aircraft landing within ZMA are tucked below HOBEE, and into the relevant low sector. For aircraft routed via the OMN corridor (east coast), this will be AOB FL300, and via the west coast AOB FL310. Whenever ZMA activates HOBEE, the controller working HOBEE shall be signed in as MIA_02_CTR, and no other callsign.
Aircraft communications shall be transferred no later than the airspace boundary.
All handoffs and point outs shall be conducted through automated means, when available, unless otherwise coordinated.
Prior to initiation of a radar handoff, the transferring controller shall ensure the data block accurately reflects assigned altitude, routing, and all other relevant information, unless otherwise coordinated.
Aircraft of similar performance, on same or similar routings/trajectories, which land within ZJX/ZMA shall be provided 5 miles in trail per destination, constant or increasing, regardless of altitude (no stacks).
Both ZJX and ZMA shall comply with all posted TMIs, provided those TMIs are either implemented through established VATUSA Command Center (DCC) processes, or communicated directly between ZMA/ZJX
TMUs, coordinators, or controllers.
Transitioning aircraft shall not be permitted to operate an enhanced simulation rate greater than 1x across the mutual airspace boundary, unless prior coordination has been achieved.
ZJX and ZMA agree to ensure all aircraft are exchanged established on the routings and at the altitudes outlined in the tables below. Aircraft on nonstandard routings require prior coordination with the affected controller(s).
| Route
|
Type
|
Restriction
|
Note
|
| KNEED V152 OMN
|
JET, TP
|
AOB 11,000
|
TPA-F11 Traffic
|
| PISTON
|
AOB 50
|
| any
|
|
F11 BDRY @ 150
|
|
| Route
|
Type
|
Restriction
|
Note
|
| ALYNA#
|
JET
|
SURFR @ 140
|
|
| GOOFY#
|
JET,TP
|
BAIRN @ 110
|
MCO SOUTH OPS
|
| JET,TP
|
BAIRN @ 080
|
MCO NORTH OPS
|
| JET,TP
|
BAIRN @ 080
|
SATELLITES
|
| JOKRS#
|
JET
|
MOANS @ 130
|
NORTH OPS: 250KTS
|
| TP
|
MOANS @ 100
|
|
| PISTON
|
MOANS @ 050
|
|
| MINEE#
|
JET
|
MOANS/ANDRO @ 130
|
NORTH OPS: 250KTS
|
| TP
|
MOANS/ANDRO @ 100
|
|
| PISTON
|
MOANS/ANDRO @ 050
|
|
| PRICY#
|
JET
|
DESCEND VIA
|
NORTH OPS: PRICY @ 250KTS
|
| RIDES#
|
JET
|
DESCEND VIA
|
|
| KMLB
|
|
AOB 50
|
|
| Route
|
Type
|
Restriction
|
Note
|
| Any
|
|
ZJX BDRY AOB FL310
|
|
| Route
|
Type
|
Restriction
|
Note
|
| Any
|
|
ZJX BDRY AOB FL210
|
|
| Route
|
Type
|
Restriction
|
Note
|
| Any
|
|
ZJX BDRY AOB FL240
|
|
| Route
|
Type
|
Restriction
|
Note
|
| Any
|
|
ZJX BDRY AOB FL340
|
|
| Route
|
Type
|
Restriction
|
Note
|
| JOSFF#
|
|
BDRY (10 HILTI) AOB FL270
|
|
| PIKKR#
|
|
WHITL AOB FL310
|
|
| SHIFTY#
|
|
INPIN AOB FL310
|
|
| TYNEE#
|
|
OGGER/PIE @ FL270
|
|
| ZEILR#
|
|
PIE AOB FL310
|
|
| Route
|
Type
|
Restriction
|
Note
|
| BANGZ# (STAR)
|
JET
|
BANGZ AOB 130
|
|
| TP
|
CORRL AOB 110
|
|
| BANGZ DCT
|
JET
|
BANGZ AOB 130
|
NON-RNAV A/C
|
| TP
|
BANGZ AOB 110
|
| LUBBR#
|
JET
|
LUBBR AOB 130
|
|
| TP
|
LUBBR AOB 110
|
|
| VARZE BREKR DCT
|
JET
|
TPA BDRY (30 VARZE) AOB 130
|
NON-RNAV A/C
|
| TP
|
TPA BDRY (30 VARZE) AOB 110
|
| Route
|
Type
|
Restriction
|
Note
|
| BANGZ# (STAR)
|
JET
|
BANGZ AOB 100
|
|
| TP
|
CORRL AOB 090
|
|
| BANGZ DCT
|
JET
|
BANGZ AOB 100
|
NON-RNAV A/C
|
| TP
|
BANGZ AOB 090
|
| DADES# (STAR)
|
JET
|
OLENE AOB 130
|
South Ops: 250Kts
|
| TP
|
OLENE AOB 090
|
|
|
|
GUURR @ 120
|
North Ops
|
|
|
GUURR @ 100
|
South Ops
|
| DADES DCT
|
JET
|
TPA BDRY (20 DADES)@ 130
|
NON-RNAV A/C
|
| TP
|
TPA BDRY (20 DADES)@ 110
|
| Route
|
Type
|
Restriction
|
Note
|
| RAYZZ#
|
JET
|
ZMA BDRY AOB FL330
|
|
| DADES#
|
JET
|
OLENE @ 130
|
South Ops: 250 Kts
|
| TP
|
OLENE AOB 1100
|
|
|
|
ZINGR @ 160
|
ZMA-F11 VIA HIBAK
|
|
|
GUURR @ 120
|
North Ops
|
|
|
GUURR @ 100, 250Kts
|
South Ops
|
| DADES DCT
|
JET
|
TPA BDRY (20 DADES) @ 130
|
SOUTH OPS: 250KTS
|
| TP
|
TPA BDRY (20 DADES) @ 110
|
|
| MAATY#
|
JET
|
MAATY @ 110
|
SOUTH OPS: 280KTS
|
| TP
|
MAATY AOB 90
|
|
| TABIR#
|
JET
|
TABIR @ 110
|
SOUTH OPS: 250KTS
|
| TP
|
TABIR AOB 90
|
|
Note: F11 may deliver prop traffic landing within TPA TRACON via vectors through the KNEED DTA.
| Route
|
Type
|
Restriction
|
Note
|
| CPTAN# WOPNR
|
JET
|
NONE
|
ATC ASSIGNED ONLY
|
| CPTAN# KENLL
|
JET
|
JOEYY AOB FL280
|
|
| JESTR#
|
TP
|
DEBRL AOB FL240
|
|
| MLB#
|
TP, PISTON
|
MLB AOB FL240
|
|
| STOOP#
|
JET
|
MLB AOB FL240
|
|
| TTYLR#
|
|
PIE AOB FL270
|
|
| Orig
|
Dest
|
Required Routing
|
Note
|
| F11
|
KMIA
|
DDANY# DDANY CSTAL#
|
|
| F11
|
KFLL
|
DDANY# JIPOD CUUDA#
|
|
| F11
|
KTPA
|
GUURR DADES# or ORL LZARD#
|
CAP AOB 120
|
Note: F11 may deliver prop traffic landing within TPA TRACON via vectors through the KNEED DTA.
Appendix Found in Source File HERE:
Source Material