Bravo Fleet
Difference between pages "Command Policy" and "USS Thyanis"

Difference between pages "Command Policy" and "USS Thyanis"

From Bravo Fleet
(Difference between pages)
(Added clarity on use of archived commands)
 
 
Line 1: Line 1:
{{icons|bfo}}Last Update: 2 March 2023
{{Starship
| name = Thyanis
| prefix = USS
| image = [[File:AerieClass.jpg]]
| registry = NCC-88019
| class = Raven
| type = Corvette
| affiliation = [[Starfleet]]
| status = Active
| commission = 2389
| decommission =
| destroyed =
| taskforce = Task Force 93
| taskgroup = Task Group 44
| role = Multi-Role
| co = [[bfms char:77255|Lieutenant Commander Wallace Jones]]
| xo = [[bfms char:77347|Lieutenant Commander Harris Tan]]
}}
The '''USS ''Thyanis''''' is a [[Raven Class|''Raven''-class]] corvette assigned to [[Fourth Fleet]].


=1 - Registry Definition=
===Mission History===
#The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
====Early Encounters (2400-2400)====
#The registry’s purpose is to maintain consistency across Bravo Fleet and its ongoing canon. As such, entries will not be added to, removed, or altered from the registry without permission of the Intelligence Office.
The earliest encounters of the ''Thyanis'' in the former Romulan Neutral Zone were mostly involving dealing with folks affected by the disruption caused following the fall of the [[Romulan Star Empire]]. As captain of the ship, Kurios and his XO engaged in establishing trade, and helped to resolve issues of malnutrition and disease among several colonies throughout the region. As a part of [[Task Force 93]], this fell well within both the skills of the [[Starfleet]] doctor and within the parameters set by the [[Fourth Fleet]]'s chain of command.
#The registry represents the In Character starships and starbases available to the Fourth Fleet in {{Year}}, and the starships and starbases available for Games and Commands.
##Exceptions such as non-Starfleet ships or ships of a different era have been created for Fictions or Games, and may not be used as Primary Commands. These will be more often added, deleted, or altered.
##The use of registry entries in Games is governed by Section 4 of the Operations Policy.
#Ships in the registry should only be used in lore by the members or Task Forces (in the case of TFHQ ships or Flagships only) to which they are assigned. If a story requires another ship, it should use a name not listed in the registry and would fall within the bounds of member canon.
#Events involving registry ships ''prior to'' 2399 may be referenced in circumstances such as character service records and backstory. This restriction changes at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon after this outside of their own characters and Command.
#Ships are assigned to a member's dossier when they are created as Commands on BFMS. A member must create an application for the Command that the Intel Office processes. The IO does not create Commands for members. Commands exist to house Missions, Stories, and crew rosters; they show the ship on the member's dossier, and ensure the registry displays what ships are available or unavailable. ''All'' ships in use require a Command, including RPGs and squadron ships.
##Once a ship has been relinquished, the BFMS Command will be labelled as 'Archive' and exist on the member's dossier for archival purposes only. Members may edit the Command page or the roster, but they may not add further Missions or Stories.
#Members should not apply for Commands on BFMS until they are ready to acquire or change their Primary Command, or for a fiction/RPG proposal to be discussed with the Intelligence Officer/Operations Officer. Draft Commands or proposals self-identifying as WIPs will have their registry link removed or be deleted.
#Upon a Command's assignment, a member may not change that Command until three months have elapsed or they are promoted, whichever comes first
##Exceptions may be permitted at the discretion of the Intelligence Officer. This may apply in cases such as the release of new starship classes or other significant alterations to the command registry.
=2 - Primary Commands=
#Primary Commands are attached to a member's dossiers as their character's starship or auxiliary craft. They are the vessels assigned In Character to a member’s Task Force in the Fourth Fleet in {{Year}}.
#Members can write on their Primary Commands on their own or with others. Writing with others on a Primary Command does not require a proposal or activity commitment being sent to the Intelligence Office. Members ''may not'' use their Primary Command as an RPG; ie, they may not openly recruit for crew or create a separate website, and collaboration should be limited to invitation-only. RPGs which any member of the Fleet may apply to join must be accepted by the Bravo Fleet Operations Officer, and thus Primary Commands are unsuitable for this purpose.
#All Commands will be removed from a member's dossier upon transfer to the Reserves.
#When a member reaches the rank of Midshipman they may request a ship on the registry for use as their Primary Command. Ship classes available are unlocked upon reaching certain ranks.
#Members below the rank of Captain may only have one Primary Command. Requesting a new eligible Primary Command will result in the current registry ship being removed from the member's dossier and returned to the pool of available ships.
{| class="wikitable" style="margin:auto"
|+Ship classes by rank
|-
!Midshipman!!Lieutenant Commander!!Commander!!
|-
|[[Raven Class|Raven]]||[[California Class|California]]|| colspan="2" |[[Akira Class|Akira]]
|-
| ||[[Challenger Class|Challenger]]|| colspan="2" |[[Defiant Class|Defiant]]
|-
| ||[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]
|-
| ||[[Diligent Class|Diligent]]|| colspan="2" |[[Gagarin Class|Gagarin]]
|-
| ||[[Grissom Class|Grissom]]|| colspan="2" |[[Inquiry Class|Inquiry]]
|-
| ||[[Intrepid Class|Intrepid]]|| colspan="2" |[[Luna Class|Luna]]
|-
|
|[[New Orleans Class|New Orleans]]
| colspan="2" |[[Manticore Class|Manticore]]
|-
| ||[[Norway Class|Norway]]|| colspan="2" |[[Nebula Class|Nebula]]
|-
| ||[[Nova Class|Nova]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]
|-
| ||[[Olympic Class|Olympic]]|| colspan="2" |[[Prometheus Class|Prometheus]]
|-
|
|[[Parliament Class|Parliament]]
| colspan="2" |[[Rhode Island Class|Rhode Island]]
|-
| ||[[Reliant Class|Reliant]]|| colspan="2" |[[Sutherland Class|Sutherland]]
|-
| ||[[Saber Class|Saber]]|| colspan="2" |
|-
| ||[[Springfield Class|Springfield]]
|-
| ||[[Steamrunner Class|Steamrunner]]
|}
=3 - Squadrons=


