ENTERPRISE CLASS

The Enterprise Class Development Project is one of several designs that has been developed to serve as the next generation exploration platform of the Federation�s Starfleet. The initial design briefings called for a large vessel, the largest yet to be produced, capable of performing long term exploration assignments on behalf of Starfleet, while providing a Federation presence in galactic hotspots. This would result in starships of this class becoming one of Starfleet�s most prominent designs for the near future.

Due to the size and nature of Enterprise�s mission it was very difficult to construct. Requiring two separate drydock construction facilities at San Francisco Yard, this ship when completed would be two and a half times the size of a Galaxy Class Starship and nearly 4 times stronger than the Federation�s Excalibur Class Explorer. Defense would be a paramount issue for this new vessel as well. The Enterprise Class Development Project would call upon creation of the most advanced shielding and power systems ever produced for a mobile platform (the systems would even have to prove better than those used on some frontline outposts).

The initial designs for the Enterprise highlighted the militaristic nature of the ship more than relying on the design ethic of the past. The initial concepts were little more than beefed up Defiant Class Starships with more weaponry. Several experienced officers worked on development of this Project, but - shockingly - the final design for the Enterprise didn�t come from one of the many Engineers that Starfleet had assigned to this project. The final design came from an Ensign on his first assignment in service of Starfleet and was originally intended to be a galactic exploration craft. What was once to be called the Pennsylvania Class was quickly altered to become the Enterprise Class Development Project. The designs were reworked under the direction of their designer and were brought to the standards of design that Starfleet was seeking for their new Starship Enterprise.

Combining all of the latest developments in Federation technology, it was predicted that Enterprise would become one of Starfleet�s most effective designs since the Constitution Class.

CONSTRUCTION HISTORY

Unfortunately, as also stated above, when work finally began the designs abandoned the feel of the past for the more modern designs of the day. Starfleet Command wanted a ship highly reminiscent of the durable nature of the previous generations (the Constellation, Constitution, Excelsior, and Miranda Class vessels of the 23rd Century). When no real design brief came to them reflecting this design, Starfleet fully considered scrapping the entire project with every intention of building smaller, single role craft to fill these roles. It was almost a fluke that a design was chosen when it was. Ensign William Teagarden, on his first assignment at Utopia Planetia Fleet Yard, responded to a design brief for a small exploration craft. Named the Pennsylvania Class, this design was rejected for the Exploration role; however, it was forwarded by Commodore T�Son�a of Starfleet�s Corp of Engineers to the review board. Beefed up to meet their requirements for the Enterprise the design was selected for their use.

Because of the secrecy involved in the Enterprise Class Development Project, construction of the Starship was conducted at multiple facilities throughout the Federation. Originally Enterprise was to have been constructed specifically at Starfleet�s San Francisco Yards - a tip of the hat to the site of the construction of the first Federation vessel to be named Enterprise - but the ship�s design proved to be too complex to be attempted at only one facility. Because of this Starfleet�s Corp of Engineers had to make available an additional three drydock facilities throughout the Federation for construction purposes; resulting in the cancellation of construction of three additional starships. Besides the site at San Francisco Yards (Saucer Construction), work was also conducted at Utopia Planetia (Stardrive), Jupiter Station (Starboard Warp Nacelle), and McKinley Station (Port Warp Nacelle).

As a prototype starship class, the Corp of Engineers unfortunately suffered from attempting to place far too many systems in the Enterprise than it was capable of handling (essentially they put too many eggs into one basket). Starfleet had attempted to create a vessel that shared two contrasting primary mission roles and many difficulties resulted from their attempts. Enterprise had a great deal of weapons and defensive systems, but her engines and sensor systems were to be equally as impressive. Many of the components themselves were still in the development stages when they were tapped for use in the ship�s construction. However, one benefit that had been discovered recently, was the development of a new type of construction technology. Unused as of yet in construction purposes, large replicator units were built and installed in the drydocks used for Enterprise construction. What was originally predicted to take 20 years to build would now take only half that time to complete.

Construction began almost immediately under several different aliases. The Saucer Module was given the codename Kirk and was assigned to Drydock DD-014 (which is the refitted unit that was used to create the Enterprise NCC-1701). The Stardrive was constructed at Utopia Planetia under the codename Picard (in Drydock DD-192, the same one used for creation of the Enterprise NCC-1701-D). The Nacelles were given the names Harriman and Garrett (Archer was constructed at the Jupiter Station Yard responsible for the NCC-1701-B, Garrett at the McKinley Station yard responsible for the creation of the Enterprise NCC-1701-C). When it was suggested attaching smaller warp capable sleds for Saucer use while separated, creation of Saucer Nacelle 1 (codenamed Archer) began at the San Francisco Yard used for creation of the NX-01, and Nacelle 2 (codenamed Teagarden) began at the San Francisco Yard used for construction of the NCC-1701-F). These would not be constantly exposed though and some minor changes were made to the Saucer module�s design to support their being swung out of the main hull and into place when needed for use during Multi Vector Assault Mode. Suffice it to say the creation of this Project was met with multiple delays.

