# ATCThing Controller Guide

VATSIM-style S1, S2, and S3 training for GeoFS controllers

Version: Draft for review  
Source material: ATCThing website syllabus files and public VATSIM rating descriptions  
Scope: GeoFS/ATCThing operations, not an official VATSIM training manual

## How to Use This Guide

This guide turns the ATCThing website course into a single training document. It is written for a new controller who wants to learn what to do on frequency, not just what the final test requires.

Read it in order:

1. Learn the shared controller habits first.
2. Complete S1 before attempting S2 responsibilities.
3. Complete S2 before attempting S3 responsibilities.
4. Use the checklists before live sessions.
5. Use the phraseology examples until you can speak naturally without losing structure.

The guide follows the ATCThing rating path:

| Rating | ATCThing Focus | Main Positions | Practical Meaning |
|---|---|---|---|
| S1 | Delivery and Ground | DEL, GND | Clearances, flight plans, taxi, runway crossing coordination |
| S2 | Tower and Departure | TWR, DEP | Runway control, takeoff/landing, circuits, initial departure flow |
| S3 | Approach and Control | APP, DEP, CTR-style control as assigned | Radar sequencing, vectoring, descents, conflict resolution |

VATSIM's public rating descriptions may differ by policy wording and local division rules. ATCThing uses a VATSIM-style progression adapted for GeoFS and its own training environment.

## Controller Mindset

ATC is not about talking fast. It is about keeping an accurate mental picture, making safe decisions early, and communicating those decisions clearly.

A good controller constantly answers four questions:

1. Where is every aircraft now?
2. Where is each aircraft going next?
3. Which aircraft can conflict if nothing changes?
4. What instruction solves the problem with the least confusion?

Every instruction should be:

- Safe: It preserves separation and runway protection.
- Clear: The pilot can understand it on the first read.
- Complete: It includes the required limit, route, altitude, heading, speed, or clearance.
- Timely: It is issued early enough that the pilot can comply.
- Coordinated: Other controllers know what you are sending them.

## Core Tools and Setup

Before controlling, prepare the workspace.

### Required Habits

- Know your airport layout before opening the position.
- Know the active runway, preferred taxi routes, local SIDs, STARs, fixes, and frequencies.
- Keep a strip or list for every aircraft.
- Mark aircraft status immediately after each instruction.
- Listen before transmitting.
- Correct readback errors immediately.
- Ask for help early if traffic exceeds your capacity.

### Basic Strip Data

Every controlled aircraft should have at least:

| Field | Example | Why It Matters |
|---|---|---|
| Callsign | AAL123 | Identifies who you are controlling |
| Aircraft type | A320 | Performance and wake category |
| Flight rules | IFR/VFR | Determines clearance type |
| Departure/arrival airport | KLAX/KSFO | Defines route logic |
| Route/SID/STAR | LOOP6 DAG | Keeps traffic predictable |
| Cleared altitude | 5000 ft | Prevents vertical conflicts |
| Squawk | 4321 | Radar identification |
| Current instruction | Taxi A hold short 25R | Prevents duplicate or conflicting instructions |
| Next controller | TWR/DEP/APP | Supports clean handoff |

### Readback Items You Must Hear

Always verify the pilot correctly reads back:

- Callsign
- Runway assignment
- Hold short instruction
- Takeoff or landing clearance
- Cleared altitude
- Heading
- Speed restriction
- Squawk code
- Route or SID
- Frequency change

If a readback is wrong, correct it immediately:

> "AAL123, negative. Cleared altitude is five thousand, read back five thousand."

## Radio Technique

### Standard Transmission Order

Use this basic order:

1. Callsign
2. Instruction
3. Restriction or condition
4. Frequency or handoff, if needed

Example:

> "AAL123, taxi to runway 25R via Alpha, Bravo, hold short runway 25R."

### Speak Clearly

