4586 Eed 03

RECORD OF AMENDMENTS
No.
Reference/date ofAmendment
Date entered
Signature
EXPLANATORY NOTES
AGREEMENT
1.
This STANAG is promulgated by the Director NATO Standardization
Agency under the authority vested in him by the NATO Standardization
Organisation Charter.
2.
No departure may be made from the agreement without informing the
tasking authority in the form of a reservation. Nations may propose changes at
any time to the tasking authority where they will be processed in the same
manner as the original agreement.
3.
Ratifying nations have agreed that national orders, manuals and
instructions implementing this STANAG will include a reference to the STANAG
number for purposes of identification.
RATIFICATION, IMPLEMENTATION AND RESERVATIONS
4.
Ratification, implementation and reservation details are available on
request or through the NSA websites (internet http://nsa.nato.int; NATO
Secure WAN http://nsa.hq.nato.int).
RESTRICTIONS TO REPRODUCTION
5.
No part of this publication may be reproduced, stored in a retrieval
system, used commercially, adapted, or transmitted in any form or by any
means, electronic, mechanical, photo-copying, recording or otherwise, without
the prior permission of the publisher. With the exception of commercial sales,
this does not apply to member nations and Partnership for Peace countries, or
NATO commands and bodies.
FEEDBACK
6.
Any comments concerning this publication should be directed to
NATO/NSA Bvd Leopold III - 1110 Brussels - Belgium.
STANAG 4586
Edition 3
NATO STANDARDISATION AGREEMENT (STANAG)
STANDARD INTERFACES OF UAV CONTROL SYSTEM (UCS) FOR NATO UAV
INTEROPERABILITY
Annexes:
A. TERMS AND DEFINITIONS

B. STANDARD INTERFACES OF UAV CONTROL SYSTEM (UCS)
FOR NATO UAV INTEROPERABILITY
AIM
1. The aim of this agreement is to promote interoperability of present and future UAV
systems in a NATO Combined/Joint Service Environment. Interoperability is required
because it will significantly enhance the war fighting capability of the forces.
Interoperability will increase flexibility and efficiency to meet mission objectives
through sharing of assets and common utilization of information generated from UAV
systems. The objective is to enable interoperability between the ground segments
(e.g., UCSs), the air segments (e.g., UAVs), and the Command, Control,
Communication, Computer and Intelligence (C4I) segments of UAV systems
operating in a NATO Combined/Joint environment. Compliance with this agreement
alone enables, but does not achieve full interoperability between various UAV
systems. Specifically, this agreement does not address platform and/or sensor
operators proficiency levels, nor does it define the CONOPs necessary to enact full
interoperability. Interoperability Levels 3-5 assume a CONOPS supporting the
operation of a UAV and/or its payload(s) by other than the organic unit responsible
for the UAV. The implementation of the specified standard UCS interfaces will also
facilitate the integration of different types of UAV systems into a NATO
Combined/Joint Service battlefield environment. The herein specified standardisation
will support interoperability of legacy as well as future UAV systems.
AGREEMENT
2. Participating nations agree to implement the standards presented herein in whole
or in part within their respective UAV systems to achieve the desired Level of
Interoperability (LOI). Ratifying nations have agreed that national orders, manuals
and instructions implementing this STANAG will include a reference to the STANAG
number for purposes of identification.
REFERENCE DOCUMENTS:
3. The following Standardisation Agreements (STANAGs), Military Standards (MILSTDs), International Telecommunication Union (ITU) Recommendations and
International Standards (ISs) contain provisions which, through references in this
text, constitute provisions of this STANAG. At the time of publication, the editions
indicated were valid. All recommendations and standards are subject to revision, and
parties to agreements based on this STANAG are encouraged to investigate the
possibility of applying the most recent editions of the STANAGs, MIL-STDs, ICAO
Documents, ITU Recommendations and ISs listed below. NATO Standardisation
Agency (NSA) maintains registers of currently valid STANAGs.
AAP-6 NATO GLOSSARY OF TERMS AND DEFINITIONS (ENGLISH AND FRENCH)
AEDP-2 - NATO ISR Interoperability Architecture
AEDP-4 - STANAG 4545, NATO Secondary Imagery Format (NSIF) Implementation
Guide
vi
STANAG 4586
Edition 3
Comit Consultatif International Tlphonique et Tlgraphique (CCITT) v.42bis
Modem standard for error correction and compression at speeds of 28.8 kbps
Common Route Definitions (CRD ICD 2.0.2.0)
Digital Feature Analysis Data (DFAD)
ECMA Script scripting language (ECMA Script 262)
Electronic Industry Association (EIA) RS-170
File Transfer Protocol (FTP), IETF, RFC 959
Hypertext Transfer Protocol (HTTP) Version 1.1, IETF RFC 2616
ICAO document - Rules of the Air and Air Traffic Services, Doc 4444-RAC/501
Institute of Electrical and Electronics Engineers, Inc.(IEEE) Network Standards - 802
Internet Protocol (IP) (IPv4 (RFC 791, 792, 919,922, 1112))
IPv6 (RFC 2460-4, 2375, 2236)
ISO/DIS 9241-3 - Visual Display Requirements
ISO/DIS 9241-8 - Requirements for Displayed Colours
ISO/Work Doc 9241-9 - Non-Keyboard Input Devices
ISO/DIS 9241-10 - Dialogue Principles
ISO/Work Doc 9241-12 - Presentation of Information
ISO/CD 9241-13 - User Guidance
ISO/DIS 9241-14 - Menu Dialogues
ISO/CD 9241-16 - Direct Manipulation Dialogues
ISO/CD 13406-2 - Flat Panel Displays
International Organisation for Standardization/International Electro technical Commission
ECMAScript Language Specification - ISO/IEC 16262
MIL-STD-2401 - World Geodetic System 84 (WGS 84)
MISB STD 0102 Security Metadata Universal and Local Sets for Digitial Motion
Imagery
MISB STD 0601 UAS Data Link Local Metadata Set
MISB STD 0902 MISB Minimum Metadata Set
NATO Interoperability Standards and Profiles (NISP)
NATO Data Policy 2000 12.20-00
Network Time Protocol (V3), April 9, 1992, NTP (RFC-1305)
SMPTE 336M
Society of Motion Picture and Television Engineers (SMPTE) 170 M
STANAG 1059 Letter Codes for Geographical Entities Edition 8
STANAG 2019 APP-6(B) Joint Symbology
STANAG 3150 Uniform System of Supply Classification
STANAG 3151 Uniform System of Item Identification
STANAG 3377 AR (Edition 6) Air Reconnaissance Intelligence Report Forms
STANAG 3809 Digital Terrain Elevation Data (DTED) Geographic Information Exchange
Standard
STANAG 4250 NATO Reference Module for Open Systems Interconnection - Part 1
General Description
STANAG 4545 NATO Secondary Imagery Format (NSIF)
vii
STANAG 4586
Edition 3
STANAG 4559 NATO Standard Image Library Interface (NSILI)
STANAG 4575 NATO Advanced Data Storage Interface (NADSI)
STANAG 4607 NATO Ground Moving Target Indicator (GMTI) Format
STANAG 4609 NATO Motion Imagery Standard
STANAG 5500 Concept of NATO Message Text Formatting System (CONFORMETS)
ADatP-3(A)
STANAG 7023 Air Reconnaissance Primary Imagery Data Standard
STANAG 7024 Imagery Air Reconnaissance Tape Recorder Standards
STANAG 7074 Digital Geographic Information Exchange Standard (DIGEST)
STANAG 7085 Interoperable Data Links for Imaging Systems
STANAG 7149 NATO Message Catalogue (NMC) APP 11(C)
STDI-0002, National Imagery and Mapping Agency, The Compendium of Controlled
Extensions (CE) for the National Imagery Transmission Format (NITF), CMETAA
Support Data Extension.
Transmission Control Protocol (TCP) (IETF STD 7) RFC 793 (TCP)
User Datagram Protocol (UDP) (IEN 88, RFC 768, 1122)
DEFINITIONS
4. The terms and definitions used in this document are listed in Annex A.
GENERAL
5. The outline of this STANAG follows the following format:
Annex A contains the Terms and Definitions used in the STANAG.

Annex B provides a top level description of the objectives and the
approach taken to achieve UAV Systems Interoperability through
standardising the interfaces between the Core UCS (CUCS) and the
air vehicle, and the CUCS and the external C4I Systems. It also
specifies the Human Computer Interface (HCI) requirements that the
CUCS shall provide to the UAV system operator. It describes the
requirement for a standard functional UCS Architecture to
accommodate those interfaces and refers to the Appendices B1 B3
that contain the details of the standards required by STANAG 4586. It
also lists other STANAGs, standards and protocols that are required
for achieving UAV systems interoperability and offers some
considerations for their implementation.
DETAILS OF AGREEMENT
6. STANAG 4586 defines the architectures, interfaces, communication protocols,
data elements, message formats and identifies related STANAGs that compliance
with is required to operate and manage multiple legacy and future UAVs in a complex
NATO Combined/Joint Services operational environment. The UCS Architecture
encompasses the CUCS to handle UAV common/core processes, the Data Link
Interface (DLI) to enable operations with legacy as well as future UAV systems, the
Command Control Interface (CCI) for UAV and UAV payload data dissemination to
support legacy and evolving NATO C4I systems and architectures, and the HCI
requirements to support the interface to the UAV system operators. Five LOIs are
defined to accommodate operational requirements. This version of the STANAG
viii
STANAG 4586
Edition 3
contains the messages which support the Electro-Optical/Infra-Red (EO/IR),
Synthetic Aperture Radar (SAR), Communications Relay, and Stores (e.g., weapons,
payloads, etc.) across the DLI. As additional payloads are defined, the STANAG will
be updated accordingly to incorporate those payloads. The CCI utilizes applicable
messages from the NATO Message Catalogue, APP-11. In addition, this STANAG
supports the NATO Air Force Armaments Group (NAFAG) NATO ISR Interoperability
Architecture (NIIA) in that it invokes compliance with the NIIA specified standards.
PROTECTION OF PROPRIETARY RIGHTS
7. If required.
IMPLEMENTATION OF THE AGREEMENT
8. This STANAG is implemented by a nation when it has issued instructions that all
such equipment procured for its forces will be manufactured in accordance with the
characteristics detailed in this agreement.
CHANGES TO EDITION 3
9. Based on further analysis by the Joint Capability Group UAV (JCGUAV)
Specialist Team (ST) and feedback from national programs and industries supporting
development of UAV systems, changes to Edition 2 have been identified, analyzed,
and agreed to by the ST. The changes fall into the following areas:
The definition of Level of Interoperability 2 (LOI 2) has been revised/clarified
to be applicable to the case where the sensor data is received in digital format
with embedded metadata in accordance with the appropriate STANAG (e.g.,
STANAG 4609). DLI related sensor data may optionally be supported.
The definition of Level of Interoperability 3 (LOI 3) now states Control and
monitoring of the UAV payload unless specified as monitor only.
monitoring of the UAV, unless specified as monitor only, less launch and
recovery.
monitoring of UAV launch and recovery unless specified as monitor only.
In order to reduce the required data link bandwidth requirements for
communication between the UCS and the air vehicle, the messages have
been modified to:
o Add a potential presence vector (applicable to each field in the
message)
o The message data elements type and units have been changed to a
more efficient form (e.g., from floating point to a scaled integer value)
Messages have been added to support a greater level of air vehicle
(AV)/VSM autonomy than was possible in Edition 2
Addition of references referring to MISB Standards for the minimum set of
Key Length Value (KLV) metadata implementation requirements
Addition of updated messages for STANAG 7085 compliant data link set-up,
control and monitoring
Interoperable mission planning via extensions to the Common Route
Definition (CRD)
Technical and administrative errors have been corrected and editorial
changes to clarify requirements
In addition, to facilitate interoperability with systems that are compliant with STANAG
4586 Edition 2, data elements were structured so as to allow direct mapping of data
ix
STANAG 4586
Edition 3
elements between Edition 3 and Edition 2 formats. This mapping may be
accomplished by a software application which can be hosted in the UCS or the UAV.
This capability will result in interoperability between STANAG 4586 Edition 2 and
Edition 3 system components (e.g., UCS and/or UAV).
STANAG MAINTENANCE AND UPDATE
10. STANAG 4586 will be maintained and updated to correct any latent errors, add
improvements from lessons learned, and incorporate new requirements by the
STANAG Custodian, supported by a multinational Custodian Support Team (CST).
The STANAG has a high degree of continuing attention from the CST. As new
editions are published, feedback is being collected on a continuing basis for follow-on
editions. That experience gained in implementation is highly valued by the CST and
should be forwarded to the STANAG 4586 Custodian, Mr. Shawn R. Murray, PEO
(U&W) CSI, e-mail: [email protected].
ANNEX A to
STANAG 4586
Edition 3
ANNEX A
TERMS AND DEFINITIONS
1
Acronyms and Abbreviations.
purpose of this agreement.
A
ACCS
Accel
ACK
ACM
ACO
ADatP-3
AGL
AMPS
ANSI
AOA
AOI
AP
API
ASCII
ASM
ASW
ATC
ATP
ATR
ATS
AV
AVC
B
BDA
BER
BIT
BDRVT
BITE
BLOS
BOM
C
C2
C4I
CBIT
CBRN
CCI
CCISM
The following acronyms are used for the
Army Command and Control System (US)/Air Command and

Control System (NATO)
Acceleration
Acknowledge
Airspace Control Means
Airspace Control Order
Allied Data Publication 3
Above Ground Level
Aviation Mission Planning System
American National Standards Institute
Angle Of Attack
Area Of Interest
Allied Publication/Alliance Publication
Application Program(ming) Interface
American Standard Code for Information Interchange
Air Space Management
Anti-Submarine Warfare
Air Traffic Control
Allied Tactical Publication
Automatic Target Recognition
Air Traffic Services
Air Vehicle
Air Vehicle Control
Battle Damage Assessment
Bit Error Rate
Built-in-Test
Bi-Directional Remote Video Terminal
Built-in-Test Equipment
Beyond Line of Sight
Bit-Oriented Message
Command and Control
Command, Control, Communications, Computers and Intelligence
Continuous Built-in-Test
Chemical, Biological, Radiological and Nuclear
Command & Control Interface
Command and Control Interface Specific Module
A-1
ANNEX A to
STANAG 4586
Edition 3
CDL
CDT
CEN
CEP
CFOV
CG
CGS
CIRC
CJTF
CL
Cm
CO
COE
CONOPS
COP
CORBA
COTS
CR
CRD
CRT
CUCS
D
DC
DCE
DCM
DIGEST
DII
DII/COE
DIN
DL
DLI
DoD
DTED
E
ECM
EIA
EIA/IS
ELINT
EMCON
EO
EO/IR
EP
Common Data Link

Control Data Terminal
European Standardisation Organisation
Circular Error Probability
Centre Field of View
Centre of Gravity
Common Ground Segment/Common Ground Station/Common
Ground System
Circular
Combined Joint Task Force
Connectionless
Centimetres
Connection Oriented
Common Operating Environment
Concept of Operations
Common Operational Picture
Common Object Request Broker Architecture
Commercial-Off-The-Shelf
Communications Relay
Common Route Definition
Cathode Ray Tube
Core UAV Control System
Direct Current
Distributed Computing Environment
Data Link Control Module
Digital Geographic Information Exchange Standard
Defence Information Infrastructure
Defence Information Infrastructure/Common Operating
Environment
Deutsche Institut fur Normung
Data Link
Data Link Interface
Department of Defence
Digital Terrain Elevation Data
Electronic Counter Measures
Electronic Industries Association
EIA Interim Standard
Electronic Intelligence
Emission Control
Electro-Optical
Electro Optical/Infrared
External pilot
A-2
ANNEX A to
STANAG 4586
Edition 3
ERF
ERS
ESM
ETA
ETSI
EW
F
FLIR
FOB
FOV
FT
FTP
G
GMT
GMTI
GOTS
GPS
GUI
H
HALE
HCI
HF
HSI
HL
HTML
HTTP
Hz
I
I/O
IA
ICAO
ID
IDD
IEA
IEC
IEEE
IER
IES
IETF
IFF
IL
INS
IP
Ego-Referenced Frame
Emergency Recovery System
Electronic Support Measures
Estimated Time of Arrival
European Telecommunications Standards Institute
Electronic Warfare
Forward Looking Infrared
Forward Operations Base
Field of View
Flight Termination
File Transfer Protocol
Greenwich Mean Time
Ground Moving Target Indicator
Government Off-The-Shelf
Global Positioning System
Graphical User Interface
High Altitude, Long Endurance
Human Computer Interface
High Frequency
Hyperspectral Imagery
Hand Launched
Hyper Text Mark-up Language
Hypertext Transfer Protocol
Hertz, cycles per second
Input/Output
International Agreement
International Civil Aviation Organisation
Identification
Interface Design Description/Interface Definition Document
Information Exchange Agreements
International Enterprise Committee/International Electro technical
Commission
Institute of Electrical and Electronics Engineers
Information Exchange Requirements
Imagery Exploitation System
Internet Engineering Task Force
Identification Friend or Foe
Image Library
Inertial Navigation System
Internet Protocol/Internal Pilot
A-3
ANNEX A to
STANAG 4586
Edition 3
IPS
IPX
IR
IRS
ISAR
ISDN
ISG
ISO
ISO/CD
ISO/DIS
ISR
ISTAR
ITDP
ITU
ITU-T(SB)
J
JFACC
JFC
JPEG
JSH
JSWG
JTA
JTF
JTFC
K
Kilo
KLV
Km
L
L&R
L-16
LIDAR
LAN
LAS
LB
LCD
LOI
LOS
LRF
LSB
M
MAV
Mb
Image Print Services

NetWare Transport Protocol
Infrared
Interface Requirements Specifications
Inverse Synthetic Aperture Radar
Integrated Services Digital Network
Industry Support Group
International Organisation for Standardisation
Committee Draft of ISO
Draft International Standard of ISO
Intelligence, Surveillance, Reconnaissance
Intelligence, Surveillance, Target Acquisition and Reconnaissance
International Technology Demonstration Program
International Telecommunication Union
International Telecommunications Union Telecommunications
(Standardisation Bureau)
Joint Force Air Component Commander
Joint Force Commander
Joint Photographic Experts Group
JASA Standards Handbook
JASA Standards Working Group
Joint Technical Architecture
Joint Task Force
Joint Task Force Commander
1,000
Key Length Value
Kilometres
Launch and Recovery
Link-16 (TADIL-J message standard)
Light Detection And Ranging
Local Area Network
Local Access Subsystem
Land-Based
Liquid Crystal Display
Level of Interoperability
Line of Sight
Laser Range Finder
Least Significant Bit
Micro Air Vehicle
Megabit
A-4
ANNEX A to
STANAG 4586
Edition 3
MB
Mb/s
MB/s
Met
MGRS
MIJI
MIL
MIL-STD
MIME
MIN
MMP
MMS
MOA
MOTS
MOU
MP
MPEG
MPO
MPS
MSE
Msg
MSI
MSK
MSL
MTF
MTI
MUM
N
N/A
NATO
NCIS
NCOE
Near RT
NED
NIIA
NIMP
NIIRS
NIPD
NISP
NITF
NITFS
Nm
NNAG
NOSIP
Megabyte
Megabits per second
Megabytes per second
Meteorological
Military Grid Reference System
Meaconing, Intrusion, Jamming, and Interference
Military
Military Standard
Multipurpose Internet Mail Extension
Minimum
Modular Mission Payload
Manufacturing Messaging Specification
Memorandum of Agreement
Military Off-The-Shelf
Memorandum of Understanding
Mission Planning/Mission Planner
Motion Pictures Experts Group
Mission Planning Operator/Mission /Payload Operator
Metres per second
Mobile Subscriber Equipment
Message
Multi-Spectral Imagery
Minimum Shift Keying
Mean Sea Level
Message Text Format
Moving Target Indicator
Manned Unmanned
Not Applicable
North Atlantic Treaty Organisation
NATO Common Interoperability Standards
NATO Common Operating Environment
Near Real Time
NATO Effective Date
NATO ISR Interoperability Architecture
NATO Interoperability Management Plan
National Imagery Interpretation Rating Scale
NATO Interoperability Planning Document
NATO Interoperability Standards and Profiles
National Imagery Transmission Format
National Imagery Transmission Format Standard
Nanometre
NATO Naval Armaments Group
NATO Open System Interconnection Profile
A-5
ANNEX A to
STANAG 4586
Edition 3
NOTS
NRT
NSA
NSE
NSIF
NSIL
NSILI
NSR
NTF
NTIS
NTSC
O
OPFOR
OPS
OSE
OSI
OTH
OTH-T
P
PDF
PDU
PG/35
PO
Pyld
Q
QoS
R
Rad
RAID
RECEXREP
RF
RFC
ROS
RP
Rpt
RT
RTP
Rx
S
SA
SALUTE
SAR
SATCOM
SB
NATO Off-The-Shelf
Non-Real Time
NATO Standardisation Agency
Non Standard Equipment
NATO Secondary Imagery Format
NATO Standard Image Library
NATO Standard Image Library Interface
NATO Staff Requirements
Network File Server
NATO Technical Interoperability Standards
National Transmission Standards Committee
Opposing Force
Operations
Open System Environment
Open System Interconnection (model)
Over The Horizon
Over The Horizon Targeting
Portable Document Format
Power Distribution Unit
Project Group 35
Payload Operator
Payload
Quality of Service
Radians
Redundant Array of Inexpensive/Independent Disks
Reconnaissance Exploitation Report
Radio Frequency
Request for Comment
Relief on Station/Rules of Safety
Route Plan
Report
Real Time
Real Time Protocol/ Real Time Processor
Receive
Situational Awareness
Size, Activity, Location, Unit, Time, Equipment
Synthetic Aperture Radar/Search And Rescue
Satellite Communications
Sea-based
A-6
ANNEX A to
STANAG 4586
Edition 3
SEC
SED
SIGINT
SINCGARS
SMPTE
SMTP
SNR
ST
STANAG
T
TBD
TCDL
TCP/IP
Tgt
TV
TX
U
UAV
UB
UCAV
UCT
UDP
UES
UHF
UI
UJTL
UPS
URL
USIS
UTC
UTM
V
VCR
VDL
VDU
VDT
VHF
VMAP
VSM
W
WAN
WAS
WGS-84
WIMP
Seconds
Signal External Descriptor
Signals Intelligence
Single Channel Ground and Airborne Radio System
Society of Motion Picture and Television Engineers
Simple Mail Transfer Protocol
Signal to Noise Ratio
Specialist Team
(NATO) Standardisation Agreement
To Be Defined
Tactical Common Data Link
Transfer Control Protocol/Internet Protocol
Target
Television
Transmit
Unmanned Aerial Vehicle/Uninhabited Aerial Vehicle
Unified Build
Unmanned/ Uninhabited Combat Aerial Vehicle
Universal Coordinated Time
User Datagram Protocol
UAV Exploitation System
Ultra High Frequency
User Interface
Universal Joint Task List
Uninterruptible Power Supply
Uniform Resource Locator
United States Imagery Standards
Universal Time Coordinated
Universal Transverse Mercator
Video Cassette Recorder
VHF Data Link
Visual Display Unit
Vehicle Data Terminal
Very High Frequency
Vector Map
Vehicle Specific Module
Wide Area Network
Wide Area Subsystem
World Geodetic System 84
Windows, Icons, Mouse and Pull-down/pop-up (menus)
A-7
ANNEX A to
STANAG 4586
Edition 3
WP
WRF
X
XML
Y
Z
Waypoint
World-Referenced Frame
Extensible Mark-up Language
A-8
ANNEX A to
STANAG 4586
Edition 3
2. Terms and Definitions. The following terms and definitions are used for the
purpose of this agreement.
Advisories
Air
Reconnaissance
Air Traffic Control
(ATC)
Air Vehicle (AV)

Aircraft Handover
Alert
Allied Data
Publication 3
(ADatP-3)
Altitude
Analysis
Automated Take-off
and Landing
Battle Damage
Assessment (BDA)
Byte
Cassette
Cautions
An alert that requires crew awareness but not immediate

awareness nor immediate attention.
The collection of information of intelligence interest either by visual
observation from the air or through the use of airborne sensors.
A service provided for the purposes of: a) preventing collisions
between aircraft and in the manoeuvring area between aircraft and
obstructions; and b) expediting and maintaining an orderly flow of
air traffic.
The core platform consisting of all flight relevant subsystems but
without payload and data link.
The process of transferring control of aircraft from one controlling
authority to another.
A signal or combination of signals that informs the aircrew of the
existence of a warning, caution, or advisory condition, and may
inform the aircrew of the nature of the warning, caution, or advisory
condition.
Refer to STANAG 7149 NATO Message Catalogue (NMC) APP
11(B)
The vertical distance of a level, a point or an object considered as a
point, measured from mean sea level. The terms most relevant to
UAV operations are:
Absolute Altitude: The height of an aircraft directly above the
surface or terrain over which it is flying.
Critical Altitude: The altitude beyond which an aircraft or airbreathing guided missile ceases to perform satisfactory.
True Altitude: The height of an aircraft as measured from
mean sea level.
The study of a whole by examining its parts and their interactions.
Note: In the context of military forces, the hierarchical relationship in
logical sequence is: assessment, analysis, evaluation, validation
and certification.
The ability of the AV to be launched with a single command once
planning and pre-flight has been conducted and permission to
launch has been granted. Includes releasing the AV from a securing
device and flight of the AV to the first waypoint and the ability to
land and secure the AV with a single command once the air vehicle
has been stationed at a gate position no closer than 100 metres to
the landing spot.
The assessment of effects resulting from the application of military
action, either lethal or non-lethal, against a military objective.
Eight bits.
In photography, a reloadable container for either unexposed or
exposed sensitised materials which may be removed from the
camera or darkroom equipment under lighted conditions.
An alert indicating a potentially dangerous condition requiring
immediate crew awareness but not immediate action.
A-9
Certification
Chemical
Monitoring
Classification
Command and
Control
Command Control
Interface (CCI)
Command and
Control Interface
Specific Module
(CCISM)
Command and
Control Information
System
Commonality
Communications
Plan
Compatibility
Component
Compression
Concept of
Operations
ANNEX A to
STANAG 4586
Edition 3
The process of officially recognizing that organizations, individuals,
materiel or systems meet defined standards or criteria. Note: In the
context of military forces, the hierarchical relationship in logical
sequence is: assessment, analysis, evaluation, validation and
certification.
The continued or periodic process of determining whether or not a
chemical agent is present.
The ability to determine unique characteristics about a contact,
which allow the differentiation of military and commercial contacts
and determination of contact class and type.
The exercise of authority and direction by a properly designated
commander over assigned forces in the accomplishment of a
mission.
The interface between the UCS Core and the external C4I systems.
It specifies the data requirements that should be adopted for
communication between the UCS Core and all C4I end users
through a common, standard interface.
Conversion software and/or hardware between the CCI and
incompatible C4I systems. May form part of a particular UCS
implementation to establish a connection between the UCS and
specific customers of the UAV system (i.e. one or more C4I
systems). Can range in complexity from a simple format or protocol
translator to a user-specific application to adapt the type of
information to C4I requirements.
An integrated system comprised of doctrine, procedures,
organisational structure, personnel, equipment, facilities and
communications which provides authorities at all levels with timely
and adequate data to plan, direct and control their activities.
The state achieved when the same doctrine, procedures or
equipment are used.
The overarching plan which covers all communication aspects.
Includes the Data Link Plan.
The suitability of products, processes or services for use together
under specific conditions to fulfil relevant requirements without
causing unacceptable interactions.
In logistics, a part or combination of parts having a specific function,
which can be installed or replaced only as an entity.
The ability to transmit the same amount of data in fewer bits. There
are a variety of data compression techniques, but only a few have
been standardized. The CCITT has defined a standard data
compression technique for transmitting faxes (Group 3 standard)
and a compression standard for data communications through
modems (CCITT V.42bis). In addition, there are file compression
formats, such as ARC and ZIP. Data compression is also widely
used in backup utilities, spreadsheet applications, and database
management systems. Certain types of data, such as Bitmapped
graphics, can be compressed to a small fraction of their normal
size.
A clear and concise statement of the line of action chosen by a
commander in order to accomplish his mission.
A - 10
Continuous Strip
Imagery
Controlled Airspace
Control Data
Terminal
Core UCS (CUCS)
Countermeasures
Damage
Assessment
Data
Communication
Data Link
Data Link Interface
(DLI)
Data Link Plan
Dispensing
Payloads
Electromagnetic
Spectrum
Electronic Warfare
(EW)
Emergency
Recovery Plan
ANNEX A to
STANAG 4586
Edition 3
Imagery of a strip of terrain in which the image remains unbroken
throughout its length, along the line of flight.
An airspace of defined dimensions within which air traffic control
service is provided to controlled flights (e.g., flights within controlled
airspace require approval by/coordination with the controlling
authority, and certain manoeuvres may be prohibited or restricted,
or require supervision).
The data link element consists of the Vehicle Data Terminal (VDT)
in the air vehicle and the Control Data Terminal (CDT) that can be
located either on the ground or in the air (e.g., Command and
Control aircraft). Connectivity between the CDT and VDT is
prerequisite for Level 2, 3, 4, and 5 interoperability.
Provides the UAV operator with the functionality to conduct all
phases of a UAV mission. It shall support the requirements of the
DLI, CCI, and HCI. Also provides a high resolution, computer
generated, graphical user capability that enables a qualified UAV
operator the ability to control different types of UAVs and payloads.
That form of military science that, by the employment of devices
and/or techniques, has as its objective the impairment of the
operational effectiveness of enemy activity.
The determination of the effect of attacks on targets.
The transfer of information between functional units by means of
data transmission according to a protocol.
The means of connecting one location to another for the purpose of
transmitting and receiving data.
The interface between the Vehicle Specific Module (VSM) and the
UCS core element. It provides for standard messages and formats
to enable communication between a variety of air vehicles and
NATO standardised control stations.
The details of the available link including the band and frequencies
to be used. It is associated with waypoints within the route and the
details of required actions made available for cueing the operator.
Objects that are released from the UAV as part of the UAV mission
objectives. This can include the release of weapons or deployment
of remote sensors, etc.
The range of frequencies of electromagnetic radiation from zero to
infinity.
Military action to exploit the electromagnetic spectrum
encompassing: the search for, interception and identification of
electromagnetic emissions, the employment of electromagnetic
energy, including directed energy, to reduce or prevent hostile use
of the electromagnetic spectrum, and actions to ensure its effective
use by friendly forces.
In case of failures such as data link loss, UAVs need to
automatically carry out recovery actions referred to as Rules of
Safety (ROS). The ROS are selected at the mission planning stage.
The ROS differ according to the priority given to emergency action
relative to that given to mission execution. Using the mission
planning application the UCS operator selects the appropriate
safety scenario (e.g., to define a pre-programmed recovery route).
A - 11
Encoding
Exercise
Field of View
Formatted
Message Text
Frame
Free Form
Message Text
Functional
Architecture
Fusion
Handover
Human Computer
Interface (HCI)
Hyperspectral
Imagery (HSI)
Image
Imagery
Imagery
Exploitation
ANNEX A to
STANAG 4586
Edition 3
Converting information or data from a system, format or signal to
another.
A military manoeuvre or simulated wartime operation involving
planning, preparation, and execution.
It is carried out for the
purpose of training and evaluation. It may be a combined, joint, or
single Service exercise, depending on participating organisations.
In photography, the angle between two rays passing through the
perspective Centre (rear nodal point)) of a camera lens to the two
opposite sides of the format. Not to be confused with angle of view.
Words composed of several sets ordered in a specified sequence,
each set characterized by an identifier and containing information of
a specified type, coded and arranged in an ordered sequence of
character fields in accordance with the NATO message text
formatting rules. It is designed to permit both manual and
automated handling and processing.
In photography, any single exposure contained within a continuous
sequence of photographs.
Words without prescribed format arrangements. It is intended for
fast drafting as well as manual handling and processing.
Establishes the following functional elements and interfaces:
Core UCS (CUCS)
Data Link Interface (DLI)
Command and Control Interface (CCI)
Vehicle Specific Module (VSM)
Command and Control Interface Specific Module
(CCISM)
The blending of intelligence and/or information from multiple
sources or agencies into a coherent picture. The origin of the initial
individual items should then no longer be apparent.
The act of passing control of a UAV and/or a payload from one UCS
to another UCS and/or transferring of data link control.
Definitions of the requirements of the functions and interactions that
the UCS should allow the operator to perform. Will support any HCI
requirements that are imposed on the CUCS by the Command and
Control Interface (CCI) and Data Link Interface (DLI). Will also
support any specific or unique CCI Specific Module (CCISM) or
Vehicle Specific Module (VSM) display requirements.
The image of an object obtained simultaneously using hundreds or
thousands of discrete spectral bands.
A two-dimensional rectangular array of pixels indexed by row and
column.
Collectively, the representations of objects reproduced
electronically or by optical means on film, electronic display
devices, or other media.
The cycle of processing and printing imagery to the positive or
negative state, assembly into imagery packs, identification,
interpretation, mensuration, information extraction, the preparation
of reports and the dissemination of information.
A - 12
Integration
Intelligence
Interaction
Interface
Interoperability
Joint
Laser Designator
Laser RangeFinder
Level of
Interoperability
(LOI)
LIDAR
Mission Plan
Meaconing
Message Text
Format (MTF)
ANNEX A to
STANAG 4586
Edition 3
In intelligence usage, a step in processing phase of the intelligence
cycle whereby analyzed information and/or intelligence is selected
and combined into a pattern in the course of the production of
further intelligence. Related term: intelligence cycle.
The product resulting from the processing of information concerning
foreign nations, hostile or potentially hostile forces or elements, or
areas of actual or potential operations. The term is also applied to
the activity which results in the product and to the organisations
engaged in such activity.
A one or two-way exchange of data among two or more
systems/sub-systems.
(1) A concept involving the definition of the interconnection between
two equipment items or systems. The definition includes the type,
quantity, and function of the interconnecting circuits and the type,
form, and content of signals to be interchanged via those circuits.
Mechanical details of plugs, sockets, and pin numbers, etc., may be
included within the context of the definition. (2) A shared boundary,
(e.g., the boundary between two subsystems or two devices). (3) A
boundary or point common to two or more similar or dissimilar
command and control systems, subsystems, or other entities
against which or at which necessary information flow takes place.
(4) A boundary or point common to two or more systems or other
entities across which useful information flow takes place. (It is
implied that useful information flow requires the definition of the
interconnection of the systems which enables them to interoperate.)
(5) The process of interrelating two or more dissimilar circuits or
systems. (6) The point of interconnection between user terminal
equipment and commercial communication-service facilities.
The ability to operate in synergy in the execution of assigned tasks.
Adjective used to describe activities, operations and organisations
in which elements of at least two services participate.
A device that emits a beam of laser energy which is used to mark a
specific place or object.
A device that uses a laser to determine the distance from the device
to a place or object.
A method for describing the ability of UAS to be interoperable for
basic types of UAS functions. This measure is applied for the DLI
and CCI capabilities.
An acronym of Light Detection And Ranging, describing systems
that use a light beam in place of conventional microwave beams for
atmospheric monitoring, tracking and detection functions.
The route planning, payload planning, data link planning (including
frequency planning), and UAV emergency recovery planning (rules
of safety) for a A/V.
A system of receiving radio beacon signals and rebroadcasting
them on the same frequency to confuse navigation. The meaconing
stations cause inaccurate bearings to be obtained by aircraft or
ground stations.
Fixed format, character-oriented messages which are man-readable
and machine processable. MTFs are described in accordance with
ADatP-3. Agreed NATO MTFs are published in APP-11.
A - 13
Metadata
Mission Plan
Modularity
Motion Imagery
Moving Map
Display
Moving Target
Indicator (MTI)
Multispectral
Imagery (MSI)
National
Transmission
Standards
Committee (NTSC)
Native System
NATO
Interoperability
Standards and
Profiles (NISP)
NATO ISR
Interoperability
Architecture (NIIA)
NATO
Standardisation
Agreement (NATO
STANAG)
ANNEX A to
STANAG 4586
Edition 3
Data about data. The term is normally understood to mean
structured data about resources that can be used to help support
resource description and discovery, the management of information
resources (e.g., to record information about their location and
acquisition), long-term preservation management of digital
resources, and for help to preserve the context and authenticity of
resources.
Might be technical in nature, documenting how
resources relate to particular software and hardware environments
or for recording digitisation parameters. In short, any kind of
standardised descriptive information about resources, including
non-digital ones.
The route planning, payload planning, data link planning (including
frequency planning), and UAV emergency recovery planning (rules
of safety) for a UAV flight.
Use of sub-systems or components from one system to function
properly as part of another system.
The interface at the subsystem level is sufficiently defined.
A sequence of images, with metadata, which are managed as a
discrete object in standard motion imagery format and displayed as
a time sequence of images.
A display in which a symbol, representing the vehicle, remains
stationary while the map or chart image moves beneath the symbol
so that the display simulates the horizontal movement of the vehicle
in which it is installed. Occasionally the design of the display is such
that the map or chart image remains stationary while the symbol
moves across a screen.
A radar presentation which shows only targets which are in motion.
Signals from stationary targets are subtracted out of the return
signal by the output of a suitable memory circuit.
The image of an object obtained simultaneously in a number of
discrete spectral bands.
The first colour TV broadcast system was implemented in the
United States in 1953. This was based on the NTSC standard.
NTSC is used by many countries on the North American continent
and in Asia including Japan. This U.S. video standard uses EIA RS170 and SMPTE 170 M 1994 formats. The standard applies to
imagery with metadata in either closed caption overlays or encoded
via closed caption. NTSC runs on 525 lines/frame and 30
frames/second with 2:1 interlace.
All components which compose a unique UAV system.
Provides the necessary guidance and technical components to
support project implementations and transition to a NATO Network
Enabled Capability (NNEC).
The architecture that defines the STANAGs used for ISR sensor
system interoperability. This architecture is defined in AEDP-2.
A normative document recording an agreement among several or
all NATO member nations that has been ratified at the authorized
national level, to implement a standard, in whole or in part, with or
without reservation.
A - 14
Near Real Time
Network
Open Systems
Interconnect Model
Order of Battle
Passive
Payload
Payload Plan
Primary Data
Primary Imagery
Processed Imagery
Protocol
Real Time
ANNEX A to
STANAG 4586
Edition 3
Pertaining to the timeliness of data or information which has been
delayed by the time required for electronic communication and
automatic data processing.
This implies that there are no
significant delays.
(1) An interconnection of three or more communicating entities and
(usually) one or more nodes. (2) A combination of passive or active
electronic components that serves a given purpose.
This model is defined in ISO/IEC 7498-1.
The identification, strength, command structure, and disposition of
the personnel, units, and equipment of any military force.
In surveillance, an adjective applied to actions or equipment which
emits no energy capable of being detected.
UAV sensor(s), weapons, chaff, pamphlets, onboard systems, etc.
carried onboard which are used to accomplish a specified mission.
Details of the sensor to be used, or which sensors are to be loaded
if multiple payloads are within the UAV capability. At specific points
along a route there may be pre-planned sensor operations and the
details of these have to be incorporated into the payload plan and
associated with waypoints in the route. Available as hard copy for
UAV payload loading and for display with or along side the route
plan, action cueing has to be incorporated either for the operator or
the UAV depending on system sophistication.
Includes payload configuration (e.g., payload type and lens size),
payload imagery extraction (e.g., desired resolution), and operator
commands for controlling both EO/IR and SAR payloads (e.g.,
zoom settings, depression angle, and focus).
Data directly received from the sensor.
Unexploited, original imagery data that has been derived directly
from a sensor. Elementary processing may have been applied at
the sensor, and the data stream may include auxiliary data.
Imagery that has been formatted into image pixel format, enhanced
to remove detected anomalies and converted to a format
appropriate for subsequent disposition.
(1) [In general], A set of semantic and syntactic rules that
determine the behaviour of functional units in achieving
communication.
For example, a data link protocol is the
specification of methods whereby data communication over a data
link is performed in terms of the particular transmission mode,
control procedures, and recovery procedures. (2) In layered
communication system architecture, a formal set of procedures that
are adopted to facilitate functional interoperation within the layered
hierarchy. Note: Protocols may govern portions of a network, types
of service, or administrative procedures.
Pertaining to the timeliness of data or information that has been
delayed only by the time required for electronic communication.
This implies that there are no noticeable delays.
A - 15
Reconnaissance
Recovery
Resolution
Route Plan
Scalability
Search and Rescue
Secondary Imagery
Sensor
Shall
Should
Signals Intelligence
Software
STANAG
Standardization
Storage
Surveillance
ANNEX A to
STANAG 4586
Edition 3
A mission undertaken to obtain, by visual observation or other
detection methods, information about the activities and resources of
an enemy or potential enemy, or to secure data concerning the
meteorological, hydrographic, or geographic characteristics of a
particular area.
In air operations, that phase of a mission which involves the return
of an aircraft to a base.
A measurement of the smallest detail which can be distinguished by
a sensor system under specific conditions.
A set of waypoints for the UAV to follow, as well as general air
vehicle commands for auxiliary systems (e.g., lights, IFF, de-icing,
etc.) and emergency operation commands. Taxi or flight patterns
may be incorporated into the route either as a series of sequenced
waypoints or as seed waypoints with range and bearing
information, which, will depend on the sophistication of the UCS
and UAV systems.
The characteristic that enables system size and capability to be
tailored dependent on the user needs.
The use of aircraft, surface craft, submarines, specialized rescue
teams and equipment to search for and rescue personnel in
distress on land or at sea.
Imagery and/or imagery products derived from primary imagery or
from the further processing of secondary imagery.
Equipment which detects, and may indicate, and/or record objects
and activities by means of energy or particles emitted, reflected, or
modified by objects.
Mandatory compliance.
Recommended compliance.
The generic term used to describe communications intelligence and
electronic intelligence when there is no requirement to differentiate
between these two types of intelligence, or to represent fusion of
the two.
A set of computer programs, procedures and associated
documentation concerned with the operation of a data processing
system, (e.g., compilers, library routines, manuals, and circuit
diagrams).
Preferred term: NATO standardization agreement. The NATO term
derived from standardization agreement.
The development and implementation of concepts, doctrines,
procedures and designs in order to achieve and maintain the
compatibility, interchangeability or commonality which are
necessary to attain the required level of interoperability, or to
optimise the use of resources, in the fields of operations, materiel
and administration.
a) The retention of data in any form, usually for the purpose of
orderly retrieval and documentation. b) A device consisting of
electronic, electrostatic or electrical hardware or other elements into
which data may be entered, and from which data may be obtained.
The systematic observation of aerospace, surface or subsurface
areas, places, persons, or things, by visual, aural, electronic,
photographic, or other means.
A - 16
Synthetic Aperture
Radar (SAR)
System
Architecture
Target
Target Acquisition
Targeting
Technical
Architecture
Tracking
Uninhabited Aerial
Vehicle /Unmanned
Aerial Vehicle
(UAV)
UAV system
UAV Control
System (UCS)
ANNEX A to
STANAG 4586
Edition 3
A system that uses the frequency shifts associated with the motion
of the sensor (Doppler shift) to produce an image with higher
resolution then would be available with only the radar systems
beam width and pulse length. It requires complex data processing
after collection of the radar data. Complements photographic and
other optical imaging capabilities because of the minimum
constraints on time-of-day and atmospheric conditions and because
of the unique responses of terrain and cultural targets to radar
frequencies.
Defines the physical connection, location and identification of the
key nodes, circuits, networks, war fighting platforms, etc.,
associated with information exchange and specifies systems
performance parameters.
Constructed to satisfy operational
architecture requirements per the standards defined in the technical
architecture.
The object of a particular action, for example a geographic area, a
complex,
an
installation,
a
force,
equipment,
an
individual, a group or a system, planned for capture, exploitation,
neutralization or destruction by military forces.
The detection, identification, and location of a target in sufficient
detail to permit the effective employment of weapons.
The ability to report the position (may include speed and direction)
of a target detected with an AV payload. Target position is reported
in terms of latitude and longitude (may include altitude) or in terms
relative to a point. Target position information is sufficiently accurate
to support weapon system fire control requirements.
A minimal set of rules governing the arrangement, interaction, and
interdependence of the parts or elements whose purpose is to
ensure that a conformant system satisfies a specific set of
requirements. It identifies system services, interfaces, standards,
and their relationships. It provides the framework, upon which
engineering specifications can be derived, guiding the
implementation of systems. Simply put, it is the building codes and
zoning laws defining interface and interoperability standards,
information technology, security, etc.
Precise and continuous position finding of targets by radar, optical,
or other means.
A powered, aerial vehicle that does not carry a human operator
uses aerodynamic forces to provide vehicle lift, can fly
autonomously or be piloted remotely, can be expendable or
recoverable, and can carry a lethal or non-lethal payload. Ballistic or
semi-ballistic vehicles, cruise missiles, and artillery projectiles are
not considered unmanned aerial vehicles.
Includes the air vehicles, modular mission payloads, data links,
launch and recovery equipment, mission planning and control
stations, data exploitation stations and logistic support.
The functional set charged with control of the AV and interfacing
with C4I, the UAV payload and UAV System operator(s). Includes
all the UAV control systems and encompasses launch and recovery
system.
A - 17
Vehicle Data
Terminal (VDT)
Vehicle Specific
Information
Vehicle Specific
Module (VSM)
Video Imagery
Warnings
Waypoint
Waypoint Control
ANNEX A to
STANAG 4586
Edition 3
The data link element consists of the Vehicle Data Terminal (VDT)
in the air vehicle and the Control Data Terminal (CDT) on the
ground. Connectivity between the CDT and VDT is prerequisite for
Level 2, 3, 4, and 5 interoperability.
Information sent to or from the air vehicle that is not contained in
the core, generic DLI message set.
A function that resides between the DLI and the air vehicle
subsystem. Facilitates compliance with this STANAG by acting as
a bridge between standard DLI data formats, and protocols, and a
specific air vehicle.
A sequence of images, with metadata, which is collected as a timed
sequence of images in standard motion imagery format, managed
as a discrete object in standard motion imagery format, and
displayed as a sequence of images. Video imagery is a subset of
the class of motion imagery.
An alert indicating a hazardous condition requiring immediate action
to prevent loss of life, equipment damage, or failure of the mission.
A point on a UAV route which is defined by latitude/longitude.
Altitude is usually defined.
Semi-autonomous or man-in-the-loop method of air vehicle control
involving the use of defined points (latitude/longitude/altitude) to
cause the UAV (air vehicle, sensor(s), weapons, dispensable
payloads, onboard systems, etc.) to accomplish certain actions.
A - 18
ANNEX B to
STANAG 4586
Edition 3
ANNEX B
STANDARD INTERFACES OF UAV CONTROL SYSTEM (UCS) FOR
NATO UAV INTEROPERABILITY
TABLE OF CONTENTS
1 INTRODUCTION................................................................................................................ 3
1.1 STANAG 4586 Objective......................................................................................... 3
1.2 Assumptions and Constraints. .............................................................................. 4
1.3 Annex B Structure................................................................................................... 4
2 INTEROPERABILITY CONCEPTS. .................................................................................. 6
2.1 Overview. ................................................................................................................. 6
2.2 Current Status of UAV Systems Interoperability. ................................................ 7
2.3 Levels of Interoperability........................................................................................ 7
3 UCS FUNCTIONAL ARCHITECTURE............................................................................ 12
3.1 Core UCS Requirements. ..................................................................................... 14
3.2 Data Link interface (DLI)....................................................................................... 14
3.3 Command and Control Interface (CCI)................................................................ 14
3.4 Human Computer Interface (HCI) Requirements. .............................................. 15
4 UCS COMMUNICATION AND INFORMATION TECHNOLOGY PROTOCOLS
AND STANDARDS............................................................................................................... 16
4.1 Data Interchange/Communications Protocols and Standards. ........................ 17
4.2 Standards For Optional Functionality................................................................. 18
4.3 Compliance With Other STANAGS...................................................................... 18
B-1
ANNEX B to
STANAG 4586
Edition 3
LIST OF FIGURES
Figure B - 1. UAV System Elements ............................................................................. 6
Figure B - 2. Current UAV System Operations Example ............................................ 7
Figure B - 3. UAV System Interoperability Architecture............................................. 9
Figure B - 4. UCS Functional Architecture ................................................................ 12
B-2
Annex B to
STANAG 4586
Edition 3
1 Introduction.
1.1 STANAG 4586 Objective.
Unmanned Aerial Vehicle Systems (UAS) have become valuable assets in helping
Joint Force Commanders (JFCs) to meet a variety of theatre, operational and tactical
objectives. The optimum synergy among the various national UAS deployed requires
close co-ordination and the ability to quickly task available UAS assets, the ability to
mutually control the unmanned air vehicles (UAVs) and their payloads, as well as
rapid dissemination of the resultant information at different command echelons. This
requires the employed UAS to be interoperable.
Currently, many UAS are not fully interoperable. The interfaces defined in the NATO
ISR Interoperable Architecture (NIIA) provide interoperability for ISR systems at
Level of Interoperability (LOI) 1 and 2 for digital sensors compliant with the applicable
referenced STANAGS, 7085 compliant data link and NATO Interoperability
Standards and Profiles (NISP) specified communications protocols.
Current or legacy UAS have been designed and procured nationally and contain
system elements that are generally unique and system specific. They do not have
standard interfaces between the system elements. This results in a variety of noninteroperable stovepipe systems. Although commonality of hardware and software
would be a solution to achieve interoperability and may be desirable from an
economic standpoint, commonality is not mandatory.
In order to enable interoperability of UAS the implementation of standards for key
system interfaces and functions is required. These standards are laid down in a
number of existing or emerging NATO STANAGs and generally applied commercial
standards documents. They are referred to and listed in this STANAG where they are
applicable. The respective operational requirements and approved Concept of
Operations (CONOPS) will determine or drive the required LOI (see Section 2.3 for
definition) that the specific UAV system will achieve.
The objective of STANAG 4586 is to specify the interfaces that shall be implemented
in order to achieve the operationally required and feasible LOI according to the
respective UAV systems CONOPS as applicable to the specific system and theatre
of operations. This will be accomplished through implementing standard interfaces in
the UAV Control System (UCS) to communicate with different UAVs and their
payloads, as well as with different C4I systems. The implementation of standard
interfaces will also facilitate the integration of components from different sources as
well as the interoperability of legacy systems.
The standards in STANAG 4586, which are identified as mandatory, shall be
implemented as a whole in order to achieve the required LOI. It is assumed that air
safety regulations will require the certification of systems, which result from
combining the operation of assets from different UAS. Compliance with STANAG
4586 will ease this process and likely UAV system combinations can be certified in
advance.
On this basis, UAS that are compliant with STANAG 4586 will increase NATO
Combined/Joint Service flexibility and efficiency to meet mission objectives through
the sharing of assets and common utilisation of information generated from UAS.
B-3
Annex B to
STANAG 4586
Edition 3
1.2 Assumptions and Constraints.
This STANAG was developed using the following assumptions and constraints:
Elements of the system (e.g., Core UAV Control System (CUCS),
Data Link Interface (DLI) Vehicle Specific Module (VSM), Command
and Control Interface (CCI), Command and Control Interface Specific
Module (CCISM),) are not required to be co-located.
The STANAG requirements have been developed independent of
national CONOPS. Thus it is not the intent to define or imply specific
CONOPS in this STANAG.
This STANAG addresses the interface with Airspace Management
Authority required to coordinate the operation of UAVs in a controlled
air space. It does not address or imply the overall requirements and
required certifications that may be necessary to operate UAVs in
controlled air space.
Critical (hard) real time requirements of UAV and payload control shall
be allocated to the VSM function. Near real time requirements can be
allocated to the CUCS as long as the STANAG 4586 specified latency
requirements for the respective messages are met, and the respective
system requirements are satisfied.
The contents of the STANAG are independent of the UAS hardware
characteristics.
1.3 Annex B Structure.
Annex B provides a top level description of interoperability objectives and the
approach taken to achieve UAS interoperability through standardising the interfaces
between the CUCS and the UAV and the CUCS and external C4I systems. It
describes the requirement for a standard functional UCS architecture to
accommodate those interfaces and refers to the Appendices B1 B3 that contain the
details of the standards required by STANAG 4586. It also lists other STANAGs,
standards and protocols that are required for achieving UAS interoperability and
offers some considerations for their implementation. The following Appendices are
elements of Annex B:
Appendix B1 explains the approach to standardising the DLI and the
functionality of the VSM. It contains the standard messages and
protocols required at the DLI that enable the CUCS to communicate
with and control different UAVs and payloads and to support the
required UAS operator(s) interface as specified in the Human
Computer Interface (HCI), Appendix B3.
Appendix B2 shows the approach selected to standardise the CCI
and the application of the Command and Control Interface Specific
Module (CCISM). The appendix contains the following:
- Information Exchange Requirements (IER), Attachment B2
1 and lists the UCS APP-11
- Attachment B2 2 identifies the UCS APP-11 Message
Implementation Requirements to satisfy the IER requirements and
supports the required UAV System operator(s) interface as specified
in the Human Computer Interface (HCI), Appendix B3.
B-4
Annex B to
STANAG 4586
Edition 3
Appendix B3 describes the Human Computer Interface (HCI)
requirements and services that the CUCS will provide to the UAS
operator(s).
B-5
Annex B to
STANAG 4586
Edition 3
2 Interoperability Concepts.
2.1 Overview.
A UAS can be divided into five distinct elements as shown in Figure B - 1. The air
vehicle element consists of the airframe, propulsion and the avionics required for air
vehicle and flight management. The payload element is comprised of payload
packages. These can be sensor systems and associated recording devices that are
installed on the UAV, or they can consist of stores, e.g., weapon systems, and
associated control/feedback mechanisms, or both. As illustrated, the data link
element consists of the Vehicle Data Terminal (VDT) in the air vehicle and the
Control Data Terminal (CDT) which may be located on the surface, sub-surface or air
platforms. Control of the UAS is achieved through the UCS and data link elements.
Although shown as part of the UAS surface component, the UCS and the associated
data link terminal can be located in any platform, (e.g., another air platform). The
UCS element incorporates the functionality to generate, load and execute the UAV
mission and to disseminate useable information data products to various C4I
systems. It should be noted that Figure B -1 shows a common path for UAV
command and control, payload command and control, and products. These
functions may be accomplished on separate, independent data links. The launch and
recovery element incorporates the functionality required to launch and recover the air
vehicle(s).
UAV SYSTEM
UAV AIR COMPONENT
PAYLOAD ELEMENT
AIR VEHICLE ELEMENT
Propulsion
Unit
Mission
Payload
Avionics
Unit
Payload
Recorder
DATA LINK ELEMENT
Vehicle Data
Terminal
(VDT)
UAV SURFACE COMPONENT
LAUNCH AND
RECOVERY
ELEMENT
Control Data
Terminal
(CDT)
UCS
ELEMENT
EXTERNAL
C4I SYSTEMS
Operator(s)
Figure B - 1. UAV System Elements

The Launch and Recovery element is unique to its air vehicle. The UCS
accommodates this vehicle specific uniqueness via its VSM as defined in Section 3,
UCS Functional Architecture.
B-6
Annex B to
STANAG 4586
Edition 3
2.2 Current Status of UAV Systems Interoperability.
Current UAS are mostly stove pipe systems. They utilize unique data links,
communication protocols and message formats for communication between UCS
and the UAV and the UCS and external C4I systems. As a result, the dissemination
of sensor data is mostly via indirect means, (e.g., from UCS to an exploitation system
to the user). Current UAS operations in Joint NATO operations are illustrated in
Figure B - 2.
The illustrated UAS all utilize unique data links and UCS as well as unique
data/message formats for communication between the UAV and the UCS and also
the UCS and the C4I nodes. Dynamic joint cooperative operations require near real
time tasking/re-tasking and dissemination of reconnaissance data to support the
Tactical Commander, which the stove-pipe UAS may not support.
Country
A
AV
Country
B
AV
Country
C
AV
DATA
LINK
DATA
LINK
DATA
LINK
UCS
UCS
UCS
C4I
C4I
C4I
CURRENT NATO/NATIONAL C4I NODES

EXPLOITATION SYSTEMS
TACTICAL COMMANDER
Figure B - 2. Current UAS Operations Example

2.3 Levels of Interoperability.
2.3.1
General.
A UAS as defined above may be composed of various components which include; a

UAV, a CUCS, a VSM, a CCISM, and data links, that provide for interoperable
operations between diverse UAS. The STANAG 4586 used the LOI as defined in
Edition 2 for the current UAS as a starting point, and modified these definitions to
enable UAS to support a broader scope of interoperable CONOPS. LOIs have been
defined for discrete levels of functionality and are Independent of one another. In
other words, the control of a sensor (within LOI 3) is independent and separate from
the control of the air vehicle (within LOI 4). LOI definitions are applied to both the DLI
and CCI. The DLI and CCI LOIs can be different for a specific UAS design.
B-7
Annex B to
STANAG 4586
Edition 3
2.3.2
Definition.
The following LOIs have been defined in this Edition of STANAG 4586 for UAS in
order to improve operational flexibility:
Level 1:
Indirect receipt and/or transmission of sensor product and associated

metadata, for example KLV Metadata Elements from the UAV.
Level 2:
Direct receipt of sensor product data and associated metadata from

the UAV.
Level 3:
Control and monitoring of the UAV payload unless specified as

monitor only.
Level 4:
Control and monitoring of the UAV, unless specified as monitor only,

less launch and recovery.
Level 5:
Control and monitoring of UAV launch and recovery unless specified

as monitor only.
Unless otherwise stated, LOI 3, 4 & 5 assume control and monitor.
2.3.3
Application.
The interoperability levels defined above can be enabled through the standardization
of interfaces between the UAS elements and between the UCS and external C4I
systems. This can be accomplished if the overall System Architecture is also
standardised to the extent that it accommodates the implementation of these
standard interfaces. In order to achieve interoperability, the UCS Architecture and
interfaces shall support the appropriate communication protocols and message
formats for legacy as well as new UAS.
To achieve LOI 2 and above (LOI 3, 4, and 5) interoperability across an RF
communications interface requires the use of a CDT that is interoperable with the
VDT. Connectivity between the CDT and VDT is prerequisite for LOI 2 and above.
B-8
Annex B to
STANAG 4586
Edition 3
UAV SYSTEM
UAV AIR COMPONENT
PAYLOAD ELEMENT
STANAG
7023, 4545, etc.
Mission Payload
AIR VEHICLE ELEMENT
Propulsion
Unit
Avionics
Unit
STANAG
7024, 4575, etc.
Mission Recorder
DATA LINK ELEMENT
VDT
ADT
UAV SURFACE COMPONENT
CDT
GDT
LAUNCH AND
RECOVERY
ELEMENT
STANAG
7085
UCS
ELEMENT
STANAG
4586
EXTERNAL
C4I SYSTEMS
Operator(s)
Figure B - 3. UAS Interoperability Architecture

As illustrated in Figure B 3, there are already a number of existing or emerging
Standardization Agreements (STANAGs) that are applicable to UAS. They provide
standards for interoperable data link (STANAG 7085), digital sensor data between
the payload and the UAV element of the data link (STANAG 7023, 4545, 4607, and
4609), and for on-board recording device(s) (STANAG 7024 and 4575).
Currently, there is no standard that defines the interfaces between the UCS and the
UAV (including launch and recovery functions) via the CDT. Although STANAG
7149, APP-11, defines a catalogue of standard messages for tasking and status
reporting, there is no standard/agreement as to which specific messages and fields
should be used by UAS. In addition, there are no standards/agreements as to the
type of information that should be presented to a UAS operator, nor for defining a
system operators required level of proficiency.
STANAG 4586 provides the standardization of these interfaces. UAS, which are
compliant with STANAG 4586, including the referenced STANAGs and standards,
will enable interoperability at LOI 2 or above. For LOI 1 or 2 systems that use digital
imaging payloads and STANAG 7085 compliant data links, only the NIIA standards
are required, regardless of whether the surface component is a UCS or other ISR
exploitation facility. The interface requirements (messages or display parameters) to
achieve a given LOI are identified in the Appendices of this Annex.
The use of the NIIA standards to enable LOI 1 or 2 implies that some of the LOIs are
conditional on the type of payload data format used by the UAS. For example,
system A produces payload data in format A (e.g., STANAG 7023) and system B
produces data in format B (e.g., STANAG 4545), both systems can be LOI 2 but they
use different payload data formats.
Where a UAS does not use the NIIA standards (e.g., analogue payload data), there
is a need to be able to associate the appropriate metadata with the analogue payload
data. To enable this to be achieved the appropriate metadata needs to be captured in
B-9
Annex B to
STANAG 4586
Edition 3
a standard way. The mechanism for achieving this is to use 4586 messages that will
support this at the appropriate LOI, e.g. LOI (3).
Thus the approach to enabling the desired LOI is based on compliance with existing
standards or establishing new standards for:
A data link system(s) that provides connectivity and interoperability
between the UCS and the UAV(s). The data link system(s) shall
accommodate legacy as well as future systems. STANAG 7085,
Interoperable Data Links for Imaging Systems, specifies a data link
system that would provide the required connectivity and interoperability.
Users that require encryption should reference work being done by the
Joint Capability Group on ISR (JCGISR) and NATO International Military
Staff (IMS) for interoperable encryption standards. A standard for a
separate, back up, command and control (C2) data link for UAS
requiring one, or for use in tactical UAS not requiring the capability of a
STANAG 7085 Data Link, is not currently available. A draft standard,
STANAG 4660, has been drafted to define the waveform and upper layers
(ISO layers) of an interoperable C2 data link. The draft STANAG is in
review process and when and if ratified, it will become a standard for an
Interoperable C2 Data Link (IC2DL).
Format for payload/sensor data for transmission to the UCS via the data
link and/or for recording on the on-board recording device. STANAG
7023, Air Reconnaissance Primary Imagery Data Standard, with addition
for non-imagery sensors, e.g., Electronic Support Measures (ESM),
STANAG 4545, NATO Secondary Imagery Format, STANAG 4607, NATO
GMTI Format, and STANAG 4609, NATO Digital Motion Imagery Format,
provide standard formats for transmitting payload data to the UCS or for
storage on the on-board recording device.
Recording device for on-board recording of sensor data, if required.
STANAG 7024, Imagery Air Reconnaissance Tape Recorder Standard,
and STANAG 4575, NATO Advanced Data Storage Interface (NADSI),
specify standard recording devices and formats for wideband tape and
other advanced media, e.g., solid state, RAID recorders, respectively.
UCS interfaces with the data link system, e.g., DLI; UCS interface with
command and control systems, e.g., CCI; and HCI top level requirements
for a UCS to support the UAS operators. STANAG 4586 defines the UCS
architecture and interface requirements.
Although beyond the scope of this STANAG, operational guidelines or
standards that define the minimum level of operator proficiency needed to
operate a given UAV at the desired LOI are also required.
It is also recognised that UAVs will have the capability to carry a range of payload
types, e.g., EO, EO/IR, SAR, ESM, etc., and that each UAS will only implement some
of these payload types. It has been accepted that each UAS will only support the
payload type implemented on that system and this in turn will affect the LOI. For
example, UAV A carries an EO/IR payload and UAV B carries a SAR payload;
system A is LOI 2 for an EO/IR payload; system B is LOI 2 for a SAR payload, both
systems are LOI 2 but only for the appropriate payload. This means that the defined
LOIs are conditional on the type of payload implemented in the UAV.
B - 10
Annex B to
STANAG 4586
Edition 3
2.3.4
Summary.
Keys concepts to remember are:

- LOI 2 monitor is conditional on the type of payload (station) and the number
of payloads (stations) implemented onboard the UAV. It is also conditional on the
type of payload data format used by the UAS.
- LOI 3 monitor only or control and monitor is conditional on the type of
payload (station) and the number of payloads (stations) and the payload data format
used by the UAV.
- LOI 4 monitor only or control and monitor is not affected by the payloads
onboard the UAV.
- The detailed impact on the LOIs and their relation to the requirements and
messages defined in STANAG 4586 is discussed further in the Annex B Appendices.
B - 11
Annex B to
STANAG 4586
Edition 3
3 UCS Functional Architecture.
The UCS Functional Architecture required to support interoperability among future
and legacy UAS is illustrated in Figure B - 4, UCS Functional Architecture.
AV
LAUNCH &
RECOVERY
SYSTEM
UCS
VSM
DLI
CCI
HCI
CORE
UCS
OPERATOR
CCI
CCISM
C4I
SYSTEM
C4I
SYSTEM
Figure B - 4. UCS Functional Architecture

This architecture establishes the following functional elements and interfaces:
CUCS
DLI
CCI
VSM
CCISM
This STANAG is not an attempt to define a detailed design or implementation for the
CUCS other than specifying that the functional architecture accommodate the
integration of the DLI and CCI and recommending that it follow applicable NATO
STANAGS and guidelines for software. Lastly, because of changing technology, this
STANAG does not define a specific Common Operating Environment (COE) but only
specifies that the Operating Environment supports/integrates the specified
network/transport protocols and supports the specified user applications.
Future, as well as legacy UAS, will be enabled for interoperability through compliance
with this architecture and the relevant STANAGs. The DLI shall support legacy as
well as future UAVs and all air vehicle technologies (e.g., fixed wing, rotary wing,
etc.), and all UAV operational missions (surveillance, reconnaissance, and combat).
B - 12
Annex B to
STANAG 4586
Edition 3
Future UAS should utilize a STANAG 7085 compliant data link system. For those that
do not (future as well as legacy systems), a VDT compatible CDT shall be provided
in order to achieve LOI 2 and above.
In similar fashion, the CCI shall support legacy as well as future C4I systems (e.g.,
Allied Command and Control System (ACCS)). Thus, the interface between the
CUCS and the external C4I nodes shall be compatible with the communication
system infrastructure utilized to support the external tasking and sensor data
dissemination. This will be accomplished by using the communication standards
identified by the NISP), Allied Data Publication 34 (ADatP-34) as specified in Section
4. The NISP is intended to provide an overall framework for NATO communications.
All future communications and information systems used in NATO are to conform to
these standards.
The concept of a VSM functionality is introduced which provides the
unique/proprietary communication protocols, interface timing, and data formats that
the respective air vehicles require. The functionality of the VSM is defined in Section
1.4 of Appendix B-1. For example, one of the VSM functions is to provide any
necessary translation of the DLI protocols and message formats to the unique air
vehicle requirements. Since the VSM may be unique to each air vehicle, the air
vehicle manufacturer would generally provide it. If the data links utilized in the UAS
are not STANAG 7085 compliant (such as a low band link providing beyond line-ofsight connectivity, e.g., SATCOM data link), then the CDT associated with the noncompliant data link must be provided and interfaced with the UCS via the VSM DLI
function, i.e. managing interfaces required to control and monitor data link(s)
operation, or the capability to receive and process the DLI specified Data Link
Command and Status Messages should be incorporated in the CDT. Selected VSM
functions, e.g. translating data from the representation used by the CUCS (DLI
defined messages) to vehicle specific representations and vice versa, can be hosted
on the UAV and/or on the ground. Critical (hard) real time functions and interfaces
shall be implemented via the VSM function. Near real time functions and interfaces
may be implemented via the CUCS or VSM function, based on data latency
requirements.
When a new UAV is introduced into a pool of interoperable UAS, it may be necessary
to integrate and validate a new corresponding VSM function into each existing UCS.
This would be necessary only if the newly introduced vehicle requires VSM
functionality in the ground portion of the system. If, however, the existing UCS
includes a 7085 compliant CDT and incorporates the data link management functions
defined by STANAG 4586, and if the newly introduced UAV implements DLI
messages directly and includes a 7085 compliant VDT, then the corresponding VSM
functions are not required.
The CCISM provides a function similar to the VSM, that is, the encapsulation of the
CCI data and any translation required to be compatible/interoperable with the
physical communication links between the UCS and the C4I systems. The CCISM
can be hosted on and collocated with the UCS or by and with the connecting C4I
node. The UCS architecture shall make provision for the integration of a CCISM.
The UAV system operator should be provided a standard set of parameters that the
operator can use to operate/monitor the UAVs that have been assigned to him. This
includes his interface with the Controlling Air Management Authority. Although it is
not necessary for different STANAG 4586 compliant UCSs to have identical displays,
it is mandatory that the CUCS meets the HCI requirements specified in Appendix BB - 13
Annex B to
STANAG 4586
Edition 3
3. To facilitate this, it is recommended that the HCI Guidelines in the STANAG 4586
Implementation Guideline Document be followed in the development of the CUCS.
The DLI and CCI shall be implemented using messages. In addition to supporting
the generic message sets defined in the appendices to the STANAG 4586, the
CUCS shall be capable of supporting a remote display capability. The remote
display capability supports the control and monitoring of vehicle specific information
on the CUCS for which there is no available generic capability. Services, which are
installed on the CUCS in an unaltered state, that are compatible with identified
operating systems to support this remote display capability, are identified in
Appendix B1. The framework for the information exchange will allow for information
to be able to move from one process to another on the same platform, between
processes on different platforms, and even between different software products and
operating systems.
3.1 Core UCS Requirements.
The CUCS shall provide a user interface that enables the qualified UAV operator to
conduct all phases of a UAV mission. It shall support the requirements of the DLI,
CCI, and HCI. The CUCS should provide a high resolution, computer generated,
graphical user interface that enables a qualified UAV operator the ability to control
different types of UAVs and payloads.
Depending on the appropriate LOI and the payloads supported in the respective
UAS, the CUCS should provide:
The functionality and capability to receive, process, and disseminate data
from the UAV and payload; perform mission planning; monitor and control
the payload; monitor and control the UAV; and monitor and control the
data links
An open software architecture to support additional future UAVs and
payload capabilities
The UAS operator with the necessary tools for computer related
communications, mission tasking, mission planning, mission execution
and monitoring, data receipt, data processing, and data dissemination
The capability to host the required VSM and CCISM functions
3.2 Data Link interface (DLI).
The DLI interface between the CUCS and the VSM element of the UAS is defined in
Appendix B1. It will enable the CUCS to generate and understand specific
messages, detailed in Appendix B1, for control and status of UAVs and payloads.
This standard message set and accompanying protocols have been developed to be
UAV and payload type, e.g., EO/IR, independent. In addition, the DLI specifies the
mechanism for the processing and display of vehicle specific messages.
3.3 Command and Control Interface (CCI).
The CCI between the C4I systems/nodes and the CUCS is defined in Appendix B2.
The standard message set and accompanying protocols have been selected to be
C4I system/node independent and to avoid placing additional requirements on the
C4I system. The UCS provider and respective C4I user of the UAS should jointly
identify the CCISM functionality required, if any, to provide UCS compatibility with the
specific C4I system. Appendix B2 specifies the protocols down to the message
content and format level. The networks and communications used to support the
B - 14
Annex B to
STANAG 4586
Edition 3
CCI shall be NISP compliant. The NISP is intended to provide an overall framework
for NATO communications that provides for interoperability among military command,
control and communications systems. The NISP strategy has been developed to
achieve interoperability, maximize the exploitation of commercial of-the shelf (COTS),
and reduce the proliferation of non-standard systems. All future communication and
information systems used in NATO will conform to these standards.
3.4 Human Computer Interface (HCI) Requirements.
The HCI Appendix B3 establishes the operator display and input requirements that
the CUCS shall support. Appendix B3 specifies the requirements levied upon the
CUCS, and does not impose any design requirements on human factors (HF) and
ergonomics, (e.g., number of displays, manual controls, switches etc.). Appendix B3,
while not specifically defining the format of the data to be displayed, identifies the
capabilities that the CUCS shall provide in order for the qualified UAS operator(s) to
effectively operate the UAS. The HCI requirements also address the display and
operator interactions that are imposed on the CUCS by the CCI and DLI.
B - 15
Annex B to
STANAG 4586
Edition 3
4 UCS Communication and Information Technology Protocols and Standards.
UAS and C4I systems should be capable of interoperating across a routed network of
multiple sub-networks, in which the UAS is seen as a terminal element (or terminal
sub-network) of the whole network. This will allow the physical components of the
UAS and C4I systems to be anywhere on that network. The electronic exchange of
information between UCS and the C4I systems shall be in accordance with the NISP,
ADatP-34 mandated standards.
The NISP will also provide the necessary guidance and technical components to
support project implementations and transition to the NATO Network Enabled
Capability (NNEC). The NISP applies to all NATO Computer Information Systems
(CIS) and Management Information Systems (MIS), including their internal and
external interfaces, which produce, use, or exchange information electronically.
The purpose of the NISP is to:
- Serve as the principal source of technical guidance for management of
NATO CIS project implementations and transition to NNEC;
-Track technology developments in order to optimise application
development;
- Compile all applicable CIS standards as baseline for optimising programmes
and project selection and adherence;
- Assess applicable CIS products for system application;
- Support architecture-based CIS programme development and evolution;
- Provision of technical reference and rationale to promote and optimise
NATO CIS systems interoperability;
- Promote NATO internal, Nation to NATO and Nation to Nation
interoperability;
- Provide guidance on transformation to NNEC.
The NISP specifies the minimum set of communication and information technology
standards to be mandated for the acquisition of all NATO Command, Control and
Communication (C3) systems. Future NATO C3 systems are expected to support
both combined and joint operations, and thus national commitments to the
appropriate mandatory standards specified in this document will also significantly
contribute to the achievement of the LOI required between NATO and national C3
systems for such objectives. The LOI needed to achieve the desired goal will be
determined by operational requirements and stipulated in the applicable CONOPs.
In this scenario, it is important to note that different LOIs may be required to achieve
internal interoperability between NATO systems than those required for external
interoperability between NATO systems and national systems. The standards
selection focuses on mandating only those standards critical to external
interoperability, and is based primarily on commercial open system technology, which
has strong support in the commercial marketplace. Where a system is to be
implemented utilizing certain services, it is essential that it adopts the relevant
standards mandated in the NISP (e.g., if a service/interface is required, it should be
implemented in accordance with the associated mandated standard(s)). Specification
and usage of other standards, if required beyond those identified in the NISP, shall
be additive, complementary, and non-conflicting with NISP mandated standards.
B - 16
Annex B to
STANAG 4586
Edition 3
4.1 Data Interchange/Communications Protocols and Standards.
4.1.1 Data Interchange Services.
For data interchange services, at a minimum, the following NISP mandated
standards shall be implemented in the UCS to achieve interoperability:
4.1.1.1 Geographical.
Digital Geographic Information Exchange Standard (DIGEST),

STANAG 7074
Digital Terrain Elevation Data (DTED) Geographic Information
Exchange Standard, STANAG 3809
Digital Feature Analysis Data (DFAD)
World Geodetic System - 84 (WGS-84), Mil-STD-2401
4.1.1.2 Communication Services.

For communications service area, at a minimum, the following NISP mandated
standards shall be implemented in the UCS to achieve interoperability:
4.1.1.2.1 Internet Protocol (IP) IPv4 (STD 5) RFC 791, 792, 919, 922, 950:1985
updated by RFC 1112:1989, 2474:1998, 2507:1999, 2508:1999, 3168:2001,
3260:2002, 3376:2002) 1112)) / IPv6, RFC 1981 through 4007.
The UCS architecture will adhere to the IP version selected by the wider defence
community within which they are integrated. In the near-term, systems will need to
support the current version of IP (STD 5)]. In the longer term, the emerging standard
IPv6 will be adopted by the military to overcome perceived weaknesses in IPv4. IPv6
increases the available address space, reorganizes the protocol headers and
improves support for security, throughput, latency, error rate and cost.
4.1.1.2.2 Transmission Control Protocol (TCP) (IETF STD 7) RFC 0793:1981
updated by RFC 3168:2001)).
The Transmission Control Protocol (TCP) [RFC 793] provides a connection oriented
reliable byte stream service. TCP is a bi-directional protocol, which has no concept of
messages. Any framing has to be added at the application level. TCP contains an
acknowledgement scheme which makes it reliable (bytes are delivered correctly and
in order) and which implements flow control.
The TCP/IP protocols were selected since they can provide consistent end-to-end
network and transport communications compliant with NATO-wide digitisation
initiatives.
4.1.1.2.3 User Datagram Protocol (UDP) (IETF STD 6:1980), RFC 768, 1122.
The User Datagram Protocol (UDP) offers only a minimal transport service nonguaranteed datagram delivery and gives applications direct access to the datagram
service of the IP layer. UDP is used by applications that do not require the level of
service of TCP or that wish to use communications services (e.g., multicast or
broadcast delivery) not available from TCP.
4.1.1.2.4 Hypertext Transfer Protocol (HTTP) Version 1.1, IETF RFC 2616:1999
updated by RFC 2817:2000.
Hypertext Transfer Protocol (HTTP) should be the main protocol used for web
browsing. Web browsing provides a common and powerful mechanism for sharing
B - 17
Annex B to
STANAG 4586
Edition 3
information. HTTP and applications associated with the use of HTTP are used to
index, access and transfer processed information. The ability to search the web
server can be provided using COTS applications. A C4I user needs a Web browser
(e.g., Netscape or Internet Explorer), the Uniform Resource Locator (URL) of the
page and communications connectivity to access the information.
4.1.1.2.5 File Transfer Protocol (FTP), IETF, RFC 0959:1985 updated by RFC
2228:1997, 2640:1999, 2773:2000.
File Transfer Protocol (FTP) should be used to transfer processed information. It can
be used in support of HTTP to transfer files, but needs additional support for
providing an index to the information stored on the file server. Once the file has been
transferred to the C4I system it is then the responsibility of the C4I to provide
applications to process the file.
4.1.1.2.6 Network Time Protocol (NTP), RFC 1305:1992 .
The Network Time Protocol (NTP) is a client/server relationship that exists between
the CUCS and the VSM (in the air or ground). This paragraph does not attempt to
provide an in-depth response to the NTP explanation. For the definition, see RFC
1305 as well as Sun Microsystems NTP related information. This paragraph provides
an overview of the planned NTP client/server capability that the CUCS will use to
control and maintain the VSM clock.
It will be required that the CUCS be provided a UTC reference source for the NTP
server daemon.
There are two solutions to synchronizing the time using NTP. The solution
recommended here is the xntp option (vs. the ntpdate). An ntp.conf file will be
required to provide configuration information required by the NTP server daemon.
Within the NTP protocol, the designation of the NTP client and server is embedded
as part of the NTP protocol initialization process. This process is defined at the lower
layers of the operating system and is transparent to the application layer.
The end result of the NTP initialization process is that the client and server can be
designated to the CUCS or VSM.
For a detailed explanation of this process, please see RFC 1305.
The NTP time server will use UDP to communicate with the clients. There is no
overhead associated with the protocol because it is connectionless. It will not
interfere with TCP/IP communications. This level of communication will not be
required to be documented in the STANAG DLI.
This protocol provides 10 millisecond accuracy with a 1 millisecond resolution.
4.2 Standards for Optional Functionality.
If it is desired to implement additional service areas (e.g., data interchange), and
classes within these service areas (e.g., video and audio interchange) into the UCS,
the NISP mandated standards should be used in implementing these services.
4.3 Compliance with Other STANAGS.
While STANAG 4586 is mandatory to enable UAV command and control
interoperability, the following ISR interface standards are required to address
interfaces among the various horizontal and vertical architectures of ISR, and include
interfaces that use both physical (e.g., wired, tape, etc.) and electromagnetic links:
B - 18
Annex B to
STANAG 4586
Edition 3
STANAG 3809 - Digital Terrain Elevation Data (DTED) Geographic
Information Exchange Standard
STANAG 4545 - NATO Secondary Imagery Format
STANAG 4559 - NATO Standard Image Library Interface (NSILI) (If
interface with Image library is desired)
STANAG 4575 - NATO Advanced Data Storage Interface (NADSI) (If
advanced storage is required)
STANAG 4607 - NATO GMTI Data Format
STANAG 4609 - NATO Digital Motion Imagery Standard
STANAG 4633 - ELINT Common Message Format (ECMF) (Study)
STANAG 5500 Concept of NATO Message Text Formatting System
(CONFORMETS) ADatP-3
STANAG 7023 - Air Reconnaissance Primary Imagery Data Standard
STANAG 7024 - Imagery Air Reconnaissance (Digital Tape Storage) (If
tape storage is required)
STANAG 7074 - Digital Geographic Information Exchange Standard
(DIGEST)
STANAG 7149 - NATO Message Catalogue - APP - 11
STANAG 7194 - NATO Imagery Interpretability Rating Scale (NIIRS)
To enhance UAV interoperability and flexibility, it is recommended that the UCS

should also be compliant with the following STANAGs:
STANAG 3377 - Air Reconnaissance Intelligence Report Forms
STANAG 4250 - NATO Reference Module for Open Systems
Interconnection
STANAG 7085 - Interoperable Data Links For Imaging Systems
- Digital Point to Point Annex of STANAG 7085 (compatible with
Common Data Link (CDL)/Tactical Common Data Link (TCDL)
specification)
B - 19
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
APPENDIX B1 DATA LINK INTERFACE
TABLE OF CONTENTS
1 INTRODUCTION.............................................................................................................. 11
1.1 Scope. .................................................................................................................... 11
1.2 Appendix B1 Overview. ........................................................................................ 11
1.3 DLI General Overview. .......................................................................................... 11
1.4 Vehicle Specific Module Functions. .................................................................... 12
1.5 Interfaces. .............................................................................................................. 15
1.6 Tailoring by Interoperability Level....................................................................... 17
1.7 Philosophy of Interface Data Representation. ................................................... 18
2 SYSTEM FUNCTIONAL REQUIREMENTS BY MISSION PHASE. ............................... 28
3 MESSAGE DISTRIBUTION STANDARD. ...................................................................... 30
3.1 Introduction. .......................................................................................................... 30
3.2 Requirements. ....................................................................................................... 30
3.3 Message Handling Approach............................................................................... 31
4 GENERIC (COMMON) DLI MESSAGE OVERVIEW. ..................................................... 36
4.1 Common Message Properties.............................................................................. 36
4.2 System ID Messages............................................................................................. 60
4.3 Flight Vehicle Command Messages. ................................................................... 77
4.4 Flight Vehicle Status Messages............................................................................ 98
4.5 Flight Vehicle Payload Relevant Messages...................................................... 116
4.6 IFF Command Messages. ................................................................................... 120
4.7 IFF Status Messages........................................................................................... 122
4.8 ATC Interface Command Messages. .................................................................. 124
1-B-1
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.9 ATC Interface Status Messages.......................................................................... 125
4.10 Vehicle Auxiliary Command Messages............................................................ 126
4.11 Vehicle Auxiliary Status Messages. ................................................................. 128
4.12 Mission Command and Status Messages........................................................ 132
4.13 Subsystems Status Messages......................................................................... 148
4.14 Miscellaneous Message Types. ........................................................................ 155
4.15 Payload Command Messages.......................................................................... 163
4.16 Payload Status Messages. ............................................................................... 196
4.17 Weapons Command Messages. ...................................................................... 225
4.18 Weapons Status Messages. ............................................................................. 228
4.19 Data Link Discovery Messages......................................................................... 231
4.20 Data Link Command Messages. ...................................................................... 237
4.21 Data Link Status Messages.............................................................................. 252
4.21.12 Message #32301: AV IP Disclosure Message........................................... 262
4.22 Data Link Transition Messages. ....................................................................... 265
4.23 Autonomy Messages. ........................................................................................ 267
4.24 General Preconnection Configuration Messages. .......................................... 272
4.25 General Postconnection Configuration Messages. ....................................... 306
4.26 VSM Forced Command Messages................................................................... 314
4.27 Draw Interface Messages. ................................................................................ 321
4.28 Vehicle and Payload Specific Message Formats. .......................................... 328
5 MISCELLANEOUS INTERFACES. ............................................................................... 330
5.1 Analogue Video Interface. .................................................................................. 330
5.2 Digital Image Data Interface. .............................................................................. 330
1-B-2
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
LIST OF FIGURES
Figure B1 - 1: DLI Role in the AV/UCS Concept ........................................................ 13
Figure B1 - 2: DLI Role in the CDT/UCS Concept...................................................... 14
Figure B1 - 3: Role of the VSM.................................................................................... 15
Figure B1 - 4: High-Level Depiction of DLI Interface Content.................................. 16
Figure B1 - 5: Autonomy Message Flow .................................................................... 20
Figure B1 - 6: Typical Scenario for Generating Vehicle-Specific Displays ............ 24
Figure B1 - 7: Message Wrapper Structure ............................................................... 32
Figure B1 - 8: Message Properties Field Definition .................................................. 33
Figure B1 - 9: Loiter Pattern........................................................................................ 87
Figure B1 - 10: Valid Area Examples.......................................................................... 94
Figure B1 - 11: Loop Action ...................................................................................... 135
Figure B1 - 12: Auto Altitude Change Actions ........................................................ 135
Figure B1 - 13: Loiter Pattern.................................................................................... 140
Figure B1 - 14: Terrain Data ...................................................................................... 223
Figure B1 - 15: CUCS VSM CDT Connection ........................................................... 233
Figure B1 - 16: Shared Data Links............................................................................ 235
Figure B1 - 17: Relay System.................................................................................... 237
Figure B1 - 18: Commands from RF Data Flow......................................................... 36
LIST OF TABLES
Table B1 - 1: Owning ID Table..................................................................................... 26
Table B1 - 2: Common vs. Vehicle Specific Functions by Mission Phase ............. 29
Table B1 - 3: IDD Version Identification ..................................................................... 34
Table B1 - 4: Checksum Length.................................................................................. 34
Table B1 - 5: Functional Message Group Table ........................................................ 41
Table B1 - 6: System ID Messages ............................................................................. 42
Table B1 - 7: Flight Vehicle Command Messages..................................................... 43
Table B1 - 8: Flight Vehicle Status Messages ........................................................... 44
Table B1 - 9: Flight Vehicle Payload Relevant Status Message ............................... 45
Table B1 - 10: IFF Command Messages...................................................................... 45
Table B1 - 11: IFF Status Messages ............................................................................ 45
Table B1 - 12: ATC Interface Command Messages.................................................... 46
1-B-3
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 13: ATC Interface Status Messages .......................................................... 46
Table B1 - 14: Vehicle Auxiliary Command Messages .............................................. 47
Table B1 - 15: Vehicle Auxiliary Status Messages..................................................... 47
Table B1 - 16: Mission Command and Status Messages .......................................... 48
Table B1 - 17: Subsystem Status Messages .............................................................. 48
Table B1 - 18: Miscellaneous Messages ..................................................................... 49
Table B1 - 19: Payload Command Messages ............................................................ 50
Table B1 - 20: Payload Status Messages................................................................... 51
Table B1 - 21: Conditional Payload Message Groups .............................................. 52
Table B1 - 22: Weapons Command Message Groups .............................................. 52
Table B1 - 23: Weapons Status Message Groups..................................................... 52
Table B1 - 24: Data Link Discovery Messages .......................................................... 53
Table B1 - 25: Data Link Command Messages.......................................................... 54
Table B1 - 26: Data Link Status Messages ................................................................ 55
Table B1 - 27: Data Link Transition Messages .......................................................... 55
Table B1 - 28: Autonomy Messages........................................................................... 56
Table B1 - 29: General Preconnection Configuration Messages............................. 57
Table B1 - 30: General Configuration Messages....................................................... 57
Table B1 - 31: VSM Forced Command Messages ..................................................... 58
Table B1 - 32: Draw Interface Messages.................................................................... 59
Table B1 - 33: Private Messages................................................................................. 59
Table B1 - 34: Message #1: CUCS Authorisation Request....................................... 64
Table B1 - 35: CUCS Type Table................................................................................. 65
Table B1 - 36: Vehicle Type IDs .................................................................................. 69
Table B1 - 37: Presence Vector Support Field Logic................................................ 71
Table B1 - 38: Message #2: VSM Authorisation Response ...................................... 75
Table B1 - 39: Message #3: Vehicle ID ....................................................................... 76
Table B1 - 40: Message #2000: Vehicle Configuration Command........................... 77
Table B1 - 41: Message #2001: Vehicle Operating Mode Command....................... 78
Table B1 - 42: Message #2002: Vehicle Steering Command.................................... 81
Table B1 - 43: Message #2003: Mode Preference Command................................... 82
Table B1 - 44: Source Message for Altitude/Airspeed.............................................. 83
Table B1 - 45: Source Message for Heading ............................................................. 83
Table B1 - 46: Message #2004: Loiter Configuration................................................ 86
1-B-4
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 47: Message #2005: Flight Termination Command ................................ 88
Table B1 - 48: Message #2006: Relative Route/Waypoint Absolute Reference
Message ................................................................................................................. 89
Table B1 - 49: Message #2007: Air Vehicle Lights .................................................... 89
Table B1 - 50: Message #2008: Engine Command.................................................... 90
Table B1 - 51: Message #2009: Zeroize Encryption Keys Command...................... 91
Table B1 - 52: Message #2010: AV Stick Command ................................................. 92
Table B1 - 53: Message #2011: Area Transmission Command .............................. 93
Table B1 - 54: Message #2012: Area Polygon Loop Segment Message ................ 95
Table B1 - 55: Message #2013: Joystick Command ................................................. 96
Table B1 - 56: Message #2014: Emergency Mode Command .................................. 97
Table B1 - 57: Message #2015: Energy Storage Unit Configuration ....................... 98
Table B1 - 58: Message #3000: Vehicle Configuration ........................................... 100
Table B1 - 59: Message #3001: Vehicle Operating Mode Report........................... 100
Table B1 - 60: Message #3002: Vehicle Operating States ...................................... 102
Table B1 - 61: Message #3003: Mode Preference Report....................................... 102
Table B1 - 62: Message #3004: Loiter Configuration Report ................................. 104
Table B1 - 63: Message #3005: Flight Termination Mode Report .......................... 105
Table B1 - 64: Message #3006: Vehicle Lights State .............................................. 105
Table B1 - 65: Message #3007: Engine Operating States....................................... 110
Table B1 - 66: Message #3008: Zeroize Encryption Keys State............................. 110
Table B1 - 67: Message #3009: Air and Ground Relative States ........................... 111
Table B1 - 68: Message #3010: Body-Relative Sensed States............................... 112
Table B1 - 69: Message #3011: AV Stick Status...................................................... 113
Table B1 - 70: Message #3012: Area Status Alert Message ................................... 114
Table B1 - 71: Message #3013: Area Transmission Status .................................... 115
Table B1 - 72: Message #3014: Emergency Mode Report ...................................... 116
Table B1 - 73: Message #3015: Energy Storage Unit State .................................... 116
Table B1 - 74: Message #4000: Inertial States......................................................... 118
Table B1 - 75: Message #4001: From-To-Next Waypoint States............................ 120
Table B1 - 76: Message #5000: IFF Code Command .............................................. 122
Table B1 - 77: Message #5001: IFF Ident (Squawk) Command.............................. 122
Table B1 - 78: Message #6000: IFF Status Report .................................................. 124
1-B-5
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 79: Message #7000: Civilian Air Traffic Control (ATC) Radio
Command............................................................................................................. 124
Table B1 - 80: Message #7001: NAVAID Radio Command ..................................... 125
Table B1 - 81: Message #9000: Civilian Air Traffic Control (ATC) Radio Status .. 126
Table B1 - 82: Message #9001: NAVAID Radio Status............................................ 126
Table B1 - 83: Message #11000: Vehicle Auxiliary Command ............................... 127
Table B1 - 84: Message #11001: Fuel, Oil & Hydraulic Command......................... 128
Table B1 - 85: Message #11101: Battery Bank Select............................................. 128
Table B1 - 86: Message #12000: Vehicle Auxiliary Status...................................... 129
Table B1 - 87: Message #12001: Electrical Report.................................................. 129
Table B1 - 88: Message #12002: Meteorological Data ............................................ 130
Table B1 - 89: Message #12003: Fuel, Oil & Hydraulic Status ............................... 131
Table B1 - 90: Message #12101: Battery Report ..................................................... 132
Table B1 - 91: Message #13000: Mission Transfer Command ............................... 133
Table B1 - 92: Message #13001: AV Route .............................................................. 134
Table B1 - 93: Message #13002: AV Position Waypoint ......................................... 137
Table B1 - 94: Message #13003: AV Loiter Waypoint ............................................. 139
Table B1 - 95: Message #13004: Payload Action Waypoint ................................... 144
Table B1 - 96: Message #13005: Airframe Action Waypoint .................................. 145
Table B1 - 97: Message #13006: Vehicle Specific Waypoint.................................. 145
Table B1 - 98: Message #13007: Define Contingency............................................. 147
Table B1 - 99: Message #14000: Mission Upload / Download Status.................... 148
Table B1 - 100: Message #15000: Subsystem Status Request .............................. 149
Table B1 - 101: Message #15001: Subsystem Status Detail Request ................... 150
Table B1 - 102: Message #16000: Subsystem Status Alert .................................... 153
Table B1 - 103: Message #16001: Subsystem Status Report................................. 154
Table B1 - 104: Message #16002: Heartbeat Message............................................ 155
Table B1 - 105: Message #17000: Message Acknowledgement ............................ 155
Table B1 - 106: Message #17001: Schedule Message Update Command ............ 156
Table B1 - 107: Message #17002: Generic Information Request Message........... 159
Table B1 - 108: Message #17003: File Transfer Notification .................................. 159
Table B1 - 109: Message #18000: Link Audio Command ....................................... 160
Table B1 - 110: Message #18001: Emitters All Off Command................................ 161
Table B1 - 111: Message #18100: Link Audio Status.............................................. 161
1-B-6
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 112: Message #18101: Emitters Status .................................................. 161
Table B1 - 113: Message #18200: Meterological Table Message........................... 162
Table B1 - 114: Message #18300: Meterological Table Report .............................. 163
Table B1 - 115: Message #18400: KLV Security Configuration Data..................... 165
Table B1 - 116: Message #18401: KLV Security Classification Data..................... 168
Table B1 - 117: Message #18402: KLV Security Classification Comment Data ... 169
Table B1 - 118: Message #18403: KLV Security Image Data................................. 172
Table B1 - 119: Message #19000: Payload Bay Command .................................... 173
Table B1 - 120: Message #19001: Payload Steering Command............................. 177
Table B1 - 121: Message #19100: EO/IR/Laser Payload Command....................... 182
Table B1 - 122: Message #19101: EO/IR/Laser Payload Quality Control .............. 184
Table B1 - 123: Message #19200: SAR Payload Command ................................... 187
Table B1 - 124: Message #19400: Communications Relay Command .................. 190
Table B1 - 125: Message #19401: Load Communications Relay Configuration
Command............................................................................................................. 192
Table B1 - 126: Message #19500: Payload Data Recorder Control Command..... 193
Table B1 - 127: Message #19600: Terrain Data Update .......................................... 194
Table B1 - 128: Message #19700: Payload Operating Mode Command................ 196
Table B1 - 129: Message #21000: Payload Bay Status ........................................... 198
Table B1 - 130: Message #21001: Payload Configuration ...................................... 201
Table B1 - 131: Message #21100: EO/IR Configuration State ................................ 204
Table B1 - 132: Message #21101: EO/IR/Laser Operating State ............................ 209
Table B1 - 133: Message #21200: SAR Operating State ......................................... 212
Table B1 - 134: Message #21400: Communications Relay Status......................... 215
Table B1 - 135: Message #21401: Communications Relay Configuration Status 217
Table B1 - 136: Message #21402: Communication Relay Configuration State .... 219
Table B1 - 137: Message #21500: Payload Data Recorder Status ......................... 220
Table B1 - 138: Message #21501: Vehicle Payload/Recorder Configuration........ 222
Table B1 - 139: Message #21600: Terrain Data Request ........................................ 222
Table B1 - 140: Message #21700: Payload Operating Mode Report...................... 225
Table B1 - 141: Message #24000: Stores Management System Command.......... 228
Table B1 - 142: Message #26000: Stores Management System Status ................ 231
Table B1 - 143: Message #28000: Data Link Control Authorisation Request....... 234
1-B-7
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 144: Message #28001: Data Link Configuration/Assignment
Message ............................................................................................................... 236
Table B1 - 145: Message #30000: Data Link To Vehicle ID Assignment ............... 238
Table B1 - 146: Message #30001: 7085 Data Link Active Configuration Set Up
Message ............................................................................................................... 240
Table B1 - 147: Message #30002: 7085 Data Link Fallback Configuration Set Up
Message ............................................................................................................... 242
Table B1 - 148: Message #30003: Data Link Control Command............................ 243
Table B1 - 149: Message #30004: RF Command Processing Set Up Message .... 244
Table B1 - 150: Message #30100: Antenna Pedestal Location Command............ 245
Table B1 - 151: Message #30101: Antenna Control Command.............................. 247
Table B1 - 152: Message #30102: Antenna Position Command ............................ 249
Table B1 - 153: Message #30200: Link Health Command ...................................... 249
Table B1 - 154: Message #30300: Set Data Link UDP Monitor Period................... 250
Table B1 - 155: Message #30301: IP Address and Port Assignment Request .... 252
Table B1 - 156: Message #32000: Data Link To Vehicle ID Report ........................ 252
Table B1 - 157: Message #32001: 7085 Data Link Active Configuration Status
Report................................................................................................................... 253
Table B1 - 158: Message #32002: 7085 Data Link Fallback Configuration Status
Report................................................................................................................... 254
Table B1 - 159: Message #32003: Data Link Control Status Report...................... 255
Table B1 - 160: Message #32004: RF Command Processing Status Report ........ 255
Table B1 - 161: Message #32005: Legacy Data Link Status Report ...................... 256
Table B1 - 162: Message #32006: Legacy Data Link Control Command Status .. 257
Table B1 - 163: Message #32100: Antenna Pedestal Location Status Report...... 258
Table B1 - 164: Message #32101: Antenna Control Status Report........................ 258
Table B1 - 165: Message #32102: Antenna Position Report .................................. 259
Table B1 - 166: Message #32103: Legacy Pedestal Status Report........................ 260
Table B1 - 167: Message #32200: Link Health Status ............................................. 261
Table B1 - 168: Message #32201: Data Link Fallback Status................................. 261
Table B1 - 169: Message #32300: Data Link UDP Count ........................................ 261
Table B1 - 170: Message #32301: AV IP Disclosure Message .............................. 265
Table B1 - 171: Message #34000: Vehicle Data Link Transition Coordination
Message ............................................................................................................... 267
Table B1 - 172: Message #35000: Handover Status Report ................................... 267
Table B1 - 173: Message #36000: Activity Constraint Message ............................ 269
1-B-8
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 174: Message #36001: Constraint Response Message ........................ 270
Table B1 - 175: Message #36002: Constraint Requests Complete Message........ 270
Table B1 - 176: Message #36003: Constraint Responses Complete Message..... 271
Table B1 - 177: Message #36100: Activity Complete Message.............................. 271
Table B1 - 178: Message #36200: Activity Status Message ................................... 272
Table B1 - 179: Message #40000: Field Configuration Request ............................ 274
Table B1 - 180: Message #41000: Field Configuration Integer Response ............ 281
Table B1 - 181: Message #41001: Field Configuration Float Response................ 288
Table B1 - 182: Message #41002: Field Configuration Enumerated Response .. 295
Table B1 - 183: Message #41003: Field Configuration Unsigned Response........ 299
Table B1 - 184: Message #41004: Field Configuration Character Response ....... 301
Table B1 - 185: Message #41005: Configuration Complete ................................... 303
Table B1 - 186: Message #41006: Integer Enumeration Response ....................... 306
Table B1 - 187: Message #42000: Display Unit Request ........................................ 307
Table B1 - 188: Message #42001: CUCS Resource Report .................................... 308
Table B1 - 189: Message #42002: Manage VSM Windows Message ..................... 311
Table B1 - 190: Message #42003: Report Controllable Element............................ 312
Table B1 - 191: Message #43000: VSM Services Report Message ........................ 313
Table B1 - 192: Message #43001: AV Route Configuration.................................... 313
Table B1 - 193: Message #43002: Remote Windows GUI Definition ..................... 314
Table B1 - 194: Message #44000: Field Change Integer Command ...................... 315
Table B1 - 195: Message #44001: Field Change Float Command.......................... 315
Table B1 - 196: Message #44002: Field Change Enumerated Command ............. 316
Table B1 - 197: Message #44003: Message Parameter Availability....................... 321
Table B1 - 198: Message #46000: Draw Layer Configuration ................................ 321
Table B1 - 199: Message #46001: Draw Layer Update Request / Status............... 322
Table B1 - 200: Message #46002: Draw Layer Control ........................................... 322
Table B1 - 201: Message #46003: Draw Line ........................................................... 323
Table B1 - 202: Message #46004: Draw Simple Polygon........................................ 324
Table B1 - 203: Message #46005: Draw Complex Polygon .................................... 325
Table B1 - 204: Message #46006: Draw Arc/Circle.................................................. 326
Table B1 - 205: Message #46007: Draw Text ........................................................... 326
Table B1 - 206: Message #46008: Draw Arrow ........................................................ 327
Table B1 - 207: Message #46009: Set Cursor Interest ............................................ 328
1-B-9
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 208: Message #46010: Remove Cursor Interest.................................... 328
Table B1 - 209: Message #46011: Cursor Interest Return ...................................... 328
Table B1 - 210: Message #51000: Vehicle Lights .................................................... 332
LIST OF ATTACHMENTS/TABS
Tab B1 - 1: Modified DLI Generic Messages and Private Message Repository for
UVs Edition 3..............................................................................................................258
1 - B - 10
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
1 Introduction.
1.1 Scope.
NATO Standardization Agreement (STANAG 4586) Annex B Appendix B1 specifies
the detailed requirements for interfacing the Core UCS (CUCS) to a Vehicle Specific
Module (VSM). This interface is designated as the Data Link Interface (DLI)
throughout this document.
STANAG 4586 Annex B Appendix B1 is intended to allow NATO nations to enable
UAV interoperability between any compliant CUCS and any compliant air vehicle
system (through its VSM) by specifying a standard set of messages and data formats
for the interface while at the same time providing support for handling vehicle-specific
data needs.
1.2 Appendix B1 Overview.
This Appendix defines the DLI element of the UCS. The DLI provides a common set
of messages and mechanisms for handling vehicle and payload specific messages.
Appendix B1 is divided into the following sections:
Section 1 Introduction
Section 2 System Functional Requirements By Mission Phase
Section 3 Message Distribution Standard
Section 4 Message Formats
Section 5 Miscellaneous Interfaces

1.3 DLI General Overview.
A wide range of air vehicles and control system requirements have been considered
in establishing the DLI message set. The DLI shall be the interface between the
UAV/data link and the CUCS element. The DLI provides standard messages and
formats to enable communication between a variety of air vehicles and STANAG
4586 compliant CUCSs
Defining the DLI generic message structure for the AV/CDT/CUCS communication is
the purpose of this Appendix. The message set defined in this Appendix includes
control and status messages for the following:
Air Vehicle
Payloads
Data Links
Cautions and Warnings
The message set contains UAV data that is vehicle and payload independent, such
that the interface standard is not required to change to accommodate a particular air
vehicle or payload. In addition the message set includes a capability to have the DLI
generate system specific displays through the UCS HCI.
The DLI has two major components. The first component is a generic set of
messages designed to be vehicle and payload independent that support CUCS
functionality, and common air vehicle data needs. The second component is a
mechanism to support communication of vehicle specific information, from the
AV/CDT to the CUCS, to remotely display vehicle-specific information. The
1 - B - 11
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
services methodology allows new vehicle specific elements, and even new
vehicles, to be added to a UCS system without having to modify the CUCS software
components.
The CUCS shall generate and understand common air vehicle and payload
messages using the DLI. The development of a standard message set and protocol
for communication between the AV/data link and the CUCS function is key to
establishing an interoperable CUCS architecture. These messages as defined in this
document are air vehicle and payload independent.
The CUCS and AV/CDT communicate with each other via messages as the primary
method of transferring information between these two components. This messaging
structure has the objective of passing UAV control and status information between
the CUCS and AV/CDT without creating dependencies between the two components.
Messages are used to pass a generic set of data between the CUCS and the
AV/CDT, and this generic data may be acted upon by both the CUCS and AV/CDT
(local host machine). This methodology allows the CUCS to act upon data
originating at the AV/CDT, and then transmits the data to an independent location.
The secondary method of communication between the CUCS and the AV/CDT is the
use of services to pass information between the two components. The services
allow the AV/CDT to affect the HCI on the CUCS, much like a web browser accesses
web pages for locally displaying data residing on a remote host. The AV/CDT-driven
displays include the display of data that is not part of any standard "data" message
sets, and allow the operator to interact with an air vehicle through the AV/CDT to
select options, modes of operation, and other vehicle-specific actions. The CUCS
has no capability to alter or use the content of the remote displays on the local
machine.
There are several ways to implement the DLI in a UAS. The following sections
describe the role of the VSM for implementing the DLI for the air vehicle and data
link.
1.4 Vehicle Specific Module Functions.
In the UCS system functional architecture, the VSM shall be responsible for the
following functions where they are not part of the AV or CDT:
Translating data from the representation used by the CUCS (DLI
defined messages) to vehicle specific representations and vice
versa.
Acting as a repository and server for vehicle-specific data (such as
vehicle configuration and performance limitations) and methods
(such as routines for updating vehicle-specific operator displays).
Packing and unpacking data link data to optimise transmission
bandwidth when necessary.
Managing UAV real-time data and interfaces required to control
and monitor data link(s) operation.
Managing interfaces required to control and monitor launch and
recovery (L/R) systems associated with the respective vehicles.
Analogue to digital conversion of sensor data, if required.
These VSM functions service/support the DLI interface between the CUCS elements
and the air vehicle system. The VSM functions insulate the CUCS from air vehicle,
1 - B - 12
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
data link, launch and recovery (L/R) and real-time air vehicle specific interface
peculiarities, by maintaining closed-loop control and communication with the air
vehicle and its payload(s) following the air vehicles specific protocols, timing and
encoding methods.
To accomplish these functions, the VSM functions can be allocated to various UAS
system components, i.e. CUCS, CDT, VDT, Air Vehicle or a stand alone VSM
system element. It is envisaged that a VSM function will be an embedded processing
element that performs the processing associated with the above VSM functions. The
VSM is envisioned as the element of the UAV system architecture that provides a
migration path for legacy UAV systems to achieve STANAG 4586 compliance with
minimal impact to the air vehicle design.
1.4.1 Example Implementations for the Air Vehicle.
The location of the VSM function may be located in the air vehicle and/or with the
UAV control system. The CUCS shall not contain real-time processes that are
required to support the air vehicle and CDT operation. There are several ways to
implement DLI and this relationship, or architecture, is presented in Figure B1 - 1.
Case 1
Case 2
Case 3
Case 4
UAV
UAV
UAV
UAV
VDT
VDT
VSM
VSM
VDT
VDT
CDT
CDT
CDT
VSM
CDT
VSM
CUCS
CCISM
C4I
Systems
HCI
DLI
Operator
CCI
C4I
Systems
Figure B1 - 1: DLI Role in the AV/UCS Concept

Figure B1 -1 illustrates four air vehicles which support different levels of DLI as its
native language. In Case 1, the air vehicle and CDT support all of the VSM
1 - B - 13
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
functionality as identified in section 1.4.2 below. Vehicle Specific (remote display)
and real-time processing functionality, if required, would be provided by the CUCS. In
Case 2, the air vehicle and CDT dont support any of the VSM functions and require
a VSM to provide this functionality. In Case 3, the VSM functionality, with possible
exception of remote display and real-time processing is allocated to the air vehicle. In
Case 4, the VSM functionality is split between the air vehicle and the ground
elements of the UAS.
1.4.2 Example Implementations for the Data Link.
In the case of systems using a data link that is not compliant with STANAG 7085
(e.g. BLOS/SATCOM), the VSM CDT function shall serve as an isolating interface
that allows the UAV system CDT interface to become STANAG 4586 compliant
without requiring modifications to the air vehicle or the data link.
Case 1
Case 2
Case 3
CDT
CDT
CDT
VSM
VSM
VSM
DLI
Case 4
CDT
VSM
Case 5
CDT
VSM
DLI to CDT
DLI to Air Vehicle
Figure B1 - 2: DLI Role in the CDT/UCS Concept

Figure B1 - 2 addresses the Control Data Terminal (CDT) DLI interface. To show the
functional flow, the AV DLI messages are shown as a separate, dotted line from the
CDT DLI messages. As with the AV, the CDT may understand the DLI messages
and not require a separate VSM. This could be true even if the AV required a VSM of
its own. The CDT could require a VSM and the AV may not require one. Both the AV
and the CDT could both require a VSM and this could be supported by either a single
physical VSM or two separate VSMs.
1 - B - 14
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
U
D
O
W
PL
IN
NL
IN
K
BLOS
Closed-loop
communication
LOS
DLI
VSM
Control of
ground-based
datalink
components
Real-time
Processing
Communication
with the UCS
core processing
suite via DLI
and control
UCS Core
Processing
Suite
Real-time and
Non-Real-time
Processing
Additional A/V spe cif ic functions as re quired (only those outside of UCS Core / Com mon func tions)
Figure B1 - 3: Role of the VSM

Figure B1 - 3 provides another view of the relationship among the CUCS, the VSM,
and the DLI. In this figure, note that real time processing has been allocated to the
VSM which maintains closed loop control with the air vehicle. In addition, it provides
a command and status interface with the data link subsystem. The CUCS, in
contrast, performs its function in non-real time. This is to say that the system is not
bound to a particular latency specification but to a maximum latency for the various
functions and messages as specified in this Appendix. This is a critical distinction
that presumes a reasonable level of automation in the system. For those functions
requiring real time interaction with a human operator, the interfaces to the system will
be directly through the VSM.
The VSM function can reside on the same, different, or even remote hardware with
respect to the CUCS, as long as sufficient bandwidth for the message interface
(including sensor data) can be provided. The intent of this appendix is not to specify
hardware, but to specify in detail the DLI such that interoperability can be achieved.
1.5 Interfaces.
1.5.1 Physical Interfaces.
The DLI (notionally depicted in Figure B1-4) can actually consist of multiple physical
interfaces. At least one full duplex bi-directional digital data interface shall provide a
communication pathway for the following:
Commands to the UAV, payload, data link and VSM
Environmental data to the UAV system elements
Status from the UAV, payload, data link and VSM
Digital payload data from the UAV - depending on data rate
requirements and available bandwidth, digital payload data may
require a separate physical interface to be included in a specific
DLI implementation
1 - B - 15
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Voice communication with ATC, if required, is outside the scope of this STANAG.
Analogue Sensor Data (under

conditions specified in text
below)
CCISM
A/V Telemetry and Digital Sensor Data
VS
A/V, Data link, Payload, and VSM Status
UCS Core
Processing
A/V & Payload Mode/Control

Commands, Environmental Data
Antenna and VSM Commands
Suite
Data Link Interface
Figure B1 - 4: High-Level Depiction of DLI Interface Content

This STANAG envisions an all-digital medium for data; analogue data interfaces are
not within the scope of the DLI. The VSM shall provide analogue to digital
conversion (frame grabbing) services when imagery or other sensor data is
transmitted from the air vehicle in analogue format. Under this circumstance, to
avoid unnecessary translation from analogue to digital and back to analogue when a
C4I system requires analogue video, the VSM shall provide a dedicated physical
interface for displays or for external feeds (through a CCISM).
The physical interface between the CUCS and the VSM functions can differ
depending upon where the VSM functionality is physically located. The VSM
functionality can reside on the ground as part of the UCS and/or as a subsystem in
the air vehicle. When the VSM function is allocated to a component outside the
CUCS, its interface with the CUCS, the physical interface, shall support the TCP/IP
and UDP/IP protocols (e.g., Ethernet (IEEE 802) 10Base2, 10BaseT, 100BaseT,
1000BaseT, fibre, etc.). When the VSM functionality resides in the air vehicle, the
interface to the VDT portion of the data link is defined in STANAG 7085.
1.5.2 System Latency and Real-time Interface Considerations.
In vehicle control systems, designers typically should consider all sources of latency
to ensure satisfactory handling qualities and system stability. This is particularly true
in a UAV system employing manual control of the aircraft. In such systems, a critical
1 - B - 16
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
area of concern is the total latency between the air vehicle and the operator controls
and displays, as this attribute will strongly influence system performance under
manual control.
In the UCS architecture, real-time UAV and data link control functions (when
required) are managed by the VSM. The CUCS performs non-real-time processing,
and the DLI specifies neither fixed nor maximum latency in exchanges between the
VSM and the CUCS. Though message delivery may be guaranteed, latency is not,
and consequently real time performance is not guaranteed for signals passing
through the DLI. In general, the DLI physical medium will have sufficiently high data
rates to support control and display data needs at reasonable rates for human
interaction. However, because the DLI medium may potentially be shared among a
number of VSMs simultaneously, messaging rates and overall bandwidth may tend to
be variable and should not be relied upon.
Several approaches are possible in constituting a UCS-compliant system:
The VSM performs all real-time functionality autonomously, and data
interchange needed to support controls and displays are designed to
be of a non-real-time nature. In this approach, controls and displays
presented to the user are not dependent upon any particular latency.
Changes in latency are managed such that they do not affect
readability of displays or performance of controls. For instance,
integrators in a control stick filter may use dynamic integration time to
avoid changes in the timing of data delivery across the DLI.
The system is designed to take advantage of measured throughput
available through the DLI and in the CUCS using near real time
techniques resulting in no significant delays, but special provisions are
incorporated to sense and accommodate excessive latency. This
approach is somewhat risky in that the CUCS hardware configuration
is variable and some configurations may not support a given function
or approach.
Certain manual controls and displays are critical and will be serviced
with no noticeable delays (isochronous) process. In this case,
processing is performed in the VSM and device interfaces are
managed directly by the VSM without passing through the DLI
logically or physically. This approach might be used by legacy
systems and UAVs that do not have the sophistication to perform
autonomous operations.
In the case where the VSM is housed in the aircraft, the CDT shall have a DLIcompliant interface and autonomously perform real time control of the data link.
1.6 Tailoring by Interoperability Level.
The applicability of the messages within the complete DLI message sets vary with
the selected interoperability level and the selected UAV System functionality. For
example, vehicle steering commands are inappropriate at Levels of Interoperability
(LOI) 1-3 (as defined in Annex B). The CUCS shall filter messages and respond to,
as well as issue, only those messages that are applicable at the currently authorized
LOI. The definition of the authorized LOI is contained later in Table B1 - 5, which
define applicability of each message.
1 - B - 17
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
LOI 3 monitor only and LOl 3 control and monitor are divisible on a per payload
station basis for an air vehicle where there is more than one payload (station) located
onboard the air vehicle.
LOI 4 is for the air vehicle alone, and does not include payload monitor only or
control and monitor, as that capability is specified as LOI 3 respectively. A CUCS
controlling both the air vehicle and its payload is exercising LOI 3 and LOI 4 control.
1.7 Philosophy of Interface Data Representation.
The approach adopted for creating the Interface Data Representation for a message
is outlined in the following sub-sections. The general requirements for the generation
of a message are identified and each message is defined in detail in Section 4. It is
recommended that these requirements be complied with whenever possible in the
specification of new messages.
1.7.1 Byte Ordering.
The byte ordering shall be most significant byte first.
Floating point numbers shall be as defined in IEEE Standard for Binary Floating-Point
Arithmetic, ANSI/IEEE Standard 754-1985, Institute of Electrical and Electronics
Engineers, August 1985.
1.7.2 Units.
Due to the variety of possible UAV systems envisioned in the future, and the
international nature of the interoperability planned for the UCS, the philosophy for
developing the message types in the DLI shall be to use metric (SI, ISO/IEC 80000)
units wherever possible. The DLI is a system-internal representation only between
the CUCS and the VSM, and therefore any conversions required for human
readability or familiarity (e.g., metres/second to knots) can be performed at the
appropriate user interface.
All earth-fixed position references shall be expressed in the latitude-longitude system
with respect to the WGS-84 ellipsoid in units of radians using Binary Angle
Measurement (BAM). Representations in other systems, such as Universal
Transverse Mercator (UTM), shall be converted at the point of use. All times shall be
represented in Universal Time Coordinated (UTC) in seconds since Jan 1, 2000
using a 5 byte unsigned integer where the least significant bit represents 0.001
seconds. In 2034 and in subsequent years, when the maximum value of the five byte
field is exceeded, the timestamp shall roll over and numbering shall restart at zero.
All angular parameters shall be expressed in radians. Bearings shall be measured
clockwise from true north. Elevation shall be referenced from local horizontal,
positive toward the zenith.
Data quantities, where specified in megabits (or megabytes), shall be specified as
1,000,000 bytes (or bits) instead of 220. (Reference: Amendment 2 to International
Standard IEC 60027-2: Letter symbols to be used in electrical technology - Part 2:
Telecommunications and electronics (Jan 1999).)
1.7.3 Approach to Packaging Command Data.
The general intent for packaging data was to strike a balance between minimizing the
overhead associated with message headers while maximizing the modularity of the
message set. In addition, the further intent was to categorize data into logical
messages combinations, such as inertial data vs. body-relative data vs. wind-relative
1 - B - 18
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
data when referring to vehicle state. Command and status data are kept in separate
message groups to separate uplink messages from downlink messages. Data for
which some sort of acknowledgement receipt is generally required are separated
from status information requiring no acknowledgement. Finally, an attempt is made
to keep data from appearing in multiple messages to avoid the possibility of
inconsistencies.
Unless specifically stated, a zero fixed point value is equal to a zero real value (i.e.,
no bias or offset). In the cases where the range limit values cannot be perfectly
represented by the fixed point representation, the fix point value closest to, but not
exceeding the real limit shall be used. For angular measurement values, Binary
Angle Measure (BAM) may be used. The fixed point scaling for BAM is a function of
the field size and is defined as / 2(n-1) radians, where n is the bit-width of the field
For an Integer field, this provides a real range of - inclusive to exclusive, and for
an Unsigned field, a real range of 0 inclusive to 2 exclusive.
1.7.4 Concept for Autonomy.
Autonomous behaviour to be provided by the VSM and/or air vehicle is described
using activity identifiers in messages that specify vehicle, payload or data link
activities. As depicted in Figure B1-5, each activity that the CUCS requests of the
AV/VSM may be immediate or may be part of a set of goals, behaviours and
constraints that the CUCS may communicate to the AV/VSM. An activity with an
Activity ID value of zero is an activity that the vehicle, payload or data link is to
perform immediately. An activity with a non-zero Activity ID is part of a set of goals
behaviours and constraints. Message numbers 36000 through 36003 are used to
specify the constraints to be applied to the activities with non-zero Activity IDs.
Messages 36100 and 36200 are used to describe activity status from the VSM to the
CUCS during mission execution. The 36000 series of messages are also used by
the AV/VSM to communicate its ability to comply with the requested constraints.
During initialization and discovery, the AV/VSM shall indicate whether or not it
supports the Activity ID field for each activity message. If a AV/VSM indicates that it
doesnt support an Activity ID field for a particular activity, then the only AV/VSM
supported operation for that activity is immediate (Activity ID = 0).
To implement autonomous operations for an AV/VSM that supports non-zero Activity
IDs, the CUCS shall send a set of activities with non-zero Activity IDs to the AV/VSM.
For each non-zero Activity ID the CUCS shall also send one or more activity
constraint messages to the AV/VSM indicating the constraints describing the
conditions under which the activity is to be performed. After sending all of the
activities with non-zero Activity IDs and all of the constraints messages for those
activities, the CUCS shall send a constraints complete message. After receipt of a
constraints complete message, the AV/VSM shall send a constraint response
message for each constraint message received from the CUCS. The AV/VSM shall
send an Activity Status Message for each activity whose constraints are marked as
"satisfied" in the associated constraint response message. After all of the constraint
responses have been sent, the AV/VSM shall send an activity status message for
each activity whose constraints have been "satisfied". Finally the AV/VSM shall send
a constraint responses complete message.
Note that Activity IDs can be referenced in more than one constraint message, but
constraint IDs cannot be reused. Activity IDs will be reused if multiple constraints are
to be applied to the same activity. For example, if an activity is to occur before
1 - B - 19
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
waypoint 9 that could be specified in a constraint message and if the same activity is
to occur after waypoint 3 that would be specified in a second constraint message, but
both constraint messages would refer to the same Activity ID. If the activity would
not be executed because one of the constraints could not be satisfied, it is necessary
for that Constraint ID to be uniquely identified so that the user knows why the activity
will not occur.
During the execution of the mission, if the AV/VSM determines that constraint
satisfaction conditions have changed, the AV/VSM shall send a constraint response
for each constraint whose satisfaction condition has changed, followed by an activity
status message for each activity whose status has changed and then the AV/VSM
shall send a constraint responses complete message. This means that if conditions
have changed so that either:
1. an activity that was to have been performed will not be performed
or
2. an activity that was not to have been performed will be performed
the AV/VSM shall send a constraint response message for each activity where
condition 1 or 2, above, has occurred and shall send an activity status message for
each activity where condition 2 has occurred and shall then send a constraint
responses complete message.
CUCS
Multiple Activities (Activity ID 0)

Multiple Activity Constraint Messages 36000
Single Constraints Complete Messages 36002

Multiple Constraint Response Messages 36001
Multiple Activity Status Messages 36200
Single Constraints Responses
Complete Messages 36003
Multiple Activity Complete Messages 36100

(During Mission Execution)
Figure B1 - 5: Autonomy Message Flow

1 - B - 20
AV/VSM
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
1.7.5 Concept for Display of Vehicle Specific Data.
There is a requirement to control and monitor an air vehicle through the generic DLI
message set, identified in Section 4 of this document. The generic message set
provides the capability for a qualified operator to control and monitor a significant
percentage of air vehicle functions through the use of generic control panels and
dialogs. The VSM is required to support all the formatted DLI messages that are
applicable to the air vehicle for which it has been developed. All data elements
contained in the generic message set that are applicable to the air vehicle are
therefore available to the CUCS, and are able to be displayed as required in the
generic displays, and allow for control of the generic air vehicle functionality by a
qualified operator.
There are control and monitoring requirements that an air vehicle may require that
are not provided for through the generic DLI message set, as they are not considered
to be generic to all air vehicles. There shall, therefore, be a capability to provide
additional operator displays and controls for these vehicle specific functionalities.
This capability is identified as the remote display capability or vehicle specific
mechanism.
The DLI enables the VSM to display information on the CUCS, for example:
Vehicle specific displays show status
Vehicle specific displays allow the selection of options and modes of
control
Vehicle specific displays are independent of the CUCS capabilities,
except for specified generic services (e.g., a change in VSM capability
should not be limited by the CUCS capability)
Vehicle specific displays are controlled by the CUCS
Vehicle specific display information is passed through the DLI
interface
Vehicle specific data intent should be maintained
It is important to note that the CUCS does not know the intended usage of the vehicle
specific parameters, and is not able to manipulate the vehicle specific parameters.
The vehicle specific data is remotely displayed on the CUCS displays. The content
and arrangement of these displays is controlled by the VSM, and the displays are
therefore tailored to a specific air vehicle. The VSM process is controlling specific air
vehicle functionality and providing status information for these specific processes
through these remote displays.
1.7.5.1 Vehicle Specific Display Services.
For generating the remote displays according to the requirements identified in this
section of the document, the following services shall be supported. The display
formats are determined by the VSM. The following services are the minimum
requirement of the CUCS platform to support interoperability with all VSMs and the
maximum allowable for the VSM platform that shall be supported for interoperability:
Web Browser Services shall be compatible with:
- http://www.w3.org/TR/2008/REC-CSS2-20080411/
Cascading Style Sheets, level 2
W3C Recommendation 12 May 1998, revised 11 April 2008
1 - B - 21
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
-http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/
Document Object Model (DOM) Level 3 Core Specification
Version 1.0
W3C Recommendation 07 April 2004
- http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/
Document Object Model (DOM) Level 3 Load and Save Specification
Version 1.0
W3C Recommendation 07 April 2004
- http://www.w3.org/TR/2008/REC-ElementTraversal-20081222/
Element Traversal Specification
W3C Recommendation 22 December 2008
- http://www.w3.org/TR/html4
HTML 4.01 Specification
W3C Recommendation 24 December 1999
- http://www.ecma-international.org/publications/files/ecma-
st/Ecma- 262.pdf
Referred as to Jscript or JavaScript
ECMA Script 262 or ISO/IEC 16262 5th Edition December 2009
- Java applet mechanism shall be compatible with:
- Sun Microsystems Compliant JRE V1.6 or superior version
The Java applet mechanism shall be integrated with the Web Browser
Service.
- The X-Server Services shall be compatible with:
- X11R6 X Window System Release 6
- http://www.x.org/releases/X11R6.9.0/
1.7.5.2 Vehicle Specific Display Requests and Presentation.
Vehicle Specific (remote) displays are initiated by the CUCS making a request to the
VSM, through the mechanisms provided by the generic formatted DLI message set.
The Remote Display philosophy is that the generic control panels shall be displayed
to the operator prior to requesting the remote displays, and the CUCS shall have
been authorized control of the specified AV. To initiate the transmission of the
remote displays from the VSM, the CUCS shall transmit Message #42001, CUCS
Resource Report, to the VSM. The VSM shall transmit the required Vehicle Specific
control panels after the reception of the CUCS Resource Report message. The
CUCS Resource Report provides the VSM with the details of where to transmit and
locate the remote displays.
As identified previously, the CUCS is required to contain a browser, an x-windows
display capability, and a Java run-time environment in accordance with Section
1.7.5.1 Vehicle Specific Display Services. The positive control over the remote
services shall be a CUCS responsibility, to include the security settings for these
1 - B - 22
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
services. It is a CUCS responsibility to ensure adequate services are selected for the
remote displays. As an example, for the web browser service this means that the
selected browser must have adequate security settings to disallow un-requested
windows from popping up on the system; potentially have the capability to hide the
close button; and disallow the resizing of the remote display windows, etc.
Vehicle specific displays can be used to request additional vehicle specific displays.
When these additional vehicle specific displays are required, they shall be initially
displayed within the resources allocated by Message #42001 or within the window
from which it was requested. A second method of an operator initiating remote
displays from the VSM is through the use of the STANAG 4586 Subsystem State
Report Reference field of Message #15001, Subsystem Status Detail Request.
These processes ensure that the operator must request all remote panels for display
thus maintaining positive control over the displays.
Remote Displays shall not be initiated by the VSM via Message #16000 or #16001
until the CUCS Resource Report has been transmitted to the VSM.
VSM shall use remote services that transmit remote displays to the CUCS in
accordance with Message #42001, CUCS Resource Report. This provides a second
level of security to ensure remote displays are displayed where expected on the
CUCS displays, and not covering critical data.
Refer to Section 4.25.2 Message #42001: CUCS Resource Report for additional
requirements.
Figure B1-6 below provides a representation of how the remote displays are
generated using the subsystem reference report. The generic displays will identify a
warning condition and any requirement to place a vehicle-specific display on the
CUCS display screens. The additional information will usually be information specific
to the air vehicle and not provided through the generic message set.
In Figure B1-6, a generic warning indication is provided to the operator in the generic
displays identifying a problem with Engine #2. An enunciator flashes to indicate to
the operator that an engine warning state exists, and identifies a more detailed
display is available to the operator. The operator may request the additional
information by clicking on the enunciator, which then generates a request to the VSM
through the generic message mechanism, requesting the detailed Engine #2 status
information. The VSM then transmits the required information to the CUCS through
the vehicle-specific mechanism implemented for the air vehicle. The CUCS then
displays this information to the operator in a controlled manner.
1 - B - 23
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
5: Window pops up in
which vehicle-specific
engine status display
is drawn
1: Warning Light
flashes in standard
display area
2: User clicks on light
for more information
CUCS
VSM
3: Generic Engine 2
Status Request is
sent to VSM
CUCS
VSM
4: Engine-specific
display data is
formatted and returned
Figure B1 - 6: Typical Scenario for Generating Vehicle-Specific Displays
The vehicle specific mechanism provides the capability to create CUCS displays for a
specific air vehicle, without having to present data that is specific to a particular
vehicle in a set of generic displays, thus eliminating unnecessary clutter from the
displays. This capability also eliminates the need for the CUCS to carry around large
libraries of display functions for many different types of air vehicles that would be
difficult to keep current. In this concept, the VSM is responsible for providing the
information necessary for detailed system management functions, and that
information remains hidden from the operator until needed.
1.7.6 Vehicle, Data Link, and CUCS Identification (ID) Numbers.
Each message shall contain fields that specify the identification (ID) numbers for the
two units (e.g., air vehicle and CUCS) that are communicating with one another.
Some messages also contain the Data Link ID. The destination ID may be set to the
ID of a VSM in advance of a connection to an air vehicle, payload or a data link. The
purpose of these numbers is to uniquely identify any entity in an arbitrarily formed
system combining multiple CUCS, air vehicles, and data links all potentially
interacting with VSMs which may control zero or more vehicles at a time. A VSM that
controls zero air vehicles might require connection to a CUCS in advance of
receiving an air vehicle handover from another STANAG 4586 ground station.
ID numbers shall be formed as 4-byte numbers. The first (most significant) byte shall
be the Owning ID for that CUCS or air vehicle. The Custodian of STANAG 4586 may
assign Owning IDs and identify an associated authority for the Owning ID at its
discretion. Two-hundred and fifty five (255 (hexadecimal FF)) shall be reserved. The
1 - B - 24
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
remaining three bytes shall be assigned according to procedures and protocols
identified and maintained by the authority associated with the Owning ID to assure
unique ID numbers for each in-service device.
The purpose of these numbers is to uniquely identify any entity in an arbitrarily
formed system combining multiple CUCS and multiple vehicles with multiple
interacting VSMs, each of which may control one or more vehicles at a time. The
following table assigns an integer for each Owning ID. Please contact the Custodian
of 4586 for future assignments or changes.
Owning ID
Assigned Number
BELGIUM
BULGARIA
CANADA
CZECH REPUBLIC
DENMARK
ESTONIA
FRANCE
GERMANY
GREECE
HUNGARY
ICELAND
ITALY
LATVIA
LITHUANIA
LUXEMBOURG
NETHERLANDS
NORWAY
POLAND
PORTUGAL
ROMANIA
SLOVAKIA
SLOVENIA
SPAIN
TURKEY
UNITED KINGDOM
UNITED STATES
PfP
ALBANIA
ARMENIA
AUSTRIA
AZERBAIJAN
BELARUS
CROATIA
FINLAND
GEORGIA
IRELAND
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
100
101
102
103
104
105
106
107
108
1 - B - 25
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Assigned Number
Owning ID
KAZAKHSTAN
KYRGYZSTAN
REPUBLIC of MOLDOVA
RUSSIAN FEDERATION
SWEDEN
SWITZERLAND
TAJIKISTAN
TURKMENISTAN
UKRAINE
UZBEKISTAN
Other
Israel
109
110
111
112
113
114
115
116
117
118
119
Table B1 - 1: Owning ID Table
Each STANAG 4586 compliant Air Vehicle, data link, and CUCS shall be assigned a
unique system ID within its respective type. Among the three types (A/V, data link, or
CUCS), devices of different types may have an identical ID number, but this should
be avoided where possible. If sharing of numbers across types is used, it shall be
according to the member nations procedures.
In this document and in the accompanying Implementation Guide, ID numbers will be
represented as individual hexadecimal bytes separated by colons (e.g.,
10:4E:F3:06). ID number FF:FF:FF:FF shall be reserved as a broadcast ID referring
to all vehicles, and FF:00:00:00 shall be reserved as a null ID. 0.xx.xx.xx shall be
reserved for logical IDs that describe a logical air vehicle that does not have a
specific instantiation. These logical IDs are defined by the VSM manufacturer. ID
Number 00:00:00:00 is reserved and indicates that this field is not applicable.
Each STANAG 4586 compliant device shall be responsible for maintaining a
permanent record of its ID number and being able to provide its ID number upon
request. For air vehicles and data link systems not possessing assigned IDs, the
VSM employed to interface with that system shall maintain a correspondence
between devices and assigned ID numbers.
An AV/payload or data link directly receiving a CUCS Authorisation Request
Message (Message #1, see Section 4.2.1) with a broadcast request ID, will respond
with at least one VSM Authorisation Response Message (Message #2, see Section
4.2.2), and more than one if more than one payload entity type/subtype combination
is controllable through the AV.
A VSM receiving a CUCS Authorisation Request Message (Message #1, see Section
4.2.1) with a broadcast request ID, will respond with at least one VSM Authorisation
Response Message (Message #2, see Section 4.2.2), and more than one if more
than one AV/ payload entity type/subtype combination is controllable through the
VSM. When a VSM is not connected to an air vehicle/ payload the vehicle ID field
shall be filled with a distinct logical vehicle ID. A distinct logical ID shall be reported
up to the number of vehicle entities that the VSM can control/ monitor.
A CUCS, VSM, data link and AV shall only respond to messages addressed to it.
Broadcast IDs are addressed to all units and each unit shall respond to those
1 - B - 26
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
messages as required. A unit responding to a specific message shall set the
Destination ID to the ID of the requesting unit. If a CUCS is in the monitor mode for a
given LOI, it shall process and display all downlink data for that LOI from the desired
unit regardless of the destination ID. If a CUCS is connected to an AV, data link or
VSM in monitor mode, the AV, data link or VSM shall only set the destination ID to
the monitoring CUCS if the message is in direct response to a specific request (e.g.,
a Message #41000 in response to a Message #40000).
1 - B - 27
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
2 System Functional Requirements By Mission Phase.
The DLI data content is determined by the functional requirements of the CUCS and
VSM needs to communicate with one another. The set of common functions and
vehicle/payload specific functions from which data elements of the DLI are described
can be found in detail in Section 4. Functionality is categorised by the phase of a
UAV mission. Within each mission phase, functionality is identified as either
common (meaning consistent across all vehicle and payload types) or vehiclespecific. In most cases, vehicle specific functions are those that vary either in
procedure or in data content and will require interaction between the CUCS and the
VSM to how those functions are to be performed. The functions within each of the
phases of the UAV mission are described in the table below.
1 - B - 28
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Mission Phase
Common Functions
Vehicle-Specific Functions
Pre-flight
Interoperable Mission Planning

Mission Plan / Verify Upload
Process.
Common Built-In-Testing (BIT).
Mission Go / No-go
Vehicle Availability.
Flight Plan Validation.
Lost Link Strategy.
Vehicle Specific BIT.
Payload Configuration Validation & BIT
checks.
Pre-flight Checkout and Initialisation.
Downloaded Mission Plan Validation.
UCS/Vehicle Communications.
Clocks Synchronization (Air Vehicle & UCS).
Takeoff
Local ATC Communications.

Checklists Complete Validation.
UCS/UAV Communications
Validation.
Takeoff Clearance Acquisition.
Ground Traffic Pattern/Plan Execution.

Ground Operations Safety Constraints
Monitoring.
Launch.
Abort Sequence Management.
Ingress / Egress
Mission Execution Monitoring.

Active Emitters (e.g., radar)
Activation.
UAV Vehicle-Specific Handover Data

Management.
Prime Mission Area

(Target Area)
Generic Payload Control.

Payload Data Handling.
System Status Summary
Information.
Detailed System Status Monitoring.

Payload Specific Control & Monitoring.
Payload Specific Data Handling
Approach / Landing
ATC Coordination.
Recovery Procedures Execution.
Approach Flight path Acquisition and

Maintenance.
Landing Sequences Execution.
Taxi Sequence Execution.
Shutdown / Safing Checklists & Procedure
Execution.
Post-Mission Reporting
Mission Execution Summary

Report.
Vehicle Maintenance Status Report.
Phase-independent Inflight
UAV handover among UCSs

Management.
Mission Phase Monitoring.
General Health & Status Monitoring
(H&SM) and Warning.
Dynamic Flight Path Replanning.
Multiple (Possibly Different) Aircraft
Control.
Data Recording / Buffering.
CDT Control, Status, & Initialisation.
Detailed Health & Status Monitoring.

Lost Link Strategy Execution and Monitoring.
Operator Control Modes Management.
CBIT (Continuous Built-In-Tests) Across
Subsystems.
Differential GPS Corrections.
Table B1 - 2: Common vs. Vehicle Specific Functions by Mission Phase
1 - B - 29
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
3 Message Distribution Standard.
3.1 Introduction.
A primary goal of the Core UAV Control System (CUCS) is to provide a set of functions that
are common among many different vehicle platforms and different C4I systems. Some of
the functions of the CUCS include providing connectivity with various national C4I systems,
providing standard controls and displays for qualified users with an appropriate training
background to operate differing air vehicle platforms, providing standard operations and
maintenance displays, and providing a common basis for battle space awareness and
mission management. However, to perform the full range of its functions in a manner that is
truly interoperable among different vehicle platforms and varying external ground-based
systems, the CUCS should have a consistent, common way of obtaining input from and
providing output to external systems. A common language for expressing key information
has to be established that is both robust enough to support a full range of functions as well
as flexible enough to adapt to a rapidly changing technology environment. The DLI in
particular should address this problem, as it shall serve as the point of contact between
vehicle specific systems and the CUCS.
A common approach to providing inter-process (and inter-processor) communications is a
technique known as message passing. In a message passing system, data serving a
common purpose is aggregated into structured packages that are commonly understood by
both sender and receiver. A system for transporting messages, assuring proper delivery,
and managing allocation of resources, as well as a standard definition for how data is
packaged and formatted, is all that is required. If a commonly available library of functions is
provided for these services, robust integration can be achieved at relatively little extra cost
and with very little interaction among disparate development teams. Properly defined, this
technique of formatting, packing, transmitting, parsing, and interpreting information can be
as flexible, detailed, and robust in application as needed. If defined as an open standard, it
can assure interoperability among independently developed systems.
This section provides a definition for message content and handling methods within the
CUCS. In general, inter-process communications shall be implemented as message
transactions in which data is sent in half-duplex mode from one process to another.
Data communications within a given process may be managed by whatever means the
developer chooses, consistent with sound software engineering practices. Interoperability
between tasks within a process is entirely within control of the developer because
performance constraints may not always permit messaging system overhead.
3.2 Requirements.
A message handling structure shall, as a minimum, consist of the following elements:
Definition of structured data format and content for standard information.

o
For information supporting common functions within the CUCS that is

supportable across multiple system types, a set of messages are defined
that specify the variables, values, data formats, and locations within the
message to permit efficient handling of the information according to a
consistent scheme. This structure should not be burdened by vehicle or
system specific baggage, and shall encompass only that which serves a
common purpose. This structured data definition should not unduly
burden message passing with unnecessary data.
1 - B - 30
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
A means for transmitting unstructured data.

o
A means of managing transport of messages of any type.

o
Some information will have to be exchanged between air vehicle and

ground processing elements that support platform-specific functionality. A
generalized messaging scheme shall be capable of passing data for
which the format and content of the message are unknown to the CUCS
but through which the data should pass.
A variety of message types will have to be supported, and a means for
distinguishing among types for proper processing shall be defined.
Furthermore, UAV systems will have multiple channels for transporting
information among system components, and the messaging system has
to be capable of managing messages passing among multiple sourcedestination pairs across multiple communications channels.
A means for managing multiple (possibly redundant) channels of communications

among multiple processes.
o
This requirement has several different flavours. Data may need to be

replicated across multiple channels for the sake of redundancy. Data may
need to be passed from one process to a sole recipient (private
communication) or from one process to many (broadcast communication).
To assure interoperability and portability among environments, the means
of transporting and routing messages shall be independent of the physical
transport mechanism used (e.g., Ethernet, dedicated serial port, Unix
sockets) and transport protocol (either TCP/IP or UDP, depending on the
port used).
In the case where data integrity must be formally checked, a transport

independent means of checking it should exist.
A means of cataloguing an expanding set of message types and tracking

changes needed to support evolving technology.
o
UAV technology is rapidly evolving, and a static system definition will soon
become obsolete. Therefore, provision shall be made for supporting a
continually evolving set of message types. This catalogue should not only
support the definition of the message types, but to be maximally useful it
shall also support an open source library of methods for handling new and
evolving message types.
3.3 Message Handling Approach.

3.3.1 Message Wrapper Information.
Each message shall use the message wrapper structure defined in Table B1-2. The header
contains information that enables the message handling software to manage transmission
and distribution of the messages to the appropriate entities. The footer contains the
checksum information that assists identifying transmission errors. The following sections
provide a description of each of the data items in the wrapper and its role in the message
handling system.
1 - B - 31
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Source Port*
Destination Port*
Packet Length*
UDP Checksum*
Sequence #
Message Length
Source ID
Destination ID
Message Type
Message Properties
Data (Message Payload)

Optional Checksum
Figure B1 - 7: Message Wrapper Structure
Special Notes: Unless otherwise noted, all header entries described below shall be 16-bit
unsigned integers.
A * indicates a UDP header field and is shown in Figure above to illustrate the complete
message header including the UDP header. The application layer message wrapper starts
with Sequence # and ends with Optional Checksum.
3.3.1.1 Source Port.
Field of standard UDP header.

3.3.1.2 Destination Port.

3.3.1.3 Packet Length.

3.3.1.4 UDP Checksum.

3.3.1.5 Sequence #.
The purpose of Sequence Number was to provide a means for segmenting data from a
single message into sequences of blocks of a maximum length. This field is not used and
shall contain - 1.
3.3.1.6 Message Length.
The length shall be a 16-bit unsigned integer of the number of bytes in the Message Data.
The length shall be any number between 1 and 528.
Note. The UDP protocol under IPv4 has a guaranteed minimum datagram size of 576 bytes
that must be supported by all implementations. Subtracting the IPv4 header size of 20 bytes
and the UDP header size of 8 bytes, leaves 548 bytes as the maximum amount data that
can be sent in a datagram that will guarantee interoperability. Therefore, no message or
multi-message datagram shall exceed this data limit. Subtracting the message wrapper size
1 - B - 32
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
of 20 bytes, gives 528 bytes as the maximum message length of a single message with no
room for another message in the datagram. Extra care should be taken when packing
multiple messages in the same datagram.
3.3.1.7 Source ID.
Source ID shall be the ID number of UAS element which is originating/transmitting the

message, e.g., air vehicle for downlink messages. ID formation shall be consistent with
Section 1.7.6.
3.3.1.8 Destination ID.
The Destination ID shall be the ID number for the UAS element for which is the intended
recipient of the message, e.g., CUCS for air vehicle downlink messages. ID formation shall
be consistent with Section 1.7.6.
3.3.1.9 Message Type.
The message type is a 16-bit unsigned integer value associated with the defined messages
types below. Message types shall be numbered as shown in Section 4.1.1. It is anticipated
that the number of standard message types may grow and that NATO will establish a
commission to maintain configuration control on changes to the standard message list. For
vehicle specific messages (private), the number range is specified in Section 4.1.1.27.
3.3.1.10 Message Properties.
Message Properties is a Bitmapped field with four subfields. The most significant bit shall be
used to indicate whether or not receipt of the message shall be acknowledged. When the bit
is 1, an acknowledgement shall be sent: if 0, an acknowledgement shall not be sent. The
next seven bits (bits 14:8) shall indicate the IDD version number.
No
ACK
= 0,
ACK
=1
Version
Range 0127
Draft STANAG 4586
Edition 3 for Ratification = 30
Future Drafts/Editions31 -127
15 14 13 12 11 10
Checksum
Length
No
Checksum
=0
2 bytes = 01
4 bytes = 10
Reserved for Future

Use
Figure B1 - 8: Message Properties Field Definition
Each message shall contain the version identification of the Interface Definition Document
(IDD) from which its structure was defined. This version identification shall be placed in a
fixed 7 bit field. Version identification management shall be used by error checking functions
to validate format consistency. Table B1-3 shows the current version of the IDD that has
been assigned.
1 - B - 33
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
STANAG 4586 Document Version
IDD Version
Identification
STANAG 4586 Edition 3
30
Table B1 - 3: IDD Version Identification
Checksum Length
Checksum
00 bin = "0"
No Checksum is used
01 bin = "1"
2 bytes
10 bin = "2"
4 bytes
Table B1 - 4: Checksum Length
3.3.1.11 Optional Checksum.
In addition to the UDP checksum (part of the UDP header), Optional Checksum may be
employed to determine the presence of errors during transmission or handling of messages.
The use of optional checksum and its length, i.e. 2-byte or 4-byte, is specified by the
checksum length field of Message Properties as illustrated in Table B1 - 4. The checksum is
an unsigned integer and calculated by simple, byte-wise unsigned binary addition of all data
contained in the message excluding the checksum, and truncated to 2 or 4 bytes.
1 - B - 34
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4 Generic (Common) DLI Message Overview.
4.1 Common Message Properties.
The Message Summary and Properties Tables (Tables B1 - 6 B1 - 33) in this

section define the required messages that shall be implemented in order to enable
the desired UAV NATO LOI via the DLI. Control systems will have a set of common
commands and requests for the air vehicle, such as air vehicle or payload operating
commands. The primary purpose of this section is to define the set of generic
(common) messages for communicating across the DLI interface between the
VSM/AV/Data Link and the CUCS. The information contained in the messages will
be used for the display and control of functions common to a STANAG 4586
compliant UCS implementation. The intent of this Appendix is to provide an
expandable structure and preliminary set of message definitions that can grow with
UAS technology.
The goal of the common message set is to provide standard information and the
functional groupings required by a CUCS for use in displays that can be made
common to all UAVs monitored or controlled by that CUCS. Provisions are also
made for the development and use of vehicle-specific (private) message types and
remote displays. Manufacturers may provide any amount of information, whether or
not redundant with the common message types, as required by their particular
design, but must still support the generic messages that contain that data. The
generic (common) message types for a functional grouping shall be supported by the
VSM (vehicle, payload, data link) regardless of where that functionality is allocated,
e.g. Vehicle, CUCS, etc., for a STANAG 4586 system to guarantee interoperability
and be considered a compliant implementation. As not every data element in the
applicable generic messages are required by the VSM (vehicle, payload, data link) in
every application, the general configuration messages allow the identification of
unsupported data elements within a message or of non-support for a complete
message within a functional grouping.
Receiving processes shall perform range checking and properly handle out-of-range
values for their system. The generic messages provide the capability to modify the
ranges and contents of the generic message data elements to specifically tailor a
message to the UAV system as applicable. Out of range values, invalid data and
non-supported messages shall not cause the CUCS/VSM to be adversely affected if
received by the system.
All the messages detailed in Section 4.1.1 below start with a presence vector. The
presence vector provides the sender a method to not send data that is not applicable
in the current message context or is not supported, thereby potentially saving
transmission bandwidth and processing time. Fields which are not supported are
disabled during configuration prior to using presence vectors to remove the fields
from a message. Fields which are not used or are not relevant per values in other
fields in the message can be eliminated using the presence vector without prior
configuration. Other uses of the presence vector are not supported. Specifically, the
presence vector shall not be used to omit data that is unchanged or stale.
The presence vector is a Bitmapped field indicating which fields in the remainder of
the message are present in that message. Each bit represents a specific field. A 1
in a given bit location indicates that the field is present, and a 0 indicates that the
1 - B - 36
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
field is absent. For example, a message containing ten fields would have a two-byte
Presence Vector. For messages that are variable in length, the repeated fields and
the repeat count field if contiguous are mapped to a single bit. The least significant
bit indicates the presence of the time stamp (field 1); the next more significant bit
indicates the presence of the second field, etc.
The first field after the presence vector is the time stamp indicating the time the
message was created, not necessarily the time at which the data was current or
accurate. For those data where unknown latency may cause a problem, it is
recommended that a time of validity also be included in the private message
indicating the time of validity of the data.
The message tables contained in this section of the document define functional
groupings that shall be supported by the CUCS. These tables also shall be supported
by a VSM if the NATO UAV LOI and functional group is supported by the UCS
system.
The lack of a field in a message only indicates that no data is present; it does not
imply that the field is not supported. If data is needed, but the field is not present, the
receiving unit should assume that the last data it received is still valid, though
possibly less fresh. While STANAG 4586 does not require that all data be sent in a
message, it does not preclude it. There may be requirements imposed by the
procuring agency that will require sending data even if it has not changed. These
requirements may be the result of safety concerns that require all associated data to
reside in a single transmitted message.
4.1.1 Common Message Functional Groups.
In the development of the STANAG 4586, the generic (common) messages have
been grouped and numbered according to their functionality. These groups of
messages are defined as Functional Groups. The currently defined Functional
Groups are as follows:
a.
b.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
m.
n.
System ID
Flight Vehicle Command
Flight Vehicle Status
Flight Vehicle Payload Relevant
IFF Command
IFF Status
ATC Interface Command
ATC Interface Status
Vehicle Auxiliary Command
Vehicle Auxiliary Status
Mission Command and Status
Subsystem Status
Miscellaneous Messages
Payload Command
1 - B - 37
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
o.
p.
q.
r.
s.
t.
u.
v.
w.
x.
y.
z.
aa.
Payload Status
Weapons Command
Weapons Status
Data Link Discovery
Data Link Command
Data Link Status
Data Link Transition
General Pre-connection Configuration
General Post-connection Configuration
Autonomy
VSM Forced Commands
Draw Interface
Private Messages
The applicability of the messages within the complete DLI message set varies with
the selected interoperability level (LOI) and the selected UAV System functionality.
The following table is a summary of the requirements to implement each of the
functional message groups to achieve a specific LOI.
The LOI columns in the table associate the functional message groups with the level
of control the CUCS has over the air vehicle and/or its payloads to include the VDT
Data Link.
The LOI fields shall define the requirement to implement the specified functional
message group for a specified LOI. LOI 2 has been reserved for a ground station
that is capable of receiving other STANAG compliant digital payload data (e.g.,
STANAG 4545, 7023, 4609) for a specific payload type and the associated auxiliary
data (pointing, position), and such a ground station shall be considered STANAG
4586 LOI 2 compliant for that payload type without having to receive the formatted
LOI 3 DLI payload messages for that payload type, e.g., for these ground systems
these messages are optional for LOI 2. LOI 3 messages are for monitor only or
control and monitoring of payload types that are installed onboard an air vehicle.
LOI 4 messages are for the monitor only or control and monitoring of an air vehicle,
without the capability to launch or recover the air vehicle. Since Launch and
Recovery is vehicle specific, complex LOI 5 functionality for Launch and recovery
functions is not implemented via generic STANAG 4586 DLI messages. Launch and
Recovery functions in excess of the flight modes provided in Message #2001,
Vehicle Operating Mode Command, shall be implemented through the VSM using the
vehicle specific mechanism or through the definition of private messages. The Stick
commands and status messages are sent between CUCS and the AV/VSM.
The Functional Message Groups in Table B1 - 5 specify at which LOI(s) each of the
messages must be supported by the CUCS / VSM to achieve a compliant STANAG
4586 implementation for that LOI. In general, the messages are not to be transmitted
between the CUCS and VSM until an authorized connection between the two
components has been established (accomplished via Message #1 and Message #2
1 - B - 38
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
for all functionality with the exception of Data Links); however certain messages such
as the System ID Messages are required to be exchanged in advance of a
connection to actually create the connection. Messages that are allowed to be
transmitted outside a valid connection will be noted.
O = Optional, Y = Yes
Message Group
LOI 2
LOI 3
(Monitor
Only)
LOI 3
(Control &
Monitor)
LOI 4
(Monitor
Only)
LOI 4
(Control &
Monitor)
LOI 5
System ID
Flight Vehicle
Command
Flight Vehicle
Status
LOI 4 Monitor not

required for
Message #3011
Flight Vehicle
Payload-relevant
IFF Command
IFF Status
ATC Interface
Command
LOI applicability
is ATC
equipment
dependent
ATC Interface
Status
LOI applicability
is ATC
equipment
dependent
Vehicle Auxiliary
Command
Vehicle Auxiliary
Status
Comment
Mission Command and Status:

Vehicle Mission
Messages
Note: In LOI 4M
only require
messages from
VSM to CUCS.
Payload Mission
Messages
Note: In LOI 4M
only require
messages from
VSM to CUCS.
Subsystem
Status
LOI 3/ 3M
required payload
systems only.
LOI 4M status
messages only.
Miscellaneous
Messages
1 - B - 39
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message Group
LOI 2
Payload
Command
Payload Status
LOI 3
(Monitor
Only)
LOI 3
(Control &
Monitor)
LOI 4
(Monitor
Only)
LOI 4
(Control &
Monitor)
LOI 5
Weapons
Command
Weapons Status
Data Link
Discovery
Comment
Data Link Command:

Control Data Link
(CDT)
LOI is not applicable to the Control Data Link Terminal (e.g.; GDT),
however the STANAG DLI messages are mandatory for controlling a
STANAG 7085 CDT. The messages are optional for all other Data Link
types.
Vehicle Data link

(VDT)
In LOI 3/3M,
these messages
are optional as a
LOI 3 operator
may not be
allowed to
control/ monitor a
VDT Data Link.
The VDT is
considered a
vehicle
subsystem,
therefore
separation of this
system from the
vehicle is an
implementation
decision.
Data Link Status:

Control Data Link
(CDT)
LOI is not applicable to the Control Data Link Terminal (e.g.; GDT),
however the STANAG DLI messages are mandatory for monitoring a
STANAG 7085 CDT. The messages are optional for all other Data Link
types.
Vehicle Data link

(VDT)
1 - B - 40
In LOI 3/3M,
these messages
are optional as a
LOI 3 operator
may not be
allowed to
control/ monitor a
VDT Data Link.
The VDT is
considered a
vehicle
subsystem,
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message Group
LOI 2
LOI 3
(Monitor
Only)
LOI 3
(Control &
Monitor)
LOI 4
(Monitor
Only)
LOI 4
(Control &
Monitor)
LOI 5
Comment
therefore
separation of this
system from the
vehicle is an
implementation
decision.
Data Link
Transition
Autonomy:
Vehicle
Autonomy
Payload
Autonomy
General PreConnection
Configuration
General PostConnection
Configuration
VSM Forced
Commands
Private
Messages
Draw Interface
VSM-specific
Payload data (product):

AV Stick
Command
AV Stick Status
Primary data
Embedded
Metadata
Y
Metadata
optional if
available through
DLI
Table B1 - 5: Functional Message Group Table
In the following tables (i.e., Tables B1 6 through B1 33), each Message type entry
is identified with several properties, one of these properties is labelled the Push/Pull
property. Push messages are communicated either periodically or based on some
event, but do not require a request to result in sending a message. Pull messages
are messages that are communicated in response to a request. This mechanism is
used to assure that data link bandwidth is not unnecessarily consumed by unneeded
data.
The Source property in the tables shall identify the component from which the
message is issued. Where the VSM is identified as the source of the message in the
1 - B - 41
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
table, it can be considered to mean either the VSM, AV, or Data Link as appropriate,
dependent on the functionally grouping and selected implementation of the UCS
system. In the case of a private message and related configuration messages, the
destination may be either the CUCS or VSM, depending on where the private
message is to be processed (e.g., in a split VSM, where one VSM sends a message
to the other part of the split VSM).
The Allowable Max Latency (msec) property defines the maximum transport delay
between the HCI input and the output at the DLI interfaces on a CUCS.
DLI common messages shall all be transmitted through a port configured for
communications using UDP multicast. UDP multicast enables multiple processes
(VSMs and CUCSs) to communicate with each other on a single IP address and port
number.
Since UDP does not provide guaranteed delivery, messages requiring
acknowledgement of receipt shall be acknowledged using the Message
Acknowledgement (Message #17000). Messages designated as Push type
messages may be communicated without the requirement for acknowledgement.
This allows transmission of streaming and ephemeral data (such as periodic vehicle
state data) for which retransmit is neither required nor desired. Messages
designated as Pull type messages are responses to queries and the message is
itself an acknowledgement. UDP multicast of these Pull type messages makes it
possible for multiple CUCSs to remain synchronized with each other and with
multiple VSMs by monitoring query/response transactions for vehicles and payloads
that are controlled by other CUCSs. However, acknowledgement of receipt of a
request to generate a pull-type message may be required if delayed response is an
issue. In such cases, the Message Acknowledgement bit in the header shall be used
to fulfil a requirement for such acknowledgement cases.
4.1.1.1 System ID Functional Group.
The messages defined in the System ID Messages table shall compose the System
ID Functional Group of messages. The messages identified here as pulled from the
VSM will be in response to the command. The System ID messages shall be able to
be transmitted between a CUCS and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Source
Allowable
Max Latency
(msec)
CUCS Authorisation Request
Push
CUCS
1,000
21
VSM Authorisation Response
Push/Pull
VSM
1,000
20
Vehicle ID
Push/Pull
VSM
1,000
22-39
Unassigned message types in the

range of 0 - 1999 are reserved
Push/Pull
SYSTEM ID MESSAGES (Section 4.2)
Table B1 - 6: System ID Messages
1 - B - 42
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.1.1.2 Flight Vehicle Command Functional Group.
The messages defined in the Flight Vehicle Command Messages table shall
compose the Flight Vehicle Command Functional Group of messages. The Flight
Vehicle Command messages shall not be able to be sent between a CUCS and VSM
without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
FLIGHT VEHICLE COMMAND MESSAGES (Section 4.3)

2000
40
Vehicle Configuration Command
2001
42
Vehicle Operating Mode Command
2002
43
Vehicle Steering Command
2003
48
Mode Preference Command
2004
41
2005
46
2006
47
Push
CUCS
1,000
Push
CUCS
500
Push
CUCS
500
Push
CUCS
500
Loiter Configuration
Push
CUCS
500
Flight Termination Command
Push
CUCS
500
Relative Route/Waypoint Absolute

Reference Message
Push
CUCS
1,000
2007
44
Air Vehicle Lights
Push
CUCS
500
2008
45
Engine Command
Push
CUCS
500
2009
49
Zeroize Encryption Keys

Command
Push
CUCS
500
2010
N/A
AV Stick Command Message
Push
CUCS
200
2011
N/A
Area Transmission Command
Push
CUCS
1000
2012
N/A
Area Polygon Loop Segment

Message
Push/Pull
CUCS/VSM
1000
2013
N/A
Joystick Command
Push
CUCS
200
2014
N/A
Emergency Mode Command
Push
CUCS
500
2015
N/A
Energy Storage Unit Configuration
Push
CUCS
500
2016 2999
50
99

range of 2000 2999 are reserved
Table B1 - 7: Flight Vehicle Command Messages

4.1.1.3 Flight Vehicle Status Functional Group.
The messages defined in the Flight Vehicle Status Messages table shall compose
the Flight Vehicle Status Functional Group of messages. The Flight Vehicle Status
messages shall not be able to be sent between a CUCS and VSM without an
authorized connection, with the exception of Message #3000, Vehicle Configuration
Message in response to a specific configuration request via Message #17002,
Generic Information Request Message.
1 - B - 43
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg #
Description
Push/Pull
Source
Allowable
Max
Latency
(msec)
FLIGHT VEHICLE STATUS MESSAGES (Section 4.4)

3000
100
Vehicle Configuration
Pull
VSM
1,000
3001
106
Vehicle Operating Mode Report
Push/Pull
VSM
500
3002
104
Vehicle Operating States
Push/Pull
VSM
500
3003
109
Mode Preference Report
Push/Pull
VSM
500
3004
112
Loiter Configuration Report
Push/Pull
VSM
500
3005
108
Flight Termination Mode Report
Push/Pull
VSM
500
3006
107
Vehicle Lights State
Push/Pull
VSM
500
3007
105
Engine Operating States
Push/Pull
VSM
500
3008
111
Zeroize Encryption Keys State
Push/Pull
VSM
500
3009
102
Air and Ground Relative States
Push
VSM
500
3010
103
Body-Relative Sensed States
Push
VSM
200
3011
N/A
AV Stick Status Message
Push
VSM
200
3012
N/A
Area Status Alert Message
Push
VSM
1,000
3013
N/A
Area Transmission Status
Pull
VSM
1,000
3014
N/A
Emergency Mode Report
Pull
VSM
500
3015
N/A
Energy Storage Unit State
Push/Pull
VSM
500
3016-3999
113 199

range of 3000 3999 are
reserved
Table B1 - 8: Flight Vehicle Status Messages

4.1.1.4 Flight Vehicle Payload Relevant Status Functional Group.
The messages defined in the Flight Vehicle Payload Relevant Status Messages table
shall compose the Flight Vehicle Payload Relevant Status Functional Group of
messages. The Flight Vehicle Payload Relevant Status Messages have been
distinguished from the other Flight Vehicle status messages to limit implementation of
messages on a system, CUCS and VSM that require the flight vehicle orientation, or
location knowledge, to correctly implement LOI 3 monitor capabilities for a payload.
The Flight Vehicle Payload Relevant Status Messages shall not be able to be sent
between a CUCS and VSM without an authorized connection.
1 - B - 44
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
FLIGHT VEHICLE PAYLOAD RELEVANT MESSAGES (Section 4.5)

4000
101
Inertial States
Push
VSM
500
4001
110
From-To-Next Waypoint States
Push
VSM
1000

Table B1 - 9: Flight Vehicle Payload Relevant Status Message

4.1.1.5 IFF Command Functional Group.
The messages defined in the IFF Command Messages table shall compose the IFF
Command Functional Group of messages. The IFF Command Messages shall not
be transmitted between a CUCS and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
IFF COMMAND MESSAGE TYPES (Section 4.6)

5000
1500
IFF Code Command
Push
CUCS
500
5001
1501
IFF Ident (Squawk) Command
Push
CUCS
500
15021599

CUCS
Table B1 - 10: IFF Command Messages

4.1.1.6 IFF Status Functional Group.
The messages defined in the IFF Status Messages table shall compose the IFF
Status Functional Group of messages. The IFF Status Messages shall not be
transmitted between a CUCS and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
IFF STATUS MESSAGE TYPES (Section 4.7)

6000
1600
IFF Status Report
Push/Pull
16011699

Table B1 - 11: IFF Status Messages
1 - B - 45
VSM
500
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.1.1.7 ATC Interface Command Functional Group.
The messages defined in the ATC Interface Command Messages table shall
compose the ATC Interface Command Functional Group of messages. The ATC
Interface Command Messages shall not be transmitted between a CUCS and VSM
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
ATC INTERFACE COMMAND MESSAGE TYPES (Section 4.8)

7000
N/A
Civilian Air Traffic Control (ATC)

Radio Command
Push
CUCS
500
7001
N/A
NAVAID Radio Command
Push
CUCS
500

Table B1 - 12: ATC Interface Command Messages

4.1.1.8 ATC Interface Status Functional Group.
The messages defined in the ATC Interface Status Messages table shall compose
the ATC Interface Status Functional Group of messages. The ATC Interface Status
Messages shall not be transmitted between a CUCS and VSM without an authorized
connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
ATC INTERFACE STATUS MESSAGE TYPES (Section 4.9)

9000
N/A
Civilian Air Traffic Control (ATC)

Radio Status
Push/Pull
VSM
500
9001
N/A
NAVAID Radio Status
Push/Pull
VSM
500

reserved
Table B1 - 13: ATC Interface Status Messages

4.1.1.9 Vehicle Auxiliary Command Functional Group.
The messages defined in the Vehicle Auxiliary Command Messages table shall
compose the Vehicle Auxiliary Command Functional Group of messages. The
Vehicle Auxiliary Command Messages shall not be transmitted between a CUCS and
VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
VEHICLE AUXILIARY COMMAND MESSAGE TYPES (Section 4.10)

11000
N/A
Vehicle Auxiliary Command
1 - B - 46
Push
CUCS
500
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
11001
N/A
Fuel, Oil, & Hydraulic Commands
Push
CUCS
500
11101
N/A
Battery Bank Select
Push
CUCS
500

reserved
Table B1 - 14: Vehicle Auxiliary Command Messages

4.1.1.10 Vehicle Auxiliary Status Functional Group.
The messages defined in the Vehicle Auxiliary Status Messages table shall compose
the Vehicle Auxiliary Status Functional Group of messages. The Vehicle Auxiliary
Status Messages shall not be transmitted between a CUCS and VSM without an
authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
VEHICLE AUXILIARY STATUS MESSAGE TYPES (Section 4.11)

12000
N/A
Vehicle Auxiliary Status
Push/Pull
VSM
500
12001
N/A
Electrical Report
Push
VSM
500
12002
N/A
Meteorological Data
Push
CUCS
500
12003
N/A
Fuel, Oil, & Hydraulic Status
Push
VSM
500
12101
N/A
Battery Report
Push
VSM
500

reserved
Table B1 - 15: Vehicle Auxiliary Status Messages

4.1.1.11 Mission Command and Status Functional Group.
The messages defined in the Mission Command and Status Messages table shall
compose the Mission Command and Status Functional Group of messages. The
Mission Command and Status messages shall not be able to be sent between a
CUCS and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
MISSION MESSAGES (Section 4.12)

13000
800
Mission Transfer Command
Push
CUCS/VSM
500
13001
801
AV Route
Push/Pull
CUCS/VSM
500
13002
802
AV Position Waypoint
Push/Pull
CUCS/VSM
500
13003
803
AV Loiter Waypoint
Push/Pull
CUCS/VSM
500
13004
804
Payload Action Waypoint
Push/Pull
CUCS/VSM
500
1 - B - 47
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
13005
805
Airframe Action Waypoint
Push/Pull
CUCS/VSM
500
13006
806
Vehicle Specific Waypoint
Push/Pull
CUCS/VSM
500
13007
N/A
Define Contingency
Push/Pull
CUCS/VSM
500
14000
900
Mission Upload/Download Status
Push
VSM
500
901999

reserved
Table B1 - 16: Mission Command and Status Messages

4.1.1.12 Subsystem Status Functional Group.
The messages defined in the Subsystem Status Messages table shall compose the
Subsystem Status Functional Group of messages. The Subsystem Status Messages
shall not be able to be sent between a CUCS and VSM without an authorized
connection.
New Msg
#
Old
Msg
#
Description
15000
1000
Subsystem Status Request
Push
CUCS
500
15001
1001
Subsystem Status Detail Request
Push
CUCS
500
16000
1100
Subsystem Status Alert
Push
VSM
500
Push/Pull
Source
Allowable
Max Latency
(msec)
SUBSYSTEM STATUS MESSAGES (Section 4.13)
16001
1101
Subsystem Status Report
Pull/Push
VSM
500
16002
1405
Heartbeat Message
Pull
CUCS/VSM
500
11021199

reserved
Table B1 - 17: Subsystem Status Messages

4.1.1.13 Miscellaneous Message Functional Group.
The messages defined in the Miscellaneous Messages table shall compose the
Miscellaneous Message Functional Group of messages.
The Miscellaneous
Messages shall not be transmitted between a CUCS and VSM without an authorized
LOI connection with the exception of Message #17000, Message Acknowledgement,
in response to a request for acknowledgement to a message that may be transmitted
without a valid connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
MISCELLANEOUS MESSAGE TYPES (Section 4.14)

17000
1400
Message Acknowledgement
1 - B - 48
Pull
CUCS/VSM
500
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
17001
1402
Schedule Message Update

Command
Push
CUCS/VSM
1,000
17002
1403
Generic Information Request
Push
CUCS/VSM
1,000
17003
1404
File Transfer Notification
Push
CUCS/VSM
1,000
18000
1800
Link Audio Command
Push
CUCS
500
18001
N/A
Emitters All Off Command
Push
CUCS
500
18100
1825
Link Audio Status
Pull
VSM
500
18101
N/A
Emitters Status
Pull
VSM
500
18200
N/A
Meteorological Table Message
Push
CUCS
500
18300
N/A
Meteorological Table Report
Push
VSM
500
18400
N/A
KLV Security Configuration Data
Push
AV
200
18401
N/A
KLV Security Classification Data
Push
AV
200
18402
N/A
KLV Security Classification

Comment Data
Push
AV
200
18403
N/A
KLV Security Image Data
Push
AV
200
14051499

reserved
Table B1 - 18: Miscellaneous Messages

4.1.1.14 Payload Command Functional Group.
The messages defined in the Payload Command Messages table shall compose the
Payload Command Functional Group messages, divisible by payload type. The
Payload Command messages shall not be sent between a CUCS and VSM without
an authorized connection for the specified Payload Type.
New
Msg
#
Old
Msg
#
Description
Push/Pull
Source
Payload
Type
Allowable
Max Latency
(msec)
PAYLOAD COMMAND MESSAGES (Section 4.15)

19000
206
Payload Bay Command
Push
CUCS
As
applicable
500
19001
200
Payload Steering Command
Push
CUCS
EO/IR,
SAR,
others as
applicable
200
19100
201
EO/IR/Laser Payload
Command
Push
CUCS
EO/IR
500
19101
208
EO/IR/Laser Payload Quality

Control
Push
CUCS
EO/IR
500
19200
202
SAR Payload Command
Push
CUCS
SAR
500
1 - B - 49
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New
Msg
#
Old
Msg
#
19400
204
19401
Payload
Type
Allowable
Max Latency
(msec)
Description
Push/Pull
Source
Command
Push
CUCS
Comm
Relay
500
Load Communications Relay

Configuration Command
Pull/Push
CUCS/V
SM
Comm
Relay
500
19500
205
Payload Data Recorder

Control Command
Push
CUCS
Recorder
500
19600
207
Terrain Data Update
Push
CUCS
EO/IR,
SAR,
others as
applicable
500
19700
209
Payload Operating Mode

Command
Push
CUCS
210299
Unassigned message types

in the range of 19000
20999 are reserved
500
Table B1 - 19: Payload Command Messages

4.1.1.15 Payload Status Functional Group.
The messages defined in the Payload Status Messages table shall compose the
Payload Status Functional Group messages, divisible by payload type. The Payload
Status Messages shall not be able to be sent between a CUCS and VSM without an
authorized connection for the specified Payload Type, with the exception of Message
#21001, Payload Configuration and Message #12100, EO/IR Configuration State in
response to a specific configuration request via Message #17002, Generic
Information Request.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Payload
Type
Allowable
Max
Latency
(msec)
PAYLOAD STATUS MESSAGES (Section 4.16)

21000
308
Payload Bay Status
Pull
VSM
As
applicable
500
21001
300
Payload Configuration
Push/Pull
VSM
All
500
21100
301
EO/IR - Configuration State
Pull
VSM
EO/IR
200
21101
302
EO/IR/Laser Operating State
Push/Pull
VSM
EO/IR
500
21200
303
SAR Operating State
Pull
VSM
SAR
500
21400
305
Communications Relay Status
Pull
VSM
Comm
Relay
500
21401
N/A
Configuration Status
Pull/Push
CUCS/VSM
Comm
Relay
500
1 - B - 50
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
21402
Payload
Type
Allowable
Max
Latency
(msec)
Description
Push/Pull
Source
N/A
Communication Relay
Configuration State
Pull
VSM
Comm
Relay
500
21500
306
Payload Data Recorder Status
Pull
VSM
Recorder
500
21501
307
Vehicle Payload/Recorder
Configuration
Pull
VSM
Recorder
1,000
21600
309
Terrain Data Request
Push
VSM
EO/IR,
SAR,
others as
applicable
500
310
Payload Operating Mode Report
Pull
VSM
311399

reserved
21700
500
Table B1 - 20: Payload Status Messages
The Payload Types have been defined to provide a set of generic (common)
messages per payload type for common air vehicle payloads. A CUCS and/or VSM
do not have to support the generic payload messages that do not apply to the
Payload type(s) in their systems configuration. However, if a generically identified
payload type(s) is applicable for the air vehicle system, the identified formatted DLI
message(s) for that payload type shall be supported.
A generic set of Payload Types has been identified in Message #21001, Payload
Configuration Message. The generic DLI messages associated with each of the
payload types is identified in Table B1 - 21.
Payload Type
Required Message
Msg Type
All LOI 2 & 3
Message #21001: Payload Configuration
Configuration
EO/IR & Fixed
Message #21100: EO/IR Configuration State

Message #21101: EO/IR/Laser Operating State
Message #21700: Payload Operating Mode Report
Message #19001: Payload Steering Command
Message #19100: EO/IR/Laser Payload Command
Message #19101: EO/IR/Laser Payload Quality Control
Message #19700: Payload Operating Mode Command
Configuration
Status
Command
Command (Modes)
Command
Command
Command
SAR
N/A
: Configuration Message
Message #21200: SAR Operating State
Message #19001: Payload Steering Command
Message #19200: SAR Payload Command
Configuration
Status
Command
Command (modes)
Dispensable
(Stores)
N/A
Message #26000: Stores Management System Status
Message #24000: Stores Management System Command
Configuration
Status
Command
Comm. Relay
N/A
Configuration
1 - B - 51
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #21400: Communication Relay Status
Message #21401: Communications Relay Configuration Status
Message #21402: Communication Relay Configuration State
Message #19400: Communications Relay Command
Message #19401: Load Communications Relay Configuration
Command
Status
Status
Status
Command
Command
Recorder
Message #21501: Vehicle Payload/Recorder Configuration

Message #21500: Payload Data Recorder Status
Message #19500: Payload Data Recorder Control Command
Configuration
Status
Command
Payload Bay
Message #19000: Payload Bay Command
Command
Table B1 - 21: Conditional Payload Message Groups
Common message formats covering command and status of other payloads (e.g.,
electronic countermeasures, weapons delivery, electronic warfare, self-defence
payloads) are not currently defined. UAVs carrying such payloads shall use vehicle
specific message mechanisms described above. Future revisions of this STANAG
will incorporate standard control and status messages for such payloads as they
become commonly employed across a variety of UAV platforms.
4.1.1.16 Weapons Command Functional Group.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Payload
Type
Allowable
Max
Latency
(msec)
WEAPONS COMMAND MESSAGES (Section 4.17)

24000
203
Stores Management System

Command
Push
CUCS
Disp.
Stores
500
Unassigned message types in

the range of 24000 25999 are
reserved
Table B1 - 22: Weapons Command Message Groups

4.1.1.17 Weapons Status Functional Group.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Payload
Type
Allowable
Max
Latency
(msec)
WEAPONS STATUS MESSAGES (Section 4.18)

26000
304
Stores Management System

Status
Pull
VSM
Unassigned message types in

the range of 26000 27999 are
reserved
Table B1 - 23: Weapons Status Message Groups
1 - B - 52
Disp.
Stores
500
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.1.1.18 Data Link Discovery Functional Group.
The messages defined in the Data Link Discovery Messages table shall compose the
Data Link Discovery Functional Group of messages. The messages identified here
as pulled from the VSM will be in response to the command. The Data Link
Discovery messages shall be able to be sent between a CUCS and VSM without an
authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max
Latency
(msec)
DATA LINK DISCOVERY MESSAGES (Section 4.19)

28000
404
Data Link Control Authorisation

Request
Push
CUCS
500
28001
500
Data Link Configuration/Assignment

Message
Pull
VSM
500

Table B1 - 24: Data Link Discovery Messages

4.1.1.19 Data Link Command Functional Group.
The messages defined in the Data Link Command Messages table shall compose
the Data Link Command Functional Group of messages.
Note that LOI is not applicable to controlling or monitoring a CDT data link terminal
(command terminal, GDT), as the CUCS is either controlling or monitoring that
terminal, or it is not. The VDT data Link terminal (vehicle terminal), for all intents and
purposes, is considered to be a subsystem of the flight vehicle, therefore it is an air
vehicle implementation decision whether to allow control of the VDT data link at LOI
3 or 4. It is recommended that at a minimum the LOI 4/5 operator is in control of at
least one VDT to maintain positive control over the flight vehicle.
The Data Link Command Messages shall not be able to be sent from a CUCS to a
VSM for a VDT without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
DATA LINK COMMAND MESSAGES (Section 4.20)

30000
405
Data Link to Vehicle ID Assignment
Push
CUCS
500
30001
400
7085 Data Link Active Configuration

Set Up Message
Push
CUCS
500
30002
401
7085 Data Link Fallback

Configuration Set Up Message
Push
CUCS
500
30003
403
Data Link Control Command
Push
CUCS
500
30004
402
RF Command Processing Set Up

Message
Push
CUCS
500
1 - B - 53
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
30100
406
Antenna Pedestal Location

Command
Push
CUCS
500
30101
407
Antenna Control Command
Push
CUCS
500
30102
408
Antenna Position Command
Push
CUCS
500
30200
409
Link Health Command
Push
CUCS
500
30300
410
Set Data Link UDP Monitor Period
Push
CUCS
1,000
30301
N/A
IP Address and Port Assignment

Request
Push
CUCS
1,000
31XXX
N/A
Reserved for future IC2DL

Commands
411499

reserved
Table B1 - 25: Data Link Command Messages

4.1.1.20 Data Link Status Functional Group.
The messages defined in the Data Link Status Messages table shall compose the
Data Link Status Functional Group of messages.
The Data Link Status messages shall not be able to be sent from a VSM to a CUCS
for a VDT without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
DATA LINK STATUS MESSAGES (Section 4.21)

32000
501
Data Link to Vehicle ID Report
Push
VSM
500
32001
502
7085 Data Link Active

Configuration Status Report
Pull
VSM
500
32002
503
7085 Data Link Fallback

Configuration Status Report
Pull
VSM
500
32003
505
Data Link Control Status Report
Push
VSM
500
32004
504
RF Command Processing Status

Report
Pull
VSM
500
32005
501
Legacy Data Link Status Report
Push
VSM
500
32006
502
Legacy Data Link Control

Command Status
Push
VSM
500
32100
506
Antenna Pedestal Location Status

Report
Push
VSM
500
32101
507
Antenna Control Status Report
Push
VSM
500
32102
509
Antenna Position Report
Push
VSM
500
32103
503
Legacy Pedestal Status Report
Push
VSM
500
1 - B - 54
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
32200
508
Link Health Status
Push
VSM
500
32201
511
Data Link Fallback Status
Push
VSM
500
32300
510
Data Link UDP Count
Push
VSM
500
32301
N/A
AV IP Disclosure Message
Push/Pull
VSM
1,000
33XXX
N/A
Reserved for future IC2DL Status
512599

reserved
VSM
Table B1 - 26: Data Link Status Messages

4.1.1.21 Data Link Transition Functional Group.
The messages in this grouping are provided to allow the transition in control of a
vehicle from one UCS system to another where there vehicle only has a single,
directional VDT, therefore these messages need to be implemented to support
interoperability with such systems.
The messages defined in the Data Link Transition Messages table shall compose the
Data Link Transition Functional Group of messages.
The Data Link Transition messages shall not be able to be sent between a CUCS
and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
DATA LINK TRANSITION MESSAGES (Section 4.22)

34000
600
Vehicle Data Link Transition

Coordination Message
Push
CUCS
500
35000
700
Handover Status Report
Push/Pull
CUCS/VSM
500
701799

reserved
Table B1 - 27: Data Link Transition Messages

4.1.1.22 Autonomy Functional Group.
The messages defined in the Autonomy Messages table shall compose the
Autonomy Message Functional Group of messages. The Autonomy Messages shall
not be transmitted between a CUCS and VSM without an authorized connection.
1 - B - 55
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg #
Description
Push/Pull
Source
Allowable
Max
Latency
(msec)
AUTONOMY MESSAGES (Section 4.23)

36000
1700
Activity Constraint
Push
CUCS
500
36001
1701
Constraint Response Message
Push
VSM
500
36002
1702
Constraint Requests Complete

Message
Push
CUCS
500
36003
1703
Constraint Responses Complete

Message
Push
VSM
500
36100
1704
Activity Complete Message
Push
VSM
500
Push/Pull
VSM
500
36200
1705
Activity Status Message
N/A
Deleted
(1706)
Deleted (Area Definition)
1707
1799

reserved
Table B1 - 28: Autonomy Messages

4.1.1.23 General Pre-connection Configuration Functional Group.
The messages defined in the General Pre-connection Configuration Messages table

shall compose the General Pre-connection Configuration Functional Group of
messages, which do not require an authorized connection to be transmitted between
the CUCS and the VSM.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
GENERAL PRECONNECTION CONFIGURATION MESSAGES (Section 4.24)

40000
1200
Field Configuration Request
Push
CUCS
500
41000*
1300
Field Configuration Integer

Response
Pull
VSM
500
41001*
1301
Field Configuration Float Response
Pull
VSM
500
41002*
1302
Field Configuration Enumerated

Response
Pull
VSM
500
41003*
1308
Field Configuration Unsigned

Response
Pull
VSM
500
41004*
1309
Field Configuration Character

Response
Pull
VSM
500
41005
1203
Configuration Complete
Push
CUCS/VSM
500
41006
N/A
Integer Enumeration Response
Pull
CUCS
1000
1 - B - 56
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New Msg
#
Old
Msg
#
Description
1303,
13101399

reserved
Push/Pull
Source
Allowable
Max Latency
(msec)
Note (*): These messages are used for both Pre-connection and Post
connection
Table B1 - 29: General Preconnection Configuration Messages
4.1.1.24 General Post-connection Configuration Functional Group.
The messages defined in the General Post-connection Configuration Messages table

shall compose the General Post-connection Configuration Functional Group of
messages. The General Post-connection Configuration Messages shall not be
transmitted between a CUCS and VSM without an authorized connection.
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
GENERAL POSTCONNECTION CONFIGURATION MESSAGES (Section 4.25)

42000
1201
Display Unit Request
Push
CUCS
500
42001
1202
CUCS Resource Report
Push
CUCS
1,000
42002
1204
Manage VSM Windows Message
Push
CUCS
1,000
42003
N/A
Report Controllable Element

Message
Push
VSM
1,000
43000
1304
VSM Services Report Message
Pull
VSM
1,000
43001
1310
AV Route Configuration
Pull
VSM
500
43002
1311
Remote Windows GUI Definition
Pull
VSM
1,000
41000*
1300
Field Configuration Integer

Response
Pull
VSM
500
41001*
1301
Field Configuration Float Response
Pull
VSM
500
41002*
1302
Field Configuration Enumerated

Response
Pull
VSM
500
41003*
1308
Field Configuration Unsigned

Response
Pull
VSM
500
41004*
1309
Field Configuration Character

Response
Pull
VSM
500
13101399

reserved
Note (*): These messages are used for both Pre-connection and Post
connection
Table B1 - 30: General Configuration Messages
1 - B - 57
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.1.1.25 VSM Forced Commands Functional Group.
The messages defined in the VSM Forced Commands Messages table shall
compose the VSM Forced Commands Functional Group of messages. The VSM
Forced Commands Messages shall not be transmitted between a CUCS and VSM
New Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
VSM FORCED COMMAND MESSAGES (Section 4.26)

44000
1900
Field Change Integer Command
Push
VSM
500
44001
1901
Field Change Float Command
Push
VSM
500
44002
1902
Field Change Enumerated

Command
Push
VSM
500
44003
1903
Message Parameter Availability
Push
VSM
500

reserved
Table B1 - 31: VSM Forced Command Messages

4.1.1.26 Draw Interface Functional Group.
The messages defined in the Draw Interface Messages table shall compose the
Draw Interface Functional Group of messages. The Draw Interface Messages shall
not be transmitted between a CUCS and VSM without an authorized connection.
New
Msg
#
Old
Msg
#
Description
Push/Pull
Source
Allowable
Max Latency
(msec)
Draw Interface Messages (Section 4.27)

46000
2000
Draw Layer Configuration
Push
VSM
500
46001
2001
Draw Layer Update Request /

Status
Push
CUCS
500
46002
2002
Draw Layer Control
Push
VSM
500
46003
2003
Draw Line
Push
VSM
500
46004
2004
Draw Simple Polygon
Push
VSM
500
46005
2005
Draw Complex Polygon
Push
VSM
500
46006
2006
Draw Arc / Circle
Push
VSM
500
46007
2007
Draw Text
Push
VSM
500
46008
2008
Draw Arrow
Push
VSM
500
46009
2009
Set Cursor Interest
Push
VSM
500
46010
2010
Remove Cursor Interest
Push
VSM
500
46011
2011
Cursor Interest Return
Push
CUCS
500
1 - B - 58
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
New
Msg
#
Old
Msg
#
Description
Push/Pull
Allowable
Max Latency
(msec)
Source

reserved
Table B1 - 32: Draw Interface Messages

4.1.1.27 Private Messages.
The Private Messages are defined as vehicle specific messages and are used within
the above defined functional groups at the specified LOI(s) as per their definition
when created. The Private Messages shall not be transmitted between a CUCS and
VSM without an authorized connection for the LOI specified in the private message
definition.
LOI
New
Msg
#
Old
Msg
#
Description
Push/Pull
2/4M
4
or
5
Allowable
Max
Latency
(msec)
(1)
(1)
(1)
500
Source
PRIVATE MESSAGES (Section 4.28)

50000
65000
3000 3999
VSM-Specific Private Message
Push/Pull
VSMSpecific
NOTE: (1) VSM-Specific
Table B1 - 33: Private Messages

4.1.2 Generic (Common) DLI Messages.
The following section contains the generic (common) DLI messages identified in the
tables above. In the tables that follow, data types shall conform to the following
meanings:
Character (n) - ASCII character data of n bytes in length, which
includes the null terminator character
Integer (n) - signed integers, where n is 1, 2, 3, 4 or 5 bytes
Float - IEEE format floating point numbers (4 bytes in length)
Unsigned (n) - unsigned integers; where n is 1, 2, 3, 4 or 5 bytes
Byte (n) - array of bytes, where n defines the size of the array
Private messages may use additional data types not defined above.
In addition, data ranges that have reserved values shall not be used by a CUCS or
VSM. Data ranges that have VSM specific values may be used by the VSM/ AV/
Data link to add vehicle unique functionality that is not supported by the STANAG
defined values to the specified data field. The addition of vehicle specific values to
the generic message data fields is accomplished through the use of the Generic Preconnection Configuration messages.
Bit maps are used in certain command messages to allow multiple data definition of
data fields in a message, such as in the request for subsystem status. Each
1 - B - 59
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
addressed component shall accept such a request and may respond with a separate
status message for the overloaded request, or as specified in the specific message.
Bit maps are indicated in the STANAG 4586 where the Units = Bitmapped.
Each field in a message has a Unique ID associated with it. Once a field is assigned
a Unique ID, that ID remains with the field even if the field is moved within the
message or to a new message. The Unique ID provides a message and position
independent method to refer to a particular field that will not change if the field is
moved.
4.2 System ID Messages.
4.2.1 Message #1: CUCS Authorisation Request.
This message shall be sent by a CUCS to a VSM/ air vehicle to request a specific
monitor/ control connection to the VSM/ air vehicle, or to discover available
connection(s) to the VSM/ air vehicle. If the Destination ID (e.g., Vehicle/VSM) for
the connection is known by the CUCS then the Destination ID field in this message
shall be filled in with the specified IDs. Where the CUCS is discovering a connection,
the Destination ID field shall be filled with the broadcast VSM ID/ Vehicle ID. If more
than one authorisation (connection) is needed for a specific vehicle (including
payload onboard), this message may be sent multiple times, once for the vehicle and
each payload station.
This message is designed to allow more than one CUCS to control AV/Payload
functions of a single VSM/ air vehicle for a given vehicle ID. For example, one
controlling the vehicle and another controlling a payload, or two stations
simultaneously controlling the vehicle, but different flight modes.
A CUCS controlling a connection (e.g., an AV at LOI 4 or 5) shall maintain control of
that functionality until either it breaks the connection, specifically relinquishes control,
or is displaced by another CUCS that is asserting override over the same
functionality while the current CUCS is not. A controlling CUCS may allow another
CUCS to have control of some or all flight modes and their associated messages.
Control of non-associated message, e.g., Air Vehicle Lights, would remain with the
original controlling CUCS. The original controlling CUCS can always select flight
modes not transferred to another CUCS and can always unilaterally take back
complete control of all flight modes.
A CUCS controlling a payload (e.g., LOI 3) shall maintain payload control until it
either breaks the connection, specifically relinquished control, or when the CUCS that
has control over the platform (i.e.: LOI 4 or 5) specifically requests control of that
payload.
The Asset Mode field shall be filled with 3 = Broadcast Request for a broadcast
request.
As specified above, the CUCS Authorisation Request message may be transmitted
from a CUCS to a VSM without an authorized LOI connection as it is used to
discover possible connections, and it is used to request an authorized LOI
connection.
1 - B - 60
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
The CUCS shall be required to support the Presence Vector capability and
demonstrate this support via the minimum test set described in the AEP-57 Volume 2
Validation/Test Guideline Document. However, should customer or regulatory test
requirements for support of the presence vector prove prohibitive for a specific
system, use of the Presence Vector Support field may be used to enforce this field to
be ignored in all messaging between the CUCS and VSM for a given system.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0001.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0001.04
VSM ID
Integer 4
None
See Section 1.7.6
0001.05
Data Link ID
Integer 4
None
See Section 1.7.6
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
0 - 65535 = No Restrictions
Unsigned 1
Bitmapped
0x01 = NA
0x02 = LOI 2
0x04 = LOI 3
0x08 = LOI 4
0x10 = LOI 5
Unsigned 1
Enumerated
0 = Unspecified
1 = Monitor Only
2 = Control & Monitor
Identifies the specific data

link to process this
message.
0001.06
Vehicle Type
Identifies the type name of
vehicle; numbers to be
assigned by STANAG
Custodian.
0001.07
Vehicle Subtype
Identifies the design block
number as designated by
the manufacturer.
0001.08
Requested/Handover LOI
0x00 = Unspecified
0001.16
Requested/Handover
Access
Allows request or handover
1 - B - 61
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0001.17
Requested Flight Mode
Unsigned 1
Enumerated
0 = No Mode
1 = All Modes
2 = Flight Director (Manual
near real-time control of AV
using Message #2002,
where AV autopilot is
disengaged)
3 - 10 = Reserved 3-10
11 = Waypoint (Fly to
predefined waypoint(s))
12 = Loiter (Defined in
Message #2004)
13 - 14 = Reserved 13-14
15 = Autopilot (Autopilot
engaged, but manual
override in near real-time of
AV using Message #2002)
16 = Terrain Avoidance
(Uses Message #2002, field
5 to define clearance
distance)
17 = NavAid (Slaved
Navigation relative to a
navigation beacon.)
18 = Reserved 18
19 = Autoland Engage
20 = Autoland Wave-off
21 = Launch
22 = Slave to Sensor
23 - 31 = Reserved 23-31
32 - 255 = Vehicle Specific
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Identifies which flight

modes the CUCS is
requesting authorisation to
use. The first CUCS
connecting at LOI 4/5 can
always regain control of all
flight modes by sending this
message with the
enumeration of All Modes.
This field is only used when
the requested / handover
LOI is 4/5. The actual flight
modes supported by this
field are restricted to those
of the LOI(s) shown in the
requested / handover LOI
field.
0001.09
Controlled Station 1-16

0x0000 = AV Platform
1 - B - 62
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0001.19
10
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Location ID on a given
Station Location
0001.20
11
Sub-Component Number
Component Location
0001.14
12
Payload Type
Unsigned 2
Enumerated
0 = Not Specified/ N/A

1 = EO
2 = IR
3 = EO/IR
4 = SAR
5 = Fixed Camera
6 = Comms Relay
7 = Dispensable Payload
8 = Recorder
9 = Payload Bay Door
10 - 999 = Reserved
1000 - 65535 = VSM
Specific
0001.15
13
Asset Mode
Unsigned 1
Enumerated
0 = Relinquish/Handover
1 = Request
2 = Override
3 = Broadcast Request
1 - B - 63
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0001.11
14
Data Element Name &

Description
Wait for Vehicle Data Link
Transition Coordination
Message
Type
Units
Range
Unsigned 1
Enumerated
0 = Dont wait
1 = Wait for Message
Unsigned 1
Enumerated
0 - 255 = See Table B1-35
Unsigned 2
Enumerated
Unsigned 1
Enumerated
0 = Presence Vector
Ignored
1 = Presence Vector Used
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Wait for Message #34000

0001.12
15
CUCS Type
CUCS; Numbers to be
assigned by STANAG
Custodian.
0001.13
16
CUCS Subtype
the manufacturer.
0001.18
17
Presence Vector Support

This field indicates whether
the CUCS uses the
presence vector.
If and only if both the CUCS
and the VSM declare use of
the presence vector will the
CUCS and VSM utilize the
presence vector in the
message set to remove
message parameters;
otherwise, both the VSM
and CUCS will implement
the STANAG message set
with all parameters present
in all of the messages; the
presence vector is ignored.
0001.21
18

Table B1 - 34: Message #1: CUCS Authorisation Request
1 - B - 64
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1-35 lists the CUCS Types of many current CUCSs. (Contact the STANAG
4586 Custodian for the most current CUCS Type Table.)
CUCS Type
CUCS Name
Not Identified
US Army One System
US Navy TCS
US Army MUM
US Army BDRVT
US Air Force Advanced Cockpit
Open Unmanned Mission Interface (UMI)

Defense Technologies Inc. (DTI)
US Army Class A Test CUCS
US Army Class B Test CUCS
US Army Class C Test CUCS

Table B1 - 35: CUCS Type Table
Table B1 - 36 lists the Vehicle Type IDs of many current UAVs. The Custodian
Staff will add to this Table as requested due to systems implementing or
experimenting with STANAG 4586. Contact the STANAG 4586 Custodian for the
most current Vehicle Type ID Table.
Vehicle Type ID
Vehicle Name
Not Identified
BAMS UAV
Crecerelle
Crecerelle GE
Eagle-1
MQ-8B Fire Scout (Navy)
RQ-4A Global Hawk A
Grasshopper
Moyen Duc
Petit Duc
10
Phoenix
1 - B - 65
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
11
MQ-1 Predator A
12
MQ-9 Predator B
13
Ranger
14
RQ-7 Shadow 200
15
Sperwer
16
Sperwer LE
17
RQ-2B Pioneer
18
Eagle Eye
19
RQ-5 Hunter
20
GHMD (Navy)
21
Mucke
22
Luna
23
KZO
24
Taifun
25
Fledermaus
26
Falco
27
Nibbo
28
Hermes 180
29
Hermes 450
30
RQ-4B Global Hawk B
31
MQ-1C Gray Eagle
32
ScanEagle A15
33
Vigilante 496
34
Vigilante 502
35
CamCopter S100
36
Little Bird
37
Neuron
38
Tier II (USMC)
39
RQ-14A - Dragon Eye
40
Silver Fox
1 - B - 66
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
41
SkyLark 1
42
Kestrel
43
Voyeur
44
Coyote
45
FCS Class I (YRQ-16A)
46
Reserved
47
Reserved
48
RQ-11A - Raven-B
49
Spyhawk
50
Wasp
51
Puma
52
Aerosonde
53
ScanEagle A20
54
Sky-X
55
Lince
56
Cobra
57
N-UCAS
58
Killer Bee
59
FCS Class IV (MQ-8B - Army)
60
GoldenEye 50
61
GoldenEye 80
62
Excalibur
63
Orion
64
STRIX-A
65
A -160
66
A-UAV SR
67
A-UAV FR
68
ORKA
69
Watchkeeper Air Vehicle WK450
70
HSUSV
1 - B - 67
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
71
CUSV
72
HERTI
73
Fire Shadow
74
RQ-21A
75
LookOut
76
SPY-V
77
Xr-T9 (Rotary wing UAV series)
78
Xf-T9 (Fixed wing UAV series)
79
Hermes 90
80
Hermes 900
81
Hermes 1500
82
Skylark 2
83
Boeing Experimental 1
84
85
86
87
US Army Tier 1 Test UA
88
89
90
Switchblade
91
LEMV
92
Commercial Integrator
93
RQ-4 EuroHawk
94
RQ-1 Predator
95
Heron
96
Asio
97
Spyball
98
Centaur
99
Crex
1 - B - 68
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
100
Fury
101
Aerovironment Experimental 1
102
103
104
105
Aerovironment Fixed Sensor 1
106
107
108
Aerovironment Mobile Sensor 1
109
110
111
Qube
112
Shrike
113
Global Observer
114
Thunder Quail
115
Avenger
116
ScanEagle ll
117
PATROLLER
118 x < 216
Reserved
Table B1 - 36: Vehicle Type IDs

4.2.2 Message #2: VSM Authorisation Response.
This message shall be sent by the VSM/ vehicle in response to a CUCS
Authorisation Request Message (Message #1) received from a CUCS. If the request
from the CUCS was a Broadcast Request or for unspecified connection access,
and the Source ID received in the wrapper message is for an authorised CUCS, the
VSM/ vehicle shall respond once for each vehicle or payload that it can potentially
control. For each vehicle/payload that the VSM/ vehicle has granted monitor only or
control and monitoring to a CUCS, the VSM/ vehicle shall respond with its VSM ID
(as applicable) and/or specific/logical vehicle ID(s), the Access Authorized, LOI
Authorized, and Access Granted fields set as granted to that CUCS for the controlled
station and the vehicle type and vehicle sub-type fields set correctly to the controlling
CUCS. For each vehicle/payload that the VSM/ vehicle has not granted control to
any CUCS, the VSM/ vehicle shall respond with its VSM ID (as applicable) and/or
specific/logical vehicle ID(s), Access Authorized, Access Granted set as N/A,
1 - B - 69
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
controlled station, payload type, vehicle type, and vehicle subtype to the requesting
CUCS. Where a VSM is able to monitor only or control and monitor more than one
vehicle/ payload entity, this capability shall be relayed to the CUCS by the use of
multiple instances of this message, one per available vehicle/payload combination.
If the CUCS requested a specified connection, monitor only or control and monitor,
for a specific VSM ID/vehicle ID and functionality in the Authorisation Request
message, then the VSM/ vehicle shall respond with the Access Granted and
Controlled Station Asset fields set as appropriate, with the Access Request field filled
to echo the original request. If another CUCS is in control of the requested
vehicle/payload, the VSM/vehicle shall deny control to a second CUCS unless that
CUCS is commanding an override for the requested functionality. If the granting of
control of a vehicle/payload to a CUCS eliminates the potential control of another
reported vehicle/payload entity, the VSM shall send this message to that CUCS ID
indicating that the connection to the eliminated vehicle/payload is no longer available,
(i.e., connection not authorized). For example, a VSM may be able to potentially
control two types of vehicles but only control one vehicle at a time. Once the VSM
grants control of one of the vehicle types to a CUCS, the other type is no longer
available for control.
A CUCS may monitor all VSM Authorisation Response Messages on the network,
not only the messages directed to that CUCS. By monitoring all messages, a CUCS
will know what vehicles/payloads are available for control/ monitoring and will know
what vehicles/payloads are currently being controlled by other CUCS. This may be
necessary to provide the override capability.
As specified above, the VSM Authorisation Response Message may be transmitted
from a VSM to a CUCS without an authorized connection as it is used to report
possible connections, and it is used to authorize connections.
The Presence Vector Support field can be used by the VSM and CUCS to enforce
the use of the presence vector, when required by customer or regulatory
requirements. The VSM will be required to support the Presence Vector capability
and demonstrate this support via the minimum test set described in the AEP-57
Volume 2 Validation/Test Guideline Document. However, should a specific system be
designed in such a manner that full length messages are unable to be supported,
then these systems can refuse to allow control by a CUCS declaring itself as not
supporting the presence vector by setting the LOI Authorized field to 0x00=
Connection Not Authorized.
Assuming all other parameters in the CUCS Authorisation Request are acceptable
for the VSM to grant control, then the logic applied to the Presence Vector Support
field will be as follows:
CUCS Indicates
Presence Vector
Support
VSM Indicates
Presence Vector
Support
Both CUCS and VSM

utilize the presence
vector within their
messaging to support
variable length
messaging
CUCS Indicates
VSM Indicates No
Both CUCS and VSM
1 - B - 70
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
ignore the Presence
Vector field and treat all
PVs as if all bits are set
(note that the bits need
not be set by sender;
the receiver will treat
them as if they are set,
regardless)
Presence Vector
Support
Presence Vector
Support
CUCS Indicates No
Presence Vector
Support
VSM Indicates
Presence Vector
Support
Both CUCS and VSM

ignore the Presence
regardless)
CUCS Indicates No
Presence Vector
Support
VSM Indicates No
Presence Vector
Support
Both CUCS and VSM

ignore the Presence
regardless)
Table B1 - 37: Presence Vector Support Field Logic

Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0002.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0021.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0021.04
VSM ID
Integer 4
None
See Section 1.7.6
0021.05
Data Link ID
Integer 4
None
See Section 1.7.6
0021.13
Access Authorized
Unsigned 1
Enumerated
0 = Connection Not
Authorised
1 = Monitor Only
3 = Relinquish/ Handover
0021.09
Access Granted
Unsigned 1
Enumerated
0 = N/A
1 = Monitor Only
0021.06
LOI Authorized
Unsigned 1
Bitmapped
0x01 = Not Authorized

0x02 = LOI 2
0x04 = LOI 3
0x08 = LOI 4
0x10 = LOI 5
0x00 = Unspecified
1 - B - 71
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0021.07
LOI Granted
Unsigned 1
Bitmapped
0x01 = LOI 2
0x02 = LOI 3
0x04 = LOI 4
0x08 = LOI 5
Unsigned 1
Enumerated
0 = No Mode
1 = All Modes
disengaged)
3 - 10 = Reserved 3-10
Message #2004)
13 - 14 = Reserved 13-14
engaged, but manual
distance)
17 = NavAid (Slaved
navigation beacon.)
18 = Reserved 18
21 = Launch
23 - 31 = Reserved 23-31
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
0x00 = N/A
0021.16
Flight Modes Granted

Identifies which flight
modes the CUCS is
authorisation to use. This
field only contains valid
data if the LOI Authorized is
4 or 5.
0021.08

0x0000 = No change
1 - B - 72
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0002.07
10
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
0002.08
11
Component Location
0021.12
12
Payload Type
Unsigned 2
Enumerated
0 = Not Specified / N/A

1 = EO
2 = IR
3 = EO/IR
4 = SAR
5 = Fixed Camera
6 = Comms Relay
8 = Recorder
10 - 999 = Reserved
1000 - 65535 = VSM
Specific
0021.15
13
Access Requested
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
0x04 = Broadcast
Response
0x08 = Relinquish/
Handover
This field echoes the

access request that this
response addresses
0x00 = Unspecified
1 - B - 73
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0021.10
14
Vehicle Type
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 1
Enumerated
0 - 255 = See Table B1-35
Unsigned 2
Enumerated
Unsigned 1
Enumerated
0 = Presence Vector
Ignored
1 = Presence Vector Used

assigned by STANAG
Custodian.
0021.11
15
Vehicle Subtype
the manufacturer.
0002.01
16
CUCS Type
CUCS; Numbers to be
assigned by STANAG
Custodian.
0002.02
17
CUCS Subtype
the manufacturer.
0002.05
18
Presence Vector Support

This field indicates whether
the VSM uses the presence
vector.
If and only if both the CUCS
and the VSM declare full
support for the presence
vector will the CUCS and
VSM utilize the presence
vector in the message set
to remove message
parameters; otherwise, both
the VSM and CUCS will
implement the STANAG
message set by ignoring
the presence vector field
and populating all the
message fields.
1 - B - 74
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0002.09
19
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
0x0000 = No change
Table B1 - 38: Message #2: VSM Authorisation Response

4.2.3
Message #3: Vehicle ID.
This message shall be sent by a VSM/ vehicle to the CUCS to identify the air vehicle.
The VSM ID shall be filled with the null ID when this message is transmitted directly
from a vehicle for which a ground based VSM does not exist. This message shall
indicate a Tail Number of zero, and a logical vehicle ID (Source ID) if transmitted
from a VSM, along with the VSM ID when there is no vehicle connected to the VSM.
This message shall be sent by the VSM/vehicle whenever the contents of this
message (vehicle ID, tail number, mission ID or ATC Call sign) change. The Vehicle
ID Update field allows a VSM to change a logical vehicle ID to a real vehicle ID and
vice versa. When the Vehicle ID Update field in this message is filled differently than
the Source ID field in this message, this shall signify that the currently used vehicle
ID value is to be replaced with the vehicle ID update value.
Upon initial connection with a VSM, after establishment (via Message #3) of vehicle
type and vehicle subtype, an optional configuration process may be utilized to
configure the CUCS. This configuration process will use a file in lieu of the
configuration commands directly from the air vehicle. If this option is utilized, it
eliminates the need to send the configuration messages to configure the CUCS for
the air vehicle.
The binary-formatted file will contain the messages as they would be received from
the VSM / air vehicle directly via UDP. The first message in the file shall be Message
#3, with the following fields required: 4 (Vehicle Type), 5 (Vehicle Subtype) & 6
(Owning ID). Following Message #3 will be further messages, in the same binary
format, for the particular air vehicles configuration and setup.
If the file for the air vehicle type, subtype or Owning ID, or if the checksum provided
in Message #3 received from the air vehicle does not match the checksum of the file
local to the CUCS, the VSM / air vehicle and CUCS configuration shall continue as
defined below.
1 - B - 75
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0003.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0020.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0020.04
VSM ID
Integer 4
None
See Section 1.7.6
0020.05
Vehicle ID Update
Integer 4
None
See Section 1.7.6
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 1
None
1 x < 255 (See Section

1.7.6)
Character 16
None
No Restrictions
Character 20
None
No Restrictions
Character 32
None
No Restrictions
Unsigned 2
None
No Restrictions
Vehicle ID that will replace

the current Vehicle ID.
0020.06
Vehicle Type
assigned by STANAG
Custodian.
0020.07
Vehicle Subtype
the manufacturer.
0020.08
Owning ID
Identifies the owning
country using STANAG
4586 maintained Owning ID
Table.
0020.09
Tail Number
Null terminated string with
the tail number designated
by the owning countrys
certifying agency.
(Printable characters only)
0020.10
Mission ID
Identifies mission and (by
reference) flight plan
currently executing on this
platform.
0020.11
ATC Call Sign

0020.12
10
Configuration Checksum
Identifies the checksum of
the optional configuration
file.
Table B1 - 39: Message #3: Vehicle ID
1 - B - 76
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.3 Flight Vehicle Command Messages.
4.3.1 Message #2000: Vehicle Configuration Command.
This message shall be used to initialize the AV energy storage unit to its current state
as required, usually in preparation for launch. This message shall be sent from the
CUCS to the VSM whenever the AV configuration is changed.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0040.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2000.01
Energy Storage Unit
Unsigned 1
None
No Restrictions
Unsigned 2
0.002 %
No Restrictions
0 = Aggregate of all storage

units (added for backwards
compatibility to Edition 2).
0040.04
Initial Propulsion Energy

Amount of usable
propulsion energy with
respect to the maximum
usable propulsion energy
for this energy storage unit
configuration.
Table B1 - 40: Message #2000: Vehicle Configuration Command

4.3.2 Message #2001: Vehicle Operating Mode Command.
This message shall be used to control the vehicle operating mode. The vehicle
operating mode defines the system behaviour and establishes how commands shall
be interpreted. The behaviours established include vehicle flight path response. The
intent of these behaviours is to provide a standard way of expressing common
operating modes and tactics. The specific implementation is left up to the vehicle
manufacturer.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0042.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 77
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0042.04
Data Element Name &

Description
Select Flight Path Control
Mode
Type
Units
Range
Unsigned 1
Enumerated
0 = No Mode
1 = Reserved 1
disengaged)
3 - 10 = Reserved 3-10
Message #2004)
13 - 14 = Reserved 13-14
engaged, but manual
distance)
17 = NavAid (Slaved
navigation beacon.)
18 = Reserved 18
21 = Launch
23 - 31 = Reserved 23-31
Unsigned 3
None
No Restrictions
Specifies the method for

controlling the vehicles
flight path. Manual control
modes lie in the range 1-10,
automatic control modes lie
in the range 11-31
2001.01
Activity ID
Used to identify goals,
behaviours and constraints.
0 = Immediate Activity
Table B1 - 41: Message #2001: Vehicle Operating Mode Command

4.3.3 Message #2002: Vehicle Steering Command.
This message shall be used to provide the ability to command a new flight vector to
the air vehicle. Such commands are generated by manual input. Upon receipt of this
message, the vehicles response shall be to immediately enter into a manoeuvre to
achieve the new desired flight state. The vehicles responsibility shall be to avoid
unsafe flight states during the manoeuvre to answer the new command.
The VSM shall use the General Configuration Messages to define the air vehicles
capability to support the fields commanded in Message #2002, dependent on the
current Flight mode (Message #2001, Vehicle Operating Mode Command) and the
current Altitude mode, Speed mode and Course/Heading mode states (Message
#2003, Mode Preference Command). Refer to Sections 4.24 and 4.25 General
Configuration Messages for additional details.
1 - B - 78
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2002.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0043.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0043.04
Altitude Command Type
Unsigned 1
Enumerated
0 = Not Specified
1 = Altitude
2 = Vertical Speed
3 = Rate-limited altitude
Integer 3
0.02 m
-1,000 x 100,000
Integer 2
0.05 m/s
-1,000 x 1,000
Unsigned 1
Enumerated
0 = Not Specified
1 = Heading
2 = Course
3 = Heading and Course
4 = Roll
5 = Heading Rate
Enumeration 0 added for

backwards compatibility to
Edition 2.
0043.05
Commanded Altitude
Altitude hold value to be
achieved (ignored in
Altitude Command Type =
2).
0043.06
Commanded Vertical
Speed
Vertical Speed value to be
achieved
(Used in Altitude Command
Type = 2, ignored in
1, used as rate limit in
3).
0043.07
Heading Command Type

Edition 2.
0043.21
Heading Reference
Unsigned 1
Enumerated
0 = True North
1 = Magnetic North
0043.08
Commanded Heading
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Heading hold value to be

achieved (Used in Heading
Command Type = 1 and 3,
ignored in Heading
Command Type = 2, 4, and
5). Provided in True North
if Heading Reference is 0,
and in Magnetic North if
Heading Reference is 1.
0043.09
Commanded Course
Course value to be
achieved (Used in Heading
Command Type = 2 and 3,
ignored in Heading
Command Type = 1, 4 and
5)
1 - B - 79
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0043.10
Commanded Turn Rate
Integer 2
0.0001 rad/s
No Restrictions
Integer 2
0.0001 rad/s
No Restrictions
Integer 2
BAM
No Restrictions
Heading or Course turn rate

value to be achieved (Used
in Heading Command Type
= 1 thru 3, and 5)
A zero commanded rate
indicates that the AV should
use its default rates for the
Applicable Heading
Command type mode. i.e.;
Does not apply to Heading
Command Type = 5.
0043.11
10
Commanded Roll Rate

Roll rate value to be
achieved (used in Heading
Command Type = 4)
use its default rates.
0043.12
11
Commanded Roll
(Used in Heading
Command Type = 4)
0043.13
12
Commanded Speed
Unsigned 2
0.5 m/s
x 10,000
0043.14
13
Speed Type
Unsigned 1
Enumerated
0 = Indicated Airspeed
1 = True Airspeed
2 = Ground Speed
3 = Thrust
Unsigned 2
None
1 x < 65,535
Unsigned 2
10 Pa
x 107,500
Unsigned 1
Enumerated
0 = Pressure Altitude
1 = Baro Altitude
2 = AGL
3 = WGS-84
Integer 4
BAM
-/2 x /2
Defines speed type

(reference frame) for all
speed related fields in this
message.
0043.15
14
Commanded Waypoint
Number
As defined in Section 4.12,
Mission Messages.
0043.16
15
Altimeter Setting
Local Barometric pressure
at sea level. Used to correct
pressure altitude to
barometric altitude.
0043.17
16
Altitude Type
Defines altitude type
altitude related fields in this
message.
0043.18
17
Loiter Position Latitude

Manual Loiter position
latitude command.
1 - B - 80
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0043.19
18
Loiter Position Longitude
Integer 4
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Manual Loiter position

longitude command.
2002.02
19
Thrust Direction
Direction that the thrust is
directed.
2002.03
20
Thrust
Unsigned 1
No Restrictions
2002.01
21
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 42: Message #2002: Vehicle Steering Command

4.3.4 Message #2003: Mode Preference Command.
The Message #2003, Altitude Mode, the Message #2003, Speed Mode, and the
Message #2003, Heading Mode fields are used to determine the source of the
altitude, (air)speed, and heading demands respectively for the selected (VSM
reported) Flight Mode (Message #2001, Select Flight Path Control Mode).
The Altitude, Speed, and Heading commanded values shall come from a specific
configuration message (see below) if the mode setting (report) is Configuration, and
the Altitude, Speed, and Heading commanded values shall come from Message
#2002, Vehicle Steering Command, when the mode setting (report) is Manual/
Override.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0048.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0048.04
Altitude Mode
Unsigned 1
Enumerated
0 = Configuration
1 = Manual/ Override until
reaching the Waypoint or
Loiter Point
2 = Manual/ Override
0048.05
Speed Mode
Unsigned 1
Enumerated
0 = Configuration
Loiter Point
0048.06
Heading Mode
Unsigned 1
Enumerated
0 = Configuration
Loiter Point
1 - B - 81
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2003.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 43: Message #2003: Mode Preference Command
Configuration enumeration: When in the selected Flight Mode (Message #2001,

Select Flight Path Control Mode), the Altitude, Speed, and Heading from the
Configuration Message specified (see below) for that flight mode shall be used. While
in this (altitude, speed, heading) mode, the altitude/speed/heading commanded
values shall not be altered using Message #2002, Vehicle Steering Command.
Manual/Override until reaching the Waypoint or Loiter Point enumeration:
Manual/Override commands (Enumeration 2) shall be used until the air vehicle
reaches the Waypoint or Loiter Point, at which time the commanded values shall be
taken from the Configuration commands (Enumeration 0): When in the selected
flight mode (Message #2001, Select Flight Path Control Mode), use the Manual/
Override settings for Altitude, Speed, and Heading for that flight mode until next
waypoint or loiter position has been reached, and then use the Configuration
message (see below) settings. Once the air vehicle reaches the transition point, it
shall revert to the Configuration mode. In order to re-enter the Manual/ Override
until reaching the Waypoint or Loiter Point mode, another mode shall first be
commanded.
Manual/Override enumeration: When in the selected flight mode (Message #2001,
Select Flight Path Control Mode), the Altitude, Speed, and Heading commanded
values shall always be from Message #2002, Vehicle Steering Command.
Table B1 - 44 shows the source message for the altitude/airspeed for each
combination of Flight Mode (Msg. #2001, Select Flight Path Control Mode) and
Altitude or Airspeed Mode (Msg. #2003, Altitude Mode, or Msg. #2003, Speed
Mode).
Flight Mode
Altitude or Airspeed Mode
2 Flight Director
0 Configuration
1 Manual until reaching the
WP, Loiter
2 Manual/Override
Not defined
2002
0 Configuration
WP, Loiter
2 Manual/Override
13002
2002
11 Waypoint
1 - B - 82
Source Message for

Altitude or Airspeed
2002
2002
12 Loiter
0 Configuration
WP, Loiter
2 Manual/Override
All other Flight Modes
0 Configuration
WP, Loiter
2 Manual/Override
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
2004
2002
2002
Not defined
2002
2002
Table B1 - 44: Source Message for Altitude/Airspeed
Table B1 - 45 shows the source message for the heading or the lat/long, dependent
on which is valid, for each combination of Flight Mode (Message. #2001, Select
Flight Path Control Mode) and Heading Mode (Message #2003, Heading Mode).
Heading Mode
2 Flight
Director
0 Configuration
1 Manual until reaching
the WP, Loiter
2 Manual/Override
Not defined
2002
Not valid
Not valid
2002
Not valid
0 Configuration
the WP, Loiter
2 Manual/Override
Not valid
2002
13002
2002
2002
2002
0 Configuration
the WP, Loiter
2 Manual/Override
Not defined
Not valid
Not defined
2002
Not valid
2002
0 Configuration
the WP, Loiter
2 Manual/Override
Not defined
2002
Not defined
2002
2002
2002
11
Waypoint
12 Loiter
All other
Flight Modes
Source Message
for
Heading
Source
Message for
Lat/Long
Flight Mode
Table B1 - 45: Source Message for Heading
Msg # Specified Mode valid and the specified message shall be used by the VSM if
the functionality is supported by the VSM.
Not valid Mode shall never be allowed by STANAG 4586 CUCS or VSM.
Not defined STANAG 4586 does not define the functionality; the VSM shall define
the required functionality and make the required controls available at the CUCS. The
VSM may use a formatted DLI message for the functionality if desired.
1 - B - 83
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.3.5 Message #2004: Loiter Configuration.
This message shall be used to command the loiter pattern that the AV must use
when in the Loiter flight mode. (Refer to Message #2001, Vehicle Operating Mode
Command). The loiter position is defined by 0043.18 Loiter Position Latitude and
0043.19 Loiter Position Longitude. The loiter altitude and loiter airspeed shall be
used as the commanded values for the AV dependent on the current Altitude Mode
and current Speed Mode settings. Refer to Message #2003, Mode Preference
Command, for additional details.
If the loiter length is specified in time, the time is for the inbound leg of the loiter
pattern. The inbound leg is, by convention, the first tangent leg the AV flies. The
time and the Loiter Speed (0041.11 and 0041.12) determine the distance travelled on
the inbound leg. The AV must adjust the outbound leg time to be able to travel that
same distance on the outbound leg while maintaining speed.
Loiter patterns can be repeated using the Loiter Duration field. Repetition can be
specified as the number of laps or the total time to execute the pattern using the
Loiter Duration Units field.
Loiter entry and exit behaviour is AV-dependent, including what to do when Loiter
Duration is specified in time and there is insufficient time to complete another lap.
The ATC Hold pattern (0041.04 = 5) is intended to be used to support a standard
hold pattern for air traffic control. It has the same shape as the Racetrack pattern,
but the primary difference is that pattern is not centred at the loiter point. Rather, the
inbound leg terminates at the loiter point, also known as the holding fix. Thus, the
Loiter Bearing and Loiter Direction have a significant impact to the footprint of the
ATC Hold pattern relative to the loiter point. The ATC Hold pattern is available when
the AV can properly execute the pattern described. Alternatively, the CUCS may
transform the parameters provided by ATC into a Racetrack pattern (0041.04 = 2) to
send to the AV.
capability to support the fields commanded in Message #2004. Refer to Sections
4.24 and 4.25 General Configuration Messages for additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2004.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0041.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0041.04
Loiter Type
Unsigned 1
Enumerated
1 = Circular
2 = Racetrack
3 = Figure 8
4 = Hover
5 = ATC Hold
6 - 9 = Reserved
0041.05
Loiter Radius
Unsigned 2
1.5 m
1.5 x
The radius of the turn for

Circular, Racetrack, and
Figure 8 patterns.
1 - B - 84
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0041.06
Loiter Length
Unsigned 2
1.5 m or s
1.5 x
Unsigned 1
Enumerated
0 = Distance (m)
1 = Time (s)
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
0 = Vehicle Dependent
1 = Clockwise
2 = Counter-Clockwise
3 = Into the wind
Used for Racetrack and

Figure 8 to define length of
pattern, centred around the
Loiter Point (defined in
Message #2002) in the
direction of the Loiter
Bearing.
2004.01
Loiter Length Units

Used for specifying the
units of measurement for
the Loiter Length. Timebased loiter lengths only
apply to Racetrack
patterns.
0041.07
Loiter Bearing
The bearing of the loiter
pattern, referenced to the
Message #2002), from True
North.
0041.08
Loiter Direction
Defines direction of turn,
viewed from above, when
rounding the loiter point
defined by Vehicle
Steering Command
Message (Message #2002).
0041.09
Loiter Altitude
Integer 3
0.02 m
-1,000 x 100,000
0041.10
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
0041.15
10
Altitude Change
Behaviour
Unsigned 1
Enumerated
0 = Manual
1 = Critical Altitude
2 = Gradual
3 = Max Rate (ROC/ROD)
4 = UAV Dependent
(Optimum Performance)
5 = Not Defined
0041.11
11
Loiter Speed
Unsigned 2
0.5 m/s
x 10,000
0041.12
12
Speed Type
Unsigned 1
Enumerated
1 = True Airspeed
2 = Ground Speed
Defines speed type

message
1 - B - 85
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2004.15
13
Flying Behaviour
Unsigned 1
Enumerated
0 = Flyby
1 = Flyover
2 = Vehicle Discretion
(added for backwards
compatibility to Edition 2)
2004.17
14
Loiter Duration
Unsigned 2
User
Specified
No Restrictions
Unsigned 1
Enumerated
0 = Lap
1=s
Unsigned 3
None
No Restrictions
Expected duration of a
loiter. A zero value
indicates forever.
2004.18
15
Loiter Duration Units

Specifies the units of
measurement for Loiter
Duration (2004.17).
2004.02
16
Activity ID
Table B1 - 46: Message #2004: Loiter Configuration
1 - B - 86
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Figure B1 - 9: Loiter Pattern
1 - B - 87
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.3.6 Message #2005: Flight Termination Command.
This message shall be used to provide means for the CUCS to issue a flight
termination command to the VSM. To accomplish flight termination, this message
shall be sent twice with two different values in field 4 (once to arm, and a second time
to execute).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2005.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0046.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0046.04
Commanded Flight
Termination State
Unsigned 1
Enumerated
0 = Reset FT System
1 = Arm FT System
2 = Execute FT Seq.
0046.05
Flight Termination Mode
Unsigned 1
Enumerated
0 = Not Specified
1 - 255 = VSM specific
2005.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 47: Message #2005: Flight Termination Command

4.3.7 Message #2006: Relative Route/Waypoint Absolute Reference Message.
This message shall be used by the CUCS to identify the absolute reference system
for relative routes and their associated waypoints. The intent of this message is to
support moving platforms for launch and recovery, and to support usage of reusable
route templates (e.g. for search patterns). This message shall be provided prior to
commanding programmed flight along any relative route, and updated as necessary
otherwise.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2006.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0047.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0047.04
Latitude (Y-axis zero)
Integer 4
BAM
-/2 x /2
0047.05
Longitude (X-axis zero)
Integer 4
BAM
No Restrictions
0047.06
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message
0047.07
Altitude
Integer 3
0.02 m
-1,000 x 100,000
0047.08
Orientation
Integer 2
BAM
No Restrictions
Defines heading of Y-axis.
1 - B - 88
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0047.09
Route ID
Character 20
None
No Restrictions
Unsigned 3
None
No Restrictions
Text identifier of route, or

null to update all routes.
2006.01
Activity ID
Table B1 - 48: Message #2006: Relative Route/Waypoint Absolute Reference

Message
4.3.8 Message #2007: Air Vehicle Lights.
This message shall be used by the CUCS to control the air vehicle lights.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2007.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0044.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0044.04
Set Lights
Unsigned 2
Bitmapped
0x0001 = Nav
0x0002 = NavIR
0x0004 = Strobe
0x0008 = StrobeIR
0x0010 = NVD
0x0020 = Reserved
0x0040 = Landing
0x0080 = LandingIR
0x0100 = Vehicle Specific 1
Unsigned 3
None
No Restrictions
When a bit is set the lights

are commanded on, when
the bit is cleared the lights
are commanded off.
2007.01
Activity ID
Table B1 - 49: Message #2007: Air Vehicle Lights

4.3.9 Message #2008: Engine Command.
This message shall be used by the CUCS to control the air vehicle engines. It is sent
for each engine.
4.24 and 4.25 General Configuration Messages for additional details.
1 - B - 89
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2008.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0045.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0045.04
Engine Number
Unsigned 1
None
No Restrictions
ID of engine currently being

commanded
0045.05
Engine Command
Unsigned 1
Enumerated
0 = Stop
1 = Start
2 = Enable/Run
3 - 9 = Reserved
2008.20
Reverse Thrust Power
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 1
Enumerated
0 = Off-All Engines
1 = On-All Engines
2 = Auto-All Engines
3 = Not Specified
4 - 9 = Reserved
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 3
None
No Restrictions

Edition 2.
2008.21
Reverse Thrust
For turbojets, it is
applicable for thrust
reversers; for props, it is
applicable for reverse prop
pitch.
Edition 2.
2008.22
Ignition Switch Power

Power to the engine ignition
circuit.
Edition 2.
2008.23
Ignition Switch Activation

Edition 2.
2008.01
Activity ID
Table B1 - 50: Message #2008: Engine Command

4.3.10 Message #2009: Zeroize Encryption Keys Command.
This message shall be used by the CUCS to request that the encryption keys
zeroize. The VSM will perform the appropriate zeroize operations for the ground
and/or the VDTs for that vehicles data links.
1 - B - 90
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2009.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
2009.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2009.02
Zeroize Air Vehicle
Unsigned 1
Enumerated
0 = Ignore
1 = Command Zeroize
Unsigned 1
Enumerated
0 = Ignore
1 = Command Zeroize
Unsigned 3
None
No Restrictions
Zeroizes all keys in vehicle

2009.03
Zeroize GCS
Zeroizes all keys in ground
control system associated
with the specified Vehicle
ID. If Vehicle ID = 0,
applies to all GCS
encryption equipment
controlled by the VSM.
2009.04
Activity ID
Table B1 - 51: Message #2009: Zeroize Encryption Keys Command

4.3.11 Message #2010: AV Stick Command.
The AV Stick Command message is used to control the AV flight surface and taxi
related functions. The AV Stick Command Message shall not be transmitted between
a CUCS and the AV without an authorized connection. This message shall be used
to send AV stick commands from the CUCS to the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2010.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
2010.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2010.02
Lateral Stick
Integer 1
None
-127 x
Integer 1
None
-127 x
Integer 1
None
-127 x
Unsigned 1
None
No Restrictions
-127 is full left, 0 is centre,

127 is full right
2010.03
Longitudinal Stick
-127 is full back, 0 is centre,
127 is full front
2010.04
Rotational Stick (Rudder)

-127 is full counter
clockwise, 0 is centre, 127
is full clockwise
2010.05
Throttle Stick - Engine 1

0 is idle, 255 is full
1 - B - 91
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2010.06
Pitch Stick - Engine 1
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Integer 1
None
-127 x
-127 is full reverse, 0 is

neutral 127 is full
forward/up, -128 feather
2010.07

2010.08

neutral 127 is full
2010.09

2010.10
10

neutral 127 is full
2010.11
11

2010.12
12

neutral 127 is full
2010.13
13
Taxi Stick
127 is full right
Table B1 - 52: Message #2010: AV Stick Command

4.3.12 Message #2011: Area Transmission Command.
Area Transmission Command Message is sent from the CUCS to the AV or from the
AV to the CUCS to indicate that a new area definition is about to be transmitted. The
CUCS can also send the message to the AV to request the transmission of an area.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2011.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
2011.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2011.02
AV Cruise Altitude
Integer 3
0.02 m
-1,000 x 100,000
2011.03
Area Min Altitude
Integer 3
0.02 m
-1,000 x 100,000
2011.04
Area Max Altitude
Integer 3
0.02 m
-1,000 x 100,000
1 - B - 92
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2011.05
Area Safety Offset
Unsigned 2
No Restrictions
Distance from edge of

defined Stay In polygon
before a manoeuvre is
required to avoid crossing
the edge of the polygon.
2011.06
Area Transfer Mode
Unsigned 1
Enumerated
0 = Not Assigned
1 = Initiate Upload
2 = Upload Complete
3 = Initiate Download
4 = Download Complete
5 = Request Transmission
6 = Cancel Upload
7 = Verify Upload
2011.07
Area ID
Unsigned 1
None
No Restrictions
Unsigned 1
None
1x
Unique ID for area

0 = Download all areas
2011.08
Area Loop Count

Number of polygon loops
defined for this Area
Table B1 - 53: Message #2011: Area Transmission Command

4.3.13 Message #2012: Area Polygon Loop Segment Message.
This message shall be used to define an area. An area can be made up of one or
more polygons. A single polygon (also called a loop) is made up of a set of vertices.
A single polygon cannot have crossed lines. These polygons can define safe
airspace (Zone Mode set to Stay in), they can define restricted airspace (Zone
Mode set to Keep out) or other areas as defined in this message. The Figure below
shows examples of how polygons go toward forming an area. If keep in and Stay
out polygons in an area overlap, the polygon with the higher polygon ID will be
active for the overlapped area.
Field ten of Message #2012 (Area Polygon Loop Segment Message) is stated as
being a Vertices List. This is an array of up to 50 latitude and longitude pairs.
1 - B - 93
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Figure B1 - 10: Valid Area Examples

Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2012.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
2012.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2012.02
Area ID
Unsigned 1
None
1x
Unsigned 1
Enumerated
0 = Keep Out
1 = Stay In
2 = Surveillance
3 = No Collection
4 = No Emission
Unsigned 1
None
1<x
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 5
0.001 s
See Section 1.7.2
Unique identifier of the area

this polygon is a member
of.
2012.03
Activity Type
Identifies the activity with
(non-zero activity ID) to
which this constraint is to
be applied
2012.04
Polygon ID
A unique identifier for this
polygon
2012.05
Polygon Start Time

Used to identify the
absolute time that this
polygon definition begins
2012.06
Polygon End Time

polygon definition ends
2012.07
Number of Segments in
this polygon (Loop)
Unsigned 1
None
1<x
2012.08
Loop segment number
Unsigned 1
None
1<x
2012.09
Number of Vertices in this

Segment (n)
Unsigned 1
None
3 < x 50
1 - B - 94
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
Vertices List repetition begins (where n = 1 to "Number of Vertices in this Segment (n)")
2012.10
Latitude #<n>
Integer 4
BAM
-/2 x /2
2012.12
Longitude #<n>
Integer 4
BAM
No Restrictions
Unsigned 3
None
No Restrictions
Vertices List repetition ends

2012.11
110
Activity ID
Table B1 - 54: Message #2012: Area Polygon Loop Segment Message

4.3.14 Message #2013: Joystick Command.
This message shall be used to send joystick input data to the vehicle. A joystick may
be used to control any number of controllable elements exposed by the vehicle
system.
This message shall be used to provide the Vehicle with joystick data from the CUCS.
This message is constructed so that the CUCS can send a set of joystick inputs in
one or more messages. A CUCS may send one or multiple messages to report a
single set of joystick inputs.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2013.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
2013.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2013.02
Number of Analogue
Inputs Reported
Unsigned 1
None
x 32
Identifies the number of

analogue inputs reported in
this message
Analog Inputs repetition begins (where n = 1 to "Number of Analogue Inputs Reported")
2013.03
Controllable Analog
Element ID #<n>
Unsigned 2
None
No Restrictions
Integer 1
None
-127 x
Identifies the analogue

device being controlled
2013.04
Axis Control Value #<n>

-127 is Axis Min (full back,
left, or counter clockwise);
127 is Axis Max (full front,
right or clockwise)
Analog Inputs repetition ends
1 - B - 95
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
2013.67
67
Data Element Name &

Description
Number of Discrete
Inputs Reported
Type
Units
Range
Unsigned 1
None
x 32
Identifies the number of

discrete inputs reported in
this message
Discrete Inputs repetition begins (where n = 1 to "Number of Discrete Inputs Reported")
2013.06
Controllable Discrete
Element ID #<n>
Unsigned 2
None
No Restrictions
Integer 1
Enumerated
0 = Off
1 = On
Identifies the discrete

device being controlled
2013.07
Discrete Control Value

#<n>
0 is button not pressed; 1 is
button pressed
Discrete Inputs repetition ends
Table B1 - 55: Message #2013: Joystick Command

4.3.15 Message #2014: Emergency Mode Command.
This message shall be used to transmit the emergency mode to the VSM/AV that the
AV should enter if not in the Waypoint Flight path Control Mode.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2014.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
2014.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2014.02
Contingency A Command
Unsigned 1
Enumerated
0 = Bypass
1 = Waypoint
2 = Glide
3 = Take-off Climb
4 - 9 = Reserved
2014.03
Contingency A Delay
Unsigned 2
No Restrictions
1 - B - 96
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
2014.09
Data Element Name &

Description
Required Manual Restore
Time A
Type
Units
Range
Unsigned 2
No Restrictions
Time prior to AV executing

loss link manoeuvre where
restoration of the link will
not result in automatic
recovery of CUCS control.
This value must be greater
or equal to the Contingency
Delay.
CUCS control is regained
when a Vehicle Operating
Mode Command is
received by the vehicle.
2014.04
Contingency A Waypoint
Number
Unsigned 2
None
1x
2014.05
Contingency B Command
Unsigned 1
Enumerated
0 = Bypass
1 = Waypoint
2 = Glide
3 = Take-off Climb
4 - 9 = Reserved
2014.06
Contingency B Delay
Unsigned 2
No Restrictions
2014.10

Time B
Unsigned 2
No Restrictions
Time prior to AV executing

loss link manoeuvre where
restoration of the link will
not result in automatic
recovery of CUCS control.
This value must be greater
or equal to the Contingency
Delay.
CUCS control is regained
when a Vehicle Operating
Mode Command is
received by the vehicle
2014.07
Contingency B Waypoint
Number
Unsigned 2
None
1x
2014.08
10
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 56: Message #2014: Emergency Mode Command
1 - B - 97
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.3.16 Message #2015: Energy Storage Unit Configuration.
This message is sent from the Vehicle/VSM to the CUCS to indicate the capacity of
each energy storage unit. This command shall not be sent if only one energy storage
unit is present; Message # 3000 shall be used. If multiple energy storage units are
present and the total of the capacity does not equal the value(s) specified in
Message # 3000, then the energy values in Message # 3000 will be ignored.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
2015.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
2015.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
2015.02
Energy Storage Unit ID
Unsigned 1
None
No Restrictions
Float
kg
No Restrictions
Float
No Restrictions
Identifies particular energy

storage unit (e.g. fuel tank,
battery bank) on the
vehicle.
2015.03
Propulsion Fuel Capacity

Amount of weight in fuel
that can be carried in this
energy storage unit.
<0: Not Applicable
2015.04
Propulsion Battery
Capacity
<0: Not Applicable
Table B1 - 57: Message #2015: Energy Storage Unit Configuration

4.4 Flight Vehicle Status Messages.
4.4.1 Message #3000: Vehicle Configuration.
This message shall be used to specify the characteristics of the vehicle, primarily for
flight planning purposes. It indicates the current characteristics of the vehicle either
as specified by type by the manufacturer, or based on current loading. For instance,
Optimum Cruise Speed is likely only to be available as the manufacturer-specified
performance index, even though presence of extra load or external stores may cause
the number to vary in an unknown manner.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 98
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0100.05
Configuration ID
Unsigned 4
None
No Restrictions
Float
kg
No Restrictions
Float
No Restrictions
Unsigned 2
0.05 m/s
No Restrictions
Identifies particular
configuration of the air
vehicle as specified by the
manufacturer. (This
manufacturer-specified
identifier is used by the
VSM to provide vehicle
specific data, such as
current weight and c.g.
given current stores status.)
0100.06
Propulsion Fuel Capacity

Amount of weight in fuel
that can be carried for this
configuration.
<0: Not Applicable
0100.07
Propulsion Battery
Capacity
<0: Not Applicable
0100.08
Maximum Indicated
Airspeed
Not to exceed dash speed
0100.09
Optimum Cruise
Indicated Airspeed
Unsigned 2
0.05 m/s
No Restrictions
0100.10
Optimum Endurance
Indicated Airspeed
Unsigned 2
0.05 m/s
No Restrictions
0100.11
Maximum Load Factor
Unsigned 1
m/s
No Restrictions
Float
kg
No Restrictions
Float
No Restrictions
Not-to-exceed G-load
tolerance
0100.12
Gross Weight
Calculated gross weight of
current configuration,
including effects of fuel load
changes.
Determined by Vehicle
Configuration
0100.13
10
X_CG
Calculated centre of gravity
of current configuration
rearward from the nose.
Determined by Vehicle
Configuration
1 - B - 99
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0100.14
11
Number of Engines
Unsigned 1
None
No Restrictions
3000.01
12
Fuel Density
Unsigned 1
5 kg/m
No Restrictions
Table B1 - 58: Message #3000: Vehicle Configuration

4.4.2 Message #3001: Vehicle Operating Mode Report.
This message shall be used to report the vehicle-operating mode, as commanded

from the Vehicle Operating Mode Command (Message #2001).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0106.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0106.04
Select Flight Path Control

Mode
Unsigned 1
Enumerated
0 = No Mode
1 = Reserved 1
disengaged)
3 - 10 = Reserved 3-10
Message #2004)
13 - 14 = Reserved 13-14
engaged, but manual
distance)
17 = NavAid (Slaved
navigation beacon.)
18 = Reserved 18
21 = Launch
23 - 31 = Reserved 23-31
Specifies the method for

controlling the vehicles
flight path. Manual control
modes lie in the range 1-10,
automatic control modes lie
in the range 11-31
Table B1 - 59: Message #3001: Vehicle Operating Mode Report

4.4.3 Message #3002: Vehicle Operating States.
This message shall be used to report the current air vehicle operating state.
1 - B - 100
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3002.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0104.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0104.04
Commanded Altitude
Integer 3
0.02 m
-1,000 x 100,000
0104.05
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
0104.06
Commanded Heading
Integer 2
BAM
No Restrictions
0104.07
Commanded Course
Integer 2
BAM
No Restrictions
0104.08
Commanded Turn Rate
Integer 2
0.0001 rad/s
No Restrictions
0104.09
Commanded Roll Rate
Integer 2
0.005 rad/s
No Restrictions

use its default rates.
0104.10
Commanded Speed
Unsigned 2
0.5 m/s
x 10,000
0104.11
Speed Type
Unsigned 1
Enumerated
0 = Indicated / Calibrated
Airspeed
1 = True Airspeed
2 = Ground Speed
3 = Thrust
Integer 1
No Restrictions
Unsigned 2
0.0016 %
x 100
Unsigned 2
0.0016 %
x 100
Unsigned 2
0.0002 %/s
x 13.1
Integer 2
BAM
No Restrictions
Defines speed type

message.
0104.12
10
Power Level
Average throttle setting of
all engines
Nominally 0-110 Percent
0104.21
11
Bingo Energy
Minimum energy required
to return to base with
reserve energy.
0104.16
12
Current Propulsion
Energy Level
Reported as a percentage
of maximum usable energy
for interoperable gauge
displays.
0104.17
13
Current Propulsion
Energy Usage Rate
Total consumption as a
percentage of maximum
usable energy of this
configuration.
0104.18
14
Commanded Roll
1 - B - 101
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0104.19
15
Altitude Command Type
Unsigned 1
Enumerated
1 = Altitude
2 = Vertical Speed
3 = Rate-limited altitude
0104.20
16
Heading Command Type
Unsigned 1
Enumerated
1 = Heading
2 = Course
3 = Heading and Course
4 = Roll
5 = Heading Rate
3002.01
17
AV State
Unsigned 1
Enumerated
0 = Unknown
1 = Power Up
2 = Pre-start
3 = Pre-launch
4 = Launch Abort
5 - 9 = Reserved
10 - 255 = VSM Specific
Integer 2
BAM
No Restrictions
Unsigned 1
No Restrictions
The reported flight phase of

the air vehicle.
3002.02
18
Thrust Direction
Direction that the thrust is
directed.
3002.03
19
Thrust
Table B1 - 60: Message #3002: Vehicle Operating States

4.4.4 Message #3003: Mode Preference Report.
The VSM shall use the Mode Preference Report message to report the Altitude
mode, Speed mode, and Heading mode states at the VSM to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0109.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0109.04
Altitude Mode
Unsigned 1
Enumerated
0 = Configuration
Loiter Point
0109.05
Speed Mode
Unsigned 1
Enumerated
0 = Configuration
Loiter Point
0109.06
Heading Mode
Unsigned 1
Enumerated
0 = Configuration
Loiter Point
Table B1 - 61: Message #3003: Mode Preference Report
1 - B - 102
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.4.5 Message #3004: Loiter Configuration Report.
This message shall be used by the VSM/ AV to report the loiter pattern/configuration
that the AV is using in the Loiter flight mode, or other flight mode(s) as applicable.
Refer to Message #2004, Loiter Configuration, for a description of the patterns.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3004.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
3004.06
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3004.07
Loiter Type
Unsigned 1
Enumerated
1 = Circular
2 = Racetrack
3 = Figure 8
4 = Hover
5 = ATC Hold
6 - 9 = Reserved
3004.08
Loiter Radius
Unsigned 2
1.5 m
1.5 x
Unsigned 2
1.5 m or s
1.5 x
Unsigned 1
Enumerated
0 = Distance (m)
1 = Time (s)
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
1 = Clockwise
3 = Into the wind
Integer 3
0.02 m
-1,000 x 100,000

Figure 8 patterns.
3004.09
Loiter Length
Bearing.
3004.03
Loiter Length Units

apply to Racetrack
patterns.
3004.10
Loiter Bearing
Message #2002), from True
North.
3004.11
Loiter Direction
Defines direction of turn,
viewed from above, when
rounding the loiter point
defined by Vehicle
Steering Command
Message (Message #2002).
3004.12
Loiter Altitude
1 - B - 103
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3004.13
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
3004.02
10
Altitude Change
Behaviour
Unsigned 1
Enumerated
0 = Manual
2 = Gradual
3 = Max Rate (ROC/ROD)
4 = UAV Dependent
5 = Not Defined
3004.14
11
Loiter Speed
Unsigned 2
0.5 m/s
x 10,000
3004.15
12
Speed Type
Unsigned 1
Enumerated
1 = True Airspeed
2 = Ground Speed
Defines speed type

message
3004.01
13
Flying Behaviour
Unsigned 1
Enumerated
0 = Flyby
1 = Flyover
3004.04
14
Loiter Duration
Unsigned 2
Lap or s
1x
Unsigned 1
Enumerated
0 = Lap
1=s
loiter
3004.05
15

Specifies the units of
measurement for Loiter
Duration (3004.04).
Table B1 - 62: Message #3004: Loiter Configuration Report

4.4.6 Message #3005: Flight Termination Mode Report.
This message shall be used to report the flight termination command set at the VSM
and its current status. This message shall be sent in response to the Flight
Termination Message (Message #2005) and whenever the current status of flight
termination changes.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3005.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0108.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0108.04
Reported Flight
Termination State
Unsigned 1
Enumerated
0 = Reset FT System
1 = Arm FT System
2 = Execute FT Seq.
0108.05
Reported Flight
Termination Mode
Unsigned 1
Enumerated
0 = Not Specified
1 - 255 = VSM specific
1 - B - 104
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 63: Message #3005: Flight Termination Mode Report
4.4.7 Message #3006: Vehicle Lights State.
This message shall be used by the VSM to report the state of the air vehicle lights.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3006.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0107.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0107.04
Navigation Lights State
Unsigned 2
Bitmapped
0x0001 = Nav
0x0002 = NavIR
0x0004 = Strobe
0x0008 = StrobeIR
0x0010 = NVD
0x0020 = Reserved
0x0040 = Landing
0x0080 = LandingIR

are commanded off
Table B1 - 64: Message #3006: Vehicle Lights State

4.4.8 Message #3007: Engine Operating States.
This message shall be used to report the operating state of a given engine and its
major components. For vehicles with multiple engines, full operating state shall
require one such message for each engine. The intent of this message is to provide
data for a generic set of indicators for the operator. (Additional information about
engine operating state and health is left as a vehicle-specific function.)
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3007.00
Presence Vector
Unsigned 5
Bitmapped
No Restrictions
0105.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0105.04
Engine Number
Unsigned 2
None
No Restrictions
Unsigned 1
Enumerated
0 = Stopped
1 = Started
2 = Enabled/Running
3 - 9 = Reserved
ID of engine currently being

reported
0105.05
Engine Status
1 - B - 105
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0105.06
3007.01
Data Element Name &

Description
Type
Units
Range
Reported Engine
Command
Unsigned 1
Enumerated
0 = Stop
1 = Start
2 = Enable/Run
3 - 9 = Reserved
Reverse Thrust Power

Status
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Added for backwards

compatibility to Edition 2.
3007.02
Reported Reverse Thrust
Unsigned 1
Enumerated
0 = Off-All Engines
1 = On-All Engines
2 = Auto-All Engines
3 - 9 = Reserved
3007.03
Ignition Switch Power

Status
Unsigned 1
Enumerated
0 = Off
1 = On
Power to the engine ignition

circuit
3007.04
Ignition Switch Activation
Unsigned 1
Enumerated
0 = Off
1 = On
0105.07
Engine Power Setting
Unsigned 2
0.0017 %
x 110
3007.12
10
Engine Speed 1 Type
Unsigned 1
Enumerated
0 = Output Shaft
1 = Gas Turbine
2 = Power Turbine
3 = Rotor
4 = N/A
5 = Not Specified
Unsigned 2
0.5 rad/s
x 21,000
Unsigned 1
Enumerated
0 = Output Shaft
1 = Gas Turbine
2 = Power Turbine
3 = Rotor
4 = N/A
5 = Not Specified
Unsigned 2
0.5 rad/s
x 21,000
Unsigned 1
Enumerated
0 = Output Shaft
1 = Gas Turbine
2 = Power Turbine
3 = Rotor
4 = N/A
5 = Not Specified
Major component of engine

selected.
Enumerations 4 & 5 added
for backwards compatibility
to Edition 2.
0105.08
11
Engine Speed 1
selected
3007.13
12
Engine Speed 2 Type

selected.
to Edition 2.
3007.14
13
Engine Speed 2
selected
3007.15
14
Engine Speed 3 Type

selected.
to Edition 2.
1 - B - 106
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3007.16
15
Engine Speed 3
Unsigned 2
0.5 rad/s
x 21,000

selected
3007.25
16
Propeller Pitch Angle
Integer 1
0.02 rad
-/2 x < /2
0105.10
17
Output Power (Shaft

Torque) Status
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
3007.18
18
Engine Temperature 1
Type
Unsigned 1
Enumerated
0 = N/A
1 = Engine Body
2 = Inlet Gas
3 = Exhaust Gas
4 = Rotor Air Outlet
5 = Lubricant - Engine
6 = Lubricant Transmission
7 = Coolant
8 = Fuel
9 = Induction for Pre-Heater
Unsigned 2
0.5 K
172.15 x 1,500.15
Unsigned 1
Enumerated
0 = N/A
1 = Engine Body
2 = Inlet Gas
3 = Exhaust Gas
7 = Coolant
8 = Fuel
Unsigned 2
0.5 K
172.15 x 1,500.15

selected
0105.11
19
selected
3007.19
20
Type
selected
3007.20
21
selected
1 - B - 107
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
3007.21
22
Data Element Name &

Description
Type
Type
Units
Range
Unsigned 1
Enumerated
0 = N/A
1 = Engine Body
2 = Inlet Gas
3 = Exhaust Gas
7 = Coolant
8 = Fuel
Unsigned 2
0.5 K
172.15 x 1,500.15
Unsigned 1
Enumerated
0 = N/A
1 = Engine Body
2 = Inlet Gas
3 = Exhaust Gas
7 = Coolant
8 = Fuel
Unsigned 2
0.5 K
172.15 x 1,500.15

selected
3007.22
23
selected
3007.23
24
Type
selected
3007.24
25
selected
3007.05
26
Engine Pressure 1 Type
Unsigned 1
Enumerated
0 = N/A
1 = Fuel
2 = Lubricant Engine
4 = Coolant
5 = Manifold
3007.06
27
Engine Pressure 1
Unsigned 2
10 Pa
x 107,500
3007.07
28
Engine Pressure 1 Status
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Status is for the Engine

Pressure Type selected
1 - B - 108
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3007.08
29
Engine Pressure 2 Type
Unsigned 1
Enumerated
0 = N/A
1 = Fuel
2 = Lubricant Engine
4 = Coolant
5 = Manifold
3007.09
30
Engine Pressure 2
Unsigned 2
10 Pa
x 107,500
3007.10
31
Engine Pressure 2 Status
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Unsigned 1
Enumerated
0 = Detection or
suppression circuit trouble
1 = Detection and
suppression circuits normal
2 = Detection circuit alarm
one
3 = Detection circuit alarm
two
4 = Suppression material
discharged
5 = No status
Unsigned 3
0.0017 %/s
x 100
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Status is for the Engine

Pressure Type selected
0105.16
32
Fire Detection Sensor

Status
Edition 2.
3007.11
33
Engine Energy Flow

Flow is percent of full
energy capacity
0105.11
34
Engine Body
Temperature Status
For reciprocating engines,
this state is nominally
reported as cylinder head
temperature.
Added for backwards
0105.12
35
Exhaust Gas Temperature

Status
Added for backwards
1 - B - 109
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0105.13
36
Data Element Name &

Description
Coolant Temperature
Status
Type
Units
Range
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Unsigned 1
Enumerated
0 = No Status
1 = Low Red
2 = Low Yellow
3 = Low Green
4 = Normal Green
5 = High Green
6 = High Yellow
7 = High Red
Added for backwards

0105.15
37
Lubricant Temperature
Status
Added for backwards
Table B1 - 65: Message #3007: Engine Operating States

4.4.9 Message #3008: Zeroize Encryption Keys State.
This message shall be used by the VSM to report the state of the zeroized command.
The VSM will report the Zeroize Air Vehicle completion status as completed as the
vehicle cannot respond further once it has been zeroized.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3008.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
3008.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3008.02
Zeroize Air Vehicle State
Unsigned 1
Enumerated
0 = Zeroize not Completed

1 = Zeroize Completed
3008.03
Zeroize GCS State
Unsigned 1
Enumerated
0 = Zeroize not Completed

1 = Zeroize Completed
Table B1 - 66: Message #3008: Zeroize Encryption Keys State

4.4.10 Message #3009: Air and Ground Relative States.
This message shall be used to send the current state of the parameters defined in
this message from the air vehicle to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3009.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0102.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0102.04
Angle of Attack
Integer 2
BAM
No Restrictions
0102.05
Angle of Sideslip
Integer 2
BAM
No Restrictions
0102.06
True Airspeed
Unsigned 2
0.05 m/s
x 1,500
1 - B - 110
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0102.07
Indicated Airspeed
Unsigned 2
0.05 m/s
x 1,000
0102.08
Outside Air Temp
Unsigned 2
0.5 K
172.15 x 327.65
0102.09
U_Wind
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Unsigned 2
10 Pa
x 107,500
Integer 3
0.02 m
-1,000 x 100,000
Integer 2
0.05 m/s
-1,000 x 1,000
Estimated wind component

along true north vector
0102.10
V_Wind
along true east vector
0102.11
Altimeter Setting
0102.12
10
Barometric Altitude
Altitude based on Altimeter
Setting
0102.13
11
Barometric Altitude Rate

Estimated vertical velocity
(+ up) based on pressure
rate from air data system
0102.14
12
Pressure Altitude
Integer 3
0.02 m
-1,000 x 100,000
0102.15
13
AGL Altitude
Integer 3
0.02 m
-1,000 x 100,000
0102.16
14
WGS-84 Altitude
Integer 3
0.02 m
-1,000 x 100,000
0102.17
15
U_Ground
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Ground Speed component

0102.18
16
V_Ground
Table B1 - 67: Message #3009: Air and Ground Relative States

4.4.11 Message #3010: Body-Relative Sensed States.
This message shall be used to send the air vehicle body-relative sensed states to the
CUCS. Directly sensed body-relative states are packaged as a separate message
type from other vehicle states because these terms may need to be known at
substantially higher rates for various control-related functions.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3010.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0103.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 111
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0103.04
X_Body_Accel
Integer 2
0.005 m/s
-100 x 100
Integer 2
0.005 m/s
-100 x 100
Integer 2
0.005 m/s
-100 x 100
Longitudinal acceleration, +
forward
0103.05
Y_Body_Accel
Lateral acceleration, + right
0103.06
Z_Body_Accel
Vertical acceleration, +
down
0103.07
Roll_Rate
Integer 2
0.0001 rad/s
- x <
0103.08
Pitch_Rate
Integer 2
0.0001 rad/s
- x <
0103.09
Yaw_Rate
Integer 2
0.0001 rad/s
- x <
Table B1 - 68: Message #3010: Body-Relative Sensed States

4.4.12 Message #3011: AV Stick Status.
The AV Stick Status Message is used to report the AV flight surface and taxi related
functions. The AV Stick Status Message shall not be transmitted between a CUCS
and the AV without an authorized connection. This message shall be used to report
the AV Stick status to the CUCS the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3011.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
3011.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3011.02
Lateral Stick
Integer 1
None
-127 x
Integer 1
None
-127 x
Integer 1
None
-127 x
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions

127 is full right
3011.03
Longitudinal Stick
-127 is full back, 0 is centre,
127 is full front
3011.04
Rotational Stick (Rudder)

-127 is full counter
clockwise, 0 is centre, 127
is full clockwise
3011.05

3011.06

neutral 127 is full
3011.07

1 - B - 112
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3011.08
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 1
None
No Restrictions
Integer 1
None
-127 x

neutral 127 is full
3011.09

3011.10
10

neutral 127 is full
3011.11
11

3011.12
12

neutral 127 is full
3011.13
13
Taxi Stick
127 is full right
Table B1 - 69: Message #3011: AV Stick Status

4.4.13 Message #3012: Area Status Alert Message.
The Area Status Alert shall be used to indicate to the CUCS that an error or
warning condition has occurred related to Area operations.

Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3012.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
3012.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3012.02
Area ID
Unsigned 1
None
1x
3012.03
Area Alert Status
Unsigned 1
Enumerated
0 = Area Transmission
Successful
1 = Loiter Point Adjusted
2 = Area Loop Missing
3 = Area Unusable
4 = Area Unreachable
5 = Catastrophic Error
6 = Verify Upload
Loiter Point Adjusted conditional begins ("Area Alert Status" == 1)

3012.04
Adjusted Loiter Latitude
Integer 4
BAM
-/2 x /2
3012.05
Adjusted Loiter
Longitude
Integer 4
BAM
No Restrictions
Loiter Point Adjusted conditional ends
1 - B - 113
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
Area Loop Missing conditional begins ("Area Alert Status" == 2)

3012.06
Polygon Loop Index #1
Unsigned 1
None
1x
3012.07
Loop Segment #1
Unsigned 1
None
1x
Loops repetition begins (where n = 1 to 31)

3012.08
Polygon Loop Index

#<n+1>
Unsigned 1
None
No Restrictions
3012.09
Loop Segment #<n+1>
Unsigned 1
None
No Restrictions
Loops repetition ends

Area Loop Missing conditional ends
Area Unreachable conditional begins ("Area Alert Status" == 4)
3012.10
70
Current AV Latitude
Integer 4
BAM
-/2 x /2
3012.11
71
Current AV Longitude
Integer 4
BAM
No Restrictions
None
No Restrictions
Area Unreachable conditional ends

Verify Upload conditional begins ("Area Alert Status" == 6)
3012.12
72
Upload checksum
Unsigned 4
Verify Upload conditional ends
Table B1 - 70: Message #3012: Area Status Alert Message
Field four of Message #3012 Area Status Alert is stated as being a Return Status
Data. This defines 0 to 64 bytes of description data relevant to Alert Status given in
field three. The length, form and format of this data are dependent on what the Alert
Status is, and varies accordingly.
4.4.14 Message #3013: Area Transmission Status.
Area Transmission Status Message is sent from the AV to the CUCS to indicate that
an area definition is about to be transmitted. This message is sent in response to an
Area Transmission Command Message with an Area Upload Mode of Initiate
Download.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3013.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
3013.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3013.02
AV Cruise Altitude
Integer 3
0.02 m
-1,000 x 100,000
3013.03
Area Min Altitude
Integer 3
0.02 m
-1,000 x 100,000
3013.04
Area Max Altitude
Integer 3
0.02 m
-1,000 x 100,000
1 - B - 114
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3013.05
Area Safety Offset
Unsigned 2
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
1x
Distance from edge of

defined Stay In polygon
before a manoeuvre is
required to avoid crossing
the edge of the polygon.
3013.07
Area ID
Unique ID for area
0 = Download all areas
3013.08
Area Loop Count

Number of polygon loops
defined for this Area
Table B1 - 71: Message #3013: Area Transmission Status

4.4.15 Message #3014: Emergency Mode Report.
This message shall be used to report the selected emergency mode to the CUCS from the
VSM/AV. The VSM/AV shall send this message to the CUCS to acknowledge that an
Emergency Mode Command has been received from the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3014.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
3014.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3014.02
Contingency A Response
State
Unsigned 1
Enumerated
0 = Bypass
1 = Waypoint
2 = Glide
3 = Take-off Climb
4 - 9 = Reserved
3014.03
Contingency A Response
Delay
Unsigned 2
No Restrictions
3014.08

Time A
Unsigned 2
No Restrictions
3014.04
Contingency A Waypoint
Number
Unsigned 2
None
No Restrictions
3014.05
Contingency B Response
State
Unsigned 1
Enumerated
0 = Bypass
1 = Waypoint
2 = Glide
3 = Take-off Climb
4 - 9 = Reserved
3014.06
Contingency B Response
Delay
Unsigned 2
No Restrictions
3014.09

Time B
Unsigned 2
No Restrictions
1 - B - 115
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
3014.07
Data Element Name &

Description
Contingency B Waypoint
Number
Type
Units
Range
Unsigned 2
None
No Restrictions
Table B1 - 72: Message #3014: Emergency Mode Report

4.4.16 Message #3015: Energy Storage Unit State.
This message is sent from the Vehicle/VSM to the CUCS to define the current energy
level in the storage unit. This command shall not be sent if only one energy storage
unit is present; Message # 3002 shall be used. If multiple energy storage units are
present and the total of the level does not equal the value(s) specified in Message #
3002, then the energy value(s) in Message # 3002 will be ignored.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
3015.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
3015.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
3015.02
Energy Storage Unit ID
Unsigned 1
None
No Restrictions
Unsigned 2
0.0016 %
No Restrictions
Identifies particular energy

storage unit (e.g. fuel tank,
battery bank) on the
vehicle.
3015.03
Current Energy Storage

Unit Level
Reported as a percentage
of the maximum capacity.
<0: Not Applicable
Table B1 - 73: Message #3015: Energy Storage Unit State

4.5 Flight Vehicle Payload Relevant Messages.
4.5.1 Message #4000: Inertial States.
This message shall be used to send the current air vehicle inertial state to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
4000.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0101.04
Latitude
Integer 4
BAM
-/2 x /2
0101.05
Longitude
Integer 4
BAM
No Restrictions
0101.06
Altitude
Integer 3
0.02 m
-1,000 x 100,000
Distance above (+) or

below (-)
1 - B - 116
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0101.07
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84 (geoid)
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.005 m/s
-100 x 100
Integer 2
0.005 m/s
-100 x 100
Integer 2
0.005 m/s
-100 x 100
Integer 2
BAM
No Restrictions
Integer 2
BAM
-/2 x /2
Integer 2
BAM
No Restrictions

message.
0101.08
U_Speed
Speed component along
true north vector
0101.09
V_Speed
true east vector
0101.10
W_Speed
Inertial vertical speed
component pointing down
0101.11
U_Accel
Acceleration component
0101.12
10
V_Accel
Acceleration component
along the true east vector
0101.13
11
W_Accel
Inertial vertical acceleration
component pointing down
0101.14
12
Roll
Rotation of the vehicle
about the longitudinal axis
relative to the local
horizontal plane, + is
clockwise looking from the
rear of the UAV towards the
front.
0101.15
13
Pitch
Angle of the vehicles
longitudinal axis (tail to
nose) relative to the local
horizontal, + is up.
0101.16
14
Heading
Projection of the
longitudinal axis onto the
horizontal plane, and that
projection's bearing relative
to true North
1 - B - 117
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0101.17
15
Roll Rate
Integer 2
0.005 rad/s
No Restrictions
Integer 2
0.005 rad/s
No Restrictions
Integer 2
0.005 rad/s
No Restrictions
Integer 2
BAM
No Restrictions
Angular rotation rate (Euler

convention)of the vehicle
about the longitudinal axis,
+ is clockwise looking from
the rear of the UAV towards
the front.
0101.18
16
Pitch Rate
Angular rotation rate (Euler
convention)of the vehicles
longitudinal axis (tail to
nose) relative to the local
horizontal, + is up
0101.19
17
Turn Rate
Angular rate change of the
projection of the
longitudinal axis onto the
horizontal plane, and that
projection's bearing relative
to true North.
0101.20
18
Magnetic Variation
True = Magnetic + Variation
Table B1 - 74: Message #4000: Inertial States

4.5.2 Message #4001: From-To-Next Waypoint States.
This message shall be used to report the vehicle From-To-Next Waypoints for the
Flight modes supported by the air vehicle that requires this function. The From, To, or
Next Waypoint may not be valid dependent on the current Flight mode (Message
#2001, Vehicle Operating Mode Command), therefore, zero values shall be
transmitted in the waypoint number field to define invalid waypoints. Fields 11
through 16 (To waypoint) shall be used to define the non-loiter/loiter destination (the
position toward which the vehicle is flying) when in the "Loiter" and "Waypoint" flight
modes. It is highly encouraged that the "To waypoint" be reported for all other Flight
modes where the air vehicle is attempting to achieve a non-loiter/loiter position.
Fields 6 through 10 (From waypoint) shall be used to define the point the air vehicle
is departing from when in the "Waypoint" Flight mode (Message #2001, Vehicle
Operating Mode Command). Fields 17 through 22 (Next waypoint) shall be used to
define the non-loiter/loiter point to which the vehicle will proceed after achieving the
"To Waypoint" when in the "Waypoint" Flight mode (Message #2001, Vehicle
Operating Mode Command). The From-To-Next Waypoints provide a monitoring
station with the capability to view a portion of the AV route. It is highly encouraged
that the "From waypoint" and Next waypoint" be reported for all other Flight modes
where applicable. The "Waypoint Numbers" used by the VSM in this message shall
not correspond to any Mission Waypoint numbers (Message #13002) loaded to the
VSM/AV by a CUCS, except to report those Mission Waypoints.
1 - B - 118
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
The Loiter Configuration Report Validity field shall be set to valid in this message to
indicate that the Message #3004, Loiter Configuration Report, is reporting the Loiter
to be performed at the To Waypoint location. The VSM/ AV shall push Message
#3004, Loiter Configuration Report, to the CUCS as required by the Flight mode to
correctly report the loiter configuration. Such an instance would be while the AV is
reporting the Fly-By-Sensor mode of operation and is updating its own loiter position
and pattern based on internal AV algorithms.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
4001.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0110.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0110.04
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84
Unsigned 1
Enumerated
1 = True Airspeed
2 = Ground Speed

message.
0110.05
Speed Type
Defines speed type
message.
0110.06
From Waypoint Latitude
Integer 4
BAM
-/2 x /2
0110.07
From Waypoint
Longitude
Integer 4
BAM
No Restrictions
0110.08
From Waypoint Altitude
Integer 3
0.02 m
-1,000 x 100,000
0110.09
From Waypoint Time
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 2
None
x < 65,535
The Time at which the AV

reached the waypoint.
0110.10
From Waypoint Number

0 indicates that the From
Waypoint is not valid.
0110.11
To Waypoint Latitude
Integer 4
BAM
-/2 x /2
0110.12
10
To Waypoint Longitude
Integer 4
BAM
No Restrictions
0110.13
11
To Waypoint Altitude
Integer 3
0.02 m
-1,000 x 100,000
0110.14
12
To Waypoint Speed
Unsigned 2
0.5 m/s
x 10,000
0110.15
13
To Waypoint Time
Unsigned 5
0.001 s
See Section 1.7.2

will reach the waypoint. Not
a countdown.
1 - B - 119
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0110.16
14
To Waypoint Number
Unsigned 2
None
No Restrictions
0 indicates that the

remaining To Waypoint
data is not valid. 65535
indicates that the remaining
To Waypoint data is valid,
but there is no valid
waypoint number.
0110.17
15
Next Waypoint Latitude
Integer 4
BAM
-/2 x /2
0110.18
16
Next Waypoint
Longitude
Integer 4
BAM
No Restrictions
0110.19
17
Next Waypoint Altitude
Integer 3
0.02 m
-1,000 x 100,000
0110.20
18
Next Waypoint Speed
Unsigned 2
0.5 None
x 10,000
0110.21
19
Next Waypoint Time
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 2
None
x < 65,535
Unsigned 1
Enumerated
0 = Not Valid
1 = Valid

will reach the waypoint. Not
a countdown.
0110.22
20
Next Waypoint Number

0 indicates that the Next
Waypoint is not valid
4001.01
21
Loiter Configuration
Report Validity for To
Waypoint
Message #3004, Loiter
Configuration Report, is
valid for the To Waypoint
Table B1 - 75: Message #4001: From-To-Next Waypoint States

4.6 IFF Command Messages.
4.6.1 Message #5000: IFF Code Command.
This message shall be used to set the IFF codes and is sent by the CUCS. Octal
values shall be packed in the least significant bits of the field (e.g., Octal 1234 would
be stored as 0x029C, or 668 decimal).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
5000.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
1500.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1500.04
Mode 1 Code
Integer 1
None
No Restrictions
Unsigned 1
Enumerated
0 = Off
1 = On
First digit 0..7

2nd digit 0..3
1500.05
Mode 1 Enable
1 - B - 120
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1500.06
Mode 2 Code
Integer 2
None
No Restrictions
Octal digits, xxxx,

transmitted as decimal
(where each x is
constrained by a value of 0
x 7)
1500.07
Mode 2 Enable
Unsigned 1
Enumerated
0 = Off
1 = On
1500.08
Mode 3/A Code
Integer 2
None
No Restrictions
Octal 0000 to 7777

1500.09
Mode 3/A Enable
Unsigned 1
Enumerated
0 = Off
1 = On
1500.10
Mode C Enable
Unsigned 1
Enumerated
0 = Off
1 = On
1500.11
Mode 4 Enable
Unsigned 1
Enumerated
0 = Off
1 = On
1500.12
10
Mode 4 A/B
Unsigned 1
Enumerated
0=A
1=B
1500.13
11
Mode 4 Hold
Unsigned 1
Enumerated
0 = Normal
1 = Hold
1500.14
12
Mode 4 Zeroize
Unsigned 1
Enumerated
0 = Normal
1 = Zeroize
5000.01
13
Mode S Address
Integer 3
None
No Restrictions
Octal 00000000 to
77777777
5000.02
14
Mode S Enable
Unsigned 1
Enumerated
0 = Off
1 = On
5000.03
15
Mode S Aircraft ID
Character 9
None
No Restrictions
While the Mode S does

support 8 characters, many
countries only allow seven
characters.
Eight (8) character
sequence. Each character
is coded using the
International Alphabet
Number (IA-5 code) but
limited to Upper case
letters, space and digits 0-9
1 - B - 121
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
5000.04
16
Data Element Name &

Description
Mode S Maximum True
Airspeed
Type
Units
Range
Unsigned 1
Enumerated
0 = No Airspeed Available
1 = 0 to 75
2 = >75 to 150
3 = >150 to 300
4 = >300 to 600
5 = >600 to 1200
6 = >1200
7 = Not Assigned
Knots
1500.15
17
Mode
Unsigned 1
Enumerated
0 = Off
1 = Standby
2 = Normal
3 = Emergency
5000.05
18
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 76: Message #5000: IFF Code Command

4.6.2 Message #5001: IFF Ident (Squawk) Command.
This message shall be used to manually transmit the vehicles Ident.

Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
5001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1501.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1501.04
Mode 3/A Ident
Unsigned 1
Enumerated
0 = Normal
1 = Ident
5001.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 77: Message #5001: IFF Ident (Squawk) Command

4.7 IFF Status Messages.
4.7.1 Message #6000: IFF Status Report.
This message shall be used to report the IFF status to the CUCS. Octal values shall
be packed in the least significant bits of the field (e.g., Octal 1234 would be stored as
0x029C, or 668 decimal).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
6000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1600.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 122
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1600.04
Mode 1 Code
Integer 1
None
No Restrictions
First Digit 0..7

2nd Digit 0..3
1600.05
Mode 1 Enabled
Unsigned 1
Enumerated
0 = Off
1 = On
1600.18
Mode 2 Code
Integer 2
None
No Restrictions
Octal 0000 to 7777

1600.06
Mode 2 Enabled
Unsigned 1
Enumerated
0 = Off
1 = On
1600.07
Mode 3/A Code
Integer 2
None
No Restrictions
Octal 0000 to 7777

1600.08
Mode 3/A Enabled
Unsigned 1
Enumerated
0 = Off
1 = On
1600.09
Mode C Enabled
Unsigned 1
Enumerated
0 = Off
1 = On
1600.10
Mode 4 Enable
Unsigned 1
Enumerated
0 = Off
1 = On
1600.11
10
Mode 4 A/B
Unsigned 1
Enumerated
0=A
1=B
1600.12
11
Mode 4 Hold
Unsigned 1
Enumerated
0 = Normal
1 = Hold
6000.01
12
Mode S Address
Integer 3
None
No Restrictions
Octal 00000000 to
77777777
6000.02
13
Mode S Enable
Unsigned 1
Enumerated
0 = Off
1 = On
6000.03
14
Mode S Aircraft ID
Character 9
None
No Restrictions
Unsigned 1
Enumerated
0 = No Airspeed Available
1 = 0 to 75
2 = >75 to 150
3 = >150 to 300
4 = >300 to 600
5 = >600 to 1200
6 = >1200
7 = Not Assigned
Eight (8) character

sequence. Each character
is coded using the
International Alphabet
Number (IA-5 code) but
limited to Upper case
letters, space and digits 0-9
6000.04
15
Mode S Maximum True

Airspeed
Knots
1 - B - 123
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1600.13
16
Mode
Unsigned 1
Enumerated
0 = Off
1 = Standby
2 = Normal
3 = Emergency
Table B1 - 78: Message #6000: IFF Status Report

4.8 ATC Interface Command Messages.
4.8.1 Messages #7000: Civilian Air Traffic Control (ATC) Radio Command.
This message shall be used to command the AV radios for data that should be sent
or received from civil aviation authorities if the UAV has to pass through civil
airspace. It is sent from the CUCS to the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
7000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
7000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
7000.02
Set Communication
Radio State
Unsigned 1
Enumerated
0 = Off
1 = On
7000.03
Set Communication
Frequency
Unsigned 2
8.333333 kHz
118,000 x 136,975
7000.04
Voice Transmit Enable
Unsigned 1
Enumerated
0 = Disabled
1 = Enabled
Unsigned 1
None
No Restrictions
Unsigned 3
None
No Restrictions
Enables voice transmission

to ATC
7000.05
Radio Unit
Selects which radio unit is
addressed by this
message.
7000.06
Activity ID
Table B1 - 79: Message #7000: Civilian Air Traffic Control (ATC) Radio
Command
4.8.2 Message #7001: NAVAID Radio Command.
This message shall be used to command the NAVAID radios and is sent from the
CUCS to the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
7001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
7001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
7001.02
Set NAVAID Radio State
Unsigned 1
Enumerated
0 = Off
1 = On
1 - B - 124
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
7001.03
Set NAVAID Frequency
Unsigned 2
50 kHz
108,000 x 117,950
7001.04
VOR Radial
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
0 = In
1 = Out
Unsigned 1
Enumerated
0 = Disabled
1 = Enabled
Unsigned 1
None
No Restrictions
Unsigned 3
None
No Restrictions
Requested Radial that AV

should fly
7001.05
Radial To/From
Defines if AV is flying in to
the VOR or away from the
VOR
7001.06
Voice Transmit Enable

from ATC over NAVAID
Radio
7001.07
Radio Unit
addressed by this
message.
7001.08
Activity ID
Table B1 - 80: Message #7001: NAVAID Radio Command

4.9 ATC Interface Status Messages.
4.9.1 Messages #9000: Civilian Air Traffic Control (ATC) Radio Status.
This message shall be used to report the ATC radios status to the CUCS from the
AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
9000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
9000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
9000.02
Communication Radio
State
Unsigned 1
Enumerated
0 = Off
1 = On
9000.03
Communication
Frequency
Unsigned 2
8.333333 kHz
118,000 x 136,975
9000.04
Voice Transmit Enabled
Unsigned 1
Enumerated
0 = Disabled
1 = Enabled
Unsigned 1
None
No Restrictions

to ATC
9000.05
Radio Unit
addressed by this
message.
1 - B - 125
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 81: Message #9000: Civilian Air Traffic Control (ATC) Radio Status
4.9.2 Message #9001: NAVAID Radio Status.
This message shall be used to report the NAVAID radios status to the CUCS
from the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
9001.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
9001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
9001.02
VOR NAVAID State
Unsigned 1
Enumerated
0 = Off
1 = On
9001.03
NAVAID Frequency
Unsigned 2
50 kHz
108,000 x 117,950
9001.04
VOR Azimuth
Integer 2
BAM
No Restrictions
9001.05
DME
Integer 3
0 x 364,000
9001.06
LOC/Glide Slope Valid
Unsigned 1
Bitmapped
0x01 = LOC Valid

0x02 = Glideslope Valid
9001.07
LOC
Integer 1
None
No Restrictions
Integer 1
None
No Restrictions
Left (-128), Right (127)

9001.08
Glide Slope
Down (-128), Up (127)
9001.09
Marker
Unsigned 1
Bitmapped
0x01 = Outer
0x02 = Middle
0x04 = Inner
9001.10
10
Voice Transmit Enabled
Unsigned 1
Enumerated
0 = Disabled
1 = Enabled
Unsigned 1
None
No Restrictions

from ATC over NAVAID
Radio
9001.11
11
Radio Unit
addressed by this
message.
Table B1 - 82: Message #9001: NAVAID Radio Status

4.10 Vehicle Auxiliary Command Messages.
4.10.1 Message #11000: Vehicle Auxiliary Command.
This message shall be used by the CUCS to control the air vehicles landing gear,
flaps, and speed brakes.
4.24 and 4.25, General Configuration Messages for additional details.
1 - B - 126
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
11000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
11000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
11000.02
Landing Gear Command
Unsigned 1
Enumerated
0 = Up
1 = Down
2 - 9 = Reserved
11000.03
Flap Deployment
Command
Integer 1
0.02 rad
-/2 x /2
Integer 1
0.02 rad
-/2 x /2
Unsigned 3
None
No Restrictions
Command to set flap

position
11000.04
Speed Brake Deployment

Command
Command to set speed
break position
11000.05
Activity ID
Table B1 - 83: Message #11000: Vehicle Auxiliary Command

4.10.2 Message #11001: Fuel, Oil and Hydraulic Commands.
This message shall be used by the CUCS to control the vehicles fuel, oil, and
hydraulic subsystems, when control or transfer valves exist to do so. This message
will be sent for each tank or type of fluid selected.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
11001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
11001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
11001.02
Source Tank ID
Integer 4
None
No Restrictions
11001.03
Tank Type
Unsigned 1
Enumerated
0 = None
1 = Fuel
4 = Coolant
5 = Hydraulic
Identifies type of tank or

fluid
1 - B - 127
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
11001.04
Valve Type
Unsigned 1
Enumerated
0 = None
1 = Shut-Off
2 = Transfer
3 = Jettison
11001.05
Valve Activation
Unsigned 1
Enumerated
0 = Closed
1 = Open
11001.06
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 84: Message #11001: Fuel, Oil & Hydraulic Command

4.10.3 Message #11101: Battery Bank Select.
This message shall be used by the CUCS to control battery bank selection for both
power use and charging.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
11101.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
11101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
11101.02
Bank Select
Unsigned 1
Bitmapped
0x01 = Bank 1
0x02 = Bank 2
0x04 = Bank 3
0x08 = Bank 4
0x10 = Bank 5
11101.03
Connection
Unsigned 1
Enumerated
0 = Not Connected
1 = Connected
Unsigned 3
None
No Restrictions
Defines if the bank(s) are

connected to the power bus
11101.04
Activity ID
Table B1 - 85: Message #11101: Battery Bank Select

4.11 Vehicle Auxiliary Status Messages.
4.11.1 Message #12000: Vehicle Auxiliary Status.
This message shall be used by the VSM to report the state of the air vehicles landing
gear, flaps, and speed brakes.
1 - B - 128
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
12000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0104.15
Landing Gear State
Unsigned 1
Enumerated
0 = Up
1 = Down & Locked
2 = Down & Not Locked
3 = No Value (added for
Edition 2)
4 = Inoperative (added for
Edition 2)
5 - 9 = Reserved
This reflects the state of the

gears defined in the Gear
Location field.
12000.03
Gear Location
Unsigned 1
Enumerated
0 = All
1 = Nose
2 = Port
3 = Starboard
4 = Aft
5 - 8 = Reserved
0104.13
Flap Deployment Angle
Integer 1
0.02 rad
-/2 x /2
Integer 1
0.02 rad
-/2 x /2
Command to set flap

position
0104.14
Speed Brake Deployment

Angle
Command to set speed
break position
Table B1 - 86: Message #12000: Vehicle Auxiliary Status

4.11.2 Message #12001: Electrical Report.
This message shall be used to display the bus voltage and bus current of the UAV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
12001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
12001.02
Bus ID
Unsigned 1
Enumerated
12001.03
Bus Voltage
Unsigned 1
0.5 V
x 127
12001.04
Bus Current
Unsigned 2
0.1 A
x 1,000
Table B1 - 87: Message #12001: Electrical Report

4.11.3 Message #12002: Meteorological Data.
This message shall be used to send ground measured meteorological data from the
CUCS to the VSM/AV.
1 - B - 129
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12002.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
12002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
12002.02
Wind U_Speed instantaneous
Integer 2
0.005 m/s
-100 x 100
12002.03
Wind V_Speed instantaneous
Integer 2
0.005 m/s
-100 x 100
12002.04
Wind U_Speed Averaged
Integer 2
0.005 m/s
-100 x 100
12002.05
Wind V_Speed - Averaged
Integer 2
0.005 m/s
-100 x 100
12002.06
Latitude
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Integer 3
0.02 m
-1,000 x 100,000
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84 (geoid)
Location of the weather

report
12002.07
Longitude
report
12002.08
Altitude
report
12002.09
Altitude Type
message.
12002.10
10
Outside Air Temp
Unsigned 2
0.5 K
172.15 x 327.65
12002.11
11
Barometric Pressure
Unsigned 2
10 Pa
x 107,500
12002.12
12
Weather Station Sensor

Status
Unsigned 1
Bitmapped
0x01 = Baro Pressure

invalid
0x02 = Air Temp invalid
0x04 = Inst U_Speed
Invalid
0x08 = Inst V_Speed
invalid
0x10 = Avg U_Speed invali
0x20 = Avg V_Speed
invalid
Table B1 - 88: Message #12002: Meteorological Data

4.11.4 Message #12003: Fuel, Oil and Hydraulic Status.
This message shall be used by the VSM to report the state of the vehicles fuel, oil,
and hydraulic subsystems. This message will be sent for each tank or type of fluid
selected.
1 - B - 130
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
12003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
12003.02
Source Tank ID
Integer 4
None
No Restrictions
12003.03
Tank Type Selected
Unsigned 1
Enumerated
0 = None
1 = Fuel
4 = Coolant
5 = Hydraulic
Identifies type of tank or

fluid
12003.04
Valve Type Selected
Unsigned 1
Enumerated
0 = None
1 = Shut-Off
2 = Transfer
3 = Jettison
12003.05
Valve Activation Status
Unsigned 1
Enumerated
0 = Closed
1 = Open
2 = Moving to Close
3 = Moving to Open
12003.06
Remaining Tank Quantity
Unsigned 2
0.1 L
x < 4,000
Amount of remaining fluid in

selected tank. NOTE:
Remaining fuel (as energy
source) is reported under
Message #3015.
12003.07
Tank Pressure
Unsigned 2
10 Pa
x 107,500
12003.08
Fluid Density
Unsigned 1
0.005 kg/L
No Restrictions
Table B1 - 89: Message #12003: Fuel, Oil & Hydraulic Status

4.11.5 Message #12101: Battery Report.
This message shall be used to display the battery voltage, charge state, current and
temperature.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12101.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
12101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
12101.02
Bank Selected
Unsigned 1
Bitmapped
0x01 = Bank 1
0x02 = Bank 2
0x04 = Bank 3
0x08 = Bank 4
0x10 = Bank 5
1 - B - 131
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
12101.03
Connection Status
Unsigned 1
Enumerated
0 = Not Connected
1 = Connected
Reports if the bank(s) are

connected to the power bus
12101.04
Bus Voltage
Unsigned 2
0.1 V
x 500
12101.07
Battery Current
Integer 2
0.1 A
-1,000 x 1,000
A negative value indicate

current flow out of the
battery
12101.05
Battery Charge
Remaining
Unsigned 2
0.1 %
x 100
12101.06
Battery Temperature
Unsigned 2
0.5 K
172.15 x 327.65
Table B1 - 90: Message #12101: Battery Report

4.12 Mission Command and Status Messages.
The messages in this section support transfer of a mission plan between the air
vehicle and the CUCS. Mission messages can be sent to/from the air vehicle before
and during flight.
4.12.1 Message #13000: Mission Transfer Command.
The Mission Transfer Command shall be used to control the overall mission transfer
and storage of a mission and to request autonomous activity status. The mission
shall be transmitted between a CUCS and VSM as a series of individual waypoints
based on Message #13002, AV Position Waypoint Message, for which there may be
a number of optional associated messages. The optional associated messages
include Message #13003, AV Loiter Waypoint, Message #13004, Payload Action
Waypoint, Message #13005, Airframe Action Waypoint, and Message #13006,
Vehicle Specific Waypoint. A Message #13000, Mission Plan Mode Transmit
Mission command to the AV/VSM shall identify that all mission waypoints have all
been transmitted from the CUCS to the VSM, and the VSM shall transform the
mission as required and load it to the air vehicle.
Field 3 value 6, "Download All Activity Status" shall be used to transmit an Activity
Status Message, Message #36200 for each activity that the VSM or vehicle will
execute, describing the scheduling status of that activity.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0800.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0800.04
Mission ID
Character 20
None
No Restrictions
Text Identifier of Mission
1 - B - 132
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0800.05
Mission Plan Mode
Unsigned 1
Enumerated
0 = Clear Route
1 = Clear Mission
2 = Transmit Mission
3 = Receive Mission
4 = Receive Single
Waypoint
5 = Cancel
Transmit/Receive
6 = Receive All Activity
Status
0800.06
Waypoint Number
Unsigned 2
None
1 x < 65,535
13000.01
Route ID
Character 33
None
No Restrictions
Unsigned 3
None
No Restrictions
Text Identifier of Route

13000.02
Activity ID
Table B1 - 91: Message #13000: Mission Transfer Command

4.12.2 Message #13001: AV Route.
This message shall be used to define a Route Type for an AV route defined by a
series of Message #13002, AV Position Waypoint, messages. If the Initial waypoint
number field in this message is set to 0, the route definition, but not the waypoints,
shall be deleted. Where routes have been uploaded to an air vehicle without a
defined Route Type, the default Route Type shall be 2= Flight.
This message shall be transmitted from the VSM/ AV in response to a Message
#13000, Receive Mission request to report the AV route types loaded onboard.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0801.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0801.04
Initial Waypoint Number
Unsigned 2
None
x < 65,535
Character 33
None
No Restrictions
Unsigned 1
Enumerated
0 = Launch
1 = Approach
2 = Flight
3 = Contingency A
4 = Contingency B
First Waypoint in defined

route.
0801.05
Route ID
Text Identifier of Route
0801.06
Route Type
1 - B - 133
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13001.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 92: Message #13001: AV Route

4.12.3 Message #13002: AV Position Waypoint.
This message shall be used by the CUCS to define a single Route, or series of
Routes, to be uploaded to the VSM/ AV. Waypoint numbers forming a route do not
need to be contiguous, but the use of contiguous integers is recommended within a
route. This message shall be used to define the location the AV will fly to. When the
Location Type is relative, the Relative Y and Relative X shall maintain the units of
radians.
#13000, Download Mission request to report the AV Position Waypoints loaded
onboard.
Note on Loop Action:
A Loop Action can be defined by using the Waypoint Type field to direct to a different
set of WPs that defines a loop connected to a Waypoint in a route. The Loop Action
defines a waypoint, which is the first (and end) loop waypoint. When encountering a
Loop Action the UAV checks the loop limit condition: if True the UAV starts the loop
path, if False it continues to fly on the main flight path. While in loop, flying towards
initial point the UAV again calculates if it can perform the next loop without meeting
the limit terms (Limit terms definitions are number of turns or minimum fuel quantity
or time pass). The calculation is based on present velocity and fuel flow. If next loop
can be performed without meeting limit terms the UAV will turn towards the next loop
point. Otherwise the UAV will continue to the next WP after the loop start/end point
(WP N+1 in the following figure).
1 - B - 134
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
WPL +1
WPL+2
Loop Action
Defines WPN/Lo
N is main path waypoint
L0 is first/last loop waypoint
WPL+3
WPN+1
ath WPN/Lo
p
in
Loop Start/End Point
Ma
WPL+M
Figure B1 - 11: Loop Action
Note on Auto Altitude Change Actions:

The altitude change can be performed either manually by commanding the UAV rate
of climb/decent, or automatically by commanding the UAV Altitude Change
Behaviour:
- In case of flight path altitude restriction: The altitude change is immediate in
spiral path (See the figure below for critical altitude action) or
- Change altitude gradually towards next navigation point, or
- Change altitude rapidly in Max Rate of Climb or Max Rate of Descend along
the track to the next waypoint, or
- When attitude in the track is not critical, change altitude according to the
UAV optimum performance
Figure B1 - 12: Auto Altitude Change Actions
1 - B - 135
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
An AV will change its airspeed, subject to Message #2003, as it flies to the waypoint.
The rate of airspeed change is not defined by this message and is air vehicle
specific.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13002.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0802.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0802.04
Waypoint Number
Unsigned 2
None
1 x < 65,535
0802.05
Waypoint to Latitude or
Relative Y
Integer 4
BAM
-/2 x /2
0802.06
Waypoint to Longitude or
Relative X
Integer 4
BAM
No Restrictions
0802.07
Location Type
Unsigned 1
Enumerated
0 = Absolute
1 = Relative (See Message
#2006)
0802.08
Waypoint to Altitude
Integer 3
0.02 m
-1,000 x 100,000
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

report
0802.09
Waypoint Altitude Type

Defines altitude type for all
altitude related fields in the
messages for this waypoint.
0802.20
Altitude Change
Behaviour
Unsigned 1
Enumerated
0 = Manual
2 = Gradual
3 = Max (ROC/ROD)
4 = UAV Dependent
5 = Not Defined
0802.10
Waypoint to Speed
Unsigned 2
0.5 m/s
x 10,000
0802.11
10
Waypoint Speed Type
Unsigned 1
Enumerated
1 = True Airspeed
2 = Groundspeed
3 = Arrival Time
0802.12
11
Next Waypoint
Unsigned 2
None
x < 65,535
Unsigned 1
Enumerated
0 = Short Turn
1 = Flyover
Next waypoint to fly to

when this waypoint is
reached. If value = 0 and
Activity = 0, this is the last
waypoint in the series. If
value = 0 and Activity ID
0, then the VSM is to fill in
the next waypoint value to
determine the order to fly
the waypoints.
0802.16
12
Turn Type
1 - B - 136
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
13002.01
13
Data Element Name &

Description
Optional Messages for
Waypoint
Type
Units
Range
Unsigned 1
Bitmapped
0x01 = Msg #13003

0x02 = Msg #13004
0x04 = Msg #13005
0x08 = Msg #13006
0x00 = None
0802.17
14
Waypoint Type
Unsigned 1
Enumerated
0 = Regular/In Loop WP
1 = First/End Loop WP
0802.18
15
Limit Type
Unsigned 1
Enumerated
0 = Time Pass
1 = Minimum Fuel
2 = Number of Laps
3 = Bingo Energy (See
0104.21)
0802.19
16
Loop Limit
Unsigned 2
s/Fuel
(%)/None
(Number)
No Restrictions
Time/Fuel/Number of Laps
0802.15
17
Arrival Time
Unsigned 5
0.001 s
See Section 1.7.2
13002.02
18
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 93: Message #13002: AV Position Waypoint

4.12.4 Message #13003: AV Loiter Waypoint.
This message shall be used to define the loiter characteristics the AV will perform
once it has arrived at the Waypoint Number.
If the loiter length is specified in time, the time is for the inbound leg of the loiter
pattern. The inbound leg is, by convention, the first tangent leg the AV flies. The
time and the Loiter Speed (13003.03 and 13003.04) determine the distance travelled
on the inbound leg. The AV must adjust the outbound leg time to be able to travel
that same distance on the outbound leg while maintaining speed.
Loiter patterns can be repeated using the Loiter Duration field. Repetition can be
specified as the number of laps or the total time to execute the pattern using the
Loiter Duration Units field.
Loiter entry and exit behaviour is AV-dependent, including what to do when Loiter
Duration is specified in time and there is insufficient time to complete another lap.
The ATC Hold pattern (0041.04 = 5) is intended to be used to support a standard
hold pattern for air traffic control. It has the same shape as the Racetrack pattern,
but the primary difference is that pattern is not centred at the loiter point. Rather, the
inbound leg terminates at the loiter point, also known as the holding fix. Thus, the
Loiter Bearing and Loiter Direction have a significant impact to the footprint of the
ATC Hold pattern relative to the loiter point. The ATC Hold pattern is available when
the AV can properly execute the pattern described. Alternatively, the CUCS may
transform the parameters provided by ATC into a Racetrack pattern (0041.04 = 2) to
send to the AV.
1 - B - 137
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
This message shall be transmitted from the VSM / AV in response to a Message
#13000, Download Mission request to report the loiter characteristics waypoints
loaded onboard.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13003.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0803.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0803.04
Waypoint Number
Unsigned 2
None
1 x < 65,535
0803.06
Waypoint Loiter Type
Unsigned 1
Enumerated
1 = Circular
2 = Racetrack
3 = Figure 8
4 = Hover
5 = ATC Hold
6 - 9 = Reserved
0803.07
Loiter Radius
Unsigned 2
1.5 m
1.5 x
Unsigned 2
1.5 m or s
1.5 x
Unsigned 1
Enumerated
0 = Distance (m)
1 = Time (s)
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
1 = Clockwise
3 = Into the Wind
Unsigned 2
0.5 m/s
x 10,000

Figure 8 patterns.
0803.08
Loiter Length
Bearing.
13003.02
Loiter Length Units

apply to Racetrack
patterns.
0803.09
Loiter Bearing
Message #13002), from
True North.
0803.10
Loiter Direction
Defines direction of turn
when rounding the loiter
point defined by the AV
Position Waypoint Message
(Message # 13002).
13003.03
Loiter Speed
1 - B - 138
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13003.04
10
Speed Type
Unsigned 1
Enumerated
1 = True Airspeed
2 = Ground Speed
3 = Not Specified
Unsigned 1
Enumerated
0 = Flyby
1 = Flyover
2 = Not Specified
Unsigned 2
Lap or s
1x
Defines speed type

message.
Edition 2.
13003.01
11
Flying Behaviour
Edition 2.
13003.05
12
Loiter Duration
loiter
13003.06
13
Unsigned 1
Enumerated
0 = Lap
1=s
13003.07
14
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 94: Message #13003: AV Loiter Waypoint
1 - B - 139
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Figure B1 - 13: Loiter Pattern
1 - B - 140
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.12.5 Message #13004: Payload Action Waypoint.
This message shall be used by the CUCS to define the Payload action that will be
performed when the AV begins to fly to the waypoint defined by the Waypoint
Number.
#13000, Download Mission request to report the Payload Action Waypoints loaded
onboard.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13004.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0804.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0804.04
Waypoint Number
Unsigned 2
None
1 x < 65,535
0804.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
13004.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
1 - B - 141
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13004.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Component Location
0804.06
Set Sensor 1 Mode
Unsigned 1
Enumerated
0 = Turn Off
1 = Turn On
2 = Go to Standby
3 = No Change
4 - 10 = Reserved
11 - 255 = Vehicle/Payload
Specific
0804.07
Set Sensor 2 Mode
Unsigned 1
Enumerated
0 = Turn Off
1 = Turn On
2 = Go to Standby
3 = No Change
4 - 10 = Reserved
Specific
0804.08
Sensor Output
Unsigned 1
Enumerated
0 = None
1 = Sensor 1
2 = Sensor 2
3 = Both Sensors
4 = No Change
5 - 10 = Reserved
Specific
1 - B - 142
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0804.09
Set Sensor Pointing Mode
Unsigned 1
Enumerated
0 = Nil
1 = Angle Relative to AV
2 = Slewing Rate Relative
to AV
to Inertial
4 = Lat-Long Slaved
5 = Target Slaved
6 = Stow
7 = Line Search Start
Location
8 = Line Search End
Location
9 = Cage
10 - 31 = Reserved
32 - 255 = Payload Specific
0804.10
10
Starepoint Latitude
Integer 4
BAM
-/2 x /2
0804.11
11
Starepoint Longitude
Integer 4
BAM
No Restrictions
0804.12
12
Starepoint Altitude
Integer 3
0.02 m
-1,000 x 100,000
0804.13
13
Starepoint Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84 (geoid)
Defines altitude type for

previous field
0804.14
14
Payload Az (wrt AV)
Integer 2
BAM
No Restrictions
0804.15
15
Payload El (wrt AV)
Integer 2
BAM
-/2 x /2
0804.16
16
Payload Sensor Rotation

Angle
Integer 2
BAM
-/2 x /2
13004.05
17
Sensor Mode
Unsigned 1
Enumerated
0 = EO
1 = IR
2 = Fuse
3 = Continuous Zoom
4 = Not Specified
Unsigned 1
Enumerated
0 = BW Mode
1 = Colour Mode
2 = Not Specified
Unsigned 1
Enumerated
0 = Black Hot
1 = White Hot
2 = Not Specified

Edition 2.
13004.06
18
EO Sensor Mode
Edition 2.
13004.07
19
IR Polarity
Edition 2.
13004.08
20
Horizontal Field of View
Unsigned 2
BAM
No Restrictions
13004.09
21
Vertical Field of View
Unsigned 2
BAM
No Restrictions
13004.04
22
Activity ID
Unsigned 3
None
No Restrictions

1 - B - 143
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13004.03
23
Station Number 17-32
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 95: Message #13004: Payload Action Waypoint

4.12.6 Message #13005: Airframe Action Waypoint.
This message shall be used by the CUCS to define the Airframe action that will be
performed when the AV begins to fly to the waypoint defined by the Waypoint
Number.
#13000, Download Mission request to report the Airframe Action Waypoints loaded
onboard.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13005.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0805.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0805.04
Waypoint Number
Unsigned 2
None
1 x < 65,535
0805.05
Function
Unsigned 1
Enumerated
1 = Navigation Lights
2 = Strobe Lights
3 = Primary Data Link
4 = Secondary Data Link
5 = Navigation IR Lights
6 = Strobe IR Lights
7 = NVD Compatible
8 = Landing
9 = Landing IR
10 = Reserved
0805.06
Enumerated State
Unsigned 1
Enumerated
0 = Turn Off
1 = Turn On
2 = Go to Standby
3 = Receive Only
4 = Transmit Only
1 - B - 144
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13005.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 96: Message #13005: Airframe Action Waypoint

4.12.7 Message #13006: Vehicle Specific Waypoint.
This message shall be used to define the vehicle specific action that will be
performed when the AV begins to fly to the waypoint. This message shall be used to
pass Common Route Definition (CRD) messages that cannot be mapped to the
generic waypoints defined in this section. A waypoint value of zero indicates mission
generic data that is not associated with any specific waypoint.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13006.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0806.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0806.04
Waypoint Number
Unsigned 2
None
x < 65,535
0806.05
Tag Type
Unsigned 1
Enumerated
0 = None
1 = Start Tag
2 = Stop Tag
0806.06
Tag/Data
Character 20
None
No Restrictions
13006.01
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 97: Message #13006: Vehicle Specific Waypoint

4.12.8 Message #13007: Define Contingency.
This message shall be used by the CUCS to define a contingency waypoint for a
single Waypoint, Route, Mission, or Area. Waypoint contingencies shall take priority
over Route contingencies which shall have priority over Mission contingencies which
shall have priority over Area contingencies. This message shall be transmitted from
the CUCS to the VSM/AV along with a mission transfer.
Messages #2011 and #2012 shall be used to define the Area referenced by this
message when defining a contingency for an Area, This message shall be
transmitted from the VSM/AV in response to a Message #13000, Download Mission
request to report the Vehicle Waypoint Contingencies loaded onboard.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13007.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
13007.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 145
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13007.02
Contingency Scope
Unsigned 1
Enumerated
0 = Waypoint
1 = Route
2 = Mission
3 = Area
This allows a contingency

to be assigned on a
Mission, Route, or
Waypoint basis.
Route / Mission Scope conditional begins (("Contingency Scope" != 0) & ("Contingency Scope" != 3))
13007.03
Unsigned 2
Not Used
None
No Restrictions
None
1 x < 65,534
Unsigned 2
None
1 x 255
Character 33
None
No Restrictions
Unsigned 2
None
1 x < 65,534
This field is only valid if the

scope is Waypoint or
Area
Route / Mission Scope conditional ends
Waypoint Scope conditional begins ("Contingency Scope" == 0)
13007.10
Unsigned 2
Waypoint Number
The ID of the waypoint this
contingency applies to
when scope is Waypoint.
Waypoint Scope conditional ends

Area Scope conditional begins ("Contingency Scope" == 3)
13007.11
Area ID
The ID of the area this
contingency applies to
when scope is Area.
Area Scope conditional ends

13007.04
Route/Mission ID
The id of route or mission
(as specified by scope) that
this contingency applies to.
This field is only valid if the
scope is Route or
Mission
Text identifier of Mission or

Route (respectively) as
selected by Scope. NOTE:
if scope is Mission, the
effective length of this field
is 20.
13007.05
Contingency Waypoint
Number
The waypoint to go to if the
contingency conditions are
met.
1 - B - 146
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
13007.06
Condition Modifier
Unsigned 1
Enumerated
0 = Disjunctive Logic (OR)

1 = Conjunctive Logic
(AND)
Unsigned 1
None
x < 255
Specifies how multiple

conditions are to be
handled. If disjunctive, the
contingency is met if any or
all of the conditions are met
(logical OR operation). If
conjunctive, the
contingency is only met if
all of the contingencies are
met (logical AND
operation).
13007.07
Number of Conditions
The number of conditions
that will comprise this
contingency.
0 Clear Contingency
Conditions repetition begins (where n = 1 to "Number of Conditions")

13007.08
Contingency Condition
<n-1>
Unsigned 1
Enumerated
0 = Loss of Comms
1 = Loss of Critical Avionics
2 = Engine Out
3 = Missed Approach
4 - 20 = Reserved
Unsigned 3
None
No Restrictions
Defines the nth condition

for this contingency.
Conditions repetition ends
13007.09
264
Activity ID
Table B1 - 98: Message #13007: Define Contingency

4.12.9 Message #14000: Mission Upload / Download Status.
This message shall be used to provide status on a mission upload / download from a
VSM to a CUCS, and to request a missing Waypoint from a CUCS mission upload. If
there are no waypoints to transfer when a transfer is requested, the CUCS/VSM shall
send this message with a status of complete and percent complete of 100.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
14000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0900.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 147
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
14000.01
Mission ID
Character 20
None
No Restrictions
Identifies mission and (by

reference) flight plan
uploading or downloading
on this platform.
Text Identifier of Mission.
0900.04
Status
Unsigned 1
Enumerated
0 = In progress
1 = Complete
2 = Aborted / Rejected
0900.05
Percent Complete
Unsigned 1
x 100
14000.02
Waypoint Request
Unsigned 2
None
x < 65,535
0 = N/A
Table B1 - 99: Message #14000: Mission Upload / Download Status

4.13 Subsystems Status Messages.
The common message set includes summary health and status information for use
by CUCS status displays. This information need not convey detailed, configurationspecific health and status information, but should provide the CUCS with overall
health summary data suitable for annunciation on the console using conventional
colour codes (Green=Nominal, Yellow=Caution, Red= Warning, Black=Failed or Outof-service). In the event of a system caution or warning, vehicle, payload or data link
specific status messages can provide detailed diagnostic information peculiar to the
configuration.
These messages shall provide health and status overview information only in an
interoperable context. Detailed status information about particular subsystems shall
be a vehicle-specific message type.
4.13.1 Message #15000: Subsystem Status Request.
This message shall be used by the CUCS to request Subsystem information from the
AV, VSM or Data Link.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
15000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1000.05
Data Link ID
Integer 4
None
See Section 1.7.6
1 - B - 148
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1000.04
Subsystem ID
Unsigned 4
Bitmapped
0x00000001 = Engine
0x00000002 = Mechanical
0x00000004 = Electrical
0x00000008 = Comms
0x00000010 = Propulsion
Energy
0x00000020 = Navigation
0x00000040 = Payload
0x00000080 = Recovery
System
0x00000100 =
Environmental Control
System
0x00000200 = VSM Status
0x00000400 = VDT
0x00000800 = CDT
0x00001000 = Reserved 1
0x00002000 = Reserved 2
0x00004000 = Reserved 3
0x00008000 = Reserved 4
0x00010000 = Reserved 5
0x00020000 = Reserved 6
0x00040000 = Reserved 7
0x00080000 = Reserved 8
0x00100000 = VSM
Specific 1
0x00200000 = VSM
Specific 2
0x00400000 = VSM
Specific 3
0x00800000 = VSM
Specific 4
0x01000000 = VSM
Specific 5
0x02000000 = VSM
Specific 6
0x04000000 = VSM
Specific 7
0x08000000 = VSM
Specific 8
0x10000000 = VSM
Specific 9
0x20000000 = VSM
Specific 10
0x40000000 = VSM
Specific 11
0x80000000 = VSM
Specific 12
Unsigned 3
None
No Restrictions
Identifier associated with

the subsystem for which
status information is being
requested as applicable.
15000.01
Activity ID
Table B1 - 100: Message #15000: Subsystem Status Request
1 - B - 149
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.13.2 Message #15001: Subsystem Status Detail Request.
This message shall be used by the CUCS to request more information from the AV,
VSM or Data Link about a specific subsystem. The AV, VSM or Data Link shall
respond using a vehicle specific service specified in Section 1.7.5.1.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
15001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1001.04
Subsystem State Report

Reference
Integer 4
None
0x
The Report Reference is

the Vehicle or Data Link
Specific information
reference previously
provided by the AV, VSM or
Data Link.
Table B1 - 101: Message #15001: Subsystem Status Detail Request

4.13.3 Message #16000: Subsystem Status Alert Message.
This message shall be used by the AV, VSM, or Data Link to create a Subsystem
Status Alert. Examples are:
Engine #3 Failure
Engine #3 Cylinder Head Temp > 280C, currently 295 C
The Subsystem State Report Reference shall be assigned by the AV, VSM or Data
Link. The purpose of this field is to provide a reference number for subsequent
requests for more information on a posted alert by the CUCS. If the CUCS requires
additional information for a specific alert posted by the AV, VSM or the Data Link, the
CUCS shall request this information using Message #15001. Alert messages of
Type 1 (Not Clearable or Acknowledgeable by operator) can be cleared by the AV,
VSM or Data Link sending the alert with a priority of 0 = Clear or Type of 0 =
Clear.
Alert groups, other than AV platform and payload are not required to be displayed to
the user in real time and may be saved to a file for later review.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
16000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1100.11
Data Link ID
Integer 4
None
See Section 1.7.6
1100.04
Priority
Unsigned 1
Enumerated
0 = Cleared
1 = Nominal
2 = Caution
3 = Warning
4 = Emergency
5 = Failed
1 - B - 150
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
1100.05
Data Element Name &

Description
Reference
Type
Units
Range
Integer 4
None
-1 x
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
4 = Propulsion Energy
5 = Navigation
6 = Payload
7 = Recovery System
8 = Environmental Control
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 19 = Reserved
Identifier associated with a

particular report associated
with the specified
subsystem. Used to request
particular status information
from the VSM.
-1 = No More Info Available
1100.06
Subsystem ID
reported.
16000.01
Alert Group
Unsigned 1
Bitmapped
0x01 = AV Platform
0x02 = Payload
0x04 = Maintenance
0x08 = Engineering
0x10 = User Defined 1
16000.02
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 151
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
16000.03
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Enumerated
0 = Clear
1 = Not Clearable or
Acknowledgeable By
Operator
2 = Clearable By Operator
3 = Display For Fixed Time
Then Automatically Clear
4 = Acknowledgeable By
Operator
5 = Acknowledgeable and
clearable
Station Location
16000.04
Component Location
1100.07
10
Type
1 - B - 152
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1100.08
11
Warning ID
Integer 4
None
No Restrictions
The Warning ID is used to

update warning messages
that have been previously
sent to the CUCS from the
VSM.
Note: Warning ID is a
unique value generated by
the VSM for use when
additional message
#16000s are sent about the
same alert
1100.09
12
Text
Character 80
None
No Restrictions
1100.10
13
Persistence
Integer 1
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
This field determines the

minimum time an alert will
be displayed. This time is
referenced to when this
message is received by the
CUCS.
<0 = Not Defined
0 = Clear Immediately
>0 = Display for at least this
many seconds
16000.05
14

Table B1 - 102: Message #16000: Subsystem Status Alert

4.13.4 Message #16001: Subsystem Status Report.
This message shall be used by the AV, VSM or Data Link to produce a Subsystem
Status Report.
1 - B - 153
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
16001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1101.04
Subsystem ID
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
5 = Navigation
6 = Payload
7 = Recovery System
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 19 = Reserved

reported as applicable. IDs
above 20 are used for
vehicle and payload
specific subsystems.
1101.05
Subsystem State
Unsigned 1
Enumerated
0 = No Status
1 = Nominal
2 = Caution
3 = Warning
4 = Emergency
5 = Failed
1101.06

Reference
Integer 4
None
-1 x
The Report Reference is

the Vehicle Specific
information reference,
provided by the AV, VSM or
Data Link, which the CUCS
can use to request
additional information from
the AV, VSM or Data Link
on the reported alert.
-1 = No More Info
Available
16001.01
Report Text Type
Unsigned 1
Enumerated
0 = Use Report Reference

1 = http URL Address
2 = PDF URL Address
16001.02
Report Text Reference
Character
256
None
No Restrictions
Contains the URL

associated with the
Subsystem detailed status.
Null if Unused.
Table B1 - 103: Message #16001: Subsystem Status Report
1 - B - 154
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.13.5 Message #16002: Heartbeat Message.
This message shall be used to allow either the CUCS or the VSM to monitor whether
the other component is operational.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
16002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
16002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
Table B1 - 104: Message #16002: Heartbeat Message

4.14 Miscellaneous Message Types.
4.14.1 Message #17000: Message Acknowledgement.
This message shall be used to acknowledge standard message types that require
acknowledgement per the Message Acknowledge bit.
Vehicle specific (private)
message types may also elect to use this message if desired.
The Message Acknowledgement Message shall only be used to acknowledge
configuration messages, as requested by the Message Acknowledge Configuration
Message, in advance of an authorized connection.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
17000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1400.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1400.06
Original Message Time

Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1400.08
Original Message Type
Unsigned 2
None
No Restrictions
17000.01
Acknowledgement Type
Unsigned 1
Enumerated
0 = Message Received (no

additional Message #17000
for this request)
1 = Message Received, but
not completed (may receive
another #17000 of Ack
Type 2 or 3)
2 = Message Received and
Completed
3 = Message Received, but
Rejected
An Ack Type of 2 or 3 may

be sent after an Ack Type 1
or can be sent without a
preceding Ack Type 1.
Table B1 - 105: Message #17000: Message Acknowledgement

4.14.2 Message #17001: Schedule Message Update Command.
This message shall be used to request that the specified message be sent at a given
frequency. The effect of this message is to make the requested message a push
type message, but without requesting each pull individually.
The Schedule Message Update Command message shall not be transmitted from a
CUCS to a VSM, and vice versa, without an authorized connection. The Scheduled
Message Update Command is valid until another Message #17001 is received for
1 - B - 155
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
that message type or until a Message #2 VSM Authorisation Response Message
Connection Not Authorized has been transmitted from the VSM, air vehicle or data
link to terminate the connection or the connection has been lost.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
17001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1402.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1402.04
Requested Message Type
Unsigned 2
None
No Restrictions
1402.05
Frequency
Unsigned 2
0.01 Hz
x 100
Unsigned 3
None
No Restrictions
0 = Cancel Automatic Send

of Requested Message
17001.01
Activity ID
Table B1 - 106: Message #17001: Schedule Message Update Command

4.14.3 Message #17002: Generic Information Request Message.
This message shall be used to request the VSM, air vehicle, Data Link or CUCS to
send the specified message. The Presence Vector field allows the requesting unit to
determine the minimum number of fields that shall be returned. This message shall
not be used to request Message #41000, Message #41001, Message #41002, and
Message #44003, as this is specifically achieved with Message #40000.
The Generic Information Request Message shall not be transmitted from a CUCS to
a VSM, and vice versa, without an authorized connection, with the exception of
requesting specific (non-generic) configuration messages such as Message #3,
Message #3000, Message #21001 and Message #21100.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
17002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1403.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 156
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1403.06
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
None
No Restrictions
17002.01
Component Number
Station Location
17002.02
Component Location
1403.07
Message Type
Type number of the
message being requested
1 - B - 157
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
17002.04
Data Element Name &

Description
Requested Field
Presence Vector
Type
Units
Range
Unsigned 5
Bitmapped
0x0000000001 = PV Bit 00
0x0000000002 = PV Bit 01
0x0000000004 = PV Bit 02
0x0000000008 = PV Bit 03
0x0000000010 = PV Bit 04
0x0000000020 = PV Bit 05
0x0000000040 = PV Bit 06
0x0000000080 = PV Bit 07
0x0000000100 = PV Bit 08
0x0000000200 = PV Bit 09
0x0000000400 = PV Bit 10
0x0000000800 = PV Bit 11
0x0000001000 = PV Bit 12
0x0000002000 = PV Bit 13
0x0000004000 = PV Bit 14
0x0000008000 = PV Bit 15
0x0000010000 = PV Bit 16
0x0000020000 = PV Bit 17
0x0000040000 = PV Bit 18
0x0000080000 = PV Bit 19
0x0000100000 = PV Bit 20
0x0000200000 = PV Bit 21
0x0000400000 = PV Bit 22
0x0000800000 = PV Bit 23
0x0001000000 = PV Bit 24
0x0002000000 = PV Bit 25
0x0004000000 = PV Bit 26
0x0008000000 = PV Bit 27
0x0010000000 = PV Bit 28
0x0020000000 = PV Bit 29
0x0040000000 = PV Bit 30
0x0080000000 = PV Bit 31
0x0100000000 = PV Bit 32
0x0200000000 = PV Bit 33
0x0400000000 = PV Bit 34
0x0800000000 = PV Bit 35
0x1000000000 = PV Bit 36
0x2000000000 = PV Bit 37
0x4000000000 = PV Bit 38
0x8000000000 = PV Bit 39
Unsigned 3
None
No Restrictions
Fields within the message

that are requested.
17002.05
Activity ID
1 - B - 158
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
17002.03
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 107: Message #17002: Generic Information Request Message

4.14.4 Message #17003: File Transfer Notification.
This message shall be used to report an FTP file transfer between the CUCS and the
VSM/AV. The message can be sent in either direction. The file will be available in
the FTP directory previously identified by the CUCS/VSM by Message #42001,
CUCS Resource Report or Message #43000 VSM Services Report Message.
The File Transfer Notification message shall not be transmitted from a CUCS to a
VSM, and vice versa, without an authorized connection.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
17003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
17003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
17003.02
File Type
Unsigned 1
Enumerated
0 = Payload Data
1 - 10 = Reserved
17003.03
File Name
Character 32
None
No Restrictions
Name of binary file being

transferred
Table B1 - 108: Message #17003: File Transfer Notification

4.14.5 Message #18000: Link Audio Command.
This message shall be used by the CUCS to assert the Push To Talk (PTT) function
within the UAS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
18000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 159
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18000.02
PTT
Unsigned 1
Bitmapped
0x01 = Out 0
0x02 = Out 1
0x04 = Out 2
0x08 = Out 3
0x10 = Out 4
0x20 = Out 5
0x40 = Out 6
0x80 = Out 7
Unsigned 3
None
No Restrictions
This field will cause a

change of the state of the
PTT discrete output.
Suggest that at least one
discrete, controlled by Bit 0,
be used, and reserved for
the primary Push To Talk
signal.
For each bit:
0 = Not Active
1 = Active
18000.03
Activity ID
Table B1 - 109: Message #18000: Link Audio Command

4.14.6 Message #18001: Emitters All Off Command.
This message shall provide the ability for the CUCS to command, in a single
message, that all emitters on the vehicle shall extinguish transmission. The
vehicle/VSM shall preserve a list of vehicle emitters that were transmitting, and their
state, in order to reset the state of the vehicle transmitters (if required). This message
shall provide the ability for the CUCS to command, in a single message, that the
transmission state of all transmitters be restored to the state they were in before the
reception of the All Emitters Off command. The vehicle/VSM may send an Emitter
Status Message to indicate that all emitters are off prior to turning off the data link
transmitter.
The vehicle/VSM shall only act upon this message from the CUCS with the highest
LOI. If more than one CUCS has the same highest LOI, the first one to connect at
that LOI will be the only one whose command is acted upon by the vehicle/VSM.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
18001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18001.02
All Emitters Off
Unsigned 1
Enumerated
1 = All Emitters Off

2 = Restore Emitter Tx
state
1 - B - 160
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18001.03
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 110: Message #18001: Emitters All Off Command

4.14.7 Message #18100: Link Audio Status.
This message is sent from the VSM to the CUCS, and shall report the status of the
Push To Talk (PTT).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18100.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
18100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18100.02
PTT
Unsigned 1
Bitmapped
0x01 = Out 0
0x02 = Out 1
0x04 = Out 2
0x08 = Out 3
0x10 = Out 4
0x20 = Out 5
0x40 = Out 6
0x80 = Out 7
For each bit:

0 = Not Active
1 = Active
Table B1 - 111: Message #18100: Link Audio Status

4.14.8 Message #18101: Emitters Status.
This message shall provide the ability for the vehicle/ VSM to report, in a single
message, that all emitters (on the vehicle) will be extinguished after this command is
transmitted.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18101.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
18101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18101.02
All Emitters Off
Unsigned 1
Enumerated
0 = Not All Emitters Off

1 = All Emitters Off
2 = Emissions restored
Table B1 - 112: Message #18101: Emitters Status
1 - B - 161
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.14.9 Message #18200: Meteorological Table Message.
This message shall be used by the CUCS to send meteorological data to the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18200.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
18200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18200.02
Publish Time
Unsigned 5
0.001 s
See Section 1.7.2
18200.03
Forecast Time
Unsigned 5
0.001 s
See Section 1.7.2
18200.04
Latitude
Integer 4
BAM
-/2 x /2
18200.05
Longitude
Integer 4
BAM
No Restrictions
18200.06
Number of levels
Unsigned 1
None
x 50
Repeat Count
Levels repetition begins (where n = 1 to "Number of levels")
18200.07
Altitude <n>
Integer 3
0.02 m
-1,000 x 100,000
18200.08
U_Speed <n>
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000

True North vector. Positive
value indicates wind is
moving to the North.
18200.09
V_Speed <n>
True East vector. Positive
moving to the East.
18200.10
Temperature <n>
Unsigned 2
0.5 K
173 x 373
18200.11
Humidity <n>
Unsigned 1
x 100
Levels repetition ends
Table B1 - 113: Message #18200: Meterological Table Message

4.14.10 Message #18300: Meteorological Table Report.
This message shall be used by the AV to report meteorological data to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18300.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
18300.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18300.02
Publish Time
Unsigned 5
0.001 s
See Section 1.7.2
18300.03
Forecast Time
Unsigned 5
0.001 s
See Section 1.7.2
18300.04
Latitude
Integer 4
BAM
-/2 x /2
18300.05
Longitude
Integer 4
BAM
No Restrictions
1 - B - 162
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18300.06
Number of levels
Unsigned 1
None
x 50
Integer 3
0.02 m
-1,000 x 100,000
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Repeat Count
Levels repetition begins (where n = 1 to "Number of levels")
18300.07
Altitude <n>
report
18300.08
U_Speed <n>
True North vector. Positive
moving to the North.
18300.09
V_Speed <n>
True East vector. Positive
moving to the East.
18300.10
Temperature <n>
Unsigned 2
0.5 K
173 x 373
18300.11
Humidity <n>
Unsigned 1
x 100
Levels repetition ends
Table B1 - 114: Message #18300: Meterological Table Report

4.14.11 Message #18400: KLV Security Configuration Data.
This message shall be used by the CUCS to send KLV Security Configuration data to
the UA for use in populating the payload Meta Data.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18400.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
18400.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18400.03
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 163
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18400.04
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
18400.05
Component Location
18400.06
Classifying Country and

Releasing Instructions
Country Coding Method
Unsigned 1
Enumerated
0 = Not Defined
1 = ISO-3166 Two Letter
2 = ISO-3166 Three Letter
3 = FIPS 10-4 Two Letter
4 = FIPS 10-4 Four Letter
5 = ISO-3166 Numeric
6 = 1059 Two Letter
7 = 1059 Three Letter
8 - 9 = Reserved
10 = FIPS 10-4 Mixed
11 = ISO 3166 Mixed
12 = STANAG 1059 Mixed
18400.07
Classifying Country
Character 33
None
No Restrictions
Character 41
None
No Restrictions
See FIPS 10-4, ISO-3166

or STANAG 1059
18400.08
Classified By
See MISB 102.9
1 - B - 164
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
18400.09
18400.10
Data Element Name &

Description
Type
Units
Range
Object Country Coding

Method
Unsigned 1
Enumerated
0 = Not Defined
1 = ISO-3166 Two Letter
2 = ISO-3166 Three Letter
3 = ISO-3166 Numeric
4 = FIPS 10-4 Two Letter
5 = FIPS 10-4 Four Letter
6 = 1059 Two Letter
7 = 1059 Three Letter
Object Country Codes
Character 41
None
No Restrictions
Unsigned 2
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
See MISB 102.9

18400.11
10
Version
Value is version number of
this document; e. g. for
STD 0102.9, this value is
0d07
18400.12
11

Table B1 - 115: Message #18400: KLV Security Configuration Data

4.14.12 Message #18401: KLV Security Classification Data.
This message shall be used by the CUCS to send KLV Security Classification data to
the UA for use in populating the payload Meta Data.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18401.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
18401.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 165
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18401.03
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
18401.04
Component Number
Station Location
18401.05
Component Location
1 - B - 166
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18401.06
Security Classification
Unsigned 1
Enumerated
0 = Not Defined
1 = UNCLASSIFIED
2 = RESTRICTED
3 = CONFIDENTIAL
4 = SECRET
5 = TOP SECRET
18401.07
Security-SCI/SHI
information
Byte 41
None
No Restrictions
Character 33
None
No Restrictions
Character 41
None
No Restrictions
Character 41
None
No Restrictions
Character 41
None
No Restrictions
Character 9
None
No Restrictions
Character 41
None
No Restrictions
Character 11
None
No Restrictions
Character 11
None
No Restrictions
See MISB 102.9

18401.08
Caveats
See MISB 102.9
18401.09
See MISB 102.9
18401.10
Derived From
See MISB 102.9
18401.11
10
Classification Reason
See MISB 102.9
18401.12
11
Declassification Date
See MISB 102.9
18401.13
12
Classification and
Marking System
See MISB 102.9
18401.14
13
Classifying Country and

Country Coding Method
Version Date
See MISB 102.9
18401.15
14
Object Country Coding

Method Version Date
See MISB 102.9
1 - B - 167
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18401.16
15
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 116: Message #18401: KLV Security Classification Data

4.14.13 Message #18402: KLV Security Classification Comment Data.
This message shall be used by the CUCS to send KLV Security classification
comment data to the UA for use in populating the payload Meta Data.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18402.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
18402.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18402.03
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 168
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18402.04
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Character
481
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Station Location
18402.05
Component Location
18402.06
Classification Comments
See MISB 102.9
18402.07

Table B1 - 117: Message #18402: KLV Security Classification Comment Data
1 - B - 169
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.14.14 Message #18403: KLV Security Image Data.
This message shall be used by the CUCS to send KLV Security image data to the
UA for use in populating the payload Meta Data.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18403.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
18403.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
18403.03
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
18403.04
Component Number
Station Location
1 - B - 170
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
18403.05
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Character 33
None
No Restrictions
Character 33
None
No Restrictions
Character 33
None
No Restrictions
Character 33
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 2
None
No Restrictions
Byte 16
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Component Location
18403.06
UMID Video
See SMPTE 330M
18403.07
UMID Audio
See SMPTE 330M
18403.08
UMID Data
See SMPTE 330M
18403.09
UMID System
See SMPTE 330M
18403.10
Stream ID
See ISO/IEC 13818-1
18403.11
10
Transport Stream ID
See ISO/IEC 13818-1
18403.12
11
Item Designator ID
See SMPTE 336M
18403.13
12

1 - B - 171
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 118: Message #18403: KLV Security Image Data
4.15 Payload Command Messages.
Since UAVs are commonly used as carriers for payload systems, the messages in
this group are specified to provide a means for the UCS to command the operating
state in an interoperable fashion. Vehicles not carrying such payloads need not
support the messages in the group.
4.15.1 Message #19000: Payload Bay Command.
This message shall be used to control each payload bay. Note: Message #21001
defines the Station to Payload Bay door configuration.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0206.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0206.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19000.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
1 - B - 172
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19000.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Component Location
0206.05
Payload Bay Doors
Unsigned 1
Enumerated
0 = Close
1 = Open
19000.04
Activity ID
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

19000.03
Table B1 - 119: Message #19000: Payload Bay Command
1 - B - 173
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.15.2 Message #19001: Payload Steering Command.
This message shall be used to steer any steerable payload located at the Station
Number specified in the message. Table B1-21, Conditional Payload Message
Groups, identifies the common payload types that are required to use the Payload
Steering Command.
The VSM shall use the General Configuration Messages to define the payloads
capability (specified by Station Number) to support the fields commanded in this
message dependent on the current payload steering mode (Message #19100, Set
EO/IR Pointing Mode and Message #19200, SAR Mode) for the Payload type. Refer
to Sections 4.24 and 4.25, General Configuration Messages for additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19001.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0200.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19001.02
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
1 - B - 174
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19001.03
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
0 = Use Set Horizontal &

Vertical Field of View
1 = Stop Zoom
2 = Zoom In
3 = Zoom Out
4 = Fast Zoom In
5 = Fast Zoom Out
6 - 10 = Reserved
Unsigned 2
0.00005
x1
Unsigned 2
0.00005
x1
Unsigned 2
BAM
No Restrictions
Unsigned 2
BAM
No Restrictions
Component Location
0200.05
Set Centreline Azimuth

Angle
+ right of aircraft x axis
0200.06
Set Centreline Elevation

Angle
+ above aircraft waterline
0200.17
Set Zoom
Allows control of the
payload zoom by either
requesting a specific angle
or by requested the payload
to zoom in or out until
commanded to stop.
19001.04
Pixel X
Horizontal position in the
video frame (The right edge
is 1)
19001.05
Pixel Y
Vertical position in the
video frame (The bottom
edge is 1)
0200.07
10
Set Horizontal Field Of

View
Applies to the Addressed
Sensor specified in
Message #19100
0200.08
11
Set Vertical Field Of View

Sensor specified in
Message #19100
1 - B - 175
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0200.09
12
Horizontal Slew Rate
Integer 2
0.0002 rad/s
-2 x 2
Integer 2
0.0002 rad/s
-2 x 2
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Integer 3
0.02 m
-1,000 x 100,000
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84
Unsigned 1
Enumerated
0 = Off/Break
1 = Acquire
2 = Track
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
+ Slew FOV right

0200.10
13
Vertical Slew Rate

+ Slew FOV up
0200.11
14
Latitude
Commanded Stare point
latitude: latitude of centre of
FOV
0200.12
15
Longitude
Commanded Stare point
longitude:
longitude of centre of FOV
0200.13
16
Altitude
Altitude of centre of FOV
0200.14
17
Altitude Type
message.
19001.01
18
Tracker Mode Command

This field is valid when the
Set EO/IR Pointing Mode
is Target Slaved (Track).
19001.08
19
Activity ID
19001.06
20
1 - B - 176
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0200.15
21
Set Focus
Unsigned 1
Enumerated
0 = No Change
1 = Focus Closer
2 = Focus Farther
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
Field added to support

edition 2.
0200.16
22
Focus Type
edition 2.
Table B1 - 120: Message #19001: Payload Steering Command

4.15.3 Message #19100: EO/IR/Laser Payload Command.
This message shall be used to command EO/IR/Laser payloads with the exception of
payload pointing commands, manual focus commands and FOV (Zoom) commands
which are commanded from the Payload Steering Command Message (Message
#19001).
Notes:
Slaved modes are assumed to lock on the centre of FOV at the time the
command is received by the payload (VSM).
Target slaving implies that the FOV will track the target.
Lat-Long slaving implies that the FOV will track a specific location on the
ground.
The VSM shall use the General Configuration Messages to define the payloads
message. Refer to Sections 4.24 and 4.25, General Configuration Messages for
additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19100.00
Presence Vector
Unsigned 4
Bitmapped
No Restrictions
0201.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 177
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0201.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19100.02
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location.
0x0000 = None Selected
0x0000 added for
Edition 2.
19100.03
Component Location.
0x0000 = None Selected
0x0000 added for
Edition 2.
1 - B - 178
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0201.05
Addressed Sensor
Unsigned 2
Bitmapped
0x0001 = EO
0x0002 = IR
0x0004 = Reserved 1
0x0008 = Reserved 2
0x0010 = Reserved 3
0x0020 = Reserved 4
0x0040 = Reserved 5
0x0080 = Reserved 6
0x0100 = Payload
Specific 1
0x0200 = Payload
Specific 2
0x0400 = Payload
Specific 3
0x0800 = Payload
Specific 4
0x1000 = Payload
Specific 5
0x2000 = Payload
Specific 6
0x4000 = Payload
Specific 7
0x8000 = Payload
Specific 8
Unsigned 1
Enumerated
0 = BW Mode
1 = Colour Mode
2 = Not Specified
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
2 = Not Specified
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
2 = Not Specified
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
2 = Not Specified
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
2 = Not Specified
Identifies which sensor (s)

to control where applicable.
Laser pointers and
rangefinders integrated with
an EO/IR sensor are not
considered a separate
sensor.
0x0000 = Not Specified
0x0000 added for
Edition 2.
0201.07
Set EO Sensor Mode

Edition 2.
0200.16
Focus Type
Edition 2.
19100.07
Set EO Iris Adjustment

mode
Edition 2.
19100.08
Set IR Gain Adjustment

mode
Edition 2.
19100.14
10
Set IR Level Adjustment

mode
Edition 2.
1 - B - 179
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0201.08
11
Set IR Polarity
Unsigned 1
Enumerated
0 = Black Hot
1 = White Hot
2 = Not Specified

Edition 2.
19100.09
12
Select IR Temperature
Unsigned 1
Enumerated
19100.04
13
Set NUC Table
Unsigned 1
Enumerated
0201.09
14
Image Output
Unsigned 2
Bitmapped
0x0001 = EO
0x0002 = IR
0x0004 = Reserved 1
0x0008 = Reserved 2
0x0010 = Reserved 3
0x0020 = Reserved 4
0x0040 = Reserved 5
0x0080 = Reserved 6
0x0100 = Payload
Specific 1
0x0200 = Payload
Specific 2
0x0400 = Payload
Specific 3
0x0800 = Payload
Specific 4
0x1000 = Payload
Specific 5
0x2000 = Payload
Specific 6
0x4000 = Payload
Specific 7
0x8000 = Payload
Specific 8

0x0000 added for
Edition 2.
0201.10
15
Unsigned 1
Enumerated
0 = No Value
to AV
to Inertial
4 = Lat-Long Slaved
5 = Target Slaved (track)
6 = Stow
7 = Cage
8 - 31 = Reserved
19100.10
16
Enable Image
Stabilization
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified

Edition 2.
1 - B - 180
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0201.16
17
Fire Laser Pointer
Unsigned 1
Enumerated
0 = Turn Off (0000 0000

(Safe))
51 = Turn On, Do Not Fire
(0001 0001 (Arm))
238 = Fire Laser (1110
1110 (Fire))
0201.11
18
Fire Laser /Rangefinder
Unsigned 1
Enumerated
0 = Turn Off (0000 0000

(Safe))
51 = Turn On, Do Not Fire
(0001 0001 (Arm))
85 = Fire One Laser Pulse
(0101 0101 (Fire))
238 = Fire Multiple Pulses
(1110 1110 (Fire))
0201.12
19
Select Laser Rangefinder

First/Last Pulse
Unsigned 1
Enumerated
1 = First
2 = Last
3 = Not Specified
Unsigned 2
None
No Restrictions

Edition 2.
0201.13
20
Set Laser Designator

Code
Laser Illuminator Code per
STANAG 5516 (Ed 2) (Link
16) Page E-3-527 DFI
#1676 DUI 001
0201.14
21
Initiate Laser Designator
Unsigned 1
Enumerated
0 = Turn Off (0000 0000

(Safe))
51 = Turn On (0001 0001
(Arm))
68 = Deactivate Laser
(0100 0100 (Disable))
85 = Activate Laser (0101
0101 (Fire))
102 = Payload Specific 1
(0110 0110)
(1000 1000)
(1001 1001)
(1100 1100)
19100.13
22
Laser Mode
Unsigned 1
Enumerated
0 = Operational Check
1 = Mission
2 = Boresight
3 = Not Specified
4 - 7 = Reserved

Edition 2.
1 - B - 181
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19100.11
23
Sensor Power
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

Sensor.
Edition 2.
19100.12
24
Activity ID
19100.05
25
Table B1 - 121: Message #19100: EO/IR/Laser Payload Command

4.15.4 Message #19101: EO/IR/Laser Payload Quality Control.
This message shall be used to manually adjust the payload quality.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19101.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
19101.04
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 182
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19101.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19101.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Enumerated
0 = No Change
1 = Focus Closer
2 = Focus Farther
Station Location
19101.02
Component Location
0200.15
Set Focus
1 - B - 183
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19101.06
Adjust EO Iris
Unsigned 1
Enumerated
0 = No Change
1 = Decrease Iris Size
2 = Increase Iris Size
19101.07
Adjust IR Gain
Unsigned 1
Enumerated
0 = No Change
1 = Decrease Gain
2 = Increase Gain
19101.08
Adjust IR Level
Unsigned 1
Enumerated
0 = No Change
1 = Decrease Gain
2 = Increase Gain
19101.03
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 122: Message #19101: EO/IR/Laser Payload Quality Control

4.15.5 Message #19200: SAR Payload Command.
This message shall be used to instruct the VSM to generate all commands for SAR
Payloads, except for pointing and FOV commands that are covered in the Payload
Steering Command Message (Message #19001).
The VSM shall use the General Configuration Messages to define the SAR payloads
message. Refer to Sections 4.24 and 4.25, General Configuration Messages for
additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19200.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0202.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 184
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0202.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19200.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Enumerated
1 = Clutter Map
2 = Moving Target
3 - 9 = Reserved
10 - 255 = Payload-Specific
Station Location
19200.02
Sub-Component
Number
Component Location
0202.06
Set MTI Radar Mode
1 - B - 185
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0202.07
Set SAR Modes
Unsigned 1
Enumerated
0 = 0FR - Mode 0, Slant Plane

1 = 0FG - Mode 0, Ground Plane
7 = 22FG - Mode 5, Ground
Plane
8 = 07A - Mode 3 Area, Slant
Plan
9 = 07L - Mode 3 LOC, Slant
Plan
10 = 14A - Mode 4 area, Slant
Plane
Plane
12 = 1SP - ETP, Spotlight 1,
Slant
13 = 3SP - ETP, Spotlight 3,
Slant
14 = 10S - ETP, Scan, Slant
15 = GSP - Tier 2+ Spot Mode
16 = GSH - Tier 2+ Search Mode
17 = AIP13 - Monopulse
Calibration
18 = AIP14 - Wide Area MTI
(WAMTI)
19 = AIP15 - Coarse Resolution
Search
20 = AIP16 -Medium Resolution
Search
21 = AIP17 - High Resolution
Search
22 = AIP18 - Point Imaging
23 = AIP19 - Swath MTI (SMTI)
24 = AIP20 - Repetitive Point
Imaging
25 = AS201 Search
26 = AS202 - Spot 3
27 = AS204 - Spot 1
28 = AS207 - Continuous Spot 3
30 = AS209 - EMTI Wide Frame
Search
31 = AS210 - EMTI Narrow
Frame Search
32 = AS211 - EMTI Augmented
Spot
33 = AS212 - EMTI Wide Area
MTI (WAMTI)
34 = AS213 Monopulse
Calibration
35 - 100 = Reserved
1 - B - 186
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0202.08
Set Radar Resolution
Unsigned 2
0.01 m
x 100
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
0 = Unknown
19200.04
Activity ID
behaviours and
constraints.
19200.03
Table B1 - 123: Message #19200: SAR Payload Command

4.15.6 Message #19400: Communications Relay Command.
This message shall be used by the CUCS to command the Communications Relay
located at the Station Number specified in the message.
The VSM shall use the General Configuration Messages to define the
Communication Relay (specified by Station Number) capability to support the fields
commanded in this message. Refer to Sections 4.24 and 4.25, General Configuration
Messages for additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19400.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0204.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 187
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0204.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
19400.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location.
19400.02
Component Location.
1 - B - 188
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19400.03
Power
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Standby
3 = Deploy
4 = Activate
5 = Deactivate
6 = Stow
7 = Not Specified
Unsigned 1
Enumerated
1 - 8 = Reserved
9 = Not Specified
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Enumerations 3-7 added for

Edition 2.
19400.04
Set Mode
Enumerations 1-9 added for
Edition 2.
19400.05
RF Power Level Radio A

Defines the transmission
power level of radio A. 0 is
the lowest power level. If
the radio has less than 256
power levels the upper
range should be configured
to only support the number
of available power settings.
19400.06
RF Power Level Radio B

Defines the transmission
power level of radio B. 0 is
19400.07
Select Stored
Configuration Number
Radio A
Selects a predefined
repeater configuration.
19400.08
10
Select Stored
Radio B
Selects a predefined
19400.09
11
Initiate BIT
Unsigned 1
Enumerated
0 = Do not run BIT

19400.10
12
Activity ID
Unsigned 3
None
No Restrictions

1 - B - 189
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19400.11
13
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 124: Message #19400: Communications Relay Command

4.15.7 Message #19401: Load Communications Relay Configuration
Command.
This message shall be used by the CUCS to load the Communications Relay
configuration values to the located Communication Relay located at the Station
Number specified in the message.
The VSM shall use the General Configuration Messages to define the
Communication Relay (specified by Station Number) capability to support the fields
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19401.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
19401.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
19401.02
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 190
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19401.07
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
19401.08
Component Location
19401.03
Unsigned 1
None
No Restrictions
19401.04
Frequency
Unsigned 3
100 Hz
x 512,000,000.0
19401.05
Hop ID
Unsigned 1
None
No Restrictions
Unsigned 3
None
No Restrictions
0 = No hop
19401.06
Activity ID
1 - B - 191
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19401.09
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 125: Message #19401: Load Communications Relay Configuration

Command
4.15.8 Message #19500: Payload Data Recorder Control Command.
This message shall be used to command the platform payload data storage device
indicated in the "Recording Device Number" field to the state as specified in the
message.
The VSM shall use the General Configuration Messages to define the Payload Data
Recorders (specified by Recording Device Number) capability to support the fields
Note: Message #21501 defines the Payload to recording device configuration.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19500.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0205.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0205.04
Recording Device
Number
Unsigned 1
None
No Restrictions
0205.05
Set Recording Index Type
Unsigned 1
Enumerated
0 = Time
1 = Block Number
2 = Event Mark
3 = Session Number
0205.06
Set Recording Mode
Unsigned 1
Enumerated
0 = Stop
1 = Ready
2 = Recording
3 = Play
4 = Seek
5 - 9 = Reserved
1 - B - 192
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0205.07
Set Recording Rate
Float
Mbit/s
0.001 x 40,000
0205.08
Initial Recording Index
Integer 4
None
0x
0 = No Active Index
0205.09
Set Replay Mode
Unsigned 1
Enumerated
0 = Stop
1 = Ready
2 = Reading
3 - 9 = Reserved
0205.10
Replay Clock Rate
Float
Mbit/s
0.001 x 40,000
0205.11
Seek Replay Index
Integer 4
None
0x
Unsigned 3
None
No Restrictions
0 = No Active Index
19500.01
10
Activity ID
Table B1 - 126: Message #19500: Payload Data Recorder Control Command

4.15.9 Message #19600: Terrain Data Update.
This message shall be used by the CUCS to convey terrain data at a specific
location.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19600.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0207.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0207.04
Latitude of terrain data

point
Integer 4
BAM
-/2 x /2
0207.05
Longitude of terrain data

point
Integer 4
BAM
No Restrictions
0207.06
Elevation of terrain data

point
Integer 3
0.02 m
-1,000 x 100,000

below (-) the WGS-84
reference geoid
1 - B - 193
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19600.01
DTED Level
Unsigned 1
Enumerated
0 = No DTED
1 = Level 0
2 = Level 1
3 = Level 2
4 = Level 3
5 = Level 4
6 = Level 5
19600.02
Magnetic Variation
Integer 2
BAM
No Restrictions
East (+) or West (-)
Table B1 - 127: Message #19600: Terrain Data Update

4.15.10 Message #19700: Payload Operating Mode Command.
This message is used to command the payload to a specific mode and whether it
should be commanded via a preplanned mission or real time.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19700.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
19700.04
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
19700.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 194
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19700.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
19700.02
Component Location
19700.06
Device Number
Unsigned 1
None
No Restrictions
19700.07
Platform Power
Unsigned 1
Enumerated
0 = Off
1 = Standby Power
2 = On
0201.06
System Operating Mode
Unsigned 1
Enumerated
0 = Deploy
1 = Activate
2 = Deactivate
3 = Initialise (for backwards
compatibility to Edition 2)
4 = Calibrate (for
Edition 2)
5 - 9 = Reserved
19700.08
Mission Plan Control

Mode
Unsigned 1
Enumerated
0 = Preplanned Mode
1 = Manual Mode
1 - B - 195
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
19700.09
Activity ID
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

19700.03
10
Table B1 - 128: Message #19700: Payload Operating Mode Command

4.16 Payload Status Messages.
Since UAVs are commonly used as carriers for payload systems, the messages in
this group are specified to provide a means for the UCS to report the operating state
in an interoperable fashion. Vehicles not carrying such payloads need not support
the messages in the group.
4.16.1 Message #21000: Payload Bay Status.
This message shall be used to return the status of a payload bay.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0308.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 196
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0308.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21000.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Enumerated
0 = Closed
1 = Open
Station Location
21000.02
Component Location
0308.05
Payload Bay Door Status
1 - B - 197
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21000.03
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 129: Message #21000: Payload Bay Status

4.16.2 Message #21001: Payload Configuration.
This message shall be used to identify payload configuration by vehicle station and
device number. Configuration data is used by mission planning, dynamic re-planning,
and mission execution monitoring applications to determine flight performance
characteristics, manoeuvring limits, and to ascertain flight safety issues, particularly
during takeoff and landing. In-flight configuration changes may also need to be
tracked by the CUCS in terms of their effect on vehicle performance as the mission
progresses.
This message shall be used to provide the CUCS with payload configuration on initial
start up and on a change basis. The CUCS shall request this message from the AV/
VSM using Message #17002, Generic Information Request Message, during the
configuration process as required for determination of the vehicle payload
configuration. At least one instance of this message shall be sent by the AV/VSM for
each employed device type. Sufficient messages shall be sent to define the
configuration for all devices installed in the payload station, component, subcomponent hierarchy when requested by the CUCS. An instance of the message
shall be sent by the AV/ VSM each time the configuration changes.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21001.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0300.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0300.05
Payload Count
Unsigned 2
None
No Restrictions
Defines the total number of

available station son the
AV. Multiple instances of
this message may be
required to define the
configuration of all available
payloads.
1 - B - 198
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0300.06
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21001.04
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
None
No Restrictions
Station Location
21001.05
Component Location
0300.10
Device Number
1 - B - 199
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0300.07
Payload Class
Unsigned 2
Enumerated
0 = Not Specified/N/A
1 = EO
2 = IR
3 = EO/IR
4 = SAR
5 = Fixed Camera
6 = Comms Relay
8 = Recorder
10 - 999 = Reserved
1000 - 65535 = VSM
Specific
21001.01
Payload Type
Unsigned 2
None
No Restrictions
Unsigned 2
Enumerated
Character 20
None
No Restrictions
Assigned by AV
manufacturer.
21001.02
Payload Subtype
Assigned by AV
manufacturer.
21001.03
10
Payload Name
Vehicle Specific
0300.08
11
Station Door
Unsigned 1
Enumerated
0 = No
1 = Yes
0300.09
12
Number of Devices on
this Station
Unsigned 2
None
No Restrictions
21001.06
13
Focus Distance Change

Rate
Unsigned 2
m/s
No Restrictions
21001.07
14
Horizontal Zoom Change

Rate
Unsigned 2
0.004 rad/s
No Restrictions
21001.08
15
Number of Discrete Fields

of View
Unsigned 1
None
x 29
Discrete Field of View List repetition begins (where n = 1 to "Number of Discrete Fields of View")
21001.09
Horizontal Field of View

#<n>
Integer 2
BAM
No Restrictions
21001.11
Vertical Field Of View

#<n>
Integer 2
BAM
No Restrictions
Discrete Field of View List repetition ends
1 - B - 200
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21001.10
74
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
21001.11
75
Payload Stations
Available
Unsigned 4
Bitmapped
0x00000001 = Stn #1
0x00000002 = Stn #2
0x00000004 = Stn #3
0x00000008 = Stn #4
0x00000010 = Stn #5
0x00000020 = Stn #6
0x00000040 = Stn #7
0x00000080 = Stn #8
0x00000100 = Stn #9
0x00000200 = Stn #10
0x00000400 = Stn #11
0x00000800 = Stn #12
0x00001000 = Stn #13
0x00002000 = Stn #14
0x00004000 = Stn #15
0x00008000 = Stn #16
0x00010000 = Stn #17
0x00020000 = Stn #18
0x00040000 = Stn #19
0x00080000 = Stn #20
0x00100000 = Stn #21
0x00200000 = Stn #22
0x00400000 = Stn #23
0x00800000 = Stn #24
0x01000000 = Stn #25
0x02000000 = Stn #26
0x04000000 = Stn #27
0x08000000 = Stn #28
0x10000000 = Stn #29
0x20000000 = Stn #30
0x40000000 = Stn #31
0x80000000 = Stn #32
Added for backwards

Table B1 - 130: Message #21001: Payload Configuration

4.16.3 Message #21100: EO/IR Configuration State.
This message shall be used to define the EO/IR configuration to the CUCS.
1 - B - 201
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21100.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0301.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0301.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21100.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21100.02
Component Location
1 - B - 202
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0301.06
EO/IR Type
Character 14
None
No Restrictions
Unsigned 1
None
No Restrictions
Integer 2
None
0x
Integer 2
None
0x
Integer 2
None
0x
Integer 2
None
0x
Integer 2
BAM
No Restrictions
Type is identified using

NATO stock numbers,
which are 13-digit
numerical values
conforming with the NATO
Codification System as
defined in STANAGs 3150
and 3151 define the
structure for these values.
0301.07
EO/IR Type Revision

Level
Number identifying
modification level of the
type specified in EO/IR
Type Field.
0301.08
EO Vertical Image
Dimension
Number of pixel rows
0 = Off
0301.09
EO Horizontal Image
Dimension
Number of pixel columns
0 = Off
0301.10
IR Vertical Image
Dimension
Number of pixel rows
0 = Off
0301.11
10
IR Horizontal Image
Dimension
Number of pixel columns
0 = Off
0301.12
11
Field of Regard
Elevation Min
Minimum payload centre
field of view wrt AV, using
payload gimbal if present.
Positive value is above the
surface defined by the AV
lateral/longitudinal plane
1 - B - 203
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0301.13
12
Data Element Name &

Description
Field of Regard
Elevation Max
Type
Units
Range
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Maximum payload centre

Positive value is above the
surface defined by the AV
lateral/longitudinal plane
0301.14
13
Field of Regard Azimuth

Min
Minimum payload centre
Positive value is clockwise
as viewed from above
relative to the nose of the
AV.
0301.15
14
Field of Regard Azimuth

Max
Maximum payload centre
Positive value is clockwise
as viewed from above
relative to the nose of the
AV.
21100.03
15
Table B1 - 131: Message #21100: EO/IR Configuration State

4.16.4 Message #21101: EO/IR/Laser Operating State.
This message shall be used to report the operating state of the EO/IR payload by
station to the CUCS.
1 - B - 204
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21101.00
Presence Vector
Unsigned 5
Bitmapped
No Restrictions
0302.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0302.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21101.05
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21101.06
Component Location
1 - B - 205
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0302.05
Addressed Sensor
Unsigned 1
Bitmapped
0x01 = EO
0x02 = IR
0x04 = Payload -Specific
Identifies which sensor (s)

to control where applicable.
Laser pointers and
rangefinders integrated with
an EO/IR sensor are not
considered a separate
sensor
0302.07
EO Camera Status
Unsigned 1
Enumerated
0 = B/W mode
1 = Colour Mode
21101.07
EO Iris Adjustment Status
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
0302.08
IR Polarity Status
Unsigned 1
Enumerated
0 = Black Hot
1 = White Hot
21101.10
NUC Table Selection
Unsigned 1
Enumerated
21101.11
10
IR Integration Time Status
Integer 2
0.001 s
0x1
21101.12
11
IR Gain Adjustment Mode

Status
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
0302.36
12
IR Level Adjustment
Mode
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
0302.09
13
Image Output State
Unsigned 1
Enumerated
0 = None
1 = EO
2 = IR
3 = Both Simultaneously
4 = Payload -Specific
0302.10
14
Actual Centreline
Elevation Angle
Integer 2
BAM
No Restrictions
+ above aircraft waterline

0302.11
15
Actual Vertical Field of

View
Integer 2
BAM
No Restrictions
0302.12
16
Actual Centreline
Azimuth Angle
Integer 2
BAM
No Restrictions
+ right of aircraft x axis

0302.13
17
Actual Horizontal Field of

View
Integer 2
BAM
No Restrictions
0302.14
18
Actual Sensor Rotation

Angle
Integer 2
BAM
No Restrictions
Unsigned 1
Enumerated
0 = Fields 20, 21, and 22

Not Valid
1 = Fields 20, 21, and 22
Valid
Integer 4
BAM
-/2 x /2
+ Clockwise rotation from

aircraft normal (Up)
0302.15
19
Image Position
Indicates when the latitude,
longitude and altitude fields
are filled with valid data
0302.16
20
Latitude of image centre
1 - B - 206
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0302.17
21
0302.18
22
Data Element Name &

Description
Type
Units
Range
Longitude of image
centre
Integer 4
BAM
No Restrictions
Altitude
Integer 3
0.02 m
-1,000 x 100,000
Unsigned 2
0.00005
x1
Unsigned 2
0.00005
x1
Unsigned 1
Enumerated
0 = No Value
to AV
to Inertial
4 = Lat-Long Slaved
5 = Target Slaved (track)
6 = Stowed
7 = Caged
8 = Initialising
9 = Calibration
10 = Standby
11 - 31 = Reserved
Unsigned 1
Enumerated
0 = Off/Break
1 = Acquire
2 = Track
3 = Not Specified
Unsigned 2
No Restrictions

below (-) the WGS-84
reference geoid of image
centre.
21101.03
23
Pixel X
Horizontal position in the
video frame (The right edge
is 1)
21101.04
24
Pixel Y
Vertical position in the
video frame (The bottom
edge is 1)
0302.19
25
Pointing Mode State

Enumerations 8-10 added
to Edition 2.
21101.02
26
Tracker Mode Status

This field is valid when the
is Target Slaved (Track).
Edition 2.
0302.21
27
Reported Range
If > 0, then reported range
is valid for the current
reported location in this
message
0 = Range is Invalid
1 - B - 207
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21101.13
28
Focus Type Status
Unsigned 1
Enumerated
0 = Automatic
1 = Manual
2 = Not Specified
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified

Edition 2.
21101.14
29
Image Stabilization Status

Edition 2.
21101.09
30
Fire Laser Pointer Status
Unsigned 1
Enumerated
0 = Off
1 = On (Safe)
2 = On - Not Firing (Arm)
3 = Lasing (Fire)
4 = Laser Masked (Disable)
5 - 15 = Reserved
0302.22
31
Fire Rangefinder Status
Unsigned 1
Enumerated
0 = Off
1 = On (Safe)
2 = On - Not Firing (Arm)
3 = On Recharging (Arm Charging)
4 = Lasing (Fire)
5 = Laser Masked (Disable)
6 - 15 = Reserved
21101.18
32
Laser Mode Status
Unsigned 1
Enumerated
0 = Operational Check
1 = Mission
2 = Boresight
3 = Not Specified
4 - 7 = Reserved

Edition 2.
0302.23
33
Selected Laser
Rangefinder First/Last
Pulse
Unsigned 1
Enumerated
1 = First
2 = Last
0302.24
34
Laser Designator Code
Unsigned 2
None
No Restrictions
Laser Illuminator Code per

STANAG 5516 (Ed 2) (Link
16) Page E-3-527 DFI
#1676 DUI 001
0302.25
35
Laser Designator Status
Unsigned 1
Enumerated
0 = Off
1 = On - Safe
2 = On - Arm
3 = Lasing
4 = Laser Masked
21101.15
36
EO Sensor Power State
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified

Edition 2.
1 - B - 208
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21101.16
37
IR Sensor Power State
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

Edition 2.
21101.17
38
Other Sensor Power State

Edition 2.
21101.08
39
Table B1 - 132: Message #21101: EO/IR/Laser Operating State

4.16.5 Message #21200: SAR Operating State.
This message shall be used to report the SAR operating state by station to the
CUCS.
Unique
ID
Field
Data Element Name

& Description
Type
Units
Range
21200.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0303.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0303.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 209
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name

& Description
Type
Units
Range
21200.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Character
14
None
No Restrictions
Unsigned 1
Enumerated
Location ID on a
given Station Location
21200.02
Sub-Component
Number
Location ID on a
given Component
Location
0303.05
SAR Type
Type is identified
using NATO stock
numbers, which are
13-digit numerical
values as of date of
publication.
0303.06
SAR Type Revision

Level
Number identifying
modification level of
the type specified in
the SAR Type Field.
1 - B - 210
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0303.07
Data Element Name

& Description
Radar Operating
Mode
Type
Units
Range
Unsigned 1
Enumerated

8 = 07A - Mode 3 Area, Slant Plan
9 = 07L - Mode 3 LOC, Slant Plan
10 = 14A - Mode 4 area, Slant
Plane
Plane
12 = 1SP - ETP, Spotlight 1, Slant
13 = 3SP - ETP, Spotlight 3, Slant
14 = 10S - ETP, Scan, Slant
15 = GSP - Tier 2+ Spot Mode
16 = GSH - Tier 2+ Search Mode
17 = AIP13 - Monopulse Calibration
18 = AIP14 - Wide Area MTI
(WAMTI)
19 = AIP15 - Coarse Resolution
Search
20 = AIP16 -Medium Resolution
Search
21 = AIP17 - High Resolution
Search
22 = AIP18 - Point Imaging
23 = AIP19 - Swath MTI (SMTI)
24 = AIP20 - Repetitive Point
Imaging
25 = AS201 Search
26 = AS202 - Spot 3
27 = AS204 - Spot 1
30 = AS209 - EMTI Wide Frame
Search
31 = AS210 - EMTI Narrow Frame
Search
32 = AS211 - EMTI Augmented
Spot
33 = AS212 - EMTI Wide Area MTI
(WAMTI)
34 = AS213 Monopulse
Calibration
35 - 100 = Reserved
Unsigned 1
Enumerated
1 = Clutter Map
2 = Moving Target
3 - 9 = Reserved
Reference: NSIF
Registry, AEDP-4,
Annex D.
0303.09
Radar MTI Mode

Status
Reference: NSIF
Registry, AEDP-4,
Annex D.
1 - B - 211
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name

& Description
Type
Units
Range
0303.10
Resolution
Unsigned 2
0.01 m
x 100
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Current pixel
resolution of SAR
product
0 = Unknown
0303.11
10
Current Field of
View - Elevation Min
above body x axis
0303.12
11
Current Field of
View Elevation
Max
above body x axis
0303.13
12
Current Field of
View Azimuth Min
right of body x axis
0303.14
13
Current Field of
View Azimuth Max
right of body x axis
21200.03
14
Station Number 1732
Table B1 - 133: Message #21200: SAR Operating State

4.16.6 Message #21400: Communications Relay Status.
This message shall be used to report the Communications Relay status to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21400.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0305.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 212
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0305.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21400.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21400.02
Component Location
1 - B - 213
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21400.03
Power
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Standby
3 = Deploy
4 = Activate
5 = Deactivate
6 = Stow
7 = Not Specified
Unsigned 1
Enumerated
1 - 8 = Reserved
9 = Not Specified
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Character 80
None
No Restrictions
Character 80
None
No Restrictions
Enumerations 3-7 added to

support backwards
21400.04
Mode Status
Enumerations 1-9 added to
support backwards
21400.05
RF Power Level Radio A

Reports the transmission
power level of radio A. 0 is
21400.06
RF Power Level Radio B

Reports the transmission
power level of radio B. 0 is
21400.07
Radio A
Reports the predefined
21400.08
10
Radio B
Reports the predefined
repeater configuration
21400.09
11
Configuration Name
Radio A
Reports the configuration
name.
21400.10
12
Configuration Name
Radio B
Reports the configuration
name.
1 - B - 214
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21400.11
13
BIT Status
Unsigned 1
Enumerated
0 = Bit not run

1 = BIT Running
2 = BIT Passed
3 = BIT Failed
21400.12
14
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 134: Message #21400: Communications Relay Status

4.16.7 Message #21401: Communications Relay Configuration Status.
This message shall be used by the VCM to indicate the Communications Relay
configuration status.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21401.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
21401.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
21401.02
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 215
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21401.07
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21401.08
Component Location
21401.03
Unsigned 1
None
No Restrictions
21401.04
Frequency
Unsigned 3
100 Hz
x 512,000,000.0
21401.05
Hop ID
Unsigned 1
None
No Restrictions
Unsigned 1
Enumerated
0 = Not Loaded
1 = Loading
2 = Loading Complete
3 = Loading Failed
0 = No hop
21401.06
Configuration Status
1 - B - 216
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21401.09
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 135: Message #21401: Communications Relay Configuration Status

4.16.8 Message #21402: Communication Relay Configuration State.
This message shall be used to define the Communication Relay configuration to the
CUCS. Please refer to Message 21001.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21402.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
21402.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
21402.02
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 217
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21402.03
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21402.04
Component Location
21402.05
Communication Relay
Type
Character 14
None
No Restrictions
21402.06
Communication Relay
Type Revision Level
Unsigned 1
None
No Restrictions
Number identifying
modification level of the
type specified in
Communication Relay Type
Field.
1 - B - 218
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21402.07
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 136: Message #21402: Communication Relay Configuration State

4.16.9 Message #21500: Payload Data Recorder Status.
This message shall be used to report the status of the platform payload data storage
device(s). It assumes that there is a potential for multiple recorders on-board the
platform and that each recorder has independent play/record states (e.g., is capable
of simultaneous record and playback activity.) Recorder status messages shall be
sent by request only.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21500.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0306.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0306.04
Recording Device
Number
Unsigned 1
None
No Restrictions
0306.05
Active Index Type
Unsigned 1
Enumerated
0 = Time
1 = Block Number
2 = Event Mark
3 = Session Number
4 - 9 = Reserved
Indicates the type of

indexing currently in use on
the given recorder.
0306.06
Recording Status
Unsigned 1
Enumerated
0 = Stop
1 = Active, Not Ready
2 = Ready/Pause
3 = Recording
4 - 9 = Reserved
0306.07
Record Rate
Float
Mbit/s
0.001 x 40,000
1 - B - 219
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0306.08
Current Recording Index
Integer 4
None
0x
Unsigned 5
0.001 s
See Section 1.7.2
0 = No Active Index
0306.09
Record Index Time Stamp

For events, time of the
event, for blocks or
sessions, the time of block
or session start.
0306.10
Replay Status
Unsigned 1
Enumerated
0 = Stop
1 = Active, Not Ready
2 = Ready/Pause
3 = Reading
4 - 9 = Reserved
0306.11
Replay Rate
Float
Mbit/s
0.001 x 40,000
0306.12
10
Current Replay Index
Integer 4
None
0x
Integer 2
None
No Restrictions
0 = No Active Index
0306.13
11
Health Status Code

Recorder Specific
Table B1 - 137: Message #21500: Payload Data Recorder Status

4.16.8 Message #21501: Vehicle Payload/Recorder Configuration.
This message shall be used by the VSM to identify the payload/recorder

configuration of the AV and is sent to the CUCS. This message will be sent once for
each connection between a Payload and Recorder.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21501.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0307.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 220
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0307.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21501.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
None
No Restrictions
Station Location
21501.02
Component Location
0307.05
Payload Recorder
1 - B - 221
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21501.03
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 138: Message #21501: Vehicle Payload/Recorder Configuration

4.16.9 Message #21600: Terrain Data Request.
This message shall be used to request the highest terrain data in a specific area. To
enable a single point request, the Latitude 1 and Latitude 2 value will have the same
latitude value while Longitude 1 and Longitude 2 will have the same longitude value.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21600.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
21600.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
21600.02
Latitude 1
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
of terrain corner
21600.03
Longitude 1
of terrain corner
21600.04
Latitude 2
of terrain corner
21600.05
Longitude 2
of terrain corner
Table B1 - 139: Message #21600: Terrain Data Request
1 - B - 222
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Figure B1 - 14: Terrain Data

4.16.10 Message #21700: Payload Operating Mode Report.
This message is used to define the payload specific mode and whether it is
commanded via a preplanned mission or real time.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21700.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
21700.04
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 223
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
21700.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
21700.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
21700.02
Component Location
21700.06
Device Number
Unsigned 1
None
No Restrictions
21700.07
Platform Power
Unsigned 1
Enumerated
0 = Off
1 = Power Standby
2 = On
1 - B - 224
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0302.06
21700.08
21700.03
Data Element Name &

Description
Type
Units
Range
System Operating Mode

State
Unsigned 1
Enumerated
0 = Deployed
1 = Activated
2 = Deactivated
3 - 9 = Reserved
Mission Plan Control

Mode
Unsigned 1
Enumerated
0 = Preplanned Mode
1 = Manual Mode
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 140: Message #21700: Payload Operating Mode Report

4.17 Weapons Command Messages.
4.17.1 Message #24000: Stores Management System Command.
This message shall be used by the CUCS to command the stores management
system located at the Station Number specified in the message.
The VSM shall use the General Configuration Messages to define the Stores
Management Systems (specified by Station Number) capability to support the fields
commanded in this message. Refer to Sections 4.24 and 4.25, General
Configuration Messages for additional details.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
24000.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0203.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 225
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0203.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
24000.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
24000.02
Component Location
24000.04
Device Number
Unsigned 1
None
No Restrictions
24000.05
Number of Stores to
Release Each Time
Unsigned 2
None
No Restrictions
1 - B - 226
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0203.06
0203.07
Data Element Name &

Description
Type
Units
Range
Active Weapon Mode

Command
Unsigned 1
Enumerated
0 = N/A (0000 0000)

17 = Disarm (0001 0001)
34 = Initialise (0010 0010)
51 = Arm (0011 0011)
68 = Jettison (0100 0100)
85 = Launch (0101 0101)
Active Target Acquisition

Mode Select
Unsigned 1
Enumerated
0 = N/A
1 = Coordinates
2 = Sensor-Based Tracking
3 - 9 = Reserved
0203.08
Active Attack Mode
Unsigned 1
Enumerated
0 = N/A
1 = Time
2 = Heading
3 = Window
4 = Altitude
5 - 9 = Reserved
0203.09
10
Rack/Rail Ejector Enable

(Hung Ordnance)
Unsigned 1
Enumerated
0 = N/A
1 = Lock
2 = Unlock
0203.10
11
Safety Enable Discrete

Command
Unsigned 1
Enumerated
0 = N/A
1 = Enable
2 = Inhibit
0203.11
12
Set Target Latitude
Integer 4
BAM
-/2 x /2
0203.12
13
Set Target Longitude
Integer 4
BAM
No Restrictions
0203.13
14
Set Target Altitude
Integer 3
0.02 m
-1,000 x 100,000
0203.14
15
Target Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84
Defines altitude type for

previous field
0203.15
16
Set Target Inertial Speed

(Vx)
Integer 2
0.05 m/s
-1,000 x 1,000
0203.16
17

(Vy)
Integer 2
0.05 m/s
-1,000 x 1,000
0203.17
18

(Vz)
Integer 2
0.05 m/s
-1,000 x 1,000
20000.06
19
Activity ID
Unsigned 3
None
No Restrictions

1 - B - 227
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
24000.03
20
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 141: Message #24000: Stores Management System Command

4.18 Weapons Status Messages.
4.18.1 Message #26000: Stores Management System Status.
This message shall be used to report the stores management system status to the
CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
26000.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
0304.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0304.04
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 228
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
26000.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
26000.02
Component Location
26000.04
Device Number
Unsigned 1
None
No Restrictions
0304.05
Active Weapon Type
Unsigned 1
Enumerated
0 = No Mode
1 = Air-To-Air Weapon
2 = Air-To-Ground Weapon
3 = Anti-Submarine
Weapon
4 - 10 = Reserved
0304.06
Active Weapon Sensors
Unsigned 1
Enumerated
0 = No Mode
1 = EO
2 = Laser
3 = EM
4 = IR
0304.07
Active Weapon Number

per Station
Unsigned 1
None
No Restrictions
1 - B - 229
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0304.08
0304.09
Data Element Name &

Description
Type
Units
Range
Active Target Acquisition

Mode
Unsigned 1
Enumerated
0 = No Mode
1 = Coordinates
2 = Sensor-Based Tracking
3 - 9 = Reserved
10
Active Attack Mode
Unsigned 1
Enumerated
0 = No Mode
1 = Time
2 = Heading
3 = Window
4 = Altitude
5 - 9 = Reserved
0304.10
11
Weapon Initialising
Unsigned 1
Enumerated
0 = No Mode
1 = Sensors Initial
Alignment
2 = Seeker Steering Mode
3 = Navigation Data
Loading
4 = Target Data Loading
5 = BIT in Progress
0304.11
12
Weapon Release
Clearance
Unsigned 1
Enumerated
0 = Not Clear
1 = Clear
0304.12
13
Clearance Validity
Unsigned 1
Enumerated
0 = Not Clear
1 = Clear
0304.14
14
Weapon Status
Unsigned 1
Enumerated
0 = N/A
1 = Ready
2 = Armed
3 = Failed
26000.05
15
Current Target Latitude
Integer 4
BAM
-/2 x /2
26000.06
16
Current Target Longitude
Integer 4
BAM
No Restrictions
26000.07
17
Current Target Altitude
Integer 3
0.02 m
-1,000 x 100,000
-100,000 x -100,000
If this field is -100,000, then

the Current Target location
fields do not contain valid
target coordinates.
-100,000 added for
Edition 2.
26000.08
18
Current Target Altitude

Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84
0304.15
19
Rack/Rail/Ejector Unlock
Unsigned 1
Enumerated
0 = Unlocked
1 = Locked
1 - B - 230
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0304.16
20
0304.17
Data Element Name &

Description
Type
Units
Range
Safety Enable Discrete

State
Unsigned 1
Enumerated
0 = N/A
1 = Enable
2 = Inhibit
21
Launch Acceptable
Region (LAR) Status
Unsigned 1
Enumerated
0 = N/A
1 = Green (Acceptable)
2 = Yellow (Marginal)
3 = Red (Not Acceptable)
0304.18
22
Safe Separation Status

(Weapon)
Unsigned 1
Enumerated
0 = N/A
1 = Green (Released)
2 = Red (Hung Store)
0304.19
23
Number of Stores
Available
Unsigned 2
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
0 = Empty or N/A
1 to 65534 = Count
65535 = 65535 or Greater
Count
26000.03
24
Table B1 - 142: Message #26000: Stores Management System Status

4.19 Data Link Discovery Messages.
The messages have been developed with the intention of separating the
communication (radio) equipment functionality from the pedestal functionality. The
Data Link Command and Status messages have also been developed with the
intention to fully control a STANAG 7085 compliant data link.
Message #28000 and Message #28001 are considered to be the Data Link
Discovery and Connection messages. The Data Link Discovery functionality is
intended to allow a CUCS on the network to discover any data link connected to the
network, whether it is a standalone network data link or a data link connection to the
network through a VSM, without the CUCS having previous knowledge of the system
data links. Once a data link has been configured for control, using the General
1 - B - 231
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Configuration Messages, Message #28000 and Message #28001 are used for the
requesting and granting of data link control within the system.
Each of the data link messages contain a Data Link ID field which is used to
specifically identify the data link terminal for which the message applies. In Message
#28001 there is an additional VDT/CDT flag to specifically identify a Data Link as a
VDT or as a CDT. The CDT and VDT are not considered permanently paired;
therefore the Data Link ID for a CDT/VDT combination shall not be a single Data Link
ID for a specific hardware pair. This is to provide the capacity to maintain a Data
Link ID reference for each terminal, such as in the event of a transition in control of
an AV from one CDT to another, where the CDT/VDT combination is altered.
A CUCS may be directly configured for control of a CDT from the CDT Data Link
terminal itself if the Data Link terminal speaks DLI, or via a VSM, using the General
Configuration messages. A VDT Data link terminal onboard an AV that speaks DLI
cannot report its presence until it has a communication channel to the CUCS.
Therefore it is expected that a CUCS that requires control over a VDT will first be
communicating with the AV.
It is suggested that the configuration, control and status of a VDT(s) onboard an AV
be coordinated by the AV avionics (control system) and not by the VDT independent
of the vehicle control system. This will ensure that the CUCS controlling the AV
maintains control over a VDT terminal for communicating AV control and status
messages between that CUCS and the AV. To support this philosophy, the Data
Link Command Messages (#30004 & 32004) support the capability to command the
data link to pass all data link messages received from the RF side of the link to the
local CUCS/ VSM/ AV without interpreting those commands at the Data Link, and
only interpret commands for itself from the hardware/ wired interface. In this sense
any Data Link control messages transmitted for an VDT located onboard an AV are
considered AV control messages, and any Data Link status messages transmitted
from the AV for an VDT are considered AV status messages, and treated as such.
Currently a multicast schema has been defined for transmitting the DLI messages
across the network, therefore the Data link messages have been developed to
provide a basic functional message routing capability. The messages allow for the
use of CDT and VDT Data Links that do not have a built in switching or routing
capability for multicast messages.
4.19.1 Message #28000: Data Link Control Authorisation Request.
When a CUCS is required to communicate with a data link (CDT) in order to transmit
and receive messages to and from an AV, the determination of the type and number
of data links attached to the system may be required in order for that CUCS to select
the data link(s) to communicate with the specified vehicle. Where the CUCS does
not know the Data Link ID(s) on the network, the CUCS may conduct a broadcast
request for Data Link information.
When a CDT Data Link is being discovered, the vehicle type and subtype fields
shall be filled appropriate to the request. The Request/Handover Access field shall
be transmitted as Unspecified for a Broadcast Discovery (Request) and the Asset
Mode field shall be set to Broadcast Request.
1 - B - 232
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
To conduct a broadcast for the VDT Data Links located on an AV, the Vehicle ID of
the AV is used in the wrapper destination field to filter (limit) the request to that AV.
Where the CUCS knows the CDT/ VDT Data Link ID, the Data Link Assignment
Request Message shall be used to request and release control over the Data Link ID
for the configuration specified in the message (e.g.; by vehicle ID, vehicle type, and
vehicle subtype).
The transmission of the Data Link Assignment Request message with both a Vehicle
ID and a Data Link ID (Destination ID in wrapper) shall be to request or release
control of the specified Data Link ID located on the specific Vehicle ID in accordance
with the Requested/ Handover Access and Assets Mode fields. Most likely the
CDT will not be located on a vehicle (AV), therefore in this instance the vehicle ID
value shall be set to the null ID to indicate that it does not apply.
Where a VSM is between the Data Link ID and the CUCS, the VSM shall be
responsible for transferring the Data Link Command and Status messages (Section
4.20 and 4.21) between the specified Data Link ID and the CUCS. Refer to the
following figure.
Air Vehicle
CDT
VSM
CUCS
Data Link ID
VSM ID
Figure B1 - 15: CUCS VSM CDT Connection
The response to this message

Configuration/Assignment Message.
is
Message
#28001,
Data
Link
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
28000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0404.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0404.10
Requested/Handover
Access
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
Allows request or handover

0x00 = Unspecified
1 - B - 233
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0404.12
VSM / Vehicle ID
Integer 4
None
See Section 1.7.6
0404.11
Asset Mode
Unsigned 1
Enumerated
0 = Relinquish/Handover
1 = Request
2 = Override
3 = Broadcast Request
0404.07
Vehicle Type
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 3
None
No Restrictions

assigned by STANAG
Custodian.
0404.08
Vehicle Subtype
the manufacturer.
28000.01
Activity ID
Table B1 - 143: Message #28000: Data Link Control Authorisation Request

4.19.2 Message #28001: Data Link Configuration/Assignment Message.
The intent of this message is to provide the CUCS with the data link configuration of
the VSM, or network, on request from a CUCS, with one instance of this message
sent for each employed Data Link ID/ vehicle type/ vehicle subtype combination.
This message shall be transmitted in response to Message #28000, Data Link
Control Authorisation Request, by appropriately filling this message with the reported
Data Link IDs capabilities and setting the Access Authorized field as appropriate.
The Access Granted field shall be set appropriately in response to a Data Link
Broadcast Request from a CUCS that is already in control of the Data Link being
reported in the broadcast response.
The appropriate supported vehicle type and Vehicle subtype identified in this
message shall be transmitted once for each vehicle type/ subtype combination
possible. The Data Link (ID) shall be responsible for identifying (reporting) the
availability of the data link based on the number of vehicle / CUCS connections that
are possible versus connected.
This message shall be used by a VDT (Data Link ID) to identify its capabilities to the
CUCS, where the message wrapper specifically identifies the vehicle ID on which the
VDT is located.
This message shall be used by a VSM to identify to a CUCS the data link capabilities
associated with a VSM, where the Data Links are attached behind the air vehicles
ground based VSM. Refer to Figure B1 - 16. Where a CDT is connected through the
VSM, the VSM shall assign a logical vehicle ID to be transmitted with the supported
vehicle type and Vehicle subtype identified in this message along with the VSM ID to
1 - B - 234
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
identify the connection. This message therefore provides the association between the
VSM and Data Link through their respective IDs as reported in this message. Where
a VSM supports more than one vehicle type and vehicle subtype for a single CDT
(resource sharing), each instance of support shall be reported to the CUCS with the
same Data Link ID, but with a different logical vehicle ID, vehicle type and subtype.
Where a data link is shared between two or more VSMs, physical or logical, the CDT
(Data Link) Status shall be the responsibility of the VSMs. Refer to the following
figure.
CUCS
Network
VSM
VSM
VSM ID
VSM ID
Network
CDT - A
CDT - B
Data Link
Data Link
Figure B1 - 16: Shared Data Links
This message shall be used by the VSM/ Data Link to grant a CUCS control over a
specific Data Link ID, report the Data Link ID connection as not authorized, or to
report the successful release/ availability of a Data Link ID. For each reported Data
Link ID/vehicle type /vehicle subtype combination, the VSM/ Data Link shall report
the controllability of the data link in the Access Authorized field. Where the CDT is
in control and being used to transmit messages to a vehicle for one of these Data
Link ID/vehicle type/vehicle subtype combinations, the Vehicle ID field located in the
message wrapper structure shall be filled with the controlled Vehicle ID.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
28001.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1 - B - 235
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0500.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
28001.06
VSM / Vehicle ID
Integer 4
None
See Section 1.7.6
28001.01
Access Authorized
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
0x04 = Broadcast
Response
0x00 = Connection Not

Authorised
28001.02
Access Granted
0x00 = N/A
28001.03
Access Requested
This field echoes the
access request that this
response addresses
0x00 = Unspecified
0500.07
Terminal Type
Unsigned 1
Enumerated
0 = CDT
1 = VDT
0500.08
Data Link Type
Unsigned 1
Enumerated
0 = STANAG 7085
1 - 7 = Reserved
28001.05
Data Link Subtype
Unsigned 2
Enumerated
0500.09
Data Link Name
Character 20
None
No Restrictions
Text identifier for Data Link

0500.10
10
Antenna Type
Unsigned 1
Enumerated
1 = Omni
2 = Directional
28001.04
11
Pedestal Index
Unsigned 1
None
No Restrictions
0500.11
12
Vehicle Type
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 1
Enumerated
0 = Available for Control

1 = Unavailable for Control
2 = Request Granted

assigned by STANAG
Custodian.
0500.12
13
Vehicle Subtype
the manufacturer.
28001.07
14
Data Link Control

Availability
Table B1 - 144: Message #28001: Data Link Configuration/Assignment

Message
1 - B - 236
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.20 Data Link Command Messages.
4.20.1 Message #30000: Data Link To Vehicle ID Assignment.
This message allows for the use of CDT and VDT Data Links that do not have a built
in switching or routing capability for multicast messages.
The CUCS shall transmit this message to the Vehicle ID, VSM ID, and Data Link ID
to identify which vehicles are communicating via the Data Link ID. The data link with
the Data Link ID specified in this message shall intercept all the other DLI messages
with the vehicle ID specified in the Communicating Vehicle ID field and forward those
messages to the specified vehicle ID over the RF link. The data link with the Data
Link ID specified in this message shall receive messages from the Vehicle ID
(Communicating Vehicle ID) and forward the messages to the required CUCS ID/
VSM ID per the received message.
This message shall be sent once for each vehicle ID required to communicate
through the specified Data Link ID.
Vehicle B
Vehicle A
CDT
CDT
Data Link ID - C
Data Link ID - B
CUCS
CDT
Figure B1 - 17: Relay System
In the above example, the CUCS transmits one message to the null Vehicle ID/ Data
Link ID A to indicate that Vehicle ID A is communicating through Data Link ID
A, and one message to the null vehicle ID/ Data Link ID A to indicate that vehicle ID
B is communicating through Data Link ID A. The CUCS transmits one message
to the Vehicle ID - A/ Data Link ID C to indicate that Vehicle ID B is
communicating through Data Link ID A.
1 - B - 237
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
If multiple Data Links on the AV are not capable of routing messages between
themselves through a multicast routing, it is the AVs responsibility to ensure the
correct messages pass between the two data links in the system.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
30000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30000.02
Communicating Vehicle
ID
Integer 4
None
See Section 1.7.6
Unsigned 1
Enumerated
0 = Specified
communicating Vehicle ID
to be unassigned from DL
1 = Specified
communicating Vehicle ID
to be assigned to DL
Vehicle ID to be controlled
through Data Link ID.
30000.03
Communication State
For Communicating Vehicle
ID
30000.04
Message Assignment
Unsigned 1
Enumerated
0 = Pass All Messages

1 = Pass Specific Message
2 = Do Not Pass Specific
Message
3 = Pass Specific LOI
4 = Do Not Pass Specific
LOI
5 = Clear All Message
Passing Assignments
30000.05
Message Type
Unsigned 4
None
No Restrictions
See Section 3.3.1.9

30000.06
Specific LOI
Unsigned 1
Bitmapped
0x01 = LOI 1
0x02 = LOI 2
0x04 = LOI 3
0x08 = LOI 4
0x10 = LOI 5
30000.08
Specific Control/Monitor
Unsigned 1
Bitmapped
0x01 = Monitor
0x02 = Control
Unsigned 3
None
No Restrictions
0x00 = Unspecified
30000.07
Activity ID
Table B1 - 145: Message #30000: Data Link To Vehicle ID Assignment

4.20.2 Message #30001: 7085 Data Link Active Configuration Set Up Message.
This message shall be used to set up the components of the VDT and/or CDT data
link communication equipment.
1 - B - 238
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30001.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30001.02
STANAG 7085 Profile ID

Part 1
Composite 1
None
No Restrictions
Defines the first three digits

of the Profile Identifier as
specified in STANAG 7085.
See STANAG 7085, Annex
P
30001.08
2.1
7085 Annex
Unsigned
Bits 2
Enumerated
0 = Annex B
1 = Annex C
2.2
7085 Appendix
Unsigned
Bits 2
Enumerated
0 = Appendix 1
2.3
7085 Implementation
Unsigned
Bits 4
Enumerated
0 = Implementation 1

Part 2
Unsigned 1
Enumerated
0 = Not Specified
1 - 255 = See STANAG
7085, Annex P
Unsigned 1
Enumerated
0 = Not Specified
1 - 255 = See STANAG AR
7085, Annex B, Appendix 1,
Implementation 1
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 1
None
No Restrictions
Defines the last digit of the

Profile Identifier as
Enumeration 0 added to
support backwards
30001.03
Set Configuration Index

Defines default values for
the data link configuration
fields.
support backwards
30001.04
Set Forward Link (FL)

Carrier Frequency
A bias of 9000 MHz is
applied to the decoded
value.
(bias = 9,000 MHz)
30001.05
Set Return Link (RL)

Carrier Frequency
value.
(bias = 9,000 MHz)
30001.06
Set Forward PN Code

Index
Implementation Specific
1 - B - 239
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30001.07
Activity ID
Unsigned 3
None
No Restrictions
Unsigned 1
Enumerated
0 = CDT
1 = VDT
Unsigned 2
None
No Restrictions
Unsigned 1
None
No Restrictions

0400.05
Addressed Terminal
Edition 2.
0400.06
10
Select Channel
This field is ignored if a
valid 7085 profile is
specified.
Edition 2.
0400.07
11
Select Primary Hop

Pattern
This field is ignored if a
valid 7085 profile is
specified.
Edition 2.
Table B1 - 146: Message #30001: 7085 Data Link Active Configuration Set Up
Message
4.20.3 Message #30002: 7085 Data Link Fallback Configuration Set Up
Message.
This message shall be used to set up the fallback configuration of the VDT and/or
CDT data link communication equipment. The data link equipment will assume this
configuration if a loss of link exceeds the Fallback time defined in this message.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30002.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 240
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
30002.02
Data Element Name &

Description
Part 1
Type
Units
Range
Composite 1
None
No Restrictions

P
30002.09
2.1
7085 Annex
Unsigned
Bits 2
Enumerated
0 = Annex B
1 = Annex C
2.2
7085 Appendix
Unsigned
Bits 2
Enumerated
0 = Appendix 1
2.3
7085 Implementation
Unsigned
Bits 4
Enumerated

Part 2
Unsigned 1
Enumerated

7085, Annex P
Unsigned 1
Enumerated
1 - 255 = See STANAG AR

7085, Annex B, Appendix 1,
Implementation 1
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
10 s
No Restrictions

30002.06
Set Configuration Index

Defines default values for
the data link configuration
fields.
30002.03

Carrier Frequency
value.
(bias = 9,000 MHz)
30002.04

Carrier Frequency
value.
(bias = 9,000 MHz)
30002.05
Set Forward PN Code

Index
Implementation Specific
30002.07
Set Fallback Time

Loss of link greater than
this time will cause the data
link to change to this
configuration.
0 = Fallback Function
Disabled
1 - B - 241
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30002.08
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 147: Message #30002: 7085 Data Link Fallback Configuration Set Up
Message
4.20.4 Message #30003: Data Link Control Command.
This message shall be used to send instructions to the VSM/Data Link to command
the components of the CDT and/or VDT data link communications equipment.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30003.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30003.02
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30003.03
Set Transmitter State
Unsigned 1
Enumerated
0 = Off
1 = Standby
2 = On
30003.04
Set Transmit Attenuation
Unsigned 1
Enumerated
0 - 255 = Data Link Specific
30003.05
Set Receiver State
Unsigned 1
Enumerated
0 = Off
1 = On
2 = Not Specified
Unsigned 1
Enumerated
support backwards
30003.06
Select Active Antenna

Pedestal Index
Selects which antenna is
being addressed
30003.07
Communication Security
Mode
Unsigned 1
Enumerated
0 = Normal (0000 0000)

17 = Zeroize (0001 0001)
34 = Hold (0010 0010)
51 = Reset (0011 0011)
68 = Bypass (0100 0100
(Future))
30003.01
Key Action
Unsigned 1
Enumerated
0 = Clear
1 = Set
2 = Not Specified
Unsigned 1
Enumerated
0 = N/A
1 = Primary
support backwards
30003.08
Key Index
1 - B - 242
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30003.09
Activity ID
Unsigned 3
None
No Restrictions
Unsigned 1
Enumerated
0 = CDT
1 = VDT
Unsigned 1
Enumerated
0 = Omni
1 = Directional
2 = Auto
Unsigned 1
Enumerated
0 = Primary
1 = Secondary
2 = Tertiary
3 - 255 = Quaternary to
Last

0401.05
10
Addressed Terminal
Edition 2.
0401.07
11
Set Antenna Mode

Edition 2.
0401.09
12
Link Channel Priority

Edition 2.
Table B1 - 148: Message #30003: Data Link Control Command

4.20.5 Message #30004: RF Command Processing Set Up Message.
This message shall be used to specify how the data link will use the data link
commands directly received via the RF transmission. The Commands from RF field
specifies if the commands are to be acted on when received via the RF path and if
the command should be passed on to the local host.
1 - B - 243
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
RF MSG
Data Link RF
Message
Processing
0&2
Local Host
Computer
0&1
Data Link
HW/SW Control
Figure B1 - 18: Commands from RF Data Flow
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30004.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
30004.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30004.02
Commands From RF
Unsigned 1
Enumerated
0 = use RF commands and

Pass them through
1 = Use RF commands and
do not pass them through
2 = Do not use RF
commands but pass them
through
Unsigned 3
None
No Restrictions
Commands the data link if it

should directly interpret
messages sent as received
on the RF side of the data
link. Also commands the
data link if it should pass all
data link messages
received from the RF side
on to the local
CUCS/VSM/AV.
30004.03
Activity ID
Table B1 - 149: Message #30004: RF Command Processing Set Up Message

4.20.6 Message #30100: Antenna Pedestal Location Command.
This message shall be used by the CUCS/VSM to send the location of the data link
antenna pedestal to the data link to allowing the data link to point the antenna. If the
antenna is not located on a pedestal, the parameters are filled with the antenna
location. This message is normally used only for the local antenna pedestal.
1 - B - 244
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30100.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30100.02
Antenna Pedestal
Latitude
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
WGS-84
30100.03
Antenna Pedestal
Longitude
WGS-84
30100.04
Antenna Pedestal Altitude
Integer 3
0.02 m
-1,000 x 100,000
30100.12
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
30100.05
Antenna Pedestal Ground

Speed
Unsigned 2
0.05 m/s
No Restrictions
30100.06
Antenna Pedestal Vertical

Speed
Integer 2
0.05 m/s
No Restrictions
Integer 2
BAM
No Restrictions
Integer 2
BAM
No Restrictions
Integer 2
BAM
-/2 x /2
Integer 2
BAM
-/2 x /2
Unsigned 3
None
No Restrictions
Platform Dependent
30100.07
Antenna Pedestal Course

Clockwise from true north
30100.08
Antenna Pedestal
Heading
Clockwise from true north
30100.09
10
Antenna Pedestal Pitch

THETA
30100.10
11
Antenna Pedestal Roll

PHI
30100.11
12
Activity ID
Table B1 - 150: Message #30100: Antenna Pedestal Location Command

4.20.7 Message #30101: Antenna Control Command.
This message shall be used to send instructions to the VSM/Pedestal to command
the components of the pedestal.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30101.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1 - B - 245
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30101.02
Pedestal Index
Unsigned 1
Enumerated
The antenna pedestal to

which the information in this
message is addressed.
30101.03
Set Pedestal State
Unsigned 1
Enumerated
0 = Stowed - Off
1 = Deployed - Off
2 = Deployed - Standby
3 = Deployed On
30101.04
Set Antenna Pointing

Mode
Unsigned 1
Enumerated
0 = Manual Position
1 = Manual - Rate
2 = Auto RF Tracking
3 = Reserved
4 = Auto - Location
5 = Search Pattern 1
30101.08
Set Antenna Type Mode
Unsigned 1
Enumerated
0 = Manual
1 = Auto
30101.05
Set Antenna Type
Unsigned 1
Enumerated
0 = Omni
1 = Directional
30101.06
Set Pedestal Location

Source
Unsigned 1
Enumerated
0 = External
1 = Internal
Unsigned 3
None
No Restrictions
Float
rad
0 x 2
Float
rad
-/2 x /2
Determine the pedestal

source of its own location,
e.g. internal = pedestal
IMU.
30101.07
Activity ID
0403.07
Set Antenna Azimuth

Edition 2.
0403.08
10
Set Antenna Elevation

Edition 2.
1 - B - 246
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0403.11
11
Set Azimuth Slew Rate
Float
rad/s
- x
Float
rad/s
- x
Float
rad
0 x 2
Float
rad
-/2 x /2
Valid for Manual Rate

control mode.
Edition 2.
0403.12
12
Set Elevation Slew Rate

control mode.
Edition 2.
0403.09
13
Set Azimuth Offset

Offset relative to Antenna
Azimuth.
Edition 2.
0403.10
14
Set Elevation Offset

Offset relative to Antenna
Elevation.
Edition 2.
Table B1 - 151: Message #30101: Antenna Control Command
Set Antenna pointing modes are defined below:

Manual, Position:
Antenna is steered manually by providing azimuth and elevation angle
(This corresponds roughly to Air Auto mode in the CDL spec. The only difference is
that in the CDL spec, the elevation is expected to come from a stored value and in
this case, the elevation must be provided. For backward compatibility, the elevation
could be ignored which would be reflected in the status)
Manual, Rate:
Antenna is steered manually by providing rate and direction for Azimuth and
Elevation
(This corresponds roughly to Ground Manual in the CDL spec. The difference is that
Ground Manual only specifies a direction with the rate being fixed and this command
specifies a magnitude and sign indicating direction and speed. For backward
compatibility, a note could be added indicating that fixed rate systems need only look
at the sign of the parameter and not the magnitude.)
Auto, RF Tracking:
1 - B - 247
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Antenna follows the remote antenna by adjusting the antenna position to maintain
maximum RF signal strength received from the remote antenna.
(This is not documented in the current CDL specification but was back in Rev E
where it was referred to as Closed Loop Tracking. This is primarily a ground antenna
mode but there is no reason any random terminal, air or ground, couldnt use it.)
Auto, Location Tracking:
Antenna points to the geographic Location (latitude, longitude, altitude) of the remote
antenna. Remote antenna location may be static or dynamic.
(This corresponds directly to the Air Auto mode defined in the CDL specification.
Generically, this mode applies to both air and ground antennas. In the Rev E
specification, this was referred to as Open Loop tracking with respect to ground
antennas.)
Search, Pattern 1
Data Link specific.
Search, Pattern 2
Data Link specific.
Search, Pattern 3
Data Link specific.
Search, Pattern 4
Data Link specific.
4.20.8 Message #30102: Antenna Position Command.
This message shall be used to control the position of the local antenna relative to the
data link/pedestal. It also provides information about the remote antenna position and
motion.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30102.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30102.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30102.02
Pedestal Index
Unsigned 1
Enumerated

0403.07
Set Antenna Azimuth
Integer 2
BAM
No Restrictions
0403.08
Set Antenna Elevation
Integer 2
BAM
-/2 x /2
0403.11
Set Azimuth Slew Rate
Integer 2
0.0001 rad/s
- x
Integer 2
0.0001 rad/s
- x
Integer 4
BAM
-/2 x /2

control mode.
0403.12
Set Elevation Slew Rate

control mode
30102.07
Remote Antenna Latitude

WGS-84
1 - B - 248
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
30102.08
Data Element Name &

Description
Remote Antenna
Longitude
Type
Units
Range
Integer 4
BAM
No Restrictions
WGS-84
30102.09
Remote Antenna Altitude
Integer 3
0.02 m
-1,000 x 100,000
30102.14
10
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
30102.10
11
Remote Antenna Ground

Speed
Unsigned 2
0.05 m/s
No Restrictions
30102.11
12
Remote Antenna Course
Integer 2
BAM
No Restrictions
30102.12
13
Remote Antenna Vertical

Speed
Integer 2
0.05 m/s
No Restrictions
Unsigned 3
None
No Restrictions
Platform Dependent
30102.13
14
Activity ID
Table B1 - 152: Message #30102: Antenna Position Command

4.20.9 Message #30200: Link Health Command.
This message shall be used to set the data link health reporting mode.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30200.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
30200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30200.02
Bit Mode
Unsigned 1
Enumerated
0 = Off (Abort)
1 = Run Initiated Bit
2 = Run Continuous Bit
30200.03
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 153: Message #30200: Link Health Command

4.20.10 Message #30300: Set Data Link UDP Monitor Period.
This message shall be used to set the period to accumulate UDP messages received
by the data link.
1 - B - 249
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30300.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
30300.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30300.02
UDP Monitor Period
Unsigned 1
x < 255
Unsigned 3
None
No Restrictions
Defines the period to count

UDP messages received
and processed by this data
link.
0 = do not count number of
UDP messages
30300.03
Activity ID
Table B1 - 154: Message #30300: Set Data Link UDP Monitor Period
4.20.11 Message #30301: IP Address and Port Assignment Request.
This message shall be sent by the CUCS to a CDT or AV to request a change in the
IP address and/or port used by the CDT or AV. If the receiving CDT or AV accepts
the requested change, it will update Message #32301 with the new configuration.
The CDT/AV may reject the request if certain criteria are not meet. If this message is
accepted, all previous stream definitions are deleted and replaced by those in this
message.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30301.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
30301.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
30301.02
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 250
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
30301.06
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
30301.07
Component Location
30301.05
Stream ID
Unsigned 1
None
No Restrictions
30301.06
New IP Address
Assignment
Unsigned 4
None
No Restrictions
30301.07
New Port Assignment
Unsigned 2
None
No Restrictions
30301.08
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
1 - B - 251
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Table B1 - 155: Message #30301: IP Address and Port Assignment Request
4.21 Data Link Status Messages.
4.21.1 Message #32000: Data Link To Vehicle ID Report.
The Data Link ID/ vehicle ID/ VSM ID shall transmit this message to the CUCS ID to
report the vehicle ID(s) communicating through the Data Link ID. This message shall
be sent for each vehicle ID communicating, uplink or downlink, through the specified
Data Link ID.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32000.02
ID - Uplink
Integer 4
None
See Section 1.7.6
Unsigned 1
Enumerated
0 = N/A
1 = Specified
communicating vehicle ID
unassigned from DL
2 = Specified
assigned to DL
Integer 4
None
See Section 1.7.6
Unsigned 1
Enumerated
0 = N/A
1 = Specified
no longer communicating
with DL
2 = Specified
down linking to DL
Vehicle ID to which the

Data Link ID is transmitting
messages over the RF link.
Use null ID to specify as not
applicable.
32000.03
Uplink Communication
State
For Communicating Vehicle
ID - Uplink
32000.04
ID - Downlink
Vehicle ID for which the
Data Link ID is receiving
messages on the RF link.
Use null ID to specify as not
applicable.
32000.05
Downlink Communication
State
for Communicating Vehicle
ID - Downlink
Table B1 - 156: Message #32000: Data Link To Vehicle ID Report

4.21.2 Message #32001: 7085 Data Link Active Configuration Status Report.
This message shall be used by the VSM to send the CUCS information on the status
of the VDT and/or CDT data link communications equipment.
1 - B - 252
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32001.02

Part 1
Composite 1
None
No Restrictions

2.1
7085 Annex
Unsigned
Bits 2
Enumerated
0 = Annex B
1 = Annex C
2.2
7085 Appendix
Unsigned
Bits 2
Enumerated
0 = Appendix 1
2.3
7085 Implementation
Unsigned
Bits 4
Enumerated
Unsigned 1
Enumerated

7085, Annex P

P
32001.07

Part 2
32001.03
Configuration Index
Unsigned 1
None
No Restrictions
0501.10
Reported Forward Link

(FL) Carrier Frequency
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 1
None
No Restrictions

value.
Link Dependent
(bias = 9,000 MHz)
0501.11
Reported Return Link

(RL) Carrier Frequency
value.
Link Dependent
(bias = 9,000 MHz)
32001.06
Forward PN Code Index

Link Dependent
Table B1 - 157: Message #32001: 7085 Data Link Active Configuration Status
Report
4.21.3 Message #32002: 7085 Data Link Fallback Configuration Status Report.
This message shall be used by the VSM to send the CUCS information on the
fallback status of the VDT and/or CDT data link communications equipment.
1 - B - 253
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
0503.14
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32002.02

Part 1
Composite 1
None
No Restrictions

2.1
7085 Annex
Unsigned
Bits 2
Enumerated
0 = Annex B
1 = Annex C
2.2
7085 Appendix
Unsigned
Bits 2
Enumerated
0 = Appendix 1
2.3
7085 Implementation
Unsigned
Bits 4
Enumerated
Unsigned 1
Enumerated

7085, Annex P

P
32002.08

Part 2
32002.03
Configuration Index
Unsigned 1
None
No Restrictions
32002.04

Unsigned 2
0.5 MHz
No Restrictions
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
10 s
No Restrictions

value.
Link Dependent
(bias = 9,000 MHz)
32002.05

value.
Link Dependent
(bias = 9,000 MHz)
32002.06
Forward PN Code Index

Link Dependent
32002.07
Fallback Timeout
0= Fallback Function
Disabled
Table B1 - 158: Message #32002: 7085 Data Link Fallback Configuration Status
Report
1 - B - 254
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.21.4 Message #32003: Data Link Control Status Report.
of the VDT and/or CDT data link communications equipment.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32003.02
Transmitter State
Unsigned 1
Enumerated
0 = Off
1 = Standby
2 = On
32003.03
Transmit Attenuation
State
Unsigned 1
Enumerated
32003.04
Receiver State
Unsigned 1
Enumerated
0 = Off
1 = On
32003.05
Active Antenna Pedestal

Index
Unsigned 1
Enumerated
0501.13
State
Unsigned 1
Enumerated
0 = Normal (0000 0000)

17 = Zeroized (0001 0001)
34 = Holding (0010 0010)
51 = Reset (0011 0011)
68 = Bypass (0100 0100
(Future))
32003.07
Key Index
Unsigned 1
Enumerated
0 = Primary
1 - 255 = Alternate Keys
Table B1 - 159: Message #32003: Data Link Control Status Report

4.21.5 Message #32004: RF Command Processing Status Report.
This message reports the current command processing status of the data link.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32004.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32004.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32004.02
Commands From RF
Unsigned 1
Enumerated
0 = Used RF commands
and passed them through
1 = Used RF commands
and did not pass them
through
2 = Did not use RF
commands, but passed
them through.
Table B1 - 160: Message #32004: RF Command Processing Status Report

4.21.6 Message #32005: Legacy Data Link Status Report.
of the ADT and/or GDT data link communications equipment. This message is to
support backwards compatibility to Edition 2.
1 - B - 255
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32005.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
32005.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0501.05
Addressed Terminal
Unsigned 1
Enumerated
0 = CDT
1 = VDT
0501.06
Data Link State
Unsigned 1
Enumerated
0 = Off
1 = Rx Only
2 = Tx / Rx
3 = Tx High Power / Rx
0501.07
Antenna State
Unsigned 1
Enumerated
0 = Omni
1 = Directional
0501.08
Reported Channel
Unsigned 2
None
No Restrictions
0501.09
Reported Primary Hop

Pattern
Unsigned 1
None
No Restrictions
0501.10

Float
Hz
No Restrictions
0501.11

Float
Hz
No Restrictions
0501.12
Downlink Status
Integer 2
0 x 100
0501.13
10
State
Unsigned 1
Enumerated
0 = Not Installed
1 = Not Keyed
2 = Keyed
3 = Zeroized
4 = Bypass
0501.14
11
Link Channel Priority

State
Unsigned 1
Enumerated
0 = Primary
1 = Secondary
2 = Tertiary
3 - 255 = Quaternary to
Last
Table B1 - 161: Message #32005: Legacy Data Link Status Report

4.21.7 Message #32006: Legacy Data Link Control Command Status.
This message is sent from the VSM to the CUCS, and shall report the status of the
instructions to the VSM for the command of the components of the data link. This
message is to support backwards compatibility to Edition 2.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32006.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32006.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0502.05
Addressed Terminal
Unsigned 1
Enumerated
0 = CDT
1 = VDT
1 - B - 256
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
0502.06
0502.07
0502.08
Data Element Name &

Description
Type
Units
Range
Reported Demanded Data

Link State
Unsigned 1
Enumerated
0 = Turn Off
1 = Rx Only
2 = Tx / Rx
3 = Tx High Power / Rx
Reported Demanded
Antenna Mode
Unsigned 1
Enumerated
0 = Omni
1 = Directional
2 = Auto
Reported Demanded
Mode
Unsigned 1
Enumerated
0 = Normal
1 = Zeroize
Table B1 - 162: Message #32006: Legacy Data Link Control Command Status
4.21.8 Message #32100: Antenna Pedestal Location Status Report.
This message shall be used by the VSM to send the CUCS information on the
antenna pedestal location.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32100.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
32100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32100.10
Pedestal Index
Integer 1
None
No Restrictions
0503.11
Antenna Pedestal
Latitude
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
WGS-84
0503.12
Antenna Pedestal
Longitude
WGS-84
0503.13
Antenna Pedestal Altitude
Integer 3
0.02 m
-1,000 x 100,000
32100.11
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
32100.05
Antenna Pedestal Ground

Speed
Unsigned 2
0.05 m/s
No Restrictions
32100.06
Antenna Pedestal Vertical

Speed
Integer 2
0.05 m/s
No Restrictions
Integer 2
BAM
No Restrictions
Platform Dependent
32100.07
Antenna Pedestal Course

Clockwise from True North
1 - B - 257
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
32100.12
10
Data Element Name &

Description
Antenna Pedestal
Heading
Type
Units
Range
Integer 2
BAM
No Restrictions
Integer 2
BAM
-/2 x /2
Integer 2
BAM
-/2 x /2
Clockwise from True North

32100.08
11
Antenna Pedestal Pitch

THETA
32100.09
12
Antenna Pedestal Roll

PHI
Table B1 - 163: Message #32100: Antenna Pedestal Location Status Report

4.21.9 Message #32101: Antenna Control Status Report.
of the VDT and/or CDT pedestal.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32101.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32101.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32101.02
Pedestal Index
Unsigned 1
None
No Restrictions
32101.03
Pedestal State
Unsigned 1
Enumerated
0 = Stowed - Off
1 = Deployed - Off
2 = Deployed - Standby
3 = Deployed On
32101.04
Antenna Pointing Mode
Unsigned 1
Enumerated
0 = Manual Position
1 = Manual - Rate
2 = Auto RF Tracking
3 = Auto Azimuth
4 = Auto - Location
32101.07
Antenna Type Mode
Unsigned 1
Enumerated
0 = Manual
1 = Auto
32101.05
Antenna Type
Unsigned 1
Enumerated
0 = Omni
1 = Directional
32101.06
Pedestal Location Source
Unsigned 1
Enumerated
0 = External
1 = Internal
Table B1 - 164: Message #32101: Antenna Control Status Report

4.21.10 Message #32102: Antenna Position Report.
This message shall be used to report the local antenna position and control
command and the remote antenna location and movement.
1 - B - 258
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32102.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
32102.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32102.02
Pedestal Index
Unsigned 1
Enumerated

0503.07
Reported Antenna
Azimuth
Integer 2
BAM
No Restrictions
0503.08
Reported Antenna
Elevation
Integer 2
BAM
-/2 x /2
0503.09
Reported Azimuth Slew

Rate
Integer 2
0.0001 rad/s
- x
Integer 2
0.0001 rad/s
- x
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions

control mode.
0503.10
Reported Elevation Slew

Rate
control mode
32102.07
Reported Remote
Antenna Latitude
WGS-84
32102.08
Reported Remote
Antenna Longitude
WGS-84
32102.09
Reported Remote
Antenna Altitude
Integer 3
0.02 m
-1,000 x 100,000
32102.13
10
Altitude Type
Unsigned 1
Enumerated
1 = Baro Altitude
2 = AGL
3 = WGS-84

message.
32102.10
11
Reported Remote
Antenna Ground Speed
Unsigned 2
0.05 m/s
No Restrictions
32102.11
12
Reported Remote
Antenna Course
Integer 2
BAM
No Restrictions
32102.12
13
Reported Remote
Antenna Vertical Speed
Integer 2
0.05 m/s
No Restrictions
Platform Dependent
Table B1 - 165: Message #32102: Antenna Position Report
1 - B - 259
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.21.11 Message #32103: Legacy Pedestal Status Report.
of the ADT and/or GDT pedestal. This message is to support backwards compatibility
to Edition 2.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32103.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
32103.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0503.05
Addressed Pedestal
Unsigned 1
Enumerated
0 = GDT
1 = ADT
0503.06
Pedestal Mode State
Unsigned 1
Enumerated
0 = Turn Off
1 = Turn On
2 = Go To Standby
3 = Deploy
4 = Stow
5 = Manual - Position
6 = Manual - Rate
7 = Acquire (Search)
8 = Track (Auto)
0503.07
Reported antenna
azimuth
Float
rad
0 x 2
Float
rad
-/2 x /2
Relative to True North

0503.08
Reported antenna
elevation
Relative to local horizontal
0503.09
Reported Antenna
Azimuth Slew rate
Float
rad/s
- x
0503.10
Reported Antenna
Elevation Slew rate
Float
rad/s
- x
0503.11
Reported GDT Latitude
Float
rad
-/2 x /2
Float
rad
- x
Float
-1,000 x 100,000
Not applicable to ADT.

0503.12
Reported GDT Longitude

0503.13
10
Reported GDT Altitude

Table B1 - 166: Message #32103: Legacy Pedestal Status Report

4.21.12 Message #32200: Link Health Status.
This message shall be used by the VSM to report to the CUCS the link health.
1 - B - 260
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32200.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32200.02
Bit Mode Status
Unsigned 1
Enumerated
0 = Off (Abort)
1 = Running BIT
2 = BIT Passed
3 = BIT Failed
4 - 255 = Link Specific
Table B1 - 167: Message #32200: Link Health Status

4.21.13 Message #32201: Data Link Fallback Status.
This message shall be used to report the fallback status of the data link.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32201.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32201.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32201.02
Fallback Status
Unsigned 1
Enumerated
0 = Normal
1 = Fall Back in Progress
2 = Fallback Failed
3 = Fallback Successful
Table B1 - 168: Message #32201: Data Link Fallback Status

4.21.14 Message #32300: Data Link UDP Count.
This message shall be used to report the number of UDP messages received by the
data link. The period that the messages are counted is defined by Message #30300,
Set Data Link UDP Monitor Period. The message reports the number of messages
for the last complete period measured and not the current period being measured.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32300.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
32300.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32300.02
UDP Message Count
Unsigned 2
None
No Restrictions
Defines the number of UDP

messages received and
processed by this data link.
65535 = at least 65535
messages received during
the monitor period.
Table B1 - 169: Message #32300: Data Link UDP Count
1 - B - 261
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.21.15 Message #32301: AV IP Disclosure Message.
This message shall be sent by the air vehicle to inform a CUCS of the data streams
in the data uplink and downlink. The primary goal is to inform the receiving entity of
what is present in the AV uplink and downlink and how to connect to those streams.
Those streams include, but are not limited to, bidirectional DLI, bidirectional audio
and unidirectional payload data.
This message shall be sent from the air vehicle on a universal multicast IP address
and port (e.g. 225.200.1.0:51017). It shall be sent once for each stream since a
station (or the AV) may have multiple streams available.
This message shall be sent by the Control Data Link (CDT) to inform the local
controlling processor (e.g. CUCS) of the DLI data streams used to control the CDT.
This message will also indicate the IP routing the CDT will use to send/receive nonCDT data to/from the AV. Those non-CDT data streams include, but are not limited
to, bidirectional DLI for the AV and ADT, bidirectional audio and unidirectional
payload data.
This message shall be sent by the CDT on a different universal multicast IP address
and port than used by the AV (x.x.x.x:x).
Additional detail on the streams will have to be pulled from the streams themselves
(e.g., the KLV portion of the video downlink streams).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32301.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
32301.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
32301.02
Controlled Station 116
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 262
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32301.07
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
None
No Restrictions
Station Location
32301.08
Sub-Component
Number
Component Location
32301.05
Stream ID
1 - B - 263
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
32301.06
Stream N Type
Unsigned 1
Enumerated
0 = AV DLI Uplink
1 = AV DLI Downlink
2 = Data Link DLI Uplink
3 = Data Link DLI Downlink
4 = EO or IR Payload Full Motion
Video (FMV) (live, from this AV)
5 = EO Payload Full Motion Video
(FMV) (live, from this AV)
6 = IR Payload Full Motion Video
(FMV) (live, from this AV)
7 = EO/IR Stills (WAS or other,
from this AV)
8 = SAR Stills (from this AV)
9 = GMTI FMV (live, from this AV)
10 = Pilot View Camera FMV (live,
from this AV)
11 = ATC Audio - Uplink
12 = ATC Audio - Downlink
13 = Tactical Audio - Uplink
14 = Tactical Audio - Downlink
15 = Tactical Comm Relay (nonaudio/wide distribution)
16 = AV DLI Uplink - Relay (live,
but relayed through this AV)
17 = AV DLI Downlink - Relay
(live, but relayed through this AV)
18 = EO or IR Full Motion Video
(FMV) - Relay (live, but relayed
through this AV)
19 = EO Payload Full Motion
Video (FMV) - Relay (live, but
relayed through this AV)
20 = IR Payload Full Motion Video
(FMV) - Relay (live, but relayed
through this AV)
21 = EO/IR Stills - Relay (WAS or
other, live, but relayed through this
UA)
22 = SAR Stills - Relay (live, but
relayed through this UA)
23 = GMTI FMV - Relay (live, but
relayed through this AV)
24 = Pilot View Camera FMV Relay (live, but relayed through
this AV)
25 = EO/IR FMV (stored/replayed)
26 = CBRNE Data
27 = SIGINT Data
28 - 36 = Reserved
37 - 255 = System Specific
32301.07
Length of URI
Unsigned 1
None
1x
32301.08
Uniform Resource
Identifier
Character
["Length of
URI"]
None
No Restrictions
1 - B - 264
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
32301.09
Data Element Name &

Description
Controlled Station
17-32
Type
Units
Range
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 170: Message #32301: AV IP Disclosure Message

4.22 Data Link Transition Messages.
The messages in this section allow the CUCS to control the data links and receive
the status of the data links. These messages also support air vehicle handover.
4.22.1 Message #34000: Vehicle Data Link Transition Coordination Message.
This message shall be used to establish a new data link configuration when
transferring from one UCS data link to another UCS data link and is sent by the
giving CUCS. .
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
34000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
0600.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0600.04
Data Link ID
Integer 4
None
See Section 1.7.6
VDT data link ID for air

vehicle transition
0600.05
Acquiring CUCS ID
Integer 4
None
See Section 1.7.6
34000.04

Part 1
Composite 1
None
No Restrictions

4.1
7085 Annex
Unsigned
Bits 2
Enumerated
0 = Annex B
1 = Annex C
4.2
7085 Appendix
Unsigned
Bits 2
Enumerated
0 = Appendix 1
1 - B - 265
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
4.3
7085 Implementation
Unsigned
Bits 4
Enumerated
Unsigned 1
Enumerated

7085, Annex P
Unsigned 2
0.5 MHz
No Restrictions
Unsigned 2
0.5 MHz
No Restrictions

P
34000.05

Part 2
0600.06

Carrier Frequency (VDT)
value.
Link Dependent
(bias = 9,000 MHz)
0600.07

Carrier Frequency (VDT)
value.
Link Dependent
(bias = 9,000 MHz)
0600.08
Set PN Code (VDT)
Unsigned 1
None
No Restrictions
0600.09
Acquiring CDT Latitude
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
WGS-84
0600.10
10
Acquiring CDT Longitude

WGS-84
0600.11
11
Acquiring CDT Altitude
Integer 3
0.02 m
-1,000 x 100,000
0600.12
12
Data Link Time-out Limit
Unsigned 2
0.1 s
No Restrictions
Unsigned 1
Enumerated
0 - 255 = See Table B1-35
Unsigned 2
Enumerated
0 = Abort data link

transition. Non-zero
indicates duration.
34000.01
13
Acquiring CUCS Type

CUCS; Numbers to be
assigned by STANAG
Custodian.
34000.02
14
Acquiring CUCS Subtype

the manufacturer.
1 - B - 266
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
34000.03
15
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 171: Message #34000: Vehicle Data Link Transition Coordination

Message
4.22.2 Message #35000: Handover Status Report.
This message shall be used to report the status of the handover procedure.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
35000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
0700.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
0700.04
Acquiring CUCS ID
Integer 4
None
See Section 1.7.6
0700.05
Status
Unsigned 1
Enumerated
0 = Handover not
Requested
1 = Handover in Progress
2 = Handover Successful
3 = Handover Failed
0700.06
Air Data Link ID
Integer 4
None
See Section 1.7.6
Data link ID for air vehicle

transition
Table B1 - 172: Message #35000: Handover Status Report

4.23 Autonomy Messages.
4.23.1 Message #36000: Activity Constraint Message.
The Activity Constraint Message, Message #36000, shall be used to communicate
requested autonomous goals and behaviour constraints from the CUCS to the VSM.
Each constraint shall be provided with a unique identifier by the CUCS so that it may
be referenced by the VSM to indicate which constraints are able to be met and which
constraints are not able to be met. In combination with the constraint response
message below, the unique constraint identifier enables the system to provide
feedback describing why a particular constraint or set of constraints for an activity
cannot be met. The system shall execute an activity if and only if all constraints
associated with the activity are satisfied.
The following time window constraints may be specified using Message # 36000:
Waypoint constraints, before, after or concurrent (field 6, values 6 8)

o
Example: Between ten and twenty seconds before waypoint six
Example: Between ten and twenty seconds after waypoint six
1 - B - 267
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Example: Between ten seconds before and five seconds after
reaching waypoint six
Absolute time constraints, before, after or concurrent (field 6, values 3 5)

o
Example: Between ten and twenty seconds before a specific time
Example: Between ten and twenty seconds after a specific time
Example: Between ten seconds before and five seconds after a specific time
Relative to other constraints, before, after or concurrent (field 6, values 0 2)

o
Example: Between ten and twenty seconds before satisfying

constraint 37
Example: Between ten and twenty seconds after satisfying constraint

37
Example: Between ten seconds before and ten seconds after

satisfying constraint 37
Conditioned on a contingency level occurring (field 6, values 9, 10)

o
Example: If contingency type "A" occurs squawk a different IFF code
Example: If contingency type "B" occurs turn on the landing lights
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
36000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
36000.03
Constraint ID
Unsigned 3
None
1x
Unsigned 1
Enumerated
0 = Before Constraint
1 = After Constraint
2 = Concurrent Constraint
3 = Before Time
4 = After Time
5 = Concurrent Time
6 = Before Waypoint
7 = After Waypoint
8 = Concurrent with Arrival
at Waypoint, or Start of
Loiter at AV Loiter Point
9 = If Contingency Type "A"
Occurs
10 = If Contingency Type
"B" Occurs
A unique identifier for this

constraint
36000.04
Constraint Timing or
Condition
behaviours and constraints
1 - B - 268
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36000.05
Timing Start
Unsigned 3
No Restrictions
Unsigned 3
No Restrictions
Unsigned 3
None
1x
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 1
None
x 100
Unsigned 3
None
1x
Used to identify the start

time of a constraint time
window, relative to a
waypoint, start of loiter at
an AV loiter waypoint, an
absolute time, or another
constraint
36000.06
Timing End
Used to identify the end
time of a constraint time
window, relative to a
waypoint, start of loiter at
an AV loiter waypoint, an
absolute time, or another
constraint
36000.07
Referenced Constraint or
Waypoint ID
waypoint or other constraint
that this constraint is
relative to; used if field 3
has a value of 0, 1, 2, 6, 7,
or 8
36000.08
Constraint Time
constraint is relative to;
used if field 6 has a value of
3, 4, or 5
36000.09
Relative Priority
Used to identify which
constraints are more
important than others;
higher priority is more
important
36000.02
Activity ID
Identifies the activity with
(non-zero activity ID) to
which this constraint is to
be applied
Table B1 - 173: Message #36000: Activity Constraint Message

4.23.2 Message #36001: Constraint Response Message.
The Constraint Response Message, Message #36001, shall be sent from the VSM to
the CUCS. It shall be used to communicate the ability of the VSM/air vehicle to meet
the requested autonomous goals and behaviour constraints received by the VSM in
Message #36000. For each constraint (Message #36000) received by the VSM, the
1 - B - 269
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
VSM shall produce a constraint response (Message #36001) indicating whether or
not the constraint will be satisfied.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
36001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
36001.02
Constraint ID or Area ID
Unsigned 3
None
1x
Unsigned 1
Enumerated
0 = Satisfied
1 = Unsupported
2 = Priority Failure
3 = Resource Unavailable
4 = Time Constraint Failure
5 = Computing Complexity
Failure
6 = Consistency Failure
7 = Auto-Router Failure
8 = Unknown Failure
9 = Vehicle Specific Failure
10 = Area Violation
11 = Illegal Area
Specification
12 - 255 = Reserved
Identifies the constraint that

will be satisfied or that has
failed, or the area that has
been violated if field 3 value
= 10 or 11.
36001.03
Constraint Response
Used indicate whether or
not the constraint will be
satisfied
Table B1 - 174: Message #36001: Constraint Response Message

4.23.3 Message #36002: Constraint Requests Complete Message.
The Constraint Requests Complete Message, Message #36002, shall be sent from
the CUCS to the VSM after the CUCS has sent all activity constraints. It shall be
used to indicate to the VSM that it should begin processing all constrained activity
and should produce constraint responses using one message (Message #36001) for
each Message #36000 received. After all constraint responses have been sent by
the VSM, the VSM shall send Message #36003, Constraint Responses Complete
Message (see below) to indicate to the CUCS that all constraints have been
processed.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
36002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
Table B1 - 175: Message #36002: Constraint Requests Complete Message

4.23.4 Message #36003: Constraint Responses Complete Message.
The Constraint Responses Complete Message, Message #36003, shall be sent from
the VSM to the CUCS after the VSM has sent all constraint responses to the CUCS.
It shall be used to indicate to the CUCS that all constraints have been processed.
1 - B - 270
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
36003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
Table B1 - 176: Message #36003: Constraint Responses Complete Message

4.23.5 Message #36100: Activity Complete Message.
The Activity Complete Message, Message #36100, shall be sent from the VSM to the
CUCS after the vehicle, payload or data link has completed an activity.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36100.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
36100.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
36100.02
Activity ID
Unsigned 3
None
1x
Activity ID that has been

completed by the AV,
payload or data link.
Table B1 - 177: Message #36100: Activity Complete Message

4.23.6 Message #36200: Activity Status Message.
The Activity Status Message, Message #36200, shall be sent from the VSM to the
CUCS at least once for each activity whose constraints are satisfied as described in
Message #36001. The VSM shall send Message #36200 when the activity status
changes to notify the CUCS that the activity will occur at a different estimated time or
enroute to a different waypoint.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36200.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
36200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
36200.03
Timing Start
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 5
0.001 s
See Section 1.7.2
Unsigned 2
None
1x

estimated absolute start
time of the activity in field 4
36200.04
Timing End
estimated absolute end
time of the activity in field 4
36200.05
Enroute Waypoint ID
waypoint that the vehicle
will be flying toward, or the
AV Loiter waypoint the
vehicle will be loitering at
when the activity in field 4 is
started
1 - B - 271
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
36200.02
Activity ID
Unsigned 3
None
1x
Table B1 - 178: Message #36200: Activity Status Message

4.24 General Preconnection Configuration Messages.
Upon initial connection with a VSM, after establishment (via Message #3) of vehicle
type and vehicle subtype, an optional configuration process may be utilized to
configure the CUCS. This configuration process will use a file in lieu of the
configuration commands directly from the air vehicle. If this option is utilized, it
eliminates the need to send the configuration messages to configure the CUCS for
the air vehicle.
The binary-formatted file will contain the messages as they would be received from
the VSM / air vehicle directly via UDP. The first message in the file shall be Message
#3, with the following fields required: 3 (Vehicle Type), 4 (Vehicle Subtype) & 5
(Owning ID). Following Message #3 will be further messages, in the same binary
format, for the particular air vehicles configuration and setup.
If the file for the air vehicle type, subtype or Owning ID, or if the checksum provided
in Message #3 received from the air vehicle does not match the checksum of the file
local to the CUCS, the VSM / air vehicle and CUCS configuration shall continue as
defined below.
4.24.1 Message #40000: Field Configuration Request.
This message shall be used by the CUCS to initiate and, if required, abort the
transmission of the DLI field related configuration parameter information from the
VSM, vehicle or data link, for a specified LOI, for a specified data link ID, vehicle ID
(specific or logical) or specific payload station, or to request the configuration of a
single parameter. The CUCS uses this message to update DLI parameter
configuration data at the CUCS, and to potentially control the display of information.
The VSM, vehicle or data link shall respond with one or more Field Configuration
Integer Response (Message #41000) message(s), Field Configuration Float
Response (Message #41001) message(s), Field Configuration Enumerated
Response (Message #41002) message(s) or Field Configuration Unsigned Response
(Message #41003) message(s) with the static configuration for each of the
configuration items specified in this document that are supported by the VSM.
The Field Configuration Request message shall be able to be transmitted from a
CUCS to a VSM without an authorized connection as it is used to request
configuration in advance of requesting a connection in order to prepare the CUCS for
the connection.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
40000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1200.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 272
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
40000.07
Request LOI
Unsigned 1
Bitmapped
0x01 = NA
0x02 = LOI 2
0x04 = LOI 3
0x08 = LOI 4
0x10 = LOI 5
0x80 = Data Link
0x00 = N/A
Bit 0x80 added for
Edition 2.
1200.06
Request Type
Unsigned 1
Enumerated
0 = Single Parameter
1 = Monitor
2 = Control
3 = Abort Configuration
1200.07
Requested Message
Unsigned 2
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
0 = N/A
1200.08
Requested Field
0 = N/A
1200.09
Station Number 1-16

40000.01
Component Number
Station Location
1 - B - 273
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
40000.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Component Location
1200.10
Sensor Select
Unsigned 1
Enumerated
0 = N/A
1 = Sensor 1
2 = Sensor 2
3 = Sensor 3
40000.04
10
Vehicle Type
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 3
None
No Restrictions
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

assigned by STANAG
Custodian.
40000.05
11
Vehicle Subtype
the manufacturer.
40000.06
12
Activity ID
40000.03
13
Table B1 - 179: Message #40000: Field Configuration Request
1 - B - 274
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.24.2 Message #41000: Field Configuration Integer Response.
This message shall be transmitted from the VSM/ vehicle/ Data Link to the CUCS
after the reception of Message #40000 as required for each of the parameters within
the list (below) that are required per a single parameter, monitor, or control
configuration request, and supported by the VSM for the Station Number. i.e.;
based on the Request type and Station Number fields in the Message #40000
configuration request.
This message shall be transmitted from the VSM/ vehicle/ Data Link to the CUCS in
direct response to a Message #40000 for a single parameter request from the CUCS
if configuration information is available for the requested parameter. Where the
VSM/ vehicle/ data link does not support a requested parameter, this message shall
be sent with the Field Supported parameter filled as Field Not Supported.
Where the Message #40000, Request Type, field is set to an LOI for monitoring,
only parameters from status messages that are applicable to the Message #40000,
Station Number, field shall be required to be sent from the VSM/ AV/ Data Link. e.g.;
Message #3002, is an AV status message therefore parameter Message #3002,
Power Level is Station Number equal to AV platform, Request Type equal to monitor
parameter required in response to such a configuration request.
Where the Message #40000, Request Type, field is set to an LOI for controlling,
parameters from both control and status messages that are applicable to the
Message #40000, Station Number, field shall be required to be sent from the VSM/
AV/ Data Link.
For CUCS commanded values, this message shall define the level of support
provided to the CUCS for control over a specified commanded DLI message
parameter of size Integer, by the VSM/ vehicle/ Data Link filling in the message for
the requested parameter and transmitting it to the CUCS.
For VSM/ vehicle/ Data Link reported values, this message shall define the level of
support provided for the reporting of a DLI message parameter, of size Integer, by
the VSM/ vehicle/ Data Link filling in the message for the requested parameter and
transmitting it to the CUCS.
This message may be sent from the VSM to the CUCS after the Configuration
Complete Message, Message #41005 has been sent to change the following
attributes of a field:
- Min Value
- Max Value
- Min Display Value
- Max Display Value
- Minimum Display Resolution
- All warning and caution limits
- Help Text
The CUCS will use this information to configure the display and control of VSM data
elements. The Default Value field shall be used by the CUCS to define the initial
state of the displayed field. If no configuration message is received by the CUCS
during the VSM response(s) to Message #40000, the CUCS will display the field with
its full range enabled.
1 - B - 275
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Where the VSM/ vehicle/ data link uses this message to report a DLI message
parameter, the CUCS shall present the Cautions and Warnings to the operator in
accordance with the message for the specified parameter. The High Caution Limit
and Low Caution limit shall be equivalent to Message #16000, Priority enumeration
of Caution. The High Warning Limit and Low Warning limit shall be equivalent to
Message #16000, Priority enumeration of Warning. The VSM shall not present
these same warnings.
The CUCS, as a minimum, shall support the reception of the following DLI message
parameters from a VSM/ vehicle/ data link:
Message #2002, Altimeter Setting
Message #2004, Altitude Change Behaviour
Message #2010, Lateral Stick
Message #2010, Longitudinal Stick
Message #2010, Rotational Stick (Rudder)
Message #2010, Throttle Stick - Engine 1
Message #2010, Pitch Stick - Engine 1
Message #2010, Taxi Stick
Message #2011, Area ID
Message #2112, Area ID
Message #2014, Contingency A Delay
Message #2014, Contingency A Waypoint Number
Message #2014, Contingency B Delay
Message #2014, Contingency B Waypoint Number
Message #2015, Energy Storage Unit ID
Message #3002, Power Level
Message #3002, Flap Deployment Angle
Message #3002, Speed Brake Deployment Angle
Message #3007, Engine Temperature 1
Message #3007, Engine Speed 1
1 - B - 276
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #3007, Engine Pressure 1

Message #3007, Engine Speed 2
Message #3007, Engine Pressure 2
Message #3007, Engine Speed 3 Message #3009, Altimeter Setting
Message #3011, Lateral Stick
Message #3011, Longitudinal Stick
Message #3011, Rotational Stick (Rudder)
Message #3011, Taxi Stick
Message #9001, DME
Message #9001, LOC
Message #9001, Glide Slope
Message #11000, Flap Deployment Command
Message #11000, Speed Brake Deployment Command
Message #12001, Bus ID
Message #13002, Waypoint Number
Message #13004, Horizontal Field of View
Message #13004, Vertical Field of View
Message #19400, RF Power Level - Radio A
Message #19400, RF Power Level - Radio B
Message #19400, Select Stored Configuration Number, Radio A
Message #19400, Select Stored Configuration Number, Radio B
Message #19401, Configuration Number
Message #19401, Frequency
Message #19401, Hop ID
Message #30001, Select Channel
Message #30001, Select Primary Hop Pattern
Message #30001, Set PN Code
Message #30001, Set Forward Link (FL) Carrier Frequency
1 - B - 277
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #30001, Set Return Link (RL) Carrier Frequency
Message #30002, Set Forward Link (FL) Carrier Frequency
Message #30002, Set Return Link (RL) Carrier Frequency
Message #30102, Set Antenna Elevation
Message #30102, Set Azimuth Slew Rate
Message #30102, Set Elevation Slew Rate
Message #32001, Reported Forward Link (FL) Carrier Frequency
Message #32001, Reported Return Link (RL) Carrier Frequency
Message #32002, Reported Forward Link (FL) Carrier Frequency
Message #32002, Reported Return Link (RL) Carrier Frequency
Message #32300, Reported Antenna Elevation
Message #32300, Reported Azimuth Slew Rate
Message #32300, Reported Elevation Slew Rate
For bit fields, e.g. 0x0001, 0x0002, 0x0004, 0x0008, the right most bit (0x0001) shall
be considered Enumeration Index 0.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41000.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
1300.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1300.04
VSM ID
Integer 4
None
See Section 1.7.6
1300.05
Data Link ID
Integer 4
None
See Section 1.7.6
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
0 = N/A
1300.06
Station Number 1-16

1 - B - 278
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41000.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Station Location
41000.02
Component Location
1300.07
Requested Message
Unsigned 4
None
No Restrictions
1300.08
Requested Field
Unsigned 1
None
No Restrictions
If Requested Field = 0, then

the entire message is not
supported.
1300.09
Field Supported
Unsigned 1
Enumerated
0 = Field Not Supported

1 = Field Supported
41000.03
10
Default Value
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
See Field In Requested

Message
1300.10
11
Max Value
Message
1300.11
12
Min Value
Message
1 - B - 279
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1300.12
13
Max Display Value
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Integer 4
See Field In
Requested
Message
No Restrictions
Character 80
None
No Restrictions

Message
1300.13
14
Min Display Value

Message
1300.14
15
Minimum Display
Resolution
Message
1300.15
16
High Caution Limit

Minimum value that will
cause a Caution
Message
1300.16
17
High Warning Limit

cause a Warning
Message
1300.17
18
Low Caution Limit

Maximum value that will
cause a Caution
Message
1300.18
19
Low Warning Limit

cause a Warning
Message
1300.19
20
Help Text
1 - B - 280
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1300.20
21
Subsystem ID
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
5 = Navigation
6 = Payload
7 = Recovery System
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 18 = Reserved 12-19
19 = Not Assigned
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight
0x08 = Contingency A
0x10 = Contingency B
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Identifier subsystem for

which this field is
associated
1300.21
22
Route Type
Identifies which route
type(s) this configuration
applies for mission
messages
41000.03
23
Table B1 - 180: Message #41000: Field Configuration Integer Response

4.24.3 Message #41001: Field Configuration Float Response.
This message shall be transmitted from the VSM/ vehicle/ Data Link to the CUCS in
direct response to a Message #40000 for a single parameter request from the CUCS,
if configuration information is available for the requested parameter. Where the VSM
1 - B - 281
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
does not support a DLI message parameter, this message shall be sent with the
Field Supported parameter filled as Field Not Supported.
Station Number, field shall be required to be sent from the VSM/ AV/ Data Link.
parameters from both the control and status messages that are applicable to the
AV/ Data Link. e.g.; Message #2002 is a control message for the Station Number of
AV platform, therefore parameter Message #2002, Commanded Altitude is a control
parameter required in response to a configuration request, Request Type of control,
for the Station Number of AV platform.
parameter, of size float, by the VSM/ vehicle/ Data Link filling in the message for the
requested DLI message parameter(s) and transmitting it to the CUCS.
For VSM/ vehicle/ Data Link reported values, this message shall define the level of
support provided for the reporting of a DLI message parameter, of size float, by the
VSM/ vehicle/ Data Link filling in the message for the requested parameter and
transmitting it to the CUCS.
This message may be sent from the VSM to the CUCS after the Configuration
Complete Message #41005 has been sent to change the following attributes of a
field:
- Min Value
- Max Value
- Min Display Value
- Max Display Value
- Minimum Display Resolution
- All warning and caution limits
- Help Text
elements. The Default Value field shall be used by the CUCS to define the initial
state of the displayed field. If no configuration message is received by the CUCS
during the VSM response(s) to Message #40000, the CUCS will display the field with
its full range enabled.
In the list (below), the configuration or support of some parameters is dependent on
the configuration of others parameters within this list or within the lists contained in
the other configuration messages.
This is to ensure consistency between
parameters for similar functionality (such as the Message #2002, Commanded
Altitude and Message #2004, Loiter Altitude), there are parameters not required to be
reported by the VSM to the CUCS as part of the configuration process, as these
parameters are to have the same configuration (some of these parameters are
identified in the list below). Note, where parameters are not contained on the list,
such as reported values or reported commanded values, these reports should use
the same configuration of their associated command data element contained in the
1 - B - 282
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
list. This means for example, that a reported altitude parameter uses the same
configuration as the commanded altitude parameter.
these same warnings on to the operator.
Message #2004, Loiter Radius
Message #2004, Loiter Length
Message #2004, Loiter Altitude uses the Message #2002, Commanded
Altitude configuration
Message #2004, Loiter Speed uses the Message #2002, Commanded
Speed configuration
Message #2002, Heading Reference
Message #2002, Commanded Altitude the configuration for this parameter
is from this message, but the support for this parameter is dependent on the
Message #2002, Altitude Command Type of Altitude and "Rate-limited
attitude" being supported
o i.e.; if Message #2002, Altitude Command Type Altitude and
"Rate-limited attitude" is not supported (see Message #44003),
this parameter is not supported
Message #2002, Commanded Vertical Speed the configuration for this
parameter is from this message, but the support for this parameter is
dependent on the Message #2002, Altitude Command Type of Altitude Rate
being supported.
o i.e.; if Message #2002, Altitude Command Type Altitude rate is
not supported (see Message #44003), this parameter is not
supported.
Message #2002, Commanded Turn Rate
Message #2002, Commanded Roll Rate
Message #2002, Commanded Speed
Message #2002, Commanded Roll
Message #3002, Current Propulsion Energy Level
Message #3002, Current Propulsion Energy Usage Rate
Message #3007, Engine Speed
Message #3009, Angle of Attack
Message #3009, Angle of Sideslip
Message #3009, Indicated Airspeed
1 - B - 283
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #3009, True Airspeed

Message #3009, Outside Air Temperature
Message #3009, Barometric Altitude
Message #3009, Barometric Altitude Rate
Message #3009, U_Ground
Message #3009, V_Ground
Message #3010, X_Body_Accel
Message #3010, Y_Body_Accel
Message #3010, Z_Body_Accel
Message #3010, Roll_Rate
Message #3010, Pitch_Rate
Message #3010, Yaw_Rate
Message #4000, Altitude
Message #4000, Phi (Roll)
Message #4000, Theta (Pitch)
Message #4000, Phi_dot (Roll Rate)
Message #4000, Theta_dot (Pitch Rate)
Message #4000, Psi_dot (Yaw Rate)
Message #4000, U_Speed
Message #4000, V_Speed
Message #4000, W_Speed
Message #4000, U_Accel
Message #4000, V_Accel
Message #4000, W_Accel
Message #7000, Voice Transmit Enable
Message #9000, Voice Transmit Enabled
Message #13002, Waypoint to Speed
Message #13002, Waypoint to Altitude
Message #13003 Loiter Radius
Message #19001, Set Horizontal Field of View uses the Message #301
configuration
Message #19001, Set Vertical Field of View uses the Message #301
configuration
Message #19001, Horizontal Slew Rate
Message #19001, Vertical Slew Rate
1 - B - 284
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #19001, Altitude

Message #21101, Reported Range
Message #30001, Set Forward Link Carrier Frequency
Message #30001, Set Return Link Carrier Frequency
Message #30003, Set Antenna Azimuth this parameter is not configured
using this message, this message is only used to identify if this parameter
is supported by the VSM.
Message #30003, Set Azimuth Offset this parameter is not configured
Message #30003, Set Elevation Offset this parameter is not configured
Message #30003, Set Antenna Elevation
Message #30003, Set Azimuth Slew Rate
Message #30003, Set Elevation Slew Rate
Message #30004, Set CDT Altitude
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41001.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
1301.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1301.04
VSM ID
Integer 4
None
See Section 1.7.6
1301.05
Data Link ID
Integer 4
None
See Section 1.7.6
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
0 = N/A
1301.06
Station Number 1-16

1 - B - 285
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41001.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 4
None
No Restrictions
Unsigned 1
None
No Restrictions
Station Location
41001.02
Component Location
1301.07
Requested Message
0 = N/A
1301.08
Requested Field
supported.
1301.09
Field Supported
Unsigned 1
Enumerated

1 = Field Supported
41001.03
10
Default Value
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions

Message
1301.10
11
Max Value
Message
1301.11
12
Min Value
Message
1 - B - 286
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1301.12
13
Max Display Value
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Float
See Field In
Requested
Message
No Restrictions
Character 80
None
No Restrictions

Message
1301.13
14
Min Display Value

Message
1301.14
15
Minimum Resolution
Message
1301.15
16
High Caution Limit

cause a Caution
Message
1301.16
17
High Warning Limit

cause a Warning
Message
1301.17
18
Low Caution Limit

cause a Caution
Message
1301.18
19
Low Warning Limit

cause a Warning
Message
1301.19
20
Help Text
1 - B - 287
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1301.20
21
Subsystem ID
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
5 = Navigation
6 = Payload
7 = Recovery System
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 18 = Reserved 12-19
19 = Not Assigned
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

which this field is
associated
1301.21
22
Route Type
applies for mission
messages
41001.04
23
Table B1 - 181: Message #41001: Field Configuration Float Response

4.24.4 Message #41002: Field Configuration Enumerated Response.
This message shall be transmitted from the VSM/vehicle/Data Link to the CUCS after
the reception of Message #40000 as required for the parameters within the list
(below) that are required per a single parameter, monitor, or control configuration
request, and supported by the VSM for the Station Number. i.e.; based on the
Request type and Station Number fields in the Message #40000 configuration
request.
This message shall report when an enumerated parameter is supported in part by
removing unsupported generic enumerations from an enumerated or bitmapped
message field. i.e.; if not all the enumerations/ bit fields in an enumerated/ bit
1 - B - 288
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
mapped field are supported by the AV/VSM, they are identified by instances of this
message in response to the Message #40000 configuration request.
This message provides the capability to configure enumerated fields where there is
no generic enumerated listing for the parameter, or to extend the set of enumerated
values where vehicle specific values are available. Where an enumerated field
contains a vehicle (payload) specific or VSM specific listing and a VSM/vehicle/data
link requires using this capability, this message shall be used by the
VSM/vehicle/data Link to extend that listing. This message shall not be used to alter
a generic enumerated listing. Reserved and specific enumerations (e.g., payload
specific), that are not defined are assumed to be undefined and not enabled.
Note, one such message is required to remove each unsupported generic
enumeration within an enumerated field, and one such message is required to add a
single vehicle (payload) specific enumeration to an enumerated field.
This message shall be transmitted from the VSM/vehicle/data Link to the CUCS in
direct response to a Message #40000 for a single parameter request from the CUCS,
if configuration information is available for the requested parameter. Where the VSM
does not support the DLI message parameter, this message shall be sent with the
Field Supported parameter filled as Field Not Supported.
Station Number, field shall be required to be sent from the VSM/ AV/ Data Link.
parameters from both the control and status messages that are applicable to the
AV/ Data Link. e.g.; Message #2001 is a control message for the Station Number of
AV platform, therefore parameter Message #2001, Select Flight Path Control Mode,
is a control parameter required in response to a configuration request of Request
Type control, for the Station Number of AV platform. Using this example, the AV/
VSM would send Message #41002 for any Message #2001, Select Flight Path
Control Mode, generic enumerations that it does not support and to potentially add
vehicle specific flight modes.
parameter, of size float, by the VSM/vehicle/data link filling in the message for the
requested DLI message parameter(s) and transmitting it to the CUCS.
For VSM/vehicle/data link reported values, this message shall define the level of
support provided for the reporting of a DLI message parameter, of size float, by the
VSM/vehicle/ data link filling in the message for the requested parameter and
transmitting it to the CUCS. The addition of an enumeration to a reported
enumeration field does not add that enumeration to the corresponding command
field, if present. Reporting an enumeration that is only defined in the reported field
does not change the related commanded field state, if present.
The CUCS shall use this message to configure the User Interface for the display or
control of VSM/vehicle/data link information. The Default Value field shall be used
by the CUCS to define the initial state of the displayed field. If no configuration
1 - B - 289
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
message is received by the CUCS during the VSM response(s) to Message #40000,
the CUCS will display the field with its full range enabled.
parameters from a VSM/vehicle/data link:
Message #1, Requested Flight Mode
Message #2001, Select Flight Path Control Mode
Message #2002, Altitude Command Type
Message #2002, Heading Command Type
Message #2002, Speed Type
Message #2002, Altitude Type
Message #2003, Altitude Mode
Message #2003, Speed Mode
Message #2003, Heading Mode
Message #2004, Loiter Type
Message #2004, Loiter Direction
Message #2004, Flying Behaviour
Message #2005, Flight Termination Mode
Message #2007, Set Lights
Message #2008, Engine Command
Message #2011, Area Upload Mode
Message #2012, Polygon Type
Message #2014, Contingency A Command
Message #2014, Contingency B Command
Message #6000, Mode 2 Code
Message #9001, LOC/Glide Slope Valid
Message #9001, Marker
Message #11000; Landing Gear Command
Message #13000, Mission Plan Mode
Message #13002, Waypoint Altitude Type
1 - B - 290
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #13002, Waypoint Speed Type

Message #13002, Turn Type
Message #13003, Waypoint Loiter type
Message #13004, Set Sensor Pointing Mode
Message #13004 Set Sensor 1 Mode
Message #13004, Set Sensor 2 Mode
Message #13004, Set Sensor Output
Message #13004, Starepoint Altitude Type
Message #13004, Sensor Mode
Message #13004, EO Sensor Mode
Message #13004, IR Polarity
Message #13005, Function
Message #13005, Enumerated State
Message #13007, Contingency Condition
Message #15000, Subsystem ID
Message #16000, Subsystem ID Note: Not implemented with Message
#41002, use Message #15000, Subsystem ID configuration
Message #16001, Subsystem ID Note: Not implemented with Message
#41002, use Message #15000, Subsystem ID configuration
Message #18000, PTT
Message #19001, Set Zoom
Message #19001, Tracker Mode Command
Message #19100, Set EO Sensor Mode
Message #19100, Select IR Temperature
Message #19100, Set EO/IR Pointing Mode
Message #19100, Focus Type
Message #19100, Set IR Level Adjustment Mode
Message #19100, Set IR Polarity
Message #19100, Initiate Laser Designator
Message #19100, Laser Mode
Message #19200, Set MTI Radar Mode
Message #19200, Set SAR Mode
Message #19300, Active Weapon Mode Command
Message #19300, Active Target Acquisition Mode Select
1 - B - 291
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #19300, Active Attack Mode
Message #19300, Target Altitude Type
Message #19400, Power
Message #19400, Set Mode
Message #19400, Initiate BIT
Message #19500, Set Recording Index Type
Message #19500, Set Recording Mode
Message #21101, IR Temperature Status
Message #21400, Power
Message #21400, Mode Status
Message #21400, BIT Status
Message #28001, Data Link Type
Message #28001, Antenna Type
Message #30001, Set Configuration Index
Message #30002, Set Configuration Index
Message #30002, Set Data Link State
Message #30002, Set Antenna Mode
Message #30002, Communication Security Mode
Message #30003, Set Pedestal Mode
Message #30003, Set Transmitter Attenuation
Message #30003, Select Active Antenna Pedestal Index
Message #30003, Communication Security Key Index
Message #30101, Pedestal Index
Message #30101, Set antenna Pointing Mode
Message #30102, Pedestal Index
Message #30200, Bit Mode
For bit fields, e.g. 0x0001, 0x0002, 0x0004, 0x0008, the right most bit (0x0001) shall
be considered Enumeration Index 0.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41002.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
1302.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1302.04
VSM ID
Integer 4
None
See Section 1.7.6
1302.05
Data Link ID
Integer 4
None
See Section 1.7.6
0 = N/A
1 - B - 292
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1302.06
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 4
None
No Restrictions
41002.01
Component Number
Station Location
41002.02
Component Location
1302.07
Requested Message
0 = N/A
1 - B - 293
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1302.08
Requested Field
Unsigned 1
None
No Restrictions
Unsigned 1
Enumerated

1 = Field Supported
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Unsigned 1
None
No Restrictions
Character 16
None
No Restrictions
Character 80
None
No Restrictions

supported.
1302.09
Field Supported
Set to zero to unsupport
all enumerations in the
reported field.
41002.03
10
Default Value
Message
1302.10
11
Vehicle (Payload) Specific

Enumeration Count
Set to zero when vehicle
specific enumerations are
not being added. When
zero, fields 1302.11,
1302.12 and 1302.13 are
also N/A.
0 = N/A
Number Of Vehicle Specific
Enumeration States For
This Field
1302.11
12

Enumeration Index
0 = N/A
Actual Enumeration Index
1302.12
13

Enumeration Text
Text To Display For
Selected Enumeration
1302.13
14

Help Text
1 - B - 294
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
41002.05
15
Data Element Name &

Description
Remove Enumerated
Index
Type
Units
Range
Unsigned 1
None
No Restrictions
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Enumerated index value

not supported by
Addressed Asset
0 = N/A
Controlled By Field
Available
1302.14
16
Route Type
applies for mission
messages
41002.04
17
Table B1 - 182: Message #41002: Field Configuration Enumerated Response

4.24.5 Message #41003: Field Configuration Unsigned Response.
the list (below) that are required per an LOI configuration request, and supported by
the VSM (i.e.; based on the Request type for LOI). The LOI for each of the
referenced parameters in the list shall be in accordance with Table B1 5, Functional
Message Group Table for the referenced messages. This message shall be
transmitted from the VSM/ vehicle/ Data Link to the CUCS after the reception of
Message #40000 in response to a single parameter request from the CUCS if
configuration information is available for the requested parameter.
This message shall define the level of support provided to the CUCS for control over
a specified commanded DLI message parameter, or for the reporting of a DLI
message parameter, of type Unsigned, by the VSM/ vehicle/ Data Link filling in the
message for the requested parameter and transmitting it to the CUCS. Where the
1 - B - 295
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
VSM/ vehicle/ data link does not support a requested parameter, this message shall
elements.
these same warnings.
The CUCS, as a minimum, shall support the reception of following DLI message
None specified at this time
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41003.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
41003.05
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
41003.06
VSM ID
Integer 4
None
See Section 1.7.6
41003.07
Data Link ID
Integer 4
None
See Section 1.7.6
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
0 = N/A
41003.08
Station Number 1-16

1 - B - 296
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41003.01
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 4
None
No Restrictions
Station Location
41003.02
Component Location
41003.09
Requested Message
See Section 4.1.1
41003.10
Requested Field
Unsigned 1
None
1x
41003.11
Field Supported
Unsigned 1
Enumerated

1 = Field Supported
41003.12
10
Max Value
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions

Message
41003.13
11
Min Value
Message
41003.14
12
Max Display Value

Message
1 - B - 297
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41003.15
13
Min Display Value
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions
Unsigned 4
See Field In
Requested
Message
No Restrictions

Message
41003.16
14
Minimum Display
Resolution
Message
41003.17
15
High Caution Limit

cause a Caution
Message
41003.18
16
High Warning Limit

cause a Warning
Message
41003.19
17
Low Caution Limit

cause a Caution
Message
41003.20
18
Low Warning Limit

cause a Warning
Message
41003.21
19
Help Text
Character 80
None
No Restrictions
41003.03
20
Route Type
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight

applies for mission
messages
1 - B - 298
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41003.04
21
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 183: Message #41003: Field Configuration Unsigned Response

4.24.6 Message #41004: Field Configuration Character Response.
This message shall be transmitted from the VSM/vehicle/data link to the CUCS after
the reception of Message #40000 in response to a single parameter request from the
CUCS if configuration information is available for the requested parameter.
This message shall define the level of support provided to the CUCS for control over
a specified commanded DLI message parameter, or for the reporting of a DLI
message parameter, of size Integer, by the VSM/vehicle/data link filling in the
message for the requested parameter and transmitting it to the CUCS. Where the
VSM/vehicle/data link does not support a requested parameter, this message shall
elements.
The CUCS is not required to support the request/reception of any DLI message
parameters from a VSM/vehicle/data link with regard to character type field
configuration.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41004.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
41004.05
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
41004.06
VSM ID
Integer 4
None
See Section 1.7.6
41004.07
Data Link ID
Integer 4
None
See Section 1.7.6
0 = N/A
1 - B - 299
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41004.08
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 4
None
No Restrictions
Unsigned 1
None
No Restrictions
0x0000 = N/A
41004.01
Component Number
Station Location
41004.02
Component Location
41004.09
Requested Message
See Section 4.1.1
41004.10
Requested Field
1 - B - 300
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41004.11
Field Supported
Unsigned 1
Enumerated

1 = Field Supported
41004.12
10
Help Text
Character 80
None
No Restrictions
41004.13
11
Subsystem ID
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
5 = Navigation
6 = Payload
7 = Recovery System
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 18 = Reserved 12-19
19 = Not Assigned
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32

which this field is
associated
41004.03
12
Route Type
applies for mission
messages
41004.04
13
Table B1 - 184: Message #41004: Field Configuration Character Response

4.24.7 Message #41005: Configuration Complete.
The VSM/vehicle/data link shall use the Configuration Complete message to identify
that all configuration messages have been sent from the VSM/vehicle/data link to the
CUCS as requested with Message #40000, Field Configuration Request, for the
identified VSM, air vehicle, data link, or payload station. The CUCS shall use this
message to identify that configuration of the CUCS is complete as requested based
on the received 41xxx, 2015, 3000, and 21100 messages and any messages
requested by Message #17002 during configuration. If the configuration messages
1 - B - 301
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
require an acknowledgement, this message shall not be sent until all the requested
acknowledgements have been received or a time out has occurred.
The null ID shall be used for an ID that is not applicable during an instance of
transmission of this message.
The VSM/ vehicle/ data link shall be able to transmit this message to the CUCS
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41005.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1203.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1203.04
VSM ID
Integer 4
None
See Section 1.7.6
1203.05
Data Link ID
Integer 4
None
See Section 1.7.6
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
0 = N/A
1203.06
Station Number 1-16

41005.01
Component Number
Station Location
1 - B - 302
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41005.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Enumerated
0 - 65535 = See Table B136
Unsigned 2
Enumerated
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Component Location
1203.07
Vehicle Type
assigned by STANAG
Custodian.
1203.08
Vehicle Subtype
the manufacturer.
41005.03
Table B1 - 185: Message #41005: Configuration Complete

4.24.8 Message #41006: Integer Enumeration Response.
1 - B - 303
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
This message shall be sent by a VSM/data link/ air vehicle to define a set of discrete
integer values for a given message field. These values are the only allowed values to
be selected by the CUCS operator and sent from the CUCS.
At a minimum the CUCS shall support this message for the following fields:
Message 11000: Flap Deployment Command
Message 13004: Horizontal Field of View
Message 13004: Vertical Field of View
Message 19001: Set Horizontal Field of View
Message 19001: Set Vertical Field of View
Message 19200: Set Radar Resolution
Message 319500: Set Recording Rate
Message 319500: Set Clock Rate
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41006.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
41006.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
41006.02
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
1 - B - 304
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41006.08
Component Number
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Bitmapped
0x01 = EO
0x02 = IR
0x04 = Payload Specific
Unsigned 4
None
No Restrictions
Station Location
41006.09
Component Location
41006.03
Addressed Sensor
Identifies which sensor(s) to
apply this enumeration to
41006.04
Requested Message
See Table B1-6 thru B1-33
41006.05
Requested Field
Unsigned 1
None
1x
41006.06
Value Count
Unsigned 1
None
2 x 16
Same as
Requested
Field
No Restrictions
Values repetition begins (where n = 1 to "Value Count")

41006.07
Unsigned 4
Value <n>
Same as requested field
Values repetition ends
1 - B - 305
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
41006.10
25
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 186: Message #41006: Integer Enumeration Response

4.25 General Postconnection Configuration Messages.
After connection Messages #41000, #41001, #41002, #41003, and #41004 are
reused in order to update any of the initial parameters that were set during the preconnection phase.
4.25.1 Message #42000: Display Unit Request.
The CUCS shall use the Display Unit Request message to identify the display units
and format that the VSM/ vehicle is required to use in Remote Displays for that
CUCS. The VSM/ vehicle shall accept this message from the CUCS anytime the
CUCS has a valid connection with the VSM/ vehicle to control functionality.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42000.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1201.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1201.05
Distance
Unsigned 1
Enumerated
0=m
1 = Foot
2 = km
3 = NM
1201.06
Altitude
Unsigned 1
Enumerated
0=m
1 = Foot
1201.07
Speed
Unsigned 1
Enumerated
0 = m/s
1 = Knot
2 = Mile per hour
3 = km per hour
1201.08
Position (Latitude,
Longitude)
Unsigned 1
Enumerated
0 = Degree
1 = UTM
2 = MGRS
1 - B - 306
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1201.09
Temperature
Unsigned 1
Enumerated
0 = C
1 = F
2=K
1201.10
Mass/Weight
Unsigned 1
Enumerated
0 = kg
1 = Pound
1201.11
Angles
Unsigned 1
Enumerated
0 = rad
1 = Degree
1201.12
Pressure - Barometric
Unsigned 1
Enumerated
0 = millibar (mb)
1 = Inch of Mercury (inHg)
2 = Pa
1201.13
10
Fuel Quantity
Unsigned 1
Enumerated
0=L
1 = Pound
2 = kg
42000.01
11
Position Display Format
Unsigned 1
Enumerated
0 = DDD MM SS
1 = DDD MM.MM
2 = DDD.DD
3 = Not Specified
When the Position field is

commanded to Degrees,
this field defines the format
of that data. The exact
number of digits displayed
is not defined, but the
absence of a . indicates
the value should be
displayed as an integer.
DDD indicates degrees,
MM indicates minutes and
SS indicates seconds.
Edition 2.
42000.02
12
Altitude Rate
Unsigned 1
Enumerated
0 = m/s
1 = Foot/Minute
42000.03
13
Activity ID
Unsigned 3
None
No Restrictions

Table B1 - 187: Message #42000: Display Unit Request

4.25.2 Message #42001: CUCS Resource Report.
This message shall be used to communicate to the VSM/vehicle/data link the

resources available within the CUCS for managing remote displays to be presented
at the CUCS. The VSM/vehicle/data link shall transmit Remote Displays to the
CUCS in accordance with the contents of this message only after the reception of
this message from a CUCS. The use of Field 12 shall be limited to transfer of
STANAG 4545 data from the VSM to CUCS.
The null ID in the wrapper shall be used for an ID that is not applicable during an
instance of transmission of this message.
1 - B - 307
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
The CUCS shall only transmit this message to the VSM/vehicle/ data link when it has
an authorized connection.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42001.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1202.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1202.10
(X Window) Display
Number
Integer 1
None
No Restrictions
1202.11
(X Window) Screen
Number
Integer 1
None
No Restrictions
1202.12
Vertical Offset from Top

Left Corner
Unsigned 2
Pixel
No Restrictions
Unsigned 2
Pixel
No Restrictions
Location of top corner of

remote display.
1202.13
Horizontal Offset from

Top Left Corner
Location of left corner of
remote display.
1202.14
Display Window
Horizontal Width (Pixels)
Unsigned 2
Pixel
No Restrictions
1202.15
Display Window Vertical

Height (Pixels)
Unsigned 2
Pixel
No Restrictions
1202.16
CUCS IP Address
Unsigned 4
None
No Restrictions
42001.01
STANAG 4545 Directory
Character
256
None
No Restrictions
STANAG 4545 directory is

encoded as a URI string. A
null string defaults to the
system specific default.
Table B1 - 188: Message #42001: CUCS Resource Report

4.25.3 Message #42002: Manage VSM Windows Message.
This message shall be used by the CUCS to identify to the VSM/ vehicle/ data link if
the selected vehicle ID (Destination ID) (separated by station)/ Data Link ID has
focus at the CUCS, thus authorizing the display of remote windows for the referenced
functionality. Where the vehicle ID (separated by station)/ Data Link ID does not have
focus at the CUCS, the VSM/ vehicle/ data link shall remove its Remote Displays as
required from the CUCS user interface. i.e.: when the Data Link ID is set to a specific
value, that Data Link must remove all its remote displays from the CUCS when the
vehicle focus field is set to false.
As another example, a message transmitted to the AV/ VSM with a non null Vehicle
ID with the Station number set to zero (AV platform only) and with the Vehicle focus
set to false, means the vehicle payload windows are still allowed to remain displayed,
1 - B - 308
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
if they were already in focus, but the vehicle platform windows must be removed from
the CUCS displays.
During the configuration process remote display items that can be selected via this
message were defined using Message #43002: Remote Windows GUI Definition and
this message shall be used by the CUCS to request the AV/ VSM/ Data Link to
display one of those particular GUIs. When the GUI Reference ID field is set to 255
the VSM shall restore the remote window configuration on the CUCS for the specified
functionality, vehicle, payload, or data link, as per previous i.e.; the remote display
configuration as for the specified station just before it was taken out of focus.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
42002.04
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
42002.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
42002.01
Component Number
Station Location
1 - B - 309
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42002.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 1
Enumerated
0 = False
1 = True
Unsigned 1
None
No Restrictions
Component Location
42002.06
Vehicle Focus
Remove all Remote
Displays for station
(1204.06), vehicle station or
for Data Link, as applicable
when set to False
42002.07
GUI Reference ID
From Message #43002,
Remote Windows GUI
Definition, GUI Reference
ID field (Unique ID
1205.05). Not valid when
Vehicle Focus (1204.07) is
false. Enumeration zero
sets the focus back to the
vehicle/ data link, but does
not call a remote display in
particular.
0 = none
1 to 254 = per
configuration
255 = Restore remote
window configuration
1 - B - 310
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42002.03
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
Table B1 - 189: Message #42002: Manage VSM Windows Message

4.25.4 Message #42003: Report Controllable Element.
This message is used by the vehicle to report to the CUCS all of the elements that
can be controlled on the vehicle with direct joystick input. For LOI-4, this message
shall be sent once for each control element pertaining to vehicle control (e.g. gear up,
aileron). For LOI-3, this message shall be sent once for each control element
pertaining to payload control (e.g. pan, tilt, and zoom).
The Controllable Element Id shall be unique on a per vehicle basis (i.e. two different
vehicles may each use the same id for different controllable elements). The Name
should be a semantically meaningful description of the controllable element (e.g.
throttle, aileron).
When applicable, the following list of controllable element names shall be used:
For (typically) analogue elements:
- Aileron
- Elevator
- Throttle
- Rudder
- Ruddervator
- Flaperons
- Elevons
- Pan
- Tilt
- Zoom
For (typically) discrete elements:
1 - B - 311
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
- Landing Gear
- Zoom In
- Zoom Out
- Cage
- Stow
- Initiate Track
The input type shall indicate if the vehicle expects an analogue value (-127 x 127)
or a discrete value (0 = Off, 1 = On).
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
42003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
42003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
42003.02
Controllable Element ID
Unsigned 2
None
1x
Character 24
None
No Restrictions
Unsigned 1
Enumerated
0 = Analogue
1 = Discrete
Unique identifier of the

controllable element
42003.03
Name
Descriptive name of the
42003.04
Input Type
Identifies the type of input
represented by the
Table B1 - 190: Message #42003: Report Controllable Element

4.25.5 Message #43000: VSM Services Report Message.
This message shall be used to communicate to the CUCS the remote display
services provided by the VSM to the CUCS. It defines the VSMs home page and
FTP location, if these services are used by the VSM. This message will be sent after
the VSM receives the CUCS Resource Report (Message #42001) and has done any
needed setup or initialization of its services. Once this message has been received
by the CUCS, the CUCS can browse to the VSMs home page.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
43000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
1304.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1304.04
VSM Home Web Page

URL
Character
249
None
No Restrictions
Blank if service not

provided by VSM
1 - B - 312
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
1304.05
FTP URL
Character
249
None
No Restrictions
Blank if service not

provided by VSM
Table B1 - 191: Message #43000: VSM Services Report Message

4.25.6 Message #43001: AV Route Configuration.
This message shall be used by the VSM to define its capability to support multiple
instances of each Route Type, and the maximum allowable number of waypoints and
the supported Location Types per Route Type.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
43001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
43001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
43001.02
Route Type
Unsigned 1
Enumerated
0 = Launch
1 = Approach
2 = Flight
3 = Contingency A
4 = Contingency B
43001.03
Instances
Unsigned 1
None
1x
43001.04
Maximum Number
Waypoints
Unsigned 2
None
1 x < 65,535
43001.05
Location Type Support
Unsigned 1
Bitmapped
0x01 = Absolute
0x02 = Relative
Table B1 - 192: Message #43001: AV Route Configuration

4.25.7 Message #43002: Remote Windows GUI Definition.
This message shall be used by the AV/ VSM/ Data Link to define remote windows
(vehicle specific displays) that the CUCS operator can select from the generic CUCS
user interface. As an example, the selection of these remote displays may be from a
CUCS menu item.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
43002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
43002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
43002.02
GUI Reference ID
Unsigned 1
None
1x
Reference ID that identifies

a standalone GUI element,
such as a dialog.
1 - B - 313
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
43002.03
Parent GUI Reference ID
Unsigned 1
None
No Restrictions
Unsigned 1
Enumerated
0 = Engine
1 = Mechanical
2 = Electrical
3 = Comms
5 = Navigation
6 = Payload
7 = Recovery System
System
9 = VSM Status
10 = VDT
11 = CDT
12 - 19 = Reserved
Character 16
None
No Restrictions
Unsigned 1
Enumerated
0 = Enabled
1 = Disabled
Reference ID that identifies

a GUI Grouping. A zero
indicates that the GUI is not
related to a higher level
GUI Group.
43002.04
Subsystem ID
reported.
43002.05
Text
Text to display on CUCS for
the GUI
43002.06
Enable
Indicates whether the VSM
GUI can be requested by
the CUCS
Table B1 - 193: Message #43002: Remote Windows GUI Definition

4.26 VSM Forced Command Messages.
4.26.1 Message #44000: Field Change Integer Command.
This message shall be transmitted from the VSM to change the current commanded
state of a CUCS field. The CUCS will use this information to update the state of the
command field.
The CUCS shall support the following fields when receiving this message:
Message #2002, Vehicle Steering Command, Commanded Altitude
Message #2002, Vehicle Steering Command, Commanded Heading
Message #2002, Vehicle Steering Command, Commanded Roll
Message #2002, Vehicle Steering Command, Commanded Speed
Message #2002, Commanded Waypoint Number
Message #2002, Altimeter Setting
Message #2004, Loiter Radius
Message #2004, Loiter Length
1 - B - 314
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #2004, Loiter Altitude

Message #2004, Loiter Speed
Message #2008, Engine Command, Engine Number
Message #2014, Contingency A Delay
Message #2014, Contingency A Waypoint Number
Message #2014, Contingency B Delay
Message #2014, Contingency B Waypoint Number
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
44000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
44000.02
Requested Message
Unsigned 2
None
No Restrictions
44000.03
Requested Field
Unsigned 1
None
No Restrictions
44000.04
Commanded Value
Integer 4
See Field In
Requested
Message
No Restrictions

Message
Table B1 - 194: Message #44000: Field Change Integer Command

4.26.2 Message #44001: Field Change Float Command.
This message shall be transmitted from the VSM to inform the CUCS of a change to
the state of the command field. The CUCS will use this information to update the
state of the command field.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
44001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
44001.02
Requested Message
Unsigned 2
None
No Restrictions
44001.03
Requested Field
Unsigned 1
None
No Restrictions
44001.04
Commanded Value
Float
See Field In
Requested
Message
No Restrictions

Message
Table B1 - 195: Message #44001: Field Change Float Command

4.26.3 Message #44002: Field Change Enumerated Command.
This message shall be transmitted from the VSM to inform the CUCS of a change to
the state of the command field. The CUCS will use this information to update the
state of the command field.
Message #2001, Vehicle Operating Mode Command, Select Flight Path
Control Mode
1 - B - 315
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #2002, Vehicle Steering Command, Altitude Command Type
Message #2002, Vehicle Steering Command, Heading Command Type
Message #2002, Vehicle Steering Command, Speed Type
Message #2002, Vehicle Steering Command, Altitude Type
Message #2003, Mode Preference Command, Altitude Mode
Message #2003, Mode Preference Command, Speed Mode
Message #2003, Mode Preference Command, Heading Mode
Message #2004, Loiter Length Units
Message #2004, Flying Behaviour
Message #2005, Flight Termination Command, Command Flight Termination
State
Message #2005, Flight Termination Command, Flight Termination Mode
Message #2007, Air Vehicle Lights, Set Lights
Message #2008, Engine Command, Engine Command
Message #2014, Contingency A Command
Message #2014, Contingency B Command
For bit fields (e.g., 0x0001, 0x0002, 0x0004, 0x0008), all bits are defined by the
Commanded Enumeration Index Value.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
44002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
44002.02
Requested Message
Unsigned 2
None
No Restrictions
44002.03
Requested Field
Unsigned 1
None
No Restrictions
44002.04
Commanded
Enumeration Index Value
Integer 4
None
No Restrictions
This field is also used to set

the state of bitmapped
fields
Index Into Enumerated
States Where 0 = First, 1 =
Second, etc.
Table B1 - 196: Message #44002: Field Change Enumerated Command
1 - B - 316
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.26.4 Message #44003: Message Parameter Availability.
This message shall be used by the CUCS to make available (default) or unavailable
any components on the CUCS interface associated with the control of supported DLI
message parameters, as referenced in the list below.
This message shall be sent from the AV/ VSM/ Data Link to the CUCS for a listed
DLI parameter anytime the controllable state of that parameter, or an enumeration/
bit mapped value within an enumerated/ bit mapped parameter, changes thus
altering the allowable state of control over the specified parameter at the AV/ VSM/
Data Link, i.e., the VSM reports if a DLI message field is currently available to control
or if it is unavailable (Field Available), or if specific enumerations within an
enumerated data element field are available or unavailable for control.
If no configuration message is received by the CUCS during the VSM response(s) to
Message #40000, the CUCS will display the field with its full range enabled.
For parameters in the list below, the availability of some DLI message fields may
depend on the availability of other message fields/ enumerations, and are therefore
noted as such. This is to ensure consistency between fields of the exact same type.
The AV/ VSM/ Data Link and CUCS shall use the primary parameter, the parameter
that the others parameters availability follows, to report the availability of that
parameter. E.g.: The Message #2002, Heading Command Type, is used to report the
availability to control the heading (Message #2002, Commanded Heading) by stating
the availability of the Heading enumeration in the Heading Command Type field.
The CUCS, as a minimum, shall support the reception of the following mandatory DLI
message parameters from the VSM/vehicle/data link:
Message #2002, Altitude Command Type
Message #2002, Heading Reference
Message #2002, Heading Command Type
Message #2002, Commanded Altitude (Use Message #2002, Altitude
Command Type)
Message #2002, Commanded Vertical Speed (Use Message #2002, Altitude
Command Type)
Message #2002, Commanded Heading (Use Message #2002, Heading
Command Type)
Message #2002, Commanded Course (Use Message #2002, Heading
Command Type)
Message #2002, Commanded Turn Rate (Use Message #2002, Heading
Command Type)
Message #2002, Commanded Roll Rate (Use Message #2002, Heading
Command Type)
1 - B - 317
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #2002, Commanded Roll (Use Message #2002, Heading Command
Type)
Message #2002, Commanded Airspeed
Message #2003, Altitude Mode
Message #2003, Speed Mode
Message #2003, Heading Mode
Message #2007, Set Lights
Message #2008, Engine Command
Message #13000, Mission Plan Mode
Message #13002, Waypoint Altitude Type
Message #13002, Waypoint Speed Type
Message #13002, Arrival time This parameter is not configured from this
message, this message is only to identify if this parameter is supported by the
VSM / AV.
Message #13002, Turn Type
Message #13003, Waypoint Loiter Type
Message #13004, Set Sensor Pointing Mode
Message #13004, Starepoint Altitude Type
Message #13005, Function
Message #13005, Enumerated State
Message #15000, Subsystem ID
Message #18000, PTT
Message #19001, Set Zoom

Message #19100, Set EO Sensor Mode
Message #19100, Focus Type
Message #19100, Set IR Polarity
Message #19200, Set MTI Radar Mode
1 - B - 318
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Message #19300, Active Weapon Mode Command

Message #19300, Target Altitude Type
Message #19700, System Operating Mode
Message #28001, Data Link Type
Message #28001, Antenna Type
Message #30002, Set Data Link State
Message #30002, Set Antenna Mode
Message #30002, Communication Security Mode
Message #30003, Set Pedestal Mode
Message #43002, GUI Reference ID
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44003.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
1303.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1303.05
Station Number 1-16
Unsigned 2
Bitmapped
0x0001 = Stn #1
0x0002 = Stn #2
0x0004 = Stn #3
0x0008 = Stn #4
0x0010 = Stn #5
0x0020 = Stn #6
0x0040 = Stn #7
0x0080 = Stn #8
0x0100 = Stn #9
0x0200 = Stn #10
0x0400 = Stn #11
0x0800 = Stn #12
0x1000 = Stn #13
0x2000 = Stn #14
0x4000 = Stn #15
0x8000 = Stn #16
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
44003.01
Component Number
Station Location
1 - B - 319
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44003.02
Unsigned 2
Bitmapped
0x0001 = #1
0x0002 = #2
0x0004 = #3
0x0008 = #4
0x0010 = #5
0x0020 = #6
0x0040 = #7
0x0080 = #8
0x0100 = #9
0x0200 = #10
0x0400 = #11
0x0800 = #12
0x1000 = #13
0x2000 = #14
0x4000 = #15
0x8000 = #16
Unsigned 4
None
No Restrictions
Unsigned 1
None
No Restrictions
Component Location
1303.06
Reported Message
See Section 4.1.1
1303.07
Reported Field
Field Identifier
0 = message not supported
1303.08
Field Available
Unsigned 1
Enumerated
0 = Complete Field Not

Available For Selection
1 = Complete Field
Available For Selection
1303.09
Reported Enumerated
Index
Unsigned 1
None
No Restrictions
Integer 1
Enumerated
-2 = Not Implemented
-1 = State Unavailable For
Selection
0 = State Available For
Selection
Reported enumerated index

for enumerated fields to
disable/ enable a single
enumeration in an
enumerated/ bit mapped
field. Overrides 1303.08
enumeration 1 for the
specified enumeration.
Controlled By Field
Available
1303.10
Enumerated Index Enable

State of the enumeration
specified 1303.09.
-2 added to support
Edition 2.
1 - B - 320
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
44003.03
10
Unsigned 2
Bitmapped
0x0001 = Stn #17

0x0002 = Stn #18
0x0004 = Stn #19
0x0008 = Stn #20
0x0010 = Stn #21
0x0020 = Stn #22
0x0040 = Stn #23
0x0080 = Stn #24
0x0100 = Stn #25
0x0200 = Stn #26
0x0400 = Stn #27
0x0800 = Stn #28
0x1000 = Stn #29
0x2000 = Stn #30
0x4000 = Stn #31
0x8000 = Stn #32
1303.12
11
Route Type
Unsigned 1
Bitmapped
0x01 = Launch
0x02 = Approach
0x04 = Flight

applies for mission
messages.
Table B1 - 197: Message #44003: Message Parameter Availability

4.27 Draw Interface Messages.
4.27.1 Message #46000: Draw Layer Configuration.
This message shall be sent by the AV, VSM or Data Link to a CUCS to assign and
name draw layers for a situation awareness display for operator reference. This
provides a priority to the draw layers, and provides the capability to hide or erase an
entire layer.
The Draw Layer specifies which draw list to use, 1- N, according to the order in which
this layer is drawn (higher numbered layers are drawn later, and hence appear over
top of lower numbered layers).
The Draw Layer (N) Name string is provided to allow the operator to turn off this layer
(to de-clutter the situation display). It is recommended that this feature be used only
for complex draw layers.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46000.02
Draw Layer Number
Unsigned 1
None
1x
46000.03
Draw Layer Name
Character 16
None
No Restrictions
Null = No Label
Table B1 - 198: Message #46000: Draw Layer Configuration
1 - B - 321
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
4.27.2 Message #46001: Draw Layer Update Request / Status.
This message shall be sent by the CUCS to the AV, VSM or Data Link to request an
update to a Draw Layer or to return status of the draw request from the AV, VSM or
Data Link.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46001.02
Draw Layer
Unsigned 1
None
No Restrictions
Unsigned 2
None
No Restrictions
Unsigned 1
Enumerated
0 = Layer Cleared
1 = Layer Displayed
2 = Layer Hidden
4 = Layer Released
5 = Object Deleted
6 = Request Update
Layer to update.
0 = All
46001.03
Object ID
0 = N/A
46001.04
Layer / Object Status
Table B1 - 199: Message #46001: Draw Layer Update Request / Status

4.27.3 Message #46002: Draw Layer Control.
This message shall be sent by the AV, VSM or Data Link to the CUCS to clear/
erase/ show/ release the contents of a Draw Layer or to delete an object within a
Layer.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46002.02
Draw Layer
Unsigned 1
None
No Restrictions
Unsigned 2
None
No Restrictions
Unsigned 1
Enumerated
0 = Clear Layer
1 = Show Layer
2 = Hide Layer
4 = Release Layer
5 = Delete Object
0 = All
46002.03
Object ID
0 = N/A
46002.04
Layer / Object Control
Table B1 - 200: Message #46002: Draw Layer Control

4.27.4 Message #46003: Draw Line.
This message shall be sent by the AV, VSM or Data Link to a CUCS to draw a georeferenced 3-D line object on a situation awareness display for operator reference.
1 - B - 322
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
The line Colour property represents the colour and transparency of the line. It is a
string representation for an RGB triple value as in: #2a443cff. The 2a is the
intensity of the red component represented as hexadecimal. Likewise, the 44 is the
green component, and the 3c is the blue component. The final ff specifies that the
line should be opaque. A value of 00 for transparency would indicate that the line
should be entirely transparent.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46003.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
46003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46003.02
Object ID
Unsigned 2
None
1x
46003.03
Draw Layer
Unsigned 1
None
1x
46003.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46003.05
Line Width
Unsigned 1
Pixel
1x
46003.06
Line Style
Unsigned 1
Enumerated
0 = Solid
1 = Dashed
2 = Dotted
3 = Stipple1
4 = Stipple2
5 = Stipple3
6 = Stipple4
46003.07
Start Latitude
Integer 4
BAM
-/2 x /2
46003.08
Start Longitude
Integer 4
BAM
No Restrictions
46003.09
End Latitude
Integer 4
BAM
-/2 x /2
46003.10
10
End Longitude
Integer 4
BAM
No Restrictions
Table B1 - 201: Message #46003: Draw Line

4.27.5 Message #46004: Draw Simple Polygon.
This message shall be sent by the AV, VSM or Data Link to a CUCS to draw a simple
geo-referenced polygon object on a situation awareness display for operator
reference.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46004.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
46004.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46004.02
Object ID
Unsigned 2
None
1x
46004.03
Draw Layer
Unsigned 1
None
1x
46004.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46004.05
Fill Style
Unsigned 1
Enumerated
0 = Outline
1 = FillSolid
2 = FillStipple1
3 = FillStipple2
4 = FillStipple3
5 = FillStipple4
1 - B - 323
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46004.06
Line Width
Unsigned 1
Pixel
1x
46004.07
Line Style
Unsigned 1
Enumerated
0 = Solid
1 = Dashed
2 = Dotted
3 = Stipple1
4 = Stipple2
5 = Stipple3
6 = Stipple4
46004.08
Latitude Top
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Top left corner

46004.09
Longitude Top
Top left corner
46004.10
10
Latitude Bottom
Bottom right corner
46004.11
11
Longitude Bottom
Bottom right corner
Table B1 - 202: Message #46004: Draw Simple Polygon

4.27.6 Message #46005: Draw Complex Polygon.
This message shall be sent by the AV, VSM or Data Link to a CUCS to draw a
complex geo-referenced polygon object on a situation awareness display for operator
reference. The last vertex shall be automatically connected to the first and at least 3
vertices shall be specified for this polygon to be drawn.
For the Message #46005, only the 8 first fields are bitmapped by the Presence
Vector.
When the eighth bit is set to:
1 the fields 8 to 8 + Total Polygon Indices x 2 are present in the message
0 the fields 8 to 8 + Total Polygon Indices x 2 are not present in the
message
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46005.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46005.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46005.02
Object ID
Unsigned 2
None
1x
46005.03
Draw Layer
Unsigned 1
None
1x
46005.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46005.05
Fill Style
Unsigned 1
Enumerated
0 = Outline
1 = FillSolid
2 = FillStipple1
3 = FillStipple2
4 = FillStipple3
5 = FillStipple4
1 - B - 324
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46005.06
Line Width
Unsigned 1
Pixel
1x
46005.07
Line Style
Unsigned 1
Enumerated
0 = Solid
1 = Dashed
2 = Dotted
3 = Stipple1
4 = Stipple2
5 = Stipple3
6 = Stipple4
46005.08
Total Polygon Indices
Unsigned 1
None
3 x 63
Vertices repetition begins (where n = 1 to "Total Polygon Indices")

46005.09
Latitude Point <n>
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Top left corner

46005.10
Longitude Point <n>

Top left corner
Vertices repetition ends
Table B1 - 203: Message #46005: Draw Complex Polygon

4.27.7 Message #46006: Draw Arc/Circle.
This message shall be sent by the AV, VSM or Data Link to a CUCS to draw a georeferenced 3-D Arc/Circle object on a situation awareness display for operator
reference.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46006.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
46006.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46006.02
Object ID
Unsigned 2
None
1x
46006.03
Draw Layer
Unsigned 1
None
1x
46006.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46006.05
Fill Style
Unsigned 1
Enumerated
0 = Outline
1 = FillSolid
2 = FillStipple1
3 = FillStipple2
4 = FillStipple3
5 = FillStipple4
46006.06
Line Width
Unsigned 1
Pixel
1x
46006.07
Line Style
Unsigned 1
Enumerated
0 = Solid
1 = Dashed
2 = Dotted
3 = Stipple1
4 = Stipple2
5 = Stipple3
6 = Stipple4
46006.08
Radius
Unsigned 2
No Restrictions
1 - B - 325
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46006.09
Start Angle
Integer 2
BAM
No Restrictions
46006.10
10
End Angle
Integer 2
BAM
No Restrictions
46006.11
11
Latitude Centre
Integer 4
BAM
-/2 x /2
46006.12
12
Longitude Centre
Integer 4
BAM
No Restrictions
Table B1 - 204: Message #46006: Draw Arc/Circle

4.27.8 Message #46007: Draw Text.
This message shall be sent by the AV, VSM or Data Link to a CUCS to draw a georeferenced Text object on a situation awareness display for operator reference.
Offset Right, Offset Down centre the text this many pixels right (if positive) and
down (if positive) from the specified coordinates. The Pixel-reference allows for the
Text object to be displaced by a fixed amount from a coordinate that is independent
of scaling.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46007.00
Presence Vector
Unsigned 2
Bitmapped
No Restrictions
46007.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46007.02
Object ID
Unsigned 2
None
1x
46007.03
Draw Layer
Unsigned 1
None
1x
46007.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46007.05
Draw Font
Unsigned 1
Enumerated
0 = Small
1 = Medium
2 = Large
46007.06
Text String
Character 20
None
No Restrictions
46007.07
Latitude
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Top Left corner

46007.08
Longitude
Top Left corner
46007.09
Offset Right
Integer 2
Pixel
No Restrictions
46007.10
10
Offset Down
Integer 2
Pixel
No Restrictions
Table B1 - 205: Message #46007: Draw Text

4.27.9 Message #46008: Draw Arrow.
This message shall be sent by the AV, VSM or data link to a CUCS to draw a georeferenced 3-D Arrow object on a situation awareness display for operator reference.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46008.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
46008.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
1 - B - 326
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46008.02
Object ID
Unsigned 2
None
1x
46008.03
Draw Layer
Unsigned 1
None
1x
46008.04
Draw Colour
Unsigned 4
RGBA
No Restrictions
46008.05
Line Width
Unsigned 1
Pixel
1x
46008.06
Line Style
Unsigned 1
Enumerated
0 = Solid
1 = Dashed
2 = Dotted
3 = Stipple1
4 = Stipple2
5 = Stipple3
6 = Stipple4
46008.07
Arrowhead Style
Unsigned 1
Enumerated
0 = SolidArrow
1 = OutlineArrow
2 = Arrow/Stem
46008.08
Arrowhead Length
Unsigned 2
Pixel
No Restrictions
46008.09
Arrow Stem Length
Unsigned 2
Pixel
No Restrictions
Unsigned 2
BAM
No Restrictions
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
Integer 4
BAM
-/2 x /2
Integer 4
BAM
No Restrictions
0 = Use Stem Location

46008.10
10
Orientation
Angle from north in CW
direction from tip to stem.
46008.11
11
Tip Latitude
Tip location
46008.12
12
Tip Longitude
Tip location.
46008.13
13
Stem Latitude
Stem location.
46008.14
14
Stem Longitude
Stem location.
Table B1 - 206: Message #46008: Draw Arrow

4.27.10 Message #46009: Set Cursor Interest.
This message shall be sent by the AV, VSM or data link to a CUCS to register for a
basic mouse click event notification where the AV, VSM or data link desires that a
coordinate be sent as a result of a coordinate selection on the situational awareness
display. Message #46011, Cursor Interest Return, shall be transmitted when a
Cursor Interest is set and the event occurs.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46009.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46009.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46009.02
Interest ID
Unsigned 1
None
1x
1 - B - 327
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46009.03
Cursor Interest Name
Character 20
None
No Restrictions
For display purposes.
Table B1 - 207: Message #46009: Set Cursor Interest

4.27.11 Message #46010: Remove Cursor Interest.
This message shall be sent by the AV, VSM or data link to a CUCS to release mouse
cursor interest, and shall stop the transmission of Message #46011, Cursor Interest
Return, from the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46010.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46010.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46010.02
Interest ID
Unsigned 1
None
1x
Table B1 - 208: Message #46010: Remove Cursor Interest

4.27.12 Message #46011: Cursor Interest Return.
This message shall be sent by the CUCS to an AV, VSM or data link in response to a
Message #46009, Set Cursor Interest Message as a result of a coordinate selection
on the situational awareness display.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
46011.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
46011.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
46011.02
Interest ID
Unsigned 1
None
1x
46011.03
Geo-referenced Pointer
Latitude
Integer 4
BAM
-/2 x /2
46011.04
Geo-referenced Pointer
Longitude
Integer 4
BAM
No Restrictions
Tip location.
Table B1 - 209: Message #46011: Cursor Interest Return

4.28 Vehicle and Payload Specific Message Formats.
Section 4.1 defines the generic message types common to all compliant systems.
Vehicle and payload specific messages may be formatted in a manner determined by
the designers of the VSM using any of the vehicle specific services defined in Section
1.7.5.1, Vehicle Specific Display Services. The VSM shall support the formatted DLI
messages where they are applicable to the air vehicle, which it supports.
The CUCS shall provide the services for displaying vehicle or payload specific data,
and for interpreting and displaying the information appropriately (such as in a
browser window). In all cases, vehicle or payload specific displays created at the
CUCS using such messaging shall be compliant with Appendix B3 (HCI).
1 - B - 328
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Vehicle and payload specific messaging shall use ports configured for either TCP/IP
or UDP/IP communications. In general, it is anticipated that TCP communications
will be commonly used for generating display information using commonly employed
GUI support tools that require TCP support. However, some vehicle or payloadspecific applications may require the support for streaming ephemeral data for which
UDP is preferable.
General Configuration Messages may be used to configure private messages as well
as the DLI defined messages.
1 - B - 329
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
5 Miscellaneous Interfaces.
5.1 Analogue Video Interface.
Interfaces for analogue video lie outside the scope of the DLI. In cases where video
data is transmitted to the ground in analogue format, the VSM shall provide services
to translate video into digital form consistent with STANAG 4609, 4545, or 7023 for
transport across the DLI. Where desired, the VSM may provide an analogue output
port for exporting analogue video (e.g., RS-170 format) to displays or other nodes. If
displays at the operator station require analogue input, a separate channel may be
established between the CUCS and VSM to transmit the data directly.
5.2 Digital Image Data Interface.
Digital payload data (still digital imagery, full motion digital imagery, SAR imagery,
etc.) shall enter the CUCS via the DLI interface. Digital payload data shall be
transferred to the CUCS using established NATO standards (STANAGs 7023, 4609,
4545, 4607, as specified in Annex B) for both communication protocol and physical
medium.
If bandwidth constraints permit, a physical interface between the CUCS and the VSM
can be shared for digital payload data and command and status data. Where
bandwidth requirements exceed capabilities of the Core-to-VSM physical interface, a
separate physical interface (e.g., a second Ethernet port) shall be established for
transfer of digital payload data.
Where necessary to satisfy system requirements, the CUCS shall provide the
functionality to annotate, display, and distribute digital payload data. The CUCS shall
also provide any necessary functionality to store, retrieve, and display digital payload
data.
Any payload-specific metadata that is associated with the digital payload data shall
be published on the same interface as the payload data in accordance with
applicable NATO standards. The metadata and payload data should be time tagged,
and share a common time reference. The resolution of the time tag shall be
sufficient to fully exploit the payload data. The contents of the metadata shall be
sufficient to process the payload data in downstream processes.
Digital motion imagery in MPEG-2 format shall be in accordance with STANAG 4609.
1 - B - 330
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
TAB B1 - 2: Modified DLI Generic Message and Private Message
Repository for UVs Edition 3
These non required modified DLI Generic Messages and Private Messages
are available to assist users in UAS as well as other UV platforms. The
Summary Table lists all captured messages received from CST members. The
actual messages are found in the following UV Type Tables. Due to the fact
that some messages can be used for multi-types of UVs, the CST Editor placed
individual messages in a suggested UV Type Table which seemed most
appropriate. An X in the last 4 columns in the Summary Table designates the
location of the actual messages in the UV Type Tables below. A * in the last 4
columns designates that the message may be applicable for that UV type. A
POC for each message is identified if you have further questions.
Summary Table
Msg
#
Description
Push/Pull
Source
Allowable
Max
Latency
(msec)
UAV Table
USV
Table
UUSV
Table
51000
Vehicle Lights
Push
CUCS
500
*
(Amphibious)
*
X
51001
Bilge Pump
Command
Push
CUCS
500
*
(Amphibious)
*
X
51002
Vehicle Lights
State
Push/Pull
VSM
500
*
(Amphibious)
*
X
51003
Bilge Pump
Report
Push/Pull
VSM
500
*
(Amphibious)
*
X
51004
Air and Ground

Relative States
Push
VSM
500
*
(Amphibious)
*
X
51005
Text Message
(Note:
Applicable to all
UV Types)
Push (3-5
Control) /
Pull (2-5
Monitor)
CUCS/VSM
1000
*
X
UGV
Table
1.0 UAV Group Messages.

1.1 Message# 51005: Text Message.
This message is used to send text messages between CUCSs via the AV.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51005.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
51005.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
51005.02
Destination CUCS
Integer 4
None
See Section 1.7.6
51005.03
Text Message
Character
160
None
No Restrictions
1 - B - 331
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Implementation Guide
The intent of this message is to allow text messages to be transferred between two
CUCS via the AV. An AV that receives this message could retransmit it to the
destination CUCS using the same message. The retransmission of the message
received by the AV will have both the To CUCS ID and the Destination CUCS set to
the same value. Retransmission could use an alternative downlink method.
2.0 USV Group Messages.
4.12.6 Message #51000: Vehicle Lights.
This message shall be used by the CUCS to control the vehicle lights.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51000.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
51000.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
51000.04
Set Lights
Unsigned 2
Bitmapped
0x0001 = Nav
0x0002 = NavIR
0x0004 = Strobe
0x0008 = StrobeIR
0x0010 = NVD
0x0020 = Anchor
0x0040 = Landing
0x0080 = LandingIR
0x0100 = Towing
0x0200 = Vehicle specific 1
Unsigned 3
None
No Restrictions

are commanded off.
51000.05
Activity ID
Table B1 - 210: Message #51000: Vehicle Lights

2.2 Message# 51001: Bilge Pump Command.
This message is used to control the bilge pumps.

Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51001.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
51001.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
51001.02
Bilge Pump Select
Unsigned 1
Enumerated
0 = All
1 - B - 332
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51001.03
Bilge Pump Mode
Unsigned 1
Enumerated
0 = Off
1 = Manual
2 = Automatic
51001.04
Activity ID
Unsigned 3
None
No Restrictions

2.3 Message# 51002: Vehicle Lights State.

This message is used by the VSM to report the state of the vehicle lights.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51002.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
51002.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
50002.04
Navigation Lights State
Unsigned 2
Bitmapped
0x0001 = Nav
0x0002 = NavIR
0x0004 = Strobe
0x0008 = StrobeIR
0x0010 = NVD
0x0020 = Anchor
0x0040 = Landing
0x0080 = LandingIR
0x0100 = Towing

are commanded off
2.4 Message# 51003: Bilge Pump Report.

This message is used to report the bilge pump status.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51003.00
Presence Vector
Unsigned 1
Bitmapped
No Restrictions
51003.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
51003.02
Bilge Pump Select
Unsigned 1
Enumerated
0 = All
51003.03
Bilge Pump Mode
Unsigned 1
Enumerated
0 = Off
1 = Manual
2 = Automatic On
4 = Automatic - Off
5 = Fault
1 - B - 333
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
2.5 Message #51004: Air and Ground Relative States.
This message is used to send the current state of the parameters defined in this
message from the vehicle to the CUCS.
Unique
ID
Field
Data Element Name &

Description
Type
Units
Range
51004.00
Presence Vector
Unsigned 3
Bitmapped
No Restrictions
51004.01
Time Stamp
Unsigned 5
0.001 s
See Section 1.7.2
51004.04
Angle of Attack
Integer 2
BAM
No Restrictions
51004.05
Angle of Sideslip
Integer 2
BAM
No Restrictions
51004.06
True Airspeed
Unsigned 2
0.05 m/s
x 1,500
51004.07
Indicated Airspeed
Unsigned 2
0.05 m/s
x 1,000
51004.08
Outside Air Temp
Unsigned 2
0.5 K
172.15 x 327.65
51004.09
U_Wind
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Unsigned 2
10 Pa
x 107,500
Integer 3
0.02 m
-1,000 x 100,000
Integer 2
0.05 m/s
-1,000 x 1,000

51004.10
V_Wind
51004.11
Altimeter Setting
51004.12
10
Barometric Altitude
Altitude based on Altimeter
Setting
51004.13
11
Barometric Altitude Rate

Estimated vertical velocity
(+ up) based on pressure
rate from air data system
51004.14
12
Pressure Altitude
Integer 3
0.02 m
-1,000 x 100,000
51004.15
13
AGL Altitude
Integer 3
0.02 m
-1,000 x 100,000
51004.16
14
WGS-84 Altitude
Integer 3
0.02 m
-1,000 x 100,000
51004.17
15
U_Ground
Integer 2
0.05 m/s
-1,000 x 1,000
Integer 2
0.05 m/s
-1,000 x 1,000
Unsigned 2
0.2 m
x 11,000

51004.18
16
V_Ground
51004.19
17
Depth Below the Keel
1 - B - 334
APPENDIX 1 to
Annex B to
STANAG 4586
Edition 3
Add Message #51004 Depth Below the Keel to Message #41000 Field Configuration
Integer Response list.
3.0 UUSV Group Messages.
4.0 UGV Group Messages.
1 - B - 335
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
APPENDIX B2 - COMMAND AND CONTROL INTERFACE
TABLE OF CONTENTS
1.1 Scope. ...................................................................................................................... 5
1.2 CCI General Overview............................................................................................. 5
1.3 Appendix B2 Overview. .......................................................................................... 7
1.4 Information Exchange Requirements. .................................................................. 7
1.5 Types of CCI Data. .................................................................................................. 8
1.6 Implementation of UAV LOI in the CCI.................................................................. 9
1.7 Strategy for Selection of CCI Standards............................................................... 9
2 CCI DATA DESCRIPTION. ............................................................................................. 10
2.1 Introduction. .......................................................................................................... 10
2.2 Tasking of the UCS. .............................................................................................. 10
2.3 Air Traffic Control (ATC)....................................................................................... 11
2.4 Collateral Data. ...................................................................................................... 12
2.5 Mission Plan. ......................................................................................................... 14
2.6 Handover Control.................................................................................................. 16
2.7 Mission Progress. ................................................................................................. 16
2.8 Resource Availability............................................................................................ 16
2.9 Payload/Sensor Data. ........................................................................................... 19
2.10 Target Data. ......................................................................................................... 23
2.11 Mission Reporting............................................................................................... 23
2.12 General Messages............................................................................................... 23
3 CCI DATA REPRESENTATION...................................................................................... 25
3.1 Introduction. .......................................................................................................... 25
2-B-1
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
3.2 Tasking of the UCS. .............................................................................................. 25
3.3 Air Traffic Control. ................................................................................................ 26
3.4 Collateral Data. ...................................................................................................... 27
3.5 Mission Plan. ......................................................................................................... 30
3.6 Handover Control.................................................................................................. 30
3.7 Mission Progress. ................................................................................................. 30
3.8 Resource Availability............................................................................................ 31
3.9 Payload/Sensor Data. ........................................................................................... 32
3.10 Target Data. ......................................................................................................... 34
3.11 Mission Reporting............................................................................................... 34
3.12 General Messages............................................................................................... 35
2-B-2
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
LIST OF FIGURES
Figure B2 - 1: UCS Interface Functional Architecture ................................................ 6
Figure B2 - 2: Types of CCI Data .................................................................................. 8
LIST OF TABLES
Table B2 - 1: Air Traffic Control Messages................................................................. 12

Table B2 - 2: AV Availability......................................................................................... 16
Table B2 - 3: Payload Availability ................................................................................ 17
Table B2 - 4: VDT Availability....................................................................................... 17
Table B2 - 5: Operational Status Data ......................................................................... 17
Table B2 - 6: UCS Availability Data ............................................................................. 18
Table B2 - 7: Launch System Availability ................................................................... 18
Table B2 - 8: Recovery System Availability................................................................ 18
Table B2 - 9: CDTs Availability .................................................................................... 18
Table B2 - 10: Other Unit Resource Availability Data ................................................ 19
Table B2 - 11: Payload and Sensor Type with CCI Output........................................ 20
Table B2 - 12: ADatP-3 Tasking Messages ................................................................. 26
Table B2 - 13: ADatP-3 Airspace Control Messages.................................................. 26
Table B2 - 14: ADatP-3 General Battlefield Picture Messages.................................. 27
Table B2 - 15: ADatP-3 Mission Dependent Data Messages..................................... 28
Table B2 - 16: ADatP-3 CBRN Data Messages ........................................................... 29
Table B2 - 17: ADatP-3 Artillery Target Intelligence Messages ................................ 29
Table B2 - 18: ADatP-3 Meteorological Data Messages ............................................ 29
Table B2 - 19: ADatP-3 Mission Report Message....................................................... 31
Table B2 - 20: ADatP-3 Air Segment Status and Operational Capability
Messages ............................................................................................................... 31
Table B2 - 21: ADatP-3 Ground Segment Status and Operational Capability
Messages ............................................................................................................... 32
Table B2 - 22: Imagery Standards ............................................................................... 32
Table B2 - 23: ADatP-3 CBRN Data Messages ........................................................... 34
Table B2 - 24: ADatP-3 Mission Results Messages ................................................... 35
2-B-3
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Table B2 - 25: ADatP-3 General Messages ................................................................. 36
LIST OF ATTACHMENTS
Attachment B2 - 1: Information Exchange Requirements........................................ 37
Attachment B2 - 2: APP- 11 Message Implementation Requirements .................... 51
Attachment B2 - 3: UAV System LOI APP- 11 Requirements .................................. 71
Attachment B2 - 4: UAV Custom Tags.........................................................................80
2-B-4
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
1 Introduction.
1.1 Scope.
STANAG 4586, Annex B Appendix B2 specifies the Command and Control Interface
(CCI) between the Core Unmanned Aerial Vehicle (UAV) Control System (CUCS)
and Command, Control, Communication, Computer, & Intelligence (C4I) systems.
Standardisation of the CCI is intended to enable NATO nations to achieve
interoperability between UAV Systems and C4I users by the implementation of a
common set of generic interface standards. A standard CCI should facilitate
seamless integration of NATO UAV systems into joint combined C4I infrastructures
across all levels of interaction.
The purpose of Appendix B2 is to specify standards covering command, control, and
data transmission and receipt from all external systems that need to communicate
with the CUCS. These standards will lead to the enablement of interoperability
between all present (legacy systems) and future UAV systems and designated C4I
systems. This appendix specifies standards to be implemented in the CUCS, and
does not impose any requirements on C4I systems.
1.2 CCI General Overview.
The CCI is an interface between the CUCS and the external C4I systems. It specifies
the data requirements that should be adopted for communication between the CUCS
and all C4I end users through a common, standard interface. Figure B2 -1 illustrates
the CCI within the UCS functional architecture.
All types of data or information that need to be formally exchanged between the
CUCS and the external C4I systems shall be defined in accordance with the
standards specified in this Appendix.
The CCI is intended to cover all types of messages and data that need to be
exchanged in both directions between the CUCS and the C4I systems during all the
phases of a UAV mission, including:
Before the flight: tasking messages, tactical situation, environmental data,
general mission constraints and mission plans.
During the flight: status and service messages, payload data, progress
reports
After the flight: status and service messages, payload data, post-flight
exploitation reports, mission reports
The format of all data passing across the CCI is defined in this appendix but a UCS
implementation or connected C4I system may use other formats provided format
translations take place in accordance with the CCI definitions:
A UCS implementation may be CCI compliant with the CUCS retaining its
own, possibly non-standard internal data representation, for example, for
processing efficiency. Appendix B2 allows CUCS developers to identify data
that has to be generated or accepted by the CUCS software in order to be
CCI compliant.
2-B-5
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Many C4I systems, particularly legacy systems, may not directly comply with
the CCI standards specified in this appendix. To avoid both proliferation of the
number of standards specified in the CCI and modifications to the large
number of national or joint C4I systems to be connected to CUCS, conversion
software and/or hardware will be necessary between the CCI and
incompatible C4I systems. This conversion software/hardware is depicted in
Figure B2 -1 and is called the Command and Control Interface Specific
Module (CCISM). The CCISM may form part of a particular UCS
implementation to establish a connection between the CUCS and specific
customers of the UAV system (e.g., one or more C4I systems). The CCISM,
when needed, can range in complexity from a simple format or protocol
translator to a user-specific application to adapt the type of information to
particular C4I requirements.
AV
LAUNCH &
RECOVERY
SYSTEM
UCS
VSM
DLI
CCI
HCI
CORE
UCS
OPERATOR
CCI
CCISM
C4I
SYSTEM
C4I
SYSTEM
Figure B2 - 1: UCS Interface Functional Architecture
The CCISM is mainly intended for communication with legacy C4I systems that are
not directly compatible with STANAG 4586 specified standards, protocols or physical
layer. When future C4I systems are developed it is expected that they will be
2-B-6
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
STANAG 4586 compliant in which case there will be a direct link without the need for
an intermediate CCISM.
This appendix does not address either the hardware needed for information
exchange between the CUCS and the CCISM or the architecture and design of the
CCISM itself. Design, development and fielding of specific CCISM functionality,
when needed, will be the responsibility of either the UAV system or the applicable
C4I program office.
Also, it is recognised that some communication will take place between the UCS and
C4I systems via voice or email. As these methods are inherently unstructured, they
fall outside the scope of this STANAG, apart from the need to conform to the
requirements of the NATO Interoperability Standards and Profiles (NISP), cited in
Annex B, to ensure that such communications can take place.
1.3 Appendix B2 Overview.
Appendix B2 is divided into the following sections:

Section 1:
Introduction: Provides a general introduction of the CCI
architecture and gives a brief system overview.
Section 2:
CCI Data Description: Identifies and describes the data
exchanged between the CUCS and the C4I systems. This section
concentrates on the description of the information to be transferred across the
CCI without specification of data formats.
Section 3: CCI Data Representation: Defines the data formats that should be
implemented in an implementation of the CCI. This chapter covers message
formats, file formats, data exchange standards, applicable transfer media and
protocols.
Attachment B2-1: Information Exchange Requirements: Lists the information
exchange requirements for communications between the CCI and external
systems.
Attachment B2-2: Allied Procedural Publication-11 (APP-11) Message
Implementation Requirements: Lists the set of messages that are to be
transferred across the CCI. These messages are a sub set of STANAG
7149, NATO Message Catalogue APP-11.
Attachment B2-3: UAV Level of Interoperability (LOI) APP-11 Requirements:
Allocates the ADatP-3 messages from APP-11 to achieve each LOI, where
suitable at the lowest level.
Attachment B2-4: UAS Custom Tags. Provides the background, definition,
and structure of a standard set of identifies for extending the Common Route
Definition (CRD) to enable full UAS mission planning.
1.4 Information Exchange Requirements.
The Information Exchange Requirements (IERs) define the generic data types,
criticality of the data, receiving and transmitting nodes, and format of the data that
need to be exchanged between the CUCS and the various types of C4I systems, as
well as other CUCSs, to support the operational user mission needs. These IERs,
provided in Attachment B2-1 of this appendix, identify the information exchange that
2-B-7
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
needs to take place between the CUCS and the external C4I systems to achieve the
operationally required feasible LOI according to the UAV systems Concept of
Operations (CONOPS). The identification and definition of messages to satisfy these
requirements is provided in Sections 2 and 3 of this appendix.
1.5 Types of CCI Data.
Figure B2 - 2 depicts the top level of the IERs exchanged between the CUCS and the
external C4I systems. Further breakdown of these top level IERs is presented in
Attachment B2 -1.
CCI
T asking
Air T raffic Control
Collateral Data
M ission Plan
UCS
Core
Handover Control
M ission Progress
Resource Availability
Payload/Sensor Data
T arget Data
CC ISM
C4I
System s
(If needed,
otherwise
goes direct
to C4I
systems)
M ission Reporting
Figure B2 - 2: Types of CCI Data
These data types are described in Section 2 of this appendix, and are summarised
below:
Tasking - UAV tasking messages as received from the appropriate tasking
authority.
Air Traffic Control (ATC) - Data that should be sent or received from civil or
military aviation authorities if the UAV has to pass through civil airspace.
Collateral Data - Supporting information that is required for the planning and
execution of UAV missions, and which is not defined in the other data areas.
2-B-8
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Mission Plan - As generated for a tasked mission.

Mission Plans are
imported and exported from the CUCS using CRD file formats.
Mission Progress - Status as the UAV mission is in progress.
Resource Availability - Status of the sub components of the UAV system.
Payload/Sensor Data - Data received from the UAV payload(s), may be raw,
processed or exploited.
Target Data - Near real time target location data for targeting purposes.
Mission Reporting Information on the outcome of a mission.
1.6 Implementation of UAV LOI in the CCI.
For an implementation of the UCS to achieve a required LOI, Levels 1 through 5, it is

necessary for the CCI to specify which different data types are mandatory to achieve
a given LOI and above. This is specified in Section 3 and Attachments B2 - 1 and B2
- 2 of this appendix.
However, this does not cover the requirements of particular national and/or NATO
concepts of operation for different types of UAV systems that may override the
necessity to include particular types of data. For example, Section 3.3 states that
ATC messages are mandatory to achieve LOI 4 and 5. This may not be appropriate
for a UAV that will never use civil airspace, such as a short range tactical UAV, but
which is nevertheless required to achieve LOI 4. Operating procedures will vary
according to individual national and NATO requirements and are therefore outside
the scope of this STANAG. Therefore, use of the term mandatory in connection with
LOI in this appendix shall be interpreted to include the phrase provided that
operating procedures require the exchange of this type of data.
1.7 Strategy for Selection of CCI Standards.
The approach taken in the selection of standards for each type of data given in
Section 1.5 has been:
To identify existing NATO standards as specified in various STANAGs and
other NATO publications.
Where such NATO standards do not exist, identify other military or
commercial standards that are applicable to that data type.
Analyse the candidate standards to ensure they meet the requirements of all
types of UAV systems.
Where choices may be made, for example in the selection of APP-11
messages, the selected items are given (e.g., the standard is profiled).
Priority has been given to existing NATO standards wherever possible. In some
cases, there is a likely future standard that is applicable to some of the data types.
Such future standards cannot be specified at this stage as they may change or never
be adopted. In these cases, an existing standard has been used, (e.g. APP-11), with
a switch to the future standard intended for the future.
2-B-9
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2 CCI Data Description.
2.1 Introduction.
This section provides a description of each of the data types exchanged between the
CUCS and the C4I system, potentially via a CCISM if the C4I system is not
compatible with specified CUCS formats and standards.
2.2 Tasking of the UCS.
The CUCS is expected to receive and respond to tasking orders, pre-planned

mission plans and mission plan changes requiring dynamic retasking (change of a
pre-planned mission after it has been uploaded to the UAV). The response to the
tasking order will be a mission plan which may be passed across the CCI interface to
higher levels of the command and control structure for deconfliction and approval.
(See Section 2.5 for a description of the mission plan.)
Tasking messages defined in STANAG 7149 are appropriate for tasking UAV
missions within the UCS. It is assumed that the UCS mission planner will be
designed to support multi-UAV operations (two or more UAVs flying simultaneously),
therefore the CUCS should be able to receive multi-mission tasking.
In a given UCS, particularly smaller systems, tasking may be received by voice or email messages. These are outside the scope of this STANAG with the exception that
e-mail message applications shall be in compliance with NATO Interoperability
Standards and Profiles (NISP) as specified in Annex B.
The CCI shall also support the capability for dynamic re-tasking of the UAV (e.g.,
changes to either the route or the payload plan). These changes may be required
during all phases of an operation.
2.2.1 Tasking.
The most prevalent method of tasking a UAV system is by the use of an Air Tasking
Order (ATO) which is common to all air missions, manned and unmanned, across
multi-national forces and multi-service operations.
The ATO is an APP-11 message that may be very large and complex, possibly
several hundred pages in size, not all of which will be applicable to UAV systems.
There are other messages in the APP-11 that do not form part of an ATO and that
may be used to task individual UAV systems or payloads. An example is the
Electronic Warfare Requesting/Tasking Message (EWRTM). The complete list of
these tasking messages is given in Section 3.2.1.
2.2.2 Airspace Control.
Airspace Management (ASM) is the activity of structuring the airspace and

scheduling its use. In the military airspace management system the airspace is
structured through the specification of Airspace Control Means (ACM) which defines
airspace volumes, surfaces and lines, and specific rules for the use of the resulting
airspace partitions. The ACMs approved for a given period of time are promulgated in
the APP-11 Airspace Control Order (ACO). The ACO is based upon the air
operations and airspace usage requirements of other Air Command and Control
2 - B - 10
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Systems (ACCS), non-ACCS tri-service entities, civil requirements and airspace
requests, together with constraints imposed on the use of that airspace.
The ACO allows the separation of all types of aircraft, manned and unmanned, fixed
and rotary wing, by the definition of altitude layers, geographic zones and
surveillance systems. The ACO defines how a volume of airspace is to be structured
for air missions over a given period. The ACO defines how this division of airspace
will be used by different air operations throughout the 24-hour ACO cycle.
Therefore, for mission planning, a UCS requires the ACO to define the constraints on
the route to be flown by the UAV.
2.3 Air Traffic Control (ATC).
When a UAV, particularly a long range strategic UAV, has to pass through controlled
airspace, it is necessary to file a flight plan with civil aviation authorities.
The International Civil Aviation Organisation (ICAO) publishes a document that
specifies the content of all messages that have to be submitted to ATC authorities
before, during and after flights. This document is the Rules of the Air and Air Traffic
Services, DOC 4444-RAC/501, latest edition.
The messages may be sent as appropriate and desired over voice channels, by
completed paper forms or electronically. Voice messages and paper forms are
outside the scope of the CCI, hence only electronic messages are considered below.
There are two types of electronic messages specified by the ICAO, Air Traffic
Services (ATS) and Automatic Dependent Surveillance (ADS) messages. ADS
messages are sent from the air platform via a data link to an ATS unit covering the
airspace in which the platform is flying, hence these are not applicable to the UCS
and not considered further. However, in order to be compliant with ICAO regulations,
the Air Vehicle (AV) should carry a compatible Identification Friend or Foe (IFF)
device (e.g., Mode S IFF).
The content and formats of ATS messages are given in Appendix 3 of the above
ICAO document. This STANAG does not mandate the use of these messages
because they will not be required for some UAV systems (e.g., small UAVs), but
does require that, if generated in a particular system, the ICAO format should be
used.
The ATS message types are listed in Table B2 1:
2 - B - 11
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Message Type
Description
Alerting
Contains a description of an
emergency
Category
Emergency
Filed flight plan

and associated
update
Coordination
(Note)
Radio communication
failure
Filed flight plan
Modification
Cancellation
Delay
Departure
Arrival
Current flight plan
Estimate
Coordination
Acceptance
Supplementary
Logical
acknowledgment
Request flight plan
Request supplementary
flight plan
Supplementary flight
plan
Changes to a flight plan

Cancellation of a flight plan
If departure is delayed
Actual departure time
Actual arrival time
Flight plan plus estimated time at
a boundary point
Estimated time at a boundary
point
Amendment to coordination data
Acceptance of the current flight
plan, estimate or coordination
message
Computer to computer
acknowledgment
Fuel endurance, frequencies

available, aircraft markings +
others irrelevant to UAVs
Table B2 - 1: Air Traffic Control Messages
Note: Coordination messages are for handing over control from one ATC centre to
the next during a flight.
2.4 Collateral Data.
2.4.1 General Battlefield Picture.
Both enemy and own tactical situation can be exchanged between C4I systems and
the UCS. This information is carried by messages, which are both incoming and
outgoing. Knowledge of the position of own and enemy forces is useful within the
2 - B - 12
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
UCS to allow the operators to understand the context of the required mission and to
optimise the flight plan. Reciprocally, the UCS may use the results of image
exploitation to update the local tactical situation (by generating tactical symbols
related to observed targets) and to export it through intelligence networks or to upper
levels of command.
Information on the tactical situation shall be obtained and reported by use of relevant
APP-11 messages, particularly the Enemy Situation Report (ENSITREP) and Own
Situation Report (OWNSITREP).
2.4.2 Mission Dependent Data.
Some information on the tactical situation may be obtained via additional APP-11
messages that are specific to particular missions and/or payloads. An example of this
is the Meaconing, Intrusion, Jamming, and Interference (MIJI) Warning Report which
provides information on hazardous Electronic Warfare (EW) situations. A full list of
this type of message is given in Section 3.4.2.
2.4.3 Chemical, Biological, Radiological and Nuclear (CBRN).
The CBRN situation is handled by a set of specific CBRN reports that are received by
all units on the battlefield (see Section 3.4.3). These are needed by a CUCS both as
a hazard warning and to carry out mission planning for CBRN payloads.
2.4.4 Artillery Targeting.
A UCS can support artillery operations such as target acquisition and firing support.
Information has to be exchanged between the UCS and the artillery networks.
2.4.5 Meteorological Data.
Meteorological data may be required for UAV mission planning. This includes
information related to wind (direction and speed), visibility, significant current and
forecasted weather, amount of turbulence, cloud cover, cloud base altitude, cloud top
altitude, temperature, and barometric pressure. This is available via the APP-11
messages listed in Section 3.4.5 or via international meteorological data.
2.4.6 Image Products.
There will be a requirement for the operator to read imagery and image products,
which are relevant to the area of operation, from external C4I systems. Such
collateral material could be needed, for example, for detailed mission planning or
image exploitation. It is expected that these image products will be accessed from
one of a number of image libraries (IL) held by various NATO or coalition nations.
STANAG 4559, the NATO Standard Image Library Interface (NSILI), exists to
standardise access to such image libraries.
The CUCS may be connected to a network to allow file transfers from the external
ILs to the CUCS using the software interface specified in STANAG 4559.
Once the operator is logged on to the external ILs, NSILI specifies query and read
transactions with ILs. Defining mechanisms for writing image products into an IPL is
the responsibility of the IPL owner and is outside the scope of STANAG 4586.
Therefore, if it is desirable to deposit imagery data into the NATO releasable IL, the
2 - B - 13
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
CUCS should follow the protocols established by the nation's IL and defined by the
external C4I system that provides this capability. This protocol is typically provided
as an FTP transfer of the imagery file data to a preconfigured directory accessible
over the network.
NSILI specifies image product formats. Delivery of image products will be via the
LAN in the majority of cases, but NSILI also permits delivery via other media. If
products are delivered on magnetic tape the media will conform to STANAG 7024 or
STANAG 7025. This will require storage devices conforming to STANAG 7024 or
STANAG 7025 to be provided in an implementation of the UCS.
2.5 Mission Plan.
2.5.1 General Considerations.
Mission planning for UAV systems consists of route planning, payload collection and
dissemination planning, communication planning (including frequency planning), and
UAV contingency planning (rules of safety). The combined results of these five items
comprise the mission plan.
It should be noted that the data required to be able to generate a mission plan is
normally far more than contained in these items. A detailed knowledge of current
Phase and Boundary lines, Engagement Areas, Hazards, Air Defence Units (ADU)
and Control Measures is also required. This information is already covered in the
collateral data section of this document.
Pre-planned missions may also be provided across the C4I interface in the form of a
mission plan that has been developed by another UAV planning system. Mission
Plans are imported into the UCS using the CRD file format.
The mission planner also requires vehicle performance models for UAVs controlled
by the UCS to calculate fuel consumption, climb rates etc. These performance
models will be included in the Vehicle Specific Module (VSM), described in Appendix
B1, Data Link Interface.
Other functions that may be available in a mission planner are the ability to do radar
shadowing and line of sight evaluations and to show confliction and inter visibility
between points and routes. These calculations require knowledge of ADU/Radar
characteristics and the plans of other users.
Planning for designator operations will also require a means of coordination/
implementing of Laser Codes and Keywords.
The capability should exist within the UCS (HCI) to provide the mission plan, or
components of the mission plan, as hard or soft copy as required. The outputs from
a mission planner may also include printouts of instructions for loading the UAV (e.g.,
fuel type and amount, sensor/designator settings, and communications frequencies).
2.5.2 Dissemination of the Mission Plan.
The mission plan needs to be sent to different recipients at various times, these
include:
The tasking authority, immediately after generation of the mission plan, for
airspace deconfliction and approval
2 - B - 14
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
The air vehicle via the Data Link Interface (DLI) for those UAVs that can
autonomously execute a mission plan
To another UCS for handover of UAV control via the DLI
The CRD data format will be used for each transfer of the mission plan data. It should
be noted that there is a difference between mission plans and mission reporting:
CRD is used for mission plans and APP-11 is used for mission reporting. However it
is recognised that not all recipients will require the full mission plan. For those
systems it will be possible to extract only the necessary parts. Note that UCS-to-UCS
transfer requires the ability for a UCS to receive a mission plan.
ATC is excluded from the list of recipients as there are existing civil flight plan
formats (see Section 2.3) that are adequate for UCS mission plan formats.
2.5.3 Route Planning.
Route planning may be done at the UCS or passed from an external agency. This
agency may be Headquarters, another UCS, or come from an intermediate level. A
route plan from Headquarters may require additional tactical information to be built
into it at the squadron of the Forward Operations Base (FOB) to make it compatible
with the current state of the battle space. The instructions might be very detailed,
where information about a specific target is required or may be instructions for a
Reconnaissance, Intelligence, Surveillance and Target Acquisition (RISTA) type
operation and specify only an area of operations. When a route plan comes from
another UCS this may be a UAV handover operation with detailed route and
instructions or may be a plan generated at another UCS for use by other operators.
A route plan will comprise a set of waypoints. These waypoints may have different
parameters, which drive the action to be taken when a waypoint is reached. Flight
patterns may be incorporated into the route either as a series of sequenced
waypoints or as seed waypoints with range and bearing information, which will
depend on the sophistication of the UCS and UAV systems.
2.5.4 Payload Planning.
Payload planning includes details of how a specific payload is to be used. The details
of planned payload operations will be incorporated into the payload collection plan
and a payload dissemination plan, and will be associated with waypoints in the route.
2.5.5 Communication Planning.
Communication planning includes the details of the data links, bands, and
frequencies to be used (e.g., see Section 3.2.1 Tasking, of this appendix). Data link
planning needs initial assignment provided by C4I (e.g., through the OPTASK LINK
message) and leads to a set of configuration data that is used by the mission
planner. This is sent to the DLI for data link configuration (see Appendix B1, Data
Link Control Command).
2.5.6 Contingency Planning.
In case of failures such as data link loss, UAVs need to automatically carry out
recovery actions referred to as Rules of Safety (ROS). The ROS are selected at the
mission planning stage. The ROS differ according to the priority given to emergency
2 - B - 15
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
action relative to that given to mission execution. Using the mission planning
application, the UCS operator selects the appropriate safety scenario (e.g., to define
a pre-programmed recovery route).
2.6 Handover Control.
This section deleted.

2.7 Mission Progress.
This data is required primarily to inform higher levels of command about the progress
of the mission. This includes information on the air vehicle position, status of onboard equipment, fuel levels and ongoing achievement of mission goals.
The
ADatP-3 defined message, Mission Report (MISREP), amplified by accompanying
text with a RMKS set will be used to report this information.
2.8 Resource Availability.
The CCI will have the capability to provide, as well as receive, the status and
operational capability of the sub-components of the UAV system. This will include
both the Air Segment and the Ground Segment of the UAV system as specified in the
following paragraphs. Message J003, GENINFOMSG, from the APP-11 catalogue,
may be used for this purpose.
2.8.1 Air Segment Status.
The status and operational capability of the air segment of the UAV system will
consist of data relevant to the air vehicle(s), the payload(s), and the air data link(s).
The following types of data will be incorporated into the resource availability reporting
process:
2.8.1.1 Air Vehicles (AV)
Total number of AVs assigned

UAV type
Number of UAVs of this type
(Repeated for each UAV
AV configuration
Tail number
type)
(repeated for each UAV of AV status (see 2.8.1.4)
this type)
AV operational state (see
below)
Table B2 - 2: AV Availability
AV operational state is one of:
Airborne - Executing a mission
Ground alert - Ready to fly and execute a mission
Airborne alert - In flight and awaiting a mission
2 - B - 16
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.8.1.2 Payloads.
Total number of payloads

Payload type
(Repeated for each
payload type)
Number of payloads of this type

Payload Configuration
Payload ID(Repeated for
each payload)
Payload Status (see
2.8.1.4)
UAV Tail number
Table B2 - 3: Payload Availability

2.8.1.3 Vehicle Data Terminals (VDT).
Total number of VDTs

VDT Type
(repeated for each VDT
type)
Number of VDTs of this type

Status (repeated for each
type)
Primary link status (see

2.8.1.4)
Secondary link status (see
2.8.1.4)
Table B2 - 4: VDT Availability

2.8.1.4 Status Table.
This table shows the status data that will be used for status entries in the tables in
Sections 2.8.1 and 2.8.2.
Fully Operational
Limited Operational
Reasons/Limitations
Estimated Time of Return to Full Ops
Number Non-Operational
Reasons
Estimated Time of Return to Full Ops
Table B2 - 5: Operational Status Data

2.8.2 Ground Segment Status.
The status and operational capability of the ground segment of the UAV system will
consist of data relevant to the UCS(s), the launch system(s), the recovery system(s)
the ground data link(s), and the maintenance and refurbishing system(s). The
following types of data will be incorporated into the resource availability reporting
process:
2 - B - 17
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.8.2.1 UCSs.
Number of UCSs available to support UAV operations

UCS ID (Repeated for
each UCS)
UCS Configuration (including AV Types supported, and

LOI)
UCS Status
(see 2.8.1.4)
CCI Dissemination
Capability
C4I Products Supported

C4I Systems Supported
Table B2 - 6: UCS Availability Data

2.8.2.2 Launch Systems.
Number of launch systems available to support UAV operations

Launch System ID
(repeated for each launch
system)
Launch System Configuration (including AV Types

supported)
Launch System Configuration (including AV Types
supported)
Status
(see 2.8.1.4)
Table B2 - 7: Launch System Availability

2.8.2.3 Recovery Systems.
Number of recovery systems available to support UAV operations

Recovery system ID
(repeated for each
recovery system)
Recovery System Configuration (including AV Types

supported)
Status
(see 2.8.1.4)
Table B2 - 8: Recovery System Availability

2.8.2.4 Control Data Terminals (CDT).
Number of CDTs available

CDT type (repeated for
each CDT type)
Number of CDT type available

Link status (repeated for
each CDT type)
Primary (see 2.8.1.4)

Secondary (see 2.8.1.4)
Table B2 - 9: CDTs Availability
2 - B - 18
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.8.2.5 Maintenance and Refurbishing Systems.
Type of replaceable unit (repeated for

each type)
Number of each type held
Fuel availability
Personnel Availability to Perform Maintenance
Table B2 - 10: Other Unit Resource Availability Data
2.9 Payload/Sensor Data.
2.9.1 Overview.
Sensor data may be received from the air platform in a variety of formats depending
on the type of UAV and sensor. Where possible, the formats used to transmit data
from the CUCS to the C4I systems across the CCI will use existing international
standards (NATO or commercial) so as to minimise the number of formats used in
the CCI and by the receiving C4I systems. It is impossible to cover all existing and
future types of payloads because of the rate of change in sensor technology.
Therefore, only the most common types of sensors have been considered to date;
and specific UCS implementations may need to convert from a particular sensor data
format to the CCI required data format if the two do not match.
The types of payloads, possible sensor outputs via the CCI, and maturity of current
standards addressed in this version of the STANAG are summarised in Table B2 11
below.
Note: If a specific UAV system does not support a particular payload type (e.g.,
GMTI, ELINT, etc.), the supporting UCS can still be STANAG 4586 compliant without
having to implement those requirements associated with that particular payload.
2 - B - 19
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Payload Type
Sensor Type
CCI Output
Imagery
EO/IR/MSI/HSI
TV camera
EO/IR/MSI/HSI
Line scanner
EO/IR/MS/HS
Photo (framing)
sensor
Synthetic Aperture
Radar
(SAR)
Motion/Still image
Signals
Intelligence
(SIGINT)
Electronic
Warfare (EW)
Chemical,
Biological,
Radiological
and Nuclear
(CBRN)
Laser
designator/
range finder
Communication
relay
Stores/Weapon
Radar
Moving Target
Indicator (MTI)
Electronics
Intelligence
(ELINT/ESM)
Communications
Intelligence
(COMINT)
Jammer
Continuous
image/Still image
Still image
Spot
Swath (Area
Search)
Vector data
Signal data
Dissemination
reports
Signal data
Dissemination
reports
None
Applicable
Standards
STANAG 4545,
7023, 4609
STANAG 4545,
7023
STANAG 4545,
7023
STANAG 4545,
7023
STANAG 4545,
7023
STANAG 4607
STANAG 4633
STANAG 4633
TBD
TBD
N/A
Detectors
Dissemination
reports
STANAG 7149
(CBRN 1 BIO,
CHEM, RAD, NUC)
N/A
None
N/A
N/A
None
N/A
N/A
None
N/A
Table B2 - 11: Payload and Sensor Type with CCI Output
It is recognised that there will be requirements to receive unprocessed (raw) sensor

data from particular UAV payloads (for example unprocessed SAR) that may need to
be transferred to an external system (for example for exploitation). Such data is likely
to be in a proprietary non-standard format, therefore it is outside the scope of the CCI
standard and not considered further in this appendix.
Those payloads that provide data to be disseminated via the CCI are described
below.
2 - B - 20
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.9.2 Imagery.
2.9.2.1 Electro/Optical Imagery.
Electro/optical imagery consists of visible, infrared as well as multispectral/
hyperspectral imagery. Multispectral and hyperspectral images consist of multiple
images from different parts of the electromagnetic spectrum.
2.9.2.1.1 Digital Still Imagery.
2.9.2.1.1.1 Framed.
A framed image is a single rectangular image of a predefined size. The still image
can be a standalone image or combined with annotations, symbology and descriptive
text. The dimensions of the image are only limited by sensor characteristics.
STANAG 7023 and 4545, respectively, are the controlling standards for these types
of payloads.
2.9.2.1.1.2 Scanned.
Scanned images are typically produced by line scan sensors and the image forms a
continuous strip. In this case, the complete image is of indefinite length and the
image may cover an irregular path according to platform route, sensor viewing angle
etc. STANAG 7023 and 4545, respectively, are the controlling standards for these
types of payloads.
2.9.2.1.2 Motion Imagery.
2.9.2.1.2.1 Analogue Video.
Analogue video is a product that is provided by many legacy UAV systems, and also
required as an input by some legacy C4I systems. If analogue video is required by a
C4I system, it shall be obtained either directly from the VSM (if analogue video is a
direct output from the air vehicle to the VSM), or via the CCISM, if format and/or
protocol conversion is required. Note that as a function of CCISM design, analogue
video can be output from the CCISM in any of the international standard formats
desired, and can also include encoding of telemetry metadata within the analogue
video stream in a closed caption format.
(Note: The CUCS has a requirement to process digital video, but not a requirement
to process analogue video. If analogue video is received from the air vehicle, it can
be distributed directly to the C4I system from the VSM, and will also be transformed
by the VSM into digital video in accordance with STANAG 4609 for processing within
the CUCS. If digital video is received from the air vehicle, it can be processed within
the CUCS; and if a C4I system requires analogue video, a CCISM will be necessary
in order to take the digital video as processed inside the CUCS, and convert it into
the analogue video product required).
2.9.2.1.2.2 Digital Motion Imagery.
Digital motion imagery will be output from the CCI as specified in STANAG 4609,
with applicable KLV metadata as specified in MISB Standard 0601, MISB Standard
0902 and MISB Standard 0102.
2 - B - 21
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.9.2.2 Radar.
2.9.2.2.1 Synthetic Aperture Radar (SAR).
SAR data that has been processed on the platform or in the CUCS will be transmitted
across the CCI using the same standards as for EO/IR images.
There may be systems (possibly legacy systems) that require SAR processing to be
carried out in an external ground station and therefore require the unprocessed data
to be transmitted from the CUCS. As stated above, this is considered to be nonstandard data and is outside the scope of the CCI standard until such time as a
standard for this data has been defined.
2.9.2.2.2 Ground Moving Target Indicator (GMTI).
Processed GMTI data gives the position and velocity of moving targets and hence
consists of a set of target vectors.
GMTI data will be transmitted in accordance with STANAG 4607.
2.9.3 Signals Intelligence (SIGINT).
2.9.3.1 ELINT.
The CUCS will handle SIGINT data and reports generated from processed SIGINT
data. Cooperating airborne platforms require that data be fused to generate SIGINT
information. This fusion may take place inside a CUCS. Therefore, this data should
be transmitted to and from the CUCS. SIGINT reports may be generated in the
CUCS for transmission to a user via the CCI.
2.9.3.1.1 ESM.
ESM data is derived from analysis of enemy electronic signals and is not included in
this issue of the CCI standard as there are no agreed standards to transmit the
information. If suitable standards are defined in the future they will be included within
the CCI.
2.9.3.2 Communications Intelligence.
Future Capability.
2.9.4 Electronic Warfare.
Future capability
UAVs can carry a large set of CBRN detectors. Results of CBRN detection will be
transmitted across the CCI through standard CBRN reports (see Section 3.9.5). This
assumes that information required within these reports is generated on board the
platform or within the CUCS. The CCI will not include unprocessed CBRN
measurements as there is no known standard format for this data.
2.9.6 Other Payload Types.
2.9.6.1 Laser Designator/Range Finder.
Future capability
2 - B - 22
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
2.9.6.2 Communication Relay.
Future capability
2.9.6.3 Stores/Weapons.
Future capability
2.10 Target Data.
Near real time target data transmission across the CCI has not been included in this
issue of the CCI. Target reporting requires a commander to approve the target and
issue authority to fire. Concept of Operations is currently under development, and
this issue may be addressed in a future update to STANAG 4586.
2.11 Mission Reporting.
The CUCS will provide the various C4I systems with payload dependent products;
including, but not limited to, payload reports, mission status, mission progress and
mission reports. This information may have to be provided on a routine basis during
the flight of the UAV, on completion of the mission, on demand, or when specified
threshold criteria are met.
Selected C4I systems may be supplied with one or more of the following types of
reports:
Reports derived from sensor processing and/or exploitation
Mission status reports. In any kind of emergency or unexpected mission
event,
the
ADatP-3
defined
General
Information
Message
(GENINFOMSG) may be used to provide information, which cannot be
provided using existing ADatP-3 message text formats. This is a special
message used for unusual circumstances that cannot be anticipated or
planned, and should not be used on a routine basis. It is not intended to
replace existing messages described in Section 2.8.
Mission Progress reports. The ADatP-3 defined message MISREP may
be used to report mission results and items of intelligence interest in all
tactical roles. It may also be used to retransmit and/or amplify in-flight
reports. The INFLIGHT REPORT (F095) message as well as the
INFLIGHTREP (voice template, usually for immediate passing of
information from flight crew/pilot to ground stations) can be used as well.
Final Mission Report. On completion of the mission.
A number of ADatP-3 defined message reports, as listed in Section 3.11, will be used
for these types of reports as appropriate.
2.12 General Messages.
There are numerous messages contained in STANAG 7149, NATO Message

Catalogue APP-11. Several of these messages are germane to overall UCS C2
functionality and operational mission accomplishment (e.g., operational environments
ranging from peacetime to Military Operations Other Than War to Wartime), but do
not appropriately fit into the message categories previously discussed. Those
2 - B - 23
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
messages that are deemed appropriate for UCS operations, but have not been
identified in previous sections, are listed in Section 3.12.
2 - B - 24
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
3 CCI Data Representation.
3.1 Introduction.
This section defines which standards are to be used for the data types described in
Section 2. Where an ADatP-3 message format from the APP-11 is mandated, a fuller
description of that message and the applicable LOI is contained in Attachment B2-2.
Some of these ADatP-3 messages are designated optional and may be included as
required by a particular CUCS; they are included below for completeness. CUCS
shall provide capability to display to the operator all messages received as defined in
the following paragraphs. For purposes of this edition of STANAG 4586, the ADatP3 messages mandated shall be interpreted to mean APP-11 messages from the
current edition of the Message Catalogue.
3.2 Tasking of the UCS.
3.2.1 Tasking.
The CUCS shall be capable of processing the following message formats in order to
accomplish the Tasking function:
Index
Identifier
Format Name
A033
FM.CFF
FIRE MISSION-CALL FOR FIRE
A034
FM.SUB
FIRE MISSION-SUBSEQUENT ADJUSTMENT
A035
FM.MTO
FIRE MISSION-MESSAGE TO OBSERVER
A036
FM.FMC
FIRE MISSION-FIRE MISSION COMMAND
A080
FRAGO
FRAGMENTARY ORDER
F015
AIRALLOC
AIR ALLOCATION MESSAGE
F043
RESPONSE
AIR SUPPORT RESPONSE
F058
ATO
AIR TASKING ORDER
J017
IFFPROD
IFF PROCEDURES
J050
ORBATTOA LAN-AIR
ORDER OF BATTLE TRANSFER OF

AUTHORITY MESSAGE LAND AND AIR
J051
ROEIMPL
RULES OF ENGAGEMENT IMPLEMENTATION
J060
ROEAUTH
RULES OF ENGAGEMENT AUTHORISATION
J065
EWSTOPJAM
ELECTRONIC WARFARE STOP JAMMING

MESSAGE
J066
EWRTM
ELECTRONIC WARFARE
REQUESTING/TASKING MESSAGE
J070
WCO
WEAPON CONTROL ORDER
J076
ACTWARN
ACTIVATION WARNING MESSAGE
2 - B - 25
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
J077
ACTREQ
ACTIVATION REQUEST MESSAGE
J078
ACTORD
ACTIVATION ORDER MESSAGE
J079
LASERWARN
LASER TARGET MARKING WARNING

MESSAGE
N010
OPTASK.ASUW
OPERATIONAL TASKING OF ANTI-SURFACE

WARFARE
N017
OPTASKLINK
OPERATIONAL TASKING DATA LINK
N023
GREEN
MARITIME UNIT EXECUTION ORDER
N028
OPTASK AIR
OPERATIONAL TASKING ORGANIC

AIRCRAFT
N067
OPTASK COMMS
OPERATIONAL TASKING COMMUNICATIONS
N068
OPTASK EW
OPERATIONAL TASKING ELECTRONIC

WARFARE
Table B2 - 12: ADatP-3 Tasking Messages

3.2.2 Airspace Control.
Where appropriate for the required LOI, the CUCS shall be capable of processing the
following message formats in order to accomplish the Airspace Control function:
Index
Identifier
Format Name
A069
SPRT.ACA
SUPPORT AIRSPACE COORDINATION

ORDER
F011
ACO
AIRSPACE CONTROL ORDER
F012
ACMREQ
AIRSPACE CONTROL MEANS REQUEST
Table B2 - 13: ADatP-3 Airspace Control Messages

3.3 Air Traffic Control.
For UAVs that fly in controlled airspace and for LOI 4 and 5, ATS messages
summarised in section 2.3 shall be formatted as described in Appendix 3 of the ICAO
document, Rules of the Air and Air Traffic Services, Doc 4444-RAC/501
2 - B - 26
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
3.4 Collateral Data.
3.4.1 General Battlefield Picture.
accomplish the General Battlefield Picture:
Index
Identifier
Format Name
A026
ENSITREP
ENEMY LAND FORCES SITUATION REPORT
A031
OWNSITREP
OWN LAND FORCES SITUATION REPORT
A032
ORBATLAND
ORDER OF BATTLE LAND FORCES
A071
SYS.RFR
SYSTEM-REQUEST FOR REPORT
F001
AIRINTREP
AIR INTELLIGENCE REPORT
F032
ORBATAIR
ORDER OF BATTLE AIR FORCES
J009
FIRSTHOSTILEACT
FIRST HOSTILE ACT REPORT
J015
MARINTSUM
MARITIME INTELLIGENCE SUMMARY
J016
MARINTREP
MARITIME INTELLIGENCE REPORT
J019
AIRATTACKWARN
AIR ATTACK WARNING
J038
GEOSITREP
GEOGRAPHIC SITUATION REPORT
J071
TRACKREP
TARGET TRACK REPORT
J111
INTSUM
INTELLIGENCE SUMMARY
Table B2 - 14: ADatP-3 General Battlefield Picture Messages
2 - B - 27
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
3.4.2 Mission Dependent Data.
provide Mission Dependent Data:
Index
Identifier
Format Name
A058
ATI.ATR
ARTILLERY TARGET INTELLIGENCEARTILLERY TARGET REPORT
A059
ATI.TIR
ARTILLERY TARGET INTELLIGENCE-TARGET

INFORMATION REQUEST
A070
SPRT.GEOM
SUPPORT-BATTLEFIELD GEOMETRY
J005
COMSPOT
COMMUNICATIONS SPOT REPORT
J006
INCSPOTREP
INCIDENT SPOT REPORT
J018
MIJIWARNREP
MIJI WARNING REPORT
J072
COVREP
WEAPON COVERAGE REPORT
J073
SENSCOVREP
SENSOR COVERAGE REPORT
J110
INTREP
INTELLIGENCE REPORT
N003
JAMWARN
JAMMING WARNING
N025
LOCATOR
MARITIME FORCE LOCATOR
Table B2 - 15: ADatP-3 Mission Dependent Data Messages

provide CBRN Data:
Index
Identifier
Format Name
J028
CBRN BWR
CBRN BASIC WIND REPORT
J061
CBRN EDR
CBRN EFFECTIVE DOWNWIND REPORT
J156
CBRN 3 CHEM
CBRN 3 CHEMICAL REPORT
J157
CBRN 4 CHEM
J158
CBRN 5 CHEM
J159
CBRN 6 CHEM
J168
CBRN 3 BIO
CBRN 3 BIOLOGICAL REPORT
J169
CBRN 4 BIO
J170
CBRN 5 BIO
J171
CBRN 6 BIO
2 - B - 28
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
J174
CBRN 3 RAD
CBRN 3 RADIOLOGICAL REPORT
J175
CBRN 4 RAD
J176
CBRN 5 RAD
J177
CBRN 6 RAD
J178
CBRN SITREP
CBRN SITUATION REPORT
J182
CBRN 3 NUC
CBRN 3 NUCLEAR REPORT
J183
CBRN 4 NUC
J184
CBRN 5 NUC
J185
CBRN 6 NUC
Table B2 - 16: ADatP-3 CBRN Data Messages

3.4.4 Artillery Targeting.
support Artillery Target Intelligence reporting:
Index
Identifier
Format Name
A058
ATI.ATR
ARTILLERY TARGET INTELLIGENCE

ARTILLERY TARGET REPORT
A059
ATI.TIR
ARTILLERY TARGET INTELLIGENCE

TARGET INFORMATION REQUEST
Table B2 - 17: ADatP-3 Artillery Target Intelligence Messages

3.4.5 Meteorological Data.
coordinate Meteorological Data:
Index
Identifier
Format Name
A062
MET.TA
METEOROLOGICAL-TARGET ACQUISITION
A060
MET.CM
METEOROLOGICAL-COMPUTER
A061
MET.RFM
METEOROLOGICAL-REQUEST FOR MET
Table B2 - 18: ADatP-3 Meteorological Data Messages

3.4.6 Image Products.
The CUCS shall provide access to external Image Product Libraries via the CCI in
accordance with the interface specified in STANAG 4559.
2 - B - 29
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
The CUCS shall be capable of transmitting and receiving imagery products in
STANAG 4545 and STANAG 4609 format (e.g., to or from an Image Product
Library). If magnetic media is used for delivery it shall conform to STANAG 4575.
Inclusion of this capability is largely independent of LOI and therefore optional, but if
there is a requirement for a system to access image product libraries for collateral
information, then use of STANAG 4559 is mandatory.
3.5 Mission Plan.
A complete mission plan needs to include a route plan, contingency plan, collection
plan, dissemination plan, and communication plan.
There is currently no
international standard agreed upon that fully defines these elements of a mission
plan. However, there is a joint US and UK interface specification, called the Common
Route Definition (CRD) that is applicable to a route plan and a contingency plan. The
core data elements (called Tags) within the CRD interface specification may be
augmented by custom Tags, which reflect unique planning requirements that are not
addressed with the core Tags. Custom UAS Tags have been developed to create a
collection, dissemination, and/or a communication plan. These custom Tags are
contained and defined in Attachment B2-4, UAS Custom Tags.
To communicate with C4I systems or other UCSs, the UCS shall use the CRD
format (see DLI Mission Upload Command Message as defined in Appendix B1)
whenever possible to transmit or receive the mission plan. When not possible, a
CCISM shall be provided to translate between the CRD format and the differentlyformatted mission plan messages.
The capability to transmit and receive mission plans is recommended for LOI 3 and
shall be provided (mandatory) for LOI 4.
The ROS are likely to be included in the VSM (Appendix B1) for two reasons:
Scenarios are likely to be specific to particular types of air vehicles as they
depend on air vehicle capability, etc.
Not all existing air vehicles implement ROS.
Therefore a standard for ROS is not proposed in this document.
(NOTE: It is assumed that the emergency recovery plan is not exchanged with the
C4I systems.)
3.6 Handover Control.
This section deleted.

3.7 Mission Progress.
The CUCS shall be capable of processing the ADatP-3 message F031, Mission
Report (MISREP), to report mission progress. When appropriate, the MISREP shall
include a RMKS set to report data not included in the standard MISREP message
sets.
2 - B - 30
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
F031
MISREP
MISSION REPORT
Table B2 - 19: ADatP-3 Mission Report Message

3.8 Resource Availability.
3.8.1 Air Segment Status.
provide status and operational capability of the Air Segment:
Index
Identifier
Format Name
J002
ASSESSREP
COMMANDER'S ASSESSMENT REPORT
J003
GENINFOMSG
GENERAL INFORMATION MESSAGE
J029
AIRSTAT
OFFENSIVE WEAPON SYSTEM AND AIR

DEFENCE STATUS REPORT
J082
LOGASSESSREP
LOGISTIC ASSESSMENT REPORT
J083
LOGUPDATE
LOGISTIC UPDATE REPORT
J095
SITREP
SITUATION REPORT
J099
CISSITREP
CIS SITUATION REPORT
Table B2 - 20: ADatP-3 Air Segment Status and Operational Capability

Messages
3.8.2 Ground Segment Status.
provide status and operational capability of the elements of the Ground Segment.
Index
Identifier
Format Name
A010
LOGSITLAND
LOGISTIC SITUATION REPORT LAND

FORCES
J002
ASSESSREP
COMMANDER'S ASSESSMENT REPORT
J003
GENINFOMSG
J029
AIRSTAT

J082
LOGASSESSREP
LOGISTIC ASSESSMENT REPORT
J083
LOGUPDATE
LOGISTIC UPDATE REPORT
J095
SITREP
SITUATION REPORT
J099
CISSITREP
2 - B - 31
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Table B2 - 21: ADatP-3 Ground Segment Status and Operational Capability
Messages
3.9 Payload/Sensor Data.
3.9.1 Overview.
This section specifies the standards to be used for transmission of UAV ISR payload
data via the CCI.
Note: If a specific UAV system does not support a particular payload type (e.g.,
GMTI, ELINT, etc.), the supporting UCS can still be STANAG 4586 compliant without
having to implement those requirements associated with that particular payload.
3.9.2 Imagery Intelligence (IMINT).
The standards identified in Table B2-22 shall be used for the exchange of imagery
data across the CCI. When the UCS is receiving payload data and a C4I system
requires that data, the UCS shall provide the capability to disseminate payload data
to the C4I system.
Standard
STANAG 4545
STDI-0002
STANAG 7023
STANAG 4607
STANAG 4609
Imagery Type
Still EO/IR, MSI/ HSI, and SAR
Controlled extensions for STANAG 4545 metadata
Still EO/IR, MSI/HSI, and SAR
Ground moving target indicator
Motion EO/IR, MSI/HSI
Table B2 - 22: Imagery Standards
3.9.2.1 Still Imagery.

All digital still imagery will be transmitted over the CCI using either STANAG 4545 or
7023 as appropriate. For all still imagery types, STDI-0002 will be used to record
metadata describing the imagery when using STANAG 4545. However when
STANAG 7023 is used, metadata describing the imagery will be captured as
specified within STANAG 7023.
3.9.2.2 Digital Motion Imagery.
STANAG 4609 specifies a standard compression (MPEG-2) and means to capture
metadata describing digital motion imagery. Motion imagery, whether collected as
analogue or digital, shall be transmitted over the CCI using STANAG 4609 to those
C4I systems requiring digital motion imagery. Applicable KLV metadata shall be
implemented in accordance with MISB Standard 0601, MISB Standard 0902, and
MISB Standard 0102.
For those instances where an external CCI node requires analogue imagery, the
VSM or the CCISM shall provide the necessary conversion (if any required) of the
payload imagery to the format required by the respective CCI node, as discussed in
Section 2.9.2.1.2.1.
3.9.2.3 Multi/Hyperspectral.
Multispectral and hyperspectral images consist of multiple images from different parts
of the electromagnetic spectrum. Though not currently a UCS requirement, STANAG
2 - B - 32
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
7023 and 4545, respectively, are the controlling standards for these types of
payloads.
3.9.2.4 Synthetic Aperture Radar (SAR).
SAR images shall be transmitted across the CCI in accordance with STANAG 4545
or STANAG 7023 specified formats.
SAR auxiliary text files shall contain support data as defined in STANAG 4545 and
STDI-0002, National Imagery and Mapping Agency, The Compendium of Controlled
Extensions (CE) for the National Imagery Transmission Format (NITF), CMETAA
Support Data Extension.
3.9.2.5 Ground Moving Target Indicator (GMTI).
STANAG 4607 specifies a common standard format for GMTI data. GMTI data shall
be transmitted over the CCI in accordance with STANAG 4607.
3.9.3 ELINT.
ELINT data and related reports shall conform to the requirements of STANAG 4633,
ELINT Common Message Format (ECMF).
ESM data derived from analysis of enemy electronic signals shall conform to
STANAG 4633.
The CUCS shall be capable of processing the following message formats to report
data from a CBRN payload. Note that the CBRN SITREP is not included as it is
envisioned that it will be generated outside the UCS following multi-source analysis.
(The CBRN SITREP is included in Section 3.4.3.)
Index
Identifier
Format Name
J020
CBRN CDR
CBRN CHEMICAL DOWNWIND REPORT
J028
CBRN BWR
CBRN BASIC WIND REPORT
J061
CBRN EDR
J154
CBRN 1 CHEM
J155
CBRN 2 CHEM
J156
CBRN 3 CHEM
J157
CBRN 4 CHEM
J158
CBRN 5 CHEM
J159
CBRN 6 CHEM
J166
CBRN 1 BIO
J167
CBRN 2 BIO
J168
CBRN 3 BIO
2 - B - 33
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
J169
CBRN 4 BIO
J170
CBRN 5 BIO
J171
CBRN 6 BIO
J172
CBRN 1 RAD
J173
CBRN 2 RAD
J174
CBRN 3 RAD
J175
CBRN 4 RAD
J176
CBRN 5 RAD
J177
CBRN 6 RAD
J180
CBRN 1 NUC
J181
CBRN 2 NUC
J182
CBRN 3 NUC
J183
CBRN 4 NUC
J184
CBRN 5 NUC
J185
CBRN 6 NUC
Table B2 - 23: ADatP-3 CBRN Data Messages

3.9.5 Other Payload Types.
3.9.5.1 Laser Designator/Range Finder.
Future Capability.
3.10 Target Data.
Formats for near real time target data may be included in a future issue of the CCI
appendix.
3.11 Mission Reporting.
Where appropriate, the CUCS shall be capable of processing the following message
formats to report the results from a mission:
Index
Identifier
Format Name
A046
OBSREP
OBSTACLE REPORT
A088
RBTRECCEREP
ROAD, BRIDGE OR TUNNEL

RECONNAISSANCE REPORT
A092
GAPRECCEREP
GAP RECONNAISSANCE REPORT
A100
OBSRECCEREP
OBSTACLE RECONNAISSANCE REPORT
2 - B - 34
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
F031
MISREP
MISSION REPORT
F095
INFLIGHTREP
INFLIGHT REPORT
J064
EWMSNSUM
ELECTRONIC WARFARE MISSION SUMMARY
J101
COMPASSESSREP
COMPLIANCE ASSESSMENT REPORT
J103
RECEXREP
RECONNAISSANCE EXPLOITATION REPORT
N024
PURPLE
MARITIME MISSION SUMMARY REPORT
Table B2 - 24: ADatP-3 Mission Results Messages

3.12 General Messages.
There are a number of messages that do not appropriately belong in any of the
message categories discussed in the previous sections, but that are applicable to
UCS functionality and may be necessary to support a given LOI. Attachment B2-2
defines whether they are mandated or optional for a given LOI. Where appropriate
the CUCS shall be capable of processing the following message formats:
Index
Identifier
Format Name
A009
PRESENCE
PRESENCE REPORT
A027
LOGASREQ
LOGISTIC ASSISTANCE REQUEST
A028
LOGASRESP
LOGISTIC ASSISTANCE RESPONSE
A057
MAPREQ
MAP REQUEST
A072
SYS.RRM
SYSTEM REPLY MESSAGE
F087
MOVEREQ
MOVEMENT REQUEST
F088
MWO
MOVEMENT WARNING ORDER
F089
MEO
MOVEMENT EXECUTION ORDER
F090
MCR
MOVEMENT COMPLETION REPORT
J001
MSGCORRCANX
MESSAGE CORRECTION OR CANCELLATION
J003
GENINFOMSG
J012
SARIR
SEARCH AND RESCUE INCIDENT REPORT
J013
SARREQ
SEARCH AND RESCUE REQUEST
J021
INTREQ
INTELLIGENCE REQUEST
J052
ROEREQ
RULES OF ENGAGEMENT REQUEST
J092
EVENTREP
EVENTS REPORT
J112
CIINTREP
COUNTER-INTELLIGENCE AND SECURITY

REPORT
2 - B - 35
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Index
Identifier
Format Name
J113
CIINTSUM

SUMMARY
J114
SUPINTREP
SUPPLEMENTARY INTELLIGENCE REPORT
J115
CISUPINTREP

SUPPLEMENTARY REPORT
N033
SATVULREP
SATELLITE VULNERABILITY REPORT
Table B2 - 25: ADatP-3 General Messages
2 - B - 36
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
Attachment B2 - 1: Information Exchange Requirements
This section contains the Information Exchange Requirements imposed on the UCS
and hence on the CCI which, excluding the DLI, represents the external interface to
the UCS.
NOTES:
Note 1
refers to
the
Product/
Action
Column of
the IER
Tx indicates that this function/product is transmitted from the UCS. Rx indicates that this
function/product is received by the UCS.
Note 2
refers to
the
Rationale
(UJTL#)
Column of
the IER
The following provides the descriptions of the various Universal Joint Task List
(UJTL) numbers identified in this document.
ST 2.2.1
Collect Information on Theatre Strategic Situation
ST 2.4.2.2
Provide Theatre Current Intelligence
ST 2.4.2.4
Provide Target Intelligence for Theatre Planning and Execution
ST 5.1.4
Monitor Worldwide and Theatre Strategic Situation
OP 1.2.5
Conduct Offensive Operations in the Joint Operations Area
OP 1.3.2
Enhance Movement of Operational Forces
OP 2.1.3
Prepare Operational Collection Plan
OP 2.2
Collect and Share Operational Information
OP 2.2.1
Collect Information on Operational Situation
OP 2.2.3
Collect and Assess METOC Information
OP 2.2.5
Collect Target Information
OP 2.4
Produce Operational Intelligence and Prepare Intelligence Products

2 - B - 37
APPENDIX 2 to
Annex B to
STANAG 4586
Edition 3
NOTES:
OP 2.4.2.1
Provide Indications and Warnings for the Joint Operations Area
OP 2.4.2.2
Provide Current Intelligence for the Joint Operations Area
OP 2.4.2.4
Provide Target Intelligence for the Joint Operations Area
OP 2.5
Disseminate and Integrate Operational Intelligence
OP 2.5.3
Provide Near Real Time Intelligence for the Joint Operations Area Planners
and Decision Makers
OP 3.1.3
Develop Operational Targets
OP 3.1.6.1
Assess Battle Damage on Operational Targets
OP 5.1.4
Maintain Operational Information and Force Status
OP 5.1.5
Monitor Strategic Situation
OP 5.2
Assess Operational Situation
OP 5.2.1
Review Current Situation
TA 1.2.2
Conduct Joint Airborne Operations
TA 2.2
Obtain and Access Intelligence Information
TA 3.1
Process Targets
TA 5.1
Acquire and Communicate Information and Maintain Status and Force

Reporting
TA 5.2.1
Establish, Operate, and Maintain Baseline Communications
Note 3
refers to
the LOI
Column of
the IER
This indicates the operating LOI of the UCS.
2 - B - 38
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
UNMANNED AERIAL VEHICLE CONTROL SYSTEM (UCS) COMMAND AND CONTROL INTERFACE (CCI)
-INFORMATION EXCHANGE REQUIREMENTS (IER) MATRIXProduct/
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
At min.
mandatory
fields: (e.g.,
ATO Msg.)
UAV Mission
Tasking;
Route, Pyld.
Comm. Plan
JFACC or
any
properly
equipped
C2 Node
UAV Det or
System
Yes
Variable;
Minutes to
Hours
Restricted
flight zones:
4-Dimension
JFACC;
Any
capable
ATM node
UCS
Yes; may
not always
be required
Variable;
Minutes to
Hours
TASKING
Identified in Section 3.2.
Tasking
(Tx/Rx)
ST 2.2.1, ST
2.4.2.2, ST
2.4.2.4, ST
5.1.4
Airspace
Control
(Tx/Rx)
ST 5.1.4,
OP 2.2.5
2, 3, 4, 5
APP-11
Tactical
Msg(s)
4, 5
APP-11:
ACO
Tactical
Msg(s)
Note: Tasking and Airspace Control Messages may also be received via e-mail and/or voice tasking as shown below.
E-Mail
Messages
(Rx)
OP 2.2.1
OP 2.2.5
2, 3, 4, 5
SMTP
Text
Message
Min. Mission
Plan, e.g.
route/target
area
Any
authorized
C2 Node
UAV Det or
System
Yes
Variable;
Minutes to
Hours
Voice
Tasking (Rx)
OP 2.2.5,
OP 2.4.2.2,
OP 2.5.3
2, 3, 4, 5
APP-11
Voice
Mission
Tasking
Any
authorized
C2 Node
UAV Det or
System
Yes
Variable;
Minutes to
Hours
2 B - 39
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
For
operations in
civil
airspace.
Corridors,
Routes, Plan
Changes,
etc.
JFACC;
Any
capable
ATM node,
UCS
JFACC; Any
capable ATM
node, UCS
Yes; may
not always
be required
Variable;
Minutes to
Hours
JFACC;
Any
capable
ATM node,
UCS
JFACC; Any
capable ATM
node, UCS
No unless
Tactical
Msgs not
available
Variable;
Minutes to
Hours
AIR TRAFFIC CONTROL

ATS
Messages
(Tx/Rx)
ST 5.1.4,
OP 2.2.5
4, 5
DOC 4444RAC/501
Tactical
Msg(s)
Note: Air Traffic Control Messages may also be transmitted/received via e-mail as shown below.
E-Mail
Messages
(Tx./Rx)
ST 5.1.4,
OP 2.2.5
4, 5
SMTP
Text
Message
Corridors,
Routes, etc.
2 B - 40
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Includes,
but not
limited to
Enemy and
Friendly
Order of
Battle and
SitReps
Blue/Red
Force
Location,
charact/OB
Map Overlay
Data. Tgt
Types
Any C2
node
having
data
(including
target
data)
Receiving
Node
Critical
Timeliness
UCS
Yes, also
depends on
mission
Variable;
Minutes to Hours
COLLATERAL DATA
General
Battlefield
Picture
(Tx/Rx)
OP 2.2.1,
OP 3.1.3,
OP 5.1.4,
OP 5.1.5,
TA 3.1,
TA 5.1
Mission
Dependent
Data
(Tx/Rx)
CBRN Data
(Tx/Rx)
2, 3, 4, 5
(May be
LOI 1 for
some
msgs. See
AdatP-3
Impl Table)
APP-11
Tactical
Msg, Text
Msg, Data
ST 2.4.2.4,
ST 5.1.4,
OP 2.2.5,
TA 2.2
2, 3, 4, 5
APP-11
Tactical
Msg
Artillery
Reports &
Requests,
Intel Reports
Any C2
node
having
data
UCS
Yes
Variable;
Minutes to Hours
ST 2.2.1,
OP 2.2
2, 3, 4, 5
APP-11
Tactical
Msg, Text
Msg
CBRN Data
for specified
location
UCS; any
C2 node
having
UCS; any C2
node having
CBRN data
Depends
on mission
Variable;
Minutes to Hours
CBRN
data
2 B - 41
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
Artillery
Targeting
(Tx/Rx)
ST 2.4.2.4,
OP 2.2.5,
OP 2.4.2.4
2, 3, 4, 5
APP-11
Tactical
Msg
Artillery Tgt
Rpts and
Requests
Any C2
node
having tgt
data
UCS
Yes
Variable;
Minutes to Hours
Meteorological Data
(Tx/Rx)
OP 2.2.3
2, 3, 4, 5
APP-11
Tactical
Msg, Text
Msg
Met. Data
for specified
location
UCS; Any
C2 node
having Met
data
UCS; Any C2
node having
Met data
Depends
on mission
Variable;
Minutes to Hours
Image
Products
(Tx/Rx)
OP 2.5
STANAG
4559
Digital
Imagery
Digital
Any C2
Node
having an IL
UCS
Depends
on mission;
yes for
most RSTA
Variable;
Minutes to Hours
1, 2, 3, 4, 5
2 B - 42
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI
(3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
MISSION PLAN
Flight Route (Tx/Rx)
OP 2.4.2.2,
OP 2.5.3
3, 4,
5
CRD
(STANAG is
TBD)
Tactical
Msg, Text
Msg
Internatl
Filing
Format
Waypoints,
recovery plan,
etc. Loaded to
AV
UCS,
JFACC, or
any
capable
C2 node
UCS,
JFACC, or
any capable
C2 node
Yes; may
not
always
be
required
Variable;
Minutes to
Hours
Collection Data Plan

(Tx/Rx)
OP 2.1.3
3, 4,
5
CRD Ext.
(STANAG is
TBD)
Tactical
Msg, Text
Msg
To/from
AMPS
Payload plan
data; formatted
message or email
UCS,
JFACC, or
any
capable
C2 node
UCS,
JFACC, or
any capable
C2 node
Yes; may
not
always
be
required
Variable;
Minutes to
Hours
Comm Plan (Tx/Rx)
OP 2.5.3
3, 4,
5
CRD Ext.
(STANAG is
TBD)
Tactical
Msg, Text
Msg
Data Link plan

data
UCS
UCS,
JFACC, or
any capable
C2 node
Yes; may
not
always
be
required
Variable;
Minutes to
Hours
2 B - 43
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI
Emergency Recovery
Plan (Contingency
Plan)
(Tx/Rx)
OP 2.4.2.2,
OP 2.5.3
3, 4,
5
CRD Ext.
(STANAG is
TBD)
Tactical
Msg(s),
Text
Msgs
Emergency
Recovery Plan
Dissemination Plan
ST 2.4.2.2,
OP 2.5
3, 4,
5
CRD Ext.
(STANAG is
TBD)
Tactical
Msgs
Data
Dissemination
(3)
NATO or
Internatl
Standard
Format
Remarks
2 B - 44
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
UCS
UCS,
JFACC, or
any capable
C2 node
Yes; may
not
always
be
required
Variable;
Minutes to
Hours
UCS
UCS, C2
Nodes
Yes
Variable
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
MISSION PROGRESS
Identified in sections 2.7 and 3.7.
Tactical
Messages
(Tx/Rx)
OP 2.4.2.1,
OP 5.1.4,
OP 5.2.1
2, 3, 4, 5
APP-11
Tactical
Msg
AV Position,
Sys. Status,
Pyld Status, etc.
UCS
UCS; any
capable C2
node
Yes
Near real time
RESOURCE AVAILABILITY
Identified in Section 2.8 and 3.8. (Includes entire system status and availability.)
Air
Segment
Status
(Tx/Rx)
OP 5.2.1,
TA 5.1
1, 2, 3, 4, 5
APP-11
Tactical
Msg, Text
Msg
UAV,
Payload, &
Data Link
Status
Includes
Payload
availability
UAV, Data
Links
UCS; any
capable C2
node
Yes
Variable;
Minutes to
Hours
Ground
Segment
Status
(Tx/Rx)
OP 5.2.1,
TA 5.1
1, 2, 3, 4, 5
APP-11
Tactical
Msg, Text
Msg
UCS, Data
Link,
Launch &
Recovery
Systems
Includes
Maintainance
and
Refurbishment
Systems (Not
Critical)
Data Link,
UCS, L&R
Sys, Maint
& Refurb
Sys
UCS; any
capable C2
node
Yes
Variable;
Minutes to
Hours
2 B - 45
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
LOI (3)
Rationale
(UJTL#) (2)
NATO or
Internatl
Standard
Format
Remarks
STANAG
4609;
MPEG2
ISO/IEC
13818-1 to
3
Encoded or
Decoded
imagery
stream
EO/IR
Framing
Line Scan
Sensor
(KLV as per
MISB STDs
0601, 0902
and 0102)
STANAG
7023
STANAG
4545
STDI-0002
Still
Imagery
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
PAYLOAD/SENSOR DATA (Primary and Secondary)

Identified in Section 2.9
Imagery Intelligence (Tx/Rx)
EO/IR
Motion
Imagery
(with KLV
metadata)
OP 2.2.5,
OP 2.4
EO/IR Still
Imagery
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
1, 2, 3, 4,
5
NITF 2.1
Continuous video and

telemetry as the AV
transmits
UCS
UCS; any
capable
C4 node
Yes
Variable;
Seconds to
Hours
UCS
UCS; any
capable
C4 node
Yes
Variable;
Seconds to
Hours
(Continuous metadata
as the video is
transmitted)
UCS
processed/annotated
imagery
2 B - 46
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
-INFORMATION EXCHANGE REQUIREMENTS (IER) MATRIXRationale
(UJTL#) (2)
LOI (3)
MSI, HSI
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
STANAG
4545
STANAG
7023
SAR
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
STANAG
7023
STANAG
4545
STDI-0002
Encoded
Imagery
Stream
Or
Still
Imagery
GMTI
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
STANAG
4607
MTI Tracks
& Vectors
Product/
Action (1)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
Future
Implement
SAR Data
formed into
an image
Continuous video and

telemetry as the AV
transmits
Or
UCS
processed/annotated
imagery
UCS
UCS; any
capable
C4 node
No (If
other
imagery
available)
Variable;
Seconds to
Hours
Continuous data as the

AV transmits
UCS
UCS; any
capable
C4 node
No (If
other
imagery
available)
Variable;
Seconds to
Hours

AV transmits
UCS
UCS; any
capable
C4 node
Yes
Variable;
Seconds to
Hours
Signals Intelligence (Tx/Rx)

ELINT and
ESM
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
STANAG
4633
COMINT
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
TBD
Future
Implement
2 B - 47
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
Chemical, Biological, Radiological, and Nuclear (Tx/Rx)

CBRN Data
OP 2.2.5,
OP 2.4
1, 2, 3, 4,
5
APP-11

AV transmits
UCS
UCS; any
capable
C4 node
No (If
other data
available)
Variable;
Seconds to
Hours
Range-to-Target Info
UCS
UCS; any
capable
C4 node
Yes (if
used for
targeting,
firing
weapons)
Seconds
UCS
UCS; any
capable
C4 node
Yes
(depends
on tactical
situation
Variable;
Seconds to
Hours
UCS
UCS; any
capable
C4 node
Yes
Variable;
Seconds to
Hours
Other Payload Types (Tx/Rx)

Laser
Designator,
Range
Finder
OP 1.2.5
OP
2,4,2,4
TA 3.1
3, 4, 5
Comms
Relay
ST 2.1.1
ST 5.1.4
OP 5.1.5
TA 5.2.1
3, 4, 5
Weapons,
Stores
OP 1.2.5
TA 12.2
3, 4, 5
Could be
tactical
msg to
define
range
Tactical
messages
See
Weapons
Appendix
See Weapons
Appendix
TARGET DATA - Deferred until future update and implementation of STANAG 4586.
Refer to Sections 2.10.
2 B - 48
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
MISSION REPORTING
Mission
Reporting
(Tx/Rx)
(Incl. Tgt
coord,
battlefield
geo, recon
rpt, BDA
rpts)
OP 2.2.1,
2.2.5, 2.4,
2.5, 3.1.6.1,
5.1.5, 5.2,
TA 3.1, 5.1
1, 2, 3, 4,
5
(See
ADatP-3
Impl
Table)
APP-11:
SMTP,
STANAGs
4545 and
4609
Tactical
Msg, Text
Msg, Video
Imagery
1, 2, 3, 4,
5
APP-11
Tactical
Messages
BDA rpts
can be via
imagery
Tasked Mission Status,
UCS
UCS; any
capable
C2 node
Yes
Variable;
Seconds to
Hours
UCS
UCS; any
capable
C2 node
YES
Variable;
Seconds to
Hours
(pending, in progress,
etc.), Target Collection
Rpts, Order of Battle,
Summary Reports, BDA
Reports
GENERAL MESSAGES
General
Tactical
Message
Could
Cover Many
UJTLs
Miscellaneous
Messages
MISCELLANEOUS
(Note: These represent several miscellaneous capabilities required for a UCS.)
2 B - 49
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Action (1)
Rationale
(UJTL#) (2)
LOI (3)
NATO or
Internatl
Standard
Format
Remarks
Includes
protocols
(e.g., TCP,
UDP, IP,
SMTP, FTP,
NFS, MIME,
etc.) (Annex
B)
LAN
Connection
TA 5.2.1
1, 2, 3, 4,
5
ISO/IEC
8802-3,
ANSI/IEEE
Std 802.3
(DOD JTA,
protocols)
Imagery,
Text,
Voice,
Video, Data
IPL (IL)
Interface
(Tx/Rx)
OP 2.2
1, 2, 3, 4,
5
STANAG
4559
Imagery
Digital Voice
(Tx/Rx)
TA 5.2.1
1, 2, 3, 4,
5
H.323
Voice
Info/Char
Sending
Node
Receiving
Node
Critical
Timeliness
N/A
N/A
N/A
Yes
N/A
Imagery files to and

from the Image Library
UCS, IL
IL, UCS
Yes
Variable;
Seconds to
Hours
UCS;
any
capable
C4 node
UCS; any
capable
C4 node
No
Real Time
Voice over
IP
2 B - 50
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Attachment B2 - 2: APP- 11 Message Implementation Requirements
The table provided in this attachment contains the list of APP-11 message formats that are applicable to the UCS. Each message is identified, its
function or purpose summarised, and its applicable LOI stated.
Index Ref. No This column contains the Message Text Format Index Reference Number as listed in APP-11. This column also indicates the
transmission (Tx) or receipt (Rx) requirements of the UCS.
MTF Identifier This column contains the Message Text Format Identifier as listed in APP-11.
MTF Name This column contains the Message Text Format Name as listed in APP-11.
Function or purpose This column contains the Function or Purpose as listed in APP-11.
LOI This column contains the applicable LOI associated with each message. This number refers to the lowest level at which the message is
mandatory. Below this number, implementation is optional (refer to the remarks in Section 1.6, Implementation of UAV LOI in the CCI).
Comments This column contains general comments and cross-references to paragraphs in Annex B and Appendix B2, where applicable.
2 B - 51
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
A009
(Tx)
PRESENCE
Presence Report
The PRESENCE report is used to inform a

commander on the deployment of military
organisations within his area of responsibility.
The report addresses both organisations under
his command and those that are not.
Optional
Para 3.12
General Msg
A010
(Tx)
LOGSITLAND
Logistic Situation
Report Land
Forces
The LOGSITLAND is used to provide a superior

headquarters with an evaluation of a units or
formation's logistical situation, capability, and
deficiencies/surpluses.
Optional
Para 3.8.2
Resource
Availability, Gnd
Seg Status
A026
(Tx/Rx)
ENSITREP
Enemy Land
Forces Situation
Report
The ENSITREP is used to report and inform on

the enemy forces situation, to include: locations,
activities, boundaries, status, order of battle
(ORBAT) and subordination of units/formations.
2, 3, 4, 5
Para 3.4.1
Collateral data,
Gen Battlefield
Pic
A027
(Tx)
LOGASREQ
Logistics
Assistance
Request
The LOGASREQ is used by land forces to

request logistics assistance.
Optional
Para 3.12
General Msg
A028
(Rx)
LOGASRESP
Logistics
Assistance
Response
The LOGASRESP is used by land forces to

respond to a request for logistics assistance.
Optional
Para 3.12
General Msg
A031
(Tx/Rx)
OWNSITREP
Own Land Forces

Situation Report
The OWNSITREP is used to report factors

affecting the situation, deployment, status and/or
order of battle of own and subordinate units.
2, 3, 4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
2 - B - 52
LOI
Comments
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
A032
(Rx)
ORBATLAND
Order of Battle Land Forces
The ORBATLAND is used to inform major

NATO commanders (MNCs)/strategic
commanders (SCs) and other NATO
commanders in peacetime and in periods of
crisis and war of changes in the order of battle
land forces and thereby to assure that the most
current information is available for operational
planning.
A033
(Tx)
FM.CFF
Fire Mission-Call
For Fire
The FM.CFF is used to transmit initial fire for

effect requests and/or orders to fire.
Para 3.2.1
Tasking
A034
(Tx)
FM.SUB
Fire MissionSubsequent
Adjustment
The FM.SUB is used to transmit updated grid

locations, to repeat fire for effect and/or to
terminate missions.
Para 3.2.1
Tasking
A035
(Tx/Rx)
FM.MTO
Fire MissionMessage to
Observer
The FM.MTO is used to transmit a message to

observer in response to a call for fire on a target
of opportunity.
Para 3.2.1
Tasking
A036
(Tx)
FM.FMC
Fire Mission-Fire
Mission
Command
The FM.FMC is used to transmit a fire mission

command to a fire unit or an observer.
Para 3.2.1
Tasking
A046
(Tx/Rx)
OBSREP
Obstacle Report
The OBSREP is used to report obstacles up the

chain of command
2, 3, 4, 5
Para 3.11
Mission
Reporting
A057
(Tx/Rx)
MAPREQ
Map Request
The MAPREQ is used to submit requests for

map coverage.
Optional
Para 3.12
General Msg
2 - B - 53
LOI
4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
A058
(Tx/Rx)
ATI.ATR
Artillery Target
IntelligenceArtillery Target
Report
The ATI.ATR is used to transmit targets by

target type based on a standing request for
information or a one-time query for target
information resulting from an ATI.ATR message.
It will also be used to establish or delete target
information.
2, 3, 4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent and
Para 3.4.4
Collateral Data,
Artillery
Targeting
A059
(Rx)
ATI.TIR
Artillery Target
IntelligenceTarget
Information
Request
The ATI.TIR is used to request target

information either as a one-time query or as a
standing request for target information.
2, 3, 4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent and
Para 3.4.4
Collateral Data,
Artillery
Targeting
A060
(Rx)
MET.CM
MeteorologicalComputer
The MET.CM is used to transmit computer

meteorological data.
2, 3, 4, 5
Para 3.4.5
Collateral Data,
MET
A061
(Tx/Rx)
MET.RFM
MeteorologicalRequest For Met
The MET.RFM is used to request meteorological

support.
2, 3, 4, 5
Para 3.4.5
Collateral Data,
MET
A062
(Tx/Rx)
MET.TA
MeteorologicalThe MET.TA is used to transmit meteorological

Target Acquisition data for target acquisition purposes.
2, 3, 4, 5
Para 3.4.5
Collateral Data,
MET
2 - B - 54
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
A069
(Tx/Rx)
SPRT.ACA
Support-Airspace
Coordination
Area
The SPRT.ACA is used to establish or delete

airspace coordination areas (ACA).
A070
(Tx/Rx)
SPRT.GEOM
SupportBattlefield
Geometry
The SPRT.GEOM is used to establish or delete

battlefield geometries (e.g., avenue of approach,
axis of advance, target areas, zone of fire) in
support of land combat operations for current
operations or for a fire plan.
2, 3, 4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent
A071
(Tx/Rx)
SYS.RFR
System-Request
For Report
The SYS.RFR is used to establish or delete a

request for ammunition status reports, fire unit
status reports, firing sites, battlefield geometry,
friendly unit locations, fire plan target lists, and
other applicable reports.
2, 3, 4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
A072
(Tx/Rx)
SYS.RRM
System Reply
Message
The SYS.RRM is used to transmit a reply to a

received message.
1, 2, 3, 4,
Para 3.12
General
Messages
A080
(Rx)
FRAGO
Fragmentary
Order
The FRAGO is used to issue key sections of an

operation order before the complete order has
been produced; provide specific instructions to
commanders who do not require the complete
operation order; provide a summary of the
complete order to serve as confirmatory notes;
issue timely changes to existing operation
orders or provide an outline operational directive
(mission order) for use in fast moving mobile
operations.
1, 2, 3, 4,
2 - B - 55
LOI
4, 5
Para 3.2.2
Airspace
Control
Para 3.2.1
Tasking
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
A088
(Tx/Rx)
RBTRECCEREP
Road, Bridge or
Tunnel
Reconnaissance
Report
The RBTRECCEREP is used to report the

results of a technical reconnaissance of a road,
bridge or tunnel along a section of a route.
2, 3, 4, 5
Para 3.11
Mission
Reporting
A092
(Tx/Rx)
GAPRECCEREP
Gap
Reconnaissance
Report
The GAPRECCEREP is used to report the

results of a gap crossing site reconnaissance.
2, 3, 4, 5
Para 3.11
Mission
Reporting
A100
(Tx/Rx)
OBSRECCEREP
Obstacle
Reconnaissance
Report
The OBSRECCEREP is used to report the

results of a reconnaissance of enemy or friendly
obstacles, existing or planned.
2, 3, 4, 5
Para 3.11
Mission
Reporting
F001
(Rx)
AIRINTREP
Air Intelligence
Report
The AIRINTREP is used to inform SACEUR and

ACO commanders of changes in the location,
disposition, status and other essential elements
of information concerning non-NATO air order of
battle.
4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
F011
(Rx)
ACO
Airspace Control
Order
The ACO is used to provide specific detailed

orders for airspace management and control
from a higher command to subordinate units
4, 5
Para 3.2.2
Airspace
Control
F012
(Tx/Rx)
ACMREQ
Airspace Control
Means Request
The ACMREQ is used to request that a specific

airspace control means be specified in a future
airspace control order.
4, 5
Para 3.2.2
Airspace
Control
F015
(Rx)
AIRALLOC
Air Allocation
Message
The AIRALLOC is used to inform subordinate

units, formations and/or tasking agencies of the
air effort allocated.
2, 3, 4, 5
Para 3.2.1
Tasking
2 - B - 56
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
F031
(Tx/Rx)
MISREP
Mission Report
The MISREP is used to report mission results

and items of intelligence interest in all tactical
roles and to retransmit and/or amplify in-flight
reports.
F032
(Rx)
ORBATAIR
Order of Battle Air Forces
F043
(Tx)
RESPONSE
F058
(Rx)
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
3, 4, 5
Para 3.7 & 3.11

Mission
Progress &
Mission
Reporting
The ORBATAIR is used to inform major NATO

commanders (MNCs)/strategic commanders
(SCs) and other NATO commanders in
peacetime and in periods of crisis and war of
changes in the order of battle air forces and
thereby to assure that the most current
information is available for operational planning.
4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Air Support
Response
The RESPONSE MTF is used to accept or

refuse one or more air support requests.
4, 5
Para 3.2.1
Tasking
ATO
Air Tasking Order
The ATO is used to task offensive, defensive

and support missions including surveillance and
control assets in order to conduct both joint and
single service air operations.
2, 3, 4, 5
Para 3.2.1
Tasking
F087
(Tx/Rx)
MOVEREQ
Movement
Request
The MOVREQ is used by a unit or higher level

to request execution of a deployment of landbased unit(s).
Optional
Para 3.12
General Msg
F088
(Rx)
MWO
Movement
Warning Order
The MWO is used by tasking agencies to warn

of intended or expected deployments of landbased unit(s).
Optional
Para 3.12
General Msg
F089
(Rx)
MEO
Movement
Execution Order
The MEO is used by tasking authorities to order

the deployment of land-based unit(s).
Optional
Para 3.12
General Msg
2 - B - 57
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
F090
(Tx/Rx)
MCR
Movement
Completion
Report
The MCR is used by land-based units to report

the completion of deployment.
Optional
Para 3.12
General Msg
F095
(Tx/Rx)
INFLIGHTREP
Inflight Report
The INFLIGHTREP is used to provide a record

of a voice inflight report, giving a mission
assessment and specifying pilot/aircrew
sightings or other vital information that may be
of tactical or intelligence value.
1,2, 3, 4,
5
Para 3.7 & 3.11

Mission
Progress &
Mission
Reporting
J001
(Tx/Rx)
MSRCORRCANX
Message
Correction or
Cancellation
He MSGCORRCANX is used to cancel a

message(s) and/or to correct the information in
a previously transmitted message(s).
1, 2, 3, 4,
Para 3.12
General Msg
J002
(Tx/Rx)
ASSESSREP
Commander's
Assessment
Report
The ASSESSREP is used to advise superior

commanders of the situation/operations in the
reporting commander's area of concern, his
assessment of the overall situation, and his
intended or recommended actions based on that
assessment.
Optional
Para 3.8.1 &

3.8.2
Resource
Availability, Air
Segment Stat &
Gnd Segment
Stat
J003
(Tx/Rx)
GENINFOMSG
General
Information
Message
The GENINFOMSG may only be used to

provide information which cannot be provided
using existing MTFs. This is a special message
used for unusual circumstances that cannot be
anticipated or planned and should not be used
on a routine basis nor is it intended to replace
existing messages.
Optional
Para 3.12
General Msg
2 - B - 58
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J005
(Tx/Rx)
COMSPOT
Communications
Spot Report
The COMSPOT is used to report actual or

forecast communications outages including
relocation and EMCON.
2, 3, 4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent
J006
(Tx/Rx)
INCSPOTREP
Incident Spot
Report
The INCSPOTREP is used to provide time

critical information on important events that have
an immediate impact on operations.
2, 3, 4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent
J009
(Rx)
FIRST HOSTILE ACT
First Hostile Act

Report
The FIRST HOSTILE ACT is used to rapidly

provide major NATO commands with
information on initial enemy/opposition forces
(OPFOR) hostile acts in order to enable major
NATO commands to react as early as possible.
1, 2, 3, 4,
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
J012
(Tx)
SARIR
Search and
Rescue Incident
Report
The SARIR is used to report any situation which

may require a search and rescue effort.
Optional
Para 3.12
General Msg
J013
(Rx)
SARREQ
Search and
Rescue Request
The SARREQ is used to request forces to

participate in a search and rescue mission.
4, 5
Para 3.12
General Msg
J015
(Rx)
MARINTSUM
Maritime
Intelligence
Summary
The MARINTSUM is used to provide periodic

summary information pertaining to the
movement of non-NATO forces in NATO
maritime areas.
J016
(Rx)
MARINTREP
Maritime
Intelligence
Report
The MARINTREP is used to provide time

sensitive advisory information pertaining to the
movement of non-NATO forces in NATO
maritime areas.
2 - B - 59
LOI
1, 2, 3, 4,
5
4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J017
(Rx)
IFFPROD
IFF Procedures
The IFFPROD is used to provide friendly forces

with effective IFF modes and codes, and
effective time periods.
4, 5
J018
(Tx/Rx)
MIJIWARNREP
MIJI Warning
Report
The MIJIWARNREP is used in times of peace

and crisis to warn NATO nations, commands
and units of hazardous electronic warfare
situations caused by MIJI incidents, which are of
hostile, friendly (inadvertent) or unknown origin.
1, 2, 3, 4,
J019
(Rx)
AIRATTACKWARN
Air Attack
Warning
The AIRATTACKWARN is used to warn of

imminent enemy air attacks against friendly
forces. It may be used in conjunction with either
global early warning (GEW) or local early
warning (LEW) messages generated by
automated air defence (AD) systems.
1, 2, 3, 4,
J020
(Rx)
CBRN CDR
CBRN Chemical
Downwind Report
The CBRN CDR is used to disseminate a

forecast of the meteorological data needed for
the chemical or biological hazard area prediction
procedure by appropriate agencies every six
hours for 3 consecutive 2 hour periods or for a
time period of at least 6 hours specified in the
message.
1, 2, 3, 4,
J021
(Tx/Rx)
INTREQ
Intelligence
Request
The INTREQ is used to standardise the method

by which military authorities and forces of NATO
nations and NATO commands request
intelligence information.
2, 3, 4, 5
2 - B - 60
LOI
Para 3.2.1
Tasking
Para 3.4.2
Collateral Data,
Mission
Dependent
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Para 3.9.5 &

3.11
Payload Data,
CBRN &
Mission
Reporting
Para 3.12
General Msg
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J028
(Tx/Rx)
CBRN BWR
CBRN Basic
Wind Report
The CBRN BWR is used to report wind direction

and speed in 2,000m increments from the
surface of the earth to 30,000m altitude for
either the nearest 6 hours or for a period at least
6 hours specified in the message.
Optional
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J029
(Tx)
AIRSTAT
Offensive
Weapon System
and Air Defence
Status Report
The AIRSTAT is used to keep SHAPE informed

on availability of offensive air forces committed
to SHAPE, maritime helicopter and patrol
aircraft committed to SHAPE, and defensive
weapon systems committed to the integrated air
defence of ACE.
4, 5
Para 3.8.1 &

3.8.2
Resource
Availability, Air
Segment Stat &
Gnd Segment
Stat
J038
(Rx)
GEOSITREP
Geographic
Situation Report
The GEOSITREP is used to keep major

subordinate commands informed during periods
of tension and war on the geographical situation
within ace. The first report is required to inform
headquarters of serious shortages and most
urgent requirements within the geographic
services when military vigilance is declared. It
also gives an overall picture of the map/chart
reproduction potential immediately available.
Continuation reports are required to keep the
information up-to-date for evaluation, planning,
and coordination by the headquarters.
Optional
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
2 - B - 61
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J050
(Rx)
ORBATTOA LAN-AIR
Order of Battle
Transfer of
Authority
Message - Land
and Air
The ORBATTOA LAND-AIR is used to report or

direct the transfer of operational command
(OPCOM) and/or control (OPCON) between
nations and NATO or within the NATO chain of
command. An ORBATTOA land-air message
will normally confirm the delegation of authority
requested in ACTWARN and ACTREQ
messages.
J051
(Rx)
ROEIMPL
Rules of
Engagement
Implementation
The ROEIMPL is used to implement and/or

cancel specific rules of engagement.
J052
(Tx/Rx)
ROEREQ
Rules of
Engagement
Request
The ROEREQ is used to request authorisation

to implement specific rules of engagement
(ROE(s)).
J060
(Rx)
ROEAUTH
Rules of
Engagement
Authorisation
The ROEAUTH is used by the North Atlantic

Council (NAC)/Defence Planning Committee
(DPC) to authorize implementation or
cancellation of specific rules of engagement
(ROE(s)).
J061
(Rx)
CBRN EDR
CBRN Effective
Downwind Report
The CBRN EDR is used to provide the effective

downwind data needed for prediction of fallout
areas following nuclear burst for either the
nearest 6 hours or for a period more than 6
hours ahead, including specific downwind
speeds and directions for up to seven selected
weapon yields.
2 - B - 62
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Optional
Para 3.2.1
Tasking
3, 4, 5
Para 3.2.1
Tasking
Optional
3, 4, 5
2, 3, 4, 5
Para 3.12
General Msg
Para 3.2.1
Tasking
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J064
(Tx/Rx)
EWMSNSUM
Electronic
Warfare Mission
Summary
The EWMSNSUM is used to summarize

significant electronic warfare missions and the
status of offensive electronic warfare assets.
J065
(Rx)
EWSTOPJAM
Electronic
Warfare Stop
Jamming
Message
J066
(Rx)
EWRTM
J070
(Rx)
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
LOI
3, 4, 5
Para 3.11
Mission
reporting
The EWSTOPJAM is used to terminate

immediately a jamming mission being conducted
by an electronic countermeasures asset.
Para 3.2.1
Tasking
Electronic
Warfare
Requesting/Tasking Message
The EWRTM is used to task component

commanders to perform electronic warfare (EW)
operations in support of the overall joint EW plan
and to support component EW operations.
3, 4, 5
Para 3.2.1
Tasking
WCO
Weapon Control
Order
The WCO is used to order new air defense (AD)

weapon control statuses for particular groundbased ad units for a given period of time.
4, 5
Para 3.2.1
Tasking
J071
(Tx/Rx)
TRACKREP
Target Track
Report
The TRACKREP is used to report aircraft

movement by track number.
J072
(Rx)
COVREP
Weapon
Coverage Report
J073
(Rx)
SENSCOVREP
Sensor Coverage
Report
2, 3, 4, 5
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
The COVREP is used to provide higher and

neighbouring echelons with the status of SAW
weapon coverage after deployment /
redeployment or in response to a CMO.
4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent
The SENSCOVREP is used to inform other

formations of SHORAD sensor coverage.
4, 5
Para 3.4.2
Collateral Data,
Mission
Dependent
2 - B - 63
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J076
(Rx)
ACTWARN
Activation
Warning
Message
The ACTWARN is used to inform nations,

military headquarters, SCs and other commands
of a potential requirement to activate
contingency plans, on call forces, special
surveillance missions or other unique
requirement to employ military forces.
1, 2, 3, 4,
J077
(Tx/Rx)
ACTREQ
Activation
Request
Message
The ACTREQ is used to request authority from

the NATO military committee (NAMILCOM) to
activate contingency plans, on call forces,
special surveillance missions or other unique
requirement to employ military forces.
Optional
Para 3.2.1
Tasking
J078
(Rx)
ACTORD
Activation Order
Message
The ACTORD is used to activate contingency

plans, on call forces, special surveillance
missions or other unique requirement to employ
military forces.
1, 2, 3, 4,
Para 3.2.1
Tasking
J079
(Tx/Rx)
LASERWARN
Laser Target
Marking Warning
Message
The LASERWARN is used to confirm the

activation arrangements for laser target
markers.
J082
(Tx/Rx)
LOGASSESSREP
Logistic
Assessment
Report
The LOGASSESSREP is used to standardise

the method for informing superior headquarters
of the command's logistics status and to provide
an assessment of the overall logistics situation
for forces, together with intended or
recommended action.
2 - B - 64
3, 4, 5
Optional
Para 3.2.1
Tasking
Para 3.2.1
Tasking
Para 3.8.1 &
3.8.2
Resource
Availability, Air
Segment Status
& Gnd Segment
Status
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J083
(Tx/Rx)
LOGUPDATE
Logistic Update
Report
The LOGUPDATE is used to provide NATO

commanders with a dynamic update of changes
to core database information on stockpiles of
specific equipment and consumable materiel
held by national forces declared to NATO, as
well as specified equipment and materiel held by
nations in support of such forces.
Optional
Para 3.8.1 &

3.8.2
Resource
Availability, Air
Segment Status
& Gnd Segment
Status
J092
(Tx/Rx)
EVENTREP
Events Report
The EVENTREP is used to provide NATO HQ

and Nations, through the SC chain of command,
information about important events, trends and
activities that do not have an element of extreme
urgency, but do influence peace support
operations force (PSOFOR) (e.g. IFOR, SFOR)
operations.
1, 2, 3, 4,
Para 3.12
General Msg
J095
(Tx/Rx)
SITREP
The SITREP is used to provide SACEUR with

information of the committed forces capabilities
with regard to current and release operations
and the overall situation of the involved parties.
1, 2, 3, 4,
J099
(Tx/Rx)
CISSITREP
The CISSITREP is used to provide a periodic

report of own communications and information
systems (CIS) status in support of operations
and exercises.
1, 2, 3, 4,
Situation Report
CIS Situation
Report
2 - B - 65
LOI
Para 3.8.1 &

3.8.2
Resource
Availability, Air
Segment Status
& Gnd Segment
Status
Para 3.8.1 &
3.8.2
Resource
Availability, Air
Segment Status
& Gnd Segment
Status
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J101
(Tx/Rx)
COMPASSESSREP
Compliance
Assessment
Report
The COMPASSESSREP is used to provide SCs

and NATO HQ information of the parties'
compliance with accepted agreements
concerning the designated 'safe' or other
area(s)/exclusion zone(s)/separation zone(s).
This report may include assessments.
1, 2, 3, 4,
J103
(Tx/Rx)
RECEXREP
Reconnaissance
Exploitation
Report
The Reconnaissance Exploitation Report

(RECEXREP) is used to report the results of an
air reconnaissance mission by the interpretation
of sensor data.
1, 2, 3, 4,
J110
(Tx/Rx)
INTREP
Intelligence
Report
The INTREP is used for the immediate

dissemination of key intelligence that could have
a significant impact on current and pending
operations and planning.
1, 2, 3, 4,
J111
(Rx)
INTSUM
Intelligence
Summary
The INTSUM is used to periodically inform

addressees of military, associated
political/economical or other related intelligence
and the assessment of this. It gives an indication
of change in potential OPFOR (opposing force)
capabilities, preparedness or military posture,
activities, intentions, objectives and/or courses
of action in peace, operations other than war,
and war.
1, 2, 3, 4,
J112
(Tx/Rx)
CIINTREP
CounterIntelligence and
Security Report
The CIINTREP is used for the immediate

dissemination of counter-intelligence and
security information that could have a significant
impact on current or pending operations and
planning.
Optional
2 - B - 66
Para 3.11
Mission
Reporting
Para 3.11
Mission
Reporting
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Para 3.4.1
Collateral Data,
Gen Battlefield
Pic
Para 3.12
General Msg
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
J113
(Tx/Rx)
CIINTSUM
Security
Summary
The CIINTSUM is used to inform addresses

periodically on current counter-intelligence and
security and to provide estimate of threat posed
by hostile intelligence services (his) or
subversive groups.
Optional
Para 3.12
General Msg
J114
(Rx)
SUPINTREP
Supplementary
Intelligence
Report
The SUPINTREP is used for providing all

addressees with comprehensive reviews of nontime-sensitive intelligence collected over an
extended period of time, or detailed intelligence
studies on specific subjects
Optional
Para 3.12
General Msg
J115
(Rx)
CISUPINREP
Security
Supplementary
Report
The CISUPINTREP is used to provide all

addressees with a comprehensive review of all
counter-intelligence (CI) data collected over an
extended period of time including an
assessment of trends in the development of the
CI situation. The CISUPINTREP is also used to
provide a comprehensive review of one or
several specific CI projects.
Optional
Para 3.12
General Msg
J154
CBRN 1 CHEM
CBRN 1
Chemical Report
The CBRN 1 Chemical Report is used to provide

the observer's initial report giving basic data on
a single chemical incident.
2, 3, 4, 5
Para 3.9.5 &

3.9.11
Payload Data,
CBRN &
Mission
Reporting
J155
CBRN 2 CHEM
CBRN 2
Chemical Report
The CBRN 2 Chemical Report is used to

disseminate evaluated data of a single chemical
incident, collected from chemical 1 reports.
1, 2, 3, 4,
5
Para 3.9.5
Payload/Sensor
Data, CBRN
2 - B - 67
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J156
CBRN 3 CHEM
CBRN 3
Chemical Report
The CBRN 3 Chemical Report is used to pass

immediate warning of predicted contamination
and hazard areas following a chemical incident.
1, 2, 3, 4,
5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J157
CBRN 4 CHEM
CBRN 4
Chemical Report
The CBRN 4 Chemical Report is used to report

chemical monitoring and survey results.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J158
CBRN 5 CHEM
CBRN 5
Chemical Report

information on areas of actual chemical
contamination.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J159
CBRN 6 CHEM
CBRN 6
Chemical Report

detailed information on a chemical incident.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
2 - B - 68
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J166
CBRN 1 BIO
CBRN 1
Biological Report
The CBRN 1 Biological Report is used to

provide the observer's initial report giving basic
data on a single biological incident.
2, 3, 4, 5
Para 3.9.5 &

3.9.11
Payload Data,
CBRN &
Mission
Reporting
J167
CBRN 2 BIO
CBRN 2
Biological Report
The CBRN 2 Biological Report is used to

disseminate evaluated data collected from
biological 1 reports of a single biological
incident.
1, 2, 3, 4,
5
Para 3.9.5
Payload/Sensor
Data, CBRN
J168
CBRN 3 BIO
CBRN 3
Biological Report
The CBRN 3 Biological Report is used to pass

and hazard areas following a biological incident.
1, 2, 3, 4,
5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J169
CBRN 4 BIO
CBRN 4
Biological Report
The CBRN 4 Biological Report is used to report

biological monitoring and survey results.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J170
CBRN 5 BIO
CBRN 5
Biological Report

information on areas of actual biological
contamination.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
2 - B - 69
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J171
CBRN 6 BIO
CBRN 6
Biological Report

detailed information on a biological incident.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J172
CBRN 1 RAD
CBRN 1
Radiological
Report
The CBRN 1 Radiological Report is used to

provide the observer's initial report giving basic
data on a single radiological release event.
2, 3, 4, 5
Para 3.9.5 &

3.9.11
Payload Data,
CBRN &
Mission
Reporting
J173
CBRN 2 RAD
CBRN 2
Radiological
Report

disseminate evaluated data of a single
radiological incident.
1, 2, 3, 4,
5
Para 3.9.5
Payload/Sensor
Data, CBRN
J174
CBRN 3 RAD
CBRN 3
Radiological
Report

pass immediate warning of predicted
contamination and hazard area following one
radiological release event.
1, 2, 3, 4,
5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J175
CBRN 4 RAD
CBRN 4
RADIOLOGICAL
REPORT

report detection data and passing monitoring
and survey results on a radiological incident.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
2 - B - 70
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J176
CBRN 5 RAD
CBRN 5
Radiological
Report

pass information on areas of actual
contamination following a radiological incident.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J177
CBRN 6 RAD
CBRN 6
Radiological
Report

pass detailed information on a radiological
incident.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J178
CBRN SITREP
CBRN Situation
Report
The CBRN Situation Report is used to pass

information on the chemical, biological,
radiological or nuclear situation.
2, 3, 4, 5
Para 3.4.3
Collateral Data,
CBRN
J180
CBRN 1 NUC
CBRN 1 Nuclear
Report
The CBRN 1 Nuclear Report is used to provide

the observer's initial report giving basic data on
a single nuclear attack.
2, 3, 4, 5
Para 3.9.5 &

3.9.11
Payload Data,
CBRN &
Mission
Reporting
J181
CBRN 2 NUC
CBRN 2 Nuclear
Report
The CBRN 2 Nuclear Report is used to

disseminate evaluated data of a single nuclear
attack.
1, 2, 3, 4,
5
Para 3.9.5
Payload/Sensor
Data, CBRN
2 - B - 71
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
J182
CBRN 3 NUC
CBRN 3 Nuclear
Report
The CBRN 3 Nuclear Report is used to pass

and hazard areas following a nuclear attack.
1, 2, 3, 4,
5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J183
CBRN 4 NUC
CBRN 4 Nuclear
Report
The CBRN 4 Nuclear Report is used to report

nuclear monitoring and survey results.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J184
CBRN 5 NUC
CBRN 5 Nuclear
Report

information on areas of actual nuclear
contamination.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
J185
CBRN 6 NUC
CBRN 6 Nuclear
Report

detailed information on a nuclear attack.
2, 3, 4, 5
Para 3.4.3 &

3.9.5
Collateral Data,
CBRN &
Payload/Sensor
Data, CBRN
2 - B - 72
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
LOI
N003
(Tx/Rx)
JAMWARN
Jamming
Warning
The JAMWARN is used to issue a warning

about own jamming operations.
1, 2, 3, 4,
N010
(Rx)
OPTASK ASUW
Operational
Tasking of AntiSurface Warfare
The OPTASK ASUW is used to promulgate

detailed tasking and instructions for the conduct
of anti-surface warfare.
N017
(Rx)
OPTASK LINK
Operational
Tasking Data
Links
N023
(Rx)
GREEN
N024
(Tx/Rx)
Para 3.4.2
Collateral Data,
Mission
Dependent
3, 4, 5
Para 3.2.1
Tasking
The OPTASK LINK is used to promulgate

detailed tasking and provide instructions
regarding the operation of tactical data links.
2, 3, 4, 5
Para 3.2.1
Tasking
Maritime Unit
Execution Order
The GREEN is used to task maritime patrol or

surveillance and ASW units.
1, 2, 3, 4,
Para 3.2.1
Tasking
PURPLE
Maritime Mission
Summary Report
The PURPLE is used to provide a

comprehensive summary of the activities of a
mission or event.
3, 4, 5
N025
(Tx/Rx)
LOCATOR
Maritime Force
Locator
The LOCATOR is used to report surface,

subsurface, air, or special interest units
operating in the maritime environment.
N028
(Rx)
OPTASK AIR
Operational
Tasking Organic
Aircraft
The OPTASK air is used for the OTC or

delegated authority to promulgate detailed
tasking and instructions for all organic aircraft.
This message is normally promulgated by the
OTC or the air coordinator.
2 - B - 73
2, 3, 4, 5
3, 4, 5
Para 3.11
Mission
Reporting
Para 3.4.2
Collateral Data,
Mission
Dependent
Para 3.2.1
Tasking
Index
Ref No
MTF Identifier
MTF Name
Function or purpose
N033
(Rx)
SATVULREP
Satellite
Vulnerability
Report
The SATVULREP is used to promulgate periods

of vulnerability to satellite reconnaissance and to
prescribe countermeasures to satellite
surveillance.
Optional
Para 3.12
General Msg
N067
(Rx)
OPTASK COMMS
Operational
Tasking
Communications
The OPTASK COMMS is used to promulgate

the communications plan in force and provide
communications related instructions.
2, 3, 4, 5
Para 3.2.1
Tasking
N068
(Rx)
OPTASK EW
Operational
Tasking
Electronic
Warfare
The OPTASK EW is used to promulgate

detailed tasking and instructions for the conduct
of electronic warfare.
3, 4, 5
Para 3.2.1
Tasking
2 - B - 74
LOI
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Comments
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Attachment B2 - 3: UAV System LOI APP- 11 Requirements
The following tables list the ADatP-3 messages contained in APP-11 that are required to
support each UAV system LOI (refer to the remarks in Section 1.6, Implementation of UAV
LOI in the CCI).
Level of Interoperability 1
Index
Ref No
MTF Identifier
MTF Name
A072
SYS.RRM
SYSTEM REPLY MESSAGE
A080
FRAGO
FRAGMENTARY ORDER
F095
INFLIGHTREP
INFLIGHT REPORT
J001
MSRCORRCANX
MESSAGE CORRECTION OR CANCELLATION
J009
FIRST HOSTILE ACT
FIRST HOSTILE ACT REPORT
J015
MARINTSUM
MARITIME INTELLIGENCE SUMMARY
J018
MIJIWARNREP
MIJI WARNING REPORT
J019
AIRATTACKWARN
AIR ATTACK WARNING
J020
CBRN CDR
CBRN CHEMICAL DOWNWIND REPORT
J076
ACTWARN
ACTIVATION WARNING MESSAGE
J078
ACTORD
ACTIVATION ORDER MESSAGE
J092
EVENTREP
EVENTS REPORT
J095
SITREP
SITUATION REPORT
J099
CISSITREP
J101
COMPASSESSREP
COMPLIANCE ASSESSMENT REPORT
J103
RECEXREP
RECONNAISSANCE EXPLOITATION REPORT
J110
INTREP
INTELLIGENCE REPORT
J111
INTSUM
INTELLIGENCE SUMMARY
J155
CBRN 2 CHEM
J167
CBRN 2 BIO
J173
CBRN 2 RAD
J181
CBRN 2 NUC
J156
CBRN 3 CHEM
J168
CBRN 3 BIO
J174
CBRN 3 RAD
J182
CBRN 3 NUC
N003
JAMWARN
JAMMING WARNING
N023
GREEN
MARITIME UNIT EXECUTION ORDER

2 - B - 71
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
All lower LOI messages are required plus the following messages (refer to the remarks in
Section 1.6, Implementation of UAV LOI in the CCI):
Index
Ref No
MTF Identifier
MTF Name
A026
ENSITREP
ENEMY LAND FORCES SITUATION REPORT
A031
OWNSITREP
OWN LAND FORCES SITUATION REPORT
A046
OBSREP
OBSTACLE REPORT
A058
ATI.ATR
ARTILLERY TARGET INTELLIGENCEARTILLERY TARGET REPORT
A059
ATI.TIR
ARTILLERY TARGET INTELLIGENCE-TARGET

INFORMATION REQUEST
A060
MET.CM
METEOROLOGICAL-COMPUTER
A061
MET.RFM
METEOROLOGICAL-REQUEST FOR MET
A062
MET.TA
METEOROLOGICAL-TARGET ACQUISITION
A070
SPRT.GEOM
SUPPORT-BATTLEFIELD GEOMETRY
A071
SYS.RFR
SYSTEM-REQUEST FOR REPORT
A088
RBTRECCEREP
ROAD, BRIDGE OR TUNNEL

RECONNAISSANCE REPORT
A092
GAPRECCEREP
GAP RECONNAISSANCE REPORT
A100
OBSRECCEREP
OBSTACLE RECONNAISSANCE REPORT
F015
AIRALLOC
AIR ALLOCATION MESSAGE
F058
ATO
AIR TASKING ORDER
J005
COMSPOT
COMMUNICATIONS SPOT REPORT
J006
INCSPOTREP
INCIDENT SPOT REPORT
J021
INTREQ
INTELLIGENCE REQUEST
J178
CBRN SITREP
CBRN SITUATION REPORT
J061
CBRN EDR
J071
TRACKREP
TARGET TRACK REPORT
J154
CBRN 1 CHEM
J157
CBRN 4 CHEM
J158
CBRN 5 CHEM
J159
CBRN 6 CHEM
J166
CBRN 1 BIO
J169
CBRN 4 BIO
J170
CBRN 5 BIO
J171
CBRN 6 BIO
J172
CBRN 1 RAD

2 - B - 72
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Index
Ref No
MTF Identifier
MTF Name
J175
CBRN 4 RAD
J176
CBRN 5 RAD
J177
CBRN 6 RAD
J180
CBRN 1 NUC
J183
CBRN 4 NUC
J184
CBRN 5 NUC
J185
CBRN 6 NUC
N017
OPTASK LINK
OPERATIONAL TASKING DATA LINKS
N025
LOCATOR
MARITIME FORCE LOCATOR
N067
OPTASK COMMS
OPERATIONAL TASKING COMMUNICATIONS
All lower LOI messages are required plus the following messages (refer to the remarks in
Section 1.6, Implementation of UAV LOI in the CCI):
Index
Ref No
MTF Identifier
MTF Name
A033
FM.CFF
FIRE MISSION-CALL FOR FIRE
A034
FM.SUB
FIRE MISSION-SUBSEQUENT ADJUSTMENT
A035
FM.MTO
FIRE MISSION-MESSAGE TO OBSERVER
A036
FM.FMC
FIRE MISSION-FIRE MISSION COMMAND
F031
MISREP
MISSION REPORT
J051
ROEIMPL
J060
ROEAUTH
J064
EWMSNSUM
J065
EWSTOPJAM
ELECTRONIC WARFARE STOP JAMMING

MESSAGE
J066
EWRTM
ELECTRONIC WARFARE
J079
LASERWARN

MESSAGE
N010
OPTASK ASUW

WARFARE
N024
PURPLE
N028
OPTASK AIR
OPERATIONAL TASKING ORGANIC AIRCRAFT
N068
OPTASK EW

WARFARE
2 - B - 73
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Level of Interoperability 4 and 5
All messages from LOI 1 & 2 tables contained in this attachment are required plus the
following messages (See remarks in Section 1.6):
Index
Ref No
MTF Identifier
MTF Name
A032
ORBATLAND
ORDER OF BATTLE - LAND FORCES
A069
SPRT.ACA
SUPPORT-AIRSPACE COORDINATION AREA
F001
AIRINTREP
AIR INTELLIGENCE REPORT
F011
ACO
AIRSPACE CONTROL ORDER
F012
ACMREQ
AIRSPACE CONTROL MEANS REQUEST
F032
ORBATAIR
ORDER OF BATTLE - AIR FORCES
F043
RESPONSE
AIR SUPPORT RESPONSE
J013
SARREQ
SEARCH AND RESCUE REQUEST
J016
MARINTREP
MARITIME INTELLIGENCE REPORT
J017
IFFPROD
IFF PROCEDURES
J029
AIRSTAT

J051
ROEIMPL
J060
ROEAUTH
J064
EWMSNSUM
J066
EWRTM
ELECTRONIC WARFARE
J070
WCO
WEAPON CONTROL ORDER
J072
COVREP
WEAPON COVERAGE REPORT
J073
SENSCOVREP
SENSOR COVERAGE REPORT
J079
LASERWARN

MESSAGE
N010
OPTASK ASUW

WARFARE
N024
PURPLE
N028
OPTASK AIR
OPERATIONAL TASKING ORGANIC AIRCRAFT
N068
OPTASK EW

WARFARE
2 - B - 74
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
NORTH ATLANTIC TREATY ORGANISATION

(NATO)
NATO Standardisation Agency (NSA)

STANDARDISATION AGREEMENT
(STANAG)
SUBJECT: Standard Interfaces of UAV Control System
(UCS) for NATO UAV Interoperability
Attachment B2 4
UAS Custom Tags
2 - B - 75
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
OVERVIEW
This Attachment describes the background, definition, and structure for the UAS custom
tags.
BACKGROUND
The core CRD is defined in the CRD Interface Control Document (ICD) (currently version
2.0.2.0) and uses a Common Route Object Model to describe the entities found in the
Common Route Definition. The object model also describes the relationships among the
entities. The Universal Modeling Language (UML) is used to specify the Common Route
Object Model. The tags describing the model entity attributes and definition are represented
in eXtensible Mark-up Language (XML) format.
The UAS custom tags were developed as new entities to the Common Route Object Model
and its tags are also represented in XML format.
COMMON ROUTE OBJECT MODEL
The following series of figures show how the core CRD object model has been changed to
add the custom UAS objects. Figure B2-4.1 shows the top level Common Route Object
Model used for establishing the relationships among the core CRD entities. The MISSION
and INTENT entities are modified by adding additional entities.
CRD
MISSION
VEHICLE
ROUTE
POINT
INTENT
PATH
ROUTE_POINT
TRANSITION
STATE
ADDITIONAL_POINT
Figure B2-4.1 Core Common Route Object Model
2 - B - 76
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Figure B2-4.2 shows the series of entities that have been associated with the Mission. In this
figure, the series of entities incorporate essential higher mission reference data that was
tasked through the Aircraft Collection Tasking Data Format (ACTDF). This allows the tracing
of collected data from the original tasking requirements.
Figure B2-4.2 Custom ACTDF Entities

Figure B2-4.3 shows the series of entities that have been created to allow a UAS to add data
collection and dissemination planning and communication planning to the existing core CRD
to generate a complete Mission Plan.
2 - B - 77
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
ORBIT_INTENT
EMERGENCY_INTENT
INTENT
IFF_INTENT
LIGHTS_INTENT
LOITER_INTENT
COLLECTION_INTENT
PAYLOAD_SETTINGS
DISSEMINATION_INTENT
COMMS_INTENT
PATTERNS
CONFIGURATION_ITEM
SAR_SETTINGS
GMTI_SETTINGS
Figure B2-4.3 Custom UAS Entities
2 - B - 78
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
DATA DICTIONARY
Table B2-4.1 is the data dictionary for the new UAS custom tags, or the individual data elements for each of the UAS entities. The
table parameters are defined as:
Name of entity or tag and description
Type: the name of the type of data under which attributes are defined
TypeInfo: the class category of data
Unit: the name of units of measure associated with the data (if applicable)
MinMax: the minimum or maximum value of the data (if applicable)
Format: the specific format of the data (if required)
Example: an example if available
Reference: name of an enumeration table. These appear after Table B2-4.1.
Card: the cardinality of the datarequired or optional
Table B2-4.1 Custom UAS Data Dictionary

ACTDF
Target collection mission identifier
ActdfMission
Type:
TypeInfo:
Unit:
MinMax:
ActdfMissionElement
Collection
N/A
N/A
Collection manager classification and control markings/data
ActdfMetadata
Type:
TypeInfo:
Unit:
MinMax:
ActdfMetadataElement
Collection
N/A
N/A<= x <= N/A
CollectionRequirements
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
format:
example:
reference:
card:
required
format:
example:
reference:
card:
required
Target collection details
CollectionRequirementsElement
Collection
N/A
N/A
2 - B - 79
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
ActdfMissionElement
MissionIdentifier
Type:
TypeInfo:
Unit:
MinMax:
An alternative identifier to "Mission Number" Either MissionNumber OR

MissionIdentifier should be filled-in
STRING
Primitive
format:
example:
reference:
card:
0 <= x <= 54
"Mission Number" or the 54 Character "Mission Identifier" must be
Type:
TypeInfo:
Unit:
MinMax:
MissionNumberElement
Container
N/A
N/A
used..
format:
example:
reference:
card:
Optional
The project code which is part of the mission number.
ProjectCode
Type:
TypeInfo:
Unit:
MinMax:
Optional
One of two ways to Identify a particular mission, either this 10 character
MissionNumber
String
Primative
N/A
N/A
format:
example:
reference:
card:
([A-Y][A-Z]|Z[A-Y])
required
ActdfMetadataElement
OverallClassification
Overall classification is defined in accordance with the,
Intelligence Community
Information Security Marking (IC ISM)
Type: reference
TypeInfo: Schema
Unit: N/A
MinMax: N/A
ACTDFACTDFACTDFOriginator
Type: String
TypeInfo: Primative
Unit: N/A
MinMax: N/A
ACTDFACTDFTaskGenerationTimestamp
Type:
TypeInfo:
Unit:
MinMax:
UTCDateTime
Primative
N/A
N/A
conditional
format:
example:
reference:
card:
conditional
Unit which originated the requirement.
Date/time the ACTDF file was created or modified. Creation Timestamp

will change anytime there is a change to the ACTDF. So, for every
Requirement ID control date change, there will be a Creation
format:
Timestamp change. But, there will not be a control date change for
example:
every Creation Timestamp change, ie Mission ID change with all the
reference:
same requirements.
card:
SectorBlankingElement
SectorBlankingID
format:
example:
reference:
card:
Identifier for area where collection is not permitted.
2 - B - 80
YYYY-MM-DDThh:mm:ssZ
required
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Type:
TypeInfo:
Unit:
MinMax:
STRING
Primitive
N/A
N/A
SectorBlankingName
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
A.42
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Optional
Name of an area where collection is not permitted
STRING
Primitive
N/A <= x <= N/A
COLLECTION_INTENT
Unique identifier for collection intent
ID
Type:
TypeInfo:
Unit:
MinMax:
ID
Reference
N/A
0 <= x <= 2147483647
OPERATION_MODE
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
UAV flight pattern or sensor search pattern associated with data

collection for a specific payload
PATTERN
Type:
TypeInfo:
Unit:
MinMax:
PATTERN
Collection
N/A
N/A
List of payloads used for this mission
PAYLOAD_LIST
Type:
TypeInfo:
Unit:
MinMax:
CONFIGURATION_ITEM
Container
N/A
N/A
PAYLOAD_SETTINGS
Type:
TypeInfo:
Unit:
MinMax:
Mode of operation for selected payload during a specific portion of the

mission. An onboard sensor data recorder is considered a Payload. A
separate communications relay is a Payload, but not the comms
systems which is part of the basic air vehicle configuration.
Specific settings to be used by the payload during a specific portion of

the mission
PAYLOAD_SETTINGS
Collection
N/A
N/A
CollectionRequirements
Control_UTCDateTime
Date/Time the Requirement ID was created or modified. The
2 - B - 81
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Type:
TypeInfo:
Unit:
MinMax:
UTCDateTime
Primative
N/A
N/A
RequestorID
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <= 50
RequirementName
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <= 100
RequirementPriority
Type:
TypeInfo:
Unit:
MinMax:
integer
Primative
N/A
0<= x <= 999
RequirementsID
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <= 12
Type:
TypeInfo:
Unit:
MinMax:
TaskElement
collection
N/A
N/A
Task
Requirement ID may not change if the exact same tasks were flown
over several days. Control Date changes only when there is a change
format:
to the Requirement ID. So, for every Requirement ID control date
example:
change, there will be a Creation Timestamp change. But, there will not reference:
be a control date change for every Creation Timestamp change, ie
Mission ID change with all the same requirements.
card:
Code for the unit which created the ACTDF. Free text
format:
example:
reference:
card:
User specified text name providing descriptive data about the collection
requirement purpose; usually the same as the nomination name.
format:
example:
reference:
card:
The relative importance of the collection requirement, where the lower
assigned number value, the higher the priority.
format:
example:
reference:
card:
User specified identification to facilitate tracking collection requirements.
format:
example:
reference:
card:
Individual intel collection segments of the overall collection message.
format:
example:
reference:
card:
required
conditional
conditional
000-999
conditional
required
required
COMMS_INTENT
ANTENNA_MODE
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
List of communication devices used for this leg of mission
COMMS_LIST
Type:
TypeInfo:
Unit:
Operating mode for communication antennas
String
Enumeration
N/A
CONFIGURATION_ITEM
Collection
N/A
format:
example:
reference:
2 - B - 82
A.52
Required
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
COMMS_SECURITY
Type:
TypeInfo:
Unit:
MinMax:
Double
Primitive
N/A
0 <= x <= 1.0E100
A.53
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Assigned receiver frequency
Double
Primitive
Hz
0 <= x <= 1.0E100
FREQ_TRANSMIT
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Selectable data transmission rate
FREQ_RECEIVE
Type:
TypeInfo:
Unit:
MinMax:
Required
Normal if TRUE; Zeroize if FALSE
Boolean
Primitive
N/A
N/A
DATA_RATE
Type:
TypeInfo:
Unit:
MinMax:
card:
Operating modes for communication devices
COMMS_MODE
Assigned transmitter frequency
Double
Primitive
Hz
0 <= x <= 1.0E100
Unique identifier for communication intent
ID
Type:
TypeInfo:
Unit:
MinMax:
ID
Reference
N/A
0 <= x <= 2147483647
LINK_LOSS_OK
Type:
TypeInfo:
Unit:
MinMax:
BOOLEAN
Primative
N/A
N/A
POWER_TRANSMIT
Type:
TypeInfo:
Unit:
MinMax:
A pre-planned flag indicating that loss of the data link will not cause
initiation of contingency actions.
Assignable transmission power level
Decimal
Primitive
Percent
0.00 <= x <= 1.00
RECEIVER_ALTITUDE
The altitude of the receiver, used for directional antennas. This could be
2 - B - 83
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
a ground location or a satellite position
Type:
TypeInfo:
Unit:
MinMax:
ALTITUDE
Container
N/A
N/A
RECEIVER_LOCATION
Type:
TypeInfo:
Unit:
MinMax:
Short
Primitive
N/A
0 <= x <= 32767
Short
Primitive
N/A
0 <= x <= 32767
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Assigned transmitter slot
Short
Primitive
N/A
0 <= x <= 32767
Time between transmission and expected reply, after which non-reply
is judged as lost communication
TIME_OUT
Type:
TypeInfo:
Unit:
MinMax:
Optional
Assigned receiver slot
SLOT_TRANSMIT
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Number of retransmission attempts after a condition of lost
communication is reached
SLOT_RECEIVE
Type:
TypeInfo:
Unit:
MinMax:
Optional
The coordinates of the receiver, used for directional antennas. This

could be a ground location or a satellite position
WGS84_POSITION
Container
N/A
N/A
RETRANSMIT
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Double
Primitive
seconds
0 <= x <= 1.0E100
COMMS_SET_IN
Type:
TypeInfo:
Unit:
MinMax:
COMMS_INTENT
Container
N/A
N/A
COMMS_SET_OUT
Type:
Setting of any communication devices needed to receive external data

for dissemination
Setting of any communication devices needed to transmit internal data

for dissemination
COMMS_INTENT
format:
2 - B - 84
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
TypeInfo:
Unit:
MinMax:
Container
N/A
N/A
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Unique identifier for dissemination intent
ID
Type:
TypeInfo:
Unit:
MinMax:
ID
Reference
N/A
0 <= x <= 2147483647
INPUT_SOURCE
Type:
TypeInfo:
Unit:
MinMax:
CONFIGURATION_ITEM
Collection
N/A
OUTPUT_DESTINATION
Type:
TypeInfo:
Unit:
MinMax:
The start time of the dissemination process based on time since

making the last waypoint
Double
Primitive
seconds
0 <= x <= 1.0E100
The stop time of the dissemination process based on time since
making the last waypoint
TIME_STOP
Type:
TypeInfo:
Unit:
MinMax:
Destination device which will receive the data. This could be an internal
recorder, sensor processor, or communication datalink.
CONFIGURATION_ITEM
Collection
N/A
TIME_START
Type:
TypeInfo:
Unit:
MinMax:
Originating device providing data for dissemination. This could be a

sensor streaming data, a recorder, post-processed data from an
onboard sensor processor, or a comm relay.
Double
Primitive
seconds
0 <= x <= 1.0E100
DSATargetElement
The DSA target identifier
DSA_ID
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <=20
The target name which generally provides information about the
target's location and/or function.
TargetName
Type:
TypeInfo:
String
Primative
format:
example:
2 - B - 85
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Unit:
MinMax:
N/A
0<= x <= 100
reference:
card:
required
format:
example:
reference:
card:
N/A
A.55
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
EMERGENCY_INTENT
EMERGENCY_RECOVERY_SETTINGS
Type:
TypeInfo:
Unit:
MinMax:
EMERGENCY_ROUTE_ENTRY_ID
Type:
TypeInfo:
Unit:
MinMax:
Entry waypoint number. Emergency route starts at entry waypoint
ID
Primitive
EMERGENCY_ROUTE_ID
Type:
TypeInfo:
Unit:
MinMax:
Settings used for emergency landings
STRING
Enumeration
Container
N/A
ID of the Route to activate as the emergency route at this waypoint
ID
Primitive
GMTI_SETTINGS
Last range bar for GMTI scan
BAR_END
Type:
TypeInfo:
Unit:
MinMax:
Short
Primitive
N/A
0 <= x <= 32767
First range bar for GMTI scan
BAR_START
Type:
TypeInfo:
Unit:
MinMax:
Short
Primitive
N/A
0 <= x <= 32767
Maximum targets per coherent processing interal
MAX_TARGETS
Type:
TypeInfo:
Unit:
MinMax:
SHORT
Primitive
N/A
0 <= x <= 32767
MIN_DETECTABLE_VELOCITY
Type:
TypeInfo:
Unit:
MinMax:
Minimum detectable velocity of targets
DOUBLE
Primitive
feet/second
0.0 <= x <= 1.0E4
2 - B - 86
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Minimum target Signal to Noise Ration (SNR)
MIN_SNR
Type:
TypeInfo:
Unit:
MinMax:
DOUBLE
Primitive
dB
0.0 <= x <= 1.0E4
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
DOUBLE
Primitive
feet
0.0 <= x <= 1.0E4
format:
example:
reference:
card:
Optional
Short
Primitive
N/A
0 <= x <= 32767
format:
example:
reference:
card:
Optional
Boolean
Primitive
N/A
N/A
format:
example:
reference:
card:
Optional
Short
Primitive
N/A
0 <= x <= 32767
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
MIN_TARGET_RCS
Type:
TypeInfo:
Unit:
MinMax:
DOUBLE
Primitive
dBsf
0.0 <= x <= 1.0E4
RANGE_RESOLUTION
Type:
TypeInfo:
Unit:
MinMax:
The range resolution
DOUBLE
Primitive
feet
0.0 <= x <= 1.0E4
Slant range to the center of the scanned area (Arc Mode only)
SLANT_RANGE
Type:
TypeInfo:
Unit:
MinMax:
Minimum target Radar Cross Section (RCS)
IFF_INTENT
MODE 1 CODE
Type:
TypeInfo:
Unit:
MinMax:
MODE 1 ENABLE
Type:
TypeInfo:
Unit:
MinMax:
Off if TRUE; On if FALSE
MODE 2 CODE
Type:
TypeInfo:
Unit:
MinMax:
MODE 2 ENABLE
Type:
TypeInfo:
Unit:
MinMax:
Boolean
Primitive
N/A
N/A
MODE 3/A CODE
2 - B - 87
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Type:
TypeInfo:
Unit:
MinMax:
Short
Primitive
N/A
0 <= x <= 32767
MODE 3/A DURATION

Type:
TypeInfo:
Unit:
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
Boolean
Primitive
N/A
N/A
Boolean
Primitive
N/A
N/A
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Normal if TRUE; Zeroize if FALSE
Boolean
Primitive
N/A
N/A
MODE C ENABLE
Type:
TypeInfo:
Unit:
format:
example:
reference:
card:
Normal if TRUE; Hold if FALSE
MODE 4 ZEROIZE
Type:
TypeInfo:
Unit:
MinMax:
Optional
Boolean
Primitive
N/A
N/A
MODE 4 HOLD
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
A if TRUE; B if FALSE
MODE 4 ENABLE
Type:
TypeInfo:
Unit:
MinMax:
Optional
Boolean
Primitive
N/A
N/A
MODE 4 A/B
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Boolean
Primitive
N/A
N/A
MODE 3/A IDENT
Optional
Amount of time Mode 3/A is Squawking
Double
Primitive
seconds
0 <= x <= 1.0E100
MODE 3/A ENABLE
format:
example:
reference:
card:
Boolean
Primitive
N/A
format:
example:
reference:
2 - B - 88
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
MinMax:
N/A
card:
Optional
OPERATION_MODE
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
format:
example:
reference:
card:
A.51
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Required
format:
example:
reference:
card:
Required
INTENT
COLLECTION_INTENT
Type:
TypeInfo:
Unit:
MinMax:
COLLECTION_INTENT
Collection
N/A
N/A
COMMS_INTENT
Type:
TypeInfo:
Unit:
MinMax:
COMMS_INTENT
Collection
N/A
N/A
Type:
TypeInfo:
Unit:
MinMax:
IFF_INTENT
Container
N/A
N/A
Controls the air vehicle lights during the mission
LIGHTS_INTENT
Container
N/A
N/A
LOITER_INTENT
Type:
TypeInfo:
Emergency actions allowed for the air vehicle
Provides the IFF settings for discrete portions of the mission
LIGHTS_INTENT
Type:
TypeInfo:
Unit:
MinMax:
Contains one or more dissemination objects, which identify the output

destination device for collected information from the payload
EMERGENCY_INTENT
Container
N/A
N/A
IFF_INTENT
Type:
TypeInfo:
Unit:
MinMax:
Contains one or more communications objects, which identify the

communication devices for C2, payload information dissemination, and
other communications interfaces
Collection
N/A
N/A
EMERGENCY_INTENT
Type:
TypeInfo:
Unit:
MinMax:
Contains one or more collection objects, which identify the payloads,

settings, and collection patterns used in the mission
A planned delay enroute
LOITER_INTENT
Container
format:
example:
2 - B - 89
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Unit:
MinMax:
N/A
N/A
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
A.41
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
required
format:
example:
reference:
card:
N/A
A.56
Optional
format:
example:
reference:
card:
Optional
LIGHTS_INTENT
LIGHT_MODE
Type:
TypeInfo:
Unit:
MinMax:
Boolean
Primative
N/A
N/A
Selection of types of lights
LIGHTS
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
N/A
LOCTargetElement
The LOC target identifier
LOC_ID
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <= 20
TargetName
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0<= x <= 100
LOITER_INTENT
A designate pattern for a loiter
LOITER_TYPE
Type:
TypeInfo:
Unit:
MinMax:
STRING
Enumeration
Container
N/A
The maximum width of the inbound/outbound legs of a loiter pattern
LOITER_WIDTH
Type:
TypeInfo:
Unit:
MinMax:
DOUBLE
Primitive
feet
0.0 <= x <= 1.0E4
The number of full circuits of the loiter pattern that must be completed
REQ_LOOPS
Type:
TypeInfo:
SHORT
Primative
format:
example:
2 - B - 90
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Unit:
MinMax:
ACTDFACTDF
N/A
0<= x <= 10000
reference:
card:
Optional
MissionNumberElement
2 alphanumeric, do not use 9Z
ProgramCode
Type: STRING
example:
Unit: N/A
MinMax: N/A
STRING
Primitive
N/A
N/A
STRING
Primitive
N/A
n/a
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
4 digits, no explicit constraint on range
Year_Int
Type:
TypeInfo:
Unit:
MinMax:
Optional
Must be 2 digits, 01-99
Sortie_Int
Type:
TypeInfo:
Unit:
MinMax:
reference:
card:
01-12 0r 1-12
Month_Int
Type:
TypeInfo:
Unit:
MinMax:
format: ( 0-8A-Z][0-9A-Z]|9[0-9A-Y])TypeInfo: Primitive
Integer
Primitive
N/A
n/a
PATTERN
Number of swaths per Spot
ALONG_TRACK
Type:
TypeInfo:
Unit:
MinMax:
Short
Primitive
N/A
0 <= x <= 32767
Altitude for the pattern
ALTITUDE
Type:
TypeInfo:
Unit:
MinMax:
ALTITUDE
Container
N/A
N/A
Number of payload frames per swath
CROSS_TRACK
Type:
TypeInfo:
Short
Primitive
format:
example:
2 - B - 91
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Unit:
MinMax:
N/A
0 <= x <= 32767
PATTERN_MODE
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
PATTERN_START
Type:
TypeInfo:
Unit:
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
String
Enumeration
N/A
REF_1
Type:
TypeInfo:
Unit:
MinMax:
WGS84_POSITION
Container
N/A
N/A
REF_2
Type:
TypeInfo:
Unit:
MinMax:
WGS84_POSITION
Container
N/A
N/A
REF_3
Type:
TypeInfo:
Unit:
MinMax:
REF_4
WGS84_POSITION
Container
N/A
N/A
format:
example:
reference:
card:
A.49
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
A.50
Optional
The duration of the pattern
Double
Primitive
seconds
0 <= x <= 1.0E100
PATTERN_TYPE
Optional
The start time of the pattern based on time since making the last
waypoint
Double
Primitive
seconds
0 <= x <= 1.0E100
PATTERN_TIME
Type:
TypeInfo:
Unit:
MinMax:
The class of collection patterns. This is used with PATTERN_TYPE to

define the full pattern functions. Defines patterns for UAV or sensor
search.
reference:
card:
The geometry of the collection pattern. This defines an area or path for
sensor data collection. This is used with PATTERN_MODE to define
the full pattern functions
Geographic coordinate to define an area, point, or payload startingpoint. The actual definition of this point is based on the selection of
PATTERN_MODE and PATTERN_TYPE. For a circle or spiral, REF_1
format:
would be the center point; for an area search, REF_1 would be the first example:
point to define the area. REF_! could also be the center point for Spot
reference:
mode on a Point pattern.
card:
Geographic coordinate to define an area, point, or payload startingpoint. The actual definition of this point is based on the selection of
PATTERN_MODE and PATTERN_TYPE. For an area search, REF_2
format:
would be the second point to define the area; for a line pattern, it would example:
b e the second point along the path..
reference:
card:
Geographic coordinate to define an area, point, or payload starting. The
actual definition of this point is based on the selection of
PATTERN_MODE and PATTERN_TYPE.
format:
example:
reference:
card:
2 - B - 92
Optional
Optional
Optional
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Type:
TypeInfo:
Unit:
MinMax:
WGS84_POSITION
Container
N/A
N/A
REF_5
Type:
TypeInfo:
Unit:
MinMax:
WGS84_POSITION
Container
N/A
N/A
REF_6
Type:
TypeInfo:
Unit:
MinMax:
WGS84_POSITION
Container
N/A
N/A
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
The spacing between pattern tracks for selected pattern. The actual
definition of the spacing is based on the selection of PATTERN_MODE
and PATTERN_TYPE. For a Raster mode the spacing is the distance
format:
between tracks; for spirals, the incremental added distance between
example:
segments; for a circle, the circle radius.
reference:
card:
Optional

WGS84_POSITION
Container
N/A
N/A
The elevation of the target
ELEVATION
Container
N/A
N/A
TRACK_SPACING
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Geographic coordinate for the target
TARGET_ELEV
Type:
TypeInfo:
Unit:
MinMax:
Optional

AIRSPEED
Container
N/A
N/A
TARGET
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Airspeed during the pattern
SPEED
Type:
TypeInfo:
Unit:
MinMax:

Short
Primitive
feet
0 <= x <= 32767
PAYLOAD_SETTINGS
ANGLE_AZ
Setting for the centerline of the payload azimuth angle
2 - B - 93
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Type:
TypeInfo:
Unit:
MinMax:
Decimal
Primitive
degrees
0.00 <= x <= 360.00
Decimal
Primitive
degrees
0.00 <= x <= 90.00
STRING
Enumeration
N/A
N/A
COMPRESSION_RATIO
Type:
TypeInfo:
Unit:
MinMax:
Decimal
Primitive
degrees
0.00 <= x <= 360.00
Optional
format:
example:
reference:
card:
A.43
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Functional settings for the GMTI payload
GMTI_SETTINGS
Container
N/A
N/A
Selection for the EO/IR output
OUTPUT
Type:
TypeInfo:
format:
example:
reference:
card:
Setting for Field Of View in the vertical plane
GMTI_SETTINGS
Type:
TypeInfo:
Unit:
MinMax:
A.56
Optional
Setting for Field Of View in the horizontal plane

Decimal
Primitive
degrees
0.00 <= x <= 360.00
FOV_VER
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Compression method to compress payload data
String
Enumeration
N/A
FOV_HOR
Type:
TypeInfo:
Unit:
MinMax:
Optional
Selected compression parameter
Short
Primitive
N/A
0 <= x <= 32767
COMPRESSION_TYPE
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
The pointing angle of the payload, relative to the air vehicle's body OR
relative to true North
ANGLE_REL
Type:
TypeInfo:
Unit:
MinMax:
Optional
Setting for the centerline of the payload elevation angle
ANGLE_ELEV
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
String
Enumeration
format:
example:
2 - B - 94
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
Unit:
MinMax:
N/A
PAYLOAD_MODE
Type:
TypeInfo:
Unit:
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
Type:
TypeInfo:
Unit:
MinMax:
A.46
Optional
format:
example:
reference:
card:
A.47
Optional
format:
example:
reference:
card:
A.48
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Assignment of an identifier for marking the start or stop of a recording

session
Double
Primitive
N/A
0 <= x <= 1.0E100
SAR_SETTINGS
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Flag to allow recorder to overwrite existing data. No overwrite if TRUE;

Overwrite if FALSE
BOOLEAN
Primitive
N/A
N/A <= x <= N/A
RECORDING_INDEX
Type:
TypeInfo:
Unit:
MinMax:
N/A
A.42
Optional
Selection for a particular SAR or GMTI function Mode

String
Enumeration
N/A
RECORDER_OVERWRITE
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
Polarity setting
String
Enumeration
N/A
RADAR_MODE
Type:
TypeInfo:
Unit:
MinMax:
A.45
Optional
Selection for a specific method for payload pointing
String
Enumeration
N/A
POLARITY
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
The state of operation of the payload (e..g., Off, Standby, Stowed, etc.)
STRING
Enumeration
Container
N/A
POINTER_MODE
A.44
Optional
Specific payload function selected when in an operating mode
String
Enumeration
N/A
PAYLOAD_OPERATING_MODE
reference:
card:
Functional settings for the SAR payload
SAR_SETTINGS
Container
N/A
N/A
2 - B - 95
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
SCENE_NUMBER
Type:
TypeInfo:
Unit:
MinMax:
Double
Primitive
N/A
0 <= x <= 1.0E100
WEAPONS_CODE
Type:
TypeInfo:
Unit:
MinMax:
Assignment of an identifier for information collected by a payload within

an assigned portion of a mission
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional
Assignment of an Laser codes or other types of codes within an

assigned portion of a mission
DOUBLE
Primitive
N/A
0.0 <= x <= 1.0E4
PointTargetElement
The Basic Encyclopedia (BE) number of the target.
BENumber
Type:
TypeInfo:
Unit:
MinMax:
String
Primative
N/A
0 <= x <= 15
Target_CategoryCode
Type:
TypeInfo:
Unit:
MinMax:
.{10}(.{5})?
Optional
The target category code is based on a breakdown of targets into major

groups.
integer
Primative
N/A
N/A
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
required
format:
example:
reference:
card:
Optional
format:
example:
reference:
card:
Optional

TargetName
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
String
Primative
N/A
0<= x <= 100
SAR_SETTINGS
Range from the sensor to the center of a strip, when the SAR is in Strip
Mode
RANGE
Type:
TypeInfo:
Unit:
MinMax:
DOUBLE
Primitive
feet
0.0 <= x <= 1.0E4
Image resolution setting for the SAR
RESOLUTION
Type:
TypeInfo:
Unit:
MinMax:
DOUBLE
Primitive
inches
0.0 <= x <= 1.0E4
2 - B - 96
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
TargetDataElement
Area where data collection is not permitted
SectorBlanking
Type:
TypeInfo:
Unit:
MinMax:
SectorBlankingElement
Container
N/A
N/A
Optional
format:
example:
reference:
card:
required
format:
example:
reference:
card:
conditional
format:
example:
reference:
card:
conditional
format:
example:
reference:
card:
conditional
Indicates the collection type for the target to be collected as either a

point, Line of Communication (LOC), or Directed Search Area (DSA).
TargetType
Type:
TypeInfo:
Unit:
MinMax:
format:
example:
reference:
card:
TargetTypeElement
Container
N/A
N/A
TargetTypeElement
Specific collection parameters or constraints associated with a DSA
target.
DSATarget
Type:
TypeInfo:
Unit:
MinMax:
PointTargetElement
Container
N/A
N/A
Specific collection parameters or constraints associated with a LOC
target.
LOCTarget
Type:
TypeInfo:
Unit:
MinMax:
PointTargetElement
Container
N/A
N/A
Specific collection parameters or constraints associated with a point
target.
PointTarget
Type:
TypeInfo:
Unit:
MinMax:
PointTargetElement
Container
N/A
N/A
TaskElement
EEI_ID
Type:
TypeInfo:
Unit:
MinMax:
EeidRefElement
Container
N/A
N/A
format:
example:
reference:
card:
Specific collection parameters or constraints associated which a

specific target.
TargetData
Type:
Identification code for an essential element of information set within a

task. EEI identification codes are defined by the user in the Exploitation
Requirements section of the ACTDFACTDF.
TargetDataElement
format:
2 - B - 97
"EEI_[0-9]+"
conditional
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
TypeInfo:
Unit:
MinMax:
Container
N/A
N/A
required
The relative importance of the task, where the lower assigned number
value, the higher the priority.
TaskPriority
Type:
TypeInfo:
Unit:
MinMax:
example:
reference:
card:
integer
Primative
N/A
0<= x <= 999
format:
example:
reference:
card:
2 - B - 98
000-999
required
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
A.41 LIGHTS
Code
Tag Value
Number
Description
NAV
Navigation lights
NAV_IR
Infrared navigations lights
STROBE
Strobe lights
STROBE_IR
Infrared strobe lights
NVD
Night Vision Devices

reserved
LANDING
Landing lights
LANDING_IR
Infrared landing lights
ANTI_COLLISION
Anti-Collision lights
A.42 PAYLOAD OPERATING MODE

Code
Tag Value
Number
Description
SYS_PWR_OFF
System power OFF
SYS_PWR_ON
System power ON
DEVICE_PWR_OFF
Device power OFF
DEVICE_PWR_ON
Device power ON
INITIALIZE
Initialize
STANDBY
Standby
ACTIVATE
Activate
CALIBRATE
Calibrate
CAGE
Cage
STOW
Stow
DEPLOY
Deploy the payload
A.43 COMPRESSION TYPE

Code
Tag Value
Number
Description
VIDEO_HUFF
EO/IR Huffman
VIDEO_QUANT
EO/IR quantization
SAR_HUFF
SAR Huffman
SAR_QUANT
SAR quantization
A.44 OUTPUT
Code
Tag Value
Number
Description
NONE
No output
EO
Electro-Optic
2 - B - 99
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
IR
Infrared
BOTH
Both
A.45 PAYLOAD MODE

Code
Tag Value
Number
Description
BW
Black & white Mode
COLOR
Color Mode
CLUTTER
Clutter Map
MTI
Moving Target indicator
REC_GOTO
Go To on recorder
REC_RECORD
Record on recorder
REC_SEEK
Seek on recorder
REC_PLAY
Play on recorder
REC_REWIND
Rewind on recorder
REC_PAUSE
Pause the recorder
REC_STOP
Stop the recorder
A.46 POINTER MODE

Code
Tag Value
Number
Description
NONE
No Value
ANGLE_AV
Angle Relative to AV
SLEW_AV
Slewing Rate Relative to

AV
SLEW_INERTIAL
Slewing Rate Relative to

Inertial
POSITION_SLAVED
Lat-Long Slaved
A.47 POLARITY
Code
Tag Value
Number
Description
BLACK
Black Hot
WHITE
White Hot
A.48 RADAR MODE

Code
Tag Value
Number
Description
LOW_RES
Low resolution
MED_RES
Medium resolution
HIGH_RES
High resolution
SAR_POLAR
SAR polar format
2 - B - 100
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
SAR_POINT
SAR point image
SAR_STRIP
SAR using strip function
GMTI_ARC
Ground moving target

indication using the Arc
function
GMTI_SPOT
Ground moving target

indication using the
Spot function
A.49 PATTERN MODE

Code
Tag Value
Number
Description
RASTER_SENS
Sensor searches in
Raster pattern
RASTER_UAV
UAV flies a Raster pattern
SPOT_SENS
Sensor collects data from

series of designated
Spots
SPOT_UAV
UAV flies to designated

Spots for optimal sensor
view
TARGET_SENS
Sensor collects data from

same Target in separate
scenes
TARGET_UAV
UAV flies a Target pattern
WAS_SENS
Sensor performs a Wide

Area Search pattern
WAS_UAV
UAV flies a Wide Area

Search pattern
A.50 PATTERN TYPE

Code
Tag Value
Number
Description
POINT
Point
LINE
Line
TRACK_FOLLOW
Follow specific track over

the ground
SPIRAL
Spiral, normal
SPIRAL_REC
Spiral, rectangular
CIRCLE
Circle
RACETRACK
Racetrack
QUADRILATERAL
Quadrilateral
POLYGON
Polygon
FIGURE_8
Figure 8
OWNTRACK
Pattern following path of

air vehicle
2 - B - 101
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
A.51 IFF OPERATING MODE

Code
Tag Value
Number
Description
OFF
Off
STANDBY
Standby
NORMAL
Normal
EMERGENCY
Emergency
A.52 ANTENNA MODE

Code
Tag Value
Number
Description
STOW
Stow
DIRECTIONAL
Directional
OMNI
Omni
AUTO
Auto
POINT_TO_RECEIVER
Point to the external

transceiver
A.53 COMMS OPERATING MODE

Code
Tag Value
Number
Description
SYS_PWR_OFF
System power OFF
SYS_PWR_ON
System power ON
DEVICE_PWR_OFF
Device power OFF
DEVICE_PWR_ON
Device power ON
INITIALIZE
Initialize
STANDBY
Standby
RX_TX
Receive and transmit
RX
Receive only
TX
Transmit only
A.55 EMERGENCY MODE

Code
Tag Value
Number
Description
PWR_OFF
Power OFF
PWR_ON
Power ON
ARM
Arm the system
DISARM
Disarm the system
ACTIVATE
Activate the system
2 - B - 102
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
A.55 LOITER TYPES

Code
Tag Value
Number
Description
CIRCLE
Circle (Hover if radius is

zero)
FAA_HOLD
FAA holding pattern
FIGURE_8
Figure 8
RACETRACK
Racetrack
A.56 ANGLE REL

Code
Tag Value
Number
Description
Uses the longitudinal

centerline of the air
vehicle as the reference
Uses true North as the
reference
BODY
NORTH
2 - B - 103
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
UAS CUSTOM TAG XML SCHEMA
The following schema must be used in conjunction with the core CRD ICD in the Data
Exchange Model for Data Validation.
<?xml version="1.0" encoding="UTF-8"?>


<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:element name="UAS_Custom">
<xs:annotation>
<xs:documentation>Root for UAV custom tags</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:all>
<xs:element name="ACTDF" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="ActdfMetadata"
type="ActdfMetadataElement"/>
<xs:element name="ActdfMission"
type="MissionElement"/>
<xs:element name="CollectionRequirements"
type="CollectionRequirementElement" maxOccurs="unbounded"/>
<xs:element name="ExploitationRequirements"
type="ExploitationRequirementElement" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="UAV"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:simpleType name="EeiIdElement">
<xs:restriction base="xs:ID">
<xs:pattern value="EEI_[0-9]+"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="EeiIdRefElement">
<xs:restriction base="xs:IDREF">
<xs:pattern value="EEI_[0-9]+"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="UuidElement">
<xs:restriction base="xs:string">
<xs:pattern value="[0-9,a-f]{8}[\-][0-9,a-f]{4}[\-][0-9,a-f]{4}[\-][0-9,a-f]{4}[\-][0-9,a-f]{12}"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="MissionNumberElement">
<xs:sequence>
<xs:element name="ProgramCode">
<xs:simpleType>
<xs:pattern value="([0-8A-Z][0-9A-Z]|9[0-9A-Y])">
<xs:annotation>
<xs:documentation>2 alphanumeric, do not use
9Z</xs:documentation>
</xs:annotation>
</xs:pattern>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Month" type="xs:string">
<!-<xs:simpleType>
<xs:restriction base="xs:integer">
<xs:pattern value="(0?[1-9]|1[0-2])">
<xs:annotation>
<xs:documentation>01-12 or 1-12</xs:documentation>
</xs:annotation>
2 - B - 104
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:pattern>
</xs:restriction>
</xs:simpleType>
-->
</xs:element>
<xs:element name="Sortie" type="xs:string">
<!-<xs:simpleType>
<xs:minInclusive value="01"/>
<xs:pattern value="[0-9]{2}">
<xs:annotation>
<xs:documentation>Must be 2 digits, 01-99</xs:documentation>
</xs:annotation>
</xs:pattern>
</xs:restriction>
</xs:simpleType>
-->
</xs:element>
<xs:element name="Year">
<xs:simpleType>
<xs:pattern value="[0-9]{4}">
<xs:annotation>
<xs:documentation>4 digits, no explicit constraint
on range</xs:documentation>
</xs:annotation>
</xs:pattern>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="MissionIdentifierElement">
<xs:maxLength value="54"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="OverallClassificationElement">
<xs:attributeGroup ref="SecurityAttributesGroup"/>
</xs:complexType>
<xs:complexType name="ActdfMetadataElement">
<xs:sequence>
<xs:element name="OverallClassification">
<xs:annotation>
<xs:documentation>The Element is defined by XML DATA ENCODING
SPECIFICATION FOR INFORMATION SECURITY MARKING METADATA (ISM.XML). The IC ISM XML Schema may be
incorporated into organizational XML-based schemas by (a) declaring the IC ISM namespace and (b) inserting an "import" statement.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="OverallClassificationElement"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="TaskGenerationTimestamp" type="UTCDateTime" minOccurs="0"/>
<xs:element name="Originator" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:attributeGroup name="SecurityAttributesGroup">
<xs:annotation>
<xs:documentation xml:lang="en">
The group of Information Security Marking attributes in which the use of attributes 'classification' and 'ownerProducer' is required.
This group is to be contrasted with group 'SecurityAttributesOptionGroup' in which use of those attributes is optional.
</xs:documentation>
</xs:annotation>
<xs:attribute ref="classification" use="required"/>
<xs:attribute ref="ownerProducer" use="required"/>
<xs:attribute ref="SCIcontrols" use="optional"/>
<xs:attribute ref="SARIdentifier" use="optional"/>
<xs:attribute ref="atomicEnergyMarkings" use="optional"/>
2 - B - 105
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:attribute ref="disseminationControls" use="optional"/>
<xs:attribute ref="displayOnlyTo" use="optional"/>
<xs:attribute ref="FGIsourceOpen" use="optional"/>
<xs:attribute ref="FGIsourceProtected" use="optional"/>
<xs:attribute ref="releasableTo" use="optional"/>
<xs:attribute ref="nonICmarkings" use="optional"/>
<xs:attribute ref="classifiedBy" use="optional"/>
<xs:attribute ref="compilationReason" use="optional"/>
<xs:attribute ref="derivativelyClassifiedBy" use="optional"/>
<xs:attribute ref="classificationReason" use="optional"/>
<xs:attribute ref="nonUSControls" use="optional"/>
<xs:attribute ref="derivedFrom" use="optional"/>
<xs:attribute ref="declassDate" use="optional"/>
<xs:attribute ref="declassEvent" use="optional"/>
<xs:attribute ref="declassException" use="optional"/>
</xs:attributeGroup>
<xs:complexType name="MissionElement">
<xs:sequence>
<xs:choice>
<xs:element name="MissionNumber" type="MissionNumberElement"/>
<xs:element name="MissionIdentifier" type="MissionIdentifierElement"/>
</xs:choice>
<xs:element name="ProjectCode" minOccurs="0">
<xs:simpleType>
<xs:pattern value="([A-Y][A-Z]|Z[A-Y])">
<xs:annotation>
<xs:documentation>2 letter code, not
ZZ</xs:documentation>
</xs:annotation>
</xs:pattern>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PointTargetElement">
<xs:sequence>
<xs:element name="BENumber" minOccurs="0">
<xs:simpleType>
<xs:annotation>
<xs:documentation>Either 10 or 15 letters, numbers, and
symbols</xs:documentation>
</xs:annotation>
<xs:pattern value=".{10}(.{5})?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TargetName">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="TargetCategoryCode" type="xs:nonNegativeInteger" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="DsaTargetElement">
<xs:sequence>
<xs:element name="DSA_ID" minOccurs="0">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:simpleType>
2 - B - 106
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="LocTargetElement">
<xs:sequence>
<xs:element name="LOC_ID" minOccurs="0">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="TargetTypeElement">
<xs:choice>
<xs:element name="PointTarget" type="PointTargetElement"/>
<xs:element name="DSATarget" type="DsaTargetElement"/>
<xs:element name="LOCTarget" type="LocTargetElement"/>
</xs:choice>
</xs:complexType>
<xs:complexType name="SectorBlankingElement">
<xs:sequence>
<xs:element name="SectorBlankingID" type="xs:string" minOccurs="0"/>
<xs:element name="SectorBlankingName" type="xs:string"/>
</xs:sequence>
<xs:attribute name="override" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
<xs:complexType name="TargetDataElement">
<xs:sequence>
<xs:element name="TargetType" type="TargetTypeElement"/>
<xs:element name="SectorBlanking" type="SectorBlankingElement" minOccurs="0"
maxOccurs="unbounded"/>
<!-<xs:element name="CountryCode" type="CountryCodeElement" minOccurs="0"
maxOccurs="unbounded"/> -->
</xs:sequence>
</xs:complexType>
<xs:complexType name="TaskElement">
<xs:sequence>
<xs:element name="TaskPriority" minOccurs="0">
<xs:simpleType>
<xs:maxInclusive value="999"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="EEI_ID" type="EeiIdRefElement" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="TargetData" type="TargetDataElement"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="CollectionRequirementElement">
<xs:sequence>
<xs:element name="RequirementID">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RequirementName" minOccurs="0">
<xs:simpleType>
2 - B - 107
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RequestorID" minOccurs="0">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ControlDate_UTCDateTime" type="UTCDateTime"/>
<xs:element name="RequirementPriority" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Task" type="TaskElement" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ExploitationRequirementElement">
<xs:sequence>
<xs:element name="EEI_ID" type="EeiIdElement" minOccurs="0"/>
</xs:sequence>
</xs:complexType>



<xs:attribute name="classification" type="CVEnumISMClassificationAll"/>
<xs:attribute name="ownerProducer" type="CVEnumISMOwnerProducer"/>
<xs:attribute name="SCIcontrols" type="CVEnumISMSCIControls"/>
<xs:attribute name="SARIdentifier" type="CVEnumISMSAR"/>
<xs:attribute name="atomicEnergyMarkings" type="CVEnumISMatomicEnergyMarkings"/>
<xs:attribute name="disseminationControls" type="CVEnumISMDissem"/>
<xs:attribute name="displayOnlyTo" type="CVEnumISMRelTo"/>
<xs:attribute name="FGIsourceOpen" type="CVEnumISMFGIOpen"/>
<xs:attribute name="FGIsourceProtected" type="CVEnumISMFGIProtected"/>
<xs:attribute name="releasableTo" type="CVEnumISMRelTo"/>
<xs:attribute name="nonICmarkings" type="CVEnumISMNonIC"/>
<xs:attribute name="classifiedBy">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="compilationReason">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="derivativelyClassifiedBy">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="classificationReason">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="nonUSControls" type="CVEnumISMNonUSControls"/>
<xs:attribute name="derivedFrom">
<xs:simpleType>
2 - B - 108
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="declassDate">
<xs:simpleType>
<xs:restriction base="xs:date"/>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="declassEvent">
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="declassException" type="CVEnumISM25X"/>
<xs:simpleType name="CVEnumISMClassificationAll">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="CVEnumISMOwnerProducer">
<xs:restriction>
<xs:simpleType>
<xs:list itemType="xs:string"/>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMSCIControls">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMSAR">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMatomicEnergyMarkings">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMDissem">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMFGIOpen">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMFGIProtected">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
2 - B - 109
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMRelTo">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMNonIC">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISMNonUSControls">
<xs:restriction>
<xs:simpleType>
</xs:simpleType>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CVEnumISM25X">
</xs:simpleType>
<xs:element name="UAV">
<xs:annotation>
<xs:documentation>This defines the structure of the CRD custom intent tags</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="COLLECTION_INTENT" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:all>
<xs:element name="ID" type="ID_TYPE"/>
<xs:element name="PAYLOAD_LIST"
type="CONFIGURATION_ITEM" minOccurs="0"/>
<xs:element name="OPERATION_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration
value="SYS_PWR_OFF"/>
<xs:enumeration
value="SYS_PWR_ON"/>
<xs:enumeration
value="DEVICE_PWR_OFF"/>
<xs:enumeration
value="DEVICE_PWR_ON"/>
<xs:enumeration
value="INITIALIZE"/>
<xs:enumeration
value="STANDBY"/>
<xs:enumeration
value="ACTIVATE"/>
<xs:enumeration
value="CALIBRATE"/>
<xs:enumeration
value="CAGE"/>
<xs:enumeration
value="STOW"/>
<xs:enumeration
value="DEPLOY"/>
<xs:enumeration value=""/>
</xs:restriction>
</xs:simpleType>
2 - B - 110
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:element>
<xs:element name="PATTERN" type="PATTERN_TYPE"
minOccurs="0"/>
<xs:element name="PAYLOAD_SETTINGS"
type="PAYLOAD_SETTINGS_TYPE" minOccurs="0"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="COMMS_INTENT" type="COMMS_INTENT_TYPE" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element name="DISSEMINATION_INTENT" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:all>
<xs:element name="COMMS_SET_IN"
type="COMMS_INTENT_TYPE" minOccurs="0"/>
<xs:element name="COMMS_SET_OUT"
type="COMMS_INTENT_TYPE" minOccurs="0"/>
<xs:element name="INPUT_SOURCE"
<xs:element name="OUTPUT_DESTINATION"
<xs:element name="TIME_START" type="TIME_TYPE"
minOccurs="0"/>
<xs:element name="TIME_STOP" type="TIME_TYPE"
minOccurs="0"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="IFF_INTENT" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:all>
<xs:element name="MODE1_CODE" type="xs:short"
minOccurs="0"/>
<xs:element name="MODE1_ENABLE" type="xs:boolean"
minOccurs="0"/>
minOccurs="0"/>
minOccurs="0"/>
minOccurs="0"/>
<xs:element name="MODE3A_DURATION"
block="restriction" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension
base="xs:double">
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="seconds"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="MODE3A_ENABLE"
type="xs:boolean" minOccurs="0"/>
<xs:element name="MODE3A_IDENT" type="xs:boolean"
minOccurs="0"/>
<xs:element name="MODE4AB" type="xs:boolean"
minOccurs="0"/>
minOccurs="0"/>
<xs:element name="MODE4_HOLD" type="xs:boolean"
minOccurs="0"/>
<xs:element name="MODE4_ZEROIZE" type="xs:boolean"
minOccurs="0"/>
<xs:element name="MODEC_ENABLE" type="xs:boolean"
minOccurs="0"/>
<xs:element name="OPERATION_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration
value="OFF"/>
2 - B - 111
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:enumeration
value="STANDBY"/>
<xs:enumeration
value="NORMAL"/>
<xs:enumeration
value="EMERGENCY"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="LIGHTS_INTENT" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="mode" use="optional">
<xs:simpleType>
<xs:enumeration value="ON"/>
<xs:enumeration value="OFF"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type" use="optional">
<xs:simpleType>
<xs:enumeration value="NAV"/>
<xs:enumeration value="NAV_IR"/>
<xs:enumeration value="STROBE"/>
<xs:enumeration
value="STROBE_IR"/>
<xs:enumeration value="LANDING"/>
<xs:enumeration value="NVD"/>
<xs:enumeration
value="LANDING_IR"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="EMERGENCY_INTENT" minOccurs="0">
<xs:complexType>
<xs:all>
<xs:element
name="EMERGENCY_RECOVERY_SETTINGS" minOccurs="0">
<xs:simpleType>
<xs:enumeration
value="PWR_OFF"/>
<xs:enumeration
value="PWR_ON"/>
<xs:enumeration
value="ARM"/>
<xs:enumeration
value="DISARM"/>
<xs:enumeration
value="ACTIVATE"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="EMERGENCY_ROUTE_ENTRY_ID"
type="xs:ID"/>
<xs:element name="EMERGENCY_ROUTE_ID"
type="xs:ID"/>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="LOITER_INTENT" minOccurs="0">
<xs:complexType>
<xs:all>
<xs:element name="LOITER_TYPE" minOccurs="0">
<xs:simpleType>
2 - B - 112
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:enumeration
value="CIRCLE"/>
<xs:enumeration
value="FAA_HOLD"/>
<xs:enumeration
value="FIGURE_8"/>
<xs:enumeration
value="RACETRACK"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="LOITER_WIDTH" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension
base="xs:double">
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="FEET"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="REQ_LOOPS" type="xs:short"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="PAYLOAD_SETTINGS_TYPE">
<xs:annotation>
<xs:documentation>The type for payload settings</xs:documentation>
</xs:annotation>
<xs:all>
<xs:element name="SCENE_NUMBER" type="xs:double" minOccurs="0"/>
<xs:element name="RADAR_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="LOW_RES"/>
<xs:enumeration value="MED_RES"/>
<xs:enumeration value="HIGH_RES"/>
<xs:enumeration value="SAR_POLAR"/>
<xs:enumeration value="SAR_POINT"/>
<xs:enumeration value="SAR_STRIP"/>
<xs:enumeration value="GMTI_ARC"/>
<xs:enumeration value="GMTI_SPOT"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="RECORDING_INDEX" type="xs:double" minOccurs="0"/>
<xs:element name="POLARITY" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="WHITE"/>
<xs:enumeration value="BLACK"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="POINTER_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="NONE"/>
<xs:enumeration value="ANGLE_AV"/>
<xs:enumeration value="SLEW_AV"/>
<xs:enumeration value="SLEW_INERTIAL"/>
<xs:enumeration value="POSITION_SLAVED"/>
<xs:enumeration value="TARGET_SLAVED"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="PAYLOAD_MODE" minOccurs="0">
<xs:simpleType>
2 - B - 113
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:enumeration value="BW"/>
<xs:enumeration value="COLOR"/>
<xs:enumeration value="CLUTTER"/>
<xs:enumeration value="MTI"/>
<xs:enumeration value="REC_GOTO"/>
<xs:enumeration value="REC_RECORD"/>
<xs:enumeration value="REC_SEEK"/>
<xs:enumeration value="REC_PLAY"/>
<xs:enumeration value="REC_REWIND"/>
<xs:enumeration value="REC_PAUSE"/>
<xs:enumeration value="REC_STOP"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="OUTPUT" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="NONE"/>
<xs:enumeration value="EO"/>
<xs:enumeration value="IR"/>
<xs:enumeration value="BOTH"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="FOV_VER" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:restriction base="ANGLE_TYPE">
<xs:totalDigits value="5"/>
<xs:fractionDigits value="2"/>
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="FOV_HOR" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="COMPRESSION_TYPE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="VIDEO_HUFF"/>
<xs:enumeration value="VIDEO_QUANT"/>
<xs:enumeration value="SAR_HUFF"/>
<xs:enumeration value="SAR_QUANT"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="COMPRESSION_RATIO" type="xs:short" minOccurs="0"/>
<xs:element name="ANGLE_ELEV" block="restriction" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ANGLE_AZ" block="#all" minOccurs="0">
2 - B - 114
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:complexType>
<xs:simpleContent>
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="PAYLOAD_OPERATING_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="SYS_PWR_OFF"/>
<xs:enumeration value="SYS_PWR_ON"/>
<xs:enumeration value="DEVICE_PWR_ON"/>
<xs:enumeration value="DEVICE_PWR_OFF"/>
<xs:enumeration value="INITIALIZE"/>
<xs:enumeration value="STANDBY"/>
<xs:enumeration value="ACTIVATE"/>
<xs:enumeration value="CALIBRATE"/>
<xs:enumeration value="CAGE"/>
<xs:enumeration value="STOW"/>
<xs:enumeration value="DEPLOY"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="GMTI_SETTINGS" minOccurs="0">
<xs:complexType>
<xs:all>
<xs:element name="BAR_END" type="xs:short" minOccurs="0"/>
<xs:element name="BAR_START" type="xs:short" minOccurs="0"/>
<xs:element name="MAX_TARGETS" type="xs:short"
minOccurs="0"/>
<xs:element name="MIN_DETECTABLE_VELOCITY"
minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:double">
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="feet/second"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="MIN_SNR" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="dB"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="MIN_TARGET_RCS" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="dBsf"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="RANGE_RESOLUTION" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="feet"/>
</xs:extension>
2 - B - 115
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="SLANT_RANGE" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="SAR_SETTINGS" minOccurs="0">
<xs:complexType>
<xs:all>
<xs:element name="RANGE" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="RESOLUTION" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute
name="UNITS" type="UNITS_TYPE" fixed="inches"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
<xs:element name="ANGLE_REL">
<xs:simpleType>
<xs:enumeration value="NORTH"/>
<xs:enumeration value="BODY"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:all>
</xs:complexType>
<xs:complexType name="PATTERN_TYPE">
<xs:annotation>
<xs:documentation>The type for pattern tags</xs:documentation>
</xs:annotation>
<xs:all>
<xs:element name="ALONG_TRACK" type="xs:short" minOccurs="0"/>
<xs:element name="ALTITUDE" type="ALTITUDE_TYPE" minOccurs="0"/>
<xs:element name="CROSS_TRACK" type="xs:short" minOccurs="0"/>
<xs:element name="PATTERN_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="RASTER_SENS"/>
<xs:enumeration value="RASTER_UAV"/>
<xs:enumeration value="SPOT_SENS"/>
<xs:enumeration value="SPOT_UAV"/>
<xs:enumeration value="TARGET_SENS"/>
<xs:enumeration value="TARGET_UAV"/>
<xs:enumeration value="WAS_SENS"/>
<xs:enumeration value="WAS_UAV"/>
</xs:restriction>
</xs:simpleType>
2 - B - 116
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
</xs:element>
<xs:element name="PATTERN_START" type="xs:double" minOccurs="0"/>
<xs:element name="PATTERN_TIME" type="xs:double" minOccurs="0"/>
<xs:element name="PATTERN_TYPE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="POINT"/>
<xs:enumeration value="LINE"/>
<xs:enumeration value="TRACK_FOLLOW"/>
<xs:enumeration value="SPIRAL"/>
<xs:enumeration value="SPIRAL_REC"/>
<xs:enumeration value="CIRCLE"/>
<xs:enumeration value="RACETRACK"/>
<xs:enumeration value="QUADRILATERAL"/>
<xs:enumeration value="POLYGON"/>
<xs:enumeration value="FIGURE_8"/>
<xs:enumeration value="OWNTRACK"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="REF_1" type="WGS84_POSITION_TYPE" minOccurs="0"/>
<xs:element name="SPEED" type="AIRSPEED_TYPE" minOccurs="0"/>
<xs:element name="TARGET" type="WGS84_POSITION_TYPE" minOccurs="0"/>
<xs:element name="TRACK_SPACING" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:short">
<xs:attribute name="UNITS" type="UNITS_TYPE"
fixed="feet"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="TARGET_ELEV" minOccurs="0">
<xs:complexType>
<xs:all>
<xs:element name="ELEVATION_VALUE"
type="ELEVATION_VALUE_TYPE" minOccurs="0"/>
<xs:element name="ELEVATION_SOURCE"
type="ELEVATION_SOURCE_TYPE" minOccurs="0"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>
<xs:complexType name="COMMS_INTENT_TYPE">
<xs:annotation>
<xs:documentation>The type for communications settings</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ANTENNA_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="STOW"/>
<xs:enumeration value="DIRECTIONAL"/>
<xs:enumeration value="OMNI"/>
<xs:enumeration value="AUTO"/>
<xs:enumeration value="POINT_TO_RECEIVER"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="COMMS_LIST" type="CONFIGURATION_ITEM" minOccurs="0"/>
<xs:element name="COMMS_MODE" minOccurs="0">
<xs:simpleType>
<xs:enumeration value="SYS_PWR_OFF"/>
<xs:enumeration value="SYS_PWR_ON"/>
<xs:enumeration value="DEVICE_PWR_OFF"/>
2 - B - 117
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:enumeration value="DEVICE_PWR_ON"/>
<xs:enumeration value="INITIALIZE"/>
<xs:enumeration value="STANDBY"/>
<xs:enumeration value="RX_TX"/>
<xs:enumeration value="RX"/>
<xs:enumeration value="TX"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="COMMS_SECURITY" type="xs:boolean" minOccurs="0"/>
<xs:element name="DATA_RATE" type="xs:double" minOccurs="0"/>
<xs:element name="FREQ_RECEIVE" type="xs:double" minOccurs="0"/>
<xs:element name="FREQ_TRANSMIT" type="xs:double" minOccurs="0"/>
<xs:element name="POWER_TRANSMIT" type="PERCENT_TYPE" minOccurs="0"/>
<xs:element name="RECEIVER_ALTITUDE" type="ALTITUDE_TYPE" minOccurs="0"/>
<xs:element name="RECEIVER_LOCATION" type="WGS84_POSITION_TYPE" minOccurs="0"/>
<xs:element name="RETRANSMIT" type="xs:short" minOccurs="0"/>
<xs:element name="SLOT_RECEIVE" type="xs:short" minOccurs="0"/>
<xs:element name="SLOT_TRANSMIT" type="xs:short" minOccurs="0"/>
<xs:element name="TIME_OUT" block="restriction" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="UNITS" type="UNITS_TYPE"
fixed="seconds"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ANGLE_TYPE">
<xs:annotation>
<xs:documentation>The type for angle settings</xs:documentation>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:decimal">
<xs:attribute name="UNITS" type="UNITS_TYPE" fixed="degrees"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="PERCENT_TYPE">
<xs:annotation>
<xs:documentation>The type to set percentages</xs:documentation>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:decimal">
<xs:attribute name="UNITS" type="UNITS_TYPE" fixed="percent"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="ID_TYPE">
<xs:annotation>
<xs:documentation>Defined in core CRD listing</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="CONFIGURATION_ITEM">
<xs:annotation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="ALTITUDE_TYPE">
<xs:annotation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="WGS84_POSITION_TYPE">
<xs:annotation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="AIRSPEED_TYPE">
2 - B - 118
APPENDIX 2 to
ANNEX B to
STANAG 4586
Edition 3
<xs:annotation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="TIME_TYPE">
<xs:annotation>
</xs:annotation>
<xs:attribute name="UNITS" type="UNITS_TYPE" fixed="seconds"/>
</xs:complexType>
<xs:simpleType name="UNITS_TYPE">
<xs:annotation>
<xs:documentation>Defined in Core CRD listing</xs:documentation>
</xs:annotation>
</xs:simpleType>
<xs:simpleType name="String35">
<xs:annotation>
<xs:documentation>Defined in core ATCM</xs:documentation>
</xs:annotation>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="UTCDateTime">
<xs:annotation>
<xs:documentation>Standard XML dateTime, except required to explicitly have "Z" zulu specifier at
end.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:dateTime">
<xs:pattern value=".*Z"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ELEVATION_VALUE_TYPE">
<xs:annotation>
<xs:documentation>Defined in core CRD</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:simpleType name="ELEVATION_SOURCE_TYPE">
<xs:annotation>
<xs:documentation>Defined in core CRD</xs:documentation>
</xs:annotation>
</xs:simpleType>
</xs:schema>
2 - B - 119
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
APPENDIX B3 HUMAN COMPUTER INTERFACE
TABLE OF CONTENTS
1 INTRODUCTION. .............................................................................................................. 3
1.1 Scope. ...................................................................................................................... 3
2.1 General Requirements............................................................................................ 5
2.2 UCS Configuration.................................................................................................. 5
2.3 Mission Planning. ................................................................................................... 5
2.4 Air Vehicle Control.................................................................................................. 5
2.5 Operator Control and Monitoring. ......................................................................... 6
2.6 Payload Control and Monitoring. .......................................................................... 6
2.7 Warnings, Cautions, and Advisories. ................................................................... 6
2.8 Communications Management.............................................................................. 6
3-B-1
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
LIST OF FIGURES
Figure B3 - 1. UCS Functional Architecture ................................................................ 3
3-B-2
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
1 Introduction.
1.1 Scope.
NATO Standardisation Agreement (STANAG 4586) Annex B Appendix B3 specifies the

Human Computer Interface (HCI) requirements that a CUCS shall support for various levels
of interoperability. As illustrated in Figure B3-1, the HCI is an integral element of the CUCS.
STANAG 4586 Annex B Appendix B3 specifies requirements which will contribute to UAV
interoperability.
The HCI requirements should facilitate seamless integration of NATO UAV systems into joint
combined NATO battlefield infrastructures across the five Levels of Interoperability (LOI).
The HCI Appendix B3 establishes the general requirements for information to be displayed
by the UCS. The requirements detail the functions and interactions that the UCS shall allow
the operator to perform.
Annex B Appendix B3 specifies the requirements levied upon the UCS, and does not impose
any requirements on Human Factors (HF) and ergonomics.
The HCI complies with the NATO Interoperability Standards and Profiles (NISP).
AV
LAUNCH &
RECOVERY
SYSTEM
UCS
VSM
DLI
CCI
HCI
CORE
UCS
OPERATOR
CCI
CCISM
C4I
SYSTEM
C4I
SYSTEM
Figure B3 - 1. UCS Functional Architecture
Although portions of the HCI will have a physical implementation within a CUCS, Annex B
Appendix B3 does not impose any design requirements. This means that there are No
Restrictions to size, form or components used in an HCI implementation. The reader is
referred to the STANAG 4586 Implementation Document for recommended methods to
incorporate HCI functional requirements, but some examples follow. Example 1: a HCI may
3-B-3
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
be a dual workstation in a shelter offering a high degree of functionality required by a High
Altitude Long Endurance (HALE) UAV, whereas a small portable unit (hand-held computer)
used to operate a Micro Air Vehicle (MAV) would also be considered a HCI implementation.
Example 2: for a maritime UCS, there may be a HCI providing LOI 5 functionality, while
lower levels of functionality (LOI 1 or 2) could be required on other parts of the vehicle, which
may require a different HCI.
Within this appendix, the applicable LOI have been identified for all requirements (both
mandatory shall and recommended should statements). This has the effect of clearly
identifying what requirements the CUCS should be compliant with in order to enable the
required LOI.
3-B-4
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
2 Functional Requirements.
This section provides a set of mandatory requirements and recommendations for the HCI to
allow user interoperability between NATO Nations UAV assets. These are categorised
under the following headings:
2.1 General Requirements
2.2 UCS Configuration
2.3 Mission Planning
2.4 Air Vehicle Control
2.5 Operator Control and Monitoring
2.6 Payload Control and Monitoring
2.7 Warnings, Cautions, and Advisories
2.8 Communications Management
Following the functional requirements statements, the applicable LOIs are presented.
In the following sections a 'qualified operator' is a system operator who has been determined
by the operational system user, e.g. US Air Force, to be qualified to perform the specified
function. Since this is an operational requirement it will not/can not be tested/verified by the
acquisition/development organization and does not have to be validated as part of the
component and system test.
2.1 General Requirements.
The operator shall have the ability to enter and synchronise a time with the UAV System and
applicable C4I systems. This applies to LOIs 1, 2, 3, 4, and 5.
2.2 UCS Configuration.
The HCI shall provide the operator with the ability to generate, receive, display, edit, and
send message types that have been defined in the STANAG 4586 as applicable to required
LOI. This applies to LOIs 1, 2, 3, 4, and 5.
The operator shall be able to globally change the measurement units (e.g., change from
imperial units to metric, or Latitude/Longitude to Universal Transverse Mercator (UTM) or
Military Grid Reference System (MGRS)). This applies to LOIs 1, 2, 3, 4, and 5.
2.3 Mission Planning.
Mission Planning includes all planning aspects of all phases of the mission contained in the
ATO (e.g., pre-flight and in-flight for AV, payload, data link and communications.) For
CUCSs, which have the capability to generate mission plan(s), the HCI shall enable a
qualified operator to create, edit, and save a mission plan(s). For mission plans developed
external to the CUCS, the HCI shall enable a qualified operator to import, view, and save a
mission plan. This applies to LOIs 3, 4, and 5.
The HCI shall enable a qualified operator to update (without uploading) a current mission
plan at any time before or during flight. This applies to LOIs, 3, 4, and 5.
The HCI shall provide a qualified operator with the ability to upload mission plans to the AV.
This applies to LOIs 3, 4 and 5.
2.4 Air Vehicle Control.
The HCI shall provide controls and displays for controlling/monitoring the air vehicle in all
supported flight modes. This applies to LOIs 4 & 5.
The operator shall have the ability to pass AV control (handover) to another UCS with a
qualified operator(s) and monitor the status of the handover as per the mechanisms defined
in Appendix B1 (DLI). This applies to LOIs 4 and 5.
3-B-5
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
2.5 Operator Control and Monitoring.
The HCI shall provide an image display to allow the operator to view image files from
external C4I sources. This applies to LOI 1, 2 and 3.
2.6 Payload Control and Monitoring.
The Payload Control HCI functions defined within the CUCS will be generic to types of
payload, rather than specific payloads, where possible. The payload types are:
Imaging Sensors (Passive) (including visible and infrared wavebands,
hyperspectral, and multispectral sensors)
Imaging Sensors (Radar/Active Sensors) (including Airborne Radar, Synthetic
Aperture Radar (SAR) and Moving Target Indicator (MTI))
Laser Based Payloads (e.g., Laser Range Finders, Laser Target Designators)
Communications Relay (CR)
Stores (Dispensing) payloads (to include weapons, humanitarian aid,
unattended ground sensors, buoys)
The HCI shall provide sufficient controls and displays to control payloads and all associated
functions for only those payloads that have been validated with the current CUCS. This
applies to LOI 3.
The HCI shall provide sufficient controls and displays to monitor payloads and all associated
functions for only those payloads that have been validated with the current CUCS. This
applies to LOI 2 and 3.
A qualified operator shall have the ability to pass and receive control (handover) of the AV's
payload to/from another control system and monitor the payload control via the mechanisms
defined in Appendix B1 (DLI). This applies to LOI 3.
For payloads that generate motion imagery, the operator shall have a motion imagery
display. This applies to LOIs 2 and 3.
Stores (dispensing) payloads are considered to be those that are released from the UAV as
part of the UAV mission objectives. This can include the release of weapons or deployment
of remote sensors, etc. The release mechanism for the payload shall be clearly identified
and labelled to the operator. This applies to LOI 3.
A safety interlock shall operate such that the operator cannot inadvertently release the
payload. This applies to LOI 3.
For multiple-shot dispensing payloads, the number of uses remaining shall be indicated to
the operator. This applies to LOIs 2 and 3.
2.7 Warnings, Cautions, and Advisories.
Warnings, cautions, and advisories inform the operator about any unusual or critical
condition. The HCI shall provide the capability to display and manage warnings, cautions,
and advisories as defined in Annex B of STANAG 4586. This applies to LOIs 2, 3, 4, and 5.
2.8 Communications Management.
Communications Management controls the communications links between the UCS and the
UAV. This would include any additional antennas or data links required to support a specific
payload (e.g., a CR payload). It provides the operator at the CUCS with the ability to
configure the data links and to change a number of parameters of the VDT and the CDT.
Whilst the majority of data link parameters will be controlled from the CUCS, some more
specific data link functions will need to be controlled through the DLI. Refer to Appendix B1:
Data Link Interface for further details.
3-B-6
APPENDIX 3 to
ANNEX B to
STANAG 4586
Edition 3
The HCI shall provide the operator with the ability to open and control the communications
links between the CUCS and other outside agencies such as:
C4I systems via the CCI interface
Air traffic control via both voice and data links
VDT/CDT
This applies to LOIs 1, 2, 3, 4, and 5.
The CUCS shall provide an antenna/data link status display. This display does not
necessarily have to be separate from the AV control/monitor display. This applies to LOIs 2,
3, 4, and 5.
3-B-7

4586 Eed 03

Uploaded by

Copyright:

Available Formats

4586 Eed 03

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4586 Eed 03

Uploaded by

Copyright:

Available Formats

RECORD OF AMENDMENTS

A. TERMS AND DEFINITIONS

Annex A contains the Terms and Definitions used in the STANAG.

The following acronyms are used for the

Army Command and Control System (US)/Air Command and

Common Data Link

Image Print Services

Air Vehicle (AV)

An alert that requires crew awareness but not immediate

Core UCS (CUCS)

Data Link Plan

Near Real Time

AIR VEHICLE ELEMENT

UAV SURFACE COMPONENT

Figure B - 1. UAV System Elements

CURRENT NATO/NATIONAL C4I NODES

Figure B - 2. Current UAS Operations Example

A UAS as defined above may be composed of various components which include; a

Indirect receipt and/or transmission of sensor product and associated

Direct receipt of sensor product data and associated metadata from

Control and monitoring of the UAV payload unless specified as

Control and monitoring of the UAV, unless specified as monitor only,

Control and monitoring of UAV launch and recovery unless specified

AIR VEHICLE ELEMENT

DATA LINK ELEMENT

Figure B - 3. UAS Interoperability Architecture

Keys concepts to remember are:

Figure B - 4. UCS Functional Architecture

Digital Geographic Information Exchange Standard (DIGEST),

4.1.1.2 Communication Services.

To enhance UAV interoperability and flexibility, it is recommended that the UCS

Section 2 System Functional Requirements By Mission Phase

Section 3 Message Distribution Standard

Section 4 Message Formats

Section 5 Miscellaneous Interfaces

Figure B1 - 1: DLI Role in the AV/UCS Concept

Figure B1 - 2: DLI Role in the CDT/UCS Concept

Figure B1 - 3: Role of the VSM

Analogue Sensor Data (under

A/V Telemetry and Digital Sensor Data

A/V, Data link, Payload, and VSM Status

A/V & Payload Mode/Control

Data Link Interface

Figure B1 - 4: High-Level Depiction of DLI Interface Content

Multiple Activities (Activity ID 0)

Single Constraints Complete Messages 36002

Multiple Activity Complete Messages 36100

Figure B1 - 5: Autonomy Message Flow

Figure B1 - 6: Typical Scenario for Generating Vehicle-Specific Displays

Table B1 - 1: Owning ID Table

Interoperable Mission Planning

Local ATC Communications.

Ground Traffic Pattern/Plan Execution.

Mission Execution Monitoring.

UAV Vehicle-Specific Handover Data

Prime Mission Area

Generic Payload Control.

Detailed System Status Monitoring.