Star Trek: Aftermath (Cardassian phase)

Session 7: Off to Atbar
Wow, we skipped out just in time...

Except from Captain’s Speech To Crew: “Brace yourselves, people, this ship is in for many tussles.”

Crewman 1 to Crewman 2: <whispers> “Does he mean like the sprouts?”

Crewman 2: <whispers> “Those are brussels .”

Crewman 1: <whispers> “Like the mushrooms?”

Crewman 3: <whispers> “Those are truffles.”


From part 2 of the meeting with Cpt Harkness (small retcon? Maaaaaybe. Mostly I just didn’t want to read to you anymore…):
“Be seated.

“Let’s take a look at our assignment then.” She pops up the TF21 area map. “Our Task Force is responsible for peacekeeping in this area. As you can see, this is a primary thoroughfare for pirates and black marketers since the Romulan and Klingon territory grab. A bonus for our operations, since the failed True Way grab, operation Candid, we have a number of sensor buys that were deployed and will remain operational for the next 9-12 months. They are passive, virtually undetectable, and send information back to us on a tight beam to a collection point on Atbar. Stealthed as they are, even the ships that deployed them would have a hard time finding them again, and those have all returned to Romulan space. That means we get to keep them and use them until they quit functioning. DO NOT TAMPER with them. Part of our agreement for their use and deployment is that we do not attempt to learn their little secrets. Expect that we will be watched closely.

“We are based out of Atbar. Our patrol range covers Keid to Sheva, Sonebr to Sheva, Atbar to Sonebr, and Sheva to Atbar, and we are the primary response force for anything inside that area and along this gap.” She points to the space between the Klingons and Romulans at the top of the map. “We may call on the Task Forces in close proximity to us as needed, and for any large forces from the Ready Response Fleet based in Avenal, though they aren’t that close to us, tactically speaking. They’re roughly 3 LY from Atbar, roughly 13 hours at maximum warp to get to Atbar, then however long to get to us. Our fastest help is simply whoever happens to be hanging around Atbar at the time.

“We are Interlocking support with Commodore Stadi’s Peacekeeping Group 4, and are expected to provide support to them upon request, and we can request support from them as well. Additionally, the largest concentration of Cardassian firepower is also in Avenal and can assist for the really big ops or if everything collapses into total anarchy.

“All right. My strategy is to keep the contra forces off balance by being unpredictable. You will each plot your own patrol path, tight beam your situation to the Fed Command Center on Atbar at 3 random times per day and receive updates the same way, and avoid direct communications with other Federation ships unless absolutely necessary. Communicate with other ships when needed with short range communications or tight beam. Run silent, keep your ears open, pounce when you sense trouble before it pounces on you.

“When available, your crew will take it’s shore leave at Atbar. Atbar was the last outpost of the Cardassian resistance just prior to the fall of the Dominion forces, and much of the population welcomes Federation help there, but the True Way has operatives in the area as well. Federation personnel and ships may be targets and are warned to take precautions when on planet and in orbit.

“We are expecting stepped up True Way action in our area, bold pirate activities, expansion of black market and smuggling activities, a more aggressive Klingon posture (as if that’s possible), and we have no clear indication of Romulan objectives.

“This is your orders package. Study it. Three days from now we go to work.”


Orders: Proceed to Atbar and enter the TF21 ops area. Patrol Sheva, Keid, Sonebr, and Atbar, respecting the boundaries of both the Klingons and Romulans, and gather detailed sensor data of all threat oriented scans at Atbar. Do not launch probes into Klingon or Romulan territory nor enter their space without their explicit invitation, even if you are pursuing criminals, true way, or aggressive Klingon or Romulan forces. Atbar is a heavily defended world and your safe harbor if you need to escape and/or evade, and it is also your home base and the command point of TF21, TF23, TF24, and TF25, and should you call for help it will be arriving from this location.

In addition to your main patrol route, which should be varied routinely, visit the Huaco, Mersoh, Sira, and Taggrut systems periodically. Be unpredictable. Use the sensor bouy array, maintain and monitor it, and add to it where you can. We have reason to believe that the core of illegal operations as well as the main supply lines of the True Way, Romulans, and Klingons run through this area of space.


  1. Act as a buffer between the Cardassians, Klingons, Romulans, and any other aggressive forces in the area to maintain peace and stability until relieved or reassigned.
  2. Observe the prime directive where it applies.
  3. Protect the citizens, property, ships, trade, and sovereign territory of the Federation in the area of operation above all following priorities.
  4. Assist the Cardassians in their efforts to maintain their government and protect their citizens, property, ships, trade, and sovereign territory.
  5. Protect civilians and civilian ships from armed threat and piracy.
  6. Use diplomacy to resolve situations unless given no other choice, and then use the least amount of force possible to accomplish the above directives.
  7. Mission specific directives will be cut on an as needed basis through the office of the Fleet Adjutant.
  8. Observe the following Rules Of Engagement (ROE):
    A. Federation ships shall not fire upon another ship unless first fired upon.
    B. Rule A is superseded in the event that engaging another vessel is necessary to accomplish the directives above, and then Federation ships shall use the least force necessary to accomplish the directive(s).
    C. When encountering superior numbers Federation ships will avoid contact, break contact, and/or withdraw from conflict if there are no considerations towards the directives above.
    D. When engaged in combat in the accomplishment of the directives above, Starfleet vessels shall do their utmost to ensure these directives are met, and shall not withdraw from conflict unless their continued presence can make no difference in the outcome. Captains shall exercise prudence to protect their ship and crews balanced against the accomplishment of directives.
    E. Report all intelligence through the chain of command, NOT Starfleet Intelligence – we report to Star Fleet Intelligence, not you.

Fleet Admiral Hans Koderman, Commanding
Cardassian Theater Command




