FANDOM


Previous battle: Battle of the Inner Caspian Worlds
Next battle: Siege of Trinumvira
Battle of Ketterslea
Conflict: Caspian Annexation Campaign
Date: 8 ABY
Place: Ketterslea; other points in the Union
Outcome: Undetermined
Combatants

Emblem empire starburst
Galactic Empire

60px
Caspian Democratic Union

Commanders

Warlord Jarl Rellik

Sar Admiral Salonika Batrad

Strength

- HIMS Sanguinary
HIMS Millinix

- CMKS Coventry
- CMS Groton

Casualties

Indicative of how the occupation of Caspia was progressing, the Battle of Ketterslea was a single battle representative of four or five smaller skirmishes in Union space on the approaches to Caspia. In each of these insular fights, Caspia employed tactics last used by the Rebel Alliance and achieved some degree of success. They were unable to make any headway at reclaiming territory, however, and only made the Empire more resolved to root out the source of Caspian resistance.

At Ketterslea, several Caspian units coordinated just enough to hamper the Imperial resupply and reinforcement effort before being overpowered by the escorting warships. The action here was fast, direct, and ruthless, but the results of this battle are now considered to be a contributing factor to the outcome of the Siege of Trinumvira.

Prelude Edit

The very seeds of this battle were sown during the second day of the Campaign, wherein a sizable convoy of nearly two dozen heavily-laden Imperial supply ships arrived in the Kett star guided by several Imperial warships, among them HIMS Sanguinary, HIMS Millinix and HIMS Dark Dispatcher. These ships were carrying the follow-up materials with which to occupy Caspia after the shocking, overwhelming attack the day prior.

Grasping At Straws Edit

Twenty Minutes of Fury Edit

Recovery and Retreat Edit



From SW1ki, a Wikia wiki.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.