[[1147.49] BMD issues w. the SAMP/T NG & TBM targets

[LetMePickThat]

Hi all,

I'm experimenting a TBM engagement with the SAMP/T NG GBAD system, using the Ground Fire 300 radar and the Aster 30 Block 1NT interceptor. The targets are three Scud B fired at close to max range, at targets in the vincinity of the SAM site.

Issue #1 (BMD_test_2): The GF300 is unable to pick up the targets until the interception window has already closed (first detection by the radar occuring at ~13nm from the SAM site). The first sensor to detect the RVs in this scenario is the good ol' Mk.1 eyeball, it was thus removed from the SAM Bty to only have radar detections. The GF300 should be able to pick up, track, classify and generate engagement data for TBMs even in rotating mode (MRBMs should be trackable in cued mode, using an external EW radar, but that's beside the point of this test).

Swapping the GF300 for another, more common BMD radar (the AN/SPY-1B) results in much earlier detections (150nm from the SAM site). Obviously, the AN/SPY-1B is much more powerful than the GF300, but there should be a happy medium between 13nm and 150nm. For comparison, the AN/MPQ-65 on the Patriot PAC-2/PAC-3 ERINT SAM Bty detects the targets at 65nmn, despite having a shorter maximum range (and, likely, a lower peak/average power rating).



Issue #2 (BMD_test_3): Testing with the AN/SPY-1B instead of the GF300 results in good tracking of the targets. However, two of the three RVs are not engaged ("Unable to intercept ballistic target before it impacts.") despite the engagement geometry making such interceptions possible.

BMD_test_2and3.zip

(22.24 KiB) Downloaded 5 times

[AceOfSpadeszzzzzz]

Haven't taken a look at the save files yet but maybe the missile is beyond maximum elevation angle?

[LetMePickThat]

Haven't taken a look at the save files yet but maybe the missile is beyond maximum elevation angle?

If that's the case, it's a DB error. The Aster 30 is fired from vertical canisters, there is no maximum elevation angle.

[AceOfSpadeszzzzzz]

Haven't taken a look at the save files yet but maybe the missile is beyond maximum elevation angle?

If that's the case, it's a DB error. The Aster 30 is fired from vertical canisters, there is no maximum elevation angle.

Oh sorry I mean the elevation of radar.

And for the aster 30 issue, normally missiles with a KKV can only engage targets that are above 100km. In your case the targets are already below 100km.

[LetMePickThat]

Oh sorry I mean the elevation of radar.*

The GF300 can scan from -20° up to 90°. There is no max elevation or blind spot.

And for the aster 30 issue, normally missiles with a KKV can only engage targets that are above 100km. In your case the targets are already below 100km.

The Aster 30 is a hit-to-kill missile, but it does not use a KKV. The PAC-3 ERINT/MSE and David's Sling's interceptor also use that approach. If that was the issue though, swapping the GF300 for the AN/SPY-1 would not solve it.

[AceOfSpadeszzzzzz]

Oh sorry I mean the elevation of radar.*

The GF300 can scan from -20° up to 90°. There is no max elevation or blind spot.

And for the aster 30 issue, normally missiles with a KKV can only engage targets that are above 100km. In your case the targets are already below 100km.

The Aster 30 is a hit-to-kill missile, but it does not use a KKV. The PAC-3 ERINT/MSE and David's Sling's interceptor also use that approach. If that was the issue though, swapping the GF300 for the AN/SPY-1 would not solve it.

I see, so for the second one I don't have a clear answer, but for the first one maybe in game it's not up to 90. You can try to place some GF300 radar further behind to see if the missile could be detected.