Computed pop-up attacks: when, where, how, and why?

[DarkFib3r]

I would like to learn when and how to create and employ computed pop-up attacks.

When is the best time to use a computed pop-up attack? Is it to simply clear terrain obstacles like hills or mountains that might be obscuring your target, or is it a better tactic for engaging high-threat targets, like SAMs and AAA? Surely there’s a time and place for this tactic as my NOE attacks usually result in me dropping a few AIRs or BLU-107s via a straight-in approach without me having to conduct any high pop-up. So far, I have never actually conducted a computed pop-up attack and I am wondering if I am depriving myself of a useful tactic.

There are two kinds of computed pop-up attack modes: VIP and VRP and each pop-up attack mode has four cues: your visual initial/reference point (VIP/VRP - diamond), your offset aiming point(s) (OA1/OA2 - triangle(s)), your pullup point (PUP - circle), and your target (TD box). From what I understand, VIP assumes that your VIP is a set steerpoint, and the target, offset, and PUP are in relation to that point. Furthermore, VRP assumes that your target is a set steerpoint, but your VRP, offset, and PUP are offset from it.

Based on my understanding of the two modes, I would use VIP if I want to conduct a pop-up attack against a target AWAY from the steerpoint and VRP is the target is ON the steerpoint. If this is accurate, my big questions are:

1. When is the best time to conduct a computed pop-up attack?
2. How do you actually follow the different cues to conduct the attack as planned?

Let’s say you have a target, like a bridge, that you want to strike. In this instance, you set up your steerpoint directly on the bridge. Let’s also say that the bridge is protected by a long but narrow hill that you can terrain mask behind. Since you don’t want to fly NOE on the exposed side of the hill, you decide to plan a computed pop-up from behind the hill. Since your steerpoint is the bridge itself, you decide on a VRP attack.

Given the scenario above, what should you consider when designing the pop-up? What is a good distance and bearing to set the TGT-TO-VRP? How about the TGT-TO-PUP? How many offsets should you set and why would you set more than one? Which one do you choose?

After you have set up you VRP in your data cartridge and you are rolling in on your target, what do you need to do in A-G mode? I read that you TMS-Right to cycle the sight mode, but which one would you choose? I am assuming that you have to go into the ICP and set VRP to 0 to enable it. Do you do this on the ramp or just before you are rolling in? Also, I have seen that new symbology (VRP, OA1, OA2, PUP) comes up on the HUD. Which ones do you follow and when? Is there anything else you need to do to configure yourself properly for the attack? When should you switch to CCIP?

I am intrigued to learn why this mode of attack is beneficial and to try this mode of attack out. Unfortunately, the sample YouTube videos and the BMS documentation are not clear to me about when, where, how, and why you would conduct this type of attack. There was a Japanese video that seemed to explain VRP/VIP attacks using Weapons Delivery Planner, but I do not know Japanese and was only able to glean a few insights from it. If there are tutorials or documentation you can point me towards, I will gladly check it out. As always, any help is appreciated!

[Frederf]

Pop-up attacks are used against fixed targets when it is determined that low altitude ingress and short duration exposure are the critical factors in maximizing survivability. When to use various tactical tools is the $1M question. Personally I would favor such a technique in a long range penetration type mission where local and/or brief superiority cannot be achieved. FLOT or large package work it’s usually better to be higher, slower, and more forceful. Unfortunately I feel that the popup’s primary strength, surprise against air defense reaction time is underrepresented in BMS.

The “bump” to either deliver level or a Maverick is a legitimate type of popup attack. The usual purpose of the extended climb is to allow maneuvering room for a dive release (often CCIP) to maximize accuracy. If your selected weapon or desired accuracy doesn’t require a diving or higher height delivery, there’s no need.

(V)IP and (V)RP depends on if your steerpoint is the target or not. A large motivation for selecting and utilizing one more or the other is the value in updating aircraft position data prior to an attack to counter accumulated INS drift. Because of GPS integration the need for position updates is reduced. Usually in Falcon you want to use VRP since steer will be target 99%.

