Pegaus Fleet Wiki - User contributions [en]

Template:Home

2024-03-03T21:26:58Z

Clement: Updated to reflect work-in-progress state of the wiki.

= Welcome to the Pegasus Fleet Wiki! =


<templatestyles src="Template:Home/custom.css"/>


Greetings and welcome to the future home of the '''Pegasus Fleet Wiki'''! We are currently in the midst of developing the base framework for what will become our database containing everything to do with our community canon, timeline, and stories. In the meantime, if you are looking to learn more about Pegasus Fleet, we invite you to visit our [https://main.pegasusfleet.site/ fleet website].

If you are looking for resources to help you with your writing, we recommend [https://memory-alpha.fandom.com Memory Alpha].

For all other questions and concerns, please contact a member of the [https://main.pegasusfleet.site/leadership/ Pegasus Fleet admiralty].
<br><br>

__NOTOC__
__NOEDITSECTION__

Template:TOC limit

2023-08-12T18:31:45Z

Clement: Created page with "<templatestyles src="Template:TOC limit/styles.css" /><div class="toclimit-{{{1|{{{limit|3}}}}}}">__TOC__</div><noinclude> {{TOC limit|3} * Add this to any article where you wish to limit the levels that will appear on the table of contents. * Setting 1 would be no TOC at all, so don't use this. * Setting 2 would be the first level headings only, etc. </noinclude>"

<templatestyles src="Template:TOC limit/styles.css" /><div class="toclimit-{{{1|{{{limit|3}}}}}}">__TOC__</div><noinclude>
{{TOC limit|3}
* Add this to any article where you wish to limit the levels that will appear on the table of contents.
* Setting 1 would be no TOC at all, so don't use this.
* Setting 2 would be the first level headings only, etc.
</noinclude>

Template:TOC limit/styles.css

2023-08-12T18:31:21Z

Clement: Created page with "/* {{pp-template}} Allow limiting of which header levels are shown in a TOC; <div class="toclimit-3">, for instance, will limit to showing ==headings== and ===headings=== but no further (as long as there are no =headings= on the page, which there shouldn't be according to the MoS). */ .toclimit-2 .toclevel-1 ul, .toclimit-3 .toclevel-2 ul, .toclimit-4 .toclevel-3 ul, .toclimit-5 .toclevel-4 ul, .toclimit-6 .toclevel-5 ul, .toclimit-7 .toclevel-6 ul { dis..."

/* {{pp-template}}
Allow limiting of which header levels are shown in a TOC;
<div class="toclimit-3">, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS). */
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}

Akira class

2022-04-19T15:51:51Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Specifications | image = 350px | name = Akira | affiliation = Starfleet | role = Heavy Cruiser | precedingclass = | succeedingclass = | dateentered = 2370s | expectedruration = | expectedrefit = | timeresupply = | crewcomplement = | emergencycap = | length = | width = | diameter = | height = | decks = | propulsionsystem = * matter/anti-matter warp drive | cruisespeed = | maxspeed = | emergencyspe..."

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Akiraclass.png|350px]]
| name = Akira
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2370s
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Akira''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]] as part of its response to the [[memoryalpha:Borg Collective|Borg threat]].

==History==
The [[memoryalpha:Battle of Wolf 359|Borg attack of 2367]] shook [[Starfleet]] to its very core. A single Borg cube had swept aside an entire fleet of Starfleet's most modern starships with very little effort at Wolf 359. Thus, Admiral Hanson's development team (now led by Commander Shelby) had to come up with other ways to solve this problem. And the ''Akira''-class was among the results of these efforts.

Project ''Akira'' was (and still is) considered to have been a radical shift way from what many saw as more "traditional" Starfleet doctrine, but one that was needed. The design concept was to develop a vessel that relied less on phasers and more on swarming threats (particularly the Borg) to make it less likely they could adapt. This ultimately led to the ''Akira'' entering service with a torpedo-heavy armament, boasting more launchers than any ship in service up to that point, as well as a large flight deck to launch a multitude of attack craft.

These requirements further impacted the design of the vessel, resulting in the return of a unique "catamaran" design that had been largely sidelined since the [[memoryalpha:22nd century|late 22nd]] and [[memoryalpha:23rd century|early 23rd centuries]]. The middle of the hull was gutted from bow to stern and repurposed into the flight deck, making the turnaround of launched small craft that much faster. Robust shielding systems and ablative hull armor further strengthened the vessel for combat operations, making it more than capable of handling the attempted [[memoryalpha:Battle of Sector 001|Borg invasion of 2373]] as well as field duty throughout the [[memoryalpha:Dominion War|Dominion War]].

While the Borg are no longer considered a major threat, the ''Akira''-class remains a staple in Starfleet service due to its versatility. In particular, the passthrough flight deck that had supported fighter operations so well in wartime proved a significant non-combat opportunity, enabling the ''Akira'' to become well-known for its support of evacuation missions by their ability to quickly launch, recover, and redeploy shuttles. Only recently has Starfleet considered introducing a companion class, the [[Gagarin class|''Gagarin''-class]], and even then, it is expected that the ''Akira'' will continue to serve for many years.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Thunderchild''

==Appendices==

===Background Information===
'''Content Coming Soon'''

===Writing Notes===
Production was prioritized for the ''Akira'' during the 2370s, making them quite a common sight around Federation space. They can be found in general exploration roles, patrol and escort duties, as well as occasionally helping in roles that require a large number of small craft. It is, however, uncommon to see more than one at a given time unless the circumstances call for it, since they are fairly capable in their own right.

Owing to their nature, ''Akira''-class starships are a common posting for pilots and flight operations personnel. Aside from that, it is considered a fairly standard career posting as of the 2390s, given its otherwise general purpose nature. Most crews tend to have no issue with their department not having enough to do, though there are those who will avoid a posting to an ''Akira'' as it can sometimes be of higher risk or faster-paced.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Akira_class ''Akira'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

File:Akiraclass.png

2022-04-19T15:51:36Z

Clement:

Steamrunner class

2022-04-19T15:25:40Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Steamrunnerclass.png|350px]]
| name = Steamrunner
| affiliation = [[Starfleet]]
| role = Frigate
| precedingclass =
| succeedingclass =
| dateentered = 2370s
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Steamrunner''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]] as a mid-sized, general purpose workhorse.

==History==
Development on the ''Steamrunner''-class began in the late 2360s alongside several other designs including the [[Akira class|''Akira'']], [[Norway class|''Norway'']], and [[Sabre class|''Sabre'']]. Part of [[Starfleet]]'s effort to modernize and adapt in response to the [[memoryalpha:Borg Collective|Borg]] threat, the [[memoryalpha:Starfleet Corps of Engineers|Corps of Engineers]] had their work cut out for them. On the one hand, they needed a ship that was smaller, more maneuverable, and more versatile. On the other, it needed to be capable of fulfilling a variety of peacetime and combat roles.

As a result, the ''Steamrunner'' and its contemporaries were the products of several departures from traditional engineering and design approaches. This is perhaps most readily apparent in the ''Steamrunner'''s rather distinctive outward appearance. However, engineers also incorporated a high degree of modularity into the design, making it so that the internal spaces could easily be rearranged and repurposed as needed. The ''Steamrunner'' boasted a powerful warp drive for its size and class as well as advanced tactical and defensive systems (a result of its anti-Borg origins).

While the ''Steamrunner'' ultimately saw minimal action against the Borg, the outbreak of the [[memoryalpha:Dominion War|Dominion War]] in 2373 marked a significant turning point in its continued development. New production was reduced as focus was shifted toward other combat-oriented designs and repair of damaged vessels, putting a damper on Starfleet's plans to field the ''Steamrunner'' as a replacement to the venerable, but aging [[Miranda class|''Miranda''-class]]. However, the loss of so many ''Miranda''-class starships and their crews, combined with the ''Steamrunner'''s performance in the field, pretty much guaranteed the change-over would happen eventually.

The cessation of hostilities brought about a new season for Starfleet and the [[:Category:Alpha Quadrant|Alpha Quadrant]]. Production shifted back toward new, less combat-oriented starships and the process of transitioning over from the remaining ''Miranda''s to the ''Steamrunner'' was begun in earnest. In the years since, the Starfleet Corps of Engineers has not yet developed a comprehensive refit for the ''Steamrunner'', meaning that it continues to perform admirably in the field as a general purpose workhorse. Indeed, engineers expect it will continue to do so alongside newer [[Reliant class|''Reliant''-class]] vessels well into the future.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Steamrunner''

==Appendices==

===Background Information===
'''Content Coming Soon'''

===Writing Notes===
Being a jack-of-all-trades workhorse, the ''Steamrunner'' can be seen in just about any support role that would normally have been associated with the [[Miranda class|''Miranda''-class]]. Production ramped up significantly following the [[memoryalpha:Dominion War|Dominion War]], so seeing more than one in situations that require it would not be uncommon, either. Overall, in the absence of a more specialized vessel, the ''Steamrunner'' is likely to be found.

It is becoming commonplace for many personnel to have served on at least one ''Steamrunner'' in their career, much as it used to be common to have had a posting on a [[Miranda class|''Miranda'']], [[Constitution class|''Constitution'']], or [[Excelsior class|''Excelsior'']] a generation before. Like other second-line vessels, it is a good place for new officers to find their footing, but tends not to be a preferred posting for more experienced personnel, especially if they are looking for greater prestige.

Owing to its multipurpose nature, it is rare for anyone in any particular career field to end up "bored". Given that the ship could move from humanitarian aid one mission to stellar research the next, followed by reinforcing border patrol and then responding to a deep space distress call, ''Steamrunner'' crews tend to agree - the work may not always be glamorous, but there is never any shortage of it.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Steamrunner_class ''Steamrunner'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Frigates]]

File:Steamrunnerclass.png

2022-04-19T15:25:10Z

Clement:

Nova class

2022-04-18T23:24:55Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Novaclass.png|350px]]
| name = Nova
| affiliation = [[Starfleet]]
| role = Corvette
| precedingclass =
| succeedingclass =
| dateentered = 2370s
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Nova''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]] as a scout ship and science vessel.

==History==
Intended to serve as a replacement for the [[Oberth class|''Oberth''-class]], the ''Nova''-class entered initial development in the mid-2360s alongside the [[Intrepid class|''Intrepid''-class]] and others. In fact, engineers used an unselected hull proposal from the concurrent [[Defiant class|''Defiant'' project]] as the basis for this new design, seeking to create a vessel that was both fast and light.

Unfortunately, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] was already stretched thin by a mandate to develop other anti-[[memoryalpha:Borg Collective|Borg]] technologies, and therefore found themselves rushed in the development process. Challenges arose when it came to the vessel being able to support extended-duration missions. The disappearance of the [[memoryalpha:USS Equinox|''USS Equinox'']] in 2371 further cast doubt on the new design. However, the outbreak of the [[memoryalpha:Dominion War|Dominion War]] just two years later (and resulting demand for starships in the field) led [[Starfleet]] to field additional vessels of this type as scout ships.

It was not until 2378 that the Corps of Engineers was able to revisit the ''Nova''-class design. After thorough analysis, which included information gained from the experience of the ''Equinox'' (as relayed by the crew of the [[memoryalpha:USS Voyager|''USS Voyager'']]), the entire design was overhauled and refit to better meet requirements.

This new refit was designated the ''Rhode Island'' refit after the ''USS Rhode Island'', the first vessel to receive it. It included a small, robust warp core that required less downtime, improved defensive systems, and an even more powerful sensor system. Completed in 2380, the results of field testing exceeded expectation. Approval was granted that same year to begin refitting all other ''Nova''-class vessels fleet-wide to the same specifications.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Nova''
*''USS Rhode Island''

==Appendices==

===Background Information===
'''Content Coming Soon'''

===Writing Notes===
Despite entering its second decade of service, the ''Rhode Island'' refit has revitalized and improved the ''Nova''-class considerably, making it the capable design it was always intended to be. It is relatively unlikely that a ''Nova'' would be encountered far behind Federation lines, though a few have been known to be used as a fast courier. Rather, it is much more common to find them serving as scout ships, surveying newly discovered systems, and occasionally acting as reconnaissance or intelligence-gathering vessels.

Its small size means that ''Nova'' crews tend to have close-knit relationships, as long as they are the sort who take well to being on potentially dangerous scouting and survey missions. The mystery and potential danger tends to attract specific people, but can turn away those who do not work well in isolated environments with a small number of colleagues.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Nova_class ''Nova'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Corvettes]]

File:Novaclass.png

2022-04-18T23:24:19Z

Clement:

Olympic class

2022-04-18T22:59:55Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Olympicclass.png|350px]]
| name = Olympic
| affiliation = [[Starfleet]]
| role = Frigate
| precedingclass =
| succeedingclass =
| dateentered = 2360s
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Olympic''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]] primarily as a dedicated hospital ship, emergency relief vessel, and medical research platform.

==History==
Work on the ''Olympic''-class starship began in the mid-[[memoryalpha:24th century|24th century]] in response to the growing need for a designated hospital ship. Prior to that, [[Starfleet]] had long relied on the modification of existing starship classes (e.g. [[memoryalpha:Hiawatha type|''Hiawatha''-type]], [[Miranda class|''Miranda''-class]]) to fulfill this purpose. However, with many of these earlier vessels aging out or reaching the limit of their capabilities and demand only increasing, [[memoryalpha:Starfleet Medical|Starfleet Medical]] pushed for the creation of a new, dedicated ship type.

