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.
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.
The following section is comprised of almost exclusively ooRP knowledge that players are required to have in order to fully understand Task Force Akhetaten membership.
Ranks & Warship Access
Task Force Akhetaten (TFA) employs the standard Liberty Navy Forty-Sixth Fleet rank structure, found in the Fleet's information page. All ranks ranging from Cadet to the Admiralty are attainable for members of TFA through standard promotion procedures, no different to those outside it.
Within Task Force Akhetaten, however, access to all ship classes is granted to all members, through the use of shareds. Members whose characters are a sufficient enough rank to command their own capital ship class may do so - as per the Forty-Sixth Fleet's generalized rank restrictions, while characters without the sufficient rank may be part of the crew of a shared capital ship. The task force offers a wide array of capital ships, all listed below (Warship Database section), that characters of any rank have access to.
Every shared capital ship has a set of three roleplay-able positions. All of them are filled by default with pre-made characters that can be found in the relevant shared ship discord channels. These characters have been thoughtfully crafted and each of them covers a different array of player skill. Below is a list of the roleplay-able positions:
⊳ Commanding Officer - [CO]
The officer in command of a capital ship. Reports to TFA Command.
⊳ Executive Officer - [XO]
The officer that's second-in-command of a capital ship. Reports to the CO. If the CO isn't present, reports to TFA command.
⊳ (Chief) Communications Officer
The officer in charge of communications aboard a capital ship. Reports to either the XO or the CO. A (Chief) Communications Officer cannot be roleplayed on a capital ship with no commanding elements being present. While roleplaying as a (Chief) Communications Officer, if a commanding officer's presence is requested you are obliged to roleplay as an officer who holds one of the two above positions.
Every rank offers certain permissions related to capital ships. Certain ranks, such as Ensign, are only able to fill in for the communications officer position on any capital ship. Other ranks, such as Lieutenant Commander, are allowed to fill in the chief communications officer position on all capital ships while also being able to be the commanding officer or executive officer of up to cruisers. Higher ranks, such as Commander, do not typically fill in for the (chief) communications officer position on any capital ship, but can take up the position of commanding officer or executive officer for up to battlecruisers.
For better understanding of what the above imply, a field example will be provided.
You are roleplaying your character, a Lieutenant, aboard the 46th|TFA-LNS-Providence, a battlecruiser. From your character's rank chart above you can see that your character is only allowed to be in the comms officer position aboard a vessel of this class. You are free to roleplay your character aboard that vessel in that position, but if a situation arises where a commanding element needs to step in, you must visit the relevant discord channel to see what the commanding elements (CO and/or XO) of the Providence are. From there, you can either pick Captain Lynn Adams or Commander Jack Walker to roleplay as during the situation that requires it.
Every character in Task Force Akhetaten may own their own snubcraft. All fighters or bombers within TFA must be codenamed, and the characters behind them must keep their identities secret at all times, regardless of who they are interacting with. Requests to reveal a pilot's identity must be forwarded to the task force's first in command (Maria Uhmen) and are to be handled by her. Of course, all TFA personnel have access to files related to TFA personnel and thus know, at all times, which operative is which officer by their full name. Two TFA characters meeting in-game will always know who is who, regardless of codenames being used.
Additionally, players who wish to log a shared snubcraft must, at all times, either roleplay their own character by their codename, or roleplay as the character who's codename is the snubcraft's shipname. Obviously, 46th members who have access to TFA upon their request are only permitted to roleplay the latter example, as they do not have personal characters. Here's an example of the above;
When logging the shared 46th|TFA-Umbral.03 you have two options:
You roleplay as your own character, but only identifying yourself by your character's codename. For example, Operative Lavinia operating from the Umbral Three snubcraft. As mentioned above, other members of TFA will know who Lavinia is by their full name, but are to not disclose such information. Operative Lavinia herself can only disclose this information to non-TFA personnel only upon the flag officer's approval.
You roleplay as Operative Umbral Three, a generic Task Force Akhetaten operative, and not your personal character. Obviously, you will never be asked for your real identification as there is none.
Below you will find a list of all characters actively being a part of Task Force Akhetaten; personal and shared ones.
For the purposes of convenience the top table has a list of all members of TFA while the table under it has the characters that have been made for usage on the shared ships.
Task Force Akhetaten has the additional below members, who are already-existing members of the Forty-Sixth Fleet who have chosen to enter TFA without personal characters and are able to only log shared ships:
With the Liberty Government approving Vice Admiral Maria Uhmen's request for the Akhetaten as well as Task Force Akhetaten receiving extended zone of operations as well as complete operational independency, Uhmen saw fit to separate the task force into two task groups in order to ensure that the task force remains a strong factor as far as the defense of Liberty sovereign space is concerned. With that in mind, Task Group Akhetaten One and Task Group Akhetaten Two - referred to as TGA One and TGA Two respectively - were formed.
⊳ TGA One
Commanding officer: Vice Admiral Maria Uhmen.
Spearheaded by the Akhetaten, and escorted by various lighter assets of the task force; exclusively cruisers and below.
Operational independence has been granted to the Akhetaten and is applicable to all assets of this contingent that are escorting the battlecruiser.
Often operates outside Liberty space but is not restricted from operating within Liberty space and being employed in standard Navy operations.
Is in direct coordination with allies local to the active area of operations.
Focuses on intelligence gathering and surgical strikes against enemies of the Republic.
⊳ TGA Two
Commanding officer: Captain Luisa Chiavallati.
Spearheaded by the New Jersey, and contains the heaviest assets of the task force; all battleships, battlecruisers as well as their garrisons.
Standard Liberty Navy rules of engagement are employed.
Operates only under standard Forty-Sixth Fleet etiquette and area of operations.
Heavy firepower is employed to ensure combat superiority against threats towards the Republic.
The two contingents make up Task Force Akhetaten, and thus direct command of both contingents falls to Vice Admiral Maria Uhmen. However, due to the Vice Admiral's inability to effectively command TGA Two, Captain Chiavallati was assigned in command of that contingent due to her experience and the trust Uhmen has in her. Chiavallati has received enhanced permissions and her calls are only to be overwritten by members of the Admiralty under extreme circumstances. Chiavallati has full control over assets belonging to TGA Two, and reports directly to Uhmen.
This effectively makes Luisa Chiavallati the second in command of Task Force Akhetaten.
Below is the detailed roster of TGA One and TGA Two:
![[Image: FQ54zPL.png]](https://i.imgur.com/FQ54zPL.png)
![[+]](/forums/images/collapse_collapsed.png "[+]")
Image Form![[Image: aAWQQFs.png]](https://i.imgur.com/aAWQQFs.png)
![[Image: OTSZkvc.png]](https://i.imgur.com/OTSZkvc.png)
![[Image: jY8ax9L.png]](https://i.imgur.com/jY8ax9L.png)
![[Image: 330px-Flag-liberty.png]](https://discoverygc.com/wiki/images/thumb/f/fe/Flag-liberty.png/330px-Flag-liberty.png)
![[Image: 5SPjwNr.gif]](https://i.imgur.com/5SPjwNr.gif)