View source for Daytona Beach Intl ATCT/TRACON

== [[Table of Updates]] ==
{| class="wikitable" style="width: 100%;"
|+
!Date
!Revision
!Items Revised
|-
|16 February 2023
|A
|Updated Satellite Release for Departures to contain IFR release
|-
|10 October 2023
|B
|Update of Format and Limit Radar Tower Information
|-
|31 January 2024
|C
|Update of Primary Tracon Facility and appropriate splits
|}

== [[Area Information]] ==
{| class="wikitable" style="width: 100%;"
|+
!ICAO Code
!Airport Name
!Airspace
!IFR Beacon Codes
!VFR Beacon Codes
|-
|KDAB
|Daytona Beach International Airport
|C
|3001-3077
|3001-3077
|}
{| 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 Daytona Beach Air Traffic Control Tower (DAB 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>
<b>Distribution</b><br>
This order is distributed to all Jacksonville ARTCC personnel.<br>
| style="width: 30%;" |[[File:DAB.JPG|200px|thumb|left|Daytona Beach International Airport via Google Maps]]
|}
== [[Operational Positions]] ==
{| class="wikitable" style="width: 100%;"
|+DAB ATCT
!Position
!Radio Name
!Callsign
!Relief Callsign
!Symbol
!Frequency
|-
|Clearance Delivery
|Daytona Beach Clearance Delivery
|DAB_DEL
|DAB_1_DEL
|5DD
|119.300
|- style="color: RED;"
|Ground
|Daytona Beach Ground North
|DAB_N_GND
|DAB_N1_GND
|5NG
|121.900
|-
|Ground
|Daytona Beach Ground South
|DAB_S_GND
|DAB_S1_GND
|5SG
|124.250
|- style="color: RED;"
|Tower
|Daytona Beach Tower North
|DAB_N_TWR
|DAB_N1_TWR
|5NT
|120.700
|-
|Tower
|Daytona Beach Tower South
|DAB_S_TWR
|DAB_S1_TWR
|5ST
|118.100
|}
{| class="wikitable" style="width: 100%;"
|+DAB TRACON
!Position
!Sector Name
!Callsign
!Relief Callsign
!Symbol
!Frequency
|-
|H
|High Radar
|DAB_H_APP
|DAB_1H_APP
|5H
|125.725
|-
|M
|Mateo Radar
|DAB_M_APP
|DAB_1M_APP
|5M
|118.850
|-
|L
|Lamma Radar
|DAB_L_APP
|DAB_1L_APP
|5L
|127.075
|- style="color: RED;"
|N
|North Radar
|DAB_N_APP
|DAB_1N_APP
|5N
|125.800
|-
|S
|South Radar
|DAB_S_APP
|DAB_1S_APP
|5S
|125.350
|-
|E
|East Radar
|DAB_E_APP
|DAB_1E_APP
|5E
|123.900
|-
|W
|West Radar
|DAB_W_APP
|DAB_1W_APP
|5W
|126.550
|}
<span style='color:red;'>Sector in Red is the primary sector.</span>

== [[Clearance Delivery]] ==
===Clearance Delivery Responsibilities===
The Clearance Delivery Controller Must:<br>
<ul>
<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>
===Pre-Departure Clearances===
<div style=color:red;>Pre Departure Clearances are not authorized at this airport.</div>

=== IFR Departures ===
<tabs>
<tab name="Route">
===Planned/Amended Routing===
All Turbojet/Turboprop aircraft departing to the north shall be assigned the ROYES # SID then as filed unless a route amend is necessary. All other aircraft shall be <i>"Cleared as filed"</i> unless a route amendment is necessary. All routes must comply with LOA-approved standards. Aircraft unable to accept the preferred route require coordination between all affected facilities.<br>
</tab>
<tab name="Altitude">
===Assigned Altitudes===
<u>Piston/Helicopter:</u> Instruct pilots that are not conducting practice approaches to maintain 3,000 feet and to expect filed cruise altitude (If higher) ten minutes after departure. Instruct pilots who are conducting practice approaches to maintain 2,000 feet. All filed cruise altitudes must be checked for validity for the direction of flight.<Br>
<u>Turboprop/Jets:</u> Instruct pilots that are not conducting practice approaches to maintain 4,000 feet and to expect filed cruise altitude (If higher) ten minutes after departure. Instruct pilots who are conducting practice approaches to maintain 3,000 feet. All filed cruise altitudes must be checked for validity for the direction of flight.<Br>
</tab>
<tab name="Frequency">
===Departure Frequency===
The Primary Departure Frequency is DAB_H_APP on 125.725. Updates to the Departure Frequency will be given by the TRACON controller.
</tab>
<tab name="Squawk">
===Squawk Assignment===
All IFR Squawk codes will be auto-assigned by the controller client. <br>
It should assign a code between 3001-3077. Controllers shall not change the auto-assigned code if a code between 3001-3007 is not assigned.
</tab>
</tabs>

=== VFR Departures ===
<tabs>
<tab name="Clearance">
===Clearance===
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 name="Altitude">
===Assigned Altitudes===
<b>Not Remaining in the Pattern</b><br>
Jet: VFR aircraft shall be instructed to maintain VFR at or below 4,000.<br>
Turboprops:  VFR aircraft shall be instructed to maintain VFR at or below 4,000.<br>
Props:  VFR aircraft shall be instructed to maintain VFR at or below 3,500.<br>
</tab>
<tab name="Frequency">
===Departure Frequency===
Aircraft not remaining in the pattern shall be given the Departure Frequency is DAB_H_APP on 125.725.<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 for all traffic not remaining in the pattern. <br>
</tab>
</tabs>
== [[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)<br>
GC1 and GC2 has control of all movement areas excluding the designated active runway(s).<br><br>
[[File:DABGCSPLIT.JPG]]
===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"<br>
===Ground Operations===
The preferred ground traffic flow is southbound on Taxiway E and northbound on Taxiway W. Under normal circumstances and unless coordinated otherwise, all taxiways are one-way taxiways <br><br>
[[File:WEDAB.JPG]] <br><br>
<h3>Departures</h3>
During high volume scenarios and when Runway 7L/25R is the primary runway, taxi all northbound aircraft to Runway 7L/25R. All southbound aircraft and VFR pattern aircraft should be taxied to Runway 7R/25L, unless an operational advantage will occur or performance characteristics dictate otherwise.<br>
===Intersection Departures===
Ground Control must advise local control of all intersection departures verbally.<br>
===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===
<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."
===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>
===Taxi Operations===
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>
===Split Ground Procedures===
The transfer of control point for northbound traffic is the hold short line south of Runway 7L/25R.<br>
The transfer of control point for southbound traffic is the north edge of Taxiway Papa at Taxiway Echo and Runway 16/34. GC1 must coordinate with GC2 for all other southbound crossings. <br>
<i> If flight strips are in use, transfer strip prior to the aircraft reaching the transfer of control point. </i>
===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. <br>
East Operations 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]

=== Area of responsibility ===
LC is divided into LC1 and LC2 as required for volume of GA traffic.<br><br>
<b>LC1</b><br>
LC1 area of responsibility includes the airspace depicted. Airspace is defined as surface to 1,500 feet. LC1 shall be responsible for movements on Runway 7L/25R and Runway 16/34.Runway 7L is left pattern. Runway 25R is right pattern.<br>
<b>LC2</b><br>
LC2 area of responsibility includes the airspace depicted. Airspace is defined as surface to 1,500 feet. LC2 shall be responsible for movements on Runway 7R/25L. Runway 25L is left pattern. Runway 7R is right pattern.<br>
[[File:DABLC1LC2AR.JPG]]

=== Arrival Procedures ===
LC shall be responsible for the separation of all arrival aircraft that have been handed off by TRACON from all departing aircraft still under LC jurisdiction<br>
Practice Instrument Approaches: Issue special instructions as verbally coordinated with the TRACON. Departure frequency as assigned by approach control.<br>
LC shall NOT change the approach sequence without coordination. Communication transfer must be completed prior to five nautical miles from the runway.
<br>

=== Automatic Terminal Information Service ===
LC shall manage the ATIS<br>
The ATIS shall be on 132.875.

=== 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>
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 Procedures ===
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, jet and turboprop departures shall be assigned a 070 heading in East operations, and a 250 heading in West operations. Prop departures shall be released on approved fan headings.<br>
<i>Note: LC2 must obtain a release from LC1 for all IFR departures.</i>
<br><br>
<B>Departure Transition Area</b><br>
The Departure Transition area or Departure Corridor is defined as the area that LC is authorized to depart aircraft into and through E-AP and W-AP without coordination, unless specified otherwise in this order. This airspace extends from Tower airspace out to 8 miles and surface to 4000 as depicted<br>
[[File:DABDTA.JPG]]
<br><br>
<B>Departure Headings</b><br>
<u>Turbojet/Turboprops</u>
When Runway 7L is primary, all departures off of 7L, 16, and 34 shall be given a heading of 070.<br>
When Runway 25R is primary, all departures off of 25R, 16, and 34 shall be given a heading of 250.<br>
<br>
<u>Prop Departure Fan Headings</u><br>
[[File:DABPROP.JPG]]


=== Go Around/ Unplanned Missed Approaches ===
<B>LC must verbally coordinate with departure prior to frequency change.</b><br>
<u>Turbojets/Turboprops:</U> The controller will assign runway heading and 3,000 unless otherwise stated.<br>
<u>Piston:</U> The controller will assign runway heading and 2,000 unless otherwise stated.<br>

=== Land and Hold Short ===
LAHSO operations are authorized at DAB. During LAHSO Operations, if requested by the pilot, issue the following available distances:<br>
<ul>
<li>Runway 16, available landing distance 2,900 feet.</li>
<li>Runway 7L, available landing distance 7,500 feet.</li>
<li>Runway 34, available landing distance 2,564 feet.</li>
</ul>

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

=== Visual Tower ===
Daytona International ATCT is a visual/VFR tower with limited radar.T he use of vSTARS display is authorized. It shall not initiate or accept any radar handoffs and shall not initiate control/start track on any target.

== [[TRACON Information]] ==
=== Operations ===
North (DAB_N_APP) is the primary "combined" radar position for Daytona Beach Tracon. No other sectors shall be staffed until the "combined" position is in use. Delegation may occur as below.<br>
<br>
<b>2-way split</b><br>
North can split high/low with Mateo (DAB_M_APP).<br>
DAB_N_APP shall be responsible for all traffic within N_APP, S_APP, E_APP, W_APP. DAB_N_APP may delegate its sectors to other new controllers. <br>
DAB_M_APP shall be responsible for all traffic within H_APP, M_APP, and L_APP. DAB_M_APP may delegate its sectors to other new controllers.<br><br>

<b>Low Split</b><br>
Note: Low split can be authorized only after the 2-way split has occurred.<br>
The selection of the Other Tracon shall be based on the departure flow of the field.<br>
W_APP during West Ops<br>
E_APP during East Ops<br>

=== TRACON Airspaces ===
<tabs>
<tab name="DAB_H_APP">
<h3>Responsibility</h3>
High Radar is responsible for the safe and expeditious movement of air traffic within the delegated airspace.<br><br>
<b>North Arrival Flow</b><br>
Enroute control and JAX TRACON will assign arrival aircraft to cross 15 NM north of OMN at 12,000’ or TTHOR via the TTHOR# STAR at 12,000’ and hand-off to H-AP.  H-AP shall assign aircraft direct OMN and decent to 8,000’ and hand-off to M-AP <br>

<br><br>
[[File:DABHAPP.JPG]]

</tab>

<tab name="DAB_M_APP">
<h3>Responsibility</h3>
MATEO Radar is responsible for the safe and expeditious movement of air traffic within the delegated airspace.<br><br>
<b>North Arrival Flow</b><br>
M-AP shall instruct aircraft to cross OMN at 6,000’. M-AP shall turn aircraft heading 070 or 260 (depending on airport operations) at OMN and descend aircraft to 4,000’. Afterwards, M-AP will hand-off to E-AP or W-AP.<br>


<br><br>
[[File:DABMAPP.JPG]]

</tab>

<tab name="DAB_L_APP">
<h3>Responsibility</h3>
LAMMA Radar is responsible for the safe and expeditious movement of air traffic within the delegated airspace.<br><br>
<b>South Arrival Flow</b><br>
F11 TRACON will assign arrival aircraft to cross the TRACON border at no higher than 6,000’. F11 will hand-off to L-AP.<br>
L-AP shall descend aircraft to 4,000’.<br>
L-AP shall turn aircraft onto a downwind leg heading 070 or 260 (depending on airport operations). Afterwards, L-AP will hand-off to E-AP or W-AP.<br>

<br><br>
[[File:DABLAPP.JPG]]

</tab>

<tab name="DAB_N_APP">
<h3>Responsibility</h3>
N-AP is responsible for the arrival sequence when runway 16 is the primary runway.  When runway 7 or 25 is the primary runway, North Radar must coordinate with the appropriate arrival sector for aircraft conducting LAHSO to Runway 16. N-AP is responsible for the safe and expeditious movement of air traffic within the delegated airspace.
<br><br>
<b>East Ops</b>
[[File:DABNEASTAPP.JFP.JPG]]<br><br>
<b>West Ops</b>
[[File:DABNWESTAPP.JPG]]
</tab>

<tab name="DAB_S_APP">
<h3>Responsibility</h3>
 S-AP is responsible for the safe and expeditious movement of air traffic within the delegated airspace. 
<br>
S-AP must vector aircraft arriving from the south to a mid field right downwind for Runway 7R, or mid field left downwind for Runway 25L. Arrivals for Runway 7R/25L must be restricted to a minimum of 1,500 feet unless otherwise coordinated and approved by LC2. South is responsible to advise LC2 that aircraft are unable to maintain 1500 feet.<br>
S-AP is responsible for the arrival sequence when runway 34 is the primary runway.<br>
S-AP owns the IFR altitude up to 1500’ in the inlet shelf.<br>

<br><br>
<b>East Ops</b>
[[File:DABSEAPP.JPG]]<br><br>
<b>West Ops</b>
[[File:DABSWAPP.JPG]]

</tab>

<tab name="DAB_E_APP">
<h3>Responsibility</h3>
E-AP is responsible for the safe and expeditious movement of air traffic within the delegated airspace.  When E-AP airspace is shared between the N-AP and S-AP positions, split the E-AP airspace along the extended centerline of runway 7L/25R. The E-AP position log and frequency must normally be combined to S-AP.<br>
The E-AP controller must assign headings to departing aircraft that will not cross the western boundary (or extended western boundary) of E-AP airspace.<br>
The receiving controller has control of the aircraft for turns toward the receiving controller’s airspace on contact.<br>
When departing east, large/turbojet departures may not be turned until leaving 3000 feet or the shoreline, whichever occurs first. <br>
The E-AP controller must keep IFR traffic AOA 2,500’ over, or within 1.5nm, of the Inlet shelf.<br><br>


<b>North Arrival Flow</b>
E-AP shall descend aircraft to 3,000’ and enter aircraft onto final. <br>
<br>
<b>South Arrival Flow</b><br>
E-AP shall descend aircraft to 2,000’ and enter aircraft onto final. <br>
<br>
<b>East Ops</b>
[[File:DABEEAPP.JPG]]<br><br>
<b>West Ops</b>
[[File:DABEWAPP.JPG]]


</tab>

<tab name="DAB_W_APP">
<h3>Responsibility</h3>
W-AP is responsible for the safe and expeditious movement of air traffic within the delegated airspace.<br>
W-AP must normally consolidate to S-AP. When W-AP airspace is shared between the N-AP and S-AP positions, split the W-AP airspace along the extended centerline of Runway 7L/25R. The W-AP position log and frequency must normally be combined to S-AP.
<br>
The W-AP controller must assign headings to departing aircraft to keep the aircraft within the confines of departure airspace.<br>
The receiving controller has control of the aircraft for turns toward the receiving controller’s airspace on contact.<br>
<br>

<b>North Arrival Flow</b>
W-AP shall descend aircraft to 3,000’ and enter aircraft onto final. <br>
<b>South Arrival Flow</b><br>
W-AP shall descend aircraft to 2,000’ and enter aircraft onto final. <br><br>

<b>East Ops</b>
[[File:DAYWEAPP.JPG]]<br><br>
<b>West Ops</b>
[[File:DAYWWAPP.JPG]]

</tab>
</tabs>

=== Arrival Procedures-General ===
E-AP or W-AP (Depending Ops) is responsible for establishing the approach sequence for all arrivals. Use Table 11 for determining arrival runway assignments. <br>
7L or 25R shall be assigned to the Turbojet/Prop Arrivals and VFR arrivals from the North<br>
7R or 25L shall be assigned to the VFR arrivals from the South<br>
16 or 34 shall be assigned when the primary runway<br>
All arriving/enroute aircraft shall be vectored as not to conflict with departing aircraft.  Communication transfer of arriving aircraft to LC must be accomplished no later than three but no earlier than ten nautical miles from the end of the arrival runway.<br>
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.<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. When runway assignment is other than primary, scratchpad entries should be used.
<Br><br>


=== Departure Procedures-General ===
During standard operations, aircraft shall be assigned runway heading climbing to their initial altitude. Aircraft who filed a cruise altitude below 4,000’ will contact E-AP, W-AP, N-AP, or S-AP. Aircraft who filed a cruise altitude at or above 4,000’ will contact M-AP or L-AP depending on departure direction.<br>
E-AP, W-AP, N-AP, and S-AP shall climb aircraft to their cruise altitude and turn departure aircraft on course as soon as practical.<br>
M-AP and L-AP shall climb aircraft to 7,000’ and turn departure aircraft on course as soon as practical. <br>
If aircraft’s cruise altitude is above 7,000’, M-AP or L-AP shall hand-off to H-AP. H-AP shall climb departure aircraft to 11,000’ and ensure aircraft are on course prior to hand-off to neighboring TRACONs or enroute positions.<br>
Aircraft on the ROYES# shall be identified with ROY in the departures scratchpad.<br><br>

=== General 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 11,000 or less if filed.<br>
Provide airspace for automatic departures and radar final.<br>
Provide airspace for missed approach on all runways.<br>
Automatic pointouts are authorized from Lamma and Mateo Arrival to East and West Radar for Turbojet/Turboprop departures.<br>

=== Handoff and Radar Tracking ===
Daytona International ATCT is a VFR tower. No radar handoffs shall be initiated to LC.<br>
TRACON controllers shall not drop the track on any arriving aircraft. This allows a controller to maintain radar identification during missed approach.

=== Orlando Area (F11) Arrivals ===
Arrivals into F11 satellites via the TTHOR# STAR shall be descended to 5000 feet by LOKII and transferred to the appropriate F11 Satellite Sector<br><br>

=== Release and Rolling Calls ===
TRACON sectors give automatic releases to all departures from Daytona 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.
<br><br>

===Satellite Fields===
TRACON must coordinate with the satellite fields’ ATCTs prior to approving overflights through Class D airspace. The restrictions are as follows:<br>
<b>KEVB:</b> Restriction: Below 1,200'<br>
<b>KFIN:</b> Restriction: AOB: 1,500'<br>
<B>KOMN:</b> Restriction: Below: 1,200' <br>
<br>
<u>IFR Clearances</u>
All routes must comply with approved standards between facilities. Aircraft unable to accept approved routes, the route must not be cleared until coordination has occurred between all affected facilities.<br>
Aircraft shall be cleared as filed unless otherwise coordinated with the TRACON controller.<br>
Aircraft departing from satellite airports shall receive an initial altitude of 2,000’. <br>
<br>
<h3>Departure Releases</h3>
All IFR departing aircraft must receive a release from the appropriate TRACON controller.<br>
IFR/SVFR departures should receive a departure heading to remain clear of KDAB traffic. If no departure heading is specified, the aircraft shall be released on runway heading. <br>
<br>
<h3>VFR Departures</h3>
Unless VFR aircraft are receiving flight following, they shall be instructed to squawk VFR and sent to UNICOM/CTAF once clear of conflict after departure.

===Sequencing===
For piston aircraft, 2.5 NM separation may be applied between aircraft established on the final approach course to either Runway 7L or 25R within 10 NM of the landing runway when all provisions of the FAAO 7110.65 are met.

===Sectorization Description ===
The primary “combined” radar position shall be High Radar (H-AP). No other sectors shall be staffed until the “combined” position is already in use. <br>

Once H-AP is in use, H-AP may delegate a portion of its airspace to MATEO Radar (M-AP) and LAMMA Radar (L-AP). <br> 
Once M-AP and L-AP are in use, M-AP and L-AP may delegate a portion of their airspaces to EAST Radar (E-AP), West Radar (W-AP), North Radar (N-AP), or South Radar (S-AP). If only one low sector is staffed, N-AP shall be the combined position.
<br>
Unless otherwise coordinated, All sectors are responsible for their areas depicted <br> 
<br>

=== VFR Aircraft within TRACON ===
VFR Aircraft entering the Class Charlie airspace will be given a discrete beacon code.<br>
If an aircraft departs from DAB 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]
<br>