First Officer’s Log

Today was a good day to die. The problem is today never happened according to the chronometer on my desk… yet I distinctly remember the events of the day. It all started when I opened my eyes this morning at 0800 and found 3 year old eyes filled with wonder staring into mine from about 6 inches above my face. My son Oliver said to me “Daddy, are you sleeping?”

Naturally, I responded “Yes.” and closed my eyes again.

A few more minutes of prodding from Ollie (with help from his sister Alice) resulted in my getting up and getting coffee for myself and my wife, Doctor Taylor, and breakfast for the kids from the replicator. I took a sonic shower, got dressed, said bye to my family and headed out of our quarters to face the day.

I stopped by Engineering to check in with Chief Bender about the calibration she was planning for the warp core in the afternoon. All was well in Engineering so I stopped by the Armory to ask Commander Knotts how we were progressing with the shipwide inventory ordered by command. He reported that we were behind schedule.

I made my way to the bridge intending to ask Commander Griffin to assign some additional personnel to the Armory to get us back on schedule with the inventory, but all thoughts of administrative minutiae flew out of my head when I stepped onto the bridge and the red alert klaxon began blaring. The lighting changed as the ship prepared itself for battle and I approached my chair to relieve Commander Griffin. “Status Report” I asked briskly both to make him aware of my arrival and to find out what was going on.

“I wish I could give you one, sir” he responded, looking perplexed. “Nothing is showing on sensors but the ship put itself into defensive mode due to a proximity alert. We’re running more intensive scans now. The sensor log shows a blip which must have triggered the defensive systems…” he trailed off, looking at reports on the status display.

“Very well, keep me apprised.” I went to the Captain’s chair and called Captain Knotts, apprising him of the situation. He asked that I keep him informed. I looked over the sensor and tactical data from my station and agreed with Commander Griffin’s assessment.

“Have we tried running a multiphasic sensor sweep?” I asked, grasping at straws.

“We’ve run every kind of sweep I know to run, unless you’ve come up with a new sensor configuration I’m not aware of” Commander Griffin quipped.

“Not recently” I replied. Looking at the sensor analysis again I saw results coming in from the scans I had inquired about. Nothing out of the ordinary. I forwarded the scans and my analysis to Captain Knotts. “Cancel red alert, but maintain condition yellow” I ordered. Yellow alert would keep the ship in increased readiness mode with more frequent automated scans. “See if you can determine what happened, and if we get anymore blips, let me know immediately. We’ll have a briefing at 1200”

Trusting the crew to investigate the mystery, I fired off a notification of the scheduled briefing and I turned my attention back to administrative duties, adding some personnel to the Armory schedule for the following day (as I knew they would be busy for the rest of the shift investigating this latest anomaly). A ship this size has an enormous amount of administration. While the crew spends it’s time investigating the nature of our universe and generating data, the command staff spends an inordinate amount of time scheduling, planning, reviewing reports, and making sure things run smoothly.

At the 1200 briefing, Lieutenant Commander Brunelle expressed dissatisfaction at our lack of scientific explanation for what caused the sensor blip. “It’s almost as if we brushed against something with our navigational deflectors, but the sensors showed nothing there.”

“Assuming we did, what could have disrupted our navigational deflectors that would not register on the sensors?” Captain Knotts asked.

“A cloaked object of some kind, but it would have to have been very small. Maybe the size of a deck of cards, and we aren’t aware of any cloaking technology that miniaturized.” replied Lieutenant Commander Brunelle.

“Just because we aren’t aware of it doesn’t mean it doesn’t exist,” I replied. “Maybe the reason the multiphasic sweep didn’t detect anything outside the ship because whatever it was wasn’t outside the ship anymore…”

Mr. Griffin began prodding the PADD in front of him furiously. “I’ve run an analysis of internal sensor log data from the time of the incident and I do see some slight distortion consistent with an object out of phase with our reality passing through the ship’s hull and several bulkheads. I’m tracing the path now.”

A few minutes later we found ourselves standing in front of our main computer core. “It’s right here,” said Commander Griffin, glancing between his PADD and the core, pointing at the primary/secondary interface near the main power junction.

“What is it?” asked Captain Knotts, the concern on his face growing deeper.

