Columbia Metro ATCT/TRACON: Difference between revisions

From ZJX ARTCC SOPs
Jump to navigation Jump to search
No edit summary
Line 103: Line 103:
</tab>
</tab>
</tabs>
</tabs>
== [[Clearance Delivery]] ==
== [[Clearance Delivery]] ==
=== General Information ===
<tabs>
<tabs>
<tab name="IFR Departures">
<tab name="Responsibilities">
Initial Altitude for all IFR Departures is 4,000 feet. Pilots shall expect their cruise (if higher) in 10 minutes after departure.<br>
===Clearance Delivery Responsibilities===
There is no published departure procedures for Columbia. All aircraft will be cleared to their destination via radar vectors to their first fix.<br><br>
The Clearance Delivery Controller Must:<br>
<b><i>Phraseology</i></B><br>
<ul>
<span style='color:green;'><b>{Callsign}</b>, You are cleared to the <b>{Arrival Airport}</b> Airport via radar vectors <b>{First fix}</b> then as filed. Maintain 4,000, expect <b>{cruise}</b> one-zero minutes after departure. Departure Frequency <b>{departure frequency}</b>, squawk <b>{squawk code}</b>.</span>
<li>Formulate and issue all IFR 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>Enter amendments to flight plans into the controller client as required and advise the pilot what those amendments are.</li>
<li>Issue clearances or route changes to aircraft, as required complying with traffic management initiatives and/or weather avoidance.</li>
<li>Forward and await a response on all non-standard routing requests to the affected facilities.</li>
<li><I><u>During Events:</i></u> Do not change routes or proposal times for aircraft participating in Traffic Management programs without prior coordination with the controller in charge.</li>
</ul>
</tab>
</tab>
<tab name="VFR Departures">
<tab name="Operational Positions">
VFR with or without flight following maintain VFR at or below 2,000 feet.<br>
===Operational Positions===
Columbia Metro is a class Charlie. All VFR traffic not remaining in the pattern will be issued a discrete squawk code.<br>
<br>
<b><i>Phraseology</i></B><br>
<span style='color:green;'><b>{Callsign}</b>, Maintain VFR at or below 2,000 feet, <b>{departure frequency}</b>, squawk <b>{squawk code}</b>.</span>
<br>
<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 name="Departure Frequency">
The table below list the common frequencies used a departures frequencies by CAE Clearance Delivery. This guide is only that, a guide. The actual departure frequency has to determined based on coordination with the other controllers that are online.
{| class="wikitable" style="width: 100%;"
{| class="wikitable" style="width: 100%;"
|+
|+
!Position
!Position
!Radio Name
!Callsign
!Callsign
!Traffic Direction
!Relief Callsign
!Symbol
!Symbol
!Frequency
!Frequency
|-
|-
|Radar South
|Clearance Delivery
|CAE_S_APP
|Columbia Clearance Delivery
|South
|CAE_DEL
|7RS
|CAE_1_DEL
|124.150
|7CD
|-
|119.750
|Radar North
|CAE_N_APP
|North
|7RN
|133.400
|}
|}
</tab>
<tab name="PDC">
===Pre-Departure Clearances===
<div style=color:red;>Pre Departure Clearances are not authorized at this airport.</div>
</tab>
</tab>
</tabs>
</tabs>


