Star Trek: Aftermath (Klingon Phase)

Phase II, Session 8: Starbase 134

You didn't see this coming....

NEWS FROM THE FRONT:

This…is FNN. Wolf Sanders reporting.

Reports of Klingon atrocities in occupied Romulan space are as expected: brutal, cruel, and frequent.

The forces of House Monak were repelled in their offensive against Talvath, a prime Romulan resource world.

House Dagot, holding Khazana, had been stalled since the opening days of combat, but now is being pushed back. Intelligence believes their forces have been hardest hit by ship reallocations from the assaulting forces to shore up the forces building up along the Klingon/UFP borders.

In the Romulus sector Klingon forces continue to engage the Romulans in heavy combat. 3 Klingon houses have been identified so far in the operation – Mur’gek, Volas, and B’Tori, none of them being high ranking houses in the Klingon social/military structure. Klingon tactics are focused on support vessels and lighter ships, leaving capital ships unengaged but stripped of outer fleet defenses. Klingon casualties are very high, especially among B’Tori forces, but the tactic is effectively leaving the Romulans with little ability to protect the evacuation operation, and it may have to be called off. The evacuation fleet, already injured in the initial assault, is down by a further 30%, though only 3 Starfleet vessels have been destroyed since the opening days of the war, all of them freighters caught incidentally in the blasts of other destroyed ships. In fact, the Klingons are taking great care to not target or damage Starfleet vessels in the area. 3 Starfleet Carrier Battle Fleets are operating in the area to protect the shipping and have seen some action, but it seems limited to rogue and overzealous Klingon ship captains in the fog of war rather than a deliberate effort to engage Federation forces. The USS Nimitz experienced minor damage to its starboard nacelle in a “friendly fire” incident from a Romulan D’deridex warbird.

Information from other sectors is mixed and confused, with worlds changing sides frequently. The Klingons employing their “hammer strike” tactics against Romulan strong points, the Romulans employing deception with hit and run tactics to harry Klingon forces and break up their attacks while sustaining little injury themselves, and engaging in large, overwhelming offenses behind Klingon lines. Still, their major supply and repair worlds in the area are cut off, forcing them to abandon wounded vessels or tow them great distances for repair, both costly choices.

Romulan forces stationed in Cardassian space have been called up, leaving only a skeleton fleet to protect their interests there. The Romulans have asked the Federation to help them protect their interests in the area, but the Federation hasn’t given them a decision on the issue yet. Meanwhile, the Cardassians are petitioning the Federation to stand aside while they “negotiate” with the Romulans for their lost worlds. Klingon forces in the Cardassian sector have become very aggressive, launching 3 unsuccessful small probing offensives against the Romulan worlds there and shooting at everything on their paths both to and from the Romulan holdings.


Star Fleet Intelligence Report:

Star Fleet Intelligence Captain sends instructions to the Captain of the USS Marathon. In it she mentions that the sabotage is a not so subtle communication from the Klingons to the Federation.

FULL MESSAGE FOLLOWS: Received via subspace message, personal communiqué for Captain’s eyes only:

(She’s a salt and pepper haired woman in her mid 50’s, linebacker build, intense eyes, looks like she used to be pretty but it now just stern and domineering) Captain, this is Captain Jessup, Starfleet Intelligence, Romulan sector. I can’t begin to tell you how disturbed we are to hear of your sabotage incidents. This corroborates a far reaching infiltration into Starfleet’s support services branch that has been under investigation for the last 7 months. We hadn’t realized how deeply some of their operatives had been hidden, and we’re positive we haven’t cleaned them all out yet. There’s every possibility that you haven’t seen the last of the sabotage on your ship yet.

You should be aware that the USS Pydna experienced some sabotage efforts, though not on the scale you encountered, and not until they were well into their mission. An Orion saboteur was found at Starbase 241. At Cardassia Prime, we believe we found another infiltrator, but this one slipped away from us before we could capture him and seems to have disappeared into the Badlands. There was extensive genetic alteration, so we’re not even sure of the race and sex of the infiltrator, but we are continuing our efforts to obtain the target.

