ASOUAID
ASO · AIRSPACE SURVEILLANCE
VLL · BELOW 120 M

Challenged. Signed. Verified.

Unified airspace identification

Identity for the lower airspace.

Ground stations challenge every node in range. Each one answers with a signature that cannot be forged, from a key that never leaves the chip. The identity holds while the airframe, the operator and the mission change underneath it.

30 m mast · permanent coverage · thousands of nodes per station

listening
Scroll
Tower model: Radio tower by Gunnar Correa, CC BY 4.0
01 · The principleProof, not announcement

Remote ID announces. UAID proves.

Upper airspace solved identification with ADS-B. Below 120 metres there is no equivalent. Remote ID identifies an airframe and announces an identifier that anyone can copy: built for accountability, not for assurance, and broken the moment a fleet operator swaps an airframe or leases a fleet out.

UAID, Unified Airspace Identification, identifies the hardware node, proves it cryptographically on every response, and keeps the identity constant while ownership, operator and airframe change underneath it in a time-stamped registry. It answers the question neither ADS-B nor Remote ID can: is this aircraft really the one it claims to be, and who was legally responsible for it at 14:22 UTC?

FIG. 01 · INTERROGATION PATH ASO · UAID · VERY LOW LEVEL AIRBORNE GROUND 01 CHALLENGE single-use nonce · every node in range wakes GROUND STATION · 30 m mast ASO-RO-25-HW-0001234-C3 96 km · −97 dBm · VERIFIED 02 SIGNED RESPONSE identifier + signature over the nonce 64 km · −94 dBm · VERIFIED ASO-DE-26-LT-0004417-C3 41 km · −91 dBm · VERIFIED NO VALID SIGNATURE DROPPED AT THE STATION · NOT PUBLISHED STATION VERIFY SIGNATURE 2–5 ms · measure RSSI · timestamp 03 RESOLVE · REGISTRY owner · operator · airframe · status 04 PUBLISH · UTM & ATC network Remote ID · ASTERIX CAT-129 KEY verified response, published dropped at the station IDENTITY IS RESOLVED BY THE REGISTRY, NEVER BY THE PAYLOAD

THE GROUND STATION IS THE OBSERVER · It challenges, measures the response itself and verifies it against the registry. Nothing reaches UTM on the strength of what an aircraft claims about itself, and an unsigned or geometrically implausible response is dropped before it ever gets there.

01

Bound to hardware

The identity key is generated inside a secure element at manufacture and can never be read out. Copying the identifier gets an attacker nothing, because without the key there is no valid signature.

02

Signed on every response

Each answer carries an elliptic-curve signature over a single-use challenge. The station verifies it in milliseconds and drops anything it cannot verify, before the track reaches UTM or ATC.

03

Observed from the ground

Identification never depends on what the aircraft says about its own position. GNSS jamming and spoofing, now routine across eastern Europe, degrade the picture; they do not blind it.

↑Interrogation range 0km From a 30 to 60 m mast against an aircraft above 300 m. Horizon-limited, not power-limited.
↑Identity refresh < 0s Per node, with a full signature, in the higher-duty deployment configuration.
↑Nodes per station 0 At a 300 second revisit interval. Fewer as the revisit interval shortens.
↑Mass on the aircraft 0g A component, not a system. No access to the flight control, only power and an antenna position.
02 · Two timelinesOne layer

State operators can use it now.

The technology is the same in both cases. What differs is what has to be true before it can be used. Military and state operations sit outside the civil framework by law, so nothing has to be agreed first. Civil U-space deployment needs an authority at the table, and that is where the mandate, and the volume, will come from.

Now · State and defence

Friend-foe classification below Mode 5

A station challenges, a node proves itself with a key that cannot be copied. That is the IFF principle, applied below the altitude where Mark XIIA Mode 5 lives, on platforms that cannot carry a Mode 5 transponder for reasons of mass, cost and export control.

  • No EASA operator ID required. A NATO unit identifier is the verification anchor instead.
  • Sovereign sub-registry, full internal audit trail, nothing forwarded to EASA.
  • Works where GNSS does not, because the station measures the signal itself.
  • Batch purchase, nodes assigned per mission order and rotated across airframes.
Available with the commercial node and the exemption path in the registry. The hardened variant is in design for Q4 2026.

Next · Civil U-space

The identity layer the mandate will need

U-space makes identification a service obligation rather than a good idea. UAID is built to supply it at an assurance level above an unauthenticated identifier, and to carry the ownership record that a broadcast cannot.

  • A technical means for the network identification service under Art. 8 of Reg. (EU) 2021/664.
  • Complementary to direct Remote ID on the aircraft, never a substitute for it.
  • The registry answers who owned, leased and flew an aircraft at a given minute.
  • Standard output formats, no bespoke integration on the customer side.
In preparation. Field mapping and update rate to be agreed with the competent authority; pilot deployments planned for 2026.
03 · DeploymentSame identity layer

Fixed site or in a case.

The node and the protocol are identical in both. What changes is the station: a permanent installation that covers a corridor or a city cell, or a case-sized unit with a telescopic antenna that an operator carries to the mission and switches on.

Fixed site

Mast or rooftop

Permanent coverage for a vertiport, a corridor or an urban cell, published into UTM and ATC and logged without interruption.

  • Thousands of nodes per station, scaling with the revisit interval.
  • Ethernet and LTE backhaul, uninterruptible supply, IP67 outdoor enclosure.
  • Keeps verifying, tracking and logging through a network outage.
  • Multilateration once three or more stations see the same node.
Range is horizon-limited: 100 km from a 30 to 60 m mast against an aircraft above 300 m.

Mobile kit

No mast, no installation

A case-sized station with a telescopic antenna for mobile missions, exercises, temporary sites and incident response. Set it down, extend the antenna, and the picture is there.

  • Up to 10 nodes, operational within minutes.
  • Skyware Light included: the traffic picture in a web app, no server to install.
  • Same challenge, same signature, same registry as the fixed site.
  • Runs standalone where there is no infrastructure to connect to.
The same horizon rule applies from operator height, so plan the range from where the station stands and how high the aircraft flies.

04 · Two ways in

Airspace to prove it in. Aircraft to carry it.

We are selecting pilot partners for the 2026 city deployment, and manufacturers who build the node into the airframe while the mechanical and electrical interface is still open. Both start with a technical session of thirty to forty-five minutes.

Book a meeting Talk to engineering