Testing Link Resilience Under Jamming Without a Jammer

The Test Everybody Skips

Deliberately radiating interference requires authorisation that most development programmes do not have and will not get for routine testing. The practical result is that EW resilience — the single most decisive factor in whether a tactical platform survives contested airspace — is the one characteristic that reaches the field completely unvalidated.

This is a solvable problem. A large fraction of what determines jamming resilience can be measured through conducted testing, link margin analysis, and behavioural testing of the failure path, none of which require radiating a watt.

Conducted Testing: The Method That Requires No Spectrum

Take the link into a shielded enclosure or work conducted, coupling the interference directly into the RF path through a combiner rather than over the air. You control interference-to-signal ratio precisely, you produce repeatable results, and you radiate nothing.

What this reveals is the shape of the degradation curve. Frequency-hopping systems typically hold nominal performance until a threshold and then collapse over a narrow band of a few dB. Direct-sequence spread spectrum degrades more gradually. Knowing which you have, and where the knee sits, tells you what the failure looks like operationally: a link that goes from full function to nothing across 3 dB gives an operator no warning at all.

The Behaviour Matters More Than the Threshold

In practice, what determines outcome is rarely the exact jamming margin — it is what the aircraft does at the moment the link is lost. This is fully testable without any interference at all: pull the antenna, power down the transmitter, block the receive path.

The questions worth answering are concrete. How long until link loss is declared? Systems with long confirmation timers fly a considerable distance under stale commands. What is the failsafe behaviour, and is it appropriate — return-to-launch is a reasonable default and a poor one if the return path crosses the threat that caused the loss. Does the aircraft attempt reacquisition, and does the attempt itself radiate a signature? Several platforms respond to jamming by transmitting harder, which is an efficient way to be located.

Field Example: Eleven Seconds of Stale Commands

On a platform we assessed, the specified link-loss timeout was 3 seconds. Measured behaviour was different: the receiver held its last valid command set through a 3-second confirmation window, then attempted reacquisition for 8 seconds before declaring failsafe. Eleven seconds at 22 m/s is 242 metres of flight under commands that no longer reflect operator intent.

The datasheet was not wrong about the 3-second timer. It simply described one stage of a three-stage sequence, and nobody had flown the full sequence and timed it with a stopwatch. We did, and the customer changed the reacquisition logic before fielding.

What to Specify

Ask vendors for the jamming margin in dB relative to nominal link budget, the degradation shape, the complete link-loss sequence with timings for each stage, and the emission profile during reacquisition. A vendor who can answer those four has tested their system. A vendor who answers "it uses frequency hopping" has told you a design choice and nothing about behaviour.