|
 Colt 1 Kills: 2 SA-3 search radars (1-1, 1-3), 1 SA-3 tracking radar (1-3), 1 EWR (1-4), 1 SA-3 launcher (1-2), 2 trucks (1-1, 1-3) Probable Damage: 1 SA-3 search radar (1-2), 2 SA-3 tracking radars (1-2, 1-3), 1 EWR (1-3), 3 SA-3 launchers (1-1, 1-2), 1 truck (1-2) Expenditures: 2 AGM-45A Shrikes (0 hits), 4 Zuni rocket bursts (2 hits), 17 FFAR bursts (15 hits), 3 20mm cannon bursts (3 hits) Losses: 1-1 (Forced landing, MIA presumed POW), 1-2 (KIA), 1-3 (KIA), 1-4 (Forced landing, MIA presumed POW) Colt 2 Kills: 1 SA-3 search radar (2-1), 1 SA-2 tracking radar (1-1), 2 trucks (2-1, 2-4), 1 MiG-21 Fishbed (2-4) Probable Damage: 1 SA-3 tracking radar (2-4), 1 truck (2-4) Expenditures: 6 AGM-45A Shrikes (1 hit), 6 gun bursts (4 hits), 5 FFAR bursts (5 hits) Losses: 2-1 (Ejected, MIA presumed POW), 2-2 (KIA), 2-3 (MIA) Of the 8 aircraft in Colt 1 and 2, the sole pilot to return was now-Seren Sauer, Colt 2-4. Based on his testimony and all available telemetry, we have been able to piece together the following: The initial approach was executed as planned; however, approaching the EWR that was the first target a breakdown in comms led to the two flights becoming disorganized on approach to Khalkhalah Air Base and the nearby air defenses. Despite this, the three sites guarding it were disabled and degraded with the use of rocket and gun attacks. The Syrian Air Force scrambled much quicker than anticipated, however. The initial wave of MiG-23 Flogger interceptors passed over us and engaged the CAP, but a second wave of MiG-21 Fishbed fighters dove on Colt shortly after. With the exceptions of Colt 1-3, who Syria is claiming to have downed with AAA fire, and Colt 2-4, the Syrian fighters engaged and downed 6 aircraft for 1 probable loss, claimed by Seren Sauer while unsuccessfully attempting to peel the bandit off Colt 2-1 (who successfully ejected and is presumed captured or evading Syrian forces). While the mission was tactically successful at degrading air defenses in the Khalkhalah area, it cannot be seen as anything but a serious setback given the failure to completely accomplish the tasking and the loss of 7 aircraft.
