Can a 10 km Counter-UAS Radar Be Exported?

Can a 10 km counter-UAS radar be exported? The short answer is: not from the range figure alone. It may be exportable, it may require an export license, or it may be prohibited under certain end-user, end-use, or destination conditions. The real answer depends on the specific product, technical parameters, destination, end user, end use, transaction route, and current export-control rules.

This article is a high-level compliance overview, not legal advice. Specific projects should be reviewed by the exporter, compliance team, and qualified counsel where needed.

10 km Is Not the Only Test

“10 km counter-UAS radar” is usually a market description that indicates a detection-range class under certain target and scene conditions. Export-control review does not rely only on the advertised distance.

Reviewers may also consider:

radar band, transmit power, waveform, and antenna capability;
detection, tracking, height measurement, velocity measurement, and target-processing functions;
dedicated software, algorithms, encryption, or data-link features;
integration into command-and-control, identification, fire-control, or other sensitive systems;
whether the configuration is civil security oriented or more sensitive;
technical data, source code, test tools, remote support, and training.

That is why two systems both described as “10 km radar” can lead to different compliance conclusions.

First Check Whether the Item Is Controlled

Under China’s export-control framework, exporters must determine whether the goods, technology, software, or services to be exported are controlled. China’s unified Dual-Use Items Export Control List took effect on December 1, 2024, and radar-related items may appear within relevant sensor and laser categories. Actual classification should be based on the current list text, technical notes, and authority requirements.

Export control is not limited to hardware. Software, technical documents, test methods, maintenance support, remote debugging, and training may also need review in some cases.

Do not rely only on HS code or product name. Customs classification helps with declaration, but export-control classification usually requires technical parameters and use context.

End User and End Use Matter

Even if a radar is intended for civil low-altitude security, review still depends on end user and end use.

Key questions include:

Who is the real end user?
Is the end user identifiable and credible?
Is the end use civil security, airport operations support, industrial-site protection, or something more sensitive?
Is there any resale, transshipment, re-export, or change of use?
Are there destination-specific restrictions?
Is the transaction connected to restricted entities, military users, or high-risk routes?
Can the buyer provide end-user and end-use assurances?

If end user or end use is unclear, compliance risk rises sharply. A serious supplier normally cannot promise exportability based only on a short inquiry.

What Documents Are Usually Needed?

To assess whether a 10 km counter-UAS radar can be exported, supplier and buyer usually need a document package.

Common materials include:

product datasheet and technical description;
key technical parameters and configuration list;
software, interface, and accessory scope;
destination country or region;
end-user information;
end-use statement;
no-change-of-use, no-transfer, or no-re-export undertaking where required;
contract, purchase order, invoice, and shipping route;
site application or project background;
license application materials if required by the authority.

Complete materials do not guarantee approval, but they make risk assessment and schedule planning more reliable.

Licensing and Delivery Time Should Be Planned Early

If the item is controlled, an export license may be required. Licensing review can add time and may require additional documents. Compliance should not be left until the last few days before shipment.

A better process is:

Collect end-user, end-use, and destination information before quotation.
Classify the product based on technical parameters.
Determine whether a license or further consultation is required.
Include compliance conditions and document obligations in the contract.
Arrange production, shipment, and site support after the compliance path is clear.

This reduces the risk of equipment being ready but unable to ship.

Buyers Should Support the Review

Some buyers ask, “Can your 10 km radar be exported directly to our country?” A supplier cannot reliably answer without context. Compliance review is not a delay tactic; it is a normal part of high-value sensor projects.

Buyers should prepare:

company and end-user information;
project scenario;
place of use and purpose;
whether government, military, law-enforcement, or critical-infrastructure users are involved;
whether resale or third-party integration is planned;
whether local import, radio, or spectrum permits are needed.

This information helps both export review and the buyer’s own import and project approvals.

What Suppliers Should Not Promise

A responsible supplier should not claim, before review:

“It can be exported to every country.”
“It is only civil because it is 10 km.”
“We can ship through a third country.”
“The real end user does not need to be stated.”
“The license will definitely be approved.”

Those claims increase project risk. Export compliance is not about making paperwork look acceptable. It is about ensuring the item, transaction, user, and use can withstand review.

Official References

For real projects, check the latest official materials, including:

Conclusion

Whether a 10 km counter-UAS radar can be exported cannot be answered with a simple yes or no based only on range. The 10 km figure is a performance description. Export compliance depends on controlled-item classification, technical specifications, destination, end user, end use, transaction path, and licensing requirements.

The practical answer is to review the technical file, user and use information, destination, and delivery scope early in the project, then follow the current licensing and compliance process before committing to shipment.