Star Trek: Renaissance Technical Manual, Section 1

Written by Chris Edmonds and Dan Carlson

Images by Robert Crosswell and Chris Edmonds

Section 1.0: Introduction to the USS Enterprise

1.1: General Overview

A rounded triangular logo, with a Starfleet delta symbol at the apex of the triangle, a red-purple bird with wings spread rising from flames, and text for the Phoenix Class Starship Development Project below.

The known galaxy has been forever changed by the Dominion War. Unlikely alliances were forged, and superpowers were both made and shattered. Add in the intervention of seemingly mystical noncoporeal beings, and the scope of the whole thing becomes simply mind-boggling. The Federation has weathered the war quite well, despite devastating losses and the humiliating strike on San Francisco launched by the Breen. Starfleet learned a hard lesson that they were becoming complacent in the field of defense. They redoubled their research into better military technologies after the dust settled.

In the years following the defeat of the Dominion, the Federation had several border skirmishes with various powers, eager to try to take a bite out of the weakened Federation. One of these powers was the Sheliak Corporate. These self-important beings thought of all other species as vastly inferior. The Sheliak Corporate got the opportunity they were waiting for to drive the Federation into war when the Tellarites’ home system of Tellar inexplicably translated itself several light-years across the Sheliak border. The Federation tried desperately to reach a peaceful solution to reclaim Tellar, but the Sheliak insisted that it was rightfully theirs, despite the extenuating circumstances. This left the Federation Council little recourse but to declare war. This only served to further shake up the war-weary Federation. This costly conflict was a bittersweet victory, having cost the lives of tens of thousands of Starfleet’s finest. It became clear that the Federation would require a specialized Rapid Reaction Force of starships was needed to defend the Federation’s interests and citizens. The Phoenix Class Project was initiated to create a starship that would be the first of this new breed of starship, and to be the pioneer of several technologies included in other Rapid Reaction Force starships.

1.2: Mission Objectives for the Phoenix Class Project

Pursuant to Starfleet Tactical Directive 1349.2 and Starfleet Exploration Directive 1140.1, the following objectives were established for the Phoenix Class Starship Development Project:

1.3: Development and Construction

The Phoenix Project began in earnest in 2389, shortly after the start of the Sheliak War. The project was dealt several setbacks early on, especially in the propulsion department. Starfleet R&D encountered major difficulties in fitting both a standard warp drive and an experimental slipstream drive into a single spaceframe without either exceeding the volume/mass requirements, or severely restricting the remaining volume available. Designers were left at an impasse until they had an epiphany: install a single hybrid drive instead, one capable of generating subspace fields for both warp and slipstream travel. After four years of concerted effort, R&D finally produced a viable hybrid propulsion system for the Phoenix Class.

The USS Phoenix (NX-87432) began accelerated production in 2397 inside of one of the new pressurized drydocks at the Utopia Planitia Fleet Yards, with the keels of the Enterprise (NCC-1701-G) and Leviathan (NCC-88326) laid four months later. In 2400, the Phoenix began its maiden voyage around the Sol System, and tested its slipstream drive on a short jaunt to the neighboring Alpha Centauri System. It then moved on to the scheduled stress tests of the slipstream drive, flying to the far reaches of Federation territory. It was nearing twelve hours of flight time when the signal from the Phoenix mysteriously vanished. Salvage teams sent to the Phoenix’s last known location discovered an unrecognizable field of debris. Subsequent analysis of the fragments determined that the ship had experienced unexpectedly severe subspace stress. It was deemed that the Phoenix was destroyed due to a catastrophic slipstream drive failure. Production on the two other hulls was halted until the cause of the breakdown was pinpointed. Ultimately, engineers determined that an inherent, irreversable flaw in the drive was the cause, and that the drive could only safely run twelve hours on slipstream, even on low speeds.

Despite this setback, the project resumed construction only a few months later. The Enterprise launched in January 2401, the eighth starship to bear the name. The Leviathan was still eight months away from launch, held up by contract disputes with Dyson Corporation, a major organization that was producing several key parts of the Phoenix class. Fears about the stability of the slipstream drive were eased tremendously with the safe first flight of the Enterprise-G during her maiden voyage.

1.4: General Specifications

Type: Heavy Cruiser

Dimensions: Length, 569.26 meters; Beam, 218.89 meters; Draft: 67.35 meters; Decks, 21

Mass: 2,135,000 metric tons

Accomodation: 45 officers; 365 enlisted; 60 Marines; 6,500 person evacuation limit

Power Plant: One 7,500+ Cochrane quantum induction core feeding two nacelles; 4 Class-VIII impulse fusion reaction chambers

Performance: 7,600 m/s² (sublight); Warp 9.2 (cruise); Warp 9.98 (maximum); Warp 9.9905 for 36 hours (burst); 120,000 TSL (quantum slipstream)

Armament: 6 Type-14 heavy phaser arrays; 25 Type-12 phaser arrays; 1 Class-VIIa rapid-fire torpedo turret; 4 Class-VI burst-fire torpedo launchers; 900 quantum torpedoes; 20 transphasic torpedoes; 4 Arc Light long-range ambush missiles

Defenses: Regenerative shields (8.1 exajoules); Polarizing reactive armor (4.0 centimeters)

Notice: This technical manual is intended for general informational purposes only, and not as a primary reference for Engineering operations. Information contained within this document may be subject to Starfleet Intelligence regulations, according to Section INTEC 34-5G. Any data contained herein may have been altered or fabricated to confuse and confound current and potential Threat intelligence operations. Starfleet personnel should consult their superior officers to obtain any classified information cleared for their security level.