Throughout both the design and construction of this new class, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] worked closely with Starfleet Medical to ensure the ''Olympic'' would meet the need. Indeed, upon its launch in the late 2360s, it boasted the most advanced treatment and research facilities available including intensive care units, surgical facilities, and laboratories. This meant the ''Olympic'', despite its relatively small size, would still be able to handle the vast majority of medical-related situations.

In addition to these new systems, designers felt the ''Olympic'' needed to be readily identifiable as a medical ship (and as non-threatening as possible). This resulted in a rather distinctive appearance that was evocative of the vintage [[Daedalus class|''Daedalus''-class]]. It also resulted in a vessel that was only moderately shielded and minimally armed for self-defense.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Olympic''

==Appendices==

===Background Information===
'''Content Coming Soon'''

===Writing Notes===
If there is a medical crisis somewhere, an ''Olympic'' is not far from it. It is uncommon to see several of these vessels at once unless they are traveling in convoy or the situation is that severe or widespread. These ships are almost exclusively sent to respond to medical emergencies and/or relief work (i.e. Starfleet does not task them to other mission types). If they are going into a hostile situation and it is clear their status as a hospital ship may be disregarded, then they will typically be escorted by another vessel.

As far as crews go, the ''Olympic'' is essentially a mobile hospital. In other words, almost every member of the crew is of a medical background, including the command staff. The few that do not have medical experience are generally there to just keep the ship running and flying. Science personnel are typically from a medical research background (or adjacent field) to help deal with research and investigation of unusual cases. And these ships typically have ''extremely'' small security detachments.

Personnel with a medical background often find the work on an ''Olympic'' challenging, but right up their alley, seeing as they are essentially bringing the hospital to the patients. It is not uncommon for chief medical officers who have command aspirations to move into first officer and commanding officer duties on an ''Olympic''-class vessel. Engineers find the work mundane and sometimes underappreciated, whereas security personnel take the posting either because they prefer Starfleet's humanitarian role or because security is a relatively minimal role on these ships.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Olympic_class ''Olympic'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Frigates]]

File:Olympicclass.png

2022-04-18T22:58:52Z

Clement:

Monarch class

2022-03-26T23:38:00Z

Clement: Corrected error in link

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Monarchclass.png|350px]]
| name = Monarch
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit = 100 years
| timeresupply = 3-5 years
| crewcomplement = 800 persons
*136 officers
*664 enlisted
| emergencycap = 1,200 persons
| length = 525 meters
| width = 260 meters
| diameter =
| height = 130 meters
| decks = 14 decks
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed = Warp 7.5
| maxspeed = Warp 9.25
| emergencyspeed = Warp 9.9 (for 12 hours)
| energyweapons =
*phaser arrays
| torplaunchers =
*torpedo launchers
| torppayload =
*photon torpedoes
*quantum torpedoes
*probes
| shields =
*standard shielding system
| defense =
*ablative hull armor
*duranium/tritanium double hull
*structural integrity field
| facilities =
*1 shuttlebay
| auxcraft =
*8 shuttlecraft
*6 maintenance craft
| msd =
}}

The '''''Monarch''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. It was intended as a companion to the [[Sovereign class|''Sovereign''-class]] similar to how the [[Nebula class|''Nebula''-class]] was for the [[Galaxy class|''Galaxy''-class]].

==History==
Of the many designs to come out of the mid-[[memoryalpha:24th century|24th century]], the [[Nebula class|''Nebula''-class]] was arguably one of the most successful. This was due, in no small part, to its durability and reliance on components shared with the venerable [[Galaxy class|''Galaxy''-class]]. However, of even greater significance was the versatility offered by the modular pod attached to the ventral side of its saucer section. This pod allowed the ''Nebula'', with relatively minimal time in spacedock, to convert from one role to the next for rapid re-deployment into the field.

Although [[Starfleet]] was understandably hesitant to replace such a successful design so "soon" after initial deployment, they also realized continued development was essential to preventing the kinds of losses endured during the [[memoryalpha:Dominion War|Dominion War]]. And so, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] was tasked to design a successor for the ''Nebula'' that would be a companion to the [[Sovereign class|''Sovereign''-class]]. It was hoped this pairing would give the new ''Monarch''-class a similarly high chance of success as its predecessor.

Work began in 2384 with the keel of the ''USS Monarch'' begin laid at the [[memoryalpha:40 Eridani A Starfleet Construction Yards|''40 Eridani A Starfleet Construction Yards'']] shortly after the destruction of [[memoryalpha:Utopia Planitia Fleet Yards|''Utopia Planitia Fleet Yards'']] in 2385. Engineers encountered some delays due to logistical issues as well as time needed to properly test the available pods that the ''Monarch''-class could use. However, shakedown and testing were successfully completed in 2390 and Starfleet approved serial production that year.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Monarch''
*[[USS Hornet|''USS Hornet'']] (NCC-94650)

==Appendices==

===Background Information===
*The ''Monarch''-class is a non-canon starship design based on a model kitbash and rendered by online user [http://jaggd.artstation.com Jaggd] as a commission for Pegasus Fleet.
*The ''Monarch''-class was introduced to the Pegasus Fleet community by the resources team in December 2020. The name was chosen by vote of the Pegasus Fleet membership with history and specifications created by the team.

===Writing Notes===
'''Content Coming Soon'''

==Related Links==

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

Monarch class

2022-03-26T23:36:07Z

Clement: Created page with content, sidebar, etc.

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Monarchclass.png|350px]]
| name = Monarch
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit = 100 years
| timeresupply = 3-5 years
| crewcomplement = 800 persons
*136 officers
*664 enlisted
| emergencycap = 1,200 persons
| length = 525 meters
| width = 260 meters
| diameter =
| height = 130 meters
| decks = 14 decks
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed = Warp 7.5
| maxspeed = Warp 9.25
| emergencyspeed = Warp 9.9 (for 12 hours)
| energyweapons =
*phaser arrays
| torplaunchers =
*torpedo launchers
| torppayload =
*photon torpedoes
*quantum torpedoes
*probes
| shields =
*standard shielding system
| defense =
*ablative hull armor
*duranium/tritanium double hull
*structural integrity field
| facilities =
*1 shuttlebay
| auxcraft =
*8 shuttlecraft
*6 maintenance craft
| msd =
}}

The '''''Monarch''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. It was intended as a companion to the [[Sovereign class|''Sovereign''-class]] similar to how the [[Nebula class|''Nebula''-class]] was for the [[Galaxy class|''Galaxy''-class]].

==History==
Of the many designs to come out of the mid-[[memoryalpha:24th century|24th century]], the [[Nebula class|''Nebula''-class]] was arguably one of the most successful. This was due, in no small part, to its durability and reliance on components shared with the venerable [[Galaxy class|''Galaxy''-class]]. However, of even greater significance was the versatility offered by the modular pod attached to the ventral side of its saucer section. This pod allowed the ''Nebula'', with relatively minimal time in spacedock, to convert from one role to the next for rapid re-deployment into the field.

Although [[Starfleet]] was understandably hesitant to replace such a successful design so "soon" after initial deployment, they also realized continued development was essential to preventing the kinds of losses endured during the [[memoryalpha:Dominion War|Dominion War]]. And so, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] was tasked to design a successor for the ''Nebula'' that would be a companion to the [[Sovereign class|''Sovereign''-class]]. It was hoped this pairing would give the new ''Monarch''-class a similarly high chance of success as its predecessor.

Work began in 2384 with the keel of the ''USS Monarch'' begin laid at the [[memoryalpha:40 Eridani A Starfleet Construction Yards|''40 Eridani A Starfleet Construction Yards'']] shortly after the destruction of [[memoryalpha:Utopia Planitia Fleet Yards|''Utopia Planitia Fleet Yards'']] in 2385. Engineers encountered some delays due to logistical issues as well as time needed to properly test the available pods that the ''Monarch''-class could use. However, shakedown and testing were successfully completed in 2390 and Starfleet approved serial production that year.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Monarch''
*[[USS Hornet|''USS Hornet'']] (NCC-94650)

==Appendices==

===Background Information===
*The ''Monarch''-class is a non-canon starship design based on a model kitbash and rendered by online user [jaggd.artstation.com Jaggd] as a commission for Pegasus Fleet.
*The ''Monarch''-class was introduced to the Pegasus Fleet community by the resources team in December 2020. The name was chosen by vote of the Pegasus Fleet membership with history and specifications created by the team.

===Writing Notes===
'''Content Coming Soon'''

==Related Links==

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

File:Monarchclass.png

2022-03-26T23:17:56Z

Clement:

Theseus class

2022-03-26T23:08:21Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Theseusclass.png|350px]]
| name = Theseus
| affiliation = [[Starfleet]]
| role = Corvette
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Theseus''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. It was intended as a standardized successor to the existing small patrol and escort classes.

==History==
As [[Starfleet]] began taking inventory of their position following the [[memoryalpha:Dominion War|Dominion War]], they soon realized they had a problem when it came to small patrol and escort vessels, namely that there were four relatively recent designs all aiming to cover the same mission profile. The [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] was ordered to come up with a solution that would standardize the fleet, an need which became even more urgent following the [[memoryalpha:Attack on Mars|Attack on Mars]] in 2385.

Project Theseus began that same year. Inspired by several of the early [[Defiant class|''Defiant'']] pathfinder designs, the engineers came up with a small, conventional hull. The latest in ablative armor technology and more robust shielding systems increased durability considerably. Designers also borrowed heavily from the concurrent [[Inquiry class|''Inquiry''-class]] project including highly tuned propulsion systems, advanced sensors, and the latest phaser and rapid-fire torpedo technology. This meant that, like the ''Inquiry''-class, the ''Theseus'' would be able to hold its own against other ships that were much larger.

Alongside these tactical developments, however, engineers made sure to include the necessary creature comforts. Years of field reports from existing [[Defiant class|''Defiant'']], [[Sabre class|''Sabre'']], [[Sentinel class|''Sentinel'']], and [[Diligent class|''Diligent''-class]] vessels made it clear the original spartan accommodations would not be enough. And so, crew quarters, common areas, and recreational facilities were enhanced where possible to improve crew well-being and overall performance.

The ''USS Theseus'' was launched in 2390 and, following successful space trials, commissioned for active duty. Additional vessels have been requisitioned and construction begun. Completed vessels are slated to be deployed first to installations as replacement for existing ''Defiant'' and ''Diligent''-class support craft before being expanded to other assignments.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Theseus''

==Appendices==

===Background Information===
*The ''Theseus''-class is a non-canon starship design created by online user Renger.
*The ''Theseus''-class was introduced to the Pegasus Fleet community by the resources team as a new escort vessel. Its history and specifications were created by the team.

===Writing Notes===
'''Content Coming Soon'''

==Related Links==

[[Category:Federation starship classes]]
[[Category:Corvettes]]

File:Theseusclass.png

2022-03-26T23:05:25Z

Clement:

Lafayette class

2022-03-26T22:34:26Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Lafayetteclass.png|350px]]
| name = Lafayette
| affiliation = [[Starfleet]]
| role = Frigate
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length =
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Lafayette''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. Created as an overhaul of the legendary [[New Orleans class|''New Orleans''-class]] design, the ''Lafayette'' was meant to fill the role of long-range patrol vessel leading into the [[memoryalpha:25th century|25th century]].

==History==
Following the end of the [[memoryalpha:Dominion War|Dominion War]], [[Starfleet]] was forced to reckon with a number of new realities. Rather high among these was the fact that many of the older classes still in service had shown glaring weaknesses during the conflict. Some, like the [[Excelsior class|''Excelsior'']] and [[Miranda class|''Miranda'']], seemed to have long surpassed their functional effectiveness. Others, like the [[New Orleans class|''New Orleans''-class]], appeared to be right on the edge. By 2380, Starfleet was seriously considering retiring the latter in favor of pursuing other designs. However, being in need of a long-range patrol vessel, they decided to instead make use of the new "rebuild" approach.

Project Lafayette was approved in 2382 as an attempt to overhaul the existing ''New Orleans''-class into a modern frigate design. Logistically, it was a rather straightforward effort in most respects. The one notable exception was the sensor arrays, which the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] totally replaced, giving the ''Lafayette'' capabilities beyond even some of the most advanced fixed arrays up to that point. This, in turn, resulted in greater weapons targeting and accuracy similar to that of the [[Inquiry class|''Inquiry''-class]].

By 2390, the ''USS Lafayette'' had completed its space trials and was officially commissioned for active duty. Efforts immediately began on rebuilding other ''New Orleans'' vessels to the same specifications. With these upgrades, the ''Lafayette''-class was poised to take on patrol duties of the [[Sentinel class|''Sentinel'']] and [[Sabre class|''Sabre''-classes]] leading into the [[memoryalpha:25th century|25th century]].

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*''USS Lafayette''

==Appendices==

===Background Information===
*The ''Lafayette''-class first appeared in the non-canon ''Star Trek Online'' game as a "modern" skin for the [[New Orleans class|''New Orleans''-class]].
*The ''Lafayette''-class was introduced to the Pegasus Fleet community by the resources team as a new long-range patrol vessel. Its history and specifications were created by the team.

