Ships of The Star Fleet 3

SHIPS OF THE STA RFLE ET
2414
The Standard Reference Guide To The Vessels of Starfleet
Ships of t he St arf leet
By The Red Admiral
Starfleet Operations/Advanced Starship Design Bureau
Copyright 2414 Starfleet Department of Technical Services

Memory Alpha Catalogue Data:
UFPI ITP/SP SOTS2414
This edition of Ships of the Starfleet is authorized for viewing only in member star systems of the United Federation of Planets, its territories and possessions, affiliated star systems and
select independent or neutral star systems.
This document and its entire contents Copyright
2012 MTD Publications
All rights reserved. We request that no part of this document be reproduced in any form or by any means, or stored on any electronic server (ftp or http) without the written permission of the author.
It is produced for purely informational and recreational purposes on a not-for-sale/not-for-profit, free-distribution basis.
This publication follows the form and layout of the Ships of the Star Fleet publications published by Mastercom Data Center. Though inspired in part by these works, the publication is not intended as a copyright
infringement in any way shape or form.
This publication includes data and images from Paramount Pictures and various other sources. A complete list can be found in the Bibliography at the end. Any display of copyrighted materials is not intended as an
infringement on the rights of the respective copyright holders in any way shape or form.
SHIPS OF THE STARFLEET
Table of Contents
State of the Fleet8

Cutters
Danube Class14
Pulsar Class16
Corvettes
Pegasus Class19
Proxima Class21
Scouts
Saber Class24
Nova/Nova II Class25
Destroyers
Norway Class28
Defiant Class31
Luna Class33
Valiant Class35
Galant Class37
Frigates
Centaur Class40
New Orleans Class42
Lancer Class44
Cruisers
Nebula Class48
Galaxy Class51
Akira Class53
Intrepid Class56
Sovereign Class58
Eagle Class60
Dauntless Class63
Prometheus Class66
Fleet Combatants
Essex Class70
Excalibur Class73
Devonshire Class76
Bibliography79
STATE OF THE FLEET

Overview
The year is 2414. The last 4 decades have been some of the most challenging and violent faced by the Federation. Prolonged conflict with the Dominion (2373-76) followed soon
by a massive Borg Invasion (2381) cost Starfleet dearly. Nearly 3,000 starships and over a million personnel were lost during this period, dealing a devastating blow.
This period of volatility also extended into the astro-political realm. The alliance known as the Typhon Pactrather than providing a quasi-peaceful, counterbalance to the
Federation Alliancewas devoted solely to opposing the UFP and its allies. Underscoring this fact were espionage efforts both industrial and otherwise as well as calculated diplomatic
maneuvering. The protracted conflict that was fought between the two sides from 2385 to 2387 reaffirmed Starfleets position of technological and tactical superiority.
The Hobus Supernova in 2387 served as a galactic reset button, not only for Starfleet, but for its allies and foes as well. With this monumental disaster serving to cool the astropolitical scene greatly, Starfleets priorities shifted back to the traditional defensive/offensive/exploratorybetter known as the multi-missionparadigm.
The advent of Quantum Slipstream Propulsionwhich revolutionized space travel in a manner similar to what Transwarp had promised to do, allowing a starship to traverse great
distances in a fraction of the time it would take a ship with conventional propulsionwas a veritable game changer. Not only did it revolutionize how starships were designed and built,
but how and where they were utilized as well. The Quantum Slipstream era brought with it a new golden age in Federation exploration and expansion spearheaded by two grand
initiatives (Project Full Circle and Mission: Gamma) to explore the Delta and Gamma Quadrants respectively.
With these initiatives well underway and with the aforementioned period of relative astro-political calm taking hold, Starfleet turned its focus inwardmoving swiftly to rebuild its
shattered force with a renewed emphasis on overall strength and power projection.
A gradual shift back towards a more militaristic posture had begun in the aftermath of the Dominion War, but it wasnt until well after the aforementioned invasion by the Borg, that
this shift gained speed and a great deal or urgency. In an overall plan drafted by C-n-C Star Admiral Leonard Akkar and Starfleets Admiralty, specific shortcomings and deficiencies
were addressed along with a multitude of other issues, in a wide-scale overhaul that has since been compared to that put forth by former C-n-C Lars Erik Valdemar a century prior. To
support planned ship production and fleet rejuvenation, the plan attempted to halt further exacerbation of the fleets already painful manpower shortage through a complete top-down
revision of Starfleet Academys entire curriculum and an easing of entrance standards, as well as increased research and development into technologies that would automate certain
ship functions, or otherwise allow crew compliments to be scaled down across the board.
The years immediately following the wars conclusionapproximately 2376-2379saw the end of Galaxy and Nebula class production in favor of the more advanced and
adaptable Sovereign class. Due to the unexpected, but extreme difficulty encountered in trying to adapt Quantum Slipstream Propulsion to Galaxy, selected vesselsalong with their
Nebula class cousins (which shared the same technological underpinnings)gradually began to be phased out of service.
The Sovereign classwhich now became the de facto fleet workhorsesaw its own production curtailed as Starfleet sought to balance out its cruiser lineup with increased
numbers of the smaller, but proven Intrepid class as well as to make room for the larger, more sophisticated Eagle class Command Cruiser.
Initially created to address the lack of dedicated command and control capability, Eagle was soon developed into a dedicated combat cruiser to fill the roles of both carrier and
troop transport. 346 meters longer (1076 m vs 680m) that Sovereign, Eagle was comparably armed and devoid of all scientific/exploratory and many of the same personnel support
facilities found on ships like Sovereign or Galaxy. Combined with a drastic reduction in the standard compliment (being rated for a mere 390 officers + crewmen) and enough room was
freed up throughout both hull sections to create a massive super-hangar for up to a full wing of craft and barracks style accommodations for the pilots/flight crews as well as up to an
entire regiment of marines. Produced on an as-needed basis, Eagle fulfilled the needs of both Starfighter Command and the Marine Corps, while also taking the burden of designing two
all new separate, dedicated classes off of Starfleet and the ASDB. This would prove to be all that Starfleets already strained infrastructure could handlethe bulk of Starfleets existing
assets and resources being divided between Transport Command and the Corps of Engineers who were tasked with ongoing reconstruction and redevelopment efforts.
Beginning in 2385, starship production surgedwith 4 new classes entering production, all conceived in the mold of the Admiraltys plan for the future of Starfleet.
The crown jewel of these was the Excalibur class Battleship (BB 99000). A 2500-meter long leviathan, Excalibur not only projected immense offensive strength and power, but served
as a flying starbaseenvisioned to serve almost exclusively in unexplored areas well outside Federation space as well as in various frontier regions, for durations previously unheard of (in
excess of 10 Earth Years). The class namesake served as a technological testbed from 2381-84; equipped with a still-experimental Quantum Slipstream Drive along with new Type XV
Phaser Emitters. Due to the extreme size, resource & personnel requirements as well as a lengthy construction time (30 months), initial production was limited to just 6 examples with none
currently on order.
Starfleets first mass-produced Battleship and a leviathan in its own right, the 800 meter long Essex class (BB 75000) was intended to supplant the Excelsior (and Galaxy to a lesser
extent) class in the fleet. Equipped not only with a Quantum Slipstream Drive, Essex also carried a punishing armament that included multiple Mark IV Torpedo Launchers, Pulse Phaser
Cannons and the aforementioned Type XV Emitters. In a nod to Galaxy, Essex also featured saucer separation capabilityboth sections remaining warp capable.
Lancer (FH 74900) was the first frigate class introduced by Starfleet since the short-lived New Orleans class in 2364. A smaller compliment to Essex, it was intended to supplant
Miranda as well as hold the line against a shipbuilding strategy that unintentionally played up overall size as a key design attribute. With an impressive cargo capacity and evacuation
limit for its size, a number of exampled gradually found their way into service with Starfleets Transport Command.
Definitely the most unique of the 4 was the Dauntless class Cruiser (CA 101000). The first class aside from Defiant to feature an integrated engine/hull design, Dauntless was intended
to compliment the Nova, Luna and Intrepid classes in their exploratory and scientific roles.
A welcome development that addressed a major fleet shortcoming was the introduction of two new Destroyer classes in 2390 and 2392. An overlooked segment of the fleet
throughout much of the 24th Century, Starfleets inattentiveness in this area was graphically highlighted during the Dominion Warin which the Defiant class, a proverbial secret weapon,
played just a supporting role.
Valiant was based on a prototype design for Defiant. Aggressively designed, it was slightly largerable to embark up to a fully equipped platoon of troopsand featured the
same armament, but stronger, regenerative shielding and thicker armor. It also sidestepped the delay Starfleet faced in refitting existing Defiant class ships with Quantum Slipstream
Propulsion, by incorporating the system in Valiant from the keel up.
Galant on the other hand, was larger than both of the aforementioned classes. A Heavy Destroyer designed to replace the Norway class, it was somewhat smaller (215m vs 365m),
but carried a heavier armament and was just as capableable to carry up to 500 metric tons of cargo (nominally given over to weapons stores) and embark up to a full company (120)
of troops.
A key component of the Admiraltys plan was a clear, cohesive, yet thoroughly modern defense strategy. Based on the concept of spherical defense devised during the 23rd
Century, the strategy called for the deployment of starships in three layers (Inner Screen/Outer Screen/Picket), encompassing all charted Federation territory. Specific deployment
strategies were to be supported by constantly updated, real-time intelligence along with highly complex probability studies allowing Starfleet to maintain the greatest possible flexibility in
its deployment choices. The one kink in that plan was the fact that Starfleet did not have any active classes smaller than a Destroyer (in size and capability) in service. The Danube (and
later, Pulsar as well) class Runabout was available in sufficient numbers for in-system use as a cutter and the Saber class was utilized quite often in the perimeter action role, but they all
failed to address the fact that Starfleet still lacked a modern corvette.
This oversight was rectified in 2395 with the launch of the Pegasus and Proxima classes. Roughly similar in design, Pegasus was the smaller of the pair, at 103 meters in length and
74,909 metric tons displacement, while Proxima was larger165 meters in length and 120,000 metric tons displacement. Both were equipped with Quantum Slipstream drives, advanced
sensor and communications equipment along with powerful weapons for their size (Type VIII Phasers and Quantum Torpedoes).
The Devonshire class, while not the newest (launched beginning in 2391), is projected to be the last ship of its size (600m >) launched by Starfleet until at least 2460at which time
ships of the Galaxy class will start to reach the end of their life cycles. The first Dreadnought launched in a century, Devonshire helped to bridge the size gap somewhat between Essex
and Excalibur, emerging as a much more manageable flagship class.
The Fleet Today
Starfleet as it stands today is in remarkable shape, given the challenges and setbacks faced over the last three decades. Currently maintaining a standing force of 7,650 vessels,
recent construction trends have tended to favor Cruisers and larger Patrol Combatants (Dreadnoughts, Battleships)addressing perceived offensive/defensive deficiencies and
strengthening overall deterrencebut have shifted to become more balanced, including Cutters, Corvettes, Scouts and Destroyers in the overall mix in an effort to achieve a more wellrounded fleet makeup.
Cruisers
Cruisers, held in high regard for their ability to balance size with capability, continue to remain the focal point of Starfleet strategy. A total of 483 vessels of this type, divided
between 8 classes, are currently active; the 20 existing ships of the Nebula class, 28 existing ships of the Galaxy class, 131 ships of the Akira class, 79 ships of the Intrepid class, 84 ships of the
Sovereign class, 8 ships of the Eagle class, 13 ships of the Dauntless class and 120 ships of the Prometheus class. This total is not expected to change significantly until at least 2462, by
which time ships of the Nebula and Galaxy classes will have started to reach the end of their life cycles. The retirement of all 48 ships is projected to be completed by 2480. Production of
the Eagle classa specialized combat cruiser developed for use by Starfleets Marine Corps and Starfighter Commandis expected to remain at as needed status for the foreseeable
future, while full scale production of the exotically-designed Dauntless isnt expected to begin until 2417 at the earliest.
Frigates
Frigate production, never having been a serious priority for Starfleet, is expected to remain constantwith the production rate of the highly adaptable Lancer class remaining at 4
per year. Existing ships of the Centaur (60) and New Orleans (32) classesdespite their age and other engineering related issuesare slated for retirement by 2437 at which time the
Lancer (currently at 116 ships) will have reached sufficient numbers.
Destroyers
Earning the renewed attention of both the Admiralty and the ASDB, Starfleets Destroyer force is expected to remain in the spotlight for the foreseeable future. It currently stands at
790 total examples, divided between the Norway (214), Defiant (282), Luna (108), Valiant (120) and Galant (66) classes. The continued classification of Luna490 meters long, displacing
2,900,000 metric tons and embarking 350 officers and crewmenas a Heavy Destroyer remains contentious, as its size and compliment alone would better fit a Frigate or Cruiser instead.
Starfleet Command has thus far refused to reclassify Lunacurrently a key part of the exploration initiatives covering the Delta (Project Full Circle) and Gamma (Mission: Gamma)
Quadrants. Norway remains the oldest Destroyer class in active service, with production slated to end in 6 months in favor of the Galant class.
Scouts
The second largest component of Starfleets overall force, 2,364 ships of this type are currently active; 1,704 ships of the Saber class; 300 ships of the Nova class and 360 ships of the
Nova II class. Of all Federation Starship classes currently produced, Saber holds the record for maintaining the longest active production runfirst introduced in 2343. Even after being reengineered to incorporate Quantum Slipstream propulsion, the class remains remarkably easy to produce in quantity and holds a durable, reliable reputation, serving primarily in the
scouting/reconnaissance, patrol and perimeter action roles.
Corvettes
Despite the large number of Sabre class ships still active, Starfleet returned to the subject of the Corvettewhich in traditional naval parlance, refers to a small, maneuverable, but
well armed ship used for general patrol and escort duties. Since the retirement of the famed Akyazi class in 2320, no dedicated class existed to perform these dutieswhich themselves,
gained new prominence as Starfleet reevaluated its overall offensive/defensive strategy in the wake of its experiences with both the Dominion and the Borg. In 2395, both the Pegasus
and Proxima classes were introduced. 103 and 165 meters in length respectively, both retained fairly conventional designs and were comprehensively equippedfeaturing Quantum
Slipstream drives, bio-neural computer systems and Quantum Torpedoes. Currently, 380 examples of each are in service, complimented by the Sabre and Nova/Nova II classes in the
patrol and perimeter action roles.
Patrol Combatants
Classifications not used since the late 23rd Centuryhaving become increasingly at odds with the peaceful, multi-mission ethos of Starfleetboth the Dreadnought and Battleship
have made surprising returns. The Essex class Battleship was the first. An 800 meter long behemoth armed to the teeth, bearing an aesthethic resemblance to both the Ambassador and
Galaxy classes and being the first regular production class to incorporate Quantum Slipstream propulsion, the introduction of Essex in 2385 also marked the gradual shift of Starfleet back
towards a predominantly militaristic posture that characterized the late 23rd Century. The Excalibur class was and still remains the largest ship designed and launched by Starfleet to date.
A 2,500 meter long leviathan, it was developed in the late 2370s as a technology testbed and entered limited production in 2384serving as a command ship and mobile starbase of
sorts in extremely remote and explored regions. Currently, just 6 of these ships are in service with no further production planned.
The Devonshire class came about as a response to Excalibura ship that could serve much the same purpose and in the same manner, but was considerably easier and less taxing
to build and deploy. Its classification as a Dreadnought was due moreso to its size and compliment rather than its armament and overall mission profile. The class, introduced in 2392, has
seen much success in service, with 33 examples currently operational.
Compared to Others
When compared to the other spacefaring powers in the galaxy, Starfleet maintains a sizable advantage, if not for the diversity in the types of starships they field, then the
technology they employ. Of its allies, the Klingon Defense Force is the closest technologically speakingand with Starfleet taking the brunt of the losses during the Borg Invasion of 2381
the closest numerically as well, in terms of active vessels fielded. The surprising (some would say, alarming) transformation of the Talarian Navy from a backwater colonial force into a firstrate superpower fielding some of the largest starships in known space has presented a welcome, if somewhat unexpected challenge to traditional Starfleet strength. The Cardassian
Guard, receiving engineering and technological assistance from both Starfleet and the KDF, came in a strong fourth, despite its still-decimated infrastructure and industrial base.
Despite the destruction and devastation wrought in the Romulan Empires home systemthe loss of their homeworld and with it, a blow to their industrial production capacitythe
non-aligned Imperial Navy came away remarkably unscathedsuffering more losses in the aforementioned Borg Invasion as well as the subsequent war between the Typhon Pact and
Federation Alliance. Their current strength remains unknown, however based on historical analysis, it can be reasonably inferred they are within close proximity to both Starfleet and the
KDF.
Both Starfleet and civilian analysts regard the Typhon Pact as being one to two orders of magnitude beneath the Federation Alliance in overall strength. However, among the
states that make up the pact (Tzenkethi Coalition/Breen Confederacy/Gorn Hegemony/Tholian Assembly/Holy Order of the Kinshaya), the Gorn Navy is generally regarded to be the
strongest. Having built their ships large and imposing since the latter half of the 23rd Century, their skillful use of common weaponry (disruptors, torpedoes) in the design of their starships
together with a naval doctrine that favors force projection have made them an opponent to be feared and respecteddespite the limited amount of overall territory they currently
control.
Comparing then, Starfleet to these powers is somewhat misleading as their strength lies not in the development and deployment of traditional naval forcesStarfleets
technological superiority making that a near certainty. With the Breen and Tholians concentrating on diplomatic/political subterfuge and blatant espionage and the rising militancy of
the Andorian Empires dominant political faction, Starfleet must continue ensure that its forces are trained, equipped and deployed in such a way so as to defend against various forms of
asymmetric warfarewhat analysts believe to be the dominant threat for the foreseeable future.
Cutters
Danube
Pulsar
2,450
540
Corvettes
Pegasus
Proxima
380
380
Scouts
Saber
Nova (2368-89)
Nova II (2390-)
1,704
300
360
Destroyers
Norway (DH)
Defiant (DD)
Luna (DH)
Valiant (DD)
Galant (DH)
214
282
108
120
66
Frigates
Centaur (Existing Only)
New Orleans (Existing Only)
Lancer (FH)
60
32
116
Cruisers
Nebula (CA; 2355-79; Existing Only)
Galaxy (CH; 2362-79; Existing Only)
Akira (CB)
Intrepid (CL)
Sovereign (CH)
Eagle (CC)
Dauntless (CA)
Prometheus (CT)
20
28
131
79
84
8
13
120
Patrol Combatants
Essex (BB)
Excalibur (BB)
Devonshire (DN)
16
6
33
Total
7,650
Cutters (CU)
Corvettes (CO)
Scouts (ST)
Destroyers
Destroyers (DD)
Heavy
Destroyers (DH)
Frigates
Frigates (FR)
Heavy Frigates
(FH)
Cruisers
Light Cruisers
(CL)
Cruisers (CA)
Heavy Cruisers
(CH)
Battlecruisers
(CB)
Command
Cruisers (CC)
Attack Cruisers
(CT)
Patrol
Combatants
Dreadnoughts
(DN)
Battleships (BB)
2,990
760
2,364
790
402
388
Total
7,650
208
92
116
483
79
33
112
131
8
120
55
33
22
CUTTERS

