U.S.S. Halcyon

FIOaMKs.png

U.S.S. HALCYON
PIONEER CLASS UTILITY CRUISER
Starfleet Registry NCC-1716

mM0K9Hy.png

The U.S.S. Halcyon was a 23rd century Federation Pioneer-class starship that served primarily in support of the premier front-line vessels of Starfleet. Though its general size and crew complement made it ineligible for the longer, high-profile expeditions, the Halcyon was still occasionally sent on solitary missions of great import when certain situations required immediate follow-up or investigation.

Spoiler: Dedication plaqueShow
9jZv5NH.png

The USS Halcyon's dedication plaque was found with the wreck of the vessel and was gifted to Deep Space 13.
It was touched up and sits on display in a glass case in the Academy Annex's library with a little gold model of the vessel.

--

MAJOR MILESTONES

2266 | Halcyon commissioned after shakedown cruise. Assigned to miscellaneous patrol and escort duties along the alpha/beta quadrant border.

2267 | Embarks on a tour that traveled Ingraham B, Theta Cygni XII, Levinius V, and Beta Portolan. Purpose was to revisit all locations that were invaded by the Denevan neural parasites and perform clean-up with the methodologies learned from Enterprise, as well as determine whether other locations were at risk.

2268 | Made first contact with a species known as the 'Children of Tama', but fails to establish any formal relations due to an inability to communicate effectively. The Tamarian language was deemed 'basically incomprehensible' and the effort was abandoned.

Later sent to patrol the Klingon-Federation border due to high tensions.

2269 | Responded to distress call from the Daedalus-class U.S.S. Laika, which had been surveying astronomical anomalies when it was attacked by Klingon starships. Klingon vessels were successfully discouraged from pursuing hostilities and leave upon Halcyon's arrival.

While assisting with the Laika's repairs, however, another group of Klingon vessels engaged. One vessel appeared equipped with an unusually powerful disruptor weapon and in the ensuing skirmish and pursuit, the Laika was destroyed. The Halcyon managed to rescue 43 of the crew prior to its destruction and escaped.

The incident required Starfleet Command to designate a new directive for the Halcyon: investigate the new Klingon weaponry and develop a counter if possible. In progress, the Halcyon failed to report in on scheduled intervals and was declared MIA, presumed lost with all hands. A search and rescue effort was organized, but due to the Halcyon's proximity to Klingon territory at last check-in, it was soon called off due to perceived extraordinary risk with very low likelihood for success.

2415 | The wreckage of the Halcyon is discovered in a dark nebula in the Doza Sector by officers on the USS Asimov and USS Brooklyn. Ship's logs were recovered and the wreck was towed to Deep Space Station 13 in Aldebaran. Read the AAR on the recovery.

A team of data specialists worked to decipher the logs that detailed the sequence of events of Halcyon's final mission, attached below.

--

KNOWN CREW MEMBERS

CAPTAIN
CAPT Reeves, Jesse
Human, Male
Jesse Reeves@dienonychus

FIRST OFFICER
CMDR Anders, Eric
Human, Male
Anders@jorathedarnesse

CHIEF TACTICAL OFFICER
LCDR Cheng, Ling
Human, Male
Ling Cheng@jeremydajao

CHIEF SECURITY OFFICER
LCDR Wilson, Aaron
Human, Male
Ezri

CHIEF ENGINEERING OFFICER
LCDR Jani, Amar
Human, Male
Amar@EledriPrime

CHIEF MEDICAL OFFICER
LCDR Dumars, Conrad
Human, Male
Conrad@DoABarrelRoll

CHIEF SCIENCE OFFICER
LCDR Kapoor, Alex
Human, Male
Alex Kapoor@mrmely95

COMMS
LT Gral, Tezba
Tellarite, Female
Tezba@asd886

SCIENCE OFFICER
LT Skyr'ven
Vulcan, Male
Skyr'ven@Shadow1710

CONN
ENS Tucker, T'Mira E.
Human-Vulcan, Female
T'Mir@siedhri

YEOMAN
CRW Cloud, Victoria
Human, Female
Victoria@crystyll







ON REASSIGNMENT FROM U.S.S. LAIKA

ENGINEERING OFFICER f.Chief
LCDR Ashkeph, Jhren
Andorian, Male
Ashkeph@holokat
SECURITY OFFICER f.Chief
LCDR Callahan, Helena
Human, Female
Lir@arkaik353
.
.
.
9 Likes
qo6AqZW.png

DETAILS OF FINAL MISSION

In attempting to defend the U.S.S. Laika against an assault from vessels claiming to be of the House of Sorzal, the Halcyon crew discovered the hard way that the Klingons seemed to be in possession of a new type of high-powered weapon, capable of dropping Federation starship shields in one to two disruptor blasts and decimating a hull with one or two more.
retrieved from date 30 Sep 2269: Halcyon ship logs, Halcyon Captain's log


Desperate for intelligence, Starfleet Command authorized the Halcyon to attempt to access a Klingon comm array, in hopes of learning how to counter this new weapon. However, while accessing the array, the Halcyon caught a Klingon vessel distress signal for a House of Sorzal bird of prey that was caught in a gravity well and requesting assistance.