In many ways, this is a not so subtle message from the Klingons to the Federation. We believe that these infiltrators were setup to be caught, and if the one in custody is any indication, they don’t have any deep intelligence to give us. We read the Klingon message as, “Stay off our boarders and out of the Romulan invasion or you’ll have a war on our hands.”

Indications are that the Klingons are prepared to make good on such a threat, positioned to immediately launch a strike into Federation territories with no notice and striking hard at our defensive positions. Furthermore, there seem to be stepped up efforts from their diplomats to convert a great many neutral and weakly loyal systems to the Klingon side. Above all, they are prepared to stop you at all costs and damn the consequences. Much the same thing is going on with the Pydna, though to a lesser degree. This is why you have your escort ships available to you, and we only wish we could spare you more. Good luck on your mission captain, Jessup out.”


Admiral Burtell’s Update:

The captain receives a recorded message on a private channel from Admiral Burtell:

Attention Captain, Command Crew, Chief Engineer, USS Marathon:

As a result of the sabotage done during the Marathon refit, Starfleet Intelligence, in cooperation with Starbase 234 Special Operations, has ordered a complete, MANUAL, level 1 diagnostic and component by component teardown and scan at Starbase 134 on Rigel. This will also gave Starfleet time to deliver a new warp core and nacelle upgrades to the Marathon, freshly constructed at Utopia Planitia under level 1 security protocols, and delivered by the USS Sentinel. The Sentinel along with Battle Group 33, which it serves as flagship for, arrives at Starbase 134 three days after the arrival of the Marathon.
Kindly do all in your power to prepare your ship for this process. The faster it is completed the faster we can get you back into space.

You’ll additionally be glad to know that the Warptug USS Brazos was dispatched and has recovered USS Voodoo and is en route to Starbase 134 where she should be repaired in plenty of time to deploy with you after you are again spaceworthy. All damage BG28 has suffered should be taken care of and those ships should be fully operational by the time you are.

Regards,
Branch Admiral Burtell
-———————————————————————————————
This additional message is included:

Captain Morgan, welcome back! We’re glad you made it back in one piece, more or less, and we’ll get you fixed up and back out to space ASAP. Nice work on the Ipsus crew as well. The intelligence boys are prying all kinds of things out of that Klingon crew captured on your trip back here. Nice work there as well! It seems that what you ran into was just the tip of the iceberg. I’ll have them give you a full intelligence briefing once you’re settled (see Captain Jessup’s report).

In the meantime, the PR boys have had quite a time spinning your story to the press. Prepare yourself and your senior personnel for the cameras – they’ve got interviews lined up with all of you. The intel boys will cover what you can and can’t say. Before you say anything, not my idea, out of my hands, don’t bother.

As for your ship, nice job on catching the saboteur! Hmmm, I’m not in the habit of saying ‘nice job’ this often – it’s a nice change of pace. Anyway, you’ll be down a bit. Since it seems that the Klingon operatives had the run of your ship during its refit, Starfleet ordered a complete, MANUAL, level 1 diagnostic and a component by component teardown and scan at Starbase 134. The bad news is that you’ll be down for the better part of 5 weeks under normal circumstances. The not so awful news is that because you are on such a high profile mission you’ve bumped everyone else out and have first right of refusal on all labor, parts, and specialists until you’re space born again. They’re projecting 17 days, but we’ll see. On the positive side, this will give Starfleet time to deliver a new warp core to the Marathon, freshly constructed at Utopia Planitia under level 1 security protocols, and delivered by the USS Sentinel – Admiral Sesat’s flagship – when he rolls through here with Battlegroup 33 on his way to his new posting at Deep Space K-7. The Federation Science Council wants the Marathon’s warp core for study, so looks like you’re getting a new one, and its next generation at that, complete with upgrades to your nacelles as well making you the fleet’s only TW-3 ship.

