RAFAir MISSION TUE 13th JUL 21

[Chris]

It was agreed after debate that a trial addition to the RAFAir MISSION planning process will be run commencing 07 JUL 21.
Neil Willis directed that Operation OH MAN will be re-run on this date.

Last night, at 19:05 a JAOP (Joint Air Operations Planning) session for this event was held in open session on TS. Apologies received from 11(F) with the rest of commanders present.
The aim is to consider the proposed mission framework for the 13th July 2021 and agree an overall Commander then define or revise

• Commanders Mission Intent - what RAFair mission intends to achieve
• Mission Success - what is measured to deem mission success
• Squadron Objectives - what individual squadrons are tasked to do
• Scheme of execution - how we all work together to achieve the mission
• Approve or amend the COMMS plan
• Define common Brevity Action codewords - if required.

Resultant:

• Chris (Gizzy) will be the 'commander'
• The mission is generally speaking unchanged at Andrews discretion.
• Mission Commanders Intent
  To assert naval dominance over Iran and deny by force all Iran military and commercial naval activity in the Gulf of Oman in accordance with NATO Directive 879/3002.
• Mission Execution
  892NAS will perform a diversionary attack North of Pdsay Kum mountains providing own CAP & SEAD
  11(F) will provide CAP primarally for 1(F), 41(F) & 1(F)
  3(F) will provide SEAD Bandarpol / Bandar Abbis
  41(f) will attack Bandarpol container port
  1(F) will attack the drone station
  97(F) will patrol and engage any shipping in the gulf of Oman exclusion zone
• Mission Success
• Disablement of Bandarpol Container Port
• Disablement of Shib Deraz Drone station
• The majority of Iranian Shipping in the Gulf of Oman exclusion zone
  disabled attacked.

Each of the commanders outlined their approach to achieve their objectives with Ade suggesting where he would place the CAP. This included such factors as approach, height, munitions and egress.

Aircraft objective minimums
1(F) CAS 2 - 3(F) SEAD 4 - 11(F) suggested 4 - 41(F) 4. 41(F) will probably field 6/8 in which 2 will proceed CAS overhead with CAP capability. 892NAS will proovide their own CAP / SEAD capability and as TGT is diversionary AC will infill SAED / CAP Squadrons if necessary. 97(F) will fulfil objective subject to Aircraft.

COMMS plan approved. All command calls initiated 251 (Overlord) then PUSH to Guard 243

Brevity codeword SEAD to be issued when SEAD successful

TOT
SEAD commenced 6 minutes prior to 41(F) and 1(F) target engagement. Target Engagement Time will be agreed and published on the night once server and MIZ ready.

above Subject to revision.....

JAMBOARD session link available for commanders if desired for briefing. Those requiring WP's inserted return to Andrew in the normal manner on INTEL-BRIEF.MIZ issue.

Group Briefing on the night will be short. Commanders please prior brief accordingly.

[Chris]

Capture.PNG (4.63 MiB) Viewed 2389 times

[Chris]

DOCKS - 41(F) Objective

222.PNG (3.43 MiB) Viewed 2389 times

DRONE BASE 1(F) OBJECTIVE

111.PNG (4.48 MiB) Viewed 2389 times

[Beanie]

Hi Chris,

When will the .MIZ be made available? I find myself with a bit of spare time tonight.

[Chris]

Use this Intel Brief MIZ Beanie, viewtopic.php?p=36417#p36417

Andrew may update the Intel if needed but treat this file as, say, 2 days pre-mission. I hope this is okay....

[0405 Andrew]

Please use .miz file to return waypoints as normal. This is the same intel .miz file as Chris's link.

The mission will be slightly updated to reflect comments from the previous outing.

[Flyco]

Andrew, the pan on which the current A-10s are located, only has 4 spaces. We are hoping for at least 6 x A-10s.

Are you content if I move them to slots 14-21 behind the Harriers and F-16s? Alternatively, I will leave the 4 where they are, and put the other 4 on slots 14-17.

Let me know which you prefer.

[Roon]

TOT PLANNING

Do you have an idea of TOT's for the port attack, bearing in mind the SEAD requirement around the port. We have slotted a SEAD/SWEEP pair on the front of the package just in case any SAM's remain. If there are no SAM's left, they are equipped to assist in the CAP task as you direct. They'll call in as available once we are safely on our way home.

Our preferred timetable would be:

SEAD strike on SAM's around the port.
+ 6 mins
41(F) SEAD/SWEEP arrive
+4 mins
41(F) Bomber package arrive

If you can give us a time (Z) for the SEAD strike, we will work back from that to work out our TOT's and takeoff times.

Takeoff times will need to bo coordinated with the A10's and F16's and Harriers that are also at Al Minhad to avoid traffic jams/confusion.

[0405 Andrew]

Alan, please put them on 14-21.
If they need to be moved I will advise you on your new position.

[Flyco]

Thanks, just hope we do get more than four A-10ers.