1

@callsign

Call a host who is on the air to start a QSO. Follow the chase with a position report within 5 minutes, and the OTA bot relays your call and grid square to the host.

@<callsign> [message...]

Call a host on the air to start a QSO.

callsign
The host to chase. Any SSID form of their callsign works.
message
Free text relayed to the host along with your grid square. optional
Available to
Anyone, from RF or APRS-IS.
Rate limit
2 per minute and 5 per 10 minutes

Replies

beacon_prompt
Send a position report within 5 mins to chase {station_call}
de_relay
DE {chaser_call} {grid} {message}
chase_receipt
{station_call} is on the air and you are now chasing
no_beacon_nudge
No beacon received. Send @{base_call} to try again.

Hints

@callsign with no on-air op
{base_call} is not on the air. See aprsota.org/now limited to 1 per hour, then silent
@callsign targeting your own operator
You cannot chase your own op limited to 1 per 24 hours, then silent
repeat @callsign while a chase is already relayed
Already chasing {base_call}. Wait for their QSL. limited to 1 per 24 hours, then silent
beacon with no usable position while a chase awaits one
Beacon has no usable position. Wait for a GPS fix and beacon again limited to 1 per hour, then silent
W1XYZ-5OTA@K7ABC-6 greetings from mike
OTAW1XYZ-5Send a position report within 5 mins to chase K7ABC-6

Your position report must come from the same callsign and SSID that sent the chase. W1XYZ-5 chases, so W1XYZ-5 beacons, not W1XYZ or W1XYZ-9. A beacon from any other station does not satisfy the window. See exchange messages for the whole QSO, step by step, and QSL for how the host confirms it.