Your crew will be debarked and detained for 2 days, and all key crew members will be debriefed on the events surrounding the sabotage. Any crew that Starfleet Intelligence needs will be detained for further questioning. We will do our utmost to insure a clean, un-tampered with, loyal crew for you when you return to your mission, captain. After that, we’re granting you and your crew 5 days shore leave (within 1 system of Rigel and Starfleet Intelligence monitoring), after which I’m sure they’ll be anxious to help put the ship back together and get her ready to return to action as soon as possible. I’m authorizing the facilities on Rigel 2 for your crew who can qualify for it. For everyone else, Risa is close and I hear it’s nice this time of year. No quibbling on this captain – you and your crew may not have a chance at any R&R for quite some time. We need them off the ship anyway so we can do depressurized work for a bit.

OK, that’s mostly it; prep your officers for interviews, prepare for debriefing, have a good time and be safe and make good decisions on shore leave, then get your ship put together and back to work ASAP. Burtell out.”
-—————————————————
Computer Record: Rigel II – Need to Know Basis, Top Secret Clearance Required. Federation scientists have worked with the REDACTED. Visitors are given REDACTED. Orbiting hotels accommodate all guests and scientists visiting this world. With the advent of REDACTED but still remains at the top of the “must do” vacation lists of the rich & famous, and those who wish to emulate them.
Same entry upon clearance approval:
-—————————————————
Computer Record: Rigel II – Amusement Planet. Automatically reads the minds of visitors and presents them with their thoughts made reality, even if these realities are dangerous or deadly to the visitors. Federation scientists have worked with the AI system running the planet and managed to place some rudimentary safety protocols into its thinking. Visitors are given strong safety briefings and mental discipline training before being allowed to visit the planet, and visits are restricted to no more than 2 days, with no sleeping allowed. Orbiting hotels accommodate all guests and scientists visiting this world. With the advent of holodecks, its popularity has dropped off, but still remains at the top of the “must do” vacation lists of the rich & famous, and those who wish to emulate them.


Note: Battlegroup 33 is 4 days away from arrival at Starbase 134 at the time of the Marathon’s arrival at Starbase 134, arriving at the end of the day of the medal ceremony.

USS Marathon Upgrade Technical Review:
NEW WARP CORE: Starfleet is taking this opportunity to upgrade the USS Marathon with the FTW3 warp core from previous their FTWC-2. Whereas the FTWC-2 physically looked like a standard warp core with 2 half-sized cores attached 2/3 of the way up, the FTW3 has 3 half-sized cores arranged equilaterally roughly ½ along the main core. This is the first field deployment of the unit. Please see technical manual for full details.
4th_Generation_Warp_System_Diagram.JPG

PERFORMANCE EXPECTATIONS:
• In solo flight this core, properly configured with FTWC-3 Engines, should propel the vessel at TW10 in solo flight, a step up from the previous TW9 speeds.
• It is expected to enhance the ability of cutter ships to create STWCs, though to what degree is uncertain.
• Most impressively is its ability to operate in “expanded” mode. In expanded mode the speed is reduced to TW9, however, the conduit is substantially increased in size and capacity, allowing multiple ships to travel along with the cutter ship. The greater the number of ships traveling in the conduit the greater the instability of the conduit and the shorter the distance it can be maintained. (Note: An unstable conduit simply disintegrates dropping all vessels within it back into normal space, unlike a conduit rupture, and this outcome has been deemed to be safe for all involved after recording thousands of such destabilization events with no negative effects in live testing as well as simulations.)
• This core relies on the same ejection system as the previous model.
Disposal of previous cores: The TransWarp cores of the USS Marathon and the USS Ipsus are both being transferred to the Daystrom Institute Warp Research Annex, located in orbit of Rigel III (Chelar) for detailed research. When available, the senior engineering officers of the Marathon have a standing invitation to participate in the research being conducted there.
TransWarp_II_System_Diagram.JPG

ENGINE UPGRADE: The USS Marathon Nacelles are being refit to bring them up to spec for FTWC-3 certification to match your new warp core.
TransWarp_III_System_Diagram.JPG