|
#
?
Mar 13, 2022 21:20
|
|
|
|
| # ? Jun 12, 2024 11:18 |
|
|
The Angry Brit posted:New video series chronicling this campaign in place of the GNN updates of the previous campaign - The Operations Goon. This is great.
|
|
#
?
Mar 13, 2022 22:03
|
|
|
Yooper posted:
For the F-16s, I can say we have already tested this quite a bit, and the Mavericks are our only reliable, accurate weapon against heavily armored vehicles. Our Mk-82s can kill, but only by dropping it directly on the tank which is possible but incredibly difficult. Our cluster bombs are not capable to damaging heavy armor.
|
|
#
?
Mar 13, 2022 22:26
|
|
|
Earthquake Update Overall the mission was a qualified success. Task 1: Destroy SAMs covering northern route "Crystal" Purpose 2: Enable safe egress back to David Ramat northwest of objective area. Results: SAMs covering Crystal consisted of two main groups of SAMs, one group due east of the FLOT, and one group northeast of the FLOT. The Eastern group was destroyed. The group to the northeast consisted of SA-2s and SA-6s and was largely untouched. This was due to several issues. First, Earthquake was operating with 3 fire platoons instead of four, so freedom to shoot and scoot as well as mass fire was diminished. Still, had the platoon leader of 1st Plt, A BTRY been able to find his own rear end in a top hat, he would have had no problem navigating all of 20 km up the road to engage the northern most targets. The M60 tanks protecting him refused to move out of the way, he got lost in a small orchard, and arrived to the target area extremely late and short on ammo, having finally frustrated his commander enough to re-task him to cleaning up targets out east. Task 2: Destroy SAMs covering Central/Southern route "Diamond" Purpose 2: Additional destruction of SAMs to reduce capability of enemy to reconstitute SAM units in follow-on missions and provide alternate egress route. Results: Route "Diamond" SAMs destroyed, zero friendly losses transiting the southern route due to enemy fire. Kills: SA-6 Search/Track Radar: 7x SA-6 Launcher: 11x KrAZ-6322 C2 vehicles: 2x SA-3 Tracking Radar: 1x SA-2 Tracking Radar: 2x SA-2 Search Radar: 1x SA-2 Launchers: 3x 1L13 Nebo Early Warning Radar: 1x Ural-375: 6x (ammunition trucks for SAMs) Target of Opportunity: BMP-2: 9x (they were not a primary target, but were sitting in parade formation close to the FLOT, so they had to die for their hubris) Additional notes: Mi-24s attacked friendly ground forces, knocking out a handful of Israeli tanks before being taken down by cannon and ATGM fire. No losses to Earthquake. [Sim notes for clarity] Will work with .miz makers to keep platoon sizes normal. Should've been 4x Platoons of 3 launchers each, was 3 platoons of 4 launchers for mission. One of the resupply units was spawned behind the border wall and couldn't figure out pathing. The tanks clustered on roads initially didn't feel like following orders, and so the BN commander had to go to first person mode and manually drive an M270 Platoon Leader's vehicle 10 km down the road, just to get the rest of the platoon unstuck. Later the tanks started to behave a bit better once we had killed some things, but still they were behaving pretty oddly compared to times I've practice controlled ground units, including online multiplayer. Nothing catastrophic, just kinda weird and finicky. Some screens: Fire Mission:  An element of the reload platoon was left behind the border wall and drove around for nearly an hour trying to get through, to no avail. The border wall effectively prevented them from conducting reload operations, resulting in limited effectiveness of the northern-most firing platoon, failing to destroy one of the SA-2 sites assigned to clear route Crystal.  Sneep on egress, passing through the corridor cleared by destroying SAMs in Diamond corridor. In the distance, an SA-6 site and BMP-2s burn. 
|
|
#
?
Mar 13, 2022 23:23
|
|
|
 DAY 1 AAR Operation: CONVERGENCE 10 June 1990, 0600 hours Ramat David IAF Base Single Element CAP flight Dodge 1-1: Prime Dodge 1-2: DarkOff Dodge 1-3: Gronank Summary Dodge 1 departed Ramat David 06:25 flying NOE to WP1 where we anchored awaiting SAM clear. After hearing Dodge 2 was engaged, Dodge 1 got permission to push North to assist, however by the time we got there Dodge 2 was down. Dodge 1-1 and 1-3 struck the first Mig-23 with a Magic each, with 1-3 claiming the kill. The second Mig launched on 1-1, but 1-3 called it allowing 1-1 to evade. 1-3 missed a Magic shot of his own, but splashed the bandits with a short guns burst. Dodge 1-1/1-3 were then vectored to support Colt 2-4 who had pulled 2 Mig-21's South of the SAM threat, who broke defensive as Dodge engaged. 1-3 secured the first kill with a Super 530, 1-1 missed a Magic shot, but 1-3 was in position to secure the kill with his second Super 530. During this time, 1-2 had become separated and picked up a bogey approx 20nm North, the bogey failed to return a valid IFF and 1-2 took the shot with a Super 530 and secured the kill, it later turns out this had been a Georgian civilian airliner. 1-1 & 1-3 pushed North to support Colt 1-3 who had a Mig-21 riding his six. Due to radar not being able to cleanly discriminate targets, Dodge pushed to visual range and 1-1 splashed the Mig-21 with a Super 530 shot from 3 miles. Shortly after, 1-1 was lost to ground fire from Khalkhalah Air Base, 1-3 got in to a fight with 2x KA-27 helicopters just North of the airbase, but pulled away due to the heavy ground fire. 1-3 picked up a bogey and closed in, similar to 1-2's position the bogey failed to return a valid IFF - 1-3 used a short cannon burst to get it's attention, but permitted it to leave noticing it was unarmed. 1-2 and 1-3 reformed and returned to Ramat David, both wheels down 07:17. Kills * MIG-23 - 2x * MIG-21 - 3x * Georgian airliner - 1x Losses * Dodge 1-1 Learnings * Flight became disorientated and lost SA on a few occasions; additional waypoints for area of operation and threat regions should be included in future * Need a consistent plan for how to reorganise and reform after going defensive * Several missile defences were unnecessary and could have reasonably been determined to be launches at others; if missile warning and no clear bandit, assess situation before defending * M0.6 is a decent speed for loitering on the deck (too much fuel consumed early in the flight ) Command request * I believe our flight would have been more efficient in escort, our radars are not great at being able to pick out individuals in a furball so being ahead of friendlies is advantageous * Our survivability is good given high speed, manoeuvrability and chaff count, but our aircraft's SA is poor - we appreciated the call we were wandering in to a SAM field on ingress, and will always appreciate warnings when approaching or overflying threats