- Use standard phraseology where possible.
- Avoid long explanations on frequency.
- Split complex instructions into smaller parts.
- Do not issue an instruction until you know what you want the aircraft to do.
- Never assume silence means compliance.

### Correction Format

When correcting yourself:

> "AAL123, correction, taxi to runway 25R via Alpha, Charlie, hold short runway 25R."

When correcting the pilot:

> "AAL123, readback correct except squawk. Squawk 4272."

### Frequency Discipline

Do not block the frequency with training commentary. If a pilot needs help, give the operational instruction first, then clarify only if necessary.

Good:

> "DAL456, hold position. Traffic crossing left to right."

Poor:

> "DAL456, wait a second because I have another aircraft and I am not sure if you can go yet."

## S1: Delivery and Ground

S1 is the foundation. You are responsible for getting aircraft from flight plan to runway without creating confusion or ground conflicts.

### S1 Objective

An S1 controller must safely and professionally:

- Issue IFR and VFR clearances.
- Assign logical routes, SIDs, squawks, and initial altitudes.
- Manage pushback, startup, taxi, and runway crossings.
- Coordinate departures with Tower.
- Detect and correct readback errors.
- Use RadarThing and VStrips at a competent level.

### S1 Prerequisites

- Signed up on ATCThing as S1.
- Knows the International Radiotelephony Spelling Alphabet.
- Knows how to use the ATCThing Discord server for communications.

### Delivery Control Workflow

Delivery turns a flight plan into a controlled clearance.

Before issuing clearance, check:

- Callsign matches the filed plan.
- Aircraft is at the correct departure airport.
- Flight rules are IFR or VFR.
- Destination is valid.
- Route is logical.
- SID matches the active runway and route direction.
- Initial altitude is appropriate for local procedures.
- Squawk is assigned and unique.
- Next frequency is correct.

### IFR Clearance Structure: CRAFT

Use CRAFT:

| Letter | Meaning | Example |
|---|---|---|
| C | Clearance limit | "Cleared to San Francisco" |
| R | Route | "LOOP6 departure, DAG transition, then as filed" |
| A | Altitude | "Climb and maintain 5000" |
| F | Frequency | "Departure frequency 124.50" |
| T | Transponder | "Squawk 4321" |

Example IFR clearance:

> "AAL123, cleared to San Francisco via the LOOP6 departure, DAG transition, then as filed. Climb and maintain five thousand. Departure frequency one two four point five zero. Squawk four three two one."

If the route is simple and already correct:

> "AAL123, cleared to San Francisco as filed. Climb and maintain five thousand. Departure frequency one two four point five zero. Squawk four three two one."

### VFR Clearance and Taxi

VFR aircraft usually need simpler handling, but they still need clear limits.

Example:

> "N172AB, VFR departure approved to the north. Maintain VFR at or below two thousand five hundred. Squawk 1200."

If the aircraft will enter controlled airspace or cross active runways, coordinate with Tower before moving them.

### Ground Control Workflow

Ground controls aircraft movement on taxiways and non-runway movement areas. The goal is to move aircraft efficiently while protecting runways and avoiding taxi conflicts.

Before taxiing an aircraft, know:

- Its current parking spot or ramp.
- Assigned runway.
- Taxi route.
- Any hotspots or closed taxiways.
- Other aircraft using the same route.
- Whether Tower must approve a runway crossing.

### Taxi Instructions

Standard format:

> "Callsign, taxi to [location/runway] via [route], [restriction]."

Examples:

> "DAL456, taxi to runway 25R via Alpha, Bravo, hold short runway 25R."

> "N172AB, taxi to the run-up area via Charlie, hold short runway 25L."

For progressive taxi:

> "N172AB, progressive taxi approved. Turn left next taxiway, then continue straight ahead."

### Hold Short Discipline

Hold short instructions protect runways. They must be read back.

Example:

> "UAL88, hold short runway 25R."

If the pilot misses it:

> "UAL88, hold short runway 25R. Read back hold short."

