Updated: 2023-04-29 --- # Tower Controller Responsibilities Tower controllers are responsible for: - The safety of flight of all aircraft in the Tower Airspace, Pattern, and on and around the active runway(s) - Sequencing aircraft in the pattern, including waveoffs and touch and go's - Transferring aircraft to ground or departure/approach control when appropriate - Not every situation in can be covered in the procedures in this document, all controllers must exercise good judgement in dealing with situations out of the norm. Controllers have wide latitude to make non-standard decisions for safety of flight. # Tower Airspace Tower airspace is a cylindrical area 5 NM in radius centered on the airport and extending from the surface to 2500 ft AGL. Aircraft cannot enter this airspace without being in contact with tower. Tower will often talk to aircraft outside this airspace, but everyone inside this airspace must be in contact with tower. # Separation Requirements and minimums Tower Controllers have the following separation requirements for all aircraft under their control. 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. # Departures ## Takeoff Aircraft will check into tower frequency when pushed by ground at the hold short and they are ready for takeoff, usually shortened to a simple “Takeoff” >[!example] Takeoff Call >“`[airport]` Tower, `[Callsign]`, takeoff” >>[!quote] >>`A/C`: “Nellis Tower, Victory 101, takeoff” > Tower must verify the runway is clear and no aircraft have been cleared to land. If it is safe to immediately clear the aircraft for departure respond with the take off clearance, single piloted aircraft like fighters are switched to departure on the runway after being cleared for takeoff. >[!example] Takeoff Clearance >“`[Callsign]`, `[Airport]` Tower, winds are `[direction]` at `[speed]`, runway `[RW #]` cleared for takeoff, contact departure” >>[!quote] >>==TWR==: “Victory 101, Nellis Tower, winds are 040/12, runway 03L cleared for takeoff, contact departure” ## Line up and wait You cannot clear an aircraft for takeoff with another aircraft cleared to land, or with less than 6000 ft between takeoffs, but if an aircraft is already on a takeoff roll or landing rollout, it is permissible to line another aircraft or flight up on the runway without giving them clearance to takeoff, this is done with the “line up and wait” command. A full clear for takeoff call is required to give actual takeoff clearance >[!example] Line up and Wait >“`[Callsign]`, `[runway]` line up and wait“ >>[!quote] >>==TWR==: “Victory 101, runway 03L line up and wait” If an aircraft checks into tower but the runway is in use and you are unable to use lineup and wait, respond with their position in the queue including arrivals, for instance if there was one arrival and one departure ahead of them, they would be #3 >[!example] Hold Short >“`[Callsign]`, `[Airport]` Tower, hold short `[runway]` number `[#]` for departure” >>[!quote] >>==TWR==: “Victory 101, Nellis Tower, hold short runway 03L, number 3 for departure” ## Departure Flow Standard Flow for Field Departures: >[!example] > `Aircraft`: _checks in at the hold short_ > ==TWR==: _verifies runway status_ >==TWR==: _gives takeoff clearance/line up and wait/hold short_ >>After takeoff clearance > >`Aircraft`: _takes runway and switches to departure frequency_ >`Aircraft`: _takes off, monitor them until they are clear of tower airspace_ ## Departure Examples >[!example] > `A/C`: “Nellis Tower, Victory 101, holding short 03L” > ==TWR==: “Victory 101, Nellis Tower, hold short 03L, number 3 for departure” > `A/C`: “Victory 101, hold short 03L” > _Time passes_ > ==TWR==: “Victory 101, 03L line up and wait” > `A/C`: “Victory 101, 03L line up and wait” > ==TWR==: “Victory 101, Winds 050 at 6, runway 03L cleared for takeoff, switch departure” > `A/C`: “Victory 101, runway cleared for takeoff 03L, switching” > _`A/C` takes off_ > [!example] > `A/C`: “Nellis Tower, Victory 101, holding short 03L” > ==TWR==: “Victory 101, Nellis Tower Winds 050 at 6, runway 03L cleared for takeoff, switch departure” > `A/C`: “Victory 101, cleared for takeoff 03L, switching” > _`A/C` takes off_ # Arrivals ## Landing Types The types of approaches/landings are: - “Full stop” aka “stop” for an approach where the aircraft intends to land and remain at the airport. - “Touch and Go” for an approach where the aircraft intends to execute a go around after touching down - “Low approach” for an approach where the aircraft intends to fly low along the runway (no less than 400 ft AGL) - “Option” for an approach where the aircraft requests the option to do a full stop, touch and go or low approach Clearing an aircraft “to land” (full stop), for a “touch and go”, or “low approach” clears the aircraft for that type ONLY, clearing the aircraft for the option clears them to do any of the above ## Check In A/C will be switched by approach control to tower frequency when they are on final bearing for a straight in or initial. Aircraft should check in with the approach they are on and the type of landing, if they are on a straight in approach and configured, they should report gear down. >[!example] Straight in Checkin >“`[airport]` Tower, `[Callsign]`, `[approach]` `[type of landing]`, down and locked” >>[!quote] >>`A/C`: “Nellis Tower, Victory 101, TACAN Z 03L, stop, down and locked” >[!example] Pattern Checkin >“`[airport]` Tower, `[Callsign]`, `[NM]` Initial `[runway]`, `[type of landing]`” >>[!quote] >>`A/C`: “Nellis Tower, Victory 101, 6 mile initial 03L, option” ## Overhead Break After aircraft check in at initial for the overhead break, verify that proper spacing exists for all other aircraft in the pattern, aircraft should not be cleared for the break unless they are #1 with interval. Aircraft may request an SHB (Shit Hot Break) which indicates they will break at the runway threshold, only approve this if the pattern is empty. >[!example] Break Approval >`[Callsign]`, `[airport]` Tower, `[direction]` break approved, report abeam with the gear” >>[!quote] >>==TWR==: “Victory 101, Nellis Tower, left break approved, report abeam with the gear” If aircraft check in and you are unable to clear them for the break due to traffic, tell them what you want them to do, usually it will be to extend the upwind. Clear them to break when they become #1 with interval >[!example] Extend Upwind >“`[Callsign]`, continue upwind, number `[number of aircraft ahead]` for the break” >>[!quote] >>==TWR== “Victory 101, continue upwind, number 3 for the break” ## Landing Clearance Once an aircraft is on final or at the abeam point in the overhead break, they can be cleared to land. Remember that there cannot be aircraft currently on the runway when you give a landing clearance. If the aircraft has already reported the status of their gear, give a “roger gear” call, if the aircraft has not reported their gear say “gear should be down” the landing clearance including runway must always be read back. >[!example] >“`[Callsign]`, `[roger gear/gear should be down]` winds `[direction]``[speed]`, runway `[RW#]`, cleared `[to land/touch and go/low approach/option]`” >>[!quote] >>==TWR==: “Victory 101, roger gear, winds 050 at 10, runway 03L, cleared to land” If an aircraft cannot be cleared yet, simply give instructions on what you want them to do, if you expect to be able to clear them before they would reach short final, simply “continue” will work ## Rollout Once it is clear the aircraft is committed to a full stop landing and will be able to exit the runway, give an initial taxi instruction and have them contact ground. >[!example] >“`[Callsign]`, off `[left/right]` when able, contact ground `[frequency]`” >>[!quote] >>==TWR==: “Victory 101, off left when able, contact ground 121.9” ## Arrival Flow Standard Flow for Field Arrivals: >[!example] >`A/C`: _Checks in on frequency with approach/initial, type of landing, and gear_ >`A/C`: _at the Break_ >==TWR==: _verifies pattern is clear enough, approves break_ >`A/C`: _At Abeam/Straight in_ >==TWR==: _clears aircraft to land_ >`A/C`: _Lands_ >==TWR==: _gives aircraft off left/off right instructions_ >`A/C`: _taxis clear of the runway and switches to ground_ ## Arrival Examples >[!example] Example Break >`A/C`: “Nellis Tower, Victory 101, 6 mile initial 03L, option” >==TWR==: “Victory 101, Nellis tower, left break approved, report abeam” >`A/C`: “Victory 101” > _`A/C` reaches abeam_ > `A/C`: “Victory 101, Abeam, down and locked" > ==TWR==: “Victory 101, roger gear, winds 050 at 10, runway 03L, cleared for the option” > `A/C`: “Victory 101, down and locked, cleared option 03L” > _`A/C` Lands_ > ==TWR==: “Victory 101, off left when able, contact ground 121.9” > `A/C`: “Victory 101, 121.9 Wilco” >[!example] Example Final/Straight In > `A/C`: “Nellis Tower, Victory 101, on the TACAN Z 03L, fullstop, gear down and locked” > ==TWR==: “Victory 101, Nellis tower, Roger Gear, Report 3 DME” > `A/C`: “Victory 101” > _`A/C` reaches 3 DME > `Aircraft`: “Victory 101, 3 DME” > ==TWR==: “101, winds 050 at 10, runway 03L, cleared to land” > `A/C`: “Victory 101 cleared to land 03L” > `A/C` Lands_ > ==TWR==: “Victory 101, off left when able, contact ground 121.9” > `A/C`: “Victory 101, 121.9 Wilco” ## Waveoff/Touch and go Wave off and touch and go procedures are the same from the controller perspective with the exception that the controller can initiate a waveoff if they believe unsafe conditions exist. Controllers should wave off anytime there is a possibility of an unsafe situation, go arounds are free. An unstable approach, confusion as to landing clearance, or any doubt as to the position of an aircraft are all good reasons to wave an aircraft off. Aircraft on a waveoff or touch and go should not be given commands after the waveoff/touch and go until they reach 400 ft AGL. Ideally give a runway heading climb to a safe position. If the aircraft is clearly stable, above 400ft AGL, able to maintain visual with the field and #1 with interval, clear them to enter the down wind. Otherwise, have them continue upwind or give climbout instructions and pass them back to approach, as appropriate. >[!example] Aircraft Initiated > `A/C`: _Waves off and begins to climb_ > `A/C`: “Victory 101, waveoff” > `A/C`: _is above 400ft AGL and stable_ > ==TWR==: “Victory 101, clear downwind when able” > `A/C`: “Victory 101” >[!example] TWR Initiated > _Fouled runway in bad weather_ > ==TWR==: “Victory 101 waveoff” > `A/C`: “Victory 101 waving off” > `A/C`: _is above 400ft AGL and stable_ > ==TWR==: “Victory 101, Foul runway, Fly runway heading, climb and maintain 1500, contact approach 245.6” > `A/C`: “101, runway heading to 1500, approach on 245.6”