Task Force 21, of which the USS Endurance is a part, is assigned their patrol operations area: Task Force 21 Operations Area Map, Peacekeeping Group 5 Operations Area Map
Ops Area Key:
PLANETARY CODE: B=Barren, T=Terrestrial, G=Gas Giant, P=Planetoid, I=Ice Core
Atbar – System consists of 2 barren planets, 2 terrestrial planets, 4 gas giants, 2 asteroid belts, arranged from star: B, T(M), T, B, G, G, G, G. Federation maintains a marine battalion garrisoned here.
Atbar II – Last outpost of Cardassian resistance forces just prior to the fall of Dominion forces. Much of the population welcomes Federation help there, but the True Way is known to have operatives in the area as well, size and disposition unknown.
• Class – M
• Satellites – 0
• Planetary Gravity – .85
• Planetary Size – 94.4% of Sol
• Land Area – 68%
• Planetary Rotation – 28 hours
• Atmospheric Density – Terrestrial
• General Climate – Warm Temperate
• Mineral Content – Trace amount industrial crystals, otherwise mineral/metal poor.
• Population – 1,230,000
Eisae – Populated system outside of, but near, operations area. System consists of 4 terrestrial planets, 3 gas giants, 0 asteroid belts, 2 ice cores, arranged from star: T, T, T(M), T(M), G, G, I, G, I
Eisae III is an unsettled desert planet, no surface water, rudimentary plant life only, no industrial or military value.
Eisae IV is an industrial colony of roughly 200,000 inhabitants, mostly indentured factory workers.
Huaco – Has no M class planets. Unremarkable. Smattering of industrial ores and crystals, none in enough concentration to be industrially viable. Young system, full of rogue asteroids and planetoids. 2 terrestrial planets, 16 terrestrial planetoids in eccentric orbits, 7 ice cores in eccentric orbits, 12 gas giants arranged from star: G, T, P, P, P, P, G, P, T, P, I, I, G, P, I, G, P, P, G, P, I, P, P, I, G, P, P, G, P, P, G, I, G, G, G, I, G
Keid – A younger system, there are still several eccentric planetoids and ice cores in the outer solar system with a single, primitive class M water world, 2 asteroid belts, and only 1 enormous gas giant arranged from the star: T, T, T(M), P, A, P, B, G, B, P, A, P, I, I, I, I, I, I, I
Keid II – No atmosphere, essentially a huge round rock in space, a productive deposit of dilithium has been mined here for over 150 years by the Cardassians, and other deposits are suspected, but so far haven’t been found except in the deepest oceanic locations making them expensive and difficult to exploit. Having mostly orbital and ship based defenses, the Dominion swept through and eliminated any resistance, then put the local population of miners back to work. It was the first system taken by any victorious government following the Dominion War, and the Klingons met little resistance aside from some ground fighting with dying Jem’Hadar.
Keid III
• Class – M
• Satellites – 3
• Planetary Gravity – 1.88
• Planetary Size – 1.52% of Sol
• Land Area – 0.02%
• Planetary Rotation – 24 hours
• Atmospheric Density – Terrestrial
• General Climate – Warm Temperate, edge of Tropical
• Mineral Content – Nothing easily attainable
• Population – 0
Mersoh – Young system, filled with debris and still in planetary formation. A multitude of highly eccentric planetoids, ice cores, and 7 gas giants roam this system, and what is not in the current path of one of them is part of the solar system wide asteroid field. Arrangement from the star is difficult as no planets have currently settled into stable orbits. The system is not fully charted and large body collisions happen 2-3 times a decade, and the system sensor probe has had to be replaced 3 times in the last 3 years due to collision.
Sira – System consists of 5 terrestrial planets, 6 gas giants and 4 ice cores with no asteroid belts arranged from the star: T, T, T, T(M), T, G, G, G, G, I, I, G, I, I.
Sira IV is a mining colony. It mines are the property of Delta Core Industries, a Cardassian firm funded to restart operations after the Dominion war by Ferengi interests, though what share, if any these Ferengi actually own is not known. Bendras Darel is the General Manager of Delta Core Industries on Sira, Lukin Prinna is the planetary governor, one of only 3 female Cardassian governors. The planet has standard ores, crystals, and gemstones, and smelts the ores into usable metals for shipping off world. No land based indigenous life has been found, and the oceans have basic microscopic ecosystems. Due to the high gravity outside installations and the harsh desert, the only other facility is a small abandoned prison, which was closed due to excessive operational and maintenance costs.
• Class – M
• Satellites – 2
• Planetary Gravity – 1.46
• Planetary Size – 58.5% of Sol
• Land Area – 36%
• Planetary Rotation – 18 hours
• Atmospheric Density – Thin, barely breathable
• General Climate – Desert
• Mineral Content – Normal metals, trace amount radioactives, gem stones, industrial crystals, no rare minerals.
• Population – 78,900
Sheva – 3 terrestrial planets, 4 asteroid belts 2 gas giants, 3 ice cores, arranged from the star: T, B, T(M), T, B, G, G, I, I, I.
Sheva II was the location of a Jem’Hadar breeding facility during the Dominion War. Little industrial or strategic value was placed on the system and it was an agricultural producer prior to the arrival of the Dominion. The population was killed by Jem’Hadar who used them for targets to train new Jem’Hadar troops. The system was only lightly resettled when the Romulans annexed the planet into their empire. Little is known about the condition of the peoples of the planet or why the Romulans found the system to be desirable. M2
• Class – M
• Satellites – 0
• Planetary Gravity – .85
• Planetary Size – 94.4% of Sol
• Land Area – 68%
• Planetary Rotation – 28 hours
• Atmospheric Density – Terrestrial
• General Climate – Warm Temperate
• Mineral Content – Trace amount industrial crystals, otherwise mineral/metal poor.
• Population – 1,230,000
Sonebr – 5 terrestrials, 1 belt, 3 gas giants, 5 ice cores arranged from the star T, T, T(M), B, T(M), G, I, I, G, I, G, I.
Sonebr III – The small size, tropical temperatures, high ocean percentage, and heavy atmosphere make for remarkably strong, constant hurricanes raging over the surface of the planet at all times. Think planet of perfect storms. The oceans teem with life, where it stays, shunning the pounding on land.
• Class – M
• Satellites – 0
• Planetary Gravity – 1.47
• Planetary Size – 67.1% of Sol
• Land Area – 34%
• Planetary Rotation – 23 hours
• Atmospheric Density – Thick, 75 atmospheres at sea level
• General Climate – Tropical
• Mineral Content – No industrial value.
• Population – 0
Sonebr IV – Mining colony and minor dilithium supplier. Common ores are abundant and easily mined, contributing to the planets gravity despite its size. While there is little natural life above a microbial level on the planet, there are substantial dilithium deposits here as well. Due to the presence of the valuable crystal, the Cardassians kept a large garrison of troops on Sonebr IV. The Klingons laid siege to the planet and essentially starved the garrison out during their take-over following the Dominion war. Of almost 50,000 Cardassian troops stationed on the planet, less than 5,000 remain alive, and those that do are used in the mines as labor.
• Class – M
• Satellites – 1
• Planetary Gravity – 1.08
• Planetary Size – 64.8% of Sol
• Land Area – 74%
• Planetary Rotation – 20 hours
• Atmospheric Density – Thin, breathing gear required
• General Climate – Arctic
• Mineral Content – Common metals, abundant dilithium.
• Population – 230,000 civilian, 64,000 troops.
Taggrut – Orbiting a red supergiant are 8 Terrestrial planets, 3 belts, 8 gas giants, 8 ice cores occupy this solar system which is one of the largest (in volume) in Cardassian space at 2.3 times the volume of the Sol solar system. Arranged from the star: T, T, B, T, T, T, B, T(M), G, T, G, B, G, I, I, I, I, I, I, I, I.
Taggrut VIII – Mining colony, abandoned during the Dominion war and recently resettled. Solid ore veins and newly found gemstone deposits have made this mining operation commercially viable. Dilithium producer, one of 3 remaining in the hands of the Cardassians, targeted by the Klingons.
• Class – M
• Satellites – 3
• Planetary Gravity – 1.51
• Planetary Size – 48.5% of Sol
• Land Area – 93.4%
• Planetary Rotation – 29 hours
• Atmospheric Density – Terrestrial
• General Climate – Cool Temperate, nearly arctic
• Mineral Content – Mine-able normal metals and gemstones, sporadic dilithium deposits, extreme density of heavy metals (low grade) making deep sensor scans difficult and unreliable and transporting underground impossible. Dilithium is extracted on an opportunity basis as deposits are uncovered in the normal course of metals mining.
• Population – 44,000, 60,000 troops.
Klingons to the left, Romulans to the (top) right, and Cardassians all around. What to do, what to do?

Starfleet Intelligence Supplemental

Update: Cardassian Theater, Peacekeeping Group Detail

Cpt Harkness wants TF21 to fly together on the trip there, leaving when all repairs and upgrades are complete. Warp 6 are fine, W7 is sustainable but damaging, W8 is very damaging and possibly catastrophic, W9+ for that distance death for your ships. She sets Warp 7 for your fleet. An engineering roll for week one and one a day after that to keep the engines running well.

Cardassia > Adarak 26 LY, W6 24.19 days, W7 14.47 days, W8 9.27 days, W9 6.26 days, W9.95 4.48 Days

Adarak > Atbar 18 LY, W6 16.75 days, W7 10.2 days, W8 6.42 days, W9 4.34 days, W9.95 3.10 Days

Even without the warp speed restrictions space is big and something the size of the Cardassian territory will take some time to get across.

What happened:

During refit and repair Dr. “Wash” Shaw, Chief Science Officer (CSO) or the USS Endurance and a terribly big deal decided that this would be a great time to do some team building and meet and greet between the science departments of TF21. She proposed a scientific symposium between the science departments of the three ships, which was enthusiastically endorsed by the CSO of the McKinley just before he promptly left on shore leave (what with being Bajoran, and therefore no fun at parties, and home just being right there through the STWC and all), though the science department of the Claymore adopted their usual, grumpy, “Let them eat static” policy. This attitude rapidly changed (slightly) when Captain Harkness, THE FREAKIN’ TASK FORCE COMMANDER HERSELF wholeheartedly endorsed and joined the symposium and strongly (ordered) encouraged the Claymore’s science staff to get with the program. Many interesting and brilliant presentations were given by the science staffs of both the Endurance and McKinley, along with, “How to make electricity with a potato”, “Model Volcano”, “What makes popcorn pop”, and “How to remove gum from hair” (the presenter was bolian) all given via comms. The party afterwards was quite the drunken affair featuring many songs from the collection of and led by Dr. Shaw, and drinks with dancing and drinking and singing and dancing and drinking and school fight songs and drinking all led by Captain Harkness, along with some young Ensign who was also led by Captain Harkness, out the door, not to be seen again for 2 days. Most theories are the she ate him.

