2165 – Dragon (as built)

After the end of the Romulan war, most ships in the  Starfleet were small, lightly armed exploratory cruisers (such as the former UESN Daedalus and Comet classes). Most of the UESN’s heavy cruisers (Conqueror class) and fighter-carriers (Yorktown class) had been mothballed, repurposed, scrapped, or sold off to local defense forces, with only a small number entering service with Starfleet.

To meet any potential remaining Romulan  threat, Starfleet needed to replace its Conqueror-class heavy cruisers.  The large crew complements and offensive mission profile made them poorly suited for a more defensive role.

In April 2163 Starfleet issued a request for proposals for the Dragon class of border-defense heavy cruisers. The requirement was for firepower (both missile and beam weaponry) at least 33% greater than that of Conqueror. Cruising and maximum speeds were wf 3.4 and wf 4.5,again an improvement over the Conqueror. Displacement was planned to be 150,000 tons or less with a crew of 430 officers – both approximately a third of those of Conqueror. These ships were planned to be less expensive to design, construct, and operate, but still  be more effective for border defence than the wartime Cruisers. 20 Ships were planned, to commission for 2166 onwards. This baseline ship is shown as the Dragon Mk1 on the Data sheet.

The successful design was in essence a scaled up Daedalus, using some Comet style components as well. Construction of the  class began in August 2164, but problems were encountered as the first Dragon began to be fitted out with various components supplied by subcontractors. The challenging requirements led to many of these systems being designed specifically for the Dragon class, and also to these systems having an impact on the overall design. In addition Starfleet Intelligence threat analysis led to a requirement for across-the-board performance increases for all ship’s systems. Accordingly, the damage and ranges of all weaponry were to be increased by an average of 25%;  and cruising and maximum speeds were increased to wf 3.6 and wf 4.7. This improvement was to be delivered from just a 10% increase in crew size and displacement.

To meet the new performance requirements, numerous changes were made. To increase the cruising and maximum speeds, a more powerful warp drive with larger reactor  was installed requiring the addition of a separate “reactor hull”. In addition, the 129-m-long nacelles were replaced by 157-m-long units. As well as the increase in firepower the missile load was increased, and the shuttle bay enlarged.  These  changes further decreased the space that could be used for crew quarters, stores, and life-support systems. Dragon was now 257 m long, with an estimated displacement of 180,000 tons, and the various technical issues were still to be overcome. This is the Mk2 configuration.

In December 2165, Hull #1 was christened USS Fafnir (NCC-213) and launched to begin trials despite the ongoing integration problems. Upon commencement of trials  construction was authorized to begin on the next 3 ships of the class. However the trials of Fafnir quickly revealed numerous problems. The most severe being that the firing of a full missile salvo from the forward missile tubes at attack speed  caused the mounts for the p forward deflector and targeting sensors to become misaligned. This was resolved by structural reinforcement. High speed warp runs revealed harmonic flexing from the nacelle supports propagating throughout the length of the ship – these vibrations played havoc with navigation, weapons targeting, and prevented Fafnir from reaching design speeds. In the longer term these vibrations would lead to fatigue failure possibly resulting in the catastrophic loss of spaceframe integrity. To resolve these issues it was necessary to shorten and thicken the neck connecting the primary and secondary hulls and adding redundant supports for the nacelles on the reactor hull. Fafnir was now 247 m long but displaced 194,000 tons

By October 2166 most of the outstanding problems were being solved: the lead ship, USS Fafnir, was commissioned. Unfortunately by  2167 Starfleet’s requirements had changed, and the defensive posture of the Dragon meant they were ill suited for use in a exploration role. The lack of internal space owing to the level of equipment and weaponry fitment meant that there was no space for the installation of laboratories, scientific equipment, crew quarters, common areas, and long-term life-support systems. With the Romulan threat in abeyance, the Dragon had become a costly and immobile white elephant, and  in November 2167 Starfleet cancelled the final 10 ships of the class before construction had begun.