== [[Ground]] ==
=== IFR Departures ===
<tabs>
<tabs>
<tab name="Pushback and Startup">
<tab name="Route">
Ground Control does not authorize pushbacks or startups unless the aircraft pushing will enter the controlled area during the pushback.<br>
===Planned/Amended Routing===
All Aircraft shall be "cleared as filed unless a route amendment is necessary.<BR>
<br>
<br>
<b><i>Phraseology</i></b><br>
<u>Aircraft does not enter the controlled area</u><br>
<span style='color:green;'><b>{Callsign}</b>, Push back and start is at your discretion.</span><br>
<u>Aircraft does enter the controlled area</u><br>
<span style='color:green;'><b>{Callsign}</b>, Push and start approved, push tail facing <b>(direction)</b></span><br>
</tab>
</tab>
<tab name="Taxi Routes">
<tab name="Altitude">
As the taxiways at Columbia Metro are simple, there are no defined routes for taxi.<br><br>
===Assigned Altitudes===
<b><i>Phraseology</i></b><br>
Aircraft shall be instructed to maintain 4,000 feet and to expect their cruise altitude (if higher) ten minutes after departure.
<u>To Runway</u><br>
<span style='color:green;'><b>{Callsign}</b>, Runway <b>{Number}</b> taxi via <b>{taxi instructions} {Any Hold Short Instructions}</b>.</span><br>
<u>To Ramp</u><br>
<span style='color:green;'><b>{Callsign}</b>, Taxi to the ramp via <b>{taxi instructions} {Any Hold Short Instructions}</b>.</span><br>
</tab>
</tab>
<tab name="Intersection Departure">
<tab name="Frequency">
Ground Control must advise Local Control of all intersection departures verbally or through the chatbox in the controller client.
===Departure Frequency===
<br><br>
The Primary Departure Frequency is CAE_S_APP on 124.150
<b><i>Phraseology</i></B><br>
<span style='color:green;'><b>{Callsign}</b>, Runway <b>{Runway Number}</B> at <b>{Intersecting Taxiway}</b>, taxi via <b>{taxiways} {Any Hold Short Instructions}</b>.</span>
</tab>
</tab>
<tab name="ATIS">
<tab name="Squawk">
Ground controller shall ensure each pilot has the current ATIS information prior to being handed off to Local Control
===Squawk Assignment===
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.
</tab>
</tab>
<tab name="Active Runway operations">
</tabs>
GC must transfer communications to LC if an aircraft is to operate on an active runway.<br>
<br>
<b><i>Phraseology</i></b><br>
<span style='color:green;'><b>{Your Callsign}</b>, <b>{Their Callsign}</b> (wait for response)<br>
One to cross runway <b>{number}</b> at <b>{Taxiway}</b> (wait for response)<br></span><br>
If Approved: <span style='color:green;'>Approved <b>{Their OI}</b> Response: Approved <b>{Your OI}</b></span><br>
If Denied: <span style='color:green;'>Hold <b>{reason}</b></span><br><br>
Once Crossing Completed: <span style='color:green;'><b>{Your Callsign}</b>, <b>{Their Callsign}</b> (wait for response)<br>
Crossing Complete <b>{Your OI}</b>, Roger <b>{Their OI}</b>


=== VFR Departures ===
<tabs>
<tab name="Clearance">
===Clearance===
VFR Aircraft do not need explicit clearance to enter or exit the airspace.
</tab>
</tab>
<tab name="Handoffs">
<tab name="Altitude">
GC shall instruct aircraft to contact tower unless otherwise agreed upon by LC. LC can request pilot monitor the frequency instead of contacting.<br>
===Assigned Altitudes===
<br>
Jet: VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
<b><i>Phraseology</i></b><br>
Turboprops:  VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
<span style='color:green;'><b>{Callsign}</b>, Contact Columbia Tower 119.5</span>
Props:  VFR aircraft shall be instructed to maintain VFR at or below 2,000.<br>
</tab>
<tab name="Frequency">
===Departure Frequency===
Aircraft not remaining in the pattern shall be given the Departure Frequency of CAE_S_APP on 124.150.<br>
Aircraft remaining in the pattern shall not be given a departure frequency.
</tab>
<tab name="Squawk">
===Squawk Assignment===
VFR Squawk codes shall be assigned by the controller client using the assign squawk feature in their controller client. <br>
</tab>
</tab>
</tabs>
</tabs>


