Tactical Unmanned Aerial Vehicle (TUAV)

Tactical Unmanned Aerial Vehicle (TUAV)
http://www.fas.org/irp/program/collect/docs/TUAV-CONOPS.htm
Paid Online Employment

www.tinjauanbandingan.net Earn RM20 in Cash Today! Register And Get Paid for Your Opinions
Concept of Operations
1 of 42 4/10/13 9:28 PM
(CONOPS)
22 March 2000
Table of Contents
Executive Summary Table of Contents Section 1. Introduction 1. 2. 3. 4. 5. 6. Purpose Overview Mission Characteristics Mission Summary Scope
Section 2. Existing Shortcomings Section 3. Concept 1. System Overview 2. System Components 1. Air Vehicle (AV) 2. Modular Mission Payloads 1. Electro-optic/Infrared (EO/IR) Payload 2. Synthetic Aperture Radar/Moving Target Indicator (SAR/MTI) 3. Communication/Data Relay Payload (CRP) 3. Ground Control Station (GCS) 4. Ground Communications 3. Organization and Personnel 1. Organization 2. Personnel 4. Staff Planning Considerations 1. Deployment Requirements and Responsiveness 2. Planning for TUAV Employment 3. Basic Considerations 1. Mission 2. Multinational Coalition Considerations 3. Enemy 4. Terrain Effects on Communications 5. Terrain Effects on Payloads 6. Weather 7. Time Available 8. Request Procedures 9. Coverage Area 10. Launch and Recovery (L/R) Positioning 1. Operational Considerations
2 of 42
4/10/13 9:28 PM
2. Physical Security 11. Navigation Planning 1. Coordinate System 2. Charts 12. Threat Considerations 13. Security 1. Classification of Sensor Products 2. Foreign Disclosure and Releasability 3. Computer Security/Accreditation 4. Operations Security (OPSEC) 5. Physical Security 14. TUAV Command and Control Planning 15. Intelligence Intergration 1. Collection Management 2. RSTA 3. Priority Reporting 4. RSTA Support 5. Airspace Management Overview 1. Joint Airspace Control Measures 2. Airspace Command and Control (C2) Organizations 1. Air Force C2 2. Army Airspace Command and Control (C2) 3. Army Aviation Command and Control (A2C2) Implementation 4. A2C2 Sections 1. A2C2 and the Battlefield Coordination Element 2. A2C2 at Theater Army 3. A2C2 at Corps 1. Corps Main Command Post (CP) 2. Corps Tactical CP 3. Corps Rear CP 4. A2C2 at Division 1. Division Main CP 2. Division Tactical CP 5. A2C2 at Brigade and Battalion 5. Air Traffic Services (ATS) Deployability/Transportability Site Selection and Emplacement 1. Single Site Operations 2. Split Site Operations 1. Mission Planning and Control Section (MPCS) 2. Launch and Recovery Site (L/R) Employment Considerations Limitations Weather Frequency Management Intelligence Security Logistics and Maintenance Support 1. Operational Maintenance 2. Depot Maintenance 3. Logistics 1. Class III 2. Class IX Threat and Survivability 1. Threat to be Countered 2. Projected Threat Environment
6. 7.
8. 9. 10. 11. 12. 13.
14.
3 of 42
4/10/13 9:28 PM
15. Tasking 1. Direct Support (DS) to the Maneuver Brigade 2. General Support (GS) to the Maneuver Brigade 16. Reporting 17. Airspace Coordination Section 6. Glossary and Acronyms Section 7. References
United States Army Intelligence Center
4 of 42
4/10/13 9:28 PM
Tactical Unmanned Aerial Vehicle (TUAV) Concept of Operation 1. Introduction. 1.1 Purpose. This document contains the US Army Intelligence Center and Fort Huachuca (USAIC&FH) concept of operation (CONOPS) for employing the Tactical Unmanned Aerial Vehicle (TUAV). The CONOPS provides guidelines for planning and employment of the TUAV system. It reflects lessons learned from the various Advanced Warfighting Experiments (AWE), discussions with proponents, and most currently Alpha Company, 15th Military Intelligence (MI) Battalion deployment to Kosovo. It is a living document, as such, it will continue to be refined as it is applied and reviewed during subsequent exercises and operations. Additionally, it reflects requirements described in the TUAV Operational Requirements Document (ORD) and capabilities of the Shadow 200, the Brigade Commanders TUAV. 1.2 Overview. 1.2.1 The Tactical Unmanned Aerial Vehicle (TUAV) is the ground maneuver commanders primary day/night, Reconnaissance, Surveillance, and Target Acquisition (RSTA) system. The TUAV provides the commander with a number of benefits to include: enhanced enemy situational awareness, a target acquisition capability, battle damage assessment (BDA), and enhanced battle management capabilities (friendly situation and battlefield visualization). The combination of these benefits contributes to the commander's dominant situational awareness allowing him to maneuver to points of positional advantage with speed and precision in order to conduct decisive operations. As a command and control enabler for tactical decision making, it's the commander's "dominant eye," it allows him to shape the Army XXI battlefield to ensure mission success. 1.2.2 The mission needs statement (MNS) states, "Warfighting Commanders in Chief (CinCs) have a need to provide lower level tactical units a real-time responsive Reconnaissance, Surveillance, and Target Acquisition (RSTA), Electronic Warfare (EW), Battle Damage Assessment (BDA), and Nuclear, Biological and Chemical (NBC) detection capability against defended areas in close proximity to friendly forces." This capability is urgently needed to provide Army tactical commanders with improved situational awareness, to permit maneuver forces to move to points of positional advantage with greater speed and precision, avoiding enemy strengths, and then combine the effects of direct and indirect fires to seize and retain terrain or destroy enemy forces. Additionally, the TUAV will give maneuver commanders superior situational awareness for improved wide-area target acquisition and tracking of High Value Targets (HVT) to conduct both shaping and decisive operations with greatly increased lethality. The need is for a day/night, adverse weather, multi-sensor collection system with improved connectivity to joint forces that provides needed, real-time battle information that can not be observed from standoff airborne sensor systems, ground collection systems, and scouts. 1.2.3 This TUAV is a ground maneuver brigade commander's UAV. It allows him to "see and understand" his battlespace and gain dominant situational awareness on the Army XXI battlefield. The TUAV is the critical component of the Army XXI Brigades collection package. It gives maneuver commanders the ability to look into the battlespace where ground recon assets can not penetrate or cover in a timely manner. It can also observe heavily protected areas where commanders are hesitant to commit manned aerial platforms. Lastly, it gives commanders a dedicated, rapidly-taskable asset with the capability to look wide as well as deep into their battlespace. It allows them to "see critical elements of the battlespace" and support the increased demand for immediate situational awareness on the Army XXI battlefield. The TUAV is a critical tool to obtain the hard to get information needed to satisfy the commanders Priority Intelligence Requirements (PIR) and Commanders Critical Information Requirements (CCIR). It's a command and control enabler for tactical decision making. 1.2.4 The TUAV system will provide flexible, responsive RSTA, Battle Damage Assessment (BDA), and battle management support to ground maneuver commanders at brigades, armored cavalry regiments (ACR), light and heavy divisions. The TUAV is dynamically retaskable in flight to ensure it is responsive to the commanders immediate needs/changing CCIR. To optimize its capabilities, TUAV is fully integrated with and cued by relevant Intelligence Preparation of the Battlefield (IPB) and other collection systems
5 of 42
4/10/13 9:28 PM
such as Joint Surveillance Target Attack Radar System (JSTARS), Guardrail Common Sensor (GRCS), Artillery Counter Mortar/Battery Radars and FAAD C2, in a synchronized effort to support the Warfighter. As demonstrated during the Force XXI AWEs, the information is fed directly to the brigade commander (as well as the S3 and Fire Support Coordinator [FSCOORD]); but in the meantime, the information is fused to answer CCIRs. Regardless of the UAV's role, the operations officer must ensure the UAV is synchronized with all of the other assets within the battlespace. 1.2.5 This is a ground maneuver brigade commanders tactical UAV. The TUAV priority is to support the maneuvering of the brigade and battalions, including fire support of maneuver. The TUAV is simple (threshold capability-- no bells and whistles), inexpensive, easy to maintain; profiled to meet the brigade commanders needs. It is required to keep pace on the Army XXI battlefield. Launch and recovery must be from an area easily accessible to the commander. Rapid set up and tear down times will ensure it keeps pace with the brigade's movement. To facilitate rapid movement, the control of the UAV may be passed to other control stations or launch/recovery stations to allow continuous flight operations to meet the commander's requirements. Due to the signature associated with the launch and recovery (L/R) of the TUAV, the L/R area will normally not be collocated with the brigade tactical operations center (TOC). However, the mission planning, tasking, and dissemination will occur through the TOC via a collocated ground control station (GCS) or, at a minimum a remote video terminal (RVT) with compatible communications for tasking and dissemination. Additionally, the commander can locate up to four RVTs throughout the brigade. As an example, he may choose to keep one with him, locate one each with a forward battalion, scouts, and the direct support artillery battalion. Additionally, future operations demand "information on the move". As such, the TUAV is a key collection asset that supports the near real time visualization of the battlespace and is focused on the commander's decisive operations. 1.2.6 The brigade commander requires sufficient coverage to fight on his and the battalion commanders piece of ground. Specifically, the TUAV is used to cover the dead space in front of the ground reconnaissance -- it extends the ground reconnaissance capability. It complements the ability to collect ground-level recon targets with a wider-area overhead look. As such, it helps eliminate the unknown and allows the commander to anticipate and respond to pre-empt. In terms of IPB, the TUAV helps the commander during the planning, preparation, and execution phases. 1.2.6.1 Planning. During the planning phase the commander needs to understand the ground, and answer the following questions: Where can I move? What are the avenues? Where are the obstacles? The UAV allows the commander to see and assess environmental benefits and limitations and answer those questions. In turn, those factors will support the development of friendly considerations, and formulation of enemy Courses of Action (COAs) for the planning staff. The UAV allows the commander to quickly assess critical components of his battlespace, such as trafficability, suitability for logistical and fire support assets, and activities of civilians on the battlefield during the planning process. Without this asset, the commander will have to commit slower moving, precious ground maneuver assets to answer these planning questions, or seek/task other assets for the intelligence. 1.2.6.2 Preparation. During preparation, the commander validates his templates by Battlefield Operating Systems (BOS) he recons, in accordance with the plan, verifies the templates, and determines where the enemy is and is not. Additionally, the commander can redirect/frag his air recon (UAV) to a different mission and area. He cannot always do this with ground recon once in, if they are fixed and attempt to move, they may die. Additionally, the commander needs to determine where he can take risk; where he can economize on forces. Instead of using troops on the flanks, the UAV can assist by providing surveillance in those areas. The UAV greatly enhances the effectiveness of the commanders counter-recon effort during the preparation phase. The UAVs mobility and range allow him to economize limited ground recon assets for the execution phase, without sacrificing his ability to detect indications of unexpected enemy spoiling actions such as Raids, Reconnaissance in Force, Fire Support Raids, etc. 1.2.6.3 Execution. During execution, the UAV helps determine maneuver options/friendly courses of action. As an example, it helps answer the question, "Is that truly an assailable (or unassailable) flank?" Another example: As the brigade penetrates the enemy defense, the commander may want the UAV over the enemy reserves, to determine when and where they are moving. The brigade commander may use a UAV capability to simultaneously look deep into his battlespace while his ground recon assets and
6 of 42
4/10/13 9:28 PM
maneuver units observe closer named areas of interest (NAIs). With this confidence that he can receive critical information during the fight"just-in-time intelligence"the commander can take prudent risk without fear that he will outrun his collection assets. 1.2.6.4 The brigade commanders TUAV needs to be dedicated for the close battle. It needs to be responsive to the current situation. The commander needs the information when it happens not maybe; not later; not reprioritized by a higher command. The brigade commander's TUAV needs to be focused for decisive operations in the brigade battlespace. 1.3 Mission Characteristics. The TUAV system is most effective when it is tasked to observe known targets, NAIs/target areas of interest (TAIs) or to confirm cueing from another intelligence asset. The strength of the system is in its ability to provide a long dwell "staring" capability and to provide near real time (NRT) video and imagery to a wide variety of users. The TUAV is less effective when tasked to conduct missions that would require wide area search over extended periods of time. The advantages of TUAVs low airspeed is the capability to dwell for extended periods of time in the immediate vicinity of a target, the ability to accompany and escort land convoys, and the ability to avoid engagement by certain surface to air missile (SAM) threats. The drawback to the low airspeed is the long transit time required to reach target areas. Due to the slow airspeed of the UAV, consideration should be given to sequentially planning targets along a logical flight profile. Examples of pre-planned surveillance missions include observation of road and rail networks, possible missile launch sites, troop assembly areas, and troop movements. The TUAV can also monitor choke points, corridors, road intersections, airfields, and similar sites. The important point to remember when tasking the system for a particular target is to provide as much information about the target and the information requirements concerning that target as possible. This allows the mission payload operator to scan the area with a specific purpose in mind vice just taking "best guess" snapshots and hoping that the analysts can determine what was sought. The TUAV system may also perform as a target acquisition platform that can acquire targets, confirm that targets are still in place, assist in fire direction, and provide immediate feedback of results to shooters. In this mode, the NRT video must be continually monitored and the video observer should have direct contact with the shooter. The Advanced Field Artillery Tactical Data System (AFATDS) is an example of one of these sensor to shooter links. During the weapons delivery phase, the TUAV can move to a loiter area or use altitude separation to deconflict with strike aircraft or other weapons systems. If the TUAV is unable to remain in the target area observing the target during the strike, it can return to the target area and provide NRT video of the battle damage at the conclusion of the strike. The TUAV can also support search and rescue missions and can assist in tactical recovery of aircraft and personnel missions. The tasking authority should be aware that the extended loiter time of the air vehicle, if detected, may cause the enemy to focus attention on the very area where the missing personnel are hiding or evading. The TUAV offers the rescue mission commander the opportunity to conduct route reconnaissance immediately prior to the ingress of recovery forces. 4. Mission. The mission of the TUAV is to support their commanders RSTA plan providing the commander a capability to gather NRT intelligence data in support of missions throughout the range of military operations. The TUAV unit conducts day and night operations to supported units. Missions include but are not limited to: Surveillance of NAIs and TAIs. Support to route, area, and zone reconnaissance. Support to IPB. Support to situation development. Support to target acquisition.
7 of 42
4/10/13 9:28 PM
Support to indirect fire weapons, close air support (CAS), and close-in fire support (CIFS). Support to rear area security. Supports to combat search and rescue. Support to BDA. TUAVs are especially valuable in environments where immediate information feedback is needed and manned aircraft are unavailable or excessive risk or other conditions render the use of manned aircraft less than prudent. With planned future growth, specified TUAVs will also perform missions such as electronic warfare (EW), communications relay, chemical detection, and mine and weather surveillance. 1.5 Summary. The TUAV is the brigade commander's most versatile confirming sensor -- his "dominant eye" -- and responds directly to his requirements. To optimize its capabilities and responsiveness to the commander, it is linked to/cued by sound IPB and wide area sensors, such as the direct feed to the JSTARS Common Ground Station (CGS) when collocated with the GCS, and as an objective, direct live feed from the UAV to the CGS. Additionally, it must be interoperable with command, control, communications, computers, intelligence, surveillance and reconnaissance (C4ISR) systems and linked into the Armys Battle Command System, in particular All-Source Analysis System (ASAS), AFATDS, and Forward Area Air Defense System (FAADS) for distribution via intelligence channels, targeting, and to meet air defense identification requirements. Due to the complexities of airspace management (ASM), even at the brigade, it needs to feed into the A2C2 system. Some of those areas are defined more precisely below. 1.6 Scope. This CONOPS describes TUAV components and capabilities provided by the TUAV system. Section 2. Existing Shortcomings. Present manned systems cannot perform critical situational awareness missions in a timely, responsive or safe manner in a hostile integrated air defense environment without high risk to personnel and costly systems. Current UAV systems possess neither the required capabilities nor the required mobility, deployability, and small footprint to meet the needs of U.S. Army commanders. While national intelligence collection systems can contribute to satisfying significant warfighting needs, serious deficiencies exist in providing continuous, responsive, timely, and detailed, information and targeting support to Army tactical commander's combat operations on an Army XXI battlefield.
8 of 42
4/10/13 9:28 PM
TUAV equipment and personnel. 3.0 Concept. 3.1 System Overview. A TUAV system consists of four basic components: the GCS and related equipment; Air Vehicles (AV); Modular Mission Payloads (MMP); and communications. The system will have a minimum of two GCSs, two Ground Data Terminals (GDTs), one Portable Ground Control Station (PGCS) and one Portable Ground Data Terminal (PGDT) with line of sight (LOS) command and control links to, and receipt of telemetry and imagery from, the AV. Additionally, it will have four Remote Video Terminals (RVTs) to provide payload information in the area of operations. The systems four RVTs that receive NRT video/telemetry from the AV can be used by: the brigade in the TOC (if a GCS is not collocated), the brigades subordinate maneuver battalions, or by direct support artillery or supporting aviation assets. The commander, will allocate RVTs, based on the mission, enemy, troops, terrain and weather, time available and civil considerations (METT-TC), to support his scheme of maneuver. The system is designed to be easy to launch, operate, recover, and maintain with a minimum of training, logistics, and personnel. It must present a small profile in order to reduce its signature; rapidly tear down, deploy and set up; and minimize any impact on brigade combat service support (CSS) resources. The system will be capable of NRT transmission of EO/IR imagery. Initially, the system will have a basic EO/IR mission payload, but will have a capability for growth to accommodate additional MMPs. The system will have sufficient AVs to support a wartime surge operational tempo (OPTEMPO) described below, as well as a means of launch and recovery, and the necessary transportation and ground support equipment for the operations and maintenance of the system. A crew of approximately 22 will operate and maintain a full baseline (AVs and two GCSs) at the OPTEMPO indicated below; this includes augmentation by the Brigade Maintenance Contact Team (BMCT) from the divisional Mobile Maintenance Facility (MMF) to sustain operations. The TUAV baseline is capable of 12 hours of continuous operations on station within a 24-hour period. The system has the capability of surge operations for 18 hours within a 24-hour period for no more than three consecutive days, with the following day being limited to eight hours of operations. Although the system has the capability to surge for 18 hours of 24 hours for 72 hours, the TUAV baseline and its
9 of 42
4/10/13 9:28 PM
parent brigade may be reconstituted after 36 hours. The threshold system will carry enough supplies and spares for initial operations. The complete TUAV system will fits into three High Mobility Multipurpose Wheeled Vehicles (HMMWVs) with shelters (two GCSs and one Air Vehicle Transport [AVT]) and includes an Air Vehicle Launcher Trailer. A Cargo/Troop carrying HMMWV with trailer is included for personnel and their equipment (rifles, helmets, camouflage netting, individual protective equipment, etc.) and enough Class I (subsistence) and Class III (Petroleum, Oils, and Lubricants) and Class IX (repair parts) supplies for initial operations. A second Cargo/Troop carrying HMMWV with trailer is provided by the BMCT to support unit personnel and equipment transport. A threshold requirement is for a system configurable to deliver 72 hours of operational capability at a minimum of 12 flight hours on station in a 24 hour period deployable in a single C-130. Sustainment beyond the initial 72 hours is supported by the BMCT. The complete baseline TUAV system is transportable in no more than two C-130 sorties. The follow-on of the BMCT from the divisional mobile maintenance facility to support sustained operations requires an additional C-130. 3.2 System Components 3.2.1 Air Vehicle. The air vehicle is a mid-wing monoplane with a twin boom empennage supporting an inverted-V tail, constructed of composite materials and powered by a rotary engine. The TUAV system has an endurance of four hours on station at 50 kms. It is operated from a soccer field size area with clear line-of-sight between the air vehicle and the ground data terminal/portable ground data terminal. The AV was not specifically designed to meet low signature requirements, but due to its small size and composite materials it does have reduced signature characteristics. The aircraft is not visually detectable from ranges exceeding 4,000 ft and is not audible from ranges exceeding 2,000 ft. It can operate during less than ideal weather conditions (operates in environments similar to a small light aircraft) with a range of 50 kms from the launch and recovery site, flying at altitudes of 14,000 feet Mean Sea Level (MSL) or greater. Nominal operating altitudes/survivable altitudes are from 8,000 to 10,000 feet Above Ground Level (AGL) for day operations and between 6,000 to 8,000 feet AGL for night operations. The AV is capable of flight into moderate rain conditions. Adverse weather conditions, such as heavy icing or precipitation, or high surface winds, may prevent launches or operations in some areas. General aircraft characteristics include:
Characteristics
TUAV
Altitude: Maximum (km,ft) Operating (km,ft)
4.6km 15,000ft 1.8 3.7km 6,000 12,000 ft
Endurance (Max): (hrs)
5 hrs
Radius of Action: (km,nm)
50 km 31 nm
Speed: Maximum (km/hr,kts) Cruise (km/hr,kts) Loiter (km/hr,kts)
227.8 km/hr 123 kts 120 130 km/hr 65 70 kts 120 130 km/hr 65 70 kts
Climb Rate (Max): (m/min,fpm)
366 m/min 1200 fpm
10 of 42
4/10/13 9:28 PM
Propulsion: Engine Prop
One rotary One pusher
Avionics: Transponder Navigation
Mode IIIC, IV (IFF) GPS
Launch & Recovery Launch Recovery
Rail Launched (soccer field size) Arrested Recovery (soccer field size)
Guidance & Control
Remote Control/Preprogrammed/Autonomous
Fuselage: Length (m/ft) Width (m/ft)
3.4 m 11 ft m ft
Wingspan: (m/ft)
3.9 m 2.8 ft
Weight: Max (kg/lbs) Payload (kg/lbs)
147.6 kg 328 lbs 27.3 kg 60 lbs
Fuel: Type Capacity (kg/lbs)
MOGAS 23.1 kg 50.7 lbs
TUAV Characteristics 3.2.2 Modular Mission Payloads (MMPs). The TUAV MMPs will be modular in design. The baseline sensor is the EO/IR payload. The second priority payload will be SAR/MTI, followed by the Communications/Data Relay payload. 3.2.2.1 Electro-optic/Infrared (EO/IR) Payload. The EO/IR payload will be a multi-mode, FLIR/Line Scanner/TV sensor with resolution sufficient to detect and recognize an Armored Personnel Carrier sized target from operational altitudes (ie. >8000ft AGL day and >6000ft AGL night) and at survivable standoff ranges (3-5km) from imaged target. Imagery will be pre-processed on board the TUAV and passed to the GCS via the system data link. The payload will be capable of autonomous preplanned operation and also be capable of instantaneous retasking throughout a mission. The EO/IR payload will provide continuous zoom capabilities when in EO mode and multiple Fields of View (FOV) when in IR, selectable by the mission payload operator (MPO). The sensor will have a Staring Mode, a Strip Mode, a Spotlight Mode, and be able to slew 360 degrees on command from the MPO. 3.2.2.2 Synthetic Aperture Radar/Moving Target Indicator (SAR/MTI). The TUAV Radar payload will be a multi-mode SAR/MTI. This payload will provide increased situational awareness by providing high-resolution imagery, sufficient to detect and recognize armored personnel carrier (APC) sized target, during periods of adverse weather or through battlefield obscurants from survivable operational altitudes and standoff range. The MTI capability will provide superior situational awareness by serving as an adjunct to JSTARS, detecting and recognizing vehicles moving into the tactical commanders area of operation (AO), and serving as an immediate cure to threat activity that can then be confirmed with the on board EO/IR or SAR sensors.
11 of 42
4/10/13 9:28 PM
3.2.2.3 Communications/Data Relay Payload. The TUAV Communications/Data Relay payload will be a multi-purpose beyond line of sight relay. This payload will provide very high frequency/ultra high frequency (VHF/UHF) beyond line of sight relay for battlefield communications (to include helicopter operations) and remote sensor data. This payload will support Army XXI extended range operations with a communications on the move capability. While functioning on board the TUAV, this payload will provide beyond line of sight relay for Single Channel Ground and Airborne Radio System (SINCGARS) and Enhanced Position Location Reporting System (EPLRS) radios as well as remote sensors. The remote sensor relay can be either through the Communications/Data Relay payload, or, objectively, through the Tactical Common Data Link (TCDL). This payload will be capable of autonomous preplanned operations or being dynamically reprogrammed during a mission. 3.2.3 Ground Control Station (GCS). The GCS has two primary functions. First, it is the primary means used to control, track, and operate the AV. Second, it is used to manipulate the payload and receive and process telemetry and video downlinks. The GCS also incorporates mission-planning functions with the ability to call for and adjust indirect fire. There are two GCSs per baseline; each in a HMMWV mounted C2 shelter. The GCS has two operator positions, an air vehicle operator (AVO) position and a MPO position. It contains the following consoles: The left console that is normally the AVO position. The right console that is normally the mission payload operator position. Both operator positions are identical in capabilities. Functions can be transferred to either in the event of an operator position failure. A GCS can only communicate with and control one AV at a time. The GCS can also place a mission AV in programmed flight and be free to acquire another AV during a handoff from or to the L/R site. The GCS controls the AV by data link through the GDT to distances up to 50 km (31 miles) as long as line of sight is maintained between the GDT and the AV. 3.2.4 Ground Communications. The GCS, gives ready interface to the existing secure command, control, communications, computers, and intelligence (C4I) architecture, to include CGS, AFATDS, ASAS, FAADS, and A2C2. Intelligence reports from the GCSs include secure voice, electronic dissemination and/or video via the various communication systems in the GCS. Secure communications and intelligence dissemination are provided via the standard DoD tactical (VHF and UHF) radios, Mobile Subscriber Equipment (MSE), and the Tactical Local Area Network (TACLAN). Ground components use Service standard tactical communications equipment and procedures. TUAV communications must interface with selected standard DoD C4I systems, architectures, and protocols. All communications will be interoperable with National Security Agency approved encryption systems. All real time video exported to other imagery systems shall be in compliance with the Department of Defense/Intelligence Community/United States Imagery and Geospatial System (DoD/IC/USIGS) approved Video Imagery Standards Profile (VISP). The system shall have UHF communications (capable of secure operations during wartime) with Air Traffic Control (ATC) agencies (peacetime) and airborne warning and control (AWACS) and airborne battlefield command and control center (ABCCC) aircraft (wartime/exercises). The system will have the capability of relaying the UHF communications from through the AV. The tactical communications system provides integrated communication to TUAV tactical users for mission support and communication between shelters. Radio communications between shelter operators, external system users, and support units is performed via SINCGARS radios. The Single Unit Transceiver radios (SUT) are used for external voice communications on the flight line. The SUT is a hand held radio with an antenna and battery pack for portable use. Telephones are used for communication between the TUAV Control Shelters, Mobile Maintenance
12 of 42
4/10/13 9:28 PM
Facility, and system users. A tactical telephone, capable of handling digital data and voice communication, is part of the TUAV system. Digital data is translated to standard formats to be used by shelter consoles. There are two telephone networks: MSE for telephone (voice/data) communication and one fiber optic net (ethernet) for intra shelter voice/data communication. The GCS radio equipment and communication devices are depicted below.
13 of 42
4/10/13 9:28 PM
TUAV GCS Communications Equipment. 3. Organization and Personnel 3.3.1 Organization. The TUAV will be found in the direct support (DS) and general support (GS) companies of the MI battalion within the heavy, light, airborne, and air assault divisions and MI companies in armored cavalry regiments. The DS company will have three baseline systems while the GS company will have one.
MI Bn Organizational Chart (HVY/LT/ABN/AASLT DIV)
14 of 42
4/10/13 9:28 PM
3.3.2 Personnel. The TUAV platoon consists of 17 personnel.
TUAV Organizational Chart
15 of 42
4/10/13 9:28 PM
TUAV Maintenance Organizational Chart 3.4 Staff Planning Considerations. Basic considerations regarding the potential, operational, and tactical missions of TUAVs facilitate planning the employment of TUAVs. Important considerations for planning the deployment of TUAVs to the operational area are detailed in order to optimize the TUAV capabilities and manage low-density/high demand systems. 3.4.1 Deployment Requirements and Responsiveness. TUAVs are organic capabilities, and decisions to deploy will normally be based on operational requirements. Typical airlift requirements to move UAVs vary by type unit, mission configuration, required operational capabilities, and supported unit/host-nation support (HNS) expected. For example, to obtain a limited operational TUAV capability requires, at a minimum, one C-130, while full self-sustaining operational capability requires three C-130s. 3.4.2 Planning for TUAV Employment. TUAVs are a limited asset that will be in high demand, because commanders at all levels want to exploit the capabilities they bring to the fight. TUAVs can support operations throughout the area of responsibility (AOR)/joint operations area (JOA). TUAVs provide the tactical commander with responsive support focused on his area of interest/influence. They are significant force multipliers when used in close support to ground operations, providing target acquisition, adjusting of supporting arms and BDA. TUAVs, in concert with other RSTA assets, increase commanders situational awareness throughout the battlespace. The figure below lists some planning considerations. PLANNING CONSIDERATIONS
DESIRED CAPABILITIES Area to be covered Products desired/timeliness Period of coverage
BASING CONSIDERATIONS Adequate runway Operating area within the range of UAV Launch and Recovery Site
16 of 42
4/10/13 9:28 PM
Information security and classified information storage
STRATEGIC TRANSPORT Airlift Varies by aircraft, desired capability sustainability and cost Sealift
COMMUNICATIONS (Connectivity) C2 of UAV Appropriate frequencies/bandwidths available for up/down links Data Dissemination How will collected information be disseminated?
POLITICAL CONSIDERATIONS Will host nation allow UAV ops? Impact of UAV mishap on relations
AIRSPACE COORDINATION How will UAV be integrated into the operational airspace, air-tasking order? Do International Civil Airspace Organization rules restrict UAV employment?
WEATHER CONSIDERATIONS Weather during period of ops suitable to UAV ops Impact on sensor employment
3. Basic Considerations. 3.4.3.1 Mission. In planning TUAV missions, the TUAV unit commander/operators must conduct a thorough mission analysis that addresses the supported commanders mission requirements. The TUAV unit, based on the commanders requirements, coordinates mission planning. When appropriately tasked, TUAV units are capable of providing support to the commander during day and night operations on land, in the air, or at sea. 3.4.3.2 Multinational Coalition Considerations. United States (US) forces often find themselves operating as part of a coalition. In such a situation, considerations must be made for TUAV operations. In addition to the established principles of airspace management used in manned flight operations. TUAV flight operations will likely require special airspace planning considerations to operate in civil airspace. Planning should ensure US and allied/coalition TUAV missions are not redundant and include actions to deconflict and synchronize. Allied/coalition partners requests for TUAV imagery must be reviewed with respect to security, prioritization, and political sensitivities. 3.4.3.3 Enemy. Planners consider the enemys disposition, composition, order of battle, capabilities, and likely courses of action. From this information, planners anticipate the enemys ability to impact the TUAV mission. Primary planning considerations are the enemys capability to conduct counterair warfare and attack TUAV mission control capabilities. The presence of counterair aircraft, surface-to-air missiles, and air defense artillery can impact TUAV operations. Electronic warfare, specifically electronic attack, can significantly impact the communications links which provide air vehicle/sensor control and sensor downlink. Planners must also consider protection from attacks against launch and recovery sites (L/R) by electronic means, air-to-surface fire, indirect fire, or special operating forces (SOF). Additionally, the enemy capability should be evaluated in terms of meaconing, jamming, and interception of the TUAV uplink and downlink. Potential or confirmed presence of chemical or biological contamination in the TUAV flight path must also be considered to avoid contamination of the L/R by a contaminated returning TUAV. As the threat level increases, pre-briefing of operators and detailed mission planning are critical. If the
17 of 42
4/10/13 9:28 PM
threat situation changes during the course of the mission, effective communications and close coordination between the operators, control agencies, and the supported force are crucial. In-flight updates on enemy activity and disposition along the flight route and in the target area may require TUAV operators to adjust the flight profile to counter the threat. 3.4.3.4 Terrain Effects on Communications. Surface sites communicating with TUAVs require LOS to the AV. Sites where LOS communications may be masked by terrain features can significantly degrade or limit operations. 3.4.3.5 Terrain Effects on Payload. Restrictive terrain (e.g., dense vegetation, urban areas) in the objective area can shield targets from TUAV payloads. Steep terrain requires TUAVs to fly closer and at higher angles to the target, as opposed to operating from a standoff position and at lower angles. 3.4.3.6 Weather. Weather affects launch and recovery operations and payload effectiveness. During launch and recovery, TUAVs are subject to the same weather limitations as other aircraft. Due to TUAV susceptibility to crosswinds during launch and recovery, predominant speed wind directions must be considered when selecting L/R locations. TUAVs are more susceptible to icing conditions and visible moisture (rain, snow, and fog) than manned aircraft. Weather conditions in the objective area may affect both the flight characteristics of the TUAV and the effectiveness of the payload. Additionally, high en route winds may significantly effect TUAV mission duration and retasking flexibility of the relatively slow TUAV. 3.4.3.7 Time Available. Time is the critical element in synchronizing TUAV missions with supported operations to enhance overall mission success. Planners estimate the amount of time necessary to plan, coordinate, and execute the mission. The time required to launch the TUAV from tasking is approximately one hour. This includes planning, launch preparations, and preflight. Inadequate planning time will result in reduced effectiveness. Satellite bandwidth and data link availability is a critical element to synchronization of TUAV missions into the overall ISR structure. Because of low airspeed, TUAVs lose a large percentage of operating time when they are re-tasked in-flight to a distant target area. 3.4.3.8 Request Procedures. Request procedures for TUAV support from operational units, are included in the normal air request or collection management procedures. Normal requests for TUAV support will use the United States message text format (USMTF) for air support request (AIRSUPREQ) and air request reconnaissance (AIRREQRECON). 3.4.3.9 Coverage Area. Current TUAV sensor payloads are limited to electro-optical (EO) and infrared (IR) cameras. Depending on the individual system utilized, the area covered by sensors will have certain limitations. TUAV sensors have a relatively narrow angle of coverage. Sensor capabilities are based upon a variety of factors including altitude, field of view, and standoff range. 10. L/R Positioning 3.4.3.10.1 Operational Considerations. TUAVs have a distinct operational radius based on a variety of factors including; fuel, LOS considerations, communications, airspeed, and payload. Forward positioning the L/R enhances the employment of TUAVs by reducing the impact of these factors. Positioning TUAV units to support a particular operation must take this into account. In addition, planners must consider the individual launch/recovery needs of a system when planning TUAV deployments. Because TUAVs require special equipment to land, as well as crews trained in recovery and service needs, safe recovery is only assured at sites possessing the requisite launch/recovery equipment and trained personnel. For the reasons listed above, the operating range of a TUAV becomes an issue during the progress of a modern high tempo battle. 3.4.3.10.2 Physical Security. Because TUAV units do not have sufficient organic
18 of 42
4/10/13 9:28 PM
personnel and equipment to provide their own physical security when operating from austere or autonomous locations, they will require security forces from the supported unit. 11. Navigation Planning 3.4.3.11.1 Coordinate System. Several coordinate systems are in use around the world and even within the US. The use of multiple map datums has led to various kinds of inaccuracies during combat operations. If there is any doubt as to which datum is being used, TUAV support requesters should specify the datum in the request. 3.4.3.11.2 Charts. TUAV units require charts and other flight planning materials similar to manned aircraft. These charts should be the most up-to-date ones available so that no unexpected obstacles such as power cables or radio towers pose a threat to safe TUAV operations. Both hardcopy and digital geospatial support (i.e., softcopy and electronic connectivity) should be considered for navigation requirements. 3.4.3.12 Threat Considerations. TUAVs operate within the threat profiles of many air defense systems (enemy aircraft, surface-to-air missiles, man portable air defense, antiaircraft artillery). Additionally, TUAV units may be targeted for attack by air, indirect fire, or SOF. Planning considerations must include assessment of current threat systems. Aerial intelligence is collected through one of two mission profiles: standoff from the target area outside of any threat envelope or penetration of a threat area (which may or may not involve over-flight). TUAVs can over fly hostile territory, particularly when the threat is low. Although TUAVs may be utilized for high priority missions that are too high-risk for manned aircraft, they are attributable but not "expendable." 3.4.3.13 Security. TUAVs are designed to provide high quality imagery. Although the imagery may appear to be unclassified, the sources, methods, and content may require classification. Regulation 50-2 pertains to the classification guidance for inclusion of other sources and methods with the TUAV imagery. Access to the ground segment and the communication and dissemination links will comply with DoD 5200.1-R and be determined by the geographic combatant commander or the designated representative. 3.4.3.13.1 Classification of Sensor Products. The geographic combatant commander or the designated representative retains the authority to classify the TUAV imagery of a particular mission, type of mission, area of coverage, or the specific collection/intelligence requirements for which the platform is tasked. It is the commanders responsibility (within the constraints of appropriate DoD procedures and guidance) to determine the releasability and priority of releasability to potential recipients of TUAV imagery. 3.4.3.13.2 Foreign Disclosure and Releasability. Classified material/ information may not be released to foreign nationals, immigrant aliens, foreign governments/companies, or international organizations, without specific approval, in advance, by the geographic combatant command, commander in chief (CINC). Approval for access will not be granted unless authorized under the provisions of the National Disclosure Policy and references contained in DoD 5200.1-R. 3.4.3.13.3 Computer Security/Accreditation. National and theater security policy and guidance determine the sensors product classification. 3.4.3.13.4 Operations Security (OPSEC). An OPSEC plan must be developed to establish protection measures for the systems and performance data during all phases of the process. The plan will apply to personnel, operations, activities, and facilities wherever data are recorded, generated, analyzed, received, or handled. The principal objective of this plan is to anticipate and eliminate OPSEC vulnerabilities. Other objectives include raising the level of OPSEC awareness, establishing the process for fulfilling OPSEC requirements, and collecting information for the analysis of required countermeasures. 3.4.3.13.5 Physical Security. As a minimum, TUAVs will be protected according to the requirements contained in DoD 5200.8-R, "Physical Security Program." These systems will comply with physical protection requirements listed in the security classification guides of components, parts, materials,
19 of 42
4/10/13 9:28 PM
individual systems, subsystems, or subcomponents. If a TUAV crashes outside of DoD property, during peacetime operational or training events, the military installation or organization closest to the UAV recovery site will be notified and directed to dispatch sufficient personnel to maintain custody of the airframe or wreckage, and the crash site, until relieved by TUAV unit personnel. If a TUAV crashes in hostile or denied territory, the commander will conduct a risk assessment to determine if a wreckage recovery operation will be launched. 3.4.3.14 TUAV Command and Control Planning. The commander must integrate and synchronize all assigned and available RSTA and C4I systems with the mission cycle, including launch platforms and weapons. This includes the capability to fuse and correlate both the operations and output of the RSTA/C4I utilizing sensors, information processing,), and communications capabilities, systems, and functions for a more consistent and clearer picture of the battlespace. Airborne reconnaissance supports each element of the air, land, sea, space, and special operations team to facilitate the application of overwhelming force. The airborne reconnaissance challenge is to provide the commander intelligence that is timely, objective, responsive, complete, accurate, and relevant. The primary mission of TUAV units is to support the tactical commanders as a tactical RSTA system, providing the commander a capability to gather NRT data on opposing force position, composition, and state of readiness. Preplanned missions will be on the air tasking order (ATO). 15. Intelligence Integration 3.4.3.15.1 Collection Management. The collection management process details the integration of TUAVs with ISR resources. ISR planning involves the collection, processing, validation, and prioritization of ISR collection requirements. ISR tasking includes matching collection requirements with collection resources and collection dissemination paths. Centralized ISR planning and tasking optimizes the application of force-wide manned and unmanned ISR resources, lessens the likelihood of unnecessary duplication of effort, and ensures designated echelons of the force receive ISR products in a timely fashion. TUAVs are key resources that can support the full range of operational and tactical ISR requirements. Therefore, planning for the employment of TUAV capabilities to meet force-wide ISR requirements is best accomplished as an integral part of the collection management process. All TUAV preplanned missions, even those tasked by Service or functional components, will be incorporated into the ATO process. 3.4.3.15.2 RSTA. RSTA support for joint operations is related to the TUAV intelligence collection function. RSTA provides information on enemy forces and installations. RSTA operations may require both continuous surveillance and reconnaissance to provide timely indications and warning of an imminent or impending threat attack. RSTA assets assist in monitoring or verifying compliance with international agreements. RSTA provides commanders with current data on enemy terrain, organization, infrastructure, and forces necessary for planning theater campaigns and major operations, to include contingencies. It also provides for adaptive, real-time planning for current operations, including monitoring enemy centers of gravity, conventional attack capabilities, enemy offensive and defensive positions, deception postures, and BDA. 3.4.3.15.3 Priority Reporting. Collection and RSTA functions impact the targeting cycle of joint force operations. To meet the challenge of mobile targets and rapidly changing enemy orders of battle, the systems long dwell capability, as well as its NRT down link and its smaller radar signature, significantly enhance the forces targeting capability. For rapid indication, warning, and retargeting efforts, raw imagery or initial data will be pushed to the appropriate tactical commander as soon as it comes into the GCS. The collection manager will request that the operations section issue rapid turnaround guidance to the TUAV unit conducting this type of mission. 3.4.3.15.4 RSTA Support. After collection of the target is accomplished, data recovery and dissemination will flow from the GCS or directly from the TUAV to a remote video terminal. If the operation tempo and PIR dictate, the S-2 will determine if, and at what level of effort, forward-deployed exploitation is required. Common sense will dictate at what level voice reports are generated. For example, if a high-value or time-sensitive target is found, a voice report to the TUAV liaison officer (an experienced individual from a TUAV unit) will be made. If a robust communications architecture is available, additional intelligence collection nodes may have access to this information in NRT. This allows the unit assigned tasking
20 of 42
4/10/13 9:28 PM
authority immediate access to re-task the platform in NRT, avoiding the slow down of an exploitation phase. The video may be transmitted real-time via the Trojan Spirit to a Global Broadcast System (GBS) injection site. Exploited images will be disseminated via the supported intelligence dissemination architecture. 3.4.3.16 Communications Integration and Interoperability. The primary mission of TUAVs is to provide organic, dedicated RSTA support to their assigned commands. Initially, this support will primarily be in day/night, near all weather imagery missions. The TUAV GCS will process imagery information. The TUAV system does not have organic capability to transmit imagery from the GCS. Single video frames may be attached to electronic mail and transmitted via the SECRET Internet Protocol Router Network (SIPRNET). Information from the imagery is provided to the supported command by tactical communications. Videotapes of missions are provided to Service intelligence agencies for analysis. The information is disseminated in digital message format and freeze frame imagery (national imagery transmission format [NITF]) to the theater intelligence system via each Service All-Source Analysis System (ASAS) (for example, Army ASAS, US Air Force [USAF] contingency airborne reconnaissance system [CARS]/Combat Intelligence System, United States Navy [USN] joint maritime command information system, and United States Marine Corp [USMC] intelligence analysis system. Users with TUAV remote video terminals may directly receive real-time imagery from the TUAV. The TUAV must transmit in the omni-directional mode and the user must be with 50 kilometers of the AV. Combat information for immediate target acquisition and targeting can be directly passed to Service fire support elements through Service tactical communications.
3.5 Airspace Management Overview. TUAV utilization of airspace is still in its infancy. Therefore, it is necessary to not only cover airspace requesting channels in each chapter, but also to provide an overview of the "big picture". TUAV operations will be integrated into the airspace management system in as transparent a way as possible. The established principles of airspace management used in manned flight operations will normally apply to TUAV operations. The difference between TUAVs and manned aircraft is there is not a pilot on board, so "see and avoid" and "visual flight rules" do not apply. The TUAV is difficult to acquire and does not provide a clear radar signature, presenting a potential hazard to high performance aircraft. Therefore, TUAV operations should be coordinated with all appropriate airspace control agencies to provide safe separation of TUAVs and manned aircraft and prevent engagement by friendly forces. Preplanned TUAV missions will be reflected in the Airspace Control Order (ACO), ATO, and the Special Instructions (SPINS). UNMANNED AERIAL VEHICLE (UAV) AIRSPACE CONTROL CONSIDERATIONS TUAVs are launched from TUAV launch and recovery sites, which may be either airfields or unimproved tactical field locations. TUAV operations should be addressed in the air control plan and air control order and adhere to the procedures established by the air control authority. As appropriate, TUAV missions should be included in the air tasking order and special instructions. Because a TUAV mission can occur as preplanned or immediate, this information must be disseminated through the airspace control system in a timely manner. Airspace management includes coordinating, integrating, and regulating airspace to increase effectiveness throughout the range of military operations. Airspace management prevents mutual interference from all users of the airspace, facilitates air defense identification, and accommodates the flow of all air traffic safely, with minimum restraint placed on friendly airspace users. 3.5.1 Joint Airspace Control Measures. The methods of airspace control vary throughout the range of military operations from war to military operations other than war (MOOTW) and include both combat and
21 of 42
4/10/13 9:28 PM
non-combat activities. The methods range from positive control of all air assets in an airspace control area to procedural control of all such assets, with any effective combination of positive and procedural control measures between the two extremes. Airspace control plans and systems need to accommodate these methods based on component, joint, and national capabilities and requirements. Full positive control would rely on radars, other sensors, identification, friend or foe (IFF)/selective identification feature (SIF), digital data links, and other elements of the air defense network command, control, communications and computers (C4) system to positively identify, track, and direct air assets. Full procedural control would rely on previously agreed to and promulgated air space control measures such as comprehensive air defense identification procedures and rules of engagement, low-level transit routes (LLTR), minimum-risk routes (MRR), minimum-risk levels, aircraft identification maneuvers, fire support coordination measures, and coordinating altitudes. In any case, all missions remain subject to the ACO. For TUAV operations, procedural control measures are used to facilitate the launch and recovery site, flight routes, and tasked mission areas. Restricted operating zones (ROZs), UAV flight routes and transit altitudes, and UAV blanket altitudes are the primary procedures used. Brief descriptions of how these measures help facilitate TUAV operations are discussed below. Since the majority of missions will be above the coordinating altitude, the coordinating altitude will be discussed for background knowledge only. It is important to note that the most flexible and responsive procedural deconfliction measure for TUAV operations is the UAV blanket altitude. 3.5.2 Airspace Command and Control (C2) Organizations. Success on the battlefield depends on how effectively the airspace over the battlefield is used. A high density of friendly weapon systems with overlapping flight profiles and operating envelopes contributes to maximum combat effectiveness without user conflicts. Airspace management maximizes force effectiveness without inhibiting either the ground effort or the airspace users supporting it. The following organizations and procedures define the methods used to accomplish the airspace control function, ensure unity, and standardize the airspace control effort. They must be sufficiently flexible and responsive to accommodate the rapid changes to planned and ongoing operations. 3.5.2.1 Air Force C2. For joint operations, the Air Force Component Commander (AFCC) is normally designated the Joint Forces Air Component Commander (JFACC). Because of the integrated relationship between airspace control measures and air defense operations, the Area Air Defense Commander (AADC) and the Airspace Control Authority (ACA) duties normally should be preformed by the same person, who may also be the JFACC. He executes his responsibilities in accordance with the objectives of the Joint Forces Land Component Commander (JFLCC). As the ACA, he fulfills his responsibilities through the integrated airspace control system. This system is structured around the theater air control system (TACS) and Army air ground systems (AAGSs). Subject to the authority and approval of the Joint Forces Commander (JFC), the ACA develops procedures for airspace control and coordination within the assigned airspace control area. The ACA develops the air control plan (ACP) and, once approved by the JFC, publishes it to all users. The ACP is implemented through a cyclic ACO. The ACO provides details of the approved request for airspace control measures and is published as Part 10 of the ATO. Based on policy in the ACP, Army commanders submit their requests for airspace control measures through the operational chain shown in the figure below. The Air Force C2 structure is designed to integrate with Army C2 to provide timely support to operations. Within this structure, personnel, organizations, and facilities are required to maintain airspace management. This overview only focuses on joint operations where the Air Combat Command (ACC) is designated as the JFACC.
22 of 42
4/10/13 9:28 PM
Army airspace request channels. 3.5.2.2 Army Airspace Command and Control (A2C2). The A2C2 organization, shown in the figure below, is composed of staff elements at each command echelon from maneuver battalion through theater Army. It includes air defense artillery (ADA) elements, fire support coordination (FSCOORD) elements, Army air traffic service (ATS) facilities, and airspace control liaison personnel. The A2C2 element is located within the command post (CP) established at each tactical echelon. Only theater, corps, and division have dedicated A2C2 elements to accomplish A2C2 tasks. Brigades and battalions must establish an A2C2 element with their organic personnel and the tactical air control party (TACP).
23 of 42
4/10/13 9:28 PM
Army A2C2 system.
3.5.3 A2C2 Implementation. Establishing most airspace control measures requires the approval of the ACA. Army commanders inform the ACA of their requirements through the operational chain. The use of USMTF facilitates and standardizes the process of requesting the establishment of airspace control measures. Airspace request formats outline the necessary information required to include location, lateral and vertical limits, and time frame during which the measure to be enforced. The actual TUAV airspace deconfliction and coordination begins with the asset manager. He identifies the operating area to be covered by the TUAV and passes this information to the A2C2 element. With the mission area and launch and recovery site identified the A2C2 element requests the appropriate control measures. The TUAV commander will be involved with this process to ensure mission specific needs are met. Once control measures have been approved, the mission is tasked. If a mission has been tasked and a UAV blanket has not been established, airspace requirements can still be met. It will require intense coordination between the A2C2 element and appropriate airspace control agencies such as the air support operations center (ASOC), the airspace control center (ACC), and the direct air support center (DASC). The A2C2 element supports the TUAV operation, accomplishes deconfliction procedures, and forwards and updates TUAV status to the ACC and the control and reporting center (CRC). All aircraft working within the sector check with the ACC upon entry and are advised of the status of TUAV protocols. The ACC and CRC are responsible for relaying this information to the Airborne Battlefield Command and Control Center (ABCCC), and the Airborne Warning and Control System (AWACS), notifying them of the "Hot and Cold" status of UAV operating areas. The following planning considerations are helpful in designing A2C2 measures:
24 of 42
4/10/13 9:28 PM
Maximize control through use of airspace control measures. These measures reserve the airspace and control the actions of specific airspace users. Exercise positive control through means such as identification, friend or foe (IFF), and identify and locate airspace users. In addition, continuous communications must be maintained with airspace users. Ensure the scheme of maneuver and commanders intent determine and govern the design of the control measures. Establish controls that provide maximum freedom consistent with the degree of risk acceptable to the commander, and that airspace users and ground based weapons crews can recognize. Ensure temporary airspace control measures are within the AO and that of the requesting echelon.
3.5.4 A2C2 Sections. All A2C2 elements form a vertical and horizontal channel through which airspace control requirements coordinate, synchronize, and disseminate operation plans (OPLANs) and operation orders (OPORDs), shown in the Army airspace request channels figure. Primary tasks of the A2C2 elements include: Developing and coordinating airspace control standing operating procedures (SOPs), OPLANs, and annexes. Coordinating and integrating airspace user requirements within the AO. Coordinating with other services and adjacent units on integrating airspace use within the AO. Identifying and resolving airspace user conflicts. Approving, staffing, and forwarding requests for special airspace use to the next higher headquarters (HQ). Maintaining A2C2 information displays and maps.
3.5.4.1 A2C2 and the Battlefield Coordination Element. The battlefield coordination element (BCE) integrates the Armys airspace requirements into the ACO and keeps the ACA informed on Army related airspace activities. When the ACO becomes effective, the CRC becomes the primary facility responsible for its execution. Deconfliction at this point is normally handled by the CRC with assistance from the A2C2 element. 3.5.4.2 A2C2 at Theater Army. The theater Army A2C2 organization supports operational planning, conducts current operations, and performs specified functions for the theater Army CP. The A2C2 elements are the focal point for all airspace control activities related to theater Army rear and deep operations as well as planning for future operations. The A2C2 element works for the G3, but is normally supervised by the G3 Air. 3.5.4.3 A2C2 at Corps. The Corps A2C2 organization supports future operational planning, conducts current operations, and performs specified functions for the Corps Main, Tactical, and Rear CPs. 3.5.4.3.1 Corps Main CP. The Corps Main CP collocates with the fire support element (FSE). It is the focal point for all airspace control activities related to corps rear area operations, deep operations, and for
25 of 42
4/10/13 9:28 PM
planning future operations. The A2C2 element works for the G3, but is normally supervised by the G3 Air. The Main CP A2C2 element consists of, but is not limited to, the ADA element; aviation element; air liaison officer (ALO); fire support element (FSE); the air traffic services (ATS) unit assigned to the corps; corps analysis and control element (ACE), as required; the G4 section, as required; and the air and naval gunfire liaison company (ANGLICO). Personnel from these elements and sections perform two separate tasks. First, they perform their primary staff functions. Second, they assist in synchronizing airspace requirements of their parent units with airspace users of the combined arms team and supporting services. 3.5.4.3.2 Corps Tactical CP. The Corps Tactical CP performs airspace management activities and supports close operations with the A2C2 element at the Main CP. The A2C2 elements at both Tactical and Main CPs maintain close coordination to ensure that airspace requirements generated by changes to the tactical situation are met in a timely and effective manner. The Corps A2C2 element representatives at the Tactical CP consist of a fire support officer (FSO); aviation officer or noncommissioned officer (NCO); ADA officer or NCO; and an ALO. The FSO or aviation officer will serve as the element chief. 3.5.4.3.3 Corps Rear CP. The Corps Rear CP airspace duties are handled at the Main CP by the A2C2 element.
3.5.4.4 A2C2 at Division. The division A2C2 organization within the Divisions Main and Tactical CPs is similar to those at Corps. The divisions primary focus is on the conduct of battles and engagements in the forward portion of the combat zone (division rear boundary and forward). Therefore, airspace control tasks are required to synchronize all airspace users of the combined arms team and supporting services with the close battle. The difference in geographical orientation (forward versus rear) results in minor differences in the airspace control procedures employed and the degree of coordination required. 3.5.4.4.1 Division Main CP. The Division Main CP includes the G3 Air; ADA element; aviation element; ATS liaison element, as required; FSE; division G2 section; G4 section, as required; ALO; and ANGLICO. 3.5.4.4.2 Division Tactical CP. The Division Tactical CP includes a G3 officer as chief, assisted by an FSO; G2 representative; aviation representative; ADA representative; and a fighter liaison officer (FLO).
3.5.4.5 A2C2 at Brigade and Battalion. As there is no formalized A2C2 element at brigade or battalion, the staffs performs A2C2 by extracting information from various sources. The Brigade or Battalion commander may form a brigade A2C2 element from the ADA Liaison Officer (LO), the FSO, the ALO, and the Army aviation LO when available. When the Army aviation LO is not present, the S3 Air assumes his duties. There may or may not be a TUAV LO present. 3.5.5 Air Traffic Services. The ATS focuses on the Armys participation to synchronize airspace use and coordinate with joint agencies, when required. Within each corps, an ATS Battalion consists of flight operation centers (FOCs); representatives at each A2C2 element; and teams maintaining navigational aids (NAVAIDS) and providing terminal control at Army airfields. 3.6 Deployability/Transportability. The TUAV system baseline will be deployable in two C-130 sorties. The BMCT from the division mobile maintenance facility, equipped with a HMMWV and trailer is required for sustained operations and requires an additional C-130. A CH-47 or CH-53 can lift separate TUAV components. The system is required to be configured for air, rail, or marine transport in two hours or less. 3.7 Site Selection and Emplacement. While many variations are possible, the normal configurations for TUAV emplacement are single site operations, and split site operations. METT-TC and deployment resources will determine the emplacement strategy to use. A typical TUAV battlefield deployment configuration is shown below and reflects the deployment of the TUAV platoon with their BMCT. In order to reach this stage of operations, the TUAV and BMCT can deploy in phase, with each phase providing
26 of 42
4/10/13 9:28 PM
additional capabilities single site operations, split site operations, and split site operations with a L/R site jump capability.
Typical TUAV Battlefield configuration. 3.7.1 Single Site Operations. In single site operations, the TUAV platoon or team with elements of the BMCT is collocated near the maneuver brigade TOC. Normally, only the mission planning and control site (MPCS) is collocated with the TOC, due to the greater electronic and physical signature of the L/R site. Single site operations, normal during initial entry operations and are configured to deploy in one C-130. The initial entry team of the TUAV platoon is emplaced near the airport of debarkation (APOD), consisting of a Ground Control Station, Air Vehicle Transport, and AV Launcher, and enough personnel from the platoon and BMCT to provide 12 hours of coverage in a 24-hour period.
27 of 42
4/10/13 9:28 PM
TUAV Initial Entry Team. 3.7.2 Split Site Operations. In split site operations, the TUAV platoon is split into two distinct sites: the MPCS, and the L/R site. To enable the TUAV platoon to provide split site operations a second C-130 is required to transport additional personnel and equipment, see below. NOTE: During split site operations, redundancy of operations is sacrificed and the platoon may require transportation support for personnel.
28 of 42
4/10/13 9:28 PM
TUAV Split Site Operations Requirements. 3.7.2.1 Mission planning and control section (MPCS). The mission planning and control section consists of one of the GCSs, and personnel and supporting equipment. It is normally collocated with the supported unit (brigade or separate battalion). The GCS receives the taskings, plans missions, takes control of the airborne TUAV for the actual conduct of the mission, and reports the information. 3.7.2.2 L/R site. The L/R site consists of the AVs, the GCS, PGCS, maintenance equipment, ground support equipment (GSE) and supporting personnel. After L/R site personnel receive their flight schedule and mission plan from the MPCS, they prepare and preflight the AV for the mission, launch, hand-off to and receive it from the MPCS, and recover it as scheduled. Site requirements depend on many factors such as METT-TC, logistics support, the environment, and equipment. When selecting the L/R site, the following must be considered: LOS between ground terminals and the UAVs. Distance from the target. Sufficient clearance to conduct operations. Areas with high population densities and an excess of high power lines should be avoided when possible. The L/R site should be close enough to the forward element to effectively communicate, hand off, and receive control of the UAVs. Site selection should incorporate OPSEC considerations to reduce the possibility of detection and destruction by enemy forces. The TUAV platoon can sustain operations upon arrival of third C-130. The arrival of third C-130 provides the TUAV platoon with organic transportation and the ability to jump the L/R site, see below.
Sustained Operations Requirements.
29 of 42
4/10/13 9:28 PM
3.8 Employment Considerations. The TUAV with its 4+ hours of dwell time is excellent for point surveillance of a single target such as an airfield or monitoring a geographic area such as a choke point. Due to the relatively narrow field of view of the optical systems and the low altitude at which the AV often flies, the system is more effective when cued against targets than when operating in a wide area search mode. However, if visual reconnaissance of a limited-width corridor is desired, continuous observation of NRT video can provide this capability. The AV could be used for route reconnaissance missions or to observe zones of separation that are a few kilometers in width. It is not suitable, however, for observation of hundreds of point targets within such a zone. As previously mentioned, because of relatively low flight altitudes and a limited field of view for the sensors, the TUAV is not optimized to be a wide-area reconnaissance system. The ability to track mobile targets with the TUAV provides the commander with a new capability. However, there is a danger that this valuable resource can be tied up tracking a decoy vehicle. Exclusive use or heavy dependence upon TUAV NRT video imagery provides the enemy a relatively cheap means of deception, which can tie up the system against targets of little or no value. To some extent, this can be countered by employing the TUAV as part of an integrated reconnaissance and surveillance plan. 3.9 Limitations. TUAVs are capable of locating and identifying major enemy forces, moving vehicles, weapon systems that are firing, and other targets which contrast with their surroundings in extreme environments. Conversely, it is difficult to locate enemy forces, which blend in with their surroundings. The TUAV is not well-suited to wide area searches, rather, its capabilities are enhanced when it is employed as part of an overall collection plan, and cued by other intelligence systems in a synchronized effort to support the warfighters needs. 3.10 Weather. Weather is crucial for planning and executing a mission. It can operate during less than ideal weather conditions (operates in environments similar to a small light aircraft) flying at altitudes of 14,000 feet MSL or greater. The capability to launch and recover in cross-winds from 0 to 20 knots and operate in moderate precipitation conditions (up to 2" per hour). Heavy rains can cause electrical abnormalities and winds can hinder total time on target as well as hamper recovery operations. Deicing capabilities are not part of any of the Army UAV systems. High-density altitudes can also adversely effect the endurance and payload capacity. 3.11 Frequency Management. In todays electronic age, frequency conflicts may impair operations. Therefore, it is essential for planners to identify their frequency needs and deconflict their requirements during the planning phase. The TUAV system will initial use UHF datalinks for communications between the GCS and the AV. 3.12 Intelligence Security. The TUAV was specifically designed to provide UNCLASSIFIED, releasable, high quality imagery. However, its source and methods, in addition to its content, may have to be classified at a higher level as determined by the S2/G2. The sensor technologies and capabilities are also UNCLASSIFIED. 3.13 Logistics and Maintenance Support. The TUAV equipment will be supported in accordance with the IEW Sustainment Streamlining (IEWSS) System, to include Contractor Logistics Support (CLS). The TUAV maintenance concept may be Life Cycle Contractor Logistics Support. The system will be maintained IAW Aviation Unit Maintenance (AVUM) "on system repair" and Aviation Intermediate Maintenance (AVIM) "off system repair" Concept. Routine maintenance will be provided by system operators and the assigned maintenance personnel augmented (as required) by the divisional MMF BMCTs. Higher-level maintenance will be accomplished at the Forward Repair Activity (FRA) and/or the Electronic Service Support Center (ESSC) within theater to allow for quick turn around of critical system components. Maintenance support is planned around two levels, operational maintenance and depot maintenance. 3.13.1 Operational maintenance. Operational maintenance is performed on-site and includes AV assembly and disassembly, preflight and postflight checkouts and inspections, minor structural repairs and servicing, and troubleshooting and repair (primarily line replaceable unit [LRU] removal and replacement). Built in test (BIT) procedures support fault location and diagnostics to the LRU level and objective card level. Once the fault has been located, the faulty item will be evacuated to depot.
30 of 42
4/10/13 9:28 PM
3.13.2 Depot maintenance. Depot maintenance is used for major airframe components, propulsion systems, MMPs, control and autopilot systems, GCS, and datalink and communications suite repair to component level. Depot will also provide software maintenance. It is important to note that TUAV units require nonstandard combat service support (CSS) needs to maintain operations. Unlike many other organizations on the battlefield, when the TUAV system is deployed, it requires CSS from forward units regardless of the C2 relationships that exist. TUAV units have the same responsibilities as other units to request and obtain supplies and logistics. Because of their uniqueness, they go about it in slightly different ways. The following breakdown of unique requirements by class of supply: Class III. For TUAVs this is a complicated class of supply. Most TUAV engines currently use MOGAS. One fueler will draw diesel from the MI battalion whenever possible, or from the forward support battalion (FSB). Another fueler or vehicle with trailer-mounted pod must plan to draw MOGAS from the MI battalion, potentially requiring long hours of driving when the UAV Platoon is dispersed. Class IX. All system peculiar repair parts are delivered to the MI element by MI contact repair teams. When deployed away from the MI battalion, the supported unit or FSB provides common items. The figure below depicts the normal resupply flow.
Resupply Flow. 14. Threat and Survivability. 3.14.1 Threat To Be Countered. The TUAV system will be used to counter the general threat to its supported unit by providing real-time combat information/intelligence. 3.14.2 Projected Threat Environment. The TUAV system will operate in close proximity to heavily defended areas. It will be subject to hostile air defenses that may include the full range of antiaircraft systems including conventional small arms, automatic antiaircraft weapons, Man Portable Air Defenses (MANPADs), and crew-served systems using radar, optics, and electro-optics for detection, tracking, and
31 of 42
4/10/13 9:28 PM
engagement. The threat will also include shoulder-fired SAMs, launcher mounted SAMs, air-to-air weapons launched by fixed wing aircraft, helicopters, and counter-UAV UAVs, anti-radiation missiles, and directed energy weapons. Airborne and ground components will be susceptible to the same threat as the unit they support. Airborne and ground computers, communications/data links (networks) may be subjected to enemy EW and signals intelligence (SIGINT) exploitation and attack as well as computer network attack (CNA). TUAVs have a much smaller signature, infrared, radar, audio, electronic, and visual, than conventional manned aircraft, thus reducing the likelihood of detection. Since TUAVs are not hardened and have a very limited maneuver capability, they can easily be damaged or destroyed by weapons strikes; therefore, effective mission planning is critical to the TUAVs survivability. It is essential that during the missionplanning phase, the operator know the location of known ADA threats. He then plans his routes and loiter areas, as necessary, to avoid detection and engagement. The TUAV normally operates at an altitude outside the effective range of small arms. Audio, electronic, and visual signatures of ground components that support TUAV operations (such as generators and radios) are vulnerable to enemy detection and exploitation. This vulnerability increases as the size of the unit or the amount of electronic emission-producing equipment increases. Standard OPSEC measures, such as camouflage, concealment, dispersion, and minimizing electronic emissions, will greatly enhance survivability. When operations require the GDT or TUAV to operate as emitters, their signals are susceptible to enemy detection, interception, and jamming. Autonomous or programmed flight modes reduce the amount of emissions, and consequently increase both TUAV and ground station survivability. Physical security for a TUAV unit depends on the deploying scenario and METT-TC. Under normal circumstances, when deployed within an established perimeter, no additional physical security requirements exist. When deployed independently or outside an established perimeter, the TUAV commander coordinates with the supported unit to provide physical security. TUAVs only require special security precautions (communications security [COMSEC] procedures) when a SIGINT payload is part of the mission. 3.15 Tasking. Tasking channels for Direct Support (DS) and General Support (GS) are as follows: 3.15.1 DS to the Maneuver Brigade Request and Tasking Channels. When TUAV platoons are task organized in a direct support role to the separate maneuver brigades, the controlling GCS will be collocated with the supported brigades TOC. This allows direct tasking by the brigade S2 and real-time downlink of raw data. The brigade S3 Air takes on the responsibility for interfacing with the A2C2 cell to initiate the coordination and deconfliction of airspace. If there are no RVT downlinks to the division, or the downlink is out of range, the brigade S2 has the responsibility to report TUAV collection results to division and higher. As the tasking authority, the brigade S2 collection manager will receive all requests for imagery support from the battalions in the form of requests for intelligence information (RIIs). When appropriate, a TUAV will be selected to fulfill the requirement. For some operations, the brigade S3 will specify TUAV support. An example would be to task a TUAV to support a suppression of enemy air defenses (SEAD) or targeting specific HVTs and high-payoff targets (HPTs). This should be the exception and not the rule. The S2 will forward his collection plan to the division collection manager for deconfliction with the division collection plan and coverage provided by division UAVs or other intelligence collection assets. Whenever possible, a mission request should be received by the appropriate echelon collection manager a minimum of 24 hours prior to the mission so that it can be included in the ACO. The asset manager can task an immediate mission or in-flight modification to an ongoing mission. This requires timely, detailed coordination between the asset manager and the A2C2 cell to ensure successful mission execution. The TUAV requires two hours notice for internal mission planning and flight preparation (if AV preflight has been accomplished and it is ready to launch, this time is reduced to a half-hour). 3.15.2 GS to the Maneuver Brigade Request and Tasking Channels. It is possible that the TUAV will
32 of 42
4/10/13 9:28 PM
not be attached to the separate maneuver brigades and that the division commander will maintain control of these assets. In this scenario, the division ACE will task the TUAV teams directly. TUAV mission taskings will include the same minimum guidance listed in the DS paragraph above. In addition, RIIs from higher and lower can be filled. Once a brigade has determined that they cannot fulfill an information requirement (IR) with organic assets, they will send a request to division for additional support. After prioritizing requirements, the collection manager determines the best supporting asset. If the TUAV is chosen, airspace is coordinated through the division A2C2 element. The asset manager then tasks the TUAV platoon. In GS, RVT or another GCS, with operators, will be located at the brigade TOC.
Tasking and Reporting 3.16 Reporting. Reporting is normally performed through voice or data messages detailing observed activity. Reports are produced in the GCS and sent to the ASAS RWS (reconfigurable workstation) or other consumers. Targeting, fire adjustment, and target damage assessment messages are sent to the AFATDS in supported artillery units. Hard copy photos or recorded video may also be used as well as remoting television monitors from the GCS to the supported TOC. The reporting flow will be as depicted in Figure 2-12 while the majority of reporting will be accomplished using the size, activity, location, unit, time, and equipment (SALUTE) report format. This format is compatible with ASAS RWS requirements and will facilitate correlation and dissemination. Division and higher-level intelligence elements may perform detailed analysis of TUAV imagery products as needed. Rapidly changing tactical requirements will preclude detailed analysis by brigade TUAV operators. TUAV operators will report targets and information as they see them. All in-flight reports are sent as directed by the major command exercising tasking authority (an example might be the brigade tasking the TUAV to support an artillery battalion). All targets reported are transcribed on a multipurpose message given in the form of a free text specifying SALUTE. All targets are numbered and referenced in the log for cross-referencing to videotape and subsequent detailed analysis. 3.17 Airspace Coordination. Regardless of the level where the TUAV is assigned, airspace integration starts with the collection manager that has the tasking authority over that particular UAV. For example, when the TUAV is in DS to the maneuver brigade commander, that brigade S2 in coordination with the S3 Air initiates airspace integration, because the S2 knows where he needs the TUAV to fly. The airspace coordination process is fairly standard worldwide. Theater-specific guidance will dictate
33 of 42
4/10/13 9:28 PM
procedures in all cases. Overflight rights of sovereign nations are not discussed since they are negotiated between the governments involved. The introduction of UAVs into airspace with manned platforms is not new but is still viewed with reservation by airspace planners and coordinators. Therefore it is imperative that the TUAV Mission Commander address airspace coordination issues in a definitive, concise, and proactive manner. For the TUAV to be successfully integrated with manned aircraft, the airspace coordination procedures must be meticulously followed and the system has to be shown to be as safe or safer than manned aircraft. All airspace restrictions and operational and safety procedures imposed by the agency controlling the airspace must be observed. The TUAV Mission Commander must know the timelines associated with the air tasking message or air tasking order and abide by them. To simplify the daily airspace coordination process, the TUAV Mission Commander should seek approval for blocks of airspace and altitudes that provide coverage of areas of high interest and maximize coverage of standing target requirements. Once approved, these blocks and altitudes become recurring items on the air tasking message or air tasking order. Additionally, corridors between the approved blocks need to be established so that it becomes a simple matter to gain approval to transit between blocks. Consistency in requesting and assigning UAV altitudes, corridors, et cetera, also builds confidence in the pilot and airspace coordination community. Knowing where UAVs are regularly flying relieves much of the misgivings in sharing airspace with manned aircraft. It is highly recommended that the use of a UAV blanket altitude be requested for the brigade AO.
GLOSSARY Abbreviations and Acronyms
A
A2C2 Army Airspace Command and Control AADC Area Air Defense Commander AAGSs Army Air Ground Systems ABCCC Airborne Battlefield Command and Control Center ACA Airspace Control Authority ACC Air Combat Command ACC Airspace Control Center ACE Analysis and Control Element ACO Airspace Control Order
34 of 42
4/10/13 9:28 PM
ACP Airspace Control Plan ACR Armored Cavalry Regiment ADA Air Defense Artillery AFATDS Advanced Field Artillery Tactical Data System AFCC Air Force Component Commander AGL Above Ground Level AIRREQRECON Air Request Reconnaissance AIRSUPREQ Air Support Request ALO Air Liaison Officer ANGLICO Air and Naval Gunfire Liaison Company AO Area of Operations AOR Area of Responsibility APC Armored Personnel Carrier APOD Airport of Debarkation ASAS All-Source Analysis System ASM Airspace Management ASOC Air Support Operations Center ATC Air Traffic Control ATO Air Tasking Order ATS Air Traffic Service AV Air Vehicle AVIM Aviation Intermediate Maintenance AVO Air Vehicle Operator AVUM Aviation Unit Maintenance AWACS Airborne Warning and Control System AWE Advanced Warfighter Exercise
B
BCE Battlefield Coordination Element BDA Battle Damage Assessment BIT Built in Test BMCT Brigade Maintenance Contact Team
35 of 42
4/10/13 9:28 PM
BOS Battlefield Operating System BRT Brigade Recon Team
C
C2 Command and Control C4 Command, Control, Communications and Computers C4I Command, Control, Communications, Computers, and Intelligence C4ISR Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance CARS Contingency Airborne Reconnaissance System CAS Close Air Support CCIR Commanders Critical Information Requirements CGS Common Ground Station CIFS Close-in Fire Support CINC Commander in Chief CLS Contractor Logistics Support CNA Computer Network Attack COA Course of Action COMSEC Communications Security CONOPS Concept of Operations CP Command Post CRC Control and Reporting Center CRP Communication/Data Relay Payload CSS Combat Service Support
D
DASC Direct Air Support Center DIA Defense Intelligence Agency DoD Department of Defense DS Direct Support
E
EO Electro-optical
36 of 42
4/10/13 9:28 PM
EPLRS Enhanced Position Location Reporting System ESSC Electronic Service Support Center EW Electronic Warfare
F
FAADS Forward Area Air Defense System FLO Fighter Liaison Officer FOC Flight Operations Center FOV Field of View FRA Forward Repair Activity FPM Feet Per Minute FSB Forward Support Battalion FSCOORD Fire Support Coordination FSE Fire Support Element FSO Fire Support Officer FT Feet
G
GBS Global Broadcast System GCS Ground Control Station GDT Ground Data Terminal GRCS Guardrail Common Sensor GS General Support GSE Ground Support Equipment
H
HMMWVs High Mobility Multi-purpose Wheeled Vehicles HNS Host-Nation Support HPT High Payoff Target HQ Headquarters HR Hour
37 of 42
4/10/13 9:28 PM
HVT High Value Target
I
IC Intelligence Community IEW Intelligence and Electronic Warfare IEWSS IEW Sustainment Streamlining System IFF Identification, Friend or Foe IPB Intelligence Preparation of the Battlefield IR Infrared IR Information Requirement ISR Intelligence, Surveillance and Reconnaissance
J
JFACC Joint Force Air Component Commander JFC Joint Forces Commander JFLCC Joint Forces Land Component Commander JOA Joint Operations Area JSTARS Joint Surveillance Target Attack Radar System
K
KG Kilogram KM Kilometer KTS Knots
L
LBS Pounds LLTR Low-Level Transit Routes LO Liaison Officer LOS Line of Sight L/R Launch and Recovery Site LRU Line Replaceable Unit
38 of 42
4/10/13 9:28 PM
M Meter MANPADS Man Portable Air Defense METT-TC Mission, Enemy, Troops, Terrain and Weather, Time available and Civil considerations MI Military Intelligence MMF Mobile Maintenance Facility MMP Modular Mission Payloads MNS Mission Needs Statement MOGAS Motor Gasoline MOOTW Military Operations Other Than War MPCS Mission Planning and Control Site MPO Mission Payload Operator MRR Minimum-Risk Routes MSE Mobile Subscriber Equipment MSL Mean Sea Level MTI Moving Target Indicator
N
NAI Named Areas of Interest NAVAIDS Navigational Aids NBC Nuclear, Biological and Chemical NCO Noncommissioned Officer NITF National Imagery Transmission Format NM Nautical Miles NRT Near-Real Time
O
OPLAN Operation Plan OPORD Operation Order OPS Operations OPSEC Operations Security OPTEMPO Operational Tempo
39 of 42
4/10/13 9:28 PM
ORD Operational Requirements Document
P
PGCS Portable Ground Control Station PGDT Portable Ground Data Terminal PIR Priority Intelligence Requirements
Q
QC Quality Control
R
RII Request for Intelligence Information ROZ Restricted Operating Zone RSTA Reconnaissance, Surveillance, and Target Acquisition RVT Remote Video Terminal
S
SALUTE Size, Activity, Location, Unit, Time and Equipment SAM Surface to Air Missile SAR Synthetic Aperture Radar SEAD Suppression of Enemy Air Defenses SIF Selective Identification Feature SIGINT Signals Intelligence SINCGARS Single Channel Ground and Airborne Radio System SIPRNET SECRET Internet Protocol Router Network SOF Special Operations Forces SOP Standing Operating Procedure SPINS Special Instructions STU-III Secure Telephone Unit SUT Single Unit Transceiver
T
TACP Tactical Air Control Party
40 of 42
4/10/13 9:28 PM
TACS Theater Air Control System TACLAN Tactical Local Area Network TAI Target Areas of Interest TCDL Tactical Common Data Link TOC Tactical Operations Center TUAV Tactical UAV
U
UAV Unmanned Aerial Vehicle UHF Ultra High Frequency US United States USMTF United States Message Text Format USN United States Navy USMC United States Marine Corps USAF US Air Force USAIC&FH United States Army Intelligence Center and Fort Huachuca USIGS United State Imagery and Geospatial System
V
VHF Very High Frequency VISP Video Imagery Standards Profile
41 of 42
4/10/13 9:28 PM
42 of 42
4/10/13 9:28 PM

Tactical Unmanned Aerial Vehicle (TUAV)

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Tactical Unmanned Aerial Vehicle (TUAV)

Hochgeladen von

Copyright:

Verfügbare Formate

Tactical Unmanned Aerial Vehicle (TUAV)

Paid Online Employment