STRUCTURAL INTEGRITY FIELD: The USS Marathon is receiving a new enhancement to its structural field. This is the same system being deployed aboard the Guardian Class Battleships being deployed now. It will effectively increase your superstructure points by 48%, has an independent temporary battery supply, which will be useful should help you ever find yourself in the crushing effects of the TransWarp Domain again. It’s potentially handy in a fight as well.


PRE-INTERVIEW BRIEFING BY STARFLEET INTELLIGENCE OFFICER QUINCY:
• Commander Loraine Quincy’s Pre-interview PR/intelligence briefing –
Don’ts:
• Do not discuss Klingons attacking you in the TWC, but the attack once you were out is fine to discuss in general terms.
• Do not discuss an accident of ANY KIND having to do with any TWC.
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save people in an unfortunate circumstance, comrades in trouble, that kind of thing.
• Do not discuss sabotage, infiltrators, or enemy operatives. Your ship was fully operational at all times until exiting TW Domain space, and you suffered damage in the process of escaping it.
• Romulans are not to be mentioned regarding any space combat involving BG28, or at all for that matter. You have no opinion of what’s going on in Romulan space.
• Do not taunt happy fun press. Don’t think of this as a press conference so much as a misinformation briefing for our enemies and a public image bolstering session for our Federation citizens.
Do’s:
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save comrades in an unfortunate circumstance.
• Present yourself as prototypical Starfleet personnel who care so much more about others than themselves it’s sickening.
Your objectives here are to:
• Build, or at least not damage, confidence in the TWC system.
• Keep operational information about the capabilities of your ship and the TWC system secret.
• To keep the public calm and confident in Starfleet.
• To further the image of the heroic crewbeings of Starfleet.
• As much as possible, to honor your heroic and good work.
-—————————————————
THE MEDAL CEREMONY:
As the Federation Anthem blared in the hall, ended, then repeated, and repeated, and played over and over again for the next 3.72 hours, the crew gathered in formation and the officers arrayed themselves on the Dais while the exploits of their amazing adventures (heavily edited) were read to the throngs of Admirals and up and comers gathered there to be seen by important higher ups who were also there or would know who was there. The Award was read aloud and then pinned to the chest of each officer (and simply passed out to the crew members.

GM Note:

  • Captain and crew of the USS Marathon, please update your characters with the following tour event: Parasitic Infection – you (if you had a headache), or your crew (if you didn’t).
  • Captain and crew of the USS Marathon, please update your characters with the following award: Citation of Conspicuous Gallantry. If this is your second time to receive it then add “With Cluster” at the end of it. If you have received it twice already, add “With Clusters” (note the plural clusters). If you have received it more than that refer to the following:
    4th – Clusters with Alba Leaves
    5th – Clusters with Alba Branch
    6th – Clusters with Alba Branch and Frocking
    7th – Heavy Frocking
    8th – Heavy Frocking with Cluster
    9th – Heavy Frocking with Clusters
    etc….

The Reading – Honorific: Citation of Conspicuous Gallantry
Awarded: Captain Alexander Morgan, USS Marathon, commanding (insert your name and rank here if you discover you are not Captain Alexander Morgan)
Citation: While trapped in an unknown dimension of space in the vicinity of Regulus, and enduring various distresses and failures within this space, the Captain and crew of the USS Marathon did detect, find, and rescue all surviving hands aboard the USS Ipsus escaping said inter-dimensional space and returning to Federation space, attempting to take the Ipsus in tow with her, though this ultimately turned out to be impossible. The decision to do so resulted in the recovery of five souls and the bodies of many of the crew of the Ipsus, which provided comfort and closure to their families. The warp core of the USS Marathon and data collected will be donated to Starfleet’s Space Sciences division to provide valuable scientific evidence to further the goals and aims of the United Federation of Planets. Captain Morgan is recognized for his clear thinking and positive risk taking in the face of unknown adversity, and the entire Crew of the USS Marathon is commended for their brave execution of their captain’s orders in uncertain and hazardous conditions.

Ship Honorific: Citation of Conspicuous Gallantry
Awarded: USS Marathon, NCC-72002, Captain & Crew
Unit Citation Reading: As per above.

Note: Battlegroup 33 is 4 days away from arrival at Starbase 134 at the time of the Marathon’s arrival at Starbase 134, arriving at the end of the day of the medal ceremony.

-———————————————————————————————

What Happened:

TIMELINE OF EVENTS:
-8 Days – Marathon begins moving towards Starbase 134, contacts BG28, saboteur discovered broadcasting their position, found, Nausican scouts show up, scan, and scoot. BG28 steps up to warp 9. – Previous Adventure Log
-7 Days – Klingons arrive to attack Marathon, then more of them, Marathon kills 2 (including ship with the USS Bull Run’s sensor pod on it’s nose), BG28 meets up with Marathon, fighting and escaping. – Previous Adventure Log
-6 Days – USS Ob Warptug arrives, takes Marathon under tow, fleet moves faster but USS Voodoo badly mauled and has to be left behind (all crew rescued).
-5 Days – Harassed by Klingons and Nausicans.
-4 Days – Harassed by Klingons and Nausicans.
-3 Days – Harassed by Klingons and Nausicans.
-2 Days – Harassed by Klingons and Nausicans.
-1 Days – Harassed by Klingons and Nausicans, Starbase 134 picket joins BG28 and Klingons and Nausicans break off their attack.
0 Day – Arrived in Rigel system, met by honor guard of 67 Starfleet starships and many 144 fighters (gross!), who escorted the Marathon into system, delivered her to Starbase 134, and put her into repair yard Alpha 3. Complete with a congratulatory message from Admiral Uunaimed (human, male) of the USS Random (Galaxy III) flagship of the Starbase 134 picket) in full dress uniform (along with a miffed and uncomfortable looking crew in the background). The crew was politely disembarked onto a waiting personnel transport (space bus) and landed at Starbase HQ on Rigel IV where they were assigned quarters. Enlisted were assigned private officer grade quarters, officers received VIP quarters. The Command staff and Department Heads are given rooms in an admiral/ambassadorial suite complete with a 3 living areas, a staff room, and 2 conference rooms, Star Fleet Intelligence officers posing convincingly as serving staff. All crew members are separated from their luggage and belongings. Lt. Th’azyron bemoans the separation from his weapons, all hidden knives and phasors having been confiscated from him upon exiting the transport. Senior officers receive agenda message for upcoming events and are otherwise left to mingle among themselves until escorted to their quarters and locked into them. All crewmembers are locked into their quarters and are isolated.