===Writing Notes===
'''Content Coming Soon'''

==Related Links==
*[https://memory-beta.fandom.com/wiki/Lafayette_class ''Lafayette'' class] at ''Memory Beta''

[[Category:Federation starship classes]]
[[Category:Frigates]]

File:Lafayetteclass.png

2022-03-26T22:31:12Z

Clement:

Reliant class

2022-03-26T22:11:08Z

Clement: Created page with content, sidebar, etc. (specs forthcoming)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Reliantclass.png|350px]]
| name = Reliant
| affiliation = [[Starfleet]]
| role = Light Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390s
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length = 251 meters
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Reliant''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. Based on the legendary [[Miranda class|''Miranda''-class]] design, the ''Reliant'' was poised to become a new workhorse of the fleet leading into the [[memoryalpha:25th century|25th century]].

==History==
By the mid-[[memoryalpha:24th century|24th century]], the [[Miranda class|''Miranda''-class]] was on the back end of its lifespan. The [[memoryalpha:Battle of Wolf 359|Battle of Wolf 359]] had forced Starfleet to pull dozens of the old vessels out of retirement until fleet numbers could be replenished. The [[memoryalpha:Dominion War|Dominion War]] broke out before sufficient progress had been made and the ''Miranda'' went to war a century out of date, and countless personnel suffered the consequences. As a result, the class was immediately slated for retirement following the war, with only a handful left in use as training ships and second-line roles.

Around that same time, rebuild programs such as the [[Excelsior II class|''Excelsior II''-class]], [[Ross class|''Ross''-class]], and [[Sutherland class|''Sutherland''-class]] were proving successful. Modernization programs, such as the [[Nova class|''Nova''-class]]' so-called ''Rhode Island'' refit, met with similar success. This led the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] to revisit the ''Miranda''-class as a potential basis for new design. Rather than simply overhauling existing vessels, however, each ''Reliant''-class would be built from scratch. They would bear the familiar silhouette, but be constructed from entirely new components.

As of 2395, a small number of ''Reliant''-class vessels had been put into service with several more scheduled for launch before the decade was out.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[[memoryalpha:USS Reliant (NCC-90200)|''USS Reliant'']] (NCC-90200)
*[[memoryalpha:USS Uhura|''USS Uhura'']] (NCC-90214)

==Appendices==

===Background Information===
*The ''Reliant''-class was first seen in the episode [[memoryalpha:The Star Gazer (episode)|"The Star Gazer" (''PIC'')]] and confirmed via behind the scenes information shared on Twitter.
*The ''Reliant''-class was introduced to the Pegasus Fleet community by the resources team following its appearance on [[memoryalpha:Star Trek: Picard|''Star Trek: Picard'']]. Much of the information presented currently has been developed by extrapolation from canon sources.

===Writing Notes===
While a relatively new class, the ''Reliant''-class already has a clearly defined mission profile - it is a second-line support ship. As such, it is most often seen further behind the line, so to speak, performing various support missions such as cargo hauling, medical transport, and assisting with second and third contact missions. However, as it is a newer class, not many are going to be encountered, and only one would be seen in a group at any given time.

''Reliant'' crews tend to have the same duality as most second-line ships. Either it’s a place where the “real” work can be done without the higher ups breathing down one’s neck or it’s a place where one’s career has gone to die. The benefits of this as a posting allow one to find their footing at their own paces, missions are rarely as fast paced as they would be on other ships, though it can lead to some slipping into lax views of regulations and slacking off. The varied missions that can come up for ''Reliant'' crews does mean that all departments get a chance to do something at one point or another.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Reliant_class ''Reliant'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Light Cruisers]]

File:Reliantclass.png

2022-03-26T21:54:07Z

Clement:

Inquiry class

2022-03-26T21:49:37Z

Clement: Added specifications

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Inquiryclass.png|350px]]
| name = Inquiry
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration = 100 years
| expectedrefit =
*5 years (minor)
*20 years (major)
| timeresupply = 3-5 years
| crewcomplement = 480 persons
*80 officers
*400 enlisted
| emergencycap = 1,920 persons
| length = 640.1 meters
| width = 296 meters
| diameter =
| height = 120 meters
| decks = 29 decks
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed = Warp 8.5
| maxspeed = Warp 9.75
| emergencyspeed = Warp 9.96 (for 12 hours)
| energyweapons =
*phaser arrays
| torplaunchers =
*2 forward launchers
*2 aft launchers
| torppayload =
*photon torpedoes
*quantum torpedoes
*probes
| shields =
*standard shielding system
| defense =
*ablative hull armor
*adaptive shield allocation algorithm
*duranium/tritanium double hull
*structural integrity field
| facilities =
*2 shuttlebays
| auxcraft =
*12 shuttlecraft
*6 maintenance craft
| msd =
}}

