Choose your server and coalition. Read the briefing, connect your radio, and work the traffic.
Connecting to the controller service…
01 / SIGN IN
Your controller desk
Use the controller website password issued for this server and side. Ask North Pole Flights staff for access.
Each login opens one coalition on one server.
02 / BEFORE YOU TRANSMIT
Controller briefing
Coordinate the handover
Agree your airfield, runway and frequency with the current human or AI controller before transmitting. Listen first. A website login does not mute AI ATC, reserve an airfield, or give you a clearance to take over.
Use the active mission’s published radio plan. Confirm aircraft can tune the frequency, especially WWII and early Cold War aircraft.
Work the pilot’s request
Use callsigns. Confirm aircraft location and intentions, then give one clear instruction at a time. Include the runway, route or holding point when relevant.
Read runway digits separately: “runway two five.” Ask pilots to read back runway, hold-short, crossing and takeoff instructions; correct a wrong readback before proceeding.
Keep the runway protected
Check runway occupancy and approaching traffic before issuing crossing, takeoff or landing instructions. Give traffic information early. If unsure, ask the pilot to hold or go around while you resolve the conflict.
The map reports observations. Speed is ground speed; magnetic heading is shown only when available. A frozen or stale track is not current traffic information.
Connect and hand back
Open SRS, use the server address below, and choose External AWACS Mode (EAM) with your coalition’s password. Set your controller name, tune the agreed frequency and check your microphone/PTT.
Tell pilots when you close the service, hand back to the agreed controller, then sign out. Keep access passwords private.