CCRP bombs not dropping and the one time they did miss
-
Kinda crazy 4 times now. First time cbu87 flat level steady 20k; no drop. 2nd time GBU10 miss long third time MK84 no drop. I tried slightly pulling up nose, push down nose, briefly let pickle button off then back on…Ready to scream!
target locked looking good GBU10
bombs miss
target radar still there
target at 27 miles good lock in GM EXP
Target lock CCRP 2-MK84
everything perfect holding steady on release button…then no drop forcing me 4 times to go CCIP and get shot down each time. Not fun
Sorry just needed to vent my frustration
-
WRT to the GBU-10, you’re in Training mode for the Laser (see HUD, it says ARM T). You need to change laser to combat (CMBT) mode via ICP List - 0 - 5 iirc.
As for the dry run with CBU and Mk, I can only guess, but as far as I know, CCRP has a built-in “acceptable area for release” and deviation left/right from that sweet spot will result in the bomb not releasing. Since CBU’s and Mk’s are just dumb freefall bombs, I assume the acceptable region at such high altitudes has to be VERY small, as a deviation by only 1 degree might deliver the bomb maybe several hundreds of feet away from target?
-
Be aware that LGB have “3/9” type release constraint which is more permissive than typical dumb bomb. If you fly with a huge lateral error the bomb comes off the rack anyway when the solution plane is crossed. It is up to the pilot to ensure that the miss is not too much. I believe the F-16 dumb bomb release constraint is the size of the FPM circle roughly.
The last picture posted looks like you still have :11 to go. Be also aware that the countdown and cue will drop twice when approaching the target, once to show you’re in max loft range and again for the current release parameters.
-
Thank you for that Eagle-Eye let me try that one again. Yeah in r/l hitting a small radar with MK84 at 19k is almost impossible I would think let alone cluster munitions. I resorted to good old Mav-G and got it
The one other issue I regularly experience is harm shots running true then just before impact and with plenty of airspeed from 45 down to 20 miles simply disappearing like one did again just now
-
I overflew the target there as the bombs didn’t release hence I made another run.@Frederf:
Be aware that LGB have “3/9” type release constraint which is more permissive than typical dumb bomb. If you fly with a huge lateral error the bomb comes off the rack anyway when the solution plane is crossed. It is up to the pilot to ensure that the miss is not too much. I believe the F-16 dumb bomb release constraint is the size of the FPM circle roughly.
The last picture posted looks like you still have :11 to go. Be also aware that the countdown and cue will drop twice when approaching the target, once to show you’re in max loft range and again for the current release parameters.
-
Be aware that LGB have “3/9” type release constraint which is more permissive than typical dumb bomb. If you fly with a huge lateral error the bomb comes off the rack anyway when the solution plane is crossed. It is up to the pilot to ensure that the miss is not too much. I believe the F-16 dumb bomb release constraint is the size of the FPM circle roughly.
The MMC will inhibit release if the lateral error exceeds 1,500 ft, IIRC. Its relation to the FPM circle (an angle in mils) depends on your altitude.
The last picture posted looks like you still have :11 to go. Be also aware that the countdown and cue will drop twice when approaching the target, once to show you’re in max loft range and again for the current release parameters.
This seems like a likely error given the screenshots.
Thank you for that Eagle-Eye let me try that one again. Yeah in r/l hitting a small radar with MK84 at 19k is almost impossible I would think let alone cluster munitions. I resorted to good old Mav-G and got it
The one other issue I regularly experience is harm shots running true then just before impact and with plenty of airspeed from 45 down to 20 miles simply disappearing like one did again just now
How far was your HARM from you? How far was it flying? Missiles have a max time of flight limit if I recall, as well as a deaggregation limit. If it flew several minutes to get there, or if you were more than 30 miles away from it, that could be the reason for it vanishing.
-
cptmtge: For CCRP bombs release, you need to press and hold pickle button 2s before release point.
I don´t think you should lock targets at GM/GMT MFD, instead use SOI at TGP(area or point track), because that will be your correct SPI. -
In the real airplane you can hold the WR button down a week before the solution and it’s fine. BMS the simulation historically has been a little funny/buggy with long duration WR holds. I don’t know if that was ever fixed so keep the WR holds relatively short, 1, 2, 3, 4 seconds. I bet I could hold down WR for 10-20 seconds and not encounter an issue but when troubleshooting that’s one technique fix to make.
Locking the radar FTT/MTT isn’t required for CCRP but it shouldn’t harm the process either. It might be worth it to try other methods for determining SPI, unlocked FCR, HUD TDC, TGP in area just to narrow down the behavior.
HARMs have I think a 200 second lifetime. Significant turns takes ages like HAD over-the-shoulder shots and can eat up the clock even at short range.
Difficulties in getting a release with CCRP are often some sort of lateral aiming error. I do find that a dive, even a shallow one significantly reduces the chance of inhibit. That being said CCRP should not be difficult for almost any delivery geometry. Hopefully you can take 12 BDU-33s to the range and have 12 successful deliveries ranging from easy to complex. Please keep sharing if you continue to have problems getting releases with dumb ordnance in CCRP.
For LGB like GBU-12 it’s important to verify that terminal guidance is occurring at all. The most positive verification that I know of is to check the bomb in external camera (Shift-7) and watch it. Before laser guidance the bomb should fall smoothly and during laser guidance the wobble tracking the laser should be very noticeable. There are half a dozen ways to screw up laser guidance, masking the laser, being the wrong wavelength, being the wrong laser code, not configuring for automatic lasing or failing to manually lase. Before worrying about LGB misses it’s important to confirm that any laser guidance is taking place.
-
In the real airplane you can hold the WR button down a week before the solution and it’s fine. BMS the simulation historically has been a little funny/buggy with long duration WR holds. I don’t know if that was ever fixed so keep the WR holds relatively short, 1, 2, 3, 4 seconds. I bet I could hold down WR for 10-20 seconds and not encounter an issue but when troubleshooting that’s one technique fix to make.
Locking the radar FTT/MTT isn’t required for CCRP but it shouldn’t harm the process either. It might be worth it to try other methods for determining SPI, unlocked FCR, HUD TDC, TGP in area just to narrow down the behavior.
HARMs have I think a 200 second lifetime. Significant turns takes ages like HAD over-the-shoulder shots and can eat up the clock even at short range.
Difficulties in getting a release with CCRP are often some sort of lateral aiming error. I do find that a dive, even a shallow one significantly reduces the chance of inhibit. That being said CCRP should not be difficult for almost any delivery geometry. Hopefully you can take 12 BDU-33s to the range and have 12 successful deliveries ranging from easy to complex. Please keep sharing if you continue to have problems getting releases with dumb ordnance in CCRP.
For LGB like GBU-12 it’s important to verify that terminal guidance is occurring at all. The most positive verification that I know of is to check the bomb in external camera (Shift-7) and watch it. Before laser guidance the bomb should fall smoothly and during laser guidance the wobble tracking the laser should be very noticeable. There are half a dozen ways to screw up laser guidance, masking the laser, being the wrong wavelength, being the wrong laser code, not configuring for automatic lasing or failing to manually lase. Before worrying about LGB misses it’s important to confirm that any laser guidance is taking place.
Is the correct laser code needed? i thought it was just needed for buddy lasing?
-
yeah, laser code is needed for all laser guided munitions .
When you Buddy lase you set your laser code to your Buddy laser weapon code
When you guide your own bombs, your laser code need to match the UI weapon laser code -
If I set and save laser code in the cartridge that does it correct?
-
If I set and save laser code in the cartridge that does it correct?
The bomb ‘read’ code can be changed in the Loadout screen, for each jet …. or left as is.
In any case, your laser designator in the jet must set to the same code as the bomb AND in CMBT mode. You can do this manually via the ICP as noted above. I am not sure if this can be ‘pre-set’ on the DTC … if it’s possible, via Weapon Delivery Planner, I guess.
-
SA10 25 miles. I perform a pop up Harm attack
then poof gone…weird
-
Hmm 28:28 to 30:30 is only 2 minutes 2 seconds. The missile should survive for at least 3 minutes. Perhaps it is self-detonating if the SA-10 radar stops radiating? It shouldn’t. Is the missile being shot by something?
-
See thats the thing and why I am posting this becase in weapon view the missile simply disappeared a couple seconds before impact and it happens frequently
-
Perhaps it is self-detonating if the SA-10 radar stops radiating?
May be the case… In my experience with 4.33, though we haven’t tested for it specifically, I have seen it happen in a few ACMI’s (not currently available to show) that air-air missiles just vanish when either the intended target, OR the shooter are destroyed.
Say I were to launch two missiles at another F16, and just a few seconds before he is destroyed he fires an AIM-120, my second and his first missile would self-destruct almost simultaneously to his aircraft being reduced to a ball of flames. This has lead to some situations were a missile was inbound for a 100% hit certainty, but because the shooter was destroyed, the target was saved.
-
@Red:
yeah, laser code is needed for all laser guided munitions .
When you Buddy lase you set your laser code to your Buddy laser weapon code
When you guide your own bombs, your laser code need to match the UI weapon laser codeI see thanks.
-
Don’t think so as the radar was still emitting and i was definitely alive. @Eagle-Eye:
May be the case… In my experience with 4.33, though we haven’t tested for it specifically, I have seen it happen in a few ACMI’s (not currently available to show) that air-air missiles just vanish when either the intended target, OR the shooter are destroyed.
Say I were to launch two missiles at another F16, and just a few seconds before he is destroyed he fires an AIM-120, my second and his first missile would self-destruct almost simultaneously to his aircraft being reduced to a ball of flames. This has lead to some situations were a missile was inbound for a 100% hit certainty, but because the shooter was destroyed, the target was saved.
-
Falcon AFAIK doesnt have provisions to allow missiles to get shot at. Its one of the things they want to improve for naval ops in particular.
Sent from my SM-N910G using Tapatalk
-
yes I have never seen any missile of any type intercepted by another