Table of Contents

Chapter 3

MISSION OPERATIONS

This chapter covers both Ground Station Module (GSM) and E-8 mission operations.

The GSM can operate in a dual van configuration. Two GSMs can be linked via intershelter cables. Personnel consist of four operators and two shift leaders. Although the descriptions below describe different duties for the different positions, any GSM operator is trained to perform all GSM tasks.

NONCOMMISSIONED OFFICER IN CHARGE:

The NCOIC is responsible for the GSM operation during missions. The NCOIC may also be one of the team leaders. The NCOIC--

• Receives the daily mission and ensures the GSM is operational throughout the mission.
• Obtains and maintains SCDL Lock with the E-8, and sends RSR and SCDL freetext messages.
• Tasks and supervises the two operators, updates map, situation, and OB overlays, and performs voice communications with the E-8.
• Communicates with the user in all aspects to include reporting activity, receiving updates on the GSM mission, and receiving briefings.
• Supervises all personnel on the GSM teams; performs quality control of incoming requests and outgoing reports.
• Manages operator workload by assigning each operator specific assigned areas of responsibility (AORs) and prioritizing taskings as they are received.
• Ensures mission equipment is operational.
• Prepares site surveys.
• Directs GSM and supporting equipment setup to include placement and camouflaging; schedules preventive maintenance checks and services (PMCS), and arranges support such as security, fuel, meals, and medical support.
• Determines equipment placement.
• Performs other implied duties to include fuel, meals, security, and medical attention.

ASSISTANT TEAM LEADER:

The assistant team leader is the second ranking noncommissioned officer (NCO). He is the second shift leader. He also performs NCOIC duties when the senior NCO is absent or incapacitated.

GSM OPERATOR:

The GSM operator--

• Initializes and updates digitized graphics during a typical mission, searching and tracking targets.
• May also send and receive TACFIRE and ASAS messages and keeps a log of the mission.
• Performs PMCS and other duties as assigned by the senior operator.
• Sets up and tears down sites.
• Operates the IGSM during missions.

Before the mission starts, the GSM crew must have a minimum amount of pre-planned mission and baseline taskings to support the intelligence collection process. These taskings are given to the team leader during mission briefs. The GSM receives immediate taskings and mission changes from the G2/G3, Collection Manager, or S2/S3 (or the FSE), depending upon echelon and unit being supported.

The GSM operators work these preplanned and baseline taskings during the mission execution. Their products are the reports and imagery copies which go to their supported unit. If there are no immediate taskings received, the operators continue to work baseline taskings. If an immediate tasking is received, the GSM operators complete the baseline tasking and then start working on the immediate tasking. Once the operator completes the immediate tasking, he works baseline taskings until another immediate tasking is received.

The NCOIC must ensure no operators are over tasked or under tasked. Other mission taskings, along with intelligence preparation of the battlefield (IPB) graphics, are in the supported command's collection plan. The collection manager must provide this information 1 to 2 hours prior to the start of GSM operations. Figure 3-1 is an example of a generic mission tasking checklist. Figure 3-2 shows examples of immediate taskings.

Coordination is not limited to the collection of intelligence data; administrative data is needed for the correct configuration of the GSM. This type of data includes frequencies, codes, keying materials, callsigns, and parameters to interface with TACFIRE, UAV, SATCOM, SCDL, and ASAS as well as other communications systems. Figure 3-3 shows a mission administrative checklist. Figure 3-4 shows the tasking cycle.

Through coordination with the supporting command, the GSM NCOIC will attend the operations order (OPORD) briefing and receive the commander's intent and intelligence tasking requirements. These mission specifics are in the collection plan. Appendix A (classified) has more information on Joint STARS mission planning factors.

The GSM NCOIC creates his plan for mission and personnel management. He briefs his crew on the tasking requirements for the mission. The individual operators then update their graphics and databases during this mission preparation time. Figure 3-5 is an example of baseline tasking.

The NCOIC or shift leader is responsible for coordinating individual GSM RSR tasking requirements with the next higher echelon GSM or GSM control. This also provides the double check against the requirements flow from unit to corps G2 through Air Operations Command (AOC) or battlefield coordination element (BCE) to the aircraft; this ensures double or triple tasking does not occur.