DANUBE
CLASS RUNABOUT
The most important small craft development in over a century, the introduction of
the Danube class in 2368 successfully bridged the gap between small craft and starships
providing a warp-capable craft that had all the multi-mission functionality of a starship, but
in a package that was only somewhat larger than the shuttlecraft of the day.
A design study begun by the ASDB in 2363 aimed to produce a small craft capable
of fulfilling a wide range of missions, most notably scientific transport, research and study as
well as intelligence gathering, tactical reconnaissance and special operations support.
Such a craft would need to be warp-capable, with a standard operating range at least
double that of existing personnel shuttles and be capable of sustained independent
operations. To support disaster relief, emergency response, special ops insertion/extraction
and other associated mission scenarios, it was also deemed essential to make the craft
large enough to support a reasonable number of passengers.
The ASDBs design, which was finalized in late 2364, was the first small craft design to
make modularity a priority. Aft of the cockpit, Danube consisted of the propulsion
assembly and could equip any number of large, swappable multi-mission modules that ran
the gamut from additional sleeping bunks and medical accommodations to cargo storage
and specialized scientific equipment. Going further, Danubelike the larger Nebula (CA
60140) classcould be equipped with a number of specialized external modules mounted
dorsally that, depending on configuration, could augment the crafts communication,
sensor or tactical capabilities.
Launched in 2365, the prototype (CU 72000) underwent extensive flight-testing and
conducted strenuous shakedown trials at the Saturn Flight Range. Upon their successful
completion, full class production commenced and the class was well dispersed throughout
the fleet by 2368.
Given Danubes range and capabilities, it was the first choice for commanders of
starships and installations located in various frontier regions, including Deep Space Nine. In
2369 after Starfleet assumed command of the station at the behest of the Bajoran
Provisional Government, the Starship Enterprise (CH 1701-D) offloaded three of these
runaboutsthe Rio Grande (CU 72452), Ganges (CU 72454) and Yangtzee Kiang (CU
72453). Piloted by Commander Benjamin Sisko and Lieutenant Jadzia Dax, the Rio Grande
was the vessel responsible for the discovery of the Bajoran wormhole and the first
Federation vessel to travel to the Gamma Quadrant.
A year later, the Rio Grandeagain, piloted by Commander Siskowas conducting
a planetary survey in the Gamma Quadrant when it became the first Federation vessel to
encounter the Dominion. After Sisko and his party were captured by the JemHadar, the
Mekong (CU 72617) and Orinoco (CU 72905) escorted the Starship Odyssey (CH 71832) on
an emergency rescue mission. Despite the two runabouts having been equipped with
extra stores of Photon Torpedoes, they and the Galaxy class Odyssey were quickly
overwhelmed by a trio of JemHadar Attack Shipsthe Mekong sustaining severe damage
and the Odyssey destroyed. Though the Danube class attrition rate remained rather high
for the next decade, the Rio Grande was the only one of Deep Space Nines original 3
runabouts to survive the tumultuous decade.
By 2380, Danubes production had become so prolific, that it began to find
increasing use in various intra-system roles, including patrol and interdiction. This led
Starfleet Command to change its classification type from runabout (which differed little
from shuttlecraft) to cutter.
In the Borg Invasion of 2381, starships that formed the spearhead of Starfleets
response to the initial invasion had wisely offloaded their Danube class craft in exchange
for more potent starfighters. The runabouts then, participated in predominantly defensive
operationsacting as early warning platforms for planetside colonies and settlements, as

well as helping to evacuate smaller stations and other spaceborne installations. In the
Invasions aftermath, with the Borgs devastation extensive and Starfleets existing resources
stretched thin, Danubes sheer numbers were a great assetrunabouts taking on patrol,
command and control, transport and humanitarian relief duties, among many others, on a
system-by-system basis.
In 2396, the Danubes perceived successorthe Pulsar class entered service and
brought with it significant technological advances. A mere 6 years earlier when the Valiant
(DD 98940) class was launched, the notion of Quantum Slipstream propulsion equipping
anything smaller that a Destroyer was considered ludicrous in the extreme. In 2395 though,
the launch of the Pegasus and Proxima corvette classeshalf the size of Valiantproved
that it could be done and it didnt take long then for the momentum to engulf certain small
craft types.
In a shrewd, but predictable move to boost force strength, Danube class production
was halted for a period while the ASDB completely overhauled the base design
incorporating necessary changes to not only support the new propulsion system, but
advanced sensor and communications equipment as well as more powerful shield
generators and weapon emplacements that equipped Pulsar.
Currently it is estimated that of the 2,450 Danube class runabouts active, a full third
roughly 817have not been upgraded to this new standard. Starfleet Command has set
2417 as the definitive deadline by which time all existing examples are
Class
Classification
Danube
Cutter/Runabout
Service
2368Number Active 2,450
Length
Beam
Height
23m
14m
6m
Mass
159 metric tons
Compliment
1 + 40 passengers
Armament
6 Type IV Phaser Emitters

2 Micro Torpedo Launchers
Defense Systems
Standard Deflector Shield System

total capacity 56,700 TerraJoules
Light Duranium/Trititanium Single Hull
PULSAR
CLASS RUNABOUT
Succeeding the venerable Danube (CU 72000) class in the majority of front-line
applications, the Pulsar class has reaffirmed the relevance and utility of small craft as part
of Starfleets overall deployment doctrineproviding enhanced support and maximum
flexibility across the entire multi-mission spectrum.
helm/operations and mission operations to port and starboard respectively, with a station
for a flight engineer aftwards. All stations are highly configurableone proposed layout
having the forward station configured for the tactical/weapons officer, with the
pilot/navigator occupying the portside aft station.
Conceived in 2394, Pulsar was the product of a development project that aimed to
address Danubes speed limitations and tactical deficiencies and more generally, to
provide a flexible medium-long range support platform that would be better able to match
the capabilities of the new generation of starships then entering service.
Moving aft from the cockpit, was a small antechamber with personnel hatches to
port and starboard and an ingress/egress ramp in the center of the floor. Continuing on
was another compartment of equal size that contained a 2 person transporter platform in
the center, equipment storage along the starboard bulkhead and a head to port. A large
crew compartment was featured nextwith three double-bunk staterooms and a small
survey lab followed up by the standard aft compartment of Danubefeaturing 2 more
double-bunks recessed into the bulkhead along with a conference table and requisite
food replicators. All told, Pulsar was capable of embarking up to 60 passengers in an
emergency compared to the 40 of Danube.
The period immediately following the end of open hostilities with the Typhon Pact
saw Starfleet focusing on two main areas of concern: rebuilding and redevelopment of
infrastructure and overall fleet strength (numerically and tactically). Whereas Danube was
the product of a more idealistic, exploration-focused design ethic that placed an extra
emphasis on technology, Pulsar was decidedly no-nonsense--focusing strictly on combining
technology, tactical strength and multi-mission functionality in a single, efficient end
product.
Aesthetically, Pulsar was streamlined a great deal compared to Danube. From a
dorsal/ventral perspective, the design bore a great deal of similarity to 20th century Earths
Space Transportation System operated by NASA. The main body, 41 meters in length, had
a smooth coke-bottle shape, tapered sharply at the fore end, with the engine nacelles
mounted dorsally at the reartaking a cue from the Raptor class starfighter.
The cockpit design was borrowed directly from the Flyer class shuttlecraft and
featured a two-tiered layout with space for up to four crew members, though as with
Danube, Pulsar was designed to be operated by as few as one crew member. The
pilot/navigator was situated on the lower tier, front and center, surrounded on three sides
by control consoles, while up a narrow ramp to the rear were the remaining three stations
The most notable feature of Pulsar was its completely redesigned drive system. A
common and accepted drawback of small craft new and old was their lack of FTL (fasterthan-light) propulsion, or in included, FTL propulsion that was severely constrained in terms
of acceleration as well as nominal cruising and overall top speeds. This could be attributed
to both technology and engineering issues, however since the introduction of Danube in
2368, considerable strides had been made in both fieldsthanks to Quantum Slipstream
Propulsion.
Intended to propel starships at speeds and across distances previously unimaginable,
the revolutionary new propulsion system required not only engines of a vastly sophisticated
design and that were meticulously engineered, but a computer system more powerful and
complex than anything previously employed. Advancements in engine design and
computer operation began trickling down to the small craft arena after those two
attributes had been refined for the smallest ships yetthe Pegasus and Proxima class
corvettes.
A correspondingly powerful reactor not only provided power to the engines and
other essential systems, by to 6 Type VII Phaser Emitters and 2 forward-firing Micro Torpedo
Launchers. The most powerful weapons of this type that have been installed aboard a
small craft, they put Pulsar on the same level as many of the older starship classes
deployed during the Dominion War, including the Miranda classthe greater total power
output from the advanced reactor core increasing the amount of raw energy able to be
directed through the emitters. Naturally, along with the more powerful weapons was an
improved Deflector Shield System, capable of absorbing an additional 11,200 TerraJoules
over that equipping Danube (67,900 vs 56,700).
The sensor suite also received a great deal of attention. Like with the phaser emitters,
Pulsars sensor arrays compared favorably with those employed aboard some starships
with maximum range and resolution setting far eclipsing those aboard any current or
previous craft in the same size class. Passive scanning, detection and tracking capabilities
were a fairly new development. Devised for and intended to upgrade existing (and new
build) Defiant (DD 74205) and equip new Valiant (DD 74300) class Destroyers, these
functions strengthened Pulsars hand a great deal. In spaceborne operations, the craft
gained a sharper defensive edgereportedly being tested with top-secret interphasic
cloaking technology, though this has never been confirmed. On the ground and in many
planetary atmospheres, Pulsar became an enhanced support tool for ground troop
formations, scientific expeditions, humanitarian missions and many other rapid-response
scenarios.
Entering service in 2396, Pulsar replaced Danube in most front-line, deep-space
applications. Rather than retire the older class, the ASDB stripped Danube down, removed
the old propulsion, computer and sensor systems and replaced them with their newer
counterparts from Pulsar. Given Danubes high-numbers in servicethis effectively
quadrupled Starfleets capabilities in this arena and also freed up larger starships for other
uses.
Class
Classification
Pulsar
Cutter/Runabout
Service
2396Number Active 540
Length
Beam
Height
41m
18m
5m
Mass
189 metric tons
Armament
6 Type VII Phaser Emitters

2 Micro Torpedo Launchers
Compliment
1 + 60 passengers
Defense Systems

Light Duranium/Trititanium Single Hull
CORVETTES
PEGASUS
CLASS CORVETTE
The smallest starship class (not falling into the small craft category) to be launched
in recent memory, the Pegasus class represents a strategic shift by Starfleet towards a more
balanced, flexible deployment plan. Brought about by the Admiraltys long-term
offensive/defensive strategy, it called for the construction of numerous smaller classes
primarily cutters, corvettes and destroyerswhich had long since fallen out of favor in favor
of larger cruisers and other such capital ships that had widely valued multi-mission
capabilities.
The addition of cutters (typified by the Danube and Pulsar runabout classes),
corvettes and additional destroyers would greatly expand Starfleets patrol capabilities as
well as give it a viable perimeter-action forcefreeing up larger frigates & cruisers for other
duties and allow them to be deployed/concentrated further in around key star systems
and towards the Federations core.
A mere 103 meters long and just 5 desk thick, Pegasus supported a compliment of
40with the ability to support a platoon of marines if necessary. Despite its diminutive size,
it packed incredibly advanced technology. Quantum Slipstream Propulsion allowed these
ships to operate in remote regions far from outside support and for durations that would
have been unheard of with previous classes. Sophisticated sensors and electronic warfare
equipment similar to that in the Eagle class Command Cruiser made it an ideal patrol
vessel and battlefield scout, while Type VIII Phasers and Quantum Torpedos gave it the
power to confront and engage ships three and four times its size, making it a valuable front
line asset.
In keeping with the concept of spherical defensewhich had these ships and
others of similar size/profile (cutters, scouts etc) form the initial picket line, Pegasus class
ships were produced primarily at production bases in remote systems on the Federations
outer rim, Grazer, Keldanis Prime and Ramatis being examples (the only production baser
closer in to the Federations core were the Antares III Starship Yards). This both expanded
and helped further decentralize a good portion of the Federations industrial basea
prudent move in the face of the destruction wrought by the Dominion and the Borg.
Production began in 2395 alongside the slightly larger Proxima corvette class and
despite other shipbuilding programs then underway, proceeded at an aggressive 10 ships
per year.
Class
Classification
Pegasus
Corvette
Service
Length
Beam
Height
103m
39m
21m
Decks
Mass
74,909 metric tons
Armament
6 Type VIII Phaser Emitters

2 MK II Torpedo Launchers
Compliment
40 + 60 passengers
Defense Systems

Standard Duranium/Trititanium Double Hull
PROXIMA
CLASS CORVETTE
The larger companion to the Pegasus class, the Proxima class Corvette was intended
to bring depth and increased capability to the perimeter action role, which had grown to
encompass patrol, scouting/reconnaissance and escort duties as well.
Spherical defense may have been simple in conceptthe strategic organization of
fleet units and other elements in defense of Federation territoryhowever it required a
number of different ship types to populate the three layers which encompassed that
territory. Corvettes, along with Cutters, Scouts and Destroyers comprised the outermost
(picket) layer. However, in the last 50 years Starfleet only made token forays into this area
and subsequently, up until roughly 20 years ago ships of these types were in woefully short
supply.
Rather than just design and mass deploy a single Corvette class, Starfleet instead
decided to split the duties between two classes so as to boost operational flexibility should
certain assets not be available or required elsewhere.
The design that became Proxima was originally intended to become the
replacement for the Nova class Scout, but with Starfleet instead choosing to produce the
Nova II variant, Proxima was instead reclassified as a Corvette. As such, the two were
extremely close in size, with Proxima having a slightly smaller beam and 1 less deck.
Fairly conventional in appearance, it was typified by a broad, crescent-shaped
primary hull and a comparatively small navigational deflector dish. 165 meters in length
and displacing 125,000 metric tons, Proxima supported a compliment of 60 officers &
crewmen and, as with Pegasus, featured enough space for up to a full platoon of marines.
Like Pegasus and to a lesser extent, Nova, Proxima was surprisingly well equipped given its
diminutive sizedesigned around a Quantum Slipstream drive system, featuring computer,
sensor and electronic warfare equipment either based off of or lifted directly from larger
classes such as Essex and Eagle and armed much more strategically than vessels of
comparable size/typefeaturing Type IX Phasers and Mark II Torpedo Launchers.
Outside of the aforementioned spherical defense responsibilities, Proxima is expected
to become the principal support platformseparate from any other deployed forcesfor
a number of remote outposts and starbases in the near term.
Class
Classification
Proxima
Corvette
Service
Length
Beam
Height
165m
59m
28m
Decks
Mass
125,900 metric tons
Armament
3 Type IX Phaser Emitters

Compliment
40 + 60 passengers
Defense Systems

SCOUTS
SABER
CLASS SCOUT
The smallest ship to be launched since the Oberth class in 2269, the Saber class Scout
was the product of the same fleetwide modernization effort which also produced the
Norway, Steamrunner and Akira classes, among others.
Tasked with developing a replacement for Oberth (which had ended production just
9 years earlier in 2338), designers came up with their third highly unconventional design
(following Steamrunner, preceding Norway). The primary hull section was roughly
pentagonal in shape, with the forward half of the warp nacelles embedded on either side
of the hull and extending outwards, while the engineering section extended aft from the
primary hull in a roughly V-shaped tail.
Slightly longer than Oberth (190m vs 150m) and with a crew requirement half the size
(40 vs. 80), designers had slightly more room to devote to the scientific suite which was
Sabers main focus. A number of laboratories as well as sophisticated sensors allowed the
class to carry out all of the same mission types, while advances in propulsion technology
contributed to an increased operating range.
Saber was the better armed of the two, mounting 4 Type VII Phaser Emitters (quite
powerful, considering the class diminutive size) and a pair of torpedo launchers.
Entering service in 2343, these ships could usually be found operating within a few
light years distance of a space station or outpost, both on the frontier and closer to the
Federations core.
The class as a whole played a key role in the Dominion War, operating as forward
reconnaissance platforms in advance of larger battle groups and fleets. Production
continues to this day, almost 75 years after the class original introduction, albeit with
modernized components and systems. Four examplesDa Vinci/ST 81623, Khwarizmi,
Musgrave, TPorahave been retained for special use, currently serving with the Starfleet
Corps of Engineers.
Class
Classification
Saber
Scout
Service
2343Number Active 1,704
Length
Beam
Height
190m
250m
41m
Decks
11
Mass
310,000 metric tons
Compliment
40
Armament
4 Type VII Phaser Emitters

2 Standard Torpedo Launchers
Defense Systems

