Maverick issue
-
15 miles is far out for a mav shot especially at 15k. I like about 7 miles at 7k, and about 5deg nose down at Mach 0.8…or so… good luck to you, hope you have success soon.
-
There are quite a few solid pointing cross requirements:
1. Seeker side-look angle (10° radius circle plus the keyhole extra area)
2. 30° bank
3. 30° bank change since track started*
4. 30°/s bank rate
5. Good track quality (minimum pixel size, range, contast)
*may not apply BMSAutomatic boresight correlation (ABC) is kind of a bypass of PRE/VIS as it is a process triggered by the TGP. When you use ABC you aren’t really doing either PRE or VIS. Not sure how possible ABC is to trigger in BORE as you can’t SOI TGP in pre-designate and I think in all three modes post-designate you can’t ABC.
Make sure you’re in the range gate as well. 10-12nm is quite far. Usually the seeker limits track inside the kinematic (bracket) range.
As always make sure you’ve boresighted all stations you want to ABC handoff. Otherwise it will likely fail handoff or less likely get handed off to the wrong target. Mavericks are surprisingly picky about launch conditions and track quality. It’s usually best to get as familiar as possible with them in the simplest delivery mode (BORE) before progressing to PRE and/or VIS and lastly to ABC. Each step up the complexity chain builds off the familiarity of the last.
-
I’m sure someone with a higher pay grade will correct me… I’m pretty sure PRE should be used with boresighting… if you want to switch to WPN as SOI you may need to forego the TGP. Losing the benefit of the system. Have never tried it… I use the handoff exclusively since it’s the new paradigm of Mav employment. Even in VIS and BORE modes the TGP is used to fine tune your final target acquisition.
You should boresight when using mavericks. If you do not boresight in VIS mode, the issue will be that the range indication may be incorrect, and the location of the TD box and the mav seeker LOS will not be coincident. If you do not boresight in PRE mode, the issue will be that the range indication may be incorrect, and the location of the mav seeker LOS will not be along the area pointed by whichever sensor you are using (TGP or FCR).
This may not be such a big issue, and as such not boresighting may not be a problem. Its hardly a big deal to actually accomplish though, so its worth doing for each station anyway.
-
What was your first target and what was your second target?
If your first was a building and your second a mover or an irregular shaped object - Radar antenna that sort of thing, I would say you DO need to get in a lot close to kill movers and irregulars that you do a nice slab sided building.
As a rule of thumb with “D’s” half your Angels is a good range in Nm’s for you to get a lock - but see above comments also.
“G’s” have longer range than “D’s” so about 2/3rds of Angels to Nm’s is about right.
At extreme range there is more chance of a “flasher” just as you decide to hold down the pickle button - that’s annoying when it happens, so get well inside the bracket if you are not under threat before you pickle with a solid cross obviously.
Ironman
-
I see that so many people have problems with Mavericks.
I also wasted some of them at the beginning. Now i am able to fire them without wasting them.There are 3 most important things:
-Don’t be too far . If your mavericks fall short, you can tell it by looking at external weapon wiev, you are too far from target.
-Maintain stable flight, reduce bank rate to minimum, this is very important in BMS.
-Don’t fire off boresight, off boresight MAV is always wasted MAV. Different variants of MAV have different acceptable seeker angles at launch.If you fire off boresight or when you are not in stable flight your missile will fire but won’t guide on target, it will simply fly ballistic without any guidance.
Its easy to screw the launch, but with a little experience you will become tank buster.
-
Here are my top tips for successful Maverick employment:
- Read Chapter 3.2 in the TO BMS1-F16CM-34-1-1 manual to understand limitations, functions, capabilities and procedures.
- Read Mission 13 in the BMS-Training manual before/as you fly training mission 14 to put what you’ve learned into practice.
- Practise until you become proficient enough to avoid tunnel vision and be more aware of what else is going on around you.
For example if you are within operational limits and in range you will have a stable weapon pointing cross; if you don’t know what those limits are how do you expect to be able to reliably use this missile?
-
The issue appears to be backward actually its in close that I can’t get a lock at max range its fine actually. Also I tried that same thing in 4.32 and the it still happens there as well. At max range on the indexer I have a stable shot and get hits. Less than half range on the indexer and its very tough to get a lock. I am going to try switching to vis when I go to lock it and tgp handoff. Also the sensor I am using is the weapon page view from the maverick. I lock the fcr on one of the line of tanks, then when I can see the tanks enough to lock I lock one up. Once I am at max range on the indexer I fire then try to lock another to the tank next to one I shot at, and most of the time I can’t get a stable shot. As a note I am using D’s on the triple racks and my targets are tanks. I would also note with the triple racks I can only uncage 2 at a time. I can’t cycle to the others in the rack. I will also try without the triple racks to see if that is a factor in getting a stable shot.
-
NB - 2 points -
1. a triple rack is not found in a RL combat situation
2. you cannot uncage 2 on the same triple rack as the racket motor from the first launch with “blind” the sensors on the second one on the same rack.You may well find that movers coming towards you or adjacent to your line of flight are easier to lock than those going away from you - they throw up a “dust” cloud that obscures the target lock.
MAVs are not an easy option in 4.33 as they are not in RL - use them for “surgical” stand off strikes with “hand off” mode - the 4.32 days of 6 for 6 in a single pass are long gone !!!
Ironman
-
LMAVs work best for tanks IRL…wish we had those in BMS.
-
The issue appears to be backward actually its in close that I can’t get a lock at max range its fine actually. Also I tried that same thing in 4.32 and the it still happens there as well. At max range on the indexer I have a stable shot and get hits. Less than half range on the indexer and its very tough to get a lock. I am going to try switching to vis when I go to lock it and tgp handoff. Also the sensor I am using is the weapon page view from the maverick. I lock the fcr on one of the line of tanks, then when I can see the tanks enough to lock I lock one up. Once I am at max range on the indexer I fire then try to lock another to the tank next to one I shot at, and most of the time I can’t get a stable shot. As a note I am using D’s on the triple racks and my targets are tanks. I would also note with the triple racks I can only uncage 2 at a time. I can’t cycle to the others in the rack. I will also try without the triple racks to see if that is a factor in getting a stable shot.
With TGP ABC handoff you never touch the WPN format. It’s never SOI. You point track TGP, monitor the handoff, verify good parameters on the WPN format and fire. Repeat. You aren’t really using PRE or VIS with TGP ABC. You’re in a mode about to use it but ABC is performed instead.
Slewing the Maverick has a difficulty proportional to how far the FPM is to the target.
Assuming your second missile is tracking successfully but the pointing cross is flashing then I’d have to see it to get a clue why it might not be going solid pointing cross.
-
NB - 2 points -
1. a triple rack is not found in a RL combat situation
2. you cannot uncage 2 on the same triple rack as the racket motor from the first launch with “blind” the sensors on the second one on the same rack.You may well find that movers coming towards you or adjacent to your line of flight are easier to lock than those going away from you - they throw up a “dust” cloud that obscures the target lock.
MAVs are not an easy option in 4.33 as they are not in RL - use them for “surgical” stand off strikes with “hand off” mode - the 4.32 days of 6 for 6 in a single pass are long gone !!!
Ironman
Depends which F-16.
-
This post is deleted! -
Blu3wolf - do tell.
-
HAF jets have TERs for the mavs.
-
TERs are for bomb, launchers are for MAVs
MAVs are fired from the rail, not by ejection.
Triple launcher for MAV is LAU-88. -
LMAVs work best for tanks IRL…wish we had those in BMS.
Why don’t we? Wouldn’t it be as simple as just changing the sensor type in the editor?
EDIT: And now that I think of it, wouldn’t the same method be relatively easy to use to implement the APKWS in BMS?
-
And for bonus points Im sure you can remind me, the proper designation for the mounting piece to the LAU-117/A which is common with the LAU-88/A and LAU-88 A/A ?
You knew what I meant by TER.
-
Why don’t we? Wouldn’t it be as simple as just changing the sensor type in the editor?
EDIT: And now that I think of it, wouldn’t the same method be relatively easy to use to implement the APKWS in BMS?
What I don’t know (not being that BMS savvy yet) is if that sensor type is even implemented, but it would be a fairly easy hack for the devs to base it similar to an LGB…I think. Other than the symbology…which would have to be coded to look like an LMAV.
But now that we can buddy lase LMAVs would be pretty cool to have in our virtual arsenal.
-
And for bonus points Im sure you can remind me, the proper designation for the mounting piece to the LAU-117/A which is common with the LAU-88/A and LAU-88 A/A ?
You knew what I meant by TER.
…sounds to me like BMS shouldn’t allow loading triple MAVs at all, from this - given “The newest Mavericks are not compatible with the LAU-88”:
http://www.globalsecurity.org/military/systems/aircraft/systems/lau-88.htm
-
AGM-65A, B and D are far from being “newest Mavericks”.
A and B are old, they have EO system that predates CCD and CMOS. They used vaccum tubes much early TV cameras.
D is newer, it allows for boresight, it has IIR sensor, but its still not newest.
Well, even G is not the newest, its quite modern but not newest.When they say newest, they probably mean K variant. It has CCD seeker, but its penetrator one so it cannot be carried on 88s.
New HEAT one are probably H, they have CCD seeker, in DCS-A-10C they can be carried on 88s, not sure if they can be IRL.
Those 2 variants mentioned above do not exist in BMS.