Close Air Support - Versionshistorik

DeadGun den 14 mars 2026 kl. 22.02

2026-03-14T22:02:40Z

DeadGun den 14 mars 2026 kl. 21.36

2026-03-14T21:36:20Z

DeadGun den 14 mars 2026 kl. 19.57

2026-03-14T19:57:42Z

DeadGun den 12 januari 2024 kl. 13.18

2024-01-12T13:18:09Z

DeadGun: /* Types of Control */

2023-07-18T11:04:17Z

Types of Control

DeadGun: /* Abbreviations */

2023-07-18T10:50:38Z

Abbreviations

DeadGun: /* Execution */

2023-07-17T15:09:34Z

Execution

DeadGun: /* Execution */

2023-07-17T15:07:20Z

Execution

DeadGun: /* Execution */

2022-08-17T13:19:26Z

Execution

DeadGun: /* Execution */

2022-08-16T17:00:46Z

Execution

@@ Rad 27: / Rad 27: @@
 ===Battle Tracking===
-Effective battle tracking will aid in maintaining and understanding of friendly and enemy progress, reduce redundant targeting, and reduce the possibility of friendly fire. JTAC must operate with the most currint information including:
+Effective battle tracking will aid in maintaining and understanding of friendly and enemy progress, reduce redundant targeting, and reduce the possibility of friendly fire. </br>
 :- FSCM's/ACM's
 :- Friendly Unit Information. (Unit boundaries, phase lines, friendly locations, objectives, etc.)
@@ Rad 35: / Rad 36: @@
 ===Risk Assessment===
-JTAC should make continuous risk assessments. CAS is not always the best option!
+JTAC should make continuous risk assessments. CAS is not always the best option! </br>
 Information to consider:
 :- Confidence in and the training of the personnel involved
@@ Rad 45: / Rad 46: @@
 ===Colleteral Damage===
-Collateral damage is unintentional injury or damage to noncombatant persons or objects.
+Collateral damage is unintentional injury or damage to noncombatant persons or objects. </br>
 The JTAC should make a Collateral Damage Estimation (CDE) by answering five basic questions.
@@ Rad 54: / Rad 54: @@
 # If not, how many noncombatants do I think will be affected by this attack?
 # Are the collateral effects in relation to the advantage gained?
 ===Fire Support Coordination Measures===
@@ Rad 91: / Rad 67: @@
 *Contact Point / Initial Point / Battle Position Selection
-::CP's/IP's/BP's should be based on enemy/friendly  capabilities, target/friendly location, weather etc. CP's and HA's should be visual points so that aircrew can visually acquire them and should be at such distance from target area that its safe from ground threats during holding.
+::CP/IP/BP should be based on enemy/friendly  capabilities, target/friendly location, weather etc. CP and HA should be visual points so that aircrew can visually acquire them and should be at such distance from target area that its safe from ground threats during holding.
 *Keyhole template
@@ Rad 105: / Rad 81: @@
 ===Pre-Combat Preperations===
-Pre-combat checks and pre-combat inspections allow personnel to prepare for a mission and provide the leader/supervisor an opportunity to ensure the operational readiness of personnel and equipment.
+* Ensure included personnel understands the mission, end-state, scheme of maneuver, and fires including:
+::- The ground force commander’s intent and the ground force scheme of maneuver
 ::- Threat scheme of maneuver
 ::- Communications plan
-::- Tasked ATO assets
+::- Tasked assets
 * Ensure distribution of graphics and/or overlays depicting:
 ::- Scheme of maneuver.
-::- FSCM's
+::- FSCM
-::- ACM's
+::- ACM
-::- NAIs and/or TAIs
+::- NAI/TAI
-::- Decision points and triggers
+::- Decision points
-::- Aircraft CPs and IPs
+::- CP/IP/HA/BP
 ::- Friendly marking procedures (Day/Night)
 ::- Laser guided munitions/designator codes
@@ Rad 156: / Rad 127: @@
 The JTAC provides a short summary of how the attack is going to be performed.
 Game plan shall include:
 * Type of control (1,2 or3)
 * Method (BOT/BOC)
 The game plan ''may'' include:

@@ Rad 68: / Rad 68: @@
 ===Method of Attack===
 * BOC
-:A BOC attack is used when the JTAC determines that he can create the desired effects against the target with CAS aircraft employing ordnance on a specified set of coordinates.
+:Aircraft employing ordnance on a specified set of coordinates.
-:For BOC missions, all aircraft delivering ordnance must readback Line 4 and Line 6 from their system or weapon, as appropriate, in conjunction with Line 8 and required restrictions. Aircrew will not modify coordinates once read back is complete.
+:All aircraft delivering ordnance must readback Line 4, Line 6 (from system/weapon), Line 8 and restrictions.
 *BOT
