on 21 September 2018
 All Forums
 Tactical Engagements, Dogfights & Campaigns
 Sunday Mission Synopsis - PUBLIC
 ITO 2107 Mission 7 (19th November)

Note: You must be registered in order to post a reply.

Screensize:
UserName:
Password:
Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert Hyperlink to Other TopicInsert Hyperlink to 185th VFS Member Profile Insert EmailInsert Image Insert CodeInsert QuoteInsert List
Videos: Google videoYoutubeFlash movie Metacafe videomySpace videoQuicktime movieWindows Media videoReal Video
   
Message:
Message:

Smilies
alien [:-alien] Angry [:(!] Approve [^] banghead [:-banghea
Big Smile [:D] Black Eye [B)] Blush [:I] burn Out [---o]
Clown [:o)] Cool [8D] Dead [xx(] Disapprove [V]
Drink [:-o-o-:] Eight Ball [8] Evil [}:)] goodnight [+O]
Happy_Spin [:-hspin] Head Scratch [scratch] Help [help] Hi [hi]
Kisses [:X] Music Band 2 [band2] Oops [oops] Phone [phone]
Popcorn [pop] Question [?] Sad [:(] Shock [:O]
Shy [8)] Sleep [___0] Sleeping [Zzz] Sleepy [|)]
Smile [:)] smoker [,O] SoapBox [box] Tongue [:P]
Wink [;)]      

   -  HTML is OFF | Forum Code is ON
   Insert an Image File
 
   

T O P I C    R E V I E W
utopic Posted - 15 Nov 2017 : 18:57:40

AI



On the western front, command wants to begin a push on the coast, as enemy ground units in the area are weakened and low on suppliers, with air defenses being almost wiped out. Also, in Syria, the enemy is low on active airbases, so you should have no AA engagements.

We are tasked to interdict enemy ground units, in and around the city of Sayda, on the west coast, in support of our ground forces advancing North. Two tank battalions are expected to defend the city, the 292th and the 263th.

South of the target area we have cover from our ships, so if need be, SW feet wet, is considered a safe area.

Note that South of the city there are remaining SA8s which are low on supplies, however take no chances and stick to the flight plan.



The package will consist of 3 AI flights: 2 four-ships and a three-ship :

  • Lobo1 AI -- Departs from the 107th @ Hatzerim -- Payload is fixed = currently loaded with LGBs

  • Panther1 AI -- Departs from the 107th @ Hatzerim -- Payload is fixed = currently loaded with LGBs

  • Python1 AI -- Departs from the 107th @ Hatzerim -- Payload is fixed = currently loaded with LGBs



Timings:


Flight            Task         TO          PP        TOT        IDM    VHF   TACAN    FL       LASER CODES

Lobo1               AI        18:09        18:20     18:33        1     1    11/74    200       1611-1614
Panther1            AI        18:10        18:21     18:34        2     2    16/79    210       1621-1624
Python1             AI        18:11        18:22     18:35        3     3    21/84    220       1631-1633




Procedures are fixed:
Please note that each aircraft in the package must have a different laser code, in the order of the flight number and seat, starting from 1611. This is the responsibility of each flight lead, and is to confirmed by each FL in the final briefing.

A FAC should be allocated during briefing, that is going to spot targets, using the laser frequency 1515.

All flights shall enter their own laser code and the spotter frequency on their LASER page, while on the ground. This is to be confirmed to the FAC on Uniform 15, before any aircraft starts to taxi

All aircraft should turn their laser ON and switch to COMBAT, while on the ground.

The calls will be:
"Flights, say status."
"Lobo12, laser armed - combat set"

The attack plan is fixed:
All flights must rendezvous at STPT4, and stack vertically, with 1000ft separation, starting with Lobo1, at FL200, with the exception of the FAC, which should hold over STPT6.

Once all flights are in the pattern, the attack may begin, with the first aircraft, from the 1st flight, followed by the next and so on.

Parameters are: 20 000 ft, 300 kts for the entire attack duration.

Sequence is:
1. FAC calls when ready, "Spotter - ready with targets"
2. The first/next aircraft in the stack calls "Lobo12 - turning IN"
3.1 Once the pilot is at IP (STPT5), he calls "Lobo12 at IP".
3.2 Once he hears this call, the next pilot turns in "Lobo13 - turning IN"
4. He will be assigned a target from the FAC, which he shall engage, then rejoin the pattern. (Lobo13 -- your target is ..., advise captured; Lobo13: captured; Lobo13, cleared hot; Lobo13: in hot)

Notes:
* if for whatever reason an aircraft is off dry, he continues with the pattern.
* when an aircraft is out of ordinance, he should stack at STPT4, with 1000ft vertical separation, starting from 21 000ft.


Mission success, all flights: 75% units hit for ordnance expended.


Note: for a quick refresher of working with a FAC, take a look here: FAC spotter settings


Thanks to Zipgun for help with various details and valuable input.
------------------------------------------------------------------

Flight Leads in this Sunday's official campaign mission, "ITO 2107 Mission 7" 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

MS/PS/MF
4   L A T E S T    R E P L I E S    (Newest First)
Zipgun Posted - 21 Nov 2017 : 17:03:27
LOBO1 - FAC

Lobo 11 - ZIPGUN AA=0, AG=0, KIA

MF

For some reason, the first 2 flights IB could not spot my laser. This caused me to wonder if 1515 was a legal code. About this time, I became spiked by 2 Mig-23s and scampered out to sea. After they were downed, I decided to try a different spot code, but was engaged by an SA-13 while trying to evade 2 more Mig-23s (and keeping my distance from the active SA-2).
Fisty Posted - 20 Nov 2017 : 09:17:13
Video from my pit is here:




https://youtu.be/kUx4-JrevQw
Fisty Posted - 20 Nov 2017 : 00:50:12
Panther 1 - Interdiction

Panther 11 - Fisty AA=3, AG=1, RTB
Panther 12 - Echion AA=1, AG=4, RTB
Panther 13 - Mango AA=0, AG=0, RTB
Panther 14 - Utopic AA=2, AG=5, RTB

MS (10x ground kills from 13 bombs)

Ingressed as fragged and formed up in 7nm trail before turning in. At IP Inbound, Lead failed to locate the target in LST so pulled off dry, as did 2. After turning for Stp 4, picked up a Mig23 2ship pressing from the east. Lead engaged both a 120 each with 2 gating to catch up and support, element on standby to press. Both migs were shot down, so we continued to target, however 2 more groups of as it turns out, a mig23 2ship and a su24 4ship were inbound. Python sorted on their nearest group (the mig23s) but merged into a furball. Lead fired both remaining heaters at a mig 23 on Python 1/1's tail, hitting with the second. That left him Winchester (having jettisoned stores after the merge), so he regained altitude and RTB'd, leaving 3 in command for the rest of the attack.

There were more sporadic engagements with enemy fighters and the bombs were dropped with varying results.

All RTB'd safely.

MS
Griffin Posted - 19 Nov 2017 : 22:04:31
Python 1 - Interdiction

Python 11 - Griffin AA=1, AG=5, RTB
Python 12 - Floyd, AA=0, AG=7, RTB

MS

Fell in behind Panther and set up for wagon wheel as briefed.

FAC laser codes didn't work. Then FAC got dropped by an SA-13, so we went on a search and destroy. We had MiG-23s appear and co-ordinated with Panther to take care of them.

Once we had gone Dakota we RTB'd with Floyd on fumes and went to the mess for tea and crumpets.



185th VFS © 2000-2018 185th VFS Go To Top Of Page
This page was generated in 0.14 seconds. Snitz Forums 2000