ZE/D01 - Bridge
The saurian felt a great sense of relief once he had heard from Raven. After the reports of the various casualties and injuries had caught his attention he feared the worst for members of the crew that he was close with. He had been cut off from getting in contact with the Engineering Bay earlier due to the Cardassian attack but right now his main focus was keeping the ship together while they were going to engage the enemy vessels.

[Understood, glad to hear you’re alright. Be safe down there. A’kilees out.]

A’kilees looked towards Morad who was firmly sitting in the captain's chair.

“Commander, Ensign Singer is reporting that control over deflectors and structural integrity has been restored but there are still multiple issues ship wide. We’re repairing plasma coolant leaks in the warp core so no warp capabilities currently. Lastly, the secondary hull is exposed and currently off limits.”

The saurian plugged a few more final commands into the engineering console.

“Damaged warped manifolds have been shut and plasma has been vented away from the core. Power has been rerouted to both the Structural Integrity Field and the aft shield emitters. Currently diverting power away from redundant systems to the forward shields. Ready for further orders.”

=== Tag Morad Ameen et al. ===
Reply
Even if the probes were not doing the job they wanted, they were doing something equally as good. They were creating a lot of confusion, so Keti was looking for a way to turn up the noise. If they were to increase the chatter between the probes, the better they might be. While Keti was accessing the controls of more than one probe he was assigning them a higher level of priority, the frequencies that they used were now alternating with what seemed like every message.

Keti enjoyed the idea of using the gravimetric pulse, it was going to hopefully work. While this was going on Keti was using what available sensors to scan the remaining ships, if they can get a better idea of what the others were doing they could plan their next step. These Escorts were not going to be easy to take care of, and Keti knew they could not fail. The problem was how were they going to do it, Keti took a loot around the Bridge for a second. Everyone had good ideas, it was going to take a bit to put it into practice. 

Right now they had two shuttles they could use, it was just going to be difficult to think of how. He wouldn't want to be on the shuttle more than anyone else, it would be a one way trip. While everything was uploading for the changes, Keti started to think about how to make a mine out of a shuttle. 

"Captain the changes are going to be uploaded any second, we will know right away if it works." Keti was attempting to sheild his voice of any doubt. 

==GM input do the changes help? also is there any updates on the ships Keti can get?==
Reply
Amila couldn't help but notice that Cortez had volunteered to help with environmental controls, but now was talking about the probes again.

"Cortez," Amila asked, "Are you still working with Baldwin on keeping life support in the essential parts of the ship within safe parameters while Molina redistributes power?"

"Don't spread yourself too thin," she warned. "One thing at a time, or you might miss something. Monitor that situation until everything is all clear. You've got the rest of us watching the Hidekis for now. Keti's got your back. Our people are important, and we're losing viable areas of the ship."

She pulled on her hair, tightening her ponytail, a nervous habit, as she continued to dig into what she could find. Really, less than a minute had passed, but it felt like so much longer. She could feel her uniform start to stick to the sweat on her back, but it was hardly a worry. 


==Tag Cortez==



==GM Zephyr, what are Baldwin and Cortez learning about the condition of the ship?  What challenges will Cortez face in keeping essential areas stable for the crew; Specifially Baldwin asked about structural integrity of Deck 3; and is she ordered/needed to help with tactical? 

Also - to Keti's thought, do we have two shuttles, or did we lose one in the last mission? - Thanks! ==
-

==GM CD, apologies, basically summarizing what science has been asking to put in one place for you : (1) How are the Hidekis responding to ECM probes, is there anything to Cortez's suggestion of a narrow range of modulation frequencies and suggestion of calculating their shield pulse parameters with probe frequencies to help tactical? Is Keti learning any more with sensors and trying to turn up the noise==
Reply
Sebastian glanced toward Amila's station before returning his attention to the environmental-control display.

"Lieutenant Ra'an, I wasn't shifting over to the shields. I was offering a general suggestion based on the telemetry we've been seeing. Ensign Baldwin and I are still working the life-support problem."

He pulled Ensign Baldwin's environmental-control feed alongside his own readings, comparing pressure, temperature, and atmospheric circulation across the remaining viable sections.

"Ensign, I've got the life-support grid mapped against the current power distribution. I'm going to take the nonessential environmental loads offline in the affected sections and isolate their circulation loops. That should keep the remaining power available for atmosphere processing and primary environmental controls."

He began making the adjustments, shutting down climate-control systems in unoccupied areas and closing several secondary circulation paths. The remaining life-support nodes immediately showed a more stable power draw.

"I've also isolated the sections that are already compromised. We don't need to spend power trying to maintain areas we can't safely occupy, and separating those systems should reduce the load on the surviving environmental-control network."

Sebastian checked the latest readings before continuing.

"Ensign, if you can keep your power reroute away from these primary life-support feeds, I'll balance the environmental loads against whatever Lieutenant Molina can spare. That should give us a little more margin while the redistribution continues."

He turned his attention back to the atmospheric processors, watching the oxygen-generation and carbon-dioxide scrubber loads settle.

"We're getting a much cleaner power profile now. I'll keep working with you on the environmental systems while the rest of the bridge handles the tactical picture. Once we've stabilized the occupied sections, we can look at the shield telemetry again."



== TAg Ra'an and Baldwin. ==
Reply
As the Zephyr joined the battle properly, one thing became apparent very quickly. The Intelligence files on the Cardassian military were woefully out of date. The opponents they faced weren't the Cardassian military of the 2370s, or even the early 2390s, when the backbone had been conscripted crew led by a solid core of technical specialists and an "Officer Class" that  seemingly existed to accrue seniority, promotion, and political clout off the backs of their subordinates' labor. The technology they were facing was state-of-the-art, even if the spaceframes weren't, and the crews appeared to be at the top of their game.

The three Hidekis formed up around the Zephyr in a triangular formation that allowed them to bring their forward cannons to bear, albeit at the maximum angle allowed by the hardware, while keeping themselves protected from all but a few of the Zephyr's phaser banks. Whenever Krandall manoeuvred to try and get one in the forward weapon arcs, the Hidekis matched his moves where possible, or scattered and rejoined formation once sufficient distance had been gained. While the Hidekis could easily match the larger Zephyr move for move, it seemed as though they were unable to accelerate quite as fast as the Zephyr, having been built as patrol/assault craft relying on agility and forward firepower, while the Zephyr had been built as a "torpedo boat" with rapid response and single-vector velocity in mind.

The Electronic Countermeasures briefly spoofed the Cardassians, sending what should have been a kill-shot with a Photon Torpedo wide, detonating harmlessly off the Zephyr's bow. However, intense Counter-Countermeasures burned through the interference, wreaking havoc on the Zephyr's own sensors while science teams raced to counter it. There had not been enough time to calculate the shifting frequency of the Hidekis' shields, but the scan would continue once the jamming was cleared.

For now, the Zephyr was holding her own. The thirty year old spaceframe wasn't enjoying the rapid and aggressive manoeuvres she was being subjected to, but thanks to Baldwon's efforts, she was at no immediate danger of flying apart or suffering any more EPS explosions.
Reply
== GM-Zephyr ==

Across the bridge consoles, the rapid coordination between Science and Operations begins to bear fruit, bringing a measure of stability to the ship's taxed internal grid.

Working in close concert with Ensign Baldwin’s triage routing, Cortez’s emergency environmental protocol successfully isolates the compromised compartments and throttles climate controls in evacuated sections down to survival minimums. The immediate drop in auxiliary draw allows the primary environmental loop to breathe; atmospheric scrubbers and oxygen-generation units settle into a steady, reliable baseline. Throughout occupied spaces; from the bridge and Sickbay to the secondary triage center established in the Mess Hall, the air feels cool and noticeably still, but clean and sustainable.

Down on Deck 3, the thermal alarms along the EPS power conduits remain lit, but Baldwin's re-balancing act keeps the junctions from cascading into further blowouts. The structural integrity field groans audibly under the strain of Krandall’s relentless dogfight maneuvers, yet the primary saucer framing holds firm, reporting no secondary breaches or imminent structural failures. Meanwhile, auxiliary hangar diagnostics confirm that both Type-14 shuttlecraft; the Aura and the Boreas, remain secured in their respective bays, fully fueled and in operational condition should Command require them.
Reply
Morad gripped the edges of the center console as the deck shuddered, the visual feed momentarily strobing with static as Cardassian counter-measures washed across the sensor arrays. The Hidekis were disciplined, deadly, and tightly coordinated, dancing just along the fringes of the Zephyr’s primary phaser arcs and refusing to give Powl a clean shot.

They’re matching our turns, but they don't have our straight-line muscle, Morad realized, watching the tactical plot update with a sudden surge of clarity. Old girl was built to sprint and hit...

"Krandall, break the weave!" Morad commanded, his voice cutting cleanly through the hum of the bridge. "Stop trying to out-turn them. They’re built for knife-fights, but they can't match our straight-line acceleration. Punch full impulse on a single burst vector, heading zero-two-five mark zero-one-zero. Blow through their formation and force them into a tail chase!"

He leaned over the display, plotting the vector directly toward the Star Base's defensive envelope before glancing back at the tactical console.

