REPORT: Fallion Asteroid Belt - Stardate: 89592.1

Subspace Network Reports
1
Stardate: 89592.1Report submitted: Commander Alegro - USS October

TO: Task Force Argo Command

The U.S.S. October alongside the U.S.S. Valley Forge responded to the glitches reported on the Light-House satellites along the Fallion asteroid belt. Both vessels arrived at approximately 1730 hours, October Shipboard Clock, and instantly both began close-to-medium range scans of the area inside and around the Fallion asteroid belt. Nothing exceptional was detected nor recorded for long term usage **based upon known elements matching the most recent reports of the sector, and there for no need to update currently** However, the western side of the belt was a little sensor fuzzy and thus a class 4A- probe sweep was conducted. After a brief relapse of static from the readings, it soon eased into a more readable result, and showed us a slimmer of Beta Frexil particles had built up. They indicated no immediate threat, therefor were logged down to be analysed back on Starbase Argo.

The U.S.S. Valley Forge then proceeded to run the perimeter of the asteroid belt while the U.S.S. October continued on her flight plan straight into the belt. After approximately 10 minutes of continued scanning and caution, the U.S.S. Valley Forge had reached one of the several Lighthouse satellites positioned inside the belt. After initiating a scan of the satellite, it was reported that it was functioning correctly, and close to -if not- 100% operational status. At this point the U.S.S. Valley Forge deployed the assigned Aquarius escort vessel away from the mother ship - presumably to conduct further, closer, scans of the belt.

The U.S.S. October soon reached a second satellite - conduction a similar sweep of the area and the satellite itself. The same conclusion was achieved as the Valley Forge, the satellite showed no signs of fault, and appeared to be 100% operational. Incidentally, the same was then said for the other three satellites in the asteroid belt. It became quite clear that there was no fault with the machines themselves, and our job there was done. However. After running through a final sweep of the area, U.S.S. October discovered the larger portion of what was believed to be a hull of a vessel - while being rather abrupt - and didn't appear to be of Federation origin. After a further detailed scan was conducted, the vessel was incredibly damaged and now had become the same as the light debris floating beside it. It isn't clear, but it was believed among the head science team that the hull hadn't been there long. A number of weeks at most. Following this, Captain Morton decided all that we could do there for the time being had been done, with the satellites being operational, it was best just to return to Outpost Argo and report the findings as soon as possible. As soon as we return to the Outpost, this report shall be posted.

Commander Allegro, T.
On behalf of Captain Morton
U.S.S. October

2
Stardate: 89592.4Report submitted: Commander tr'Khnialmnae - RRW Bloodwing

TO: Task Force Argo Command

The U.S.S. Valley Forge alongside the R.R.W. Bloodwing responded to the malfunctions reported on the Light-House satellites along the Fallion asteroid belt. Upon arrival, both vessels began close-to-medium range scans of the area inside and around the Fallion asteroid belt. Valley Forge took the interrior arc, while Bloodwing managed the exterior arc. U.S.S. Valley Forge deployed the assigned Aquarius escort vessel away from the mother ship once on the far side of the beld, while Bloodwing deployed her Scorpion fighters.

After approximately 5 minutes of continued scanning and caution, the U.S.S. Valley Forge had reached one of the several Lighthouse satellites positioned inside the belt. A Gorn frigate was detected, though the vessel declined to heave to for boarding. The Gorn Frigate departed on course 148 Mk 54. Speed Warp 6.


The U.S.S. Valley Forge soon reached the remains of a second satellite. Sensors showed that there were no weapons used, indicating that it was a probable asteroid impact which cause the unit's destruction.

The remaining three sattelites were located on the opposite side of the field along Bloodwing's path. All three sattelites were inoperative, yet started up when properly triggered. Diagnostics and external scans showed that there were no detectable malfunctions. This suggests outside interference - possibly the same Gorn Frigate which escaped - in deactivating the sattelites.

3
Stardate: 89592.7Report submitted: Lieutenant Hob - U.S.S. Semmelweis

TO: Task Force Argo Command

The U.S.S. Semmelweis departed Outpost Argo for the Fallion system and was joined en-route by the U.S.S. Freya.

Upon reaching the Fallion system, the Semmelweis proceeded to the location of lighthouse 413. The Freya, acting as escort, maneuvered to cover the Semmelweis' belt-facing flank. While proceeding to the lighthouse's location, the Semmelweis conducted several long-range scans, finding no relevant information. Upon reaching short-range scan distance of lighthouse 413, however, the ships picked up signatures belonging to Gorn vessels. The Freya moved to engage, destroying two Gorn corvettes that moved to engage. The third Gorn vessel, a support craft, remained near the lighthouse until the Freya and Semmelweis approached after destroying the support craft's escorts. Thereupon, the final Gorn ship attempted to flee. This attempt to flee was unsuccessful; the Freya successfully detonated the Gorn ship's warp core before warp could be achieved.

Science and engineering teams aboard the Semmelweis began intensive scanning of lighthouse 413. When scans brought up no anomolies or malfunctions, an away team was beamed to the lighthouse's exterior to investigate. Evidence that the Gorn had been attempting to tamper with the satellite was found, but the attempt appeared to have been unsuccessful. The away team returned to the Semmelweis, and both ships proceeded to lighthouse 411.

The Semmelweis, escorted by the Freya, proceeded to scan and investigate lighthouses 411, 409, and 410 in that order. Each lighthouse was found dormant but was easily restored to active status with no issues arising. The Semmelweis and Freya crossed over the belt before investigating lighthouse 410, as it and 412 were on the other side of the belt.

After approaching lighthouse 412, the Semmelweis' crew spotted an unregistered satellite in position near 412. After investigating the Lighthouse, the Semmelweis maneuvered to scan this mysterious satellite. Unfortunately, the satellite exploded upon the scan's initiation. The scan produced no viable data, and the destruction of the satellite was complete so as to preclude additional scanning.

When the mysterious satellite exploded, the Freya performed an immediate damage and threat assessment and began a sweep for additional hostiles or hazards, but found none. Neither ship was damaged.

Following the failed investigation of the mysterious satellite, the Semmelweis and Freya proceeded to lighthouse 412, which was also found in a dormant state and was also restored to full functionality with no issues.

At the time of the Semmelweis' and Freya's departure from the Fallion system, lighthouses 409-413 were all in good condition and fully operational. It is, however, Commander Blathohr Ohlazlo's professional opinion that the Gorn will return to tamper with the lighthouses again, having been interrupted. The captain presumes these incidents have been the work of a larger organization than the three ships destroyed today.

Lt. Hob
U.S.S. Semmelweis