Yeager SC Mission 01: "Hidden Agenda"
Captain Joseph Valiant recording:
I’ve sat here and pondered over where to begin this report. I guess because all records from the first half of the Yeager’s mission was lost when the Computer core was infected with a rather destructive virus, I’ll start over from the beginning, back before I took command of the Yeager.
It all began about 8 months ago when Captain Luke Johnson, a friend of mine, was given Command of the USS Yeager shortly after the Borg conflict.
The Yeager’s first mission was simple, go to the McClin system and investigate some pirate attacks and get to the bottom of it. Intelligence was sketchy at best on the situation but it didn’t appear severe enough to have to send out anything larger then a scout to investigate.
The Yeager arrived at the McClin system only to find 3 disabled freighters. They were attacked shortly before the Yeager arrived by pirates. After establishing communications and discussing what had happened with the Captain of the freighters, the Yeager was nowhere closer to figuring out who was behind the attacks.
To get some much needed answers Captain Johnson decided to set the Yeager up as a decoy to lure them into a trap so the crew could board the pirate’s ships and get prisoners and information.
Things didn’t turn out as planned however. While setting the Yeager up as a decoy worked, everything else didn’t. The Yeager was ambushed by roughly two dozen fighters, piloted by experienced pilots; the Yeager didn’t stand a chance. After only a few moments into what would be a short battle, the Yeager lost its shields, engines, and weapons.
The ship being completely vulnerable, the Yeager was ordered by the lead attacking ship to stand down and prepare to be boarded.
Captain Johnson gave into their requests, that way they wouldn’t just destroy the ship, yet he didn’t give up. He ordered the crew to evacuate the areas the pirates would likely board first, and ordered them to defend the ship from boarders.
Thankfully the crew of the Yeager was able to put up a better fight against the boarders then the ship against the pirate ships out there in space. The Yeager crew was able to stop them from taking over the ship, but wasn’t able to stop them from trashing and stealing anything of value before they gave up the assault and left.
The plan wasn’t an absolutely disaster however, the Yeager was able to stun a few pirates and take them as prisoners.
The Security department, headed up by Commander Balak, quickly began interrogation of the Prisoners; they weren’t to forthcoming however. Getting impatient, Captain Johnson himself interrogated one of the prisoners. After only a very short time of interrogating the prisoner, Captain Johnson got the information he needed; coordinates to the main sector these pirates were operating out of.
Considering his mission was to gain intelligence, and shut down these pirates Johnson ordered the ship to go to radio silence, set course to the coordinates given to him by the prisoner.
Arriving there it quickly became evident that it was a trap. The Yeager was ambushed, and this time it appeared there was some inside help. With a single volley if missile fire the pirates were able to lower the ships shields, which suggests someone gave them the ships shield modulation frequency.
With the shields down, the pirates boarded the ship, again. Catching the crew completely unaware they were able to take over the ship. At the same time, several crew members chose to mutiny and join up with these pirates. The ship’s Chief Tactical Officer, Commander Laine, was one of them.
One could only guess these pirates were on a time schedule by the way they kept their attention on the time. Reason being was unknown; however it was clear that their time was running out.
With their time now out, the pirates beamed out, taking Captain Johnson as prisoner with them.
As soon as the pirates beamed out, every station, every system on the ship overloaded; the ship was infected with a rather destructive computer virus.
Now without life support, warp engines, or communications, the Yeager was left adrift in space to die.
Thankfully for the crew of the USS Yeager, the USS Drake had found them, and set an intercept course. It became clear at that point that the Drake was the reason the pirates left in such a hurry. Knowing the Yeager could no longer function and support its crew the Drake beamed the remaining crew of the Yeager aboard, and took the ship in tow to its next stop Starbase Alpha.
That’s where I come into the picture. With Captain Johnson kidnapped by these pirates, someone had to rescue him. Star Fleet thought I was the best choice for the job, seeing that myself and Luke Johnson grew up together and knew each other quite well. So Star Fleet gave me command of the USS Yeager with orders to find Captain Johnson and rescue him, capture the other mutineers and capture them if possible, and to find where these pirates are operating out of.
After repairs were completed to the damaged done to the Yeager the mission before, we left space dock and headed to where the Yeager’s previous mission really began, the McClin system.
On our way to the McClin system, the Yeager was temporarily assigned a new mission, to assist in the destruction of a threat to the security of the federation. The battle was quite intense, but Yeager along with a large portion of the First Fleet, successfully took on an Orion Cartel.
Once minor repairs were conducted the Yeager set a course back to the McClin system.
While in route to the McClin system the Yeager began experiencing unusual problems, such as crew members being transported to another section of the ship, the start of a launch sequence of a shuttle, and the ship mysteriously dropping out of warp. At the time the problems didn’t really warrant much of an investigation, after all the Yeager just recently went through a mass of repairs caused from damages from its last mission, and the flaws in the system could be blamed on that. Little did we know an unknown entity that appears as green goo was behind all these problems. Arriving at the McClin system we began to run our scans. Suddenly a subspace rift opened up. My original reaction was to seal the rift, never giving though of what else it could have been. Thankfully before I gave the order to destroy the rift the entities at work manage to make contact with us telepathically, telling us they wished to go home. This life form wasn’t a linear life form, very similar to the worm hole aliens in the Bajoran wormhole, and somehow after making contact, everyone began to see flashbacks of their life. For whatever reason, probably them knowing I was the Commanding Officer of the ship, they made a special connection with me. I had the similar flashbacks as everyone else but in addition to that I began to see the future events of my life. That wasn’t all however, they even gave me an insight as to what happened during this ships last mission. No doubt it will be a great help, and they knew it. After the flashbacks ended I gave the order to take the ship into the rift. I’m not totally sure how I knew it would allow them to return to their home without destroying the ship, but I think during the flashbacks they were also able to communicate with me on another level completely, I guess I’ll never know for sure.
With the entity gone, and systems back to normal we set a course back to the McClin system.
Shortly after we got rid of the entity, we were faced with another problem, a saboteur. I can only guess this saboteur is someone sympathetic to these Pirates that have captured Captain Johnson, and that the saboteur is attempting to end our rescue mission early. He nearly was successful. Using his skill as an Engineer, he managed to overload a series of power conduits, which exploded which left us with a rather big hole in our hull near engineering.
He didn’t stop there however; next he attempted to kill both the Chief of Security Commander Balak, and our Chief Engineer Lt. Commander Obuszewski. Thankfully his attempts failed.
Knowing if he would stay on the Yeager he would end up being caught the saboteur stole a shuttle and left the ship.
Using the Yeager’s powerful long range sensors we allowed him to think he had got away by putting the Yeager well enough away from the shuttles sensor range, yet still close enough to be in our sensor range.
Little did he know he lead us right to his destination, Volon II.
With the Yeager in orbit around Volon II, and an away team was sent to the planet to investigate where our stolen shuttle was, and were the man who stole it was so we could subdue him. Little did anyone realize, or even think of, was this planet wasn’t all to liking of the federation, and Star Fleet. I guess in our biased opinions us Star Fleet officers we feel we’re accepted everywhere…yet this time it around proved to serve as a lesson to a lot of us. Not only was the away team not accepted among the locals, they were despised, which didn’t seem to help the investigation any. In the end I feel it was the locals hatred of Star Fleet that lead the away mission to failure. The Yeager wasn’t able to recover its stolen shuttle, nor was it able capture the man who stole it, former Engineering Lieutenant, Jean-Rene Lacardo.
During the away teams time on the planet they were contacted by a Trill Ambassador, who requested the aid of Star Fleet to transport her to the nearest Starbase. I granted her request and she was beamed aboard along with the rest of the away team when they returned after things got a bit sour on the planet....
Once the away team was on board, I wanted to go speak to the Ambassador in person, however almost as soon as the away team was beamed aboard a starship approached the Yeager it was the massive pirate ship that attacked the Yeager during its pervious mission. I was in my quarters at the time, waiting for the away team to arrive, when I got the message to come to the Bridge.
Stepping on the Bridge, I was greeted by a man on the view screen who was hidden by shadows from his own Bridge. With a voice that was familiar to me, the man arrogantly taunted. After a few minutes the man stepped out of the shadows he was standing in, to reveal his identity. To everyone’s surprise, it was Captain Luke Johnson, the very man the Yeager was sent to rescue. Johnson was a traitor.
Wanting to stop the Yeager’s investigation into finding these Pirates, Johnson demanded I hand the ship over to him. Having a duty to Star Fleet to not allow sensitive materials to fall into hostile hands, I refused. Not liking my reply Johnson and his group of pirates attacked the Yeager.
After a short battle which resulted in numerous hull breaches, the Yeager was able to disable to pirate warship. Some would say it was luck, others would say it was skill, but none the less as tiny of a ship the Yeager was, it managed to disable a warship.
Though the warship was disabled its shuttles weren’t, and one managed to escape. The shuttle had Johnson and his senior staff on it. Before the shuttle left a self-destruct sequence was activated on the warship. I ordered the Yeager to get to a safe distance, and the Yeager managed to just before the warship exploded.
During the battle the Yeager sustained enough damage to not be able to go to warp. Being unable to arrive at a starbase in a reasonable time on its own, the Yeager requested the assistance of the USS Drake to tow us back to Starbase once again.
I must say that I feel this mission was a complete failure. We weren’t able to complete any of our intended objectives, Johnson whether he was a Star Fleet officer or not was not recovered, nor were any of the other mutineers. We were also unable to find any clues on where the pirates are operating from.
The price for this failure was too high; too many good people lost their lives, and for what…absolutely nothing…
I can only hope sometime in the future I can make it up to those people who lost their lives, and bring these pirates to justice.
End Mission Summery Log.
Excerpts from Captain Joseph Valiant’s meeting with Rear Admiral Benestad following the mission:
Captain Joseph Valiant Commanding Officer USS Yeager:
Jos nodded once again, to acknowledge what the Admiral said. Instead of getting refreshments, Jos handed the Admiral the PADD he was carrying, and sat down in the chair that was in front of the Admirals desk.
“Well Admiral, to summarize the mission I would say it was a failure. The Yeager wasn’t able to bring back Johnson. Though I don’t feel it was our fault, we were sent out on a search and rescue mission, when in reality this mission was more of a search and capture mission. We found him, though things weren’t as we thought they were.
To be honest sir all our intelligence for this mission was wrong. We were played, and preyed upon.
Reports said Captain Johnson was captured. What really happened Admiral, was Luke Johnson staged his own kidnapping, and betrayed Star Fleet to join this group of pirates. He openly admitted so sir. He said the only intention he had for commanding the Yeager was so he could give it over to these pirates, or whatever they are.
The problem is sir; I don’t think this is just a small group of pirates. They seem very organized, they seemed more like what the Maquie where during the Dominion war then pirates Though in the end, the Yeager’s mission was to bring back Johnson. Whether he was a prisoner or not, we didn’t accomplish the mission.”
Jos paused for a minute and then continued.
“Another ship perhaps could have done the job, maybe one that was more suited for combat. Because in the end I think it was the lack of offensive abilities that allowed Johnson to escape. When we found Johnson he demanded we surrender. I refused, and they opened fire and attempted to destroy us.
The ship we were fighting against out manned and out gunned us, it was by shear luck we survived. We could barely keep ourselves alive let alone capture the Captain of the warship…”
RAdm Rasmus Benestad 1st Fleet Commander StarBase Alpha:
Rasmus leant back in his chair as he listened to the report. He listened to the Captains reasons for the failure though in one sense they had now determined from the report that Johnson was actually a traitor and part of an organized group. The codes had all been changed months ago, and they would just have to accept that someone senior who had knowledge of the Fleet procedures and abilities had gone rogue. He would have to deploy additional ‘special assets’ to see what he could do about that aspect. However there remained the nature of the report.
He put the PADD down on his desk without reading it – he’d do that later. What he always placed a lot of reliance on was his gut feeling on the person sitting infront of him.
In a calm and considered voice he asked his nest questions:
“Okay Captain. You have mentioned several aspects of the mission that are of course of concern to me. During your mission can you tell me when you first detected Johnson, and what your ships condition was at the time. I also cannot recollect a request for additional fleet support from yourselves so were you discovered before you found Johnson, or did you attempt a recovery on your own?”
Captain Joseph Valiant Commanding Officer USS Yeager:
Jos sat in his chair, almost nervously. Somehow these debriefings always felt like an interrogation, and he always felt as if he was defending what he had to do or what happened.
“Well Admiral, during our search for Johnson he found us, or did we find him…” Captain Valiant said his voice showing his puzzlement on the subject, “Its hard telling to be honest Admiral. What happened, from my point of view, was we found a few leads, well actually we had another traitor still on the Yeager and he stole a shuttle. The Yeager followed him to the planet of Volon II. Johnson’s ship was in orbit there, but we didn’t know it at the time. He was in a polar orbit which combined with any jamming capabilities, Johnson’s in-depth tactical knowledge of Federation ships, and his knowledge of the systems on the Yeager, must have allowed him to mask his presence in the system. I guess we could have contacted the local government to ask them about any ships that had entered the system, but we were trying to mind our own business and not arouse any suspicions as to why we were there. We knew that the person who stole the shuttle had a reason to be there, and I didn’t want to alert any of the authorities in the area, I wasn’t sure if they weren’t being paid off by these pirates or not. So I wasn’t going to contact the local government unless they contacted us first.”
Jos paused, he knew where this was going, and what the Admiral was really trying to figure out, the admiral was trying to figure out if the mission failure it was his fault or not.
“Sir, I know how this must appear…it looks like it was all staged once again, perhaps its was, I’ve known Johnson for years…he is quite intelligent, worked for Star Fleet Academy teaching several different tactical classes, he knows how a Star Fleet Captain thinks, and probably used that against us. But once again, I didn’t know who was behind all this, I thought this was a rescue mission and treated it as such. Following acceptable leads until we found what we were looking for. I didn’t realize the true nature of our mission until it was too late, had I known, I wouldn’t have put the Yeager in the position it was in.”
Valiant paused once again, this time giving himself time to reflect on what he had just said.
“I must say Admiral, when looking back I did learn a valuable lesson. I learned that something’s aren’t as they appear, and should learn to think ahead based on that fact, instead of thinking ahead on what I think or have been told is happening.”
Contents
Captain's Logs
Capt Luke Johnson
Stardate 20308.07
Stardate 20308.07 Captain Luke Johnson recording
The Yeager’s mission orders were simple, track down and stop pirates operating in the McCin system, Star Fleet however didn’t have much Intel on the situation, other than what a few freighter captains had said, even then that information was sketchy at best.
A few days out of space dock we arrived at our destination only to find these pirates had attacked again, this time disabling 3 transports. Two of the three ships had lost communications, and contact had to be made, so I sent over an away team to each of the two transports to find out what happened and to assist in repairs. In the mean time I contacted the ship able to receive communications. I didn’t have much luck finding out what happened, as the Captain wasn’t very forth coming with information, but my crew on their away mission did find something out, they heard rumors that the Maquie were behind these attacks, but rumors aren’t enough. I have to have more concrete evidence, something more than rumors, and speculation, and sketchy intel from freighter captains. I need something I can work with. That’s why I’ve decided to set the Yeager up as a decoy. We’re going to hang the Yeager there as bait and hope these pirates take it. If they do, we’ll attempt to board their ships and take as many prisoners as possible, so we can get information from them. While this tactic is extremely risky, I’m confident the crew can handle whatever these pirates throw at us.
End Log.
Stardate 20311.22
Stardate 20311.22 Captain Luke Johnson recording
The mission thus far has been anything but perfect. Star Fleet should have known better than to send out a scout ship to do the job of that of a ship much bigger.
We set the Yeager up as a decoy, and from there everything went down hill. While setting the ship up as a decoy seemed to work, the overall plan didn’t. The plan was to board their ships and capture them; ironically it happened the other way around. They attacked us like a swarm of bees. This poor scout ship never stood a chance against 23 fighters, crewed with experienced pilots. It was only a short time into the battle before we lost our shields, engines and weapons, leaving us completely vulnerable.
Knowing that we couldn’t fight, or retreat, I gave into their demands and ordered the Yeager to stand down. They ordered us to come to a complete stop and prepare to be boarded. I had no choice but to let them…but that didn’t mean I was just going to just let them trample all over us.
Knowing the bridge and engineering would be the first place they would beam in and try to capture, I ordered everyone to clear the bridge, and to set up a command post in the Security Office.
Moments later the raiders boarded us, and wreaked havoc on this poor ship. They stole or damaged anything they could, and left the ship a mess. If it weren’t for Commander Balak’s security forces, things could have easily gotten worse.
Luckily the raiders were on a time schedule, and left on their own free will, but before they left, we managed to capture a few of them.
Commander Balak quickly went into interrogating our prisoners which I think he, being a Klingon, enjoyed. Our prisoners though weren’t too forthcoming with information. Growing impatient, I went in and interrogated one of the prisoners personally…I guess I could ask the right questions, as the man gave me exactly the information I wanted.
Right now, as it stands, I’m planning on using the information that this raider gave me, and attempt to get some intelligence on what their operating out of. With any luck Star Fleet will be able to use this information and shut down their operation for good.
On another note, the ships Chief Engineer, Lt. Commander Prolog is no longer with us. During the battle the Lalya, one of the transports we set up the decoy with and the ship Prolog was helping repair, jumped into warp mid battle, taking our CEO with them to Star Base Charlie. With the ship in dire need of a CEO to assist with repairs, I reluctantly changed the command structure of the Yeager, and demoted Commander Donaghue to the position of CEO. That left the position of First Officer open. So when I contacted Star Fleet to send us supplies so we can conduct our own repairs, I asked for a replacement. They sent me Commander Flynn, a former pupil of mine from the Academy.
I can only hope the rest of our mission is more successful than our last half.
End Log.
Cdr Flynn
Stardate 20401.12
Stardate 20401.12 Acting Captains Log, Cdr Flynn Recording
What a way to make a first impression. I had just arrived on the USS Yeager as the new First Officer and things pretty much went wrong.
I met with Captain Luke Johnson and he decided to chase after the pirates once the crew had put the Yeager back together. I suggested we at least contact Star Fleet, but he seemed against the idea. He thought the pirates would know what we were doing.
Shortly afterwards a large pirate ship attacked us, they took out our shields with their first shot. They then beamed aboard and started to take control of the ship.
I was knocked unconscious during the events and was filled in by the other senior officers. While I was out, the pirates took Captain Johson with them when they left in a hurry.
I believe that these pirates are the Maquis, but I'm not sure.
Capt Joseph Valiant
Stardate 20404.26
Stardate 20404.26 Captain Joseph Valiant USS Yeager recording
After several months out of active duty, I’m finding it rather hard being back in Star Fleet. After my last mission, the battle against the Borg, I never wanted to be on a starship again, let alone commanding one, but Star Fleet left me really no choice, so I shall do my job to the best of my abilities.
The purpose of me being called back is to assist the Yeager on its mission to find its former Commanding Officer, Captain Luke Johnson, who was taken during a raid on the ship during its last mission. I guess Star Fleet feels that with Luke being a close friend of mine since my early childhood, I can possibly notice small clues that can help further the investigation and get the Captain back before these Pirates get bored with him…
There’s a catch to all this though, there are no records from last mission, not even so much as a Captains Log survived. From the reports I’ve read from Star Fleet, these Pirates that kidnapped Captain Johnson, infected the Yeager’s computer core with a horrific virus, that literally fried the computer core, destroying everything contained within it. Because of that the only thing that I can go by right now is the crew’s knowledge from last mission, and any evidence left floating in space. That’s why I had the Yeager set course to were its previous mission first began, the McClin system, I figure that’s the best place to start.
On our way to the McClin system, the Yeager was temporarily assigned a new mission, to assist in the destruction of a threat to the security of the federation. The battle was quite intense, but Yeager along with a large portion of the First Fleet, successfully took on an Orion Cartel.
After a few minor repairs were conducted after the battle, the Yeager set course back to the McClin system, where we’re currently en route too.
I must say I’m rather nervous, I can only hope that when we get there that we can find some lead to go on.
End Log.
Stardate 20407.07
Stardate 20407.07 Captain Joseph E. Valiant USS Yeager recording
A lot has happened since my last entry. While in route to the McClin system the Yeager began experiencing unusual problems, such as crew members being transported to another section of the ship, the start of a launch sequence of a shuttle, and the ship mysteriously dropping out of warp. At the time the problems didn’t really warrant much of an investigation, after all the Yeager just recently went through a mass of repairs caused from damages from its last mission, and the flaws in the system could be blamed on that. Little did we know an unknown entity that appears as green goo was behind all these problems. Arriving at the McClin system we began to run our scans. Suddenly a subspace rift opened up. My original reaction was to seal the rift, never giving though of what else it could have been. Thankfully before I gave the order to destroy the rift the entities at work manage to make contact with us telepathically, telling us they wished to go home. This life form wasn’t a linear life form, very similar to the worm hole aliens in the Bajoran wormhole, and somehow after making contact, everyone began to see flashbacks of their life. For whatever reason, probably them knowing I was the Commanding Officer of the ship, they made a special connection with me. I had the similar flashbacks as everyone else but in addition to that I began to see the future events of my life. That wasn’t all however, they even gave me an insight as to what happened during this ships last mission. No doubt it will be a great help, and they knew it. After the flashbacks ended I gave the order to take the ship into the rift. I’m not totally sure how I knew it would allow them to return to their home without destroying the ship, but I think during the flashbacks they were also able to communicate with me on another level completely, I guess I’ll never know for sure.
Right now the over all condition of the Yeager is good. We haven’t suffered any damage, and with the entity gone, hopefully our systems will run better, and we’ll be able to move on with our search for Captain Johnson.
End Log.
Stardate 20408.03
Stardate 20408.03 Captain Joseph E. Valiant USS Yeager recording
There’s no such that as peace and quite on the USS Yeager. Shortly after we got rid of the entity, we were faced with another problem, a saboteur. I can only guess this saboteur is someone sympathetic to these Pirates that have captured Captain Johnson, and that the saboteur is attempting to end our rescue mission early. He nearly was successful. Using his skill as an Engineer, he managed to overload a series of power conduits, which exploded which left us with a rather big hole in our hull near engineering.
He didn’t stop there however; next he attempted to kill both the Chief of Security Commander Balak, and our Chief Engineer Lt. Commander Obuszewski. Thankfully his attempts failed.
Knowing if he would stay on the Yeager he would end up being caught the saboteur stole a shuttle and left the ship.
Using the Yeager’s powerful long range sensors we allowed him to think he had got away by putting the Yeager well enough away from the shuttles sensor range, yet still close enough to be in our sensor range.
Little did he know he lead us right to his destination, Volon II.
Currently the Yeager is in orbit of Volon II, and we’re going to attempt to capture this saboteur, and gain any information we can about these pirates from those residing on the planet. I can only hope that this saboteur’s actions will lead us even closer to finding my friend Captain Johnson.
End Log.
Stardate 20410.30
Stardate 20410.30 Captain Joseph E. Valiant USS Yeager recording
Thankfully this is the final log regarding this mission. While it’s a mission I wish I could forget, however I don’t believe I’ll ever be able to.
So much has happened since my last log entry, so much to cover, so let be begin where I last left off.
The Yeager was in orbit around Volon II, and an away team was sent to the planet to investigate where our stolen shuttle was, and were the man who stole it was so we could subdue him. Little did anyone realize, or even think of , was this planet wasn’t all to liking of the federation, and Star Fleet. I guess in our biased opinions us Star Fleet officers feel we’re accepted everywhere…yet this time around proved to serve as a lesson to a lot of us. Not only was the away team not accepted among the locals, they were despised, which didn’t seem to help the investigation any. In the end I feel it was the locals hatred of Star Fleet that lead the away mission to failure. The Yeager wasn’t able to recover its stolen shuttle, nor was it able capture the man who stole it, Lt. Jean-Rene Lacardo.
During the away teams time on the planet they were contacted by a Trill Ambassador, who requested the aid of Star Fleet to transport her to the nearest Starbase. I granted her request and she was beamed aboard along with the rest of the away team when they returned after things got a bit sour on the planet....
Once the away team was on board, I wanted to go speak to the Ambassador in person, however almost as soon as the away team was beamed aboard a starship approached the Yeager it was the massive pirate ship that attacked the Yeager during its pervious mission. I was in my quarters at the time, waiting for the away team to arrive, when I got the message to come to the Bridge.
Stepping on the Bridge, I was greeted by a man on the view screen who was hidden by shadows from his own Bridge. With a voice that was familiar to me, the man arrogantly taunted. After a few minutes the man stepped out of the shadows he was standing in to reveal his identity. To everyone’s surprise, it was Captain Luke Johnson, the very man the Yeager was sent to rescue. Johnson was a traitor.
Wanting to stop the Yeager’s investigation into finding these Pirates, Johnson demanded I hand the ship over to him. Having a duty to Star Fleet to not allow sensitive materials to fall into hostile hands, I refused. Not liking my reply Johnson and his group of pirates attacked the Yeager.
After a short battle which resulted in numerous hull breaches, the Yeager was able to disable to pirate warship. Some would say it was luck, others would say it was skill, but none the less as tiny of a ship the Yeager was, it managed to disable a warship.
Though the warship was disabled its shuttles weren’t, and one managed to escape. One could only guess that that shuttle had Johnson and his senior staff on it. Before the shuttle left a self-destruct sequence was activated on the warship. I ordered the Yeager to get to a safe distance, and the Yeager managed to just before the warship exploded.
During the battle the Yeager sustained enough damage to not be able to go to warp. Being unable to arrive at a starbase in a reasonable time on its own, the Yeager requested the assistance of the USS Drake to tow us.
Currently the Yeager is docked at Starbase Alpha, and the crew is on shore leave.
I must say that I feel this mission was a complete failure. We weren’t able to complete any of our intended objectives, Johnson whether he was a Star Fleet officer or not was not recovered, nor were any of the other mutineers. We were also unable to find any clues on where the pirates are operating from.
The price for this failure was too high; too many good people lost their lives, and for what…absolutely nothing…
I can only hope sometime in the future I can make it up to those people who lost their lives, and bring these pirates to justice.
End Log.
Crew Logs
Science
CSO - LCdr Bob Truax
Stardate 20403.01
Well this is my first log aboard the Yeager. She is a mighty fine ship. I'm surprised at her crew, the yeager may be a scout ship but the crew know how to make her handle like a battle ship.
[Door chime]
Somebody's at my door, computer end log.
Stardate 20406.30
LCdr Truax LCdr Bob Truax - Acting Chief Science Officer Stardate 20406.30
The events that lead up to this last mission began shortly after my last log. Jaina had just transferred over from the Drake and... let's just leave it at that. Anywhoo while in the shower Green Goo started to spurt from the shower head covering the both of us. Unknown at the time this goo was actually a lifeform similar to the Bajoran Prophets, in that they lived in a region of subspace and were non-linear. But alas I am getting ahead of myself.
Strange things started to happen all over the ship. Goo dripping from the ceilings in various crew quarters, seeping from the consoles, and in one unverified instance I believe it reanimated a corpse. LCdr Meor the CMO had an interesting thought about the goo, he placed a small container of it on his abdomen and it was absorbed into his skin and in contact with the symbiont Meor. This lead to the discovery of a subspace anomaly which happened to be a gateway to the creatures home.
And on a happier and less technical note Jaina is with child. We found out during a routine medical exam.
End Log.
Tactical
TO - Lt [JG] Nathan May
Stardate 20403.06
Nathan began after waking from his nap. "What a sleep. I'm not sure if I was tired from the Battle or what, but I was tired! Anyway, I sent a message home to my Aunt's House in Tennessee. I still need to contact my family on Andrea II. For clarity sake, I haven't contacted them for almost two months now, but they know that sometimes I go very long periods without sending word, so I am sure they aren't worried."
Nathan got up and headed to the replicator, the log recorder still on. "Terran Coffee, black." After taking a few sips, he continued.
"Amalek, got his promotion and I am sure that means he'll get the CTO job. No matter though, we are all in it together. Mine'll come soon enough." He resolved.
Thinking for a moment about the positives he should enter, he continued. "Sat in the Mess yesterday and talked with three DH's and a Junior Security Officer. Two of the DH's are getting married. One's part Klingon and wants to be beaten to death for it." Nathan said sarcastically almost causing himself to burst into laughter.
"But I guess it's there way, who am I to judge?" He asked shaking his head and taking another sip of his coffee. "Well, I need to get ready for the day. Thanks for listening. Computer close log." LCdr Truax Well this is my first log aboard the Yeager. She is a mighty fine ship. I'm surprised at her crew, the Yeager may be a scout ship but the crew know how to make her handle like a battle ship.
[Door chime]
Somebody's at my door, computer end log.
Stardate 20408.09
The Yeager is currently in orbit of Volon II. Well, what's left of the Yeager. She's been through hell and I'm sure her hull can't wait to be supported by Dry Dock Tractor Beams after this cruise is over.
The strange thing is... we haven't been in one battle yet! The damage has ranged from system glitches caused by a run in with non-corporeal beings to sabotage resulting in an explosion by an unknown assailant using old command codes. We have tracked him to Volon II after he managed to steal a shuttle in the wake of attempting to assassinate two command officers.
I mean, yeah this has been a mission for the books already and our mission isn't even over yet. I can't wait to see what fate has in store for our brave little ship next.
To who ever reads this. I am in a light hearted mood.
End log.
Stardate 20408.25
Spotted, what I am pretty sure is, a cloaked vessel just a few moments ago. I've tagged it so that the computer will monitor the distortion's orbit. If it's regular, I'll know for sure. Then I'll bring it to the Captain's attention.
Also ran a scan on a passing Vulcan Transport which was carrying Klingon Rations. Makes me wonder if thats a Klingon warship here around Volon II. With the current state of relations between the Federation and the Empire, I'd hate to be right. Who's to say those 'honorable' warriors wouldn't think twice about attacking a small lightly armed Star Fleet Scout.
Sometimes, I long for the protection of a Battle Cruiser's teeth and protection. But, deep down I wouldn't change being posted here if I had the chance. Good people here. Aunt Virginia would like them.
End Log.
