Syracuse class destroyer

Syracuse class destroyer

Though in serious competition for the more complex heavy destroyer Detroyat design, in a bid to break out as the predominate military shipbuilder in the Federation, Geering lost out to Aurora. However, this was far from a critical setback, as the company had been recently awarded the Burke frigate contract and received the lower-tier Syracuse destroyer one immediately following the Detroyat announcement. Since there were at least four times as many hulls associated with this particular victory, the other loss to Aurora was not a large cause of disappointment.

The Syracuse was relatively simple to take on, as it used the Burke-type saucer with relatively few modifications to it. It borrowed the hangerette/spinal attachment that was well underway for the forthcoming Aldrin subclass deep space frigate and incorporated Geering’s developing concept of a weapons pod, though with a permanent presence and an established torpedo tube arrangement. The nacelle pylon design was also similar, though only one nacelle was incorporated into this design.

The PB-29 warp nacelle had proven—in the initial warp tests—the capability of getting this anti-capital ship platform up to warp 5.1, with a cruise speed of warp 4. The nacelle itself massed 148,000 metric tons and came in at a length of 148 meters. Similar to the PB-21 series, it also had a Hycor deflector system built ahead of the stunted Bussard collector, providing an FTL graviton stream out forty-seven light-seconds ahead of the vessel, for obstructions up to 5 tons and up to two light-minutes for considerably smaller objects. It also carried most of the warp power generation equipment, though the nacelle pylon shared some of this responsibility.

The weapons pod was a concept developed for the Burke class nearspace frigates which Geering promoted as an installable option when heavy firepower was needed for an emergent threat. The off-hull pod idea was explored with the Syracuse, though it was not removable on this vessel, since the torpedoes served as the primary weapons system. Unfortunately, the tight space and still-developing technology meant that the pod was restricted to two forward and two rearward light torpedo tubes (though a total complement of 60 photonic torpedoes were loaded in the magazine).

Early combat engagements demonstrated the class was just not a worthy combatant alongside the Detroyats, not only because the warheads were under-inspiring, but largely due to the lack of maneuverability associated with a single nacelle warp field. Range also proved to be a considerable barrier to strategic deployment of the Syracuse assets and all three shortcomings forced Star Fleet planners to re-examine the needs of the fleet. While production of the first two runs remained authorized, Star Fleet ordered an improved model be identified and produced.

The Syracuse destroyers’ first production run honored ancient cities that had successfully resisted assaults & sieges, while the second run were named after classic Terran gods and demigods.

Saladin subclass destroyer

Due to the numerous disappointments that severely limited the Syracuse class in serving alongside its intended sister-in-arms, the Detroyat, the third production run was delayed in order to incorporate lessons learned. Intending to honor Earth warriors of the past, the subclass was designated as Saladin, after the lead new-build. Additional power generation machinery and the requisite fuel tanks replaced the hangerettes in the stern (the smaller contingent of two shuttlepods and one work pod were stored in small concealed cargo bays accessed ventrally), while the “peashooter” torpedo tubes in the weapons module were replaced with (only) two forward-facing Selenia 700mm Mk 1 heavy photon torpedo launchers. These were deemed marginally more effective, but less so than the Detroyat’s much heavier Keindoffer-Klaatsen warp launchers, which were in production shortage.

To the disappointment of the armchair admirals who claimed the saucer was too large and under-defended, the Saladin subclass had two fewer defensive lasers than the Syracuse, with the phase cannons also removed. The rationale, later proven, was the twin bank arrangement was more efficient than the single emplacements and the removed (and unnecessary) weaponry freed up space in the saucer for future equipment, even though the nature of those additions were not yet realized.

Test runs of the PB-45 nacelle on USS Saladin (NCC-500) brought the top speed up to warp 5.5, which finally allowed the light destroyers to exceed the more massive Detroyat’s 5.2 (at least until the latter’s refit in 2230), and cruise at warp 5. The ship was commissioned in 2225 with a greater length (than the Syracuse) of 226 meters, though the height and beam dimensions remained the same. The endurance afforded by the increased fuel was increased by a year. Two additional officer billets replaced four enlisted crew members.

Forty-six hulls were initially planned over four to five runs, but production was halted after the second batch was completed in 2227. Radically new dilithium-regulated antimatter technology was on the cusp of being released and it was decided that the next variant of Syracuse destroyers would be able to make efficient use of this new interpretation on variable matter conversion propulsion.

Boston subclass destroyer leader

