Orlando International ATCT: Difference between revisions

From ZJX ARTCC SOPs
Jump to navigation Jump to search
Line 448: Line 448:


=== Go Around/ Unplanned Missed Approaches ===
=== Go Around/ Unplanned Missed Approaches ===
East Operations: LC shall assign a heading of 070 and 2,000 feet.<br>
<ul><li>LC shall assign IFR aircraft 3,000 feet. West Complex will issue a heading of 270. East Complex will issue a heading of 090.</li>
West Operations: LC shall assign a heading of 320 and 2,000 feet.<br>
<li> 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.
<B>LC must verbally coordinate with departure prior to frequency change.</b><br>
 
=== Land and Hold Short ===
=== Land and Hold Short ===
N/A
N/A

Revision as of 08:28, 21 June 2023

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

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
This order is distributed to all Jacksonville ARTCC personnel.

Orlando International Airport via Google Maps


Operational Positions

MCO ATCT
Position Radio Name Callsign Relief Callsign Symbol Frequency
Clearance Delivery Orlando Clearance Delivery MCO_DEL MCO_1_DEL 4OD 134.700
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.


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

Pre Departure Clearances are authorized at this airport.

It is advisable that ALL controllers issue PDCs for departures for KMCO INTL ATCT
PDC Commands
For Pilot Navigation 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}

IFR Departures

Planned/Amended Routing

RNAV Departure: All Aircraft shall be "cleared via {Departure} {Fix} Transition then as filed" unless a route amendment is necessary.
Non-Rnav Jets: Aircraft shall be "cleared via ORL# departure radar vector {fix} then as filed" unless a route amendment is necessary.
Non-Rnav Turboprops/props: Aircraft shall be "cleared via CITR# departure radar vector {fix} then as filed" unless a route amendment is necessary.

Departures

  • CITR= (Turboprops and Props Only)/li>
  • 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)
  • ORL
  • OSPRY= West and Southwest Bound (Turbojets Only)
  • RDSOX= West Bound (Turbojets Only)

Note: Scratchpad entry shall be entered for all departures out of Orlando. The scratchpad should contain the first 3 letters of the departures except when using the ORL/CITR. It shall then contain the first three letters 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.

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.

Orlando Departure DTA (ORLA#) Turbojet/Turboprop Aircraft
Direction DTA Associated Fixes
West CAMAN CTY, SZW, OCF, KNOST, BULZI, HEVVN, PATOY, BRUTS
Southwest KLMAN RSW, SRQ, CYY
Southeast ATLAS MLB, TRV, PBI, FLL
Northeast WORMS CRG, OMN, SGJ, SSI
Northwest MICKI TAY, OTK

Citrus Departure DTA (CITR#) Piston Aircraft
Direction DTA Associated Fixes
Northwest CAMAN CTY, SZW, OCF, BULZI, HEVVN
Southwest KLMAN RSW, SRQ, CYY
Southwest KNEED PIE, MCF, LAL
Southeast TPSTR TRV, PBI, FLL, MLB, PHK
North WORMS TAY, CRG, OMN, SGJ, SSI



Aircraft with none of the above 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. a. Example: Aircraft filed directly to PAM (not listed) shall be routed through CAMAN.

VFR Departures

Clearance

VFR Aircraft do need explicit clearance to "into" or "out of" the airspace.
All VFR remaining in the pattern will require coordination with the tower and will be directed to contact when ready for taxi.

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.

Departure Runway Assignments
West Complex (18L, 18R, 36L, 36R) East Complex (17L, 17R, 35L, 35R)
OSPRI#
FSHUN#
RDSOX#
JEEMY#
MICKI
KLMAN
CAMAN
DDANY#
FATHE#
MZULO#
WORMS
ATLAS
TPSTR

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.

Split Ground Procedure on Taxiway E and F
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.

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.

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.

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

ORLA# Departure Headings - North Ops
DTA Runways Heading
CAMAN North/South All North Runways 345-010
ATLAS All North Runways 060
KLMAN All North Runways 345-010
WORMS/MICKI 35s
36s
025-035
010


ORLA# Departure Headings - South Ops
DTA Runways Heading
CAMAN North/South 17s
18s
220
205
ATLAS 17s
18s
160
140
KLMAN 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

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.

    Traffic Pattern

    The VFR pattern will be at or below 1,500 feet. Runway 8 and 32 will utilize left hand pattern. Runway 14 and 26 will utilize right hand pattern.

    Visual Tower

    Jacksonville ATCT is a visual/VFR tower and shall not initiate or accept any radar handoffs and shall not initiate control/start track on any target.