author note: this fluff is incomplete. Once again I grossly underestimated how long I can drag a bit of fluff out, but its two in the morning and I need to sleep so I'll finish it tomorrow, probably.
As the Navy saw the 29th century wind down, the Admiralty had begun to take stock of their current fleet and, finding plenty of room for improvement, ordered the Naval Upgrade Program of 2898. In addition to upgrading the existing fleet of cruisers and light destroyers with improved electronics and armor protection and beginning a major, and long delayed upgrade package on the fleet's perpetual flagship the Washington, this action also dictated a wave of new construction, including several "almost" all new classes meant to greatly expand the fleet's capabilities. One of these classes was the long overdue Adventurous class.
While the navy had hundreds of capital ships on the registry, the Bastion's fleet was still overwhelmingly configured in accordance with the Coastal Defense doctrine. At the time, the only ships capable of conducting or supporting an operation far beyond the Bastion's borders were the Washington and the two modified Riga class frigates Tallinn and Vilnius. And for quite a while, the Admiralty had considered this adequate, even cancelling plans to build more modern long range vessels in 2825. After all, there were no organized entities strong enough to threaten the Bastion's security anywhere within four hundred light years, and even the great houses of the Inner Sphere were by all accounts not only ignorant of the Bastion, but likewise incapable of organize a sufficiently threatening force after spending so many decades devastating each other. And even those isolated groups that had found their way to the bastion had proven easily dealt with, and their apparent backers in the Star League Ministry of Communications had seemed to lose interest by the middle of the 29th century.
Of course, simply because there was nothing to worry about beyond the Bastion's borders now didn't mean that would never change, so these deep patrols were still considered an essential duty. And as the twenty ninth century was drawing to a close, it was gradually realized that the ships responsible for the job were showing their age. The Tallinn and Vilnius were certainly capable ships, but they were by this point centuries old, and even with the refits they had received, their machinery and jump cores were so outdated that manufacturing replacement components was essentially custom work, which heavily inflated operating costs. And the Washington was the most powerful, most storied, most beloved ship in the fleet, and herself quite the grand old lady, and increasingly it seemed insane to continue to risk the heart and soul of the Navy to a possible malfunction or misadventure far from home.
So, new ships would be needed to take up the task of leading the deep patrol. And as it happened the navy had a hull and jump core that they felt could solve all of their problems.
Though the new class, to be named the Adventurous, would be classified as a frigate to reflect its long range patrol role, it would still share the same hull, machinery, and jump core of the Impetuous class and its half sister designs being developed in parallel, simply reconfigured to fit its intended role. As a long range frigate specifically intended to support an expeditionary force of smaller short ranged capital ships, this primarily meant carrying a large amount of cargo. To this end, two of the Impetuous's five transit drives were removed from the design, along with all of the Imperator-Whirlwind cannons, reducing the ship's primary armament to "only" its twenty four Kreus XXX naval PPCs. Redesigns of the interior spaces and the dorsal hull to accommodate the ship's improved storage capabilities also resulted in the Adventurous' characteristic "Humpback", a design choice made to make access to the cargo bays more convenient and thus make underway replenishment of supporting units easier. While this modification does make the ship's cargo spaces more likely to take damage in combat, designers claimed it would also have a small but measurable benefit to the Adventurous' overall survivability. At flat angles of attack, the taller profile of the Adventurous compared to her half sisters tended to draw the aim of gunners unfamiliar with the design higher, meaning more shots would tend to penetrate around the cargo bays and thus miss more vital areas. While experienced Navy personnel were unlikely to be taken in by the Adventurous' hunchback, the same could not necessarily be said for any foreign opponents. Actual simulation tests seemed to tell a different story however. While yes, aiming at the ship's perceived center of mass would mean that some shots that would have hit dead center over the ship's vitals might instead strike the relatively expendable cargo bays, it also meant that shots that would have missed low would instead be potentially striking the ships' vital points instead, making the affects of the cargo bays soaking hits a net wash at best and a disadvantage at worst. Captain Garson of the tactical studies office would describe the results thus: "It was a cunning bit of fast talking, but in the end making your ship wider and easier to hit is never conducive to survivability".
Arguments over the hunchback aside, the Adventurous class would begin entering service in 2900, and would immediately replace their predecessors on deep patrol duty, with Washington being assigned to the home fleet permanently for a few decades before going into her first stint in Permanent Ordinary, while the Tallinn and Vilnius would go through a brief period in Ordinary before being mothballed in 2905, thus freeing up their names for two new Adventurous class frigates intended to carry on their legacy.
With the introduction of the Adventurous class came a revision to how deep patrols were conducted. Initially, a deep patrol force would consist of a single mothership responsible for carrying the task force's supplies, with usually a picket flotilla of light destroyers for escort and to conduct the actual survey operations of the mission. This was fine if everything went well, but it also left the entire patrol force with a single point of failure. If the mothership was disabled by malfunction or enemy action, then depending on the distance from Bastion territory the entire patrol force could find itself stranded. Or at the very least, waiting for months for one of its number to make it back to the Bastion to send rescue. The threat of just such an incident happening to the aging Washington, Tallinn, and Vilnius had been the final push needed to even get the Adventurous built in the first place, and while the navy now had newer and potentially more reliable ships to do the job, the risk was still there.
So with the first Deep Patrol of 2900, the frigate Adventurous would be paired with her sister ship the Bonaventure, along with the standard flotilla of Hunt class destroyers. Having two motherships ensured that the patrol force was not at risk of being stranded by the loss of one vessel, and the extra space afforded by the vast carrying capacity of the two long range frigates ensured that plentiful spare parts could be carried to support any necessary repairs or maintenance issues. Using a pair of Adventurous class frigates would become standard practice for Deep Patrol missions to this day, with even the Washington's symbolic Deep Patrol in 3032 on the four hundredth anniversary of her commissioning being accompanied by the modern incarnations of the frigates Tallinn and Vilnius. The unfortunate encounter with the SLMC (or "Comstar" as they preferred to be known) explorer ship Ptolemy during that trip would see the Washington's part of the voyage cut short, but the Tallinn and Vilnius would lead the rest of the group further back along the Ptolemy's route of travel, searching for any additional SLMC ships that might have been following the Ptolemy, returning only once they were confident that there were no other SLMC ships probing close to the Bastion.
The Bastion would complete twelve Adventurous class frigates over the course of a rather sedate six year building program. Very often one pair of frigates would return from a completed patrol only to pass the duty on to a pair of brand new frigates that had just cleared their acceptance trials. As the number of available frigates grew, the navy was quickly able to maintain two active deep patrol forces at all times, greatly improving the Bastion's knowledge of the surrounding space and nearby territories like the Axumite Providence, the Hanseatic League, or the Thelos Sector. A refit of the entire class with advanced sensor systems in 2950 only improved their ability to passively monitor these interstellar neighbors, gathering mountains of data while avoiding detection themselves. Though these missions would net valuable intelligence and scientific information, their crews tended to regard them as ordinary, even painfully boring. Maintaining secrecy meant shore leave was never an option, and the occasional unavoidable encounter with a foreign vessel only offered a brief bit of violent excitement followed by decidedly hostile interaction with any survivors. Even the vast database of entertainment media the ship's computer was able to store, or the local entertainment recorded during signals intelligence missions, only offered some respite from the humdrum routine of shipboard life. While service among one of the Adventurous class was commonly billed as a prestige position, enlisted personnel might make only one or two tours aboard a frigate before requesting posting with a ship that operated closer to home.
Oddly enough, the desire to not be cooped up aboard ship for as much as two years at a time would even cause some crewmembers to challenge their own deeply held personal beliefs. By the middle of the thirtieth century, service aboard an Impetuous class cruiser, a Lee class escort, or a Pentagon assault ship required that a prospective sailor provide verification that they had received gene therapy to enhance their resistance to high gravity, along with confirmation that the therapy had properly taken hold. For the Admiralty, this was simply a practical precaution. These ships were all capable of extremely high acceleration, and ensuring that their crews could endure the force of such acceleration long term greatly increased their tactical and strategic capabilities, and as this was job related, prospective crewmen could receive the normally very expensive gene therapy at no cost.
While those who were unwilling or unable to receive gene therapy were not barred from service in the navy, their options for available postings were still somewhat limited. Those who still wanted a place on a capital ship would either have to fight for one of the scarce billets on a Formidable or Relentless, join the picket fleet, or sign up with an Adventurous. Since most of these available capital ship postings meant you would find yourself joining a deep patrol force at some point, many sailors who were once vehemently opposed to elective gene therapy would come back from a two year stint in the desolate emptiness around the Bastion with a fresh new perspective and a burning desire to serve in a posting where you got to see something other than the same people, bulkheads, and endless emptiness regularly.
Tedious or not, it was almost universally accepted that the Adventurous class was performing a vital service for the Bastion by keeping an eye on the surrounding space. While the Ptolemy incident of 3032 certainly reinforced that notion, that was nothing compared to the news that came to the Bastion in 3052. That was when the Bastion learned about the Clans.
The catastrophic, world changing psychological shock learning of the existence and origins of the Clans had inflicted on the Bastion cannot be done justice here. Suffice it to say, after reading the reports provided by the Morgan Commission, then Director General Martin's first call wasn't to the Senate or his advisors, but to the Army General Staff and the Admiralty. Passing on the information he had received, he then ordered the Bastion's top military commanders to draft a plan for an offensive war, with the stated aim of rendering these "abominations" extinct.
Fortunately, this objective was not practically viable at the time. While the Senate exploded in fiery rhetoric and panic in the public grew at a fevered pitch, the Admiralty recommended the much more restrained option of dispatching several deep patrol forces towards the rear areas of the clan incursions into the Inner Sphere, dedicated to identifying possible supply lines or, if it could be done quietly, even seizing the odd isolated clan vessel to gain more information. If possible, it was also advocated to identify a location for a forward base to support future operations. Beyond that, nothing else could be done. Neither the Army nor the Navy were equipped to simply go charging across the void to fight a war far from its own source of supply. And even if the Senate were prepared to allocate the funds for a colossal building program that would dwarf the programs that followed the evacuations from the Hegemony, it would still be years before those would pay off to make a serious attempt.
The only alternatives to this cautious approach would be the genocidally massive use of weapons of mass destruction, an option that the military made clear to the Director General that they would not support or implement.
Fortunately, cooler heads prevailed (barely) in the senate, with the vote for an immediate declaration of war against the Clans in their entirety failing by only the slimmest of margins. While the public got over their shock at how quickly their leaders had almost pushed them into a massive war hundreds of lightyears away based on centuries old grudges, the Admiralty's scout plan was approved, and four deep patrol forces centered around the frigates Adventurous, Bonaventure, Insolence, Tallinn, Vilnius, Indefatigable, Essex, and Shannon were dispatched on their long journey. While the Director General's orders included instructions to target shipping owned by the Clans if practical, the Admiralty quietly added the following addendum to each force's orders. "Absent notification of a formal declaration of war, each commander is instructed to only take hostile action against any encountered vessel if that vessel represents a threat to your ship's security or the security of the rest of your patrol force."
The fleet would not actually arrive at their patrol along the coreward periphery until early 3054. Bastion charts for this region of space had not been updated since the fall of the Star League, so extreme caution became the watchword as the fleet broke up into independent patrol forces and began surveying star systems for evidence of these clans. The primary method used was long range passive observation, with ships running minimal emissions while remaining at least twenty astronomical units from the proximity limit of the target star while their powerful sensor systems monitored for radio traffic and other signs of life. Over the course of a year, this allowed the scout fleets to identify six separate periphery outposts then under clan control, as well as collect signals intelligence from border worlds in the Lyran Commonwealth, Draconis Combine, and from the various clan occupation zones. In a bit of a strange diversion, the Hunt class THS Trahn Truk Ngo would receive special instructions to survey the Kowloon system, despite this system lying outside the original planned survey area. In addition to monitoring system communications, the captain would also order honors rendered to the birth world of the ship's namesake, before quietly slipping away to rejoin its patrol force.
Their mission complete, the fleet would meet back up again and begin the long trip back to the Bastion, arriving in mid 3055 to find a very different political situation from the one they had left. In their absence, the Blue Revolution had seen the old Senate and the Director General swept from power, along with wide reaching efforts at reforms that had left the economy and political landscape in turmoil. Reasonably certain they would come home only to find out the Bastion was now at war with the clans, they instead found new leaders committed to keeping the Bastion as far away from entanglements with the Inner Sphere as possible. Economic uncertainty and budget cuts had seen half the active fleet placed in ordinary, and most of the ships returning from their nearly three long expedition would soon join them. During these lean years following the Blue Revolution, the Admiralty found itself unable to maintain even one deep patrol on continuous rotation, and even had to fight tooth and nail to preserve the budget to send each deep patrol out with two motherships simultaneously.
Even so, the Deep Patrol continued its work where it could, probing further towards the coreward periphery, now focused on where the Clans might have come from. And in time the political and economic factors hamstringing the navy began to let up, and in time the fleet was once again operating at full capacity. These efforts would greatly expand the Bastion's knowledge of coreward regions beyond the Hanseatic League, but their search for the CLan Homworlds would come up empty. In the end, the Bastion would only learn this secret in 3060, after it had become public information in the Inner Sphere. Patrol forces would quietly poke around the edges of the Clan Homeworlds in 3062, and again in 3065, but a very close call with an unexpected task force owing allegiance to the Burrocks led to further operations in or near clan space being curtailed, and the patrol forces would instead resume concentrating on territories closer to the Bastion. While the Bastion's new government had moved away from their predecessors' barely controlled rage towards the clans, they were still willing to acknowledge that between the clans and the rapid recovery and pseudo-unification of the Inner Sphere under a new Star League, that the Bastion would at the very least find itself at risk should its own location be discovered. With that concern in mind, the Senate would vote through special funding to construct an additional twenty four Adventurous class frigates and another run of Hunt class destroyers in 3066 specifically to expand patrol efforts around the Bastion. This decision would prove especially prescient soon enough, as in 3068, news of the conflict later known as the Jihad would reach the Bastion, and roughly a year later, so would the Word of Blake.
Adventurous Frigate
Mass: 830,000 tons
Technology Base: Inner Sphere (Advanced)
Introduced: 2900 (Mark I), 2950 (Mark II-V)
Mass: 830,000
Battle Value: 83,606
Tech Rating/Availability: E/X-X-F-F
Cost: 22,270,814,000 C-bills (Mark I) 22,770,934,000 C-bills (Mark II-V)
Fuel: 2,500 tons (6,250)
Safe Thrust: 3
Maximum Thrust: 5
Sail Integrity: 5
KF Drive Integrity: 18
Heat Sinks: 3000 (6000)
Structural Integrity: 80
Armor
Nose: 231
Fore Sides: 231/231
Aft Sides: 231/231
Aft: 221
Cargo
Bay 1: Fighter (18) 4 Doors
Bay 2: Small Craft (8) 2 Doors
Bay 3: Cargo (134233.0 tons) 2 Doors (Mark I)
Bay 3: Cargo (133649.0 tons) 2 Doors (Mark II-V)
Ammunition:
2,880 rounds of Anti-Missile System [IS] ammunition (240 tons),
110 rounds of Barracuda ammunition (3,300 tons)
Dropship Capacity: 4
Grav Decks: 2 (90 m, 90 m)
Escape Pods: 20
Life Boats: 30
Crew (Mark I): 45 officers, 176 enlisted/non-rated, 47 gunners, 76 bay personnel, 20 passengers, 30 marines
Crew (Mark II-V): 45 officers, 188 enlisted/non-rated, 47 gunners, 76 bay personnel, 20 passengers, 30 marines
Notes: Equipped with
lithium-fusion battery system
1 Mobile Hyperpulse Generators (Mobile HPG)
1 Naval Comm-Scanner Suite (Large) (Mark II-V) only
1,328 tons of lamellor ferro-carbide armor.
Weapons: Capital Attack Values (Standard)
Arc (Heat) Heat SRV MRV LRV ERV Class
Nose (36 Heat)
6 Anti-Missile System 6 2(18) 0(0) 0(0) 0(0) AMS
Anti-Missile System Ammo [IS] (720 shots)
3 Capital Missile Launcher (Barracuda) 30 6(60) 6(60) 6(60) 6(60) Capital Missile
Barracuda Ammo (30 shots)
FRS/FLS (920 Heat)
4 Naval PPC (Heavy) 900 60(600) 60(600) 60(600) 60(600) Capital PPC
2 Capital Missile Launcher (Barracuda) 20 4(40) 4(40) 4(40) 4(40) Capital Missile
Barracuda Ammo (20 shots)
RBS/LBS (906 Heat)
4 Naval PPC (Heavy) 900 60(600) 60(600) 60(600) 60(600) Capital PPC
6 Anti-Missile System 6 2(18) 0(0) 0(0) 0(0) AMS
Anti-Missile System Ammo [IS] (720 shots)
ARS/ALS (920 Heat)
4 Naval PPC (Heavy) 900 60(600) 60(600) 60(600) 60(600) Capital PPC
2 Capital Missile Launcher (Barracuda) 20 4(40) 4(40) 4(40) 4(40) Capital Missile
Barracuda Ammo (20 shots)
Aft (6 Heat)
6 Anti-Missile System 6 2(18) 0(0) 0(0) 0(0) AMS
Anti-Missile System Ammo [IS] (720 shots)