Jul 10

Operation: Typhus

Category: News

Task Force: Typhus was formed and launched due to a large Warlord threat in the Ios System and the neighboring Yetton System, as Task Force: Typhus was only meant for the Ios System, Task Force: Iron Sweep was made for the neighboring Yetton. As the Ios System had not been heard from for some time, the Task Force was sent at the behest of Grand Admiral Japheth. NAVCOM didn’t have any info on the Ios System, therefore Typhus was going in blind, that is why the Naval High Command supplied the Task Force with a venerable amount of ships and support craft, including Viper Squadron. The following is quoted from a Viper Squadron Member’s datapad:

“At the behest of Grand Admiral Japheth, a Task Force Typhus was also created with the intent of heading straight to the Ios system. Their main goal was to investigate the situation in force, but also retake the system if possible. They would travel along the eastern frontier, and arrive from roughly the same direction as any would-be attacker.”

Even though the Warlord was not identified to the public at first, it was rumored to be Imperial Splinter Warlord Drakan, who has been reeking havoc on the Vast Empire Eastern Frontier. The Task Force initial purpose was to discover the fate of the Ios Imperial Garrison, which was unknown at the time (that makes up for the huge amount of allied forces). The inital start and forming of the Task Force was when a Code 0 Alert from the Yetton System Listening Outpost: Viverro was recieved. Since the only hyperoute into the Yetton System is through the Ios System, Naval High Command sent the Typhus Task Force to the Ios System. When Captain Dak Zalter wrote a full report of the Ios and Yetton System and then published it at 5 O’clock Vectra standard time, it released some insight to the battle:

“When the NHC felt the need to have a forward bases protecting the eastern frontier of our space, the Ios system was chosen to be occupied and developed into a ‘fortress’ system – this is one of the many that have been built, and more are being planned to be bult.

The small settlement that we created was locatest on Ios Delta, the only planet closest to the hyperspace lanes that lead into Vast Empire Territory. We brought in a smaller version of the Rendili StarDrive Space Dock was towed into orbit and two Golan II space defence platforms, they we’re strategically placed near the dock. At the beginning of this ‘project’ if you will, Ios became a powerful outpost and garrison

But In order to maintain efficient communications between this forward out post and the rest of the Empire, the Yetton system was chosen to also be occupied and developed to include a relay network along our Easter Front. The hyperspace lanes in the area meant that you could only reach the Yetton System either by coming from Vast Empire space, or by going through the Ios Hyperspace Lanes. Our theory was that only a smaller garrison was needed at Yetton, as any would be invader would first have to go through Ios, or one of the other border outposts. We were proved wrong.

In the year following the collapse of the Galactic Empire upon Palpatine’s death, at the hands of the Rebellion, an Imperial Warlord by the name of Drakan fled the known galaxy, and made his own ‘mini-empire’ in space not far from that of the Vast Empire’s. We did not know this, this is a fatal error.

Drakan then wanted to expand his holdings, his eyes fell upon the vulnerable Ios System, distant from the Vast Empire capital and also a hyperspace lane into the profitable Yetton System. His eyes fell upon the Bannth, and Yetton Systems as well. War would soon span the Eastern Frontier.

With his eyes set on Ios, along with the profitable Bannth asteroid facility further up the Eastern arm, Drakan assembled an invasion force in secret, unknown to our intelligence. And unknown to us, his mischievous plan would start with the open Yetton System, as it was barely guarded by any Vast Empire Naval Forces, or Army Forces…”

The full brief is available at our Center, you may visit one of those locations. If you have any information regarding Drakan, than please – report it to the Vast Empire Officials immediately. Anyway, back to business. When the Task Force arrived in the system, a battle pursued. It was discovered that the Ios Outpost was completely demolished, and the forces accompanying the Outpost did not meet a better fate. The Warlord Forces fought valiantly, but they met the same fate as the outpost-KIA. Except for some of the ships, this was fault to two ISDs entering the system and letting the ships retreat. The last piece of info was published at the end of the Captain’s brief book:

“…Ultimately, the Second Battle for Ios was a victory for the Vast Empire. But this victory came at a price. The task force had been decimated, the instillations at Ios ruined, and there was now a huge gap in the eastern front. The Drakan crisis had lived up to its name.

Ios would remain a mystery to our tacticians for some time after the incident. The official reports from both the Typhus and Iron Sweep Task Forces stated that, at the very end, two new Imperial-class Star Destroyers entered the system. Admiral Piatt, Analysts of the Eastern Front has assumed they were part of Drakan’s fleet, and that the warlord had sent reinforcements to continue the push into VE space.

It’s unclear however as to what happened. All that has been shown from the logs of the Serenity, a Dreadnought that entered the system after Typhus’ retreat that the two ISDs retreated. Their reasoning is unknown.

This made our analysts puzzled, as combined the two Imperial Star Destroyers’s had enough firepower, if now more to wipe out what was left of the fleet, the Serenity powered up her weapons, and no response came from the enemy. Naval High Command has issued that there will probably be counterstrikes, and it probably wont be long until the eastern front was at war once more. This is why we are issuing a Code Black on the Eastern Front, and sending reinforcements to the East side of our space…”

No comments

No Comments

Leave a comment

You must be logged in to post a comment.