"Keep that line burning straight toward the station's perimeter," Ameen added with a grim edge. "If they want to stay on our six, we'll drag them right through Starbase 214’s heavy battery kill zones. And Powl, prep our aft torpedo tube. The second they commit to our baffles and try to close the distance, feed them a spread right down their throats. Let's see how tight their formation holds when they're chasing into heavy ordnance."

Turning toward Science, Morad’s eyes locked onto Ra'an and her team.

"Amila, our probes' first ECM attack saved the day! Launch a renewed effort on their sensors, get creative and try to bog them down again. Focus all auxiliary sensor power through the ventral and saucer arrays. Burn through any other counter-jamming they try and continue to boost our own resolution. Yes, they are better than we thought, but if they think they can compete with Star Fleet Science and sensors, they have another thing coming."  Morad leaned toward their console, the tension in his jaw giving way to a sharp, defiant smirk. His eyes locked onto Amila for a split second, carrying that unspoken, absolute trust between them, before sweeping to Keti and Cortez with a challenging nod. "You three are the smartest minds in this sector. Now go remind them who wrote the book on electronic warfare. Don't hold back!"

He then pivoted toward the engineering station, a seat that still held a special place in his heart, meeting the Saurian's gaze directly and offering a firm, appreciative nod.

"A'kilees, outstanding work keeping the core clamped down and getting deflector control back in our hands," Ameen said, his voice warming with genuine pride. "Your team saved us from a total collapse. Now, I need you to keep that impulse manifold fed with clean power. Don't let her starve; we need every ounce of thrust this old girl has got!"

== Tag Bridge ==
Reply
"That was too close," Amila muttered nervously as she watched the way they formed up around them. "They are trying to surround us."

Krandells flying was keeping them alive, but it wasn't a comfortable ride. Inertial dampeners took a hit with their first jump, and she could feel the ship moving in ways that she wasn't used to. She did her best to relax her body at her station so that she could move with the inertia, but with every broad sensor scan of the situation - relaxing just wasn't an option. 

They took another hit. She flinched and stepped back from her panel, but thankfully this one wasn't as bad as the first, but the sensors on the ship were glitching horribly. She glanced over and saw that Keti and Sebastian still had operational readings on from the probes.

It was sensors, not the computer.

She scrambled to adjust and bring the Zephyr's sensors back online after the hit. Ameen's quick response gave her direction to move the concentration to the ventral and saucer arrays. Krandell was going to try to outrun them.

"Cortez, if life support is stable, Officer Molina can take over," she ordered. "You and Jukish and going to need to get creative to keep our probes in play - and we're going to need them to stay in the fight. I think if the Hidekis try to chase us at that heading, trailing them in a straight line is going to be a sure tip off if we're able to get away. I know you can think of something, you guys are doing great."


==Tag Cortez and Keti==
Reply
Sebastian kept one hand on the edge of his console as another vibration passed through the deck. The primary sensor display remained unreliable, but the telemetry coming through the surviving probe feeds was still usable. There was not enough information for a complete tactical picture, but the differences between the individual feeds were beginning to reveal something about how the Cardassians were fighting.

He brought the separate probe feeds onto his secondary display and compared them side by side.

"Lieutenant Ra'an, I think you're right about the probes trailing us being too predictable." Sebastian watched the three Hideki contacts shift across the remaining sensor data. "They're already matching our turns when they can, so if we give them a predictable sensor pattern, they'll probably use it to anticipate where we're going."

He highlighted the probe positions relative to the Zephyr's projected flight path.

"Would it help if we spread the probes laterally instead? That would give us observations from different angles while Krandall keeps them moving. We might be able to see which of the Hidekis is actually committing to a turn and which one is simply maintaining formation."

Sebastian brought up another set of readings.

"It could also help with the acceleration difference we're seeing. They can stay with us through the turns, but they aren't matching the Zephyr's straight-line acceleration as well. If we can maintain sensor coverage outside our immediate flight path, we might be able to see when they're forced to break formation to keep up."

His attention shifted toward Lieutenant Jukish.

"Lieutenant Jukish, I have a possible way we might get a little more information out of the probes. If we stagger their emission frequencies rather than having all of them operate in the same band, we could compare how the Cardassian interference affects each one."

Sebastian brought up a simple model of the three probe signals.

"Essentially, we'd be giving the countermeasures three slightly different problems to solve. If the interference follows all three equally, we're probably dealing with broad-spectrum suppression. If it follows only one or two, we may be able to identify what characteristics they're using to prioritize their jamming."

He looked directly toward Jukish.

"What do you think? Would the probes tolerate that kind of frequency separation without compromising their ability to share data? If they can, I could correlate the three telemetry streams and see whether there's a pattern."

Sebastian returned his attention to the Hideki contacts.

"And if we can establish that pattern, Lieutenant Ra'an, it might give you a cleaner sensor picture during the next maneuver. Even a few seconds of reliable tracking could make a difference when they're trying to stay just outside our phaser arcs."

He checked the environmental controls. Life support remained stable.

"Everything on the environmental side is holding, so I can keep working the telemetry from here. I'll correlate the probe positions, interference levels, and the Hidekis' movements. If either of you sees something that doesn't fit, let me know. Having the science and probe data cross-checked in real time may be our best chance of figuring out what they're doing."

Another burst of static crawled across the primary sensor display.

Sebastian watched the three faint contacts reappear through the interference.

"They're showing us how they want to fight this battle. If we can figure out what their sensors are telling them, maybe we can find the part of the fight they're not seeing."



== Tag Ra'an and Keti.==
Reply
Amila listened to Sebastian's points as she focused not only on getting them ready to hopefully outrun the Hidekis, but also keeping an eye open for any surprises that might heading their way.

"... If we can figure out what their sensors are telling them, maybe we can find the part of the fight they're not seeing," he offered.

"Yeah, you're right," Amila said. "But also, I think that ECM attack you guys did is what kept them from getting a direct hit. The way they were on us, we should have taken a lot more damage. You've seen their shields are better that we thought, I'm guessing their sensors are too. We might have to do more than just spread out like you said..."

Amila thought for a moment. "Could we go dark with them somehow and come back? Turn the lights out, or find a blind spot before we hit them again? But we need to do it before they hit us, so we'd have to move fast."



==Tag Cortez and Jukish==
Reply
== NPC Lt Tom Krandall, Tactical Officer, Helm ==

Just as Tom was about to have the line on an enemy, the other two hit hard on the port side in almost the exact same spot, The very hard hit caused the ship to rock a bit and he was forced to let the enemy get away briefly while he reacted and kept them alive. The three were actually coordinating better than he had thought and just as he was rethinking the fight, he was told to try and draw them toward the base.

"Alright, at least that's easier than trying to be on the offensive with three ships. Doing pure evasive and working our way to the base."

Tom did a roll that allowed him to then bank hard out of it and begin more evasive efforts to doge erratically as he punched the throttle to make them give chase.

Powl had missed the chance to fire on the one and now would have to hope he got a chance to fire from the rear arcs to hit any of those still giving chase.

== Tag all ==
Reply
It was clear that they were not going to win this by any kind of brute force, they were going to need to be more creative. The ECM was working perfectly now they were going to have to go more in depth, while Keti was paying attention to what was going on it almost looked like he wasn't. He was hard at work putting in further instructions to the probes, the purpose was to increase the activities between the probes. He wanted to give them something a little more interesting, it might give them the upper hand somehow.

As part of the process the communications were being staggered, some even went quiet only receiving communications never sending them. One of the probes "collecting information" went dark, suddenly two went dark both of them were no longer sending or receiving anything. This was part of the sleeper program that was already programmed, it was designed to be like a mine. Once the enemy ship went to go collect it, the programming would send it into overload and explode. It had the promise of doing some damage, but there was no way of knowing how much. 

Two of the probes that were the furthest apart from each other, they were starting the process to hack into the Cardassian systems. The main purpose of this was to hopefully get them to break apart into a smaller group, what was left might be easier to handle or even slip through. If that was even a good idea, Keti would allow the Command team to figure that out. Right now the probes were going from data collection to dump, once they were ready the flow if information would overwhelm theirs. 

That part of the plan would take time, Keti was focused on making the probes unpredictable to the Cardassians. As he worked everything was in the open for anyone on the Bridge to see, the adjustments that Keti was making  took some time to do. A few seconds turned to minutes, thankfully not hours. "Updates are being uploaded right now." Keti closed his eyes for a second then blinked a few times. "I am not sure how this is going to work but its something." Keti started to hope more attention to the probes would take away from their own.

==GM input on how the changes work, and tag.==
Reply
Ensign Cortez pulled Ensign Baldwin's environmental-control feed alongside his own readings, comparing pressure, temperature, and atmospheric circulation across the remaining viable sections.

Ens Cortez spoke directly to Ens Baldwin, "Ensign, I've got the life-support grid mapped against the current power distribution. I'm going to take the nonessential environmental loads offline in the affected sections and isolate their circulation loops. That should keep the remaining power available for atmosphere processing and primary environmental controls."

There was a short pause and he spoke to Ens Baldwin again.

"I've also isolated the sections that are already compromised. We don't need to spend power trying to maintain areas we can't safely occupy, and separating those systems should reduce the load on the surviving environmental-control network."