Eventually, the ships were repaired and upgraded and the diligent engineering crew of the Endurance had repaired every blemish on her hull, leaving her looking as shiny and new as she was likely to ever get. As Captain Harkness ordered, Task Force 21 got underway as a unit heading out of system at warp 2, then kicking up to warp 7. On the second day of the 2 week trip to Atbar Captain Gamble received a series of messages, the first from a Federation Marshall named Hearns. Marshall Hearns, it seems, was asking after Lt. (Dr.) Shaw for “questioning” in relation to events concerning REDACTED, CLASSIFIED, NEED TO KNOW AND YOU DON’T, etc (they wouldn’t tell him). Not long (a matter of minutes) after that Captain Gamble received another call, this time from a security detail from the Andorian Space Navy regarding improper requests and attempted unauthorized acquisition of Andorian government property and were armed with a warrant to detain Lt. Cmdr Shran questioning and probable indictment. Finally, a security detail from Utopia Planitia arrived on Cardassia looking for Commander Zaran, found the Endurance had left for Atbar and contacted Captain Gamble just another few minutes later and demanding he turn the ship around and bring Zaran to them, or at least stop long enough for them to catch up to take her into custody, again, for questioning. The Captain declined and they were not happy. The Captain had a conversation with Captain Harkness regarding the situation, who basically didn’t seem to care. She was of the opinion that her ships and their crews were set and functioning reasonably well and she was not about to let that situation get messed up over what couldn’t possibly be that big a deal if it was just ‘questioning’ they were wanted for (and you should see what we got on the people on the Claymore!). She then asked Cpt. Gamble what he thought of Fleet Captain Flanagan when he met her, and he admitted that he hadn’t gotten to form much of an opinion based on the situation of that meeting, but her adjutant was certainly loud. Harkness told Gamble, “What you don’t realize about Flanagan is that she is extremely loyal to her people. Regardless of what she may think of the people under her, she will throw down with anyone to take care of her own. I’ll refer these issues up to her and you’ll most likely not hear about them again.” Some unnamed male Ensign was glimpsed at the edge of the viewscreen getting dressed during the conversation, though Gamble had the good sense not to see it at all, under any circumstances, bring on your damned Vulcan mind probe.

Cpt Gamble and Lt Shaw had a moment to sit down and discuss events of the past, a long overdue conversation that went to dark places in Wash’s (Dr. Shaw) past that they will recount for you in their private logs as none of us was there to actually hear it.

Captain Harkness orders TF21 to battle drills during the trip out to Atbar, practicing various formations and tactics and laying in a basic foundation of Fleet operations for the crews of these ships. All characters under 4o Fleet Operations gain 10 points in the skill, even if it is at o. If 10 points takes you over 40, then stop at 40 or consult with the GM (bringing him food will help your case).

Session 6: Arriving at Cardassia
Back to spacedock for repairs and more

Things that need to happen this session:
Captain needs to get Affidavits from the Crew and officers involved (perhaps delegated).
1st officer needs to assign (inflict) Jr Officer duties and see to it they are carried out. Done

When last we left our intrepid heroes (and their bleeding ship) they were in the middle of a fight with 3, then 2 True Way Cardassian vessels. Then the USS Claymore showed up….

What happened….

As usual, the appearance of the Claymore was, at best, a mixed blessing. The Endurance faced 2 remaining True Way (Cardassian rebels) Galors, having already dispatched one at the end of last session. The superior reflexes, training, and overall systems of the Endurance, as well as the Captain’s finely honed tactical acumen, gave it the advantage, allowing it to maneuver, dump plasma onto the path of the ship next to them (which it drove through), and dispatch with little damage (ok, none) in return. The far vessel was unable to acquire a target lock on the Endurance and could not get within firing range either. Luckily, the Claymore had charged its photon banks, raised it’s forward shield only, and put everything else into movement allowing it to close the distance (at 23 hexes a turn) and render the remaining Cardassian’s range and target lock difficulties a non-issue due to excessive explosion of their ship. The combat was resolved with 16% casualties aboard the Endurance and 3 dead.

After initiating a friendly (not at all) jib (taunt) at the Endurance, the Claymore warped away towards some unknown point and leaving the Endurance to proceed to Cardassia. After a quick word with Captain Harkness they were given permission and encouragement to travel at maximum in-system warp speed (warp 2).

Upon arrival the Endurance was immediately stuffed into a repair hanger and various space-suited individuals began climbing all over her, attaching things, tearing things away, all in the name of repairs. Captain Harkness arrived by shuttlecraft after doing a flyby to ascertain the condition of the ship, greeted the Captain and miscellaneous officers, remounted her shuttle (as captains often do) and left for parts unknown (the USS McKinley).

The Captain left the ship by shuttle to meet with Fleet Captain Flanagan, commander of Peace Keeping Group 5, to which Task Force 21 belonged (and also to have a look at the ship’s damage), and was escorted into her office upon arrival. Captain Seran or the Claymore was already present and standing at attention. Cleverly sussing out the situation, and opting to not go for the sneak attack, Captain Gamble also came to attention beside Captain Seran. A captain Mattox introduced himself as Fleet Captain Flanagan’s adjutant, then proceeded to tear into both captains for being over the legal limit of shenanigans. He mentions Utopia Planitia, failing to cooperate during combat operations, the Endurance being late, and the Claymore for showboating and breaching STWC protocol. Following their ‘Mattox-ing’, Fleet Captain (basically a Commodore) Flanagan deigned to speak, explaining, “Since there is time the equipment is on hand, and TF21 is assembling here, there have been some ship upgrades left behind by galaxy exploration types who got orders and didn’t have a chance to get them installed. Lucky you. Better to get them on a ship and used than have them gathering dust in our warehouses until some enterprising Cardie or Ferengi gets their hands on them. Take advantage of it while you can. Dismissed.” She seemed like a nice lady. (Ahem.)

Following the meeting with FCpt Flanagan, the command staffs (Captains, 1st Officers, and 2nd Officers) gathered aboard the USS McKinley, flagship of TF21 and Commanded by Cpt Sarah Harkness, also commander of TF21. In attendance:

Task Force 21 (TF21) Commander: Captain Sarah Harkness Flagship: USS McKinley
SHIP: USS McKinley USS Claymore USS Endurance
Commander: Captain Sarah Harkness Captain Seran Harkool Captain William Gamble
1st Officer: Commander Gurta Swin} Commander Yari Kim Commander Trinity Zaran
2nd Officer: Lt Cmdr Hamoirc Kresila Lt Cmdr Weirie Pelar Lt Cmdr Thelin Shran

The group stood at attention upon her entry and she left them there for the duration of the following speech: (Her tone isn’t kind; she’s upset with her situation and makes sure everyone knows it. While the briefing is for all in the room, she addresses the Captains only, knowing the junior officers are listening.) She began:

“Welcome to Task Force 21, the worst Task Force in the fleet. [pause] At least that’s what I was just told by Fleet Captain Flanagan. The good news is that expectations of us are low, and we have nowhere to go but up.” She shows the Operations map of the section of the outer asteroid belt in the Cardassian system the mission was to take place in, “Because all our ships didn’t arrive on time, the combined available Federation and Cardassian fleets had a hole in the sensor net exactly 2 cruisers wide. The firepower of the 3 federation cruisers, short by 2, was to give heft to the cardassian’s lightweight fleet of 16 cutters. This gap in sensors and lack of firepower allowed the True Way to escape, and that’s all on us. Now, it’s optimistic to think that we would have captured or destroyed all of them under any circumstances, however, we would have disabled or destroyed at least SOME of them! As it is, they ALL got away and we inflicted only minor damage, if any. That’s the reason you were met at the border by True Way forces. It was a retaliation from them for operation Candid, and it should have never been able to happen because they should be captured or destroyed, or at least have some bumps and bruises.

