ZMA LOA: Difference between revisions
No edit summary |
|||
Line 44: | Line 44: | ||
When Sector 02 (HOBEE) of Miami Center is online, ZJX shall ensure all aircraft landing within ZMA routed via the OMN corridor (eastern shore) will cross the ZJX/ZMA common airspace boundary AOB FL300, and via the western shore corridor AOB FL310.<br> | When Sector 02 (HOBEE) of Miami Center is online, ZJX shall ensure all aircraft landing within ZMA routed via the OMN corridor (eastern shore) will cross the ZJX/ZMA common airspace boundary AOB FL300, and via the western shore corridor AOB FL310.<br> | ||
ZMA authorizes ZJX to work all arrivals via PRICY# & ALYNA# (or equivalent) through Miami Center airspace when Miami Center is offline.<br> | ZMA authorizes ZJX to work all arrivals via PRICY# & ALYNA# (or equivalent) through Miami Center airspace when Miami Center is offline.<br> | ||
ZJX authorizes ZMA to work the MAATY | ZJX authorizes ZMA to work the MAATY/DADES arrivals (or equivalent) through Jacksonville Center and F11 ATCT airspace when Jacksonville Center is offline. Arrivals are to be issued descent in compliance with this LOA.<br> | ||
ZMA shall not descend aircraft below 12,000ft. until West of the Tampa ATCT/F11 shared boundary. | ZMA shall not descend aircraft below 12,000ft. until West of the Tampa ATCT/F11 shared boundary. | ||
Revision as of 17:32, 16 April 2023
Table of Updates
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. |
ARTCC Information
ARTCC Code | ARTCC Name | Effective Date |
---|---|---|
ZMA | Miami ARTCC | 15 July 2020 |
Purpose: This agreement establishes coordination procedures and defines delegation of airspace between VATUSA Jacksonville ARTCC (ZJX) and VATUSA Miami ARTCC(ZMA). This agreement is supplemental to procedures contained within FAA Order 7110.65.
Distribution:
This order is distributed to all Jacksonville and Miami ARTCC personnel.
General Responsibilities
All handoffs will be conducted by radar handoff functionality unless otherwise coordinated.
All communications handoffs shall occur no later than the sector boundary.
Unless otherwise coordinated, data blocks and any relevant scratchpads shall be updated by the transferring center controller to accurately reflect assigned altitude information prior to initiation of a radar handoff.
Aircraft of similar performance landing within ZJX/ZMA shall be provided 5 miles in trail, constant or increasing, regardless of altitude (no stacks).
Transitioning aircraft shall not be permitted to operate an enhanced simulation rate greater than 1x across the sector boundary, unless prior coordination has been achieved.
Upon receiving a handoff from F11, ZMA shall have control for climbs.
When initially logging on to a position, ZJX shall indicate to ZMA whether F11 is utilizing north or south operations.
When initially logging on to a position, ZMA shall indicate to ZJX whether Tampa ATCT is utilizing north or south operations.
When Sector 02 (HOBEE) of Miami Center is online, ZJX shall ensure all aircraft landing within ZMA routed via the OMN corridor (eastern shore) will cross the ZJX/ZMA common airspace boundary AOB FL300, and via the western shore corridor AOB FL310.
ZMA authorizes ZJX to work all arrivals via PRICY# & ALYNA# (or equivalent) through Miami Center airspace when Miami Center is offline.
ZJX authorizes ZMA to work the MAATY/DADES arrivals (or equivalent) through Jacksonville Center and F11 ATCT airspace when Jacksonville Center is offline. Arrivals are to be issued descent in compliance with this LOA.
ZMA shall not descend aircraft below 12,000ft. until West of the Tampa ATCT/F11 shared boundary.
Route Restrictions
If ZJX75/57 are combined, ZMA will issue BDRY AOBFL310. If ZJX57 is staffed by a separate controller, ZMA will issue BDRY AOBFL250.
Aircraft on or east of Q77/V267 shall be cleared northbound at ODD altitudes and southbound at EVEN altitudes.
Aircraft on routes/flight plans which are west of Q77/V267 shall be cleared northbound at EVEN altitudes and southbound at ODD altitudes.
Aircraft arriving TPA via the DADES# STAR HIBAC transition shall cross ZINGR at 17000 for F11 transition to TPA TRACON. DADES# STAR HIBAC transition shall be at the Tampa ATCT border at 12,000 if north OPS. South OPS 10,000 and 250 knots at the TPA ATCT border.
Airspace: ZJX
ZJX Airspace:ZJX Airspace exists North of the ZJX/ZMA shared boundary depicted on the FAA En Route H-8 High Airway Chart. This airspace also exists from the surface to FL600.
ZJX & F11 Delegated Airspace: ZJX & F11 are delegated airspace from ZMA in accordance with of this agreement. F11 is delegated airspace from Tampa ATCT in accordance with this agreement.
Airspace: ZMA
ZMA Airspace:ZMA Airspace exists South of the ZJX/ZMA shared boundary depicted on the FAA En Route H-8 High Airway Chart. This airspace also exists from the surface to FL600.
ZMA & Tampa ATCT Delegated Airspace: ZMA & Tampa ATCT are delegated airspace from ZJX in accordance with this agreement.
Airport Specific Restrictions to ZMA
Crossing Restrictions
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
VUUDU# | MOLIE | at or below FL350 | ||
CPTAN# | Border | FL280 | WOPNR Transition not to be used on VATSIM. | |
JESTR# | DEBRL | At or below FL240 | Turboprops Only | |
MLB# | Boundary | At or below FL240 | Turboprops and props only | |
STOOP# | Boundary | At or below FL240 | Turbojets only | |
TTYLR# | PIE | At or below FL270 |
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
BANGZ# | Bangz | 10,000 | 250 Knots if in South Operations | |
DADES# | Border | 12,000 (North)/10,000 (South) | 250 Knots if in South Operations |
Crossing Restrictions
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
TYNEE# | OGGER or PIE | FL270 | ||
SHFTY# | INPIN | at or below FL310 | ||
JOSFF# | HILTI or PIE | at or below FL270 |
Crossing Restrictions (Jets)
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
BANGZ# | BANGZ | 13,000 | ||
LUBBR# | LUBBR | 13,000 | ||
All Others | BORDER | 13,000 |
Crossing Restrictions (Props)
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
BANGZ# | BANGZ | 11,000 | ||
LUBBR# | LUBBR | 11,000 | ||
All Others | BORDER | 11,000 |
Aircraft departing F11 and intending to land at an airport within the Tampa ATCT boundary shall be vectored through the KNEED DTA.
Jet aircraft departing KMCO airport and intending to land KTPA airport shall be routed via GUURR DADES# or ORL LZARD#. Aircraft shall be vectored through the CAMAN SOUTH DTA and onto the ORL transition of the respective arrival. Aircraft shall be climbed to an altitude at or below 12,000ft.
Crossing Restrictions
Departure | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
DADES# | OLENE | 13,000 | 250 Knots if in South Operations | |
DARBS# (Discontinue 4/20/2023) | TABIR | 13,000 | 250 Knots if in South Operations | |
MAATY# (Discontinue 4/20/2023) | Descend via arrival and airport ops. | |||
MAATY# (Effective 4/20/2023) | MAATY | 11,000 | 280 Knots if South OPerations | |
DADES# via HIBAC | Border | 12,000 (North Ops) 10,000 (South Ops) | 250 Knots if in South Operations |
Airport Specific Restrictions from ZMA
Aircraft departing from an airport within the Tampa ATCT boundary and intending to land at an airport within the DAB ATCT shall be routed via KNEED V152 OMN.
Note: Turboprop and turbojet aircraft shall cross the TPA/F11 boundary at or below 11,000ft. Piston aircraft shall cross the TPA/F11 boundary at or below 5,000ft.
Aircraft coming from ZMA airspace not from the TPA area shall cross F11 boundary/MLB (on V3) at 15,000 feet.
Jet aircraft departing KTPA airport and intending to land KMCO or KSFB airports shall be routed via the MINEE#/PRICY# arrival.
Prop/TurboProp aircraft departing an airport within the Tampa ATCT boundary and intending to land at an airport within the F11 boundary other than MCO be routed via the MINEE# arrival, and instructed to cross the TPA/F11 border at 5,000ft.
ZMA shall vector and/or instruct all aircraft intending to land at an airport within the F11 boundary to cross one of the following intersections at the specified altitude:
Arrival | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
GOOFY# | BAIRN | 8,000 (North Ops), 11,000 (South Ops) | ||
MINEE# | ANDRO | 13,000 | 250 Kts | |
MINEE# | MOANS | 10,000 (North Ops), 13,000 (South Ops) | 250 Kts | |
AYLNA# | SURFR | 14,000 | F11 will issue the "descend via" instructions. | |
All other RNAV Arrivals | Descend via the arrival with appropriate airport operations. |
Arrival | Waypoint | Altitude | Speed | Note |
---|---|---|---|---|
GOOFY# | BAIRN | 8,000 | ||
MINEE# | MOANS or ANDRO | 13,000 | ||
JOKRS# | JOKRS | 8,000 | ||
ALYNA# | SURFR | 14,000 | ||
RIDES# & PRICY# | ZMA will issue "descend via" and will treat it as single flow with MCO arrivals. |
Traffic to MLB and COF will cross F11 boundary at 5,000 feet.
Other Restrictions
Aircraft departing F11 shall be vectored towards a DTA and then cleared on course.
Jet aircraft departing F11 which are Southeast bound through TPSTR/ATLAS/CUSSR shall be instructed to climb to 14,000ft.
Aircraft departing F11 which are Southwest bound through KLMAN shall be instructed to climb to 16,000ft.
Aircraft departing from KMLB, KCOF, KCOI, KTIX, KXMR, KTTS, X21 may utilize the VALKA and PIPER DTAs. No other airports may utilize these DTAs.
Aircraft transitioning through the CAMAN DTA shall cross the F11/Tampa ATCT shared boundary above 13,000ft unless that aircraft intends to land at an airport within the Tampa ATCT boundary.