|
|
#
?
Mar 14, 2022 00:30
|
|
|
gently caress SNEEP posted:For the F-16s, I can say we have already tested this quite a bit, and the Mavericks are our only reliable, accurate weapon against heavily armored vehicles. Our Mk-82s can kill, but only by dropping it directly on the tank which is possible but incredibly difficult. Our cluster bombs are not capable to damaging heavy armor. How many Mavericks can you carry per F-16? Is there a limited stock? (2nd part is a question for Vaha) mlmp08 posted:Kills: I was super happy with how well Earthquake performed. To be honest I was quite concerned that the MLRS would be as effective as it was. This enabled the op to kick off and make it back safely and quickly. Yes, we could have go back through Jordan, but this felt better and plowed a big rear end path through SAM's for future tasking. Regarding the MI-24 attack, we need to preserve Earthquake at all costs, this thing is a huge force multiplier. Standing order is ignore rotary unless Earthquake is under fire. The Angry Brit posted:Learnings I think we're all learning the capabilities and drawbacks of older aircraft and this is definitely part of that learning curve. Elendil and I will have to work on providing more cues from Slingshot / MatzoMaker to keep everyone on target. We really took for granted how our birds could perform in Georgia. Question Why was 1-1 so low that they got hit by AAA? Was it hunting that rotary? Our initial fears were of the SAM's being laser precise and absolute murder machines. Now that I see much more survivability, I think we'll keep CAP closer for future ops.
|
|
#
?
Mar 14, 2022 00:58
|
|
|
Panther 3 AAR Mission Status: Failure Known Targets Destroyed: 1x Ural Truck, 1x ZSU-23 AAA, 1x Mig-21 Losses: 2x F-16s Debrief: I can't consider this anything but a complete failure. Flight departed Ramat David and headed East, our planned orbiting altitude was initially going to be 5000 ft, but upon reaching steer point 1 I immediately recognized we were too low and the flight began a slow spiral climb to angels 20 to conserve fuel. Flight lead was monitoring poackage comms on 262 while Panther 3-2 was monitoring the ABM on 261. I was anticipating orders to attack to come in on 262, but as the situation became more confused, Panther 3 flight was ordered to attack assigned objectives once the SAM umbrella was confirmed inoperative. Since we were not assigned objectives prior to mission start, this led to confused comms. Ultimately Panther 3 was directed to Steer 3 to attack any remaining targets at the airfield there. En route, flight dropped altitude to angels 5. Partly due to confusion and partly due to bad planning on my part, Panther 3 flight passed too close to the airfield at Steer 2. This led to the loss of Panther 3-2 to AAA fire. His vertical stabilizer was destroyed and he entered an uncontrollable spin. His status is unknown but he is presumed dead. Panther 3-1 continued to objective, and upon arriving began searching for targets with the maverick seeker. This is a time consuming and painstaking process when the targets are not pre-defined, so Panther 3-1 did multiple passes, claiming kills against a cargo truck, and AAA battery. At least 2 Mig-21s appeared to take damage from Mavericks targeting their secure hangars but their status is ultimately unknown, believed to be fully operational. All of this target seeking took too much time and Panther 3-1 was ultimately the last plane in the AO by a wide margin. ABM ordered one final pass followed by immediate egress. Panther 3-1 used this final pass to drop his two Mk-84s. One struck a parked Mig-21 for a confirmed kill. The other missed. While rolling out of the attack, Panther 3-1 was struck by AAA fire and began leaking fuel and a perilous rate. While egressing, 3-1 was forced to eject. His status is unknown. Conclusion: Poor planning on part of flight lead, poor communication between the rest of the package, and poor flying on the part of flight lead led to the destruction of Panther 3 with little to show for it. Should Panther 3 lead be recovered he should face immediate court-martial. Ice Fist fucked around with this message at 01:26 on Mar 14, 2022 |
|
#
?
Mar 14, 2022 01:18
|
|
|
Yooper posted:How many Mavericks can you carry per F-16? Stations 6 and 4 cannot carry Mavericks, but they can carry bombs and rocket pods for added short-ranged punch against ground targets.
|
|
#
?
Mar 14, 2022 01:33
|
|
|
Ice Fist posted:Panther 3 AAR I'll take flak here, you guys came in for tasking and 1, I kind of forgot you were reserve, and 2, we didn't have a clear BDA of how things were going. Your flight plan was on cue, https://forums.somethingawful.com/showthread.php?threadid=3993395&pagenumber=4#post521894960. In hindsight we should have had you go in for clean up on both sites and simply prepped you to bypass one site or the other as the situation warranted it. I still feel holding someone in reserve is important, but we'll have to figure out a good way to make it clearer for you guys and easier for your package. We'll hold off on the court martial should 3-1 make it back. It was a rough enough day without a court getting involved.
|
|
#
?
Mar 14, 2022 02:18
|
|
|
Package Logistics Officer Briefing From a cost perspective, that was pretty rough. We faced stiff resistance today, and took quite a few losses for the damage we did. I was able to compile a report based on confirmed unit deaths: be advised that it does not necessarily take damage from static objects such as runways into account. Wonkotron proved to be the most efficient pilot from this perspective, and Gronank was our most destructive pilot. code: We were able to partially achieve our objectives, at the cost of one fighter. Objective 1: Runway Destruction
Objective 3: Parked Aircraft: We have confirmed the destruction of three aircraft, with potential damage to two others. According to flight recordings, the surviving aircraft include Seven MiG 23s, twenty MiG 21s, and a single MiG 25. That said, the majority were in bunkers, so we did decently based on what we had. Unfortunately, the planned flight path put us within range of an SA-2, which managed to shoot down one of us. AAA and SAM threat ensured we were unable to hang around for long; in fact some flight members were forced out of the AOO before we could release all of our munitions. We also had a momentary SA fail as we passed WPT2, as we accidentally overflew the airport Panther 2 was targeting, potentially sending them on alert prematurely. We did switch half of the flight from Mk82SEs to mavericks last minute, which had mixed results. Unfortunately, they were a bit difficult for us to employ under pressure, and one of us was completely unable to use them due to fuel constraints. SEAD was a requirement to effect meaningful damage to this airbase, and by the time we had arrived, Colt was compromised. In my opinion, this attack should have been aborted when it became apparent that Colt would be unable to support us, with Panther 1 assets redirected south to help Panther 2. Despite this, Panther 1 performed admirably, and I am proud to see we have achieved as much as we did.
|
|
#
?
Mar 14, 2022 05:03
|
|
|
 VF-154 AAR: Ford 1-1 and Ford 1-2 launched from the carrier deck without incident. Enroute to practice recce over Ramat David airfield, Ford and Devil flight monitored Israeli ABM radio traffic, and noticed what sounded like a full scale strike operation being carried out. Ford Flight decided the best course of action was to loiter over the Haifa Beach waypoint to further observe Israeli action, and be available in case CAG came to use with new commands, or in case Devil flight faced any retaliation threat from Syrian aircraft as they made their detection run. After some time and determination that our services weren't needed, Ford flight made a friendly show of force over the Haifa beach, and headed back to the boat. .... Black Knights, know that we are likely to be placed on high alert given the situation. Prepare for further orders from CAG.