The ACC, through the Joint Forces Air Component Commander (JFACC), controls the E-8 aircraft. The LCC designates the corps commanders or units to be supported, who in turn will determine the required coverage area, effective employment times of coverage, and radar priorities. When required, the ACC deploys with adequate aircraft to provide 24-hour coverage of the designated GRCA.

E-8 subsystems' specific parts and personnel replacements would be pushed into the theater supply and replacement system from the supporting wing to the operations squadron. Examples of support would be radome and SCDL equipment and software upgrades support. The wing would also be responsible for locating any continental United States (CONUS) parts which may be required.

These requirements are passed to the AOC through the BCE for Joint STARS mission planning and tasking, as shown in Figure 3-6. The JFACC determines the number of Joint STARS aircraft and orbits needed to provide the required coverage. In support of the JFC's guidance and campaign objectives, the JFLCC allocates the corps commanders or units to be supported and for how long.

During mission execution, the corps commanders or units being supported request changes in coverage area, times, or radar parameters; they coordinate these changes by direct communication with the E-8 mission crew.

DUAL AIRCRAFT OPERATIONS:

Individual commands may sometimes need two Joint STARS E-8 aircraft flying simultaneously to cover their mission area. This requirement would stem from terrain masking the radar, a larger than normal corps front, peculiar sector shape, or unprotected flank. Figure 3-7 shows possible flight orbits for two aircraft supporting a normal corps sized frontage in Korea.

When two aircraft are used to cover a corps area, two GSMs will also be needed. Each GSM will interface with one aircraft. The corps commander or G2 will designate which of the GSMs will interface with the second aircraft. The two GSMs should then be collocated at the Analysis and Control Element (ACE) with remote displays side-by-side in the ACE. This gives the commander the ability to view the complete imaged and overlapping areas. GSM crews will need to be in constant contact with each other so not to duplicate collection and targeting efforts.

BATTLEFIELD COORDINATION ELEMENT:

The BCE is the LCC's designated liaison within the AOC. The BCE is divided into six sections: operations, intelligence fusion, ADA and airspace, plans, airlift, and intelligence. The BCE mirrors the functions of the AOC staff in planning tomorrow's and executing today's air tasking order (ATO). This includes dynamic coordination reacting to a fluid battlefield. Each corps headquarters has liaison officers within the BCE to provide this coordination.

Below corps level, commanders will determine their required coverage area, effective times of employment, times of coverage, and radar priorities. These requirements are forwarded by supported elements through the normal collection management process. All requirements from subordinate units are consolidated at the corps G2 (in coordination with the G3 and the fire support coordinator [FSC] or fire support officer [FSO]). The G2 will then forward them to the JFACC through the BCE or AOC for inclusion in the ATO.

In a multiple corps environment, the JFLCC consolidates corps requirements and forwards them to the BCE or AOC.

Immediate changes in the Joint STARS mission (for example, coverage area, time, or radar priorities) are sent directly to the E-8 mission crew or by coordination with the BCE or AOC. Figure 3-8 shows the real-time mission coordination.

If the aircrew is unable to resolve the conflict, the BCE or AOC is the next higher authority. The aircrew will execute any request to change the GRCA that does not require an aircraft orbit change. Changes to the GRCA that require an orbit change must be approved by the AOC before the changes go into effect.

The AOC coordinates Air Force requests for a change in the radar priority or mode in the GRCA. This includes changes to the GRCA that may interfere with established corps priorities. The AOC, through the BCE, coordinates these requests with the supported corps or units before executing the change.

AIR TASKING ORDER PROCESS:

Once the JFC approves the JFACC's recommendations, the AOC tasks Joint STARS aircraft through the ATO. The ATO is the means by which the Joint STARS E-8 aircraft is normally tasked. Figure 3-9 is an example of the ATO process.

The ATO tasks the E-8 (and other Air Force aircraft sorties) to accomplish specific missions and provides sufficient detail to enable the E-8 crew to execute its mission. The ATO lists all the callsigns, radio frequencies, units to be supported, orbits, and direct attack aircraft (DAA) with preplanned targets to be updated by Joint STARS, WAS radar area of coverage, take-off time, and mission duration.

The AOC issues the ATO in sufficient time for the aircrew and supporting elements to plan their missions and covers a specific period (normally 24 hours). Preplanned Army attack aviation, unmanned aerial vehicle (UAV) flights, Army Tactical Missile System (ATACMS) firings, and airborne intelligence collectors appear in the air control order (ACO).

