Orlando International ATCT: Difference between revisions

From ZJX ARTCC SOPs
Jump to navigation Jump to search
No edit summary
Line 12: Line 12:
|21 June 2023
|21 June 2023
|B
|B
|Added PDC Authorized, Removal LOAs, Added LUAW Section, Organization
|Removal LOAs, Added LUAW Section, Organization
|}
|}
== [[Area Information]] ==
== [[Area Information]] ==
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
Line 24: Line 23:
!VFR Beacon Codes
!VFR Beacon Codes
|-
|-
|KCAE
|KMCO
|Columbia Metro Airport
|Orlando International Airport
|C
|B
|1601-1677
|0701-0777
|1601-1677
|0701-0777
|}
|}
<br>
<br>
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|-
|-
| style="width: 60%;" |<b>Purpose</b><br>This document prescribes the procedures to be utilized for providing air traffic control services at the Columbia Metro Air Traffic Control Tower (CAE ATCT) and TRACON. 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.<br><br>
| style="width: 60%;" |<b>Purpose</b><br>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.<br><br>
<b>Distribution</b><br>
<b>Distribution</b><br>
This order is distributed to all Jacksonville ARTCC personnel.<br>
This order is distributed to all Jacksonville ARTCC personnel.<br>
| style="width: 30%;" |[[File:CAEGOOGLE.JPG|200px|thumb|left|Columbia Metro Airport via Google Maps]]
| style="width: 30%;" |[[File:MCO.JPG|200px|thumb|left|Orlando International Airport via Google Maps]]
|}
|}


== [[Operational Positions]] ==
== [[Operational Positions]] ==
<tabs>
<tab name="CAE ATCT">
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+
|+MCO ATCT
!Position
!Position
!Radio Name
!Radio Name
Line 50: Line 49:
!Symbol
!Symbol
!Frequency
!Frequency
|-
|- style="color: RED;"
|Clearance Delivery
|Clearance Delivery
|Columbia Clearance Delivery
|Orlando Clearance Delivery
|CAE_DEL
|MCO_DEL
|CAE_1_DEL
|MCO_1_DEL
|7CD
|4OD
|119.750
|134.700
|-
|-
|Ground
|East Ground
|Columbia Ground
|Orlando Ground
|CAE_GND
|MCO_E_GND
|CAE_1_GND
|MCO_E1_GND
|7CG
|4EG
|121.900
|126.400
|-
|- style="color: RED;"
|Tower
|West Ground
|Columbia Tower
|Orlando Ground
|CAE_TWR
|MCO_W_GND
|CAE_1_TWR
|MCO_W1_GND
|7CT
|4WG
|119.500
|121.800
|}
</tab>
<tab name="CAE TRACON">
{| class="wikitable" style="width: 100%;"
|+CAE TRACON
!Position
!Sector Name
!Callsign
!Relief Callsign
!Symbol
!Frequency
|-
|-
|RN
|West Tower
|Radar North
|Orlando Tower
|CAE_N_APP
|MCO_W_TWR
|CAE_1N_APP
|MCO_W1_TWR
|7RN
|4WT
|133.400
|124.300
|- style="color: RED;"
|- style="color: RED;"
|RS
|East Tower
|Radar South
|Orlando Tower
|CAE_S_APP
|MCO_E_TWR
|CAE_1S_APP
|MCO_E1_TWR
|7RS
|4ET
|124.150
|118.450
|-
|RF
|Radar Final
|CAE_F_APP
|CAE_1F_APP
|7RF
|128.500
|}
|}
<span style='color:red;'>Sector in Red is the primary sector.</span>
<span style='color:red;'>Sector in Red is the primary sector.</span>
</tab>
 
</tabs>


