Main Sim - Cargo Bay

Posted June 7, 2023, 11:21 p.m. by Gamemaster Rei (GMT) (Sam Haynes)

Posted by Lieutenant Commander Teller Graham (Chief Science Officer) in Main Sim - Cargo Bay

Posted by Lieutenant Commander Teller Graham (Chief Science Officer) in Main Sim - Cargo Bay

Posted by Gamemaster Rei (GMT) in Main Sim - Cargo Bay
Posted by… suppressed (25) by the Post Ghost! 👻
From the bridge Atoded grabbed the piece of the B’hari’s bridge and tractored it (OOC or beamed not sure which works here Lady GM). Coordinating with the Ops officer on duty in the Cargo Bay they brought the large piece of debris in and it settled with a loud thud-dunk on the floor plating. A swarm of NEs in protective gear, just in case, wen about securing and supporting the large structure so it was stable.

Atoded, CoS

Charles was one of the Ensigns present as well. He was helping a group hold up one of the sides while the others braced it from underneath. Charles also elected to preform a “bump test” afterwards to make sure it was secure, pushing with a non-insignificant amount of force onto the heavy chunk of debris.

“Well, if that didn’t move it,” he said to the others, “I think it is good, no?”

[Ensign Charles-Louis, Engineering]

((The good ol’ “That ain’t goin’ nowhere.” :D ))

Magnetic clamps and a few straps saw the wreckage locked in place. A quick scan revealed low levels of particle emissions emanating from the materials, which were well within safety parameters.

The piece of ship in question was roughly the size and shape of a small watercraft, such as a small cabin cruiser or sport boat. It was an intersection of two flat bulkheads which formed an L that curved along the last third of the long end, giving it a somewhat talon-like appearance. Several NEs noted the resemblance, though only vaguely. The wall edges were frayed with ODN relays poking out, along with an EPS relay. An access terminal along one wall seemed viable, but it was unclear if there was anything useful there.

Along the edges, the piece showed signs of buckling and mechanical stress, along with tendrils of metal that had streamed off and then cooled in the vacuum. In a few spots it seemed the metal had ejected away or just flown apart. Whatever had happened to the B’hari was quite violent.


Teller picked up a scanner and gave the piece of debris the once over. “So it is reading low levels of particle emissions emanating from the materials, but I think we are safe enough to ditch the suits,” Teller advised those moving around.

Looking at the ship, Teller noticed one section of the ship with ODN and EPS relays which looked viable. Grabbing a matrix injector, he plugged it into the access terminal along one wall hoping it would glean some information for them about what happened.

Teller CSO

Charles, relieved, took off his headgear. He gave the fragment a quick glance to see if he could identify anything about the ship that stood out.

“So guess what do you think we are looking at,” Teller asked as he waited to see if he was able to hook into the ODN and EPS relays and what information he might be able to find.

Teller CSO
“A cargo ship?” he guessed out loud. It might have been a good guess, or simply his experience. He approached the areas where it appeared to have been separated from the rest of the ship.

“Now, what happened to you?” Charles pondered. He pulled out a tricorder and began scanning for any kind of anomalies in the metal or energy signals. Anything that could give him a clue as to what cause the damage.

[Ensign Charles-Louis, Engineering]


The tricorder readings would start to come back immediately. There were signs of thermal shock, along with mechanical sheering, and the leftover effects of nadion discharge, including various isotopes in a few points in the materials. High-energy phaser weaponry. Which at least confirmed that the ship had been attacked.

It took a few moments for the matrix injector interface pondered for a few moments before coming to life. The internal power supply began cycling energy into the relays, and a moment later the console lit up. A quick synching diagnostic scrolled along the matrix readout, then mirrored the information in the console. It appeared to be one of the auxiliary panels from the command module or bridge.

Who knew what waited in it’s digital depths.


“Nothing too unusual, reading indicate phaser fire.” Charles commented.

Charles came over to watched the console over the shoulder of the CSO.

“But it doesn’t appear the relays were significantly damaged. That is a good start.”

[Ensign Charles-Louis, Engineering]

Teller nodded. “There are signs of thermal shock and mechanical shearing but the ship is in pieces so it backs up some kind of explosion like the CMO reported to the bridge.” Nat’s message was shared with the teams however with nothing to report, Teller never responded but filed away the information.

“I am still getting enough nadion coming off this stuff to make it a mystery but not enough to make it a worry.”

