|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| Vosene |
Posted - 11 Oct 2015 : 21:21:35
Flight leads in this Sunday's official campaign mission, "Battle for Sinai 9" 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
 |
| 4 L A T E S T R E P L I E S (Newest First) |
| Sabre |
Posted - 14 Oct 2015 : 18:27:16
Flight Role: Escort
Rapier11: "Sabre" AA=0 AG=0 RTB
Rapier12: "Mango" AA=0 AG=0 RTB
Rapier13: "Scruffy" AA=1 AG=0 RTB
Mission Outcome: MS
Pretty uneventful flight, queued for Elephant take off.
Set up CAP as required, minor engagement with Scruffy getting a kill
RTB with out issue, briefly joined by Sharpe on the way home.
Sabre was here |
| Sharpe |
Posted - 12 Oct 2015 : 11:40:39
Eagle 1 Close Escort
MS
Eagle11”Sharpe”. AA4/AG0. RTB
Eagle12”Vosene”.AA1/0. Tech
Fairly normal escort flight, proceeded out via 05L and hooked up with the BAI flights en-route. Provided support to a couple of leakers and hostiles inbound towards the BAI flights from the West and North West.
After dealing with a couple of leakers, some AI F16s were inbound to our general area, as Rapier 1 seemed busy with the sweep I called the BAI flights in under the extra cover provided by the AI aircraft.
On ‘miller time’ call from BAI flights, hung around to cover the exit of Rapier 1. Soon after it was clear that Rapier 1 was being pursued by 2 Mig23’s so moved in for a delouse (delouse call soon followed). RTB’d in good order.
Notes:
Good comms between close escort and BAI flights.
Based on previous sweep experiences, it might be worth making the package commander NOT the sweep lead (they are very busy flights normally) and tumbleweed is easy in a furball.
We happen to be using a double runway. Can I suggest that we start using it for take-off? We have two options:
a) Two aircraft on each runway and take of simultaneously (for four ship departures). This will help with inter flight rejoins.
b) Position a flight on each runway, and providing the turns are coordinated (ie left runway turns left to flight path and right runway turns right to flight path) we can get the whole package up much quicker.
Like the package taxi, I think we should look to brief one of these types of departure every time we use a double runway.
-Sharpe
 |
| Griffin |
Posted - 11 Oct 2015 : 21:51:06
Flight Role: Interdiction
Avenger11: "Griffin" AA=0 AG=1 RTB
Avenger12: "Flying Stone" AA=0 AG=1 RTB
Avenger13: "Veiland" AA=0 AG=1 RTB
Avenger14: "Floyd" AA=0 AG=2 RTB
Mission Outcome: PS
Took off last and climbed to FL230. Started pushing to start of patrol area at SP3 but were called away by package commander due to enemy air activity. Once clear we were called back in. No2 spotted a group of targets south of SP2 and we engaged in trail. Our hard deck was FL140 but we did go below it with BA of 3500 for Mk-20Ds. We dropped them in ripples of two with 300' spacing. Although the attack runs went well we got pitiful kills for the effort.
We then called Miller Time (or was it something about hot flushes?) and headed home with Rapier and Eagle watching our backs.
A rubbish lead by myself, but great support and inter flight comms along with Sabre's good Package Commander work. And no planes lost either! A good day at the office for us.
|
| utopic |
Posted - 11 Oct 2015 : 21:42:56
Flight Role: Interdiction
Gypsy11: "Utopic" AA=0 AG=11 RTB
Gypsy12: "Tank" AA=0 AG=1 RTB
Gypsy13: "Zipgun" AA=0 AG=13 RTB
Gypsy14: "Poppy" AA=0 AG=11 RTB
Mission Outcome: MS
We cut in front of Sabre's flight - sorry for that! - and flew like a package on the way. When the escorts became engaged, we turned called and made it back to stpt 2, then turned back in and by that time, the target area was safer.
We engaged units in the target area, then turned toward home, failed to regroup with #2 because of some tech issues. We did manage to land safely and debriefed while waited for the rest of package to land. |
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
