This discussion is the direct follow-up to the analysis of Track-While-Scan, which often turns out to be a detrimental, if not counterproductive, radar mode.
Today’s topic is how you can use multiple radars better when you are flying with your friends. As I did before, the simple animations show the characteristics of the F-14’s AWG-9, but the concepts are applicable to any other aircraft.
The picture below shows a pair of smart crews using a fully open radar setup, for instance, Range-While-Search. The distance is 80nm. As you can see, you can’t see two radar cones: most of the time, in fact, radars are not used proactively and are left there, scanning the same areas. However, we can do better than that!

Sanitisation and Radar Mating
The idea is rather simple: stack the radar vertically. By doing so, the evident blind spot identified in the previous video is addressed and, depending on the conditions, the crews can reduce the size of the scanned cone (in DCS, that is).
This concept is not new, as many players might have encountered it whilst studying Timelines and Intercepts. Simplifying, the purpose of the so-called “sanitisation” and “radar mating” was to ensure maximum airspace coverage to check for potential threats before refocusing on the picture.
However, the same idea can be profitably applied to other situations.

The (quasi) Modern US Navy Way
The public documentation provided by the US Navy recommends setting the T-45’s radar to 140° azimuth 6 bars, and the display to 25nm. The lead element should then set his radar to bracket between 40,000ft and 15,000ft. The wingman should instead cover between 25,000ft and the ground.
In addition, a certain overlap between the two AoRs is encouraged to ensure no gaps are left unchecked.
The airspace sanitisation process is expected to last a fairly considerable amount of time, circa 13 seconds. However, what happens if we try to reapply the concepts to a smaller radar cone, for instance 130°, 4 bars? As we can see, these settings do not cover the vertical side properly. An alternative would be to reduce the azimuth by a notch to 80°, and set the bars back to 8. This can be an acceptable compromise in a casual environment, especially if friendly forces are in the area, as the result is still vastly more effective than leaving the radars at 0° of elevation.

At the end of the day, it comes down to the crews in the cockpits. Still, similarly to what was discussed in the previous video about Track-While-Scan, seeing different possibilities and options can be beneficial, even if used out of their intended context or not strictly by the book. That’s the beauty of a video game.
…Now What?
If you are wondering how things progress after the radars are arranged as discussed, here is a quick and dirty overview. These topics have been discussed on FlyAndWire at the beginning of 2020, and you can find more information linked in the description below.
Starting with the lexicon, the two halves of the airspace are called AoR, or Areas of Responsibility. The recommended overlapping zone is called “Razor”. In this case, it is equivalent to 20,000ft.
Each element scans his AoR. If a contact is illuminated and matches certain criteria, such as the aspect or the distance, then the Section may decide to commit.

One of the most appreciable features of such a radar arrangement is that the element that spots the target can take the lead for the engagement. Let’s say, for example, that the target is trying to sneak below the Section’s radars, but it is seen by the wingman in his AoR. Rather than passing information to have the lead point the radar, assess and rebuild situational awareness, the wingman can just take over and command the intercept. At this point, the Section leader automatically assumes the role and responsibilities of a “temporary” wingman.

Like many other topics concerning operations, these procedures can be amended, defined in ad hoc contracts, and shaped depending on how you prefer to fly, whether it be casual servers, airquake, et cetera.
Note: for the wingman, if the upper boundary of the AoR is lower that the current altitude, the cone will point towards the ground. Ergo, the Razor should be adjusted as a function of the Section’s altitude.
Conclusions
The concepts discussed in this video and the previous one probably are, in hindsight, plain and simple common sense, isn’t it? The thing is, since the vast majority of us play a video game and are not exposed to the world of military aviation directly, we simply lack the experience, expertise, or perspective, to realise how we can introduce little things to improve our effectiveness. That’s why tools such as TacView are so important.
So, I hope you have found this video useful. If you have questions or suggestions about topics I can cover, feel free to post in the video description, forum, Discord, and so on.

You must be logged in to post a comment.