# Missions and Organization

Note on Command and Control Section

While the information presented in the **Mission and Organization** section is undoubtedly intriguing, it's important to acknowledge that the content is considerably dense, extensive, and somewhat repetitive. 

The nature of which does not align well with the operational dynamics and requirements of a DCS squadron, necessitating a tailored approach to ensure relevance and applicability.

***

\
The attack reconnaissance battalion (ARB) and attack reconnaissance squadron (ARS) are organized and equipped to support joint, interagency, multinational and Army operations. These units conduct continuous combat operations throughout the depth and breadth of the operational environment. Although their organization and missions differ by parent division, their principal focus is similar. Each unit focuses on time-tested fundamentals to achieve success. This chapter discusses these fundamentals and outlines basic organization, principal mission focus, and capabilities of the ARB. The organization description for each unit is based on the official table of organization and equipment (TOE). Operationally, all units are resourced according to the modified table of organization and equipment (MTOE), so actual organizations may look different from the TOEs described in this FM

{% hint style="info" %}
Throughout this manual, for readability, the term company includes troop, and battalion includes squadron. The terms troop and squadron may be used when specifically discussing air cavalry squadrons (ACSs) or their respective subordinate units.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://229.gitbook.io/229-hub/knowledge/attack-reconnaissance-helicopter-operations/missions-and-organization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.