-:A BOT attack requires that the JTAC's intended target or mark are TALLY/CONTACT/CAPTURED by the aircrew.
+:Target are confirmed TALLY/CAPTURED by the aircrew.
-:For BOT missions, only the flight lead is required to readback lines 4, 6 and 8 in conjunction with other required restrictions. All attack aircraft will provide readbacks only if requested by the JTAC.
+:Only the flight lead is required to readback lines 4, 6, 8 and restrictions.
 ===Fire Support Coordination Measures===
@@ Rad 93: / Rad 91: @@
 *Contact Point / Initial Point / Battle Position Selection
-::The JTAC selects the CP's/IP's/BP's based on enemy capabilities, target orientation, friendly location, weather, aircraft capabilities, and FSCM's. CP's and IP's should be visually significant geographic points whenever possible so that aircrew can visually acquire them in the event of a degraded navigation systems or GPS-denied environments. IP's and BP's should be in such distance from target area that allows for safety of the aircraft from enemy AD threat, during holding and for employment of weapons, typically 5 to 15 NM. Actual distance therefore depends on anticipated threat, aircraft and weapons used. For example FW PGM delivery run typically begins about 8-10NM from the target. High altitude aircraft may require IP's in excess of 20 nautical miles from the target. If ground forces want to achieve surprise the holding distance should prevent the enemy from spotting the aircraft and reduce the noise to minimum.
+::CP's/IP's/BP's should be based on enemy/friendly  capabilities, target/friendly location, weather etc. CP's and HA's should be visual points so that aircrew can visually acquire them and should be at such distance from target area that its safe from ground threats during holding.
 *Keyhole template
-::Keyhole is an efficient method for establishing an IP/BP in the absence of control points or their location does not sufficiently support target engagement. When CAS aircraft are passed to a JTAC from a contact point, the JTAC should immediately pass an “Echo” point (typically the target) to those CAS players, and then anchor their hold point off of the target with a direction and distance.
+::Keyhole is an efficient method for establishing reference points.
-::JTAC may also send other than target coordinates (for example center of the target area), however this has to be clearly communicated to the aircrew. The standard keyhole method is to label each of the cardinal directions with a letter: A – North, B – East, C – South, D – West and E – Overhead Target and use radials when cardinal/subcardinal directions are not appropriate. Distances are expressed in nautical miles (for FW) or kilometers (RW). FW Aircraft should hold outside the distance given. For RW the distance given is considered the center of BP.
+::E or "Echo Point" is set at center of target area. The different cardinals are referred to by letters: A for North, B for East, C for South, D for West. Radials are to be used in between. Distances are expressed in nautical miles (for FW) or kilometers (RW). FW Aircraft should hold outside the distance given. For RW the distance given is considered the center of BP.
 ::''Note: If holding multiple aircraft around one Echo point the JTAC should consider deconflicting all the players also by altitude, as holding patterns of some players may accidentally overlap during holding.''

@@ Rad 1: / Rad 1: @@
 ''[[Home]] >> [[Tactical Guides]] >> [[Close Air Support]]''
-CAS is an air action against hostile targets which are in close proximity to friendly forces and which require detailed integration of each air mission with fire and movement of those forces. CAS provides ground or amphibious forces with firepower in offensive and defensive operations, by day or night, to destroy, suppress, neutralize, disrupt, fix or delay enemy forces in close proximity to friendly ground forces. The firepower and mobility of aircraft can make an immediate and direct contribution to the surface battle, especially against targets that are either inaccessible or invulnerable to available surface weapons effects. The variety of targets likely to be encountered makes it important to be able to employ a variety of weapons and delivery systems, thus reliable and interoperable communications with the supported force are essential features in the CAS environment.
+Close Air Support (CAS) is an air action against a hostile targets which are in close proximity to a friendly forces and which require detailed integration of each air mission with fire and movement of those forces.
+CAS procedures are to be conducted at any time friendly forces are in close proximity to enemy forces.
 Terminal Attack Control is the authority to control the maneuver of and grant weapons release clearance to attacking aircraft. A qualified JTAC, in accordance with CAS Syllabus, will be recognized across MA as capable and authorized to perform TAC operations.
@@ Rad 30: / Rad 29: @@
 Effective battle tracking will aid in maintaining and understanding of friendly and enemy progress, reduce redundant targeting, and reduce the possibility of friendly fire. JTAC must operate with the most currint information including:
 :- FSCM's/ACM's
