The Largest Security-Cleared Career Network for Defense and Intelligence Jobs - JOIN NOW

Intelligence

FM 34-43: Multiservice Procedures for Requesting Reconnaissance Information in a Joint Environment

Appendix C

ADDITIONAL RECONNAISSANCE REQUEST FORMATS

1. COMPLETION INSTRUCTIONS: AIRSUPREQ (AIR SUPPORT REQUEST)

Note: The AIRSUPREQ format is in Chapter 3 of the Joint User Handbook for Message Text Formats [JUH-MTF].

The AIRSUPREQ (Figure C-1) is used to request preplanned and immediate reconnaissance missions. The following paragraphs contain line-by-line instructions for filling out the AIRSUPREQ Message. (Refer to Figure C-1 for a visual representation of these instructions.)

a. Line 1 - EXER

Enter the exercise name and any additional exercise identifier.

b. Line 2 - OPER

Enter the operation name. Other information that can be entered here includes name of the headquarters originating the plan, the plan number, and option(s) within the operations plan.

Note: EXER and OPER can not be used in the same message.

c. Line 3 - MSGID

Enter AIRSUPREQ and the unit name of the message originator. Other information can be added such as: a message serial number, the first three letters of the month, a qualifier code and a qualifier serial number.

d. Line 4 - REF

    (1) Enter a reference to other messages or documents. You may list as many references as needed. Each reference must have--

      (a) A serial number (A for the first reference, B for the second, etc.).

      (b) A message title or reference type (enter the USMTF message short title OR one of the following codes for other types of references: CON (conference/meeting), DOC (document), LTR (letter), TEL (telephone), or MSG (formatted or nonformatted message).

Note: A free-text amplification (AMPN) or narrative (NARR) set must be used to explain the message if it is not a USMTF message).

      (c) The name of the unit that originated the reference.

      (d) The date-time group of the reference.

    (2) Other information pertaining to the reference may also be included such as the serial number of the referenced message, any special notation (NOTAL), or a filing number of the referenced document.

e. Line 5 - CANX

Use this set, if operationally required, to cancel previous message(s) and report new information. (If you wish to cancel a previous message and not report new information, use set IDENT in the MSGCHANGEREP message.) This set may be repeated as many times as necessary to indicate all previous messages canceled by this message.

    (1) MESSAGE TYPE - Identify the type of message to be canceled using one of the following methods:

      (a) USMTF message short title as listed in the Joint User Handbook chapter 3 table of contents.

      (b) Enter CON (conference/meeting), DOC (document), LTR (letter), TEL (telephone conversation), or MSG (nonformatted message) to identify the communication type to be canceled. If you use one of these codes, add a free-text set to describe further the message to be canceled.

    (2) ORIGINATOR - Enter the name of the unit or agency that originated the message being canceled.

    (3) DATE OF REFERENCE - Enter the date of the message to be canceled, using one of the following methods:

      (a) Date-time-group (two digits each for day, hour, minute, one letter for the time zone, three letters for the month, and two digits for the year).