== [[Clearance Delivery]] ==
== [[Clearance Delivery]] ==
=== General Information ===
===Clearance Delivery Responsibilities===
===Clearance Delivery Responsibilities===
The Clearance Delivery Controller Must:<br>
The Clearance Delivery Controller Must:<br>
<ul>
<ul>
<li>Formulate and issue all IFR clearances to aircraft departing this field.</li>
<li>Formulate and issue all IFR and VFR clearances to aircraft departing this field.</li>
<li>Review proposed flight plan information for accuracy and amend routings and altitudes, as necessary, in accordance with this SOP.</li>
<li>Review proposed flight plan information for accuracy and amend routings and altitudes, as necessary, in accordance with this SOP.</li>
<li>Enter amendments to flight plans into the controller client as required and advise the pilot what those amendments are.</li>
<li>Enter amendments to flight plans into the controller client as required and advise the pilot what those amendments are.</li>
Line 121: Line 100:
</ul>
</ul>
===Pre-Departure Clearances===
===Pre-Departure Clearances===
<div style=color:red;>Pre Departure Clearances are not authorized at this airport.</div>
<div style=color:green;>Pre Departure Clearances are authorized at this airport.</div>
<B>It is advisable that ALL controllers issue PDCs for departures for KMCO INTL ATCT</b><br>
<b><i>PDC Commands</i></B><br>
<u>For Pilot Navigation SIDS</u>
If Orlando Approach or Jacksonville Center is Online: <span style='color:orange;'> .pdcr <B>{Departure Runway} {Dep Frequency ID}</b></span><br>
If Orlando Approach and Jacksonville Center is Offline: <span style='color:orange;'> .pdcru <B>{Departure Runway} </b></span><br>
<b>
<u>For Radar Vector SIDS</u>
If Orlando Approach or Jacksonville Center is Online: <span style='color:orange;'> .pdco <B>{Departure Runway} {Dep Frequency ID}</b></span><br>
If Orlando Approach and Jacksonville Center is Offline: <span style='color:orange;'> .pdcou <B>{Departure Runway} </b></span><br>


=== IFR Departures ===
=== IFR Departures ===
Line 127: Line 115:
<tab name="Route">
<tab name="Route">
===Planned/Amended Routing===
===Planned/Amended Routing===
All Aircraft shall be "cleared as filed unless a route amendment is necessary.<BR>
RNAV Departure: All Aircraft shall be "cleared via {Departure} {Fix} Transition then as filed" unless a route amendment is necessary.<BR>
Non-Rnav Jets: Aircraft shall be "cleared via ORL# departure radar vector {fix} then as filed" unless a route amendment is necessary.<br>
Non-Rnav Turboprops/props: Aircraft shall be "cleared via CITR# departure radar vector {fix} then as filed" unless a route amendment is necessary.<br>
<br>
<u>Departures</u><br>
<ul>
<li>CITR= (Turboprops and Props Only)/li>
<li>DDANY= Southeast Bound (Turbojets Only)</li>
<li>FATHE= North Bound (Turbojets Only)</li>
<li>FSHUN= Southwest Bound (Turbojets and Turboprops Only)</li>
<li>JEEMY= North Bound (Turbojets Only)</li>
<li>MZULO= Northeast Bound (Turbojets Only)</li>
<li>ORL</li>
<li>OSPRY= West and Southwest Bound (Turbojets Only)</li>
<li>RDSOX= West Bound (Turbojets Only)</li>
</ul>
<b>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.</b>
<br>
<br>
</tab>
</tab>
<tab name="Altitude">
<tab name="Altitude">
===Assigned Altitudes===
===Assigned Altitudes===
Aircraft shall be instructed to maintain 4,000 feet and to expect their cruise altitude (if higher) ten minutes after departure.
Aircraft shall be instructed to maintain 3,000 feet and to expect their cruise altitude (if higher) ten minutes after departure.<br>
All IFR Aircraft conducting practice approaches shall maintain 3,000 feet
</tab>
</tab>
<tab name="Frequency">
<tab name="Frequency">
===Departure Frequency===
===Departure Frequency===
The Primary Departure Frequency is CAE_S_APP on 124.150
The Primary Departure Frequency is JAX_N_APP on 127.000.
</tab>
</tab>
<tab name="Squawk">
<tab name="Squawk">
===Squawk Assignment===
===Squawk Assignment===
All IFR Squawk codes will be auto-assigned by the controller client. <br>
All IFR Squawk codes will be auto-assigned by the controller client. <br>
It should assign a code between 1601-1677. Controllers shall not change the auto-assigned code if a code between 1601-1677 is not assigned.
It should assign a code between 2601-2677. Controllers shall not change the auto-assigned code if a code between 2601-2677 is not assigned.
</tab>
<tab name="DTA Information">
{| class="wikitable" style="width: 100%;"
|+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
|}<br>
{| class="wikitable" style="width: 100%;"
|+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
|}
<br><br>
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.<br>
</tab>
</tab>
</tabs>
</tabs>
Line 149: Line 210:
<tab name="Clearance">
<tab name="Clearance">
===Clearance===
===Clearance===
VFR Aircraft do not need explicit clearance to enter or exit the airspace.
VFR Aircraft do not need explicit clearance to enter or exit the airspace.<br>
All VFR remaining in the pattern will require coordination with the tower and will be directed to contact when ready for taxi.
</tab>
</tab>
<tab name="Altitude">
<tab name="Altitude">
===Assigned Altitudes===
===Assigned Altitudes===
Jet: VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
<b>Not Remaining in the Pattern</b><br>
Turboprops:  VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
Jet: VFR aircraft shall be instructed to maintain VFR at or below 3,000.<br>
Props:  VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
Turboprops:  VFR aircraft shall be instructed to maintain VFR at or below 3,000.<br>
Props:  VFR aircraft shall be instructed to maintain VFR at or below 3,000.<br>
</tab>
</tab>
<tab name="Frequency">
<tab name="Frequency">
===Departure Frequency===
===Departure Frequency===
Aircraft not remaining in the pattern shall be given the Departure Frequency of CAE_S_APP on 124.150.<br>
Aircraft not remaining in the pattern shall be given the Departure Frequency is JAX_N_APP on 127.000.<br>
Aircraft remaining in the pattern shall not be given a departure frequency.
Aircraft remaining in the pattern shall not be given a departure frequency.
</tab>
</tab>
<tab name="Squawk">
<tab name="Squawk">
===Squawk Assignment===
===Squawk Assignment===
VFR Squawk codes shall be assigned by the controller client using the assign squawk feature in their controller client. <br>
VFR Squawk codes shall be assigned by the controller client using the assign squawk feature in their controller client for all traffic not remaining in the pattern. <br>
</tab>
</tab>
</tabs>
</tabs>
Line 186: Line 249:
The runway assignment should be the runway closest to the position of the aircraft based on the Active Runway Assignments as selected by the Local Controller.<br>
The runway assignment should be the runway closest to the position of the aircraft based on the Active Runway Assignments as selected by the Local Controller.<br>
===Taxi Operations===
===Taxi Operations===
Aircraft taxing to a runway shall be given the closest and shortest taxi instructions to the active runway.<br>
As the taxiways at Jacksonville are simple, there are no defined routes for taxi.<br>
<b>NOTE: Do not direct an aircraft leaving the runway to hold short of the parallel taxiway without prior approval from LC.</b>
 
