Mercury Overview and Statistics

USS Mercury
INACTIVE STATUS
Menthar Corridor Astrofori One Menthar Anchorage Deep Space 10 Task Force 105 Invicta Expedition USS Invicta USS Garuda USS Tiger-A USS Syracuse Crew Roster Crew History Crew Awards Mission History 2389 · 2390 Officers' Mission Logs Mercury Technical Overview Deck Layout Auxiliary Craft Mercury Dedication Plaque Mercury Forums Mercury Google Group Mercury Sim Archive Mercury Yahoo! Archive Oracle class NCC-99812 Edit this nav

NOTE: The stats below represent the Mercury in her original launch condition. Following her recovery in 2391, the ship's capabilities were reevaluated by Starfleet, and she was refitted before being relaunched and sent back to the Menthar Corridor. Her uprated technical details have been classified.

The Oracle class starship is designed to be the cutting edge of scientific research and exploration. She is equipped to handle extended missions without the need to return to starbase for refuel or repair. The ventral section of the hull is host to a large sensor module, the next step in the evolution of the Nebula class sensor sail, and has been designed with a highly sensitive transpectral array for maximum sensitivity across a range of specifications. In many ways, this new sensor system was the focus of the ship’s design, making the Oracle class starship ideal for gathering and processing data on spatial anomalies, stellar cartography, and further in-depth scans of previously discovered worlds.

In the current galactic political climate, however, the sensitivity of the Oracle's sensor systems has not gone unnoticed by Starfleet’s Security and Intelligence departments. Enhanced range and clarity of sensor data provides an opportunity for an early-warning system in sensitive sectors, as well as the ideal scouting platform during emergency situations and inter-species conflicts. However, this is very much a secondary concern, and the Oracle class is built purely as a science vessel with limited offensive capabilities. Its six type-IX phasers are nothing more than standard issue, and the class is limited to two torpedo tubes, one fore and one aft, primarily designed for the launching of probes.

Mission Objectives

Pursuant to Starfleet Exploration Directives 1016.8 & 901.12, Federation Diplomatic Corps Mandate 66.105.b, 66.105.c & 200.2.2, and Federation Security Council General Policy, the following objectives have been established for an Oracle Class Starship:

• Provide a platform for extended scientific survey, scouting and exploration missions.
• Replace the Oberth for long range missions, stellar cartography, and detailed scientific study.
• Provide autonomous capability for full execution of Federation cultural, scientific, intelligence and explorative policy in deep space or border territory. Provide limited execution of Federation defensive policy in the same circumstances.
• Serve as a support vehicle during emergencies and a platform for the extension of Federation diplomacy and policy.
• Provide diplomatic support in border territories and, where necessary, work as the eyes and ears of a task force through use of the Oracle sensor module.

Design Statistics

• Length: 580 meters
• Width: 205 meters
• Height: 155 meters
• Cargo Capacity: Variable dependant on mission type; cargo bays customisable to transport volatile or unstable substances as required for scientific missions.
• Hull: Duranium/Tritanium composite
• Number of Decks: 30 Total
• Crew Complement: 500

DITL: Strength Calculator

• Affiliation: Federation Oracle Class
• Beam Weapon Output: 7500 TeraWatts (Six Type IX Phaser Emitters)
• Torpedo Tubes: 2 Pulse-fire Photon Torpedo Tubes
• Weapons Range/Accuracy: 350
• Shield Capacity: 900000 TeraJoules
• Hull/Armour: Standard Duranium/Tritanium Single Hull
• 1cm Anti-phaser coating armour
• Standard Structural Integrity Field
• Maximum Warp Factor: 9.97 (TNG)
• Combat Manoeuvrability: 9000
• Overall Strength: 494.025

Sensor Module

The sensor module, which comprises decks 24-30 of the Oracle class includes a considerable number of Scientific laboratories as well as the Oracle sensor array. While the module is not designed to be separated from the rest of the ship unless for major refits or overhauls, it can be sealed off in case of extreme quarantine procedure and, if ultimately necessary, jettisoned from the rest of the hull.

Tactical Systems

Phasers

• Phaser Array Arrangement: Dorsal saucer section is covered by four phaser strips; two of which are arranged in an arc along the forward section of the main hull, the other two in linear strips above the main arc. Two more emitters are located on the ventral section of the main hull, which extend further towards the aft of the ship to cover the aft firing arc.

Phaser Array Type: Unlike other contemporary starships such as the Sovereign- and Vesta-classes, which use the most recent Type-XII, the Oracle is equipped with Type-IX phaser emitters. Each array fires a steady beam of phaser energy, and the forced-focus emitters discharge the phasers at speeds approaching .986c (which works out to about 182,520 miles per second - nearly warp one). The phaser array automatically rotates phaser frequency and attempts to lock onto the frequency and phase of a threat vehicle's shields for shield penetration.