+1 Days: The following morning, going in order of rank from high to low (except for the Ferengi whose interrogations go for a full 2 days and ‘alternate techniques are used’ as they are psionically resistant, their files receive the addition, “Person Of Interest”), the Captain is interrogated for 2 hours using invasive psionic techniques and being questioned while in that state. Surprising many, he is declared clean, as are all other senior officers. Following the senior officers interrogation sessions, they find they have been moved to other quarters, still VIP level, but each suite has adjoins common room where all can meet and interact.

+2 Days: Interrogations continue, all Civilian Specialists are cleared as are all but 1 officer, and the interrogation teams (35 of them) are working their way through the crew. By the end of the day another 4 (5 total) potential threats are found, removed, never heard from again. The psionically sensitive among the crew note that during their ‘interviews’ as many as 12 other psi’s or sensitives were present nearby and ‘tuned in’.

Commander Loraine Quincy joins the officers and gives them their pre-interview PR/intelligence briefing for the upcoming press conference many of them didn’t know was going to happen and now get to dread. He told them the do’s and don’t as follows:
Don’ts:
• Do not discuss Klingons attacking you in the TWC, but the attack once you were out is fine to discuss in general terms.
• Do not discuss an accident of ANY KIND having to do with any TWC.
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save people in an unfortunate circumstance, comrades in trouble, that kind of thing.
• Do not discuss sabotage, infiltrators, or enemy operatives. Your ship was fully operational at all times until exiting TW Domain space, and you suffered damage in the process of escaping it.
• Romulans are not to be discussed. You have no opinion of what’s going on in Romulan space.
• Do not taunt happy fun press. Don’t think of this as a press conference so much as a misinformation briefing for our enemies and a public image bolstering session for our Federation citizens.
Do’s:
• The crew of the Ipsus are heroes and not to be portrayed in any other light.
• The mission was a Starfleet rescue operation mounted to save comrades in an unfortunate circumstance.
• Present yourself as prototypical Starfleet personnel who care so much more about others than themselves it’s sickening.
Your objectives here are to:
• Build, or at least not damage, confidence in the TWC system.
• Keep operational information about the capabilities of your ship and the TWC system secret.
• To keep the public calm and confident in Starfleet.
• To further the image of the heroic crewbeings of Starfleet.
• As much as possible, to honor your heroic and good work.
The officers discuss and debate and formulate their press strategem. While they are doing this, most of their personal belongings are returned to them. By end of day, all personal effects are returned.

