Fleet Organization

Adapted from Decipher's Star Trek Roleplaying Game: Starfleet Operations Manual, Chapter 6: Ships of the Line, "Fleet Organization", pp. 75-79

Flexible Command & Control (2133)

At the formation of the United Earth Starfleet, starships were directed upon their missions by Starfleet Command (back on Earth) and, when outside easy range of communication, authorized to act independently and with as much guidance established policy could provide. Like with the task force model of the post-Romulan War era (see below), ships would be assigned to operate together when needed (and then under the command of the most senior captain), but these occasions were rather rare. There was no need for sector commands, much less numbered fleets.

However, as distances between Earth and her starships' destinations increased, the long periods without communication became problematic. The trust in their captains was real and evident, but it was understood that sometimes a captain needed to be able to bounce decisions off a person more senior than his own shipboard staff, as well as receive a more in-depth "understanding" that comes with senior ranks. To accomplish this, diplomatic agreements would lead to the request for a Starfleet office within range of a certain number of ships, as well as access to communication arrays (or the provision of such arrays). From this developed the sector modeling of command, whereby the space around Earth was sliced up into designated regions and overseen by commodores (post-tour captains) who could provide that level of leadership to the ships within range.

Originally, these sector commands only dealt with the ships that were within their immediate designated area of responsibility (even if just passing through), as they provided on-scene guidance from Earth, acting merely as command-enhanced communication relays. Eventually, though, sector commands grew to be de facto squadron commanders, as ships were assigned to particular sectors.

Task Force Model (2161)

Upon the conclusion of the Romulan War, the various fleets of the victors were combined into one Star Fleet, in service to the fledgling United Federation of Planets. Due to the disparate units now under control and the need to unite the personnel, tactics, and organizations, the concept of multiple fleets was put aside for the foreseeable future. Instead, Star Fleet Command provided control, administration, and orders from its headquarters in San Francisco, on Earth.

When one vessel just couldn't do the job, however, the local Star Fleet authority—or Star Fleet Command, if it was within communications range—would detail the necessary units from whatever their individual current assignments might be. This task force model allowed the UFP to show the flag or exert just the right amount of force, when necessary. With the conclusion of the emergency, the task force would be broken up and the units would return to their mission areas.

This concept worked well enough for the next century, give or take a few decades, but it would sometimes suffer from a lack of available starships. Results could vary from unqualified successes to unmitigated disasters, but Star Fleet did what it could do with what resources it controlled. However, lack of available starships as a reason for situational difficulties ceased, suddenly, to be a problem in 2341, as replicator technology was realized. Now, starships could be mass produced, with only the design and assembly phases taking up the significant portion of the production process.

However, with the advent of scores of new starships warping around the Federation and the frontiers, Star Fleet organization had reached a crisis point. As long as the UFP remained at peace, the organizational snarls and spotty communications could be overlooked in the name of Star Fleet captains' traditional independence and initiative. But, the Cardassian and Tholian Wars (2347-2366 and 2353-2360, respectively) strained the system past the breaking point. Certainly, the outcomes of certain battles—and possibly the length of time of the conflicts themselves—could have been affected with more precise administration.

Sector Assignments (2260)

Adapted from Edge Of Midnight - The Business of Risk, pp 227-230.

In the wake of growing operational complexities and expanding Federation borders, Star Fleet Command determined that the traditional, ad hoc deployment of vessels was no longer sufficient to safeguard its territories or project influence effectively. At the landmark command conference convened at Starbase 19 in February 2260, senior admirals and staff acknowledged the limitations of previous practices, whereby ships responded to incidents based on proximity and immediate availability. Instead, a transformative approach was formalized: rather than dispatching ships reactively, the Federation’s extensive frontier would be systematically mapped into contiguous sectors, each comprising roughly 8,000 cubic lightyears.

This division was far more than a mere administrative reorganization—it represented a conceptual shift in how Star Fleet perceived and exercised its responsibilities. By assigning a rear admiral or higher to reside within each sector, accompanied by an appropriately staffed command center and a dedicated group of ships, the intention was to nurture both tactical expertise and diplomatic rapport unique to that region. Sector staff would have the opportunity not only to develop specialized knowledge of local planetary systems and political conditions but also to cultivate enduring relationships with residents and allies, strengthening Federation cohesion and response times.

