Modern ARH SAM Guidance: Multipath Rejection and Low-Altitude Tracking

Welcome to my second suggestion ! This one is about multipathing in a modern era backround; suggesting a rework of the comportment of ground-to-air ARH (actve radar homing) missiles against low-flying targets. Prepare a good couch, cup of coffee and maybe Aspirin for later !
Your opinion is welcome, poll is at the end

Close Air Support (CAS) plays a major role in modern conflics; and so are weapons designed to avoid enemy aerial forces. They have evolved drastically trough the ages; started with a quadruple trench-war machine gun mounted on a truck to missiles creating dead-zones with radius up to 100km, and weights more than 500kg. But avoiding those missiles have never been easy; with each generation cames weaknesses.

Quick call-back : origins of multipathing

One of the oldest tricks in the book is multipath: when a radar signal bounces off the sea, the ground, or any nearby surface on its way to and from a target, the receiver picks up two overlapping copies of the same return (one direct, and a reflect on the ground) arriving from slightly different angles at nearly the same time.

The radar can struggle to tell them apart, and the reflected copy can drag its tracking solution toward a “phantom” position, sometimes right down toward the surface itself. For decades, this was a genuine exploitable weakness — the reason sea-skimming anti-ship missiles fly at wave-top height, and why a low-flying aircraft could sometimes vanish into ground clutter. This post looks at how that weakness works, how much modern radar processing has closed it, and where the physics still leaves a real tinnier gap.

image

Exemple of ground clutter.

Multitude of software and hardware updates have been made trough the 2000’s all the way to today in the objective of fighting against those clutter.

In-game, games at upper BR’s are ruled by air domination. Sadly most anti-air at toptier are quickly abused by multipathing targets and pop-up attacks or low-flying/hovering attackers (helicopters). Any target flying low (currently ± 30m) can escape any incoming ARH missiles, representing 13 out of 24 12.+ total missiles (>50%).

IRL comparaison.

‘Magnum!’ Flying A Wild Weasel Mission With The Tornado ECR And The F-35 - The Aviationist

In practice, multipath is no longer a reliable evasion method against modern air defenses. Today’s radars counter it directly through fine angular resolution, adaptive sidelobe cancellation, frequency agility, and other complex methods (that are quickly explained further). As a result, real-world evasion today relies on active, trainable tactics — notching, terrain masking, chaff/jamming, going cold — while multipath survives mainly as a residual, partial effect against older or lower-tier systems rather than a real tactic against modern ones.

Example of an imaginary modern SEAD mission of the Luftwaffe against Buk anti-air

1. Intelligence and mission planning

Before any aircraft launches, planners build an Electronic Order of Battle from prior SIGINT/ELINT collection — known or suspected SAM sites, likely engagement ranges, and radar activity patterns. Without a dedicated EW platform doing real-time jamming/geolocation, this pre-mission picture matters even more, because the strike aircraft won’t have a Growler-type asset actively mapping and suppressing emitters as it goes.

2. The range problem — why “medium-range” still matters a lot

Pantsir-S1 has an engagement envelope out to roughly 20 km against aircraft; Buk-M2/M3 extends further, commonly cited around 35–70 km depending on variant and target type. AARGM/HARM-class missiles have stated ranges well beyond both (AARGM is generally cited around 100+ km depending on launch conditions). So in principle, the strike aircraft can launch from outside the SAM’s engagement envelope entirely — this is the whole logic of an anti-radiation missile: force the enemy radar to choose between staying on (to keep guiding its own missiles) and getting hit, or going dark (and losing its eyes and guns).

3. Terrain masking during ingress

The strike aircraft’s survivability leans heavily on staying undetected as long as possible during approach — flying low, using ridgelines/valleys to break line of sight to known or suspected SAM search radars, and only climbing to acquire the emitter and get a valid missile solution at the last practical moment. This is slower and riskier than a jammer-supported package, since there’s no one degrading the SAM’s radar picture while the strike aircraft is exposed.

4. The wild weasel “pop-up and shoot” moment

At some point the aircraft needs enough altitude/line-of-sight to either passively detect the SAM’s radar (via RWR) or receive third-party targeting data, then fire from outside or at the edge of the SAM’s own engagement range. This is a vulnerable window — the aircraft is briefly exposed above terrain masking specifically to get a shot off.

5. What happens on the SAM’s side

A competent SAM crew, especially Pantsir or Buk operators aware of ARM threats, will often shut their radar down (“go cold”) or move immediately after illuminating a target, precisely to deny the ARM a stable emitter to home on — this is the mirror image of the notching/cold tactics you mentioned earlier for aircraft. Modern ARMs like AARGM partially counter this with GPS/INS memory of the last known emitter location plus a millimeter-wave radar terminal seeker as backup, so a “go dark” doesn’t fully save the site the way it would against older, purely passive-homing HARMs — but it’s not a guaranteed kill either.

Examples of modern counters

AESA radars with fine angular resolution

