¶ Orlando International Air Traffic Control Tower
¶ General Info
¶ Operational Positions
| Position | Callsign | Frequency | Symbol |
|---|---|---|---|
| Clearance Delivery | |||
| Orlando Clearance Delivery | MCO_DEL | 134.700 | 4O |
| Ramp Control (events only) | |||
| Orlando West Ramp | MCO_W_RMP | 134.300 | NA |
| Orlando East Ramp | MCO_E_RMP | 129.650 | NA |
| Terminal C Ramp | MCO_C_RMP | 122.275 | NA |
| Ground Control | |||
| Orlando Ground Control West | MCO_W_GND | 121.800 | 3O |
| Orlando Ground Control East | MCO_E_GND | 126.400 | 3H |
| Local Control | |||
| Orlando Local Control West | MCO_W_TWR | 124.300 | 3W |
| Orlando Local Control East | MCO_E_TWR | 118.450 | 3E |
Denotes primary position
¶ Clearance Delivery
| Orlando International SIDs | ||
|---|---|---|
| SID Name | Aircraft Type | Initial Altitude |
| CITR# | Prop/Turboprop | 2,000 |
| ORL# | Turbojet | 7,000 |
| DDANY# | Turbojet | Climb via SID |
| FATHE# | Turbojet | Climb via SID |
| JEEMY# | Turbojet | Climb via SID |
| MZULO# | Turbojet | Climb via SID |
| OSPRY# | Turbojet | Climb via SID |
| RDSOX# | Turbojet | Climb via SID |
- Orlando uses a combination of radar vector and RNAV SIDs for IFR departures.
- Aircraft using radar vector SIDs (CITR#, ORL#) must be assigned a DTA appropriate to the SID they are flying.
- Assign all prop/turboprop aircraft on the CITR# departure.
- Assign all turbojet aircraft not filed on an RNAV SID via the ORL# departure.
- Turbojets are preferred to use an RNAV departure procedure.
- The use of vTDLS is authorized and encouraged at Orlando International. Be sure to familiarize yourself with the appropriate departure runways for each SID before utilizing vTDLS.
Sattelite Radar DTA Diagram
- Assign the CITR# departure to all IFR prop/turboprop aircraft, with radar vectors to their first fix.
- Append an appropriate DTA from the Satellite DTA diagram to the first word of a pilot's route.
- Assign an initial altitude of 2,000.
| Common Sattelite Radar DTA Fixes | |
|---|---|
| DTA | Common Fixes |
| WORMS* | KIZER, CRG, OMN, SGJ, SSI |
| VIZTA | CTY, SZW, OCF, BULZI, HEVVN |
| FSHUN* | RSW, SRQ, CYY |
| KNEED | PIE, MCF, LAL |
| TPSTR | TRV, PBI, FLL, MLB, PHK |
| * denotes that DTA is also a fix | |
EXAMPLE FLIGHT PLAN: Aircraft filed on DDANY JIPOD CUUDA3 should have their flight plan converted to TPSTR DDANY JIPOD CUUDA3
PHRASEOLOGY: Cleared to (clearance limit), Citrus 1 departure, radar vectors DDANY, then as filed. Maintain 2,000, expect 8,000- 10 minutes after departure...
Departure Radar DTA Diagram
- Assign the ORL# departure to all IFR turbojet aircraft not filed on an RNAV SID, with radar vectors to their first fix.
- Append an appropriate DTA from the Departure DTA diagram to the first word of a pilot's route.
- Assign an initial altitude of 7,000.
- Assign all aircraft filed for the Tampa complex through the KNEED DTA (Sattelite Radar diagram) at or below 12,000. Assign turbojets on the ORL# departure.
| Common Departure Radar DTA Fixes | |
|---|---|
| DTA | Common Fixes |
| WORMS* | KIZER, CRG, OMN, SGJ, SSI |
| CAMAN | CTY, SZW, OCF, KNOST, BULZI, HEVVN, PATOY, BRUTS |
| FSHUN* | RSW, SRQ, CYY |
| ATLAS | MLB, TRV, PBI, FLL |
| MICKI | TAY, OTK |
| * denotes that DTA is also a fix | |
EXAMPLE FLIGHT PLAN: Aircraft filed on DDANY JIPOD CUUDA3 should have their flight plan converted to ATLAS DDANY JIPOD CUUDA3
PHRASEOLOGY: Cleared to (clearance limit), Orlando 7 departure, radar vectors DDANY, then as filed. Maintain 7,000, expect flight level 350- 10 minutes after departure...
MCO RNAV Departure Map
- Assign RNAV departures to turbojet aircraft as filed.
- Ensure that the transition on all RNAV departures match.
- Instruct aircraft to "climb via SID"
PHRASEOLOGY: Cleared to (clearance limit), FATHE3 departure, VIYAP transition, then as filed. Climb via sid...
Notice how "expect FLXXX- 10 minutes after departure was not included in this clearance. This is because it is listed on all RNAV charts and thus instructing an aircraft to "climb via SID" does not require us to state this in the clearance.
SOURCE: FAA JO 7110.65 4-3-2 DEPARTURE CLEARANCES
| Aircraft Type | Initial Altitude |
|---|---|
| Prop/Helicopter | VFR AOB 1,500 |
| Turboprop/Turbojet | VFR AOB 2,000 |
- KMCO is a Class B airport. All VFR aircraft require an explicit clearance into the airspace, must remain in two-way radio communications with ATC, and must have a discrete beacon code whilst operating in the airspace.
- Assign aircraft an initial altitude using the chart provided.
PHRASEOLOGY: Cleared out/through of the Orlando Class B airspace, maintain VFR at or below 1,500, departure frequency 124.800, squawk 1234.
¶ Ground Control
¶ General Info & Responsibilities
- Ground Control is responsible for all taxiways east of runway 18L/36R and west of 17R/35L, as well as taxiways west of runway 18R/36L (west ramp).
- Ground Control West is responsible for the west ramp and all taxiways west of the bridges on taxiways J, E, and F. Ground Control East is responsible for taxiways east of the bridges on taxiways J, E, and F.
- Ensure pilots have the current ATIS prior to contacting Local Control.
- Advise local control of all intersection departures.
MCO Ground Split
¶ Split Ground Procedures
- GCW shall deliver aircraft east on taxiway E. GCW shall instruct aircraft to hold short at taxiway E4 and contact GCE.
- During north operations, GCW shall deliver aircraft eastbound on taxiway J. GCW shall instruct aircraft to hold short at J3 and contact GCE at the bridge.
- During south operations, GCE shall deliver aircraft westbown on taxiway J. GCW shall instruct aircraft to hold short at J2 and contact GCW at the bridge.
¶ Operation Specific Info
Select Airport Operations
¶ Runway Assignments
| West Complex (36R) | East Complex (35L) |
|---|---|
| OSPRY# | DDANY# |
| RDSOX# | FATHE# |
| FSHUN# | JEEMY# |
| FSHUN | MZULO# |
| MICKI | WORMS |
| CAMAN | ATLAS |
| KNEED | CUSSR |
| VIZTA | TPSTR |
- Assign aircraft the following runways based on their DTA or RNAV SID.
- All aircraft on the west ramp are automatically authorized to use runway 36L.
¶ Taxi Flow
- Taxiways C & G (inner taxiways) shall be utilized one-way south (towards the runway thresholds).
- Taxiways B & H (outer taxiways) shall be utilized one-way north (away from the runway thresholds).
- Taxiway E is one-way eastbound.
- Taxiway F is one-way westbound.
- Taxiway J is one-way eastboard during split ground procedures.
MCO Taxi Flow - North Ops
¶ Runway Assignments
| West Complex (18L) | East Complex (17R) |
|---|---|
| OSPRY# | DDANY# |
| RDSOX# | FATHE# |
| JEEMY# | MZULO# |
| FSHUN# | MICKI |
| FSHUN | WORMS |
| CAMAN | ATLAS |
| KNEED | CUSSR |
| VIZTA | TPSTR |
- Assign aircraft the following runways based on their DTA or RNAV SID.
- All aircraft on the west ramp are automatically authorized to use runway 18R.
¶ Taxi Flow
- Taxiways C & G (inner taxiways) shall be utilized one-way north (towards the runway thresholds).
- Taxiways B & H (outer taxiways) shall be utilized one-way south (away from the runway thresholds).
- Taxiway E is one-way eastbound.
- Taxiway F is one-way westbound.
- Taxiway J is one-way westbound during split ground procedures.
MCO Taxi Flow - Sorth Ops
¶ Tower
- Orlando Tower uses RNAV off the Ground (ROTG) procedures and simultaneous parallel departures & arrivals to increase airport efficiency.
- Other non-RNAV procedures still apply similar principles to maintain airport efficiency.
¶ Area of Juristiction & Responsibilities
Local Control Airspace
- Local Control is responsible for a 2nm by 2nm box from SFC-2000.
- Local Control West (LCW) is responsible for runways 18R/36L, 18L/36R, & all taxiways between both runways.
- Local Control East (LCE) is responsible for runways 17R/35L, 17L/35R, the Terminal Top Heliport & all taxiways between both runways.
- Local Control is reponsible for all runway crossings. Local Control should not authorize runway crossings to GC.
¶ Runway Selection
- South operation is the calm wind configuration.
- Should the wind velocity exceed three knots, operations shall be selected based on which configuation allows the greatest headwind component to aircraft.
¶ Line Up and Wait
LUAW is authorized at MCO with the following caveats:
- Do not use LUAW from an intersection between sunset and sunrise.
- Do not authorize multiple aircraft to LUAW on the same runway.
Due to the ASDE-X available at MCO, LC may issue landing clearances if LUAW procedures are in use.
- The minimum ceilings and visibility for these operations are 800ft/2sm.
- Provide traffic information to aircraft recieving landing clearances while using LUAW.
¶ Departure Fixes & Instructions
- Assign all aircraft using ROTG procedures (RNAV SIDs) the appropriate RNAV fix for their SID and departure runway. Assign all other aircraft the appropriate departure heading.
- West Complex turbojet departures are limited in that they may operate simultaneously only with aircraft arriving Runways 17L or 35R. LW must ensure appropriate separation from aircraft arriving Runways 17R/35L
MCO North Departure Fixes
| Runway | SID / DTA | Fix / HDG |
|---|---|---|
| 36L | RDSOX, OSPRY, FSHUN, JEEMY, FATHE, MICKI, WORMS, CAMAN, TPA COMPLEX | KYOTE / H010 |
| 36R | RDSOX, OSPRY, FSHUN, JEEMY, FATHE, MICKI, WORMS, CAMAN, TPA COMPLEX | FACTS / H010 |
| 36L/36R | CITR, ALL VFR | H270 |
| ALL | MZULO, DANNY, TPSTR, ATLAS | GOHOM / H040 |
| 35L/35R | RDSOX, OSPRY, FSHUN, TPA COMPLEX | SAWZZ / H355 |
| 35L/35R | JEEMY, FATHE, MICKI, WORMS | JWOLF / H040 |
| 35L/35R | CITR, ALL VFR | H090 |
MCO South Departure Fixes
| Runway | SID / DTA | Fix / HDG |
|---|---|---|
| ALL | FSHUN | BAAIT |
| ALL | RDSOX, OSPRY | VILNS |
| ALL | MZULO, DDANY | KAAPE |
| 17L/17R | JEEMY, FATHE | KAAPE |
| 17L/17R | WORMS, ATLAS, TPSTR | H160 |
| 17L/17R | MICKI, CAMAN, FSHUN DTA, TPA COMPLEX | H220 |
| 17L/17R | CITR, ALL VFR | H090 |
| 18L/18R | JEEMY, FATHE | VILNS |
| 18L/18R | WORMS, ATLAS, TPSTR | H150 |
| 18L/18R | MICKI, CAMAN, FSHUN DTA, TPA COMPLEX | H205 |
| 18L/18R | CITR, ALL VFR | H270 |
¶ Missed Approaches
| Complex | Heading | Altitude |
|---|---|---|
| West | 270 | 3,000 |
| East | 090 |
- For go-arounds/missed approaches, LC shall issue heading 270 if the aircraft is on the west complex and heading 090 if the aircraft is on the east complex. IFR aircraft should be assigned 3,000 feet.
- LC should coordinate with F11 and coordinate with the appropriate controller.
¶ Radar Tower
¶ Overview
- Orlando Intl. has a certified tower radar display (CTRD). This means that LC has the ability to radar identify and track aircraft using the STARS display.
- Aircraft inbound to MCO shall be monitored using a STARs display utilizing the “quick look” functionality. This can be achieved by typing F7 Q ALL. It should display as "FQ ALL" before pressing enter.
¶ Radar Procedures
- LC shall not track departures bound for departure control.
- LC shall track VFR departures intending to depart the class bravo airspace at or below 900 feet (typically helicopters).
- LC shall track aircraft in the traffic pattern
¶ Midnight Operatons
- While not required to be followed, midnight operations can be used at the discretion of the controller and should be coordinated as such.
- Midnight operations are authorized between 2300-0700 (11pm-7am) local time.
- Utilize north operations during midnight operations unless the tailwind component exceeds 10 knots.
- Assign all turbojets heading 060.
| Turbojet/HP Headings | |
|---|---|
| Complex | Heading |
| ALL | 060 |
| Turbojet/HP Headings | |
|---|---|
| Complex | Heading |
| West | 190 |
| East | 175 |
- Assign turbojets and high performance turboprops based on the table.