Sebastian look at his console and checked the latest readings before continuing.

"Ensign, if you can keep your power reroute away from these primary life-support feeds, I'll balance the environmental loads against whatever Lieutenant Molina can spare. That should give us a little more margin while the redistribution continues."

"That is fine Ens Cortex, my reroutes have not include life support. Please do not increase the power levels through the EPS junctions on deck three; I have orders to protect the secondary sensor feeds from any damage via power surges and alike. The power levels through the EPS junctions on deck three are critical to the Secondary Sensors they feed information to and from the probes. I am monitoring the EPS junction on deck three."


== Tag Ens Cortez. ==
Reply
==NPC Ava O'Fee Science==

There was a lot for Ava to process, the attacks of both ships and how the Cardassian ships were handling it. They might have advanced their technology but not the ship as a whole, its like building a great house on a bad foundation eventually it was going to fail. There was an idea that she had, but it needed work. If they were to launch the shuttles, they could get in close to launch smaller attacks. Giving them smaller targets that attack, the harder it would be for them to defend. 

"Captain permission to launch the shuttles, if we can get them close enough they can evade attack from one of the ships. If they were close enough the other ships won't attack, unless they changed their policy about not firing on another Cardassian ship." It was a bit of a long shot at best, however in times like this almost any idea is a good one. 

==Tag==
Reply
Ensign Cortez acknowledged Ensign Baldwin’s warning with a brief nod, immediately bringing the Deck Three EPS junction telemetry onto a secondary display. He had no intention of jeopardizing the sensor feeds, particularly while the USS Zephyr was still engaged with the Cardassian forces. The secondary sensors and their associated probes might prove essential to understanding the enemy’s movements, and a power surge could cost them information they could not afford to lose.

Rather than increase the power flowing through the junctions, he began examining the environmental-control network for inefficiencies elsewhere.

“Understood, Ensign Baldwin. I’ll leave the Deck Three junctions and your secondary sensor feeds untouched. I’m more interested in finding out how much of our existing power we’re losing to environmental systems that are working harder than they need to.”


Sebastian called up the environmental grid’s operational history and began comparing current consumption against pre-engagement baselines. The damage to the Zephyr had forced several environmental systems to compensate for compromised circulation, while automatic regulators continued attempting to maintain standard conditions in sections that were no longer habitable. It was a sensible safety response under ordinary circumstances, but the ship was operating under anything but ordinary circumstances.


He isolated the pressure-regulation and thermal-control demands from the circulation systems, studying how they interacted across the surviving sections. A pattern began to emerge. Several intact environmental zones were receiving overlapping thermal compensation because their neighboring sections had suffered pressure losses. The regulators were responding independently, each trying to correct conditions that another system was already addressing.

Sebastian leaned closer to the display.

“That’s our problem. We have regulators fighting the same environmental imbalance from different parts of the network. We’re not necessarily short of power everywhere; we’re wasting some of what we have compensating for the same problem twice.”


He began adjusting the environmental-control logic, grouping the unaffected compartments into coordinated control zones rather than allowing every regulator to respond independently. He retained independent safeguards for pressure loss, atmospheric contamination, and sudden temperature changes, ensuring that the adjustments would not compromise the crew’s immediate safety. The revised configuration would allow the system to share environmental data across the intact sections, anticipate fluctuations, and reduce unnecessary corrective cycles.


He then opened a second diagnostic window, this time examining the power draw of the atmospheric processors themselves. Instead of attempting to increase their supply, he adjusted the sequencing of noncritical filtration and atmospheric-conditioning cycles, staggering those that did not require uninterrupted operation. Oxygen regeneration, carbon-dioxide removal, and emergency pressure control remained prioritized; only processes with sufficient reserve capacity were rescheduled.


It was a small change in principle, but across multiple decks, the reduction in simultaneous demand could provide the environmental network with a valuable margin without placing additional strain on the EPS junctions.
Sebastian transmitted the revised load profile to Ensign Baldwin for review.


“Ensign, I’ve reorganized the environmental regulators into coordinated zones and staggered the noncritical conditioning cycles. The primary atmospheric processors and emergency safeguards retain priority, and I haven’t increased the load on Deck Three. Would you be able to compare this against your current power-distribution model? I’d like to confirm that the reduced demand translates into usable capacity without creating a fluctuation on your sensor feeds.”

He checked the life-support telemetry again. The figures were beginning to settle, though he resisted the temptation to call the adjustment a success before the system had completed another diagnostic cycle.

There was still another possibility worth investigating. The Zephyr’s damage had forced some environmental systems to operate in isolation, depriving them of the predictive data normally supplied by neighboring compartments. If he could restore limited telemetry between the surviving environmental controllers without reconnecting their damaged power circuits, they might anticipate pressure and temperature changes instead of reacting after the fact.

He opened a diagnostic partition and began testing that possibility in simulation first, keeping the proposed data links electrically isolated from the power-distribution network

“I’m also testing a way to share environmental telemetry between the intact sections without reconnecting their power circuits. If the simulation holds, we may be able to reduce the regulators’ reaction time and prevent another unnecessary spike in demand. I won’t put it into operation until I’ve confirmed that the data links are isolated from the damaged network.”

For the first time in several minutes, Sebastian had a potential solution that did not depend on asking the ship for power it might not have. The Zephyr was fighting for survival, and every available system had to justify its demands on the remaining resources. His job was not to make life support consume less at the expense of the crew. It was to make the system work intelligently enough that the power it received went where it mattered most. And if the adjustments worked, the power saved across the environmental network could remain available for the ship’s other critical systems, without jeopardizing the secondary sensors Ensign Baldwin had been ordered to protect.

== GM: Input: Does the simulation support Sebastian’s proposal to share telemetry between the intact environmental-control systems, and are there any technical complications, limitations, or risks he should address before implementing it? ==


== Tag Baldwin and all. ==
Reply
Cortez sounded busy helping Baldwin keep the crew alive as they funnelled people away from areas they needed to be sealed off and anticipated more damage while Keti seemed to be working hard to help implement Cortez's ideas along with his own on how to keep the probes in play as Krandell initiated the chase when Amila heard Ava speak out.

Commander O'Fee's voice carried to Amila's station, "Captain permission to launch the shuttles, if we can get them close enough they can evade attack from one of the ships. If they were close enough the other ships won't attack, unless they changed their policy about not firing on another Cardassian ship."

How can we... that sounds like a suicide mission. Amila thought.

The shuttles were just as old as the ship. Trying to pilot the ships remotely would be clunky at best.

Then Amila remembered that Raven had used some type of drone in the science lab with them. She had mentioned it's intelligence was backed up or something, so it wouldn't act out like the exo-comps.

"Captain," Amila spoke out. In the midst of the emergency she had time to wonder if she would get flack for calling him that later, if they survived.

"Raven, Raven Singer in engineering. She might have a way to pilot the shuttles if you are considering it," Amila offered, briefly turning away from her panel to guage his response.



==Tag Ameen, any==
Reply
== NPC Lt Tom Krandall, Tactical Officer, Helm ==

Tom was managing to evade most of the incoming fire, but then said to Powl, "For a few seconds, I'm going to use a basic figure eight evasive pattern. I'll line you up on at least two of the targets, but then I'll have to change my pattern or the enemy is going to be able to take advantage of it. Ready? Here we go...."

As stated, Tome made some rather wildly exaggerated moves, then suddenly swung the ship into the figure eight. Powl saw the targets quickly brought into the rear firing arc and he let lose with everything he had available. Then, just as quickly, the ship came around to line up a second ship that was hot on their heels and was able to let loose a second salvo. Tom was keeping things moving with the throttle at full, just trying to keep them guessing. He didn't have time to see if the shots landed or not. The enemy wasn't backing down and they were pouring on plenty of effort in their own firing patterns.

== Tags to all. Posted with permission for Powl's actions. ==
== GM Input: Do they hit anything? Is it good, bad, or ugly? ==
Reply
Rather than increase the power flowing through the junctions, Cortez began examining the environmental-control network for inefficiencies elsewhere.

“Understood, Ensign Baldwin," said Ens Cortez, "I’ll leave the Deck Three junctions and your secondary sensor feeds untouched. I’m more interested in finding out how much of our existing power we’re losing to environmental systems that are working harder than they need to.”

Ens Ava Baldwin could see on her console that the EPS junction on deck three where not experiencing additional strain at the moment..


The same information was showing on Ens Cortez's transmittion of revised load profile to Ensign Baldwin for review. But it was early in the battle, and she watched the Juctions on Deck three and the secendary sensors for any spikes and/or damage.

“Ensign, I’ve reorganized the environmental regulators into coordinated zones and staggered the noncritical conditioning cycles. The primary atmospheric processors and emergency safeguards retain priority, and I haven’t increased the load on Deck Three. Would you be able to compare this against your current power-distribution model? I’d like to confirm that the reduced demand translates into usable capacity without creating a fluctuation on your sensor feeds.”

Baldwin worked quickly to compare the information Sebastian had sent her.

"When I'm sure its stable, I'll let you know," she replied.


== GM input, please?
1. As the battle continues, apart from a direct hit by enemy fire, do the EPS junction on Deck Three and the secondary sensor array remain stable.

