RIO advice needed on locking targets on DDD to match target on TID

[hannibal]

after a few months of enjoying and exercising RIO work..

I still have trouble looking at bricks on DDD, HCU to lock a target on DDD, and have it match what i am seeing on TID....

i am setting the SCAN AZIMUTH to 10 degrees, pointing antenna in direction of where bandit group is, (trying to go for the closest target) and usually do a few takes on STT locking on bricks on the DDD to get the corresponding target displayed on TID

(it seems to always lock on a really far target like 80+nm away, when i am just trying to lock on the closest bandit to me....)

I cant seem to confidently lock on something on DDD, that i see on TID... i even tell pilot to go faster to get better resolution in closure..

 

ideas i have are,

a) to turn off DATALINK contacts on TID

b) go to PULSE Search, set to a desired range like 25-50 NM, and better lock on target based on range instead of closure?

 

ANY ADVICE, most appreciated...

Edited January 8, 2024 by hannibal

[Thorp]

I am a DCS RIO with more than a few flight hours, but I'm still learning the do's and don'ts.

Idea A to toggle datalink is an okay idea within reason; it's your call to clear the clutter. But datalink provides accurate information that helps with spacial awareness. It's your call. At least toggle it on periodically as to not be blind-sided by avoidable scenarios.

I would say that your idea B, using Pulse Search to identify targets by range on the DDD, is a good idea within certain parameters. You'll certainly have an easier time identifying which targets are closer on the DDD in Pulse Search. When targets are flying in close formation it can be tough to separate them on the DDD and TID and the computer will often combine formation spikes as a single brick (that can look slightly bigger than normal, oddly shaped, or fade as 2 separate bricks). The main issue with Pulse Search is that it does not pin information to the TID (neither does Pulse Doppler) and Half Action drops all information until a target is locked.

If targets are 30+ nm away, I find it reasonable to either use RWS because it populates the TID the fastest and you can judge which DDD brick matches the TID formation and see closure on the DDD, or you may have enough time to use TWS Manual/Auto so you can assess and then hook the specific target you want on the TID directly (this is extremely slow). The pilot also benefits from RWS & TWS TID readings if they can take the time to glance. The downside to the Doppler searches (PD, RWS, & TWS) is they can be notched especially when the bandit is trying to defend from the AIM-54 missile you launched at 45-70 nm which should be pitbulling a hot target by the time you reach 30+ nm if you cranked 55-65 degrees after launch. When the targets are hot, notching is not a huge threat because they'll only notch if they are trying to defend and if they do, they'll have to go cold or beam which likely puts you on the advantage. (But this is where my knowledge flounders because if I have 2 cold bandits that are going to nose hot again, they will naturally notch when turning back hot unless I'm in Pulse Search which limits locking to only 1 target anyway).

In the instance that you're outnumbered and terribly close to the squadron of bandits, you'll want to either bug out or send missiles to ideally force them on the defensive and off your tail. At 30 nm, AIM-54s can splash but it's not too likely and the bandits get awfully close if not already firing missiles at you before your missiles are close enough to threaten them. TWS Auto will allow guided AIM-54 launches or you can risk bypassing the missile loft for a straight line bore-sight shot by switching to ACM mode in the pilot seat or flipping the switch on the bottom right of the left vertical panel (PH ACT). (Low altitudes drastically reduce the travel distance potential of AIM-54s).

Furthermore with TWS hooks, I find switching from a hook to STT is more successful when the STT button is pressed as soon as or shortly after the hooked target is spiked on the DDD.

Remember to keep an eye on the TID closure rate and alert the pilot to adjust the flight path to avoid notching, and if the notch is unavoidable switch to P-STT so you don't lose them (only to chaff can they be lost except for terrain occlusion).

Edited February 3, 2024 by Thorp

[bonesvf103]

Since you are concerned with locking on to the closest bandit based on returns in your DDD, I would suggest being in pulse search mode, that way you get range in your DDD.  Since you were trying to get info in the TID, I assume you were in a pulse doppler mode.  If the bandit is less than 50 nm away and you are in pulse mode, you can see which one is closest to you in the DDD then use the HCU to lock him, and then you will get all the info you wanted in the TID.

Now if for whatever reason you want to use the pulse doppler modes (maybe you want a longer detection range than 50 nm), then the best thing you can do to lock the closest bandit is to use the datalink.  That way you can get the clues you need to help you figure out which blip in the DDD is the closest one to you based on the datalink contact in your TID.  It might not be very efficient though as you wont' have closure information from the DL and that is what is displayed on the DDD in this mode, but you can at least get azimuth to be able to pick out a little better which blip is the closest one to you.  But I think the more efficient way to get a lock on the closest bandit from a pulse doppler mode is to use the DL or the BRAA call to help you configure the radar to get the bandits on your own radar.  If they are far enough out, start with PD Search and once you see them in the DDD and they are less than 90 nm away, switch to RWS and give them a few sweeps, you will have info in the TID as to who is closest then you can switch to TWS, hook the closest one you want, then hit PSTT or PDSTT as needed.  The idea is you start building up your picture and SA and you refine your target returns as you close in to shoot or intercept.

v6,

boNes

 

 

 

 

[Silverphinex]

There is also the option of using the IFF to have the DDD in a more Top down view Temporarily It's Not perfect but its another way to use the DDD