JTAC - Revision history

Krad 1337 at 17:38, 18 August 2023

2023-08-18T17:38:47Z

Krad 1337: /* Joint Terminal Attack Controllers */

2022-06-30T16:08:34Z

‎Joint Terminal Attack Controllers

Krad 1337 at 01:50, 30 June 2022

2022-06-30T01:50:32Z

Krad 1337 at 01:48, 30 June 2022

2022-06-30T01:48:50Z

Krad 1337 at 01:36, 30 June 2022

2022-06-30T01:36:34Z

Krad 1337: /* What is JTAC */

2022-06-29T23:54:51Z

‎What is JTAC

Krad 1337: /* What is JTAC */

2022-06-29T23:54:36Z

‎What is JTAC

Krad 1337: /* What is JTAC */

2022-06-29T23:53:54Z

‎What is JTAC

Krad 1337: /* Putting it all together */

2022-06-29T23:41:12Z

‎Putting it all together

Krad 1337 at 23:39, 29 June 2022

2022-06-29T23:39:53Z

@@ Line 108: / Line 108: @@
   ACFT: READY
-  JTAC: ordinance type pilots discretion; RESTRICTIONS,
+  JTAC: ordinance type pilots discretion; RESTRICTION,
     readback target location, restrictions,
     report ready for talk-on
@@ Line 174: / Line 175: @@
 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:
+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.
 <pre style="background-color: #ccc;font-family: 'Lucida Console'">
-  stryker 1-1 at Alpha 10 angels 12
+  stryker 1-1 at Alpha 10 angels 12 block 13
-  lightning 1-1 at Alpha 10 angels 14
+  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..

@@ Line 1: / Line 1: @@
 == 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.
+[[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 ===
@@ Line 33: / Line 36: @@
 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
@@ Line 123: / Line 128: @@
   JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
 </pre>
 == Being a Human JTAC ==

@@ Line 1: / Line 1: @@
 == 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.
+[[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 ===

@@ Line 1: / Line 1: @@
 == 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_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.
@@ Line 36: / Line 39: @@
 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'.
@@ Line 118: / Line 125: @@
   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.
@@ Line 159: / Line 168: @@
 ==== 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.
@@ Line 175: / Line 185: @@
 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.
@@ Line 191: / Line 203: @@
 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

@@ Line 1: / Line 1: @@
-== What is a JTAC ==
+== Joint Terminal Attack Controllers ==
-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:
+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.
-* To direct the attacking aircraft to prevent friendly casualties
+[[File:jtac_working.jpg]]
-=== Overview of the process ===
+=== How CAS flights work with JTAC's ===
-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.
+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, and the JTAC will either assign another target via a new 9-line or release the pilot.
+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 ===
@@ Line 16: / Line 15: @@
 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.
+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'.
@@ Line 24: / Line 23: @@
 [[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:
+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 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 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
+''Type III'': The JTAC can clear multiple attacks within a single engagement
-Bombs on XX:
+And, finally '''Bombs on X'':
-Bombs on Target (BoT): JTAC will do a 'talk on' to the target
+''Bombs on Target (BoT)'': The JTAC will do a 'talk on' to the target
-Bombs on Coordinates (BoC): JTAC provides high-precision lat/long of the target
+''Bombs on Coordinates (BoC)'': The 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 ordinance the pilot checks in with can inform whether the JTAC directs them for BoT or BoC.
 === The 9-line ===
@@ Line 151: / Line 150: @@
 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
 If a human GCI/AWACS is on let them know they can direct CAS assets to your location and frequency
@@ Line 164: / Line 164: @@
 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
+</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)
+   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.
@@ Line 189: / Line 189: @@
 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 ==

← Older revision		Revision as of 23:54, 29 June 2022
Line 1:		Line 1:
−	== 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:		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:

@@ Line 3: / Line 3: @@
 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
+* To direct the attacking aircraft to prevent friendly casualties
-	* And to direct the attacking aircraft on to their targets
+* And to direct the attacking aircraft on to their targets
 === Overview of the process ===

@@ Line 73: / Line 73: @@
 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
@@ Line 118: / Line 118: @@
   JTAC: direct ACFT back to the holding point, and ready to copy next 9-line
 == Being a Human JTAC ==