| U.S.S. Defender | |
|---|---|
| |
|
Namesake: Class: Registry: Owner: Operator: Status: |
HMS Defender (D36) Lexington Class NCC-93136-A United Federation of Planets Starfleet Active |
| |
| |
U.S.S. Defender
The U.S.S. Defender (NCC-93136-A) is a Lexington Class Dreadnought, operated by the Federation Starfleet, 38th Fleet.
It is a primarily tactical upgrade to the Block II Yorktown design, itself an upgrade based upon the Odyssey Class. In addition to the standard armaments, it includes a phaser-lance cannon, and a mission-pod fitted slightly above and behind the primary hull (attached to the secondary), providing additional tactical sensors, and a greatly increased sensor and communication capability.
The class retains all the functionality from the previous Yorktown-Class design, including facilities aboard for science, engineering, and support roles, meaning it is well-suited for either deep-space exploratory missions, tactical patrols, fleet or taskforce command/communication/coordination. The facilities are certainly available to support diplomatic efforts as well, where the upgraded armaments would not be considered a hinderance to those missions.
The Defender (Formally the U.S.S. Majestic) has also had a number of none standard upgrades applied that where, applied at first during her upgrade from Block I Odyssey Class to Block II Yorktown Class, and then another series of adjustments where made during the upgrade to the Block II Lexington Frame.
Legacy
There has been three other vessels in Starfleet history to have been launched with the name Defender, with a number from earth history with one notable ship listed below.
HMS Defender (D36): 2013-2030
Commissioned in March 2013, the HMS Defender was the fifth of the Royal Navyâs six Type 45 destroyers. Together with her sister vessels, Defender was one of the most advanced warships ever constructed at the time.
In late 2030, despite the on-going third world war the HMS Defender was still in service, and presumed lost with all hands as a result on the on-going conflict.
USS Defender (NCC-26227): 2215-2280
The USS Defender (NCC-26227) was a Federation Miranda-class (Reliant-subclass) cruiser starships in service to Starfleet in the 23rd century.
The Defender was one of the first new build Reliant-subclass starships to enter service, and was launched on reference stardate 2215. On stardate 2220, the Defender was refitted to Mk II specifications.
The ship served with distinction until it was decommissioned and scrapped in 2280.
USS Defender (NCC-62422): 2370-2401
The USS Defender (NCC-62422) was an Akira-class Federation cruiser starship in Starfleet service in the 24th century. This ship was in active service around the 2370s decade.
Following the Cardassian uprising and the obliteration of the Federation reserve fleet in the Pearl Nebula on Stardate 54642.8 (August 23rd, 2377), the Defender was found derelict near Zarush by Chancellor Martok and his small fleet of Klingon Defense Force ships. Martok instructed his warriors to retrieve and repair all of the derelict Federation ships before Ferengi scavengers could seize them. The Defender subsequently participated in Martokâs obliteration of the Cardassian base in the system.
The Klingons returned the salvaged ships to the Federation, and the Defender returned to active duty, until it was destroyed during the battle of Frontier Day in 2401.
USS Defender (NCC-93136): 2405-2424
Commissioned in 2405, the USS Defender was an Sovereign-class vessel. Originally built as part of Starfleetâs reconstruction efforts following the events of 2401, the ship had it shake down cruise before being deployed to Klingon front in 2405 as part of the 7th fleet as part of patrol and defensive operations to ensure the security of Federation space.
The Defender remained in service for just nineteen years, being plunged directly into the Federation-Klingon War and subsequent Iconian War, Hurâq Conflict and Romulan War Civil Wars where she served with distinction, earning multiple unit citations throughout all conflicts.
Following the wars, and subsequent crew rotation, the Defender was tasked with security and diplomatic missions as part of the 38thâs fleet Cetratus Squadron, before itâs destruction on stardate 101085.3, where the ship was destroyed by an Azedi Etnoziroh-class Dreadnought, during a convoy escort mission.
Service History
Construction and Block I Service
Launched on October the 8th in 2410, as the U.S.S. Majestic NCC-97020 with the Aquarius Escort, the U.S.S. Daring NCC- 97032, it was assigned to the 64th Fleet to serve as the Fleetâs Flagship replacing the U.S.S. Sword following that ships decommissioning, with Captain Chester, Kolinski taking command.
The Majestic was the head of the 64th Fleetâs Task force Mars, which was first deployed to the Klingon boarder as part of Federation security patrols in the area, before in December of 2411 the Majestic and Task Force Mars where scrambled to assist Federation forces at DS9 with a group of displaced JemâHadar forces, after this and helping ensure station security, the ship and task force Mars returned to Klingon boarder patrol operations, with the group of ships being reassigned to Anti-borg patrols in 2412. Due to the range at which Task Force Mars was operating, the Majestic hosted Admiral James Carter of the 64th who made use of the lower bridge module to command operations.
Later in November of 2412, the Majestic returned to dock for a brief refit to ensure safe transit through the recently discovered Iconian gateway network, with this being completed in January of 2413, the Majestic was assigned to Federation Solanae holdings heading up the 64th Fleetâs recently created Task Force Saturn and tasked with assisting in on going scientific and defense operations, with the ships of Task Force Saturn, including the Majestic helping fend off a Voth attack in July of 2413.
However in April of 2414 with the discovery of the Iconian threat, all but two ships of Task Force Saturn were recalled to Starbase Twenty, which housed the 64th Fleetâs command staff for further orders, with the Majestic leading the ships of Task Force Mars to Calbriden III in an attempt to halt an Iconian Assault in May of the same year. This attempt resulted in minor damage to the Majestic and the loss of Ten of Task force Mars ships.
Once Repairs where completed in June of 2414, the Majestic was sent with Task Force Mars to reinforce the Caitian Defense Force above Cait, with the rest of the 64th Fleet being formed into Task Force Athena and being deployed to the Sol system.
The Majestic took part in the Battle of Cait in August of 2414, resulting in heavy damage in an attempt to shield both System Facilities and ships of the CDF from Iconian fire, this resulted in the loss of Captain Chester, Kolinski and Admiral James Carter who was coordinating efforts from the bridge, the Majestic was towed into Caitian Ship Yard Four, Dock Two to await repair work.
In September of 2414 this work started with the decision at first taken to upgrade the Majestic to the Block II Yorktown frame, whilst retaining the original Odyssey Class Nacelles.
Block II Refit and Project Sundance Service
As work started on the Block II upgrade, under the oversight of Engineer One of Eight, the ship caught the attention of Starfleet Intelligence who quickly stepped in, under a yet to be named project with the aim of creating an Intelligence modification for the Odyssey frame, to make use of the ship as mobile agent operation point.
To this end a number of modifications to the Majestic where approved, these included stealth systems original in the form of Sensor and Warp masking hull plating, which resulted in the Majesticâs and Daringâs darker appearance, the ship also received a number of advanced covert and monitoring sensors placed around the ship in key locations, and the lower bridge module was to be converted from a CIC/Conference area into a module for on-board agents to operate from, having access to the ships advanced sensor and communication systems, including a series of deployable privacy screens to isolate the module from the rest of the bridge during classified meetings and briefings.
Following a series of unsuccessful tests of the plating, which only resulted in minor reductions in the ships profile, the Project now going by Sun-Dance, brought in Alliance Intelligence staff, creating a joint oversight board, and with a number of conditions set by the Romulan Republic and Klingon Empire, permission was given to fit a cloaking device taken from a heavily damaged Falchion class, following installation and trials it was found that due to power draw issues the cloaking device would shut down after eight hours of operation, however following adjustments to the power grid it was found that the power draw could be off-set with increased cycle time, with a twenty four hour test of systems showing a cycle time of 15 minutes, however the U.S.S. Daring being fitted with a Federation standard cloaking device suffered no such problems.
Following all trials and a successful shake down cruise, Ferasan Captain Junern, Jhizit, a newly commissioned Khitomer alliance Captain was selected as the best fit for this joint operation, with overall command falling to the 64th fleet which the ship was reassigned to, and the Sun Dance oversight board also holding reviews of the ship as needed.
With successful testing of the systems and the ship fully staffed itâs first covert task was to assist the I.K.S. PâNgev from Klingon Intelligence and the R.R.W. Irese from Republic Intelligence with investigating Tzenkethi activities in the Ferenginar sector in October of 2416.
Then in January of 2417 the Majestic was recalled to Starbase Twenty and took on a detachment of MACO officers and Ferasan Assault Marines, to enhance itâs covert operations mission profiles, with both groups coming under the Command of Commander Carlos Kaz âFormally Nightingaleâ who had previously over seen the Armory refit to the Majestic. After taking on the two detachments, the U.S.S. Majestic was tasked with heading up the 64th Fleetâs newly formed group Spectre, and along with the U.S.S. Berlin and U.S.S. Royal was assigned to DS9, taking part in the opening battle of the Hurâq conflict only a month later, with Marines and MACOs being deployed to assist with Station security operations.
Despite the timely help of the Dominion, Starfleet Command and Intelligence didnât trust the intensions of the group, with the Berlin and Royal being rotated out of Group Spectre for repairs, and the Cloud and Icon being rotated in. The Majestic then under cloak with the Icon and Cloud transitioned through the Bajoran wormhole, to begin extended Intelligence and monitoring operations in March of 2417.
The only notable information uncovered by the Majestic during this time was an ancient Dominion research station discovered in June of 2417, however the crew was ordered to not investigate at the time, then the following month with the end of the Hurâq conflict, Task Force Spectre was disbanded and the U.S.S. Cloud and Icon returned to the Alpha quadrant, with the Majestic remaining in the Gamma Quadrant and being tasked with monitoring the Hurâq to ensure there is no risk of a repeat of the recent conflict. This monitoring is uneventful until a call from Admiral James, Carter Jr alerted the crew of the Majestic to be on standby to return to the Alpha quadrant at a moments notice due to on-going Azed Confederation tensions with the 38th Fleet in November of 2417.
It wasnât until November of the following year that the Majestic would be recalled to Starbase Twenty for new orders, however during this transit the ship was intercepted by the U.S.S. Thunderchild and took on a passenger of TâZon, Jhizit before carrying on to Starbase twenty.
Following a resupply stop at Starbase Twenty and a slightly extended holiday downtime, where the ship played host to families of crew of the Majestic and other fleet personal of the 64th, with the crew returning to normal operations in January of 2418 and heading to the Klingon boarder, along with two newly constructed Caitian Shikaris Escort of the CDF and two Ferasan Slithus Escort of the Ferasan Defense Fleet, to form the temporary group of Task Force Claw, for joint operations near the Klingon boarder following reports of strange activity over the boarder.
In March of the same year the ships are ordered to cross the boarder to assist a Klingon defector who had information on the on going reports the Klingon Empire was near a Civil war, after safely securing the Defector and a tense stand off with House MoâKia forces, the Majestic and Task Force Claw returned to the Federation side of the boarder, the U.S.S. Daring being deployed to transfer the defector to the Sol system, as Task Force Claw remains behind and carries out security patrols of the boarder.
However in October 2419 following a house MoâKia attack on Andoria and the revealing of a new super weapon, the ships of the CDF and FDF are recalled to their home systems, with the ships of Task Force Mars being deployed to assist the Majestic at the boarder, then with the outbreak of the Klingon Civil War in August of 2420, the command of the U.S.S. Majestic is temporarily placed under Commander Carlos Kaz, as Captain J. Jhizit is recalled to Starfleet Intelligence for an extended interview, with the ship later being recalled in December of 2420 for repairs, resupply and a refit.
Lexington Class Refit Service
In December of 2420, the Majestic was handed over to Dry dock staff and upgraded to the Lexington Class Frame, with the mission pod attachment, resulting in some covert and monitor sensors being moved to the mission pod, with a rear and forward probe launcher being fitted, instead of the normal tactical focused six additional torpedo launches, the increase in weapon power with the fitting of the Phaser Lance Cannon under foreward-ventral secondary hull and additional sensors being fitted, caused the Cloaking time suffered a reduction in time before increased cycle time would become a problem. The ship also saw the addition of the A Taste of Home Restaurant to support Messhall facilities.
With the upgrades taking longer than expected due to power management problems the ship was prevented from leaving dry dock on schedule, however in May of 2421 the Majestic was scrambled to Assist the U.S.S. Berlin and U.S.S. Icon that where dealing with rouge Klingon forces who where attempting to attack a Federation shipment to the colonies near the Klingon Boarder. Then in June of the same year with the end of the Klingon Civil war the U.S.S. Majestic is reassigned to DS9 to take part in Bad land patrol operations, with other alliance forces.
In September of 2421, the Majestic is taken from standard operations and takes part in Wargames with the U.S.S. Defender, U.S.S. Armada and U.S.S. Echo, however the reports of the outcome and actions taken during the the Wargames are highly classified and restricted, with staff involved being required to not speak of their involvement, with the only mention was that the crew of the Majestic was grounded shortly after the Wargames.
The crew where then scrambled back to Badland patrol operations in November of 2421, with the Majestic heading up Task force Star, due to increased threat from the Terran Empire, this was only paused to allow for a brief diversion to investigate a joint Caitian-Ferasan colony that was no longer responding to communications in December of the same year, with Terran involvement feared.
Following investigations the Majestic reported the colony had been destroyed, with the only survivors being a young hybrid cub called SâTau and his Maine Coon pet Nova, the ship then returning to dock following this diversion, the crew where briefed on current intelligence reports around the Terran Empire as well as informed they would be required to return to dock in February of 2422.
After returning to regular patrols, which where largely uneventful, the ship then returned to dock in February 2422, where they had their aging Peregrine Class fighters replaced with newly constructed Valkyrie fighters, helping to increase the capability of the ships fighter pilots as well as itâs own combat abilities. With the Badland patrols being resumed shortly after, until in July of 2422 the Majestic was called on to assist the I.K.S. Thorâmuk with investigating reports that a Caitian lead PMC group was attempting to disrupt trade in the Bajor Sector, this lead to a confrontation where the U.S.S. Daring, the original Majesticâs escort was lost, and whilst the PMC was dealt with and the leaders arrested, taken into joint Starfleet and Klingon custardy, the Majestic needed to return to space dock to receive a replacement Escort, with this happening in September of the same year, with the U.S.S. Leopard NCC-97122 being paired with the Majestic, following itâs hull plating being replaced to match that of the U.S.S. Majestic, following this the crew then returned to regular patrols.
In January of 2423, the Majestic was recalled to Starfleet Headquarters, with the senior staff interviewed on the outcome of project Sun-Dance, and what future the ship had, now that Starfleet looking to suspend the project, the crew where then ordered back to the Majestic and taken from the 64th Fleetâs command and placed on Operation Home Front, where the ship was to take part in moral boosting displays with other Starfleet ships, including hosting public visitations to the ship.
The ship remained assigned to Operation Homefront until June of 2423, where the Ship was reassigned back to the 64th Fleet and back to the head of Task Force Mars, leading Anti-borg patrol operations with-in the 64th Fleetâs area of operation as part of a rapid response group. Following a rather uneventful time deployed with the 64th and a request from the Khitomer Alliance Captain to be reassigned elsewhere, it was decided in December of 2423 to Dry dock the Majestic for an extended resupply and refit cycle, where all systems would receive inspections, and a new Captain was to be selected.
Reassignment to the 38th Fleet
Following this extended time in dry dock, which included the removal of the cloaking devices on both the U.S.S. Majestic, and the one that had been fitted to the U.S.S. Leopard, it was decided that with the destruction of the U.S.S. Defender, the Majestic would be rechristened the U.S.S. Defender NCC-93136-A and after clearing other modifications with Argo command, was to be transferred to the command of Captain HâLtol, Shâow, the previous Defender Captain.
Technical Data
| Specifications | |
|---|---|
|
Length: Beam: Draft: Mass: |
1041.5 Meters 385.32 Meters 175.62 Meters 7,105,362 Metric Tons |
|
Habitable Decks: Crew Complement: Emergency Cap.: |
43 1,500 15,700 (Evac. Limit) |
|
Avg. Cruising Spd: Max. Cruising Spd: Maximum Spd: |
Warp 8 Warp 9 Warp 9.995 (Non-Slipstream) |
|
Armaments: |
22 Type-XV Phaser Arrays 4 Type-XII Pulse Phaser Cannons 1 High-Yield Phaser-Lance Cannon 4 Variable Payload Torpedo Tubes (Fore) 2 Variable Payload Torpedo Tubes (Aft) 2x Variable Payload Torpedo Tubes (Aquarius Aft) |
|
Defenses: |
Neutronium Alloy Hull Armor with Ablative Duranium Layer 10 Yoyodyne 1080-D Unified Deflector Field Emitter Arrays JAWS System Active Directional Sensor Matrix |
|
Sensors: |
14x DYN-90 Multi-band Linear Sensor Suites 4x Omniwave Passive Sensor Matrices 4x SENTINEL Omni-Directional Targeting Arrays |
|
Auxiliary Craft: |
36 Valkyrie Fighters 20 CMU Workbees 6 Type 8 Shuttlecraft 2 Type-11 Shuttlecraft 2 Yellowstone Class Runabouts (U.S.S. Avon and Wye) 1 Aquarius Class Escort Corvette (U.S.S. Leopard) |
Based upon the Yorktown-Class design, itself a Block II refit of the Odyssey Class, the Lexington-class uses the same basic arrangement common to most Starfleet ships. The vessel is composed of two main hull sections: an oval, domed primary hull, and a detachable secondary hull. The forward section of the stardrive hull extended under most of the saucer, retaining most of its length during saucer-separation. Like many designs before it, the two hulls of the Lexington-class could reattach without returning to spacedock. This ability provided for great variety in meeting mission needs and in tactical scenarios. The main difference from the Yorktown-class is the addition of a mission pod to the aft-dorsal secondary hull, and a phaser-lance cannon to the foreward-ventral secondary hull. (Giving the appearance of being on the ventral primary hull, barring saucer-separation, or close visual inspection.)
The Lexington-Class has received minor system and equipment upgrades that are also being refit into Yorktown-Class vessels as necessary and/or convenient, unlike other ships of the class the U.S.S. Defender has a few none standard modifications that have not been applied to other vessels of the line, these modifications where applied as the recently declassified Alliance Intelligence Project, Sun-Dance.
External Layouts
Standard Lexington Class external views.The U.S.S. Defender (Formally the U.S.S. Majestic) has a darker hull appearance than other ships of the Lexington Class, due to upgrades made during Project Sun-Dance, it also retained itâs original Odyssey Class nacelles pylons.
Internal Layouts
Yorktown Class Master Systems Display (Lexington unavailable at time of entry.)Command & Control Systems
Main Bridge
VAR-1 Bridge Module U.S.S. Defender
Two bridge turbolifts were located on the port side, with the entrance to the ready room on the starboard. An observation area was between the viewscreen and the forward viewport.
The lower deck was below the observation area and served as the executive conference room, which was also subject to adjustments and change once the Defender was upgraded to a Block II Frame, whilst retaining itâs conference room capabilities, the lower bridge area also had privacy screens that could be raised and lowered from inside the lower area to provide an area for classified conversations and briefings, and an area for any Intelligence teams stationed on board to have access to encrypted communications and information which was fed to consoles around the area from the advanced sensor package.
Unlike other ships of the class, whilst the bridge systems where updated and the consoles where brought up to modern standards, the module itself was left as the VAR-1 bridge module, to retain the lower bridge area.
Auxiliary bridge
Located on Deck 13 in the secondary hull, the auxiliary bridge, sometimes referred to as the âbattle bridge,â served as a secondary central command facility in the event that the main bridge was unusable or inaccessible. It also served as the primary command facility of the stardrive section during saucer separation scenarios.
Propulsion systems
Vessels of the Lexington-class were equipped with one Yoyodyne 47B Matter-Antimatter Reaction Assembly and two Keenser/Pegg Heavy Impulse engines, unlike other ships of the class the Defender retains itâs original Odyssey Class nacelle support pylons which houses the set of ten Zhiv/Rev SR83 Impulse Thrusters. The primary hull also sported two Inline Flux Secondary Impulse engines for use during saucer separation.
Carrying over from the Odyssey-class design, the Lexington-class also included an advanced quantum slipstream propulsion system (QSPS). The slipstream tunneling projector was located forward of the navigational deflector on the ventral hull. The system allowed for Lexington vessels to travel at slipstream speeds exceeding 300 light years per hour for 15 seconds before needing a 2 hour recovery downtime. The dual-neck design connecting the primary and secondary hulls served as waveform attenuators, affording the cruisers improved stability under slipstream.
An Ithra IT-7 Subspace Conduit Access Coil was the core element to the classâ subspace conduit propulsion system (SCPS). This device allowed Lexington-class starships to connect to the Federation Transwarp Network and jump to gateways within the network at speeds of 360,000 light years per hour. The system had massive power needs, even more than the quantum slipstream drive. To power the coil, starships had to divert energy from weapon and shield systems. Due to strains on the IT-7 coil, it could only be used once every 20 hours.
Science and remote sensing systems
Twelve DYN-90 Multi-band Linear Sensor Suites, Two SENTINEL Omni-Directional Targeting Arrays, four Omniwave Passive Sensor Matrices, and a JAWS Active Directional Sensor Array were the initial standard equipment for the class. The JAWS array was located on the ventral hull behind the phaser-lance cannon. With an additional Two SENTINEL Omni-Directional Targeting Arrays located in the mission pod, along with an additional two DYN-90 Multi-band Linear Sensor Suites.
Unlike Standard Lexington Classes, the Defender is fitted with an advanced suite of advanced sensor systems, which originally where fitted at key points around the ship, however with the adding of the mission pod during her Lexington upgrade, time was taken to move parts of the sensor package into the mission pod, with sensors being used to also augment the traffic control and fleet coordination abilities of the Defender, however the fitting of these sensor systems does result in the loss of the six torpedo launchers that would normally be fitted here, instead the mission pod had a one fore and one aft heavy probe launcher for further information gathering and surveillance, with a dry dock however the mission pod could be removed and replaced with a standard tactical focused pod.
Tactical systems
Like its parent classes, the Lexington-class is heavily armed and incredibly resilient under enemy fire. The hull was a neutronium alloy reinforced with micro-ablative generators. Based upon technology brought back from the Delta Quadrant by the USS Voyager, these generators helped to dissipate energy across the hull and to regenerate damaged portions of the ablative hull coating, this hull plating also was given minor stealth properties, having the ability to have sensor and warp trail masking properties, however this effect is little to none existent due to the size and profile of the ship.
When developing the Yorktown-class, designers updated the deflector shield systems to the new Yoyodyne 960-B unified field emitter deflector shield arrays. The three equipped arrays projected unimatrix shields with regenerative, multi-spectrum, covariant, and metaphasic properties around the vessels. Nexus Defense Screens, that protected the crew from the effects of the Nexus and similar phenomena, were also integrated into the shield systems. These are carried forward to the Lexington-Class.
Vessels of the class mounted 22 Type-XV Annular Confinement Beam-jacketed phaser arrays and a single Phaser-Lance Cannon. The stardrive carried the Phaser-Lance, and 14 of the arrays, two of which were only usable during saucer separation, with the remaining 8 on the primary hull. Four Type-XII pulse phaser cannons were mounted along the forward edge of the saucer. A total of six Mk 110 variable-payload fixed-mount launch tubes are fitted to the stardrive section. Four of the launchers faced forward, while the remaining two faced aft, with an additional two aft launchers usable when the Aquarius escort is docked, by making use of the Aft launchers on the escort. Quantum torpedoes were carried as standard ordnance, but the class also carried a complement of tricobalt devices for the bombardment of heavy targets.
Auxiliary systems
Including the transporter pad on Deck 1, the Lexington-class features 11 transporter facilities at strategic locations throughout the ship.
Located aft of the bridge were six compartments for the classâ Modular Rapid Deployment System. Each compartment could be used to quickly deploy probes, mines, and other equipment.
Auxiliary craft systems
Berths
The class carried one specialized berth. This is for an Aquarius-class corvette and is located at the aft of the secondary hull. This berth is designed to allow crews to easily service and refuel the craft.
Missing from the Lexington-Class, but present on the Odyssey and other variants, is a berth for the Captainâs Yacht, an auxiliary craft larger than most standard shuttles, but serving a similar purpose. The normal location for this berth is overtaken by the Phaser-Lance Cannon. As such, the Aquarius-Class vessel at the aft of the ship or other embarked shuttles and runabouts suffice in the role.
Shuttlebay
The sole shuttlebay of the Lexington-Class is situated on the aft rim of the saucer section between the primary impulse engines. The entrance is segmented into three distinct shutters for structural integrity and to allow for streamlined control of craft traffic. Docking control sits above the shuttlebay in a facility that runs most of the width of Deck 3. With the pylons of the mission pod in front of the shuttlebay doors, it is a more challenging ingress and egress, but the pylons align with the dividers between the three doors, making this better than it could have been.
A small afterdeck outside the shuttlebay doors could also serve as a landing platform for additional craft, although access to them would require using a transporter or environmental suit.
Auxiliary craft
The initial standard complement of the U.S.S. Defender (Formally U.S.S. Majestic) was an Aquarius-class corvette, 36 Peregrine Class fighters, and other auxiliary craft, including 25 workpods, 7 shuttlecraft, and 2 runabouts. Actual numbers of craft would vary depending on a starshipâs assignment and mission requirements. In February of 2422, the Peregrine fighters were rotated to other ships and stations in core Federation territory, and the Defender was finally stocked with 36 Valkyrie fighters, for which a requisition was entered months prior. The Starfleet Valkyrie fighters were designed after the Dominion War to replace the aging, but dependable, Peregrines. Faster and more maneuverable, with a similar armament, they also have a slightly smaller overall footprint, making the Valkyrie an even nicer choice for a ship that isnât a dedicated carrier, like the Jupiter or Seneca classes.
Valkyrie Class Fighter (Artist's Rendering)
Evacuation pods
The Lexington continues to use the same evacuation pods used in the Odyssey design. The cruisers carry 448 of the Type A Mark IX Autonomous Survival and Recovery Vehicles (ASRV) and 24 of the Type C Mark XII models, for its cetacean crew. Forty-two of the Type A pods are located in the separation plane between the saucer and secondary hull and can only be launched during saucer separation.
Crew Support Systems
Medical facilities
The Lexington-class contains 6 sickbay wards, four of which were housed on Deck 7 with the office of the chief medical officer. The main sickbay is Class G and the other three on Deck 7 are Class E. The two sickbay wards on Deck 27 in the stardrive section are both Class D.
Holographic projection system
Holographic projectors are equipped throughout Lexington-class vessels. These allow for emergency holograms to be quickly activated at any location in a time of need. As such, the starshipâs computer stores the programs for six Emergency Medical Holograms, six Emergency Engineering Holograms, eighteen Emergency Security Holograms, and an Emergency Command Hologram.
Crew Quarters Systems
Standard Living Quarters: Located on Decks 3-11, these quarters are where the majority of the crew live.
Crew Quarters: Standard Living Quarters are provided for both Starfleet Non-Commissioned Officers, attached civilian personnel and officers holding the rank of Ensign. These persons are expected to share their room with another crewmate due to space restrictions aboard the starship, and after serving aboard the ship for six months, are eligible to bring family aboard and be relocated to Family Quarters.
Two NCOs or two Ensigns are assigned to a suite. A large living area spreads across two bays at the center of the dwelling. Furnished for comfort, it typically holds a personal holographic viewer, couch, two chairs and a work station as well as a standard replicator. This room is flanked on both sides with identical bedrooms, which each take up one bay in length and house room for a double-sized bed and room for personal belongings. A half-bathroom is located on the opposite side from the bedroomâs entrance, and has a sonic shower, wash basin, mirror and several drawers. Provisions for small pets can be made available.
Enlisted crewmembers share quarters with up to four other people of the same gender. A large living area spreads across two bays at the center of the dwelling. Furnished for comfort, it typically holds a personal holographic viewer, couch, two chairs and a work station as well as a standard replicator. This room is flanked on both sides with identical bedrooms, which each take up one bay in length and houses a bunk for two occupants, as well as space for their belongings. A half-bathroom is located on the opposite side from the bedroomâs entrance, and has a sonic shower, wash basin, mirror and several drawers. Pets are not allowed for enlisted crewmen.
Crewmen can request that their living quarters be combined to create a single larger dwelling.
Residential Apartments: Located on Deck 6 and 8-9, these quarters offer more privacy and flexibility for officers, as well as those crew with family onboard. Unlike the standard living quarters, these apartments can be configured to suit the needs of those living in them. Listed below is the base configuration for these living spaces, which can then be tailored by the resident for his needs.
Officersâ Quarters: Starfleet personnel from the rank of Lieutenant Junior Grade up to Commander are given one set of quarters to themselves. In addition, department heads and their first assistant are granted such privileges as well, in an effort to provide a private environment to perform off-duty work. After six months, officers are permitted to bring family aboard the ship and a slightly larger room can be allocated to them. Members of the Senior Staff can have these restrictions waived with the Captainâs permission.
These accommodations typically include a two-bay living area at the center of the dwelling, which usually holds a personal holographic viewer, personal workstation, couch, replicator and a small dining area. Connected to this is a bedroom that occupies one bay and features a double-sized bed and room for personal belongings. Normally, the bedroom is connected by a half-bathroom with wash basin, mirror, several drawers and a sonic shower. This can be upgraded to a full-sized bathroom with a bathtub with permission from the Operations officer as space permits. Provisions can also be made available for pets.
Officers may request that their living quarters be combined to form one larger dwelling.
Executive Quarters: Executive quarters are specially designed to give both the Commanding Officer and Executive Officer added comfort and privacy to perform their duties.
The accommodations are similar to that of the Officerâs Quarters, however, they feature a longer three-bay living area and a full bathroom by default. Slightly more luxurious furniture is also provided, since the Captain often uses this room as an informal meeting area for both private conferencing and reception of guests.
VIP/Diplomatic Guest Quarters: Located on Deck 10 near the shuttlebay, diplomatic quarters are the same as Executive Quarters, but feature private communications terminals for secure conferencing and an additional living area(s) for diplomatic aides. Such facilities on Deck 10 are limited, and in cases involving transport of large numbers of diplomats, VIPs and ambassadors, several areas on Deck 9 can be converted to these standards. In addition, these quarters can be immediately converted to class H, K, L, N, and N2 environments within a few hours notice.
Understandably, only a limited number of residential apartments exist aboard a starship. Allocation of available rooms falls under the authority of the Operations Chief, who is then responsible to make arrangements with Engineering and the shipâs Counselor concerning assignment of personnel.
Crew Quarters Systems, Notes
With Captain J. Jhizit being the longest serving Captain a number of modifications where made for personal taste to his personal quarters, including a borg regeneration alcove, which was later removed, and connection to the Quarters next door, which was original converted to Dorm style accommodation for his three children, TâZon, SâTau and KâMure Jhizit.
Whilst the dorm style rooms have been removed, returning it to a more conventional style of crew quarters, the connection remains, with the room currently housing four empty hand crafted wooden cots, which have been decorated with a number of ancient Bajoran and Caitian blessings for the young.
Recreation Systems
As with any other ship in the fleet, the Defender features a number of recreational facilities, including holodecks and smaller holosuites, as well as phaser ranges, weight rooms and gyms. There is also a Three screen cinema set up on deck 9 and a swimming pool located on deck 10.
There facilities are spread out across decks 3 to 11, with deck 10 housing a holodeck reserved for any visiting guests or VIPs, however this is often opened to all staff when no guests are on ship.
A Taste of Home
Following the success of the A Taste of Home restaurant located a short five minute walk away from Starfleet Academy on earth, and a smaller stall location opening on DS9. Jordard Jhizit, asked for permission from Starfleet Command and current Captain J. Jhizit to open a location on the U.S.S. Majestic (Now the U.S.S. Defender), during the application process a suitable head chef was trained up by Jordard and then once the application was approved in December 2420, this chef was sent to set up shop with the help of on-board engineers and dry dock staff, with Jordard visiting in the ship in January of 2420 to help host the opening and over see the first shift.
This restaurant focuses on providing a home cooked meal for all crew on board, focusing on providing a small taste of home even whilst exploring the galaxy, the Chefs and staff that work there are highly trained in all forms of food a Starfleet crew might eat, whilst this was originally fitted to be a once or twice a week treat for staff, following popular demand additional staff was assigned room on the ship and granted permission to begin full time operations, with tables often booked in advance due to itâs high popularity.
Using the onboard Hydroponic bays to secure freshly grown produce as well as trading with ships and stations they encounter, with the staff priding themselves on providing as fresh and home grown of an experience as possible, however during prolonged deployments away from stations, the staff have been known to use replicated meat produce when fresh is unavailable.
It is to be noted that the Captain of the ship is often known to host parties and guest events in the restaurant.
Personnel
Previous Commanding Officers
2410 - 2414
(KIA, Battle of Cait)
2414 - 2424
(Khitomer Alliance)
Current Senior Staff
COMMANDER
Zenade, Sunin {NPC}
LIEUTENANT
Tisa, Jurud {NPC}
COMMANDER
Six of Eight {NPC}
LT COMMANDER
Haituk {NPC}
LT COMMANDER
Jack, Nightingale {NPC}
LT COMMANDER
Tiroh, T'Soph {NPC}
LT COMMANDER
Sieth {NPC}
LIEUTENANT
M'Koin Jhizit {NPC}
OOC Crew currently NPC staff, this will update if/when ship is opened to player staffing
Notable Additional Staff
COMMANDER
Carlos Kaz {NPC}
HEAD CHEF
H'Lrur Krasi {NPC}
SOUS CHEF
Margaret Graham {NPC}
FLUFFY
Nova {NPC}
OOC Fully NPC Staff area
Mission Patches, Battle Honors, and Awards
Odyssey class USS Majestic
Yorktown class USS Majestic
Lexington class USS Majestic
Lexington Class U.S.S. Defender
Odyssey class Development Patch
Yorktown class
Development Patch
Klingon War
Solanae Sphere
Borg Incursion
Iconian War
Hur'q Conflict
Terran Incursion
Gallery
U.S.S. Majestic under going upgrades 2412
U.S.S. Majestic In Dry Dock in Cait System, prior to relaunch in May 2415
U.S.S. Majestic in dock following Lexington Upgrade program Jan 2421
U.S.S. Majestic preparing to enter the Bajoran Wormhole as part of group Spectre
U.S.S. Majestic In Combat with the Hur'q
U.S.S. Majestic Engaging True Way Forces
U.S.S. Majestic, updated hull following rechristening U.S.S. Defender
Recently rechristened U.S.S. Defender
OOC Most shots are of U.S.S. Majestic due to only recent name change
Further Reading Roleplay Information
NCC-97020
USS Majestic
(Odyssey Class)
NCC-97020
USS Majestic
(Yorktown Class)
NCC-97020
USS Majestic
(Lexington Class)
D36
HMS Defender
(Daring-class)
NCC-93136
USS Defender
(Sovereign Class)
NCC-93136-A
USS Defender
(Lexington Class)
Despite an upgrade to the Lexington Class frame which included the installation of a High-Yield Phaser-Lance Cannon and the additional mission pod the Defender is still set up to serve as not only a fleet leading vessel but one that is still very capable in diplomatic duties, with extensive communication and sensor equipment, and it's large frame helping to house a number of diplomatic suites that can house any number of guests, safely and securely. With it's on-board restaurant helping to provide freshly prepared meals on board.
The ship was also deployed with a fighter wing of thirty six Valkyrie Class Fighter, which are used in not only, limited strike and ship defense capabilities but also as escorts for the two type-11 shuttles or the two Yellowstone runabouts, in the event they are used in diplomatic functions, helping add a sense of ceremony to bringing guests aboard the ship when transporters are not suitable.
The ship also has additional sensor suites when compared to a standard ship of the class, at the loss of the six Variable Payload Torpedo Tubes that would normally be housed in the shipâs mission pod, instead opting for two additional sensor suites, and targeting suites, as well as one fore and one aft heavy probe launcher, which means despite itâs more tactical refit the Defender is also well equip to handle scientific and exploration missions, keeping with the wide mission profile of the class of ships.
When in combat the ship is often one to be attempting to attract fire from other ships in itâs task group, often relying on itâs heavy shielding and armor plating to take hits that other ships may not be able to, with it also able to dish out the pain to hostile forces by making use of not only itâs many on-board weapon, but by coordinating with itâs Aquarius-class corvette, embarked fighters, and other ships in the taskforce it is deployed with, using the sensor suites and communication arrays on board.
OOC Information - Rp Locations
The Defender also makes use of multiple bridge locations to make up the complete bridge set for Rp locations, which are broken down below. This is to account for the lack of a conference room and other such features on the aquarius bridge, this will be updated if Devs release a more modern federation bridge as seen in the tutorial and recent missions.
Bridge
The bridge module for the Defender is the VAR-1 bridge module, aquarius bridge set to allow for use of the Ready room, and lower bridge module. This is the bridge that will be general use for all bridge set Rps
Conference Room
The Conference room of the Voyager 2410 Bridge, will be used for meetings that would normally take place in a conference room on a bridge.
Secondary Sickbay
The Secondary sickbay of the Defender will make use of the sickbay of the Voyager 2410 Bridge
Taste of Home
The Taste of Home Restaurant will make use of the Messhall of the Voyager 2410 Bridge
OOC Information - NPC Information
A number of NPC staff are used on the Defender for certainly purposes, with notable ones below.
Commander Carlos Kas {Formerly Nightingale}
ICly, the commander acts as a guide to the ship for the current command officer, due to his long service with the ship and crew, he also is an un-official Command staff member, who when required can be used in place of a Commander, First or Second officer, given his experience in command before his demotion and reassignment to the Majestic.
He also often goes by the nickname Major, due to his time heading up the MACO and Ferasan Assault Units on the Majestic, even though he left the MACOs a number of years ago himself, however he often encourages the use of this nickname, even by other ranking officers preferring the nickname to his official rank and given name.
He is sometimes also referred to as Grumpy Spots, a nickname that was given to him by the Jhizit Cubs on board, with SâTau and KâMure Jhizit calling him this more often, with some NPC crewmen adopting this nickname as well.
Head Chef HâLrur Krasi and Sous Chef Margaret Graham
These two serve as the main NPC Chefâs, with a number of other Chefs taking other shifts, on the Defender in a Taste of Home, with all having been trained by Jordard Jhizit on Earth, the Head and Sous Chef are often very prideful of their work and often speak to staff and post surveys to staff to see how their menu is liked by the crew and adjusting it as needed.
References
- Jayceâs Navy Interstellar - Starfleetâs New Odyssey
- Ktarnfleet Wiki (Odyssey class)
- Ktarnfleet Wiki (Yorktown class)
- Ktarnfleet Wiki (Aquarius class)
- Yorktown class MSD
- Spacedock Video Enterprise, NCC-1701-F Enterprise, NCC-1701-F Information Break Down
- Spacedock Video Yorktown Yorktown Information Break down.
- U.S.S. Wasp Mission Patches Layout, and Lexington Class Information.
- U.S.S. Dragon Lexington Class Information.
- U.S.S. October Lexington Class Information.
