Use case
Drone detection for airports and helipads
At an airport the arithmetic is simple: one drone in the wrong place stops traffic, and every minute stopped costs money and confidence. Visibility of what is flying nearby is not a luxury there.
Why people fly above a site like this
- Spotters and photographers launching from the edge of the site for shots of landing aircraft.
- Simple ignorance: many pilots do not know how far a restricted area around a runway extends.
- At regional fields: model and FPV flyers active in the surrounding area.
- Rare but decisive: someone deliberately disrupting traffic.
What a deployment looks like
- Number of units
- A three-kilometre runway takes two to three units, at the thresholds and in the middle, linked into a single picture.
- Mounting
- Existing masts and roofs on the site, permanent and over PoE.
- Deployment model
- Buy with a subscription, or offline on your own server. The optional ADS-B module puts manned and unmanned traffic on the same map.
- Alerts
- Through the API into air traffic control or the operational control room, with zones per runway direction.
Where the limit sits
An airport usually already has radar and sometimes RF analysis. The DRID does not replace that; it adds identity and pilot position, which radar does not provide. We would rather supply one layer of your architecture here than a replacement for it.
Your situation not among them?
Describe your site and what you want to know. We will say honestly whether Remote ID detection is the right tool for it.