Six years after her 2230 launch, USS Boston (NCC-425), a Syracuse-class destroyer, re-entered drydocks for a radical modification. The weapons pod was removed and a pre-built secondary hull was attached via a strengthened spinal extension and pylon to the dorsal side of the saucer. The intention, experimental in nature, was to address some of the shortcomings of the single-nacelle class from which she originated. The class had been faulted—amongst other issues—as being too slow to the “fight”, arriving well behind established task force doctrine. This, along with the ships’ lack of warp maneuverability, was to be addressed by the installation of a considerable amount of command, control, communications, and intelligence (C3I) apparatus that would enable the lead ship to focus on the battle ahead and bring in the late arrivals (typically operating in formation) at exactly the angle and attitude to instantaneous advantage.

Typically, in blue navies of old, a destroyer leader was a destroyer of larger displacement than other similarly-designated warships with which it operated, usually significantly better armed and/or armored, but still fulfilling the role of capital ship engagement. However, Star Fleet chose the appellation “leader” literally, by providing dedicated and precise combat control for generally three other Syracuse destroyers nominally assigned to a specific task force, when that task force could not be expected to “spare the horses” in order for the slower ships to maintain formation. The removal of the primary weapon for a destroyer, the torpedo launchers, was seen as necessary in order to provide the degree of battlespace awareness necessary for the delayed entrants. Instead of designing an entire new class, seen as throwing additional credits at an unplanned tactical shortfall, the Boston, Drona (NCC-431), and Rahman (NCC-434) were selected to step out of their original roles and take on the compensatory one of guiding their sisters.

The modification, surprisingly, had not decreased the ships’ original warp performance, though it did have a significant impulse maneuverability penalty. This, along with the “de-fanging” of the main weapons systems, usually meant the destroyer leader held station outside or orbited the battle, continuing to provide battlespace data updates to the friendly combatants. The addition of a useful load of auxiliary craft (18 light or 6 heavy shuttles, 2 shuttlepods, and 4 work pods) also allowed the Boston subclass ships to provide search, rescue, recovery, and repair capabilities both during and in the aftermath of a confrontation.

Einstein subclass observation ship

The C3I role undertaken by ships Boston, Drono, and Rahman starting in 2231 was deemed a qualified success. It also opened the door for a similar re-tasking of 18 of the old Texas class light cruisers (re-designated as Navigator subclass) shortly thereafter. Because there were six times as many Navigators as Bostons, it was decided to take the destroyer leader role completely from the trio and assign them, with their superior sensor suites, to the (generally) solitary observation role.

The new mission—patrolling suspect areas of hostile borders or other contested space—was an easy fit for the Bostons and by 2235, in an act normally not condoned in naval tradition, the three vessels were all re-named after scientists and engineers: Einstein, Gray, and Kelvin, respectively. To further differentiate them from the destroyer registry range in which they were embedded, they were given a prefix of the letter “O” as a reflection of their observation duties. Despite the added letter, the three were often affectionately referred to as the “zero-” or “aught-leaders”, in recognition of their brief but forward roles as destroyer leaders.

Siva subclass destroyer

Starting in 2239, the Syracuse class destroyers began a program to modernize, with the primary intent to adopt the radically new dilithium-regulated propulsion systems, much as the Burke class frigates would attempt five years later. Unlike the frigates, however, the effort was a complete success and definitely worth the expense and time. The new solid-state coils led to the introduction of the sophisticated PB-31 nacelle which was only about 10% more massive, despite the increased density of the FWD-1 (and later FWD-1A) coils.

These powerful new nacelles were not themselves directly responsible for the overly different vertical dimensions of the Siva subclass, when compared to its parent. This was attributed to the nacelle pylon—more of a mounting neck—that placed the nacelle almost three times as far from the saucer, for proper coil placement and for housing the power systems that would be normally found installed within older, spooled coil housings.

The changes to support the revolutionary new take on dilithium power required a new profile of the role of the saucer. Space would have to be appropriated in the main superstructure, more than the neck could spare, in order to provide the power the nacelle required. To also accommodate all of the operational, tactical, and support equipment the ship needed meant that the saucer would have to be redesigned. Andorian shipbuilding company Chiokis was brought in to handle the re-design.

