DroneSentry-X Mk2 procurement: detect vs defeat, export licensing, and equivalents

Buyers asking for DroneShield DroneSentryX Mk2 are usually solving perimeter or convoy CUAS — but the quote path forks immediately on whether they need detection only or active defeat (jamming/ECM). That single choice…

Buyers asking for DroneShield DroneSentry-X Mk2 are usually solving perimeter or convoy C-UAS — but the quote path forks immediately on whether they need detection only or active defeat (jamming/ECM). That single choice drives export control, end-user eligibility, supplier shortlist, and lead time. This brief is the procurement spine we use before routing an RFQ — distilled from live sourcing (including Argentina airport deliveries) and DroneShield's own product configuration.

What DroneSentry-X Mk2 is

DroneSentry-X Mk2 is DroneShield's vehicle-mountable / expeditionary detect-and-defeat unit: passive RFAI detection across consumer and commercial ISM bands, plus optional RFAI-ATK electronic countermeasures in the same enclosure. It ships in two configurations:

Configuration	What it does	Typical buyer
Detect Only	Passive RF detection, bearing, geo-location, operator locate (DroneLocator where available)	Civil airports, critical infrastructure where mitigation authority sits with police/military
Detect and Defeat	Same detection + integrated soft-kill jamming/GNSS denial	Military bases, government security forces, sites with spectrum/defeat authorisation

Key field specs (verified against DroneShield on-the-move documentation): 46 kg, 710 × 710 × 532 mm, IP67, -20°C to +55°C, C2 via JSON / gRPC / TAK (CoT). Mounting: commercial roof-rack, mast, vessel deck, or semi-fixed via the Expeditionary Fixed Site (EFS) Kit.

DroneShield is Australian — export sales typically run through DASA (Defence Export Controls), which many non-US buyers prefer over ITAR timelines on US effector systems.

The question that unblocks quoting: detect or defeat?

Before any supplier can price DroneSentry-X Mk2 for cross-border delivery, confirm:

Engagement scope — detection/tracking/ID only, or mitigation required?
Who holds defeat authority — site operator (licence/exemption in hand), co-located state force, or detection-only with defeat deferred?
End-user type — civil airport operator vs government/security agency (matters enormously for jammer exports).

If the buyer needs defeat at a civil airport but lacks spectrum/defeat authority, the honest architecture is often:

Detect-only Mk2 (or detect-only fixed DroneSentry) for the site operator, plus
Separate defeat operated by police/military (handheld DroneGun, protocol-takeover, or kinetic), or
A protocol-takeover system (no wideband jamming) that clears civil licensing faster.

Routing a Detect-and-Defeat Mk2 RFQ to distributors without confirming defeat authority is how quotes stall at export compliance — we saw this on a live Argentina/Ezeiza requirement.

Export and licensing — Argentina and LATAM pattern

Jammer-grade defeat systems (DroneSentry-X Mk2 defeat mode, Cerbair Medusa/Chimera, MCTECH RF jammers, R&S CUAS effectors) are dual-use. For Argentina specifically:

Government end-user is typically required for defeat/jammer variants.
Expect export licence from the country of manufacture plus Argentine end-user certificate and import approval.
Civil airport operators without a designated state mitigation partner should assume detect-only unless they can name the authorising agency.

Faster civil/airport paths (where defeat is still required but jamming is restricted):

Approach	Suppliers / products	Licensing note
Protocol takeover (RF-cyber)	D-Fend EnforceAir, Sentrycs	No wideband jamming — often easier at operating airports
Detect-only + outsourced defeat	DroneShield Detect-Only Mk2 + state force effector	Site buys sensors; defeat operated under state authority
LATAM channel partner	America's Solutions (Cerbair), MCTECH + BE1 partner	Proven regional delivery paths; still need end-user paperwork

US-channel DroneShield resellers (e.g. Security Pro USA, Pyrdex) frequently quote HS 8543.70.9090 and ITAR/EAR awareness on defeat variants — useful for US-sourced paths, not a substitute for Argentine import clearance.

Equivalent products (when Mk2 is specified but not mandatory)

If the buyer accepts equivalents, these appear on live LATAM/Gulf RFQs:

Product	OEM	Fit vs Mk2	Export note
Chimera 200	Cerbair (France)	Detect + defeat; Argentina Army tender reference	EU dual-use; LATAM via America's Solutions
MC-Horizon D360	MCTECH (Israel)	RF jammer — defeat-heavy	Govt end-user; LATAM deliveries via regional partner
EnforceAir	D-Fend (Israel)	RF-cyber takeover — best civil airport regulatory fit	No jamming — faster civil licensing
Sentrycs	Sentrycs (Israel)	Protocol takeover	Proven LATAM government deals
Crow	Indra (Spain)	Integrated C-UAS	Strong LATAM government footprint

Do not substitute equivalents when the buyer names DroneSentry-X Mk2 on a firm OEM spec — confirm acceptability first (OEM channel: DroneShield direct, Security Pro USA, Pyrdex, MSS Defence, Orbital Connect).

Procurement checklist (supplier quote request)

When routing an anonymised RFQ, suppliers should be asked to confirm:

Unit price and MOQ for Detect Only vs Detect and Defeat (if both are in scope)
Lead time to DDP destination airport/city
Export licence path (DASA for DroneShield; ITAR/EAR if US channel; EU dual-use if EU OEM)
End-user documentation required (government end-user cert, import permit, spectrum licence for defeat)
Training, C2 integration (TAK/CoT, REST), and monthly RF signature library subscription
Detect-only downgrade option if defeat authority is not yet granted

Related Aviation Souk resources

Counter-UAS Systems for Airport Perimeters — sensor layers, legal constraints, Gulf context
DroneSentry-X Mk2 product page — verified specs and supplier link
Counter-UAS & Base Air Defence category — full supplier index

Last verified: June 2026. Export rules change — confirm end-user and licence path with the OEM or authorised distributor before placing a firm order.