Despite these problems the 10 completed Dragons proved to be rugged and reliable ships –  however, all Dragons were withdrawn from front-line service by 2180 without ever having fired a shot in anger.

The Dragon-class heavy cruiser USS Jörmungandr (NCC-218) is on display in the Starfleet Museum.

Class: XI
Year: 2165
Ship Source: Starfleet Museum
Ship Datasheet: Coming Soon

Dragon Mk2 Configuration:

dragon2

Commissioned Ships

  • USS Fafnir NCC-213 completed in this configuration, but was modified during trials

2164 – Dragon (Design)

After the end of the Romulan war, most ships in the  Starfleet were small, lightly armed exploratory cruisers (such as the former UESN Daedalus and Comet classes). Most of the UESN’s heavy cruisers (Conqueror class) and fighter-carriers (Yorktown class) had been mothballed, repurposed, scrapped, or sold off to local defense forces, with only a small number entering service with Starfleet.

To meet any potential remaining Romulan  threat, Starfleet needed to replace its Conqueror-class heavy cruisers.  The large crew complements and offensive mission profile made them poorly suited for a more defensive role.

In April 2163 Starfleet issued a request for proposals for the Dragon class of border-defense heavy cruisers. The requirement was for firepower (both missile and beam weaponry) at least 33% greater than that of Conqueror. Cruising and maximum speeds were wf 3.4 and wf 4.5,again an improvement over the Conqueror. Displacement was planned to be 150,000 tons or less with a crew of 430 officers – both approximately a third of those of Conqueror. These ships were planned to be less expensive to design, construct, and operate, but still  be more effective for border defence than the wartime Cruisers. 20 Ships were planned, to commission for 2166 onwards. This baseline ship is shown as the Dragon Mk1 on the Data sheet.

The successful design was in essence a scaled up Daedalus, using some Comet style components as well. Construction of the  class began in August 2164, but problems were encountered as the first Dragon began to be fitted out with various components supplied by subcontractors. The challenging requirements led to many of these systems being designed specifically for the Dragon class, and also to these systems having an impact on the overall design. In addition Starfleet Intelligence threat analysis led to a requirement for across-the-board performance increases for all ship’s systems. Accordingly, the damage and ranges of all weaponry were to be increased by an average of 25%;  and cruising and maximum speeds were increased to wf 3.6 and wf 4.7. This improvement was to be delivered from just a 10% increase in crew size and displacement.

To meet the new performance requirements, numerous changes were made. To increase the cruising and maximum speeds, a more powerful warp drive with larger reactor  was installed requiring the addition of a separate “reactor hull”. In addition, the 129-m-long nacelles were replaced by 157-m-long units. As well as the increase in firepower the missile load was increased, and the shuttle bay enlarged.  These  changes further decreased the space that could be used for crew quarters, stores, and life-support systems. Dragon was now 257 m long, with an estimated displacement of 180,000 tons, and the various technical issues were still to be overcome. This is the Mk2 configuration.

In December 2165, Hull #1 was christened USS Fafnir (NCC-213) and launched to begin trials despite the ongoing integration problems. Upon commencement of trials  construction was authorized to begin on the next 3 ships of the class. However the trials of Fafnir quickly revealed numerous problems. The most severe being that the firing of a full missile salvo from the forward missile tubes at attack speed  caused the mounts for the p forward deflector and targeting sensors to become misaligned. This was resolved by structural reinforcement. High speed warp runs revealed harmonic flexing from the nacelle supports propagating throughout the length of the ship – these vibrations played havoc with navigation, weapons targeting, and prevented Fafnir from reaching design speeds. In the longer term these vibrations would lead to fatigue failure possibly resulting in the catastrophic loss of spaceframe integrity. To resolve these issues it was necessary to shorten and thicken the neck connecting the primary and secondary hulls and adding redundant supports for the nacelles on the reactor hull. Fafnir was now 247 m long but displaced 194,000 tons