Note: Date-time-group is the preferred method of identifying the date of the message to be canceled.

      (b) Date (two digits each for year, month, and day).

      (c) Day-time (two digits each for day, hour, minute, and one letter for time zone).

      (d) Day-month-year (two digits each for day, month, and year).

      (e) Day-alphamonth-year (two digits for the day, three letters for the month, and two digits for the year).

      (f) Verified day-time (two digits each for day, hour, minute, one letter for the time zone, and one digit for checksum).

      (g) Verified month-date-time (two digits for the day, hour, minute, one letter for time zone, one digit for checksum, and three letters for month).

      (h) Verified date-time-group (two digits each for day, hour, minute, one letter for the time zone, one digit for checksum, three letters for the month, and two digits for year.

      (i) Day-Time and month of reference (two digits each for day, hour, and minute, one letter for time zone and three letters for the month).

    (4) SERIAL NUM - This field may be used (if operationally required) to enter the identifying number of the message(s) being canceled, using one of the following methods:

      (a) Enter the message serial number (two digits each for day and month, followed by a three digit message sequence number).

      (b) Enter the document serial number.

    (5) SPECIAL NOTE - This field may be used, if operationally required, to enter special notations such as:

      (a) PASEP (passed separately).

      (b) NOTAL (not provided to all concerned).

f. Line 6 - PERID

Report the effective time period of the information in the message.

    (1) TIME FROM: - Enter two digits each for day, hour, and minute, and one letter for time zone to indicate the time at which the reporting period started.

    (2) TO: - Enter the field descriptor (TO:) followed by two digits each for day, hour, and minute, and one letter for time zone to indicate the time at which the reporting period ended.

    (3) ASOF: - Enter the field descriptor (ASOF:) followed by two digits each for day, hour, and minute and one letter for time zone to indicate the time the report was made.

g. Line 7-8 - REQUEST

This is a columnar set used to request a mission. Enter the set name, then the column headers on the next line. Start the column headers in the spaces shown. See Figure C-2.

    (1) REQNO: - Enter the request number. The column is left justified.

    (2) PR: - Enter the priority of the mission as 1 (highest), 2, 3, or 4 (lowest). If you are requesting more than one mission with the same priority, enter one letter after the priority to show the precedence, using A (highest) through Z (lowest). Left justify this column.

    (3) MSNTYP - Enter a code for the requested mission type using Entry List 107A. Left justify this column.

    (4) MSTART - Enter the mission start time, using one of the following:

      (a) Relative time. First enter C (C-Hour), H (H-Hour), or L (L-Hour). Next, enter P (plus) or a hyphen (-) for minus. Then, enter two digits each for hour and minute. Right justify the column if this option is used.

      (b) Day-time (two digits each for day, hour, minute, and one letter for time zone). Left justify the column if this option is used.

      (c) Time qualifier. Enter ASAP (as soon as possible), INDEF (indefinite), CANCEL (cancel), or UNK (unknown). Left justify the column if this option is used.

    (5) MSTOP - Do not use this field when requesting a reconnaissance mission. Enter a hyphen (-) in this column. Left justify the hyphen.

    (6) R - Do not use this field when requesting a reconnaissance mission. Enter a hyphen (-) in this column. Left justify the hyphen.

    (7) WPNTY - Do not use this field when requesting a reconnaissance mission. Enter a hyphen (-) in this column. Left justify the hyphen.

    (8) SR - This field is used, if operationally required, to ask for a certain number of sorties. Right justify this column.

    (9) ACTYP - Do not request a specific reconnaissance aircraft type under normal circumstances. However, you may use this field only if you are certain that your operational requirements dictate reconnaissance products derived from a specific reconnaissance aircraft type (e. g., U-2R). Explain the rationale for specific requests in Line 8 (AMPN). Use one of the following methods if mission requirements dictate a platform-specific request (left justify this column):

      (a) Aircraft/helicopter type/model. Use Entry List 513.

      (b) Aircraft category. Use Entry List 662.

      (c) Helicopter category. Use Entry List 662.

    (10) ALR - This field is used, if operationally required, to indicate aircraft are to be on alert. When requesting a reconnaissance mission you would put a hyphen (-) in the field. This column is left justified.

    (11) CMNT - This field is used, if operationally required, to enter additional information about the basic request or to link this line entry with line entries in other sets. This column is left justified. See Figure C-3.

Note: Sets PERID and 8 REQUEST are mandatory in all AIRSUPREQ messages. You may add any of the sets in Figure C-3 to the AIRSUPRERQ message.

h. Line 8 - AMPN

You must use this set if additional information relating to the preceding set is required. Include any extraordinary mission or threat information that has been determined so recently that it makes the information of little use if it is disseminated by normal joint/component intelligence distribution systems.

2. COMPLETION INSTRUCTIONS: AIRREQRECON (AIR REQUEST RECONNAISSANCE)

Note: The AIRREQRECON format is in Chapter 3 of the Joint User Handbook for Message Text Formats [JUH-MTF]

The AIRREQRECON is a voice-only message used to request preplanned and immediate aerial reconnaissance support missions. The following paragraphs contain line-by-line instructions for filling out the AIRREQRECON. (Refer to Figure C-1 for a visual representation of these instructions). When making specific requests, use line 21 to justify your request.

a. HEADING

    (1) Addressee and Originator: Use callsigns IAW theater mission planning documents, AFKAI, or other published callsign guidance.

    (2) Message Precedence/Security Classification: Use applicable theater guidance regarding precedence and message classification.

b. Line 1 - REQUEST

Use coded request number IAW your theater's numbering system. You can find this in operation orders, TACP Mission Planning Guides, theater planning documents, or similar documents.

c. Line 2 - PRIORITY

The distinction between PREPLANNED and IMMEDIATE depends on the ability of the request to meet the appropriate Air Tasking Order (ATO) cycle. Use PREPLANNED for requests that can "wait" for the ATO cycle, and IMMEDIATE for those you must have answered in a more timely manner. Use priority number, or number and letter, based on your commander's guidance regarding priority and precedence of reconnaissance requests. Chapter III provides further discussion on Priority.

d. Line 3 - TYPE

Select from Visual, Imagery, Electronic, and Weather.

e. Line 4 - START

This line permits you to specify a time over target (TOT). Use hard time, no earlier than (NET) or no later than (NLT) time.

f. Line 5 - LATEST

Specify the LTIOV. Chapter III provides further discussion on LTIOV.

g. Line 6 - DAYS

Sometimes, the reconnaissance information you want has already been collected to support someone else's request. This line permits you to indicate that you will accept previously-collected information (if it exists) in lieu of having a mission generated specifically to support you. Determine how dated the information can be and still be useful in accomplishing your mission. Enter the number which expresses that to collection managers. For example, if you can use data that's up to 72 hours old, enter 3.

h. Line 7 - COVERAGE

Specify the type of coverage you need. Select from PINPOINT, STRIP/LOC, ROUTE RECCE, AREA SEARCH, and AREA COVER. The term coverage refers to the way in which the sensors should be employed to get the results you are looking for. General types of coverage are--

    (1) PINPOINT: A single image, or short series of images, of a specific target or object.

    (2) STRIP/LOC: A series of overlapping images taken along a straight line or a line of communications (LOC).

    (3) ROUTE RECCE: Images of points of interest along a designated route.

    (4) AREA SEARCH: Imagery of points of interest within a designated area.

    (5) AREA COVER: A series of images of an area providing uninterrupted imagery of a contiguous area.

i. Line 8 - SENSOR

In most cases, let the reconnaissance planners select the most appropriate sensor--enter "BEST" to leave the decision to these experts. However, if you have a valid need for a specific kind of recce (IR, radar, etc.), then enter it on this line (choose from optical, IR, radar, etc.) and use Line 21 to justify specific sensor requests.

j. Line 9 - OTHER

This is where you may request the "look" you need (vertical, oblique, etc.) However, entering "BEST" gives the reconnaissance people the latitude to make the best match between your request, available platforms, threats, and conditions.

k. Line 10 - TARGET

Specify the target code/EEIs IAW the theater/joint force instructions, or the sample target list in Chapter III.

l. Line 11 - LOCTYPE

This line lets you give the recce crews and planners a broad description of the geographical area you want covered. You may choose from PINPOINT, STRIP, or AREA. PINPOINT is used when you want coverage of a single point. STRIP denotes a line between two specified points. Use AREA for box coverage with at least 3 boundaries.

m. Line 12 - LOCATION

Specify the coordinates of your target. The two most widely used means of specifying geographical coordinates are Latitude/Longitude and universal transverse mercator (UTM).

n. Line 13 - REPORTS

Choose from one or more of the following: INFLTREP, RECCEEXREP, TACREP, IPIR, SUPIR, or MISREP. Use the chart (Figure C-4) to select the report that best fits your needs:

o. Line 14 - PRODUCT

Specify the products you need, and include size and quantity. For example, one set positives indicates you want a set of photographic prints, while one set negatives means you want the original film negatives. For non-imagery products, use Line 21 to describe your requirements.

p. Line 15 - DELIVERY

Specify the organization(s), office(s), unit(s), or individual(s) who should receive the reports and/or other products--include telephone (voice/FAX) numbers where applicable.

q. Line 16 - AIRDROP

Some reconnaissance systems can airdrop imagery packages directly to you. If you need airdrop, specify the coordinates of your airdrop point on this line. Very few aircraft types can perform airdrop, and those resources for airdrop are very limited, so you must provide justification in Line 21.

r. Line 17 - CALLSIGN

If you are requesting an in-flight report (INFLTREP) or an airdrop, you specify the callsign of the organization/office/unit/individual who is to receive it on this line. Use your Signal Operating Instructions (SOIs), AFKAIs, or theater mission planning documents to find the appropriate callsign.

s. Line 18 - PRIMARY

Specify primary radio frequency for the INFLTREP or airdrop contact.

t. Line 19 - SECONDARY

Specify the secondary or backup radio frequency for the INFLTREP or airdrop contact.

u. Line 20 - POINT

If you're requesting an airdrop, specify the location of the airdrop vehicle's report-in point.

v. Line 21 - NARRATIVE

    (1) Use this line to clarify items you specified on previous lines, or to make informational statements.

    (2) This is the place to emphasize or further justify your requirements, such as why your "short-fuze" LTIOV is so important to your commander's mission objectives. If you feel strongly about some part of your request, use the narrative section to make it clear to your higher headquarters and to collection managers exactly what you want and why you want it!

    (3) This line may request very specific information regarding a particular feature of the target. Additionally, this line is often used to inform reconnaissance planners/crews of potential threats. Some examples of typical narrative statements include:

      (a) "Use south-to-north run-in to the target"

      (b) "Confirmed enemy SA-13 activity 2 miles south of target"

      (c) "Report on number of lanes being used for vehicular traffic"

w. Line 22 - TIME

Enter a date-time-group in ZULU when required to identify the message time of origin.

x. Line 23 - AUTHENTICATION

Enter the proper authentication IAW your theater's COMSEC requirements.



NEWSLETTER
Join the GlobalSecurity.org mailing list