Contents03 / 14
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."