By October 2166 most of the outstanding problems were being solved: the lead ship, USS Fafnir, was commissioned. Unfortunately by  2167 Starfleet’s requirements had changed, and the defensive posture of the Dragon meant they were ill suited for use in a exploration role. The lack of internal space owing to the level of equipment and weaponry fitment meant that there was no space for the installation of laboratories, scientific equipment, crew quarters, common areas, and long-term life-support systems. With the Romulan threat in abeyance, the Dragon had become a costly and immobile white elephant, and  in November 2167 Starfleet cancelled the final 10 ships of the class before construction had begun.

Despite these problems the 10 completed Dragons proved to be rugged and reliable ships –  however, all Dragons were withdrawn from front-line service by 2180 without ever having fired a shot in anger.

The Dragon-class heavy cruiser USS Jörmungandr (NCC-218) is on display in the Starfleet Museum.

Class: X
Year: 2164
Ship Source: Starfleet Museum
Ship Datasheet: Coming Soon

Dragon Mk1 Configuration:

dragon1

Commissioned Ships

  • USS Fafnir NCC-213 was commenced in this configuration but was modified before commissioning,

2246 T2 Vastagor Lattam (Death Talon)

Introduced about Stardate 1/8905 and assigned as groups to various fleets in the Romulan navy, the T-2s were designed for escort and patrol duties.  Though they had no room to spare for leisure, and though the quarters and work areas were quite cramped, the class is considered to be roomy and comfortable by early standards.

After Stardate 1/9902, vessels appeared in which the hull had been modified to hold a plasma weapon.  After Stardate 2/0001, the first Type 3s appeared, with increased length, weight, and crew complement.  The firepower of the new type was more than double its original configuration, and the newer shields gave a combat efficiency three times greater than the Type 1.  After several years of service, the destroyers began undergoing minor changes to the hull configuration and interior layout, and, beginning with the Type 6, the weapons mountings were increased from four to six.

The Type 7, with this new weapons arrangement, a more powerful impulse engine, and more efficient shields, made its appearance about Stardate 2/0803.  A cloaking device also was installed on the Type 7.  Reports from the Klingons indicate these were useful in escort duties.  Many times, Klingon long-range sensor scans of Romulan convoys would show few escort vessels, but actual contact would reveal five to ten T-2s materializing from nowhere, making the supposed easy Klingon victory and prize a mere dream.
Of the approximately 250 T-2s built, about 150 are in reserve fleets and another 20 are being used as training vessels.  Only five of these ships have been sold to the civil sector, all of which operate in the the Triangle or along Federation borders; it is not known if any of these are armed.
The class is named from the Romulan vastagor lattam (death talon), a reference to the Mogari, a large carnivorous bird native to Romulus.  These man-sized birds are reported to swoop down on their prey at speeds up to 120 mph and inflict fatal blows with their long talons.

2269 – V11B Thevas’kalabam (Stormbird B)

Because of the Romulan-Klingon technological exchange treaties, the Klingons agreed to exchange their D-7A Class cruisers for Romulan plasma weapons and several old-style cloaking devices.  These vessels, delivered Stardate 2/09, 2/12, and 2/17 became the V-11 Class.

The 80 vessels in the initial shipment were stripped of their weapons, but the Klingon engines were retained to form the Type 1.  The 42 in the second shipment were delivered without engines, shields, or weapons; these were fitted as the Type 2 with a plasma weapon and more efficient shielding.  The 50 vessels in the final shipment also were delivered completely stripped, and these were fitted as the Type 5, with fore and aft-mounted photon torpedoes reminiscent of the Klingon D- 7M Class.  Types 3 and 4 are modified Type 1s.

Although 172 of these ships have entered Romulan service, they are not liked by their commanders or crews, many of whom consider them to be enemy vessels.  In recent years, the Romulans have begun deploying many of the approximately 160 remaining in active service along the Klingon borders in direct violation of the signed accords.  The class is named for thevas’kalabam (bird of storms), a small, flying predator of Remus.  These nocturnal avians are often seen gliding on the rising winds before a storm and it is said they are capable of traveling hundreds of miles in the vanguard of a storm.