The first delay came while construction was underway for Enterprise�s Stardrive. A load of Duranium Alloy was lost while underway from the Qualor System (reports indicated that Orion Pirates attacked the Convoy but these remain unconfirmed). With the loss of the alloy, the Corp of Engineers lost out on a full month�s work. The delay, even though short, would destabilize the entire time table.

Later more delays would crop up with the Warp Nacelles. Substandard composite was used in the creation of the warp coils on Harriman and, while undergoing power up procedures while attached to the drydock, the coils blew out and structural damage occurred. Work to repair those components resulted in a delay of eight weeks, but this was - oddly - of little consequence to the timeline of development. The Nacelle named Harriman was ahead of schedule and this provided time for the workers on Garrett to catch up (which was behind schedule by three months).

Shortly after the completion of both Nacelles they were towed from their construction facilities to Utopia Planetia to be placed on standby while the Stardrive underwent final construction. Once the Stardrive was completed the connection of the two drive assemblies went as scheduled. Sadly though, once connected, the power up of the nacelles wasn�t as by the book as hoped. The new nacelles and drive systems proved to be too advanced for the Core design that had been installed and caused several system burnouts and blackouts aboard the Stardrive of the craft. The same problems appeared when Components Archer and Teagarden were attached to Component Kirk. The problem resulted in the core assembly design having to be returned to the Theoretical Propulsion Group. Their experiments would further delay construction by months while their simulations and development of theories had to be conducted.

While work was being conducted by the Theoretical Propulsion Group, construction continued on Enterprise herself. The experimental Navigational Deflectors (both Main and Secondary) and Long Range Sensor Telescopes were the next components to be installed. Interestingly these installation procedures were straightforward, unfortunately though testing of these technologies couldn�t be conducted until Enterprise�s Power Systems were installed. Computer Systems were also installed around this time and assisted in sharing command and control roles aboard the different sections. The Computer Core - a combination of Bioneural, Isolinear, and Positronic Computer Systems - would require ten separate cores in total to be effective. (Six are installed in the Saucer, Four in the Stardrive).

As work was being finalized on the Power Cores for the Enterprise, the ships massive weapons arrays were put into place along the main hull. Featuring several different types of Phaser Arrays, Enterprise would have a wide variety of tactical components. Included in this was the attachment of two powerful phaser cannons. The Torpedo Launchers were added around this point to their respective positions along the outer hull. It is important to note that Enterprise�s weapons were designed to also be hidden from view to better conceal the war like nature of the Starship.

Once an acceptable power system was developed, it was quickly attached to Enterprise for use. The Saucer Module, while undergoing testing, featured a surplus of power available to it; the Stardrive didn�t share that luxury and had a shortage of energy. Compounding this problem was that not all of Enterprise�s essential components were installed. The Shields - which consumed the most power of all - were still not aboard and the sensor pallets - another draining component - were just being attached at the time. This created severe problems. While work continued on attaching these vital components, the Theoretical Propulsion Group returned to their drawing board once more. At this point, seven years had passed in Enterprise�s ten year development schedule. It was growing more likely that Starfleet would scrap the project if these problems persisted and use the metals in the construction of other craft (resource wise the materials used to create Enterprise could be easily reappropriated to constructing a minimum of ten Sovereign Class Explorers).

Despite these threats, work continued. Enterprise�s new sensor arrays were the next mechanisms installed. Several of the upgraded pallets though were created using substandard lenses in several of their instruments. This required their removal and reworking as well. While that work was being conducted, the Corp of Engineers installed the last of the essential components to defend the ship. The Enterprise�s shields were attached and instated. At this point the necessities of the new propulsion system and energy generation core had become even more necessary. The Enterprise�s Shields, which operated by creating three different layers, had taken all Energy available and cut power to several areas - including the weapon systems during battle and catastrophe simulations.

The Theoretical Propulsion Group had their answer though: the Quantum Slipstream Drive. Based upon an experimental technology brought back from the Delta Quadrant by the Starship Voyager, until this time Starfleet Engineering had not been able to produce a functioning unit. This unit, if it worked, would be able to produce massive amounts of energy for the starship�s use. Construction of two units was conducted and the first was attached to the Enterprise-F (this vessel�s predecessor) for testing. Sadly though this ship struck a Quantum Filament and was destroyed while testing this component. The designer of the Enterprise - who was Captain William Teagarden of the Enterprise-F - survived the destruction and was assigned to the Enterprise Development Project for the final stages of development. The Quantum Slipstream, however, underwent several diagnostic tests based upon the telemtry and sensor data made available before the NCC-1701-F was lost. It was the judgment of the Corp of Engineers, the Judge Advocate General's Office, and Starfleet Command that the Slipstream Core was not the cause of the Enterprise-F�s destruction and the destruction of the ship was not the result of negligence on the part of the Starship's Crew. Data suggested that the Slipstream was actually operating flawlessly at the time of the destruction. Some changes were made to support the addition of this new propulsion system, and Enterprise was ready for final construction procedures.

Support and Auxiliary systems were quickly installed utilizing the replication construction technology. One of the most ingenious additions was the inclusion of an automated repair system that was based upon the repair systems of the Alpha Series Starbase. Holographic emitters were also placed on every deck so that emergency medical holographic programs or holographic personnel could be permitted access to any location aboard the ship. The final component installed was the Enterprise�s advanced communications array (attached to the Long Range Sensor Antennae) capable of reaching distances beyond normal communications satellites and it was even able to process communications if necessary to relieve stresses placed on neighboring communications relay stations.

Enterprise was launched in 2410 on a one year shakedown cruise under the command of William Teagarden. Unfortunately, Enterprise went missing during her first mission in an accident in the Badlands. It was listed as destroyed in action; however, Enterprise really wasn�t as destroyed as many believed it to be. Enterprise was recovered in 2412 by a deep salvage team and taken to Starbase 375. It was listed for scrapping due to it�s damage; however, with the destruction of Deep Space Eight by enemy forces Enterprise was repaired and further upgraded based upon data taken from other vessels that were utilizing it�s experimental technologies. Several additional technologies which were under development at the time of it�s loss have been incorporated into the Enterprise�s refit. She is now once again exploring space as the Flagship of the Federation. She remains under the command of Fleet Admiral William Teagarden

NOTEWORTHY VESSELS

SPECIFICATIONS

Propulsion:

2 LF-75 Advanced Linear Warp Drive Units
2 LF-35 Linear Warp Drive Units (Separated use only)
1 FIG-11 Subatomic Unified Energy Impulse Unit
2 FIG-10 Subatomic Unified Energy Impulse Units
2 FIG-8 Subatomic Unified Energy Impulse Units (Emergency use only)
Reaction Control System Thruster Assemblies

Velocity:

Standard Cruising Velocity: Warp 7.0
Maximum Cruising Velocity: Warp 9.8
Maximum Attainable Velocity: Warp 9.999+ (Quantum Slipstream Velocity)

All stop to full impulse: 5.74 seconds
Full impulse to Warp 1: 1.4 seconds
Warp 1 to Warp 4: 2.8 seconds
Warp 4 to Warp 7: 3.5 seconds
Warp 7 to Warp 9: 4.7 seconds
Warp 9 to Warp 9.999+: 6.0 seconds

Phasers:

02 Type XX+ Heavy Phaser Cannon
05 Type XX Pulse Phaser Cannons
06 Type XIX Collimated Phaser Arrays
08 Type XVIII Collimated Phaser Arrays
20 Type XVIII Single Mount Phaser Banks (1 Bank/1 Mount) (Unexposed unless needed)
20 Type XVII Single Mount Phaser Banks (1 Bank/1 Mount) (Unexposed unless needed)

Torpedoes:

09 Mk 110 Burst Fire Torpedo Launchers
     (Phoenix/Quantum/Tachyon)
15 Mk 105 Direct Fire Torpedo Launchers
     (Phoenix/Photon/Quantum/Stratospheric/Tachyon/Transphasic/Tricobalt)

Special: Ablative Hull Armor, Saucer Separation Capability
Shields: FSS XXV Multiphasic/Regenerative Forcefield and Deflector Control System (PRIMARY), FSS-4 Primary Forcefield and Deflector Control System (SECONDARY)
Primary Computer System: Class XXV Bioneural/Isolinear hybrid computer core/LCARS Version 8.0
Primary Navigation System: RAV/ISHAK Mod 9 Warp Celestial Guidance
Primary Propulsion System: Type XXV Matter/Antimatter Warp/Quantum Slipstream Hybrid Propulsion Core
Secondary Propulsion System: Type XXV Matter/Antimatter Warp Propulsion Core

Embarked Craft:

Gunship (Various Classes): 10
Runabouts (Various Classes): 10
Scoutcraft (Einstein Class): 5
Shuttlecraft (Various Classes): 20
Shuttlepod (Various Classes): 15
Work Bee General Utility Craft: 8

The Enterprise Class starship was created by William Teagarden in early 2001 for use in his role playing game. Images of the Enterprise are based upon the Victory Class designed for Star Trek Bridge Commander by Queball. Specifications and history of the Enterprise Class are by William Teagarden. Image of the Enterprise is by William Teagarden.

Task Force 5 is based upon Star Trek created by Gene Roddenberry and is in no way affiliated with CBS Corporation, Paramount Pictures Corporation, or Viacom. Star Trek, Star Trek: The Next Generation, Star Trek: Deep Space 9, Star Trek: Voyager, Star Trek: Enterprise, and all related marks are registered trademarks of Paramount Pictures and their respective owners; no copyright violation is intended or desired.