Unless this ends up being a triple-engine beauty.Actually now that I think about it this post of mine is wrong, the Sagarmathas won't be the only ship class with the range to engage in raids in Klingon territory, SanFran is designing the Radiant-class Long Range Cruiser right now, presumably that will have the range to engage in raiding Klingon space given its entire purpose is to have long range.
Triple nacelles lend themselves towards endurance (even if not quite as much as quad designs, though they should be cheaper) and if we are going all 'explorer battlecruiser' that's something that'd be quite useful.I want a triple-engine Explorer to succeed the Sagarmatha! Even if it's 'supposed to be the Connie'. Then it'll look like more like the Federation-class...
Unless this ends up being a triple-engine beauty.
That's a good point, we made quite a good showing of reusing the Saga saucer towards the end of a technological/design era, imagine what we (and SanFran) could do if we hit it at the start of a new paradigm!Going Explorer will also give us a modern full saucer section to reuse.
Despite being outnumbered (Thunderchild + 8 Stingrays Vs 12 Warbirds + Outpost) and somewhat out-teched (no shields but Romulans only had nuclear torpedos) the Thunderchild really carried the engagement.The first was a squadron of the three NX starships led by Columbia and accompanied by a half-dozen Stingrays, while the other consisted of the Thunderchild and eight Stingrays.
Attacking two of the three Romulan outposts simultaneously, the defenders were unwilling to leave the unmolested outpost over the Denobulan homeworld completely undefended, leaving a flight of three warbirds to protect it against any surprise attacks or disengagements by the faster Earth starships. Of the remaining Romulan vessels, twelve engaged the Thunderchild and her escorts while five fought a delaying action to protect against Columbia's fleet element.
The Thunderchild immediately came under heavy fire in the initial exchange, appearing the preferential target for the Romulan force and the outpost itself. No less than nine disruptor beams impacted her forward hull in under three seconds, overwhelming the polarised hull plating and causing multiple hull breaches on C, D, and E deck. The dreadnought responded with her beam weapons, a rapid salvo from a dozen phase cannons over the span of five seconds burning through the shields of one of the lead warbirds and causing a catastrophic hull breach.
The fleet then cleared the first clash, passing through the Romulan formation. The Thunderchild's escorts broke apart and came about to re-engage the Romulan fleet in detail, while the dreadnought closed on the station and fired a full volley of photonic torpedoes. The four antimatter warheads and a barrage of phase cannon fire broke through the shield and inflicted serious damage on the station. The Thunderchild then banked to starboard while continuing fire from her cannons, turning back towards the fleet battle and firing a pair of photonic torpedoes into the outpost from her aft launchers. This caused massive secondary explosions as volatile storage and antimatter supplies were breached, resulting in the station's destruction.
The dreadnought then rejoined the battle proper, but her compromised forward plating meant the ship was unable to bring her forward torpedoes to bear on any of the warbirds. Instead the Thunderchild made a pass on the edge of the battle, using her starboard and aft cannons to concentrate fire on targets of opportunity. As a result two more warbirds were destroyed in cooperation with the Stingrays, although the Whiptail and Fanray were lost to Romulan atomic torpedoes.
The battle then turned against the Earth starships however, Romulan disruptor beams disabling the Butterfly and Softnose. The Thunderchild was again left as the main target of the Romulan force, with her remaining four escorts harried away from her by a squadron of warbirds. While her aft coverage and photonics allowed her to destroy another enemy ship, the concentrated fire quickly penetrated her aft plating and damaged her nacelles and main saucer section. Now beginning to lose her cannons, Thunderchild began a spiralling turn to port to bring her forward weapons to bear, but the more agile warbirds were able to evade this effort and continue to fire.
Now leaking drive plasma and with only one functional aft torpedo tube, the dreadnought managed to disable another attacker before the remaining five warbirds chasing her scored a hit on her starboard engine assembly and nearly brought the ship to a standstill. On the brink of losing power entirely, the Thunderchild returned fire with her few remaining operational cannons to no effect. However the arrival of the Columbia and Endeavour at high warp into the battlespace forced the attacking warbirds to disengage under the force of the NX's forward armament, saving the ship from certain destruction.
Approximately ten seconds later the surviving four Stingrays and the damaged Challenger from Columbia's attack group also dropped out of warp and joined the battle, prompting a Romulan withdrawal from the area and to the final station, which resulted in a consolidated defending force of a dozen warbirds. The battle would conclude a week later when a partially-repaired Thunderchild and a quartet of newly arrived Andorian Kumari-class battlecruisers spearheaded an attack by the fleet on the remaining outpost. Without the threat of Romulan ships in orbit, the Denobulans quickly overran the minor Romulan garrison in the capital and liberated the planet.
yeah, part of the reason why I want to do an Explorer first is to start in on the "recycle the saucer/other bits of the hull" thing as just a Thing That Starfleet Does™, because parts commonality good.That's a good point, we made quite a good showing of reusing the Saga saucer towards the end of a technological/design era, imagine what we (and SanFran) could do if we hit it at the start of a new paradigm!
Edit: that does remind me, though, the Saga saucer was the same diameter as a refit Connie's!
It should also be noted that what finally killed the Thunderchild was a lost nacelle and its inability to go to warp with only one nacelle forcing us to scuttle it. It was mission killed due to lack of mobility but during the battle it was still combat effective even after losing the nacelle, its just that once the battle was over it couldn't go anywhere. The Thunderchild was so tough the Romulans couldn't properly destroy it so we had to finish the job for them.After the latest discussion regarding the viability of battleships I decided to revisit the Thunderchild's first battle.
Despite being outnumbered (Thunderchild + 8 Stingrays Vs 12 Warbirds + Outpost) and somewhat out-teched (no shields but Romulans only had nuclear torpedos) the Thunderchild really carried the engagement.
In the opening engagement the Thunderchild tanks the entire Romulan fleet plus Outpost's alpha strike and doesn't lose any critical systems or weapons while killing a Warbird and the Outpost itself in exchange (this probably saved a Stingray or two from being killed at the very start).
It then kills a further 3 Warbirds, 2 in cooperation with the Stingrays and one on it's lonesome along with disabling another Warbird before it's incapacitated but retains enough functionality to be able to repair itself enough to take part in another fight a week later (Engineering 7 coming in clutch).
It's final kill tally is 4 Warbirds and an Outpost plus a disabled Warbird.
This was achieved despite lacking shields (polarized hull sucks for big ships since each section can be overwhelmed unlike shields), having outnumbered and lackluster support ships (the Stingray's an old policing vessel that was militarized rather than a purpose built warship), and being the main target of the Romulan fleet for much of the battle.
For reference the Skate which was it's contemporary but as a cheap combat frigate still costed roughly 1/3 of a Thunderchild (82 vs 28) and I highly doubt 3 Skates would have done anywhere near as well.
Even if more Skates could be fielded you'd still be looking at far more disabled/destroyed ships as casualties would have been inevitable with how many ships were involved and unlike the Thunderchild the disabled ones wouldn't have been able to repair themselves without support ships.
I also forgot how useful those Fabrication facilities turned out to be.
While I always remembered the Thunderchild being extremely tanky and hard hitting I forgot how there didn't seem to be any indication that any other ship or repair dock was involved with repairing it despite the downright brutal beating it took.
With the way things are looking with the Hailey and the fact that our next flagship explorer is likely to have Fabrication facilities we might be able to straight up perform enmass onsite resurrection of crippled ships just from feeding the Fabricators battlefield wreckage.
Honestly, I kinda want to do a sister-class for this ship, where we go Shuttles and Medical? Most of the design work for this is already done, and it's literally just filling in the bulk empty spaces of the hull.
TBF it wasn't just the Thunderchild. The three NXs that led the other force each had their own workshop too, though some of those were likely directed to fixing up that one NX that got damaged. Even assuming they got split half and half, two workshops to do an okay patch on one big ship is not that bad a ratio.I also forgot how useful those Fabrication facilities turned out to be.
While I always remembered the Thunderchild being extremely tanky and hard hitting I forgot how there didn't seem to be any indication that any other ship or repair dock was involved with repairing it despite the downright brutal beating it took.
With the way things are looking with the Hailey and the fact that our next flagship explorer is likely to have Fabrication facilities we might be able to straight up perform enmass onsite resurrection of crippled ships just from feeding the Fabricators battlefield wreckage.
And now we have the ability to affect the sort of repairs that would let her limp back to starbase, or potentially even tow her back (depending on what sort of auxiliary options we get) at warp.It should also be noted that what finally killed the Thunderchild was a lost nacelle and its inability to go to warp with only one nacelle forcing us to scuttle it. It was mission killed due to lack of mobility but during the battle it was still combat effective even after losing the nacelle, its just that once the battle was over it couldn't go anywhere.
There's a potential synergy between the cargo pod and the fabrication workshops, the cargo pod is just long enough to store a Type-3 nacelle and the fabrication workshops could manufacture the components needed to repair the pylon and attach the new nacelle and our shuttlecraft swarm can do the engineering work of actually connecting the nacelle. We won't have to lose a ship to a lost nacelle ever again as long as there's a Halley with a spare nacelle in its cargo pod nearby ready to help.And now we have the ability to affect the sort of repairs that would let her limp back to starbase, or potentially even tow her back (depending on what sort of auxiliary options we get) at warp.
Indeed, though I'm still keeping all my fingers crossed the rest of the sublight engine rolls are at least not bad.Funny thing is? ORB isn't even very expensive for what it's offering, we've managed to keep our costs shockingly low for this level of performance.
Considering it's been implied a war might be coming up with in as little as 14 years. This might mean we might only be able to get literally one design in before combat starts, as these designs seem like they can take 8 years or so?And considering our entire fleet is warp 7 right now, this basically means one needs to decide which role in the fleet need warp 8 capability first.So I'm curious, what ship should we be designing next for the 1st warp 8 ship? I'm thinking large generalist cruiser, real workhorse for the new generation.
Indeed, it's hard to predict exactly what the other yard will do before the next design round comes up to tell us. And you'd have to hope they optimize the design as one wants as well. And having two light/medium designs made in numbers would obviously have more impact then one light/medium and one big. Especially as the fleet compositions and the lacking weapon technology seem to indicate that next design round big craft may still be some what stifled in firepower increases and inability to make free use of their high warp factors in larger fleets.On the other hand, there's an argument for going to the larger vessel first because the smaller one could easily be rolled out in wartime if we needed to (we built basically all the old Skates in like the last six months of the Romulan War for example, though we probably aren't going to have that kind of surge capacity again until replicators are a thing given the creep upward in size), but we'll see what happens when we get done with the Hally.
There is also San Francisco to consider; simply because we elect to build a large vessel doesn't necessarily mean that a small one isn't going to be made.