How do I use JTAC in DCS World?

To use JTAC in DCS World, find its callsign and frequency in the mission briefing, tune the correct radio, select the JTAC through that radio’s communications menu, and check in. Copy the nine-line, locate the assigned target, report “in”, wait for “cleared hot”, attack, then report the result.

What must be set up before contacting JTAC?

An AI JTAC can only respond if the mission contains a live friendly controller with a FAC or JTAC task, an assigned frequency and eligible targets. JTAC means Joint Terminal Attack Controller; DCS may also use an airborne FAC, usually written as FAC(A), for the same broad job.

• Read the mission briefing: note the controller’s callsign, frequency, radio modulation, target area and any attack restrictions.
• Prepare the correct radio: AM and FM are not interchangeable. With Easy Communications enabled, DCS may select and tune the appropriate radio; with it disabled, tune it manually and use that radio’s PTT or microphone-switch binding.
• Bind the essential controls: radio PTT, sensor slew, target designate, undesignate and weapon release should be accessible without searching the keyboard. Our guide to configuring radio and sensor controls on a HOTAS covers that preparation.
• Have somewhere to record the attack: line 6 coordinates, elevation, friendlies, mark type, laser code and egress instructions are the details most often forgotten. You can also set up the DCS kneeboard for mission notes and reference pages.

How do you complete a DCS JTAC attack?

A DCS AI JTAC attack is completed by following the radio-menu prompts in order rather than transmitting free-form voice calls.

1. Tune and call the JTAC. Open the communications menu through the appropriate radio, choose the JTAC entry and select the callsign listed in the briefing. Use the available check-in command when ready to accept tasking.
2. Copy the nine-line. The controller will identify the target, coordinates, mark, nearby friendlies and egress direction. Remarks may add threats, a laser code, requested weapon or final attack heading.
3. Read back the requested details. Select the contextual radio-menu response shown by DCS. The exact menu wording can vary with the stage of the attack and the mission’s control type.
4. Proceed from the IP or holding area. Make the “IP inbound” call when offered. Do not treat this as permission to release a weapon.
5. Acquire and verify the target. Use the coordinates, description and mark together. Check that the target’s position agrees with line 8 friendlies before designating it.
6. Report the attack run. Select “In” or the equivalent menu option once established on the instructed heading. Request “Laser on” or another mark only when the relevant option appears.
7. Wait for clearance. Release only after “Cleared hot”, “Cleared to engage” or the explicit clearance used by that mission. Break off immediately if the controller transmits “Abort”.
8. Report the result. After impact, use “Attack complete” or the next available response. JTAC may order a reattack, assign another target or report that no further tasking is available.

What does the JTAC nine-line mean?

The nine-line gives the information needed to find the target, avoid friendlies and fly the authorised attack direction.

Remarks and restrictions matter just as much as the numbered lines. This is where DCS JTAC commonly states the requested weapon, laser code, threats and attack-axis restrictions.

How do you find the JTAC target?

The safest way to find a JTAC target is to combine its coordinates, description and mark rather than relying on smoke or a laser alone.

• Coordinates: create a waypoint or sensor point using line 6 and the supplied elevation. DCS aircraft accept different coordinate formats, so do not enter an MGRS grid into a latitude-and-longitude field or omit required leading digits.
• Laser: enter the stated code into the appropriate sensor or weapon system, point the sensor near the target area, request “Laser on”, then use laser search if the aircraft supports it. Terrain, buildings, pod masking and a narrow search field can all prevent detection.
• Smoke: treat smoke as an area marker, not a precision aimpoint. It can obscure vehicles, and the assigned target may be offset from the centre of the plume.
• IR pointer: use compatible night-vision equipment or sensors. A normal daylight display will not necessarily show the pointer.
• No mark: use the coordinates, target description and talk-on. Confirm the target against the stated friendly position before attacking.

The A-10C is particularly well suited to this workflow because it can turn a JTAC grid into a sensor point and share that designation between its systems. Our A-10C sensor and weapon walkthrough explains the aircraft-specific side without repeating the radio procedure here.

Which JTAC laser code should you use?

Use the laser code given in the JTAC remarks or mission briefing, not a code assumed from another mission.

Code 1688 is common in DCS missions, but it is not universal. The sensor’s laser-search code and the weapon’s code must match the designator where applicable, and some modules require those values to be set at a different stage of weapon preparation.

Why is JTAC missing or not responding?

A missing or silent JTAC usually means the mission task, radio configuration or line of sight is wrong.

• No JTAC entry appears: the mission may not contain a friendly FAC/JTAC task, or the controller may have been destroyed or deactivated. In a self-made mission, simply placing a vehicle is not enough; it must receive the appropriate FAC task, frequency, callsign and target assignment.
• The callsign appears but nobody answers: check the selected radio, frequency, AM/FM mode and PTT binding. Terrain and distance can block a ground controller’s transmission.
• JTAC says “No tasking available”: its assigned targets may already be destroyed, inactive or outside the conditions set by the mission designer. Calling repeatedly will not create a new target.
• No laser spot appears: confirm the code, wait until JTAC acknowledges the laser request, point the sensor close enough to search and avoid masking it with the aircraft. The controller also needs an unobstructed view of the target.
• You never receive clearance: a required readback, “IP inbound” call or “In” call may still be pending. Reopen the radio menu and select the next contextual option rather than skipping ahead.
• The attack does not advance after impact: report “Attack complete”. A damaged vehicle may still count as alive, while a genuinely stuck sequence can indicate faulty mission scripting.

Do you have to use the weapon requested by JTAC?

Yes, follow the requested weapon and attack restrictions unless the mission explicitly permits another method.

DCS AI logic does not reproduce every detail of real close-air-support communication, and some missions may technically allow a different weapon. That does not make an uncleared release correct: the requested ordnance may reflect friendly proximity, target type, mission triggers or collateral-damage limits. If you cannot comply, abort the pass rather than improvising over friendlies.

Does a human JTAC work the same way?

No, a human JTAC normally communicates through the multiplayer server’s chosen voice system rather than the AI communications-menu sequence.

The nine-line, readback, attack restrictions and clearance still apply, but calls and terminology depend on that server’s procedures. Easy Communications, map labels and external views may also be disabled, so use the briefing and establish the required voice channel before entering the target area.