Terran Stellar Navy › Forums › Command Centre › INT.>INTEL.>O.N.I. Report 2917-2237
- This topic has 0 replies, 1 voice, and was last updated 5 years, 6 months ago by Leonard Hall.
06/09/2017 at 20:55 #26446Leonard HallParticipant
THIS DOCUMENT IS PUBLISHED IN ACCORDANCE WITH THE
TERRAN STELLAR NAVY
RECORD, ANALYZE, REPORT, ACT
SECURITY CLEARANCE LEVEL THREE
BRIDGE OFFICERS AND INTELLIGENCE STAFF EYES ONLY
OPERATIONAL DEBRIEFING FOLLOWS….
The 4LD executed a strike mission to disrupt Kralien preparations for an assault on USFP space. The objectives were to destroy infrastructure and capital ships doing maximum damage with available ordnance loadout. The division entered Erebus X from Sierra, struck Erebus sector VI, and exited sector II to Cronus.where it encountered a major fleet and several command vessels. All of the stations in sector VI and two stations in sector II were taken offline in the face of very large enemy fleets. No command ships in the area were destroyed. In sector II, TSN Lancer, under the command of Lt. Cmdr. Aramond, was badly damaged. Lifepods were ejected and recovered by the remaining ships. Once the division began to run low on ordnance, it rendezvoused with supply ships and returned to Promethean.
The 4LD was then tasked with escorting the new USFP ambassador to the Hjorden to Sierra-One-Two. In addition, the [REDACTED], designated TSN Hunter for the duration of the mission, was assigned to the division in a support role, stripped of classified equipment. The crew of the lost TSN Lancer was assigned to Hunter, with two [REDACTED] operatives observing the crew’s performance and capabilities. The ambassador paused briefly at Hjorden VI, D-46 to greet the Hjorden and take up her new duties and then proceeded to Hjorden V, S-12 to view the boarding action damage. A major Caltron force entered from Coreward including a Superswarm. All were destroyed but four Hjorden cruisers were put out of commission during the engagement.
…OPERATIONAL DEBRIEFING ENDS
CURRENT FLEET INTELLIGENCE:
Kralien forces are in suitable disarray after the deep strike into Erebus. While, strictly speaking, their assault forces are still at near-full strength and have their full command craft complements, the destruction of so many bases in Erebus is projected to scare the Kraliens into digging in a bit longer while they attempt to reactivate their bases.
This, in turn, gives 1BATDIV and Insystem Security forces more time to prepare themselves, perhaps launch a few strikes of their own to keep the invasion fleet occupied. However, Kralien and Hegemony forces are likely to continue escalating their buildup. Reports from across 2SPACFLT forces indicate the front seems on the way to a full scale engagement.
Caltron units seem to be becoming a very common sight as of late. [REDACTED] have a theory and will be looking deeper into that. All further information is withheld to personnel of CL 1.
Ambassador Fernbrook still needs transit to Hjorden IV to formally relieve Ambassador Estes. Additionally, the source of the Caltron incursion in Hjorden II needs to be investigated.
TSN Lancer’s fall in enemy territory mandates immediate action. Hegemony forces may have seized the wreck of the ship. Naturally, Terran technology cannot be permitted to fall into Hegemony hands. ONI is liaising with the Zolmari to locate and plan the extraction or destruction of Lancer’s remains.
First and foremost it should be highlighted that vessels designed for hit and run strikes should avoid allowing themselves to be swamped by mass forces. While TSNCOM tactical planners are uncertain as to whether or not a tractor beam was involved in Lancer’s destruction the vast number of ships it was engaged against, alone, certainly wore against her limited area of effect options.
It is also believed that throughout the operations that communications intended to reach the CIC were only being directed to the communications relay. In light of this and other vessel list changes, personnel who need to communicate to CIC or other ships should verify their direct-comm control keys (// whispers) follow an order similar to this:
2: TSN Sabre
3: TSN Horizon
4: TSN Viper
5: TSN Hunter
6: TSN Excalibur
7:TSN Lancer (// Drydocked)
8: All Fleet
Officers who need guidance on how to set their direct-comm keys, and who need to use these keys may ask their superior officers, or ONI-CIC personnel for aid. Remember that all direct communiques must additionally be patched through the Command Comms Relay assigned to the mission, to ensure communication encryption and transfer.
(// Comms Relay records the audio logs, if you don’t broadcast to it you won’t be in the audio logs and they will sound weird when only Xavier is issuing orders in the log!)
- You must be logged in to reply to this topic.