Standard Duranium Single Hull
NOVA/NOVA II
CLASS SCOUT
Starfleets shipbuilding emphasis in the 24th century was centered around a multimission philosophy that dictated larger and larger designs to both incorporate and better
make use of technological advances which began appearing at a breakneck pace.
Dedicated classes, whether peaceful in nature or not, were further de-emphasized as time
went on, despite the introduction of the Saber class Scout in 2343 and the Akira class
Battlecruiser in 2363.
Despite this fact, there was still a clear need for ship classes with a narrow mission
focus as newer, larger designs took longer to build, were more resource intensive and
required more manpower to operate. One area that demonstrated this need was that
occupied by the Oberth class Scout.
Commissioned over a nearly 70 year period from 2269 to 2338, these ships filled
varying roles ranging from scouting & reconnaissance to short-range mapping and
planetary surveys. By the mid 24th century however, the Federations expansion made the
speed, range and capability limitations of the Oberth all too clear. The Saber class was
intended to partially supplant the Oberth, but couldnt accommodate many of the
advanced sensors and science facilities ideal for such a shipeither because of its size or
because of power considerations. The Cheyenne class, developed around the same time,
was much larger and featured a more powerful reactor core, however, notorious and
persistent problems plagued its warp drive and quad-nacelle arrangement.
Starfleet and the ASDB remained in something of a quandary until the late 2360s.
Mission requirements for the Defiant class had been altered to the point where the original,
pathfinder design was considered to be totally unusable. The ASDB did determine
however, that with the included reactor core, propulsion systems and some moderate
modifications, the design would be ideal for a science vessel.
Codenamed Nova, design modifications began in 2367 and included the removal of
the two forward torpedo launchers and the replacement of the phaser emitters and
deflector shield system with less powerful units to facilitate the installation of more powerful
sensor arrays and various science labs. Additionally, engineers replaced the isolinear
computer system with a bio-neural system. Originally conceived for the Intrepid class
which was under development, the system was still experimental, but promised an
exponential increase in processing power as well as energy efficiencyideal for a design
which was now basically a large mobile sensor platform.
The prototype Nova (STX 72380) was launched 8 months later and the class itself was
certified for full fleet production in 2368. In service, Nova class ships proved themselves
extremely worthy successors to their Oberth class forebearers and soon became a
common site throughout the Federationusually operating from Space Stations or
Outposts on missions ranging between 6 and 24 months in duration.
In 2370, the Equinox (ST 72381) vanished on a mapping mission near the Badlands. It
was later discovered to have been transported to the Delta Quadrant and was discovered
thre in 2376 by the Starship Voyager (CL 74656) which had been transported there itself a
year after the Equinox. Unfortunately, the ship was destroyed by an alien species in
retaliation for the actions of the Equinox crew which resulted in the deaths of many
members of that species.
Throughout the Dominion War and the protracted conflict with the Typhon Pact,
Nova class ships performed admirably in scouting and reconnaissance-related roles. In
2378, along with ships of the larger Luna class, they played key roles in Mission Gamma
Starfleets initiative to explore the Gamma Quadrant.
In 2381, Nova was one of a number of ship classes selected to participate in Starfleets parallel initiative to explore the Delta Quadrant, Project Full Circle. However, the stillexperimental state of Starfleets Quantum Slipstream Propulsion technology necessitated further R&D work that stretched on until late 2384. The Federations return to a state of war in
2385 and stretching to 2387 further delayed the deployment of this technology (without which, Full Circle could not occur). Production of the class was halted in late 2386 so retrofitting
of existing ships could take place and the Nova class design could be modified in-kind to accommodate this new technology. Production was resumed in early 2388, with Cygnus (ST
73617), Revere (ST 73595) and Columbia (ST 73621) joining other Starfleet assets already in the Delta Quadrant.
Late in that same year, Starfleet Command compiled a list of changes and improvements gathered from in-field performance appraisals that would utilize technology not initially
available. The changes and improvements requested were so extensive that rather than compile them into a complex refit program, the ASDB designated vessels built to this upgraded
standard as members of the new Nova II sub-class. Externally, Nova II retained the same design, but was somewhat larger221 meters in length and displacing 170,000 metric tons vs
165m and 127,000mT for Nova.
Beginning production in 2389, Nova II featured vastly upgraded sensor systemsincorporating upgrades and improvements intended for the Luna classlarger and more
sophisticated laboratory facilities and technological upgrades intended to keep Starfleets premier scout class on par with comparable explorers, the aforementioned Luna class most
notably.
Class
Classification
Nova/Nova II
Scout
Mass
Service
2368-89 (Nova); 2390- (Nova II)
Number Active 300 (Nova); 360 (Nova II)
Length
Beam
Height
165m (Nova); 221m (Nova II)

Decks
8 (Nova); 11 (Nova II)
127,000 metric tons

(Nova)
Armament
170,000 metric tons

(Nova II)
Compliment
Nova
11 Type VIII Phaser Emitters
Nova II
80 (Nova); 107 (Nova II)

Defense Systems

total capacity 688,500 TerraJoules (Nova)
922,172 Terra Joules (Nova II)
DESTROYERS
NORWAY
CLASS HEAVY DESTROYER
Part of the same fleet-wide modernization project that gave rise to the Akira (CB
62497), Saber (ST 61940) and Steamrunner (CL 52130) classesand that was also noted for
its highly unconventional designsthe Norway class broke with the century-old, singlenacelle destroyer design tradition and revolutionized the very concept of what a destroyer
was and could be, its legacy going on to have a heavy influence on the later Luna (DH
80101) class.
The proliferation of fleet picketsperimeter action ships, light cruisers, corvettes and
clippersin the years following the introduction of the Saladin class (DD 500) in 2224,
caused Starfleet to gradually let its deployment doctrine and construction programs loose
their meaning and direction. Larger cruisers and fleet combatants were deployed farthest
out on extended duration exploratory and defense missions, frigates and other midsized
vessels carried out patrol and intelligence gathering operations in frontier and other
borderspace regions, while smaller vesselssuch as destroyerswere built often as an
afterthought, used in low-priority or supporting roles. As the years went by, destroyer types
became more numerous and varied and they slowly evolved into highly specialized
vessels, used not only in supporting roles, but also on exploratory missions and more often
than not, they formed the first line of defense in many regions as well.
With the dawn of the 24th century however, the role of the modern destroyer
became deemphasized in favor of larger frigates and cruisers built to a flexible multimission standard. The primary class in service at this time was Defender (DD 22012)a
single-nacelle design built in the Saladin tradition, using Ambassador class components.
Intended as a singular replacement for a number of classes built during the Linear Warp
era, Defender was produced in great numbers and proved both more popular and more
capable in service than the Freedom (DD 68700) classso much so, that production was
canceled after just 4 years (2356-60). Defender though had both age and a general lack
of flexibility counting against it by 2360 however, proving Starfleet could no longer ignore
the fact that a replacement was sorely needed.
With the Norway class, the ASDB maintained a single hull design, but instead of a
standard saucer, the Norways hull was roughly triangular in shape with smooth, rounded
corners. At the fore end, centrally located and embedded within a recessed housing was
the main deflector dish. The bridge module was similarly embedded on the dorsal side of
the hull, providing enhanced protection and contributing to a lower overall sensor profile.
Surrounding it on three sides was a specially designed, reinforced hull section that served as
a mounting point for the warp nacelles, which themselves were attached on support
pylons that extended aft to some length, from the rest of the ship.
Externally, the design eschewed any sense of aesthetics in terms of strict
functionalitythough Norway was able to maintain extremely favorable warp field
dynamics as well as enhanced agility, a destroyer hallmark to be sure. Internally however,
was where designers and engineers concentrated the bulk of their efforts.
With a stated compliment of 190 officers and crew, a 500 person emergency
evacuation requirement and the overall design being just 11 decks thick, the ASDB had
their work cut out for them. Crew accommodations were surprisingly good, atypical for a
destroyer, though support facilities were limited. With space remaining at a premium,
designers opted to install two large cargo bays instead of a larger number of smaller bays.
On a typical mission, a varied load of weapons stores, spare parts and other consumables
occupied one of the bays while the other was used for either the transport of cargo, or for
emergency medical use.
The rest of the internal volume was occupied by science and medical facilities.
Unusual for a ship of this type, Norway followed in the steps of the earlier Exeter (CB 2200)
class and featured a limited, but quite robust scientific capability typified by three highly
adaptable laboratories and an advanced (for the day) astrometrics baywhich had
value tactically, as well as scientifically.
and employing a viable defense. In 2367, despite being combat proven, no Norway class
ships were diverted to Wolf 359 to face the invading Borg cubeStarfleet instead electing
to deploy larger ships including the Ambassador class USS Yamaguchi (CH 26510) and the
Nebula class USS Endeavor (CA 71805).
While these multi-mission capabilities did receive a good deal of attention, Norway
also excelled as a fleet combatant. Her armament comprised 6 Type IX Phaser Emitters
and 2 forward mounted MK I Torpedo Launchers, with a standard deflector shield system
providing protection. When combined with her aforementioned speed and agility, she
more than surpassed the Admiraltys expectations for a next-generation destroyer.
With the ultimate failure of the New Orleans (FR 57290) classand its removal from
front line service by 2368Norway gained an additional measure of importance. Still
primarily operating with the 9th (2nd & 5th Squadrons) and 12th (3rd Squadron) fleets along
the Cardassian DMZ in 2373, they were witness to the Cardassian slaughter of the Maquis in
August and were central to a massive rescue operation in October when the Cardassian
Guardbacked by the JemHadarembarked on their Final Solution for the Maquis,
exterminating what was left of the paramilitary group, leaving just 400,000 survivors.
Entering service in 2363, Norway gained instant acclaim from crews and
commanders alike for its vast improvement in accommodation standards (when
compared to the older Defender (DD 22012) and Miranda (FH 1830) classes) as well as its
capabilities vis--vis various threat force vesselsnamely the VMelak class of the Imperial
Romulan Navy and the Galor class of the Cardassian Guard.
Despite the Romulans self-imposed isolation following the Tomed Incident of 2311,
the destruction of the Starship Enterprise (CH 1701-C) by several of the former at Narendra
III in 2345 marked the beginning of a period of uncharacteristic adventurism along the
Neutral Zone. During the Nostveg wargames of 2365 that took place near Khitomer, KDF
and Starfleet forces (including the 12th Fleets 3rd Destroyer Squadron) were shadowed by a
Romulan squadron operating out of the fleet base at Glasko. Unbeknownst to the
Romulans, the entire area was being monitored by Starbase 234. Upon detecting the
Romulan ships in the Neutral Zone, a covert message was sent to the USS Defiance (DH
64927) who subsequently transferred the data to the IKV Lukara, lead ship of the KDFs 11th
Strike Group. Breaching the Neutral Zone from two separate directions, the Romulans
attempted to retreat back into their own space, but were caught in a modified pincer
maneuver and quickly destroyed.
The Cardassians on the other hand did not bother to waste effort disguising their
activities. Hostilities between the Federation and the Union remained white-hot right up to
the establishment of a ceasefire in 2366. In 2365, a mere 7 months following the Nostveg
incident with the Romulans, a supply convoy departing the Federation colony world of
Ronara Prime was attacked and destroyed by a Cardassian battle group. The incident,
recorded by the nearby Argus Array, prompted the massing of the 9th Fleet at Starbase 129.
The 2nd and 5th Destroyer squadrons were detached and sent to the area of the Hugora
Nebula, where the USS Denmark (DH 64908) and USS Olympia (DH 64911) discovered that
the Cardassians had established a base on a small asteroid inside the nebula from which
covert reconnaissance and other activities were coordinated.
While surveying the area, the Cardassians emerged and executed a lightning strike
destroying the Olympia and severely damaging Denmark before 7th fleet arrived,
destroying the asteroid base and either destroying or driving off the bulk of the battle
group.
Subsequent to Starfleets first contact with the Borg in 2365 (in system J-25 by the
Starship Enterprise (CH 1701-D)), a great deal of Starfleets emphasis shifted to developing
They played a key role in the subsequent war between the Federation Alliance and
Dominionfaring much better than older classes such as Miranda (FH 1830) and Excelsior
(CH 2000). With speed and maneuverability being just two of Norways strong points, these
destroyers often found themselves leading cavalry raids and performing hit-and-run strikes
against various targets alongside ships of the Defiant (DD 74205) class. Along with the fleet
as a whole, the Norway class suffered heavy losses in late 2375the Canberra (DH 64914)
and Iowa (DH 64912) lost with all hands at the Second Battle of ChinToka while the
Defiance (DH 64927), North Carolina (DH 64910) and Warspite (DH 64913) were destroyed
when Starbase 451 was overrun.
As part of Starfleets overall defensive/offensive buildup following the war, the
Norway class received tactical (Type X Phasers, MK II Torpedo Launchers) upgrades in 2380
along with computer and propulsion (to support Quantum Slipstream) upgrades in 2386.
Despite expanded production of the Defiant (DD 74205) class beginning in 2378 and the
introduction of the Valiant (DD 98940) and Galant (DH 92410) classes in 2390 and 2392
respectively, Norway class production continuedofficials citing the high number of elderly
Miranda class ships that needed to be replaced.
With the proliferation of Valiant and Galant plus other frigate (Lancer/FH 74900) and
cruiser (Intrepid/CL 74600; Dauntless/CA 101000) classes since then, production of Norway is
slated to end in the next 6 months, with the most recent examples produced expected to
be retired by 2497 at the latest.
Norways legacy however, will continue to live on with the Luna (DH 80100) class.
Introduced in 2379, Luna was intended to moderate the growing militarism within the fleet.
Originally intended as a light troop transport/shuttlecarrier, the success of Norway in various
scientific roleseven given its suite of onboard facilities and systemsconvinced Starfleet
Command of the value a ship with these capabilities would have. Indeed, thanks to the
pioneering work of Norway, Luna currently stands at the forefront of Starfleets scientific
and exploratory endeavors as one of the most advanced vessels of its type currently
fielded.
Class
Classification
Norway
Heavy Destroyer
Service
Length
Beam
Height
Decks
355m
220m
51m
12
Mass
604,958 metric tons
Compliment
185; 480 evac. limit
Armament
2363-2380
2 MK I Torpedo Launchers
23806 Type X Phaser Emitters
Defense Systems

Standard Duranium/Tritianium Single Hull
DEFIANT
CLASS DESTROYER
One of several design proposals developed to defend against the Borg in the period
between initial contact (2365) and the Battle at Sector 001 (2373), the Defiant class
concept called for a small, compact vessel that was comprehensively armed and capable
of extreme endurance in all conceivable mission scenarios. A secondary objective for the
project was to develop, implement and test a full spectrum of systems that could be
implemented in the Sovereign class project that was in an earlier stage of development.
What resulted was a ship that was compact, yet completely unorthodox in design,
devoted solely to combat and packing a lethal amount of firepower that was unrivaled by
any starship launched by Starfleet up to that point.
were the first on any Starfleet vessel able to fire Quantum Torpedoszero-point energy
weapons that produce a much more violent, destructive reaction compared to standard
Photons.
The Defiant was also the first class to feature ablative armoran expendable hull
layer capable of dissipating incoming weapons fireas well as an experimental deflector
shield system that placed shield modulation frequency under the control of the ships main
computer. The computer would continuously evaluate incoming weapons fire and alter
modulation frequencies to provide the optimum defense.
Angular and somewhat boxy in design, Defiant class ships are 3 decks thick (4, if the
bridge level is included). Whereas traditional designs featured the Warp Nacelles on
support pylons that were swept outward to varying degrees, on the Defiant, the engines
themselves were installed in housing that protruded outwards on either side of the hull
improving warp field dynamics a great deal.
The prototype vessel Defiant (DDX 74205) was assigned to Commander Benjamin
Sisko in 2370. Sisko, a veteran of the Battle at Wolf 359, was also the first Starfleet officer to
make contact with the Dominion. The results of that disastrous first contact (primarily the
loss of the USS Odyssey/CH 71832) demonstrated to Starfleet the potential value this Borg
Buster held and Sisko was subsequently ordered to take the Defiant on a search to
contact the highly reclusive Founders (the leaders of the Dominion).
The interior is extremely spartan, similar to Klingon designs in this respect. The crew is
housed in bunk-style accommodations, with only the Captain and First Officer receiving
their own quartersquarters that are cramped and furnished with only the bare essentials
compared to those onboard the Galaxy class. A communal mess hall, medical bay,
transporter room, engineering compartment and a small shuttlebay occupy the rest of the
interior volume.
That first mission was equally disastrous, with the Defiant being overpowered and
boarded in short order. Intense testing following this mission resulted in both the deflector
shield and structural integrity systems being redesigned. Full-scale production commenced
soon after the prototype was declared fit for duty and the class gradually began spreading
throughout the fleet.
Befitting the class combat-oriented (Borg Busting), the armament is extremely

impressive. 4 Pulse Phaser Cannonsweapons which fire highly concentrated bursts of
directed energywere installed along with 4 MK IV Torpedo Launchers. These launchers
In 2372, the Defiant departed Deep Space Nine and hurriedly rendezvoused with a
Federation battle group sent to stop a Borg Cube near the Typhon star system. The
resulting battle (Battle of Sector 001) saw many of the ships destroyed and the Defiant
heavily damaged herself. The Breen later destroyed the tough little ship in 2375 at the
Second Battle of ChinToka.
In 2374, the Horizon (DD 75668) and Moscow (DD 75655) joined the USS Spector (CB
63898) in retaking the USS Prometheus (CTX 59650) after it had been hijacked by agents of
the Romulan TalShiar.
The Defiants small size, minimal crew requirements and outstanding performance in
the field have led to a continued production run, even with the advent of the closely
related Valiant (DD 98940) class. Starfleets emphasis on fleet diversity & resilience ensures
that these vessels will be a common sight throughout the space lanes for many years to
come.
Class
Classification
Defiant
Destroyer
Service
Length
Beam
Height
Decks
171m
134m
30m
4
Mass
355,000 metric tons
Compliment
50
Armament
1 Type X Phaser Emitter

4 Pulse Phaser Cannons
4 MK IV Torpedo Launchers
Defense Systems

