[Message Dump] Insurgency Navy - Internal Communications

Hi there Guest,

Existing user? Create account

Server Time (24h)

Players Online

Active Events - Scoreboard

Latest activity

[Message Dump] Insurgency Navy - Internal Communications

Nika

07-08-2020, 04:28 PM,

#185

Armed to the Teeth

Posts: 1,727
Threads: 201
Joined: Mar 2018

Incoming Transmission

ID: Captain Sapphire Lance

Recipient: Insurgency Navy Reporting Center

Subject: Enterprise maiden voyage. Combat in California and Pennsylvania.

Loading Message

Good evening.

After appropriate repairs provided on Leniex, Enterprise have relocated to California and entered active service under it's new banners, engaging in offensive operations against local heavy Naval assets in California. First target was an LSF Interdictor, LNS-Ranger that preferred to save himself and the ship's crew instead of taking actual combat it's commander expressed intention to engage in. The contact with said warships was lost at Los Angeles and it was decided not to chase it in unidentified direction. It only graced us with just a couple decoy messages.

Flight log exempt, LNS-Ranger

However, it was not long before new targets resurfaced on radar. This time, identified as Epsilon-3, Atlantis-class carrier, and PAULxW, Overlord-class Dreadnought. Due to limited availability of engine disruption support it was decided to focus on a single target instead of letting both of them to escape. Assault carrier utilised the window to engage cruise engines and leave his comrades behind, and the Overlord itself attempted little resistance, instead opting to try and surrender in the wake of the overwhelming force. I opted not to reason with the insurgent and complete the demolition of the vessel, despite it's commander pledging for mercy.

Flight log exempt, Ontario lane engagement.

Another Interdictor-class battlecruiser, Indianapolis, arrived to Riverside, as Enterprise accompanied by Beta-3 have planned to return to base of operations - and chose to fight, despite the overwhelming odds. Bravery bordering on stupidity is what constituted for their downfall. Signifying the destruction of Indianapolis, i have opted for Enterprise and Beta-3 to retreat back to initial disposition.

Flight log exempt, Riverside engagement

On the way to Fontana Freeport, a light fighter have entered scanner range and, despite all warnings, chose to close distance and engage in combat with Beta-3, but was mowed down by Enterprise's point defense batteries, allowing himself to get distracted, despite being engaged in combat.

Later this day, after being called upon by Jarvis Riddle i have directed Enterprise to Pennsylvania system. Upon joining up with Heroica in the Appalachian Asteroid Field, me and Riddle pressed on to Philadelphia station - and that is where our targets have soon appeared, the force composed of Liberty siege cruiser, assault battlecruiser Florida and assault carrier Epsilon-3, that managed to escape the grasp of Enterprise earlier. With numbers on their side and confident in their advantage thought it is a good idea to separate their attention and leave the siege cruiser to deal with Heroica, and this is what have turned the tide of battle. Having our own strike craft joining us in the heat of combat - something that Navy have been outright neglecting this entire time - Heroica and Enterprise managed to destroy the assault carrier with joint fire and force the assault battlecruiser to chose crash landing on Dudley instead of being sent back to shipyard for repairs.

Flight log exempt, Pennsylvania combat

With the conclusion of this minor incrusion both Enterprise and Heroica have retreated to Kansas, mooring to Mulvane outpost for field repairs and resupplying.

Lance, out.

|1| |2|