• Phaser Array Output: Each phaser array takes its energy directly from the impulse drive and auxiliary fusion generators. Individually, each Type-IX emitter can only discharge approximately 6.0 MW (megawatts). However, several emitters (usually two) fire at once in the array during standard firing procedures, resulting in a discharge approximately 12 MW.
• Phaser Array Range: Maximum effective range is 300,000 kilometers.
• Primary purpose: Drilling/Dispersion of asteroids
• Secondary purpose: Defense/Anti-Spacecraft

Torpedo Launchers

• Arrangement: Two pulse-fire torpedo launchers, One fore, and one aft. Torpedo tubes one is located on the fore section of the strut that connects the main hull to the sensor module, on deck 21; torpedo tube two is located on the aft section of the same deck. Designed primarily for a vehicle through which probes can be launched, the torpedo tubes are equipped with a pulse-fire function that allows small volleys of four photon torpedoes to be fired in one volley, although this comes with a three minute reload time.
• Type: Type-6, Mark-XXV photon torpedo, capable of pattern firing (sierra, etc.) as well as independent launch. Independent targeting once launched from the ship, detonation on contact unless otherwise directed by the ship. No quantum torpedoes are carried aboard, as these are unnecessary for scientific, diplomatic or even intelligence-based missions.
• Payload: The Oracle Class can carry a maximum of 60 torpedo casings with at least 20 of them geared as probe casings at any one time.
• Range: Maximum effective range is 3,500,000 kilometers.
• Primary purpose: Probes
• Secondary purpose: Anti-Spacecraft

Deflector Shields

• Type: Symmetrical occilating subspace graviton field. This type of shield is similar to those of most other starships. Other than incorporating the now mandatory nutational shift in frequency, the shields alter their graviton polarity to better deal with more powerful weapons and sophisticated weaponry (including Dominion, Breen, and Borg systems).

During combat, the shield sends data on what type of weapon is being used on it, and what frequency and phase the weapon uses. Once the tactical officer analyzes this, the shield can be configured to have the same frequency as the incoming weapon - but different nutation. This tactic dramatically increases shield efficiency.

