This guide helps you get useful results quickly without touching advanced settings first.
In about 15 minutes, you will learn how to:
- read the main AO layout
- search and select a live aircraft
- inspect core flight fields
- measure distance with the range tool
- react to page suggestions by altitude context
Before you start
- Open AO in desktop browser at
https://anobservatory.com. - Use the default light theme for this walkthrough.
- Keep data source on
ADS-B Exchangefor consistency.
Step 1. Understand the main layout
Use this as your orientation point before interacting with traffic.

Focus on three areas:
- map canvas (center)
- toolbox and side panels (left/right)
- context menus and status overlays
Step 2. Search for an aircraft
Open the search panel, switch to Aircraft mode, and enter a callsign or identifier.

Then click one result to center and select that aircraft.

Step 3. Read flight info fields
With one aircraft selected, open the flight info section and read these first:
- callsign
- altitude trend
- groundspeed
- heading / track

Tip: do not interpret a single value in isolation. Watch short trend changes for better context.
Step 4. Use the range tool
Enable Range Calculator and place points to measure practical distances.

Use this for quick sanity checks such as relative spacing and rough travel distance.
Step 5. Follow page suggestion logic
If a selected aircraft altitude fits another control context, AO can suggest page switching.

Use this as an operational hint, not a hard rule. Keep your current page when your immediate task requires it.
Optional tuning: target preference
After the basic flow is comfortable, tune target behavior.


Recommended starting point:
- keep smoothing moderate
- avoid aggressive filter changes initially
- change one option at a time and re-check behavior
Optional view aid: gridlines
Gridlines can help with quick visual positioning depending on your task.
Gridlines ON

Gridlines OFF

Common mistakes
- Using too many toggles before learning base behavior
- Judging traffic state from one snapshot instead of short trends
- Forgetting to confirm selected target before measuring range
Next step
After this quickstart: