After recent events, the Tiberius was ordered back to Narendra station for some much needed repairs and for the crew to take some much deserved R&R. On their way back, Admiral Walker gave some words of praise to the crew for their work in recent days and told them the station was at their disposal. He also informed the crew of the memorial services on the station in wake of the latest news from the Dominion Wars.
After that, the crew set about doing some prep work for departure. Lt. Commander Foxwell (Eng) assembled his team and made a list of things needing repaired. XO MacKenzie and Captain Ral (GM) discussed crew performance. In addition to the promotion of Dr. Jerrynn to Lt. Commander, MacKenzie also requested Ens Faraggut (NPC) be promoted to Lt Junior Grade. MacKenzie also inquired about taking the Command test, which Captain Ral said he would put in a request. MacKenzie then offered Captain Ral the chance to get together and have a drink at the station, which the Captain accepted.
The trip to the station, though longer than normal due to speed restrictions, was uneventful. Once at the station, the crew set about for some R&R, but not before the memorial service. Once the service was over, Captain Ral and Lt. Commander MacKenzie invited the crew out for a drink, which they accepted.
Lt. Commander Torc, being Klingon, invited the crew to the Klingon part of the station for some blood wine. Things were going well until a friend from the past, Captain Akul, broke up their party to accuse the Federation of stealing his Bat'leth. After a few words were exchanged, it turned out other equipment has been stolen as well. Captain Ral excused himself in order to confirm this with Admiral Walker. Akul tasked the party to investigate his missing Bat'leth and find who was responsible.
This lead the team into a search of the missing gear. In addition to the bat'leth, a random assortment of items were reported missing: medical supplies, firearms, parts for ships, etc. The crew first began their investigation by searching Captain Akul's quarters. However, this turned up no clues.
Meanwhile, part of the crew went to the cargo bay to speak to Lt. T'Kot (Quartermaster) in the cargo bay where the gear went missing. T'Kot insisted he doesn't know how things went missing, only noting that he was awaiting parts to repair the transporter that had been busted for the past couple of weeks. While talking with the party, Doctor Jerrynn noticed an unusual twitch occurring on T'Kot's face. When asked about, T'Kot got a little defense, well as defensive as a Vulcan can get. Scans by science officer Wegen were inconclusive, though he figured something was off on the scan. Dr. Jerrynn relieved T'Kot of duty and ordered him to sickbay for a full physical, which he complied.
While T'Kot was being escorted to sickbay, the crew did a very thorough scan of the cargo bay and found something quite unusual. An ancient piece of technology, one resembling the technology recently discovered on previous missions, was found attached to the transporter. This device seemed to mask and erase any evidence of transporter activity from that pad, including masking its activities from the station log as well.
Back in sickbay, just as the scans on T'Kot were nearly finished, he seemed to suddenly melt into a puddle and escape sickbay. T'Kot, it turns out, was in fact a Changling! The crew immediately notified the station ops, who put the station on red alert.
The crew, with assistance by the station, was able to track the Changling to an empty science lab near the actual T'Kot's quarters. Once security measures were in place, a scan of hurtful energy beams was swept across the lab, finding the Changling in the corner disguised as a common house plant.
With the Changling captured, he was transferred into a bucket and taken to a secured prison cell. After several hours, the Changling finally emerged from the bucket and was interrogated. The crew found out this Changling was working for the XO and was stealing parts for the pirates in the XOs employ. This was about as much information as they cagey Changling was willing to give up.
The plot thickens with the XO. Who are they? Where are they located? And other than sewing discord between allies, what is their purpose? Join us as the crew of the Tiberius continues their investigation into these and other questions!
Monday, April 27, 2020
Monday, April 13, 2020
Signals Part 2
The crew of the Tiberius, after debriefing with the leader of the settlement Ero, received a distress signal from the Susquehanna. The signal originated about 1 light year deeper inside the nebula, which has caused the distress signal to become garbled.
With warp speeds not advisable in the nebula, the crew set off at full impulse toward the signal, knowing the Romulans are still out there but unaware of the dangers located inside the nebula. A game of cat-and-mouse ensued as both the Tiberius and the Romulan Warbird Veritex search for the Susquehanna. Shortly after launching, the Tiberius, unfortunately, ran into a pocket of metrionic gas, causing some further complications on their journey. After encountering, and dodging, some debris, the Tiberius was able to find the Susquehanna first.
As the crew scrambled to lock a tractor beam onto the Susquehanna, the Veritex arrived and immediately hailed the Tiberius. After not answering their demands, a fire-fight broke just after the Susquehanna was rescued. Luck was on the side of the Tiberius, and they were able to chase the Veritex away after a few rounds of fire were exchanged.
Meanwhile, Dr. Jerryann raced to the shuttle bay with his team of doctors to treat the crew of the Susquehanna. Thankfully, the Tiberius arrived in time to save the remaining 2 crew members, who were on the verge of being unconscious and looked malnourished. Dr. Jerryann and his team were able to stabilize the crew members without many problems.
Meanwhile, Chief Science Officer Wegen and Chief Engerineeer Foxwell scanned the shuttle to determine what had happened to the Susquehanna. They were able to determine that the Susquehanna was blasted by the same blue energy bolt that dropped their (and the Romulan) shuttles on Seku VI. They were also able to determine that this bolt of energy was what caused the transporter accident that killed the other 2 crewmembers.
Once all was secured, the crew headed back to Seku VI to warn the settlement about the Romulan threat in the area. Ero thanked the crew for the warning and said they would contact Starfleet should they want or need further assistance.
The Tiberius was then ordered back to Narendra station to make some much needed repairs to the ship (top speed has been limited to Warp 6 and the runabout needs repairs). The crew was also offered to use the time at Narendra station for some much needed R&R. However, before getting there, Admiral Walker broke the news to Dr. Jerryann that, effective once he arrives at Narendra Station, he will be promoted from Lieutenant to Lieutenant Commander for his outstanding work onboard the Tiberius.
What will await the crew of the Tiberius once at the station? Will it be a time of fun and relaxation? Or will something cut into their R&R? Tune in next time for the continuing adventures of the USS Tiberius!
With warp speeds not advisable in the nebula, the crew set off at full impulse toward the signal, knowing the Romulans are still out there but unaware of the dangers located inside the nebula. A game of cat-and-mouse ensued as both the Tiberius and the Romulan Warbird Veritex search for the Susquehanna. Shortly after launching, the Tiberius, unfortunately, ran into a pocket of metrionic gas, causing some further complications on their journey. After encountering, and dodging, some debris, the Tiberius was able to find the Susquehanna first.
As the crew scrambled to lock a tractor beam onto the Susquehanna, the Veritex arrived and immediately hailed the Tiberius. After not answering their demands, a fire-fight broke just after the Susquehanna was rescued. Luck was on the side of the Tiberius, and they were able to chase the Veritex away after a few rounds of fire were exchanged.
Meanwhile, Dr. Jerryann raced to the shuttle bay with his team of doctors to treat the crew of the Susquehanna. Thankfully, the Tiberius arrived in time to save the remaining 2 crew members, who were on the verge of being unconscious and looked malnourished. Dr. Jerryann and his team were able to stabilize the crew members without many problems.
Meanwhile, Chief Science Officer Wegen and Chief Engerineeer Foxwell scanned the shuttle to determine what had happened to the Susquehanna. They were able to determine that the Susquehanna was blasted by the same blue energy bolt that dropped their (and the Romulan) shuttles on Seku VI. They were also able to determine that this bolt of energy was what caused the transporter accident that killed the other 2 crewmembers.
Once all was secured, the crew headed back to Seku VI to warn the settlement about the Romulan threat in the area. Ero thanked the crew for the warning and said they would contact Starfleet should they want or need further assistance.
The Tiberius was then ordered back to Narendra station to make some much needed repairs to the ship (top speed has been limited to Warp 6 and the runabout needs repairs). The crew was also offered to use the time at Narendra station for some much needed R&R. However, before getting there, Admiral Walker broke the news to Dr. Jerryann that, effective once he arrives at Narendra Station, he will be promoted from Lieutenant to Lieutenant Commander for his outstanding work onboard the Tiberius.
What will await the crew of the Tiberius once at the station? Will it be a time of fun and relaxation? Or will something cut into their R&R? Tune in next time for the continuing adventures of the USS Tiberius!
Monday, March 30, 2020
Signals Part 1
The crew was tasked to investigate a strange alien signal and the missing runabout, the Susquehanna. After traversing the Nebula and after performing their initial scans of the planet, Seku VI, the players were able to locate the source of the alien signal, as well as the comm-badges of 2 Starfleet Officiers.
As the players were about to make their way to the surface, the runabout was attacked by a Romulan shuttle. After a brief fire-fight, both ships were hit with a burst of energy that emanated from the planet. Both ships lost power and crashed to the planet.
Thankfully, the Atilla was being steered by Ens. Farragut, a top-notch pilot, and he was able to safely crash land the shuttle with out causing injuries to the crew.
Once planet-side, the crew found the comm badges and the crew members who belonged to them. Unfortunately, the 2 crew members appeared to have died in a terrible transporter accident.
Knowing that the Romulans crashed nearby, the away team decided to search for them. However, the Romulans had the same idea and a fight broke out on the planet. However, the away team made fairly quick work of the Romulans, and after a brief questioning session (which yielded nothing of interest), the crew set off to investigate the signal.
The crew set out for their several hour walk toward the source of the signal. However, the walk was not without peril. First, a sandstorm suddenly sprung up on the team, forcing them to shelter for a bit. Only the security and engineer took a little damage from the storm. Once the storm passed, they pressed on. About an hour or two later, they came upon a ravine that needed to be crossed. With a little team work and a lending hand by XO MacKenzie, the team managed to cross the ravine safely, only losing the Doctors medical tri-corder in the process.
As they approached the signal, the away team came across a settlement in a valley. As they were surveying the situation, a rifle blast hit the rocks in front of the away team, and they were soon surrounded by 3 snipers. The away team was told to toss down their phasers and put their hands up. The team complied and was lead into the settlement and to the sniper's boss, Ero Drallen.
Ero took the team to his office where a conversation was had. Ero explained what his miners had found in the caverns below the town and asked the away team for their help. Since the team was trapped on the planet, they agreed to help as best they could.
The team was lead into the caverns below the settlement to a chamber. This chamber contained an obelisk and some computer consoles. Inspection of these devices proved nearly inconclusive, though they were determined to be quite old. In fact, the age nearly matched the age of the technology from the Rl'lowo Shal.
Chief Engineer Foxwell was able to detect an off switch of sorts for the device, and after some discussion, turned the device off. For a moment, the obelisk appeared to be powered down. However, tricorder readings suggested a surge of power was building below them, leading the team to infer that a self-destruction sequence had been activated!
Left with the decision to flee or try to stop the explosion, the team decided to stay and try to deactivate the self-destruction sequence. With only a few minutes to work with, the team was able to quickly shut down the device before it could explode!
Once back on the surface, Ero and the Away team were able to beam up to the Tiberius, now that the signal and device were shut down. Onboard, Ero and Captain Ral negotiated a peaceful agreement for the time being until an actual diplomat from Starfleet could arrive.
The crew still has the missing Susquehanna to find, but has a new lead. Tune in next time as the Tiberius races to find the Susquehanna.
As the players were about to make their way to the surface, the runabout was attacked by a Romulan shuttle. After a brief fire-fight, both ships were hit with a burst of energy that emanated from the planet. Both ships lost power and crashed to the planet.
Thankfully, the Atilla was being steered by Ens. Farragut, a top-notch pilot, and he was able to safely crash land the shuttle with out causing injuries to the crew.
Once planet-side, the crew found the comm badges and the crew members who belonged to them. Unfortunately, the 2 crew members appeared to have died in a terrible transporter accident.
Knowing that the Romulans crashed nearby, the away team decided to search for them. However, the Romulans had the same idea and a fight broke out on the planet. However, the away team made fairly quick work of the Romulans, and after a brief questioning session (which yielded nothing of interest), the crew set off to investigate the signal.
The crew set out for their several hour walk toward the source of the signal. However, the walk was not without peril. First, a sandstorm suddenly sprung up on the team, forcing them to shelter for a bit. Only the security and engineer took a little damage from the storm. Once the storm passed, they pressed on. About an hour or two later, they came upon a ravine that needed to be crossed. With a little team work and a lending hand by XO MacKenzie, the team managed to cross the ravine safely, only losing the Doctors medical tri-corder in the process.
As they approached the signal, the away team came across a settlement in a valley. As they were surveying the situation, a rifle blast hit the rocks in front of the away team, and they were soon surrounded by 3 snipers. The away team was told to toss down their phasers and put their hands up. The team complied and was lead into the settlement and to the sniper's boss, Ero Drallen.
Ero took the team to his office where a conversation was had. Ero explained what his miners had found in the caverns below the town and asked the away team for their help. Since the team was trapped on the planet, they agreed to help as best they could.
The team was lead into the caverns below the settlement to a chamber. This chamber contained an obelisk and some computer consoles. Inspection of these devices proved nearly inconclusive, though they were determined to be quite old. In fact, the age nearly matched the age of the technology from the Rl'lowo Shal.
Chief Engineer Foxwell was able to detect an off switch of sorts for the device, and after some discussion, turned the device off. For a moment, the obelisk appeared to be powered down. However, tricorder readings suggested a surge of power was building below them, leading the team to infer that a self-destruction sequence had been activated!
Left with the decision to flee or try to stop the explosion, the team decided to stay and try to deactivate the self-destruction sequence. With only a few minutes to work with, the team was able to quickly shut down the device before it could explode!
Once back on the surface, Ero and the Away team were able to beam up to the Tiberius, now that the signal and device were shut down. Onboard, Ero and Captain Ral negotiated a peaceful agreement for the time being until an actual diplomat from Starfleet could arrive.
The crew still has the missing Susquehanna to find, but has a new lead. Tune in next time as the Tiberius races to find the Susquehanna.
Sunday, March 15, 2020
Tug of War
The crew of the Tiberius, after encountering pirates, Ferengi, and an organization only known as the XO, was tasked with a scientific exploration of a pair of M-Class planets that orbit the same star. Among other things that made these 2 planets unusual is the fact that both planets are in the final stages of a planet-wide extinction event. In orbit of the planets, which has been cleared away of asteroid debris, was a derelict space station and other space debris.The crew was given the task to collect data from these planets to learn what happened.
The crew first came into a stable orbit in between both planets and made some initial scans of the planets and the space station. Then, they decided to beam over to the derelict space station and investigate it. Onboard the station, the crew found the station completely without power and no artificial gravity. The space station was fully intact but did not show any signs of a crew or its things. The only thing the crew was able to salvage were a few discs that the crew presumes store data. They also discovered that this space station was hundreds of thousands of years old. They grabbed the discs and headed back to the Tiberius.
The crew then beamed down to the smaller of the two planets, which they eventually learned was named the Rl’lowo Shal. The planet was nearly fully dead. Just a few planets and fish were remaining alive. Buildings and cities were showing signs of being in ruined. The technology that they came across seemed to match the technology of the space station, leading the crew to draw the conclusion that the space station probably came from this planet.
The crew then proceeded to the other, larger planet in this system. This planet had a smaller population and only sparse technology. However, the technology matched that of the technology from the smaller planet, lending the crew to assume the technology was shared. This planet, the crew discovered, was called Five Turns and the inhabitants called themselves Us.
The crew also discovered that both world were covered in multiple asteroid craters, many of which were larger than the dinosaur killing impact on Earth from millions of years ago.
It was at this point the away team was recalled to the Tiberius as the ship was recalled in order to help search for a Federation runabout that had gone missing.
As the ship attempted to break orbit, 2 powerful tractor beams locked onto the ship. Both beams emanated from the planets: one from each. The ship was trap! As the crew scrambled to figure out what happened and to assess the damage, the ship took some significant damage. Shields were dropped along with taking a breach to both the sensors and the engines. The crew struggled to keep the ship together as the structural integrity fields was starting to fail. As engineering teams enacted repairs all over the ship, and medical teams tended to the wounded, the crew devised a plan to send a beam out through the deflector dish to negate the tractor beams. This plan worked and the ship, albeit beaten up pretty bad (the ship's top speed is now just warp 6), they were able to move away from the beams.
Just as they were starting to leave, more alarm bells started to go off as a Romulan Warbird decloaked off the port side of the ship. The commander of the Warbird claimed the Tiberius was in Romulan space (they claimed this system as theirs). A verbal confrontation occurred, but as the Tiberius was already leaving, they just agreed to leave and let the Admirals deal with this.
However, just as the Tiberius was finally starting to leave, they were hailed by the Warbird once again as the tractor beams locked onto the Warbird. The Commander claimed the Federation did this. Another verbal confrontation occurred, but eventually ended when the Tiberius agreed to transmit the same wave frequency that freed them from the tractor beams to the Warbird. Skeptical, but not seeing many other options, the Commander reluctantly took the data and was able to free themselves. Both ships went on their way without further interactions.
The Tiberius left the system and began the search for the missing runabout, the Susquehanna, to discover what had happened to it. Come back in 2 weeks to see if the Tiberius was able to locate the Susquehanna.
The crew first came into a stable orbit in between both planets and made some initial scans of the planets and the space station. Then, they decided to beam over to the derelict space station and investigate it. Onboard the station, the crew found the station completely without power and no artificial gravity. The space station was fully intact but did not show any signs of a crew or its things. The only thing the crew was able to salvage were a few discs that the crew presumes store data. They also discovered that this space station was hundreds of thousands of years old. They grabbed the discs and headed back to the Tiberius.
The crew then beamed down to the smaller of the two planets, which they eventually learned was named the Rl’lowo Shal. The planet was nearly fully dead. Just a few planets and fish were remaining alive. Buildings and cities were showing signs of being in ruined. The technology that they came across seemed to match the technology of the space station, leading the crew to draw the conclusion that the space station probably came from this planet.
The crew then proceeded to the other, larger planet in this system. This planet had a smaller population and only sparse technology. However, the technology matched that of the technology from the smaller planet, lending the crew to assume the technology was shared. This planet, the crew discovered, was called Five Turns and the inhabitants called themselves Us.
The crew also discovered that both world were covered in multiple asteroid craters, many of which were larger than the dinosaur killing impact on Earth from millions of years ago.
It was at this point the away team was recalled to the Tiberius as the ship was recalled in order to help search for a Federation runabout that had gone missing.
As the ship attempted to break orbit, 2 powerful tractor beams locked onto the ship. Both beams emanated from the planets: one from each. The ship was trap! As the crew scrambled to figure out what happened and to assess the damage, the ship took some significant damage. Shields were dropped along with taking a breach to both the sensors and the engines. The crew struggled to keep the ship together as the structural integrity fields was starting to fail. As engineering teams enacted repairs all over the ship, and medical teams tended to the wounded, the crew devised a plan to send a beam out through the deflector dish to negate the tractor beams. This plan worked and the ship, albeit beaten up pretty bad (the ship's top speed is now just warp 6), they were able to move away from the beams.
Just as they were starting to leave, more alarm bells started to go off as a Romulan Warbird decloaked off the port side of the ship. The commander of the Warbird claimed the Tiberius was in Romulan space (they claimed this system as theirs). A verbal confrontation occurred, but as the Tiberius was already leaving, they just agreed to leave and let the Admirals deal with this.
However, just as the Tiberius was finally starting to leave, they were hailed by the Warbird once again as the tractor beams locked onto the Warbird. The Commander claimed the Federation did this. Another verbal confrontation occurred, but eventually ended when the Tiberius agreed to transmit the same wave frequency that freed them from the tractor beams to the Warbird. Skeptical, but not seeing many other options, the Commander reluctantly took the data and was able to free themselves. Both ships went on their way without further interactions.
The Tiberius left the system and began the search for the missing runabout, the Susquehanna, to discover what had happened to it. Come back in 2 weeks to see if the Tiberius was able to locate the Susquehanna.
Saturday, February 15, 2020
Convoy Conclusion
Following the attack on the convoy, the crew had many things to accomplish. First thing was to help their friend, Captain Akul, mend his ship and crew. Dr. Jerrynn and his team was able to mend most of the crew of the Mupw'l. However, one crew member appeared to have hit his head, which needed more serious medical attention. After some convincing, Captain Akul agreed to allow the crew member to be released into the crews hands for further treatments.
Meanwhile, Lt. Cmdr Foxwell and team set to work on making repairs onboard the Mupw'l. The ship sustained some damage, most serious of which affected the ship's warp drive. Foxwell and team were able to make the best of the situation, repairing the warp drive enough to allow the ship to reach warp 7, though more extensive repairs will be required in dry dock. Other more minor repairs, including to some EPS conduits and to the tactical display, were made and the crew was sent back to the Tiberius with gratitude from Captain Akul.
Once all senior staff were back on the Tiberius, the crew quickly set up a class 9 probe and sent it after the stolen cargo freighter. The Tiberius then set off with the Mupw'l to deliver the remain cargo ships to Array 3-5. However, they weren't traveling alone as the crew picked up a few guest, namely the Ferengi Captain named Solec, the captain of one of the Pirate Freighters.
After some interrogation of Captain Solec, the crew discovered the Ferengi were under orders from the group called the X.O. The Solec was only willing to provide some information, such as the XO wants to weaken the partnership between the Klingons and Federation and that the XO can't be contacted (they contact you). Solec said his partner, another Ferengi (the other freighter captain) named Leck, may have some more answers if they find him and the stolen cargo transporter.
At this point, the crew decided to contact Captain Akul to tell them that the Tiberius was going after the stolen cargo ship and that the Mupw'l was to stay behind to escort the rest of the cargo ships to Array 3-5. Captain Akul wasn't exactly thrilled to 'be left out of seeking glory' but ultimately was persuaded to continue on with the mission.
The Tiberius, based on data obtained from their probe, was able to track the stolen cargo ship to a Class-H planet. Captain Ral ordered the ship to Yellow Alert as they dropped out of warp, and a good thing he did so as another squadron of fighters attempted to attack the Tiberius. The Tiberius made quick work of the squadron and set its focus onto the stolen cargo ship.
As expected, the crew found Captain Leck (Ferengi) attempting to steal the cargo and kidnap the crew as the cargo ship was in a decaying orbit around the planet. Leck, once he was persuaded to surrender, gave the crew the time and place for where the XO was going to meet them with the stolen goods. The crew of the Tiberius decided to attempt to catch the XO using this information, but the XO never showed up. After waiting several hours, Captain Ral recalled the team to regroup.
The Tiberius then returned the rest of the cargo to Array 3-5 and set course back to Narendra station to figured out their next course of action. But who are the XO and what do they want?
Tune in next time as the Tiberius seeks more answers inside the Shackleton Expanse!
Meanwhile, Lt. Cmdr Foxwell and team set to work on making repairs onboard the Mupw'l. The ship sustained some damage, most serious of which affected the ship's warp drive. Foxwell and team were able to make the best of the situation, repairing the warp drive enough to allow the ship to reach warp 7, though more extensive repairs will be required in dry dock. Other more minor repairs, including to some EPS conduits and to the tactical display, were made and the crew was sent back to the Tiberius with gratitude from Captain Akul.
Once all senior staff were back on the Tiberius, the crew quickly set up a class 9 probe and sent it after the stolen cargo freighter. The Tiberius then set off with the Mupw'l to deliver the remain cargo ships to Array 3-5. However, they weren't traveling alone as the crew picked up a few guest, namely the Ferengi Captain named Solec, the captain of one of the Pirate Freighters.
After some interrogation of Captain Solec, the crew discovered the Ferengi were under orders from the group called the X.O. The Solec was only willing to provide some information, such as the XO wants to weaken the partnership between the Klingons and Federation and that the XO can't be contacted (they contact you). Solec said his partner, another Ferengi (the other freighter captain) named Leck, may have some more answers if they find him and the stolen cargo transporter.
At this point, the crew decided to contact Captain Akul to tell them that the Tiberius was going after the stolen cargo ship and that the Mupw'l was to stay behind to escort the rest of the cargo ships to Array 3-5. Captain Akul wasn't exactly thrilled to 'be left out of seeking glory' but ultimately was persuaded to continue on with the mission.
The Tiberius, based on data obtained from their probe, was able to track the stolen cargo ship to a Class-H planet. Captain Ral ordered the ship to Yellow Alert as they dropped out of warp, and a good thing he did so as another squadron of fighters attempted to attack the Tiberius. The Tiberius made quick work of the squadron and set its focus onto the stolen cargo ship.
As expected, the crew found Captain Leck (Ferengi) attempting to steal the cargo and kidnap the crew as the cargo ship was in a decaying orbit around the planet. Leck, once he was persuaded to surrender, gave the crew the time and place for where the XO was going to meet them with the stolen goods. The crew of the Tiberius decided to attempt to catch the XO using this information, but the XO never showed up. After waiting several hours, Captain Ral recalled the team to regroup.
The Tiberius then returned the rest of the cargo to Array 3-5 and set course back to Narendra station to figured out their next course of action. But who are the XO and what do they want?
Tune in next time as the Tiberius seeks more answers inside the Shackleton Expanse!
Saturday, February 8, 2020
Tiberius and Crew Stats
This is a work in progress, but here are some stats about the USS Tiberius and her crew:
USS Tiberius
NCC-74662
Service Date: 2368
Space frame: Nova Class
Mission Profile: Multirole Explore
Systems:
Engines 9
Computers 10
Weapons 8
Structure 8
Sensors 10
Communications 10
Departments:
Command 2
Security 2
Science 4
Conn 2
Engineering 3
Medicine 2
Talents:
Advanced Sensor Suites
Improved Hull Integrity
Rugged Design
Scale 3
Resistance 4
Power 9
Crew Support 3
Launch Bay:
1 Waverider Shuttlecraft
1 Type 8 Shuttlecraft
1 Type 9 Shuttlecraft
Weapons:
Tractor Beam (strength 2) 2 CD
Phaser Array (Medium range, versatile 2, area or spread) 5 CD
Photon Torpedoes (Long range, high yield) 5 CD
Crew:
Captain Malko Ral (Joined Trill) (GM)
XO Commander Robyn MacKenzie (Human), Temporarily on assignment
Temporary XO Commander Kasan Goddard (Human)
Chief of Security/Tactical Commander Torc (Klingon)
Chief Engineer Lt. Commander Darwin Foxwell (Human)
Chief Medical Officer Lt. JG Jerrynn (Andorian/Vulcan)
Chief Science Officer Lt. Norv Shittull (Tellarite)
Helmsman Ensign Farragult (Human NPC)
USS Tiberius
NCC-74662
Service Date: 2368
Space frame: Nova Class
Mission Profile: Multirole Explore
Systems:
Engines 9
Computers 10
Weapons 8
Structure 8
Sensors 10
Communications 10
Departments:
Command 2
Security 2
Science 4
Conn 2
Engineering 3
Medicine 2
Talents:
Advanced Sensor Suites
Improved Hull Integrity
Rugged Design
Scale 3
Resistance 4
Power 9
Crew Support 3
Launch Bay:
1 Waverider Shuttlecraft
1 Type 8 Shuttlecraft
1 Type 9 Shuttlecraft
Weapons:
Tractor Beam (strength 2) 2 CD
Phaser Array (Medium range, versatile 2, area or spread) 5 CD
Photon Torpedoes (Long range, high yield) 5 CD
Crew:
Captain Malko Ral (Joined Trill) (GM)
XO Commander Robyn MacKenzie (Human), Temporarily on assignment
Temporary XO Commander Kasan Goddard (Human)
Chief of Security/Tactical Commander Torc (Klingon)
Chief Engineer Lt. Commander Darwin Foxwell (Human)
Chief Medical Officer Lt. JG Jerrynn (Andorian/Vulcan)
Chief Science Officer Lt. Norv Shittull (Tellarite)
Helmsman Ensign Farragult (Human NPC)
Saturday, February 1, 2020
A Convoy of a problem...
The USS Tiberius enjoyed a couple of weeks of R&R at Narendra Station. While most of the crew spent the time catching up on personal activities, the science and engineering crews spent much of the time upgrading the sensors on board the Tiberius and IKS Mupwl' (but let's be honest: a happy engineer or scientist is one who is working). Our Doctor spent much of his time off in the holodeck, working on his combat training. However, he also spent some time in therapy as he was struggling to come to terms with the loss of Commander Johanssen (from our last mission...sorry forgot to type up the recap for that). That was the first lost for our Doctor under his watch, and he was taking it badly.
Once R&R was over, the Tiberius brought on a temporary new XO in time to start their next mission. This mission seemed to be pretty straight forward: Team up with the IKS Mupwl' to escort some cargo ships to the joint station Array 3-5 located deep within the Shackleton Expanse.
Once underway, however, problems quickly sprung up on the Tiberius. While performing some routine scans, the Tiberius encountered some electromagnetic eddies, knocking out some EPS conduits on backup systems and reducing the overall ships power. Repairs could not be made while in space, but the Engineering team determined that, other than having a little reduced power, the ship should be able to complete their mission.
Shortly thereafter, alarm bells rang out as an explosion rocked the Mupwl'. Before the Tiberius could figure out what was going on, the Mupwl' dropped out of warp. Captain Ral on the Tiberius ordered the convoy to drop out of warp to assess the situation. As soon as the Tiberius dropped out of warp, they encountered another eddie, this time taking out some shield emitters.
With the convoy now out of warp speed, Captain Akul of the Mupwl' requested assistance from the Tiberius to help with repairs and to tend to the injured, a task the Tiberius was also needing to undertake. Captain Ral (Tiberius) agreed to send an engineering team, a medical team, and some security to assist the Mupwl'.
The away teams boarded 2 shuttlecrafts and set out for the Mupwl'. The first shuttle, armed with medical and security teams, arrived on the Mupwl' and began to assess the situation. Before the second shuttle, which was filled with the engineering team and equipment, could reach the Mupwl', 2 pirate freighters and about a dozen single-seat fighters suddenly appeared. A massive firefight has broken out!
Luck was on the side of the Tiberius and Mupwl' as they ultimately came out victorious in the battle. However, the numbers were not on their side, and 3 of the fighters and 1 of the freighters were able to hijack one of the cargo ships and made a run for it.
With most of the fighters disabled, and the remaining pirate freighter also disabled, what will the crew do? The action will continue in 2 weeks!
Once R&R was over, the Tiberius brought on a temporary new XO in time to start their next mission. This mission seemed to be pretty straight forward: Team up with the IKS Mupwl' to escort some cargo ships to the joint station Array 3-5 located deep within the Shackleton Expanse.
Once underway, however, problems quickly sprung up on the Tiberius. While performing some routine scans, the Tiberius encountered some electromagnetic eddies, knocking out some EPS conduits on backup systems and reducing the overall ships power. Repairs could not be made while in space, but the Engineering team determined that, other than having a little reduced power, the ship should be able to complete their mission.
Shortly thereafter, alarm bells rang out as an explosion rocked the Mupwl'. Before the Tiberius could figure out what was going on, the Mupwl' dropped out of warp. Captain Ral on the Tiberius ordered the convoy to drop out of warp to assess the situation. As soon as the Tiberius dropped out of warp, they encountered another eddie, this time taking out some shield emitters.
With the convoy now out of warp speed, Captain Akul of the Mupwl' requested assistance from the Tiberius to help with repairs and to tend to the injured, a task the Tiberius was also needing to undertake. Captain Ral (Tiberius) agreed to send an engineering team, a medical team, and some security to assist the Mupwl'.
The away teams boarded 2 shuttlecrafts and set out for the Mupwl'. The first shuttle, armed with medical and security teams, arrived on the Mupwl' and began to assess the situation. Before the second shuttle, which was filled with the engineering team and equipment, could reach the Mupwl', 2 pirate freighters and about a dozen single-seat fighters suddenly appeared. A massive firefight has broken out!
Luck was on the side of the Tiberius and Mupwl' as they ultimately came out victorious in the battle. However, the numbers were not on their side, and 3 of the fighters and 1 of the freighters were able to hijack one of the cargo ships and made a run for it.
With most of the fighters disabled, and the remaining pirate freighter also disabled, what will the crew do? The action will continue in 2 weeks!
Subscribe to:
Posts (Atom)