Ramp, gate and ops on one channel

One press, whoever is on the stand

A channel per stand, per shift or per function, and everyone connected hears the same call at the same moment. No dialling, no waiting for someone to accept.

• One speaker at a time, arbitrated by the server, so two people cannot talk over each other on a busy stand
• Connection quality is shown before you key the mic, not after the call fails
• Works on the airport Wi-Fi or on cellular, with no repeater and no spectrum to coordinate

The map as the index into the channels In development

A live picture of what is on the ground and on approach, where every aircraft is a way into the conversation about it. Not a second screen to watch — a way to stop asking "which channel is the Madrid turnaround on?".

• Tap an aircraft, land in its channel. A turnaround gets a channel when it gets a stand, and the map is how you find it without knowing its name
• Stands and gates are channels too. Tap a stand to hear the crew working it right now, and see who is connected before you key the mic
• Inbounds create channels before they land. The channel for a flight exists while it is still on approach, so the crew is briefed rather than assembled on arrival
• An emergency shows where it was raised. The alert already carries the channel; the map turns that into a place on the airfield

The neat part is the split. Aircraft positions come from ADS-B, which every aircraft broadcasts unencrypted to anyone with an aerial — it is public, and that is exactly why we can put it on a map cheaply. What is not public is what your crew says about it: the positions are open, the conversation stays end-to-end encrypted. The map is not the secret. The talk is.

How it would actually be built, and where it stops

Written now rather than after, because the honest constraints decide whether this is useful at your airport or a toy.

• Air picture is easy. A public ADS-B feed, or your own receiver on the roof for lower latency and no third party in the path
• Ground picture is the hard part. ADS-B surface coverage is patchy and many aircraft stop transmitting at the stand. Reliable ground movement needs an airport surface feed we would have to integrate per site
• Stand and flight association is per airport. Mapping a callsign to a stand means your AODB or turnaround system, not something we can guess from the air picture
• We would not track staff. Putting your people on that map is surveillance, not coordination — if it is ever built it will be opt-in per person and consent-gated, like every other setting that trades privacy for visibility

And the line that matters most: this would be situational awareness for ground operations, never surveillance for separation. It is not certified, it is not ATC, and it must not be used to make a movement decision that belongs to a controller. If you want it, tell us which airport and what surface data you already have — that answer decides whether it is weeks or a research project.

What airside actually asks about

Two questions come up on every airside conversation, so they are answered here rather than discovered later.

• Nothing is broadcast over the air. There is no licence, no spectrum and no scanner to overhear — traffic goes over the data network as ciphertext
• It does not replace certified voice. push.tt is operational coordination, not an air-ground or safety-of-life system, and we will not pretend otherwise

If your operation needs a system with an availability guarantee behind it, ask us before you buy. We would rather lose that sale than be the reason a turnaround stalls.