Orlando International ATCT
Table of Updates
| Date | Revision | Items Revised |
|---|---|---|
| 12 May 2023 | A | Turboprops shall receive the Citrus# Departure |
| 21 June 2023 | B | Removal LOAs, Added LUAW Section, Organization, Fixed Tower Callsign, Fixed Runway Assignment. |
| 8 July 2023 | C | DTA Update |
| 1 August 2023 | D | Taxiway Usage for B11 and E1. |
| 28 August 2023 | E | Updated: Scratchpad Entries, PDC Instructions, Taxi Instructions to and from South Terminal. |
| 4 March 2024 | F | Scratchpad and DTA data updated in delivery section. |
| 4 April 2024 | G | Updated Assigned Runway for JEEMY#, East Complex |
| 4 May 2024 | H | Updated Assigned Runway for JEEMY# based on OPS |
| 7 October 2024 | I | Ramp Control Instructions |
Area Information
| ICAO Code | Airport Name | Airspace | IFR Beacon Codes | VFR Beacon Codes |
|---|---|---|---|---|
| KMCO | Orlando International Airport | B | 0701-0777 | 0701-0777 |
| Purpose This document prescribes the procedures to be utilized for providing air traffic control services at the Orlando Air Traffic Control Tower (MCO ATCT). The procedures described herein are supplemental to the Jacksonville ARTCC Facility Operating Guidelines and FAA Order JO 7110.65, as well as any published FAA guidelines or procedures. Distribution |
Operational Positions
| Position | Radio Name | Callsign | Relief Callsign | Symbol | Frequency |
|---|---|---|---|---|---|
| Clearance Delivery | Orlando Clearance Delivery | MCO_DEL | MCO_1_DEL | 4OD | 134.700 |
| West Ramp | Orlando Ramp | MCO_W_RMP | *Delivery AND Ground must be online to open during non events* | 134.300 | |
| East Ramp | Orlando Ramp | MCO_E_RMP | *Events ONLY* | 129.650 | |
| Terminal C Ramp | Orlando Ramp | MCO_C_RMP | *Events ONLY* | 122.775 | |
| East Ground | Orlando Ground | MCO_E_GND | MCO_E1_GND | 4EG | 126.400 |
| West Ground | Orlando Ground | MCO_W_GND | MCO_W1_GND | 4WG | 121.800 |
| West Tower | Orlando Tower | MCO_W_TWR | MCO_W1_TWR | 4WT | 124.300 |
| East Tower | Orlando Tower | MCO_E_TWR | MCO_E1_TWR | 4ET | 118.450 |
Sector in Red is the primary sector.
Ramp Control
Ramp Control Responsibilities
The Ramp Controller Shall:
- Control movements in the non-movement area to avoid conflicts with arriving and departing aircraft.
Departing traffic will be guided to push into the most efficient position. Once ready to taxi, they should be sent to an exit point and hold short of the movement area. At this time transfer of communications shall be made to the appropriate ground controller.
Example - "Ramp, DAL123 ready to push."
"DAL123, Orlando Ramp, push tail facing north, advise ready to taxi"
"Ramp, DAL123 ready to taxi"
"DAL123, taxi to H3 hold short of G, contact ground 126.4"
Inbound aircraft will not be given a ramp "entry" point from ground, but rather a nearby parallel taxiway. This should be coordinated with ground control. When an aircraft calls you inbound, you will issue the "entry" taxiway and further instructions.
Example - "Ramp, DAL124 on H inbound for gate 73". "DAL124, ramp, enter at H4 and to the gate when able"
Clearance Delivery
Clearance Delivery Responsibilities
The Clearance Delivery Controller Must:
- Formulate and issue all IFR and VFR clearances to aircraft departing this field.
- Review proposed flight plan information for accuracy and amend routings and altitudes, as necessary, in accordance with this SOP.
- Enter amendments to flight plans into the controller client as required and advise the pilot what those amendments are.
- Issue clearances or route changes to aircraft, as required complying with traffic management initiatives and/or weather avoidance.
- Forward and await a response on all non-standard routing requests to the affected facilities.
- During Events: Do not change routes or proposal times for aircraft participating in Traffic Management programs without prior coordination with the controller in charge.
Pre-Departure Clearances
The TDLS (Tower Data-Link Services) system is available for use at KMCO though the vNAS. If it is not working or if there are unforeseen issues, the ALIAS FILE may be used as below.
It is advisable that ALL controllers issue PDCs for departures for KMCO INTL ATCT
PDC Commands
For All departures EXCEPT from Terminal Charlie
For RNAV SIDS
If Orlando Approach or Jacksonville Center is Online: .pdcr {Departure Runway} {Dep Frequency ID}
If Orlando Approach and Jacksonville Center is Offline: .pdcru {Departure Runway}
For Radar Vector SIDS
If Orlando Approach or Jacksonville Center is Online: .pdco {Departure Runway} {Dep Frequency ID}
If Orlando Approach and Jacksonville Center is Offline: .pdcou {Departure Runway}
For All departures from Terminal Charlie (South Terminal)
For RNAV SIDS
If Orlando Approach or Jacksonville Center is Online: .pdcrc {Departure Runway} {Dep Frequency ID}
If Orlando Approach and Jacksonville Center is Offline: .pdcruc {Departure Runway}
For Radar Vector SIDS
If Orlando Approach or Jacksonville Center is Online: .pdcoc {Departure Runway} {Dep Frequency ID}
If Orlando Approach and Jacksonville Center is Offline: .pdcouc {Departure Runway}
IFR Departures
Planned/Amended Routing
RNAV Departure: All Aircraft shall be "cleared {Departure} {Fix} Transition then as filed" unless a route amendment is necessary.
Non-RNAV Jets: Aircraft shall be "cleared ORL# departure, then as filed" unless a route amendment is necessary.
Non-RNAV Turboprops/props: Aircraft shall be "cleared CITR# departure, then as filed" unless a route amendment is necessary.
Departures
-
RADAR VECTOR SIDs
- CITR= (Turboprops and Props Only)
- ORL= (Turbojets Only) RNAV SIDs
- DDANY= Southeast Bound (Turbojets Only)
- FATHE= North Bound (Turbojets Only)
- FSHUN= Southwest Bound (Turbojets and Turboprops Only)
- JEEMY= North Bound (Turbojets Only)
- MZULO= Northeast Bound (Turbojets Only)
- OSPRY= West and Southwest Bound (Turbojets Only)
- RDSOX= West Bound (Turbojets Only)
Note: Departure scratchpads should be entered automatically through the vNAS system. The scratchpad should contain the first 3 letters of the departures except when using the ORL/CITR SIDs. It shall then contain the first letter of the Departure Transition Area. Flight plan routing information for the ORLA# and CITR# SID SHALL include the DTA in place of the SID name followed by the remainder of the route.
What is a scratchpad? A scratchpad is abbreviation to provide information to be viewed in the data tag of the aircraft. For aircraft at KMCO, it is used in the delivery phase to abbreviate the SID or the DTA (Departure Transition Area) to be flown. The scratchpad will be visible on the ASDE-X and departure radar data tag.
Scratchpad entry shall be entered for all departures out of Orlando. Departure scratchpads will be entered automatically through the vNAS system as long as the correct syntax is available in the routing. The scratchpad should contain the first 3 letters of the departures except when using the ORL/CITR.
For all other departures (ORL#/CITR#) the following DTA Scratchpad entry shall be entered:
- VIZTA - V
- KNEED - K
- WORMS - W
- TPSTR - T
- CAMAN NORTH - C
- CAMAN SOUTH - C
- FSHUN - F
- ATLAS - A
- CUSSR - R
- MICKI - M
Assigned Altitudes
All Pilot Navigational SID Departures shall be instructed to "climb via SID"
Pilots on the ORL# departure shall be instructed to "maintain 7,000" to expect filed cruise altitude (if higher) 10 minutes after departure.
Pilots on the CITR# departure shall be instructed to "maintain 2,000" to expect filed cruise altitude (if higher) 10 minutes after departure.
Departure Frequency
The Primary Departure Frequency is MCO_E_APP on 124.800.
Squawk Assignment
All IFR Squawk codes will be auto-assigned by the controller client.
It should assign a code between 0701-0777. Controllers shall not change the auto-assigned code if a code between 0701-0777 is not assigned.
1. Turbojet aircraft not able to fly an RNAV departure procedure shall be assigned the ORLA# departure procedure (SID). The aircraft must depart the F11 through a valid departure radar DTA (see below). Piston aircraft shall always be assigned the CITR# departure procedure (SID). The aircraft must depart the F11 through a valid satellite radar DTA (see below).
2. Flight plan routing information for the ORLA# and CITR# SID SHALL include the DTA in place of the SID name followed by the remainder of the route. The DTA name implies the departure procedure. (See Diagram 1). Aircraft with none of the below as their first fixes shall use the departure gate closest to their first fix as long as the fix is outside of the F11 airspace.
Example: Aircraft filed directly to PAM (not listed) shall be routed through the CAMAN DTA.
3. DTA DIAGRAMS
| Direction | DTA | Associated Fixes |
|---|---|---|
| West | CAMAN | CTY, SZW, OCF, KNOST, BULZI, HEVVN, PATOY, BRUTS |
| Southwest | FSHUN | RSW, SRQ, CYY |
| Southeast | ATLAS | MLB, TRV, PBI, FLL |
| Northeast | WORMS | CRG, OMN, SGJ, SSI |
| Northwest | MICKI | TAY, OTK |
| Direction | DTA | Associated Fixes |
|---|---|---|
| Northwest | VIZTA | CTY, SZW, OCF, BULZI, HEVVN |
| Southwest | FSHUN | RSW, SRQ, CYY |
| Southwest | KNEED | PIE, MCF, LAL |
| Southeast | TPSTR | TRV, PBI, FLL, MLB, PHK |
| North | WORMS | TAY, CRG, OMN, SGJ, SSI |
DIAGRAM 1
VFR Departures
Clearance
VFR Aircraft do need explicit clearance "into" or "out of" the airspace.
All VFR remaining in the pattern will require coordination with the tower.
Assigned Altitudes
Not Remaining in the Pattern
Jet: VFR aircraft shall be instructed to maintain VFR at or below 2,000.
Turboprops: VFR aircraft shall be instructed to maintain VFR at or below 2,000.
Props: VFR aircraft shall be instructed to maintain VFR at or below 1,500.
Departure Frequency
Aircraft not remaining in the pattern shall be given the Departure Frequency is MCO_E_APP on 124.800.
Aircraft remaining in the pattern shall not be given a departure frequency.
Squawk Assignment
VFR Squawk codes shall be assigned by the controller client using the assign squawk feature in their controller client for all traffic.
Ground
General Information
Ground Control Responsibilities
The Ground Controller is responsible for the movement of vehicles and aircraft on the airport movement areas except for the active runway(s)
ATIS
Ground control shall confirm all pilots have the current ATIS code PRIOR to commencing taxi to the active runway. This can be achieved by requesting the pilot "state the current ATIS code". The ATIS is the responsibility of the tower controller.
Active Runway Operations
Except for runway crossings, Ground Control must transfer communication to Local Control if a vehicle/aircraft is to operate on a runway. Coordination for all runway crossings must be accomplished by requesting permission from local control by stating "(Number of Aircraft) to cross Runway (#) at Taxiway (Letter). Once approved and crossing has been granted and the crossing has been observed, ground control must state to local control "Runway (#) crossing complete"
Intersection Departures
Ground Control must advise local control of all intersection departures verbally.
Opposite Direction Departures
Ground Control must coordinate and obtain approval from Local Control, prior to taxiing an aircraft to a runway for an opposite-direction departure.
Pushback and Startup
Push back into a controlled area: Aircraft shall be instructed: "Push and Start Approved, tail facing (direction)." The direction should keep the aircraft pointed in the direction the aircraft will taxi.
Push back will not enter a controlled area: Aircraft shall be instructed: "Push and start at pilot's discretion."
Runway Assignments
GC shall taxi aircraft to the appropriate runway for their direction of flight. GC shall use Departure Runway Assignments at all times.
Note: Aircraft parked at the west ramp (FBO, Cargo Areas) can be assigned runway 18R/36L for departure as long as coordinated with Local Control and F11 Tracon if they are a cross-complex departure.
| West Complex (36L, 36R) | East Complex (35L, 35R) |
|---|---|
| OSPRI# FSHUN# RDSOX# MICKI FSHUN CAMAN |
DDANY# FATHE# JEEMY# MZULO# WORMS ATLAS |
| West Complex (18L, 18R) | East Complex (17L, 17R) |
|---|---|
| OSPRI# FSHUN# JEEMY# RDSOX# MICKI FSHUN CAMAN |
DDANY# FATHE# MZULO# WORMS ATLAS |
Split Ground Procedures
Taxi aircraft via taxiways E and F in accordance and instruct the pilot to change ground control frequencies at the bridge.
Taxi aircraft via taxiway J in accordance with the following:
a. During MCO South Operations… Taxiway J is one way westbound between J2 and J3. GC East must instruct aircraft to hold short of J2 and contact GC West at the bridge.
b. During MCO North Operations… Taxiway J is one way eastbound between J2 and J3. GC West must instruct aircraft to hold short of J3 and contact GC East at the bridge.
| Network Callsign | Taxi Route | Hold Short Point |
|---|---|---|
| MCO_W_GND | East on E | E4 |
| MCO_E_GND | West on F | E2 |
Taxi Operations
GC shall only taxi aircraft east on taxiway E.
GC shall only taxi aircraft west on taxiway F.
GC shall utilize taxiway H and taxiway B for arrival aircraft.
GC shall utilize taxiway C and taxiway G for departing aircraft.
South Terminal (Terminal C)
Inbound aircraft shall enter Terminal C via B and based on gate information into B11 or B12.
The Charlie North Ramp is counterclockwise flow B11 out to B9.
Aircraft pushing out of gates 240, 242 and 244 (Charlie Ramp West) shall be advised to hold at Spot 2 (Transition Control Point) and call for taxi. Aircraft pushing out of Charlie North Ramp shall be advised to hold at Spot 3 (Transition Control Point) and call for taxi.
Aircraft departing the west complex shall taxi via B9 C.
Aircraft departing the east complex shall taxi via E1 E.
Transfer of Communication
Departing aircraft shall be instructed to contact the local control frequency upon or slightly before holding short the runway for departure. Local control has the option to have the pilot "monitor" the frequency. If a pilot is going to monitor, ground control must send a private message via the controller client of the aircraft with their callsign and runway.
Ramp Control Coordination
If Ramp Control is online, coordination shall be made between Ramp and Ground control to expedite movement into the ramp.
Tower
Active Runway Selection
The active runway shall be determined based on wind and known factors that may affect the safety of takeoff/landing operations.
South configuration is designated as the calm wind runway.
7110.65Z Runway Selection
Area of responsibility
LC has responsibility for a two-mile by two-mile box from surface up to and including 2,000 MSL. LC has responsibility for all taxiways between parallel runways. LC West is responsible for arrivals and departures on Runway 18L/R & 36L/R, all taxiways between Runway 18L/R & 36 L/R. LC East is responsible for arrivals and departures on Runway 17L/R & 35R/L and all taxiways between Runway 17L/R & 35R/L
Arrival Procedures
LC shall be responsible for separation of all arrival aircraft that have been handed off by TRACON from all departing aircraft still under LC jurisdiction
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the TRACON. Practice Instrument Approaches shall assign runway heading and maintain 3,000 feet. Departure frequency as assigned by approach control.
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles from the runway.
Simultaneous Approaches
Runways 36L/36R and Runways 18R/18L may not be used for simultaneous instrument approaches.
The ATIS shall indicate at all times “Caution simultaneous approaches in use” prior to stating the arrival runways.
Automatic Terminal Information Service
LC shall manage the ATIS
The ATIS shall be on: DEP 120.525, ARR 121.250
Automatic Releases
LC is authorized automatic releases from the TRACON controller so long as the aircraft departs on the pre-coordinated active departing runway(s) on approved departure headings
In order for automatic releases to be authorized, procedures in this document shall be followed.
Departure releases must be obtained if automatic releases are suspended by TRACON.
Departure Procedures
IFR departures will be automatically released if the aircraft departs IAW with procedures including headings and altitudes outlined in this document.
VFR departures will be automatically released if the departure heading and altitude matches approved headings and altitudes.
Aircraft going to the same departure gate or on the same RNAV SID shall be separated by 4nm off the runway.
WORMS DTA Departures - Caution should be exercised with the JEEMY and FATHE SIDS. These SIDS exit the WORMS gate in parallel with 6nm separation. JEEMY is on the west side, FATHE on the east. JEEMY departures from the west complex and FATHE departures from the east complex may depart simultaneously.
Departure Headings
| DTA | Runways | Heading |
|---|---|---|
| CAMAN North/South | All North Runways | 345-010 |
| ATLAS | All North Runways | 060 |
| FSHUN | All North Runways | 345-010 |
| WORMS/MICKI | 35s 36s |
025-035 010 |
| DTA | Runways | Heading |
|---|---|---|
| CAMAN North/South | 17s 18s |
220 205 |
| ATLAS | 17s 18s |
160 140 |
| FSHUN | 17s 18s |
220 205 |
| WORMS/MICKI | 17s 18s |
160 140 |
Citrus Departure Heading
Aircraft departing the west complex shall depart on a heading 270. Aircraft departing the east complex shall depart on a heading 090. Cross Complex VFR traffic shall be coordinated with TRACON.
RNAV Departure Fixes
| SID | 17L | 17R | 18L | 18R | 35L | 35R | 36L | 36R |
|---|---|---|---|---|---|---|---|---|
| FATHE# | KAAPE | KAAPE | VILNS | VILNS | JWOLF | JWOLF | KYOTE | FACTS |
| JEEMY# | KAAPE | KAAPE | VILNS | VILNS | JWOLF | JWOLF | KYOTE | FACTS |
| RDSOX# | VILNS | VILNS | VILNS | VILNS | SAWZZ | SAWZZ | KYOTE | FACTS |
| OSPRI# | VILNS | VILNS | VILNS | VILNS | SAWZZ | SAWZZ | KYOTE | FACTS |
| FSHUN# | BAAIT | BAAIT | BAAIT | BAAIT | SAWZZ | SAWZZ | KYOTE | FACTS |
| MZULO# | KAAPE | KAAPE | KAAPE | KAAPE | GOHOM | GOHOM | GOHOM | GOHOM |
| DDANY# | KAAPE | KAAPE | KAAPE | KAAPE | GOHOM | GOHOM | GOHOM | GOHOM |
Go Around/ Unplanned Missed Approaches
LC shall assign IFR aircraft 3,000 feet. West Complex will issue a heading of 270. East Complex will issue a heading of 090.
LC must verbally coordinate with departure prior to frequency change. Radar handoff, controller coordination and voice handoffs should be initiated as soon as practical to the appropriate final controller.
Land and Hold Short
N/A
Line Up and Wait
Line up and wait is authorized at this field only in VMC Conditions. LUAW departures from an intersection are only authorized between sunrise and sunset.
Radar Tower
Inbound aircraft to MCO will be monitored on the limited radar. Local shall "Quick Look" (See STARS Documentation) the adjacent sector for data tag visualization. F11 will not directly hand off the tag but will transfer communications. Aircraft that are missed approach should be communicated to the final controller as the aircraft could need transfer to another F11 sector. LC will not track departures destined for departure control. LC shall radar identify VFR aircraft and track the aircraft until they are outside of the Orlando Class Bravo airspace, or hand off to F11 for flight following if departing the pattern. F11 releases control for VFR aircraft tracked by MCO tower through the airspace within a 5NM radius of MCO as long as the aircraft intends to depart Bravo airspace below 900ft. This usually only applies to helicopter traffic. VFR aircrafts radar services must be terminated once they leave the Bravo airspace.
*note - If JAX_CTR is covering F11(ERAM Client), the scratchpad will not be visible in STARS.
Traffic Pattern
The VFR pattern will be at or below 1,500 feet. Runway 18R (right traffic) or Runway 36L (left traffic) shall be utilized for closed traffic. All aircraft in the pattern must receive a discrete beacon code.