Dennis "Bill" Anderson

Dennis

Captain Dennis William Anderson NCC-101304-A -- U.S.S. Daedalus NCC-101305-A -- U.S.S. Biliskner Fleet Administrative Officer

Featured Ship of the Month: U.S.S. Riviera

 Comments Off on Featured Ship of the Month: U.S.S. Riviera
Oct 042014
 

Hail Captains of the 101st Fleet! So, many of you may be wondering why the our Ship of the Month was delayed until October (since Captain Confuto was supposed to be featured for September). The answer is that it took me that long to get clearance to access U.S.S. Riviera’s systems manifest (that’s right, it’s classified!), not to mention getting permission from the higher-ups to publish the information. Alas, I couldn’t get any records on Riviera’s activities in the past, as those are classified as well, and Captain Confuto himself politely declined comment when I asked him about his ship and its activities.
In spite of the difficulties in obtaining the information, though, U.S.S. Riviera’s systems manifest is now unclassified and published alongside our past Featured Ship system manifests. Click the link after the jump, and happy warping!

Riviera2 Riviera6 Riviera5 Riviera4 Riviera3

U.S.S. Riviera systems manifest

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Featured Ship of the Month: U.S.S. War-Dog

 Comments Off on Featured Ship of the Month: U.S.S. War-Dog
Aug 042014
 

Hail 101st, this is Captain Bill with our Featured Ship for the month of August, the U.S.S. War-Dog! Built for battle and tough as tritanium nails, the War-Dog sees action all over the galaxy, fighting wherever 101st  Fleet Command calls her. Her captain, Captain Gunnerwolf, is as tough as his ship, and not a commander to mess around with unless you want to be sitting on your butt. Thankfully, I’m on his good side today.

2014-07-23_00003

Cpt. Bill: “Captain Gunnerwolf, thanks for joining me for this interview, and may I say congratulations on being featured for this month’s article.”

Cpt. Gunnerwolf: “Thank you Captain, I’m glad to be here.”

CB: “I guess we’ll just dive right in, shall we? What would you say is the War-Dog’s strongest point?”

CG: “I would have to say that the U.S.S. War-Dog’s most definitive strength is its power and ability to destroy enemies quickly and efficiently. It was redesigned from a Sovereign class to use state-of-the-art tetryon weapons, quantum mines and torpedoes, along with metreon gas, which is highly volatile but does immense damage to anything in it path.”

CB: “I’ve seen you use those gas canisters before to great affect, Captain. You must have mastered the Riker maneuver a long time ago. Moving on; what would you say you value most in your crew?”

CG: “I value most their ability to work together and follow my orders no matter what they are. They are a strong crew with the best training Starfleet can offer.”

CB: “Starfleet is extremely good at giving us the best, aren’t they? Now, given the ship’s role in our current war-time status, would you say it’s difficult to maintain operational integrity with everything that goes on?”

CG: “It can be very difficult to maintain my ship due to its design. Originally it was a Sovereign class but was was heavily damaged by the Borg and redesigned. Now an Imperial class starship, it’s a more compact design and more powerful. Although it lacks some defensive capabilities of the previous design, it can still take most enemies head on. My crew works very hard to maintain the ship and its systems.”

CB: “I definitely appreciate all the work you and your crew put in to your ship. I know my own crew works hard, but we all know their job is easier than others, being on a new ship. Speaking of difficult times, what is the hardest mission you’ve had to put the War-Dog and your crew through?”

CG: “The U.S.S. War-Dog has had many challenging missions. A recent battle against a crystalline entity would be one, but there have been many times in my ship’s past has such entities threatened to destroy my ship and crew. Thankfully on those occasions we were victorious. The ship and crew are ready for any challenge no matter how strong or destructive.”

CB: “Well I think I speak for all of us in the 101st when I say that we appreciate the hard work that you and your crew go through to help us defend the Federation.”

CG: “Thanks, Captain. I won’t pretend it’s easy, but we all enjoy the work we do, and it’s all for a great cause.”

CB: “Well, that’s all the time we have, I’m afraid. Thank you all for listening in on our little conversation. You all can find the U.S.S. War-Dog’s manifest page in the Fleet Engineering Archives. We’ll see you in the field, and until next month, happy warping!”

2014-07-23_00004

The U.S.S. War-Dog Equipment Manifest can be found here.

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Featured Ship of the Month: U.S.S. Juggernaut

 Comments Off on Featured Ship of the Month: U.S.S. Juggernaut
May 012014
 

