Difference between revisions of "USS Helios"
(Transfer Helios to Daedalus) |
(Condensed mission summaries) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Starship | {{Starship | ||
| name = Helios | | name = Helios | ||
| Line 16: | Line 15: | ||
| taskgroup = Task Group 63 | | taskgroup = Task Group 63 | ||
| squadron = | | squadron = | ||
| division = Helios Division | |||
| mothership = | | mothership = | ||
| homeport = | | homeport = | ||
| Line 23: | Line 23: | ||
| dedication = [[File:HELIOS PATCH.png]] | | dedication = [[File:HELIOS PATCH.png]] | ||
}} | }} | ||
{{quote|The test of any man is in action.|Pindar}} | |||
'''USS ''Helios'' (NCC-63284)''' is an [[Akira Class|''Akira''-class]] [[United Federation of Planets|Federation]] starship assigned to [[Fourth Fleet|Fourth Fleet's]] [[Task Force 47]]. She is currently under the command of [[bfms char:81015|Captain Tanek]], operating out of [[Deep Space 47]] in the [[Thomar Expanse]], providing pathfinding and diplomatic support in the politically unstable region. | |||
== Service History == | == Service History == | ||
=== Commissioning and Early Service === | === Commissioning and Early Service === | ||
One of the first block of ''Akira'' class vessels produced in 2363, ''Helios'' was part of the wave of new designs rapidly sweeping across the fleet that explored a different form of shipbuilding that focused on mission specialisation over larger multi-role vessels. Spending much of the next two decades undertaking operations at the [[Cardassian Union|Cardassian]] Border, ''Helios'' also served with distinction during the Dominion War as part of the Fourth Fleet's space command programme, defending key locations throughout the war | One of the first block of ''Akira'' class vessels produced in 2363, ''Helios'' was part of the wave of new designs rapidly sweeping across the fleet that explored a different form of shipbuilding that focused on mission specialisation over larger multi-role vessels. Spending much of the next two decades undertaking operations at the [[Cardassian Union|Cardassian]] Border, ''Helios'' also served with distinction during the Dominion War as part of the Fourth Fleet's space command programme, defending key locations throughout the war front. | ||
''Helios'' was present in the task force that supported the efforts of ''[[ma:USS_Stargazer_(NCC-82893)|Stargazer]]'' and the [[ma:Agnes_Jurati#Queen_of_the_Borg|Jurati]] Collective to defend against the dangers of the temporal and spatial anomaly. Following these events the ship underwent a major overhaul at the [[Avalon Fleet Yards]] to modify it for deployment with Task Force 47. | ''Helios'' was present in the task force that supported the efforts of ''[[ma:USS_Stargazer_(NCC-82893)|Stargazer]]'' and the [[ma:Agnes_Jurati#Queen_of_the_Borg|Jurati]] Collective to defend against the dangers of the temporal and spatial anomaly. Following these events the ship underwent a major overhaul at the [[Avalon Fleet Yards]] to modify it for deployment with Task Force 47. | ||
=== Threadbare Flags === | === Threadbare Flags === | ||
2401, Helios found themselves redeployed to the Cardassian border following the destruction of Outpost C-91, reportedly by the True Way separatist movement. Initially assigned reconnaissance and overwatch responsibilities in the expansive region, utilising it's large number of auxiliary craft to supplement long range sensor platforms, ''Helios'' was part of a network providing real time | In 2401, Helios found themselves redeployed to the Cardassian border following the [https://bravofleet.com/group_news/the-shape-of-things-to-come/ destruction of Outpost C-91], reportedly by the True Way separatist movement. Initially assigned reconnaissance and overwatch responsibilities in the expansive region, utilising it's large number of auxiliary craft to supplement long-range sensor platforms, ''Helios'' was part of a network providing real time oversight of the region. When a personal message to a young Lieutenant suggests an imminent bomb threat from the New Maquis, Helios is retasked to Cyodan II, to investigate the security threat. | ||
=== [https://bravofleet.com/mission/122490 Echoes in the Weeds] === | === [https://bravofleet.com/mission/122490 Echoes in the Weeds] === | ||
Late in the year 2401, ''Helios'' was assigned to act as a research support platform for a new long-range sensor suite designed to improve surveillance in the [[ma:Badlands|Badlands]]. | [[File:Helios - STO - Labyrinth.jpg|thumb|300x300px|USS ''Helio'' in orbit of the remote Kazon colony.]] | ||
Late in the year 2401, ''Helios'' was assigned to act as a research support platform for a new long-range sensor suite designed to improve surveillance in the [[ma:Badlands|Badlands]]. While testing the new platform, the vessel was caught unaware by the opening of a subspace aperture related to the galaxy-wide [[Labyrinth Campaign Guide|Underspace emergence]]. Transported several thousand lightyears through the [[Underspace]] corridors, ''Helios'' was damaged and stranded in a remote system where the high level of electromagnetic and stellar radiation made attaining warp speeds impossible. | |||
Whilst undertaking repair works in the system and investigating possible avenues for their return to Federation space, ''Helios'' encountered a remote Kazon colony, seemingly separated from the other [[Kazon Collective]] over 50 years prior | Whilst undertaking repair works in the system and investigating possible avenues for their return to Federation space, ''Helios'' encountered a remote Kazon colony, seemingly separated from the other members [[Kazon Collective]] over 50 years prior. These Kazon appeared to have settled on the planet and were operating a satisfactory subsistence lifestyle. When it became apparent that the access portal to the Underspace was collapsing due to the activities of the Cardassian Union in the Alpha quadrant, ''Helios'' was forced to take the risk and attempt to return to Underspace unprepared. The Kazon revealed they were not as peaceful as believed and launched an attack on ''Helios'' to secure its advanced technology, having been unable to open the portal themselves with their limited assets. | ||
Helios was able to return to the Alpha quadrant but incurred | ''Helios'' was able to return to the Alpha quadrant but incurred several losses, returning to Deep Space 47 for repairs and post-action debriefing. | ||
==Design and Capabilities== | ==Design and Capabilities== | ||
| Line 48: | Line 47: | ||
===Heliades Squadron=== | ===Heliades Squadron=== | ||
[[File:Helidae Squad Updated.png|alt=|left|frameless]] | [[File:Helidae Squad Updated.png|alt=|left|frameless]] | ||
Originally created to take advantage of the ''Helios''<nowiki/>' through-deck design as it fulfilled escort carrier duties during the [[ma:Dominion_War|Dominion War]]; ''Heliades'' Squadron has found new life as a specialist service unit. In a galaxy of instant transporters and increased automation, several members of [[ma:Starfleet Operations|Starfleet Operations]] have identified a critical vulnerability in starship operations when these systems are rendered unavailable. Whilst effective mass-produced vehicles, the standard shuttle designs are created with adaptability in mind and as a result cannot provide high level support to star ships and operations. The need for craft and officers who can provide expert logistical support & mobile services aboard larger ships, over and above the standard training of shuttle pilots was becoming evident. ''Heliades'' squad are experts with a wide range of | Originally created to take advantage of the ''Helios''<nowiki/>' through-deck design as it fulfilled escort carrier duties during the [[ma:Dominion_War|Dominion War]]; ''Heliades'' Squadron has found new life as a specialist service unit. In a galaxy of instant transporters and increased automation, several members of [[ma:Starfleet Operations|Starfleet Operations]] have identified a critical vulnerability in starship operations when these systems are rendered unavailable. Whilst effective mass-produced vehicles, the standard shuttle designs are created with adaptability in mind and as a result cannot provide high level support to star ships and operations. The need for craft and officers who can provide expert logistical support & mobile services aboard larger ships, over and above the standard training of shuttle pilots was becoming evident. ''Heliades'' squad are experts with a wide range of auxiliary vehicles, their operation and usage, including shuttles, combat auxiliary craft (such as the [[Starfighters#Valkyrie-class_fighter|''Valkyrie''-class starfighter]]) and ground craft, including traditional motorised and wheeled vehicles. | ||
==Notable Locations== | ==Notable Locations== | ||
< | ==== The Orrery ==== | ||
Situated in the enclosed centre of ''Helios'<nowiki/>'' flight deck, the Orrery is the command centre of the ships' flight wing and Heliades squadron. A modification of the auxiliary bridge, the Orrery takes advantage of the room's command and control systems as well as the direct connection to the ship's computer and sensor systems to manage the airspace around ''Helios''. With a number of dedicated stations for the management of ''Helios''' vast shuttle bays and a live link to the main bridge, the Orrery acts as a CIC during combat but most importantly provides vital operational & strategic support during humanitarian and transport missions. | |||
With ''Helios''' recent return to non-combat duties with Task Force 47 and the Fourth Fleet's return to a more scientific mission brief, the Orrery has received a permanent contingent of science officers into the duty roster. These scientists provide support to the divisions's exploratory efforts, utilising the ship's huge number of auxiliary craft to extend the reach of the ship's sensors and directing their efforts to survey systems with surprising speed. | |||
==== Sunspot Lounges ==== | |||
[[File:Helios - Sunspot Lounge.jpg|left|thumb|300x300px|Several of the booths feature impressive vistas into the space beyond Helios, holographic or otherwise.]] | |||
The Akira-Class vessels make novel use of space to facilitate social areas for almost 500 crew members with limited space. Several large open plan messes combined with passing place style corridor lounges (taking advantage of lessons learnt with the Galaxy class) allow ''Helios'' to make use of normally wasted space. Nestled on the port and starboard trailing edge of ''Helios''' deck 8, the twin sunspot lounges are one of the ship's more subdued and intimate social spaces, converted from small junior messes. | |||
Fitted with a number of private booths and sofas, the low lighting and ambient music that spills forth from hidden speakers gives the lounges a more intimate feel for evenings of quiet gatherings and rendezvous. The twin lounges feature a number of privacy considerations such as inbuilt replicators in the booth's tables, holographic dividers and an all-holographic bar and waiting staff. The focal point of each booth is a large aft quarter-facing window giving unobstructed views out into space, which more than once has caused a subtle course correction to maximise a romantic vista. | |||
<!--Do not delete the Notable Crew section. It is used by the Intel Office for command history tracking. Leave at the bottom of the page.--> | |||
== Notable Crew== | == Notable Crew== | ||
===Commanding Officers=== | ===Commanding Officers=== | ||
Latest revision as of 13:59, 20 October 2024
- "The test of any man is in action."
- —Pindar
USS Helios (NCC-63284) is an Akira-class Federation starship assigned to Fourth Fleet's Task Force 47. She is currently under the command of Captain Tanek, operating out of Deep Space 47 in the Thomar Expanse, providing pathfinding and diplomatic support in the politically unstable region.
Service History
Commissioning and Early Service
One of the first block of Akira class vessels produced in 2363, Helios was part of the wave of new designs rapidly sweeping across the fleet that explored a different form of shipbuilding that focused on mission specialisation over larger multi-role vessels. Spending much of the next two decades undertaking operations at the Cardassian Border, Helios also served with distinction during the Dominion War as part of the Fourth Fleet's space command programme, defending key locations throughout the war front.
Helios was present in the task force that supported the efforts of Stargazer and the Jurati Collective to defend against the dangers of the temporal and spatial anomaly. Following these events the ship underwent a major overhaul at the Avalon Fleet Yards to modify it for deployment with Task Force 47.
Threadbare Flags
In 2401, Helios found themselves redeployed to the Cardassian border following the destruction of Outpost C-91, reportedly by the True Way separatist movement. Initially assigned reconnaissance and overwatch responsibilities in the expansive region, utilising it's large number of auxiliary craft to supplement long-range sensor platforms, Helios was part of a network providing real time oversight of the region. When a personal message to a young Lieutenant suggests an imminent bomb threat from the New Maquis, Helios is retasked to Cyodan II, to investigate the security threat.
Echoes in the Weeds
Late in the year 2401, Helios was assigned to act as a research support platform for a new long-range sensor suite designed to improve surveillance in the Badlands. While testing the new platform, the vessel was caught unaware by the opening of a subspace aperture related to the galaxy-wide Underspace emergence. Transported several thousand lightyears through the Underspace corridors, Helios was damaged and stranded in a remote system where the high level of electromagnetic and stellar radiation made attaining warp speeds impossible.
Whilst undertaking repair works in the system and investigating possible avenues for their return to Federation space, Helios encountered a remote Kazon colony, seemingly separated from the other members Kazon Collective over 50 years prior. These Kazon appeared to have settled on the planet and were operating a satisfactory subsistence lifestyle. When it became apparent that the access portal to the Underspace was collapsing due to the activities of the Cardassian Union in the Alpha quadrant, Helios was forced to take the risk and attempt to return to Underspace unprepared. The Kazon revealed they were not as peaceful as believed and launched an attack on Helios to secure its advanced technology, having been unable to open the portal themselves with their limited assets.
Helios was able to return to the Alpha quadrant but incurred several losses, returning to Deep Space 47 for repairs and post-action debriefing.
Design and Capabilities
Heliades Squadron
Originally created to take advantage of the Helios' through-deck design as it fulfilled escort carrier duties during the Dominion War; Heliades Squadron has found new life as a specialist service unit. In a galaxy of instant transporters and increased automation, several members of Starfleet Operations have identified a critical vulnerability in starship operations when these systems are rendered unavailable. Whilst effective mass-produced vehicles, the standard shuttle designs are created with adaptability in mind and as a result cannot provide high level support to star ships and operations. The need for craft and officers who can provide expert logistical support & mobile services aboard larger ships, over and above the standard training of shuttle pilots was becoming evident. Heliades squad are experts with a wide range of auxiliary vehicles, their operation and usage, including shuttles, combat auxiliary craft (such as the Valkyrie-class starfighter) and ground craft, including traditional motorised and wheeled vehicles.
Notable Locations
The Orrery
Situated in the enclosed centre of Helios' flight deck, the Orrery is the command centre of the ships' flight wing and Heliades squadron. A modification of the auxiliary bridge, the Orrery takes advantage of the room's command and control systems as well as the direct connection to the ship's computer and sensor systems to manage the airspace around Helios. With a number of dedicated stations for the management of Helios' vast shuttle bays and a live link to the main bridge, the Orrery acts as a CIC during combat but most importantly provides vital operational & strategic support during humanitarian and transport missions.
With Helios' recent return to non-combat duties with Task Force 47 and the Fourth Fleet's return to a more scientific mission brief, the Orrery has received a permanent contingent of science officers into the duty roster. These scientists provide support to the divisions's exploratory efforts, utilising the ship's huge number of auxiliary craft to extend the reach of the ship's sensors and directing their efforts to survey systems with surprising speed.
Sunspot Lounges
The Akira-Class vessels make novel use of space to facilitate social areas for almost 500 crew members with limited space. Several large open plan messes combined with passing place style corridor lounges (taking advantage of lessons learnt with the Galaxy class) allow Helios to make use of normally wasted space. Nestled on the port and starboard trailing edge of Helios' deck 8, the twin sunspot lounges are one of the ship's more subdued and intimate social spaces, converted from small junior messes.
Fitted with a number of private booths and sofas, the low lighting and ambient music that spills forth from hidden speakers gives the lounges a more intimate feel for evenings of quiet gatherings and rendezvous. The twin lounges feature a number of privacy considerations such as inbuilt replicators in the booth's tables, holographic dividers and an all-holographic bar and waiting staff. The focal point of each booth is a large aft quarter-facing window giving unobstructed views out into space, which more than once has caused a subtle course correction to maximise a romantic vista.