|
|
#
?
Mar 14, 2022 15:56
|
|
|
Will have to see what intel pops up, but I expect sooner than later, it will get a lot harder for MLRS to just delete SAMs within 32 km of them. We caught the Syrian forces unaware, and SA-2 / SA-3 sites may not move quickly, but SA-6 units will likely start leapfrogging sites around for survivability vs pre-planned fires.
|
|
#
?
Mar 14, 2022 17:12
|
|
|
 Attention Naval Aviators. The Syrians have decided to threaten the Roosevelt with Silkworm missiles staged on the coast near Tyr. This will not be allowed to stand and we have been given the green light to remove this threat to our freedom of navigation. As such we are going to sail NE to around 100nm from Tyr and launch operation IVERMECTIN. OPERATION IVERMECTIN 10 June 1990 Objective: Neutralize the anti ship missile battery located at Tyr Takeoff: 1200hrs  Aspen has provided us overflight imagery from 6am today.  Intel has provided a targeting breakdown of the battery. The primary targets are the silkworm radar and the missile launchers. Other millitary vehicles in the immediate vicinity are also fair game including any AAA protecting the site. In addition there are SAM threats in the region including an SA6 site to the South East. We do not have reconnaissance imagery of this site but it may be suppressed with anti radiation missiles to enable the strike on the objective.  Hostile aircraft may be engaged but only in self defense. We are striking a threat to the battlegroup not attacking Syria or Lebanon's air force. In terms of strike package responsibilities that can be negotiated between the Knights and the Devils. The Syrians shouldn't expect us to be this proactive so defenses both surface and aerial should be fairly light. However nothing is off the table in terms of self protection. AIM-54 use is authorized but for the love of god don't shoot down something that shouldn't be shot down. The target site is extremely close to civilian buildings. Don't give CNN something to make us look bad. We will have an E3 up as well as S3 tanker support.
|
|
#
?
Mar 14, 2022 19:47
|
|
|
Watch out for Georgian airliners boys.
|
|
#
?
Mar 14, 2022 20:14
|
|
|
 The Angry Brit posted:During this time, 1-2 had become separated and picked up a bogey approx 20nm North, the bogey failed to return a valid IFF and 1-2 took the shot with a Super 530 and secured the kill, it later turns out this had been a Georgian civilian airliner. OH. MY. G-D. TheNakedJimbo posted:4) Make absolutely sure you know what you're shooting at before you shoot anything. We do not need another USS Liberty. Confirm your targets before opening fire. Commander Yooper may set the terms of engagement as desired, but you need to know that if you start shooting blues because you didn't confirm your target, there will be very little that the Military Advocate General's Corps can do for you in whatever legal proceedings may occur. Congratulations, DarkOff. If you were TRYING to make this worse for Israel, you could not possibly have done a better job. Legal requires that you immediately submit a full report of your flight, from takeoff to landing. At this point a grounding or a court martial might be the BEST you can hope for, and you had better pray you don't end up in the Hague on trial for war crimes. Let the record show that the events of this mission may have just scrubbed the whole campaign. Between Syria formally requesting that the United States withdraw, and Israel SHOOTING DOWN A NEUTRAL AIRLINER, I'm not sure how much longer we can prevent the United Nations General Assembly from condemning this entire action. --- vv OOC: I haven't watched the whole Tacview of the mission yet, so be prepared for another apoplectic post at some point tomorrow. TheNakedJimbo fucked around with this message at 02:39 on Mar 15, 2022 |