-:- Friendly Unit Information. Unit boundaries, phase lines, friendly locations, objectives, etc.
+:- Friendly Unit Information. (Unit boundaries, phase lines, friendly locations, objectives, etc.)
 :- Current and planned artillery locations and gun-target lines.
 :- Enemy Locations including surface-to-air threats.
@@ Rad 36: / Rad 35: @@
 ===Risk Assessment===
-In addition to proper battle tracking, the supported commander and JTAC makes continuous
+JTAC should make continuous risk assessments. CAS is not always the best option!
-tactical risk assessments. Risk assessments involve the processing of available information
+Information to consider:
-to ascertain a level of acceptable risk to friendly forces or civilians. Based on the current risk
+:- Confidence in and the training of the personnel involved
 :- Confidence in battle tracking
 :- Confidence in targeting information
 :- Ordnance available for attack
 ===Colleteral Damage===
-Collateral damage is unintentional or incidental injury or damage to persons or objects that
+Collateral damage is unintentional injury or damage to noncombatant persons or objects.
-The CDE process does not limit or supersede a commander’s responsibility to
+The JTAC should make a Collateral Damage Estimation (CDE) by answering five basic questions.
 # Can I make a positive identification of the object I want to affect?
-# Are there protected or collateral objects, civilian or noncombatant personnel, involuntary or unwitting human shields, or significant environmental concerns within the effects range of the weapon I would like to use to attack the target?
+# Are there "collateral objects / noncombatants" within the effects of the weapon I would like to use?
-# Can I mitigate damage to those collateral concerns by striking the target with a different weapon or with a different method of engagement, yet still accomplish the mission?
+# Can I mitigate damage to those collateral concerns by striking the target with a different weapon or with a different method of engagement?
-# If not, how many civilians and noncombatants do I think will be injured or killed by this attack?
+# If not, how many noncombatants do I think will be affected by this attack?
-# Are the collateral effects of my attack excessive in relation to the expected military advantage gained, and do I need to elevate this decision to the next level of command to attack the target based on the ROE in effect?
+# Are the collateral effects in relation to the advantage gained?
 ===Types of Control===
 * Type 1
-:: JTAC will visually acquire the target and the attacking aircraft during the terminal phase of an attack, prior to weapons release, and assess attack aircraft geometry while maintaining control of individual attacks.
+: The JTAC will visually acquire the target and the attacking aircraft during the terminal phase of an attack and maintaining control of individual attacks.
 * Type 2
-: JTAC will utilize other measures to mitigate risk while maintaining control of individual attacks. : While not required, if the tactical situation allows, the JTAC should make every effort to gain a visual on the aircraft and assess attack geometry under Type 2 control in order to provide an additional measure of safety, enhance SA, and be able to abort the attack if necessary.
+: While not required, the JTAC should make every effort to, gain a visual on the aircraft during the terminal phase of an attack and maintaining control of individual attacks.
+:* The JTAC should state "BLIND, CLEARED HOT" if unable to gain a visual on the aircraft.
 * Type 3
-: JTAC will utilize other measures to mitigate risk and assesses that the measures in place will allow multiple attacks within the same engagement.
+: The JTAC will allow multiple attacks within the same engagement.
 ===Method of Attack===

@@ Rad 321: / Rad 321: @@
 ''Note: For safety, "cleared hot!" are words ONLY to be said by the JTAC, ever. You are not allowed to asked "am I cleared hot?".
-When the pilot fires, he should preferably call out the weapon release. For instance "Pickle" (all bombs) or Rifle (air-to-ground missile, like a Maverick). No callout is needed for a strafe.
+When the pilot fires, he should preferably call out the weapon release. For instance "Bombs Away" or Rifle (air-to-ground missile, like a Maverick). No callout is needed for a strafe.
 When the pilot has fired, he calls "Off" if he has fired, or "Off dry" if he didn't fire.

@@ Rad 114: / Rad 114: @@
 : JTAC will utilize other measures to mitigate risk and assesses that the measures in place will allow multiple attacks within the same engagement.
-: While not required, if the tactical situation allows, the JTAC should make every effort to gain a visual on the aircraft and assess attack geometry under Type 2 control in order to provide an additional measure of safety, enhance SA, and be able to abort the attack if necessary.
+: While not required, if the tactical situation allows, the JTAC should make every effort to gain a visual on the aircraft and assess attack geometry under Type 3 control in order to provide an additional measure of safety, enhance SA, and be able to abort the attack if necessary.
 :Used when:
 :: - JTAC requires the ability to provide clearance for multiple attacks within a single engagement subject to specific attack restrictions.
 ===Method of Attack===

