S2: Tower and Departure

S2 adds runway control. This is where ATC becomes time-critical because every runway instruction can affect separation immediately.

S2 Objective

An S2 controller must:

• Control active runways.
• Sequence arrivals and departures.
• Integrate VFR circuits.
• Issue takeoff and landing clearances.
• Apply wake turbulence separation.
• Manage go-arounds.
• Coordinate with Approach/Departure.

S2 Prerequisites

• Hold S1 for at least 30 days.
• Log at least 50 hours on Ground/Delivery.
• Demonstrate a 3-minute traffic briefing without notes.

Tower Scan

Tower must continuously scan:

• Final approach.
• Runway surface.
• Departure queue.
• Aircraft crossing or approaching hold short lines.
• Circuit/downwind/base/final traffic.
• Missed approach and go-around paths.

Before any runway clearance, ask:

1. Is the runway clear?
2. Is final clear?
3. Is wake separation satisfied?
4. Is the aircraft lined up correctly?
5. Is there a crossing, landing, or departure conflict?

Runway Clearances

Takeoff:

"AAL123, runway 25R, cleared for takeoff."

Landing:

"DAL456, runway 25R, cleared to land."

Line up and wait:

"AAL123, runway 25R, line up and wait."

Hold short:

"AAL123, hold short runway 25R."

Cancel takeoff clearance:

"AAL123, cancel takeoff clearance. Hold position."

Go around:

"DAL456, go around. Fly runway heading, climb and maintain three thousand."

When to Use "Line Up and Wait"

Use line up and wait only when:

• The aircraft can enter the runway safely.
• A departure clearance is expected soon.
• No aircraft is landing too close.
• You will not forget the aircraft on the runway.

If there is any doubt, keep the aircraft holding short.

Departure Sequencing

A basic departure sequence considers:

• Wake category.
• Route direction.
• Aircraft performance.
• Release restrictions from Departure.
• Intersection departures.
• Pilots ready at the runway.

Good runway flow is not always first-come, first-served. Sometimes launching a fast jet before a slow prop prevents airborne conflict. Sometimes holding a departure lets an arrival land without an unnecessary go-around.

Arrival Sequencing

Tower must protect final approach. Watch for:

• Arrival spacing too close.
• Runway occupied by a slow departure.
• Aircraft slow to vacate.
• VFR circuit traffic turning base into IFR final.
• Landing clearance issued too late.

If the runway will not be clear by about 2 NM final, issue a go-around unless local procedure allows otherwise.

VFR Circuit Management

Circuit traffic needs simple, timely instructions.

Examples:

"N172AB, enter left downwind runway 25R."

"N172AB, number two, follow A320 on two-mile final."

"N172AB, extend downwind, I will call your base."

"N172AB, make short approach, runway 25R cleared touch and go."

Track every circuit aircraft by leg:

• Upwind
• Crosswind
• Downwind
• Base
• Final

Wake Turbulence

Apply the local wake turbulence standard used by the network or trainer. The practical rule is simple: larger aircraft can create dangerous wake for smaller aircraft behind them.

Be extra careful with:

• Heavy followed by light.
• Intersection departures behind a heavy departure.
• Landing behind a heavy arrival.
• Departure from the same runway after a heavy rotates late.

If unsure, increase spacing.

ATIS

ATIS gives pilots the current airport setup before they call.

Include:

• Airport name.
• Information letter.
• Time.
• Active runway.
• Wind.
• Visibility and weather if relevant.
• Altimeter.
• Approach in use.
• Departure instructions if standardized.
• Notice to pilots if needed.

Example:

"Los Angeles information Alpha. Runway 25R in use. Wind 250 at 8. Visibility greater than 10. Altimeter 29.92. IFR departures expect LOOP6. Advise on initial contact you have Alpha."

Update ATIS when meaningful elements change, such as runway, wind, weather, altimeter, approach, or important airport status.

Departure Handoff

Tower should hand aircraft to Departure when:

• The aircraft is airborne.
• It is clear of immediate runway conflict.
• Initial heading/altitude instructions are understood.
• Departure is ready to receive it.

Example:

"AAL123, contact Departure one two four point five."

Coordinate unusual departures:

"Departure, Tower, AAL123 airborne runway 25R, assigned runway heading, climbing five thousand."

S2 Emergencies

Engine failure after takeoff:

1. Keep the runway and departure path protected.
2. Ask pilot intentions if workload permits.
3. Provide runway, wind, and traffic information.
4. Coordinate with Ground and Approach.
5. Stop departures until safe.

Runway incursion:

1. Stop affected aircraft immediately.
2. Cancel takeoff clearance or send arrival around.
3. State traffic if useful.
4. Coordinate and reset the runway.

Example:

"AAL123, stop immediately."

"DAL456, go around, traffic on runway."

S2 Competency Targets

To be S2 competent, the trainee should:

• Handle at least 12 movements per hour on a single runway in calm-wind configuration.
• Apply wake turbulence separation correctly.
• Respond to circuit position reports within 15 seconds.
• Issue go-arounds by 2 NM when the runway will not be clear.
• Handoff departures with accurate altitude, heading, and speed context.
• Keep phraseology controlled under pressure.

S2 Training Sessions

Suggested structure:

1. Local airspace, tower responsibilities, and runway selection.
2. Wake turbulence, runway occupancy, and departure sequencing.
3. VFR circuits and mixed IFR/VFR operations.
4. ATIS, runway changes, and coordination with Departure.
5. Emergency simulations.
6. Live traffic consolidation and final preparation.

S2 Practical Exercises

S2 Final Test

Retest policy:

• First fail: 14-day cooldown.
• Second fail: 30-day cooldown plus mandatory remedial training.
• Third fail: senior instructor panel review.

Post-S2 Privileges

After S2 completion, the controller may:

• Mentor S1 students.
• Begin S3 training.
• Control Tower and Departure within ATCThing limits.