“I’m not sure, but I don’t like the looks of it,” answered Chief Bender. It was invisible to our eyes, but she held up her PADD to show a 3D rendering of the object. It looked exactly like a box of playing cards but had no distinguishing marks of any kind, just smooth sides and sharp edges.

Just then, the captain’s communicator squawked. “CAPTAIN TO THE BRIDGE!” and the red alert klaxon began sounding again.

Captain Knotts, Commander Griffin and I headed quickly to the nearest turbolift. “Status report,” the captain requested.

“There’s a ship off our port bow of unknown configuration. At least we think it’s a ship. It wasn’t there a second ago and now it’s there. They aren’t responding to hails.”

We stepped onto the bridge and the image on the view screen was something to behold. It was a large box, a giant version of the object on our computer core. It was at least 1/3 the size of our ship and it’s silvery surface looked like liquid metal but was not the least bit reflective, instead seeming to generate its own dim light from within. The edges looked sharp enough to cut space-time itself and it stood out starkly from the blackness of space filled with stars and galaxies behind it.

“Open a channel,” said the Captain. A chirp signified that communications had been initialized. “Unidentified Vessel: I am Captain James Knotts of the Federation Starship Narragansett. You are in Federation space. Please announce your intentions and identify your species and planet of origin.”

“No response, sir,” said Lieutenant Commander Dreyfus from the communications station. “I am sending our translation codes using all standard modes of communication.”

“Try the non-standard ones too,” I said. Anyone with this kind of technology should be able to translate our language in short order once they recognized the series of primes at the beginning of our translation codes for what they were.

“Bender to bridge.”

“Go ahead,” replied the captain.

“Sir, it seems that the device on the computer core is accessing our main computer database. It’s downloading everything, and I do mean everything.”

“Interesting,” I said as I sat down at my station to review the data from Chief Bender’s PADD.

The Captain looked in my direction and said “Exasperating is more like it. I don’t like this one bit.”

“Incoming transmission sir, audio only, putting it through” said Lieutenant Commander Dreyfus.

“Starship Narragansett: We have analysed all of your ‘data’ and determined that your kind is not ready to know us. You are not developed. You cannot be allowed to continue with the knowledge of our existence.”

“What do you mean we cannot be allowed to continue? Who are you to decide that?” replied the Captain.

Lieutenant Commander Dreyfus reported “They terminated their transmission, sir.”

“Bender to bridge.”

“Go ahead Chief,” the captain replied as he began to pace.

“Sir, the device is showing a massive energy buildup that should not be possible based on it’s size. I’d estimate is has more energy currently than we can produce over the course of a year.”

Commander Griffin turned from the Ops station to look at the Captain and I. “I think we know what they mean now, sir.”

Suspecting that our choice to live on a Starship with our young family was poor, my thoughts turned to my wife and children a few decks below us. I didn’t have long to regret, as the world went blindingly white.

What seemed like an eternity later, I found myself sitting at my desk. The time on the chronometer read 1000, and none of the events I have recounted here after I stepped onto the bridge this morning seem to have happened. It seems after I checked with Commander Griffin to assign more staff to the Armory I came here to my office to work on crew evaluations. Despite my vivid recollection, no one else’s logs seem to reflect these events and the sensor logs show no anomalies of any kind.

Captain Knotts had no idea what I was talking about when I inquired as to what was going on, so I decided to write this report to make sure there was a record of my memories. I think I’ll go to sickbay and get checked out.

Chief Medical Officer’s Log

Oh, this will be a doozy… I suppose that’s not a very professional introduction but it’s a very accurate one. When Lieutenant Commander Bender arrived with Crewman Redmond Shert I figured it was just another case of Andorian flu. It had been going around on Starbase 313 before the “comet” devastation. (I can’t believe I am mentioning that as a side note of this report, but we were successful in treating most of the casualties. The death toll came to 33, most of them dead on arrival.)

Crewman Shert displayed almost all symptoms of the flu – high temperature, body aches and pains, a nasty cough and sore throat, headache. I took a sample of his blood to analyze and positively identify the flu virus, but to my surprise that is not what I found at all. That is, I didn’t find anything at first. It was as if there was nothing wrong with him… except for the fact that he was effectively dying from the flu something that hasn’t happened in hundreds of years. Nothing I gave him worked. Antivirals and antifebriles were all ineffective. 

I had nurse practitioner Tribble take some tissue samples to analyze in her lab. 

