General Notes

If you play SFB long enough, you will inevitably come up with ideas for new ships or improved versions of existing ships. Eventually, you will try to make SSDs out of those ideas and, if you are foolish and persistent enough, put them up on the web. Here are my offerings.

Included are two specialty ships that never made the transition from the Commander's rules to the Captain's rules. There are also two ships that were invented by others. Besides those, these are all my inventions. (Though some are so obvious - Fed TGA - others have also created their own, nearly identical, versions.) My primary focus is on the Federation, as they are my favorite empire, but I have tried to diversify my portfolio as inspiration has struck.
General Federation Klingon Romulan Kzinti Gorn Tholian
Orion Hydran Andromedan Lyran WYN ISC LDR
Seltorian Jindarian Vudar Paravian Carnivon

Master Ship Chart

Ship Studies

Occasionally a random idea with pop into my mind that will involve more than just one ship. In such cases (assuming I don't stop myself first), I will create a whole set of ships around the idea. Just to give them their own heading, I am collectively calling these "Ship Studies".

Barbarian Light Cruisers
When I first got Module C4, I was curious as to how all of the various war cruisers would compare with a fairly well define common denominator that the Barbarian Light Cruiser provided. While I first planned on doing this a long time ago, I never took the time to complete the whole thing.  For no apparent reason, the base project is now complete.

Escort Carriers
I created an entire class of ships called Escort Carriers.  They are carriers with the weapons of an escort of the same size.  Since they can protect themselves, they don't need dedicated escorts, allowing their escort requirements to be fulfilled by standard warships.  These were (correctly) rejected, as they would completely change carrier doctrine and use in SFB.  However, I think they are cool, and present them here.


Photon-Armed Freighter:  I have never fully understood why the Federation never made photon armed freighters.  No they aren't that scary, but with the larger engines the photons can be effectively used, particularly on the large freighter.  Plus the phaser armed version is completely ineffective and two drone racks just isn't going to do much.  If you are going to spend the money to arm a freighter, at least you can give it some teeth.  Used by the Federation and Orions operating in Federation territory.
(F-AS) (ssd)
(F-AL) (ssd)

Photon-Armed Auxiliary: Same rationale applies (in spades) to the various Auxiliary Cruisers introduced in R8. Everyone else gets the option to use some form of heavy weapons on their auxiliaries, but the Federation is left with drones or phasers. If you are going to spend that much money to create an auxiliary cruiser, the least you can do it give it some weapons to use. Used by the Federation. (Could have been used by Orions in Federation territory, but I don't think they used auxiliaries.)
The AWR refit on the Large and Huge auxiliaries only converts enough to reload the photons. (No, overloads were not considered "reloading".) It wasn't deemed cost efficient to convert all of the APR.
(S-AC) (ssd)
(L-AC) (ssd)
(H-AC) (ssd)
Actually, I walk back that comment on the Huge auxiliary. While two or three drones isn't impressive for the main armament, seven drone racks for the Huge auxiliary makes a lot of sense, particularly with its horrible turn mode. I leave the photon version above, however, as it completes the set.

General Master Ship Chart



Dreadnought Carrier (DNV): A DNG modified to carry a full compliment of F-14 fighters. It loses some weapons to make room for the widened shuttle bay. The shuttle bay has been completely redesigned so that there are opposing doors on either side of the secondary hull, rather than a single door at the front. There are two balcony positions at each door. It can operate with either two (like the CVS) or three (like the CVA) escorts. (ssd)
Improved New Jersey Battlecruiser (BCJ+):  I have always felt that the BCJ was pathetically under powered.  What is the point of giving a cruiser 6 photons if you can't use them?  The BCJ+ has the power to use those photons.  It is a very simple refit (conceptually), and just rearranges some of the labels on the saucer: the AWR becomes Battery, the Battery becomes Lab and the Lab becomes AWR.  The BCJ+ uses the same shock restrictions as the base BCJ.  (ssd)
Heavy Battlecruiser Carrier (BCV):  This version of the BC trades the "optional" weapons in to expand the shuttle bay. While this only carries a half-squadron of fighters, as opposed to the full squadron carried by the "real" BCV, this ship has the advantage of being a quick conversion of the existing ships. The "real" BCV uses what is, for all intents and purposes, a completely new secondary hull. This ship uses the same secondary hull as the standard BCs. (ssd)
Fleet Cruiser (NCB):  I did not make this ship, though I wish I did.  John Kim is the creator of this gem.  But it is such a good idea, I had to include it here.  (Especially since his site is now long gone.)  It is basically a DNG saucer that has been "NCA-ized" to give it the missing systems in a rear deck. Here is is original entry:

In Y173 of an alternate history, Star Fleet realized that the existing plans for a "battlecruiser" (the BCG and BCF designs) would soon be outstripped by more advanced designs. With the ceasefire, the Federation had time to develop a new design.
In design philosophy, this was a return to the original Constitution class cruiser. Rather than turning to drones or plasmas, it relies on heavy photon firepower. It is well-powered and extremely durable against damage.
The hull itself was based on the DNG dreadnaught saucer. It does not have a separate rear hull, but rather a small extension for the added shuttle bay (similar to the NCA of the primary SFB timeline). The four warp engine arrangement was made possible by a breakthrough in warp field physics, giving the ship a lot of stability.
Dubbed the Constellation class, this design proved an enduring one. Ship names include the Hathaway, and also the Stargazer which was eventually rebuilt using X-technology.
As one might guess, it an attempt to great a TNG Stargazer for SFB. (ssd)
Strike Cruiser (CS):  This is what I imagine the Federation would have created if they had felt compelled to make an equivalent of the Coalition's maulers.  This ship would be used under all of the restrictions of a mauler and, as a result, would never be encountered alone.  It suffers from shock like the BCJ.  (ssd)
Medium Carrier (CVM):  This is really a heavy carrier, but as that title is already taken, the more modest title of medium carrier was adopted.  This origins of this ship was as a competing design to the CVA.  The Federation decided then that a DN based CVA was a better choice.  However, as the CVAs began to be knocked out of service, the Federation decided to revive the old design.  The design was modified to be as similar to the CVS as possible, and the CVM is the result.  The two bays are completely separate; no transfers are allowed.  As the rear hull is identical to a CVS, not a CVB, it cannot carry F-15s.  (The CVA proponents wanted to make sure the CVM didn't supplant the CVA.)  It only ever carried two squadrons of F-18s, but one squadron could have eventually been replaced by F-101s.  The CVM can replace CVSs in the production schedule as desired.  (ssd)
Battle Tug Light (BTL):  This ship is an very interesting little package.  Take the light battle pod and put it on the standard fleet tug, instead of an LTT.  It becomes the fastest battle tug the Federation can field, if not the fastest ship.  It is incredibly overpowered, though it is a bit light on shields.  Please note that this is an official ship.  ADB probably never provided an SSD because they never wanted anyone to realize it exists (though it is in the MSC).  (ssd)
Armed Tug (TGA):  Here is what I think the tug would have looked like if it had been given an offensive capability.  I only gave it two photons, because they are there to make it painful to attack, not to make it a full warship in its own right.  Also increased the shields and phasers slightly.  This does make the BT a little nastier, but the BT is still no better than its Klingon counterpart.  (ssd).
Armed Battle Tug Light (BTL-A):  The Combat Tug with the Light Battle Pod.  Nasty little ship.  (ssd)
Drone Frigate (FDB):  This is a drone bombardment frigate.  I never really understood how the Klingons and Kzintis could manage to stick 6 drone racks on a frigate, but the Feds could only manage 3.  That's just dumb.  Here is a proper drone frigate.  It is designed to be used in a three ship squadron of two FDB and one FFS.  (ssd)

NCL and Variants

Though I have many ships I really like, probably my favorite ship across all of SFB is the NCL.  One of the most frustrating things about that ship though (besides the 4-6 breakdown), is that the first thing ADB did when designing variants was to strip off the photons.  And usually this was totally needless.  Fortunately, I was successful in getting the two most important variants changed to put some photons back in, the NVS and NAC, but failed with the LAT.  So here is the LAT and a few others.

And that 4-6 breakdown never made much sense either.  It is just a disk with close mounted engines.  It should be incredibly stable.  What would make more sense is to make the CA's breakdown 4-6 (what with the thin "neck" and long skinny engine pylons) and the NCL's breakdown 5-6.  That breakdown is just bizarre.

An interesting note:  If you look at the description of the AWR refit, the completely unrefitted NCL never existed, except for any pre-production prototypes.  All NCLs must either be an NCLa or NCLa+, as they are in service after the AWR refit date.  (This applies to all NCL variants as well.)  As a result, all of my NCL SSDs automatically include AWR, unless not equipped with photons.

New Strike Carrier (NVS):  This version of the NVS keeps the full weapons load of the NCL. (Yes, it only has a single drone, but then the D5V doesn't have any!) Every single other carrier variant always adds a few boxes to reflect the changes wrought by a massively increased shuttle bay. Why must the Federation NVS/NCL fail to do this? Using this extra space allows the NVS to retain the full photon armament of the NCL. This ship also has four balcony positions on its shuttle bay. (ssd)
Light Armed Transport (LAT):  This version of the LTT keeps half the photons and adds an extra drone while sacrificing no existing systems from the LTT, though I do replace the APR with lab.  I still have no idea why this was rejected.  (Although, I can guess:  ADB was probably needlessly terrified of the LAT + BP combo, with its 8 photons.  This is unnecessary as the Klingon BT already has 8 disruptors, and the LAT + BP can barely move!)  (ssd)
New Scout (NSC):  I always found it odd that while the SC has 8 (count 'em:  8!) scout channels, the NSC has only 4.  I think splitting the difference would be a little more effective;  it should have 6.  (ssd)
New Aegis Cruiser-R (NAR):  This what the NER would look like when based on the NAC instead of the NEC.  It chews up plasmas just like the NER, but now has some offensive punch with two photons and still has the rear drone rack.  (ssd)
New Drone Cruiser (NSD):  While the Federation has proved to be completely capable of making stupid decisions, this seems a bit egregious.  Having a drone cruiser that can also function as the fleet scout is a tremendous tactical advantage, plus it is now able to perform bombardment missions alone, instead of wasting valuable scout ships.  Also, most other drone ships can magically add extra drone racks (e.g. F5D), why can't the Federation? This is a much more useful version of the NCD.  (ssd)
New Mine Sweeper (NMS):  I have always felt the NMS was a crummy ship, especially when compared to the original MS.  This version of the NMS fixes those faults and makes some significant improvements.  Two of the drone racks are type E;  they are used to destroy multiple mines per turn.  The other two remained type G for drone defense.  A pair of Ph-Gs would have been nice (in the forward bank), but those are used exclusively on carrier escorts.  (ssd)
New Strike Cruiser (NCS):  This ship trades its two forward phasers for more photons.  It also gains the power to use its new photons.  The deployment philosophy was to add it singly to NCL fleets to counterbalance the presence of an NVS or NCD and keep the number of photons in the fleet to a reasonable level.  It was a limited deployment ship, as it did suffer from shock, and because it was to be deployed only in fleets.  (It actually is operationally used much like a mauler.)  Uses the same shock restrictions as the BCJ, but has a lower threshold (10).
Even so, it couldn't be published because, despite how it was intended to be used, it would be unbalancing because of how it would be used.  Plus every other empire would want their own CW with DN heavy weapons.  ADB decided it just didn't want to go there.  But it is fun to fly, so enjoy.
This ship was originally created by Thomas A.Clifton and designated a Torpedo Cruiser (NCT). (ssd)

If I could start again with the NCL, leaving it basically intact, but still allowed to make subtle changes, this is what I would end up with.  While the changes are not extensive, it significantly improves its performance.
Medium Cruiser (CM):  The NCL is my favorite ship, but I really wish it looked like this, and used this name.  This has a more appropriate breakdown rating, has a second drone rack so that a drone will likely survive the first set of internals and two extra hull.  The hull of the NCL is bigger than the DD, but its SSD only shows a gain of two shuttle boxes. I have added the hull to further reflect the slightly larger hull. (ssd)
Medium Carrier (CMV):  The carrier version of the CM. This is similar to the improved NVS above (and, indeed, caused me to make the NVS). By rearranging the tractors, enough space is freed up to keep the auxiliary control, two drones and the full photon suite of the CM. The shuttle bay has four balcony positions. (ssd)

Alternative Designs

The base Federation ships are the DN, CA, and DD, with the CL and FF thrown in. (I am ignoring the Tug, as I am focusing on the combat ships.) The CL and FF were added as the game developed, and the DN, CA, and DD were made before the game existed. As a result, all of these ships show the effects of when they were added to the game. As a thought exercise, I tried to "fix" each of the ships and make them more consistent with each other. Note that there is no alternative CA, as the CA is the basis for all of the alternative ships.

Alternative Dreadnought (DN-A): The weird DN is explained as being an early dreadnought that wasn't updated until the Federation was being swept up in the General War. This DN assumes a more reasonable progression. The existing DN would become known as the DNE and the existing DN+ ceases to exist. This DN becomes the DN, and its initial refit becomes the DN+. (All following DNs (e.g. DNG, DNH) are unchanged.) (ssd)
Alternative Light Cruiser (CL-A):  If the Federation had decided not to continuously update the venerable sublight cruiser, but instead replace it with a saucer equivalent, I imagine that it would look like this.  It is based on the NCL, but is "un-refitted" to fit back into the past.  It has no drone rack, no APR, "normal" engines, and has unequal shields.
The plus refit is a combination of the refits for the DD and CA:  it gets the side Ph-3s and Lab/AWR conversion of the DD refit and the drone and upgraded rear shields of CA refit.  (ssd)
War Cruiser (CW-A):  As the CL+ is not the equal of the other empires' war cruisers, the Federation would have been forced to introduce their own war cruiser. They would have taken the CL+, given it "hot warp" engines and beefed up the shields.  The result is a ship which is identical to the NCLa+, but with a different name.
Alternative Destroyer (DD-A):  This is an attempt to make a destroyer more in line with those of the other empires. It has only two photons, and its refit includes a drone rack.  (ssd)
Alternative Frigate (FF-A):  The Federation Frigate has always felt wrong.  To me, it has always been a "modern" General War frigate that was "back-dated" to the Middle Years days.  If it had been introduced into the game at the same time as the CA and DD, it most likely would have looked different.  It only takes two minor changes to fix the problem:  removed the Ph-3s and reduce the #2-#6 shields.  No line ship in the Federation fleet ever had Ph-3s until fighters and relevant drones forced the issue.  They should be part of the refit, not the base ship.  Also, no early Federation ship has equal shields; the shields should gradually reduce toward the rear. (Note that the refit, while increasing the shields, does not increase the shields to the level of the FFG.) The FFG would still likely have been made as a further refit beyond the FF+. (ssd)

Captured Ships

Captured Klingon D6 Destruction (CD6):  Since the "real" CD7 (what I called the D7F) was published in CL23, I have decided to instead show what Kumerian's Destruction would have looked like had it been converted instead of returned.  Note that at the time of the conversion, it would have had the plus refit, but not the AWR refit. (ssd)
Captured Klingon D5 (CD5):  Since I have a big thing for war cruisers, here is the D5 converted to Federation technology.  Unlike the CD7, this ship is not markedly superior to the Federation's war cruiser, but is roughly comparable.  (ssd)
Captured Klingon F5 (CF5):  Probably the most likely ship to be captured by the Federation, so I include it here.  (ssd)
Captured Romulan War Eagle (WE):  Any "Eagle" ship that Star Fleet captures and decides to convert is pretty much guaranteed to be done as a King Eagle, as shown in CL27.  However, prior to the introduction of the King Eagle, or in the cases were someone besides Star Fleet captures an "Eagle", they may not be willing to fully convert the captured ship.  In such cases, any conversion will be done as cheaply as possible, resulting in this ship.  Sometimes photons may not be available for the conversion, so, in such a case, two drone racks would be used.  This SSDs allows either configuration to be used.  (The ship must use either two photons or two drone racks; it would not be configured with one of each system.)  This ship does not use a cloaking device.  (ssd)
Captured Romulan Sparrowhawk (SPA): While the Firehawk makes a very, very nice Federation ship, the Sparrowhawk doesn't. Using the base conversion rules, it is left with two photons and two drone racks. Not a very exciting weapons array for a cruiser. A much better conversion converts all of the plasma to photons. While I could try to convert two Ph-3 into drones (a la the RKL), I chose not to. The ship is most likely to work on the Romulan border, so the absence of drone racks shouldn't be a big deal. This ship does not use a cloaking device. (base ssd) (photon ssd)
Captured Romulan Sparrowhawk Carrier (SPB): On the other hand, having a split photon and drone armament works very well for a carrier. This particular carrier has an added benefit in that it carries 16 fighters to the battle, instead of just a normal 12. This ship does not use a cloaking device. (ssd)
Purchased Hydran Knight (KN):  The only known surviving ship of the Hydrans' "Operation Federation" was a Knight destroyer.  It was too badly damaged to bother with, this supposes it was converted for use by the Federation.  Presumably, the Federation would have paid for the hull somehow, so as to make it a "purchased" ship, rather than a "captured" ship.  Note that it has three photons, rather than two, as the Lancer's three fusion beams imply it has the room.  Any Federation conversion of a Lancer would likely end up looking like this, too.  (ssd)


A-18 "Wasp" Fighter:  With the advent of Interceptors, the Federation had no adequate response.  Philosophically unwilling to commit to the use of similar ships, the Federation had to come up with an alternative.  While the A-20 was initially thought to be adequate in that role, it was determined to be too slow and too difficult to field.  (After all,  there ended up being only two ships in the entire fleet that carried them:  a single NVH and a single SCS.)  What was really needed was a mass produced fighter that could move fast and still deliver a photon hit.  The result is the A-18.A-18 Fighter
It is based on the design of the F-18, but replaces the two type I drone rails with a single photon.  While it is effectively a variant of the F-18, it is not possible for one to be converted to the other.  Since it was not developed until Y179 and did not enter mass production until Y181, it functionally includes the "B" refit of the F-18, but was never called the A-18B.  It has 10 damage points, 2 type VI drones, one chaff pack (it was not intended to dogfight), a Ph-3 and a single photon.  The photon is, of course, limited to a range of 12 hexes.  Special rails where never added.  Speed is 15.  DFR is 1.  BPV is 11.
It could be deployed anywhere an F-18 could, but was primarily used on NVSs.  It replaces half of the original number of F-18s on the carrier.  In addition, the CVA could replace its A-10s with A-18s.  Other exceptions were typically the SCS which never carried them as it already had A-20s and the AuxCVA and CVA pod which typically only carried six A-18s instead of the allowable twelve. Obviously, the fighter box for an A-18 would have photon reloading capabilities.
    A-18C:  Replace the two light rails with two standard rails in Y183.  The A-18C was fairly rare for several years as F-14s, F-15s and F-18s were all refitted before A-18s.


The Federation never fielded gunboats. Multiple reasons were put forward to explain this, but none of them made a huge amount of sense. The most commonly quoted reason is because the Federation believed that gunboats were "deathtraps", and assigning crews to them was tantamount to a death sentence. But, that makes little sense, as the same could be said for any frigate, escort, auxiliary, fighter, or bomber that saw combat. Even destroyers and war cruisers could explode from a single strike in a fleet battle. So, it is likely there were other reasons, probably economic, that made the use of gunboats unpalatable to Star Fleet.

However, this hurt police and security forces. Gunboats were so superior to skiffs and heavy shuttles, that civilian, police, and security forces faced an economic disadvantage by not employing them. Historically, they just sucked it up and dealt with it. Below provides two different ways that they could have worked around the limitation and prohibition of Star Fleet to get gunboats.

Cowboy Gunboat

While the Federation Star Fleet refused to make use of gunboats, there was an entity within the Federation that *did* make use of gunboats. While the Buccaneer gunboat was employed by the Orion Pirates, whom, of course, the official civilian government of Orion completely disavowed, the Orion police forces could have fielded "civilian" versions of the Buccaneer had they wanted to push the issue with the Federation. (In they end, they did do this with the introduction of the Orion workboat.) Had the Orion government decided to do so earlier, they would have called it the Cowboy (as opposed to the Buccaneer) gunboat. There is no interceptor predecessor, as the political maneuvers necessary to allow for the sale of the Cowboy gunboat took enough time that the gunboat technology was already figured out. For all intents the standard Orion Pirate interceptor functions as the interceptor for the Cowboy.
It has no stealth bonus and cannot double its engines. In addition, its systems follow a standard gunboat arrangement, without the changes used by Orion Pirates. (To stress that the design has nothing to do with those illegal Pirates.) It also does not have any option mounts, but instead has standard fixed weapons. The configuration shown is the standard armament, but two very common variants replaced the photon with a Ph-1 FX or a drone rack. The standard variants (cargo, troop, etc.) are also available. The first link shows a standard flotilla. The second link shows the phaser, drone, patrol, survey, cargo, and troop variants. The workboat is the published Orion workboat. (base ssd) (variant ssd)

Police Gunboat

The Federation police forces were extremely frustrated that Star Fleet refused to allow the use of gunboats, which would significantly improve their resources could they use them. The fact that Star Fleet refused to use gunboats was actually seen as a bonus, as it means that Star Fleet would not "steal" these forces, like they tended to do with so many other police assets. Despite the resistance of Star Fleet to the production of gunboats, the various police forces were able to push this through.
There was no interceptor predecessor to this gunboat, as it took so long to get the approvals to create the police gunboat that the parameters of how gunboats were already well understood, and the Federation could just leverage the experiences of the Kzinti (and Orions).
This gunboat is designed on the outline of the ubiquitous police cutter. It has a very standard design, but it sacrificed a weapon mount to include a transporter on the standard design. The configuration shown is the standard armament, but two very common variants replaced the photon with a Ph-1 FH or a drone rack. The standard variants (cargo, troop, etc.) are also available The first link shows a standard flotilla. The second link shows the phaser, drone, cargo, survey, troop, and workboat variants. (base ssd) (variant ssd)


I am not a big fan of X-ships and probably won't put too many up on this website.  However, these two variants were too obvious and tempting to pass up on.
Advanced Light Cruiser (NLX):  This is an X-version of the NCL.  Since, like all other light cruisers, is based on the NCL, but is not a conversion.  As such, the Federation designers took the opportunity to add a few little details to make it more general purpose.  The primary addition was to add a little more living space (hull) and to add lab capabilities at the expense of some auxiliary power.  (ssd)
Advanced New Cruiser (NCX): This basically takes the DDX and adds an updated NCA rear hull. The number of boxes in the rear hull is unchanged, but they are all X-systems. It uses a uniform arrangement of three matching engines. Since the rear hull systems appear to have a movement cost of 1/3, and the base hull has a movement cost of 1/2, the whole ship has the unusual movement rate of 5/6. It has fewer phasers than the CX, it has twice the drone racks. It uses the shields and electronics of the CX. (ssd)
Advanced Destroyer (DDX):  This is just a single-engine variant of the DDX.  It was never developed as the two engine version had more power, but this version just seems to be more aesthetically pleasing. (ssd)

Federation Master Ship Chart



Doomslayer (D7C):  The Hammerfield and Doomslayer were introduced in the story that first introduced the Masters.  (I believe this was in Captain's Log 3.)  This ship has some factory unauthorized modifications.  This ship would never have appeared in the "real world" as these modifications were made by the Masters.  I have updated this from the original to reflect the changes that have taken place to the base D7C.  Also, instead of adding two APR, I have given it a emergency warp engine on the boom (like on the D6J and C7).  (There are no ADDs, as these were deleted to make room for the photons.  Looks like a good trade to me.  :-) )  It packs quite a punch.  Presumably, the Masters would have eventually given it the K refit and made it a D7L.  (ssd)
Hood (FCA): Assume that the Klingons managed to capture the Hood, instead of just blowing it up.  (SH19.0)  (As an aside, how was it not captured?  With 15 transporters between the three Klingon ships, they should have captured the Hood!)  ADB published an SSD for a Fed CA captured and converted by the Klingons in CL23.  As a result, I have taken my Hood SSD down.

Alternative Designs

It always seemed so odd that the smaller ships didn't mount their disruptors on their engines, but instead mounted them in the hull.
Alternative F5 (F5-A): When the disruptors are moved to the engines, a little more space was opened up, allowing for a redundant tractor. (ssd)
Alternative E4 (E4-A): When the disruptors are moved to the engines, a little more space was opened up, allowing for a redundant tractor. (ssd)

Captured Ships

Captured Federation Light Cruiser (FCL):  As a counterpart to the CD6 above, here is the Klingon conversion of a CL.  This results in a pretty interesting ship.  (ssd)
Captured Federation New Light Cruiser (FNL):  As a counterpart to the CD5 above, here is the Klingon conversion of an NCL.  While weaker than the D5, it would still do an acceptable job.  (ssd)
Captured Federation Frigate (FFF):  The most likely ship to be captured by the Klingons, so I include it here.  (ssd)

Klingon Master Ship Chart



K9S Space Control Ship (K9S):  At some point the Romulans probably considered converting the Behemoth into a Space Control Ship.  They would not have bothered with the conversion into a CVA as they had plenty of other carriers they could use, and the addition of just fighters would not justify the cost of converting the K9R.  However, once PFs were introduced, the Romulans probably did seriously consider converting the K9R into a K9S, but would only have done it if it needed serious repairs.  (It probably still was not worth pulling an undamaged dreadnought in for a conversion.)
This ship basically just uses the rear deck house identical to that of a C8S.  Note, however, that it still only has a single wing phaser as it is still based on the K9R, not the C8.  Ideally it would be escorted by a KDE and two K5Es, but if they are not available, various other combinations would be acceptable.  (ssd)
K9P Dreadnought (K9P)
: Going back to the idea that Romulan fighters are somewhat pointless, but their PFs are very powerful, here is a PF only version of the K9R. Rather than using the C8S/K9S as a basis, this is a direct modification of the K9R using the ROC as a model. This includes a pair mech links on the boom, and uses half of the copious shuttle bay to get room for the repair facilities. This conversion is a dramatically simpler conversion than the K9S.  (ssd)
K5R-C Frigate (K5R-C)
:  This is the KF5R from the old Commander's edition. The original KF5R had a single plasma G that was then upgraded to a plasma S with the B-refit. In Captain's edition, the plasma was reduced to a pair of Pl-Fs (which fit the SSD better). Also, the Captain's edition rules were changed to prevent a Pl-S from being mounted on a class 4 ship. I, however, always liked the old KF5R better than the new K5R, so here it is (including its Pl-S). (ssd)
K1 Gunboat (K1)
:  The Romulans have a "KR" version of just about every other class of Klingon ship, but one was never done for the G1 gunboat. After making the conversion, I was quite impressed with how effective a PF it is. It has two Ph-1, a rear Ph-3, and three Pl-Fs with very wide arcs. These are very nice little ships.  (ssd)

Captured Ships

Captured Federation New Light Cruiser (NCL):  This is a straight conversion of the NCL.  Oddly enough, as weak of a conversion as the CA is, this ship is quite strong.  It has a stronger weapons suite than the SPA, and would be able to operate with them.  Its only real weak points are its limited reserve power and low breakdown rating. (ssd)

Movie-style KR Ships

I always thought it was cool in the movies how the weapons were fired from the front of the boom.  So here are versions of the KR ships with the plasmas in the nose.  These are functionally equivalent to the real versions, but do add some minor variations because of arcs and weapons locations.  I have only done the base classes;  it does not take much to then extend the idea out to all of the various variants.

As a general rule, place the heaviest plasmas farthest forward.  If there are secondary plasma, put it in the wing positions.  Then move the displaced phasers to the engine mounts.

Alternative K9R (K9R-A):  This places the Pl-R and Pl-Ss up front; the Pl-Fs are in the wings.  The phasers are moved to the engines.  Unlike the cruisers, the number of phasers on the K9R-A and K9R are the same, but I had to keep the wing phasers, in addition to adding the Pl-Fs, to do this.  Without the B refit, delete the shaded shield boxes and reduce the Pl-Ss to Pl-Gs with LF-L and RF-R arcs.  (ssd)
Alternative K7R (K7R-A):  This places the two Pl-Ss up front and the Pl-Fs in the wings.  The phasers are put on the engines.  The K7R-A loses a phaser over the standard version.  This is because the K7R gains a "box" on each engine (for the plasma F), but the K7R-A only gains a single "box" (in the boom).  Without the B refit, deleted the shaded shield boxes and reduce the Pl-Ss to Pl-Gs with the FA arc.  (ssd)
Alternative KR (KR-A):  This places the two Pl-Gs up front.  The phasers are put on the engines.  The KR-A gains a phaser because of this, but the forward phasers end up with slightly worse arcs.  This is because the KR-A gains a "box" in the boom (the two Pl-Ss take up four "boxes", but the phasers only take up three "boxes").  The B refit (not shown) increases the 3-4-5 shields to 22 boxes and change the plasmas to Pl-S with FP arcs.  (ssd)
Alternative KDR (KDR-A):  This, ironically, gives the ship a more conventional plasma arrangement of 1x Pl-S and 2x Pl-F instead of the standard KDR's 2x Pl-S.  The Pl-S replaces the forward phasers, and each Pl-F replaces a wing phaser.  All displaced phasers are put on the engines.  I gave the phasers the same arcs the disruptors have on the D5.  This ship effectively includes the B refit.  (ssd)
Alternative K5R (K5R-A):  This results in a purely cosmetic change.  The Pl-Fs are moved to the nose and the forward phasers are moved to the wings.  Without the B refit, deleted the shaded shield boxes.  (ssd)

Heavy Plasma KR Ships

Going a step further, you can end up with a true revamping of the Kestrel fleet.  Figure that the Romulans would tend toward what they currently know (heavy plasma) and only made the full transition to "standard plasma" with the Third Generation.  Doing so, you end up with the following ships.  (The KDR would not change.)

Alternative K9R (K9R-B):  Make the same changes as in the K9R-A, but replace the two Pl-Ss with another Pl-R.  Then put the Pl-Rs in the positions of the Pl-Ss on the K9R-A, giving them split arcs.  This also leaves the two nose Ph-1s in place, and so does not have any phasers in the wings.  The other phasers are moved to the engines.  Again, the number of phasers on the K9R-B and K9R are the same.  Without the B refit, delete the shaded shield boxes. (ssd)
Alternative KRC (KRC-B):  Move the Pl-Ss to the nose of the boom and combine them into a single Pl- R.  The Pl-Fs are moved to the wing positions and two Ph-1s are positioned on each engine mounts.  The Pl-D racks and waist phasers are unchanged.  There is no B/L refit.  (ssd)
Alternative K7R (K7R-B):  This has the same plasma arrangement as the KRC-B.  Without the B refit, deleted the shaded shield boxes. (ssd)
Alternative KR (KR-B):  Replace the two Pl-Gs with a single Pl-R.  Without the B refit, delete the shaded shield boxes.  (ssd)
Alternative KDR (KDR-B):  The alternative KDRs are the same.  By using the Pl-S and the two Pl-Fs, it has already been built around the biggest plasma torpedo the ship can carry.  See the KDR-A.
Alternative K5R (K5R-B):  This gets a heavy plasma up front and moves the phasers to the wings. The overall power is pretty equivalent because I have violated the rules by making the heavy plasma a Pl-S. While this against the rules, this is a truly imaginary ship, and the Pl-S just works better. If necessary, just downgrade the Pl-S to a Pl-G. Without the B refit, change the plasma to a fixed Pl-G with an FA arc, and remove the shaded shield boxes. (ssd)

Romulan Master Ship Chart



Heavy Cruiser Carrier (CVB): The more I look at the CVL, the more I realize how the Kzinti got completely screwed on their CA carrier.  While it was a reasonable counterpart to the D6V and CVT, by the time of the D7V, Lyran carriers, and Fed CVS/NVS, it is completely outclassed. While it is probably too "cookie-cutter", the Kzintis probably aught to have a wartime 12 fighter carrier on the CA hull.
The fighter bay is expanded on this ship and the rear pylons that were mysteriously removed on the CVL were put back.  (Why were they removed!?)  (ssd)

Purchased Federation Ships

At the beginning of the General War, the Kzintis were dramatically running out of ships.  While it didn't happen, it was quite possible the Federation would have just outright sold the Kzintis some of their own hulls so the Kzintis could field more warships.  (In the end, the Federation ended up just funnelling them funds which the Kzintis used to make their own ships.)  Had ships been sold to the Kzinti, they would have simply been the NCL and FF (the two ships that were mass-produced by the Federation).
Purchased NCL (FNL):  This is a Federation NCL converted to use by the Kzintis.  The phaser suite was reduced, but disruptors and drones were added.  It is roughly comparable to the Kzinti CM, but the CM has more firepower.  They didn't number the refit, and just called it a "plus" refit.  (ssd)
Purchased FF (FFF):  This is a Federation FF converted to use by the Kzintis.  Again, the phaser suite was reduced.  Also the APR in the refit was changed to another drone.  (ssd)

Kzinti Master Ship Chart



PF Dreadnought (DNP):  The Gorns never really subscribed to the use of fighters.  So I would have expected to see this type of dreadnought instead of an SCS.  There are several advantages of a PF-only dreadnought.  First, it is cheaper to make.  Unlike the SCS or CVA, this is made within an unaltered DN hull;  the other two require extensive modifications to the DN hull to fit in the carrier bays.  Second, it doesn't have to carry around marginally effective fighters.  Finally, it is no longer required to be escorted by two or three toothless vessels;  the carrier escorts that would otherwise be required can now be replaced with actual warships.  This is a true PFT.  (ssd)
Dreadnought Carrier (DNV):  The Gorns never made a CVA, but could have easily deployed a "dreadnought carrier", which carries a single squadron of fighters.  The advantage of this is that with the sacrifice of a single transporter, the dreadnought gets the extra firepower of a squadron of fighters.  However, as the hull is not "stretched" or "widened" or massively altered in some other way, it is easily constructed for little additional cost over a standard DN.  (Or is easily and quickly converted from a DN.)  While it is not required, it would have the same escorts as the CVA.
It has a single, tunnel bay (J1.59) with three balcony positions on each side.  (ssd)
PF Heavy Battlecruiser (BCP):  Using the above rationale, the Gorns could also make a PF-only BCH instead of a BCS.  The first benefit above really comes into play because the hull of the BCS is massively altered.  This just uses a standard BCH hull, but with new wings.  This is a true PFT.  (ssd)
Armed Tug (TGA):  I have never understood why anyone would be so blindly stupid as to not only replace a Pl-G or Pl-S with a single tractor beam, but to do it twice.  How many tractors does a tug need?  Five seems a bit much.  This puts the normal CL wings back onto the tug.  (ssd)
Gunfighter Battle Destroyer (GBD):  With the introduction of the gunfighter frigates in CL28, I started to wonder what a gunfighter battle destroyer would look like. Seeing as the Gorns are willing to slap a rear disk on just about any other DD variant to make a BDD variant, why not this one? Interestingly, the BDD design already has so much APR crammed into it, this design only gains a single APR. It does, however, gain several weapons. (ssd)

Heavy Fighter Gorns

I have always thought it odd that the Gorns would depend so totally on a foreign empire to pilot all of their fighter craft. It would seem that they would attempt to minimize that as much as possible. As long as they have to field single-space fighters, they don't have a choice, however. And, throughout their history, that would be the case. However, with the introduction of heavy fighters, they would be able to signficantly change the equation. This would make the Gorns into the "heavy fighter" empire.

Ideally, the Gorns would be a PF-heavy empire, as they hate fighters and need attrition units.  Unfortunately, they get PFs behind everyone else.  However, this feeds into the idea above, as it forces them to make much heavier use of heavy fighters during the half-decade gap between the introduction of heavy fighters and PFs. And, even after the introduction of PFs, they would continue to be the one empire that makes significant use of heavy fighters.

When the Federation introduced the Gorns to fighters, the Gorns understood the need, but didn't like them because they couldn't fly them.  They had to hire Federation mercenaries to fly for them.  Plus, the Federation only sold them fighters after having fulfilled their own needs first.  So, when they were introduced to the idea of heavy fighters, they quickly took to it.  After designing the G-30 and G-40, and realizing they could easily be configured to accept a Gorn pilot, the Gorns quickly retrofitted their fleet to make use of the heavy fighters.

All carriers are converted to carry 6 heavy fighters instead of 12 single-space fighters.  (The CVA would carry 12 heavy fighters in violation of normal rules. The SCS would carry 6 heavy fighters and 6 PFs in violation of the normal rules.)  The BDV and HDW also carry heavy fighters, but only have partial squadrons because of their smaller size.  Most carriers made use of the G-30, however the supply of G-30s was sometimes insufficient, and they would have to make due with G-40s. Also, carriers that only carried superiority fighters (e.g. HDV or auxiliary carriers) always carried G-40s, not G-30s. As quickly as the supplies would allow, bases were also converted over to the G-30s, with each hanger module being configured to hold 3 G-30s.  (Hanger modules so configured would only be deployed in pairs.) Again, however, supplies of G-30s were not as much as desired, and many bases had to operate with G-40s for the entire war.

Purchased Federation Ships

The Gorns don't have much of a production schedule, and the HDD is a pretty light war cruiser. If the Federation had wanted to, they probably could have supplied some NCL hulls to the Gorns to be converted to their use. They wouldn't have bothered with the FF, as the BDD (and even the DD) is better than anything they could convert from a Federation FF. That is definitely not the case for the NCL.
Purchased NCL (FNL):  This is a Federation NCL converted to use by the Gorns. The weapons were converted as described in the Fed/Romulan Anarchist article, but with one exception. The rear drone rack, instead of being converted to hull, is instead converted to a rear firing plasma torpedo. Also, the marine contingent and shuttle arrangement reflects the Gorn preferences. (ssd)

Gorn Master Ship Chart



Disruptor Dreadnought (DN): I never fully understood why the Tholians could replace a pair of Ph-3s with a pair of photons, but couldn't do it with disruptors. This ship assumes that the lessons with the photons allow them to use disruptors, too. The DN is just a DP with disruptors in place of the photons, giving a total of six disruptors. (I used the "corrected" hull form from CL29.) (ssd)
Space Control Ship (SCS):  This takes the CVA to its full extreme to be a Space Control Ship.  The wonderful thing about the CVA is that it already has the 6 tractor beams.  One option was to just put mech links on the tractors and have an SCS with no repair.  Instead I deleted some systems to make room for a minimal repair suite.  And since the fighter bays are all external, I just left them, so it retains the full 24 fighters.  (The fighters are mounted forward in the center, and on the sides.  The PFs are mounted on the bottom and the top rear.) (ssd)

Tholian Master Ship Chart



Hammerfield (CA):  (See the Doomslayer for origin.)  This was Deth O'Kay's personal ship, which had been extensively modified.  (Unlike the Doomslayer, these changes were made before being captured by the Masters.)  The only change I have made to the original was to increase the shields to the CA+ levels (the original had 30-28-22-20; it now has 30-30-24-24).  The Ph-G's are fairly irrelevant because of their arcs, but that big center warp engine sure is impressive!  This ship has a cloak.  I have not bothered with the BPV.  (ssd)
Strike Cruiser (CS):  This is a slightly modified CR.  Two of the forward phasers are swapped with the wing options.  This fans the phaser arcs out some, but the compensation is a better option mount arrangement.  The option mounts are all considered adjacent center-line mounts.  Designed by Rodger Burns and Mike Raper. (ssd)
Heavy PF Tender (CPF):  Instead of wasting time converting obsolete CAs into carriers, they should have made them into PF Tenders instead.  First, it is cheaper and easier to produce (just add mech links and stuff the cargo with repair equipment).  Second, it is far more effective.  The CPF can be used either offensively with a full weapons load in addition to the PFs, or in a support role.  In the support role it would usually carry two special sensors, a drone rack and an ADD rack.  (Two drones racks would be used if the ship also had OAKDISC.)  Only PFs in the last two positions can be repaired.  This is a true PFT.  (ssd)
Super Salvage Cruiser (SSL):  This takes the improvements of the SGS, but doesn't use the fighters or PFs.  It simply performs the role of a Salvage Cruiser, but with the bigger hull and engines. (ssd)
Super PF Tender (SPT):  This takes the improvements of the SGS, but it only carries PFs.  There are no fighters.  The beauty of this ship is that it can now do what a real Orion is supposed to do: capture cargo.  It is a full PFT, with repair, but also has a very (for an Orion) spacious cargo hold where lots of loot can be kept.  This can be considered the perfection of Orion design in their original role.  Because of its utility, it would rarely used in the mercenary role.  (Unlike the SGS, which is used almost exclusively in the mercenary role.)  (ssd)
Super Salvage Carrier (SSV): This takes the improvements of the SGS, but it only carries fighters.  It is a true carrier, with a full squadron of 12 fighters, but still has as much cargo space as the original Salvage Cruiser.  (While nice, the SPT is a much better use of the hull.)  (ssd)

Orion Master Ship Chart



All new Hydran ships presented here have no "class names".  There are so many, I don't know them all, and, if I do pick an unused one, it will probably be used for something else.  Consequently, I will just go with a more standard class description for my Hydran ships.

Armed Tug (TGA):  This is a Caravan with some weapons.  It sacrifices a little internal cargo space to put the weapons back in.  It has the same weaponry and power as a Ranger, but only has a third of the fighters.  It only has fusions, as I figure the Hydrans wouldn't put any of their fairly scarce hellbores on a support ship. Plus, the fusions would scare just about anything short of a full warship.  (ssd)

Hellbore Fleet

With the official Hydrans, the hellbore weapon is used sparingly and rarely. Their primary focus is always on the fusion beam; both on ships and on their innumerable fighters. However, what if the Hydrans focused on the hellbore to the exclusion of fusions and fighters? What if they made a much more conventional fleet? As a thought exercise, I decided to try and find out.

I mainly focus on the leaders, as they are the only ships with mixed weaponry. All of the non-leader ships are hellbore only and, with the exception of the new and old heavy cruisers, carry no fighters. In this conversion, the general rule is that fusions are turned into phasers and fighter boxes are deleted. Fighters are occasionally turned to power, but only when noted below. While it is tempting to change at least some of the fighters into power, I felt that was "dishonest". The power curve of the ships remains the same; the weapons just become much more effective.

I didn't make class names for any of the ships. Instead I just refer to them as the standard classes they are, but with an "H" in front to designate that they are part of the hellbore fleet.

Heavy Cruiser (HCA): The Dragoon is almost the perfect model for what I am trying for, except that it has three fighters. This variation simply removes the fighters (and their boxes) from the ship (which is how it is almost always used, anyway). (ssd)
Dreadnought (HDN): Based on the standard Paladin, it gets the six hellbores it should have always had. The other two fusions are turned into phasers. Some of the fighters are exchanged for extra power and some for shuttles, and the rest are deleted. (ssd)
Heavy Battlecruiser (HBC): Based on the Overlord, it exchanges its fusions for phasers, changes half the fighters to shuttles, and deletes the other half. This ship is now the ship it was always born to be. It is absolutely devastating. (ssd)
Command Cruiser (HCC): Based on the Lord Bishop, it exchanges its fusions for phasers and deletes the fighters. (ssd)
New Heavy Cruiser (HNCA): Based on the Iroquois, it simply deletes the fighters (just like the Dragoon). (ssd)
Medium Command Cruiser (HMCC): Based on the Apache, it exchanges its fusions for phasers. It already doesn't have any fighters. (ssd)
Medium Cruiser (HCM): A standard Tartar.
Light Command Cruiser (HLCC): Based on the Baron, it exchanges fusions for phasers, and deletes the fighters. (ssd)
Light Cruiser (HCL): A standard Traveler.
War Destroyer Leader (HDWL): Based on the Lion Hunter. It exchanges its fusions for phasers, and deletes its fighters. A wonderful little ship that you wish could have a third hellbore. (ssd)
War Destroyer (HDW): A standard Rhino Hunter.
Destroyer Leader (HDL): Based on the Warrior. It exchanges its fusions for phasers, and deletes its fighters. (The SSD may not look like that, as some extra rearranging of the boxes was done.) This makes an amazing Hydran destroyer with six Ph-1s and the power to use its hellbores. (ssd)
Destroyer (HDD): A standard Knight.
Frigate Leader (HFL): Based on the Crusader. It swaps it fusions for phasers. It only has Ph-2s, but with six and a hellbore, it packs a pretty good punch none the less. (ssd)
Frigate (HFF): A standard Cuirassier.
Captured Klingon D7 (HD7): This is an optimized D7H. It removes the fighters and fusions, and changes the rear security into a much needed APR. It also gets the full shield refit. (ssd)

Hydran Master Ship Chart



Gunfighter War Destroyer (GDW):  The Lyrans really love to make trimarans out of catamarans, whether they are needed or not. (Even more than Gorns love to add rear disks.) So, if they ever really did make any gunfighter frigates, it is almost guaranteed they would at least try to make a gunfighter war destroyer.  Interestingly, this ship does not gain any more disruptors than the GFF, but it does get more Ph-1s and  lots more power. (ssd)

Lyran Master Ship Chart



PF Tender (PFT): The Flivver PFT is based on the CW hull. While it loses its hyperdrone racks, it gains special sensors and a full PF flotilla. (ssd)
Destroyer PF Tender (DPF): The Flivver DPF is based on the ubiquitous DW. Like the full size PFT, it trades out its own weapons for special sensors and the firepower of a PF flotilla. (ssd)
Fast Patrol Ship (PF): The Flivver PF is a straight application of standard Flivver design. The center warp engine provides hoverwarp power, but the booster packs do not. As a result, the PFs are somewhat more limited in their ability to use hoverwarp. Standard hyperdrone racks are just too large to put into such a small hull, so a smaller version of the rack was designed. The smaller rack has only two magazines and only four rounds per magazine. Other than its size and capacity, it works exactly like a full sized hyperdrone rack. As with drone armed PFs, the Flivver PF is incapable of reloading its own racks; all reloads are done by the tender. (ssd)

Flivver Master Ship Chart


Master Ship Chart

Page last modified Thursday, 12/13/17.


Star Fleet Battles, SFB, Federation & Empire, Star Fleet Missions, Prime Directive, and all contents thereof are copyright (C) 1990 by Amarillo Design Bureau. Second Edition copyright (c) 1994 by Amarillo Design Bureau. These games were produced under license from Franz Joseph Designs, authors of the STAR FLEET TECHNICAL MANUAL. Elements of the Star Fleet Universe are the property of Paramount Pictures Corporation and are used with their permission.
Amarillo Design Bureau (ADB) and Task Force Games (TFG) are NOT related in anyway with these Web pages; it is an undertaking and opinions of a private citizen (hence unofficial), and is not construed to be an official position of either companies. Ideas and information from the games are presented without permission.