Hail fleet; Captain Bill again with the 101st’s Featured Ship of the Month! For May, we’re proud to feature Captain Saleen’s U.S.S. Juggernaut, a Voth Bastion Flight-Deck Cruiser. Captain Saleen is notorious for having good luck with lock-boxes, but it isn’t all luck on the battlefield! The Juggernaut is named so for a good reason, and Saleen’s prowess in the command chair only serves to compliment the Juggernaut’s abilities. Its combination of Voth weaponry, Dyson Joint Command systems, and fleet equipment make it a deadly force to be reckoned with. Here are a few images of the ship herself, and you can check out the Juggernaut’s equipment loadout after the jump!

screenshot_2014-04-26-22-02-19

screenshot_2014-04-26-22-06-47

screenshot_2014-04-26-22-06-51

U.S.S. Juggernaut loadout

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Featured Ship of the Month: U.S.S. Reisen

 Comments Off on Featured Ship of the Month: U.S.S. Reisen
Apr 152014
 

Hello Captains, this is Captain Bill with this month’s featured ship! This month, we’re honoring Captain Ulaan’s U.S.S. Reisen, a fiesty little Comet class that can and will be a thorn in your nacelles if you don’t watch yourself! I’ve had the pleasure of flying alongside Captain Ulaan for several months now and I can say it’s amazing what his crew can pull off. U.S.S. Reisen is currently in drydock at Starbase 1–she’s being refit with new systems, courtesy of the reverse engineers in the Solanae Dyson Sphere, in response to the new threat from the Undine. Check out U.S.S. Reisen’s loadout page after the jump!

U.S.S. Reisen Ship Loadout

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Captain’s Log – U.S.S. Biliskner

 Comments Off on Captain’s Log – U.S.S. Biliskner
Mar 242014
 

Captain’s Log
Stardate 91831.3

It’s been awfully slow for the last month or so. 101st Fleet Command has kept the Biliskner on light duty and close to the Starbase while Vice Admiral Jim is on leave. The timing isn’t terrible though–Biliskner spent some time in drydock undergoing her quarterly maintenance check.

About a week ago marked the beginning of what seems like a constant onslaught of ships from the Mirror Universe attempting to take over Vauthil Station. Biliskner hasn’t seen much action, but my crew and I are still part of a 24-hour rotation of defense teams. We still have no idea when the Incursion will end, but the Terrans can only have finite resources. It’s not as if they get to take many of their ships back to their own universe once we’re done with them.

After several months of reaching out with my cross-faction contacts, I have established sporadic contact with a member of the 101st Imperial Fleet. While their identity remains unknown, I have received information that the fleet’s leader has gone almost completely underground. Whether for fear of his own life, or other reasons, I don’t know. But it doesn’t matter. My gut tells me that even in his absence, the Imperials continue to grow in numbers and strength. This does not bode well.

All in all, it has been a slow month. I can only hope that this isn’t the calm before a massive storm. Especially given the events surrounding the rescue of Admiral Tuvok…

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Featured Ship of the Month: U.S.S. Gunfighter

 Comments Off on Featured Ship of the Month: U.S.S. Gunfighter
Mar 092014
 

Hi all, I know its been a little while since we’ve done a Ship of the Month. The Administrative Department has been in a mild state of disarray lately–Vice Admiral Jim has been out-of-game due to some RL issues, and he’s got big shoes to fill! Needless to say that we at the F.A.D., and Fleet High Command all wish him well, and hope that we see him again soon.

As it is, the Ship of the Month has been pushed back, meaning we skipped February, but here we have the U.S.S. Gunfighter, our Featured Ship for the month of March, courtesy of Fleet Captain Kayliee! (Hint: click on the image to take you to the Gunfighter’s page! You can also get to it from the Fleet Shipyard Roster).

Gunfighter 11

Hope you enjoy it, and see you all in game!

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Captain’s Log – U.S.S. Biliskner

 Comments Off on Captain’s Log – U.S.S. Biliskner
Feb 112014
 

[PHOTO REDACTED]

Captain’s Log
Security Classification Level: Omega 2
Stardate 91694.21

A successful mission to rescue Admiral Tuvok has, unfortunately, left me not feeling very successful at all.

The Biliskner’s shields were remodulated to survive extreme proximity to the Solanae Sphere’s central star, thereby allowing us to move forward with the beginning of our mission. We managed to bypass the battle raging with the Voth by staying beneath the peaks of the star’s solar flares, and neared the space station without incident. Biliskner joined the battle following my departure to the station. I met with Admiral Tuvok and Dr. Eric Cooper, an expert (or as much an expert as any) on the Solanae technology in the Sphere. According to Tuvok, the rest of his team, and the captain of his ship, the U.S.S. Dyson, was killed in scuffles with the Voth. As it turns out, the solar station controls the Sphere’s ability to ‘jump’ to anywhere in the galaxy. Our goal was to disable the station, before the Voth had the chance to jump the Sphere to their space, deeper into the Delta Quadrant. Aside from the fact that we would very likely lose the opportunity to continue studying the Sphere, the jump would would require the energy release of thousands of Omega particles, which would devastate the entire area of space–likely a good portion of the Quadrant.