Tapping the console once the matrix injector interface came on line, Teller waited for a second before announcing,” okay this seems to be one of the auxiliary panels from the command module or bridge. Trying to ascertain which one now. ” Depending on where it came from might relay different data. “Running a scan to see if I can bring up some logs to help us figure out what happened to them.

Teller CSO

Logs began to scroll up the display rapidly. Dozens, if not hundreds of them, scrolled past. All generated by the ships systems, computer, and the various actions of running a starship. Of course, something like the Saracen generated much more data to sort through. And this particular panel wasn’t anything as significant as a full operations console. It was a lot to crunch. However, the most recent logs weren’t hard to find. Bland, boring, dry technical readouts. Sensor data. and all sorts of telemetry. A veritable haystack, and a mess of jumbled, but intact data.

((Lemme know what you guys wanna look for, and I’ll see if she’s got that this chunk of computer infrastructure. Thankfully the isolinear array is still attached to the panel, so all the data it holds is still there. Each console has some measure of data storage, besides what’s available in other areas. Kind of a mix of local harddrive and RAM.))


“Phew,” Teller let out a whistle seeing the data. “This is going to take a minute.” Tapping his badge he contacted the bridge.

=/=Captain we have brought up a data cache from the wreck but we are gonna need a minute to figure out what we have adn what we can use. I will contact you when I have something.=/=

=/\= Good work Teller, =/\= Dante replied over the comm, =/\= Stay alert, we may have company soon. =/\=

Looking at the console he punched a few buttons and then said =/=Computer can you isolate the date dealing with long range scans prior to the ship being attacked and any information gained in that. Also bring up the weapons log and any information about what we used or what we were hit with.”

The list was long but hopefully there would be a hit somewhere.

Teller CSO

Charles waited for the computer’s response, arms crossed. He let out a sigh.

“We must certainly find something, no? Hopefully it is something useful.” he commented.

“One time I was trying to recover data from an engineering console: direct phaser hit, almost completely in pieces, barely held together with electrical tape. The only thing we could recover was the replicator recipe for tomato soup.”

[Ensign Charles-Louis, Engineering]

((It’s so hard to resist turning that into a quick gag, but this is not the Constellation))

The computer pondered the instructions for a moment. Most of the request was hilariously basic. The database quickly filtered and organized itself in front of them by the most recent dates, with the most recent at the top. Knowing the parameters of the current main mission for the Saracen, it selected the most recent files/logs, chopping away the non-essentials for the last little bit. The last minutes of the B’hari’s life began to take shape. There wasn’t much external sensor information available, and much of the files were still encoded.

Pondering it’s plan of attack, the Pendragon’s powerful computer chunked off some of it’s processing power. Electronically cracking it’s knuckles it went to work, decyphering, and unscrambling what it could. Five seconds later, an eternity for a machine, the computer began displaying lines of text and logs. It was a lot to sort through still. And humans usually preferred simplicity. And as per LCARS, it was always better to ascertain intent and act accordingly. The text vanished, but then a moment later the display began showing a gallery of readouts, each labeled, along with a timeline as best the ship’s electronic brain could come up with, based on the data available in an auxiliary panel.

((Assuming you guys want the playback))

The ship had been traversing through the system, taking survey scans with it’s limited scanning suite. It wasn’t as good as almost any Starfleet ship in that regard, but they were serviceable. They were drawing near one of the planets when an alert went out across the B’hari’s systems as they picked up tachyons and neutrinos. The alert scaled up into red alert, and power feeds shifted to feed energy into the B’hari’s shields, which immediately registered being struck by a column of nadion particles. A phaser beam. Power fed from the engines into impulse and thrusters, and inertial dampers. She was maneuvering.

On one of the displays, the computer interpreted the data quickly, showing the B’hari pitch her nose down, roll, and essentially bank. The shields registered an intense cascade of photons. A torpedo detonation. The B’hari’s phaser banks were charged by then, and were returning fire, even as the ship was heating up from the increased energy output and usage.

Damage reports scrolled in as well, impacts along the frame from phaser fire. The ship went from sluggish to ponderous, while the crew yelled into the void for help. It took a moment to scrub through what it had. There was a decayed copy in the buffer of the transmission. Pulling from the stored comms logs in the Saracen’s memory, the computer compared the two. Both were a mess, but having more pieces of the puzzle, the accuracy rose and rose again.

