> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/gov/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltaquad.com/gov/abbreviations.md).

# Abbreviations

On this page, all abbreviations used throughout this manual and their full forms can be found.

<table data-header-hidden><thead><tr><th width="191"></th><th></th></tr></thead><tbody><tr><td>ADS-B</td><td>Automatic Dependent Surveillance–Broadcast</td></tr><tr><td>AGL</td><td>Above Ground Level (Altitude Above Ground Level)</td></tr><tr><td>AMC</td><td>Auterion Mission Control</td></tr><tr><td>APDS</td><td>Aerial Payload Deployment System</td></tr><tr><td>AS</td><td>Air Speed</td></tr><tr><td>ATAK</td><td>Android Team Awareness Kit</td></tr><tr><td>BLOS</td><td>Beyond Line of Sight</td></tr><tr><td>BVLOS</td><td>Beyond Visual Line of Sight</td></tr><tr><td>CG</td><td>Center of Gravity</td></tr><tr><td>EO</td><td>Electro-Optical (Visible Light)</td></tr><tr><td>FW</td><td>Fixed-wing</td></tr><tr><td>GCS</td><td>Ground Control Station</td></tr><tr><td>GOV</td><td>Government</td></tr><tr><td>GPS</td><td>Global Positioning System</td></tr><tr><td>GS</td><td>Ground Speed/Horizontal Speed</td></tr><tr><td>GUI</td><td>Graphical User Interface</td></tr><tr><td>HGT</td><td>Height (Heights are referenced to the takeoff location)</td></tr><tr><td>IMU</td><td>Inertial Measurement Units</td></tr><tr><td>I/O board</td><td>Input/Output board</td></tr><tr><td>IR</td><td>Infra-Red</td></tr><tr><td>ISR</td><td>Intelligence, Surveillance, and Reconnaissance</td></tr><tr><td>LAT</td><td>Latitude</td></tr><tr><td>LED</td><td>Light-Emitting Diode</td></tr><tr><td>LI-ION</td><td>Lithium-ion</td></tr><tr><td>LON</td><td>Longitude</td></tr><tr><td>LOS</td><td>Line of Sight</td></tr><tr><td>MGRS</td><td>Military Grid Reference System</td></tr><tr><td>MR</td><td>Multirotor</td></tr><tr><td>MSL</td><td>Mean Sea Level (Altitude Above Mean Sea Level)</td></tr><tr><td>OLED</td><td>Organic Light-Emitting Diode</td></tr><tr><td>POI</td><td>Point of Interest</td></tr><tr><td>RC</td><td>Radio Control</td></tr><tr><td>RF</td><td>Radio Frequency</td></tr><tr><td>SR</td><td>Slant Range (Direct Distance)</td></tr><tr><td>UAV</td><td>Unmanned Aerial Vehicle</td></tr><tr><td>USB</td><td>Universal Serial Bus</td></tr><tr><td>VLOS</td><td>Visual Line of Sight</td></tr><tr><td>VS</td><td>Vertical Speed</td></tr><tr><td>VTOL</td><td>Vertical Take-off and Landing</td></tr><tr><td>XT(90)</td><td>Extreme</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.deltaquad.com/gov/abbreviations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