|
#
?
Mar 14, 2022 23:00
|
|
|
Once again, why are we not spinning this realistically? That was FOR SURE hamas terrorists coming back from a terrorist training camp in Georgia and they had their IFF off because they are nefarious actors. edit: Are we gonna tell Jimbo about the single gun round the other pilot put through the OTHER civilian airliner? Elendil004 fucked around with this message at 02:12 on Mar 15, 2022 |
|
#
?
Mar 15, 2022 02:09
|
|
|
The one circling over a sam site with a mig behind it?
|
|
|
#
?
Mar 15, 2022 07:38
|
|
|
TheNakedJimbo posted:
what happened was that i took defensive actions against sam locks and got disoriented. Got calls of bogeys at direction of airliner but altitude call got garbled due to SRS issues. So i was looking for bogeys at previous call height while my flight members were making fox 2 calls. Seeing that there was bogey in front of me that wasnt going down i decided to shoot after IFF:ing contact as hostile. At the time i was also getting locked up by sam site, making decision more urgent. I then defended against several sam launches and managed to takedown sam site by making its proxy fuse detonate over other other sam site. I do agree that this was a disaster that could have been avoided by having no fly zone above target areas, also in hindsight not accounting for civilian air traffic in briefing was a mistake. Im also grounding myself until investigation finishes.
|
|
#
?
Mar 15, 2022 17:48
|
|
|
Dark Off posted:what happened was that i took defensive actions against sam locks and got disoriented. Got calls of bogeys at direction of airliner but altitude call got garbled due to SRS issues. So i was looking for bogeys at previous call height while my flight members were making fox 2 calls. Seeing that there was bogey in front of me that wasnt going down i decided to shoot after IFF:ing contact as hostile. At the time i was also getting locked up by sam site, making decision more urgent. I then defended against several sam launches and managed to takedown sam site by making its proxy fuse detonate over other other sam site. I do agree that this was a disaster that could have been avoided by having no fly zone above target areas, also in hindsight not accounting for civilian air traffic in briefing was a mistake. It's also kind of a failure on mission making, since in reality a civ air would not show hostile on IFF.
|
|
#
?
Mar 15, 2022 18:18
|
|
|
Elendil004 posted:It's also kind of a failure on mission making, since in reality a civ air would not show hostile on IFF. tbf his IFF did not show hostile; it showed "other". In reality those systems are fallible and not 100% accurate, so the pilot would 100% be expected to make a confirmation. The jetliner was not maneuvering towards him or making any kind of indication that it was a threat or even aggressive. That should be enough information for a pilot to question whether a blind shot is appropriate. Panther 2 flight also encountered a jetliner as we were attacking the airfield. Wonkotron assessed it's actions and decided that it was not acting as a hostile bandit would be expected to, so took the next step to actually visually ID it and then report back to the rest of the flight the location and altitude of it so that none of the rest of us engaged it either. It's a pretty weak legal argument to say "screen said 'not teammate' so i murdered a jetliner full of georgian civilians". The entire package was briefed that civilian airliners were expected to be all over the AO since this was a surprise attack and there would have been no time to clear the skies or ground anything prior.
|
|
#
?
Mar 15, 2022 18:43
|
|
|
Elendil004 posted:It's also kind of a failure on mission making, since in reality a civ air would not show hostile on IFF. There’s no aircraft really on Earth that shows “hostile” on IFF. DCS IFF is godawful, so they err on the side of feeding unrealistic amounts of info to players with too much clarity vs the garbled or multiple responses you really get if firing Mode 1/2/3/4 interrogations into busy airspace. In reality, especially for the time period, it’s more like a response of “friendly” or a response of “could be anyone at all, I don’t know” or a total lack of any response.
|
|
#
?
Mar 15, 2022 18:52
|
|
|
fair
|
|
#
?
Mar 15, 2022 19:09
|
|
|
deadseedinside posted:tbf his IFF did not show hostile; it showed "other". In reality those systems are fallible and not 100% accurate, so the pilot would 100% be expected to make a confirmation. The jetliner was not maneuvering towards him or making any kind of indication that it was a threat or even aggressive. That should be enough information for a pilot to question whether a blind shot is appropriate. to implicate myself further i checked the manual and i didnt understand IFF properly. Unknown only shows up if there is friendly aircraft near target it will otherwise show neutral targets as hostile on mirage. i read the flight briefing and it had no mention of civilians. and i must have missed it in voice briefing.. the civilian airliner was flying towards me (at really slow speed, which should have tipped me off) and due to closure rate i would have had only 10 seconds more before i would had to have taken shot from it if it was mig21 less if it was mig23.
|
|
#
?
Mar 15, 2022 19:34
|
|
|
mlmp08 posted:There’s no aircraft really on Earth that shows “hostile” on IFF. Didn't actually know this myself, my SA page showed me multi-donor confirmation of hostile track so I 100% thought it was. Main reason we didn't shoot our air liner was because as the US it wasn't a shooting in war yet so I asked for permission and GCI told me it was an airliner.
|
|
#
?
Mar 15, 2022 19:35
|
|
|
to complicate the situation further. Rest of mirage flight was 30km away from hostile mig's the civilian airliner was 30km away from me. So the radio call for hostile mig21's would have lead me to believe that what i was looking was the hostiles. as Bearing and range was same with altitude being garbled.
|
|
#
?
Mar 15, 2022 19:57
|
|
|
 Panther Squadron Commander 101st IAF "gently caress SNEEP" PANTHER 2 AFTER-ACTION REPORT We had a had a nice, long taxi to runway 27 where we got to watch the line of planes take off past us. We were the last flight to take off and headed towards waypoint 1 as we climbed to 26k ft. We went past waypoint 1 towards waypoint 2, but the swarm of bandits on our HSD and FCR had us circle back around to wait until CAP gave us the all clear. After a short delay we were called in to do our strike on Khalkalah AB. Myself and Deadseed attacked the Northern runway with Mk-84s while Slip dropped a Mk-82 on some MiGs that were on the Southern runway lining up to take off, preventing them from doing so. Wonkotron orbited above in reserve. We completed our second pass on our assigned targets, including the fuel tanks, and then continued our passes until we ran out of munitions. I dropped all of my bombs first and sped out of there following the waypoints safely out of Syria and back to Israel. Everyone else in Panther 2 made it back safely, and I believe only one of us took slight damage from AAA. Overall, I'd say we were successful with our mission. We destroyed plenty of aircraft, fuel tanks, and disabled their runways. PANTHER FLIGHTS AFTER-ACTION REPORT/BATTLE DAMAGE ASSESSMENT Now putting on my Panther Squadron lead hat on. We planned correctly for this mission. We were also executing the mission well... up until one flight flew over an active airbase and low altitude chasing a helicopter! The SEAD flights were not completely successful in disabling the SAMs around Marj Ruhayyil, which led to some losses for Panther 1 and 3. They were still able to inflict heavy damage on to the runways, aircraft, and some light vehicles. I'm sure their families will be glad to hear about their kill/death cost ratio. Going forward we need to make sure we keep our situational awareness high, stick to our mission, and communicate between the flights when you need assistance. Khalkhalah BDA  pre:Killed: MiG-21x9 S-60 (AAA) Fuel Tanksx2  pre:Killed: ZU-23x2 S-60x2 Tigr MiG-23x3 MiG-21x4 Damaged: MiG-23x2 MiG-21x1 Fuel Tanksx2 Munitions Depot Each day the best Panther flight in the squadron will be awarded a shiny gold star for their performance during the mission. This week the award goes to Panther 2 for not losing any planes and successfully hitting every intended target at the airfield. Hooray Panther 2!  See you next mission! FUCK SNEEP fucked around with this message at 22:54 on Mar 15, 2022 |