These saucer changes were also an opportunity to adopt all new manners of other fabulous technological improvements, which helped guide the overall change in shape. Upper and lower decks were extended, allowing the addition of a prominent dorsal sensor array and the inclusion of internal torpedo launchers; this allowed the weapons sled to be jettisoned permanently. An additional partial deck was added to the rim for the Hycor DS-20 shield generator’s field guides; now, the laser emitters could be removed, since the shields were far superior in proximity defense. This, in turn, opened up additional weapons space for two more phase cannons, with the entire complement re-located into three paired banks. The navigational deflector was remounted on the ventral bulge, from a steerable strut. While not powerful enough to serve as a warp weapon, this was the intent for a cruiser design yet to be developed, and the Sivas’ could serve as an operational testbed.

Confidence was so high that not only were ten new-built Sivas funded, but all of the remaining original Syracuse ships were ordered to begin conversion, on a staggered schedule. (Three Syracuses had already been converted to the Boston/Einstein subclass, and two others had been lost in the line of duty.) By 2242, the Syracuse configuration was historical only, with its mission fully met by the Siva subclass.

Siva Flight II destroyer

In 2249, the Siva subclass was both refitted and enlarged in overall numbers, but with no new-builds. Instead, the USS Siva herself initiated the upgrades of both propulsion and tactical equipment, starting with a clean sweep of the external hull, warp nacelle, and accompanying pylon. The PB-32 nacelle provided cruise and maximum speeds of warp 6 and warp 8 (from 5 and 5.8, respectively). The weaponry was completely replaced: the torpedo systems were modified to support forced-intermix warhead supply equipment and the six phase cannons were replaced by an equal number of less massive—but far more adaptive—Type VII phaser emitters. The bridge was provided a lower target profile by being “sunk” half a deck into the surrounding deck 2 superstructure. And, for utilitarian purposes, a powerful tractor beam emitter was mounted on the pylon’s trailing edge, midway between the saucer and the nacelle.

The Siva Flight II became the iconic image of the single-nacelle destroyers, not only because of its familiar external heritage shared with the Constitution class heavy cruisers, but also largely due to their sheer force of presence: the 26 original Sivas were joined by the remaining 20 Saladins in the Flight II configuration and—crossing class identification lines—eight Monoceros (of the Hermes family). This decision to add these “cousin” ships was largely based on the need to re-balance the scout/destroyer ratio, but the pre-existing similarity between the Sivas and Monoceros played a large part in the determination. Their yard periods were longer, due to the installation of torpedo launchers, targeting computers, and six phaser emplacements and the removal of specialized sensors, and they were recommissioned with new names (though they retained their construction codes).

Despite the stellar speed performance afforded by the PB-32, the single nacelle design was still severely hampered in the maneuverability arena; the ships had to drop from warp outside the battlespace, to adjust for close combat situations at impulse—jeopardizing their survivability in one-on-one combat against more maneuverable opponents. Still, knowledge is power and awareness of these limitations helped keep the ships from finding themselves in such dire straits. Historically, the more famous casualties involved the USS Iblis (NCC-528), which—in 2259—struck USS Newton (NCC-1127) with her navigational deflector, killing 23, and the USS Azrael, which sprung an atmospheric leak pulling away from a miscalculated approach on a black star, losing 12 crewmembers.

Pompey subclass destroyer

The Syracuse / Saladin / Siva family of destroyers was developed and operated as a source of attrition units during a time of near-certainty of total war with the Klingon empire. This is not meant to say they were constructed haphazardly by any means, but that the intent of the class was to engage larger capital ships in acts of harassment in order to allow Star Fleet’s own capital ships to press advantages that might not be available in a more symmetric battle. If ships were to be lost, better it to be the smaller ones that sacrificed themselves in order that the more capable cruisers survived and persevered.

One of the well-documented weaknesses of these “cheaper” ships was its lack of maneuverability while at warp speeds. One of its proven strengths was adaption, so in the late 2250s considerable effort was made to make these ships “multi-mission capable”, a more valued attribute than a combat-focused single mission. One of the ways this was explored was by adding an additional nacelle to improve the maneuverability weakness. USS Pompey (NCC-506), a Siva Flight II, was pulled off the Klingon border and reassigned to the propulsion research group established to improve the destroyer assets. An additional PB-32 was acquired from the Nelson class spares cache and both nacelles were attached via a horizontal pylon bar meeting in a junction platform installed on the bottom of the now-shortened neck pylon.