#The Squadron system allows members holding the dossier rank of Captain and above greater flexibility in their Command choices. Where Commanders and below may pick a single Primary Command from a list, Captains are entitled to a certain level of ‘Squadron Strength’ in their Command selection. This gives them options like choosing between a single, larger ship or multiple smaller ones.
==== Refit (2400-2401) ====
#If a member holds multiple Commands under the Squadrons system, these ships are all subject to the same usage requirements as outlined under Primary Commands above. They may not be used as RPGs, and IC are starships assigned to the member’s Task Force.
Following the departure of Commander Thevius; ''Thyanis'' was returned to Starbase Bravo for minor re-fit. Being a small vessel with little tactical significance, she remained berthed as a reserve ship for nearly a year until she was assigned a new crew and captain at the start of March 2401.  
##All ships must have their own Command on BFMS. This is solely to ensure the registry accurately reflects what ships are in use and dossiers show all of a member's ships. Members are free, however, to house Stories and Missions involving the ship and crew on any of their squadron BFMS Commands.
##Members with multiple ships should designate one as their Primary Command on BFMS. This is solely for display and organisational purposes, and has no other or IC significance. The Primary Command must be a Squadron Commands, and may not be an RPG or Fiction.
##Members have some freedom on how to IC depict these multiple ships. They may be entirely unaffiliated, all falling directly under their Task Force’s IC chain of command, with the member using them to tell totally different stories.
##Members may use all/some of them to form an IC-only unit within their Task Force, referred to as a squadron. This typically takes its title from the squadron’s ‘lead ship’ or starbase (for example, a squadron led by the USS Endeavour would be called ‘Endeavour Squadron’). This ensures all squadrons have a unique IC name. Members may not call these IC units ‘task groups’, to avoid confusion with the OOC unit.
##Members may create an officer in command of this squadron, who may or may not also be the commanding officer of one of these starships/starbase, and who falls IC under the chain of command of the member’s Task Force. All Canon Policy rank restrictions remain.
#The Squadron Strength to which a member is entitled is dependent on their dossier rank.
{| class="wikitable"
|+'''Squadron Strength by Dossier Rank'''
!Captain
!Fleet Captain
!Commodore
!Rear Admiral
!Vice Admiral
!Admiral
!Fleet Admiral
|-
|3
|4
|6
|7
|8
|9
|10
|}


== 3.1 - Starship Strength ==
The nature of her refit was only minor, involving updating many of the standard systems aboard the vessel and returning her to a standard configuration for a multi-role mission profile.


# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
=== Deneb Sector Crisis (2401) ===
# Members may select any number of ships as their Commands under the Squadrons system, so long as the total Strength does not exceed their rank entitlement.
In March 2401 Lieutenant Commander Wallace Jones assumed command of the ''USS Thyanis'' immediately following the outbreak of the Dominion crisis in the [[Deneb Sector|Deneb sector]].


