Get Joint Tactical Airstrike Request Form
The Joint Tactical Airstrike Request form, known as the DD Form 1972, plays a critical role in the coordination of Close Air Support (CAS) within all branches of the U.S. Armed Forces. This document serves as a mandatory tool, except under specific conditions authorized by higher authorities, to precisely request airstrike support. The form is structured in distinct sections, including Mission Request, Coordination, and Mission Data, each requiring detailed information to ensure the accuracy and efficacy of the airstrike request. The form encompasses essential data points such as the unit making the request, the urgency and priority of the mission, target information encompassing location, type, and characteristics, as well as specific ordnance and result desired. Additionally, it outlines the coordination with other forces and artillery support, including restrictive fire plans or air plans in effect. The detailed instructions aim to provide clarity on the specification of the target, including its location by coordinates and even the desired timing for the airstrike. The ultimate goal of the Joint Tactical Airstrike Request form is to streamline the process of requesting air support, ensuring that such requests are clear, precise, and result in the most effective support for ground forces engaged in operations.
Joint Tactical Airstrike Request Example
Appendix D
Joint Tactical Airstrike Request
All U.S. Armed Forces use the JTAR Request Form (DD Form 1972) to request CAS. The use of this form is mandatory unless otherwise authorized by a higher authority. The following para- phrased instructions are included for reference only. A sample JTAR request form is shown in figure
D |
|
MCWP |
|
JOINT TACTICAL AIRSTRIKE REQUEST |
See JCS Pub 12, Vol II, for instructions for |
|
preparation. |
||
|
|
|
|
|
|
|
|
|
|
|
|
SECTION I - MISSION REQUEST |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DATE |
|||||||||||||||||||||||||||
1. |
UNIT CALLED |
|
|
|
THIS IS |
|
|
|
|
|
|
|
|
|
|
|
REQUEST NUMBER |
|
|
|
SENT |
|
|||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TIME |
|
BY |
|||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
2. |
PREPLANNED: |
A |
|
PRECEDENCE |
|
|
|
|
B |
|
PRIORITY |
|
|
|
|
|
|
|
|
|
|
|
|
|
RECEIVED |
||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TIME |
|
BY |
|||||||||||
|
|
IMMEDIATE: |
C |
|
PRIORITY |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
TARGET IS / NUMBER OF |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||
|
|
A |
|
PERS IN OPEN |
|
|
|
B |
PERS DUG IN |
|
|
C |
WPNS/MG/RR/AT |
|
|
|
D MORTARS, ARTY |
|
|
||||||||||||||||||||||||||||||||||
|
|
E |
|
AAA ADA |
|
|
|
|
|
F |
RKTS MISSILE |
|
|
G |
ARMOR |
|
|
|
H |
VEHICLES |
|
|
|||||||||||||||||||||||||||||||
3. |
I |
|
BLDGS |
|
|
|
|
|
J |
BRIDGES |
|
|
K |
PILLBOX, BUNKER |
|
|
|
L |
SUPPLIES, EQUIP |
|
|
||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
M |
|
CENTER (CP,COM) |
|
|
N |
AREA |
|
|
|
|
|
|
O |
ROUTE |
|
|
P |
MOVING N S E W |
|||||||||||||||||||||||||||||||||
|
|
Q |
|
REMARKS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TARGET LOCATION IS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CHECKED |
|||||||||||||||||
|
A |
|
|
|
|
|
|
|
|
B |
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||
4. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BY |
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(COORDINATES) |
|
|
|
|
|
|
|
|
|
|||||||||||||||||||||||
|
|
|
(COORDINATES) (COORDINATES) |
|
(COORDINATES) |
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||||
|
|
E |
|
TGT ELEV |
|
F |
SHEET NO. |
G SERIES |
|
|
|
|
H CHART NO. |
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TARGET TIME / DATE |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||
5. |
A |
|
ASAP |
|
B |
NI T |
|
|
|
|
|
C AT |
|
|
|
|
D |
|
TO |
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6. |
DESIRED ORD / RESULTS |
|
|
|
|
|
A ORDNANCE |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||
B |
|
DESTROY |
|
C |
|
NEUTRALIZE |
D HARASS / INTERDICT |
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FINAL CONTROL |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||
7. |
A |
|
FAC/RABFAC |
|
|
B |
CALL SIGN |
|
|
|
|
|
|
|
|
|
|
C |
|
FREQ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||||||||||||
|
|
D |
|
ASRT |
|
|
|
|
|
E |
*FREQ |
|
|
|
|
|
|
|
|
|
F |
|
FIX / CONT PT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
8. REMARKS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ACKNOWLEDGED |
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BDE / REGT |
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DIVISION |
|
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OTHER |
|||||||||
Figure
Close Air Support |
|
D - 3 |
|
SECTION II - COORDINATION
9. NGF |
|
|
10. |
ARTY |
|
11. AIO / G - 2 / G - 3 |
|||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
12. REQUEST |
|
|
13. |
BY |
14. REASON FOR DISAPPROVAL |
||||||||||||||
|
APPROVED |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DISAPPROVED |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
15. RESTRICTIVE FIRE PLAN / AIR PLAN |
16. IS IN EFFECT |
|
|
|
|
|
|
|
|
||||||||||
A IS NOT |
|
B |
NUMBER |
A (FROM TIME) |
|
|
B (TO TIME) |
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
17. LOCATION |
|
|
|
|
|
18. WIDTH (METERS) |
19. ALTITUDE / VERTEX |
||||||||||||
A |
|
|
B |
|
|
|
|
A |
|
|
|
|
B |
|
|
||||
(FROM COORDINATES) |
(TO COORDINATES) |
|
|
(MAXIMUM / VERTEX) (MINIMUM) |
|||||||||||||||
|
|
|
|
|
SECTION III - MISSION DATA |
|
|
|
|
|
|
|
|
||||||
20. MISSION NUMBER |
21. CALL SIGN |
22. NO. AND TYPE AIRCRAFT |
|
|
23. ORDNANCE |
||||||||||||||
24. EST / ACT TAKOFF |
25. EST TOT |
26. CONT PT / RDNVS (COORD / |
27. INITIAL CONTACT |
||||||||||||||||
|
|
|
|
|
|
|
NAVAID FIX) |
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
28. FAC/ASRT/TAC(A) CALL |
29. RESTRICTIVE FIRE / |
30. TGT DESCRIPTION |
31. TGT COORD /ELEV |
||||||||||||||||
SIGN FREQ |
|
AIR PLAN SEE 15 |
|
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
32. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ACKNOWLEDGED |
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
TUOC |
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
CRC |
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
TACP |
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
ASRT |
|||||||
Figure
(continued).
D - 4 |
|
|
MCWP |
|
|
||
|
SECTION I - MISSION REQUEST |
||
Line Title and Elements |
Explanation |
||
1 |
Unit Called |
Identifies the unit designation/call |
|
|
|
sign/preassigned number. |
|
|
This is |
Identifies the request originator by |
|
|
|
unit designation/call sign/preassigned |
|
|
|
number. |
|
|
Request Number |
For preplanned missions, indicates the |
|
|
|
originator’s request number in series. |
|
|
|
For immediate missions, this number |
|
|
|
is assigned by the ASCS/DASC. |
|
|
Sent |
Indicates the time and the individual |
|
|
|
who transmitted the request. |
|
2(Mission categories)
Preplanned: |
|
A. Precedence |
For preplanned requests, enter |
B. Priority |
precedence (block A) |
|
or priority (block B). Precedence is |
|
stated numerically in descending |
|
order of importance, as determined by |
|
the requester. Priority is expressed |
|
as shown below. |
Immediate: |
|
C. Priority |
For immediate requests, enter |
|
priority (block C). A precedence |
|
entry is not required for immediate |
|
requests because, by definition, all |
Close Air Support |
|
D - 5 |
|
|
|||
|
|
immediate requests have a precedence |
|
|
|
of 1. |
|
Line Title and Elements |
Explanation |
||
|
|
Use the numerical designation below |
|
|
|
to determine priority (e.g., define the |
|
|
|
tactical situation) for preplanned |
|
|
|
(block B) or immediate (block C): |
|
|
|
1. Emergency: Targets that |
|
|
|
require immediate action and |
|
|
|
supersede all other categories of |
|
|
|
mission priority. |
|
|
|
2. Priority: Targets that require |
|
|
|
immediate action and supersede |
|
|
|
routine targets. |
|
|
|
3. Routine: Targets of opportunity. |
|
|
|
Targets that do not demand urgency |
|
|
|
in execution. |
|
3 |
Target is/ |
Describes the type, approximate |
|
|
Number of |
size, and mobility of the target to be |
|
|
|
attacked. It is necessary to specify, |
|
|
|
even if a rough estimate, the number |
|
|
|
of targets (i.e., 10 tanks) or the size |
|
|
|
of the target area (i.e., personnel on a |
|
|
|
||
|
|
cannot accurately determine what |
|
|
|
force is |
|
|
|
type and ordnance amount/type. |
|
4 |
Target |
Locates the target by using the |
|
|
Location is |
MGRS prescribed for the area |
|
|
|
concerned. |
|
D - 6 |
|
MCWP |
|
Line Title and Elements |
Explanation |
|
|
A. Coordinates |
Locates a point target or starting |
|
|
point. |
|
B. Coordinates |
When used together with A, provides |
|
|
from ____ to ____ coordinates. |
|
C. Coordinates |
When used together with A and B, |
|
|
provides a route. |
|
D. Coordinates |
When used together with A through |
|
|
C, provides a route or describes a |
|
|
target area. |
|
E. Target Elevation |
Target elevation in feet above sea |
|
|
level. |
|
F. Sheet Number |
|
|
G. Series |
|
|
H. Chart Number |
|
|
Checked |
Indicates with whom target infor- |
|
|
mation has been |
5 |
Target Time/ |
Indicates the time/date when the |
|
Date |
airstrike is requested. |
|
A. ASAP |
As soon as possible. |
|
B. NLT |
The target is to be attacked before, |
|
|
but not later than (NLT) the time |
|
|
indicated. |
Close Air Support |
|
D - 7 |
|
Line Title and Elements |
Explanation |
|
|
C. At |
Indicates time at which target is to be |
|
|
attacked. |
|
D. To |
Denotes the end of the period of time |
|
|
in which support such as airborne |
|
|
alert or column cover is required. |
|
|
When D is used with C, B is |
|
|
unnecessary. |
6 |
Desired Ordnance/ |
Indicates the requester’s desired |
|
Results |
results. This is essential information |
|
|
for the planner and must be carefully |
|
|
considered by the requester. |
|
A. Ordnance |
Desired ordnance. |
|
B. Destroy |
|
|
C. Neutralize |
|
|
D. Harass/ |
|
|
Interdict |
|
7 |
Final Control |
Identifies the final controller (FAC, |
|
|
FAC(A), etc.) who will conduct the |
|
|
briefing and control the release of the |
|
|
ordnance. |
|
A. FAC |
Transmits the type of terminal control. |
|
B. Call Sign |
Call sign of terminal controller. |
|
C. Frequency |
Recommended TAD frequency that is |
D - 8 |
|
MCWP |
|
|
|
|
|
|
|
usable on the FEBA. |
|||
Line Title and Elements |
Explanation |
||||||||
|
D. Fix/Control Point |
Military grid coordinates and/or |
|||||||
|
|
|
|
|
|
navigation aid (NAVAID) fix of a |
|||
|
|
|
|
|
|
control point that is the furthest limit |
|||
|
|
|
|
|
|
of the attack aircraft’s route of flight |
|||
|
|
|
|
|
|
before control by the final controller. |
|||
8 |
Remarks |
Allows incorporation of briefing |
|||||||
|
|
|
|
|
|
information not included elsewhere in |
|||
|
|
|
|
|
|
the request. Enter data for the |
|||
|
|
|
|
|
|
standard CAS brief. |
|||
1. |
IP/BP |
|
|
|
|
|
|||
2. |
Heading |
|
|
MAG: Offset Left/Right |
|||||
3. |
Distance |
|
|
|
|
|
|||
4. |
Target Elevation |
|
|
|
Feet MSL |
||||
5.Target Description
6.Target Location
7. |
Mark Type |
|
Code ___________ |
8.Friendlies
9.Egress
SECTION II - COORDINATION
Line Title and Elements |
Explanation |
|
9 |
NGF |
Now known as NSFS. |
10 |
Artillery |
Artillery coordination. |
11 |
Air Intelligence Officer, |
|
|
|
other Service equivalent coordination. |
Close Air Support |
|
D - 9 |
|
Line Title and Elements |
Explanation |
|
12 |
Request |
|
|
A. Approved |
Indicates the approval or disapproval |
|
B. Disapproved |
of the request. |
13 |
By |
Indicates the individual who approved |
|
|
or disapproved the request. |
14 |
Reason for |
|
|
Disapproval |
|
15 |
Airspace |
The ACA establishes airspace that |
|
Coordination |
is reasonably safe from friendly, |
|
Plan |
|
|
A. Is Not |
The ACA provides a warning to |
|
B. Number |
aircraft of the parameters of surface- |
|
|
delivered fire in a specific area. A |
|
|
plan number or code name is issued, |
|
|
as appropriate. |
16 |
Is in Effect |
Establishes the time period that the |
|
A. From Time __ |
applicable ACA plan will be in effect. |
|
B. To Time __ |
|
17 |
Location |
Grid coordinates of the start/end |
|
A. From |
points of the ACA’s centerline. |
|
Coordinates |
|
|
B. To |
|
|
Coordinates |
|
18 |
Width (Meters) |
Defines the ACA from either side |
|
|
of the centerline. |
D - 10 |
|
MCWP |
|
Line Title and Elements |
Explanation |
|
19 |
Altitude/ |
ACA altitude given in feet above |
|
Vertex |
MSL. (Use A for Vertex only |
|
A. Maximum/ |
entry). |
|
Vertex |
|
|
B. Minimum |
|
SECTION III - MISSION DATA
Note: Mission data information transmitted to the requesting agency may be limited to those items not included in the request.
Line Title and Elements |
Explanation |
|
20 |
Mission Number |
Indicates mission number. |
21 |
Call Sign |
Call sign of mission aircraft. |
22 |
Number and Type |
|
|
Aircraft |
|
23 |
Ordnance |
Type of ordnance either by code |
|
|
number or actual nomenclature. |
24 |
EST/ACT Takeoff |
Estimated or actual time the mission |
|
|
aircraft will take off. |
25 |
EST TOT |
Estimated TOT. |
26 |
Control Point/Rendezvous |
The furthest limit of the attack |
|
(Coordinates/ |
aircraft’s route of flight before |
|
NAVAID Fix) |
control by the final controller. Same |
Document Specifics
| Fact Name | Description |
|---|---|
| Form Usage | All U.S. Armed Forces use the Joint Tactical Airstrike Request Form (DD Form 1972) to request Close Air Support (CAS). |
| Mandatory Status | The use of this form is mandatory unless a higher authority provides authorization for an alternative process. |
| Content Guidance | Instructions for the preparation of the Joint Tactical Airstrike Request can be found in the JCS Pub 12, Vol II. |
| Mission Categories | The form differentiates requests by mission category—Preplanned and Immediate, each with its precedence and priority guidelines. |
| Target Information Specificity | Requesters must describe the target with specificity, including type, approximate size, and mobility, to ensure appropriate force and ordnance allocation. |
Guide to Writing Joint Tactical Airstrike Request
Filling out a Joint Tactical Airstrike Request (JTAR) requires a detailed understanding of the mission's specifics and clarity in communication to ensure the request is processed efficiently and effectively. The form, an essential document within all branches of the U.S. Armed Forces, is designed to streamline the process of requesting close air support (CAS). Completion of the form is the initial step in a series of coordinated actions aimed at securing the requisite approval and support for mission success. Below is a stepwise guide to completing the JTAR Request Form (DD Form 1972) effectively.
- Section I - Mission Request:
- Fill in the "Unit Called" with your unit’s designation, call sign, or preassigned number.
- In the "This is Request Number" field, specify your request number. For preplanned missions, use your originator’s request number in series. Immediate missions will have the number assigned by the ASCS/DASC.
- Record the "Sent Time By" with the time and the individual who transmitted the request.
- For "Preplanned" requests, enter precedence or priority in the appropriate block:
- Precedence is stated numerically in descending order of importance.
- Priority is expressed as emergency, priority, or routine based on the tactical situation's urgency.
- For "Immediate" requests, specify the priority only in the designated block, as these requests inherently have top precedence.
- Describe the "Target is/Number of" by detailing the type, approximate size, and mobility of the target.
- Under "Target Location is Checked By", locate the target using Military Grid Reference System (MGRS) coordinates for optimal accuracy.
- Section II - Coordination:
- Input necessary coordination details, including "NGF" (Naval Gunfire), "ARTY" (Artillery), and intelligence officer or G-2/G-3 information.
- Indicate whether the request was "Approved" or "Disapproved" and, if applicable, include the reason for disapproval.
- Specify if a "Restrictive Fire Plan/Air Plan" is in effect and provide relevant details such as the plan number, effective times, location, and width in meters.
- Section III - Mission Data:
- Fill in the "Mission Number" and "Call Sign" as designated.
- Detail the "No. and Type Aircraft", the ordnance required, and the estimate/actual takeoff times.
- Provide the estimated time on target, control point/rendezvous coordinates, initial contact, FAC/ASRT/TAC(A) call sign frequency, and any restrictive fire or air plan details previously outlined.
- Clearly describe the "TGT Description" and "TGT Coord/Elev" for precise targeting and mission planning.
- Upon completion, review the entire form to ensure accuracy and completeness of the information provided.
Once the JTAR Request Form (DD Form 1972) is fully completed and reviewed for accuracy, it should be submitted through the designated channels for approval. The process following the submission includes review by the appropriate authorities, coordination with supporting units, and ultimately, the planning and execution of the airstrike mission. Each step in this process is crucial to the mission’s success, making the thorough and precise completion of the JTAR form a vital initial step.
Understanding Joint Tactical Airstrike Request
What is a Joint Tactical Airstrike Request (JTAR) form, and who uses it?
The Joint Tactical Airstrike Request (JTAR) form, designated as DD Form 1972, is an essential document employed by all U.S. Armed Forces to request Close Air Support (CAS). Its use is mandated for the coordination and execution of tactical airstrikes unless an exception is authorized by a higher authority. This form facilitates detailed communication between military units and support elements to ensure accurate and efficient airstrike deployments.When is the JTAR form required, and what are its key sections?
The JTAR form is required whenever a unit of the U.S. Armed Forces needs to request close air support. The form is structured into three main sections:- Section I - Mission Request: Collects detailed information about the mission, including the requesting unit, mission type (preplanned or immediate), target details, and desired timing and outcomes.
- Section II - Coordination: Used for the coordination details, including approvals or disapprovals, coordinating instructions, and any fire support plan details.
- Section III - Mission Data: Captures specific mission-related data like mission number, call sign, type and number of aircraft, ordnance details, and target information.
How do you determine the priority of a request on the JTAR form?
Priority on the JTAR form is determined based on the tactical situation's urgency and is divided into three categories:- Emergency: Targets requiring immediate action that supersede all other mission priorities.
- Priority: Targets needing prompt engagement, ranking above routine targets.
- Routine: Targets of opportunity not demanding urgency in execution.
Can you explain the process of specifying a target in the JTAR form?
When specifying a target on the JTAR form, it is crucial to describe the type, approximate size, and mobility of the target intended for the airstrike. The form requires the requester to provide even rough estimations, such as the number of tanks or the size of a target area (e.g., personnel spread over a 500-meter front). This specificity enables planners to accurately determine the force required, including the number and type of aircraft and the amount and type of ordnance.What is the significance of the target location section in the JTAR form?
The target location section is of paramount importance as it provides the geographical details necessary to locate and engage the target. Coordinates are typically given using the Military Grid Reference System (MGRS), ensuring precision in defining the target area for the attacking aircraft. This detailed location information is crucial for the success of the mission, minimizing the risk of collateral damage and ensuring the efficient use of military resources.How are JTAR forms approved, and what happens if a request is disapproved?
JTAR forms go through a detailed review and coordination process, outlined in Section II of the form, involving various levels of command and control. Approval signifies that the request has been evaluated and deemed necessary and feasible, considering operational priorities and resources available. If a request is disapproved, the reason for disapproval is documented, and the requesting unit may need to revise the request or explore alternative support options. This structured approach ensures that air support is deployed judiciously and in alignment with overall mission objectives.Is there any flexibility in the use of the JTAR form or is its use strictly mandatory?
While the use of the JTAR form (DD Form 1972) is mandatory for requesting Close Air Support in the U.S. Armed Forces, exceptions are possible when authorized by a higher authority. This provision ensures that the process remains adaptable to varying operational contexts and urgencies, allowing for deviations when justified by the situation on the ground. However, such exceptions are rare and are typically accompanied by strict guidelines to ensure that the objectives of the request are clearly communicated and understood by both the requesting unit and the supporting air elements.
Common mistakes
- Failing to accurately identify the unit making the request in Section I, specifically in the fields for unit called and this is request number, can lead to confusion about the origination of the request.
- Incorrectly stating the mission's precedence or priority in Section I, under preplanned or immediate categories, might result in the misallocation of resources or delayed response times.
- Omitting or inaccurately estimating the size and type of the target in Section I under target is/number of, can hinder effective planning and execution of the airstrike.
- Providing inaccurate target location coordinates in Section I, can lead to failure in engaging the target.
- Not specifying or misstating the desired timing for the airstrike under target time/date in Section I, can result in coordination failures or missed opportunities to engage the target effectively.
- Failure to properly fill out final control information, including FAC/RABFAC and call sign in Section I, can impair in-mission communication and coordination.
- Overlooking or incorrectly entering information in Section II pertaining to coordination with ground and artillery units, potentially leads to operational conflicts and safety risks.
- Neglecting to acknowledge or comply with restrictive fire plans or air plans in Sections II and III, can result in unintended engagements and conflicts with other operational directives.
- Inaccurately describing the target or providing wrong coordinates/elevation in Section III under target description and tgt coord/elev, may lead to ineffective ordinance use or collateral damage.
Documents used along the form
When military operations call for close air support, the Joint Tactical Airstrike Request (JTAR) form is a critical document, but it’s often just one of many pieces in the puzzle. To ensure a successful mission, various other forms and documents are used alongside the JTAR form. Each of these plays a unique role in the orchestration of military efforts, providing crucial information, and ensuring seamless communication among different units and command structures.
- Operation Plan (OPLAN): A comprehensive document that outlines the strategy for a series of military operations aimed at achieving strategic objectives within a theater of operations.
- Intelligence Summary (INTSUM): Provides an overview of available intelligence regarding the enemy’s position, strength, capabilities, and potential intentions, aiding in the meticulous planning of the airstrike.
- Target Nomination List (TNL): A prioritized list of targets approved for engagement, which supplements the JTAR by indicating the broader scope of strategic targets.
- Mission Briefing Sheet: Details specific instructions for pilots and ground support crews, including objectives, expected resistance, and contingency plans, ensuring all participants are fully briefed.
- Airspace Control Order (ACO): Dictates the allocation, restriction, and control of airspace to minimize the risk of friendly fire and ensure the safe coordination of all air movements.
- Fire Support Coordination Measure (FSCM): Identifies areas where ground forces are operating and outlines measures to prevent fratricide, ensuring close air support missions do not endanger friendly troops.
- Communications Plan: Lists frequencies and call signs for all units involved in the operation, facilitating efficient and secure communications across all echelons.
- Rules of Engagement (ROE): Clearly outlines the conditions under which enemy targets may be engaged, ensuring compliance with legal and ethical standards of warfare.
- After Action Report (AAR): Compiled post-mission, this document provides a debrief of the operation, detailing what was achieved versus what was planned, lessons learned, and recommendations for future operations.
Together, these documents ensure a well-rounded approach to planning and executing military operations, with the JTAR form at the heart of close air support missions. They facilitate a complex dance of coordination, communication, and compliance with operational directives and legal constraints. In essence, each document, while serving its individual purpose, contributes to the larger goal of mission success and the safe return of all service members.
Similar forms
The Joint Tactical Airstrike Request (JTAR) Form shares similarities with the Tactical Air Control Party (TACP) Airstrike Request Form, commonly used to facilitate ground-to-air communication regarding the need for air support in combat situations. Both forms serve as structured tools for requesting aerial support, highlighting specific information about the target, desired munitions, and the timing of the attack. They demand precise details such as target coordinates, type of target (e.g., armored vehicles, troop concentrations), and the desired outcome of the airstrike (e.g., destroy, neutralize). This level of detail ensures that airborne assets can effectively support ground operations and achieve the intended tactical objectives with minimal collateral damage.
Similarly, the JTAR Form has commonalities with the Naval Gunfire Support Request Form, which is used by units to request support from naval ships' artillery. Although the domains of application (air for JTAR and sea for naval gunfire) are different, both forms require detailed information about the target, including its location, description, and desired timing for the support. These forms ensure that supporting units, whether air or naval, can accurately deliver their firepower to support ground operations. By detailing specifics such as target coordinates and timing, these request forms enhance the precision and efficacy of external support in combat scenarios.
The JTAR also aligns with the Fire Support Coordination Form, a document used for planning and coordinating indirect fire support (e.g., artillery, mortars). This documentation encompasses information critical to ensuring that fires are coordinated in time and space to support the maneuver of friendly forces, avoid fratricide, and optimize the effects on the enemy. Both the JTAR and Fire Support Coordination Forms require detailed information about the target area, the nature of the target, and the desired effects, ensuring that the support provided is synchronized with the overall tactical plan and adheres to the principles of economy of force and prevention of friendly fire.
Additionally, the JTAR Form parallels the Special Operations Forces (SOF) Direct Action Mission Planning Form. While the SOF document is tailored toward the unique requirements of special operations missions, including stealth, precision, and a high degree of coordination, both forms necessitate detailed operational planning. They both focus on clearly defining the mission objectives, target details, execution timelines, and specific support requirements. This precision enables a coordinated effort that maximizes the effectiveness of the mission while minimizing risks to personnel and collateral damage.
Dos and Don'ts
When completing the Joint Tactical Airstrike Request form, accuracy and clarity are paramount. Adhering to a set of do's and don'ts can greatly enhance the effectiveness and speed of your request. Below are eight key guidelines to follow:
- Do ensure all information is accurate and up-to-date. Incorrect information can lead to mission delays or failure.
- Do use the Military Grid Reference System (MGRS) for target location to ensure precision.
- Do specify the target size, number, and type as precisely as possible, as this information is crucial for mission planning.
- Do clearly indicate if the mission is preplanned or immediate, as this affects the mission's priority and urgency.
- Don't leave any fields blank. If a section does not apply, mark it as N/A (Not Applicable) to indicate it was not overlooked.
- Don't guess or estimate critical information. If uncertain, seek clarification before completing the form.
- Don't use jargon or acronyms not commonly understood or accepted within the broader armed forces without providing a definition or explanation.
- Don't ignore the importance of the remarks section. Use it to provide additional information that can assist in the mission's success.
Remember, the Joint Tactical Airstrike Request form is a crucial tool in mission planning and execution. The precision and care taken in filling out this document can have a direct impact on the outcome of a requested airstrike. Always review the form thoroughly before submission to ensure that it meets all required guidelines and provides a comprehensive picture of the mission needs.
Misconceptions
When it comes to the nitty-gritty of military operations, few documents are as crucial yet as misunderstood as the Joint Tactical Airstrike Request (JTAR) form. Let's dispel some common misconceptions about this pivotal piece of paperwork.
- Misconception 1: The JTAR is only used by the Air Force.
Contrary to popular belief, the JTAR form isn't exclusive to the Air Force. It serves as a standardized request form across all U.S. Armed Forces branches when Close Air Support (CAS) is needed. This unified approach ensures that requests are made using a common language and format, facilitating clearer communication and quicker action regardless of the service branch.
- Misconception 2: It's optional to use the JTAR form for CAS requests.
Some might think that the JTAR form is just a formality or even optional. However, its use is mandatory unless an exception is authorized by a higher authority. This mandatory policy ensures that critical information is conveyed in a consistent manner, reducing the chance of errors in fast-moving operational environments.
- Misconception 3: The JTAR is only for preplanned missions.
While the JTAR certainly plays a crucial role in planning preplanned missions, it's also essential for immediate requests. The form accommodates both types of missions by providing specific sections to delineate the nature of the request, whether it's preplanned or requires immediate action. This flexibility is key in dynamic combat situations where the need for CAS can arise unexpectedly.
- Misconception 4: The form is complicated and difficult to use.
At first glance, the JTAR might seem overwhelming, but it's designed for clarity and efficiency. Each section of the form is carefully structured to capture vital information about the mission request, target, and desired outcome. By following the instructions and completing each relevant section, users can effectively communicate their needs to support units, simplifying the process of coordinating a tactical airstrike.
Understanding the JTAR form's purpose and proper use is key for all members of the U.S. Armed Forces involved in operations requiring air support. By clarifying these common misconceptions, we can appreciate the JTAR's role in ensuring precise, effective, and timely air support on the modern battlefield.
Key takeaways
Filling out the Joint Tactical Airstrike Request form (DD Form 1972) is a critical process that ensures the successful coordination and execution of Close Air Support (CAS) missions. Here are some key takeaways for anyone involved in this vital task:
- Universal Application: The JTAR Request Form is utilized across all branches of the U.S. Armed Forces, underscoring its importance in facilitating a standardized methodology for requesting air support.
- Mandatory Use: Employing this form is compulsory, demonstrating its pivotal role in the CAS request process, except when an exception is granted by a higher authority.
- Preparation Guidelines: For detailed instructions on how to properly fill out the form, JCS Pub 12, Vol II, is the go-to resource, ensuring requests are accurately and thoroughly documented.
- Sectioned Format: The form is organized into distinct sections, including Mission Request, Coordination, and Mission Data, guiding the requester through a systematic process of inputting requisite information.
- Priority and Precedence: It delineates between preplanned and immediate mission requests, with specific blocks to indicate the urgency and priority of the airstrike, ensuring timely responses to the most critical situations.
- Target Details: Requesters must describe the target accurately, including type, number, or area, to inform the planners of the specific requirements for aircraft type and ordnance load.
- Location Accuracy: Precise target location coordination is imperative, with the Military Grid Reference System (MGRS) preferred, to ensure effective deployment of assets and prevention of fratricide or collateral damage.
- Comprehensive Coordination: Sections II and III demand details on coordination with ground forces and restrictive fire plans, in addition to aircraft and mission specifics, emphasizing the integrated nature of air-ground operations.
- Importance of Acknowledgement: The form must be acknowledged by various levels (BDE/REGT DIVISION/OTHER), concluding its journey through the request channel and symbolizing the start of operational planning and eventual execution.
Understanding and correctly completing the Joint Tactical Airstrike Request form is crucial for the seamless integration of air power into the joint operational environment, ultimately contributing to mission success and the safety of friendly forces.
Popular PDF Documents
1040 Irs Form - Cash payments for estimated taxes can be made through specific retail partners.
IRS Schedule K-1 1041 - The IRS requires it as part of the Form 1041 filing, underscoring its importance in the tax landscape for estates and trusts.
Estimate Taxes Due - This form is crucial for determining penalties related to not making sufficient estimated tax payments.