The Tomb of Galahad

From Australis Ultima 30k
Jump to: navigation, search

The Tomb of Galahad
Galahad Badge Site.png

Honour Badge:

The Device of Galahad


The Tomb of Galahad


Galahad Ribbon.jpg

Campaign Detail

Type: Campaign
Date: 003.010.M31
Sub-Sector:Helix Cluster
System: AL-NH-1574
Planet: System Wide
Victor: Unresolved
Draw: n
Influence: 0


Loyalists Involved In The Conflict


Crusade Fleet Forces Involved In The Conflict

Traitors Involved In The Conflict

Campaign Summary

Prelude to War

Sometime before the Heresy erupted throughout the Imperium, Crusade Fleet 1574 was recorded to have refitted and prepared for deep space travel at the Savage Naval Yards in the Savage Reach Sub-Sector. Shortly after a small notation was recorded in the Kildrech System status report of the Fleet passing through their system and meeting up with an Expeditionary fleet led by Rogue Trader Castus Tharr before exiting the Sub-Sector all together.

The fleets traversed an, as yet, unexplored Warp lane which led to a highly isolated Sub-Sector, latter named the Helix Cluster. While Castus and his expeditionary fleet established a base of operations on the world of Corabie, the first system linking to the Warp Lane, Crusade Fleet 1574 prepared to continue its exploration of the Sub-Sector. Before leaving the Corabie System however, the Fleet laid down a series of transmission buoys leading back to the Savage Reach in order to overcome communication difficulties experienced by the unstable and unusually long Warp Lane, something which proved to be a prophetic action in the next few years. Unbeknownst to Imperial forces within the Helix Cluster, the Heresy had erupted within the Imperium, before news could spread to the remote outpost, warp storms closed the already unstable lane back to Savage Reach, severing the forces connection with the greater Imperium except for one-way status reports sent via the buoys.

Leaving Castus to establish his capital Fleet 1574 pushed deeper into the Cluster, sending scouting ships to all of the far flung stars but finding little of note except for those located closest to the core of the spiral. One such desolate system, designated AL-NH-1574, was ear marked for further investigation due to the presence of a gas giant which may provide valuable resources for the Sub-Sectors growing infrastructure, even with a harsh F-Class star. As the Fleet moved on, a splinter outrider task-force was sent to conduct the investigation, traversing the wild space between systems and engaging the few remaining Xenos hold outs this close to Corabie relative space.

Arriving in-system at AL-NH-1574, the task-force conducted a high level scouting of the solitary planet, declaring it compliant after finding no life signs, designating the gas giant 1574-78. A closer investigation of the planet then commenced to determine the viability of mining operations in and around the planet, it was then that the task-force discovered the Ark.

Situated in a Lissajous orbit at Lagrange point 2 between the planet and its star, a massive Ark Mechanicus ship lay seemingly dormant. Previously undetected because of it powered down state and hidden from general view by its stationary orbit so close to the planet the ship would have continued to have gone buried had it not been for the task-forces closer inspection. Having been notified of the find, the main Crusade Fleet began a lumbering reversal of their path to return to this momentous discovery, although it would be years before they arrived due ongoing Xenos resistance.

In the meantime the task-force began preliminary investigations of the ship. Massive in size, stretching many kilometers, the Mechanicus vessel dwarfed even the largest Battleships in the Fleet, such were the nature of these rare behemoths. Unable to raise any form of response from communications but confirming that there was still power via the observation of stabilisation thrusters keeping it in orbit, the task-force opted to establish a small station some distance away from the Ark for safety.

In the time waiting for the main Fleet, Klevestav Station grew as the outpost became more permanent and scouting expeditions were sent into the Ark. During the time though, very little was found, the ship was far too large for such a small force to fully secure and explore and most of the vessel was in some form of lock down. By the time the Fleet arrived all that had been confirmed was a number of main boarding points had been mapped and that there was no sign of the Ark’s crew or what had happened to them. The ships name though had been uncovered; Galeas, an ancient version of the mythical Terran Knight better known as Galahad. Confirming the find, the Fleet commander sent the news back to the Imperium; such a miracle find would surely attract a lot of attention!

The attention the message received, however, was not what he had anticipated. Sending the report through standard Imperial Crusade encryption over the open communication buoys, the commander had no idea that such forms of secrecy was no longer used as both sides of the Heresy had the means of decryption. Both factions did indeed receive, decrypt and digest the message and its potential. The discovery of an intact, functional Ark Mechanicus was nearly unheard of. The technology and firepower contained within such ships would rival most things that the Imperium could deploy even during this powerful age, but more importantly, the potential for STC fragments was high.

Responding to the broadcast, both factions mobilised huge fleets in the Australis Ultima Sector and deployed to Helix Cluster using the buoys as anchor points in the warp storms. Engaging each other at Corabie and clashing with the incumbent Rogue Trader Governor, smaller fleets broke away to make the push to AL-NH-1574.

Upon translating into System, Crusade Fleet 1574 only had time to send a single welcoming message before the two arriving forces opened fire on each to the horror and bewilderment of the garrisoned imperial forces.

The Heresy had come to the Helix Cluster.

Battle Reports

Imperial Search....No Result

(Press the CREATE button to lodge a single Battle report, do not modify the name, you can lodge a Skirmish report within this Battle Report)

Skirmish Reports

Imperial Search....No Result

(Press the CREATE button to lodge a single Skirmish report, do not modify the name)

Campaign Pictures