{| class="wikitable" style="margin:auto"
===== Oppenheimer Station =====
|+Ship classes by rank
''Thyanis'' first assignment was to investigate [[Oppenheimer Station|Oppenheimer Research Outpost]] in the Gamma Cronae Borealis system. The station failed to respond to the evacuation order and Starfleet Intelligence requested that a vessel be immediately dispatched.
|-
!1!!2!! colspan="2" |3
!4
|-
|Small Civilian Ship|| colspan="2" |[[Akira Class|Akira]]||[[Century Class|Century]]
|[[Odyssey Class|Odyssey]]
|-
|[[California Class|California]]|| colspan="2" |[[Defiant Class|Defiant]]||[[Galaxy Class|Galaxy]]
|
|-
|[[Challenger Class|Challenger]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]||[[Obena Class|Obena]]
|
|-
|[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Gagarin Class|Gagarin]]||[[Ross Class|Ross]]
|
|-
|[[Diligent Class|Diligent]]|| colspan="2" |[[Inquiry Class|Inquiry]]||[[Sovereign Class|Sovereign]]
|
|-
|[[Grissom Class|Grissom]]|| colspan="2" |[[Luna Class|Luna]]||[[Typhon Class|Typhon]]
|
|-
|[[Intrepid Class|Intrepid]]|| colspan="2" |[[Manticore Class|Manticore]]||[[Vesta Class|Vesta]]
|
|-
|[[New Orleans Class|New Orleans]]|| colspan="2" |[[Nebula Class|Nebula]]||
|
|-
|[[Norway Class|Norway]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]||
|
|-
|[[Nova Class|Nova]]|| colspan="2" |[[Prometheus Class|Prometheus]]||
|
|-
|[[Olympic Class|Olympic]]|| colspan="2" |[[Rhode Island Class|Rhode Island]]||
|
|-
|[[Parliament Class|Parliament]]||[[Sutherland Class|Sutherland]]
|-
|[[Reliant Class|Reliant]]||
|-
|[[Saber Class|Saber]]||
|-
|[[Springfield Class|Springfield]]
|
|-
|[[Steamrunner Class|Steamrunner]]
|
|}
#For example, upon reaching the rank of Captain a member has a Squadron Strength entitlement of 3. If they already have a Commander-level ship, they are only using 2 of their Squadron Level. They may ‘upgrade’ as they did upon reaching the rank of Commander, returning their current ship to the registry and choosing a single new Command with a Strength of 3. If they keep their ship with its Strength of 2, they may choose to add to their dossier another ship with a Strength of 1.
##Members are under no obligation to use their total Squadron Strength. These Commands are a reflection of the hard work of members, however, and may be chosen for storytelling opportunities or simple prestige.
#‘Small Civilian Ship’ is a catch-all term for non-Starfleet civilian vessels members may wish to use for different kinds of storytelling. It refers to ships of, for example, the [[Kaplan F17 class]] or the [[Groumall class]], usually freighters, that are not affiliated IC with Starfleet and may be used for trading, prospecting, exploration, or other adventures. Acquiring a ship like this is subject to a successful Fiction Proposal, and so they are not listed as available on the registry but created as required by the Intelligence Office.
#The Intelligence Office may make adjustments to ship class Strengths to account for balance as the system and canon evolve. No member will have an asset removed because of a rebalance, but they would only be grandfathered in until they wanted to change their squadron, at which point the new strength values would be used.


== 3.2 - Starbase Strength ==
With most of the 4th fleet engaged on the front line, ''Thyanis'' was assigned this mission out of operational necessity


# Starbases as Commands work the same as starships under the Squadron system, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in 2400.
===== Voyage to Deneb Sector =====
# Members do not have to choose between a starbase or starship under the Squadron system. They are only restricted by their rank’s total Squadron Strength.
During her voyage to the Deneb Sector the ''USS'' ''Thyanis'' was attacked by a Breen Plesh Tral Raider near the galactic Northern border of the Ferengi Alliance A short skirmish ensued which resulted in the death of one crewmember and life changing injuries to another, ''Thyanis also'' received significant damage.
# Registry Starbases are created by the Intelligence Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Intelligence Office. This is Fleet Canon that cannot be altered without permission of the Intelligence Office, even by the member to whom the starbase registry is attached. As such, members should heavily consider their choice, as a Starbase Command is under more restrictions and requirements from the Intelligence Office.
## If you are interested in a Starbase Command, please speak with the Intelligence Office to develop your concept so the registry can be created.
# Members may choose to depict any of their other ships as attached to or operating out of the starbase.