total capacity 2,376,000 TerraJoules
Heavy Duranium/Tritianium Single Hull plus 20cm Ablative Armor
LUNA
A contradiction in terms, not only in form, but also in function, the Luna class has
nevertheless gone on to join other classes such as Nova II, Intrepid and Dauntless to form
the backbone of Starfleets exploratory arm.
Concieved in late 2369, following the discovery of the Bajoran Wormhole, Luna was
intended expressly to carry out scientific research and exploratory missions in the Gamma
Quadrant. The eminently peaceful nature of the ship and the development project
however, made it one of the first projects halted by Starfleet Command following the
disastrous first encounter with the Dominion and JemHadar in 2371.
Designed by Dr. Xin Ra-Havreii at the Utopia Planitia Shipyards, Luna was unlike any
starship previously conceived. The design was based loosely on that of the Gettysburg
classa heavy destroyer design which never made it past the preliminary stagebut much
larger, at 450 meters in length, only slightly smaller than the Akira class. The reason for the
increase in size was the unprecedented 32 science labs driving Lunas development. In
essence, Luna was to science, what Olympic was to medicinea highly sophisticated,
specialized vessel with but a singular focus. Extremely adaptable and featuring
sophisticated environmental control systems, vessels so equipped could undertake studies
and perform specialized missions once thought impossible for all but the largest starships
and starbases.
Supporting the science capability was an extremely sophisticated and complex
sensor system. Based on the system in use aboard the Eagle class Command Cruiser,
engineers extensively modified the system, more than quadrupling the bandwith and in
turn, using that to help greatly enhance the systems transpectral capabilitiesa great
asset when studying various nebulae, gaseous and gravitational anomalies and other
volatile subspace phenomena.
With these sophisticated systems and facilities in place, there was precious little
power or interior volume left over to devote to high power phaser banks, extra shield
generators or hot-rodded engines. Therefore, Luna was initially equipped with equivalent
systems from the smaller Intrepid and older Ambassador class. Development was halted
however, before the systems outfitting could be evaluated and further refined.
Following the wars conclusion in 2376, a general trend towards a more robust
defensive/offensive capability took hold throughout the fleet. With Luna, this involved
completely overhauling the power systemsinstalling a more powerful reactor core
capable of greater power output as well as redundant high capacity power transfers
between the core, EPS network and various shipboard systems. While this did indeed take a
great deal of stress off of Lunas power generation and distribution network, it provided only
a modest increase in the amount of raw power available for use by other shipboard
systems.
The initial, Block I, configuration saw Luna equipped with Type IX Phasers, MK II
Torpedo Launchers, a Standard Deflector Shield System and a standard warp drive.
Completely ignoring its size, Starfleet took these capabilities into account along with its
intended mission profile and classified Luna as a Heavy Destroyerplacing it under even
the smaller, more powerful Intrepid class. Of the initial 12-ship production orderproduced
between 2377-81all were produced to this configuration.
In late 2387, with Quantum Slipstream Propulsion beginning to spread throughout the
fleet, engineers at the ASDB finalized the Block II configuration, which is the standard to
which all Luna class vessels are currently built, or operate. The configuration includes a
larger, more powerful reactor core and bleeding-edge computer systems to support the
new propulsion system, more powerful fusion reactors, type X phasers, MK III torpedo
launchers and regenerative shielding.
Despite current astro-political conditions, the high expectations that Starfleet and the Federation Council have placed on the current exploratory initiatives ensure that production
will remain constant for the foreseeable future.
Class
Classification
Luna
Heavy Destroyer
Service
Length
Beam
Height
Decks
450m
307m
84m
21
Mass
2,962,823 metric tons
Compliment
350
Armament
Block I (2377-87)
Defense Systems
Block II (2387-)
4 MK III Torpedo Launchers
total capacity 1,819,881 TerraJoules (Block I)
Regenerative Deflector Shield System
total capacity 1,853,564 TerraJoules (Block II)
Standard Duranium/Tritianium Double Hull
VALIANT
CLASS DESTROYER
One of Starfleets newer Destroyers, Valiant would appear to be little more than a
highly evolved upgrade of the original Defiant class design. On the contrary though, so
profound was Defiants impact once it entered active service that it prompted a
fundamental shift in the way Starfleet thought of these small starship types.
The gradual decline in prominence of Destroyers, Corvettes and other vessels in this
general size class had its roots in the late 23rd Century. The Saladin (DD 500) class
established a successful design blueprint that was gradually refined and expanded through
the decades resulting in a number of successful and very capable classes entering serving
with the fleet. As time went forward however, emphasis shifted towards more capable
frigates and then larger, multi-mission cruiser types.
To the fleets credit, the Saladins basic design lived on in the Defender (DD 22000)
and Freedom (DD 68700) classes of the mid 24th Century. These ships however were
generally considered to be inadequatelittle thought having been given to the
application of technology together with design and mission profileand as such, were not
the key players that many were expecting them to be.
Fast forward to 2365. Development of the Defiant class was initiated in response to
the Federations first encounter with the Borg at J-25. Developed chiefly as an
offensive/first-strike weapon for use against the Borg, the prototype was still months away
from completion when the Borg made their first incursion in 2367. Once emerging from the
dockyards in early 2368 and then finally entering fleet production in 2369, she proved to be
the proverbial answer to Starfleets prayers. Defiant was blindingly fast and surprisingly well
armedhaving the maneuverability of a strike fighter and packing the armor and firepower
of a dreadnought.
The class performance during the Borg Incursion of 2373 and then the Dominion War
further validated its utility and cemented it as an essential part of the fleetopening the
door for other starships of similar size and design.
The initial concept of a second modern Destroyer class was conceived in 2382
subsequent to Starfleets issuing of the Perimeter Defense Directive and the rise in activity by
Orion and Nausicaan pirates. However, Starfleet had much more pressing needs
especially given the extremely weakened state it found itself in in the aftermath of the
Borgs final incursion just a year earlier.
This concept didnt re-emerge until 2387when Starfleet shipbuilding began to
expand dramatically. Lessons learned during the protracted conflict with the Typhon Pact
(2385-87), the emergence of Quantum Slipstream Propulsion as a viable technology and
Starfleets recently announced exploratory initiatives for both the Delta and Gamma
Quadrants all influenced the development of Valiant.
When it came to the design of this new Destroyer however, the ASDB already had the
majority of their work doneValiant was originally one of the proposals submitted and
taken under consideration midway through Defiants development process. The design
itself remained basically the same, with refinements made to give it a more aggressive
appearance.
The biggest hurdle to overcome was technological integration into the design.
Valiant was the smallest vessel thus far slated to be fitted with a Quantum Slipstream Drive.
Installing the reactor core and engines was fairly routine, however, modifying the Defiants
computer system to work with the drive was extremely complex and time-intensive,
amounting to what was essentially a total redesign.
Once completed in late 2388, extensive simulations and actual flight testing of the
prototype were undertaken at the Saturn Flight Range to evaluate the drive systems
performance and enduranceengineers hoping to keep Valiant from becoming
overpowered to the point of dysfunction as Defiant was upon her launch.
From there, development gained speed. The weapon systems incorporated into the
design of Valiant were similar to those incorporated into Defiant (4 Pulse Phaser Cannons, 1
Type X Phaser Emitter and 4 MK IV Torpedo Launchers), though due to the vast increase in
power afforded by the new reactor core, these weapons were reengineered to operate at
much higher power levels, thus giving them more raw damage potential.
Class
Classification
Providing protection is a Regenerative Deflector Shield System (as opposed to the

older, Auto-Modulating system aboard Defiant) and an astonishing 35cm of high-density
ablative hull armor (compared to Defiants 20cm).
Length
Beam
Height
Decks
187m
192m
39m
6
Being slightly larger (187m long/6 decks) than Defiant (171m long/4 decks), the
Valiant class supports an enlarged compliment of 60 officers + crewmen, with room for up
to an entire platoon (60) of troops.
Mass
362,769 metric tons
Compliment
60
Entering full fleet production in 2390, Valiant class ships were deployed to fleets and
bases along the Federations outer rim and other frontier regions. The reemergence of the
Kazon and their harassment of Starfleet forces deployed in the Delta Quadrant led Starfleet
Command to consider the class for duty there, but ultimately went on to choose the
Gallant class for that task instead.
The class was instead chosen for deployment to the Gamma Quadrant as part of
Starfleets Mission Gamma. Though the decision to deploy what was essentially a
dedicated warship to the Dominions native quadrant ignited controversy, Starfleet was
quick to point out that the Dominion had allowed Starfleets exploratory and scientific
efforts to resume unfettered since the end the war in 2376.
Valiant
Destroyer
Service
Armament

1 Type X Phaser Emitter
Defense Systems

Heavy Duranium/Tritianium Single Hull plus 35cm High Density Armor
GALANT
Part of the new generation of starship designs which made its debut with the Exeter
& Lancer classes in 2385, the Galant class was born out of several needs:
-To provide a Heavy Destroyer, larger than the Defiant and Valiant classes, to
compliment ships-of-the-line which continued growing in size
-To maintain parity with the Klingon Defense Forces and the Imperial Romulan Navy
-To incorporate advanced technologies developed and employed on the Excalibur
and Essex classes.
When crafting the design, size was the key factor in play for the ASDB. Obviously, the
Galant was going to be larger than the Defiant/Valiant, however, what designers didnt
want to do was make the ship too big. To keep that in check, the dimensions of the
Miranda class were set in stone as their extreme upper limit.
Aside from size, most of the pioneering work on interior layouts and systems
integration aboard modern destroyers had been pioneered with the Defiant and further
refined by the Valiant classes.
The final design, emerging in 2390, consisted of a dagger shaped hull sweeping out to
port and starboard, mounted on the ends of which were the warp nacelles. Extruding in
from the nacelles and back towards the ship were large pods that provided a direct
power feed to the Pulse Phaser Cannons housed within. Helping to provide structural
support to the nacelles and boosting the Galants overall structural integrity were two
large, reinforced pylonsreminiscent of the Mirandas rollbarthat extended in from each

nacelle and attached to either side of the raised bridge module. Mounted ventrally on
those pylons were two pods--(1 port/starboard)--which contained 2 of the ships 5 Torpedo
Launchers (both forward facing). 2 Aft Launchers were placed underneath the hangar
bay, while the last launcher was forward facing, mounted on the hulls ventral surface
Completing the armament are 9 Type XII Phaser Emittersmaking Galant the most powerful
ship of its size when full fleet production began in 2392.
Not only was armament a primary focus, but maneuverability as well. Defiant set the
benchmark standard for all modern Destroyers and ships in her size class. Able to
outmaneuver JemHadar Attack Ships and keep up with Breen Frigates at the very least, this
initially caused problems for the Galants designers. However, the smooth, tapered design
of the hull along with the design and placement of both the warp and impulse engines
aided greatly in overall warp field efficiency and when combined with internal tweaks,
resulted in the ship being vastly more maneuverable than a Defiant at warp and on par at
impulseremarkable, given her larger size and increased capabilities.
Quantum Slipstream Propulsionthe impetus behind Starfleets rapid modernization
during this periodwas included by default, though engineers had encountered a
moderate degree of difficulty in adapting a drive system developed for larger capital ships,
to a comparatively miniscule Destroyer (even after having incorporated it into the smaller
Valiant class).
Despite its size and advanced capabilities, Galant class ships maintained a standard
compliment of just 60 officers and crew. The extra interior space was given over to
weapons stores and supplies and could also accommodate up to an entire company (120)
of Marinesthough in cramped conditions.
A nominal small craft loadout for a Galant class ship included 1 Pulsar class Runabout
and 2 Type 9 Shuttlecraft. However under certain circumstances, ships could be refit to
accommodate up to a full flight (4) of fighters.
A number of these ships, eventually adding up to a full squadron, were assigned to
Project Full Circle in 2395. The Kazon, a nomadic, warrior race which the USS Voyager (CL
74656) had sporadic contact with during its first 3 years in the Delta Quadrant, had
gradually been stepping up their harassment of the Starfleet expeditionary force since its
arrival a decade earlierculminating in a bloody assault on forces assigned to the
construction of the Federations first Starbase in the quadrant. As hostilities continue to
escalate, its expected that more Galant class ships will call the Delta Quadrant home.
Class
Classification
Galant
Heavy Destroyer
Service
Length
Beam
Height
Decks
215m
168m
37m
9
Mass
446,345 metric tons
Compliment
60
Armament
9 Type XII Phaser Emitters

Defense Systems

FRIGATES
CENTAUR
CLASS FRIGATE
Starfleets replacement for the Okinawa class and a compliment to the large number
of Miranda and Kearsarge II class ships in service, the Centaur was fielded over a 17 year
period from 2325 to approximately 2352 and still serves in a limited capacity today.
Starfleets shipbuilding doctrine during these early years of the 24th century was
centered chiefly around larger cruisers such as Renaissance (CA 9778), Ambassador (CH
10521) and Korolev (CH 41050). Unconventional designs of smaller size (Sabre, Steamrunner,
Norway) which began to enter service saw widely varying degrees of success while various
technological and engineering problems made wide-scale deployment of other designs
(Freedom, Cheyenne) difficult.
Centaur however, had none of the quirks, nor any of the problems of the
aforementioned classes, designers and engineers striving for simplicity and functionality.
Based on the Excelsior (CH 2000) class, the Centaurs design was made of up three parts:
the primary hull (saucer), a basic warp nacelle assembly, using Excelsiors FTWA-1 warp
nacelles and the weapons pod. The weapons pod, taken from the Miranda class and
featuring 4 standard torpedo launchers, was mounted on the underside of the saucer and
actually served as the mounting point for the nacelle pylons as well. The saucer itself was
also heavily modified to contain the necessary engineering and support facilities.
A strong armament, comparable to Miranda, combined with outstanding
maneuverability and a relatively high nominal cruise speed for the time (Warp 7), gave the
class a tremendous value proposition and would go on to directly contribute to the high
production run.
Centaur class ships were utilized heavily during the Federation-Cardassian War,
outgunning and outmaneuvering Hideki class corvettes while being able to successfully
engage and defeat larger Galor class destroyers one-on-one. This, despite the relatively
poor standard of shipboard accommodations, helped the class gain a reliable, rugged
reputation.
Alongside her larger Excelsior class progenitors, the Centaurs received regular
upgrades and refits well into the early 2370s.
During the Dominion War, these ships once again played a pivotal roleacting as
fleet pickets alongside smaller classes like Mirandaand paid a heavy price. Not only were
they faced the Cardassians once more, but also the Dominionwhose attack ships, though
only slightly more maneuverable, outgunned their Starfleet counterparts by a significant
margin.
Surviving vessels were initially slated to be retired en masse beginning in 2378, but due
to their relatively high numbers, were retained until a replacement for the New Orleans (FF
57290) class could be developed. That replacementthe Lancer (FH 74980) class Heavy
Frigateentered service in 2385 and currently sits at 116 examples. Due to the production
targets specified by Starfleet Command, it is currently estimated that surviving Centaur class
ships wont be retired until 2437 at the earliest.
Class
Classification
Centaur
Frigate
Service
Length
Beam
Height
Decks
210m
127m
33m
8
Mass
479,527 metric tons
Compliment
175
Armament
9 Type VIII Phaser Banks

Defense Systems

Standard Duranium Single Hull
NEW ORLEANS
CLASS FRIGATE
The 5th and final design produced based on the Galaxy (CH 70637) classthe others
being the Nebula (CA 60147), Cheyenne (CL 71610), Freedom (DD 68710) and Challenger
(CL 57530)the New Orleans joined these ranks to serve as a capable frigate-type
counterpart, attempting to blend the idyllic multi-mission design ethos with a measure of
militarism that had once been a stable of Federation starship design.
trials of the prototype (FFX 57290), propulsion, computer and sensor performance scores
were markedly higher than either Norway or Defender, thanks to incorporated technology
borrowed from Galaxy and Nebula. These scores and other information collected led to
full fleet production beginning in 2364.
The early 2360s saw Starfleet move away from a long-held tradition of using its ships
predominantly for offensive power projection. Of course, they still served that purpose, but
it was largely marginalizedthe pendulum swinging the other way and starships becoming
complex, highly specialized tools of scientific discovery and exploration. This was true even
as the Federations war against the Cardassian Union became more destructive and
bitterculminating in the infamous scorched earth campaign carried out by
Commodore Edward Sherman.
Initital in field performance was promising. The Rutledge (FF 57295) served with the
12th Fleet along the Cardassian Border in the period immediately leading up to the
establishment of the Federation-Cardassian Treaty (2366) and was the first starship to
respond to the distress call sent by the colony on Setlik IIIengaging Cardassian forces of
Jagul Hanno. The New Orleans (FF 57290) and Savannah (FF 57293) participated in
Starfleets subsequent reprisalpart of the task force assembled around the carriers Ark
Royal (CV 2202), Yamato (CV 2205) and Northampton (CV 2209) that destroyed a
Cardassian space station and a number of supply depots before enforcing a blockade of
the Beloti star system.
The introduction of the Norway (DH 64900) class in 2363 would seem to satisfy the
need for which New Orleans was developed though355 meters in length and armed with
6 Type IX Phaser Emitters and a pair of MK I Torpedo Launchers. Indeed, with Norway and
her highly capable brethren (Akira, Steamrunner, Saber) in service, many questioned the
need for and wisdom of constructing New Orleans and her related classes. In the end, as is
often the case, it came down to simple politics, with New Orleans backers championing
the promise that flexibility and interoperability with her larger progenitors would bring.
Designed fairly conventionally, New Orleans bore a slight resemblance to the Nebula
class, with a broad saucer appearing to connect directly to the sleek, ovoid shaped
secondary hull. Unlike Nebula though and going along with Galaxy, her warp nacelles
extended out and uplining up roughly with the dorsal phaser emitter. Like Norway, New
Orleans was equipped with 6 Type IX Emitters and 3 MK I Torpedo Launcherstheir bolt
on, modular nature being a nod to the earlier Defender class Destroyer. In shakedown
In 2367, the Kyushu (FF 65491) was diverted from its patrol route along the Romulan
Neutral Zone to the Wolf system, part of the hastily assembled task force formed by Admiral
John Patrick Hanson to meet an invading Borg Cube. Along with the USS Gage, USS John
C. Stennis and Hansons command, the USS Melbourne, the Kyushu was destroyed before
the arrival of the squadron led by the USS Saratoga.
In the aftermath of this disastrous battle, production of the class slowedwith
resources and yard space devoted to several Borg Busting designs, while at the same
time, the ASDB undertook a study examining the offensive/defensive capabilities of the
Galaxy class and its offshoots.
The ultimate failure of the Galaxy class to stop the Borg along with the loss of the
Nebula class Melbourne, the severe damage dealt to the Endeavor and the destruction of
the Kyushu dealt an irrecoverable blow to the related shipbuilding programs. By 2372, the
loss of the USS Enterprise (CH 1701-D) had all but sealed the fate of these once promising
classes. Late in that year, production of New Orleans, Challenger, Cheyenne and Freedom
were halted, with many, if not all of the vessels produced removed from service. Starfleet
instead chose to refit a number of older classes (including Apollo, Kearsarge II, Okinawa,
Korolev and Ambassador) and expand production of Norway to augment the new Defiant
and upcoming Sovereign classes.
On the eve of the Dominion War, 60 of these frigates were still in service. A further
blow to the class reputation, they were reclassified as second-line units used strictly in
defensive roles. A selected few, including the New Orleans herself, were stripped down
and hot roddedrefitted with more powerful reactors, phaser banks and deflector
shields, while also outfitted with stores of Quantum and Tri-Cobalt torpedoes. Of those 60
ships, 28 were lost over the course of the war.
Today, the 32 surviving examples are still in service. Along with a number of Centaur
class ships, the New Orleans class in expected to remain in service until 2437, by which time
Starfleet expects production of the Lancer class to reach specified production levels.
Class
Classification
New Orleans
Frigate
Service
Length
Beam
Height
Decks
350m
290m
83m
20
Mass
900,000 metric tons
Compliment
190
Armament

Defense Systems