Class: VIII Year: 2269
Ship Source: FASA/Paramount  Pictures Ship Datasheet: Coming Soon

v-11b-100

2266 – V11A Thevas’kalabam (Stormbird)

Because of the Romulan-Klingon technological exchange treaties, the Klingons agreed to exchange their D-7A Class cruisers for Romulan plasma weapons and several old-style cloaking devices.  These vessels, delivered Stardate 2/09, 2/12, and 2/17 became the V-11 Class.
The 80 vessels in the initial shipment were stripped of their weapons, but the Klingon engines were retained to form the Type 1.  The 42 in the second shipment were delivered without engines, shields, or weapons; these were fitted as the Type 2 with a plasma weapon and more efficient shielding.  The 50 vessels in the final shipment also were delivered completely stripped, and these were fitted as the Type 5, with fore and aft-mounted photon torpedoes reminiscent of the Klingon D- 7M Class.  Types 3 and 4 are modified Type 1s.
Although 172 of these ships have entered Romulan service, they are not liked by their commanders or crews, many of whom consider them to be enemy vessels.  In recent years, the Romulans have begun deploying many of the approximately 160 remaining in active service along the Klingon borders in direct violation of the signed accords.  The class is named for thevas’kalabam (bird of storms), a small, flying predator of Remus.  These nocturnal avians are often seen gliding on the rising winds before a storm and it is said they are capable of traveling hundreds of miles in the vanguard of a storm.

Class: VIII Year: 2266
Ship Source: FASA/Paramount  Pictures Ship Datasheet: Coming Soon

v-11a-100

2265 – V9 Temar Vastaram (Night Flyer)

The V-9 Class, created from plans for the older V-8 (Bird Of Prey) Class, was constructed in response to the need for increased firepower and speed.  Its similarity to the V-8 on casual inspection is responsible for the prolonged myth that the V-8 was the mainstay of the Romulan Navy. 

The Type 1 was introduced about Stardate 2/0805.  It was the first vessel in the Romulan fleet to carry two plasma weapons, and it had an impressive array of disruptors and a cloaking device.  This vessel reportedly became extremely popular with front line commanders, because of its ability to deliver multiple plasma weapon strikes.  It did not, however, address the speed problem still seen in the concurrent Type 4 V-8, and several power plant changes resulted in the successful Type 6.

Of the approximately 180 V-9s constructed, about 160 remain in active service; of these, some are known to be assigned to Romulan Intelligence as training vessels.  There are reports of these vessels operating within the Triangle.

The class is named from the RomuIan temar vastaram (night flyer), in reference to a small, nocturnal, flying predator native to Remus.  The Eridam Papers state that they were the source of many ancient legends and myths about invisible predators from another dimension.

2257 – V7 Aye Mosaram (Whitewind)

Like their counterparts in the V-6 Class, the V-7s were designed for multiple roles, with spacious in- teriors and complete onboard research facilities.

The Type 1 entered service about Stardate 2/12 and is still being produced as a support ship, even though it is not as efficient in combat as later models.  Mounting the RPL-2 plasma weapon and a cloaking device, the Type 1 is capable of operating alone.

The Type 3, introduced about Stardate 2/17, is the preferred model of the class.  It mounts two additional disruptors and three photon torpedoes, and it has more efficient shields.

Of the approximately 80 V-7s built, nearly all remain in active service.  Current production of the Whitewind is estimated at six per year.

The aft weaponry of the V-7s has set the standard for the Romulan Navy, as exemplified by this Project Grey Ghost report of an incident between two V-7s and two Klingon L-9 class frigates. The V-7s, investigating asteroid clusters, detected the Klingons as they approached.  Both V-7s cloaked and deployed.  As the unsuspecting Klingons began surveying the asteroids, the V-7s de-cloaked and opened fire, only to have the Klingons disappear from view and sensor, obviously taking advantage of cloaking capabilities acquired in the technological exchange.  In the waiting game that followed, all four ships remained cloaked and invisible to sensors for several hours.  Finally, one of the Klingon commanders became impatient and attempted to warp away from the area.  Unfortunately, his path of departure resulted in a collision and catastrophic explosion.  The remaining ships immediately de-cloaked, only to find themselves lying aft to aft, which put the Klingon at a disadvantage because of its lack of torpedoes to the rear.  It suffered serious damage and surrendered to the Romulan commander, who allowed the Klingon to leave after surrendering the cloaking device.