It was then that the biobed Crewman Shert was laying on malfunctioned. I recalled Lieutenant Commander Bender to sickbay to take a look at the problem. She looked over that bio bad like I looked over my patient – really confused as to what the problem might be – very unlike our chief engineer, who was usually ready with answers and brilliant solutions to complex problems. 

NP Tribble returned with some results. She had managed to identify a virus before her equipment start to malfunction too. To determine how contagious this virus was we took blood and tissue samples from everyone in sickbay, including Lieutenant Commander Bender. Imagine our surprise at learning that we were all infected with the same virus. Except we weren’t sick… yet. I quarantined sickbay immediately. No one was getting in or out.

I wondered about the source of the infection – it had to be Starbase 313… clearly there was more to that “comet” story that no one believed anyway, but I digress. It would be impossible to pinpoint patient zero. We had since left the base and we did not have tissue samples from all of the crew. Just some of those we treated. There were so many injured… from the attack or comet or whatever… But not one person from our own crew… Usually there was at least a scrape, gash, sprained ankle, something! But it occurred to me that I had not treated a single member of our own crew since we left that Starbase. A fluke of good health and accident free living? Doubtful. We needed more tissue samples from the rest of the crew. Thankfully I could simply contact the off duty medical personnel and they could collect and deliver the samples to sickbay. 

That was how we found out that every single member of the crew was infected. But still only Crewman Shert was ill and the biobed he was laying on. And the instruments that had analyzed his samples… Could this virus spread from humans to machines? I ask NP Tribble to analyze Mr Shert’s full genetic profile while I went to work on the virus’ RNA sequence. We had to work fast. Mr. Shert’s condition was deteriorating. 

My findings were astonishing to say the least. The virus was indeed capable of infecting man and machine. Ms. Tribble’s diligent work also yielded interesting results. There was a unique element in Mr. Shert’s DNA that acted as a switch for this virus… turned it’s extreme healing properties destructive. Ms. Tribble was sure she could flip this switch back with some “good old-fashioned genetic engineering”. As a witness to her recent work – I did not doubt she could pull it off. 

I had so many questions at this point. I was absolutely certain that this “well” virus was not naturally occurring. Was someone trying to create a so called “fountain of youth”? Did that have something to do with the attack on SB 313? If Crewman Shert’s genetic makeup triggered something in the virus to cause harm rather than heal – how fast would that effect the rest of the ship? Already more systems in sickbay were starting to fail… And if we managed to flip the switch back… would everything be repaired again? 

I started to feel feverish… I decided to check on NP Tribble’s progress. On my way to the lab I saw our chief engineer working feverishly (literally), trying to purge the effected systems. 

NP Tribble was breaking out some ancient equipment she had replicated long before this “incident”. Equipment relying less on computers. We worked in silence unless we needed to speak. We were both feeling the ill effects of the virus. We could only imagine the rest of the crew starting to do the same. After all, as it spread through the computer, quarantining sickbay proved to be ineffective. I heard the Captain’s voice over the con. I told him to stand by. We did not have time to explain. 

By the time we were reasonably sure we had what we needed to “switch off” the unique gene in Crewman Shert we could barely walk. We ambled over with an old fashioned syringe NP Tribble had and injected the cure… A strange mist descended over sickbay and I slid down to the floor. I saw a couple of men in black uniforms enter sickbay…

When we woke up, Crewman Shert was gone. Not just from sickbay, but as it turned out, the ship as well. His file just stated “reassigned”. Reassigned where? And how? It’s not like we had reached our new destination yet – Starbase 14. 

We were also virus free. Good virus, bad virus, gone virus. The mist… maybe it wasn’t a figment of my feverish imagination. Maybe it had been a cure…

***

Chief Medical Officer’s log – supplemental. After logging my report of the incident it was immediately classified… I expect it’ll be soon purged from record entirely. 

IOIS – College of US History
CUSH 101 – 1600-1699 DISTINCTION

Navigation Officer’s Log