{| class="wikitable" style="margin:auto"
Here ''Thyanis'' first encountered a Ferengi vessel commanded by Daimon Tal. The Daimon approached the ''Thyanis'' crew with a proposition as a front to covertly gather data and information on the ''Thyanis's'' destination.
|+Starbase classes by Strength
|-
!2!!3!!4
|-
|[[Jupiter Class|Jupiter]]||[[Anchorage Class|Anchorage]]||[[Canopus Class|Canopus]]
|-
|[[K Class|K-Type]]||[[Copernicus Class|Copernicus]]||[[Unity Class|Unity]]
|-
|[[Regula Class|Regula]]||[[Narendra Class|Narendra]]||
|-
|[[Vision Class|Vision]]||[[Presidium Class|Presidium]]||
|-
| ||[[Watchtower Class|Watchtower]]||
|}


== 3.3 - Attached Ships ==
After returning to Farpoint Station for repairs, ''Thyanis'' continued her journey to her destination without incident.


# Certain commands, like starbases, have an attached ship, which has its own registry entry but has an effective Strength of 0. Whether or not an attached ship is selected does not affect a member’s Squadron Strength.
===== '''Arrival at Oppenheimer Station''' =====
# Most attached ships are assigned to starbases. Upon requesting a starbase, the member should identify to the Intelligence Office an appropriate choice of ship from the registry. That ship will then be removed from the public pool. It will not be given a BFMS Command, but should be written about as part of the starbase’s Command.
On arrival at Oppenheimer Research outpost, ''Thyanis'' attempted to beam a small away team onto the station. The transport was aborted when it was discovered that the station was housing a Quantum singularity that had the potential to interfere with the transporter process and nearly cost the lives of the away team.
# The ''Odyssey''-class always has an ''Aquarius''-class ship attached. Unlike with starbases, the ''Aquarius''-class’s name is predetermined and cannot be changed. Details about an ''Odyssey’s'' ''Aquarius''-class will be listed on the ship’s wiki page.


{| class="wikitable"
A follow up away mission was carried out with the aid of a shuttle, led by the ''Thyanis'' X.O. Lt Commander Harris Tan
|+Starbase Attached Ship Options
|[[Aerie Class|Aerie]]
|
|
|
|
|-
|[[Aquarius Class|Aquarius]]
|
|
|
|
|-
|[[Sydney Class|Sydney]]
|
|
|
|
|}


== 3.4 - Requesting Squadron Ships ==
At about the same time, the Ferengi Vessel commanded by Daimon Tal approached the station. ''Thyanis'' attempted to warn them of the danger but their actions were seen as aggressive and ''Thyanis'' took significant damage when the Ferengi retaliated.


# Members must use BFMS to request any Commands under the Squadron system, as was done with previous Command requests.
Meanwhile on the station, the away team discovered bodies of the Jem'Hadar in advanced stages of decomposition. After shutting down and examining the energy device containing the Quantum Singularity, it was determined that the Jem'Hadar had died as a result of the relativistic effects from the unstable singularity.
# BFMS requests for new Commands under the Squadron system must use the ‘Lore Office Proposal’ window to clearly communicate their allocation of their Squadron Level. This must include what ships, if any, are being returned to the registry.
 
## If a new Captain requests a Command with a Strength of 3 with no further detail, the Intelligence Office will assume they are returning their current ship to the registry, just as with previous upgrades, and process accordingly.
As the singularity was shut down, Daimon Tal boarded the station, killed a ''Thyanis'' crew member and kidnapped Dr Molly Xan and - the ''Thyanis'' Chief Medical officer and Dr Sutherland - Chief scientist aboard the station; all whilst stealing the energy device itself.
## If a Member wishes to retain their current Command and add another, they may request the new ship under BFMS and say so in the Proposal window. A simple message, such as ‘I am keeping the USS Lollipop (Strength 2), and adding this one (Strength 1) for a total Squadron Strength of 3’ will suffice.
 
## If a Member wishes to return any of their ships to the registry, they must say so. Any requests for additional Commands that does not include a registry return and would bring a member over their Squadron Strength will be deleted. A simple message, such as ‘I am returning the USS Lollipop (Strength 2) and adding this one (Strength 3) for a total Squadron Strength of 3’ will suffice.
==== '''Ferengi Pursuit''' ====
# If the Intelligence Office receives competing requests for the same starship, requests for a primary command from Lieutenant Commanders or Commanders will be prioritised, or upgrades to a single Strength 3 starship for new Captains. After that, ships will be allocated on a first-come, first-served basis.
The ''Thyanis'' crew worked desperately to push the ship to its absolute limit in pursuit of the Ferengi Vessel, that was heading for a region of space plagued by subspace instability and a nebula like phenomena. After nearly tearing the ship apart flying well beyond her maximum rated warp speed; ''Thyanis'' successfully kept pace with the Ferengi and were able to maintain pursuit.
 