After fighting our way through a few Voth hard-points, we got to the station’s main control room. As Dr. Cooper brought the shutdown program online in the main computer, I fused the fail-safe conduits to prevent the computer from bypassing our commands. A hard-coded byproduct of the station’s shutdown was the activation of an Iconian gate, which would have served as an escape point for the Sphere’s original inhabitants, in the event of an emergency. Immediately after the gate activated, a Voth Bastion cruiser flew into the gate, and we were forced to pursue.

This new gateway, as it turns out, leads to what we know as the Jenolan Dyson Sphere, which had vanished from the Beta Quadrant when the Iconian Gateway network was reset a few months ago. It turned up in the Delta Quadrant, with the U.S.S. Gold still trapped inside. The Voth ship had disabled the Gold, without destroying it, and turned its attention to the nearby doorway to outside space. As the we approached the Voth ship, Dr. Cooper attacked Tuvok, revealing himself to be an Undine, and then left the ship. I revived Tuvok, but as I did that, and Undine energy weapon blasted through the Sphere’s bulkheads, destroying the Voth ship in a single hit. The Dyson was thrown into battle against an onslaught of incoming Undine ships, and we managed to hold our own until the arrival of the Romulans and the Klingons to help defeat the Undine.

After the battle, we all returned to the Dyson Joint Command spire in the Solanae Sphere, shaken and irritable. The plot by the Undine to open a door to the Alpha Quadrant is unsettling to us all, and instability is growing in the three-way alliance we’ve preserved so far. But with each side attempting to claim the Jenolan sphere for themselves, only time will tell if we can set aside our own differences, in order to defeat a common enemy. The Romulans seem reasonable, but there’s no telling which side they will fall on if the Klingons decide to take the Spheres for themselves.

————————————————————————–

Captain’s Log
Stardate 91716.78

It’s business as usual on the Biliskner; ever since last week’s operation, we’ve been running tactical drills with other ships in the 101st Fleet. Our previously friendly Klingon counterpart, the 101st Imperial Fleet, has officially declared war on us, following the destruction of the U.S.S. Queen Mary C by a renegade Ferasan captain known as ‘Aj H’Rjarr Kzin M’Ktatt. In response to the QMC’s destruction, a previously commissioned Fleet Sovereign cruiser was rechristened and pressed into service as the U.S.S. Queen Mary D, under the command of Vice Admiral Ieon Winter. There have been a few skirmishes with the Imperial Fleet, but no sign of H’Rjarr since the initial incident over a month ago. A few ships have been lost on both sides, and search parties generally get sent out after ships that have gone missing.

My Chief Engineer, and long time pupil, has made an interesting observation about our weapons systems, and how it interacts with the power distribution system. He and I are working on a joint report to be sent to the Starfleet Engineering Corps, and the technical details of the logic will be found in there. The gist of it is this–since Biliskner is outfitted entirely with energy beams, the biggest hindrance it has is the instantaneous energy draw of each beam that is firing in parallel with other beams. Ken’s observation is that, if we could somehow stagger the beams’ firing times, we could increase our sustained damage by allowing the EPS system to distribute power back into the weapons system just before another beam fires. The only tradeoff that I can see is that our initial damage in the first volley would be laughable at best; it would take a couple seconds before the beams really kicked in. He and I will be continuing our work in this area–I admit, I miss working on projects like this. It reminds me of a time not long ago when I was the Chief Engineer and someone else was Captain. I’m not sure I miss that old Miranda, but I miss spending my nights in bed listening to the rumble of the warp core two decks beneath my feet. Sleeping in the Captain’s Suite just isn’t the same.

2014-02-10_00004

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Captain’s Log – U.S.S. Biliskner

 Comments Off on Captain’s Log – U.S.S. Biliskner
Feb 012014
 

2014-01-31_00001_Banner

Captain’s Log
Security Classification Level: Omega 2
Stardate 91680.92

We were on route to Deep Space Nine from Starbase 101 when I received a Priority One text-only communique from Starfleet Command: an encrypted message instructing the Biliskner to rendezvous, with all due haste, at the Dyson Joint Command Spire, in the Solanae Sphere. The last time we visited the sphere was during shakedown, when there was minimal crew aboard that were all aware of the Sphere. Unfortunately, this time our classification protocols will be need to be enacted. Knowledge of the Sphere is classified by all three of the involved governments. Starfleet Captains are all briefed on the Omega Directive (Senior Officers may be briefed by their Commanding Officers on a need-to-know basis), however, knowledge of the Sphere is restricted within Starfleet on a need-to-know basis only. Therefore, during our stay in the Sphere, the blast shields will remain closed, and we will be on yellow alert at all times. I will be briefing my officers within 12 hours; most of them have been briefed before, the only exception being my new Tactical officer, who was assigned to us post-shakedown to relieve my First Officer of Tactical duties.

