(JR1.0)  PELADINE WARSHIPS                       

(JR1.2) HEAVY CRUISER (CA):  SSD in Stellar Shadows #1  The mainstay of the Peladine fleet, the Resolute-class heavy cruiser is capable of performing a variety of duties, including patrol, exploration, diplomatic missions and front-line combat. The unified hull, a feature common to all Peladine ships, allows the ship to withstand a severe beating and still return fire. Notable are the copious laboratory facilities, installed at the insistence of the ever-inquisitive Phelan. Few heavy cruisers have such well-equipped facilities. Emphasis was also placed on shuttle bays, as the Peladine quickly learned the many uses of these small craft. The combined plasma/drone armament allows for some rather unique tactics, especially after the second drone rack is installed with the refit.

        Balcony positions: 3 left + 3 right.  

        Variants include the CC (JR1.3), CV (JR1.19), MAL (JR1.27), SR (JR1.28), SRV (JR1.28A), CCH (JR1.35), CD (JR1.47), and CVD (JR1.58).  The CX (JR1.201) was based upon this ship.  

(JR1.3)  COMMAND CRUISER (CC):   This ship was designed as a fleet flagship, with improved communications and command facilities, as well as more defensive phasers and reserve power.  The class was eventually supplanted as a flagship by the dreadnought (RJ1.4), but continued to serve as a squadron command ship until Y175, when most were converted to the CCH (RJ1.35) design.

        Balcony positions:  3 left + 3 right.

(JR1.4)  DREADNOUGHT (DN):   Built in an attempt to put a final end to the Lyran raiders in Peladine space (in the Lyran simulators, at any rate), the Determination -class dreadnought was produced at a rate of one per year from Y168 until X-ships began regular production in Y185.  Possessing the dreaded type-R plasma torpedo as well as the standard plasma array of a CA, the dreadnought was a very powerful vessel, even more so after the refit of Y170.  It proved capable of dealing with anything short of a battleship (or Andromedan Dominator) on equal terms, relying upon large banks of batteries to keep the R-torp in a rolling delay.

        The DN-design dedicated much space to both laboratories and shuttle bays, and for this reason the dreadnought was sometimes sent to investigate particularly dangerous phenomena, such as a space-dragon or hostile probe.

        Balcony positions:  4 left + 4 right.

        Variants include the CVA (JR1.29), SCS (JR1.32), DNH (JR1.54) and DNE (1.56).

(JR1.5)  LIGHT CRUISER (CL):  SSD in Stellar Shadows #1  The true workhorse of the Peladine fleet, the Steadfast-class light cruiser was produced in quantity, and was the source of most Peladine support vessels. The basic design was capable of performing most duties, and could deal with a heavy cruiser if flown well. Shielding was less than ideal; a problem dealt with in the refit but never truly solved. In addition to the standard improvements in warp output, two auxiliary reactors were installed with the refit, allowing the ship to put a few points of reinforcement to the inadequate shields.

        Balcony positions: 2 left + 2 right.  

        Variants include the MS (JR1.17), SC (JR1.18), CLE (JR1.20), CLA (JR1.20A), PFT (JR1.30), COM (JR1.38), and CSV (JR1.60).