The Halcyon moved to the BoP's location, where its predicament had forced the vessel to divert all power to engines as it tried to get free. With the vessel thusly vulnerable, the Halcyon crew elected to transport the BoP's senior officers into their own brig, before transporting to the bridge to access information.

After downloading part of the BoP's database and transporting a large chunk of miscellaneous technology from their engineering weapons bay, the away team returned and discussed the BoP's fate. Fearful of the Klingons reporting back about their activities, but not willing to outright kill them, they elected to take all 36 Klingons prisoner before nudging the trapped BoP into the singularity, where it was quickly crushed.

In going over the findings from the BoP, the Halcyon crew discovered that a technology 'sheath' had been integrated into the Klingon vessel and was capable of practically tripling the weapon output. Though there was no obvious weakness that could be discerned, engineering suggested that since the technology chain that is used to integrate the augmenting sheath is singularly unique and easily identifiable through code selection, a fast-spreading lightweight virus could be utilized to identify ships carrying the technology and to overload it, rendering it inert and likely disabling weapons entirely. The plan was approved to create a virus that would spread through ship hails, in hopes of locating and targeting House of Sorzal vessels and disabling them without ever exchanging fire.
retrieved from date 2 Oct 2269: Halcyon ship logs


A week has passed since the Halcyon officers successfully developed a quick-spreading virus, which they began to deploy by initiating hails with all vessels they crossed paths with. The hope was that the virus would spread quietly, causing no disruption to systems they weren't targetting and only hitting hard the systems with the identified technology enhancements. With no word of success, the crew decided to attempt to lure a House of Sorzal vessel to their location by falsifying a distress signal with comm codes appropriated from their previous encounter with the Klingon comms array. The gambit worked, attracting a D7 and a bird of prey to their location.

A skirmish ensued as the Klingon vessels arrived and realized they'd been had and the Halcyon crew despaired a little as the Klingon vessels continued to refuse their hails. Just as the Halcyon was ready to attempt retreat however, the D7 opened a channel to taunt the Pioneer-class vessel. The Halcyon officers jumped at the opportunity to return hail and deploy the virus. It took a few more exchanged blasts of fire before the virus took effect. As the smaller ship with less systems to travel, the bird of prey was affected first, having exchanged communications with the D7 after it was infected. The D7 followed soon after and both ships found themselves with weapons offline and shields crippled.

Enraged, the D7's commander initiated a ramming run on the Halcyon, but the Federation vessel veered off and utilized remotely-detonating torpedoes to trigger an explosion big enough to rock the D7 off its collision course with the Halcyon. Instead, the D7 collided with its allied bird of prey and both ships were destroyed. The Halcyon crew was just barely beginning their relieved celebrations when an alien distress call was received. The signal belonged to neither Federation nor Klingon registries and the language itself had never been heard before.

The distress signal was sixteen hours away and Halcyon, after spending an hour repairing their warp systems, got immediately underway.
retrieved from date 8 Oct 2269: Halcyon ship logs


The Halcyon arrived at the source of the distress signal, an alien vessel of which no record existed in the Federation's databases. Sensors could determine that the vessel's various systems were failing and the Halcyon seemed helpless to provide any real assistance to save the vessel. The alien vessel soon called for abandon ship and escape pods were jettisoned. Power fluctuation interference prevented the Halcyon from using transporters to rescue individuals off the main hulk, but they were able to rescue just over a dozen individuals from escape pods. Many more were lost due to the power failure affecting the escape pods as well.

The aliens were moved to sickbay, in critical condition, though one recovered sufficiently to exchange some words with the Halcyon's Captain. Struggling with the Universal Translator, the alien begged for assistance with saving the 'habitation', assumed to reference the alien's homeworld, and provided coordinates for the Halcyon to follow.

In the meantime, Halcyon engineering had beamed aboard samples of the alien vessel debris in order to determine what had caused the malfunctions. They were startled to discover that the aliens were the source of the Klingon's weapon augmentation technology; the same unique markers in the Klingon's technology existed in the alien's technology as well. The realization came that the virus the Halcyon crew had developed in order to stop the Klingons had spread to the alien vessels as well. But instead of only shutting down the Klingon weapons, the species entire technology system was affected and failing.

Engineering desperately attempted to come up with a countervirus that could be spread to halt the original virus's affects and the Halcyon sped to the alien 'habitation' in order to deliver it. But upon arrival, the prototype countervirus appeared not to work and the well-guarded alien colony greeted the Halcyon vessel with hostility. They called themselves the Kilur and pronounced the Halcyon the propagator of the downfall of their civilization and proceeded to open fire on the vessel.

The Halcyon was torn apart in the ensuing chase and all hands were lost. A distress beacon had been activated during the retreat, but quickly went dark when the Halcyon's core went critical and blasted most of the vessel apart. The wreck of the Halcyon then drifted for decades, eventually drawn into the gravity of a dark nebula.
retrieved from date 9 Oct 2269: Halcyon ship logs


// END OF FILE REACHED. //
7 Likes