It is the overlying radar controller's responsibility to separate IFR arrivals and departures out of the field. In order to ensure this separation into/out of the tower environment, a departure release is required. An IFR departure release is a takeoff authorization from the overlying radar controller for each individual IFR departure.
When requesting a departure release you need to include the following three items in the request:
Callsign
Runway
Routing - SID/Initial heading/etc.
The controller can respond with any of the following:
Released - This means that the pilot is authorized to depart.
Released, <heading> - This means that the pilot is authorized to depart and that you shall instruct the pilot to fly a particular heading after departure.
Hold for Release - This means the pilot is not authorized to depart yet, and usually the controller will call you back when the aircraft can be released.
When released, the controller has a 3 minute window to get the aircraft airborne to prevent tying up the protected airspace.
EXAMPLE:
AFW TWR: "Regional Approach, Alliance Tower."
REG APP: "Regional Approach"
AFW TWR: "Request release N123AB, runway 16R, runway heading"
REG APP: "N123AB Released, CB"
AFW TWR: "MK"
When are IFR Releases Required?
If you are working a class Bravo, Charlie, or Delta tower associated with it's own TRACON, IFR releases are not required, unless dictated by SOP.
Examples: ACT, MAF, SPS, MLU, LBB, SJT, etc.
If you are working any other class Delta tower, IFR releases are required for every individual IFR departure from the overlying radar controller.
Examples: CNW, PWA, AFW, CSM, DTN, etc.
5−8−2. INITIAL HEADING
a. Before departure, assign the initial heading to be flown if a departing aircraft is to be vectored immediately after takeoff.
PHRASEOLOGY− FLY RUNWAY HEADING. TURN LEFT/RIGHT, HEADING (degrees).
b. Issue an altitude to maintain with the initial heading when the heading will take the aircraft off a departure procedure that contains both a published lateral path to a waypoint and crossing restrictions.
c. When conducting simultaneous parallel runway departures utilizing RNAV SIDs, advise aircraft of the initial fix/waypoint on the RNAV route.
PHRASEOLOGY− RNAV to (fix/waypoint), RUNWAY (number), CLEARED FOR TAKEOFF.
5−8−3. SUCCESSIVE OR SIMULTANEOUS DEPARTURES
Separate aircraft departing from the same airport or adjacent airports in accordance with the following minima, provided radar identification with the aircraft will be established within 1 mile of the takeoff runway end, and courses will diverge by at least the minimum required, as stated below.
NOTE− RNAV SIDs specific to this paragraph are those SIDs constructed with a specific lateral path that begins at the departure end of the runway.
a. Between successive departures from the same runway or parallel runways separated by less than 2,500 feet− 1 mile if courses diverge by 15 degrees or more immediately after departure (10 degrees when both aircraft are flying an RNAV SID).
b. Between simultaneous departures departing in the same direction from parallel runways, authorize simultaneous takeoffs if the centerlines are separated by at least 2,500 feet and courses diverge by 15 degrees or more immediately after departure (10 degrees when both aircraft are flying an RNAV SID).
d. Between aircraft departing from diverging runways:
1. Nonintersecting runways. Authorize simultaneous takeoffs if runways diverge by 15 degrees or more.
2. Intersecting runways which diverge by 15 degrees or more. Authorize takeoff of a succeeding aircraft when the preceding aircraft has passed the point of runway and/or takeoff course intersection.
5−8−4. DEPARTURE AND ARRIVAL TERMINAL.
Except as provided in Paragraph 5−8−5, Departures and Arrivals on Parallel or Nonintersecting Diverging Runways, separate a departing aircraft from an arriving aircraft on final approach by a minimum of 2 miles if separation will increase to a minimum of 3 miles within 1 minute after takeoff.
Practically Speaking - If there is an IFR arrival inside of a 2 mile final for the airport, you cannot clear an IFR aircraft for takeoff.
5−8−5. DEPARTURES AND ARRIVALS ON PARALLEL OR NONINTERSECTING DIVERGING RUNWAYS
Authorize simultaneous operations between an aircraft departing on a runway and an aircraft on final approach to another parallel or nonintersecting diverging runway if the departure course diverges immediately by at least 30 degrees from the missed approach course until separation is applied and provided one of the following conditions are met:
a. When parallel runway thresholds are even, the runway centerlines are at least 2,500 feet apart.
c. When nonintersecting runways diverge by 15 degrees or more and runway edges do not touch.
3−9−3. DEPARTURE CONTROL INSTRUCTIONS
b. After takeoff.
1. When the aircraft is about 1/2 mile beyond the runway end, instruct civil aircraft, and military transport, and cargo types to contact departure control, provided further communication with you is not required.
IFR aircraft executing a missed approach need to be on a valid IFR routing/altitude that keeps them clear of terrain/obstructions. There are 3 methods we can use to ensure that this is obtained:
1. Published Missed - All instrument approaches have a published missed approach depicted on the chart. Aircraft may be instructed to "Fly the published missed approach" and contact departure. Note that aircraft conducting a visual approach do not have a published missed approach, and therefore should not be instructed to do so.
2. Heading/Altitude - Because IFR aircraft need to be positively separated with terrain/obstructions, only use published headings/altitudes prescribed in the minor reference guide or the applicable SOP. "Fly runway heading, climb and maintain 3,000"
3. Pattern Entry - If an IFR aircraft is on a visual approach or circling approach, you may instruct the aircraft to enter the traffic pattern for landing. Note that this procedure is not recommended at airports where the landing sequence is set by approach when traffic volume is higher. "Enter right traffic runway 17"