MCO APP ARTCC LOA
Table of Contents
1. Purpose
The purpose of this LOA is to define standard operating procedures into and out of the Orlando TRACON airspace
from Center to Delivery controllers. This LOA hereby cancels all previous LOAs between MCO APP, JAX CTR, and the
appropriate towers listed herein.
This LOA Was Re-Drafted on 15th April 2010 by Jacksonville Facilities Engineer, Rahul Parkar and Jacksonville Training Administrator, Stephen Faison. This Re-Draft was also Approved by Jacksonville Air Traffic Manager, Chris La Salle on the 15th April 2010.
2. Jacksonville Center/Orlando TRACON LOA
The following procedures are applicable only when Orlando TRACON and Jacksonville Center are both staffed. In the absence of Jacksonville Center
the TRACON controller shall only clear aircraft to the TRACON ceiling of 16,000. Once the aircraft is nearing 16,000 or leaving the lateral boundaries of the TRACON airspace (whichever comes first), the controller shall terminate radar services by giving approval of a frequency change.
2.1 Arrival Procedures
Aircraft inbound to any airport within the Orlando TRACON shall follow the scratchpad procedures as outlined in section 2.4
as outlined for Center control. If Jacksonville Center is acting as Orlando TRACON, Jacksonville Center controllers shall abide
by the appropriate sectors as per the level of control for the aircraft.
Aircraft inbound via a Standard Terminal Arrival Route (STAR) shall have the appropriate altitudes assigned as defined by their
filed STAR unless pilot requests otherwise and such intentions are communicated with and approved by the appropriate TRACON controller.
All altitude assignments must be in concurrence with section 2.5.
2.2 Departure Procedures in the TRACON
After departure and radar contact with the appropriate Departure or Approach controller, the aircraft will be climbed to 8,000 MSL (with the exception of the aircraft departing on the 35's or 36's with an initial departure heading of 060/065), these aircraft will be given an initial climb to 5,000 MSL as depicted in diagram A5). Once clear of the arrival flow of aircraft, these departures may be climbed to your TRACON ceiling and given vectors to the first fix on their flight plan, or vectors to rejoin the SID they were on. Before they leave the vertical or lateral limits of your airspace, they shall be handed off to the adjacent sector/facility.
Diagram Available : Section A4 & A5
Aircraft on SIDs, with the exception of those restricted in section 2.2.1, shall exit as per their filed route at an altitude appropriate for their direction of travel or
an altitude assigned by the SID.
Altitude and scratchpad procedures listed under sections 2.4 and 2.5.
2.2.1 North SIDs (JAG, MCOY, northbound) Restrictions
Aircraft departing via the following SIDs shall be handled as defined in this section:
After departure, aircraft shall be climbed to 8,000 feet along with initial heading. Once clear of the arrival flow(s), they may be climbed to your TRACON ceiling of 16,000 ft. and vectored to the GUANO intersection to resume the departure procedure as published. They shall be handed off as defined under section 2.6, but remain in
radio contact with Orlando Approach until 5 nautical miles from the Orlando NASA Sector and Orlando Daytona Sector boundary unless otherwise coordinated.
2.3 Holdings
During periods of high traffic, Orlando Approach may choose to have aircraft enter holds. This shall be coordinated utilizing the automated handoff procedures outlined in section 2.6
or via inter-facility communications. To coordinate holdings via inter-facility communications, utilizing the following phraseology:
APP: Daytona, Orlando Approach, Request.
Daytona: Daytona.
APP: Request holding of inbound aircraft (call sign) for (duration) minutes.
Daytona: (Initials).
APP: (Initials).
Holding as outlined in the handoff procedures defined by section 2.6 is the preferred method but communication of intentions is still highly recommended.
2.4 Scratchpad Entries
Center shall place in the scratchpad of arriving aircraft their filed STAR or final waypoint prior to the arrival airport. The following
is a list of STARs into the Orlando area and their associated scratchpad entry (STAR NAME - SCRATCH PAD ENTRY):
- Kissimee Gateway (KISM):
- BAIRN2 - BRN2
- BITHO7 - BTH7
- COSTR2 - CST2
- GOOFY5 - GFY5
- LEESE2 - LSE2
- MINEE4 - MNE4
- PIGLT2 - PGL2
- Orlando Executive (KORL):
- BAIRN2 - BRN2
- CORLL1 - CRL1
- COSTR2 - CST2
- CWRLD2 - CWD2
- GOOFY5 - GFY5
- LEESE2 - LES2
- MINEE4 - MNE4
- PIGLT2 - PGL2
- Orlando International Airport (KMCO):
- BAIRN2 - BRN2
- BITHO7 - BTH7
- BUGGZ1 - BGZ1
- COSTR2 - CST2
- CWRLD2 - CWD2
- GOOFY5 - GFY5
- LEESE2 - LSE2
- MINEE4 - MNE4
- PIGLT2 - PGL2
- Melbourne International (KMLB):
- BITHO7 - BTH7
- COSTR2 - CST2
- Orlando Sanford International (KSFB):
- BAIRN2 - BRN2
- CORLL1 - CRL1
- COSTR2 - CST2
- CWRLD2 - CWD2
- GOOFY5 - GFY5
- MINEE4 - MNE4
2.5 Altitude Assignments in VRC
All altitude assignments outside of cruise altitude assignment or adjustments shall be placed in an aircraft's scratchpad. VRC
allows this by two methods; right click on an aircraft, select the "Temp. Alt" menu then select the appropriate altitude or utilize
the text command ".QQ (TEMP ALT IN 3 DIGITS, 017 = 1,700, 170 = 17,000, etc.)" and selecting the aircraft. Descents via STARs are to be
placed in temporary altitudes as well.
2.6 Handoffs
En-route controllers shall initiate automated handoffs to TRACON controllers no later than 20nm prior to their filed STAR's published holding point. If an aircraft reaches 5nm from that point
and the handoff has not be accepted, controllers shall instruct the aircraft to hold as published with an expected further clearance time of 10 minutes. During this time,
traffic permitting, center controllers shall attempt to do a verbal radar handoff with the appropriate TRACON controller. If a verbal handoff is unsuccessful, the aircraft
shall continue holding until the handoff is accepted by Approach.
During periods of high traffic, Approach controllers may request aircraft to be held. All aircraft will be held at the published holding points
with radar handoffs being initiated as stated above. Aircraft shall remain in the holding pattern until a handoff is accepted by the appropriate
TRACON controller wherein the aircraft shall be vectored out of the holding pattern and back to their filed route and a communications handoff completed ("CONTACT ____ on ____").
If an aircraft is not flying on a filed route that does not contain a STAR, radar handoff shall be attempted prior to 30nm from the border. If
in a period of holding, or handoff not completed, the aircraft is to enter a holding pattern at a location at the discretion of the center controller.
A verbal radar handoff is completed utilizing the following phraseology:
Daytona: Orlando Approach, Daytona, Handoff.
APP: Approach.
Daytona: November 4 6 4 8 Lima, Type Baron, 10 miles from LEESE at 7,000.
APP: Radar Contact, (initials).
Daytona: (initials).
If an approach controller is not ready to take an aircraft being handed off through a verbal radar handoff procedure, they are to respond with "Unable. Continue hold (approximate duration)." and await for center to state their initials
meaning they acknowledge the request. After center acknowledges, the approach controller shall state their initials to indicate that they copied the holding acknowledgment.
Approach controllers shall hand off aircraft to the appropriate center controller. During normal operations, all handoffs will go to the following sectors in order of responsibility
depending which sectors are on: 35, 34, or 33, consult the Low Altitude Sector Chart in Appendix A3.
3. Miami ARTCC/Orlando TRACON LOA
The following is a letter of agreement between Jacksonville ARTCC and Miami ARTCC specific to the Orlando TRACON region and Tampa TRACON region.
3.1 Routing and Handoff of Aircraft Inbound Orlando Area
Miami En-route Controllers and Tampa TRACON controllers shall facilitate the use of STAR procedures for aircraft which will land within the Orlando
TRACON boundary whenever possible and instruct all aircraft with filed STAR procedures to cross the following points at the following altitudes:
| STAR | Crossing Restrictions |
|---|
| GOOFY | KMCO South Ops-BAIRN at 11000
All Others-BAIRN at 8000 |
| MINEE | KMCO South Ops-MOANS at 13000
KMCO South Ops-ANDRO at 13000
All Others-MOANS 10000 @ 250kts
All Others-ANDRO 13000 @ 250kts |
For all other arrivals not following a specified STAR shall have an aircraft cross the boundary with the above altitudes. Controllers will complete handoffs
and transfer of communication before an aircraft crosses BAIRN, MOANS, or ANDRO or otherwise crosses the lateral or vertical boundaries of Orlando TRACON.
3.2 Routing and Handoff of Aircraft Inbound Melbourne Area
Aircraft which will land at airfields within the Melbourne area shall be handed off to Orlando Approach before crossing the boundary at 5,500 ft. MSL with the aircraft
descending to maintain 4,000 ft. MSL within 20nm of their destination, or to the appropriate ZJX En-route Controller when staffed if Orlando Approach is offline.
3.3 Routing and Handoff of Aircraft Inbound Daytona Area
Aircraft inbound into the Daytona Beach area shall be handed off to Orlando Approach, if staffed otherwise Center, at or below 10,000 ft. MSL prior to crossing the Orlando
TRACON boundary.
3.4 Routing and Handoff of Aircraft Inbound Tampa Area
Jacksonville Center and Orlando TRACON controllers shall vector and/or instruct all aircraft which will land at an airport within the boundaries of
Tampa TRACON to cross one of the following intersections at 13,000 ft. MSL:
- WALTR - KSRQ Arrivals Only
- TABIR (DARBS1 & FOOXX2)
- OLENE (LZARD4 & DADES2)
Handoff and transfer of communications shall be completed prior to an aircraft crossing the above fixes or otherwise crossing the lateral or vertical limits
of the Tampa TRACON.
3.5 Departure Altitude Assignments
For all departures out of the Orlando TRACON entering Tampa TRACON or Miami En-route airspace shall be assigned an altitude of 16,000 ft. MSL, or the aircraft's filed cruise
altitude, whichever is lower, unless previously coordinated with the appropriate controllers.
For all departures out of the Tampa TRACON entering Orlando TRACON or Jacksonville En-route airspace shall be assigned an altitude of 12,000 ft. MSL, or the aircraft's filed cruise
altitude, whichever is lower, unless previously coordinated with the appropriate controllers.
4. Orlando TRACON Intrafacility
The following is a letter of agreement for operations within the Orlando TRACON.
4.1 Scratchpad Entries
Aircraft inbound on a STAR are to have scratchpad entries as defined under the Center/TRACON LOA in Section 3.4 until expected vectors to final
have been presented to an aircraft. Controllers telling an aircraft to expect a specific runway are to place the assigned runway in their scratchpad
without the approach type. Once vectors for the approach have been issued utilizing the phraseology "vectors (approach type) runway (runway assignment) (airport)" has been
stated, the scratchpad shall be updated to reflect the approach type and runway utilizing the tables below.
| Approach Types |
|---|
| I | ILS |
| B | Localizer Backcourse |
| BK | Overhead Break |
| G | GPS/RNAV |
| L | Localizer |
| N | NDB |
| R | VOR/DME |
| V | Visual |
Runways shall be placed in the scratchpad in 2 digit form. Examples: an ILS approach to runway 36R would appear as "I6R". Visual to runway 7 would appear as "V07".
4.2 Altitude Assignments
All altitude assignments that are not an aircraft's cruise altitude shall conform to requirements under the TRACON/Center LOA Section 2 and Section 2.5 and be appropriate for their direction of flight.
4.3 Airspace Dimensions
The Orlando TRACON airspace is broken up into three areas. The Melbourne airspace area runs from surface up to, but not including, 5,500 ft MSL. The main body of the TRACON
runs from surface up to, but not including, 16,000 ft. MSL. The northern area around Daytona Beach runs from surface up to, but not including, 11,000 ft. MSL.
4.4 Split Operations
During normal operations, the TRACON controller staffing MCO_1_APP shall be responsible for all unstaffed airspace within the boundaries of
Orlando Approach from Delivery to Approach.
The order of sectors at Orlando TRACON to be opened are: Epcot, NASA,
then Daytona. At no time shall a controller open final approach before
opening any other approach position first. Final may only be opened once
Epcot is staffed.
5. Orlando Approach/Orlando Final Approach
The following is applicable at all times, with the exception of Handoff procedures when Final is not staffed.
5.1 Vectors
Aircraft are to be given vectors toward downwind, or crosswind when necessary, and assigned a runway and approach type prior to handoff with Final.
5.2 Handoff Procedures
TRACON controllers are to initiate an automated radar handoff when an aircraft is parallel of the departure end of the runway they are inbound for, or no less than 10nm from the base leg.
TRACON Controllers shall transfer communications to the final controller as soon as the automated radar handoff is complete and while the aircraft is still on the downwind leg or approaching the base leg. It is the responsibility of the Final
controller to sequence aircraft, turn them to base and then final.
5.3 Scratchpad Entries
TRACON controllers are to ensure they are in compliance with Orlando TRACON Intra-facility LOA Section 4.1 prior to initiating a radar handoff.
5.4 Altitude Assignments
Final controllers are responsible for setting temporary altitudes to reflect the aircraft's assigned altitude.
5.5 Simulteanous Approaches
Simultaneous Approaches to KMCO are authorized in the following runway pairs:
- 18R and 17R
- 18R and 17L
- 18L and 17R
- 18L
and 17L
- 36R and 35L
- 36R and 35R
Simultaneous operations involving an aircraft arriving in the west complex and an aircraft departing the west complex are NOT authorized.
6. Orlando Approach/Orlando Area Towers
The following applies only when both TRACON and the lower level positions apply with regards to handoff procedures.
6.1 Initial Departure Headings
| Initial Fix | 18L/R |
| 17L/R |
| 35L/R |
| 36L/R |
|
|---|
| CAMDT (CTY/KNOST) | 205 |
| 220 |
| 345 |
| 010 |
|
| FMYDT (PIE/RSW) | 205 |
| 220 |
| 345 |
| 010 |
|
| VALCA (VRB/MLB/LENDS*/ETECK*/HOBEE*) | 140 |
| 160 |
| 060 |
| 065 |
|
| JAG3 | 205 |
| 220 |
| 025 |
| 010 |
|
| MCOY9 | 140 |
| 160 |
| 025 |
| 010 |
|
* These waypoints are on the AR airways and used on rare occasion usually to avoid impeding weather to the north
6.2 Communications Handoff
Departing aircraft are to be transferred to the appropriate TRACON controller as soon as practical.
Arriving aircraft are to be transferred tower no later than 5 miles unless a short final is pre-coordinated.
6.3 Missed Approach Procedures
Unless assigned in the table below, aircraft are to instructed to fly runway heading and maintain 3,000 ft. MSL.
Missed Approach Assignments for KMCO:
| Runway | Turbojet Heading/Altitude | Turboprop Heading/Altitude |
|---|
| 18R/18L | 205/3000 MSL | 270/1500 MSL |
| 17R/17L | 090/3000 MSL | 090/1500 MSL |
| 36R/36L | 355/3000 MSL | 270/1500 MSL |
| 35R/35L | 090/3000 MSL | 090/1500 MSL |
All aircraft are to cross the departure end of the runway at or below 2,000 feet MSL and handoff the aircraft to the appropriate controller.
6.4 Departure Procedures
Calm wind runways for KMCO are 18R, 17R, and 17L for Arrivals, and 18L, 17R and 17L for Departures. Winds greater than 5 knots favoring the north shall constitute a change to north operations
at the discretion of the Local controller.
For Noise Abatement during night time operations, KMCO controllers shall utilize runways northern flow operations for Turbojet arrivals, and southern flow operations for departures
between the hours of 2300 and 0700 local if winds permit. When wind, weather, or other operations require northern departures, runways 35L and 35R shall be used for all turbojet departures
between the hours of 2300 and 0700 local. Turbojet departures during these times shall be assigned an initial departure heading of 060, with 35L's turn occurring at the middle marker.
For Noise Abatement during day time operations (0700 to 2300 local), when winds, weather and field conditions permit, runways 35L and 35R shall be used for all turbojet departures, and 35L, 35R, 36L, and 36R for all other aircraft departures.
6.5 VFR Traffic Pattern
Traffic conducting VFR Traffic Patterns within the TSA shall squawk VFR and remain on the tower's frequency. If an aircraft approaches the boundary
between the TSA and the Class B, Local controllers shall conduct a point out with the appropriate TRACON controller.
Aircraft departing the TSA VFR shall be assigned a discreet squawk code and be squawking the discreet squawk code prior to departing the TSA.
6.6 Tower Surface Area (TSA)
The Tower Surface Area is an area of the Class B that remains under the local controller's control. This airspace is defined as a 5nm ring around the airfield and spans
from surface up to but not including 3,000 feet MSL for KMCO, surface and up to, but not including 1,600 feet MSL for KORL, and surface and up to, but not including 1,500 feet at all other airfields.
All aircraft in this airspace must have radio contact with the local controller or an approved point out prior to entering the airspace from the appropriate controller.
6.7 Gate Stops
TRACON controllers can request Gate Stops for specific periods of time for aircraft departing at the TRACON's discretion. These shall be relayed utilizing appropriate communications methods to
the affected positions.
6.8 Releases
Local controllers shall request a release for an aircraft from the appropriate TRACON controller prior to the aircraft rolling on the runway. This release lasts for 3 minutes
and does not require a "rolling call" from the Local controller or a communications transfer notification. If, after 3 minutes, the aircraft has not departed, a new release shall be
obtained by the Local controller.
Phraseology for Releases are as follows:
Local: Epcot, Orlando Tower, Release.
Epcot: Epcot.
Local: Release, American 472 runway 36R.
Epcot: Released, (initials).
Local: (initals)
During releases, Approach may give climbout instructions that differ from the standards. This is done by "(instructions), released, (initials)." Instructions can include heading, altitude assignments, etc. Examples:
"Heading 160 at 3000. Released, AW.", "Heading 090 at 2 miles. Released, AW", etc.
During times of Blanket Releases at Orlando, The TRACON Controller may request rolling calls for aircraft taking off at Orlando, if this is the case a Rolling call may happen like this:
Local: Epcot, Orlando Tower, AAL252 Rolling 35L, Cross City.
Epcot: Tower, Epcot, Roger (Initials)
Local: (Initials)
6.9 Scratchpad
Prior to an aircraft departing, local controllers shall ensure scratchpad entries have been cleared.
6.10 Altitude Assignments in the Tower
Cab Controllers will give aircraft departing Orlando an initial altitude of 5,000 MSL in their clearance. All other IFR aircraft at satellite airports within the MCO Class B shall be assigned an altitude of no higher than 3,000 ft. MSL. VFR aircraft are to remain at or below 3,500 ft. MSL within the class B.
6.11 Daytona Beach (KDAB) VFR Departures
Aircraft departing VFR on runways 7L or 7R with their direction of flight being northbound shall be instructed to fly heading 030 after departure
to join the shoreline northbound. Aircraft departing runway 7L or 7R with their direction of flight being southbound shall be instructed to fly heading 110 after
departure to join the shoreline southbound. Runways 25L or 25R Northbound shall be assigned heading 290, Southbound 210. Runways 16 or 34 shall be assigned
runway heading.
A. Appendix
A1. Orlando TRACON Diagram
A2. Orlando Class B/C/D Diagram
A3. Jacksonville Enroute Low Sector Splits
When Sector 35 offline, Sector 35 is covered by Sector 34. When Sector 34 is offline, Sectors 35 and 34 are covered by Sector 33.
A4. South Ops Departure Transition Zone
A5. North Ops Departure Transition Zone