A hangerette was slotted into the neck (at the expense of the tactical tractor) to allow more rapid deployment of the warp-enabled light shuttle (than from the previous ventral saucer cargo hatches). An additional bank of FH-11 Type VIII phasers was added to the forward dorsal saucer and two more deflector emitters joined the pre-existing array on the saucer rim. Defensive shielding was upgraded to the Hycor CS-60 standard. As the Pompey approached completion, and the low cost of such a conversion warranted further ships being upgraded, USS Sargon (NCC-504) and USS Suleiman (NCC-508) were also taken off the line for similar yard periods.

The Pompey subclass destroyers would only ever number three. Though ten more were on the verge of being ordered (also as conversions) in the late 2260s as Klingon tensions mounted, the Organian peace treaty put a stop to that. The reasoning for not changing all of the Syracuse family to this variant was simple: “it’s not enough.” Yes, the increased maneuverability was substantial and appreciated, but in the end the ship did not have the multiple redundancies that larger classes carried as a matter of course; such installations would actually reduce the present capabilities of the destroyers at considerable expense in shipyard time. Additionally, there was no way to shoehorn the laboratories, minimal auxiliaries, sensors, and supporting computing power a true multi-mission platform required. The Pompeys would excel at deep space escort, without a doubt, but such conversions of mission would then leave Star Fleet without the “damage sponge” role for fleet actions. Instead, it was decided to enhance the multi-mission need of the fleet with upgrades to the heavy frigates and allow the Sivas to continue in their traditional role.

Pompey Q-pod

The Pompey, Sargon, and Suleiman would continue to operate in the deep-space escort role for a minimum of fifteen years (thirty for the Suleiman). Another advantage that came with the double nacelle design was the ability to masquerade as just another under-defended Ptolemy transport at both long and medium sensor ranges. When outfitted with its own container, it maintained the façade even at visual ranges—until it dropped the pod, opened fire and took offensive maneuvers. Early in the design phase, it was realized that a customized tow module could be easily attached at the pylon box. The ship could carry an empty container with barely any drop in efficiency and a full container at speeds still in excess of the Ptolemies.

It was not long before missions to draw raiders out were proposed and Q-pods were provided to the Pompeys: powered by the mothership, a set number of the doors on the container’s 11 false hangers would open to reveal a full-powered Type VI phaser bank, manned by the ship’s own crew at local stations. These opening barrages were often enough to surprise and scare away some raiders, but it also gave the convoy the opportunity to draw in the mass of smaller vessels, disable a few, and allow the Pompey to release the pod and sweep up the retreating ships. Dedicated turbolift stations enabled the pod crew to quickly return to the Pompey before disengagement.

The primary downside to the Q-pods was that the Pompey could only charge two of the available banks at the same time while keeping the ship’s own phaser armament fully primed. However, a simple hierarchical algorithm allowed the ship’s helmsman to quickly assign routed power to another of the pod’s phaser stations between the raider passes, if necessary.

Pompey torpedo module

Additional attachment systems were also proposed for the Pompeys when the viability of a container tow module was first realized. Though neither would enter service—because of the decision to not continue the conversion of the Sivas—modules of each were manufactured.

The first was a torpedo pod of enormous relative size. The odd dimensions were a necessity; the pod had to be quickly attached with a station’s own work pods (no need for a drydock facility), but the Pompey’s underslung navigational dish was an obvious impediment to torpedo launch. The workaround was to have either a dedicated extension to the pylon box to place the torpedo module well under the dish—which would take longer to install and require additional support infrastructure to be stored in a near-ready status—or to widen the module itself to launch the torpedoes around the sides. The latter was the preferred option, as it allowed for the inclusion of the automated machinery necessary to support the heavy torpedo launchers. The width also allowed for a considerable number (55) of torpedoes in the embedded module armory.

The inclusion of rear-firing launchers was a literal afterthought in the planning process. The initial pod was smaller than the mounting plate for the container tow module, therefore it had to be extended by a fair bit; it already had enough heat radiators and adding in another 45 torpedoes seemed like an unnecessary expense and drain on the ship’s armory upkeep procedures. Rear-firing launchers required just a bit more of a pod hull than was necessary otherwise and were seen as providing an added and valued weapons arc.

Pompey scanning array

The subspace scanning array was another component meant to take advantage of the container tow module on the Pompey subclass destroyers. Like the torpedo pod, it would not enter service—because of the decision to discontinue the conversion of the Sivas. However, two were manufactured and tested by the Suleiman.