Never let an aircraft cross or enter a runway unless Tower has approved it or you own that runway under local procedure.

### Pushback and Startup

When pushback matters for traffic flow:

> "AAL123, pushback approved, expect runway 25R."

If pushback would block another aircraft:

> "AAL123, hold position, traffic behind you."

### Ground Conflict Prevention

Use the "next three" scan:

1. The aircraft moving now.
2. The aircraft it could meet next.
3. The aircraft you will move after that.

Common ground risks:

- Opposite-direction taxi on a narrow taxiway.
- Aircraft crossing behind pushback traffic.
- Aircraft taxiing to the wrong runway.
- Multiple aircraft approaching the same hold short line.
- Pilot continuing after a missed hold short readback.

### S1 Coordination

Coordinate with Tower for:

- Runway crossings.
- Departure releases if required.
- Runway changes.
- Intersection departures.
- Aircraft ready at the hold short line.

Example coordination:

> "Tower, Ground, AAL123 ready runway 25R, IFR departure DAG transition."

### S1 Competency Targets

To be S1 competent, the trainee should:

- Build logical routes and assign expected SIDs about 90 percent of the time.
- Catch all clearance readback errors involving route, squawk, and altitude.
- Create zero runway incursions under normal traffic.
- Keep phraseology errors minor and infrequent.
- Prioritize departures in an order that does not overload Tower or Departure.
- Transfer aircraft to Tower with complete strips.
- Use RadarThing and VStrips confidently.

### S1 Training Sessions

Suggested structure:

1. Aircraft performance, basic routing, and GeoFS airport layouts.
2. IFR/VFR clearance building and CRAFT practice.
3. Taxiway geometry, hold short discipline, and ground conflicts.
4. Mixed traffic practice, readback errors, and final test preparation.

### S1 Practical Exercises

| Scenario | Focus | Minimum Traffic |
|---|---|---|
| Rush-hour IFR departures | Route and SID selection | 8 aircraft |
| Mixed VFR helicopter and IFR traffic | Prioritization | 5 aircraft |
| Runway change with active circuit | Dynamic re-routing | 6 aircraft |
| Readback error drill | Catching incorrect readbacks | 4 aircraft |

### S1 Final Test

| Segment | Format | Pass Standard |
|---|---|---|
| Oral clearance exam | 10 random routes | 9 correct clearances |
| Live ground session | 45 minutes, at least 10 movements | Zero major deviations |
| Debrief | Verbal self-critique | Explains errors and improvements |

Any runway incursion requires a retest.

### Post-S1 Privileges

After S1 completion, the controller may:

- Begin S2 training.
- Operate Delivery and Ground during events.

## 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

| Scenario | Focus | Minimum Traffic |
|---|---|---|
| Parallel runway operations | Wake separation and scanning | 10 aircraft |
| Heavy jet plus light GA circuit | Circuit integration | 8 aircraft |
| Thunderstorm with tailwind | Weather decisions | 6 aircraft |
| Runway incursion drill | Contingency control | 5 aircraft |
| Night or reduced lighting | Visual judgment | 6 aircraft |

### S2 Final Test

| Segment | Format | Pass Standard |
|---|---|---|
| Oral theory | 40 questions in 45 minutes | 80 percent |
| Practical live | 60 minutes, at least 14 movements | Zero runway separation loss |
| Debrief | 10-minute reflection | Explains decisions and errors |

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.

## 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

| Scenario | Focus | Minimum Traffic |
|---|---|---|
| Parallel approaches | No-transgression and breakout thinking | 10 aircraft |
| Thunderstorm deviations | Weather vectoring | 12 aircraft |
| Heavy aircraft plus medical emergency | Priority handling | 8 aircraft |
| Partial radar failure | Procedural separation | 6 aircraft |
| Miles-in-trail metering | Speed and delay control | 14 aircraft |

### S3 Final Test