Standard Duranium/Trititanium Single Hull
LANCER
CLASS HEAVY FRIGATE
A smaller companion to the larger Essex class Battleship, the Lancer class Heavy
Frigate was designed to incorporate the same technological advancements, engineering
techniques and construction methods so as to help modernize and strengthen Starfleet.
In the wake of Starfleets pyrrhic victory against the Dominion and its nearannihilation at the hands of the Borg, it was understandable that Starfleet began to bulk
up, especially in the cruiser bracket on up. However, the fleet was lacking at the smaller
end of the spectrumhaving comparatively few modern Destroyer & Frigate classes in
service.
The Miranda class, a tough, reliable design that had served Starfleet for over a
century, had suffered a high attrition rate throughout the Dominion War and was ill suited
to serve in its role of protecting larger ships of the line, when it was handily outdated in
terms of the technology it employed. The most damning factor of allthe one that caused
surviving ships of the class to be retired en masse at the wars conclusionwere the
presence of stress related hull fractures, a symptom of age that could not be remedied
and pretty much required re-construction of the whole vessel.
The fleets most common frigate type after Miranda was Centauran Excelsior
based design that was comparatively armed to Miranda and had 300 examples in service.
Unfortunately, many of those examples were later lost defending against the Borg. That left
a small handful of Centaurs along with a number of Okinawa and New Orleans class ships.
Okinawa was Starfleets hastily developed, Enterprise-based solution to the notorious
delays of the late 23rd Century Perimeter Action Ship program. Removed from front line
service in 2318 and formally retired in 2350, 200 surviving ships of the class were reactivated
during the Dominion War, of which 82 were lost.
The New Orleans class on the other hand, was an attempt to field a frigate using the
same technology and construction methods as in the larger Galaxy and Nebula classes.
Slightly smaller than the older Okinawa (350m vs 366m), New Orleans did not see much
wartime service, being relegated to second-line status, ships of the class being used in the
convoy escort and system defense roles.
The resulting situationa mishmash of older classes dating from the mid 23rd to early
24th century together with a misfit class now approaching middle agewas extremely
disconcerting to many throughout Starfleet Command. Many of those officials saw
promise in the new Essex class Development Project and pressed for the ASDB to develop a
smaller frigate-type companion.
Almost from the start, Lancer was conceived as a 24th Century Miranda sharing the
same mission profile and being strikingly similar in designthe ASDB remaining none to shy
about where they drew their inspiration.
Lancers design was centered on a heavily reinforced duranium/trititanium single
hull. Whereas the Mirandas single-hull saucer design was comparatively little changed
from the larger Enterprise, Lancers was a completely unique design when compared to
Essexsharing only the same detachable bridge module design and captains yacht.
Elongated, it arcs up in a gentle curve before gradually turning angular back past
the bridge module at the aft end. Viewed from the fore end, Lancer takes on a somewhat
bulbous appearance, highlighted by the main deflector dishhoused in a semi-circular
indention along the centerline. Mounted dorsally, is a weapons rollbar. Rollbars had fallen
out of favor as a design feature in favor of mission adaptable pod systems (like that
designed for the Nebula), but with the mission profile of Lancer being comparatively
limited, multi-mission adaptability in this sense, isnt much of a concern. It holds a torpedo
pod in the center, with 2 Mark IV launchers1 fore and 1 aft. Flanking that, are 2 Pulse
Phaser Cannons1 each port and starboard. This gives Lancer a heavy strike capability
comparable to Essex and boosts each ships survivabilityallowing a ship to act
independently as well as part of a squadron, task force or fleet.
Type XII Phaser Emitters comprised the primary armament13 in all. Engineers
debated about arming Lancer with the new Type XV emitters set for inclusion on Essex, but
settled on Type XIIsperfectly capable of dealing with all conceivable threats the new
frigate class could be expected to come across. The worry with the newer weapons was
that their adoption on other new build classes would spark a dangerous arms race among
the major galactic powers (and thus, play into the hands of the Federation Councils small,
but vocal pacifist bloc).
Regenerative Deflector Shield Systems however, had begun to transition to more
mature, energy efficient defense platformsthe latest of which took advantage of the
extremely powerful computer systems being introduced and incorporated standard AutoModulating capability. This feature, first employed with the shield system of the Sovereign
class and later backfitted to the Defiant class, slaved control of a vessels shield modulation
frequencies to the main computerwhich analyzed incoming weapons fire as well as
other threatsto provide an optimum level of defense and protection.
This, along with 35cm of high-density ablative armor plating was installed however,
without any afterthought or debate.
While combat was a large part of the life of many a frigate, Lancer was also
designed with other multi-mission attributes that made it useful in a variety of scenarios. It
was equipped with a basic scientific suite (comprising sophisticated sensor arrays and
laboratories),that while functional, was not as full-featured as that on larger ships or
dedicated science vessels.
Particularly impressive was its cargo capacity. The lack of extensive science &
medical facilities and the accompanying officers & crew that usually went along with them
freed up a great deal of internal volumeso much so that the 5 cargo bays have a total
storage volume equal to that of a Deneva class Freighter.
Even more impressive was Lancers emergency evacuation limit of 6000 people.
These two attributes, together with the revolutionary Quantum Slipstream Propulsion
technology have made the class a favored one among Starfleet Transport Command as
well as the Federation Department of Colonial Administrationutilizing the vessels to
transport both cargo and people to various locations along the Federation frontier, both
alone and as part of larger flotillas.
Lancer also holds a distinction among Destroyer & Frigate classes of having a diverse
small craft loadout2 Type 9 Shuttlecraft, 2 Type 12 Cargo Shuttles (1 of which is a M
variant) and a single Pulsar class Runnabout along with a mixed flight of fighters2
Avenger and 2 Archangel class craft.
Along with Essex (BB 75000), Lancer (FH 74900) was also completed in 2385, pressed
into wartime service along with her sister ships Lancaster, Truxtun and Majesticall assigned
to separate fleets and used to great effect against the Breen particularly.
At present, 116 Lancer class ships are in service. 6 still remain under the control of
Transport Commandassisting in ongoing redevelopment and rebuilding efforts with the
rest split between assignments in the Alpha/Beta, Delta and Gamma Quadrants.
Class
Classification
Lancer
Heavy Frigate
Service
Length
Beam
Height
Decks
468m
227m
77m
19
Mass
Compliment
505
Armament

Defense Systems

CRUISERS
NEBULA
CLASS CRUISER
Often overshadowed by its larger, more prestigious Galaxy class cousin, the Nebula
class nonetheless occupied an important niche in the fleet structure during the latter half of
the 24th centurycarrying out patrol, interdiction, transport and escort missions usually
assigned to older classes such as Excelsior and Miranda while also being able to conduct
the same kind of long-term exploratory and scientific missions that became a hallmark of
Galaxys service.
been explored with the Abbe class Heavy Destroyer in 2273, but failed to gain widespread
traction in service. With the lack of major technological hurdles, the ASDB developed 4
major podsan advanced sensor, SWACS pod, an enhanced weapons pod, a cargo
transport pod and an emergency field hospital pod. Any one of these pods could be
swapped out in as little as 30 minutes at a drydock or starbase and made Nebula an
extremely flexible tactical tool, allowing Starfleet to do more with less.
Throughout the early 24th century, technological advancement proceeded at a

tremendous rate. Starfleets ability to incorporate/integrate these advances also improved
a great deal. However, the concept of operational flexibility was still lost on many and
proved to be one of the prominent design and engineering challenges of this era. Simply
put, design & engineering practices couldnt keep up with rapidly evolving mission
requirements that placed a burden on ships to perform equally well in an ever-expanding
range of roles.
The design was highly simplified, featuring the new standard saucer attached
directly to the secondary hull. The nacelle pylons, instead of retaining their normal spot at
the aft end of the hull, were moved forward and attached roughly between the two hull
sections, with the nacelles themselves angled downwards. The secondary hull itself was
extended at the aft end just slightly, providing space for a large, reinforced support pylon
that extended upwards. This pylon, which towered above the saucer, served as the
mounting point for the various mission-specific pods.
Size wasnt necessarily the solution to the problem either. Propulsion and computer
technology had evolved to the point where starships could travel longer and faster and do
more. All that was required now was an extra degree of creative innovation. For
inspiration, the ASDB referred back to the Exeter (CB 2200) class that featured a number of
science labs that were highly adaptable, featuring sophisticated and flexible
environmental controls and able to be used with any number of scientific disciplines with
next to no modifications needednearly unheard of in the late 23rd century, especially on
a battlecruiser. Nebula took this approach and expanded upon it, extending this
adaptability/flexibility to the medical facilities, incorporating a surprisingly sophisticated
suite given the relatively small size of the design that was taking shape.
442 meters in length, displacing just over 3.3 million metric tons and rated for a
compliment of 750, Nebula was larger than the Korolev, but smaller than the Ambassador
Heavy Cruiser classes. Basic armament centered on 5 Type X Phaser Emitters and 2 MK III
Torpedo Launchers. In addition to more sophisticated targeting sensors, with a longer
range and enhanced multi-target tracking/targeting abilities, the enhanced weapons pod
added an additional 2 self-contained torpedo launchers.
Perhaps the most notable (and novel) approach to the issue of operational flexibility,
was the ASDBs plan for a multi-mission/mission-specific pod system. The concept had first
Though full fleet production began in 2355 while the Federation-Cardassian war was
getting increasingly more violent, Nebula class ships saw relatively little actionStarfleet
instead choosing to deploy the Renaissance, Korolev and Ambassador as its principal
capital ship classes.
In 2367, a year after the signing of the armistice between the Federation and
Cardassians, the Phoenix (CA 65420) commenced on an unsanctioned campaign against
Cardassian forces in a number of sectors along the recently established Demilitarized Zone,
destroying a small space station and at least 2 starships. Though these actions were
unsanctioned and highly irregular, further investigation by the Starship Enterprise revealed
that the commander of the Phoenix had been acting on suspicions that the Cardassians
were covertly rearmingin clear violation of the terms of the armisticeand that these
suspicions were correct.
Later that same year, the Melbourne (CA 62043), Bellerophon (CA 62048) and
Endeavour (CA 71805) were part of the task force hastily assembled to defend against the
Borg at Wolf 359. The Melbourne was to be the second ship to bear the name, replacing
her Excelsior class forbearer that was originally launched in 2289. The urgency of the Borg
threat necessitated her early launch and both vessels ended up facing the Borg cube and
were lost with all hands. The Endeavour on the other hand survived the battle. Sustaining
severe damage, she was towed 4 light years back to Earth and spent the next two months
laid up at Starfleets Yokohama Naval Yards.
Near the years end, after repairs were completed, the Endeavour and the
Sutherland (CA 72015) were part of a Starfleet task force sent to the Klingon-Romulan
border, forming a rudimentary tachyon detection net to thwart Romulan interference in the
Klingon Civil War. The Romulans trained their ECCM equipment on the Sutherland,
temporarily disrupting the tachyon net in a radius of 10 million kilometers around the ship.
Further investigation by the crew and the launch of several modified low-yield photon
torpedoes revealed a cloaked Romulan flotilla attempting to cross the border and deliver
supplies to forces of the Duras family, whom the Romulans had been secretly aiding all
along.
In 2371, the Farragut (CA 60597) led a rescue mission to Veridian III to recover
survivors from the Enterprise after that vessel had been destroyed in combat against a
rogue Klingon D-11/BRel class Bird of Prey. During the short-lived conflict between the
Federation and Klingon Empire in 2373, the Farragut was ambushed and destroyed near
Ajilon Prime.
The class was utilized quite heavily during the Dominion War, comprising numerous
cruiser wings during fleet engagements along with other classes such as Akira, Steamrunner
and Excelsior.
In 2374, the Bonchune (CA 70915) was detached from fleet operations to intercept
and retake the USS Prometheus (CTX 59650), which had been hijacked by agents of the
TalShiar during shakedown trials. Upon intercepting the Prometheus however, the TalShiar
utilized the attack cruisers experimental multi-vector assault mode to quickly overpower
and disable the Bonchune.
The Lexington (CA 61832) accrued the most impressive combat record during the
war, being present for every major fleet engagement. Her most impressive performance
came during the Battle of Tyra in 2374. At this point, the Lexington was part of the 7th Fleet
which numbered just 112 ships. Arriving at the Tyra system, the fleets objective was to blunt
the Dominions advance and prevent further loss of territory. After arriving on station and
deploying into a defensive bulwark, they engaged a numerically superior Dominion force
of 248 ships. Hoping to turn the battle into one of attrition, they initially concentrated their
assault on the capital ships assembleddestroying the flagship USS North Star in the initial
clash. The Lexington held the line and led a charge, forcing her way through multiple
waves of JemHadar attack ships and severely damaging the forces Keldon class flagship.
Ultimately however, the battle was a thorough routLexington being one of only fourteen
Federation Starships to survive the disastrous encounter.
In 2379, production of both Nebula and Galaxy ended, with Nebulas direct
replacement not coming until 2385 in the form of the Dauntless (CA 101000) class. In the
aftermath of the Borg Invasion of 2381 however, only 20 examples remainedall of which
are expected to be removed from service by 2480.
Class
Classification
Nebula
Cruiser
Service
Length
Beam
Height
Decks
442m
318m
130m
32
Mass
Compliment
750
Armament

2 MK III Torpedo Launchers (4 when equipped with Enhanced Weapons
Pod)
Defense Systems

GALAXY
CLASS HEAVY CRUISER
The largest and most complex starship class designed and constructed until the
introduction of the Excalibur (BB 99000) class, the introduction of the Galaxy class
represented a watershed moment in modern starship design for the Federation.
Galaxy was the culmination of a record 14 year design and development period
incorporating every known technological and engineering advance up to that point.
Guided by a robust and detailed multi-mission design brief, the class was designed to
supplant the older Renaissance, Ambassador and Rigel classes as Starfleets premier deep
space explorers.
Given the class complexity, a small minority of critics derided it, declaring it overthough and over-engineered. These arguments were not without merit; the scientific,
medical, computer and engineering systems rivaled those on the largest, most expansive
starbases. As with the Ambassador, Galaxy set a new benchmark in shipboard luxury,
featuring crew appointments and recreational facilities that bested those found aboard
the lushest star liners.
Befitting its status as the fleets largest and most capable starship class, Galaxy was
comprehensively armed, featuring 12 Type X Phaser Emittersthe most powerful then in
serviceand 3 MK III Torpedo Launchers. The class combat capability was also enhanced
due to the fact that routine saucer separation was made a part of the design. Though the
saucer featured just 2 of the 12 total Phaser Emitters and 1 of the 3 torpedo launchers
(which was only able to be used when the saucer was separated), the relative power of
these weapons presented an extra challenge for potential enemies.
Saucer separation also boosted the survivability for those serving on board. In the
event the ship was overwhelmed by enemy forces, or of a catastrophic systems failure, the
entire ships compliment (officers, crew and civilians) could be evacuated aboard the
saucer section.
The problems inherent in such a complex design became apparent beginning in

2365 when the Yamato (CH 71807) fell victim to an ancient Iconian computer virus, causing
scattered shipboard systems failures before infecting the antimatter containment system
which ultimately led to a warp core breach which destroyed the ship.
In 2370, the Odyssey (CH 71832) was overpowered and destroyed by 3 JemHadar
Attack Ships during the disastrous first contact with the Dominion (ironically, the ships
dedication plaque read Its origins and purpose, still a total mystery). Despite running
through the entire spectrum of modulation frequencies, the Odysseys deflector shields
provided no defense against her opponents phased poloron weaponry.
A year later in 2371, the Enterprise (CH 1701-D) was destroyed by a Klingon Bird of
Prey. The second ship bearing the name to be destroyed by such a vessel (the first being
CH 1701 in 2285), the Enterprise suffered critical damage resulting in a warp core breach
after her opponents matched their disruptor and torpedo modulations to that of the
Enterprises deflector shields.
These deficiencies, plus other, more minor ones, led to several design and
engineering changes culminating in the Galaxy II sub-class. The Venture (CH 71854) was
the first ship built to these improved specifications, while existing vessels were refit to Galaxy
II specs beginning in 2372.
Galaxy class ships, including the Venture and Magellan, performed admirably during
the Dominion Warbeing some of the largest capital ships (other than the Sovereign class)
deployed by Starfleetas well as during its aftermath, playing a key role in rebuilding
efforts. Production was formally ended in 2379, in favor of the Sovereign class. Along with
the Nebula class ships still in service, existing ships of the Galaxy class are expected to be
removed from service by 2480.
Class
Classification
Galaxy
Heavy Cruiser
Service
Length
Beam
Height
Decks
641m
470m
145m
42
Mass
Compliment
1,014; 15,000 person

evacuation limit
Armament
12 Type X Phaser Emitters (Galaxy)

14 Type X Phaser Emitters (Galaxy II)
Defense Systems

(Galaxy)
Standard Duranium/Trititanium Double Hull plus 10cm Ablative Armor
(Galaxy II)
AKIRA
CLASS BATTLECRUISER
As the 24th century unfolded, a renewed era of peace and prosperity took hold
throughout the Federation. Starships had gradually morphed into tools of exploration and
scientific discovery rather than strategic symbols of power and force. As such, the
battlecruiser was considered to run counter to the Federations core principles and of
course, none were in service. However, conflict with the Cardassian Union, coupled with
the rapid expansion of Federation territory and concern over the average age of ship
classes then in service prompted calls for a wide-ranging fleet-wide modernization
program. As part of this program, not only were the fleets exploration and scientific
capabilities enhanced and upgraded, but there were calls for a renewed emphasis on
defense as well.
One such offshoot of the program was the Akira class Battlecruiserthe first ship to
receive the classification since the late 2280s.
As originally envisioned, the Akira class was proposed as a through-deck cruiser, or
light carrier. Two large shuttlebays at the fore and aft ends of the saucer were to be linked,
thus providing for rapid launch and recovery operations. However, this came into conflict
with the proposed weapons loadout, which featured a total of 15 Torpedo Launchers. The
number of torpedos able to be carried was thus, severely limited by the presence of the
shuttlebays and accompanying storage and maintenance facilities and with that in mind,
the decision was made to erase the carrier capability from the overall design.
A traditional saucer section dominates Akiras design, with the secondary hull
mounted directly to the saucers ventral surface. The unique catamaran element begins
on the suacers dorsal surface, with two raised hull elements extending aft, connected by a
weapons rollbar in the middle and featuring warp nacelles extending out at the tips.
Tactically, Akira places its emphasis on its heavy weapons capability. The 15
aforementioned torpedo launchers are spread equally across the ship3 mounted above
the primary deflector dish with 1 below, 7 in the rollbar mounted pod and 2 each on the
port and starboard sides, just above the centerline. Completing the weapons loadout are
5 Type X Phaser Emitters.
The Akira was a pure warship in the traditional sense, but its as close as Starfleet
would come until the launch of the Defiant class in 2370. The class was given a
compliment of 500 officers and crew, with an emergency evacuation limit of 4500.
Additionally, up to an entire battalion (600) of marines could be embarked depending on
mission requirements.
From the time they entered service in mid 2363, the Akira and her sister ships led
generally unremarkable operational lives, with most performing routine border patrol and
interdiction missions. With the discovery of the Borg by the USS Enterprise (CH 1701-D) in
2365, the short lived Klingon conflict in 2371 and the advent of hostilities with the Dominion
in 2372, Starfleets renewed defensive emphasis was quite justified.
In 2373, the Borg launched a second assault on Eartha cube proceeding all the
way to Sector 001 where it was met by a task force in Earth orbit. The Akira (CB 62497) and
Thunderchild (CB 63549) both participated in the final battle that destroyed the cubethe
Thunderchild sustaining severe damage and spending the next 8 weeks drydocked for
repairs.
Akiras also featured prominently in the Dominion War with the Rabin (CB 63293) and
Spector (CB 63572) performing admirably during the First and Second Battles in the
Chintoka star system as well as the final battle near Cardassia Prime. They were tough,
reliable ships that were also extremely maneuverable for their size. This maneuverability, combined with their heavy firepower made them favored assets of many fleet
commanders, who liked to concentrate them in squadrons so as to maximize their offensive potential.
During the Borgs Final Invasion in 2381, Akira class vessels proved to be Starfleets most potent weapon. Starfleet Command initially wanted to supply just a handful of vessels with
powerful Transphasic Torpedos, but after the invasion begun, specifications for those weapons were distributed across the fleet. The Borg eventually adapted to these weapons and both
the Spector & Rabin were destroyed as cubes advanced towards Sector 001.
As in the Dominion War, the class played a strong supporting role in the protracted conflict with the Typhon Pact from 2385-87Starfleets tactical & technological superiority
graphically demonstrated by these vessels.
For all its tactical prowess, Akira was also a technological gem-in-the-rough. It was Starfleets oldest starship class that was capable of handling the new Quantum Slipstream
Propulsion system without heavy modifications. The fact the much-heralded Galaxy class was launched just one year earlier, yet couldnt accept the same modifications (without a great
deal of work) sparked a firestorm of controversycentered around various claims and rumors that the exotic propulsion technology was developed chiefly for its offensive potential.
The simmering and ultimately short-lived controversy was the prime reason the initial expeditionary force of Project Full Circle consisted primarily of smaller cruisers and explorers.
The Devore (CB 64088) however, was assigned to support the construction efforts of the Federations first Delta-Quadrant Starbase along with the Destroyers Horizon (DD 75668) and
Moscow (DD 75655). In 2390, with the Starbase nearly complete, a numerically superior Kazon force arrived and engaged the 3 ships without warning or provocation. Though the Kazon
ships employed Plasma Torpedos in their initial attack, the superior maneuverability of the Starfleet vessels combined with the Kazons comparatively weak Deflector Shield technology
allowed them to hold out until the arrival of the Excalibur class Battleship Exeter (BB 99002).
Though the exact number remains classified, additional Akira class ships have since been deployed to the Delta Quadrant in support of the exploratory and scientific initiative. They
also play a key role in the defense of Sector 001, although again, specifics on exactly how remain classified.
Class
Classification
Akira
Battlecruiser
Service
Length
Beam
Height
Decks
464m
317m
87m
21
Mass
Compliment
500; 4500 evac. limit
Armament

