|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| Griffin |
Posted - 10 May 2015 : 22:42:36
Flight leads in this Sunday's official campaign mission, "Strong DPRK 7" (Veiland, Floyd, Sharpe and Ironman) are requested to post a debrief of their flights actions, including any lessons learned or that should be learned by others.
Please put the following information at the top of your post:
Flight Role: (SEAD, ESCORT, STRIKE, Etc..)
Callsign11: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign12: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign13: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Callsign14: "Pilot's name" AA=X AG=X RTB,MIA/KIA,EJT
Mission Outcome: MS/PS/MF
|
| 5 L A T E S T R E P L I E S (Newest First) |
| Poppy |
Posted - 19 May 2015 : 14:30:31
I got shot down in the initial fight in the grinder, extending 10 seconds after you went cold, to protect your grinder egress because a bandit was close. When turning discovering a bandit at angels 40 at 8 miles on the nose. Couldn't lock him up because my antenna was not slewed to that altitude. I was looking low. And AWACS did not help :(. So when I did lock him up, fired a slammer, he fired as well and we both got shot. This left you as a three ship.
Next was Zipgun to get shot in the second engagement. After rejoining on Sharpe's right wing north of the flight path.
The bandits did not engage until we engaged them, but this we could not have known on the onset of the engagement. And with regards to flight management, you employed your element to take tactical lead on both grinders which was good. And you have a wingman (me in that flight) that you can put to use as well while staying back.
So even though you have lead, you can put yourself in a no.4 position when engaging and getting your 4 fighters to get into it. Worked well in my opinion. So being no.1 in the flight does not mean you have to be the first engaged/engaging fighter in my opinion. So excellent lead and PC in my opinion.
Poppy |
| Sharpe |
Posted - 18 May 2015 : 09:40:47
Ironman,
I was expecting Skal to post the debrief for Green Flight. However I will add some thoughts to your notes above:
1) Don't beat yourself up you did a fine job as PC.
2) You had a choice to make with those first threats: Notch or attack. Given your position relative to the whole package I might have hook turned away and diverted the package further south and fried to slip past or fight as a whole package. But the fact is you did at least make a decision and your decision was a measured one - the is no harm in this.
3) My flight getting mugged over the target was exactly that - a mugging. There ain't much me or anyone else could have done about it.
4) For me, the learning point for this one is all about the mission planning. We now know that while they will passively lock you the enemy tend not to engage if you are a) feet wet and/or b) about 40-50nm away and not on an intercept course - we know all this now, but with the exception of taking our flight path right along the south (bottom) part of the map at the planning stage there wasn't much we could have done different.
5) That mission was crucial to starting to reduce the enemies air assest availability. Heavy losses were the price that was paid but the net effect was worth it. Think this doesn't happen in real life? Read about 'Package Q'.
-Sharpe
 |
| Ironman |
Posted - 11 May 2015 : 17:31:22
Viper 1 – Escort
Ironman 3-0 Eject
Poppy 2-0 Kia
ZipGun 1-0 Eject
Tank 1-0 Kia
The take-off was disrupted, so my intention was for Viper 1 to rally at Stp 2 with the rest of the group, Viper 1 would enter a left hand wagon wheel 30deg of bank.
On route to Stp 2 we spotted a group of jamming contacts to our north – I dispatched 2nd element to investigate. They were spiked so I decided that element 1 would support and set up a grinder – which we did. I informed Shape and he, very correctly, informed me that he was unable to support.
My rational for the decision to take on the hostiles and let the strike force continue with their full complement of escort fighters was as follows:-
1. My element was being spiked, contact about 35 miles out, and we know from Sharpe’s training that is a Mig of this type spikes you there is a high probability that he has sent at least one mad dog after you – you won’t know that until it goes active and pops up on your RWR as “a missile from nowhere” which gives you about 10 seconds to get out of dodge.
2. I did not want to disengage from the Migs once we had entered the fight as to do so would drag the Migs into the path of the oncoming package, which as you will recall were hampered for both speed and manoeuvrability by the heavily loaded strike force.
3. The job of the Escort is to keep the bad guys away from the strike force – which we did – albeit at some cost, I haven’t checked the ACMI yet but I think we lost one plane in the initial fight – Poppy can you check please.
4. I handed off PC to Sharpe as Viper 1 was by now engaged with other contacts so we were a bit busy to be honest.
5. I did NOT Red flag even after both Viper and Cobra suffered heavy losses – because the strike flight still seemed confident that they could complete their mission, which they did.
6. Viper 1&4 bugged out at Winchester and were caught trying to get feet wet on route to RTB.
7. Two of the Cobra flight were mugged by ground hugging Migs.
For anyone aspiring to be a PC in the future I would point out that it has taken me 15 mins to type this – in the big chair you will be lucky if you get 15 secs to accumulate – formulate – hand off – act – and try to stay alive ho yes and try to shoot down the bad guys …. Best of luck with that then ;0)
I think it only fair to state that my “style” of PC was very evident last evening – in so much as - I will throw pilots into harm’s way, but not recklessly, while ever there is a realistic chance of getting the job done. So if I get to sit in the big chair again you will know what to expect.
Having said all that – I thoroughly enjoyed it last night and despite the other options discussed afterwards and the heavy losses I do think we made a positive impact on the overall situation.
Ps. Not all my reports will be this long but I felt that some issues needed to be addressed.
 |
| Floyd |
Posted - 11 May 2015 : 16:12:37
Flight Role: SEAD Escort
Serpent11: "Floyd" AA=1 AG=2 RTB
Serpent12: "Griffin" AA=2 AG=2 RTB
Mission Outcome: MS
Our task was to fly SEAD escort and destroy the two
SA-2 sites over the air bases. #2 attacked the site
at Kwangju while #1 continued north with the escort
to attack the second SA-2. While getting close we've
encountered bandits, so #2 was ordered to take a shot
at Kwangju search radar and help with A2A (shot down
two SU-30). #1 destroyed the SA-2 radar at Kunsan.
RTB was uneventful because we've kept a safe distance
to the CAP flights over the south coast. |
| Veiland |
Posted - 11 May 2015 : 10:02:00
Flight Role: OCA
Panther11: "Veiland" AA=0 AG=3 RTB
Panther12: "Elmo" AA=0 AG=3 RTB
Mission Outcome: MS
Were tasked with attacking runways at Kwangju and Kunsan. We decided to take one airbase each, as to not risk loosing both aircrafts on first target.
Combination of 6xDurandals + 2x600gal tanks made us very heavy, so we were struggling to keep up.
Of the coast of korea Viper flight dealt with a hostile CAP (taking losses in the process) and we diverted to the back of the package until situation was resolved.
50nm from our first target (Kwangju), and after area was anounced safe by SEAD, 2 peeled off to attack, but immediatly after escort picked up contacts over the airbase. Again we kept clear while this was being dealt with by escort (again taking losess in the process)
2 then succesfully destroyed 3 segments of the runway, and we continued to Kunsan where again we picked up enemy aircraft. These were in the process of landing, and I believe one were shot down while the rest ran off to the north (this time with no friendly losses)
Runway was attacked by 1 destroying 3 segments. No manpads were launced but I did receive a hefty amount of ground fire upto 23mm.
Flight home was uneventful.
|
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