As far as the nature of our mission in the Sphere, we have no knowledge. Protocol directs me to report to Subcommander Kaol upon my arrival, and given the urgency with which the initial communique was sent, I can only guess that whatever this mission will entail, it is of dire emergency.

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

Captain’s Log
Security Classification Level: Omega 2
Stardate 91690.38

We’ve arrived in the Solanae sphere, and I’ve had the chance to speak to Subcommander Kaol. It seems that my original assessment was correct: the news is indeed dire. Admiral Tuvok was sent on a mission to investigate a space station in orbit extremely close to the star at the center of the Sphere. In the middle of the mission, the Voth discovered the station, and the detachment’s presence there, and attacked. Tuvok has been stranded on the station with few reserves, with the Voth persisting in their attacks. The Biliskner is to go to the station, rescue the Admiral and his crew, and complete the mission before the Voth have a chance to gain control of the station…

2014-01-31_00005

OOC: Have fun everyone, and enjoy the new FE and Season 8.5!

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Captain’s Log, U.S.S. Biliskner

 Comments Off on Captain’s Log, U.S.S. Biliskner
Jan 162014
 

Captain’s log
Stardate 91640.44

We have finished patrolling the Hfihar system, which completes our patrol of the Romulan Neutral Zone. Three days ago we were attacked by a pair of T’liss warbirds, two lightyears from the Rator system. The markings on the vessels matched known Tal Shiar markings, and they did not respond to hails. The Biliskner took minor damage in the initial volley, when shields were at idle power levels. The dorsal half of our omni-directional antiproton array was damaged, along with a nearby shield emitter. We do not have the equipment to repair the antiproton beam out here, nor the safety equipment to prevent antiprotons from escaping the containment fields they are normally confined to; maintenance crews at Starbase 101 are already preparing a drydock with the proper equipment. These events may prove useful, however, as Chief Engineer Geoghegan has informed me that he and Lieutenant T’Mir, during their examination of the damaged shield emitter, may have found a way to boost our shield’s ability to regenerate itself with only minimal alterations to the emitter nodes. I’ve looked over their proposal, and I’ve forwarded it to the engineering team that will be assigned to Biliskner upon our arrival. When repairs are complete, our standing orders are to report to Deep Space Nine, for an assignment from Captain Kurland.

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office

Captain’s Log, U.S.S. Biliskner

 Comments Off on Captain’s Log, U.S.S. Biliskner
Jan 072014
 

Biliskner_Drydock Biliskner_at_spire

Captain’s Log
Stardate 91603.18

I’m nearing the end of my first week in command of the Biliskner, and I must say that, once again, I’m very impressed with Utopia Planitia. The Avenger class is a marvel of engineering, and in my opinion holds is place very well between the Sovereign and Akira classes. We’ve just completed the final part of our shakedown, and are headed back to drydock at Starbase 101 for a few minor adjustments, and an “upgrade”, if you will. Originally, the ship was to be fitted with a regenerative shield array created by the Dyson Joint Command Technology Reverse-Engineering team. However, due to setbacks on the Voth front, the research team lost several days of work time moving their workspace to a more secure location. In order to test the rest of the Dyson equipment installed on the ship, 101st Fleet command ordered a standard regenerative array installed temporarily, in order for shipboard operations to continue on schedule. Luckily, the Dyson team completed the shield equipment this week, so we are carrying all of the necessary components for the array back to Starbase 101 for its installation. In the meantime, I have instructed two engineering teams to begin integrating some of the internal components of the array. We’ve been under way for about 13 hours–we should be back in drydock in five days.

———————————————————————

Captain’s Log
Stardate 91622.34

101st Fleet drydock personnel have just reported that their modifications to the ship are complete. They’ve informed me that, along with the new shield array, they’ve installed an experimental proton weapon from Dyson Joint Command as well. They’ve asked us to use it against both the Voth and the Borg in our routine missions and to report back on its performance. They’ve assured me that it will not cause any ill effects when used in conjunction with our current loadout of antiproton arrays. I admit I’m slightly nervous about having both protons and antiprotons used in such proximity, when the two together are so volatile. On the other hand, this weapon’s integration with proton stabilizer system is supposed to have increased the yield potential of our gravimetric photon torpedoes. In addition, the Dyson shield’s integration with the other Dyson systems has added automated defensive algorithms and technologies which will increase our resistance to focused energy damage during battle. Both systems are to be tested under normal operating conditions, so the only thing I can do is wait and see… and hope that whatever the Dyson engineering team has come up with works.

Biliskner_topdown Biliskner_Drydock_2

---
Captain Dennis William Anderson
U.S.S. Biliskner - NCC-101305-A
Fleet Administrative Office
Skip to toolbar