on 13 September 2026
 All Forums
 Tactical Engagements, Dogfights & Campaigns
 Sunday Mission Synopsis - PUBLIC
 Sunday 3rd November - Gators 'n' Swamps
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Griffin



UNITED KINGDOM
5068 Posts
Status: offline

Posted - 03 Nov 2013 :  19:34:07  Show Profile Send Griffin a Private Message  Reply with Quote
Flight leads in this Sunday's official mission, "Gator 'n' Swamps" 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


vaughan

UNITED KINGDOM
245 Posts
Status: offline

Posted - 03 Nov 2013 :  21:57:41  Show Profile Send vaughan a Private Message  Reply with Quote
Flight Role: STRIKE
Lobo11: "Vaughan" AA=0 AG=2 RTB
Lobo12: "Griffin" AA=0 AG=2 RTB
Lobo13: "Novac" AA=1 AG=1 RTB

Plan
1. Loiter until the SAM threat is eliminated or time runs out and we have to make a move (0545 at STP 4).
2. At STP 5, split into elements. First element to attack the runways from low level, egressing to the south east and making use of terrain masking to stay clear of any SAM threats. Second element to circle to the east of target and attack secondary targets from there, possibly using a loft attack to avoid entering SAM range.
3. Regroup to the south and RTB.

Execution
On ingress to our STP 3, we were aware of a MiG 23 engagement. I ordered the flight to turn south west to avoid entering the engagement zone. After hearing from Snake1 that the picture was clear, we turned towards our STP4. We were on time, with no time to loiter, so proceeded at buster.

At STP5, I ordered the flight to split and called that we were heads down and going in on target. Chalis advised me to hold, as there were multiple air threats in the area. I put the first element into a left orbit. We had 29 spikes on RWR and Griffin went defensive. According to the ACMI I also was fired upon, but I had turned cold as soon as the missile was launched, so was not aware of this in the pit. Griffin called that he had defeated the missile and we regrouped and proceeded as fragged.

It was 5:57 and we had to get bombs on target within 3 minutes, so we proceeded in the weeds at 560kts. Griffin struck the left runway slightly ahead of me and I hit the right one. I had a really cool view of the bomb blasts. We came off target south east and climbed once clear of the SA11.

Novac asked Chalis for status of the runways and the response was that one runway was still active. I ordered Novac to strike the still active runway, which he did and then also hit one of the buildings. As it turned out, the runways had been destroyed during the initial bombing run. It was the AWACS screen that took a little while to update.

We regrouped and RTB was uneventful.

An excellent mission, with really good support from the other flights and Chalis. Thanks all!
Go to Top of Page

Skal

UNITED KINGDOM
102 Posts
Status: offline

Posted - 04 Nov 2013 :  00:03:32  Show Profile Send Skal a Private Message  Reply with Quote
Flight Role: SEAD ESCORT
Shark11: "Mango" AA=0 AG=0 TECHNICAL
Shark12: "Skal" AA=1 AG=1 RTB
Shark13: "Jack" AA=0 AG=4 RTB
Shark14: "Wolfman" AA=0 AG=4 RTB

Plan
1. Shark flight to follow flightplan after takeoff. At STP 3, 1st element to seperate from flight and engage SA2 near Haeju (PPT59) and SA2 north of R107 (PPT60)
2. Flight regroup at STP 4, Shark12 to engage SA3 north of target, Shark11 to monitor SA11 going active and act as deterrent against SA11 and engage if become active allowing 2nd element to engage with Mavericks
3. Regroup to the south of target and RTB.

Execution
While approaching the runway for takeoff, Mango had a technical forcing him out the game. Skal (Shark12) took role of flight lead.
On approach to STP3 2nd element ordered to continue as fragged, Shark12 diverted west of course and engaged/destroyed SA2 near Haeju. Regrouped south of STP4 and received MiG23 spike, flight turned to engage but threats eliminated before we could get picture.
Once passed STP4 on route to target, 2nd element ordered to proceed as fragged and engage SA11 if safe to do so. Shark12 fired/missed onto SA3, followed immediately by directions from Chalice to engage MiG29A in support of Blue Flight. 1x MiG29A engaged/destroyed.
Shark12 remained on the edge of SAM threats successfully drawing lock from SA3 & SA11.
Once 2nd element passed target STP and assed threats, ordered to turn turn cold to setup for ground attack while shark12 remained within visual to provide air support. Both Shark13 & Shark14 made two passes destroying 4 ground targets each.

Regrouped near STP 6 and RTB was uneventful.

Was a shame we lost Mango but I think we did very well and hopefully my lead was satisfactory. I think communication from 2nd element was very good and were where expected to be at any given point, cant fault them any way. Thanks :-)
Go to Top of Page

Homer

United Kingdom
1082 Posts
Status: offline

Posted - 04 Nov 2013 :  09:34:57  Show Profile Send Homer a Private Message  Reply with Quote
Flight Role: SEAD ESCORT
Snake11: "Homer" AA=3 AG=0 RTB
Snake12: "Zipgun" AA=0 AG=0 Blue on Blue
Snake13: "Utopic" AA=3 AG=0 RTB
Snake14: "Zipgun" AA=1 AG=0 RTB

Plan was to have lead element 10 miles in front of Lobo, with second element shadowing them. This worked right up to the first MiG23 engagement when all hell broke lose, resulting the in the AI shooting down Zipgun. In the ultimate act of kindness, Zipgun teleported into the #4 seat, kicked the AIs ass out of the plane, and took over.

I would like to tell you how the escort went, but in all honesty I can't - it got very messy with the lead element (i.e. me) losing contact with the second element and we separately engaged various MiG29 groups until they were all dead.

Established a quick CAP over the target zone until we heard the runways were destroyed, then rejoined for the flight home. Formed up landing upon return was highpoint of egress/rtb.

I felt things were were messy with little coordination to begin with, but this improved vastly when Crowebar took over as AWACS. I am not the best at leading flights either.

Enjoyable none the less. Powercut meant I was kicked offline right at the start of debrief. Fairly common since they started upgrade work... go figure. Worked fine before!
Go to Top of Page

utopic



ROMANIA
577 Posts
Status: offline

Posted - 04 Nov 2013 :  12:25:54  Show Profile  Visit utopic's Homepage  Send utopic an ICQ Message Send utopic a Private Message  Reply with Quote
Thanks for leading, Homer, I certainly wasn't up to it last night.

I'd say we only got separated once we went north beyond the SA2 line. At that time, the comms were so busy I could not get any directions from you (I had to declare a bandit 3 times before I could get a reply from our AI AWACS) so I turned east and engaged a group that was closing in on friendlies.

Thanks for the mission, Zipgun.
Go to Top of Page

Floyd

Germany
1357 Posts
Status: offline

Posted - 04 Nov 2013 :  16:42:58  Show Profile Send Floyd a Private Message  Reply with Quote
Flight Role: SEAD Strike
Falcon11: "Floyd" AA=3 AG=2 RTB
Falcon12: "Wildcard" AA=0 AG=2 RTB
Falcon13: "Crowbar" AA=0 AG=1 EJT

Our targets were two SA-2 sites at ppt 56 & 58. The plan was to
engage another SA-2 by splitting off the second element and this
worked as briefed.

During the first engagement (MiG-23) we lost #3 and #4 to IR missiles,
while leaving the area for Escort to engage.

Both primary targets were engaged sucessfully as were two more MiG-23
coming in from the west.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
185th VFS © 2000-2018 185th VFS Go To Top Of Page
This page was generated in 0.75 seconds. Snitz Forums 2000