ZMA LOA: Difference between revisions

From ZJX ARTCC SOPs
Jump to navigation Jump to search
No edit summary
Line 27: Line 27:
|}
|}
'''Purpose:'''
'''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.
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:'''
'''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.


This order is distributed to all Jacksonville and Miami ARTCC personnel.
== [[Coordinating Runway Configurations]] ==
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)<br>
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)<br>
Note: (1)Including any of TPA_TWR, TPA_APP, or MIA_CTR.<br>
(2)Including any of MCO_TWR, MCO_APP, or JAX_CTR. <br>


== [[General Responsibilities]] ==
== [[Conditional Authorization for Use of Airspace]] ==
All handoffs will be conducted by radar handoff functionality unless otherwise coordinated. <BR>
All communications handoffs shall occur no later than the sector boundary. <br>
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. <br>
<br>
<br>
Aircraft of similar performance landing within ZJX/ZMA shall be provided 5 miles in trail, constant or increasing, regardless of altitude (no stacks).<br>
<b>General</b><br>
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.<br>
<br>
<br>
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.<br>
<b>F11 Area Arrivals</b><br>
Upon receiving a handoff from F11, ZMA shall have control for climbs.<br>
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.<br><br>
<b> TPA Area Arrivals</b><br>
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.<br>
<br>
<b> Other Inbound Aircraft</b><br>
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.<br><br>
== [[F11 Departure Traffic]] ==
Aircraft Departing F11 airspace shall be vectored towards a Departure Transition Area (DTA) and cleared on course before communications are transferred to ZMA. F11 departures via TPSTR/ATLAS/CUSSR shall be delivered to ZMA climbing to 14,000 (or lower requested altitude, as appropriate for direction of flight). The VALKA and PIPER DTAs may only be used by aircraft departing from MLB, COF, COI, TIX, XMR, TTS, or X21. ZMA shall have control for climb, on contact, of all F11 departure traffic. <br>
<br>
<br>
When initially logging on to a position, ZJX shall indicate to ZMA whether F11 is utilizing north or south operations.<br>
When initially logging on to a position, ZMA shall indicate to ZJX whether Tampa ATCT is utilizing north or south operations.<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>
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 handoff all DADES# arrivals via HIBAC to F11. F11 will descend and then transfer control to TPA.


== [[Route Restrictions]] ==
== [[Q77 Rule]] ==
<tabs>
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.<br><br>
<tab name="Jacksonville Area">
If ZJX75/57 are combined, ZMA will issue BDRY AOBFL310. If ZJX57 is staffed by a
separate controller, ZMA will issue BDRY AOBFL250.
</tab>
<tab name="Q77">
Aircraft on or east of Q77/V267 shall be cleared northbound at ODD altitudes and southbound at EVEN altitudes.<br>
Aircraft on routes/flight plans which are west of Q77/V267 shall be cleared northbound at EVEN altitudes and southbound at ODD altitudes.
</tab>
<tab name="Tampa via F11">
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.<br>
</tab>
</tabs>


== [[Airspace: ZJX]] ==
<U>ZJX Airspace:</U>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.<br>
<u>ZJX & F11 Delegated Airspace: </u> 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.
<br><br>
[[File:F11AR.JPG]]


== [[Airspace: ZMA]] ==
== [[Activation of ZMA's HOBEE Sector]] ==
<U>ZMA Airspace:</U>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.<br>
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.<br><br>
<u>ZMA & Tampa ATCT Delegated Airspace: </u> ZMA & Tampa ATCT are delegated airspace from ZJX in accordance with this agreement.


<br><br>
== [[Transfer of Control and Communication]] ==
[[File:TPALOA.JPG]]
Aircraft communications shall be transferred no later than the airspace boundary. <br>
All handoffs and point outs shall be conducted through automated means, when available, unless otherwise coordinated.<br>
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.<br>
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).<br>
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.<br>
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.


== [[Routing and Altitude Requirements]] ==
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).<br><br>


== [[Airport Specific Restrictions to ZMA]] ==
== [[Restrictions and Requirements]] ==
<tabs>
=== [[Daytona (KDAB and Satellites)]] ===
<tab name="PBI">
<b>Crossing Restrictions</b>
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+
|+
!Departure
!Route
!Waypoint
!Type
!Altitude
!Restriction
!Speed
!Note
!Note
|-
|-
|VUUDU#
|rowspan="2"|KNEED V152 OMN
|MOLIE
|JET, TP
|at or below FL350
|AOB 11,000
|
|rowspan="2"|TPA-F11 Traffic
|
|-
|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#
|PISTON
|Boundary
|AOB 50
|At or below FL240
|
|Turbojets only
|-
|-
|TTYLR#
|any
|PIE
|At or below FL270
|
|
|F11 BDRY @ 150
|
|
|}
|}
</tab>
 
<tab name="PIE">
=== [[F11 Orlando (KMCO and Satellites)]] ===
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+
|+
!Departure
!Route
!Waypoint
!Type
!Altitude
!Restriction
!Speed
!Note
!Note
|-
|-
|BANGZ#
|ALYNA#
|Bangz
|JET
|10,000
|SURFR @ 140
|250 Knots if in South Operations
|
|-
|DADES#
|Border
|12,000 (North)/10,000 (South)
|250 Knots if in South Operations
|
|}
</tab>
<tab name="RSW">
<b>Crossing Restrictions</b>
{| class="wikitable" style="width: 100%;"
|+
!Departure
!Waypoint
!Altitude
!Speed
!Note
|-
|TYNEE#
|OGGER
|FL270
|
|
|
|-
|-
|SHFTY#
|rowspan="3"|GOOFY#
|INPIN
|JET,TP
|at or below FL310
|BAIRN @ 110
|
|MCO SOUTH OPS
|
|-
|-
|JOSFF#
|JET,TP
|HILTI or PIE
|BAIRN @ 080
|at or below FL270
|MCO NORTH OPS
|
|
|}
</tab>
 
<tab name="SRQ">
<b>Crossing Restrictions (Jets)</b>
{| class="wikitable" style="width: 100%;"
|+
!Departure
!Waypoint
!Altitude
!Speed
!Note
|-
|-
|BANGZ#
|JET,TP
|BANGZ
|BAIRN @ 080
|13,000
|SATELLITES
|
|
|-
|-
|LUBBR#
|rowspan="3"|JOKRS#
|LUBBR
|JET
|13,000
|MOANS @ 130
|
|NORTH OPS: 250KTS
|
|-
|-
|All Others
|TP
|BORDER
|MOANS @ 100
|13,000
|
|
|
|}
<br>
<b>Crossing Restrictions (Props)</b>
{| class="wikitable" style="width: 100%;"
|+
!Departure
!Waypoint
!Altitude
!Speed
!Note
|-
|-
|BANGZ#
|PISTON
|BANGZ
|MOANS @ 050
|11,000
|
|
|
|-
|-
|LUBBR#
|rowspan="3"|MINEE#
|LUBBR
|JET
|11,000
|MOANS/ANDRO @ 130
|
|NORTH OPS: 250KTS
|
|-
|-
|All Others
|TP
|BORDER
|MOANS/ANDRO @ 100
|11,000
|
|
|
|}
</tab>
<tab name="TPA">
Aircraft departing F11 and intending to land at an airport within the Tampa ATCT boundary shall be vectored through the KNEED DTA.<br>
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.<br>
<br>
<b>Crossing Restrictions</b>
{| class="wikitable" style="width: 100%;"
|+
!Departure
!Waypoint
!Altitude
!Speed
!Note
|-
|-
|DADES#
|PISTON
|OLENE
|MOANS/ANDRO @ 050
|13,000
|250 Knots if in South Operations
|
|
|-
|-
|DARBS# (Discontinue 4/20/2023)
|PRICY#
|TABIR
|JET
|13,000
|DESCEND VIA
|250 Knots if in South Operations
|NORTH OPS: PRICY @ 250KTS
|
|-
|-
|MAATY# (Discontinue 4/20/2023)
|RIDES#
|
|JET
|Descend via arrival and airport ops.
|DESCEND VIA
|
|
|
|-
|-
|MAATY# (Effective 4/20/2023)
|KMLB
|MAATY
|11,000
|280 Knots if South OPerations
|
|
|-
|AOB 50
|DADES# via HIBAC
|Border
|12,000 (North Ops) 10,000 (South Ops)
|250 Knots if in South Operations
|
|
|}
|}
</tab>
</tabs>


== [[Airport Specific Restrictions from ZMA]] ==
=== [[Jacksonville (KJAX and Satellites)]] ===
<tabs>
<tab name="DAB">
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. <br>
<i>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. </I><br>
Aircraft coming from ZMA airspace not from the TPA area shall cross F11 boundary/MLB (on V3) at 15,000 feet.
</tab>
<tab name="MCO or F11">
Jet aircraft departing KTPA airport and intending to land KMCO or KSFB airports shall be routed via the MINEE#/PRICY# arrival.<br>
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.<br>
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:
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+Orlando International Arrivals
|+
!Arrival
!Route
!Waypoint
!Type
!Altitude
!Restriction
!Speed
!Note
!Note
|-
|-
|GOOFY#
|rowspan="2"|QUBEN#/POGIE#
|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.
|AOB FL310
|J57/J75 COMBINED
|-
|-
|All other RNAV Arrivals
|
|
|
|
|AOB FL250
|Descend via the arrival with appropriate airport operations.
|J57/J75 SPLIT
|}
|}


=== [[Fort Myers Area (KRSW)]] ===
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+KISM, KLEE, KMLB, KORL, KSFB, and KTIX
|+
!Arrival
!Route
!Waypoint
!Type
!Altitude
!Restriction
!Speed
!Note
!Note
|-
|-
|GOOFY#
|JOSFF#
|BAIRN
|8,000
|
|
|BDRY (10 HILTI) AOB FL270
|
|
|-
|-
|MINEE#
|PIKKR#
|MOANS or ANDRO
|13,000
|
|
|WHITL AOB FL310
|
|
|-
|-
|JOKRS#
|SHIFTY#
|JOKRS
|8,000
|
|
|INPIN AOB FL310
|
|
|-
|-
|ALYNA#
|TYNEE#
|SURFR
|14,000
|
|
|OGGER/PIE @ FL270
|
|
|-
|-
|RIDES# & PRICY#
|ZEILR#
|
|
|
|PIE AOB FL310
|
|
|ZMA will issue "descend via" and will treat it as single flow with MCO arrivals.
|}
|}
<br>
Traffic to MLB and COF will cross F11 boundary at 5,000 feet.<br>
</tab>
</tabs>
== [[Other Restrictions]] ==
<tabs>
<tab name="Orlando Area">
Aircraft departing F11 shall be vectored towards a DTA and then cleared on course.<br>
Jet aircraft departing F11 which are Southeast bound through TPSTR/ATLAS/CUSSR shall be instructed to climb to 14,000ft. <br>
Aircraft departing F11 which are Southwest bound through KLMAN shall be instructed to climb to 16,000ft.<br>
Aircraft departing from KMLB, KCOF, KCOI, KTIX, KXMR, KTTS, X21 may utilize the VALKA and PIPER DTAs. No other airports may utilize these DTAs.<br>
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.
</tab>
</tabs>[https://zjxartcc.org/media/doc/ZJX_ZMA_LOA_202209_1.pdf Reference LOA]

Revision as of 15:28, 7 September 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.
7 September 2023 B 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 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.

Coordinating Runway Configurations

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.

Conditional Authorization for Use of Airspace


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.

F11 Departure Traffic

Aircraft Departing F11 airspace shall be vectored towards a Departure Transition Area (DTA) and cleared on course before communications are transferred to ZMA. F11 departures via TPSTR/ATLAS/CUSSR shall be delivered to ZMA climbing to 14,000 (or lower requested altitude, as appropriate for direction of flight). The VALKA and PIPER DTAs may only be used by aircraft departing from MLB, COF, COI, TIX, XMR, TTS, or X21. ZMA shall have control for climb, on contact, of all F11 departure traffic.

Q77 Rule

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.


Activation of ZMA's HOBEE Sector

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.

Transfer of Control and Communication

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.

Routing and Altitude Requirements

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).

Restrictions and Requirements

Daytona (KDAB and Satellites)

Route Type Restriction Note
KNEED V152 OMN JET, TP AOB 11,000 TPA-F11 Traffic
PISTON AOB 50
any F11 BDRY @ 150

F11 Orlando (KMCO and Satellites)

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

Jacksonville (KJAX and Satellites)

Route Type Restriction Note
QUBEN#/POGIE# AOB FL310 J57/J75 COMBINED
AOB FL250 J57/J75 SPLIT

Fort Myers Area (KRSW)

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
Retrieved from "https://www.idszjxartcc.org/index.php?title=ZMA_LOA&oldid=862"