The '''''Inquiry''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. Designed in response to Starfleet's defense-oriented turn in the late 2380s, the ''Inquiry''-class heavy cruiser is a fast, well-armed starship deployed in large numbers near the Federation's borders.

==History==
Development on the ''Inquiry''-class began during a period of major upheaval for the [[:category:Alpha Quadrant|Alpha]] and [[:category:Beta Quadrant|Beta Quadrants]]. In particular, the loss of the ''[[memoryalpha:Utopia Planitia Fleet Yards|Utopia Planitia Fleet Yards]]'' in 2385 and the sharp political changes that surrounded that incident put Starfleet in a difficult position. They needed to find a way of restoring their fleet numbers and projecting strength quickly without the support of (arguably) one of their most vital production facilities. And yet, they were greatly limited by the [[memoryalpha:Federation Council|Federation Council]]'s hesitancy to green-light major projects.

Eventually, a successful argument was made and a new generation of designs began to take shape on the drawing board. In an effort to overcome the challenges that arose with earlier designs, such as the [[Prometheus class|''Prometheus''-class]]' and its multi-vector assault mode systems, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] aimed for something that would be more open to upgrades like the [[Constitution class|''Constitution''-class]] had been. It was hoped adaptability and standardization of parts would make these new vessels much easier to build and maintain anywhere in the Federation.

Designers quickly settled on the [[Sovereign class|''Sovereign''-class]] as the basis for the design. This resulted in the ''Inquiry'' having many of the latest systems while also focusing on tried-and-true systems where it best served the needs of the ship. Adaptations were made to propulsion, sensors, as well as the offensive and defensive systems. These, along with advancements in processing and interface components, made it possible for the ''Inquiry'' to operate with the capabilities of a much larger starship while still being able to move and react like a much smaller one.

The timeline for design and construction proved surprisingly short, with the ''USS Inquiry'' being launched in 2390. Field testing proved successful and engineers as well as fleet command staff were pleased by the results. High priority was placed on subsequent production, with the goal of having over two hundred vessels in service by the end of the twenty-fourth century. Yet, the ''Inquiry'' has also sparked much debate among the upper echelons of Starfleet. Some argue the organization is taking too belligerent and militaristic a stance while others point out that it is simply avoiding mistakes of the past by investing in the Federation's future security.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[[memoryalpha:USS Zheng He|''USS Zheng He'']] (NCC-86505)

==Appendices==

===Background Information===
*The ''Inquiry''-class was first seen in the episode [[memoryalpha:Et in Arcadia Ego, Part 2 (episode)|"Et in Arcadia Ego, Part 2" (''PIC'')]]. Very little information is known about this design, including why there were several variants in the episode. Screenwriter and producer [https://memory-alpha.fandom.com/wiki/Michael_Chabon Michael Chabon] identified the class name in a tweet.
*The ''Inquiry''-class was introduced to the Pegasus Fleet community by the resources team following its appearance on [[memoryalpha:Star Trek: Picard|''Star Trek: Picard'']]. Much of the information presented currently has been developed by extrapolation from canon sources.

===Writing Notes===
By the year 2399, [[Starfleet]] was able to field at least two hundred ''Inquiry''-class vessels. Captain William Riker even boasted them to be the "toughest, fastest, most powerful ship Starfleet ever put into service". Therefore, it would not be uncommon for sims operating at or near the edges of the [[United Federation of Planets|Federation]] to bump into one during a mission, especially if they are investigating possible threats or acting as the response to a threat already identified or encountered by another ship. In fact, depending on the threat, Starfleet may be willing to send several ''Inquiry''-class ships at a time.

While the initial assumption can be to assume anyone posted to an ''Inquiry'' is more of a hardline militarist, that is only true of a small fraction of the crews serving aboard this class. Most have a strong sense of duty and believe that they are serving to protect the Federation. In their minds, the best fight is the one in which they don't have to fire a shot. Thus, a majority of ''Inquiry'' captains see their role as policing (i.e. a stern word being better than a volley of quantum torpedoes). They also tend to see themselves as the "cavalry" coming to the rescue, willing to put themselves in harm's way to protect others.

Although engineers typically don't mind being on such an advanced ship, science and medical personnel tend to find such postings at odds with their careers. Very few would consider it as being one of their top ten choices. Conversely, those who grew up with tales of heroism and glory during the Dominion War might find such an assignment appealing, only to discover the reality much different from the picture painted for them.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Inquiry_class ''Inquiry'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

Odyssey class

2022-03-26T21:36:55Z

Clement: Revised

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Odysseyclass.png|350px]]
| name = Odyssey
| affiliation = [[Starfleet]]
| role = Explorer
| precedingclass =
| succeedingclass =
| dateentered = 2381
| expectedruration = 100 years
| expectedrefit =
* 5 years (minor)
* 20 years (major)
| timeresupply = 3-5 years
| crewcomplement = 2,502 persons
* 417 officers
* 2,085 enlisted
| emergencycap = 10,608 persons
| length = 1061.1 meters
| width = 371.9 meters
| diameter =
| height = 147.9 meters
| decks = 37 decks
| propulsionsystem =
* matter/anti-matter warp drive
* [[quantum slipstream drive]]
| cruisespeed = Warp 8
| maxspeed = Warp 9.6
| emergencyspeed = Warp 9.99 (for 12 hours)
| energyweapons =
* 12 phaser arrays
| torplaunchers =
* 2 forward launchers
* 2 aft launchers
| torppayload =
* photon torpedoes
* quantum torpedoes
* probes
| shields =
* standard shielding system
| defense =
* ablative hull armor
* duranium/tritanium double hull
* structural integrity field
| facilities =
* 3 shuttlebays
| auxcraft =
* 30 shuttlecraft
* 6 transports
* 12 maintenance craft
| msd =
}}

The '''''Odyssey''-class''' starship was a [[Starfleet]] vessel first introduced in the early 2380s. It was one of the largest and most powerful [[United Federation of Planets|Federation]] starship classes of its time, a true successor to the earlier [[Galaxy class|''Galaxy''-class]].

==Class History==
Development of the ''Odyssey''-class began in the early 2370s. Even as the [[Sovereign class|''Sovereign''-class]] was entering service, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] looked ahead to its next groundbreaking achievement. It was felt by some that the ''Sovereign'' had been pressed into service too soon, largely in an effort to meet the Borg threat, and that this had significantly altered the trajectory of the class itself. The plan moving forward was to design a vessel that would succeed (and ultimately surpass) both the [[Galaxy class|''Galaxy''-class]] and the ''Sovereign''-class by building upon the lessons learned from each.

No one could have imagined such a design would need to have been implemented so quickly, especially with the ''Galaxy''- and ''Sovereign''-classes still actively serving frontline duties. Yet, circumstances changed and Starfleet’s experiences with the [[memoryalpha:Dominion War|Dominion War]] pressured engineers to once again push ahead earlier than they had planned.

The keel for the ''USS Odyssey'' was laid down in 2376 at the ''San Francisco Fleet Yards''. Work began on a second vessel, the ''USS Verity'', soon afterward at the [[memoryalpha:Utopia Planitia Fleet Yards|''Utopia Planitia Fleet Yards'']]. Conflicts between the ''Odyssey'', ''Ascension'', and ''Excalibur'' projects, however, led to tension among the respective design teams and a stiff competition for resources. Ultimately, the ''Odyssey''-class was deemed a higher priority and the necessary resources were allocated accordingly.

Despite these protests and setbacks, both the ''Odyssey'' and the ''Verity'' were launched in 2381, five years after construction had begun. They quickly proved their worth in field trials as well as on active duty and were considered by many to be a successful demonstration of the project. Unfortunately, their size placed certain limitations on the number of vessels that could be constructed, fielded, or otherwise serviced by existing fleet yards. These included the amount of physical resources as well as the personnel available. Still, [[Starfleet]] had every intention of requisitioning the class for serial production.

That all changed with the [[memoryalpha:Attack on Mars|destruction of the ''Utopia Planitia Fleet Yards'']] in 2385. The Starfleet Corps of Engineers immediately put a hold on further production, first to address the more urgent need of sorting out the aftermath of the attack, and then to seek other [[United Federation of Planets|Federation]] facilities with the resources and the infrastructure to support such a project. They eventually identified the ''San Francisco Fleet Yards'', the ''40 Eridani A Starfleet Construction Yards'', and the ''Gavor Shipyards'' as possible candidates for when the time came to resume.

The ''Odyssey'' and ''Verity'' were the absolute pinnacle of Starfleet engineering upon their launch. However, the Corps of Engineers knew that would not always be the case. Thus, it was always their intent to further upgrade and modernize the class as new capabilities and technologies became available, allowing it to remain relevant well into the future. This enabled them to use the hold on production to refine the design and to incorporate systems that had been field tested on other starships during the interim. Most notable for the Mark II ''Odyssey''-class was the addition of [[quantum slipstream drive]] and enhanced sensor arrays.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[https://memory-beta.fandom.com/wiki/USS_Odyssey_(NX-97000) ''USS Odyssey''] (NX-97000)
*[https://memory-beta.fandom.com/wiki/USS_Verity ''USS Verity''] (NCC-97000)
*[[USS Astraea (NCC-80895-A)|''USS Astraea'']] (NCC-80895-A)

==Appendices==

===Background Information===

===Writing Notes===
The ''Odyssey''-class is by far one of the largest starship designs ever fielded by Starfleet. Similar to the [[Vesta class|''Vesta''-class]], encountering a vessel of this type as an NPC would be ''extremely'' unusual as there are literally only a handful currently operating throughout the entire Federation. Characters should be impressed, proud, and perhaps humbled to even set foot aboard one.

It makes sense, then, that serving aboard an ''Odyssey''-class starship would be as prestigious (if not moreso) than even the much sought after [[Vesta class|''Vesta''-class]]. All personnel are most likely to be the best in their fields and, given the ship's size and importance, it's not unheard of for certain department heads (e.g. chief engineer, chief medical officer, executive officer) to hold the rank of captain alongside the commanding officer.

In cases where the vessel is being used as a flagship for a member of the admiralty, command may be assigned to a relatively junior captain who oversees the daily operations on behalf of the flag officer. Ships not utilized for this purpose are assigned to senior captains with considerable experience in long-range exploratory and diplomatic missions.

''Special Note: Because of their unique role as flagships and emissaries on behalf of the Federation, an ''Odyssey''-class starship may include departments not normally found aboard smaller vessels or simulations.''

==Related Links==

[[Category:Federation starship classes]]
[[Category:Explorer]]

Quantum slipstream drive

2022-03-26T21:25:16Z

Clement:

__NOEDITSECTION__
The '''quantum slipstream drive''' (also known as '''quantum slipstream''', '''slipstream drive''', or simply '''QSD''') is an advanced form of propulsion technology that allows for travel across vast distances at speeds far exceeding that of conventional warp drive. It is believed to have been originally developed by a [[:Category:Delta Quadrant|Delta Quadrant]] race with the Borg designation, [[memoryalpha:Species 116|"Species 116"]].

==History==
The crew of the ''[[memoryalpha:USS Voyager|USS Voyager]]'' first encountered slipstream technology in 2374 when they discovered the ''[[memoryalpha:USS Dauntless|USS Dauntless NX-01-A]]'', a vessel they were made to believe was sent by Starfleet to transport them back home to the [[:Category:Alpha Quadrant|Alpha Quadrant]]. It was later revealed, however, that the vessel was an elaborate ruse by an alien named Arturis and the plot was foiled by the ''Voyager'' crew. The following year, the ''Voyager'' crew managed to construct their own quantum slipstream drive using rare [[memoryalpha:benamite|benamite]] crystals. Despite the initial promise of the new drive, a phase variance was discovered in the slipstream that ultimately proved impossible for the crew to overcome.

For a time, the technology was set aside, and further development seemed unlikely until the technical specifications were delivered to [[Starfleet Command]] in 2376. Analysis of the information began almost immediately in the hope that it might yield some method of bringing the ''Voyager'' crew home. Not long afterward, a team was formed at the ''[[memoryalpha:Utopia Planitia Fleet Yards|Utopia Planitia Fleet Yards]]'' to take on the project of making quantum slipstream drive a workable reality.

''Voyager''’s safe return in 2378 meant it was no longer necessary to develop a functioning drive in order to bring them home. However, the drive’s potential for use in deep space exploration remained, and so the work continued. Having access to the physical hardware, personal experience, and full data files brought back by the ''Voyager'' crew gave the team a significant advantage. Within a relatively short time, they were ready to begin the initial testing phase.

The first official tests of Starfleet-built quantum slipstream drive began utilizing specially designed drone ships. These were followed by modified [[Intrepid class|''Intrepid'' class]] starships, and later the construction of the first [[Spirit class|''Spirit class'']] vessels, which served as the primary testbed for the next phase of slipstream development. Once the individual components had been trialed in the field, engineers moved into yet another phase, utilizing the ''Voyager'' crew’s thorough analysis of the ''Dauntless'' to construct a detailed replica, the ''[[memoryalpha:USS Dauntless (NCC-80816)|USS Dauntless (NCC-80816)]]''. By 2383, this version of the vessel had completed rigorous testing and been deployed to the field, where it was used in Admiral Janeway’s search for the ''[[memoryalpha:USS Protostar|USS Protostar]]''.

Not long after initial construction of the ''Dauntless'' prototype, the discovery that the Romulan sun would explode brought changes to large portions of Starfleet. The re-prioritization of ''Utopia Planitia'' toward a total emphasis on the evacuation fleet shifted primary responsibility for the slipstream project (including the new [[Vesta class|''Vesta'' class]] design) to the ''[[memoryalpha:40 Eridani A Starfleet Construction Yards|40 Eridani A Starfleet Construction Yards]]'' in orbit of Vulcan. This proved fortuitous in that, despite the [[memoryalpha:Attack on Mars|attack on Mars]] in 2385, the project was able to continue unabated.

Commissioned at ''40 Eridani A Yards'' in 2386, the prototype ''[[USS Vesta]]'' was dispatched to the [[Eleventh Fleet]] patrol zone to conduct her shakedown and slipstream trials away from the core worlds. The results of these trials were found to be in line with those of earlier testing. Although a few of the tests did uncover some flaws that the smaller test vessels did not experience, refinements to the system and additional tuning of the ''Vesta'' spaceframe ultimately proved the system’s viability for use aboard larger starships.

==Technology==
===Operational Parameters===
The current Starfleet quantum slipstream drive system maintains a cruising velocity of three hundred (300) light years per hour. This can be sustained for a period of up to twelve (12) hours before the auto-shutdown sequence is initiated. Forty (40) minutes of preparation, inspection, and warm-up are required before making a standard slipstream jump. Afterwards, a minimum of nine-point-eight (9.8) hours’ down time per one (1) hour of flight time is required, and a minimum of five (5) days total if the auto-shutdown sequence was initiated.

Any attempt to activate the quantum slipstream drive before the cool-down cycle has been completed presents an ''extreme'' risk of slipstream failure and the ''significant'' possibility that the vessel in question will be severely damaged or destroyed.

The benamite crystals utilized in the quantum slipstream drive are rare, unstable, and extremely difficult to synthesize. The supply of crystals allotted to each vessel equipped with a quantum slipstream drive has only a finite use as the crystals are in a constant state of decay, a problem exacerbated by their use. When operational guidelines are followed, the benamite matrix will require servicing at a qualified shipyard as part of standard refit procedures. If the operational parameters are exceeded, the benamite matrix will last significantly less time.

Failure to abide by Starfleet regulations when utilizing the quantum slipstream drive will result in an investigation and a hearing at which disciplinary action may be taken.

===Security Concerns===
Starfleet Command has ordered the strictest security and marked all materials pertaining to the quantum slipstream drive as classified. This is largely due to the anticipated impact such technology will have on the balance of power across the [[:Category:Alpha Quadrant|Alpha]] and [[:Category:Beta Quadrant|Beta Quadrants]]. While it is expected that other powers will eventually become aware of the drive’s existence, Starfleet considers it of paramount importance that the specifications are not allowed to pass into the hands of non-Starfleet personnel.

===Compatible Ship Classes===
As standard:
*[[Spirit class|''Spirit'' class]]
*[[Dauntless class|''Dauntless'' class]]
*[[Vesta class|''Vesta'' class]]
*[[Odyssey class|''Odyssey'' class]] (Mk II refit)

As refit:
*[[Intrepid class|''Intrepid'' class]]

==Alternate Timelines==
===''Vesta''’s failure===
One alternate version of the ''[[USS Vesta]]'' existed in a timeline where development of the quantum slipstream drive was initially considered a failure. Early testing proceeded as it had in the prime timeline and, although reports seemed promising, the end results were far less than what had been hoped for. The ''Vesta'' prototype returned to drydock for retrofitting while subsequent [[Vesta class|''Vesta'' class]] starships were constructed without quantum slipstream capabilities.

==Writing Notes==
*Use of the quantum slipstream drive aboard any sim requires that a written request be submitted to and approved by the Department of Resources.

==Related Links==
*[[memoryalpha:Quantum slipstream drive|Quantum slipstream drive]] at ''Memory Alpha''

Eleventh Fleet

2022-03-26T21:10:39Z

Clement: Updated PFXO

__NOEDITSECTION__
{{Icons|pfc}}
{{Task_Force
| name = Eleventh Fleet
| seal = [[Image:PF-logo.png|325px]]
| areaofops = Milky Way Galaxy
| designation = Pegasus Fleet
| url = [https://pegasusfleet.net/ Pegasus Fleet]
| sims =
|co=Fleet Admiral [[Emily Quinn]]
|xo=Vice Admiral [[D'era Virtam]]
|cas=
}}
The '''Eleventh Fleet''', colloquially known as '''Pegasus Fleet''', is one of the numbered fleets that make up the [[United Federation of Planets|Federation]] [[Starfleet]]. Founded in response to incursions and rising threats of the 2360s and 70s, it was rendered inactive after being destroyed at the Battle of Benzar during the Dominion War. The fleet was later re-established in the mid-2380s to ease strain on Federation resources as well as mitigate concerns that Starfleet had been neglecting the worlds of the frontier regions. Since then, the Eleventh Fleet has taken on additional duties and responsibilities throughout Federation space and beyond, including providing the core element of the Delta Quadrant Exploratory Group.

==Overview==
The Eleventh Fleet was one of several that saw considerable action during the early days of the [[memoryalpha:Dominion War|Dominion War]], often dispatched to help shore up defenses and assist other fleets weakened by Dominion attacks. In early 2374, the fleet was redeployed to protect Benzar, homeworld of a key member of the Federation. However, they were caught by surprise, quickly overwhelmed, and eventually destroyed by a Dominion strike force. Subsequently, Starfleet placed the Eleventh Fleet on inactive status, opting to transfer the remaining personnel and assets to other fleets.

Following the war, Starfleet was faced with the monumental task of establishing a foundation for a post-war era. This meant dealing with multiple (often competing) interests that demanded much of their time and resources. Not only were they concerned about the rebuilding within the Federation, they were also responsible for assisting in the [https://memory-beta.fandom.com/wiki/Cardassia#Post-Dominion_War_recovery Cardassian reconstruction], and later the [[memoryalpha:Romulan_sun#The_Romulan_supernova|Romulan evacuation]]. Further complicating matters was the fact that some who believed the Federation had not focused enough on the frontier regions began to speak of leaving.

It became increasingly clear that something needed to be done to better address these needs. And so, by the early 2380s, Starfleet Command had started to reconstitute several of its inactive fleets. Vice Admiral Roman Sanchez was assigned to oversee the reactivation of the Eleventh Fleet. Most of the assets that Sanchez chose to become part of the reformed fleet, nicknamed ‘Pegasus’ after the admiral’s well-known style in battle, were drawn from what remained of the Starfleet reserves or from other active fleets and captained by freshly-promoted officers.

The fleet’s headquarters was soon established on [[Cestus III]] and it was given responsibility for a patrol zone spanning much of the galactic-south of Federation territory, sharing borders with the Tholians, Klingons, Gorn, and Metron Consortium. Official operations began in 2386 and, within three years, the Eleventh Fleet had established itself and proven itself capable of carrying out its duties in the Galactic South. In light of this, [[memoryalpha:Starfleet Command|Starfleet Command]] ordered an expansion of their operations into other areas of Federation space and beyond.

In 2392, the Eleventh Fleet took on additional responsibility for providing core elements of a new [[Delta Quadrant Exploratory Group]] based out of the [[Iota system]].

==Major Events==
* '''2374:''' Eleventh Fleet is destroyed by Dominion strike force at the Battle of Benzar
* '''2386:''' Vice Admiral Sanchez reactivates Eleventh Fleet, headquarters on Cestus III
* '''2389:''' Starfleet Command orders expansion of Eleventh Fleet operations into areas of Federation space beyond the Galactic South
* '''2392:''' Eleventh Fleet provides core elements of new Delta Quadrant Exploratory Group
* '''2394:''' [[graviton catapult|graviton catapults]] shut down following major accident, Eleventh Fleet tasked with two-pronged effort to re-establish support lines to the exploratory group

Inquiry class

2022-03-26T17:18:33Z

Clement:

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Inquiryclass.png|350px]]
| name = Inquiry
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length = 640.1 meters
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Inquiry''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. Designed in response to Starfleet's defense-oriented turn in the late 2380s, the ''Inquiry''-class heavy cruiser is a fast, well-armed starship deployed in large numbers near the Federation's borders.

==History==
Development on the ''Inquiry''-class began during a period of major upheaval for the [[:category:Alpha Quadrant|Alpha]] and [[:category:Beta Quadrant|Beta Quadrants]]. In particular, the loss of the ''[[memoryalpha:Utopia Planitia Fleet Yards|Utopia Planitia Fleet Yards]]'' in 2385 and the sharp political changes that surrounded that incident put Starfleet in a difficult position. They needed to find a way of restoring their fleet numbers and projecting strength quickly without the support of (arguably) one of their most vital production facilities. And yet, they were greatly limited by the [[memoryalpha:Federation Council|Federation Council]]'s hesitancy to green-light major projects.

Eventually, a successful argument was made and a new generation of designs began to take shape on the drawing board. In an effort to overcome the challenges that arose with earlier designs, such as the [[Prometheus class|''Prometheus''-class]]' and its multi-vector assault mode systems, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] aimed for something that would be more open to upgrades like the [[Constitution class|''Constitution''-class]] had been. It was hoped adaptability and standardization of parts would make these new vessels much easier to build and maintain anywhere in the Federation.

Designers quickly settled on the [[Sovereign class|''Sovereign''-class]] as the basis for the design. This resulted in the ''Inquiry'' having many of the latest systems while also focusing on tried-and-true systems where it best served the needs of the ship. Adaptations were made to propulsion, sensors, as well as the offensive and defensive systems. These, along with advancements in processing and interface components, made it possible for the ''Inquiry'' to operate with the capabilities of a much larger starship while still being able to move and react like a much smaller one.

The timeline for design and construction proved surprisingly short, with the ''USS Inquiry'' being launched in 2390. Field testing proved successful and engineers as well as fleet command staff were pleased by the results. High priority was placed on subsequent production, with the goal of having over two hundred vessels in service by the end of the twenty-fourth century. Yet, the ''Inquiry'' has also sparked much debate among the upper echelons of Starfleet. Some argue the organization is taking too belligerent and militaristic a stance while others point out that it is simply avoiding mistakes of the past by investing in the Federation's future security.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[[memoryalpha:USS Zheng He|''USS Zheng He'']] (NCC-86505)

==Appendices==

===Background Information===
*The ''Inquiry''-class was first seen in the episode [[memoryalpha:Et in Arcadia Ego, Part 2 (episode)|"Et in Arcadia Ego, Part 2" (''PIC'')]]. Very little information is known about this design, including why there were several variants in the episode. Screenwriter and producer [https://memory-alpha.fandom.com/wiki/Michael_Chabon Michael Chabon] identified the class name in a tweet.
*The ''Inquiry''-class was introduced to the Pegasus Fleet community by the resources team following its appearance on [[memoryalpha:Star Trek: Picard|''Star Trek: Picard'']]. Much of the information presented currently has been developed by extrapolation from canon sources.

===Writing Notes===
By the year 2399, [[Starfleet]] was able to field at least two hundred ''Inquiry''-class vessels. Captain William Riker even boasted them to be the "toughest, fastest, most powerful ship Starfleet ever put into service". Therefore, it would not be uncommon for sims operating at or near the edges of the [[United Federation of Planets|Federation]] to bump into one during a mission, especially if they are investigating possible threats or acting as the response to a threat already identified or encountered by another ship. In fact, depending on the threat, Starfleet may be willing to send several ''Inquiry''-class ships at a time.

While the initial assumption can be to assume anyone posted to an ''Inquiry'' is more of a hardline militarist, that is only true of a small fraction of the crews serving aboard this class. Most have a strong sense of duty and believe that they are serving to protect the Federation. In their minds, the best fight is the one in which they don't have to fire a shot. Thus, a majority of ''Inquiry'' captains see their role as policing (i.e. a stern word being better than a volley of quantum torpedoes). They also tend to see themselves as the "cavalry" coming to the rescue, willing to put themselves in harm's way to protect others.

Although engineers typically don't mind being on such an advanced ship, science and medical personnel tend to find such postings at odds with their careers. Very few would consider it as being one of their top ten choices. Conversely, those who grew up with tales of heroism and glory during the Dominion War might find such an assignment appealing, only to discover the reality much different from the picture painted for them.

==Related Links==
*[https://memory-alpha.fandom.com/wiki/Inquiry_class ''Inquiry'' class] at ''Memory Alpha''

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

Inquiry class

2022-03-26T17:15:26Z

Clement: Created page with sidebar template, history, etc. (still needs specifications)

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Inquiryclass.png|350px]]
| name = Inquiry
| affiliation = [[Starfleet]]
| role = Heavy Cruiser
| precedingclass =
| succeedingclass =
| dateentered = 2390
| expectedruration =
| expectedrefit =
| timeresupply =
| crewcomplement =
| emergencycap =
| length = 640.1 meters
| width =
| diameter =
| height =
| decks =
| propulsionsystem =
* matter/anti-matter warp drive
| cruisespeed =
| maxspeed =
| emergencyspeed =
| energyweapons =
| torplaunchers =
| torppayload =
| shields =
| defense =
| facilities =
| auxcraft =
| msd =
}}

The '''''Inquiry''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. Designed in response to Starfleet's defense-oriented turn in the late 2380s, the ''Inquiry''-class heavy cruiser is a fast, well-armed starship deployed in large numbers near the Federation's borders.

