Find a Security Clearance Job!




The purpose of the TA tab to the FA support appendix is to assign missions,
consolidate field artillery TA assets, establish target processing flow, and
assign and coordinate responsibilities not covered in unit SOPs. This
appendix explains the preparation of the TA tab and its enclosures (the
radar deployment orders).



The TA tab is a managerial tool used, when time permits, primarily by the div arty (or FA brigade) and DS battalion staffs. It is used to ensure that all TA assets are employed to support the overall maneuver operation. Although no specific format for the tab is prescribed, the five-paragraph operation order format is used when the TA tab is issued separately from the FA support plan. (See the sample tab FIGURE G-6a.) The TA tab is an integral part of the field artillery support plan, which is an appendix to the fire support annex of the operation order. This hierarchy is shown below:

  • Operation Order __________ (52d Mech Inf Div).

  • Annex __________ (Fire Support).

  • Appendix __________ (Field Artillery Support Plan).

  • Tab __________ (Target Acquisition).


In the div arty headquarters, the div arty S2 is responsible for the preparation of the TA tab. He is assisted by the div arty counterfire officer, the TAB commander, and the assistant counterfire officer (the TAB executive officer). In the FA brigade, the TA tab also is developed by the S2. In separate maneuver brigades, the TA tab is produced jointly by the FA battalion S2 and S3 with assistance from the TA platoon leader. The TA tab usually consists of the heading, five major paragraphs, and the enclosures.


The tab heading includes the security classification, the title line, the references, and the time zone used throughout. The classification is shown at the top and bottom of each page of the document.

Figure G-1a. Example

Figure G-1b. Example Continued


Situation (Paragraph 1)

This paragraph should include the friendly situation, supported units, and other TA assets in sector. Include specific enemy and friendly assessments that form a basis for threat assessments required on the radar deployment order.

Mission (Paragraph 2)

This paragraph should be a clear, concise statement of the target acquisition mission.

Execution (Paragraph 3)

The execution paragraph contains the subparagraphs described below.

Concept of the Operation. This subparagraph (3a) gives the commander's concept for target acquisition. This should include identification of designated cueing agents and general cueing guidance. Specific cueing guidance is listed below in the coordination subparagraph (3e).

Processing. The processing subparagraph (3b) is used to denote target processing flow. This targeting information flow describes the relationship between the target acquirer and the headquarters controlling the radar. This paragraph does not represent the actual communications nets used but shows the destination flow of targeting information. This paragraph should list all field artillery TA assets and headquarters controlling them. The following are examples of the types of information that may be included in the processing subparagraph:

  • AN/TPS-25A(58B) section reports targets to the div arty TOC.

  • AN/TPQ-36 section reports targets to the controlling DS battalion FDC.

  • AN/TPQ-37 section reports targets to the div arty (or FA brigade) TOC.

  • Aerial fire support observer reports targets to the controlling headquarters TOC.

  • DS battalions report targeting data to the div arty TOC.

  • Div arty TOC will exchange targeting information with the supporting FA brigade TOC (especially when it acts as the alternate div arty TOC).

The target processing flow is based on the tactical situation and command and control relationships. There are many options available for structuring the MTLR target flow. One option is that the MTLR sends targeting information to the brigade FSE. Information is then forwarded through FA communications channels to the div arty TOC. Another option is that the MTLR sends targeting Information to the DS battalion FDC. The DS battalion then relays the information to both the div arty TOC and the maneuver brigade FSE.

Visual Observation. This subparagraph (3c) includes ground and air observation. Ground observation is covered in Enclosure 1 to the TA tab, which is the consolidated visibility diagram. This diagram covers the entire division sector to include forward observers and the MTLR. Time is the critical factor in assembling this enclosure.

Air observation addresses the missions and command and control relationships assigned to the AFSOs. Types of C2 relationships assigned to the AFSOs are operational control, direct support, or general support. At each level of command, assets from the field artillery and the aviation brigade combine to form the OH-58D system. At corps level, 15 AFSOs are assigned to corps artillery HHB, and 15 aircraft and pilots are assigned to the target acquisition and reconnaissance company, command aviation battalion, corps aviation brigade. In the heavy division, six AFSOs are assigned to div arty HHB, and six aircraft and pilots are assigned to the div arty support platoon of the command aviation company, corps aviation brigade. The overall mission of the OH-58D is normally assigned by the FSE to execute the commander's intent. However, mission briefings to, and actual flight control of, the OH-58D crew are often better accomplished by the force artillery TOC because of the availability there of technical information required by the crew. Examples of employment options are shown in the table below.

Figure G-2. Examples of Employment Options

Radar. This subparagraph (3d) deals with the missions and command and control relationships assigned to the FA radars. FA radars may be attached to FA battalions or higher FA headquarters. They help perform the mission of the FA unit. Although not given the standard mission assigned to FA units, an attached radar assumes the mission of the supported unit; for example, DS or GS.

An example mission for an AN/TPQ-36 section might be as follows:

AN/TPQ-36, Section 3, Btry A, 25 FA; Mission: Attached to 1-51 FA (DS). (See RDO, Enclosure 5.)

Coordination. The coordination subparagraph (3e) covers information that is not addressed in the unit tactical standing operating procedure (TSOP). As a minimum, the paragraph should contain the following:

  • The requirement for the supported DS battalion to report its radar locations and sectors of search to the div arty targeting element.

  • Cueing guidance established by the div arty counterfire officer.

  • Common sensor boundary. Firefinder radars sharing or having overlapping search sectors need to be identified. Consideration must then be given to the establishment of a CSB. The CSB is indicated by a series of grid coordinates to define its location.

  • Coordination for communications nets and relays, if required.

  • Additional coordination for survey and security, if required.

