AAR: Encounter with a Borg Vessel


SUBMITTED:
Stardate 94654.0
FILED BY:
CAPT S. Bishop
SECURITY:
Level 2 - Confidential


LOCATION: Aldebaran Sector

MISSION: Simulated War Games

OUTCOME: War Games concluded successfully. Borg ship defeated and data gained before the ship's eventual destruction.

KEY PERSONNEL:
CAPT Samuel Bishop (USS Endeavour)
CAPT Fiona Skye (USS MacAlpine)

CPT Eve Sharpe
1LT Gabriella Valencia

NARRATIVE:

The USS Endeavour and the USS MacAlpine participated in a round of simulated war games in order to collect data and practise battle drills on each ship. Towards the conclusion of these games, scanners detected an incoming Borg vessel. Both Federation ships moved to red alert and attempted to contact the incoming vessel. I must note here that the Borg ship was not a standard Borg design, rather a curious fusion of a KDF ship and a Federation ship. After receiving a threat of assimilation, the Endeavour and the MacAlpine quickly disabled the enemy vessel with ease. Given the ship was disabled, I decided the best course of action would be to board the ship and attempt to gather information about the Borg's intentions in the area, given our recent sporadic encounters with them over the past few months.

The away team, led by 1st Lieutenant Valencia from the Endeavour and Captain Eve Sharpe from the MacAlpine beamed across to the vessel. They encountered some resistance which they dispatched without much difficulty. I am told that the enemy they faced were not all Borg drones; a group of Engineers they faced were human in look, though scans of their brain revealed that it had been extensively rewired.

Moving to what was Main Engineering, they found that the standard Warp Core was not there, instead, the found a small box that was wired to the ship. This device seems to be an attempt at a Warp Drive; more information will be submitted as an addendum when we have been able to analyse the data.

The away team also encountered an assimilated Klingon. Whilst they did kill this Klingon, they were able to have it transported to the MacAlpine, where we are waiting on the results of an autopsy.

Unfortunately, more data could not be gathered as the ship quickly lost structural integrity and the away team returned to safety. The enemy vessel broke apart and exploded, resulting in no survivors. We received no losses and the only minor injuries were suffered by the away team.

RECOMMENDATION: More information is to follow after we have analysed the data. This event seems consistent with other events in recent months, though we are still not sure as to the extent of this problem. Disabling the ship was very easy, no doubt due to the rag-tag nature of the ship's design. My recommendation to any ships who encounter such vessels is to disable if possible and try to gain more data, if they can do so without casualties.

3 Likes

SUBMITTED:
Stardate 94674.5
FILED BY:
CMDR T'Lyra
SECURITY:
Level 2 - Confidential


LOCATION: USS Endeavour

MISSION: Examination of the Borg engine data

OUTCOME: Partial reconstruction of engine and possible data collected.

KEY PERSONNEL:
CMDR T'Lyra
CMDR Molly Faraday
LTJG Ashley Lewis

USS Endeavour Engineering and Science Officers

NARRATIVE:

The data we received used a different encryption than we did and so required some effort to extract. I believe that this is our result that should be mentioned. Rather than having the standard unified Borg matrix, the code was in a rather unusual mix of Borg, Federation typeset, and Klingon typeset, as well as having influences from other species. In short, it is believed that we are witnessing a form of incomplete assimilation. It is unknown why this might be the case.

Due to this strange coding, we were only able to partially extract the data; at first, we believed the mix of coding styles would aid our comprehension since we just had to access each type of coding and overlay it onto our code, but in practice, the coding styles were very well integrated into the system to be able to pick apart. It was, in all essence, a Borg coding, but when comparing the code with known Borg code, there was very little comparison.

Turning on the data that we did recover, we managed to access the device that was recovered. For clarity, the device is shown below. To give an indication of dimensions, the device is able to sit in a human hand, with relative ease. The dimensions are 6x6x6 inches, with a weight of 9 kilograms.

Spoiler: Borg DeviceShow
QYApk.jpg

The device seems to made to generate power to function the ship. We do not know the exact method of power generation, but we do know that the power output was 10^(4.2) megajoules per Cochrane, which, when tested in several simulations, was enough to power the ship at warp 2. We cross-referenced the device set up with all known warp drives and have not found a matching system or layout, including those of Borg vessels. We will continue to analyse the data in order to gain a better understanding of the device.

Our last area of analysis was the whereabouts of the warp drive of both the Klingon and Federation halves of the ship. Our data did not reveal much, but upon examination of the device, we noticed Federation and Klingon elements in the design. It is unknown whether this is down to coincidence when making the drive, or whether they are taken from the original ships. Without any other evidence, it is logical to assume the latter.

RECOMMENDATION: I agree with Captain Bishop's recommendation in the previous report, that is; any ships who encounter such vessels should disable and gather more data if they can do so without casualties. Furthermore, we will work with our Starfleet Intelligence Liason to further decrypt the data we have and will report with further knowledge.




OOC: Huge thanks to Master_Dex for the power output calculation!
2 Likes