SS Peedy Thor PTRP012 "Uneasy Future" 180602

Originally Named for Admiral Peedy Thor. The Sovereign Class ship is assigned to protect and serve United Federation Starfleet. With a dual assignment of both exploration and defence, The ship is available to serve a multitude of needs for the Federation.

USS Thor and it’s crew are on a ‘protect and serve’ mission in the deepest parts of the Delta Quadrant, championing the Federation’s philosophy and ideals under the motto ‘For Those That Came Before’

Roleplay Times: Thursdays at 1330 Pacific Time, Alternate Tuesdays at 1100 Pacific Time
Commanding Officer: Draco Dimanovic
Executive Officer: 3249Rowena Resident

Moderators: 3249Rowena, Draco Dimanovic

Post Reply


Mission Name: Uneasy Future
SS Peedy Thor Mission PTRP012
Stardate: 180602
Mission Time: 1pm slt
Prepared by: Comm Ravyn Stormchyld/Comm Kermie Mistwallow
1. Mission Briefing
2. Status Report & Current Orders
3. Important Participation Notes
4. Supplemental Information
5. Uniform of the Day


With all that has been going on, I am not sure how much more the crew can take. They are the strongest bunch I have ever served with but where is our breaking point. With the station almost falling out of orbit and the new problems that occurred with the plant, I am not sure our survival is an obtainable goal at this point.

The crew is returning for duty after the plant almost killed 90% of the crew. We have started getting odd diagnostic reports from Operations. Some files have been deleted and some seem to be duplicated or out of place in the file system. Nothing seems to be affected as far as the station operation goes, but it is still strange that this would happen now. How could this have happened, especially when most of the crew was in sickbay or make shift wards throughout the ship.

Location of RP: SS Peedy Thor
Meeting Brief Location: Operations Deck
Alert Status: None
Damage: Bulkheads are still being repaired. Completed about 80% of the repairs to the hull. There are still some areas that are sealed off awaiting repairs. We have limited power back to the station but should not effect normal duties.

STARTING OBJECTIVES ( * = indicates leading assignments)

Operations: Make sure our systems stay up and running.

Engineering: Ascertain the damage to the station and begin damage control to effected areas.

Science: Work with Operations to determine the corruption of data in our core.

Medical: Begin physicals on the crew. Double check for any signs of return of the illness from the spores.

Security: Maintain security on the Engineering teams and secure damaged areas. Routinely check in on our guest in the brig.

Marines: Start prepping for tactical drills, these plants came from somewhere and we need to be prepared if their creators decide to pay us a visit.

Cadets: Assist where directed

Ships Assisting: None

Remember: Q does not serve on the ship. Be creative with your solutions to issues. Its not about 1 person, we are a crew and as a crew we need to overcome our obstacles, together.

1) Joining in late? Not sure what to do? Talk with others in your branch/division/department to be briefed. If they are unavailable, contact Rich Lombardia or Ravyn Stormchyld to get an update and request assignment.
2) Have a major twist you'd like to implement? IM the Mission Creator (who wrote the briefing)
3) SCS combat system is required.


Confused about the mission? In this section, you'll find background supplemental information about our mission, the area of space we're in, supporting ships, and so on that you can use to help build atmosphere and add detail when participating or to your logging, if you like!
We have had some extreme conditions lately on the station, see above for full details.

=/\= Uniform of the Day =/\=

Uniform of the day will be Duty Uniform



Comm Ravyn Stormchyld
Lt Cmdr Brittany Buttons
Commander T'Prain
Lt Cmdr Yaria Carmona
Ensign aadazriamel

Operations reports that large chunks of information has been either copied or deleted from our computer core. From what they could track down it was sensitive files on our movements, security codes for some of the fleet line, personnel files, and some of our protocols. The hacker was very careful in covering his or her tracks so we have no idea who did it.

During all this, Emerick Kearne escaped from the brig, bypassed security lockouts on his ships mooring clamps and began to escape. With great haste, we departed on the USS Mjolnir to track down and re-apprehend the fugitive. We tracked him toward the Khitomer wormhole, and despite his trying to scatter is ion trail, Ops was able to determine that he changed course to the Hapke Cluster. Is this just coincidence or did he have something to do with the missing data?
Post Reply

Return to “USS Thor”