2. Is there anything else that Ens Baldwin could assist with? ==
Reply
== GM-Zephyr ==

Inside the Zephyr, the coordinated push between Science, Operations, and Flight Control pushes the thirty-year-old Steamrunner’s internal grid to the razor's edge, yet the ship holds together through sheer engineering grit.

As Ra'an shifts primary sensory concentration to the ventral and saucer arrays, the initial spike in auxiliary power draw courses directly through the Deck 3 EPS relays. For a tense few seconds, thermal warnings along the secondary sensor trunks flare into the red, especially as the double disruptor strike reported by Krandall hammers the port shields and sends a heavy electromagnetic feedback surge rippling down the portside conduits. However, Baldwin’s preemptive isolation protocols and load-shedding dampers catch the spike just before the relays can blow. The circuit breakers groan and a pair of secondary diagnostic monitors at the back of the bridge flicker with static, but the secondary sensor feeds remain intact, giving Cortez and Keti clean, uninterrupted telemetry lines to compile and transmit their updated probe instructions.

Meanwhile, the transition from tight dogfighting turns into a straight-line impulse sprint, punctuated by the violent lateral shear of Krandall’s sudden figure-eight maneuver and the heavy power draw of Powl’s back-to-back aft salvos, places immense strain on the spaceframe, yet the Zephyr’s internal grid holds with remarkable resilience. With Officer Molina monitoring the primary environmental controls, the isolated life-support loop remains steady under the heavy demands of the twin impulse engines.

At the Science and Operations consoles, the diagnostic partition completes its pass on Cortez’s proposed environmental telemetry link. The simulation confirms that sharing predictive pressure and thermal data across the intact control zones via the ship's optical data network (ODN), keeping the pathways completely isolated from the damaged EPS power circuits, is viable and will reduce regulator reaction times by nearly forty percent. However, the simulation flags one critical limitation and risk: because two primary ODN trunks on Deck 4 were fused during the earlier port-side strikes, routing the environmental telemetry through the surviving Deck 3 optical bypass will place the data stream on the exact same multiplexers currently handling Keti’s high-volume probe telemetry. To implement the link safely without causing packet lag or signal cross-talk on the secondary sensor feeds, Cortez will need to cap the environmental polling rate to low-bandwidth bursts and manually lock out the automated fire-suppression overrides in the depressurized zones so a stray sensor ghost doesn't trigger a false purge across the linked intact compartments.

On Baldwin’s power-distribution model, comparing Cortez’s staggered conditioning profile confirms that the reduced environmental demand translates into a clean, usable buffer of auxiliary power. Apart from the threat of another direct hull strike, the EPS junctions on Deck 3 and the secondary sensor array feeds remain completely stable, free of harmonic fluctuations or thermal spikes.

However, Baldwin’s master systems display flags an urgent new priority where her assistance is needed: the rapid-fire discharge of the aft burst-fire torpedo launcher and rear phaser arrays, combined with the heavy port-side disruptor hits taken moments earlier, is causing a localized heat buildup along the aft weapons power couplings and the port-aft shield emitter relays on Deck 4. By routing that newly freed environmental power reserve into the aft thermal dissipation loops and reinforcing the port-aft shield emitter circuits, Baldwin can keep Powl's rear weapons cycling cleanly and prevent the port-aft shield quadrant from buckling as the chase continues.
Reply
Morad’s boots planted wide against the deck plates as Krandall whipped the Zephyr into the sudden, bone-jarring figure-eight, the inertial dampers whining in protest against the violent lateral G-forces. Through the tactical plot on the center console, he watched Powl seize the fleeting split-second openings, unloading two blistering salvos from the aft burst-fire launcher and rear phaser arrays straight into the teeth of the pursuing Hidekis before Krandall snapped them back onto their high-speed escape vector.

"Good shooting, Powl! Way to thread the needle, Tom, keep that throttle buried!" Morad called out, his grip tight on the command chair's armrest as the twin impulse engines roared back to full linear thrust.

Before the vibration of the aft torpedoes had fully cleared the deck, Commander O'Fee's voice cut through the bridge clamor with her proposal to launch the shuttles as close-in disruptors, followed immediately by Amila speaking up from the Science station.

"Captain," she called out, turning from her panel to suggest using Ensign Singer’s drone algorithms to pilot the craft remotely.

For a fraction of a second, the word hung in Morad’s ear. Even in the middle of a firefight, hearing Captain come from Amila’s lips sent a brief, warm jolt through his chest. He didn't let it break his command mask, nor would he ever give her flack for it, though the briefest, knowing glint flickered in his dark eyes as he met her gaze.

"It's clever thinking from both of you," Morad replied, addressing Ava and Amila together with decisive clarity. "And using Singer’s drone subroutines to fly the Aura and the Boreas instead of risking pilots in a suicide run is smart adaptation. But right now, those three Hidekis are glued to our six and pouring disruptor fire directly into our rear arcs. Dropping our aft shields and depressurizing the hangar bays to launch at full impulse would hand them an unshielded target right into our belly, and I can't pull Singer off the warp core coolant repairs while our main drive needs his attention."

He gave Amila and Ava a firm nod, refusing to let a good tactical ace go to waste.

"Hold the shuttles in their bays for now, but don't scrap the play. Amila, have Ava coordinate with Singer when Engineering has a breathing room to pre-stage that remote drone interface with the shuttlebay flight computers. If they manage to box us in before we cross Starbase 214’s perimeter, having two unmanned Type-14s ready to sprint out as close-range decoys could buy us the seconds we need."

Shifting his attention toward Operations and the auxiliary science displays, Morad read the fresh internal diagnostics flashing across his armrest monitor.

"Cortez, your environmental zoning just bought us breathing room, and the simulation on your optical telemetry link is solid; implement it, but cap your polling rate to low-bandwidth bursts so you don't crowd Keti's probe feeds on the Deck Three multiplexers, and manually lock out those fire-suppression overrides first. Baldwin, take that power margin Cortez just freed up and dump it straight into the Deck Four aft weapons cooling loops and our port-aft shield relays. Keep Powl's rear guns cold and that port quadrant standing!"

== Tag Bridge ==
Reply
Sebastian braced himself against the deck's persistent vibration as the Zephyr surged forward under Krandall's aggressive maneuvering. The tactical display continued to track the pursuing Hidekis, but his attention remained fixed on the diagnostic readouts scrolling across his console. Baldwin's latest power-distribution model confirmed that the revised environmental-control profile had created a usable auxiliary reserve. Now Captain Ameen had given him the authorization to put that margin to work.

"Understood, Captain. I'll implement the optical telemetry link using low-bandwidth polling bursts and isolate the automated fire-suppression overrides in the depressurized zones before bringing the connection online."

He opened the environmental-control diagnostic partition and began configuring the surviving Deck Three optical bypass. The fused Deck Four trunks had eliminated the simplest routing options, leaving the bypass as their only viable path between the intact environmental-control zones. Unfortunately, that same network was carrying Keti's probe telemetry, and Sebastian had no intention of compromising the sensor data they needed to survive the engagement.

He reduced the environmental polling frequency, converting the predictive pressure and thermal readings into staggered data bursts rather than a continuous stream. He then manually locked out the fire-suppression overrides in the depressurized sections, checking each affected zone against the compartment status reports before confirming the isolation.

"Lieutenant Ra'an, the environmental telemetry link is being brought online through the Deck Three optical bypass. I'm keeping its data rate below the threshold that could interfere with Keti's probe feeds. You should see the predictive pressure and thermal updates begin appearing shortly."

Sebastian watched the connection establish across the surviving optical network. The first packets arrived without a reported conflict. He cross-checked the new readings against the existing environmental-control data, looking for discrepancies that might indicate signal cross-talk or a sensor ghost rather than an actual change in compartment conditions.

The results were encouraging. By sharing predictive data between the intact control zones, the environmental regulators could begin compensating for pressure and temperature changes before individual compartments drifted outside their preferred operating ranges. The simulation's projected improvement in reaction time was substantial, and the reduced demand on the environmental-control network had already given Operations something the Zephyr desperately needed: a little more power to work with.

Sebastian glanced toward Baldwin's station as the aft weapons and shield diagnostics remained highlighted on the master systems display.

"Ensign Baldwin, the environmental load reduction is holding within the model's projections. The auxiliary margin should be available for the aft weapons cooling loops and port-aft shield relays, as the Captain directed. I'd recommend we keep a close watch on the Deck Four coupling temperatures as that reserve comes online. If another disruptor strike drives the portside feedback higher, we may need to reassess how much of that margin we can safely commit."

He returned his attention to the sensor telemetry, comparing the incoming probe instructions against the surviving secondary feeds. Keti's data stream remained uninterrupted, but the Deck Three bypass was now carrying two mission-critical streams over a network with little room for error. Sebastian kept the environmental polling bursts staggered and watched for any sign of packet delays.

Another violent shudder ran through the deck as the Zephyr continued its high-speed escape. Sebastian caught himself against the edge of his console, then immediately checked the environmental pressure readings. The intact compartments remained stable.

For now, the solution was working. The ship's environmental systems were consuming less power, the telemetry link was delivering useful predictive data, and the freed auxiliary margin could help protect the weapons and shields, keeping the pursuing Hidekis at bay.

