Drone MANET Communications in Contested Environments

Modern drone operations have moved from single FPV strikes to coordinated formations and, increasingly, to swarms of cooperating UAS that share sensing and targeting data, re-plan around lost members, and saturate point-defence systems from multiple axes. All of this rests on one thing: a mesh datalink that survives jamming, node loss, and a topology that never stops changing. This page walks through a NetSim model of exactly that problem — a mixed force of strike, ISR and relay drones operating over an L-band ad-hoc mesh in a 5 km × 5 km contested patch, stress-tested with both an adversary jammer and a kinetic kill on a backbone relay.

The Scenario

A drone strike and reconnaissance operation runs over a 5 km × 5 km area. Eight FPV strike drones engage ground targets; two ISR drones provide wide-area surveillance; four high-altitude relay drones form a backbone that ties the forward UAS back to a single Ground Control Station at the southwest edge of the area. The adversary brings two threats: a jammer parked near the centre of the operating area, and a short-range air-defence system capable of engaging low-altitude UAS.

Figure 1: Initial node deployment. The shaded red circle is the jammer's 750 m effective radius; it covers Strike-1, Strike-2, ISR-1 and Relay-2.

Force composition

The Network

All fifteen nodes share a single L-band DTDMA mesh with AODV routing on top. Connectivity is range-based at 1500 m: any two nodes inside that radius have a link; beyond it, they do not. That hard cutoff forces traffic to multi-hop through the relay backbone, and it is what makes mobility and node loss interesting — an optimal next-hop today is gone tomorrow.

Parameter	Value
Frequency band	L-band, 1350–1400 MHz
Channel bandwidth	5 MHz
MAC protocol	DTDMA, frequency hopping enabled
Routing protocol	AODV (reactive, suits mobile UAS)
Aggregate channel capacity	12 Mbps
Communication range	1500 m (range-based pathloss)
TX power	20 W per node
Modulation / coding	16-QAM, rate 3/4

Table 1: Headline radio and network parameters. PHY values are based on published specs of fielded tactical L-band MANET radios.

Traffic Carried Over the Mesh

Four application flows model the operational traffic. Three move uplink to the GCS; only the C2 stream goes the other way.

Flow	Direction	Rate	What it is
C2 commands	GCS → each Strike UAS	64 kbps × 8	Joystick / waypoint updates. < 200 ms latency budget.
FPV video	each Strike UAS → GCS	64 kbps × 8	Low-bitrate H.265 from the strike camera.
PLI	each UAS (all 14) → GCS	16 kbps × 14	Position / status reports for situational awareness.
ISR imagery	each ISR UAS → GCS	128 kbps × 2	Wider field-of-view surveillance video.

Table 2: Application flows. Aggregate offered load is roughly 1.5 Mbps; the channel itself carries 12 Mbps. The mesh is hop-count limited, not bandwidth limited.

The Stress Events

The 70-second simulation includes two adversary actions designed to stress different failure modes: one electronic, one kinetic.

Figure 2: Stress event timeline. Both events affect the same mesh.

Event 1: L-band jammer activation (t = 30–60 s)

A jammer at (2200, 2500) lights up the 1350–1400 MHz band. Drones inside its 750 m radius see a 20 dB rise in noise floor, which knocks SINR down hard enough to drop packets even though the link still “exists” from a range perspective. At the initial node positions the jammed set is Strike-1, Strike-2, ISR-1 and Relay-2 — one of the two relays that the central backbone runs through.

Event 2: Relay-4 shoot-down (t = 45 s)

Fifteen seconds into the jamming window, adversary air defence engages and destroys Relay-4. The kinetic loss is instantaneous and permanent: no warning, no graceful shutdown, no SINR ramp. Relay-4 is one of the GCS's two backbone neighbours, so its loss forces every remaining packet to enter the mesh through Relay-1, on top of an already-jammed Relay-2.

Three Experiments

The two stress events stack progressively across three experiments so that each failure mode can be isolated.

Experiment	Configuration	What it isolates
Exp 1 — Baseline	No jamming, no failure	Best-case PDR, latency and PHY-error floor under nominal mobility.
Exp 2 — Jamming	L-band jammer active 30–60 s	Localized PHY-layer impact on the four drones inside the jammer zone.
Exp 3 — Jam + Shoot-down	Exp 2 + Relay-4 destroyed at t = 45 s	How far damage spreads when a backbone relay is lost during EW.

Table 3: Experiment matrix. Each experiment is run with 4 seeds and reported with 95% confidence intervals.

Results

Three indicators show the stress climbing across the experiments. The first is a spotlight on the most-jammed flow — FPV from Strike-1, the closest strike to the jammer's centre. The second is the PHY-layer error count, which captures jammer impact directly even when frequency hopping protects the PDR. The third counts the nodes in the network whose performance is materially affected by each stress event.

Figure 3: Three indicators of progressive stress. Left: PDR for the FPV flow from Strike-1, the strike drone closest to the jammer's centre. Middle: PHY-layer error count over the 70 s window. Right: number of UAS whose performance is materially affected — nodes inside the jammer zone in Exp 2, plus nodes whose primary route to the GCS used Relay-4 in Exp 3.

Why It Matters

Stress-testing a tactical mesh against this exact combination — mobility, coordinated electronic warfare, and a kinetic kill on a key node — is almost impossible to do on real hardware. NetSim makes it a configuration file. The same scenario template extends to alternative routing protocols, different waveforms, larger swarms, mobile jammers, multi-jammer geometries, and progressive air-defence engagements. If you are evaluating a tactical MANET radio, designing a swarm comms architecture, or studying contested-environment resilience, this is the kind of analysis NetSim is built for.