Defense Systems

Standard Duranium/Tritianium Double Hull plus 6cm High Density Armor
INTREPID
CLASS LIGHT CRUISER
While the introduction of the Galaxy class in 2362 was hailed by many and
considered to be a watershed moment in Starfleet ship design, the class as a whole has
had a troubled history with various design/engineering flaws as well as offensive/defensive
deficiencies resulting in several extensive changes being made, culminating in the Galaxy
II sub-class that was only in production for 7 years (2372-79) before being ended in favor
of the Sovereign class.
What Starfleet failed to recognize during this period was that their current
shipbuilding policy severely limited the fleets overall flexibility. Larger ships, typified by the
Galaxy/Galaxy II and Sovereign, not only took longer to build, but also required more
resources (not only to build, but to support) and had high crew requirements. This meant
they couldnt be as widely deployed as other classes and the spots to which they were
deployed, required much more scrutiny than had been the case in the past.
The fleet did have a large number of Sabre class ships in service, but their diminutive
size hampered their overall range & capability and a renewed production run really
wouldnt have gone far enough to solve the aforementioned problem. What was
needed was a diverse mix of ships that retained the same basic multi-mission philosophy
as their larger counterparts, yet were vastly smaller and able to utilize the latest
technologies.
The Nova class Scout, which entered service in 2368, was the first ship class to truly
address this issue. A replacement for the long-serving Oberth class, it was extensively
equipped for scientific and general exploratory duties and was well armed for its size.
The Intrepid class though, would prove to be the magic bullet that Starfleet was
looking for, developed over a 3 year period from 2367 to 2370.
Like Nova, it featured extremely sophisticated sensors and extensive scientific
facilities but was also the testbed for several notable technological advances including
bio-neural computer technology (which would eventually supplant all isolinear-based
systems by 2376) and an entirely new warp propulsion system. Advances in
engineering/physics as well as the discovery of new materials led to a more advanced
and energy-efficient warp coil design translating into higher speeds and also eliminating
energy emissions that had been shown to damage the fabric of subspace (advances
that would be adopted fleet-wide by 2373). Intrepid was also the first ship class to
introduce the Emergency Medical Holograma holographic supplement to the ships
medical staff.
Also, like Nova, the Intrepid was quite well armed given its overall sizeequipped
with 13 Type IX Phaser Emitters covering all firing arcs along with 4 MK I Torpedo Launchers
The Intrepid was also (and currently is) the only Federation Starship class capable of
routinely operating within various planetary atmospheres and landing on most solid
planetary surfacesproviding an extra dimension of flexibility in various mission scenarios
(The Intrepid/CL 74600 and Bellerophon/CL 74705 were utilized heavily in the ground
attack role during the liberation of Betazed in 2375 during the Dominion War).
The starship Voyager (CL 74656) was presumed lost with all hands in 2371 while
pursuing a Maquis ship in the Badlands, however it was later revealed to have been
transported to the Delta Quadrant by an alien artifact. She returned safely to Federation space in early 2378 via a Borg Transwarp Hub. Upon her return, Captain Kathryn Janeway
was promoted to Vice Admiral and command was formally transferred to Captain Chakotay in 2379.
Voyager was also responsible for introducing the concept of Quantum Slipstream Propulsion to Starfleet. A revolution in the same sense that Transwarp Drive was in the late 23rd
Century, it would actually see tangible success. Existing ships were refit to accommodate the new propulsion system, while the design and engineering of the class itself was modified to
include the system during the construction process for all new builds.
Voyager was also chosen to spearhead Project Full Circle upon its inception in 2378 while Bellerophon, Armstrong (CL 74672) and Defiance (CL 74691) joined the exploration
initiative not long after, still continuing in that role today.
Class
Classification
Intrepid
Light Cruiser
Service
Length
Beam
Height
Decks
343m
133m
66m
15
Mass
700,000 metric tons
Compliment
140
Armament

Defense Systems

SOVEREIGN
CLASS HEAVY CRUISER
The latest in a long, proud lineage of multimission explorersof which the

Constitution, Ambassador and Galaxy classes also belongthe Sovereign class was
launched in 2372.
Originally, the Sovereign was conceived as a dedicated warshipa variant of the
Ambassador class intended for use against the Klingon Defense Force in the tumultuous
period just prior to the Battle of Narendra III in 2344. As time went on and new threats
presented themselves, so too was the Sovereigns mission profile subtly altered. In the late
2360s, it became yet another part of Starfleets overall anti-Borg strategy. In 2371, the
design and mission profile of Sovereign was altered for the last time.
At that time, much of the technology behind the Sovereign was based on the Galaxy
classa poor performer not only against the Borg, but also the Dominion who had recently
emerged as an equally sinister threat.
Technology developed for and employed on other classes was extensively used
most notably bio-neural computer and Emergency Medical Hologram (EMH) technology
from the Intrepid class along with ablative armor, quantum torpedos and an automodulating deflector shield system from the Defiant. The Warp Propulsion System was
based partially on that of the Intrepida high speed, energy-efficient design which
eliminated damage to subspace, while Phaser technology was upgraded significantlythe
Sovereign becoming the first class to be equipped with the new Type XII emitters.
After the prototype Sovereign (CHX/CH 73811), the Enterprise (CH 1701-E) was the
second ship of the line to be launched, responsible for thwarting a Borg Invasion in 2372 as
well as a planned strike on Earth by the Reman terrorist Shinzon, during the short lived
Romulan coup in 2378. Sovereign class ships saw limited front-line service during the
Dominion War, being utilized only in major engagements. This was despite the fact the class
was comprehensively armedequipped with 16 Type XII Phaser Emitters and 6 MK IV
Torpedo Launchers.
In the wars aftermath, they participated heavily in rebuilding efforts across the
Federation and began to be deployed, along with the Luna and Intrepid classes, on
extended exploratory and scientific missions in the Gamma Quadrant.
In 2381, the Sovereign, Enterprise and Atlas participated heavily during the Borgs final
incursionthe Atlas in particular, suffering severe damage while defending Vulcan.
With the Galaxy II and Nebula classes having ended production in 2379, the
Sovereign and Intrepid classes began to enter service in greater numbers, gradually
becoming fleet mainstays.
The Enterprise herself continued in service, command transferred to Data in 2386 after
his return to duty and the retirement of Jean-Luc Picard a year prior. In 2392, sabotage and
a subsequent attack by elements of the Imperial Guardboth acts coordinated by the
Andorian terrorist group True Heirs of Andorresulted in the starship taking severe
damage, so much so that it could not return to Earth under its own power. Upon its return to
the San Francisco shipyards and a through evaluation by the ASDB, Starfleet Command
ordered the retirement and scrapping of the 20 year old vessel. Its name and legacy would
live on however, hull number 1701-F inserted into the Devonshire class production schedule
at the same starship yards.
Class
Classification
Sovereign
Heavy Cruiser
Service
Length
Beam
Height
Decks
680m
240m
87m
29
Mass
Compliment
700
Armament

Defense Systems
High Capacity Deflector Shield System

Heavy Duranium/Tritianium Double Hull plus 15cm High Density Armor
EAGLE
CLASS COMMAND CRUISER
The Eagle class Command Cruiser was developed in the post-Dominion War era as a
larger compliment to the Sovereign class with the goal of evaluating the effectiveness of
and potential future need for a large cruiser that placed a heavy emphasis on command &
control (C3), carrier and troop transport capabilities.
The Sovereign class rather conspicuous absence from many of the major
engagements of the war robbed Starfleet of a major combat capability boost, placing a
more substantial burden on the less powerful Galaxy, Nebula and Excelsior classes. The
Excelsior class in particular suffered mightily during the war. Developed nearly a century
earlier in the late 2270s, it literally made Starfleets existing fleet of Dreadnoughts obsolete
overnight. However, its agility, armament and defenses were woefully inadequate
compared to the enemy aggressors they faced.
The large-scale movement of troops and equipment along with the coordinated use
of fighters and other small craft on an equally large scale were both things the Federation
and Starfleet had comparatively little experience with. Not since the days of Operation
Vanguard had Starfleet been tasked with and faced the need to move large numbers of
personnel, equipment and small craft and not since the days of the Four Years War (224650) had they faced the need to make these moves with extreme urgency.
It was here that Starfleet faced challenges as well. Despite having distinct, semiautonomous commands devoted to both ground forces (Starfleet Marine Corps SFMC)
and starfighters (Starfleet Starfighter Command SFSFC), these commands didnt currently
operate any starships independent of Starfleet. In particular, Starfighter Command was
particularly indignant at the fact they were relegated to using an Excelsior class derivative
(the Curry class) that fared rather poorly in the volatile climate (the massive Midway class
was sidelined from the conflict, due to concerns about its relatively exotic propulsion system
and other sensitive technologies falling into enemy hands).
Thus, what was needed was not another multi-mission explorer with extra functionality
tacked on as an afterthought, but a ship that was purpose built to fulfill these roles.
Additionally, Starfleet itself showed great interest in developing a dedicated C3
(Command, Control, Communications) platform. Such capability was incorporated to
certain degrees in both the Galaxy and Sovereign classes (and to a lesser extent, the
Nebula and Intrepid classes as well), but was never widely utilized, due to Commands
reluctance to use these ships outside of their intended roles for which they were developed.
Consisting of sophisticated long-range communications equipment along with highly
adaptable sensor arrays, an extremely powerful electronic warfare suite and custom
designed software and computer systems, a ship so equipped would be capable of
exercising complete and absolute control over a battlefield spaceborne or planetside.
With Eagle, the decision was made to address not only the C3 capability, but the
carrier and troop transport issues as well. Any semblance of multi-mission capability was
completely disregarded, making this the first class since Defiant to be designed and
constructed to such a standard. Only the medical department received more than
average attention with facilities included and systems employed that were equal to those
of the Olympic class somewhat unusual for a class with this mission profile.
The design of Eagle, while aesthetically similar to Sovereign, is actually a highly
streamlined version of the original prototype design for the Intrepid class. The primary hull
takes the form of a smoothed-out triangle with now standard elements such as the main
bridge, primary hangar bay and secondary impulse engines featured in familiar locations.
The ship is bereft of any connecting neck section, the primary hull integrated flush with the
secondary hullwhere the warp nacelles are mounted low along the midline.
The most distinct design feature is the scarab/diamond shaped SWACS/torpedo pod. Mounted dorsally, at the rear of the secondary hull, this combined features of multiple pods
developed for the Nebula classincorporating sophisticated, specialized sensor pallets on both its dorsal and ventral surfaces as well as 4 MK III Torpedo Launchers (2 fore, 2 aft).
The addition of two large superhangars at the aft end of the secondary hull gave Eagle the ability to embark up to two full wings of starfighters (144 craft) or a mixed small craft
loadout, depending on mission requirements.
The lack of any scientific or exploratory support facilities whatsoever was a major factor in keeping the compliment low. This in turn helped free up enough internal volume for the
aforementioned hangar bays as well as for barracks-style accommodationsenough to accommodate up to an entire regiment of troops (1,296), making Eagle the only ship class able
to embark formations this large.
In terms of armament, Eagle lagged slightly behind Sovereign, mounting 12 Type XII Phaser Emitters, 3 MK IV and 4 MK III Torpedo Launchers, but was more heavily armored (20cm of
Ablative Armor) and featured a more powerful deflector shield system. When combined with her C3 equipment, she is generally regarded as being more powerful.
First commissioned in 2378, a total of 10 ships were produced; Eagle (CC 94350), Phoenix (CC 94351), Valiant (CC 94352), Merrimac (CC 94353), Bismarck (CC 94354), Atlantis (CC
94355), Montana (CC 94356), Repulse (CC 94357), Olympia (CC 94358) and Eclipse (CC 94359).
During the Borg Invasion of 2381, both Merrimac and Bismarck were lost with all hands at the Azure Nebula as part of a combined force attempting to prevent the Borg from
penetrating further into the Alpha Quadrant.
Phoenix was also used frequently by the Special Operations Group (SOG) of the SFMC and has been rumored to be equipped with a prototype interphasic cloaking device
though this has never been substantiated. Under the command of Admiral Thomas Dodge, the ship saw heavy action during the war between the Federation Alliance and the Typhon
Pact. In 2385, the Phoenix was ambushed and severely damaged by the Breen & Kinshaya at Lambda Boralis while returning from a classified mission.
With the entry of the Essex, Devonshire and Excalibur classes into fleet service, the Eagle class moved to as-needed statusdevoted almost entirely to both the Marine Corps and
Starfighter Command. Resource scarcity and a diminished manpower pool has placed the future of any further examples in doubt, though the class as a whole stands to play a key role
in the future of both commands.
Class
Classification
Eagle
Command Cruiser
Service
2378Number Active 8
Length
Beam
Height
Decks
1026m
362m
131m
33
Mass
Compliment
390
Armament

Defense Systems

Heavy Duranium/Tritianium Double Hull plus 20cm Ablative Armor
DAUNTLESS
CLASS CRUISER
One of the more unique starship designs launched in recent memory, Starfleets
Dauntless class is the second to break away from the traditional design pattern (primary
hull secondary hull warp nacelles) that has dominated Federation starship design since
the early 23rd Century.
Starfleet could ill-afford to support yet another large cruiser class. In the wake of the
devastation wrought by the Borg during their invasion and then the subsequent war with
the Typhon Pact in the early-mid 2380s, the fleets resources were severely depleted and its
infrastructure was bruised & tattered.
The advent of Quantum Slipstream propulsion was a veritable game-changer in

terms of not only starship design, but the entire astro-political realm as well. Providing
Starfleet with more than just a potential first-strike capability, it held the potential to revitalize
scientific exploration, colonization & commerce as well as territorial expansion.
Additionally, the midsize workhorse of the fleetthe oft-maligned and overlooked

Nebula class was not aging as gracefully as many in Starfleet Command wouldve liked.
The primary drawback of such a propulsion system was the raw computing power
needed to perform the enormously advanced computations in near real-time. The
Excalibur class was purposely designed from the start to incorporate the advanced
computer systems needed. The Eagle class proved the easiest of all existing classes to refit
with the new propulsion technology due to sophisticated computer systems already
installed to support its function as a Command Cruiser. The Sovereign and Intrepid classes
also proved similarly easy to refit.
However, classes such as Galaxy and Nebula along with ones that were still older
were much harder and more time consuming to modify. The flipside therefore, of such a
revolutionary leap in technology, was that the bulk of the Starfleet was rendered somewhat
obsolete.
With major exploration initiatives beginning in both the Delta & Gamma Quadrants,
the need for fleetwide modernization was clear.
Along with its larger (and newer) Galaxy class cousin, the Nebula received a host of
upgrades at the outset of the Dominion War designed to maximize its offensive and
defensive capabilities. Its multi-mission pod system also played a vital role in the aftermath
of the Borgs devastating incursion in 2381vessels equipped with the emergency field
hospital unit helping to treat untold scores of patients.
The unexplained disappearance of a number of examples however, including the
Hera and Proxima, the need to overhaul the computer system on every ship of the class
following the destruction of the Galaxy class Yamato (CA 71807) (the two classes
computer systems being virtually identical), along with the Bonchunes (CA 70915) rapid
and embarrassing defeat by the captured Attack Cruiser Prometheus (CT 74913) stirred the
misgivings of many, who questioned the decision to continue to employ and rely on a class
with such notable failures.
The subsequent introduction of the Lancer Frigate class in the mid-late 2370s did
much to relieve these misgivings, but they were designed from a more militaristic
standpoint, with true multi-mission capability treated as an afterthought and were thus not
able to carry out the same range of missions as Nebula.
With the need made clear, the next issue to resolve became one of design. With the
Excalibur class signaling the start of a new era in Federation Starship Design, the ASDB
elected to pursue an experimental path in an effort to establish a new design language
that eschewed the traditional primary-secondary hull/warp nacelle arrangement that had
driven the design of starships since the late 22nd Century.
To that end, Dauntless design encompassed a single hull with tightly integrated
slipstream (warp) and impulse drive engines, much like the Defiant and Valiant classes.
Dauntless though had a much more fluid or organic designroughly diamond shaped
and was much larger than the two Destroyers and even the Nebula495 meters in length
and displacing 3,790,000 metric tons.
As with many more recent starship designs, the class was designed from the ground
up to incorporate a Quantum Slipstream drive. More unique than that though, was that the
design of Dauntless did not include any engine nacelles as we know them. Instead, the
warp coils and other related components were all arranged in a large, semi-circular
outboard hull section which curved gracefully around the aft end of the ship, with
integrated bussard ramscoops at their forward tips.
While highly unconventional in concept, a byproduct of this design feature was vastly
increased interior volume as opposed to modern nacelle designsallowing engineers to
utilize much more powerful driver coils and other associated components while saving
space.
The placement of the impulse enginescomparatively large given the ships overall
sizeat the aft corners helped give Dauntless impressive maneuverability when
compared to other cruisers of comparable size. Additionally, the design of the engines and
their associated control systems as warp drive boosters for a limited duration for truly
impressive acceleration.
The Dauntless, being intended to supplant Nebula as well as compliment the Intrepid
and Nova classes, naturally received a great deal of attention when it came to exploratory
and scientific capabilities. Numerous omni-directional, multi-spectrum sensor arrayswith
range equal to those aboard the Excalibur classfed back into a sophisticated bio-neural
computer system comprised of both primary and secondary cores. A total of 17
laboratories were included, designed to make extensive use of modular equipment and
featuring highly adaptable environmental control systems.
The prowess of Dauntless computer systems wasnt limited to peaceful roles either.
Sophisticated targeting software was developed, allowing the ship to analyze incoming fire
from as well as engage numerous targets. Providing the teeth for which this software was
designed were 11 Type XII Phaser Emitters (7 Dorsal, 4 Ventral) and 4 MK III Torpedo
Launchers. Regenerative Deflector Shields, the new de facto standard previously installed
only on larger capital ships of a more militaristic nature, were included. Befitting the
peaceful nature for which Dauntless was primarily designed, the decision was made to not
include ablative armor.
The prototype Dauntless (CAX 101000) was launched in 2384 and formally
commissioned in 2385. In 2387, Dauntless and Cochrane (CA 101001) were assigned to
support Project Full Circle while Pyotr Velikiy (CA 101002) was assigned to Mission: Gamma.
Data taken and collected from shakedown cruises and in-field performance evaluations
led Starfleet to order a 10-ship production run, starting with Solaris (CA 101003) in 2388 and
ending with Tripoli (CA 101012) in 2397.
General consensus was positive among the officers and crew who praised the ships
versatility and performance in virtually every type of mission scenario encountered
supporting a second, larger production run slated to begin in 2399. However, resource
allocation levels of other shipbuilding projects and the continuing
rebuilding/redevelopment of the Federations infrastructure have so far delayed further
production of the class, which Starfleet estimates will not begin until early 2417.
Class
Classification
Dauntless
Cruiser
Service
Length
Beam
Height
Decks
495m
133m
53m
12
Mass
Compliment
120
Armament