|
#
?
Mar 15, 2022 21:30
|
|
|
TheNakedJimbo posted:
FROM THE OFFICE OF THE 109th TO WHOM IT MAY CONCERN, After a review of the scenario leading up to the shoot down of an airliner during operations of the morning of June 10th 1990, we fully support our pilots actions and will act (with prejudice) against any further action taken against our pilot. With all due respect to those who pilot a desk, I will tell you, when my squadron is ordered to conduct offensive actions, you are not dispatching negotiators, you are unleashing warriors, who make more life and death decisions in an hour, than in the combined lives of those who would seek to judge them. I abhor the death of innocents, but their blood is on the the hands of the pilots and airlines that chose to occupy that airspace. Understand, my flight were called to engage 7 hostile fighters, over the top of two enemy air defence sites, south of an occupied and defended military air base. And yet, within a mere 20 miles, TWO 'civilian' assets are operating, are you would blame my pilot for his choice? Would a normal pilot look out of their window, see an air war unfolding ahead of them and knowingly fly in to it? would you cross a road without looking? this is bullshit. I ask that the necessary investigations are conducted in to the airlines and pilots, their motivations, political allegiances, and where they received their training. I tell you, as a pilot, their allegiances clearly were not to the safety of their passengers, perhaps they chose to sacrifice these lives for the sake of propaganda? Please take this as notice that pilots of the 109th will not be cooperating any further with investigations in to this matter. The Angry Brit fucked around with this message at 00:11 on Mar 16, 2022 |
|
#
?
Mar 15, 2022 23:44
|
|
|
 Excellent legal banter above, and great job DarkOff for having humor and playing along. War is hell. Next flight day is 19th March! Reminder, this is now afternoon of the Day 1, so 1200hrs on 10th of June. Expect intel soon. It's daylight savings in the US, so take that into account. The world map has been edited and it now has airbases that are knocked out for repairs, destroyed planes, and it has destroyed SAM sites. https://www.google.com/maps/d/edit?mid=1FqSMMT7sxxOPvIzfgQsvfsEDVd7jikQt&usp=sharing
