5-71. The FDC computer executes fire missions by establishing and updating relevant information. This function is graphically depicted in figure 5-3.
Figure 5-3. Fire Mission Execution
T
ARGETA
NALYSIS5-72. Upon receipt of a fire mission message, the computer screens the target to determine the requirements for target analysis. The computer analyzes the target using the following information to determine its placement in the commander's criteria and to specify priority or non-priority handling:
• Type/subtype/element.
• Location.
• Strength.
• Behavior.
• Permanence and age.
W
EAPON(M
UNITIONS/S
UB MUNITIONS) S
ELECTION5-73. Targets/missions received from a higher echelon computer that specify a weapon to be employed are evaluated. Although subordinate FDCs have the capability to change the weapon type, authorization to modify missions directed by a higher echelon computer must be coordinated. If the FDC is authorized to change the weapon directed, it must be done manually.
5-74. If ATACMS or Guided Unitary is selected, the AFATDS that performs the initial fire mission processing creates platoon airspace hazard (PAH) and target airspace hazard (TAH) geometries.
Platoon Air Hazard Message
5-75. When the AFATDS processes an AFOM fire mission or guided mission, it generates a PAH message. The message describes the aircraft danger area around the launcher selected to fire as the PAH.
The area is defined by 2 grids on the ground and a width giving the PAH 4 grids on the ground (depicted in figure 5-4 by the points 1, 2, 3, and 4) and an altitude (depicted in figure 5-4 as ZALT). This area is used to warn all flight operations and to gain clearance to fly through the airspace. If more than 1 LCHR is required to fire the mission, separate messages are displayed for each LCHR.
5-76. The platoon air hazard message is munition specific. It is generated only for those LCHR the computer has listed as having the munition. If a unit to fire in effect (UFFE) was specified in the fire mission message, that UFFE is used. If a UFFE was not specified, the computer provides the best solution based on available information. The operator can enter the XDIST value and an effective date-time group (DTG) indicating when the platoon air hazard area is valid.
5-77. The PAH may be passed to other organizations as a restricted operations zone (ROZ) also known as a restricted operations area. A ROZ is a volume of space that the Air Force often uses to restrict airspace.
The same 4 points (1, 2, 3, and 4 in figure 5-4) and altitude define the ROZ. The term restricted operations zone is being replaced by restricted operations area but the former term may still be encountered.
Figure 5-4. AFOM Platoon Air Hazard Area
Target Air Hazard Message
5-78. The TAH message describes the TAH area where the missile will dispense the submunitions. Like the platoon air hazard message, it is used to warn all flight operations and to gain airspace clearance. The platoon air hazard message is generated when an AFOM fire mission is processed. The Block I and 1A target air hazard message defines 4 points on the ground around the target. The size of the hazard depends on the range to the target. The ZALT defines the height of the airspace hazard based on the target center and munitions’ burst point. Figure 5-5 depicts the default Block I and 1A target air hazard airspace (ZALT 1,500 meters or less). The computer alerts the operator when the target air hazard airspace is other than the default (when ZALT exceeds 1,500 meters). The operator entries are limited to defining the effective DTG of the message.
Figure 5-5. Default Block I and 1A Target Air Hazard Area
5-79. Upon receipt of the Mission Fired Report MFR from the fire unit, the AFATDS will generate a mission fired report (MFR) and forward it through the mission chain. An MFR or DENY message will purge the PAH and TAH geometries.
B
ATTLEFIELDG
EOMETRYV
ALIDATION5-80. The FDC computer validates that the fire mission does not violate any FSCM or downrange mask restrictions. FSCM violations will be presented to the operator in the form of a warning message, but the
computer can continue to process the fire mission. Downrange mask violations will be presented in the form of an error message and will prevent the operator from continuing the mission.
5-81. The fire mission support function establishes or updates the map modification, geometry, ammunition effects, and meteorological databases to enhance tactical fire control. This function is depicted in figure 5-6.
Figure 5-6. Fire Mission Support Function 5-82. Coordinate conversion includes the following:
• Zone-to-zone transformation.
• Zone-to-zone across grid zones.
• Spheroid conversion.
• Datum conversion.
• Geodetic/ Universal Transverse Mercator (UTM).
5-83. Battlefield geometry maintenance—
• Overwrites duplicate geometry features.
• Reports overlap of SPRT;ZNE messages.
F
IREU
NITS
ELECTION5-84. Fire unit selection in the FDC computer is based on the following:
• Availability—no more than the allowable number of fire missions at each launcher.
• Appropriate munitions onboard or at next reload point.
• Within range of selected munitions.
• No exclusions.
• Able to meet all time restrictions.
M
ETHOD OFA
TTACK/E
FFECTSA
NALYSIS Volleys-Type Target5-85. If the target is designated as a volleys type, all rockets are normally aimed at the center of the target, unless the size or shape is large and specified. If the number of rockets to be fired at the 1 aim-point is entered in the volleys field of the message, that number of rockets is fired at the target center. If there is no entry, a default value of 6 rockets is used.
Effects-Type Target
5-86. If the target is designated as an effects-type target, the AFATDS may generate multiple aim-points.
The computer performs effects calculations and determines the expected effects for each target selected for engagement on the basis of weapon performance, capability characteristics, and target degree of protection.
Other processes involved with effects-type targets include:
• The target type is checked to be sure it is a legal effects type. If it is not, a warning message is displayed.
• The target dimensions are checked to verify that they are within the size limits for MLRS processing. If they are not, the computer stops processing and the mission is rejected and redisplayed for transmission back to the higher headquarters.
• The computer designates 1 to 6 aim-points for an effects target. The number of aim-points for an effects-type target and the number of rockets to be fired at each aim-point depend on the following:
• Desired effects (for effects-type target only).
• Dimensions of the target.
• Range to target from the launcher.
• Lethal area of submunitions in relation to target type.
• Disposition of enemy personnel in the target area.
• The computer rejects the fire mission request when the percentage of effects requested cannot be achieved and/or the solution indicates more than the maximum number of rounds to fire (for an effects-type target only).
• The number of aim-points (aim-point easting and northing offset from target center) and number of rockets required for each aim-point are temporarily stored for use by the fire unit selection routing.
Joint Munitions Effectiveness Manuals
5-87. Effectiveness tables published in JMEM/SS provide guidance for determining the expected fraction of casualties to personnel targets or damage to materiel targets. JMEMs for surface-to-surface weapons are published as field manuals. The basic data for these manuals were obtained from test firings, actual combat performance, and mathematical modeling. Using JMEMs to determine attack data requires considerable time. Because of time constraints, use of JMEMs at battalion and battery FDC levels for engaging targets of opportunity is not recommended. The effects data included in these manuals incorporate reliability, delivery accuracy, and munitions lethality against a representative spectrum of targets. The computational assumptions, defeat criteria, and instructions for use are included in each manual.
Note: There is no assurance that the expected fraction of damage or casualties will be provided by any number of volleys in a given situation. Although not precisely within the mathematical definition, the method of averaging data used for the tables will result in less damage being realized for approximately 50 percent of the rounds and, conversely, greater damage for the other 50 percent of the rounds.
C
OMMANDER'
SC
RITERIA5-88. The key to exploiting automated processing is incorporating the commander's guidance into the computer's database. The commander influences tactical fire control solutions by establishing the commander's intent, which is used to develop the commander's criteria for engaging targets. These criteria guide the selection of units to fire, munitions, and volume of fire for each mission. The AFATDS, based on a portion of the commander's criteria, selects targets for MLRS engagement. It helps in the fire planning, collation of intelligence, and tactical fire control (TFC) for MLRS. The commander's criteria should be entered into AFATDS before the fighting begins. When they have been entered, the computer will automatically execute the criteria without delaying fire mission processing.
5-89. Commander's criteria are established and updated as the situation changes. They may be overridden manually when a situation warrants. As circumstances and SOP dictate, the battalion operations officer, battery operations officer, and/or fire direction personnel can override the commander's modifications on a mission-to-mission basis. A specific request for fire overrides the commander's criteria. Extreme care must be used in modifying the execution of the commander's criteria, because their effect on the AFATDS solutions influences the outcome of the battle. The parameters involved in establishing the commander's criteria are discussed below.
5-90. The supported force commander's concept for fires is used to develop engagement criteria. When given an R mission, the MLRS unit will use the criteria of the reinforced unit supported maneuver force.
When assigned a GSR or GS mission, the MLRS unit will use the criteria of the force headquarters.
5-91. Commanders can override the attack criteria for each target type and can specify an SVF for an effects target. However, they cannot specify desired effects for a volleys target. For a volleys target, the SVF works with the volleys size factor to generate the computer recommendation for the total number of volleys to fire on the target.
Munition Selection Matrix
5-92. Table 5-6 gives the fire planner a matrix for determining the best MLRS munition with which to defeat a target. For a complete listing see TB-11-7025-354-10-3
Table 5-6. Ammunition Selection Matrix Target Types Range
(km) Payload
(Submunitions) Projectiles Per Pod M26 Rocket Personnel, light armor, soft
vehicles (stationary) 10-32.5 644 M77 6
M26A2 Extended Range Rocket
Personnel, light armor, soft vehicles (stationary)
13-45 518 M77 6
M30 GMLRS Personnel, and/or light materiel (stationary)
15-70 404 M77 6
M31 Guided Unitary Personnel, and/or light
materiel (stationary) 15-70 1 6
M39 ATACMS Block I Personnel, and/or light
materiel (stationary) 25-165 950 M74
M39A1 ATACMS
Block IA Personnel, and/or light
materiel (stationary) 70-300 300 M74 1
M39A3 ATACMS
Block II C2 nodes, log sites, SRBMs, ACV assembly areas
(stationary) or SRBMs, MRLs, SP artillery, ACV formations (moving)
35-145 13 BAT 1
M48/M57 ATACMS Personnel, and/or light 70-270+_ 1 1
Table 5-6. Ammunition Selection Matrix Target Types Range
(km) Payload
(Submunitions) Projectiles Per Pod Quick Reaction
Unitary
materiel Legend
ACV = armored combat vehicle C2 = command and control MRL = multiple rocket launcher
SP = self-propelled
SRBM = short range ballistic missile
MLRS Size
5-93. If the AFATDS AFU file contains MLRS fire units, the computer considers those units first to engage a target when the target radius exceeds the size entered in the MLRS size (MLRSIZ) modification.
F
IREM
ISSIONI
NTERVENTIONP
OINTS5-94. Another powerful capability AFATDS offers is the ability to eliminate the traditional mission delays associated with processing fire missions through multiple layers of fire support coordination. Not every mission needs to stop at every fire support node in the mission thread (digital route). See paragraph 4-41 for the operational implications of this capability.