“We had the True way ships bottled up in the Cardassia system with only one path out, straight at us, and an op to engage them, Operation Candid, was held up because of lack of forces to effectively engage them due to ships being quietly pulled from here to Romulan space. Our Peacekeeping Group’s job was to keep them bottled up, and our Task Force was to hold the bottleneck. Unfortunately, your deployment timetable was missed, the ships that were stationed here had their orders and left, and the bottleneck escape route that was left open was not sufficiently blocked by TF21 and attachments. The True Way forces fought out of the trap and have disappeared. The Cardassians are upset, a carefully planned Operation was blown, the Fleet Captain looks bad, and TF21 looks worse.

“Now then, I’ve just read the after action reports of the Claymore and the Endurance from the ambush you both took part in. First, regarding your combat situation, nicely done, especially you Captain Gamble. Your crew compensated well for the software glitch in your tactical systems and being alert to potential trickery on the part of the enemy.

“Captain Seran, while you did well also, first taking out that True Way Keldan and then joining the Endurance on the hunch that they may be running into the same type of situation. However, you were wrong to leave the Endurance to pursue the True Way vessel when she was so wounded and with additional potential enemies in the area. We are a team, we act as a team, and regardless of the situation and personalities I expect you to be professional and work as a team with the ships of this Task Force. Gamble, you were in the wrong to refuse the help of the Claymore, especially in a fluid situation when the threat of other True Way ships in the area was hanging over you – you have to look to the security of your ship and crew at all times and I shouldn’t have to remind you of that. Finally, I’ve had reports from Utopia Planitia and the Starfleet Intelligence STWC detachment regarding both of your ships, as well as a suspected security breach of the USS Mushashi. Whatever is going on between you two captains and your ships is OVER. We have a job to do, and it’s serious. We don’t need showboating, we don’t need backstabbing, we don’t need infighting, and we definitely don’t need your egos! Is that understood?” (Assumed Captain’s acknowledgment) Under normal circumstances you’d both be looking at a serious reprimand, possibly leading to a Courts Martial of one or both of you, and certainly the loss of one of both of your commands.

“Now, I’m having this conversation with you both together and with the command crews of the entire Task Force present so that there is no misunderstanding of what I expect and how this Task Force will operate going forward. As 1st and 2nd officers, you are expected to temper your captain’s actions with good second or third party objectivity. I want to see strong inter-ship cooperation and support going forward. Officers, I strongly dislike having these kinds of conversations, and I trust there’ll be no further need for others like it in the future. Agreed? Good.

“Unfortunately, these are not normal circumstances. Here’s our situation: Star Fleet has entered into an aid and assistance treaty with the Romulans. Let that sink in for a minute. As you know, the Hobus star, in binary with the Romulus home star, was on the edge of supernova. As you likely know, it exploded 2 weeks ago. What’s generally unknown, but is breaking news in the Federation, is that the Klingons used the situation to launch a massive attack. We’re unclear on the force size involved, but what is clear is that the Klingons are playing for keeps. They’re not just trying to grab some territory as they did after the Nemesis episode, they’ve declared war on the Romulans and mean to break them completely.

“As you know, we’ve been helping the Romulans and Remans evacuate their home planets, using all of our assault ships and freighters, and a fair number of civilian transports as well. The Klingons swept in to the Romulas/Remus system, attacking everything that looked like a Romulan target. Some Klingon forces, in spite of our peace treaties, also attacked our relief ships, destroying around 1/3 and damaging another 1/3 of these unarmed Federation vessels in the area. In response, the Federation has called up the reserves, pulled the carrier fleets out of mothballs and is doing minor refit, shaking them down, and mobilizing for what could rapidly become an unstable situation. The Vulcans are pushing hard for a military aid and assistance treaty to help the Romulans fight off the Klingons, and it looks more than likely that the Federation Council will grant it.

“With the current animosity of the Klingons towards the Federation, we may well see the Klingons declare war on us. That means things are going to get hot around here, since we’ve got a large number of Romulans and Klingons in the area, and Cardassians who want them both gone. If you study our operating area”, she points to the TF21 Ops Area map, “you’ll see that we’re in the vise, quite literally. This is going to get worse before it gets better, and that process has already started.

“Star Fleet pulled all the Galaxy Exploration vessels out of this area 2 weeks ago, hoping their absence wouldn’t be noticed until reinforcements could arrive. No such luck. We think there’s a leak in Star Fleet Intelligence that tipped off the True Way, but it’s possible that we could have just run afoul of bad luck. Either way, observe your intelligence reporting directives in your orders package for the time being, regardless of who orders you to report otherwise. If they are putting significant pressure on you, refer them to the Theater Commander, Admiral Koderman, and those are his orders.

“What does this all mean? It means we don’t have the firepower to be everywhere we need to be all the time. If the Klingons mass their forces in the area, we’re insufficient to stop them, spread out as we are. If the Romulans and Klingons engage in hostilities, we’ll be hard pressed to protect everyone else from the spill-over damage. Even worse, if the treaty goes through and the Romulans and Klingons engage, we’ll be expected by the Romulans to throw in on their side, making it much more likely they will go on the offensive. The pirates and smugglers and slavers and black marketers in the area know this too, and it’s going to be even more difficult to do our jobs if we’re having to deal with frying bigger fish."

[A quick flash of something unpleasant crosses her face]

“There’s something else as well. By order of the Federation Council, Star Fleet is cooperating with the Cardassian Government at every level and is to be “responsive to their reasonable requests” whenever possible. What does this mean to you and I? It means that we get to play host to a Cardassian liaison officer stationed on each of our ships.” She pops her comm badge, “Please come in.” 3 Cardassians enter the room. “Gentlemen, these are your liaison officers from the Cardassian Defense Force. Dalin 1st Tier Nedai is stationed on board the USS McKinley, Dalin 1st Tier Mukigo will post on the USS Claymore, and Dalin 1st Tier Tathon will post aboard the USS Endurance. Captains, you and your crews will show these representatives every courtesy and regard them with ambassadorial privilege.

“Please be aware that they have their own objectives to accomplish in addition to their liaison duties. They will from time to time need to communicate, travel to specific systems, host conferences on board your ships, or beam down into a hostile area and will need support to let them accomplish their objectives. This is acceptable to Star Fleet. While you are not at their direct disposal, if they make a formal request of you, you will log it and do your best to accommodate them. If there is a difficulty with what you are asked to do, log it, and follow your directives, using proper courtesy and protocol at all times. If there is a direct conflict with your orders and/or objectives, your orders & objectives take precedence. If necessary, send issues up the chain to me, but I don’t want to hear about every little thing, and I expect you to be able to handle these issues yourself as [she turns and stares at Dalin 1st Tier Nedai as she finished her sentence using a very icy tone] I’m handling mine. Let’s be clear on that. Finally, if you need anything from the Cardassian Defense Force, any Cardassian world, or the Cardassian government, you send that through your liaison.

“Be seated. Any questions?” There were questions. Some were answered. She gave everyone their orders package:

Orders: Proceed to Atbar and enter the TF21 ops area. Patrol Sheva, Keid, Sonebr, and Atbar, respecting the boundaries of both the Klingons and Romulans, and gather detailed sensor data of all 4 (threat oriented scans at Atbar. Do not launch probes into Klingon or Romulan territory nor enter their space without their explicit invitation, even if you are pursuing criminals, true way, or aggressive Klingon or Romulan forces. Atbar is a heavily defended world and your safe harbor if you need to escape and/or evade, and it is also your home base and the command point of TF21, TF23, TF24, and TF25, and should you call for help it will be arriving from this location.

In addition to your main patrol route, which should be varied routinely, visit the Huaco, Mersoh, Sira, and Taggrut systems periodically. Be unpredictable. Use the sensor bouy array, maintain and monitor it, and add to it where you can. We have reason to believe that the core of illegal operations as well as the main supply lines of the True Way, Romulans, and Klingons run through this area of space.

Travel times (at maximum warp):

From System To System Dist. (LY) Time W9.95 Time W6
Atbar Sheva 6 1.32H 5.58D
Atbar Keid 6.75 1.48H 6.28D
Atbar Sonebr 4 52.78M 3.72D
Atbar Taggrut 2 26.39M 1.86D
Atbar Huaco 4 52.78M 3.72D
Sonebr Keid 4 52.78M 3.72D
Huaco Sheva 1.6 21.11M 1.49D
Huaco Keid 2.33 30.74M 2.17D
Huaco Sonebr 2.4 31.67M 2.23D
Huaco Sira 1.25 16.49M 2.17D
Huaco Taggrut 2.66 35.1M 2.48D
Huaco Mersoh 1.8 23.75M 1.67D

Your Mileage May Vary.

It was a long meeting and no coffee was served.

Following the meeting, the Command crew rode with Cpt Gamble back to the ship in his shuttle and he toured the ship’s damage for their viewing displeasure. Once back on board an unknown captain was waiting for Cpt Gamble who was, by now, a little tired and exasperated what with fighting a space battle, losing crew, 2 meetings with commanders that were, to say the least, uncomfortable, and a long discussion with the TF21 command crews where Captain Seran was, shockingly, a pompous ass and his Trill 2nd officer with the Borg eye that locked onto, and stared at, Cmdr Zaran the entire time. Basically, he was ready for a nap.

Cpt Albert Whittaker introduced himself to Gamble and minglers as the commander of C1SEF (Cardassia One Starfleet Engineering Facilities). He was there to get the repairs to the Endurance handled, finish the work that really should have been done in Utopia Planitia on their warp drive, and install a couple of components for them and he was here to discuss this with the captain and engineer. Specifically, new shielding was installed [1/7 ratio, max 60 per shield] and an upgrade to the tactical software systems that will allow a superior lock of up to 3 ships. Their meeting is brief and work starts.

Unfortunately, C1SEF isn’t really equipped, nor does it have the manpower to scrub, repaint, and give necessary cosmetic touches to the ship’s hull, but the chief engineer, Cmdr Tanari, puts his men on it and they get it knocked out. The shields are installed along with the tactical software, the repairs are made, and the engines are giving a warm test to certify the ship for max warp capability of 9.95. After 3 days the ship is ready to begin it’s mission.

During the 3 days of work on the ship, Dalin 1st Tier (D1T) Tathon does his best to make himself, and his retainers, and belongings, and a cask of Amontillado, comfortable in the VIP quarters (2) he and they were assigned and set about his personal mission of being a thorn in the side of the officers and crew of the USS Endurance. There are simply not enough pillows aboard this ship, but at least he finally has a working replicator in his quarters, even if the recipes are either bland or terrible.



Session 5: A funny thing happened on the way to Cardassia....
transwarp and a (not very) well laid trap

As per your orders you are to travel to Cardassia, arriving no less than 4 weeks from the start of your ship refit (or would it just be a ship fitting at this point?) which was 23 days ago. The trip via the Stable TransWarp Conduit system (SWTC system) takes 7 days with current traffic levels. Other travel times will take months of travel.

At the start of today’s fun you currently have 5 days until you are in violation of your orders.

Going into this session, a few standard things you would know that are relevant:

  1. In system, near inhabited worlds you don’t warp. 1/4 impulse is standard speed. At your tonnage, that’s roughly 15 miles per second, just over twice planetary escape velocity, and more power is required to travel faster. The mechanism of the engines is such that they don’t accelerate according to Newtonian physics as they are essentially a gravity drive grabbing and pulling nano-patches of spacetime around the ship to accelerate and decelerate, which is why the ship seems to respond aerodynamically in space rather than by Newtonian laws of physics. more power
  2. In system, away from planets and traveling about, warp 1 is max safe speed and also the standard speed for Starfleet.
  3. In system, unless the Borg are attacking or some other horrendous event is taking place, Warp 2 is emergency speed as there is a LOT of stuff to be avoided here.
  4. In deep space (not in a solar system) the speed limit is warp 5 except for emergencies. Properly fitted ships may travel at warp 6. Your ship is so fitted though it is NOT calibrated and calibrating it en route is something you will be expected to do.
  5. The trip out is an excellent time to familiarize yourself with the Cardassian Theater Intelligence briefing if you haven’t already, and to do so again if you have.

Familiarize yourself and crew with STWC entry and exit procedures before doing it:
Inserting and exiting requires a sensor roll, a helm roll, -20% for each. If either is failed the ship fails to insert and goes to the back of the line and a fail on an exit is an ejection to some random point 1d10 ly away with 1d10 SS damage and d100 crew casualties. Stop for repairs 1 hr per SS, travel to nearest STWC destination to try again. Tuning your ship will take 4 days if all goes well, and with each day of tuning the penalty is reduced 5%. A failure in the STWC will cost you a day of tuning and add 5% to the penalty. I will be working hard to find ways for you and your crew to win including luck rolls, poetry readings, and the morality rap stylings of LtJG Rixx. Be aware that Administrative rolls may help with long lines, priority orders and all.

What happened….
Travel via the STWC (Stable TransWarp Conduit) network shaved some time off their trip turning what is a typical 148 day trip at warp 5 into a 7 day trip:: Sol to STWC 12 hours then a wait of 13 hours (-7 hours with good Admin roll), STWC travel 1 hour, crossing starbase 74 space 24 hours, no delay, STWC travel 1 hour, crossing Draylon space 18 hours, no delay, STWC travel 1 hour, crossing Trill space 12 hours, waiting your turn at Trill 36 hours (-18 hours with good Admin roll), STWC travel 1 hour, crossing Bajor system 24 hours + 2 hour stop at DS9 for Marines, no delay, STWC travel 1 hour, travel from SWTC exit to Cardassia 12 hours.

The crew rejoiced as the Endurance broke Mars orbit and headed for the STWC point to leave the Sol system. On the way, the engines were stabilized a bit, allowing a maximum speed of Warp 6. At the entry point of the STWC one of the officers running the entrance to it (one ship at a time to limit exposure should it fail) was someone Lt. Shran knew briefly from a prior tour in Starfleet Intelligence. This, combined with a healthy bribe of excellent real coffee (plus their priority orders) got them moved up in the line of waiting starships so they only had to wait 6 hours for their turn instead of 13, gaining some of their lost time back.Began crossing Starbase 74 space via wide arc over system to use higher warp speeds and shave another 6 hours off their time. Continuing through Starbase 74 space, Lt. Garcia initiated the start of a 3 day Marksmanship Modern (Phaser) tournament, which many of the crew participated in. The Endurance traveled to Draylon space via STWC near the end of the day. Crossed Dralan space. Phaser tournament continued, traveled to the Trill system via STWC, negotiated 18 hours away, moving halfway up the line. Spotted the USS Claymore 5 ships from the front of the line when they entered the que and made the quick decision to contact them and send their greetings. Oddly, the Claymore’s automatic Quarantine protocol activated as their turn was coming up, though it disengaged after 10 minutes or so (very suspect, that) and they took their turn to enter the STWC. Lot of time sitting in line while Lt Rixx fidgeted. The Endurance got it’s turn to travel the STWC to Bajor at the end of this day. The Phaser tournament wrapped up with MCPO Jacek Skanokovich taking 1st place and Lt. Shran taking second. There was a YOGA session led by Wash as well. Traveled to DS-9 taking half the day, picked up a company of marines (125 units of jarhead) and headed to the Cardassia SWTC arriving in system 6 hours late for their ‘must report by’ date, with 12 hours travel to Cardassia Prime still ahead of them.

After arriving the Endurance checked in with Starfleet Command at Cardassia and got orders to report to Fleet Captain Flanagan. 2 hours into their 12 hour trip they ware hailed by 2 pre-war Galors on an intercept course identifying as Cardassian Defense Force,
Gul Joret Dal of the CDS Rajan and Gul Audnes Toran of the CDS Nestern, who have been ordered to escort the Endurance to Cardassia Prime as a favor to Admiral Florez. This is normal for Cardassians, though a bit out in the boonies, but who knows what circumstances lead to this being the best place to meet up with you. Their credentials checked out.

Of course these are True Way vessels leading the Endurance into a trap. 2 hours after beginning the trip to Cardassia with their new escorts, one third of the way from the STWC exit and at closest approach to badlands the Endurance picks up a distress call from another Galor. Gul Lang of the CDS Velain claims to be under attack by 2 Klingon Vor’cha and Gul Dal demands the Endurance move with them and render aid. Communications with the Ship are spotty but they report that they are basically fine with light damage, claiming the Klingons ran when the relief fleet came within sensor range, but that they have sustained some engine damage and could use support while they effect repairs. Sensors show it is venting charged plasma which is interfering with other sensor scans at this distance. The Endurance joins to help and all 3 move towards the disabled ship, shields up, weapons armed. When all 3 came in range sensors and computer work combined to reveal the ruse just before they will open up on the Endurance. Luckily these are pre-war Galors or the Endurance would be in real trouble.

Still, tuning flaws in the targeting array reared their ugly head and the entire opening folly of all forward weapons on the Endurance missed their target. The two Galors flanking opened on the Endurance, blowing down it’s forward shield and their aft port shield, inflicting serious damage. If not for the valiant efforts of the damage control teams it would have been much worse. After a little maneuvering the Endurance launched it’s full spread of aft torpedoes destroying one of the Galors. The Galor that pretended to be hurt moved within weapons range but was ineffective. Just then, the Claymore appeared , closing on the distant Galor.

To be continued….

Session 4: Warp drive issues, inquiries, Orions, and quarantine
Field testing, shakedown, and Claymore Shennagins

Continuing on the time table, Currently 1 day behind schedule:
You have a full schedule of tasks that may or may not be completed in time and you are already 1 day behind schedule:

  • Day 10-11: Full warp core power up, rough tune dilithium matrix, EPS test, warp engine power up, rough balancing of engines, begin 36 hour test cycle to create tuning profile, finish starship services equipment installs.

It didn’t want to power up. Tried, failed, repaired. Lather Rinse repeat. 4 tries to finally succeed. Even then, it was shaky. Eventually got the 36 hour engine tuning cycle started. Lost a day here.

  • Day 12-13: Board essential crew and officers, tow from stardock to Phoebes testing range for full warp power up and fine tuning, warp core dilithium matrix fine tuning, full sensor tuning powered from Impulse and Auxiliary only, light weapon testing and calibration, transporter system test.

More Warp issues, weapons testing was fine, but transporters had glitches. Didn’t fall further behind, much.

  • Day 14-17: Warp shakedown runs and continued fine tuning.

Flew around the Sol system trying to work out a serious shimmy at warp 5. Got it down to a low vibration by the end. Still not good.

  • Day 18: Full shielding test, full weapons test, full sensor test, deflector test, red alert test.

Shield testing had issues as well, this ship is fighting the crew every step of the way it seems. Weapons test went fine, sensor test went fine, deflector test and red alert test successful. No time lost.

  • Day 19: Full crew boarding and ship systems fine tuning back at Utopia Planitia.

Crew moved in, brought their crap, and no one failed to report.

  • Day 20: Continued fine tuning and repairs, take on armament, take on shuttle compliment, take on marine landing craft (x2 40 man ship to ground transport vessels), marines board, final preparations for departure.

Captain Yu has sends a formal summons to Captain Gamble through channels and the office of the Judge Advocate General’s office basically saying, “Please report to my office at 09:00 hours tomorrow.”

Upon arrival Yu informs Captain Gamble the USS Claymore left the system the day before, on time. Before leaving, Captain Seran of the Claymore filed a grievance with Captain Yu against the Endurance, it’s crew, and captain for a series of trumped up charges:
1. Captain Gamble waits for 25 minutes in a conference room adjacent to Captain Yu’s work office. Probably catching up on his texting and downloading cat videos.
2. Lieutenant Junior Grade T’Kreef (no image available), female Vulcan with a husky voice, enters the room, doesn’t acknowledge the captain, arranges her stuff on the table, seats herself, activates a recording device and says: “Please state your name, rank, and assignment for the record.” – He does. She is efficient and as worthwhile to talk to as most teapots. She is on her script and doesn’t vary from it.
3. “I will now read the charges brought against you and your ship: 1) That crew members of the USS Endurance did willfully appropriate materials and components assigned to other ships construction for the benefit of the Endurance’s own timetable and construction. 2) That the Officers of the USS Endurance did willfully reroute materials both various and numerous away from the construction yards and through warehouse Echo Alpha Alpha 889208 Bravo as a collection point before choosing specific components out and sending them on to the USS Endurance to be fitted immediately and bypassing various systems, methods, and processes designed to coordinate, track, and and record the deployment and receipt of said materials. 3) That transportation officers assigned delivery of materials, notably warp engines, were harassed, assaulted, and forced at phaser-point to vacate their assigned Slow Tug Boat that they were the lawful skipper of, in particular one Harvy Sosae (pronounced so-say). 4) That the timetable of the critical launch window of the USS Claymore was interrupted by the interference of various officers of the USS Endurance unlawfully entering the USS Claymore for said purposes. 5) That the Captain of the USS Endurance, Captain William Gamble did knowingly authorize or otherwise refuse to curtail each of these incidents and actively engaged Captain Hitaki Yu in order to “run interference” for his crew and their activities in this conspiracy. How do you plead Sir?
4. “You have the right to have an advocate here if you wish Captain. This is simply an exploratory briefing. Do you feel the need to exercise this right at this time?" He declined.
5. She went through the charges 1 by 1 taking his side of the story while being as pointlessly Vulcan as possible. Gamble bristled, in an efficient, proper, Starfleet Captain sort of way.
6. She wraps up: “Very well Captain.” Turns off recorder. “You should be aware that Captain Yu arranged this meeting after Captain Seran requested an investigation into the role the Captain and Crew of the Endurance played in the difficulties experienced by the Claymore, as is his right as a Starfleet Captain. If you should wish to make a similar request, or even prefer charges and have a full investigation launched, that is your right. I would point out captain that neither of you would seem to have time for such proceedings but it is your right should you wish to do so anyway. Therefore, these are your options:
A. You may write up reports and submit evidence. The Claymore will be recalled and the officers of both ships will be retained and transferred to Starbase 1 and a full investigation launched leading to courts martial proceedings for one or both Captains and perhaps various members of their crews. Other officers will be selected and given these ship and command slots.
B. You may, instead, choose to let it go. I am authorized to inform you that a quiet investigation is underway already, your testimony will be added to that, I will ask you to take affidavits from your senior officers and transmit them to me within 1 week, you keep your command and ship slots, and you launch as soon as you can with Captain Yu doing his utmost to accommodate you.
“What do you wish to do?”
Captain Gamble, shockingly, choose option….B.

