AMVI 28/V/2018

[Daisan]

Hi,
This is an invitation to our 2018 Online Operations which will be carried out on the Israeli Theater of Operation. version 1.0.3
https://www.benchmarksims.org/forum/sho ... BMS-4-33-3

Different tasks task will be available from A-A to A-G, Sead etc.
We will be happy to meet you on our TS and Falcon server on the date in subjest.
Would you please post your interest on the dedicated thread at our Forum here:

http://www.amvi.it/forum/viewtopic.php?f=128&t=21883


Hope to see you soon
Kind regards
Hawk
http://www.amvi.it



External Groups/Wings are kindly invited to participate at the activities of our 2018 online Missions (Tac. Eng.).
In order to organize the available slots, each Group/Wing shall announce his intention on the relative thread into this Forum Area (usually the Responsible for the Group will take action), specifying:
- Name of the Group/Wing
- Number of participants
- Preferred aircraft
- Task of their flight (this will be managed/assigned depending to the general plan of the daily mission)

We remind you that AMVI will have human crew for ATC, AWACS, JTAC and Tanker roles.
Thanks for your participation

ATO, COMMPLAN, etc(.pdf/docx): http://www.vitaf.it/AMVI_Sito/Activity/ ... 04-ATO.pdf

Mission Files (.tac,.ini,.twx, etc ): http://www.vitaf.it/AMVI_Sito/Activity/ ... 04-MIX.zip


Falcon Weather(.fmap): files to be uploaded by the Mission Planner

F4Wx sample




Rain
Temperature
Wind

Weather at Takeoff: Ben Gurion AB Time XXHXX
Weather at Target ......

ATO Number: DR04
Mission Commander: OPEN

Mission Start Time 21:30 Falcon Time (UTC+2)
First human flight Takes Off at 22:04 Falcon Time (UTC+2)
Sunrise in Ben Gurion AB 04:51 068° Falcon Time (UTC+2)
Sunset in Ben Gurion AB 18:32 291° falcon Time (UTC+2)


Intelligence Report

Overview



Targets

















Known Threats



LASER CODE



HIDACZ Coordination



GROUND TASK
ATC: OPEN
AWACS : OPEN

Package 742

20009 - Cowboy 1 - 1xF16CM52 - TRAINING - SERVER
-

ARTIFICIAL INTELLIGENCE FLIGHTS

Package 6301

20006 - Chalis 1 - 1xE3 - AEW/ABCCC

20007 - Claw 1 - 4xF15C - HAVCAP

20008 - Camel 1 - 1xKC10 - AIR REFUEL
-

HUMAN PILOTS FLIGHTS - BEN GURION AB

Package 6328

20010 - Falcon 1 - 2xF16CM52 - SEAD
-
-

20011 - Fury 1 - 2xF16CM52 - HAVCAP
-
-

Package 6331

20012 - Lobo 1 - 2xF16CM52 - SEAD
-
-

20013 - Panther 1 - 2xF16CM52 - HAVCAP
-
-

Package 743

20014 - Python 1 - 2xF16CM52 - STRIKE
-
-

20015 - Serpent 1 - 2xF16CM52 - STRIKE
-
-

Package 744

20017 - Snake 1 - 2xF16CM52 - STRIKE
-
-

20019 - Stud 1 - 2xF16CM52 - STRIKE
-
-

20016 - Shark 1 - 2xF16CM52 - STRIKE

Package 746

20020 - Viper 1 - 2xF16CM52 - SEAD
-
-

20021 - Hornet 1 - 4xFA18C - TARCAP

AWACS
Alex

PILOTOS

F-16
Mario
CAG

F18
Daisan
Fresco
Dardo
Viñaspre

[CAG]

Yo

[Fresco]

Me apunto con un 18, si hay slot libre..., a ver si puedo el lunes, joer.

Fresco

[Daisan]

Hay slot! Vamos allá Fresco!

Enviado desde mi GT-I9195I mediante Tapatalk

[Daisan]

