Curse Fortizar Battle, Part II: Combat and Chaos


Earlier today, a Fortizar belonging to Freedom Among the Stars entered the vulnerability timer for its Structure section in the system of XX9-WV, a system in Curse connecting the region to FAS-controlled sovereignty in Scalding Pass.

Previously, the Fortizar’s Armor timer had met with unorthodox strategies in use by the defenders to make up for a lack of numbers. However, for the kill timer, FAS made contact with DRF and RED Alliance forces, bringing in nearly 400 additional defenders for a more standard engagement.

Local was seen peaking at over 1300 as numerous parties flooded into the system. As FAS and their allies duked it out with Imperium forces from Initiative, NCPL and Bomber’s Bar entered the fray as third party forces.

The various fleet compositions were largely as follows:

FAS/BSOD : Rail Nagas
DRF : Machariels
SOLAR : Interceptors
RED Entities : Maelstroms
Initiative. : Ravens, Scorpions
Mercenary Coalition : Rail Nagas
NCdot : Rail Rokhs
PL : Arti Lokis
Bomber’s Bar : Eponymously, Stealth Bombers

As the fight raged on, Bomber’s Bar claimed several dozen INIT. Ravens to a well-executed bombing run. With merely 15 bombers, the majority of the attacking force was swiftly and abruptly removed from the field. The sudden loss of the battleships is believed to have been the turning point in the battle, and the Fortizar was later seen successfully completing repairs. With the Fortizar secure and the attacker’s objective lost, the groups began to extract from the grid.

A bloody and destructive butcher’s bill has begun to reveal itself, with upwards of 110 billion isk in ships destroyed and more kill reports streaming in. This number is expected to rise as reports continue to make their way in.

The battle report can be viewed here. Please note that the sides can be difficult to ascertain with the volume of third and small-party entities, and as such may be partially inaccurate. Corrections may be made as new information becomes available.

Editor’s Note: An earlier version of this article incorrectly had NC. in Nagas. This has been corrected.

Let your voice be heard! Submit your own article to Imperium News here!

Would you like to join the Imperium News staff? Find out how!


  • Muul Udonii

    Fairly sure NC. were in Rokhs, not Nagas. Didn’t lose any either. Was a really fun fleet.

    November 15, 2017 at 1:35 AM
    • Rhivre Muul Udonii

      will update that, thanks

      November 15, 2017 at 5:16 AM

      That is never getting old. 😉

      November 15, 2017 at 5:13 PM
      • Daito Endashi Nine

        Aw man this is glorious… thank you so much for that!

        November 15, 2017 at 6:45 PM
        • Nine Solo Daito Endashi

          You are welcome!
          Every time I see a Rokh, I listen to this song.
          I think, the Rokh is the most badass battleship of all the battleships in EvE ^_^.

          November 18, 2017 at 10:16 PM
  • Doughlas MacAlister

    These fights are such a cluster fuck that it is not even funny. Imperium is red to FAS NC/PL and blue to Red. Red is blue to imperium and blue to FAS, NC/PL and red to TEST. Imperium has no agression pact with TEST. This is going to end in major diplomatic meltdown, of relationships on all sides.

    November 15, 2017 at 9:04 AM
  • Rhivre

    the smartbombing Mallers combined with Bombers Bar made the BR a complete mess

    November 15, 2017 at 3:07 PM
    • Nine Rhivre

      I was there! 😉

      ..flying an arty Naglfar and a bunch of cynoceptors. The points I made is from the one of our videos captured. Truly, it was a real bloody mess XX9 didn’t seen for a looong time.

      November 15, 2017 at 5:12 PM
  • Nine Solo

    Well… those Naglfars were the main reason the battle took place 500km+ away. Thats our version if you ask me ^_^.

    But, in true, we were a little bored. The only fleet that actually entered close range around Fortizar – was an Imperium abaddons+phoons. They came 2 times, and both times had to warp out – from bombrun 1stly and from DRF machs threat 2ndly.

    Ravens did they part trying to keep on the edge of 300km zone, but this time, we had a refit ready (+1 sensor booster which makes 2 of them) and that gave us a 300km lockrange on overheat.
    That was enough to shoot down INITs Damnation and 2 Eoses. Without info-links the Ravens could not shoot a fortizar, end the citadel has repaired. There was a TiDi and it favors defenders a lot, especially if attackers use Cruise Missiles with delayed damage.

    Actually, that refit with second sensor booster we made in the first battle also – right in the middle of the fight, when we realized the flaw in our stratagem, I made a quick delivery of additional sensor boosters to naglfars shared fleet hangars, but it was already too late to prevent attackers from dismantling fortizar armor.

    November 18, 2017 at 10:12 PM
  • Nine Solo

    Also, I can tell you more about the actuall fight since I was there chilling in tether range on alt and bubling our enemies on main.

    After the citadel was repaired to fullHP, the RED maels warped to MC nagas partially caught in bubles 450-500km on top of Fortizar. MC nagas escaped, but the Bjorn Bee mallers warped in close to maels, and the DRF machs followed not very long after… that how the bloodbath started.

    If you interested, you should see the video from one of the maelstorms pilots, Canarisis:

    November 18, 2017 at 10:26 PM