Bravo Fleet
Difference between pages "Task Force 17" and "Exodus"

Difference between pages "Task Force 17" and "Exodus"

From Bravo Fleet
(Difference between pages)
 
(Ship widget update)
 
Line 1: Line 1:
{{icons|bfc}}{{Task Force
{{Starship
| name = Task Force 17
| name = Exodus
| seal = [[Image:TF17Seal.png]]
| prefix =
| mandate = Deep Space Operations
| image =
| headquarters = [[Deep Space 17]]
| registry =
| url = [http://www.bravofleet.com/group/task-force-17 Main Website]
| class = Borg Sphere
| co = [[bfms_char:15254|VADM Elizabeth Hayden]]
| type = Ark
| xo = [[bfms_char:83715|CAPT Khim Samnang]]
| affiliation = Unimatrix Zero
| logo = [[Image:17-logo.png]]
| status = NPC
| commission = 2375
| decommission =
| destroyed = 2401
| unit =
| taskforce =
| taskgroup =  
| squadron =  
| mothership =  
| homeport =  
| role =
| co = Brynn
| xo = Aramook
| dedication = Nothing happens unless we dream
}}
}}
'''Task Force 17''' conducts deep space exploratory and diplomatic missions far beyond [[United Federation of Planets|Federation]] borders from its headquarters on the edge of charted space, [[Deep Space 17]]. As the Fourth Fleet unit tasked with long-range missions of discovery, Task Force 17 has ships deployed in such distant corners of the galaxy as the [[:Category:Delta Quadrant|Delta]] and [[:Category:Gamma Quadrant|Gamma]] Quadrants. Starships and crews assigned to this task force are specially equipped and trained to operate with little support from [[Starfleet]] infrastructure.


==Objectives==
[[File:Daedalus meets Exodus.png|thumb|''USS Daedalus'' Meets ''Exodus'']]


* '''Manage''' the operations of Federation ships far from local space, as well as those isolated in the Delta and Gamma Quadrants.
Encountered by ''[[USS Daedalus]]'' in 2401 as part of the Fourth Fleets investigations into increased [[Borg]] signals, ''Exodus'' was the home of a group of [[ma:Unimatrix_Zero|Unimatrix Zero]] survivors following the Borg Collective's restructure caused by the release of the [[ma:Neurolytic_pathogen|Neurolytic Pathogen]].
*'''Explore''' deep space beyond Federation territory in the four quadrants.
*'''Establish''' peaceful relations with native species.
*'''Expand''' Federation interests in deep space, including securing friendly trade routes and exchanging in scientific knowledge with other peaceful nations.


==Overview==
When ''Daedalus'' encountered the vessel it was severly damaged as a result of its journey from Borg territory, those aboard were considering abandoning the vessel when they arrived.
'''To boldly go where no one has gone before''.' These legendary words have long been repeated and paraphrased by successive generations of explorers and scientists seeking to fulfill one of the core mandates of the Federation Starfleet’s philosophy and are etched into the minds of every Starfleet cadet and many Federation citizens. In a time preceded by great galactic strife and conflict, Task Force 17 of the [[Fourth Fleet]] seeks to embody those principles once more as Starfleet recovers from the atrocities and existential threats posed by the Dominion War and the attack on Mars, to once again rediscover its sense of wonderment and exploration, and return to exploring the final frontier.


Armed with the same ethos and mandate that guided the historic ''Constitution''-class vessels and their five-year missions of the twenty-third century, Task Force 17 is committed to exploring the farthest reaches of deep space. With unprecedented access to both the Gamma and Delta Quadrants, Starfleet vessels return to not simply protect citizens and defend against ideological threats, but to seek out new life and new civilisations, in whatever form they may be and wherever they may reside. To this end, Task Force 17 has dispatched a number of starships, manned by intrepid Starfleet officers from across the Federation and beyond, to make this foray into the unknown.
== Service History ==


By nature of the enterprise, Task Force 17 vessels very often find themselves alone, operating far from the vestiges of Federation society or Starfleet support, relying strongly on their guile, character, and one another to survive and flourish in an uncertain and often inhospitable galaxy of unknowns. The voyages of these brave officers will become legendary as they chart new frontiers beyond what is already known by the Federation. Each new discovery will be worthwhile and exciting for generations to come.  
=== Service to the Collective ===
Constructed in 2375 at [[ma:Unimatrix_325,_Grid_006|Unimatrix 325]], the vessel began as Sphere 531 and was assigned a variety of obejctives in service of the collective. It was primarily stationed in the Alsuran Sector during the assimilation of several planetary systems and operated in an exploratory and monitoring function at the border of the [[ma:Krenim_Imperium|Kremin Imperium]], deep in the [[Delta Quadrant]].  


==Task Force Assets & Headquarters==
=== Release from the Hive Mind ===
While Task Force 17 regularly dispatches starships to deep space assignments far from Starfleet infrastructure, it launches and manages these operations from its headquarters at [[Deep Space 17]] in the [[Typhon Frontier]]. More distant missions are supervised from the flagship, the [[USS Discovery]]. As with other Fourth Fleet task forces, ships operating in other regions rely heavily on local facilities to see to their wide-ranging duties. The other starships of Task Force 17 are divided into two task groups, which share the numbers of the two prior task forces that were merged to create the task force in 2399.  
In 2378 the crew of USS Voyager released a neurolytic pathogen in the heart of the collective causing the apparent death of the Borg Queen and the desctruction of a large portion of the collective's internal infrastructure. This pathogen seperated a substantial number of drones and vessels from the Hive Mind's control. Where other drones fell into a state of confusion, those drones with the genetic mutation that allowed them to retain their indentities within the hive mind (who had at one time formed Unimatrix Zero) found themselves fully released from the Borg control. By chance, several of these Unimatrix Zero surivors were aboard Sphere 531 when the pathogen rendered the vessel immobile.


=== Task Group 9 ===
Following several days of work the survivors were able to isolate the remaining drones and take direct control of the vessel and began searching for any further remnants of the Unimatrix. As a result of several attempts to make contact with other survivors by the small crew of the sphere, now named ''Exodus'', several other clusters of survivors joined from disabled vessels skirting the edge of [[Malon Cooperative|Malon]] & [[Hirogen]] space. 
*[[USS Blythe|USS ''Blythe'']], a [[California Class|''California''-class]] utility cruiser
*[[USS Elysion|USS ''Elysion'']], an [[Elysion Class|''Elysion''-class]] light explorer
*[[USS Gilroy|USS ''Gilroy'']], a [[California Class|''California''-class]] utility cruiser
*[[USS Paramount|USS ''Paramount'']], a [[California Class|''California''-class]] utility cruiser
*[[USS Reliant|USS ''Reliant'']], a [[Reliant Class|''Reliant''-class]] frigate
*[[USS Sizemore|USS ''Sizemore'']], a [[Steamrunner Class|''Steamrunner''-class]] light cruiser


=== Task Group 38 ===
=== Journey to the Federation ===
*[[USS Ahwahnee|USS ''Ahwahnee'']], a [[Cheyenne_Class|''Cheyenne''-class]] light cruiser
The Unimatrix attempted to make contact with several other vessels but found them either completely disabled or operating in a state of base responsiveness, forcing them into conflict as the Borg remnant attempted to reintegrate them. Following a particularly dangerous engagement with a remnant sphere they discovered the Collective was not as dysfunctional as they had assumed following the pathogen's release and a programme of aggressive resource collection and territorial expansion was underway by the newly adapted Hive Mind. 
*[[USS Babylon|USS ''Babylon'']], a [[Grissom Class|''Grissom''-class]] surveyor
*[[USS Burbank|USS ''Burbank'']], a [[California class|''California''-class]] utility cruiser
*[[USS Fearless|USS ''Fearless'']], an [[Excelsior Class|''Excelsior''-class]] heavy cruiser
*[[USS Nighthawk|USS ''Nighthawk'']], a [[Reliant Class|''Reliant''-class]] frigate


==Task Force History==
Following this discovery of a renewed Borg threat and aware they were not going to be welcomed by the local races who had suffered at the hands of the Collective for decades, the community voted almost unanimously to begin travel towards the [[Alpha Quadrant]] following the promises once made by [[ma:Kathryn_Janeway|Captain Janeway]] to the original inhabitants of the Unimatrix.  
Being one of the Fourth Fleet's many exploration arms, primarily focused in the Alpha and Beta Quadrants, when Starfleet decided to redeploy the assets from [[Task Force 9]] and Task Force 38 into one centralised task force then Task Force 17 was the logical decision. In 2399, Task Force 17 was handed all of the fourth fleet's deep space exploration assignments and assets. The handover was relatively simple and smooth sailing, but Starfleet was keen to reestablish a long term presence in the Delta Quadrant. When command of the task force was given to Captain (later Commodore) Bennet, the creation of the lead expeditionary group was Starfleet's first step forward in its efforts to return to the Delta Quadrant.  


=== 2399 ===
After several years of travelling, the Unimatrix found their ability to maintain and supply the new community to be declining as a result of the failing vessel; once designed to be operated by the full hive mind, the Unimatrix was unable to operate the vessel at full capability. As a result of repeated conflicts at the newly resurgent [[ma:Vaadwaur|Vaadwuaar]] border, ''Exodus'' lost a significant portion of its power systems and as a result was no longer able to reach transwarp speeds. Still intent on journeying to the promised lands of the [[United Federation of Planets|Federation]] but facing a journey of several decades the Unimatrix made the decision to attempt to utlise the underspace corridors of the [[Turei Alliance|Turei]] to speed their transit. During their attempts to use the corridors they were repeatedly engaged by Turei forces, who despite their tactically inferior vessels were able to cause significant damage to the sphere. ''Exodus'' was forced from the corridors near the edge of the [[Beta Quadrant]] and forced to continue under their standard warp capabilities. 


==== Archanis Campaign ====
=== Talvath Cluster and ''USS Daedalus'' ===
On the eve of Bennet's expeditionary group leaving the Alpha Quadrant, the threat of the [[Hunters of D'Ghor]] increased rapidly requiring Starfleet to redeploy elements from the fourth fleet to combat it. As a result the expeditionary group, along with several other ships, were rushed to the area to bolster Starfleet's presence and remove the threat caused by the rogue element from the [[Klingon Empire]]. Task Force 17's mandate quickly changed as it was responsible in securing several systems and the assembly of the Archanis Array. Within a matter of days, the ships (all led by Bennet) completed their initial orders and removed the threat of the Hunters and were successful in bringing the new array online. Along with creating an innovative way of monitoring the Klingon-Federation border, the task force's involvement in the campaign was instrumental in removing key players and ships from the Hunters of D'Ghor's fleet. Days after the campaign was declared a victory by Starfleet, Task Force 17 supported in the rebuilding of several key listening outposts along the border and deployment of orbital weapon platforms. Bennet, was promoted to commodore and ordered to return his exploration fleet back to Federation space so it could start its mission in the Delta Quadrant.  
The journey towards Federation territory took several years under standard FTL and the Unimatrix continued to suffer losses as the infrastructure of the vessel failed without the constant upkeep undertaken by hundreds of drones. By the time the vessel arrived in the [[Talvath Cluster|Talvath cluster]] at the far edge of Federation and [[Romulan Factions|Romulan]] territory only a half dozen members of the community remained alive. Since their initial release form the Hive Mind, the community had operated a modified [[ma:Vinculum|vinculum]] aboard the vessel to act as a focal point for the shared virtual reality they developed to recreate Unimatrix Zero, named 'Unimatriz Zero Point Five'. When a series solar events caused major damage to the ship's hull, the dying community decided to channel all their efforts into adapting the vinculum's long range transmission abilities into a distress beacon.  


==== Operation: Delta Expedition ====
[[Overwatch Station|Overwatch station]], still under construction at the edge of the cluster detected the Borg transmission and following review with Starfleet command ''USS Daedalus'' was dispatched to the cluster to investigate the possible threat.  
A month after the Archanis Campaign, Task Force 17's lead expeditionary group began its exploration efforts in the Delta Quadrant. It's first priorities were to explore what happened to the races that ''Voyager'' had left on good terms.


==== Echoes of the TKon Fleet Action ====
Upon arrival at the site ''Daedalus'' found the vessel heavily damaged and only 4 members of the Unimatrix alive aboard. At the instruction of [[Task Force 72]] command the crew began to provide aid in an attempt to make the vessel safe to continue its travels into Federation space, intent on securing their alligence in the process.
Task Force 17 was instrumental in the Fourth Fleet's [[Echoes of the Tkon|fleet action response to the Echoes of the Tkon crisis]] in 2399 as the unit with the most widely spread starships. The placement of the vessels in this task force allowed the Fourth Fleet to identify sites where the Omega Molecule was emerging so that other vessels could respond and stop the outbreak. The task force was also key to identifying Tkon archaeological sites and other remnants of their technology which allowed the Fourth Fleet to end the crisis by shoring up the Galactic Barrier.
 
==== Stormbreaker Campaign ====
While humanitarian efforts were largely carried out by other task forces, Task Force 17 provided reconnaisance and scientific support during the [https://bravofleet.com/mission/46549/ Stormbreaker Campaign] in late 2399. Information provided by starships in this unit were able to gather enough data to allow Starfleet to develop countermeasures for the subspace rifts driving the storm and to predict subspace "weather" patterns well enough to guide aid convoys through the Paulson Nebula.
 
=== 2400 ===
 
==== A New Home ====
As research agreements were made with the [[Romulan Free State]] and Starfleet saw fit to launch new missions of exploration in the [[Typhon Frontier]], Task Force 17 undertook rearrangements. No longer making use of the lead expeditionary group, it was headquartered at Deep Space 17 in the Lioh System. From there, it has the freedom to launch missions into the deeper Beta Quadrant as well as the fringes of the Delta Quadrant, and has extensive research opportunities with the [[ma:Typhon Expanse|Typhon Expanse]] fresh on its doorstep.
 
==== Sundered Wings Fleet Action ====
Along with the rest of the Fourth Fleet, Task Force 17 participated in the fleet action response to the [[Sundered Wings|Sundered Wings Crisis]] in mid-2400. Given the scope of the crisis, Task Force 17 was instrumental in providing real-time data to allow Fourth Fleet Intelligence and Fourth Fleet Operations to prioritize the most important missions within the space of the collapsing Romulan Star Empire.
 
==== Blood Dilithium Campaign ====
In late 2400, Task Force 17 took the lead in the [https://bravofleet.com/mission/64568/ Fourth Fleet's response] to a growing crisis in the Gradin Belt of the Delta Quadrant: the emergence of so-called [[Blood Dilithium|blood dilithium]], which proved to be a serious and immediate threat to life in the region, especially to telepathic life. As the unit with the most experience in the Delta Quadrant, Task Force 17 helped to ensure that the rest of the Fourth Fleet resources being deployed to the region went where they could do the most good.
 
=== 2401 ===
 
==== Lost Fleet Fleet Action ====
In early 2401, Task Force 17 was one of the first Fourth Fleet units on the scene in the Deneb Sector to begin the Fourth Fleet's fleet action response to the [[The Lost Fleet|Lost Fleet]] Crisis, thanks to their headquarters being located at nearby Deep Space 17. Throughout the fleet action, Task Force 17 provided reconnaissance and scientific support to the rest of the fleet.
 
=== Command History ===
Since it's reconstitution in 2399, there have been six commanders of Task Force 17. [https://bravofleet.com/staff_positions/34818/ A full list] including those commanders assigned during Task Force 17's prior history in the 2370s and 2380s is available.
 
* [[bfms_char:29961|Commodore Zach-Marshall-Bennet]], Stardates 2399.7 to 2399.11
* [[bfms_char:27493|Captain/Fleet Captain Alexandra Sudari-Kravchick]], Stardates 2399.11 to 2400.4
* [[bfms_char:34461|Captain/Fleet Captain Erill'Yun Mek]], Stardates 2400.4 to 2400.12
* [[bfms_char:47905|Captain Andreus Kohl]], Stardates 2400.12 to 2401.3
* [[bfms_char:45331|Captain Romaes Anjin]], Stardates 2400.3 to 2401.5
* [[bfms_char:15254|Vice Admiral Elizabeth Hayden]], Stardate 2401.5 to Present

Revision as of 17:23, 7 December 2023

' Exodus
General Information
Class & Type Borg Sphere-class Ark
Affiliation Unimatrix Zero
Status NPC
Commissioned 2375
Destroyed 2401
Assignment
Key Personnel
Commanding Officer Brynn
Executive Officer Aramook
Nothing happens unless we dream
Template:Starship


USS Daedalus Meets Exodus

Encountered by USS Daedalus in 2401 as part of the Fourth Fleets investigations into increased Borg signals, Exodus was the home of a group of Unimatrix Zero survivors following the Borg Collective's restructure caused by the release of the Neurolytic Pathogen.

When Daedalus encountered the vessel it was severly damaged as a result of its journey from Borg territory, those aboard were considering abandoning the vessel when they arrived.

Service History

Service to the Collective

Constructed in 2375 at Unimatrix 325, the vessel began as Sphere 531 and was assigned a variety of obejctives in service of the collective. It was primarily stationed in the Alsuran Sector during the assimilation of several planetary systems and operated in an exploratory and monitoring function at the border of the Kremin Imperium, deep in the Delta Quadrant.

Release from the Hive Mind

In 2378 the crew of USS Voyager released a neurolytic pathogen in the heart of the collective causing the apparent death of the Borg Queen and the desctruction of a large portion of the collective's internal infrastructure. This pathogen seperated a substantial number of drones and vessels from the Hive Mind's control. Where other drones fell into a state of confusion, those drones with the genetic mutation that allowed them to retain their indentities within the hive mind (who had at one time formed Unimatrix Zero) found themselves fully released from the Borg control. By chance, several of these Unimatrix Zero surivors were aboard Sphere 531 when the pathogen rendered the vessel immobile.

Following several days of work the survivors were able to isolate the remaining drones and take direct control of the vessel and began searching for any further remnants of the Unimatrix. As a result of several attempts to make contact with other survivors by the small crew of the sphere, now named Exodus, several other clusters of survivors joined from disabled vessels skirting the edge of Malon & Hirogen space.

Journey to the Federation

The Unimatrix attempted to make contact with several other vessels but found them either completely disabled or operating in a state of base responsiveness, forcing them into conflict as the Borg remnant attempted to reintegrate them. Following a particularly dangerous engagement with a remnant sphere they discovered the Collective was not as dysfunctional as they had assumed following the pathogen's release and a programme of aggressive resource collection and territorial expansion was underway by the newly adapted Hive Mind.

Following this discovery of a renewed Borg threat and aware they were not going to be welcomed by the local races who had suffered at the hands of the Collective for decades, the community voted almost unanimously to begin travel towards the Alpha Quadrant following the promises once made by Captain Janeway to the original inhabitants of the Unimatrix.

After several years of travelling, the Unimatrix found their ability to maintain and supply the new community to be declining as a result of the failing vessel; once designed to be operated by the full hive mind, the Unimatrix was unable to operate the vessel at full capability. As a result of repeated conflicts at the newly resurgent Vaadwuaar border, Exodus lost a significant portion of its power systems and as a result was no longer able to reach transwarp speeds. Still intent on journeying to the promised lands of the Federation but facing a journey of several decades the Unimatrix made the decision to attempt to utlise the underspace corridors of the Turei to speed their transit. During their attempts to use the corridors they were repeatedly engaged by Turei forces, who despite their tactically inferior vessels were able to cause significant damage to the sphere. Exodus was forced from the corridors near the edge of the Beta Quadrant and forced to continue under their standard warp capabilities.

Talvath Cluster and USS Daedalus

The journey towards Federation territory took several years under standard FTL and the Unimatrix continued to suffer losses as the infrastructure of the vessel failed without the constant upkeep undertaken by hundreds of drones. By the time the vessel arrived in the Talvath cluster at the far edge of Federation and Romulan territory only a half dozen members of the community remained alive. Since their initial release form the Hive Mind, the community had operated a modified vinculum aboard the vessel to act as a focal point for the shared virtual reality they developed to recreate Unimatrix Zero, named 'Unimatriz Zero Point Five'. When a series solar events caused major damage to the ship's hull, the dying community decided to channel all their efforts into adapting the vinculum's long range transmission abilities into a distress beacon.

Overwatch station, still under construction at the edge of the cluster detected the Borg transmission and following review with Starfleet command USS Daedalus was dispatched to the cluster to investigate the possible threat.

Upon arrival at the site Daedalus found the vessel heavily damaged and only 4 members of the Unimatrix alive aboard. At the instruction of Task Force 72 command the crew began to provide aid in an attempt to make the vessel safe to continue its travels into Federation space, intent on securing their alligence in the process.

Retrieved from "https://wiki.bravofleet.com/index.php?title=Task_Force_17&oldid=12124"