|
|
#
?
Mar 16, 2022 00:29
|
|
|
Dark Off posted:what happened was that i took defensive actions against sam locks and got disoriented. Got calls of bogeys at direction of airliner but altitude call got garbled due to SRS issues. So i was looking for bogeys at previous call height while my flight members were making fox 2 calls. Seeing that there was bogey in front of me that wasnt going down i decided to shoot after IFF:ing contact as hostile. At the time i was also getting locked up by sam site, making decision more urgent. I then defended against several sam launches and managed to takedown sam site by making its proxy fuse detonate over other other sam site. I do agree that this was a disaster that could have been avoided by having no fly zone above target areas, also in hindsight not accounting for civilian air traffic in briefing was a mistake. The Military Advocate General's office has processed your after-action report. I must advise you of two developments. First, the government of Georgia has not issued a formal protest against the downing of their airliner. Second, the airline itself has not issued a passenger manifest. Based on these developments, Legal has issued the following guidelines: 1: Dark Off is not grounded pending further investigation. Be aware that numerous communication errors led to the situation in which Dark Off acquired a lock on a civilian airliner, and these errors must be immediately remedied. 2: The airliner is considered to be a hostile target until a passenger manifest is produced. We have credible intelligence that the airliner itself may have contained Hamas terrorists on the way back from training in the USSR, and that will be Legal's official stance until we obtain evidence to the contrary. The Angry Brit posted:Please take this as notice that pilots of the 109th will not be cooperating any further with investigations in to this matter. Be advised that the Military Advocate General outranks you. The 109th's cooperation is not a matter of your pleasant acquiescence. You are ordered to comply.
|
|
#
?
Mar 16, 2022 00:57
|
|
|
 Good evening, I have in my possession the passenger manifest for the marked civilian aircraft that was shot down by Israeli air force fighters. I would like to remind you that it was not a Georgian airliner you shot down on this day in the current year, which is 1990. Allow me to spin my sign around, if you would be so kind. 
Dandywalken fucked around with this message at 02:46 on Mar 16, 2022 |
|
#
?
Mar 16, 2022 02:42
|
|
|
Dandywalken posted:
https://www.youtube.com/watch?v=VuofaDxa6Oo
|
|
#
?
Mar 16, 2022 02:50
|
|
|
Hearing rumours that nuclear scientist Dr. Leonid Pavel was on board
|
|
#
?
Mar 16, 2022 06:15
|
|
|
Dandywalken posted:
Hmm interesting, so what you are saying is that DarkOff may have single-handedly either delayed, or prevented, the collapse of the Soviet Union? A rallying cry echoes around the USSR and an alternate timeline is created.
|
|
#
?
Mar 16, 2022 07:19
|
|
|
 Aluf Yooper I am happy to report that the 91st Division "Galilee" has made excellent progress this morning. They have caught the Syrian Army unprepared and have been able to move through the UN buffer zone and into Syrian territory with minimal casualties. However, the Syrians hold numerical superiority in the area and the 91st Division is vulnerable to a counterattack. It will be facing the 10th Mechanized Infantry Division, the 3rd Armored Division, and the 11th Armored Division. These divisions have regrouped and are pressing forward on the attack. It is very unlikely without significant air support that the 91st can hold its gains. With our strike this morning on the two nearby airbases we will likely have complete air superiority. Their could be some enemy fighter response from Damascus but this is unlikely as they are likely to be reserved for capital defense. However, the Syrians are expected to have a large force of Mi-24 'Hinds' attacking our ground forces. Most of our tanks causalities have been due to this threat. The 7338 Artillery Regiment did an excellent job knocking out Syrian SAM positions in the area. While friendly aircraft will need to be careful of the air defense networks near Damascus and the Jordanian border, we should be able to attack the Syrian ground forces with little resistance from the ground. 
|
|
#
?
Mar 16, 2022 10:46
|
|
|
jzilla posted:
 Can you comment on any intel beyond the front line armor? Our A-4's may struggle to directly pound tanks so I'm interested in tasking them on softer targets or logistics channels. Any idea on what type of air defenses we may encounter? ZSU-23-4's? 57mm's? MANPAD's? Regarding the A2A threats, I know there were 4 - MIG-29's reported at Damascus International, is this our primary threat or can we expect vectored aircraft out of Lebanon?
