AAR: Dreadnought


SUBMITTED:
Stardate 94912.1
FILED BY:
LT Rizar Visynth
SECURITY:
Level 2 - Confidential


LOCATION: Azedi Dreadnought, Deep Space 13, Aldebaran Sector.

MISSION: Gather intelligence on the Azedi Dreadnought.

OUTCOME: Dreadnought successfully boarded, preliminary investigation completed.

KEY PERSONNEL:
CAPT Alistair Nimitz
CAPT Emery Quint
CAPT Benjamin Rosewood
CMDR Mischa Leveson-Scott
CMDR T’irin of Vulcan
LCDR Klaarna Daughter of J’Den
LT Rizar Visynth
LTJG Phantom Moon

NARRATIVE: The team arrived at DS13’s dry dock where the Azedi dreadnought was housed. Boarding a shuttle, we deployed to an open section of hull where interior wall and door remained intact. Utilizing EV suits, the team approached the inner hull section to determine a way into the ship. While the door had no controls to speak of, I was able to find space in the door mechanism made by damage to the outer hull. This space was large enough for a member of the crew to slip through and attempt to override the locking mechanism. After some discussion, LTJG Moon was ordered to make the attempt with my guidance. We were successfully able to release the locking mechanism and open the door. This led the team into what appeared to be an airlock for the dreadnought. CMDR T’irin was able to pressurize the airlock and gain entry into the ship.

The inner ship still had breathable atmosphere, however lifeform scans returned negative results. NOTE: Once inside, tricorders functioned normally. It appears the composition of the outer hull is what prevents Starfleet ships from scanning the interiors of Azedi Dreadnoughts. Testing on the hull sample retrieved from the dreadnought should be more conclusive. Computer consoles within the dreadnought were all surprisingly low tech in comparison to Starfleet standards. They contained physical switches, dials and buttons, similar to what one would expect from a fully analogue system. While others explored the consoles further, I ran a scan on the dreadnought to try and locate what would most likely be the engine room.

It was at this point CAPT Nimitz decided to press a button on one of the consoles he guessed to be the ‘on’ button. The console began emitting a buzzing noise, which continued until the Captain pushed it again. At this point, an unknown speaker system began to play back the seconds of conversation between myself and the Captain between the two button presses. It was later discovered to be some sort of communication system, as the same recording played upon reaching the engine room.

Having discovered the likely location of said engine room, I asked for a volunteer to accompany me. LCDR Klaarna volunteered. We were able to make our way to the specified location without incident. NOTE: In addition to the lack of digital computer displays, the Azedi Dreadnought also appears to function without any swift means of transportation such as turbolifts. It is possible the same technology used to transport Confederacy representatives to DS13 is used to quickly move ship crew around the dreadnought. However, without digital computer systems to calculate arrival points, precise movement seems unlikely. More study is required.

The engine room itself was rather large with an open section where the engine core would reside, with consoles positioned on either side of the room. From the pattern of sensors and conduits, the room we discovered could only be the engine core and power plant. The core itself appeared to be ripped up and missing large sections. Just like in the first room we explored, all control panels contained physical controls, routed through conduits on the floor. The room also contained a large tank full of verteron particles. As verteron particles are found in the center of wormholes, it is safe to assume the Azedi utilize the particles as the fuel source for their wormhole generation technology. NOTE: Based on information gathered from the engineering section, it is likely the Azedi were in the process of creating another wormhole before the ship was disabled. It appears they attempted to shut down the wormhole but ended up evacuating the dreadnought instead. It can be surmised the “missing” parts of the engine core and power plant wound up at whatever destination the dreadnought was trying to reach.

While I investigated the power process of the dreadnought, LCDR Klaarna examined the weapons systems. She discovered the veteron beam generation. CMDR Leveson-Scott was able to determine the input system for the weapon; rudimentary controls accepting manual targeting solutions based on position, speed and direction of travel. Scans of the dreadnought indicated the the beam is only able to be fired forward. Adjustments can be made to arc the beam by manipulating the angle of the equipment in the engineering section, however to a very limited degree.

After all engineering and tactical data had been recorded, Captain Quint ordered one final scan of the room before the team returned to the shuttle. The team was able to reach the shuttle again without incident and took a hull sample to bring back for further analysis.

Full details and scans taken of the Azedi Dreadnought can be found attached at the end of this report.

RECOMMENDATION: More data is required. Engineering and Intelligence teams should be put in place to scan the ship, meter by meter, until we discover everything the dreadnought has to offer. The more Starfleet understands about Azedi technology, the better suited we will be to combat them in the future if required. Discovering how the Azedi use the vereton particles to generate and utilize wormholes for instantaneous transport should be among the highest priorities. Our phase-conjugate graviton beam appears to have been successful in disabling their wormhole generation capabilities in this instance, however it is only a matter of time before the Adezi are able to adapt to this tactic. Despite their use of analogue control mechanisms, the Azedi clearly have understanding of advanced technology.

It is also this Officer’s recommendation in future situations, Officers should be reminded not to touch control panels outside of their area of expertise. While in the case of this mission the resulting actions did not prove problematic for the mission objectives or the team, fortune may not be so favorable in the future.

//ATTACHMENT// Azedisensordata.log



OOC: Thanks for having me along! I had fun! If I missed anything or anyone, it was not intentional. Just send me a message and I’ll get it corrected.
11 Likes