===== '''Battle with the Dominion''' =====
The disruption to sensors, shields and energy weapons caused by the anomalous region forced the ''Thyanis'' to adopt 20th century tactics to navigate the anomaly and locate Daimon Tal's ship. Using a modified deflector pulse designed to emit Tachyons, ''Thyanis'' soon caught up with the Ferengi, only to encounter a Jem'Hadar Battleship in the process.
 
Meanwhile, During a showdown between the ''Thyanis'' C.O. - Wallace Jones and Daimon Tal - it was revealed that Tal had been replaced by a Changeling, who was plotting to re-engineer the stolen energy device as a devastating weapon - a Black hole Bomb. The changeling was defeated (but not killed) with the combined effort of the ''Thyanis'' away team however the energy device had already been delivered to the Dominion ship.
 
At the same time ''Thyanis'' became locked in a deadly battle with the Dominion vessel. Completely out-classed and out gunned, the ''Thyanis'' X.O. Harris Tan devised a tactic that would later become known as '''The Tan Manoeuvre''<nowiki/>' to cripple the Dominion vessel. Taking inspiration from 20th century fighter weapons tactics, the crew modified several Photon torpedo's to act with delayed autonomous guidance on the same principle as the Tachyon pulse the ship had been using to find the Ferengi.
 
The resulting damage caused to the Dominion vessel detonated the energy device on board, which was in the process of powering up for a test fire. This detonation allowed the singularity contained within to become self sustaining and this then evolved into a stellar mass black hole.
 
As the Black hole began consuming the surrounding matter in the region, ''Thyanis'' rescued the survivors on board the Ferengi ship and her away team before departing for Farpoint station to conclude her mission.
 
===Crew Complement===
The maximum crew of the ''Thyanis'' is only 20 strong, and as such the needs and the abilities of the crew are both affected. The crew has a greater focus on the medical and engineering careers, with only a handful of Starfleet officers specializing in particular fields. Many of the crew are of lower ranks to the point that a former captain, Ensign Kurios, once called it a "can of Ensigns". This quip was a mild misnomer however, as at least a quarter of the crew were cadets or crewman.
 
Interestingly, despite being a ship providing humanitarian support to the former Romulan Neutral Zone, the crew itself could easily find itself in the care of only a old [https://memory-alpha.fandom.com/wiki/Emergency_Medical_Holographic_programs#EMH_Mark_I first generation EMH]. This was considered a bit grim, given the antiquated unit was already being phased out back in [https://memory-alpha.fandom.com/wiki/2374 2374]. As such, it was taken as a bit of black humour among some of the crew that nobody should get injured unless they wanted to be 'walking dead'. The attitude was not helped with the tendency of her captain to be involved in away missions or otherwise be indisposed.
 
===Vessel Configuration===
The current configuration of the ''Thyanis'' is standard for its class. In the past she had been fitted with a slightly more well equipped sick bay to assist her mission profile but this was replaced by its standard configuration to allow the vessel to align to its multi-role profile in 2401. No particular compartment is favoured over another and while she is equipped with two generalist science labs, these facilities can be used simultaneously for different purposes. For example: Science lab 1 can be configured for astronomical survey's where as Science lab 2 can be configured for medical research.
 
Each science lab is configurable by the crew without the need for return to space dock; being stocked and equipped to perform a wide range of experiments and research. Preparing the science lab for a new field of study may require several hours to several days of setting up and calibrating the on-board equipment, but it is most certainly 'user serviceable'.
 
==== '''Warp Drive System''' ====
''Thyanis'' is equipped with a standard Matter/Anti-Matter reactor for her size, capable of an unrestricted sustained velocity of Warp 8. Her maximum (safe) obtainable speed is Warp 8.85 for 12 hours.
 
In 2401, during her mission to the Deneb sector; ''Thyanis'' was forced to exceed this speed and managed to obtain a maximum velocity of warp 8.94. This was obtained without significant modification but caused severe stress damage to her hull and warp drive systems. This was also at the expense of having to override a number of failsafe's and safety protocols.
 
It is worth noting that this operation was only performed due to an unprecedented operational necessity and many of the failsafe's that were overridden at the time have now been re-designed to require dry-dock engineering equipment to bypass.
 
The intense heat generated from the warp matter reaction at these speeds was sufficient to weld her anti-matter injectors shut as they began to cool following an immediate warp core shut down. This made restarting the core impossible and required several injectors to be replaced in order to reinitialise a reaction.
 
While the Matter/Antimatter reaction could remain sustained after securing from such a high warp speed, it is highly likely that the injectors would have suffered heat stress beyond acceptable tolerance and for safety reasons, the injectors would have had to have been replaced before engaging the warp drive again regardless of whether the reaction was terminated immediately or gradually to allow time for adequate cooling and tempering of the alloys used in their construction.
 
Following her return to space-dock, the damage caused by this operation required a complete replacement of the Warp drive system, including all Matter/Anti-matter reaction components and a complete refurbishment of her warp coils, as many of them sustained micro fractures due to the stress of high warp flight.
 
==== Crew Transportation System ====
One rather unique design choice employed on the ''Thyanis'' is the complete lack of Turbo Lifts which are an over-complicated mechanism that would take up vast amounts of internal space. Instead ''Thyanis'' is equipped with 'Ladders' in various locations around the ship, these resemble very steep sets of stairs that were typical on contemporary Navy Warships of the 20th & 21st century. They are a simple and effective solution to allow access to all decks of the ship whilst maximising the internal space available for internal compartments and living quarters.
 
=== Deck plan (overview) ===
 
==== Deck 1 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* Escape Pods
* Science Lab 1
* Escape Pods
* Science Lab 2
* Escape Pods
* '''''Aft Sensor Suite'''''
 
==== Deck 2 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* C.O. Ready Room
* Main Bridge
* Environmental Control
* Portside Mess
* Starboard Galley
* X.O Quarters
* Equipment Storage
* '''''Life Support Consumable Storage Tanks'''''
 
==== Deck 3 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* C.O. Quarters
* Sickbay
* Hollo Suite
* '''''Anti Matter Storage'''''
* '''''Warp Core (upper Level)'''''
* '''''Deuterium Storage'''''
* '''''Computer Core (upper Level)'''''
* Cargo Loading Dock
* Shuttle Bay
 
==== Deck 4 ''(From Bow to Stern)'' ====
'''''Bold''''' Denote Area only accessible via crawlspace & Jeffries tube
 
* '''''Deflector Control'''''
* Torpedo Magazine & '''''Launcher Tube'''''
* Brig
* Crew Quarters
* Forward Cargo Bay
* Main Engineering
* Computer Core
* Transporter Room
* Aft Cargo Bay
* Crew Quarters
 
==== Deck 5 ''(From Bow to Stern)'' ====
'''Note: Deck 5 Is only accessible via Crawlspace and not all areas are routinely pressurised'''
 
* '''EPS Power Buffers'''
* '''Forward Sensor array'''
* '''Subspace Transceiver'''
* '''Forward Landing Gear'''
* '''Forward Cargo Bay Doors & Elevator'''
* '''Warp Core (Lower Deck)'''
* '''Rear Cargo Bay Doors & Elevator'''
* '''Aft Landing Gear'''
 
===Notable Crew===
====Commanding Officers====
*[https://bravofleet.com/command/60986/ 2400 - 2400]: [[bfms char:59211|Ensign Cimozjen Kurios]]
*[https://bravofleet.com/command/52947/ 2400 - 2400]: [[bfms char:53381|Commander Thevius]]
*[https://bravofleet.com/command/77256/ 2401 - Present]: [[bfms char:77255|Lieutenant Commander Wallace Jones]]
 
{{clear}}

Revision as of 18:23, 18 June 2023

AerieClass.jpg
USS Thyanis
General Information
Registry NCC-88019
Class & Type Raven-class Corvette
Affiliation Starfleet
Status Active
Commissioned 2389
Assignment
Task Force Task Force 93
Task Group Task Group 44
Role Multi-Role
Key Personnel
Commanding Officer Lieutenant Commander Wallace Jones
Executive Officer Lieutenant Commander Harris Tan
Template:Starship

The USS Thyanis is a Raven-class corvette assigned to Fourth Fleet.

Mission History

Early Encounters (2400-2400)

The earliest encounters of the Thyanis in the former Romulan Neutral Zone were mostly involving dealing with folks affected by the disruption caused following the fall of the Romulan Star Empire. As captain of the ship, Kurios and his XO engaged in establishing trade, and helped to resolve issues of malnutrition and disease among several colonies throughout the region. As a part of Task Force 93, this fell well within both the skills of the Starfleet doctor and within the parameters set by the Fourth Fleet's chain of command.

Refit (2400-2401)

Following the departure of Commander Thevius; Thyanis was returned to Starbase Bravo for minor re-fit. Being a small vessel with little tactical significance, she remained berthed as a reserve ship for nearly a year until she was assigned a new crew and captain at the start of March 2401.

The nature of her refit was only minor, involving updating many of the standard systems aboard the vessel and returning her to a standard configuration for a multi-role mission profile.

Deneb Sector Crisis (2401)

In March 2401 Lieutenant Commander Wallace Jones assumed command of the USS Thyanis immediately following the outbreak of the Dominion crisis in the Deneb sector.

Oppenheimer Station

Thyanis first assignment was to investigate Oppenheimer Research Outpost in the Gamma Cronae Borealis system. The station failed to respond to the evacuation order and Starfleet Intelligence requested that a vessel be immediately dispatched.

With most of the 4th fleet engaged on the front line, Thyanis was assigned this mission out of operational necessity

Voyage to Deneb Sector

During her voyage to the Deneb Sector the USS Thyanis was attacked by a Breen Plesh Tral Raider near the galactic Northern border of the Ferengi Alliance A short skirmish ensued which resulted in the death of one crewmember and life changing injuries to another, Thyanis also received significant damage.

Here Thyanis first encountered a Ferengi vessel commanded by Daimon Tal. The Daimon approached the Thyanis crew with a proposition as a front to covertly gather data and information on the Thyanis's destination.

After returning to Farpoint Station for repairs, Thyanis continued her journey to her destination without incident.

Arrival at Oppenheimer Station

On arrival at Oppenheimer Research outpost, Thyanis attempted to beam a small away team onto the station. The transport was aborted when it was discovered that the station was housing a Quantum singularity that had the potential to interfere with the transporter process and nearly cost the lives of the away team.

A follow up away mission was carried out with the aid of a shuttle, led by the Thyanis X.O. Lt Commander Harris Tan

At about the same time, the Ferengi Vessel commanded by Daimon Tal approached the station. Thyanis attempted to warn them of the danger but their actions were seen as aggressive and Thyanis took significant damage when the Ferengi retaliated.

Meanwhile on the station, the away team discovered bodies of the Jem'Hadar in advanced stages of decomposition. After shutting down and examining the energy device containing the Quantum Singularity, it was determined that the Jem'Hadar had died as a result of the relativistic effects from the unstable singularity.

As the singularity was shut down, Daimon Tal boarded the station, killed a Thyanis crew member and kidnapped Dr Molly Xan and - the Thyanis Chief Medical officer and Dr Sutherland - Chief scientist aboard the station; all whilst stealing the energy device itself.

Ferengi Pursuit

The Thyanis crew worked desperately to push the ship to its absolute limit in pursuit of the Ferengi Vessel, that was heading for a region of space plagued by subspace instability and a nebula like phenomena. After nearly tearing the ship apart flying well beyond her maximum rated warp speed; Thyanis successfully kept pace with the Ferengi and were able to maintain pursuit.

Battle with the Dominion

The disruption to sensors, shields and energy weapons caused by the anomalous region forced the Thyanis to adopt 20th century tactics to navigate the anomaly and locate Daimon Tal's ship. Using a modified deflector pulse designed to emit Tachyons, Thyanis soon caught up with the Ferengi, only to encounter a Jem'Hadar Battleship in the process.

Meanwhile, During a showdown between the Thyanis C.O. - Wallace Jones and Daimon Tal - it was revealed that Tal had been replaced by a Changeling, who was plotting to re-engineer the stolen energy device as a devastating weapon - a Black hole Bomb. The changeling was defeated (but not killed) with the combined effort of the Thyanis away team however the energy device had already been delivered to the Dominion ship.

At the same time Thyanis became locked in a deadly battle with the Dominion vessel. Completely out-classed and out gunned, the Thyanis X.O. Harris Tan devised a tactic that would later become known as 'The Tan Manoeuvre' to cripple the Dominion vessel. Taking inspiration from 20th century fighter weapons tactics, the crew modified several Photon torpedo's to act with delayed autonomous guidance on the same principle as the Tachyon pulse the ship had been using to find the Ferengi.

The resulting damage caused to the Dominion vessel detonated the energy device on board, which was in the process of powering up for a test fire. This detonation allowed the singularity contained within to become self sustaining and this then evolved into a stellar mass black hole.

As the Black hole began consuming the surrounding matter in the region, Thyanis rescued the survivors on board the Ferengi ship and her away team before departing for Farpoint station to conclude her mission.

Crew Complement

The maximum crew of the Thyanis is only 20 strong, and as such the needs and the abilities of the crew are both affected. The crew has a greater focus on the medical and engineering careers, with only a handful of Starfleet officers specializing in particular fields. Many of the crew are of lower ranks to the point that a former captain, Ensign Kurios, once called it a "can of Ensigns". This quip was a mild misnomer however, as at least a quarter of the crew were cadets or crewman.

Interestingly, despite being a ship providing humanitarian support to the former Romulan Neutral Zone, the crew itself could easily find itself in the care of only a old first generation EMH. This was considered a bit grim, given the antiquated unit was already being phased out back in 2374. As such, it was taken as a bit of black humour among some of the crew that nobody should get injured unless they wanted to be 'walking dead'. The attitude was not helped with the tendency of her captain to be involved in away missions or otherwise be indisposed.

Vessel Configuration

The current configuration of the Thyanis is standard for its class. In the past she had been fitted with a slightly more well equipped sick bay to assist her mission profile but this was replaced by its standard configuration to allow the vessel to align to its multi-role profile in 2401. No particular compartment is favoured over another and while she is equipped with two generalist science labs, these facilities can be used simultaneously for different purposes. For example: Science lab 1 can be configured for astronomical survey's where as Science lab 2 can be configured for medical research.

Each science lab is configurable by the crew without the need for return to space dock; being stocked and equipped to perform a wide range of experiments and research. Preparing the science lab for a new field of study may require several hours to several days of setting up and calibrating the on-board equipment, but it is most certainly 'user serviceable'.

Warp Drive System

Thyanis is equipped with a standard Matter/Anti-Matter reactor for her size, capable of an unrestricted sustained velocity of Warp 8. Her maximum (safe) obtainable speed is Warp 8.85 for 12 hours.

In 2401, during her mission to the Deneb sector; Thyanis was forced to exceed this speed and managed to obtain a maximum velocity of warp 8.94. This was obtained without significant modification but caused severe stress damage to her hull and warp drive systems. This was also at the expense of having to override a number of failsafe's and safety protocols.

It is worth noting that this operation was only performed due to an unprecedented operational necessity and many of the failsafe's that were overridden at the time have now been re-designed to require dry-dock engineering equipment to bypass.

The intense heat generated from the warp matter reaction at these speeds was sufficient to weld her anti-matter injectors shut as they began to cool following an immediate warp core shut down. This made restarting the core impossible and required several injectors to be replaced in order to reinitialise a reaction.

While the Matter/Antimatter reaction could remain sustained after securing from such a high warp speed, it is highly likely that the injectors would have suffered heat stress beyond acceptable tolerance and for safety reasons, the injectors would have had to have been replaced before engaging the warp drive again regardless of whether the reaction was terminated immediately or gradually to allow time for adequate cooling and tempering of the alloys used in their construction.

Following her return to space-dock, the damage caused by this operation required a complete replacement of the Warp drive system, including all Matter/Anti-matter reaction components and a complete refurbishment of her warp coils, as many of them sustained micro fractures due to the stress of high warp flight.

Crew Transportation System

One rather unique design choice employed on the Thyanis is the complete lack of Turbo Lifts which are an over-complicated mechanism that would take up vast amounts of internal space. Instead Thyanis is equipped with 'Ladders' in various locations around the ship, these resemble very steep sets of stairs that were typical on contemporary Navy Warships of the 20th & 21st century. They are a simple and effective solution to allow access to all decks of the ship whilst maximising the internal space available for internal compartments and living quarters.

Deck plan (overview)

Deck 1 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • Escape Pods
  • Science Lab 1
  • Escape Pods
  • Science Lab 2
  • Escape Pods
  • Aft Sensor Suite

Deck 2 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • C.O. Ready Room
  • Main Bridge
  • Environmental Control
  • Portside Mess
  • Starboard Galley
  • X.O Quarters
  • Equipment Storage
  • Life Support Consumable Storage Tanks

Deck 3 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • C.O. Quarters
  • Sickbay
  • Hollo Suite
  • Anti Matter Storage
  • Warp Core (upper Level)
  • Deuterium Storage
  • Computer Core (upper Level)
  • Cargo Loading Dock
  • Shuttle Bay

Deck 4 (From Bow to Stern)

Bold Denote Area only accessible via crawlspace & Jeffries tube

  • Deflector Control
  • Torpedo Magazine & Launcher Tube
  • Brig
  • Crew Quarters
  • Forward Cargo Bay
  • Main Engineering
  • Computer Core
  • Transporter Room
  • Aft Cargo Bay
  • Crew Quarters

Deck 5 (From Bow to Stern)

Note: Deck 5 Is only accessible via Crawlspace and not all areas are routinely pressurised

  • EPS Power Buffers
  • Forward Sensor array
  • Subspace Transceiver
  • Forward Landing Gear
  • Forward Cargo Bay Doors & Elevator
  • Warp Core (Lower Deck)
  • Rear Cargo Bay Doors & Elevator
  • Aft Landing Gear

Notable Crew

Commanding Officers

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