==History==
Development on the ''Inquiry''-class began during a period of major upheaval for the [[:category:Alpha Quadrant|Alpha]] and [[:category:Beta Quadrant|Beta Quadrants]]. In particular, the loss of the ''[[memoryalpha:Utopia Planitia Fleet Yards|Utopia Planitia Fleet Yards]]'' in 2385 and the sharp political changes that surrounded that incident put Starfleet in a difficult position. They needed to find a way of restoring their fleet numbers and projecting strength quickly without the support of (arguably) one of their most vital production facilities. And yet, they were greatly limited by the [[memoryalpha:Federation Council|Federation Council]]'s hesitancy to green-light major projects.

Eventually, a successful argument was made and a new generation of designs began to take shape on the drawing board. In an effort to overcome the challenges that arose with earlier designs, such as the [[Prometheus class|''Prometheus''-class]]' and its multi-vector assault mode systems, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] aimed for something that would be more open to upgrades like the [[Constitution class|''Constitution''-class]] had been. It was hoped adaptability and standardization of parts would make these new vessels much easier to build and maintain anywhere in the Federation.

Designers quickly settled on the [[Sovereign class|''Sovereign''-class]] as the basis for the design. This resulted in the ''Inquiry'' having many of the latest systems while also focusing on tried-and-true systems where it best served the needs of the ship. Adaptations were made to propulsion, sensors, as well as the offensive and defensive systems. These, along with advancements in processing and interface components, made it possible for the ''Inquiry'' to operate with the capabilities of a much larger starship while still being able to move and react like a much smaller one.

The timeline for design and construction proved surprisingly short, with the ''USS Inquiry'' being launched in 2390. Field testing proved successful and engineers as well as fleet command staff were pleased by the results. High priority was placed on subsequent production, with the goal of having over two hundred vessels in service by the end of the twenty-fourth century. Yet, the ''Inquiry'' has also sparked much debate among the upper echelons of Starfleet. Some argue the organization is taking too belligerent and militaristic a stance while others point out that it is simply avoiding mistakes of the past by investing in the Federation's future security.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[[USS Vesta|''USS Vesta'']] (NX-82601)
*[[USS Niagara (NCC-80485-B)|''USS Niagara'']] (NCC-80485-B)

==Appendices==