For all computed pop ups I would run the data through WDP. There I enter ingress speed, alt, G, turn, and offset leg length and the calculator spits out the numbers. As with all weapon release profiles it’s proper to find the best release parameters and work backwards.

The “sighting rotary” is selecting which sub-point is your DMPI for attack/CCRP cues. Despite the common use of RP/PUP/OA1/OA2 for maneuvers they are just simple tools in your toolbox and it’s possible to deliver weapons to any of them. It’s perfectly acceptable to bomb OA2. The “WDP way” is for I/RP and PUP to form your baseline pre-pop axis. The goal is to fly through I/RP aimed at PUP. Passing the PUP you point at OA1 (if that requires a change of azimuth depends on the profile). Passing OA1 follow the attack cues to aim at target. OA2 can be placed below OA1 vertically at the PUP elevation or at the calculated AOD for the post-pulldown dive. As always this is one use of generic tools and not the only way, but it is a good one.

Generally switch to CCIP for increased accuracy only once you have aligned on the final attack heading, tally’d the target, and no longer need the attack cues.

Good documentation can be found here: http://www.weapondeliveryplanner.nl/download/index.html especially “Manual WDP version 2.0”

[Frederf]

This post is deleted!

[Snowman]

I would advice reading the manual of wdp. It describes the popup

[Dee-Jay]

Computed pop-up attacks: when, where, how, and why?

http://www.weapondeliveryplanner.nl

IIRC, There are manuals explaining almost everything about pop up attack.

[DarkFib3r]

Hehe, reading the WDP manual is a FANTASTIC idea - it looks like it goes into ALL the gory details of pop-ups. I thought I had looked at the WDP manual, but all I looked at was “Working with the DTC” and the NavOffsets section, which obviously didn’t give me the information I was looking for.

In addition to Fred’s helpful post, I’ll devour this material and I am confident that I will be competent at computed pop-up attacks in no time. Thanks all!

[Blu3wolf]

So, Ive noted something interesting about the offset aimpoints and VRP/VIP sighting modes. All of these markers have a set altitude, which can be changed in the pit via the upfront controls. Interestingly, these altitudes are all AGL, rather than AMSL. Seems like a bit of an oversight? Is the DTS meant to be implemented in the future?

[Frederf]

I don’t think they are AGL or ASL but relative to the height of the referenced steerpoint? So steerpoint is elevation 500’ and OA1 is +200’ it is 700’ ASL by addition. At least that’s how it should be if these symbols were designed to fly airshows around the target area.

[Blu3wolf]

This post is deleted!

[Blu3wolf]

@Frederf:

I don’t think they are AGL or ASL but relative to the height of the referenced steerpoint? So steerpoint is elevation 500’ and OA1 is +200’ it is 700’ ASL by addition. At least that’s how it should be if these symbols were designed to fly airshows around the target area.

I’ll test this again and report my findings.

[Dee-Jay]

Unfortunately, steerpoint elev in DED is not correctly implemented. The steepoint elev in DEST page should be the ground elevation at steerpoint (not the planned flight level) and MCC/FCC should use this elevation to compute OA VIP VRP elevation …

[Red Dog]

you don’t need to compute popups

all you need is a profile with the following:

• action point (distance)
• climb angle
• pull down altitude (AGL)
• Apex altitude (AGL)
• PRA= Planned Release Altitude (AGL)
• MRA= Minimum Release Altitude (AGL)

http://www.viperdrivers.org/forum/blog.php

Make a few profiles on paper for some typical profiles and use them whenever convenient

[Blu3wolf]

@Dee-Jay:

Unfortunately, steerpoint elev in DED is not correctly implemented. The steepoint elev in DEST page should be the ground elevation at steerpoint (not the planned flight level) and MCC/FCC should use this elevation to compute OA VIP VRP elevation …

This was what I thought was the case.

[Frederf]

@Blu3wolf:

I’ll test this again and report my findings.

I think about it again and if it says “elevation” then it should be altitude. If it was a vertical offset from steerpoint it would use language like that. AGL makes no sense at all.