Corrected 7 September 2026. The original article combined interception counts from one UAE update with larger detection totals from a later update. Its 36% drone and 80% missile figures were incorrect. The headline and conclusions have been revised.
The UAE reported intercepting about 93% of detected drones in its early updates on the attacks beginning on 28 February 2026. The figures describe hundreds of interceptions, but offer limited evidence about the performance of individual air-defence systems.
These are aggregate figures released by the UAE authorities. They are neither independently verified engagement records nor a performance assessment of a particular weapon system.
Two updates, two sets of totals
The initial statement reported 209 drones detected and 195 intercepted, alongside 137 ballistic missiles detected and 132 destroyed. Fourteen drones fell within UAE territory or waters; five missiles fell into the sea. WAM report carried by Emirates 24|7
A subsequent WAM update on 1 March covered cumulative detections since the attacks began: 541 drones, of which 506 were intercepted and destroyed, and 165 ballistic missiles, of which 152 were destroyed and 13 fell into the sea. Two cruise missiles were also reported destroyed. These were UAE totals, not a combined count for all Gulf states. WAM's cumulative update
The arithmetic is straightforward when each numerator stays with its own denominator:
195 of 209: 93.3%
132 of 137: 96.4%
506 of 541: 93.5%
152 of 165: 92.1%
The percentages above are calculations from the reported counts. Dividing the earlier 195 interceptions by the later 541 detections produces approximately 36%, but describes no consistent reporting period. The earlier 132 missile destructions divided by the later 165 detections creates the same error.
What those percentages can tell a buyer
At face value, the releases describe a defence effort intercepting a large majority of detected threats in both categories. They do not demonstrate that drones were categorically harder to intercept than ballistic missiles in these engagements.
Nor would reversing the comparison establish that missiles were harder. The categories involve different threats and potentially different engagement decisions. Aggregate percentages conceal those differences.
A procurement officer evaluating performance would need considerably more information: the threats actually engaged, the criteria used to classify an interception, the assets being protected and the systems involved. A release listing detected objects and reported destructions cannot answer those questions.
Objects reported as falling into the sea should not automatically be counted as successful defensive engagements. Equally, a detected object that was not reported destroyed cannot automatically be assumed to have struck its intended target. The public figures do not provide that level of attribution.
This limits the conclusions available about Patriot, THAAD or any other named system. Assigning the aggregate result to one platform, or diagnosing a failure in its radar configuration from these totals, would go beyond the evidence.
Protection extends beyond the interception count
The cumulative statement also reported casualties and property damage, including damage from interception debris. A high reported interception share therefore cannot be equated with an absence of harm. WAM
For civil authorities, the outcome of interest includes injuries, damage and disruption to essential services. For armed forces, it also includes whether defended assets remain available for their missions. Interception statistics describe only one part of that outcome.
This distinction matters when comparing counter-drone proposals. A supplier offering a high detection or interception percentage still needs to explain what was measured and under what conditions. A demonstration against a known target set is different evidence from a sustained operational record.
The US Government Accountability Office's 2022 counter-drone technology assessment distinguishes detection from mitigation and identifies limitations including false detections, interference and unintended effects. Those considerations support evaluating a complete protection requirement, rather than selecting equipment from a single headline percentage.
Costs need the same discipline
The price of an attacking drone compared with the price of a defensive interceptor is a useful starting question, but an incomplete measure of value.
A costly interception can still be justified if it prevents a much larger loss. Conversely, a low advertised cost per engagement says little about total expenditure unless it includes the relevant equipment, staffing, support and replacement requirements.
Comparisons between different defensive technologies need a consistent accounting basis. The purchase price of an interceptor and the electricity consumed during an engagement are different categories of expense.
A better commercial comparison begins with the protection required and the duration for which it must be sustained. Buyers can then assess acquisition costs, support needs, consumables and the consequences of interruption.
The procurement conclusion
The early UAE figures provide no sound basis for declaring a broad failure against drones or for prescribing a particular replacement system. They also cannot settle whether additional capabilities would improve protection.
The useful lesson is narrower: evaluate counter-drone procurement against an explicit protection requirement and comparable evidence. Keep reported operational results separate from vendor specifications, and signed purchases separate from proposals.
For a concrete acquisition case, Poland's SAN programme shows how a buyer is assembling several capabilities within one programme. Our European drone-wall review follows the separate question of which political commitments have become orders.
The UAE reporting demonstrates why those distinctions matter. An incorrect denominator can manufacture a capability gap; it cannot justify a procurement decision.