Air Tasking Order (ATO) Basics DCS AOC Tools
Last updated: Aug 21, 2026

ATO Basics in AOC Tools for DCS World

The Air Tasking Order (ATO) is the central operational planning structure in AOC Tools, the mission planning and Air Operations Center platform within the Combined Ops suite for DCS World. The ATO organizes missions, Task Units, packages, timings, and operational information into a structured order that can be used to plan and coordinate complex DCS World air operations.

An ATO in AOC Tools is built around several interconnected elements. The ATO Header establishes the operational context, while Task Units, Missions, and Packages organize the forces and activities assigned to the operation.

Main ATO Elements

ATO Header: Defining the Operation

The ATO Header defines the general, administrative, and timing parameters of the Air Tasking Order. It provides the operational context for the missions contained in the ATO and is the foundational step required before the other ATO planning sections can be fully configured.

The Header is accessed through the Header section of the project navigation.

INFO

• Real Date: The real-world date associated with the ATO. When available, this value is initially derived from the project's DCS World .miz mission file.
• Real Time (UTC, Z): The real-world UTC time associated with the ATO. When available, this value is initially derived from the project's .miz mission file.

OPER/EXER

This section identifies whether the ATO represents an exercise or an operational scenario.

• ATO Type: Defines the type of ATO.
  • EXER: Used for exercise scenarios.
  • OPER: Used for operational scenarios.
  Selecting the ATO type determines which corresponding identification field is displayed.
• Exercise Name: Available when the ATO Type is EXER and identifies the exercise.
• Operation Name: Available when the ATO Type is OPER and identifies the operation.

MSGID

The MSGID section defines the identification information for the ATO message.

• Originator: Identifies the organization, command, or entity originating the ATO.
• Message Serial Number: Provides the serial number used to identify the ATO message.
• Qualifier: Defines the status of the ATO message.
  • New: Identifies a new ATO.
  • Change (CHG): Identifies an amendment or change to a previously issued ATO.
• Qualifier Serial Number: When Change (CHG) is selected, this field identifies the serial number of the previous ATO message being amended.

TIMEFRAM (UTC, Z or Local, J)

The TIMEFRAM section defines the period during which the ATO is valid. The time reference used by the ATO follows the Project Time Zone configured in the project properties.

• Time From (date): Defines the starting date of the ATO validity period.
• Time From (time): Defines the starting time of the ATO validity period.
• Time To (date): Defines the ending date of the ATO validity period.
• Time To (time): Defines the ending time of the ATO validity period.
• ASOF: As of Time (date): Defines the date associated with the ATO's effective status.
• ASOF: As of Time (time): Defines the time associated with the ATO's effective status.

Note: The project time reference can be configured as Z (UTC) or J (Local Time/Sim Time) in the project properties.

AMPN/NARR

• AMPN: Provides amplifying information or additional explanations related to the ATO.
• NARR: Provides narrative information and additional operational context for the ATO.

After entering the required information, click Save to create or update the ATO Header. The ATO Header is a prerequisite for configuring the subsequent ATO planning sections, including Missions, Task Units, and Packages.

Task Units

Task Units are a fundamental organizational element of the ATO. They represent the units or formations to which missions are assigned and provide the organizational structure required to build the operational order of battle.

• Mission Assignment: Missions are assigned to a specific Task Unit, allowing AOC Tools to associate each mission with its responsible unit.
• Airbase Reference: A Task Unit can be associated with an ICAO code or location name representing its operating or home base.
• Flight Timing: The airbase reference is important for flight timing calculations, including the calculation and display of takeoff-related information.
• Mission Filtering: Correct Task Unit and airbase information also supports the filtering and organization of missions within AOC Tools.

For detailed information about creating and managing Task Units, including their configuration and the importance of the associated ICAO code, see the Task Units Guide.

Missions

Missions define the individual air missions that make up the ATO. A mission can contain operational information such as mission number, callsign, aircraft type, task, timing, and assigned Task Unit.

In AOC Tools, missions form the operational core of the ATO. They can be organized into Task Units and combined into Packages when multiple missions are required to achieve a common operational objective.

Packages

Packages group related missions that are planned to operate together as part of the same operational activity. A package can contain different mission types and supporting elements that contribute to a common objective.

Using Packages provides a higher-level organizational structure for complex DCS World operations involving multiple aircraft formations and mission types.

Remarks

Remarks provide additional information associated with units or missions. They can be used to communicate specific operational details, restrictions, coordination requirements, or other information that does not fit into the primary mission fields.

Additional ATO Planning Elements

Depending on the project configuration, the ATO can be supported by additional operational planning sections within AOC Tools:

• Comm Plan: Defines radio communications, frequencies, callsigns, and related communication information.
• SPINS (Special Instructions): Provides special instructions and operational procedures applicable to the mission or operation.
• Assignments: Associates personnel with missions and operational roles such as pilots, ATC, and AWACS.
• Airspace Control Order (ACO): Defines and manages airspace control measures associated with the operation.

ATO Workflow in AOC Tools

A practical ATO workflow starts with the ATO Header and then progressively builds the operational structure:

1. Configure the ATO Header: Define the operation, message identification, validity timeframe, and supporting information.
2. Create Task Units: Organize the participating units and configure their associated airbase information.
3. Create Missions: Define the individual missions and assign them to Task Units.
4. Organize Packages: Group related missions when required for coordinated operations.
5. Configure supporting information: Complete communications, special instructions, assignments, airspace control, and other operational data as required.

Once configured, these elements provide a structured Air Tasking Order for DCS World operations, allowing virtual squadrons and flight groups to organize complex missions using the same fundamental concepts of operational tasking, unit organization, mission assignment, and coordination.