===Background Information===
*The ''Inquiry''-class was first seen in the episode [[memoryalpha:Et in Arcadia Ego, Part 2 (episode)|"Et in Arcadia Ego, Part 2" (''PIC'')]]. Very little information is known about this design, including why there were several variants in the episode. Screenwriter and producer [https://memory-alpha.fandom.com/wiki/Michael_Chabon Michael Chabon] identified the class name in a tweet.
*The ''Inquiry''-class was introduced to the Pegasus Fleet community by the resources team following its appearance on [[memoryalpha:Star Trek: Picard|''Star Trek: Picard'']]. Much of the information presented currently has been developed by extrapolation from canon sources.

===Writing Notes===
By the year 2399, [[Starfleet]] was able to field at least two hundred ''Inquiry''-class vessels. Captain William Riker even boasted them to be the "toughest, fastest, most powerful ship Starfleet ever put into service". Therefore, it would not be uncommon for sims operating at or near the edges of the [[United Federation of Planets|Federation]] to bump into one during a mission, especially if they are investigating possible threats or acting as the response to a threat already identified or encountered by another ship. In fact, depending on the threat, Starfleet may be willing to send several ''Inquiry''-class ships at a time.

While the initial assumption can be to assume anyone posted to an ''Inquiry'' is more of a hardline militarist, that is only true of a small fraction of the crews serving aboard this class. Most have a strong sense of duty and believe that they are serving to protect the Federation. In their minds, the best fight is the one in which they don't have to fire a shot. Thus, a majority of ''Inquiry'' captains see their role as policing (i.e. a stern word being better than a volley of quantum torpedoes). They also tend to see themselves as the "cavalry" coming to the rescue, willing to put themselves in harm's way to protect others.

Although engineers typically don't mind being on such an advanced ship, science and medical personnel tend to find such postings at odds with their careers. Very few would consider it as being one of their top ten choices. Conversely, those who grew up with tales of heroism and glory during the Dominion War might find such an assignment appealing, only to discover the reality much different from the picture painted for them.

==Related Links==

[[Category:Federation starship classes]]
[[Category:Heavy Cruisers]]

File:Inquiryclass.png

2022-03-26T17:14:40Z

Clement:

Eleventh Fleet

2022-03-26T16:06:30Z

Clement: Updated interwiki links

__NOEDITSECTION__
{{Icons|pfc}}
{{Task_Force
| name = Eleventh Fleet
| seal = [[Image:PF-logo.png|325px]]
| areaofops = Milky Way Galaxy
| designation = Pegasus Fleet
| url = [https://pegasusfleet.net/ Pegasus Fleet]
| sims =
|co=Fleet Admiral [[Emily Quinn]]
|xo=Admiral [[S'iraa]]
|cas=
}}
The '''Eleventh Fleet''', colloquially known as '''Pegasus Fleet''', is one of the numbered fleets that make up the [[United Federation of Planets|Federation]] [[Starfleet]]. Founded in response to incursions and rising threats of the 2360s and 70s, it was rendered inactive after being destroyed at the Battle of Benzar during the Dominion War. The fleet was later re-established in the mid-2380s to ease strain on Federation resources as well as mitigate concerns that Starfleet had been neglecting the worlds of the frontier regions. Since then, the Eleventh Fleet has taken on additional duties and responsibilities throughout Federation space and beyond, including providing the core element of the Delta Quadrant Exploratory Group.

==Overview==
The Eleventh Fleet was one of several that saw considerable action during the early days of the [[memoryalpha:Dominion War|Dominion War]], often dispatched to help shore up defenses and assist other fleets weakened by Dominion attacks. In early 2374, the fleet was redeployed to protect Benzar, homeworld of a key member of the Federation. However, they were caught by surprise, quickly overwhelmed, and eventually destroyed by a Dominion strike force. Subsequently, Starfleet placed the Eleventh Fleet on inactive status, opting to transfer the remaining personnel and assets to other fleets.

Following the war, Starfleet was faced with the monumental task of establishing a foundation for a post-war era. This meant dealing with multiple (often competing) interests that demanded much of their time and resources. Not only were they concerned about the rebuilding within the Federation, they were also responsible for assisting in the [https://memory-beta.fandom.com/wiki/Cardassia#Post-Dominion_War_recovery Cardassian reconstruction], and later the [[memoryalpha:Romulan_sun#The_Romulan_supernova|Romulan evacuation]]. Further complicating matters was the fact that some who believed the Federation had not focused enough on the frontier regions began to speak of leaving.

It became increasingly clear that something needed to be done to better address these needs. And so, by the early 2380s, Starfleet Command had started to reconstitute several of its inactive fleets. Vice Admiral Roman Sanchez was assigned to oversee the reactivation of the Eleventh Fleet. Most of the assets that Sanchez chose to become part of the reformed fleet, nicknamed ‘Pegasus’ after the admiral’s well-known style in battle, were drawn from what remained of the Starfleet reserves or from other active fleets and captained by freshly-promoted officers.

The fleet’s headquarters was soon established on [[Cestus III]] and it was given responsibility for a patrol zone spanning much of the galactic-south of Federation territory, sharing borders with the Tholians, Klingons, Gorn, and Metron Consortium. Official operations began in 2386 and, within three years, the Eleventh Fleet had established itself and proven itself capable of carrying out its duties in the Galactic South. In light of this, [[memoryalpha:Starfleet Command|Starfleet Command]] ordered an expansion of their operations into other areas of Federation space and beyond.

In 2392, the Eleventh Fleet took on additional responsibility for providing core elements of a new [[Delta Quadrant Exploratory Group]] based out of the [[Iota system]].

==Major Events==
* '''2374:''' Eleventh Fleet is destroyed by Dominion strike force at the Battle of Benzar
* '''2386:''' Vice Admiral Sanchez reactivates Eleventh Fleet, headquarters on Cestus III
* '''2389:''' Starfleet Command orders expansion of Eleventh Fleet operations into areas of Federation space beyond the Galactic South
* '''2392:''' Eleventh Fleet provides core elements of new Delta Quadrant Exploratory Group
* '''2394:''' [[graviton catapult|graviton catapults]] shut down following major accident, Eleventh Fleet tasked with two-pronged effort to re-establish support lines to the exploratory group

Quantum slipstream drive

2022-02-14T01:02:06Z

Clement: Created page with "__NOEDITSECTION__ The '''quantum slipstream drive''' (also known as '''quantum slipstream''', '''slipstream drive''', or simply '''QSD''') is an advanced form of propulsion technology that allows for travel across vast distances at speeds far exceeding that of conventional warp drive. It is believed to have been originally developed by a Delta Quadrant race with the Borg designation, "Species 116". ==History== ===..."

__NOEDITSECTION__
The '''quantum slipstream drive''' (also known as '''quantum slipstream''', '''slipstream drive''', or simply '''QSD''') is an advanced form of propulsion technology that allows for travel across vast distances at speeds far exceeding that of conventional warp drive. It is believed to have been originally developed by a [[:Category:Delta Quadrant|Delta Quadrant]] race with the Borg designation, [[memoryalpha:Species 116|"Species 116"]].

==History==
===Early Encounters===
The crew of the ''[[memoryalpha:USS Voyager|USS Voyager]]'' first encountered slipstream technology in 2374 when they discovered the ''[[memoryalpha:USS Dauntless|USS Dauntless NX-01-A]]'', a vessel they were made to believe was sent by Starfleet to transport them back home to the [[:Category:Alpha Quadrant|Alpha Quadrant]]. It was later revealed, however, that the vessel was an elaborate ruse by an alien named Arturis and the plot was foiled by the ''Voyager'' crew. The following year, the ''Voyager'' crew managed to construct their own quantum slipstream drive using rare [[memoryalpha:benamite|benamite]] crystals. Despite the initial promise of the new drive, a phase variance was discovered in the slipstream that ultimately proved impossible for the crew to overcome.

For a time, the technology was set aside, and further development seemed unlikely until the technical specifications were delivered to [[Starfleet Command]] in 2376. Analysis of the information began almost immediately in the hope that it might yield some method of bringing the ''Voyager'' crew home. Not long afterward, a team was formed at the ''[[memoryalpha:Utopia Planitia Fleet Yards|Utopia Planitia Fleet Yards]]'' to take on the project of making quantum slipstream drive a workable reality.

''Voyager''’s safe return in 2378 meant it was no longer necessary to develop a functioning drive in order to bring them home. However, the drive’s potential for use in deep space exploration remained, and so the work continued. Having access to the physical hardware, personal experience, and full data files brought back by the ''Voyager'' crew gave the team a significant advantage. Within a relatively short time, they were ready to begin the initial testing phase.

The first official tests of Starfleet-built quantum slipstream drive began utilizing specially designed drone ships. These were followed by modified [[Intrepid class|''Intrepid'' class]] starships, and later the construction of the first [[Spirit class|''Spirit class'']] vessels, which served as the primary testbed for the next phase of slipstream development. Once the individual components had been trialed in the field, engineers moved into yet another phase, utilizing the ''Voyager'' crew’s thorough analysis of the ''Dauntless'' to construct a detailed replica, the ''[[memoryalpha:USS Dauntless (NCC-80816)|USS Dauntless (NCC-80816)]]''. By 2383, this version of the vessel had completed rigorous testing and been deployed to the field, where it was used in Admiral Janeway’s search for the ''[[memoryalpha:USS Protostar|USS Protostar]]''.

Not long after initial construction of the ''Dauntless'' prototype, the discovery that the Romulan sun would explode brought changes to large portions of Starfleet. The re-prioritization of ''Utopia Planitia'' toward a total emphasis on the evacuation fleet shifted primary responsibility for the slipstream project (including the new [[Vesta class|''Vesta'' class]] design) to the ''[[memoryalpha:40 Eridani A Starfleet Construction Yards|40 Eridani A Starfleet Construction Yards]]'' in orbit of Vulcan. This proved fortuitous in that, despite the [[memoryalpha:Attack on Mars|attack on Mars]] in 2385, the project was able to continue unabated.

Commissioned at ''40 Eridani A Yards'' in 2386, the prototype ''[[USS Vesta]]'' was dispatched to the [[Eleventh Fleet]] patrol zone to conduct her shakedown and slipstream trials away from the core worlds. The results of these trials were found to be in line with those of earlier testing. Although a few of the tests did uncover some flaws that the smaller test vessels did not experience, refinements to the system and additional tuning of the ''Vesta'' spaceframe ultimately proved the system’s viability for use aboard larger starships.

==Technology==
===Operational Parameters===
The current Starfleet quantum slipstream drive system maintains a cruising velocity of three hundred (300) light years per hour. This can be sustained for a period of up to twelve (12) hours before the auto-shutdown sequence is initiated. Forty (40) minutes of preparation, inspection, and warm-up are required before making a standard slipstream jump. Afterwards, a minimum of nine-point-eight (9.8) hours’ down time per one (1) hour of flight time is required, and a minimum of five (5) days total if the auto-shutdown sequence was initiated.

Any attempt to activate the quantum slipstream drive before the cool-down cycle has been completed presents an ''extreme'' risk of slipstream failure and the ''significant'' possibility that the vessel in question will be severely damaged or destroyed.

The benamite crystals utilized in the quantum slipstream drive are rare, unstable, and extremely difficult to synthesize. The supply of crystals allotted to each vessel equipped with a quantum slipstream drive has only a finite use as the crystals are in a constant state of decay, a problem exacerbated by their use. When operational guidelines are followed, the benamite matrix will require servicing at a qualified shipyard as part of standard refit procedures. If the operational parameters are exceeded, the benamite matrix will last significantly less time.

Failure to abide by Starfleet regulations when utilizing the quantum slipstream drive will result in an investigation and a hearing at which disciplinary action may be taken.

===Security Concerns===
Starfleet Command has ordered the strictest security and marked all materials pertaining to the quantum slipstream drive as classified. This is largely due to the anticipated impact such technology will have on the balance of power across the [[:Category:Alpha Quadrant|Alpha]] and [[:Category:Beta Quadrant|Beta Quadrants]]. While it is expected that other powers will eventually become aware of the drive’s existence, Starfleet considers it of paramount importance that the specifications are not allowed to pass into the hands of non-Starfleet personnel.

===Compatible Ship Classes===
As standard:
*[[Spirit class|''Spirit'' class]]
*[[Dauntless class|''Dauntless'' class]]
*[[Vesta class|''Vesta'' class]]
*[[Odyssey class|''Odyssey'' class]] (Mk II refit)

As refit:
*[[Intrepid class|''Intrepid'' class]]

==Alternate Timelines==
===''Vesta''’s failure===
One alternate version of the ''[[USS Vesta]]'' existed in a timeline where development of the quantum slipstream drive was initially considered a failure. Early testing proceeded as it had in the prime timeline and, although reports seemed promising, the end results were far less than what had been hoped for. The ''Vesta'' prototype returned to drydock for retrofitting while subsequent [[Vesta class|''Vesta'' class]] starships were constructed without quantum slipstream capabilities.

==Writing Notes==
*Use of the quantum slipstream drive aboard any sim requires that a written request be submitted to and approved by the Department of Resources.

==Related Links==
*[[memoryalpha:Quantum slipstream drive|Quantum slipstream drive]] at ''Memory Alpha''

File:Odysseyclass.png

2022-01-03T00:19:28Z

Clement:

Odyssey class

2022-01-03T00:17:27Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Specifications | image = 350px | name = Odyssey | affiliation = Starfleet | role = Explorer | precedingclass = | succeedingclass = | dateentered = 2381 | expectedruration = 100 years | expectedrefit = * 5 years (minor) * 20 years (major) | timeresupply = 3-5 years | crewcomplement = 2,502 persons * 417 officers * 2,085 enlisted | emergencycap = 10,608 persons | length = 1061.1 meters | width = 371.9 meters..."

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Odysseyclass.png|350px]]
| name = Odyssey
| affiliation = [[Starfleet]]
| role = Explorer
| precedingclass =
| succeedingclass =
| dateentered = 2381
| expectedruration = 100 years
| expectedrefit =
* 5 years (minor)
* 20 years (major)
| timeresupply = 3-5 years
| crewcomplement = 2,502 persons
* 417 officers
* 2,085 enlisted
| emergencycap = 10,608 persons
| length = 1061.1 meters
| width = 371.9 meters
| diameter =
| height = 147.9 meters
| decks = 37 decks
| propulsionsystem =
* matter/anti-matter warp drive
* [[quantum slipstream drive]]
| cruisespeed = Warp 8
| maxspeed = Warp 9.6
| emergencyspeed = Warp 9.99 (for 12 hours)
| energyweapons =
* 12 phaser arrays
| torplaunchers =
* 2 forward launchers
* 2 aft launchers
| torppayload =
* photon torpedoes
* quantum torpedoes
* probes
| shields =
* standard shielding system
| defense =
* ablative hull armor
* duranium/tritanium double hull
* structural integrity field
| facilities =
* 3 shuttlebays
| auxcraft =
* 30 shuttlecraft
* 6 transports
* 12 maintenance craft
| msd =
}}

The '''''Odyssey''-class''' starship was a [[Starfleet]] vessel first introduced in the early 2380s. It was one of the largest and most powerful [[United Federation of Planets|Federation]] starship classes of its time, a true successor to the earlier [[Galaxy class|''Galaxy''-class]].

==Class History==
Development of the ''Odyssey''-class began in the early 2370s. Even as the [[Sovereign class|''Sovereign''-class]] was entering service, the [[memoryalpha:Starfleet Corps of Engineers|Starfleet Corps of Engineers]] looked ahead to its next groundbreaking achievement. It was felt by some that the ''Sovereign'' had been pressed into service too soon, largely in an effort to meet the Borg threat, and that this had significantly altered the trajectory of the class itself. The plan moving forward was to design a vessel that would succeed (and ultimately surpass) both the [[Galaxy class|''Galaxy''-class]] and the ''Sovereign''-class by building upon the lessons learned from each.

No one could have imagined such a design would need to have been implemented so quickly, especially with the ''Galaxy''- and ''Sovereign''-classes still actively serving frontline duties. Yet, circumstances changed and Starfleet’s experiences with the [[memoryalpha:Dominion War|Dominion War]] pressured engineers to once again push ahead earlier than they had planned.

The keel for the ''USS Odyssey'' was laid down in 2376 at the ''San Francisco Fleet Yards''. Work began on a second vessel, the ''USS Verity'', soon afterward at the [[memoryalpha:Utopia Planitia Fleet Yards|''Utopia Planitia Fleet Yards'']]. Conflicts between the ''Odyssey'', ''Ascension'', and ''Excalibur'' projects, however, led to tension among the respective design teams and a stiff competition for resources. Ultimately, the ''Odyssey''-class was deemed a higher priority and the necessary resources were allocated accordingly.

Despite these protests and setbacks, both the ''Odyssey'' and the ''Verity'' were launched in 2381, five years after construction had begun. They quickly proved their worth in field trials as well as on active duty and were considered by many to be a successful demonstration of the project. Unfortunately, their size placed certain limitations on the number of vessels that could be constructed, fielded, or otherwise serviced by existing fleet yards. These included the amount of physical resources as well as the personnel available. Still, [[Starfleet]] had every intention of requisitioning the class for serial production.

That all changed with the [[memoryalpha:Attack on Mars|destruction of the ''Utopia Planitia Fleet Yards'']] in 2385. The Starfleet Corps of Engineers immediately put a hold on further production, first to address the more urgent need of sorting out the aftermath of the attack, and then to seek other [[United Federation of Planets|Federation]] facilities with the resources and the infrastructure to support such a project. They eventually identified the ''San Francisco Fleet Yards'', the ''40 Eridani A Starfleet Construction Yards'', and the ''Gavor Shipyards'' as possible candidates for when the time came to resume.

The ''Odyssey'' and ''Verity'' were the absolute pinnacle of Starfleet engineering upon their launch. However, the Corps of Engineers knew that would not always be the case. Thus, it was always their intent to further upgrade and modernize the class as new capabilities and technologies became available, allowing it to remain relevant well into the future. This enabled them to use the hold on production to refine the design and to incorporate systems that had been field tested on other starships during the interim. Most notable for the Mark II ''Odyssey''-class was the addition of [[quantum slipstream drive]] and enhanced sensor arrays.

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[https://memory-beta.fandom.com/wiki/USS_Odyssey_(NX-97000) ''USS Odyssey''] (NX-97000)
*[https://memory-beta.fandom.com/wiki/USS_Verity ''USS Verity''] (NCC-97000)
*[[USS Astraea (NCC-80895-A)|''USS Astraea'']] (NCC-80895-A)

==Appendices==

===Background Information===

===Writing Notes===
The ''Odyssey''-class is by far one of the largest starship designs ever fielded by Starfleet, second only to the [[Valkyrie class|''Valkyrie''-class]] ''USS Dreadnought''. Similar to the [[Vesta class|''Vesta''-class]], encountering a vessel of this type as an NPC would be ''extremely'' unusual as there are literally only a handful currently operating throughout the entire Federation. Characters should be impressed, proud, and perhaps humbled to even set foot aboard one.

It makes sense, then, that serving aboard an ''Odyssey''-class starship would be as prestigious (if not moreso) than even the much sought after [[Vesta class|''Vesta''-class]]. All personnel are most likely to be the best in their fields and, given the ship's size and importance, it's not unheard of for certain department heads (e.g. chief engineer, chief medical officer, executive officer) to hold the rank of captain alongside the commanding officer.

In cases where the vessel is being used as a flagship for a member of the admiralty, command may be assigned to a relatively junior captain who oversees the daily operations on behalf of the flag officer. Ships not utilized for this purpose are assigned to senior captains with considerable experience in long-range exploratory and diplomatic missions.

''Special Note: Because of their unique role as flagships and emissaries on behalf of the Federation, an ''Odyssey''-class starship may include departments not normally found aboard smaller vessels or simulations.''

==Related Links==

[[Category:Federation starship classes]]
[[Category:Explorer]]

Vesta class

2022-01-02T23:54:20Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Specifications | image = 350px | name = Vesta | affiliation = Starfleet | role = Explorer | precedingclass = | succeedingclass = | dateentered = 2386 | expectedruration = 100 years | expectedrefit = * 5 years (minor) * 20 years (major) | timeresupply = 3-5 years | crewcomplement = 750 persons * 125 officers * 625 enlisted | emergencycap = 3,080 persons | length = 672 meters | width = 195 meters | diameter =..."

__NOEDITSECTION__
{{icons|pfc}}
{{Specifications
| image = [[Image:Vestaclass.png|350px]]
| name = Vesta
| affiliation = [[Starfleet]]
| role = Explorer
| precedingclass =
| succeedingclass =
| dateentered = 2386
| expectedruration = 100 years
| expectedrefit =
* 5 years (minor)
* 20 years (major)
| timeresupply = 3-5 years
| crewcomplement = 750 persons
* 125 officers
* 625 enlisted
| emergencycap = 3,080 persons
| length = 672 meters
| width = 195 meters
| diameter =
| height = 88 meters
| decks = 22 decks
| propulsionsystem =
* matter/anti-matter warp drive
* [[quantum slipstream drive]]
| cruisespeed = Warp 9.2
| maxspeed = Warp 9.99
| emergencyspeed = Warp 9.995 (for 12 hours)
| energyweapons =
* 8 phaser arrays
* 2 phaser cannons
| torplaunchers =
* 2 forward launchers
* 2 aft launchers
| torppayload =
* photon torpedoes
* quantum torpedoes
* probes
| shields =
* standard shielding system
| defense =
* ablative hull armor
* duranium/tritanium double hull
* structural integrity field
| facilities =
* 3 shuttlebays
| auxcraft =
* 26 shuttlecraft
* 4 transports
* 8 maintenance craft
| msd =
}}

The '''''Vesta''-class''' starship was introduced by the [[United Federation of Planets|Federation]] [[Starfleet]] in the late [[memoryalpha:24th century|24th century]]. It was created to be a multi-mission explorer and was a test-bed for a number of experimental technologies including the [[quantum slipstream drive]].

==History==
Development of the ''Vesta''-class can be traced back to the triumphant return of the [[memoryalpha:USS Voyager|''USS Voyager'']] in 2378. After nearly seven years in the [[:Category:Delta Quadrant|Delta Quadrant]], the crew of ''Voyager'' brought back a veritable treasure trove of new technology and scientific data. It included records of their encounters with alien species, spatial phenomena, and the challenges of such a long journey without the usual support of Federation assets. This information was immediately turned over to Starfleet engineers and scientists for analysis.

While a good deal of what they learned was able to be incorporated into existing starship classes, other aspects lent themselves more readily to the development of new designs. One item in particular that fascinated them was the [[quantum slipstream drive]] encountered by ''Voyager'' in 2374. Although an attempt by the ''Voyager'' crew to recreate and utilize slipstream technology as a way of hastening their trip home proved almost disastrous, Starfleet engineers saw potential and spent months studying the data. They eventually managed to improve upon ''Voyager'''s efforts and create a functioning, albeit simulated model of the drive system.

Trials using the simulated drive system appeared to show the technology was viable. However, the only way to prove its effectiveness was to develop a physical working model and test it aboard an actual vessel. This was done using the specially designed [[Spirit class|''Spirit''-class]] courier. The results seemed to confirm what had been produced during the simulated trials and paved the way for what would eventually become the ''Vesta''-class starship.

Although much of the initial research and conceptual design had been done by the engineers at ''Utopia Planetia Fleet Yards'', the prioritization of the Romulan evacuation fleet in 2381 caused a major shift in the project. Development of quantum slipstream technology and the ''Vesta''-class was relocated to the ''40 Eridani A Starfleet Construction Yards'' in orbit of Vulcan where the prototype was laid down in early 2385. Construction was overseen by [[memoryalpha:Captain|Captain]] [[Emily Quinn]] who assumed command of the vessel upon its commissioning the following year.

After fitting out, the ''Vesta'' trained at testing grounds just outside the Vulcan system. She then set out for the [[Eleventh Fleet]] patrol zone and arrived at [[Starbase 332|''Starbase 332'']] for resupply. Over the ensuing month, the ''Vesta'' conducted her shakedown and slipstream trials away from civilized areas. The results of these trials were found to be in line with those of earlier testing. Although testing did uncover some flaws the smaller test vessels did not experience, refinements to the system and additional tuning of the ''Vesta'' spaceframe ultimately proved the system's viability for use aboard larger starships. ("''The Next Great Experiment''").

==Mission and Purpose==
'''Content Coming Soon'''

==Shipboard Life==
'''Content Coming Soon'''

==Ships Commissioned==
*[[USS Vesta|''USS Vesta'']] (NX-82601)
*[[USS Niagara (NCC-80485-B)|''USS Niagara'']] (NCC-80485-B)

==Appendices==

===Background Information===
*The design of the ''Vesta''-class is by [https://memory-beta.fandom.com/wiki/Mark_Rademaker Mark Rademaker], who drew influence from several ships including the [[Intrepid class|''Intrepid''-class]] and [[memoryalpha:USS Dauntless|''USS Dauntless'']], as both had previously used slipstream.
*The ''Vesta''-class was introduced to the Pegasus Fleet community by [[User:Emily_Quinn|Emily Quinn]]. Additional class info was developed by the resources team.

===Writing Notes===
The ''Vesta''-class is one of the most complex starship designs in Starfleet history, due in large part to the integrated [[quantum slipstream drive]]. As such, there are only a limited number of ''Vesta''-class starships currently in operation, making them a rare sight. Encountering a vessel of this type as an NPC would be ''extremely'' unusual as they are typically assigned to important, long-range exploratory missions at or beyond the limits of [[United Federation of Planets|Federation]] space.

Serving aboard a ''Vesta''-class starship is among the more prestigious assignments in all of [[Starfleet]]. Individuals, particularly those being considered for command or other leadership responsibilities, are often the best in their given field. Because of this, many view being assigned to one of these rare vessels as the culmination of their career (or, at least, a major high point). Command is only given to those who have considerable experience, either in command of other starships or as the executive officer of an explorer.

==Related Links==

[[Category:Federation starship classes]]
[[Category:Explorers]]

File:Vestaclass.png

2022-01-02T23:45:16Z

Clement:

Category:Starfleet Onboard Departments

2022-01-02T21:53:19Z

Clement:

__NOEDITSECTION__
Every unit in Starfleet (whether a starship, station, or planetary facility) has a command structure. As part of this structure, each member of the crew is assigned a position in a department within one of the three divisions of Starfleet - Command, Operations, and Science. This category includes descriptions of all departments found aboard most vessels and bases. Individual position descriptions are found in each department's article.

''Note: Commanding officers have a wide degree of latitude when it comes to determining the structure of their unit, meaning these positions can vary to meet the specific needs of a particular ship or base.''

==Command Division==
[[File:R-blank.png|alt=The division color for command: red.|thumb|The division color for command: red.]]
The command division is denoted by the color red. It includes the unit-level departments of command, flight operations, tactical, strategic operations, and intelligence. Other more specialized departments also included within this category, but which are not strictly part of this division, include the Judge-Advocate General's Corps and the diplomatic services.
* [[Command Department]]
* [[Flight Operations Department]]
* [[Tactical Department]]
* [[Strategic Operations Department]]
* [[Intelligence Department]]
* [[Judge-Advocate General's Corps Detachment]]
* [[Starfleet Diplomatic Corps Detachment]]

==Operations Division==
[[File:Y-blank.png|alt=The division color for operations: gold.|thumb|The division color for operations: gold.]]
The operations division is denoted by the color gold. It includes a wide variety of departments related to the safe operation of Starfleet's many assets. At the unit-level, departments in this division include operations, engineering, security, and communications. Aboard starships, communications is often included with operations and, on occasion, security and tactical may be combined into a single department.
* [[Operations Department]]
* [[Engineering Department]]
* [[Security Department]]
* [[Communications Department]]

==Sciences Division==
[[File:T-blank.png|alt=The division color for sciences: blue.|thumb|The division color for sciences: blue.]]
The sciences division is denoted by the color blue. It includes the science, medical, and counseling departments, all of which are tied to Starfleet's core exploratory and humanitarian missions. The science department itself may have many sub-departments, especially on larger ships and bases, while counseling might itself be considered a sub-department of medical, depending upon the vessel or installation.
* [[Science Department]]
* [[Medical Department]]
* [[Counseling Department]]

Category:Starfleet Onboard Departments

2022-01-02T21:53:04Z

Clement: Created page with "Every unit in Starfleet (whether a starship, station, or planetary facility) has a command structure. As part of this structure, each member of the crew is assigned a position in a department within one of the three divisions of Starfleet - Command, Operations, and Science. This category includes descriptions of all departments found aboard most vessels and bases. Individual position descriptions are found in each department's article. ''Note: Commanding officers have a..."

Every unit in Starfleet (whether a starship, station, or planetary facility) has a command structure. As part of this structure, each member of the crew is assigned a position in a department within one of the three divisions of Starfleet - Command, Operations, and Science. This category includes descriptions of all departments found aboard most vessels and bases. Individual position descriptions are found in each department's article.

''Note: Commanding officers have a wide degree of latitude when it comes to determining the structure of their unit, meaning these positions can vary to meet the specific needs of a particular ship or base.''

==Command Division==
[[File:R-blank.png|alt=The division color for command: red.|thumb|The division color for command: red.]]
The command division is denoted by the color red. It includes the unit-level departments of command, flight operations, tactical, strategic operations, and intelligence. Other more specialized departments also included within this category, but which are not strictly part of this division, include the Judge-Advocate General's Corps and the diplomatic services.
* [[Command Department]]
* [[Flight Operations Department]]
* [[Tactical Department]]
* [[Strategic Operations Department]]
* [[Intelligence Department]]
* [[Judge-Advocate General's Corps Detachment]]
* [[Starfleet Diplomatic Corps Detachment]]

==Operations Division==
[[File:Y-blank.png|alt=The division color for operations: gold.|thumb|The division color for operations: gold.]]
The operations division is denoted by the color gold. It includes a wide variety of departments related to the safe operation of Starfleet's many assets. At the unit-level, departments in this division include operations, engineering, security, and communications. Aboard starships, communications is often included with operations and, on occasion, security and tactical may be combined into a single department.
* [[Operations Department]]
* [[Engineering Department]]
* [[Security Department]]
* [[Communications Department]]

==Sciences Division==
[[File:T-blank.png|alt=The division color for sciences: blue.|thumb|The division color for sciences: blue.]]
The sciences division is denoted by the color blue. It includes the science, medical, and counseling departments, all of which are tied to Starfleet's core exploratory and humanitarian missions. The science department itself may have many sub-departments, especially on larger ships and bases, while counseling might itself be considered a sub-department of medical, depending upon the vessel or installation.
* [[Science Department]]
* [[Medical Department]]
* [[Counseling Department]]

File:Y-blank.png

2022-01-02T21:45:44Z

Clement:

File:T-blank.png

2022-01-02T21:45:07Z

Clement:

File:R-blank.png

2022-01-02T21:44:54Z

Clement:

Category:Gamma Quadrant

2022-01-02T21:31:44Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Quadrant | name = Gamma | image = 350px | major powers = * The Dominion | minor powers = | important sectors = | important places = * Bajoran Wormhole }} The '''Gamm Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "north-west" region of the galactic map, adjacent to the Alpha Quadrant and the :Categ..."

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Gamma
| image = [[File:quadrants.png|350px]]
| major powers = * The [[memoryalpha:Dominion|Dominion]]
| minor powers =
| important sectors =
| important places = * Bajoran Wormhole
}}

The '''Gamm Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "north-west" region of the galactic map, adjacent to the [[:Category:Alpha Quadrant|Alpha Quadrant]] and the [[:Category:Delta Quadrant|Delta Quadrant]].

==Overview==
Almost as little is known about the Gamma Quadrant as its neighbor, the [[:Category:Delta Quadrant|Delta Quadrant]], due to its incredible distance from the [[United Federation of Planets|Federation]] and other [[:Category:Alpha Quadrant|Alpha]] and [[:Category:Beta Quadrant|Beta Quadrant]] powers. In fact, it was largely thought to be inaccessible until the discovery of the [[memoryalpha:Bajoran wormhole|Bajoran wormhole]] in 2369. Not only did this provide a path by which starships could traverse more easily from one quadrant to the other, it also opened up new possibilities for exploration and contact.

Despite this lack of knowledge, what is clear is that this region has been populated by various species, some of which have histories spanning millions of years. It is believed the [[memoryalpha:Hur'q|Hur'q]] of ancient Klingon legend originated from this quadrant and evidence has been found of [[memoryalpha:Iconian|Iconian]] settlements as well. Even the [[memoryalpha:Dominion|Dominion]], which continues to dominate much of the quadrant, is said to be over ten thousand years old.

Category:Delta Quadrant

2022-01-02T21:07:08Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Quadrant | name = Delta | image = 350px | major powers = * Borg Collective | minor powers = * Kazon Order * Hirogen * Ts'usugi Empire * Dalacari Republic | important sectors = | important places = * Iota system }} The '''Delta Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. I..."

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Delta
| image = [[File:quadrants.png|350px]]
| major powers = * [[memoryalpha:Borg Collective|Borg Collective]]
| minor powers = * [[memoryalpha:Kazon Order|Kazon Order]]
* [[memoryalpha:Hirogen|Hirogen]]
* [[Ts'usugi Empire]]
* [[Dalacari Republic]]
| important sectors =
| important places = * [[Iota system]]
}}

The '''Delta Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "north-east" region of the galactic map, adjacent to the [[:Category:Beta Quadrant|Beta Quadrant]] and the [[:Category:Gamma Quadrant|Gamma Quadrant]].

==Overview==
Unlike the other three quadrants of the galaxy, which appear to have been dominated by one or more major political entities, the Delta Quadrant is largely decentralized in terms of political landscape. Although hundreds of interstellar powers have been documented, they are spread out across thousands of light-years. Most have had no communication with and little knowledge of each other except for their closest neighbors.

Some factions, such as the [[memoryalpha:Vaadwaur|Vaadwaur]] or the [[memoryalpha:Krenim Imperium|Krenim Imperium]], have been known to exert enormous influence in the past. However, none have persisted into the late [[memoryalpha:24th century|24th century]]. This may be caused in part by the presence of the [[memoryalpha:Borg Collective]] who, up until recently, maintained a fearsome control over large sections of the quadrant.

Since the return of the [[memoryalpha:USS Voyager|''USS Voyager'']] in 2378, Starfleet and others have taken a renewed interest in exploring the far-flung reaches of this remote region of space. Yet, it was not until the advent of the [[Delta Quadrant Exploratory Group]] that any concerted effort involving crewed vessels was undertaken to revisit the quadrant.

Category:Alpha Quadrant

2022-01-02T20:45:47Z

Clement: added image for info sidebar

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Alpha
| image = [[File:quadrants.png|350px]]
| major powers = * [[United Federation of Planets]]
* [[Cardassian Union]]
* [[Ferengi Alliance]]
* [[Tholian Assembly]]
* [[Breen Confederacy]]
| minor powers = * [[Tzenkethi Coalition]]
* Talarian Republic
| important sectors = * Sector 001
* Bajor Sector
* Former [[memoryalpha:Demilitarized Zone|Demilitarized Zone]]
| important places = * Sol
* Bajoran Wormhole
}}

The '''Alpha Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "south-west" region of the galactic map, adjacent to the [[:Category:Beta Quadrant|Beta Quadrant]] and the [[:Category:Gamma Quadrant|Gamma Quadrant]].

==Overview==
The Alpha Quadrant is home to a number of major and minor political entities. Of these, the largest by far is the [[United Federation of Planets]], with its capital, [[memoryalpha:Earth|Earth]], being located on the border with the neighboring [[:Category:Beta Quadrant|Beta Quadrant]]. Nearly half of all Federation territory lies within the Alpha Quadrant, including a number of major member worlds.

Other major Alpha Quadrant powers include the [[Cardassian Union]] and the [[Klingon Empire]], though the majority of the territory held by the latter is found in the Beta Quadrant. This was also true of the former [[Romulan Star Empire]] until it collapsed following the [[memoryalpha:Romulan sun#The Romulan supernova|supernova of 2387]].

Many of the remaining powers are divided into two groups. Some, like the [[Ferengi Alliance]], achieve a place on the galactic stage through trade and engagement with other powers. Meanwhile, many of the more isolationist governments like the [[Breen Confederacy]], the [[Tholian Assembly]], and the [[Tzenkethi Coalition]] are known to defend their territory aggressively against outsiders.

As of the late [[memoryalpha:24th century|24th century]], the Federation is believed to have explored less than half of the quadrant, though much of this space consists of the distant galactic rim.

Category:Beta Quadrant

2022-01-02T20:45:17Z

Clement: added image for info sidebar

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Beta
| image = [[File:quadrants.png|350px]]
| major powers = * [[United Federation of Planets]]
* [[Klingon Empire]]
* [[Romulan Free State]]
| minor powers = * [[Gorn Hegemony]]
| important sectors = * Sector 001
* Former [[memoryalpha:Romulan Neutral Zone|Romulan Neutral Zone]]
| important places = * Sol
* [[Cestus III]]
}}

The '''Beta Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "south-east" region of the galactic map, adjacent to the [[:Category:Alpha Quadrant|Alpha Quadrant]] and the [[:Category:Delta Quadrant|Delta Quadrant]].

==Overview==
For much of the last two hundred years, the Beta Quadrant has been largely divided among three major political entities. The largest of these has traditionally been the [[United Federation of Planets]], followed closely by the [[Klingon Empire]], and the former [[Romulan Star Empire]]. Their sizeable territories and political dominance have left little room for other local powers. Most were either conquered by the Klingons or the Romulans, or joined the Federation out of cooperation or a desire for protection.

Two notable exceptions to this have been the [[Gorn Hegemony]] and the [[Ritorian Confederacy]]. Whether due to their distance from the core worlds of the "big three" or some other as yet unknown factor, both have managed to navigate the balance and to emerge as minor regional powers in their own right.

Things changed dramatically following the [[memoryalpha:Romulan sun#The Romulan supernova|supernova of 2387]], casting the Beta Quadrant into unprecedented chaos. The collapse of the Romulan Empire and the dissolution of the former [[memoryalpha:Romulan Neutral Zone|Romulan Neutral Zone]] has given rise to a number of smaller Romulan factions. Of these, the most powerful and dominant appears to be the [[Romulan Free State]], though it remains to be seen how these events will affect long-term stability moving forward.

File:Quadrants.png

2022-01-02T20:44:24Z

Clement:

Category:Beta Quadrant

2022-01-02T02:14:01Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Quadrant | name = Beta | image = | major powers = * United Federation of Planets * Klingon Empire * Romulan Free State | minor powers = * Gorn Hegemony | important sectors = * Sector 001 * Former Romulan Neutral Zone | important places = * Sol * Cestus III }} The '''Beta Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "so..."

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Beta
| image =
| major powers = * [[United Federation of Planets]]
* [[Klingon Empire]]
* [[Romulan Free State]]
| minor powers = * [[Gorn Hegemony]]
| important sectors = * Sector 001
* Former [[memoryalpha:Romulan Neutral Zone|Romulan Neutral Zone]]
| important places = * Sol
* [[Cestus III]]
}}