== [[Tower]] ==
== Ground ==
=== General Information ===
<tabs>
<tabs>
<tab name="Area of Responsibility">
<tab name="Responsibilities">
LC has responsibility for a five mile radius from the CAE field from surface up to and including 2,500 feet. LC has responsibility to control 4,000 feet and below 1 ½ miles either side of the extended centerline within 5 miles of the departure end of the automatic departure runways.<br>
===Ground Control Responsibilities===
The Ground Controller is:<br>
<ul>
<li>Responsible for the movement of vehicles and aircraft on the airport movement areas except for the active runway(s)</li>
</ul>
</tab>
<tab name="Operational Positions">
===Operational Positions===
{| class="wikitable" style="width: 100%;"
|+
!Position
!Radio Name
!Callsign
!Relief Callsign
!Symbol
!Frequency
|-
|Ground Control
|Columbia Ground
|CAE_GND
|CAE_1_GND
|7CG
|121.900
|}
</tab>
<tab name="ATIS">
===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.
</tab>
<tab name="Active Runway Operations">
===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"<br>
</tab>
<tab name="Intersection Departures">
===Intersection Departures===
Ground Control must advise local control of all intersection departures verbally.<br>
</tab>
<tab name="Opposite Direction Departures">
===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.
</tab>
<tab name="Pushback and Startup">
===Pushback and Startup===
<b>Push back into a controlled area:</b> 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.<br>
<b>Push back will not enter a controlled area:</b> Aircraft shall be instructed: "Push and start at pilot's discretion."
</tab>
<tab name="Runway Assignments">
===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.<br>
</tab>
<tab name="Taxi Operations">
===Taxi Operations===
Aircraft taxing to a runway shall be given the closest and shortest taxi instructions to the active runway.<br>
</tab>
<tab name="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.
</tab>
</tab>
</tabs>
== Tower ==
<tabs>
<tab name="Active Runway Selection">
<tab name="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>
Line 205: Line 262:
[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]
</tab>
</tab>
<tab name="Departure Procedures">
<tab name="Area of Responsibility">
LC will provide separation for aircraft in the LC airspace.
=== Area of responsibility ===
<br>LC shall provide initial radar separation between successive departures.
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>
<br> When automatic departures are in effect, IFR jet/turbojet departures
shall be released on runway heading climbing to 4,000 feet.<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>
<b><i>Phraseology</i></b><br>
<span style='color:green;'><b>{Callsign}</b>, <b>{Departure Instruction}</b>, Wind <b>{direction}</b> at <b>{speed}</b>, Runway <b>{Runway}</b>, Cleared for takeoff</span><br>
<span style='color:green;'><b>{Callsign}</b>, Contact Departure <b>{frequency}</B></span><br>
</tab>
</tab>
<tab name="Arrival Procedures">
<tab name="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
been handed off by TRACON from all departing aircraft still under LC
jurisdiction<br><br>
jurisdiction<br><br>
<b><i>Phraseology</i></b><br>
<span style='color:green;'><b>{Callsign}</b>, <b>{Traffic Advisories} </b>, Wind <b>{direction}</b> at <b>{speed}</b>, Runway <b>{Runway}</b>, Cleared for land</span><br>
<br>
<br>
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the
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>
TRACON. Practice Instrument Approaches shall assign runway heading and maintain 4,000 feet. Departure frequency as assigned by approach control.<br><br>
<b><i>Phraseology</i></b><br>
<B></B><span style='color:green;'><b>{Callsign}</b>, Fly Runway Heading, Climb and Maintain 4,000, Contact Approach on <b>{Frequency}</b></span><br>
<br><br>
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles
from the runway.
from the runway.
<br><br>
<br><br>
</tab>
</tab>
<tab name="Go Around/unplanned Missed Approach">
<tab name="ATIS">
LC shall assign IFR aircraft runway heading and 4,000 feet<br>
=== Automatic Terminal Information Service ===
<B>LC must verbally coordinate with departure prior to frequency change.</b><br><br>
LC shall manage the ATIS for KCAE<br><br>
<b><i>Phraseology</i></b><br>
The ATIS shall be on 120.150
<B>AFTER COORDINATION WITH TRACON: </B><span style='color:green;'><b>{Callsign}</b>, Fly <b>{Heading}</b>, Climb and Maintain <b>{Altitude}</b>, Contact Approach on <b>{Frequency}</b></span><br>
</tab>
</tab>
<tab name="Automatic Releases">
<tab name="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>
In order for automatic releases to be authorized, procedures in this document shall be followed.<br>
In order for automatic releases to be authorized, procedures in this document shall be followed.<br>
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>
<b><i>Phraseology</i></b><br>
</tab>
Requesting Release: <span style='color:green;'><b>{Their Callsign}</b><b>{Your Callsign}</b>, <br>(Hold for answer)<br> Release for departure, <b>{Airport} {Callsign} {Runway} {First Fix}</b><br>(Hold for Answer)</span><br>
<tab name="Departure Procedures">
If Approved: <span style='color:green;'>Approved<b>{Any Restrictions} {Their OI}</b> Roger, Approved <b>{Restrictions} {Your OI}</b></span><br>
=== Departure Procedures ===
If Denied: <span style='color:green;'>Hold; Expect clearance at <b>{Zulu} {Their OI}</b> Roger <b>{Your OI}</b></span><br>
LC will provide separation for aircraft in the LC airspace.
<br>LC shall provide initial radar separation between successive departures.
<br> When automatic departures are in effect, IFR jet/turbojet departures
shall be released on runway heading climbing to 4,000 feet.<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>
</tab>
<tab name="Go Around/unplanned Missed Approach">
=== Go Around/ Unplanned Missed Approaches ===
LC shall assign IFR aircraft runway heading and 4,000 feet<br>
<B>LC must verbally coordinate with departure prior to frequency change.</b><br><br>
</tab>
<tab name="LUAW">
=== 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.
</tab>
</tab>
<tab name="Visual Tower">
<tab name="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.
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.
</tab>
<tab name="ATIS">
LC shall manage the ATIS for KCAE<br><br>
The ATIS shall be on 120.150
</tab>
</tab>
</tabs>
</tabs>
== [[TRACON Information]] ==
== [[TRACON Information]] ==
<tabs>
<tabs>

