DCS F-14 & RIO Gaming

ΔV in non co-speed intercepts: Empirical Assessment

The declassified and freely accessible documents cover only co-speed intercepts. This is a short study that aims to quantify the impact of the difference between VF14 and VTGT on the Collision Course.

As we have seen multiple times, the basic documentation (such as the P-825/17) covers only the co-speed intercepts. In such scenarios, the Collision Bearing is determined very easily by using the relation: CBCOSPD = Cut / 2.
However, in DCS this is very rarely the case. Therefore, when the speed of the fighter (VF14) and the speed of the target (VTGT) are different (ΔV > 0), the relation is no longer applicable.

This simple study aims to quantify the difference between CB and CBCOSPD. In other words, help the RIO to better understand this situation by having an idea of how much, what he can expect and what he can do to compensate such difference.

Note: The CB is often referred to as CATA: Collision Antenna Train Angle. It makes sense since the CB is the ATA value when there is Collision.

Let’s start from the beloved TID in Aircraft Stabilized mode, as it shows very clearly when Collision Course is established no matter ΔV. By comparing that angle and CBCOSPD, we can understand the magnitude of the impact of ΔV on CB.

Testing scenario

These are the parameters set for recreating the TID AS display below. In this scenario, the two variables are VF14 and VTGT.

FH = 360°
BH = 135°

DTG = 135° (“ α “)
Cut = 45L
DOP Left to Right

The image above clearly shows how the CB changes depending on the speed of the fighter and the bandit.

It is interesting to note how the Vector generated by aircraft having the same ratio displays the same angle, although the Vector’s length is different.

For example, the Vector angle (and therefore the CB) of a situation where VF14 = 300 and VTGT = 200 is exactly the same of a scenario where VF14 = 450 and VTGT = 300:

300/200 = 450/300 → 1.5

(The image on the side is hand-drawn, so there are imprecisions).

Hey, hey kid! Wanna calculate some angles?!

The question is how we find the angle. The answer can be found in the geometry, by doing some poor man’s reverse-engineering on the TID Vector:

We already know that, then CB is established, the vector points towards the F-14 and the triangles defined by the vectors and the one defined by the headings and the CB are geometrically similar (my coolest discovery so far :p ).
Let’s consider the third image. The thick black line is the FFP, the red thick line is the FFP used to construct the vector. Therefore, they are parallel. CB, the thinner black line that connects the vector to the F-14, is therefore cutting two parallel lines. The angles originated are congruent (“γ”, the green one, plus the red, which is the opposite angle). We also know b, c and α.

The Cosine rule allows to easily calculated the hypotenuse (the “length” of the Vector, “a“). From there, we can calculate γ.

a2 = b2 + c2 – 2bc * cos α

cos γ = (a2 + b2 – c2) / 2ab

I chucked the formulas on Google Spreadsheet (I can share the spreadsheet, but there’s really not much to see there) and then filled a table with different values of speed:

CB Variation, Cut 45°

CB Variation, Cut 45°

Then determined ΔCB:

Δ CB, Cut 45°

Δ CB, Cut 45°
Δ CB, Cut 45° (%)

Practical Test

A simple test to check if the model makes sense:
Altitude: Co-altitude, value non-factor;
VF14 = 400;
VTGT = 200;
I set up the geometry a bit randomly, let’s see what the TID said:

True Course: 167
True Heading: 19

DTG = 148°

Cut = 32° → CBCOSPD = 16°

However, due to the speed difference, CB must be adjusted. The model should tell us how much:

I measured the CATA graphically, htherefore there is a double chance of introducing imprecisions: CB in-game and measurement with GIMP. However, the resulting value is 10.26°, quite close to what the model suggested.

Practical Utility?

The issue here is that there is no linear relation between the parameters (at least I can’t see one). If, for example, the values of ΔCB expressed as a percentage were constant for different values for DTG, then it would be easy. Unfortunately, this is not the case and the simplest solution in this scenario is using the avionics (e.g. the Collision option on the TID).
There are still some interesting things to notice. Let’s start by looking at how the values change for different DTG.

VTGT is constant at 400, DTG is calculated between 80 and 170:

It gets even more interesting when we look at the Δ:

Observations and Conclusions

After this quick dive into the geometry, what can we conclude?

  1. No simple relation: unfortunately the lack of a simple relation describing the variations of the CATA as a function of ΔV makes the creation of a single model impossible (it would require too many pages: assessing the drift and correcting is much more efficient).;
  2. Maths & Geometry. The relation between the parameters is purely geometrical. It does not matter if the values are IAS, TAS, CAS, GS, mm/day; as long as both speeds are measured using the same unit;
  3. ΔV: considering an equivalent ΔV, CB varies more from CBCOSPD when the target is slower than the F-14.
  4. Higher DGT = Less Variation: it may be taken for granted, but there is more: if you look at the Δ percentages of the test right above, they are quite similar after a certain magnitude of DTG, although in reality the variation consists of several degrees. For example, VTGT = 350, DGT = 80 → -9.1%, DGT = 90 → -8.5%. The same interval instead includes from DTG 120 (-7.3%) to DTG 170 (-6.7%). This is important because the RIO can expect a greater variation between the Cut / 2 and the actual CB when Cut is high.
    Therefore, low DTG requires more corrections, since it impacts the angles the most;
  5. Low Target Speed: when VTGT is low, the difference between CBCOSPD and the new CATA is higher.
    For example, considering the Δ for DTG = 130, VTGT = 200 → CB = -8.84°; for VTGT = 600 = 5.33;
  6. Combining the last two points, we can now identify the case where CB diverges the most from CBCOSPD: low Speed, high Cut (or low DTG). This case is the trickiest as the two parameters make the CB diverge the most from CBCOSPD. On the other hand, the difference decreases along the Cut, to the point where, in extreme cases, reference tables are not even useful anymore.

New Kneeboard Page

The quantity of parameters and the lack of a simple, intuitive and linear relation that does not require the RIO to do any abstruse calculation, makes creating a dedicated kneeboard page quite hard. In theory, dozens of pages are required to satisfy the combinations of the variables, which is honestly a waste of time when we can use the Tactical Information Display in Aircraft Stabilized mode to monitor the CB and the DDD (or the attack display in a modern aircraft) to monitor the drift and correct if necessary.
Nevertheless, a couple of reference tables can help new RIOs to have an idea of the magnitude of the difference between the actual CB and CBCOSPD.

This page is quite simple to use: the columns’ header with inverted colours is the speed of the F-14 (I choose 400, 500, and 600). The headers are the speed of the target. The rows’ header is the Cut. The column having a grey background is the co-speed CB.

Examples

The following are three simple examples of how the page can be used to determine the CATA.
Example I

VF14 = 500
VTGT = 350
Cut = 40

We use the second table, fourth column, fourth row from the bottom → 16°. The RIO simply has to command the Pilot to turn until ATA = 16°.

Example II
This is the same example discussed above in the Practical Test.

VF14 = 400
VTGT = 200
Cut = 30

We use the first table, first column, third row from the bottom → 10°. Again, the RIO simply has to command the Pilot to turn until ATA = 10°.

Example III
For the last example I put together a simple scenario:

VF14 = 400
VTGT = 600
Cut = 97
CBCOSPD = Cut / 2 = 48.5°
Instead, CB in this scenario is ~61°.


When values are not exactly what reported in the tables (it never will), they can be rounded following the usual procedure. At the end of the day, this is a tool aiming to help the RIO to better understand what to expect, not SOP-worthy material (in my opinion, of course).

2 comments

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: