This is troubling. The search for Spegg and the survival pod has been hindered by inconsistencies in the data we’ve received from the scans.

Unusual as it may sound, the scan data shows numerous inconsistencies in “preferred object size” numbers from scan to scan. I can’t rule out failing system code or software or calculations, given that Spegg engineered a fairly devastating systems crash prior to departing the ship. This seems strangely different. Something isn’t right. Since systems native to a deep-space vessel like the SM5 have enormous fault tolerance, as well as both roll-forward and roll-back recovery for different catastrophic error situations, it is almost as if some objects kept appearing and disappearing at random. At one earlier point, I altered the scans to return object numbers using the mass and density data for the SM5 herself. I waited for several hours before an ongoing scan returned an exact match. Thinking it might have been another ship arriving, I jumped at the nav system monitor and tried to lock in the location data. In an instant, it was completely gone.

Adding an increased level of confusion to the situation is the fact that the ship’s communications array also picked up a signal fragment at the same time. Due to the duration and content, however, this may be simply a signal reflection. I am well aware that space is an extraordinarily unpredictable environment, but even for extreme deep space, this is an unusual set of occurrences. My plan is to put these concerns aside for now. I have a fish to catch.

[Communication sent: 30DEC2185 Shinkai Maru 5]    Send article as PDF