AESA radars use many small transmit/receive elements combined electronically, giving a much narrower, more precisely steerable beam than older mechanically-scanned or conical-scan antennas. That narrower beam and finer angular measurement let the radar separate the direct return from a low target and its ground/sea-reflected image, which older wide-beam systems couldn’t resolve apart. This largely closes off the low-altitude multipath deception that made terrain-hugging or sea-skimming an effective way to break a lock.

Frequency agility

rapidly hopping frequency changes the interference pattern the multipath reflection creates pulse to pulse, decorrelating it so it averages out over the tracking window instead of producing a stable false angle.

Adaptive SideLobe Cancellation (ASLC) / Constant False Alarm Rate (CFAR) processing

image

actively nulls energy arriving from the reflection’s angle and statistically rejects clutter-level returns, both used explicitly on systems like Type 03 Chu-SAM.

How CFAR works (easy schema).

Link to the video it’s from in

‘>Links and images to understand better some concepts if I wasn’t clear enough’

image

The objective is to electronically identify ‘noise’ and the target using complex numerical methods, and cancel the sound/jammer.

Micro-Doppler / blade-flash discrimination: The Doppler paradox of an helicopter

Is used to target helicopters mainly. Doppler works by supressing sationnary stuff to only see the targets and can work without being ‘jammed’ by scanning the whole regionnal topography. But what about a stationnary helicopter such as a hovering Mi-28NM by exemple ? Well Micro-Doppler is the Doppler effect for rotor blades, compressor faces, or propellers. Each add their own oscillating signature distinct from the fuselage’s overall closing velocity. The most exploitable form is blade-flash: brief, high-amplitude spikes generated when a rotor blade presents its broadside to the radar, recurring at a rate tied to blade count and RPM, which gives seekers a near-fingerprint for classifying rotorcraft or drones even when bulk Doppler is near zero, as with a hovering helicopter otherwise indistinguishable from ground clutter.

image

Steep terminal engagement geometry

missiles (Fox 3 especially, once on their own seeker) generally close from above or a steep dive angle rather than skimming the surface themselves, which geometrically separates direct and reflected paths far better than a shallow ground-radar look.

image

sorry for the bad meme, it’s the cleanest schema I could find to explain.

Used in air vs air in WT and IRL to get almost a 100% sure shot.

What can be found in toptier missiles ?

What I could find on modern anti-air and presence of modern counters in them
Missile AESA Seeker Frequency Agility ASLC / CFAR Micro-Doppler / Blade-Flash Discrimination Steep Terminal Engagement Geometry
Aster-30 (Block 1NT) Contraindicated — Ka-band active seeker; no AESA architecture disclosed Confirmed — explicitly stated in official sources Claimed — described as clutter suppression, not formally designated CFAR/ASLC Unconfirmed Confirmed — PIF-PAF thrust-vector control, ~60g terminal maneuver capability
Chu-SAM (Type 03, base) Confirmed — AESA seeker inherited from AAM-4 lineage Claimed — implied by AESA architecture, not independently stated Unconfirmed Unconfirmed Unconfirmed
Chu-SAM Kai Confirmed — explicitly stated; enhanced for low-RCS target detection Claimed — inferred from stated resilience to jamming Claimed — generic ECCM language, no formal designation Unconfirmed Unconfirmed
AMRAAM-ER Contraindicated — shares seeker family with AIM-120C-7; mechanically scanned Claimed — general improved ECCM language Claimed Unconfirmed Contraindicated — no thrust-vectoring system disclosed
AIM-120C-7 Contraindicated — confirmed mechanically scanned slotted array Claimed — improved ECCM with jamming detection cited Claimed Unconfirmed Contraindicated
9M317MA (Buk-M3) Unconfirmed — active radar homing head (ARGSN); AESA architecture unverified Unconfirmed Unconfirmed Unconfirmed Claimed — high-g thrust-vector control
CAMM Unconfirmed — solid-state seeker; scanning architecture not specified Unconfirmed Confirmed — clutter rejection explicitly stated by manufacturer Unconfirmed Claimed — thrust-vectoring control referenced
CAMM-ER Unconfirmed — shares seeker family with CAMM Unconfirmed Confirmed — pulsed-Doppler processing with clutter rejection stated Unconfirmed Claimed
FM-3000 Unconfirmed — insufficient open-source technical documentation Unconfirmed Unconfirmed Unconfirmed Unconfirmed
I-Derby ER Unconfirmed — software-defined RF seeker; AESA architecture not specified Confirmed — software-defined parameter control explicitly stated Claimed — ECCM capability stated, no formal CFAR/ASLC designation Unconfirmed Unconfirmed
Sources

Aster-30 (Block 1NT)

Chu-SAM / Chu-SAM Kai

AIM-120C-7 / AMRAAM-ER

CAMM / CAMM-ER

I-Derby ER

No usable links for 9M317MA (Buk-M3) or FM-3000 — I didn’t find sources solid enough…

Conclusion:

Visible complications of such application

Sadly, this addition would completely change the dynamic of toptier air gameplay. I’ve tried to list the arrangement to be implemented in an optic of keeping CAS possible and fair.

