|
Note: You must be registered in order to post a reply.
|
| T O P I C R E V I E W |
| utopic |
Posted - 05 Feb 2018 : 19:40:23
AI
On the western coast our troops have managed to capture the city of Sayda, but barely. It remains to be seen if we'll be able to hold it. In the meantime our squadrons are being redirected to the eastern front.
Remember, in order to win this campaign, we must capture both cities of Beirut and Damascus.
Since we have no clear information on the enemy air defenses to the N-E, our first mission in the area will be a more cautious one, with the purpose of taking out enemy troops while gathering intel, and in the future, move north and clear the way.
Cowboy1 and Fury1 are tasked to interdict enemy ground units, in the kill-box around steer-point 4. Our assets on the ground indicate that there are 2 full strength Frog battalions on the move, heading for friendly positions which, due to their long range capabilities, are considered high priority targets.
Falcon1 is 4-ship escort for the package.
Note that 16miles to the east of the target area, at the Kalhalhak airbase there are 2 mig21MF fighter squadrons. While the airbase is at only 60%, the enemy could try to scramble flights against us.
In spite of this, keep in mind that completely taking out the airbase is NOT this package's responsibility.
GREEN lane is south.
The package will consist of 2 AI flights and a SWEEP/ESCORT:
- Falcon1 – SWEEP -- Departs from the 4329th @ Hatzerim -- Payload is free
- Cowboy1 – AI -- Departs from the 4329th @ Hatzerim -- Payload is free = currently loaded with AGM65Ds
- Fury1 – AI -- Departs from the 4329th @ Hatzerim -- Payload is free = currently loaded with AGM65Ds
Timings:
Flight Task TO PP TOT IDM VHF TACAN FL LASER CODES
Cowboy1 AI 16:17 16:17 16:28 1 1 11/74 240 1611-1614
Falcon1 SWEEP 16:15 16:18 16:32 2 2 16/79 270 1621-1624
Fury1 AI 16:16 16:19 16:33 3 3 21/84 220 1631-1633
Further considerations:
- Falcon1 is ESCORT, the flight should not engage enemy flights that are not a threat to the package
- Falcon1 is package commander. If Winchester and not yet Bingo, the package commander's flight is expected to provide over-watch for the package from a safe distance, until Miller Time
- Since Falcon1 may still need RTB due to fuel, the commanding responsibility needs to be discussed during the briefing.
- Also flights are expected to be able to switch roles depending on the circumstances ( even as far as jettisoning AG ordinance ).
Mission success, all flights: 75% units hit for ordnance expended, and no losses to enemy fighters.
------------------------------------------------------------------
Flight Leads in this Sunday's official campaign mission, "ITO 2107 Mission 17" 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
https://youtu.be/je0lFe0MHjU |
| 5 L A T E S T R E P L I E S (Newest First) |
| Vosene |
Posted - 13 Feb 2018 : 14:36:39
quote:
Originally posted by Zipgun
3) we should have called for a 'drop stores" by the AI flights earlier -- the SOP should be to do a cascading drop -- an element at a time as needed.
Regardless of this becoming a formal part of the SOP or not, we should still specifically brief this as part of the mission plan, including priority order of Flights to go A2A.
I don’t have an issue with the SOP to be an element at a time but, as always, Flight Lead has the authority to change this as required and have the whole Flight go A2A if deemed necessary.
 |
| Zipgun |
Posted - 12 Feb 2018 : 19:02:03
Flight Role: SWEEP
Falcon 11: Zipgun AA=4 AG=0 EJT
Falcon 12: Fisty AA=5 AG=0 EJT
Falcon 13: UTOPIC AA=2 AG=0 EJT
Falcon 14: AIM AA=0 AG=0 EJT
MF
As we were setting up the CAP, we noticed 4 hostiles heading west, we decided to ignore them and hope they kept going west. Soon, another 4 Mig-23s appeared from the NE. As we were beginning to engage, another 4 ship was spotted by #3. #2 & #4 had trouble keeping lock and were not able to get off timely shots. We soon found ourselves flanked and without a good exit strategy.
After a lengthy debrief and tape review, our lessons learned were:
1) we should have continued cold and dragged the hostiles toward the package, in hopes of getting a more even contest (we were 4 vs. 12 - soon to be 4 on 16)
2) wingmen need to call difficulties in getting shots and stick to the leads
3) we should have called for a 'drop stores" by the AI flights earlier -- the SOP should be to do a cascading drop -- an element at a time as needed. |
| Griffin |
Posted - 11 Feb 2018 : 21:17:40
Flight Role: AI
Fury 11: "Griffin" AA=0 AG=0 RTB
Fury 12: "Echion" AA=2 AG=0 RTB
Fury 11: "Floyd" AA=1 AG=0 RTB
Fury 11: "Mango" AA=1 AG=0 RTB
MF
On approaching the target we were told to orbit at SP 6. Unfortunately there were so many enemy aircraft, Falcon were three aircraft down.
We took the decision to go AA and we dropped stores (except for Floyd) to assist. I tried to clear Fisty's six and despite my declare coming in as "hostile", it was actually Fisty. Sorry mate.
Things got much worse so I called the abort and we all RTB'd.
|
| Vosene |
Posted - 11 Feb 2018 : 21:04:44
Flight Role: AI
Cowboy11: "Vosene" AA=0 AG=0 RTB
Cowboy12: "Sabre" AA=0 AG=0 RTB
MF
Plan - Join Fury1 during Wagon Wheel attack in kill box around Stp 5.
Execution - Uneventful ingress until Stp 3 when Falcon1 started to engage Air threats. We held at Stp 6 but got a call from Falcon1 stating they were down to a 1-ship with a further 4-ship bandit group inbound, type unknown. Fury1 went A2A and supported before they called more bandits inbound and called the abort.
Uneventful egress and Overhead break landing onto R32 Right.
|
| Griffin |
Posted - 06 Feb 2018 : 19:23:47
That's mildly disturbing music mister. Very...odd.
|
|
|
| 185th VFS |
© 2000-2018 185th VFS |
 |
|
|