The ACO is transmitted along with the ATO, but it is a separate order. Information concerning orbit locations, altitudes, flight routes, station times, target locations, launch points, and gun-target lines are provided here. This information is a tool to resolve sister service battlefield efforts. The ACO also includes USMC and USN aerial efforts not covered in the ATO.

E-8 MISSION PLANNING:

The E-8 crews extract the necessary information from the ATO to plan their next mission. The Deputy Mission Crew Commander (DMCC) contacts the supported corps G2 collection manager for the commander's requirements and intent, which he briefs to the crew. The airborne intelligence officer (AIO) or airborne intelligence technician (AIT) briefs the latest intelligence update. Figure 3-10 is a sample ATO extract.

The Joint STARS produces a variety of report types and formats. These reports are considered either internal to the Joint STARS (exchanged between the E-8 and the GSM) or external (sent to other systems from the E-8 or the GSM).

INTERNAL REPORTS:

The SCDL provides the standard operating link for exchanging reports between the E-8 and the GSM. Reports over SCDL fall under freetext or RSRs. The RSRs are electronically formatted messages which request additional imagery mode (for example, SS, AP, AC, SAR, FTI).

For further details and sample messages, see Appendix A (classified). The GSM and E-8 can also exchange situation reports over secure voice UHF radios.

EXTERNAL REPORTS:

The E-8 provides electronically formatted messages to Air Force C³I nodes (ground-AOC and air-ABCCC) and DAA (F-15E) through Air Force communication networks.

The datalinks and networks provide tactical information exchanges among the Air Force C³I nodes and target updates and inflight reports between the DAA and the E-8 aircraft.

The E-8 provides secure voice communication to USAF C³I nodes and DAA using UHF, VHF, and SATCOM equipment.

The Block I series has interface with ASAS, TACFIRE, and Advanced Field Artillery Tactical Data System (AFATDS).

One of the pre-formatted electronic messages from ASAS is called the multiple assets tasking message (MATM). Another type of ASAS report is a direct tasking called request for information (RI). The TACFIRE protocol message format is called an Artillery Target Intelligence-Target Criteria Message (ATI-TCRIT). The GSM response message is a response to request for information (RRI). This message can use the ASAS RI format or the GSM freetext format.

• Artillery Target Intelligence-Coordinate Report (ATI-CDR).
• Fire mission-call for fire (FM-CFF).
• System-plain text message (SYS-PTM).

The GSM operators also have the capability to send freetext messages, such as size, activity, location, unit, time, equipment (SALUTE) reports if needed.

The IGSM and the Block I series of GSMs can also produce hardcopy products upon request. This print screen option offers time segmented color pictures of the viewed portions within the GRCA. Color prints are copied in a thermal color printer within the GSM. All hardcopy information can be hand carried to the supported command. The GSM operator will maintain a record copy within the GSM.

The IGSM and the Block I series of GSMs have UHF and VHF communications to transmit secure voice situation reports (SITREPs) to supported units including Army aviation, maneuver brigades, artillery units, and C³I nodes.

The maximum number of GSMs that can directly coordinate at one time with the aircraft is 15. The controlling headquarters and Corps G2 establish a "NET CONTROL" GSM. This does not imply that this GSM will not receive radar imagery but that as an additional duty, it ensures that the O&C console operators onboard the aircraft are not overwhelmed with RSRs from the rest of the GSM operators.

Work station operators or intelligence analysts can conduct after-action analyses from Joint STARS imagery, technical information, and graphics that are stored on magnetic tape or in the disk drive. Post mission analysis can (upon direction) be completed by both Army and Air Force analysis personnel after completing each ground or air mission. This includes but is not limited to in-depth imagery exploitation of Joint STARS radar products, GSM, and E-8 mission log analysis, after-action reviews (AARs), and lessons learned.

The GSM team conducts post mission imagery exploitation at all echelons by reviewing the previously recorded mission data. The in-depth analysis is correlated with all-source information to support future planning and targeting. This exploitation allows processed Joint STARS imagery products to be disseminated to the respective echelons (shown in parentheses below) with amplifying information not available from the raw imagery products. The database affords the analyst with the opportunity to--