+3 Days: Everyone puts on their dress uniforms (which is basically a dress) and prepares for their award ceremony. (see Above)
Following the ceremony (10:00am local time) the senior officers enjoy a very dry and tedious 4 hour reception. There they meet the top local brass including Admiral Burtell, dignitaries, members of the press, high-level business people, and defense contractors. (It’s really a LOT of fun…hors d’oeuvres, drinks, lots of press, lots of brass – the perfect cocktail to destroy a career, or make one). No carousing are blown as far as we know (can’t say the same for all the admirals), and all is well. Finally, at 2:00pm the press conference gets under way.
MEET THE PRESS – Interviewed by:
• Wolf Sanders (human male) of FNN (Federation News Network)
• Sorva (vulcan male) of The Rational Enquirer (Information stripped of emotionalism and mysticism)
• Mott Fruis (bolian female) of The Freedom Group (syndicated talk show)
• Stanton Meriwether Haventhorp (human male) of Modern Spacefarer Magazine (For private ship owners, promoting the interstellar yachting lifestyle)
• Jali Moenserg (denobulan female) of The Plain Truth (dumbing down the news for the average Joe since 2219)
• 20 other miscellaneous newsletters, publications, talk shows, blogs, and public rumor mongers of various races and sexes
In a private reception for the senior officers, they are officially “pinned” (again, it’s a photo op) with their awards in front of a small audience (all at the Fleet Captain level and above, many of them Starfleet Intelligence officers). Afterwards, the members of the press corps of Starbase 134 are introduced. The media feeding frenzy gets underway. The incoherent 1st Officer (only entirely drunk) is the highlight of the show.

Press Conference Interview Questions:

1. Captain:
A. Stanton Haventhorp of Modern Spacefarer Magazine – How did you know you weren’t in normal space anymore?
B. Jali Moenserg of The Plain Truth – What was it like in that strange dimension you were in?
C. Mott Fruis of The Freedom Group – Did anything happen to you and/or the crew while you were in there? Did you see any interesting creatures or make first contact with anyone?
D. Wolf Sanders of FNN – How did you find the Ipsus?
E. Wolf Sanders of FNN – How did you buoy up the spirits of your crew when you learned the grisly fate of your sister ship?
F. Wolf Sanders of FNN – Will you be returning to this new area of space for further exploration? Follow up: Do you know how to return to this new part of space?
G. Sorva of The Rational Enquirer – With this being your first command and being so new to the captain’s chair and in such a high stress situation, how did you get the crew to follow your orders?
H. Can we see your new medal? Can you tell us how you felt when you received it please?
2. 1st Officer (too drunk to answer), Tactical Officer:
A. Sorva – Did you agree with your captain’s decision to fly into an unknown dimension of space?
B. Wolf – If you were in command, what would you have done differently? Follow up: How often do you find yourself at odds with your captain like this?
C. Stanton – At any point, were you close to needing to relieve the captain of command for the danger he put the ship and crew in?
D. Jali – What did you feel when the Ipsus first came into view?
E. Mott – How did you grieve for the crew of the Ipsus and help the crew of your ship to come to grips with the losses?
F. Sorva – Considering your situation and ship’s condition, was the effort to attempt to rescue the Ipsus logical?
G. Mott Fruis – I had a brother that served on a dangerous Starship a few years ago and he nearly got killed on several occasions. Is that why you serve commander – for the thrill and adventure of it?
3. 2nd Officer:
A. Jali – What does a 2nd Officer do? No, I mean in a crisis situation like this – are you like a spare 1st Officer?
B. Wolf – What did you do during the rescue operation?
C. Mott – Were you expecting trouble from the survivors, or maybe alien intruders, or anything like that?
D. Stanton – Was it hard to keep your people calm and focused during the rescue, or was there some panicking?
E. Stanton – In the fight with the Klingons, after you returned to real space, how badly were you outmatched?
F. Did the Klingons damage the Marathon? Is that why you’re in the ship dock for repairs?
G. Sorva – Do you feel the decisions of your captain to rescue the Ipsus were commendable or foolhardy considering you could have all been killed in the attempt?
4. Chief Engineering Officer:
A. Wolf – How long has Starfleet known about this new dimension of space and why are we just hearing about it for the first time?
B. Mott – Are there plans to return to this new dimension, and if so how will you do it?
C. Jali – First, you’re a genius, and now a hero. I have to ask, and our audience is dying to know, are you currently seeing anyone?
D. Sorva – Were you able to learn anything that will help refine the work of of Dr. Sethis of the Vulcan Science Academy, whose equations make TransWarp Conduits possible?
5. Ops/Helm Officer:
A. Stanton – How did you know how to fly in that new dimension? Was everything weird, like backwards, upside down, or reacting funny, or something like that?
B. Jali – Would you like to go back and explore it further?
6. Medical Team Leader:
A. Jali – Have any of the crew grown strange appendages, odd skin, changes to their foreheads, or developed amazing new abilities as a result of exposure to this new area of space you were in?
B. Wolf – How are the surviving crew of the Ipsus doing? Is there any chance we can talk to them?
C. Wolf – What was the interior of the Ipsus like?
D. Stanton – Was it dangerous getting on board her? How did you do it?
E. Jali – Weren’t you afraid of getting germs or parasites or something from them? I mean, they’ve been here in unknown space for months – there could have been anything over there!

How It Turned Out

