S3: Approach and Control

S3 is radar control. The controller now manages aircraft in three dimensions: position, altitude, speed, and time.

S3 Objective

An S3 controller must:

• Sequence arrivals.
• Vector aircraft efficiently.
• Issue climb, descent, heading, and speed instructions.
• Maintain separation in terminal airspace.
• Manage departures after Tower handoff.
• Handle go-arounds and emergencies.
• Coordinate with Tower, adjacent Approach sectors, and Control sectors.

S3 Prerequisites

• Hold S2 for at least 60 days.
• Log at least 100 hours on Tower/Departure.
• Demonstrate holding-pattern knowledge within trainer standards.

Radar Scan

Radar control depends on prediction. Do not stare at one aircraft.

Scan cycle:

1. Arrival stream.
2. Departure stream.
3. Conflicts within 5 minutes.
4. Aircraft needing descent.
5. Aircraft needing speed control.
6. Handoffs and coordination messages.
7. Weather or route deviations.

Radar Identification

Before providing radar control, know which target belongs to which callsign. Use the method approved by the local procedure or trainer.

Do not issue radar vectors to an aircraft you have not identified unless local procedure allows it.

Basic Vectoring

Heading instructions:

"AAL123, fly heading two seven zero."

Turn direction:

"AAL123, turn left heading two two zero."

Vector for sequence:

"DAL456, turn right heading three four zero, vector for spacing."

Resume own navigation:

"AAL123, resume own navigation direct DAG."

Altitude Control

Climb:

"AAL123, climb and maintain one three thousand."

Descent:

"DAL456, descend and maintain six thousand."

Crossing restriction:

"DAL456, cross SMO at or above seven thousand."

Approach descent planning must happen early. If an aircraft is too high at 20 NM, it will still be too high at 10 NM unless you fix it.

Speed Control

Common arrival speed gates:

• 220 knots on downwind or early base.
• 190 knots before intercept.
• 160 knots to final or 5 NM final, depending on local practice.

Examples:

"DAL456, reduce speed two two zero knots."

"DAL456, maintain one six zero knots until five-mile final."

Cancel speed restriction:

"DAL456, resume normal speed."

Speed control is not a replacement for vectoring. Use speed to fine-tune spacing, not to solve a broken sequence at the last second.

Descent Planning

A simple planning rule is 3 NM per 1000 ft of descent, plus extra distance for slowing.

Example:

• Aircraft at 12000 ft.
• Needs 3000 ft at final approach fix.
• Descent needed: 9000 ft.
• Distance needed: about 27 NM, plus extra for speed reduction.

If the aircraft is fast, high, or with tailwind, start earlier.

Sequencing Arrivals

Build a landing order before aircraft reach the final turn.

Consider:

• Distance to runway.
• Altitude.
• Speed.
• Aircraft type.
• Wake category.
• Route direction.
• Pilot responsiveness.
• Runway configuration.

Techniques:

• Extend downwind for spacing.
• Use speed reduction early.
• Turn base at different distances.
• Assign vectors across final only if safe and coordinated.
• Use holds when traffic exceeds capacity.

Example sequence:

"AAL123, reduce speed two one zero knots, expect number one."

"DAL456, turn right heading three six zero, reduce speed one niner zero, you are number two following Airbus on final."

Approach Clearance

Before clearing an aircraft for approach:

• It is established or being vectored to intercept.
• Altitude is appropriate.
• Speed is manageable.
• Separation from preceding traffic is safe.
• Tower can accept the arrival.

Example:

"DAL456, turn left heading two four zero, maintain three thousand until established, cleared ILS runway 25R approach."

Visual approach:

"DAL456, traffic twelve o'clock, five miles, Airbus on final. Report traffic in sight."

"DAL456, cleared visual approach runway 25R, follow the Airbus."

Departure Control

After Tower handoff, Departure should:

• Radar identify the aircraft.
• Confirm altitude and route.
• Climb aircraft according to SID or local procedure.
• Turn aircraft toward route when safe.
• Separate it from arrivals and other departures.

Examples:

"AAL123, radar contact, climb and maintain one three thousand."

"AAL123, turn right direct DAG, resume own navigation."

Conflict Detection

A conflict is easier to solve 5 minutes early than 30 seconds late.

Look for:

• Converging tracks at similar altitude.
• Fast aircraft behind slow aircraft.
• Departures climbing into arrivals.
• Opposite-direction traffic on same altitude.
• Aircraft turning toward the same fix.
• Missed approach path crossing departure path.

Tools:

• Heading change.
• Altitude change.
• Speed change.
• Vector extension.
• Hold.
• Coordination with another sector.

Do not rely on one instruction if the conflict is serious. Use vertical and lateral separation if needed.

Go-Around Resequencing

When Tower sends an arrival around:

1. Issue or confirm climb-out altitude.
2. Turn the aircraft away from final/departure conflicts if required.
3. Rebuild the sequence.
4. Coordinate with Tower.
5. Do not forget the original arrival stream.

Example:

"DAL456, fly runway heading, climb and maintain three thousand."

Then:

"DAL456, turn right heading zero seven zero, vectors for another approach."

Holding

Use holding when sequencing cannot be solved safely with vectors and speed.

A holding clearance should include:

• Fix.
• Direction from fix.
• Inbound course.
• Turn direction.
• Leg length or time.
• Altitude.
• Expect further clearance time if used.

Example:

"AAL123, hold east of DAG on the zero niner zero radial, left turns, one-minute legs, maintain one zero thousand."

S3 Emergencies

For emergencies, keep the plan simple:

1. Aviate: let the pilot fly.
2. Separate: protect the emergency aircraft from other traffic.
3. Navigate: offer headings, nearest suitable airport, and runway options.
4. Communicate: coordinate with Tower and adjacent controllers.
5. Prioritize: delay normal traffic if needed.

Example:

"AAL123, roger emergency. Turn left heading two four zero, descend and maintain five thousand. Airport is twelve o'clock, one five miles. Say souls on board and fuel remaining when able."

S3 Competency Targets

To be S3 competent, the trainee should:

• Cross aircraft at the final approach fix within trainer tolerances.
• Sequence at least 8 aircraft to one runway with low average delay.
• Vector efficiently without excessive extra track miles.
• Use 220/190/160 knot speed gates correctly.
• Answer point-outs and release requests within 30 seconds.
• Detect and resolve all conflicts at least 5 minutes before closest point of approach.
• Re-sequence go-around aircraft within 3 minutes.
• Handle emergencies without delaying essential instructions.

S3 Training Sessions

Suggested structure:

1. Navigation, RNAV transitions, and aircraft performance.
2. Radar identification, vectoring, and altitude control.
3. Descent planning and final approach fix management.
4. Speed control and arrival sequencing.
5. Departure control and mixed arrival/departure flows.
6. Holding, weather deviations, and abnormal operations.
7. Complex scenarios and emergency handling.
8. Live traffic consolidation and final preparation.

S3 Practical Exercises

S3 Final Test

Retest and currency:

• First fail: 30-day cooldown plus mandatory mentoring.
• Currency: 10 hours within the previous 60 days or checkride required.

Post-S3 Privileges

After S3 completion, the controller may:

• Operate assigned APP/DEP/CTR-style positions solo within ATCThing rules.
• Mentor up to S2.
• Recommend candidates for S1 and S2 tests.
• Apply for instructor ratings after additional experience.