Revision as of 12:19, 5 June 2023

Table of Updates

Date Revision Items Revised
2 May 2023 A Update of Organization

Area Information

ICAO Code Airport Name Airspace IFR Beacon Codes VFR Beacon Codes
KCAE Columbia Metro Airport C 1601-1677 1601-1677


Purpose
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.

Distribution
This order is distributed to all Jacksonville ARTCC personnel.

Columbia Metro Airport via Google Maps

Operational Positions

Position Radio Name Callsign Relief Callsign Symbol Frequency
Clearance Delivery Columbia Clearance Delivery CAE_DEL CAE_1_DEL 7CD 119.750
Ground Columbia Ground CAE_GND CAE_1_GND 7CG 121.900
Tower Columbia Tower CAE_TWR CAE_1_TWR 7CT 119.500
CAE TRACON
Position Sector Name Callsign Relief Callsign Symbol Frequency
RN Radar North CAE_N_APP CAE_1N_APP 7RN 133.400
RS Radar South CAE_S_APP CAE_1S_APP 7RS 124.150
RF Radar Final CAE_F_APP CAE_1F_APP 7RF 128.500

Sector in Red is the primary sector.

Clearance Delivery

General Information

Clearance Delivery Responsibilities

The Clearance Delivery Controller Must:

  • Formulate and issue all IFR 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.

Operational Positions

Position Radio Name Callsign Relief Callsign Symbol Frequency
Clearance Delivery Columbia Clearance Delivery CAE_DEL CAE_1_DEL 7CD 119.750

Pre-Departure Clearances

Pre Departure Clearances are not authorized at this airport.

IFR Departures

Planned/Amended Routing

All Aircraft shall be "cleared as filed unless a route amendment is necessary.

Assigned Altitudes

Aircraft shall be instructed to maintain 4,000 feet and to expect their cruise altitude (if higher) ten minutes after departure.

Departure Frequency

The Primary Departure Frequency is CAE_S_APP on 124.150

Squawk Assignment

All IFR Squawk codes will be auto-assigned by the controller client.
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.

VFR Departures

Clearance

VFR Aircraft do not need explicit clearance to enter or exit the airspace.

Assigned Altitudes

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 2,000.

Departure Frequency

Aircraft not remaining in the pattern shall be given the Departure Frequency of CAE_S_APP on 124.150.
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.

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)

Operational Positions

Position Radio Name Callsign Relief Callsign Symbol Frequency
Ground Control Columbia Ground CAE_GND CAE_1_GND 7CG 121.900

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

Aircraft taxing to a runway shall be given the closest and shortest taxi instructions to the active runway.

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

7110.65Z Runway Selection

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.

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 4,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 for KCAE

The ATIS shall be on 120.150

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 runway heading climbing to 4,000 feet.
LC has the option to assign all NON-JET aicraft runway heading or a fanned heading that will conform to the applicable departure corridor.

