Updated: 2023-04-30 --- # Approach/Departure Controller Responsibilities Approach/Departure controllers are responsible for: - The safety of flight for all aircraft in the Terminal Radar Service Area (TRSA) on approaches, and in the radar pattern. - Sequencing and clearing aircraft for approaches - Sequencing and vectoring aircraft in the radar pattern - Providing vectoring services to aircraft in the TRSA, workload permitting - Transferring aircraft to tower, center or chopping due regard as appropriate # APR/DEP Airspace APR/DEP airspace is a cylindrical area 50 NM in radius centered on the airport and extending from the surface to infinity. Aircraft cannot enter this airspace without being in contact with APR/DEP. APR/DEP can establish contact and control with aircraft outside this area, and can also authorize aircraft to switch to other controllers while inside this airspace. vCSG-3 operations will have always have a unified approach/departure frequency, departing aircraft should address the controller as “departure” and inbound aircraft as “approach”, but the controller must respond to both callsigns. # Separation Requirements and minimums APR/DEP Controllers have the same separation and minimums as tower controllers, they are responsible for building the required separation for landings before handing aircraft off to tower. 3NM separation between aircraft with less than 1000 ft of altitude separation not in the pattern. (does not apply to aircraft in the same flight) 6000 ft (~20 sec) separation between subsequent takeoffs and/or landings on the same runway. (does not apply to section/interval takeoffs within a flight) No aircraft may be cleared to land while another aircraft is still on the runway, no aircraft may be cleared to takeoff or lineup and wait while another aircraft is cleared to land. Aircraft on final travel ~2.5-3 NM per minute, and it is approximately ~3 minutes from the break to final for aircraft in the overhead pattern. Give ~90 sec per aircraft in a flight to line up and depart. # Departure ## Check in Departing A/C should check in to departure with their altitude. If they have intentions other than what has been planned, they may also check in with a “request”. >[!example] Leveled off Checkin > “`[airport]` Departure, `[Callsign]`, `[altitude]`” > >[!quote] > >`A/C`: “Nellis Departure, Victory 101, 3000” >[!example] Climbing Checkin > “`[airport]` Departure, `[Callsign]`, Passing `[altitude]` for `[assigned altitude]`” >>[!quote] >>`A/C`: “Nellis Departure, Victory 101, Passing 3500 for 6000” >[!example] Climbing Checkin with request > “`[airport]` Departure, `[Callsign]` `[altitude(s)]` request” >>[!quote] >>`A/C`: “Nellis Departure, Victory 101, Passing 3500 for 6000, request” ## Initial Vector Immediately after aircraft check in, the DEP controller must place the aircraft under their control with a “Radar Contact” call, if unable to establish contact, give “Negative Contact” and request aircraft position. In either case, place the aircraft under positive control with a vector, or procedural control by clearing them either direct or as fragged. If the aircraft had a request, ask for it now. >[!example] Inital Vectors >"`[Callsign]`, `[Airport]` Departure, `[Radar contact/negative contact and position request]`, `[vector/direct/as fragged]`” >>[!quote] Examples >>- ==DEP==: “Victory 101, Nellis Departure, Radar contact, cleared direct WP1, climb and maintain FL250” >>- ==DEP==: “Victory 101, Nellis Departure, Radar contact, right 090, climb and maintain 6000” >>- ==DEP==: “Victory 101, Nellis Departure, Radar contact, cleared as fragged” >>- ==DEP==: “Victory 101, Nellis Departure, Negative contact, fly runway heading, climb and maintain 6000 and say position” >>- ==DEP==: “Victory 101, Nellis Departure, Radar contact, right 090, climb and maintain 6000, say request” ## Vectors Departure control vectors are designed to get aircraft from the airfield to a route to their destination while keeping them clear terrain and traffic. In situations where there is little terrain and limited inbound traffic, clearing aircraft direct to a WP with a discrete altitude or as fragged may be sufficient. It should be the goal of the departure controller to get all aircraft on deconflicted courses out of the airspace and get them off the frequency as soon as possible. Some potential situations and their standard responses include: - A/C is out bound to mission > clear as fragged or direct, assign discret altitude or fragged altitude - A/C looking to enter radar pattern for an approach > vectors into radar downwind - A/C outbound but traffic/terrain in course > vectors around obstacles, then cleared direct - A/C Requests holding (usually for rendezvous) > approve as requested if possible, else give holding instructions ## Checkout Once the departure controller is ready to clear an aircraft out of their airspace, they will give them a checkout call with final instructions/advisories. If the aircraft is being handed over to another controller like a center, range control, or directly to a CATCC, simply tell the aircraft to contact that controller on their frequency. >[!example] 'Warm Handshake' Checkout >“`[Callsign]`, contact `[controller]` on `[frequency]`” >>[!quote] >>==DEP==: “Victory 101, contact Nellis Range Control on 321.4” If the aircraft is not being given that “warm handshake” off to another controller, departure needs to release them from control. If the aircraft is currently under positive control, release that by telling the aircraft to “resume own navigation”, release the aircraft from general control by telling them “Radar services terminated”. Finally allow them to switch off frequency with “cleared to switch” >[!Example] 'Cold Shoulder' Checkout >“`[Callsign]`, (resume own navigation), radar services terminated, cleared to switch” >>[!quote] >>- ==DEP==: “Victory 101, Radar services terminated, cleared to switch” >>-==DEP==: “Victory 101, Resume own navigation, radar services terminated, cleared to switch” ## Flow >[!example] Standard Flow for Field Departures > `A/C`: Checks in on frequency with Altitude + request if applicable > ==DEP==: establishes control, provides initial vector, asks for request if applicable > `A/C`: Reads back, gives request if applicable > ==DEP==: gives vectors, clears direct, as needed until aircraft is outbound and deconflicted > ==DEP==: gives checkout call to aircraft > `A/C`: acknowledges and switches off frequency ## Examples >[!example] Standard example > `A/C`: “Nellis Departure, Victory 101, passing 1000 for 6000” > ==DEP==: “Victory 101, Nellis Departure, Radar contact, Cleared direct WP1, climb and maintain FL260” > `A/C`: “Victory 101, Direct WP1, FL260” > *`A/C` is clear of all potential traffic/obstacles* > ==DEP==: “Victory 101, Radar services terminated, cleared to switch” *> `A/C`: is clear of all potential traffic/obstacles* “Victory 101, Switching” >[!example] Example with vectors for obstacles or traffic and transfer to a range control > `A/C`: “Nellis Departure, Victory 101, passing 1000 for 6000” > ==DEP==: “Victory 101, Nellis Departure, Radar contact, left 090 climb and maintain 10,000” > `A/C`: “Victory 101, left 090, 10,000” > ==DEP==: “Victory 101, right direct WP1, climb and maintain FL220” > `A/C`: “Victory 101, right direct WP1, FL220” > *`A/C` is clear of all potential traffic/obstacles* > ==DEP==: “Victory 101, contact Nellis Range Control on 259.6” > `A/C`: “Victory 101, Nellis Control 259.6, switching” > [!example] Example with request for holding (LSV is the Nellis TACAN identifier) > `A/C`: “Nellis Departure, Victory 101, 3000, request” > ==DEP==: “Victory 101, Nellis Departure, Radar contact, maintain heading, climb and maintain 10,000, say request” > `A/C`: “Victory 101, this heading to 10,000, request holding for rendezvous” > ==DEP==: “Victory 101, Right 060, Cleared to hold LSV 040/25 15000, CV rendezvous, say flight modexs” > `A/C`: “Victory 101, right direct 060, Hold LSV 030/25 15000, CV, Flight is 101, 104, 105” > ==DEP==: “Victory 101 readback correct, I will send your flight to meet you” > `A/C`: “Victory 101” > *==DEP== vectors flight to join lead, rendezvous complete* > `A/C`: “Departure, Victory-1 flight of 3, complete in holding, request direct WP1” > ==DEP==: “Victory-1 flight, cleared direct WP1, contact Nellis Range Control on 254.6” > `A/C`: “Victory-1 direct WP1, Nellis Range on 254.6” # Arrivals ## Check In Arriving A/C should check in to approach with either their altitude and intentions if being handed off by another controller, or a position, altitude, intentions call if picking up control. Aircraft may include a request as well. >[!example] Control pickup check in with request >“Nellis approach, Victory 101, on the 270 radial for 56 at Angels 26, request” >[!example] Handoff check in > “Nellis approach, Victory 101, FL220, inbound” ## Establish Control After an aircraft checks in, approach should establish control over the aircraft and give local altimeter and runway in use. vCSG-3 does not normally use ATIS, this call serves as a form of ATIS, and if the inbound aircraft calls in with ATIS information, this call may be omitted. If they have a request, ask them for their request. The inbound aircraft should readback the altimeter setting. > [!example] Establish Control Call > In response to an aircraft 'inbound' call: > > “`[Callsign]`, `[airport]` Approach, `[Radar Contact/Negative Contact]`, `[airport]` altimeter `[inhg]`, `[runway]` in use, Final Bearing `[#]`” > > >[!quote] > >==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis altimeter 30.01, Runway 03L in use, final bearing 034” > >In response to an aircraft 'request': > > “`[Callsign]`, `[airport]` Approach, `[Radar Contact/Negative Contact]`, `[airport]` altimeter `[inhg]`, say your request” > >[!quote] > >==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis altimeter 30.01, Runway 03L in use, final bearing 034, say your request” ## Approach Requests Aircraft should request the type of approach they would like, as well as how that approach will terminate (fullstop, option, flight plan route, etc). >[!example] >“`[callsign]`, request (vectors) `[type of approach]`, (followed by) (`[additional approaches]`) `[approach termination]`” >>[!quote] >>- `A/C`: “Victory 101, request the TACAN W 03L fullstop” >>- `A/C`: “Victory 101, request vectors to final for the TACAN Z 03L followed by vectors to initial for the overhead break full stop” >>- `A/C`: “Victory 101, request vectors to initial for the TACAN W 03L followed by departure to the southeast” ## Approach Priority If an aircraft does not request a specific approach, it is up to the approach controller to determine what approach to use. The criteria that determine the approach include the terrain, weather, and controller workload. The general recommended priority for approaches from most to least preferred is: - Vectors to Initial for the Overhead Break - Visual Straight-in/Overhead Break - TACAN Approach to the Overhead Break (TACAN W) - Vectors to Final for the TACAN Straight-in Approach (TACAN Z) - TACAN Straight-in Approach (TACAN Z) ## Verifying an Approach Since approaches are not unique to the airfield, it is possible for an airfield to have terrain incompatible with an approach. This mostly affects the TACAN W/Z approaches, but it can render the overhead break non-viable as well. Approaches and ATC vectors must maintain 1000 ft of obstacle clearance (accepting descents below 1000ft AGL on final). In order to use the TACAN W/Z approach, the following must be true: - Along final bearing, 10NM from the airport in both directions with a 3 NM wide corridor, elevation must increase no more than 200 ft from field elevation. - Along final bearing, from 10-21 DME on the approach end, elevation must increase no more than 400 ft per NM (starting at 10 DME) from field elevation. For example, if field elevation is 0ft, then at 10 dme the elevation can be no greater than 200ft, at 11 DME no greater than 600ft, at 12 DME no greater than 1000ft, ect. If the altitudes are marginal err on the side of not authorizing the approach. If an approach meets part of the requirements, you can provide vectors until that segment, then clear the aircraft for the remainder of the approach. If the airport only fails the departure side requirements, the approach can be used with custom climb out instructions ![[Runway Diagram.png]] ## Initial Control Once an aircraft has checked in and passed any requests, the controller needs to establish either positive or procedural control over the aircraft. There is no one-size-fits-all option here, one of the simplest options is to clear the aircraft to the field and tell them to report a certain DME value (akin to the carrier “see you at 10” call. If a full procedure approach is in use, you can clear them directly to their IAF/holding fix. Workload dependant, you can simply immediately place them on vectors. In either case the two required elements are to give the aircraft a immediate instruction to follow (positive or procedural control), and then to tell them what approach to expect in order to allow them to prepare. ### Examples In response to “inbound” after A/C readback >[!example] Post Inbound Control >“`[Callsign]`, `[vector/direct]`, you can expect the `[approach in use]`” >>[!quote] >>- ==APR==: “Victory 101, cleared direct the field, descend and maintain 6000, report 10 DME, you can expect vectors to initial for the overhead break 03L” >>- ==APR==: “Victory 101, right 040, you can expect vectors to final for the TACAN Z 03L” >>- ==APR==: “Victory 101, hold on the 214 radial at 21 DME, 7000, you can expect the TACAN Z 03L” > >In response to a requested approach (assuming the plan is to approve the request) >>[!quote] >>==APR==: “Victory 101, cleared direct the field, descend and maintain 10,000, you can expect that” ## Full Procedure Approaches A full procedure approach is one where the aircraft begins the approach at the IAF and executes the entire approach procedure per the plate. The two full procedure approaches used by vCSG at the field are the TACAN W and TACAN Z. Full procedure is the default way to complete an approach (ie: if someone requests the “TACAN W 07”, it’s a full procedure). An aircraft is authorized to conduct a full approach by using the phraseology “Cleared for the `[approach]`” this implies that they are to go to the IAF (if not already there) and then execute the whole approach as it appears on the plate. The advantages of full procedure approaches is that they can be completed entirely without controller input, even NORDO. Additionally, all pilots are very familiar with the full procedure approaches. The disadvantages of full procedure approaches are that they take a long time and a great deal of airspace. ### Clearance If the aircraft is not already in holding or at the IAF, they must be given the holding position and altitude for the approach, you can clear them at this point as well if you want them to commence the approach immediately after reaching the IAF. >[!example] Approach Clearance >“`[Callsign]` hold on the `[radial]` radial `[DME]` DME, `[altitude]`, (cleared for the `[approach]`)” >>[!quote] >>- ==APR==: “Victory 101, hold on the 213 radial 21 DME, 6000” >>- ==APR==: “Victory 101, hold on the 213 radial 21 DME, 6000, cleared for the TACAN Z 03L” > >If an aircraft is already at the IAF/in holding, simply tell them they are cleared for the approach > >“`[Callsign]`, cleared for the `[Approach]`” >>[!quote] >>==APR==: “Victory 101, cleared for the TACAN W 03L” ### Altitudes Once an aircraft reads back their approach clearance, provide them the airfield elevation, platform altitude, and on final altitude. This call needs to be acknowledged, but not read back. Platform is rounded up to the next highest thousand (as are holding altitudes), final altitude and pattern altitude are rounded up to the next hundred. >[!example] >“`[callsign]`, Field elevation `[#]` ft, call platform at `[altitude]`, altitude on final `[altitude]`” >>[!quote] >>==APR==: “Victory 101, field elevation 352 ft, call platform at 6000, altitude on final 1600” ### Full Procedure Flow Standard flow for vectors to initial/final: >[!note] >Not all steps are necessarily distinct calls >[!example] Full Procedure Flow >`A/C`: _Aircraft Check in (either inbound or on waveoff from tower)_ > ==APR==: _Establish control and pass airport information_ > ==APR==: _Establish procedural control and give expected approach/clear aircraft for the approach_ >`A/C`: _Navigates to IAF/holding_ > ==APR==: _Clears aircraft for approach if not done already_ >`A/C`: _executes approach_ > ==APR==: _once A/C on final with good sequence, switch them to tower_ ### Vectors to Initial/Final Vectoring an aircraft to initial or final is where the controller uses positive control to place the aircraft somewhere on the approach, and then clears them to complete the rest of the approach under procedural control. When vectoring aircraft onto an approach, before they can be cleared for the approach, they must be placed on an intercept course with a segment of the approach (usually initial or final). Aircraft must always be placed back on the approach and cleared prior to the final approach fix. Aircraft must be given an intercept with the approach course (final bearing) that is 30 degrees or less and places them on the approach course with at least 3 miles of remaining straight away prior to the FAF. (an intercept course for a point 6 miles from the field). Additionally aircraft must be at the correct altitude for the segment of the approach they are joining. The phraseology for this is the same as for a full procedure, the difference being it can only be said when the aircraft is already on an intercept for the approach at the correct altitude. >[!example] Approach Clearance > “`[Callsign]`, cleared for the `[Approach]`” > >[!quote] > >==APR==: “Victory 101, cleared for the TACAN W 03L” ### Vectors to Initial/Final Flow Standard flow for vectors to initial/final: >[!note] >Not all steps are necessarily distinct calls >[!example] Vectors to I/F Flow > `A/C`: _Aircraft Check in (either inbound or on waveoff from tower)_ > ==APR==: _Establish control and pass airport information _ > ==APR==: _Establish Positive control and give expected approach_ > ==APR==: _Vector aircraft to <=30 degree intercept with initial/final, aircraft at correct altitude_ > ==APR==: _Direct_ “Join Final Bearing” > ==APR==: _Clears aircraft for the approach_ > ==APR==: _Directs a switch to tower_ ### Examples >[!example] Full procedure > `A/C`: “Nellis Approach, Victory 101, on the 360 radial for 50 at angels 22, inbound” > ==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis Altimeter 29.99, Runway 03L in use, final bearing 034” > `A/C`: “Victory 101, Altimeter 29.99, runway 03L, final bearing 034” > ==APR==: “Victory 101, readback correct, hold on the 214 radial for 21 DME, at 8000, expect the TACAN Z 03L approach, report established” > `A/C`: “Victory 101, 214 for 21, 8000, Wilco” > `A/C`: “Victory 101, Established in holding” > ==APR==: “Victory 101 Cleared for the TACAN Z 03L approach, Call platform at 7000” > `A/C`: “Victory 101, Cleared for the TACAN Z 03L, platform 7000” > `A/C`: “Victory 101, platform” > ==APR==: “Victory 101, Field elevation 1532, altitude on final 2800” > `A/C`: “Victory 101” > ==APR==: “Victory 101, contact tower on 234.5” > `A/C`: “Victory 101, tower on 234.5, switching” >[!example] Vectors to initial > `A/C`: “Nellis Approach, Victory 101, on the 360 radial for 50 at angels 22, inbound” > ==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis Altimeter 29.99, Runway 03L in use, final bearing 034” > `A/C`: “Victory 101, Altimeter 29.99, runway 03L, final bearing 034” > ==APR==: “Victory 101, readback correct, right 230, descend and maintain angels 12 expect vectors to initial 03L” > `A/C`: “Victory 101,right 230, down to Angels 12,roger” > ==APR==: “Victory 101, Left 210, descend and maintain angels 6” > `A/C`: “Victory 101, Left 210, angels 6” > ==APR==: “Victory 101, Left 124, descend and maintain 2800” > `A/C`: “Victory 101, Left 124, 2800” > ==APR==: “Victory 101, Left 064, join final bearing, cleared for the overhead break” > `A/C`: “Victory 101, Left 064 for final bearing, cleared break” > ==APR==: “Victory 101, contact tower on 234.5” > `A/C`: “Victory 101, tower on 234.5, switching” >[!example] Direct the field, then Vectors to final > `A/C`: “Nellis Approach, Victory 101, on the 180 radial for 50 at angels 22, inbound” > ==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis Altimeter 29.99, Runway 03L in use, final bearing 034” > `A/C`: “Victory 101, Altimeter 29.99, runway 03L, final bearing 034” > ==APR==: “Victory 101, readback correct, Cleared direct the field, Descend and maintain 3000 and report 10 DME, expect vectors to final for the TACAN Z 03L” > `A/C`: “Victory 101, Direct the field, down to 3000, We will report 10” > `A/C`: “Victory 101, 10 DME” > ==APR==: “Victory 101, right 010 and join final bearing, descend and maintain 2800 ” > `A/C`: “Victory 101, right 010 for final bearing, descend and maintain 2800” > ==APR==: “Victory 101, Field Elevation 1532, cleared for the TACAN Z 03L approach, contact tower 234.5” > `A/C`: “Victory 101, Cleared for the TACAN Z 03L, switching tower on 234.5” >[!example] Full procedure TACAN Z followed by Vectors for initial per Request > `A/C`: “Nellis Approach, Victory 101, on the 180 radial for 50 at angels 22, request” > ==APR==: “Victory 101, Nellis Approach, Radar Contact, Nellis Altimeter 29.99, Runway 03L in use, final bearing 034, say your request” > `A/C`: “Victory 101, Altimeter 29.99, runway 03L, final bearing 034, Request TACAN Z 03L followed by vectors to initial for the overhead break full stop” > ==APR==: “Victory 101, readback correct, hold on the 214 radial for 21 DME, at 8000, cleared for the TACAN Z 03L, and you can expect the rest” > `A/C`: “Victory 101, 214 for 21, 8000, Cleared for the TACAN Z 03L” > ==APR==: “Victory 101, Call platform at 7000, field elevation is 1532, altitude on final 2800” > `A/C`: “Victory 101, platform at 7000, copy all” > `A/C`: “Victory 101, Platform” > ==APR==: “Victory 101, climbout instructions: runway heading, climb and maintain 4000, contact tower 234.5” > `A/C`: “Victory 101, Copy climbout runway to 3000, switching tower on 234.5” > _aircraft executes touch and go_ > `A/C`: _on the go_ > `A/C`: “Victory 101 passing 2000 for 4000” > ==APR==: “Victory 101, Radar Contact, Right 120” > `A/C`: “Victory 101, right 120” > ==APR==: “Victory 101, right 210, descend and maintain 2800” > `A/C`: “Victory 101, right 210, 2800” > ==APR==: “Victory 101, right 004, join initial, cleared for the overhead break” > `A/C`: “Victory 101, right 004 for initial, cleared for the break” > ==APR==: “Victory 101 switch tower 234.5” > `A/C`: “Victory 101 switching 234.5”