The pod had an advanced Mk IX (later designated Type I) subspace scanner array on every side except for the dorsal (as that would be covered by the module attachment point). The sensors themselves provided both active and passive detection capabilities out to 5 and 15 lightyears, for high and low resolutions respectively. The initial pod experienced considerable interference (and even disruptive electronic feedback in other ship’s systems, in one event) because the full forward sensor array reacted poorly with the ship’s navigational deflector. However, that was quickly resolved with an adaption that put two much smaller arrays that “peeked” around the dish and coordinated their emissions with the uprated sensor computers installed within the pod.

Einstein Flight II observation ship

Starships are designed with a specified lifespan; a starship that exceeds this target usually requires a tremendous investment in maintenance costs which is often a stated reason classes are retired en masse. However, if the class is valued enough, the ships may receive refits which extend the lifespans an equivalent period of time (i.e., generally matching the initially programmed operational period), significantly reducing those costs. A comprehensive review of equipment and structure—involving the planned replacement of any item lacking appropriate levels of technical capability expected of the present era—takes place, often with an accompanying and considerable change both internally and externally. A refit usually takes between 6 months and a year to complete and is often tied to a change of command.

In 2262, the Einstein, Gray, and Kelvin—each about 40 years old—entered the yards for long-scheduled refit periods. Chiokis had already performed superbly in updating the other members of the Syracuse class from the Geering saucer, so it was decided to give them a crack at updating the capabilities of the Einsteins with the introduction of the Flight II configuration. The ships were lengthened (by the swapping out of the PB-29 with the PB-32) to almost 245 meters and heightened to 66 meters. The new warp nacelle enabled the ships to cruise at warp 5 (a full factor increase) and achieve the maximum speed of warp 7.5 (from 5.1) with only an additional 28,000 tons added overall. The phase cannons and laser emitters were all replaced by the six under-powered Type V phasers (in three banks) with the weapons’ adaptability well appreciated for their defensive capacity. Lastly, the vastly improved deuteron wake detectors were increased in surface area and moved to the hull’s pylon (in order to keep shuttlebay activities from interfering).

The ships continued to operate in their observation role well into the 2280s.

Siva Flight III (testing model)

In the early 2270s, two members of the Siva Flight II configuration—USS Siva (NCC-520) and USS Jenghiz (NCC-501)— were re-assigned to separate propulsive research groups. The latter was provided in the study of furthering single-nacelle propulsion for future destroyers and scouts (as detailed in the Cygnus series), while the former was given up for the intent of once again modernizing the large numbers of Siva destroyers. Geering, the lead corporation on this task, started by removing the ship’s single PB-32 and replacing it with the ultra-modern LN-64.

While this would clearly enhance the ship’s cruise and warp speeds—even with the relatively antiquated warp core of the Siva— the full intent was to increase the maneuverability of destroyers in general, making them more effective in their anti-capital mission. So, following the successful integration and testing of the ventral LN-64 (placed in an inverted position for optimum multiple warp field integration), the ship returned to drydock for a radical change in its overall superstructure: the ventral pylon was replicated by a dorsal one to a high degree of similarity with a second nacelle installed atop it. Flight testing immediately followed.

Unfortunately the highly expensive modification was no more effective in either warp speed nor maneuverability than the horizontally-modified ships of the Pompey configuration. The physics of subspace displacement fields, as it was thought to be understood, could not account for this failure. Surely—it was reasoned—the problem lay in the technical engineering of the Siva class when married with linear warp technology. Thus the path to the development of the two-nacelle Akula was paved with good intentions.

Siva Flight III (operational upgrade)

Like with the Pompey modernization program of a decade earlier, the Siva herself was still seen as a viable platform. While she would not once again be the vanguard for her sisters, she was still seen as a ship fully capable of continuing fleet escort assignments as her warp performance envelope had increased. Star Fleet authorized the removal of the two (now) light torpedo tubes from her dorsal saucer and a single heavy torpedo launcher was added low on her ventral pylon. The ventrally-mounted dish had to be removed and some old, familiar equipment of the long-ago Syracuse / Saladin days was broken out of storage: the deflector emitters were installed at similar locations on the Siva. Though antiquated and prone to electronic failures, there were plenty of parts to draw upon from the caches and they worked well enough.

USS Siva remained operational in her solo Flight III configuration, including as a reserve and then training vessel, until 2301.

Note: USS Siva kept the Flight III moniker from her research period through the operational upgrade for two reasons: 1) she was not operational during the propulsion testing, therefore not yet recognized as a production version and 2) as she would never be visually mis-identified as a Siva Flight II (being the only one of the class with a dorsal nacelle).