Go Around/ Unplanned Missed Approaches

LC shall assign IFR aircraft runway heading and 4,000 feet
LC must verbally coordinate with departure prior to frequency change.

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.

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.

TRACON Information

RS (CAE_S_APP) is the primary "combined" radar position for Columbia Metro Tracon. No other sectors shall be staffed until the "combined" position is in use. RS may delegate a portion of its airspace to RN. One RS and RN are staffed, they both can delegate a portion of their airspace to RF


Responsibility
Provide Overflight Services, approach/departure sequence, and, where required, uncontrolled operation services to aircraft landing in the Columbia Tracon Airspace.

Jurisdiction RS area of jurisdiction is the South quadrant of the airspace as depicted, surface to 10,000 feet MSL. RS is responsible for departure control for Southbound traffic

RS Area of Jurisdiction
RN (CAE_N_APP) is the secondary radar position for Columbia Tracon. RS may delegate a portion of its airspace to RN.


Responsibility
Provide Overflight Services, approach/departure sequence, and, where required, uncontrolled operation services to aircraft landing in the Columbia Tracon Airspace.

Jurisdiction RN area of jurisdiction is the North quadrant of the airspace as depicted surface to 10,000 feet MSL. RN is responsible for departure control for Northbound traffic.

RN Area of Jurisdiction

RN and RS may delegate a portion of their airspaces to RF, once both are in use.

RF area of jurisdiction is from the arrival end of the selected arrival runway to a 20nm radius for 10nm on either side of the selected arrival runway, from surface to 4,000 feet MSL. RF is responsible for sequencing arrival aircraft.

VFR Aircraft entering the Class Charlie airspace will be given a discrete beacon code.
Phraseology
{Callsign}, squawk {squawk code}.

If an aircraft departs from CAE and does not request a flight following, the aircraft will be handed off from LC to TRACON and released to UNICOM once clear of the Class Charlie.

Phraseology
{Callsign}, Change to Advisory Frequency Approved, squawk 1200.
7110.65Z Class C Service- Terminal

Columbia Metro ATCT is a VFR tower. No radar handoffs shall be initiated to LC.

TRACON controllers shall not drop the track on any arriving aircraft. This allows a controller to maintain radar identification during missed approach.
Phraseology
{Callsign}, Contact Columbia Tower on {frequency}.

TRACON sectors give automatic releases to all departures from Colubia ATCT when departures follow the standard departure procedures as specified in this document.
All other airports within TRACON’s boundaries shall request a departure release. Upon approval of the release, the release shall be good for five minutes.
Upon issuance of the takeoff clearance, a departure message shall be sent to the appropriate departure sector. This can be accomplished non-verbally by the LC ensuring the aircraft is squawking the appropriate squawk code and mode C is enabled when airborne.

Phraseology
Requesting Release: {Their Callsign}{Your Callsign},
(Hold for answer)
Release for departure, {Airport} {Callsign} {Runway} {First Fix}
(Hold for Answer)

If Approved: Approved{Any Restrictions} {Their OI} Roger, Approved {Restrictions} {Your OI}
If Denied: Hold; Expect clearance at {Zulu} {Their OI} Roger {Your OI}

Forward departure instructions to LC for aircraft executing practice missed approaches.
Ensure all departures are on course as soon as practical.
All departures should be on course before handoff to Enroute Control unless otherwise coordinated. Aircraft shall be climbed to 10,000 or less if filed.
Provide airspace for automatic departures and radar final.
Provide airspace for missed approach on all runways.

The sector responsible for the primary runway shall establish the approach sequence for all arrivals.
Communications transfer of arriving aircraft to LC must be accomplished no later than five nautical miles from the end of the arrival runway.
When simultaneous approaches are being conducted on converging runways, LC is responsible for ensuring runway separation. However, TRACON must provide enough spacing to minimize the possibility of a go-around.
When vectoring to final from parallel downwinds, aircraft on opposing base legs shall be assigned altitudes to ensure vertical separation unless other approved separation has been applied. This ensures separation in the event of an overshoot on final.
Coordinate with LC for any aircraft conducting approaches to other runways than the active arrival runway(s) in use.