The implementation of sector assignments marked the beginning of semi-organic growth in Star Fleet’s organizational model, steadily extending this system throughout the totality of explored space. The effectiveness of this approach lay in its capacity to promote continuous cooperation among Star Fleet assets, rather than restricting unified operations to moments of crisis. As the sectors evolved, so too did the command structures embedded within them, enabling Star Fleet to combine flexibility with local expertise—ultimately leading to a more robust and proactive starship presence across the Federation frontier. This foundational change laid the groundwork for subsequent innovations in fleet management and operational doctrine, emphasizing collaboration, preparedness, and regional accountability as key pillars of Star Fleet’s enduring mission.

Tactical Fleet Model (2267)

Adapted from the TacFleet and Rapid Deployment Force concepts from Ships of the Star Fleet, Volume Four: Star Fleet Operating Forces (PDF pp 33-35).

While maintaining the Task Force Model that had been in use for the previous century, the TacFleet modification to fleet doctrine introduced a system in which select ships within any given operating area were specially equipped and trained to respond to developing tactical situations. Established in 2267, following the Romulan Star Empire’s covert attack against Federation Neutral Zone outposts by a single bird-of-prey, the concept was intended to ensure a credible and immediate force projection in response to foreign aggression within Federation borders.

Each designated TacFleet vessel participates in regular or semi-regular multi-ship exercises. While non-TacFleet ships may also take part, the primary aim of these drills is to strengthen the readiness of TacFleet vessels to engage and respond effectively to potential adversaries. For this reason, it is uncommon for a TacFleet ship not to be involved in such an exercise.

Within any given area of responsibility (AOR), approximately 25% of the ships-of-the-line are typically assigned to the local TacFleet. Their crews regard this designation as both an honor and a duty. Each TacFleet is identified by the starbase responsible for its AOR; for example, Starbase 80 serves as the administrative headquarters for the 80th TacFleet. Not all starbases, however, carry tactical responsibility or host a designated tactical fleet.

Fleet Model (2357)

At Star Fleet Command, Admiral Taneko applied his Bolian gift for organization to address the fleet’s challenges between 2348 and 2350. Drawing on the lessons of both earlier wars, he developed a new fleet model that endured and proved its effectiveness through the Tzenkethi (2358–2362), Klingon (2372–2373), and Dominion Wars (2373–2375), and well beyond.

In Taneko's fleet model, Star Fleet organizes itself into fleets comprising around 150 to 250 ships each, under the command of a rear admiral (upper half) or vice admiral [see Flag Officers (post-2353) for details]. The "flagship" of a fleet is simply the ship best suited for command-and-control functions in an emergency (as determined by the admiral) and, sometimes, is pre-selected and maintained in a ready state at the admiral's assigned starbase.

Each fleet serves either a tactical purpose (such as to protect Vulcan) or a strategic one (such as ready reserve). Most tactical fleets are "standing" fleets, which retain the same mission throughout their existence. Most strategic fleets are either "mobile" fleets, sent to any crisis area or placed on deep-space patrol and exploration duty, or "supporting" fleets kept ready for specific contingencies. The deployment of a mobile fleet essentially follows the older task force model, only with better communications and more ships. Most mobile fleets keep their starships in the same broad area for faster concentration and coordination in case of emergencies.

On the eve of the Dominion War, these fleets numbered 27 in total, which itself was a significant increase over the last ten years*, due to the re-emergence of the Romulans as an active threat and as a response to the Borg incursion of 2366. During the war, the number of fleets grew to 44 in number, although the hard fighting left many of them severely understrength. The war left approximately 2,500 ships (from about 6,100) in ready condition, with about that many again in varying states of damage, dis-repair, or suffering from crew attrition.

*_{By 2364, the Fleet Model had been fully realized, with the 24 fleets formed and operating, as designed and accepted in 2356. With the re-emergence of the Romulan Star Empire late the same year, consistent re-evaluation of the composition of the Fleet Model began. By 2372, three additional fleets had been activated.}

Fleet Types

As indicated above, the 27 fleets are categorized by types: standing, mobile, or support. While a fleet may be tasked with a very specific mission, it will always fall into one of these three types.