The '''Beta Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "south-east" region of the galactic map, adjacent to the [[:Category:Alpha Quadrant|Alpha Quadrant]] and the [[:Category:Delta Quadrant|Delta Quadrant]].

==Overview==
For much of the last two hundred years, the Beta Quadrant has been largely divided among three major political entities. The largest of these has traditionally been the [[United Federation of Planets]], followed closely by the [[Klingon Empire]], and the former [[Romulan Star Empire]]. Their sizeable territories and political dominance have left little room for other local powers. Most were either conquered by the Klingons or the Romulans, or joined the Federation out of cooperation or a desire for protection.

Two notable exceptions to this have been the [[Gorn Hegemony]] and the [[Ritorian Confederacy]]. Whether due to their distance from the core worlds of the "big three" or some other as yet unknown factor, both have managed to navigate the balance and to emerge as minor regional powers in their own right.

Things changed dramatically following the [[memoryalpha:Romulan sun#The Romulan supernova|supernova of 2387]], casting the Beta Quadrant into unprecedented chaos. The collapse of the Romulan Empire and the dissolution of the former [[memoryalpha:Romulan Neutral Zone|Romulan Neutral Zone]] has given rise to a number of smaller Romulan factions. Of these, the most powerful and dominant appears to be the [[Romulan Free State]], though it remains to be seen how these events will affect long-term stability moving forward.

Category:Alpha Quadrant

2022-01-02T01:19:46Z

Clement: Created page with "__NOEDITSECTION__ {{icons|pfc}} {{Quadrant | name = Alpha | image = | major powers = * United Federation of Planets * Cardassian Union * Ferengi Alliance * Tholian Assembly * Breen Confederacy | minor powers = * Tzenkethi Coalition * Talarian Republic | important sectors = * Sector 001 * Bajor Sector * Former Demilitarized Zone | important places = * Sol * Bajoran Wormhole }} The '''Alpha Quadrant''' is the com..."

__NOEDITSECTION__
{{icons|pfc}}
{{Quadrant
| name = Alpha
| image =
| major powers = * [[United Federation of Planets]]
* [[Cardassian Union]]
* [[Ferengi Alliance]]
* [[Tholian Assembly]]
* [[Breen Confederacy]]
| minor powers = * [[Tzenkethi Coalition]]
* Talarian Republic
| important sectors = * Sector 001
* Bajor Sector
* Former [[memoryalpha:Demilitarized Zone|Demilitarized Zone]]
| important places = * Sol
* Bajoran Wormhole
}}

The '''Alpha Quadrant''' is the common designation for one of the four quarters of the Milky Way galaxy. It lies in the "south-west" region of the galactic map, adjacent to the [[:Category:Beta Quadrant|Beta Quadrant]] and the [[:Category:Gamma Quadrant|Gamma Quadrant]].

==Overview==
The Alpha Quadrant is home to a number of major and minor political entities. Of these, the largest by far is the [[United Federation of Planets]], with its capital, [[memoryalpha:Earth|Earth]], being located on the border with the neighboring [[:Category:Beta Quadrant|Beta Quadrant]]. Nearly half of all Federation territory lies within the Alpha Quadrant, including a number of major member worlds.

Other major Alpha Quadrant powers include the [[Cardassian Union]] and the [[Klingon Empire]], though the majority of the territory held by the latter is found in the Beta Quadrant. This was also true of the former [[Romulan Star Empire]] until it collapsed following the [[memoryalpha:Romulan sun#The Romulan supernova|supernova of 2387]].

Many of the remaining powers are divided into two groups. Some, like the [[Ferengi Alliance]], achieve a place on the galactic stage through trade and engagement with other powers. Meanwhile, many of the more isolationist governments like the [[Breen Confederacy]], the [[Tholian Assembly]], and the [[Tzenkethi Coalition]] are known to defend their territory aggressively against outsiders.

As of the late [[memoryalpha:24th century|24th century]], the Federation is believed to have explored less than half of the quadrant, though much of this space consists of the distant galactic rim.

File:D74-logo.png

2022-01-01T23:55:38Z

Clement:

File:TF56-logo.png

2022-01-01T23:55:22Z

Clement:

File:TF37-logo.png

2022-01-01T23:55:08Z

Clement:

File:TF11-logo.png

2022-01-01T23:54:52Z

Clement:

Template:Award

2022-01-01T22:05:25Z

Clement:

<div class="infobox">
{| width="315" align="right" cellpadding="3" cellspacing="0" style="border-radius:13px;margin-bottom:0;padding-left:10px;"
{{#if: {{{image|}}}|
{{!}} colspan="2" bgcolor={{{bgcolor_value|#222222; style="border-top-right-radius: 13px; border-top-left-radius: 13px; background: #f3f3f3 !important; color: #cccccc; font-size:smaller; text-align: center;padding: 10px;"}}} {{!}} {{{image}}} }}
|-
| colspan="2" style="text-align: center; color: #e5e5ed; font-size:larger; background-color:#304665 !important; text-align:center;padding: .3rem 1.25rem;" | '''{{{name}}}'''
|-
{{#if: {{{awardedby|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Awarded by
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{awardedby}}} }}
|-
{{#if: {{{type|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Type of Award
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{type}}} }}
|-
{{#if: {{{status|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Status
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{status}}} }}
|-
{{#if: {{{recipient|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Recipients
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{recipient}}} }}
|-
{{#if: {{{lower|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Preceding Award
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{lower}}} }}
|-
{{#if: {{{higher|}}}|
{{!}} bgcolor={{{bgcolor_value|#222222; style="background: #e0e0e0; padding:8px 10px; color: #696969; font-size:smaller; width:40%;"}}} {{!}} Succeeding Award
{{!}} bgcolor={{{bgcolor_value|#2B2B2B; style="background: #ececec; padding:8px 10px; color: #696969; font-size:smaller; width:60%;"}}} {{!}}
{{{higher}}} }}
|- class="infobox-link" style="border-radius-bottom-right: 13px; border-radius-bottom-left: 13px;"
|colspan="2" style="border-bottom-right-radius: 13px; border-bottom-left-radius: 13px; text-align: center; color: #F67F00; font-size: 8pt; background-color:#2a4667c9; text-align:center;padding: 6px 0;" | [[Template:Award]]
|}</div>
[[Category:Award]][[Category:Pegasus Fleet Policy]]
<noinclude>
<br clear=all>
<pre>
{{Award
|name=
|image=
|awardedby=
|type=
|status=
|recipient=
|lower=
|higher=
}}</pre>
[[Category:Infobox Templates|{{PAGENAME}}]]
</noinclude>