Login

Lobster · (This post was last modified: 06-08-2025, 01:35 PM by Lobster.)

Incoming Transmission
Liberty Navy, First Fleet
LIBERTY NAVY PATROL REPORT
Ensign Amelia Hale

DEPARTMENT RECEIVING: LIBERTY NAVY PATROL ARCHIVE

1. Summary. On 080916(Z)JUN835, I launched from Manhattan in a Patriot Light Fighter and joined a Navy patrol starting at West Point Military Academy. The course of the patrol took us through Pennsylvania, New York, California, Magellan, and Cortez. The patrol ended at Battleship Concord in California. The patrol consisted of one light fighter and one very heavy fighter. Our patrol leader was Lieutenant Matthew Austin. During the patrol, three encounters occurred.

2. Encounter 1, Civilian Miner (080928(Z)JUN835). A freelancer named Assay_Of_Hope flying a Kestrel was encountered in the Pennsylvania System at grid G4. A scan of his cargo and his activities showed him to be mining heavy water from the Ralston Ice Field. The freelancer was questioned if he had seen any unlawful activity nearby, to which he responded no. With the area clear on scanners and no reports of unlawful activity, the patrol departed.

3. Encounter 2, Intel on TFP Forces (080945(Z)JUN835). One Core tagged artificial intelligence probe designated 776-28X and, arriving later, one bounty hunter named Flintlocke were encountered at Cordova Shipping Platform in Magellan. The core probe indicated it was scouting for optimized trade routes into Britonia, while the bounty hunter was taking a break from running missions for the local guild. Of note, the core probe indicated it had observed Hellfire Legion remnants during the past few days, totaling a force of three fighters and one gunship. The sightings had happened in Magellan, Coronado and New York. Additionally, the probe relayed that the Hellfire Legion forces were seen collaborating with the Technocracy. None of these contacts were active at the time of the report. After a final exchange of pleasantries, the patrol departed for Cortez via California.

4. Encounter 3, Zoner Colony Ship in Cortez (081018(Z)JUN835). A Zoner Battleship was encountered at grid D4 in the Cortez System. The ship was captained by a Saule Khalid. The resulting conservation mainly revolved around Zoner politics in the Omicrons, and events transpiring over the past ten years. Of note, the Zoner requested access to Liberty Space for his ship, stating the reason to be for sight-seeing and transit. He was directed to contact the Liberty Government to request official permission before transiting into house space. After some conversation, the patrol departed for California and concluded at Battleship Concord.

5. Logs are attached to this report in Annex A.

6. The point of contact for this report is ENS Amelia Hale at amelia.c.hale3943.nav@libertynavy.mil.

Annex A. Flight Logs

AMELIA HALE
ENS, NFO
1ST Fleet, Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Cypher · (This post was last modified: 08-11-2025, 02:30 PM by Cypher.)

***INCOMING TRANSMISSION***

COMM ID:Capt. John Hemmingway
TARGET ID:Liberty Navy High Command
SUBJECT:Patrols have been quiet so far.
ENCRYPTION: High
PRIORITY: Normal

Evening, Command.

Patrols have been relatively quiet, nothing of importance to report. There hasn't been an awful lot to do out here, not even a passing Junker.

Signing out,
Capt. John Hemmingway
Liberty Navy, First Fleet

[Image: latest?cb=20110801072539]

Important: This communication remains the property of the Liberty Defense Forces and is subject to the jurisdiction of the Neural Net Communications Act 807A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

***TRANSMISSION TERMINATED***

GnollPetter · 06-28-2025, 12:40 PM,

Incoming Transmission
Liberty Navy, First Fleet
LIBERTY NAVY PATROL REPORT
Ensign Theodore Barlow

DEPARTMENT RECEIVING: LIBERTY NAVY PATROL ARCHIVE

1. Summary. Launched from West Point to intercept rogue battlegroup, met other liberty forces on route and overheard a very choice comment made which has been included below for posterity. On route, met Freelancer(?) with malfunctioning Transponder, when questioned they said they didn't like to fly with it on. As we were in formation and on the move we moved on. Recommending Liberty Security Forces do a follow-up investigation, included are logs below. Mission Completed, and we returned to Cordova Shipping Platform for Schnapps.

Included Flightlog

THEODORE BARLOW
ENS, NFO
1ST Fleet, Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Lobster · (This post was last modified: 07-10-2025, 05:02 PM by Lobster.)

Incoming Transmission
Liberty Navy, First Fleet
LIBERTY NAVY PATROL REPORT
Lieutenant Amelia Hale

DEPARTMENT RECEIVING: LIBERTY NAVY PATROL ARCHIVE

1. On 100400(Z)JUL835, a patrol of Pennsylvania was ongoing consisting of the Overlord Class Dreadnought Waimea commanded by ADM Cleveland, the Archer Class Cruiser Leyte Gulf commanded by CPT Shiv, and a patriot in escort piloted by myself. We were moving near the Ralston Ice Field when a pirate began demanding tolls for the usage of the New York gate over system-wide comms. I moved to investigate, finding a Barnacle.;.;.: Liberty Rogue Destroyer blocking the gate. After a brief conversation, I retired to Erie where ADM Sophia coordinated the response, moving to her personal fighter so that we could assist the Leyte Gulf in the upcoming engagement.

2. I moved back to the New York gate once coordination was complete, relaying information on the destroyer's load-out before the engagement. Barnacle.;.;.: seemed to be piloted by a rather easy-going captain, not firing immediately and only demanding a mild toll, and so we engaged in some banter while the others were arriving. As soon as the Archer moved in from the tradelane though, weapons fire was initiated, and so all three ships engaged the Liberty Rogue Destroyer.

3. The destroyer fled through the Pocono Asteroid Field, ping-ponging around the jagged rocks and making shots from the archer as difficult as possible. After a brief period where all three of our ships were engaged with the lone destroyer, ADM Cleveland moved away from the fight due to technical issues, leaving the Leyte Gulf and myself to continue the engagement. What resulted was a long, drawn-out chase. One important item of note: The Patriot I was flying only had one debilitator, and so it was extraordinarily difficult for my ship to maintain constant pressure on Barnacle.;.;.:'s shields. I adapted to this by committing to each attack run aggressively, placing an emphasis on firepower over my own ship's safety. This worked to a limited degree, and between Leyte Gulf and myself, we were able to get the Pirate ship's shields down, though this took a good fifteen minutes to accomplish and at the cost of many nanobots on my part. Another Navy ship, the Praetorian, began to arrive as we had finally whittled the destroyer's hull down to a mere sliver. ADM Cleveland ordered the ship to stand by.

4. At this point I made a critical mistake. I redoubled my aggressive flying to reduce the destroyer's shields, so stubbornly clinging to life, so that the Archer could put the finishing blow into it's hull. I did not notice the asteroid looming on the right side of the Patriot until it was took late. I impacted, bouncing directly into the Barnacle.;.;.:'s kill zone with my shields already down. To his credit, the Barnacle.;.;.:'s gunnery officer made good on the opportunity. My ship disintegrated around me, and I jettisoned into space. At least I have plenty of time in my escape pod to write this report. I now await my scolding, which is sure to come after making such an error.

5. Logs are attached to this report in Annex A.

6. The point of contact for this report is LT Amelia Hale at amelia.c.hale3943.nav@libertynavy.mil.

Annex A. Flight Logs

AMELIA HALE
LT, 1FLT
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Perfect Gentleman · (This post was last modified: 07-20-2025, 05:52 AM by Perfect Gentleman.)

Incoming Transmission
Liberty Navy
First Fleet
Lieutenant Matthew Austin

Report of 20/07/835 - ZDF encounter on Erie planet orbit

On the night of July 20, I was on night watch at the gate to New York in the Pennsylvania system. During a routine overflight, I received an alert from orbit of the planet Erie, indicating an ongoing battle between local patrol forces and a large Militant ship. I responded to the alert and headed to the planet, finding Lt. Jenkin Shiv engaged in combat with a Q-Class ship - Fearless.

I immediately came to the aid of the allied ship and, during a brief battle, we managed to hit the enemy ship, taking it away from the planet's orbit beforehand. I then docked with the battleship Alma, where my ship is undergoing refueling and a standard maintenance inspection. Scan and black box data attached.

Attachment files:

Photo and scan materials

Blackbox data

Matthew Austin
Lieutenant
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Cherry Blossom · (This post was last modified: 07-27-2025, 01:51 PM by Cherry Blossom.)

Incoming Transmission
Liberty Navy, 1st Fleet
Admiral Sophia Cleveland

FOR 1FLT ADMIRALTY EYES ONLY

Esteemed colleagues of the Admiralty. Yesterday I have sent a communique to Commodore Edwards of the Fourty-Sixth fleet. He has served under my command in the 5FLT for some time before his transfer. I have taken the liberty to inquire about the current border-situation and I have to honestly say that I am shocked with what I have read. He has given me access to an after-action report of a recent conflict in Galileo.

After reading through the presented logs of the report, it came to my attention that Fleet Admiral Kemp-Smith has taken it into his own hands to break the fragile peace with Kusari. We have had border skirmishes before with Kusari in Galileo, yet, it never ended with anyone breaching the sovereign space of the other until now. It does not surprise me that after the incursion into their space and the return to Galileo, a skirmish broke out between the Navy and the Naval Forces. Actions have consequences.

Many know me as someone who is direct and speaks her mind and I shall continue to do so. This seems like a deliberate move to cause an escalation from mere skirmishes to a full-out war. I do not need to remind you that this was done without the approval of the Government. We are the tip of the spear. Liberty points the spear and we act. The Government has yet to point us into the direction of Kusari. We should make sure to not escalate it further and I request an official investigation about this incursion of Shikoku. We can't have navy personnel actively attempting to undermine Liberty's diplomacy. Kusari is a thorn and they keep rattling sabres, however, if we give into that, we will be seen as the great evil that wishes to wage war on another house for seemingly no reason but little gain within the Galileo system.

A full on war must be avoided at all cost until Kusari invades our sovereign space and the Government points the spear at them.

Sophia Cleveland
Admiral, 1FLT
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Cypher · (This post was last modified: 08-10-2025, 08:17 PM by Cypher.)

***INCOMING TRANSMISSION***

COMM ID:Capt. John Hemmingway
TARGET ID:Liberty Navy High Command
SUBJECT:Patrol and Operational Update
ENCRYPTION: High
PRIORITY: Normal

Evening, Command.

While I continue to await word regarding a potential rank adjustment following my return from reserves, I have remained active in service alongside the 46th, particularly in the efforts to expel the Kusari threat from the Galileo system.

Patrols throughout Liberty have seen varied activity, though on the whole, the situation has remained relatively quiet. At times, there has been little more than routine monitoring, with even Junker traffic being unusually absent.

I remain at the fleet's disposal and ready to respond as required.

Signing out,
Capt. John Hemmingway
Liberty Navy, First Fleet

[Image: latest?cb=20110801072539]

Important: This communication remains the property of the Liberty Defense Forces and is subject to the jurisdiction of the Neural Net Communications Act 807A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

***TRANSMISSION TERMINATED***

Cypher · 08-10-2025, 08:19 PM,

Incoming Transmission
Liberty Navy, First Fleet
Personnel Department / Command Office
Capt. John Hemmingway

To Whom It May Concern,

Prior to my return to active duty, I was informed there would be a rank adjustment. However, no further details have been provided as to the nature or extent of this adjustment.

The last recorded change to my rank was from Commander to Captain — an advancement earned through years of dedicated service and consistent operational performance. The absence of any formal communication or clarification regarding this pending adjustment makes it difficult to reconcile expectations.

In operational environments, ambiguity leads to hesitation. Within command structures, it undermines confidence and trust. I have served the Liberty Navy with loyalty and professionalism, and I expect transparency and respect in return.

If such principles are no longer priorities within the chain of command, I will need to seriously consider my future within its ranks.

Respectfully,

Capt. John Hemmingway
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

[/font]

Lobster · 08-30-2025, 10:52 AM,

Incoming Transmission
Liberty Navy, First Fleet
LIBERTY NAVY PATROL REPORT
Lieutenant Amelia Hale

DEPARTMENT RECEIVING: LIBERTY NAVY PATROL ARCHIVE

1. Summary. On 300506(Z)AUG835, I launched in an Upholder bomber from Norfolk shipyard to conduct a patrol of the New York, Texas, and Bering systems. Moving initially through Texas to Bering, there were no noteworthy encounters. My patrol followed the trade lanes, briefly visiting the original Hamburg jumpgate as a detour, and then returned to Texas. Battleship Arkansas had a few tasks pending, and so I joined in assisting friendly forces in taking down a small Xeno presence and some minor Unioner weapons platforms. Following the completion of these tasks, I returned to Norfolk Shipyard and ended my patrol.

2. Logs are attached to this report in Annex A.

3. The point of contact for this report is LT Amelia Hale at amelia.c.hale3943.nav@libertynavy.mil.

Annex A. Flight Logs

AMELIA HALE
LT, 1FLT
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Lobster · Yesterday, 05:49 AM,

Incoming Transmission
Liberty Navy, First Fleet
LIBERTY NAVY PATROL REPORT
Lieutenant Amelia Hale

DEPARTMENT RECEIVING: LIBERTY NAVY PATROL ARCHIVE

1. Summary. On 060400(Z)SEP835, a distress call from LSF Operative DIME|Tundra was put out. As the agent explained it, a Freelancer Base in Pennsylvania under the name Nebula Technologies was under attack by heavy rogue and outcast forces. ENS Theodore Barlow was also present with me in his VHF, and so we readied to render assistance. Several other Navy units were already present, both from 46th fleet and other assorted fleets. While I launched my Upholder bomber from Norfolk shipyard to assist, a scan of the Liberty List of Approved Modular Bases revealed that Nebula Technologies is not an approved base on Liberty Space. While I have no love of Rogues or Outcasts in our space, this did put the whole situation in a legal grey area, as supplying or defending the base is against § 1.4 of the Laws of Liberty. Our dilemma was rendered moot, however, when all friendly Liberty forces were eliminated by the time myself and ENS Barlow arrived. We made a few recon sweeps, detecting four hostile capital ships, then moved away from the area.

2. Logs are attached to this report in Annex A.

3. The point of contact for this report is LT Amelia Hale at amelia.c.hale3943.nav@libertynavy.mil.

Annex A. Flight Logs

AMELIA HALE
LT, 1FLT
Liberty Navy

Important: This communication remains the property of the Libertonian Armed Forces and is subject to the jurisdiction of the Neural Net Communications Act 807 A.S, Section 30. If you have received this message in error, you are requested to contact the sender and delete the communication.

Login
Username:
Password:	Lost Password?
	Remember me