Standing

This type of fleet is charged with the defense and surveys of a given sector or small group of sectors. A ship in a standing fleet may operate out of a stationary base of operations.

Mobile

A fleet of this type operates over a vast, wide-ranging theater of operations, performing exploratory, scientific, diplomatic, and intelligence missions, but will also be tasked with providing response to strategic issues, such as incursions or other emergency missions.

Support

These fleets tend to have rather specific missions, such as colonization support, evacuation, active reserve, or rapid response (of a tactical nature).

Fleets (as of 2373)

• 1st Fleet: support; the "Training Fleet", operating ships in the vicinity of the Academy's various campuses, for cadets' onboard experience
• 2nd Fleet: mobile; explores the uncharted regions of the Beta Quadrant, focusing on the coreward direction.
• 3rd Fleet: standing; assigned to defend the Sol system.
• 4th Fleet: mobile; explores the uncharted regions of the Beta Quadrant, focusing on the rimward direction.
• 5th Fleet: standing; patrols Sectors 005 (Vulcan) and 006 (Andor)
• 6th Fleet: standing; patrols Sectors 001 (Sol) and 007 (Tellar).
• 7th Fleet: standing; headquartered in the Betazed Sector, this fleet patrols the Federation's border with the Cardassian Union.
• 8th Fleet: mobile; explores the uncharted regions of the Alpha Quadrant, focusing on the rimward areas in the direction of Alpha Cygni.
• 9th Fleet: standing; patrols Sectors 003 (Terra Nova) and 004 (Sigma Draconis).
• 10th Fleet: support; the "Test Fleet", operating prototype ships, ships conducting post-construction testing and ships assigned to technology testing
• 11th Fleet: standing; patrols Sectors 002 (Alpha Centauri) and 008 (Ophiucus).
• 12th Fleet: support; the "colonization fleet", made up of 34 vessels plus transports and commanded out of Starbase 4, it specializes in establishing new colonies and terraforming missions
• 13th Fleet: mobile; explores the uncharted regions of the Beta Quadrant, focusing on the antispinward direction.
• 14th Fleet: support; one of the three "evacuation fleets", based out of the Rigel sector, the fleet has enough ships to coordinate and defend a convoy carrying up to 10 million civilians in case of planetary emergencies.
• 15th Fleet: support; one of the two "rapid response fleets", operates in the Alpha Quadrant and reports directly to the Star Fleet Response Command
• 16th Fleet: mobile; spread throughout the Federation and areas under its auspices, this fleet handles a wide range of survey, diplomatic and border emergency missions; the "flagship" fleet.
• 17th Fleet: support; one of the three "evacuation fleets", based out of the Deneb Kaitos Sector, the fleet has enough ships to coordinate and defend a convoy carrying up to 10 million civilians in case of planetary emergencies.
• 18th Fleet: mobile; explores the uncharted regions of the Alpha Quadrant, focusing on the coreward areas past Ferenginar.
• 19th Fleet: support; one of the two "rapid response fleets", operates in the Beta Quadrant and reports directly to the Star Fleet Response Command
• 20th Fleet: mobile; patrols the rimward sectors of the Federation
• 21st Fleet: mobile; explores the uncharted regions of the Alpha Quadrant, focusing on the spinward areas.
• 22nd Fleet: standing; on guard for Romulan incursion from across the Neutral Zone, the fleet is also the first line against another Borg invasion.
• 23rd Fleet: support; one of the three "evacuation fleets", based out of the Canopus Sector, the fleet has enough ships to coordinate and defend a convoy carrying up to 10 million civilians in case of planetary emergencies.
• 24th Fleet: support; the original "active reserve" fleet, providing individual commands to fill gapped positions in the table of organization, until relieved by an active command.
• 25th Fleet: support; an added "active reserve" fleet
• 26th Fleet: support; an added "active reserve" fleet
• 27th Fleet: support; an added "active reserve" fleet

Starbases

Both models of fleet deployment depend heavily on starbases to coordinate, resupply and even defend the ships on duty. From almost its earliest days, Star Fleet has joined the stationary starbases with mobile starships as part of its defensive and exploratory policies.