|
|
#
?
Mar 16, 2022 16:25
|
|
|
Yooper posted:
Each division has the typical motor pool, fuel depots, ammo dumps, and various other expected parts of a logistical chain. Their approximate locations are marked by a colored square. The Syrian army has limited short range air defenses. All Syrian units will have a small amount of MANPADS and AAA. SAAF MiG-23s may respond from Al-Dumayr. They will likely be emboldened by their recent success at shooting down an entire flight of F-15s. I do not anticipate any hostile fighters coming from Lebanon.  The order of battle for the three divisions is as follows: 10th Mechanized Division:
|
|
#
?
Mar 16, 2022 18:41
|
|
|
jzilla posted:
Excellent! Thank you. Precisely what I was looking for. IAF IT is currently updating my computer to Windows 3.0. Once this has concluded I will get mission tasking out. I'm told it shouldn't be much longer...
|
|
#
?
Mar 16, 2022 19:07
|
|
|
 4x F-15C Eagle Element 1: Dodge 2-1: ninjahedgehog aka wrathcough Dodge 2-2: Karrick Element 2: Dodge 2-3: Dodge 2-4: Tythas DAY 1 DEBRIEFING Well, it didn't go great -- but on the upside, we've now all got valuable first-hand experience in desert survival and avoiding Syrian Army patrols on our long hike back to the border. I really don't want to have to drink my own piss again. Our mission Escort the strike package into the AO, ensure air supremacy over the target area, remain on station for potential intercepts, and then escort the strike package back home along the exfil route once Earthquake had suppressed enemy SAMs. What happened Fortunately, the Operations Goon logged pretty much our entire flight, so I'll re-link his video here with a timestamp and relay its events from our flight's perspective. https://www.youtube.com/watch?v=C2gUjOYt6T4&t=77s Dodge 2-1 saw three hostile contacts on radar and assigned targets to the rest of the flight, but was unaware Dodge 2-3 had burned ahead to give his missiles more energy. 2-1 mistakenly identified the first fireball he saw as a MiG-23 kill, but it was in fact Dodge 2-3's wreckage -- he had pulled too many Gs attempting to maneuver his plane and had ripped his own wings off. Shortly after this, Dodge 2-2 was shot down by one of the MiGs' SARH missiles. Both 2-1 and 2-4 managed to fire a Sparrow each, but both missed, and we entered the merge with three MiG-23s. 2-1 shot down one Flogger with a second Sparrow -- narrowly avoiding a hostile R-60 in the process -- while 2-4 engaged the other two MiGs. 2-1 turned in to assist and shot down another Flogger with a Sidewinder. However, while 2-1 was attempting to clear 2-4's tail of the third MiG, a fourth bandit entered the fray and shot him down. 2-4, now alone, was quickly overwhelmed and shot down, despite a valiant attempt at a guns kill. What went right Not much -- we managed to score two MiG-23 kills, but at the cost of all four of our Eagles. Not a good trade. What went wrong Situational awareness was a huge problem from the moment the mission began. The F-15C lacks a datalink and the F10 map was set to "own ship only," so we were largely unaware of our position in relation to the rest of the package. Our initial BVR intercept with the MiG-23 flight went poorly as well. Dodge 2-3 burned ahead of the flight, limiting his ability to coordinate with his wingmen, but this was moot anyway as he shortly lost his wings. Shortly thereafter, Dodge 2-2 was shot down by a SARH missile and made no attempt to perform defensive manuevers or release countermeasures, indicating that he was not aware he was being fired upon. This meant that by the time we entered the merge, it was 2v3, which quickly became 2v4 as another Flogger entered the furball- largely unwinnable odds. Despite scoring two kills, Dodge 2-1 and 2-4 were overrun. This meant that Colt flight was completely unprotected over their AO and were shot down to a plane -- a complete mission failure on the part of Dodge 2. Where to improve Situational awareness -- I need to be more proactive in determining our position in relation to the rest of the package. We were out of place to cover Colt flight as they engaged the SA-6 site, resulting in their deaths to MiG-21s they were not in any position to engage. This will likely involve more active communication with Sling Shot, but we'll need to find a balance so he isn't task-saturated keeping every flight in the right place even when they're idle. BVR -- Dodge 2-2, by all rights, should have survived until the merge even if he could not get a shot off. I recommend we all re-familiarize ourselves with the F-15's RWR system to determine when there are incoming missiles inbound, and practice defensive maneuvers against SARH missiles. BFM -- Dodge 2-3 ripped his own wings off in the merge, reportedly with zero foreknowledge from his automated over-G warning system. 2-4 also underperformed in the dogfight by attempting to turn too rapidly, quickly losing energy and becoming a sitting duck for the enemy MiGs. Short-range knifefighting is not the Eagle's strong suit but it will likely be necessary again in the future, so we'll need to familiarize ourselves with the F-15's optimum turn rate, G-limit, and maintaining situational awareness even in a chaotic dogfight. Campaign aerial victories Thanks to DCS server lag, Tacview is inconsistent as poo poo -- my feed showed Jae missing his first Sparrow and Tythas hitting, Operations Goon showed Jae hitting and Tythas missing, and Tythas's feed showed neither scoring any hits. For consistency's sake, we'll consider Operations Goon as the official record. ninjahedgehog: 2x MiG-23 Jae: 1/2x MiG-23 (split with Dodge 1-1 or 1-2, unsure) ninjahedgehog fucked around with this message at 20:06 on Mar 16, 2022 |
|
#
?
Mar 16, 2022 19:45
|
|
|
Prawned posted:Hmm interesting, so what you are saying is that DarkOff may have single-handedly either delayed, or prevented, the collapse of the Soviet Union? The New Union Treaty gets ratified early and Georgia stays on board?
|
|
#
?
Mar 16, 2022 20:01
|
|
|
|
| # ? Jun 12, 2024 11:18 |
|
Yvonmukluk posted:The New Union Treaty gets ratified early and Georgia stays on board? An error so bad it negated our win in the last campaign too
|
|
|
#
?
Mar 16, 2022 20:03
|
|