• Output: There are 24 shield grids on the Oracle class and each one generates 37500TJ, resulting in total shield strength of 900000TJ. The power for the shields is taken directly from the warp engines and impulse fusion generators. If desired, the shields can be augmented by power from the impulse power plants. The shields can protect against approximately 42% of the total EM spectrum (whereas a Galaxy class Starship's shields can only protect against about 23%), made possible by the multi-phase graviton polarity flux technology incorporated into the shields.
• Range: The shields, when raised, maintain an average range is 30 meters away from the hull.
• Primary purpose: Defense from hazardous radiation and space-borne particulates.
• Secondary purpose: Defense from enemy threat forces

Propulsion Systems

Warp Propulsion System

• Type: Standard Matter/Antimatter Reaction Assembly (M/ARA)
• Normal Cruising Speed: Warp 7
• Maximum Cruising Speed: Warp 9.97 for 6 hours

The Oracle class has two nacelles, which are located at the aft section of the vessel and connected to the main hull by small horizontal pylons.

Impulse Propulsion System

• Type: Standard fusion-powered impulse engines. Full impulse is considered to be 0.25c (one quarter light speed)

Reaction Control System

• Type: Standard Version 3 magneto-hydrodynamic gas-fusion thrusters.
• Output: Each thruster quad can produce 3.9 million Newtons of exhaust.

Communications

• Standard Communications Range: 30,000 - 90,000 kilometers
• Standard Data Transmission Speed: 18.5 kiloquads per second
• Subspace Communications Speed: Warp 9.9997

Flight Operations

Operations aboard an Oracle Class starship fall under one of three categories: Flight Operations, Primary Mission Operations, or Secondary Mission Operations.

• Flight Operations are all operations that relate directly to the function of the starship itself, which include power generation, starship upkeep, environmental systems, and any other system that is maintained and used to keep the vessel space worthy.
• Primary Mission Operations entail all tasks assigned and directed from the Main Bridge, and typically require full control and discretion over ship navigation and ship's resources.
• Secondary Mission operations are those operations that are not under the direct control of the Main Bridge, but do not impact Primary Mission Operations. Some examples of secondary mission operations include long-range cultural, diplomatic, or scientific programs run by independent or semi-autonomous groups aboard the starship.

Mission Types

Seeking out new worlds and new civilizations is central to all that Starfleet stands for. The Oracle Class facilitates this, outfitted for long-duration missions over planets and systems, cataloguing and monitoring anything and everything of interest inside a designated area.

Mission for an Oracle Class starship may fall into one of the following categories, in order of her strongest capable mission parameter to her weakest mission parameter.

• Ongoing Scientific Investigation: An Oracle Class starship is equipped with scientific laboratories and a wide variety of sensor probes and sensor arrays, as well as the hi-tech sensor module; giving it the ability to perform a wide variety of ongoing scientific investigations.
• Gathering of Intelligence/Surveillance: An Oracle Class ship is capable of monitoring communications traffic and fleet placement at a greater distance than many other Starfleet vessels, and is an invaluable addition to Starfleet’s border patrols during times of uncertainty or high alert.
• Contact with Alien Lifeforms: Pursuant to Starfleet Policy regarding the discovery of new life, facilities aboard the Oracle Class include a variety of exobiology and xenobiological suites, and a cultural anthropology staff, allowing for deep-space life form study and interaction.
• Federation Policy and Diplomacy: An Oracle Class starship’s secondary role is the performance of diplomatic operations on behalf of Starfleet and the United Federation of Planets. These missions may include transport of Delegates, hosting of negotiations or conferences aboard in the vessel’s Conference Hall, courier for important people and/or items, and first contact scenarios.
• Emergency/Search and Rescue: Typical Missions include answering standard Federation emergency beacons, extraction of Federation or Non-Federation citizens in distress, retrieval of Federation or Non-Federation spacecraft in distress. The class’s relatively high top speed makes it a reliable option for hostile evacuations.

Operating Modes

The normal flight and mission operations of the Oracle Class starship are conducted in accordance with a variety of Starfleet standard operating rules, determined by the current operational state of the starship. These operational states are determined by the Commanding Officer, although in certain specific cases, the Computer can automatically adjust to a higher alert status. The major operating modes are:

• Cruise Mode - The normal operating condition of the ship.
• Yellow Alert - Designates a ship wide state of increased preparedness for possible crisis situations.
• Red Alert - Designates an actual state of emergency in which the ship or crew is endangered, immediately impending emergencies, or combat situations.
• External Support Mode - State of reduced activity that exists when a ship is docked at a starbase or other support facility.
• Reduced Power Mode - This protocol is invoked in case of a major failure in spacecraft power generation, in case of critical fuel shortage, or in the event that a tactical situation requires severe curtailment of onboard power generation.

During Cruise Mode, the ship’s operations are run on three 8-hour shifts designated Alpha, Beta, and Gamma. Should a crisis develop, it may revert to a four-shift system of six hours to keep crew fatigue down.

Typical Shift command is as follows:

• Alpha Shift – Captain (CO)
• Beta Shift – Executive Officer (XO)
• Gamma Shift – Second Officer (2XO)

Maintenance

Though much of a modern starship’s systems are automated, they do require regular maintenance and upgrade. Maintenance is typically the purview of the Engineering, but personnel from certain divisions that are more familiar with them can also maintain specific systems.

Maintenance of onboard systems is almost constant, and varies in severity. Everything from fixing a stubborn replicator, to realigning the Dilithium matrix is handled by technicians and engineers on a regular basis. Not all systems are checked centrally by Main Engineering; to do so would occupy too much computer time by routing every single process to one location. To alleviate that, systems are compartmentalized by deck and location for checking. Department heads are expected to run regular diagnostics of their own equipment and report anomalies to Engineering to be fixed.

Systems Diagnostics

All key operating systems and subsystems aboard the ship have a number of pre-programmed diagnostic software and procedures for use when actual or potential malfunctions are experienced. These various diagnostic protocols are generally classified into five different levels, each offering a different degree of crew verification of automated tests. Which type of diagnostic is used in a given situation will generally depend upon the criticality of a situation, and upon the amount of time available for the test procedures.

• Level 1 Diagnostic - This refers to the most comprehensive type of system diagnostic, which is normally conducted on ship's systems. Extensive automated diagnostic routines are performed, but a Level 1 diagnostic requires a team of crew members to physically verify operation of system mechanisms and to system readings, rather than depending on the automated programs, thereby guarding against possible malfunctions in self-testing hardware and software. Level 1 diagnostics on major systems can take several hours, and in many cases, the subject system must be taken off-line for all tests to be performed.

• Level 2 Diagnostic - This refers to a comprehensive system diagnostic protocol, which, like a Level 1, involves extensive automated routines, but requires crew verification of fewer operational elements. This yields a somewhat less reliable system analysis, but is a procedure that can be conducted in less than half the time of the more complex tests.

• Level 3 Diagnostic - This protocol is similar to Level 1 and 2 diagnostics but involves crew verification of only key mechanics and systems readings. Level 3 diagnostics are intended to be performed in ten minutes or less.

• Level 4 Diagnostic - This automated procedure is intended for use whenever trouble is suspected with a given system. This protocol is similar to Level 5, but involves more sophisticated batteries of automated diagnostics. For most systems, Level 4 diagnostics can be performed in less than 30 seconds.

• Level 5 Diagnostic - This automated procedure is intended for routine use to verify system performance. Level 5 diagnostics, which usually require less than 2.5 seconds, are typically performed on most systems on at least a daily basis, and are also performed during crisis situations when time and system resources are carefully managed.

Emergency Operations

Emergency Medical Operations

Pursuant to Starfleet General Policy and Starfleet Medical Emergency Operations, at least 25% of the officers and crew of the Oracle Class are cross-trained to serve as Emergency Medical Technicians, to serve as triage specialists, medics, and other emergency medical functions along with non-medical emergency operations in engineering or tactical departments. This set of policies was established due to the wide variety of emergencies, both medical and otherwise, that a Federation Starship could respond to on any given mission.

All of the cargo bays and some of the science labs (biological sciences) can be easily converted into emergency treatment wards or emergency triage centres and recovery overflow. Portable field emitters can be erected for contagion management.

Emergency Medical Hologram

Pursuant to new Medical Protocols, all Medical Facilities are equipped with holo-emitters for the emergency usage of the Emergency Medical Hologram System. Starships of this type carry the EMH Mark-II, with options to upgrade to new versions as they become available.

Lifeboats

Pods are located on decks below Deck 1. Each pod can support a total of eighty-six person-days (meaning, one person can last eighty-six days, two can last for forty-three, etc.). Two pods are reserved for the top four officers in the chain of command on the ship, because they are the last four to leave the ship. These are located on Deck 2. If the ship is abandoned, the top four officers in the chain of command will wait until everyone else is off the ship, opt to arm the auto-Destruct (not always necessary, but there if needed), and then leave in the two escape pods. In situations when the base vessel is not near a habitable system, up to four pods may be linked together in a chain at junction ports to share and extend resources.

Rescue and Evacuation Operations

Rescue and Evacuation Operations for an Oracle class starship will fall into one of two categories - abandoning the starship, or rescue and evacuation from a planetary body or another starship.

Rescue Scenarios

Resources are available for rescue and evacuation to Oracle class starship include:

• The ability to transport 760 persons per hour to the ship via personnel transporters.
• The availability of the four Type-9 shuttlecraft to be on hot standby for immediate launch, with all additional shuttlecraft available for launch at an hour’s notice. Total transport capabilities of these craft vary due to differing classifications but an average load of 50 persons can be offloaded per hour from a standard orbit to an M Class planetary surface.
• Capacity to support up to 750 evacuees with conversion of the shuttlebays and cargo bays to emergency living quarters.
• Ability to convert the Crew Lounge to an emergency triage and medical center.
• Ability to temporarily convert Cargo Bay 1, 2, 3 and 4 to type H, K, or L environments, intended for non-humanoid casualties.

Abandon-Ship Scenarios Resources available for abandon-ship scenarios from an Oracle class starship include:

• The ability to transport 750 persons per hour from the ship via personnel and emergency transporters.
• The availability of the 4 Type-9 shuttlecraft to be on hot standby for immediate launch, with all additional craft available for launch at an hour’s notice. Total transport capabilities of these craft vary due to differing classifications but an average load of 50 persons can be offloaded per hour from a standard orbit to an M Class planetary surface.
• Protocols also include the use of Lifeboats.
• Environmental Suits are available for evacuation directly into a vacuum. In such a scenario, personnel can evacuate via airlocks, the flight bay, or through exterior turbolift couplings. Environmental suits are available at all exterior egress points, along with survival lockers spaced throughout the habitable portions of the starship. Standard air supply in an EV suit is 4 hours.

Warp Core Ejection

Though rare, starships occasionally face the horrible concept of a warp core breach. As the primary power source for a starship, the explosive power of a warp core far surpasses the superstructure and structural integrity field strengths and most often ends in the complete destruction of the starship and anything within a 20km blast radius. Modern starships have been equipped for this possibility and have the capability to eject their warpcore. The Oracle class has an ejection port on the aft side of the main hull. Magnetic rails inside the channel accelerate the core once disengaged from the ship and ‘fires’ it as far as 2000 meters away from the ship. The ship then moves away from the core as fast as possible under impulse power.

Should the core not go critical, the Oracle class can recover its warpcore by use of tractor beams and careful manipulation.