A base's purpose may shift over time; a former strategic base on the Federation frontier may, as the Federation expands, become a supply station and then a service hub and eventually serve as a locus of trade and recreation.

Command Center

These starbases are major administrative centers for Star Fleet, serving as 'continuity' offices for Star Fleet Command (should something befall Earth) as well as coordinate transits of defense ships between the inner and outer cores of the Federation. Sometimes located in the huge spacedocks but just as common to be located on-planet, the command center is often co-located with an Academy campus. Oftentimes, high visibility events -such as Federation admission ceremonies or important courts martial- are held at these well-known locations and they are important locations for large quantities of ongoing starship maintenance and stockpiles of major starship systems. In certain circumstance, such as the larger neutral zones, these bases may be established to coordinate the defense of a border or prosecution of any hostilities.

Science Station

Often solitary way-stations devoted to science or medical research, including the observation of long-term astronomical phenomenon.

Service Hub

These starbases come in several different 'flavors' or a combination of all: facilities devoted to rest and recreation usually exist on-planet, while the maintenance-minded base may be anything from a small, well-stocked station to the larger spacedocks, both of which will have top-rate technical expertise. A third type focuses on providing preventative and supporting maintenance for remote commercial (foreign and domestic) trade ships, along with other services. These last often serves as centers of cultural exchange and may be run by a non-Star Fleet agency, such as the Federation Merchant Marine.

Strategic Base

These bases provide an amalgamation of services but for the purposes of defensive and responsive fleets only (i.e., not for commercial or diplomatic functions). Unlike a command center base that may oversee the totality of a large front, these bases focus on the complete support for fleet assets in a specific region of that front, providing services in the areas on intelligence, medical, repair and supply. For repair, while assistance can run the full spectrum needed, there is a large technical focus on getting combat assets back into the fight, so expertise will be on hull, propulsion and tactical repairs. Supplies will be similarly focused, with an emphasis on torpedoes, medical and fighter-craft. These bases are well-defended, with a mix of organic ships and station armament.

Supply Station

Supply Stations serve one of two types of customers: either colonial efforts or Star Fleet. The former provides medical, technical, infrastructure, terraforming and administrative support and is often a jumping off point for regional colonial expeditions. Temporary lodging exists in great capacity (up to 250,000 on some larger stations) for the purposes of establishing these expeditions, but also serve refugees from natural or hostile disasters or otherwise failed colonial efforts. These bases provide for a larger number of refits and repairs of colonial shipping (with some allowance for commercial endeavors) and also provide stockpiles of ship equipment for point-of-purchase sales. Because of the nature of colonial supply bases, they tend to be very cultural in nature, with diplomatic resources. The other supply base type focuses on rearward support of Star Fleet and -while providing many of the same types of services- are the cultural opposite, as they are very utilitarian and efficient. Smaller transports routinely arrive and depart, as they provide forward delivery of supplies to starships that are unable to deviate from ongoing missions.

Deep Space Station

The Federation understands its ability to provide direct and full support of a region may lag behind opportunities that arise at the far extent of its borders or even beyond them. When something suggests Federation presence would be seen as beneficial or necessary over a long term, a deep space station may provide that presence. These bases tend to be remote with no starship support, or at the most one assigned to the general area on unrelated missions. They'll be equipped with the personnel necessary to perform the appropriate mission, which means these stations may be heavily crewed by any one particular branch of Star Fleet and may serve as regional centers of culture and commerce. In some instance. deep space stations may serve as a way-point between major friendly or allied powers.

Personnel

Note: This is based upon an analysis of the support personnel versus combatant/deployable personnel of both the USN & USMC in 2024.

Star Fleet personnel (with the exclusion of the Star Fleet Marine Corps) are either assigned to deployable units (starships, wings, Seabee battalions, etc.) or units that support them. The support tail requirement of personnel is generally about 144% that of the deployable units. Note: personnel assigned to operate a station proper (such as a strategic base) would count towards that support requirement for a given number of deployable units; additional personnel assigned to the station (medical, intelligence, repair, supply, etc.) would make up the remainder.

For the entirety of the Star Fleet Marine Corps, the support tail requirement of personnel is generally about 230% that of the deployable units.