Defense Systems

Standard Duranium/Tritianium Single Hull
PROMETHEUS
CLASS ATTACK CRUISER
The third and last of Starfleets Borg Busting starship designs to be launched following
the encounter between the USS Enterprise-D and a Borg Cube at the J-25 star system, the
Prometheus was a technological tour de force that promised to revolutionize Starfleets
tactical capabilities.
traditional primary hull/secondary hull/warp nacelle arrangement. The primary hull

itself took the form of a slightly tapered arrowhead, connected to a slender, non-descript
secondary hull that featured a hangar bay aft.
Starfleets ill-preparedness both before and following this initial encounter has
become legendary. Given how many of the concepts and starships that were developed
would later go on to play key roles in the Dominion War, it would be nave to suggest the
encounter should have never taken place, or at least taken place when it did.
In its standard, docked configuration, the ship featured a quad-nacelle arrangement

only the second starship class after Constellation (CA 1974) to do so. Using a mix of
specially designed components and those taken from the Sovereign class, Prometheus was
able to attain a nominal cruising speed of Warp 9.9 making her the fastest starship class in
the fleet and representing the absolute apex of conventional warp drive design and
engineering.
The concept Prometheus was designed to exploit was that of starship separation.
Incorporated sparingly and used only as an extreme last-ditch measure, it gained new
importance as Starfleets technological and engineering expertise grew and developed
incorporated into and intended to be a more routine feature onboard the Galaxy class (CH
70637). From a tactical standpoint, what the ASDB endeavored to create, was a starship
that could separate into two or more warp-capable sections and engage either a single
target from multiple vectors, or multiple targets.
Like the Defiant (DD 74205) and unlike Sovereign (CH 73811), Prometheus was
intended from the start to be a dedicated warship, devoid of all facilities one would
normally find on a multi-mission explorer. A notable bonus this provided was a low
personnel support requirementbeing rated for just 175 officers & crew.
Externally, it broke from established Starfleet design aesthetics and was highly
aggressive, even compared to Defiant and older classes such as Exeter and Korolev. 415
meters in length and displacing 2,100,000 metric tons, it did however maintain the
Starship separation to the ASDB soon translated into what engineers dubbed as
multi-vector assault mode (MVAM)fitting, considering the class intended purpose. As
designed, Prometheus was comprised of three battle sections. The upper section did not
make use of any of the 4 included warp nacellesinstead being equipped with 2 vastly
smaller nacelles in an over/under arrangement that were automatically deployed when
the ship was separated. The mid and lower sections however, split the nacelles into pairs of
2.
For its size, Prometheus was extensively armedfeaturing Type XII Phasers, large stores
of Quantum and Photon Torpedoesand well protected, featuring a first-in-the fleet
regenerative deflector shield system backed up by a generous amount of ablative armor.
As opposed to the standard deflector shield systems on most modern vessels, the
regenerative system equipping Prometheus worked by acting as a sponge of sorts
absorbing incoming energy, but then converting that energy and feeding it back into the
shield grid allowing the shields to constantly regenerate. Like Defiant and Sovereign, the
system was auto-modulating as well, the ships computer constantly analyzing incoming
weapons fire and automatically altering shield frequencies to provide optimum protection.
war between the Federation Alliance and the Typhon Pact later that year introducing a
major sense of urgency to the operations.
An equally notable development was the extensive engineering and R&D work into
the areas of computer control and automation. While to a large degree this work was
necessary due to the unique operating principles of the MVAM, the ASDB sought to go
above and beyond by keeping resource & personnel requirements as low as possible.
Thanks to the extensive collaboration between the ASDB and the Daystrom Institute,
Prometheus could theoretically be operated by as few as 4 people, while both docked and
also in multi-vector assault mode. This created a tremendous value proposition that the
Starfleet Admiralty was quite enthusiastic about.
The class characteristics (namely its size), capabilities and excellent in-service
performance record have contributed to an assured production run with the Vanguard,
Sentinel (CT 74928), Andromeda (CT 74931) and Liberator (CT 74930) all slated for
deployment to the Delta Quadrant as part of Project Full Circle within the next 3 months.
The Special Operations Group (SOG) of the Starfleet Marine Corps has also expressed
interest in the class, though they refuse to disclose to what end.
In 2374, shortly before the Romulan Empires entry into the Dominion War as part of
the Federation Alliance, agents of the TalShiar hijacked the prototype (CTX 59650) from the
Antares III Starship Yards, executing the skeleton crew aboard and attempting to take the
vessel back to Romulus. Starfleet swiftly dispatched the USS Bonchune (CA 70915), but the
Nebula class ship stood no chance and was quickly overpowered by Prometheus. The
warship was stopped just short of the Neutral Zone by the starships Spector (CB 63898),
Horizon (DD 75668) and Moscow (DD 75655)which deployed security forces to retake the
vessel, before turning to engage a trio of Romulan warbirds which had arrived to
rendezvous with the TalShiar.
With the prototypes capabilities proven, albeit in a highly unorthodox manner,
production commenced soon after. Upon completion of the second ship, Cerebus (CT
74924) in 2375, Vice Admiral William Ross transferred his flag there from the Bellerophon (CA
74705), the ship serving throughout the rest of the war.
The class finally saw its first taste of combat against the Borg in 2378. Along with 26
other starships, the USS Prometheus was hurriedly dispatched to guard against a Borg
transwarp apature that had materialized a little more than a light year from Earth.
Unbeknownst to the Prometheus and other Starfleet ships, traversing through the apature
was the Starship Voyager (CA 74656). Hot on Voyagers tail as she existed, was a Borg
Sphere that the Prometheus and the rest of the forces engaged and quickly destroyed.
Three years later, the class again got a chance to fight the Borg, this time during their
disastrous final invasion. The Heracles (CT 74919), Overlord (CT 74922), Virginia (CT 74927)
and Hyperion (CT 74916) were part of the Allied fleet on station at the Azure Nebula and
were later lost with all hands when the Borgnumbering 7,461 shipsarrived. The
Prometheus herself was hastily recalled to Earth and was the ship aboard which the
Admiralty recommended UFP President Nanietta Bacco evacuate too (in preparation for a
retreat from Sector 001), though she vocally chose not to heed this advice.
In the aftermath of the invasion, the Prometheus herself remained at Earth while class
production was prioritized. In 2383 both the Prometheus and the Vanguard (CT 74929) were
recalled to the Yokohama Naval Yards and underwent extensive suitability testing,
investigating the possibility of deploying Quantum Slipstream Propulsion class-wide.
With the introduction of the Essex (BB 75000) and Lancer (FH 74900) classes in 2385,
ships of the Prometheus class were recalled and refitted on a gradual basis, the outbreak of
The pioneering work in adapting starship separation capability for tactical uses and
well as being the first class to employ regenerative deflector shields provided a legacy on
which much of Starfleets current defense capability reststhe massive Essex class
Battleship employing saucer separation (with the saucer maintaining full Quantum
Slipstream capabilities) and regenerative deflector shields becoming the new de facto
standard for all starships.
Despite the existence of newer, larger and more powerful starship classessuch as
the Devonshire, the current Starship Enterprise being an examplecurrent UFP President
Liam Bacco is known to be an admirer of the Prometheus class. To that end, Starfleet
Security has modified the USS Chimaera (CT 74921) for use as a presidential transport,
incorporating a number of highly classified changes and improvements and also assuming
the callsign Federation One while Bacco is aboard.
Class
Classification
Prometheus
Attack Cruiser
Service
Length
Beam
Height
Decks
415m
163m
64m
15
Mass
Compliment
175
Armament
(Docked)

Defense Systems

Heavy Duranium/Trititanium Double Hull plus 30cm Ablative
Armor
PATROL COMBATANTS
ESSEX
CLASS BATTLESHIP
Along with the Lancer class, the Essex class was borne partly out of necessitythe
age and capability of many Starfleet ship classes severely hampering the fleets operational
capabilities during the Dominion War and its immediate aftermath as well. Varying factors
such as speed, cargo capacity and survivability as well as the ability to employ the latest
technology in fields such as science, medicine and engineering were all key to the
Federations rebuilding efforts.
Many ship classes, most notably Miranda and Excelsior, were nearing or had just
passed the century mark. Maintaining vessels in service for that length of time was not only
a costly drain on the fleets resources, but extremely dangerous in certain cases as well, as
some age related issues such as hull stress fractures proved extremely difficult or impossible
to remedy.
Not only was Essex expected to be built and perform to an exacting standard, based
on the harsh lessons learned by Starfleet during the Dominion War, but it was also expected
to incorporate bleeding-edge technological innovations from the keel up. Foremost
among these innovations was Quantum Slipstream Propulsion, a radical advancement in
propulsion technology that ushered in a new era of starship design & constructionwhich
some would say was as radical as that ushered in by the advent of Linear Warp Drive.
Essex class Development began in 2382, before the Alpha & Beta Quadrants were
plunged back into war (with the Typhon Pact, from 2385-87), but after most major powers
had been brought to their knees in what was the Borg Collectives final invasion into our
part of the galaxy. Development of the related Lancer class was begun 3 months later
while Starfleets future flagship classExcaliburhad been in development since early
2381.
Aesthetically speaking, designers did not break much, if any new ground with Essex.
It was well known throughout both the military & civilian sectors that Starfleet ship design
was as much an exercise in art as it was a showcase for technological and engineering
innovations. With this project however, technological goals and considerations took sole
priority, making the ASDBs job somewhat easier.
Bearing a striking resemblance to two 24th century iconsthe Ambassador and
Galaxy classesEssex struck a traditional profile, though at 800 meters in length and
weighing in at an estimated 6.5 million metric tons, it had a decisive size advantage over its
two forbearers.
Unlike the Excalibur, whose massive armament was seen as proportional in relation to
its size, the Essex carried a punishing armament for its sizecementing its classification as a
Battleship and becoming a cause for concern throughout the small, but vocal pacifist bloc
on the Federation Council.
Critics were swiftly silencedthe mere existence of the Dominions Battleship and the
fact that Starfleet & the Federation barely escaped almost-certain extermination by the
Borg serving as Starfleet Commands only justification for authorizing its development.
Type XV Phaserswhich currently have the most raw, destructive potential of any
existing directed energy weaponcomprise the primary armament of Essex, with 17
emitters deployed, covering all firing arcs. Capable of directing nearly 200% more energy
against a target compared to the Type XII, while costing just 20% more in terms of power
requirements made this an incredibly potent weaponon par with the Dominions Phased
Poloron weapons in terms of tactical significance.
Phaser Cannonslong consigned to smaller escorts, destroyers and frigates along

with mammoth starbases and space stationswere also includes, the first time such
weapons had been employed on a capital ship of this size. To provide the needed power
while keeping the design and layout of the ships power distribution network as streamlined
as possible, the four cannons were incorporated into the lower portion of the nacelle
pylons, 2 each on either side of the secondary hull. Together with the 4 Type IV Torpedo
Launchers (3 forward, 1 aft), the Essex had the most powerful heavy strike capability of any
ship class short of Excalibur.
located on Deck 10 in the saucer--underscoring the fact that the two sections werent
designed to operate independently for extended periods.
A regenerative deflector shield system rated for a maximum energy capacity of

7,160,062 TerraJoules together with 50cm of thick, high-density ablative armor plating
provided robust, reliable protection during combat and also other hazardous situations.
The main compartment was roughly ovoid in shape and contained a small twoperson transporter bay at the forward end, a large conference room aft and 2 luxuriously
appointed staterooms to port and starboard.
Amazingly enough, the advanced and comprehensive armament of Essex played a

supporting role to the most radical featuresits propulsion and hull separation capabilities.
Fully warp capable (equipped with a conventional warp drive), the yacht was
capable of operating within planetary atmospheres and making planetfall via three large
landing pads (2 forwardport/starboard; 1 aft). An airlock chamber was situated just
forward of the transporter bay with an elevator platform which allowed for personnel
ingress/egress.
Quantum Slipstream Propulsion by itself wasnt as radical as it was complex and

advancedrequiring an extremely powerful and sophisticated computer system, deflector
dish and obviously, engines. Using data and technology being tested and developed for
the Excalibur class Development Project, ASDB engineers were able to develop and
incorporate two separate systems.
The reason for incorporating two independent, fully functional drive systems was a
byproduct of the Essex class crowning achievementroutine hull separation capability,
with each hull section remaining fully warp capable.
The concept of hull separation capability was born in the early 24th century, first
incorporated into the Galaxy class as an emergency measure, a way to evacuate the
ships compliment during critical or catastrophic emergencies.
The tactical dimension of this concept was not fully realized until the Prometheus class
was developed in the early 2370s. That ship, an experimental Attack Cruiser class, was
designed from the start with what the ASDB Multi-Vector Assault Modethe ship being
able to split into 3 sections, each being well-armed and warp capable. With the Essex, the
ASDB aimed to combine the two dimensions into one functional system.
A second warp reactor core was installed in the ventral half of the saucer
occupying space in the central section of decks 12-19 with the accompanying engineering
section occupying the lower 3 decks of that. The saucers dual warp nacelles are
integrated into the ventral hull surface and when activated, extend out and downwards at
a 45-degree angle. While the ship is operating as a single, integrated unit, the saucers
engineering section is unmanned, its warp reactor being controlled entirely from the main
engineering section in the secondary hull.
Along with the redundant propulsion elements present, the saucer also contains its
own deflector dish, computer core, 1 of the 4 total torpedo launchers (with 1 additional
launcher present when the saucer is separated) and 1 of the 2 hangar bays. The one
element not present in both hull sections is the medical facilitiesthe single medical bay
Another design feature borrowed from Galaxy and its Sovereign class successor was
that of the Captains Yacht. A yacht in the true sense of the word, it resembled a slightly
larger, streamlined Danube class runabout. The cockpit was comparatively small for the
craft and was situated in a small, upper level compartment accessible by a small twoperson lift and having room for just 2 people.
Like the Sovereign class yacht, the example included in the Essex class was armed
with a number of phaser emitters (6 Type IV) and protected by a standard deflector shield
system.
Incredibly enough, the innovations didnt stop with the Captains Yacht. The bridge
module was purposely designed to act as a two-deck, self-contained lifeboat that could
maintain full impulse for up to a week. It was designed to operate in this manner only in dire
emergencies, requiring the services of a drydock or starbase for re-integration once it had
been jettisoned.
It also contained a small transporter bay identical to that aboard the Captains Yacht
as well as enough weapons and other emergency stores to last up to 100 people for two
weeks.
Under normal operations, with the module hard-docked, Deck 2 was utilized
exclusively by the senior staff and department heads, with offices, conference room and a
VIP lounge occupying the majority of the deck.
The first ship of the class - Essex (BB 75000) - was completed in 2385. With the
Federation and Starfleet back on a war footing, there was no time for a shakedown cruise,
many of the new systems being tested and fine-tuned while the ship carried out missions as
part of the 2nd Fleet. Only one more ship Royal Sovereign (BB 75001) was completed in
time to see wartime service (in late 2386). Assigned to the 9th fleet, both her and her sister
ship gained fearsome reputationsespecially against the Kinshaya, who were especially
venomous, sending their largest, most heavily armed vessels up against the Federation
Battleships.
There have subsequently been 14 further examples produced, replacing older
cruisers of the Galaxy class.
Class
Classification
Essex
Battleship
Service
Length
Beam
Height
Decks
800m
587m
181m
45
Mass
Compliment
860
Armament
17 Type XV Phaser Emitters

4 Type IV Torpedo Launchers
Defense Systems

EXCALIBUR
CLASS BATTLESHIP
The largest starship class constructed and operated to date by the Federation
Starfleet, Excalibur was the product of 5 years of exhaustive research and development
aimed at producing a definitive flagship class that not only possessed incredible tactical
ability, but could operate as a mobile starbase of sorts--carrying out a full range of
operations in regions far outside Federation territory for durations previously unheard of.
Discussion regarding such a ship began in the period immediately following the
Dominion War. Sporadic encounters during the wars final chapter had been made with
two massive Dominion vesselsa Dreadnought, approximately 1,282 meters in length along
with a Battleship, which was a staggering 4,800 meters in length. Thankfully, only the
Dreadnought had been engaged in combat (by the Academy Training Vessel Valiant/DD
74210), but the mere existence of these war machines was more than enough to prompt
serious discussion on a solution. These discussions were bolsteredat least from a tactical
standpointby the engagement between the Reman warbird Scimitar and the Starship
Enterprise (CH 1701-E) in 2378.
Concrete action was finally taken later that same year, when the ASDB commenced
their design and development project for this new class, codenamed Excalibur.
Designers and engineers were given a free reign to work and took that to heart, crafting a
design that has been universally accepted as one of the most graceful since the Galaxy
class.
2500 meters in length and displacing 12,867,647 metric tons, the design achieved its
sleek aesthetics by forgoing the traditional primary/secondary hull layout presented by
classes such as Constitution, Ambassador and Galaxy for a layout that integrated both hull
sections more directly. Forgoing the more graceful interpretation of this design trait
popularized with the Sovereign classdesigners went for the utilitarian interpretation as
presented by the Korolev class. In this manner, the saucer-shaped primary hull was
built in to the secondary hull section with an elongated connecting dorsal linking the two
and the main bridge/command module centered at the top.
80 decks thick, Excalibur was initially rated for a compliment of 1,125 though due to
extensive automation of many secondary systems, this number was eventually reduced to
880. Excalibur was also the most comprehensively outfitted vessel ever produced, with
extensive scientific and medical facilities that were elaborately designed, equipped with
bleeding-edge technologies and which came incredibly close to outclassing the
capabilities of many starbases. The class also had the capacity to embark an entire
brigade (7,632) of Marines and serve as the launch platform for a fully equipped division
(216) of starfighters.
Befitting its size and importance, the ship was also comprehensively armed. 24 Type
XV Phaser Emittersimmensely powerful weapons first employed aboard the Essex class
blanketed the hull, backed up by 6 Mark IV Torpedo Launchers (3 fore, 3 aft). The entire
hull was sheathed in 75cm of thick, high-density armor plating while the regenerative
deflector shield system was capable of absorbing an incredible 21,091,911 TerraJoules of
energy. This made Excalibur the most powerful starship class by defaultoutclassing not
only every other class developed by Starfleet to that point, but the largest, most prestigious
classes of other major navies as well.
Construction on the prototype (BBX 99000) began in late 2379. Due to security
concerns, construction took place at Starfleets San Francisco Shipyards complexlong
regarded as one of the most secure in Earth orbit. Due to the sheer size and complexity of
the design, construction lasted a record 30 monthsbeing completed just weeks following
the Borgs final invasion.
were assignedseeing combat primarily against Kinshaya and Breen forces, but also
against the Gornwhose starships were better matched vis-a-vis Excalibur, in terms of size.
Quantum Slipstream Propulsionarguably the defining characteristic of Excalibur

