Myrtle Beach ATCT/TRACON: Difference between revisions
(→Tower) |
|||
(14 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== [[Table of Updates]] == | |||
{| class="wikitable" style="width: 100%;" | |||
|+ | |||
!Date | |||
!Revision | |||
!Items Revised | |||
|- | |||
|2 May 2023 | |||
|A | |||
|Update of Organization/Adding of CRE SOP. | |||
|- | |||
|1 May 2024 | |||
|B | |||
|STARS Tower Added to MYR | |||
|} | |||
== [[Area Information]] == | == [[Area Information]] == | ||
{| class="wikitable" style="width: 100%;" | {| class="wikitable" style="width: 100%;" | ||
Line 11: | Line 27: | ||
|Myrtle Beach International Airport | |Myrtle Beach International Airport | ||
|C | |C | ||
|6501-6577 | |||
|6501-6577 | |||
|- | |||
|KCRE | |||
|Grand Strand Airport | |||
|D | |||
|6501-6577 | |6501-6577 | ||
|6501-6577 | |6501-6577 | ||
Line 98: | Line 120: | ||
|CRE_1_TWR | |CRE_1_TWR | ||
|124.600 | |124.600 | ||
|} | |} | ||
</tab> | </tab> | ||
Line 121: | Line 134: | ||
<tab name="VFR Departures"> | <tab name="VFR Departures"> | ||
VFR with or without flight following maintain VFR at or below 3,000 feet.<br> | VFR with or without flight following maintain VFR at or below 3,000 feet.<br> | ||
Myrtle Beach is a class Charlie. All VFR traffic will be issued a discrete squawk code.<br> | Myrtle Beach is a class Charlie. All VFR traffic not remaining in the pattern will be issued a discrete squawk code.<br> | ||
<br> | <br> | ||
<b><i>Phraseology</i></B><br> | <b><i>Phraseology</i></B><br> | ||
Line 280: | Line 293: | ||
If Denied: <span style='color:green;'>Hold; Expect clearance at <b>{Zulu} {Their OI}</b> Roger <b>{Your OI}</b></span><br> | If Denied: <span style='color:green;'>Hold; Expect clearance at <b>{Zulu} {Their OI}</b> Roger <b>{Your OI}</b></span><br> | ||
</tab> | </tab> | ||
<tab name=" | <tab name="Limited Radar Tower"> | ||
Myrtle Beach ATCT is a | Myrtle Beach ATCT is a Limited Radar tower and shall not initiate or accept any radar handoffs and shall not initiate control/start track on any target. <br> This radar is to be limited to the following uses | ||
<br> | |||
<ul> | |||
<li>Determined the exaction location of an aircraft and its relationship to other aircraft.</li> | |||
<li>Provide radar traffic advisories and basic rada services to aircraft if the benefits are more efficient and its use effective of the local control positions.</li> | |||
<li>To suggest headings or direction to VFR aircraft as a radar identification method or as an advisory aid for navigation.</li> | |||
<li>Instruction and information within the tower airspace to aircraft within its option of area.</li> | |||
<li>Ensure separation between arrivals, departures, and overflights.</li> | |||
</ul> | |||
</tab> | </tab> | ||
<tab name="ATIS"> | <tab name="ATIS"> | ||
Line 291: | Line 312: | ||
== [[TRACON Information]] == | == [[TRACON Information]] == | ||
<tabs> | <tabs> | ||
<tab name="MYR_E_APP"> | |||
{| class="wikitable" style="width: 100%;" | |||
|- | |||
| style="width: 60%;" |EARDR (MYR_E_APP) is the primary "combined" radar position for Myrtle Beach Tracon. No other sectors shall be staffed until the "combined" position is in use. EARDR may delegate a portion of its airspace to WARDR.<br> | |||
<br> | |||
<B>Responsibility</b> <br> | |||
Provide Overflight Services, approach/departure sequence, and, where required, uncontrolled operation services to aircraft landing in the Myrtle Beach Tracon Airspace. | |||
<br> | |||
<br> | |||
<b>Jurisdiction</b> | |||
EARDR area of jurisdiction is the east quadrant of the airspace as depicted, surface to 10,000 feet MSL. EARDR is not responsible for the final approach to runway 18 to MYR ATCT. | |||
| style="width: 30%;" |[[File:MYREAPP.JPG|200px|thumb|left|EARDR Area of Jurisdiction]] | |||
|} | |||
</tab> | |||
<tab name="MYR_W_APP"> | |||
{| class="wikitable" style="width: 100%;" | |||
|- | |||
| style="width: 60%;" |WARDR (MYR_W_APP) is the secondary radar position for Myrtle Beach Tracon. EARDR may delegate a portion of its airspace to WARDR.<br> | |||
<br> | |||
<B>Responsibility</b> <br> | |||
Provide Overflight Services, approach/departure sequence, and, where required, uncontrolled operation services to aircraft landing in the Myrtle Beach Tracon Airspace. | |||
<br> | |||
<br> | |||
<b>Jurisdiction</b> | |||
WARDR area of jurisdiction is the west quadrant of the airspace as depicted, surface to 10,000 feet MSL. WARDR is responsible for the final approach to runway 18 to MYR ATCT. | |||
| style="width: 30%;" |[[File:MYRWAPP.JPG|200px|thumb|left|WARDR Area of Jurisdiction]] | |||
|} | |||
</tab> | |||
<tab name="VFR Aircraft within TRACON"> | |||
VFR Aircraft entering the Class Charlie airspace will be given a discrete beacon code.<br> | |||
<b><i>Phraseology</i></B><br> | |||
<span style='color:green;'><b>{Callsign}</b>, squawk <b>{squawk code}</b>.</span><br><br> | |||
If an aircraft departs from MYR 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.<br> | |||
<br> | |||
<b><i>Phraseology</i></B><br> | |||
<span style='color:green;'><b>{Callsign}</b>, Change to Advisory Frequency Approved, squawk 1200.</span><br> | |||
[https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap7_section_8.html 7110.65Z Class C Service- Terminal] | |||
</tab> | |||
<tab name="Handoff and Radar Tracking"> | |||
Myrtle Beach ATCT is a limited radar tower. No radar handoffs shall be initiated to LC.<br> | |||
<tab name=" | TRACON controllers shall not drop the track on any arriving aircraft. This allows a controller to maintain radar identification during missed approach. | ||
< | <br> | ||
<b><i>Phraseology</i></B><br> | |||
<span style='color:green;'><b>{Callsign}</b>, Contact Myrtle Beach Tower on {frequency}.</span><br> | |||
</tab> | |||
<tab name="Release and Rolling Calls"> | |||
TRACON sectors give automatic releases to all departures from Myrtle Beach ATCT when departures follow the standard departure procedures as specified in this document.<br> | |||
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.<br> | |||
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. <br><br> | |||
<b><i>Phraseology</i></b><br> | |||
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> | |||
If Approved: <span style='color:green;'>Approved<b>{Any Restrictions} {Their OI}</b> Roger, Approved <b>{Restrictions} {Your OI}</b></span><br> | |||
If Denied: <span style='color:green;'>Hold; Expect clearance at <b>{Zulu} {Their OI}</b> Roger <b>{Your OI}</b></span><br> | |||
</tab> | |||
<tab name="General TRACON Departure Procedures"> | |||
Forward departure instructions to LC for aircraft executing practice missed approaches.<br> | |||
Ensure all departures are on course as soon as practical.<br> | |||
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.<br> | |||
Provide airspace for automatic departures and radar final.<br> | |||
Provide airspace for missed approach on all runways.<br><br> | |||
<span style='color:red;'>Note: Ensure notification with SSC, FLO, CHS or ZJX is completed before clearing aircraft to operate in the Gamecock Charlie MOA or ROBROY airspace.</span> | |||
</tab> | |||
<tab name="General TRACON Arrival Procedures"> | |||
The sector responsible for the primary runway shall establish the approach sequence for all arrivals.<br> | |||
Communications transfer of arriving aircraft to LC must be accomplished no later than five nautical miles from the end of the arrival runway.<br> | |||
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.<br> | |||
Coordinate with LC for any aircraft conducting approaches to other runways than the active arrival runway(s) in use. | |||
</tab> | |||
</tabs> | |||
== [[KCRE- Grand Strand]] == | |||
<tabs> | |||
<tab name="Clearance Delivery"> | |||
Initial Altitude for all IFR Departures is 2,000 feet. Pilots shall expect their cruise (if higher) in 10 minutes after departure.<br> | |||
There is no published departure procedures for Grand Strand, All aircraft will be cleared to their destination as filed.<br><br> | |||
<b><i>Phraseology</i></B><br> | |||
<span style='color:green;'><b>{Callsign}</b>, You are cleared to the <b>{Arrival Airport}</b> Airport as filed. Maintain 2,000, expect <b>{cruise}</b> one-zero minutes after departure. Departure Frequency <b>{departure frequency}</b>, squawk <b>{squawk code}</b>.</span> | |||
</tab> | |||
<tab name="Ground"> | |||
As the taxiways at Grand Strand are simple, there are no defined routes for taxi.<br><br> | |||
<b><i>Phraseology</i></b><br> | |||
<u>To Runway</u><br> | |||
<span style='color:green;'><b>{Callsign}</b>, Runway <b>{Number}</b> taxi via <b>{taxi instructions}</b>.</span><br> | |||
<u>To Ramp</u><br> | |||
<span style='color:green;'><b>{Callsign}</b>, Taxi to the ramp via <b>{taxi instructions}</b>.</span><br> | |||
</tab> | |||
<tab name="Tower"> | |||
<b> ALL IFR DEPARTURES REQUIRE RELEASE</b> | |||
<br> | <br> | ||
< | <b> Departure Procedures </b><br> | ||
LC will provide separation for aircraft in the LC airspace. | |||
<br>LC shall provide initial radar separation between successive departures. | |||
LC has the option to assign all NON-JET aicraft runway heading or a fanned heading up to 30 degrees each direction.<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><br> | |||
<b> Arrival Procedures </b> | |||
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><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> | |||
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the | |||
TRACON. Practice Instrument Approaches shall assign runway heading and maintain 2,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 2,000, Contact Approach on <b>{Frequency}</b></span><br> | |||
<br><br> | <br><br> | ||
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles | |||
from the runway. | |||
</tab> | |||
<tab name="Active Runway Selection"> | |||
The active runway shall be determined based on wind and known | |||
< | factors that may affect the safety of takeoff/landing operations.<br> | ||
< | Runway 23 is designated as the calm wind runway.<br><br> | ||
[https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap3_section_5.html 7110.65Z Runway Selection] | |||
</tab> | |||
<tab name="Go Around/unplanned Missed Approach"> | |||
LC shall assign IFR aircraft runway heading and 2,000 feet<br> | |||
<B>LC must verbally coordinate with departure prior to frequency change.</b><br><br> | |||
<b><i>Phraseology</i></b><br> | |||
<br><br> | <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> | ||
< | |||
<br><br> | |||
<i> | |||
< | |||
< | |||
</tab> | </tab> | ||
<tab name="Visual Tower"> | |||
Grand Strand 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 name=" | |||
</tab> | </tab> | ||
<tab name="ATIS"> | |||
<tab name=" | LC shall manage the ATIS for KCRE<br><br> | ||
< | The ATIS shall be on 119.625 | ||
</tab> | </tab> | ||
</tabs> | </tabs> |
Latest revision as of 12:02, 1 May 2024
Table of Updates
Date | Revision | Items Revised |
---|---|---|
2 May 2023 | A | Update of Organization/Adding of CRE SOP. |
1 May 2024 | B | STARS Tower Added to MYR |
Area Information
ICAO Code | Airport Name | Airspace | IFR Beacon Codes | VFR Beacon Codes |
---|---|---|---|---|
KMYR | Myrtle Beach International Airport | C | 6501-6577 | 6501-6577 |
KCRE | Grand Strand Airport | D | 6501-6577 | 6501-6577 |
Purpose This document prescribes the procedures to be utilized for providing air traffic control services at the Myrtle Beach Air Traffic Control Tower (MYR 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 |
Operational Positions
Position | Radio Name | Callsign | Relief Callsign | Symbol | Frequency |
---|---|---|---|---|---|
Ground | Myrtle Beach Ground | MYR_GND | MYR_1_GND | 8MG | 120.300 |
Tower | Myrtle Beach Tower | MYR_TWR | MYR_1_TWR | 8MT | 128.450 |
Position | Sector Name | Callsign | Relief Callsign | Symbol | Frequency |
---|---|---|---|---|---|
EARDR | Radar East | MYR_E_APP | MYR_1E_APP | 8E | 119.200 |
WARDR | Radar West | MYR_W_APP | MYR_1W_APP | 8W | 127.400 |
Sector in Red is the primary sector.
Airport | Position | Radio Name | Callsign | Relief Callsign | Frequency |
---|---|---|---|---|---|
KCRE- Grand Strand | Ground | Stand Ground | CRE_GND | CRE_1_GND | 121.800 |
Tower | Stand Tower | CRE_TWR | CRE_1_TWR | 124.600 |
Clearance Delivery
Initial Altitude for all IFR Departures is 3,000 feet. Pilots shall expect their cruise (if higher) in 10 minutes after departure.
There is no published departure procedures for Myrtle Beach. All aircraft will be cleared to their destination via radar vectors to their first fix.
Phraseology
{Callsign}, You are cleared to the {Arrival Airport} Airport via radar vectors {First fix} then as filed. Maintain 3,000, expect {cruise} one-zero minutes after departure. Departure Frequency {departure frequency}, squawk {squawk code}.
VFR with or without flight following maintain VFR at or below 3,000 feet.
Myrtle Beach is a class Charlie. All VFR traffic not remaining in the pattern will be issued a discrete squawk code.
Phraseology
{Callsign}, Maintain VFR at or below 3,000 feet, {departure frequency}, squawk {squawk code}.
All VFR remaining in the pattern will require coordination with the tower and will be directed to contact when ready for taxi.
Routings to ZTL, ZMA, ZDC and ZHU ARTCCs have been coordinated through letters of agreements (LOAs).
The table below list the common frequencies used a departures frequencies by MYR 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.
Position | Callsign | Traffic Direction | Symbol | Frequency |
---|---|---|---|---|
Radar East | MYR_E_APP | East | 8E | 119.200 |
Radar West | MYR_W_APP | West | 8W | 127.400 |
Ground
Ground Control does not authorize pushbacks or startups unless the aircraft pushing will enter the controlled area during the pushback.
Phraseology
Aircraft does not enter the controlled area
{Callsign}, Push back and start is at your discretion.
Aircraft does enter the controlled area
{Callsign}, Push and start approved, push tail facing (direction)
As the taxiways at Myrtle Beach are simple, there are no defined routes for taxi.
Phraseology
To Runway
{Callsign}, Runway {Number} taxi via {taxi instructions}.
To Ramp
{Callsign}, Taxi to the ramp via {taxi instructions}.
Ground Control must advise Local Control of all intersection departures verbally or through the chatbox in the controller client.
Phraseology
{Callsign}, Runway {Runway Number} at {Intersecting Taxiway}, taxi via {taxiways}.
Ground controller shall ensure each pilot has the current ATIS information prior to being handed off to Local Control
GC must transfer communications to LC if an aircraft is to operate on an active runway.
Phraseology
{Your Callsign}, {Their Callsign} (wait for response)
One to cross runway {number} at {Taxiway} (wait for response)
If Approved: Approved {Their OI} Response: Approved {Your OI}
If Denied: Hold {reason}
Once Crossing Completed: {Your Callsign}, {Their Callsign} (wait for response)
Crossing Complete {Your OI}, Roger {Their OI}
During high volume sessions, GC should use the following procedures for taxiing aircraft to the commercial ramp:
Inbound:Once aircraft have landed and are on GC frequency, the GC should ask the pilot using the following phraseology, “Say gate”, GC will use the information to observe available/unavailable gates and decide whether to hold inbound aircraft at a safe location or instruct the pilot to taxi to the ramp.
Phraseology
{Callsign}, Say Gate.
Outbound:When the pilot calls for clearance, the controller should read the clearance, verify read-back, and resolve any flow control issues:
To properly plan for taxiing aircraft holding for gates and to mitigate taxiway congestion, GC should instruct the pilot to “Advise prior to push”. This should assist controllers in deciding which aircraft need to hold at gates to avoid pushbacks that may interfere with timed departures and mitigate taxiway congestion.
When the aircraft calls for pushback, the controller should determine whether to approve or deny the request. Pushback requests can be denied by stating “hold your push” or “hold position”.
If a controller approves pushback, the controller should inform the pilot “push at pilot's discretion”
Phraseology
After Readback: {Callsign}, Advise Prior to Push
Deny the push: {Callsign}, Hold your push or {Callsign},Hold Position
GC shall instruct aircraft to contact tower unless otherwise agreed upon by LC. LC can request pilot monitor the frequency instead of contacting.
Phraseology
{Callsign}, Contact Myrtle Beach Tower 128.45
Tower
LC has responsibility for a 2.5 mile radius from the MYR field from surface up to and including 2,000 feet MSL. LC is also authorized to control 3,000 feet MSL and below in the published departure corridors.
Runway 18 Departure Corridor
The airspace from midfield of the runway from a 150° bearing clockwise to a 210° bearing, extending 5 miles from the departure end of the runway, surface to 3000 feet. This airspace is delegated to LC for automatic releases of MYR departures when runway 18 is in use. IFR Aircraft shall remain 3 miles east of a 150° bearing from the midfield of the runway clockwise to 3 miles west of a 210° bearing, 8 miles from the departure end of the runway. VFR aircraft shall remain clear of the departure corridor and 8 miles from the runway from a 150° bearing clockwise to a 210° bearing.
Runway 36 Departure Corridor
The airspace from midfield of the runway from a 330° bearing clockwise to a 030° bearing, extending 5 miles from the departure end of the runway, surface to 3000 feet. This airspace is delegated to LC for automatic releases of MYR departures when runway 36 is in use. IFR Aircraft shall remain 3 miles west of a 330° bearing from the midfield of the runway clockwise to 3 miles east of a 030° bearing, 8 miles from the departure end of the runway. VFR aircraft shall remain clear of the departure corridor and 8 miles from the runway from a 330° bearing clockwise to a 030° bearing.
The active runway shall be determined based on wind and known
factors that may affect the safety of takeoff/landing operations.
Runway 18 is designated as the calm wind runway.
7110.65Z Runway Selection
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 3,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.
Phraseology
{Callsign}, {Departure Instruction}, Wind {direction} at {speed}, Runway {Runway}, Cleared for takeoff
{Callsign}, Contact Departure {frequency}
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
Phraseology
{Callsign}, {Traffic Advisories} , Wind {direction} at {speed}, Runway {Runway}, Cleared for land
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the
TRACON. Practice Instrument Approaches shall assign runway heading and maintain 2,000 feet. Departure frequency as assigned by approach control.
Phraseology
{Callsign}, Fly Runway Heading, Climb and Maintain 2,000, Contact Approach on {Frequency}
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles
from the runway.
LC shall assign IFR aircraft runway heading and 3,000 feet
LC must verbally coordinate with departure prior to frequency change.
Phraseology
AFTER COORDINATION WITH TRACON: {Callsign}, Fly {Heading}, Climb and Maintain {Altitude}, Contact Approach on {Frequency}
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.
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}
Myrtle Beach ATCT is a Limited Radar tower and shall not initiate or accept any radar handoffs and shall not initiate control/start track on any target.
This radar is to be limited to the following uses
- Determined the exaction location of an aircraft and its relationship to other aircraft.
- Provide radar traffic advisories and basic rada services to aircraft if the benefits are more efficient and its use effective of the local control positions.
- To suggest headings or direction to VFR aircraft as a radar identification method or as an advisory aid for navigation.
- Instruction and information within the tower airspace to aircraft within its option of area.
- Ensure separation between arrivals, departures, and overflights.
LC shall manage the ATIS for KMYR
The ATIS shall be on 123.925
TRACON Information
EARDR (MYR_E_APP) is the primary "combined" radar position for Myrtle Beach Tracon. No other sectors shall be staffed until the "combined" position is in use. EARDR may delegate a portion of its airspace to WARDR.
|
WARDR (MYR_W_APP) is the secondary radar position for Myrtle Beach Tracon. EARDR may delegate a portion of its airspace to WARDR.
|
VFR Aircraft entering the Class Charlie airspace will be given a discrete beacon code.
Phraseology
{Callsign}, squawk {squawk code}.
If an aircraft departs from MYR 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
Myrtle Beach ATCT is a limited radar 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 Myrtle Beach Tower on {frequency}.
TRACON sectors give automatic releases to all departures from Myrtle Beach 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.
Note: Ensure notification with SSC, FLO, CHS or ZJX is completed before clearing aircraft to operate in the Gamecock Charlie MOA or ROBROY airspace.
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 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.
KCRE- Grand Strand
Initial Altitude for all IFR Departures is 2,000 feet. Pilots shall expect their cruise (if higher) in 10 minutes after departure.
There is no published departure procedures for Grand Strand, All aircraft will be cleared to their destination as filed.
Phraseology
{Callsign}, You are cleared to the {Arrival Airport} Airport as filed. Maintain 2,000, expect {cruise} one-zero minutes after departure. Departure Frequency {departure frequency}, squawk {squawk code}.
As the taxiways at Grand Strand are simple, there are no defined routes for taxi.
Phraseology
To Runway
{Callsign}, Runway {Number} taxi via {taxi instructions}.
To Ramp
{Callsign}, Taxi to the ramp via {taxi instructions}.
ALL IFR DEPARTURES REQUIRE RELEASE
Departure Procedures
LC will provide separation for aircraft in the LC airspace.
LC shall provide initial radar separation between successive departures.
LC has the option to assign all NON-JET aicraft runway heading or a fanned heading up to 30 degrees each direction.
Phraseology
{Callsign}, {Departure Instruction}, Wind {direction} at {speed}, Runway {Runway}, Cleared for takeoff
{Callsign}, Contact Departure {frequency}
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
Phraseology
{Callsign}, {Traffic Advisories} , Wind {direction} at {speed}, Runway {Runway}, Cleared for land
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the
TRACON. Practice Instrument Approaches shall assign runway heading and maintain 2,000 feet. Departure frequency as assigned by approach control.
Phraseology
{Callsign}, Fly Runway Heading, Climb and Maintain 2,000, Contact Approach on {Frequency}
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles
from the runway.
The active runway shall be determined based on wind and known
factors that may affect the safety of takeoff/landing operations.
Runway 23 is designated as the calm wind runway.
7110.65Z Runway Selection
LC shall assign IFR aircraft runway heading and 2,000 feet
LC must verbally coordinate with departure prior to frequency change.
Phraseology
AFTER COORDINATION WITH TRACON: {Callsign}, Fly {Heading}, Climb and Maintain {Altitude}, Contact Approach on {Frequency}
Grand Strand 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.
LC shall manage the ATIS for KCRE
The ATIS shall be on 119.625