Keep in mind that multipathing is not the only way to escape a missile !

  • point n°0: stock chaff will be not only good but a need in smaller environements.

  • First of all, multipathing won’t work anymore after a certain missile generation (already partially in-game with SACLOS or IR missiles) , or be reduced to altitudes that messes with fuze’s sensibility, which makes pilots risking a lot with abrupt topography changes and a much higher risk of crash (that will be combined with the ‘new’ ,as of july 2026, maneuver kill mechanic.)

  • Secondly is the issue of smaller maps; some have air spawns too close and as well the end of the map still in the ‘dead’ zone of some missiles. Pilots will have to constantly notch, use the terrain and evade missiles without any possibility to have rest.

  • Helicopter will have to use as much as possible terrain coverage and MAW’s chaffs. The ‘hind doctrine’ ,as I call it, of frontal attack and count on armor/ECCM won’t be as good.

  • Helipads and airports will have to be in safer area, and more distant from the ground map. But remember that a static aircraft with shut down and cooled engine have no difference from a tree !

  • Slower gameplay, maybe a need for longer battles ?

Those changes are realistic and manageable; it is a big change in the gameplay, making pop-up attacks and short range air-to-ground missiles less common.

Links and images to understand better some concepts if I wasn't clear enough

https://www.radartutorial.eu/01.basics/Angular%20Resolution.en.html

To understand fine angular resolution.

https://www.researchgate.net/publication/313392321_Object_Discrimination_in_GMTI_Doppler_Radar_Data

image

to understand better Blade Flash discrimination

https://www.youtube.com/watch?v=BEg29UuZk6c

Constant false alarm rate - Wikipedia

To understand better CFAR (Constant False Alarm Rate)

What is Adaptive Sidelobe Canceller? | RF Essentials

To understand ASLC better (here in a context of electronic jamming)

Thank you for taking time to try to understand such complex systems ! I might even myself don’t understand fully things; feel free to correct me on those.

The objective here is not in an optic of complexification of mechanics, but to show a software and hardware update having as goal the rejection of multipathing and low-altitude tracking.

PS: This will surely not be added soon. Better missiles and jets can be added, ECM as well, and maybe modern stealth airframe will help a lot for HARM missions.

Give your opinion about changing multipathing for last-gen missiles

  • Change multipathing for toptier ARH SAM if sources/proof shows it can counter multipath.
  • Change multipathing for every aunti-air missiles (air-to-air as well) if sources/proof shows it can counter multipath.
  • No, keep multipathing as a way to deal with some of the modern missiles.
0 voters
3 Likes

I think for the sake of the game being playable above certain BRs an unrealistic degree of multipathing is needed. Imagine if we couldnt multipath to get away from hawk missiles in NE, that would be actual hell to play, now imagine its a quad of F-14s or any fox-3 slinger all looking at YOU, theres no fun in knowing you will die and you cant stop it unless we get some really good ECM and decoys soon. I think some tweaks to your idea would make it far better for gameplay.

Make trees affect radar altitude, they dont at the moment so on maps with absurdly giant trees you cant multipath to escape even relatively crappy radars without risking eating the local flora. This is especially annoying dealing with SAMs that can follow you through a forest which should be impossible. It also fixes your concern about helipads and airstrips if theres woodland or more hills giving natural radar cover.

Having a flat 50m ( i think its 50m, i always stick to 40m as the mpath and IOG can get lucky still) for all radar is rather silly. I think it should have differing heights depending on a general radar “generation”, earlier worse radars having a higher mpath alt (would also help with the dominance of the F3H right now) while the newest AESA radars have a much smaller Mpath height would help with the games authentic feeling.

TLDR:

I think multipath is a neccessary evil in the quest for realistic representation but the game can handle it better (trees affect Radar Altitude) and different alts for Mpath on newer better radars.

2 Likes

Good post however its complex would be a realistic addition esspecally for the future of the game for example when we get missile ships dumping SAM missiles into a sea skimming aircraft or missile for them to all miss when why should not have would be annoying. +1

True ground skimming is how I limp around at top tier.

1 Like

you will almost never not see me flying like this as soon as phantoms start appearing:
image

2 Likes

We need altitude hold and terrain following systems if available to the plane. (Terrain following tech was developed for this very issue)

1 Like

I dont think ground following autopilot would be good for the game tbh. let us follow the ground with radar sure, but i dont think automation should appear at all

2 Likes

If the Automation was built into the plane (I should write a suggestion for it) it should have it for example the BAC TSR-2 had the tech built in to go low and fast. Some systems to my knowledge can only work on the sea.

kinda makes the game play itself tho. WT has had serious issues with botting in the past (there was a while where almose every wyvern was a bot doing AFK grinding) and i dont think that should be incentivised.

This is getting off topic now, Worth suggesting it though as im sure aspects of it can work

1 Like

See, possibly for SAMs it could be a balancing thing. But, people should be warned that for AAMs that means multipath altitude for R-27 and R-77s would be 20m, well within the splash zone.

To add to this:
Multipath is something I use less than 1% of the time, but it as a feature allows for more varied enemies for both teams.
Many at high altitude, mid altitude, & the deck.

It’s far more interesting than matches all on the deck or all up high.

I enjoy the variety of matches.