This month the ship was sent to a starbase to assess damages done by a so called comet, but upon arrival it seemed that there was damage done by photon weapons. After doing our assessment and assisting with repairs we have been ordered to go to another starbase to yet again assess some comet damage. Due to personal issues I had taken a short leave of absence and have now returned to my duties. Now that I am back I am hoping to find certain parts for the delta fliers to hopefully give them an upgrade and make them a bit more useful in the future. If I can get the correct scanner arrays we might just be able to make them useful for scouting missions, but I still need to run this by the Captain first. If I can get him to approve this endeavor then we could definitely gain some benefits. For now though I need to just sit at my controls and continue my work on some of the flight protocols to see if I can improve any of them. I may need to be in touch with engineering on some of these aspects as I should hopefully not cause any power fluctuations. Should I cause a problem, as long as I have engineering assisting me, it should be fixed quickly. First on the list is some protocols that were sent from Starfleet Command that should, in theory, help to widen our scanning range without the need for a new system. Again though I will need to consult the Captain on these first.

Engineering Officer’s Log

This month I am having most of my teams concentrating on repairing the damage done to Star-base 313, as well as investigating more into the actual cause of the damage.
Some of my crew are busy with some minor repairs to the Narragansett, a couple of glitchy replicators and some crew doors that are acting up.
I’m getting a bit worried about the environmental controls again, it’s been running a bit hot, so I have a few crewmen checking on that.
I have been fairly busy with my new job at Sol Sector, but my crews have been reporting to me hourly on their progress. I hope to have answers to several of these issues fairly soon.

Science Officer’s Log

The science department attended the region 15 summit with our commanding officers and a delegation of fellow crew members, travelling on a shuttle piloted by the very adept Mr. Nelson, and enjoyed the company of fellow officers and crew from several starships of the region. The replicators made very tasty bagel jalepeno sandwiches and the summit did much to improve inter-region relations and diplomacy. It was a sweeping success enjoyed by all.

The science department has been working on various experiments and studies this month including, but not limited to studying Earth animals of the 21st century and the cultural practice known as visiting a “”zoo”” and its’ purpose in maintaining species’ and preventing extinction. We have also been focusing a lot of our efforts in preparation for upcoming missions.

Operations Log

Some sort of temporal anomaly has swept through the Narragansett. The after-effects have been… disconcerting. Details have been difficult to parse together. My memory can’t be trusted to fill-in any blanks, and neither can my logs (or any ship’s record for that matter). Couple that with the frustrations of having to be debriefed ad-nauseam by Temporal Investigations has led to some short tempers. And really, how can I know if the timeline has been altered if I can’t remember any of the details that transpired during our “temporal incursion”?

I’ve never liked temporal mechanics.

Second Officers Log

Apparently the Narragansett was caught in a temporal anomaly. Temporal Agent Grey reports that it resulted in an alternate timeline that was so unstable that it collapsed and we appear to have been returned to our normal timeline. We have arrived at Star-base 313 to investigate the damage done by a “rogue comet”. The damage is not consistent with a comet strike. Our scans show it was more likely a transphasic torpedo. Science also detected a temporal distortion in the area. We are investigating the damage and assisting with repairs. Medical is assisting with treatment of casualties.

This section has been deemed CLASSIFIED and has been REDACTED. Security clearance level Beta-Two.

This month we made some changes to the website to incorporate SFI and Sol Sector to the crew manifest. The new promotions schedule has been posted. I resumed managing status reports and we have begun plans for a complete overhaul for the new website. I would like to reiterate my request for all Department heads to choose an Assistant to take over in their absence.

First Officers Log

Reported to starbase 313 for general inspections and repairs After a comet strike. We picked up strange temporal readings and contacted command. We received standby orders from section 31. As for ship functions, all stations and departments report in all systems functioning. Report on the summit at starbase 15 will be coming in the next few days once data can be compiled, and points can be confirmed by regional command.

Chief Security Officer’s Log

We had a very slow month, nothing to exciting happened. We went over some simulations in case of a Red alert made sure everyone knew where to go and what they needed to do. We also did a weapons check, count and cleaned all weapons.
Made sure everyone knew how to properly discharge and fire all weapons. We will continue weapons training into the next month.

In Service,
Lieutenant Commander Anzaldi, CSO

Chief Engineering Officer’s Log

All of the teams have been extremely busy over the past several weeks as the environmental controls have been severely malfunctioning, causing extreme cold temperatures throughout the ship, sprinkled intermittently with fairly warm temperatures. It has caused many illnesses among the crew, so we also had to use parts of engineering to help out sick bay.

I believe my crew has sorted it all out, however, and we will move on to upgrading various computer systems for the next month.

In Service,
Lieutenant JG Bender, CEO