Upon exiting Captain Yu let Captain Gamble know that there was a situation upon his ship that needed his immediate attention. Gamble phoned home, got the bad news, and went to see what could be done about it. Yu promised to help all he could as Gamble left.

While he was having his fun and exciting deposition the Endurance was enjoying a visit from Starfleet Intelligence. Two properly identified LTC’s, Smith, and also Smith, requested entrance to the ship from the rating on duty after properly identifying themselves and their organization and flashing scary paperwork at the poor fella (who, to his credit, peed not one little bit, as he tells the tale). He escorted them through the ship, to the turbolift, and up to the bridge. They presented themselves from the turbolift and made no effort to stroll onto the bridge. 2nd Officer (also Chief of Security and Chief Tactical Officer – really long signature line on his correspondence) LtCmdr Shran immediately enacted ‘Unwelcomed Hostile Naughty People Nearly On The Bridge Protocol’ and did not offer them either coffee nor entry to the bridge. A flurry of activity ensued as badges were flashed, protocols were inflicted, arrest warrants were flourished, the 1st Officer was alerted, coffee was drunk, feet were dragged, insincerely polite smiles were offered, chests were puffed out, security arrived as not much happened, and a low ranking enlisted rating sneaked away to resume his post outside the ship at the entryway to the gangplank (which is actually a tube between the station and the airlock).

