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

From Bravo Fleet
(Difference between pages)
m
 
m
 
Line 1: Line 1:
{{icons|bfc}}{{Task Force
{{Starship
| name = Task Force 86
| name = Exodus
| seal = [[Image:TF86Seal.png]]
| prefix =
| mandate = Border Operations
| image =
| headquarters = [[Starbase 86]]
| registry =
| url = [http://www.bravofleet.com/group/task-force-86/ Main Link]
| class =
| co = [[bfms_char:65950|CAPT Ryoko Takato]]
| type = Ark
| xo = [[bfms_char:15032|CAPT Keith Anderson]]
| affiliation = Unimatrix Zero
| logo = [[Image:Tf86.png]]
| status = NPC
}}Based out of [[Starbase 86]] and bordering the unclaimed [[The Triangle|Triangle]] region of the Beta Quadrant, T'''ask Force 86''' has a mandate of maintaining local stability and security. They operate in regions beset by insurgency or criminal forces, primarily through cooperation and support of local governments and civilian populations.
| commission = 2375
| decommission =
| destroyed =
| unit =
| taskforce =
| taskgroup =  
| squadron =  
| mothership =  
| homeport =  
| role =
| co = Brynn
| xo = Aramook
| dedication =  
}}


==Objectives ==
[[File:Daedalus meets Exodus.png|thumb|''USS Daedalus'' Meets ''Exodus'']]
*'''Manage''' Starfleet’s border defense and counterinsurgency operations.
*'''Monitor''' criminal organizations operating within the Triangle region.
*'''Develop''' relationships with local governments and communities.
*'''Assist''' those local governments to push back against criminal elements already established and prevent footholds being established.


==Overview==
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]].
Following the synth attack on Mars in 2385, the Federation consolidated her borders and pulled back on her exploratory missions to focus on protecting Federation worlds and citizens.  This action caused power vacuums to arise in several areas, allowing criminal organizations to fill those vacuums.


Operating out of a Starbase on the edge of the [[Azure Nebula]], Task Force 86 is charged with border defense and counterinsurgency operations throughout the FederationFrom its Headquarters on [[Starbase 86]], the Task Force manages and co-ordinates patrols of the Federation’s borders with her neighbors and responds to incursions, monitors criminal activity within Federation space, works with local governments and communities to push back against and disrupt that criminal activity.
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.   


One particular area of concern for the Federation is The Triangle, an unaligned region between the borders of the Federation, the Romulan Republic and the Klingon Empire.  The Triangle has always been a hotbed of criminal activity but the Federation’s shift in focus over the past fifteen years allowed several criminal groups to expand their operations and threaten the stability of worlds throughout the Federation.
== Service History ==


==Task Force Assets and Headquarters==
=== Service to the Collective ===
With the Triangle a particular area of interest to Task Force 86 and its remit, headquarters along with flagship [[USS Majestic|USS ''Majestic'']] are located near the border at [[Starbase 86]]. A smaller outpost, it provides support and resupply to Starfleet vessels heading to the chaotic, unclaimed region, and for many, is the last stop before the end of civilization.
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 Composition ===
=== 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. 


==== Task Group 25 ====
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 Sovereign |USS ''Sovereign'']], a [[Sovereign Class|''Sovereign''-class exploratory cruiser]]
=== Journey to the Federation ===
*[[USS Chico|USS ''Chico'']], a [[California Class|''California''-class utility 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 Neptune|USS ''Neptune'']], a [[Vesta Class|''Vesta''-class explorer]]
*[[USS Erigone|USS ''Erigone'']], a [[Raven Class|''Raven''-class corvette]]
*[[USS Liris|USS ''Liris'']], a [[Raven Class|''Raven''-class corvette]]
*[[USS Los Angeles|USS ''Los Angeles'']], a [[New Orleans Class|''New Orleans''-class frigate]]
*[[Mariner Squadron]]
**[[USS Mariner|USS ''Mariner'']], a [[Pathfinder Class|''Pathfinder''-class long-range science vessel]]
**[[USS Tokyo|USS ''Tokyo'']], a [[New Orleans Class|''New Orleans''-class frigate vessel]]


====Task Group 64====
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. 


*[[Lafayette Squadron]]
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. 
**[[USS Lafayette|USS ''Lafayette'']], a [[Sovereign Class|''Sovereign''-class exploratory cruiser]]
**[[USS Alita|USS ''Alita'']], an [[Alita Class|''Alita''-class heavy cruiser]]
*[[Valhalla Squadron]]
**[[USS Valhalla|USS ''Valhalla'']], a [[Prometheus Class|''Prometheus''-class heavy escort]]
**[[USS Andromeda|USS ''Andromeda'']], an [[Intrepid Class|''Intrepid''-class light explorer]]
*[[USS Jaxartes|USS ''Jaxartes'']], a [[Raven Class|''Raven''-class corvette]]
*[[USS Rubidoux|USS ''Rubidoux'']], a [[California Class|''California''-class multi-mission support vessel]]
*[[USS Tomcat|USS ''Tomcat'']], a [[Akira Class|''Akira''-class corvette]]
*[[USS Brawley|USS ''Brawley'']], a [California Class|''California''-class multi-mission support vessel]]