Les he puesto algunas dudas que tenía. Os lo reproduzco aquí. En cuanto tenga respuestas igualmente las colgaré

Great job with the ATO/mission!

I have several doubts:

- Regarding Hornet Tarcap. Is the flight responsible of defending all the east FAOR or just getting escort of SEAD? If we asume all the FAOR coverage, could we move our asigned TARCAP hold?
- I know that mission is already done and planned, but for us would be easier to have all the strikers entering in our FAOR in the same package, in order to have some good situational awareness provided by the DL
- Any scheduled terminology for hostiles going from one FAOR to the adjacent?
- Could we get more intel of the red hostiles? Expected reactions ( CAP vs scramble), usual tactics, missiles on board, radar capabilities, best and worst expected scenario for instance
- I think we should coordinate reactions with strikers. Some items should be kick authority, kick headings, desired engagement zone. Do you have any standard?

Grazie mile for letting us flying with you. It is really great!

Ciao

Daisan

[Daisan]

DEBERES

HORNET
1. Tácticas, weapons employment
2. Domestics
3. Intel AA, reacciones
4. Bingo/ Joker, meteo


VIPER
1. Tácticas, weapons employment, intel AG, reacciones
2. Domestics, alternative, bingo, meteo

[Daisan]

A expensas de lo que nos responda a las dudas el MC, voy planteando la parte táctica

