USS Enterprise
USS Enterprise
Registry NX-1701-G
Class Enterprise
Affiliation United Federation of Planets - Starfleet
Assignment Battle Group Omega
Location New Vulcan, Beta Quadrant
Commander Admiral Greg Coulson
Home Port Spacedock
Mission Support Vessel USS Spock
Status PC

The USS Enterprise is an Enterprise Class Command Battleship that was launched in 2409.


Development of the Enterprise Class was primarily a result of the offensive encounters with the Dominion, Cardassian Union, and Borg Collective of the previous decades and the growing rise of hostilities throughout the Alpha and Beta Quadrants. Designed to be the next generation explorer and battleship, the Enterprise Class Development Project officially began work in early 2395; however, its origins could be traced back to shortly after the Battle of Wolf 359 and the First Battle of Sector 001 where the Federation faced off against the Borg. Despite the fact that a design had not been considered or any direct work had been conducted on the vessel at that time, the discussions calling for a larger ship of this type were running rampant throughout the Federation’s Engineering divisions and got the ball rolling upon development upon such a craft for the future. For the time being, however, Starfleet was contented with the already completed starships serving in the Federation Fleet which made Starfleet’s necessity for the Enterprise Class nothing more than discussions in the backrooms of Development Centers and the subject of theoretical papers in Engineering Courses and Conferences. Another blow to the project came when the Romulan Star Empire’s homeworld of Romulus was destroyed by the Hobus Stellar Event. With much of Starfleet’s resources devoted to helping the fracturing Romulan Star Empire to survive and dealing with the growing risks from the Klingon Empire (who opposed the Federation aiding a race that they were engaged in open war with), Starfleet held off on instituting such a major project in order to focus on tried and true designs. Despite Enterprise not coming to fruition then, as said above, it did get the ball rolling on the development of this class of ship as these early thoughts were the start of something truly amazing.

With the growing galactic dangers the Federation sponsored peace talks between the Klingons, Romulans, Gorn and Orions in effort to create a truce in the splintering Beta Quadrant. Unfortunately, these talks failed with gave birth to the Enterprise Project in 2395. Surprisingly each of the proposed designs abandoned the feel of the past for the more modern designs of the present day with a focus on making the Enterprise resemble the current generation of escort type vessels. Starfleet Command wanted a ship highly reminiscent of the durable nature of the previous generations (such as the Constitution and Excelsior Classes of the 23rd Century); nonetheless, each of the proposals lacked that grace and ignored the legacy that the Federation was trying to maintain. In a sense, Starfleet wanted a ship that was as much a work of art as it was a means of representing the Federation and its storied history in the galaxy. When no real design brief came to them reflecting this design, Starfleet Command fully considered scrapping the entire project. Reports also grew stressing that, in a military sense, the Enterprise was an impractical design because smaller ships could just as easily fulfill Enterprise's mission duties. With the prospect of war with the Klingon Empire intensifying it was believed by the top advisors of Starfleet that the Enterprise's resources should be used to produce more smaller craft instead of one massive one. It was almost a fluke that a design was chosen when it was. Ensign William Teagarden, on his first assignment at Utopia Planitia Fleet Yard after graduation from Starfleet Academy, responded to a design brief for a small exploration craft intended to replace the Intrepid Class Light Explorer. Named the Pennsylvania Class, in honor of his family's ancestral homeland, this design was rejected for the exploration role; however, it was forwarded by Commodore T’Mok to the review board working on the Enterprise for their consideration. Starfleet Command was impressed by the design and could see traces of Starfleet's ancestry among the proposed schematics provided. Modifications were soon made to the design in order to allow the ship to meet all mission requirements set forth in the development brief for the Enterprise. The size of the ship was also increased - after some consideration to keep the ship in the smaller stature of the Pennsylvania - to meet the size requirements set forth by Command. The decision to make the Enterprise a large vessel was entirely political in origin as Starfleet Command and the Admiralty believed that the Federation Flagship should be the largest vessel of the Federation's line of craft in order to serve as the representative of the Federation's power, strength, and status among the galactic powers. With the support of the Federation Council and the approval of the designer, Starfleet Command authorized and began construction of the craft in 2396 with proposed completion of the construction by 2421. This met the Federation's time table as they felt that the Century Class USS Enterprise-F would be nearing retirement from active service as Federation Flagship by that time.

Because of the secrecy involved in the Enterprise Class Development Project, construction of the Starship was conducted at multiple facilities throughout the Federation under heavy security patrol. Originally Enterprise was to have been constructed entirely at Starfleet’s San Francisco Yards - a tip of the hat to the site of the construction of the first Federation vessel to hold the name Enterprise - but the ship’s design proved to be too complex for construction to be attempted entirely at 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 construction), Jupiter Station (Starboard Warp Nacelle construction), and McKinley Station (Port Warp Nacelle construction). It was decided to complete as much of the Enterprise in the Sol System as possible as to avoid risks of Enterprise being detected by external forces and to make it easier on the construction teams when final assembly was to take place.

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) with its present configuration. 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 to defend the ship when she was standing in for the Federation in hotspots, but her engines and sensor systems were to be equally as impressive and powerful so that she could be effective in her exploratory duties. 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 industrial replicator units were built and installed in the drydocks used for Enterprise's construction. While a common feature to produce small goods for over a generation, replicator technology was inefficient until this time in producing large scale items. Thanks to this breakthrough what was originally predicted to take 25 years to build would now take only half that time to complete. Nevertheless, the incredible cost to fund the construction of such a large ship would practically bankrupt several star systems if the project was deemed a failure so great care was essential.

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 in the 23rd Century). 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 (Harriman 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 Oakland Shipyard used to refit the NX-01 and the building of Nacelle 2 (codenamed Shon) began at Tranquility Base (which was used for construction of the NCC-1701-F). These new nacelles 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 Separated Flight Mode. Suffice it to say the creation of this Project was met with multiple delays caused by the continued changes required to build the starship.

The first delay came while construction was underway on the Enterprise’s Stardrive. A load of Duranium Alloy was lost while underway from the Qualor System (reports indicated that Nausicaan Pirates attacked the Convoy but these reports remain unconfirmed). With the loss of the alloy, the Corp of Engineers lost out on a full six month’s work. While a six month delay may seem relatively inconsequential, the delay would destabilize the entire time table on a project that's development was highly controversial among even the men and women that approved it. 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 causing structural damage to occur along the nacelle's superstructure. 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 with their counterparts (they were behind schedule by a little under three months).

Shortly after the completion of both Nacelles they were towed from their construction facilities to Utopia Planitia to be placed on standby while the Stardrive underwent the final construction phase. Once the Stardrive was completed the connection of the two drive assemblies went as scheduled. The process was met with success as the three components attached without any major incidents. Sadly though, once connected, the power up of the nacelles wasn’t as by the book as was hoped by the engineers. The new nacelles and drive systems proved to be too advanced for the Warp Drive design that had been installed aboard the ship. With all systems online this had the unfortunate side effect of causing several systems to burnout from receiving too much energy and several blackouts aboard the Stardrive of the craft to compensate for the heavy power demand aboard the Enterprise. When components Archer and Shon were attached to component Kirk the same happened again. Analysis of the data provided by the Enterprise's computers, the construction yards, and sensor scans revealed several conflicting results. Nevertheless, the problem resulted in the core assembly design having to be returned to the Theoretical Propulsion Group for complete redesign in effort to develop a new power core for the Federation's new command ship (the design of the core itself, however, was a success when attached to smaller vessels and it was soon employed in several new starship designs and refits so the work was not a total loss). Their experiments would further delay construction by months while their simulations and development of theories had to be conducted - not to mention they needed to build two new prototype engine cores. Nevertheless, this caused significant concern for Starfleet Command to the point that a hearing was convened to end work on the Enterprise immediately in favor of other designs. During the final days of the hearing - with only one of the polled judges saying he was voting in favor of the Enterprise's construction to be continued - word was received that the Klingon Empire had conquered the Gorn Hegemony. In an instant the poll changed. The Admirals assigned to the review board immediately approved work to continue on Enterprise in order to have a new vessel capable of defending the Federation against the growing Klingon threat.

While work was being conducted by the Theoretical Propulsion Group, construction continued on Enterprise herself in the hopes of getting the physical structure ahead to compensate for the system based delays. The experimental Navigational Deflectors (both Main and Secondary) and Long Range Sensor Telescopes were the next components to be installed in the structure. Interestingly these installation procedures were straightforward; unfortunately though testing of these technologies couldn’t be conducted until Enterprise’s Power Systems were installed and online. Computer Systems were also installed around this time and assisted in sharing command and control roles aboard the different sections (decreasing the workload on the overtaxed computers of the drydocks as they could not compensate due to the massive amounts of data processed by the starship). 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). It was believed that, through the experimental positronic computer systems, the Enterprise would be able to accomplish complex calculations that had overtaxed other vessels with only a fraction of its computational abilities employed and no disruptions to system efficiency.

It was hoped that the sheer size of the ship would serve as sufficient means to frighten an opponent into submission (much like Romulan ships were designed to strike fear into opponents); although, Starfleet knew the truth that this would not always work to stop opponents from attacking. As work was being finalized on the Power Cores for the Enterprise, the ship's massive weapons arrays were put into place along the main hull. Featuring several different types of Phaser Arrays and even turrets, Enterprise would have a wide variety of tactical components at its discretion for defense. Included in this was the attachment of several incredibly powerful phaser cannons that previously could only be utilized on stationary facilities or planetary bases due to their power demands. The Torpedo Launchers were added around this point to their respective positions along the outer hull of the starship. While the defensive capabilities of the Enterprise were important, for political and diplomatic reasons Starfleet Command had decided that they didn't want to outright display to potential enemies that the Enterprise was overly outfitted for combat operations and performance. Hull components were constructed to sit flush with the outer skin of the hull and would serve to hide the weapons that were in the compartment below from view. In the event that a weapon was needed, these doors would slide out of place and reveal these weapons to allow their usage in combat. When the threat had been neutralized they would be covered (it is important to note that not all of the Enterprise's weapons are hidden in such a manner and the hidden weapons do not have to be employed in all engagements).

Once an acceptable power system was developed, it was quickly attached to Enterprise for use and testing. The Saucer Module, while undergoing testing with all currently installed systems online, featured a power surplus; the Stardrive didn’t share that luxury and had a shortage of energy. Compounding this issue the Engineers had not yet installed all of the Enterprise’s essential components and systems aboard the ship. The Shields - which consumed the most power of all - were still not aboard the ship and the sensor pallets - another draining component - had just begun to be attached to the hull assembly. This created severe problems and derailed all of the current work on the ship in order to mend this problem. While work did continue on attaching these vital components, the Theoretical Propulsion Group was forced to return to their drawing board once more to create a new power system. At this point, seven years had passed in Enterprise’s now thirteen year development schedule and many Admirals felt that the Engineers were cutting things far too closely for their comfort. Political pressures were also coming to play as a change in military policy within the Federation Council had begun to cut back Starfleet's resources to dangerous levels. Many in both the administration and Starfleet Command quickly came to the belief that the Enterprise wasn't worth the resources being diverted to it as it was costing them more capable craft. It was growing more likely that Starfleet would scrap the project if these problems persisted, salvage the already used resources, and use the systems 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 using modern technology).

Despite these threats, work continued (though with greater scrutiny) following the Klingon Empire staking claim to the Hromi Cluster and the surrounding sectors of space all of which were within Federation territory. With war essentially declared efforts to produce the Enterprise were doubled and the engineers were given express permission to take what time they needed to ensure that the Enterprise was ready for the galaxy it was entering as it would be the flagship against the Klingons. Enterprise’s new sensor arrays were the next mechanisms installed. The range and sensitivity of the sensors on the Enterprise had been greatly enhanced allowing the Enterprise to conduct detailed, long term research without significant impact to other shipboard operations. Several of the upgraded pallets, though, were created using substandard lenses in several of their instruments which could provide faulty readings during high resolution scans. This required the removal and reworking of these pieces of equipment in order to accommodate the Enterprise's mission profile as scan resolution was also determined to be slightly impaired during standard scans. 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 inserted to the key points along the outer hull. At this point the necessities of the new propulsion system and energy generation core had become even more apparent. The Enterprise’s Shields, which operated by creating three different layers of protection and had built in redundancies to allow the replacement of lost shields even during combat, had taken all available energy upon activation. Making things far worse, the shields cut power to several areas - including the weapon systems - during battle and catastrophe simulations making the Enterprise lose its spaceworthiness in the blink of an eye.

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, the Slipstream would be able to provide all the power needed with a reserve. Up until this time, however, Starfleet Engineering had not been able to produce a functioning unit that could fit the needs of a large starship (so far produced units had been attached to smaller vessels only). This unit, if it worked, would be able to produce massive amounts of energy for the starship’s use and serve as a faster means of propulsion than conventional warp drive. Construction of three 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 vital component. The designer of the Pennsylvania Project - 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 the development process. The Quantum Slipstream, however, underwent several diagnostic tests based upon the telemetry 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 that 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 and above anticipated parameters. It was a freak accident that no one could have anticipated. Some changes were made to Enterprise's spaceframe in order to support the addition of this new propulsion system, and Enterprise was ready for final construction procedures shortly afterward.

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 automated repair systems Starfleet Engineering and Sciences had reverse engineered from a captured Dominion Battlecruiser. 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, the Enterprise's Communications Array would be capable of reaching distances beyond even the most advanced communications satellites and, as needed, would even able to process communications to relieve stresses placed on neighboring communications relay stations and distribute them to their receiving stations. Construction was completed in 2409, ironically, on the same day that the Klingon Empire declared war on the United Federation of Planets and its allies.

Despite not being officially commissioned and not having completed a shakedown cruise, the Enterprise was deployed on several missions along the Klingon frontier in 2409 under the command of Captain William Teagarden – against the recommendations of several of the Federation’s senior military advisors and officers. Starfleet felt that, despite his service record, Captain Teagarden was not a suitable choice to command the Federation Flagship and that the Enterprise was too vital a piece of technology to risk without extensive testing. These missions were designed to put the Enterprise through its paces and it faced, on more than one occasion, extreme odds that would destroy lesser vessels - including an encounter with a remnant of the Borg Collective that had mysteriously been reactivated. Starfleet Command, despite earlier reservations, was impressed by how the Enterprise handled herself in combat against a superior force and, specifically, how Captain Teagarden handled himself. Orders were immediately signed that Captain Teagarden was to be promoted to Commodore and the Enterprise christened as Federation Flagship effective immediately.

Enterprise was officially launched in 2410 on a one year shakedown cruise under the command of William Teagarden (despite having already been rigorously tested in extreme combat scenarios). Unfortunately, Enterprise went missing during her first mission in an accident in the Badlands. A thorough investigation of the region revealed no traces of the Federation's latest flagship and it was listed as destroyed in action while investigating a believed to be rogue Jem'Hadar base – the exact details of the Enterprise’s mission remain classified to this day. Enterprise wasn’t as destroyed as many believed it to be and had remained surprisingly intact. Enterprise was recovered in 2412 by a deep salvage team and taken to Starbase 375 for analysis. Somehow it had survived the impossible, but it was listed for scrapping due to its damage from years adrift in the plasma fields and because the Klingon War had ended. While the Enterprise's crew were learning their fate, Deep Space Eight was destroyed by enemy forces. Starfleet Command decided to keep the Enterprise in use and ordered her immediate repair. Many of the components used in her construction were still in the experimental stages; however, many vessels had tested these systems through the years since Enterprise went missing. All systems were upgraded based upon data taken from these other vessels that were utilizing Enterprise's experimental technologies. With much fanfare the Enterprise was relaunched into the galaxy where it remained under the command of William Teagarden.

During the T'Saz wars the Enterprise led Starfleet forces into battle in many desperate engagements. During Enterprise's trial by fire she proved herself to have met each and every one of Starfleet's goals for members of this line of vessel. Further, many new technologies emerged that were soon to be employed in the Enterprise herself - some of which were designed by the Enterprise's own staff to handled the unique challenges that the ship faced on a daily basis. A full artificial intelligence was installed and activated to help coordinate Enterprise's systems, enhanced targeting systems were built into the ship's computers, and a new docking facility was built into the underside of the saucer module to allow smaller craft to dock with the ship. A full time mission support ship was also attached to the Enterprise and authorized to replace the Commanding Officer's personal transport ship that had been lost in a previous engagement against the T'Saz. The Enterprise continued to serve with distinction throughout Federation space on missions that would destroy lesser ships. For all intents and purposes Enterprise has proven herself to be a success; although, Starfleet Command has opted not to produce any more vessels of the class. As predicted the incredible cost to fund the construction of the Enterprise had practically bankrupted several star systems and cost significant resources that could have been better spent on smaller, mission specific craft as argued by Starfleet Command several times during Enterprise's construction. In lieu of additional Enterprise Class Starships, the Federation has begun to focus efforts on the recently introduced Barrier Class Starship that features many of the same components of the Enterprise in a more cost effective package.

Following the signing of the Charter of the Federation Alliance after the Supremacy attacked the homeworlds of every major power in the Alpha Quadrant, Enterprise was reassigned to serve as the Flagship vessel of the new government and a further 4 vessels of the class were approved for construction. Enterprise has been assigned to a specialized mission of exploration under the direct orders of Starfleet Command and granted autonomy to represent the Federation as it seeks out new worlds and new civilizations. During one such mission the Enterprise came under attack from the Federation Starship USS Zeus, a Barrier Class Starship that had been captured by a previously unencountered offshoot of the Confederacy of Vulcan. The Enterprise was severely damaged during the engagement and was nearly destroyed by the Zeus. With main power offline, hull integrity at 12%, and little chance for survival the Enterprise crew prepared to abandon ship. However, at the same time, an internal power struggle erupted on the Vulcan Colony and an ancient weapon discharged that destroyed the Zeus before it could eliminate the Enterprise. Starfleet Command dispatched the USS Resolute to tow the Enterprise to Earth where the New Federation Government would determine the fate of the Enterprise. Impressed by the ability of the Enterprise to withstand the onslaught and survive, Starfleet Command approved the request to repair the Enterprise. In addition to this, due to the new technologies made available because of the New Federation Alliance, the Enterprise would undergo a full refit under the direction of her new Commanding Officer: Captain Kor.

Following a brief stint under the command of Captain Kor, the Enterprise was reassigned back to the command of Admiral William Teagarden and assigned to multiple missions of exploration. Three years into her five year mission, the Vaadwaur launched a renewed assault upon the galaxy utilizing enhanced vessels beyond the abilities of even the Enterprise. Enterprise was assigned to lead a Starfleet contingent against the flagship of the Vaadwaur invasion fleet; however, the Enterprise was diverted at the last moment and assumed command over a small task group that began investigating the source of the Vaadwaur's enhanced equipment. The team was able to trace the source to the Typhon Sector and found that the Vaadwaur had captured an ancient installation known as the Foundry. With the combined strength of the Federation Fleet attacking the base, an away team was able to infiltrate the base and attack the leader of the Vaadwaur Fleet. Nevertheless, the battle did not go without loss. Admiral William Teagarden was killed in the process and the Enterprise was severely damaged and presumed destroyed in the attack.

Reborn at Gateway Station, the Enterprise underwent significant repairs and upgrades while docked at the station. In addition to receiving upgrades including a prototype Coaxial Warp Drive, the Enterprise was reunited with her former Commanding Officer William Teagarden. The Enterprise was launched on a new five year mission of exploration in the Beta Quadrant a short time afterward. The Enterprise would soon find itself embroiled in another ancient mystery when the vessel uncovered a Preserver outpost. A lone survivor awoke during the Enterprise's investigation and launched himself on a lone mission to destroy the Federation at Earth. Enterprise pursued and was transported back in time to the year 2012. Working together, the Enterprise and her crew were able to stop the attack and save the Human race. After two years Admiral Teagarden reassigned his entire Senior Staff and took the Enterprise on a mission to the center of the galaxy to recover the USS Gettysburg and its crew following a mission that released a dangerous entity upon the galaxy. Distressed at the loss of his fiancé, Captain Lynz, Admiral Teagarden resigned from Starfleet and command of the Enterprise transferred to her Executive Officer: Commander Asa Tisdura.

Following the death of Captain Tisdura while investigating a Section 31 outpost, Enterprise was assigned to the command of the recently recovered Captain Lynz. Admiral Teagarden transferred his flag to Enterprise a short time later to be with his wife. A year later the Enterprise responded to an investigation into the mysterious death of Admiral Daniel Teagarden. The investigation led the Enterprise to the Maelstrom Sector, where it came into direct conflict with the Cardassian Union. Raiding a Cardassian Outpost known as Vlulyr Tuok, it was discovered that the Cardassian Union had entered into an agreement with a rogue Starfleet Intelligence Operative known as 47. Having captured the USS Ark Royal, the conflict led to the Enterprise being severely damaged in combat and having to be rescued by the USS Bismarck. Returned to Sol Sector for repairs, Admiral Teagarden was temporarily reassigned to Starfleet Headquarters while Captain Lynz was reassigned to Spacedock.

The Enterprise continues undergoing repair at San Francisco Yards with plans for Admiral Teagarden to return to command in late 2427. These plans were altered when Admiral Teagarden was promoted to Commanding Officer of Starfleet Headquarters. Starfleet has announced plans for Admiral Lynz to assume command of the Enterprise as she begins a patrol of the Sol Sector. With the announcement that the Klingon Empire and the Romulan Star Empire had entered into a new alliance, President Gruzy announced that Starfleet would resume exploration of the galaxy with the development of the Starfleet Expeditionary Group. Enterprise was selected to serve as Starfleet One under the orders of the President with Admiral William Teagarden once again in command.

Following the degradation of relations between the Federation and Klingon Empire in 2428 the Enterprise was reassigned to the command of Admiral Greg Coulson when Admiral Teagarden was made Federation Ambassador to the Klingon Empire. While investigating an unprovoked attack on Betazed by an unknown party the Enterprise was disabled and had to be towed to drydock for emergency repairs. It has been relaunched and has resumed service as Starfleet One under Admiral Coulson.

Crew Manifest



  • Chief Engineering Officer: Commander Hwiii ih'iie-uUlak!ha' (Dolphin/Male)
    • Assistant Chief Engineering Officer: Lieutenant Dillon Herrera (Human/Male)
  • Chief Flight Control Officer: Lieutenant Thrus'Helm Sarbin (Andorian/Male)
    • Alpha Watch Flight Control Officer: Lieutenant Avir Yavan (NPC) (Angosian/Female)
  • Chief Operations Officer: Commander Nathan Bishop (Human/Male)


  • Chief Counseling Officer: Lieutenant Commander Victoria Rigby (Human/Female)
  • Chief Medical Officer: Commander Sherwin Porter, MD (Betazoid/Human/Male)
  • Chief Science Officer: Lieutenant Commander Carla Green (Human/Female)


  • Chief Security/Tactical Officer: Lieutenant Commander Jasmine Haynes (Human/Female)
  • Chief Strategic Operations Officer: Commander Nathan Hawkins (Human/Male)

See Also

Real World

The Enterprise Class was originally created as the Venture Class by madeinjapan1988. Conversion of the model to Star Trek Bridge Commander was completed by Cliperkins. Images of the Enterprise Class were created by AdmiralTeagarden.


Star Trek and all related marks, logos and characters are solely owned by CBS Studios Inc. This fan production is not endorsed by, sponsored by, nor affiliated with CBS, Paramount Pictures, or any other Star Trek franchise, and is a non-commercial fan-made production intended for recreational use. No commercial exhibition or distribution is permitted. No alleged independent rights will be asserted against CBS or Paramount Pictures.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License