Intelligence Report – 2950-CIT-05-INT-0223



Updated intelligence report
This report is an update to the mission report 2950-CIT-05-SRR-0217S and intelligence report 2950-CIT-05-INT-0222.

Data recovery data pod 341
With the help of Pilot-4512 our team was able to verify most of the data from the recovered pods. The pods were heavily damaged but the design of the pods protected about 95% of the data. After verifying with the pilot of Echolon-5 we are sure to have the copy of pod 341 as well as the scanner data from the surveillance of MIC L1.

Decryption data pod 341
The copied data is encrypted twice, one time by our pilot and the data below is encrypted with a military grade encryption. Pilot-4512 helped in decrypting our encryption level and our specialists are currently in the process of breaking the encryption on the underlying data.

Second recovered pod
The second recovered pod from the surface of Microtech contained data, which shouldn’t have existed. It contained internal and external readings of Echolon-5s systems, which is a breach of the operation protocol for these missions.
After confronting Pilot-4512 about the existence of this data, the pilot gave us plausible reason for that. Pilot-4512 did route this data to one of the pods because of the damage the ship sustained during the meteor shower. The data was needed to plot and estimate the fuel usage and time the bursts and the drop out of QT at the right moment. The data would have been deleted as soon as the ship was on a station to refuel, but due to the circumstances, there was no time to delete that data.
As the data only contained minor readings and no flight coordinated it was an acceptable deviation from the protocol, even though we need to find a different solution for similar problems in the future.
Nonetheless for the current problem the data was invaluable, as it contained energy readouts of Echolon-5 during the surveillance mission. These readouts showed a very regular burst for a fracture of a millisecond in the energy of one of the pods. Pilot-4512 ensured us, that the pod shown in the logs, was pod 341.
Currently we assume that pod 341 had a beacon planted in it, to give up Echolon-5s location.

Surveillance footage MIC L1
The surveillance footage of MIC L1 is still being analyzed. We have computers as well as personnel watching the footage and checking every possible lead. But since the footage consist of roughly 27 hours of scanner data, optical recordings, captured communications etc. It takes some time to combine all those and cross reference that with leads we already have.

Logs from the UEE
Further cross referencing the logs from the UEE with data we already have did put the similar scrambled IDs near MIC L1 during the Echolon-5 incident and also in the vicinity of our SRR mission 2950-CIT-05-SRR-0130. From the looks of it, these scrambled signatures were detected at nearly all of our missions we made after the Echolon-5 incident.

Our teams are still analyzing all data from the surveillance of MIC L1. The decryption of 341 will take another day or two, but we are on track with that. The data of the second pod gave us a very important clue and our assumption is, that’s the way how the attackers intercepted Echolon-5 and managed to perfectly hit it with EMPs. The UEE logs also show us that we may have been watched all the time by an someone unknown. All our ships will receive an updated profile to watch out for scrambled IDs and if found follow them for visual identification.