Eventually the 1st and 2nd Officers conferred and determined that they would escort these Smiths (still smiling insincerely) to the galley and would not allow their shoes to soil the freshly laid bridge carpeting. There they would be presented with their quarry – it seems they were here to take the two Orion members of the crew into custody. Their orders checked out as authentic, but were classified, leaving little room for maneuvering for the gallant command staff or the Endurance to thwart their presumed evil intentions. As per “the plan” they were led, by the longest and most circuitous route imaginable (their Starfleet equivalents of Fitbits chirping happily at them as they got plenty of steps that day). They were even taken by sickbay where the CMO insisted on accommodating them with complimentary anti-parasite full body cavity searches and injections, as per many a Starfleet regulation he happened to be versed in.

They (eventually) arrived at the galley, were met by LtJG Daevohse, Assistant Chief Tactical Officer, and Lt Cmdr Josco Tanari, Chief Engineer, who were both escorted, quite respectfully, by Endurance Security folk and presented to the SI Smiths who informed them of their situation took them away without fanfare or handcuffs. LtCmdr Shran placed a call to an old friend from Starfleet Intelligence who was posted here on station.

The Captain arrived back at the ship shortly after their departure, called a hasty staff meeting to discuss how to get the officers back, options to cover them so they could still meet the launch schedule if they couldn’t get them back, what a jackass Captain Seran is (hey, it’s in the log!), etc. Towards the end of the meeting Shran got a call from his SFIntel friend who asked for a quick meeting in a specific bar on station.

With the ship preparing to leave for it’s warp flight certification test, Shran hurried to the meeting, met with his buddy Jones, shared a quick drink, and basically found out that Captain Seran has friends in Starfleet Intelligence who were holding the Orions for questioning on trumped up charges for a period of 21 hours, implying that a favor was being repaid or favors had been exchanged for this. Shran Thanked him, beamed back to the Endurance as it was in final departure preparations, and just before Captain Yu came aboard to administer the warp flight certification test.

  • Day 21: Warp flight certification test, released from Utopia Planitia command, depart.

The Endurance moved smoothly up to and through warp 4 and shimmied it’s way to warp 5. Captain Yu hid his anxiety well, having been on more than a few of these rides. Eventually the trip came to an end back at Mars, the warp drive was certified, and Captain Yu had a (very) brief commissioning ceremony for the USS Endurance on the bridge. As the ship approached the station for docking the quarantine protocols were activated, locking down the ship, putting it at station keeping, and preventing anyone from entering or leaving the ship.

Thinking ahead to the traditions of the ship and events of the day, the Chief Of The Boat, aka Crew Chief Skanokovich, had procured and set aside, in a quite secure area, a beverage in quantities sufficient for a ship’s crew level celebration of the commissioning of the USS Endurance. With nothing better to do, the party got started. There were toasts, there was dancing (though no music, at first anyway), there was a vicious rumor of the 1st Officer attempting to drag Lt Garcia away for a private health and welfare inspection. Both were saved by the quick thinking of the Chief Science Officer, LT Mary Washington “Wash” Shaw, PhD., aka “Wash”. Wash had earlier participated in the finer points of an excessively dense health and welfare report and ongoing parasitic sterility action play submitted by her and Cmdr Dr Walon Burress. The results of this report are that the 48 hour quarantine was lifted after only 4 hours (pretty much first thing the next morning by that time). The Orion officers were allowed to be beamed aboard the Endurance, Captain Yu said his adieu and beamed out, and the Endurance was released to embark upon it’s mission.

Session 3: Where the hell did we leave that warp core this time?
How to fillet a panda (or a selat)

Lt Farrad, Nadira
Chief Science Officer
USS Endurance
Task Force 21
Peace Keeping Group 5
Cardassian Theater Command

Lt Farrad,

You are hereby relieved of duty aboard the USS Endurance and will report to USS Olympic Glory by stardate (12 hours from now) for reassignment to DS-5 as Chief Science Officer. You will report to Commander Tranoff upon arrival for duty assignment.

Thank you for your service in Cardassian Theater Command and best of luck in your new duties.

Branch Admiral Brandon Mitchel, Adjutant
Cardassian Theater Command
Lt Shaw, Mary Washington
Civilian At Large, Starfleet Ready Reserve
Prior Service Endorsement

Lt Shaw,

You are hereby reinstated to active duty, rank of Lieutenant. You are ordered to report for duty aboard the USS Endurance, NCC – 83812 and will report to Captain Gamble by stardate (7 days from now – today game time) for assignment to USS Endurance as Chief Science Officer.

Thank you for your service in Cardassian Theater Command and best of luck in your new duties.

Branch Admiral Brandon Mitchel, Adjutant
Cardassian Theater Command
Continuing operations to source out the disruption of supplies and components by the officers and crew of the Endurance are almost completely successful with the notable exception of the Starboard Pylon (the stick thingy that connects the warp engine to the hull of the ship). Said component was instead routed to the Claymore and was already being installed when LtJG located it (after beaming aboard the Claymore and wandering around for several hours unsuccessfully looking for someone to answer her questions) and finally reported in.

During the period from day 6 through day 10 of the refit the investigation was stepped up and much computer modeling and network tracing was inflicted upon both the station and the Claymore by LtJG Frey. Frey, who was very close to sorting through the mess, ‘accidentally’ opened a sealed record of a unnamed (officially, it was Captain Seran of the Claymore) but quickly discovered the mistake made through the use of overly aggressive algorithms (she’s sticking to that) and used her expertise to quickly reseal the file without reviewing any of the content of said file. (Ahem.)

Suspecting members of the Claymore crew were being overzealous in the efforts to refit their ship at the expense of other vessels timetables, a plot was hatched, an evil scheme became apparent (raising schemes is such a hassle), and, based on information that had ‘come to light’, and ‘item’ of high desirability came to the notice of the crew of the Claymore while the officers of the Endurance both watched, and waited (wringing their hands and laughing creepy little laughs). It was 3 days before the patient perpetrators started to make subtle moves towards acquiring the remaining Selat being held at Utopia Planetia.

Being less patient than the crew of the Claymore, 1st Officer Zaran launched her own investigation. She discovered that the animal was, in fact, in good health, that it’s cage was, in fact, in good working order, and that it was, including the Selat along with its own weight, quite heavy. Somehow the Selat managed to get a swipe at her and medical attention was rendered. She and the Captain discussed her adventure, then she got back to her duties.

A meeting with Captain Seran and Captain Gamble was called by Captain Yu for the next morning in Yu’s office after Gamble, Frey in tow, delivered to Yu come compelling evidence for what might be going on down on the refit docks. Apparently someone down there may have seen a bat the size of a man, but that’s just a rumor. Captain Seran seemed surprised and concerned about what seemed to be happening right under his very nose. When Gamble mentioned the Selat Captain Seran didn’t seem to know exactly what Gamble was talking about but was concerned to know how He was aware that Seran had a pet Selat as a child. The meeting ended shortly thereafter with Seran vowing to start his own investigation aboard the Claymore.

The following day, as the shiny new Starboard Pylon was being installed on the Endurance, Seran and his Chief of Security marched into Yu’s office and told him that the 3 crewmen responsible had been apprehended, evidence of their guilt found, and there should be no more Tom Foolery going on from people assigned to his ship. It seems that these crewmen spent their last tour aboard the Endurance and likely had a grudge or something. (I think I served with a Thom Phoularie back in the ‘Nam, but I can’t be sure). Gamble, upon being notified of the arrested crewmen notified his senior personnel, at which point the Master Crew Chief of the Boat and All He Surveys (when not on shore leave) who served with these men last tour informed the Captain that these men were excellent crewmen, would not have done this, and did not have the technical expertise to pull off anything like this in any event. Someone somewhere (resembling a bald and very handsome GM fellow) suggested that this may have been a message of some sort from the Captain and Crew of the Claymore to the Captain and crew of the Endurance.

