U.S.S. Wasp
| USS Wasp | |
|---|---|
| |
| History | |
|
Namesake: Builder: Laid Down: Launched: Commissioned: Homebase: Operator: Registry: Status: |
USS Wasp (LHD-1) San Francisco Fleetyards Stardate 85133.3 Stardate 86506 Stardate 86925.1 Deep Space 13 Starfleet, 38th Fleet NCC-98346 Active |
| General Characteristics | |
|
Class and Type: |
Block II/S(UA) Odyssey (Lexington)- class Dreadnought Cruiser |
|
Length: Beam: Draft: Mass: |
1041.5 m 385.32 m 175.62 m 7,105,362 metric tons |
|
Propulsion: |
1x Yoydyne 47B M/ARC Warp Core 1x Rigel Labs X06 Quantum Slipstream Field Projector 1x Ithra IT-7 Transwarp Coil Access Conduit 2x Keenser/Pegg Heavy Impulse Engines 2x Inline Flux Secondary Impulse Engines (Saucer Section only during separation) |
|
Avg. Cruise: Max Cruise: Max Speed: |
Warp 8 Warp 9 Warp 9.995 (Non-QSD) |
|
Decks: Crew: Capacity.: |
34 1500 15,700 |
|
Sensor Systems: |
12x DYN-90 Multi-band Linear Sensor Suites 4x Omniwave Passive Sensor Matrices Twin SENTINEL Omni-Directional Targeting Arrays JAWS Active Directional Sensor Array |
|
Defenses: |
FSR4-C Metaphasic Resilient Shield Array Yoyodyne N-90 Multiphasic Navigational Deflector Neutronium Alloy Hull Armor, with Ablative Duranium layer |
|
Armaments: |
22x Type-XII Phaser Arrays 8x Type-XII Phaser CIWS Turrets 8x Torpedo SAM Turrets 12x Variable-Payload Torpedo Launchers Spinal Phaser Lance Modular Rapid Deployment System 3x Yoyodyne 960-B Unified Field Emitter Arrays (Fitted For) |
|
Auxiliary Craft: |
18x Valkyrie class Strike Fighters 7x Type 8 Shuttlecraft 3x Type 11 Shuttlecraft 2x Yellowstone class runabouts 1x Argo class Shuttles (with rovers) 5x CMU Workbees 1x Aquarius class Escort Corvette (USS Parramatta) |
| |
| |
The USS Wasp (NCC-98346) is a Lexington class Dreadnought Heavy Cruiser in service with Starfleet’s 38th fleet. She is the fourth Starfleet vessel to bear the name Wasp following a Constitution class, Galaxy class, and Defiant class vessel of the same name. She was originally launched as an Odyssey class Star Cruiser, before receiving multiple upgrades and refits, resulting in her becoming a Lexington class Dreadnought Heavy Cruiser.
History
Laid down as a Block I/T Odyssey class cruiser in late 2408, USS Wasp was launched on Stardate 86506 (July 4, 2409) and commissioned on stardate 86925.1 (December 4, 2409). For the first four months of her shakedown cruise, Wasp flew without the support of her assigned Aquarius class escort, USS Parramatta, as the ship had yet to be launched, due to problems and issues in her construction and fitting out schedule. After finishing the portions of her shakedown that were impossible to complete without her assigned escort, Wasp was assigned to the Romulan Border, to patrol the area in the aftermath of the announcement by Romulan Empress Sela that any Reman or Romulan factions not aligned with the Star Empire (i.e., D’Tan’s Romulan Republic) to be terrorists. Wasp was one of the few ships in the region not to be called to assist in the defence of the newly established Mol’Rihan from an Elachi attack, as she was busy dealing with a minor flashpoint in the Rihan system.
In late 2411, Wasp was reassigned from the Romulan Front to general anti-Borg defensive duties, due to an increase in Borg activity at the time. After spending most of 2412 assigned to anti-Borg duties, Wasp and Parramatta were recalled to Utopia Planitia for a minor system update, in response to the newly discovered Solanae Dyson Sphere. This refit included upgrading the ship’s SIF generators to allow for safer transit of the Iconian Gateway network. However, after this refit was completed, Wasp was sent to DS9, in order to keep an eye on, and intervene if necessary in, Breen aggression against the Deferi. After about a year patrolling the UFP-Breen border, Wasp was hurriedly reassigned to the Delta Quadrant to assist in combatting the Vaadwaur. While she didn’t participate in the Assault on Vaadwaur Prime, Wasp did deal with any major flashpoints that cropped up. However, stardate 92332.9, Wasp was recalled to Sol as fast as possible – the Iconians had begun their assault on the Alpha and Beta Quadrants.
Wasp and Parramatta were kept in the Vulcan Sector, patrolling the core worlds of the Federation – Sol, Vulcan, Andoria, Tellar – making sure that the Iconians were unable to do much damage. Despite all this, stardate 92738.4, September 27, 2415, the Iconians hit the Sol system, in what would become known as the Battle of Midnight. During this battle, Parramatta was disabled, and Wasp was heavily damaged – damaged enough that she was out of service for a couple of years, as she – alongside the USS Yorktown and Enterprise, as well as a handful of other Odyssey vessels – underwent an upgrade to Odyssey Block II/S (Yorktown class) standard. Wasp and Parramatta returned to service in October 2417, just in time to assist against the Tzenkethi Coalition’s Protomatter attacks. In February 2418, when it was discovered that the Hur’q were the reason why the Tzenkethi were doing what they were doing, Wasp was deployed to the Gamma Quadrant to assist in the Dominion’s effort against the Hur’q. When the Hur’q were somehow dealt with in July of that same year, Wasp was stood down from her duties in the Gamma Quadrant, and returned to the Beta Quadrant, this time operating out of Starbase 24.
After returning from the Gamma Quadrant, Wasp was assigned to Starbase 24, and patrolling the UFP-Klingon border. During this time, Wasp participated in multiple multi-national fleet exercises. After tensions began rising in the Empire after the return of J’Ula and House Mo’kai, Wasp was one of multiple Yorktown class vessels recalled to Sol and hurriedly given an upgrade to Odyssey Block II/S(UA) (Lexington class) standards. This upgrade gave the ship a mission pod on the dorsal side of the engineering hull, a Spinal Phaser Lance on the ventral side of the saucer, and a pair of SENTINEL Omni-directional Targeting Arrays. These upgrades proved to be extremely useful in the coming Klingon Civil War of 2421-22 and later Terran Crisis of 2422-23. At the close of the Terran Crisis, Wasp was retrofitted with a Torpedo-based Surface-to-Air Missile system. These were equipped due to the system’s success on the Alita line of vessels.
Technical Data
Physical Arrangement & Crew Support
Based upon the Yorktown class hull, the Lexington class cruiser takes the basic form of most Starfleet cruisers. Her design is comprised of a saucer section connected by a split neck to an engineering hull that supports the mission pod, deflector array, and warp nacelles. The two hull sections are capable of separating and reintegrating without the need for a Starbase, like the old Galaxy line of exploration cruiser. The ship’s phaser lance is mounted on the ventral side of the saucer section, a section which, during separation, is actually a part of the engineering hull.
As with others in the Odyssey family, the Lexington class is highly automated, as well as has holoprojectors on all decks, enabling the use of all kinds of Emergency Holograms – from EMHs, Emergency Security Holograms, Emergency Engineering Holograms, and other such holograms.
Command & Control Systems
The bridge of the Lexington is the VAR-2 bridge module, developed in response to the cavernous design of the VAR-1 module. While the new version retains some aspects of the old, the size of the new one was drastically decreased.
Chairs for the commanding officer and two other officers were placed in the center of the area facing the large viewscreen. Between the command area and the screen, in a slightly recessed area, were the flight control station and the primary tactical station. Imbedded in a raised console that curved behind the command area was the secondary tactical station. To starboard of the command chair, and next to the doorway to the ready room, was the operations station. Two consoles were immediately behind the station along the wall, the first was the auxiliary control station followed by a mission operations console. Behind these consoles was the doorway to the Deck 1 corridor. This was mirrored on the port side by the turbolift. Forward of the turbolift doors was a multi-use console, followed by the secondary and then primary science stations. The entryway to the executive lounge stood beside the primary science console. The aft wall of the bridge, behind the secondary tactical console, was covered by three additional consoles. The center console was a dedicated engineering station, while the other two stations were multi-use.
On Stardate 99670.5, the Wasp recieved a third update to her bridge module, this time to the VAR-3 module. For all intents and purposes, this variant is identical to the VAR-2 module, except that the VAR-3 has more updated consoles, and a cleaner look, bringing in line with the newer station designs that had been coming out.
For sensors, the Lexington class uses the same sensors as the Yorktown, those being the twelve DYN-90 Multiband Linear Sensor suites, four Omniwave Passive Sensor Matrices, and the JAWS Active-directional Sensor Array. She also has a number of probes deployable via the Modular Rapid Deployment System. In addition to these carried over from the Yorktown, the Lexington also carries a pair of the SENTINEL Omni-Directional Targeting Arrays, originally deployed on the Odyssey Block II/T (Endeavour class).
Propulsion & Power Generation
Power is provided to a Lexington class vessel by a Yoyodyne 47B M/ARC Warp Core. This provides the power to propel the ship to a maximum speed of warp 9.995, and a cruising speed of either warp 8 or 9. As with other vessels in the Odyssey family, the Lexington class is capable of Quantum Slipstream travel, thanks to a Rigel Labs X06 Quantum Slipstream Field Projector; the same model equipped on the Pathfinder class Long Range Science Vessel. Lexingtons are also equipped with an Ithra IT-7 Transwarp Conduit Access Coil, which allows ships of the class to access the Khitomer Alliance Transwarp Network. For Subluminal speeds, the Lexington is powered by two Keenser/Pegg Heavy Impulse Engines, mounted in the ships’ nacelle pylons. However, because the Lexington is capable of Saucer Separation like other ships of its family, ships of the class also mount a pair of Inline Flux Secondary Impulse Engines on the aft of the saucer section. These impulse engines are only operable when the saucer is separated from the engineering hull. Otherwise, the Keenser/Pegg Heavy Impulse Engines take priority for subluminal propulsion.
Tactical & Defense Systems
Like the Yorktown on which it was based, the Lexington is just as, if not even more, powerful when it comes to firepower. Sporting the same 22 Type-XII Phaser Strips and 6 variable payload torpedo launchers as its predecessor, the Lexington is a terror on the battlefield. This is compounded by the fact that the Starfleet Corps of Engineers have mounted a mission pod carrying 6 additional torpedo launchers to the ships’ dorsal hull, and a Galaxy Dreadnought/Yamato class style Spinal Phaser Lance to the ventral side of the Saucer section. While primarily for the launching of probes and other equipment, the Lexington’s Modular Rapid Deployment System can also be configured to deploy various types of mines. Ships of the Lexington class can also mount the Yorktown’s trio of Yoyodyne 960-B Unified Field Emitter Arrays. These emitters allow a ship of this type to harness various exotic particles and use them to potentially disable hostile vessels. These are, at the time of this entry, not currently installed on Wasp, however.
Defensively, the Lexington borrows just as heavily from the Yorktown, however, it does add a few touches of its own. Like the Yorktown, Lexingtons are protected by a FSR4-C Metaphasic Resilient Shield Array and a Yoyodyne N-90 Multiphasic Navigational Deflector. Ships in the Lexington line are also protected by Neutronium Alloy Hull Armor, with an Ablative Duranium layer. Unlike a Yorktown, a Lexington also carries a series of Phaser CIWS and Torpedo SAM turrets to help protect the ship from torpedos, mines, and asteroids.
Auxiliary Spacecraft
While the Wasp’s embarked craft is rotated on and off on a regular and mission-specific basis, a standard loadout of embarked craft consists of 36 Valkyrie class strike fighters, 7 Type 8 shuttlecraft, 3 Type 11 shuttles, 2 Yellowstone class runabouts, 1 Argo class shuttle (with docked rover), 5 CMU Workbees, and 1 Aquarius class escort corvette, docked in the aft docking berth at the fantail of the vessel. Wasp, and most Lexingtons in general are rated to carry Peregrine class strike fighters in place of Valkyries, however the Valkyries are much more common, due to their smaller footprint. Wasp can carry up to 72 of either type, at the cost of the rest of its air wing – bar the Aquarius – as a “surge capacity” for more area denial missions, when a dedicated carrier is unavailable.
Mission Patches, Battle Honours, and Awards
Odyssey class USS Wasp
Yorktown class USS Wasp
Lexington class USS Wasp
Aries Squadron
Odyssey class Development Patch
Yorktown class
Development Patch
Romulan Civil War
Borg Incursion
Vaadwaur Campaign
Iconian War
Hur'q Conflict
Terran Incursion
Gallery
Master Systems Display of a separate Yorktown class vessel (Unfortunately, at the time of writing, the MSD of a Lexington is yet to be declassified)
Odyssey class USS Wasp just prior to launching on Stardate 86506
Wasp stationed at Deep Space 9
Wasp engaging a Borg Sphere alongside the USS Grotius, a Gagarin class Battlecruiser based out of Starbase 24, circa 2419
Wasp and her fighter wing engaging a Breen Sarr Theln class Carrier, circa January 2422
References
- Jayce’s Navy Interstellar - Starfleet’s New Odyssey
- 26th Fleet Wiki (Yorktown class)
- Ktarnfleet Wiki (Yorktown class)
- Ktarnfleet Wiki (Aquarius class)
- Yorktown class MSD
- Credit to Coby for the assets for the Odyssey and Yorktown Wasp Patches
