|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| Vosene |
Posted - 06 Jul 2014 : 18:57:01
Flight leads in this Sunday's official mission, "Sub Hunt Revisited" are requested to post a debrief of their flights actions by Tuesday, 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
 |
| 7 L A T E S T R E P L I E S (Newest First) |
| Elmo |
Posted - 13 Jul 2014 : 10:08:32
Flight Role: SEAD
Mako11: "Elmo" AA=0 AG=1 KIA
Mako12: "Veiland" AA=X AG=2 RTB
Mako13: "Griffin" AA=X AG=X RTB
Mako14: "Floyd" AA=X AG=X RTB
Mission Outcome: MS (I think we achieved a success as aircraft were only shot down by air to air however we did not make it to the target so not sure if that actually counts?)
I got shot down so early in the flight and didn't take down the final scores so not sure what the other pilots in the flight managed to kill.
We took off and took a bit of seperation to the West due to know Su-27 in the area. First phase was to take out the SA-2 and SA-4, unfortunately the SA-4 did not become active on first pass into threat area, numbers 1 and 2 got shots off on the SA- and SA-5 which were destroyed but unfortunately for me being heads down was not concentrating on the air threats and didn't realise how close we had got, cant even remember even hearing a lock tone but then had a missile inbound which ultimately took me down and so do not have any more details for the rest of the flight.
Lesson learnt in that situation is that at either myself or my wingman should have been monitoring air threats while the other person attacked the ground threats to ensure we did not get to close.
Elmo |
| Blade |
Posted - 10 Jul 2014 : 13:32:11
Oh if I was supposed to do that, here is the abstract I posted on our own forums. I filtered out tiger 13 and 14.
RECORD BEGIN TIMESTAMP 7/6/2014 23:08:58.
Game is Tactical Engagement type Networked
Mission name: Sub Hunt Revisited 20
Mission Type: SEAD Strike
Flight Unique Id: Tiger1
2 Ship Flight
Ac type: F-16C-52
Contry: U.S.
FLIGHT EVENTS
Event Bladewood joined as Tiger11 at 18:25:04
Event Elf joined as Tiger12 at 18:25:04
Event Elf exited from Tiger12 at 18:30:04
Event Elf joined as Tiger12 at 18:32:26
Event Elf exited from Tiger12 at 18:32:49
Event Elf joined as Tiger12 at 18:34:55
Event Elf exited from Tiger12 at 18:35:20
Event Elf joined as Tiger12 at 19:07:20
Event Elf exited from Tiger12 at 19:07:35
Event DPRK MiG-23ML downed by Bladewood at 19:10:01
Event DPRK MiG-29A downed by Bladewood at 19:10:57
Event Bladewood landed at 19:23:34
Event Bladewood exited from Tiger11 at 19:25:38
The plan was to clear out the air defenses at target area which consisted of 4 SA11 launchers, and 4 AAA battallions split over 2 locations with the notion of possible addtional popup threats. The idea was pretty straightforward. We could preplan the 4 SA11 launchers to be taken out with mavericks, which would be the task of #2, and #1 would look out for any popup threats. Also we planned to stay out of any a2a engagement as well as possible. However...
Immediately after getting into the pit, Elf seemed to have issues with his aircraft not showing the HUD, which multiple reconnects sadly didn't fix. Informing the package commander of this, it was decided to carry on anyway, using my HARMS and the now AI wingman to take out as many SA11 as possible.
The mission itself was carried out in sequential waves, pushing further into enemy territory by taking out several known BARCAP flights and air defenses en route. We were the second-to-last flight to arrive at the target area to clear it of enemy air defenses. The enemy air threats were better skilled than expected and several of the escort aircraft fell to enemy missiles. The major air defenses were eventually taken out, but the air was filled with enemy air threats when it was time to clear out the target area itself. The package commander at this point decided for a package-wide RTB during which I took out several air threats that were literally in my way. Made it back to base in one piece. |
| Griffin |
Posted - 09 Jul 2014 : 14:05:35
Just in case they don't get a chance to post here I thought I'd post our guests results.
AMVI - Diamond 1
11 Grape, AA=1, Ag=0, RTB
12 Lionell, AA=2, Ag=0, RTB
13 Tycho, AA=0, Ag=0, EJT
11 Falcrum, AA=3, Ag=0, EJT
401st - Tiger 11 and 12
11 Blade, AA=2, AG=0, RTB
12 Elf, TECH PROBLEMS
Thanks for sharing the celebration with us.
|
| Crowebar |
Posted - 08 Jul 2014 : 23:53:10
Flight Role: Close ESCORT
Tiger13:Crowebar AA=0 AG=0 EJT
Tiger14:Vosene AA=0 AG=0 CTD
Mission Outcome: MF
We spent most of the mission between steerpoints 2 & 3, between Knight & the air action. Had 1 call from knight for help as they were being spiked by mig-23's however these turned out to be no threat as they were Winchester.
#4 picked up some low level Mig-29's, but again these were being engaged by the escorts. But a few minutes later we had Mig-29's appear behind us on route towards knight flight, I turned to engage and got one missile off which missed, before being hit by a mig-21 to my rear. Almost simultaneously #4 had a crash to desktop. Endex for Tiger 13 & 14.
However all in all, an enjoyable mission.
|
| Vosene |
Posted - 07 Jul 2014 : 01:50:06
Plan
As the TE writer, I allowed about 30 minutes from departing Stp 2 for first aircraft in the package to get to the target with mediium defences.
There were 4 fixed SAMs, 3 of which could be destroyed while still feet wet. Only the SA-10 presented a challenge and with the right tactics it is a fairly easy to kill with a HARM. Given 8 HARMs in the SEAD escort, to punch a hole in the AD network to the target only required a 50% hit rate.
There were 2 BARCAPs that were pre-briefed, a 4-ship Su-27 flight at the FLOT and a 2-ship Mig-29s flight closer to the target. The only scrambled threat until 1905 was a 4-ship of MiG-23 with semi-active weapons only. Against these 10 aircraft I planned for 2 dedicated escort flights (8 ac) and a swing role SEAD (4 ac).
Lessons
Although the package eventually became overwhelmed and had to abort this is primarily down to not clearing a way to the target quickly enough as the briefing also made it clear other threats would be scrambled to intercept.
Given the degree of pre-briefing on the threats and the structured nature of the mission plan I anticipated that a human AWACS would not be required. In hindsight I was wrong. With multiple Sqns joining the mission who are not used to operating together, a human AWACS would have added significantly to SA with regard to vectoring aircraft onto threats, ensuring mutual support, providing a better overall picture and confirming when AD assets were down. For future large scale TEs we should always have a human AWACS.
A misunderstanding about instructing the AI aircraft to RTB reduced Lightening 1 to a 2-ship. I have posted clear direction about when AI should be told to RTB in the members area.
We once again lost aircraft due to not honouring the MAR!
Other Points
Great work by Zipgun in staying alive against 3 MiG-23's in a furball, and even exhausting all of their missiles!
Great job by Sharpe as the package commander after giving the abort in co-ordinating the RTB and proving the BARCAP to ensure most aircraft managed to RTB.
Huge thanks to members of the AMVI and the 401st for joining us tonight to celebrate our 15th anniversary.
|
| Zipgun |
Posted - 06 Jul 2014 : 23:59:59
Lightening1: Escort
Mission Outcome: MF
Lightening11: Zipgun AA:3 AG:0 (RTB)
Lightening12: Ironman AA:0 AG:0 (EJC)
Lightening13: AI AA:0 AG:0 (RTB)
Lightening14: AI AA:0 AG:0 (RTB)
I didn't know we were supposed to keep our AI aircraft, it might have gone better with some extra missiles.
We approached our 2nd push point (STP-3) and saw Diamond/Mako were engaged with Migs, so we turned south to wait until they were "Open Sesame"... the battle got drawn out and MIG-23s were now inbound. I turned our flight to cover the right flank, but Ironman caught one in the back and was in the silk. I did the furball dance with the remaining MIGs to keep them occupied (I had run them out of missiles) and then proceeded towards the target - dragging them along. The MIG-29s near the target were engaged and I was low on fuel and spears, so I turned back and killed a few on the way out. Called Winchester/Bingo and RTB'd. |
| Sharpe |
Posted - 06 Jul 2014 : 22:50:25
Knight 1: Deep Strike
Mission Outcome: MF
Knight 11: Sharpe AA:2 AG:0 (RTB)
Knight 12: Sabre AA:0 AG:0 (RTB)
Knight 13: Jack AA:1 AG:0 (RTB)
Knight 14: AI AA:0 AG:0 (RTB)
Departed as planed and held at STP 2. Struggled to make out clear picture or code words and eventually (and cautiously) declared code word 'OPEN SESSAMI'.
Arriving at STP3 it was clear that the air picture was against us. After waiting some time to see if the escorts/SEAD could fight through, it became clear that the probability of getting to the target was slim. We got bounced by multiple packages (in particular MIG23's). Called for a delouse on top of STP3 while we tried to get away. Sharpe got a kill as we turned away towards STP8.
At this point Sharpe called a package wide ABORT and used Knight flight as a BARCAP while the rest of the package egressed. All of Knight flight got missiles off the rail at various targets and then turned away for base, calling in support from AWACS, who sent F/A18's to support.
Thence RTB without incident.
Notes on the mission:
Comms: Not bad, but needed to be much better for such a complicated mission. As package commander I was expecting/hoping for updates on aircrafts status on the codeword phases but none came and it was very hard to get a clear update from flight leads.
SEAD+Escort: Seemed to be very slow to engage and clear SAM's/airspace, I think this bogged down the whole package, which in turned gave time for enemy forces to converge on our position, making matters worse.
Language barrier: I would like to put a massive thumbs up in the direction of those that joined up from various other VFS's. Not only did they fly with us using a second language but also while not being familiar with 185th SOP's. While the respect level for those pilots can't be high enough, it also makes life a little bit harder in missions and the more complicated the mission the harder it becomes to react to it all. So yes, it did make life more complicated but that is to be expected - well done guys-.
-Sharpe
 |
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