Sebastian swallowed against the tension tightening his throat and refocused on his displays. There was no room to celebrate a successful simulation while the ship was still taking fire.

"Captain, the environmental telemetry link is establishing cleanly, and the initial data checks show no interference with Keti's probe feeds. I'll continue monitoring the bypass and environmental stability while the revised load profile runs. If either telemetry stream begins showing delays or inconsistencies, I'll flag it immediately."



== Tag all. ==
Reply
<<< Sickbay <<<

Gath silently returned to the Bridge and stopped to take in the situation, listening to the complex crosstalk to get a feel for what he had missed and what their situation had evolved into. To any who took notice, there was blood on his uniform, but none of it appeared to be his. His boots were a mess and you didn't want to look too closely, it looked like organic matter of some kind, but was fortunately unrecognizable at the moment. It was only in glancing himself over that Gath noticed he had a burn on the back of his left hand that he had no idea where it had come from, but it could wait for now, so he went back to ignoring it.

He came up behind Baldwin and looked at what was in progress on the monitor, "Outstanding! Keep up the good work!"

Moving to his primary station, he heard to talk about the drones and the shuttles. Gath spoke up, "I'll prep the shuttles with programs designed for Tactical. It shouldn't take more than a moment. They will be in idle and ready for tactical launch. When you give the order, they will launch at the same time in crossing patterns that will be verticale from our current axis of travel. The enemy will either follow or be harassed by them and they're less likely to be able to take them both out as the exit. No need to depressurise the bay and we're going to keep the shields up with the shuttles modulated to the shield frequency to be able to pass right through them."

Gath made sure that the drone programs were set for maximum evasive capability and would aggressively try to draw attention and shield power to make the shots to the enemy forward shield that much more effective. They would be ready to launch in less than a minute, most of which was time for the shuttles to be warmed up an at idle.

"I might suggest that you launch them immediately after you fire another one of those handy barrages of torpedos that they seem so fond of. That will give the shuttles an additional margin to work with to successfully exit the ship and get to work."

== Tag to all...finally back on the Bridge... ==
Reply
The three Hidekis were momentarily stymied by the sudden change from evasive dogfighting to a straight-run sprint towards Starbase 214. Caught flat-footed, one of the Hidekis was slower to return to formation than its compatriots, and paid the price as the Zephyr's aft phasers stripped its shields, and its stern was blown clean off by a torpedo. The ship was not destroyed outright, but spiraling out of control and venting atmosphere, it was no longer a threat.

The sudden change in odds lasted exactly ten seconds, however. Commander Ameen's decision to make a break for the Starbase meant they came into the patrol area of the other nine Hidekis in the system. The three closest moved from their patrol routes at high speed, seeking to block the Zephyr's run, while the other two groups of three repositioned to cover the gap in their blockade.

And granting the sensor blip identified as "Federation One" to begin moving from its parking orbit around the Starbase on a least-time trajectory towards the nearest system edge, and the ability to jump to warp without risking life and limb.
Reply
Amila was too focused on the visuals at her station to see the Commander nod at her or to have noticed how long Gath had been absent from the Bridge. She was anxious, but doing her best not to show it. She did notice how the sweat had gathered at the nape of her neck and on her back, soaking the base of her pony tail and her undershirt. It was strange how small details like that stood out in the chaos. The sweat, and the smell of burned electronics from one of the jumps. Morad's voice. The way he encouraged everyone around him. 

There was too much going on out there in the small part of the system, and Amila didn't want to miss a thing. Gath's tactical knowledge was more than welcome as he had a way to weaponize the shuttles without losing shield integrity.

"We need to do something quick," Ra'an warned from her station. "Three more Hidekis just broke from Two-Fourteen and are on a heading to intercept."

Her voice was urgent. She was worried. Baldwin and Cortez had done a spectacular job at keeping life support steady in areas where the crew was currently needed most, but they already had to evacuate significant portions of the ship, and if felt like they were operating on luck and prayers right now.

More quietly she spoke just to Sebastian. "Cortez, nice work, you are doing great," Amila said to the younger officer sitting next to her. "While you keep an eye on that telemetry, help Jukish keep an eye on close range sensors and try to spin up some chaos with those probes again. If those other three ships make it to us, it's about to be five-on-one. We need to consider anything you can think of at this point. No idea is too crazy."

It's about to get bloody, she thought to herself. 

She stole a quick glance to Baldwin and Gath's station and resisted the urge to check on how many escape craft were still accessible. They weren't there yet, but unless more support came through for them, she had a hard time seeing how the Zephyr - or any of them - could pull this off. One of the Hidekis was down, but not destroyed. By showing it mercy, would the Cardassians do the same for them? 

She had put everything into aft sensors when they thought it would be a simple chase, but long-range still managed to pick up the break in formation around the base. "Captain, shifting sensors to give us a more detailed broad range look at what's coming at us." 


==Cortez, All==
Reply
A grim spark of satisfaction flashed across Morad’s face as the tactical plot registered the trailing Hideki spinning out of formation, its stern sheared away by Powl’s pinpoint torpedo follow-up. Better still, the broader sensor sweep confirmed what their gambit had truly bought them: with the blockade patrols shifting to intercept the Zephyr, Federation One had slipped its parking orbit around Starbase 214 and was burning hard on a least-time trajectory toward the system edge and open warp.

Step one accomplished, Morad thought sharply. Now we make sure our intelligence survives, and we keep every pair of Cardassian eyes glued to us while Federation One clears the system...

"Amila, keep that broad-range picture locked in," Morad ordered, his fingers flying across the command console’s tactical uplink controls. "Before those three fresh Hidekis close the bracket on us, we’re getting every byte of our deep-scan telemetry on that Cardassian Dreadnought and these upgraded Hideki escorts off this ship."

He glanced toward Operations and Science, calling up the Zephyr’s phased-array directional transceiver protocols.

"Cardassian broadband jamming is attempting to blanket standard subspace channels, so we’re not broadcasting omnidirectionally," Morad directed crisply. "Compile the complete deep-scan dossier, the Dreadnought's structural profile, weapon signatures, and the Hidekis' upgraded shield and countermeasure telemetry, into a compressed burst package. Route it through our phased-array emitters using a Multi-Function Advanced Datalink protocol: ultra-narrow aperture, frequency-agile tight-beam, low-probability-of-intercept. Punch the first directional burst straight to Starbase 214’s command tower so the Base Commander knows exactly what that Dreadnought is capable of..."

They will have to decide to gamble on the task force arriving in time, or to start evacuating the Starbase... I'm glad I'm not the one making that decision... and where the heck is the starbase's own garrison? Why are they not launching...

His hand shifted across the display, highlighting the covert relay marker sitting just beyond the system's outer boundary.

"Simultaneously, slave a second directional tight-beam link to the communications buoy we dropped outside the system perimeter," Morad continued. "That buoy is already configured to handshake with the Zephyr’s phased-array datalink via narrow-beam line-of-sight. Once the buoy catches our burst, have it relay the entire tactical package at maximum subspace priority straight back to Deep Space Nine. Whatever happens in this sector over the next five minutes, Starfleet Command and DS9 are going to have the playbook on the Cardassians' new hardware."

Turning his head toward the tactical and security consoles, Morad caught sight of Gath back at his post-blood-streaked uniform, scorched hand, and all, already prepping the Aura and the Boreas to slip straight through the shield modulation window.

"Good to have you back on the deck, Gath, and that shield-modulated launch is the exact force multiplier we need," Morad called out, his voice cutting cleanly through the bridge clamor. "Powl, Gath, execute right now! Powl, dump a full aft torpedo barrage straight down the throats of the two Hidekis on our tail to blind their forward scopes. The second that ordnance clears the tube, Gath, punch the Aura and the Boreas out through the modulated shield window on those vertical crossing axes. Have the drones harass their forward shields and force them to break stride!"

Pivoting back toward the helm, Morad studied the intercept vectors of the three fresh Hidekis racing out from Starbase 214’s patrol grid. If the Zephyr stayed on a rigid, dead-straight line, the three interceptors would catch them in a head-on pincer while the two pursuers hammered their stern.

"Krandall, we're not letting those three new contacts T-bone our bow, and we're not giving up our speed advantage," Morad ordered, tracing a high-velocity curving trajectory across the helm repeater that skirted the edge of the interceptors' firing cone while spiraling tighter toward Starbase 214. "Use our superior straight-line acceleration to bend our sprint into a wide, sweeping tangential arc, heading zero-four-zero mark three-five-five! Outpace their lateral cutoff angle and force those three interceptors to over-rotate onto our stern to keep up. I want all five of those Hidekis stacked up in a single trailing tail-chase behind our aft shields and fighting through our shuttles, phasers, torpedoes and probes while we ride that curve straight into Starbase 214’s heavy weapons envelope!"

"Engineering, what's your ETA on warp drive?" Ameen called out.

== Tag Bridge ==
Reply
Gath acknowledged, "Aye, sir!" When Powl fired the next barrage, Gath hit the button and the shuttles launched as programmed. They shot out of the bay with one going up and one going down relative to the ship's axis. They instantly fired a volley each into the two oncoming ships, but then began their intense harassment from their ventral and dorsal flanks, but using their superior maneuverability to try and make themselves very hard targets.

