This section aims to provide the most basic and bare-bones summary as well as the history of Task Force Akhetaten. The aim of it is to bring people up to date with not only what the task force aims to do but also how and why it was founded as well as how it evolved over the years.
~Tenshi
Brief Summary
Task Force Akhetaten, a Liberty Navy battle group tasked with assisting the LNS-Akhetaten and assuring the safety of the warship's operations, has seen multiple deployments during its time in active service. With Battlecruiser Akhetaten expanding its roles within the Navy, the task force has found itself undertaking duties far beyond its original mandate. With overwhelming firepower, unparalleled cyber-warfare capabilities, rapid and effective deployment, as well as excellence in research, development and intelligence gathering, Task Force Akhetaten has made quite a name for itself, well within reason.
This has rendered Task Force Akhetaten as one of the most well endowed, widely known, capable and feared Liberty Navy Divisions.
History
The LNS-Akhetaten, serving under the Liberty Navy Fifth Fleet at the time, played a role of utmost importance during the campaign against the Insurgency's forces. Being integrated into LIBWESTCOM as per the Fifth Fleet Admiralty's orders, the warship's main objective was to ensure the security of the Libertonian border with Bretonia and Crayter. Pooling together what little intelligence they had, the Insurgency was able to piece together rumors of a task force operating on the border, lead by a vessel of utmost importance to the Republic. The Insurgency's forces saw an opportunity to attack the Akhetaten's convoy directly, during the warship's prolonged stay at the system of California, to prevent the LNS-Delaware's advance into Kansas - and inevitably Vespucci - from receiving any more reinforcements.
The goal of this attack was to gather intelligence on the patrol paths of the Akhetaten's battle group so that they can later down the line launch a larger-scale invasion in the system, a goal which was met as surviving Insurgency fighters made it back to Veracruz and the Insurgency's intelligence teams begun analyzing what information was gathered on the task force's flight plans.
During the warship's deployment into California at the year 829 A.S. and while the war with the Insurgency was fully on-going, it was decided by the Fifth Fleet's Admiralty that the Akhetaten is to resupply at Norfolk Shipyard in order to be deployed in the Kansas system alongside the LNS-Delaware to spearhead the advance into Vespucci alongside the Forty-Sixth Fleet.
Notably, one of the most important series of events that lead to Task Force Akhetaten's founding were the events shortly after the loss of the LNS-Delaware. With the Akhetaten by her side since day one of the advancement into Kansas, the warship was in grave need of resupplying and Commodore Maria Uhmen ordered the Akhetaten to be pulled away from the frontline prior to the tragic fight, unbeknownst to her what the result would be. With the LNS-Akhetaten now back in Liberty core space, the warship yet again returned to her duty as the spearhead of LIBWESTCOM.
A direct transmission from Operative Draco of the LSF would quickly disturb the peace and quiet that the crew was used to, after their pulling-back from the frontlines. The transmission revealed that forward intelligence suggests a small Insurgency battlegroup to have breached the blockade and be headed for Magellan, information which was later on forwarded to the entirety of the Liberty Navy by Commodore Maria Uhmen.
It appears that the Navy's defeat in the system not more than four months ago would finally become a consequence and a major thorn on the Akhetaten's side. With all of the intelligence properly analyzed and with only one goal in mind, the Insurgency launched a full scale assault in the system to attempt to destroy the LNS-Akhetaten. Luckily, Operative Draco's forewarning gave the Navy enough time to scramble a small strike force in defense of the vital warship. Fortunately for the LNS-Akhetaten and her crew, the warship survived but sustained heavy damage and casualties in the process.
The bloodbath of California was merely a bad omen of what was to come, and Commodore Maria Uhmen was well aware that the Akhetaten would not survive another direct hit. The vessel's value to the Republic is no longer a secret, and her status has now became a danger to both the ship and her crew. Action had to be taken.
Task Force Akhetaten, formally founded under the command of the Fifth Liberty Navy Fleet by Fleet Admiral Sophia Cleveland (May 28th, 829 A.S.), was an attack group established with only one goal; the defense of the LNS-Akhetaten at any cost. The task force saw many deployments, following its flagship and ensuring the safety of the Akhetaten's operations, and would take part in many operations. Undoubtedly the highest priority deployment followed after a direct order by Fleet Admiral Cleveland that saw the deployment of Task Force Akhetaten to the Vespucci front, to aid Carrier Ohio against the Insurgent forces. Months later, and after multiple conflicts and casualties, the Akhetaten along with her task force made their return to friendly grounds, this time to remain there. The task force had suffered severe losses in the field, and Commodore Maria Uhmen, disheartened as she was at the time, deemed it fruitless to try and repair what few ships made it back alongside the flagship. It was thus decided by her for Task Force Akhetaten to be disbanded.
With the Akhetaten now serving under the Forty-Sixth Fleet, a growing and well funded establishment, and with Project: Akhetaten finally reaching it's conclusion, the recently promoted Vice Admiral Maria Uhmen saw reason into re-instating Task Force Akhetaten into active duty, and she did, as her first official command after her latest promotion.
With the Task Force now back stronger than it ever was before, it's duties and responsibilities grow even larger.
![[Image: zHA8qW0.gif]](https://i.imgur.com/zHA8qW0.gif)
![[Image: vy04L0s.gif]](https://i.imgur.com/vy04L0s.gif)