Service Support (Paragraph 4)

This paragraph lists additional service support requirements as required. It may refer to the service support annex.

Command and Signal (Paragraph 5)

The fifth paragraph lists required information as necessary. It may refer to the fire support annex.


Enclosures to the TA tab should include the following:

  • Enclosure 1 is a consolidated visibility diagram.

  • Enclosure 2 is a consolidated capabilities overlay. It normally contains the following:

    o Major unit boundaries, FEBA, and FLOT.

    o Major search sectors to include primary and alternate sectors, zones with type and number, and radar type and section description. Primary zones are depicted by solid lines; alternate zones, by dotted lines. Section SOPs should specify color coding for individual radar data.

    o Common sensor boundary, drawn as a solid line labeled with CSB and the effective DTG.

    o Major unit locations, especially those covered by the CFZ.

    o Overlay title, classification, and register marks.

  • Enclosure 3 is the AN/TPS-25A or AN/TPS-58B RDO.

  • Enclosures 4 through 6 are the AN/TPQ-36 RDOs.

  • Enclosures 7 and 8 are the AN/TPQ-37 RDOs.

NOTE: It may not always be possible to include
all RDOs as enclosures. This is especially true
for radars attached to subordinate FA battalions.



The RDO (DA Form 5957-R) is an enclosure to the TA tab. DA Form 5957-R replaces DA Form 5364-R (Commander's Target Criteria Message). The RDO designates the information required by each radar technician to deploy his radar section and begin operations.


Direct Support Battalion S2

The DS battalion S2 is the TA manager for assets attached to the battalion. He is responsible for developing and issuing the RDO to the TA technician (MOS 131A). When developing an RDO, the S2 must coordinate with the maneuver brigade targeting officer (brigade FSE) to integrate TA assets into the overall maneuver scheme.

Division Artillery Counterfire Officer

The counterfire officer is the TA manager for the division artillery. He is responsible for developing and issuing RDOs to radar sections that are controlled by division artillery.

FA Brigade Counterfire Officer

The brigade CFO has the same responsibilities as the div arty CFO for TA assets under control of the FA brigade.

DA FORM 5957-R

The instructions for completing DA Form 5957-R are explained below.


In the first block, list the radar section number, and circle the type of radar involved.

In the second block, enter the mission (GS or attached). If the section is attached, list the unit to which it is attached; for example, 3/A/25 FA attached to 1-51 FA. Limited attachments are not listed on the RDO; for example, when the section is attached for administrative and logistic support only.

Under LOCATION, enter a primary and an alternate general position area for the section. The radar technician will select the actual site and report its location.

Search Sector

In this section, describe the search sector. For an MTLR, select primary and secondary azimuths and indicate the sector edges in mils for each. For a WLR select a primary azimuth only. Then determine the left and right sector edges. These edges are normally approximately 800 mils left and right of the primary azimuth. Range search limits can be specified, but are normally expressed as the maximum system capability. (See Chapter 4.)

EW Threat Assessment

In this section indicate the EW threat assessment. Specify whether an EW threat exists, if it is affecting friendly assets, and the type of threat (air or ground). Use the Firefinder survivability flowchart in Chapter 3 to determine emission limits.

Cueing Agents

In this section list, in priority by call sign, agents that can cue the radar. For a Q-36 that is attached, cueing agents may be a CP, a brigade FSE, a battalion FSO, a company FIST, a COLT, a reinforcing battalion TOC (if applicable), or AFSO sections. Cueing agents for an MTLR in general support might be the div arty TOC, division G2, alternate div arty TOC (FA brigade TOC), or AFSO sections.

Reporting Channels

In this section list the communications nets on which the radar is to operate. Include the call sign for each.

This section implements STANAG 2029, Edition 6, and QSTAG 514, Edition 1.

Zone Data

In this section include zone data. List the type of zone and zone number (for example CFZ1), and corner coordinates of the zones. In the description column, list the description of the activity (if any) in the zone. Also list the command priority for CFFZs when upgraded from 2. (See sample RDO below.)

Figure G-3. Sample Radar Development Order

Figure G-4. Example of Zone Rejection

The following are some rules for developing zone data:

  • Up to nine zones can be entered in the radar. All zones may be of one type or any combination of types.

  • A zone may be defined by a minimum of three and a maximum of six coordinates.

  • A radar zone cannot intersect or touch another zone.

  • No more than two zones can be along the same search azimuth, except a CFZ around the radar itself as shown in the figure at the left.

  • Grid coordinates must be listed and entered sequentially. (Coordinates should be entered clockwise.)

  • Zone coordinates cannot fall outside the sector of search (except for CFZs).

  • An azimuth should not intersect the boundary of a zone more than two times as shown in the figure below.

Figure G-5. Example of Azimuth Rejection

Figure G-6a. Sample TA Tab to FA Support Plan

Figure G-6b. Sample TA Tab to FA Support Plan (Continued)

Figure G-6c. Sample TA Tab to FA Support Plan (Continued)

Figure G-6d. Sample TA Tab to FA Support Plan (Continued)

Figure G-6e. Sample TA Tab to FA Support Plan (Continued)

Figure G-6f. Sample TA Tab to FA Support Plan (Continued)

Figure G-6g. Sample TA Tab to FA Support Support Plan (Continued)

Figure G-6h. Sample TA Tab to FA Support Plan (Continued)

Join the mailing list