With no actual pilots, the inertial dampeners were not required and left more power for shields weapons and thrusters. They had a full load of micro-torpedoes as well and given that the drones had been adapted from targeting programs to begin with, they were quite at home with the task given to them. Technically, the programs were not considered to have an actual personality, but they certainly seemed to be trying very hard to live up to the name chosen by the parent program. OPS could pick up that the shuttles were communicating with each other, but not what they were actually saying.

Ameen called out, "Engineering, what's your ETA on warp drive?"

To his surprise, his answer came over the comm. It was Singer and she was shouting at someone as the channel opened, but she stopped mid curse: [...Oh...sorry...I'm working on it. We repaired the manifold but manually aligning a coil in the middle of combat isn't exactly in the manual...no-no, just cut it with the torch and toss it out the hole in the nacelle that's scrap now...sorry boss...as I was saying, this thing is daisy chained like a two hundred year old string of holiday lights. Keep your eyes on the helm. If we get it to work, it might not get us far or fast, but I'll try to get as much as I can out of it. I have no idea if she will hold together at all, so when it happens, don't push it...Come on, put your back into it!...My best guess is we'll know in about five more minutes if this will ever work again or if we're walking home...Hey, grab him before he...I gotta go!]

== Tag Bridge Crew...hoping A'kilees is able to add some brilliant technobabble as well... ==

== GM Input request: Given the damage that was done...when they do try to use the warp drive again...if it works...what might our expectations be? Singer is quite the little miracle worker, if unconventional, but A'kilees might be able to also work some magic of his own as he assists in trying to manipulate what is left of the warp field they might be able to generate. ==
Reply
Ameen's response to the new threat was swift, get their information out. Science and Operations were ordered to get everything they had to their communications buoy in the hopes they could get it to Deep Space Nine and also directly to Starbase 214. Two separate, specifically directed advanced datalink protcol to hopefully bypass the Cardassian's attempts to jam their communications.

Another step in preparation that they might not make it out of here. But she didn't have time to dwell on it. Amila quickly set her team in motion to most efficiently execute the Commander's orders.

"Cortez," Amila ordered, "You get that message out to our comms buoy, Jukish, start working now on getting that buoy ready to transmit to Deep Space Nine. Both of you keep working to get that message out to DS9 until it's working. Talk to me or Molina if you have any problems."

"Molina and I will work on getting everything to Two-Fourteen," she stated. "O'Fee, keep tactical's sensor's looking sharp."

Petty Officer Molina heard the directive and understood her role. She began to prepare the narrow aperature comm link, scanning to double check for frequencies most likely to be outside of what the Cardassians were currently jamming. Lieutenant Jukish had called on older Bajoran signals to try to confused the ships when they had first entered the system, but it had become apparent that their ships were highly advanced and their current intelligence on what their sensors were capable of were outdated. The Cardassians had always been good at controlling information in and out - this would have to precise as Commander Ameen had ordered.

"Lieutenant, I have a few options for a subspace frequency that appear to be outside of their broadband jamming work," Molina offered. "Fast is key, I suggest that you hop onto the second signal at the buoy before transmission to DS9, it won't take any time, our advanced comms systems are designed to oscillate frequencies at relay stations for situations like this."

"Perfect, get those frequencies to Cortez and Jukish," Amila stated. She had never stopped typing as she listened, both to the Commander continue orders, and now to Molina tightening up the the frequencies. "Sending you the data package for transmition."

"Done, Sir," Molina responded. "Ready to transmit to Two-One-Four."

Amila took a quick look at the broadrange sensors to see if she could tell how the Aquila and Yeager were fairing. Maybe there was something else useful out there to add to the package before they sent off their transmission.


==Tag Cortez and Keti to get to work==

== Tag GM-CD - Do broad range sensors give Amila any information on the Yeager or Aquila and how they are doing out there, or any information on the Cardassian fleet to add to this attempt to send out a signal? ==



==OOC, NRC Petty Officer Isabel "Izzy" Molina, Operations - she's been here a while chiming in as needed==
Reply
Sebastian acknowledged Amila’s order with a quick nod, already pulling up the compressed telemetry package on his console. The Zephyr’s sensor readings filled the display, detailing the Cardassian Dreadnought’s structural configuration, weapons signatures, and the upgraded shield characteristics of the Hideki escorts. There was enough information here to give Starfleet a fighting chance of understanding what they were up against, provided they could get it through the jamming.

“Understood, Lieutenant. I’m prioritizing the Dreadnought’s structural profile and weapons telemetry, followed by the Hidekis’ shield modulation and countermeasure data. I’ll compress the files without sacrificing the details that might prove critical to developing countermeasures.”

His fingers moved rapidly across the interface, stripping out redundant sensor returns and consolidating the overlapping scans gathered during their engagement. He cross-referenced the results against the Zephyr’s existing sensor records, careful to distinguish direct observations from analytical projections. The last thing they needed was to send Starfleet a confident assessment built on an assumption that turned out to be wrong.

“Jukish, I’m forwarding the completed package to you now. The buoy link needs to be our priority for Deep Space Nine. I’ll keep the transmission directed through the narrow-beam channel and coordinate with Operations if we need to adjust the frequency hopping.”

A fresh warning flashed across his display as the three additional Hidekis accelerated toward the Zephyr. Sebastian glanced at the tactical plot, watching the contacts converge on their projected course. The first Hideki had been disabled, but the remaining ships were adapting quickly. Commander Ameen’s maneuver might force the Cardassians into a less favorable pursuit formation, but there was no guarantee they would remain there.

He opened a secondary window and began monitoring the communications link while keeping the sensor telemetry in view. The Zephyr was taking a considerable risk by attempting to transmit so much intelligence while under fire, but the information could matter long after the outcome of this engagement had been decided.

“Lieutenant, the package is ready for transmission to the buoy. I’m monitoring the carrier signal for signs of interference, and I’ll flag any corrupted segments for retransmission. If the Cardassians are actively tracking our emissions, we may have to keep the bursts short and prioritize the most time-sensitive data first.”

Sebastian swallowed, his eyes flicking briefly toward the tactical display before returning to his console. The damaged Hideki, the incoming reinforcements, and the uncertain state of the Zephyr’s warp drive all weighed on him. He could feel the tension building across the bridge, but he had work to do, and Amila had trusted him with it.

He drew a measured breath and steadied his hands over the controls.

“I'm not seeing a reason to assume the channel is compromised yet,” he added, keeping his voice controlled. “I'll continue monitoring the signal quality and the sensor picture. If we get this intelligence through to Starbase 214 and Deep Space Nine, at least our next move won't be made in the dark.”



== Tag Ra'an and Keti.==

== Tag GM-, is Sebastian successful at getting that message out to the comm buoy?==
Reply
Baldwin could see the power-distribution model, comparing Cortez’s staggered conditioning profile confirms that the reduced environmental demand translates into a clean, usable buffer of auxiliary power. Apart from the threat of another direct hull strike, the EPS junctions on Deck 3 and the secondary sensor array feeds remain completely stable, free of harmonic fluctuations or thermal spikes.

Suddenly several flags appeared om Baldwin’s master systems display an urgent new priority where her assistance is needed: the rapid-fire discharge of the aft burst-fire torpedo launcher and rear phaser arrays, combined with the heavy port-side disruptor hits taken moments earlier, is causing a localized heat buildup along the aft weapons power couplings and the port-aft shield emitter relays on Deck 4.

"Baldwin, take that power margin Cortez just freed up and dump it straight into the Deck Four aft weapons cooling loops and our port-aft shield relays. Keep Powl's rear guns cold and that port quadrant standing!" ordered the Commander.

"Ay, Commander," she said." Ens Baldwin had never been on a bridge in a battle before. She had feelings rising in her that she had little experience of handling or blocking,. They where strong feelings.

Is this what fear feels like? Living on Earth all of my life has made me ill equipped because of a lack of Vulcanization! Especialy in a roles like engineering I'm not particularly trained in.

Ens Cortez spoke and withdrew her from her self-indulgence "Ensign Baldwin the environmental load reduction is holding within the model's projections. The auxiliary margin should be available for the aft weapons cooling loops and port-aft shield relays, as the Captain directed. I'd recommend we keep a close watch on the Deck Four coupling temperatures as that reserve comes online. If another disruptor strike drives the portside feedback higher, we may need to reassess how much of that margin we can safely commit."

Ens Baldwin acknowledged Ens Cortez.

Another surprise put her back on the Vulcan track as Lt Gath came up behind her and looked at what was in progress on the monitor, "Outstanding! Keep up the good work!"

Soon after Commander Ameen called out "Good to have you back on the deck, Gath, and that shield-modulated launch is the exact force multiplier we need," his voice cutting cleanly through the bridge clamor. "Powl, Gath, execute right now! Powl, dump a full aft torpedo barrage straight down the throats of the two Hidekis on our tail to blind their forward scopes. The second that ordnance clears the tube, Gath, punch the Aura and the Boreas out through the modulated shield window on those vertical crossing axes. Have the drones harass their forward shields and force them to break stride!"

Ens Baldwin realized she had to work quickly and accurately other wise there may be no launch of weapons and worst still the aft shield may go down. She had to correct this before the Shuttles launched.

Ava rerouted the newly freed environmental power reserve into the aft thermal dissipation loops and reinforcing the port-aft shield emitter circuits, so that the rear weapons cycling cleanly and prevent the port-aft shield quadrant from buckling as the chase continued. She finish the transfer of power exactly thirty seconds before the weapons fired and the Shuttles launched.

If there was a lesson to be leant from these intense moments on the bridge it was not to wallow in self-indulgence, it was strictly logic and do your job from now on!
Reply
Sebastian found himself struggling to process everything that had happened on the Bridge. There had been so little time to think, so little room for uncertainty, and yet every decision seemed to carry consequences that extended far beyond the immediate problem in front of him. As a Science Officer, he was accustomed to approaching difficult situations through observation, analysis, and careful consideration of the available evidence. The battle had forced him to accept that sometimes there simply wasn't enough time to gather all the information he wanted before acting. He respected the way Captain Ameen and the senior officers coordinated their efforts, and he was proud that Science had contributed to keeping the Zephyr in the fight. At the same time, he couldn't quite shake the feeling that he was still learning how to function when the stakes were so high. Watching the Bridge crew work under pressure was both reassuring and humbling. He wanted to be someone they could depend on, not merely another officer waiting for instructions.

His feelings toward the Cardassians were considerably more complicated than simple dislike. Sebastian understood that the Cardassian Union had its own history, culture, and political motivations, and his scientific training made him reluctant to judge an entire people by the actions of their military or government. Still, understanding an opponent didn't mean he had to approve of what they were doing. The Cardassian forces had demonstrated just how dangerous they could be, employing disciplined formations, redundant fire-control systems, and coordinated attacks that left little room for mistakes. Their willingness to pursue the Federation ships and threaten Starbase 214 made it difficult to regard them as anything other than a very real danger. He found himself wondering what had brought matters to this point, whether there was some diplomatic or strategic context he didn't know, and whether the crews aboard those Cardassian vessels understood the consequences of the conflict as clearly as he did. But whatever their motivations, he couldn't afford to let curiosity become a distraction. They were the enemy in this engagement, and the people aboard the Zephyr had to come first.

The battle itself left Sebastian with an uneasy mixture of fear, determination, and professional fascination. He could appreciate the tactical complexity of what was happening without losing sight of the fact that people were dying. The Zephyr was no longer simply a vessel conducting a mission; she was a ship fighting to survive against a determined enemy, and every damaged system or lost vessel was a reminder of how quickly circumstances could turn catastrophic. The destruction of the Hideki's stern during the Zephyr's desperate sprint toward Starbase 214 had driven that reality home. Even a successful strike didn't necessarily mean an enemy ship was out of the fight, and a tactical victory could still leave wounded personnel, damaged equipment, and unanswered questions in its wake. Sebastian wanted to understand the battle well enough to anticipate what the Cardassians might do next, to identify patterns in their movements, and to find some scientific advantage that might help the Zephyr and her allies survive. He knew that his contribution might not be as dramatic as firing a phaser or commanding a maneuver, but good information could make the difference between a calculated risk and a disastrous guess.

Beneath all of that, however, was the uncomfortable realization that he was discovering things about himself that he hadn't expected. He was frightened. He would have preferred not to admit it, even privately, but pretending otherwise wouldn't make the danger disappear. His recent struggle with claustrophobia during the spacewalk had already shaken his confidence, and now he was being tested in a different way. There was no helmet to clear his vision, no horizon to focus on, and no mental exercise that could make the tactical display in front of him feel less immediate. He had to trust his training, listen to the people around him, and do the work that was expected of him. He didn't suddenly feel fearless, nor was he entirely convinced that he was ready for every responsibility Starfleet might eventually place on his shoulders. But he was beginning to understand that courage didn't require him to feel no fear at all. It required him to keep thinking, keep contributing, and keep faith with his crewmates even when he wasn't certain how the battle would end. For now, that would have to be enough.
Reply
There was a communication to Gath [Sickbay to Lieutenant Gath, Condition Green.] Her voice had a lot of optimism, he would also know she just did it to take something weighing heavily on his mind.
Reply
== GM-Zephyr ==

Down in Main Engineering, the sheer audacity of Singer’s field repairs begins to bear fruit, but physics and Starfleet engineering tolerances still demand their toll. By physically severing the fused secondary coils and venting the slagged components into the void, Singer and her damage control teams successfully clear the short-circuits along the starboard nacelle feeder lines. However, the resulting drive assembly is missing over a third of its magnetic containment runners and relies on a precarious network of emergency EPS shunts.

When the five-minute clock runs down, the patched drive will engage, but sustainable high-warp cruising speeds are completely out of the question. At best, the compromised assembly will deliver a fragile, brute-force burst capped strictly between Warp 3.0 and Warp 4.2. Because the starboard nacelle is severely compromised, the resulting warp field will be asymmetrical. Without continuous manual compensation from the Bridge engineering console, the field will suffer from severe spatial distortion and violent harmonic shear, threatening to drop them back into sub-light or rip the remaining nacelle strut clean off the spaceframe.

Furthermore, barring any further repairs or adjustments, the bypassed coolant loops as they are can only absorb so much friction. Once engaged, the jury-rigged assembly will operate on a hard thermal countdown, giving Command a window of roughly three to four days of sustained warp flight before the remaining coils superheat and trigger an automatic emergency core shutdown to prevent a catastrophic breach. In short, Singer’s miracle will give the Zephyr an exit ticket and perhaps even a short trip to the nearest repair facility, but it will be a rough, white-knuckle sprint that requires A'kilees and the bridge team to manually nurse the bubble every step of the way.

Along the secondary ODN lines, Cortez’s phased-array directional link makes clean, positive handshake contact with the outer perimeter communications buoy. The compressed deep-scan dossier transfers via the tight-beam burst without packet loss or signal degradation, and telemetry confirms the buoy has begun oscillating its subspace relay to squirt the package toward Deep Space Nine, however there was no confirmation if DS9 has received the signal or not. 

Across Deck 3 and the primary living compartments, the environmental load shedding is holding steady. However, the sudden force of launching both Type-14 shuttles through the shield-modulated bay doors, combined with Krandall's hard banking arc, causes a brief pressure oscillation across the Deck 4 life-support conduits. Automated regulators immediately compensate without tripping the manual fire-suppression locks, keeping bridge and sickbay air levels well within green thresholds while the ship braces for the incoming five-ship tail chase.
Reply
The deck shivered violently under Morad’s boots as Krandall snapped the Zephyr into that wide, sweeping tangential arc, the inertial dampeners screaming in protest against the lateral sheer. On the main viewer, the stars swung in a disorienting smear, the towering superstructure of Starbase 214 rotating into the upper quadrant while the three fresh Hideki interceptors bore down across their forward vector.

Behind him, Gath’s automated sequences fired with surgical precision. The twin Type-14 shuttles, Aura and Boreas, slipped through the modulated shield window in vertical crossing patterns right behind Powl’s torpedo barrage, banking aggressively to draw fire and slice into the pursuers' flanks.

Now we see if the Cardassians take the bait or split the difference, Morad thought, dark eyes locked on the tactical plot as the computer tracked whether the interceptors would over-rotate into a chase or cut across their bow. Outnumbered, outgunned, and she is holding together on sheer stubbornness...

The legendary Captain Picard once said that things are only impossible until they’re not. Morad had carried those words with him from the Academy halls to the center chair, and right now, this battered old destroyer was going to prove him right.

"Keep that curve tight, Krandall!" Morad commanded over the roar of the impulse manifolds. "Ride the edge of their firing arcs. Don't give them a stationary target!"

Stepping up toward the center well, he glanced over toward Amila at Science, his expression focused and sharp.

"Amila, keep passive broad-range sweeps scanning Starbase 214 and the surrounding battlespace. The base command tower should be receiving our direct tight-beam burst right about now. If they acknowledge, I want their heavy phaser arrays primed the second we cross their outer perimeter. And keep an eye out for any sign of the Yeager or the Aquila, we need to know if either of them is still in the fight."

Morad braced himself against the railing as the deck shuddered from another near-miss disruptor bloom off their port quarter, keeping his eyes glued to the forward viewer where the battle lines were about to collide.

"Powl, keep aft and forward tubes hot," Morad ordered, before reaching up to tap his comm-badge in direct reply to Singer's frantic scramble. "Copy that, Singer. Five minutes, holiday lights and all. Do what you have to do down there, toss whatever scrap you need to into the void, but give us that sprint. Ameen out."

== Tag Bridge ==
Reply
The two shuttles proved marginally effective upon deployment; the first was nailed by a stray torpedo almost immediately after launching, a direct result of being deployed into the line of fire. The second, less constrained by things such as pilot G-tolerances thanks to its guidance programming, ducked and weaved and began to harass the two trailing Hidekis. That harassing fire proved distracting enough that Powl's follow-up torpedo volley nailed one, leaving nothing but an expanding cloud of gas. The shuttle was caught in the secondary detonation caused by the Hideki's warp core, but it had done its job and the odds were now even.

Scans for the Aquila and Yeager revealed that the two ships were heavily engaged:

The Aquila had just lost shields to a matter/antimatter detonation with the yield of a medium-sized antimatter reactor (likely the Aquila's Secondary Core), while the two Keldons she had faced off against were both holding position out of weapons range to lick their own wounds.

Meanwhile. the Yeager was in trouble. Sensors showed she was off-course, trailing atmosphere and debris, with structural integrity fluctuating around critical levels. The crippled Scout Cruiser was arcing around onto a collision course with the lead Keldon, and hull plating covering escape pods began to be jettisoned in preparation of the crew abandoning ship.

As the timer ticked down, the Yeager's final transmission to the group was received, a text-only command for the Aquila and Zephyr to withdraw to Starbase 214 and provide support for any craft evacuating the area.
Reply
== NPC Ens Raven Singer == 

A'kilees comm came to life with Raven's voice: [Raven to A'kilees...I need to you get to Main Engineering to manage things. We're going to need to test this mess I'm making to see if we will ever have warp capability again or not. You can still monitor the ship from down there as well, but you might get a little dirtier than staying in that comfy spot on the Bridge. If you're not already in a Damage Control suit, you might want to get into one. They aren't as comfy as your bathrobe and slippers, but you did fine the last time I saw you in one, so I think you can handle it. Let me know when you're in place.]

== Tag A'kilees ==
Reply
Sebastian kept his attention fixed on the science console as the latest telemetry reports populated his display. The successful transmission to the communications buoy was a small victory, but an important one. The deep-scan dossier had been delivered without packet loss, and the buoy had begun relaying the compressed data toward Deep Space Nine. Unfortunately, there was no confirmation that the station had actually received it. For now, all he could do was monitor the relay and hope the information reached someone who could put it to use.

The engineering report was considerably less encouraging. Singer's improvised repairs had managed to clear the short circuits along the starboard nacelle feeder lines, but the resulting configuration was anything but stable. A maximum warp speed somewhere between Warp 3 and Warp 4.2, with only three to four days of operation before the remaining coils overheated, was hardly the sort of performance anyone wanted from a starship fleeing a battle. The asymmetrical warp field presented another problem entirely. A'kilees and the Bridge engineering team would have to continuously compensate for the distortion and harmonic shear. One mistake could cost them their remaining nacelle strut.

Sebastian glanced briefly toward the engineering status indicators. He was grateful Singer had managed to give them an opportunity to escape, but he couldn't help wondering how much more punishment the Zephyr could take before even the most ingenious repairs stopped being enough.

Then the latest sensor reports appeared.

His expression tightened as he examined the readings from the two Federation vessels. The Aquila's shield grid had apparently collapsed following what sensors indicated was a matter-antimatter detonation comparable to the yield of a medium-sized antimatter reactor. If the readings were accurate, the Aquila had likely lost her secondary core. The two Keldons appeared to be holding their distance, presumably assessing their own damage, but that hardly meant the danger had passed.

The Yeager's situation was worse. Structural integrity was fluctuating around critical levels, the ship was trailing atmosphere and debris, and her trajectory placed her on a collision course with the lead Keldon. The jettisoning of hull plating around the escape pods was particularly troubling. It suggested the Yeager's crew was preparing to abandon ship.

Sebastian swallowed, studying the tactical and sensor overlays. He knew several people aboard those vessels, and the thought of either ship being lost was difficult to push aside. Still, he had a job to do, and the information coming across his console might make a difference.

The Yeager's final transmission appeared on his display, ordering the Aquila and Zephyr to withdraw toward Starbase 214 and assist any vessels evacuating the area.

He looked toward the forward stations before turning his attention back to the science console.

"Captain, I'm still monitoring the communications buoy. The relay has begun transmitting our dossier toward Deep Space Nine, but I haven't received confirmation of delivery from the station. I'll continue monitoring the subspace carrier signal for any acknowledgment."

He paused, bringing the Yeager's sensor readings onto a separate display.

"Captain, the Yeager's structural integrity readings are deteriorating rapidly. I'm detecting continued atmospheric loss and significant debris shedding. Her projected trajectory puts her on a collision course with the lead Keldon. The escape pod compartment plating is also being jettisoned, which suggests they're preparing to abandon ship."

Sebastian shifted his attention to the Aquila's readings.

"The Aquila's shield failure coincides with a massive matter-antimatter discharge. The energy signature is consistent with a secondary antimatter core detonation. The two Keldons appear to be maintaining their distance, but I wouldn't assume they're out of the fight."

He returned his attention to the sensor display, expanding the available scanning parameters around the Zephyr's projected route.

"I'll keep passive sensors focused on the surrounding battlespace and monitor the escape pod transponders as we approach the station. If the Yeager's crew begins abandoning ship, we should be able to identify their positions and relay them to the evacuation coordinators."

There was little Sebastian could do from the science station to repair the damage or change the course of the battle. But he could make certain that the Bridge had the best information available. Right now, that might be just as important as another volley of torpedoes.



== Tag Captain Ameen, tag all.==
Reply
The fighting to this point was fierce. The Zephyr’s evasive movements with Krandall at the helm mixed with the occasional hit from enemy fire jolted the vessel around. A’kilees had kept himself entirely focused at the secondary engineering console, keeping power flowing between the impulse manifolds and other critical weapon and defensive systems. He had been keeping tabs on various other life support systems in the background and so far everything was still operational except in the damaged restricted areas of the vessel. The ship shook suddenly about taking another impact from a disruptor volley from the surrounding Hidekis. The Cardassians weren’t letting up on their attack on the Zephyr or on the other Federation ships in the vicinity.

With the message from Raven coming over the comms, he could only imagine how the situation was down in the lower decks. Although it was important to remain at his station, the saurian knew that his engineering skills would be required elsewhere helping to repair the warp drive. Kier 77 was still occupying the primary engineering console managing multiple systems and there would be another engineering officer on standby to take over the secondary console while he left to assist in repairs.

The saurian pressed on his combadge.

[Understood Raven, I’ll retrieve a damage suit and get down to Engineering immediately. I’ll contact you as soon as I’m positioned.]

A’kilees looked towards Morad Ameen who was busily giving commands at the railing.

“Commander, I’m returning to Engineering to assist Ensign Raven with repairing the warp drive. We’re going to need it operational, especially if we plan to get out of here. We’ll keep you informed of our status.”

The saurian stood up from his station and waved at a nearby ensign to replace him. She hurried over and sat down in the chair immediately regulating the EPS flows balancing them between critical systems. A’kilees made his way over towards the turbolift doors which opened with a hiss.

“Engineering” A’kiless requested and the doors quickly closed behind him.

>>> Engineering >>>

== Tag Raven Singer, Morad Ameen et all ==

== GM Input: What is the current situation in Main Engineering? Please post input in Engineering. Thank you! ==
Reply
The deck plates groaned beneath Morad’s boots as another concussive tremor rippled through the hull, the harsh strobe of red alert reflecting off the sweat sheen across his brow. On the tactical display, the grim realities of the broader battlespace laid bare the cost of every second they had bought.

"Go, A'kilees," Morad said, catching the Saurian's eye with a sharp, resolute nod as the officer stepped toward the lift. "You and Singer are our ticket home. Keep that bypass from blowing out our bulkheads. Godspeed."

Turning back toward the center well, Morad stepped down toward the science and operations station, his face hardening as he took in the telemetry Cortez had pulled up. The telemetry for the Aquila; her secondary core gone, shields down, two damaged Keldons hovering just outside her perimeter. And then the Yeager... crippled, hemorrhaging atmosphere, and deliberately curving into a terminal ramming vector with the lead Cardassian warship while blowing her escape pod covers.

Damn it Jen... you had to go and play the hero now... Just do me a favor and don't go down with the ship...

The scout cruiser's final text order flickered on his armrest repeater: Withdraw to Starbase 214. Provide support for any craft evacuating the area.

A tight knot formed in Morad's chest, but his voice remained absolute steel when he spoke.

"Cortez, lock onto those Yeager pod transponders," Morad ordered, his jaw set tight. "Tag every single beacon signature and stream the telemetry straight to Starbase 214 and the evacuation shuttle routes. We honor the Yeager's sacrifice by making damn sure her people make it to the base."

He stepped up beside the helm, his eyes locked onto the towering, illuminated spire of Starbase 214 looming ahead on the main viewer, while the three fresh Hideki escorts were steadily closing in to join the pursuit.

"Krandall, you heard Captain Braggins' final transmission. Hold this vector, full impulse!" Morad barked, leaning over the console. "Don't let them box us in. We ride this arc straight across Starbase 214's outer defense threshold and give those pods the escort they need. Powl, keep aft tubes hot and stagger our rear phaser sweeps. If any of those Hidekis try to break away from us to hunt pods, put a torpedo right through their flight deck!"

"Ra'an, what's the status of Federation One? Are they clear?" Ameen asked.

He keyed the shipwide channel, his voice cutting through the klaxons and engine whine across every deck.

"All hands, this is the Bridge. Prepare for extreme maneuvers and final defensive transition. We're almost to the threshold. Hold fast."

== Tag Bridge ==
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)