Other than some initial power up test issues with the Port engine, an initial power up issue with the Impulse engines and a small difficulty with the shield installation, things went smoothly from there and all the technical problems were resolved efficiently and rapidly. All said and done the Endurance is 1 day behind schedule at this time.

Sickbay is running smoothly and efficiently, though the CMO has not been seen outside of the 4-Aft lounge or the hallways between there and his quarters.

At some point towards the end, which my goldfish-like memory is not producing for me, a revelation that quite a few members of the crew of the Claymore, especially among the officer ranks are former Maquis. Captain Seran’s status in that regards is unknown (more or less), but you know how that Bajorans can get….

Session 2: Fun with Warp Engines
How to steal a tug boat and make it their fault....

The Officers arrived (eventually) and work on the actual refitting of the USS Endurance began. There were problems with supply but seemed to sort themselves our. There was a scene where the 1st Officer want to Cpt Yu for some help and explanation only to discover 4 Captains angry and yelling at Yu in his office. She forced her way to the front, joining the fray, staying after it dispersed, attempting to get something helpful from Yu, but there was little he could, or would, do.

As things began to smooth out LtJG Frae discovered some oddities in the logistics of the computer records regarding the shorted items and brought this to Cmdr Jeren’s attention. Following up on this, the Crew Chief and the 1st Officer Jeren secured a warehouse (legally), had all shipments to the Endurance routed there via transporter for inspection and verification, then to be be beamed to the Endurance (which slowed things down, but not much). As this project was under way, they jumped aboard the Slow Tug SS Crawfish (legally), captained by Lt Harvy Sosae, to travel out with it to their warp engines which it was to tow to the Endurance for later fitting. On the way out, the 1st Officer produced a phaser and, engaging in an act of high piracy, took command of the Slow Tug. Whether by circumstance or design, the Pilot of the Slow Tug was ejected into space (in a space suit) where he was eventually (8 seconds) beamed into some kind of a bar and some smooth talker tried to convince him to, “get drunk or something”.

The ‘heroic’ 1st Officer then, using some white-knuckle maneuvering, towed the first of the two warp cores to their warehouse, avoiding the notice of anyone buy some unknown means (suspected witchcraft). The engine was determined to be the correct one for the Endurance and checked out fine. Cmdr Jeren surrendered the pilot seat (it got boring) to Grant Jackson who then flew the tug to the destination that Lt Sosae was given which turned out to be the USS Claymore, not the Endurance.

Under Jeren’s orders the engine was flown to the Endurance and dropped off, then the Slow Tug went back for the other warp nacelle. Upon arrival it was nowhere to be seen. Contacting the station they received transponder codes for both warp engines (they had the same code since they were paired. One showed up on the view screen at the Endurance’s location, the other was moving away from the engine storage facility towards the various mobile ship repair facilities, and specifically closing on the position of the Claymore. The Crawfish was prodded forward (beaten like a rented mule) at best speed until it caught up with the Slow Tug towing the second nacelle, which was fairly easy once a security team was beamed aboard and they convinced (intimidated) the Specialist piloting it to bring it to a halt.

Via comms (I think, hard to remember during the shock and awe phase of this) Cmdr Jeren had the security detail checked the destination of the nacelle to confirm that it was bound for the Endurance and was indeed being taken to the Claymore. With a bit of persuasion (coercion) the nacelle was rerouted to it’s proper location.

That’s the point where Lt Jackson noticed their first nacelle was moving again, and away from the Endurance. The Crawfish scampered over to it (as only a Slow Tug can) and using their strategy (alarming tactics) managed to get the Slow Tug hauling IT away to stop, then take it back after discovering it was being taken to the USS Murmann. And that’s when….the session ended.

Things that happened:

Time Table:
a. Day 1: Select ship components. Components pulled and assembled for installation, umbilicals attached, computer cores installed.
b. Day 2: Computer cores attached to core systems and powered from umbilicals, core engineering consoles installed and tied to computer if available, otherwise lose a day. If successful, warp Core installed, EPS Systems installed, Auxiliary power (2 fusion plants) brought online, if all parts are available, else lose 1 day.
c. Day 3: Begin installation of ships services (replicators, turbolifts, airlocks, internal doors, internal force field projectors, replicator consoles, large medical equipment, security equipment, internal sensors, external hull sensors, etc. This will continue on an ongoing basis during and around other component installation. Some parts are available, others aren’t, rather expected at this stage and they are installed upon arrival.
d. Day 4: Impulse engines arrive and begin 3 day installation process, if available, lose day(s) if not, transporter component upgrade installation, photon and quantum launcher installation. Recheck availability daily.
e. Day 5: Space seal accomplished under any circumstances, deflector array install, sensor array equipment install and connection, life support established under ship power or umbilicals. Everything gets easier and faster from here, for the most part. Engines arrive, precheck begins, positioned for installation.

Things expected to happen next time:

Time Table (Continued)
a. Day 6: Port warp engine (if available) installed, bond welded to pylon mounts and pylons bond welded to both inner and outer hull connectors and superstructure, connected to EPS power supply.
b. Day 7: Starboard warp engine (if available) installed, bond welded to pylon mounts and pylons bond welded to both inner and outer hull connectors and superstructure, connected to EPS power supply. It should now looks like a ship.
c. Day 8: Impulse engine power up testing, first M/AM reaction of the new warp core conducted inside class 3 engineering force field. If successful EPS testing and tweaking begins, warp engines low power circuit test, cooldown, and offline. Bridge equipment installed.
d. Day 9: Shielding connections and initial low power testing, deflector array test, cabin furnishings, marine equipment, phaser array installation, finish all console installs. Yellow alert test.
e. Day 10-11: Full warp core power up, rough tune dilithium matrix, EPS test, warp engine power up, rough balancing of engines, begin 36 hour test cycle to create tuning profile, finish starship services equipment installs.
f. Day 12-13: Board essential crew and officers, tow from stardock to Phoebes testing range for full warp power up and fine tuning, warp core dilithium matrix fine tuning, full sensor tuning powered from Impulse and Auxiliary only, light weapon testing and calibration, transporter system test.
g. Day 14-17: Warp shakedown runs and continued fine tuning.
h. Day 18: Full shielding test, full weapons test, full sensor test, deflector test, red alert test.
i. Day 19: Full crew boarding and ship systems fine tuning back at Utopia Planitia.
j. Day 20: Continued fine tuning and repairs, take on armament, take on shuttle compliment, take on marine landing craft (x2 40 man ship to ground transport vessels), marines board, final preparations for departure.
k. Day 21: Warp flight certification test, released from Utopia Planitia command, depart.

Session 1: Our ship on her maiden thud
THAT'S our ship?!?

Campaign opens: We begin with a single ship and crew in the Cardassian sector as the events surrounding the Hobus supernova unfold. The USS Endurance, fresh from teardown is ready for refit, assigned all new officers, and has a standard 10% annual crew rotation out to other assignments. The 90% of the enlisted crew remaining onboard are veteran shipboard spacialists, and the crew chief has been drilling them to maintain their efficiancy levels in anticipation of their new captain, command crew, department heads, and their juniors. The ship, like all others in the area, receive their orders directly from Admiral Koderman, Commanding Federation Theater Operations, Cardassian Sector, via his adjutant, through the office of Branch Admiral Florez, Commander Peace Keeping Forces, Cardassian Sector, Via her Adjutant, through the office of Fleet Captain Flanagan, Commander Peacekeeping Group 5, via her Adjutant, through the office of Captain Harkness, Commander Task Force 21, via her Adjutant and 1st Officer Gurta Swinn. Directly. Right to you. Yep. That really is Koderman’s signature, though. Direct enough for a brand new captain and crew. Believe it.

Captain’s Orders:

Session 0: Building Characters
Pre-Session Campaign Information

Star Trek: Aftermath, Cardassian Theater

Session 1: Character Building

Starting Game Situation

(From Home Page)


I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.