Counter-UAS research

Counter-UAS Research Methodology

Understand what each counter-UAS dataset represents, how dates limit its interpretation and how the fixed proprietary scenario is presented. Source references support specific claims; arithmetic checks do not independently validate a market model.

How to read this evidence

Directory entries, programme disclosures and dated opportunity snapshots describe different evidence. They do not establish current availability, procurement awards or validated market forecasts.

Three evidence grains

A directory row is a system description, a programme row is a public programme disclosure, and a pipeline row is a dated research observation. Record counts and quantitative fields retain these distinctions throughout the module.

Separate scenario arithmetic from model validation

The released global snapshot retains saved scenario values, five annual intervals for 2026–2031 CAGR, and four components that reconcile to the total. It has not been refreshed or independently validated. Detailed geography remains excluded while allocation labels and forecast drivers are reviewed.

Proprietary global scenario methodology

These figures present a fixed scenario from UXV Searcher’s proprietary counter-UAS model. All amounts are in USD million. Historical-year amounts are model estimates, and future values are forecasts rather than reported spending or booked supplier revenue. Detection, command and control, mitigation, and services are components of the same model total and must not be added to it. The 2026–2031 CAGR uses five annual intervals and is recalculated directly from the displayed series endpoints. This release uses saved aggregate values rather than a fresh model recalculation; underlying geographic allocations and forecast-year drivers require further review. The model’s original revision date and constant-price or current-price basis are not specified. Publication and extraction dates do not make the forecast a newly updated market assessment.

Saved aggregate arithmetic reviewed 1 November 2026. Detailed geographic outputs are excluded while their allocation labels are reconciled.

View the scenario and calculations →

Explore the evidence

Choose a table and open a record to review its source, date and limitations. Search and category selections stay within this view.

Public sample
Fixed public sample
2
Programs and commercial events · unfiltered sample rows
Retained catalog coverage
310
Rows in this dataset; not a market total
Catalog reference period
Mixed dated source records
Each record retains its own source date
Current access
Public preview
Additional records require module permission

Programs and commercial events

Schema-mapped, source-linked workbook records for licensed historical research. Current status is not reverified and amounts are not additive. Malformed or unlinked records are withheld.

Checking module access; public evidence remains available.

2 matching sample records · 2 fixed public records before filters. Catalog coverage: 310 retained rows. Counts describe research rows with the scope stated above.

Programs and commercial events. Expand a record for evidence, limitations and source links.
Record and evidenceProgram / eventOrganizationActivityGeography as suppliedAnnouncement date, where establishedSource-record value
Cerberus XL supply contractOpen evidence and sources

Evidence record AD-PREVIEW-004

Organization
Teledyne FLIR Defense / Kongsberg Defence & Aerospace
Program / event
Cerberus XL supply contract
Activity
Supplier contract announcement
Geography as supplied
Ukraine (announced end use)
Announcement date, where established
2023-08-29
Source-record value
USD 31 million (approximately)
Value scope
Announced supplier contract; not the total Ukraine programme budget, delivered units or expenditure.
Reported summary
On 29 August 2023, Teledyne FLIR Defense announced a roughly US$31 million Kongsberg contract for Cerberus XL platforms, software, spares, support and training within a wider counter-UAS solution for Ukraine.
Evidence label
Historical supplier contract announcement
Verification scope
Announcement date, named parties, stated value and scope; fulfilment and present contract status are not reverified.
Source check date
2026-11-01
Amount Aggregation Allowed
No
Verified Current Status
No
Record Basis
CURATED_PRIMARY_SOURCE_PREVIEW
Cerberus XL supply contractTeledyne FLIR Defense / Kongsberg Defence & AerospaceSupplier contract announcementUkraine (announced end use)2023-08-29USD 31 million (approximately)
PARADE programme commitmentsOpen evidence and sources

Evidence record AD-PREVIEW-005

Organization
Thales / CS GROUP
Program / event
PARADE programme commitments
Activity
Programme commitment announcement
Geography as supplied
France
Announcement date, where established
2022-04-29
Source-record value
EUR 33 million (as_announced)
Value scope
Firm commitments stated in the 2022 announcement; not the full multi-year programme budget or verified expenditure.
Reported summary
On 29 April 2022, Thales announced that the French defence procurement agency had selected the Thales and CS GROUP consortium for PARADE, with EUR33 million in firm commitments.
Evidence label
Historical prime-contractor announcement
Verification scope
Announcement date, named parties, stated firm commitments and programme identity; fulfilment and present status are not reverified.
Source check date
2026-11-01
Amount Aggregation Allowed
No
Verified Current Status
No
Record Basis
CURATED_PRIMARY_SOURCE_PREVIEW
PARADE programme commitmentsThales / CS GROUPProgramme commitment announcementFrance2022-04-29EUR 33 million (as_announced)

Explore the complete research

The public sample demonstrates the evidence structure. Request a demo to discuss the scope and access to approved anti-drone research. Signing in alone does not grant a module license.

Research questions

What does a linked source establish?

It establishes only the claim and scope described for that record. A document link does not independently validate current capability, every spreadsheet field or a commercial relationship.

How should historical directory entries be used?

Use them to understand documented coverage at the source date. Verify current specifications, availability, company status and deployments before making present-day comparisons.