DCS World Wiki - Hoggitworld.com - User contributions [en]

JTAC

2023-08-18T17:38:47Z

Krad 1337:

== Joint Terminal Attack Controllers ==

[[File:jtac_working_small.jpg|right|300px]] ''Joint Terminal Attack Controllers'' (JTAC's) are the people who coordinate the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold. First they coordinate and deconflict the attacking aircraft to prevent friendly casualties on the ground or in the air. Secondly they guide the attacking aircraft to their targets ensuring effective application of force to quickly eliminate the enemy positions.

A variation on this is ''Forward Air Controller, Airborne'' abbreviated FAC(A). These units perform the same tasks as JTAC's, but from an airborne platform.

=== How CAS flights work with JTAC's ===

When approaching the CAS Aircraft will check in with the JTAC. The JTAC will give the aircraft a holding position and will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point. The JTAC will then either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

The first is ''Keyhole CAS'' - a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

Secondly there are ''control types''. There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

''Type I'': JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

''Type II'': The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

''Type III'': The JTAC can clear multiple attacks within a single engagement

And, finally '''Bombs on X'':

''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target

''Bombs on Coordinates (BoC)'': The JTAC provides high-precision lat/long of the target

The ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTION,
final attack heading XXX through YYY
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime
</pre>

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For a flight its common to give the flight an altitude block of 1000ft for each aircraft.

For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

<pre style="background-color: #ccc;font-family: 'Lucida Console'">
stryker 1-1 at Alpha 10 angels 12 block 13
lightning 1-1 at Alpha 10 angels 15 block 17
</pre>
Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield
F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

Consider stating in your 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

Hoggit DCS World Wiki

2022-06-30T21:35:05Z

Krad 1337: /* Technique Guides & Resources */

<div class="row">
<div class="col-sm-12 hidden-xs">
[[File:Toc.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:Toc_small.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-xs">
[[File:GAWupdate.png|class=img-responsive center-block|link=Georgia At War]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:GAWupdate_small.png|class=img-responsive center-block|link=Georgia At War]]
</div>
</div>

===Learn to Fly===
Welcome to Hoggit's DCS: World Wiki! We're a noob-friendly SeriousFaceTM multiplayer and singleplayer flight simulation community based on Reddit. This Wiki is meant to be a resource for anyone looking for information on the simulations we primarily play, DCS: World and Falcon BMS. We're gathering and organizing all the information related to the games, their peripherals, their quirks, and their tweaks/mods into this central repository in hopes that the World community will find it a valuable "one-stop shop" resource for everything you'd want to know.

[[Frequently Asked Questions]]

[https://www.youtube.com/watch?v=apvriPLtiZA&list=UUHa9LMylydkT0T3qSzAVrlw&feature=c4-overview What is DCS World?]

[[Simulator Scripting Engine Documentation|Looking for MIST/Scripting Documentation?]]

<div class="row">
<div class="col-sm-12">
[https://discord.gg/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" /> Join the Discord!</span>]
</div>

<div class="col-sm-12">
[[Tuesday Night Noob|<span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" />Looking to ease your way into multiplayer? Join Tuesday Night Noob!</span>]]
</div>

<div class="col-sm-12">
Hoggit was created as a laid back place for flight simmers of all skill levels to get together and fly online all while learning the modules of DCS World. Multiplayer DCS World groups tend to be very strict and regimented so we wanted to create a niche where people could casually come together and focus on having a good time. A great place to start is our Discord, where you'll find a community of sim pilots who are always willing to lend a hand to a new player, or just talk about sims in general.
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

== DCS World Modules ==

<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Fighter/Multirole====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F-A-18C-icon.png|link=F/A-18C]]</p>
[[F/A-18C]]
</div>

<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F14 Icon TEMP.png|75px|link=F-14A/B]]</p>

[[F-14A/B]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:M2000-icon.png|link=Mirage 2000C]]</p>

[[Mirage 2000C|M-2000C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F5.png|link=F-5E Tiger II]]</p>

[[F-5E Tiger II]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig21.png|link=Mig-21bis]]</p>

[[Mig-21bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F86f.png|link=F-86F Sabre]]</p>

[[F-86F Sabre]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig15.png|link=Mig-15bis]]</p>

[[Mig-15bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Fc3.png|link=Flaming Cliffs]]</p>

[[Flaming Cliffs]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F16CM icon.png|link=F-16C]]</p>
[[F-16C|F-16CM]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:RWR-Track.png|80px|link=JF-17]]</p>
[[JF-17]]
</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">

====Attack====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:A10C-icon.png|link=A-10C]]</p>

[[A-10C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:av8b.png|link=AV-8B(NA)]]</p>

[[AV-8B(NA)]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ajs37.png|link=AJS-37]]</p>

[[AJS-37]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Su25t.png|link=Su-25T]]</p>

[[Su-25T]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem;">
====Rotorcraft====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ka52.png|link=Ka-50]]</p>

[[Ka-50]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:uh1h.png|link=UH-1H]]</p>

[[UH-1H]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:mi8.png|link=Mi-8]]</p>

[[Mi-8]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:sa342.png|link=SA342]]</p>

[[SA342]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
</div>
<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">

====World War 2====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:p51.png|link=P-51D]]</p>

[[P-51D]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:bf109.png|link=Bf 109 K-4]]</p>

[[Bf 109 K-4]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:spitfire.png|link=Spitfire Mk. IX]]</p>

[[Spitfire Mk. IX]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:fw190.png|link=Fw 190 D-9]]</p>

[[Fw 190 D-9]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Trainers====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:l39.png|link=L-39]]</p>

[[L-39]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:c101.png|link=C-101_Aviojet]]</p>

[[C-101]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:hawk.png|link=Hawk T.1A]]</p>

[[Hawk T.1A]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>

<div class="col-md-4" style="margin-bottom: 3rem;">

====Tools & Utilities====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Srs.png|link=Simple Radio Standalone]]</p>

[[Simple Radio Standalone]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:LotATC.png|link=LotATC]]</p>

[[LotATC]]
</div>
<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Tacview.png|link=Tacview]]</p>

[[Tacview]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Combatflite_logo_abbreviated.png|100px|link=CombatFlite]]</p>

[[CombatFlite]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Voice_attack.png|80px|link=Voice Attack]]</p>

[[Voice Attack]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:OVGME_Logo.PNG|170px|link=OVGME]]</p>

[[OVGME]]
</div>

</div>
</div>

==Non-DCS World Sims==
<div class="row">
<div class="col-sm-4">
<p style="margin-bottom: 0;">[[File:Bms.png|86px|link=Falcon BMS]]</p>
[[Falcon BMS]]
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|client=ca-pub-6997190595986605
|slot=7221930773
|width = 728px
|height = 90px
}}</center>

== Technique Guides & Resources ==
<div class="row">
<div class="col-md-6">
[[Basic Airmanship|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Basic Airmanship</span>]]
</div>
<div class="col-md-6">
[[Air-to-Air_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Air Combat</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Threat Database|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Threat Database</span>]]
</div>
<div class="col-md-6">
[[Air-to-Ground_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Ground Combat</span>]]
</div>
<div class="col-md-6">
[[Charts and Checklists|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Brevity (Jargon), Charts and Checklists</span>]]
</div>
<div class="col-md-6">
[[Carrier Air Operations|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Carrier Air Operations</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Getting started with GCI/AWACS|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting started with GCI/AWACS</span>]]
</div>
<div class="col-md-6">
[[Helicopter Operations (Logistics)|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Helicopter Operations (Logistics)</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[ATC and Airfield Communications|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">ATC and Airfield Communications</span>]]
</div>
<div class="col-md-6">
[[Attack Helicopter Operations|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Attack Helicopter Operations</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[JTAC|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">A/G Communication with JTAC's</span>]]
</div>
<div class="col-md-6">
</div>
</div>



== Multiplayer Guides ==
<div class="row">
<div class="col-md-6">
[[Getting Started With Multiplayer|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started With Multiplayer</span>]]
</div>
<div class="col-md-6">
[[Simple Radio Standalone|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Multiplayer Comms</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Running a Server|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Running a Server</span>]]
</div>
</div>

== Setup Guides ==
<div class="row">
<div class="col-md-6">
[[Peripherals Guide|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Peripherals Guide</span>]]
</div>
<div class="col-md-6">
[[Joystick Profiles|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Joystick Profiles</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Headtracking Guides|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Headtracking Guides</span>]]
</div>
<div class="col-md-6">
[[Cockpit Views|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Cockpit Views</span>]]
</div>
<div class="col-md-6">
[[Exporting MFCD Displays|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Exporting MFCD Displays</span>]]
</div>
<div class="col-md-6">
[[DCS Bios / Cockpit Building|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">DCS Bios / Cockpit Building</span>]]
</div>
</div>

== Mission Making ==
<div class="row">
<div class="col-md-6">
[[Simulator_Scripting_Engine_Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Simulator Scripting Engine Documentation</span>]]
</div>
<div class="col-md-6">
[[Mission Scripting Tools Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Scripting Tools Documentation</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_mission_editor|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Editor Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_mission_editor_tools_mods|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Editor Tools and Mods</span>]]
</div>
<div class="col-md-6">
[[Mission Design Resources|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Design Resources</span>]]
</div>
</div>

== Modding ==
<div class="row">
<div class="col-md-6">
[[Modding_Basics|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started</span>]]
</div>

<div class="col-md-6">
[[DCS_export|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Export</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_server_gameGUI|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">DCS Server Control Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_liveries|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Liveries</span>]]
</div>
</div>

== Other Links ==
<div class="row">
<div class="col-md-6">
[https://www.reddit.com/r/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Hoggit on Reddit</span>]
</div>
<div class="col-md-6">
[https://forums.eagle.ru <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Eagle Dynamics Forums</span>]
</div>
</div>

== Current Prices on Recommended Gear==
<div class="row">

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B004I5XB4K&asins=B004I5XB4K&linkId=839983d8016d022c4e361d068dcedd5e&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LY285ZH&asins=B01LY285ZH&linkId=0f1fe6cb2b72e84f9187d474626d1d93&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0029M6VKA&asins=B0029M6VKA&linkId=0f3882a4ce7cc8e7c03973917133f9d2&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=as_ss_li_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LX398IE&asins=B01LX398IE&linkId=60ad1f8062e080986ecea05098ed8a21&show_border=true&link_opens_in_new_window=true|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B005CMOV06&asins=B005CMOV06&linkId=3696e75c77379f2aab8dc914c2de19a6&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0000512IE&asins=B0000512IE&linkId=c0fc561a2ac5effe5ca2540e14a2f9af&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>
</div>
<div class="row">If nothing appears here, Amazon links are removed by AdBlock. Consider whitelisting our wiki in your ad blocker! We use the money for things like giveaways, contests, and funding our dedicated server.

Check out the [[Peripherals Guide]] for more information.</div>

JTAC

2022-06-30T16:08:34Z

Krad 1337: /* Joint Terminal Attack Controllers */

== Joint Terminal Attack Controllers ==

[[File:jtac_working_small.jpg|right|300px]] ''Joint Terminal Attack Controllers'' (JTAC's) are the people who coordinate the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold. First they coordinate and deconflict the attacking aircraft to prevent friendly casualties on the ground or in the air. Secondly they guide the attacking aircraft to their targets ensuring effective application of force to quickly eliminate the enemy positions.

A variation on this is ''Forward Air Controller, Airborne'' abbreviated FAC(A). These units perform the same tasks as JTAC's, but from an airborne platform.

=== How CAS flights work with JTAC's ===

When approaching the CAS Aircraft will check in with the JTAC. The JTAC will give the aircraft a holding position and will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point. The JTAC will then either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

The first is ''Keyhole CAS'' - a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

Secondly there are ''control types''. There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

''Type I'': JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

''Type II'': The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

''Type III'': The JTAC can clear multiple attacks within a single engagement

And, finally '''Bombs on X'':

''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target

''Bombs on Coordinates (BoC)'': The JTAC provides high-precision lat/long of the target

The ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime
</pre>

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

<pre style="background-color: #ccc;font-family: 'Lucida Console'">
stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14
</pre>
Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield
F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

Consider stating in your 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-30T01:50:32Z

Krad 1337:

== Joint Terminal Attack Controllers ==

[[File:jtac_working_small.jpg|right|300px]] Joint Terminal Attack Controllers (JTAC's) are the people who coordinate the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold. First they coordinate and deconflict the attacking aircraft to prevent friendly casualties on the ground or in the air. Secondly they guide the attacking aircraft to their targets ensuring effective application of force to quickly eliminate the enemy positions.

=== How CAS flights work with JTAC's ===

When approaching the CAS Aircraft will check in with the JTAC. The JTAC will give the aircraft a holding position and will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point. The JTAC will then either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

The first is ''Keyhole CAS'' - a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

Secondly there are ''control types''. There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

''Type I'': JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

''Type II'': The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

''Type III'': The JTAC can clear multiple attacks within a single engagement

And, finally '''Bombs on X'':
''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target
''Bombs on Coordinates (BoC)'': The JTAC provides high-precision lat/long of the target

The ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime
</pre>

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

<pre style="background-color: #ccc;font-family: 'Lucida Console'">
stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14
</pre>
Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield
F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

Consider stating in your 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-30T01:48:50Z

Krad 1337:

== Joint Terminal Attack Controllers ==

[[File:jtac_working_small.jpg|left|180px]] Joint Terminal Attack Controllers (JTAC's) are the people who coordinate the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold. First they coordinate and deconflict the attacking aircraft to prevent friendly casualties on the ground or in the air. Secondly they guide the attacking aircraft to their targets ensuring effective application of force to quickly eliminate the enemy positions.

=== How CAS flights work with JTAC's ===

When approaching the CAS Aircraft will check in with the JTAC. The JTAC will give the aircraft a holding position and will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point. The JTAC will then either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

The first is ''Keyhole CAS'' - a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

Secondly there are ''control types''. There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

''Type I'': JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

''Type II'': The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

''Type III'': The JTAC can clear multiple attacks within a single engagement

And, finally '''Bombs on X'':
''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target
''Bombs on Coordinates (BoC)'': The JTAC provides high-precision lat/long of the target

The ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime
</pre>

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

<pre style="background-color: #ccc;font-family: 'Lucida Console'">
stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14
</pre>
Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield
F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

Consider stating in your 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

File:Jtac working small.jpg

2022-06-30T01:38:33Z

Krad 1337:

JTAC

2022-06-30T01:36:34Z

Krad 1337:

== Joint Terminal Attack Controllers ==

A Joint Terminal Attack Controllers (JTAC), formerly called a Forward Air Controller (FAC) people who coordinate the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold. First they coordinate and deconflict the attacking aircraft to prevent friendly casualties on the ground or in the air. ANd secondly they guide the attacking aircraft to their targets ensuring effective application of force to quickly eliminate the enemy positions.

[[File:jtac_working.jpg]]

=== How CAS flights work with JTAC's ===

When approaching the CAS Aircraft will check in with the JTAC. The JTAC will give the aircraft a holding position and will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point. The JTAC will then either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

The first is ''Keyhole CAS'' - a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

Secondly there are ''control types''. There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

''Type I'': JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

''Type II'': The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

''Type III'': The JTAC can clear multiple attacks within a single engagement

And, finally '''Bombs on X'':
''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target
''Bombs on Coordinates (BoC)'': The JTAC provides high-precision lat/long of the target

The ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime
</pre>

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

<pre style="background-color: #ccc;font-family: 'Lucida Console'">
stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14
</pre>
Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield
F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

Consider stating in your 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

File:Jtac working.jpg

2022-06-30T01:24:47Z

Krad 1337:

JTAC

2022-06-29T23:54:51Z

Krad 1337: /* What is JTAC */

== What is a JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-29T23:54:36Z

Krad 1337: /* What is JTAC */

== What is JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights in a specific target area. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-29T23:53:54Z

Krad 1337: /* What is JTAC */

== What is JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-29T23:41:12Z

Krad 1337: /* Putting it all together */

== What is JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
</pre>

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

JTAC

2022-06-29T23:39:53Z

Krad 1337:

== What is JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:Keyhole_example.png]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.png]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:

ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

File:Nine line.png

2022-06-29T23:39:15Z

Krad 1337: The 9-line form used for CAS an JTAC operations

The 9-line form used for CAS an JTAC operations

File:Keyhole example.png

2022-06-29T23:38:04Z

Krad 1337: Keyhole CAS JTAC diagram

Keyhole CAS JTAC diagram

JTAC

2022-06-29T23:36:50Z

Krad 1337: Created page with "== What is JTAC == A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (C..."

== What is JTAC ==

A Joint Terminal Attack Controller (JTAC), formerly called a Forward Air Controller (FAC) is the person who coordinates the attacks of Close Air Support (CAS) flights. Their purpose is two-fold:

* To direct the attacking aircraft to prevent friendly casualties
* And to direct the attacking aircraft on to their targets

=== Overview of the process ===

Aircraft will check in. The JTAC will give the aircraft a holding position. JTAC will then provide the SITREP and GAMEPLAN - the situation on the ground and an overview of what the pilot will be doing.

The JTAC will then give the pilot the '9-line' - specific details what to attack and how to attack it. Once the pilot does a read-back, the JTAC will do a 'talk on' describing and confirming the pilot has tally on the correct target. The pilot will start their run and if everything looks good the JTAC will clear the pilot for weapons release. The pilot will then egress the target area, return to a holding point, and the JTAC will either assign another target via a new 9-line or release the pilot.

=== Keyhole, control types, and BoT/BoC ===

There are a few concepts to touch on before going deeper into the details of JTAC operations.

''Keyhole CAS'' is a simplified way to manage the navigation and orientation in a target area. A waypoint is designated a the center of the target area, this is the 'ECHO point'. Aircraft are oriented from this point, and keyholes are assigned in the four cardinal directions from ECHO, north is Alpha, east is Bravo, south is Charlie, west is Delta.

Aircraft are also provided distances, and altitudes oriented to these points. So if the JTAC wanted an aircraft to go to a initial point 10 miles north of the target at 12000 ft, you would direct them to 'Alpha 10, angels 12'.

One nuance, fixed wing distances are in NM, rotary are KN, so an Apache assigned D5 will be closer than an F18 at D5.

[[File:keyhole_cas.jpg]]

There are three control types, from most strict to most lax.. If there were noncombatants or friendlies nearby you'd opt for a stricter control type - although in DCS most times type 2 or type 3 are appropriate:

Type I: JTAC acquires both aircraft and target, JTAC can visually confirm the aircraft's orientation towards the target before giving final clearance for the attack.

Type II: The JTAC can only see either the target, or the aircraft. The JTAC will clear the aircraft in to only attack a single target.

Type III: jtac can clear multiple attacks within a single engagement

Bombs on XX:
Bombs on Target (BoT): JTAC will do a 'talk on' to the target
Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target

The ordinance your pilot checks in with can inform whether the JTAC directs them for BoT or BoC. Human JTAC's could state in their 'sunrise' 'check in with ordinance guidance type, laser/gps/unguided' - and use that check-in to vary BoT/BoC.

=== The 9-line ===

A standard briefing is done by the JTAC to the pilot before the pilot makes their attack.. it is known as a '9-line' and contains specific details needed for the pilot to know the parimeters and constraints for their attack on the assigned target.

[[File:nine_line.jpg]]

=== The talk-on ===

For BoC - the ordinance can be guided to a specific Lat/Long and that is sufficient, but for BoT, the JTAC must communicate the target to the pilot verbally, and must have confidence the pilot is looking at the right target before providing clearance. This process is called the 'talk on'.

If the JTAC has Smoke and a Laser the talk on can be very easy:

JTAC: do you see the tracked vehicle at the red smoke?
Pilot: Yes
JTAC: thats your target

If the JTAC does not have these tools available, the the talk on will be more complex. Quoting USN 'ADVANCED NFO CAS PROCEDURES T–45C'
<pre style="background-color: #ccc;font-family: 'Lucida Console'">
Generally, talk-ons should be conducted big-to-small. A technique for doing this is to give directions in the
following format, known by the mnemonic, “FIDO:”
a. From a point (easily recognizable start point)
b. In a direction (cardinal/sub-cardinal direction)
c. Distance to travel (established unit of measure or meters)
d. Object seen (target or object the JTAC/FAC(A) wants the aircrew to see)

Halo-11 - “Hammer-11, call contact the Shelby airfield”
Hammer-11 - “Hammer-11, I see a northeast / southwest runway, with a road extending east from the north end of
the runway.”
Halo-11 - “Hammer-11, using the runway as one unit of measure, the target is half a unit from the north end of
runway along that east running road, target is a tank pointed east.”
Hammer-11 - “Hammer-11, tally target.”
</pre>
=== Putting it all together ===

Here's the script for the JTAC interaction with a CAS aircraft in the target area:

ACFT: Checks in w/ number/type, location, ordenance, playtime

JTAC: keyhole, type 2/3 in effect, echo point is XXX YYY (description and/or coordinates)

JTAC: proceed to and hold at A/B/C/D NN Angels NN, report established

JTAC: SITREP - enemy strength, nearby friendlies, restrictions, hazards

JTAC: GAMEPLAN - Type 1/2/3 Bombs on (target|coordinates).
Report established and ready for 9-line

ACFT: established/ready

JTAC: NINE-LINE
Entry Keyhole delta, heading NNN, NN distance,
Elevation NNN
Target is DESCRIBE,
Located DESCRIBE
Marked by SMOKE|LASER code NNNN
Friendlies are JTACS_LOCATION
Egress Keyhole ABCD
Advise ready remarks

ACFT: READY

JTAC: ordinance type pilots discretion; RESTRICTIONS,
readback target location, restrictions,
report ready for talk-on

ACFT: (does readback), ready for talk-on

JTAC/ACFT - talked into seeing the target

JTAC: report IP and INBOUND

ACFT: IN from the north/south/east/west

JTAC: cleared HOT (single/type 2) or to ENGAGE (multiple/type 3)

ACFT/JTAC - report firing, shack's, aaa/sams etc.

ACFT: 'OUT' to the north/south/east/west

JTAC: direct ACFT back to the holding point, and ready to copy next 9-line

== Being a Human JTAC ==

Filling the role of a human JTAC is a great way for assaulting an enemy airbase to capture it, such as Krymsk or Kraznodar in phase one; Gudata or Beslan in phase 2.

So how does one become a 'human JTAC' within the context of a DCS multiplayer environment? There are a few options:

==== CTLD - AI JTAC ====

Grab your huey or hip, load a CTLD JTAC group, and take it to a suitable location on a hill outside your target area. The advantage is that AI JTAC will automatically Lase and Smoke targets, leaving you just the communication portion. You can also pick up the group and move them to a new area once the targets are all shack'ed. The drawback is that the AI selects/prioritizes the targets (not you).

This is the method I've used for JTAC

==== CTLD - HMMVW AND CI ====

Grab your huey or hip, load a CTLD Tow HMMWV, drop it on a suitable hill near your target. Now jump into a JTAC/Observer role, and use 'combined arms' to control the HMMWV. Use binocular view to select and lase targets.

The advantage is you can pick/prioritize the targets and you control the laser. The downside is that using smoke is less effective (it only lasts 60 seconds).

==== 'spectator' mode ====

Stay with the 'spectator' role and use F10/F7 to observe a target area. Use SRS in AWACS mode for communication. One big upside is you don't have to spend a bunch of time flying a huey somewhere (and get shot down in the process). And you can see everything in the target area. But the downside is that you cannot mark a target with laser or smoke. You will have to be very good with your talk-on's.

One trick is that all enemy vehicles are by-default spawned in facing North, so you can quickly determine what way you are facing in F7 view by noting the vehicles' orientation.

==== FAC(A) (jtac in a plane) ====

You can also do airborne Forward-Air-Controller, using an aircraft with a laser designator and targeting system, such as an Apache, Gazelle, or A-10 with a tpod. Downside here is you have to fly, communicate, and work your laser (autopilot modes should help!). Also you can't mark with smoke, and you only have so many pounds of Jet-A before you have to go off station.

---

Once you are ready, select a frequency to use to do your controlling, and announce it on SRS common and on discord ala:

!gci sunrise gaw RAMBO 32.0FM Beslan JTAC Keyhole type 2 in effect, ECHO is Beslan Airfield. check in with
aircraft, location, loadout, & playtime

If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency

==== Deconfliction ====

One of the most important responsibilities for a JTAC is deconfliction, ensuring one aircraft does not fly into or drop ordinance on another. This happens both during the attack and while aircraft are holding for their turn to run-in.

The easiest way to provide separation for multiple aircraft waiting their turn for 'inbound' is to do a simple vertical stack at the holding point. Simply stack aircraft, separating them by some amount. For example, these aircraft are deconflicted by assigning them holding points with 2000ft vertical separation:

stryker 1-1 at Alpha 10 angels 12
lightning 1-1 at Alpha 10 angels 14

Another deconfliction example with Apaches and fixed wing strike aircraft. In this example you could have two groups conducting simultaneous attacks, while safely deconflicted from one another..

Apaches: IP is Delta 5, restricted at or below 2k, type 3, restricted to targets West side of the airfield

F18 Flight IP is Alpha 8, egress Bravo, restricted hard deck angels 4, type 2 (and assigned single targets to
the east side of the airfield)

This ensures the apaches and F18 have vertical separation (Apaches low, F18 high) and deconflicts ordinance release, type 2 for the F18 on specific targets east of the field reduces risk of 'splash damage' to the Apaches operating west.

==== Other Considerations ====

Know the state of SAM's in your target area. you may want to wait until the medium/long range sams have been knocked out by anti-radiation missiles. Warn your pilots about any enemy /hazards/ like AAA or manpads. Be sure you maintain your control points outside of the range of the enemy. its also handy to have some CAP aircraft that ensure your CAS flights aren't getting engaged while orbiting at their control points.

Keep an eye out for threats while your pilot is "in" - call out 'SAM' (sam launch) or 'GUN' (aaa fire). Keep your pilots away from threats, above 12k for MANPADS, and above 7k for AAA.

Have the high ground - set up your JTAC position on a hill such that you can look down on your targets.

I dont know if it's legit, but I will often set a control point at say 'Alpha 12' and the IP at 'Alpha 8' - just have the pilot run in from their control point flying straight to target (reporting 8 )

I vary type 2 / type 3 control based on number of aircraft I have in my AO. If there's only one aircraft, I'll clear them in under type 3 so they can kill as many enemy units as they can on a single pass. If I have multiple aircraft I will do type-2 control, as this shortens the wait for the queued aircraft and gives everyone a chance to get kills.

If using keyhole, entry direction will be opposite your keyhole location. i.e. if a pilot's entry is keyhole Alpha (North) their entry direction can be '180' (South)

== Tips for Pilots ==

Keyhole points are oriented at the target 'ECHO' point. you can use your planes nav system to orient by setting your bullseye to the ECHO waypoint

if your airframe has a laser spot tracker know how to use it, it will ease the talk on and identification of the target if your LST can just acquire it for you

== Resources ==

Keyhole CAS briefing by JUICE https://www.youtube.com/watch?v=tpbojyXDKeA

Example of providing JTAC/FAC(A) by RotorScout https://www.youtube.com/watch?v=ltHPoQJuNHU

JTAC controls in Combined Arms by JUICE https://www.youtube.com/watch?v=FFDOGIxb_Nc&t=454s

https://sofrep.com/fightersweep/what-close-air-support-is-and-isnt-part-two/

https://irp.fas.org/doddir/dod/jp3_09_3.pdf

User:Krad 1337

2022-06-29T23:23:51Z

Krad 1337:

All about me - usually found on the servers as Rocky 1-1

[[JTAC]]

User:Krad 1337

2022-06-29T23:22:35Z

Krad 1337: Created page with "All about me - usually found on the servers as Rocky 1-1"

All about me - usually found on the servers as Rocky 1-1