| Segment | Format | Pass Standard |
|---|---|---|
| Written theory | 60 questions in 75 minutes | 85 percent |
| Practical live | 90 minutes, at least 16 movements | Zero separation loss |
| OJTI demo | 30-minute mentoring role-play | Gives useful teaching and feedback |

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.

## Shared Phraseology Reference

### Initial Contact

> "AAL123, Los Angeles Ground, good evening."

> "DAL456, Los Angeles Tower, runway 25R, continue."

> "UAL88, SoCal Approach, radar contact."

### Clearance

> "Cleared to [destination] via [SID/route]. Climb and maintain [altitude]. Departure frequency [frequency]. Squawk [code]."

### Taxi

> "Taxi to runway [runway] via [taxiways], hold short runway [runway]."

### Runway

> "Runway [runway], cleared for takeoff."

> "Runway [runway], cleared to land."

> "Line up and wait runway [runway]."

> "Go around, fly runway heading, climb and maintain [altitude]."

### Radar

> "Radar contact."

> "Fly heading [heading]."

> "Turn left/right heading [heading]."

> "Climb and maintain [altitude]."

> "Descend and maintain [altitude]."

> "Reduce speed [speed] knots."

> "Cleared [approach] runway [runway] approach."

### Handoff

> "Contact [position] on [frequency]."

> "Monitor Tower on [frequency]."

## Common Mistakes and Fixes

| Mistake | Why It Matters | Fix |
|---|---|---|
| Not correcting readback errors | The aircraft may do the wrong thing | Correct immediately and require a correct readback |
| Taxiing aircraft without a route | Creates ground conflicts | Plan the route before transmitting |
| Forgetting hold short | Causes runway incursions | Always include and verify hold short near runways |
| Clearing takeoff with final too close | Creates runway separation loss | Scan final before every takeoff clearance |
| Using speed too late | Aircraft cannot slow enough | Assign speed reductions earlier |
| Descending arrivals too late | Unstable approaches | Plan descent distance before the aircraft reaches the TMA |
| Over-talking | Blocks pilot readbacks and coordination | Use shorter instructions |
| Ignoring coordination | Surprises the next controller | Coordinate releases, crossings, and unusual plans |

## Session Preparation Checklist

Before opening a position:

- Confirm your rating and position authorization.
- Review local SOPs and airport diagrams.
- Choose active runway based on wind and traffic.
- Prepare SID/STAR/runway notes.
- Check frequencies.
- Open RadarThing and VStrips.
- Prepare a scratchpad or strip bay.
- Know who owns adjacent positions.
- Set personal limits and ask for a mentor if needed.

## Live Controlling Checklist

During the session:

- Keep strips current.
- Scan before transmitting.
- Use callsigns every time.
- Correct readbacks immediately.
- Protect runways.
- Coordinate before handoff if anything is unusual.
- Keep instructions short under pressure.
- Slow the operation before it becomes unsafe.

## Debrief Checklist

After the session, answer:

1. What went well?
2. What caused the most workload?
3. Did I miss any readback errors?
4. Did I issue any unclear instructions?
5. Did I coordinate early enough?
6. Did any aircraft get delayed unnecessarily?
7. What is one thing I will improve next session?

## Rating Progression Summary

| Rating | Training Time | Key Test Standard | Unlocks |
|---|---|---|---|
| S1 | Suggested 4 sessions | Clearances, ground control, zero incursions | Delivery/Ground, S2 training |
| S2 | Suggested 6 sessions | Runway control, wake separation, emergency response | Tower/Departure, S3 training |
| S3 | Suggested 8 sessions | Radar sequencing, vectoring, conflict resolution | Approach/Control, mentoring path |

## Final Notes

ATC skill comes from repetition. The goal is not to memorize every phrase; the goal is to understand the operation well enough that your instructions are safe, predictable, and easy for pilots to follow.

When unsure:

- Slow traffic down.
- Stop aircraft before they enter a risk area.
- Use altitude to create safety.
- Coordinate with the next controller.
- Ask a trainer before the situation becomes overloaded.