@@ Rad 443: / Rad 443: @@
 ==Abbreviations==
 *<b>ATM</b> Air Tasking Message
 *<b>ATO</b> Air Tasking Order
@@ Rad 454: / Rad 456: @@
 *<b>FFA</b> Free Fire Area
 *<b>FO</b> Forward Observer
-*<b>FSCM</b> Fire Support Coordination Line
+*<b>FSCL</b> Fire Support Coordination Line
 *<b>FSCM</b> Fire Support Coordination Measures
 *<b>HA</b> Holding Area

@@ Rad 189: / Rad 189: @@
 [[Fil:AMSL.png|400px|thumb|AMSL MA TRAINING 2022]]
 When the flight is established at the contact point (CP), they will contact the JTAC and if unencrypted comms is used the pilot should challange the JTAC using [https://wiki.masterarms.se//index.php/Comms#RAMROD RAMROD] or [https://wiki.masterarms.se//index.php/Comms#AMSL AMSL].
-In our case the JTAC will typically pass an Echo point (target area) to the flight. If the flight is ''not'' able to work with MGRS coordinates (which is standard), and need some other format (typically DDD° MM.MMM' coordinates), this should be mentioned before the echo point is communicated. The JTAC might also give the flight instructions to proceed to another location in relation to the echo point.
+In our case the JTAC will typically pass an Echo point (target area) to the flight. If the flight is ''not'' able to work with [https://wiki.masterarms.se/index.php/Geographical_Reference_Systems_(WIP)#MGRS MGRS] coordinates (which is standard), and need some other format (typically [https://wiki.masterarms.se/index.php/Geographical_Reference_Systems_(WIP)#Latitude_and_Longitude DDD° MM.MMM'] coordinates), this should be mentioned before the echo point is communicated. The JTAC might also give the flight instructions to proceed to another location in relation to the echo point.
 ''Note: The actual check-in has not happened yet. The JTAC typically wants to point the flight in the right direction before that, in order to save time.''

@@ Rad 188: / Rad 188: @@
 ===Initial contact===
 [[Fil:AMSL.png|400px|thumb|AMSL MA TRAINING 2022]]
-When the flight is established at the contact point (CP), they will contact the JTAC and if unencrypted comms is used the pilot should challange the JTAC using RAMROD or AMSL.
+When the flight is established at the contact point (CP), they will contact the JTAC and if unencrypted comms is used the pilot should challange the JTAC using [https://wiki.masterarms.se//index.php/Comms#RAMROD RAMROD] or [https://wiki.masterarms.se//index.php/Comms#AMSL AMSL].
 In our case the JTAC will typically pass an Echo point (target area) to the flight. If the flight is ''not'' able to work with MGRS coordinates (which is standard), and need some other format (typically DDD° MM.MMM' coordinates), this should be mentioned before the echo point is communicated. The JTAC might also give the flight instructions to proceed to another location in relation to the echo point.
@@ Rad 203: / Rad 203: @@
 # Playtime
 # Relevant capabilities (TGP, VDL, NVG, etc.)
-# Abort code (if needed using AMSL/RAMROD otherwise "in the clear")
+# Abort code (if needed using [https://wiki.masterarms.se//index.php/Comms#AMSL AMSL]/[https://wiki.masterarms.se//index.php/Comms#RAMROD RAMROD] otherwise "in the clear")
 ===Situation Update===

@@ Rad 194: / Rad 194: @@
 ===Check-in===
+[[Fil:Check-in.png|400px|thumb|Check-in]]
 The flight should not ''check-in'' until the JTAC asks them to. JTACs should be directive about when they want the aircraft to check-in, providing the details on the flight's capabilities.  When the flight checks in, the following info should be included:
@@ Rad 206: / Rad 206: @@
 ===Situation Update===
 The JTAC provides a short overview on what's happening, and if there is anything the flight needs to know, like any hazards (air defence threat, other CAS flights), enemy and friendly forces situation and artillery activity.
@@ Rad 211: / Rad 212: @@
 ===Game plan===
 The JTAC provides a short summary of how the attack is going to be performed.
 Game plan shall include:
@@ Rad 223: / Rad 225: @@
 ===CAS-brief===
 The CAS brief is the standard for use with FW and RW aircraft. The brief is used for all threat
 conditions and does not dictate the CAS aircraft’s tactics. It consist of 9-line, remarks and