How do GCI and CAP missions work in DCS World?

In DCS World, CAP aircraft patrol a defined area to detect and stop hostile aircraft, while GCI uses radar information to direct fighters towards an interception. A typical mission combines both: CAP holds at an assigned station, GCI builds the air picture, then supplies headings, altitude, range and target priorities.

GCI and CAP compared

CAP is an airborne defensive task; GCI is the control service that turns radar detections into useful intercept instructions.

A barrier CAP blocks an expected threat route, while target and high-value-asset patrols protect a strike area or aircraft such as an AWACS or tanker. GCI can control any of these, but it is not itself a patrol pattern or aircraft task.

How does a combined GCI and CAP mission unfold?

The mission normally progresses from check-in and patrol to detection, interception, engagement and reset.

1. Brief the patrol: establish the CAP station, altitude block, controller frequency, bullseye, rules of engagement, fuel limits and defended area. Pilots must know what authorises them to leave the station and fire.
2. Check in with GCI: report callsign, position, altitude, weapons and fuel state. Airfield ATC handles departure and recovery; it does not provide combat interception control.
3. Build the picture: the controller correlates radar tracks and reports relevant contacts. Pilots may request a picture or bogey dope from AI AWACS where the aircraft and mission support those radio options.
4. Commit the fighter: GCI assigns a target and gives a vector or contact position. The CAP leaves its station only when ordered or when the mission's rules permit an autonomous intercept.
5. Sort and identify: pilots separate multiple contacts, use radar and IFF, then request a declaration if supported. A bogey is unidentified; a bandit has been identified as hostile.
6. Engage or abort: the fighter attacks under the stated rules of engagement, or disengages if identification, fuel, weapons or geometry is unsuitable.
7. Reset the CAP: surviving fighters return to station, re-form, report their remaining weapons and fuel, or recover while another flight takes over.

A common mistake is treating every bearing as a steering command. A BRAA call gives the contact's bearing, range, altitude and aspect relative to the receiving aircraft. A controller may issue a different heading to create lead pursuit rather than sending the fighter directly at the target's present position.

Bullseye calls use a fixed reference point instead of the fighter's position, so every flight hears the same location. Pilots should confirm during the briefing whether calls are BRAA or bullseye and which distance and altitude units the mission uses.

Can you act as a human GCI controller in DCS World?

A player can provide GCI when the mission and server expose a suitable controller role and enough coalition track information.

This is commonly done through an authorised Tactical Commander, Game Master or observer-style slot, depending on mission permissions and installed DCS content. The controller uses the tactical map and voice communications to assign contacts, provide vectors, deconflict friendly flights and monitor the defended airspace. Our guide to using the F10 map for bearings, distances and unit information covers the core map tools.

The mission's F10 visibility setting matters. Fog-of-war or coalition-only views can limit the controller to detected tracks, while a less restrictive setting may reveal information no real radar network would possess. Units marked as hidden and server role permissions can also affect what appears.

Human voice calls direct human pilots. They do not automatically retask an AI CAP group; AI aircraft follow their Mission Editor tasks, trigger logic and internal detection system.

How do you set up AI GCI and CAP?

An AI-controlled scenario needs a sensor network, properly tasked fighters and clear engagement limits.

• Add surveillance: place an AWACS aircraft with the appropriate task and route, or suitable ground-based early-warning radar units. Keep terrain masking, radar coverage and survivability in mind.
• Configure communications: verify coalition, callsign, frequency and modulation. The player must tune the correct cockpit radio and transmit with the correct radio or push-to-talk binding.
• Define the patrol: give the CAP a sensible route, altitude and station. A broad CAP task may chase contacts far beyond the intended area, so a constrained search-and-engage zone is often the better choice.
• Set behaviour: check rules of engagement, reaction to threat, target categories and task priority. Conflicting orbit, attack and triggered tasks can leave a flight circling indefinitely or abandoning its station.
• Plan reinforcement: late activation and triggers can launch alert fighters when an intruder enters a detection or defence zone.

For the practical editor workflow, see our explanation of creating routes, zones, AI tasks and rules of engagement in the DCS Mission Editor.

Why are GCI calls or CAP intercepts not working?

Most failures come from radio configuration, restricted tactical information or AI tasking rather than the basic GCI concept.

• No AWACS menu or reply: check that the controller is alive, belongs to the correct coalition, has the correct task and is reachable on the selected radio frequency and modulation. Easy Communications can change how radio selection behaves.
• Human GCI sees no contacts: inspect the player's assigned role, F10 map restrictions, hidden-unit settings and whether friendly radar actually has line of sight to the target.
• AI CAP never engages: confirm that its task includes the target category, its rules permit engagement and no higher-priority orbit or triggered task is blocking the attack. Terrain masking may also prevent detection.
• AI CAP chases aircraft across the map: replace an unrestricted engagement task with a bounded search-and-engage zone, and add stop conditions or trigger logic that returns the group to patrol.
• Pilot reaches the intercept but cannot shoot: GCI only places the fighter near the contact. The pilot must still configure the radar, select the correct sensor mode, designate the track, identify it and satisfy weapon-launch conditions. Our DCS radar selection and target-lock workflow covers that next stage.
• Datalink and GCI disagree: tracks may be delayed, filtered or sourced from different sensors. Treat the controller's call as tactical guidance and confirm the contact with onboard sensors before firing.

AWACS is useful but not mandatory

CAP can operate without AWACS, but interception becomes less efficient and more dependent on fighter radar, visual detection and pre-briefed threat routes. Ground early-warning radar or a human controller can provide some of the same service if the mission exposes their detections correctly.

Without any controller or external sensor picture, the patrol is effectively autonomous. Pilots must sanitise their own sector, manage identification and decide when to leave station, which makes clear patrol boundaries and rules of engagement essential.