===Transfer of Communication===
===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.
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.
</tab>
</tabs>


== [[Tower]] ==
== [[Tower]] ==
=== Active Runway Selection ===
=== Active Runway Selection ===
The active runway shall be determined based on wind and known
The active runway shall be determined based on wind and known factors that may affect the safety of takeoff/landing operations. <br>
factors that may affect the safety of takeoff/landing operations.<br>
East Operations is designated as the calm wind runway.<br>
Runway 11 is designated as the calm wind runway.<br><br>
<ul>
<li><b>East Ops:</b> Runway 8 and 14. It is recommended that VFR traffic remaining in the pattern use runway 8.</li>
<li><b>West Ops:</b> Runway 26 and 32. It is recommended that VFR traffic remaining in the pattern use runway 26.</li>
</ul>
<br>
<br>
[https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap3_section_5.html 7110.65Z Runway Selection]
[https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap3_section_5.html 7110.65Z Runway Selection]
=== Area of responsibility ===
=== Area of responsibility ===
LC has responsibility for a five-mile radius from the CAE field from the surface up to and including 2,500 feet. LC has the responsibility to control 4,000 feet and below 1 ½ miles on either side of the extended centerline within 5 miles of the departure end of the automatic departure runways.<br>
LC has responsibility for a five mile radius from the JAX field from surface up to and including 3,000 MSL.<br>
=== Arrival Procedures ===
=== Arrival Procedures ===
LC shall be responsible for separation of all arrival aircraft that have
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<br>
been handed off by TRACON from all departing aircraft still under LC
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.<br>
jurisdiction<br><br>
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles from the runway.
<br>
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the
TRACON. Practice Instrument Approaches shall assign runway heading and maintain 4,000 feet. Departure frequency as assigned by approach control.<br><br>
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles
from the runway.
<br>
<br>
=== Automatic Terminal Information Service ===
=== Automatic Terminal Information Service ===
LC shall manage the ATIS for KCAE<br><br>
LC shall manage the ATIS<br>
The ATIS shall be on 120.150
The ATIS shall be on 125.850
 