Package composition:
4 F18 TARCAP ( Hornet1) + 2F15Block52 SEAD
Entrada en FAOR de 3x strike ( Shark, Snake, Stud) a las 22:25, que no estarán posiblemente en DL
Entrada simultánea de Hornet / Viper según MC en la FAOR a las 22:20. Antes de WPT 3 con fence realizado y picture de AWACS
No se espera oposición para entrar en la FAOR. Push con Hornet en box reducida en azimuth( los dos aviones de delante 1/2 con 5 nm de separación lateral entre ellos, 3-4 a 15 nm tras 1-2, 0.9M FL280 , tras viraje TAC en WPT 3. Vuelo Viper 5 nm en trail del 1/2, con la idea de hacer push agresivo y eliminar en la entrada SA3 DARNER2, respetando la MAR a posibles RED. Si no fuese posible en el peor de los casos retrograde a WPT 3, aunque preferiblemente a MARS area WPT4-5. Si no se encuentra oposición en el push, se recomienda ( a expensas de lo que prefiera la SEAD) tras eliminar DARNER2, seguir hacia el oeste para silenciar DARNER1. Si se consiguen silenciar y no se precisa apoyo en A2A a la TARCAP, Viper se retirará a MARS área al hold hasta Miller time

RADAR SET UP
Standard del EdAv. Búsqueda en RWS 80 nm, con mate a 20 nm 0-20000 ft 1/3 y 18.000-40.000 2/4. Disparos si multiboogey recomendados en TWS
Short commit sin mate

AOR
Definida en ATO, pero vamos a obviar boogeys al sur del WPT 66, FAID AB, con F16. Si nos dejan cambiaremos la posición de la CAP a más al sur tratando de interponernos entre los strikers y el eje de ataque de los bandits, que se supone desde el Oeste-suroeste hacia el norte-noreste. Ojo al Bullseye que está un poco lejos y nos puede confundir para las picture

CAP
Lo dicho, si nos dejan la cambiaremos. En cualquier caso 15 nm entre tramos ( no 20 como está actualmente), FL280. Mínimo 0.8M, recomendado 0.85-0.9M. 2x2 aviones separados en azimuth 5 nm, dándose la vuelta con virajes IN PLACE, virajes a la derecha y ojo a coordinarse y pasarse la picture
Búsqueda según radar set up. MUSIC OFF salvo commit
Se espera AWACS humano, si no tuviésemos ni humano ni IA cobertura durante el playtime ( 40 mins) por los medios del propio package. Flujo de comms habitual

COMMIT
No se esperan aviones aliados al sur de la línea de costa o fuera de MARS.
Se hará commit a todos los bandits en caliente, al norte de la línea E/W que pasa por WPT 66 FAIB AB, dentro de la FAOR SATURN EAST. Inmediatamente a la declaración de commit el segundo elemento se pondrá en caliente

Commit en el push: se intentará hacer bracketing, single side offset cada uno por su lado, ojo a los SA3 y otras amenazas. Fox 3 respetando la MAR, launch and leave tactics 25-28 nm disparo en commit frontal, se deben cubrir todos los aviones dentro del FBR 25nm. Ojo a pasar info al darse la vuelta. MUSIC on en el commit. Si no es posible bracket, ataque frontal estándar intentar crank/pump cada uno hacia su lado para recolocarse separados en azimuth para el recommit. Segunda línea agresiva y energética, intentar grinder que avance, buscar separación por azimuth y jugar con drags si es necesario. Evitar el merge a toda costa en el push. Abort criteria: MAR/SAM envelope. Si es necesario retrograde a wpt 3 y contar con SEAD para el push
Late pick up/ leaker handover (20 nm): hard lock ( para que se vea en data), cheapshot respetando MAR, drop y dejarlo para segunda línea

Commit desde CAP: Si más de 30 nm a strikers previstos al final de interceptación ( shoot a 16-20 nm por beam/sector trasero) y geometría favorable intentar single side offset. Si no intentar braketing, interponiéndose entre los strikers. Banzai autorizado si distancia bandit/strikers menos de 25 nm o si leakers. Evitar acercarse a menos de 20 nm al WPT 66 para poder identificar scrambles con tiempo suficiente. Mismo late pick up que en anterior

Reset CAP coordinada entre elementos para evitar estar ambos en frío simultáneamente

Comms de commit estándar

TARGETING/ SORTING GAME PLAN
Según estándar nuestro y SPINS de AVMI

SHOT DOCTRINE
Debe ser declarado bandit/hostile según SPINS, resto CAF, friendlies in close, etc según nuestros estándares

F16B52 AIM-120 MAR 18, DR 20 DOR 25nm
Mig21 a espera de intel de MC, posiblemente sin capacidad BVR, disparos en no escape

VISUAL ENGAGEMENTS
Según OCU

NOTCH CONTRACT
Se defenderán los spikes de aviones con capacidad BVR por fuera de la DR y en banzai. En cualquier otro caso PUMP

EGRESS FLOW
Incialmente a MARS area, ajustando para dejar un elemento en caliente. Con miller time y sin hostiles a menos de 30 nm RTB. En caso de gran separación de elementos, cada uno por separado sin problema

CONTINGENCIES
- 3 ship game plan: push 2 delante 1 detrás, luego en CAP 1/2. Ojo al commit y a disparar a todos los aviones del FBR, sobre todo si coindice el commit desde el singleship
- 2 ship game plan: push los dos en spread, segunda línea SEAD, coordinar la CAP con la SEAD ( minimum asset 2 TARCAP, otherwise no-go)
- Skosh: RTB
- Wounded bird: RTB, si es posible tácticamente con escolta
- Looser plan: reunión WPT 3, coordinación con SEAD y MC y si es necesario push vs RTB

[Vinaspre]

Base: Ben Gurion (LLBG) - 82X - 14/32 LR - ILS (14R) 109.7
ALT: Sde Dov (LLSD) - 83X - 02/20 - ILS (02) 109.1

METEO:

AL DESPEGUE: DESPEJADO, VIENTO COMPONENTE NORTE 14 KTS. Y 28º NUBES A PARTIR DE 28000 FT MSL

EN TGT: LAS MISMAS QUE AL DESPEGUE

JOKER/BINGO: 4000/3000 LBS (CAP A 97nm DE BASE)

[mppzgz]

I have several doubts:

- Regarding Hornet Tarcap. Is the flight responsible of defending all the east FAOR or just getting escort of SEAD? If we asume all the FAOR coverage, could we move our asigned TARCAP hold? => TARCAP's responsability is to cover the entire sector of HIDACZ; maybe it is better to position your CAP on the original assigned area and wait AWACS directives. Hostiles may arrive from south or south west. Keep alerted about the position of hostile airports with significant threats, which will be marked with "X" on your HSD. TARCAP will stay in CAP for 40min and at disposal of AWACS for any threats available.

- I know that mission is already done and planned, but for us would be easier to have all the strikers entering in our FAOR in the same package, in order to have some good situational awareness provided by the DL => TARCAp and STRIKE are into different packages because our Commander CATU wants an additional effort of our pilots about their Situation Awareness. However, we'll have a dedicated AWACS (eDAV) which will coordinate TARCAP's flights and another which will keep an eye on SEADs and STRIKEs.

- Any scheduled terminology for hostiles going from one FAOR to the adjacent? => NO, standard brevities in use.

- Could we get more intel of the red hostiles? Expected reactions ( CAP vs scramble), usual tactics, missiles on board, radar capabilities, best and worst expected scenario for instance => Hostile's CAPs and SCRAMBLEs expected on HIDACZ, while other hostiles flights, which are not a factor for us, have been noted far south-est (Sinai), On the INTEL's map you find the kind of A-A threats from different enemy airports

- I think we should coordinate reactions with strikers. Some items should be kick authority, kick headings, desired engagement zone. Do you have any standard? => You shall not be concerned about STRIKEs because they have their TOT and shall comply with that..

- Would it be possible to have another location for the bullseye? Present position is quite far away from ops area and can be difficult to interpret data. I would suggest to set it in the South intersection of both Saturn FAORs : => Pending item to be discussed during the mission briefing with CATU

Grazie mile for letting us flying with you. It is really great!

Ciao

[mppzgz]

PACKAGE COMPOSITION
HORNET1 - TARCAP with HIDACZ EAST FAOR
VIPER1 - SEAD TGTs DARNER1 and DARNER2

IP TO TGT
Split at wpt 4. VIPER11 to DARNER1 VIPER22 to DARNER2.
Press to force radar ON, then shot. As soon as shot. rejoin WPT 5.
ECM OFF until MUD 3 or other RWR indication, then MUSIC ON. Chaff dispense only if shoted (SINGER 3)
Shot in WPN-EOM.
If naked just at timed out --> SAM assumed down if not, press to check and BDA if no RWR indication --> SAM assumed down.
TGT area MSA – 1600 FT.
AIR TO AIR THREATS
If HARM remaining – GO COLD to TARCAP MARS AREA. HORNET flight will assume. IF ARIZONA, NOTIFY ENGAGED TO AWACS and engage only as SELF DEFENCE or if HORNET requires support.
TARGETING/ SORTING GAME PLAN/SHOT DOCTRINE
STD y SPINS de AVMI. Declared as bandit/hostile IAW SPINS.
F16B52 AIM-120 MAR 18, DR 20 DOR 25nm. SHORT SKATE.
Mig21 BANZAI to NO ESCAPE SHOT.
GROUND THREATS
Use ECM and Chaff as SQN STD. GO COLD ASAP. Rejoin at WPT 5
REATTACK EXECUTION.
Each aircraft reattacks its target under command of VIPER11
ROUTE OVERVIEW
FLOT: COASTLINE INSIDE HIDACZ
ROUTING. FL230 (BLOCK 220-240) – SPEED to COMPLY timings (MACH 0.75 aprox)
FORM : SPREAD 1nm VISUAL
FENCE check at level off.
SLIPs by VIPER11
IP: WPT 4 SMS
EGRESS
Same as INGRESS. Inverse sequence.
COMM
AWACS , CHALIS 1 in CH2 PRI (278.650) APPLE, SEC (321.050) MANGO
INTRA-FLIGHT: CH 3 VHF (150.000)
Blind / Separated: IF in PLAYTIME Rejoin at WPT 5. Out of PLAYTIME, VIPER11 will direct.
QUESTIONS ?


Carlos, haz tu la guia de briefing general que comprende la tarea que te ha asignado Diego. Si algo es de mi parte, déjalo en blanco con una nota y te lo relleno después.