The class is named for a meteorological disturbance peculiar to Remus.  As described in The Eridam Papers, twice per Remus year, a hot wind blows across the northern hemisphere for as long as five days.  Mineral particles from the western cliffs are borne aloft by the winds, and, at night, their phosphorescense causes the hemisphere-wide nightglow that gives the weather phenomenon its name aye mosaram (white wind).

Again, to make this class fit in the right position I’ve bought it forwards, this can be attributed to an error in Project Grey Ghost’s data.

2257 – V8 Vas Hatham (Bird of Prey) (“Cricket”)

On Stardate 2/0710 (2266), a V-8 was encountered by a Star Fleet cruiser patrolling the Neutral Zone, the first such contact in over 100 years and the very first visual contact with a Romulan war vessel.  The incursion into Federation space obviously was intended to test UFP defenses, and the V-8 destroyed several listening posts and bases before being heavily damaged by the Federation vessel and self-destructing to avoid capture.  Because of this incident, and because these ships were encountered in increasing numbers afterward, this vessel, more than any other, has been identified with Romulan military actions.  For many years, these vessels were believed to be the mainstay of the Romulan fleet, but improved intelligence reveals that this was a misconception.

The vessel was designed to carry the RPL-2 plasma weapon; because of its size and bulk, the Type 1 ships–136 meters long–actually were built around the 110-foot-Iong weapon.  The other major feature of the Type 1 was the use of new shielding technology.  The Type 4, with upgraded disruptors, was introduced to overcome the inadequate firepower of earlier models.

Of the approximately 100 ships built, about 40 are assigned to reserve fleets.  Six have been modified and sold to the civil sector, including two Type 1s, one each of Type 2 and Type 3, and two Type 4s, all of which operate in and out of the Triangle.

The class is named for the Romulan vas hatham (bird of prey), in reference to a huge, flying predator reportedly native to Romulus, but so revered that they have been transplanted to several of the conquered worlds in the empire.  Living for nearly 100 years, these avians can reach nearly giant proportions, some having wingspans as wide as 50 feet and weighing as much as 400 pounds.

Class: IX Year: 2257
Ship Source: The Starfleet Museum FASA Ship Datasheet: Coming Soon

v8-100

2256 – V6 S’ten Vastam (Gallant Wing)

The V-6 class was considered to be the ultimate replacement to fill the need for both a military vessel and a research vessel.  Designed much like Star Fleet research cruisers, they are well equipped for research duties and for combat.

At the time of their introduction about Stardate 2/09, they were the most powerful ships in the fleet.  The Type 1 mounted six of the most powerful disruptors available and the RPL-2 plasma weapon.  Although these vessels never saw combat with any Federation ships, it is speculated that this model would have been an even match for a Constitution Class cruiser.

With the Type 5, introduced about Stardate 2/11, the combat efficiency improved because its more powerful disruptors, more efficient shields, and stronger superstructure.  At this time, all Type 1s were recalled for refitting to the new configuration, and, by Stardate 2/13, this process had been completed.  The Type 5 remained in service until about Stardate 2/22, when all had been converted to the Type 7.

The Type 7, introduced on Stardate 211607, mounted improved engines and was structurally improved.  Vessels of this type are expected to remain a mainstay of the active Navy.

Of the approximately 100 V-6s built, nearly all remain in active service.  One operates as a private research vessel, appearing infrequently in the Triangle.

The class is named from the RomuIan s’ten vastam (gallant wing).

NB To fit in I’ve decided that this class was actually commissioned 10 years prior to the converted FASA date