=== Automatic Releases ===
=== 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 <br>
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 <br>
Line 218: Line 283:
Departure releases must be obtained if automatic releases are suspended by TRACON. <br><br>
Departure releases must be obtained if automatic releases are suspended by TRACON. <br><br>
=== Departure Procedures ===
=== Departure Procedures ===
LC will provide separation for aircraft in the LC airspace.
LC will provide separation for aircraft in the LC airspace. LC shall provide initial radar separation between successive departures. When automatic departures are in effect, IFR jet/turbojet departures shall be released on the appropriate heading climbing to 3,000 feet. When automated departures are in effect, VFR may be released on the appropriate heading climbing at or below 3,000.
<br>LC shall provide initial radar separation between successive departures.
<br><br>
<br> When automatic departures are in effect, IFR jet/turbojet departures
<b>Departure Headings</b><br>
shall be released on runway heading climbing to 4,000 feet.<br>
<B>Standard Turbojet Departure Headings</b><br>
LC has the option to assign all NON-JET aicraft runway heading or a fanned heading that will conform to the applicable departure corridor.<br><br>
<u>East Operations</u><br>
Runways 8 and 14 Traffic Departing to the South Sector: Heading 140.<br>
Runway 8 Traffic Departing to the North Sector: Heading 080.<br>
Runway 14 Traffic Departing to the North Sector: Heading 100.<br>
<br>
<u>West Operations</u><br>
Runways 26 and 32 Traffic Departing to the South Sector: Heading 220.<br>
Runway 26 and 32 Traffic Departing to the North Sector: Heading 320.<br>
Exception: Traffic Going to the southwest during west operations will be given a heading of 320.<br>
<br>
<u>Standard PROP departure Headings</u>
Assign an alternate departure heading as depicted to achieve separation between IFR prop departures.<br>
[[File:JAXDEPPROP.JPG]]
<br><br>
=== Go Around/ Unplanned Missed Approaches ===
=== Go Around/ Unplanned Missed Approaches ===
LC shall assign IFR aircraft runway heading and 4,000 feet<br>
East Operations: LC shall assign a heading of 070 and 2,000 feet.<br>
<B>LC must verbally coordinate with departure prior to frequency change.</b><br><br>
West Operations: LC shall assign a heading of 320 and 2,000 feet.<br>
<B>LC must verbally coordinate with departure prior to frequency change.</b><br>
=== Land and Hold Short ===
N/A
=== Line Up and Wait ===
=== 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.  
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 ===
=== Visual Tower ===
Columbia Metro 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.
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.

Revision as of 08:10, 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

Aircraft shall be instructed to maintain 3,000 feet and to expect their cruise altitude (if higher) ten minutes after departure.
All IFR Aircraft conducting practice approaches shall maintain 3,000 feet

Departure Frequency

The Primary Departure Frequency is JAX_N_APP on 127.000.

Squawk Assignment

All IFR Squawk codes will be auto-assigned by the controller client.
It should assign a code between 2601-2677. Controllers shall not change the auto-assigned code if a code between 2601-2677 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 not need explicit clearance to enter or exit 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 3,000.
Turboprops: VFR aircraft shall be instructed to maintain VFR at or below 3,000.
Props: VFR aircraft shall be instructed to maintain VFR at or below 3,000.

Departure Frequency

Aircraft not remaining in the pattern shall be given the Departure Frequency is JAX_N_APP on 127.000.
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 not remaining in the pattern.

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

The runway assignment should be the runway closest to the position of the aircraft based on the Active Runway Assignments as selected by the Local Controller.

Taxi Operations

As the taxiways at Jacksonville are simple, there are no defined routes for taxi.
NOTE: Do not direct an aircraft leaving the runway to hold short of the parallel taxiway without prior approval from LC.

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.
East Operations is designated as the calm wind runway.

  • East Ops: Runway 8 and 14. It is recommended that VFR traffic remaining in the pattern use runway 8.
  • West Ops: Runway 26 and 32. It is recommended that VFR traffic remaining in the pattern use runway 26.



7110.65Z Runway Selection

Area of responsibility

LC has responsibility for a five mile radius from the JAX field from surface up to and including 3,000 MSL.

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 125.850

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

LC will provide separation for aircraft in the LC airspace. LC shall provide initial radar separation between successive departures. When automatic departures are in effect, IFR jet/turbojet departures shall be released on the appropriate heading climbing to 3,000 feet. When automated departures are in effect, VFR may be released on the appropriate heading climbing at or below 3,000.

Departure Headings
Standard Turbojet Departure Headings
East Operations
Runways 8 and 14 Traffic Departing to the South Sector: Heading 140.
Runway 8 Traffic Departing to the North Sector: Heading 080.
Runway 14 Traffic Departing to the North Sector: Heading 100.

West Operations
Runways 26 and 32 Traffic Departing to the South Sector: Heading 220.
Runway 26 and 32 Traffic Departing to the North Sector: Heading 320.
Exception: Traffic Going to the southwest during west operations will be given a heading of 320.

Standard PROP departure Headings Assign an alternate departure heading as depicted to achieve separation between IFR prop departures.
JAXDEPPROP.JPG

Go Around/ Unplanned Missed Approaches

East Operations: LC shall assign a heading of 070 and 2,000 feet.
West Operations: LC shall assign a heading of 320 and 2,000 feet.
LC must verbally coordinate with departure prior to frequency change.

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.

Retrieved from "https://www.idszjxartcc.org/index.php?title=Orlando_International_ATCT&oldid=773"