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

# Using the map

The [map](https://wingbits.com/map) shows live aircraft tracked by the Wingbits network. When logged in, you can also open it from "Map" on the dashboard.

### Find a flight or place

Click the magnifying glass and search by callsign, registration, hex or address. Click a result to jump to it.

### Find your stations

Click the person icon (only shown when logged in) to see your stations. Click one to jump to it. "Show my coverage" draws your total coverage on the map.

To see all stations, turn on "Wingbits stations" under "Layers". Yours are orange and everyone else's are blue. Click a station to see its 7 day earnings, or "Show coverage" to draw its coverage area.

### Look at an aircraft

Click any aircraft to open its details. The buttons at the top let you:

* "Pin" it to a comparison list (or hold Ctrl, Cmd on Mac, while clicking another aircraft)
* "Share flight" to copy a link to it
* "Track flight" so the map follows it
* "Replay flight" to replay its recent path

The tabs show the flight's route and times ("Overview"), cockpit instruments and altitude chart ("Cockpit"), the full ADS-B readout ("Technical") and its past flights for up to 45 days ("History"). Click a past flight to replay it.

### Change what you see

* "Layers" switches between the map and satellite views, 2D, 3D or globe, and turns on layers like weather radar and emergency squawks. Click "Customize" to add up to 5 layers to the toolbar as shortcuts.
* "Preferences" (the sliders icon) colors aircraft by altitude or type, and filters by altitude range, aircraft type or military only. A dot on the button means a filter is on.


---

# 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.wingbits.com/general-help/using-the-map.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.
