T O P I C R E V I E W |
utopic |
Posted - 15 May 2016 : 21:45:12 TASK: AI
FLIGHT: Vosene Cowboy11: 0 AA 2 AG KIA Mango Cowboy12: 0 AA 0 AG RTB Utopic Cowboy13: 2 AA 2 AG RTB Veiland Cowboy14: 1 AA 0 AG RTB
RESULT: MF due to low hit ratio
On ingress, nothing interesting. Over the target area, Vosene broke the hard deck and got shot down by a SA3 or something similar.
Afterwards, I took command and continued the attack. When #2 was Dakota, he took over air cover until he ran out of fuel and RTBed.
Veiland started to engage AG once Mango was AA, and once he was Dakote he covered me until he was Bingo and RTB.
I engaged AG, but had trouble getting a solid cross, which in the end meant that for the 2 shots when I had a solid cross, I got hits. I then fired 3 MAVs with the blinking cross and missed, which was expected and returned with the last one.
Myself and Veiland also engaged enemy aircraft that got close, and had 3 kills between us, but enemy bandits were never a threat.
I would say good flight, with the exception of the bad performance of the MAVs. |
8 L A T E S T R E P L I E S (Newest First) |
Veiland |
Posted - 19 May 2016 : 12:23:49 quote: Originally posted by Vosene
quote: Originally posted by Fisty
I was under the impression that the flashing cross was a visual warning that your parameters aren't right. So if you bypass the warning by switching to wide view, that's all you're doing and your parameters will still be off and you'll miss. All you're doing is switching off the alarm without putting out the fire.
Your cross does not flash in narrow FOV, it does flash in Wide.
I'm just making people aware of this because if you don't know about it then you could easily believe you are within parameters in Narrow FOV because the cross is not flashing. By switching back to Wide FOV before firing you can check if the cross is flashing. If it is then clearly you need to adjust launch parameters before firing otherwise your Maverick will probably miss.

Ah thats what happened to me then. Was in narrow FOV and mistook the solid cross for a lock... |
Fisty |
Posted - 18 May 2016 : 17:42:04 Ah, sorry I misunderstood your post. Yes, that makes sense now. |
Vosene |
Posted - 18 May 2016 : 16:23:36 quote: Originally posted by Fisty
I was under the impression that the flashing cross was a visual warning that your parameters aren't right. So if you bypass the warning by switching to wide view, that's all you're doing and your parameters will still be off and you'll miss. All you're doing is switching off the alarm without putting out the fire.
Your cross does not flash in narrow FOV, it does flash in Wide.
I'm just making people aware of this because if you don't know about it then you could easily believe you are within parameters in Narrow FOV because the cross is not flashing. By switching back to Wide FOV before firing you can check if the cross is flashing. If it is then clearly you need to adjust launch parameters before firing otherwise your Maverick will probably miss.
 |
Fisty |
Posted - 18 May 2016 : 15:48:10 I was under the impression that the flashing cross was a visual warning that your parameters aren't right. So if you bypass the warning by switching to wide view, that's all you're doing and your parameters will still be off and you'll miss. All you're doing is switching off the alarm without putting out the fire. |
Vosene |
Posted - 18 May 2016 : 03:51:58 I don't know why it is worked for you Veiland. The BMS Dash 34 manual 4.33.1 Pages 161 and 163 specifically states that you can only Boresight with the B and D variant launcher and Handoff with the D and G variant Maverick. While I was able to follow the Boresight process it didn't work correctly as I did not get the Handoff in Progress or Avionics fault during Boresighting and, despite manually locking up the Maverick seeker head on the same target as the TGP and pressing BSGT I did not a get a proper correlation between the Maverick seeker head and the TGP picture and at no time did I get a target Handoff from the TGP to the Maverick seeker head once over the target area.
On the issue of the flashing/non-flashing cross, I found if the seeker FOV is set to narrow, for some reason you don't get a flashing cross even if outside of limits. If the seeker head is in narrow I therefore set it to Wide before engaging to make sure the cross is not flashing.
 |
Poppy |
Posted - 17 May 2016 : 17:57:54 2 things I can think of; 1) weapons are going to miss sometimes, no matter what you do. 2) I had trouble (also with D model) of getting a solid lock unless zoomed in on the WPN page. Plus the B is optical, so it is possible the missile is just not seeing the target, B's are more difficult definitely
Poppy |
Veiland |
Posted - 17 May 2016 : 12:06:58 Hmm, I had no problems with boresighting and handoff and had immediately solid cursor prior every launch, yet didnt hit anything (was all moving targets). At times it seemed I got solid luck even though I shouldn't (way outside keyhole) and this perplexed me some. Later tried B models again in a TE against stationary targets at KOTOR and had no problems. |
Vosene |
Posted - 16 May 2016 : 02:57:51 I would add that we engaged with the Maverick B (D variant was not available from the Tessera F-16 Sqn). Despite the good weather the sensor was unable to lock targets until very close and picking targets up without an IR seeker on the Maverick was difficult and TGP handoff is not available on the B model Maverick. These limitations led to me pressing below the hard deck to prosecute the target, my own fault I should have know better. I was hit by an SA-7 and SA-14.
I would recommend not flying with the B model Maverick due to these limitations.
 |