Counter-UAS in the Gulf — opportunities and challenges

The requirement stopped being exceptional

Counter-UAS in the Gulf is no longer a special project attached to a single event. It is a standing line in the security architecture of airports, ports, energy infrastructure, borders and government facilities — which changes how it is bought. Special projects are bought on capability demonstrations. Standing requirements are bought on integration, sustainment and cost per site.

That shift is why a great many counter-drone vendors report strong interest and few contracts. The interest is real. The procurement, when it comes, asks questions the demonstration never covered.

Why single-sensor systems disappoint

Every sensing method has a failure mode that another one covers, and a system built on one method inherits that failure without compensation.

The Gulf environment sharpens all four weaknesses. Heat and dust degrade electro-optical performance. Urban and airport sites are among the most RF-congested environments anywhere, which raises the noise floor for detection and the false-alarm rate for classification. And there is a great deal of entirely legitimate air traffic to discriminate against.

• RF detection misses an autonomous drone flying a pre-programmed route with its link off
• Radar struggles with small, slow, low-flying targets against ground clutter
• Electro-optical needs a cue, and daylight or thermal contrast
• Acoustic detection has short range and degrades badly in noise

Detection is the easy half

The hardest part of a counter-UAS programme is not detecting a drone. It is deciding what to do about one — and that is a legal, jurisdictional and operational question rather than a technical one.

Who has the authority to act, over what airspace, under what rules of engagement, and with what liability if a mitigation attempt affects a legitimate aircraft or falls on a populated area? These answers vary by site and by end user, and they determine what equipment is worth buying at all. Programmes that specify effectors before establishing the authority to use them tend to buy capability they cannot lawfully employ.

A detection system that produces alerts nobody is empowered to act on has not created security. It has created a log.

The authority question has named owners, and they are not the same body

The reason the mitigation question is hard is not that nobody has thought about it. It is that the answer is distributed across several authorities with different mandates, and a vendor conversation usually touches only one of them.

In the UAE, the civil use of unmanned aircraft sits under Federal Decree-Law No. 26 of 2022, with the General Civil Aviation Authority developing the operating framework and the relevant Emirate-level aviation authority involved as well. The radio spectrum side is separate: the Telecommunications and Digital Government Regulatory Authority issues the regulations for unmanned aircraft radio systems — updated again during 2026 — under the federal telecommunications law, setting technical and authorisation rules for the bands used by drone control and payload links in order to manage spectrum use and harmful interference. It governs the authorisation of drone radio systems; it is not a counter-drone authorisation instrument. Where TDRA and civil aviation requirements conflict, the civil aviation position takes precedence.

At Emirate level the responsibilities are in some cases published. Dubai Law No. 4 of 2020 regulating unmanned aircraft assigns Dubai Police responsibility for establishing and implementing countermeasures, with the Dubai Civil Aviation Authority, Dubai Police and the concerned entities involved in evaluating and selecting countermeasure systems. So the question of who owns the decision does have public answers in places.

What remains unpublished, so far as we have found, is the operating layer: no generally available instrument sets out the spectrum authorisation and conditions under which a site operator or a vendor may actually use a radio-frequency effector against a drone. Detection that does not transmit avoids that particular problem, though it raises others of its own — passive radio monitoring can engage communications and interception rules, and camera-based detection engages privacy and restricted-site rules, which Dubai's drone law addresses directly.

The practical consequence for a vendor: a mitigation capability sold on performance, into a site whose operator has not established that authority, is a capability the customer may not be permitted to switch on. That conversation is better had early, where it shapes what you propose, than late, where it cancels it.

Integration is what the evaluation actually scores

Buyers have learned that a counter-UAS system which cannot hand a track to the existing command centre becomes a separate screen in a separate room, watched by nobody at three in the morning.

The questions that decide a competitive bid are therefore about behaviour rather than specification: how the system classifies a track and with what stated confidence, what its measured false-alarm rate is in that specific environment, how it feeds the command and control system already in service, and what happens to the operator picture when one sensor drops out.

This is why counter-UAS is increasingly procured as a layer of a wider security system rather than as a product. It is also why an integrator who has already connected disparate systems for that end user has an advantage no amount of sensor performance overcomes.

A standing requirement is bought differently from a project

The shift from event-driven projects to permanent capability changes the commercial shape of the opportunity, and vendors are slow to adjust to it.

A one-off installation is bought largely on capability and price. A capability that has to be maintained across many sites for years is bought on sustainment cost, spares and support in country, training and certification of local operators, software and threat-library update paths, and how the whole thing is refreshed as drones change. Those are the questions that dominate the evaluation, and they are the ones a demonstration never answers.

It also brings the localisation machinery into play. Multi-site, multi-year security programmes are exactly the kind of procurement where in-country value scoring and, above the relevant thresholds, industrial participation obligations start to matter to the price and to the choice of partner. A counter-drone vendor who has thought carefully about detection probability and not at all about who sustains the system in country has prepared for the wrong evaluation.

What this means for a company entering the market

If you sell a sensor, your realistic route is as part of a layered system somebody else integrates — which means the partner conversation matters more than the product conversation. If you sell an integrated system, expect to prove it against local RF conditions and local traffic, not in a European trial.

In either case the buyer has usually already been disappointed once. Being specific about what your system does not do is, counter-intuitively, the fastest way to be believed about what it does.

Three things are worth establishing before the first serious meeting, and none of them is about your technology. Which authority owns the mitigation decision at the site in question. What the system has to hand a command centre that already exists, and in what format. And who performs sustainment in country over the life of the capability. A vendor who arrives with considered answers to those is having a different conversation from one who arrives with a detection range.