The Detail Data Display: Introduction
Most of the introductory details about the DDD are covered in the manual, so I will not repeat them here. Just to recap, the DDD displays different measures depending on the radar mode or the function used (i.e. P, AN/APX-76 and PD).
The DDD in Pulse mode has been mentioned several times already: it is a b-scope, showing Azimuth as the abscissa, and range as the ordinate. This mode is really handy for intercepts and angle considerations as it is basically a top-down view clearly showing a potential drift.
The DDD in Pulse Doppler mode shows the Azimuth as the abscissa, but the closing rate but versus the ground, rather than the F-14. What does it mean?
As mentioned, PD mode removes the F-14 as a factor in terms of speed. Understanding how this works is fundamental, as the TID in Aircraft Stabilized mode does not provide all the information the RIO may need or want at a glance. Not to mention when the target is beyond “RWS-range”.
Happy 3+ Friends
The DDD provides little information about the contacts detected. Contrary to the TID, it cannot show different values or data. Therefore, if the RIO is limited to the DDD by malfunctions or radar (i.e. contacts are displayed only in PD SRCH), combining the DDD with other devices can drastically augment the SA. This is also a good practice to better understand the situation at a glance, without cycling through the TID readouts by means of the CAP.
For example, noting which bar returns a contact can help to assess if a contact is higher or lower and if the situation changes over time. Of course, due to the range, even 1B is very tall, but it is still a good indication (you can use my Antenna Elevation model “backwards” to get ΔALT from range and angle). Speaking of range, an empirical and rough way to determine it is switching from PD SRCH to RWS. If the target is shows in PD SRCH but not in RWS, then it may be further away than a certain range, depending on the aircraft. This last information can be sometimes obtained by means of the RWR if the target is a fighter.
The following scenario shows a MiG31 probably hot, high and fast but not appearing on the RWR. Therefore, the range is higher than circa X.
DDD in Pulse Doppler mode
When a Pulse Doppler radar mode is selected, the display switches the Range on the ordinate with the Relative closure, maintaining the Azimuth on the abscissa.
This mode is less intuitive than Pulse, but it greatly complements the TID in Aircraft Stabilized mode, providing the RIO with the information that the TID does not immediately show.
The Aspect Switch
Recently implemented, the Aspect switch not only affects how the DDD presents information, but also affects directly how the radar operates:
“In the pulse doppler search modes it controls the rate processing windows of the radar, NOSE sets 600 knots opening to 1,800 knots closing, BEAM sets 1,200 knots closing to 1,200 knots opening and TAIL sets 1,800 knots opening to 600 knots closing.”
The effect on the DDD is simple: the central mark on the left side in “Beam” represents 0 kts. The marks above and below indicate either +600 kts or -600 kts. The zero shifts consequentially.
Mainlobe clutter trace
When the Mainlobe Clutter filter switch is used to turn it off, if at the same altitude the terrain is visible (for example, when feet-dry at low altitude with 4 or 8 bars selected), the ground return normally filtered appears on the DDD.
The position of the trace depends on a few factors, in primis the Aspect switch discussed above.
In very simple terms, the MLC trace shows where the relative speed is zero, so it normally “follows the zero around” as the switch is operated.
As we know, if a contact enters this region, it usually becomes “invisible” to the radar because its relative speed is zero, so it is considered de facto as ground returns.
ZDF: Is it Curved or is it Flat?
The MLC trace is not flat, and the reason is immediate. What about the area filtered by the Zero Doppler filter?
Since the ZDF “surrounds” VF14 and is not related to the contact per sé, it is always positioned at -VF14 ± 100 kts. Unfortunately, this means that the ZD filtered area fluctuates following the speed of the fighter. The RIO should be always aware of the TAS of the F-14, to immediately understand what happens if a target suddenly disappears from the scope.
The following example shows multiple contacts, either flying true or parallel stern, appearing and disappearing due to the effect of the Zero Doppler Filter. The contacts start at a speed of 250 kts, whereas the F-14 starts at 450 kts. The contacts then accelerate to 650 kts and then slow down again to 250 kts. Therefore, the targets spawn at 200 closing, reach 200 opening, and then slow down again, passing the ZDF twice in the process. Two aspects are worth noting:
- the area on the DDD where the contacts fade: as mentioned, it is flat;
- drift: pay attention to how the targets drift as the speed changes.
This is a collage of the different traces, to highlight the ZD Filtered area.
Using the Detail Data Display in Pulse Doppler Mode
In Search mode or, better, in non-STT modes, the DDD complements the TID providing additional information. This is especially true in the case of the, in my opinion, best attack mode: Aircraft stabilized mode.
Since the vector displayed in such mode is the difference of the euclidean vectors, it does not change depending on the position of the target and it is sometimes often to spot changes in heading or speed, which immediately affect the closure rate and are giveaways (especially the heading) of a target trying to, for instance, defend from a missile, either preventively or actively.
In Ground Stabilized mode, when the NAVGRID is on the aircraft is patrolling and building or maintaining Situational Awareness, the DDD provides information that Range While Search does not provide, since this mode does not build any track (not mention when the contacts are so far away that PD SRCH is the only meaningful mode).
Displaying the relative closure rate, it can provide some details useful to the RIO to better understand the situation. For example, a non-drifting target (although the drift is harder to appreciate in PD than P mode), with high closure may indicate that a bogey placed us on collision course, and it is intercepting us. Similarly, if the relative closure drops, it may indicate that the target is manoeuvring (perhaps a CAP now turning cold).
The DDD in PD mode completes the TID AS by telling the RIO if a contact is about to notch or if it is trying to hide in the ZDF area. These details are not available directly to a RIO that relies only on the TID AS (at least not in such as direct way as by means of the DDD).
A Potential Drawback: Clutter
Who doesn’t love some Maths?
Welcome again to the best part of any article: Trigonometry (aka the proof that High School is useful)!
The Closure Rate, VC has been recently discussed in this simple article. Make sure you checked it before proceeding.
The formula I used to determine the Closure rate is the following:
However, the DDD does not display VC on the ordinate, but the Relative Closure (it does display a mark on the right side). This is explained in the manual:
“[…] the radar itself only reads relative airspeed which is then modified by subtracting own airspeed for display on the DDD.”
This means that the displayed contact will have a relative rate of:
This equation allows the RIO to understand the displayed values.
An Alternative Implementation?
I have a question. Why subtracting VF14 rather than setting it to zero?
If VF14 = 0, then it’s component in the Vc equation becomes zero, but the ordinate on the DDD becomes even more representative of the aspect of the contact. In fact, when the ordinate = speed of the target, then the target aspect would mean zero: that would be a neat and almost instantaneous way to determine the target aspect!
Instead, the implementation of the DDD is a mere Vc – VF14 so, although the ordinate is still indicative of the closure of the contact, it is… well, not as cool.
(unless I’m missing something, which is entirely possible).
Setting VF14 to zero:
VREL = – VTGT * cos (BRG – HDGTGT)
It appears even more immediate now how, if the target is Hot, the BRG matches the Bandit reciprocal, the VREL tends to be closer to the speed of the target.
(The sign does not matter)
VREL = 0 * VF14 * cos (BRG – HDGF14) – VTGT * -1 = VTGT
HDGTGT = 205°
BRG = 025°
As usual, we can determine the TA as usual:
BR = 025°
TA = BR → BB = 025 → 025 = 0°
Now, proving the equation:
VREL = – VTGT * cos (BRG – HDGTGT) = – VTGT * cos (025 – 205) = – VTGT * -1 = VTGT
The implementation we have in the DDD perhaps better represents the positioning of the target, see the examples discussed below.
Practical Examples and Empirical Demonstration
The following scenarios aim to better give some ideas about how the DDD can be used and which are some of the information provided. At the moment, the DDD does not provide all the information displayed on the manual (such as the AGC Trace).
Each of this scenario sees a contact on the nose (FH = BR) and a second contact, with the same speed and heading, but with an offset on the azimuth.
I also approximated the Notch gate (±133 kts around V0 and the Zero Doppler Filter ±100 kts). Moreover, I added the representation of the vector as it is calculated in the TID in Aircraft Stabilized mode. In these scenarios, the “height” of the vector, when the speed of the F-14 is not considered, matches the VREL value.
The empirical evaluation is the only way we can compare the DDD output with the hypothesis expressed above.
They may not be spot on down the single knot, but it is a good comparison nonetheless.
The scenario above, replicated in DCS, looks like the following:
A simple, yet very approximative, way to understand is the conclusions explained above are correct, we can measure the distance between different points, using the known 600 kts mark as meter to determine the others. The results are, all things considered, fairly similar:
The contact already matches the 600 kts mark.
ATA = 45
45.5 : 600 = 19.2 : x
→ x = 253.2 kts
Considering the many imprecisions introduced by this empirical approach, such as the difficulty in creating a proper scenario in DCS in terms of angles, or even nailing the correct ATA considering how fast the aircraft are moving and the consequent drift, the result is quite convincing.
ATA = 0
36.8 mm → 517 kts
ATA = 45
28.5 mm → 400 kts
The resulting value is still quite similar.
A different example here: both notching and ZDF.
The in-game scenario is a bit different. In fact, none of the returns are visible immediately.
On the left, the target appears almost immediately, as soon as the closure drops under -133 kts (I did not nail the correct ATA, btw).
On the right, the target is hidden in the ZDF, and it appears much later compared to the previous.
Let’s check the numbers:
Notching Target (Left)
10.9 mm → -144 kts (negative, as the target is opening)
53.4 mm → -705 kts
Both cases match both the closest value to the theoretical, allowing them to be visible.
The mission with all the scenarios covered in this article (besides the MiG-31), is available here. Keep in mind it is not perfect and the angles are eyeballed, but it should give you a better idea of how contacts behave on the DDD in a known scenario.