- Scope:
This agreement is made by and between Miami ARTCC (herein ZMA) and
Jacksonville ARTCC (herein ZJX) of the VATUSA Division of the North
American Region of VATSIM, and is entered into by the current Facility
ATMs of each ARTCC.
- Purpose:
This Letter of Agreement establishes a set of agreed upon Air Traffic
Control procedures between ZMA and ZJX, and defines the limitations and
coordination expectations of both ATC facilities.
- Cancellation
The terms of this Letter of Agreement may be suspended only by
agreement of both Facility ATMs of ZMA and ZJX, and with the explicit
approval of the VATUSA Southern Regional Director or the Director of
VATUSA. This agreement cancels all prior agreements between ZMA and ZJX.
- Tampa TRACON and Tampa International Airport
- Tampa TRACON Lateral Boundaries.
The lateral boundaries of the Tampa TRACON are described by
the Latitude and Longitude coordinates contained in Appendix A.
These coordinates shall not be altered by either ARTCC without
the explicit agreement of the Facility Chiefs of both ZMA and ZJX.
- Tampa TRACON Vertical Boundaries.
The vertical dimensions of the Tampa TRACON area shall be
from the surface to, but not including, 15,000 ft. MSL.
- Delegation of Airspace, and Controlling Authority.
The airspace of the Tampa TRACON and the airports contained
within its lateral limits shall be considered a part of ZMA
airspace. All operations within the Tampa TRACON shall fall
under the jurisdiction of ZMA, and shall be governed by the
Miami ARTCC Standard Operating Procedures and Agreements. Only
members of ZMA shall be authorized to provide ATC service within
the Tampa TRACON.
- Transfer of Control and Communication.
ZMA controllers shall complete all transfers of radar control
and communication to Enroute Center controllers or a controller
staffing MCO_APP before an aircraft reaches an altitude of
15,000 ft. MSL or the lateral limits of the Tampa TRACON,
whichever comes first. If a ZMA controller is not online
staffing the position of TPA_APP or MIA_CTR, local controllers
operating within the Tampa TRACON will advise pilots of the
presence of a ZJX controller staffing the position of JAX_CTR
or MCO_APP (whichever is appropriate) prior to the departure of
an aircraft or the termination of service.
- Orlando TRACON and Orlando International Airport:
- Orlando TRACON Lateral Boundaries.
The lateral boundaries of the Orlando TRACON are described
by the Latitude and Longitude coordinates contained in Appendix
B. These coordinates shall not be altered by either ARTCC
without the explicit agreement of the Facility ATMs of both ZMA
and ZJX.
- Orlando TRACON Vertical Boundaries.
The vertical dimensions of the Orlando TRACON area shall be
as set forth in the following diagram:
The western area of the Orlando TRACON, shown in solid gray in the
above diagram, shall be delegated the airspace within the lateral
boundaries shown and from the surface to, but not including, 15,000 ft.
MSL. The eastern area of the Orlando TRACON, shown as cross-hatched in
the above diagram, shall be delegated the airspace within the lateral
boundaries shown and from 5,500 MSL to, but not including, 15,000 MSL.
- Delegation of Airspace, and Controlling Authority.
The airspace of the Orlando TRACON and the airports contained
within the lateral limits of the western area shall be considered a part of ZJX
airspace. All operations within the Orlando TRACON shall fall
under the jurisdiction of ZJX, and shall be governed by
Jacksonville ARTCC Standard Operating Procedures. Only ZJX
controllers shall be authorized to provide ATC services within the
Orlando TRACON.
- Transfer of Control and Communication.
ZJX controllers shall complete all transfers of radar control
and communication to Enroute Center controllers or a controller
staffing TPA_APP before an aircraft reaches an altitude of
15,000 ft. MSL or the lateral limits of the Orlando TRACON,
whichever comes first. If a ZJX controller is not online
staffing the position of MCO_APP or JAX_CTR, local controllers
operating within the Orlando TRACON will advise pilots of the
presence of a ZMA controller staffing the position of MIA_CTR
or TPA_APP (whichever is appropriate) prior to the departure of
an aircraft or the termination of service.
- Daytona TRACON and Daytona International and Melbourne International Airports
- Daytona TRACON Lateral Boundaries
The lateral boundaries of the Daytona TRACON are described by the
Latitude and Longitude coordinates contained in Appendix C. These
coordinates shall not be altered by either ARTCC without the explicit
agreement of the Facility ATMs of both ZMA and ZJX.
- Daytona TRACON Vertical Boundaries
The vertical dimensions of the Daytona TRACON area shall be as set
forth in the following diagram:
The northern area of the Daytona TRACON, shown as the northern solid
gray in the above diagram, shall be delegated the airspace within the
lateral boundaries shown and from the surface to, but not including,
11,000 MSL. This northern area is wholly within the ZJX ARTCC enroute
center boundaries The southwestern area of Daytona TRACON, shown as
cross-hatched in the above diagram, shall be delegated the airspace
within the lateral boundaries shown and from the surface to, but not
including, 5,500 MSL. This area is located under the airspace delegated
to the Orlando TRACON. The southeastern area of Daytona TRACON, shown as
the southern solid gray area in the above diagram, shall be delegated
the airspace within the lateral boundaries shown and from the surface
to, but not including, 5,500 MSL.
- Delegation of Airspace, and Controlling Authority.
The airspace of the Daytona TRACON and the airports contained within
its lateral limits shall be considered a part of ZJX airspace. All
operations within the Daytona TRACON shall fall under the jurisdiction
of ZJX, and shall be governed by Jacksonville ARTCC Standard Operating
Procedures. Only ZJX controllers shall be authorized to provide ATC
services within the Daytona TRACON.
- Transfer of Control and Communication.
ZJX controllers shall complete all transfers of radar control and
communication to Enroute Center controllers before an aircraft reaches
an altitude of 5,500 ft. MSL or the lateral limits of the Daytona
TRACON, whichever comes first. If a ZJX controller is not online
staffing the position of DAB_APP or JAX_CTR, local controllers operating
within the Daytona TRACON will advise pilots of the presence of a ZMA
controller staffing the position of MIA_CTR prior to the departure of an
aircraft or the termination of service.
- Procedures and Responsibilities for all Enroute Center Controllers:
- Transfer of Control and Communication.
Enroute Center controllers (CTR) shall initiate the transfer of
control of an aircraft which will enter the enroute airspace of the
neighboring ARTCC no less than 10 NM from the ARTCC boundary, and
at a distance no greater than 40 NM from the ARTCC boundary unless
prior coordination has occurred. The transfer of control and
communications must be completed before the aircraft crosses the
ARTCC boundary.
- Separation of Enroute Aircraft.
Aircraft which are enroute, established on the same airway
and traveling in the same direction, shall enter the airspace
of the neighboring ARTCC at a separation minimum of no less than
10 NM in trail unless prior coordination has occurred and the
receiving controller has agreed to accept a separation distance
of less than 10 NM.
- Separation of Terminal Area Aircraft.
Aircraft which will be landing within the Orlando TRACON, the Daytona
TRACON, or the Tampa TRACON and are established on the same airway or
STAR, traveling in the same direction, shall enter the airspace of the
TRACON at a separation minimum of no less than 10 NM in trail
unless prior coordination has occurred and the receiving
controller has agreed to accept a separation distance of less
than 10 NM.
- Control Authority.
A receiving Enroute Controller shall not alter the altitude
or direction of flight of any aircraft which is still within
the neighboring ARTCC unless prior coordination has occurred
and the controller initiating the transfer of control has
agreed to allow the receiving controller to maneuver the
aircraft before it crosses the ARTCC boundary.
- Simulation Rate of Aircraft Transiting Boundaries.
All aircraft crossing the ARTCC boundary shall be at a
simulation rate of 1X unless prior coordination has occurred and the
receiving controller has agreed to accept the aircraft at the increased
simulation rate; no acceleration rate shall be permitted
until the aircraft has crossed the ARTCC boundary.
- Procedures and Responsibilities for ZMA Controllers:
- Routing of Aircraft Arriving Into the Orlando TRACON.
Miami Enroute Center controllers (MIA_CTR) and Tampa TRACON
controllers (TPA_APP) shall facilitate the use of STAR
procedures for aircraft which will land within the Orlando
TRACON whenever possible and instruct all aircraft with filed
STAR procedures to descend as follows:
| GOOFY arrival - KMCO landing south: |
Cross BAIRN at 11,000 MSL |
| GOOFY arrival - all others: |
Cross BAIRN at 8,000 MSL |
| MINEE arrival - KMCO landing south: |
Cross MOANS at 13,000 MSL |
|
or ANDRO at 13,000 MSL |
| MINEE arrival - all others: |
Cross MOANS at 10,000 MSL |
|
and 250 kts or ANDRO at 13,000 |
|
MSL and 250 kts. |
MIA_CTR controllers and TPA_APP controllers will instruct all
aircraft which will land within the Orlando TRACON, but have not
filed a STAR procedure, to cross BAIRN, MOANS or ANDRO as specified
above.
- Transfer of Control and Communications-Orlando TRACON
MIA_CTR controllers and TPA_APP controllers will complete all
handoffs and transfers of communication before an aircraft crosses
BAIRN, MOANS or ANDRO, or otherwise crosses the lateral or vertical
limits of the Orlando TRACON.
- Transfer of Control and Communications-Daytona TRACON
Aircraft which will land at airfields within the Daytona TRACON shall
be handed off to DAB_APP (when online) at or below 5,500 MSL before
crossing the Daytona TRACON boundary, to DAB_APP (when online) at 5,500
MSL with the aircraft descending to maintain 4,000 MSL within 20nm of
their destination, or to a ZJX Enroute controller (JAX_CTR) at the
lateral points and altitudes described above if DAB_APP is offline.
- Transfer of Control and Communications-Aircraft Arriving KDAB
Aircraft which will land at Daytona Beach International Airport
(KDAB) shall be handed off to MCO_APP (when online) at or below 10,000
MSL before crossing the Orlando TRACON boundary, DAB_APP (when online
and MCO_APP offline) at or below 10,000 MSL and above 5.500 MSL before
crossing the ARTCC boundary, or to a ZJX Enroute controller (JAX_CTR) at
or below 10,000 MSL before crossing the ARTCC boundary.
- Altitude Assignments-Cruise Below 15,000 MSL
Aircraft departing the Tampa TRACON that have received a
clearance for an enroute cruise altitude below 15,000 ft. MSL shall
be cleared to their final cruise altitude before departing the
boundaries of the Tampa TRACON.
- Altitude Assignments-Cruise At or Above 15,000 MSL
Aircraft departing the Tampa TRACON that have received a
clearance for an enroute cruise altitude above 15,000 ft.
MSL shall be cleared to climb and maintain 15,000 ft. until radar
control and communications have been transferred to an Enroute
Center Controller.
- Initial Course
Aircraft departing the Tampa TRACON shall be cleared to the
first waypoint in their filed route unless prior coordination with
the ZJX controller who will be accepting the handoff has occurred.
- Point-Outs for Westbound KTPA Departures
Aircraft departing the Tampa TRACON to the west will cleared to
the first waypoint in their filed route, and depart the Tampa TRACON
on a heading direct to COVIA intersection. If the flight path of
the aircraft will take the aircraft inside ZJX airspace, the
Tampa TRACON controller, or ZMA Controller providing departure
service, shall request a point-out from the ZJX Enroute controller
to minimize the necessary transfers between facilities, and radio
frequency changes that would be required by the pilot.
- Procedures and Responsibilities for ZJX Controllers:
- Routing of Aircraft Arriving Into the Orlando TRACON.
Jacksonville Enroute Center controllers (JAX_CTR) and Orlando
TRACON controllers (MCO_APP) shall vector and/or instruct all
aircraft which will land at an airport within the Tampa TRACON to
cross one of the following intersections at 13,000 MSL:
WALTR - KSRQ Arrivals only
TABIR
MARVI
DADES
- Transfer of Control and Communications-Tampa TRACON
JAX_CTR controllers and MCO_APP controllers will complete all
handoffs and transfers of communication before an aircraft crosses
WALTR, TABIR, MARVI or DADES, or otherwise crosses the lateral or
vertical limits of the Tampa TRACON.
- Altitude Assignments-Cruise Below 15,000 MSL (Below 5.500 MSL for
Daytona TRACON)
Aircraft departing the Orlando TRACON that have received a
clearance for an enroute cruise altitude below 15,000 ft. MSL shall
be cleared to their final cruise altitude before departing the
boundaries of the Orlando TRACON. Aircraft departing the Daytona TRACON
that have received a clearance for an enroute cruise altitude below
5,500 ft. MSL shall be cleared to their final cruise altitude before
departing the boundaries of the Daytona TRACON.
- Altitude Assignments-Cruise At or Above 15,000 MSL (At or Above
5,500 for Daytona TRACON)
Aircraft departing the Orlando TRACON that have received a clearance
for an enroute cruise altitude above 15,000 ft. MSL shall be cleared to
climb and maintain 15,000 ft. until radar control and communications
have been transferred to an Enroute Center Controller. Aircraft
departing the Daytona TRACON that have received a clearance for an
enroute cruise altitude above 5,500 ft. MSL shall be cleared to climb
and maintain 5,000 ft. until radar control and communications have been
transferred to an Enroute Center Controller.
- Initial Course
Aircraft departing the Orlando or Daytona TRACONs shall be cleared to the
first waypoint in their filed route unless prior coordination with
the ZMA controller who will be accepting the handoff has occurred.
This Letter of Agreement has been agreed upon and entered into on 01 July 2006 at 0400Z by:
