Username:
Password:


Nebula Class Exploratory Cruiser
Expected Duration: 120 years
Time Between Resupply: 4 years
Time Between Refit: 6 years

Personnel
Officers: 180
Enlisted Crew: 600
Passengers: 110
Maximum Capacity: 8000

Speed
Cruising Velocity: Warp 6
Maximum Velocity: Warp 9
Emergency Velocity: Warp 9.8 (for 12 hours)

Dimensions
Length: 442.23 meters
Width: 470 meters
Height: 133 meters
Decks: 35

Auxiliary Craft
Shuttlebays: 2

Runabouts
Captains Yacht - Mk1: 1
Danube Runabout: 3 (USS Nipur, USS Susa, USS Umma)
Talon Scout: 2

Shuttles
Hunley Shuttle: 1
Type 11 Shuttle: 2
Type 9 Shuttle: 3
Type 8 Shuttle: 8

Transports
Argo Transport: 1

Armament

Phasers
Type X Array: 8

Defensive Systems
  Structural Integrity Field

Shielding Systems
  Auto-Modulating Shields
  Metaphasic Shielding
  EM Dispersal Field
  Standard Shielding System

Torpedoes
Burst-Fire Torpedo Launcher: 2
Quantum Torpedoes: 80
Photon Torpedoes: 220

Description
The Nebula carries a changeable mission pod that can be changed out during a layover at a starbase. The swap-out between pods takes beteeen 72 hours and 3 weeks depending on the types of pods involved. It takes the longest to change between the Sensor Pod and any of the other pod designs due to the difference in pod mounting components.

Description of Mission Pod Specifications

Between missions COs may dock their ship at a starbase to change pods. This is done to provide greater flexibility in the range of Nebula Class missions. The default pod that Nebula Class starships in Horizon Fleet carry is the Tactical Pod.

Sensor Pod: This pod contains multiple long-range sensor pallets, greatly increasing the ship's sensor range. This was the first pod designed for the Nebula Class and has significantly different mounting structure compared to the other pods. The USS Babylon is typically equipped with the Sensor pod.

Weapons Pod: This pod design was commissioned during the Dominion War after a rapid development during the Klingon Conflict instigated by changeling infiltrators. This pod carries 5 forward and 3 aft pulse-fire torpedo launchers with a payload of 200 photon and 100 quantum torpedoes. This pod also mounts 2 Type XII phaser arrays.

Tactical Pod: This pod was the 2nd pod developed for the Nebula class, going into service just prior to the Klingon Civil War. This first ship outfitted with the Pod was the USS Sutherland. After the initial wrinkles were worked out of the design, this pod quickly became the standard mounted pod for most Nebula Class ships. The Tactical Pod carries 3 burst-fire torpedo launchers (2 fore, 1 aft) with 150 photon and 75 quantum torpedoes. It also mounts sensor pallets to aid in the aiming and targeting of the pod's torpedo launchers.

Hospital Pod: This pod is not often used, but is kept on hand at major starbases for medical relief missions. THe Hospital Pod contains a full medical facility of starbase size and quality and has the capacity to house nearly 100 medical personnel and up to 600 patients.

Habitation Pod: This pod is used for colony or troop transportation and, depending on configuration, can carry up to 3000 colonists or 5000 troops with full equipment for a 90 day deployment. This pod also carries several high-capacity personnel transporters and a hangar bay with capacity for up to 10 craft, depending on craft types.

Hangar Pod: This pod is essentially a large hangar bay and servicing facilities. The standard craft load is:
12 Avenger class Interceptors
12 Mustang Class Space Superiority Fighters
10 Runabouts, various classes

SHIPS HISTORY

The USS Babylon was originally built at the San Francisco Fleetyard in 2358. Her first Commanding Officer was a Commander Louis Armstrong and was launched with a full compliment of crew in 2359. One of the first Nebula Class vessels to be built, the Babylon was originally intended to be a support vessel for the Galaxy class line of starships being built in tandem but Starfleet command quickly recognized the value of the class as a stand alone platform. As such, the Babylon was deployed on a five year mission of exploration in 2360, charting courses in Beta quadrant.

In 2367, the USS Babylon then under the command of Captain Farra Talell, narrowly missed destruction at Wolf 359 due to an engine malfunction that caused her to have to lag behind the fleet she was supporting. The fleet, one of many attempting to halt the Borg's advancement toward Earth, consisted of 14 Federation ships which during the engagement were summarily destroyed. Captain Talell retired following this incident.

2370 saw the USS Babylon deep in unexplored Federation space where she was sent on a second 5 year mission to search out new life and new civilisations - commanded by Captain David Taggart. Recalled shortly after the start of the Dominion war, the Babylon didn't arrive back in Federation space until mid 2375. Having missed the first half of the war the Babylon nearly made it through the conflict unmolested. The ship's high point came at the second battle of Chin'toka where as part of a reserve force held at the edge of the system the Babylon was able to retrieve dozens of escape pods after the devastating engagement, saving the lives of nearly 2500 stranded crewmen. After several flawless engagements the luck of the Babylon and her crew ran out at the battle of Cardassia where at the last engagement of the war she was critically damaged. Afterwards the Babylon was ferried to drydock at Utopia Planita where she remained until 2385.

An ageing and very sick Admiral Fredrickson (who was at the first launch of the Babylon) was visiting the Fleetyard and saw the Babylon gathering dust. It was at his request that she be brought back to life and after a six month restoration project the USS Babylon was sent to Starbase 129 for a complete update of its systems. Admiral Fredrickson died before the repairs were complete.