(JR1.6)  DESTROYER (DD): The Focus-class destroyer was designed to fulfill two roles--fleet support vessel and light patrol unit.  As such, it was equipped with the heavier G-torps, rather than plasma-Fs, in order to participate in long-range fleet bombardment, as well as to pack a considerable punch alone.  A large laboratory facility was included for use while on independent patrol missions, and for additional seeking-weapon identification capability in fleet battles.  When S-torps became available, the fleet support capability was slightly diminished, as it proved impossible to deploy the newer torpedoes on a hull smaller than a cruiser.  

        Balcony positions:  1 left + 2 right. 

        The sole variant was the DDL (JR1.48; light cruiser hulls supplied most fleet support variants until the arrival of the war destroyer (JR1.25). 

(JR1.7)  FRIGATE (FF):  The Steady-class frigate was the smallest ship in the regular fleet. It was relegated to the role of fleet point-defense, and was rarely sent out on lone patrol. The relatively large lab facility was expected to be used in support of the fleet by identifying incoming seeking-weapons. Power was a definite problem until the refit provided additional warp power and stasis systems for the plasmas.

        Balcony positions: 2 left.

        Variants include the FFE (JR1.21), FFA (JR1.21A), and FFS (JR1.39).  The FFX (JR1.204) was based upon this ship.

(JR1.8)  POLICE CORVETTE (Pol):  Designed as a customs and safety vessel, the Foothold-class police corvette was capable of doing just that--grabbing a "foothold" until a real ship could show up.  The twin P-torps were impressive, but were also a severe drain on the tiny warp engines.  The "+" refit improved matters somewhat, but it was still prudent to operate these ships in teams of two or more.       

        No balcony.    

        Variants include the PolC (JR1.40).

(JR1.9)  FLEET TUG (Tug):  Equivalent to the tugs of most races, the Foundation-class tug was designed to provide logistical support in hostile situations (freighters were used in peaceful regions).  When carrying certain pods, the tug can become a powerful combat unit in its own right; however, with limited numbers of tugs in operation, sending a tug into frontline combat was avoided whenever possible. 

        The pods are in-line, the first attached to the tug, with the second (if any) attached to the first.  Note that the front pod will block the forward arc of weapons on the rear pod, while the rear pod will block the rear arc of weapons on the front pod (exception:  360-degree phasers are not blocked, as they are mounted on dorsal or ventral turrets and can clear the other pod [and the tug]).

Balcony positions:  1 left + 1 right. 

(JR1.10)  BATTLE POD (P-B):  This pod was designed to convert the tug to a combat capable unit (designated a battle tug, or BT).  It brings the tug up to the approximate level of a heavy cruiser, or slightly better.

        Note that it swivel mounts were never installed for the S-torps during the "+" refit;  the added bit of arc would have been blocked by the tug.

        On extremely rare occasions a tug may carry two of these pods, the combination designated as a bombardment tug (BBT).  As the plasmas on the rear pod would only be able to track in the left or right firing arcs, this configuration was primarily used in planetary assaults, with the tug in a high orbit around the planet at slow speeds, occasionally executing a full 180-degree turn to bring the off-side plasmas to bear.  This tactic was also employed against bases, where the power of four plasma-S torpedoes proved quite effective.

        No balcony.

(JR1.11)  CARRIER POD (P-CV): The carrier pod supports a full squadron of Piranha-1s, six fighters per bay.  In addition, it provides a bank of 360-degree phaser-2s for defensive fire, as well as drone-control capabilities equal to the sensor rating of the pod.

        Operationally, these pods are deployed in pairs on a tug, a configuration designated a carrier tug (CVT).  In such a configuration, the combined unit is limited to a maximum speed of warp 2.6, and must be deployed at the rear of any formation.

        On rare occasions, only one carrier pod will be deployed with a tug, forming a light carrier tug (CVLT).  This unit is capable of achieving fleet speeds, and can count on its superior maneuverability to survive brief combats.

        Following is escort and fighter information for the CVT:   

        Balcony positions: 4 left + 4 right (per pod).

 (JR1.12)  CARGO POD (P-C):  The typical member of the species:  a collection of cargo boxes in a duraluminum wrapper.  There are actually several types for a variety of cargoes:  dry goods, liquids, containers, etc., but they are functionally identical.  When detached, any hits on the pod are considered to be cargo hits.

(JR1.13)  DRONE POD (P-D):  This pod was used for long-range drone bombardment, as well as for planetary assault missions.  Up to 500 spaces of drones can be held in the large cargo bay.           

        When used in planetary assaults, two pods would usually be deployed on the tug, providing phenomenal drone capabilities as well as a limited EW-platform.

(JR1.14) PF TENDER POD (P-PF):  When interceptors were first deployed in Y179, a special pod was built as a support platform.  In Y182, with the deployment of PFs, more were built, supplementing the limited number of PF tenders in the fleet.      

        All mech-link positions, which are semi-internal, are accessible by the repair bays.

(JR1.15) REPAIR POD (P-R):  Used to repair critical units on the front line, there were never enough repair pods (or tugs to carry them) to go around.       

There are two repair-capable docking positions, one on either side of the pod.  This can be done even with the pod still attached to the tug, usually by docking to the aft end of the damaged unit.

(JR1.16) TROOP TRANSPORT POD (P-T):  A well-equipped pod, the P-T can carry up to 80 boarding parties, though the normal compliment is much smaller (32).  Both shuttles in the bay are GAS, and the pod is capable of making gravity landings (P2.432).    

        This pod is capable of limited independent operations (at sublight speeds).

        Balcony positions:  2 rear (because of this, the pod is always the hindmost when part of a two-pod combination.  If both pods are P-Ts, the foremost's balcony is blocked, though a hatch above the shuttle bay can be used to launch/receive shuttles at the standard rate).

(JR1.17)  MINESWEEPER (MS): One of the earlier conversions of the light cruiser, the minesweeper was the first Peladine unit to mount phaser-1s, and the last to do so for a long time (until the "+" refits in Y170).  This was a Peladine attempt to build a heavier phaser to better deal with mines.  Unfortunately, the result, while functionally identical to a phaser-1, was so bulky, and the power circuits so jury-rigged, that it could only be mounted in the warp nacelles, in the former plasma-P mounts.

        Despite this "technical difficulty," the minesweeper proved to be a very effective unit, with excellent mine warfare capabilities, both offensive and defensive.

        Two shuttles are MSS (M8.312).

        Balcony positions:  1 left + 1 right.

(JR1.18)  SCOUT CRUISER (SC):  This extraordinary EW-unit, deployed only two years after the ill-fated FFS (JR1.39), was the primary Peladine scout until the development of X-ships, even after the introduction of the DWS (JR1.44).  Despite a shortage of CL-hulls in later years, the Peladine admirals realized a good thing when they had it, and the scout cruiser was given priority in CL-hull construction and conversion until Y182, when the PFT (JR1.30) bumped the SC down a notch in priority.

        The combination of eight sensor channels, and the power to use them, marks this ship as perhaps the best fleet scout on either side of the galaxy.

        Note that the drone load for this ship normally consists of 25% probe drones.

        Balcony positions:  2 left + 2 right.

(JR1.19)  CARRIER (CV):  SSD in Stellar Shadows #1  A well-designed carrier, the CV is fully capable of front-line combat, possessing the weaponry of a refitted heavy cruiser. The long flight bays contain, per bay, three each Piranha-1 and Piranha-2, as well as two administrative shuttles (one of which was normally replaced with a MRS). Plasma-F reload facilities are provided for the six Piranha-2s on board.

        A distinct advantage of the CV-design is the ship's capability of launching every fighter, as well as two admin shuttles, in a single impulse using the balcony and track system (J1.53).

        Balcony positions: 7 left + 7 right.  

(JR1.20)  ESCORT CRUISER (ECL): Designed to escort the CV (JR1.19) and CVT (JR1.11), the ECL possessed phenomenal anti-fighter and anti-drone capabilities.  With its generous phaser array, G-type drone racks, ADDs and Plasma-D racks all controlled via a limited aegis rig (D13.4), the ECL was an excellent escort.

        Unfortunately, the ECL utilized the CL-hull, as did most other Peladine support ships.  As the scout cruiser (JR1.18) was at the top of the CL-hull priority pecking order, relatively few ECLs were built, and construction virtually ceased with the introduction of the new CWA (JR1.24).

        This ship has ready racks for Piranha-1s in the shuttle bays; it does not, however, carry any fighters of its own.

        Balcony positions:  2 left + 2 right.

(JR1.20A)  AEGIS CRUISER (ACL):   The ECL was improved in Y175, its limited aegis upgraded to full aegis (D13.0).  This was a short-lived upgrade, as the following year saw the production of the CWA (and the virtual elimination of the ECL/ACL).

        Other data as the ECL (above).

(JR1.21)  ESCORT FRIGATE (FFE):  Produced concurrently with the ECL (JR1.20), the FFE was virtually obsolete upon introduction, as frigate-hulls were becoming less and less survivable in the evolving combat environment.  The ship was very effective against drones and fighters, and because of this and its small size it was usually targeted for massed salvoes by enemy fleets.

        The phasers, G-racks, plasma-D racks and ADDs are controlled by a limited aegis rig (D13.4).

        This ship has reload facilities for Pirahna-1 fighters; it carries no fighters of its own.

        Balcony positions:  2 left.

(JR1.21A)  AEGIS FRIGATE (FFA):  An interim upgrade of the FFE, replacing the limited aegis with a full aegis rig (D13.0).

        Other data as the FFE (above).

(JR1.22)  WAR CRUISER (CW):  Upon receipt of improved weapons technology in Y168 (see JR1.R1 for details), the Peladine designed a new cruiser based upon the new technology, not merely using bits and pieces in refits.  Efficiency of production was a priority, as raids had intensified in recent years, and relations with the neighboring Lyrans had worsened (in fact, war was feared to be inevitable at this point).  Full-scale production began in Y170.       

        The Secure-class, though designated as a war cruiser, had armament nearly as powerful as the heavy cruiser (the subsequent NCA [JR1.37] contained power improvements, for the most part).  The ship is more than a match for other war cruisers.  Laboratory facilities were spartan, and the shuttlecraft contingent was reduced by a third, in order to lessen production cost.  The new phaser-1s were installed throughout, except for a pair of phaser-3s for rear defense.  Power was scarce, as the ship had two S-torps and two F-torps but the warp engines of a light cruiser (a deficiency corrected in the NCA).           

        Balcony positions:  2 left + 2 right. 

        Variants include the CWL (JR1.23), CWA (JR1.24), and CVP (JR1.59).

(JR1.23)  WAR CRUISER LEADER (CWL):  Designed as an economical alternative to the command cruiser (JR1.3), the CWL incorporated a number of improvements over the basic war cruiser.  The rear phaser-3s were replaced with phaser-1s, power was improved slightly by expanding the auxiliary reactors by 20% and the batteries by 25%, laboratory space was increased, and a flag bridge was added.

        The ship still suffered from power shortages, and production ceased upon introduction of the NCA (JR1.37).

        Balcony positions:  2 left + 2 right.

(JR1.24)  WAR AEGIS CRUISER (CWA):  SSD in Stellar Shadows #1   The only widely produced variant of the war cruiser, the CWA replaced the older ECL/ACL (RJ1.20/20A), freeing CL-hulls for conversion to scouts and minesweepers (and later PF-tenders). Not quite as effective as the ACL, but a good escort nonetheless.

        This ship has reload facilities for Piranha-1 fighters; it carries no fighters of its own.

        Full aegis rig (D13.0) controls all phasers, drone racks, plasma-D

racks, and ADD racks.

        Balcony positions: 2 left + 2 right.

(JR1.25)  WAR DESTROYER (DW):  SSD in Stellar Shadows #1    While the Peladine admiralty was seeking a more efficient cruiser, they were also planning a more powerful destroyer to support it. Utilizing newly-"acquired" technology, they designed a small, powerful unit with a versatile hull arrangement, able to be modified to several support roles, as well as perform well as a warship in its basic configuration.

        The Intensity-class DW design replaced destroyer construction, utilizing the same construction facilities. The ship had large warp engines for its size-class, providing ample power for the twin F-torps and the larger, centerline-mounted G-torp. The phaser array was not large, but was composed entirely of the newer phaser-1s. Both reactor and battery power were increased over the older destroyer design, and shielding was greatly improved.

        The ship was often employed as a fast attack vessel on the flanks of a battle, loading the G-launcher every two turns as a type-F and using its good maneuverability at high speeds to flank opponents.

        Balcony positions: 3 left.

        The DW spawned a number of variants, easing demands on CL-production.  These include the DWA (JR1.26), DWC (JR1.41), DWD (JR1.42), DWM (JR1.43), DWS (JR1.44) and DWT (JR1.45).  The DDX (JR1.202) and SCX (JR1.203) were based upon this ship.

 (JR1.26)  AEGIS WAR DESTROYER (DWA):  SSD in Stellar Shadows #1  This ship replaced the smaller FFE/FFA (RJ1.21/21A), providing a more-survivable small escort. The combination of ADDs, PL-Ds and G-racks provided excellent protection from drones and fighters (and PFs in later years). In desperate situations, the eight phaser-1s could be used against enemy ships, with impressive results.

        The ship has reload facilities for Piranha-1 fighters; it does not carry any fighters of its own.

        A full aegis rig (D13.0) controls all phasers, drone racks, plasma-D racks and ADD racks.

        Balcony positions: 3 left.

(JR1.27)  MAULER CRUISER (MAL):     In Y184, a Peladine force engaged a group of Andromedan satellite ships cut off from their mother ship (a Dominator).  The Andromedans were evidently low on fuel and supplies, and were defeated en masse.  By means still classified, Ranel marines managed to capture one  Andromedan ship:  an Asp-class mauler.  The ship was hauled home to a special dock under the purview of Peladine Intelligence, and was dissected and analyzed by the top minds of the Republic.  The phaser-2s were nothing new, of course, and the secret of the PA-panels was never unlocked, but the mauler weapon fascinated the top command.

        Within a year, the first MAL was built within the hollowed-out frame of a heavy cruiser.  More followed at the rate of one per year, all at the Intelligence dock.  The ships were placed under central command, from which they were detached to support important operations.  An officer from Intelligence was aboard each ship, whose job was to ensure the ship did not fall into enemy hands, regardless of circumstances;  he or she could order the destruction of the ship, even over objections of the captain.

        As with all maulers, this ship is subject to shock (D23.0).

        Balcony positions:  1 left + 1 right.

        (Side note:  the batteries from the captured Asp provided some of the final answers necessary to converting Peladine ships to X-technology.)   

 (JR1.28)  SURVEY CRUISER (SR):  When the Peladine realized just how closely they were boxed in by their neighbors, they decided that a survey ship capable of combat was in order.  The survey cruiser reflects this philosophy.  Based upon a heavy cruiser hull, the SR retained the heavy centerline torpedoes, as well as two-thirds of the phaser compliment.  A total of four drone racks were installed, ostensibly for using probe drones but also impressive in combat.  Special pods were attached to the sides of the ship, containing two special sensor arrays.  Two more sensor arrays replaced the plasma-Ps at the front of the warp nacelles.        

        The SR had impressive research capabilities.  A large laboratory facility was located just aft of the bridge.  Twin probe launchers, each with ten probes, flanked the phaser turret at the stern.  Ample transporters were provided for landing parties, and two cargo bays, each forward of a shuttle bay, provided storage for both scientific supplies and recovered material samples and artifacts.              

        The shuttle bays themselves were quite large, housing eight shuttlecraft total.  This was deemed necessary for a science vessel, and the many shuttles could also provide defensive fire in a conflict.  Because of these large shuttle bays, the survey cruiser became a test bed for fighter technology, and many were converted to the SRV (JR1.28A) configuration in wartime.        

Balcony positions:  2 left + 2 right.

(JR1.29) HEAVY CARRIER (CVA):  Seeing the need for a larger fighter platform, the Peladine extensively modified a dreadnought in Y175 to this configuration.  This ship retained the entire torpedo and phaser compliment of the DN, and was a very powerful carrier. 

        By reducing the number of drone racks by one and setting the batteries as low as possible, it was possible to provide "wrap-around" balconies for each of the two very large shuttle bays, providing eight balcony positions per bay.

   The ship originally had twelve plasma-F reload positions for the Piranha-2s;  these were reduced to six positions when the new Piranha-3 replaced 6 of the Piranha-2s in Y182.

        Balcony positions:  8 left + 8 right.  

(JR1.30)  PF TENDER (PFT):  SSD in Stellar Shadows #1  An experimental conversion of the light cruiser in Y180 produced the prototype of this unit; it was used with interceptors until Y182, when PFs became available and the PFT entered full production. Demand was so great that PFTs had priority for CL-hulls, even over the scout cruiser (RJ1.18).

        The ship was a fairly typical example of the breed. Repairs were possible on PFs docked to any of the mech-links, where collapsible repair bays (K2.63) were utilized.

        With the exception of the PFT pod (RJ1.14), and the SCS (RJ1.32) and BCS (RJ1.35), this ship was the only warship PFT in Peladine service.

        Balcony positions: 1 left + 1 right.

(JR1.31)  BATTLECRUISER (BC):  In an effort to keep its cruisers competitive, the Peladine launched the first of these ships in Y175, producing them at a rate of two per year thereafter.  The Righteous-class, designated a battlecruiser, was equivalent to the heavy battlecruisers of other races (much as was the Federation "battlecruiser").

        Built on a "stretched" heavy cruiser hull, the battlecruiser incorporated a third heavy torpedo centerline, and the newer phaser-1s in the wings and in the 360-degree turret.  The rear-defense phaser-2s were supplemented with a pair of phaser-3s.  A third drone rack was added.  Power production was impressive, as both the impulse engines and auxiliary reactors were expanded by 50 percent.

        The mech-links were included in the original design to carry a pair of interceptors, which were replaced with PFs in Y182.

        Balcony positions:  3 left + 3 right.

        Variants include the BCV (JR1.34) and BCS (JR1.35).

 (JR1.32)  SPACE CONTROL SHIP (SCS):  The CVA Lightning Swarm was converted to this design in Y183; at least one more was built as new construction, perhaps two.

        A fairly standard SCS, this ship was equipped with facilities for 12 Piranha-1 fighters and a full flotilla of six PFs.  All mech-link positions are equipped with a collapsible repair bay (K2.63).  Due to the positioning of the repair bays, it proved impossible to retain the "wrap-around" balconies of the CVA, and the shuttle bays themselves, reduced in size, were move 20 meters forward. 

        Balcony positions:  3 left + 3 right.

(JR1.33)  BATTLESHIP (BB):   The Decisive -class battleship was planned on a dreadnought hull "stretched" over 80 meters, with thickened wings supporting massive warp engines.  Twin centerline-mounted R-torps, as well as twin S-torps and the two nacelle-mounted F-torps, were envisioned, to be complemented by a massive phaser battery containing 18 phaser-2s and 5 phaser-1s.  Mech-links for four PFs were to be included, as well as facilities for six Piranha-1 fighters.

        The project was continually delayed by problems in the prototype warp engines.  The problems were eventually resolved, and one battleship, the Decisive Achievement, was completed in Y180; however, by this time X-ships were on the drawing board, and the entire project was scrapped as obsolete.  The massive warp engines and nacelles constructed for the second vessel of the class (the only part of the ship actually built) ended up in the Ranel Polytechnic Institute, where they were displayed to engineering students as the upper limit in warp design. 

        Balcony positions:  6 left + 6 right.

        Variants include the BBV (JR1.52) and SDS (JR1.53).

(JR1.34)  BATTLE CARRIER (BCV):  Desiring a more powerful fleet carrier, the Peladine converted the battlecruiser Swift Strike during construction to this design in Y181.  The ship retained the power and weapons of the battlecruiser, expanding the shuttle bays through better management of hull-space to accommodate the dozen Piranha-1 fighters. The probe launcher of the basic design removed due to space considerations; while this was unusual, it was felt that the ever-present escorts could fill the need for probes.

        The two casual PFs were often assigned to the fighters, one per squadron, as "fighter leaders," dealing with larger threats to the squadrons (such as an enemy PF sent in to kill off the fighters).

        Designs for this ship existed as early as Y176, but no battlecruiser hulls could be spared until Y181.  The Swift Strike remained the sole ship of this class, which was superseded the following year by the BCS (JR1.35).  

        Balcony positions:  3 left + 3 right.

(JR1.35)  BATTLE CONTROL SHIP (BCS):   In Y182 the Rapid Strike, planned to be the second BCV, was converted during construction to this design, taking advantage of the new Stingray-class PFs.  Of the two BC-hulls built per year afterward, one would usually be a BCS.

        The design packed the hull to the limit.  The fighter complement was cut to six, and a flotilla of PFs was added, along with repair systems.  As with the BCV, all weapons and power systems were retained.  Balcony space was, by necessity, slightly reduced.   

         Balcony positions:  2 left + 2 right.

(JR1.36)  HEAVY COMMAND CRUISER (CCH):  This ship, an upgrade of the CA/CC design, was first launched in Y175.  The design pushed the hull to the limit.  All refits to the command cruiser were included in the design.  Both the reactors and batteries were expanded, easing power management.  Firepower was improved by replacing the phaser-2 banks in the wings with an identical number of phaser-1s.  An unfortunate effect of the redesign was a reduction in balcony space.

        Almost all heavy and command cruiser production was switched over to CCH production after Y175; existing CAs and CCs were not converted.  Variants based on the CA (such as the CV and SR) remained in production.

        Balcony positions:  2 left + 2 right.

(JR1.37)  NEW HEAVY CRUISER (NCA):   The development of the CCH effectively ended heavy cruiser production.  To fill the gap, the CW design was improved with expanded power and shuttlecraft facilities to bring it up to the level of a true heavy cruiser.  The hull was lengthened 10 meters to accommodate the improvements.  Lab facilities were improved somewhat, but remained spartan next to those on the older CA design.  The warp engines were redesigned to bring them up to heavy cruiser standards. 

        Balcony positions:  2 left + 2 right.

(JR1.38)  COMMANDO CRUISER (COM):  The first of many variants of the light cruiser, the commando cruiser was first deployed in Y125, in response to planetary invasions by the Kzinti.  The ship was designed to be capable of planetary landings (P2.434) in order to quickly recapture the violated worlds; it required much work, however, to get the thing back off the ground.

        Expanded shuttle bays were included in the design, which included an HTS.  There were not many transporters for a commando ship, but the many shuttles and the landing capability were expected to fill the gap.

        The 32 boarding parties include two Commando and three Heavy Weapons Squads.  Three GCV and three GAS, along with the HTS, were included in the BPV.

        Balcony positions:  2 left + 2 right.

(JR1.39)  SCOUT FRIGATE (FFS):  The earliest of the Peladine EW-platforms, the FFS was soon found inadequate for fleet support missions, resulting in the development of the excellent scout cruiser (JR1.18).

        Small numbers of scout frigates remained in production, both to supplement the scout cruisers and to provide scouts for small squadrons.  The deployment of the DWS (JR1.44) put an end to FFS production, and only one survived to receive the drone rack refit in Y175.

        Balcony positions:  2 left.

(JR1.40)  COMMAND CORVETTE (PLC): Designed to provide a leader for a squadron of police corvettes, this ship included improved command and support facilities.  A flag bridge was added for a police commodore to operate from, and the cargo bays were removed to allow for a small lab facility and an additional transporter.  The shuttle bay was doubled in size.  The design also incorporated the various improvements that eventually became the "+" refit for the police corvette as standard equipment.

        The improved command and communications capabilities of this vessel permitted the deployment of four-ship police squadrons.  These ships comprised approximately 20% of all police ship construction after Y140.

        No balcony.

(JR1.41)  COMMAND WAR DESTROYER (DWC): This ship provided a leader for war destroyer squadrons.  Command and control facilities were improved, and there was a modest increase in firepower (provided by an additional drone rack and 360-degree phaser-1).

        Balcony positions:  3 left.

 (JR1.42)  DRONE WAR DESTROYER (DWD):  SSD in Stellar Shadows #1  Built to provide fleet drone support, the DWD was also capable (barely) of long-range drone bombardment missions, utilizing its single special sensor array.

        Balcony positions: 3 left.

(JR1.43)  WAR MINESWEEPER (DWM):  SSD in Stellar Shadows #1  As mine warfare intensified, and the demand on light cruiser hulls for variants was increased, the DWM was deployed to relieve the pressure in critical areas. The forward shield was heavily reinforced, providing protection even from a NSM blast. Mine racks were installed beside the shuttle bay, and tractors for minesweeping replaced the plasma-Fs in the nacelles. Two admin shuttles were replaced with MSSs.

        Balcony positions: 3 left.

 (JR1.44)  WAR DESTROYER SCOUT (DWS):  SSD in Stellar Shadows #1  A very capable small scout with four sensor channels, the DWS completely replaced the obsolete scout frigate (RJ1.39) in production, and relieved the demand somewhat for scout cruisers (RJ1.18).

        Balcony positions: 3 left.

(JR1.45)  WAR TRANSPORT (DWT):  Used for priority resupply missions, such as carrying fighters and supplies to front line carrier groups and other fleet elements.  Note that this is not a LTT, and cannot carry pods (the Peladine never deployed a LTT).

        One HTS shuttle is included as standard equipment.

        Balcony positions:  3 left.

(JR1.46)  SPACE CONTROL POD (P-SC): In an attempt to field more space control ships without sacrificing dreadnought production, the Peladine constructed a pod of this type in Y184.  Operationally, the unit was slow and underarmed, and no further pods were built.

        This is a double-weight pod.

        Balcony positions:  4 left + 4 right.

        The tug/pod combination is designated a TSC.

(JR1.47)  DRONE CRUISER (CD):  An early variant of the heavy cruiser, the drone cruiser was designed for long-range drone bombardment.  It was equipped with two special sensor arrays, side-mounted as on the survey cruiser (RJ1.28).  300 spaces of drone are stored in the two cargo bays (FD2.445).  All drone racks were installed as type-B.

        Balcony positions:  3 left + 3 right.

(JR1.48)  DESTROYER LEADER (DDL):  This ship was originally developed to be a leader for destroyer squadrons; however, wile the firepower was significant, the loss of tractor beam redundancy and 50% of the research facilities was seen by captains as too high a price to pay. As such, the planned production run was cancelled, with only two or three ships produced to fulfill shipyard contracts.

        After the advent of the "plus" refit and the S-torp, however, the original DD design was seen to be at something of a disadvantage, as the G-torps could not be upgraded on such a small hull. The DDL design was resurrected, and a number of destroyers were converted to the design. The single tractor beam remained something of a sore point, but was accepted as the price of continuing with these old ships in an evolving combat environment.

        Balcony positions:  1 left + 2 right.  

(JR1.49)  FAST CRUISER (CF):  First built in Y172, the Response-class fast cruiser was designed to live up to its class name:  to be able to respond to emergencies on little or no notice.  In practice, however, the few ships of this class that were built ended up as fast raiders, striking soft targets behind enemy lines.

        Balcony positions:  3 left + 3 right.  

(JR1.50)  HEAVY WAR DESTROYER (HDW):  Typical of the HDW breed that cropped up around Y180, the Purposeful class could fill a variety of rolls; however, it was almost never configured in the roll of a full-fledged carrier, due to Peladine fleet philosophy regarding carriers.  It is, however, equipped with facilities for two casual Piranha-1 fighters, and is treated as a "casual carrier."

        Balcony positions:  3 left.  

(JR1.51)  FAST CARRIER RESUPPLY FRIGATE (FCR):  The last several non-X frigates produced by the Peladine were configured as carrier resupply frigates; this was the last survivable role available for the venerable frigate hull to fill.

        Balcony positions:  2 left.  

(JR1.52)  BATTLESHIP CARRIER (BBV):  The Peladine battleship program did not proceed beyond the first ship, due to the development of X-technology.  If it had, however, it is likely that a carrier variant would have been built of a design similar to this one.  The large balconies would have greatly facilitated coordinated strikes.

        Balcony positions:  9 left + 9 right.  

(JR1.53)  STELLAR DOMINATION SHIP (SDS):  Another probable offshoot of the abortive battleship program.  The entire strike group would have been able to have been staged on the spacious balconies.

        Balcony positions:  6 left + 6 right.  

(JR1.54)  HEAVY DREADNOUGHT (DNH):  Starting in Y178, Peladine dreadnoughts were either built or refitted to this configuration, as an interim measure pending the planned production of battleships.  With a modest increase in phaser and drone firepower, as well as in power generation and storage capacity, these ships performed very well in their intended role.

        Balcony positions:  4 left + 4 right.  

(JR1.55)  LIGHT DREADNOUGHT (DNL):  Designed concurrently with the fast cruiser, the Diligent-class light dreadnought was designed to lead squadrons of fast warships to head off sudden incursions.  With the short production run of the fast cruiser and the emergence of fleet carriers, however, this mission was no longer practical by the time the first ship of this class was launched in Y172.  In the end, the two light dreadnoughts produced were relegated to raiding duty.

        The design sacrificed the heavy type-R torpedo to save both mass and power.  With the large torp gone, batteries were reduced by 25%, saving further weight and space.  Between the reduced power demands and the smaller hull, the ship was indeed very, very fast, both in and out of combat.

        Balcony positions:  4 left + 4 right.

        The DVL (JR1.57) is a variant of this ship. 

(JR1.56)  EARLY DREADNOUGHT (DNE):  The original Peladine dreadnought design was on the drawing board along with the heavy cruiser in Y120; however, production of the ship was deferred for a wide variety of reasons until Y155, and even then only a very small number were constructed to serve as fleet flagships.  The last of these ships was refit (with a slightly stretched hull) as a modern dreadnought in Y171.

        Balcony positions:  4 left + 4 right.  

(JR1.57)  LIGHT DREADNOUGHT CARRIER (DVL): One of the Diligent-class light dreadnoughts was converted to this design in Y174, in an effort to create a fast carrier. The design was not entirely successful, and the experiment was not repeated.

        Balcony positions: 4 left + 4 right.

(JR1.58)  INTERDICTION CARRIER (CVD): Based on a heavy cruiser hull, a small number of ships of this class were built as stand-off platforms for large fighter strikes. The large balconies permitted rapid launch-and-recovery operations, but the ship was still vulnerable to an enemy willing or able to close the distance, and a substantial escort group was necessary for protection.

        Balcony positions: 7 left + 7 right.

(JR1.59)  PATROL CARRIER (CVP):  One of the very few Peladine war cruiser variants, the patrol carrier was designed as another stand-off fighter platform. As with the CVD (JR1.58), rapid launch-and-recovery was possible due to the large balconies. The ship suffered the same problem as the CVD, however, in its vulnerability to close combat; compounding this problem was the lack of a large escort group, as other carriers had priority.

        Balcony positions: 5 left + 5 right.

(JR1.60)  SCOUT CARRIER (CSV): Deployed in Y180 to carry Super Piranhas into battle, the CSV, while based on the light cruiser hull, was a substantially different design from the later PFT (RJ1.30). With four special sensors, the CSV was intended to be a fleet EW support platform in addition to a heavy fighter carrier, and it managed this role well.

        Balcony positions: 4 left + 4 right.