had its origins in the Excalibur class development project, but was further refined and first
employed aboard battleships of the smaller Essex class. Similar in principle to transwarp
technology researched by Starfleet in the mid 23rd Century and utilized by the Borg up to
2381, the revolutionary form of propulsion operated by focusing energy through a vessels
main deflector, creating a focused quantum field. This field allowed a vessel to penetrate
the quantum barrier and travel at speeds that vastly exceeded traditional warp drive limits.
To maintain such velocities, the phase variance of the quantum field had to be constantly
adjusted.
On 07 April 2386, the Nautilus led the Twelfth Fleet in the Battle of Deep Space Nine.
The enemy force of Breen/Tholian/Tzenkethi outnumbered the fleet nearly four to onethe
Nautilus size making it a prime target and the presence of previously unknown Breen and
Tholian Battleship classes making Starfleet extremely hard pressed to defend the station.
The Twelfth had sustained heavy losses and the Nautilus herself was beginning to take
heavy damagedespite the massive power of her Type XV Phaserswhen the Cardassian
3rd Order, led by the Guards massive flagship Hutet, arrived and drove off or destroyed the
remaining enemy vessels.
Initially, the use of such technology was thought to be predicated on the overall
design of a vesselthe more aerodynamic the design, the better the resulting warp field
dynamics, thus the more success a vessel would have at generating a quantum field and
maintaining a given velocity while within a subspace corridor. In simulations, this was later
proven to be a fallacy as a highly advanced computer system paired with a sufficiently
powerful reactor core were able to overcome any potential stumbling blocks presented
due to a vessels design.
In actual use, the propulsion system proved itself when the Excalibur herself traveled
from Starbase 24 to the Grazer system in the outer rimtraversing a distance of just over
130 light yearsin just under an hour.
Combined with her armament and massive size, Quantum Slipstream Propulsion
effectively transformed Excalibur into what critics called a first strike weapon, much to the
chagrin of the Starfleet Admiralty and especially those in the ASDB who actively developed
the system.
Excalibur herself was formally commissioned on 12 March 2381 with a limited
production run of a further five vessels ordered on 20 AprilOdyssey (BB 71832-A),
Columbia (BB 99001), Nautilus (BB 99002), Charleston (BB 99003) and Alliance (BB 99004).
In the interim period between this point and leading up through early-2385, Excalibur
and her sister ships were used extensively in reconstruction and rebuilding efforts,
transporting untold millions of tons of cargo and supplies, helping to stabilize the Federation
and Starfleets vital infrastructure during this vital period.
On 22 Feburary 2385, the Excalibur under command of Captain TLaan, was
reassigned as the lead ship of the Fourth Fleet. Since mid 2382, Orion and Nausicaan
pirates had waged an increasingly costly campaign of harassment against Alliance
merchant shipping, starting in systems adjacent to the Romulan Neutral Zone but
eventually spreading inward. The Fourths mission was one of aggressive interdiction/antipiracy and containment that featured two componentsthe destruction of pirate bases
and an overall blockade of Nausicaa itself.
With the Federations entry into war alongside the Klingons later that year, the
Excalibur and her sister ships became the spearheads of the respective fleets to which they
The Odyssey, named for the first Federation starship lost in combat against the
Dominion, amassed an impressive kill record throughout the conflict as well. Flagship of the
Seventh Fleet stationed along the Gorn border, numerous enemy ships fell to her
especially after the Seventh participated in Operation Thunderbolt (11 June 23
September 2386), a joint operation with the KDF, in which Gorn space was penetrated and
completely cut off from outside aid for a prolonged period.
Despite the capabilities and the impressive performance of the Nautilus, Odyssey
and her sister ships in service, the class lengthy construction time and high resource
requirements led Starfleet Command to decline any further orders following the wars end
in 2387. The performance of the smaller Essex and Eagle classes was judged to be more
than adequate and all Excalibur class ships were soon reassigned to both Project Full
Circle and Mission: Gamma, save for the Excalibur herself which was kept in the Alpha
Quadranttasked with the defense of Sector 001.
Though production has long since ended, these 6 mighty ships symbolize the
Starfleets technological sophistication and tactical superiority, continuing on a path
blazed by legendary classes such as Constitution, Ambassador and Galaxy.
Class
Classification
Excalibur
Battleship
Service
2381Number Active 6
Length
Beam
Height
Decks
2500m
882m
320m
80
Mass
Compliment
880
Armament

6 Mark IV Torpedo Launchers
Defense Systems

DEVONSHIRE
CLASS DREADNOUGHT
From the late 24th well into the beginning of the 25th century, Starfleets shipbuilding
strategy remained in a perpetual state of disarray and confusionmired down by politics,
resource & manpower shortages and a general lack of direction. Attempting to chart a
new path forward and moderate the increasing militarization of Starfleet, the ASDB
introduced a proposal for a spiritual successor to the Sovereign class.
Starfleets recent ship introductions from 2376 onwards were targeted efforts to fill
perceived holes or gaps in the fleets inventorythe Luna class being an example,
designed specifically for deep space scientific exploration and study. The Eagle class was
another example--the product of a study aimed at evaluating the feasibility of integrating
a dedicated Command Cruiser into the overall fleet structure, but later became devoted
solely to fulfilling the needs of both Starfleets Starfighter Command as well as its Marine
Corps.
However, there was also a need to replace a number of venerable ship classes,
either because of age and related issues, or because of difficulty and/or inability to adapt
to the latest technologies.
The former was the case with both Excelsior and Miranda. Though they expanded
the fleets capabilities and overall strength exponentially, they had fallen far behind
technologically by the late 24th century and suffered grievously during the Dominion War.
Additionally, age-related stress fractures in many of these ships led Starfleet to retire both
classes en masse at the wars conclusion.
The latter on the other hand, applied to Galaxy and Nebula. Revolutionary in the
same sense as Excelsior and Miranda at the time of their introduction in the late 2350s,
both nonetheless suffered several notable problems with major systems over the next
decade. They were also ill equipped tactically and lacked the defenses to thwart primitive
aggressors (the Starship Enterprise-D being destroyed by an outdated Klingon BRel class
Bird of Prey) as well as those that were more advanced (the Starship Odyssey being quickly
overpowered by and subsequently falling to a trio of JemHadar Attack Ships). The
proverbial nail in the coffin for these two classes though, was the extreme difficulty faced
by engineers and technicians in upgrading both to handle new Quantum Slipstream drives.
The new propulsion technology revolutionized space travel as we know it and
promised to usher in a new golden age in scientific exploration and discovery.
Unfortunately though, the inability of the computer systems to handle the complex
calculations required to keep the slipstream stable, as well as the enormous complexity of
installing a completely new system consigned both classes to eventual retirement.
Starfleets solution for both issues came in the form of the Essex class Battleship and
Lancer class Heavy Frigate. Massive vessels designed from the keel up to remain highly
adaptable and capable of incorporating the latest technological advances, they are
poised to become the next great fleet workhorses.
These overriding issues aside, Starfleet also faced difficulty in fielding a flagship class
capable of adapting to the challenges born out of an increasingly unstable astro-political
landscape. Sovereign was Starfleets technological gem, succeeding Galaxy as the fleets
premier multi-mission cruiser. The success found by ships of the class against notable
threats including the Borg, Dominion and Remans as well as Starfleet continuing the famed
Enterprise lineage with a Sovereign class vessel (the Starship Enterprise-E, launched 2372)
seemed to cement the class reputation. However, the Federations peaceful ethos as well
the infamous multi-mission philosophy which had heavily influenced (or some say,
dictated) Federation starship design and construction since the beginning of the century
had constrained to a certain extent, the creative direction in which designers and
engineers felt they could go. The one barrier they had not yet broken was that of size.
Thus, to find a solution to this vexing issue, ASDB designers broke that barrier in a big
way, resulting in the Excalibur class. A 2500m long leviathan, Excalibur bristled with
weapons and was capable of embarking untold numbers of ground troops and
starfighters, while also remaining large enough to maintain fully staffed departments
(Science, Medical etc) that one would normally find on a deep-space exploration vessel.
By 2390, 6 of these ships had been produced, including the prototype, and despite
their outstanding in-field performance, the construction time (30 months from start to finish)
and the resource requirements were considered too prohibitive for a class that was
intended to see mass production.
The ASDBs second attempt, completed early the following year, was considerably
more restrained in scope. The design itself was based predominantly on the Sovereign,
with moderate influence from Excalibur and was brought up in sizeending up just 100m
longer than Eagle (1,126m vs 1,023m). Designed to the same multi-mission standard as
Sovereign, though with a stronger offensive/defensive focus, the ASDB attracted the
attention of the Admiralty and many throughout the officer corps as well.
Designed around the same 1st Generation Quantum Slipstream Drive that equipped
the Essex, Lancer and Excalibur classes, this new classclassified as a Dreadnought, with
the codename Devonshirewas rated for a compliment of 825 officers and crew and
could embark up to 1 Regiment (1,296) of Marines.
Like the Galaxy and Sovereignand the trailblazing ConstitutionDevonshire was
outfitted with extensive scientific facilites. A total of 20 science labs and related support
facilities made extensive use of bleeding edge technologies that promised to enhance
Starfleets scientific and exploratory efforts immeasurablymaking it, as with its famous
progenitors, ideally suited for extended duration deep space assignments.
Unlike the Galaxy class though, Devonshire was also supremely equipped tactically.
Several incidentsincluding the destruction of the Starship Enterprise-Dhad irrevocably
marred Galaxys reputation and for better or worse, had pointed out the fatal drawbacks
in pursuing a multi-mission philosophy at the expense of defensive/offensive capability.
Type XV Phasersemployed on both the Excalibur and Essex classeswere made
central to Devonshires armament. The 17 emitters were each capable of delivering nearly
200% more raw energy against a target, while having only a increased power draw of 20%
over Type XII weapons. Supplemented by 8 Type IV Torpedo Launchers, Devonshire would
seem to outgun Essex by a marginal amount.
Classification would seem to be a confusing issue at first, as Devonshires size and
armament would place it solidly in the company of many grand Battleships. However, it is
important to note that these two factors do not take into account modern mission profiles.
Designers anticipated this however and in keeping with traditional naval parlance,
emphasized the speed and agility aspects at the expense of heavier armor and
protection.
To that end, the Regenerative Deflector Shield System was engineered with a lower
total energy capacity and the amount of ablative armorthough slightly thicker than
Sovereignwas still measurably less than either Essex or Excalibur.
An equally notable, but oft-overlooked design feature, were the five separate
hangar baysthe most on any Federation Starship past or present (excluding carrier
classes). This gave the Devonshire the ability to not only embark large numbers of small
craft (actually putting it ahead of the Eagle), but also provides the flexibility to fully respond
to different types of disasters (emergency evacuation, mass casualty etc).
In time of war, Devonshire could embark up to a full wing of fighters (for 72 total
craft)but this was an extreme measure only envisioned for use during periods of sustained
hostilities. The class nominal small craft loadout was a highly diverse mix of shuttlecraft,
runabouts and fighters intended to enhance the ships overall flexibility in carrying out a
wide range of missions. Additionally, Devonshire was selected as the primary launch
platform for the Pulsar class RunnaboutStarfleets intended successor to the venerable
Danube class.
With the design and engineering work finalized, production commenced late in 2391.
With the catastrophic damage inflicted to the Starship Enterprise (at the hands of the
notorious terrorist group True Heirs of Andor) and Starfleet Commands decision to scrap
the nearly 20 year old ship following its recovery and return to Earth in early 2392, hull
number 1701-F was inserted into the production schedule at Starfleets San Francisco Yards
complex and Enterprise became the second Devonshire class Dreadnought to be
launched, formally commissioned on 22 December of that year.
Along with Devonshire (DN 100100) and Enterprise (the seventh Federation Starship to
bear the name) a total of 10 further vesselsEclipse (DN 100101), Royal Sovereign (DN
100102), Endeavour (DN 100103), Magellan (DN 100104), Independence (DN 100105),
Challenger (DN 100106), Dauntless (DN 100105), Victory (DN 100106), Bonaventure (DN
100107) and Solaris (DN 100108)were launched between 2392 and 2404 with production
expanding to the naval yards at Boston, Miami, Plymouth (England) and Yokohama
(Japan) at Earth, Port Armstrong at Luna, Utopia Planitia at Mars and other notable
complexes including Antares III, Keldanis Prime and ASDBs Integration Facilities based at
Starbase 74.
Their deployment was split evenly, with Devonshire, Enterprise and half of the first
build group being assigned to Project Full Circle in the Delta Quadrant while the
remaining ships were retained for use with Mission: Gamma and other duties throughout
the Alpha, Beta and Gamma Quadrants.
With tensions once again on the rise between the Federation Alliance and the
Typhon Pact, it remains to be seen if Starfleet will keep these majestic starships devoted to
the kind of deep space exploration for which they were designed. If history is any judge however, the opening of a new conflict will almost certainly see Starfleets assetsincluding
these Dreadnoughtsredeployed as part of a broader offensive/defensive plan.
Devonshire Block I (1701-F) configuration (top); Block II/Production configuration (bottom)
Class
Classification
Devonshire
Dreadnought
Service
Length
Beam
Height
Decks
1,123m
443m
121m
26
Mass
Compliment
825
Armament

Defense Systems

Standard Duranium/Tritianium Double Hull plus 15cm High Density Armor
Bibliography
LogosUnknown/Cyklus07 (DeviantART)
Danube
SchematicsBernd Schneider (Ex-Astris-Scientia)
Pulsar
DesignGalen/Kaden Designs
VisualsJack Skieczius (Project Gryphon)
Pegasus
Design/Visualsrengers (Star Trek: Bridge Commander Model)
Centaur
DesignAdam Buckner
SchematicBernd Schneider (Ex Astris Scientia)
New Orleans
DesignEd Miarecki
SchematicBernd Schneider (Ex Astris Scientia)
Lancer
Design/SchematicGustavo Castillo (Gustavo Castillos DesignsGOODSTUFF 2)
Proxima
Design/VisualsDJ Curtis (Star Trek: Bridge Commander Model)
Nebula
DesignGreg Jein
SchematicRobert Bonchune (Drex Files)
Saber
DesignAlex Jaeger
SchematicDoug Drexler (Drex Files)
Galaxy
DesignAndrew Probert
SchematicGustavo Castillo (Gustavo Castillos DesignsGOODSTUFF 2)
Nova/Nova II
DesignRick Sternbach
SchematicEddie Robison (Drex Files)
Akira
DesignAlex Jaeger
Norway
DesignAlex Jaeger
SchematicHandofmanos (DeviantART)
Intrepid
Defiant
DesignJames Martin/Herman Zimmerman/Gary Hutzel
SchematicBernd Schneider (Ex Astris Sceintia)
Sovereign
DesignJohn Eaves (Eavesdropping with Johnny)
SchematicGustavo Castillo (Gustavo Castillos DesignsGOODSTUFF 2)
Luna
Design/SchematicSean Tourangeau (DeviantART)
Eagle
Design/SchematicAdam Heinbuch
Valiant
SchematicEBOLII D. Bates (Star Trek: The Final Frontier)
Dauntless
Design/Visualscliperkins (Star Trek: Bridge Commander Model)
Galant
VisualsMayhemUK, Queball et al. (Star Trek: Bridge Commander Model)
(Star Trek: Armada 2 Model)
Prometheus
SchematicFoundation Imaging (Ex Astris Scientia)
Essex
Design/Schematic/CutawayGustavo Castillo (Gustavo Castillos DesignsGOODSTUFF
2)
Excalibur
DesignSteven Davis
VisualsCpt LC Amaral (Star Trek: Bridge Commander Screens)
Devonshire
Design/SchematicsJoshua Samuelson (DeviantART)

Ships of The Star Fleet 3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ships of The Star Fleet 3

Uploaded by

Copyright:

Available Formats

SHIPS OF THE STA RFLE ET

Ships of t he St arf leet

By The Red Admiral

Starfleet Operations/Advanced Starship Design Bureau

Copyright 2414 Starfleet Department of Technical Services

This document and its entire contents Copyright

2012 MTD Publications

SHIPS OF THE STARFLEET

STATE OF THE FLEET

operationsacting as early warning platforms for planetside colonies and settlements, as

159 metric tons

6 Type IV Phaser Emitters

Standard Deflector Shield System

189 metric tons

6 Type VII Phaser Emitters

Standard Deflector Shield System

74,909 metric tons

6 Type VIII Phaser Emitters

Standard Deflector Shield System

125,900 metric tons

3 Type IX Phaser Emitters

Standard Deflector Shield System

310,000 metric tons

4 Type VII Phaser Emitters

Standard Deflector Shield System

165m (Nova); 221m (Nova II)

8 (Nova); 11 (Nova II)

127,000 metric tons

170,000 metric tons

80 (Nova); 107 (Nova II)

Standard Deflector Shield System

604,958 metric tons

185; 480 evac. limit

Standard Deflector Shield System

Befitting the class combat-oriented (Borg Busting), the armament is extremely

355,000 metric tons

1 Type X Phaser Emitter

Standard Deflector Shield System

2,962,823 metric tons

Providing protection is a Regenerative Deflector Shield System (as opposed to the

362,769 metric tons

4 Pulse Phaser Cannons

Regenerative Deflector Shield System

large, reinforced pylonsreminiscent of the Mirandas rollbarthat extended in from each

446,345 metric tons

9 Type XII Phaser Emitters

Regenerative Deflector Shield System

479,527 metric tons

9 Type VIII Phaser Banks

Standard Deflector Shield System

900,000 metric tons

6 Type X Phaser Emitters

Standard Deflector Shield System

2,408,823 metric tons

13 Type XII Phaser Emitters

Regenerative Deflector Shield System

Throughout the early 24th century, technological advancement proceeded at a

3,575,000 metric tons

5 Type X Phaser Emitters

Standard Deflector Shield System

The problems inherent in such a complex design became apparent beginning in

4,960,000 metric tons

1,014; 15,000 person