The publicity ploy of Starfleet PR of holding a press conference with the senior officers of the Marathon has had mixed results:
• Wolf Sanders of FNN, human, male (Federation News Network) – Gives a straightforward accounting of the fiction that Starfleet Intelligence spun, painting the crew as heroes and the work as nail-biting drama to save the desperate, but oh-so-brave, survivors of the Ipsus, pulling off the amazing feat of recovering the ship and deceased crew members of the ill-fated ship as well. There’s talk of a movie of the week with Jason Spurgeon (vid star and sexy hunk) playing the captain and Marvin Grayson (comedic genius) playing his comic relief as the First Officer.
• Sorva of The Rational Enquirer, vulcan, male (Information stripped of emotionalism and mysticism) – Gives a biting article on the ill-advised attempt with a high likelihood of failure and loss of yet another ship and crew under the command of an untested captain with a yes-man first officer which succeeded purely by random chance and the scientific and engineering efforts resulting from the intensive study of the theories of Dr. Sethis of the Vulcan Science Academy. The human instinct to venture into every possible place and situation they can has once again ended in near disaster, only averted by the most unlikely perversions of chance.
• Mott Fruis of The Freedom Group, female, bolian (syndicated talk show) – The Klingon attack against the Marathon occupies nearly 70% of the broadcast with each of the panel members having a different take on what it could mean to the security of the boarder planets, all of them bad. The potential for changes in the physiology and psychology of the crew and potential first contact with new, threatening, species take up the remaining time allowed. A very brief spot in the beginning and end of the show discuss the heroic rescue, the plight of the Ipsus, and the glory seeking aspect of Starfleet (showing the crew getting their medals as they say this).
• Stanton Meriwether Haventhorp of Modern Spacefarer Magazine, human, male (For private ship owners, promoting the yachting lifestyle) – Starfleet, as always, is jealously guarding the information that could be critical to the captains and crews of civilian craft using these STWC’s. However, that Starfleet has the capability to not only enter this domain, but to find and effect a rescue is encouraging. At this time, the recommendation of Modern Spacefarer is to use the STWC network only as necessary, but with reasonable confidence.
• Jali Moenserg of The Plain Truth, female, denobulan (dumbing down the news for the average Joe since 2219) – The crew is so brave, their mission so AWESOME, this new area of space so mysterious, and such an eligible BACHELOR on board as well! A detailed description of how the senior crew, especially the chief engineer, looked in their dress uniforms, how they plan to go back and, “just rescue everyone ever who got stuck in there”, and hints at how a certain commander, who is still single and shall remain unnamed, may have been flirting with a certain reporter.
• 20 other miscellaneous newsletters, publications, talk shows, and public rumor mongers – It seems obvious from a general reading/viewing/listening to the material coming from the press conference that someone leaked information about people in TransWarp space turning into lizards (unfounded, denied by Starfleet Intelligence and Starfleet Medical) and a rumor regarding discord among the crew, in particular the first officer and the captain, has been circulating. The sources of both of these is under investigation by Starfleet Intelligence. Starfleet Intelligence is generally pleased with the press conference regarding their objectives, misinformation and information dilution/deflection, and issues they wished to keep secret.
:
-————————————————————

Admiral Sesat and Battlegroup 33 arrives at Starbase 134 at the end of the day of the medal ceremony. He entered the hall where the medal ceremony was held and the remnents of the party were still enjoying the food, drink, and political maneuvering. He approached several very senior admirals, boiling mad, and had a conversation at a low volume that eavesdroppers would describe as ’couldn’t really hear much, but there was a lot of hissing’. Spotting the Captain in the room, he composed himself and marched over to make the obligatory congratulations and introductions. He told the Captain that he had his new warp core on board, that the Captain should be very grateful to him for bothering to use his battleship as a transport, and that he’s better put it to good use. Then he took the Captain by the arm and walked him into a small side room where they remained for roughly 4 minutes and talked about who knows what? Admiral Sesat then left the room and the event, beaming back to his flagship. Admiral Burtell then briefly entered the room, emerging 2 minutes later and looking very troubled. The Captain exited the room and twirled his mustache.


SHORE LEAVE

+4 Days: Begin shoreleave (hold on to your butts!)
Several officers choose to go to Rigel II, including the Chief Engineer, and all of them are able to pass the discipline training and get to go down to the planet and enjoy the amusements to be had there – except the Chief Engineer. The events that occured on Rigel II are classified and can only be found in the personal journal’s of the participants and we shall examine this time no more.

The remaining officers (including the Captain), and after 2 days of struggling with discipline training the Chief Engineer, head to Risa. There are many events that happen on Risa, including a Vulcan pon farr, but what happens on Risa stays on Risa and we shall examine this time no more.

+9 Days Shoreleave ends (release your butts!)
The Chief Engineer gets invited to the Daystrom Institute on Rigel III, bargains to bring 2 people with him, and offers these slots to his assistant (who would have been invited anyway) and the Captain.

Tired of the drinking issue and eager to test his ability to get anything and everything he wants, the Captain had his 1st Officer transferred off the ship and promoted his Chief Engineer (who had just become a chief engineer and held the position for only a few days now) to that position. He promoted the Assistant Chief Engineer, Lt Christina Williams (his former girlfriend that he seems to still be interested in) to Chief Engineer, and he made his tactical officer, Lt. Th’azyron, his new second officer. A new Assistant Chief Engineer is now being vetted to join the crew.

Comments

friendlypickle

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.