What is moving around the crew, on the screen they already hold

A ramp crew needs to know what is on short final. A quay gang needs to know which ship is alongside and which is still an hour out. Both answers exist in public broadcasts — this puts them on the handset that is already in their hand.

See it on your site See the security model

Scoped to the place they are standing

An organisation names the airports and ports it works at. Everyone there sees the same picture, and a worker who moves between sites can set their own without waiting on an administrator.

Aircraft around an airport, vessels in a port, nearest first, with bearing and distance from the site
A worker can add the site they are at today; it is theirs alone and does not clutter anybody else’s list
Nothing asks the handset where it is — the site’s coordinates are the org’s, so this feature learns nothing about where any individual stood

The details that decide what happens next

Not a map full of anonymous dots. Each contact opens to what a crew actually acts on, in the units the trade uses.

Aircraft: callsign, altitude and climb or descent in feet, ground speed and track in knots, and whether it is on the ground — the first thing a ramp crew reads
Vessels: name, IMO, flag, course and speed in knots, destination and ETA, and whether it is moored or under way
A photograph of the vessel where one is known, because "is that the one?" is the question a quay gang is actually asking
A full-screen map with range rings, and one tap to centre on the contact you were reading about

Reachable while you are talking

The point is to use it mid-job, so it is on the channel screen next to the audio route — not somewhere you navigate away to.

An aircraft or ship button inside the channel, only when your administrator has enabled it
Opens over the conversation and hands the screen back when you are done
Switched on and off by adding or removing a site — there is no second setting to disagree with the first

Awareness, not an instrument — and we draw that line in the product

Positions come from public ADS-B and AIS broadcasts, relayed by community receivers with real coverage gaps. It tells a crew a widebody is on short final. It is not separation assurance, and the app says so where it cannot be missed.

An empty list can never mean "the feed is down" — the app reports whether it is actually watching, separately from what it found, because to somebody on a runway those are opposite instructions
Coverage genuinely varies by region: some coasts are dense with receivers and others are nearly bare, and the app shows the difference rather than smoothing it over
Read-only. Nothing here can be commanded, and it is about vehicles rather than people — the same broadcasts any receiver on the apron already hears
Only the latest position is kept. A track history of everything near a customer’s sites is a surveillance dataset we have no reason to build

Which site do you work?

Give us the airport or the port and we will tell you what coverage actually looks like there before you commit to anything.

Talk to us