• Look for infiltration and exfiltration points (for example, special operations).
• Develop battle damage assessment (BDA) and TDA.
• Follow theater ballistic missiles (TBMs) movement from known launch sites or garrison locations.
• Assist in developing enemy situational templates (G2 or S2).
• Analyze potential assembly areas, logistic areas, TOC sites (G2 or S2).
• Service historical logs (Army, USAF).
• Analyze mission logs.
• Analyze both GSM and E-8 imagery logs and SAR. This analysis contributes to BDA information. The BDA is taken from SALUTE reports, SITREPs, and in-flight reports received by the GSM and E-8 operators from supported combat units and DAA. The information from the logs can be consolidated from flight and crew debriefings. This information can be disseminated to any echelon through SITREPs as needed.
• Analyze mission logs at GSM and E-8 level. This analysis can validate existing standing operating procedures (SOPs) and contribute to developing future SOPs, crew drills, position duties and responsibilities, doctrine, and TTP.

As the Joint STARS becomes more mature, and as new IEW systems are fielded, the GSM will have an increased capability to integrate imagery and data from multiple sources in real time.

The Block I GSM is currently connected to the UAV GCS via two 300-foot cables. The Block I GSM operator can pull up UAV data or video on his console screen in the form of a smaller "window" on the larger screen. Given that the UAV is flying at the same time that the Joint STARS aircraft is flying, this additional capability is invaluable to the commander. UAV and Joint STARS flight paths complement each other. For example, Joint STARS can cue the UAV to a possible high-value target (HVT) set. Joint STARS (or UAV) can then confirm what the other sensor has detected and the HVT can then be attacked by a Multiple-Launch Rocket System (MLRS), attack helicopters, or USAF assets.

Another example of Joint STARS and UAV's complementing each other is the use of UAV imagery when Joint STARS radar is affected by terrain masking. The UAV is not affected because it can fly directly over the masked area. The collection manager could use the UAV to cover those areas the E-8 aircraft cannot see during a mission. Doing this, the commander could then literally "see" all the battlefield in NRT. Figure 3-11 shows the Joint STARS and UAV relationship.

The UAV operator feeds its video data from its GCS into the GSM. Once the GSM operator calls up a UAV window, he can quickly confirm or deny enemy presence and do limited correlation of assets using both Joint STARS and UAV data. The CGS includes an antenna to give the operator the capability to receive UAV data directly into the GSM vice going through the GCS. See Chapter 4 for information on UAV and Joint STARS cueing.

The JTT, like the UAV, is another tool that the GSM operator can use. A JTT is installed inside the GSM and is connected to the operator's console (see Appendix D).

SIGINT icons are overlayed on the operator's console screen. On the screen he sees the ellipse and possible transmitter type (for example, R-122 radio or END TRAY radar depicted on the screen for a general area). The operator then correlates this with MTI or SAR to confirm or deny additional enemy presence in that area. (The presence of an active air defense artillery [ADA] radar would bean indicator that there may be elements of an ADA unit nearby. A SAR image would confirm or deny this.) Figure 3-12 shows the Joint STARS and JTT relationship.

The GSM now can confirm or deny enemy activity first detected by another sensor, but the operator must be told to do this function via a message he would receive from an external source. This could be either a preplanned or an immediate tasking, depending on the situation. The GSM operator can use these additional tools to refine his products to better support the commander. Examples follow:

• LRSU team 6 has just spotted an enemy armored column of unknown size moving SW along HWY 3 vic BV23456718 at time 212100Z OCT 95. Joint STARS: Confirm or deny this activity and indicate current location and strength of this enemy force.
• Theater Army SIGINT sources report enemy higher headquarters (HQ) communications activity associated with surface-to-surface missiles (SSM) units. All-source analysis element's communications activity is at BT13572468, the garrison location of the 51st SSM Bale. Request Joint STARS monitor all traffic of two or more vehicles leaving the garrison location and report locations of these small groupings as they occur for the next 8 hours.
• Enemy prisoner of war report 222100Z FEB 95 states that the main CP of the 99th Armored Div is located at BU98765432. (It is now 230600Z FEB 95.) Joint STARS: Confirm or deny any enemy movement or activity located vic this area.
• With these additional capabilities, the GSM operator can integrate these assets with the E-8 radar picture at leisure, or be directed to do this via message or telephone call. Being able to do this in NRT will give the commander an even higher degree of confidence in the GSM product and allow him to target enemy forces with greater accuracy.
• For example, it is 232200Z FEB 95; GSM operator 1 with the corps tactical command post (TCP) has just received the mission to locate a suspected SSM battery located vic BJ12347890 that had just (5 minutes prior) fired an SSM at location Y. The GSM operator will then review his historical E-8 radar data; see if a UAV was flying in the vic of the SSM battery during the firing time and also check to see if the JTT can give any side lobe data from the meteorological radar--this radar is normally active where the SSM unit is present and the SSM battery is about to fire.
• Ideally, the E-8 historical radar showed 4 vehicles moving into a firing position (the data disappeared from the screen); the operator then watched the same area after the SSM was fired and saw 4 movers going SE at 20 km/h at 232207Z FEB 95 at BJ11447980. A UAV was flying in the same general area and on UAV imagery 232208Z FEB 95, 4 vehicles associated with SSM activity were noted in the same general area. The analyst at the JTT noted that an END TRAY radar was active at vic BJ12347812 at 232155Z FEB 95. The GSM operator tracked these 4 vehicles in NRT to vic BJ22335122 where they stopped at 232207Z FEB 95. He then sent a message via his TACFIRE link to the FSE for target servicing.

The Block I GSMs have SATCOM uplink capability and receive on-themove capability. All the radar data from the E-8 aircraft is transmitted to a stationary GSM and then relayed to a GSM on the move via a SATCOM link. A secondary SATCOM link for the GSM can be the TROJAN Special Purpose Integrated Remote Intelligence Terminal (SPIRIT) System. Figure 3-13 shows the GSM and SATCOM linkup.

The commander has access to all the E-8 radar coverage, even while moving, with no gaps in Joint STARS coverage. Once the GSM stops with the CP to set up, the operator can review all the recorded radar data and begin to work his missions. TROJAN SPIRIT can be used in lieu of the onboard SATCOM; however, TROJAN SPIRIT is the only SATCOM for IGSM.

The GSM is employed in a wide variety of operational settings ranging from EAC down to maneuver brigade. Because of the inherent flexibility built into the GSM, it provides tailored support to intelligence collection as well as targeting by field artillery or aviation assets and battle management at all echelons.

If there is only one GSM at any one of these levels, the GSM is considered a shared asset that provides intelligence battle management and targeting data support to the commander. If there is more than one GSM at a given level, then each can be given more specialized missions. For example, when the G2 controls the GSM, it will do more intelligence-related functions than targeting functions. If the FSE controls the GSM, it will do more targeting-related functions vice intelligence functions. FSE targeting is a coordinated effort between the FSE and G2. The GSM can be operationally employed at each echelon as follows.

ARMY THEATER:

The GSMs that support this echelon are initially assigned to the Theater Army MI brigade. The commander may place the GSM in the Joint Intelligence Center (JIC), the Theater Army ACE; a Deployable Intelligence Support Element (DISE); or the BCE (collocated with the USAF AOC).

At Theater Army, GSMs focus on situation awareness and target development. Joint STARS provides the commander an "overhead view" and an unprecedented advantage over his adversary. For tasking purposes, the J2 collection manager, in coordination with the FSE and Joint Intelligence Directorate (J2), provides baseline administrative guidance.

Once the GSM operator receives his mission priorities for the day, and the aircraft is on-station, he generates reports based on his baseline taskings. These reports can then be sent to the requestor via TACFIRE or ASAS. If the TACFIRE is not working at this echelon or links are not available, GSM reports can be sent via secure telephone (TA-312), secure FM radio, FAX, or couriered by messenger if necessary.

CORPS AND DIVISION:

Figure 3-14 is an example of Joint STARS support to DTOC or CTOC. At the Corps, the GSM will be employed in support of the ACE--

• At the corps main CP.
• With the artillery headquarters or corps main CP.
• With the tactical corps CP.
• With the aviation brigade and ACR.

CORPS TARGETING:

Targeting is the primary function when the GSM is employed in direct support (DS) of fire support nodes. The FSE specifies the fire support target numbers for use by the GSM operator. The target number block is specified in the fire support annex to the OPORD. Fire support target numbers are by standard North Atlantic Treaty Organization (NATO) STANAG 5620 and are comprised of two alpha characters and four numeric characters (for example, AZ0001 to AZ1000). Target number blocks are assigned to the GSM operator to reduce target number redundancy in the fire support system. The GSM operator assigns the target number prior to transmitting digital TACFIRE messages to the fire support center.

Target acquisition is a principal subset of targeting. The GSM can perform target acquisition in support of units from battalion through corps and EAC. Figures 3-15 and 3-16 are examples of Joint STARS GSM support to corps and division artillery CP and ACE. Typical fire support nodes where GSMs can be employed in a DS role are--

• Corps FSE.
• Corps artillery CP.
• Field artillery brigade CP.

Currently, the Joint STARS GSM interfaces with these organizations through the TACFIRE. Depending upon communications assets available and proximity to the TACFIRE shelter, operators can use combat net radio (CNR) or MSE to pass digital data between these systems. The Army Command and Control Master Plan (ACē MP) defines the architecture for the Army Tactical Command and Control System (ATCCS). The fire support control component of ATCCS is the AFATDS, replacing TACFIRE. Joint STARS GSMs are capable of interfacing with AFATDS.

Figure 3-17 shows the Joint STARS Block I GSM support to corps, division, and brigade FSE. Immediate taskings are sent to the GSM operator through TACFIRE links or FM radios. The operator disseminates his reports through the methods previously mentioned. For artillery operations by corps artillery assets, the GSM operator can use the following paths:

• Sensor to GSM.
• GSM to corps FSE via TACFIRE link or voice communications.
• Corps FSE to, for example, corps MLRS battalion fire direction center (FDC) via TACFIRE/AFATDS.
• Corps MLRS battalion FDC to MLRS battery FDC to TACFIRE/AFATDS link.

Figure 3-18 shows normal FSE channels for Joint STARS data. The corps FSE may authorize a quick fire channel between the corps GSM and firing battery to expedite an attack. Figure 3-19 shows an example of quick fire channels. Here, the flow would be--

• Sensor to GSM.
• GSM to corps artillery (MLRS) battalion FDC.
• Corps MLRS battalion FDC to battery FDC to MLRS launcher. The FSE would monitor traffic.

CORPS TACTICAL COMMAND POST:

The G2 tasks the GSM at the corps TCP. If the corps has more than one GSM in support, coordination must take place among the GSMs to ensure no over or underlap in coverage and reporting. Figure 3-20 and the vignette show how all of this coordination supports the commander.

At division, the GSM can be employed in support of the ACE at the division main CP, the aviation brigade at division, or at one of the division maneuver brigade CPs. Figure 3-24 shows the division battle. An additional GSM will support the Division Tactical Command Post (DTAC) or FSE.

The commander can keep one GSM at the division main CP and deploy one with the TCP. The IGSM must be in a fixed position approximately 15 to 30 minutes in order to set up and be prepared to receive data.

With two GSMs, the one in a fixed location can provide voice and imagery updates to the moving LGSM via tactical SATCOM secure radio on radar return highlights during the move (for example, heavy convoy movement on LOC A from 1400 to 1500Z; no significant activity noted elsewhere in sector).

The advantages of having the GSM at the TCP are threefold:

• The commander can look at the screen to see the situation as it happens.
• The commander has on-the-move situation update capability with LGSMs.
• The FSE can target, based on the situation up front, where decisions are being made.

The ACR, with respect to GSM operations, is similar to that of division. Figure 3-25 shows the ACR battle.

The S2 produces a reconnaissance and surveillance (R&S) overlay for the GSM team so that the operators can annotate these areas as graphics on their screens. The taskings, as well as the overlays, should arrive at the GSM 1 to 2 hours prior to aircraft on-station time to allow the operators enough time to enter the necessary graphics.

Joint STARS provides corps and division aviation assets with a much improved ability to anticipate events on the battlefield. It augments organic cavalry and reconnaissance assets and provides integrated updates to support the IPB process. Joint STARS improves aviation support of close, deep, and rear area operations by providing an NRT picture of enemy and friendly forces. Commanders can then use aviation assets to better mass superior combat power at the decisive time and place on the battlefield.

