| Author |
 Topic  |
|
|
Zipgun
USA
521 Posts
Status: offline |
 Posted - 01 Jul 2016 : 15:51:27
|
This week's mission begins the task of reducing the troops in the buffer zone. A large breakout group of several battalions have begun moving toward our front-line positions. Our job is to weaken them as much as possible.
Python1 - 4 ship Interdiction Recommended MS= 16 total GRND kills (or 4/AC) PS= 12 (or 3/AC)
Serpemt1 - 4 ship Sweep MS= no losses to package from red air PS= no Python1 losses from red air
2 SA-11 launchers remain 30NM to the west, AAA and MANPADs are also present in the area.
More flights can be added as needed.
|
|
|
Vosene
United Kingdom
4594 Posts
Status: offline |
Posted - 03 Jul 2016 : 19:03:02
|
Flight Leads in this Sunday's official campaign mission, "185th Campaign Mission 4" 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
 |
 |
|
|
Fisty
United Kingdom
701 Posts
Status: offline |
Posted - 03 Jul 2016 : 21:00:47
|
Serpent 1
Flight Role: Escort
Callsign11: "Fisty" AA=3 AG=0 RTB
Callsign12: "Mango" AA=1 AG=0 RTB
Callsign13: "Vosene" AA=1 AG=0 EJT
Mission Outcome: MS
Good ingress and comms. Once we reached our CAP area, we quickly picked up a 2-ship SU30M escorting a 2-ship SU25 hot on the nose. Fisty and Mango sorted on the SU30s and although they killed them, they were forced defensive. Vosene then turned in hot to support, but unfortunately broke MAR and was shot down. Immediately after, Fisty and Mango found themselves in a furball with the SU25s and also at least 1 SU27, with another 2 groups of SU30s heading in from about 35 miles. At this point they requested Python 1 element to assist, who joined and deloused. Finding themselves low on ordinance, they were relieved to hear Miller Time from Python 1, so turned for Homeplate and Python Element rejoined their flight. A comfortable RTB and competent formation landing from Fisty and Mango.
|
|
|
|
Poppy
NETHERLANDS
1055 Posts
Status: offline |
Posted - 03 Jul 2016 : 22:35:12
|
Flight Role: AI
Callsign11: "Poppy" AA=1 AG=6 RTB
Callsign12: "Tank" AA=0 AG=0 RTB
Callsign13: "Zipgun" AA=2 AG=0 RTB
Callsign14: "Wildcat" AA=0 AG=0 RTB
Mission Outcome: PS
Ingress as fraged, struggling for the 12:14 ToT on push point.
On request of sweep we decided to strip element and support A-A. AI mission aborted for #3 and #4.
Lead element continued to with the AI, two runs in aborted due to A-A picture. Second run was radar snoozed at 200ft. AGL but
we still got picked up by 29 nails at 35mi. As per Chalis request we had a window to push for target which we did, egressed and comms 'Miller Time' we're sent.
On RTB, Second element was 15+ miles north of lead element and we deloused and regrouped.
Adjusting for fuel capacity we had changed the landing for 3,4,2,1. All RTB.
Two points: Sweep can drag back to push point (as per MAR). Second element was aborting AI based on Sweep being merged: second element was 40nm away when the call came:
best is to fall back, regroup, rejoin, and then start the fight again. As opposed to fighting your way out of a paper bag
https://www.youtube.com/watch?v=Dp2k5ThC4HA&ab_channel=824morris
Poppy |
|
|
|
Vosene
United Kingdom
4594 Posts
Status: offline |
Posted - 04 Jul 2016 : 03:04:44
|
To clarify on the Sweep first two engagements:
1st engagement - 2x Su-30M killed with 2x AIM-120B shots, 1 each from 1 & 2 with element supporting. During this engagement 2 broke MAR by not notching after firing and not turning cold. He was engaged by 3x R-77. 3 was supporting during this whole engagement and did not break MAR.
After the 1st engagement 3 had picture. There was no need for the entire flight to turn cold but best option would have been for first element to continue cold and let second element take the lead, thus maintaining element separation and mutual support. This didn't happen and the first element turned hot again with some 35nm to the next bandit groups and 7nm separation between the elements.
Su-25 group on right side was no factor so Element did not commit on it but called the group to Python1 for SA.
2nd engagement - Two left groups, 1x Su-30 and 2x Su-25 with a 3rd group of 2xSu-27 +20nm range.
1st element were now lower (A17 approx) and slower (M0.7) so broke MAR pressing on the Su-25 and Su-30 groups. After the Su-30 turned cold, No 2 fired the first Slammer B shot on one of the Su-25 (splashed) while No 1 continued hot on the Su-30, which led him right into the still hot Su-27 group.
Second element was forced to commit on the Su-27 group with No 4 firing at the left Su-27 when Lead was 9nm away from the hot Su-27 and No 3 engaging the right Su-27. Both of these shots were fired from inside MAR due to the lack of separation between the elements after the first engagement and the first element pressing inside MAR on their targets. The two 2nd element shots killed the 2x Su-27 but unfortunately one of them got an R-77 away that killed No 3.
Lessons -
As usual, don't break MAR.
Maintain formation integrity. As Poppy suggested, either the whole Flight could have turned cold, or the second element could have taken Lead after first engagement and first element re-positioned to regain SA and maintain separation.
Using aircraft system to increase SA to determine highest threat aircraft, which could have meant the entire Flight focusing on the Su-27 and Su-30 and ignoring the left Su-25 group, which was no factor.
|
|
|
| |
Topic |
|
|
|
| 185th VFS |
© 2000-2018 185th VFS |
|
|
|
3 July 2016 - 185th Theatre Mission 4
