Вы находитесь на странице: 1из 16

DOCKYARD

REVIEW
THE JOURNAL OF THE ADVANCED STARSHIP DESIGN BUREAU

VOLUME FOUR
ISSUE EIGHT
APRIL 2376

The Entente Class


Dreadnought: An
Attempt to Correct
the Olympus Class
Problems.

The Prometheus Class


Tactical Cruiser: A Radical
Concept In Starship Design.

Nexus Spacedock: An
interesting venture enters
its third century.

DOCKYARD REVIEW
APRIL 2376

HARD COPY PRINTOUT

GROUP HEADQUARTERS

Advanced Starship Design Bureau


Sol III Orbital Repair and Construction Facility (SpaceDock)
In Orbit Over the San Francisco Metroplex
State of California
United States of America
Terra - Sol System
DIRECTOR

Rear Admiral Chris Wallace


COORDINATOR

Captain Belldandy Morisato


TECHNICAL STAFF

Admiral Alex Rosenzweig


Vice Admiral J. Scott Spadaro
Commander Miyuki Kobayakawa
COVER ART AND COMPUTER MESHES

Cover - Eric Peterson (http://wolf359a.anet-stl.com/)


PUBLISHING OFFICE

Panda Productions
9301 Avondale Road Northeast #D-2022
Redmond, Washington 98052-3353
United States of America
Terra - Sol System

PANDA PRODUCTIONS
United States of America - Terra * 2376
Articles in this publication may be reproduced for informational or archival purposes only, provided proper credit is given to
the author(s).
Text Copyright 1999, Panda Productions. Artwork Copyright 1999 the respective authors. Where possible, permission
has been acquired for their appearance in this document. This document was created purely for recreational and informational purposes
Published by Panda Productions on a not-for-profit, free-distribution basis. Neither articles nor this publication may be sold
or re-sold by any party in any format.
All correspondance should be directed to the Publishing Office.

1002

CONTENTS
AUTHOR

TITLE

PRINTOUT

Comment

1004

RAD Kiri Vaughn

The Entente Class Dreadnought

1005

RAD Chris Wallace

The Prometheus Class Tactical Cruiser

1009

CMD Kyle A. JaFadey

Nexus Spacedock

1013

ENTER THE FORUM


We welcome brief
comments on material
published in Dockyard
Review and also brief
discussions of interest for
possible publication in the
Comments section. We
are also looking for
articles for future issues.
Any articles or letters
submitted to Dockyard
Review are subject to
editing for content and
length before publication.

COVER
ILLUSTRATION
The Entente Class
Dreadnought U.S.S.
Toconderoga (DN 73281)
and the Nebula Class
Light Cruiser U.S.S.
Endeavour (CL 71805)
on joint patrol.

The U.S.S. Bright Star (CKE 71875), Sutherland (CL 72015), and Intrepid (CR 74655) return to
Nexus Spacedock from an engagement with pirate Klingon forces.
(Art by MJN - www.desktopstarships.com)

The opinions or assertions in the articles here are the personal ones of the authors
and should not be construed as official. They do not necessarily reflect the views of
the Advanced Starship Design Bureau or the publishers of Dockyard Review.
This publication incorporates data and scanned images taken from other various
works relating to the Star Trek seroes and movies. This publication is intended for
recreational and informational purposes and is published on a not-for-profit and
free-distribution basis. The inclusion of this data and imagery is not intended to be a
violation of the copyrights and trademarks of the original works publishers and
authors.

1003

Comment
Klingon Ships - Against
(see Klingon Vessels in Starfleet? by Vice Admiral Gilak Nantiya,
October 2371 Dockyard Review
Captain Steven Horn, Starfleet Operating Forces
Military Operations Command - TacFleet
It is indeed a dark day for the Federation and Starfleet when we need to rely on the
Klingons to fill-out our force structure. Slow, underpowered, overweaponed, and riddled
with safety and design defects, to ask our brave crews to risk their lives aboard them is ludicrous. Starfleet needs to seriously review its shipbuilding priorities from grandiose designs
like the Galaxy and Sovereign, and concentrate on smaller ships, like the Intrepid and Norway,
that perform the day-to-day duties of patrol, support, and rescue.

Klingon Ships - For


(see Klingon Vessels in Starfleet? by Vice Admiral Gilak Nantiya,
October 2371 Dockyard Review
Captain Jake Cutter, Starfleet Operating Forces
Military Operations Command - TacFleet
Though decried by many within Starfleets upper echelons as a waste of resources, the
opportunity presented to us by the Klingons is one I think we should not let go to waste. Yes,
the Klingon vessels are inferior in many ways to their Starfleet counterparts. But they are also
incredibly tough, designed for years of service on the frontier with a minimum of maintenance exactly the role they are needed.
It is an unfortunate fact that Starfleet, lulled into a false sense of security by quiet
neighbors, allocated a far-too-generous amount of the shipbuilding budget to high-ticket
Explorer vessels. These ships proved ill-equipped to the task of defending the Federation
from threats like the Borg and Romulans, and are far too expensive to place on picket duty
alongside the Cardassian Union or outside the badlands. The Klingons have offered us a
class of ships well-suited to the picket and patrol role operating far from Federation supply
and support stations. And they can be quickly updated with Federation computer and safety
systems, as well as Federation-style accommodations.
And let us not forget that this is an excellent way for the Federation and Klingons to
strengthen ties that, as of late, have become increasingly strained in areas. Klingon crews
will need to train their Federation counterparts, and Federation design-uprating can be
added to Klingon-crewed vessels, as well.
1004

The Entente Class


Dreadnought
Take Two on the Dreadnought
By:

Rear Admiral Kiri Vaughn


Dreadnought Development Program
Advanced Starship Design Bureau

The first modern dreadnought, the Olympus class, entered Fleet service in 2370 along with the Galaxy (II)
class Improved Large Exploratory Cruiser. The Olympus class was created by adding a third nacelle to the Galaxy class spaceframe, as well as improvements in her tactical and shielding systems. Five vessels of the class
were built, one of which was designed to serve as a frontline combat hospital.
However, as soon as they entered service it became obvious that there were some serious design problems with the class. The third nacelle, in particular, suffered from severe stress fractures at high-warp maneuvers and it was feared that, in combat, the strut would be susceptible to failure under fire. Also, advances in
weapons and shielding systems had made some of the newer vessels (like the USS Bright Star and the Sovereign
class) almost their equal.
In 2373, the SSDAC met to consider options to either refit or replace the Olympus class. Tensions in the
Gamma Quadrant with the Dominion made it seem prudent to continue development, and possible construction, of large combat vessels.
GENERAL APPEARANCE
Like the Olympus, the Entente class also mounts three nacelles. From a distance, both the Olympus and
Entente classes look similar. It is only when viewed from closer angles do the obvious differences between the
classes become apparent. Unlike the Olympus, the Entente class uses a standard Galaxy class secondary hull
without the rear hangar deck modifications.
PROPULSION AND POWER SYSTEMS
Learning from the mistakes with the Olympus class, the third LF-41 nacelle was mounted on a special
strut extending up from the secondary hull. This negated the extensive modification to run a third intermix shaft
into the nacelle as had been the case with the Olympus. As with the Olympus, only one warp core is installed with
the same modifications to provide the additional reactants necessary to power three nacelles. The system maintenance penalty has been reduced a little, now standing about 15% more than a Galaxy class.
TACTICAL SYSTEMS
Initial plans were to add the Type XII phaser strip, but additional thought on the issue decided that
sticking with the improved-duration Type X units fitted on the Olympus was a better idea, with firing times now
increased to 35% over a standard Type X. As with the Olympus, mounting of the FSS shield system proved
impossible, and the FSQ/2 was fitted.
One of the problems with the Olympus was that it lacked the ability to deliver a killing first salvo blow.
The Mk 100 photon torpedo system was fitted to allow the firing of quantum torpedoes, but additional punch
was wanted.
Fitting additional photon torpedo launchers was not really an option, so it was decided to fit a massive
phaser cannon on the bottom of the saucer that extends back to the dorsal connector. This cannon is fed by

1005

special high-capacity plasma conduits, but still allows separated flight mode. Output is classified, but it is rumored to be able to punch through the shields of any known starship. In addition, two narrow-beam phaser
canons similar to those used on the Defiant class were fitted to either side of the bridge to improve forward
firepower.
Both a Combat Information Center and Aegis are standard on the Entente class. CETIS MK III with Type
225 TACAR II (Target Acquisition Center Accelerated Response) remain standard equipment, though the 42/
ADA Countermeasures Support System has been added.
The mounting hardware of the third nacelle allowed all three shuttlebays to remain in their original
positions Embarked craft is about double that of a Galaxy, including a mix of runabouts, shuttles, and Peregrine
fighters.
COMPUTER SYSTEM
The Entente class carries the same M-15 Isolinear III with LCARS system as the Olympus class. As in
Olympus, the Aegis and other mission-specific computer hardware integrates directly with the onboard computer system, though multiple redundancies are in place to insure that they will continue to operate in case of
primary computer failure.
SHIPS FACILITIES
The Entente performs a dual military and exploration role like the Olympus class and carries the same
mix of equipment in general and reflecting the advances in both classes of systems over the intervening years.
DEVELOPMENT AND CONSTRUCTION HISTORY
The ASDB finalized the design in December of 2370 and construction on two new hulls was started.
Once war with the Dominion had been declared, four more vessels were laid down. Initial construction on
Entente (DN 73280) and Ticonderoga (DN 73281) was completed in early 2375, and the ships were immediately
sent into combat operations against the Dominion. The other four were rushed into service in mid-2376, a few
months before the Armistice.
CONCLUSION
The Entente class seems a more viable platform than the Olympus. Its combat prowess was better than
the Olympus, and the vessel is a little cheaper to build. At the completion of the war, all six vessels returned to the
yards to complete their outfitting. With five Olympus and six Entente class vessels, Starfleets offensive capabilities should be well served for decades to come.

Rear Admiral Vaughn currently serves as the head of the ASDBs Dreadnought Development Group. In
addition to the Entente, she also worked on the Olympus class. Her Starfleet credentials include both the
XO and CO spots on Excelsior (including the U.S.S. Berlin) and Nebula (U.S.S. Farragut) class starships.

1006

1007

Entente Class Dreadnought


Displacement:
Overall Length:
Overall Draft:
Overall Beam:
Propulsion:

Velocity:
Duration:
Complement:

Embarked Craft:

Navigation:
Computers:
Phasers:
Phasers:
Phasers:
Missiles:
Defense:
Life Support:

1008

5,520,000 mt
643 m
195 m
464 m
Three LF-41 Mod 1 energized-energized antimatter warp drive units with Continual Warp Field
Balance Generation
(System Contractor: Leeding Energies, Sydney, Earth)
Two FIG-5 subatomic unified energy impulse units
(System Contractor: Kloratis Drives, Tellar)
QASR-2 particle beam maneuvering thrusters
(System Contractor: Scarbak Propulsion Systems, Earth)
Trentis IV pulsed laser reaction control system
(System Contractor: Orage Ijek, Aksajak, Andor)
Warp 7.0
Standard Cruising Speed
Warp 9.5
Maximum Cruising Speed
Warp 9.9
Maximum Attainable Velocity
5 years, standard
90
Officers
575
Enlisted Crew
1000
Passengers (Normal Up to 5000 maximum)
500
Marines (Normal Up to 5000 maximum for short duration)
2165
Total Crew (Standard)
4
Danube Class Runabout
20
Type 10 Combat Drop Shuttle
6
Type 6 Personnel Shuttle
10
Peregrine Class Fighter
6
Type 7 Personnel Shuttle
2
S-3 Sentry SWAC Shuttle
9
Type 9A Cargo Shuttle
10
Type 16 Shuttlepod
RAV / ISHAK Mod 3 Warp Celestial Guidance
(System Contractor: Tlixis Ramab RRB, Coridan III)
M-15 Isolinear III with LCARS interface software
(System Contractor: Daystrom Computer Systems, Luna)
12 Type X Collimated Phaser Array
(System Contractor: HiBeam Energies, Earth)
2 Type XII Phaser Cannon
(System Contractor: HiBeam Energies, Earth)
1 Type XV Phaser Cannon
(System Contractor: HiBeam Energies, Earth)
4 Mk 95 Photon Torpedo Launchers
(System Contractor: Loraxial, Andor)
FSQ/2 Primary Force Field
(System Contractor: Charlotte Shields, Earth)
MM6 Modular Gravity Unit
(System Contractor: Morris Magnatronics, Palyria, Mars)
AL4 Life Support System
(System Contractor: AAlakon Landiss, Divallax, Andor)

The Prometheus Class


Tactical Cruiser
A Radical New Starship Design
By:

Rear Admiral Chris Wallace


Chief of Fleet Operations, Starfleet

DESIGN HISTORY
Since the early 2300s, Starfleet has changed the focus of its force structure to reflect a far more defensive
posture. While the Fleet has never been intended as an instrument to impose Federation policy, the
decommissioning of battleship and dreadnought class vessels has significantly altered the combat capabilities of
the Fleet.
In many ways, this was understandable. With the disappearance of the Romulans in 2311 after the
Tomed Incident, and the alliance with the Klingon Empire in the mid 2300s after the Battle of Narendra III,
Starfleet no longer needed heavily armed warships. This time of Galactic Peace allowed the Federation to
concentrate on exploration, and Starfleet adapted to reflect this.
But times have changed. Two deep incursions by the Borg Collective, the current war with the Dominion,
hostilities with the Romulans, and instability within the Klingon Empire have made the galaxy a much more
dangerous place. A raft of new designs have been developed to address this issue, but none as radical as the
Prometheus concept.
DESIGN OVERVIEW
The Prometheus introduces the concept of Multi-Vectored Attack Mode to starship design. The
Prometheus can actually split into three separate warp-capable tactical platforms which can then attack a target
from three separate angles. Though the two classes look similar, the Prometheus and Intrepid classes share little
similarities beyond dimensions. classified as a Deep Space Tactical Frigate, she is expected to be used on
missions deep into Cardassian and Dominion territory.
PROPULSION AND POWER SYSTEMS
The Prometheus is the first ship since the Peacekeeper class to mount four nacelles, and unique amongst
vessels in mounting three separate warp cores. In normal flight mode, only the two directly feeding the upper
and lower nacelle pairs are in operation. Only when the ship splits into MVAM does the third core, mounted
between the two impulse engines, come on-line.
Balancing the output of two cores into four nacelles is a highly complicated procedure. The Prometheus
mounts the most powerful shipboard computer system, the M-16, which is also used on the Galaxy (II), Intrepid,
and Sovereign classes. The two cores and four nacelles result in the fastest speed ever attained by a Federation
starship a stupendous Warp 9.999. However, such speed requires massive amounts of consumables, resulting
in a range of some one year.
TACTICAL SYSTEMS
As a warship, the Prometheus mounts the latest in Federation weaponry. She literally bristles with thirteen
Type XII phaser strips and six Mk. 90 torpedo launchers. This makes her the most powerful vessel in known
space.

1009

Shielding is provided by the FSS system though, remarkably, the FCE-2 cloak system has not yet been
fitted. Considering this classs role, it is expected to be fitted once trials and tests are completed.
OPERATIONAL DISPOSITION
The U.S.S. Prometheus * NX-59650 was launched in 2374. On her maiden voyage, agents of the Tal Shiar,
who attempted to return her to Romulan space, hijacked her. Incredibly, both the Prometheus EMH and the
EMH from the missing starship U.S.S. Voyager were able to incapacitate the hijackers and assist the Federation
pursuit force against three Romulan Dderidex class warbirds. The vessel was heavily damaged in the engagement,
and has since returned to Utopia Planitia for repairs.
CONCLUSION
The Tal Shiar incident has shown the effectiveness of this platform, disabling a Nebula class cruiser and
destroying a Dderidex warbird. Trials and shakedowns are expected to last until 2375, but with the conflict with
the Dominion, a favorable outcome will probably result in further vessels being procured.

Admiral Wallace is the Chief of Fleet Operations, Starfleet. As the former Chairman of the ASDB, he
assisted on the Prometheus Class Starship Development Project.

1010

1011

Prometheus Class Tactical Cruiser


Displacement
Overall Length
Overall Draft
Overall Beam
Propulsion:

Velocity:
Duration:
Complement:

Embarked Craft:

Navigation:
Computers:
Phasers:
Missiles:
Defense:
Life Support:

1012

1,500,000 mt
344 m
94 m
141 m
Two LF-50 Mod 1 energized-energized antimatter warp drive units
(System Contractor: Shuvinaaljis Warp Technologies, Vulcan)
Two FIG-5 subatomic unified energy impulse units
(System Contractor: Kloratis Drives, Tellar)
QASR-2 particle beam maneuvering thrusters
(System Contractor: Scarbak Propulsion Systems, Earth)
Trentis IV pulsed laser reaction control system
(System Contractor: Orage Ijek, Aksajak, Andor)
Warp 9.0
Standard Cruising Speed
Warp 9.8
Maximum Cruising Speed
Warp 9.99
Maximum Attainable Velocity
1 year, standard
41
Officers
100
Enlisted Crew
0
Passengers (Normal Up to 50 maximum)
141
Total Crew (Standard)
0
Danube Class Runabout
2
Type 6 Personnel Shuttle
0
Type 7 Personnel Shuttle
0
Type 9A Cargo Shuttle
4
Type 16 Shuttlepod
RAV / ISHAK Mod 3 Warp Celestial Guidance
(System Contractor: Tlixis Ramab RRB, Coridan III)
M-16 Bio-Neural Gel Pack-Isolinear III with LCARS interface software
(System Contractor: Daystrom Computer Systems, Luna)
13 Type XII Collimated Phaser Array
(System Contractor: HiBeam Energies, Earth)
3 Mk 95 Photon Torpedo Launchers
(System Contractor: Loraxial, Andor)
FSS Primary Force Field
(System Contractor: Sylvanesti Shields, Alkara XV)
MM6 Modular Gravity Unit
(System Contractor: Morris Magnatronics, Palyria, Mars)
AL4 Life Support System
(System Contractor: AAlakon Landiss, Divallax, Andor)

Nexus Spacedock
Fortifying the High Frontier
By:

Lieutenant Commander Kyle A. JaFadey


Tactical Officer, Nexus Spacedock
With grateful acknowledgement of the contributions by Lord Gateway, Chairman Emeritus,
Nexus Free Trade Company.

As one of the first Deep Space Stations commissioned, Space Station Nexus entered service in the Obsidian
Planetary System in 2277, located on the extreme Southern edge of the Federation, about equidistant between
the Klingon Empire and the Cardassian Union. Local records going back centuries show that the Obsidian system
was a major intersection of trading routes between the Klingon Empire, Federation space, and an unknown race
beyond the Federation Treaty Zone.
The original Nexus Station used the trusty Centurion class design. The people of Galena, one of the two
inhabited planets in the Obsidian system, funded the construction of the original Nexus Station and subsequently
leased it to Starfleet for a period of 99 years. The Stations mandate was to insure the safe conduct of traders and
at the same time help establish a strong military presence along the Klingon frontier. This move of course drew
some criticism from diplomatic circles, but the Galenan principle of welcoming open trade even at the height of
tensions with the Empire, soon mollified even the loudest critics. In 2349, first contact with the Cardassian Union
was made by a Starfleet Excelsior class starship on exploratory patrol approximately ten light-years from BajorBhavael. The Excelsior was fired upon, but was able to withdraw. The subsequent encounters with the Cardassian
Union opened up yet more trade for the venerable station, while at the same time re-emphasizing its need as a
strong defensive presence out on Starfleets newest frontier.

DEVELOPMENT AND CONSTRUCTION HISTORY


The 99-year lease on Nexus Station came to an end in 2376. By that time, the original station was getting
extremely long in the tooth. Negotiations between Starfleet and the Galenans began in 2356 to both renew the
stations lease, and uprate the station to a newer design. The recent start of hostilities with the Cardassian Union
helped drive these talks. The Galenans expressed strong interest in a facility that would handle the largest
Starfleet ships, including the Galaxy and Nebula classes.
With the massive expansion of the Federation Treaty Zone, and active missions to begin mapping it, it
was necessary for a new generation of starbases to provide way stations for starships, as well as facilities for the
administration and defense of these territories. It was decided that the traditional process of constructing
individual starbases on the surface or in orbit around planets would not be a viable option, due both to cost and
timescale. Two general Starbase structures were commissioned, each designed for a special purpose.
When the Galaxy class Starship Development Project went official in 2343, the Utopia Planitia Yards
where the ships would be built lacked the orbital dockyard facilities to construct such a massive vessel. Original
plans were to use the giant skeletal dockyards like those found on Earth Station McKinley. However, such
facilities would not allow the office and computer space needed by the Engineering and Design Teams working
on the vessel. Therefore, it was decided to take the Spacedock in orbit around Terra and scale it up by a factor of
three. This would allow a number of Galaxy class Ships to be built simultaneously inside, with full protection
from solar radiation events as well as almost unlimited office and support space. It was quickly decided that
most of the connecting structure between the upper docks and the matter / anti-matter power supply would not
be needed, dramatically lowering the cost and construction time. The facility was finished in 2350, just in time
for the start of construction on U.S.S. Galaxy.
The original plans were kept, however, and became the first of two planned starbase types. It was
decided that only one in ten of the new starbases would use this design, due to the costs involved. They would

1013

be spread more or less equidistant throughout the Federation, and would be used for vessel uprating and major
repairs. Starbase 74 in orbit around Tarsas III was the first of these stations, and there are now an additional nine
in service. The second series of starbases would use the old R1 station, updated to modern systems. Cheap and
quick to produce, dozens are now in service.
The Galenans decided that the Spacedock type would be the better fit. However, such a massive facility
was beyond the financial means of a single star system. Starfleet offered to build and run the facility, as such a
design would be an excellent fit for Starfleets purposes, but while the Galenans had no problem with Starfleet
administration, they did not want Starfleet ownership. Just as it was with the construction of Nexus Station,
ownership was a matter of planetary pride for the Galenans, who see these facilities as a mark of continued
peace and prosperity within the system. To finance the construction of the station and retain overall ownership,
the government of Galena entered into a limited partnership with the Nexus Free Trade Company (NFTC). The
NFTC was able to underwrite much of the construction cost by leveraging its vast dilithium mining operations.
The Galenan Government and the NFTC were able to secure 25% of the construction cost of the station with
Starfleet agreeing to cover the remaining 75% of the costs in return for a 99-year rent-free lease with an automatic
99-year extension at the end of that time. In addition, Starfleet would have full control over the upper docking
facility (the NFTC would control the lower unit and all civilian commercial activities), as well as assigning the
Command and Senior Staff for the facility. Thus, Starbase Nexus became the largest privately owned structure
in Federation space and the only Spacedock not to be constructed and owned by Starfleet itself. Completed in
2375, it now takes its place as the crown jewel in one of the Federations most heavily secured and prosperous
Systems.

STATION FACILITIES
Spacedock Nexus has a normal resident operational staff approaching 25,000. The station is also home

1014

to close to 100,000 resident dependents from Galena and the Federation, as well as Klingons and even some
Romulans. As a major free-trade port, it should come as no surprise that the Ferengi Alliance maintains a strong
presence of some 3000, including a full Consulate on Galena, as well as a Ferengi Trade Mission and one of the
largest offices of the Ferengi Commerce Authority outside of Ferenginar on Spacedock. The daily transient
population can reach upwards of 100,000, most of these merchants and businessmen.
Spacedock Nexus Boardwalk is one of the largest open malls in the quadrant. Fifteen stories in height,
literally thousands of merchants maintain shops and even stalls selling just about every legal substance in the
galaxy (and a few illegal ones, though the NFTC Security Forces are some of the best in the business). In addition
to the Boardwalk, there are other mercantile zones spread throughout the main levels.
The Starfleet Annex on Spacedock Nexus is quite large. Since this is the headquarters of both the Fifth
Fleet and administrative headquarters for Starfleet Region Five, this is to be expected.

STATION DOCKYARD FACILITIES


Spacedock Nexus boasts the most advanced small-ship production facilities on the frontier. The Hakon
Shipyards (as the Hakon Shipbuilding Conglomerate paid for the secondary dockyards) have six berths equipped
to construct everything from luxury yachts to merchantmen, and does an extensive refitting service, as well.
The upper dockyards are ostensibly the exclusive realm of Starfleet, but due to their large size, are often
used by Hakon for the refitting of larger vessels. In addition, Hakon assists Starfleet in the refitting and repair of
Starfleet vessels. This is a mutually beneficial arrangement as Hakon crews learn new skills, and Starfleet has
been able to reduce the costs and time of refits by 15% implementing new techniques developed by Hakon.
While Terra may be home to the premier fighter design companies in the Federation, the Galena system
is by far the largest manufacturer of these craft, with almost 10% of the Fleets fighter inventory for the past
thirty years coming from her ground-based production facilities. The construction quality of these fighters is
second-to-none, and they are used by some of the top Federation squadrons.

TACTICAL SYSTEMS
Due to its proximity to both Cardassian and Klingon space, the Obsidian system was the site of three
major engagements during the Dominion War. It also served as the home port for the Fifth Federation Fleet
under the command of Admiral Kyle Argent, himself a former Commander of Space Station Nexus. Elements of
the Fifth Fleet intercepted a joint Dominion and Cardassian strike force en route to Klingon space, bloodying
them enough to prevent their continuation. In gratitude, the Klingons stationed two task forces at Nexus. Elements
of the Fifth Fleet continuously staged in or around Nexus Space, in preparation for the various Campaigns
during the Dominion War. The Starships U.S.S. Bright Star and Pendragon, assisted in the re-taking of Deep Space
Nine in Operation Return. The Bright Star was also involved with the invasion of the ChinTaka system, while
the Pendragon and other ships of the Fifth Fleet, in conjunction with Klingon forces, assisted in defending the
Southern border of the Federation from two Dominion counter-attacks.
Nexus Spacedock carries the same armament as the other Spacedock starbases. Tactical weapons include
two hundred high output (Type X+) phaser arrays assigned fifty to a quadrant along with forty Mk 90 photon
torpedo launchers (ten per quadrant). The shield system is also the same used by the other Spacedocks, and is
the most powerful in existence. The result is a facility that can withstand attack by elements up to the Task Force
level. For local defense and support, both the NFTC and the Royal Galenan Space Force maintain large squadrons
of fighters at Nexus Spacedock and Galena itself. And if all this was not enough, Starfleet has recently assigned
a task force of five ships to Nexus Spacedock for a two-year tour. They will then be replaced in 2378 by a force
from the Klingon Defense Forces.
Though highly classified, Spacedock Nexus includes some of the most extensive active and passive
surveillance and listening installations known to exist in Federation Space, designed to keep track of ship
movements along the frontier. A highly advanced communications suite is also fitted to maintain contact with
deep-space explorers.

1015

CONCLUSION
With the cessation of the Dominion War and despite its history of conflicts erupting in and around it,
things have returned to a more business-like atmosphere in Galenan Space. However, with its legacy one that
was forged in the heat of Battle, the newest installation to bear the name Nexus indeed stands ready to defend
the High Frontier of the Federation once more if called upon.

Lieutenant Commander JaFadey is the Tactical Officer of Spacedock Nexus.


This work is copyright Kurt F Roithinger 1999, all rights reserved.

1016