Joint STARS provides the ATKHB in NRT information for targeting, surveillance, and situational awareness using secure voice radios. Objectively, the GSM link to the Aviation Tactical Operations Center (AVTOC) allows Joint STARS data to be integrated with the AMPS for premission planning while helicopters are enroute. Secure voice or secure data bursts provide updates. Joint STARS supports aviation operations by providing battle management (situation and target development) and targeting information to the corps and division aviation brigade TOCs. This information can then be transmitted to subordinate battalions through the Army Battle Command Systems (ABCS).

LOS communications is limited when helicopters fly at nap-of-the-earth (NOE) altitudes. Therefore, transfer of Joint STARS information using LOS VHF and UHF radios is limited. Information may have to be retransmitted through others platforms (such as the ABCCC) based on C² support requirements.

For high priority, deep strike missions, the E-8 aircraft may provide Joint STARS support via secure radio to Army aviation assets in flight. Division and corps G3 channels must specify this relationship well in advance of the mission. A near-term communications improvement will come in the form of the NOE communications package for aviation units. This package includes increased power amplifiers (SINCGARS) and relocated antennas that provide more reliability. Additionally, the new HF radio will allow for secure voice data communications out to a minimum of 300 km.

CURRENT EMPLOYMENT:

An example of a specific Joint STARS employment in support of aviation units is discussed below. Figure 3-26 shows aviation brigade current system data flow.

Planning. The brigade S2 provides air operations instructions (AOI) to GSM operators. This AOI includes battle engagement area, ingress and egress routes, and target location and disposition. The GSM crew--

• Monitors areas for activity and provides to the S2 on-call reports based on console screen time compression and time integration analysis.
• Responds to immediate taskings for target updates as requested.

Execution Cycle. The GSM crew monitors the AOI and provides an overwatch function. As required, GSM crews-

• Provide requestor changes in target speed, time of arrival, and formations.
• Update pictures (situation awareness), new enemy targets, and the friendly situation.

The S3 sends mission or target changes directly to the GSM operator (for example, via hardcopy message, telephone call). Communications range problems can be overcome through prearranged coordination with the E-8 operator, brigade S2, signal officer, and the GSM NCOIC.

Communications Path. E-8 SCDL to GSM, GSM to AVTOC's S2/S3 on local area network (LAN) (ASAS), S2/S3 to aircraft via secure voice VHF, UHF, or HF.

FUTURE EMPLOYMENT:

An example of a possible Joint STARS employment in support of aviation units in the future is discussed below and shown in Figure 3-27. Other initiatives include transmission of imagery from attack helicopter to GSM and E-8 imagery to the Army Airspace Command and Control System (A²C²S).

Pre-Mission Planning. During this stage, GSM updates from time integration and time compression functions on the screen are fed into the Aviation Mission Planning System (AMPS) via the established coordination digital datalink to the AVTOC. AMPS planning data on board the C² helicopter goes to attack aircraft commander via data transfer module (DTM).

Execution. GSM data is sent to the C² helicopter via AMPS aviation assets using secure data bursts. Support to Army aircraft out of communications range comes through E-8 retransmission GRCS, A²C²S, or other C² media as specified in the OPORD. The A²C²S or Air Mission Commands can also retransmit digital burst updates from ATKHB direct to AVTOC or through A²C²S to update pictures (for example, BDA, OB new targets, equipment, unidentified forces).

Communications Path. Communications from GSM to ATKHBs and A²C²S are through an improved data modem (IDM). An AVTOC can also be used to retransmit communications via an IDM.

The maneuver brigade will generally employ its GSM with the analysis and control team (ACT) in the brigade TOC.

The GSM NCOIC obtains a copy of the brigade event template or R& S plan in order to create these graphics on the screen. This will assist in coordination of taskings and provide the operator a better understanding of the mission.

FSE taskings are sent to the GSM via hardwire digital or FM secure voice links established between the GSM and TACFIRE. Intelligence taskings are given to the GSM operator via telephone call or by hardcopy message. If TACFIRE links are not available, then TA-312 field telephone or couriers can be employed. Reports in response to preplanned (baseline) or immediate taskings are sent to the requestor by the means which they were received.

The brigade FSE, along with the ACT and GSM, is at the TOC. Hardware digital or FM secure voice should be established between TACFIRE and the GSM. The FSO can look at hardcopy reports or at the GSM remote display for information on enemy forces nearing or inside kill zones, engagement areas, or preplanned targets.