http://www.amvi.it/forum/viewtopic.php? ... 89866c2a1d
Por lo que parece es una semirrepetición de la anterior
Voluntarios?
F-16
CAG (dudas)
Zoom
F18
Daisan
Dardo
AMVI 11/VI/2018
AMVI 11/VI/2018
Last edited by Daisan on Sat, 09 Jun 2018, 16:39, edited 2 times in total.
Diego Novillo "Daisan"
Re: AMVI 11/VI/2018
Yo dudoso tengo dentista, sino hay nadie con viper voy con el hornet
Re: AMVI 11/VI/2018
Diegooo que te olvidas de mi!! Jajaja
Eso si, esta vez te toca de líder
Eso si, esta vez te toca de líder
Francisco Navarro "Dardo" - AME022
Piloto de Caza y Ataque
F-18
Destino Operativo:
Piloto 152 Escuadrón Virtual
Piloto de Caza y Ataque
F-18
Destino Operativo:
Piloto 152 Escuadrón Virtual
Re: AMVI 11/VI/2018
Ya hice de FL en la última jajajajajaja Da igual, aplicable todo el briefing previo
Diego Novillo "Daisan"
Re: AMVI 11/VI/2018
Yo imposible mañana lunes. Mi avión llega a Valencia a las 22:00, y aun tengo que llegar a casa. Me cago en toooooo, que ganas tengo de jubilarmeeeeeeee
Fresco
Fresco
Re: AMVI 11/VI/2018
Me he apuntado?? 
, si teneis en cuenta a la hora del despegue un margen de +7 u 8 mins, que es lo que tarda en entrar al vuelo en Israel. Solucionado. In.
Si estoy solo de F16, vuelo con 18 mismo.
, si teneis en cuenta a la hora del despegue un margen de +7 u 8 mins, que es lo que tarda en entrar al vuelo en Israel. Solucionado. In.Si estoy solo de F16, vuelo con 18 mismo.
Re: AMVI 11/VI/2018
I acted as leader of Hornet flight ( Hornet11). Firstly we were short of pilots. Two guys is a minimum and a risky business if things turn taugh. So our initial plan was getting supported by the SEAD, Viper1. In fact we decided to use the same VHF channel to coordinate between ourselves
We departed as 2 ship close formation, we were as fragged but we didn't want to delay flow making our night standard: 30 seconds radar trail
Uneventful transit to FAOR, receiving updates from the AWACS ( good job). We pushed to enter, and asumed or CAP, just 2 planes, because the SEAD was delayed following AWACS instructions
We were ordered to engage a pair of F16. Hornet12 was ahead so direct intercept 11 as support. 12 did a wrong pump and was shot down, bagging a F16 meanwhile. 11 splashed the surviving plane.
Reset, single ship CAP ( in theory I should have done an RTB, just one plane is usually a victim not a threat)
Reseting CAP, and after a while directed to intercept. 11 coordinated with Viper flight in order to pince red F16s. Hornet 11 flew a single side offset with tail conversion, getting two kills. Reseting CAP again, and uneventfull recovery in Ben Gurion
Some considerations:
- I think that all formations should post their own briefings. Mission Commander should take final decissions, but I think that all flights can improve scheduled plan. That way AWACS could have known that we needed Viper flight as support for the initial push and to fly the TARCAP
- Using different AWACS for A2A and ground pounders/SEAD makes really difficult to have good situational awareness, and makes coordination a nightmare. In our experience one AWACS per FAOR is the ideal set. So all people in that area knows what is happening, where and when
- Same item but related to data link. If all flights operating in the FAOR are in the same package, we can add them to the data link ( at least the leader of each formation) and know what they are doing, avoiding raygun calls ( almost impossible if strikers are in different UHF freq), blue on blue, and getting a clearer picture
- Some pilots sufered comm problems with Alex. I think that it is the outsiders=all problem. Please check file C:\Falcon BMS 4.33 U1\Bin\x86\IVC\IVC Client.ini and be sure of having:
outsiders = all
Our ACMI file
https://drive.google.com/open?id=1CKIqc ... dizTG62YUz
Anyway it was a great mission. Thank you for giving us the opportunity of flying with you all
Grazie mile
Daisan/Diego
We departed as 2 ship close formation, we were as fragged but we didn't want to delay flow making our night standard: 30 seconds radar trail
Uneventful transit to FAOR, receiving updates from the AWACS ( good job). We pushed to enter, and asumed or CAP, just 2 planes, because the SEAD was delayed following AWACS instructions
We were ordered to engage a pair of F16. Hornet12 was ahead so direct intercept 11 as support. 12 did a wrong pump and was shot down, bagging a F16 meanwhile. 11 splashed the surviving plane.
Reset, single ship CAP ( in theory I should have done an RTB, just one plane is usually a victim not a threat)
Reseting CAP, and after a while directed to intercept. 11 coordinated with Viper flight in order to pince red F16s. Hornet 11 flew a single side offset with tail conversion, getting two kills. Reseting CAP again, and uneventfull recovery in Ben Gurion
Some considerations:
- I think that all formations should post their own briefings. Mission Commander should take final decissions, but I think that all flights can improve scheduled plan. That way AWACS could have known that we needed Viper flight as support for the initial push and to fly the TARCAP
- Using different AWACS for A2A and ground pounders/SEAD makes really difficult to have good situational awareness, and makes coordination a nightmare. In our experience one AWACS per FAOR is the ideal set. So all people in that area knows what is happening, where and when
- Same item but related to data link. If all flights operating in the FAOR are in the same package, we can add them to the data link ( at least the leader of each formation) and know what they are doing, avoiding raygun calls ( almost impossible if strikers are in different UHF freq), blue on blue, and getting a clearer picture
- Some pilots sufered comm problems with Alex. I think that it is the outsiders=all problem. Please check file C:\Falcon BMS 4.33 U1\Bin\x86\IVC\IVC Client.ini and be sure of having:
outsiders = all
Our ACMI file
https://drive.google.com/open?id=1CKIqc ... dizTG62YUz
Anyway it was a great mission. Thank you for giving us the opportunity of flying with you all
Grazie mile
Daisan/Diego
Diego Novillo "Daisan"