==Task Force History==
=== Talvath Cluster and ''USS Daedalus'' ===
Task Force 86 has had along and illustrious career as one of the longest serving Task Forces in the Fourth Fleet's history. In 2399, when Starfleet tasked the Fourth Fleet to return to space they also knew it was vitally important that their backyard was watched just as much what laid beyond. As a result, Task Force 86 was designated with the task of border patrol and security. One area that had become a further hotbed of criminal insurgency since the Attack on Mars was around the Azure Nebula in the region known as the [[The Triangle]]. Task Force 86 was assigned to setup its headquarters in this region as a starting point.  
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.  


===The Archanis Campaign ===
[[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.  
Task Force 86's mandate was put to the test in 2399 when the [[Archanis Sector]] was attacked by the [[Hunters of D'Ghor]]. The Fourth Fleet sent a large presence into the sector to defend the border and remove the threat to the Federation colonists and other important assets. Along with other task forces, starships from Task Force 86 responding immediately to the invasion and were able to eventually push the rogue faction out of Federation territory. Working in tandem with other ships, the border was eventually secured from further raids by the Hunters, however the clean-up operation would require a lot of effort. While [[Task Force 93]] led on helping with repairs, rebuilding and recovery operations among the Federation colonies, it would be Task Force 86 that would be required to ensure the border was secure. Thanks to help from [[Task Force 17]], who had built a brand new sensor array near to the border, Task Force 86 were able to monitor and defend the border from any further attacks. After several months of heavy patrolling and the installment of new defense grids (or upgrades to existing ones), Task Force 86 was able to pull some of its forces from the area after it appeared that the tension along the border had returned to the status quo.  


=== The Echoes of the Tkon===
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.
During the end of 2399, every single ship across Starfleet was placed on high alert after multiple sightings of the [[Omega molecule]] were reported. Task Force 86 was given the simple order: secure the border. During this crisis, it was vitally important for the Federation's territory to be defended. Orders were issued to all Task Force 86 ships and bases to patrol various borders, in the event local neighbors decided to take advantage of the situation. Captains were ordered to do whatever it took to ensure Federation security was maintained, such a harsh approach was a surprise to many crews however when it came apparent that Omega was a genuine threat across the entire galaxy, it was down to Task Force 86 to maintain order and prevent chaos from creeping into Federation space. Along with patrols, Task Force 86 ships provided escort to convoys of ships evacuating from affected areas or responded to those who needed help.
 
===The Stormbreaker Campaign ===
In early 2400, the [[Century Storm]] hit the [[ma:Paulson Nebula|Paulson Nebula]] and the surrounding region. This phenomenon severely affected those ships, stations and colonies that existed in this area, causing huge disruption to communication and placing lives on the line. To prevent millions from being killed, the Federation government ordered an immediate evacuation of the area. Elements from Task Force 86 responded to the distress calls of those in need but also aided in preventing criminal organizations from taking advantage of the innocent who were attempting to flee affected areas.
 
====Sundered Wings====
Having so many ships and stations based near to the shared border with the Romulans, Task Force 86 found itself once again having to monitor the border and prevent local crime syndicates from interfering when the [[Star Empire of Rator]] collapsed and the [[Velorum Sector]] declared its independence before seeking assistance from the Federation. This massive political upheaval caused a high level of tension between the Federation and the various Romulan Factions. Task Force 86 ships were ordered to track any ships crossing the border and causing more strife that was not needed.  Those ships involved prevent some pirate ships from launching raids against civilian targets and halting any Romulan warlords from gaining resources from the black market. The Velorum Sector eventually opted to join the Romulan Republic once a majority of their worlds were stabilized, thanks to the efforts of Starfleet and a meditated deal led by the Federation.
 
=== Command History ===
 
*Early 2399: Rear Admiral Arjaal Taam
*Early 2399: [[bfms_char:17740|RADM T'Vrell]]
*Mid 2399: [[bfms_char:24691|COMO Maxwell Stafford]]
*Early 2400: [[bfms_char:34461|FCAPT Erill'Yun Mek]]
*Mid 2400: [[bfms_char:39959|FCAPT Brodie Lewis]]
*Late 2400: [[bfms_char:68750|COMO Jaret Taila]]*
*Early 2401: [[bfms_char:65950|CAPT Ryoko Takato]]
*Early 2401: [[bfms_char:66022|CAPT Theo Barrington]]
*Mid 2401: [[bfms_char:72402|CAPT Taavik]]
*Late 2401: [[bfms_char:68750|COMO Jaret Taila]]*
*Late 2401: [[bfms_char:65950|CAPT Ryoko Takato]]
 
''<sup>* denotes Interim Commander</sup>''

Revision as of 17:20, 7 December 2023

' Exodus
General Information
Affiliation Unimatrix Zero
Status NPC
Commissioned 2375
Assignment
Key Personnel
Commanding Officer Brynn
Executive Officer Aramook
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.