Download - Small UAV Manual
Purpose
The purpose of this handbook is to enhance understanding of Army airspace command and control
(A2C2) to mitigate risks between small unit unmanned aerial vehicles (SUAVs) and rotary wing
operations below the coordinating altitude. This handbook provides leaders at the brigade and
below with guidelines in the form of airspace coordination techniques and procedures regarding
SUAV mission planning and airspace deconfliction.
This handbook is the result of combining information from several sources, including Raven
operators currently deployed in support of Operation Enduring Freedom and Operation Iraqi
Freedom.
Scope
This handbook provides an overview of A2C2, to include types of airspace control, modular design,
and unit-level duties and responsibilities. It also focuses on SUAV operations and A2C2. Finally, it
discusses common SUAV airspace coordination techniques and procedures.
Due to the dynamic nature of both rotary wing and SUAV operations, A2C2procedures must be established and enforced by the Chain of Command.
WARNING
Failure to conduct airspace coordination prior to SUAV operations may
contribute to a mid-air collision resulting in severe injury or death to personnel.
LAWRENCE H. SAULCOL, FADirector, Center for Army Lessons Learned
LEADER’S GUIDE TO A2C2 AT BRIGADE AND BELOW
TABLE OF CONTENTS
CHAPTER 1: ARMY AIRSPACE COMMAND AND CONTROL 1
TYPES OF AIRSPACE CONTROL 1
TYPES OF SEPARATION 4
A2C2 UNDER THE MODULAR DESIGN 4
BATTALION A2C2 TASKS 6
SUAV MISSION REQUEST FORMAT 6
MISSION APPROVAL FLOW GUIDE 7
CHAPTER 2: SUAV OPERATIONS AND A2C2 11
SUAV PLANNING AND MISSION EXECUTION 11
AIRSPACE MANAGEMENT FOR SUAVS 11
PREPLANNED SUAV OPERATIONS 12
IMMEDIATE SUAV OPERATIONS 12
CHAPTER 3: COMMON SUAV TACTICS, TECHNIQUES, AND PROCEDURES 15
TYPES OF PROCEDURAL AIRSPACE CONTROL 15
LOSS OF LINK RECOVERY OPERATIONS 20
APPENDIX A: MISSION FLOW GUIDE 21
APPENDIX B: SUAV TROOP-LEADING PROCEDURES CHECKLIST 23
APPENDIX C: MISSION REQUEST FORMATS 25
APPENDIX D: RAVEN SUAV SPECIFICATIONS 29
ACRONYMS 31
REFERENCE LIST 33
FOR OFFICIAL USE ONLY i
LEADER'S GUIDE TO A2C2
CENTER FOR ARMY LESSONS LEARNED
Director Colonel Lawrence H. Saul
Managing Editor Dr. Lon Seglie
This handbook represents a collaborative effort of personnel across the Army, to include:
Fort Benning, Fort Bliss, Fort Huachuca, Fort Knox, Fort Leavenworth, Fort Rucker, Fort Sill, Hurlburt Field, FORSCOM Units, and Units Deployed to Iraq and Afghanistan.
Editor Angela McClain
Graphic Artist Mark Osterholm
Publication Administrator Carrie Harrod
CALL has many products of interest to the Total Force. We invite you to visit our Web site at:
http://call.army.mil
The intent of this CALL publication is to share knowledge, support discussion, and impart lessons
and information in an expeditious manner. This CALL publication is not a doctrinal product. The
tactics, techniques, and procedures (TTP) observed and reported in this publication are written by
Soldiers for Soldiers. Please send relevant TTP to Mr. George J. Mordica II, Managing Editor
(commercial: (913) 684-9503 or DSN: 552-9503, FAX: DSN 552-9583, E-mail:
<[email protected]>). Articles must be submitted in Microsoft Word format.
Graphs, slides, and clipart must be submitted separately in their original form in either TFF, PSD
(Adobe Photoshop), or high resolution JPEG format.
The Secretary of the Army has determined that the publication of this periodical is necessary in the
transaction of the public business as required by law of the Department. Use of funds for printing
this publication has been approved by Commander, U.S. Army Training and Doctrine Command,
1985, IAW AR 25-30.
Unless otherwise stated, whenever the masculine or feminine gender is used, both are intended.
Note: Any publications referenced in this newsletter (other than the CALL newsletters), such as
ARs, FMs, and TMs must be obtained through your pinpoint distribution system.
This information was deemed of immediate value to forces engaged in the Global War on Terrorism
and should not necessarily be construed as approved Army policy or doctrine.
This information is furnished with the understanding that it is to be used for defense purposes only;
that it is to be afforded essentially the same degree of security protection as such information is
afforded by the United States; that it is not to be revealed to another country or international
organization without the written consent of the Center for Army Lessons Learned.
ii FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
CHAPTER 1 ARMY AIRSPACE COMMAND AND CONTROL
GENERAL
Army airspace command and control (A2C2) is the Army’s application of airspacecontrol to coordinate airspace users for concurrent employment in theaccomplishment of assigned missions. Effective A2C2 enables all the battlefieldoperating systems to function efficiently while synchronizing air operations tosupport the commander’s intent. Successful A2C2 is dependent upon the ability toperform the functions of identification, coordination, integration, and regulation ofairspace users. A unit’s proficiency in performing these functions correlates to itsaptitude in command and control, air defense, fire support coordination, air trafficcontrol, and airspace management activities.
It is important to understand that the term A2C2 does not denote Army ownershipof a block of airspace or command over activities within that airspace. Rather, itrefers to Army users of the airspace. All air missions are subject to the airspacecontrol order (ACO) published by the Airspace Control Authority (ACA). Itprovides direction to deconflict, coordinate, and integrate the use of airspace withinthe operational area. Joint forces also use airspace to conduct air operations,deliver fires, employ air defense measures, and conduct intelligence operations. Attimes, these missions may be time sensitive and preclude the ability to conductdetailed coordination with the land force. It is imperative that land forces providetheir higher headquarters with all airspace control measures in order to providevisibility to other Joint users and prevent fratricide.
Airspace control does not infringe on the authority vested in commanders toapprove, disapprove, or deny combat operations. The primary objective of airspace control is to maximize the effectiveness of combat operations without adding undue restrictions and with minimal adverse impact on tactical operations. See FM 3-52,Army Airspace Command and Control in a Combat Zone, Aug 2002.
1. TYPES OF AIRSPACE CONTROL
Brigade operations require the commander to utilize airspace control to synchronize air and ground battlespace in support of the scheme of maneuver. Airspace usersare controlled by positive and procedural means, or a combination of both. Examples which combine both procedural and positive control measures are located in Chapter 3.
FOR OFFICIAL USE ONLY 1
LEADER'S GUIDE TO A2C2
Positive Control
Positive control is conducted by elements designated by the ACA that positivelyidentify, track, and direct air assets in the airspace control area. It uses electronicmeans such as radar; other sensors; identification, friend or foe (IFF) systems;selective identification feature capabilities; digital data links; and other elements ofthe command, control, communications, and computer systems. Normally, thebrigade combat team (BCT) does not have the capability to provide positive control unless augmented with an air traffic services (ATS) support package.
Procedural Control
Procedural control relies on previously agreed to and disseminated airspace controlmeasures; these may include rules of engagement (ROE), restricted operatingareas/zones (ROA/ROZ), standard use Army aircraft flight route (SAAFR), aircraftidentification maneuvers, fire support coordinating measures (FSCM), andcoordinating altitudes. Chapter 4 of FM 3-52 describes the different types ofprocedural control measures. Furthermore, it provides Army airspace controlmeasures standing operating procedures, which aid in deconfliction.
Among the procedural airspace control measures, it is particularly important forleaders at brigade, battalion, company, and platoon levels to understand thefollowing:
a. An air control point (ACP) is an easily identified point on the terrain oran electronic navigational aid used to provided necessary control during airmovement. ACPs are generally designated at each point where the flightroute or air corridor makes a definite change in any direction and at anyother point deemed necessary for timing or control of operations. It is agraphic control measure used to segment an air corridor similar tocheckpoints on a ground route.
b. An air corridor is a restricted air route of travel specified for use byfriendly aircraft and established for the purpose of preventing friendlyaircraft from being fired on by friendly forces. Air corridors are used toroute combat aviation elements between such areas as forward arming andrefueling points (FARPs), holding areas, and battle positions. Thesecorridors also deconflict artillery firing positions with aviation traffic,including unmanned aerial vehicles (UAVs). Altitudes of an air corridor donot exceed the coordinating altitude.
c. A base defense zone (BDZ) is an air defense zone established around anair base and limited to the engagement envelope of short-range air defenseweapon systems defending that base (JP 3-52). BDZs have establishedentry, exit, and IFF procedures. The base defense zone may be thought of as a specific type of ROA or special-use airspace. Employment of counter-rocket, artillery, and mortar (C-RAM) capabilities at fixed sites or baseswithin a BCT's area of operations (AO ) may necessitate the establishment
2 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
of a BDZ.
d. Coordinating altitude is a procedural airspace control method used toseparate fixed and rotary wing aircraft. This method determines an altitudebelow which fixed-wing normally will not fly and above which rotary wingwill normally not fly. The airspace control plan (ACP) normally specifiesthe coordinating altitude and may include a buffer zone for small altitudedeviations.
e. Restricted operating zones/areas (ROZ/ROA) is airspace of defineddimensions created in response to specific operational situations orrequirements within which the operation of one or more airspace users isrestricted. Establishing an ROZ helps prevent fratricide by closelyrestricting access over a designated surface area. Typical uses are overArmy Tactical Missile System (ATACMS) launch and target areas as wellas UAV launch and recovery areas. Depending upon the ACP, a specificarea of responsibility (AOR) may or may not be included on the ACO.
ROZ/ROAs can be established over areas where combat operationsinvolving a mix of air vehicles are likely to be employed (i.e. over urbanoperations areas). The ROZ/ROA is disseminated throughout theater usingthe ACO. Information about the ROZ includes contact frequency for theaircraft desiring to transition through the ROZ.
The BCT responsible for the AO is also in charge of monitoringfrequency and communicating with aircraft as required for the entire periodthe ROZ is active. Although the brigade tactical operations center (TOC)radio-telephone operator (RTO) may be responsible for monitoring thefrequency, the brigade fire support element (FSE) coordinates and tracks allfires and aviation activity in the ROZ/ROA. Refer to FM 3-52 for moreinformation.
WARNING
Failure to conduct airspace coordination prior toSUAV operations may contribute to a mid-air collision
resulting in severe injury or death to personnel.
FOR OFFICIAL USE ONLY 3
LEADER'S GUIDE TO A2C2
2. TYPES OF SEPARATION
There are three primary means of maintaining separation between manned andunmanned aircraft: lateral, time, and vertical separation. Beyond the need to ensure physical separation exists, leaders must plan for frequency separation betweenunmanned vehicles.
a. Lateral separation spaces aircraft that may be operating at the samealtitude by not having them operate in the same geographic space. This canbe done through the assignment of flight corridors, ROA/ROZ, and othergraphic control measures such as phase lines and unit boundaries.
b. Time separation spaces aircraft that may be operating in the samegeographic area or at the same operating altitudes by not allowing them tooperate at the same time. Time separation may also be required whenaircraft, manned and unmanned, must fly near indirect-fire trajectories orordnance effects. The timing of surface fires must be coordinated withaircraft routing. This ensures that, even though aircraft and surface firesmay occupy the same space, they do not do so at the same time.
c. Vertical separation spaces aircraft based on operating altitude or byassigning different operating altitudes to other aircraft that may be workingin the same geographic area. Vertical separation is the least preferredmethod since SUAVs and rotary wing aircraft normally operate from thesurface to 500 feet above ground level (AGL).
3. A2C2 UNDER THE MODULAR DESIGN
In the Modular Force, airspace management occurs in A2C2 cells, organic to unitsfrom the BCT through the unit of employment (UEy). These cells combine aviationand air defense artillery personnel who operate in close coordination with the unit’s fires and effects cell (FEC). Fires and airspace deconfliction in the FEC at the BCT level is closely coordinated between the targeting officer, air liaison officer (ALO),effects coordinator (ECOORD) and the Air Defense Airspace Management/Brigade Aviation Element (ADAM/BAE) cell. The FEC and the ADAM/BAE cells shouldbe located side by side in the BCT command post (CP) to facilitate rapidcoordination.
These A2C2 cells from the BCT through the UEy have full digital connectivity tothe theater level, enabling the BCT to request airspace digitally. This digitalconnectivity should drastically reduce the processing and staffing time associatedwith airspace requests. The Tactical Airspace Integration System (TAIS) is thecomponent of the Army Battle Command System (ABCS) for automating andintegrating airspace management at the BCT and above.
4 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
Note: For units that have not yet transitioned to the Modular Force, commandersmust assign these critical duties and responsibilities of airspace coordination tosomeone within their organization (usually a member of the S3 staff).
See battalion A2C2 tasks on the following page. Other methods are available andused for non-TAIS equipped organizations or when TAIS digital connectivity doesnot exist. See Appendix C for examples.
Brigade A2C2 Organization
a. Brigade Combat Teams: BCTs have an ADAM/BAE cell to conduct thefunction of airspace management. The ADAM/BAE combines air and missiledefense and aviation personnel, along with enhanced digital capabilities, to providethe BCT with a capability to perform A2C2 and maintain a near real-time airspacepicture. The ADAM/BAE coordinates A2C2 requirements with higher headquarters and may be required to coordinate with Joint or Multi-National Forces to integratethe BCT requirements into the operations.
The brigade aviation officer (BAO) is the lead integrator among the brigadestaff members responsible for A2C2 tasks. The primary duty of the BAO is tointegrate aviation into the scheme of maneuver. The BAO accomplishes this byclose coordination with the S-3 and BCT commander. The BAO works for theBCT commander and is an integral part of his staff. He must also maintain arelationship with the aviation brigade commander and his staff. The BAO mustensure that appropriate information is exchanged between the aviation brigade, theBCT, and the rest of the BAE to facilitate smooth and timely aviation support.
Within the ADAM/BAE, the BAE supports the BCT commander by planning andsynchronizing Army aviation operations and conducting A2C2 throughout the BCT AOR. Paired to this effort, the ADAM provides the BCT commander with a jointcapability. It can link with an air picture provider, (joint or local) to detect aircraftas they become airborne, assign them a friendly identification (ID), and transmit the track information and ID to reduce the chance of fratricide. The ADAM cell airdefense coordinating officer is in charge of air and missile defense (AMD)operations within the ADAM/BAE and provides situational awareness, situationalunderstanding, and early warning for the brigade.
The ADAM/BAE implements and disseminates the airspace control order (ACO)for brigade and below and the FEC provides the same function for the air taskingorder (ATO). The BAE is responsible for the integration and synchronization ofthe ACO/ATO. The BAE is responsible for the integration and synchronization ofArmy aviation and UAVs and submits airspace control means requests (ACMREQ) to the next higher A2C2 element. When the BCT works directly for a Joint TaskForce, the ADAM/BAE is capable of interfacing directly with the battlefieldcoordination detachment (BCD) (the Army’s liaison at the air operations center).
FOR OFFICIAL USE ONLY 5
LEADER'S GUIDE TO A2C2
b. Other Brigades: The ADAM/BAE is a standardized organization that exists inthe heavy and light BCTs. A similar organization, the ADAM cell, exists in theStryker brigade combat team (SBCT) with a smaller aviation element. Variants ofthe ADAM/BAE also exist in other brigades such as the Battlefield SurveillanceBrigade (BFSB), Fires Brigade, and Aviation Brigade. While the structure may bedifferent from the ADAM/BAE in the BCT, the functions and responsibilitiesremain the same.
Battalion and Below A2C2 Organization
The battalion and below have no formal A2C2 element. The battalion S3 hasoverall responsibility for coordinating, deconflicting, and managing airspacewithin the battalion AO. The ADAM/BAE at the BCT minimizes the A2C2workload on battalion/company/platoon SUAV operators. The battalions mustcoordinate with the ADAM/BAE at the BCT to ensure their mission requests areprocessed as efficiently and expeditiously as possible.
4. BATTALION A2C2 TASKS
• Establish “S3 Air” equivalent, from existing personnel assigned to the S3section, that has staff responsibility for all SUAV operations.
• Receive and disseminate SUAV airspace request approvals/ changes/disapprovals.
• Review planned and immediate airspace requests and resolve conflicts within the battalion.
• Monitor and analyze aviation, SUAVs, field artillery, air defense, andmaneuver operations to determine and resolve conflicts.
• Submit to ADAM/BAE all planned and immediate airspace requestsincluding SUAV (Appendix C).
• Communicate any deviations from pre-planned mission to the ADAM/BAEor higher headquarters immediately.
• Ensure no SUAV flies without prior airspace coordination through theADAM/BAE or higher headquarters.
• Inform airspace users at each echelon of any communication loss duringoperations.
• Track and report aviation, field artillery, air defense, and SUAV systems andpersonnel status.
• Monitor rotary/fixed wing aircraft in the battalion AOR to aid indeconflicting SUAVs and other air traffic.
• Manage separation and frequencies of battalion and below UAV operations.
5. SUAV MISSION REQUEST FORMAT
There are two types of mission requests: planned and immediate. Further, there aretwo formats for requesting planned missions and one format for an immediatemission. Examples of mission requests are located in Appendix C. The battalion
6 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
will consolidate and deconflict subordinate mission requests and send to theADAM/BAE at the BCT. The ADAM/BAE will extract the pertinent informationfor airspace management. If TAIS is used to deconflict airspace, the ADAM/BAEwill enter the data into the TAIS workstation. Mission requests can be sent by radio(Single Channel Ground and Airborne Radio System [SINCGARS], very highfrequency [VHF], ultra high frequencey [ UHF]), advanced mobile phone system[AMPS], Force XXI battle command brigade and below (FBCB2), TAIS Web pagefor Airspace Control Means Requests and Tracking [WebACMR], or Blue forcetracking (BFT).
6. MISSION APPROVAL FLOW GUIDE (See Appendix A for abbreviated checklist)
The ADAM/BAE, representing the brigade commander/S3, has the responsibility to deconflict air missions between battalions. Conflicts may result in missionmodifications or cancellation dependant upon mission priority.
ABCS provides a means for rapid deconfliction and the ability to quickly sharedigital airspace information between units and higher echelons. Because theADAM/BAE will have visibility of airspace requests across the network, mostdeconfliction will occur at the brigade level.
For non-Modular Forces or forces lacking digital connectivity, the mission approval flow remains the same but the systems used and the personnel executing specificresponsibilities will be different. The S3/G3 and the S3/G3 Air carry out the rolesand responsibilities of the ADAM/BAE/UEx A2C2 Cell. While TAIS is theprimary intended means for managing airspace, other methods are available andused for non-TAIS equipped organizations or when TAIS digital connectivity doesnot exist. An example of another method would be to create a Falcon View screencapture that is then imported into a Power Point slide. See Appendix C for example format and detailed information.
SUAV MISSION PLANNING FLOW
1. Battalion commander, S3, S2, fire support officer (FSO), or companycommander determines a need for SUAV mission.
2. Battalion S3 (or S3 Air, if assigned) ensures no internal battalion conflict withother internal SUAV operations and other known airspace users (aircraft; close airsupport [CAS]; fires; counter-rocket, artillery, and mortar [C-RAM], etc.) andpasses initial mission data down to supporting company to begin planning. Thecompany, with assistance from the SUAV mission commander, creates a detailedflight plan that includes specific routes, times, and locations. The battalion S3 alsosubmits a mission request up to the BCT’s ADAM/BAE (see Appendix C).
FOR OFFICIAL USE ONLY 7
LEADER'S GUIDE TO A2C2
3. If the ADAM/BAE receives the request by voice or text, they enter the pertinentairspace data into the TAIS. If the data is received via WebACMR, the data will be automatically entered into TAIS. The ADAM/BAE reviews the mission request todetermine any airspace conflicts between the SUAV and other airspace users in thebrigade AO.
• Since most SUAV missions fly below the coordinating altitude, the focus fordeconfliction will be with Army aviation or CAS weapons effects.
• Theater-specific directives will determine mission request approval authority.• When C-RAM capabilities are employed in the brigade AOR, a base defense
zone (BDZ) or similar airspace control measures (ACM) may impose certainadditional deconfliction or coordination requirements on UAV operations, toinclude coordination with any C-RAM unit operating at intended SUAVlaunch/recovery sites.
4. If a conflict exists, the ADAM/BAE determines mission priority based upon thecommander’s guidance and makes recommendations to the brigade airspaceapproval authority (the brigade S3 or brigade CDR). Once a course of action isapproved, the ADAM/BAE notifies the affected battalion S3/S3 Air and providesrecommended modifications to support mission request, if possible.
• Battalion S3/S3 Air accepts modifications or provides an alternative courseof action (COA).
• The ADAM/BAE then updates the modified/alternate mission data withhigher headquarters.
5. Once the ADAM/BAE deconflicts the mission request, it is forwarded to higherheadquarters A2C2 Cell and G3 Aviation (AVN) Cell (usually the UEx).
• As the company further refines the mission details, it sends the updated datato the battalion S3/S3 Air, who in turn forwards it to the ADAM/BAE.
• The ADAM/BAE adds any additional detail/modifications to the missionrequest, which is now potentially visible at every brigade and above levelA2C2 cell in theater.
6. The UEx A2C2 cell forwards the approved mission request to higher A2C2 cellsand all subordinate BCTs and support brigades (ie, Fires Brigade, ManeuverEnhancement [ME] Brigade, Battlefield Surveillance Brigade [BFSB], andAviation [AVN] Brigade) for coordination and safety purposes. If the approvalauthority is UEx or higher, formal approval methods will be used and the missionrequest will be approved once it is deconflicted.
• If the mission request conflicts with other missions, UEx A2C2 celldetermines mission priority based upon the commander’s guidance andmakes recommendations to the UEx approval authority (usually the UEx G3).
8 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
• Once the airspace approval authority approves a COA, the UEx A2C2 cellnotifies the affected brigade ADAM/BAE cell of the conflict and providesrecommended modifications to support the mission request.
• The ADAM/BAE deconflicts the mission with appropriate requestingorganization.
• ADAM/BAE sends modified approved mission request back to UEx A2C2cell for deconfliction/approval/situational awareness (approving authoritydependent), simultaneously updating and modifying previously submittedmission requests.
7. Once the UEx deconflicts the mission request across the entire UEx force, themission request is forwarded to the higher headquarters in accordance withtheater-specific procedures.
FOR OFFICIAL USE ONLY 9
LEADER'S GUIDE TO A2C2
CHAPTER 2SMALL UNIT UNMANNED AERIAL VEHICLE (SUAV)
OPERATIONS AND A2C2
1. SUAV PLANNING AND MISSION EXECUTION
The mission of the SUAV is to provide reconnaissance, surveillance, and targetacquisition (RSTA); day/night imagery to support situational awareness; and battledamage assessment (BDA). The SUAV operates from platoon to battalion leveland is suited for rapid employment to meet the needs of the commander.
Due to the dynamic nature of both rotary wing and SUAV operations, A2C2procedures must be established and enforced by the chain of command.
2. AIRSPACE MANAGEMENT FOR SUAVs
Airspace control procedures must be used to safely employ SUAVs in conjunctionwith rotary and fixed wing aircraft, other UAVs, friendly air defense fires, andindirect fires in the unit of employment (UEx) airspace. Each unit will have uniqueairspace challenges based on its area of operations (AO) (civilian airports,controlled airspace, urban operations, etc.) and mission set (tactics, techniques, andprocedures [TTP] for employment of air and fires assets). Because of these distinctdifferences in AOs, SUAV planners must know and comply with the establishedairspace procedures and applicable area of responsibility (AOR) aviator planningguide to prevent loss of life and/or damage to equipment.
SUAV flights must be coordinated to ensure deconfliction with other airspaceusers. The primary means for ensuring that the SUAVs are deconflicted withall other airspace users is through the Air Defense Airspace Management /Brigade Aviation Element (ADAM/BAE) at the brigade. The ADAM/BAEserves as the “one stop shop” in the Modular Force for airspace deconfliction at thebrigade level. The ADAM/BAE deconflicts all airspace missions within thebrigade and forwards requests to higher headquarters to ensure deconfliction occurs with units above the brigade level. The ADAM/BAE will coordinate amongbattalions, through higher headquarters, to safely separate SUAVs from mannedaircraft and to prevent engagement by friendly air defense systems.
The Airspace Control Authority (ACA) may use the coordinating altitude toseparate fixed wing traffic from SUAV traffic in the same manner it sometimesuses the coordinating altitude to separate fixed wing traffic from rotary wing traffic. If this occurs, the approval authority for most SUAV missions will reside at either
FOR OFFICIAL USE ONLY 11
LEADER'S GUIDE TO A2C2
the UEx or, possibly, at the brigade level and mission requests will be sent higherfor situational awareness.
WARNING
Failure to conduct airspace coordination prior to SUAV operations may contribute to a mid-air collisionresulting in severe injury or death to personnel.
3. PREPLANNED SUAV OPERATIONS
Preplanned SUAV flights should, when possible, appear on the Airspace ControlOrder (ACO) allowing for advanced notice of SUAV operations to manned rotarywing aircraft. Airspace requirements are identified and requested through airspacemanagement channels (ADAM/BAE) during planning to ensure deconfliction. Ifapproval authority resides below the Joint Forces Air Component Commander(JFACC), these missions may not appear on the air tasking order (ATO)/ACO if the SUAV operating altitude remains below the coordinating altitude. Instead, the UEx may manage a separate list or matrix of missions below the coordinating altitudethat, nevertheless, must be deconflicted and receive approval internal to the UEx.
The information required can be found in Appendix C, Mission Request Format. This should be submitted as soon as possible to the ADAM/BAE for deconfliction.
4. IMMEDIATE SUAV OPERATIONS
Immediate SUAV missions are conducted with limited or no prior planning. Despite being time sensitive, airspace coordination must still occur. It is incumbent upon units at all levels to develop battle drills to expedite planning, A2C2, andmission execution. Immediate SUAV missions will be coordinated with theappropriate airspace control agencies (the ADAM/BAE at the BCT) to safelyseparate SUAVs from manned aircraft and to prevent inadvertent engagement byfriendly air defense elements.
At a minimum, the Immediate Mission Request Format (below) must be submittedto the ADAM/BAE. The requestor will be informed by the ADAM/BAE whenlaunch permission is granted and a UAV launch alert should be broadcasted tonotify all BCT airspace users.
12 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
Immediate Mission Request Format:
Line 1: Unit identification (call sign and frequency)Line 2: Launch and recovery siteLine 3: Restricted operating areas (ROA) location (includes global
positioning system [GPS] coordinates and operating altitude)Line 4: Ingress route azimuth and distanceLine 5: Egress route azimuth and distanceLine 6: Times and durations of missionLine 7: SUAV operating channel
FOR OFFICIAL USE ONLY 13
LEADER'S GUIDE TO A2C2
CHAPTER 3COMMON SMALL UNIT UNMANNED AERIAL VEHICLE(SUAV) AIRSPACE COORDINATION TECHNIQUES AND
PROCEDURES
1. TYPES OF PROCEDURAL AIRSPACE CONTROL
Figure 1. SUAV Operations within Vicinity of Forward Operating Base (FOB)
SUAV Operations within Vicinity of FOB• This procedure involves two basic principles: Pre-establishment of ROAs
and operating only within approved/active ROAs.• Pre-establish ROAs around the FOB over key areas to facilitate rapid launch
of SUAV as part of a quick reaction force.• Battalion S3 submits SUAV mission request to ADAM/BAE cell.• If a Battalion FOB, the battalion S3/fire support officer (FSO) will manage
the airspace.• Operators call tactical operations center (TOC) and obtain clearance from
S3/FSO prior to launching SUAV and remain in radio contact during entiremission.
• Higher headquarters is advised of SUAV launch for quick reaction mission.• TOC deconflicts airspace with rotary wing aircraft.
FOR OFFICIAL USE ONLY 15
LEADER'S GUIDE TO A2C2
Figure 2. SUAV Operations within a BCT AOR
SUAV Operations within a Brigade Combat Team (BCT) Area ofResponsibility (AOR)
• SUAV operations within a BCT AOR follow the principles of a pre-plannedor immediate mission.
• SUAV operators request to establish an ROA (within the AOR) to supportthe mission.
• Airspace controlling agency establishes ROA and disseminates to rotarywing units operating in AOR.
• Rotary wing assets requesting to transition through AOR are notified ofongoing SUAV operations on the brigade/battalion TOC net.
• SUAV operators contact battalion TOC prior to launch.• Battalion TOC notifies higher headquarters TOC.• SUAV operators maintain radio/digital contact during entire mission with
airspace controlling agency of AOR.
16 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
Figure 3. SUAV Operation Vicinity Airfield/Airport
SUAV Operations Vicinity Airfield/Airport• SUAV mission is within controlled airspace.• Tower controls the airspace and is responsible for deconfliction.• SUAV operators or staff representative conduct coordination with tower and
establish procedures for SUAV operations within the controlled airspace.• SUAV operators establish means of two-way communications with tower.• SUAV operators submit mission plan in advance, if possible.• SUAV operators request permission to launch and recover the SUAV.• SUAV operators must maintain positive communications with the control
tower during SUAV operations in the controlled airspace.• SUAV operators take commands from the tower during operations, as
required, to allow other traffic to move through ROA.• Upon mission completion, the operators call tower and close the ROA.
Note: This example does not circumvent the normal planning sequence, but sincethe operation occurs within controlled airspace, the SUAV operator mustcoordinate and communicate directly with the airspace controller during executionof the mission.
FOR OFFICIAL USE ONLY 17
LEADER'S GUIDE TO A2C2
Figure 4. SUAV Operations outside BCT AOR
SUAV Operations outside BCT AOR• Mission required for convoy security or route reconnaissance operations
when operating outside the BCT AOR (i.e., convoy/route recon/improvisedexplosive device [IED] sweep).
• May be used in non-contiguous operations, where SUAV operates betweenBCTs’ AORs in areas controlled by UEx.
• SUAV operators request, in advance, (through battalion and BCT) toestablish an ROA to support the mission.
• Use of an air route, with multiple air control points (ACP), is a suitable formof airspace control for these types of missions.
• If a standard use Army aircraft flight route (SAAFR) already exists, this route could be used. To prevent an entire route being activated, battalion notifiesthe ADAM/BAE to activate segments as the convoy moves, freeing theremainder of the SAAFR for other airspace users.
• ADAM/BAE submits request through the UEx for coordination.• SUAV operator maintains communications with higher headquarters or
airspace controlling agency during entire mission.• Common procedures also established to separate SUAV from other aircraft.• Battalion communicates with rotary wing aircraft as required to facilitate
traffic avoidance.
18 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
Figure 5. SUAV High Density Urban Operations
SUAV High Density Urban Operations• It is an area with a high volume of rotary wing/fixed wing and UAV traffic.• A high density urban area is segmented into zones for ease of procedural
control, and managed by an airspace control agency (i.e. Baghdad Radio).• Two-way communications is required for all participants.• SUAV operators submit mission request in accordance with standard request
procedures (including L/R point and mission ACPs).• After mission approval from battalion, SUAV operators call the airspace
control agency prior to launch and maintain positive communications duringoperation.
• SUAV operators must request permission from the airspace control agencyprior to movement between ACPs or zones prior to descending below transitaltitude.
FOR OFFICIAL USE ONLY 19
LEADER'S GUIDE TO A2C2
2. LOSS OF LINK RECOVERY OPERATIONS
Loss of link is a function of no uplink from the ground control unit (GCU) to the air vehicle, no down link from the air vehicle to the GCU, or both. When this loss oflink occurs, the air vehicle will initiate whatever program was planned into theGCU (i.e., rally to a predetermined point or land as soon as loss of link is detected). Failure to adequately prepare for loss of link may result in loss of air vehicle. Iflink quality degrades to the point where the operator no longer has control of the air vehicle, the operator must do the following:
• Immediately notify higher airspace controlling agency (i.e. fires and effectscell [FEC], combat control teams [CCT]) of air vehicle loss of link toinclude: last known position, heading, airspeed, altitude, and approximatebattery time remaining.
• Continue attempts to regain control of the air vehicle, including commandingAUTOLAND.
• Assess the situation (proximity of other aircraft, restricted airspace, etc.) andreport possible entry of the air vehicle into any known hazards.
Upon notification of an SUAV that is no longer controlled by the operator, theADAM/BAE or airspace control agency (tower, Baghdad Radio, FOB TOC) willbroadcast an advisory on appropriate frequencies to notify any other airspace usersof the errant SUAV.
20 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
APPENDIX A: MISSION FLOW GUIDE
• SUAV mission requirement determined• Mission planning at appropriate levels begins• Mission request submitted from battalion to ADAM/BAE• ADAM/BAE reviews mission request for conflicts• If there are no conflicts, the ADAM/BAE notifies the battalion S3 of
acceptance and forwards to next higher level authority• If there is a conflict, ADAM/BAE:
» Makes recommendations to the airspace approval authority
» Notifies the battalion S3 along with recommended modifications
» Battalion S3/S3Air accepts or provides an alternative
» The ADAM/BAE updates the mission• Mission request is forwarded to the next higher A2C2 cell (usually the UEx)• Mission refinements are continually forwarded for update
Figure 1. Mission Flow
FOR OFFICIAL USE ONLY 21
LEADER'S GUIDE TO A2C2
APPENDIX B: SUAV TROOP-LEADING PROCEDURES CHECKLIST
RECEIVE THE MISSION• Identify priority information requirements (PIR), specific named areas of
interest (NAIs)• Time of mission execution• Get target approval from battalion• Request weather forecast from S2
ISSUE WARNING ORDER• Charge / confirm charge of aircraft / video recorder batteries• Prep aircraft (two aircraft if available or as per SOP), GCU, and remote video
terminal (RVT)• PCI equipment list
• Binoculars• Hand-held GPS• Map• Charged batteries (GCU and AV)• Battery charger and generator or power source• Compass• Repair kit with tape• Flashlight and chemlights• Recording device• Flight logs• SUAV Operator's Manual• Notebook• Wind meter
MAKE A TENTATIVE PLAN• Refer to SUAV Operator’s Manual for planning considerations• Initiate the mission planning process with consideration given to:
• Aircraft availability• Location and compliance with ACMs (ROZ/ROA, etc.)• Mission launch criteria• Weather• Target location• Collection requirements• Threat• Battery requirements• Altitude and speed• Loiter times• Crew manning• UAVs return to home locations• Emergency recovery options
FOR OFFICIAL USE ONLY 23
LEADER'S GUIDE TO A2C2
• Plot target and mission (utilize Portable Flight Planning Software(PFPS)/Falcon View if available)
• Conduct line of sight analysis using digital terrain evaluation data (DTED)and planned flight altitudes
• Print graphics of specific NAIs• Determine launch site
INITIATE MOVEMENT• Prepare all equipment for mission
CONDUCT RECONNAISSANCE• Recon launch site• Conduct map / imagery recon of objectives
COMPLETE THE PLAN• Utilize the Mission Request Format found in APPENDIX C.• Plan flight route on PFPS/Falcon View (airspace control measures, mission
graphics, etc.)• Program above ground level (AGL) altitudes for entire flight on PFPS/Falcon
View• Submit the Mission Request (APPENDIX C)• Once the Mission Request is approved, proceed with the mission
ISSUE THE ORDER• Conduct the SUAV Mission Team Briefing
SUPERVISE• Verify grids• Sanity check all altitudes, azimuths, and distances• Triple check to ensure all equipment is loaded and inspections are completed
CONDUCT INSPECTIONS• Perform pre-combat inspections (PCIs) on vehicles• Load radios, conduct commo checks• Ensure all radios loaded with current communications security (COMSEC)
and tuned to appropriate frequencies• Setup RVT antenna and link to TOC• Ensure mission essential equipment on hand
CONDUCT REHEARSALS
24 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
APPENDIX C: MISSION REQUEST FORMAT Example (Preferred Method)
Figure 1. Mission Request Format
FOR OFFICIAL USE ONLY 25
LEADER'S GUIDE TO A2C2
APPENDIX C: MISSION REQUEST FORMAT Example
Requestor Information
Unit: _________________________________________
POC: ________________________________________
Phone: _______________________________________
Email: ________________________________________
Contact Frequency: _____________________________
Mission Purpose:____________________________________________________
Requested Name of Airspace Control Measure:____________________________
Launch Site (Grid)_____________ Recovery Site (Grid)_________________
Launch Site Altitude (MSL) _____ Recovery Site Altitude (MSL) _________
SUAV Channel _______________
Type of Measure (Shape) Mark an “X” next to type requested:
• ROZ (Circle) Grid coordinate of center point______Radius___(Nm/miles/Km)
• Route (Corridor) Enter two coordinates & width for each segment. Identify (Nm/m/km)
1.____________w:____ 5._______________w:___ 9._____________w:____
2.____________w:____ 6._______________w:___ 10._____________w:____
3.____________w:____ 7._______________w:___ 11._____________w:____
4.____________w:____ 8._______________w:___ 12._____________w:____
• Box (Can have more than 4 points.) Enter a coordinate for each corner of the shape:
1. 5. 9.
2. 6. 10.
3. 7. 11.
4. 8. 12.
Flight Altitude in AGL Minimum: __________ Maximum: ____________
DTG of Mission: Start (Launch)____________ Stop (Recovery)___________
NOTE: ZULU TIME ONLY! Zulu = Local +/- ___ Hours.
DTG Request Submitted to Battalion S-3: _______________
OFFICE USE
Battalion S-3: Reviewed By______________________________________
Sent to ADAM/BAE (POC and DTG) _______________________
Comments:
ADAM/BAE: Received By_________________________________________________
Approved/Disapproved (Circle One) By_________________________________
Sent to HHQ for inclusion in ACO (POC and DTG)_______________________
Comments:
26 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
APPENDIX C: IMMEDIATE MISSION REQUEST FORMAT:
Line 1: Unit identification (call sign and frequency)Line 2: Launch and recovery siteLine 3: ROA location (includes GPS coordinates and operating altitude)Line 4: Ingress route azimuth and distanceLine 5: Egress route azimuth and distanceLine 6: Times and durations of missionLine 7: SUAV operating channel
FOR OFFICIAL USE ONLY 27
LEADER'S GUIDE TO A2C2
APPENDIX D: RAVEN SUAV SPECIFICATIONS
System Components
• 3 air vehicles per system
• 3 payloads
• One (1) ground control unit
• Remote video terminal (RVT)
• Batteries: rechargeable
• Carry / protective cases
• Battery charger / power supply
• Field maintenance kit
Characteristics / Description:
• Power: rechargeable lithium ion battery
• Wing span: 4.5 feet
• Weight: 4.2 lbs (w/ carrying case, 12 lbs)
• GCU weight: 17 lbs
• Range: 5-12 + km
• Endurance (mins): 60-90 (lithium ion)
• Speed: 27-70 mph, cruise 30 mph
• Payload(s): high resolution, day / night
camera and thermal imagery
• Crew / Manpower: 2 Soldiers
Mission:
Army tactical-level reconnaissance, surveillance, target acquisition, and battle damage assessment
Capabilities:
• Hand-launched / AutoLand recovery
• Military P(y) - Code GPS
• Auto-navigation
• Quick assembly (< 3 min)
• Man portable / backpackable
• Quiet
• Reusable
• Typical operational altitude 150-500 ft AGL
• Climb to operational altitude in 1-2 minutes
FOR OFFICIAL USE ONLY 29
LEADER'S GUIDE TO A2C2
ACRONYMS
A2C2 Army airspace command and controlABCS Army Battle Command SystemACA Airspace Control AuthorityACM airspace control measuresACMREQ airspace control means requestsACO airspace control orderACP airspace control planADAM Air Defense Airspace ManagementAGL above ground levelALO air liaison officerAMD air and missile defenseAMPS advance mobile phone systemAO area of operationsAOR area of responsibilityATACMS Army Tactical Missile SystemATO air tasking orderATS air traffic servicesBAE Brigade Aviation ElementBAO brigade aviation officerBCD battlefield coordination detachmentBCT Brigade combat teamBDA battle damage assessmentBDZ base defense zoneBFSB battlefield surveillance brigadeBFT blue force trackingCAS close air supportCCT combat control teamCOA course of actionCOMSEC communications securityCP command postC-RAM counter-rocket, artillery, and mortarDTED digital terrain evaluation dataDTG date-time groupECOORD effects coordinatorFARP forward arming and refueling pointFBCB2 Force XXI battle command brigade and belowFEC fires and effects cellFSCM fire support coordinating measuresFSE fire support elementFSO fire support officerGCU ground control unitGPS global positioning systemIED improvised explosive deviceIFF identification, friend or foeJFACC Joint Force Air Component CommanderNAI named areas of interestPCI pre-combat inspectionsPFPS Portable Flight Planning Software
FOR OFFICIAL USE ONLY 31
LEADER'S GUIDE TO A2C2
PIR priority information requirementsROA restricted operations areasROE rules of engagementROZ restricted operations zonesRSTA reconnaissance, surveillance, and target acquisitionRTO radio-telephone operatorRVT remote video terminalSAAFR standard use Army aircraft flight routeSBCT Stryker brigade combat teamSINCGARS Single-Channel Ground and Airborne Radio SystemSUAV small unit unmanned aerial vehicleTAIS Tactical Airspace Integration SystemTOC tactical operations centerTTP tactics, techniques, and proceduresUAV unmanned aerial vehiclesUEx unit of employment, division levelUEy unit of employment, corps levelUHF ultra-high frequencyVHF very high frequencyWebACMR TAIS Webpage for Airspace Control Means and Requests
32 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED
REFERENCE LIST
JOINT PUBLICATIONSMost joint publications are online at <http://www.dtic.mil/doctrine/jel/>.
JP 1-02, DOD Dictionary of Military and Associated Terms. Available online at<http://www.dtic.mil/doctrine/jel/doddict/>.
JP 3-30, Command and Control for Joint Air Operations. 05 June 2003.
JP 3-52, Joint Doctrine for Airspace Control in the Combat Zone. 30 August2004.
Multi-Service Procedures for Integrated Combat Airspace Command and Control(ICAC2)
Multi Service Procedures for Theater Air Ground Systems (TAGS)
ARMY PUBLICATIONSMost Army publications are online at:<https://akocomm.us.army.mil/usapa/doctrine/Active_FM.html>.
AR 95-23, Unmanned Aerial Vehicle Flight Regulations. 14 May 2004.
FM 1-100, Army Aviation Operations. 21 February 1997. Will be revised asFM 3-04.100.
FM 2.0, Intelligence. 17 May 2004.
FM 3-0, Operations. 14 June 2001.
FM 3-04.111 (1-111), Aviation Brigades. 21 August 2003.
FM 3-04.300 (1-300), Flight Operations Procedures. 26 April 2004.
FM 3-04.513 (1-513), Battlefield Recovery and Evacuation of Aircraft. 27September 2000.
FM 3-52 (100-103), Army Airspace Command and Control in a Combat Zone. 1 August 2002.
FM 34-130, Intelligence Preparation of the Battlefield. 08 July 1994. (Will berevised as FM 2-01.3.)
FOR OFFICIAL USE ONLY 33
LEADER'S GUIDE TO A2C2
TC 34-212, Unmanned Aerial Vehicle Aircrew Training Manual. 27 August1997.
OTHER PUBLICATIONS
Raven Small Unmanned Aerial Vehicle Operator’s Manual. Version 2.2. February2004.
NOTE: USAAVNC DOTD is currently drafting a new Army Field Manual thatwill be the Army’s doctrine for how to fight and sustain Army UAVs. The finaldraft of this manual is scheduled for approval NLT 30 October 2005, and will beentitled: FM 3-04.155, Army Unmanned Aerial Vehicle System Operations.
34 FOR OFFICIAL USE ONLY
CENTER FOR ARMY LESSONS LEARNED