It flagged the comms log and transmission information with an update, along with the other readouts.


“An unexpected attack…” Charles commented dryly. “It looks like she barely had a chance to retaliate.”

[Ensign Charles-Louis, Engineering]

He scanned the massive amounts of information looking for something the bridge might need. Finding it he hit is comm badge. =/+Sir the logs are showing that the ship was hit with a massive disruptor type weapon that emitted nadion radiation. It is usually only found in phasers but it appears like they turned it into a weapon on the scale of a ship. Sending you all data we have so far=/=

Teller CSO

Picking up on Teller’s focus, Charles offered a suggestion,

“Given the size of the initial impact area on the shields, the level of shield drainage, and the distance of the hostile ship according to onboard sensors, and assuming normal particle scattering through space, we could estimate the potential power output and range of this weapon.”

Normally, he would have entered these parameters and done the calculations by hand. However, he was excited to see the capability of the Pendragon-class computer system.

“Computer,” he prompted, “Calculate the output and estimated maximum range of the nadion weapon fired by the enemy ship. Cross reference these capabilities with known weaponry, including non-federation technology. Output potential candidates for the identity of the weapon.” Charles-Louis used the console to manually highlight the data he wanted to include in the calculation, out of habit.

“Given the sensor readings, we can estimate the size of the ship. This should narrow down the list further.”

[Ensign Charles-Louis, Engineering]

((As a reminder, you’re looking at a very small module of the ship, with a pretty limited data set, despite the amount of logs, and the B’hari itself is around a century old, civilian vessel, and possibly rickety from age.))

The computer chewed on the information for a minute thoughtfully. The nadion particles had their own frequency and tuning. There weren’t many other powers in the region that actually used phaser technology. Federation, of course. But nothing in their records was as powerful and used that kind of tuning. It was lower frequency, which had a lower pulse cycle. Bajorans were more in line with Federation standard. But the Cardassians…

Teller let out a small whistle seeing the response to Charies’ query. “The Galor-class medium cruiser, or the Keldon-class heavy cruiser,” he stated the names scrolling on the screen. “Both are Cardassian but with the energy profile of a Bajorn Keldon-class. From a weapons POV it is the best o both worlds but for the person on the receiving it is jus plain sucks ah,” he started before being interrupted.

That brought out some possibilities. Mentally it scrawled through the known Cardassian ship types that might match. High energy output, well.. more high energy. A particle weapon was pretty high energy output to begin with.

Two ships popped up with that consideration - The Galor-class medium cruiser, or the Keldon-class heavy cruiser, both Cardassian. Comparing the energy profiles, it leaned closer to the Keldon-class as it used a phase disruptor. Best of both worlds.


At that moment, the lights denoting the ship was moving into Red Alert sounded, joined by the alarm Klaxon.

Captain Knight

“Okay this is going to be fun if the ship that did this just arrived on our doorrstep,” Teller frowned.


Charles let out a chuckle.

“Indeed it will be, Commandant!” he said, almost beaming at the thought of entering battle.

“A Keldon-class vessel is a worthy opponent for our Saracen, no?”

[Ensign Charles-Louis, Engineering]

((Y’all are adorable. - Rei))

“Well if you compare the two ships we have 100 more officers to repeal boarders if this goes south. We have 9 phasers. They have 8 disruptors, but numbers aren’t a direct power correlation in this sort of comparison,” Teller stated in a neutral tone.

Teller CSO.

((Unless you guys want to recover and review the message from the comms buffer, there’s not much left to do right now. The Saracen is in a standoff and in combat conditions/battle stations.. and there haven’t been any new inquiries (to my knowledge) unless I missed one somewhere. So you’re not really waiting on me. It’s y’all’s thread. :)

Sam ))

ookay.. do we need the Captain to order something or are you expecting somehting else


((Uh, not really. Just presenting options, since it seems y’all might be waiting on me, and I’m waiting on y’all. Though in truth in a red alert/battle stations situation like this senior crew would report to their stations, and have NE’s secure the wreckage so it’s not banging around or getting blown back out into space while the ship is under potential maneuvers or fires. It’s up to you what you guys wanna do though. Or we can tie this thread off and call it a day. ^_^

Sam H.))

Posts on USS Saracen

In topic

Posted since

© 1991-2023 STF. Terms of Service

Version 1.13.2