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.

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.

Captain’s Log, Supplemental

The USS Narragansett has taken heavy damage. We had to eject the warp core. We suffered many hull breaches and many casualties. Support ships are inbound and we are doing our best to repair what we can with parts on hand. I’m afraid the Commodore will be disappointed with the state of the ship. Life support is stable at 35% and auxiliary power is holding.

We lost a lot of good people today, and the fleet lost many, many ships. I remember when we spent our time exploring the galaxy rather than fighting in wars. I miss those days.

Operations Status Report

All Departments report systems operating within normal parameters. Tactical is concerned about the wear on the weapons systems with their current ruining status. I have asked Engineering to increase the frequency of maintenance to compensate.

Department head reports continue to trickle in. It is nice to be back from leave.

April Meeting of the USS Narragansett

The meeting was called to order at 1515 at the EWG JSHS Library with Fleet Captain Knotts presiding.

He brought us up to speed on the happenings in SFI R15. The Regional Coordinator has resigned effective June 1st and nominations are open. So far the captain is aware of 3 people who have announced their candidacy, himself included. He is hopeful that the Region will consider our success and listen to his platform rather than the RC election becoming a popularity contest.

S3C is continuing to work on improving communication and reporting as well as developing their Academy.

Lieutenant Bender announced a contest to name the USS Narragansett newsletter. Please provide your entries within the next two weeks. There will be a prize for the successful entry.

Commander Taylor explained that there is a New Members Guide to the USS Narragansett and an associated Questionnaire and Exam on our website. All members are requested to complete the exam before the next meeting.

Captain Anzaldi told us about a new simulation tool he would like us to investigate. He will post a link later today.

A general discussion was had around upcoming events. Our next meeting will be held at the Fleet Captain’s quarters on May 26th, where we will complete the assembly of the Delta Shields and then have an away mission to recruit at the Gaspee Days Arts and Crafts festival.

We are also planning an away mission to the Air Show on June 9th.

Lieutenant Dreyfuss mentioned that the Foxwoods ComiCONN is June 30-July 1st. Altered Reality is looking for volunteers, and the Narragansett will also have a table at the show that will need to be staffed as well.

Chief Chapasko is also looking into the possibility of an away mission to do laser tag to prepare for upcoming missions.

Second Officers Log

It has been a tough week. I dealt with a difficult personnel matter and ended up having to turn it over to Captain Anzaldi. As a result, I created a New Member’s Guide to the Narragansett and a Questionnaire and Exam to go with it that lays out the expectations for crew members as well as an explanation of what we are about and how we are organized. When a new member completes the exam they will earn the rank of Crewman 1st Class, and the questionnaire will inform us as to what assignment they desire and what level of participation they wish to have.

Our mission to Cestus III has been, thus far, uneventful. We are enroute and will arrive next week. I am pleased with the progress of the upgrades reported by Lieutenant Bender. She is doing an excellent job in her new role as Chief Engineer.

Captain Knotts’ event on the holodeck was an enjoyable affair. It’s always nice to kick back and relax with friends after a long week. The senior staff members who could not make it were sorely missed.

Commander J. Taylor

Second Officer’s Log

Participation in the Shenzhou mission far exceeded my expectations. Even the crew members who did not participate and were following along enjoyed it. I do wish that the platform we used allowed more people to be included in Command chatrooms without the ability to talk, just so they could follow along. Many of the conversations we had would have been made from the bridge of the ship and the crew would have been kept in the loop without the plethora of screenshots.

I was surprised at how much I enjoyed being in the center seat of the Narragansett. I did not think that the command branch was for me, but perhaps someday I will consider changing branches from Services. In the meantime, I will do my best to serve the ship from the Operations seat. I am very proud of the crew members who served with me on the Narragansett, and of my Commanding Officers’ performance during the mission, as evidenced by my long list of recommendations for commendations.

I am very happy with LTJG Bender’s transition to the position of Chief Engineer. She has proven to be quite adept at the Engineering coursework at SFA and I expect her to have her BOCP certificate very shortly. She is also well on her way to recognition by the academy for outstanding coursework.

CMN Feldman has made good progress on the Narragansett newsletter. She provided me with a mock-up of the design (attached) and I am happy with the layout. She has requested a piece from FCPT Knotts for the first edition’s Captain’s Corner, in which she would like him to speak to our mission and his vision for the future of the Narragansett and the Fleet. With her level commitment to the ship, she will be a rising star on the Narragansett. Should this newsletter be successful, a Fleet newsletter may be in order also, perhaps published twice a year.

LTJG Anzaldi has made improvements in her communication. She has already reached out to me about her report and I expect it soon. This bodes well for the future.

I have designed a flyer (attached). I would like approval to post it in the EWG Library and other locations as applicable, or alternatively, I would like someone to design one for this purpose.

Proudly in Service,
CMDR J. Taylor
Second Officer
Senior Services Division Chief
Chief Operations Officer

After Action Report

Things were going pretty well until FCPT Knotts made the decision to join the away team against the advice of the Chief Archeologist, A-CMDR Brunelle and myself. After that, things went from bad to worse.

All ships should have immediately changed their command codes and locked out FCPT Knotts. This did not occur to anyone until after the computers began malfunctioning.

There were several computer glitches that were not found because we failed to verify that the information presented was correct by checking with our departments.

I fired on USS Voyager when she requested that we help in disabling her secondary command processors. I did not think about the ramifications of that action. I made a quick call and it was the wrong decision. I wanted to help, but I should have trusted A-CMDR Brunelle to think her way out of the situation and gave her suggestions instead of acting rashly.

We failed to look at the contents of the Klingon distress call. We don’t even know that the Klingon Ships weren’t there to help.

Some ships failed to interact with their NPC Klingon characters which arose their suspicions. I will say that for the situation to be believable, the NPC Klingons should have reached out to the Bridge and demanded to be told what was going on, rather than sending out a distress call. Only if ignored should they have sent a distress signal.

My ship used anesthetine gas to subdue the Klingons. This was uncalled for. I did not object because I was pissed that they sent a distress call, and I had every intention of moving them to the holodeck while they slept and modifying the memory of the two that were not already asleep. Was it the best way to deal with the situation? Probably not. Would it have worked? Probably

Captain’s Log

We have embarked on a top secret mission. FCAPT Knotts and CAPT Anzaldi have been assigned to the USS Enterprise for the duration of the mission. LCDR Brunelle has been assigned to the USS Voyager. Most of the other senior staff have been assigned to other ships as well. A-CMDR Griffin is serving as my first officer. His performance thus far is impressive.

A-ENS Feldman and A-ENS Clauson are acclimating well to bridge duty. We have successfully completed an auto-destruct drill which went off without a hitch. I look forward to the challenges that lie ahead. The mission will require some significant feats of engineering balanced with significant tactical issues from this hostile area of space. I have faith that the crew will meet those challenges with the mettle I have come to expect from all who call the USS Narragansett home.

Second Officer’s Log

Monthly status reports are almost complete with one outstanding authorized extension. Duty logs have been posted. One personnel issue was dealt with resulting in a demotion. CAPT Anzaldi announced the opening for Chief Engineer. I’m looking forward to seeing many qualified applicants.