Star Fleet Command Manual - Volume II

STAR FLEET COMMAND
MANUAL
VOLUME II
STAR FLEET OPERATIONS
Control Number
Terranglo Edition, Copyright © 2277 Star Fleet Command, Star Fleet Printing Office
All rights reserved under the laws of the United Federation of Planets
STAR FLEET COMMAND MANUAL
VOLUME II
STARDATE 25201.18 UFP521-2a.i OFFICIAL USE ONLY

VOLUME II
This Page Left Intentionally Blank
STARDATE 25201.18 UFP521-2a.ii OFFICIAL USE ONLY

VOLUME II
TABLE OF REVISIONS
Revision Section/Page
Stardate Description of Change
Number Number
0.0 0054.44 All Initial Publication
0.1 0117.01 All Modified all manual pages to incorporate the Stardate standard.
0.2 0302.55 All Modified manual to include civilian employees of Star Fleet.
0.3 0444.20 Section 1.0 Incorporated newly created symbol for the Operations Division
0.4 0510.37 Section 2.1 Added sections for the Commandant of the Star Fleet Marine Corps.
0.5 0627.91 Section 2.6 Added a section on Star Fleet Transport ship commanders.
0.5a 0628.32 Section 2.9 Updated Table 2a29.1
Added Section 5.7 will all currently standing General Orders.
0.5b 0981.71 Chapter 5
Sections 5.4 and Added General Order 6; updated Table 2a54.1.

0.6 2377.4
5.7
Added Figure 2a18.2 to show the layout of the newly completed
0.7 6558.54 Section 1.8
Operations Center.
0.8a 6744.65 Section 2.8 Updated Figures 2a28.1 and 2a28.2
Updated Figures 2a13.1 and 2a13.2; added Table 2a13.1, which
0.8b 6792.72 Section 1.3
lists Local Force Liaison Officer assignments.
0.9 6894.35 Section 7.5 Added a new section on current base and station locations.
1.0 7305.29 All Final Version
Section 1.3 Updated list of Liaison Officer assignments
1.1 7328.86
Table 2a13.1
Sections 5.6 and Added picture of a Subspace Relay Station
1.2 11255.92
7.3
1.3 16458.43
5.7
Sections 5.4, 5.7 Added General Orders 8, 9, 10, 11, 12 and 13; updated Table
1.3b 18402.8
and 8.2 2a54.1.
1.4 21358.10
5.7
Sections 5.4 and Added General Orders 15, 16, 17, 18, 19, 20, 21, 22, 23, 24 and 25;
1.5 21676.54
5.7 updated Table 2a54.1.
1.5.1 22084.55 Section 8.2 Updated section with recent alert cases.
1.6 22985.00 Section 1.5 Updated Table 2a15.1 with current ship assignments
Sections 6.6, 5.4, Added new section with Star Fleet ships and their assignments.
1.7 23704.96
5.7, 6.1 and 6.2 Added General Orders 26, 27 and 28; updated Table 2a54.1.
Chapter 4, Updated information on Star Fleet ships included new Attack carrier;
1.7b 23882.38 Sections 6.3 and updated manpower data. Updated section for current debt
6.4 obligations. Updated Table 2a64.2.
1.8 24140.62
5.7
Added references to the Gorn, Melkotian and Tholian empires;
Sections 3.1, 3.2,
1.9 24744.83 updated Table 2a32.1 regarding Buffer Zones. Updated maps and
8.3, 8.4 and 8.5
charts.
2.0 25107.55 Section 5.3 Incorporated declassified mission order example.
2.0b 25166.82 Section 7.5 Updated base and station locations.
2a.iii, New forward by the current Chief of Star Fleet Operations.
2.1 25201.18
Section 1.1
STARDATE 25201.18 UFP521-2a.iii OFFICIAL USE ONLY

VOLUME II
STARDATE 25201.18 UFP521-2a.iv OFFICIAL USE ONLY

VOLUME II
FORWARD
The Star Fleet Command Manual was created to lay the foundation for the structure, authority and
functions of Star Fleet. It is divided into nineteen volumes, each of which relates to a specific function of
the Department and is written in the languages of the worlds that are signatories to the Articles of
Federation.
Not only is the function of the Star Fleet Command Manual to lay the foundation for the Star Fleet,
but also to act as a reference guide to all members of the Service and is used at all Star Fleet training
facilities for the education and indoctrination of its members. Every command within the Department shall
have at least one copy of the complete manual in the languages representing the United Federation of
Planets.
Therefore, I invite all members of the Star Fleet Service to read this manual and become familiar with
all the information it has to offer. It should be noted that certain sections and chapters of this volume
contain highly classified information. Therefore, the entire volume is classified as containing SECRET
information. All authorized personnel shall handle this volume appropriately and in accordance with the
regulations regarding the handling of classified material.
Heihachiro Nogura, Admiral, SFC

Chief of Star Fleet Operations
STARDATE 25201.18 UFP521-2a.v OFFICIAL USE ONLY

VOLUME II
STAR FLEET COMMAND MANUALS
VOLUME I STAR FLEET COMMAND

VOLUME II STAR FLEET OPERATIONS
VOLUME III STAR FLEET PERSONNEL
VOLUME IV STAR SHIP COMMAND
PART 1 STAR SHIP COMMAND DIVISION
PART 2 STAR FLEET SHIP OPERATIONS
VOLUME V STAR FLEET SHIPS

PART 1 STAR FLEET SHIP DESIGN
PART 2 STAR FLEET SHIP CONSTRUCTION
PART 3 STAR FLEET SHIP SYSTEMS
PART 4 STAR FLEET SHIP SYSTEMS OPERATION
PART 5 STAR FLEET SHIP MAINTENANCE
PART 6 STAR FLEET SERVICE CRAFT
PART 7 STAR FLEET AUXILLIARY UNITS
PART 8 STANDARD STAR FLEET EQUIPMENT
VOLUME VI STAR BASE COMMAND

PART 1 STAR BASE COMMAND DIVISION
PART 2 STAR FLEET BASE OPERATIONS
VOLUME VII STAR FLEET BASES

PART 1 STAR FLEET BASE DESIGN
PART 2 STAR FLEET BASE CONSTRUCTION
PART 3 STAR FLEET BASE SYSTEMS
PART 4 STAR FLEET BASE SYSTEMS OPERATION
PART 5 STAR FLEET BASE MAINTENANCE
VOLUME VIII STAR FLEET JUSTICE

VOLUME IX STAR FLEET REPRESENTATIVES
VOLUME X STAR FLEET MEDICINE
VOLUME XI STAR FLEET SECURITY
VOLUME XII STAR FLEET SCIENCE
VOLUME XIII STAR FLEET ENGINEERING
VOLUME XIV STAR FLEET EDUCATION
VOLUME XV STAR FLEET EXPLORATION
VOLUME XVI STAR FLEET MATERIEL
VOLUME XVII STAR FLEET MARINE CORPS
VOLUME XVIII STAR FLEET CONSTRUCTION
VOLUME XIX STAR FLEET CHAPLAINS
STARDATE 25201.18 UFP521-2a.vi OFFICIAL USE ONLY

VOLUME II
VOLUME II TABLE OF CONTENTS
Introduction 2a.ix
1.0 Star Fleet Division of Operations 2a10

1.1 Star Ship Command 2a11
1.2 Star Base Command 2a12
1.3 Star Fleet Adjunct Forces Command 2a13
1.4 Star Fleet Intelligence 2a14
1.5 Star Fleet Space Exploration Command 2a15
1.6 Star Fleet Operations Offices 2a16
1.7 Star Fleet Operating Forces 2a17
1.8 Star Fleet Operations Center 2a18
2.0 Star Fleet Operations Division Organization 2a20
2.1 Chief of Star Fleet Operations 2a21
2.2 Star Fleet Operations Staff 2a22
2.3 Sector Commandants 2a23
2.4 Fleet Commanders 2a24
2.5 Base Commanders 2a25
2.6 Ship Commanders 2a26
2.7 Officers in Command 2a27
2.8 Adjunct Forces 2a28
2.9 Reserve Forces 2a29
3.0 Global Fleet Organization 2a30
3.1 Federation Territories and Spaces 2a31
3.2 Octants, Districts, Regions and Sectors 2a32
3.3 Designation of Fleets 2a33
3.4 Star Fleet Chain of Command 2a34
3.5 Fleet Requirements 2a35
3.6 Fleet Components 2a36
3.7 Fleet Deployment 2a37
3.8 Organization of Service Craft 2a38
4.0 Fleet Operational Requirements 2a40
4.1 Manpower Requirements 2a41
4.2 Materiel Requirements 2a42
4.3 Support Requirements 2a43
4.4 Budgetary Requirements 2a44
STARDATE 25201.18 UFP521-2a.vii OFFICIAL USE ONLY

VOLUME II
VOLUME II TABLE OF CONTENTS - CONTINUED
5.0 Fleet Command Operations 2a50

5.1 Fleet Administration 2a51
5.2 Fleet Operations 2a52
5.3 Fleet Assignments and Missions 2a53
5.4 Fleet Operational Orders 2a54
5.5 Fleet Operational Command 2a55
5.6 Fleet Communications 2a56
5.7 Star Fleet General Orders 2a57
6.0 Star Fleet Ship Operations 2a60
6.1 Star Fleet Ship Functions 2a61
6.2 Star Fleet Ship Missions 2a62
6.3 Star Fleet Ships 2a63
6.4 Star Fleet Ship Assignment 2a64
6.5 Reserve Status Ships 2a65
6.6 Current Star Fleet Ship Assignments 2a66
7.0 Star Fleet Base Operations 2a70
7.1 Star Fleet Base Functions 2a71
7.2 General Base Operations 2a72
7.3 Star Fleet Bases 2a73
7.4 Star Fleet Base Placement 2a74
7.5 Current Star Fleet Base Locations 2a75
8.0 Tactical and Strategic Operations 2a80
8.1 Galactic Defense Conditions 2a81
8.2 Alert Conditions 2a82
8.3 Fleet Positioning 2a83
8.4 Battle Strategies 2a84
8.5 Security Patrols 2a85
9.0 Special Operations 2a90
9.1 Star Fleet Intelligence 2a91
9.2 Intelligence Gathering Methods 2a92
9.3 Special Ship Missions 2a93
9.4 Secret Operations 2a94
STARDATE 25201.18 UFP521-2a.viii OFFICIAL USE ONLY

VOLUME II
INTRODUCTION
In the year 2203 the Federation Council and the Military Staff Committee was tasked, under
Executive Order 521, to develop the structure, authority and operation of the Department of the
Star Fleet. A special task force composed of the military experts from all the signatory members of the
Federation was created to establish the structure of Star Fleet. The resulting document, along with the
Star Fleet Charter, was the Star Fleet Command Manual.
The Star Fleet Command Manual took over two years to develop. Many of the aspects of the structure
and organization described in the manual were developed from the old military systems of Earth and
from the old Space Service. Therefore, most readers will find this familiar to them. The Star Fleet
Command Manual is actually a set of manual volumes, each focusing on a specific function of the
Department of the Star Fleet. This volume, Volume II of the Star Fleet Command Manual,
describes how the Operating Forces are organized into the functional units as required in accordance
with the Star Fleet Charter, and of the officers that command these units. In addition, this volume will
also describe the organization that has the responsibility for the management and operation of the entire
Operating Forces and Shore Establishments of the Department of the Star Fleet – the Star
Fleet Division of Operations.
The Star Fleet Command Manual is written in the five languages of the original signatories to the
Articles of Federation. The Terranglo version of the manual is written for those members of Star
Fleet that originate from Earth and is written in the English language. Other versions written in
languages other than the standard five can be obtained from the Star Fleet Printing Office upon
request.
Throughout the manual the following typographic standards will be used:
1. Bolded items are important Star Fleet and Federation names, titles, designations and other key
words that Star Fleet personnel should become familiar with.
2. Titles, designations and other identifiers will be illustrated in a generic format. Where a specific value
must be entered to complete the title or phrase, angle brackets (“<>”) will be used to indicate the
point of insertion.
3. Where a choice is required in order to complete a title or phrase, a vertical bar (‘|’) is used to
indicate a selection. However, only one selection can be made from the choices offered. All choices
and ranges of choices are enclosed within braces (“{}”).
4. References to classified material will be exposed as to their classification level and printed in Bold
RED print.
5. Throughout this manual there are hyperlinks to sections and figures provided in this manual. Internal
links to figures, for example: “Figure 2a15.3”, will allow the reader to jump to that figure by clicking
the text “Figure 2a15.3.” To return back to the source page, click on the page number at the bottom
of the figure, such as “UFP521-2a15.11.” This also applies to any referenced section in the manual.
Thus, clicking “Section 2.0” in the manual will jump to that section or an appropriate page in that
section. However, there is no return link to the source page.
6. In addition, there are various editorial comments made regarding information or references to texts,
concepts or items stated or presented within the TOS episodes. These are indicated with a
superscripted bracket, such as: TEXT[n]. Clicking on the superscript will jump the reader to the
explanation in the Star Fleet Guide section of this manual. To return to the source page, click
anywhere on the descriptive text.
STARDATE 25201.18 UFP521-2a.ix OFFICIAL USE ONLY

VOLUME II
STARDATE 25201.18 UFP521-2a.x OFFICIAL USE ONLY

OFFICIAL USE ONLY
VOLUME II
1.0 STAR FLEET DIVISION OF OPERATIONS

In this chapter the structure of the Star Fleet Division of Operations will be presented.
The basic organizational structure for the Star Fleet Division of Operations is
illustrated in Figure 2a10.1. Operations, as it will be defined in this volume, is the
execution of the missions and functions of Star Fleet as specified in the Star Fleet
Charter. As such, the primary function of the Division of Operations is to direct and
manage the forces and assets needed to carry out the missions and functions to which
Star Fleet is assigned.
What will not be extensively covered in this volume is the Federation Strategic
Command or STRATCOM, which is a joint Star Fleet-Federation organization created
to establish the strategic direction of Federation military forces and operations.
STAR FLEET OPERATIONS DIVISION
The Star Fleet Division of Operations (SFOPS), also known as Star Fleet
Operations, is the primary organization responsible for overseeing and managing the
Operating Forces and Shore Establishments of the Department of the Star Fleet.
The Operating Forces consist of all the ships, craft, troops and the personnel assigned to
these assets, while the Shore Establishment consists of all the bases, stations, facilities
and the personnel assigned to those assets. As such, Star Fleet Operations directs all
the activities of the aforementioned assets and personnel and in so doing, organizes,
deploys and assigns Star Fleet forces to missions on behalf of the Federation, while
ensuring the readiness, effectiveness, and efficiency of those forces.
In fulfillment of the requirements of ARTICLE 8 of the Star Fleet Charter the Division
of Operations is also charged with the gathering and handling of all intelligence for the
Department. As such, Star Fleet Operations is the central authority for all intelligence
gathering and such other operations as required to obtain critical information or to achieve
some strategic objective.
The officer in command of the Star Fleet Division of Operations is the Chief of Star
Fleet Operations (CSFO). The CSFO is the senior officer over all the Operating Forces
and Shore Establishments of Star Fleet in accordance with ARTICLE 42 of the Star
Fleet Charter, and reports directly to the Director: Star Fleet Command. The CSFO is
an officer of the line (SFC) with the rank of Admiral. Also within the Office of the Chief
of Star Fleet Operations, and sharing authority within the Division, is the
Commandant: Star Fleet Marine Corps (CMMC), who is the senior officer in command
of all the ground forces within the Star Fleet Service and who also has the rank of
Admiral (MMC). Together, they form the Office of the Chief of Star Fleet Operations
which commands all Operating Forces and shore activities.
In addition, and also reporting directly to the Chief of Star Fleet Operations, are the
nine Sector Commandants in command of all the forces and bases within the territories
dividing Federation space, the Fleet Commanders of the eight permanent fleets, the
five Battle Group Commanders and the two Treaty Zone Flotilla Commanders.
These commanders will be described in more detail in Chapter 2 of this volume.
STARDATE 7305.29 UFP521-2a10.1 OFFICIAL USE ONLY

VOLUME II
FUNCTIONS
As previously stated the primary function of the Star Fleet Division of Operations, also
known as Star Fleet Operations, is to command and manage all the Operating Forces
and Shore Establishments of the Department of the Star Fleet. All the primary
functions of Star Fleet are directed from this central command, which are basically:
1. To protect the peace and security of the United Federation of Planets, and to
provide protection and assistance to all its members.
2. To enforce Federation laws, regulate shipping and space travel, and establish rules of
safe navigation within the Federation territories.
3. To carry out basic research in the physical and life sciences, survey known and
unknown areas of space, and expand Federation space through exploration and
colonization.
As such, these primary functions will be translated into policies, missions and operations
directed to the Operating Forces in the accomplishment of these functions. The specific
organizations within the Operations Division that will carry out these functions are listed
in the table below.
Table 2a10.1
STAR FLEET OPERATIONS: DIVISION OF RESPONSIBILITY
Star Fleet Function Responsible Operations Organization
Military Operations Operating Forces
Law Enforcement Operating Forces
Scientific Investigation Operating Forces
Exploration Star Fleet Space Exploration Command
Consular Operating Forces
Intelligence Star Fleet Intelligence
Colony Support Operating Forces
RESPONSIBILITIES
The Operations Division has the primary responsibility to manage and direct all the
activities as regards to Star Fleet assets and personnel. This division is responsible for
organizing forces, deploying such forces and assigning the missions on behalf of the
Federation to such forces while ensuring the readiness, effectiveness, and efficiency of
these forces. Therefore, it is the Operations Division that generates and transmits the
orders to the Operating Forces to accomplish the missions to which Star Fleet is
assigned.
Another major responsibility of this division is to keep the Director: Star Fleet
Command and the Federation Council informed on the latest intelligence. As such, this
division is the primary source of military and political intelligence for the Federation as
required under ARTICLE 8 of the Charter. In so doing, this division will analyze and
develop strategic plans for the direction of Star Fleet and the Federation, and will
prepare the plans for the strategic deployment of the forces within Star Fleet.

VOLUME II
AUTHORITY
The Operations Division was specifically created under ARTICLE 42 of the Star Fleet
Charter, which gave the division the authority and responsibility over all the Operating
Forces and Shore Establishments of Star Fleet. As such, this division is empowered
with the authority to:
1. To determine the operational needs of the Federation and to develop the operational
plans to meet such needs and in so doing, issue all operational orders and directives to
all the forces to fulfill such needs.
2. To organize all forces into such units as it deems appropriate and necessary, and to
develop the plans for the organization and use of such forces.
3. To move or deploy any and all forces to locations it deems necessary or proper.
4. To determine the requirements for an effective force and to procure such assets as
needed to ensure an effective force.
5. To determine the placement of all bases and stations anywhere within the Federation
and to authorize and direct the construction of such facilities.
6. To expand the boundaries of the Federation and to explore and colonize new regions
of space.
7. To engage in any activity required to obtain intelligence information or to engage in
such operations as required for the peace and security of the Federation.
DIVISION ORGANIZATION
Star Fleet Operations, as a primary division, is divided into five “Type Commands” and
three administrative offices designed to distribute the primary functions to which the
division has responsibility. These offices are listed in the table below and will be described
in more detail within their respective sections of this chapter.
Table 2a10.2
STAR FLEET OPERATIONS OFFICES
Office Office Chapter
Star Fleet Division or Bureau
Code Designator Section
2000 Star Fleet Division of Operations SFOPS 1.0
2100 Star Ship Command SSC 1.1
2200 Star Base Command SBC 1.2
2300 Star Fleet Adjunct Forces Command AFOR 1.3
2400 Star Fleet Intelligence ICOR 1.4
2500 Star Fleet Space Exploration Command XCOM 1.5
2600 Star Fleet Office of Fleet Logistics FLTSUP 1.6
2700 Star Fleet Office of Fleet Communications FLTCOMM 1.6
2800 Star Fleet Office of Strategic and Tactical Operations TAC 1.6

VOLUME II
STAR FLEET OPERATIONS SYMBOL
The symbol for the Star Fleet Division of Operations is a derivative of the Star Fleet
arrowhead. The symbol consists of a stylized version of the arrowhead placed over a red
globe, which symbolizes the Federation. This symbol will also be displayed on all Star
Fleet Operations documents and is also a patch or badge worn on the uniforms of the
members of this division.
Illustration 2a10.1
STAR FLEET OPERATIONS SYMBOLS
As stated above, the above symbol is also a patch worn on the uniforms of the members
of the division. However, this patch will only be worn by the administrative staff of the
Operations Division. Not all persons within the division is required to wear this symbol.
In addition, the other commands within the Operations Division also have their own
symbol, which must be worn on the uniform of the command. However, there are some
commands that do not have a specific identifying symbol. These organizations are:
• The Star Fleet Adjunct Forces Command

• Star Fleet Intelligence
• The Star Fleet Office of Fleet Logistics
• The Star Fleet Office of Fleet Communications
• The Star Fleet Office of Strategic and Tactical Operations
Table 2a10.1 on the next page illustrates the various pins and badges worn by members
within the Star Fleet Division of Operations.

VOLUME II
Table 2a10.1
STAR FLEET DIVISION OF OPERATIONS UNIFORM BADGES
Badge Division Application
Metal pin worn only on the Formal Dress Blue uniform of
administrative personnel working within Star Fleet
Star Fleet Operations Operations. Individuals working in Star Fleet Operations will
normally wear the Starburst on their working or duty
uniform.
Metal pin worn on the Formal Dress Blue uniforms of
members of Star Ship Command. Persons in the Star Ship
Star Ship Command Command branch (the Operating Forces) will wear the
vertical arrowhead patch on their working or duty uniform as
specified by Star Ship Command.
Metal pin worn on the Formal Dress Blue uniforms of
members of Star Base Command. However, personnel
Star Base Command working within Star Base Command or the Shore
Establishment will wear the regular rectangular patch on
their working or duty uniform.
those working within the Star Fleet Adjunct Forces
Star Fleet Adjunct Forces
Command. Individuals working in this command will
Command normally wear the Starburst on their working or duty
uniform.
The Starburst is worn on all the uniforms of all those
working within Star Fleet Intelligence at all times.
Star Fleet Intelligence

those working within the Star Fleet Space Exploration
Star Fleet Space
Command. A stitched cloth version of this badge will be
Exploration Command worn on the working or duty uniform of all members of this
command.
Star Fleet those working within the Star Fleet Office of Fleet Logistics.
Office of Individuals working in this office will normally wear the
Fleet Logistics Starburst on their working or duty uniform.

Star Fleet those working within the Star Fleet Office of Fleet
Office of Communications. Individuals working in this office will
Fleet Communications normally wear the Starburst on their working or duty
uniform.
Star Fleet those working within the Star Fleet Office of Strategic &
Office of Strategic & Tactical Operations. Individuals working in this office will
Tactical Operations normally wear the Starburst on their working or duty
uniform.

VOLUME II
ORGANIZATION CHARTS
The subsequent page presents the organizational chart for the Star Fleet Division of
Operations. The title block for each office within the division contains the name of the
division, the division number and the Office Designator. The Office Designation is a
shorthand version of the division name.
Division Number Division or Office
2000 Star Fleet

Division of
SFOPS Operations
Office Designator

VOLUME II
Figure 2a10.1
STAR FLEET OPERATIONS DIVISION
2000 Star Fleet

Division of
SFOPS Operations
2100 2200 2300 Star Fleet 2400

Star Ship Command Star Base Command Adjunct Forces Star Fleet Intelligence
SSC SBC AFOR Command ICOR
2500 Star Fleet 2600 Star Fleet 2700 Star Fleet 2800 Star Fleet
Space Exploration Office of Office of Office of Strategic &
XCOM Command FLTSUP Fleet Logistics FLTCOMM Fleet Communications TAC Tactical Operations
Operating Forces

VOLUME II

VOLUME II
1.1 STAR SHIP COMMAND

In this section the structure of Star Ship Command, a subdivision of the Division of
Operations, will be discussed. The function of Star Ship Command (SSC) is to manage
the operations relating to Star Fleet ships, craft and their crews. Star Ship Command is
a particular branch of the Star Fleet Service as specified in Star Fleet Regulation
5100. Star Ship Command is essentially an administrative “Type Command” and as
such, all operations involving Star Fleet vessels of all types are the responsibility of Star
Ship Command. In addition, this command has the responsibility, as delegated to it by
the Director: Star Fleet Command, to manage and maintain the Star Fleet Vessel
Register in accordance with Star Fleet Regulation 2400.
As stated above, Star Ship Command is a branch of the Star Fleet Service and as
such, has authority over of all personnel assigned to Star Fleet ships. All personnel
assigned to this branch of the Service will have a “SSC” designation applied to their title or
rating as specified in Paragraph 3 of Star Fleet Regulation 5320. In order to manage
the operations of ships and craft, Star Ship Command is divided into several offices
designed to handle the tasks associated with fleet operations. The organizational chart
showing these offices can be seen in Figure 2a11.1 and their functions described in the
subsections below.
The Deputy Chief: Star Ship Command (CSSC) is the senior officer in charge of Star
Ship Command and reports directly to the Chief of Star Fleet Operations. As such, all
activities regarding the operations, missions and assignments of Star Fleet ships, craft
and their personnel is the responsibility of the CSSC. The CSSC will be an officer of the
line, and will typically have the rank of Vice Admiral.
RESPONSIBILITY
Star Ship Command is basically responsible for all the aspects regarding the operations
and missions of Star Fleet ships and craft, except those vessels that are assigned to
divisions that support the fleet, such as those vessels assigned to Star Fleet Materiel or
Star Fleet Engineering. In effect, Star Ship Command is responsible for the entire
Operating Forces of Star Fleet and as such, is responsible to the Chief of Star Fleet
Operations for the overall readiness of the fleet in terms of military efficiency, personnel
competence and appropriate force size.
As part of this responsibility, Star Ship Command is tasked with ensuring that all its
personnel are properly trained and qualified in the performance of their duties, and that a
high level of morale is maintained within these forces. In view of this requirement, Star
Ship Command has established a special Starship qualification program designed to
ensure a high degree of competence of ship crewmembers.
In addition, Star Ship Command is also responsible to ensure that the Operating
Forces are provided with all the equipment and supplies necessary to maintain the fleet in
a high state of readiness for all forms of service. As such, Star Ship Command was given
authority to procure the materiel needs of the fleet in concert with the Star Fleet Supply
Command.

VOLUME II
STAR SHIP COMMAND SYMBOL[1]
The symbol for the Star Ship Command is a derivative of the Star Fleet arrowhead.
The symbol consists of the vertical arrowhead placed over a red globe, which symbolizes
the Federation. This symbol will also be used on all Star Ship Command documents
and a version of this symbol is also worn on the uniforms of all the members of this branch
of service.
Illustration 2a11.1
STAR SHIP COMMAND SYMBOL
The division is divided into six offices for the delegation of its responsibilities as illustrated
in Figure 2a11.1. These subdivisions or offices are:
 Office of Star Fleet Ship Personnel

 Office of Star Fleet Ship Operations
 Office of Star Fleet Ship Materiel
 Office of Star Fleet Ship Planning
 Office of Star Fleet Ship Services
 Star Fleet Service Craft Command
Each of these subdivisions will be described in the subsequent sections below.

VOLUME II
OFFICE OF STAR FLEET SHIP PERSONNEL
The Office of Star Fleet Ship Personnel (SSCPER), shown in Figure 2a11.2, functions
much the same way as the Star Fleet Division of Personnel. The primary function of
this office is to determine ship complements and will make requests to the Star Fleet
Bureau of Personnel (BUPERS) for the allocation of personnel to this branch, and will
work with the Star Fleet Office of Force Planning in determining the force size of the
fleet. However, it will be BUPERS that will issue the assignment orders to SSC personnel.
This office also makes recommendations regarding the selection of Fleet, Force and
Flotilla Commanders to the Chief of Star Fleet Operations (CSFO). Typically, the
CSFO will request SSCPER to supply him with a list of possible candidates to command
such forces, but is not obliged to seek such recommendations from SSCPER. The CSFO
can select any eligible flag officer he so chooses, so long as it meets with the approval of
the Director: Star Fleet Command. However, SSCPER is directly responsible for
determining the eligibility of Star Fleet officers to command Star Fleet operating units in
accordance with Star Fleet Regulation 5750, and in the selection and assignment of
Commanding Officers to ships.
Another responsibility of SSCPER is to ensure that SSC personnel are properly trained
and qualified to perform their duties aboard ship. As such, this office will establish the
criteria for ship and on-board duty station qualification, and will design the necessary
training programs to fulfill such qualification. In addition, this office will establish special
training programs for Commanding Officers and other officers relating to the command,
navigation and operation of Star Fleet ships, and will work with the Star Fleet Training
Command in the development of such training programs. Within the Office of Star
Fleet Ship Personnel is the Star Fleet Ship Personnel Requirements Section which
determines the numbers and vocations of personnel to be allocated to Star Fleet ships.
The Personnel Requirements Section also works with the Star Fleet Office of Force
Planning in establishing the force requirements.
The function of the Star Fleet Ship Personnel Certification Section is to establish the
requirements for Star Fleet ship duty. In addition, this section is responsible for crafting
the requirements for watch standing and watch station qualification, as well as establishing
the tests and training requirements for the various watch stations onboard all Star Fleet
ships. In addition, this office maintains the records of watch qualification for every person
assigned to a Star Fleet ship.
The Star Fleet Ship Personnel Assignment Section manages all the aspects regarding
the assignment of Star Ship Command personnel to ships. As such, this section will work
with the Star Fleet Office of Personnel Assignment concerning the ships that will
need manpower replacements and to assign SSC personnel to ships based upon this need.
However, it will be BUPERS that will issue the orders to individuals for assignment to ship
duty.
The Star Fleet Ship Commanders Section is essentially responsible for establishing the
requirements for officers who wish to become Starship Commanding Officers. This
office will manage the Commanding Officer Training and Certification Program, and
will make recommendations to the Chief of Star Fleet Operations and the Chief of
Star Fleet Personnel regarding the readiness of individuals to become Starship
Captains.

VOLUME II
OFFICE OF STAR FLEET SHIP OPERATIONS
The function of the Office of Star Fleet Ship Operations (SSCOPS) is to command the
entire fleet in terms of their functions, operations and missions. This office plans the
missions assigned to it by higher authority, assigns such missions to fleets and other
operational units along with the Rules of Engagement that are to be applied during the
mission, and monitors the locations of all ships within the fleet.
One of the major offices within SSCOPS, shown in Figure 2a11.3, is the Star Fleet Ship
Assignment Section. This section is solely responsible for assigning Star Fleet ships
and craft to Sectors, Fleets, Squadrons, and Divisions as well as to other operating
units and areas. This section is also responsible for designating and managing the various
Fleets, Flotillas, Groups and other operational units in space. It is the Star Fleet Ship
Assignment Section that issues all the orders to Fleet Commanders regarding the
operations and missions to which they are assigned.
The basic function of the Star Fleet Ship Operations Planning Section is to plan and
organize the missions to which Star Fleet ships will be assigned. In addition, this section
will organize ships into forces and units and will submit such plans to the Star Fleet Ship
Assignment Section for implementation.
The Star Fleet Ship Readiness Section monitors and inspects the fleet for readiness.
This section will develop special maneuvers designed to test the readiness and
effectiveness of ship forces under various scenarios through war games and other such
exercises. In addition, this section will also develop the standard drills and exercises
internal to the organization of Star Fleet ships designed to test the readiness of the ship’s
crew. Since the Ship Readiness Section is responsible for the readiness of all Star
Fleet ships it will investigate any situation that could affect the status and readiness of the
entire fleet and therefore, will instigate such Boards of Inquiry as needed to investigate
any loss of, or damage to Star Fleet vessels and report their findings to the Director.
The function of the Star Fleet Ship Organization and Processes Section is to develop
and establish the basic organizational structure aboard all Star Fleet ships, which includes
the basic “Chain of Command” within all Star Fleet ships. In addition, this section is also
responsible for establishing the basic duty stations, routines, as well as the basic watch
rotation on board all ships within the fleet. As such, this section will create the Ship’s
Operations and Regulations Manuals or SORM for each Star Fleet ship in
commission. In general, this section is responsible for developing and maintaining all the
procedures and regulations required for the safe operation and handling of all Star Fleet
ships, and is responsible for developing any special procedures, guidelines or instructions
regarding the type of mission and the functions assigned to any ship within the fleet.
Star Fleet Ship Mission Control is a major section of the Star Fleet Operations
Center and is managed by the Office of Star Fleet Ship Operations. In this area, the
entire territory of the Federation is holographically mapped and the location of each Star
Fleet vessel displayed, as well as any private, commercial or enemy vessel. This is the
nerve center for the entire operation of the fleet, which allows for real-time evaluation of
any situation and to make adjustments in strategy as needed. This center is a highly
classified area and as such, cannot be described in any more detail here; nor can any of its
operations and functions be explained in any detail.

VOLUME II
OFFICE OF STAR FLEET SHIP MATERIEL
The function of the Office of Star Fleet Ship Materiel (SSCMAT) is to determine the
material needs of the fleet and to provide all units within the fleet the equipment and
supplies needed to operate effectively. As such, this office will plan and schedule all supply
rendezvous with elements of the fleet. SSCMAT also submits the logistical requirements of
the fleet to the Star Fleet Office of Fleet Logistics for the allocation of the materials
and supplies required by units of the fleet. The organizational chart for this office is
illustrated in Figure 2a11.4.
One of the major offices within the Office of Star Fleet Ship Materiel, shown in Figure
2a11.4, is the Star Fleet Ship Supply Requirements Section. This office is responsible
for assessing the material needs of the various units within the fleet, as well as for the
personnel within Star Ship Command. As such, the primary function of this office is to
ensure an adequate supply of tools, spare parts, replacement equipment, service craft,
and food stuffs for Star Fleet vessels. Therefore, this section essentially determines the
complete material needs for the entire Operating Forces of Star Fleet based upon the
material requirements submitted by the various supply and procurement officers of the
operating commands. From these inputs this office will make the plans, budgets and
schedules for the procurement of the materials, goods and services needed to sustain the
fleet. This section will work with the Star Fleet Office of Fleet Logistics in determining
the budgetary requirements based upon the materiel needs of the Operating Forces.
The Star Fleet Ship Supply Planning Section within SSCMAT handles all the planning
and distribution of supplies to the Operating Forces. As part of this function, this office
will work with the Star Fleet Transportation Command and the Star Fleet Logistical
Operations Section in the planning and scheduling of supply shipments and convoys to
the various ship support facilities, and will schedule supply rendezvous of equipment and
spare parts to the various Fleet Supply Commands within the Operating Forces and
Shore Establishments.
The function of the Star Fleet Ship Supply Allocation Section is to manage all
activities regarding the allocation of the material and equipment for the Operating
Forces. As such, this section will work with the Star Fleet Supply Command, through
the Star Fleet Logistical Supply Section, in obtaining the materials, equipment and
supplies needed to maintain the Operating Forces in a state of maximum readiness. In
addition, this section will also develop the procedures for allocating and procuring materiel
for the fleet, and will train Star Fleet Ship Supply Officers in such procedures.

VOLUME II
OFFICE OF STAR FLEET SHIP PLANNING
The Office of Star Fleet Ship Planning (SSCPLN) is responsible for determining the
basic force needs of the fleet. As such, this office will perform studies, analyze current
capabilities, project future requirements and make recommendations regarding the future
of the fleet. SSCPLN will work with the Star Ship Systems Command (STARSHIPS) in
ordering the construction of new ships, the design of new classes of ships and make
recommendations regarding the decommissioning of stricken or aging vessels. This office
is also tasked with establishing the schedules for refitting and refurbishing Star Fleet
ships currently in active service. As such, SSCPLN determines which ships will undergo
refitting and when, and will allocate the budget monies to STARSHIPS for building and
refitting the fleet. Figure 2a11.5 presents the organizational structure for this office.
Within this office is the Star Fleet Ship Requirements Section, which has the primary
responsibility for analyzing and determining the number, types and classes of ships needed
to maintain an effective operating force, with the exception of those vessels assigned to
the Star Fleet Transportation Command, the Star Fleet Exploration Command and
the Star Fleet Construction Command. Based upon the results of its studies, this office
will work with the Star Fleet Office of Planning and Budgets in the allocation of the
funds required to design and construct new vessels or in the budgeting for the repair and
maintenance of currently active vessels. In addition, it is this office that is specifically
responsible for maintaining the Star Fleet Vessel Register.
The basic function of the Star Fleet Ship Allocation Section is to acquire ships for the
fleet. However, this does not include ships that are leased or procured for use by the Star
Fleet Transportation Command. That is, this section will only allocate ships that will
have a NCC designation and does not have any authority over the allocation of ships that
will have a NAS or other designation. For new ships, this section will submit procurement
orders to the Star Ship Systems Command for the construction of new Star Fleet
ships. Once such ships are built and ready for space, the Allocation Section will become
involved in the receipt of the ship prior to service through acceptance trials and tests, and
will work with the Star Fleet Office of Startup and Testing within STARSHIPS in the
development of the acceptance test plans.
In addition, this section may also allocate ships from the Reserve fleet as well. Should the
use of older ships become necessary, the Allocation Section will submit a request to the
Star Fleet Reserve Ships Command (RSHIPS) for the reactivation of ships that are
currently in reserve or “Inactive Status”. Should a ship in reserve require upgrading, it
will be the responsibility of the Allocation Section to submit the requirements to
RSHIPS, which will move the ship to a Star Fleet Construction facility for refitting.

VOLUME II
OFFICE OF STAR FLEET SHIP SERVICES
The function of the Office of Star Fleet Ship Services (SSCSRV) is to determine and
provide the fleet with the personal needs of ship crews, as well as determining the type of
recreational facilities that will be built into ships. Such recreational facilities include rest
and lounge areas, theaters, gymnasiums and shops. As such, this office is primarily
concerned with the personal environment in order to foster a high degree of morale
onboard ships. Figure 2a11.6 presents the organizational structure for this office. The
various organizations within this office will be described in the subsequent paragraphs.
Within the Office of Star Fleet Ship Services the Star Fleet Ship Habitability
Section is primarily responsible for the basic work and living environment on board ships.
As such, this section is responsible for developing the requirements regarding equipment
ergonomics, comfort parameters such as average temperature and pressure, the types of
background sounds that may be played on board Star Fleet ships and any kind of odors
that may be injected into the atmosphere. This section is also responsible for designing the
basic crew quarters, including colors schemes, and will submit the requirements to the
Star Ship Systems Command (STARSHIPS) for incorporation into the overall ship
design specifications. Most of the personnel that work in this section are Star Fleet social
psychologists, but this office will also contain civilian contractors such as graphic and
interior designers, and architectural psychologists.
The function of the Star Fleet Ship Recreation Section is to determine and supply the
recreational needs of Star Fleet ships. In addition, this section will also develop the
requirements for recreational areas, their sizes and the equipment to be installed in these
areas. This section also works with STARSHIPS in the design of recreational spaces and
in the procurement of the recreational and entertainment equipment needed to furnish
these spaces.
The Star Fleet Ship Stores Section was created to manage the small shops and stores
that may be built into Star Fleet ships. Some of the larger Starships will contain small
shops or stores where crewmembers can purchase personal items such as clothing,
jewelry, toiletries and other non-military personal items. The purpose for this is to provide
crewmembers with a sense of being “at home” while embarked on the long journeys
through space. As such, the Ship Stores section is responsible for providing such shops
and stores with merchandise and will work with the Office of Star Fleet Ship Materiel
and the Star Fleet Office of Personnel Materiel and Supply in the allocation of the
merchandise required in meeting the needs of Star Fleet ship personnel.

VOLUME II
STAR FLEET SERVICE CRAFT COMMAND
The function of the Star Fleet Service Craft Command (CRAFTCOM) is to manage the
entire operating fleet of Star Fleet Shuttlecraft, Interceptors and other forms of craft
used for functional operations. This, however, does not include any craft used at facilities
under the administration of the Star Fleet Division of Engineering. This office is tasked
primarily with determining the types and classes of craft that are required to support fleet
operations, to make the needed requests to the Star Fleet Service Craft Command for
the construction or allocation of such craft, and to assign such craft to Star Fleet units.
One of the major offices within the Star Fleet Service Craft Command, shown in Figure
2a11.7, is the Service Craft Requirements Section, which determines the number and
types of service and fighter craft needed to support the fleet. In addition, this office will
work with the Star Fleet Service Craft Systems Command in establishing the
standards regarding the color schemes of the various classes of craft, as well as the size
and location of emblems, registry numbers and pennants.
The general function of the Service Craft Allocation Section is to allocate or procure
service and fighter craft, and will place the orders for the construction of such craft with
the Star Fleet Service Craft Systems Command. As part of its procurement
responsibilities, this section will monitor the progress of the construction of such craft and
will perform the acceptance inspections and space trials when such craft are ready for
delivery.
Within CRAFTCOM the Service Craft Operations Section maintains the Service Craft
Register in terms of the assignment and location of the Star Fleet service craft under
their authority. In most instances this section is primarily concerned with the assignment
to newly constructed ships, bases and stations. However, this section is also responsible
for the assignment of replacement craft to the Operating Forces and the Shore
Establishment as well. In addition, this section will be responsible for developing and
assigning fighter and interceptor craft to Fleet Fighter Squadrons, Groups, Wings and
other organizational units as well.
The function of the Service Craft Management Section is to maintain the service craft
fleet for the Operating Forces and the Shore Establishment in a maximum state of
readiness and service. As such, this section performs periodic and random inspections of
fleet service craft to determine their readiness and worthiness for fleet duty. This is an
informal inspection of a craft’s space worthiness and should not be confused with a formal
In-service Inspection or INSURV performed by the Office of the Inspector
General. In addition, this section is partially responsible for developing the maintenance
schedules of all craft and their systems, and will work with Star Fleet Service Craft
Systems Command in developing Preventive Maintenance and overhaul schedules
for all service craft based upon their duty cycle.
Within CRAFTCOM the Combat Craft Operations Section generally develops the
tactics and operations that are employed by fighter and interceptor craft.
The Combat Craft Training Section develops the programs and requirements for
training fighter craft pilots. Training includes knowledge of the craft and its components,
how to operate and fly craft and the various tactics and maneuvers used for space combat.

VOLUME II
ORGANIZATION CHARTS
The subsequent page presents the organizational chart for the Star Ship Command. The
title block for each office within the division contains the name of the division, the division
number and the Office Designator. The Office Designation is a shorthand version of the
division name.
Division Number Office Title
2100
Star Ship Command
SSC
Office Designator

VOLUME II

VOLUME II
Figure 2a11.1
STAR SHIP COMMAND
2100
Star Ship Command
SSC
2110 Office of 2120 Office of 2130 Office of 2140 Office of

Star Fleet Ship Star Fleet Ship Star Fleet Ship Star Fleet Ship
SSCPER Personnel SSCOPS Operations SSCMAT Materiel SSCPLN Planning
2150 Office of 2160 Star Fleet

Star Fleet Ship Service Craft
SSCSRV Services CRAFTCOM Command
2170 Star Fleet

Operations
OPSCEN Center

VOLUME II
Figure 2a11.2
OFFICE OF STAR FLEET SHIP PERSONNEL
6100 Star Fleet 2110 Office of

Bureau of Star Fleet Ship
BUPERS Personnel SSCPER Personnel
2111 Star Fleet Ship 2112 Star Fleet Ship 2113 Star Fleet Ship 2114 Star Fleet Ship
Personnel Personnel Personnel Commanders
SSCPER Requirements Section SSCPER Certification Section SSCPER Assignment Section SSCPER Section

VOLUME II
Figure 2a11.3
OFFICE OF STAR FLEET SHIP OPERATIONS
2120 Office of
Star Fleet Ship
SSCOPS Operations
2129 Star Fleet

Board of
SSCOPS Inquiry
2121 Star Fleet 2122 Star Fleet Ship 2123 Star Fleet 2124 Star Fleet Ship
Ship Assignment Operations Planning Ship Readiness Operations and
SSCOPS Section SSCOPS Section SSCOPS Section SSCOPS Processes Section
2125 Star Fleet Ship

Mission Control
SSCOPS Center

VOLUME II
Figure 2a11.4
OFFICE OF STAR FLEET SHIP MATERIEL

Supply Star Fleet Ship
SUPCOM Command SSCMAT Materiel
2131 Star Fleet Ship 2132 Star Fleet Ship 2133 Star Fleet Ship
Supply Requirements Supply Planning Supply Allocation
SSCMAT Section SSCMAT Section SSCMAT Section

VOLUME II
Figure 2a11.5
OFFICE OF STAR FLEET SHIP PLANNING
2140 Office of
Star Fleet Ship
SSCPLN Planning
2141 Star Fleet 2142 Star Fleet

Ship Requirements Ship Allocation
SSCPLN Section SSCPLN Section

VOLUME II
Figure 2a11.6
OFFICE OF STAR FLEET SHIP SERVICES
2150 Office of
Star Fleet Ship
SSCSRV Services
2151 Star Fleet Ship 2152 Star Fleet Ship 2153 Star Fleet
Habitability Recreation Ship Stores
SSCSRV Section SSCSRV Section SSCSRV Section

VOLUME II
Figure 2a11.7
STAR FLEET SERVICE CRAFT COMMAND
2160 Star Fleet

Service Craft
CRAFTCOM Command
2161 Service Craft 2162 Service Craft 2163 Service Craft 2164 Service Craft
Requirements Allocation Operations Management
CRAFTREQ Section CRAFTALC Section CRAFTOPS Section CRAFTMGT Section
2165 Combat Craft 2166 Combat Craft

Operations Training
CRAFTCBO Section CRAFTCBT Section

VOLUME II

VOLUME II
1.2 STAR BASE COMMAND[2]

In this section the structure of Star Base Command, a subdivision of the Division of
Operations, will be discussed. The function of Star Base Command (SBC) is to
manage the operations of the Shore Establishment, which includes all Star Fleet
bases, stations, outposts, their personnel, and all the buildings, equipment and assets
contained therein. As with Star Ship Command Star Base Command is a branch of the
Star Fleet Service as specified in Star Fleet Regulation 5100. Star Base Command
is essentially an administrative command and as such, this “Type Command” is primarily
involved with the management of Star Fleet Bases, Stations and Outposts. In addition
and as delegated to it by the Director: Star Fleet Command, Star Base Command is
responsible for managing and maintaining the Star Fleet Station Register in accordance
with Star Fleet Regulation 2500.
As stated above, Star Base Command is a branch of the Star Fleet Service and as
such, has authority over all personnel assigned to Star Fleet bases and stations. All
personnel assigned to this branch of the Service will have a “SBC” designation applied to
their title or rating as specified in Paragraph 3 of Star Fleet Regulation 5320. In order
to manage the operations of bases and stations, SBC is divided into several offices
designed to handle the various functions associated with base operations. These offices
are shown in Figure 2a12.1 and will be described in the subsequent paragraphs below.
The Deputy Chief: Star Base Command (CSBC) is the senior officer in command of
Star Base Command, and of all activities regarding the operations, assignments and
management of Star Fleet bases, stations and their personnel. The CSBC is an officer of
the line (SBC), and will typically have the rank of Vice Admiral.
RESPONSIBILITY
Star Base Command is basically responsible for all the aspects regarding the operation
and functioning of Star Fleet bases, stations and outposts. In essence, Star Base
Command is responsible for the entire Shore Establishment of Star Fleet and as such,
is responsible to the Chief of Star Fleet Operations for the overall readiness of all bases
and stations in terms of military efficiency, for the servicing of Star Fleet vessels, for base
personnel competence, and to maintain the appropriate force size of bases and stations.
As part of this responsibility, Star Base Command is tasked with ensuring that all its
personnel are properly trained and qualified in the performance of their duties, and that a
high level of morale is maintained within these forces.
In addition, Star Base Command is also responsible to ensure that the Shore
Establishments are provided with all the equipment and supplies necessary in order to
maintain this aspect of the fleet in a high state of readiness.

VOLUME II
STAR BASE COMMAND SYMBOL[3]
The symbol for the Star Base Command utilizes the Star Fleet star placed within a red
rectangle, which symbolizes the Federation, and surrounded by Laurel leaves, which
represents command authority. This symbol is used on all Star Base Command
documents and a version of this symbol is used as a patch worn on the uniforms of all
members of this branch of service.
Illustration 2a12.1
STAR BASE COMMAND SYMBOL
The division is divided into six offices for the delegation of its responsibilities as illustrated
 Office of Star Fleet Base Personnel

 Office of Star Fleet Base Operations
 Office of Star Fleet Base Materiel
 Office of Star Fleet Base Requirements
 Office of Star Fleet Base Facilities
 Office of Star Fleet Base Security

VOLUME II
OFFICE OF STAR FLEET BASE PERSONNEL
Within SBC is the Office of Star Fleet Base Personnel (SBCPER), shown in Figure
2a12.2, operates much the same way as the Star Fleet Division of Personnel and the
Office of Star Fleet Ship Personnel. This office determines base complements, makes
requests to the Star Fleet Bureau of Personnel (BUPERS) for the allocation of SBC
personnel, and works with the Star Fleet Office of Force Planning in determining the
force size of bases and stations. However, it will be BUPERS that will cut the orders to
SBC personnel for their assignments. In addition, this office will also determine the
personnel rotation policy. Personnel assigned to Star Fleet bases and stations will
periodically be rotated to other bases or stations. As such, this office will establish the
criteria for base rotation and reassignment of SBC personnel.
The Office of Star Fleet Base Personnel will also make recommendations regarding the
selection of System Base Commanders to the Chief of Star Fleet Operations
(CSFO). Typically, the CSFO will request SBCPER to supply him with a list of possible
candidates to command major bases, but is not obliged to seek such recommendations
from SBCPER. It is the prerogative of the CSFO to select any eligible flag officer from this
branch of service he desires without the approval of the Director: Star Fleet Command.
However, it will be SBCPER that has responsibility for determining the eligibility of Star
Fleet officers to command Star Fleet bases, stations, outposts and other facilities in
accordance with Star Fleet Regulation 5730, and in the selection and assignment of
Commanding Officers and other personnel to bases and stations.
Another responsibility of SBCPER is to ensure that personnel are properly trained and
qualified to perform their duties. As such, this office is responsible for establishing the
criteria for base duty station qualification, to design the training programs necessary to
fulfill such qualification, and to work with the Star Fleet Training Command in the
completion of such training.
Within the Office of Star Fleet Base Personnel is the Star Fleet Base Personnel
Requirements Section which determines the numbers and rates of personnel to be
allocated to Star Fleet bases and stations. The Personnel Requirements Section
works with the Star Fleet Office of Force Planning in setting the force complements.
The Star Fleet Base Personnel Assignment Section handles all the aspects regarding
the assignment of Star Base Command personnel to Star Fleet bases and stations. This
section will work with the Star Fleet Office of Personnel Assignment regarding what
bases or stations will need manpower replacements and to assign SBC personnel to such
bases and stations based upon this need. As such, this office will submit the requests to
BUPERS, which will issue the orders for assignment to shore duty.
The Star Fleet Base Commanders Section is essentially responsible for establishing
the requirements for officers to become Star Fleet Base Commanding Officers. As
such, this office will manage the Commanding Officer Training and Certification
Program, and will make recommendations to the Chief of Star Fleet Operations and
the Chief of Star Fleet Personnel regarding the readiness of individuals to become base
and station Commanders. This training includes base and personnel management as well
as Star Fleet vessel maintenance procedures and scheduling.

VOLUME II
OFFICE OF STAR FLEET BASE OPERATIONS
The function of the Office of Star Fleet Base Operations (SBCOPS) is to manage all
Star Fleet bases and stations located throughout the Federation. As such, this office
establishes the functional mission of all Star Fleet bases, stations, outposts and other
facilities, and will determine where such Star Fleet bases and stations will be located, as
well as the number of personnel, troops and other units that will be assigned to such
bases, stations, garrisons and outposts. In general, this office has the responsibility to
analyze and determine the number, types and classes of bases and stations, the size and
power of their defensive systems, and to select the location of such bases and stations in
concert with the Star Fleet Office of Strategic Planning.
Within the Office of Star Fleet Base Operations, illustrated in Figure 2a12.3, is the
Star Fleet Base Operations Planning Section, whose primary function is to plan,
organize and monitor the missions to which Star Fleet bases and stations will be
assigned. The planning of the basic missions and functions of Star Fleet bases and
stations will be performed in conjunction with the Office of Star Fleet Ship Operations
in coordinating the activities involving both ships and bases. Monitoring of the missions or
functions assigned to bases will be performed at the Star Fleet Operations Center
where communications, sensors and other methods can be utilized to evaluate the
conditions occurring at Star Fleet bases and stations. In addition, it is this office that is
specifically responsible for maintaining the Star Fleet Station Register.
The Star Fleet Base Readiness Section monitors and inspects bases and stations for
the purpose of determining their readiness. As such, this section develops the standard
drills and exercises internal to the organization of Star Fleet bases and stations which are
designed to test the readiness of their personnel, their operating and contingency plans,
and their emergency procedures. As part of its responsibility for base readiness, the Base
Readiness Section will investigate any situation that may affect the status and readiness
of any base or station, and will set up such Boards of Inquiry as needed to investigate
any loss of, or damage to Star Fleet bases and stations and report their findings to the
Director.
The function of the Star Fleet Base Operations and Processes Section is to develop
and establish the organizational structure of Star Fleet bases and stations. This section
created the basic organizational structure and the general “Chain of Command” for the
Shore Establishment. In addition, this section is also responsible for establishing the
basic duty stations, routines and basic watch rotation for all bases and stations within Star
Fleet. As such, this section will create the Station Operations and Regulations
Manuals (SORM) for each Star Fleet base and station. In general, this office is
responsible for developing and maintaining all the procedures and regulations required for
the efficient and safe operation of the Shore Establishment.

VOLUME II
OFFICE OF STAR FLEET BASE MATERIEL
The function of the Office of Star Fleet Base Materiel (SBCMAT) is to provide all
bases and stations with the equipment and supplies needed to function effectively. As part
of this function, this office will plan and schedule all supply runs to bases and stations, and
will work with the Star Fleet Transportation Command in the delivery of supplies to
bases and stations. SBCMAT is also responsible for submitting the logistical requirements
of bases and stations to the Star Fleet Office of Fleet Logistics for the allocation of the
materials and supplies required by units of the Shore Establishment. The organizational
chart for this office is illustrated in Figure 2a12.4.
Within the Office of Star Fleet Base Materiel the Star Fleet Base Supply
Requirements Section is responsible to assess the material needs of the Shore
Establishment and the personnel within Star Base Command. The primary function of
this office is to ensure an adequate supply of tools, spare parts, replacement equipment,
service craft, and food stuffs for Star Fleet bases, stations and outposts. This section will
analyze and determine the material needs for the entire Shore Establishment based
upon the material requirements gathered from all the various supply and procurement
officers of the operating commands, and based upon these inputs this office will make
plans, budgets and schedules for the procurement of the materials, goods and services. In
accomplishing this goal, this section will work with the Star Fleet Office of Fleet
Logistics in determining the budgetary requirements and the materiel needs of the entire
Shore Establishment.
The Star Fleet Base Supply Planning Section within SBCMAT handles all the planning
and distribution of supplies to the Shore Establishment. As part of this function, this
office will work with the Star Fleet Transportation Command and the Star Fleet
Logistical Operations Section in the planning and scheduling of supply shipments and
convoys to the various bases, stations and outposts throughout the Federation.
The function of the Star Fleet Base Supply Allocation Section is to manage all
activities regarding the allocation of the material and equipment for the Shore
Establishment. As such, this section will work with the Star Fleet Supply Command in
obtaining the materials, equipment and supplies needed to maintain the Star Fleet bases,
stations and outposts in a state of maximum readiness. In addition, this section will also
develop the procedures for allocating and procuring materiel for the fleet, and will train
Star Fleet Base Supply Officers in such procedures.

VOLUME II
OFFICE OF STAR FLEET BASE REQUIREMENTS
The Office of Star Fleet Base Requirements (SBCREQ) is responsible for determining
the design and operating requirements of bases and stations. Such requirements include
the structural needs of bases and stations based upon local conditions, the offensive and
defensive needs of the station, and the manpower required to operate and maintain the
base or station. In general, this office has the responsibility to analyze and determine the
requirements of potential new bases and stations, and will work with the Star Fleet
Office of Strategic Planning regarding the requirements for selecting the location of
such bases and stations. Figure 2a12.5 presents the organizational structure for this office.
Within SBCREQ the Star Fleet Base Requirements and Specifications Section is the
office with the primary responsibility for determining the location and construction of Star
Fleet bases and stations. This section will work with the Star Fleet Office of Strategic
Planning in determining where Star Fleet bases and stations should be located and
then, work with the Star Fleet Space Exploration Command in assembling the survey
teams used to evaluate the suitability of the location or area of space for the construction
of a Star Fleet base or station. Once all the survey information has been obtained, this
section will create and submit the base or station design specifications to the Star Base
Systems Command (STARBASES) for translation into actual designs and plans. This
section will then work with the STARBASES in the design and construction of the base or
station.
The primary function of the Star Fleet Base Construction Design Section is to create
the building and structural or infrastructure layout plans and specifications of planetary-
based Starbases and stations. Based upon the data developed from the Requirements
and Specifications Section, this section will determine the general appearance of the
bases in terms of the placement and orientation of buildings and structures, including any
parks or other recreational areas. This section will work with Star Fleet Office of Base
Architecture, within STARBASES, regarding the architectural layout of all Star Fleet
bases, which includes the development of the underground infrastructure as well. The
layout specifications will then be submitted to the Requirements and Specifications
Section for incorporation into the overall base construction specification that will be sent
to the Star Base Systems Command.
The function of the Star Fleet Base Defensive Systems Section is to determine the
basic defensive needs for any new base or station that will be built. This section will
determine the number, sizes and power of the permanently mounted weapons units that
should be installed at any given base or station. Primarily, these units are large phaser and
pulse cannons mounted on stanchions or towers located at the periphery of the base. In
addition, this section will determine the power requirements for any defensive shields that
may be installed on the base. As such, this section will work with the Star Fleet
Weapons Command and other units of the Star Fleet Division of Engineering in the
design and allocation of defensive weapon systems.

VOLUME II
OFFICE OF STAR FLEET BASE FACILITIES
The function of the Office of Star Fleet Base Facilities (SBCFAC) is to determine the
functional needs of Star Fleet bases and stations. This office will work with the Star
Fleet Corps of Engineers in the design and architecture of the structures and buildings
to be constructed at base sites to ensure compliance with specifications. Along with the
design of the base, this office will work with the Star Fleet Construction Command
during the construction of bases and stations to ensure that the specifications are fulfilled.
In addition, this office will also determine the requirements for any auxiliary structures and
equipment that may be necessary to support the operations at a base such as fire
suppression and recreational facilities. As such, this office is responsible for allocating and
purchasing all the basic equipment needed to support base and station operations, and to
provide base and station personnel with any personal items they may require. Figure
2a12.6 presents the organizational structure for this office. The various organizations
within this office will be described in the subsequent paragraphs.
Within the Office of Star Fleet Base Facilities the Star Fleet Base Habitability
Section is primarily responsible for the work environment of bases and stations. As such,
this section is responsible for developing the requirements and standards concerning
equipment ergonomics, comfort parameters such as average temperature and pressure,
and the types of background sounds that may be played on board enclosed Star Fleet
stations. As part of this function, this section will be responsible for designing standardized
crews quarters, including colors and patterns, and will submit the requirements to the Star
Base Systems Command (STARBASES) for incorporation into the design specifications.
Most of the personnel who work in this office are Star Fleet social psychologists, but may
also contain civilian contractors such as graphic and interior designers, and architectural
psychologists.
The function of the Star Fleet Base Recreation Section is to determine and supply the
recreational needs of Star Fleet bases and stations. In addition, this section will also
develop the requirements for recreational areas, their sizes and the equipment to be
installed in these areas. This section also works with STARBASES in the design of indoor
and outdoor recreational areas, and in the allocation of the recreational and entertainment
equipment needed to outfit these areas. In addition, this section will also be involved in
the design and outfitting of special areas where Star Fleet personnel may relax by
becoming engaged in a hobby or activity. Such activities may include repair shops where
personnel may work on their own vehicles or to fabricate personal items.
The Star Fleet Base Stores Section was created to manage the shops and stores that
may be built at Star Fleet bases or stations. All Star Fleet bases and large stations
contain shopping malls and stores where Star Fleet personnel can purchase food and
personal items such as clothing, jewelry, toiletries, vehicles and other non-military personal
items. The purpose for this is to provide personnel with a feeling of community or of being
“at home” while away from home. As such, the Base Stores section is responsible for
providing such shops and stores with food and merchandise. To accomplish this goal, this
section will work with the Office of Star Fleet Base Materiel and the Star Fleet Office
of Personnel Materiel and Supply in allocating the merchandise required in meeting
the needs of Star Fleet base and station personnel.

VOLUME II
OFFICE OF STAR FLEET BASE SECURITY
The function of the Office of Star Fleet Base Security (SBCSEC) is to determine the
security needs of Star Fleet bases and stations. This office will work with the Star Fleet
Security Forces Command in allocating base security personnel. In addition, this office
will also develop the structure for the base Military Police force used in maintaining law
and order on the base. Figure 2a12.7 presents the organizational structure for the Office
of Star Fleet Base Security.
The Star Fleet Base Security Requirements Section determines the base security
needs in terms of the number of security personnel, the level of physical security and the
amount and types of small arms that are necessary to keep the base or station secure. In
order to determine such security needs, this section performs security and threat studies
on areas where a base may be located. Personnel from this section will be part of the
survey team under the direction of the Office of Star Fleet Base Requirements when
evaluating an area for the location of a base or station. In addition, this section will also
periodically evaluate the existing base security infrastructure in order to determine any
deficiencies and make such recommendations as necessary to correct such deficiencies.
The primary function of the Star Fleet Base Security Personnel Section is to allocate
the security force for Star Fleet bases and stations. As such, this section will work with
the Star Fleet Security Forces Command in allocating security personnel to bases and
stations. In addition, this section is responsible for assigning Security Personnel
Officers to bases and stations for the management and discipline of base security
personnel.
The function of the Star Fleet Base Security Supply Section is to keep the security
forces supplied with the materials and equipment needed to maintain an efficient and
effective security force. Such equipment generally entails small arms, ground vehicles,
personal protection devices and other such supplies. Other supplies may include forensic
or other such equipment needed for the investigative staff of the security force as well.
The Star Fleet Base Law Enforcement Section establishes the structure for the
Military Police forces used at planetary Starbases. The function of the Military Police
force is to maintain law and order on such Starbases and as such, this section will
develop the procedures used by the Military Police force in the maintenance of law and
order at these bases. This function is not the same as the regular security force, which is
designed to guard sensitive areas and perform plain clothes security functions. The
Military Police is a small force of security personnel under the direction of a Provost
Marshal used strictly to enforce base law. Therefore, this section will also select and
assign Provost Marshals to Starbases and Star Fleet Headquarters. In addition, this
section will work with the Star Fleet Security Forces Command in the selection of
Provost Marshals and the Bureau of Star Fleet Personnel regarding the assignment
of Provost Marshals.

VOLUME II
ORGANIZATION CHARTS
The subsequent page presents the organizational chart for the Star Base Command. The
title block for each office within the division contains the name of the division, the division
number and the Office Designator. The Office Designation is a shorthand version of the
division name.
2200
Star Base Command
SBC
Office Designator

VOLUME II

VOLUME II
Figure 2a12.1
STAR BASE COMMAND
2200
Star Base Command
SBC
2210 Office of 2220 Office of 2230 Office of 2240 Office of

Star Fleet Base Star Fleet Base Star Fleet Base Star Fleet Base
SBCPER Personnel SBCOPS Operations SBCMAT Materiel SBCREQ Requirements
2250 Office of 2260 Office of

Star Fleet Base Star Fleet Base
SBCFAC Facilities SBCSEC Security

VOLUME II
Figure 2a12.2
OFFICE OF STAR FLEET BASE PERSONNEL

Bureau of Star Fleet Base
BUPERS Personnel SBCPER Personnel
2211 Star Fleet Base 2212 Star Fleet Base 2213 Star Fleet Base
Personnel Personnel Commanders
SBCPERREQ Requirements Section SBCPERASN Assignment Section SBCPERCMD Section

VOLUME II
Figure 2a12.3
OFFICE OF STAR FLEET BASE OPERATIONS
2220 Office of
Star Fleet Base
SBCOPS Operations
2229 Star Fleet

Board of
SBCOPS Inquiry
2221 Star Fleet Base 2222 Star Fleet 2223 Star Fleet Base
Operations Planning Base Readiness Operations and
SBCOPSPLN Section SBCOPSRED Section SBCOPSPRC Processes Section

VOLUME II
Figure 2a12.4
OFFICE OF STAR FLEET BASE MATERIEL

Supply Star Fleet Base
SUPCOM Command SBCMAT Materiel
Supply Requirements Supply Planning Supply Allocation
SBCMATREQ Section SBCMATPLN Section SBCMATALC Section

VOLUME II
Figure 2a12.5
OFFICE OF STAR FLEET BASE REQUIREMENTS

Office of Star Fleet Base
SFPLAN Strategic Planning SBCREQ Requirements
Requirements & Construction Defensive
SBCREQSPC Specifications Section SBCREQDSN Design Section SBCREQDEF Systems Section
3400 Star Base 3420 Star Fleet 3800 Star Fleet

Systems Office of Weapons
STARBASES Command STARBASES Base Architecture WEPSCOM Command

VOLUME II
Figure 2a12.6
OFFICE OF STAR FLEET BASE FACILITIES
2250 Office of
Star Fleet Base
SBCFAC Facilities
2251 Star Fleet Base 2252 Star Fleet Base 2253 Star Fleet
Habitability Recreation Base Stores
SBCFACHAB Section SBCFACENT Section SBCFACMKT Section

VOLUME II
Figure 2a12.7
OFFICE OF STAR FLEET BASE SECURITY

Security Forces Star Fleet Base
SECFOR Command SBCSEC Security
2261 Star Fleet Base 2262 Star Fleet Base 2263 Star Fleet Base 2264 Star Fleet Base
Security Security Personnel Security Supply Law Enforcement
SBCSECREQ Requirements Section SBCSECPER Section SBCSECSUP Section SBCSECENF Section

VOLUME II

VOLUME II
1.3 STAR FLEET ADJUNCT FORCES

COMMAND
The function of Local Forces is to protect the interests of, and maintain the laws and
regulations of the local system government to which they serve. In times of war or galactic
emergency, member systems are required, under ARTICLE 43 of the Articles of
Federation, to transfer a portion or all of their Local Force to Star Fleet in order to
augment Star Fleet forces. When integrated into Star Fleet such forces are known as
Adjunct Forces. To help in transitioning these forces Star Fleet created a special
organization designed specifically to prepare Local Forces to be adjoined into a unified
Star Fleet command. This organization is the Star Fleet Adjunct Forces Command
(AFOR), which is separately organized within Star Fleet Operations.
The basic function of the Star Fleet Adjunct Forces Command is to manage all
activities regarding the operations and missions of the Local Forces that are adjoined to
Star Fleet in a unified command as specified in ARTICLE 15 of the Star Fleet Charter,
and to keep the Chief of Star Fleet Operations informed on the state and readiness of
such forces. In addition, this office will develop joint strategic and tactical operations with
Local Forces in order to establish and maintain effective battle plans should such forces
become necessary. This is typically done through the development of specific “Task
Commands” utilizing such forces.
In command of AFOR is the Deputy Chief: Adjunct Forces (CFOR) who is the senior
officer in charge of all activities regarding the operations and missions of the Local
Forces adjoined to Star Fleet in a unified command. The CFOR is an officer of the line
and will typically have the rank of Vice Admiral. The CFOR is directly responsible to the
Chief of Star Fleet Operations for:
1. The assignment of Federation Local Forces to Star Fleet commands and units,
2. The development of specific task commands utilizing Adjunct Forces,
3. Keeping the CSFO informed on the status and readiness of Local Forces,
4. Maintaining communication and close relationships with Local Force Commanders,
which is accomplished through the use of Local Force Liaison Officers assigned to
the Local Force Commands,
5. The training of Local Force Commanders and personnel in Star Fleet protocol,
operations, regulations and procedures,
6. Determining the needs and requirements for unified commands, and
7. Developing joint strategic and tactical operations with Local Forces.
A complete list of the Local Forces available to Star Fleet may be found in Table 1a16.1
in Volume I of the Star Fleet Command Manual.
The Adjunct Forces Command contains four administrative offices for the management
of the command. Each of these offices will be described in the subsequent sections of this
chapter. The top-level organization chart for AFOR is illustrated in Figure 2a13.1.

VOLUME II
STAR FLEET OFFICE OF LOCAL FORCE PLANNING
Within AFOR the Star Fleet Office of Local Force Planning has the responsibility of
planning the employment of the Local Forces that are assigned to Star Fleet. As such,
this office determines where Local Forces are needed within the fleet, the strength of the
force required and into what Star Fleet command structure they will be placed. Once the
requirements have been established, this office will then assign Local Forces to Star
Fleet commands and units. As part of this planning function this office will receive periodic
reports from the Star Fleet Office of Local Force Readiness on the state of the various
Local Forces that may be assigned to Star Fleet units. In general, the state of readiness
of a Local Force is extremely important in order to determine how they can best be used.
Figure 2a13.2 presents the organizational structure for this office.
This office will also make plans relating to the exact use of particular Local Forces during
Federation emergency conditions. As such, this office will develop the strategies given to
Local Forces relating to their deployment within a specific theatre of operations. In most
cases this office develops the plans for assignment of Local Forces to specific Star Fleet
units and will relay such plans to the Local Force Liaison Officer assigned to the Local
Force.
The Star Fleet Local Force Resource Section analyzes the capabilities of Local
Forces in terms of the number of vessels, troop levels and other assets that could be
employed within Star Fleet. Most of the information will come from the Office of Local
Force Readiness. This information is vitally important as it is used to determine the
deployment strategies of Local Force units.
The Star Fleet Local Force Assignment Section will determine where best to place a
Local Force unit within the Operating Forces of Star Fleet. Weight will be given to the
location of the force relative to the location of Star Fleet forces in the area. However, for
Local Forces with a high volume of assets, they may be assigned to any Star Fleet unit
deployed throughout Federation space. This section pre-plans the assignment of Local
Forces based upon simulations of the various combat and strategic scenarios. Should
there be the need to employ Local Forces to a specific situation it is this section that will
make the recommendations to the Deputy Chief: Adjunct Forces regarding the
application of those forces. The recommendations will be submitted up the chain of
command and eventually, the Local Force Commanders will be made aware of their
place within the command structure of Star Fleet.
The Star Fleet Local Force Databank is a database of all the capabilities, equipment,
force size and commanders of all the available Local Forces. This database is
continuously updated with information from the Local Force Readiness and Local
Force Training sections. It is from this databank that the Local Force Assignment
Section will make its decisions on where to place a Local Force unit within the structure
of Star Fleet and what their role within the combined force will be.

VOLUME II
STAR FLEET OFFICE OF LOCAL FORCE READINESS
The function of the Star Fleet Office of Local Force Readiness is to assess the
capabilities and materiel needs of the various Local Forces available to Star Fleet, and
to evaluate their strengths and weaknesses in terms of their operational readiness. Once
assessed, this office will make recommendations to the Local Force Commanders,
through the Local Force Liaison Officer, regarding the changes that may be needed in
order to merge and operate within Star Fleet. Figure 2a13.3 presents the organizational
structure for this office.
The Star Fleet Local Force Standards Section within AFOR has the responsibility for
developing the standards and procedures regarding the integration of Local Forces into
Star Fleet, as well as the standards concerning the capability and effectiveness of Local
Force equipment. In order for Local Forces to function with the Star Fleet command
structure, they must meet the minimum standards set forth by Star Fleet such as
armament capabilities, and vessel speed and maneuverability capabilities.
In addition, the Star Fleet Local Force Standards Section also has the responsibility
for developing the standards and procedures regarding the interoperability and use of Star
Fleet equipment in Local Force assets. This section will work with the builders of Local
Force vessels in the design of their ships so that they may be allowed to easily incorporate
Star Fleet systems and equipment if and when it becomes necessary. The purpose for
this is to allow a high degree of interchangeability and interoperability between Star Fleet
and Local Force systems.
The job of the Star Fleet Local Force Evaluation Section is to observe and evaluate
the readiness of Local Forces. The primary goal of this evaluation is to determine if a
Local Force is ready and up to the challenge of deep space military missions, and
whether the force would make a suitable contribution to the overall effectiveness of a Star
Fleet force. This evaluation is primarily done at the home systems of the Local Forces
while in the execution of their local exercises. To aid in gathering this information the
Local Force Liaison Officer may request a team of Star Fleet personnel to accompany
the Local Force during their exercises.
This section will also evaluate the operating procedures and tactical plans of the Local
Forces as well, the primary purpose of which is to ensure that the operating procedures of
Local Forces contain provisions relating to the joining of their forces into Star Fleet and
to incorporate any Star Fleet procedures relating to force coalescence that may be
required. In addition, a check will be made to ensure that Local Forces are trained in
Star Fleet regulations, procedures and customs so that if they were to be merged the
transition would be as smooth as possible, with little training or time spent on getting the
force up to speed on Star Fleet methods and procedures.

VOLUME II
STAR FLEET OFFICE OF LOCAL FORCE TRAINING
The Star Fleet Office of Local Force Training was set up to bring Local Forces up to
speed on Star Fleet operations, command processes, procedures, regulations and tactics
in order that the force can seamlessly merge into a unified command with Star Fleet. In
most cases training will involve the Local Force working together with Star Fleet forces
in simulated combat situations, war games and other maneuvers. Such exercises are
performed periodically and are usually scheduled events. Figure 2a13.4 presents the
organizational structure for this office.
The primary function of the Star Fleet Local Force Training Evaluation Section is to
observe and evaluate the performance of Local Forces as they function within the Star
Fleet chain of command. In addition, this section will also evaluate the performance of
both Star Fleet and Local Forces as they work together during combined exercises in
order to uncover any deficiencies in the management of combined operations and to
determine the strengths and limitations of the Local Force as an adjunct unit. The result
of these evaluations will be suggestions and recommendations regarding the type of
training that will be required, and to develop and submit plans regarding such training to
the Star Fleet Local Force Training Programs Section.
The Star Fleet Local Force Training Programs Section develops the processes and
procedures for the training of Local Forces so that they can be eligible and capable to
seamlessly merge into Star Fleet when the time comes. This section also develops the
training exercises and simulations used to evaluate the performance of Local Forces both
as an individual fighting unit and as a combined force within a Star Fleet command
structure. In addition, this section will analyze the training programs of the various Local
Forces in order to ensure that they incorporate Star Fleet processes into their training
programs and to determine if their training program is adequate enough to meet the
needs of Star Fleet.
The Star Fleet Local Force Personnel Training Section is basically responsible for
training Local Force officers and personnel in the procedures, regulations, standards and
tactics used by Star Fleet. As such, this section will work with the Star Fleet Training
Command (TRAINCOM) in developing the indoctrination and training programs given to
Local Force personnel regarding Star Fleet processes and procedures. TRAINCOM has
specific classrooms and training facilities whereby Local Force personnel can come and
attend such classes. Although training is performed mainly at Star Fleet facilities, training
can also be performed at Local Force facilities as well. In addition, the Star Fleet
Academy also has classes and facilities to train Local Force personnel in combat tactics
and strategies.

VOLUME II
STAR FLEET OFFICE OF LOCAL FORCE MATERIEL
The function of the Star Fleet Office of Local Force Materiel is to equip Local Forces
with the weaponry, equipment and other material they require in order that they can
effectively operate within the Star Fleet command and control structure. In addition, this
office will assess the materiel needs of all Local Forces in order to determine any possible
deficiency in their material status should they be integrated into Star Fleet, and to
determine the equipment needs and requirements for the unified commands containing
such forces. Where such deficiencies exist, it will be the responsibility of this office to
correct them. To accomplish these aims, the Star Fleet Office of Local Force Materiel
is divided into three functional sections designed to manage these responsibilities. Figure
2a13.5 presents the organizational structure for this office.
The function of the Star Fleet Local Force Material Evaluation Section is to evaluate
the material condition and suitability of Local Force equipment. Basically, this information
is obtained from reports submitted by the Readiness Evaluation Section regarding the
state of Local Force equipment. In addition, this section will also analyze Local Forces in
terms of their consumption of consumable goods. This is necessary in order to determine
the logistical needs of the Local Force so that Star Fleet forces can plan for the total
logistical needs of the combined force.
The primary function of the Star Fleet Local Force Material Engineering Section is to
perform engineering evaluations on Local Force equipment in order to determine if Star
Fleet equipment can be integrated into Local Force systems. Engineers within the
section will go to Local Force facilities to perform studies relating to any design or
construction issue that may apply regarding the incorporation of Star Fleet components
into Local Force equipment and systems. Based upon the results of these studies, this
section, as well as Star Fleet Engineering, will work with the Local Force regarding
modifications to their systems in order that Star Fleet equipment may be retrofitted to
their machinery.
The Star Fleet Local Force Supply Section allocates the materials and equipment
necessary to retrofit or upgrade Local Force equipment and systems. This includes all
materials used in the preparation of the Local Force system to accept Star Fleet
equipment. As such, this section will work with the Star Fleet Supply Command in the
allocation and procurement of such materiel and equipment. In addition, this section also
maintains an accounting of the material given or lent by Star Fleet to Local Forces. The
purpose of this is to prevent unauthorized use or lending of Star Fleet equipment by
Local Forces. And after joint operations have been concluded, the equipment lent by
Star Fleet must be returned.
On the surface the actions taken by this office may appear to violate Star Fleet
Regulation 8790, which prohibits Star Fleet property to be given, leased or lent to any
agency outside of the Department. However, ARTICLES 48 and 49 of the Articles of
Federation require that Local Forces assist Star Fleet during any action that requires
their support. In order that the adjunct forces can effectively support Star Fleet in such
matters it may become necessary that Local Forces be equipped with Star Fleet
materiel. As such, the Federation Council has given Star Fleet carte blanche to lend or
supply Local Forces with certain Star Fleet equipment should it become necessary, but
only in this particular instance and only to bonafide Local Forces of member systems.

VOLUME II
LOCAL FORCE LIAISON OFFICES
AFOR has offices located on the worlds of Local Forces in order to maintain close
communication and relationships with such forces, and to assess the state of readiness of
that force. By working within the Local Force command structure and understanding
Local Force operations, Star Fleet can assess the capabilities of these forces. As such,
this office will periodically submit reports to the Adjunct Forces Command on the state
of readiness of the Local Force and will develop specific plans regarding the integration of
Local Forces into Star Fleet.
Each local office will have a Local Force Liaison Officer or FORCEREP assigned to it
that has the responsibility to interact with Local Force Commanders on the matters
described above. In addition, FORCEREPS are given sufficient authority to act on behalf
of Star Fleet Command when interacting with Local Force Commanders. As such,
Local Force Liaison Officers will typically have the rank of Captain (SSC) and they
report directly to the Deputy Chief: Adjunct Forces. The Liaison Officer’s staff will
typically be composed of a junior officer to aid the FORCEREP in his duties and a yeoman
who will compose and issue the required reports. The following table lists the worlds in
which a FORCEREP will be assigned.
Table 2a13.1
TABLE OF LOCAL FORCE LIAISON OFFICER ASSIGNMENTS
FORCEREP
Federation System Present Local Force Local Force Commander
SOL: Earth Y Commander in Chief:
United Earth Forces United Earth Forces
SOL: Martian Colonies N (COMSOL)
Allied Forces of Commander in Chief:
Alpha Centauri Y
Alpha Centauri Allied Forces of Alpha Centauri
Director:
UV Ceti: Vulcan Y Vulcan Defense Ministry
Vulcan Defenses
The Grand Fleet of
Epsilon Eridani: Rigel II Y Admiral of the Fleet
Epsilon Eridani
The Armed Forces of Marshal General:
61 Cygni: Tellar Y
61 Cygni Armed Forces of 61 Cygni
Imperial Forces of Supreme Commander:
Epsilon Indii: Andor Y
Epsilon Indii Imperial Forces of Epsilon Indii
40 Eridani: Rigel Armed Forces of the Eridani Commander in Chief:
Y
Colonies Confederation Eridani Confederation Forces
Ariannus Y Defense Forces of Ariannus General of the Force1
The Troyan Hipparchia or
Tellun: Troyius Y The Strategos of Troyius
Armed Forces1
Army of the Republic of Commander in Chief:
Epsilon Canaris III Y
Epsilon Canaris Army of the Republic
Izar Y The Izarian Space Fleet1 Admiral of the Fleet1
Armed Forces of the Malurian Supreme Commander:
Malurian System Y
Star Empire Malurian Imperial Forces
The Defense Forces of Merak Supreme Commander: Merakian
Merak II Y
II Defense Force
Styris IV N The Styris Constabulary Superintendent
Notes;
1. Equivalent title as translated.

VOLUME II
Figure 2a13.1
STAR FLEET ADJUNCT FORCES COMMAND
2300 Star Fleet

Adjunct Forces
AFOR Command
Office of Local Force Office of Local Force Office of Local Force Office of Local Force
AFOR Planning AFOR Readiness AFOR Training AFOR Materiel
2350 Local Force

Command Liaison
AFOR Offices

VOLUME II
Figure 2a13.2
STAR FLEET OFFICE OF LOCAL FORCE PLANNING

Office of Strategic & Office of Local Force
TAC Tactical Operations AFOR Planning
2311 Star Fleet 2312 Star Fleet 2313 Star Fleet

Local Force Local Force Local Force
AFOR Resource Section AFOR Assignment Section AFOR Databank
0323 Star Fleet

Central
BUMANPUB Records

VOLUME II
Figure 2a13.3
STAR FLEET OFFICE OF LOCAL FORCE READINESS
2320 Star Fleet

Office of Local Force
AFOR Readiness

Local Force Local Force
AFOR Standards Section AFOR Evaluation Section

VOLUME II
Figure 2a13.4
STAR FLEET OFFICE OF LOCAL FORCE TRAINING

Training Office of Local Force
TRAINCOM Command AFOR Training

Local Force Training Local Force Training Local Force Personnel
AFOR Evaluation Section AFOR Programs Section AFOR Training Section

VOLUME II
Figure 2a13.5
STAR FLEET OFFICE OF LOCAL FORCE MATERIEL
2340 Star Fleet

Office of Local Force
AFOR Materiel

Local Force Material Local Force Material Local Force
AFOR Evaluation Section AFOR Engineering Section AFOR Supply Section
7100 Star Fleet

Supply
SUPCOM Command

VOLUME II

VOLUME II
1.4 STAR FLEET INTELLIGENCE

The function of Star Fleet Intelligence (ICOR) is to assist the Director: Star Fleet
Command and the Federation Intelligence Agency in collecting intelligence through
personnel sources and by other appropriate means; correlating and evaluating intelligence
information related to the security of the Federation and to disseminate such intelligence
to the appropriate consumers; providing overall direction for and coordination of the
collection of intelligence outside the Federation through personnel sources by elements
of the Intelligence Community authorized to undertake such collection and, in coordination
with other departments, agencies, or elements of the United Federation of Planets
which are authorized to undertake such collection, ensuring that the most effective use is
made of resources and that appropriate account is taken of the risks to the Federation
and those involved in such collection; and performing such other functions and duties
related to intelligence as the Federation Council President or the Director: Star Fleet
Command may direct as authorized under ARTICLE 8 of the Star Fleet Charter.
The person responsible for the collection of intelligence for Star Fleet, and thus the
Federation, is the Deputy Chief: Star Fleet Intelligence (CINT). The CINT is the
senior officer in charge of all operations and aspects concerning intelligence gathering and
in the management and performance of covert and clandestine activities for Star Fleet.
The CINT will typically be an officer of the line (SFC) and will typically have the rank of
Vice Admiral.
RESPONSIBILITY
Star Fleet Intelligence is basically responsible for all the aspects regarding the
gathering, analyzing and dissemination of intelligence for Star Fleet and the Federation
in accordance with ARTICLE 8 of the Star Fleet Charter. As such, it is responsible for the
operations and missions designed to gather such information, which includes, but not
limited to: documents, communications codes, computer hardware and software, military
equipment, and other special operations. In addition, Star Fleet Intelligence is also
tasked with performing such clandestine and covert operations as may be required or
authorized by the Federation Council and therefore, it will be Star Fleet Intelligence
that will plan, direct, coordinate and execute all such activities.
The division is divided into five offices for the delegation of its responsibilities. As
illustrated in Figure 2a14.1, these subdivisions or offices are:
 Star Fleet Intelligence Operations

 Star Fleet Intelligence Analysis
 Star Fleet Intelligence Personnel
 Star Fleet Intelligence Coordination
 Star Fleet Intelligence Technology

VOLUME II
STAR FLEET INTELLIGENCE OPERATIONS
Within ICOR, Star Fleet Intelligence Operations (IOPS), the organizational structure
shown in Figure 2a14.2, is the primary operational unit tasked with the collection of
intelligence and in the performance of special intelligence activities. This organization
contains all the necessary units for the collection of information and the performance of
clandestine or “black” operations, counter-intelligence, and other forms of espionage. As
such, the above functions are organized into Units or Specialties depending on the nature
of the operation and the level of secrecy, and will have such names as Spec-8, Unit-12
or Section 31.
The Star Fleet Clandestine Service (SFCS), also known simply as the Clandestine
Service, manages and performs the overt and covert operations relating to intelligence for
Star Fleet and the Federation. As such, the Star Fleet Clandestine Service supports
the Federation’s security and foreign policy interests by conducting clandestine activities
designed to collect information that is not obtainable through other means. The Star
Fleet Clandestine Service also serves as the Federation authority for the coordination,
deconfliction, and evaluation of clandestine “personal” intelligence operations across the
intelligence community. As such, SFCS will coordinate all intelligence activities among the
major intelligence agencies across the Federation. In addition, the SFCS will also conduct
counterintelligence and other special activities as authorized by the Federation Council
President.
The function of the Star Fleet Intelligence Operations Planning section is to plan and
organize the operations that will be carried out by the Clandestine Service and by other
intelligence operators. Such planning may involve other Federation intelligence agencies
as well, the purpose of which is to coordinate intelligence activities among the various
agencies within the intelligence community. Therefore, this section will be involved in
planning intelligence operations with the other agencies. However, these other agencies
need not always cooperate with Star Fleet Intelligence since they may be involved in
their own clandestine operations. The only requirement is that Star Fleet Intelligence
be informed as to the general nature of the operation so that operations conducted by
IOPS will not be hindered by other operations.
The function of the Star Fleet Communications Surveillance unit is to gather

information through the monitoring of all communications traffic inside and outside the
Federation. Star Fleet Intelligence has many standard and subspace radio receivers
scattered throughout Federation space for this purpose, the locations of which are
classified.
Star Fleet Intelligence also has an area where the clandestine operations, currently
underway, can be supervised. The center, known as the Star Fleet Intelligence
Operations Center, is located within Starbase Central nearby the Mission Control
Center. This area is extremely sensitive and only authorized personnel are allowed access
to the facility. Such individuals will have security clearances of TOP SECRET or higher.
The Commander: Star Fleet Intelligence Operations (COMINTOPS) is the senior

officer in command of this office. The COMINTOPS is an officer of the line (SFC) and will
typically have the rank of Rear Admiral. Also under the COMINTOPS are the various
Staff Operations Officers situated in the field that manage and coordinate intelligence
activities throughout the galaxy.

VOLUME II
STAR FLEET OFFICE OF INTELLIGENCE ANALYSIS
Analysis of intelligence information gathered by IOPS is performed by the Star Fleet

Office of Intelligence Analysis (INAL). This section gathers the information, correlates
it with other known data, makes security assessments, predictions and recommendations,
and disseminates the information to the proper authorities. It is this section that prepares
the daily intelligence reports and briefings for the Director: Star Fleet Command and to
the Federation Council. This section is also responsible for the Star Fleet Intelligence
Database and the links to other intelligence databases. Figure 2a14.3 presents the
The Socio-Political Analysis Section basically analyzes the political and sociological
state of affairs throughout the known regions of the galaxy. For example, this unit will look
for potential political instabilities that may be occurring on hostile worlds and makes
recommendations on how to exploit such conditions. The information obtained from such
analyses may be useful in developing covert operations by the Clandestine Service. As
such, this unit works very closely with Star Fleet Intelligence Operations.
The Economic Analysis Section analyzes the economic and financial systems of the
many known worlds of the galaxy and to evaluate their effectiveness or search for
weaknesses. In addition, this section tracks the movement and use of financial resources
by hostile worlds and forces. Many of the hostile worlds fund covert operations within the
Federation using seemingly legitimate front corporations and enterprises. As such, it is
the function of this unit to determine and trace the source of such funds and to identify
the entities that may be funding covert operations within the Federation, and where
possible, develop plans to disrupt the flow of such funds, eliminate such funding entities
and confiscate the funds.
The primary function of the Military Analysis Section is to analyze the movements of
hostile forces and to assess the strengths and weaknesses of such forces. The results of
such analyses will be useful to Star Fleet Operations in the assignment of forces to
areas where hostile forces may be concentrated. In addition, this unit will also analyze
information regarding hostile and enemy weapons systems to determine their effectiveness
against Star Fleet and to determine ways to counter the effects of such weapons or to
determine a countermeasure should such weapons be employed against Star Fleet
forces.
The Psychological Analysis Section analyzes the psychological makeup of peoples and
individuals for the purpose of influencing or demoralizing an enemy. Such information may
also be used to develop Psychological Operations (PSYOPS), which are the techniques
used to influence a target audience's value systems, belief systems, emotions, motives,
reasoning, and behavior. Target audiences can be governments, organizations, groups,
and individuals, and are used in order to induce confessions, or reinforce attitudes and
behaviors favorable to the originator's objectives. These are sometimes combined with
black operations and "false flag" tactics.
This section is also involved in the planned use of propaganda and other psychological
actions having the primary purpose of influencing the opinions, emotions, attitudes, and
behavior of hostile foreign groups in such a way as to support the achievement of
Federation objectives. In order to achieve its goals, this section will obtain input from
both the Star Fleet Bureau of Mental Health and the Star Fleet Office of Social
Science.

VOLUME II
The Codes, Ciphers and Decipherment Section analyzes coded transmissions in order
to break the code, and to examine uncoded transmissions for hidden messages or codes
and will compare such codes against Star Fleet’s database of known codes and ciphers.
For unknown codes, this unit will work to decipher any new code or cryptogram and place
it into the database. This unit will also work with the Intelligence Technology section to
reverse-engineer any absconded code machinery or computers, and will develop the
software used to decipher the codes from such machinery.
The function of the Pattern Analysis Section is to find and interpret patterns that may
be embedded in various media for the purpose of passing intelligence information to
hostile governments. These patterns may form a specific code in sending information
through innocuous and open means. The Pattern Analysis Section also contains
machinery and computers that scan books, periodicals and other written materials for the
purpose of finding possible cryptograms, code phrases and patterns that may be, in part or
in whole, a hidden or secret message or instruction.
The Technology Analysis Section evaluates the technologies and the technological
capability of the known and hostile worlds within the galaxy for the purpose of developing
countermeasures to such technology, to adopt such technology, or to recommend covert
operations to obtain such technology. The information obtained from such analyses may
be given to the Star Fleet Office of Intelligence Technology for their development or
given to other Federation intelligence agencies for their use.
The function of the Operations Simulation Section is to mathematically model specific

socio-political and military situations and to simulate them in order to analyze various
outcomes. The purpose of this is to evaluate possible conditions and responses to such
conditions by Star Fleet and the Federation. This section utilizes specially designed M-2
computers built by the Daystrom Institute that have a high degree of artificial
intelligence.
The Chief Star Fleet Intelligence Analyst is the senior officer in charge of this section
and is responsible for preparing the daily intelligence briefings. The Chief Star Fleet
Intelligence Analyst is an officer of the line (SFC) with the rank of Commodore.

VOLUME II
STAR FLEET OFFICE OF INTELLIGENCE PERSONNEL
The function of the Star Fleet Office of Intelligence Personnel (IPER) is to recruit
qualified personnel into the Star Fleet intelligence branch of the service. In addition, this
section is also responsible to train officers and operators on intelligence methods, and the
use of special equipment and weapons. The organizational structure for this office is
shown in Figure 2a14.4.
The function of the Intelligence Personnel Recruitment and Clearance Section is to

recruit new members into the organization. Members of this section will go out to the fleet
in search of experienced and qualified personnel, primarily for the Clandestine Service.
All prospective members will have an intensive background check performed on them by
the Star Fleet Investigative Service. This section will also travel to public Federation
colleges and universities for the purpose of recruiting analysts for the service. Primarily,
this section seeks sociologists, engineers, political scientists, language experts, historians,
psychologists, philologists, mathematicians, and any degreed person that may be useful to
the intelligence service.
The function of the Intelligence Personnel Training Section is to train intelligence

officers and operators on intelligence and espionage methods, and in the use of special
equipment and weapons. The Training Section is divided into two functions: 1) To train
the operators that work within the Clandestine Service, and 2) to indoctrinate the
civilian and administrative workforce in intelligence procedures and the handling of
classified material. The first training program is highly classified and will not be discussed
beyond this point. The civilian indoctrination program is non-classified and is designed
primarily to indoctrinate new hires in the procedures used by Star Fleet Intelligence. In
addition, this section will also provide refresher training, on a yearly basis, on such things
as the proper handling of classified material and to challenge individuals without proper
identification.
The Civilian Intelligence Personnel Section basically manages the civilian personnel
that work for Star Fleet Intelligence. Most of the civilians working for Star Fleet
Intelligence perform an administrative or clerical function. However, Star Fleet
Intelligence may also hire contract specialists to perform some of the analysis of
intelligence information. Individuals from this section may also assist Operations
Officers in the selection of civilian field operatives. Psychologists from this section may
also be employed at the behest of the Operations Officer to confirm the reliability and
stability of selected operators.
Intelligence Personnel Records Section maintains the records of all personnel within
Star Fleet Intelligence. As part of its function, this section will remove the names of
personnel within the Clandestine Service from all Federation databases in order to
conceal the identities of field agents and/or to establish new or counterfeit identities, while
maintaining the true identities of their agents. As such, his section has extraordinary
access to Federation personnel databases.
In charge of this section is the Star Fleet Intelligence Personnel Officer. This person
will be an officer of the line (SFC) and will typically have the rank of Captain. Typically,
this person will come from the ranks of the Clandestine Service, but with additional
training in personnel management.

VOLUME II
STAR FLEET OFFICE OF INTELLIGENCE COORDINATION
As a separate agency, ICOR serves as an independent source of analysis on topics of

interest, but will work closely with the Federation Intelligence Agency and other
organizations within the intelligence community to ensure that the intelligence consumer—
whether it is a Federation government policymaker or battlefield commander—receives
the best intelligence information possible. As such, the Star Fleet Office of Intelligence
Coordination (ISYN), shown in Figure 2a14.5, will handle the coordination of intelligence
information and techniques between the various Federation and the member government
intelligence agencies.
To aid in the coordination of intelligence across all the agencies an officer will be assigned
to each agency for this purpose and will act as the liaison between Star Fleet and the
agency. The office responsible for the coordination of intelligence between the various
Federation intelligence agencies is the Federation Intelligence Liaison Section, the
organizational structure of which is illustrated in Figure 2a14.6. This office manages all the
liaison officers assigned to the various intelligence agencies. An Intelligence Liaison
Officer is a line officer or officer of the Diplomatic Corps from Star Fleet Intelligence
who works with the Federation Intelligence Agency, as well as with the other member
system intelligence agencies, to coordinate intelligence activities. This officer is assigned to
work at the offices of the other intelligence organizations and as such, will be physically
located that these sites. There are only a handful of these liaison officers in ICOR and
they are chosen among the senior ranks of the Clandestine Service. All of these liaison
officers come under the direction of the Chief Federation Intelligence Liaison Officer.
The Intelligence Protocol Section develops the methods and procedures relating to the
coordination of intelligence activities between Star Fleet and the various Federation
intelligence agencies. In addition to establishing the procedures, this section will also
develop the standardized codes that will be used by intelligence operatives throughout the
Federation. All Federation and member government intelligence agencies are required
to follow these codes and procedures, which helps facilitate the coordination of intelligence
activities.
The Central Intelligence Databank is a large computer database of all data obtained
by Star Fleet Intelligence, as well as the information relating to the activities performed
by IOPS. This databank is shared with the databank that is kept by the Federation
Intelligence Agency and with the databanks of all the member system intelligence
agencies. This allows every intelligence agency to obtain the latest and best intelligence
information. However, not all information is shared with all of the external agencies. Some
of the operations that may be performed by Star Fleet must remain secret. This also
applies to the operations performed by the other intelligence agencies as well. The primary
function for database sharing is for data collection and not for operations.
The Star Fleet Intelligence Coordinator is an officer of the line (SFC) and will typically
have the rank of Captain. Typically, this officer will come from the ranks of the
Intelligence Liaisons.

VOLUME II
STAR FLEET OFFICE OF INTELLIGENCE TECHNOLOGY
To accomplish its mission, ICOR engages in research, development, and deployment of

high-leverage technology used exclusively for intelligence purposes. This intelligence
function belongs to the Star Fleet Office of Intelligence Technology or ITEK. The
function of this office is to research, develop, test and implement technologies and special
equipment used in tracking, surveillance and for other intelligence activities. To help in this
effort, this office will work with the Star Fleet Research and Development Command
(RAND), the Star Fleet Office of Science and Technology, the Technology Analysis
Section and any other agency in the development of the special equipment used by Star
Fleet Intelligence and its operators working in the field. The organizational structure for
this office is shown in Figure 2a14.7.
Within ITEK the Special Equipment Development Section is tasked with designing
and developing the high-leverage technologies used for intelligence purposes. Such
equipment is too highly classified to be described in this section. Suffice it to say, most of
the equipment developed by this section primarily deals with communications and
surveillance.
The function of the Special Weapons Section is to develop specialized weapons for field
operators such as those that can be transported undetected. This section will also analyze
and reverse-engineer weapons that were obtained or absconded during special operations.
The purpose of this is to understand the technology, be able to reproduce the technology
and to find ways to defeat the technology if it should be used against Federation forces.
As such, this section may also work with the Star Fleet Weapons Command in the
development of countermeasures against such weaponry.
The Special Equipment Issue Section maintains all the production equipment used by
the field operators. The equipment is stored in special security storerooms or vaults where
an operator can checkout and sign for equipment to be used in a mission. The equipment
will then be “checked” back in after use and the operator debriefed as to the usefulness of
the equipment. In addition, this section maintains an inventory of all such equipment and
will repair and test such equipment as necessary. It is this section that will usually make
the requests to the other sections for the development of specialized equipment.
The Intelligence Systems Support Section basically maintains the computer-based

intelligence systems. This section is composed primarily of computer and electronics
engineers, software developers and other specialists. Their primary function is to maintain
all of the intelligence system computers and electronics, software and databases. In
addition, this section will develop special computer applications required by Operations in
the performance of their duties. In addition, this section also maintains the Fleet
Intelligence Control System (FICS) used in the Star Fleet Intelligence Operations
Control Center. It is basically a large computer program and database that receives
[near] real-time field information for Operations to examine and evaluate actual and
simulated intelligence operations, along with their conditions and situations.
The Commander: Star Fleet Intelligence Technology (COMINTTEK) is the senior

officer in command of this office. The COMINTTEK will usually be an officer of the
Engineering Corps (ENG) and will typically have the rank of Commodore.

VOLUME II
SPECIAL INTELLIGENCE UNITS
Many commands within the Operating Forces and the Shore Establishment may have
units designated to perform intelligence functions. Most commands will have an
Intelligence Officer whose task it is to collect intelligence relevant to current command
operations. These officers will have access to the Intelligence Databank in order to
gather such information for the commander and will communicate with Star Fleet
Intelligence concerning any information that may be useful to the commander. These
officers are not Star Fleet Intelligence personnel, but command operations personnel
assigned to this duty. However, it is possible that Star Fleet Intelligence may assign
operators to commands for the purpose of performing special operations or to help
coordinate intelligence activities with the command.
Due to the sensitive nature of the assignments of these units, they will not be described in
any detail here. Chapter 9 will provide a more detailed explanation of the functions of
these units.

VOLUME II
Figure 2a14.1
STAR FLEET INTELLIGENCE
2400
Federation Intelligence Agency Star Fleet Intelligence
ICOR
Intelligence Office of Intelligence Office of Intelligence Office of Intelligence
IOPS Operations INAL Analysis IPER Personnel ICID Coordination
2450 Star Fleet Member System

Office of Intelligence Intelligence
ITEK Technology Agencies

VOLUME II
Figure 2a14.2
2410 Star Fleet

Intelligence
IOPS Operations
Clandestine Intelligence Intelligence Communications
IOPS Service IOPSPLN Operations Planning IOPSCEN Operations Center IOPSURV Surveillance
****
CLASSIFIED
****

VOLUME II
Figure 2a14.3
STAR FLEET OFFICE OF INTELLIGENCE ANALYSIS

Intelligence Office of Intelligence Office of Strategic &
IOPSPLN Operations Planning INAL Analysis TAC Tactical Operations
2421 Socio-Political 2422 Economic 2423 Military 2424 Psychological

Analysis Analysis Analysis Analysis
INAL Section INAL Section INAL Section INAL Section
2425 Codes, Ciphers and 2426 Pattern 2427 Technology 2428 Operations
Decipherment Analysis Analysis Simulation
INAL Section INAL Section INAL Section INAL Section

VOLUME II
Figure 2a14.4
STAR FLEET OFFICE OF INTELLIGENCE PERSONNEL

Office of Intelligence Bureau of
IPER Personnel BUPERS Personnel
2431 Intelligence Personnel 2432 2433 Civilian Intelligence 2434

Intelligence Personnel Foreign Assets
Recruitment and Personnel
Training Section Section
IPER Clearance Section IPER IPER Section IPER
2431A Intelligence Personnel 2435 Intelligence

Testing and Evaluation Personnel Records
IPER Section IPER Section
0323 Star Fleet

Central
BUMANPUB Records

VOLUME II
Figure 2a14.5
STAR FLEET OFFICE OF INTELLIGENCE COORDINATION
2440 Star Fleet

Office of Intelligence
ICID Coordination
2441 2442 Star Fleet 2443 Star Fleet

Federation
Intelligence Protocol Central Intelligence
Intelligence Liaisons
ICID ICID Section ICID Databank
Local Intelligence Liaison Offices

VOLUME II
Figure 2a14.6
FEDERATION INTELLIGENCE LIAISON SECTION
Intelligence Agency of
Intelligence Agency of Andor Federation Intelligence Agency
Alpha Centauri
9700 Star Fleet 2441 0820 Star Fleet

Federation
Investigative Bureau of
Intelligence Liaisons
SFIS Service ICID SFBI Investigation
Intelligence Agency of
Intelligence Agency of Rigel Intelligence Agency of Tellar
Earth-Mars

VOLUME II
Figure 2a14.7
STAR FLEET OFFICE OF INTELLIGENCE TECHNOLOGY
5200 Star Fleet Office of 2450 Star Fleet 3600 Star Fleet Research
Science and Office of Intelligence and Development
SCITEK Technology ITEK Technology RAND Command
2451 Special Equipment 2452 2453 Special Equipment 2454 Intelligence

Special Weapons
Development Issue Systems Support
Section
ITEK Section ITEK ITEK Section ITEK Section

VOLUME II

VOLUME II
1.5 STAR FLEET SPACE EXPLORATION

COMMAND
The function of the Star Fleet Space Exploration Command (XCOM) is to manage the
operations, assets and personnel concerned with the exploration of space by Star Fleet
forces. This “Type Command”, created under ARTICLE 6 of the Star Fleet Charter, is
tasked with assembling the vessels, equipment and personnel into the units and teams
required to accomplish its exploration mission. As such, all Star Fleet survey, exploration
and scientific vessels will come under direct authority of the Exploration Command.
Although it may appear on the surface that XCOM would conflict with the Star Fleet
Bureau of Federation Space Exploration (BUEXPLOR), it does not. XCOM only
manages the personnel and assets engaged in exploration missions carried out by Star
Fleet; whereas BUEXPLOR manages the Federation civilian and commercial exploration
enterprises. And although BUEXPLOR is responsible for and in charge of all survey and
mapping activities within Federation space, it is XCOM that determines what Star Fleet
forces and assets will be needed to perform these activities within Federation space. As
such, XCOM will work with BUEXPLOR in determining the areas of Federation space
that require exploration. However, it is XCOM that is wholly responsible for exploration
outside Federation space.
The Commander: Space Exploration (COMFLTEXP) is the senior officer in command

of XCOM, and of all activities regarding space exploration operations and missions by Star
Fleet, and in the assignment of Star Fleet exploration vessels and personnel. The
COMFLTEXP is an officer of the line (SFC), and will typically have the rank of Rear
Admiral. The COMFLTEXP reports directly to the Chief of Star Fleet Operations
regarding all exploration and survey activities performed by Star Fleet.
RESPONSIBILITY
The Star Fleet Space Exploration Command is basically responsible for all the aspects
relating to the exploration and colonization activities performed by Star Fleet in fulfillment
of its duties under ARTICLES 19 and 20 of the Star Fleet Charter. That is, XCOM is
responsible for surveying and exploring new areas of space for incorporation into the
Federation; expanding current Federation boundaries; colonizing Federation space by
establishing military and scientific outposts; and to seek out new life forms and civilizations
that could be an asset to the Federation as members of the same.
In addition, the Space Exploration Command is also responsible to ensure that all its
personnel are properly trained and qualified to perform the exploration duties to which
they are assigned, and are fully aware of all Star Fleet and Federation regulations and
procedures regarding space exploration and contact with new life forms.
Finally, XCOM is accountable to ensure that its exploration teams are provided with all the
equipment and supplies necessary to fulfill their exploration and contact missions, and that
they are always supplied with all the provisions necessary to sustain their exploration and
survey efforts.

VOLUME II
SPACE EXPLORATION COMMAND SYMBOL[4]
The symbol for the Space Exploration Command is a derivative of the Star Fleet
arrowhead. The symbol consists of an angular and sharp diagonal red arrowhead placed
through a blue ring, which symbolizes the passage through space. The arrowhead is seen
moving through space and pointing to new areas of space indicating exploration. This
symbol is displayed on all exploration and survey vessels, and on all XCOM documents
and manuals.
Illustration 2a15.1
SPACE EXPLORATION
COMMAND SYMBOL
The division is divided into four offices for the delegation of its responsibilities as illustrated
• Star Fleet Office of Exploration Planning

• Star Fleet Office of Exploration Operations
• Star Fleet Office of Exploration Materiel
• Star Fleet Space Exploration Vessel Command

VOLUME II
STAR FLEET OFFICE OF EXPLORATION PLANNING
Within the Exploration Command is the Star Fleet Office of Exploration Planning
(XCOMPLAN), the function of which is to determine and plan the areas of space that will
require exploration. Primarily these areas of space are usually outside the boundaries of
the Federation, but may also include regions within Federation territory as well. Once
these regions of space designated for exploration have been determined, this office will
develop the program for the exploration effort. This effort could be in the form of a full-
scale expedition or as a simple survey mission assigned to the Operating Forces. Figure
2a15.2 presents the organizational structure for this office.
Within XCOMPLAN the Space Mapping and Surveying Section manages the space
mapping and surveying activities performed by Star Fleet. This section selects the areas
of space that will require surveying by Star Fleet survey vessels or by the Operating
Forces, and will develop the Mission Profiles required to perform such survey and
mapping activities that will be carried out by Star Ship Command. The data obtained
from such survey activities will be handed over to the Star Fleet Office of Maps and
Charts, which creates the charts and galactic maps used throughout the Federation. In
addition, the survey data will also be given to the Star Fleet Bureau of Federation
Space Navigation to aid that agency in their surveys and to update the charts relating to
any navigational hazards that were encountered during the survey.
The primary function of the Exploration Plans and Strategies Section is to work with
the Star Fleet Bureau of Federation Space Exploration (BUEXPLOR) in planning the
short and long-term exploration missions that will be performed by Star Fleet. In this
way, space exploration can be divided between the civilian authority and Star Fleet.
Where it is expected that a new alien race may possibly be found in a particular area of
unexplored space, the task of exploring and surveying these areas will be given to Star
Fleet. The commercial and private exploration licensed by BUEXPLOR will generally be
limited to areas of space where it is anticipated that new civilizations or alien races would
not be present.
Within XCOMPLAN the Expedition Logistics Planning Section is responsible for

developing the logistical plans for survey and exploration missions by determining the
types and amount of equipment that will be needed to complete each mission. Such plans
include the amounts and types of supplies, food and other essentials that will be required
by the team. In addition, this section will also determine if permanent or temporary
structures will be necessary at the exploration site, as well as the size and numbers of
such structures. If so required, this section will provide the Star Fleet Office of
Exploration Operations with the requirements for such structures, and will also work
with the Star Fleet Corps of Engineers and the Star Fleet Construction Command
concerning the requirements for such structures.

VOLUME II
STAR FLEET OFFICE OF EXPLORATION OPERATIONS
The Star Fleet Office of Exploration Operations (XCOMOPS) is the organization

within the Star Fleet Space Exploration Command that manages all Star Fleet
expeditions and exploration missions. This office is responsible for selecting the teams and
determining the personnel composition for all exploration missions. This office was given
the authority, under ARTICLE 6 of the Star Fleet Charter, to develop and direct all Star
Fleet exploration and survey missions, which includes all scientific and other such missions
and therefore, is responsible for the overall management of such missions and expeditions.
In addition, this office will develop the procedures used during the initial contact of new
life forms and civilizations, and is responsible for training all Star Fleet personnel in first
contact procedures. The organizational structure of this office is shown in Figure 2a15.3.
Within XCOMOPS, the Exploration Mission Development Section develops or creates

the Mission Profiles for any exploration mission undertaken by XCOM teams or by the
Operating Forces in the course of their patrol duties. As such, this section will develop
the mission requirements, guidelines and rules of engagement that may be applied when
any new civilization is encountered by Star Fleet Contact Teams. In addition, this office
will work with Star Ship Command in developing any procedures that may be used when
contacting new life forms by Starship crewmembers during the normal course of their
patrol duties or during a specialized exploration mission.
The Exploration Personnel Section essentially manages the personnel engaged in the
expeditions undertaken by XCOM. That is, this section will select and assign personnel to
exploration and survey teams, and will set up the leadership structure of such teams.
However, this authority only applies to those specific missions that are under the control of
XCOM and does not extend to exploration and survey missions performed by units of the
Operating Forces. That is, the assignment of personnel to specific exploration missions
initiated by an operating unit is the sole prerogative of the Commanding Officer of that
unit.
The primary function of the Expedition Management and Control Section is to direct
and monitor the special expeditions and survey missions prepared by Star Fleet from
initiation to completion. This includes monitoring all of the exploration and survey vessels
assigned to such missions, as well as, the expeditions placed on newly discovered planets
and worlds. As part of this responsibility, this section will schedule periodic calls to such
expeditions to review their progress, and will require from such expeditions status reports
on their progress and findings. When the mission has been completed, this section will
process any results obtained by the exploration and survey team, and will publish and
present them to higher authority. This section, however, has no authority over the general
survey or exploration activities performed by the Operating Forces.
The primary function of the Expedition Engineering Section within XCOMOPS is to

design and construct the temporary and permanent structures that may be utilized at
expedition sites. This work not only includes the design of the structures themselves, but
any supporting system that may be required as well. As such, this section will coordinate
with the Star Fleet Corps of Engineers and the Star Fleet Construction Command
regarding the design and construction of any facility required at the expedition site, as well
as any infrastructure needed to support the site.

VOLUME II
STAR FLEET OFFICE OF EXPLORATION MATERIEL
The Star Fleet Office of Exploration Materiel (XCOMSUP) is responsible for the
logistical support of all exploration and survey missions. Although the Expedition
Planning and Logistics Section develops the logistical requirements of an expedition,
this office is responsible for allocating or procuring the necessary supplies from the Star
Fleet Supply Command. In addition, this office also has the responsibility of monitoring
the consumption of supplies used during any mission as mandatory under Star Fleet
Regulation 8791. As such, this office will determine the maintenance needs of any
XCOM expedition and will make arrangements with the Star Fleet Transportation
Command to make periodic supply runs to such expeditions. Figure 2a15.4 presents the
The Exploration Procurement Section within XCOMSUP will perform the actual
allocation and procurement of supplies and equipment to Star Fleet expeditions. As such,
this section will work with the Star Fleet Supply Command in acquiring the necessary
materials and supplies. In addition to procuring the supplies and equipment needed for
specific expeditions, this section will also allocate the standard equipment needed by any
expedition, with the exception of survey vessels and other space craft. Such standard
equipment include Tricorders and other recording, surveillance or analysis devices,
Universal Translators, portable shelters, portable food processing units and power
supplies.
The function of the Exploration Equipment and Storage Section is to store and
maintain the basic hardware and material used on any Star Fleet expedition. This section
possesses several storage and warehouse facilities where such equipment is located. As
such, this section is responsible for the storage and inventory of all equipment used by the
Star Fleet Space Exploration Command. Storage of equipment also involves the
maintenance and repair of the equipment as well. As such, these storage and warehouse
facilities also contain shops for the repair and upkeep of exploration equipment.
Within XCOMSUP the Expedition Supply and Replenishment Section is primarily

responsible for keeping the expeditions and survey teams supplied with food, parts and
other necessities. As part of its responsibility, this section will schedule supply runs with
the Star Fleet Transportation Command to the long-term expeditions that are
currently in progress. Most of the supply runs have been planned and scheduled in
advance, but in the event that emergency or ad hoc replenishment is required, it is the
responsibility of this section to ensure that such expeditions receive the needed food, parts
and the necessary materiel in order to sustain the operation.

VOLUME II
STAR FLEET SPACE EXPLORATION VESSEL COMMAND
The Star Fleet Space Exploration Vessel Command (ESHIPS) manages all the
exploration and survey vessels assigned to such missions. This office is primarily concerned
with the Survey / Exploration (SV) vessels of the Explorer class (NCC-632) and the
Laboratory (SL) vessels of the Lehrner class (NCC-1371). As such, this office will work
with Star Ship Command in the selection and assignment of these vessels to Star Fleet
expeditions. The organizational structure of this office is shown in Figure 2a15.5.
The Exploration Vessel Requirements Section within ESHIPS essentially establishes

the requirements for survey and exploration vessels in terms of their numbers, sizes and
capabilities. The requirements are then submitted to the Star Ship Systems Command
(STARSHIPS) for the procurement or construction of these specialized vessels.
The primary function of the Exploration Vessel Maintenance Section is to maintain

the fleet of exploration and survey vessels that may be used for such missions. As such,
this section is responsible for keeping the exploration fleet in a high state of readiness for
such service. The survey and exploration ships under control of this section are located at
a station maintained by the Star Fleet Bureau of Docks and Yards (BUDOCKS).
Table 2a15.1
LIST OF STAR FLEET EXPLORATION AND SURVEY VESSELS
Registry Commissioned
Primary Function
(NCC) Name
632 U.S.S. EXPLORER Space exploration
635 U.S.S. DISCOVERY Base and station evaluation
636 U.S.S. SURVEYOR Planetary survey vessel
637 U.S.S. MAGELLAN Space exploration
638 U.S.S. GRISSOM Space survey and mapping
639 U.S.S. STARGAZER Space exploration
641 U.S.S. ARMSTRONG Base and station evaluation
642 U.S.S. VOYAGER Space exploration
643 U.S.S. CARPENTER Planetary survey vessel
647 U.S.S. HORIZON Planetary survey vessel
648 U.S.S. SEARCHER Space survey and mapping
649 U.S.S. ERICSON Space survey and mapping
651 U.S.S. MARCO POLO Planetary survey vessel
652 U.S.S. SHEPARD Colonization vessel
1371 U.S.S. LEHRNER Fleet scientific duty
1372 U.S.S. INFINITY Scientific study of gravitational fields
1373 U.S.S. ABELIAN Fleet scientific duty
1374 U.S.S. OBSERVATORY Space structure studies
1375 U.S.S. GALAXY Scientific study of solar phenomenon
1376 U.S.S. CURIOSITY Fleet scientific duty
1377 U.S.S. DEDUCTION Fleet scientific duty
1378 U.S.S. INTUITION Fleet scientific duty
1379 U.S.S. ARCHIMEDES Planetary survey duty
1380 U.S.S. EDDINGTON Scientific study of solar phenomenon
1381 U.S.S. FARADAY Fleet scientific duty

VOLUME II
ORGANIZATION CHARTS
The subsequent page presents the organizational chart for the Star Fleet Space
Exploration Command. The title block for each section within the division contains the
name of the office, the division number and the Office Designator. The Office Designation
is a shorthand version of the division name.
2500 Star Fleet

Space Exploration
XCOM Command
Office Designator

VOLUME II

VOLUME II
Figure 2a15.1
STAR FLEET SPACE EXPLORATION COMMAND

Bureau of Federation Space Exploration
BUEXPLOR Space Exploration XCOM Command
2510 Star Fleet Office of 2520 Star Fleet 2530 Star Fleet 2540 Star Fleet
Exploration Office of Office of Space Exploration
XCOMPLAN Planning XCOMOPS Exploration Operations XCOMSUP Exploration Materiel ESHIPS Vessel Command
3900 Star Fleet 7100 Star Fleet 2100

Construction Supply Star Ship Command
CONST Command SUPCOM Command SSC

VOLUME II
Figure 2a15.2
STAR FLEET OFFICE OF EXPLORATION PLANNING

Bureau of Federation Office of Exploration
BUEXPLOR Space Exploration XCOMPLAN Planning
2511 Space Mapping 2512 Exploration 2513 Expedition

and Surveying Strategic Planning Logistics Planning
XCOMPLAN Section XCOMPLAN Section XCOMPLAN Section

VOLUME II
Figure 2a15.3
STAR FLEET OFFICE OF EXPLORATION OPERATIONS
2520 Star Fleet

Office of Exploration
XCOMOPS Operations
2521 Exploration 2522 Exploration 2523 Expedition 2524 Expedition

Mission Development Personnel Management and Engineering
XCOMOPS Section XCOMOPS Section XCOMOPS Control Section XCOMOPS Section
2100 3900 Star Fleet

Star Ship Command Construction
SSC CONST Command

VOLUME II
Figure 2a15.4
STAR FLEET OFFICE OF EXPLORATION MATERIEL
2530 Star Fleet

Office of Exploration
XCOMSUP Materiel
2531 Exploration 2532 Exploration 2533 Expedition

Procurement Equipment and Storage Supply and
XCOMSUP Section XCOMSUP Section XCOMSUP Replenishment Section

Supply Transportation
SUPCOM Command TRANSCOM Command

VOLUME II
Figure 2a15.5
STAR FLEET SPACE EXPLORATION VESSEL COMMAND
2540 Star Fleet

Space Exploration
ESHIPS Vessel Command

Exploration Vessel Exploration Vessel
ESHIPS Requirements Section ESHIPS Maintenance Section
3300 Star Ship 3910 Star Fleet

Systems Bureau of
STARSHIPS Command BUDOCKS Docks and Yards

VOLUME II

VOLUME II
1.6 STAR FLEET OPERATIONS OFFICES

As previously mentioned, Star Fleet Operations is comprised of five Type Commands
and three administrative support offices. The five Type Commands were described in the
previous five sections of this chapter. This section will discuss the remaining three
administrative offices responsible for supporting Star Fleet operations, which are:
 The Star Fleet Office of Fleet Logistics

 The Star Fleet Office of Fleet Communications
 The Star Fleet Office of Strategic and Tactical Operations
Their primary function is to support and maintain the fleet in a high state of readiness for
any operation they may be required to perform. These offices report directly to the
Operations Chief of Staff (OPSOS). The subsequent paragraphs will describe the
functions of each of the above offices, and the organization charts for each of these offices
are contained in Figures 2a16.1 to 2a16.3.

VOLUME II
STAR FLEET OFFICE OF FLEET LOGISTICS
The Star Fleet Office of Fleet Logistics (FLTSUP) is the organization responsible for
keeping the Operating Forces and Shore Establishments supplied with the materials
needed to effectively operate and fulfill their missions. Within FLTSUP are the various
offices and sections devoted to the logistical support of the fleet as illustrated in Figure
2a16.1, each of which will be described in the following paragraphs.
The Star Fleet Logistical Planning Section is responsible for ascertaining the overall
material needs of the Operating Forces and Shore Establishment. This office will
perform the long-range plans for the material requirements of the fleet based upon the
inputs from Star Ship Command, Star Base Command, the adjunct forces and the
other Type Commands within the division. This office will then combine the requirements
of all of these commands into a single logistical plan, which will be used as a basis for
developing the budgets for the Operating Forces, the Shore Establishments and the
Fleet Marine Corps.
The Star Fleet Logistical Supply Section allocates the material resources and
equipment needed to supply the Operating Forces and Shore Establishments. This
office will work with the Star Fleet Supply Command in allocating the equipment and
supplies necessary to keep the fleet operating efficiently, and with the Star Fleet
Transportation Command for the transportation of these supplies to the operating
commands. In addition, this office is responsible for keeping the fleet stores and
warehouses supplied with tools, fuel, food, equipment and spare parts. Such stores are
located throughout the various System Bases located on member worlds.
The Logistical Supply Section is also responsible for maintaining the various supply
depots and fleet stores used by the Operating Forces which are located throughout the
Federation. As such, this office has the authority to determine the location of such supply
depots and stores. Where a fleet store or supply depot is needed, this office will work with
the Star Fleet Corps of Engineers and the Star Fleet Construction Command in the
building of such stores and depots.
The Star Fleet Logistical Operations Section is responsible for getting the supplies
and equipment to the Operating Forces and Shore Establishments. This office will
work with the Star Fleet Transportation Command in scheduling the replenishments
of Star Fleet ships, bases and stations. This office will then direct the Transportation
Command to make their supply runs to the various bases and stations, and to rendezvous
with the ships and stations that operate out in deep space.
The Logistical Operations Section is also responsible for training command Supply
Officers in the management and handling of fleet supplies, and in establishing the
standards and procedures regarding the management, accounting, handling and storage of
fleet supplies. This office will assign Supply Officers to fleet supply depots and stores
jointly with the Star Fleet Bureau of Personnel.
The Commander: Fleet Logistics (COMFLTSUP) is the senior officer in command of all
activities regarding the supply and replenishment of the Operating Forces and Shore
Establishment of Star Fleet. The COMFLTSUP will usually be an officer of the Supply
Corps (SUP) and will typically have the rank of Rear Admiral.

VOLUME II
STAR FLEET OFFICE OF FLEET COMMUNICATIONS
The Star Fleet Office of Fleet Communications (FLTCOMM) is the central command
responsible for communicating with the Operating Forces and Shore Establishments
regarding the missions and operations to which they are assigned. In addition, this office is
responsible for keeping the forces informed on galactic conditions and current events
within the Federation, and to keep force commanders informed on current military and
political conditions throughout the galaxy. As a secondary function, this office is also
responsible for keeping the forces connected with friends and family through private
communications. FLTCOMM contains various offices and sections devoted to fleet
communications as illustrated in Figure 2a16.2, each of which will be described below.
Within FLTCOMM is the Star Fleet Communications Standards Section. The function
of this section is to establish the communications frequencies and channels used by Star
Fleet. As such, this office will work with the Star Fleet Office of Technology
Standards and with other Federation agencies in setting the proprietary Star Fleet
frequencies, the emergency communications channels and the civilian communications
channels, as well as establishing the regulations (FLTCOMMREGS) governing the use of
these channels. As part of its function, this office will monitor all communications channels
for compliance with these and other Federation regulations.
The function of the Star Fleet Communications Equipment Section is to provide the
fleet with the proper communications equipment. In addition, this office is also responsible
for maintaining all the ground communications apparatus and networks that are distributed
throughout the Federation, which includes all communications stations and subspace
relay units. This office is also responsible for standardizing the communications equipment
used by the fleet, and is responsible for developing and managing all Star Fleet hand-
held communications devices. Finally, this section is tasked with developing sensor and
communications jamming and disruption equipment for use during wartime.
The Star Fleet Communications Operations Section (COMMOPS) is responsible for

all communications sent to and received from the Operating Forces and Shore
Establishments. In addition, this section determines the communications channels the
fleet will use; determines and creates the message packages; decides what codes and
ciphers will be used; and will send special communications packages that will automatically
change the cipher codes within a command’s computer. This office will also send any
galactic-wide alert codes to the fleet, general fleet communiqués, and handle all personal
communications. During wartime, this section will also control all private communications
and endeavor to disrupt enemy communications through the use of remote stations.
Lastly, this office has the responsibility to select the location of any communications relay
stations, and to design and maintain the Star Fleet Communications Network.
FLTCOMM also has a special Star Fleet Cryptographic Section whose function it is to
code and decode Star Fleet messages. As such, this section manages and maintains the
cryptographic machinery used to code and decode Star Fleet messages, and therefore,
develops the ciphers and coding methods used in secure communications. This office will
also work with Star Fleet Intelligence in decoding foreign communications as well. Only
persons with TOP SECRET clearance can work within this section.
The Commander: Fleet Communications (COMFLTCOMM) is the senior officer in

command of all activities regarding fleet communications. The COMFLTCOMM is a flag
officer of the line (SSC) with the rank of Rear Admiral.

VOLUME II
STAR FLEET OFFICE OF STRATEGIC AND TACTICAL

OPERATIONS
The function of the Star Fleet Office of Strategic and Tactical Operations (TAC) is
to develop the combat strategies and tactics that will be employed by the Operating
Forces. In the development of such strategies and tactics, this office will work closely with
Star Fleet Intelligence in the development of combat strategies and tactics. As such,
Star Fleet Intelligence will supply this office with any intelligence data concerning the
strategies and tactics employed by foreign powers, or with any material obtained through
clandestine operations. Within TAC are the various sections responsible for developing the
strategies and tactics used by Star Fleet as illustrated in Figure 2a16.3 and are discussed
in the following paragraphs.
The office responsible for developing the strategies and tactics used by Star Fleet is the
Star Fleet Strategies and Tactics Development Section. This section is responsible
for developing the methods and procedures for all military operations employed by the
Operating Forces and the Shore Establishment, which includes developing peacetime,
as well as wartime strategies. The strategies and tactics developed by this office will be
translated into methods and procedures that will be employed by the field commanders in
the execution of their missions.
TAC also contains the Star Fleet Tactical Simulation Section that tests the theories,
procedures and tactics developed by the Strategies and Tactics Development
Section. To accomplish its analyses this section utilizes specialized computers designed to
simulate the actions during combat and other situations. In addition, this section will
develop the combat simulation models and scenarios that will be used by the Office of
Star Fleet Training Simulators within the Star Fleet Training Command.
The function of the Star Fleet Strategy and Tactics Training Section is to train
commanders and personnel on Star Fleet strategies and tactics. Most of this type of
training occurs within the classroom, but hands-on training is also available through the
use of Star Fleet Training Command simulators and through operational maneuvers
carried out by actual fleet assets that were designed by this section. Thus, commanders
and personnel can exercise the tactical maneuvers learned from the classroom training.
The Star Fleet Alien Tactics Section within TAC was created to analyze the combat
tactics employed by foreign or alien forces. Tactical information is obtained by field
commanders in their encounters with alien forces, as well as from intelligence activities.
This information is then analyzed and methods developed to counter or make ineffectual
the tactics employed by potential hostile forces.
Finally, this office also contains the Star Fleet Tactical Command or TACOM, which is
responsible for developing and executing all the tactical operations assigned to Star Fleet
by the Federation Council or the Military Staff Committee. A more detailed
discussion regarding the function of TACOM can be found in Section 5.2 of this volume.
The Commander: Tactical Operations (COMTAC) is the senior officer in charge of

establishing, creating and maintaining all strategic and tactical operations for the
Operating Forces of Star Fleet. The COMTAC will be an officer of the line (SFC) and
will typically have a rank of Rear Admiral.

VOLUME II
ORGANIZATION CHARTS
The subsequent page presents the organizational charts for the supporting offices with
Star Fleet Operations. The title block for each section within the division contains the
name of the office, the division number and the Office Designator. The Office Designation
is a shorthand version of the division name.
2600 Star Fleet

Office of
FLTSUP Fleet Logistics
Office Designator

VOLUME II

VOLUME II
Figure 2a16.1
STAR FLEET OFFICE OF FLEET LOGISTICS
2600 Star Fleet

Office of
FLTSUP Fleet Logistics

Logistical Planning Logistical Supply Logistical Operations
FLTSUPPLAN Section FLTSUP Section FLTSUPOPS Section

Supply Transportation
SUPCOM Command TRANSCOM Command
2130 Office of
Star Fleet Ship
SSCMAT Materiel
2230 Office of
Star Fleet Base
SBCMAT Materiel

VOLUME II
Figure 2a16.2
2700 Star Fleet

Office of
FLTCOMM Fleet Communications
Communications Communications Communications Cryptographic
COMMREG Standards Section FLTCOMM Equipment Section COMMOPS Operations Section CRYPTO Section
2400
ICOR

VOLUME II
Figure 2a16.3
STAR FLEET OFFICE OF STRATEGIC AND TACTICAL OPERATIONS
2400 2800 Star Fleet

Star Fleet Intelligence Office of Strategic &
ICOR TAC Tactical Operations
Strategies and Tactics Tactical Simulation Strategy and Tactics Alien Tactics
TACDEV Development Section TACSIM Section TACTRAIN Training Section TAC Section
2850
Federation Strategic Command Star Fleet
(STRATCOM) Tactical Command
TACOM

VOLUME II

VOLUME II
1.7 STAR FLEET OPERATING FORCES

In this section the Operating Forces of Star Fleet will be discussed. In this context the
term “operating forces” will refer to both the Operating Forces and the Shore
Establishments of Star Fleet, which will fundamentally be defined as all the ships,
vessels, bases, stations, troops, and all other assets used to maintain peace and security
within the Federation. In order to effectively maintain the peace and security of the
Federation, the Operating Forces of Star Fleet is divided into nine command units, all
of which are managed by Star Fleet Operations as illustrated in Figure 2a17.1.
SECTOR COMMANDS
Sector Commands refer to the command organization associated with Federation

octants and sectors, which includes all the bases, stations and outposts within these areas.
In general, Sector Commands are basically connected with the Shore Establishment.
At the top of any Sector Command is the Sector Commandant, a command position
established by the Star Fleet Charter and codified in Star Fleet Regulation 3400.
The primary function of a Sector Command, as illustrated in Figure 2a17.2, is to manage

and support the fleet within their jurisdiction. In essence, Sector Commands are the
extended arm of Star Fleet Command and as such, all orders and directives issued by
these commands are to be considered as coming from the central authority. As such,
Sector Commands will be the local source of instructions to the Operating Forces and
in providing support to the fleet. In keeping with this role, Sector Commands will also be
the primary means from which the Operating Forces can maintain their high degree of
readiness by replenishing and refurbishing the fleet.
FLEET COMMANDS
Fleet Commands generally refer to the Operating Forces within an octant or sector.
Fleet Commands are divided into two distinct categories: ships and ground forces, both
of which constitute the Operating Forces of Star Fleet within the region. Therefore,
when the term “the fleet” is used it refers to all of the mobile forces and not merely ships.
As such, it means the command structure associated with mobile troops and assets, with
the exception of the specialized assets belonging to the Star Fleet Transportation
Command and Star Fleet Intelligence.
The primary mission of Fleet Commands is to carry out Federation policy and to carry
out the basic functions to which Star Fleet was chartered, which will be accomplished
through the use of the Operating Forces and other assets at the disposal of such
commands; assets being defined as the ships, troops and other specialized assets within
the Star Fleet.
In general, Star Fleet ships constitute the bulk of the Operating Forces. They operate
at the fringes of Federation space and are the first line of defense against aggressive
forces from outside the territory. At the top level of this command structure is the Fleet
Commander, a command position established by ARTICLE 62 of the Star Fleet Charter
and whose authority is specified in Star Fleet Regulation 5710. The basic organizational
structure for a typical Fleet Command is illustrated in Figure 2a17.3.

VOLUME II
STAR FLEET GROUND FORCES
The Operating Forces of Star Fleet also includes the Star Fleet Marine Corps, which
are the ground forces of Star Fleet. Where ground fighting is required, it will be the Fleet
Marine Corps’ responsibility to execute such missions.
The Star Fleet Marine Corps is that branch of the Operating Forces developed to
furnish power projection from space, utilizing the mobility of the Star Fleet to rapidly
deliver combined-arms task forces to galactic crises. The Marine Corps serves as the
primary landing force in readiness, and has three primary areas of responsibility:
1. The seizure or defense of advanced bases and other land operations to support Star
Fleet campaigns,
2. The development of tactics, techniques, and equipment used by landing forces, and
3. Such other duties as the Director: Star Fleet Command, the Military Staff
Committee or the Federation Council President may direct.
In command of all the ground forces within a Federation octant is the Commander:
Fleet Marine Forces or COMFOR. The COMFOR is the operational head of the Corps
within the octant and is responsible to train and equip the Fleet Marine Corps within the
octant. During war or conflict, the COMFOR will serve as the direct battlefield commander
for the area, and will share co-equal command with the Fleet Commander assigned to
that octant. In any action where ground forces will be required, the COMFOR and the
Fleet Commander will work together to plan the operation. Otherwise, during peacetime,
each is separately in command of their respective units. The basic organizational structure
for the ground forces of the Star Fleet is illustrated in Figure 2a17.4.
SPECIAL FORCES
The Star Fleet Marine Corps also contains a special force created to perform clandestine
military operations, and who are trained to conduct missions of unconventional warfare
and reconnaissance. Special Forces are the elite ground units highly trained in close-
quarter combat, insurgency and counter-insurgency, rescue and deep penetration
missions. They are often deployed in small groups armed and supplied with specialized
equipment, and operate under the principles of self-sufficiency, stealth, speed and close
teamwork. Much of their work is TOP SECRET and will not be discussed here. However, a
more detailed treatment of such units may be found in Section 9.1 of this volume.
The selection process for a special operations unit is typically extremely rigorous, with
training often exceeding two years. Certain missions may require additional training. As the
work of special operations forces is often performed covertly and involves classified
information, candidates are put through extensive trials prior to acceptance, which have
extremely high attrition rates. In addition, candidates must also possess a TOP SECRET
security clearance, and may work with Star Fleet Intelligence and other intelligence
agencies and operatives on a regular basis, facilitating rapid action in response to current
intelligence. Special Forces operators may also be used to train foreign forces when
military aid is given to other planetary systems, so that much of their specialized training
includes language and cultural skills. Due to the secrecy surrounding much of their training
and work, special operations forces have a mystique and aura of mystery about them.

VOLUME II
Figure 2a17.1
STAR FLEET SECTOR COMMANDS
2000 Star Fleet

Division of
SFOPS Operations
2910 2920 2930 2940

Commandant: Commandant: Commandant: Commandant:
Federation Sector 1 Federation Sector 2 Federation Sector 3 Federation Sector 4
COMSEC 1 COMSEC 2 COMSEC 3 COMSEC 4
2950 2960 2970 2980

Commandant: Commandant: Commandant: Commandant:
Federation Sector 5 Federation Sector 6 Federation Sector 7 Federation Sector 8
COMSEC 5 COMSEC 6 COMSEC 7 COMSEC 8
2900
Commandant:
Federation Treaty Zone
COMSEC 0

VOLUME II
Figure 2a17.2
BASIC SECTOR COMMAND
29X0 Federation Sector

Command
COMSEC
29X0-N000 29X1 29X2 29X3

Fleet Fleet Marine Sector Base
Command Command Administration Command
COMFLT COMFOR SECADM SECBAS

VOLUME II
Figure 2a17.3
BASIC FLEET COMMAND
29X0 Fleet
Command
COMFLT
29X0-G 29X0-F 29X0-S 29X0-A

Group Fleet Squadron Fleet Support Attack Craft Group
Command Command Command Command
FLTGRP FLTSQ FLTSUP FLTAT

VOLUME II
Figure 2a17.4
BASIC GROUND FORCE COMMAND
29X1 Fleet Marine

Command
COMFOR
29X1-F 29X1-G 29X1-S 29X1-A

Marine Division Ground Force Force Support Attack Craft Group
Commands Commands Command Command
FOR FOR FORSUP FORAT
29X1-X
Special Forces
SPECFOR

VOLUME II
1.8 STAR FLEET OPERATIONS CENTER

The Star Fleet Operations Center, also known simply as the Operations Center, is
the central command and control site for all Star Fleet operations. It is the nerve center
for the entire Star Fleet and is physically located at the very center of the upper dome
area of Star Base Central. This is also the site where the Federation Joint Chiefs of
Staff will meet to plan and manage joint operations with all Federation forces should
they become necessary. In addition, the Operations Center contains all the offices and
commands within the Operations Division and along with them, the offices for all the
division chiefs of Star Fleet Operations. In charge of the Operations Center is the
Operations Center Commander, a line office with the rank of Captain.
The Operations Center is manned around the clock by personnel working in three eight-
hour shifts. The center is normally manned by personnel from Star Ship Command, the
Star Fleet Office of Strategic and Tactical Operations and the Star Fleet Office of
Fleet Communications. However, in addition to Star Ship Command personnel, this
center may also be manned by Star Base Command personnel as well. Their function
will be to relay the operational plans, developed at the center, to the Star Fleet bases
that will be engaged in the operation at hand.
The maintenance of the Operations Center is the responsibility of the Star Fleet Office
of Fleet Communications (FLTCOMM). FLTCOMM is responsible to ensure that all the
equipment functions properly and will execute repairs if necessary. The duty officer in
charge of the center is the Operations Center Duty Officer (CDO), whose responsibility
it is to manage the facility (see Figure 2a18.1). The CDO is normally an officer assigned
from FLTCOMM, but may come from any other office within Star Fleet Operations. This
is a rotational assignment and a new CDO is picked each month. The CDO’s primary
function is to keep the center operating at peak efficiency. This basically means that the
CDO is responsible for all the equipment and displays in the center.
The original design and construction of the complex was performed by Star Fleet
Engineering. As such, any upgrades to the systems at the facility will be performed by
Star Fleet Engineering. Maintenance of the center is the responsibility of base
engineering.
STAR FLEET MISSION CONTROL CENTER
The Star Fleet Mission Control Center is the central part of the Operations Center
that monitors all the activities of the Operating Forces. Physically, the center is a large
circular area surrounded by viewers and control panels. In the middle of this area is a
large domed holographic display of Federation space. Here also sits the Operations
Commander (OPC) as well as his assistants. This is not a permanent title, but an
assignment given to the person within Star Fleet Operations that was assigned a
specific operation. The OPC will typically come from Star Ship Command, but may also
come from the Star Fleet Adjunct Forces Command in the case of joint force
operations. The function of the Operations Commander is to oversee all aspects of an
operation and to provide the Operational Commanders in the field with the tools vital
for them to make real-time operational decisions. However, the OPC is not an
Operational Commander, but supports the commander regarding his operation.

VOLUME II
OFFICES AND AREAS
The Operations Center contains all the major offices of Star Fleet Operations. The
reason the Operations Center was arranged in this manner was in order that all fleet
operations would be focused in the control room and that all the operating commands and
offices would be nearby for support. Figure 2a18.2 presents a diagram of the layout of the
offices and spaces that make up the Operations Center complex.
STAR SHIP COMMAND
The Operations Center contains the administrative offices for Star Ship Command.
Specifically, the Office of Star Fleet Ship Operations (SSCOPS) is there to command
the entire fleet in terms of their functions, operations and missions from this central
location. In addition, it is the Office of Star Fleet Ship Operations which manages Star
Fleet Mission Control – the very heart of the Star Fleet Operations Center.
STAR BASE COMMAND
The Operations Center contains the administrative and planning offices for Star Base
Command, which is located within the facility in order to manage the operations involving
the bases and stations. The presence of this command is primarily to monitor the missions
and functions assigned to bases and stations. The Office of Star Fleet Base Operations
will work in concert with the Office of Star Fleet Ship Operations in the coordination of
activities that involve both ships and bases.
SPACE EXPLORATION COMMAND
The Star Fleet Space Exploration Command maintains a small office within the
complex primarily for the planning and monitoring of the colonies and expeditions initiated
by the command. The primary function of this office, as it relates to the functioning of the
Operations Center, is to support Operations in the selection and planning of strategic
areas of space for exploration and colonization. In addition, the Space Exploration
Command will utilize resources within Mission Control to monitor exploration and
survey vessels in the performance of their missions.
STRATEGIC COMMAND
The Operations Center is also headquarters for the Federation Strategic Command
or STRATCOM. The command’s scope of responsibility includes the interrelated areas of
space operations, information operations, computer network operations, and strategic
defense and attack. Tying these areas together STRATCOM is a globally focused
command and control, communications and intelligence, surveillance and reconnaissance
network located at the Star Fleet Operations Control Center. As such, STRATCOM is
located within this facility and linked with Star Fleet Intelligence and the other
Federation intelligence agencies in the development of specific strategic assignments.

VOLUME II
TACTICAL COMMAND
The Star Fleet Tactical Command or TACOM is a sub-organization of the Star Fleet
Office of Strategic and Tactical Operations which develops the short-term missions
based upon the plans originated by STRATCOM. Therefore, it is natural to have this office
within this facility where Tactical Operations or TACOPS will be developed and
monitored.
FLEET COMMUNICATIONS
All communications between the central command and the Operating Forces and Shore
Establishments throughout the Federation and beyond, is handled through the
Communications Center located within the complex. Though direct visual and verbal
communication with the fleet is done within Mission Control, the Communications
Center also sets the cryptographic codes and sends the encrypted messages throughout
the fleet.
The Communications Center is also the central facility that monitors, controls and
programs all of the center’s communications computers. This is where all the cryptographic
and security codes are entered and programmed into all the fleet’s computers. In addition,
all fleet computer programming messages are relayed through this facility and sent to all
the commands throughout the Federation.
Adjacent to the Communications Center is the area where all the communications
receivers, transmitters, amplifiers and computers are located. In this area the physical
messages are sent and received, whether by standard or subspace methods. This is a
highly classified and sensitive area that is normally unmanned and sealed from entry.
Security guards are posted at the entry of the area at all times.
FLEET LOGISTICS
The Operations Center contains a large area devoted to the Star Fleet Office of Fleet
Logistics. This area contains partitioned cubicles containing the various units involved
with planning and executing the logistical plans for any operation and to maintain the
location and inventory of all Star Fleet warehouses, depots and supply storage facilities
throughout the Federation.
OPERATIONS PLANNING
Since the Operations Center is all about operations it is natural to have an area devoted
to the planning of such operations. As such, the Operations Center contains a large area
known as Operations Planning. This is where the various planning sections (e.g. the
Star Fleet Office of Strategic Planning, the Star Fleet Ship Operations Planning
Section, the Star Fleet Base Operations Planning Section, the Star Fleet Office of
Local Force Planning, the Star Fleet Office of Fleet Logistics, and the Star Fleet
Office of Strategic and Tactical Operations) meet and plan current and future
operations in which the Federation and Star Fleet will be involved. However, this area
does not include any Star Fleet Intelligence operations that may be planned. Such
operations are planned and monitored within the Star Fleet Intelligence Operations
Center adjacent to the complex.

VOLUME II
ADJUNCT FORCES COMMAND
The Adjunct Forces Command maintains its central office within the Operations
Center complex so that it can be near Mission Control to manage joint exercises with
Local Forces. This is specifically performed by the Star Fleet Office of Local Force
Planning, whose responsibility it is to plan how to use the Local Forces that may be
assigned to Star Fleet. It is from this facility that the strategies utilizing Local Forces are
developed and monitored as they are being executed within the theatre of operations, and
where the assignment of Local Forces to specific Star Fleet units are developed and
relayed to the respective Local Force Liaison Officer.
FEDERATION JOINT CHIEFS
The Federation Joint Chiefs of Staff have a special conference room within this facility,
which serves as a place for general staff meetings and to discuss Federation and Star
Fleet policy as well as to plan strategic operations. The Federation Joint Chiefs do not
maintain permanent offices at Star Base Central, but have guest offices at every major
Star Fleet Headquarters. They rotate the location of their meetings every one hundred
Federation days. This is done as a courtesy to the signatory worlds so as not to give the
appearance of partiality towards any specific center or culture.
CONFERENCE ROOMS
The center contains several conference rooms where operations personnel can get
together for various meetings. However, the center has one large conference room for
major and private operations and conferences. This conference room has a large view
screen for display and communications with any command or agency throughout the
Federation. As such, meetings with field commanders to discuss operations can take
place in real-time.
COMPUTER EQUIPMENT AND CIRCUITRY
In order to access and maintain all the equipment and computers needed for real-time
fleet monitoring and communications, all the computer equipment and circuitry is located
within the Operations Center complex. Engineers and technicians are on duty 24 hours a
day to keep the equipment at top operational condition. As such, all computer rooms,
circuitry trunks and conduit tunnels are considered highly classified areas and only
authorized personnel are allowed access to them.

VOLUME II
Figure 2a18.1
STAR FLEET OPERATIONS CENTER ORGANIZATION
OPC Operations Center

Commander
CAPT
OCDO
Operations Center
Duty Officer
CMDR
OPCADM
Administrative
Assistant
T5
OCSO OCEO OCRO OCLO

Center Security Center Engineering Center Maintenance Center Support
Officer Officer Officer Officer
LCDR LCDR LCDR LCDR

VOLUME II
Figure 2a18.2
BASIC OPERATIONS CENTER LAYOUT
Space
Exploration
Star Base Command
Command
Maps and
Surveys
Communications
Conference Room
Center
Tactical
Command
(TACOM)
Comm
Circuitry
Operations Mission
Fleet
Planning Control
Logistics
Holographic
Display
Duty Intelligence Operations Center
Quarters
Tactical
Simulation
Star Ship CDO

Joint Chiefs Office
Conference Command
Room Security
Office Computer
Room
Strategic
Command Adjunct
(STRATCOM) Forces
Command

OFFICIAL USE ONLY
VOLUME II
2.0 STAR FLEET OPERATIONS DIVISION

ORGANIZATION
In this section the organizational structure of Star Fleet Operations will be briefly
discussed. This structure represents the “Chain of Command” for the division. The
remaining sections of this chapter will discuss the various elements of the command
structure in more detail.
The high-level command structure of Star Fleet Operations is illustrated in Figure

2a20.1, which shows all the primary division heads by their title, designation and rank. At
the top level is the Chief of Star Fleet Operations (CSFO), the senior military officer of
the Operations Division as required under ARTICLE 42 of the Star Fleet Charter, with
the responsibilities and authorities as stipulated therein. A complete description of the
CSFO may be found in Section 2.1 of this volume.
The organization and function of each division head within the Operations Division will
be described in detail within the subsequent sections of this chapter. Note that throughout
the sections of this chapter the term “his” or “him” may be used. This is not to indicate
gender, but merely a convenient way to show possession.
OFFICE OF THE CHIEF OF STAR FLEET OPERATIONS
The Office of the Chief of Star Fleet Operations was established in accordance with
ARTICLE 42 of the Star Fleet Charter and as such, represents the top most level within
the Operations Division of the Department of the Star Fleet. The Office of the
CSFO contains the Operations Chief of Staff and the Commandant: Star Fleet
Marine Corps as specified in Paragraph 4 of Star Fleet Regulation 2600.
OPERATIONS CHIEF OF STAFF
The Operations Chief of Staff (OPSOS) is a position created within the Office of the
Chief of Star Fleet Operations under Star Fleet Regulation 3810 for the purpose of
supervising and coordinating the work of the staff assigned to the CSFO. The OPSOS is
an officer junior to the CSFO, and will typically have the rank of Vice Admiral, which was
established following the guidelines set forth in Paragraph 2 of Star Fleet Regulation
3810, and which defines the requirements of an officer detailed as "Chief Staff Officer."
Although essentially managing the staff for the CSFO, the position of OPSOS has no
command authority in and of itself. The OPSOS basically coordinates the work assigned to
the staff by the CSFO. A more detailed description of the duties of the OPSOS will be
made in Section 2.2 of this volume.
DIVISION COMMANDERS
The Operations Division is organized into five Operational (Type) Commands and
three administrative offices specifically created to manage the major functions of the
division. In general, a “Command” is a large organization with a somewhat wide scope,
whereas an “Office” is more focused on a specific function. The heads of these commands
and offices will be described in the subsequent sections of this chapter.

VOLUME II
ORGANIZATIONAL CHARTS
Throughout this chapter organization charts will be presented for the various commands
and subdivisions within the Star Fleet Division of Operations. These charts generally
represent the “Chain of Command” within the division, and will be referred to
throughout the remaining sections of this chapter. The title blocks of each office contains
the office or command title, the Command Designation and the specified rank of the officer
holding that position. The Command Designation is a shorthand version of the office title.
Command Designation Command Title
CSFO
Chief of Star Fleet
Operations
ADML
Command Rank
In addition, the organization charts will contain abbreviations for the rank of the individual
holding that position. The following table lists the abbreviations for the Command Ranks
presented in these charts.
Abbreviation Command Rank

FADM Fleet Admiral
ADML Admiral
VADM Vice Admiral
RADM Rear Admiral
COMO Commodore
CAPT Captain
CMDR Commander
LCDR Lieutenant Commander
LEUT Lieutenant
LTJG Lieutenant Junior Grade
ENSN Ensign

VOLUME II
Figure 2a20.1
STAR FLEET OPERATIONS ORGANIZATION
Office of the Chief of CSFO

Chief of Star Fleet
Star Fleet Operations Operations
ADML
CMMC
Commandant: Star
Fleet Marine Corps
ADML
OPSADM
Administrative
Assistant
T5
OPSOS
Operations
Chief of Staff
VADM
CSSC CSBC CFOR CINT

Deputy Chief: Deputy Chief: Deputy Chief: Deputy Chief:
VADM VADM VADM VADM
COMFLTEXP COMFLTSUP COMFLTCOM COMTAC

Commander: Commander: Commander: Fleet Commander:
Space Exploration Fleet Logistics Communication Tactical Operations
RADM RADM RADM RADM
COMSEC
Sector
Commandants
ADML

VOLUME II

VOLUME II
2.1 CHIEF OF STAR FLEET OPERATIONS

The Chief of Star Fleet Operations[1] (CSFO) is the senior officer in command of Star
Fleet Operations and of all the Operating Forces and Shore Establishments within
the Department of the Star Fleet. This office was created under ARTICLE 42 of the
Star Fleet Charter and as stated in this article, the Chief of Star Fleet Operations is
responsible for:
 Organizing the forces and resources of Star Fleet and to assign duties to subordinate
Star Fleet Commanders
 Preparing the plans for the employment of the forces of Star Fleet to meet existing
and foreseeable strategic requirements
 Maintaining effective intelligence and to keep the Director informed of the political
and military situations inside and outside the Federation
 Ensuring the readiness, effectiveness, and efficiency of Star Fleet forces through
inspections and other instruments
 Executing all operational orders, directives, instructions and policies derived from the
Director
Basically speaking, next to the Director: Star Fleet Command and the Vice Director:
Star Fleet Command, the Chief of Star Fleet Operations is the third most senior
officer within the Department of the Star Fleet, and will have precedence over the
other Division Commanders as well as precedence over all Local Force Commanders
assigned to joint operations with Star Fleet or operating in open space.

VOLUME II
AUTHORITY AND RESPONSIBILITY OF THE CSFO
In general, the Chief of Star Fleet Operations commands the entire Operating Forces
of the Star Fleet as well as all its shore activities. The CSFO is directly responsible to the
Director for the utilization of Star Fleet resources in accomplishing the missions to which
Star Fleet is assigned, and for maintaining the operating efficiency of all commands and
activities within the Operating Forces and Shore Establishments.
The CSFO is directly responsible to the Director for organizing, preparing, training,
equipping and maintaining the readiness of Star Fleet forces, including those assigned to
a unified or specific command for the performance of the missions assigned to it by the
Director or the Military Staff Committee. In addition, the CSFO will determine and
direct the efforts necessary to fulfill current and future requirements of the Operating
Forces and of the Shore Establishments for manpower, material, facilities and services,
including the determination of quantities, qualities, and military performance requirements.
As such, the Chief of Star Fleet Operations will formulate tactical plans and directives
regarding the assignment and use of Star Fleet assets in order to fulfill the strategies and
missions given to it by the Director and the Military Staff Committee. In addition, the
CSFO will participate in the formulation of joint and combined strategic plans with all of
the Local Forces in order to fulfill the requirement to maintain an effective Federation
force.
The CSFO is also responsible for the budgets of all the commands within the division, and
is responsible to budget for all operational activities and programs as assigned, except as
may be otherwise instructed by the Director. In so doing, the CSFO is responsible for
determining the requirements of Star Fleet forces and all their activities, and is required
to inspect and investigate components of the Star Fleet to determine their efficiency,
discipline, readiness, effectiveness and economy.
In addition to the authorities and responsibilities mentioned, the Director: Star Fleet
Command has also delegated to the CSFO the responsibility for maintaining the Star
Fleet Vessel and Station Registries. Therefore, the CSFO is also responsible for the
assignment and classification of Star Fleet spacecraft, and for the designation of the
status of each ship and service craft in the fleet, as well as the designation of the status of
each Star Fleet station and base.

VOLUME II
OFFICE OF THE CHIEF OF STAR FLEET OPERATIONS
ARTICLE 42 of the Star Fleet Charter established the Office of the Chief of Star Fleet
Operations as the focal point for all Star Fleet operations. In addition, this office is also
shared with the Commandant: Star Fleet Marine Corps (CMMC), who is the senior
officer in command of all Star Fleet troops and ground forces. The CMMC shares coequal
authority with the CSFO since the Fleet Marine Corps is part of the Operating Forces
of the Star Fleet, but only with respect to the ground forces. In any action where ground
forces will be required the CMMC and the CSFO will work together to plan the operation.
Otherwise, each is in complete command of their respective forces.
The Office of the Chief of Star Fleet Operations also contains the Operations Chief
of Staff, whose responsibility it is to supervise and coordinate the work of the staff
assigned to the CSFO. A more detailed description of the duties and responsibilities of the
Operations Chief of Staff can be found in Section 2.2 of this volume.
Physically, the Office of the Chief of Star Fleet Operations is located at Star Base
Central, with the office very close to the Director. Figure 2a21.1 illustrates the command
organization of the Office of the Chief of Star Fleet Operations.
OPERATIONS CHIEF OF STAFF
The Star Fleet Operations Chief of Staff (OPSOS) is an appointment created within
the Office of the Chief of Star Fleet Operations in accordance with Star Fleet
Regulation 3810 for the purpose of supervising and coordinating the work of the staff
assigned to the CSFO. The OPSOS is an officer junior to the CSFO, and will typically have
a rank of Vice Admiral. This rank was established following the guidelines set forth in
Paragraph 2 of Star Fleet Regulation 3810 regarding an officer detailed as "Chief
Staff Officer." The Operations Chief of Staff is appointed by the Chief of Star Fleet
Operations. It is the privilege of the CSFO to select his or her own Operations Chief of
Staff under Star Fleet Regulation 3810. The only requirement to become the
Operations Chief of Staff is that the officer selected must be a senior Star Fleet officer
of flag grade and eligible to command. Should the position of Operations Chief of Staff
become vacant, the CSFO can choose any eligible senior flag officer to fill the position.
Although essentially managing the staff of the CSFO, the position of OPSOS has no
command authority in and of itself. The OPSOS basically coordinates the work assigned to
the staff by the CSFO. Figure 2a21.2 illustrates the command organization of the Office
of the Operations Chief of Staff.

VOLUME II
CIVILIAN ASSISTANTS
The Office of the Chief of Star Fleet Operations (CSFO) contains several civilian
assistants to help the CSFO interact with civilian Federation authorities and other
government or civilian officials regarding military operations and intelligence. The CSFO
maintains several civilian assistants that work within the Federation Intelligence
Agency in order to keep Star Fleet informed on the latest global intelligence information.
In addition, the CSFO will also employ or appoint civilian personnel to work as assistants
to the Federation Joint Chiefs of Staff within the Military Staff Committee as well.
UNIFORM OF THE CHIEF OF STAR FLEET OPERATIONS
The uniform of the Chief of Star Fleet Operations is the same as for all other officers
and enlisted Technicians within the Star Fleet Service. The uniform for the Chief of
Star Fleet Operations conforms to the Star Fleet Uniform Standard (BUPERSMAN-
332), and consists of the Formal Dress Blue (SFMO1N) and the Ceremonial Dress
White (SFMO1W) uniforms as illustrated in Figure 2a21.3 for official and formal
occasions, and the Service Dress (SDMO1G) as shown in Figure 2a21.4 for semi-formal
and military functions. However, the Chief of Star Fleet Operations will generally wear
the standard working uniform (SWMO1A) while on duty. The uniform generally consists
of a pair of black trousers (Item 3421) and the Type II tunic (Item 3413 or 3414 for
females) in goldenrod. The sleeve braid of the Chief of Star Fleet Operations consists
of one thick solid gold band and three thin solid gold bands as illustrated in Figure 2a21.3.

VOLUME II
CHIEF OF STAR FLEET OPERATIONS FLAG
The Office of the Chief of Star Fleet Operations is indicated by the emblem of the
Star Fleet Division of Operations and as such, the CSFO may fly a personal flag with
this emblem. The flag is a rectangle with the dimensions 168 cm long by 94 cm wide. The
symbol and title of Star Fleet Operations is placed in the center of a blue field with a
gold border. At the corners are four white stars indicating the rank of the CSFO to be a
full Admiral as stipulated by Star Fleet Standards and as illustrated below:
CHIEF OF STAR FLEET OPERATIONS BADGE
The Office of the Chief of Star Fleet Operations is indicated by the special badge
worn only by the Chief of Star Fleet Operations. The following is the badge for the
CSFO, which may be worn on all uniforms.

VOLUME II
SELECTION OF THE CSFO
The Chief of Star Fleet Operations is an appointed position, the selection of which is
solely the prerogative of the Director: Star Fleet Command. It is the privilege of the
Director: Star Fleet Command to select his or her chief of operations. As such, the
selection of the Chief of Star Fleet Operations by the Director: Star Fleet Command
does not require the approval of either the Federation Council or the Military Staff
Committee. Generally, the CSFO will come from the senior flag ranks of the Operations
Division and will typically be selected based upon the candidate’s position within the
lineal list of flag officers along with any other criteria the Director deems important or
necessary.
As stated above, the Director: Star Fleet Command will normally select the candidate
to head the Operations Division. However, the Flag Officer Review Board may make
several selections of its own and present them to the Director for consideration as well.
The Director may then choose one of the candidates suggested or will continue with his
original selection. When selecting a candidate for any position within Star Fleet, the
Director will always have the privilege of interviewing any candidate considered or may
request an interview of anyone he so chooses. The Director will then inform the Division
of Personnel, through the Star Fleet Chief of Staff, of his approved selection. The
Chief of Star Fleet Personnel will draw-up and sign orders for the selected candidate.
The Director will then make his final signature and the orders will be issued to the
candidate.
The duration of the appointment is completely up to the Director, and there is no time
limit associated with this appointment. The Director will evaluate the performance of the
CSFO on a yearly basis, and will decide if a replacement is necessary or desired. As with
all division directors within the Department, the CSFO works for and at the pleasure of the
Director.
SUCCESSION
In accordance with Star Fleet Regulation 5930, the Operations Chief of Staff, and
then the officers of Star Fleet on duty in the Office of the Chief of Star Fleet
Operations in the order of their seniority will, unless otherwise directed by the Director:
Star Fleet Command, temporarily perform the duties of the CSFO during his absence or
disability, or in the event of a temporary vacancy in that office until the Director: Star
Fleet Command appoints a permanent replacement. Should the Operations Chief of
Staff or any other of the officers within the Office of the Chief of Star Fleet
Operations become unable to fulfill the duties of the CSFO, the Director will select a
commander from one of the operational units to fill the position.

VOLUME II
COMMANDANT: STAR FLEET MARINE CORPS
The Commandant: Star Fleet Marine Corps is the senior officer in command of all
Star Fleet troops and ground forces. The CMMC shares coequal authority with the CSFO
since the Fleet Marine Corps is part of the Operating Forces of the Star Fleet, but
only with respect to the ground forces. In such action where ground forces will be required
the CMMC and the CSFO will work together to plan the operation. Figure 2a21.5
illustrates the command organization of the Office of the CMMC. However, with regard
to operations performed by Star Fleet, the orders and directives issued by the Chief of
Star Fleet Operations take precedence over those issued by the Commandant of the
Star Fleet Marine Corps as required under ARTICLE 42 of the Star Fleet Charter.
AUTHORITY AND RESPONSIBILITY OF THE CMMC
In general, the Commandant: Star Fleet Marine Corps commands the entire ground
forces of Star Fleet. The CMMC is directly responsible to the Director for the utilization
of Star Fleet Ground Forces in accomplishing the missions to which the Star Fleet is
assigned and for maintaining the operating efficiency of all ground troop commands.
The CMMC is directly responsible to organize, train, equip, prepare and maintain the
readiness of the Star Fleet Marine Corps for the Director, including those assigned to a
unified or specific command. In addition, the CMMC will determine and direct the efforts
necessary to fulfill current and future requirements of the ground forces for manpower,
material and services, including the determination of quantities, qualities, and military
performance requirements. And along with the Chief of Star Fleet Operations, will
formulate tactical plans and directives regarding the assignment and use of Star Fleet
ground troops in the fulfillment of strategies and missions given to it by the Director and
the Military Staff Committee.
The CMMC is also responsible to budget for the commands within the corps, and to
budget for all operational activities and programs as assigned, except as may be otherwise
instructed by the Director. In so doing, the CMMC is responsible to determine the needs
of the Star Fleet Marine Corps and all their activities, and is required to inspect and
investigate components of the Marine Corps to determine and maintain their efficiency,
discipline, readiness, effectiveness and economy.
RELATIONSHIP WITH OTHER MEMBERS OF THE

OPERATIONS DIVISION
Although part of the Operations Division, the Commandant: Star Fleet Marine
Corps does not have authority over the staff or of the regular personnel of the division.
The Commandant only has command authority over the Marine Corps staff and troops.
However, all deference shall be observed towards the Commandant since he is a senior
officer of the Star Fleet and takes precedence over other officers due to his rank and
position, but cannot make changes to other organizations or direct personnel other than
those in his own command as specified in Star Fleet Regulations 6230 and 6850.

VOLUME II
OFFICE OF THE MARINE CORPS COMMANDANT
The Office of the Commandant: Star Fleet Marine Corps is an integral part of the
Office of the Chief of Star Fleet Operations. It was created thus in order for the two
branches to coordinate the activities of the two separate parts of the Operating Forces.
As such, the Office of the Commandant: Star Fleet Marine Corps will be the focal
point for all Star Fleet Marine Corps operations, but will coordinate with the other
offices within the Operations Division as required. As previously stated, the CMMC
shares coequal authority with the CSFO since the Fleet Marine Corps is part of the
Operating Forces of the Star Fleet, but only with respect to the ground forces. In any
action where ground forces will be required the CMMC and the CSFO will work together
to plan the operation. Otherwise, each is in complete command of their respective forces.
The Office of the Commandant: Star Fleet Marine Corps contains the Marine Corps
Chief of Staff (MMCOS), who is second in command of the Marine Corps. As such, all
orders from the MMCOS will have the same force as those issued by the CMMC. In
addition, the MMCOS also has the responsibility of supervising and coordinating the work
of the staff assigned to the CMMC and of all the force and division commanders in the
field.
Physically, the Office of the Commandant: Star Fleet Marine Corps is located at Star
Base Central adjacent to the Chief of Star Fleet Operations. Figure 2a21.5 illustrates
the command organization of the Office of the CMMC.
MARINE CORPS CHIEF OF STAFF
The Marine Corps Chief of Staff (MMCOS) is an appointment created within the Office
of the Commandant: Star Fleet Marine Corps in accordance with Star Fleet
Regulation 3810 for the purpose of supervising and coordinating the work of the staff
assigned to the CMMC. The MMCOS is an officer junior to the CMMC, and will typically
have a rank of Vice Admiral. This rank was established following the guidelines set forth
in Paragraph 2 of Star Fleet Regulation 3810 regarding an officer detailed as "Chief
Staff Officer." Since the Marine Corps Chief of Staff is an appointed position to the
Commandant: Star Fleet Marine Corps, it is the privilege of the CMMC to select his or
her own Marine Corps Chief of Staff under Star Fleet Regulation 3810. The only
requirement to become the Marine Corps Chief of Staff is that the officer selected must
be a senior officer of the Marine Corps of flag grade and eligible to command. Should the
position of Marine Corps Chief of Staff become vacant, the CMMC can choose any
eligible senior Marine Corps flag officer to fill the position.
Although essentially managing the staff of the CMMC, the position of MMCOS has no
command authority in and of itself. The MMCOS basically coordinates the work assigned
to the staff by the CMMC. Figure 2a21.6 illustrates the command organization of the
Office of the MMCOS.

VOLUME II
FLAG OF THE COMMANDANT
The Office of the Commandant: Star Fleet Marine Corps is indicated by the emblem
of the Star Fleet Marine Corps and as such, the CMMC may fly a personal flag with this
emblem. The flag is a rectangle with the dimensions 168 cm long by 94 cm wide. The
symbol and title of the Star Fleet Marine Corps placed in the center of a red field with a
gold border. At the corners are four gold stars indicating the rank of the CMMC to be a full
Admiral as stipulated by Star Fleet Standards and as illustrated below:
COMMANDANT: STAR FLEET MARINE CORPS BADGE
The Office of the Commandant: Star Fleet Marine Corps is indicated by the special
badge worn only by the Commandant: Star Fleet Marine Corps. The following is the
badge for the CMMC, which may be worn on all uniforms.

VOLUME II
UNIFORM OF THE COMMANDANT: STAR FLEET MARINE

CORPS
The uniform of the Commandant: Star Fleet Marine Corps is the same as for all other
officers and enlisted Technicians within the Star Fleet Service. The uniform for the
Commandant: Star Fleet Marine Corps conforms to the Star Fleet Uniform
Standard (BUPERSMAN-332), and consists of the Formal Dress Blue (SFMO1N) and
the Ceremonial Dress White (SFMO1W) uniforms as illustrated in Figure 2a21.7 for
official and formal occasions, and the Service Dress (SDMO1G) as shown in Figure
2a21.8 for semi-formal and military functions. However, the Commandant: Star Fleet
Marine Corps will generally wear the Star Fleet Marine Corps working uniform while
on duty. The uniform generally consists of a pair of tan trousers (Item 3421) and the Type
II tunic in tan. The sleeve braid of the Commandant: Star Fleet Marine Corps consists
of one thick solid gold band and three thin solid gold bands as illustrated in Figure 2a21.7.
SELECTION OF THE CMMC
As with the Chief of Star Fleet Operations, the Commandant of the Marine Corps is
an appointed position, the selection of which is solely the prerogative of the Director:
Star Fleet Command. And like the CSFO, the selection of the Commandant does not
require the approval of either the Federation Council or the Military Staff Committee.
Generally, the CMMC will come from the senior flag ranks of the Fleet Marine Corps and
will typically be selected based upon the candidate’s position within the lineal list of flag
officers. The procedure for review and approval will be the same as that for the Chief of
Star Fleet Operations.
The duration of the appointment is completely up to the Director, and there is no time
limit associated with this appointment. The Director will evaluate the performance of the
CMMC on a yearly basis, and will decide if a replacement is necessary or desired.
SUCCESSION
In accordance with Star Fleet Regulation 5930, the Marine Corps Chief of Staff, and
then the officers of Star Fleet on duty in the Office of the Commandant: Star Fleet
Marine Corps in the order of their seniority will, unless otherwise directed by the
Director: Star Fleet Command, temporarily perform the duties of the CMMC during his
absence, or disability, or in the event of a temporary vacancy in that office until the
Director: Star Fleet Command appoints a permanent replacement. Should the Marine
Corps Chief of Staff or any other of the officers within the Office of the Commandant
become unable to fulfill the duties of the CMMC, the Director will select a commander
from one of the operational ground units.

VOLUME II
Figure 2a21.1
STAR FLEET OPERATIONS ORGANIZATION
CSFO
Chief of Star Fleet
Operations
ADML
CMMC
Commandant: Star
Fleet Marine Corps
ADML
OPSADM
Administrative
Assistant
T5
OPSOS
Operations
Chief of Staff
VADM
CSSC CSBC CFOR CINT

Deputy Chief: Deputy Chief: Deputy Chief: Deputy Chief:
VADM VADM VADM VADM
COMFLTEXP COMFLTSUP COMFLTCOM COMTAC

Commander: Commander: Commander: Fleet Commander:
Space Exploration Fleet Logistics Communications Tactical Operations
RADM RADM RADM RADM
COMSEC
Sector
Commandants
ADML

VOLUME II
Figure 2a21.2
OFFICE OF THE OPERATIONS CHIEF OF STAFF
OPSOS
Operations
Chief of Staff
VADM
OPSADJ OPSADM
Operations Command
Staff Adjutant Yeoman
COMO T5
OPLAN OPREQ OPRED OPSRV

Fleet Planning Fleet Requirements Fleet Readiness Fleet Services
CAPT CAPT CAPT CAPT

VOLUME II
Figure 2a21.3
UNIFORM OF THE CHIEF OF STAR FLEET OPERATIONS
Formal Dress Blue Ceremonial Dress White
Star Fleet
Unifor m
Star Fleet
Unifor m

VOLUME II
Figure 2a21.4
UNIFORM OF THE CHIEF OF STAR FLEET OPERATIONS - CONTINUED
Service Dress Uniform Standard Working Uniform
Star Fleet
Unifor m
C
o
m
m
a
n
d
D
e
s
i
g
n
a
t
i
o
n

VOLUME II
Figure 2a21.5
COMMANDANT OF THE STAR FLEET MARINE CORPS
CMMC
Commandant: Star
Fleet Marine Corps
ADML
SECFOR MMCADM
Commander: Administrative
Special Forces Assistant
RADM T5
MMCOS
Marine Corps
Chief of Staff
VADM
COMFOR 1 Commander: COMFOR 2 Commander: COMFOR 3 Commander: COMFOR 4 Commander:

Sector Fleet Marine Sector Fleet Marine Sector Fleet Marine Sector Fleet Marine
VADM Forces 1 VADM Forces 2 VADM Forces 3 VADM Forces 4
COMFOR 5 Commander: COMFOR 6 Commander: COMFOR 7 Commander: COMFOR 8 Commander:

Sector Fleet Marine Sector Fleet Marine Sector Fleet Marine Sector Fleet Marine
VADM Forces 5 VADM Forces 6 VADM Forces 7 VADM Forces 8
COMDIV
Marine Division
Commanders
RADM

VOLUME II
Figure 2a21.6
OFFICE OF THE MARINE CORPS CHIEF OF STAFF
MMCOS
Marine Corps
Chief of Staff
VADM
MMCADJ MMCADM
Marine Corps Command
Adjutant Yeoman
COMO T5
MCLAN MCREQ MCRED MCSRV

Marine Corps Marine Corps Marine Corps Marine Corps
Planning Officer Requirements Officer Readiness Officer Services Officer
CAPT CAPT CAPT CAPT

VOLUME II
Figure 2a21.7
UNIFORM OF THE COMMANDANT OF THE STAR FLEET MARINE CORPS
Formal Dress Blue Ceremonial Dress White
Star Fleet
Unifor m
Star Fleet
Unifor m

VOLUME II
Figure 2a21.8
UNIFORM OF THE COMMANDANT OF THE STAR FLEET MARINE CORPS - CONTINUED
Service Dress Uniform Standard Working Uniform
Star Fleet
Unifor m
C
o
m
m
a
n
d
D
e
s
i
g
n
a
t
i
o
n

VOLUME II
2.2 STAR FLEET OPERATIONS STAFF

The Operations Division is organized into five Operational (Type) Commands and
three administrative offices specifically created to manage the major functions of the
division. These commands vary in size and scope and as such, the title of the directors of
such subdivisions will be commensurate with their duties and responsibilities. Commanders
of large Star Fleet “Type Commands” will have the title of Deputy Chief, while the
commanders of the smaller offices will have the title of Commander. However, in
general, commanders will be titled according to the size and scope of the subdivision or
Type Command they command in accordance with ARTICLE 43 of the Star Fleet
Charter. The function of each subdivision commander will be described in the following
subsections.
STAR FLEET OPERATIONS CHIEF OF STAFF
The Office of the Operations Chief of Staff was created under Star Fleet Regulation
3810 to aid the Chief of Star Fleet Operations in the management of the division. The
primary function of the Operations Chief of Staff (OPSOS) is to manage the various
subdivision commanders and to dispense to them the work assigned by the Chief of Star
Fleet Operations. In addition, the OPSOS will forward any requests made by the
subdivision commanders to the CSFO. In this capacity the OPSOS is second in command
within the Operations Division and therefore, the orders issued by the OPSOS have the
same authority as if such orders were issued by the CSFO.
The organizational structure for the Office of the Operations Chief of Staff is
illustrated in Figure 2a22.1. The persons that come under direct authority of the OPSOS
are the commanders of the subdivisions comprising the Operations Division, also known
as “Subdivision Commanders”.
The OPSOS has assigned to him the Operations Staff Adjutant (OPSADJ) to aid in the
administration and discipline of the staff members that report directly to the OPSOS.
Typically a line officer with the rank of Commodore, the OPSADJ will ensure that the
individuals under the direction of the OPSOS perform their duties. These individuals are
typically the administrative assistants to the CSFO and the OPSOS and those civilian
assistants employed by the division.
The position of Operations Chief of Staff is an appointment made by the Chief of Star
Fleet Operations. It is the privilege of the CSFO to select his or her own Chief of Staff
under Star Fleet Regulation 3810. The only requirement to become the Chief of Staff
is that the officer selected must be a senior Star Fleet line officer of flag grade and
eligible to command. Should the current position of Chief of Staff become vacant for
some reason, the CSFO can choose any eligible senior flag officer to fill the position. The
CSFO will evaluate the performance of the Chief of Staff on an annual basis, and can
remove or replace the individual holding that office at any time.

VOLUME II
OPERATIONS STAFF
The operations staff consists of the commanders of the offices and units that support fleet
operations. As shown in Figure 2a20.1 the Operations Division contains eight operations
subdivisions to distribute the functions of the division. These subdivisions are commanded
by a “Subdivision Commander” and are listed below:
 The Deputy Chief: Star Ship Command

 The Deputy Chief: Star Base Command
 The Deputy Chief: Adjunct Forces
 The Deputy Chief: Star Fleet Intelligence
 The Commander: Space Exploration
 The Commander: Fleet Logistics
 The Commander: Fleet Communications
 The Commander: Tactical Operations
TYPE COMMANDERS
A Type Commander is a generalized term for a commander of a specific function or unit

within Star Fleet. Within the Operations organization, Type Commanders manage the
primary functional and support units of the Operating Forces. As such, there are only
five Type Commanders at the division level, which represent the basic Operations
“types” such as those relating to ships, shore facilities, Local Forces, exploration and
intelligence. Type Commanders will generally have the title of Deputy Chief, and within
the Operations Division they are:
 The Deputy Chief: Star Ship Command

 The Deputy Chief: Star Base Command
 The Deputy Chief: Adjunct Forces
 The Deputy Chief: Star Fleet Intelligence
 The Commander: Space Exploration
GENERAL SELECTION OF SUBDIVISION COMMANDERS
Subdivision commanders will generally come from the senior ranks of the Operations
Division and are generally selected by the Chief of Star Fleet Operations. Generally,
these commanders will be selected from a lineal list of flag officers based upon their
position within the list.
In general, the Chief of Star Fleet Operations (CSFO) will select the candidate to
command a subdivision and will submit the name to the Chief of Star Fleet Personnel
(CPER). The CPER will then task the Flag Officer Review Board to review the
candidate’s record and to make their recommendation as to the suitability of the officer for
the position, or they may submit their own candidate to the CSFO for review. The CSFO
will then inform the Division of Personnel, through the Operations Chief of Staff, of
his approved selection. The Chief of Star Fleet Personnel will draw-up and sign orders
for the selected candidate. The Director: Star Fleet Command will then make his final
approval and the orders will be issued to the candidate.

VOLUME II
DEPUTY CHIEF: STAR SHIP COMMAND
The Deputy Chief: Star Ship Command (CSSC) is the senior officer in command of all
activities regarding the operations, missions and assignments of Star Fleet ships, craft
and their personnel. The Deputy Chief: Star Ship Command is the senior officer in
command of the Star Ship Command (SSC) subdivision and is directly responsible to the
Chief of Star Fleet Operations for:
 The assignment of Star Fleet ships and craft to sectors, fleets, squadrons, etc.
 The planning and assignment of Star Fleet ships and craft to missions, expeditions,
maneuvers, etc.
 The assignment of Star Ship Command personnel to duty
 The training of Star Fleet ship Commanding Officers and operations personnel
 Determining fleet needs and requirements
 Developing strategic and tactical maneuvers for Star Fleet ships and craft
The CSSC is an officer of the line (SSC) junior to the CSFO, and will typically have the
rank of Vice Admiral. Under the CSSC are the various commanders of the offices and
sections necessary to carry out the duties and responsibilities of Star Ship Command, as
illustrated in Figure 2a22.2. These are listed in the table below:
Office Title Rank Duties and Responsibilities

Commander: Star Fleet Ship Commodore  Assigns Star Ship personnel to duty
Personnel (COMO)  Determines force requirements
 Assigns ships to operating units
Commander: Star Fleet Ship Rear Admiral
 Maintains locations of all Star Fleet vessels
Operations (RADM)
 Assigns ships and crews to missions
 Determine the material and supply needs of
the fleet
Commodore
Commander: Star Fleet Ship Logistics  Plan and schedule supply rendezvous
(COMO)
 Submits logistical requirements to the Office of
Logistics
 Determine fleet and force size
 Studies and recommends what the future of
Captain the fleet should look like
Commander: Star Fleet Ship Planning
(CAPT)  Recommends orders for new ships or ship
classes
 Maintains the Star Fleet Vessel Register
 Determines the personal needs of ship crews
Captain
Commander: Star Fleet Ship Services  Establishes recreational and other ship-board
(CAPT)
services
 Manage the entire shuttlecraft and service
craft fleet
Rear Admiral  Assign shuttlecraft, interceptors and other
Commander: Star Fleet Service Craft
(RADM) service craft to the Operating Forces and the
Shore Establishment
 Maintains the Service Craft Register

VOLUME II
DEPUTY CHIEF: STAR BASE COMMAND
The Deputy Chief: Star Base Command (CSBC) is the senior officer in command of all
activities regarding the operations and missions of Star Fleet bases, stations, outposts
and their personnel; in effect the Deputy Chief: Star Base Command is responsible for
the entire Shore Establishment of Star Fleet. The CSBC is the senior officer in charge
of the Star Base Command (SBC) subdivision and is directly responsible to the Chief of
Star Fleet Operations for:
 The assignment of Star Base Command personnel to duty on bases, stations and
outposts
 Selecting the location of new bases and stations
 The planning and assignment of Star Fleet troops to bases, stations and garrisons
 The training of Star Fleet base and station Commanding Officers and operations
personnel
 Determining the needs and requirements for each facility
 Developing strategic and tactical plans for Star Fleet bases and stations
The CSBC is an officer of the line (SBC) junior to the CSFO, and will typically have the
rank of Vice Admiral. Under the CSBC are the various commanders of the offices and
sections necessary to carry out the duties and responsibilities of Star Base Command, as
illustrated in Figure 2a22.3. These are listed in the table below:

 Assigns Star Base personnel to bases and
Commander: Star Fleet Base Commodore
stations
Personnel (COMO)
 Determines base duty rotations
 Determines the functional mission of Star Fleet
bases
Commander: Star Fleet Base Rear Admiral
 Establishes the type, level and power of
Operations (RADM)
weapons systems to be installed
 Maintains the Star Fleet Station Register
 Determine the material and supply needs of
the Star Fleet bases and stations
Commodore
Commander: Star Fleet Base Logistics  Plan and schedule base replenishment
(COMO)
 Submits logistical requirements to the Office of
Logistics
 Examines locations for future bases
 Determines the structural needs for the new
Commander: Star Fleet Base Captain facility based upon local conditions
Requirements (CAPT)  Determines the defensive needs for new bases
 Determines the manpower needs for new
bases
 Determines functional needs for bases and
stations
Captain
Commander: Star Fleet Base Facilities  Develops requirements for designing and
(CAPT)
building bases and stations
 Purchases equipment for shore facilities
 Determines base security needs
Captain
Commander: Star Fleet Base Security  Works with the Division of Security to allocate
(CAPT)
security force resources

VOLUME II
DEPUTY CHIEF: ADJUNCT FORCES
The Deputy Chief: Adjunct Forces (CFOR) is the senior officer in command of all
activities regarding the operations and missions of the Local Forces adjoined to Star
Fleet in a unified command according to ARTICLE 15 of the Star Fleet Charter. The
Deputy Chief: Adjunct Forces is the senior officer in command of the Adjunct Forces
Command (AFOR) subdivision and is directly responsible to the Chief of Star Fleet
Operations for:
 The assignment of Federation Local Forces to Star Fleet commands and units
 The development of specific task commands utilizing adjunct forces
 Keeping the CSFO informed on the status and state of readiness of Local Forces
 Maintaining communication and close relationships with Local Force Commanders,
which is accomplished through Local Force Liaison Officers assigned to the Local
Force Commands
 The training of Local Force Commanders and Local Force personnel regarding
Star Fleet operations, regulations and procedures
 Determining the needs and requirements for unified commands
 Developing joint strategic and tactical operations with Local Forces
The CFOR is an officer of the line (SFC) junior to the CSFO, and will typically have a rank
of Vice Admiral. Under the CFOR are the various commanders of the offices and sections
necessary to carry out the duties and responsibilities of the Adjunct Forces Command,
as illustrated in Figure 2a22.4. These offices are listed in the table below:

Captain  Selecting the Local Forces to be used
Commander: Local Force Planning
(CAPT)  Make plans on how Local Forces will be used
 Generate the standards to be used to evaluate
Local Force capability and readiness
Captain
Commander: Local Force Readiness  Evaluate the readiness of Local Forces
(CAPT)
 Determine the material and functional
weakness of Local Forces
 Train Local Forces in Star Fleet procedures
Captain  Train Local Forces on Star Fleet equipment
Commander: Local Force Training
(CAPT)  Develop Local Force training programs
 Develop joint training exercises
 Evaluate the material condition of Local Force
equipment
Captain  Supply Local Forces with Star Fleet equipment
Commander: Local Force Supply
(CAPT) and supplies
 Engineer ways to refit Local Force vessels with
Star Fleet equipment
 Maintains a close relationship with the
assigned Local Force
Captain  Work within the Local Force command
Local Force Liaison Officer
(CAPT) structure
 Evaluate the current readiness of the assigned
Local Force

VOLUME II
DEPUTY CHIEF: STAR FLEET INTELLIGENCE
The Deputy Chief: Star Fleet Intelligence (CINT) is the senior officer in command of
all activities regarding the gathering, analysis and dissemination of intelligence obtained by
Star Fleet in accordance with ARTICLE 8 of the Star Fleet Charter. The Deputy Chief:
Star Fleet Intelligence is the senior officer in command of the Star Fleet Intelligence
(ICOR) subdivision, which is the sole and central authority for the gathering and analysis
of all intelligence within Star Fleet, and is directly responsible to the Chief of Star Fleet
Operations and the Director: Star Fleet Command for:
 The gathering and analysis of intelligence and other such security information
 Issuing intelligence briefs and making recommendations based upon the results of the
analysis of gathered intelligence
 Performing such missions and operations as the intelligence, The Federation Council
President and the Federation Joint Chiefs of Staff directs
 Maintaining close contact with the other intelligence agencies throughout the
Federation
 The training of Star Fleet intelligence personnel and operatives
The CINT is an officer of the line (SFC) junior to the CSFO, and will typically have the
rank of Vice Admiral. Under the CINT are the various commanders of the offices and
sections necessary to carry out the duties and responsibilities of Star Fleet Intelligence,
as illustrated in Figure 2a22.5. These are listed in the table below:

 Manage the Star Fleet Clandestine Service
Rear Admiral  Plan and monitor intelligence operations
Commander: Intelligence Operations
(RADM)  Execute the Star Fleet Intelligence Plan
 Perform various forms of surveillance
 Analyze and track the intelligence information
Commodore gathered
Commander: Intelligence Analysis
(COMO)  Decipher foreign codes and messages
 Prepare daily intelligence briefings
 Recruit qualified personnel into the intelligence
Commodore
Commander: Intelligence Personnel program
(COMO)
 Train personnel in intelligence methods
 Maintain a liaison with other Federation
intelligence agencies
Captain
Command Intelligence Coordinator  Maintain the Central Intelligence Databank
(CAPT)
 Coordinate intelligence information and
methods with all other Federation agencies
 Analyze and reverse engineer captured
Commodore equipment
Commander: Intelligence Technology
(COMO)  Develop special equipment for field operatives
 Maintain the Fleet Intelligence Control System

VOLUME II
COMMANDER: SPACE EXPLORATION
The Commander: Space Exploration (COMFLTEXP) is the senior officer in command

of all activities regarding the exploration and mapping of space outside the Federation by
Star Fleet as specified in accordance with ARTICLE 6 of the Star Fleet Charter. The
Commander: Space Exploration is the senior officer in command of the Star Fleet
Space Exploration Command (XCOM) and is directly responsible to the Chief of Star
Fleet Operations for:
• The assignment of Star Fleet resources to exploration and mapping activities

• The development of Star Fleet exploration missions outside Federation space
• The determination, assignment and management of Star Fleet expeditions
• The coordination of exploration and survey activities within Federation space with the
Star Fleet Bureau of Federation Space Exploration (BUEXPLOR)
• Developing procedures for the initial contact of new life forms and civilizations
• The training of Star Fleet personnel on first contact procedures
The COMFLTEXP is an officer of the line (SFC) junior to the CSFO, and will typically have
the rank of Rear Admiral. Under the COMFLTEXP are the various commanders of the
offices and sections needed to carry out the duties and responsibilities of the Star Fleet
Space Exploration Command, as illustrated in Figure 2a22.6 and as listed in the table
below:

• Determines areas of space for exploration and
survey activities
Captain • Plans survey and exploration missions
Fleet Exploration Planning Officer
(CAPT) • Works with Star Fleet Strategic Planning and
the Star Fleet Bureau of Federation Space
Exploration
• Selects personnel for specific exploration,
survey and scientific missions
• Assembles exploration and survey teams
Captain • Develops exploration and survey missions
Fleet Exploration Operations Officer
(CAPT) • Develops first contact and other exploration
procedures
• Trains personnel in exploration and contact
procedures
• Determines equipment and material needed
for exploration, survey and other Star Fleet
expeditions
Captain • Allocates equipment and material resources for
Fleet Exploration Supply Officer
(CAPT) surveys and expeditions
• Schedules expedition replenishments
• Purchases scientific equipment and living
supplies for expeditions
• In command of the Star Fleet Exploration Fleet
• Manages all Star Fleet survey and laboratory
Commodore
Commander: Exploration Fleet ships
(COMO)
• Assigns vessels to scientific and exploration
missions, as well as to other such expeditions

VOLUME II
COMMANDER: FLEET LOGISTICS
The Commander: Fleet Logistics (COMFLTSUP) is the senior officer in command of all
activities regarding the supply and replenishment of the Operating Forces and Shore
Establishments of Star Fleet. The Commander: Fleet Logistics is the senior officer
in command of the Star Fleet Office of Fleet Logistics (FLTSUP) and is directly
responsible to the Chief of Star Fleet Operations for:
• Scheduling ship and base replenishments

• Supplying the fleet with its logistical needs and requirements
• Keeping the CSFO and the CMAT informed on the material needs of the Operating
Forces
• Allocating and storing the material needs of the fleet
• Maintaining the fleet budget
The COMFLTSUP is an officer of the Supply Corps (SUP) junior to the CSFO, and will
typically have the rank of Rear Admiral. Under the COMFLTSUP are the various officers
in charge of the sections needed to carry out the duties and responsibilities of Star Fleet
Office of Fleet Logistics, as illustrated in Figure 2a22.7. These are listed in the table
below:

• Gathers fleet logistical requirements
• Maintains plans for fleet replenishment
Captain • Performs long-range logistical projections
Logistical Planning Officer
(CAPT) • Determines fleet budgetary needs
• Manages the fleet budget
• Maintains accounting of fleet expenditures
• Allocates materials and supplies for Star Fleet
Commander: Fleet Supplies & Commodore ships, bases and stations
Materials (COMO) • Works with the Star Fleet Supply Command in
the allocation of fleet material needs
• Schedules ship and base replenishments
Captain
Commander: Fleet Supply Operations • Works with the Star Fleet Transportation
(CAPT)
Command in the scheduling of replenishments

VOLUME II
COMMANDER: FLEET COMMUNICATIONS
The Commander: Fleet Communications (COMFLTCOMM), also known as the “Fleet

Communications Director,” is the senior officer in command of all activities regarding
the communications with and for the Operating Forces and Shore Establishment of
Star Fleet. The Commander: Fleet Communications is the senior officer in command
of the Star Fleet Office of Fleet Communications (FLTCOMM) and is responsible to
the Chief of Star Fleet Operations for:
• Communicating with all the Operating Forces and Shore Establishments

• Providing and maintaining reliable, secure and rapid communications for the entire
Star Fleet in peace time or war
• Establishing the security and cryptographic communications protocols and subspace
frequencies to be used throughout Star Fleet
• Supplying the fleet with communications equipment and services
• Maintaining the fleet communications relay stations and the entire Star Fleet
communications network
The COMFLTCOMM is an officer of the line (SFC) junior to the CSFO, and will typically
have the rank of Rear Admiral. Under the COMFLTCOMM are the various officers in
charge of the sections needed to carry out the duties and responsibilities of Star Fleet
Office of Fleet Communications, as illustrated in Figure 2a22.8. These are listed in the
table below:

• Establishing the various fleet communications
frequencies and channels
Captain • Establishes the standards for fleet
Communications Standards Officer
(CAPT) communications protocols and procedures
• Creates the fleet alert codes and cryptographic
methods
• Supplying the fleet with communications
equipment
Captain
Communications Equipment Officer • Maintaining fleet communications equipment
(CAPT)
• Maintains the fleet communications relay
stations
• Communicating with the Operating Forces and
Shore Establishments
• Training of fleet communications personnel
• Determines locations of fleet communications
Commodore
Star Fleet Communicator relay stations
(COMO)
• Determines and sets secure communications
channels
• Determines and sets current classified
communications codes
• Performs the coding and decoding of fleet
Captain
Fleet Cryptographic Officer messages
(CAPT)
• Interacts with Star Fleet Intelligence

VOLUME II
COMMANDER: TACTICAL OPERATIONS
The Commander: Tactical Operations (COMTAC) is the senior officer in command of

establishing, creating and maintaining all strategic and tactical operations and maneuvers
for the Operating Forces of Star Fleet. The Commander: Tactical Operations is the
senior officer in charge of the Star Fleet Office of Strategic and Tactical Operations
(TAC) and is directly responsible to the Chief of Star Fleet Operations for:
• Developing the methods and procedures for all military operations for the Operating
Forces and Shore Establishments
• Developing peacetime and wartime strategies
• Developing tactical military operations related to the use of Star Fleet assets
• Training the Operating Forces on strategy and tactical maneuvers
The COMTAC is an officer of the line (SFC) junior to the CSFO, and will typically have the
rank of Rear Admiral. Under the COMTAC are the various officers in charge of the
offices and sections needed to carry out the duties and responsibilities of Star Fleet
Office of Strategic and Tactical Operations, as illustrated in Figure 2a22.9. These are
listed in the table below:

• Developing the strategies and tactics to be
used by Star Fleet
Commodore • Developing the methods and procedures for
Chief Star Fleet Strategist
(COMO) military operations
• Developing both peacetime and wartime
strategies
• Test strategic and tactical theories and
procedures using upon computer models
Captain
Tactical Simulations Officer • Develop the tactical and strategic computer
(CAPT)
simulation models and scenarios
• Maintain the simulation computers
• Train Star Fleet Commanders and other
Captain personnel in Star Fleet strategies and tactics
OINC: Tactical Training
(CAPT) • Test personnel on the use of strategies and
tactics
• Analyze the combat tactics employed by alien
Captain
Alien Tactics Officer or foreign forces
(CAPT)
• Develop methods to counter alien tactics

VOLUME II
Figure 2a22.1
OFFICE OF THE OPERATIONS CHIEF OF STAFF
OPSOS
Operations
Chief of Staff
VADM
OPSADJ OPSADM
Operations Command
Staff Adjutant Yeoman
COMO T5
OPLAN OPREQ OPRED OPSRV

Fleet Planning Fleet Requirements Fleet Readiness Fleet Services
CAPT CAPT CAPT CAPT

VOLUME II
Figure 2a22.2
DEPUTY CHIEF: STAR SHIP COMMAND
CSSC
Deputy Chief:
Star Ship Command
VADM
SSCADM
Administrative
Assistant
T5
SSCOS
Star Ship Command
Chief of Staff
RADM
COMSHIPPER Commander: COMSHIPOPS Commander: COMSHIPSUP Commander: COMSHIPPLN Commander:

Star Fleet Ship Star Fleet Ship Star Fleet Ship Star Fleet Ship
COMO Personnel RADM Operations COMO Logistics CAPT Planning
COMSHIPSRV Commander: COMCRAFT Commander:

Star Fleet Ship Star Fleet
CAPT Services RADM Service Craft

VOLUME II
Figure 2a22.3
DEPUTY CHIEF: STAR BASE COMMAND
CSBC
Deputy Chief:
Star Base Command
VADM
SBCADM
Administrative
T5
Assistant
SBCOS
Star Base Command
Chief of Staff
RADM
COMBASPER Commander: COMBASOPS Commander: COMBASMAT Commander: COMBASREQ Commander:

Star Fleet Base Star Fleet Base Star Fleet Base Star Fleet Base
COMO Personnel RADM Operations COMO Logistics CAPT Requirements
COMBASFAC Commander: COMBASSEC Commander:

Star Fleet Base Star Fleet Base
CAPT Facilities CAPT Security

VOLUME II
Figure 2a22.4
CFOR
Deputy Chief:
Adjunct Forces
VADM
FORADM
Administrative
Assistant
T5
FOROS
Adjunct Force
Chief of Staff
RADM
COMFORPLN Commander: COMFOROPS Commander: COMFORTRN Commander: COMFORSUP Commander:

Local Force Local Force Local Force Local Force
CAPT Planning CAPT Readiness CAPT Training CAPT Supply
FORCEREP
Local Force
Liaison Officer
CAPT

VOLUME II
Figure 2a22.5
DEPUTY CHIEF: STAR FLEET INTELLIGENCE
CINT
Deputy Chief:
VADM
INTADM
Administrative
Assistant
T5
INTOS
Intelligence
Chief of Staff
RADM
COMINTOPS Commander: COMINTANL Commander: COMINTPER Commander: COMINTOPS Star Fleet

Intelligence Intelligence Intelligence Intelligence
COMO Operations CAPT Analysis COMO Personnel CAPT Coordinator
COMINTTEK Commander:
Intelligence
CAPT Technology

VOLUME II
Figure 2a22.6
COMMANDER: SPACE EXPLORATION
COMFLTEXP
Commander:
Space Exploration
RADM
EXPADM
Administrative
Assistant
T5
EXPCOS
Space Exploration
Chief of Staff
COMO
FLTEXPPLN FLTEXPOPS FLTEXPSUP COMEXPFLT

Fleet Exploration Fleet Exploration Fleet Exploration Commander:
Planning Officer Operations Officer Supply Officer Exploration Fleet
CAPT CAPT CAPT COMO

VOLUME II
Figure 2a22.7
COMMANDER: FLEET LOGISTICS
COMFLTSUP
Commander:
Fleet Logistics
RADM
FLTSUPADM
Administrative
Assistant
T5
FLTSUPOS
Fleet Supply
Chief of Staff
COMO
FLTSUPPLN Logistical FLTSUPMAT Commander: FLTSUPOPS Commander:

Planning Fleet Supplies and Fleet Supply
CAPT Officer COMO Materials CAPT Operations

VOLUME II
Figure 2a22.8
COMMANDER: FLEET COMMUNICATIONS
COMFLTCOMM
Commander:
Fleet Communications
RADM
FLTCOMADM
Administrative
Assistant
T5
FLTCOMOS
Fleet Communications
Chief of Staff
COMO
FLTCOMSTD Communications FLTCOMMAT Communications FLTCOMM FLTCRYPTO

Star Fleet Fleet Cryptographic
Standards Equipment
Communicator Officer
CAPT Officer CAPT Officer COMO CAPT

VOLUME II
Figure 2a22.9
COMMANDER: TACTICAL OPERATIONS
COMFLTTAC
Commander:
Tactical Operations
RADM
FLTTACADM
Administrative
Assistant
T5
FLTTACOS
Tactical Operations
Chief of Staff
COMO
FLTSTRAT FLTTACSIM Tactical FLTTACTRN Officer in Charge: FLTTACALN

Chief Star Fleet
Simulations Tactical Alien Tactics Officer
Strategist
COMO CAPT Officer CAPT Training CAPT

VOLUME II

VOLUME II
2.3 SECTOR COMMANDANTS

Each of the eight Federation octants and the Federation Treaty Zone is commanded
by a Sector Commandant with the rank of Admiral who reports directly to the Chief of
Star Fleet Operations as specified in ARTICLE 45 of the Star Fleet Charter and in
Star Fleet Regulation 3400. Therefore, there are nine such Sector Commandants in
the entire Star Fleet. These commanders have a great responsibility since they are in
command of all Star Fleet forces and facilities within a volume of space equivalent to
about 161,000 cubic parsecs. Therefore, the function of this section is to describe the
organizational structure for the office of the Sector Commandant.
The Sector Commandant is an officer of the line (SFC) with the rank of Admiral and
has the title of “Commandant: Federation Sector <n>” or COMSEC<n>, where the
number <n> corresponding to the octant number. However, the exception to this rule is
the Sector Commandant for the Federation Treaty Zone who will have the title of
“Commandant: Federation Treaty Zone” and will have a designation of COMSEC0.
The term Sector Commandant is used for this position since this officer is in command
of all the sectors within the assigned octant, and since the term octant is not an official
standard, the term sector is used instead.
The Sector Commandant is the chief commander within an octant and is in command of
all the forces assigned to his or her octant. The Sector Commandant reports directly to
the Chief of Star Fleet Operations on all matters pertaining to his or her octant. As
such, the Sector Commandant is the most senior officer in that volume of space and has
precedence over all Star Fleet base and station commanders, over all troops and Fleet
Marine forces, and over the Fleet Commander assigned to that sector as well. The
location of the office of the Sector Commandant will always be the Sector Base for
that octant, the selection of which is completely up to him or her.
Sector Commandants are selected by the Chief of Star Fleet Operations with the
approval of the Director: Star Fleet Command. Typically, Sector Commandants are
usually either former Starbase or Fleet Commanders, depending on where they stand
in the lineal list of flag officers.
AUTHORITY
The authority of the Sector Commandant is explicitly described in ARTICLE 45 of the

Star Fleet Charter, which states: “The Sector Commandant shall be the central operating
authority over all the Star Fleet forces, bases and stations assigned to that volume of
space, and shall report directly to the Chief of Star Fleet Operations on all matters
pertaining thereto.” As such, the Sector Commandant is the principal Commander in
Chief of all Star Fleet forces within his assigned volume of space.
As the Commander in Chief of his or her assigned octant, the Sector Commandant
has precedence over any commander of a Local Force that is operating outside the
boundaries of their system as specified in ARTICLE 15 of the Star Fleet Charter. The
Sector Commandant, however, does not have authority over any member Local Force
while they function within the boundaries of their own system as specified in ARTICLE 14
of the Charter.

VOLUME II
OFFICE OF THE SECTOR COMMANDANT
The Office of the Sector Commandant is essentially the administrative command

structure for the management of the octant to which the Sector Commandant has
command. All orders and directives issued by Star Fleet Command will be sent to the
Office of the Sector Commandant for dissemination to the forces within the octant.
The office itself is physically located on the Sector Base within the octant the Sector
Commandant is assigned, and acts as the command center for the entire octant within
the Federation Exploration Zone. Sector Bases will be further discussed in Section
7.5 of this volume. Figure 2a23.1 illustrates the command organization of the Office of
the Sector Commandant. In terms of the administration of the octant, the Office of
the Sector Commandant contains:
 The Sector Representative

 The Sector Magistrate
 The Regional Judge Advocate
 The Sector Federation Consul
 The Sector Chief of Staff
SECTOR REPRESENTATIVE
The Sector Representative is the chief liaison to member and non-member worlds of
the Federation and represents Star Fleet in all matters pertaining to its consular role in
that octant. The Sector Representative (SECREP) is also the senior officer in charge of
all Fleet Representatives (FLTREP) that may be assigned to commands within the
octant. Sector Representatives are assigned to octants by the Star Fleet Bureau of
Consular Affairs (BUCONAF) and will typically be a Captain from the Diplomatic
Corps. The Sector Representative reports directly to the Sector Commandant
concerning consular activities within the octant, and will keep the Sector Commandant
informed of any changes relating to the treaties and agreements between the Federation
and the local governments contained within the octant.
SECTOR MAGISTRATE
ARTICLE 28 of the Star Fleet Charter authorizes Star Fleet to establish courts, in
compliance with ARTICLE 95 of the Articles of Federation, for the adjudication of cases,
and to make summary judgments on infractions of Federation law in deep space. Such
courts are typically located on Starbases and on some of the larger Star Fleet Stations.
Sitting in judgment of such cases a Star Fleet Magistrate from the Star Fleet Bureau
of Courts will be assigned to sit on the bench. To manage all the Star Fleet magistrates
and courts within an octant, a Sector Magistrate is assigned by the Office of the Star
Fleet Judge Advocate General to perform this function.
The Sector Magistrate will be an officer of the Judicial Corps (JUD), usually with the
rank of Commodore, who reports directly to the Director: Star Fleet Command, but
will also indirectly report to the Sector Commandant regarding the legal proceedings
that occur within the octant. Primarily, the Sector Magistrate will make reports to the
Sector Commandant regarding the number and types of cases adjudicated within the
octant, and to keep the Sector Commandant informed of any changes in local laws and
legal precedence.

VOLUME II
REGIONAL JUDGE ADVOCATE
Every major Star Fleet base and space station will contain a local office of the Judge
Advocate General with a significant staff of Fleet Judge Advocates. Such base offices
will be part of the judicial complex for the base and will provide the full range of legal
services to Service members. Most of the larger Star Fleet space stations may contain a
smaller legal office. Usually, these station offices will contain a staff of about six Judge
Advocates and enlisted legal assistants. These smaller offices can provide most of the
more private legal services such as drawing up wills, etc. However, these smaller offices
may not have the staff or resources to perform defense counsel duties. In such cases,
lawyers and Judge Advocates must be brought in. Small stations such as Star Fleet
outposts are too small to contain a permanent legal staff. In charge of these local offices
will be an officer of the Judge Advocate General's office with the title of Regional
Judge Advocate or Space Sector Judge Advocate.
The Regional Judge Advocate will be an officer of the Judicial Corps (JUD), usually
with the rank of Captain, who reports directly to the Star Fleet Judge Advocate
General, but will also indirectly report to the Sector Commandant regarding the trials
and other legal matters that occur within the octant. Primarily, the Regional Judge
Advocate will make reports to the Sector Commandant regarding the types of legal
cases, legal proceedings, trials and court-martials that occurred in the octant, and to keep
the Sector Commandant informed of any changes in local laws and legal precedence.
On the other hand, a Space Sector Judge Advocate will generally report to a Regional
Judge Advocate.
SECTOR FEDERATION CONSUL
The Sector Federation Consul (FEDADM) is the primary civilian ambassador to the
various Federation and foreign governments within or adjacent to the sector, and acts as
council to the Sector Commandant on the matters pertaining thereto. FEDADM is a
person with extensive knowledge of the laws, treaties and agreements with the worlds
within the sector and of the foreign worlds outside the Federation, and is well versed in
the political processes of the worlds contained within the octant. In addition, the FEDADM
will work with Federation and foreign ambassadors and diplomatic personnel during
peace negotiations within and external to the Federation.
The Sector Federation Consul reports directly to the Star Fleet Consul General
(SFCCG) and as such, will have direct access to the Director: Star Fleet Command.
The FEDADM acts as a counselor to the Sector Commandant, but does not come under
direction of the COMSEC. In addition, the FEDADM has the authority to attend meetings,
negotiations or other conferences with foreign and domestic officials involving Star Fleet
Representatives or Star Fleet Commanders at any time.

VOLUME II
SECTOR COMMANDANT’S FLAG
All Sector Commandants are allowed to fly a personal flag in accordance with ARTICLE
48 of the Star Fleet Charter. The flag is a rectangle with the dimensions 168 cm long by
94 cm wide. The number of the octant the Sector Commandant is in command of is
prominently displayed in the center of a blue field with a gold border. At the corners are
four white stars indicating the rank of the COMSEC to be a full Admiral as stipulated by
Star Fleet Standards and as illustrated below:
SECTOR COMMANDANT’S BADGE
The Office of Sector Commandant is indicated by the special badge worn only by the
Sector Commandant. The following is the badge for a Sector Commandant, which
may be worn on all uniforms.

VOLUME II
SECTOR CHIEF OF STAFF
The Sector Chief of Staff is the “Executive Officer” to the Sector Commandant and as
such, has much the same authority and precedence as the Sector Commandant. The
basic function of the Sector Chief of Staff is to supervise and coordinate the work of the
staff assigned to the Sector Commandant. The SECOS is an officer junior to the Sector
Commandant and will typically have the rank of Vice Admiral (SFC).
The organizational structure for the SECOS is illustrated in Figure 2a23.2. The persons
that come under direct authority of the SECOS are the various operations specialists
assigned to the Sector Commandant as listed in Table 2a23.1 below. The SECOS has
assigned to him the Sector Adjutant (SECADJ) to aid in the administration and
discipline of the staff members under him. Typically a line officer with the rank of Rear
Admiral, the SECADJ will ensure that the individuals under the direction of the SECOS
perform their duties.
Table 2a23.1
STAFF TO THE SECTOR COMMANDANT
Office Title/Designation/Billet Rank Duties and Responsibilities
 Interface with Local Federation government
Commander: System Liaison
Captain forces
(COMSECCON <n>)
[29<n>2]
(CAPT)  Issue reports relating to the state of affairs of
the systems located within the octant
 Evaluate the readiness of the Local Forces in
Commander: Sector Forces
Captain the octant
(COMSECFOR<n>)
[29<n>3]
(CAPT)  Create training and other operational plans
with the Local Forces
 Establish operational plans and to coordinate
Commander: Sector Operations
Commodore such plans with the Star Fleet Office of
(COMSECOPS <n>)
(COMO) Strategic and Tactical Operations
[29<n>4]
 Issue the operational orders and directives
Commander: Sector Intelligence  Collect intelligence from the forces
Captain
(COMSECINT <n>)
(CAPT)  Coordinate with Star Fleet Intelligence
[29<n>5]
 Manage the communications network for the
Commander: Sector Communications octant
Captain
(COMSECCOM <n>)  Send and receive all operational messages
(CAPT)
[29<n>6]  Set the communications codes for coded
messages
 Plan and manage the supply needs for the
forces in the octant
Commander: Sector Logistics
Captain  Consolidate the various logistics needs of the
(COMSECSUP <n>)
(CAPT) forces and facilities within the octant
[29<n>7]
 Work with the Star Fleet Supply Command to
allocate the required supplies
 Plan and manage exploration and expedition
Commander: Sector Exploration
Captain activities in or around the octant
(COMSECEXP<n>)
[29<n>8]
(CAPT)  Plan and schedule replenishments to Star
Fleet and Federation colonies and settlements
 Develop strategies and tactics to be employed
Sector Tactical Officer
Commander by the forces in the octant
(COMSECTAC<n>)
[29<n>9]
(CMDR)  Develop training scenarios that can be
exercised by the forces within the octant

VOLUME II
COMMANDER: SECTOR FLEET MARINE FORCES
The Commander: Sector Fleet Marine Forces is the Commander in Chief of all Star
Fleet Ground Forces within the octant. In terms of the Chain of Command, the
Commander: Sector Fleet Marine Forces reports directly to the Commandant: Star
Fleet Marine Corps through the Sector Commandant of the octant his force has been
deployed. Therefore, ground force operational orders come directly from Star Fleet
Command to the Commander: Sector Fleet Marine Forces, either directly from the
Commandant: Star Fleet Marine Corps, the Chief of Star Fleet Operations or
through the Sector Commandant.
The commander of the octant’s ground force will typically be a line officer from the Fleet
Marine Corps (MMC) with the rank of Vice Admiral, and will have the title of
“Commander: Sector Fleet Marine Forces <n>” or COMFOR <n>.
FLEET COMMANDER
Each octant will have a fleet of ships assigned to it which will comprise the Operating
Forces for that octant. The fleet assigned to the octant of the Sector Commandant is
commanded by a Fleet Commander who is the senior officer of the fleet and will have
precedence over all the personnel within his assigned fleet. Although under the authority
of the Sector Commandant, the Fleet Commander does not directly report to the
Sector Commandant, but directly to the Chief of Star Fleet Operations through the
Sector Commandant. As such, fleet operational orders come directly from Star Fleet
Command to the Fleet Commander, either directly from the Chief of Star Fleet
Operations or through the Sector Commandant. A more detailed description of the
Fleet Commander may be found in Section 2.4 of this chapter.
SECTOR BASE COORDINATOR
Octants contain many Star Fleet bases and stations spread out through its volume. To
coordinate the operations of bases within an octant a Sector Base Coordinator will be
assigned by Star Base Command. The function of the Sector Base Coordinator is to
coordinate the operations of all the various bases and stations within the octant. The
Sector Base Coordinator will assign operations to bases and stations based upon the
needs of the moment and will balance such operations between the bases and stations. In
addition, the Sector Base Coordinator will also ensure that all bases and stations within
an octant receive the supplies and materials they need to perform their function, and to
set and balance the troop levels of the bases assigned to the octant.
The Sector Base Coordinator will typically be a line officer (SBC) with the rank of Rear
Admiral, and have a title of “Commander: Sector Bases <n>” or COMSECBAS <n>.
The Sector Base Coordinator essentially reports to both Star base Command and the
Sector Commandant on matters relating to the operations and missions of Star Fleet
bases and stations. The organization chart for this office is illustrated in Figure 2a23.3.

VOLUME II
REGIONAL AND AREA COMMANDERS
To aid the Sector Commandant in the management of his forces throughout the octant,
Regional, Sector or Area Commanders are designated and assigned to sectors or
regions of space within the octant. The terms Regional Commander and Area
Commander are not formal titles, but defined as the “Senior Officer Present” of a
specified area or region of space in accordance with Star Fleet Regulation 6110.
Regional Commanders are normally the “Senior Officer Present” of the volume of space
surrounding a Star Fleet Headquarters facility or around a System Base. Specifically,
commanders of Star Fleet Headquarters have the title of District Commander and
are located primarily within the Federation Treaty Zone and as such, will report directly
to the Commander: Federation Treaty Zone.
As a rule, the commander of a System Base located within an octant of the Federation
Exploration Zone will be designated as the Regional Commander of the volume of
space encompassing the base. System Bases or System Starbases are large facilities
built on worlds that are members of the Federation and are also known as Regional
Star Fleet Headquarters. Besides serving as fleet command centers, they also act as a
liaison between member systems and Star Fleet, serve as major training centers, and as
command and control centers with Local Forces.
An Area Commander, on the other hand, is generally defined as the “Senior Officer
Present” of an area of space and is the senior officer of all the forces within that sector,
area or region of space. This includes any Star Fleet ships that may be operating within
this area. As such, all operational orders to the forces within the area originate from the
Area Commander. However, such Area Commanders do not, on their own, initiate
operations for the Starships that happen to be in the area, but merely relay command
orders from higher authority. However, they do have direct authority over all ground
troops located within their jurisdiction.
The above command authority will typically be conferred upon the local Starbase or Star
Fleet Station Commander. Where there may be more than one base or station within
the grouped region, one of the bases will be designated as the Area Base or Regional
Command Center. As such, the commander of the Area Base will be the senior officer
of the region and will report directly to the Sector Commandant through the Sector
Base Coordinator.
The volume of space commanded by the Area Commander may contain other smaller
stations. The Commanding Officers of these stations will come under direct authority of
the Area Commander. These smaller stations have their own jurisdictional authority or
“Sphere of Influence”. Jurisdictional Authority is defined as the volume of space
around the station where the Commanding Officer of the station is the “Senior Officer
Present” and has absolute command authority. All vessels, whether they are private,
commercial or Star Fleet, come under the direct authority of the Station Commander.
In addition, Starships also have their own “Sphere of Influence” as well, which will
typically be the ship’s patrol zone. At the outer rim of Federation space a Starship
commander is the Area Commander and has Jurisdictional Authority over all
persons, vessels, and activities within his patrol zone.

VOLUME II
SELECTION OF SECTOR COMMANDANTS
The Chief of Star Fleet Operations will generally make the selection and assignment of
Sector Commandants to Federation octants, unless otherwise directed by the
Director: Star Fleet Command. The general rule is to have the CSFO make the
selection and then submit the selection to the Star Fleet Bureau of Personnel for
review by the Flag Officers Review Board. The board will review the selection and
make its recommendation for approval or may select their own Sector Commandant,
subject to the approval of the CSFO.
The duration of the assignment is completely up to the CSFO, and there is no time limit
associated with this assignment. The CSFO will evaluate the performance of all Sector
Commandants on a yearly basis, and will decide if a replacement is necessary or desired.
SUCCESSION
In accordance with Star Fleet Regulation 5950, the Sector Commandant may
prescribe the order of succession to his command. Typically, this order of succession is
created when the commander assumes the title of Sector Commandant. However, if no
order of succession is prescribed, the Sector Chief of Staff will, unless otherwise
directed by the Chief of Star Fleet Operations or the Director: Star Fleet Command,
temporarily perform the duties of the Sector Commandant during his absence, or
disability, or in the event of a temporary vacancy in that office until the Chief of Star
Fleet Operations appoints a permanent replacement. Should the Sector Chief of Staff
become unable to fulfill the duties of the Sector Commandant, the CSFO will select a
commander from one of the other operational units within the Department.

VOLUME II
Figure 2a23.1
SECTOR COMMANDANT ORGANIZATION
COMSEC
Sector
Commandant
ADML
SECLT SECSX
Flag Flag
Lieutenant Secretary
CMDR LCDR
SECREP SECADM
Sector Flag
Representative Yeoman
CAPT T5
FEDADM SECJUD
Sector Sector
Federation Consul Magistrate
CIVILIAN COMO
SECOS
Sector
Chief of Staff
VADM
SECADJ
Sector
Adjutant
RADM
COMFLT COMFOR Commander: SECOS Sector COMSECBAS

Fleet Sector Base
Sector Fleet Marine Administration
Commander Coordinator
VADM VADM Forces (Direct Reports)
* RADM

VOLUME II
Figure 2a23.2
SECTOR CHIEF OF STAFF
SECOS
Sector
Chief of Staff
VADM
SECADJ SECOSADM
Sector Administrative
Adjutant Assistant
RADM T5
COMSECCON COMSECFOR COMSECOPS COMSECINT

Commander: Commander: Commander: Commander:
System Liaison Sector Forces Sector Operations Sector Intelligence
CAPT CAPT COMO CAPT
COMSECCOM COMSECSUP COMSECEXP COMSECTAC

Commander: Sector Commander: Commander:
Sector Tactical Officer
Communications Sector Logistics Sector Exploration
CAPT CAPT CAPT CMDR

VOLUME II
Figure 2a23.3
SECTOR BASE COORDINATOR
COMSECBAS
Sector
Base Coordinator
RADM
SECADJ SECBASADM
Sector Administrative
Adjutant Assistant
COMO T4
COMSECBASOPS Commander: COMSECBASSUP Commander: COMSECBASFOR Commander:

Sector Base Sector Base Sector Base
COMO Operations CAPT Materiel CAPT Forces

VOLUME II

VOLUME II
2.4 FLEET COMMANDERS

Outside the Federation Treaty Zone and throughout the remaining parts of Federation
space are distributed the eight Fleets that comprise the bulk of the Operating Forces of
the Star Fleet. Each fleet is assigned to one of the eight primary octants which divides
the Federation Exploration Zone, and are numbered respectively: 1st Fleet, 2nd Fleet,
..., 8th Fleet. Each fleet is commanded by a Fleet Commander, once known as a Fleet
Captain during the period of the early Confederation. In this section the commanders of
fleets will be described as well as the commanders of the various units that are under the
command of a Fleet Commander, or that comprise an independent unit of Star Fleet
ships. In addition, the internal organizational structure of a typical Fleet Commander, as
illustrated in Figure 2a24.1, will also be discussed, as well as the role of each member of
the fleet command staff.
A Fleet Commander will be an officer of the line (SSC) with the rank of Vice Admiral,
and will have the title of “Commander: <nth> Fleet” with a moniker of COMFLT<n>;
where <n> corresponds to the number of the octant in which the fleet was originally
created. For example, Commander: 3rd Fleet will be designated COMFLT3. In general,
Fleet Commanders typically come from the ranks of Starship commanders and those
commanding units of Star Fleet ships.
Succinctly, the Fleet Commander is the senior officer in command of all the ships and
forces assigned to his or her fleet and will have precedence over all personnel within his
assigned fleet. Although the Fleet Commander is in command of the fleet as a whole, he
will leave the operating routine of the units under his command to the individual unit
commanders. Fleet Commanders generally do not micromanage the internal operations
of any unit under their command. In terms of the Star Fleet Chain of Command, the
Fleet Commander reports directly to the Chief of Star Fleet Operations through the
Sector Commandant of the octant to which his fleet has been deployed. Therefore, fleet
operational orders come directly from Star Fleet Command to the Fleet Commander,
either directly from the Chief of Star Fleet Operations or through the Sector
Commandant.
Usually, the Fleet Commander will be stationed at the same base or location as the
Sector Commandant. Together, they represent force operations for the octant of space
assigned to them. The Fleet Commander will also work with the sector Fleet Marine
Commander regarding any operation by the Fleet Marine Corps that may require
assistance from the fleet. Such support may include transportation of ground forces as well
as fire support from Star Fleet ships.
For some of the more specialized functions of fleet command the Fleet Commander will
delegate some of those responsibilities to subordinate officers with the necessary
specialized skills. These subordinate officers comprise the Fleet Commander’s staff, and
the function of managing this staff will rest with the Fleet Chief of Staff.

VOLUME II
AUTHORITY
The authority of the Fleet Commander is explicitly stated in ARTICLE 62 of the Star
Fleet Charter, which states: “A Fleet shall be assigned, and so numbered, to each
primary division of Federation space. Therefore, there shall be established eight primary
Fleets distributed throughout the eight octants of the Federation. Each fleet shall be under
the command of a "Fleet Commander" and shall be responsible to the Chief of Star Fleet
Operations through the Sector Commandant.”
FLEET COMMANDER’S FLAG
All Fleet Commanders are allowed fly a personal flag in accordance with ARTICLE 48 of
the Star Fleet Charter. The flag is a rectangle with the dimensions 132 cm long by 94
cm wide with the symbol of Star Ship Command and the title of the Fleet Command
placed in the center of a blue field with a gold border as illustrated below. This particular
flag indicates that the Fleet Commander has the rank of Vice Admiral.
FLEET COMMANDER’S PIN
All Fleet Commanders are allowed to wear a Commander's Pin. The Commander's
Pin is a device worn only by officers holding the position of Commander of a large unit,
such as a fleet. The pin is required only for the Formal Dress Blue uniform and optional
on the Ceremonial Dress White and Service Dress uniforms.
FLEET CHIEF OF STAFF
The function of the Fleet Chief of Staff is to manage the operations staff of the Fleet
Commander, and is also the Executive Officer for the Fleet Commander and will
have the title of Chief of Staff: <nth> Fleet. As such, orders from the Fleet Chief of
Staff carry the same weight as those issued by the Fleet Commander.

VOLUME II
FLEET COMMAND STAFF
The fleet command staff is composed of those specialists that aid the Fleet Commander
in the management and command of his particular fleet. The Fleet Commander will
delegate certain responsibilities to these individuals regarding specific fleet management
functions. The following table lists the staff members within a standard fleet command
structure, which will be under direct authority of the Fleet Chief of Staff.
Table 2a24.1
FLEET COMMAND STAFF MEMBERS
 Personal assistant to the Fleet Commander
Lt. Commander
Flag Lieutenant  Acts as liaison to civilian and government
(LCDR)
authorities
Lieutenant  Personal aide to the Fleet Commander
Flag Secretary
(LEUT)  In charge of all Flag Yeomen
 Manages the operations assigned to the fleet
Captain
Fleet Operations Officer  Organizes the fleet into operational units
(CAPT)
 Assigns forces, groups and ships to missions
Commander  Manages the intelligence gathered by the forces
Fleet Intelligence Officer
(CMDR) within the fleet
 Ensures the fleet is properly supplied
Commander
Fleet Logistics Officer  Arranges for supply rendezvous to the fleet
(CMDR)
 Maintains logistical requirements for the fleet
Commander  Sends operational orders to the fleet
Fleet Communications Officer
(CMDR)  Sets the cryptographic codes to the fleet
Commander  Responsible for fleet security
Fleet Security Officer
(CMDR)  Commands the fleet security forces
ASSIGNMENT OF SUBCOMMANDS
Fleets may be divided into one or more subcommands or subdivisions, the organization of
which will be up to the Fleet Commander as permissible under Star Fleet Regulation
3300. The following subsections will describe the various subcommand types a Fleet
Commander may organize his forces into as permitted under Star Fleet Regulation
5710.
TYPE COMMANDERS
A Type Commander, as it relates to the fleet, is a generalized term for an officer who
commands a group of ships of the same type. Typically, a Type Commander may be
established for such groupings of ships such as a Division, Squadron or Flotilla of the
same class. For example, a commander of all the support ships in the Third Fleet is
designated Commander: Fleet Support, Third Fleet or COMFLTSUP3. As such, a
Type Commander will be responsible for the readiness, equipment, organization, and
staffing of the ships under his command. The typical command structure for a Fleet
Support Commander may be found in Figure 2a24.4.

VOLUME II
GROUP COMMANDERS
At times the Fleet Commander may organize his forces into special Task Commands or
Task Groups. A Task Group is a temporary assemblage of ships in order to perform a
specific mission. When such groups are formed, the Fleet Commander will assign a
Group Commander to lead the force with a title of “Commander: Task Group <n>”
or COMTASKGRP <n>, depending on the type of group that was organized. As such,
Group Commanders report directly to the Fleet Commander. The general structure of
a group command is shown in Figure 2a24.2.
In addition, Star Fleet has five permanent Battle Groups that may be assigned to an
octant. When a Battle Group is assigned an octant, the group will be attached to the
fleet assigned to that octant. As such, the Battle Group Commander will report directly
to the Fleet Commander and will receive all orders and directives from him.
SQUADRON COMMANDERS
Each fleet is divided into six primary operating units called Fleet Squadrons, each of
which containing about six line combatants and about 2-3 support vessels. This grouping
of vessels will be under the command of a Squadron Commander, usually with the rank
of Commodore, and will have a designation of “Commander: Fleet Squadron <n>” or
COMFLTRON<n>. Typically, the Commanding Officer of the largest ship within the
squadron – generally a Heavy Cruiser – will become the Squadron Commander. All
other Starship Captains within the squadron will report directly to the Squadron
Commander unless detached to perform a special mission assigned by Star Fleet
Operations. The basic command structure of a squadron is shown in Figure 2a24.3.
Squadron Commanders are usually chosen by the Fleet Commander as permissible

under Star Fleet Regulation 5710. It is the privilege of the Fleet Commander to pick
his or her own Squadron Commanders, if so desired. However, an incoming Fleet
Commander will generally refrain from upsetting the fleet command structure by
selecting new squadron commanders at the onset. Instead, the Fleet Commander will
keep the current command structure intact while evaluating his or her Squadron
Commanders. It should be noted that becoming a Squadron Commander is usually
the first step towards a fleet command.
COMMANDER: SECTOR FLEET MARINE FORCE
Each octant will have several divisions or a corps of Star Fleet Marine troops assigned to
it. The commander of this force is called the Commander: Sector Fleet Marine Forces;
an officer of the line (MMC) who will typically have the rank of Vice Admiral. The Fleet
Commander will work with the Sector Marine Force Commander or COMFOR in
planning operations that require ground forces and will organize the forces necessary to
support the Fleet Marine force in the performance of their mission.
In addition, fleets may also contain Marine Corps forces assigned to the various ships in
the fleet. In overall command of these forces will be the “Commander: Fleet Marine
Force” or COMFLTFOR. This commander reports directly to the Fleet Commander
regarding the stationing of troops onboard the ships within the fleet. The COMFLTFOR is
an officer of the line (MMC) with the rank of Rear Admiral, and will have the title of
“Commander: Fleet Marine Force <n>” or COMFLTFOR <n>.

VOLUME II
FLEET ATTACK SQUADRON COMMANDERS
Fleet Attack Squadrons are assemblages of fighter and attack craft. A typical squadron
will contain ten craft of a particular type (e.g. Fighter, Attack or Interceptor) and are most
likely found on Attack Carriers that make up a Battle Group.
The commanders of such squadrons have designations such as: “Commander: Attack
Squadron <n>” or “Commander: Fighter Squadron <n>”, both having a designation
of COMATSRON <n>. These commanders are typically line officers with the rank of
Commander. In overall command of all the attack squadrons within the fleet is the Fleet
Attack Group Commander. The Fleet Attack Group commander is an officer of the
line (SSC) with the rank of Captain, and will have a title of “Commander: Fleet Attack
Group <n>” or COMATGRP <n>. The command structure for a typical Fleet Attack
Group can be seen in Figure 2a24.5, and the command structure for a typical Fleet
Attack Squadron can be seen in Figure 2a24.6.
RELATIONSHIP WITH FLAGSHIP COMMANDER
Fleet Commanders generally command the fleet from their office at the Sector Base.
However, should the Fleet Commander travel in space, he will normally move his staff to
his Flagship. Typically, when assuming command of the fleet the Fleet Commander will
usually select his or her Flagship to function as his or her mobile office of operation. The
Flagship, generally a Star Fleet Battleship, will contain the offices and spaces needed
to conduct operational business, and will also contain the necessary offices, staterooms
and living quarters for the staff.
While the Fleet Commander is embarked the Commanding Officer of the Flagship is
at all times subject to the orders of the Fleet Commander regarding the operations and
routine of the ship as specified in Star Fleet Regulation 3210. In this particular case,
the Fleet Commander will not be embarked as a passenger of the ship, but will be in
operational command of the ship and of all the ships attached to his command.
In addition, all staff officers and personnel attached to the Fleet Commander and
embarked onboard the Flagship will not be subject to the orders of the Flagship
Commanding Officer as specified in Star Fleet Regulation 5551. The staff of the
Fleet Commander will be at all times under his command.

VOLUME II
SELECTION OF FLEET COMMANDERS
The Chief of Star Fleet Operations generally assigns Fleet Commanders to fleet
units, unless otherwise directed by the Director: Star Fleet Command. The general rule
is to have the CSFO make the selection and then to submit the selection to the Star Fleet
Bureau of Personnel for review by the Flag Officers Review Board. The board will
review the selection and make its recommendation for approval or may select its own
Fleet Commander, subject to the final approval of the Chief of Star Fleet Operations.
During times of war or conflict, the CSFO will select a Fleet Commander for immediate
duty without having to go through the normal review and approval process as permitted
under Star Fleet Regulation 5470.
The duration of the assignment of Fleet Commander is completely up to the CSFO, and
there is no term limit associated with this assignment. The CSFO will normally evaluate
the performance of all Fleet Commanders on a yearly basis, but may also evaluate such
commanders at any time and may decide if a replacement is necessary or desired.
SUCCESSION
In accordance with Star Fleet Regulation 5950, the Fleet Commander may prescribe
the order of succession to his command. Typically, this order of succession is usually
prepared when the Fleet Commander assumes command. However, if no order of
succession is prescribed, the Fleet Chief of Staff will, unless otherwise directed by the
Chief of Star Fleet Operations or the Director: Star Fleet Command, temporarily
perform the duties of the Fleet Commander during his absence or disability, or in the
event of a temporary vacancy in that office until the Chief of Star Fleet Operations
appoints a permanent replacement. Should the Fleet Chief of Staff become unable to
fulfill the duties of the Fleet Commander, the CSFO will select a commander from one of
the operational units within that particular fleet – usually the most senior commander
within the fleet.
In addition, if the Fleet Commander is embarked onboard his or her Flagship and is
incapacitated in battle the next in rank onboard the Flagship, eligible to succeed him,
shall succeed as provided in Star Fleet Regulation 5950, and shall announce that he or
she has taken command. It is the duty of the officer who succeeds provisionally to report,
as soon as practicable, the incapacity of the Fleet Commander to the officer who will
succeed him and to the Sector Commandant of the Fleet Commander as required
under Star Fleet Regulation 5960.

VOLUME II
Figure 2a24.1
FLEET COMMANDER’S ORGANIZATION
Fleet Command Staff COMFLT Fleet

VADM Commander
FLTLT Flag FLTSX Flag

LCDR Lieutenant LEUT Secretary
FLTFOR Commander: Fleet FLTOS Fleet

RADM Marine Force RADM Chief of Staff
FLTINT Fleet Intelligence FLTOPS Fleet Operations

CMDR Officer CAPT Officer
FLTMAT Fleet Logistics FLTCOM Fleet Communications

CMDR Officer CMDR Officer
FLAG Flagship FLTSEC Fleet Security

COMO Commander CMDR Officer
COMGRP Group FLTRON Squadron FLTSUP Fleet Support AT Fleet Attack

RADM Commander(s) COMO Commanders RADM Commander CAPT Group Commander
SC Starship SC Starship SP Support Ship

CAPT Commanders CAPT Commanders CAPT Commanders

VOLUME II
Figure 2a24.2
GROUP COMMANDER’S ORGANIZATION
COMGRP Group
RADM Commander
GRPOS Group GRPSX Flag

CAPT Chief of Staff LEUT Secretary
GRPOPS Group Operations

COMO Officer
GRPRON Squadron MF Ground Force GRPSUP Group Support AT Commander: Fleet

COMO Commander(s) COMO Commander(s) COMO Commander CAPT Attack Squadron
SC Starship SP Support Ship

CAPT Commanders CAPT Commanders

VOLUME II
Figure 2a24.3
FLEET SQUADRON COMMANDER’S ORGANIZATION
COMFLTRON
Fleet Squadron
COMO Commander
FLAG Flagship
Commander
*
SQAD Squadron SQSX Flag

LCDR Adjutant LTJG Secretary
SQCS Squadron SQLG Squadron

CAPT Operations Officer CMDR Supply Officer
FLTREP Fleet FLAG Flagship

LCDR Representative LCDR Department Heads
SC Squadron Starship SP Squadron Support

CAPT Commanding Officers CAPT Ship Captains
* Squadron Commanders typically command their own ships – their Flagship. However, where there is a separate Squadron Commander from the Flagship commander, the
Flagship commander may also become the Squadron Operations Officer.

VOLUME II
Figure 2a24.4
FLEET SUPPORT COMMANDER’S ORGANIZATION
COMFLTSUP
Fleet Support
RADM Commander
SUPOS Fleet Support SUPSX Flag

CAPT Chief of Staff LEUT Secretary
SUPOPS Fleet Support

COMO Operations Officer
SUPMAN Fleet Repair SUPXPT Fleet Transportation SUPMAT Fleet Material SUPMED Fleet Medical
CAPT Officer CAPT Officer CAPT Support Officer CAPT Support Officer
RP Repair Ship TR Transport SP Supply Ship HS Hospital Ship

CMDR Commanders CMDR Commanders CMDR Commanders CMDR Commander

VOLUME II
Figure 2a24.5
FLEET ATTACK GROUP COMMANDER
COMATGRP
Attack Group
CAPT Commander
ATGADJ Group
CMDR Adjutant
ATGOPS Group ATGSUP Group

CMDR Operations Officer LCDR Supply Officer
ATSRON Attack Squadron

CMDR Commander

VOLUME II
Figure 2a24.6
FLEET ATTACK SQUADRON COMMANDER
COMATSRON
Attack Squadron
CMDR Commander
ATSADJ Squadron ATSOPS Squadron

LCDR Adjutant LEUT Operations Officer
ATSMAN Squadron ATSSUP Squadron

LEUT Maintenance Officer LEUT Supply Officer
AT Attack Craft
LEUT Commanders

VOLUME II
2.5 BASE COMMANDERS

Star Fleet bases provide the primary support for the Operating Forces of the Star
Fleet and serve as major command centers for the fleet. Such Star Fleet bases or
Starbases are quite large as they must support a large number of ground troops, support
fleet operations, provide local protection, support Star Fleet ships and craft, and provide
rest and recreational facilities to the Operating Forces. As such, the Commanding
Officer of a Star Fleet base has a great responsibility for affecting the efficiency and
effectiveness of the Operating Forces in their role as maintainers of peace and security,
in the enforcement of law and order, and in the overall preservation of the Federation.
The purpose of this section is to present and describe the commanders of the various
types of Star Fleet bases and stations.
In general, a Star Fleet Base Commander represents Star Fleet and therefore, the
Federation in the region of space his base is located; he speaks for it and is personally
accountable for all activities occurring in and around his base or station. Therefore, since
he is accountable for everything that occurs in and around his base, he is given full power
to enforce Federation law and Star Fleet Regulations. In addition, Federation space
also contains many civilian operated deep-space stations used exclusively for recreation
and support. These stations will also come under the authority of the Star Fleet Base
Commander nearest to it. The individual in charge of these stations is usually referred to
as a Station Master or Port Master. All Star Fleet personnel visiting such stations must
respect and comply with all its regulations. However, Station Masters have no command
or legal authority over anyone in the Star Fleet Service.
A Star Fleet Base Commander will be an officer of the line (SBC) with broad command
authority over all the personnel in and around his base or station. As such, the commander
of a Star Fleet base will have the rank and authority commensurate with his responsibility
as stipulated in Star Fleet Regulation 5730. Usually, the Commanding Officer of a
large base will be a flag officer with the rank of Commodore, while the commander of a
Star Fleet station will have the rank of Captain. Regardless of rank, the Commanding
Officer of a Star Fleet base or station will always be called “Commander.” In general,
the selection of all base and station commanders within an octant will be the privilege of
the Sector Commandant, with approval from the Chief of Star Fleet Operations.
STARBASE CENTRAL
Starbase Central is the central command base for the entire Star Fleet. All divisional
command and operational offices for the Star Fleet are located within this base, which
includes the Office of the Director: Star Fleet Command. However, the base itself will
be administered and commanded by an officer of line (SBC) with the primary responsibility
of managing the daily operation of the base. The organizational structure of the base will
essentially be the same as that for any other Starbase. The officer in command will have
a title of “Commander: Starbase Central” or COMCENTBASE and will have a rank of
Commodore, but who will report directly to the Star Fleet Chief of Staff instead of the
Chief of Star Fleet Operations, primarily regarding base services and in providing
special services and accommodations to visiting officials and dignitaries. In summary, the
day to day operation of the base will be solely the responsibility of the COMCENTBASE.

VOLUME II
DISTRICT BASE COMMANDER
A District Base is one that is located on one of the five home or signatory worlds within
the Federation Treaty Zone that originally signed the Articles of Federation. Such
bases are known as System Bases and are generally very large ground facilities with the
designation of “Star Fleet Headquarters”. These bases are primarily administrative
facilities that may contain both Star Fleet and Local Forces. These bases act as liaison
sites between the member government and Star Fleet. As such, the commanders of
these bases, called District Base Commanders, not only have the responsibility over the
Star Fleet forces assigned to them, but must also interact with local government officials
and military commanders as well.
District Base Commanders, also known as Regional Commanders, are flag officers
of the line (SBC) and will typically have the rank of Rear Admiral, as shown in Figure
2a25.1, and will have a title of “Commander: Star Fleet Headquarters - <Planet
Name>” or COM<System>. For example, the Regional Commander for the volume
of space surrounding Earth is called COMSOL. The District Base Commander reports
directly to the Chief of Star Fleet Operations, but will also keep the Commander:
Federation Treaty Zone informed on all matters regarding operations within their area.
OPERATING BASE COMMANDERS
An operating base is a large ground or orbiting facility primarily used for the purpose of
area command and control, and fleet support. These are primarily operations facilities that
will only comprise Star Fleet forces and as such, are the local area command centers for
Star Fleet operations. These operational facilities are called Starbases and are located
out in deep space. They are not usually located within a member system or on a signatory
world and therefore, do not directly interact with any local government or force.
The primary responsibility of a Starbase Commander is the command and control of the
Operating Forces located within his or her area. As such, the Starbase Commander is
the Area Commander for that volume of space, which could encompass a volume of
space with a reach of about 30 light-years in any direction or about 3200 cubic parsecs. All
stations and forces operating within this volume of space will come under the authority of
the Starbase Commander.
A Starbase Commander is in command of all the personnel assigned to his or her base,
and will have authority over any adjunct facility, such as a repair facility, which may be
situated on or around the base, though the facility itself will be under the command of an
officer of the Star Fleet Division of Engineering. In addition, the base may contain a
Brigade of Fleet Marine troops under the command of a Brigade Commander with a
rank of Commodore. These troops represent the operating force for the base and as
such, the Brigade Commander will come under the direct authority of the Starbase
Commander.
Starbase Commanders are flag officers of the line (SBC) with a rank of Commodore,
and will have the title of “Commander: Starbase <n>” or COMBASE<n>. They report
directly to the Sector Commandant of the octant their base is located. Typically, all
operational orders that come from Star Fleet Command will be issued to the Sector
Commandant and then distributed to the various Starbase Commanders in the octant
for execution. A typical Starbase organization can be seen in Figure 2a25.2.

VOLUME II
GARRISON COMMANDERS
Garrisons are smaller Starbases that are primarily used to billet Star Fleet troops and
are normally located near the edge of Federation space. Garrisons have very little fleet
support capabilities, concentrating more on housing, training and supporting the Fleet
Marine forces stationed there, but can also be major supply bases for the equipment and
materials needed to support the Operating Forces in the area. They typically house only
a small crew of Star Fleet personnel to support the base, typically around 150. However,
the bulk of the personnel stationed at a Garrison are Star Fleet Marine Corps troops.
The primary responsibility of the Garrison Commander is to support the Fleet Marine
Corps troops assigned to the base. Typically, a Garrison will accommodate only a single
Marine Division, which is equivalent to about 11,700 troops, and commanded by a Rear
Admiral. The commander will have the title of “Commander: <nth> Marine Division”
or COMDIV <n>. In addition, the Marine Division Commander has precedence over
the Garrison Commander and as such, the Garrison Commander works for the
Marine Division Commander and will receive all operational orders from him.
Star Fleet Garrison Commanders are flag officers of the line (SBC) with the rank of
Commodore, and will have the title of “Commander: Star Fleet Garrison <n>” or
COMFLTGAR<n>. The personnel under direct authority of the Garrison Commander,
as shown in Figure 2a25.3, are only those Star Base Command personnel stationed at
the Garrison for the purpose of operating and supporting the base and the troops.
STATION COMMANDERS
Star Fleet Stations are smaller self-contained bases and are usually floating free in open
space or in orbit around a planet. They serve as command relay centers for the fleet within
a sector and are limited in their support capabilities. However, there are some very large
stations that are capable of fully supporting the fleet. The volume of space in which the
station has jurisdiction is quite small as compared to a Starbase, encompassing a volume
of space with a radius of only 160,000 km. Therefore, as Area Commander, the Station
Commander is limited as to the authority over the forces that operate in and around his
or her station.
As stated, a station may contain a fleet repair facility such as a Drydock. Such facilities
generally come under the command of the Star Fleet Division of Engineering and
therefore, the Station Commander will have no direct authority over the personnel
stationed at the facility, the dock or facility commander, or of the activities occurring at the
facility. However, since fleet repair personnel live on the station, they will come under the
military discipline of the Station Commander.
Star Fleet Station Commanders are usually officers of the line (SBC) with the rank of
Captain, and will have the title of “Commander: Star Fleet Station <n>” or
COMSTATION<n>. They are in command of all the personnel stationed at the base and
are responsible for the efficiency and discipline of their command. Technically, the Station
Commander reports directly to the Sector Commandant of the octant the station is
located. However, it will be the Starbase Commander that is nearest to the station that
the Station Commander will usually report to. Typically, all operational orders to the
station from Star Fleet Command will be relayed to the Station Commander from the
nearest Starbase. A typical station’s organization can be seen in Figure 2a25.4.

VOLUME II
OUTPOST COMMANDERS
Outposts are small stations constructed at the edge of Federation space or around
Federation Neutral Zones. Their primary function is to monitor the boundary and to
provide the first level of defense and communication in case of attack or invasion. In
general, Outposts that are built near Neutral Zones or on the border of hostile territory
will usually be constructed inside large asteroids, which provide additional protection from
enemy attack since such asteroids are essentially large blocks of iron. Outposts may also
be stationed around Federation Buffer Zones to monitor compliance with local zone
restrictions. As such, these outposts are law enforcement stations and will usually possess
a small squadron of fighter craft used to patrol the zone.
An Outpost Commander has full authority over the activities that occur in and around
his area of jurisdiction, and of the fighter squadron that is attached to his command.
However, the jurisdictional area of an Outpost is quite small and as such, the
commanders of such stations are not considered Area Commanders and must report
directly to the nearest command base or station. The basic command organization for an
Outpost is shown in Figure 2a25.5. Star Fleet Outpost Commanders are officers of the
line (SBC) with the rank of Commander[2], and will have the title of “Commander: Star
Fleet Outpost <n>” or COMFLTPOST<n>.
DOCK AND REPAIR FACILITY COMMANDERS
Star Fleet has several ship construction and repair facilities, called Docks, distributed
throughout Federation space. These stations normally come under the command of Star
Fleet Engineering and as such, are not commanded by line officers, but officers of the
Engineering or Construction Corps as stipulated in Star Fleet Regulation 5740.
Such facilities are under the command of a Dock Commander. The basic responsibility of
a Dock Commander is the efficient repair, care and safety of all the ships and craft
located at their facility as stipulated in Star Fleet Regulation 4830. Therefore, while a
Star Fleet ship is at the facility, anchored, locked and powered-down, the responsibility
for everything that physically occurs to the ship rests with the Dock Commander. The
Commanding Officer of the ship, while still in command of the crew, is temporarily
relieved of command until the ship has been powered-up and is ready for space.
The commander of a Star Fleet ship construction or repair facility will typically be a Staff
Corps officer (ENG or CNT) and his rank will range from Commander to Commodore,
depending on the size and function of the facility. Such commanders will usually have the
title of “Commander: Star Fleet Ship Repair Facility<n>” or “Commander: Star
Fleet Ship Construction Facility<n>” or simply COMSHIPFAC<n>. The essential
command organization for a Ship Repair Facility can be seen in Figure 2a25.6.
OTHER STATION COMMANDERS
Star Fleet has other stations and facilities located out in space as well. Such stations
include Communications, Intelligence and Tactical Command or TAC stations.
These stations are typically quite small and therefore, are usually commanded by an officer
with the rank of Commander. The organizational structure of these small stations is very
much the same as for a Star Fleet Outpost, but may contain additional or specialized
departments based upon the function of the station.

VOLUME II
Figure 2a25.1
STAR FLEET DISTRICT BASE ORGANIZATION
District
District Base
Base CO District Base
Command
Command Staff
Staff RADM Commander
FOR Commander: Fleet BASSX Flag

RADM Marine Division LEUT Secretary
STFREP District Staff JUD District

CMDR Representative CAPT Judge Advocate
AW Commander: ENG Commander:

COMO Fighter Attack Wing COMO Fleet Repair Facility
PER District TRN District

CAPT Recruiting Officer CAPT Training Officer
AFOR Local Force RCT Commander: Recruit

CAPT Liaison Officer CAPT Training Center
XO District Base
COMO Executive Officer
OPS Base Operations FAC Base Facilities and MED Base Medical SEC Base Security
CAPT Officer CMDR Services Officer CMDR Officer CMDR Officer
FLT Base Transportation CFT Base Materiel INT Base Intelligence DEF Base Defense
CMDR Officer CMDR Officer CMDR Officer CMDR Officer

VOLUME II
Figure 2a25.2
BASIC STARBASE ORGANIZATION
Starbase CO Starbase
Command Staff COMO Commander
FOR Commander: Fleet BASSX Flag

COMO Marine Brigade LEUT Secretary
FLTREP JUD
Space Sector Regional
CMDR Representative CAPT Judge Advocate
AW ENG
Commander: Commander:
COMO Fighter Attack Wing COMO Fleet Repair Facility
MAT EDU
Commander: Commander:
CAPT Fleet Supply Center CAPT Fleet Training Center
XO Starbase
CAPT Executive Officer
OPS FAC MED DEF

Base Operations Base Facilities and Base Medical Base Defense
CMDR Officer CMDR Services Officer CMDR Officer CMDR Officer
SEC INT
Base Security Fleet Intelligence
CMDR Officer LCDR Officer
CoTSpace Sector
Judge AdvocCMDR
T
STARDATE 7305.29 UFP521-2a25.6 JUD
OFFICIAL USE ONLY
fSpace Sector
RepresentatLCDR
cFLTCommander:
VOLUME II
Figure 2a25.3
BASIC STAR FLEET GARRISON ORGANIZATION
Garrison
FOR Commander: Fleet
Command Staff
RADM Marine Division
CO Garrison
COMO Commander
FLTREP Space Sector BASSX Flag

LCDR Representative LEUT Secretary
JUD Space Sector AG Fighter Group

CMDR Judge Advocate CAPT Commander
XO Garrison
OPS Garrison Operations FAC Garrison Facilities and MED Garrison Medical DEF Garrison Defense
Officer Services Officer Station Officer Officer
CMDR CMDR CMDR CMDR
Operation
s
Officer
SEC Garrison Security INT Fleet Intelligence

CMDR Officer LCDR Officer

VOLUME II
Figure 2a25.4
BASIC STAR FLEET STATION ORGANIZATION
Station CO Station
Command Staff CAPT Commander
FLTREP Space Sector JUD Space Sector

LCDR Representative CMDR Judge Advocate
FOR Fleet Marine TEK Commander:

LEUT Company Commander CAPT Fleet Repair Facility
AT Commander:
CMDR Fighter Attachment
XO Station
CMDR Executive Officer
OPS Station Operations ENG Station Engineering MED Station Medical DEF Station Defense
LCDR Officer LCDR Officer LCDR Officer LCDR Officer
SEC Station Security

LCDR Officer

VOLUME II
Figure 2a25.5
BASIC STAR FLEET OUTPOST ORGANIZATION
CO Outpost
CMDR Commander
AS Fighter Squadron COMYEO Command

LCDR Commander T4 Yeoman
XO Outpost
LCDR Executive Officer
OPS Outpost Operations ENG Outpost Engineering MED Outpost Medical SEC Outpost Security
LEUT Officer LEUT Officer LEUT Officer LEUT Officer

VOLUME II
Figure 2a25.6
BASIC STAR FLEET REPAIR FACILITY ORGANIZATION
Star Fleet Repair Facility CO Repair Facility

Command Staff COMO Commander
BASSX Flag
LTJG Secretary
PER FIN
Facility Facility
CMDR Personnel Officer CMDR Accounts Officer
ENG PRJ
Design Engineering Facility
CMDR Officer CMDR Project Manager
QAC SAF
Quality Assurance Facility
LCDR Officer LCDR Safety Officer
XO Repair Facility
OPS FAC SUP REP

Facility Facility Facility Facility
CMDR Operations Officer CMDR Services Officer CMDR Materiel Officer CMDR Repair Officer
DOK REC
Facility Facility
LCDR Docking Officer LEUT Records Officer

VOLUME II
2.6 SHIP COMMANDERS

Star Fleet ships represent the front line for peace and security within and for the United
Federation of Planets. As such, the Commanding Officer of a Star Fleet ship plays a
crucial role in the maintenance of peace and security, in the enforcement of law and order,
and in the overall preservation of the Federation. In this section the commanders of Star
Fleet vessels will be examined, as well as the organizational structure they function under.
A Star Fleet ship commander is an officer of the line (SSC) who is given total command
authority on board his ship. As such, the commander of a Star Fleet ship will have the
rank and authority commensurate with his or her responsibility, which is stipulated in Star
Fleet Regulation 5750. However, regardless of his rank, the Commanding Officer of
a Star Fleet ship will always be referred to as “Captain.”
In general, the Commanding Officer symbolizes the ship; he represents and speaks for
it, and is personally accountable for it. He is completely responsible for the operation and
fighting efficiency of the ship, and is responsible for all members of his crew and all their
actions. The captain does not make excuses or pass blame to others since he is completely
accountable for all that the ship does, for the quality of training aboard ship, and for the
conduct of the crew at all times. As such, he is likewise given full power to enforce Star
Fleet Regulations aboard his ship and to insure that his crew behaves accordingly. In
short, since his responsibility is complete, his authority must also be complete. The general
organizational structure of a typical Star Fleet ship is illustrated in Figure 2a26.1.
Though all authority, command, direction, and responsibility will ultimately rest with the
Commanding Officer, in practice the captain delegates the duties necessary for carrying
out the functions of the ship to the Executive Officer, to the heads of the departments,
to the Officer of the Deck and through them, to the crew.
STAR FLEET PILOTS
A Star Fleet Pilot is defined as a person within Star Fleet who directs or guides the
movement of a Star Fleet ship into or out of a docking facility when such direction is
required or requested under Star Fleet Regulation 4820. A pilot will board the ship
prior to docking and will direct the Helmsman or personally maneuver the ship into
docking position. Once docking is complete, the pilot will relinquish control of the ship back
to the Commanding Officer or to the Docking Officer if the ship was anchored under
the direction of the pilot.
Star Fleet Pilots are not Commanding Officers per se, but do have the legal authority
to direct a ship’s Helmsman regarding the speed and direction of the vessel under his
control. The Commanding Officer of the ship will generally give a pilot plenty of leeway
regarding the movement of his ship in or out of a facility. However, the Commanding
Officer of the ship remains fully responsible for the actions of his ship while it operates
under power as required under Star Fleet Regulation 4830, regardless of the actions of
the pilot. As such, the Commanding Officer of the ship can override the orders of the
pilot if he or she believes that the pilot is not properly handling the ship.

VOLUME II
STARSHIP COMMANDERS
Star Fleet combatants or Starships are the most powerful and versatile vessel in
Federation space. They perform many differing functions, but their primary mission is to
protect the Federation and all of its resources, property and people. As such, a Starship
Commander will be particularly trained in combat tactics and strategies. Federation
Starships generally operate at the outer rim of Federation space and typically operate
at the periphery of the Star Fleet Chain of Command. As such, the normal mission of a
Starship places the vessel out of communication with Star Fleet Command for long
periods of time. Because of this, a Starship Commander is given unusually broad
powers over both the lives and welfare of his crew, as well as extensive jurisdiction over
the people, places and activities he will encounter during the course of the vessel’s mission
as will be described below.
A Starship Commander must also act as a police officer, enforcing the laws of the
Federation and ensuring the safe navigation practices of the vessels he may encounter.
In so doing, the Starship Commander will monitor space traffic within his operating area
for vessel compliance with Federation transportation laws and to ensure the safety of
vessels within the area. In addition, the Starship Commander has the responsibility to
apprehend and detain any criminal or fugitive from justice within Federation space. This
includes fugitives from foreign as well as from Federation authorities. With this authority
a Starship Commander has broad search and seizure powers, and with due cause can
stop, board, and inspect any vessel for proper documentation, content, safety equipment,
and proper navigational beacons. In the performance of his law enforcement duties, the
Starship Commander can issue citations for any violation of safety regulations or ship
handling practices and may confiscate any contraband found on the vessel, or may seize
the vessel and incarcerate or detain its crew, or make summary judgments relating to
minor infractions of Federation law.
The mission of a Starship is also to engage in scientific studies and as such, a Starship
Commander may also function as a scientist, though he will not personally be engaged in
any scientific investigation. Where scientific study is required, the Starship Commander
will establish scientific investigation teams as needed to accomplish the mission. Another
mission of a Starship is to survey existing territories of the Federation and to explore
new territories for the Federation. Therefore, a Starship Commander must also be an
explorer. Along with this role, the Starship Commander may function as an ambassador
to both known Federation societies and to newly discovered societies. Carefully trained
and briefed as to Star Fleet’s goals and policies, it is the responsibility of any Starship
Commander to interpret them and to apply them as required. As such, a Starship
Commander becomes the highest Federation authority in deep space.
Starship Commanders are officers of the line (SSC) with the rank of Captain, and will
have the title of “Commanding Officer: <Commissioned Name>” or “Captain:
<Commissioned Name>.” For example, the Commanding Officer of the Starship
NCC-1710 will have the title of “Commanding Officer: U.S.S. Constellation.”
However, commanders of larger combatants, such as Battleships or Attack Carriers,
will typically be flag officers with the rank of Commodore as stipulated in Star Fleet
Regulation 5750. In general, the Starship Commander reports directly to the Fleet
Commander to whom his ship is assigned, although communication will typically come
from the Squadron Commander or from the local Star Fleet base or station where his
ship may be operating.

VOLUME II
SUPPORT SHIP COMMANDERS
A Star Fleet support vessel also has an important role to play in the overall mission of the
fleet. They perform the repair of ships, the replenishment of ships and stations and
perform some of the scientific and exploration duties for the fleet. As such, the Support
Ship Commander plays an important part in the success of the fleet and its mission.
Support Ship Commanders are officers of the line (SSC), usually with the rank of
Commander, and will have the title of “Commanding Officer: <Commissioned
Name>” or “Captain: <Commissioned Name>.” For example, the Commanding
Officer of the Star Fleet Repair Ship NCC-1299 will have the title of “Captain: U.S.S.
Assurance.”
Support Ship Commanders report directly to the Fleet Support Commander who is
the senior officer in command of all activities concerning the support of the ships within
the fleet, and who reports directly to the Fleet Commander. All directives regarding the
deep-space repair of ships, supply rendezvous, assignment of support ships to Fleet
Squadrons and transport of supplies and equipment to stations within the octant to which
the fleet is assigned come from the office of the Fleet Support Commander.

VOLUME II
STAR FLEET TRANSPORT COMMANDERS
Star Fleet contains a number of vessels built by Star Fleet, but manned by Federation
civilian personnel. These ships generally are transport or cargo vessels managed by the
Star Fleet Transportation Command and are not commissioned Star Fleet ships, but
instead, have the Star Fleet designation of "Naval Class Auxiliary Support Ship" or
“NAS” as stipulated in Paragraph 5 of Star Fleet Regulation 2400. Most of these ships
are unarmed having only defensive shields and therefore, can be manned by non-military
personnel. That is, civilian personnel cannot, by law, man or operate military or military-
like vessels.
Commanders of Star Fleet auxiliary ships will generally be qualified civilian pilots hired by
the Star Fleet Transportation Command. Civilian commanders of Star Fleet ships are
called “Ship’s Captain” and are subject to Star Fleet Regulations as with any other
Star Fleet officer. Aboard their ship such commanders will have full authority over the
crew and as such, will have the authority to exercise most of the Star Fleet Regulations
regarding the command and discipline of the ship’s crew. They generally have a rank
equivalent to a Commander, but will have no authority over Star Fleet personnel, nor
do they have any authority regarding vessels and personnel that may be encountered
during their travels as with Starship Commanders. Their only authority is over the
immediate crew of the vessel and its operation. An illustration of the typical command
structure aboard a civilian-manned transport vessel of the Star Fleet can be found in
Figure 2a26.2.
Star Fleet officers will always have precedence and authority over civilian Transport
Ship Commanders. However, Star Fleet officers may not change the organizational
structure of the civilian commander unless necessary for the safety of the ship. A Star
Fleet officer, eligible to command Star Fleet vessels, may relieve a civilian commander
under Star Fleet Regulation 4210 if it has been determined that the civilian Transport
Ship Commander is unfit to command or pilot the ship.

VOLUME II
Figure 2a26.1
GENERAL STAR FLEET SHIP ORGANIZATION
Command
Department CO
Commanding
Officer
CAPT
FLTREP COMYEO
Resident Star Fleet Command
Representative Yeoman
LCDR T5
XO
Executive
Officer
CMDR
OPS ENG MED SCI

Operations Engineering Chief Medical [Chief]Science
LCDR LCDR LCDR LCDR
FLT RPR MAT CRG

[Chief]Flight [Chief]Repair [Chief]Materials [Chief]Cargo
LCDR LCDR LCDR LCDR
AT Commander: EXP Commander: SPEC Special FOR Commander:

Attack/Fighter Planetary Survey Functions Fleet Marine
CMDR Squadron CMDR Expedition CMDR Commander CMDR Detachment

VOLUME II
Figure 2a26.2
STAR FLEET TRANSPORT SHIP ORGANIZATION
CO
Ship’s Captain
CIVILIAN
FO
First Officer
CIVILIAN
NAV ENG CRG COMM

Ship’s
Chief Navigator Chief Engineer Cargo Officer Communicator
CIVILIAN CIVILIAN CIVILIAN CIVILIAN

VOLUME II
2.7 OFFICERS IN COMMAND

Star Fleet Regulations require that someone must be in command of a Star Fleet unit
at all times. Specifically, Paragraph 1 of Star Fleet Regulation 4130 states: “Except as
otherwise provided herein or otherwise authorized by the Director: Star Fleet Command,
as appropriate, at least one (1) officer, either in command or eligible to succeed to
command, shall be present and ready for duty at each command. ” To be in command
implies that an individual in the Service has been given the authority to lawfully exercise
control over subordinates by virtue of their rank, assignment or position. Given this
authority, such officers will be called “Commanders”, “Commanding Officers”, or
“Officers in Command.” In general, all officers in command of any unit of the
Operating Forces shall be an officer of the line from either one of the two following
branches of the Star Fleet Service: Star Fleet Command or Star Ship Command.
The term "eligibility for command", as defined in Star Fleet Regulation 6120, means
those officers of the line of Star Fleet who are trained and authorized to perform all the
duties on board a ship or base. However, eligibility for command does not normally apply
to Limited Duty Officers and to certain Restricted Line Officers who are designated
to perform only those specialized duties to which they are assigned or commissioned. As
such, all persons seeking a command or who might succeed to command must meet the
requirements regarding their eligibility to command as defined by the Chief of Star Fleet
Personnel.
The authority of an officer in command is specified in Star Fleet Regulation 5460,

which states: “An officer, either of the line or a Staff Corps, detailed to command by
competent authority, has authority over all officers or other persons attached to the
command, whatever their rank, and whether they are of the line or of a Staff Corps.” In
summary, authority means the license given to an individual to direct and discipline all
personnel under their command, and the license to direct the movements and efforts of all
personnel and equipment under their supervision.
Where necessary to meet the missions or duties assigned, an officer in command may
organize his or her personnel or equipment as desired to accomplish the objectives and
goals of the command, except where the officer in command is assuming the duties of a
Commanding Officer during his absence such as in the case of the Command Duty
Officer. In such cases, the Command Duty Officer or CDO is not authorized to make
any changes in the existing organization, but is obliged to maintain the normal routine of
the command and must carry out the mission and affairs of the command in the usual
manner as required under Star Fleet Regulation 4130.
In this section officers who are in charge or in command of units will be examined. In
many cases units will be temporary organizations assembled to perform a specific task or
mission. In all cases there will always be someone in charge or in command of the unit
and that “Officer in Charge” will follow the Chain of Command up to the Chief of
Star Fleet Operations.

VOLUME II
UNIT COMMANDERS
A Unit Commander is one who commands an elementary unit of Star Fleet. An

elementary unit can be a squad of troops, a single craft or any assemblage of equipment
or personnel. In all cases someone is assigned the duty of commanding the unit as
required under Star Fleet Regulation 4130.
Small units such as troop squads, landing parties or other groups of ten individuals or less
will be under the command of an “Officer in Charge.” The term “Officer” does not
necessarily indicate that the person must be a commissioned Star Fleet officer, but as the
senior person authorized to lead the team. Usually, this authorization is conferred upon the
individual in charge by a commissioned officer. Therefore, the Officer in Charge of a unit
of the Star Fleet may be a senior enlisted person with all the authority and responsibility
as a commissioned officer as specified in Star Fleet Regulation 5420.
Moderately-sized units such as Star Fleet space stations and ships will always be under
the authority of a Commanding Officer and will always be a commissioned Star Fleet
officer of Command rank such as a Captain or Commander as described in Section 2.6.
Large units such as Fleets, Groups, Task Commands, Star Fleet Headquarters and
Starbases will be under the authority of a Commander or Commander-in-Chief, who
will always be an officer of Flag Grade. As such, the rank of such commanders will range
from Commodore to full Admiral.
OTHER FIELD COMMANDERS
Field Commanders generally refer to those officers in command of Star Fleet Marine
troops. However, a Field Commander is a general term for anyone who is in command
of a unit of the Operating Forces of Star Fleet. In the case of large units engaged in
combat out in space, the Field Commander will be the officer in command of the
operation; typically it will be the Fleet or Task Force Commander.

VOLUME II
SENIOR OFFICER PRESENT
The Senior Officer Present, as defined in Star Fleet Regulation 6110, is the senior
military officer, eligible to command, that is present and in command at the locality or
area. In general, the term “senior officer” is construed to mean the officer most senior to
all other officers within the command or area. Seniority is determined by the individual’s
precedence as stated in Star Fleet Regulation 5210 and described in more detail in
Chapter 4 of Volume III of the Star Fleet Command Manual.
The authority of the Senior Officer Present is specified in Star Fleet Regulation
6210, which states: “At all times and places not excluded in these regulations, or in orders
from competent authority, the senior officer present shall assume command and direct
movements and efforts of all personnel in the Star Fleet present, when, in his judgment,
the exercise of authority for the purpose of cooperation or otherwise is necessary. He
shall exercise his authority in a manner consistent with the full operational command
vested in the Commanders of unified or specified commands.” The authority of the Senior
Officer Present is somewhat similar to that of a Commanding Officer, but with certain
restrictions. For example, the Senior Officer Present may not divert his or her command
from the mission or operation assigned to it by a higher authority. The Senior Officer
Present may only change such orders if the public interest requires it. In addition, and in
most cases, the Senior Officer Present cannot make major changes to the organization
he or she is taking command of since he or she is only in temporary command. However,
during war or conflict where the Senior Officer Present is taking command of unit that
is engaging the enemy, he or she can organize the unit in any manner he or she wishes in
order to prevail in the conflict.
During combined operations with Local Forces or when Local Forces are present in
deep space, the Senior Officer Present will be the senior Star Fleet officer, regardless
if the Local Force Commander is senior in rank to the Star Fleet Commander as
stated in Star Fleet Regulation 6220. However, when Star Fleet forces are located
within a member system or attached to a Local Force, the Senior Officer Present will
be the senior Local Force Commander, regardless of the seniority of the Star Fleet
Commander, except as authorized by the Federation Council or the Military Staff
Committee.

VOLUME II
STAR FLEET CRAFT COMMANDERS
A Craft Commander is defined as one who commands or operates a small craft of the
Star Fleet. A person detailed to command a Star Fleet shuttlecraft or other service craft
need only be a Star Fleet officer or senior enlisted Technician as affirmed in Star Fleet
Regulation 5751. Therefore, the requirement regarding the eligibility to command does
not apply to Star Fleet craft.
Although a Craft Commander may be a senior enlisted Technician and in charge of the
craft, the senior line officer embarked on board the craft will be the Senior Officer
Present at all times and as such, will have authority over all passengers embarked therein
and over the mission or operations to which the craft is assigned in accordance with Star
Fleet Regulation 5570. The Craft Commander will only have authority regarding the
functioning of the craft itself and not of the mission or personnel to which the craft was
assigned. However, being accountable for the craft the Craft Commander will be
responsible for the safety of the passengers embarked and of the equipment loaded on
board, and may order or direct the passengers to perform tasks for the safety of the craft.
Where a conflict arises between the Craft Commander and the Senior Officer Present
regarding the safety of the craft and its passengers, the Craft Commander shall prevail
regardless of rank. However, in the case where the Craft Commander is junior to the
Senior Officer Present and that senior overrides the Craft Commander with a direct
order, the Craft Commander shall execute the order in accordance with Paragraph 2 of
Star Fleet Regulation 5450, but shall report the incident to his superior. In this case
the Senior Officer Present assumes full responsibility for the consequences of his action
and for the condition of the craft.

VOLUME II
2.8 ADJUNCT FORCES

Adjunct Forces are those armed forces used to augment Star Fleet in the event of war,
invasion or general galactic emergency as required under ARTICLE 49 of the Articles of
Federation. Adjunct Forces comprise the various fleets and personnel that come from
the military forces of the member systems within the United Federation of Planets.
Under the Articles of Federation any action taken on behalf of the Federation will be
performed by Star Fleet. However, should Star Fleet require aid in the performance of
their functions, Local Forces may be temporarily adjoined to the fleet. As such, should
Local Forces be used to augment Star Fleet they will come under the direct authority
and command of Star Fleet as stipulated in ARTICLE 48 of the Articles of Federation.
However, only the Federation Council, through the Military Staff Committee, may
authorize Local Forces to be joined into Star Fleet for the defense of the Federation.
When Local Forces are adjoined to Star Fleet in open space, Star Fleet will have full
jurisdiction regarding the placement and operational assignments of the forces adjoined to
it. Therefore, it is incumbent upon Local Force Commanders to comply with the orders
and directives given to them by the Star Fleet Commander they are assigned to. When
adjoined to Star Fleet, Local Force Commanders may only command their own forces
and cannot command Star Fleet forces in open space as specified in ARTICLE 15 of the
Star Fleet Charter. In addition, officers of Local Federation Forces may not command
Star Fleet ships or any other asset as stipulated in Star Fleet Regulation 5540.
SOURCES OF ADJUNCT FORCES
The sources for adjunct forces come primarily from the local Federation systems that are
signatories to the Articles of Federation. As required under ARTICLES 43 and 45 of the
Articles of Federation, members of the United Federation are obliged to make ready
and available, on call of the Federation Council, their armed forces and any other such
assistance as necessary for the maintenance of interplanetary peace and security. Table
1a16.1 in Volume I of the Star Fleet Command Manual lists the primary forces that
would normally be called upon to augment Star Fleet.
Although signatory worlds are obliged to render some or all of their forces to Star Fleet,
other worlds that are not a signatory or that do not have a representative sitting on the
Federation Council may also be asked to provide their military forces as well. In such
circumstances the Federation Council will invite such a world to become a member of
the Federation Council in appreciation for their service to Star Fleet under ARTICLE 44.
Only the Federation Council can make such a request. Star Fleet cannot permanently
adjoin any force into its organization, but can only schedule and perform joint exercises
with Local Forces.
The management of the Local Forces by Star Fleet is performed by the Star Fleet
Adjunct Forces Command (AFOR), which is described in Section 1.3 of this volume.
The primary function of this command is to manage all activities regarding the operations
and missions of the Local Forces adjoined to Star Fleet in a unified command, and to
keep the Chief of Star Fleet Operations informed on the state and readiness of those
forces. The organizational structure for this command is illustrated in Figure 2a28.1.

VOLUME II
The Deputy Chief: Adjunct Forces (CFOR) is the senior officer in command of all
activities regarding the operations and assignments of the Local Forces adjoined to Star
Fleet in a unified command in accordance with ARTICLE 15 of the Star Fleet Charter.
The Deputy Chief: Adjunct Forces is directly responsible to the Chief of Star Fleet
Operations for:
1. The assignment of Federation Local Forces to Star Fleet commands and units,
2. The development of specific task commands utilizing adjunct forces,
3. Keeping the CSFO informed on the status and readiness of Local Forces,
4. Maintaining communication and close relationships with Local Force Commanders.
This is accomplished through Local Force Liaison Officers assigned to the Local
Force Commands,
5. The training of Local Force Commanders and personnel regarding Star Fleet
operations, regulations and procedures,
6. Determining the needs and requirements for unified commands, and
7. Developing joint strategic and tactical operations with Local Forces.
The CFOR is an officer of the line (SFC) who is junior to the CSFO and will typically have
the rank of Vice Admiral. The organization structure for the Office of the Deputy
Chief: Adjunct Forces can be found in Figure 2a28.2.
LOCAL FORCE LIAISON OFFICERS
Each Local Force will have assigned to it a Star Fleet Local Force Liaison Officer, also
known as a FORCEREP. The function of the FORCEREP is to maintain close relationships
with Local Force commanders and to communicate to the Local Force Commander any
plans Star Fleet may have regarding the use of such forces. In addition, the FORCEREP
will assess the state of readiness of the Local Force by working within the Local Force
command structure and participating in Local Force meetings and operations.
The FORCEREP will periodically embark onboard Local Force vessels to participate in
their exercises and participate in combined operations with Star Fleet. In this way the
FORCEREP can evaluate the tactics and operations of the Local Force and will make
recommendations to Local Force commanders on how to increase the efficiency of their
operations. The FORCEREP will also submit reports to the Adjunct Forces Command
on the state of readiness of the Local Force.
The Local Force Liaison Officer will typically have the rank of Captain (SSC) and will
report directly to the Deputy Chief: Adjunct Forces. FORCEREPS are selected by the
Deputy Chief: Adjunct Forces with the cooperation of the Sector Commandants and
Fleet Commanders. Typically, the officers selected for this duty are senior officers from
the Operating Forces with command experience. As such, they will normally be former
Starship commanders.

VOLUME II
COMBINED OPERATIONS
Periodically, Local Forces will be involved in joint exercises with Star Fleet. These
exercises are designed to asses and maintain the forces of the Federation in a high state
of readiness, and to test these forces in various tactical situations. In such situations the
Local Force acts as a separate unit retaining its own command structure, but under the
command of Star Fleet. As stated earlier in Section 2.7, during combined operations or
general war the senior commander of the joint force will be the senior Star Fleet officer,
regardless whether the Local Force Commander is senior in rank to the Star Fleet
Commander as stipulated in Star Fleet Regulation 6220.
During wartime conditions, Local Forces will be merged into Star Fleet in order to
augment the fleet. During this time the Federation Council President will declare a
Federation Emergency and invoke ARTICLES 45 and 49 of the Articles of Federation,
requiring all members to supply Star Fleet with a portion or all of their forces. When this
occurs the Military Staff Committee will be notified of the President’s decision and the
individual Commanders in Chief will inform their governments and mobilize their forces.
The commanders of the adjoined Local Forces will report to their respective Star Fleet
commanders as assigned by the Deputy Chief: Adjunct Forces upon notification by
their respective governments. Typically, the Local Force Liaison Officer will notify the
Local Force Commander regarding the Star Fleet commander he will be assigned. In
most cases the assignment of the Local Force to a specific Star Fleet force will already
have been determined in advance by the Star Fleet Office of Local Force Planning
and communicated to the Local Force Commander.
In order to make effective use of the combined force, the Star Fleet Commander and
the Local Force Commander will plan the missions and strategies together, utilizing the
strengths and weaknesses of both forces. When the plans have been made, the Local
Force Commander will execute the mission or the battle plan he is assigned. From this
point onward the Local Force Commander will be in complete command of his forces,
and will organize and direct his forces as he deems fit. The Star Fleet commander will not
manage the individual units of the Local Force, but will provide general guidelines and
direction to the Local Force Commander on how his force will be utilized to accomplish
the mission. And although the Local Force Commander will be in total command of his
force, he must always and continuously report to his Star Fleet Commander on his
present situation and on the progress of his mission.
Where smaller units of Local Forces are assigned to larger Star Fleet units, the Unit
Commander of the Local Force will come under direct authority of the Star Fleet
Commander. The Star Fleet Commander has full authority to direct the Local Force
unit as he sees fit, but may not reorganize the command structure within the unit. That is,
unit cohesion must be maintained at all times.

VOLUME II
ADJUNCT FORCE COMMANDERS
An Adjunct Force Commander is the senior officer of the Local Force assigned to a
Star Fleet unit. The Adjunct Force Commander has absolute authority over his own
Local Force and as such can organize his forces any way he deems fit to carry out the
missions assigned to him.
When attached to Star Fleet the Adjunct Force Commander will be subject to Star
Fleet Regulations and authority and therefore, is subject to the same discipline as any
other officer within Star Fleet. However, the Adjunct Force Commander will also have
the same authorities and responsibilities and will be accorded the same honors and respect
as any other Star Fleet commander.
Star Fleet Regulations are specific regarding the relationship with Adjunct or Local
Force Commanders. Specifically, Star Fleet Regulation 6220 gives the Star Fleet
senior officer to which the Local Force has been attached full authority over the Adjunct
Force Commander. This regulation specifically states: “In open and deep space, the Star
Fleet senior officer present shall be the governing authority in that region. All officers and
men of Local Forces attached to the Star Fleet command shall come under the authority of
the Star Fleet senior officer present, whether the senior Local Force Commander is senior
to the Star Fleet Commander or not.” However, reasonableness in the assignment of Local
Force Commanders will usually be applied and as such, Adjunct Force Commanders
will typically be assigned to Star Fleet commanders of similar or superior rank.

VOLUME II
Figure 2a28.1
STAR FLEET ADJUNCT FORCES COMMAND
2300 Star Fleet

Adjunct Forces
AFOR Command
Office of Local Force Office of Local Force Office of Local Force Office of Local Force
AFOR Planning AFOR Readiness AFOR Training AFOR Materiel
2350 Local Force

Command Liaison
AFOR Offices

VOLUME II
Figure 2a28.2
OFFICE OF THE DEPUTY CHIEF: ADJUNCT FORCES
CFOR
Deputy Chief:
Adjunct Forces
VADM
FORADM
Administrative
Assistant
T5
FOROS
Adjunct Force
Chief of Staff
RADM
COMFORPLN Commander: COMFOROPS Commander: COMFORTRN Commander: COMFORSUP Commander:

Local Force Local Force Local Force Local Force
CAPT Planning CAPT Readiness CAPT Training CAPT Supply
FORCEREP
Local Force
Liaison Officer
CAPT

VOLUME II
2.9 RESERVE FORCES

During times of peace the active Operational Forces of Star Fleet are sufficient to
maintain the peace and security of the United Federation of Planets. During conflict,
however, additional trained forces and assets may be required to increase the ―Active
Fleet.‖ For such occasions, Reserve Forces are needed and are ready. Reserve Forces
are those Star Fleet forces and assets that are currently not on active status, but which
are still regarded as part of Star Fleet. Reserve Forces not only include personnel, but
inactive assets as well, such as ships, craft, bases, stations, equipment, etc. The primary
function of Reserve Forces is to augment and reinforce the active fleet in time of war,
galactic emergency or contingency operations. They provide temporary relief for the active
forces in peacetime, and they provide a service to local governments when needed by
supplying qualified Star Fleet personnel that are already trained in their duties. For
example, in time of galactic emergency certain individuals or assets in Reserve Status
may be called into active service to augment the Operating Forces or to supplement the
fleet.
It should be noted here that the Reserve Force does not include fully retired members or
assets of Star Fleet, only those personnel and assets placed in inactive status that are still
a part of Star Fleet, as well as those persons who are drawing pay. Within this context
retirement means personnel that have been placed on the Retirement List who no
longer have an obligation to Star Fleet, and those assets such as ships or bases that have
been permanently decommissioned and are no longer of any value to Star Fleet.
Reserve Forces can be called into active service at any time should the need arise, as
determined by Star Fleet Operations. Should it be decided that additional forces will be
needed to augment the fleet beyond the use of Adjunct Forces, Star Fleet Operations
will make a request to the Director: Star Fleet Command for the reactivation of the
Reserve force. It should be noted that the reactivation of Reserve forces will not require
the approval of the Federation Council or the Military Staff Committee, but only by
the Director because personnel and assets in Reserve are still part of Star Fleet and as
such, come under the authority of the Director as specified in ARTICLE 47 of the Star
Fleet Charter.
Should there be a need for personnel with specific specialties or for general personnel,
Star Fleet Operations, specifically the Operations Chief of Staff with the approval of
the Director, will make a request to the Division of Personnel for such personnel. The
request will be forwarded to the Bureau of Reserve Personnel for execution. It will be
up to the Bureau of Reserve Personnel to decide who will be reactivated, based upon
the individual’s qualifications, expertise and reserve status.
Should there be a need for ship assets, the Star Fleet Ship Allocation section within
Star Ship Command will make the request, with the approval of the Director, to the
Division of Engineering for the types and numbers of vessels in reserve that will be
needed. The request will then be forwarded to the Star Fleet Reserve Ships Command
(RSHIPS), an office within the Star Fleet Construction Command for implementation.
It will then become RSHIPS responsibility to prepare and reactivate any ship currently in
reserve that was requested and to make it ready for service.

VOLUME II
RESERVE FORCE COMPOSITION
The size, composition, and deployment requirements of Star Fleet at any given time will
depend upon developments within the United Federation of Planets. As such, Star
Fleet maintains a total Reserve Force of about 102,000, with a split of about 34,000
Active Reserve persons and 68,000 Inactive Reserve persons. Active Reservists are
individuals that are no longer active in the fleet, but are still considered active in the sense
that they are continuously training with the active fleet, and would be the first called if
needed. As such, this group will always be ready for action and comprises the ―Ready
Reserve‖. This group reports weekly to their nearest Star Fleet Reserve Office to
receive instruction and planned training, and will report monthly for actual training. In
addition, they will be called for fleet duty and training for one week each year in order to
keep their skills current. The second group, the Inactive Reserve, is made up of groups
from the ―Standby Reserve‖ and the ―Retired Reserve.‖ This group would be called
into active service only during Federation emergencies.
READY RESERVE
The Ready Reserve consists of the Selected Reserve and the Individual Ready
Reserve. The Ready Reserve includes those members, not on active duty, who are
subject to call to active service. They may be called to active service at any time by the
Director: Star Fleet Command if needed. Members of the Ready Reserve are fully
expected to be available for active duty immediately upon receiving orders. However, they
are also allowed a reasonable time between the date they are alerted or ordered to active
duty and the date they must report for duty as shown in Table 2a29.1. Participation or
nonparticipation in a training program has no effect on the liability of Ready Reservists
for recall—all are equally liable. Under the current partial mobilization concept, however,
those participating in Selected Reserve units are more likely to receive involuntary
orders to active duty than other Reservists. Enlisted members serving voluntarily in the
Ready Reserve must volunteer for a specific period. Officers execute Ready Reserve
Agreements for an indefinite length of time. Of the three Reserve categories, only
members of the Ready Reserve may receive pay for participation in Reserve training.
Within the Ready Reserve Star Fleet maintains a Selected Reserve Force, which are
units and individuals that are so essential to initial wartime missions that they require a
high degree of mobilization readiness. Therefore, they must take part in active-duty and
annual training in a pay billet status. As the initial and primary source for Active Fleet
augmentation, the Selected Reserve is immediately deployable upon mobilization. It
must, therefore, be continuously combat-ready and immediately responsible in times of
crisis.
The Individual Ready Reserve (IRR) consists of those service members of the Ready
Reserve who are not in the Selected Reserve. Limitations in the number of available
pay billets, the absence of training units within commuting distance, possible conflicting
employment, and other factors may prevent some Reservists from participating in the
Selected Reserve. Therefore, Reservists affected by any of these factors are assigned
to the IRR. While assigned to the IRR, members can still participate in the Star Fleet
Reserve Training Program. Additionally, within the limitation of funds, personnel in the
IRR who have maintained an active status may participate in 12 to 14 days of active-duty
training annually.

VOLUME II
STANDBY RESERVE
The Standby Reserve consists of Reservists who have transferred from the Ready
Reserve after fulfilling certain requirements. Ready and Standby status differ mainly in
the degree of liability for recall to active duty. Standby Reservists can be ordered to
active duty without their consent only in the event of war or an emergency declared by the
Federation Council President or when otherwise authorized by law. Star Fleet cannot
recall a member of the Standby Reservist to active duty involuntarily until the Military
Staff Committee has decided this group’s availability for duty. The Standby Reserve
includes the Standby Reserve-Active and the Standby Reserve-Inactive.
The Standby Reserve-Active consists of Reservists who have completed their active-
duty or Selected Reserve service obligation. They have requested transfer to the Active
status list of the Standby Reserve. Officers with at least eighteen, but less than twenty
years of satisfactory service toward retirement pay for non-regular service can also request
transfer to the Standby Reserve-Active.
The Standby Reserve-Inactive (also called the Inactive Status List or ISL) includes
three groups of Reservists who have been screened from the Ready Reserve. The first
consists of those who did not maintain a satisfactory level of participation. The second
consists of those who allowed their Ready Reserve agreement to expire while in this
status. The third consists of those who fit into both the first and second group. While in
this Inactive status, a member may not participate in training programs, earn retirement
points, or be considered for promotion. Reservists transferred to the Standby Reserve-
Inactive may apply for reinstatement in the Ready Reserve at any time within the
following two years. Those members not voluntarily returning to a Ready Reserve status
at the end of two years are discharged or transferred to a retired status, as appropriate.
Members on the Inactive Status List may be called to active duty under the same
conditions as other members of the Standby Reserve. However, a determination must
first be made that adequate numbers of qualified personnel in an Active status (Ready
and Standby Reserve-Active) are not available.
RETIRED RESERVE
The Retired Reserve consists of Reservists who are drawing Retirement Pay. Their
liability for active service is the same as those in the Standby Reserve[3].

VOLUME II
PERSONNEL IN RESERVE STATUS
Star Fleet maintains a Reserve Force of service personnel that are no longer on active
duty, but that are still members of the Star Fleet Service who still have a contractual
obligation to continue to serve Star Fleet. As such, there are essentially two types of
personnel in the Reserve Force:
a. Those that are no longer on active duty status, but wish to continue a career in Star
Fleet or that still have an obligation to the Service, and
b. Those that join Star Fleet as Reservists in order to balance military service with a
civilian career.
In either case, the Reserve Force is a pool of resources that Star Fleet can draw from
should the need require additional personnel. This pool is divided into three categories,
which represent the order of reactivation.
Table 2a29.1
CLASSIFICATION OF RESERVE PERSONNEL
Reserve State Reactivation
Description
Classification Time
Star Fleet’s primary source of immediate mobilization manpower
and represents those Reservists who are on active duty status
Ready Reserve 12 hrs.
in the training and administration of Star Fleet’s Reserve Force
program.
Reservists who have transferred from the Ready Reserve after
Standby Reserve 48 hrs.
fulfilling certain requirements established by law.
Reservists who are drawing compensatory pay or are qualified for
Retired Reserve 72 hrs.
retired pay, but do not receive a pension. Used as a last resort.
Retired Star Fleet personnel are generally not considered in Reserve status since, in
most cases, they are detached from service and no longer have any obligation to serve.
Only those retired members, those in the Retired Reserve, receiving compensatory pay
may be considered on Reserve Status and could be called back into active service in
cases of extreme emergencies. However, this does not include retired members receiving a
regular Star Fleet pension.
The Star Fleet division responsible for managing the Reserve Force of personnel is the
Star Fleet Bureau of Reserve Personnel (BURESRV), a component of the Star Fleet
Division of Personnel. The organizational structure for BURESRV can be found in
Figure 2a29.1. The primary function of BURESRV is to maintain the active and inactive
Reserve Duty Lists and to keep track of the location and status of all members of the
Reserve force. This bureau is responsible for keeping the entire Reserve force informed
on any changes to regulations, standards, pay, benefits or anything that may be of
concern to persons on Reserve status. In addition, BURESRV also provides training to
Reservists in order to keep the Reserve Force up to date and ready for any emergency.
This training is usually accomplished by requiring Reservists to enter active service every
six months for two weeks. In charge of BURESRV is the Deputy Chief: Star Fleet
Reserves (CRES) who is an officer of the line (SFC), and will typically have the rank of
Rear Admiral.

VOLUME II
SHIPS IN RESERVE STATUS
Star Fleet also maintains a ―mothball‖ fleet of retired vessels known as the Reserve
Fleet. Vessels that are no longer needed by the fleet, for one reason or another, are
decommissioned, their names and numbers stricken from the Star Fleet Vessel
Register, their commissioning and fleet service pennants removed from the hull and the
vessel placed in storage.
In general, Star Fleet ships that are no longer in use are not dismantled, but are placed
in storage at one of the three Star Fleet Reserve Ship Facilities located throughout the
Federation Treaty Zone. Ships that enter the Reserve Fleet will undergo special
preparations before they are parked in orbit and locked-up at the facility. All environmental
systems will be shut down and the interior of the ship will be exposed to the vacuum of
space. This helps in preserving the ship from decay or corrosion. However, heaters will be
placed at key locations throughout the ship in order to prevent moisture from condensing
and freezing on vital components or circuits. A more detailed description of the Reserve
Ship decommissioning process may be found in Section 6.5 of this volume. Needless to
say, ships in Reserve Status do not require crews to maintain them as they are self-
maintained.
A Reserve Ship Facility is generally an area of space around a moon or planet within a
system that does not contain life or that is out of the way of normal commercial space
traffic. These facilities are simply open areas of space where the ships stored at these
facilities are simply ―parked‖ out into space. Each facility has a small station with a small
crew of engineering, maintenance and security personnel. The security force assigned to
the facility will perform periodic patrols around the site to prevent intruders and looting of
the ships. In addition, the area around the facility contains sensors that will alert the
security force of any intruder, and beacons warning anyone coming near the area that it is
Star Fleet property.
In practice, however, many ships in the Reserve Fleet may be scrapped if they have
been placed in Reserve Status for more than 75 years. The technology of these old ships
is so outdated that the cost of updating them to standard would be too prohibitive. As
such, the older ships in the Reserve Fleet will either be sold to private concerns or to
friendly governments, or used as target practice for the fleet.
The organization, as shown in Figure 2a29.2, responsible for the care and maintenance of
the Reserve Fleet is the Star Fleet Reserve Ships Command (RSHIPS), an office
within the Star Fleet Construction Command. It is the function of the RSHIPS to
manage the Reserve or ―mothball‖ fleet. In charge of this division is the Commander:
Reserve Fleet, who will typically have the rank of Commodore.
In addition, there is another form of reserve fleet in which the Star Fleet may draw
vessels from. The Federation Transportation Administration maintains a fleet of
inactive and retired merchant and other commercial space vessels, many of which go back
to the Romulan War of 2132. These ships were armed transports during a time when
commerce between the worlds of the old Confederation required armed convoys. Today,
these ships may be sold or auctioned off to private and commercial enterprises that need
ships to transport their goods. However, they may also be used to augment Star Fleet as
well. Typically, these ships would be used as fleet support vessels or may be enlisted into
the Star Fleet Transportation Command to temporarily augment its freighter fleet.

VOLUME II
OTHER RESERVE ASSETS
Other reserve assets refer to equipment, weapons, vehicles and other objects placed in
storage for later use. Equipment that may have been produced during wartime, but that
are no longer needed will not automatically be scrapped or sold-off. Such equipment that
exhibit little or no wear will be ―mothballed‖ and placed at a storage facility just as with
vessels that are no longer used. The organization that is primarily responsible for the
storage and upkeep of such mothballed equipment is the Star Fleet Supply Command.
Other major assets such as bases or stations may also be placed in Reserve Status as
well. For instance, if a base or station is no longer deemed to have a strategic value, or is
no longer economically feasible to maintain as the cost of keeping such a base or station is
too great to justify its function, Star Fleet Operations may elect to shutdown the facility.
Bases or stations that are shutdown will be stripped of all equipment and hardware and
will either be sold or placed in reserve. However, unlike ships, bases and stations placed in
reserve must remain in place as they cannot be moved, or that could be moved, but would
simply be too costly to move.
The determination of whether a base or station is to be shutdown is the sole responsibility

of Star Base Command – specifically, the Star Fleet Base Operations Planning
Section. It is this office that determines the basic usefulness of bases and stations, as
well as monitoring the readiness and effectiveness of such facilities. Therefore, should this
section determine that a facility needs to be shutdown or placed in Reserve Status, it will
submit such a request to the Director: Star Fleet Command for approval. If approved,
the Star Fleet Base Operations Planning Section will submit a request to the Star
Fleet Construction Command to perform the preparations required to place the facility
in a Reserve Status condition. Any equipment or material on the facility will be removed,
stored or disposed of by the Star Fleet Supply Command. Once placed in reserve, the
Base Operations Planning Section will strike the facility from the Star Fleet Station
Register.
Facilities placed in reserve will usually contain a small maintenance and security force
assigned to it to keep the facility in some level of operational readiness, but the facility
may also be completely shut down and administered by Local Forces or by a contracted
security force.

VOLUME II
Figure 2a29.1
STAR FLEET BUREAU OF RESERVE PERSONNEL
6500 Star Fleet

Bureau of
BURESRV Reserve Personnel
6510 Star Fleet 6520 Star Fleet 6530 Star Fleet Office of
Office of Office of Reserve Training
BURESRV Reservist Benefits BURESRV Reservists BURESRV and Certification

VOLUME II
Figure 2a29.2
STAR FLEET RESERVE SHIPS COMMAND
3950 Star Fleet

Reserve Ships
RSHIPS Command

Office of Reserve Ship Office of
RSHIPSEC Reserve Ship Security RSHIPSFAC Facility RSHIPSREC Reserve Ship Records
3952 Reserve Ship 3952 Reserve Ship 3952 Reserve Ship

Operations Engineering Maintenance
RSHIPSFAC Section RSHIPSFAC Section RSHIPSFAC Section

OFFICIAL USE ONLY
VOLUME II
3.0 GLOBAL FLEET ORGANIZATION

This chapter will describe how Star Fleet organizes its forces within Federation space.
Federation space is divided into octants or one-eighth of a spherical volume enclosing the
United Federation territories. As such, Star Fleet organizes the Operating Forces and
Shore Establishments within the boundaries of this structure.
Section 3.1 briefly describes how the regions of space enclosing the United Federation
are defined. Much of this information was previously discussed in Section 5.1 of Volume I
of the Star Fleet Command Manual. As such, the reader should refer to that section for
more details. In addition, this section will also provide a description of the known hostile
governments neighboring the United Federation that help shape Federation policy and
strategic direction.
Section 3.2 describes how Star Fleet makes use of the regions discussed in Section 3.1
into command areas. This section describes how such regions of Federation space are
divided into Regions, Sectors and Areas, and the basic command structure within these
spaces.
Section 3.3 introduces the reader to how Star Fleet organizes its mobile forces into fleets
and other such operational units, and defines what constitutes the various operational
units employed by Star Fleet.
Section 3.4 describes the basic “Chain of Command” as it relates to the Operating
Forces. This section will show that the chain of command not only defines the lines of
communication, but the line of authority as well.
Section 3.5 discusses the requirements that determine the size and the scope of the fleet.
As such, this section defines the requirements and factors used in determining the number
of operating vessels and the support infrastructure needed to carry out the missions to
which Star Fleet is assigned.
Section 3.6 describes the internal components of fleets and the definition of the various
assemblages of ships and craft. As such, this section defines what constitutes a fleet,
force, flotilla, squadron and any other unit or assemblage of ships and craft.
Section 3.7 describes how the Operating Forces are deployed within Federation space
and how Star Fleet Commanders deploy their forces. This section will also discuss how
ships and units may be rotated to different units or areas of space.
Section 3.8 describes how service craft and attack craft are organized, and will establish
the standard by which craft are organized and designated.

VOLUME II

VOLUME II
3.1 FEDERATION TERRITORY AND

SPACES
The United Federation of Planets occupies a very small portion of the galaxy called the
Milky Way. It is divided into two roughly spherical volumes: the inner Federation Treaty
Zone and the outer Federation Exploration Zone. These two volumes, as they relate to
Star Fleet operations, will be discussed in more detail in the subsequent sections below.
FEDERATION TREATY ZONE
The Federation Treaty Zone is a virtual sphere with a diameter of space approximately
41.6 light-years or about 12.8 parsecs, and has an estimated total volume of about 1086
cubic parsecs. This volume of space was established when the Articles of Federation
was ratified, thus the name “Treaty Zone”. This volume contains 56 star systems, five of
which contain the planets of the original signatories to the Articles of Federation.
The Treaty Zone is divided into nine sectors as illustrated in Figure 2a31.1. At the very
center is Sector 001, otherwise known as the “Prime Sector”[1], which is a sphere eight
(8) light-years in diameter with a volume of about 8 cubic parsecs that encompasses the
SOL system, Star Base Central and various Star Fleet shipbuilding and repair facilities.
The remaining eight sectors that surround Sector 001 are spherical sectors each having a
volume of about 152 cubic parsecs.
At the very center of the Federation Treaty Zone is located Star Base Central. This
space station is the main headquarters for Star Fleet Command, which was established
in accordance with ARTICLE 67 of the Star Fleet Charter. All command directives and
operations come from this central location. In addition, and dotted throughout the Treaty
Zone, are various Starbases and Star Fleet stations orbiting the various worlds of the
Federation. These bases and stations act as the regional command centers for the zone.
The primary mission of Star Fleet within the Treaty Zone is basically the maintenance of
interplanetary law and order among the signatory worlds of the Federation, which are
shown in Figure 2a31.3. As such, the Treaty Zone is patrolled by 34 light combatants and
about 16 fleet support vessels of the Star Fleet, and which comprise the two Flotillas
assigned to the region as stipulated in ARTICLE 63 of the Star Fleet Charter. These two
Flotillas typically check commercial space traffic to ensure that vessels navigate and
operate safely and are properly licensed and registered.
Non-military vessels, private and commercial, account for about 80% of the traffic within
Federation space, the bulk of which is primarily in and around the Federation Treaty
Zone. Therefore, as part of its law-enforcement function, Star Fleet will monitor and
regulate the flow of space traffic within this area.

VOLUME II
FEDERATION EXPLORATION ZONE
The Federation Exploration Zone is the unseen volume of Federation space that
surrounds the outer volume of the Treaty Zone. Currently, the average breadth of the
Exploration Zone is roughly 450 light-years or about 140 parsecs in diameter (where 1
pc = 3.258 ly). The size varies depending on the extent of exploration in the outer regions,
as well as boundary encroachment into other alien territories. The Exploration Zone is
essentially made out of cubical volumes or Sectors of about 20 light-years on each side.
These areas, combined together, form a rough sphere that is further divided into eight (8)
primary divisions, unofficially called “Octants”, used to group the sectors together for fleet
assignment, as illustrated in Figure 2a31.2. As implied, the Octant designation is not a
formal standard within the Federation and its only purpose is to arrange the sectors for
assignment to the eight primary fleets of the Operating Forces outside the Federation
Treaty Zone.
Each of these octants will be commanded by a senior flag officer with the title of Sector
Commandant. This commander will have the rank of Admiral and will report directly to
the Chief of Star Fleet Operations. Sector Commandants have a great responsibility
since they are in command of all the forces and bases within a volume of space equivalent
to roughly 161,000 cubic parsecs. As such, they rely heavily on the various Area, Station
and Starship commanders for their support and to carry out the missions and operations
assigned to the Sector Commandant.
Outside the Treaty Zone, and throughout the rest of the Federation, are distributed the
eight Fleets that comprise the bulk of the Operating Forces of the Star Fleet, as
stipulated in ARTICLE 62 of the Star Fleet Charter. As such, each fleet is assigned to one
of the eight primary octants dividing the Federation Exploration Zone, and is numbered
accordingly (e.g. 1st Fleet, 2nd Fleet, ..., 8th Fleet). The primary function of these fleets
in the Exploration Zone is to protect Federation space. Their secondary function is to
expand Federation space through exploration and colonization.
Each fleet is commanded by a Fleet Commander having the rank of Vice Admiral, and
who will have the title of Commander: <nth> Fleet and designated as COMFLT<n>.
For example, Commander: 3rd Fleet will have a designation of COMFLT3. The Fleet
Commander is the senior officer of the fleet and has precedence over all personnel within
his assigned fleet. The Fleet Commander will also directly report to the Chief of Star
Fleet Operations, but through the Sector Commandant of the octant in which his fleet
has been deployed. Therefore, fleet operational orders will usually come directly from Star
Fleet Command to the Fleet Commander, either directly from the Chief of Star Fleet
Operations or through the Sector Commandant. Usually, the Fleet Commander will
be stationed at the same base or location as the Sector Commandant. Together, they
represent force operations for the octant of space assigned to them.
At the present time about 68% of the Exploration Zone has been fully explored and
mapped, while 32% of the territories have not yet been fully explored. Approximately 40%
of the total volume of the Exploration Zone or 59% of the explored regions contain
systems that are members of the United Federation. As such, there continues to be
ample opportunity for exploration within this zone and therefore, it is one of the primary
aims of any patrol mission of the Operating Forces to carry on exploration and mapping
activities within the Federation territories. The known worlds of the Exploration Zone
can be seen in Figures 2a31.4 through 2a31.7.

VOLUME II
KNOWN HOSTILE POWERS
Beyond the Federation Exploration Zone is open space, except in those areas where a
foreign power has jurisdiction or has made a claim to the area. Two powers in particular
are relatively large empires that are hostile to the Federation: the Klingon and Romulan
empires. Both of these will be briefly described in the subsequent pages.
The function of this section is to describe the major cultures and powers that are hostile to
the Federation, the purpose of which is to acquaint the reader regarding the impact such
powers have on shaping Federation policy and therefore, Star Fleet operations. On the
whole, the primary goal of Star Fleet with regard to such hostile governments is defense
– the protection of the Federation. Therefore, the missions and operations performed by
Star Fleet will essentially be designed to contain these hostile powers and to prevent
them from gaining a foothold into Federation space or from gaining territories and areas
of space that the Federation may wish to acquire. This policy is known as “Containment”,
and is one which has been used by powers throughout the centuries.
Among the many alien powers of the galaxy are some comparatively minor races. Though
only occupying a small area of space, they are sometimes a source of military challenges
to the Federation as well. Therefore, these smaller empires will also be included, except
those minor principalities composed of a single planet, such as Platonius, or those peoples
that do not venture out into deep space.
In order of their initial contact with the Federation the known hostile governments will be
presented in the following pages, and a diagram showing the location of these hostile
governments relative to the Federation can be found in Figures 2a31.8 through 2a31.10.

VOLUME II
ROMULAN STAR EMPIRE
The Romulan Star Empire is situated between 100 to 133 degrees in the SCS system with
an approximate length of 330 light-years and an overall width of about 190 light-years. All
of which encompasses a volume of space of roughly 180,000 cubic parsecs. The home
system of the Romulan Empire is Beta Romii (Delta Andromedae in the catalog), and is
located at 112-MARK-025 approximately 99.5 light-years from the center of Federation
space. At its closest point the boundary of Romulan space encroaches into Federation
space 89.6 light-years from the center of the Federation in the direction: 111-MARK-014.
Little is known of the Empire as a whole, but from what intelligence can be obtained it
encompasses many star systems. The home planet, Romulus, circles the star Beta Romii
and represents the seat of government for the empire. The name Romulus was given to
the planet by the early settlers which called themselves Romulans and who presumably
fled Vulcan almost two thousand years ago after being wholly disenchanted with the new
peaceful, and logic-based social reforms that were taking place, who have lost contact with
the mother race in the distant past.
The basic physiology of the Romulan race is very near that of the Vulcan race: pointed
ears, upswept eyebrows, and copper-based blood that is green when oxygenated in the
arteries and copper or rust colored when deoxygenated in the veins. However, unlike the
Vulcans, Romulans have a V-shaped ridge above the bridge of their nose, undoubtedly an
evolutionary trait passed down from the early settlers.
Romulans are highly militaristic, aggressive by nature and ruthless in warfare as illustrated
by some of the stories during the Romulan War. However, they are highly organized and
excel in combat tactics. As such, they quickly sought out to conquer and settle the space
around them and thus formed the Romulan Star Empire.
The central political and governing body over the Empire is the Senate, which is presided
over by the Praetor, and his various Proconsuls. This form of government is very much like
the ancient Roman Empire on Earth. Policy and dictatorship is driven towards complete
control over the masses, as the preferred method of existence in order to maintain an
orderly, efficient lifestyle, whist keeping private, low profiles.
The Federation’s first contact with the Romulans occurred in 2132 with a clash involving
a commercial convoy traveling to Catulla that resulted in the 31 year Romulan War. The
war caused both sides to suffer heavy losses. To end hostilities, an armistice was declared
in 2163 and a peace treaty was negotiated entirely by sub-space radio three years later.
The treaty, which was called the Treaty of Algeron, established the Romulan Neutral
Zone between which none of the parties are allowed to trespass or the treaty would be
broken.
Recent intelligence indicates that the Romulan Empire may have established agreements
with the Klingon Empire whereby the Romulans can purchase warp-driven D-7 battle
cruisers, weapons and other equipment from the Klingons. This is a cause for concern to
the Federation since with this technology the Romulans can become more aggressive.
However, this alliance may be somewhat tenable since the Klingons suspect the Romulans
of treachery near their borders. Due to their aggressive nature and their history of attacks,
the Romulan Star Empire poses a direct threat to the security of the Federation.

VOLUME II
KLINGON EMPIRE
The Klingon Empire is larger and more powerful than the Romulan Empire. The territories
of the Klingon Empire extend from 353 to 98 degrees in the SCS system and do not
encroach into Federation territory. Klingon space has a maximum length of about 375
light-years and a width of about 300 light-years, which encompasses a volume roughly
950,000 cubic parsecs. However, this volume of space is sparsely populated with planetary
systems and therefore, must rely on a limited number of key planets for its resources.
The home system of the Klingon Empire is Kazh (HD209149) in the constellation Pegasus,
which is located at 078-MARK-045 approximately 216.1 light-years away. Encircling Kazh is
the Klingon capital world of Qo'noS (known as Kronos), which basically consists of a single
large landmass, dominated by a vast ocean. Seen from space, its predominant color is
green. Its climate encompasses simultaneous extremes of warm and freezing weather and
wild seasonal changes, all generated due to the planet's severe axial tilt and nutation.
The Klingons are a humanoid warrior species, their origin of which is unknown. The pure
Klingon is a large, strong hominine with a thick skull, ribbed along the center of the frontal
and occipital areas of their cranium and on down the spine. The patterns are also visible
on their feet and backs and vary by genetic line, which may be an evolutionary remnant of
a hypothetical prehistoric crustacean-like form. There had been some genetic experiments
performed in the past by Klingon scientists in attempt to breed a hybrid Klingon-humanoid
species. The result was a dark-skinned humanoid with long bushy eyebrows with a very
minor cranial rib. However, this particular race is somewhat revolting to the pure Klingons
and the breed was left to propagate and govern in their own area of Klingon space. And
although largely ostracized by the pure races, they are frequently used when there is some
deceitful work to be carried-out.
The government of the empire is controlled by the High Council, which presides over the
empire from the Great Hall of the First City on Qo'noS. The High Council is presided over
by a Chancellor, and is composed of a loosely faction-based, informal cabinet consisting of
the prominent members or leaders of the various “Houses of the Empire”. Most of the
seats within the cabinet are hereditary, but some are conferred upon distinguished
warriors. Star Fleet Intelligence speculates that the council may consist of as many as
24 such houses, but this is not an absolute certainty. Political judgments are made by
these members and overseen by the Chancellor. Power is controlled by the least discussion
and bureaucracy possible, and decree is swift.
First contact with the Klingons occurred in 2245 as the Federation was embarked on
deep-space exploration. Up to that point in time there were only reports and stories of
missing space craft and atrocities committed by these peoples. The first major political
encounter occurred during a peace-keeping mission to the planet Organia in 2266. The
result was the Organian Peace Treaty, which required concessions on both sides.
Tactically, Klingon weaponry is somewhat similar in power to that of the Federation.

Their warships are comparable to Federation Starships in strength and capability, with a
slight edge on the side of the Federation of about 1.13:1. As such, a one-on-one battle
between a cruiser class Starship and a D-7 battlecruiser would give a slight advantage to
the Starship. Therefore, due to their aggressive nature, the Klingon Empire poses a direct
threat to the security of the Federation.

VOLUME II
GORN EMPIRE
The Gorn Empire is a relatively small volume of space encompassing approximately 683
cubic parsecs located mainly in the constellation Aquila and is almost completely engulfed
by the territories of the Federation. The length of this volume of space is approximately
50 light-years, which encompasses sectors 2470-2472, 2422-2424, 2518-2520, 3575-3577,
3631-3633, 3687-3689, 3743-3745, 5143-5146, 5203-5206, 5263-5266, 5323-5326, 6943-
6946, 7008-7010 and 7072-7074. The Gorn home system is the star Ghdar (4 Aquarii in
the catalog) located at 041-MARK-017 approximately 191 light-years away. The home
planet of the Gorn Empire is S’sgamon, which is essentially a desert planet with various
minor seas and lakes.
The denizens of the planet S’sgamon, the Gorns, are of reptilian origin and have a lizard-
like appearance. As with most reptilians the Gorn are evidently cold-blooded and as such,
are poikilothermic – requiring heat from the environment. They are quite large, standing
approximately 2.3 meters with an average weight of 220 kg. They are proud creatures
with a long history of war, art and culture, and are a more civilized and cultured race than
most people believe.
The government of the Gorn Empire is essentially a hegemony in which the home world of
S’sgamon has dominion over its member systems. The central government of the Gorn is
an oligarchy of Autarchs, which is called “The Alliance” in their language. Each Autarch
singly governs their entire system or colony world and their rule is absolute. The Gorn
consider this form of government as being the most efficient.
The Federation’s first contact with the Gorn occurred in 2267 when the Star Fleet
garrison on Cestus III was attacked and totally destroyed by Gorn forces. What made
matters worse was the deceitful way in which a nearby Starship on patrol was invited to
attend a dinner with the garrison commander, but only to find the base utterly destroyed.
The crew was essentially invited into a trap, but was able to ward off the attack initiated
by Gorn forces. The Starship pursued the Gorn ship into their space in retribution, but
vessels both were stopped by a race known only as the Metrons. An agreement was forced
upon both parties whereby both would leave the other alone, which is known simply as the
Metron Agreement. The exact sequence of events that took place still remains classified
to this date.
Gorn technology is on par with the Federation. Their ships are nearly as fast as Star
Fleet vessels thanks to technology borrowed from the Klingons. Gorn infantry units
possess powerful disruptors, capable of completely disintegrating targets at ranges of up
to several kilometers. Gorn ships also use such disruptors, but of a much larger scale.
Their sensor technology is slightly less effective than that of the Federation and as such,
has recently begun developing their own cloaking device.
The Gorn Empire itself is almost completely enveloped by the Federation, but is not part
of the United Federation of Planets. This race would rather remain independent and
due to their reptilian physical nature, do not mingle well with the humanoid races. They
trade often with the Klingon Empire to which they seem to have a kinship and have little
contact with the Federation, perhaps as a result of the Cestus III encounter and the strict
provisions in the Metron Agreement. However, the Gorn Empire does not pose a direct
or imminent threat to the peace and stability of the Federation at this time.

VOLUME II
MELKOTIAN REALM
Melkotian Space, also known as the Melkotian Realm, is a relatively large conglomerate of
stars beyond the outer rim of Federation space between 292-MARK-308 and 305-MARK-
313 in the Federation Standard Coordinate System and is estimated to encompass a
spatial volume of about 51,100 cubic parsecs.
The home system of the Melkotian Realm is the star Theta Kiokis or Theta 1 Crucis, in the
standard star catalog, located 312-MARK-308 and about 230 light-years away. The second
planet encircling this star is the home world of Melkot or Theta Kiokis II. Though explored
only in a very inexact way, Melkot has revealed itself to be a planet of class M in the lower
atmosphere with dense clouds of CO2 and water vapor in the upper regions. The planet is
predominately covered by about 82% land and only about 18% water, and has an average
ambient temperature of around 54o C. The relatively high atmospheric temperature and
composition suggest that most of the planet’s water is in the form of vapor composing the
atmosphere.
Very little is known of the race known as the Melkotians, but from little that is known they
have a form limited to only a head connected to a small abdominal structure from which
tentacles emanate. However, what is positively known about this race is that they are born
with strong psionics powers. Observers have affirmed that they utilize their telekinesis for
motion and that they have the ability to create very realistic illusions.
Melkotians are very reclusive and xenophobic creatures who regard all outsiders as an
"infection." As such, they have disseminated buoys and warning devices all around their
space to ward off intruders, and have dealt harshly with those who have violated their
warnings. Therefore, very little information regarding their culture, government or social
structure is available. Melkotians will communicate if approached and they communicate
telepathically such that their messages are perceived in the receiver's native language.
However, they can also create immersive illusions similar to high quality virtual reality. In
such illusions individuals can die if they believe in them strongly enough.
No treaty or agreement exists with the Melkotians and they do not pose a direct threat to
the Federation at this time, primarily because they wish isolation from outside cultures.
However, due to the nature of the Melkotian’s telepathic and psionic abilities, the entire
realm has been classified as a 7-6 Quarantine domain and as such, buoys around the
Neutral Zone established for this realm will transmit a Code 706 warning to travelers of
the dangers if they enter Melkotian space.
Lastly, Melkotians no longer venture out into deep space and have abandoned their fleet of
space ships since they have mastered their telepathic capabilities. Their telepathic
capabilities allow them to traverse their volume of space instantaneously and therefore,
have no need for physical instrumentalities. As such and as of this writing, no encounters
with a Melkotian vessel have ever occurred.

VOLUME II
THOLIAN ASSEMBLY
The Tholian Assembly is a small conglomerate of star systems beyond the outer rim of
Federation space between 303-MARK-352 and 332-MARK-328 in the Federation
Standard Coordinate System and is likely that it encompasses a spatial volume of
about 13,000 cubic parsecs. The home system of Thol centers around the star HD121901
in the standard star catalog, which is located at 325-MARK-319 approximately 213 light-
years away in the constellation Centaurus. The home world of Tholia is a large and
extremely hot planet with a somewhat dense atmosphere composed primarily of methane
gas as determined from spectrographic measurements. The average temperature of Tholia
is believed to be around 480o K.
The Tholians are a race of beings that evolved in the searing hot methane environment of
Tholia. Non-humanoid in form, Tholians have crystalline bodies with two exoskeletal arm-
like appendages, and six articulated podia. They dwell in an environment of extreme heat,
their comfortable living environment being 480 o K (206.85 °C). Temperatures below 380o K
(106.85 °C) will kill Tholians, causing them to shatter into tiny crystalline shards.
Tholians are not considered a space-faring civilization since they do not stray much past
their territorial boundaries. They are an extremely territorial race and fiercely isolationist,
guarding their borders against any intrusion with constant patrols. It is not known if the
Tholians are simply not interested in expansion, or biding their time in order to wait for the
appropriate moment so that at the present moment, they are not interested in forming
trade links with the Federation or any other space-faring culture.
The government of the Tholian Assembly is basically a technocracy. It is basically an

assembly composed entirely of scientists and technologists who make all the decisions
concerning the direction of their race. However, not much else is known regarding their
intentions, but it appears that the entire race is of one mindset. That is, the Tholian race is
somehow endowed with a biological collective conscious and appears to have somewhat of
a hive mentality. In addition, there does not appear to be a separate military or civilian
population. The majority of the population is basically omnifarious and its members can
perform any function required of them.
First contact with the Tholians occurred in 2268 when a Starship class vessel was
responding to a distress signal from another Star Fleet ship. When first encountered by
the Federation, Tholian tactics seemed to be based entirely on defense. Their ships seem
to be designed purely for defense as their tactics and weaponry would indicate. Besides
utilizing standard offensive weaponry, Tholian ships can also work in concert to emit an
energy field shaped much like a web, which will trap any space vessel inside and drain its
energy. Two or more Tholian craft would weave their energy web around a ship and tow it
back to one of their bases. When more ships become available, the web takes much less
time to construct; several Tholian vessels working in concert can spin such a web in under
a minute, while two damaged vessels might take hours.
No treaty or agreement between the Federation and the Tholian Assembly exists. The
Tholians are essentially isolationists and do not wish to interact with outside cultures. As
such, they do not pose a direct threat to the Federation at this time. As a precautionary
measure, a Neutral Zone has been established at the conjunction between Tholian and
Federation space and marker buoys have been placed signaling a Code 701 to warn
travelers that this culture seeks isolation.

VOLUME II
Figure 2a31.1
FEDERATION TREATY ZONE SECTORS
000-MARK-000 Sector 001

180o
270 o
Sector 004
Upper Half Sector 005 Sector 003
Sector 004
Sector 002
90o
Sector 005 Sector 003 0o
180o
Sector 002 270 o
Sector 008
Sector 009 Sector 007
Sector 006
Sector 009 Sector 007
Lower Half
Center of Galaxy
Sector 006
90o
0o

VOLUME II
Figure 2a31.2
FEDERATION EXPLORATION ZONE OCTANTS
Treaty Zone
180o
270 o
COMSEC 3
Upper Half COMSEC 4 COMSEC 2
Octant 3
COMSEC 1 90o
Octant 4 Octant 2 0o
180o
Octant 1
270 o
Octant 8 COMSEC 7
Octant 6
Octant 5
COMSEC 8 COMSEC 6
Lower Half
COMSEC 5 90o
0o

VOLUME II
Figure 2a31.3
SYSTEMS WITHIN THE FEDERATION TREATY ZONE
Legend - Hemisphere 180o
Upper (0o – 90o) 195o 165o
Lower (360o – 270o) 210o Marcus II (GLIESE 229) 150o
135o
225o
Federation Treaty Zone 120o

240o
Rigel Colonies (40 ERIDANI A)
Rigel XII (40 ERIDANI B)
Rigel II (EPSILON ERIDANI)

255o Benecia Colony (LALANDE 21185) 105o
Axanar (82 ERIDANI)
Planet Q (WOLF 359) Tau Ceti III (TAU CETI)

Vulcan (UV CETI)
270o 90o
Tantalus V (DEN 1048-3956) Earth-Mars (SOL)
Alpha-Proxima II (PROXIMA CENTAURI) Tellar (61 CYGNI)
Alpha III (RIGEL KENT A)
Centauri VII (RIGEL KENT B) Earth Colony 2 (LACAILLE 9352)
285o
Andor (EPSILON INDII) 75o
60o
300o
Marcos XII (FOMALHAUT-ALPHA PISCIS AUSTRINI)

Altair VI (ALTAIR-ALPHA AQUILAE)
45o
315o
Ophiuchus III (70 OPHIUCHI)
30o
330o Kaferia (DELTA PAVONIS)
15o
345o
0 5 10 15 20
0o
Center of Galaxy
Light-years

VOLUME II
Figure 2a31.4
MEMBER GOVERNMENTS OF THE FEDERATION IN THE EXPLORATION ZONE
Upper (0o – 90o) 195

o
165
o
Lower (360o – 270o) 210

o
150
o
o
o 135
225
o Federation Exploration Zone 120

o
240
o Merak II (Merak – Alpha Ursae Majoris) o

255 105
Izar (Mizar – Zeta Ursae Majoris A)
Makus III (Talitha – Iota Ursae Majoris)
Tiburon (Delta Trianguli)
Orion Colonies (Tabit – Pi 3 Orionis)
Federation Treaty Zone Argelius (Mu Cassiopeiae)
Aldebaran III (Aldebaran – Alpha Tauri)
270o Ariannus (44 Bootis A)
90o
Cygnet XIV (Porrima – Gamma Virginis B)
Elba II (Muphrid – Eta Bootis) Epsilon Canaris III (Iota Pegasi) Malurian System (33 Cygni)
Delta Vega (Vega – Alpha Lyrae) Cygnia Minor (Mu 1 Cygni)

Styris IV (Syrma – Iota Virginis)
Theta Cygni XII (Theta Cygni)
Alpha V Colony (Nu 2 Lupi)
o
o 75
285
Troyius (Tellun System - 37 Pegasi)
o
o 60
300
o
o 45
315
o
o 30
330
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
Figure 2a31.5
NON-MEMBER GOVERNMENTS FRIENDLY WITH THE FEDERATION
Upper (0o – 90o) 195

o
165
o
o
Lower (360o – 270o) 210
o
150
o
o 135
225

o
240
Catulla (Caput Trianguli)
o o
255 105
Antos IV (Phecda)
Capella IV (Alpha Aurigae)
Gamma 7A System (Gamma Leporis A)

Berengaria VII (Kappa 1 Ceti)
Ardana (Alpha 1 Canum Venaticorum) Coridan (Delta Eridani)
Pegasus Colony (85 Pegasi)
270o Denebian System (Deneb Kaitos)
90o
Betazed (70 Virginis)
Organia (Alpha Pegasi)
Ligon II (Zeta Virginis)
Hansen's Planet (41 Arae) Federation Treaty Zone
Beta Antares IV (18 Scorpii)
o
o First Federation 75
285 Epsilon Scorpii
Ingraham B (Delta Equulei)
Levinius V (Epsilon Cygni)
Balok’s Planet
Elas (Tellun System - 37 Pegasi)
Ekos (Epsilon 2 Arae)

Medusa (Gamma 2 Sagittarii) o
o 60
300
o
o 45
315
o
o 30
330
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
Figure 2a31.6
OTHER NON-MEMBER WORLDS WITHIN FEDERATION SPACE
Upper (0o – 90o) 195o 165o
Lower (360o – 270o) 210o 150o
135o
225o
Ceti Alpha V (Menkar – Alpha Ceti)
Federation Exploration Zone

Neural (Delta Leporis)
240o 120o
Planet 892-IV (HD50806 – Canis Majoris) Beta III (Xi Piscium)
Omicron Ceti III (66 Ceti)

Holberg 917G (Eta 1 Pictoris)
255o
Talos IV (16 Ursae Majoris)
105o
Taurus II (Al Haud – Theta Ursae Majoris) Eminiar VII & Vendicar (Revati – Zeta Piscium A)
Daran V (Al Agemim – Eta Cephi)
Sigma Iotia II (Alpheratz – Alpha Andromedae)
270o Gamma Canaris N (51 Pegasi) 90o

Gamma Vertis IV (HD128311 - Bootis)
Thasus (HR5864 - Lupi) Federation Treaty Zone
285o 75o
Omicron IV (Omicron Bootis)
60o
300o
45o
315o
Gamma Trianguli VI (Gamma Trianguli Australis)
30o
330o
o
15
345o
0o 0 50 100 150 200

Center of Galaxy
Light-years

VOLUME II
Figure 2a31.7
COLONIES AND EXPEDITIONS SUPPORTED BY THE FEDERATION
Upper (0o – 90o) 195

o
165
o
o
Lower (360o – 270o) 210
o
150
o
o 135
225

o
240 Dulisian IV Colony (HD15524)
Camus II (HD33632)
o o
255 105
Aldebaran Colony (Alpha Tauri)
New Paris Colony Makus III (Iota Ursae Majoris)
Theta VII(Er Rai)

Tarsus IV (HR753)
Berengaria VII (Kappa 1 Ceti) Janus VI (HD3268)
Haelium Experimental Station (Alpha Fornacis)
Planet Q (Wolf 359) Rigel XII (40 Eridani B)
270o Benecia Colony (Lalande 21185)

Centauri VII (Rigel Kent B)
Pegasus Colony (85 Pegasi)
90o
Risa Resort Colony (59 Virginis) Earth Colony 2 (Lacaille 9352)
Caldos Colony (Iota Antliae) Mariposa Colony (HD114783) Norpin Colony (Gliese 783)
Bringloid V Colony (EQ Virginis) Cygnia Minor (Mu 1 Cygni)
Alpha V Colony (Nu2 Lupi) Deneva (Deneb Algiedi)
Vega Colony (Vega)
Planet M-113 (HD147513)
Ophiuchus III (70 Ophiuchi) o
o Barradas III (Epsilon Serpentis)
285 Midos V (Alpha Circini)
75
Gamma Hydra IV (Gamma Hydrae)
Kessik IV Colony (HD203803)
Beta VI (HD93372)
Exo III (Zeta Lupi)

o
o 60
300
Archanis IV (Epsilon Equulei)
o
o 45
315
o
o 30
330 Sherman’s Planet (HD175529)
o
o 15
345
0o 0 50 100 150 200

Center of Galaxy
Light-years

VOLUME II
Figure 2a31.8
GOVERNMENTS HOSTILE TO THE FEDERATION – LOOKING DOWN ONTO THE GALACTIC PLANE
180o
o o
195 165
o o
210 150
o
o 135
225
Romulan
Federation Exploration Zone Star Empire
o o
240 120
o o
255 105
Romulus
Beta Romii (Delta Andromedae)

270o 90o
Qo’noS
Kazh (HD209149)
o
o 75
285
o
o 60
300 Klingon
Gorn Empire
Empire
S’sgarnon
Theta Kiokis (Theta 1 Crucis) o
Melkot o Ghdar (4 Aquarii) 45
315
Tholia
Melkotian
Realm Tholian Thol (HD121901)
o 30
o
Assembly 330
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
Figure 2a31.9
RELATIVE POSITIONS OF HOSTILE WORLDS – LOOKING FROM THE GALACTIC CENTER
90o
105o 75o
120o 60o
Klingon
o
Empire
45
135o Kazh (HD209149)
Qo’noS

150o 30o
Romulan
Gorn
Empire Star Empire
S’sgarnon
165o Ghdar (4 Aquarii) 15o
Romulus

270o 90o
Tholia
Thol (HD121901) Center of Galaxy
Sherman’s Planet (HD175529) Ceti Alpha V (Menkar – Alpha Ceti)
Tholian 345o
195o Assembly
330o
210o
315o
225o
300o
240o
o
285
255o
Melkotian
Theta Kiokis (Theta 1 Crucis)
Realm 270o 0 50 100 150 200
Melkot
Light-years

VOLUME II
Figure 2a31.10
RELATIVE POSITIONS OF HOSTILE WORLDS – LOOKING FROM THE GALACTIC PLANE
90o
105o 75o
120o 60o
Klingon
45o
135o Empire

150o 30o
Gorn
Empire
15o
S’sgarnon
165o Ghdar (4 Aquarii)

180o 0o Center of Galaxy
Tholia
Thol (HD121901)
Tholian
195o 345o
Assembly
330o
210o
315o
225o
300o
240o
o
285
255o
Melkotian
270o Realm 0 50 100 150 200
Theta Kiokis (Theta 1 Crucis)
Melkot
Light-years

VOLUME II
3.2 OCTANTS, DISTRICTS, REGIONS AND

SECTORS
As stated in Volume I of the Star Fleet Command Manual, the United Federation of
Planets occupies a very small portion of the galaxy. In general, Federation space is
roughly spherical with an approximate diameter of about 450 light-years or 140 parsecs.
This sphere is known as the Federation Exploration Zone and is located in the center
of the Alpha Quadrant of the galaxy. However, the actual size varies from place to place
depending on the extent of exploration in the outer regions, as well as boundary intrusion
into other alien territories.
The function of this section is to illustrate how Star Fleet established its command and
control structure based upon the division of Federation space into the manageable units
that would be under the authority of a Star Fleet Commander. By dividing space into
such units Star Fleet, in effect, developed a “Chain of Command” structure from the
central authority to the outlying areas.
FEDERATION OCTANTS
Federation space is divided into eight primary partitions called Octants or “Primary
Sectors.” An Octant is defined as one-eighth the volume of a virtual sphere defining the
Federation Exploration Zone, which is created by the intersection of three planes of
the orthogonal (Cartesian) coordinate system referred to as the Federation Standard
Coordinate System or SCS. However, the Octant designation is not a formal standard
within the Federation and its only purpose is to group the sectors for assignment to the
eight (8) primary fleets of the Operating Forces outside the Federation Treaty Zone
as required in ARTICLE 62 of the Star Fleet Charter.
From the very beginning of the United Federation of Planets, the Federation Council
had chosen Star Fleet to manage all of Federation space within the Exploration Zone.
To aid Star Fleet in the management of Federation space, the octant principle became a
convenient way of organizing and managing its forces and the volumes of space they must
operate within.
As previously stated, Octants are the primary division of Federation space in which
fleets are assigned. In general, fleets are not assigned to specific areas of space, but to
the large divisions referred to as octants. However, fleets will be further subdivided into
smaller operational units that will be assigned to the smaller areas of Federation space
such as Regions and Sectors.
The management of all forces and assets within an Octant will be under the direction of a
Sector Commandant, as required under ARTICLE 45 of the Charter. That is, each octant
will be commanded by a Sector Commandant, or COMSEC, who will have the rank of
Admiral and who reports directly to the Chief of Star Fleet Operations regarding the
activities occurring within his octant. These commanders have a great responsibility since
they are in command of all the forces and bases within a volume of space equivalent to
about 161,000 cubic parsecs. As such, they rely heavily upon the various Area, Base and
Starship commanders for their support and to carry out the missions and operations
assigned to them by the COMSEC.

VOLUME II
STAR FLEET DISTRICTS
A Star Fleet District is defined as a region of Federation space encompassing any one
of the five Star Fleet Headquarters. That is, the five original signatory worlds of the
Articles of Federation who had originally adjoined all or a portion of their military forces
to create the Star Fleet, and that has a permanent representative on the Federation
Joint Chiefs of Staff (see Figure 1a14.1 in Volume I), will have a key Star Fleet office
located on their home world. All of these Star Fleet Headquarters, and the volume of
space enveloping them, are located within the Federation Treaty Zone and are called
Star Fleet Districts. An illustration of these districts can be seen in Figure 2a32.1.
The purpose for establishing such districts is to maintain a liaison between the member
system governments, their chief military commanders and Star Fleet Command. Each of
the five Star Fleet Headquarters contains offices for the Local Force Commander so
that a close relationship with that force can be maintained, and to keep the commander of
the local force apprised of any changes and developments within the Service. In addition,
such Districts are also liaison centers with the local businesses and manufacturers that
supply Star Fleet. Member system businesses supply the bulk of the materials, equipment
and services to Star Fleet. As such, these district headquarters contain regional offices of
the Star Fleet Bureau of Finance and Accounting to handle the various contracts with
the local manufacturers and for the payment of rendered services.
Star Fleet Districts are also the primary source of personnel for the Service. Each district
headquarters has recruitment facilities located at the base to recruit newcomers into the
Service. These recruitment facilities are fully equipped to completely process recruits into
the Service. Once processed, applicants can then begin recruit training, which is located on
the base. District bases are the primary locations for recruit training and every Star Fleet
Headquarters facility will have a Star Fleet Recruit Training Center within it.
District bases are also the central location for general and specialized fleet training as well.
These bases have extensive training facilities, including a Star Fleet Academy Annex.
As such, local member recruits may be educated at these annexes without having to travel
and live on Earth. Therefore, these bases are the focal point for the training of Star Fleet
personnel within the region.
The Star Fleet commander of such headquarters is called the District Commandant.
However, this role is not the same as that of a Sector Commandant since the authority
of the District Commandant is restricted to the forces within the jurisdictional area of
the base. Basically, the District Commandant is a representative of and acts on behalf
of the Chief of Star Fleet Operations through the Commander: Federation Treaty
Zone as illustrated in Figure 2a32.2. The District Commandant will have the title of
Commandant: <Member System> District (e.g. Commandant: Andor District)
and will typically be an officer of the line (SFC) with the rank of Rear Admiral. The basic
responsibilities of the District Commandant include:
 The support of the Star Fleet in the area

 The recruitment and training of Star Fleet personnel in the region
 The defense of the district and to support the Local Force
 The control of public relations and communications with the local government
 The maintenance of industrial mobilization plans
 The supervision of local legal matters

VOLUME II
STAR FLEET REGIONS
An Octant is a very large volume of space (about 161,000 cubic parsecs) with hundreds, if
not thousands, of star systems and planets, depending on the octant. In order to manage
and defend such a large volume of space, and the forces contained therein, Star Fleet
constructed bases and space stations at strategic locations to function as support centers
for the forces assigned to the region. Any given octant will have several large Star Fleet
bases, called Starbases, placed in areas called Regions throughout its volume. As such,
a Region is defined as the volume of space encompassing a Star Fleet base or station
within the Federation Exploration Zone where the base or station has direct jurisdiction
over everything contained therein as illustrated in Figure 2a32.3. The individual in charge
of the region and who has jurisdiction within the region is called the Area Commander.
The Area Commander is the senior officer of all the forces within that sector, area or
region of space, but not necessarily in command of such forces, except for the ground
troops located within the commander’s jurisdiction. As such, all operational orders to the
forces within the area originate from the Area Commander. However, and in general,
Area Commanders cannot, on their own, initiate operations utilizing any Starship that
may happen to be in the area, but can only relay command orders from higher authority.
In addition, the volume of space commanded by the Area Commander may contain
other smaller stations as well. As such, the Commanding Officers of these stations will
come under direct authority of the Area Commander. These smaller stations have their
own “Sphere of Influence” or “Jurisdictional Authority” as well. Jurisdictional Authority
is defined as the volume of space enclosing a station where the Commanding Officer of
the station is the “Senior Officer Present” and who will have absolute command authority
in that area as defined in Chapter 6000 of Star Fleet Regulations. All vessels, whether
they are private, commercial or military, will come under direct authority of the Station
Commander. The size of the enclosing volume will range depending on the type of the
station as specified below.
Table 2a32.1
STAR FLEET BASE JURISDICTION
Jurisdictional
Station Type Radius
Star Base 1 AU
Station,
Garrison, 160,000 km
Drydock
Outpost 16,000 km
TAC Base,
32,000 km
Communications Station
When a vessel enters this area or orbits around the station, the Station Commander will
have complete authority regarding the location and positioning of the vessel around the
station, and permission must be sought from the Station Commander to orbit around
and visit the station. However, the Station Commander has no authority regarding the
internal operations of any vessel within its area as stated in Star Fleet Regulation 5520.
In terms of the Operating Forces, Fleet Squadrons will customarily be assigned to
Regions since they form the basis for establishing Patrol Areas.

VOLUME II
FEDERATION SECTORS AND AREAS
Federation space in the Exploration Zone is currently divided into 5570 blocks of space
called Sectors. A Federation Sector is defined as a cubic volume of space 20 light-years
on each side and occupying a volume of space of approximately 8000 cubic light-years or
about 231 cubic parsecs. Although a Sector is described here as a right cube, in actuality
it is somewhat curved in order to conform to the general spherical shape of Federation
territory. However, the average distance across any side of a sector will be about 20 light-
years.
Sectors are identified and labeled with a numeric designation, increasing in value the
further it is from Sector 001. The numbering scheme is based upon the ring in which the
sector is contained. A ring is defined as the outer radius of a virtual sphere in 20 light-year
increments away from the center of the Federation. Ring 0 is the outer boundary of the
Treaty Zone or 21.6 light-years from the center of the Treaty Zone, Ring 1 would be
40 light-years from the center, etc. Currently, there are eleven such rings comprising the
entire Federation Exploration Zone.
Sectors are usually planned and identified before any Star Fleet ship has entered the
area. Typically, this is done if an adjacent sector has been explored. However, a sector will
not be considered Federation territory at this point. That is, a Sector can only become
Federation territory when over 50% of its volume has been explored and mapped, and
which has not been claimed by some other system or government. Should the Star Fleet
exploration team encounter another system government within the block of space which
claims jurisdiction, treaties and agreements will be made establishing its boundaries or a
Neutral or Buffer Zone may be created. Should the new Sectors will be designated and
incorporated into the appropriate Octant, and marker buoys placed in and around the
new Sector indicating that it is Federation territory.
Sectors are further divided into smaller cubic Areas. Each side of a cubic Area is about
6.67 light-years or about 1/27 the volume of the Sector. That is, there are 27 Areas to a
Sector as illustrated in Figure 1a51.9 in Volume I. Areas are identified by an alphabetic
designation (A to Z), with the central cube being designated as dash zero (-0) signifying
the central point of the sector. Therefore, the center of, for example Sector 39, would be
labeled 39-0, while an outer area may be designated as 39J. The basic labeling standard
established is that the center area closest to the center of the Federation is labeled “A”,
while the central area farthest from the center is labeled “Z”. This naming convention is
illustrated in Figure 1a51.10 in Volume I of the Star Fleet Command Manual.
To aid the Sector Commandant in the management of his forces throughout the octant
Regional, Sector or Area Commanders are designated and assigned to various regions
of space. The term Area Commander is not a formal title per se, but a convenient way of
designating the “Senior Officer Present” of the area or region of space in accordance with
Star Fleet Regulation 6110.
Also, Star Fleet ships within a fleet will be assigned Sectors and Areas to patrol. In such
cases the Starship Commander will be the “Senior Officer Present” within the sector and
therefore, will be the Area Commander, except where an officer senior to the Starship
Commander is present or where the Star Fleet ship is located in an area of space under
the command of a Starbase or station commander.

VOLUME II
FEDERATION BUFFER AND NEUTRAL ZONES
Federation space contains many volumes or areas of space where travel is restricted,
limited or regulated. These areas are called interdiction or Buffer Zones as defined in
Section 5.1 in Volume I of the Star Fleet Command Manual. The purpose of Buffer
Zones is to separate an area of space from entry into Federation space or to isolate a
planetary system within Federation space.
Section 5.1 in Volume I also defines a special form of political Buffer Zone called a
Neutral Zone. The purpose of a Neutral Zone is to separate the space belonging to a
belligerent power from Federation space. Such zones are called Neutral Zones since
the intervening area of space separating the disputed areas is considered neutral territory
to both sides as established by treaty or agreement. Neutral Zones are generally located
at the periphery of Federation space, whereas Standard Buffer Zones are typically
established within Federation space. In order to monitor these zones for compliance Star
Fleet may place special sensor buoys around the periphery of the zone. In addition, Star
Fleet will also establish outposts along the boundaries of such Neutral Zones in order to
ensure compliance with the treaties that established the zone. The following table lists the
various Buffer and Neutral Zones that are currently being monitored by Star Fleet.
Table 2a32.2
TABLE OF FEDERATION BUFFER ZONES
Buffer Zone Classification SCS Location Range
Separation Area or Year
World Est. Dist.
Type Class Level Vector
(ly)
Elba II Standard Military1 Limited 2262 282-MARK-028 39.1
Gamma Trianguli VI Standard Social Limited 2267 339-MARK-317 183.1
039-MARK-011 144.0
Gorn Empire Neutral Political Restricted 2266
058-MARK-024 198.0
Jaros II Standard Military1 Limited - 015-MARK-043 83.3
355-MARK-345 192.0
Klingon Empire Neutral Military Restricted 2218
098-MARK-009 225.0
292-MARK-308 215.0
Melkotian Space Neutral Political4 Regulated 2268
305-MARK-313 230.0
Neural Standard Social Limited 2268 119-MARK-335 68.1
Omega IV Standard Social Limited 2267 130-MARK-032 91.3
Orion Colonies Standard Commercial2 Limited 2269 162-MARK-341 25.0
Platonius Standard Commercial2 Restricted 2268 257-MARK-037 112.0
098-MARK-022 89.6
Romulan Empire Neutral Military Restricted 2166
133-MARK-009 150.0
Talos IV Standard Social Restricted 2253 207-MARK-037 65.1
Tantalus V Standard Military1 Limited 2258 275-MARK-323 14.3
Taurus II Standard Social Restricted 2266 215-MARK-030 45.3
303-MARK-352 180.0
Tholian Space Neutral Political4 Limited 2269
332-MARK-328 215.0
CLASSIFIED3 Standard Social Restricted 2266 133-MARK-340 220.3
Notes
1. Penal colonies, prisons and institutions regulated by Star Fleet. Access is limited only to authorized
commercial traffic.
2. Established as a punitive measure.
3. The name of the planet is withheld.
4. Established by the Federation. No treaty provisions associated.

VOLUME II
As stated above, to ensure compliance with the designated restrictions marker or signal
buoys are placed around the outer edge of the zone. These buoys mark the location of the
zone and warn approaching vessels with signals indicating the type and purpose for the
zone. Should a vessel ignore such signals and enter a Buffer Zone, the buoy will send a
subspace message to the nearest Starbase and a Starship will be dispatched to the
area.
In terms of operations, Buffer and Neutral Zones are one of the primary areas of space
in which the Operating Forces will be assigned to protect or regulate. As such, these
areas will usually have adjacent Patrol Areas and Patrol Zones assigned to them where
Star Fleet forces will patrol and monitor the zone. See Section 8.5 within this volume for
more detail regarding Patrol Areas. A diagram illustrating the various Neutral Zones
can be found in Figure 2a32.4.

VOLUME II
Figure 2a32.1
STAR FLEET DISTRICTS
25 ly
20 ly
15 ly
10 ly
5 ly
1350
Star Fleet Headquarters - Tellar

1800 900
Star Fleet Headquarters -Rigel

2250 450
Star Fleet Headquarters - Earth Starbase Central
Star Fleet Headquarters - Alpha Centauri
Star Fleet Headquarters - Andor
270
0 00
Galactic Center
3150

VOLUME II
Figure 2a32.2
STAR FLEET DISTRICT CHAIN OF COMMAND
CSFO
Chief of Star Fleet
Operations
ADML
COMSEC0 Commandant:
Federation Treaty
VADM Zone
COMDIST1 COMDIST2 Commandant: COMDIST3 COMDIST4

Commandant: Commandant: Commandant:
Alpha Centauri
Earth-Mars District Rigel District Andor District
RADM RADM District RADM RADM
COMDIST5
Commandant:
Tellar District
RADM

VOLUME II
Figure 2a32.3
ILLUSTRATION OF STAR FLEET REGIONS
Starbase Region Federation Exploration Zone
Octant Slice Starbase

VOLUME II
Figure 2a32.4
FEDERATION BUFFER AND NEUTRAL ZONES
Legend 180o
Star Fleet Regulated o o

195 165
Social Buffer Zone 210

o 150
o
Commercial Buffer Zone o

o 135
225
Standard Neutral Zone Federation Exploration Zone Romulan
o
Star Empire
o
240 120
Omega IV
Talos IV
o o
255 105
Taurus II Orion Colonies
Platonius Neural
Romulan Neutral Zone
o Tantalus V
270 Elba II 90o
Organian Buffer Zone

o
o 75
285 Klingon Neutral Zone
Jaros II
Melkotian Neutral Zone

o
o Gorn Neutral Zone 60
300
Tholian Neutral Zone Klingon
Gorn Empire
Empire
o
o Gamma Trianguli VI
45
315
Tholian
Melkotian Klingon Neutral Zone
Assembly 30
o
Realm 330
o
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
3.3 DESIGNATION OF FLEETS

As previously stated, the primary function of the Star Fleet Division of Operations is
the command and control of the Operating Forces and Shore Establishments of Star
Fleet. In general, the Operating Forces of the Star Fleet basically comprise the various
fleets, flotillas and other groupings of ships. In this section the standard by which ships are
organized and designated into Fleets and Flotillas will be presented.
FLEET NUMBERING
At the highest level, the primary unit of operating forces within Star Fleet is the “fleet.”
As defined in ARTICLE 61 of the Star Fleet Charter, a fleet is the largest operating unit
of Star Fleet, which is composed of several Fleet Squadrons, Groups and other Type
Commands. They are numbered from one (1) to eight (8) based upon the eight primary
divisions or “octants” of Federation space in accordance with ARTICLE 62 of the Charter
which states: “A Fleet shall be assigned, and so numbered, to each primary division of
Federation space. Therefore, there shall be established eight primary Fleets distributed
throughout the eight octants of the Federation.” As such, each primary fleet is designated
according to the octant the fleet was initially assigned: 1ST Fleet, 2ND Fleet, 3RD Fleet,
4TH Fleet, 5TH Fleet, 6TH Fleet, 7TH Fleet and 8TH Fleet.
Although the eight permanent fleets are numbered according to the number of octants as
shown in Figure 2a33.1, fleets are not necessarily assigned to an octant based upon their
designation[2]. This was true, however, during the initial creation of the fleet back in 2207
when the designation scheme was established. But today fleets are constantly being
reassigned or relocated to different octants. This is known as “fleet swapping” or Fleet
Rotation, where the entire fleet in one octant is replaced by the entire fleet of another
octant and vice verse, but their designation will remain intact. As such, Sixth Fleet may
be assigned to Octant 8, but will remain designated as the Sixth Fleet.
As stated above, fleet designations are permanent. That is, the fleets that were originally
created, such as Third Fleet, will always remain as such so long as there is a Star Fleet.
However, the specific ships and ship classes that make-up a fleet will not be permanently
assigned to any specific fleet. Star Fleet will periodically rotate ships from one fleet to
another just as fleets are periodically rotated. This is known as “Fleet Duty Rotation.”
However, what will remain constant is the number and types of ships designed to a fleet,
which is known as the “Fleet Allowance.” The allowance will remain fixed until Star
Fleet Command decides to change the number and class make-up of its fleets.
With regard to permanent fleets, the Director: Star Fleet Command is the only person
who can form and designate a permanent fleet. All other units are formed by the Chief of
Star Fleet Operations or his subordinate commanders. However, during times of war
the Chief of Star Fleet Operations may assemble and designate temporary fleets in
order to accomplish a specific mission. Such fleets may be formed from squadrons and
groups from any of the eight permanent fleets, or may be formed by the combination of
two or more of the permanent fleets into a larger unit called an Armada.
Local Forces also have fleets, but the size of these units will generally be small. However,
since many of the Local Forces may only have a single grouping of ships, the term “the
fleet” is often synonymous with a Local Force.

VOLUME II
FLEET COMMAND
Each fleet is commanded by a Fleet Commander, who will be the Commander in Chief
of that unit. As such, the Fleet Commander is the senior officer of the fleet and will have
precedence over all officers and men within his assigned unit. The Fleet Commander will
typically have the rank of Vice Admiral (SSC) and will be given the title Commander:
<nth> Fleet, with a designation of COMFLT<n>. For example, Commander: 3rd Fleet
will be designated COMFLT3. In general, all Fleet Commanders report directly to the
Chief of Star Fleet Operations through the Sector Commandant of the octant the
fleet has been deployed. Therefore, fleet operational orders to Fleet Commanders come
directly from Star Fleet Command, either directly from Star Fleet Operations or via
the Sector Commandant from the Chief of Star Fleet Operations. As far as his office
is concerned the Fleet Commander will usually be stationed at the same base or location
the Sector Commandant is situated, though the Fleet Commander will also have an
office onboard his Flagship as well. Together, the Fleet Commander and the Sector
Commandant represent force operations for the division of Federation space assigned
to them.
Each fleet is further subdivided into several units called Fleet Squadrons, each of which
commanded by a subordinate Squadron Commander, which are described in more
detail in Section 3.6. In general, squadrons are usually composed of homogeneous groups
of the same class, such as Cruisers or Destroyers, and which are often further divided
into divisions. This type of squadron is known as a “Type Command.” However, a Fleet
Squadron, designated FLTRON, is generally a heterogeneous grouping of combatant and
support vessels as determined by the Fleet Commander. The distributions of the Fleet
Squadrons throughout the Exploration Zone, along with their Home Ports, are shown
in Figures 2a33.5 and 2a33.6.
FLOTILLAS
In addition to the eight primary Fleets, Star Fleet also has two permanent Flotillas as
required under ARTICLE 63 of the Charter. A Flotilla is usually a smaller version of a fleet
and will typically be a grouping of two or more Squadrons into a single unified command.
The term Flotilla comes from the Spanish, meaning a flota of small ships, and from the
French word flotte, or naval flotilla – a small formation of warships that may be part of a
larger fleet. Additionally, a flotilla may also be composed of a homogeneous group of
vessels of the same class, such as destroyers, when three or more Divisions are grouped
together.
Both of these flotillas are located within the Federation Treaty Zone and are distributed
as shown in Figure 2a33.2, with the Home Ports of their respective squadrons shown in
Figures 2a33.3 and 2a33.4. Flotillas are not numbered like the fleets, but continue their
numbering scheme from eight. As such, the two permanent flotillas assigned to the
Treaty Zone are designated as Flotilla 9 and Flotilla 10. Any future designations for
flotillas will continue from the last designation and in increments of ten. For example, the
next permanent flotilla would be designated as Flotilla 20.
A Star Fleet Flotilla, as a general rule, will usually be commanded by a Rear Admiral or
a Commodore, depending on the size and importance of the command. A Flotilla is
often, but not necessarily, a permanent formation.

VOLUME II
Figure 2a33.1
INITIAL DISTRIBUTION OF FLEETS WITHIN THE FEDERATION EXPLORATION ZONE
Federation Exploration Zone Treaty Zone

180o
270o
3RD FLEET
Upper Half 4TH FLEET 2ND FLEET
Octant 3
1ST FLEET 90o
Octant 4 Octant 2 0o
180o
Octant 1
270o
Octant 8 7TH FLEET
Octant 6
Octant 5
8TH FLEET 6TH FLEET
Lower Half
Center of Galaxy
5TH FLEET 90o
0o

VOLUME II
Figure 2a33.2
DISTRIBUTION OF FLOTILLAS IN THE FEDERATION TREATY ZONE
Federation Treaty Zone Sector 001

180o
270 o
FLOTILLA 10
Upper Half
Sector 004
FLOTILLA 9
90o
Sector 005
Sector 003 0o
180o
Sector 002 270 o
Sector 009 Sector 007 FLOTILLA 10
Sector 006
Lower Half
Center of Galaxy FLOTILLA 9

90o
0o

VOLUME II
Figure 2a33.3
DISTRIBUTION OF FLOTILLA SQUADRONS IN TREATY ZONE WITH HOME PORTS – UPPER HALF
Legend 180o
Flotilla Squadron 195

o
165
o
o
Home Port 210
o 150
o
o 135
225
o o
240 120
o o
255 105
FLTRON 4
270o SIGMA STATION SSN-4 90o
o
o 75
285
STAR FLEET HEADQUARTERS ANDOR

o
o FLTRON 2 60
300
o
o 45
315
o
o 30
330
o
o 15
345
0 5 10 15 20
0o
Center of Galaxy
Light-years

VOLUME II
Figure 2a33.4
DISTRIBUTION OF FLOTILLA SQUADRONS IN TREATY ZONE WITH HOME PORTS – LOWER HALF
Legend 180o
Flotilla Squadron 195o 165o
Home Port 210o 150o
135o
225o
STAR FLEET HEADQUARTERS RIGEL
FLTRON 3
240o 120o
255o 105o
270o 90o
STAR FLEET HEADQUARTERS ALPHA CENTAURI

FLTRON 1
285o 75o
60o
300o
45o
315o
30o
330o
o
15
345o
0 5 10 15 20
0o
Center of Galaxy
Light-years

VOLUME II
Figure 2a33.5
DISTRIBUTION OF FLEET SQUADRONS IN THE EXPORATION ZONE WITH HOME PORTS – UPPER HALF
Legend 180o
Fleet Squadron 195

o
165
o
o o
Squadron Home Port 210 150
3RD FLEET 2ND FLEET o

o 135
225
o o
240 FLTRON 32 120
FLTRON 25 STARBASE 27
TANIA STATION SSN-36
FLTRON 34 STARBASE 18 FLTRON 21
FLTRON 33 FLTRON 22
o STARBASE 11 o
255 105
FLTRON 36
FLTRON 24
FLTRON 35 CATULLA STATION SSN-15
STARBASE 19 FLTRON 31 STARBASE 10
STARBASE 3 FLTRON 23
o FLTRON 26
270
CYGNET XIV
90o
STARBASE 1 MALURIAN SYSTEM
FLTRON 41
FLTRON 11 FLTRON 12
STARBASE 4
STARBASE 14
o o
285 FLTRON 13 FLTRON 15 75
STARBASE 25
FLTRON 16
o
o 60
300 STARBASE 20
STARBASE 28
FLTRON 44 FLTRON 14
FLTRON 43
ARCHANIS IV
o
o 45
315 4TH FLEET 1ST FLEET
o
o 30
330
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
Figure 2a33.6
DISTRIBUTION OF FLEET SQUADRONS IN THE EXPORATION ZONE WITH HOME PORTS – LOWER HALF
Legend 180o
Fleet Squadron 195

o
165
o
o o
Squadron Home Port 210 150
7TH FLEET 6TH FLEET o

o 135
225
STARBASE 23
STATION 38SSN-38
FLTRON 73
FLTRON 64
o o
240 120
FLTRON 62
STARBASE 26
FLTRON 71 FLTRON 65
o o
255 STARBASE 7 105
FLTRON 61
STARBASE 15
FLTRON 72
STARBASE 6
FLTRON 75 FLTRON 76 FLTRON 66
FLTRON 63
STARBASE 22
270o 90o
STARBASE 16 FLTRON 52 FLTRON 51
STARBASE 8 o
o STARBASE 13 FLTRON 53 75
285 FLTRON 85
FLTRON 84 FLTRON 54 STARBASE 21
FLTRON 56
FLTRON 86
FLTRON 83 o
o 60
300 DELTA GARRISON SGN-12
STARBASE 24
FLTRON 81
o
o 45
315 8TH FLEET 5TH FLEET
FLTRON 55 o
o
SHERMAN’S PLANET 30
330
o
o 15
345
0o 0 50 100 150 200
Center of Galaxy
Light-years

VOLUME II
3.4 STAR FLEET CHAIN OF COMMAND

Star Fleet Command defines the “Chain of Command” as the line of authority and
responsibility along which orders and directives are passed. This line of command will
generally go from a higher-ranked person who gives the order to the lower-ranked person
who will receive and carry out the order. In an organization, a Chain of Command is the
sequence of commanders who have direct authority and responsibility for accomplishing an
assigned mission of their command while being mindful of the personnel and property in
their charge.
In general, military personnel give orders only to those directly below them within their
chain of command and receive orders from those directly above. For example, a crewman
who has difficulty carrying out an order is likely to be disciplined for not observing the
Chain of Command if he or she skips the officer who has direct authority over them and
directly appeals to a higher-ranked officer within his or her Chain of Command.
The concept of a “Chain of Command” also implies that an individual of higher rank
alone does not entitle a person to give commands. For example, an officer of a given Star
Fleet unit does not directly command individuals of another unit, because that officer is
outside of his Chain of Command. That is, a senior officer can give an order to anyone
below him that is within his Chain of Command, but should not bypass the mid-level
officers. If the officer needs something from a crewmember of another unit, he or she is
generally expected to approach an officer along the chain of command of the other unit.
The aforementioned can be illustrated using the following situation. A Starship assigned
to a Starbase will come under direct authority of the Starbase Commander. However,
the Starbase Commander, or any of his senior officers, cannot give direct orders to any
member of the crew of the attached ship unless it involves the station. Only the Starship
Commander can give such direct orders to his crew. Although assigned to the base, the
Starship does not fall directly within the Chain of Command of the base, but only under
Star Ship Command or Star Fleet Operations. The Starbase Commander will only
have operational authority over the Starship and as such, can only give direct orders to
the Starship Commander.
At its highest level, the Star Fleet Chain of Command starts with the Director: Star
Fleet Command and works downward. However, due to the nature of the office and its
responsibilities, the duties of the Director will normally be delegated to his direct reports
and Division Chiefs. Regarding his responsibility under Star Fleet Regulation 2300 to
organize and maintain an effective force, the Director has delegated this task to the
Chief of Star Fleet Operations. All operational orders and directives to the Operating
Forces and Shore Establishments come from the Chief of Star Fleet Operations as
illustrated in Figure 2a34.1. In effect, Star Fleet Operations is the Chain of Command
for the Operating Forces.
At the outer periphery of the Chain of Command are the Outposts and the Starships,
along with their Commanding Officers. The Outpost represents the outer chain of Star
Fleet authority, and the Starship represents the final or ultimate link of Star Fleet in the
chain and thus, Federation authority.

VOLUME II
STAR FLEET COMMAND ORDERS AND DIRECTIVES
The functions of Star Fleet, as specified in Chapter I of the Star Fleet Charter, are
translated into operational orders and directives issued to the Operating Forces by Star
Fleet Command. Orders and directives usually come in the form of written communiqués
sent down the Chain of Command to all or to specific commands within the Operating
Forces and Shore Establishments. Although some orders may be issued through visual
or verbal means, they are always followed-up with a written copy.
Star Fleet orders and directives have their basis in Federation law. The diagram below
illustrates the basis and hierarchy of the various orders and directives within Star Fleet.
Each level of the pyramid represents an order of precedence for that particular level of a
directive. To illustrate, a Star Fleet Regulation will trump a Star Fleet General Order.
That is to say, a Star Fleet General Order cannot violate Star Fleet Regulations or
any other order, regulation, instruction or directive it is based upon.
Operational
Orders
Star Fleet General

Orders
Star Fleet Regulations
Star Fleet Executive Orders
Star Fleet Charter
Articles of Federation / Federation Law
At a very elementary level, generalized Star Fleet orders come in the form of directives.
In general, a directive is an instruction issued by the Director: Star Fleet Command in
order to fulfill a specific requirement of the Star Fleet Charter, a Star Fleet Regulation
or a Federation policy. A directive is somewhat permanent and can only be rescinded by
the Director or by his successor. Only those holding the position of the Director can
generate or rescind a directive. This is usually performed by amending the directive with a
nullification statement.
The first kind of directive is a Star Fleet Executive Order. These are one-time orders or
instructions given to division directors, commanders and other staff members when the
Department of the Star Fleet was first created. Star Fleet Executive Orders were
issued to define and create the various divisions, bureaus, sections, commands and other
units of the Department of the Star Fleet in order to fulfill the requirements set forth in
the Star Fleet Charter. An example of such an order was Star Fleet Executive Order
6.2, which directed the Chief of Star Fleet Personnel to assimilate the contingents of
the various member forces of the Federation into the Star Fleet Service; to create and
train the Star Fleet Officer Corps and to recruit new members into the Service.

VOLUME II
The next kind of directive is a Star Fleet General Order. General Orders are derived
from the directives issued by the Director: Star Fleet Command to implement the
requirements set forth in the Star Fleet Charter and Star Fleet Regulations. General
Orders, as the term implies, are general instructions pertaining to a specific responsibility
or restriction of Star Fleet and therefore, a General Order applies to all members of the
Star Fleet Service. At the present time there are 29 such General Orders.
An order, on the other hand, is a specific momentary directive or instruction designed to

accomplish a particular mission, assignment or operation. There are two types of orders:
a. Operational Orders – those directives issued to specific commands for the execution
of a mission or other operational objective. These are generally broad in nature and
leave much of the details to the assigned commander.
b. Functional Orders – those directives or instructions issued to perform a specific
operation or assignment. Functional Orders are those issued to individuals to
perform a task or to assign an individual to a command or function.
The central authority for the issuance of Star Fleet operational orders and directives is
Star Fleet Operations and therefore, the primary focus of Star Fleet Operations is the
creation and transmission of Operational Orders. This subject will be treated with more
detail in Chapter 5 of this volume. As such, it is Star Fleet Operations that will assign
ships and vessels to Sectors and Areas, and it is Star Fleet Operations that will assign
missions, operations and exercises to the Operating Forces by means of the Chain of
Command as illustrated in Figure 2a34.1. All such Operational Orders received by any
command, whether visual or audio, will always be followed by an electronic order sent by
subspace radio and inserted directly into the command’s computer system.
The last category of an order or instruction is a command or “Direct Order”. These are
typically verbal directives issued by a superior to a junior describing a task that needs to
be executed. Typically, the method of accomplishing the task or assignment is left to the
discretion of the person ordered. Star Fleet Regulations 8140, 8920 and 5420 deal
exclusively with how such orders and commands are to be carried out.

VOLUME II

VOLUME II
Figure 2a34.1
BASIC STAR FLEET OPERATIONS CHAIN OF COMMAND
Star Fleet Operations

(CSFO)
Sector Commandant COMSEC0
Group Commander Fleet Commander Base Commander Flotilla Commander Base Commander
Starship Commander Group Commander Station Commander Squadron Commander Station Commander
Squadron Commander Outpost Commander Starship Commander
Starship Commander

VOLUME II

VOLUME II
3.5 FLEET REQUIREMENTS

In this section the basic requirements needed to create and maintain an effective Star
Fleet force will be discussed. Fleet requirements are defined as the factors used in
determining the number of operating vessels and the support infrastructure needed to
carry out the objectives assigned to Star Fleet. In general, the size of the United
Federation of Planets requires a large operating force of vessels and personnel. The
requirements for a fleet, its size and the criteria to support such a fleet will be based upon
several factors:
1. The size of Federation space; the volume of space that must be patrolled,
2. The amount of space traffic that must be monitored,
3. The number of active worlds within Federation space, which includes the number of
non-aligned worlds, and
4. The number of hostile worlds and regimes that the Federation must deal with.
As implied above, the size of Federation space will essentially dictate the size of the fleet.
The distances that must be covered at the speeds technically achievable places restrictions
on the ability of Star Fleet to respond to situations within Federation space. As such,
time becomes the greatest factor in determining the criteria regarding the size of the fleet
such that in order to reduce the time to respond, there must be a sufficient force size on
hand to respond to any situation anywhere in Federation space. In addition, the amount
of space traffic also has a direct bearing on the numbers and types of Star Fleet vessels
needed to monitor the space lanes. With over 800 vessels travelling around the Treaty
Zone on a daily basis, a fleet large enough to monitor this amount of traffic and maintain
law and order within the space lanes will be required.
The number of active worlds within the territories of the Federation also has an impact
on the size of the fleet; not only the number of worlds, but their distances as well. This is
primarily so that Star Fleet can protect the many worlds within the Federation. That is,
to have a force size large enough to respond to any situation upon any world within the
United Federation of Planets in order to meet all of its obligations under the Articles
of Federation.
The fact that there are worlds hostile to the Federation makes it imperative that a force
of sufficient size exists to defend the Federation, and that such a force be comparable in
size to such hostile forces, and to counter any action, political or military, these hostile
powers may impose. Therefore, the size of the fleet must be, at a minimum, proportional
to the number and size of the threats against the Federation.
The Office of Star Fleet Ship Planning (SSCPLN) within Star Ship Command is the
office responsible for determining the force needs of the fleet. As such, this office performs
studies and publishes recommendations regarding the current and future size of the fleet.
However, the overall responsibility for determining fleet requirements rests with the Star
Fleet Office of Strategic Planning (SFPLAN) with input from the Office of Star Fleet
Ship Planning. The primary function of the Star Fleet Office of Strategic Planning is
to establish the strategic direction for Star Fleet and the Federation, which includes the
overall size of the fleet, along with the number and location of bases and stations.

VOLUME II
FLEET SIZE REQUIREMENTS
The size of the fleet is primarily dependent upon the distances a ship must travel and the
time allowed for the ship to respond and meet any threat or situation as declared in the
previous page. The primary requirement is the time required to respond to a threat and
have a ship reach the affected area of space within a reasonable amount of time, ready for
action. The ideal situation is to have a Star Fleet ship respond to any condition and to be
on station within 24 hours at maximum safe speed. This would mean that a ship would be
required to cover nearly 6.6 trillion kilometers of space and therefore, would necessitate an
operating range (volume) of about 0.042 cubic parsecs. Considering that the volume of an
octant in the Exploration Zone is roughly 161,000 cubic parsecs, this would indicate that
about 4 million ships would be required to patrol just one octant of space. If this identical
requirement was placed on vessels in the Treaty Zone, which has an approximate volume
of 136 cubic parsecs, the fleet requirement would be almost 3300 ships. Such amounts are
hardly realistic and well beyond the financial capability of the Federation. Therefore, the
requirement was modified in order to be more reasonable and attainable.
The final requirement established by Star Fleet was that a ship should able to respond to
any situation at the periphery of the vessel’s patrol zone in seven to ten days [3], taking into
consideration the huge distances involved. This would make the effective patrol zone of a
Star Fleet vessel at 42 cubic parsecs, or about 7 light-years in any direction. This equates
to about four ships in any octant of the Treaty Zone, or a total of 32 ships to patrol the
entire Treaty Zone. Thus, the two flotillas, required under ARTICLE 63 of the Star Fleet
Charter, would contain approximately 32 vessels.
However, the same criterion could not be directly applied to ships operating within the
Exploration Zone since the distances are simply too great. As such, a different set of
requirements had to be established. The response criterion would now be based upon the
combination of the locations of bases along with their assigned ships. The response time
requirement would remain at 10 days, but taken from a point near the outer edge of the
Exploration Zone. It was decided that vessels would essentially patrol within a volume
corresponding to about 10 percent of the total radius of the Exploration Zone. Since the
Exploration Zone has a radius of about 70 parsecs and takes approximately 32 days to
reach from the center of the Treaty Zone at maximum safe speed, a patrol zone of about
7 parsecs from the edge of the Exploration Zone was established, which is equivalent to
the breadth of one cubic sector. As such, this would allow Starships to quickly respond to
any emergency and reach the affected area within 48 hours at its maximum speed. Hence,
the number of Starships (combatants) was based upon the distance they can effectively
travel within a time frame of about 48 hours.
The effective distance a Starship can travel at maximum Warp in two days, considering
time distortion, is approximately 10 parsecs or roughly 33 light-years. Using this figure, the
number of Starships necessary to patrol an octant within the Exploration Zone was
determined to be 38. This sums up to be a total combatant force of 340 line Starships,
including the forces within the Treaty Zone. As such, this number of ships became the
initial force size target. However, as the size of the Federation increases, the number of
ships required to protect Federation space must also increase. As such, Star Fleet has
established that for every 1500 cubic parsecs of new space added to the Federation,
another line Starship must be added to the fleet.

VOLUME II
BASE AND FLEET SUPPORT REQUIREMENTS
The requirements for a Star Fleet force must also take into account the number of bases,
stations and other facilities needed to support the size of the fleet and therefore, the base
and support requirements are directly related to the fleet requirements. In general, the
requirement for the number of bases and stations is based primarily upon the time and
distance required to efficiently send and receive communications with the fleet. As such,
Star Fleet has set, as a standard, the maximum distance between any base or station to
be based upon a maximum communication range by subspace radio of 48 hours or ten
days by message drone. Therefore, Star Fleet originally set the distance between bases
at 22.65 light-years or about 6.95 parsecs. However, this would establish a base Region
volume of approximately 1405 cubic parsecs and as such, would require 115 bases to be
constructed per Octant, or a total of 920 bases to cover the entire Federation. This is
also an unrealistic goal and well beyond the financial resources of the Federation.
The solution to this problem was the development of the Subspace Relay Station, which
house signal amplifiers that basically processes a message packet and then resends it in a
very fast and efficient manner. By placing such relay stations at strategic locations
throughout Federation space, the distance between bases could be extended. As a result,
Star Fleet established the optimal the distance between bases at 21.72 parsecs or
roughly 71 light-years – effectively tripling the distance, thereby requiring only four major
Starbases per Octant, or a total of 32 Starbases to cover the entire Federation.
However, it should be noted that the distances between these bases are still large and
Star Fleet ships travelling at maximum warp from one base would take approximately a
week to reach another base. Therefore, it was determined that smaller space stations
would also be needed in order to fill the gap.
Although the above requirement works well in terms of communications, Star Fleet ships
would still be required to travel vast distances to reach these bases. Therefore, to fill the
gap between the bases and the outlying areas smaller stations will be required. Star Fleet
analyzed the situation and taking into consideration the configuration and placement of the
Starbases, it was determined that an additional six intermediate space stations per octant
will be required. This amounts to a total of 48 station units, based upon the current size of
the Federation. And as with the expansion rule for ships, this current value will change as
the size of the Federation increases.
At the outer edge of the Federation Outposts and Garrisons would be located which
would signal the boundary of Federation space, and which would provide protection from
invading forces. As such, there is no requirement regarding the number of Outposts and
Garrisons needed to support the fleet. The number of such units will be based solely on
need. In addition, where multiple Outposts are to be located the rule of thumb for the
placement of such stations is to set the distance between them equivalent to one hour at
normal warp speeds or approximately two seconds via subspace radio.

VOLUME II
CONSTRUCTION REQUIREMENTS
The number of ships, bases and stations needed to maintain an effective force contributes
to the size of the construction force needed to build these assets. Initially, 220 ships were
incorporated into Star Fleet from the member worlds. However, most of these ships were
remnants of the Romulan War and were truly not up to the task given to Star Fleet. In
addition, the Articles of Federation mandated the construction of a new class of vessel.
Therefore, considering a force requirement of 340 line warships, 120 additional warships
had to be built to meet this target. As such, the additional ships would be composed of the
newly designed Starship class. The plan was that as the new Starship class vessels were
being commissioned and incorporated into the fleet, the older ships would be phased out.
Therefore, a requirement had to be established regarding the number of ship construction
facilities that would be necessary in order to meet the force size goals.
To meet the force size requirement, Star Fleet had established the requirement that any
ship-building facility must be able to construct or work on four combatants simultaneously,
and that at least two ships must be placed in service each year until the appropriate force
size is achieved, which was estimated to require ten years. This equates to a new ship
entering service every six months. Considering these requirements and the fact that it
takes approximately 3.8 years to build and launch a new line Starship, it was determined
that a minimum of six construction facilities would be required to meet this goal. The
general process for new construction of ships is that the core vessel will be built at the
construction facility, and then later moved to a Drydock or mobile repair facility for
completion. This allows for a higher volume of new ships to be built.
Another consideration regarding the Star Fleet vessel support force is that the vessels
currently in service require constant maintenance. As such, the requirement for repair
facilities depends upon the refit and repair rate of Star Fleet ships. At the present time
the repair rate for Star Fleet ships is approximately 1 in 20, or about 5% of the fleet. In
addition, Starships will generally require overhauling every five to seven years, which is
usually scheduled at the end of a standard patrol cycle. The reason for this refit rate is that
many Starships on patrol are fully engaged in many activities that demand a lot from the
ship, with little time allowed for periodic refitting or major servicing. Therefore, based
upon this rate, about 17 Drydocks or repair facilities would be needed to accommodate
this refit requirement. However, unlike the repair rate, the overhaul rate is not significant;
only about 2.5% of the fleet will be out of commission in overhaul at any one time during
any fiscal year. This will require an additional two construction facilities and a number of
Drydocks that will need to be built and stationed at key locations within the Federation
Exploration Zone for minor ship maintenance and refitting.
The requirements regarding the size of the construction force also extends to bases and
stations as well. For example, the size of the workforce needed to build bases on planets.
However, this force does not necessarily require a large permanent organization. In the
majority of cases local labor will temporarily be utilized to build such assets. On the other
hand, the construction of self-contained stations typically requires a large construction
facility. As such, the construction facilities used to build ships will also be used to construct
Outposts and deep-space stations. In general, a station takes approximately 3.1 years to
construct, while an Outpost usually takes about one year for a free-floating station and
about eight months for one to be constructed inside an asteroid.

VOLUME II
3.6 FLEET COMPONENTS

A fleet is the largest organization of ship units within the Operational Forces of Star
Fleet that is under a single command structure. Star Fleet has eight permanent fleet
units within the entire organization as required under ARTICLE 62 of the Star Fleet
Charter. Each fleet has approximately 53 ships containing 37 combatants and about 16
support vessels. In this section the components that make up a fleet will be discussed. At
first the elements that compose a typical fleet, the ship types, will be presented. Next the
organization of these elements will be described.
Fleets are generally composed of discrete assemblages of vessels such as Squadrons,

Groups or Divisions. The eight permanent fleets are made up of seven operational units,
six of which are Fleet Squadrons and the seventh being the Command Group as
illustrated in Figure 2a36.1. The Command Group is the operational center of the fleet
from which all operational orders to the fleet will originate. It contains the Flagship and
several ships that support the fleet. At the heart of the Command Group, the Flagship
contains the office and staff of the Fleet Commander. In addition to the attached Fleet
Squadrons, the Fleet Commander may also organize his ships into Task Forces or
other groupings for the purpose of completing a specific military mission. Such vessel
groupings will typically be employed during wartime and is not a normal subdivision of a
fleet during peacetime conditions.
At an elementary level, Star Fleet ships are divided into two major types: Combatants
and Support Ships, both of which can be further divided into functional classes, which
will be described in more detail in Section 6.3 of this volume. The eight permanent fleets
are composed of ships from virtually all of the available classes of Star Fleet combatants
and support vessels, each of which comprise an element of a fleet, and who has a specific
function to perform based upon the size, power, speed and armament of the vessel or its
role in supporting the fleet. Therefore, a fleet is composed of or may be subdivided into
several types of constituent units, which are referred to as the components of the fleet.
These components are defined in the following table.
Table 2a36.1
FLEET COMPONENT DEFINITIONS
Component Designation Definition
Division <class>DIV A grouping of two or more vessels of the same type or class.
<class>RON A unit of vessels; a grouping of two or more Divisions when
Squadron
FLTRON<n> grouping vessels into Type Squadrons.
The elementary part of a fleet or unit; typically, a vessel. Also, a
Task Element TF<X.Y.Z.n>
subdivision of a Task Unit as in a Task Element.
An assemblage of two or more elements; a subdivision of a Task
Task Unit TF<X.Y.Z>
Group as in a Task Unit.
An assemblage of two or more squadrons; an assemblage of two
Task Group TF<X.Y> or more units of a Force; a subdivision of a Force as in a Task
Group.
A major operational command within a Fleet; units temporarily
Task Force TF<X> assembled together for a specific task or mission as in a Task
Force.

VOLUME II
SHIP DIVISIONS
A ship Division is a grouping of two or more vessels of the same class. The basic function
of a division is to group together a class of ship primarily because the class of ship will
determine its primary mission and therefore, will be given specific mission assignments
based upon the capabilities of that class of vessel. Divisions are designated by the class
of ship that comprises the division. For example, a Cruiser Division will have the label
CRUDIV and will be commanded by a Division Commander, who will normally be the
senior Commanding Officer of all ships within that division. For temporary divisions,
such as during fleet action, the senior Commanding Officer of the division will not have
a Division Commander’s title, but will simply be called “Commander”. In general, the
term Division Commander is not usually a formal title per se, but a job description given
to the senior ship commander of the division. However, Star Fleet maintains several
permanently assigned divisions with a formal Division Commander as illustrated below.
Table 2a36.2
STAR FLEET SHIP DIVISION DESIGNATIONS
Ship Division Designation Type Commander
Cruisers CRUDIV <n> Commander: Cruiser Division <n>
Supply and Fuel Ships SUPDIV <n> Commander: Supply Ship Division <n>
Repair Ships REPAIRDIV <n> Commander: Repair Ship Division <n>
Survey Ships SURVDIV <n> Commander: Survey Ship Division <n>
Freighters FREIGHTDIV <n> Commander: Freighter Division <n>
FLEET SQUADRONS
The term Fleet Squadron is used to define a grouping of Star Fleet ships that subdivide
a fleet into smaller, manageable units. As such, a Fleet Squadron is a grouping of several
divisions of ships of differing types as illustrated in Figure 2a36.2. In general, each fleet is
divided into six Fleet Squadrons, each containing six line combatants and about two to
three support vessels. In addition, since Fleet Squadrons are a subdivision of a fleet they
will be numbered and designated by the fleet to which it is a part. For example, a specific
squadron within Third Fleet may have the designation of Squadron 31 or FLTRON 31.
The purpose of a Fleet Squadron is to assemble ships into operational units that can be
deployed together to specific areas of a Federation octant. Since octants are so vast, it is
easier to monitor fleet operations regionally by groups instead of individually. Therefore,
each squadron will be assigned a sector or group of sectors to patrol. However, the ships
composing the squadron will typically be dispersed throughout the assigned patrol sector
or throughout several sectors. This allows for a decentralized command of fleet elements
through the use of a Squadron Commander.
A Fleet Squadron will be commanded by a Squadron Commander, who will typically

be the senior Commanding Officer of the largest ship in the squadron – generally a
Heavy Cruiser. As such, he will typically have the rank of Commodore, and will be
given the title of Commander: Fleet Squadron <n> or COMFLTRON<n>. All other
Starship captains within the squadron will report directly to the Squadron Commander,
unless detached to perform a special operation by Star Fleet Command. The Squadron
Commander reports directly to the Fleet Commander in which his squadron is
attached[4].

VOLUME II
TYPE SQUADRONS
A Type Squadron is an assemblage of two or more Divisions into a unit called a “Type
Command” and is composed solely of vessels of the same type or class as illustrated in
Figure 2a36.4. This designation is not the same squadron grouping of vessels as a Fleet
Squadron, which is a permanent subdivision of a fleet. Typically, this type of grouping will
be used in the formation of ships of the same type that are engaged in a common mission,
such as fleet support. Such Type Squadrons will usually be composed of support class
ships like Supply or Repair ships. For instance, a squadron of Supply Ships will always
be assigned to support a fleet.
Type Squadrons are numbered and designated by Star Fleet Operations. For example,
a squadron of Destroyers may have the designation of Destroyer Squadron Five or
DESRON 5. The commanders of such units are called Type Commanders and will have
the title of: Commander <Ship Type> Squadron <n> or <Type>RON <n>. As with
other squadrons, the Type Commander will usually be the most senior Commanding
Officer of the ship within the Type Squadron. Table 2a36.3 below lists most of the more
common squadron types.
Table 2a36.3
STAR FLEET SHIP TYPE SQUADRON DESIGNATIONS
Ship Type Designation Type Commander
Destroyers DESRON <n> Commander: Destroyer Squadron <n>
Supply and Fuel Ships SUPRON <n> Commander: Supply Squadron <n>
Repair Ships SERVRON <n> Commander: Service Squadron <n>
Survey and Laboratory
EXPLORON <n> Commander: Exploration Squadron <n>
Ships
Freighters FREIGHTRON <n> Commander: Freight Squadron <n>
Transports TRANSRON <n> Commander: Transport Squadron <n>
Where more than one class of ship may be assigned to a Type Squadron the lead
command ship determines the squadron designation. For example, a squadron that
contains Supply, Fuel and Repair ships will be designated as a SERVRON or Service
Squadron since the squadron serves the fleet, and the lead class of vessel will be the
Repair ship.

VOLUME II
FORCE COMMANDS
In general, a Force is a smaller or more specialized grouping of vessels than a fleet. As

such, a Force will generally be assembled from fleet units under the command of a Force
Commander.
TASK FORCE
A Task Force is a specific type of force and is a major grouping of ships within a fleet
designed to achieve specific large-scale military objectives. Task Forces are temporary
assemblages of several Fleet Squadrons, Type Commands and other assemblages or
units in order to create a single unified command structure for the achievement of a major
goal or mission as illustrated in Figure 2a36.6. During times of war Task Forces may be
assembled from units of several fleets in order to accomplish broader, more extensive
operations. The primary components of a Task Force, their designations and command
titles, are defined in the table below.
Table 2a36.4
STAR FLEET TASK FORCE DESIGNATORS
Force Unit Designation Commander
Task Force Task Force <n> Commander: Task Force <n>
Task Group Task Group <n> Commander: Task Group <n>
Task Unit Task Unit <n> Commander: Task Unit <n>
A Task Force will normally be created and designated by the Fleet Commander should
he receive orders to accomplish a large-scale operation. However, during wartime and for
large operations, Task Forces will be created and designated by Star Fleet Operations.
The typical designation for a Task Force will generally be a number assigned to it by Star
Fleet Operations, which maintains the designations of all units of the Operating Forces
for Star Fleet. This number is a linearly increasing value starting with one. For example, if
the Commander: Forth Fleet has a mission to perform some operation, the Task Force
may be designated Task Force 41. As such, the tactical command designation for this
unit will be Task Force 41 or TF41.
Units contained within the Task Force will inherit the command designation of the force.
For example, a Task Group within the force that is assigned a specific task to perform for
the overall operation will have the designation of TF41.2. The commander of such a group
will have the title of Commander: Task Group <n> or COMTSKGRP<n>. Task Units
within this group will be designated TF41.2.1, and elements (Task Elements) within this
unit will have the designation TF41.2.1.<n>.
A Task Force is essentially an administrative organization that manages the operations of

the various operating commands, each under the command of a Type Commander. As
such, the commander of a Task Force will be designated as a Commander-in-Chief of
the unit and will typically have the rank of Vice Admiral. The title of this commander will
be Commander: Task Force <n> as defined above. The Task Force Commander has
tactical command of the operation and will direct and deploy his forces has he sees fit in
order to accomplish the mission.

VOLUME II
GROUP COMMANDS
In general, a Group is a temporary assemblage of vessels created to perform a specific

task. A Group will contain a mixture of ships of differing classes and as such, will be made
up of several Divisions or Squadrons, each of which would be defined as a Group Unit,
while each individual ship within the group would be defined as a Group Element. The
commander of such groups will typically have the title of Commander and will usually be
of flag grade.
TASK GROUPS
A Task Group is a major subdivision of a Task Force and will typically comprise a Type
Command as illustrated in Figure 2a36.6 which therefore, forms the basic operational unit
of a Task Force. The basic function of a Task Group is to provide the Task Force with
the appropriate types and numbers of Task Elements necessary for the Task Force to
complete its mission. In general terms, a Task Group is basically a Type Command that
essentially divides the Task Force into specific functional or operational units.
BATTLE GROUPS
Star Fleet also has five standing or permanent Battle Groups, designated BATGRP1 to
BATGRP5 (BG1 - BG5) independent of the eight fleets. The function of these groups is
to project power to a belligerent government and to provide an immediate strike force
should trouble occur. Each Battle Group will be assigned a sector to patrol on a rotational
basis. That is, a Battle Group is assigned a patrol a sector for a specified period of time,
usually around nine months, before it is moved or assigned to another area, or is relieved
by another Battle Group. Typically, Battle Groups will be assigned to sectors or areas
near Neutral Zones close to potential trouble areas. However, at least one Battle Group
will always be assigned to Sector 001. When not patrolling a sector, a Battle Group will
typically “anchor” near its assigned Sector Starbase for an extended leave period.
Each of the five Battle Groups is made up of nine combatants and two support ships,
with the primary capital ship being the Attack Carrier as illustrated in Figure 2a36.3. An
Attack Carrier is a large, flat vessel containing several hundred Attack, Interceptor or
Fighter craft used for long-range combat, attack and reconnaissance missions. Attack
Carriers usually serve as the flagship for the Group Commander. Flanking the carrier
are typically two Light Cruisers, or Heavy Frigates, used to protect the carrier against
enemy combatants. They are also used to support troop landings on hostile planets by
laying down suppressive fire on surface targets while the troops are being deployed to the
surface. Protecting the group is an assortment of Destroyers and Escort ships used as
screening vessels for incoming fighter attack.
A Battle Group is commanded by a Group Commander who maintains an office aboard

the flagship and is always with the group. The Group Commander will have the rank of
Rear Admiral and will have a title of Commander: Battle Group <n>, designated as
COMBATGRP<n>. For example, Commander: Battle Group 1 will be designated
COMBATGRP1. In most cases the Group Commander reports directly to the Chief of
Star Fleet Operations through the Sector Commandant of the sector his group is
currently assigned. As such, group operational orders will come directly from Star Fleet
Command to the Group Commander, either directly from the Chief of Star Fleet
Operations or through the Sector Commandant.

VOLUME II
GROUND FORCE ORGANIZATION
Regarding ground troops, the term Division is also used to define a grouping of two or
more Brigades, which is equivalent to about 12,000 ground soldiers. This definition of a
division will be used exclusively by the Star Fleet Marine Corps for the organization of
ground troops, which is defined in ARTICLE 70 of the Star Fleet Charter. The primary
components of ground forces, as well as their designations and commanders are defined in
Table 2a36.5 below.
The primary and largest unit of troops within an octant is the Division. As such, each and
every Starbase and Star Fleet Garrison within an octant will contain at least one troop
Division that will comprise the ground force for the region. The commanders of Marine
Divisions are usually Rear Admirals and will be given the title of Commander: <n>
Marine Division or COMDIV <n>.
In command of all the forces within any octant is the Commander: Sector Fleet Marine
Force or COMFOR. As such, all base and station Marine Corps commanders within the
octant will report to him. The COMFOR reports directly to Star Fleet Operations and
therefore, all operational orders for the Fleet Marine forces in the octant will come
directly from Star Fleet Command, either directly from the Commandant: Star Fleet
Marine Corps, the Chief of Star Fleet Operations or via the Sector Commandant.
The commander of the octant’s ground force will typically be a line officer from the Fleet
Marine Corps with the rank of Vice Admiral, and will have the title of Commander:
Sector Fleet Marine Force <n> or COMFOR <n>.
Table 2a36.5
STAR FLEET GROUND FORCE DESIGNATORS
Force Force Typical
Designation Commander
Unit Size Rank
<n> Marine Corps or Commander in Chief: <n> Corps or Admiral or
Corps 60,000
Fleet Marine Force <n> Commander: Fleet Marine Force <n> Vice Admiral
Division 12,000 <n> Marine Division Commander: <n> Marine Division Rear Admiral
Brigade 4,000 <n> Marine Brigade Commander: <n> Marine Brigade Commodore
Regiment 2,000 <n> Marine Regiment Commander: <n> Marine Regiment Captain
Battalion 1,000 <n> Marine Battalion Commander: <n> Marine Battalion Commander
Company 250 <n> Company Company Commander: <n> Company Lieutenant
Platoon 60 <n> Platoon First Lieutenant: <n> Platoon Lieutenant JG
Squad 10 None Squad Leader
Ground forces will typically be deployed to a planet using a Ground Assault Force. This
is a grouping of ships with a Ground Assault ship (GG class) as the flagship. The
Ground Assault ship will usually be surrounded by about seven combatants used to
protect the force and to initiate ground operations by laying down ground fire onto targets
on the planet’s surface. An illustration of such a force can be seen in Figure 2a36.5.

VOLUME II
Figure 2a36.1
TYPICAL FLEET ORGANIZATION
Squadron 5
Squadron 3
Flagship
Squadron 1 Squadron 6 Command Group
Squadron 2
Squadron 4

VOLUME II
Figure 2a36.2
TYPICAL FLEET SQUADRON ORGANIZATION
Destroyer Escorts
Frigates Squadron Support Ships
Squadron Flagship
Fleet Squadron

VOLUME II
Figure 2a36.3
ATTACK CARRIER BATTLE GROUP
Carrier/Flagship

VOLUME II
Figure 2a36.4
TYPE SQUADRON (SUPPLY SHIPS)

VOLUME II
Figure 2a36.5
GROUND ASSAULT FORCE
Assault Ship/Flagship

VOLUME II
Figure 2a36.6
ILLUSTRATION OF THE TYPES OF COMMAND UNITS COMPRISING A TASK FORCE
Force Commander
Flag Lieutenant Flag Secretary
Chief of Staff
Fleet Squadrons Operations Logistics Communications Intelligence

Group Commands
Flag Commander Flag Commander
Flag Lieutenant Flag Secretary Flag Lieutenant Flag Secretary
Chief of Staff Chief of Staff
Operations Support Communications Tactics

Task Force Operations Support Communications Tactics
Ship Commanders Ship Commanders
Type Commands Ground Assault Commands

Type Commander Flag Commander
Flag Lieutenant Flag Secretary Flag Lieutenant Flag Secretary
Chief of Staff Chief of Staff
Operations Logistics Communications Services Operations Support Communications Troops
Ship Commanders Ship Commanders

VOLUME II
3.7 FLEET DEPLOYMENT

Fleets are assigned to octants as required under ARTICLE 62 of the Star Fleet Charter,
but the actual deployment of a fleet (or elements thereof) within an octant will be based
upon the strategic requirements within the octant as mandated under ARTICLE 69 of the
Charter. As such, the Fleet Commander will receive generalized instructions regarding
the basic mission of the fleet within the assigned octant. It will then be up to the Fleet
Commander to decide how his forces will be deployed or situated within the octant, while
meeting the goals set down within the confines of his generalized orders. This principle will
also apply to the commanders of the five Battle Groups, as well as to any commander of
a large force.
A Fleet Commander will generally deploy his forces throughout the octant in a matrix or
lattice configuration as illustrated in Figure 2a37.1. That is, since a standard fleet contains
six Fleet Squadrons, each squadron will be deployed into six perpendicular nodes around
the central Command Group. As previously state, the Command Group contains the
fleet Flagship, which will direct all operations of the squadrons within the fleet from this
central location. As part of the deployment, the Fleet Commander will issue instructions
to his or her Squadron Commanders as to the nature of the mission or goals to be
accomplished within the assigned area, and the duration of the assignment.
The Fleet Squadron Commander will also deploy his or her forces in a similar manner
like that shown for a fleet as illustrated in Figure 2a37.1. The squadron Flagship will act
as the central command of the squadron and like the Fleet Commander, will direct all
operations concerning the squadron from this central location. However, unlike the fleet
Flagship the Squadron Flagship will also be engaged in the same general activities as
the Starships within the squadron. That is, the Squadron Flagship will perform such
duties as exploration, patrol and all the other duties assigned to Starships, based upon
the mission assigned to the squadron.
The Squadron Commander will generally deploy his forces by assigning Patrol Areas
to the ships within his command. Patrol Areas will generally be located near Buffer and
Neutral Zones. Ships deployed to these areas will have the primary function of patrolling
and monitoring the area. As such, the Commanding Officer of these ships will act as the
Area Command within those regions. A more detail discussion of Patrol Areas can be
found in Section 8.5 of this volume.
During wartime, fleet deployment may be handled by Star Fleet Operations or by a

Commander in Chief. In the case of Star Fleet Operations, the basic deployment
strategy would be handled within Mission Control and generalized instructions to the
Fleet Commander regarding force deployment will be issued from that location. The
Fleet Commander, in this instance, would be in overall Tactical Command of the
operation, issuing Operational Orders to his Unit Commanders. For large operations
involving Armadas or large Task Forces, the Commander in Chief or CINC of the
force will have Operational Command of all the forces within his force. The CINC will
deploy his or her forces as required to fulfill the missions to which he or she is assigned.

VOLUME II
FLEET ROTATION
Fleet Rotation is the reassignment of the entire fleet from one octant to another octant,
or when large portions of a fleet, such as a Squadron, may be reassigned to another fleet
or octant. Today, fleets are periodically reassigned or relocated to different octants. This is
known as “fleet swapping” or Fleet Rotation, where the entire fleet in one octant will be
exchanged with the entire fleet of another octant. Although assigned to a different octant,
the designation of the fleet will remain intact. In general, the rotation schedule of fleets
will normally be developed by Star Fleet Operations and will usually be kept a secret.
However, Fleet Rotation may also be instigated by the Chief of Star Fleet Operations
or the Director: Star Fleet Command at any time.
The basic function of Fleet Rotation is diversity in mission and operations. What is meant
by diversity in mission can be explained in the following rationale:
1. To keep hostile and enemy forces off-balance; to confuse them as to the nature, size
and capabilities of the forces in the area. When forces close enough to be observed by
enemy forces are continually present, the enemy may develop a familiarity with the
routine and operating patterns of that force to the point where the actions of the
commanders of Star Fleet forces may become predictable. To mitigate this possibility,
forces will be replaced with other commands on an irregular or unpredictable schedule.
2. To provide the crews and personnel of Star Fleet forces diverse experiences. If ships
and their crews continuously perform the same duties and missions in the same area,
boredom may develop. Missions will simply become mundane tasks, which may result
in ambivalence to the mission and the Service. Therefore, Star Fleet strives to
provide its personnel with a wide range of experiences. Fleet Rotation, therefore, is
another method of providing crewmembers with new experiences, which will enhance
their understanding of differing cultures and increase their ability to handle new and
challenging situations.
Rotation will also occur within fleets as well. The Fleet Commander and the Squadron
Commander will periodically rotate the forces within their respective commands for the
identical reasons stated above, utilizing a fixed or variable rotation schedule. The rotation
schedule is completely up to the commanders, but in general a rotation schedule of six to
twelve months is typical. Each commander will usually create a Rotation Plan, which
outlines the location, timing and basic mission of the forces under their command. Figure
2a37.2 provides an illustration of such a rotation plan.
The same rotation philosophy also applies to other types of forces as well. For example,
each Battle Group will be assigned a sector on a rotational basis. That is, a Battle
Group may be assigned to patrol a sector for a specified period of time, usually around
nine months, before it is moved or reassigned to a different sector, or is relieved by
another Battle Group. Typically, Battle Groups are assigned to sectors near Neutral
Zones or areas of potential trouble, as determined by Star Fleet Operations. But at
least one Battle Group will always be assigned to Sector 001. When not patrolling the
sector, a Battle Group will typically “anchor” near the Sector Starbase for an extended
leave period. This gives the crews of Battle Groups the needed rest and relaxation from
an extended tour, and provides ample leave opportunities for crews to rejoin family and
friends.

VOLUME II
Figure 2a37.1
GENERALIZED MATRIX DEPLOYMENT OF A FLEET
Fleet Command Group Squadron Command
Command Unit: Starship

VOLUME II
Figure 2a37.2
BASIC FLEET DEPLOYMENT AND ROTATION PLAN
Command Unit Center of Federation

1
Command Group
4

VOLUME II
3.8 ORGANIZATION OF SERVICE CRAFT

The word ship is a general term for any large vessel which moves through space under its
own power. Craft, on the other hand, are essentially small ships. As such, there is no
absolute distinction between the two, since they both are space-worthy vessels that carry
a crew, weapons and material. The only real distinction between the two is range and
speed. However, to make the distinction Star Fleet has defined a craft, or Service Craft,
as a small vessel which can be loaded onto a ship or station, or that can land on a planet
and housed at a base. A complete description of the types and classes of Service Craft
can be found in Chapter 2 in Part 6 of Volume V of the Star Fleet Command Manual.
The organization responsible for service craft operations, as it applies to fleet service, is
the Star Fleet Service Craft Command (CRAFTCOM). The function of CRAFTCOM is
to manage the entire operating fleet of Star Fleet Shuttlecraft, Fighters and other
forms of craft used for functional operations. This, however, does not include any craft
used at facilities under the command of the Star Fleet Division of Engineering. In
addition, CRAFTCOM will also determine what types and classes of craft will be needed to
support fleet operations and will make requests to the Star Fleet Service Craft Systems
Command for the construction or allocation of such craft and lastly, will assign such craft
to Star Fleet units.
CRAFTCOM is also responsible for maintaining the Service Craft Register as well. As
such, CRAFTCOM is responsible for developing the numbering and designation systems
for every craft in the fleet, including those used by Star Fleet Engineering. However, it
is not responsible for the organization or grouping of craft used by that division.
GENERAL CRAFT ORGANIZATION
As with Star Fleet ships, craft of the Star Fleet are also organized into groups. However,
unlike ships, craft are not grouped into divisions. The smallest grouping of Service Craft
is the Squadron, a grouping of four or more service craft of the same type. Therefore,
Service Craft are only organized by type. There are no mixed grouping of craft as with
fleets and ship groupings. The following table defines how service craft are organized.
Table 2a38.1
SERVICE CRAFT ORGANIZATION STANDARD
Commander in Chief
Unit Definition
Title Rank
The smallest operational grouping of Star Fleet Service Craft. A
Commander:
Squadron is composed of four or more craft of the same class
Squadron <Craft Type> Commander
or type. Squadron designations are typically two or three digit
Squadron <n>
values.
A grouping of two or more Squadrons of the same type of
Commander:
service craft. If the Group is attached to a wing, the numerical
Group <Craft Type> Captain
designation will be a two-digit value with the Wing number up
Group <n>
front.
An assemblage of two or more Groups. In this case a Wing
Commander:
may contain Groups of differing craft types, or may be several
Wing <Craft Type> Commodore
groups of the same type. A Wing is generally organized at large
Wing <n>
Starbases and Garrisons.

VOLUME II
CRAFT ORGANIZATION DESIGNATIONS
Service Craft groupings are designated and numbered according to type. CRAFTCOM is
the only organization that develops and assigns craft groupings and as such, maintains the
designations for such groupings. The standard for designating craft groupings is illustrated
in the table below.
Table 2a38.2
SERVICE CRAFT ORGANIZATION DESIGNATIONS
Grouping Organization Type
Unit Designation Avg. Size Type Designation Description
Squadron S 12-24 Attack A Assigned to Attack craft
Group G 48-96 Fighter F Assigned to Fighter craft
Wing W 140-280 Service S Assigned to any service craft
The standard established by CRAFTCOM and used to identify a craft within a grouping as
follows:
O G Group Number / Craft Number
Where “O” is the craft Organization Type Designation, “G” is the craft Grouping
Designation and the craft designation number. For example a craft within a lone Fighter
Squadron would have a designation such as FS1/23. This example indicates that it is the
twenty-third fighter craft in Fighter Squadron One. The rule is that the most significant
organization grouping is displayed in front along with its number. For example if this same
fighter squadron was attached to Fighter Group Three, then the craft’s designation
would become FG31/23, and if Fighter Group Three was attached to Fighter Wing
Six, the designation would become FW631/23.
Each craft within a grouping will have their designation placed onto the craft’s hull. The
standard is that this designation will be placed up front near the bow on both the port and
starboard sides of the craft. In general, craft are usually assigned to an organization on a
permanent basis. As such, changes to the designation do not occur very frequently.
Craft that are not assigned to any grouping will not have a designation placed on them.
This can be seen on any fleet type shuttlecraft assigned to Starships. Such craft do not
belong to any group, but are simply a part of the ship. As such, their designation will be
the ship’s registry number along with a sequence number as required under Star Fleet
Regulation 2400 and as illustrated below:

VOLUME II
ATTACK SQUADRONS
Fleet Attack Squadrons are assemblages of fighter and attack craft. A typical squadron
may contain ten to twenty craft of a particular type (e.g. Fighter, Attack or Interceptor)
and are most likely found on Attack Carriers that make up a Battle Group. Their main
function is to a) protect the Battle Group, 2) to engage enemy forces, ships, stations and
other craft at remote distances in space away from the group, 3) to attack ground bases
and installations, and 4) to support the ground troops. An Attack Carrier may contain
several Squadrons, each specializing in a particular form of combat mission. In addition,
such Fleet Attack Squadrons may also be found on Ground Assault Ships as well.
The commanders of such squadrons will have designations such as: Commander, Attack
Squadron <n>, (COMATKRON<n>), or Commander, Fighter Squadron <n>
(COMFTRRON<n>), and are usually line officers (SSC) with the rank of Commander.
Fleet Attack Squadrons may also be grouped together to form Fleet Attack Groups. A
large Attack Carrier may contain several of such groups and as such, the commanders of
such groups will have titles such as: Commander, Attack Group <n> or Commander,
Fighter Group <n>; COMATKGRP<n> and COMFTRGRP<n>, respectively. Such
commanders will typically be line officers (SSC) with the rank of Captain.
In overall command of all the attack squadrons within a fleet is the Fleet Attack Group
Commander. The Fleet Attack Group commander is an officer of the line (SSC) with
the rank of Captain, and will have the title of Commander: Fleet Attack Group <n>
with the designation COMFLTATKGRP<n>. An example of the command structure for an
Attack Squadron can be found in Figure 2a24.5.
Lastly, Fleet Attack Groups may be assembled into Fleet Attack Wings as illustrated in
Figure 2a38.1. These are the largest groupings of attack craft in the fleet. In overall
command of an Attack Wing will be the Attack Wing Commander. The Attack Wing
Commander will be an officer of the line (SSC) with the rank of Commodore, and will
have the title of Commander: Attack Wing <n> or COMATKWNG<n>. An example
of the command structure for an Attack Wing can be found in Figure 2a38.2.
PATROL SQUADRONS
Patrol Squadrons of combatant craft are generally assigned to Star Fleet bases and
stations. The function of these squadrons is to protect the base or station from attack. This
is accomplished by continually patrolling around and within the base’s sphere of influence.
Therefore, their operating range typically will extend to only about 5 AU or approximately
750 million km from the base or station.
Patrol Squadrons are designated by number, which are organized and numbered by the
commander of the primary organization the craft is assigned (e.g. Wing or Group.) As
such, the designation “Patrol Squadron” is not a formal organization developed or
managed by CRAFTCOM, but is a local organization designation. The commanders of
Patrol Squadrons will have designations such as: Commander, Patrol Squadron <n>
and will typically be line officers (SSC) with the rank of Commander.
Patrol Squadrons are typically part of a larger Wing of fighter craft stationed at a major
Starbase. As such, there is no specific designation concerning Patrol Squadrons since
they belong to a specific group.

VOLUME II
NON-COMBATANT SQUADRONS
A noncombatant squadron is an assemblage of service craft that perform a specific support

function. For example, one such squadron could be a group of engineering shuttlecraft
that may be located at a Drydock or ship repair facility. As such, the designations for
these squadrons or groupings will be handled by Star Fleet Engineering and not
CRAFTCOM since these vessels will be under the authority of Star Fleet Engineering.
However, the same standard is used as with ship-board shuttlecraft, which is the facility
number followed by a sequence number and the name or designation of the facility under
the craft’s registry. For example:
or
or with a group number[5]
SHIP BOARD SHUTTLECRAFT
Most of the large Starships contain Class-F Fleet Shuttlecraft used for the long-range
transport of equipment and personnel for missions where the ship itself is not required or
where transporting to the surface of a planet is not possible due to extreme environmental
conditions. The number of such craft will depend on the size and mission of the ship. For
example, most cruiser class Starships will typically have six such Shuttlecraft that can
be launched from their hangar deck.
All operations regarding the use of ship-board shuttlecraft is the responsibility of the ship’s
Commanding Officer and as with his ship, the Commanding Officer is personally
accountable for all the actions performed by the craft assigned to his ship as specified in
Paragraph 5 of Star Fleet Regulation 5530.
In general, ship-board Shuttlecraft will not be grouped into squadrons on board the ship.
Such craft are typically loosely assigned to the ship and are indeed a part of the ship as
stated in Paragraph 1 of Star Fleet Regulation 4780. All assignments of fleet
Shuttlecraft to Star Fleet ships are done by the Star Fleet Service Craft Command.

VOLUME II
Figure 2a38.1
EXAMPLE OF FIGHTER CRAFT WING ORGANIZATION DESIGNATIONS
FW
Fighter Wing
1
FG FG FG
Fighter Group Fighter Group Fighter Group
11 12 13
FS FS FS FS
Fighter Squadron Fighter Squadron Fighter Squadron Fighter Squadron
121 122 123 124
FC FC FC FC
Fighter Fighter Fighter Fighter
123/1 123/2 123/3 123/4
FC FC FC FC
Fighter Fighter Fighter Fighter
123/5 123/6 123/7 123/8

VOLUME II
Figure 2a38.2
EXAMPLE OF AN ATTACK WING ORGANIZATION
AW Commander:
COMO Attack Wing <n>
WNGOS Wing WNGSX Flag

CAPT Chief of Staff LTJG Secretary
WNGOPS Wing Operations

CAPT Officer
AG<n1> Commander: AG<n2> Commander: AG<n3> Commander: AT Commander:

CAPT Attack Group <n1> CAPT Attack Group <n2> CAPT Attack Group <n3> CAPT Service Group <nm>
AS<n31> Commander: AS<n32> Commander: AS<n33> Commander: AS<n34> Commander:

Attack Squadron Attack Squadron Attack Squadron Attack Squadron
CMDR <n31> CMDR <n32> CMDR <n33> CMDR <n34>
AT<n331> Lead Attack Craft AT<n332> Attack Craft AT<n333> Attack Craft AT<n334> Attack Craft
Commander Commander Commander Commander
LCDR <n331> LEUT <n332> LEUT <n333> LEUT <n334>

OFFICIAL USE ONLY
VOLUME II
4.0 FLEET OPERATIONAL REQUIREMENTS

Fleet Operational Requirements are those materials, funds and equipment needed to
sustain Star Fleet in a maximum state of readiness for the duties and missions or other
service for which it may be required. The basic fleet size requirements were established in
Section 3.5. In that section the requirements to build an effective force and the command
infrastructure were presented. In this chapter the requirements needed to support the
operations of those forces and assets will be discussed. That is, this chapter will examine
what is required to maintain the fleet and to keep it in a high state of readiness for war or
other service.

VOLUME II

VOLUME II
4.1 MANPOWER REQUIREMENTS

An organization the size of Star Fleet requires a large force of men and women. As such,
this section will acquaint the reader on the manpower required to operate and maintain a
fleet of such size. As a general rule, the manpower required to manage the fleet is directly
proportional to the number of ships and support facilities required to execute the goals set
forth by the Federation Council. To illustrate this principle, the following table lists the
manpower currently required to manage and operate the Star Fleet in an optimum state
of readiness.
Table 2a41.1
STAR FLEET MANPOWER REQUIREMENTS
Number of Required Active
Manpower Requirement Duty Personnel
Star Fleet Administration
Star Fleet Command 656
Sector Commands 180
Star Fleet Academy Staff (includes annex staff) 610
Academy Students (Midshipmen) 2,400
Operating Forces
Star Fleet Combatants 106,134
Star Fleet Support Ships 35,629
Star Fleet Security Personnel 16,650
Star Fleet Engineering and Construction Units 4,800
Star Fleet Troops 400,930
Shore Establishments
Star Fleet Bases 115,073
Star Fleet Stations 6,200
Star Fleet Outposts 2,720
Star Fleet Garrisons 1,800
Star Fleet Intelligence and Communications Stations 1,350
Star Fleet Repair and Construction Facilities 15,080
Reserve Forces
Active Reserve 34,000
Inactive Reserve 68,000
Civilian Employees
Star Fleet Consuls 25
Star Fleet Command Personnel (excluding consultants) 2,860
Civilians Locally Employed at Star Fleet Bases and
32,836
Facilities
Total: 847,933
As seen from the above table, the largest concentration of personnel resides in the Star
Fleet Marine Corps. This large size was determined based upon the number of ground
personnel that would be needed to fight an eight-front war with current technology – the
eight fronts being a major conflict in each Federation octant at the same time.

VOLUME II
In order to sustain this level of manpower, a significant infrastructure is required to recruit,

train, house and maintain this amount of personnel. As such, the Star Fleet Division of
Personnel is one of the largest divisions within the Department of the Star Fleet.
The primary sources of Star Fleet personnel are the many worlds that are members of
the United Federation of Planets. However, the majority of the personnel who enlist
into the Service come from Earth, Mars and the colonies of Alpha Centauri. The primary
reason for this appears to be the propensity for adventure that is part of the psychological
makeup of Earth humans, which is why most ships of the Star Fleet are typically manned
by human beings.
The chart below shows the average distribution of the personnel from the various worlds
of the Federation that make up the Star Fleet. As seen from this chart, the majority of
the personnel that make up the Star Fleet Service are essentially of human origin[1].
Chart 2a41.1
CURRENT SOURCES OF STAR FLEET PERSONNEL
Distribution of Star Fleet Personnel
Aldebaran Colony
Alpha Centauri
Alpha V Colony
Altair VI
Andor
Ariannus
Benecia Colony
Beta VI
Cygnet XIV
Federation World
Cygnia Minor
Deneva
Earth-Mars
Epsilon Canaris III
Izar
Kaferia
Makus III
Marcos XII
Marcus II
Merak II
Ophiuchus III
Orion Colonies
Planet Q
Rigel Colonies
Rigel II
Styris IV
Tau Ceti
Tellar
Vulcan
0% 5% 10% 15% 20% 25% 30%
Percent of Force
A secondary source of Star Fleet personnel come from those that reenlist or extend their
term of service. At this time the average reenlistment rate is about 95%, which is a good
indication of the loyalty and the desire to be a member of the Star Fleet Service.

VOLUME II
STAR FLEET SHIP CREWS
Star Fleet forces also include the crews of ships. As shown in the Table 2a41.2 below, the
total number of personnel stationed onboard Star Fleet ships at this time is 141,213, with
105,584 stationed on line combatants. The duties of these crews will be explained in more
detail in Chapter 5, Part 2 of Volume IV of the Star Fleet Command Manual.
Table 2a41.2
DISTRIBUTION OF STAR FLEET SHIP CREWS
Ship Number Total Average
Class Description
Class of Ships Crew Crew
Combatants
AA Attack Carrier 5 3,766 753
BB Battleship 9 4,504 502
BC Battlecruiser 3 1,516 500
HB Heavy Battleship 1 550 550
HC Heavy Cruiser 16 7,300 456
CC Cruiser 26 10,705 412
LC Light Cruiser 26 9,040 348
FF Frigate 33 11,973 363
HF Heavy Frigate 5 2,000 400
HD Heavy Destroyer 40 9,600 240
DD Destroyer 64 14,018 219
LD Light Destroyer 33 7,155 217
DE Destroyer Escort 95 19,077 202
EE Corvette 20 3,705 185
GG Ground Assault Ship 3 675 225
Support Vessels
SR Repair Ship 34 10,636 313
SL Laboratory Ship 11 1,925 175
TF Freighter 23 2,330 101
SF Fuel Ship 23 1,105 48
TG Tugs 22 3,209 146
SP Supply Ship 42 3,998 95
TD-R Cargo Drones 20 0 0
IT Intelligence/Command Ship 5 1,000 200
SV Survey Ship 14 1,775 127
TR Shuttlecraft Transport 5 1,330 266
SM Hospital Ship 11 2,695 245
MR Mobile Repair Facility 9 5,626 625
Total: 598 141,213
Total Combatants: 380 106,134
Total Support: 219 35,629

VOLUME II
STAR FLEET BASE AND STATION CREWS
Distributed throughout Federation space are 5 Regional Star Fleet Headquarters, 28

major Starbases, 41 Star Fleet stations, 68 outposts, 12 garrisons, 59 fleet support
facilities and one central command base for a total of 214 facilities. The table below lists
the distribution of Star Fleet forces to bases and stations. As illustrated in this table, Star
Fleet bases and stations require a significant force to operate and maintain its bases. The
large ground bases require a large population of service personnel to manage the buildings
and infrastructure, as well as to support the families of service members.
Table 2a41.3
DISTRIBUTION OF STAR FLEET BASE AND STATION CREWS
Number Average Total
Base Type
of Bases Complement Complements
Regional Star Fleet Headquarters 5 2,400 12,000
System Starbase 8 4,200 33,600
Large Planetoid Starbase 5 5,000 25,000
Medium Asteroid Starbase 9 2,000 18,000
Standard Self-contained Base 6 1,600 9,600
Star Base Central 1 2,600 2,600
Standard Station 25 120 3,000
Star Fleet Station 16 200 3,200
Star Fleet Outpost 68 40 2,720
Star Fleet Garrison 12 150 1,800
TAC Base 18 35 630
Communications Stations 8 90 720
Drydock 16 45 720
Construction facility 6 2,100 12,600
Repair Facility 11 160 1,760
Total: 214 127,950
In general, Star Fleet Command, in accordance with ARTICLE 23 of the Star Fleet
Charter, will determine the location of all bases and stations. ARTICLE 23 of the Charter
also gives Star Fleet the authority to construct military shore facilities with the restriction
that the location of the facility be outside the boundaries of a member system, or that
permission must be obtained from the local system should the base be placed anywhere
within the system. However, regardless of the restrictions Star Fleet is given full authority
to construct bases on any planet within Federation territory that is not specifically within
an inhabited system.

VOLUME II
4.2 MATERIEL REQUIREMENTS

Materiel requirements are the resources, supplies and equipment needed to maintain the
Star Fleet in the proper state of readiness for war or other service. Such requirements
are directly related to the size of the Operating Force and the Shore Establishment.
In general, the size of the United Federation of Planets requires a large operating force
of vessels and personnel. The operating requirements are based upon several factors:
1. The number of ships actively patrolling Federation space,

2. The number of bases and stations built to support the fleet,
3. The size of the force required to man the ship and base assets, and
4. The size of the ground force required for assaults.
The number of ships, bases and personnel required to operate Star Fleet has already
been analyzed in Section 3.5. This section will deal primarily with the material needs of the
current active force.

VOLUME II
GENERAL FLEET LOGISTICAL REQUIREMENTS
Star Fleet requires an enormous amount of supplies in the form of consumable goods in
order to maintain an effective force; primary among them is food. An average humanoid
consumes about 650 grams of foodstuffs per day. As such, commands must maintain a
large stock of basic protein and other materials required for food production by Food
Synthesizers. For example, a typical Starship must produce about 280 kg of food daily.
In the course of a typical five-year mission, this averages to over 500,000 kg or 500 metric
tons of food that must be produced. Star Fleet ships cannot carry this amount of material
and must be continuously resupplied during the course of their patrol.
Another important supply item is water. An average humanoid drinks about 1.5 liters of
water per day, but uses a total of about 30 liters per day for all personal uses. As such, a
typical cruiser class Starship must carry a minimum of about 14,000 liters or 14 metric
tons of potable water for various personal purposes. However, all Star Fleet ships recycle
their water through recycling and purification units and therefore, do not require a
continuous supply. In addition, they will periodically refresh their water supplies either
from supply ships or from planets that contain plenty of fresh clean water.
Ground shore facilities, on the other hand, do not have the restrictions on water usage as
do enclosed vessels. This is because most ground stations will have a continuous source of
fresh water available to them on the surface of the planet. Therefore, daily water usage is
a bit higher (approximately 40 liters per day) and as such, is usually not a supply issue.
Planets chosen to hold bases and stations will generally be selected on the basis that there
will be an adequate water supply available. This includes planets where stations may be
placed in orbit around the planet as well.
Atmospheric gases are another essential item that requires replenishment – especially for
closed-container vessels such as ships and space stations. For vessels that require class-M
atmospheres, production of oxygen (O2) will be accomplished within the vessel through the
electronic dissociation (hydrolysis) of pure water. However, what can’t be easily produced
are nitrogen (N2) and the other inert gases that may be required for humanoid existence.
Therefore, enclosed vessels will periodically require recharging of their gas storage banks.
Another important material item is fuel; fuel for propulsion and for power generation. Star
Fleet ships are propelled through the fusion of matter and antimatter (i.e. Polymass). As
such, the amount of Polymass that must be produced to initially supply warp-driven
Starships is significant, not to mention the high cost of producing and storing antimatter.
However, the amounts required to supply Star Fleet ships is CLASSIFIED and cannot be
mentioned here. Needless to say, however, a typical cruiser class Starship will contain
enough fuel for eighteen years[2] of self-sustained operation.
Finally, Star Fleet ships must maintain an adequate supply of spare parts, instruments
and raw materials for repair and maintenance. This is especially true for vessels operating
at the outer regions, away from any repair or supply facility. Star Fleet ships on patrol
must be able to make their own repairs or be able to place the ship in a condition where it
can remain operational. As such, the larger Star Fleet ships such as Cruisers and Frigates
contain fabrication and machine shops designed to construct most of the parts needed to
keep the ship running or to make any necessary repairs to the hull. As such, these ships
must carry a large supply of raw materials for their converters and fabricators.

VOLUME II
MATERIEL REQUIREMENTS – TREATY ZONE
The primary mission of the Star Fleet forces within the Federation Treaty Zone is the
maintenance of interplanetary peace and security among the signatory worlds of the
Federation. As such, the Treaty Zone is patrolled by 34 Star Fleet combatants and
about 16 fleet support vessels, which comprise the two Flotillas assigned to the region.
The primary class of ships that patrol the Treaty Zone are typically Destroyers and
Escorts, which are light combatants designed for speed and mobility. The selection of such
light vessels was designed so that citizens in private ships would not feel intimidated when
a Starship approaches them and therefore, would not give the impression of heavy-
handedness on the part of Star Fleet. In addition, these light combatants do not normally
carry out exploration missions, nor do they engage in any extensive scientific research. As
such, they are not equipped with extensive scientific facilities, cargo areas or specialized
personnel and therefore, do not need to be supplied for such functions.
In addition, Star Fleet ships that operate within the Treaty Zone do not carry a large
amount of the raw materials typically needed for daily functioning or repairs since they
usually operate close to a base or station from which they can obtain the required supplies
or needed repairs. And since most of the line Starships operating within the Treaty
Zone are light combatants and escort vessels, their hulls do not have the capacity to store
large amounts of material or equipment any way. Therefore, they can only carry enough
raw food materials to last them about three weeks or 24 days and as such, their patrol
cycle will revolve around this time frame.
Most of the major bases within the Treaty Zone are the large Star Fleet Headquarters
facilities located on the signatory worlds of the Federation. These are very large facilities
which have significant material requirements, not only for the support of itself, but also to
warehouse and supply the operating forces in the region as well. Therefore, Starbases
are built with significant storage and supply facilities for both their own consumption and
to support the fleet. For example, the Star Fleet Headquarters on Alpha Centauri has
2260 regular Star Fleet personnel and 6160 troops. As such, this station requires about
6.5 metric tons of food daily to feed its personnel. In addition, it must be able to resupply
at least five cruiser class Starships simultaneously as well. This amounts to an additional
215 metric tons of foodstuffs and 115,000 liters of water in order to supply the requisite
number of Starships for about a year.
Most of the food and water that supply these ground bases come from local sources or are
grown or pumped, in the case of water, on site. Bases located on populated worlds may
purchase such supplies from the indigenous population. However, on unpopulated worlds
Starbases will grow their own food, either on base farms or hydroponic gardens. As such,
the total amount of food required to feed all the bases and stations within the Federation
Treaty Zone is estimated to be about 50,000 kg per day or 50 metric tons, which will also
require a significant water supply. Therefore, such planets must be carefully selected for
their water supply. As such, planetary survey teams will often include a hydrologist.
In terms of total consumable resources, the Treaty Zone contains 37,600 regular Star
Fleet personnel and 52,000 Star Fleet troops. This amounts to a total daily intake of food
of about 54 metric tons and about 2.7 million liters of water usage.

VOLUME II
MATERIEL REQUIREMENTS – EXPLORATION ZONE
As stated in Section 3.1 of this volume, the primary function of the Operating Forces in
the Exploration Zone is to protect Federation space and all its colonies, undertakings
and citizens. The secondary function of the Operating Forces in this zone is to expand
Federation space through exploration and colonization, and to perform scientific research
where needed. As such, the bulk of the Operating Forces and Shore Establishments
of Star Fleet are assigned to the Federation Exploration Zone and therefore, account
for the greater part of the fleet's material requirements.
The functions to which the Operating Forces are assigned within the Exploration Zone
require ships of significant capability. As such, these ships will primarily be the larger line
Starships such as Cruisers and Frigates, which are equipped with powerful weapon
systems, significant medical facilities, laboratories, scientific and exploration equipment
and an abundant amount of storage and cargo space. Destroyers and Escort vessels are
also assigned to the Exploration Zone, but primarily for fleet protection and law
enforcement. In summary, the bulk of the missions at the outer boundary areas will be
performed almost exclusively by Cruisers and Frigates.
To support the mission in the outer regions, a typical cruiser class Starship is designed to
carry approximately 22,750 liters of water for various purposes, which is equivalent to
nearly 23 metric tons in mass. Star Fleet ships, operating at the outer reaches of the
Federation, will refresh approximately 25% (~6000 liters) of their water supply every 90
days and as such, ship commanders will schedule water replenishment runs based on that
frequency. In terms of food, a typical cruiser class Starship contains enough foodstuffs to
feed 430 people for about 165 days. This amounts to an average food material load-out of
roughly 43 metric tons. As such, most cruiser class Starships, operating at the outer rim,
will request a supply run by a fleet supply ship about twice a year.
As stated in previous subsections, the small escort vessels within any fleet do not have the
storage capacity as the larger combatants. As such, these smaller ships must be resupplied
more frequently. Therefore, there will be at least one support ship assigned to each Fleet
Squadron designed to replenish these smaller vessels. Such support ships will normally
follow alongside the Squadron Flagship awaiting assignment to a specific ship within the
squadron.
In terms of personnel, the total number of Star Fleet troops and personnel within the
Exploration Zone is approximately 428,000. This equates to a daily food consumption of
roughly 112,000 metric tons. As such, the primary function of the Shore Establishment
within the Exploration Zone is to support the Operating Forces. The majority of this
support will come from the large Starbases and the many Star Fleet Stations that dot
the Exploration Zone. The criterion for fleet support is that a major Starbase must be
able to repair and replenish five line Starships simultaneously with a load-out of at least
six months. On the other hand, the criterion for fleet support from a deep-space station is
that the station must be able to supply two cruiser class Starships for at least five days.
For example, deep-space stations usually carry a crew load out for about 280 days, with
water replenishment somewhat sooner. As such, a typical deep-space station will require
storage space for about 70 metric tons of foodstuffs and 168,000 liters of water.

VOLUME II
GENERAL MAINTENANCE REQUIREMENTS
Ships and stations require constant maintenance and upkeep. Specifically, line Starships
require constant inspection, upkeep and refitting due in large part to the stresses placed
on the vessel’s structure by the propulsion system. The process of warping space and
accelerating to enormous speeds places a great strain on such ships. As a result, these
ships are often in Drydock undergoing inspection and repair. Therefore, the next two
pages will address these requirements.
STAR FLEET SHIP MAINTENANCE REQUIREMENTS
As stated above, Star Fleet ships typically require extensive maintenance in order to keep
such a complex piece of equipment in peak operating condition. Ships that are assigned to
patrol duty will usually undergo an overhaul every five to eight years of service, depending
on the nature and duration of the mission. These will typically be the cruiser class of ships
because of their patrol mission. However, most of the other combatant classes will usually
require an overhaul between eight and ten years, and support ships will generally have an
even longer service time before they need to undergo an overhaul. As such, the following
table will illustrate the average time the various Star Fleet ship classes will require major
inspection and maintenance.
Table 2a42.1
STAR FLEET SHIP MAINTENANCE REQUIREMENTS
Basic Inspection Schedule Maintenance Schedule
Ship Class 1
Service Structural Inservice Refit Overhaul
Strategic
Attack Carrier 6-12 mos. 6 years 12-14 mos. 10 years
Patrol
Fleet
Battleship 10 mos. 6 years 12 mos. 8 years
Command
Cruiser Security Patrol 9-12 mos. 5 years 9-12 mos. 5-8 years
Squadron
Destroyer 8-10 mos. 5 years 12 mos. 5-7 years
Protection
Convoy
Escort 6-9 mos. 5 years 10-12 mos. 5-6 years
Support
Frigate Security Patrol 9-12 mos. 5 years 9-12 mos. 5-8 years
Troop
Assault Ship 12 mos. 7 years 12 mos. 6-8 years
Transport
Fleet Support
Fleet Support 12-16 mos. 6 years 14 mos. 5-10 years
Ship
Hospital Ship Fleet Support 12-16 mos. 8 years 16 mos. 12 years
Transports Base Support 6-10 mos. 5 years 10-12 mos. 6-8 years
Science Science and
12-18 mos. 10 years 12-18 mos. 8-10 years
Vessels Exploration
Notes
1. Inservice Inspections are performed by the Star Fleet Board of Inspection and Survey (INSURV).
In general, the average Star Fleet ship is designed for fifty years of operation before it
must either be completely rebuilt or replaced with a more modern vessel.

VOLUME II
BASE AND STATION MAINTENANCE REQUIREMENTS
Deep-space stations also require constant inspection and repair as well. Space stations,
especially those located within planetary systems, are constantly bombarded by solar
radiation, meteorites and other particles travelling through space. The hulls or shells of
these stations are constantly being damaged or worn and therefore, require constant
repair and refurbishment. As such, the hulls of these stations will be completely inspected
every year, with an average repair cycle of about five to seven years.
Ground bases, on the other hand, see normal wear and tear as with any other urban area.
As such, the frequency of upkeep and repair would be the same as that for a small town.
Therefore, ground bases will employ a full-time maintenance and repair force. However,
any major new construction or extensive repair will normally be performed by the Star
Fleet Corps of Engineers and the Star Fleet Construction Command.
BASE AND STATION SECURITY REQUIREMENTS
Another fundamental operating requirement for a base is its security, as required under
Star Fleet Regulation 4670. Such security considerations come in two forms:
1. Security from or mitigation of natural disasters, and

2. Security from unnatural threats and enemy forces.
As such, these security considerations form the basis for the requirements regarding the
security of the base or station. To manage the security aspect relating to the unnatural
threats such as from external forces, a base will be manned with the appropriate number
of security personnel according to its location and proximity to hostile or unfriendly forces.
Security patrols around the base or station will be required to maintain the security of the
base around its Jurisdictional Radius (Table 2a32.1). The number and intensity of the
security patrols will determine the number of attack craft, along with their crews, that will
be deployed to the base.
Another form of security is basic law-enforcement within the base. As such, personnel in
the form of Military Police, from the Star Fleet Security Forces Command, will be
assigned to the larger bases. Their primary function will be to maintain law and order in
and around the base, providing access to visiting personnel, patrolling the base perimeter
and monitoring ground traffic within the base. The size of the Military Police force will
depend on the size of the base, the number of base personnel stationed, the number of
civilians employed on the base and the size of neighboring population centers.
In addition, and by regulation, Star Fleet bases and stations must also institute security
measures designed to prevent or mitigate property damage as a result of natural and
other disasters. For example, one of the most important security issues on a Star Fleet
base or station is fire - especially on bases and stations with enclosed atmospheres. As
such, Star Fleet bases will be equipped with fire protection and fire-fighting equipment
and other emergency vehicles. The size of this force will be based upon the size and type
of facility, as well as the planetary resources available to the base.

VOLUME II
4.3 SUPPORT REQUIREMENTS

Support requirements are those subject matters related to colonies, expeditions and other
enterprises that come under the direct authority of Star Fleet. ARTICLES 9 and 21 of the
Star Fleet Charter specifically state that Star Fleet is the primary agency responsible for
the logistical and security support for all colonies, outposts and expeditions established by
Star Fleet or the Federation government, and may include some of the privately owned
and managed colonies and expeditions scattered throughout the Federation as well. In
general, however, Star Fleet is not directly responsible for the basic logistical support of
private or commercial colonies or other such enterprises, but only for those provisions that
may be required to keep the colony or expedition operational. The function of the general
supply of such enterprises is the sole responsibility of the organization that established the
colony or outpost. Star Fleet, in its security role, is only responsible for protecting these
outposts, and its personnel, from invading forces or other illegal activities. As such, Star
Fleet has a limited support role regarding private or commercial ventures.
As such, the function of this section is to describe the various requirements associated with
supporting Federation colonies and expeditions as may be required under ARTICLE 9 of
the Star Fleet Charter, and only those colonies and expeditions that are listed in Table
2a43.1 that are currently active.
PROVISIONS AND SUPPLIES
The basic goal of any colony and expedition is to flourish, independent of any outside help,
and to become self-sufficient through their own means and labor. However, during the
early stages of their development colonies may require outside assistance. As such, Star
Fleet may be required to provide such enterprises with the supplies, provisions and other
essential items that may be required for their success. To meet this obligation Star Fleet
must allocate certain resources for the logistical support of colonies and expeditions and
therefore, Star Fleet ships must maintain an adequate supply of such resources that are
for the exclusive use by colonies. However, and in general legally, it is the responsibility of
the colonizing enterprise to contract or make arrangements for the replenishment of their
colonies using commercial means.
As a general rule Star Fleet supply ships do not replenish private or commercial colonies
and expeditions, but only those colonies and expeditions initiated by Star Fleet or that
were started by some other Federation agency. However, a Starship may supply a
private colony or expedition with some of their necessities when performing their annual
medical examinations and could provide colonies and expeditions with essential goods and
services, but Star Fleet is in no way obligated to supply such enterprises with any other
item such as private communications or documents. Such enterprises must contract private
or commercial services to furnish them with non-essential, luxury or other such items.
However, there may be special agreements or provisions placed in the colony’s license
which may stipulate a specific relationship between that venture and Star Fleet regarding
the supply of the enterprise. For example, Star Fleet may be obligated to visit a colony at
specific intervals for delivery of special materials, for perishable goods or to bring back to
Federation authorities any special reports or data the enterprise deems important. [3]

VOLUME II
PERSONNEL
By law Star Fleet can only provide personnel to government-owned settlements and
expeditions. Star Fleet cannot, and will not, provide personnel for, or transport personnel
to private or commercial colonies and expeditions. This is the sole responsibility of the
enterprise that established the colony or expedition. However, Star Fleet may temporarily
supply a small security force for some of the more sensitive expeditions [4], and along with
security personnel, temporarily supply medical personnel until permanent civilian medical
personnel are available.
MEDICAL SUPPORT
As a part of maintaining the welfare of colonies, expeditions and other such enterprises,
Star Fleet is obligated to supply private and commercial enterprises with medical supplies
and medical attention if needed. And to ensure the health of such enterprises Star Fleet,
by law, must conduct periodic medical examinations of the members of such enterprises.
The period may vary based on location, licensing stipulations or contractual agreements.
However, the Federation Council has set a minimum interval of two years between such
examinations. However, Star Fleet established a medical certification policy of one year.
SECURITY REQUIREMENTS
Star Fleet is charged with protecting all Federation colonies, whether inside or outside
Federation space, and is responsible for the welfare of such colonies and expeditions as
required in ARTICLE 9 of the Charter. As such, Star Fleet must provide the same security
services to private and commercial colonies and enterprises as with any other Federation
entity. Therefore, and as part of their mission, Star Fleet ships are required to perform
periodic security checks on colonies located within their Patrol Zone. Star Fleet
Commanders are encouraged to plan their Patrol Areas such that a typical Starship
will be responsible for about two or three colonies, thereby minimizing the need for line
Starships to divert from their normal routine to perform colony support [5].
EMERGENCY SUPPORT REQUIREMENTS
Humanitarian aid is the responsibility of every member of the United Federation. When
a planet or social system is struck with disaster, it is the duty and responsibility of Star
Fleet to come to the aid of any planet or system. Aid may be in the form of food, medical
supplies or medical attention, or to provide equipment and materials needed to mitigate or
prevent a disaster from worsening, or to provide transportation for the evacuation of the
residents and to provide, to the extent possible, shelter.
In addition to humanitarian aid to planets and systems, Star Fleet has the responsibility
and the duty to assist persons, ships and craft that are in distress in open space. Distress
in space may be defined as problems with the spacecraft, collision with another spacecraft,
persons stranded on a planet or in space, or persons lost in space. In such instances, the
nearest Star Fleet vessel will be required to proceed with all possible speed to the vessel
or persons in distress, rescue such persons in distress and render any aid or assistance as
needed. As such, Star Fleet ships and stations are outfitted with special equipment and
supplies used exclusively for such humanitarian aid.

VOLUME II
Table 2a43.1
COLONIES AND EXPEDITIONS SUPPORTED BY STAR FLEET
SCS Location
1 2
Name System Type Class Distance
(ly) Direction Sector
Aldebaran Colony ALPHA TAURI F B 64.0 158-MARK-350 324A
Alpha V Colony NU2 LUPI F B 47.7 328-MARK-337 136L
Archanis IV EPSILON EQUULEI F S 196.0 046-MARK-026 5385W
EPSILON
Barradas III F S 71.6 318-MARK-027 215K
SERPENTIS
Benecia Colony LALANDE 21185 F B 10.1 244-MARK-023 004
Berengaria VII KAPPA 1 CETI F B 28.4 136-MARK-343 29J
Beta Agni II OMICRON TAURI F B 209.5 137-MARK-348 8114L
Beta VI HD93372 F B 104.0 321-MARK-298 1542C
Bringloid V Colony EQ VIRGINIS F A 66.9 291-MARK-003 189P
Caldos Colony4 IOTA ANTLIAE F S 200.1 275-MARK-319 8458E
Camus II HD33632 F S 84.6 169-MARK-010 473C
Centauri VII RIGEL KENT B F C 5.2 309-MARK-337 009
Coltar IV4 OMEGA 1 AQUARII F F 132.0 075-MARK-352 2026P
Cygnia Minor MU 1 CYGNI F B 72.1 071-MARK-044 222M
Delta Rana IV4 GAMMA ERIDANI F B 219.5 138-MARK-323 8370Z
Deneva DENEB ALGIEDI F C 37.2 048-MARK-003 11Y
Dulisian IV Colony4 HD15524 F B 164.5 131-MARK-008 3646H
Dytallix B EPSILON BOÖTIS B F C 211.9 290-MARK-041 7437P
Earth Colony 2 LACAILLE 9352 F S 9.0 050-MARK-337 006
Elba II ETA BOÖTIS S X 39.1 282-MARK-028 16R
Exo III ZETA LUPI F S 116.6 329-MARK-332 1398W
Johnson Expedition3 -
GAMMA HYDRAE F S 133.7 295-MARK-348 2090V
Gamma Hydra IV
Haelium Experimental
ALPHA FORNACIS F F 44.2 117-MARK-313 143C
Station
Janus VI HD3268 F C 121.1 101-MARK-009 1669I
Jaros II Brig ZETA AQUILAE S X 83.3 015-MARK-043 555C
Notes:
1. Type Codes:
F – Federation private colony or expedition
S – Star Fleet colony or expedition
N – Non Federation colony or expedition
2. Class Codes:
A – Advance base
B – Social
C – Commercial/Industrial
F – Agricultural/Farming Colony
M – Military
P – Private/Independent Society
S – Scientific/Engineering Research
X – Prison/Penal Colony
3. Colony decommissioned.
4. New colony.

VOLUME II
Table 2a43.1
COLONIES AND EXPEDITIONS SUPPORTED BY STAR FLEET - CONTINUED
SCS Location
1 2
Name System Type Class Distance
(ly) Direction Sector
Kessik IV Colony HD203803 F C 180.1 063-MARK-042 5508D
Crater Expedition3 –
HD147513 F S 42.7 336-MARK-348 120F
Planet M-113
New Paris Colonies – IOTA URSAE
F B 49.1 211-MARK-024 67P
Makus III MAJORIS
Mariposa Colony HD114783 F B 69.0 284-MARK-005 188N
Midos V ALPHA CIRCINI F A 53.8 331-MARK-319 136W
Norpin Colony GLIESE 783 F P 19.0 018-MARK-352 006
3
Sandoval Colony – 4
MIRA F S 416.0 117-MARK-343
Omicron Ceti III
Ophiuchus III 70 OPHIUCHI F F 17.6 350-MARK-033 005
Pegasus Colony5 85 PEGASI F F 38.5 102-MARK-027 12R
Planet Q WOLF 359 F B 9.7 254-MARK-002 004
Research Station 75 HD12661 S S 119.5 126-MARK-010 1018X
Rigel XII 40 ERIDANI B F C 14.7 152-MARK-328 007
Risa Resort Colony 59 VIRGINIS N P 61.1 279-MARK-016 212H
Sherman’s Planet HD175529 F F 200.7 008-MARK-349 8027H
Starnes Expedition 3– TW PISCIS
F S 23.2 055-MARK-342 27B
Triacus AUSTRINI
Tantalus V DEN 1048-3956 F X 14.3 275-MARK-323 009
Tarsus IV HR753 F B 22.2 128-MARK-351 28E
Theta VII ER RAI F B 45.2 159-MARK-062 81C
Vega Colony –
VEGA F B 25.6 359-MARK-068 25F
Vega IX
Notes:
1. Type Codes:
F – Federation private colony or expedition
S – Star Fleet colony or expedition
N – Non Federation colony or expedition
2. Class Codes:
A – Advance base
B – Social
C – Commercial/Industrial
F – Agricultural/Farming Colony
M – Military
P – Private/Independent Society
S – Scientific/Engineering Research
X – Prison/Penal Colony
3. Colony/Expedition shutdown.
4. Outside the boundaries of the Federation.
5. A Pelagic planet.

VOLUME II
4.4 BUDGETARY REQUIREMENTS

The budgetary requirement to sustain Star Fleet is enormous. The primary source of
money to support Star Fleet comes from the member systems of the Federation and
from other sources such as from contracts with non-member systems to provide protection
services, tariffs, etc. As such, this is the fundamental reason why Star Fleet is tasked with
expanding Federation boundaries, and to seek out and recruit new member worlds.
Table 2a44.1
STAR FLEET ANNUAL BUDGETARY REQUIREMENTS
Annual Outlay in
Budget Item Federation Credits
Fleet Capital Expenses
New Starship Construction (6) 961,747,572,816
New Base Construction (1) 2,080,000,000,000
New Station Construction (1) 310,691,823,899
Other Stations and Outposts (6) 431,328,444,444
Star Base Capital Improvements 6,300,000,000
Amortized Capital Expenses (50 years) 26,794,690,730,148
Fleet Maintenance Expenses
Ship Maintenance and Repair 1,416,000,000
Ship Overhauls 2,986,285,714
Station Maintenance and Repair 8,200,000,000
Ship and Station Spare Parts and Equipment 403,150,000
Fleet Operating Expenses
Fleet Energy Expenses (Ship Fuel, Base Fuel, etc.) 43,590,000,000
Food and Medical Expenses 36,264,960,000
Support for Star Fleet Colonies and Expeditions 519,930,000
Other Support 231,650,000
Fleet Personnel Expenses
Star Fleet Command 87,175,300
Starship Crews 4,089,727,582
Starbase Personnel 3,338,980,833
Star Fleet Troops 6,630,815,850
Reserve Forces 948,444,218
Other Non-Star Fleet Personnel 591,048,000
Other Operating Expenses
Star Base Leases (17) 425,000,000
Star Fleet Academy (including its annexes) 9,000,000
Training Costs 85,019,004
Research and Development Expenses
Establishment of Star Fleet Colonies and Expeditions (Budgeted) 85,000,000
Engineering and Technical Research (Budgeted) 50,000,000
Scientific Research (Budgeted) 30,000,000
Research Grants to External Entities (Budgeted) 25,000,000
Total: 30,694,767,734,721

VOLUME II
CURRENT LONG-TERM DEBT
Star Fleet capital costs (i.e. the cost of constructing ship and facility assets) are typically
amortized over a 50 year period. The primary reason being that the Federation does not
have the financial resources required to pay the cost of constructing Star Fleet assets all
at once. As such, the current long term debt includes the cost of constructing all 598 ships,
and 214 bases and stations, which totaled f 942,123,044,000,000 Federation Credits.
Amortized over a 50-year period at an average interest rate of 1.5%, this amounts to an
annual cost to the Federation of approximately f 26,794,690,730,150 Credits[6].
Primarily, the burden of this debt falls largely upon the many worlds of the Federation.
Considering the number of worlds (approximately 159) that form the United Federation
of Planets, the average cost per world of this debt amounts to approximately 170 billion
Credits, which is a manageable amount. However, the cost per world is actually dependent
upon the size of the overall population. Basically, the total population of the Federation is
determined and a per capita cost is calculated. The total cost burden of a world will be
calculated using this per capita value. In addition, credit is given to the worlds that directly
support Star Fleet for such things as the cost to lease property for a System Base, etc.
As such, the payout by Star Fleet for base leases will reduce the overall annual outlay by
about f 425,000,000 to the supporting world.
Table 2a44.2
TABLE OF STAR FLEET’S LONG-TERM DEBT
Amortization Current Total Debt
Item Number
Period (Credits)
Ships
Capital Starships 89 50 years 118,850,924,675,325
Standard Combatants 290 45 years 267,657,922,077,922
Fleet Support 128 30 years 77,672,974,545,455
Transports 50 30 years 39,653,766,233,766
Special Purpose Vessels 41 30 years 24,932,690,909,091
Ship Totals: 598 528,768,278,441,558
Bases
Major Star Fleet Bases 34 80 years 147,755,000,000,000
Star Fleet Stations 109 50 years 44,050,000,000,000
Garrisons 12 50 years 960,000,000,000
Fleet Support Facilities 33 50 years 2,508,000,000
Special Purpose Stations 26 50 years 55,536,000,000
Base and Station Totals: 214 192,823,044,000,000
Total Assets: 721,591,322,441,558

CONFIDENTIAL
RESTRICTED DATA
NOFORN
VOLUME II
5.0 FLEET COMMAND OPERATIONS

Fleet Command Operations refers to the methods and processes used to direct the
Operating Forces in the performance of their missions and functions. Essentially, this
chapter will examine how Star Fleet Operations creates and assigns the missions that
carry out Federation policy.
Fleet Command Operations begins with the development of a mission. Typically, a

mission is created to achieve or accomplish some goal set by the Federation Council or
to carry out a specific assignment that will fulfill a general function of Star Fleet such as
exploration, scientific study or intelligence gathering. The mission or specific assignment
will first be planned based on the type of operation that is expected to be performed. As
part of this process all the key components of the mission will be examined, such as the
firepower that will be required, the number and types of vessels to be employed, and any
equipment and logistical support that may be required. From this data a Mission Profile
will be developed, which will be used to monitor the progress of the assignment and the
expected results. This process will be explained in more detail in Section 5.3.
Once the profile has been developed, the mission directive will be created and issued to
the command or force for implementation. Most such orders given to the Operating
Forces are single-time efforts designed to accomplish a single goal. However, there are
other “general” and “standing” orders or generalized instructions of indefinite duration.
These types of orders will be explained in subsequent paragraphs and section of this
chapter.
Star Fleet defines a Standing Order as a generalized order of indefinite duration, which
remains in effect until modified or rescinded. Standing orders are necessarily general and
vague since the exact circumstances for execution may occur in the future under unknown
conditions. For example, in Star Fleet there is a standing order for juniors to come to
attention when a senior officer enters a room. As such, standing orders will rarely specify
times, dates or names and must rely on the person executing the order to interpret the
circumstances in which the order is to be executed. Another example is a standing order to
all Star Fleet ship commanders to study stellar phenomenon as they are encountered. As
such, Standing Orders are most often issued by commanders to their units.
A General Order, on the other hand, is a published directive, originated by a commander,

and binding upon all personnel under his command. The purpose of a General Order is
to enforce a policy or procedure unique to a unit's situation, which may not otherwise be
addressed in applicable regulations, military law or public law. As such, a General Order
has the force of law, and it is an offense punishable by court martial or lesser military
court to disobey one. What makes it a “general order” (as opposed to a Direct Order), is
the fact that the actor is not explicitly named, nor precisely that (or whom) the order is to
be acted upon.
With regard to Star Fleet operations, a Star Fleet General Order is a specific set of
directives used to implement specific Federation or Star Fleet policies that originate
from the Director: Star Fleet Command. They apply to all members of the Star Fleet
Service. A description of these types of orders will be described in more detail in Section
5.4, and the full set of General Orders are contained in Section 5.7.

VOLUME II

VOLUME II
5.1 FLEET ADMINISTRATION

Star Fleet Command is the central authority for all of the Operating Forces and Shore
Establishments within the Department of the Star Fleet. Specifically, it is the Star
Fleet Division of Operations that is assigned the responsibility of administering all of
the Operating Forces and Shore Establishments, herein referred to as “the fleet”. In
this section the administration of the Operating Forces, as well as the coordination of
these forces, will be discussed.
ADMINISTRATION OF STAR FLEET FORCES
The administration of Star Fleet forces is divided between Star Ship Command and
Star Base Command. Star Ship Command is the organization responsible for all the
aspects regarding the operation, functioning and missions of Star Fleet ships and craft,
except those vessels that are assigned to divisions that support the fleet such as those in
the Star Fleet Transportation Command and the Star Fleet Space Exploration
Command. In essence, Star Ship Command represents the entire Operating Forces
of Star Fleet. Star Ship Command is essentially an administrative command and as
such, all operations involving Star Fleet vessels are the responsibility of this organization.
Star Base Command, on the other hand, is basically responsible for all the aspects
regarding the operation, functioning and missions of Star Fleet bases, stations and
outposts, the sole purpose of which is to support the Operating Forces. As such, Star
Base Command, which is also an administrative command, represents and manages the
entire Shore Establishment of Star Fleet.
These two organizations comprise the bulk of the Star Fleet Division of Operations.
Both Star Ship Command and Star Base Command will independently plan and
execute operations within their area of responsibility. However, although independent of
each other in terms of their areas of responsibility, both commands will coordinate their
activities between them. Where there may be an overlap in operations between them, or
that some functionality of one command will be necessary by the other, each command
will confer and support the other in their operations.
In addition, the forces of the Star Fleet Marine Corps will also be administered by Star
Fleet Operations. Although within the Operations Division, the Star Fleet Marine
Corps operates somewhat independently under the Commandant: Star Fleet Marine
Corps. However, where joint operations with other elements of the Operating Forces
will take place, the administration of the forces involved in the operation will come under
Star Fleet Operations and its various offices and commands.

VOLUME II
ADMINISTRATION OF ADJUNCT FORCES
Adjunct Forces, as the term implies, relates to those assets (e.g. personnel or materiel)
that may be joined to Star Fleet under certain circumstances. Should a situation exist that
may require that Local Forces be merged into Star Fleet, the administration of Adjunct
Forces will be handled by the Star Fleet Adjunct Forces Command. However, once a
Local Force has been merged into Star Fleet, the force will be managed or commanded
by the Star Fleet commander to whom the Local Force was assigned. Only the internal
structure of the adjoined force will be preserved.
During wartime conditions, Local Forces will be merged into Star Fleet in order to
augment the fleet. During such situations the Federation Council President will declare
a Federation Emergency and invoke Articles 45 and 49 of the Articles of Federation,
requiring all members to supply Star Fleet with a portion or all of their forces. When this
occurs most, if not all, of the Local Forces will be merged into Star Fleet and therefore,
will report directly to Star Fleet Operations as a member of the Operating Forces.
The commanders of the adjoined Local Forces will report to their respective Star Fleet
commanders as assigned by the Deputy Chief: Adjunct Forces upon notification by
their respective governments. Typically, the Local Force Liaison Officer stationed with
the Local Force will notify the Local Force Commander regarding the Star Fleet
commander to whom the Local Force Commander will be assigned. In most cases the
assignment of the Local Force to a specific Star Fleet force has already been determined
in advance by the Star Fleet Office of Local Force Planning and therefore, the notice
by the Local Force Liaison Officer will merely be a formality.
In order to make effective use of the combined force, the Star Fleet Commander and
the Local Force Commander will plan the missions and strategies together, utilizing
both of their strengths as well as accounting for both their weaknesses. When the planning
is done, the Local Force Commander will execute the mission or the plan to which he is
assigned. From this point on the Local Force Commander will be in complete command
of his forces, and may organize and direct his forces as he deems fit to accomplish the
mission. Star Fleet Commanders do not manage the individual units of Local Forces,
but only provide general guidelines or directives to their Local Force Commanders on
how their force will be utilized to accomplish the mission. And although the Local Force
Commander will be in complete command of his force, he must always and continuously
report to his Star Fleet Commander on the status and progress of his mission.

VOLUME II
COORDINATION OF FORCES
In such a large volume of space as the United Federation of Planets, it is essential that
the forces scattered throughout Federation space are properly managed and coordinated
by the central command. Coordination is not only important for large scale operations such
as during galactic conflict, but also in the minor and routine operations performed by any
command, such as ship supply rendezvous, freight and transport scheduling, assigning
traffic monitoring areas, etc. As such, these forces will continuously be monitored at the
central command location known as Star Fleet Mission Control.
As stated in Section 1.8 the Star Fleet Mission Control Center is the central part of the
Operations Center that focuses on the activities being performed by the Operating
Forces. All Star Fleet forces, and all those other forces attached to Star Fleet will be
monitored and controlled from this central location. Monitoring and coordination of the
forces from the center is performed through visual displays that completely encircle the
center and via a three-dimensional holographic image of Federation space wherein all the
ships and bases can be displayed in all sectors of the Federation. In order to accomplish
this, Federation space is littered with observation posts, scanners and transmitters that
provide near real-time viewing of events in space as they occur. In addition, fast subspace
communication also allows for real-time coordination and direction of all forces.
To help coordinate and synchronize activities of all of Star Fleet’s forces throughout
Federation space, the Federation Stardate standard is used. Information fed to the
commands will be time-stamped with the Federation Stardate. Thus, unit commanders
will know when the message was sent and when an activity is expected to be executed.
Because of the huge distances and the variations in the time lag involved, operations
requiring time sensitive actions will be adjusted accordingly. That is, if a unit is expected to
perform some operation at a specific time, a time delay factor will be added based upon
the amount of time it takes for the command to receive the message. In this way the
likelihood that a key operation will be neglected will be minimized.
The use of the Federation Stardate to coordinate activities will also be required by any
Local Force that is merged into Star Fleet as well. As such, the equipment of the Local
Force may require modification in order to function properly within this standard. This
issue has been addressed by most of the major Local Forces and only a small fraction of
the smaller or newer forces require equipment modification.

VOLUME II
STAR FLEET MISSION CONTROL
Star Fleet Mission Control is the large central monitoring area within the Star Fleet
Operations Center, located in the heart of Starbase Central, whereby the entire
operation of the fleet can be monitored and directed. All essential military operations are
monitored and controlled at this facility. However, secret intelligence operations are not
monitored in this facility. Due to the secret nature of intelligence operations, they will be
managed and controlled within their own facility known as the Star Fleet Intelligence
Operations Center. However, there is a direct communications link to Mission Control
from the Intelligence Operations Center in order that some of the joint intelligence
operations may be coordinated with military operations.
The Star Fleet Mission Control Center, as described in Section 1.8 of this volume, is
divided into several areas or sections devoted to handling the various operational tasks
required for fleet command and control. Specifically, the two primary forms of operations,
strategic and tactical, will be managed by the Federation Strategic Command
(STRATCOM) and the Star Fleet Tactical Command (TACOM) units. The STRATCOM
section will perform the command and control of all the strategic plans and operations,
while the TACOM section executes the short-term tactical plans. Both forms of operations
are controlled and monitored within Mission Control.

VOLUME II
5.2 FLEET OPERATIONS

In this section the types of operations that Star Fleet will be engaged in will be discussed.
In general, there are two types of operations: Strategic and Tactical, both of which will
be discussed in the subsequent sections.
STRATEGIC OPERATIONS
Strategic Operations are those designed to carry-out the long-range strategic plans of
the Federation Council that have a global affect. That is, those plans that will affect the
entire Federation. Basically, such operations are political in nature that have a galactic
impact and are not bound by a single area of operations. A simple example of a Strategic
Operation is the general deployment and posturing of forces throughout the Federation,
the purpose of which is to distribute the forces in areas where conflict will most likely occur
or to display a “show of force” in order to deter conflict.
Strategic Operations also includes the monitoring of Federation space. Star Fleet has
deployed many signal buoys and other monitoring devices throughout Federation space.
These devices provide an early warning system to defend against incursion and general
invasion. Such monitoring will be performed within the Mission Control Center at the
very center of the Star Fleet Operations Center.
Strategic missions originate mostly within the Military Staff Committee. At the direction
of the Federation Council, the Federation Joint Chiefs of Staff will be directed to
execute some plan developed by the Council. The Joint Chiefs, along with the Director:
Star Fleet Command, will develop the basic direction of the effort and will establish the
guidelines and criteria for success. The Director will then submit the strategy to the Chief
of Star Fleet Operations in order that the specifics of the operation can be worked out
and executed. Once established Strategic Operations will generally be executed and
managed by local Starbases in coordination with the Star Fleet Operations Control
Center.
The area of strategic operations planning and execution within the Star Fleet Division of
Operations is called the Federation Strategic Command or STRATCOM. The scope
of this STRATCOM’s responsibility will include the interrelated areas of space operations,
information operations, computer network operations, and strategic defense and attack. As
such, STRATCOM is a globally focused command and control, intelligence, surveillance,
communications and reconnaissance network located inside the Star Fleet Operations
Control Center. As such, STRATCOM is linked with Star Fleet Intelligence and the
other Federation intelligence agencies in the development of specific strategic
assignments.

VOLUME II
STRATCOM is the command and control center for Star Fleet forces that directs military
space operations, computer network operations, information operations, strategic warning
and intelligence assessments as well as global strategic planning. STRATCOM is made up
of members from the following Star Fleet divisions or offices:
 Star Fleet Intelligence,

 Star Fleet Office of Strategic and Tactical Operations,
 Star Fleet Office of Strategic Planning,
 Star Fleet Adjunct Forces Command, and the members of the
 Federation Joint Chiefs of Staff.
Some of the more specific responsibilities of STRATCOM include:
1. Deterring conflict by posturing forces to conduct operations in response to a threat of

a major military attack upon the Federation,
2. Employing forces as directed by the Director: Star Fleet Command, the Military
Staff Committee, and the Federation Council,
3. Coordinating directly with Local Force Commanders and with Star Fleet Force
commanders as directed by the Director: Star Fleet Command,
4. Conducting integrated strategic operational planning,
5. Conducting galaxy-wide strategic reconnaissance when appropriate, and
6. Coordinating with various service component commanders and supporting combatant
commanders on issues relating to the organizing, training, equipping and support of
the forces used for STRATCOM missions.
In command of STRATCOM is the Commander: Strategic Operations Command or

COMSTRAT. The COMSTRAT is typically a line flag officer who will typically be given the
rank of Admiral. The COMSTRAT will usually be selected by the Director: Star Fleet
Command in coordination with the Chairman: Federation Joint Chiefs of Staff. The
function of the COMSTRAT is to command and coordinate the activities of STRATCOM,
to issue policies for the management of the command, and to manage the Strategic
Global Strike Plan. In addition, the COMSTRAT also provides a voice to the Military
Staff Committee on all matters related to strategic policies, force structure, and fleet
modernization, as well as implications of Federation policies and initiatives that could
affect STRATCOM.
TACTICAL OPERATIONS
Tactical Operations are those designed to carry-out the short-term plans of Star Fleet
or the Military Staff Committee, which are generally of short duration and will usually
have only a local effect. That is, Tactical Operations are performed for a single purpose
at a specific location or area and for a limited period of time. Such operations are usually
military in nature and are generally initiated by Star Fleet. An example of such a tactical
operation would be the survey of a specific planet near a hostile area of space for the
purpose of determining its benefit as a base of operations. Such a survey mission would be
carried out in order to obtain some future tactical advantage over a hostile force should it
become necessary. In general, all major Tactical Operations and the missions assigned
to operating units are developed by Star Fleet Command; specifically, by the Star Fleet
Tactical Command (TACOM).

VOLUME II
TACOM is essentially a sub-organization of the Star Fleet Office of Strategic and

Tactical Operations (TAC), which develops the short-term missions based upon the
plans originated by STRATCOM. As such, the scope of responsibility of TACOM is very
similar to that of STRATCOM, but which is primarily focused in the development of
specific tactical assignments. TACOM is also located within the Star Fleet Operations
Control Center and it will be TACOM which will normally monitor the specific missions
and assignments of the Operating Forces. As part of its responsibilities TACOM also
manages all the TAC stations located at classified locations throughout Federation space.
The function of these stations is essentially intelligence gathering, surveillance and
reconnaissance so that tactical plans can be formulated. These are small stations located
near strategic areas, which will be discussed in more detail in Section 7.3 of this volume.
Such missions, as described above, are called TACOPS and will generally be managed by
the fleet command to which the operation is assigned. As such, the specific undertakings
developed for such operations will be produced by TACOM and assigned to a Fleet
Commander, who will develop the detailed plans for execution by his forces. Possibly,
such Tactical Operations may require a special force to be assembled from units of the
fleet command. As such, these units will be considered as the Tactical Elements of the
force created to perform the operation, and each Tactical Element will have a specific
function to perform within the force.
Tactical Operations also includes the specific operations that may be performed by a
force or by an individual unit during combat. These operations could be specific maneuvers
executed in order to gain some advantage over an opponent. Such tactical operations or
functions consist of the best use of weaponry and shields, the positioning of spacecraft
relative to the opponent, the employment of special maneuvers and the consideration of
secondary and tertiary tactics.
Tactical Operations may also include special operations as well. These are essentially
clandestine military operations designed to accomplish some military or political objective.
Such operations will generally employ Special Forces of the Star Fleet Marine Corps
and may also involve personnel from the Star Fleet Intelligence Clandestine Service.
Teams or groups performing such operations are usually called Tactical Operations
Commands or TOC’s. A TOC is a small group of specially trained military personnel that
perform special clandestine military operations and missions. Each member of the team is
considered an active Tactical Element during such an operation. Such TACOPS require
extensive and specialized training. TACOPS training is conducted by a diverse group of
highly experienced instructors with extensive real-world experience. Instructors are drawn
from the elite of the military and intelligence community — professionals who are currently
operational.
In overall command of TACOM is the Commander: Tactical Operations Command or

COMTAC, who is also the commander of Star Fleet Office of Strategic and Tactical
Operations (TAC). The function of the COMTAC is to command and coordinate the
activities regarding the development of Tactical Operations. The COMTAC will typically
be selected by the Chief of Star Fleet Operations.

VOLUME II
FUNCTIONAL OPERATIONS
Functional Operations are those relating to the basic mission of Star Fleet such as
exploration, galactic surveying, colony support and scientific investigation. They are
generally non-military in nature, but not in all cases. Many of these types of Functional
Operations will be in the form of General Orders issued to commanders in the field and
to be performed as part of their normal patrol duties. However, specific missions will also
be developed for specialized purposes.
FLEET MOVEMENTS
Fleet Movement generally refers to the deployment of the Operating Forces. Fleet
movements will generally be based upon the tactical or strategic directions developed by
Star Fleet Operations, which will include such things as:
1. Movement and relocation of ships, squadrons and fleets,

2. Movement and relocation of Fleet Marine troops and forces,
3. The location and placement of bases and stations, and
4. The creation and deployment of special Task Groups.
In general, fleet movements are the deployments of Star Fleet assets and personnel,
which will be developed and monitored by Star Fleet Operations. However, specific
movements within a fleet or force will always be up to the Fleet or Force Commander,
which may include the creation and deployment of specialized Task Groups.
FLEET ASSIGNMENTS
Fleet Assignments are the specific orders, directives, instructions or guidelines given to
Fleet or Force Commanders for the accomplishment of Star Fleet goals and objectives.
Such directives will always be developed by Star Fleet Operations and issued to Fleet
Commanders, Sector Commandants or other commanders as generalized guidelines
or goals that have to be accomplished. The commander receiving such instructions will
examine and interpret the guidelines or goals issued them and will develop the specific
operational plans for his or her forces to carry out. As such, Star Fleet Operations will
give field commanders the freedom to develop the mission and assignment specifics.

VOLUME II
5.3 FLEET ASSIGNMENTS AND MISSIONS

A mission is an assigned task or undertaking designed to accomplish an operation or
function. Missions are developed and assigned to the Operating Forces by Star Fleet
Command; specifically, by the Star Fleet Division of Operations. The function of this
section is to outline the origin of such assignments and how they are carried out.
FEDERATION PLANS AND POLICIES
Chapter V of the Articles of Federation established the Federation Council as the

executive branch of the Federation government that has overall responsibility for
developing and formulating Federation policy. In addition, the Federation Council is
the controlling authority over all the peacekeeping forces of the Federation through its
Military Staff Committee, which includes both Star Fleet and local system forces.
Therefore, the basic policies regarding the peace and security of the Federation originate
within the Federation Council and will be assigned to the Military Staff Committee
for implementation.
Plans and policies created by the Federation Council are generally global in nature as
they deal almost exclusively with the peace and security of the entire Federation. As
such, the Federation Council will usually craft strategic policy objectives that will
become Strategic Missions assigned to Star Fleet by the Military Staff Committee.
Because of the global scope of such missions, Strategic Missions usually involve large or
multiple force units, and may include Adjunct Force units as well.
On the other hand, specific Federation policies that can be implemented on a regional or
local level will be planned and implemented by Star Fleet, with the express approval of
the Federation Council. As such, the Federation Council will issue policy guidelines to
Star Fleet along with the complete freedom to craft the missions and operations designed
to execute such policies as Star Fleet deems appropriate. Therefore, Tactical Missions,
developed by Star Fleet Command, are primarily intended to accomplish specific military
objectives or implement specific regional policies that are designed to meet current needs
and goals. As such, Tactical Missions generally involve only small units and will be local
in scope.
Star Fleet, under standing orders from the joint Military Staff Committee and the
Federation Council, will execute its primary functions, as outlined in the Star Fleet
Charter, through the development and implementation of Functional Operations.
MISSIONS ASSIGNED BY THE FEDERATION COUNCIL
Missions developed by the Federation Council and assigned to Star Fleet that are of a
more secretive nature will generally be handled directly by Star Fleet Intelligence. In
general, all intelligence, clandestine or covert missions will be developed and executed by
Star Fleet Intelligence, with the approval of the Federation Council through the
Military Staff Committee, except those that may be delegated to the Federation
Intelligence Agency. Such assignments will usually be in the form of clandestine or
covert operations that will be performed by Star Fleet Intelligence, alone or in concert
with selected units of the Operating Forces.

VOLUME II
MISSION DEVELOPMENT
Mission development will basically depend upon the Star Fleet unit selected to accomplish
the goal. Most missions are assigned to Star Fleet ships. However, Star Fleet bases may
also be assigned missions as well. Such base missions will typically involve the use of local
assets such as shuttlecraft or troop forces. In addition, missions assigned to Star Fleet
ships may also involve bases as well. In such situations the base will be assigned the role
of logistics center for the mission supporting the ship in the accomplishment of its mission.
As such, the orders sent to the ship Commanding Officer will also be sent to the Base
Commander as well.
The first step in mission development will be to define the goals or objectives and the
criteria for success. In most cases the goals will be set by the Federation Council or the
Military Staff Committee. However, goals and objectives that are designed to meet the
basic functions delegated to Star Fleet will be developed by Star Fleet Operations.
The next step is to identify the key mission components. The purpose of this step is to
determine the assets needed to accomplish the goal or objective. A mission component
may be a ship, a force, the type and qualifications of personnel or the equipment needed.
Most missions will generally involve Starships, which generally possess the equipment
needed to execute the majority of the missions.
The next step is to create the Logistics Plan, if one is required. A Logistics Plan will be
developed in the case of large missions of extended duration, where provisions and other
consumables will need replenishment. In this case the plan will include the supplies and
materials that will require periodic replenishment, the frequency of replenishment and the
schedules for re-supply activities. However, for small single-time efforts, a Logistics Plan
may not be necessary. For example, a certain mission may be assigned to a Starship to
perform some special scientific study. Since most Starships are fully equipped with
scientific resources, such as laboratories and equipment, it will not be necessary to
develop a Logistics Plan. In this particular instance it will be up to the Commanding
Officer of the vessel to develop the Logistics Plan if needed. However, where a specific
piece of equipment is not normally carried on board the ship, the Logistics Plan will
identify the nearest location, such as a Starbase, where the equipment may be obtained.
The next step is to develop the Mission Profile. A Mission Profile is the summary of the
generalized steps that will be involved to execute and complete the mission. The profile
will also define the measure that will be used to gauge the success of the mission as well
as the reports or deliverables that must be submitted at the conclusion of the mission.
However, the Mission Profile will only provide general guidelines. The commander of the
operation to whom the Mission Profile is assigned must make the detailed plans and
procedures necessary to carry out the plan.
From the Mission Profile specific orders will be drawn up and issued to the command or
the units involved. An order of this type is simply a directive with a synopsis of the mission
profile. The full profile will be attached to the order as reference or supplemental material.
These mission orders will be issued by Star Fleet Command and sent to the command
units, via subspace radio, by the Star Fleet Office of Fleet Communications. A typical
example of such an order may be found later in this section.

VOLUME II
ASSIGNMENT OF MISSIONS
As previously stated, the assignment of a mission will be based upon the Mission Profile
and the key components necessary to successfully accomplish the goal or objective. Based
upon the mission profile, Star Fleet Operations, or the Force Commander to which
the profile has been assigned, will determine what assets will be needed and then assign
them to the mission. Should the Mission Profile be directed to a Fleet Commander, he
will determine which ships, craft or squadrons or other units will be needed to complete
the assignment. It will then be up to the individual Unit Commanders to organize and
acquire the assets needed for the successful completion of their part of the overall mission.
The assignment of all missions to the Operating Forces and Shore Establishments is
the responsibility of Star Fleet Operations. Specifically, it will be Star Ship Command
that will develop the missions involving ships and craft, and Star Base Command that
will develop the assignments for bases and stations. Each of these Type Commands have
offices assigned specifically for the purpose of developing and assigning missions and
operations, and where joint action is required, these organizations will work together in the
development of the whole operation.
EXAMPLE OF A WRITTEN ORDER
Star Fleet Operations will generally draft all orders and will communicate these orders
to shore facilities for dissemination to the fleet or directly to individual units. In most cases
there is complete visibility of the operation by all units, whether they are involved in the
operation or not. This, however, does not apply to special intelligence operations since a
level of security and likely plausible-deniability must be maintained. Only those units that
will have a “need to know” will be aware that such operations are taking place.
Star Fleet orders will generally be written communiqués. Operational order will visually
and verbally be transmitted to the command via special subspace channels, which will be
followed-up by a written version, which is entered into the receiving command’s computer.
The commander to which the order is issued must acknowledge the message by sending
an electronically signed and stamped version of the order back to Star Fleet Command,
with the date of receipt and acknowledgement by the commander.
An example of a written order issued to a Starship Commander is illustrated on the

following page. The Commanding Officer receiving such an order will usually read the
order on an electronic clipboard and sign it with a stylus. The action of signing the order
will automatically time-stamp the signature, which will indicate acknowledgement. The
signed version is then electronically sent back to the communications computer for later
encoding and transmission to Star Fleet Command. Once signed and acknowledged, the
Commanding Officer will announce and read the order to the entire command via the
ship’s intercom.

VOLUME II

STAR FLEET COMMAND HEADQUARTERS
UNITED FEDERATION OF PLANETS
STAR FLEET OPERATIONS ORDER 3217 STARDATE 21749.8
TO:
COMMANDING OFFICER
U.S.S. ENTERPRISE NCC-1701
FROM:
Pursuant to Fleet Operations Directive 512.3c you are hereby ordered to:
1. Proceed with all speed to the Carinae Station (SSN-20) in Sector 428O for
refitting and installation of the M-5 Multitronic unit. There, you will grant leave
and liberty privileges to all members of your crew with the exception of those
officers that may be required to control and maintain the ship. Expected time of
arrival: Stardate 21766.2.
2. Take on as passenger Dr. Richard Daystrom of the Daystrom Institute for the
purpose of overseeing the testing of the M-5 unit. He is to be in complete charge
of the installation and testing of the unit and you will render him all possible
assistance.
3. Proceed to Sector 428L where you will rendezvous with Starships U.S.S. Hood
(NCC-1703), U.S.S. Potemkin (NCC-1702), U.S.S. Excalibur (NCC-1704) and
U.S.S. Lexington (NCC-1709) for the purpose of exercising the M-5 under
simulated combat conditions. You will report to Commodore Robert Wesley,
Commander: Fleet Squadron 35 for assignment.
4. Upon completion of combat exercises you will proceed to test the M-5 unit in
standard operational conditions and evaluate the performance of the unit.
5. After all assignments have been completed, you will proceed directly back to the
Carinae Station for refitting and debriefing.
The anticipated duration of the mission should not take any longer than five (5) standard
days.
By order of:
Commander: Star Fleet Ship Operations

VOLUME II
5.4 FLEET OPERATIONAL ORDERS

In general, an Order is a directive declaring what must be accomplished, but leaving the
method of execution up to the individual or organization that was so directed. On the other
hand, Operational Orders are specific instructions given to the Operating Forces in
order to accomplish the missions and goals to which Star Fleet is responsible. In this
context, this section will deal strictly with those orders related to performing an operation
or mission and as such, will exclude any instruction relating to the routine operation of any
command.
The central authority for the issuance of Star Fleet operational orders and directives is
Star Fleet Operations. It is Star Fleet Operations that assigns ships and vessels to
Sectors and Areas, and it is Star Fleet Operations that assigns missions, operations
and exercises to the Operating Forces through the Star Fleet Chain of Command as
illustrated in Figure 2a34.1. Operational orders received by any command, whether visual
or audio, will be followed by an electronic version sent via subspace radio and inserted
directly into the command’s computer system.
STANDING ORDERS
Standing Orders are those that, when issued, remain in effect until it is rescinded by the
issuing officer or countermanded by higher authority. Standing Orders can be issued by
anyone in a command position. For example, a Starship commander may issue standing
orders to clear Impulse vents every half hour. As such, Standing Orders are generalized
instructions that remain in effect for an indefinite period of time. They are intentionally
vague, giving only a brief or general description of the functions or operations that must
be performed. It will be up to the executing officer to interpret and carry out the order.
GENERAL ORDERS
General Orders are “standing orders” issued by the Director: Star Fleet Command to
all commanders and Star Fleet personnel. The primary function of General Orders is to
codify the basic functions of Star Fleet, as established by the Star Fleet Charter or Star
Fleet Regulations, into specific directives that must be carried-out. Only the Director
can issue General Orders under ARTICLE 71 of the Charter. When issued, General
Orders must be reviewed and approved by the Federation Council President in order
to ensure its legality and that the order fits within the designated functions of Star Fleet.
As with issuing General Orders, the Director is the only one within Star Fleet that can
rescind them. And as with issuing General Orders, the Federation Council President
must approve the annulment of them. A current list of active General Orders is contained
in Table 2a54.2.
FUNCTIONAL ORDERS
Functional Orders are the specific assignments given to individual commanders to

accomplish some particular mission or goal. They are usually meant to accomplish
Functional Operations. Functional Orders can also be issued to individuals to perform
a task or to assign an individual to a command or function. Such Functional Orders are
generally in the form of a Direct Order.

VOLUME II
TRANSMISSION OF ORDERS
Operational and Functional Orders are always transmitted via special secured
subspace communications channels for use only by Star Fleet. They can either be sent
directly to the command, or relayed through the Shore Establishment to the relevant
commands. The following diagram illustrates the command layers through which orders
are transmitted and received.
Figure 2a54.1
STAR FLEET COMMAND LAYERS
Outposts
Stations
Starbases
Star Fleet
Central Starship Units
Command
Operational Orders are also transmitted in a specific format. This format is set by the
Star Fleet Office of Fleet Communications and set down in FLTCOMMREGS (see
Section 5.6 for details). The following table presents a general description of the format of
any subspace message or order.
Table 2a54.1
OPERATIONAL ORDER FORMAT
Order Section Description/Contents
 Message Addresses & Prefix Codes
Header  Encoding/Decoding Protocols
 Message classification
 Copy of the written order or message
Body and Attachments  Copy of any attachments, diagrams or other reference
material relevant to the message or order
 Instructions or programs inserted into the command’s
Command Instructions computer system for execution
 New encryption software
 Message return requirements
Return Codes
 Return encryption
General and Standing Orders, on the other hand, are published documents that can be
accessed by anyone through the command’s Library-computer. Functional Orders
may be placed in the Library-computer for non-classified and general missions. All
missions that require a high level of security will not be posted in the Library-computer
or where they can be accessed by the public.

VOLUME II
Table 2a54.2
STAR FLEET GENERAL ORDERS
General
Order
Title Description
The Cultural Non-Interference or Prime Directive is designed to
1 Cultural Non-Interference prevent any member of the Star Fleet from interfering with the normal
social and or technological progress of developing worlds.
General Order 2 establishes guidelines for the use of armed force in
2 Use of Force
peacetime and to prevent willful harm or injury to any intelligent being.
General Order 3 is considered the second "Prime Directive" as it
concerns the interference of developed worlds, whereas, General
3 Territorial Integrity Order 1 relates to developing worlds. The basis for General Order 3
comes directly from the Star Fleet Charter that prohibits Star Fleet
from intruding upon the jurisdiction of local and foreign governments.
The Articles of Federation tasks the Star Fleet with the defense of the
4 Protection of Federation Space Federation. As such, General Order 4 directs the Star Fleet to protect
and defend Federation space, and all its citizens and assets.
The Star Fleet Charter tasks the Star Fleet with the protection of
Federation trade. Any interruption of trade greatly affects the
5 Protection of Federation Commerce economy and, thus, the security of the Federation. Therefore,
General Order 5 requires Star Fleet Commanders with protecting
Federation trade.
General Order 6 is designed to prevent enemy forces from obtaining
and holding any Star Fleet asset or to gain any information that could
6 Protection of Commands
be used to endanger the United Federation. It is also designed to
protect the Federation and its citizens from communicable diseases.
Originally established to prohibit contact with the planet or to enter the
system of Talos IV. Violation of this directive carried a mandatory
death sentence. General Order 7 was temporarily suspended in 2266
7 Planetary Quarantine
and revised to remove the death penalty provision. In addition, the
directive was amended to include other worlds as well, and was no
longer singularly applicable to Talos IV alone.
General Order 8 prescribes the action that must be taken if it is
8 Galactic Alert suspected, or that indeed an invasion of Federation space has taken
place.
General Order 9 was designed to impress upon persons commanding
or operating Star Fleet ships and craft the need handle their vessels
9 Ship Handling
responsibly, and to adhere to the rules of navigation and ship
handling.
The purpose of this General Order is to establish the procedures
required to isolate a command from the dangers of disease or other
10 Command Quarantine agents that will adversely affect the health and safety of the general
public. Isolation of a command is required by law to prevent the
spread of such agents and disease to an unsuspecting public.
General Order 11 implements Star Fleet's exploration function as
required by the Star Fleet Charter. This General Order directs Star
11 Space Exploration Fleet ship Commanding Officers to perform space exploration while in
the course of their normal patrol duties. This General Order instructs
ship Commanders to seek out new life and new civilizations.
General Order 12 directs Star Fleet Commanders to identify and
determine the intentions of all vessels in space. This order requires
12 Encounters in Space
Commanders to take adequate precautions when approaching
spacecraft in which contact has not been made.
General Order 13 directs Star Fleet Commanders to aid all spacecraft
13 Vessels in Distress
and persons in distress per Star Fleet Regulation 6630.
General Order 14 reiterates the importance of maintaining and
adhering to the rules regarding Buffer and Neutral Zones. Such zones
14 Neutral and Buffer Zones are legal boundaries, the violation of which may have serious political,
military, economic or other consequences that may affect the peace
and security of the Federation.

VOLUME II
Table 2a54.2
STAR FLEET GENERAL ORDERS - CONTINUED
General
Order
Title Description
General Order 15 emphasizes Star Fleet Regulation 4670. This
15 Flag Commanders Embarked General Order also reiterates the relationship between Commanding
Officers and Flag Officers embarked on commands.
General Order 16 clarifies the duties of Star Fleet personnel when
16 Search and Seizure contraband or illegal items were found during lawful inspection of
private and commercial vessels under General Order 5.
General Order 17 was formally issued to grant Star Fleet full law
17 Federation Law Enforcement enforcement authority and to direct Star Fleet Commanders and
Commanding Officers to exercise this authority without reservation.
The objective of General Order 18 is to reemphasize and revitalize
18 Military Conduct and Leadership Star Fleet leadership in all its aspects: inspirational, technical, and
moral.
General Order 19 reiterates the roles and responsibilities of Star Fleet
Commanders to protect and support Federation colonies, settlements
19 Federation Colonies
and expeditions, and establishes the rules governing the support and
authority of Star Fleet over commercial and private colonies.
The purpose of General Order 20 is to direct the commanders of Star
Fleet forces to organize and deploy their forces where they can best
20 Fleet Deployment
protect and defend the interests of the United Federation of Planets as
specified in ARTICLE 69 of the Star Fleet Charter.
The purpose of this General Order is to codify Star Fleet’s role during
treaty negotiations as specified in ARTICLE 32 of the Star Fleet
21 Treaties and Agreements Charter and to specify that Star Fleet does not have the authority to
prepare, make or present any treaty or agreement without a proper
Federation Consul present.
This General Order sets the Rules of Engagement that Star Fleet
22 Encountering Hostile Forces Commanders must adhere to when encountering forces of known
hostile governments.
This General Order is essentially the second part of General Order 22
and deals solely with the engagement of hostile forces. However, this
23 Engaging Hostile Forces
General Order also applies during law enforcement operations as
well.
The purpose of this order is to project Federation power on a
belligerent world. Should the situation require such action, the
24 Automated Planetary Destruction
Commanding Officer may issue General Order 24 when considering
the safety of his ship or persons under his command.
The purpose of this General Order is to establish the guidelines to
25 First Contact Star Fleet Commanders and senior officers regarding the initial
contact of newly discovered civilizations and peoples.
This General Order is issued as a result of an incident involving a Star
Fleet garrison and a Starship within the territorial boundaries of an
unknown power that had legal claim to the area of space the garrison
26 New Space Identification
was located. As a result of this incident the United Federation of
Planets instituted new guidelines regarding the exploration and
colonization of unknown space, which are known as the Gorn Rule.
The basic purpose of this General Order is to reiterate the law
enforcement role of Star Fleet Commanders as it relates to
27 Drug and Contraband Interdiction possession or transport of illegal drug and contraband. Star Fleet
Commanders are encouraged to use their law enforcement authority
in the interdiction of such illegal substances or materials.
The purpose of this order is to reiterate the intelligence function of
28 Gathering Intelligence
Star Fleet Commanders.
This General Order reiterates the relationship between a
29 Federation Officials Onboard Commanding Officer and a Federation government official that is
embarked or that is visiting the command.

VOLUME II
5.5 FLEET OPERATIONAL COMMAND

In this context Operational Command is defined as the central authority or organization
responsible for carrying out the operational directives of Star Fleet Command. In almost
all cases the person responsible for carrying out Star Fleet Command directives will be a
“Commander”, which, in this context, is not a specific rank but the title of a position of
considerable authority and responsibility as defined in Star Fleet Regulations.
The authority and responsibility of a Commander is specifically set down in Star Fleet
Regulation 3210. Particularly, a Commander is wholly responsible for the satisfactory
accomplishment of the missions and duties assigned to him and his command. Such
responsibility is his and his alone and cannot be transferred. Therefore, the authority
conferred upon a Commander is called “Operational Command Authority”, or simply
“Command Authority”, which cannot be delegated. It is defined as the authority to
perform those functions of command which involve organizing and employing command
units and forces, assigning tasks, designating objectives, and giving authoritative direction
over all aspects of military operations, joint training, and logistics necessary to accomplish
the missions assigned to the command. Command Authority will normally be exercised
through the commanders of subordinate organizations. Combatant command (Command
Authority) provides full power to organize and employ commands and forces as the
Commander considers necessary to accomplish assigned missions. As such, this form of
operational control, therefore, is a necessary part of Command Authority.
Command Authority may be exercised by Commanders at any echelon at or below the

level of combatant command. As previously stated above, operational control is inherent in
combatant commands and may be delegated within the command. When force units are
transferred between combatant commands, the command authority over such forces the
gaining commander will exercise (and the losing commander will relinquish) must be
specified by the Director: Star Fleet Command. As such, all Command Authority will
come from the Director. However, for Operational Control of Star Fleet forces, the
Director: Star Fleet Command has delegated the awarding of this authority to the
Chief of Star Fleet Operations.
Normally, this authority is exercised through subordinate joint force commanders and/or
functional component commanders (Functional Commanders). Operational control
normally provides full authority to organize commands and forces and to employ those
forces as the commander in operational control considers necessary to accomplish his
assigned missions; it does not, in and of itself, include authoritative direction for logistics
or matters of administration, discipline, internal organization, or training. Such authority
will normally be given to the Functional or Unit Commanders.

VOLUME II
OPERATIONAL COMMANDERS
An Operational Commander is the one in charge of an operation or mission. He is

usually the head of principal units of the Operating Forces of Star Fleet and is usually
the commander to which most of the operational assignments will be given. His authority
to command forces is provided within Star Fleet Regulation 3210. Such commanders
include:
 Fleet Commanders,
 Flotilla Commanders,
 Group Commanders,
 Type Commanders,
 Task Force Commanders, and other
 Special Operations Commanders.
The aforementioned are usually in command of a unified or specified command with a

broad continuing mission. They are established, and so designated, by the Director: Star
Fleet Command, through the Chief of Star Fleet Operations, with the advice and
assistance of the Military Staff Committee. Operational Commanders will typically
have spatial, geographic or functional responsibilities.
Operational environments in which Operational Commanders must function are

complex and require continuous learning and adaptation. Operational Commanders use
experience, training, applied judgment, and various analytic tools to attain the situational
understanding necessary to make timely decisions in order to maintain the initiative and
achieve decisive results. The more commanders understand their operational environment,
the more effectively they can employ their forces. Mission success in these modern times
demands that forces possess an unparalleled ability to use information to seize, retain, and
exploit the initiative and to achieve decisive results. It demands that commanders prevail
in the continuous struggle for intelligence information superiority, a struggle that begins
before deploying their forces and will continue long after concluding traditional military
activities.
Operational Commanders use the spectrum of conflict to help describe the level of
force in terms of an ascending scale marked by graduated steps. Star Fleet forces will
operate anywhere along the spectrum of conflict, from peacetime military engagement in
areas of stable peace to major combat operations during general war. In each case, the
objective is to create conditions that advance Federation goals.
Operational Commanders execute command and control through battle command.

They understand, visualize, describe, direct, lead, and assess operations within complex,
dynamic environments. In addition, commanders encourage individual initiative through
mission orders and a climate of mutual trust and understanding. Guided by experience,
knowledge, education, intelligence, and intuition, commanders will apply leadership to
translate decisions into action.
Operational Commanders will generally develop one or more Operational Plan that
outlines the goals, objectives and steps needed to successfully execute the plan. Usually,
the commander will develop more than one plan, and these plans may be broad in scope
or highly detailed, depending on the individual commander's preference. But each must
define the conditions of mission success and present the methods for concluding the plan.

VOLUME II
FUNCTIONAL COMMANDERS
A Functional Commander is the officer in charge who executes the Operational Plan
of an Operational Commander. They are typically the Commanding Officers of the
component units, such as Starships, that are under the authority of an Operational
Commander. As such, the burden of completing the tasks within an Operational Plan
will fall upon the Functional Commander. However, the responsibility for completing the
plan rests with the Operational Commander.
EXERCISING OPERATIONAL COMMAND
Effective Operational Command must be continuously developed. This will usually be

exercised or tested through war games and other forms of operational exercises. The
purpose of such exercises is to ensure that operational plans can be carried out seamlessly
and that low-level or subordinate commanders are experienced and capable of assuming a
larger command, if required.
In general, all Functional Commanders will usually obtain such operational experience
through operational exercises. In addition, Operational Commanders will provide their
subordinate commanders with the opportunity to experience Operational Command.
Therefore, training exercises will be developed that allow Functional Commanders to
take on the role of Operational Commander. This is important if the need arises where
an Operational Commander must turn over command to a subordinate commander as
such conditions may occur as specified in Star Fleet Regulation 5960.
OPERATIONAL ASSIGNMENTS
Operational assignments are generally issued to Functional Commanders in the form of

Operational Orders, as previously illustrated in Section 5.4 of this volume. Such orders,
issued by Operational Commanders, will either be sent to specific command units or
broadcast to all units within the command. Operational Orders received by or from
Operational Commanders must be executed, except where such orders may conflict
with other orders. When an Operational Order is received, the recipient is required to
promptly acknowledge the receipt of the order.
In addition, Operational Orders can sometimes be vague as they may only direct a
commander to accomplish some goal or take some objective and therefore, may not
contain any of the details regarding force size or the methods that may be involved in
accomplishing the mission. As such, the recipient will have latitude in determining a course
of action and the resources needed to achieve the desired outcome of the goals stated in
such orders.

VOLUME II
EXECUTION OF ORDERS
The execution of orders given to operational units by an Operational Commander or

Commander in Chief (CINC) will typically be carried out by a Commanding Officer, in
the role of Functional Commander, of the unit or element within the organization. As
such, the success or failure of any operation will depend on the correct interpretation of
such orders by Functional Commanders.
As stated earlier, discretion regarding the interpretation of orders will solely be up to the
recipient Commanding Officer, unless such orders state specific methods, resources or
personnel required to accomplish the mission. As such, Operational Orders are generally
translated by the Commanding Officer, who is given broad authority to interpret such
orders as he or she sees fit. A Commanding Officer may deviate from his orders if he or
she determines that such orders cannot reasonably be carried-out, or that it such orders
requires the commander to perform some illegal action, or that such orders conflict with
orders already given to him or her by higher authority. However, such deviation must be
accompanied by a complete and written justification as stated in Star Fleet Regulation
4120: “A Commanding Officer who departs from his orders or instructions, or takes official
action that is not in accordance with such orders or instructions, does so upon his own
responsibility and shall report immediately the circumstances to the officer from whom the
prior orders or instructions were received.”
Should the Commanding Officer receive conflicting orders, he or she must follow the
procedures laid-out in Star Fleet Regulation 5450. Specifically, this regulation states:
“If an officer receives an order which annuls, suspends, or modifies one received from
another superior, or one contrary to instructions or orders from the Director: Star Fleet
Command, he shall exhibit his first orders, unless he has been instructed not to do so, and
represent the facts in writing to the superior from which the last order was received. If,
after such representation, the officer from whom the last order was received should insist
upon the execution of his orders, it shall be obeyed. The officer receiving and executing
such order shall report the circumstances to the superior from whom he received the
original order.”
In summary, Operational Orders issued to Commanding Officers are the exclusive

responsibility of that officer. The Commanding Officer may, at his or her discretion and
when not contrary to law or regulation, delegate the implementation of such orders to
subordinates. However, such delegation does not relieve the Commanding Officer of the
responsibility to carry out the orders given to him by higher authority.
The execution of an Operational Order will generally require planning before it is

actually carried out. The Commanding Officer receiving such orders will assemble his or
her staff officers as required by Paragraph „a‟ of Star Fleet Regulation 4710. This
regulation states: “Before going into battle or action communicate to his officers, if
possible, his plans for battle or action and such other information as may be of operational
value should any of them succeed to command.”

VOLUME II
THE MILITARY STAFF COMMITTEE
ARTICLE 47 of the Articles of Federation established the Military Staff Committee,

which has the responsibility of executing Federation policy as it relates to the security of
the Federation. In general, the Military Staff Committee has the role of advice and
consent regarding the conduct of war and other military matters. However, it will be the
Chairman, Joint Chiefs of Staff that will receive, directly from the Federation Council
President or from the President’s staff, the directives to carry out specific Federation
policies. Such directives will then be carried out by Star Fleet or by Local Forces under
Paragraph 4 of ARTICLE 47 of the Articles of Federation.
As stated above, the Military Staff Committee is directly accountable for carrying out
Federation policy, as it relates to the peace and security of the Federation. As such,
Federation policy becomes Star Fleet policy, except where it may interfere with the
efficient functioning of Star Fleet, or violate Federation law. As such, all orders issued
by the Military Staff Committee must be treated as though they originated from the
Federation Council President.

VOLUME II

VOLUME II
5.6 FLEET COMMUNICATIONS

In this section the general control of all communications to the fleet will be discussed.
ARTICLE 4 of the Star Fleet Charter gives Star Fleet the authority to establish the
frequencies and channels for Federation-wide communication, and to assign such
frequencies and channels to civilian as well as military units.
COMMUNICATIONS CONTROLS
Control of fleet communications is the sole responsibility of the Star Fleet Office of Fleet
Communication (FLTCOMM). The organizational chart for this office is illustrated in
Figure 2a56.1. In addition, however, the Federation Council has also given Star Fleet
full authority to issue and regulate communications in open Federation space. As such,
Star Fleet is empowered to issue communications licenses and channels to the general
public for the purposes of inter-system communications. The purpose for this centralized
control is to establish standards regarding open space communications and to maintain
consistency in the type and level of communications. For example, a standard set of
frequencies will be compressed together to form a special frequency known as a “ Hailing
Frequency”[1].
Hailing Frequencies are agreed-upon channel groupings which, when used, would emit
a specific signal indicating that a vessel requests to establish a communications link. There
are several types of Hailing Frequencies, each having specific restrictions and all having
been established by Star Fleet. It is a Federation law that all vessels operating within
Federation space must respond to any ship that hails them via a Hailing Frequency. In
addition, all ships must respond to any hail from a Star Fleet vessel[2]. When attempting
to communicate with any vessel it encounters, Star Fleet will use Hailing Frequencies
to establish a communication link with the vessel. Failure to respond to a Star Fleet hail
may result in fines and/or imprisonment.
However, Star Fleet has no authority regarding intra-system communications. Every

system will regulate all communications that occur within their respective system and as
such, Star Fleet must abide by these local intra-system communications regulations while
they operate within the local system. In addition, for stations located and operating within
such systems, Star Fleet will adopt and implement the local communications regulations
within the station's procedures.
COMMUNICATIONS REGULATIONS
The specific regulations regarding deep-space communications that are developed by the
Star Fleet Communications Standards Section within the Star Fleet Office of Fleet
Communication are called FLTCOMMREGS. All vessels that operate within Federation
space must abide by these regulations. The following table provides a summary of the
FLTCOMMREGS communications regulations issued and maintained by Star Fleet.
STARDATE 11255.92 UFP521-2a56.1 CONFIDENTIAL

VOLUME II
Table 2a56.1
SUMMARY OF STAR FLEET COMMUNICATIONS REGULATIONS
Reg. Regulation Title Synopsis of Regulation Text
A. All Star Fleet communications shall conform to Federation laws and regulations regarding
space and planetary communications.
B. Star Fleet shall become the sole agency for the licensing, control and distribution of
frequencies used in open-space communications.
1 General Communications C. Star Fleet shall establish and regulate specific "Hailing Frequencies" for the purpose of
contacting any vessel within the United Federation.
D. Star Fleet shall have no authority to govern or regulate intra-system communications that
are regulated by system governments.
Subspace communications
A. All subspace communications shall come under the control, authority and monitoring of
Star Fleet.
B. Star Fleet shall establish all subspace communications channels and shall assign
2 Subspace Communications designated frequencies to military, private and commercial organizations.
C. Star Fleet shall be the only agency to license and issue subspace communications
channels.
D. Star Fleet shall establish specific Hailing Frequencies used to reach out vessels in order
to establish a communications link.
Standard electromagnetic or sub-light communications shall be used for ship-ship or ship-
3 Standard Communications shore communications within 500,000 km.
All official Star Fleet communications shall be encoded. No uncoded tactical or mission related
4 Coded Communications messages shall be transmitted to the fleet.
Star Fleet shall establish and disseminate the codes and algorithms required to encode and
decode coded communications.
A. All encoding and decoding algorithms shall be maintained and regulated by the Star Fleet
5 Communications Codes Office of Fleet Communications.
B. All codes shall be changed or modified on a continuing basis.
C. The schedule for installation of new codes shall not follow a specific pattern, but shall be
randomly determined.
A. Star Fleet shall be the sole agency to establish and regulate codes used to signal
conditions throughout the Federation.
B. The following Alert Codes are established:
1. Code 1: Galactic Alert
6 Alert Codes 2. Code 2: Galactic Disaster
3. Code 3: Sector Trouble
4. Code 4: Local Disaster
5. Code 5: Standby Alert
C. The use of such Alert Codes shall be controlled by Star Fleet.
Coding Protocols are the computer algorithms, modules or devices used to encode and
decode messages. Star Fleet shall establish such protocols for coded transmissions.
However, private and commercial communications may also be encoded, provided they
7 Coding Protocols conform to the following rules:
A. All private or commercial encoding algorithms are submitted to Star Fleet for review and
approval.
B. Star Fleet shall maintain a library of all private and commercial protocols.
Communications Channels are the specific frequencies through which verbal, visual or data
communications are transmitted or received. As such:
A. Star Fleet shall regulate the use of such channels in open space.
B. Star Fleet shall have the authority to assign communications channels and frequencies
8 Communications Channels to all entities within the United Federation of Planets. As such, Star Fleet shall issue
licenses to Federation entities concerning the use of such frequencies.
C. Star Fleet shall have the authority to revoke the license of any entity that violates
Federation communications regulations.
Priority Channels shall only be used for galactic emergencies. Priority Channels are military
communications channels and as such, shall not be used or tapped into by any civilian, private
9 Priority Channels or corporate entity. Any violation of this regulation is subject to severe sanctions and
Federation prosecution.
Emergency channels are specific subspace, sub-light or electromagnetic frequencies
established for the sole purpose of transmitting distress signals, disaster relief requests,
medical emergency notifications and other designated emergency notifications. As such:
10 Emergency Channels A. Emergency channels shall never be used for any form of communication of a non-
emergency nature.
B. Star Fleet shall, at all times, monitor Emergency Channels for any call for aid or distress,
and shall immediately respond to such requests when received.

VOLUME II
Table 2a56.1
SUMMARY OF STAR FLEET COMMUNICATIONS REGULATIONS - CONTINUED
Government Channels are only to be used by government, Star Fleet and other authorized
11 Government Channels entities within the Federation. Such channels shall only be used by Federation government
offices and agencies.
Inter-government channels are the specific subspace frequencies used for communications
12 Inter-government Channels between member system governments and their agencies. As such, Star Fleet shall have
access to all inter-government communications channels.
Public Channels are the subspace frequencies created by Star Fleet for use by the general
public.
A. Star Fleet shall never, under normal conditions, transmit information or communicate
13 Public Channels between Star Fleet units using Public channels.
B. Star Fleet units may transmit emergency and uncoded messages via Public channels if all
other communication channels are not available.
Commercial Channels are the subspace frequencies created by Star Fleet for use by bone fide
14 Commercial Channels Federation businesses. Used specifically for the communication between commercial vessels
and their ports or business offices.
Private Channels are those electromagnetic or subspace frequencies issued to and reserved
for the use by private citizens of the Federation.
15 Private Channels A. Star Fleet shall not, in the normal course of operations, monitor or tap Private Channels.
B. Star Fleet shall never use Private Channels to transmit or receive official Star Fleet or
Federation government communications.
All Commanding Officers shall allow some form of private communications for their personnel
based on the following provisions:
A. Private communications on board ships shall be non-interactive one-way except as
authorized by the Commanding Officer.
B. The Commanding Office may suspend private communications based on the tactical
situation at the time.
16 Private Communications C. Interactive two-way private communications onboard a base or station shall be allowed.
D. The Commanding Officer of a base or station may suspend private communications as
the tactical situation warrants.
E. All private communications from Star Fleet facilities shall be through Star Fleet
equipment and circuits. No private or secret communications devices shall be used or
allowed on Star Fleet facilities.
Violations of these Communications Regulations carries with it severe sanctions and penalties.
The following penalties have been established:
1. Unauthorized use of Emergency Channels: f 20,000 and ten years imprisonment in a
17 Violations Federation Penal Colony.
2. Unauthorized use of Star Fleet or military channels: f 10,000 and five years imprisonment
in a Federation Penal Colony.
3. Unauthorized use of Private, Public or Commercial Channels: f 5,000.
A communications device is defined as any equipment used to transmit or receive any

information through open space.
A. All communications devices used for communications in open Federation space shall
18 Communications Devices conform to Star Fleet standards.
B. Star Fleet shall regulate the design of communications devices that are intended for
communications in open space.
A Communications network is defined as the system of devices spread across Federation
space. As such:
19 Communications Networks A. Star Fleet shall control and monitor all deep-space communication networks.
B. Star Fleet shall have no authority over local system communications networks.
Subspace communications relay stations shall be under the control and authority of Star Fleet.
A. All Subspace Relay Stations shall be clearly marked with the identification number and
other Star Fleet markings indicating the purpose of such.
20 Subspace Relay Stations B. All Subspace Relay Stations shall emit such identification beacons as necessary for the
safe navigation of spacecraft.
C. All Subspace Relay Stations shall be periodically calibrated to ensure complete and error-
free reception and transmission of subspace communications.

VOLUME II
Table 2a56.1
Communications arrays are large multi-channel antenna devices out in deep space that are
21 Communication Arrays used primarily for data transmission, computer networking and other forms of communications.
Only Star Fleet is authorized to build and maintain such arrays.
A. All communications between Star Fleet vessels shall be coded.
Ship-To-Ship B. All communication between vessels shall be both visual and verbal.
22 C. Communications between Star Fleet ships shall always use the specific channels
Communications
designated by the Office of Fleet Communication.
A. All communications between a ship and a shore facility shall, at a minimum, be verbal.
B. All communications between a ship and a shore facility shall follow the rules regarding the
rendering of honors.
Ship-To-Shore C. Communications between a ship and a station must be initiated by the approaching
23 vessel. The initiation of communications by the ship must begin no less than 1.0 AU from
Communications
the shore facility.
D. Vessels that plan to visit a Star Fleet space station or shore facility must communicate
such plans at least one solar day in advance.
The following are the rules regarding communication between private and commercial vessels
and facilities and Star Fleet vessels and shore facilities
A. All private and commercial vessels shall always initiate (Hail) communications with Star
Fleet vessels and shore facilities.
Private and Commercial B. All private and commercial shore facilities shall always initiate or hail all vessels
24 approaching the facility.
Protocols
C. All vessels shall acknowledge all signals and hails from Star Fleet vessels and shore
facilities.
D. There are no specific protocols regarding communications between private and
commercial shore facilities.
Ground communications are defined as the transmission and reception of information,
messages or instructions between points on a planetary surface.
25 Ground Communications A. All ground communications shall conform to local regulations.
B. Where full coverage cannot be obtained, orbiting satellites are permitted.
Communications satellites may be placed in orbit around a planetary body when conditions
26 Communications Satellites require 360o communications around the planet. However, satellites are temporary orbital
devices and shall be retrieved when no longer in use.
Classified communications is defined as the transmission of any information deemed sensitive
as determined by the Star Fleet Office of Information Security. Classified communications
includes voice and visual communications as well as data and documents transmitted over
communications channels. As such:
27 Classified Communications A. Star Fleet shall set the sensitivity level for all classified communications.
B. All Classified Communications shall be stored in historical archives and the retention
period for the storage of such communications shall be governed by the regulations set
forth in the Star Fleet Manual for Classified Information.
Pursuant to the provisions stated in FLTCOMREG 27, the following regulations are set
regarding the transmission of classified information:
A. Classified information shall never be transmitted unless authorized by competent
authority.
Transmission of Classified B. Transmission of classified information shall only be performed through secured and coded
28 channels.
Information
C. Star Fleet shall establish special coded channels for the purpose of transmitting classified
information to the fleet. Star Fleet shall not divulge such channels to the general public.
D. The Star Fleet Division of Security shall establish the rules governing the transmission of
classified information.
Data Channels are high-speed subspace frequencies used exclusively for the transmission of
scientific, military, computer or other data through a subspace computer network.
29 Data Channels A. Star Fleet shall monitor and regulate all subspace networks.
B. Where full coverage cannot be obtained, orbiting satellites are permitted.
Tight-beam communications is defined as a point-to-point transmission aimed at a specific
unit.
Tight-Beam A. All Classified Communications to specific command units shall be through tight-beam.
30 B. Anyone interrupting or tapping into any Star Fleet tight-beam signal shall be prosecuted
Communications
with no less than 20 years in a Federation penal institution and a minimum fine of
f 100,000

VOLUME II
Table 2a56.1
31 Message Torpedoes REGULATION RESCINDED STARDATE 1856.3.
Recorder Markers are emergency communications devices used to
A. Recorder Markers shall only be deployed under the following conditions:
1. Abandon ship;
2. When General Order 6 is invoked;
32 Recorder Markers 3. When there is a high degree of certainty that the ship or station will be destroyed.
B. When launched, Recorder Markers shall be aimed and directed towards the center of the
Federation at 000-MARK-000.
C. Recorder Markers shall contain a record of all ships activities prior to launch. At a
minimum, recorder markers shall contain a copy of the ship’s most important logs.
A Prefix Code is a communications address to a specific command’s main computer that
allows remote access to the command’s computer by Star Fleet Command. As such:
33 Prefix Codes A. Only Star Fleet Command shall assign Prefix Codes.
B. Only Star Fleet Command shall be cognizant of Prefix Code.
C. Only specified officers of any particular command shall know the command's Prefix Code.
Star Fleet Messages are packets of information sent to commands.
A. All Star Fleet Messages shall contain the Message Header specified by Star Fleet Office
34 Star Fleet Messages of Fleet Communications.
B. Star Fleet Message Headers shall incorporate the Command Prefix Number to identify
the command recipient of the message.
The format for all Star Fleet messages shall be set by the Star Fleet Office of Fleet
35 Message Format Communications.
All Star Fleet communications shall be copied and saved in special communications archives.
As such:
A. Each command shall maintain a computer archive of all communications entering or
Star Fleet Message leaving the command.
36 B. Each command shall determine the level of internal communications that will be archived
Retention
within their command.
C. Each command shall upload their communications archive to Star Fleet Command at
least once each week, conditions permitting.
Star Fleet has established the following retention schedule for all communications:
Message Retention A. Standard, non-classified communications: five years.
37 B. All classified communications: Indefinitely or until declassified by higher authority as
Schedule
specified in the Star Fleet Manual for Classified Information.
Broadcast Messages are general fleet communiqués used to inform the general fleet.
38 Broadcast Messages A. Broadcast Messages shall only be sent on Star Fleet channels.
B. Broadcast messages shall not contain Confidential or Secret information.
Secret messages are defined as specially coded messages designed to hide their contents
39 Secret Messages from Star Fleet. As such, secret messages transmitted by private and commercial enterprises
in open space are not permitted.
Foreign messages are defined as communications that emanate from outside Federation
space and captured within Federation space. As such,
A. Star Fleet shall monitor and regulate all foreign communications.
40 Foreign Messages B. Private individuals or organizations shall not respond to any foreign communications
without permission from the Federation government.
C. For security reasons all individuals receiving foreign communications shall report the
same to Star Fleet authorities.

VOLUME II
Table 2a56.1
As the Federation authority to regulate communications in open space, Star Fleet has the
authority to:
Monitoring of
41 A. Monitor any Private, Public or Commercial channel for compliance with Star Fleet and
Communications Channels Federation regulations.
B. Monitor Government channels as necessary for the peace and security of the Federation.
Star Fleet is authorized to monitor Public, Private and Commercial communications channels
under the following conditions:
Monitoring of Public, A. At any time during conditions of galactic war or other emergency.
42 Private and Commercial B. When there is credible evidence of an illegal insurrection or other illegal activity in
Channels progress.
C. When there is credible evidence that communications directing illegal activities is
occurring.
Star Fleet shall only monitor government channels under the following conditions:
Monitoring of Government
43 A. Government channels where public information is dispensed.
Channels B. Under direction of the Federation Council.
A. When not in use, all Public, Private and Commercial communications channels shall be
Opening and Closing
44 closed.
Channels B. Emergency and Priority Channels shall be open at all times.
Communications Over In general, all tactical communications shall only be transmitted or received over a secured
45 channel.
Secured Channels
All tactical communications that must be transmitted on unsecured channels shall be
performed as follows:
A. If it is suspected that transmissions are being monitored during battle or other tactical
Communications Over situations, the command shall not transmit uncoded messages on an open or unsecured
46 channel.
Unsecured Channels
B. Each command shall establish such Situation Codes as needed to convey accurate
information when 1) communications may be monitored, or 2) when captured and forced
to send a prepared message to the command.
During wartime conditions all official Star Fleet communications shall be treated as containing
47 Wartime Communications classified information. As such, all fleet communications during war time shall be transmitted
over secured, classified channels.
Special communications are specific channels and protocols used by Star Fleet Intelligence for
48 Special Communications secret and classified communications to intelligence operators in the field and to other
intelligence organizations and agencies.
Star Fleet Intelligence is assigned special and secret communications channels. As such, Star
Fleet Intelligence shall be responsible for these channels.
A. All special intelligence channels shall be classified as TOP SECRET – ULTRA
SENSITIVE.
Special Communications B. Star Fleet Intelligence shall not divulge such channels to any entity outside of the
49 intelligence community.
Channels
C. Star Fleet Intelligence is authorized to divulge the special channels only to select
agencies within the Federation intelligence community.
D. Star Fleet Intelligence is the only agency authorized to maintain these channels and any
equipment, such as relay stations, etc.
A. Star Fleet Intelligence is authorized to develop and issue such equipment as necessary
for the purpose of:
a. Surveillance
b. Covert Communications
Special Communications c. Eavesdropping
50 B. Special equipment developed for Star Fleet Intelligence shall be for intelligence use only.
Equipment
Star Fleet Intelligence is not authorized to sell, lend or otherwise give such equipment to
anyone outside of the division without authority from the Director: Star Fleet Command.
C. No private or commercial entity is authorized to produce, posses or otherwise operate
such special equipment.

VOLUME II
COMMUNICATION NETWORKS
Normal space communications utilize electromagnetic waves traveling at the speed of light
(3.0 x 105 kilometers per second). However, this form of communication is much too slow
considering that modern vessels travel at speeds that far exceed that of light and cannot
receive such signals while in subspace. As such, a form of communication wave utilizing
tachyons traveling through subspace was developed. The speed and frequency of the
tachyon wave is dependent on its excitation energy. In addition, this excitation energy is
logarithmic and requires a significant amount of energy.
At this time the maximum speed of subspace communications is limited to an equivalent

speed of Warp 18.1712 or approximately 6,000 times the speed of light. Taking into
account subspace time dilation, the apparent speed of subspace communication is more
like 109,000 times the speed of light[3]. With such speeds the average time a message sent
from Star Base Central to Earth would take about 10 minutes, which is 2.1 light-years
away; from Star Base Central to the Romulan Neutral Zone, about 8 hours, and from
Star Base Central to the outer edge of Federation space, about 23 hours.
Communication time via subspace radio, though quite fast, still takes time to reach the
outer command areas. In addition, subspace radio also has range limitations. Energy
dissipation of the tachyon carrier will cause the signal strength to weaken. As such, the
effective range of a subspace message packet is about 22.65 light-years. In order to
maintain signal strength Subspace Relay Stations are placed throughout Federation
space, the locations of which are classified. These stations contain signal amplifiers that
essentially process the message packet and resend the entire packet. This requires a
substantial power plant and therefore, relay stations were built onto moderately sized
asteroids with pergium-fueled reactors. This system of relay stations constitutes the Star
Fleet Subspace Message Relay System, as illustrated in Figure 2a56.2.
The Star Fleet Communications Network and the Star Fleet Subspace Message
Relay System are maintained entirely by the Star Fleet Communications Equipment
Section of Star Fleet Operations.
SUBSPACE RELAY STATIONS
Subspace Relay Stations were developed to handle the signal and range issues inherent
in subspace communications. Such relay stations are the responsibility of the Star Fleet
Office of Fleet Communications which determines the number and location of these
stations in order to meet the global communications needs of the fleet. These stations are
placed at strategic locations so that a single station may supply multiple bases, stations
and ships with subspace messages within their range. In addition, there is enough overlap
so that in the event that a single station was to be placed out of service, the loss would
not significantly impact the receipt of vital messages. The number and location of these
stations is CLASSIFIED. An example of a Subspace Relay Station is shown in Figure
2a56.3.
Subspace Relay Stations are periodically recalibrated as required by FLTCOMMREG

19C, especially for tight-beam communications. This is primarily due to station drifting or
the unintentional relocation of the station due to gravitational effects and other physical
influences on the structure. The schedule for recalibration is typically around six months
and sometimes up to a year for stations out in deep space.

VOLUME II
COMMUNICATION OF ORDERS AND DIRECTIVES
Orders from Star Fleet Operations are always sent via subspace radio. Messages sent
by Star Fleet are encoded into compressed packets, the technical description of which will
be described in Volume V. The encoded packet is then sent through one or more subspace
frequency channels, depending on the type of message. A subspace channel is a specific
frequency or energy level of the tachyon wave, which can only be picked-up by equipment
attuned to that frequency. In order to handle the myriad of message frequencies and
formats, Star Fleet ships and stations are equipped with multiple-channel subspace
receivers. A diagram of the message receipt process is shown in Figure 2a56.4.
All subspace transmissions are automatically encoded as a matter of course. Encoding and
decoding is performed by the facility’s communications computer. There are several code
formats used in the creation of the message package and each of these formats have been
programmed into all the communications computers throughout the fleet. Each message
packet contains a message header that identifies how the packet is to be decoded and by
what communications subsystem. The header also contains the Prefix Code of the vessel
or station the message is intended. This code is essentially a communications address to
the command’s main computer, which allows remote access to the ship’s computer by
Star Fleet Command. The Prefix Code is also used to program a mission into the ship’s
computer when a high level of secrecy is required. Only Star Fleet personnel with a high
level of security clearance will be allowed to know the prefix code of Star Fleet vessels.
Any ship or base Commanding Officer can select the code in which they will transmit
their messages. The message header contains the necessary information to allow the
receiving command to decode the message. Should any of these encryption/decryption
formats become known to anyone outside of Star Fleet, a message will be sent warning
command units of the security breach along with a programming script that will deactivate
the coding module in the computer and will insert the new coding module.
Star Fleet has two methods of transmitting subspace messages: Broadcast and Tight-
beam. A Broadcast message is sent through all subspace channels and received by all
commands, including all Local Forces. Typically, Broadcast messages are used to send
general information and global alert codes to all the Operating Forces throughout the
Federation. Broadcast messages are also used to send specific information to a single
command as well. The Prefix Code within the message header would identify the specific
command the message was intended, and would only allow the specific command to read
and decode the message.
Tight-beam messages are designed for a specific command only. This form of message
will normally be sent through the Subspace Message Relay System utilizing a special
tachyon beam. The message beam will be sent along the chain of relay stations until the
message reached the last and most appropriate station. The message is then sent to the
command using the special tachyon beam. This form of communication is used primarily
for highly classified messages.

VOLUME II
Figure 2a56.1
2700 Star Fleet

Office of
FLTCOMM Fleet Communications
Communications Communications Communications Cryptographic
COMMREG Standards Section FLTCOMM Equipment Section COMMOPS Operations Section CRYPTO Section

VOLUME II
Figure 2a56.2
GENERAL STAR FLEET COMMUNICATIONS
Station
Relay Starships
Station
Starships
Relay
Station
Starbase
Sector
Starships Base Station

Outpost Station
System
Starbase Base
Station
Outpost
Star Fleet
Operations
Star Base Central
Relay
Outpost Station
Sector
Base
System
Base Relay
Station
Starships
Outpost
Starships
Starbase
Outpost
Starships
Station
Starships

VOLUME II
Figure 2a56.3
SUBSPACE RELAY STATION EXAMPLE

VOLUME II
Figure 2a56.4
GENERAL ONE-WAY COMMUNICATIONS RECEIPT PROCESS
Subspace
Message
Receiver Communications Computer Ship’s Computer
Command Navigational
Coded Message Decoder Execution Subsystem
Hub
Module
Verbal
Security
Subsystem
Buffer
Recorder
Ship’s
Log
Transcriber
Database
Router Secure Secure

Router Log
Database
Queue Bridge Other

Personal Station Stations
Personal Bridge
Data Communications Queue
Library Station Captain’s
Station
Personal
Station

VOLUME II
5.7 STAR FLEET GENERAL ORDERS[4]

In this section the current active Star Fleet General Orders will be presented in their
original document form. As stated, Star Fleet General Orders are the standing directives
issued by the Director: Star Fleet Command to all operational commanders. General
Orders remain in effect for all time unless removed or superseded by a new order and
only the Director can issue or rescind General Orders under ARTICLE 71 of the Charter.
In addition, General Orders are essentially “Star Fleet” orders and as such, cannot
simply be disregarded or changed by any new or incoming Director since they apply to
the Director as well. There is a specific procedure that must be followed whenever any
new order is to be added or an existing order removed.
A General Order will first be proposed by the Director and submitted to the Military
Staff Committee for review. A General Order must first be reviewed by the Joint
Chiefs of Staff before it can become enacted since the order may also apply to Local
Forces as well. When received, the Committee will perform an intense review of the new
General Order to ensure that it is legal and that it will not conflict with another order.
Upon a successful review, the new order will be submitted to the Federation Council
President who will sign it, emboss it with his seal and the order will become law. Once a
General Order is approved it cannot be overridden by another General Order. That is,
one General Order cannot revise or supersede an existing order.
GENERAL ORDER ONE
Although all of the General Orders are important and have the sanction of law, the most
important of them is General Order One or the Non-Interference Directive. This
General Order goes back to origin of the United Federation of Planets when the
Articles of Federation was first established. Specifically, Paragraph 2 of ARTICLE 1
grants the right of self-determination to any social system, regardless of whether they are
a member of the Federation. As such, General Order One was issued to codify that
right and that interference in the normal progress of a civilization was not only immoral,
but harmful to the peoples affected.
Although General Order One primarily applies to Star Fleet personnel it also applies to
Federation citizens as well. No one within the Federation is allowed to interfere in the
normal development, socially or technologically, of primitive worlds, nor is any form of
contamination, such as knowledge of things outside their understanding, allowed to be
introduced into such worlds. As such, Star Fleet is given the primary responsibility to
uphold this principle through the implementation of General Order One and anyone
caught violating it will be subject to criminal prosecution. As such, Star Fleet has been
given the authority to incarcerate anyone violating this law within Federation space.
General Order One however, does provide for a Star Fleet Commanding Officer to
interfere if, and only if, societal or technological contamination has already occurred. In
such cases, the Commanding Officer must obtain proof that such contamination has
occurred, and must be prepared to answer to Star Fleet Command for any action he has
taken to remedy the situation.

VOLUME II

VOLUME II
DIRECTOR: STAR FLEET COMMAND

STAR FLEET GENERAL ORDER ONE: CULTURAL NON - INTERFERENCE
Pursuant to Paragraph 7, ARTICLE 2 of the Articles of Federation, no member of the Star Fleet Service shall
interfere in the normal social or technological development of any culture whether such culture is a member or
non-member of the United Federation of Planets, or whether such world resides inside or outside the territorial
boundaries of the Federation.
In addition, no person in the Star Fleet shall knowingly allow any person to interfere in the normal development
of any culture inside the Federation, nor in territories outside the boundaries of the Federation where no known
government or authority has a legal claim or dominion.
Should any member of the Star Fleet Service come in contact with denizens of worlds where the social or
technological development does not, at least, equal that of the United Federation, it shall be their prime duty
and responsibility to make no reference to the United Federation, its technology, or to the state of galactic
affairs or to its existence thereof. Where applicable and possible, no person in the Star Fleet Service shall
make their presence or identity known to any denizen of a developing world or culture, or provide such
denizens with any indication that cultures or technologies at a level other than their own exists outside the
boundaries of their world.
To ensure compliance with this order, regulations and procedures shall be established to prevent, limit, or
otherwise mitigate any social or technological contamination of developing worlds. It is incumbent upon all
Star Fleet personnel to ensure the normal social and technological progress of such developing worlds at all
cost, even if it requires the forfeiture of their lives in the prevention of such contamination.
Therefore, it is hereby directed that the Chief of Star Fleet Operations shall cause to be developed such
procedures, devices and methods to ensure compliance with this order and to implement policies that will
prevent any violation of this order. In addition, the Judge Advocate General is also directed to research and
establish appropriate penalties for the violation of this order, and design them in such a manner as to deter
violation.
DISCUSSION
The purpose of this order is to allow primitive cultures to progress, socially and technologically, at their natural
rate of development. As such, it is important that contamination of any kind, be it knowledge or a technological
device, not cause a change in that development. This can easily be accomplished by limiting contact with
developing cultures. However, should it be necessary to study a developing culture, special procedures and
techniques shall be employed to keep out of contact with the culture under observation.
In addition to direct contact, Star Fleet vessels are not permitted to perform any function that may make its
presence known to the inhabitants of a developing world. This includes any form of military exercise near or
around the planet.
- PAGE 1 OF 2 -

VOLUME II
STAR FLEET GENERAL ORDER ONE - CONTINUED
APPLICABILITY
This General Order is applicable to all personnel in the Star Fleet as well as all citizens of the United
Federation of Planets.
EXCEPTIONS
The Commanding Officer has the authority, at his or her discretion, to interfere if, and only if, cultural or
technological contamination has already occurred. In such cases, the Commanding Officer shall obtain proof
that such contamination has occurred, and must be prepared to answer to Star Fleet Command and the
Federation Council for any action taken to remedy the situation. A full report justifying such actions shall be
submitted to the Director: Star Fleet Command at the earliest opportunity.
By order of Approved:
Director: Star Fleet Command President, Federation Council

United Federation of Planets United Federation of Planets
Stardate 0034.2
- PAGE 2 OF 2 -

VOLUME II

STAR FLEET GENERAL ORDER TWO: USE OF FORCE
Pursuant to Star Fleet Regulation 6520, no member of the Star Fleet Service shall use force or order the use
of force in time of peace against another planet, culture or against anyone within or outside the territorial
boundaries of the United Federation of Planets, except as an act of self-defense.
The use of force shall only be exercised as a last resort, and then only to the extent that is absolutely
necessary to accomplish the end required, or to counter either the use of force or an immediate threat of the
use of force.
In addition, no person in the Star Fleet Service shall willfully harm or injure any intelligent being or life-form, or
allow harm to come to any intelligent life-form, except in self-defense.
DISCUSSION
The purpose of this order is to reiterate Federation policy regarding the use of force. It is the policy of the
Federation to respect the inherent right of life-forms to exist, and as such, every effort is to be made to prevent
harm or injury to befall any and all life-forms. This principle is most exemplified in the Articles of Federation,
the basis of all Federation law and the source document for the creation of the Star Fleet. Therefore, force
shall only be used as a last resort measure after all other options have been exhausted, and then only in self-
defense. In addition, force may never be used to inflict punishment for acts already committed.
RIGHT OF SELF-DEFENSE
ARTICLE 51 of the Articles of Federation provides for the use of force for individual or collective self-defense
should it become necessary. Star Fleet Regulations require Star Fleet Commanders to take all necessary
precautions to prevent the loss of their command. Therefore, Star Fleet Commanders have the right and the
duty to defend their commands, even to the point of using force against anyone presenting a threat to that
command.
RULES OF ENGAGEMENT
Should the use of force become necessary, the Commanding Officer will use such force as necessary to
disable the threat. Typically, the Commanding Officer will primarily disable the weapons or propulsion systems
of an attacking vessel. During the engagement, the Commanding Officer is prohibited from destroying the
vessel, unless it is absolutely necessary to protect his command or to ensure the safety of the innocent.
The Director: Star Fleet Command, as deemed appropriate, may issue other Rules of Engagement for
circumstances as yet undetermined. Such Rules shall not circumvent or supplant this General Order.
- PAGE 1 OF 2 -

VOLUME II
STAR FLEET GENERAL ORDER TWO - CONTINUED
APPLICABILITY
This General Order is applicable to all personnel in the Star Fleet as well as all citizens of the United
EXCEPTIONS
1. The Commanding Officer has the authority, at his discretion, to use force if, and only if, he has no other
option in the defense of his command and all personnel therein. A full report justifying the actions taken
shall be submitted to the Director: Star Fleet Command at the earliest opportunity.
2. In case of general war, this General Order is not applicable.

Stardate 0981.7
- PAGE 2 OF 2 -

VOLUME II

STAR FLEET GENERAL ORDER THREE: TERRITORIAL INTEGRITY
Pursuant to Star Fleet Regulation 6530, all Star Fleet officers commanding or in command of any Star Fleet
vessel shall respect the territorial integrity of any member or non-member system inside or outside the
territorial boundaries of the United Federation of Planets. No Star Fleet vessel shall cross the boundary of any
system, territory or region of space without obtaining the permission of the local authority governing that
territory unless the proper Rights of Passage have been established with the government of the system,
territory, or planet. However, Star Fleet Commanders entering unexplored or unknown space where no
governing authority can be ascertained may assume such Rights of Passage and Port Visitation Rights.
In addition, no one in Star Fleet shall, by virtue of their rank or commission, interfere in the internal affairs of
any member or non-member system, except as authorized by Star Fleet Command. Failure to comply with this
section of General Order Three shall be considered a violation of both General Orders One and Three and
therefore, shall be subject to the sanction of both General Orders.
No Star Fleet person shall land, disembark, or otherwise visit a planet or facility of any system without first
obtaining permission from both their Commanding Officer and an authorized official of the planet or facility they
intend to visit. Star Fleet personnel shall visit a planet or facility, without permission, only when performing
official Federation business, or if such Port Visitation Rights have been established allowing personnel to visit
the planet or facility.
Star Fleet Commanders shall endeavor to review such treaties or agreements, or consult such Federation
authorities as needed to ensure that the proper Rights of Passage and/or Port Visitation Rights have been
established prior to entering or requesting to enter any territorial space.
In case of general war, however, this General Order may be waived to allow Star Fleet Commanders the
freedom to enter the territories of hostile forces in order to perform such operations as needed to end the
conflict.
DISCUSSION
General Order 3 is considered the second "Prime Directive" as it concerns the interference of developed
worlds; whereas, General Order 1 relates to developing worlds. The basis for General Order 3 comes directly
from ARTICLES 14, 24 and 34 of the Star Fleet Charter, which prohibits Star Fleet from intruding upon the
jurisdiction of local and foreign governments.
In addition, the Articles of Federation are clear on the issue of the sovereignty rights of planetary governments.
Therefore, to enter a system, or territory, or land on a planet is considered trespassing, except where Rights of
Passage and Port Visitation Rights have been established with the local government, and the local
government would have every right to lodge a formal complaint against Star Fleet to the Federation Council for
the violation of its sovereignty.
- PAGE 1 OF 2 -

VOLUME II
STAR FLEET GENERAL ORDER THREE - CONTINUED
APPLICABILITY
This General Order is applicable to all personnel commanding or piloting Star Fleet craft, shuttlecraft or
barges, as well as to officers commanding or in command of Star Fleet ships.
EXCEPTIONS
None; except as authorized by Star Fleet Command.

Stardate 0981.7
- PAGE 2 OF 2 -

VOLUME II

STAR FLEET GENERAL ORDER FOUR: PROTECTION OF FEDERATION SPACE
In accordance with the Star Fleet Charter and Federation law, all Star Fleet Commanders shall:
1. Protect and defend all interests of the United Federation of Planets. This shall include all the territories
and boundaries, citizens, planets, worlds, and assets within the United Federation of Planets;
2. Protect and defend all Federation colonies and expeditions whether they are located inside or outside the
boundaries of the United Federation;
3. Endeavor to protect all Federation citizens whether they are located inside or outside the boundaries of
the United Federation.
4. Under no circumstance shall anyone in the Star Fleet Service give-up or give away any territory legally
owned by the United Federation of Planets.
All Star Fleet vessels are the property of the United Federation of Planets and as such, shall be considered as
an extension of Federation territory in all places where such vessels may be located. Therefore, Star Fleet
Commanders shall take all action necessary to protect and maintain the security of their vessel and all those
embarked on such vessels in accordance with Star Fleet Regulations.
DISCUSSION
ARTICLE 1 of the Star Fleet Charter as well as the Articles of Federation tasks Star Fleet with the defense of
the Federation. Specifically, ARTICLE 26 of the Charter directs the Star Fleet to protect and defend
Federation space, and all its citizens and assets. In addition, ARTICLE 19 requires Star Fleet to maintain the
physical boundaries of the United Federation.
In executing this General Order, the term Federation assets shall be construed to mean all uninhabited
planets, moons, asteroids, as well as hard manufactured assets such as spacecraft and other equipment, and
everything residing within the territorial boundaries of the United Federation.
Lastly, any violation of Clause 4 of this General Order shall be subject to court-martial, and, under certain
circumstances, the penalty of death may be ordered.
APPLICABILITY
This General Order is applicable to all personnel serving in the Star Fleet Service.
EXCEPTIONS
NONE

Stardate 0981.7
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER FIVE: PROTECTION OF COMMERCE
In accordance with the Star Fleet Regulation 6570, all Star Fleet Commanders shall protect, insofar as lies
within their power, all commercial vessels within the boundaries of Federation space in their lawful
occupations; and shall advance the commercial interests of the Federation.
All Star Fleet Commanders shall protect and defend all Federation commercial enterprises and outposts within
Federation space, except where General Order 3 may be violated. Star Fleet Commanding Officers shall use
such force as necessary, and in accordance with the Rules of Engagement as stipulated in General Order 2, to
protect Federation interests.
In order to ensure lawful commercial trade, all Star Fleet Commanders shall, if circumstances permit, stop and
inspect commercial vessels for contraband and/or proper shipping and operating documentation.
In addition to commerce, all Star Fleet Commanding Officers or Officers in Command of Star Fleet ships shall
protect and support all Federation commercial enterprises, colonies and settlements within their area of
operation. Commanding Officers of Star Fleet ships shall periodically inspect and monitor Federation colonies
and commercial enterprises situated in open space as part of their normal patrol duties.
DISCUSSION
ARTICLE 3 of the Star Fleet Charter tasks the Star Fleet with the protection of Federation trade. The protection
of Federation commerce is of vital interest to the security of the United Federation. Any interruption of trade
greatly affects the economy and, thus, the security of the Federation. Therefore, it is necessary that
commercial trade be protected at all times from enemies, pirates and other illegal activities.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders and to all owners of properly registered
Federation private and commercial enterprises, and is applicable to all colonies and settlements whether within
or outside of Federation space.
EXCEPTIONS
The protection of trade within Local Systems is the responsibility of Local Forces. Therefore, unless otherwise
authorized or requested, Star Fleet Commanders are not required to protect trade within member or non-
member social systems.

Stardate 0981.7
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER SIX: PROTECTION OF COMMANDS
All Star Fleet Commanders, Commanding Officers and Officers in Command shall take whatever action is
necessary to protect and maintain the security of their command from the dangers of attack, sabotage and
other actions of subversive or militant groups or of any person with intent to do harm, and to protect and
maintain the security of the command against the dangers of fire, atmospheric breach or other acts of natural
and or unknown phenomenon in accordance with Star Fleet Regulation 4670. However, should it become
inevitable that the command cannot be saved or that command itself may become a danger to the Federation,
the Commanding Officer shall cause the command to be destroyed.
Commanding Officers of Star Fleet ships, craft, bases and stations shall be required to destroy their
commands should it become evident that such commands would be taken by enemy forces.
Commanding Officers of Star Fleet ships, craft, bases and stations shall be required to destroy their
commands should it become apparent that all personnel in the command will perish because of a highly
communicable or uncontrollable disease.
All Star Fleet Commanders shall endeavor to protect other commands from the dangers of disease or enemy
capture. In the case of seizure by enemy forces, the Commanding Officer shall, to the extent possible, inform
Star Fleet Command and issue a Code One alert to all commands. In the case of communicable disease, the
Commanding Officer shall, if possible, transmit a Code 705 warning other commands from becoming infected
or contaminated.
In all cases where the command must be evacuated or abandoned prior to destruction, Star Fleet Regulations
4750 and 4760 shall take effect.
DISCUSSION
General Order 6 was designed to prevent enemy forces from obtaining and holding any Star Fleet asset or to
gain any information that could be used to endanger the United Federation. However, self-destruction is a last
resort measure, and should not be invoked until all the other alternatives have been exhausted.
General Order 6 was also designed to protect the Federation and its citizens from unknown communicable
diseases. If all the persons within a command perished because of disease, General Order 6 is automatically
implemented 24 hours after the last person has died. This action protects other ships or commands from
infection when no one is available to warn the ship or command of the danger.
CONDITIONS
The following guidelines establish the conditions for the use of General Order 6:
1. Self-destruction shall be implemented should it become evident that the command will be seized and
dispossessed of equipment and personnel by enemy forces.
2. Self-destruction may be implemented should it become evident that the Commanding Officer may lose
control of the command by an invader or an invading force.
3. Self-destruction shall be implemented should it become evident that a communicable disease will
overcome and destroy the entire command.
- PAGE 1 OF 2 -

VOLUME II
STAR FLEET GENERAL ORDER SIX - CONTINUED
REQUIREMENTS
The decision to self-destruct a command requires the concurrence of the three most senior officers of the
command or their designees who are eligible to command. All senior officers eligible to perform the self-
destruct sequence must first be identified and listed within the command’s computer in order to perform their
self-destruct responsibility.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders, Commanding Officers and officers eligible to
command.
EXCEPTIONS
General Order 6 or the act of self-destruction may be cancelled at any time should the conditions change
which had invoked self-destruction.

Stardate 2377.4
- PAGE 2 OF 2 -

VOLUME II

STAR FLEET GENERAL ORDER SEVEN: PLANETARY QUARANTINE
No Star Fleet vessel, under any condition, emergency or otherwise, shall contact, visit, or enter the territorial
boundaries of the planets or systems listed in the Table of Prohibited Worlds contained within this order. The
planets listed have been quarantined as they represent a threat to the safety and security of the United
Federation of Planets. Contact of any kind, be it physical or otherwise, including all forms of communication is
strictly prohibited and subject to severe sanctions as prescribed by law. This General Order shall remain in
force in perpetuity, or until such time as when all of the worlds listed have been removed from quarantine.
General Order 7 shall apply to all members of the Star Fleet Service, whether active, inactive, or retired. It shall
be incumbent on all Star Fleet Commanders to direct all personnel under their command to fully comply with all
aspects of this General Order. In addition, no Star Fleet person shall issue any command or directive, or
execute any command or directive that would place themselves or others in contradiction with this Order.
General Order 7 shall also apply to all members of the Federation as well. It shall be incumbent on all Star
Fleet Commanders to prevent contact with the worlds listed by anyone, except as authorized by the Federation
Council.
To ensure compliance with this order, devices shall be placed to warn all vessels that they are entering the
boundaries of quarantined worlds. In addition, procedures shall be developed and implemented to ensure
compliance with this order.
Therefore, it is hereby directed that the Chief of Star Fleet Operations shall cause to be developed such
procedures, devices and methods to ensure compliance with this order and to implement policies that will
prevent any violation of this order. In addition, the Judge Advocate General is also directed to research and
establish appropriate penalties for the violation of this order, and to design them in such a manner as to deter
its violation.
DISCUSSION
The purpose of this order is to prevent contact with worlds that may have an effect or that may threaten the
health, safety, or security of the United Federation of Planets. Such threats to safety and security include, but
not limited to, the health and safety to any persons in the Federation, but may also include aspects or facets of
the quarantined system that may have a deleterious effect on the functioning of the government of the
Federation and any of its members. Such worlds constitute a galactic security threat to the entire United
Federation, and as such, contact with these worlds must be avoided at all costs.
To aid in the evaluation of worlds or planets in which quarantine is required, the following classification system
was developed. These classification codes shall be transmitted by warning buoys in such a manner that all
ships within a radius of 750,000 kilometers shall be able to receive this signal.
- PAGE 1 OF 3 -

VOLUME II
STAR FLEET GENERAL ORDER SEVEN - CONTINUED
QUARANTINE CODES
The following codes are established in accordance with the Federation Agreement on Communications
Standards.
Classification Code Description

7-1 701 Voluntary Isolation - This world requested that it be isolated from, or refuses
contact with, any or all members of the Federation.
7-2 702 Society Under Development - A planet or society where, if visited, may cause the
violation of General Order One.
7-3 703 Renegade Society - World placed under quarantine as a punitive measure, which
may include certain penal colonies.
7-4 704 Physical Hazard - This world contains chemicals, compounds or elements that
are extremely hazardous to health, or are extremely dangerous or unstable to
safely handle.
7-5 705 Medical or Biological Hazard - This world contains organisms or diseases which,
if spread, could endanger the health of the entire Federation.
7-6 706 Dangerous Knowledge or Technology - Knowledge obtained from this society
could endanger the very existence of the Federation.
7-7 707 Delicate Life forms - Entering this world may completely destroy the delicate
ecological balance of the planet, or could destroy all life on that world.
7-8 708 Dangerous Life forms - This world contains life forms which are extremely
dangerous to the United Federation, and therefore, shall not be allowed to leave
the planet.
7-9 709 Misanthropic Society - This society is highly dangerous if allowed to venture out
into deep space.
7-10 710 General War - Entering the system of this world constitutes a safety threat since
the world is engaged in war, either internally or with a planetary neighbor.
Each of the above codes, when transmitted, shall be prefaced with the statement:
UNDER NO CIRCUMSTANCES WHATSOEVER APPROACH THIS PLANET
- PAGE 2 OF 3 -

VOLUME II
STAR FLEET GENERAL ORDER SEVEN - CONTINUED
APPLICABILITY
This General Order is applicable to all Federation personnel whether within or outside the Star Fleet
Service. The specific worlds to which General Order 7 applies are listed in the table below:
TABLE OF PROHIBITED WORLDS
Planet Code Justification

Eminiar VII 710 Currently engaged in a general war with Vendikar (Eminiar III).
Vendikar 710 Currently engaged in a general war with Eminiar VII.
Talos IV 706 Society exists on illusion and therefore, knowledge of their techniques
could endanger Federation civilization.
Taurus II 702 A world undergoing pre-social development.
Omicron Ceti III 705 Contains plant life that could induce behavioral changes in individuals.
In addition, the planet is constantly bombarded by lethal levels of
Berthold rays.
Gamma Trianguli VI 702 Primitive society which needs isolation for proper development.
Gamma Hydra IV 704 Contains unknown elements, which if exposed, could cause hyper aging.
Platonius 709 A society with humanoids that possess unrestrained telekinetic abilities
and therefore, cannot be trusted.
Scalos 704 Contains compounds in its waters that could cause an extreme
acceleration of an individual's metabolism.
Gideon 701 An extremely overpopulated world which has requested isolation.
Tholia 701 The society of this planet does not wish contact with outside civilization
and as such, wishes to remain in isolation.
Melkot 706 The society of this planet has extremely powerful telepathic and psionic
abilities that can immerse an individual into realistic illusions.
Planet at 133-MARK-340/220.3 706 The planet has a device that can alter the course of time.
EXCEPTIONS
NONE
As revised Stardate 21302.9


Stardate 16458.4
- PAGE 3 OF 3 -

VOLUME II

STAR FLEET GENERAL ORDER EIGHT: GALACTIC ALERT
In the event of general invasion or the possible threat of invasion:
A. The Senior Officer Present shall immediately report the threat to Star Fleet Command.
B. The Senior Officer Present shall make such reports as necessary to ascertain the nature and size of the
threat to Star Fleet Command as soon as possible.
C. The Senior Officer Present shall muster such forces as necessary to repel the invasion.
All Star Fleet Commanders, Commanding Officers and Officers in Command shall immediately respond to any
Code 1 Alert signifying a general invasion of the Federation. All Star Fleet Commanders and Commanding
Officers of Star Fleet ships shall proceed with utmost speed to the area designated for assemblage for the
formation of such task commands as necessary to repel the invasion.
In view of the potential for invasion, all Star Fleet Commanders and Commanding Officers shall maintain their
command in such a state of readiness at all times in accordance with Star Fleet Regulations 3300 and 6550.
In the act of repelling such invasion the Use of Force is authorized, but shall abide by the Rules of
Engagement as set forth in General Order 2. And in action with the enemy, all Star Fleet Commanders and
Commanding Officers shall adhere to Star Fleet Regulation 4710.
DISCUSSION
General Order 8 prescribes the actions that must be taken if it is suspected, or that indeed an invasion of
Federation space has taken place. This General Order was issued as a result of an incursion into Federation
space in 2258 by the Klingon Empire.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders, Commanding Officers and to all Senior
Officers Present.
EXCEPTIONS
NONE

Stardate 18399.2
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER NINE: SHIP HANDLING
Commanding Officers of Star Fleet ships and craft are responsible for the safe navigation and handling of their
ship or craft in accordance with Star Fleet Regulation 4850. In time of war or conflict, competent authority may
modify the use of flashers, lights, signal beams or registry beams, or other safeguards required by law to
prevent collisions in space, near bases, and planets or other natural formations in space. However, all sensing
devices shall be operational and in good working condition at all times.
Professional standards and regulations governing ship handling, safe navigation, safe docking, and related
operational matters, shall be promulgated by the Director: Star Fleet Command and the Chief of Star Fleet
Operations.
All persons in the Star Fleet Service responsible for the operation of Star Fleet ships and craft shall diligently
observe the Interplanetary Rules for Preventing Collisions in Space and such other rules and regulations as
may be established by the Federation Council Transportation Administration or other competent authority for
regulating traffic and preventing collisions in space, in orbit, in an atmosphere or on a base, where such laws,
rules and regulations are applicable to Star Fleet ships and craft.
Any significant infraction of the laws, rules and regulations governing traffic or rules designed to prevent
collisions in space, in orbit, in an atmosphere or on or near a base, observed by persons in the Star Fleet
Service, shall be promptly reported. Commanding Officers receiving such reports shall immediately inform Star
Fleet Command, including the Director: Star Fleet Command and the Chief of Star Fleet Operations.
DISCUSSION
General Order 9 was designed to impress upon persons commanding or operating Star Fleet ships and craft
the need handle their vessels responsibly, and to adhere to the rules of navigation and ship handling. This
General Order also applies to civilian vessels as well. Any infraction of the rules and regulations governing the
safe operation and navigation of Federation space vessels by civilian operators shall be handled by Star Fleet.
APPLICABILITY
This General Order is applicable to all Commanding Officers and officers in command of Star Fleet ships and
craft.
EXCEPTIONS
NONE

Stardate 18402.8
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TEN: COMMAND QUARANTINE
Command Quarantine shall be defined as placing a command in a state of isolation from external contact for a
specified period of time or until the nature of the quarantine has been resolved. As such and pursuant to Star
Fleet Regulation 4920, a Star Fleet Commander must place his command in a state of quarantine should it be
determined that his command is infected with a virulent and communicable disease of unknown origin, or that
his command is contaminated with agents or materials of an unknown origin that will place the health and
safety of the general public at risk.
Should the Commanding Officer declare and place his command in a state of quarantine, the Commanding
Officer shall:
1. Communicate to Star Fleet Command immediately that he has placed his command in a state of
quarantine and to communicate all possible data concerning the nature and extent of the cause for the
quarantine.
2. Prevent any person within his command to leave or prevent any outside person from entering the
command.
3. Place such buoys or devices to signal any approaching vessel that the command is under quarantine.
The Commanding Officer shall issue and continue to issue a code 705 signal until the situation has been
relieved.
Should it become apparent that the cause for the quarantine cannot be controlled, or that the entire crew or
staff will imminently die, the Commanding Officer shall issue an order to destroy the command under the
provisions of General Order Six.
DISCUSSION
The purpose of this General Order is to establish the procedures required to isolate a command from the
dangers of disease or other agents that will adversely affect the health and safety of the general public.
Isolation of a command is required by law to prevent the spread of such agents and disease to an
unsuspecting public.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders, and Commanding Officers of Star Fleet ships
and bases.
EXCEPTIONS
NONE

Stardate 18402.8
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER ELEVEN: SPACE EXPLORATION
All Star Fleet ships engaging in the normal course of their patrol duties shall, if conditions permit, explore, map,
and otherwise survey the areas of space they are currently patrolling. In addition to exploring space all Star
Fleet ships shall examine and study all natural or unusual phenomena in the region of space in which they are
conducting their patrol mission.
All Star Fleet ships engaging in the normal course of their patrol duties shall, if conditions permit, search for
and study any new life form or civilization that is encountered. When a new civilization is encountered, the
Commanding Officer of the Star Fleet vessel shall endeavor to contact such civilization or society with the
intention of bringing them into the United Federation of Planets, except where it may violate or cause to violate
General Order 1.
All Star Fleet ship Commanding Officers shall make a full report on the findings of such explorations or studies
to the Chief of Star Fleet Operations at their earliest opportunity.
DISCUSSION
The purpose of this order is to execute the exploration function of the Star Fleet Service. According to the Star
Fleet Charter and the Articles of Federation, the exploration of space is a primary function of the Star Fleet,
and a fulfillment of its scientific mission. Therefore, it is a standing order that all Star Fleet ships will explore
space, map and chart space sectors, make galactic surveys, study all natural and unnatural phenomenon, and
to seek out new life and new civilizations.
APPLICABILITY
This General Order is applicable to all Star Fleet ship Commanding Officers or Star Fleet Commanders
embarked on Star Fleet ships.
EXCEPTIONS
None, except where General Order 1 may be violated. In such cases, General Order 1 takes precedence over
General Order 11.

Stardate 18402.8
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWELVE: ENCOUNTERS IN SPACE
All Star Fleet officers commanding or in command of any Star Fleet vessel, craft, base or station shall
challenge any and all vessels they encounter in space or that approach a Star Fleet base or station. A
challenge shall be construed to mean any request for ship identification, course, destination, or mission and
intent.
All Star Fleet Commanders, Commanding Officers and Officers in Command shall take all necessary
precautions when approaching vessels in space or when vessels approach a base or station. Star Fleet
Commanders shall endeavor to identify any vessel they may encounter or that may approach their command,
and to take appropriate action should any vessel refuse to make its identity known.
Pursuant to General Order 9, all Star Fleet ship Commanding Officers shall endeavor to make their presence
known, and to ensure the proper identification of their vessel and their reason for challenging when
encountering vessels in space.
Pursuant to Federation law or treaty, and in accordance with Star Fleet Regulations, all Star Fleet
Commanders, Commanding Officers or Officers in Command shall render such honors to vessels encountered
in space that are appropriately accorded to them.
DISCUSSION
General Order 12 is an extension to Star Fleet Regulations 4680 and 6550 which require that all Star Fleet
ship Commanding Officers and Officers in Command will, to the maximum extent possible, protect their
command from attack or any action which may endanger the command or its crew, and to take such measures
as necessary to minimize the possibility of an undetected approach of hostile forces.
In addition to the security of the command, General Order 12 also requires that Star Fleet commands be
properly identified to all vessels encountered in space. This part of the order is a reference to General Order
9, which requires the safe handling and navigation of Star Fleet vessels. However, this aspect of General
Order 12 can be waived for Star Fleet vessels under special operational assignments in order to keep their
identity unknown.
DEFINITIONS
Term Definition
Friendly Vessels Vessels identified as belonging to the Federation or to a "Friendly Power". Note
that “Friendly” vessels may be considered “Unfriendly” if proper communications
cannot be established with the vessel.
Neutral Vessels Vessels identified as belonging to a "Neutral Power" and thus, shall be
considered as friendly, unless determined otherwise.
Unfriendly Vessels Vessels identified as belonging to an "Unfriendly Power". All possible security
measures shall be taken when such vessels are encountered.
Unknown Vessels All other vessels or vessels which have not yet been properly identified.
- PAGE 1 OF 2 -

VOLUME II
STAR FLEET GENERAL ORDER TWELVE - CONTINUED
RULES FOR ENCOUNTERS
The most dangerous period of an encounter between two vessels is the period of time between first sensor
contact and identification of the unknown vessel. Therefore, all Commanding Officers or Officers in Command
of Star Fleet vessels shall exercise the following Rules for Encounters in space:
Situation Action
Encountering Friendly Vessels: When it has been determined that a vessel is "Friendly", the
determination must be confirmed with a visual sighting. The vessel
shall then be challenged for destination and mission. When the
challenge is complete the Commanding Officer shall then render any
honors accorded to such vessel in accordance with the articles in Star
Fleet Regulation 7000.
Encountering Neutral Vessels: The action is the same as above, except when such vessel refuses the
challenge. In such cases, the vessel shall be considered "Unfriendly".
When the challenge is complete the Commanding Officer shall only
render honors in accordance with the articles prescribed in Star Fleet
Regulation 7000 when the vessel belongs to a government recognized
by the Federation.
Encountering Unfriendly Vessels: All possible security measures shall be taken. The command shall be
placed on General Quarters and a defensive posture taken. All
possible measures shall be taken to identify the intent of "Unfriendly"
vessels. When the challenge is complete the Commanding Officer
shall not render any honors in accordance with Star Fleet Regulation
7120.
Encountering Unknown Vessels: All possible measures shall be taken to identify the vessel and to have
its intentions known and understood. On encountering "Unknown
Vessels", the command shall be placed on an appropriate level of
security, balancing command safety with non-hostile intent. When the
challenge is complete the Commanding Officer shall not render any
honors in accordance with Star Fleet Regulation 7120. Should the
encounter occur outside of Federation space, the Star Fleet
commander shall make all efforts to establish friendly contact under
General Order 11.
APPLICABILITY
This General Order is applicable to all personnel commanding or piloting Star Fleet craft, shuttlecraft or
barges, as well as to officers commanding or in command of Star Fleet ships, bases or stations.
EXCEPTIONS
NONE

Stardate 18402.8
- PAGE 2 OF 2 -

VOLUME II

STAR FLEET GENERAL ORDER THIRTEEN: VESSELS IN DISTRESS
In accordance with Star Fleet Regulation 6630 all Star Fleet Commanding Officers, Officers in Command or
the Senior Officer Present shall render assistance to persons and/or vessels found to be in distress in deep
space. All Star Fleet Commanding Officers shall continuously monitor all emergency communications channels
in accordance with FLTCOMMREG 10B for possible distress calls and if such call is received, to immediately
respond to such calls and proceed with all speed to the location of the vessel, or individual, or individuals in
distress.
When such distress calls are received by a Star Fleet base or station, the Commanding Officer of such base or
station shall dispatch the nearest available ship or craft to the location of distress.
Should medical assistance be required to persons found in distress, Star Fleet Commanding Officers are
authorized to lend such assistance as stipulated in Star Fleet Regulation 6620.
Should the vessel or facility found to be in distress require maintenance or repairs, Star Fleet Commanding
Officers are not authorized to lend such repair assistance as stipulated in Star Fleet Regulation 6640.
However, Commanding Officers of Star Fleet ships or craft are authorized to tow such vessel in distress to the
nearest ship repair facility, provided the vessel can be moved by the ship or craft. Commanding Officers of Star
Fleet ships and craft are also authorized to request such assistance from any private or commercial enterprise
specializing in such towing or repair operations, in behalf of the owners of the vessel in distress, when the
damaged vessel’s communications system is not functioning. However, Star Fleet or any of its members or
agencies is not authorized to recompense such enterprises for work performed on vessels in distress.
DISCUSSION
General Order 13 is considered as one of the humanitarian orders. It is the duty and responsibility of all
members of the Star Fleet Service to help persons found to be in distress anywhere in space – whether within
or outside Federation territory. A person is considered to be in distress when that person is lost in space, their
vessel disabled, marooned, or injured.
APPLICABILITY
This General Order is applicable to all persons in the Star Fleet Service.
EXCEPTIONS
NONE

Stardate 18402.8
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER FOURTEEN: NEUTRAL AND BUFFER ZONES
All Star Fleet Commanders, Commanding Officers or Officers in Command shall respect the integrity of any
and all Neutral or Buffer Zones established by the United Federation of Planets, and shall strictly adhere to the
rules governing the entrance to or operations around such zones. Therefore, all Star Fleet Commanders,
Commanding Officers and Officers in Command shall endeavor to review any and all treaties or agreements
establishing any such Neutral or Buffer Zone they may encounter or that are within the vicinity of their patrol
area or base of operations.
All Star Fleet Commanders, Commanding Officers or Officers in Command shall prevent any unauthorized
person or vessel from entering into or exiting from any established Neutral or Buffer Zone, except as
authorized by the Federation Council. Star Fleet Commanders are authorized to use such force as necessary
to prevent the violation of any restricted zone pursuant to the Rules of Engagement established in General
Order 2.
No Star Fleet Commander, Commanding Officer or Officer in Command has the authority to cross into any
Neutral Zone for the purpose of apprehending any fugitive or to perform any punitive action against a
belligerent that had violated the terms of the zone. Any violation of an established Neutral Zone shall be
immediately reported to Star Fleet Command and to the appropriate Federation authorities for action. Only the
Federation Council may authorize the entrance into a Neutral Zone.
Should a Star Fleet Commanding Officer enter a Neutral, Buffer or any other restricted area the Commanding
Officer shall report the reasons for his actions to Star Fleet Command as soon as practical in accordance with
Star Fleet Regulation 4910.
DISCUSSION
The function of Buffer and Neutral Zones is to restrict access to and from a volume of space for the purpose of
isolation or separation. Such zones are legal boundaries, the violation of which may have serious political,
military, economic or other consequences that may affect the peace and security of the Federation.
The function of General Order 14 is to reiterate the importance of maintaining and adhering to the rules
regarding Buffer and Neutral Zones. This General Order was issued as a result of an incident between a
Starship and a Romulan vessel that had crossed the Neutral Zone and attacked a Federation outpost.
APPLICABILITY
This General Order is applicable to all persons in the Star Fleet Service and to all citizens of the United
EXCEPTIONS
NONE

Stardate 21323.6
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER FIFTEEN: FLAG COMMANDERS EMBARKED
Pursuant to Star Fleet Regulation 5551 all Star Fleet Commanding Officers shall be subject to the orders of a
flag commander when such flag officer is embarked on or attached to their command, except where such flag
officer is merely embarked as a passenger or when such order, issued by the flag officer, conflicts with current
orders of a higher authority than that of the flag commander. In refusing a conflicting order, the Commanding
Officer shall adhere to Star Fleet Regulation 5450 regarding conflicting orders.
While a flag commander is embarked on his command, the Commanding Officer shall render all honors and
courtesies afforded the flag officer, and shall provide the flag officer with quarters suitable to his rank as well
as to provide quarters for the flag officer’s staff. However, members of a staff attached to a flag commander
and embarked on a command shall be placed on duty by the Commanding Officer of the command in
accordance with Star Fleet Regulation 3910.
While a flag commander is embarked on his command, the Commanding Officer shall ensure the safety and
well-being of the flag officer and his staff in accordance with Star Fleet Regulation 4670. The Commanding
Officer shall not allow such flag commanders to be placed in a position where their personal safety may be at
risk. The Commanding Officer, in accordance with Star Fleet Regulation 4670, shall provide such armed
escorts as needed to protect the flag officer when such flag officer is away from, but attached to, the
command.
DISCUSSION
General Order 15 reiterates the relationship between a Commanding Officer and a flag officer that is embarked
afloat. This General Order is particularly addressed to Star Fleet ship Commanding Officers; that although the
authority of a Star Fleet ship Commanding Officer is absolute, a Commanding Officer still comes under
authority of a senior officer. However, a flag officer that is merely embarked as a passenger on a Star Fleet
vessel, while such vessel is under orders, shall not countermand such orders or divert the ship from its
intended mission unless the flag officer is directly related to the mission.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanding Officers and Flag Officers.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER SIXTEEN: SEARCH AND SEIZURE
All Star Fleet Commanders, Commanding Officers and Officers in Command in their lawful duty to stop and
search private or commercial vessels, under General Order 5, shall seize the vessel and all of its contents
should it be found that such vessel contains contraband or other illegal items or persons as established by
Federation law, regulation or treaty. When such contraband has been found, the vessel and all its contents
shall be impounded and taken to the nearest Star Fleet command base at the earliest opportunity.
All Star Fleet Commanders, Commanding Officers or Officers in Command receiving impounded property shall
safeguard the vessel and its contents until the disposition of the vessel, or its contents, or both can be
determined.
All crew members or persons in command or operating the vessel where contraband or illegal items were
discovered shall be detained and an investigation into the matter initiated as soon as possible. Should the
investigation reveal the circumstances and intent was to commit a Federation offense in these matters, the
Commander, Commanding Officer or Officer in Command may take such action as appropriate under Star
Fleet Regulation 4330 including confinement, restraint or surveillance and the individuals delivered to the
appropriate authority.
Should confinement or restraint be ordered, the Commander, Commanding Officer or Officer in Command
shall ensure the safety and well-being of those imprisoned in accordance with Star Fleet Regulations 8880,
8890 and 8910 until such prisoners can be transferred to the nearest Star Fleet facility for permanent
imprisonment or trial.
DISCUSSION
The Star Fleet Charter gives Star Fleet full law enforcement powers and the authority to prevent contraband
items from entering or leaving Federation space. As such, General Order 5 was issued to allow the inspection
of private and commercial vessels for contraband or illegal items. This General Order clarifies the duties of
Star Fleet personnel when such contraband or illegal items were found during such an inspection.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders, Commanding Officers and Officers in
Command of Star Fleet ships and bases.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER SEVENTEEN: FEDERATION LAW ENFORCEMENT
All Star Fleet Commanders, Commanding Officers and Officers in Command are hereby granted full law
enforcement authority as stipulated in ARTICLES 2, 3, 4 and 27 of the Star Fleet Charter, and shall enforce all
laws and regulations of the United Federation of Planets.
All Star Fleet Commanders, Commanding Officers and Officers in Command shall establish a relationship with
local law enforcement agencies, and shall cooperate with such agencies to the fullest extent possible or as
conditions permit. However, Commanders are not required to provide support to law enforcement agencies
that are not part of the United Federation of Planets, but shall use prudence when dealing with such agencies.
All Star Fleet Commanders, Commanding Officers and Officers in Command shall have the authority to stop
and inspect any vessel encountered in open space and shall have the authority to seize and impound such
assets without warrant as the law permits. Star Fleet Commanders shall also have the authority to detain,
restrain or otherwise incarcerate any person found under incriminating circumstances as stipulated in Star
All Star Fleet Commanders, Commanding Officers and Officers in Command in the performance of their law
enforcement duty shall execute any warrant issued by competent Federation authority.
DISCUSSION
General Order 17 was formally issued to grant Star Fleet full law enforcement authority and to direct Star Fleet
Commanders and Commanding Officers to exercise this authority without reservation.
APPLICABILITY
Command, except where it might conflict or violate General Orders 1, 3 or 14.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER EIGHTTEEN: MILITARY CONDUCT AND LEADERSHIP
Every command in the Operating Forces and the Shore Establishment, as well as every office or bureau of the
Department of the Star Fleet shall review, on a continuing basis, its standards of personal leadership to ensure
that those in responsible positions are discharging their duties in accordance with Star Fleet Regulations 8120
and 8130.
Every command in the Operating Forces and the Shore Establishment shall integrate into their training
programs, on a continuing basis, both the technical and moral principles and practices of leadership.
The Star Fleet Inspector General shall regularly report to the appropriate Commanders evidence of leadership
that is both markedly superior to accepted standards, and decidedly inferior. Commanders receiving such
favorable reports shall make appropriate notations on the record of the officer or officers responsible. In the
event that unfavorable reports are received, corrective action shall be initiated and completed.
The Chief of Star Fleet Personnel shall issue directives to carry out the intent and to achieve the objectives of
this General Order. Such directives shall be specific and forceful to ensure that leadership standards and
training are a matter of continuing concern and importance to every person in authority within the Star Fleet
Service.
DISCUSSION
The objective of General Order 18 is to reemphasize and revitalize Star Fleet leadership in all its aspects:
inspirational, technical, and moral. The Star Fleet profession is an honorable one, which has traditionally
commanded the respect of the entire Federation. The Star Fleet Service has long been distinguished for the
high quality of its officers and technicians. The challenge is to continuously improve Star Fleet leadership. By
Star Fleet leadership is meant the art of accomplishing the missions assigned to it by its personnel. Effective
leadership, therefore, is based on personal example, good management practices, and moral responsibility.
APPLICABILITY
This General Order is applicable to all persons in authority within the Star Fleet Service.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER NINETEEN: FEDERATION COLONIES
In accordance with Star Fleet Regulation 6570 all Star Fleet Commanding Officers or Officers in Command of
Star Fleet ships shall protect all colonies and settlements within their area of operation, regardless whether the
colony or settlement is located outside the boundary of the United Federation of Planets.
All Star Fleet Commanding Officers or Officers in Command of Star Fleet ships shall, as part of their normal
patrol duties, periodically make calls on colonies and settlements to inspect the outpost for health, safety and
sanitation; to examine the outpost for illegal activity, to enforce Federation laws and to ensure the legal
operation of the colony or settlement; and to monitor the progress and security of these outposts and if
necessary, to deliver such supplies as needed to sustain the colony or settlement until relief supplies are
forthcoming. However, Star Fleet Commanders, Commanding Officer and Officers in Command are in no way
obligated to supply such colonies and settlements with non-essential goods.
In addition, a medical examination by a certified Star Fleet Medical Officer shall be performed on all persons
within a colony or settlement under the purview of the Commanding Officer at least once each year. The Star
Fleet ship Commanding Officer shall schedule and arrange such medical examinations within the normal patrol
period, and shall support the Medical Officer in any way in the performance of this duty.
DISCUSSION
As specified in ARTICLE 9 of the Star Fleet Charter, Star Fleet is the primary agency for the logistical support
of all Federation colonies, outposts and expeditions. General Order 19 reiterates the roles and responsibilities
of Star Fleet Commanders to protect and support Federation colonies, settlements and expeditions. General
Orders 4 and 5 outline the responsibility to protect, defend and support Federation colonies in their lawful
occupations. However, General Order 19 establishes the rules governing the support and authority of Star
Fleet over commercial and private colonies.
APPLICABILITY
This General Order is applicable to all persons in the Star Fleet Service and to all owners of properly
registered Federation private and commercial colonies and settlements, and is applicable to all colonies and
settlements whether within or outside the boundaries of the United Federation of Planets.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY: FLEET DEPLOYMENT
In accordance with ARTICLE 69 of the Star Fleet Charter, Star Fleet forces shall be deployed to strategic
locations throughout and at the boundaries of Federation space. As such, it is the responsibility of all Star Fleet
Commanders in Chief, Commanders of Fleets and other Commanders of substantial vessel assemblages to
deploy their forces in locations that would afford them a strategic and tactical advantage over hostile forces.
In addition and in accordance with Star Fleet Regulation 3300, all Star Fleet Commanders or Officers in
Command of Star Fleet forces shall organize their force where they can best protect and defend the territories
of the United Federation of Planets. As such, Star Fleet Commanders shall:
1. Deploy their forces near and around established Neutral Zones separating the Federation from hostile
powers;
2. Deploy their forces such that they will have ready access to support and other shore facilities for the
purpose of repair, replenishment and administration;
3. Establish Patrol Areas and Patrol Zones in which their forces will operate to protect and defend the
interests of the Federation, and to enforce the laws of the United Federation of Planets;
DISCUSSION
The purpose of this General Order is to direct all Operational Commanders of Star Fleet forces to organize and
deploy their forces where they can best protect and defend the interests of the United Federation of Planets as
specified in ARTICLE 69 of the Star Fleet Charter. Star Fleet Commanders forces are directed to deploy their
forces at strategic locations throughout and at the boundaries of Federation space.
APPLICABILITY
This General Order is applicable to all Fleet Commanders, Commanders in Chief and other Operational
Commanders of large vessel groupings.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY ONE: TREATIES AND AGREEMENTS
Under no circumstance shall any Star Fleet Commander, Commanding Officer or other senior officer, except
as authorized by Star Fleet Command, prepare, make or present any treaty, agreement, pact or other bond to
any social system or government, foreign or domestic, without a Federation Consul or a designated Star Fleet
Representative, authorized to do so, present in accordance with Star Fleet Regulation 6860.
In addition, no Star Fleet Commander, Commanding Officer or any Star Fleet person shall sign, ratify, approve,
sanction or endorse any treaty or agreement that may be presented to them by any government, foreign or
domestic, or by anyone acting on behalf of any government or entity without a Federation Consul or a
designated Star Fleet Representative, authorized to do so, present.
Star Fleet Commanders, Commanding Officers and the Senior Officer Present are only authorized to act as a
witness to any agreement or treaty and only when a Federation Consul or a designated Star Fleet
Representative is present. However, the Senior Officer Present may make recommendations or clarify specific
aspects of Federation law while such an agreement or treaty is being drafted. Star Fleet Commanders,
Commanding Officers and the Senior Officer Present may also invite disputing parties for the pacific settlement
of a dispute on neutral Star Fleet property for the purpose of mediation or to produce such an agreement,
settlement or treaty.
Star Fleet Commanders shall, when a Federation diplomat is present, honor all reasonable requests made by
such consul or appropriate Federation official while in the exercise of their lawful duties relating to the
diplomatic mission at hand, as long as such requests do not violate Federation law, Star Fleet Regulations,
General Orders or interfere in the normal functioning of the command to which the Federation official is
assigned.
DISCUSSION
The purpose of this General Order is to codify Star Fleet’s role during treaty negotiations as specified in
ARTICLE 32 of the Star Fleet Charter and Star Fleet Regulation 6860. The charter specifies that Star Fleet
does not have the authority to prepare, make or present any treaty or agreement with any social system
without a proper Federation Consul present. The power to make agreements and treaties rests solely with the
Federation Council. Star Fleet may only act as a witness to any agreement or treaty drafted between the
parties for the pacific settlement of a dispute while on neutral Star Fleet property.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders, Commanding Officers and other senior officers
that have dealings with governments, whether inside or outside the United Federation of Planets.
EXCEPTIONS
NONE

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY TWO: ENCOUNTERING HOSTILE FORCES
All Star Fleet Commanders, Commanding Officers and Officers in Command of Star Fleet ships shall place
their command in a state of full readiness for action in accordance with Star Fleet Regulations 4670 and 4680
and General Order 6 whenever known hostile forces are encountered. As such, this General Order establishes
the following Rules of Engagement when encountering known hostile forces:
a. Commanding Officers shall place their vessel in a defensive posture and shall not take any provocative
action. Commanding Officers shall establish communications with the commander of the hostile force as
soon as possible in order to ascertain the intent of the hostile force as required under General Order 12;
b. Commanding Officers shall prepare their vessel for action if it becomes necessary. However, the
Commanding Officer should refrain from immediately raising defensive shields as it may be interpreted as
an aggressive act. Therefore, shields should be withheld if there is no clear and present danger to the
ship as evaluated by the Commanding Officer. However, once shields are up the Commanding Officer
must expect to take fire;
c. Should force be necessary, the Rules of Engagement established in General Order 2 shall come into
effect. As such, it is the policy of Star Fleet that Commanding Officers, when defending their command,
rapidly destroy the enemy’s capability to inflict damage;
d. Should a hostile force show a willingness to break off the attack, the Commanding Officer of the Star
Fleet vessel shall allow it to do so, but shall retain a full defensive posture in accordance with Star Fleet
Regulation 4680;
e. Star Fleet Commanding Officers shall demand the immediate removal of the threat to security, either by
the removal of the hostile force from the area or the immediate surrender of the force. ANY SHIP THAT
PERFORMS AN ACT OF WAR ON THE FEDERATION CANNOT BE ALLOWED TO LEAVE AND
MUST EITHER BE FORCED TO SURRENDER OR BE DISABLED FROM BEING A THREAT.
DISCUSSION
This General Order sets the Rules of Engagement that Star Fleet Commanders must adhere to when
encountering forces of known hostile governments. This General Order is an extension of General Order 12,
but specifically geared towards hostile encounters.
APPLICABILITY
Command of Star Fleet vessels.
EXCEPTIONS
There are no existing exceptions to this General Order except where it may be in conflict with General Order 2.

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY THREE: ENGAGING HOSTILE FORCES
Should the use of force be necessary in the engagement of hostile forces, Star Fleet Commanders, Star Fleet
Commanding Officers, Officers in Command or Senior Officers Present shall engage the enemy to the utmost
of their ability, and pursuant to Star Fleet Regulation 4710 shall:
a. Before going into action communicate to his officers, if possible, his plans for battle or action and such
other information as may be of operational value should any of them succeed to command;
b. During action, station the Deputy Commander, Executive Officer or the officer designated to succeed him
where he can best aid the commander, and if practicable, where he could probably escape the effects of
a casualty disabling the commander, and yet would be able to assume command promptly and efficiently;
c. During action, the Commanding Officer shall not, without permission, break off action to assist a disabled
ship or take possession of a captured one;
d. During action, the Commanding Officer shall destroy the enemy’s ability to inflict damage by targeting
weapons and propulsion units, but shall, to the extent possible, minimize the loss of life to the enemy;
e. Immediately after the battle or action, the Commanding Officer shall repair damage so far as possible,
exert every effort to prepare the command for further service, and make accurate, explicit, and detailed
reports as required;
f. At an appropriate time after a battle or action, and after repairs have reasonably been completed, the
Commanding Officer may assist a disabled ship or take possession of a captured one.
g. Prisoners taken as a result of action shall be placed in secure detention facilities and the Commanding
Officer shall follow the directives set forth in Star Fleet Regulation 8890.
DISCUSSION
This General Order is essentially the second part of General Order 22 and deals solely with the engagement of
hostile forces. However, this General Order also applies during law enforcement operations as well.
APPLICABILITY
This General Order is applicable to all Star Fleet Commanders and Commanding Officers of Star Fleet ships,
craft, bases and command units.
EXCEPTIONS
There are no existing exceptions to this General Order except where it may be in conflict with General Order 2.

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY FOUR:

AUTOMATED PLANETARY DESTRUCTION
At the direction of the Commanding Officer or the Officer in Command, the planet or selected targets of the
planet specified shall be destroyed automatically after the specified time period has elapsed. Orders and
directions shall be fed into the ship’s computer system directing the system to fire upon the selected targets
when the specified time period has elapsed. This order shall remain in effect until the target or targets have
been destroyed, or until the order has been countermanded by the issuing officer.
The use of General Order 24 is a serious matter and must only be used under the most serious of conditions
and used with extreme prejudice. As such, the misuse of General Order 24 constitutes a direct violation of Star
Fleet Regulation 6520 and therefore, is subject to courts-martial. The Commanding Officer invoking General
Order 24 must submit a full report, in writing, outlining the details requiring the use of this General Order, and
must present himself to a Board of Inquiry at his earliest possible opportunity.
DISCUSSION
The basic purpose of this order is to project Federation power on a belligerent world. Should the situation
require such action, the Commanding Officer may issue General Order 24 when the safety of his ship or
persons under his command is in danger. General Order 24 may also be used in hostage situations where a
belligerent world has taken Star Fleet personnel or Federation citizens for the purpose of extortion.
When issued, major population centers, military facilities, selected targets, or the entire surface of a planet will
be entered into the ship's weapons fire control system and a countdown initiated. After the specified delay time
has elapsed, the fire control computer will automatically begin firing upon the targets programmed, and will
continue until all the selected targets have been destroyed or the order countermanded by the issuing officer -
typically, the Commanding Officer. However, Commanding Officers should never use General Order 24 as a
means of diplomacy or when diplomacy may relieve the Commanding Officer of the situation. As such, the use
of General Order 24 is very serious and its misuse is a court-martial offense.
APPLICABILITY
This General Order is applicable to Starship Commanding Officers or Star Fleet Commanders embarked on
line Starships.
EXCEPTIONS
There are no existing exceptions for the use of this General Order except where its use may be in conflict with
or in violation of any other General Order. In such cases, all other General Orders have precedence over
General Order 24.

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY FIVE: FIRST CONTACT
It is a Standing Order that all Commanders and Commanding Officers of Star Fleet vessels seek out new
civilizations, and to extend the arm of friendship to all newly discovered systems in order that they may
become part of the United Federation of Planets.
When first contact is to occur, the Senior Officer Present shall assemble such appropriate Contact Teams as
necessary for the purpose of: a) evaluating the level of technological development, b) performing a general
survey of the planet and its peoples, c) make initial contact if within Federation guidelines, and d) make
recommendations regarding the feasibility of having the newly discovered world enter the United Federation of
Planets. Upon completion of the evaluation the Star Fleet Commander, Commanding Officer or Senior Officer
Present shall issue a report to Star Fleet Command on the results of such contact as soon as possible.
In all instances of first contact, Star Fleet Commanders, Commanding Officers and all Star Fleet personal shall
respect the customs, traditions and beliefs of the newly discovered civilization. All Star Fleet personnel in
dealings with newly contacted civilization shall show in themselves exemplary conduct to the newly discovered
peoples as required under Star Fleet Regulations 6540 and 8130.
When contacting new civilizations and cultures, Star Fleet Commanders and Commanding Officers shall
establish such relations with their governments as though they were a member of the United Federation of
Planets and in accordance with its laws. Star Fleet Regulation 8630 shall apply regarding any relationship with
newly discovered civilizations. However, Star Fleet Commanders engaged in first contact shall not, without
proper authority or a Federation Consul present, prepare, make, or present any treaty or agreement with the
newly discovered culture as required under General Order 21. In addition, it must be reiterated that newly
discovered civilizations and governments have no standing with the United Federation of Planets and as such,
no military honors shall be accorded under Star Fleet Regulation 7120.
DISCUSSION
The purpose of this General Order is to establish the guidelines to Star Fleet Commanders and senior officers
regarding the initial contact of newly discovered civilizations and peoples.
APPLICABILITY
This General Order is applicable to Starship Commanding Officers or Star Fleet Commanders embarked on
Star Fleet vessels.
EXCEPTIONS
There are no existing exceptions for this General Order except where its use may be in conflict with or in
violation of any other General Order. In such cases, all other General Orders shall have precedence over
General Order 25.

Stardate 21676.5
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY SIX: NEW SPACE IDENTIFICATION
All Star Fleet Commanders, Commanding Officers and Officers in Command of any Star Fleet vessel or unit
engaged in exploration missions or activities shall:
1. Ensure that the region of space being explored or that is under survey has no prior claim regarding
ownership or jurisdiction. Commanding Officers must make every effort to determine that the region of
space under survey is free from any claim or part of any known or unknown jurisdiction.
2. Should it be determined that a claim is made by an unknown jurisdiction, the Commanding Officer of the
Star Fleet unit shall immediately contact Star Fleet Command and to request council. The Star Fleet
Commander shall request from the claimant any proof as necessary to substantiate the claim.
3. Should it be determined that a claim is made by a known jurisdiction, the Commanding Officer of the Star
Fleet unit shall immediately contact Star Fleet Command; at which time the Star Fleet Commanding
Officer shall withdraw from the area. The Federation Council will then be placed in charge of determining
the validity of the claim.
4. Should it be determined that no claim to the area exists, the Commanding Officer shall place such
signaling devices as required denoting that the area is Federation territory. In addition, the Star Fleet
Commander shall establish a research or survey post within the area indicating that the area is populated
by the Federation.
DISCUSSION
This General Order is issued as a result of an incident involving a Star Fleet garrison and a Starship within the
territorial boundaries of an unknown power that had legal claim to the area of space the garrison was located.
As a result of this incident the United Federation of Planets instituted new guidelines regarding the exploration
and colonization of unknown space known as the Gorn Rule.
APPLICABILITY
This General Order is applicable to all Commanding Officers of Starships, exploration vessels or any Star Fleet
vessel assigned to or engaged in exploration activities. In addition, this General Order is also applicable to Star
Fleet Commanders embarked on vessels assigned to or engaged in exploration and survey activities as well.
EXCEPTIONS
NONE

Stardate 23704.96
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY SEVEN:

DRUG AND CONTRABAND INTERDICTION
All Star Fleet Commanders, Commanding Officers and Officers in Command shall enforce the laws and
regulations regarding the possession and transport of illegal drugs, substances, materials and other
contraband as required under Star Fleet Regulation 3600.
All Commanding Officers of Star Fleet ships shall inspect private and commercial vessels for such contraband
items while in the performance of their inspection duties under General Order 17. If such contraband is found
during such an inspection Commanding Officers shall exercise their authority or discretion regarding the
confiscation of such material, the arrest of such individuals and the impounding of the suspect vessel.
All Commanding Officers of Star Fleet vessels receiving information regarding the transport of illegal
substances or contraband, the Commanding Officer shall locate and pursue the suspect vessel, stop and
board such vessel, and take such appropriate action as necessary within the confines of their authority.
However, Commanding Officers of Star Fleet vessels shall not pursue such vessels found to contain drug or
contraband into sovereign territory as stipulated in General Order 3. Star Fleet Commanding Officers shall
notify the local authorities that the vessel in pursuit has entered their space and shall request assistance from
the local authority to engage or restrain the vessel and its crew, or seek permission to enter their territory for
the purpose of apprehending the individuals involved.
The Office of the Judge Advocate General shall issue a list of all contraband items and substances and
transmit such a list to the Commanders of all Star Fleet bases, stations and ships.
All Star Fleet personnel are responsible to report any crime or violation of Federation drug and contraband
laws to the proper Star Fleet or Federation law enforcement agency as required under Star Fleet Regulation
8741.
DISCUSSION
The basic purpose of this order is to reiterate the law enforcement role of Star Fleet Commanders as it relates
to possession or transport of illegal drugs and contraband. Star Fleet Commanders are encouraged to use
their law enforcement authority in the interdiction of such illegal substances or materials.
APPLICABILITY
This General Order is applicable to Starship Commanding Officers or Officer in Command of line Starships.
EXCEPTIONS
NONE

Stardate 23704.96
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY EIGHT: GATHERING INTELLIGENCE
All Star Fleet ships engaging in the normal course of their patrol duties shall, if conditions permit, gather
intelligence or other such information of useful strategic value as can be obtained within the areas of space
they are currently patrolling. As such, all Star Fleet ship Commanding Officers, in the performance of their
support functions shall inquire from the various colonies and expeditions any information that could be useful
to the security of the Federation.
All Star Fleet ships engaging in the normal course of their patrol duties shall, if conditions permit, engage in
intelligence gathering when encountering any new civilization. When a new civilization is encountered, the
Commanding Officer of the Star Fleet vessel shall endeavor to evaluate the civilization or society for the
purpose of determining:
a. Their intention and feelings regarding the Federation;

b. Their military and threat capabilities;
c. Their relations and involvement with known hostile governments;
d. Other capabilities and technologies they may possess.
All Star Fleet ship Commanding Officers shall submit a report of such findings, information and intelligence
gathering activities to the Chief of Star Fleet Operations at their earliest opportunity.
DISCUSSION
The purpose of this order is to reiterate the intelligence function of Star Fleet Commanders. According to the
Star Fleet Charter, the intelligence gathering is a primary function of Star Fleet and as such, all Star Fleet
personnel are obligated to help in the gathering of intelligence as they are able to do for the peace and security
of the Federation.
APPLICABILITY
This General Order is applicable to Starship Commanding Officers or Officer in Command of line Starships.
EXCEPTIONS
NONE

Stardate 23704.96
- PAGE 1 OF 1 -

VOLUME II

STAR FLEET GENERAL ORDER TWENTY NINE: FEDERATION OFFICIALS ONBOARD
Pursuant to Star Fleet Regulation 5552 all Star Fleet Commanding Officers shall be subject to the orders of an
official of the Federation government when such official is embarked on the command for official business.
Federation government officials shall have operational authority over the command regarding the mission to
which the official and the Commanding Officer of the command is assigned, but only to the extent necessary to
fulfill the mission. As such, all Commanding Officers shall obey the lawful orders of Federation government
officials that are within the scope of the mission when such orders do not conflict with any other standing or
general order, or that will not endanger the health and safety of the command or the mission.
All Federation government officials embarked as passengers on board Star Fleet vessels shall have no
authority over the command as specified under Paragraph 2 of Star Fleet Regulation 5552 and are subject to
the authority of the Commanding Officer of the command as specified in Star Fleet Regulation 4410. All
Federation officials visiting commands are also subject to the authority of the Commanding Officer under Star
While a Federation government official is embarked or visiting his command, the Commanding Officer shall
render all honors and courtesies afforded the official as required under Chapter 7000 of Star Fleet
Regulations, and shall provide the official with quarters suitable to his position as well as to provide quarters
for the staff of such official.
While a Federation government official is embarked on his command, the Commanding Officer shall ensure
the safety and well-being of that official and his staff in accordance with Star Fleet Regulation 4670. The
Commanding Officer, in accordance with Star Fleet Regulation 4670, shall provide such armed escorts as
needed to protect the official when such official is away from the command.
DISCUSSION
This General Order reiterates the relationship between a Commanding Officer and a Federation government
official that is embarked. This General Order was issued as a result of several instances where a Star Fleet
Commanding Officer either ignored the orders of a competent government official while in the performance of
official business or did not show the proper courtesy afforded such official.
APPLICABILITY
This General Order is applicable to all Commanding Officers or Officers in Command.
EXCEPTIONS
NONE

Stardate 24140.62
- PAGE 1 OF 1 -

CONFIDENTIAL
RESTRICTED DATA
NOFORN
VOLUME II
6.0 STAR FLEET SHIP OPERATIONS

In this chapter the basic operations of Star Fleet ships will be examined. Operations, as it
is defined here, will essentially mean the missions to which Star Fleet ships are assigned
and the functions they perform. As specified in Paragraph 3 of ARTICLE 47 of the Articles
of Federation and ARTICLE 16 of the Star Fleet Charter, Star Fleet was given the
authority to construct and deploy ships so that it could meet the missions to which it was
chartered. As such, Star Fleet ships became the long arm of the Federation. Their basic
function is to protect the Federation and to project its power across space.
In general, all operations concerning Star Fleet ships and craft are the responsibility of
Star Ship Command. That is, Star Ship Command is the organization altogether
responsible for every aspect regarding the operation, performance and assignments of all
Star Fleet ships and craft. In essence, Star Ship Command is basically responsible for
the Operating Forces of Star Fleet. Chapter 6.0 is divided into six sections, the contents
of which will be described below.
Section 6.1 describes the functions that Star Fleet ships perform. These functions were
derived from the basic functions of the Department of the Star Fleet as specified in the
Articles of Federation and the Star Fleet Charter.
Section 6.2 outlines the various missions to which Star Fleet ships and craft are typically
assigned. In addition, this section will also describe how such missions are developed and
how the orders or assignments are issued.
Section 6.3 describes the various classes of ships and craft used by Star Fleet, as well as
their primary mission. However, class distinction and definition is solely controlled by the
Star Ship Systems Command (STARSHIPS), which will be covered in Volume V. This
section provides only a brief description of the various classes of ships that make up the
Star Fleet.
Section 6.4 describes how ships are organized into fleets and other functional units and
how such units are deployed. This section will also describe the operational functions of
each ship unit, their mission and how they are used.
Section 6.5 deals with ships and other assets that are no longer in active service and will
provide a brief description of the process of decommissioning and re-commissioning these
ships. The function of this section is to show how Star Fleet handles and maintains ship
assets that are no longer in active service.
Section 6.6 presents the current assignments of commissioned Star Fleet ships, which
includes the organization to which they are assigned and their current primary mission.
This section is classified CONFIDENTIAL because the missions to which some of the
individual ships are currently engaged in are classified.

VOLUME II

VOLUME II
6.1 STAR FLEET SHIP FUNCTIONS[1]

In general, the function of Star Fleet ships is the same as that of the Department of
the Star Fleet itself: 1) to defend the Federation, 2) to keep the peace, 3) to explore
new worlds, and 4) to bring in new worlds and civilizations into the United Federation of
Planets. In summary, Star Fleet ships accomplish the functions and missions of the
Federation as stipulated in the Articles of Federation.
The number one function of any Star Fleet ship is the control of Federation space. As
such, and in accordance with ARTICLE 53 of the Articles of Federation, Star Fleet
ships are built with firepower that is superior to any vessel within or known to exist outside
the Federation.
This section will deal primarily with those specific functions performed by Starships and
will not consider the standard activities of ships that support the fleet in the performance
of such functions such as those ships within the Star Fleet Transportation Command
manned and operated by civilian crews.
PROTECTING THE FEDERATION
As stated above, the number one function of any Star Fleet ship is to protect and defend
Federation space. As such, the authority of Star Fleet to defend Federation territory is
stipulated in ARTICLE 47 of the Articles of Federation and further enhanced in the Star
Fleet Charter. In addition, ARTICLE 53 of the Articles of Federation stipulates that
heavily armed "Starships" be constructed for the maintenance of peace and security. The
primary reason for this stipulation is because the local system forces cannot perform the
protection and the free flow of materials in deep space. Local systems do not have the
force size that can extend to the far reaches of the Federation and simultaneously
maintain a security force at home. A dedicated security force is needed to perform this
function. Therefore, the Federation Council, supremely charged with the preservation of
interplanetary peace and security, decided early on to have a single Star Fleet perform
the function of protecting the Federation, its people and all its property. As such, Star
Fleet maintains a large fleet of warships and other armed vessels to support its military
and law enforcement roles. This large fleet would operate at the fringes of Federation
territory to be the first line of defense against aggressive forces from outside the territory.
To accomplish this role Star Fleet ships are assigned patrol areas at the outer regions of
Federation space.
Protecting the Federation not only means protecting it from invading forces from without,
but also protecting it from within as well. Therefore, as part of its peace-keeping duties
under ARTICLE 9 of the Star Fleet Charter, Star Fleet has the additional duty to aid any
member system in special emergency situations. Such emergencies may include military
aid to suppress illegal rebellion or to supply humanitarian aid to any Federation system
that requests it. In these situations, a Star Fleet ship has the authority to supply the
affected planet with any security force or materiel necessary to mitigate the dangers the
planet or system is facing. As such, a Star Fleet ship Commanding Officer is authorized
to provide any of the ship’s property, equipment, medicines or facilities to the affected
system as he deems necessary.

VOLUME II
FEDERATION LAW ENFORCEMENT
In addition to protecting the Federation from invading forces, Star Fleet also has the
responsibility of enforcing Federation laws within its boundaries. As such, Star Fleet
ships will be used to monitor the space lanes for vessel compliance with Federation laws,
to ensure the safety of vessels within these space lanes, and to apprehend and detain all
criminals and fugitives from justice within Federation space. This includes fugitives from
foreign as well as from Federation authorities. However, Star Fleet has this authority
only within Federation space, and does not have any authority to pursue or apprehend
fugitives within local systems without permission from that system. This authority belongs
to the local system forces. In addition, Star Fleet does not have the authority to pursue
or apprehend fugitives outside of Federation space, except in places not recognized as
belonging to any social system or government.
In the enforcement of Federation laws, a Starship Commander has broad search and
seizure powers. With due cause, usually as a result of a routine ship scan, private as well
as commercial spacecraft can be stopped, boarded, and inspected by Starship security
personnel for proper documentation, content, safety equipment, and proper navigational
beacons. Starship Commanders are also authorized to issue citations for violations of
safety regulations or ship handling practices, and they are authorized to arrest any person,
or seize and impound any vessel found to have illegal drugs and substances and any other
contraband items[2].
Starships are also tasked with monitoring space traffic corridors as well. Non-military
vessels account for approximately 80% of the traffic within the Federation. As such, the
need for specific regulations, traffic corridors and space lanes are important in preventing
collisions in space. Therefore, Star Fleet is tasked with developing and implementing the
Rules of Space Navigation designed to prevent collisions in space, and the regulations
establishing basic ship handling standards and practices that must be observed by every
citizen of the Federation. As such, Starships will monitor the space lanes for compliance
with these regulations.
Also as part of its law enforcement role, Star Fleet also acts as the judicial arm of the
Federation in deep space. Federation courts do not extend to the outer boundaries of
Federation space and therefore, a Starship Commander is empowered with judicial
authority in the outlying territories. He has the authority to deliver judgment on minor
offenses within their patrol area and can exercise judicial authority for certain major
offenses when, because of circumstances, he is unable to transport the individual or
individuals involved to the nearest Star Fleet or Federation facility in a timely manner.
In such cases, the Starship Commander may, if he so chooses, convene a summary
court consisting of his senior officers and a member of the crew acting as counselor for the
defendant. But in most instances, the Starship Commander will simply investigate a
crime, interrogate suspects and hand them over to the nearest Star Fleet authority. This
power, however, does not extend to Commanding Officers of Star Fleet support ships,
but only to line Starship Commanders.

VOLUME II
SPACE EXPLORATION
As stipulated in ARTICLE 6 of the Star Fleet Charter, Star Fleet is the chief exploration
and colonization agency for the Federation. As such, Star Fleet ships will perform the
bulk of the exploration and survey activities within and outside the Federation.
In the early years Star Fleet ships were used mainly to survey and map the Federation
Treaty Zone. The main purpose for this activity was to determine and set the physical
boundaries of the inner zone of the Federation. The information obtained from these
surveys also aided Star Fleet in the development of military and non-military space travel
corridors. Space lanes and corridor maps were developed that provided the most efficient
travel routes with a minimum of navigational hazards. These early surveys were principally
performed to map and inventory the geophysical objects within Federation space. Later,
as the Treaty Zone was almost completely mapped, Star Fleet ships were embarked on
exploration and survey missions designed to expand the boundaries of Federation space,
primarily to expand Federation boundaries in order to establish buffer zones that would
widen the distance between potential enemies and the home worlds. Such Buffer Zones
allow Star Fleet time to organize and act on any invasion threat. When it is determined
that no threat exists, Star Fleet will then open the region to colonization.
As part of their exploration mission Star Fleet ships are also tasked with discovering new
sources of mineral and other important resources. This is performed through mineralogical
expeditions conducted by science research personnel stationed aboard Star Fleet ships.
These types of expeditions will only begin after the initial survey vessels have completed
exploring the subject region of space. Later, Star Fleet science teams will be posted to
selected planets in the region in order to survey them for mineral resources. Unlike other
scientific expeditions, mineralogical expeditions are of a very short duration, usually five to
six months. When their work is complete, the entire expedition is removed and reassigned
elsewhere.
In addition, exploring space also provides a unique opportunity to discover new worlds and
new civilizations. The strength of the Federation is greatly dependent on the number of
social systems under its banner. Therefore, it is imperative that Starship Commanders
seek-out new civilizations, and to extend the arm of friendship to every newly-discovered
system so that they may become part of the United Federation of Planets.
Private and commercial enterprises, as well as local system governments, may also engage
in exploration missions and establish private colonies. In these cases, Star Fleet will only
have law enforcement authority over these enterprises should they establish a colony or
enterprise outside the boundaries of their local system. In general, Star Fleet has no legal
authority over private colonies or expeditions that operate within a sovereign system. In
addition, Star Fleet will also have no authority over colonies that were established outside
the boundaries of the Federation. In such cases, these enterprises must assume the risk
of intruding into the territory of a foreign government and therefore, subject to their laws.
However, should trouble occur to private colonies or expeditions outside the Federation,
a Starship Commander will still be obliged to protect them, even though they may be
outside of Federation space. These people are citizens of the Federation and must still
be protected. However, Star Fleet is not obliged to protect the private property of any
colony or expedition that is located outside of Federation space.

VOLUME II
GALACTIC SURVEYING AND CHARTING
Establishing and maintaining Federation territory is described as physically setting the

boundaries of the Federation and to periodically check that the boundaries are correct.
As such, Star Fleet ships will survey Federation space in the outlying regions in order to
establish the boundaries and to reconcile these boundaries against the agreements and
treaties to which they were established[3]. When the surveys and measurements have been
completed marker buoys will be placed on location by the ship. These buoys will send both
visual and electronic signals indicating the boundaries of Federation space. Star Fleet
ships will periodically travel to the buoys and ensure that they are functioning properly and
that they are positioned at the correct location.
Along with maintaining Federation space, Star Fleet is the primary agency for exploring
new territory as specified in ARTICLE 21 of the Star Fleet Charter. As such, Starship
Commanders are authorized to expand the boundaries of Federation space by entering
and exploring new regions outside the Federation. This function will be an integral part
of the normal patrol duty of any Starship as stipulated in General Orders 11 and 26.
The process first begins with a Star Fleet ship surveying and mapping the newly explored
region of space. The vessel will then set up a small research station on a selected planet,
moon or asteroid within the new area. The function of the research team will vary with the
reason the installation was established. The reasons could range from engineering and
scientific studies in order to obtain critical information regarding any natural resources, to
performing military studies in order to determine the suitability of establishing a permanent
Star Fleet base, or to perform agricultural or other research as a prelude to colonization.
Regardless of the type of research undertaken, these survey teams will typically be staffed
by Starship scientific personnel. The team would remain on the planet and establish a
temporary base while the Starship would continue on its assigned mission. Such a survey
mission will usually be of short duration and when complete, the Starship will return to
retrieve the team members.
COLONIZATION
Colonization, as it applies to Star Fleet, is basically the establishment of military, scientific

or other outposts in the unknown regions of the galaxy, the basic purpose of which is to
pave the way for military, commercial or private colonization and development. Therefore,
the primary function of Star Fleet ships in this regard will be to:
1. Transport Star Fleet exploration and survey teams to selected planets,

2. Perform direct scientific surveys on newly discovered planets and spatial bodies, and
3. Establish temporary outposts.
Generally, Star Fleet's colonization function will be closely linked with its surveying and
charting function. However, Star Fleet ships may also be tasked with establishing a small
military base, scientific or engineering station upon a newly discovered world. This would
constitute a specific mission that would be outside the normal parameters of a Starship
patrol mission or beyond the requirements of General Order 11.

VOLUME II
SCIENTIFIC DISCOVERY AND INVESTIGATION
Star Fleet is the chief scientific and research agency for the Federation as stipulated in
ARTICLE 5 of the Star Fleet Charter. Typically, the kind of pure scientific research that
Star Fleet will normally be engaged will range from astrophysics to alien zoology. Such
research is vitally important to Star Fleet and has important strategic benefits as well. As
such, Starships will be engaged in many differing scientific projects during the normal
course of their patrol cycle as stipulated in General Order 11[4].
Besides studying physical phenomenon, a Star Fleet ship may also be engaged in large
agricultural projects as well. However, this is generally rare and would most likely be
performed by special Star Fleet Laboratory Ships or by some of the specialized farming
colonies established by the Star Fleet Division of Science. Starships could become
involved in such research by studying the effects to the plants and animals transplanted to
selected colonies. Their function would be to determine what can be grown and the crop
yields produced under varying soil, atmospheric, and climatic conditions. The knowledge
gained from these studies will be used to aid the many Federation colonies that exist
throughout the galaxy. Such knowledge could mean the difference between the success
and failure of an existing or planned colony.
In addition to pure scientific research Star Fleet ships may also engage in engineering
research and development as well. It is a basic function of Star Fleet to determine and
develop practical applications from any scientific knowledge obtained. Such applications
may include, but not limited to, a new and improved Warp-drive system, a new weapon
system, the improvement of materials used to construct space stations, or simply a new
food packaging system. As such, Star Fleet ships may be used to test new applications,
materials or components under actual operational conditions.
To fulfill their scientific role Star Fleet vessels, primarily line Starships, are equipped
with laboratories and other facilities in order to perform scientific research. When not
actively involved in military or other peacekeeping missions, a Starship on patrol will
always be engaged in some form of scientific research. Such research may include the
study of stellar and gravitational phenomenon, planetary or geological studies, life science
studies, and any other studies that would expand the knowledge base of the Federation,
or would be of some strategic benefit to Star Fleet.

VOLUME II
SUPPLY AND SUPPORT FUNCTIONS
As specified in ARTICLE 9 of the Star Fleet Charter, Star Fleet is the primary agency for
the basic support of Federation colonies, outposts and expeditions. Besides logistical
support, Star Fleet has the added responsibility of providing humanitarian or any other
assistance when disasters occur to any Federation system or undertaking.
Since Star Fleet initiated many of the colonies and expeditions, they are the sole property
of the Federation and thus, come under the protection of Star Fleet. It is the duty and
responsibility of Star Fleet ships to provide security and protection to such colonies and
expeditions. Therefore, Starships will be deployed to areas where such settlements and
expeditions are located with the primary responsibility for their protection and security. As
part of its normal patrol duties, a Starship will periodically visit and make official calls to
remote colonies and expeditions in order to ensure the safety and security of them, and to
provide essential law enforcement services. And as part of their law enforcement function,
Starship Commanders have the authority to inspect these outposts for compliance with
Federation regulations, and the enforcement of Federation law. In the enforcement of
Federation law, a Starship Commander has jurisdiction over all private and commercial
outposts and colonies that are in Federation space.
In addition to protection and basic security services, Star Fleet ships will also support
Federation government colonies and expeditions by providing them with needed food,
equipment and other supplies. Such support is usually in the form of prescheduled supply
calls to these colonies and expeditions by the Star Fleet Transportation Command.
However, line Starships may also be tasked with fulfilling certain supply requirements of
specific civilian colonies and expeditions as well. In addition to such supply calls, a Star
Fleet ship is required to call on civilian colonies and science expeditions for periodic health
certifications, and to report on the condition of such colonies and expeditions as required
by law, or the licensing agreements that established the enterprise. In general, however,
Star Fleet ships are not responsible for the logistical support of private or commercial
colonies or other such enterprises. This function is exclusively the responsibility of the
organization that established the colony or outpost.
Humanitarian aid is the responsibility of every member of the United Federation, but
especially for Star Fleet. When a planet or social system is struck with disaster, it is the
duty and responsibility of any Starship Commander to come to the aid of such planet or
system. Aid may be in the form of food, medical supplies and medical attention, or to
provide equipment and materials needed to mitigate or prevent a disaster from worsening,
or to provide transportation for evacuation, or to provide, to the extent possible, shelter.
In addition to humanitarian aid to planets and systems, Starship Commanders have the
duty and responsibility to assist persons, ships and craft that are in distress in open space
as required by Star Fleet Regulation 6630. Distress in space may be defined as serious
problems with a spaceship, spacecraft adrift in space, a collision with another spacecraft,
persons stranded on a planet or in space, or persons lost in space. In such cases, the
nearest Star Fleet vessel is required to proceed with all possible speed to the vessel or
persons in distress, rescue persons in distress and render any aid or assistance as needed.

VOLUME II
6.2 STAR FLEET SHIP MISSIONS

In general, ship missions refer to the assignments given to Star Fleet ships designed to
carry out the functions to which they were commissioned. In this section the standard or
basic types of missions assigned to Star Fleet ships will be discussed. Such missions will
generally be based upon the typical functions of Star Fleet ships as described in Section
6.1.
STANDARD OPERATIONS
Standard Operations are basically the routine activities performed by Star Fleet ships.
These are the missions outlined in the orders given to ship Commanding Officers upon
assumption of command. The specific operations performed by the ship, however, will be
based upon the functions described in Section 6.1. These functions will be translated into
specific missions or tasks to be carried-out by the ship and its crew, the responsibility of
which will rest with the ship’s Commanding Officer.
Standard Operations also refer to those specific functions involving ships in the various
Type Commands such as those in the Star Fleet Transportation Command, etc. For
example, operations such as high energy waste removal are a standard function of the
Transport Command, which is to deploy vessels to pick up and transport high energy
waste and dangerous goods. Such operations do not involve any special planning as in
other missions since they are scheduled tasks or events performed by the command, but
only the scheduling of the specific operation will be required, and such operations already
have the procedures in place to specifying the times and amounts required.
PATROL MISSIONS
The Patrol Mission is the standard assignment issued to Starships. They are orders
issued to the Commanding Officer at the start of a patrol cycle, which is usually five
years in duration[5]. The five-year mission is the standard Patrol Cycle of a line Starship.
This does not mean that the crews of these ships are totally out of contact with their
homes and families for five years, but that crews will be engaged in the mission duties for
around five years. This also means that a Starship Commander assigned to a Patrol
Mission will be in command of the ship for a minimum of five years. Starships embarked
on a five-year mission may also be periodically diverted to perform other duties, or may be
sent to their Home Ports for leave and liberty privileges during their Patrol Cycle.
The Patrol Mission will also involve various specific assignments or objectives that the
Starship must accomplish while on patrol. Some of these assignments are codified in
Star Fleet General Orders. Specifically, General Orders 4, 5, 11, 13, 17, 19, 25, 26
and 27 outline the required functions that Starship Commanders must perform in the
normal course of their patrol duties. These duty assignments will be delineated in the
Commanding Officer's patrol orders. Typically, Patrol Missions will be assigned to
Starship Commanders when they assume command of their ship. These are written
orders to the commander prior to his assumption. An example of just such an order will be
presented later in this section.

VOLUME II
EXPLORATION MISSIONS
An exploration mission is a specific assignment given to a Starship that is in addition to or

above those prescribed within the standard patrol assignment. Such special assignments
are beyond the normal exploration duties performed on patrol as required under General
Order 11. Typically, these assignments are issued by Star Fleet Operations when there
is a strategic need to explore, survey and map a specified volume of space, or where the
area in question is just outside the Patrol Area of the ship.
Exploration missions are also issued to special commands whose purpose it is to explore
and survey space and to establish expeditions and settlements. Such missions are specific
to the Star Fleet Space Exploration Command (XCOM) and will be assigned to the
Commanding Officers of the survey vessels (SV class) that are under the control of
XCOM. As such, they are the Standard Operations of such vessels.
SCIENTIFIC MISSIONS
A scientific mission is a specific assignment given to a Starship in addition to or above

those Standing Orders prescribed within the standard patrol assignment or General
Order 11. They are specific assignments to investigate a particular phenomenon, perform
a specific experiment, or obtain and analyze specific scientific data. Such assignments are
typically developed within the Star Fleet Division of Science in cooperation with Star
Fleet Operations.
FEDERATION SUPPORT MISSIONS
Federation support missions are those relating to the support of such things as civilian
colonies and expeditions, or rescue and recovery operations. For example, providing
support to a Federation colony with prescheduled supply runs. Although such missions
may be part of their normal patrol duties, a Starship may also be assigned other specific
missions of a support nature. Special missions may include the assistance of a Federation
member government in suppressing an illegal rebellion, or the evacuation of Federation
citizens from a disaster area, combat zone or other such humanitarian efforts. Therefore,
Star Fleet ships will, when necessary, be involved in humanitarian efforts providing aid to
Federation citizens in the form of food, medical supplies and medical attention, providing
equipment and materials needed to mitigate or prevent a disaster from worsening, or to
provide transportation for evacuees, or to make available, to the extent possible, shelter.
TRAINING MISSIONS
Training missions are those designed to exercise the crew under simulated conditions.
Such missions are used to evaluate the performance of the crew and the effectiveness of
procedures and battle plans. Training missions are generally outside the scope of the
commander’s patrol mission and usually of short duration.
Special war-games may be scheduled to test Starship Commanders and their crews
under various tactical situations. Usually, such war-games will involve several Starships,
one of which will be selected as the object of the exercise. The ship selected will act as the
adversarial element in the exercise.

VOLUME II
SPECIAL MISSIONS
Special missions are those ad hoc activities that are generally outside the normal scope of
the ship commander's patrol orders. Such missions include diplomatic or other non-military
mission, special intelligence missions, missions involving the implementation of Transitory
Security Arrangements, or the suppression of insurrection and rebellion upon legally
recognized governments of the Federation. An example of such a special mission may be
the transport of envoys and delegations to a peace conference. In general, such special
missions will almost always be initiated by the Federation Council or the Military Staff
Committee and given to Star Fleet ships for execution.
FLEET ROTATION
Although Star Fleet ships are generally assigned to a specific fleet, ships will periodically
be reassigned to other fleets by Star Fleet Operations as well. This is commonly known
as Fleet Rotation, which is basically the exchanging of one or more ships from one fleet
to another, or from one squadron to another. An equal exchange of similar ship types will
usually be performed in order to maintain the proper balance of vessels among the fleets.
Fleet Rotation may also be performed when a ship undergoes an overhaul or major refit.
This will generally be performed after a five-year patrol mission when a ship returns and
undergoes a refit, which will generally take up to two years to complete. During this period
the ship is taken out of service. When the refit is complete and the ship is ready for space,
another ship may be entering its refit cycle. The recently outfitted ship will replace the
incoming vessel if it is of the same class.
Star Fleet ships may also have their duty mission changed as well. This is referred to as
Operational Duty Rotation, which can be described as the periodic reassignment of the
mission of a ship from one function to another. For example, a ship on a five-year patrol
mission at the fringes of Federation space may be reassigned to pure exploration duty or
may be involved in diplomatic duty within the Federation Treaty Zone, or some special
operation elsewhere. As with Fleet Rotation, Operational Duty Rotation will always
be exercised by Star Fleet Operations.
Fleet Commanders will also periodically move their ship forces around as well. In this
scenario a Star Fleet ship may be reassigned or swapped between Fleet Squadrons.
However, in order to do so the Fleet Commander will require approval from Star Fleet
Operations primarily since the Star Fleet Ship Register will have to be updated to
reflect the new assignments. This approval is not required in times of war since Fleet
Commanders require the freedom to move their forces about to meet operational needs.
Battle Groups, on the other hand, will always be deployed on a rotational basis. That is,
a Battle Group will be assigned to a patrol a sector for a specified period of time, usually
around nine months, and then moved or assigned to a different sector, or relieved by
another Battle Group. Typically, Battle Groups are assigned to sectors near Neutral
Zones, close to potential trouble areas. However, at least one Battle Group will always
be assigned to Sector 001 for the purpose of protecting the home worlds and for other
diplomatic reasons. When not actively patrolling the sector, a Battle Group will typically
“anchor” near the Sector Starbase for an extended leave period.

VOLUME II
STAR SHIP COMMAND
The assignment and rotation of Star Fleet ships to missions and operations is the sole
responsibility of Star Ship Command - specifically, the Office of Star Fleet Ship
Operations (SSCOPS). The function of the Office of Star Fleet Ship Operations is to
manage the entire fleet in terms of their functions, operations and missions. This office
plans the missions assigned to it by higher authority, assigns such missions to fleets and
other operational units along with the Rules of Engagement that are to be applied
during such missions and lastly, will monitor and maintain the whereabouts of all ships
within the fleet.
Within SSCOPS is the Star Fleet Ship Assignment Section, which is solely responsible
for assigning Star Fleet ships and craft to Sectors, Fleets, Squadrons, Divisions and
other operating units and areas. This section is also responsible for naming and managing
the various Fleets, Flotillas, Groups and other operational units in space. It is the Star
Fleet Ship Assignment Section that issues the orders to Fleet Commanders relating
to the operations and missions to which they are assigned.
DEVELOPMENT OF ASSIGNMENTS
Star Ship Command is the primary organization responsible for the development and
assignment of missions to Starships. However, the mission goals and objectives will
usually originate from Star Fleet Operations. On the other hand, assignment of
personnel to Starships is performed by the Star Fleet Ship Personnel Assignment
Section of the Office of Star Fleet Ship Personnel, which manages all the aspects
regarding the assignment of personnel to ships. This section will work with the Star Fleet
Office of Personnel Assignment concerning the ships that will need manpower
replacements and to assign SSC personnel to ships based upon this need. However, it will
be BUPERS that will issue the orders to individuals for assignment to ship duty. An
example of such an order can be found at the end of this section[6].

VOLUME II
ASSIGNMENT TO MISSIONS
Missions are assigned to Star Fleet ships by Star Ship Command, the subdivision of
Star Fleet Operations that handles ship operations. And except in the case where a
Star Fleet ship Commanding Officer must respond to a situation on his own, all
missions and operations assigned to Star Fleet ships come from Star Ship Command.
Mission orders and profiles will generally come to the ship by subspace radio – either as a
secure verbal message or as a written coded message, and will be directed to the
Commanding Officer of the vessel. All mission orders and profiles will be transmitted to
the fleet by the Star Fleet Office of Fleet Communications as stated in Section 1.6 of
this volume.

VOLUME II
STAR FLEET BUREAU OF PERSONNEL

TO: James T. Kirk, Commander SSC, SC 937-0176 CE
FROM: Chief of Star Fleet Personnel
STARDATE: 20786.4
I. Pursuant to BUPERSMAN-341, you have been promoted to the rank of Captain, SSC and
assigned to command a Starship of the Line. As such, your identification number has been
upgraded to CEC, and all pay and benefits associated with this promotion are henceforth in
effect as of this Stardate.
II. Proceed WITHOUT DELAY to Starbase 11 for further instruction and to relieve the current
Commanding Officer, Christopher Pike, Captain SSC, and oversee the refitting of United
Space Ship ENTERPRISE, currently in Drydock.
III. You are therefore posted, effective immediately, to assume command of United Space Ship
ENTERPRISE, registry NCC-1701, a Cruiser Class Starship of 173,000 metric tons.
IV. The nature and duration of your mission will be as follows:
Perform standard galactic security, exploration and investigation for a minimum duration of 5
years.
V. You will be assigned to Fleet Squadron 33 operating in the third sector.
VI. Consistent with the limitations of your vessel and equipment, you will confine any landings
and contacts to Class “M” planets.
VII. You will conduct this patrol to accomplish primarily:
(a) Federation security, via explorations for intelligence and social systems capable of
galactic threat in accordance with General Order 4, and
(b) Scientific investigation to add to the body of knowledge of alien life forms, alien social
systems, space and stellar phenomenon in accordance with General Order 11, and
(c) Provide any required assistance to the various colonies in your patrol area, and the
enforcement of appropriate laws and statutes affecting such private or commercial
vessels and traders as you may contact in the course of your patrol as required under
General Orders 5, 17 and 19.
Chief of Star Fleet Personnel Director: Star Fleet Command

Star Fleet Division of Personnel STAR FLEET COMMAND
- PAGE 1 OF 1 -

VOLUME II
6.3 STAR FLEET SHIPS

The eight permanent fleets are composed of ships from virtually all of the available classes
of Star Fleet combatants and support vessels, each of which comprises an element of a
fleet. Each class of ship within a fleet has a specific function based upon the size, power,
speed and armament of the vessel or its role in supporting the fleet. In this section the
various classes of Star Fleet ships and how they are used will be discussed. Star Fleet
ships are classified by the mission or the function they perform. There are generally two
types of ships employed by the fleet: Combatants and Support ships, both of which can
be further divided into functional classes. However, regardless of the type of vessel, all
commissioned ships of the Star Fleet are called Starships.
THE STARSHIP CLASS
The term “Starship” was originally coined on 20th century Earth and later by Zefram
Cochrane of Alpha Centauri in 2113 during a conference on faster-than-light propulsion
systems. The term “Starship” was officially adopted in 2165 by the newly-formed United
Federation of Planets and codified in ARTICLE 53 of the Articles of Federation to be
used to identify the type of ships comprising the Star Fleet. As such, the Federation
made it a law that only Star Fleet ships shall bear this title and that no other vessel within
the United Federation of Planets shall be called a Starship.
LINE STARSHIPS
The term Line Starship, or “Starship of the Line[7]”, was derived from the Earth term
“ship of the line”. A ship-of-the-line was a type of wood-framed naval warship constructed
on Earth from the 17th century through the mid-19th century, the culmination of a naval
tactic known as the line-of-battle in which two columns of opposing first line warships
would maneuver to bring the greatest power of their broadside guns to bear. Since these
engagements were almost invariably won by the heaviest ships carrying the most powerful
guns, the natural state of progression was to build the largest, most powerful sailing ships
at the time, which in turn would lead to the title line-of-battle-ship being bestowed upon
them, in effect making these vessels the ancestors of the later steel battleship and the
modern space Starship. Needless to say all Star Fleet combatants are Line Starships.
However, Star Fleet generally defines Line Starships as those operating at the front
lines and performing the standard Star Fleet duties of defense, law enforcement and
exploration that such ships chiefly perform at all times. Therefore, all Cruisers, Frigates,
Destroyers and Escorts are Line Starships.
CAPITAL SHIPS
The term “Capital Ship” also comes from Earth. Such a ship is regarded as the most
important vessel of the fleet; the one with the heaviest firepower and armor. The term
“capital” is used because of the cost of such vessels, which required a sizeable investment
of financial resources of a government to construct. Today, there is no formal criterion for
the classification, but it is a useful concept when thinking about strategy, for instance to
compare relative fleet strengths in a theatre of operations without having to getting mired
in the details of size and firepower. A capital ship, therefore, is generally the leading or the
primary ship in a fleet or squadron and as such, all Battleships, Attack Carriers and
some Heavy Cruisers are considered Capital Ships.

VOLUME II
FLEET COMBATANT CLASSES
Combatants are Star Fleet ships specifically designed for combat. Combatants vary in
size, mass and firepower, but all are designed with the same basic criteria in mind: (1)
armament, (2) armor, (3) space worthiness, (4) habitability, (5) maneuverability, (6)
speed, and (7) endurance. In this section the various categories of combatants will be
discussed. In general, all Star Fleet combatants are referred to as Starships[8].
The first and foremost criterion a combatant must have is the ability to inflict damage to
other vessels. This is accomplished using the weapons designed for this purpose, which is
known as armament. The primary armament of Star Fleet combatants are the phaser and
the photon torpedo. However, combatants may also use attack or fighter craft to inflict
damage as well. A combatant must also be capable of withstanding attack from other
vessels as well. This is generically known as armor, or the protective capability of the ship.
To meet this criterion Star Fleet ships are equipped with protective screens and shields.
A combatant must be able to handle severe space conditions such as ion storms, meteor
showers and hard radiation. This is known as space worthiness. In addition, Star Fleet
ships must also provide a safe, comfortable home for its crew, which is its habitability. And
a Star Fleet ship must also be capable of starting and stopping fast, to make sudden
changes in speed and to turn in as short a radius as possible. This is maneuverability. But
most important, a combatant must have speed in order to get to the scene of action
quickly. Speed may be used to overtake a fleeing enemy or to withdraw from an area if it
becomes necessary. Speed and maneuverability together help a ship avoid direct hits from
an enemy and allow it to quickly relocate to gain a more advantageous position. The last
criteria for a combatant is range or endurance – the ability of the ship to remain in deep
space for long periods of time, covering hundreds of light-years without refueling or taking
on fresh water, air or provisions such as food and other stores.
Table 2a63.1
TABLE OF GENERAL COMBATANT CLASSES
Combatant Class Average Maximum
Average Basic
Weight Speed Functions
Designation Name Crew Armament1
(MT) (WF)
Attack  Long-range attack
AA 241,000 750 9.1 A,B,C,D,S,T
Carrier  Command Flagship
 Primary battle vessel
BB Battleship 208,000 500 8.8 B,C,D,F,P,S,T
 Command Flagship
 Primary battle vessel
CC Cruiser 173,000 430 8.4 B,D,F,P,S,T
 Squadron Flagship
 Screening vessel
DD Destroyer 131,000 250 7.8 B,D,F,S
 Law Enforcement
 Merchant vessel and
EE Escort 69,000 200 7.8 B,D,S
convoy protection
 Hunter-Killer
FF Frigate 159,000 350 8.0 B,C,D,F,S,T
 Fleet protection
 Ground assault
GG Assault 207,000 2252 7.6 B,C,D,P,S,T
 Troop transport
Notes
1. Armament codes:
A – Attack or Fighter Craft, B – Phaser Banks, C – Phaser Cannons, D – Deflectors, F – Photon
Torpedoes, P – Primary Phaser Batteries, S – Shields and Screens, T – Tractors.
2. Less troops.

VOLUME II
ATTACK CARRIERS[9]
An Attack Carrier (A-class) is the largest man-made vessel in space and a somewhat
recent addition to the fleet. Only five such “AA” vessels were ever built, the first one being
commissioned in 2254. Attack Carriers are essentially large, flat vessels containing well
over a hundred attack, interceptor or fighter craft used for long-range reconnaissance and
combat missions. Carriers serve as a platform for making strikes against planets and fleet
targets, and to protect the Carrier and its group using fighter craft. In addition, these
ships are equipped with the most powerful phaser batteries among all of the ships in the
fleet, and can reach speeds of up to Warp 9 due to their large main engines. An example
of an Attack Carrier is shown in Figure 2a63.1.
Essentially an offensive weapon, Attack Carriers are not used for standard Starship
patrol missions and as such, will not be assigned to exploration or survey missions. These
ships have minimal facilities for the study of scientific phenomenon and therefore, are
primarily used for military purposes and for handling general emergencies.
Their primary function of this class of vessel in peacetime is to project power and political
influence during tense situations. Stationed near hostile territory, their presence alone will
make any hostile force think twice before engaging any Federation asset.
Attack Carriers are seldom deployed alone, but instead they are the primary capital ship
of a Battle Group. Carriers serve as the flagship for the Group Commander who will
maintain his or her office aboard the flagship and therefore, is always onboard with the
group. In essence, the Attack Carrier is the combat control center for the entire group.
BATTLESHIPS
The primary capital ship of a fleet is the Battleship (B-class). These vessels are very
large Starships with powerful weapon systems and look similar in appearance to the
standard Cruiser class Starship, as illustrated in Figure 2a63.3, but on a much larger
scale. The primary function of a Battleship (BB) is to inflict severe damage to the enemy.
Their weaponry is such that they can destroy the most heavily shielded vessels and most
large planetary bases. As such, they are used almost exclusively during wartime
conditions.
During peacetime Battleships generally perform a diplomatic role, engaging in diplomatic

exchanges and affairs of state. They are used to display the power of the Federation. As
with Attack Carriers, this class of ship is primarily an offensive weapon and will not be
assigned to exploration or survey missions.
A Battleship will usually serve as the flagship for the Fleet Commander when he or she
is embarked in space. Battleships are large enough to contain the offices and staterooms
for the flag command staff. Where there may be more than one Battleship within a fleet,
the Fleet Commander will select one of them to be his or her flagship.
A variant to this class of vessel is the Battlecruiser (Figure 2a63.4), which is a smaller
version of the larger ship, but with greater speed. These vessels have a class designation
of BC and contain the same armament as a Battleship, but are slightly smaller in size. In
addition, Battlecruisers also carry a greater number fighter and interceptor craft than the
standard Battleship.

VOLUME II
CRUISERS
Second to the Battleship in power is the Cruiser (C-class) class of Starship. These
ships were designed for speed as well as for firepower. However, unlike the Battleship
the primary missions of Star Fleet will generally be carried-out using this class of vessel.
That is, these ships perform the function of exploring deep space; seeking out new life and
civilizations, scientific investigation, act as the regional court and will generally be involved
in the protection of Federation persons, property and trade within deep space. A fleet will
average around seven (7) such ships ranging in size from Heavy Cruisers (HC) to Light
Cruisers (LC). In addition, each of the permanent flotillas will have at least one Heavy
Cruiser to act as the Flagship for the Flotilla Commander. These ships are primarily
deployed at the outer boundaries of Federation space, especially near hostile systems or
in unexplored regions of space. Their speed allows them to reach an area of space in the
shortest amount of time, and will typically receive their orders and missions from nearby
Starbases or Star Fleet stations.
Cruisers (CC) are well suited for the task of exploration since their large presence and
firepower would impress any new culture it discovers, and would be able to manage any
unknown hostile power they may encounter. In addition, the impressive nature of the
Cruiser may make it easier to enlist new members into the Federation since these ships
would give the impression of a strong Federation and one that could protect the new
race from its enemies. Examples of cruisers are illustrated in Figures 2a63.5 and 2a63.6.
FRIGATES[10]
Each fleet will also contain a class of ship called Frigates (F-class). These vessels are just
slightly smaller than a Light Cruiser, but with greater speed. However, Frigates do not
have the same level of firepower as the Cruiser class and as such, are typically deployed
to areas where the potential for hostility is less than that a Cruiser may experience. As
such, these ships will perform the same basic functions as Cruisers, but with a reduced
risk of encountering a belligerent force. A typical Frigate class ship can be seen in Figure
2a63.8, with a variant having a Secondary Hull shown in Figure 2a63.9.
In modern space fleets, Frigates will be used to protect other warships. The Frigate was
introduced to remedy some of the shortcomings inherent in the Destroyer design, namely
limited armament, many of which were built with a single main engine that limited speed,
and lacked range. As such, the Frigate became the ship class of choice among the Local
Forces and therefore, became their primary interplanetary defense vessel.
Frigates are divided into two types or categories: The Fast Frigate (FF) and the Heavy
Frigate (HF) or Frigate-Cruiser. The Fast Frigate (Figure 2a62.10), usually called
simply a Frigate, will be used during battle engagements as an attack vessel. In some of
Star Fleet’s standard maneuvers the FF “charges” into battle to supply cover fire to the
ships in the rear, while inflicting damage to the enemy force. Heavy Frigates (Figure
2a63.7), on the other hand, will generally be used to protect a Battle Group – flanking
the Attack Carrier. Their primary function is to screen the carrier from attack by heavier
enemy vessels.

VOLUME II
DESTROYERS
The next class of ship in a fleet is the Destroyer (D-class) class. A Destroyer is a fast
and maneuverable, yet long-endurance combatant intended to escort larger combatants in
a fleet or battle group and to defend them against smaller, short-range, but powerful,
attackers. These ships account for the bulk of the fleet with an average of about 24 such
ships in each fleet, which include Heavy Destroyers (HD – Figure 2a63.11), Standard
Destroyers (DD – Figure 2a63.12) and Destroyer Escorts (DE) and Corvettes (EE).
However, it should be noted that the DE and EE class of destroyer have been assigned
their own class designation of Escort or E-class of vessel. A Heavy Destroyer has a
similar configuration as a standard Starship with a Primary Hull, a Secondary Hull and
two outboard main engines anchored to the Secondary Hull by support pylons. However,
the smaller Destroyer Escorts and the light Corvettes do not have a Secondary Hull
and are generally propelled by only one main engine.
Destroyer class ships are basically used to patrol the central areas of the octants in which
the fleet is assigned. They perform the majority of the escort and law enforcement duties
in deep space. Destroyers will generally patrol the various flight routes and space lanes
to ensure that private and commercial vessels comply with travel regulations. In addition,
Destroyers also perform space surveys and other functions relating to the safe navigation
of ships in deep space.
During fleet action, Destroyers act as screening vessels, protecting the fleet from enemy
vessels and fighter craft, and sweeping space for high-energy mines. They typically will
flank the fleet and protect it from vessels approaching from the sides and will be assigned
to protect the fleet support vessels, if required. Destroyers (as well as Frigates) are, as
always, the workhorses of the fleet, the former optimized for defense and the latter for
attack or offense. They are equally at home in large task groups or autonomously such as
for sanctions enforcement, humanitarian relief or anti-contraband patrols. The principal
criterion for all full sized Destroyers is that it must be able to keep up with or exceed the
speed of the faster Capital Ships.
ESCORTS
Escort (E-class) vessels are light combatants used primarily in a commercial protection
role. They are small Starships with only one main engine, as shown in Figure 2a63.13,
but are capable of accelerating to Warp speeds faster than any other combatant – though
they may not have the top speed to equal that of the capital ships. However, they are
more maneuverable than the large vessels and can penetrate an enemy’s defensive line for
close assault, while evading the enemy’s fire.
The first of the E-class of ships is the Corvette (EE – Figure 2a63.14), which first
appeared during the Romulan War as an easily built patrol and convoy escort vessel. Most
of the patrol ships used by Local Forces are of the Corvette class. These ships are quite
fast owing to their light weight, but with main engines comparable to that of a Destroyer.
As such, they are primarily used for space traffic and law enforcement where quick
acceleration and speed is important for overtaking fleeing ships.
A Destroyer Escort (DE) is the designation given to a small, relatively slow Destroyer
designed for use as screening vessels used to escort convoys of commercial and supply
ships. The DE is a slightly larger E-class vessel that fits between the standard Destroyer
and the Corvette. As such, they will have a role similar to that of a Light Destroyer.

VOLUME II
GROUND ASSAULT SHIPS[11]
Ground Assault (G-class) ships are large flat vessels designed to carry Star Fleet
Marine troops, ground combat vehicles and attack support craft. Their primary mission is
to rapidly deliver combined-arms task forces to galactic crises and to land ground troops
where needed. Figure 2a63.2 illustrates a typical G-class ship.
A Ground Assault ship consists of a single large Primary Hull with an aft Well Deck
used for ground support Attack craft. The Well Deck contains two small hangar bays
and four craft elevators for the support craft. At the aft end of the ship, and within the
"cutwater", is a single large hanger and launch bay for the assault craft, which are used to
transport the Star Fleet Marine troops and their ground vehicles to the surface of a
planet.
The number of troops an Assault ship can carry is that of Brigade strength, which means
that the G-class can handle upwards of about 6000 troops. However, the operations crew
of an Assault ship will typically be around 225 Star Ship Command personnel. Their job
is primarily the management of the vessel and the support of the ground troops and their
equipment.
The number of Attack craft an Assault ship carries will usually be of Group strength
containing several Attack Squadrons. This typically amounts to about 24 Attack and
Fighter craft used to support the ground troops and to protect the ship from attack. At
the present time Star Fleet has only three such ships:
NCC-2201 U.S.S. TARAWA

NCC-2202 U.S.S. OKINAWA
NCC-2203 U.S.S. TRIPOLI
Only three such ships were built since it was determined that large ground assaults were
no longer necessary. However, these ships are still on active service and would be used if
the need arose.

VOLUME II
STAR FLEET SUPPORT CLASSES
Support ships, as the term suggests, support the combatants. These ships perform such
functions as repair, supply and to load nuclear fuel. Support ships come in two distinct
classes: S-class or Support Class and T-class, which is the Transport Class. Typically,
a specific number of S-class types will be assigned to a fleet and all ships within this class
will be under the command of Star Fleet Operations. The T-class ships, on the other
hand, are generally reserved for the Star Fleet Transportation Command.
Table 2a63.2
TABLE OF GENERAL SUPPORT CLASSES
Support Class Average Maximum
Average
Weight Speed Basic Armament1 Functions
Designation Name Crew
(MT) (WF)
 Fuel ships
SF Fuel Ship 143,6002 48 4.8 B,D,S,T  Refuel stations
 Fuel disposal
 Mobile laboratory
SL Laboratory 22,000 175 4.1 D,S,T
 Scientific expeditions
 Care of sick and
SM Hospital 98,200 245 6.7 S wounded
 Disaster relief
10,3003 –  Ship replenishment
SP Supply 30 - 95 6.2 B,D,F,S
65,0002  Spare parts
 Ship repair
SR Repair 95,000 313 6.6 B,D,S,T
 Parts fabrication
 Space surveying
SV Survey 82,000 127 4.8 B,D,S,T
 Planetary surveying
 Supply bases and
18,0003 -
TF Freighter 20 - 100 5.4 B,D,P,S,T stations
53,0002
 Move heavy freight
 Towing ships
TG Fleet Tug 141,0002 146 5.5 B,D,F,P,S,T
 Transport containers
 Transport Shuttlecraft
TR Transport 230,0002 266 7.1 B,D,P,S,T
 Transporting Personnel
Notes
1. Armament codes:
A – Attack or Fighter Craft, B – Phaser Banks, C – Phaser Cannons, D – Deflectors, F – Photon
Torpedoes, P – Primary Phaser Batteries, S – Shields and Screens, T – Tractors.
2. Unloaded weight.
3. Weight for small SP class. Weight is class dependent.

VOLUME II
REPAIR SHIPS
Support-Repair (SR) or “Tenders” are S-class ships that carry out immediate and
temporary repairs on Star Fleet vessels*. Typically, such repairs will be made as a result
of battle or collision where the ship might not be completely spaceworthy. These ships will
physically attach itself to the affected ship with brows and gangways for personnel and
equipment traffic between ships. In addition, these brows also have power connections to
allow the affected ship to receive power from the tender while repairs are in progress.
Repair ships have many shops where ship parts can be repaired or fabricated, and are
equipped with stores containing the spare parts necessary for the repairs.
Repair ships also have large external cranes and gantries for hull and main engine work.
These cranes are normally retracted into lockers on deck topside when not in use. Near
each gantry are hatches where equipment may be hoisted between the tender and the
affected ship.
Repair ships are assigned to fleets by Star Fleet Operations. Typically, four such tenders
will be assigned to a fleet. This number is sufficient to cover six squadrons of Starships
since a single repair ship can service two Starships simultaneously. An example of a
typical repair ship can be found in Figure 2a63.18.
Some repair ships will be assigned to a Star Fleet station nearest to where ships may be
engaging hostile forces, and where no Starbase may be nearby to handle substantial
repairs. In such assignments repair ships will be rotated between stations, but always
nearby to make repairs if necessary.
*Star Fleet ships are not authorized to repair private or commercial ships under Star Fleet Regulation 6640.
However, a repair ship may only make those repairs to such ships if it is necessary to prevent loss of life and the
ship was called in to assist a ship in distress under Star Fleet Regulation 6630.

VOLUME II
SUPPLY SHIPS
A Supply Ship is a generic term used to describe S-class vessels designed to replenish
the fleet. Replenishment includes items that can be purchased at the ship’s store as well as
the necessary logistical items. As such, the S-class ship will have offices on board where
the ship’s Materials Officer maintains an accounting of the provisions consumed by the
replenished ship. This support class is under direct control of Star Fleet Operations and
as such, can only be assigned to specific units by Operations. Therefore, as with repair
ships S-class ships will also be managed by Star Fleet Operations.
The Support-Provision or SP class is the primary vessel used for in-space replenishment
of supplies and equipment. Supplies include foodstuffs, oxygen, nitrogen and other needed
gases, water, tools and the raw material used in material fabricators.
An example of a SP class supply ship can be found in Figure 2a63.15, which is one of the
earlier Reserve (NCC-1141) class ships. With the advent of Attack Carriers and other
capital ships, the size of the SP class had to become larger. Thus, the Replenish class
(NCC-1901) supply ships were developed to meet the needs of the larger ships, and the
Clark (NCC-2230) class developed for Star Fleet stations. The newer SP class can
handle up to four Starship class vessels simultaneously. An example of this class can be
found in Figure 2a63.16.
The Support-Fueling (SF) class is a vessel like the SP, but whose primary function is to
resupply Star Fleet ships with antimatter and other nuclear fuel used for propulsion and
power generation. Although modern Starships have Polymass[12] production units, these
production units can not completely keep up with the demand of the main engines at high
warp speeds and therefore, require periodic charging. The propulsion units of these ships
have large containment rings for the storage of Polymasp and Polymasn – the high-
energy plasma used onboard Warp-driven ships, as well as liquid hydrogen for the fusion-
drive Impulse Engines, Hydrazine, a low-power propellant used for the maneuvering
thrusters of spacecraft and for the primary thrusters of small craft, and as coolant for the
engines.
Fueling ships have large hatches with fueling booms that attach to the main engine of
warp-driven Star Fleet ships and charge the primary loops with Polymass. Fuel ships
also have large Polymass production units to maintain a charge in the storage rings. As
such, fueling ships can be large in size, though the crew size required to operate the
vessel is quite small. These ships also have large retractable ram scoops that draw free
hydrogen gas from clouds and small nebulae. The gas accumulated will be compressed
and cooled into liquid hydrogen. An example of this class can be found in Figure 2a63.17.

VOLUME II
SCIENTIFIC SHIPS
The primary scientific ship in the fleet is the Galactic Survey Vessel or SV class (see
Figure 2a63.24). These ships primarily come under the control of the Star Fleet Space
Exploration Command. As such, the SV class can only be assigned to survey and
exploration missions by Star Fleet Operations. Although completely under the command
of Star Fleet Operations, the Star Fleet Bureau of Federation Space Exploration
may make requests to Star Fleet Operations for the utilization of these ships for survey,
mapping or exploration operations. However, all such BUEXPLOR missions or tasks using
SV class vessels will be under the direction of Star Fleet Operations. BUEXPLOR
personnel may be assigned to such vessels to perform their duties, engage in scientific and
other research using the ship’s facilities, but cannot direct or interfere in the duties of the
crew, which will be Star Fleet Operations personnel.
The SV class contains many laboratories and research facilities with computers and other
equipment needed to perform the studies they are required to accomplish. However, most
of the labs on these ships are designed for planetary exploration and will not be used for
general-purpose experimentation. In addition, these ships also contain, and will deploy,
marker buoys and other devices during exploration activities.
Another scientific ship is the Laboratory ship or SL class (see Figure 2a63.19). The SL
class is primarily used by the Star Fleet Division of Science, but does not maintain the
vessel or provide the crew or the command for the ship. The ship itself will be under the
command of XCOM. The Science Division will simply assign the scientific personnel to
the ship and will make requests to Star Fleet Operations regarding where a SL class
ship should be used to accomplish a specific scientific mission.
HOSPITAL SHIPS
Support-Medical or Hospital ships (SM – Figure 2a63.20) are essentially large mobile
medical facilities capable of handling most emergencies. They contain large convalescence
areas that can handle up to 2400 patients. These ships were designed to handle battle
casualties from several Starships simultaneously. Hospital ships are also used to provide
disaster relief to Federation victims of natural disasters and will be deployed to any
disaster area by Star Fleet Command. Hospital ships have extensive surgery and
examination areas, and contain many different types of laboratories for the investigation
and research into new diseases. Hospital ships are equipped with special gyro-stabilizers to
keep it stabile during surgical operations and to keep the patients comfortable while
travelling at warp speeds. They are also equipped with large transporter facilities for the
transfer of large numbers of the sick and injured, and contain two hangar bays along with
several medical shuttlecraft used for ground medical emergencies and evacuations.
Hospital ships are assigned by Star Fleet Command and will generally be attached to a
fleet. The placement and movement of Hospital ships within a fleet is solely the province
of the Fleet Commander. Typically, Hospital ships will not be assigned to any squadron,
but are usually part of the Command Group of the fleet. As such, Hospital ships will
generally operate independently from any Fleet Squadron. Hospital ships are manned
by Star Ship Command personnel for the general operation of the vessel. However, the
hospital portion of the ship will be completely manned and administered by Star Fleet
medical personnel.

VOLUME II
TRANSPORT VESSELS
Transport or T-class vessels are the “work horses” of Star Fleet and makes up the
entire fleet of the Star Fleet Transportation Command (TRANSCOM), a subdivision of
the Star Fleet Division of Materiel. All operations concerning T-class ships will come
under the authority of TRANSCOM and therefore, only TRANSCOM can assign these
vessels to duties and operations where heavy freight or equipment must be transported to
Star Fleet facilities. Star Fleet Operations and other divisions must make requests to
TRANSCOM for such transport duties. Ships within this class also include civilian-manned
vessels, which are not commissioned Star Fleet vessels.
Among the Transport (T-class) vessels is the Fleet Tug or TG (see Figure 2a63.21). A
Fleet Tug is a ship of the Star Fleet Transportation Command used primarily to haul
containers and tow crippled ships. These ships have limited repair facilities, only enough to
keep a vessel spaceworthy and allow it to be moved. The TG class is equipped with very
powerful Tractors and Deflectors to pull and push heavy objects in space, such as ships
and Fleet Containers, at Warp speeds.
The Freighter or TF (see Figure 2a63.22) is a ship designed to haul heavy freight and
equipment, specifically to Star Fleet bases and stations. These ships primarily comprise
the Military Space Lift Command or MILIFTCOM, a subdivision of the Star Fleet
Transportation Command. Freighters will also be used to haul equipment for the Star
Fleet Construction Command. These ships are not directly assigned to a fleet, but will,
instead, be attached to a fleet as a separate command unit.
Another vessel of MILIFTCOM is the Shuttlecraft Transport or TR ship. The function

of these ships is to deliver service craft to bases and stations since most of these small
craft do not have the range to travel to remote facilities. In addition, these transports are
also used to replace shuttlecraft assigned to Starships that are too badly damaged for
repairs onboard the ship, or where the ship does not have the time to go to a nearby
Starbase for a replacement. The TR class is a large vessel with a forward Primary Hull
and an aft Secondary or Service Hull as shown in Figure 2a63.23, which can be
detached if necessary. The two hulls are attached via an access boom and all power to the
ship originates from the Primary Hull, with limited power being generated from the aft
Impulse unit. The Service Hull also contains two large Hangar Bays for shuttlecraft
and other small vessels.
Besides shuttlecraft the TR class also contains berthing space for 1400 persons, with 50
single staterooms, 175 double staterooms and 50 large berthing areas or bunk rooms that
can hold 20 troopers each. As such, these ships are also used as personnel and troop
transports. Troops assigned to a base will be transported there by such ships.

VOLUME II
SPECIAL PURPOSE VESSELS
Star Fleet also contains some specialized ships for intelligence and other operations.
Specifically, the Intelligence/Command ship, or IT-class, is used for special operations
by Star Fleet Intelligence and as such, their configuration, functions and operations are
CLASSIFIED. An example of an intelligence ship can be seen in Figure 2a63.25.
The Mobile Repair Facility (MR) is not a ship, but a mobile Drydock or construction
frame used for extensive repairs of Star Fleet ships when the vessel cannot be moved or
otherwise cannot be towed to a repair facility. MRs contain small repair and fabrication
shops and offices attached to their frames as illustrated in Figure 2a63.26. There is also a
main control room up front on top of the structure where the commander of the MR is
located.
MRs do not have propulsion systems to move them about, but must be towed to the site
of the affected vessel. However, an external propulsion unit can be temporarily mounted
to the frame that will allow it to move to a site under its own power, but can only propel
the MR at sublight speeds since the unit has no capability to generate a Warp field and as
such, cannot warp space. Such temporary propulsion units are only used for relocating the
frame to nearby areas. Only by being towed by a warp-driven tug can the unit obtain warp
speed, and even then there are restrictions on the tug as to how fast it can haul the unit.
The maximum speed a MR unit can be towed is Warp 3. MRs come under the control of
the Star Fleet Construction Command and will typically be towed to the location of the
affected ship by a Fleet Tug (TG) of the Star Fleet Transportation Command.
Cargo Drones (TD-R) are special purpose T-class vessels. These are unmanned robot
ships that perform the replenishment function to remote Star Fleet stations and outposts.
Therefore, these vessels have the –R (robotic) designation attached to their class. The
TD-R operates on a pre-programmed schedule and flight path. These ships have minimal
armament, supplied only with screens and shields, and therefore, will not be deployed to
high-risk areas.

VOLUME II
SHIP DESIGNATION
Star Fleet ships are designated based upon the requirements set forth in Star Fleet
Regulation 2400. In accordance with this regulation, all Star Fleet combatants and fleet
support ships will be commissioned: "United Space Ship" or "U.S.S." This convention
was adopted from the old UESPA standard. Civilian operated vessels of the Star Fleet
Transportation Command or other commands designated as active vessels are called:
"Starfleet Ship" or "S.S."
Star Fleet capital ships or "Starships of the Line" are military vessels and therefore,
have the designation of "Naval Class Cruiser." As such, the registry numbers of these
vessels are prefixed with "NCC". This convention was originally adopted during the early
Romulan War and has remained in effect ever since. All Star Fleet ships that were built as
experimental vessels or that are under development or being evaluated will have a
designation of "Naval Class Experimental Ship." As such, the registry numbers of these
ships will be prefixed with "NX".
Civilian manned ships of the Star Fleet Transportation Command that are owned by
Star Fleet are not commissioned vessels in the strict sense, but will have the designation
of "Naval Class Auxiliary Support Ship." As such, the registry numbers of these ships
will be prefixed with "NAS".
SHIP NAMING CONVENTION
Star Fleet ships are generally commissioned using a naming convention developed by
Star Ship Command. The following table catalogs the naming conventions of Star Fleet
ships by class designation.
Table 2a63.3
GENERAL SHIP NAMING CONVENTION
Class
Class Designation Naming Convention
Attack Carrier AA Terms indicating formidability
Battleship BB Terms indicating invincibility
Cruiser CC Names of past historical warships
Destroyer DD Names of historical or mythical warriors
Escort EE Names or terms indicating speed or agility
Frigates FF Names or terms indicating courage
Assault GG Names of historical assault ships
Intelligence Ship IT Terms indicating vigilance
Fuel Ship SF Names or terms indicating fuel
Terms indicating discovery or names of famous
Laboratory Ship SL
scientists
Hospital Ship SM Terms indicating comfort or convalescence
Supply SP Terms indicating provision or delivery
Terms indicating ability or names of past repair
Repair SR
vessels
Survey SV Names of famous explorers
Freighter TF Names of historical transports
Fleet Tug TG Names or terms indicating strength
Transport TR NO CONVENTION

VOLUME II
SHIP IDENTIFICATION
In accordance with Federation regulations, all ships that operate within Federation
space must be equipped with devices that will identify the vessel. The purpose of this is for
communications and to prevent collisions in space. Devices include, as a minimum, port
and starboard running lights and registry beacons. As such, all Star Fleet vessels will
have such devices as required by law.
A Registry Beacon is a pulsed signal containing critical information about the vessel in a
compressed form such as its Federation registry number, point of origin, class of vessel
and a binary IFF signal. The signal must conform to the Federation Registry Protocol
(FRP), which establishes the format of the beacon. This is the method used by Star Fleet
ships to identify each other and to identify all other Federation vessels. Failure to send
such a Registry Beacon will subject the owner and operator of the vessel with heavy
fines and loss of license.
Another form of identification, though not used for navigational or registration purposes, is
the ship’s Prefix Code. This code is essentially a communications address to the ship’s
main computer that allows remote access to the computer by Star Fleet Command. The
Prefix Code is generally used to program a mission into the ship’s computer when a high
level of secrecy is required[13]. Only Star Fleet personnel with the highest level of security
clearance will know how to access the prefix code of any Star Fleet vessel.
The basic shape of the Starship class of vessel is unique to Star Fleet and as such, no
other vessel within the Federation will be allowed to look like a Starship. Star Fleet
ship design standards require that all Star Fleet ships must place their registry number
prominently on the bow of the vessel, along with its commissioned name, as follows:
All Star Fleet combatants and fleet support ships will have a NCC designation, which
stands for “Naval Class Cruiser” as required under Star Fleet Regulation 2400. In
addition, the commissioned name of the vessel will be prefixed with U.S.S. or “United
Space Ship”, also required under Star Fleet Regulation 2400.
As part of Star Fleet ship identification, all commissioned Star Fleet ships, craft and
units will have a red commissioning pennant painted on the hull of the vessel, with the
registry number of the vessel superimposed on the pennant. This pennant is a tapered
device that is prominently displayed on all commissioned Starships, usually on the
outboard side of the ship’s main engine nacelles. Reserve or decommissioned vessels,
however, may retain the registry number, but the commissioning pennant will be removed.
For vessels operating on their own power and which perform fleet duty, an additional
Fleet Service pennant may be displayed on their hull. For multi-sectioned Starships, this
pennant will usually be displayed on the port and starboard sides of the ship’s Secondary
Hull.

VOLUME II
AUXILIARY SUPPORT SHIPS
Auxiliary support ships are vessels constructed or leased by Star Fleet, but manned by
civilian employees of Star Fleet. They are not commissioned vessels in the strict sense,
but are Star Fleet vessels nonetheless.
The identification standard for these vessels will follow closely with the standards used to
identify commissioned vessels. That is, vessels of this type will have their registry number
prominently placed on the bow of the vessel, along with its name as with commissioned
Starships, for example:
These ships will have a NAS designation, which means “Naval Class Auxiliary Support
Ship” as required under Star Fleet Regulation 2400. And the designated name of the
vessel shall be prefixed with S.S. for “Starfleet Ship”, also required under Star Fleet
Regulation 2400. These ships will not display the red commissioning pennant as on
Starships since they are not commissioned Star Fleet vessels. However, some of these
ships may display the Fleet Service pennant if they are currently assigned to fleet duty.
Many of these ships are of the older Daedalus class vessels that were not converted into
modern Starships. These ships were placed as part of the transport fleet within the Star
Fleet Transportation Command as civilian-manned and operated vessels. As such,
these ships were re-designated as “Starfleet Ship” or S.S.

VOLUME II
SERVICE CRAFT
Star Fleet defines a “Craft”, or Service Craft, as a small vessel which can be loaded
onto a ship or station, or that can land on a planet and housed at a base. However, unlike
ships, craft are not commissioned vessels of the Star Fleet. They will typically be attached
to a larger command and therefore, are considered the property of the command. As such,
shuttlecraft will have the same registry number as the ship or command unit to which it is
attached, but with an additional sequence number appended at the end with a slash mark
and the commissioned name of the ship, base or station under the registry as illustrated
below and in Figure 2a63.28.
Service craft may also have a unique name given to them as illustrated in Figure 2a63.28.
However, the naming of service craft is a recent practice within Star Fleet and is not a
requirement under any regulation. The names of craft are assigned and maintained by the
Star Fleet Service Craft Command, along with the Service Craft Registry.
Table 2a63.4
STANDARD SERVICE CRAFT NAMING CONVENTION
Class General Function Naming Convention
A Attack, Fighter or Interceptor No Name Applied
B Base service Known stars, planets, systems and constellations
C Command service No Name Applied
D Dock service No Name Applied
E Engineering duty Famous engineers and inventors
F Fleet Duty - exploration Famous explorers (e.g. Columbus)
G General service Names of famous people
H Heavy Duty No Name Applied
M Medical service Famous doctors or persons in the medical field
S Scientific service Famous scientists (e.g. Galileo)
T Transport service No Name Applied
Service craft come in many types and the fleet has many such craft of various classes and
purposes. The standard craft used by almost all ships is the Class-F Shuttlecraft. This is
an all-purpose vessel used to transport crewmembers and equipment long distances away
from the ship. An example of this craft is shown in Figure 2a63.28. Another important class
of craft is the Class-A Attack craft. This particular vessel has the single purpose of
combat, to protect the fleet and to support ground operations, and will generally be found
on Attach Carriers and Ground Assault ships. An example of this class of service craft
is presented in Figure 2a63.27.

VOLUME II
Figure 2a63.1
TYPICAL ATTACK CARRIER STARSHIP

VOLUME II
Figure 2a63.2
TYPICAL GROUND ASSAULT SHIP

VOLUME II
Figure 2a63.3
TYPICAL BATTLESHIP CLASS STARSHIP

VOLUME II
Figure 2a63.4
TYPICAL BATTLECRUISER CLASS STARSHIP

VOLUME II
Figure 2a63.5
TYPICAL HEAVY CRUISER CLASS STARSHIP

VOLUME II
Figure 2a63.6
TYPICAL CRUISER CLASS STARSHIP
138
4
189
7
708
130
102 0

VOLUME II
Figure 2a63.7
TYPICAL HEAVY FRIGATE CLASS STARSHIP

VOLUME II
Figure 2a63.8
TYPICAL FRIGATE CLASS STARSHIP

VOLUME II
Figure 2a63.9
TYPICAL SHORT-DECK FRIGATE CLASS STARSHIP

VOLUME II
Figure 2a63.10
TYPICAL FAST FRIGATE CLASS STARSHIP

VOLUME II
Figure 2a63.11
TYPICAL HEAVY DESTROYER CLASS STARSHIP (PRE-CONVERSION)

VOLUME II
Figure 2a63.12
TYPICAL DESTROYER CLASS STARSHIP

VOLUME II
Figure 2a63.13
TYPICAL ESCORT CLASS STARSHIP

VOLUME II
Figure 2a63.14
TYPICAL CORVETTE CLASS STARSHIP

VOLUME II
Figure 2a63.15
TYPICAL SUPPORT CLASS LIGHT SUPPLY SHIP

VOLUME II
Figure 2a63.16
TYPICAL SUPPORT CLASS HEAVY SUPPLY SHIP

VOLUME II
Figure 2a63.17
TYPICAL SUPPORT CLASS FUEL SHIP

VOLUME II
Figure 2a63.18
TYPICAL SUPPORT CLASS REPAIR SHIP

VOLUME II
Figure 2a63.19
TYPICAL SUPPORT CLASS SCIENCE/LABORATORY SHIP

VOLUME II
Figure 2a63.20
TYPICAL SUPPORT CLASS HOSPTIAL SHIP

VOLUME II
Figure 2a63.21
TYPICAL TRANSPORT CLASS FLEET TUG (WITH CONTAINER)

VOLUME II
Figure 2a63.22
TYPICAL TRANSPORT CLASS LIGHT FREIGHTER

VOLUME II
Figure 2a63.23
TYPICAL TRANSPORT CLASS SHUTTLECRAFT TRANSPORT

VOLUME II
Figure 2a63.24
EXAMPLE OF A SURVEY/EXPLORATION SHIP

VOLUME II
Figure 2a63.25
EXAMPLE OF AN INTELLIGENCE/COMMAND SHIP

VOLUME II
Figure 2a63.26
EXAMPLE OF A MOBILE REPAIR UNIT
138
4
189
7
708
130
102 0

VOLUME II
Figure 2a63.27
EXAMPLE OF AN CLASS-A ATTACK CRAFT

VOLUME II
Figure 2a63.28
EXAMPLE OF A CLASS-F FLEET SHUTTLECRAFT
PUSH

VOLUME II
6.4 STAR FLEET SHIP ASSIGNMENT

The primary function of the Star Fleet Division of Operations is the command and
management of the Operating Forces of Star Fleet. The Operating Forces of the
Star Fleet essentially comprise the various fleets, flotillas and other groupings of ships. In
this section the standard by which ships are organized, designated and apportioned to
command units will be discussed.
SHIP ORGANIZATION STANDARD
In accordance with ARTICLE 61 of the Star Fleet Charter, Star Fleet vessels will be
grouped together and organized into specific units. Star Fleet Command has established
the following definitions for the organization of Star Fleet ships:
Table 2a64.1
SHIP ORGANIZATION STANDARD
Commander in Chief
Unit Definition
Title Rank
The largest operational unit of Star Fleet. A fleet may be
comprised of several Squadrons, Divisions and Groups, all
Commander:
Fleet under the command of a single Fleet Commander. At the Vice Admiral
<nth> Fleet
present time, the eight permanent fleets are comprised of six
Starship Squadrons and a Flagship.
A smaller, specialized grouping of vessels. A Force is
basically a temporary organization created to perform a
specific military task. Such forces may be called Task Force or Commander:
Force Vice Admiral
Strike Force, and are typically slightly smaller than a fleet. A <X> Force
Force may be comprised of several Groups and Squadrons
under the command of a Force Commander.
A grouping of two or more Squadrons. Flotillas are generally
called mini-fleets, and are typically comprised of several Commander:
Flotilla Rear Admiral
Squadrons or Divisions, all under the command of a single Flotilla <n>
Flotilla Commander.
An assemblage of vessels into a specific task command, and
will generally center around an Attack Carrier, Battleship or
other capital ship, which will be called the Flagship. Such
Commander:
Group groups will have designations such as Attack Group, Battle Rear Admiral
<X> Group <n>
Group or Strike Group. In command of this assemblage is the
Group Commander, usually of flag grade and will be aboard
the Flagship.
A grouping of two or more Divisions of vessels. A Squadron
will usually be comprised of ships of the same class, or may
be comprised of ships with a similar mission or capability. The Commander:
Squadron Squadron will be commanded by a Squadron Commander <X> Squadron Commodore
who is typically the Commanding Officer of the lead ship <n>
within the Squadron, and will usually have the rank of
Commodore.
A grouping of two or more ships of a particular class. The
function of a Division is to group a class of ship together,
generally because the class of ship determines its basic
mission. Divisions are designated by the class of ship that Commander:
Division Captain
comprises the Division. For example, a Cruiser Division will <X> Division <n>
have the designation CRUDIV and will be commanded by a
Division Commander, who will normally be the senior
Commanding Officer of all ships within that division.

VOLUME II
FLEETS
In general, the majority of Star Fleet ships will be assigned to one of the eight permanent
fleets established under ARTICLE 62 of the Star Fleet Charter, except those special
operations vessels which function independently such as Intelligence ships (IT) and those
assigned to the Star Fleet Transportation Command. And as stated in Section 3.3 of
this volume, only the Director: Star Fleet Command can originate and designate
permanent fleets. However, the assignment of ships to fleets will be the responsibility of
the Chief of Star Fleet Operations and specifically, by Star Ship Command. As such,
it will be Star Fleet Operations that will assign ships to fleets and other operating units
of the Star Fleet. However, once a ship is assigned to a fleet it is the Fleet Commander
who decides where in the fleet the ship will be deployed; specifically, in which of the six
Fleet Squadrons the ship will be assigned.
As stated above, fleets are the largest operational unit of vessels within Star Fleet and
are ordinarily, but not necessarily, permanent formations assigned to particular quadrants,
octants or sectors in space. However, and for the time being, the eight designated fleets
are permanent creations. Most of the fleets belonging to the members of the Federation
will be named after the particular star system, constellation or region of space to which
they belong. But in the case of Star Fleet, fleets will be identified by number.
Fleets may also be created during times of war or galactic conflict. In such times fleets will
be temporary groupings of vessels made up of ships or units from the eight permanent
fleets. Such temporary fleets will be created by Star Fleet Operations with the approval
of the Director: Star Fleet Command, or may be created by the Director himself for a
specific purpose, or designed to handle a major conflict within an octant. In such cases,
there may be more than one fleet stationed and operating within a Federation octant. In
general, such temporary fleets will be completely managed by Star Fleet Operations.
Temporary fleets created by Star Fleet Operations will be designated using the same
numeric standard used to designate the eight permanent fleets, but starting with the
number eleven (11) since the numbers nine and ten are reserved for the two permanent
Flotillas. This numeric designation will remain with the fleet until it has been disbanded or
decommissioned, in which case the fleet designation will no longer be used. Any temporary
fleet created after the disbandment of a previous temporary fleet will be designated with
the next numeric value, and so forth.

VOLUME II
FLOTILLAS
A Flotilla, on the other hand, is a small version of a fleet and is typically defined as a
grouping of two or more Squadrons of vessels into a single unified command. The term
flotilla comes from the old Earth Spanish word flota and from the French word flotte,
meaning a formation of small sea-going warships that may be part of a larger fleet, but
the term modernized for space-going vessels today. A flotilla is usually composed of a
large homogeneous grouping of warships of the same class, such as Destroyers, and will
generally be composed of several divisions of vessels of this same class. In this case the
flotilla will be commanded by the most senior ship commander within the unit. However, a
flotilla may also contain one or two heavier class of ship, such as a Cruiser, to act as the
mobile command center for the group and as the Flagship for the command. In general,
a flotilla is often, but not necessarily, a permanent formation.
Flotillas are generally designated with an abbreviation of FLOT and are consecutively
numbered starting with the number of the last permanent fleet, such as those numbered
for the two permanent flotillas: Flotilla 9 and 10. As stated in Section 3.3 of this volume,
Star Fleet contains two permanent Flotillas as required under ARTICLE 63 of the Star
Fleet Charter, and as with the eight permanent fleets, only the Director: Star Fleet
Command can create and designate permanent flotillas. However, the ships within a fleet
may also be organized into flotillas as well, which will usually be formed by combining two
or more Fleet Squadrons, which is completely up to the Fleet Commander. Flotillas
organized by a Fleet Commander will be so numbered according to the fleet in which it
was created. For example, a flotilla organized within the Third Fleet will be designated
FLOT31, which indicates the first flotilla within Third Fleet.
A flotilla will usually be commanded by a Rear Admiral or a Commodore, depending on

the size and importance of the unit. The commander of a flotilla will have the title of
Commander: Flotilla <n> or COMFLOT<n>, or in the case of a Type Command
flotilla, Commander: <type> Flotilla <n> or COM<type>FLOT<n>.
FLEET SQUADRONS
Fleet Squadrons are specific ship assemblages within a fleet created and designated by
Star Fleet Operations, and are principally groupings of combatants along with a number
of support ships. Their primary function is to organize a combatant force for assignment to
a specific location. Starships assigned to a fleet will generally be assigned to one of its
Fleet Squadrons. An example of a typical Fleet Squadron on maneuvers can be seen in
Figures 2a64.1 and 2a64.2.
As with fleets, Fleet Squadrons are designated by a numeric value. Fleet Squadrons
are numbered based upon the fleet they were originally organized, and will be created and
maintained by Star Fleet Operations. However, the assignment of ships within a fleet to
individual Fleet Squadrons will solely be the business of the Fleet Commander, which
also includes any reassignment or rotation of ships from one squadron to another.
Fleet Squadrons are usually commanded by a flag officer with the rank of Commodore,
who will also be the Starship Commander of the lead or Flagship of the squadron and
who will have the title of Commander: Fleet Squadron <n>. Star Fleet ships assigned
to Fleet Squadrons will report directly to the Squadron Commander.

VOLUME II
TYPE COMMANDS
Type Commands refer to a specific organization of vessels of a specific class, which

generally applies to Squadrons and Divisions. As such, the assignment of ships to Type
Commands will primarily be dependent upon the class of ship. However, and in general,
all ships are generally grouped into one form of Type Command or another by Star Ship
Command. Such Type Commands are generally referred to as Unit Commands, which
are the elementary basis of ship organization. At the lowest level is the Division, which is
a grouping of two or more ships of the same class or type. Thus, a division of cruisers will
contain two or more such ships and will have the designation of Cruiser Division <n> or
CRUDIV<n>. However, capital ships such as Battleships and Attack Carriers will not
be organized into divisions since they will typically be Flagships of a particular group.
Type Command units will generally be commanded by a Type Commander, typically a

flag officer with a rank of Rear Admiral. An example of a Type Commander would be
the Fleet Support Commander – the officer in charge of all support ship activities and
personnel assigned to a given fleet.
GROUP COMMANDS
In general, a Group is an assemblage of vessels into a specific task command. That is, a
Group is created to perform a specific function, which could either be a permanent or
temporary assemblage of vessels of differing classes and types. As a rule, Groups will be
organized and designated by the Fleet Commander. However, the ships assigned to a
group will come under the command of the Group Commander. The following sections
will provide a brief description of the various Group Commands a Star Fleet vessel may
be assigned.
CARRIER GROUPS
Star Fleet Attack Carriers are not assigned to fleets or group command, but will usually
form the basis for such commands. That is, the Attack Carrier forms the basis for the
group and all other ships assigned to the group are there to support the carrier. Such
groups are called Carrier Groups, Carrier Battle Groups or simply, Battle Groups. As
such, all Star Fleet Attack Carriers will be assigned combatants and support ships in
order to form the Carrier Group, as illustrated in Figure 2a36.3. In general, Attack
Carriers do not operate singly nor are they assigned to any of the eight permanent fleets.
Currently, Star Fleet has five such Attack Carriers, all of which form the five permanent
Battle Groups. The function of these groups is to display power to a belligerent regime
and to provide an immediate strike force should trouble occur. These particular groups
were originally created in 2259 during an exercise when it was discovered that an Attack
Carrier could not attack or defend itself on its own, but in concert with other vessels.
In command of the Battle Group is the Group Commander who maintains his or her
office aboard the flagship and who is permanently embarked with the group. The Group
Commander will have a rank of Rear Admiral with the title of Commander: Battle
Group <n> and designated as COMBATGRP<n>.

VOLUME II
ATTACK GROUPS
Attack Groups are special, temporary assemblages of ships created during war-time
designed to attack enemy forces or installations. In addition, they will also be used to
support ground assault landings. Attack Groups will generally involve Ground Assault
(G-class) ships. An illustration of such a force can be seen in Figure 2a36.5.
SPECIAL TASK COMMANDS
Special Task Commands are temporary assemblages of ships or ship units designed to
perform a specific mission. A larger version of a Special Task Command is called a Task
Force, with a command organization as illustrated in Figure 2a36.6. A more detailed
treatment of a Task Force can be found in Section 3.6 of this volume. The following will
provide a sampling of some of such Task Commands.
EMERGENCY DETERRENT FORCE
An Emergency Deterrent Force or EDF is a special temporary force that is assembled

as necessary to deter invasion, or to engage an invading force until a larger force can be
assembled. They will generally be assembled from the Fleet Squadrons closest to the
action by the Fleet Commander or the Area Commander nearest the action. The
primary function of the EDF is to hold off invading forces from advancing utilizing delaying
tactics until reinforcements arrive.
ARMADAS
An Armada is essentially a grouping of two or more fleets, along with elements of Local
Forces, and will only be created and designated by the Director: Star Fleet Command
in his role as Commander-in-Chief: United Federation Defense Forces or CINCDEF
during times of galactic war. These are very large groupings of vessels organized and used
within a specific Theater of Operation (see Section 8.4).
FLAGSHIPS
In general, a Flagship is one which contains the officer in command of all the vessels
contained within the Squadron, Flotilla, Fleet, Force, or Type Command. The term
“flagship” comes from the fact that the commander who makes the ship his or her base of
operations will usually be of flag grade. As such, there may be several “flagships” within
any fleet or force depending on the number of command organizational units. Each fleet or
Force Commander will designate a flagship as his mobile base of operations, which will
usually be a Battleship or Heavy Cruiser. As such, only flag commanders will possess a
flagship. However, in the case of a Battle Group, the flagship will normally be the Attack
Carrier. In general, the flag commander in charge of any fleet, force, group or other unit
has the privilege of selecting his or her own flagship.
A flagship is not necessarily a permanent designation or assignment. For example, within

temporary organizations, such as in a Task Force, the Force Commander will choose
and designate his or her flagship for the coming operation. However, after the operation
has concluded and the force has been dissolved, the ship designated as flagship will return
to its previous duty status.

VOLUME II
STAR FLEET SHIP DISTRIBUTION
All Star Fleet ships will be assigned to one unit or another. As previously mentioned, all
Starships will be assigned to one of the eight Fleets, to one of the two Flotillas or one
of the five Battle Groups. Table 2a64.2 below provides the current distribution of ships,
by type, within the various permanent Fleets, Flotillas and Battle Groups.
Table 2a64.2
STAR FLEET SHIP DISTRIBUTION
SHIP FLEETS FLOTILLAS BATTLE GROUPS CLASS
CLASS 1
ST
2
ND RD
3 4
TH
5
TH
6
TH TH
7
TH
8 9 10 1 2 3 4 5 TOTAL
LINE COMBATANTS
AA - - - - - - - - - - 1 1 1 1 1 5
BB 1 1 1 2 2 1 2 2 - - - - - - - 12
HC 2 2 2 2 2 2 2 2 - - - - - - - 16
CC 3 3 3 3 3 3 3 3 1 1 - - - - - 26
LC 2 3 3 1 1 3 1 2 2 2 1 - 1 2 2 26
FF 4 4 5 4 4 5 4 4 - - 1 2 1 - - 38
HD 4 4 3 3 4 4 4 4 - - 2 2 2 2 2 40
DD 8 8 8 8 8 8 8 8 - - - - - - - 64
DE/EE 13 12 12 14 13 11 13 12 14 14 4 4 4 4 4 148
LINE: 37 37 37 37 37 37 37 37 17 17 9 9 9 9 9 375
FLEET SUPPORT SHIPS
SF 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 23
SL 1 2 1 2 1 1 2 1 - - - - - - - 11
SP 4 4 4 4 4 4 4 4 2 2 1 1 1 1 2 42
SR 4 4 4 4 4 4 4 4 1 1 - - - - - 34
TF 3 2 2 2 3 3 1 3 2 2 - - - - - 23
TG 2 2 3 2 2 2 3 2 2 2 - - - - - 22
SUPPORT: 16 16 16 16 16 16 16 16 8 8 2 2 2 2 3 155
TOTAL: 53 53 53 53 53 53 53 53 25 25 11 11 11 11 12 530
SPECIAL PURPOSE VESSELS
DR NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET TRANSPORTATION COMMAND 20
IT NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET OPERATIONS 5
MR NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET CONSTRUCTION COMMAND 9
SM NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET OPERATIONS 11
SV NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET EXPLORATION COMMAND 14
TR NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET TRANSPORTATION COMMAND 5
GG NOT ASSIGNED TO ANY FLEET – ASSIGNED BY STAR FLEET OPERATIONS 3
HB STAR FLEET FLAGSHIP – ASSIGNED BY STAR FLEET OPERATIONS 1
GRAND TOTAL IN FLEET: 598

VOLUME II
Figure 2a64.1
TYPICAL FLEET SQUADRON

VOLUME II
Figure 2a64.2
EXAMPLE OF ELEMENTS OF A FLEET SQUADRON ON MANEUVERS

VOLUME II
6.5 RESERVE STATUS SHIPS

Reserve status ships are those Star Fleet vessels that have been decommissioned for one
reason or another and are no longer in active service. Decommissioned ships are typically
not dismantled or scrapped, but rather placed in reserve should they be needed again or
that could be refurbished or upgraded at some future date. These vessels are no longer
commissioned ships and as such, will be removed or stricken from the Star Fleet Vessel
Register. When this occurs the commissioned name of the vessel is removed from the list
of active names and being removed, may be reassigned to a new vessel. However, the
registry number is not stricken from the Register, but remains with the ship, though it is
visibly removed from the hull of the vessel along with the commissioning and fleet service
pennants during its preparation to reserve status.
Ships that enter the Reserve Fleet will undergo special preparations before they are
parked in orbit and locked-up at the facility. The first step is the complete shutdown of all
engines and reactors, the discharge and extrication of all weapons and weapon systems,
and the evacuation of all fluids, coolants and air banks. The ships’ reactors and propulsion
systems will then be de-fueled and cleaned or scavenged of any anti-matter.
Mothballed ships will then have all their computers downloaded with only the operating
system remaining. This will allow the computers to restart when needed. All auxiliary and
supporting systems will remain intact, though their main power supplies have been
removed. In this way these ships can be reactivated at any time if it becomes necessary.
In support of the ship, equipment will be installed to maintain the vessel in a mothballed
state. A portable Pergium reactor will be installed that will provide power to keep the
batteries charged. Generally, any system that will remain active while the ship is in reserve
will receive its power from the ship’s batteries. However, the batteries must continuously
be recharged. Therefore, a portable reactor is required for this purpose.
Finally, all environmental systems will be shut down and the interior of the ship will be
exposed to the vacuum of space. This helps in preserving the ship from corrosion and
decay. To prevent moisture from condensing and freezing within vital components and
circuits heaters are placed at key locations throughout the ship and around vital electronic
components.
The organization responsible for the care and maintenance of the reserve fleet is the Star
Fleet Reserve Ships Command (RSHIPS), an organization within the Star Fleet
Construction Command. The function of RSHIPS is to manage the Reserve or
“mothball” fleet. Star Fleet ships that are no longer in use are not dismantled, but are
placed in storage at one of the three Star Fleet Reserve Ships Facilities[14] located
throughout the Federation Treaty Zone. Ships that enter the Reserve Fleet will
undergo special preparations by RSHIPS before they are parked in orbit and locked-up at
the facility. In charge of this division is the Commander: Reserve Fleet, who is usually
an officer of the Construction Corps and will typically have the rank of Commodore.

VOLUME II
RESERVE SHIP REACTIVATION
Should a reserve ship be reactivated, RSHIPS has special procedures for this purpose.
However, before a ship can be reactivated it must be refueled, which includes the refueling
of its reactors and propulsion systems. In most cases this process must be performed with
an atmosphere present throughout the ship. As an illustration, the refueling of the Main
Engines requires the manual startup and control of the containment fields required to
confine the matter and anti-matter plasma. Therefore, the first step in ship reactivation is
the restart of the environmental systems on board the ship and the introduction of air in
order to re-establish an atmosphere. This is so workers can move about the ship freely
without environmental suits. In addition, the restart will permit the HVAC (Heating,
Ventilation and Air Conditioning) system to bring the ship’s atmospheric environment
back to normal levels of temperature, pressure and humidity. This whole process normally
takes around six to twelve hours depending on the size of the ship. For very large ships,
the process will be performed in stages - activating only key decks and compartments as
necessary while keeping the others isolated.
The next step is the startup of the Impulse Engines so that the ship can function on its
own power. In general, it is the ship’s Impulse drive system that supplies the base
electrical load for any Starship. Once the ship is on its own power the portable Pergium
reactor can be shut down, dismantled and removed from the ship.
Next is the restart of the ships computer systems. In addition, computers may have to be
reprogrammed or the software upgraded with the latest versions. Up to this point, all the
initial ship systems had to be restarted manually since the automated systems were not
available. However, once the computers are back online, they can resume the automatic
control of the ship’s systems.
The next step is to startup the ship’s auxiliary systems. These are the systems that make
the water; produce the oxygen; process the waste; scrub CO2 and other gasses from the
atmosphere; generate the artificial gravity, as well as those other systems needed to keep
the ship in operating condition.
Next is the restart of the ship’s Main Engines. This process takes a considerable amount
of time as the matter and anti-matter Polymass must be preheated before the fusion
reaction can take place. The standard preheating process generally requires approximately
six hours, but for emergency restarts, may take as little as 30 minutes. However, the
restart of the Main Engines need not necessarily be accomplished at the facility. The
restart process can take place while the ship is underway on Impulse power to a repair
facility for final work and commissioning preparations.
The final step in the reactivation process is the re-commissioning of the ship. This is a
complicated process as there is always the possibility that the original commissioned name
of the vessel was reassigned to another vessel. In such situations, a new name from the
list of unassigned names will be selected. However, the vessel’s Registry Number will
still be the same as before. Upon re-commissioning the commissioning pennant and other
identification markings will be placed on the hull while in Drydock. The ship will then be
certified as spaceworthy and will leave the dock for space trials and acceptance.

VOLUME II
6.6 CURRENT STAR FLEET SHIP

ASSIGNMENTS
In this section the entire list of active Star Fleet ships will be presented, as well as their
current status, fleet, squadron and division assignments. In addition, a brief description of
their current assignment may also be provided. The table provided in this section is but a
part of the complete Star Fleet Vessel Register.
The Star Fleet Vessel Register is the apparatus required under Star Fleet Regulation
2400 to list the ship assets of Star Fleet along with their current duty assignment. The
register is essentially an electronic database located within Central Records containing all
the classes of vessels, including dates of construction and commissioning, weights and
capacities, type, speed, current location, group assignments, etc. This database is
constantly being updated as information regarding changes in vessel location and status
are received.
The Director: Star Fleet Command has direct responsibility for maintaining the Vessel
Register as required in Star Fleet Regulation 2400. However, this responsibility has
been delegated to Star Fleet Operations, specifically to Star Ship Command. The unit
specifically charged with the responsibility of maintaining the Vessel Register within Star
Ship Command is the Star Fleet Ship Requirements Section, which is principally
responsible for analyzing and determining the number, types and classes of ships needed
to maintain an effective operating force. As such, this office, in essence, establishes the
fleet.

VOLUME II

VOLUME II
Table 2a66.1
STAR FLEET SHIP ASSIGNMENTS
Registry Ship Type
Commissioned Name Status Fleet Group Squadron Current Duty Assignment
(NCC) Class Command
ELIMINATOR CLASS ATTACK CARRIERS
61 AA U.S.S. ELIMINATOR A N/A BATGRP4 N/A COMGRP 14 CLASSIFIED
62 AA U.S.S. FORMIDABLE A N/A BATGRP1 N/A COMGRP 11 CLASSIFIED
63 AA U.S.S. AMERICA A N/A BATGRP3 N/A COMGRP 13 Reserve duty in Treaty Zone
64 AA U.S.S. RESOLUTION A N/A BATGRP2 N/A COMGRP 12 CLASSIFIED
65 AA U.S.S. DETERRENT A N/A BATGRP5 N/A COMGRP 15 CLASSIFIED
CUTLASS CLASS DESTROYER ESCORTS
201 DE U.S.S. CUTLASS A N/A FLOT9 DESRON 1 FLTRON 2 Treaty Zone Patrol Duty
202 DE U.S.S. LASABRE A N/A FLOT9 DESRON 1 FLTRON 2 Treaty Zone Patrol Duty
203 DE U.S.S. SKYLARK A N/A FLOT9 DESRON 1 FLTRON 2 Treaty Zone Patrol Duty
204 DE U.S.S. NOVA A N/A FLOT10 DESRON 3 FLTRON 3 Treaty Zone Patrol Duty
205 DE U.S.S. COMET A N/A FLOT9 DESRON 1 FLTRON 2 Treaty Zone Patrol Duty
206 DE U.S.S. CHALLENGER A N/A FLOT10 DESRON 3 FLTRON 3 Treaty Zone Patrol Duty
207 DE U.S.S. DART A N/A FLOT10 DESRON 3 FLTRON 3 Treaty Zone Patrol Duty
BOUNTY CLASS SUPPLY SHIPS
TH
210 SP U.S.S. BOUNTY A 8 - SUPDIV 3 SERVRON 10
211 SP U.S.S. PROVISION A - FLOT9 SUPDIV 1 SERVRON 1 Flotilla 9 support
RD
212 SP U.S.S. PROVIDER A 3 - SUPDIV 4 SERVRON 6
213 SP U.S.S. STOCKER A - FLOT10 SUPDIV 2 SERVRON 2 Flotilla 10 support
TH
214 SP U.S.S. ABUNDANT A 8 - SUPDIV 3 SERVRON 10
215 SP U.S.S. GENEROUS A - FLOT9 SUPDIV 1 SERVRON 1 Flotilla 9 support
216 SP U.S.S. OPPORTUNE A - FLOT10 SUPDIV 2 SERVRON 2 Flotilla 10 support
ABILITY CLASS REPAIR SHIPS
266 SR U.S.S. ABILITY A - FLOT9 REPAIRDIV 11 SERVRON 1 Flotilla 9 support
267 SR U.S.S. DILIGENT A - FLOT10 REPAIRDIV 11 SERVRON 2 Flotilla 10 support
TH
268 SR U.S.S. ENHANCE A 7 - REPAIRDIV 9 SERVRON 9

VOLUME II
Table 2a66.1
STAR FLEET SHIP ASSIGNMENTS - CONTINUED
Registry Ship Type
(NCC) Class Command
NELSON CLASS CORVETTES
TH
305 EE U.S.S. NELSON A 7 - DESRON 73 FLTRON 72
306 EE U.S.S. COCHRANE A - FLOT9 DESRON 1 FLTRON 1
307 EE U.S.S. PERRY A - FLOT10 DESRON 4 FLTRON 3
ST
308 EE U.S.S. LACROSSE A 1 - DESRON 14 FLTRON 12
309 EE U.S.S. AGILITY A - FLOT10 DESRON 4 FLTRON 3
310 EE U.S.S. DASH A - FLOT9 DESRON 1 FLTRON 1
RD
311 EE U.S.S. CORONET A 3 - DESRON 30 FLTRON 35
312 EE U.S.S. PROWESS A - FLOT10 DESRON 3 FLTRON 4
TH
313 EE U.S.S. SPITFIRE A 7 - DESRON 73 FLTRON 71
314 EE U.S.S. TOMAHAWK A - FLOT9 DESRON 2 FLTRON 2
ST
315 EE U.S.S. VIXEN A 1 - DESRON 14 FLTRON 14
TH
316 EE U.S.S. AURORA A 7 - DESRON 73 FLTRON 71
RD
317 EE U.S.S. SWIFTSURE A 3 - DESRON 30 FLTRON 35
318 EE U.S.S. METEOR A - FLOT10 DESRON 3 FLTRON 4
TH
319 EE U.S.S. DESAULT A 7 - DESRON 73 FLTRON 71
TH
320 EE U.S.S. CHAPARRAL A 8 - DESRON 81 FLTRON 85
321 EE U.S.S. ASTUTE A - FLOT9 DESRON 2 FLTRON 2
ND
322 EE U.S.S. TALENT A 2 - DESRON 23 FLTRON 26
ND
323 EE U.S.S. SPITEFUL A 2 - DESRON 23 FLTRON 26
TH
324 EE U.S.S. REPEL A 8 - DESRON 81 FLTRON 85

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
NARWHAL CLASS LIGHT DESTROYERS
TH
401 LD U.S.S. NARWHAL A 7 - DESRON 72 FLTRON 72
TH
402 LD U.S.S. SKIPJACK A 6 - DESRON 63 FLTRON 62
TH
403 LD U.S.S. SCAMP A 7 - DESRON 74 FLTRON 76
ND
404 LD U.S.S. SCORPION A 2 - DESRON 20 FLTRON 21
TH
405 LD U.S.S. SARGO A 7 - DESRON 74 FLTRON 75
ND
406 LD U.S.S. SKATE A 2 - DESRON 20 FLTRON 21
TH
407 LD U.S.S. THRASHER A 7 - DESRON 75 FLTRON 75
ND
408 LD U.S.S. STURGEON A 2 - DESRON 22 FLTRON 25
TH
409 LD U.S.S. PERMIT A 6 - DESRON 63 FLTRON 62
TH
410 LD U.S.S. PLUNGER A 6 - DESRON 64 FLTRON 62
RD
411 LD U.S.S. FLASHER A 3 - DESRON 31 FLTRON 34
TH
412 LD U.S.S. NAUTILUS A 6 - DESRON 64 FLTRON 66
TH
413 LD U.S.S. GROWLER A 7 - DESRON 75 FLTRON 76
RD
414 LD U.S.S. DARTER A 3 - DESRON 31 FLTRON 36
TH
415 LD U.S.S. GRENADIER A 8 - DESRON 85 FLTRON 86
ANTARES CLASS LIGHT FREIGHTER
RD
501 TF U.S.S. ANTARES A 3 - FREIGHTDIV 5 SERVRON 6
TH
502 TF U.S.S. HURON A 8 - FREIGHTDIV 10 SERVRON 10
TH
503 TF U.S.S. ERIE A 8 - FREIGHTDIV 10 SERVRON 10
TH
504 TF U.S.S. GRIFFIN A 6 - FREIGHTDIV 7 SERVRON 8
TH
505 TF U.S.S. LAWRENCE A 5 - FREIGHTDIV 6 SERVRON 7 Base supply duty – Octant 6

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
PERSEUS CLASS DESTROYERS
TH
510 DD U.S.S. PERSEUS A 6 - DESRON 64 FLTRON 63
TH
511 DD U.S.S. SARGON A 4 - DESRON 45 FLTRON 41
TH
512 DD U.S.S. PEGASUS A 6 - DESRON 65 FLTRON 63
RD
513 DD U.S.S. POSEIDON A 3 - DESRON 32 FLTRON 32
ST
514 DD U.S.S. OLYMPUS A 1 - DESRON 14 FLTRON 15
ST
515 DD U.S.S. AEGIS A 1 - DESRON 14 FLTRON 16
ST
516 DD U.S.S. ZEUS A 1 - DESRON 15 FLTRON 13
TH
517 DD U.S.S. AMPHION A 5 - DESRON 54 FLTRON 51
ND
518 DD U.S.S. BELLEROPHON A 2 - DESRON 21 FLTRON 23
TH
519 DD U.S.S. JUPITER A 8 - DESRON 80 FLTRON 85
ND
520 DD U.S.S. NIMBUS A 2 - DESRON 20 FLTRON 24
TH
521 DD U.S.S. ACHELOUS A 5 - DESRON 54 FLTRON 53
RD
522 DD U.S.S. PHOEBUS A 3 - DESRON 33 FLTRON 31
RD
523 DD U.S.S. ELEKTRA A 3 - DESRON 30 FLTRON 31
ND
524 DD U.S.S. NEPTUNE A 2 - DESRON 22 FLTRON 22
ST
525 DD U.S.S. PERSEPHONE A 1 - DESRON 13 FLTRON 11
TH
526 DD U.S.S. CENTAUR A 4 - DESRON 41 FLTRON 43
TH
527 DD U.S.S. APOLLO A 6 - DESRON 65 FLTRON 63
TH
528 DD U.S.S. PHOENIX A 6 - DESRON 65 FLTRON 65
ST
529 DD U.S.S. ATHENA A 1 - DESRON 15 FLTRON 12

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
PALADIN CLASS DESTROYERS
TH
541 DD U.S.S. PALADIN A 8 - DESRON 82 FLTRON 82
ND
542 DD U.S.S. INTENSION A 2 - DESRON 24 FLTRON 25
ND
543 DD U.S.S. KNORR A 2 - DESRON 25 FLTRON 24
TH
544 DD U.S.S. ANTIOCH A 8 - DESRON 83 FLTRON 82
RD
547 DD U.S.S. ALEXANDRIA A 3 - DESRON 34 FLTRON 34
ND
548 DD U.S.S. MEMPHIS A 2 - DESRON 23 FLTRON 26
TH
551 DD U.S.S. LING A 4 - DESRON 45 FLTRON 45
TH
552 DD U.S.S. MAVERICK A 4 - DESRON 44 FLTRON 44
RD
553 DD U.S.S. PROCYON A 3 - DESRON 35 FLTRON 35
TH
554 DD U.S.S. EQUALIZER A 5 - DESRON 50 FLTRON 54
TH
555 DD U.S.S. RETRIBUTION A 4 - DESRON 45 FLTRON 44
ND
557 DD U.S.S. RESTITUTION A 2 - DESRON 24 FLTRON 21
ST
558 DD U.S.S. VINDICTIVE A 1 - DESRON 11 FLTRON 14
TH
559 DD U.S.S. TALON A 4 - DESRON 45 FLTRON 45
ND
560 DD U.S.S. INTERNECINE A 2 - DESRON 25 FLTRON 23
ST
561 DD U.S.S. PREDATOR A 1 - DESRON 10 FLTRON 15
ST
562 DD U.S.S. REFORMER A 1 - DESRON 14 FLTRON 11
TH
563 DD U.S.S. VENDETTA A 8 - DESRON 84 FLTRON 81
TH
564 DD U.S.S. IMPETUOUS A 5 - DESRON 54 FLTRON 54
TH
565 DD U.S.S. INDOMABLE A 8 - DESRON 85 FLTRON 81

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
HERMES CLASS DESTROYER ESCORT
574 DE U.S.S. HERMES A - BATGRP5 DESRON 9 FLTRON 10
575 DE U.S.S. ASCENSION A - BATGRP5 DESRON 9 FLTRON 10
580 DE U.S.S. CENTURION A - FLOT9 DESRON 1 FLTRON 1
RD
581 DE U.S.S. HECTOR A 3 - DESRON 34 FLTRON 31
RD
582 DE U.S.S. DARIUS A 3 - DESRON 34 FLTRON 31
TH
583 DE U.S.S. ALEXANDER A 5 - DESRON 50 FLTRON 53
TH
584 DE U.S.S. LEONIDES A 4 - DESRON 44 FLTRON 42
585 DE U.S.S. XERXES A - FLOT10 DESRON 3 FLTRON 4
586 DE U.S.S. PHALANX A - FLOT10 DESRON 3 FLTRON 4
587 DE U.S.S. AETNA A - FLOT9 DESRON 2 FLTRON 1
TH
588 DE U.S.S. AGAMEMNON A 6 - DESRON 60 FLTRON 64
RD
589 DE U.S.S. THESEUS A 3 - DESRON 32 FLTRON 36
TH
590 DE U.S.S. ODYSSEUS A 4 - DESRON 44 FLTRON 42
ND
591 DE U.S.S. ACHILLES A 2 - DESRON 21 FLTRON 22
ND
592 DE U.S.S. AJAX A 2 - DESRON 21 FLTRON 24
TH
593 DE U.S.S. NIKE A 6 - DESRON 60 FLTRON 64
594 DE U.S.S. PERSHING A - FLOT10 DESRON 4 FLTRON 3
595 DE U.S.S. SPARTACUS A - FLOT9 DESRON 2 FLTRON 1
596 DE U.S.S. ASTERION A - FLOT9 DESRON 2 FLTRON 1
TH
597 DE U.S.S. THERMOPYLAE A 5 - DESRON 50 FLTRON 53
598 DE U.S.S. MARATHON A - FLOT10 DESRON 4 FLTRON 4
599 DE U.S.S. HANNIBAL A - FLOT10 DESRON 4 FLTRON 4

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
SINCLAIR CLASS FUEL SHIP
TH
601 SF U.S.S. SINCLAIR A 8 - SUPDIV 11 SERVRON 10
602 SF U.S.S. OXLEY A - BATGRP4 SUPDIV 23 SERVRON 15 Group supply duty
TH
603 SF U.S.S. ARCO A 4 - SUPDIV 17 SERVRON 5
604 SF U.S.S. PROMETHIUS A - FLOT10 SUPDIV 2 SERVRON 2 Flotilla 10 support
ND
605 SF U.S.S. IONIA A 2 - SUPDIV 14 SERVRON 4
TH
606 SF U.S.S. HALCYON A 6 - SUPDIV 16 SERVRON 8
ND
607 SF U.S.S. DEARBORN A 2 - SUPDIV 14 SERVRON 4
TH
608 SF U.S.S. LANSING A 5 - SUPDIV 13 SERVRON 7
RD
609 SF U.S.S. PHILLIPS A 3 - SUPDIV 15 SERVRON 6
TH
610 SF U.S.S. AUCKLAND A 7 - SUPDIV 18 SERVRON 9
ST
611 SF U.S.S. COSWORTH A 1 - SUPDIV 12 SERVRON 3
TH
612 SF U.S.S. HUXLEY A 4 - SUPDIV 17 SERVRON 5
613 SF U.S.S. SYLVANIA A - BATGRP5 SUPDIV 19 SERVRON 14 Group supply duty
TH
614 SF U.S.S. LANCASTER A 6 - SUPDIV 16 SERVRON 8
615 SF U.S.S. OMICRON A - FLOT9 SUPDIV 1 SERVRON 1 Flotilla 9 support
TH
616 SF U.S.S. PEABODY A 5 - SUPDIV 13 SERVRON 7
TH
617 SF U.S.S. TARPON A 7 - SUPDIV 18 SERVRON 9
TH
618 SF U.S.S. AEOLUS A 8 - SUPDIV 11 SERVRON 10

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
EXPLORER CLASS SURVEY/EXPORATION VESSEL
TH
632 SV U.S.S. EXPLORER A 4 N/A SURV1 COMGRP 4 Space exploration
TH
635 SV U.S.S. DISCOVERY A 8 N/A SURV4 COMGRP 8 Base and station evaluation
RD
636 SV U.S.S. SURVEYOR A 3 N/A SURV2 COMGRP 3 Planetary survey vessel
TH
637 SV U.S.S. PIONEER A 4 N/A SURV4 COMGRP 4 Space exploration
TH
638 SV U.S.S. GRISSOM A 7 N/A SURV3 COMGRP 7 Space survey and mapping
ND
639 SV U.S.S. STARGAZER A 2 N/A SURV1 COMGRP 2 Space exploration
TH
641 SV U.S.S. ARMSTRONG A 5 N/A SURV3 COMGRP 5 Base and station evaluation
RD
642 SV U.S.S. VOYAGER A 3 N/A SURV4 COMGRP 3 Space exploration
ST
643 SV U.S.S. CARPENTER A 1 N/A SURV2 COMGRP 1 Planetary survey vessel
TH
647 SV U.S.S. HORIZON A 8 N/A SURV2 COMGRP 8 Planetary survey vessel
RD
648 SV U.S.S. SEARCHER A 3 N/A SURV1 COMGRP 3 Space survey and mapping
TH
649 SV U.S.S. TRAILBLAZER A 7 N/A SURV3 COMGRP 7 Space survey and mapping
TH
651 SV U.S.S. MARCO POLO A 6 N/A SURV1 COMGRP 6 Planetary survey vessel
TH
652 SV U.S.S. SHEPARD A 7 N/A SURV4 COMGRP 7 Colonization vessel
ALBANY CLASS CRUISER
660 CC U.S.S. ALBANY A - FLOT9 CRUDIV 9 COMGRP 9 Flagship Flotilla 9
TH
661 CC U.S.S. DALLAS A 4 - CRUDIV 42 FLTRON 41 Flagship to Fleet Squadron 41
TH
662 CC U.S.S. SUSSEX A 5 - CRUDIV 52 FLTRON 51 Flagship to Fleet Squadron 51
TH
663 CC U.S.S. BOISE A 4 - CRUDIV 42 FLTRON 42 Flagship to Fleet Squadron 42
TH
664 CC U.S.S. MONARCH A 4 - CRUDIV 42 FLTRON 43 Flagship to Fleet Squadron 43
665 CC U.S.S. CENTURY A - FLOT10 CRUDIV 10 COMGRP 10 Flagship Flotilla 10
TH
666 CC U.S.S. VICTORIA A 7 - CRUDIV 72 FLTRON 71 Flagship to Fleet Squadron 71
TH
667 CC U.S.S. BRITANNIA A 6 - CRUDIV 62 FLTRON 61 Flagship to Fleet Squadron 61
TH
668 CC U.S.S. ATLANTIA A 7 - CRUDIV 72 FLTRON 72 Flagship to Fleet Squadron 72
TH
669 CC U.S.S. GALACTICA A 7 - CRUDIV 72 FLTRON 73 Flagship to Fleet Squadron 73

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
DEFIANT CLASS SHORT-DECK FRIGATE
TH
700 FF U.S.S. DEFIANT A 6 - CRUDIV 64 FLTRON 64
TH
701 FF U.S.S. DETROIT A 8 - CRUDIV 83 FLTRON 84
TH
702 FF U.S.S. CHICAGO A 6 - CRUDIV 64 FLTRON 64
TH
703 FF U.S.S. TRIUMPHANT A 8 - CRUDIV 83 FLTRON 86
TH
704 FF U.S.S. KONGO A 5 - CRUDIV 53 FLTRON 55
TH
705 FF U.S.S. REVENGE A 5 - CRUDIV 53 FLTRON 53
TH
706 FF U.S.S. COMPETENT A 8 - CRUDIV 83 FLTRON 83
ST
707 FF U.S.S. ABSOLUTION A 1 - CRUDIV 13 FLTRON 13
TH
708 FF U.S.S. CONSORTIUM A 4 - CRUDIV 43 FLTRON 42
ND
709 FF U.S.S. EMINENCE A 2 - CRUDIV 23 FLTRON 25
TH
710 FF U.S.S. TRENCHANT A 6 - CRUDIV 64 FLTRON 61
TH
711 FF U.S.S. INDELIBLE A 5 - CRUDIV 53 FLTRON 54
RD
712 FF U.S.S. SABRE A 3 - CRUDIV 34 FLTRON 31
TH
713 FF U.S.S. ALDEBARAN A 7 - CRUDIV 73 FLTRON 76
TH
714 FF U.S.S. REGAL A 8 - CRUDIV 83 FLTRON 85

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
WRIGHT CLASS DESTROYER
751 HD U.S.S. WRIGHT A - BATGRP2 DESRON 5 FLTRON 7
TH
752 HD U.S.S. KREIGER A 4 - DESRON 40 FLTRON 42
TH
753 HD U.S.S. ELASS A 4 - DESRON 41 FLTRON 46
754 HD U.S.S. SWIFT A - BATGRP2 DESRON 5 FLTRON 7
TH
755 HD U.S.S. ELAN A 4 - DESRON 42 FLTRON 46
TH
756 HD U.S.S. NEWCOMB A 7 - DESRON 70 FLTRON 73
TH
757 HD U.S.S. ELITE A 7 - DESRON 71 FLTRON 71
TH
758 HD U.S.S. EUROPA A 6 - DESRON 60 FLTRON 62
TH
759 HD U.S.S. MEREK A 8 - DESRON 80 FLTRON 85
TH
760 HD U.S.S. PELTON A 8 - DESRON 81 FLTRON 83
TH
761 HD U.S.S. ECLAT A 6 - DESRON 61 FLTRON 62
TH
762 HD U.S.S. MERCURY A 8 - DESRON 82 FLTRON 84
TH
763 HD U.S.S. PEERLESS A 5 - DESRON 50 FLTRON 56
TH
764 HD U.S.S. VANTAGE A 5 - DESRON 51 FLTRON 56
TH
765 HD U.S.S. VANQUISH A 8 - DESRON 83 FLTRON 86
TH
766 HD U.S.S. LAGONDA A 5 - DESRON 52 FLTRON 52
TH
767 HD U.S.S. THUNDERBOLT A 7 - DESRON 72 FLTRON 72
TH
768 HD U.S.S. CORVAIR A 5 - DESRON 53 FLTRON 55
TH
769 HD U.S.S. ESPRIT A 6 - DESRON 62 FLTRON 63
TH
770 HD U.S.S. CONVERSE A 6 - DESRON 63 FLTRON 63

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
ERIDANUS CLASS DESTROYER ESCORT
TH
785 DE U.S.S. ERIDANUS A 8 - DESRON 82 FLTRON 81
ST
786 DE U.S.S. ALPHA CENTAURI A 1 - DESRON 15 FLTRON 12
ST
787 DE U.S.S. PROTECTOR A 1 - DESRON 13 FLTRON 14
TH
788 DE U.S.S. CONCORDIUM A 4 - DESRON 41 FLTRON 45
TH
789 DE U.S.S. VALOR A 5 - DESRON 51 FLTRON 51
790 DE U.S.S. GATLING A - FLOT9 DESRON 2 FLTRON 2
TH
791 DE U.S.S. HONORABLE A 4 - DESRON 41 FLTRON 43
TH
792 DE U.S.S. ARCTURUS A 8 - DESRON 80 FLTRON 81
793 DE U.S.S. SECRETARIAT A - FLOT10 DESRON 4 FLTRON 3
TH
794 DE U.S.S. DEFENDER A 5 - DESRON 51 FLTRON 51
RD
795 DE U.S.S. OBERON A 3 - DESRON 35 FLTRON 34
796 DE U.S.S. TANTALUS A - FLOT10 DESRON 4 FLTRON 4
TH
797 DE U.S.S. HYPERION A 8 - DESRON 80 FLTRON 82
ST
798 DE U.S.S. THASOS A 1 - DESRON 13 FLTRON 13
RD
799 DE U.S.S. VALERON A 3 - DESRON 33 FLTRON 33
RD
800 DE U.S.S. PHOBOS A 3 - DESRON 33 FLTRON 33
801 DE U.S.S. ORPHEUS A - BATGRP4 DESRON 8 FLTRON 9
TH
802 DE U.S.S. WRAITH A 8 - DESRON 82 FLTRON 82
803 DE U.S.S. ACADIA A - FLOT9 DESRON 2 FLTRON 1
804 DE U.S.S. CALLISTO A - BATGRP4 DESRON 8 FLTRON 9

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
ARIES CLASS DESTROYER
TH
905 DD U.S.S. ARIES A 5 - DESRON 55 FLTRON 53
TH
907 DD U.S.S. ORION A 4 - DESRON 43 FLTRON 46
TH
908 DD U.S.S. TAURUS A 4 - DESRON 44 FLTRON 46
TH
911 DD U.S.S. POLARIS A 6 - DESRON 60 FLTRON 65
TH
912 DD U.S.S. SIRIUS A 5 - DESRON 55 FLTRON 56
TH
914 DD U.S.S. TITAN A 6 - DESRON 62 FLTRON 65
TH
917 DF U.S.S. ANDROMEDA A 7 - DESRON 71 FLTRON 74
TH
921 DF U.S.S. PROTEUS A 6 - DESRON 63 FLTRON 66
TH
928 DD U.S.S. CYGNUS A 6 - DESRON 64 FLTRON 66
TH
945 DF U.S.S. ALTAIR A 7 - DESRON 71 FLTRON 74
TH
946 DD U.S.S. CASSIOPEIA A 7 - DESRON 72 FLTRON 74
TH
947 DD U.S.S. HYADES A 5 - DESRON 54 FLTRON 55
TH
948 DD U.S.S. VIRGO A 5 - DESRON 55 FLTRON 55
TH
949 DD U.S.S. PLEIADES A 7 - DESRON 72 FLTRON 74

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
KNIGHT CLASS DESTROYER ESCORTS
TH
951 DE U.S.S. KNIGHT A 7 - DESRON 71 FLTRON 72
TH
952 DE U.S.S. GALAHAD A 4 - DESRON 40 FLTRON 43
TH
953 DE U.S.S. PERCIVALE A 4 - DESRON 40 FLTRON 43
TH
954 DE U.S.S. MORDRED A 5 - DESRON 52 FLTRON 55
ST
955 DE U.S.S. SAGAMORE A 1 - DESRON 15 FLTRON 16
TH
956 DE U.S.S. GAWAIN A 5 - DESRON 53 FLTRON 54
TH
957 DE U.S.S. LANCELOT A 7 - DESRON 70 FLTRON 73
TH
958 DE U.S.S. IVANHOE A 5 - DESRON 52 FLTRON 54
TH
959 DE U.S.S. HASTINGS A 7 - DESRON 70 FLTRON 73
TH
960 DE U.S.S. TEMPLAR A 4 - DESRON 40 FLTRON 41
ND
961 DE U.S.S. SCEPTRE A 2 - DESRON 22 FLTRON 23
TH
962 DE U.S.S. FURIOUS A 4 - DESRON 43 FLTRON 42
ND
963 DE U.S.S. LACONIA A 2 - DESRON 24 FLTRON 22
ST
964 DE U.S.S. RAPIER A 1 - DESRON 10 FLTRON 14
TH
965 DE U.S.S. ARTEMIS A 7 - DESRON 75 FLTRON 73
966 DE U.S.S. VENTURE A - BATGRP2 DESRON 5 FLTRON 7
967 DE U.S.S. LANCER A - BATGRP2 DESRON 5 FLTRON 7
ST
968 DE U.S.S. HAWK A 1 - DESRON 10 FLTRON 12
969 DE U.S.S. WARRIOR A - BATGRP3 DESRON 6 FLTRON 8
970 DE U.S.S. SHRIKE A - BATGRP3 DESRON 6 FLTRON 8

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
KNOX CLASS DESTROYER ESCORT
TH
1040 DE U.S.S. KNOX A 6 - DESRON 61 FLTRON 61
1041 DE U.S.S. LOCKWOOD A - BATGRP3 DESRON 6 FLTRON 8
1042 DE U.S.S. SHIELDS A - BATGRP3 DESRON 6 FLTRON 8
ST
1043 DE U.S.S. VREELAND A 1 - DESRON 11 FLTRON 11
TH
1044 DE U.S.S. BADGER A 5 - DESRON 53 FLTRON 56
TH
1045 DE U.S.S. HOLT A 5 - DESRON 53 FLTRON 56
RD
1046 DE U.S.S. FANNING A 3 - DESRON 35 FLTRON 32
TH
1047 DE U.S.S. HEWES A 5 - DESRON 55 FLTRON 52
ST
1048 DE U.S.S. AUSTIN A 1 - DESRON 1 FLTRON 13
1049 DE U.S.S. HUNLEY A - BATGRP2 DESRON 5 FLTRON 7
RD
1050 DE U.S.S. BEDFORD A 3 - DESRON 31 FLTRON 32
1051 DE U.S.S. FAIRFAX A - BATGRP2 DESRON 5 FLTRON 7

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
TRITON CLASS LIGHT CRUISER
TH
1052 LC U.S.S. TRITON A 4 - CRUDIV 43 FLTRON 41
ST
1053 LC U.S.S. WASP A 1 - CRUDIV 13 FLTRON 15
1057 LC U.S.S. TALOS A - FLOT9 CRUDIV 9 FLTRON 1 Flagship to Squadron 1
RD
1072 LC U.S.S. TRIDENT A 3 - CRUDIV 33 FLTRON 34 Flagship to Fleet Squadron 34
1073 LC U.S.S. VICTORY A - BATGRP1 CRUDIV 5 FLTRON 6
1074 LC U.S.S. ESTEEM A - BATGRP3 CRUDIV 7 FLTRON 8
ND
1075 LC U.S.S. RELENTLESS A 2 - CRUDIV 23 FLTRON 23
1077 LC U.S.S. MAWLER A - FLOT10 CRUDIV 10 FLTRON 4 Flagship to Squadron 4
1079 LC U.S.S. VALCOUR A - FLOT10 CRUDIV 10 FLTRON 3 Flagship to Squadron 3
ND
1080 LC U.S.S. INFLEXIBLE A 2 - CRUDIV 23 FLTRON 26
TH
1081 LC U.S.S. SENATOR A 5 - CRUDIV 53 FLTRON 51
1082 LC U.S.S. HALSEY A - FLOT9 CRUDIV 9 FLTRON 2 Flagship to Squadron 2
TH
1083 LC U.S.S. PERSISTENT A 7 - CRUDIV 73 FLTRON 75
ST
1084 LC U.S.S. NIMITZ A 1 - CRUDIV 13 FLTRON 15 Flagship to Fleet Squadron 15
1085 LC U.S.S. YAMATO A - BATGRP5 CRUDIV 8 FLTRON 10
1093 LC U.S.S. CITATION A - BATGRP5 CRUDIV 8 FLTRON 10

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
CRUSADER CLASS DESTROYER
RD
1100 DD U.S.S. CRUSADER A 3 - DESRON 33 FLTRON 33
RD
1101 DD U.S.S. CORSAIR A 3 - DESRON 34 FLTRON 36
RD
1102 DD U.S.S. INTRUDER A 3 - DESRON 35 FLTRON 32
TH
1103 DD U.S.S. PROWLER A 8 - DESRON 84 FLTRON 86
TH
1104 DD U.S.S. HUSTLER A 7 - DESRON 74 FLTRON 75
TH
1105 DD U.S.S. VIGILANTE A 7 - DESRON 75 FLTRON 75
TH
1106 DD U.S.S. PHANTOM A 7 - DESRON 74 FLTRON 76
TH
1107 DD U.S.S. MIRAGE A 7 - DESRON 70 FLTRON 76
TH
1108 DD U.S.S. FALCON A 8 - DESRON 81 FLTRON 84
TH
1109 DD U.S.S. VALKYRIE A 8 - DESRON 85 FLTRON 83

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
FLETCHER CLASS HEAVY DESTROYER
TH
1112 HD U.S.S. FLETCHER A 7 - DESRON 73 FLTRON 74
ST
1113 HD U.S.S. SCHOFIELD A 1 - DESRON 10 FLTRON 14
RD
1114 HD U.S.S. PRESCOTT A 3 - DESRON 30 FLTRON 36
ND
1115 HD U.S.S. TIRPITZ A 2 - DESRON 20 FLTRON 26
1116 HD U.S.S. SHARP A - BATGRP1 DESRON 7 FLTRON 6
ND
1117 HD U.S.S. COMMENDABLE A 2 - DESRON 21 FLTRON 22
1118 HD U.S.S. TRIBUNE A - BATGRP1 DESRON 7 FLTRON 6
1119 HD U.S.S. RENITENT A - BATGRP5 DESRON 9 FLTRON 10
ST
1120 HD U.S.S. ORISKANY A 1 - DESRON 11 FLTRON 15
ST
1121 HD U.S.S. ENGAGE A 1 - DESRON 12 FLTRON 11
1122 HD U.S.S. MERRIMACK A - BATGRP5 DESRON 9 FLTRON 10
RD
1123 HD U.S.S. PRESTIGE A 3 - DESRON 31 FLTRON 35
RD
1124 HD U.S.S. FORTITUDE A 3 - DESRON 32 FLTRON 33
1125 HD U.S.S. IMPERTINENT A - BATGRP3 DESRON 6 FLTRON 8
ND
1126 HD U.S.S. TRIUMPH A 2 - DESRON 22 FLTRON 21
1127 HD U.S.S. EXPLOIT A - BATGRP3 DESRON 6 FLTRON 8
ST
1128 HD U.S.S. LITTORIO A 1 - DESRON 13 FLTRON 13
ND
1129 HD U.S.S. INEXORABLE A 2 - DESRON 23 FLTRON 25
1130 HD U.S.S. KODIAK A - BATGRP4 DESRON 8 FLTRON 9
1131 HD U.S.S. DISCORDIA A - BATGRP4 DESRON 8 FLTRON 9

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
RESERVE CLASS SUPPLY SHIP
TH
1141 SP U.S.S. RESERVE A 8 - SUPDIV 3 SERVRON 10
TH
1142 SP U.S.S. PLENTIFUL A 5 - SUPDIV 8 SERVRON 7
TH
1143 SP U.S.S. BOUNTIFUL A 6 - SUPDIV 10 SERVRON 8
TH
1144 SP U.S.S. FORTIFY A 7 - SUPDIV 9 SERVRON 9
TH
1145 SP U.S.S. MUNIFICENT A 7 - SUPDIV 9 SERVRON 9
RD
1146 SP U.S.S. NECESSITY A 3 - SUPDIV 4 SERVRON 6
RD
1147 SP U.S.S. RATION A 3 - SUPDIV 4 SERVRON 6
TH
1148 SP U.S.S. ENHANCE A 6 - SUPDIV 10 SERVRON 8
VANGUARD CLASS INTELLIGENCE/COMMAND SHIP
TH
1271 IT U.S.S. VANGUARD A 5 N/A N/A COMGRP 5 CLASSIFIED
ST
1272 IT U.S.S. SENTINEL A 1 N/A N/A COMGRP 1 CLASSIFIED
ND
1273 IT U.S.S. GUARDIAN A 2 N/A N/A COMGRP 2 CLASSIFIED
TH
1274 IT U.S.S. VIGILANT A 8 N/A N/A COMGRP 8 CLASSIFIED
TH
1275 IT U.S.S. HAWKEYE A 6 N/A N/A COMGRP 6 CLASSIFIED
VULCAN CLASS REPAIR SHIP
TH
1276 SR U.S.S. VULCAN A 6 - REPAIRDIV 6 SERVRON 8 Docked at SSN for ship repair duty.
TH
1277 SR U.S.S. RIGEL A 8 - REPAIRDIV 8 SERVRON 10
ST
1278 SR U.S.S. SPERRY A 1 - REPAIRDIV 4 SERVRON 3
TH
1279 SR U.S.S. FORGER A 8 - REPAIRDIV 8 SERVRON 10 Assigned to FLTRON

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
CANOPUS CLASS REPAIR SHIP
TH
1280 SR U.S.S. CANOPUS A 7 - REPAIRDIV 9 SERVRON 9
TH
1281 SR U.S.S. FULTON A 6 - REPAIRDIV 6 SERVRON 8
TH
1282 SR U.S.S. PRESERVER A 8 - REPAIRDIV 8 SERVRON 10
ST
1283 SR U.S.S. LANGLEY A 1 - REPAIRDIV 4 SERVRON 3
ST
1284 SR U.S.S. DAEDALAS A 1 - REPAIRDIV 4 SERVRON 3
TH
1291 SR U.S.S. SWAGER A 4 - REPAIRDIV 1 SERVRON 5
RD
1292 SR U.S.S. LIPSCOMB A 3 - REPAIRDIV 5 SERVRON 6
ND
1293 SR U.S.S. INGRAM A 2 - REPAIRDIV 3 SERVRON 4 Fleet service duty – FLTRON 21
TH
1294 SR U.S.S. EXCEL A 4 - REPAIRDIV 1 SERVRON 5
TH
1295 SR U.S.S. BREMERTON A 5 - REPAIRDIV 2 SERVRON 7
RD
1296 SR U.S.S. WAINWRIGHT A 3 - REPAIRDIV 5 SERVRON 6
TH
1297 SR U.S.S. LYCOMING A 5 - REPAIRDIV 2 SERVRON 7
ND
1298 SR U.S.S. REDSTONE A 2 - REPAIRDIV 3 SERVRON 4
TH
1299 SR U.S.S. ASSURANCE A 6 - REPAIRDIV 6 SERVRON 8
TH
1300 SR U.S.S. INGALLS A 7 - REPAIRDIV 9 SERVRON 9

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
HUDSON CLASS FREIGHTER
1306 TF U.S.S. HUDSON A 1ST - FREIGHTDIV 11 SERVRON 3
1307 TF U.S.S. BEAGLE A 5TH - FREIGHTDIV 6 SERVRON 7 Equipment hauling and colony support
1308 TF U.S.S. VALLEY FORGE A 3RD - FREIGHTDIV 5 SERVRON 6
1309 TF U.S.S. DEPENDABLE A 1ST - FREIGHTDIV 11 SERVRON 3
TH
1310 TF U.S.S. GEARING A 5 - FREIGHTDIV 6 SERVRON 7
1311 TF U.S.S. NASSAU A 6TH - FREIGHTDIV 7 SERVRON 8
1312 TF U.S.S. TRAVERSE A 7TH - N/A SERVRON 9 General supply duty – Octant 7
1313 TF U.S.S. DIERDRE A 8TH - FREIGHTDIV 10 SERVRON 10
1314 TF U.S.S. FREUHAUF A FLOT9 FREIGHTDIV 1 SERVRON 1 Treaty Zone base supply duty
1315 TF U.S.S. COMSTOCK A FLOT9 FREIGHTDIV 1 SERVRON 1 Treaty Zone station cargo supply duty
F1327 TFX U.S.S. TA YUN-HO A Test model
VIKING CLASS FUEL SHIP
1316 SF U.S.S. VIKING A - BATGRP3 SUPDIV 21 SERVRON 12 Group supply duty
1317 SF U.S.S. TROJAN A - BATGRP2 SUPDIV 22 SERVRON 13 Group supply duty
1318 SF U.S.S. QUASAR A 1ST - SUPDIV 12 SERVRON 3
1319 SF U.S.S. ROCKWELL A - BATGRP1 SUPDIV 20 SERVRON 11 Group supply duty
1320 SF U.S.S. JUNEAU A 3RD - SUPDIV 15 SERVRON 6

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
CONSOLATION CLASS HOSPITAL SHIP
1321 HS U.S.S. CONSOLATION A 3RD N/A N/A COMGRP 3 Standard fleet medical duty
1322 HS U.S.S. TRANQUILITY A 1ST N/A N/A COMGRP 1 Standard fleet medical duty
1323 HS U.S.S. CONVALESCE A 5TH N/A N/A COMGRP 5 Standard fleet medical duty
1324 HS U.S.S. OCEANIS A 4TH N/A N/A COMGRP 4 Standard fleet medical duty
TH
1325 HS U.S.S. SANCTUARY A 6 N/A N/A COMGRP 6 Standard fleet medical duty
1326 HS U.S.S. HAVEN A 5TH N/A N/A COMGRP 5 Standard fleet medical duty
1328 HS U.S.S. COMFORT A 1ST N/A N/A COMGRP 1 Federation Treaty Zone
1329 HS U.S.S. SERENITY A 6TH N/A N/A COMGRP 6 Standard fleet medical duty
1330 HS U.S.S. REFUGE A 2ND N/A N/A COMGRP 2 Standard fleet medical duty
1331 HS U.S.S. SOLACE A 2ND N/A N/A COMGRP 2 Standard fleet medical duty
TH
1332 HS U.S.S. REASSURANCE A 8 N/A N/A COMGRP 8 Standard fleet medical duty
LEHRNER CLASS LABORATORY SHIP
1371 SL U.S.S. LEHRNER A 4TH N/A N/A COMGRP 4 Fleet scientific duty
1372 SL U.S.S. INFINITY A 7TH N/A N/A COMGRP 7 Scientific study of gravitational fields
1373 SL U.S.S. ABELIAN A 3RD N/A N/A COMGRP 3 Fleet scientific duty
TH
1374 SL U.S.S. OBSERVATORY A 8 N/A N/A COMGRP 8 Space structure studies
1375 SL U.S.S. GALAXY A 2ND N/A N/A COMGRP 2 Scientific study of solar phenomenon
1376 SL U.S.S. CURIOSITY A 7TH N/A N/A COMGRP 7 Fleet scientific duty
1377 SL U.S.S. DEDUCTION A 1ST N/A N/A COMGRP 1 Fleet scientific duty
1378 SL U.S.S. INTUITION A 4TH N/A N/A COMGRP 4 Fleet scientific duty
1379 SL U.S.S. EXAMINATION A 6TH N/A N/A COMGRP 6 Planetary survey duty
TH
1380 SL U.S.S. EXPERIMENTOR A 5 N/A N/A COMGRP 5 Scientific study of solar phenomenon
1381 SL U.S.S. BEAKER A 2ND N/A N/A COMGRP 2 Fleet scientific duty

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
CONSTITUTION CLASS CRUISER
1700 CC U.S.S. CONSTITUTION X - - - - Stricken
RD
1701 CC U.S.S. ENTERPRISE A 3 - CRUDIV 32 FLTRON 33 Five-year patrol duty
RD
1702 CC U.S.S. POTEMKIN A 3 - CRUDIV 32 FLTRON 33 Flagship to Fleet Squadron 33
RD
1703 CC U.S.S. HOOD A 3 - CRUDIV 32 FLTRON 35 Flagship to Fleet Squadron 35
TH
1704 CC U.S.S. EXCALIBUR A 5 - CRUDIV 52 FLTRON 52 Flagship to Fleet Squadron 52
TH
1705 CC U.S.S. CONSTITUTION A 6 - CRUDIV 62 FLTRON 65 Flagship to Fleet Squadron 65
TH
1706 CC U.S.S. EXETER A 6 - CRUDIV 62 FLTRON 66 Flagship to Fleet Squadron 66
ST
1707 CC U.S.S. REPUBLIC A 1 - CRUDIV 12 FLTRON 14 Flagship to Fleet Squadron 14
ND
1708 CC U.S.S. VALIANT A 2 - CRUDIV 22 FLTRON 25 Flagship to Fleet Squadron 25
ST
1709 CC U.S.S. LEXINGTON A 1 - CRUDIV 12 FLTRON 12 Flagship to Fleet Squadron 12
ST
1710 CC U.S.S. CONSTELLATION A 1 - CRUDIV 12 FLTRON 16 Flagship to Fleet Squadron 16
TH
1711 CC U.S.S. INTREPID A 5 - CRUDIV 52 FLTRON 55 Flagship to Fleet Squadron 55
TH
1712 CC U.S.S. YORKTOWN A 8 - CRUDIV 82 FLTRON 83 Flagship to Fleet Squadron 83
EXCELLSIOR CLASS HEAVY CRUISER
TH
1713 HC U.S.S. EXCELLSIOR A 6 - CRUDIV 61 FLTRON 62 Flagship to Fleet Squadron 62
TH
1714 HC U.S.S. COLUMBIA A 8 - CRUDIV 81 FLTRON 81 Flagship to Fleet Squadron 81
TH
1715 HC U.S.S. DEFIANCE A 6 - CRUDIV 61 FLTRON 63 Flagship to Fleet Squadron 63
RD
1716 HC U.S.S. ESSEX A 3 - CRUDIV 31 FLTRON 31 Flagship to Fleet Squadron 31
TH
1717 HC U.S.S. INDEPENDENCE A 5 - CRUDIV 51 FLTRON 53 Flagship to Fleet Squadron 53
TH
1718 HC U.S.S. ENDEAVOR A 8 - CRUDIV 81 FLTRON 82 Flagship to Fleet Squadron 82
ALLIANCE CLASS STRIKE CRUISER
TH
1719 CC U.S.S. ALLIANCE A 8 - CRUDIV 82 FLTRON 84 Flagship to Fleet Squadron 84
ND
1720 CC U.S.S. REPRISE A 2 - CRUDIV 22 FLTRON 24 Flagship to Fleet Squadron 24
ND
1721 CC U.S.S. INDOMITABLE A 2 - CRUDIV 22 FLTRON 23 Flagship to Fleet Squadron 23
TH
1722 CC U.S.S. VINDICATOR A 8 - CRUDIV 82 FLTRON 86 Flagship to Fleet Squadron 86

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
MONITOR CLASS LIGHT CRUISER
TH
1723 LC U.S.S. MONITOR A 6 - CRUDIV 63 FLTRON 64
TH
1724 LC U.S.S. IMPALA A 8 - CRUDIV 83 FLTRON 81
TH
1725 LC U.S.S. CORINTHIAN A 6 - CRUDIV 63 FLTRON 64 Flagship to Fleet Squadron 64
RD
1726 LC U.S.S. FARRAGUT A 3 - CRUDIV 33 FLTRON 36 Flagship to Fleet Squadron 36
1727 LC U.S.S. SARATOGA A - BATGRP4 CRUDIV 4 FLTRON 9 Flagship to Fleet Squadron 9
ND
1728 LC U.S.S. CONGRESS A 2 - CRUDIV 23 FLTRON 26 Flagship to Fleet Squadron 26
RD
1729 LC U.S.S. HORNET A 3 - CRUDIV 33 FLTRON 36
TH
1730 LC U.S.S. RANGER A 6 - CRUDIV 63 FLTRON 61
1731 LC U.S.S. PROVIDENCE A - BATGRP4 CRUDIV 4 FLTRON 9
TH
1732 LC U.S.S. CONQUEST A 8 - CRUDIV 83 FLTRON 82
ENDURANCE CLASS HEAVY CRUISER
ST
1733 HC U.S.S. ENDURANCE A 1 - CRUDIV 11 FLTRON 13 Flagship to Fleet Squadron 13
TH
1734 HC U.S.S. INDEFATIGABLE A 4 - CRUDIV 41 FLTRON 44 Flagship to Fleet Squadron 44
TH
1735 HC U.S.S. ILLUSTRIOUS A 4 - CRUDIV 41 FLTRON 45 Flagship to Fleet Squadron 45
ND
1736 HC U.S.S. DETERMINATION A 2 - CRUDIV 21 FLTRON 21 Flagship to Fleet Squadron 21
RD
1737 HC U.S.S. RENOWN A 3 - CRUDIV 31 FLTRON 32 Flagship to Fleet Squadron 32
TH
1738 HC U.S.S. VENGEANCE A 5 - CRUDIV 51 FLTRON 54 Flagship to Fleet Squadron 54
TH
1739 HC U.S.S. SOVEREIGN A 7 - CRUDIV 71 FLTRON 75 Flagship to Fleet Squadron 75
ND
1740 HC U.S.S. RESOLVE A 2 - CRUDIV 21 FLTRON 22 Flagship to Fleet Squadron 22
ST
1741 HC U.S.S. VENERABLE A 1 - CRUDIV 11 FLTRON 11 Flagship to Fleet Squadron 11
TH
1742 HC U.S.S. MAJESTIC A 7 - CRUDIV 71 FLTRON 76 Flagship to Fleet Squadron 76

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
CHARGER CLASS FAST FRIGATES
RD
1743 FF U.S.S. CHARGER A 3 - CRUDIV 34 FLTRON 34
ND
1744 FF U.S.S. ILLUSIVE A 2 - CRUDIV 23 FLTRON 21
ND
1745 FF U.S.S. AUDACIOUS A 2 - CRUDIV 23 FLTRON 22
1746 FF U.S.S. FEARLESS A - BATGRP1 CRUDIV 5 FLTRON 6
TH
1747 FF U.S.S. COURAGE A 7 - CRUDIV 73 FLTRON 72
TH
1748 FF U.S.S. IMPULSIVE A 7 - CRUDIV 73 FLTRON 71
DAUNTLESS CLASS HEAVY FRIGATES
ST
1750 HF U.S.S. DAUNTLESS A 1 - CRUDIV 13 FLTRON 15
1751 HF U.S.S. ENFORCER A - BATGRP2 CRUDIV 6 FLTRON 7
ND
1752 HF U.S.S. DECEPTION A 2 - CRUDIV 23 FLTRON 24
1753 HF U.S.S. STEADFAST A - BATGRP2 CRUDIV 6 FLTRON 7
1754 HF U.S.S. CONCORDE A - BATGRP3 CRUDIV 7 FLTRON 8
RESOLUTE CLASS FAST BATTLESHIPS
TH
1780 BB U.S.S. RESOLUTE A 4 - - FLTRON 46 Flagship to Fleet Squadron 46
TH th
1781 BB U.S.S. INVINCIBLE A 4 - - COMGRP 4 Flagship 4 Fleet
TH th
1782 BB U.S.S. REPULSE A 6 - - COMGRP 6 Flagship 6 Fleet
TH
1783 BB U.S.S. EXULTANT A 8 - - FLTRON 85 Flagship to Fleet Squadron 85
TH
1784 BB U.S.S. DOMINANCE A 5 - - COMGRP 5
TH th
1785 BB U.S.S. NEMISIS A 8 - - COMGRP 8 Flagship 8 Fleet
EXECUTOR CLASS BATTLESHIPS
ND nd
1790 BB U.S.S. EXECUTOR A 2 - - COMGRP 2 Flagship 2 Fleet
ST st
1791 BB U.S.S. DECISIVE A 1 - - COMGRP 1 Flagship 1 Fleet
RD rd
1792 BB U.S.S. REDOUBTABLE A 3 - - COMGRP 3 Flagship 3 Fleet
FEDERATION CLASS BATTLECRUISERS
TH th
1795 BC U.S.S. FEDERATION A 7 - - COMGRP 7 Flagship 7 Fleet
TH
1796 BC U.S.S. CONCORDANCE A 7 - - FLTRON 74 Flagship to Fleet Squadron 74
TH th
1797 BC U.S.S. DREADNOUGHT A 5 - - FLTRON 56 Flagship 5 Fleet

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
DIRECTORATE CLASS HEAVY FLEET BATTLESHIP
1800 HB U.S.S. DIRECTORATE A N/A N/A N/A N/A
AVENGER CLASS FRIGATES
TH
1860 FF U.S.S. AVENGER A 6 - CRUDIV 64 FLTRON 65
TH
1861 FF U.S.S. FIDELITY A 4 - CRUDIV 43 FLTRON 45
TH
1862 FF U.S.S. DISTINCTION A 6 - CRUDIV 64 FLTRON 66
ST
1863 FF U.S.S. RESOURCEFUL A 1 - CRUDIV 13 FLTRON 16
RD
1864 FF U.S.S. RELIANT A 3 - CRUDIV 34 FLTRON 34
TH
1865 FF U.S.S. IMPERIAL A 5 - CRUDIV 53 FLTRON 52
ST
1866 FF U.S.S. DOUBTLESS A 1 - CRUDIV 13 FLTRON 12
RD
1867 FF U.S.S. COURAGEOUS A 3 - CRUDIV 34 FLTRON 35
RD
1868 FF U.S.S. BAINBRIDGE A 3 - CRUDIV 34 FLTRON 32
TH
1869 FF U.S.S. TRUXTON A 4 - CRUDIV 43 FLTRON 44
TH
1870 FF U.S.S. VALENCIA A 4 - CRUDIV 43 FLTRON 43
TH
1871 FF U.S.S. LAGRANGE A 7 - CRUDIV 73 FLTRON 73

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
BELKNAP CLASS DESTROYER ESCORTS
1881 DE U.S.S. BELKNAP A - BATGRP1 DESRON 7 FLTRON 6
1882 DE U.S.S. DECATUR A - BATGRP1 DESRON 7 FLTRON 6
ST
1883 DE U.S.S. UBIQUITOUS A 1 - DESRON 12 FLTRON 16
ND
1884 DE U.S.S. STRATOS A 2 - DESRON 25 FLTRON 25
TH
1885 DE U.S.S. INCORRIGIBLE A 4 - DESRON 42 FLTRON 44
TH
1886 DE U.S.S. CEPHEUS A 4 - DESRON 42 FLTRON 44
ST
1887 DE U.S.S. INFLICT A 1 - DESRON 12 FLTRON 16
ST
1888 DE U.S.S. SIROCCO A 1 - DESRON 12 FLTRON 11
1889 DE U.S.S. RAPTOR A - BATGRP1 DESRON 7 FLTRON 6
ND
1890 DE U.S.S. FEROCIOUS A 2 - DESRON 24 FLTRON 23
ND
1891 DE U.S.S. THOR A 2 - DESRON 25 FLTRON 24
1892 DE U.S.S. ODIN A - BATGRP5 DESRON 9 FLTRON 10
1893 DE U.S.S. SPECTER A - BATGRP1 DESRON 7 FLTRON 6
1894 DE U.S.S. HYDRA A - BATGRP5 DESRON 9 FLTRON 10

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
REPLENISH CLASS SUPPLY SHIPS
TH
1901 SP U.S.S. REPLENISH A 6 - SUPDIV 10 SERVRON 8
TH
1902 SP U.S.S. VICTUAL A 8 - SUPDIV 3 SERVRON 10
RD
1903 SP U.S.S. DELIVERANCE A 3 - SUPDIV 4 SERVRON 6
TH
1904 SP U.S.S. GUARANTOR A 5 - SUPDIV 8 SERVRON 7
ND
1905 SP U.S.S. VALANCE A 2 - SUPDIV 6 SERVRON 4
TH
1906 SP U.S.S. ELDORADO A 4 - SUPDIV 7 SERVRON 5
ST
1907 SP U.S.S. UMBRIA A 1 - SUPDIV 5 SERVRON 3
TH
1908 SP U.S.S. ALLARD A 6 - SUPDIV 10 SERVRON 8
ST
1909 SP U.S.S. HIBERNIA A 1 - SUPDIV 5 SERVRON 3
TH
1910 SP U.S.S. AUBURN A 4 - SUPDIV 7 SERVRON 5
TH
1911 SP U.S.S. IBERIA A 7 - SUPDIV 9 SERVRON 9
TH
1912 SP U.S.S. MOBILE A 7 - SUPDIV 9 SERVRON 9
TARAWA CLASS ASSAULT SHIPS
2201 GG U.S.S. TARAWA A - SALTGRP1 - COMGRP 16
2202 GG U.S.S. OKINAWA A - SALTGRP2 - COMGRP 17
2203 GG U.S.S. TRIPOLI A - SALTGRP3 - COMGRP 18

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
BRIDGEPORT CLASS REPAIR SHIPS
TH
2205 SR U.S.S. BRIDGEPORT A 6 - REPAIRDIV 6 SERVRON 8
TH
2206 SR U.S.S. CINCINNATI A 8 - REPAIRDIV 8 SERVRON 10
ND
2207 SR U.S.S. BUFFALO A 2 - REPAIRDIV 3 SERVRON 4
RD
2208 SR U.S.S. SPRINGFIELD A 3 - REPAIRDIV 5 SERVRON 6
TH
2209 SR U.S.S. JOURNEYMAN A 5 - REPAIRDIV 2 SERVRON 7
ST
2210 SR U.S.S. CRAFTSMAN A 1 - REPAIRDIV 4 SERVRON 3
TH
2211 SR U.S.S. PORTER A 4 - REPAIRDIV 1 SERVRON 5
RD
2212 SR U.S.S. SAGINAW A 3 - REPAIRDIV 5 SERVRON 6
TH
2213 SR U.S.S. BATTENFELD A 4 - REPAIRDIV 1 SERVRON 5
ND
2214 SR U.S.S. HOBART A 2 - REPAIRDIV 3 SERVRON 4
TH
2215 SR U.S.S. BESSEMER A 5 - REPAIRDIV 2 SERVRON 7
TH
2216 SR U.S.S. NASHUA A 7 - REPAIRDIV 9 SERVRON 9

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
VAUXHALL CLASS FREIGHTERS
ND
2219 TF U.S.S. VAUXHALL A 2 - FREIGHTDIV 3 SERVRON 4
ST
2220 TF U.S.S. HUMBOLT A 1 - FREIGHTDIV 11 SERVRON 3
TH
2221 TF U.S.S. WAYFARER A 4 - FREIGHTDIV 4 SERVRON 5
TH
2222 TF U.S.S. LEVIATHAN A 6 FREIGHTDIV 10 SERVRON 8
ND
2223 TF U.S.S. BETELGEUSE A 2 - FREIGHTDIV 3 SERVRON 4
TH
2224 TF U.S.S. COLOSSUS A 4 - FREIGHTDIV 4 SERVRON 5
2225 TF U.S.S. GOLIATH A - FLOT10 FREIGHTDIV 2 SERVRON 2 Treaty Zone station cargo supply duty
2226 TF U.S.S. ZEPHYR A - FLOT10 FREIGHTDIV 2 SERVRON 2 Treaty Zone station cargo supply duty
CLARK CLASS SUPPLY SHIPS
TH
2230 SP U.S.S. CLARK A 5 - SUPDIV 8 SERVRON 7
TH
2231 SP U.S.S. MARINER A 5 - SUPDIV 8 SERVRON 7
TH
2232 SP U.S.S. LEHIGH A 4 - SUPDIV 7 SERVRON 5
TH
2233 SP U.S.S. OLYMPIA A 4 - SUPDIV 7 SERVRON 5
ND
2234 SP U.S.S. MARSHALL A 2 - SUPDIV 6 SERVRON 4
2235 SP U.S.S. HOLLAND A - BATGRP4 SUPDIV 23 SERVRON 15
ND
2236 SP U.S.S. SYRACUSE A 2 - SUPDIV 6 SERVRON 4
2237 SP U.S.S. CORTINA A - BATGRP5 SUPDIV 19 SERVRON 14
ST
2238 SP U.S.S. TAIPEI A 1 - SUPDIV 5 SERVRON 3
ND
2239 SP U.S.S. VERSAILLES A 2 - SUPDIV 6 SERVRON 4
2240 SP U.S.S. GUNARD A - BATGRP3 SUPDIV 21 SERVRON 12
2241 SP U.S.S. PROVINCE A - BATGRP1 SUPDIV 20 SERVRON 11
ST
2242 SP U.S.S. TONNANT A 1 - SUPDIV 5 SERVRON 3
2243 SP U.S.S. ROANOKE A - BATGRP2 SUPDIV 22 SERVRON 13
2244 SP U.S.S. SUFFOLK A - BATGRP5 SUPDIV 19 SERVRON 14

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
ELUSIVE CLASS LIGHT DESTROYERS
TH
2401 LD U.S.S. ELUSIVE A 6 - DESRON 61 FLTRON 61
TH
2402 LD U.S.S. TEMPEST A 6 - DESRON 61 FLTRON 61
2403 LD U.S.S. REGULUS A - BATGRP4 DESRON 8 FLTRON 9
TH
2404 LD U.S.S. ARCHON A 5 - DESRON 51 FLTRON 52
2405 LD U.S.S. POLARA A - BATGRP4 DESRON 8 FLTRON 9
TH
2406 LD U.S.S. LEOPARD A 5 - DESRON 53 FLTRON 52
TH
2407 LD U.S.S. SPRITE A 4 - DESRON 43 FLTRON 41
TH
2408 LD U.S.S. COBRA A 4 - DESRON 43 FLTRON 41
TH
2409 LD U.S.S. MANTIS A 5 - DESRON 52 FLTRON 51
TH
2410 LD U.S.S. VIPER A 6 - DESRON 62 FLTRON 66
TH
2411 LD U.S.S. COUGAR A 6 - DESRON 62 FLTRON 65
TH
2412 LD U.S.S. PYTHON A 4 - DESRON 42 FLTRON 46
TH
2413 LD U.S.S. LAMPREY A 8 - DESRON 85 FLTRON 84
TH
2414 LD U.S.S. STINGRAY A 4 - DESRON 42 FLTRON 45
TH
2415 LD U.S.S. TIGER A 8 - DESRON 83 FLTRON 84
TH
2416 LD U.S.S. OSPREY A 8 - DESRON 83 FLTRON 83
TH
2417 LD U.S.S. TYPHOON A 8 - DESRON 84 FLTRON 83
TH
2418 LD U.S.S. OCELOT A 8 - DESRON 84 FLTRON 86
TEREX CLASS SHUTTLECRAFT TRANSPORTS
2501 TR U.S.S. TEREX A - - TRANSDIV 1 -
2502 TR U.S.S. GEMINI A - - TRANSDIV 1 -
2503 TR U.S.S. HARKNESS A - - TRANSDIV 1 -
2504 TR U.S.S. LA SALLE A - - TRANSDIV 1 -
2505 TR U.S.S. GALLANT A - - TRANSDIV 1 -

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
HERCULES CLASS TUG/TRANSPORT
3801 TG U.S.S. HERCULES A 8TH - TUGDIV 10 SERVRON 10 Container transport duty
3802 TG U.S.S. ATLAS A 7TH - TUGDIV 8 SERVRON 9
3803 TG U.S.S. MARS A 4TH - TUGDIV 6 SERVRON 5
3804 TG U.S.S. URSUS A 2ND - TUGDIV 3 SERVRON 4
3805 TG U.S.S. PRATT A - FLOT9 TUGDIV 1 SERVRON 1
3806 TG U.S.S. CONSERVER A 7TH - TUGDIV 8 SERVRON 9
3807 TG U.S.S. INGERSOLL A 3RD - TUGDIV 5 SERVRON 6
3808 TG U.S.S. SAMPSON A 1ST - TUGDIV 4 SERVRON 3
3809 TG U.S.S. ENTEMEDOR A - FLOT10 TUGDIV 2 SERVRON 2
3810 TG U.S.S. RETRIEVER A 5TH - TUGDIV 7 SERVRON 7
RD
3811 TG U.S.S. MANITOWOC A 3 - TUGDIV 5 SERVRON 6
3812 TG U.S.S. READY A - FLOT9 TUGDIV 1 SERVRON 1
3813 TG U.S.S. STALLION A 2ND - TUGDIV 3 SERVRON 4
3814 TG U.S.S. TENACIOUS A - FLOT10 TUGDIV 2 SERVRON 2
3815 TG U.S.S. ULYSSES A 6TH - TUGDIV 9 SERVRON 8
EUCLID CLASS FLEET TUGS
3831 TG U.S.S. EUCLID A 6TH - TUGDIV 9 SERVRON 8
3832 TG U.S.S. STALWART A 4TH - TUGDIV 6 SERVRON 5
3833 TG U.S.S. LETOURNEAU A 3RD - TUGDIV 5 SERVRON 6
3834 TG U.S.S. VIGOROUS A 1ST - TUGDIV 4 SERVRON 3
3835 TG U.S.S. BRAWNY A 7TH - TUGDIV 8 SERVRON 9
TH
3836 TG U.S.S. HEARTY A 5 - TUGDIV 7 SERVRON 7
3837 TG U.S.S. FORCEFUL A 8TH - TUGDIV 10 SERVRON 10
3848 TG U.S.S. ANAXIMANDER A - FLOT9 TUGDIV 1 SERVRON 1

VOLUME II
Table 2a66.1
Registry Ship Type
(NCC) Class Command
SHERMAN CLASS CARGO DRONES
TH
G145 TD-R U.S.S. SHERMAN A 5 - DRONEDIV 1 COMGRP 5 Station and outpost supply from Starbase 21
TH
G146 TD-R U.S.S. JACKSON A 7 - DRONEDIV 1 COMGRP 7 Station and outpost supply from Starbase 23
TH
G147 TD-R U.S.S. MOORE A 8 - DRONEDIV 1 COMGRP 8 Station and outpost supply from Starbase 24
ST
G148 TD-R U.S.S. ROBERT E. LEE A 1 - DRONEDIV 1 COMGRP 1 Station and outpost supply from Starbase 25
ST
G149 TD-R U.S.S. HARRISON A 1 - DRONEDIV 1 COMGRP 1 Station and outpost supply from Starbase 17
TH
G150 TD-R U.S.S. RICHARDSON A 7 - DRONEDIV 1 COMGRP 7 Station and outpost supply from Starbase 15
ND
G151 TD-R U.S.S. GILLESPIE A 2 - DRONEDIV 1 COMGRP 2 Station and outpost supply from Starbase 27
TH
G152 TD-R U.S.S. McCLELLAND A 8 - DRONEDIV 1 COMGRP 8 Station and outpost supply from Starbase 16
ND
G153 TD-R U.S.S. THOMPSON A 2 - DRONEDIV 1 COMGRP 2 Station and outpost supply from Starbase 18
TH
G154 TD-R U.S.S. STEWART A 4 - DRONEDIV 1 COMGRP 4 Station and outpost supply from Starbase 20
TH
G155 TD-R U.S.S. GRANT A 5 - DRONEDIV 1 COMGRP 5 Station and outpost supply from Starbase 13
TH
G156 TD-R U.S.S. SHILOH A 4 - DRONEDIV 1 COMGRP 4 Station and outpost supply from Starbase 14
TH
G157 TD-R U.S.S. TECUMSEH A 4 - DRONEDIV 1 COMGRP 4 Station and outpost supply from Starbase 28
ST
G158 TD-R U.S.S. RIO GRANDE A 1 - DRONEDIV 1 COMGRP 1 Station and outpost supply from Starbase 9
TH
G159 TD-R U.S.S. LINCOLN A 5 - DRONEDIV 1 COMGRP 5 Station and outpost supply from Starbase 5
TH
G160 TD-R U.S.S. SHENANDOAH A 6 - DRONEDIV 1 COMGRP 6 Station and outpost supply from Starbase 26
RD
G161 TD-R U.S.S. TICONDEROGA A 3 - DRONEDIV 1 COMGRP 3 Station and outpost supply from Starbase 19
TH
G162 TD-R U.S.S. ALLEGHENY A 6 - DRONEDIV 1 COMGRP 6 Station and outpost supply from Starbase 22
RD
G163 TD-R U.S.S. FRANKLIN A 3 - DRONEDIV 1 COMGRP 3 Station and outpost supply from Starbase 11
TH
G164 TD-R U.S.S. MEADE A 8 - DRONEDIV 1 COMGRP 8 Station and outpost supply from Starbase 8

CONFIDENTIAL
RESTRICTED DATA
NOFORN
VOLUME II
7.0 STAR FLEET BASE OPERATIONS

In this chapter the principal operations concerning Star Fleet bases and stations will be
examined. ARTICLE 52 of the Articles of Federation, specifically Paragraph 3, sets the
requirement to establish Star Fleet Headquarters and “Starbases” by Star Fleet, and
ARTICLE 16 of the Star Fleet Charter gave Star Fleet the authority to construct these
bases. As such, Star Base Command was created to build and manage these facilities,
which constitutes the entire Shore Establishment of Star Fleet. All operations, missions
and functions concerning Star Fleet bases, stations and outposts will be the responsibility
of Star Base Command.
Section 7.1 describes the basic functions of Star Fleet bases and stations. The functions
range from fleet support to diplomatic responsibilities. This section will also describe how
bases and stations are used to set the boundaries of Federation space and how they are
used as law enforcement centers for the Federation. This section basically answers the
question: what are bases for?
Section 7.2 outlines the basic operations performed by Star Fleet bases and stations, as
well as a brief explanation of their capabilities. This section will also describe the command
jurisdiction of the various bases and stations. As such, this section answers the question:
what do bases do?
Section 7.3 describes the various types of bases and stations contained within the Shore
Establishment. This section defines the difference between a base and a station and will
summarize the function of each of the base and station types described.
Section 7.4 describes the process of selecting and constructing Star Fleet bases and
stations. In addition, the rules or the criteria used to decide on the location of bases and
stations will also be presented.
Section 7.5 presents the current locations of Star Fleet bases, stations and outposts. The
locations of such bases and stations will be presented in both tabular and pictorial form.
However, this section has been classified as CONFIDENTIAL and as such, all security
precautions are in effect.

VOLUME II
STANDARD OPERATIONS
Standard Operations are basically the routine functions performed at or by Star Fleet
bases and stations. These are the functions that will be outlined in the orders given to
base and station Commanders upon assumption of command. The specific operations,
however, will be based upon the functions described in Section 7.1 and will be explained in
more detail in Section 7.2.
Standard Operations also refer to those specific tasks that are routinely performed at
the base or station, but involving other units and Type Commands as well. For example,
replenishing base stores is a standard function involving the Star Fleet Transportation
Command. Such operations do not involve any special planning since they are scheduled
tasks or events performed by the command.
Standard Operations will also include those functions performed by any attached repair
facility as well. Since it is a primary function of a Star Fleet base to service the fleet, all
repair and refit operations performed by repair facilities will be part of the Standard
Operation of the base, regardless whether the repair facility may be separately managed
by the Star Fleet Division of Engineering.
ASSIGNMENT TO MISSIONS
In general, the missions assigned to most Star Fleet bases are in the form of general and
standing orders issued by Star Fleet Command. These orders are the broad directives
relating to the essential functions of bases and stations as stated in ARTICLE 65 of the
Star Fleet Charter and which are outlined in Sections 7.1 and 7.2 of this chapter. As
such, these directives are given to everyone who is assigned to command a Star Fleet
base or station.
Missions are assigned to Star Fleet bases by Star Base Command, the subdivision of
Star Fleet Operations that handles base and station operations. And except in the case
where a Star Fleet Base Commander must respond to a situation on his or her own, all
operations assigned to Star Fleet bases and stations come from Star Base Command.
Base and station operations primarily deal with the management of troops, the assignment
of craft, and the deployment of Starships to missions, if such ships are assigned to the
base. However, a mission assigned to a base may also involve some special action such as
how a local government or its Local Force should be handled, or an assignment involving
some special operation.
In general, mission orders and profiles will usually come to bases and stations by subspace
radio – either as a secure verbal message or as a written coded message. Such mission
orders and communications will always be directed to the Commanding Officer of the
facility. Missions assigned to Star Fleet bases and stations usually involve supporting the
fleet or the Operating Forces in their mission. As such, Star Fleet bases may share a
mission profile with the Operating Forces.

VOLUME II
DEVELOPMENT OF BASE ASSIGNMENTS
Star Base Command is the organization primarily responsible for the assignment of
missions to Star Fleet bases and stations. As such, it will be Star Base Command that
will develop and transmit mission directives to bases and stations. In addition, Star Base
Command will also develop the Standard Operations that will be performed by most, if
not all, bases.
In most cases assignments are to entities outside the base, but that will directly involve
the installation. For example, when a new Fighter Wing is assigned to a base, or when a
Starship has been assigned to the base.

VOLUME II
BASE DUTY ROTATION
Base Duty Rotation is the planned reassignment of base and station personnel from one
duty station to another. The function of this is to provide personnel with a diverse set of
skills and experiences, and to maintain or boost morale. If individuals continuously perform
the same duties on the same station boredom may develop and ambivalence to their duty
may ensue. Therefore, Star Fleet, specifically Star Base Command, strives to provide
its personnel with a wide range of experiences. Base Duty Rotation, therefore, is the
primary method of providing personnel with new experiences, which will enhance their
knowledge of differing cultures and to increase their ability to handle new and challenging
situations[1].
Personnel assigned to Star Fleet bases are generally stationed there for about two years.
However, for the larger planetary bases, such as on Star Fleet Headquarters, the length
of the assignment may be up to four years. This furnishes personnel with ample time to
become familiar with base operations and to become experts and specialists in their field.
Base personnel generally rotate between stations and outposts about every four to six
months. That is, a person assigned to an Outpost is there for about four months and then
rotated to a Starbase or Deep-space Station for six months before returning to another
Outpost. The relief schedule is scattered so that only a few Outposts need to have their
personnel relieved at any one time. This relief procedure is performed on a quarterly basis
and is timed with the required quarterly medical checkups. Star Fleet Transports, and
sometimes Starships, will generally be assigned to perform the relief operation as well as
the quarterly physicals.
Table 2a70.1
STAR FLEET BASE DUTY ROTATION SCHEDULE
Assignment Expected Next
Duty Station
Length Duty Station Comments
Type
(months) Type
Planetary Base 36 - 48 Station Most desired of all shore duty
Orbiting Base 30 Outpost/Station Usually for engineering personnel
Orbiting Station 24 Outpost/Base Primarily for engineering personnel
Deep-space Station 18 Base The usual rotation from an Outpost
Garrison 24 Base
Floating Outpost 6 Station About 15-20% rotated each month
Fixed Outpost 4-6 Station Utilizing a scattered rotation schedule
In general, Base Duty Rotation is not mandatory except where there will be a need to
fulfill a billet on a particular station and as such, base and station personnel are given the
opportunity to accept a post on another base or station. However, should an individual
refuse to accept the position, no disciplinary action will generally be taken, but it will
reflect negatively on that person’s commitment to the Service and may cause his or her
name to be dropped to the bottom of the promotion list. If the request is in the form of a
Direct Order, the individual must accept or experience the full weight of the Star Fleet
judicial system. Individuals may also request duty at a particular base or station as well. In
such cases the individual will be placed on top of the billet list for the base – in the order
that the request is made. The individual must then wait until there is an opening at the
requested assignment.

VOLUME II
7.1 STAR FLEET BASE FUNCTIONS

In general, Star Fleet bases and stations represent the Federation government in open
space as well as being operational support centers for Star Fleet. In order to perform the
functions to which it has responsibility Star Fleet maintains five Regional Star Fleet
Headquarters, 28 major Starbases[2], 41 Stations, 68 Outposts, 12 Garrisons, and
59 fleet support facilities of various types distributed throughout Federation space. As
such, this constitutes the bulk of the Shore Establishment of the Star Fleet. In general,
such Star Fleet bases are typically quite large as they must support a large number of
ground troops, support fleet operations, provide local protection, support Star Fleet ships
and craft, and provide rest and recreational facilities to the Operating Forces. The
purpose of this section is to define the roles and functions that bases and stations provide
to Star Fleet and the Federation in general.
FLEET COMMAND CENTERS
The primary function of Star Fleet bases is to serve as local command centers for the
fleet, which are the extended arms of Star Fleet Operations. All bases receive their
orders and missions from the central command authority, which then relays them to the
Operating Forces. As such, the Operating Forces will primarily receive their orders
from Star Fleet bases and stations and must regard such orders as coming directly from
Star Fleet Command.
In general, the commander of the base or station is the representative of the Federation
and of Star Fleet in that region of space his base is located and as such, will be the Area
Commander of that region of space; he speaks for it and is personally accountable for all
activities occurring in and around the region of space he has Jurisdictional Authority*.
Since he is accountable for everything that occurs in and around his base, he is given full
power to enforce Federation law and Star Fleet Regulations.
OPPERATING FORCES SUPPORT
In addition to being regional command centers, the secondary function of Star Fleet
bases and stations is to support the fleet. Star Fleet bases provide the primary support
for all the Operating Forces of Star Fleet. In terms of fleet operations, bases supply the
fleet with provisions and equipment, fuel and craft; are the source for troops and crew
personnel; act as repair and refurbishment facilities, and centers for rest and recreation.
Star Fleet bases and stations will generally be placed at strategic locations throughout a
Federation octant in order to efficiently support the fleet. Based upon the location of the
bases and stations within his octant of operation, a Fleet Commander will customarily
position his forces such that any unit of his fleet will have access to a nearby Star Fleet
base or station. As such, each ship within the fleet will be assigned to a specific Starbase
or Station from which it will normally operate from. This base or facility is called the ship’s
“Home Port” and it will be from this base that the ship will normally receive its orders,
supplies and equipment[3]. In addition, these Home Ports will have sufficient lodgings to
house the entire crews, and their families, of the ships assigned to them.
*See Section 5.3 of Volume I for the definition of Jurisdictional Authority.

VOLUME II
LOCAL AREA LAW ENFORCEMENT
Since Star Fleet bases represent the Federation government they also symbolize
Federation law as well. As such, Star Fleet bases also act as regional law enforcement
centers. Base operations relating to law enforcement are generally performed by base
security personnel using Star Fleet shuttlecraft designed for that purpose. The security
force periodically patrols the areas throughout the bases’ Jurisdictional Area. The base
security force is made up of personnel from the various offices within the Star Fleet
Division of Security and the Star Fleet Division of Justice, including those from the
Star Fleet Bureau of Investigation, the Star Fleet Investigative Service and the
Star Fleet Bureau of Corrections.
In addition, local law enforcement may also be accomplished through the use of “Home
Port” Starships as well. Bases may contact nearby Starships to perform the duty of
local constabulary by investigating crimes and apprehending criminals. The use of such
Starships in this role will primarily be to pursue fleeing criminals or to stop and board
vessels suspected of smuggling. Therefore, should any form of warrant be issued by a
Federation court, it will be directed to the appropriate Star Fleet base for execution. It
is the responsibility of Star Fleet to execute all Federation warrants.
In order to hold suspects and prisoners, Star Fleet bases and stations contain detention
facilities, which may range from small Brigs to large prisons or penitentiaries, depending
on the size and function of the base or station. Some Starbases, particularly the District
Headquarters, have extensive prison facilities – primarily for military prisoners. That is,
when Star Fleet must adjudicate a case, the sentence will most likely be carried out at
the nearest Local System prison facility or penal colony. However, most of the larger
Starbases are equipped with extensive Brig and detention facilities that accommodate
both military and civilian prisoners. In addition, Star Fleet will also manage Federation
penal colonies as well. However, these facilities will be managed solely by the Star Fleet
Bureau of Corrections and therefore, are not considered bases per se.
Star Fleet Stations, on the other hand, will only have minor Brig facilities designed
primarily for military detainees, but which may be used for civilian prisoners if necessary.
For civilian detainees the Brig on a station will only be a temporary detention facility until
the prisoner can be moved to a larger or permanent facility.
Star Fleet bases are also equipped with extensive crime laboratories and other facilities
for the collection and analysis of evidentiary material. Base security personnel that are
performing the role of criminal investigators include experts in the fields of crime scene
investigation, pathology, toxicology and other activities involved in the investigation and
analysis of evidence. The laboratories are primarily operated by the Star Fleet Bureau of
Investigation, except for the smaller laboratories that may be installed on Star Fleet
Stations. These labs are solely managed by station security personnel.

VOLUME II
REGIONAL COURT
As part of its law enforcement role, Star Fleet also functions as the judicial arm of the
Federation in deep space. Federation courts do not normally extend to the outer
boundaries of Federation space and therefore, Star Fleet is empowered with judicial
authority in the outlying territories and as such, was given the authority to establish courts
in these regions as provided under ARTICLE 28 of the Star Fleet Charter. Star Fleet
courts are located on all Starbases[4] and on some stations, and are managed and
operated by the Star Fleet Bureau of Courts (BUCOURTS).
Star Fleet courts are designed to handle both military courts-martial to adjudicate cases
involving Star Fleet personnel and in some cases Local Force personnel that operate in
open space that are adjoined to units of the Star Fleet, as well as criminal cases involving
civilians that violate the laws and regulations of the Federation to which Star Fleet has
purview. Such cases may entail the violation of safe navigation regulations and practices,
incorrect or missing vessel licensing, registration or cargo manifest documentation, missing
or incorrect operator’s licenses, smuggling, theft and others. However, such courts are not
normally designed to handle capital cases such as murder, treason or other high crimes, or
civil cases such as law suits and therefore, will usually be deferred to a civilian Federation
court.
Although a Star Fleet court will not adjudicate a high crime, it can impose confinement
and bail should the suspect be caught in open space by Star Fleet and brought before a
Star Fleet Magistrate. The court, in this instance, would direct to have the nearest Star
Fleet ship transport the prisoner to the proper Federation detention facility and to a
district court.
With regard to trials that occur on Star Fleet bases, Star Fleet will provide or to make
available defense attorneys from the Star Fleet Office of Judge Advocates to supply
legal counsel to defendants. It is not required that defendants use Star Fleet lawyers
since defendants always have the right to select and hire a civilian lawyer of their choice
from anywhere within the Federation – so long as it will not excessively delay or hamper
the judicial process. However, the prosecution of cases within Star Fleet courts will
always be handled by Star Fleet attorneys from the Judge Advocate General’s office.
In open space and far from any Federation facility, Star Fleet ships do not always have
the luxury of time when it comes to incarcerating and transporting prisoners to a nearby
Star Fleet or Federation facility for minor crimes and misdemeanors. As such, Star
Fleet was given the authority to establish minor courts onboard Starships. In addition, to
handle the minor offenses that occur at the outlying areas of Federation space, Starship
Commanders were given the authority to investigate and adjudicate these minor cases[5],
which is a prerogative only given to Starship Commanders, and not to Commanding
Officers of Star Fleet support ships.

VOLUME II
REGIONAL CONSUL
ARTICLE 7 of the Star Fleet Charter gives Star Fleet consular authority in open space
when no Federation diplomat or consulate is available. As such, Star Fleet bases will
serve as the local area consulate and will provide consular services if necessary. However,
some of the larger District and Sector Starbases may possess a Federation consulate
with an ambassador present on site. Furthermore, Star Fleet bases will either maintain a
Sector Representative (SECREP), a District Staff Representative (STFREP), a
Fleet Representative or a Space Sector Representative (FLTREP) from the Star
Fleet Bureau of Consular Affairs (BUCONAF). The particular representative stationed
at the base will depend upon the size and mission of the base or station.
A Sector Representative is the chief liaison to member and non-member worlds of the
Federation and will represent Star Fleet in all matters pertaining to its consular role in
that octant. The Sector Representative (SECREP) is also the senior officer in charge of
all Fleet Representatives that may be assigned to commands within the octant. Sector
Representatives are assigned to these regions by the Star Fleet Bureau of Consular
Affairs and will be a Captain in the Diplomatic Corps. The Sector Representative
reports directly to the Sector Commandant regarding all the consular activities within
the octant, as well as to keep the Sector Commandant informed of any changes in the
treaties and agreements between the Federation and the local governments contained
within that area of space.
The Sector Federation Consul (FEDADM) is the primary civilian ambassador to the
various Federation and foreign governments within or adjacent to the sector and will act
as council to the Sector Commandant on the matters pertaining thereto. FEDADM is a
person with extensive knowledge of the laws, treaties and agreements connected with all
of the Federation worlds that are within the sector and of the many worlds outside the
Federation as well. The FEDADM will work with Federation and foreign ambassadors
and diplomatic personnel during peace negotiations within and outside of Federation
space.
The Sector Federation Consul reports directly to the Star Fleet Consul General
(SFCCG) and as such, will have direct access to the Director: Star Fleet Command.
The FEDADM will also perform the duty of counselor to the Sector Commandant, but
does not come under the direct authority of the COMSEC. In addition, the FEDADM has
the authority to attend any meeting, negotiation or other conference with foreign officials
that may involve Federation ambassadors, diplomats, Star Fleet Representatives or
Star Fleet Commanders.
ARTICLE 29 of the Charter provides Star Fleet with the authority to settle disputes
between social systems within the boundaries of the Federation. This authority is given
to Star Fleet only when no Federation diplomat is available to settle the dispute. As
such, bases are typically used as neutral sites to settle disputes between member or
nonmember systems.

VOLUME II
RECREATIONAL CENTERS
Star Fleet bases and stations also act as rest and recuperation centers for the fleet.
Almost every base and station, with the exception of Star Fleet Communications, TAC
bases, and Outposts, which will have some measure of recreational services within their
facility that can be utilized by visiting Star Fleet personnel. Services may include stores,
parks, gymnasiums, libraries and hobby areas to keep relaxing crewmembers busy.
The larger Starbases usually have ample housing facilities and quarters for visiting crews,
including large dining halls and entertainment centers. In addition, many of these large
Starbases are located on worlds with a large civilian population as well. As such, visiting
crews and off-duty station personnel can go outside the base compound for recreational
activities. Star Fleet stations also contain some recreational facilities, though not at the
scale of the larger Starbases[6].
Star Fleet Outposts are also built with recreational facilities. However, the recreational
facilities within the small outposts are designed primarily for the personnel stationed at the
facility and are not designed to accommodate a visiting Starship. And although a
Starship on patrol may stop at an outpost, usually for official business or replenishment,
for a few days and may partake in their recreational facilities, only a small company of the
crew will be able to exercise liberty privileges at any given time. As such, the ship’s crew
will have to carrying out liberty privileges in shifts.
FORM FEDERATION BOUNDARIES
Outlying bases and space stations are essentially used to establish the boundaries of
Federation space. In particular, Star Fleet Outposts are designed for this purpose as
they will mark the boundary of the Federation by their physical presence. To indicate and
communicate the boundary to any vessel, outposts will emit signals and beacons that
identify the area as belonging to the Federation. In addition, outposts function as guard
posts, monitoring the boundaries for space traffic, compliance with treaties and
agreements; act as “trip wires” for possible incursions of unknown or hostile forces, and to
function as listening posts for alien communications outside the Federation. To aid in
monitoring the region of space in which they have Jurisdictional Authority, outposts
may be equipped with several shuttlecraft that are used to patrol the areas around the
station.

VOLUME II
RIGHTS OF PASSAGE AND PORT VISITATION RIGHTS
By definition, all Star Fleet ships and craft have Port Visitation Rights to any Star
Fleet base or station. Where a base or station is located within the sovereign territory of a
member system, Rights of Passage are given to Star Fleet vessels in order that they
can visit the base, regardless of the reason. This is because ARTICLES 43, 49 and 105 of
the Articles of Federation guarantee Star Fleet such "Rights of Passage" and "Port
Visitation Rights" with the members of the Federation for the fulfillment of its missions
and therefore, each member system is required to carry out its obligations to support Star
Fleet.
With regards to non-member systems, bases and stations that are located within these
sovereign territories, Star Fleet ships will be granted Rights of Passage within the
system and may be given Port Visitation Rights to the worlds within the system as part
of the agreement for establishing the installation. However, such rights into the system
can only be established through agreements with the sovereign world. In most cases, if
Star Fleet receives approval from a world to build a base or station anywhere within the
sovereign territory of the system, Star Fleet will generally receive Rights of Passage
and Port Visitation Rights as part of the agreement to build the facility.
On the other hand private, commercial or foreign vessels have Port Visitation Rights as
it applies to Star Fleet facilities, even if the base or station is located within a sovereign
system that has open Rights of Passage. As such, private and commercial vessels may
only have Port Visitation Rights to local system facilities and must, nonetheless, request
permission from the Star Fleet Base Commander to enter orbit around or land at any
Star Fleet facility. This restriction does not apply to Local Forces where the Star Fleet
base or station is located. Local Forces will generally have free access to any Star Fleet
facility located within the boundaries of their respective system. However, out in deep
space Local Forces may not have Port Visitation Rights to Star Fleet bases or
stations except in the case where the Local Force has been attached to Star Fleet. In
any case all non-Star Fleet vessels do not have Port Visitation Rights or access to any
Star Fleet base or station located in deep space except as authorized by the Federation
Council or when conditions require immediate access such as for emergencies.

VOLUME II
7.2 GENERAL BASE OPERATIONS

In this section the basic operations performed by Star Fleet bases and stations will be
discussed. That is, this section will describe the various operations that may be performed
for the functions outlined in Section 7.1.
FLEET ADMINISTRATION
As earlier stated, the primary function of Star Fleet bases is to serve as local command
centers for the fleet and for Star Fleet Operations. Fleet administration, as it relates to
operations, is the management of the operating assets that are assigned to the base or
station, or that may be contained within the Jurisdictional Authority of the command.
Jurisdictional Authority is defined as the region of space surrounding a base or station
where the Commanding Officer of the facility will be the “Senior Officer Present” and
will have command authority over all forces contained within that region. As such, all
vessels, whether they are private, commercial, military or Star Fleet that are inside the
Jurisdictional Authority of the base or station, will come under the direct authority of
that base or station commander exercising the role of Area Commander.
However, regarding fleet administration, bases and stations are usually a “pass-through”
for the orders and operations administered by Star Fleet Command and as such, will
usually only relay Operational Orders to the Operating Forces.
Ships that are assigned to a Starbase will come under direct authority of the Base
Commander. As such, the Base Commander can issue orders to ships and can assign
missions to the ships under his authority when such ships are not currently under orders
from Star Fleet Command. However, the Base Commander has no direct authority
over the ship’s crew, nor can he make any changes to the organization of the ship. The
ship’s captain is the only person with direct authority over the ship’s crew. However, while
the ship is attached to the base in question, the Commanding Officer of the ship will
come under direct authority of the Base Commander.
Ships that are not assigned to a Starbase do not come under direct authority of the Base
Commander, but must conform to the policies and regulations as laid down by the Base
Commander, as Area Commander, while it is operating within the Jurisdictional
Authority of the Base Commander. For example, if a Starship Commander wishes to
make an official visit to the base and to grant Leave or Liberty privileges to his crew, he
must seek authorization from the Base Commander as soon as he enters the base’s
Jurisdictional Authority and before his ship can orbit the base or station.
The volume of space commanded by the Base Commander may contain other smaller
stations and as such, the Commanding Officers of these stations will come under direct
authority of the Base Commander in the role of Area Commander. However, these
smaller stations will also have their own Jurisdictional Authority as well, though not to
the extent that the Base Commander may have. As such, the Jurisdictional Authority
of the Station Commander will supersede that of the Base Commander if the ship is
within the range of the station, or the ship wishes to make a call on the station or wishes
to orbit around the station. However, regarding operational command authority over the
vessel, the Base Commander has precedence over the Station Commander.

VOLUME II
REGIONAL DEFENSE
Star Fleet bases and stations provide regional defense for their jurisdiction. That is, the
base or station commander has the major responsibility of defending his Jurisdictional
Authority and of defending all the forces, planets and peoples contained therein. This
protection is typically performed using the fighter craft attached to the command and by
the Starships that may be assigned to the base or station.
Most Star Fleet bases have a large detachment of Fighter or Attack craft assigned to
them. For the larger Starbases, this contingent of Attack craft will usually be of Wing
strength, which is equivalent to about 120 such craft. However, such bases may contain
more than one Wing depending upon the location of the base relative to the extent of
hostile forces around the area or the space traffic density within the area. Craft assigned
to such wings will primarily be engaged in security patrols and law enforcement duties in
and around the Jurisdictional Authority of the base.
Defense of the region can also come from attached or nearby Starships. In areas of
prevalent hostile activity, Star Fleet Operations may assign one or more Starships to a
Base Commander for the purpose of base and area defense. These ships will generally
come from nearby Fleet Squadrons and will more than likely be of the lighter Destroyer
or Escort class of combatants. But this is rare. What normally takes place is that the Fleet
Commander will assign his Fleet Squadrons to command bases, which will become the
Home Port of the ships within the squadron. Therefore, should an emergency call go out
from the base, the ships assigned to that Home Port will automatically respond to the
call.
The base’s sphere of influence will typically be divided into operational octants or sectors
that will constitute the Patrol Zones around the base. Such zones are a convenient way
of assigning and distributing the base's forces to Patrol Zones. The establishment of such
zones, their size and number, will be wholly up to the Base Commander. The function of
these Patrol Zones is primarily for base defense, but they may also be used to patrol the
volume surrounding the base in fulfillment of its law enforcement responsibilities as well.
Star Fleet bases are one of the primary targets of any hostile force. To destroy a Star
Fleet base would mean the disruption of the command and control link between nearby
forces and the central command. Therefore, bases are heavily armored and fortified. Bases
will usually contain troops of Division strength or about 12,000 troops. Such troops are
used to protect the base in case of invasion and as a source of troops for assaults. In
addition, Star Fleet bases and stations also have extensive defense systems all their own.
They have very powerful Phaser and Pulse Cannon weapons systems capable of destroying
an enemy hundreds of thousands of kilometers away. However, such weapon systems are
fixed installations that can only fire weapons out into space. These are, in essence, the
final line of defense for the base.

VOLUME II
REGIONAL LAW ENFORCEMENT
As with the defense of the region, Star Fleet bases and stations will also be responsible
for law and order within their region as well. Law enforcement operations generally entail
patrolling the region for compliance with spacecraft and navigational regulations, assuring
the free movement of trade, the protection of private and commercial vessels from pirates,
and the pursuit and apprehension of criminals and fugitives.
However, the typical and daily role of bases and stations with regard to law enforcement is
to monitor and protect the private and commercial space lanes within the region. This will
normally be accomplished using local light combatant Starships that have been assigned
to the base as stated in Section 7.1 of this volume. However, this role may be changing as
the operating cost in using Starships for such law enforcement duties is becoming more
prohibitive. As such, there are plans underway to develop a new class of vessel called the
Cutter or Patrol (P-class) ship. This new class of warp-driven combatant will be sized
somewhere between an E-class Escort ship and an A-class Fighter craft, and will have
a crew capacity sufficient for law enforcement duty around the region.
FLEET SUPPLY
Fleet support operations typically denote the outfitting, replenishment and refitting of the
Operating Forces. As such, Star Fleet bases and stations are regional supply centers for
the Operating Forces and to other Shore Establishments as well. They function as the
source and rendezvous points for fleet replenishment.
Star Fleet bases typically have large supply depots on site that can store the provisions,
equipment and the spare parts needed to replenish and repair the fleet, and the smaller
stations and outposts. Much of the supplies are contained in large warehouses managed
by the Star Fleet Office of Material Management, an office within the Star Fleet
Supply Command that manages all supply and storage facilities. Star Fleet Stations,
on the other hand, have small storage repositories for spare parts and equipment. They
can only carry the smaller machinery subassemblies and parts since they are not equipped
to handle major repairs of Star Fleet ships. Outposts and Garrisons also have storage
areas as well, but these are designed primarily for their own material needs, repairs and
maintenance and are not generally used as a source of fleet supplies and material.
Many of the larger Starbases, specifically the Sector Bases, may have assigned to them
freighters and containers from the Military Space Lift Command. The primary purpose
for these vessels is to supply the various Star Fleet bases and space stations that are
within the Jurisdictional Authority of the larger area base. As such, all requests for
replenishment by the smaller bases and stations within the command jurisdiction will be
made to the Sector Base.
The replenishment of Starships will normally be performed by the Home Port of the
ship. This will normally be done after an extended period on patrol when the ship has been
ordered back for rest, leave and liberty privileges. However, while a Starship is on patrol
near the outskirts of the Federation, replenishment, if needed, will be handled by any
nearby Starbase or Station, or by supply ships that are part of the fleet.

VOLUME II
FLEET REPAIR
Some bases and stations have Drydocks for the purpose of performing major repair and
refit work on Star Fleet vessels, or they may have repair ships assigned to them for such
purposes. However, most bases will possess Mobile Repair vessels, which are moveable
frames designed to enclose a ship for external hull work.
Fleet Tugs may also be attached to Starbases for the purpose of towing Starships to
their repair facility. Only the large Starbases that have extensive repair facilities will have
Fleet Tugs attached to them. These vessels are the same as those assigned to the fleet.
For Sector Bases with an attachment from the Military SpaceLift Command, Fleet
Tugs will be assigned for the purpose of transporting containers to and from nearby bases
and stations.
Fleet construction is performed at special stations in space. There are six such stations
located throughout the Treaty Zone. These facilities build all the ships and craft for Star
Fleet, as well as fabricating the sections used to build the various free-floating space
stations. These facilities are very large stations floating in space with the capability of
building up to four Starships simultaneously. These stations are a part of the Star Fleet
Construction Command and as such, Star Fleet Operations will have no authority
regarding the operations of these facilities. However, the location or placement of these
stations will be determined by the Star Fleet Office of Strategic Planning (SFPLAN).
All six of these Construction Facilities are located within the Treaty Zone.
Distributed throughout the Treaty Zone are four Mobile Drydocks. These structures are
used for the repair and refitting of ships and craft in deep space where there may not be
any repair or construction facility nearby. These facilities were not intended for major refits
or overhauls, but only for ship repairs. They typically have the appearance of a scaffold-
like frame structure, with offices and work areas attached to the outside of the frame.
Drydocks are mobile and can be moved from place-to-place using Fleet Tugs since they
do not contain their own propulsion system.
Starships and craft will enter the structure and moor within it. An enclosed brow will be
attached to the ship at a convenient external hatch for access between the ship and the
dock, as well as to provide shore power and other utility connections. An officer of the
Engineering Corps who reports directly to the Area Commander generally commands
a Mobile Drydock, but it is the Area Commander who will determine which ship will
undergo refitting or that has priority to use the facility. Some of the very large Starbase
facilities may have two flag commanders - the Base Commander and the Facility
Commander[7]. In this situation the Base Commander has authority over the base
facility and everything within his or her Jurisdictional Authority. Whereas, the Facility
Commander has authority only over the repair facilities and the vessels that are
undergoing repair or refit. However, the Facility Commander will report to the Base
Commander on all administrative matters concerning facility personnel that may be on
the base or those operations that may involve the base. It should be noted that repair
facility personnel will normally live on the base and therefore, will be under administrative
discipline of the Base Commander.

VOLUME II
DIPLOMATIC AND CONSULAR ACTIVITIES
Each Star Fleet base or station represents the Federation government in open space
and therefore, are considered as consulates in their own right. As such, Federation
citizens in their travels in deep space can utilize these facilities for official Federation
business or for aid.
Some Star Fleet bases may have embassies, which are permanent Diplomatic Missions
provided by the Federation Council. These embassies are typically located on System
Bases constructed on non-member worlds. The function of these embassies is to protect
the interests of the Federation and the citizens that are located within the system, all
within the limits permitted by interplanetary and galactic law. These embassies negotiate
with the host government concerning matters of law and policy, and in ascertaining, by
lawful means, conditions and developments within the non-member system, and reporting
thereon to the Federation Council. Their primary function is to promote friendly relations
between the Federation, Star Fleet and the receiving system, and to aid in the advance
of economic, cultural and scientific relations between the Federation and the non-aligned
system.
In addition, ARTICLE 29 of the Charter clearly provides Star Fleet with the authority to
settle disputes between social systems within the boundaries of the Federation when no
Federation diplomat is available to settle the dispute. As such, Star Fleet bases and
stations may be used to settle such disputes. They will act as neutral territory from which
treaties and agreements may be negotiated and signed. And although the Federation and
Star Fleet do not have the authority to settle disputes that occur outside Federation
space, Star Fleet bases may also be used as neutral ground from which external disputes
may be settled between the parties.
In fulfillment of the above authority, each Star Fleet base and station will have a Space
Sector Representative, also called a Fleet Representative (FLTREP), assigned to
them by the Star Fleet Bureau of Consular Affairs (BUCONAF) for the purpose of
performing the consular duties to which Star Fleet is empowered under ARTICLES 7 and
29 of the Star Fleet Charter. The Space Sector Representative is the chief liaison to
member and non-member worlds of the Federation and will represent Star Fleet in all
matters pertaining to its consular role in that region. The Space Sector Representative
reports directly to the Sector Representative (SECREP), who is the officer in charge of
all FLTREPs in the octant and who reports to the Sector Commandant regarding all
consular activities within the octant.
In addition, those Starbases and Regional Headquarters that have embassies may
contain a Federation Consul. These persons are in effect Federation Ambassadors
assigned by the Department of Foreign Relations within the Federation Council to
perform such work. Each Consul, in turn, reports directly to the Sector Federation
Consul (FEDADM), who is the primary civilian ambassador to the various Federation
and foreign governments within or adjacent to the sector and who acts as council to the
Sector Commandant on all matters pertaining thereto. The FEDADM is a person with
extensive knowledge of the laws, treaties and agreements with the Federation worlds
within the sector and of the foreign worlds outside the Federation, and will work with
Federation and foreign ambassadors and diplomatic personnel during peace negotiations
within and external to the Federation. The Sector Federation Consul reports directly
to the Star Fleet Consul General (SFCCG) and as such, will have direct access to the
Director: Star Fleet Command.

VOLUME II
REGIONAL TRAINING
Technical training of Starship personnel regarding specific ship systems or equipment is

generally performed onboard the ship. However, for advanced, detailed or upgraded
training, Star Fleet bases contain the facilities needed to provide such advanced training
through their Star Fleet Training Centers and Fleet Schools.
A Star Fleet Training Center is a large base facility containing several types of schools
designed to provide initial and advanced training in many fields of specialization. These are
campuses containing many buildings dedicated to specific specialties such as propulsion,
communications, navigation and auxiliary equipment. As such, these Star Fleet Training
Centers are primarily designed for enlisted personnel in pursuit of their specialty.
Fleet Schools, on the other hand, are smaller facilities providing only limited areas of
specialization. These facilities are generally located within smaller Star Fleet bases and
stations. They are primarily designed for more highly specialized training within a field, or
as schools to update or enhance an individual’s knowledge within their area of expertise or
for training on a specific piece of equipment.
The Star Fleet Division of Education also manages the many Fleet Training Centers
that are spread out across the Federation. The function of these centers is to provide
concentrated and specific training on particular ship and base systems and machinery,
thus providing technical personnel with in-depth knowledge of Star Fleet equipment as
required under ARTICLE 56 of the Charter. In addition, these training centers also provide
such schools and classes whereby personnel can earn credits towards a bachelor’s degree
or higher, and where enlisted personnel may be trained to become commissioned officers,
or where officers may become Commanding Officers.
Most Star Fleet bases also contain Induction Centers for the processing of enlisted or
conscripted personnel. At an Induction Center inductees will go through the examination
process to verify eligibility before being sent to a nearby Star Fleet Recruit Training
facility. Upon successful processing of the inductee, the individual will then report to the
Star Fleet Recruit Training Command facility located at the base. From this point
forward the specifics of recruit training will be covered in more detail within Chapter 8 of
Volume III of the Star Fleet Command Manual.
Besides recruit and fleet training, some of the major Star Fleet Headquarters will also
provide professional and continuing education through a Star Fleet Academy Annex.
Although the main facility of the Academy is located in San Francisco on Earth, the
Academy also maintains many annexes located throughout the Federation and on the
home worlds of the original signatories to the Articles of Federation. All such annexes
are managed by the Star Fleet Academy Annex Command, which coordinates and
standardizes the degree requirements and programs at each of these annexes. As such,
the manpower levels of the Star Fleet Officer Corps can be preserved through these
annexes. In addition, Academy annexes, located physically at Star Fleet bases, can also
be used to further the professional education of individuals within the Department of the
Star Fleet to both Service and civilian personnel.

VOLUME II
7.3 STAR FLEET BASES

As previously stated, the primary function of Star Fleet Operations is the command and
management of the Operating Forces of Star Fleet. In support of this role, Star Fleet
is tasked under ARTICLES 65 and 73 of the Star Fleet Charter with constructing bases,
stations and outposts designed to extend the coverage of its command authority to the
outer reaches of Federation space. As such, Star Fleet Operations was charged with
building and maintaining such command and control centers throughout the Federation,
which will comprise the bulk of the Shore Establishment. The specific organization
tasked with this responsibility was Star Base Command.
SHORE ORGANIZATION STANDARD
The Star Fleet Charter defines the various units, by their size and function, that will
comprise the Shore Establishment. As such, and in accordance with ARTICLE 66 of the
Charter, Star Fleet bases and stations are organized into specific operational units. Star
Fleet Command has established the following definitions for the organization of Star
Fleet bases:
Table 2a73.1
SHORE ESTABLISHMENT STANDARD
Commander in Chief
Unit Definition
Title Rank
The largest organized Shore Establishment unit. A base may Commander:
be either an installation built upon a planet or other body in Star Fleet
Rear Admiral
space, or as a large self-contained vessel orbiting or floating in Headquarters
Base free space. The definition of a base also includes District <Planet>
Headquarters as well. Standard bases within octants and
sectors used for the purpose of command and control, and Commander:
Commodore
support of the fleet are called Starbases. Starbase <n>
A moderately sized base containing Star Fleet troops. Commander:
Garrison Garrisons are generally installations built upon a planet, Star Fleet Commodore
asteroid or other celestial body in space. Garrison <n>
A smaller, specialized Star Fleet base. All stations are self- Commander:
Station contained vessels either orbiting around a planet or celestial Star Fleet Captain
body, or are free-floating in open space. Station <n>
A moderately sized station for the purposes of supporting the
Commander: Commodore -
Facility fleet. Generally, facilities will come under the command of Star
<X> Facility <n> Commander
Fleet Engineering
A small station at the boundaries of Federation space.
Commander: Star
Outposts are self-contained stations, or installations built upon
Outpost Fleet Outpost Commander
or within a small planetoid, asteroid or other celestial body in
<n>
space.

VOLUME II
TYPES OF BASES AND STATIONS
Star Fleet bases and stations are either fixed or stationary installations, usually built upon
planets or large asteroids or planetoids. In this section the definitions and characteristics of
Star Fleet bases and stations will be presented.
Star Fleet defines a “Base” as a fixed ground facility, center, reservation or installation
directly owned and operated by and for the Department of the Star Fleet that shelters
Star Fleet equipment and personnel, and that facilitates operations and training. A base
will also contain large concentrations of supplies and may contain extensive repair facilities
in order to support the Operating Forces. As such, the majority of bases are built on
planets, planetoids or very large asteroids with the exception of Star Base Central, which
is a self-contained artificial structure constructed at the center of the Treaty Zone. In
summary, Star Fleet bases provide accommodations for an operational unit and are used
as regional command and control centers for a specific area of space. Bases are generally
restricted to the general public, and only authorized personnel may have access to them.
There are only two types of Star Fleet ground bases: “Open” and “Closed” or “Self-
contained”. An Open base is one that needs no pressure or atmospheric containment
structures since the base was constructed on a planet with a suitable atmosphere. A Self-
contained base, on the other hand, is built on a planet with a poisonous atmosphere, or
one that has little or no atmosphere, or one where the radiation levels may be too high to
allow continuous exposure. As such, a Self-contained base must erect pressure domes,
shielding or are built as pressurized and shielded structures upon a planet. Typically, Self-
contained bases will be built on such planets for a specific strategic or tactical reason, but
they are rare.
Star Fleet bases are also classified by their location and primary function as well, and are
classified as either “System” or “Fleet” bases. System Bases are large installations built
on worlds that are members of the United Federation of Planets, and are also known
as Regional Star Fleet Headquarters. Besides serving as fleet command centers, they
also act as liaison focal points between member systems and Star Fleet, serve as major
training centers, and as command and coordination centers with Local Forces. Currently,
all System Bases are “Open” type facilities since all of them are located on planets with
an atmosphere. Fleet Bases, on the other hand, are large bases constructed on planets
or planetoids that are uninhabited, or on worlds that are not members of the Federation.
Fleet Bases, officially known as Starbases, serve as the primary regional command and
support center for the fleet in the area. As such, they will typically be located outside the
Treaty Zone, but well within the Federation Exploration Zone.
Each octant of the Federation Exploration Zone will contain one base which will act as
the command center for the entire octant as required under ARTICLE 68 of the Star Fleet
Charter. These bases, called Sector Bases, will house the Sector Commandant, the
Fleet Commander and all the administrative offices required to command and control the
octant and therefore, there are eight such bases. All orders and directives issued by Star
Fleet Command will be sent to the Sector Base for dissemination among the forces
within that octant.

VOLUME II
A “Space Station” is an artificial structure designed for life in outer space. Star Fleet
defines a Station as a Self-contained stationary vessel constructed in space and can be
distinguished from other manned vessels by its lack of a propulsion system. Otherwise, a
station shares much of the same systems and functionality as do ships. Space Stations
come in two forms: a) the monolithic station intended to be constructed as a single unit
and launched or constructed in one piece, and b) the modular station in which a core unit
is constructed so that other functional modules may be later added as needed. This type of
station allows for greater flexibility in its operation as modules can be added, removed or
replaced as needed.
Star Fleet Stations are also classified by their location or position in space and are
classified as either: orbital or free-floating stations. Orbital Stations are those that
are placed in an orbit around a planet, moon or other celestial body, and are commonly
found within member systems. They will typically be placed in synchronous orbit in order
to protect a major population center on the surface of the planet, and will act as the
primary center for law enforcement in the area. Free-floating Stations are those that
are constructed out in deep space, away from any planet or celestial body. Free-floating
Stations are generally stationary command platforms and function as command centers
for the forces in the area. They function as relay and support points for the fleet, and are
used to fill a gap in the overall command and control structure between the Starbases
and the Operating Forces operating at the outer edge of Federation space. In either
case, the function of the station will be the same. The difference is simply in need.
STARBASE CENTRAL
Star Base Central is the central headquarters for the entire Star Fleet and was built in
accordance with ARTICLES 67 and 73 of the Star Fleet Charter, which stated: “There
shall be one central base to act as the Star Fleet Command Headquarters that shall be
located at the center of the Federation Treaty Zone.” As such, the base is located at 000-
MARK-000 in the SCS system. The purpose for this base is not only to house the central
administrative offices for Star Fleet, but also to direct the Operating Forces of Star
Fleet from this central location. Having all the offices within this base and separate from
any particular system will allow Star Fleet to maintain a sense of neutrality and as such,
removes any appearance of bias or favoritism towards any particular world or race.
The base itself, as seen in Figure 2a73.1, is a very large self-contained station which is a
combination of the monolithic design along with some modular aspects and was one of the
first bases to be constructed. Base construction started in the year 2214 and took 11 years
to complete.
The base itself is administered and commanded by an officer of line (SBC) tasked with the
responsibility of managing the operations of the base. The officer in command has the title
of “Commander: Starbase Central” or COMCENTBASE and will have the rank of
Commodore. However, unlike all other Star Fleet bases and stations, the commander of
Star Base Central does not report to Star Fleet Operations, but directly to the Star
Fleet Chief of Staff.

VOLUME II
STAR FLEET HEADQUARTERS
Star Fleet Headquarters are large “System Bases” built on the member worlds of the
United Federation of Planets. They are the Regional or District Headquarters for
the Star Fleet. Since Star Fleet was initially made up of the forces of the five original
member systems it is only fitting that each system be represented within Star Fleet. As
such, there are only five District Headquarters within the entire Federation.
The basic purpose and functions for such headquarters are:
1. To keep the five signatory governments working together and to provide consistency
regarding Federation and Star Fleet policy. In essence, these headquarters have a
political purpose to them.
2. To function as liaison between Star Fleet, the Federation and the member systems,
and to function as the point of contact for the commanders of the Local Forces. As
such, these bases will be the headquarters for the Local Force Liaison Officers, or
FORCEREPS, as well.
3. To function as the primary source of recruits and the center for recruit training, as well
as for fleet and specialty training. As such, these bases are equipped with extensive
recruit and fleet training facilities. In addition, all Star Fleet Headquarters will also
have annexes to the Star Fleet Academy.
All five of these District Headquarters are located inside the Treaty Zone. There are
no such headquarters outside in the Exploration Zone at this time. The Jurisdictional
Authority of these headquarters encompasses only the area that surrounds the base
because the base is situated on a member world. Therefore, Jurisdictional Authority for
the space around the world resides with the Local Force.
All Star Fleet Headquarters will have a registry number with a prefix of “SFHQ” as
specified in Star Fleet Regulation 2500. In addition, Star Fleet Headquarters will
also be identified by the planet or system they are located. An example of such a base is
that of Star Fleet Headquarters Earth, which is shown in Figure 2a73.2 and the first of
such headquarters to be built. Designed as SFHQ1, it is a very large facility containing
military housing for Service personnel and their families, dining halls, hospitals, churches,
gyms, and other types of recreational facilities (such as sports courts, schools, parks, etc).
In addition, this particular base is also home to the Star Fleet Academy – the primary
training facility for Star Fleet officers. All other such headquarters will only have annexes
to the Academy.
The commander of such headquarters will be designated: Commander: Star Fleet

Headquarters <Member Planet> or COM<System Name>. For example, the
Commander: Star Fleet Headquarters Earth will be designated COMSOL. However,
since the base commander is also the Star Fleet commander for the region, he will also
be known as the District Commandant. This role is not the same as that of the Sector
Commandant since the District Commandant is restricted only to the forces within the
immediate area. However, the District Commandant is a representative of and acts on
behalf of the Chief of Star Fleet Operations through COMSEC0 as illustrated in Figure
2a32.2. The District Commandant will have the title of Commandant: <Member
System> District (e.g. Commandant: Andor District) and will typically be an officer
of the line (SFC) with the rank of Rear Admiral.

VOLUME II
FLEET STARBASES
Fleet Starbases refer to those bases located outside the Federation Treaty Zone and
within the Federation Exploration Zone. They are collectively called Sector Starbases
since they will be located within an octant or sector of space. However, the term "Sector
Starbase" should not be confused with the term “Sector Base”, which is the term used
to define the central command base for an octant. In summary, all such Fleet or Sector
Starbases are simply referred to as Starbases.
Starbases are military facilities equipped with large fixed weapon systems that are used
primarily for defense. However, being fixed installations, the range of uses for such
weapons is very limited and can only be directed out into space. As such, they cannot be
used against any invading ground force and must rely on other forms of defense to handle
ground attacks. Therefore, Starbases carry a large detachment of ground troops for the
defense of the base. This force will typically be of Division strength, or about 11,000
Marine Corps troops along with their ground attack vehicles. In addition many of the
larger planetary Starbases will also contain large numbers of Attack and Fighter Craft,
which will be assigned to one or more Wings. These craft are not only used for base and
regional protection, but also as a source of replacement craft for the fleet as well.
Although Starbases are also major fleet repair and support facilities, Star Fleet ships are
too large and cannot land on such bases. Instead, most of the large Starbases will have
mobile repair facilities orbiting around the planet the base is located. The base itself will
have extensive shops and facilities for the construction of major ship parts. As such, they
can only transport such parts and pieces to the orbiting facility for installation using utility
service craft.
Each octant of the Federation Exploration Zone contains one base that acts as the
command center for the entire octant as required under ARTICLE 68 of the Star Fleet
Charter, which states: “There shall be a ‘Sector Base’ located in each primary division of
Federation space that will serve as the headquarters for the Sector Commandant and the
Fleet Commander assigned to that area.” These bases are called Sector Bases and house
the Sector Commandant and the Fleet Commander for that region and as such. There
are eight such bases. All orders and directives issued by Star Fleet Command will be
sent to the Sector Base for dissemination among the forces within that octant.
All Starbases will have a registry number assigned to them with a prefix of “SB” and
placed in the Star Fleet Station Register as required by Star Fleet Regulation 2500.
And as with headquarters, all Starbases will also be identified by the planet on which
they are located or the name of the system in which they are located.
Starbases are commanded by a Base Commander, a flag officer of the line (SBC) with
the rank of Commodore, and will have the title of “Commander: Starbase <n>” or
COMBASE<n>. The primary responsibility of the Starbase Commander is the
command and control of the Operating Forces located within his or her area and to act
as Area Commander to the forces within the base’s Jurisdictional Authority.
There are basically two types of Starbases: the large Planetary Starbase and the
Free-floating Command Starbase. Both of these will be described in more detail in the
subsequent paragraphs.

VOLUME II
PLANETARY STARBASES
Planetary Starbases are fixed ground installations built on planets, planetoids and very
large asteroids like the one illustrated in Figure 2a73.3. The majority of the Fleet
Starbases are of this type primarily since they are more economical to build and maintain
than the Free-floating type. To build this type of Starbase only requires a suitable
planetoid and the Star Fleet Corps of Engineers, along with the Star Fleet
Construction Command, will do the rest. It usually takes around two years to build a
basic Starbase and in most cases, the materials used to build the base will be obtained
locally.
A variant of the Planetary Starbase is the Self-contained Planetary Starbase. These

bases are placed on planets with little or no atmosphere, or one that has an unbreathable
or poisonous atmosphere. As such, most of the base will be constructed underground in
pressurized structures or on the surface under pressure domes. However, their usefulness
is limited and therefore, only two such bases exist. For example, one such base, though
not a command Starbase, is the Star Fleet Prison on Elba II.
FREE-FLOATING COMMAND STARBASES
Free-floating Command Starbases are very large self-contained space stations, which
are primarily used for fleet support and command, and area defense. Such bases generally
have extensive and powerful weapons systems and as such, will be constructed or placed
near hostile locations. However, due to their high cost and long construction time, such
bases are rare and only five exist. The primary function of these bases is fleet command
and area protection. These bases have very powerful Phaser weapon systems that are
more than 11 times more powerful than the Main Batteries of a Battleship. These
weapons have an effective range of over 500,000 km. A single burst from one of these
Phasers can completely destroy a large shielded space cruiser 500,000 km away. A prime
example of such a base is Starbase 1, as shown in Figure 2a73.4.

VOLUME II
STAR FLEET STATIONS
Star Fleet Stations are smaller self-contained space stations floating freely in space.
They serve as command centers for the fleet within a sector, but are limited in their
support capabilities. However, there are some very large stations that are capable of fully
supporting the fleet. Stations are generally assembled out in deep space, somewhere
between the outer edge of Federation space and the Starbases located deep within
Federation territory. They are the third layer of fleet command and are the relay points
for the central command. Star Fleet Stations also serve as regional law-enforcement
centers with courts to adjudicate cases involving the violation of Federation law in that
region, as well as for military courts-martial. In addition, these stations act as rest areas
for Starship crews and contain small shops and recreation areas for the crews to utilize.
All Star Fleet Stations have a designation or registry number with a prefix of “SSN” as
required by Star Fleet Regulation 2500. In addition, Star Fleet Stations may also be
named based upon the system in which they are located or the planet around which they
are orbiting.
The most common design of the Star Fleet Station is the Free-floating Y-nodal design
as pictured in Figure 2a73.6. The Y-nodal is essentially a monolithic station consisting of a
central command module (node) and three service nodes radiating out from the central
module. The central node contains all the command offices, engineering, power, service
and storage areas. The three radial nodes are divided into functional units: one for housing
base personnel, one for housing visiting commands and dignitaries, and the last one
containing facilities for other station functions such as brigs, courts and consulates. Finally,
these stations will also have a lower Hanger Bay node for station and visiting shuttlecraft.
This type of station is primarily used for fleet support and communication. They act as
command relay centers for the fleet and fill the gap in communications between the larger
Starbases and the forces operating at the far reaches of Federation space. They are
generally placed out in deep space away from any star system. In addition, they have
powerful weapons systems and carry both Phaser and Photon Torpedoes. The power of
their Phaser weapons is about four times the equivalent of that of a Battleship class
Starship.
The other form of a Star Fleet Station is the Modular Command Station, designated
as STMP, as illustrated in Figure 2a73.5. There are 16 of these types of stations currently
in operation. The advantage of this design is its extensibility – the allowance of the design
to expand as needed without significantly disrupting the existing structure. Most of these
bases are orbital stations that act as administrative headquarters for nearby Drydocks
and other deep-space repair facilities. Unlike the Free-floating type, this type will have
minimal weapons systems since they are primarily administrative stations. A hybrid
between the two types of stations is the Free-floating Modular station. This type of
station design will typically be used for deep-space communications stations, such as the
one shown in Figure 2a73.8. This type of design allows for the expansion of its
transmission grid as Federation space near the station expands further out.
Star Fleet Stations are commanded by a Station Commander, an officer of the line
(SBC) with the rank of Captain, and will have the title of “Commander: Star Fleet
Station <n>” and a designation of COMSTATION<n>. The primary function of the
Station Commander is to support the fleet, represent Star Fleet Command in the far
reaches of space and to function as Area Commander to the forces assigned within the
station’s Jurisdictional Authority.

VOLUME II
STAR FLEET GARRISONS
The term Garrison comes from the old French word garnison, itself from the verb
garner, "to equip" and is the collective term for a body of troops stationed at a particular
location. Garrisons are permanent Star Fleet bases, usually installed on small planetoids,
containing a large number of Marine Corps troops, usually of Division strength or
approximately 11,700. In addition to the troops the garrison will also contain around 150
Star Base Command personnel who manage and maintain the base, and who support
the troops.
The function of the garrison is to provide a source of ground assault forces during times of
war, and will typically be located in the outlying regions of the Federation near trouble
areas. Garrisons are also a source for outpost and deep space station personnel for duty
rotation.
Garrisons have very little fleet support capabilities, concentrating more on housing,
training and supporting the Fleet Marine forces stationed there. However, they are major
supply bases for the equipment and supplies needed to support the ground forces in the
area. As such, Star Fleet ships may take advantage of these resources if necessary. In
addition, Garrisons are also equipped with extensive ground combat training areas where
troops will train and practice in ground combat operations.
Garrisons, like Planetary Starbases, have fixed weapons installations, which are used
for defense only. In addition, these weapons have a limited range in space and are not
effective for ground combat due to their location and their position on the planet. As such,
Garrisons will be assigned a Fighter Wing attached to them in order to broaden their
defensive capabilities. The wing will primarily contain Fighter Craft manned by Star
Fleet Marine Corps pilots for close support of their troops, but will also be used to patrol
the space around the base as well.
In addition, a G-class Ground Assault vessel may also be attached to a Garrison as

well. The function of the Ground Assault ship is to transport the troops from the garrison
to the action. As such, the Garrison will act as the Home Port for the Assault ship. The
Garrison will be home to the troops while not deployed on the ship.
Currently, there are twelve (12) such Garrisons located throughout Federation space.
Some are stand-alone bases, while others are part of a larger base system and may be
located on the same planet as a Starbase, but in a different location. For example, Star
Fleet Headquarters – Earth is located in San Francisco, but there is also a garrison
located in Europe as well.
Star Fleet Garrisons are commanded by a Garrison Commander, a flag officer of the
line (SBC) with the rank of Commodore, and will have the title of “Commander: Star
Fleet Garrison <n>” or COMFLTGAR<n>. The primary responsibility of the Garrison
Commander is to support the Fleet Marine Corps troops assigned to the garrison,
which will be under the command of a Marine Division Commander, an officer of the
line (MMC) with the rank of Rear Admiral or Commodore as well. As such, the Marine
Division Commander has precedence over the Garrison Commander and therefore,
the Garrison Commander works for the Marine Division Commander and will receive
all operational orders from him.

VOLUME II
STAR FLEET OUTPOSTS
Outposts are small Self-contained stations constructed at the edge for Federation
territory or at Federation Neutral Zones and as such, establish the boundaries of
Federation space, or a Buffer or Neutral Zone. Many of them are built deep inside
large asteroids and designated as A type. The B type is small outpost that is built on the
surface of a large asteroid or small planetoid. However, most are small Free-floating
stations or C types. Their primary function is to monitor the boundary and to provide the
first level of defense and communication in case of attack, invasion, incursion or violation
of the boundary. Outposts will also be positioned around Federation Buffer Zones to
monitor compliance with zone restrictions. Outposts that are near Neutral Zones or on
the border of hostile territory will generally be constructed inside relatively large asteroids
and will normally be of the A type (Figure 2a73.7). These asteroids provide an additional
protection from enemy attack since such asteroids are essentially large blocks of iron.
Outposts are also considered “volatile” stations. That is, an Outpost that was placed at a
specific location today may not be active in the future. This is because an Outpost is used
to mark the boundaries of Federation space, which is continuously changing. Typically,
when an Outpost is no longer used or is deactivated it may be sold to a private concern –
stripped of all Star Fleet equipment. However, this does not necessarily apply to the C
type Free-floating Outposts, which can be relocated to another position by Star Fleet
Tugs.
Personnel at these Outposts are generally stationed there for about three months. They
rotate between stations and outposts about every six months. That is, a person assigned
to an Outpost is there for three months, and then rotated to a Starbase for six months
before returning to another Outpost. The relief schedule is scattered so that only a few
Outposts need to have their personnel relieved. This rotational schedule is done on a
quarterly basis and is timed with the required quarterly medical checkups. Starships are
generally used to perform the relief operation when they arrive to perform the quarterly
physicals.
Star Fleet Outpost Commanders are command officers of the line (SBC) with the rank
of Commander, and will have the title of “Commander: Star Fleet Outpost <n>” or
COMFLTPOST<n>. However, for the very small outposts, a line officer with the rank of
Lieutenant Commander may also command such an outpost.
TACTICAL COMMAND STATIONS
Tactical Command Stations or TAC bases are small Free-floating outposts containing
Star Fleet Intelligence and communications personnel. Their function is to act as early
warning outposts and serve as remote fleet intelligence, communications and surveillance
outposts. However, some serve as bases for clandestine or covert operations and missions
as well. The locations of these stations are highly classified and are usually placed in areas
where they will not be easily seen or encountered.
Star Fleet TAC Base Commanders are officers of the line (SBC) with the rank of
Commander, and will have the title of “Commander: Star Fleet Tactical Station
<n>” or COMTACBAS<n>. Due to the classified nature of their mission, TAC Base
Commanders will usually report directly to Star Fleet Command or Star Fleet
Intelligence.

VOLUME II
FLEET SUPPORT FACILITIES
Fleet Support Facilities are basically either Free-floating fixed or mobile installations
whose primary function it is to perform repairs or to construct Star Fleet ships and craft,
and are usually facilities of the Star Fleet Division of Engineering.
Some of the large Free-floating Starbases have internal moorings for ships. These
moorings are called “Space Docks”, which are contained within the structure of the base,
but not necessarily pressurized. The mooring stations will have moveable brows that will
attach to the vessel for personnel and equipment entry and egress.
Ship building facilities are large floating or orbital stations that can accommodate the
construction of six ships simultaneously. They have large gantry cranes and arms to lift
and position large sections of a ship. The ship’s keel is locked to a Docking Bay while the
ship is being built or repaired. The ship is connected to the facility by a Keelway, which is
a large cylindrical tube connecting the ship with the station that contains an elevator, and
electrical and service umbilicals. The Keelway allows personnel to travel between the ship
and the facility using fast Turbo-lift elevators. This system is incorporated into the design
of most Star Fleet ships so that whenever a major repair must be performed utilizing a
construction facility, the Keelway will provide anchorage and access without the need for
special equipment.
Drydocks are stationary frames free-floating in space into which vessels are anchored or
moored. Such Drydocks contain offices and workshops that can fabricate most of the
smaller pieces of equipment. However, large sections of a ship, such as the main engines
or its parts, must be hauled to and from the Drydock. In addition, support facilities also
include Mobile Repair stations as well. Mobile Repair facilities are similar to Drydocks
in design except that they are mobile.
The commander of a Star Fleet ship repair facility will typically be a Staff Corps officer
from the Engineering or Construction Corps (ENG or CNT), and their rank will range
from Commander to Commodore, depending on the size and function of the facility.
They will usually have a title of “Commander: Star Fleet Ship <Type> Facility<n>,”
or simply COMSHIPFAC<n>.
SUBSPACE RELAY STATIONS
Subspace Relay Stations are part of the overall communications network of Star Fleet.
Subspace Relay Stations are not manned bases or stations per se, but are Star Fleet
assets that come under the authority of the Sector Commandant of the octant the relay
station has been placed. Although typically unmanned, relay stations are large enough to
include simple quarters for extended stays, usually for repair and calibration.
Because such stations are usually unmanned, there is no assigned Commanding Officer.
The officer responsible for the proper functioning and maintenance of sector relay stations
will be the Sector Communications Officer or COMSECCOM. However, the placement
of these stations, the calibration and the setting of frequencies is the responsibility of the
Star Fleet Office of Fleet Communications.

VOLUME II
Figure 2a73.1
STAR BASE CENTRAL

VOLUME II
Figure 2a73.2
STAR FLEET HEADQUARTERS: EARTH

VOLUME II
Figure 2a73.3
FLEET STARBASE: STARBASE 11

VOLUME II
Figure 2a73.4
SELF-CONTAINED STARBASE: STARBASE ONE

VOLUME II
Figure 2a73.5
STAR FLEET ORBITAL STATION: EPSILON STATION (SSN-26)

VOLUME II
Figure 2a73.6
STAR FLEET FREE-FLOATING STATION: CARINAE STATION (SSN-20)

VOLUME II
Figure 2a73.7
STAR FLEET OUTPOST: OUTPOST FIVE

VOLUME II
Figure 2a73.8
TYPICAL STAR FLEET COMMUNICATIONS STATION

VOLUME II
7.4 STAR FLEET BASE PLACEMENT

As previous stated, bases and stations are important links in the overall command and
control infrastructure for the Star Fleet. They serve as extensions to the central command
structure by acting as relay points at which fleet operational directives can be transmitted
to the command units at the fringes of Federation space, and as points of replenishment
for the Operating Forces they serve. As such, the location of such bases and stations is
important to Star Fleet. Therefore, the assignment of any base or station to a sector or
region of space will greatly depend upon tactical, strategic, logistical and other factors.
These factors can be summarized below:
 The amount of commercial and private space traffic in an area

 The location of hostile neighbors and forces and therefore, the need for a significant
force presence
 The location of Neutral and Buffer Zones that will require monitoring
 The number of populated worlds in a region of Federation space
 The extent of space exploration and the force size needed to maintain and protect the
new areas of space
 The number of outlying colonies and settlements that will need support and protection
 Subspace and other communications restrictions
Star Fleet basically defines Shore Facilities as the various installations built on inhabited
or uninhabited planets. These are typically large ground stations used for the command of
the forces within a large area of Federation space. ARTICLE 23 of the Charter gives Star
Fleet the authority to construct such shore facilities within the following restrictions:
1. That the location of the facility is outside the boundaries of member systems, and
2. That permission is required of the local system should a base be placed anywhere
within a member system.
Star Fleet was given the authority to construct bases on any planet within Federation
territory that is not specifically within an inhabited system. Some of these bases are self-
contained pressurized structures since the planets on which they were constructed have
little or no atmosphere. However, most planets upon which Star Fleet has established a
base typically has an atmosphere sufficient enough to preclude the need for pressurized
containment.
Many of the member system home worlds have Star Fleet bases, primarily because the
system has a Local Force. These bases are essentially command centers for joint force
operations. As such, both Star Fleet and Local Forces are stationed at these bases,
which are classified Star Fleet Command Headquarters. One such Headquarters is
located in the city of San Francisco on Earth with the title: Star Fleet Headquarters –
Earth. In most cases where Star Fleet has established a base a lease is not required.
That is, Star Fleet does not pay a fee to the local government for the use of the land.
However, there are some worlds, specifically non-member planets, where Star Fleet has
a lease agreement with the local government. In such cases the Federation Council
manages such agreements.

VOLUME II
AUTHORITY TO CONSTRUCT SPACE STATIONS
The authority to build space stations is specified in ARTICLES 16 and 23 of the Charter,
and it is ARTICLE 73 that directs Star Fleet to construct such stations. The construction of
Star Fleet bases and stations will fall under the purview of the Star Fleet Construction
Command, a subdivision of the Star Fleet Division of Engineering. The larger stations
will typically be constructed at the selected site, with supplies and materials shipped in via
the Star Fleet Transportation Command. While construction is taking place workers
will reside in mobile housing units that were towed to the site by Fleet Tugs of the Star
Fleet Transportation Command. However, the smaller stations will generally be built at
Star Fleet Construction Facilities and towed to the sight by such Star Fleet tugs.
Typically, these stations will be built or placed in strategic areas around the Federation.
They essentially act as relay stations for the transmission of Star Fleet Command orders
and directives, as repair facilities and as replenishment points. They also act as short-term
rest and recreation facilities as well. That is, the location of these stations is important to
Star Fleet for tactical and strategic reasons and therefore, Star Fleet is given complete
freedom and authority to select the location of space stations and to construct such
stations at the locations selected.

VOLUME II
DETERMINING BASE AND STATION LOCATIONS
As previously stated, Star Fleet was given complete freedom and authority to select the
location of its bases and stations. This authority was conferred upon Star Fleet under
ARTICLES 16 and 23 of the Star Fleet Charter. The organization within Star Fleet that
was specifically given the responsibility of selecting the location of Star Fleet bases and
stations is the Star Fleet Office of Strategic Planning (SFPLAN).
The principal function of the Star Fleet Office of Strategic Planning is to establish the
strategic direction for Star Fleet and the Federation, which includes the placement of
bases and stations at strategic locations. Therefore, as part of its function this office will be
involved in initiating, planning and supervising the base and station site selection process
and will be responsible for surveying and selecting the location of Star Fleet bases and
stations in accordance with ARTICLE 23 of the Star Fleet Charter.
The process generally begins by determining a need for a new base or station, which will
be based upon the criteria stated earlier and the general area of space in which the base
will be placed. The next step will be to prepare a survey team to investigate possible sites
within the preferred area of space. The team will examine any reports that may already
exist regarding the star systems and planets located within the region of space under
consideration. If no such reports exist, SFPLAN will request a survey to be performed by
the Star Fleet Space Exploration Command (XCOM). XCOM will then either initiate a
survey expedition to the requested region of space, or may request Star Ship Command
to assign the nearest Starship to undertake the survey mission.
After analyzing all available information obtained from the survey reports, SFPLAN will
make several selections and will submit their recommendations to the Director: Star
Fleet Command and the Federation Council for review and approval as required under
Paragraph 3 of ARTICLE 52 of the Articles of Federation. Where the selection of a base
site may be an inhabited world of the Federation, SFPLAN will initiate agreements for
the establishment of such bases or stations within or upon sovereign territory. This office
was given the authority to negotiate the terms of such agreements, but must submit such
agreements to the Judge Advocate General’s office for legal review and endorsement.
Upon approval of the selected site and the completion of any negotiations that may have
been necessary concerning the site, construction of the base may begin.

VOLUME II
RULES GOVERNING SITE SELECTION
In general, Star Fleet has unrestricted authority to select and construct bases anywhere
in Federation space except within member systems. However, that does not imply that
Star Fleet bases or stations cannot be constructed or placed within a member system. On
the contrary, Star Fleet was given the authority to construct bases within member space
so long as the following conditions are met:
a. Should Star Fleet decide that the best place to locate a base or station is within a
member system, Star Fleet requires only written permission from the local system
government to place such a base within that system. Such an agreement would go
through the Federation Council for review and approval.
b. Should Star Fleet decide that the best place to locate a base or station is on an
uninhabited planet or moon within a member system Star Fleet, again, would only
require written permission from the local system government to place such a base
within the affected system.
c. Should Star Fleet decide that the best place to locate a base or station is on an
inhabited planet of or the home planet of a member system, Star Fleet would not
only require written permission from the local system government to place such a base
on the world, but may also be required to pay for the use of the land area the base
will be located. In such instances, the leased area occupied by the base becomes Star
Fleet property and thus, the local government would be restricted from any access to
the facility and would require permission from the Base Commander or from Star
Fleet Command to obtain access to the facility.
d. Star Fleet cannot build or place bases or stations on any inhabited world within the
Trusteeship System, but has unrestricted authority to place its bases and stations
anywhere else within the Trusteeship System that is uninhabited, which includes the
installation of an orbiting station around the planet under Trust. Such Trust areas will
generally be isolated from the rest of the Federation by imposing a Social Buffer
Zone around it. Therefore, as part of its function and responsibility to monitor such
zones, Star Fleet may place a base or station inside the zone, but not on the planet
under trusteeship.
In general, it is incumbent upon the member systems to cooperate with Star Fleet in the
selection of sites within their respective systems as required in ARTICLE 49 of the Articles
of Federation. This is usually not a problem and the only source of issues in the past has
been with locating bases in non-member systems, since they are not signatory worlds to
the Articles of Federation and therefore, do not have an obligation to allow Star Fleet
facilities or ships within their system. However, agreements similar to those established in
Paragraph c above have usually been successfully implemented, along with provisions that
Star Fleet provide protection to the non-member system.

VOLUME II
BASE TYPE AND SIZE DETERMINATION
The type and size of the base or station to be constructed at a particular selected site will
depend on local conditions. The requirements for the type and size of the base or station
may depend on several factors such as:
1. Space traffic density, both commercial and private. This will determine the size of the
station that will be required. Stations are only required in these areas for space traffic
control and monitoring. These areas are primarily law enforcement zones and are not
military zones where troops may be needed requiring a large base to support them. In
this situation a free-floating station would best fit this need.
2. The strength of nearby hostile forces will determine the force size and troop levels that
will be needed to deter war or conflict. As a rule, Fleet Starbases will be constructed
in these regions to house troops, repair ships and to generally support a large number
of combatants. In this situation a Star Fleet Garrison would most likely be located in
the area.
3. The type of planet that can support a base of a specific design will also determine the
type of base that will be constructed. There are only two types of bases that can be
constructed on a planet or large asteroid: Open and Self-contained. An Open base
is one that needs no pressure structures since the base is constructed on a planet with
an atmosphere, while a Self-contained base will be constructed on a planet with an
unbreathable or noxious atmosphere or one that has no atmosphere at all. Therefore,
such a base will require pressure domes or other enclosures. However, this type is
extremely rare and will typically be used only for Star Fleet prisons.
4. The number of Star Fleet ships that operate within the area will determine the type
and size of the base or station. In areas of space where a significant number of Star
Fleet ships will require support, a free-floating station may be required or a Fleet
Starbase with an attached repair facility.
5. Whether a base or station is required within a member system of the Federation. For
example, a station may be required in a system where Star Fleet has an arrangement
with the local government to supply security services or to act as the Local Force for
the system. In such cases, an orbiting station around the home planet may be in
order, or a large ground facility may be needed in the case of a largely populated
system.

VOLUME II
CONSTRUCTION OF BASES AND STATIONS
ARTICLE 65 of the Charter gives Star Fleet the authority to physically construct bases and
stations at the sites selected. The first step in this process is to develop the construction
requirements for the base. This will customarily be performed by the Office of Star Fleet
Base Requirements (SBCREQ), which is principally responsible for determining the
design and operating requirements of all bases and stations. The design requirements for
construction of the facility will include such things as the structural requirements, the
offensive and defensive needs of the facility, and the manpower required to operate and
maintain the facility. The final requirements for the construction of the base will then be
submitted to both, the Star Fleet Corps of Engineers (ENGCOR) and the Star Base
Systems Command (STARBASES). These two subdivisions of the Star Fleet Division
of Engineering will develop and create the design and construction plans for any new
base or station.
The actual construction of Star Fleet bases and stations falls under the purview of the
Star Fleet Construction Command within the Star Fleet Division of Engineering.
The larger stations are typically constructed at the selection site, with supplies and
materials shipped in by the Star Fleet Transportation Command. As construction
begins a mobile housing unit will be towed to the site for the construction workers. The
smaller stations are usually built at Star Fleet Construction Facilities and then towed
to the sight by Star Fleet tugs.

VOLUME II
7.5 CURRENT STAR FLEET BASE

LOCATIONS
Distributed throughout the Federation Exploration Zone are five Regional Star Fleet
Headquarters, twenty-eight major Starbases, forty-one Star Fleet Stations, sixty-
eight Outposts, twelve Garrisons, fifty-nine fleet support facilities and one central
command base for a total of 214 facilities. These bases function as the command centers
for the fleet and as such, provide the communications link between Star Fleet Command
and the Operating Forces at the outer rim of Federation space.
In this section the location of the various bases, stations and outposts will be presented.
The information contained herein is classified CONFIDENTIAL and shall be treated in
accordance with the guidelines set forth in the Star Fleet Manual for Classified
Information. In addition, facilities such as Communications, Intelligence and TAC
stations will not be identified as their locations are highly classified.
STAR BASE CENTRAL
At the very center of the Treaty Zone or Sector 001, and therefore the United
Federation of Planets, is Star Base Central, a large self-contained station containing
all the offices for Star Fleet Command. From this central base the entire operation of
Star Fleet will be managed. An image of Star Base Central can be seen in Figure
2a73.1.
As stated, Star Base Central is located at the center of the Federation at 000-MARK-
000 and is designated SFHQ0. The base contains approximately 4500 Star Fleet
personnel, 2600 of which are a mixture of Star Fleet Command personnel, Star Fleet
Security personnel and Star Base Command personnel assigned to operate and
maintain the base. In addition, there are two Battalions or approximately 1900 Star
Fleet Marine Corps troops stationed at the base to comprise the local area security
force.

VOLUME II
STAR FLEET HEADQUARTERS
Scattered throughout the Treaty Zone are five major Star Fleet bases located on the
signatory worlds to the Articles of Federation. These bases are known as System
Bases by classification, but are usually referred to as district “Star Fleet Headquarters”.
Each of these five Star Fleet Headquarters defines a specific Star Fleet District as
described in Section 3.2 of this volume.
As stated in Section 3.2 a Star Fleet District is defined as a region of Federation space
encompassing any one of the five Star Fleet Headquarters. That is, each of the five
original signatories of the Articles of Federation who had originally adjoined all or a
portion of their forces to create the Star Fleet and that has a representative sitting on the
Federation Joint Chiefs of Staff (see Figure 1a14.1 in Volume I) will have a Star Fleet
Command office located on their home world. All five of these Star Fleet Headquarters
and their associated Districts are located only within the Federation Treaty Zone. All
stations, worlds and spacecraft operating within any one of these districts will come under
the authority of the District Commandant, with the exception of the home world on
which the base is located. An illustration of the locations of these district bases can be
seen in Figures 2a32.1 and 2a75.1.
Other forms of Star Fleet Headquarters are the various System Starbases built on
worlds that are members of the Federation, but who were not the original signatories of
the Articles. They have a similar function as the District Star Fleet Headquarters, but
also serve as area fleet command centers, function as liaison between member system and
Star Fleet, serve as major training centers and as command and control centers for the
Local Forces.
As stated above, System Bases are large ground facilities located on a home world of a
Federation member. These bases are primarily administrative facilities that may contain
both Star Fleet and Local Forces, which act as liaison points between the member
government and Star Fleet. However, these types of bases are not what are commonly
known as Starbases.
Table 2a75.1
TABLE OF STAR FLEET HEADQUARTERS
Registry
SCS Location Personnel
Number Base Name Distance
Vector (ly)
Octant Sector Stationed Troop Force
Star Fleet Headquarters

SFHQ1 272-MARK-018 2.1 0 001 2650 4000
Earth
SFHQ2 309-MARK-337 5.2 0 009 2260 3900
Alpha Centauri
SFHQ3 024-MARK-324 10.9 0 006 2470 3950
Andor
SFHQ4 060-MARK-065 11.1 0 002 2440 3800
Tellar
SFHQ5 152-MARK-328 14.7 0 007 2180 3910
Rigel

VOLUME II
STAR FLEET BASES
Starbases are the basic command and control centers outside the Treaty Zone and are
the largest type of base within the Star Fleet Shore Establishment. They are typically
stationary structures constructed on planets, planetoids or very large asteroids. There are
basically two types of Starbases: Fleet Starbases and System Starbases. Fleet
Starbases are large facilities constructed on planets or planetoids that are uninhabited or
on a world that is not a member of the Federation. System Bases, on the other hand,
are large ground facilities located on a home world of a Federation member. These bases
are primarily administrative facilities that may contain both Star Fleet and Local forces.
Both types of bases serve as major command and support centers for the fleet, and the
commanders of such facilities will typically be the Area Commander for the sector. A
mapping of the locations of Starbases may be found in Figure 2a75.2.
Table 2a75.2
TABLE OF STAR FLEET BASES
Registry
Vector (ly)
2
SB1 Starbase 1 012-MARK-035 19.2 1 002 1,590 6,000
SB2 Starbase 21 137-MARK-044 24.0 2 13C 4,200 3,900
SB3 Starbase 31 247-MARK-029 31.9 3 15-0 2,800 3,800
SB4 Starbase 41 318-MARK-056 36.3 4 25Y 4,200 5,800
SB5 Starbase 51 016-MARK-300 23.1 5 34D 4,000 6,000
1
SB6 Starbase 6 162-MARK-327 28.0 6 29P 4,200 5,800
SB7 Starbase 71 197-MARK-355 59.4 7 114U 5,000 11,720
SB8 Starbase 81 344-MARK-319 39.0 8 33X 4,200 5,800
SB9 Starbase 91 018-MARK-032 49.9 1 58N 5,000 11,720
SB10 Starbase 10 117-MARK-071 48.8 2 95Q 4,500 12,000
SB11 Starbase 11 204-MARK-042 68.0 3 231L 5,000 11,720
SB12 Starbase 12 124-MARK-344 69.2 6 346K 5,000 11,720
SB13 Starbase 132 035-MARK-321 65.7 5 364A 1,600 6,500
SB14 Starbase 14 291-MARK-026 87.0 4 547O 4,300 11,720
SB15 Starbase 15 240-MARK-332 91.2 7 799-0 5,200 11,720
SB16 Starbase 16 301-MARK-337 60.0 8 135T 3,400 10,000
SB17 Starbase 172 069-MARK-041 114.0 1 1120W 1,300 3,340
2
SB18 Starbase 18 149-MARK-082 100.5 2 1272G 1,000 1,800
SB19 Starbase 19 257-MARK-068 103.3 3 1211E 5,000 11,720
SB20 Starbase 20 337-MARK-016 122.0 4 1695D 4,500 9,200
SB21 Starbase 21 062-MARK-322 138.2 5 2184U 5,000 11,720
3
SB23 Starbase 23 186-MARK-325 140.7 7 3210F 633 N/A
SB25 Starbase 25 044-MARK-038 96.3 1 557V 5,000 11,720
SB26 Starbase 263 148-MARK-324 126.7 6 2154H 800 750
SB27 Starbase 27 128-MARK-009 155.5 2 2483Y 4,200 11,720
SB28 Starbase 28 310-MARK-070 176.2 4 4178S 2,200 3,600
Notes
1. Indicates that the base is a Sector Base – headquarters for the Sector Commandant.
2. Closed; free-floating Starbase.
3. Closed; domed planetary Starbase.

VOLUME II
STAR FLEET GARRISONS
Garrisons are smaller ground Starbases that are primarily used to house Star Fleet
troops and will normally be located near the edge of Federation space. Garrisons have
very little fleet support capabilities, focused more on housing, training and supporting the
Fleet Marine forces. There will generally be a small company of Star Base Command
personnel stationed at Garrisons, typically around 150, but the bulk of the personnel
stationed at a Garrison will be Star Fleet Marine Corps troops. The typical force size
stationed at the base will be of division strength or approximately 12,000 troops.
Garrisons are generally placed near areas where conflict will most likely occur. As such,
Garrisons are more likely to become temporary installations rather than permanent ones.
That is, as political and tactical situations change the need for the base will also change.
Figure 2a75.3 shows the current location of Star Fleet Garrisons.
Although still listed, the garrison on Cestus III was destroyed by elements of the Gorn
Empire in 2267. Fortunately, there were no troops stationed at the time. The garrison had
been recently completed and as such only a handful of base personnel were available at
the time. This small group was stationed there for startup and to make the base ready for
operation before bringing the garrison up to full strength. At this time Star Fleet has no
intention of rebuilding this base as a condition set forth by the Metrons.
Table 2a75.3
TABLE OF STAR FLEET GARRISONS
Registry
Vector (ly)
Star Fleet Garrison –

SGN1 274-MARK-018 2.1 0 001 150 11,720
Earth1
SGN2 Teegarden Garrison 139-MARK-001 11.1 2 003 125 12,000
SGN3 Hamal Garrison 126-MARK-009 64.4 2 178A 133 11,500
SGN4 Canaris III Garrison 074-MARK-040 36.9 1 11T 154 11,750
SGN5 Ceti Garrison 103-MARK-351 94.9 6 723Y 132 12,100
SGN6 Xi Bootis Garrison 294-MARK-034 24.0 4 16D 117 11,720
SGN7 UM36 Garrison 222-MARK-037 43.4 3 67F 124 10,780
SGN8 Marsh Garrison 076-MARK-341 124.9 5 2106D 142 11,350
2
SGN9 Cestus III Garrison 039-MARK-011 145.9 1 2471B N/A N/A
SGN10 Marfak Garrison 134-MARK-041 136.3 2 1792V 155 12,500
SGN11 Falcon Garrison 018-MARK-050 143.1 1 2708A 144 11,800
SGN12 Delta Garrison 336-MARK-341 123.6 8 2135C 97 8,700
Notes:
1. Earth Garrison is located on a different continent from Star Fleet Headquarters.
2. Destroyed by forces of the Gorn Empire.

VOLUME II
STAR FLEET STATIONS
Star Fleet Stations are smaller self-contained bases and are usually suspended freely in
space. They serve as command centers for the fleet within a sector, but are limited in their
support capabilities. However, there are some relatively large stations that are capable of
fully supporting the fleet. They are somewhat permanent stations floating in space, but
can be moved if necessary.
Stations are generally assembled deep in space, somewhere between the outer edge of
Federation space and the Starbases that are located deep within Federation territory.
Star Fleet Stations constitute the third layer of fleet command and are relay points for
the central command. Star Fleet Stations also function as regional law-enforcement
centers with courts to adjudicate cases involving the violation of Federation law in that
region, as well as for military courts-martial. In addition, these stations will function as rest
areas for Starship crews since they house small shops and recreation areas for the crews
to utilize. In general, stations are hardly ever assigned as Home Port to any Star Fleet
ship due to their small size and their lack of accommodations for ship crews. However,
certain auxiliary or support ships may be assigned to a station for fleet support purposes.
The locations of the forty-two Star Fleet Stations are illustrated in Figures 2a75.4 and
2a75.5. Figure 2a75.4 presents the locations of all the Star Fleet Stations located within
the Federation Treaty Zone, whereas Figure 2a75.5 will only show the positions of the
stations that are located in the Exploration Zone.
One of the stations was sold to a commercial enterprise and converted into a public deep-
space way station under the provisions of the Organian Peace Treaty of 2267 (Federation
Stardate 21420). Under the Organian Peace Treaty Star Fleet Station 33 (SSN-33),
which was originally used to monitor activities at the Klingon Neutral Zone, was converted
into a neutral deep-space way station, open to all travelers. The station was purchased by
a private concern and renamed Deep Space Station K-7.

VOLUME II
Table 2a75.4
TABLE OF STAR FLEET STATIONS
Registry
Number Station Name Distance
Vector (ly)
SSN1 Barnards Station 334-MARK-035 6.9 4 005 120 250

SSN2 Rigel II Station1 143-MARK-328 8.4 6 007 140 310
SSN3 Sirius Station1 208-MARK-321 8.6 7 008 108 64
SSN4 Sigma Station1 269-MARK-011 16.4 3 004 118 200
SSN5 Wolf Station 102-MARK-004 12.1 2 003 88 N/A
SSN6 Scorpius Station 344-MARK-355 23.5 8 33D 100 80
SSN7 Tarsus Station 128-MARK-351 22.2 6 28E 80 160
SSN8 Alaraph Station 264-MARK-360 38.0 7 31U 120 230
SSN9 Hercules Station1 293-MARK-060 53.5 4 87S 118 240
SSN10 Reticulus Station1 062-MARK-288 38.8 5 35Z 121 250
SSN11 Castor Station 199-MARK-005 52.6 3 50O 120 250
1
SSN12 Iota Station 357-MARK-328 57.8 8 137V 126 250
SSN13 Sagitta Station1 034-MARK-043 57.6 1 59T 83 N/A
SSN14 Alpha Station 132-MARK-077 57.3 2 95V 120 250
SSN15 Beta Station1 126-MARK-016 62.6 2 202H 62 N/A
SSN16 Cetus Station 106-MARK-339 74.9 6 345R 110 200
SSN17 Phi Station1 019-MARK-325 78.1 5 363S 82 160
1
SSN18 Virginia Station 304-MARK-018 98.8 4 517R 120 250
SSN19 Hydra Station 233-MARK-325 70.9 7 377-0 94 180
SSN20 Carinae Station 283-MARK-285 69.6 8 428O 121 252
SSN21 Pegasus Station 073-MARK-043 89.0 1 560L 110 210
SSN22 Draco Station 257-MARK-076 89.1 3 672M 142 330
SSN23 Zebra Station 299-MARK-072 97.2 4 676Z 116 245
SSN24 Lambda Station 065-MARK-317 116.2 5 1444T 124 250
SSN25 Zeta Station 115-MARK-318 103.2 6 1449D 96 166
SSN26 Epsilon Station1 184-MARK-336 127.7 7 2118P 62 80
SSN27 Plax Station1 355-MARK-347 107.1 8 1365L 118 225
SSN28 Delphi Station1 043-MARK-042 121.5 1 1782E 124 300
SSN29 Omega Station 328-MARK-021 108.3 4 1074O 106 192
1
SSN30 Sceptrum Station 150-MARK-320 107.7 6 1453K 80 66
SSN31 Station 31 107-MARK-012 74.0 2 177S 66 188
SSN32 Station 32 118-MARK-031 193.8 2 5457W 142 330
SSN33 Station 332 008-MARK-349 200.7 5 8027H N/A N/A
SSN34 Theta Station 053-MARK-330 131.3 5 2143N 121 300
1
SSN35 Perseus Station 158-MARK-025 132.5 2 1715L 120 250
SSN36 Tania Station1 225-MARK-025 135.5 3 1723S 60 N/A
SSN37 Upsilon Station 321-MARK-335 117.9 8 1398R 132 280
SSN38 Station 38 168-MARK-333 132.9 6 2116P 58 62
SSN39 Aquilae Station 022-MARK-036 171.8 1 3853-0 146 340
SSN40 Station 40 102-MARK-331 173.9 6 4593V 120 260
SSN41 Station 41 220-MARK-335 168.8 7 4556Q 66 180
SSN42 Station 42 085-MARK-335 181.9 5 6292C 121 300
Notes:
1. STMP Type of station.
2. Sold to a private concern under the provisions of the Organian Peace Treaty with the Klingon
Empire and renamed Deep Space Station K-7.

VOLUME II
STAR FLEET OUTPOSTS
Outposts are small stations constructed at the edge for Federation territory or at
Federation Neutral Zones. Their primary function is to monitor the boundary and to
provide the first level of communication in case of attack or invasion. Outposts are also
stationed around Federation Buffer Zones to monitor compliance with zone restrictions.
Outposts that are near Neutral Zones or on the border of hostile territory are generally
constructed inside relatively large asteroids. Such asteroids provide additional protection
from enemy attack since such asteroids are essentially large blocks of iron.
Figure 2a75.6 provides an illustration of the locations of all outposts within Federation
space. As can be seen from this figure, the highest concentration of outposts is in the
areas adjacent to the Romulan and Klingon boundaries. They are essentially used to
monitor the Neutral Zones located there.
Table 2a75.5
TABLE OF STAR FLEET OUTPOSTS
Registry
Vector (ly)
1
SOP1 Outpost 1 111-MARK-014 89.6 2 499O 41 20
SOP2 Outpost 21,2 111-MARK-014 89.6 2 499O 40 20
SOP15 Outpost 15 078-MARK-045 201.1 1 7463G 44 22
Notes:
1. Asteroid or A-type outpost.
2. Destroyed during the Romulan incursion of 2266.

VOLUME II
Table 2a75.5
TABLE OF STAR FLEET OUTPOSTS - CONTINUED
Registry
Vector (ly)

SOP27 Outpost 27 079-MARK-045 201.1 1 7464I 42 20
SOP31 Outpost 31 116-MARK-011 91.9 2 446K 38 20
SOP32 Outpost 32 116-MARK-011 91.9 2 446K 38 20
SOP37 Outpost 37 078-MARK-034 199.1 1 5451S 40 20
SOP41 Outpost 41 118-MARK-010 97.9 2 468T 40 20
SOP42 Outpost 42 122-MARK-008 101.1 2 982C 40 20
SOP43 Outpost 43 125-MARK-006 128.6 2 1631M 40 20
SOP45 Outpost 45 105-MARK-022 201.4 2 7148D 40 20
SOP46 Outpost 46 101-MARK-026 201.5 2 7211F 40 20
SOP50 Outpost 50 087-MARK-039 201.9 1 7401H 40 20
SOP52 Outpost 52 146-MARK-028 174.2 2 3816V 20 10
SOP53 Outpost 53 149-MARK-028 174.3 2 3817Y 20 10
SOP54 Outpost 54 152-MARK-028 174.4 2 3817V 20 10
SOP55 Outpost 55 035-MARK-019 134.2 1 1701W 38 40
SOP57 Outpost 57 043-MARK-016 135.9 1 1662U 36 38
SOP59 Outpost 59 054-MARK-029 200.9 1 7267H 40 20
SOP62 Outpost 62 073-MARK-031 200.7 1 7271B 40 20
SOP67 Outpost 67 168-MARK-304 209.2 6 8631M 20 N/A
SOP68 Outpost 68 171-MARK-303 209.2 6 8632L 22 N/A
Notes:
1. Asteroid or A-type outpost.

VOLUME II
Figure 2a75.1
LOCATION OF STAR FLEET HEADQUARTERS
25 ly
20 ly
15 ly
10 ly
5 ly
1350
Star Fleet Headquarters - Tellar

0 0
180 90
Star Fleet Headquarters -Rigel

0
225 Star Base Central 450
Star Fleet Headquarters - Earth
Star Fleet Headquarters - Alpha Centauri
Star Fleet Headquarters - Andor
0
270 00
Galactic Center
3150
Federation Treaty Zone Sphere

VOLUME II
Figure 2a75.2
LOCATION OF STAR FLEET BASES
250 ly
200 ly
150 ly
100 ly
50 ly
Starbase 18
Romulan Star Empire
Starbase 19
0 0
180 Starbase 27 90
Starbase 11 Starbase 17
Starbase 25 Klingon Empire
Starbase 10
Starbase 28
Starbase 2
Starbase 26
Starbase 12
Starbase 3 Starbase 4 Starbase 1
Gorn
Starbase 23 Starbase 7 Starbase 9 Empire
S
Starbase 5 First
B
Federation Starbase 21
Starbase 16 Starbase 24 Starbase 13
Starbase 8
Starbase 15
2700 C 00
Tholian
Space Galactic Center
Melkotian Space

VOLUME II
Figure 2a75.3
LOCATION OF STAR FLEET GARRISONS
250 ly
200 ly
150 ly
100 ly
50 ly
Romulan Star Empire
Falcon (SGN-11)
0 0
180 Marfak (SGN-10) 90
Klingon Empire
Canaris III (SGN-4)
UM36 (SGN-7) Hamal (SGN-3)
Ceti (SGN-5)
Teegarden (SGN-2)
Xi Bootis (SGN-6) Marsh (SGN-8) Cestus 3 (SGN-9) Gorn
S
Empire
Earth (SGN-1)
First
Delta (SGN-12)
Federation
B
0
270
C 00
Tholian
Melkotian Space

VOLUME II
Figure 2a75.4
LOCATION OF STAR FLEET STATIONS – TREATY ZONE
25 ly
20 ly
15 ly
10 ly
5 ly
1350
0 0
180 90
Wolf Station (SSN-5)
Rigel II Station (SSN-2)
0
Star Base Central
225 450
Sirius Station (SSN-3) Barnard’s Station (SSN-1)
S
Sigma Station (SSN-4)
2700
t 00
a Galactic Center
r
3150
Federation Treaty Zone Sphere

B
a
s
e
C
e
n
t
r
a
VOLUME II
Figure 2a75.5
LOCATION OF STAR FLEET STATIONS – EXPLORATION ZONE
250 ly
200 ly
150 ly
100 ly
50 ly
Romulan Star Empire

SSN-35 SSN-32
SSN-28
0 0
180 90
SSN-22 SSN-21 Klingon Empire
SSN-36 SSN-14
SSN-23 SSN-31
SSN-15
SSN-13 SSN-42
SSN-30 SSN-7 SSN-16 SSN-40 SSN-39
SSN-26 SSN-38 SSN-11
SSN-9 Gorn
S
SSN-25 Empire
SSN-8
SSN-6
SSN-10 First
SSN-41 SSN-19 SSN-18
SSN-20
SSN-29
SSN-12 Federation
SSN-17 B SSN-24
0
270
SSN-37
C
SSN-27
SSN-34
SSN-33
00
Tholian
Melkotian Space

VOLUME II
Figure 2a75.6
LOCATION OF STAR FLEET OUTPOSTS
250 ly
200 ly
150 ly
100 ly
50 ly
Romulan Star Empire
Outpost 25
Outpost 44 43 Outpost 20 Outpost 26 Outpost 15 Outpost 16
Outpost Outpost 21 Outpost 36 Outpost 17
Outpost 42 Outpost 35 Outpost 27 Outpost 18
Outpost 54 Outpost 52 Outpost 31 Outpost 23 Outpost 33 Outpost 51 Outpost
0 38
180
0
Outpost 30 Outpost 24 Outpost 14 Outpost 50 Outpost
90 40
Outpost 13 Outpost 39
Outpost 29 Outpost 12 Outpost 63 Klingon Empire
Outpost 5 Outpost 46
Outpost 1 Outpost Outpost 59
Outpost 67 45
Outpost 68 Outpost 4 Outpost 2
70 Oph Outpost 3 Outpost 58
Sol Outpost 57 Gorn
61 Cyg Outpost 56 Empire
Cen
Ind
First
S Outpost 55
B
Federation
Outpost 64
C
Outpost 66
Outpost 65 00
2700
Tholian
Melkotian Space

CONFIDENTIAL
RESTRICTED DATA
NOFORN
VOLUME II
8.0 TACTICAL AND STRATEGIC

OPERATIONS
In this chapter the basic tactical and strategic operations of Star Fleet will be discussed.
Strategic Operations are those designed to carry-out the long-range plans of the
Federation that have a global affect. Basically, such operations are political in nature,
which have galactic impact and are not bound by a single area of operation. A simple
example of a Strategic Operation is the deployment and posturing of forces throughout
the Federation, the purpose of which is to distribute the forces in areas where conflict
will most likely occur.
Tactical Operations are those designed to carry-out the short-term plans of Star Fleet,
the Military Staff Committee and the Federation Council, which will generally be of
limited duration and that will only have a local effect. That is, Tactical Operations are
performed for a single purpose at a specific location or area and for a limited period of
time. Such operations are usually military in nature and will generally be initiated by Star
Fleet. An example of such an operation would be the survey of a specific planet near a
hostile area of space for the purpose of determining its benefit as a base of operations.
Such a survey mission would be implemented in order to achieve some future tactical
advantage over a hostile force should it become necessary. In general, all major Tactical
Operations and the missions assigned to operating units are developed by Star Fleet
Command; specifically, by the Star Fleet Tactical Command (TACOM).

VOLUME II

VOLUME II
8.1 GALACTIC DEFENSE CONDITIONS

Galactic Defense Conditions are the states of readiness for the entire Federation.
These conditions or states alert Star Fleet and all the other forces of the member and
non-member systems to place themselves in a specific state of material preparedness for
war, conflict or other emergency. These conditions were established by the Federation
Council and set by the Military Staff Committee. As such, the Federation Council is
the only group that can change the state of global readiness for the Federation.
The Galactic Defense Conditions or DEFCONs established for the Federation are
listed in Table 2a81.1 below. These particular conditions are based upon similar states
established on Earth in the twentieth century. These conditions were recommended by the
Military Staff Committee in 2203 when they were tasked to develop the structure of
the Department of the Star Fleet. These condition states have remained the standard
ever since.
Table 2a81.1
TABLE OF FEDERATION GALACTIC DEFENSE CONDITIONS
Galactic Defense
Description
Condition
This is the condition used to designate normal peacetime military readiness. An
DEFCON 5 upgrade in military preparedness is typically made by the Federation Council and
announced or set by the Federation Joint Chiefs of Staff.
This refers to normal, increased intelligence and the heightening of Federation
DEFCON 4
security measures.
This refers to an increase to force readiness above normal. All communications
DEFCON 3 protocols used by Star Fleet and Local Forces change to currently-classified call
signs.
This refers to a further increase in force readiness just below maximum
DEFCON 2 readiness. To prepare for a possible invasion and to station forces at strategic
locations.
This refers to maximum readiness. It is reserved for general invasion and
DEFCON 1 imminent or ongoing attack on Star Fleet or Federation forces or Federation
territory by a foreign or alien military power.
DEFCONS were originally called "Galactic Code Factors", but were later changed to the
current designation in order to prevent confusion with other warning and communications
codes[1].

VOLUME II
READINESS CONDITIONS
Readiness Conditions or REDCONs refer to the conditions of readiness of Star Fleet

forces. They indicate the state of preparedness that Star Fleet forces are required to
initiate in response to certain alerts or when engaging in combat operations. However,
unlike Galactic Defense Conditions (DEFCONs), Readiness Conditions are not
global, but are generally localized to a specific unit or force. Such readiness conditions will
also depend upon the global state of readiness for the entire Federation (DEFCON).
Table 2a81.2
TABLE OF STAR FLEET READINESS CONDITIONS
Readiness
Description
Condition
Maximum Alert: All personnel, ships and equipment are on alert. All weapons
REDCON 1 manned and engines started. Forces are in position or are proceeding to their
appointed position.
Full Alert: Forces are alerted, all ships are up and running, but will remain on
REDCON 2
standby at their current locations.
Reduced Alert: This refers to an increase to force readiness above normal. All
REDCON 3 communications protocols used by Star Fleet and Local Forces change to
currently-classified call signs.
Minimum Alert: This refers to the lowest level of force readiness. This is the
REDCON 4
normal peace-time condition of Star Fleet forces.
REDCON 1
When received, all commands will go on maximum alert, ready to mobilize and engage in
battle. Weapons are manned, powered up and ready for action. All Star Fleet ships will
proceed to an assigned assembly point.
REDCON 2
When received, all commands will go on full alert and ready to fight. All weapons systems
will be manned and powered up. All communications will be switched to subspace battle
channels. However, unlike REDCON 1, ships will remain on station until further orders are
received, but ready to move within 10 minutes of notification.
REDCON 3
When received, the command is placed in a heightened state of alert, but will continue its
normal routine with 50% of the unit executing work and rest plans. The remaining 50%
will execute security plans. If in port, ships will make all preparations for getting underway
within 30 minutes. All communications will be switched to designated subspace channels.
Weapons systems are not required to be powered-up, but all weapons watch stations will
be manned.
REDCON 4
This is the normal state of readiness for Star Fleet forces during peacetime, which means
that commands must be able to respond and move out within one hour of notification.
However, when received after being on a higher state of readiness, REDCON 4 means
that all weapon systems are to be powered down.

VOLUME II
8.2 ALERT CONDITIONS

Alert Conditions are the codes broadcast throughout the fleet indicating the state of
readiness or preparedness that the fleet must place themselves. When such an alert is
received, all commanders must immediately take all the steps required to place their
command in the appropriate state of readiness for combat or other service as required
under Star Fleet Regulation 3300. This regulation states: “A Commander shall take all
practicable steps to maintain his command in a state of readiness to perform its mission. ”
To alert the entire fleet of an alert condition, a broadcast message will typically be sent out
in the form of a LERTCON or Alert Condition. This message will be broadcast to all units
in the fleet or will be sent to only specific units, depending on the nature of the situation,
and will usually be followed-up by specific instructions from Star Fleet Operations. That
is to say, an alert code will be sent to all units, but the coded message may only require
specific units to respond[2].
As mentioned above, there are some Broadcast messages which are global alert codes
(LERTCON), or standard condition codes, sent throughout the fleet. In addition, any
LERTCON sent by Star Fleet Operations, could also be translated into a Defense
Condition (DEFCON) and vice verse. As such, a DEFCON issued by the Federation
Council through the Military Staff Committee will cause a LERTCON to be sent as
well. The following table lists the LERTCONs that may be sent as Broadcast messages
throughout the fleet.
Table 2a82.1
STANDARD COMMAND ALERT CODES
Alert
Code Designation Description
Code
The Federation is in a state of galactic war or that an invasion is
1 Galactic Alert
imminent.
2 Galactic Disaster Major natural or physical disaster; possible evacuation.
3 Sector Trouble Possible interplanetary war.
4 Local Disaster Local system or region natural or physical disaster.
5 Standby Alert Make preparations for action; remain at current location.
In general, LERTCONs are also associated with specific REDCONs. That is, when a given
LERTCON is issued a corresponding REDCON will also be issued.

VOLUME II
FEDERATION-WIDE ALERTS
Federation-wide alerts are specific codes sent throughout the fleet indicating trouble of
a global nature. Due to the nature of these alerts Federation-wide alerts can only be
issued by Star Fleet Command. The two codes issued for Federation-wide alerts are
Codes 1 and 2, both of which will be explained below.
A Code 1 is a Federation-wide alert that is broadcast to all command units everywhere

throughout the Federation indicating a possible invasion, galactic war or some major
disaster that could affect the entire Federation. A Code 1 alert will usually result in
placing the Federation in DEFCON 1, which will require that all commands and units go
to REDCON 1 and be ready for immediate action.
The last time a Code 1 alert was issued was in 2267 (Federation Stardate 21420.22)
when negotiations broke down between the Federation and the Klingon Empire and war
was declared. The fleet was dispatched to a position near the border with the Klingon
Empire, but was still several days away. The Starship U.S.S. Enterprise was ordered to
proceed to the planet Organia to negotiate the establishment of a base of operations
there. However, circumstances there resulted in the Organian Peace Treaty, which is
still observed today.
Another incident in 2267 (Federation Stardate 21427.12) resulted in another Code 1

alert issued as a result of an unexplained time-warp distortion that propagated throughout
the galaxy. It was thought that the distortion was a prelude to invasion, but later turned
out to be something totally different. The alert may have been prematurely issued since
the Federation had just a week past been in a state of war and was still recovering from
that incident.
A Code 2 is a Federation-wide alert indicating a global disaster. A Code 2 will be issued

when the danger to the entire Federation is real and imminent, or that has already taken
place. Usually, such disasters are caused by known natural phenomenon such as novas or
the effects from exploding stars, the sudden disruption of the space-time continuum or a
sudden and unknown break-out of a highly communicable disease. Typically, when a Code
2 alert is issued all commands will be placed on REDCON 2 or REDCON 3, requiring a
heightened condition of readiness, but will usually have little or no impact on the Defense
Condition (DEFCON) of the Federation as a whole.
An example of a Code 2 alert occurred in 2268 (Federation Stardate 21717.88) when

it was discovered that an enormous 17,700 km single-celled organism destroyed system
Gamma 7A. The projected trajectory of the organism indicated that it would strike at the
heart of the Federation. As such, a global Code 2 was issued to all units and the fleet
was placed in a REDCON 3 state of readiness. However, units closest to the organism
were instructed to proceed to the location of the organism and engage it to the best of
their ability.

VOLUME II
DISTRICT ALERTS
District alerts are particular codes sent only to fleet units located in specific regions or
sectors indicating a problem that is of a local nature. Unlike Federation-wide alerts
District alerts can be issued by commands within the region and not necessarily by Star
Fleet Command exclusively. However, when issued by a local command, Star Fleet
Command must also be notified in order to determine the impact to the general security
of the Federation as a result of the alert. The two codes issued for District alerts are
Codes 3 and 4, both of which will be explained below.
A Code 3 is a district or localized alert indicating a possible invasion within a small region
of space, a regional conflict or impending interplanetary war between local systems. This
alert is primarily issued for conflicts that take place within Federation territory and not
necessarily due to an invasion from the outside. In cases where a Code 3 alert is issued
because two or more systems are engaging in war, Star Fleet will isolate the area, and
place marker buoys around the affected area that will send a Code 710 warning.
A Code 3 was sent in 2266 (Federation Stardate 21323.62) when a Starship on

patrol near the Romulan Neutral Zone received reports from Outpost Four that they
were under attack and upon arrival, found the station destroyed. The attacking vessel was
determined to be a Romulan Bird of Prey. After several skirmishes with the vessel, the
Commanding Officer of the Starship decided, upon his own authority, to issue a Code
3 and pursue the vessel into the Neutral Zone in order to destroy the attacking vessel.
Star Fleet Command was immediately notified of the situation and of the Commanding
Officer’s decision. However, the nearest command base was over three hours away by
subspace communications and therefore, the Commanding Officer had to make the
decision to enter the zone immediately. But before the Starship could receive the reply
back from Star Fleet Command the Romulan vessel was destroyed inside Federation
space and the Starship never entered the Neutral Zone. As such, A Code 1 was never
issued since the Romulan ship was destroyed before it could report back to its home base.
No Romulan ship has entered Federation space since then.
A Code 4 indicates an impending or actual local disaster. This would most likely be issued
in the case where an inhabited planet within Federation space may be subjected to an
unusually intense asteroid bombardment, a collision with a rogue body travelling through
space, some local spatial effect or other natural or unnatural occurrence. In such cases
only the commands in the region would receive the LERTCON and would be placed in a
REDCON 3 or other appropriate level or condition of readiness.
A Code 4 alert was issued in 2268 (Federation Stardate 22007.67) for Sector 94
when it was discovered that a hitherto unknown and unusually large asteroid was headed
for a Federation system. Analysis of the trajectory indicated that the asteroid would strike
the Federation member world of Daran V within 360 days. As such, a nearby Starship
was dispatched to the location of the asteroid to determine a course of action: either to
divert it or destroy it if possible. Upon examination of the asteroid it was determined to be
a hollow space vessel known to its inhabitants as Yonada. The propulsion system of the
vessel was realigned and the disaster was diverted.

VOLUME II
STANDBY ALERTS
A Standby Alert, or Code 5 Alert, is one that warns or prepares the fleet for impending
action. Star Fleet ships receiving this alert will not immediately act, but will remain on
station until further instructions are received. As such, a Code 5 will typically mean that
the command unit receiving the LERTCON should be placed in a REDCON 3 condition.
However, unlike the other LERTCONs, a Code 5 may be either a local or a global alert.

VOLUME II
8.3 FLEET POSITIONING

Fleet Positioning, within the context of Star Fleet operations, relates to the planned
placement of Star Fleet forces as a result of a specific Alert Condition or the placement
of sufficient forces at a location to dissuade a potential threat. This includes stationary as
well as mobile forces. Within this context the term “fleet” will be defined as both the
Operating Forces and the Shore Establishments. As such, the function of this section
will be to describe the placement of bases and stations as well as that of ships and troops.
The mobile forces are primarily the eight fleets and five Battle Groups comprising the
bulk of the Operating Forces. In the more active sectors of Federation space these
mobile forces will be positioned primarily for defense. Patrol Zones will be established
around these areas and Starships will be assigned to watch and guard them, in addition
to their regular duties of law enforcement and space exploration. An example of the
positioning of such mobile forces within Federation space can be seen in Figure 2a83.1.
Fleet Positioning also takes into account the exploration aspect as well. For example, in
Octants 3 and 7 there is little hostile activity. The fleet, in these octants, will primarily be
involved in space exploration and colonization. As such, Fleet Squadrons will be assigned
to the outer rim of Federation space for this purpose, and since it will be Starships that
will primarily be engaged in exploration activities within these areas they will serve as the
Federation’s first line of defense should they encounter new or unknown hostile forces.
Mobile forces also include Star Fleet Marine Corps troops as well. However, instead of
patrolling unfriendly areas Marine Corps troops will be stationed on bases near problem
areas as a “show of force” to any potential aggressor. Typically, Star Fleet Garrisons will
be established in such areas from which troops may be deployed, and Assault ships will
also be assigned ready to pick up the troops and carry them to the trouble spot. However,
in the case where no such Garrison exists within a problem area, Star Fleet will establish
temporary facilities designed to house and support the troops, or it may simply keep them
onboard an Assault ship to perform patrol duties.
With regard to stationary forces, the location of bases, as described in Section 7.4 of this
volume, also constitutes the foundation for fleet positioning. The strategic placement of
bases and stations is, in itself, a form of fleet positioning. Where there are bases and
stations there will be Starships nearby. Bases and stations are an important link in the
overall command and control infrastructure of Star Fleet. They serve as extensions to the
central command structure by acting as relay points from which fleet operational directives
can be transmitted to the commands operating at the fringes of Federation space, and as
replenishment points for the operating forces they serve. Therefore, the location of bases
and stations is important to Star Fleet. As such, Starbases and Star Fleet Stations will
be placed near hostile areas and trouble spots so that the mobile forces will have ready
access to support facilities, equipment, supplies, troops as well as Star Fleet Command.
Fleet Positioning is performed based upon the plans established by the Star Fleet
Office of Strategic Planning. Such plans are given to Star Fleet Operations so that
they can develop the missions and directives to the Fleet Commanders. For a more
detailed description of this process, see Sections 5.3 and 5.4.

VOLUME II
POSITIONING AROUND NEUTRAL ZONES
Since Neutral Zones are political boundaries separating the Federation from hostile
governments and forces, Star Fleet Operations will position forces near and around
such zones. Federation sectors bordering Neutral Zones will be divided into Patrol
Zones where Starships will perform their standard patrol duties. These forces will be
placed in such a manner as to allow the quick assembly and deployment of forces to the
area where an invasion or other hostile action may take place. Such assemblies are called
Emergency Deterrent Forces, a description of which can be found in Section 6.4. This
force is designed to engage an invading force in a delaying action until a larger force can
be assembled and deployed to the area.
Fleet Positioning around Neutral Zones also include the positioning of Outposts and
other stations for the purpose of monitoring such zones for compliance with the treaties
and agreements that created them, as well as to monitor them for any space traffic in or
out of these zones. The responsibility for the placement of such outposts rests solely with
Star Base Command specifically, the Requirements and Specifications Section of
the Office of Star Fleet Base Requirements.
In addition, Star Fleet forces will also be positioned around other Buffer Zones as well.
The primary reason is to monitor the zone to ensure compliance with any regulations
regarding the creation and maintenance of the zone. As such, a Starship will periodically
travel to and patrol around such zones. Figure 2a83.2 illustrates the location of the Buffer
Zones to which a Starship may be assigned to monitor.
GENERAL ORDER TWENTY
General Order 20 is the directive issued by the Director: Star Fleet Command to all
Operational Commanders of Star Fleet forces instructing them to organize and deploy
their forces where they can best protect and defend the United Federation of Planets
as specified in ARTICLE 69 of the Star Fleet Charter. This order also directs Star Fleet
Commanders to deploy their forces at strategic locations throughout the Federation, as
well as at the boundaries of Federation space.

VOLUME II
Figure 2a83.1
GENERAL POSITIONING OF STAR FLEET MOBILE FORCES
180o
Legend
o o
195 165
Fleet Squadron
o o
210 150
Battle Group
o
o 135
Flotilla 225
Romulan
Support Group Star Empire
o
240
Assault Group
o o
255 105
Romulus
10
270o 90o
9
Qo’noS
Kazh (HD209149)
o
o 75
285
o
o 60
300 Klingon
Gorn Empire
Empire
HD90874 S’sgarnon o
Melkot
o Ghdar (4 Aquarii) 45
315
Tholia
Melkotian
o 30
o
Assembly 330 o
o 15
345
0o 0 50 100 150 200

Center of Galaxy
Light-years

VOLUME II
Figure 2a83.2
FLEET POSITIONING AROUND BUFFER AND NEUTRAL ZONES
180o
Legend
o o
195 165
Star Fleet Regulated
o o
210 150
Social Buffer Zone
o
o 135
Commercial Buffer Zone 225
Federation Exploration Zone Romulan
Standard Neutral Zone Star Empire
o o
240 120
Starship
Omega IV
Talos IV o
o 105
255
Platonius Neural Romulan Neutral Zone
270o Tantalus V
90o
Elba II
o
o 75
285 Klingon Neutral Zone

o
300 Klingon
Tholian Neutral Zone
Gorn Empire
Empire
o
o 45
315 Gamma Trianguli VI
Tholian
Assembly 30
o
Realm 330
o
o
o 15
345
0o 0 50 100 150 200

Center of Galaxy
Light-years

VOLUME II
8.4 BATTLE STRATEGIES

Star Fleet operations also include the methods for engaging hostile forces, whether singly
or en masse as during an invasion or war. As such, battle strategies are developed to cope
with hostile forces should they invade Federation space or attack Federation interests.
These battle strategies were developed based upon previous experiences with known
hostile forces. Star Fleet first developed various battle plans and then tested these plans
through rigorous simulation in order to ensure maximum effectiveness against such hostile
forces. The responsibility for developing such strategic and tactical operations falls to the
Star Fleet Office of Strategic and Tactical Operations (TAC), whose function it is to
develop the combat strategies and tactics that are employed by Star Fleet ships, bases,
stations and troops.
During the development of strategies and tactics, TAC will work closely with Star Fleet
Intelligence who will supply this office with any intelligence data regarding the strategies
and tactics employed by foreign powers, or with any other operational material obtained
through clandestine means.
The function of this section is to present some of the large-scale or fleet battle strategies,
and not those of individual ships. The tactics that will be employed by individual Starship
Commanders will be discussed in Chapter 4, Part 2 of Volume IV of the Star Fleet
Command Manual.
THEATER OF WAR AND THEATER OF OPERATION
The term “Theater of War”, as it applies to the Federation denotes that area of space
over which war prevails and in which its boundaries are protected. This protection may
consist of bases, stations, ships, or important natural obstacles and the stellar bodies that
are present within the volume, or even the considerable distances separating the rest of
space embraced in war. Such areas of space are not merely a piece of the whole, but a
small whole complete in itself; and consequently it is more or less in such a condition that
any changes which take place at other points in the seat of war will have only an indirect
influence upon it. To give an adequate idea of this, one may suppose that in one portion of
space an advance is made, whilst in another quarter a retreat is taking place or that upon
the one a force is acting defensively, whilst an offensive is being carried out within the
other. Such a clearly defined idea as this is not capable of general application; it is merely
used to indicate the area of isolation encompassing the space known as the Battlespace.
This same concept also applies to a “Theater of Operation”. However, unlike a Theater
of War, where engagements are made within a specific sphere of operation, the Theater
of Operation for Star Fleet is the entire volume of space encompassing the United
Federation of Planets. A Theater of Operations is essentially an administrative term
for a theater which has both an operational and an administrative command.
An example of a Theater of War can be illustrated in Figure 2a84.1. In this case a

theoretical war with the Romulan Star Empire is presented, along with one of the most
likely battle spaces. In this particular instance a Star Fleet force will plan to drive the
opposing Romulan force back to their home world and to attack the home world in an
effort to bring the theoretical war to an expedient close.

VOLUME II
CONTROL OF THE BATTLESPACE
The primary objective of any battle strategy is to control the Battlespace. A Battlespace
is the volume of space (or planetary surface area) in which combat operations are to take
place, and includes all the environmental factors such as space conditions, the status of
friendly and hostile forces, neutrals and noncombatant vessels. For ground operations the
Battlespace includes weather, terrain, the electromagnetic spectrum, facilities and other
conditions that must be understood to successfully apply combat power, protect a force, or
complete a mission.
In order to control a battlespace, a commander must recognize all of the above conditions
prior to any operation within this space. This is known as Battlespace Awareness or the
knowledge and understanding of the operational area's environment, conditions, and other
factors, including the status of friendly and adversary forces, neutrals and noncombatants,
weather and terrain (for ground operations), that enables timely, relevant, comprehensive
and accurate assessments in order to successfully apply combat power, protect the force
and/or complete the mission.
Battlespace or Combat Intelligence will also be required. Combat Intelligence is the

analytical methodologies used to reduce uncertainties concerning the enemy, environment
(or terrain) for all types of operations. Such analytical information will be entered into
tactical simulations in order to establish the initial strategy for combat in order to “design
the battlespace.” That is, to station or maneuver forces to selected locations and around
areas for the most effective use of resources to ensure tactical advantage and superiority.
Although this may appear that commanders may rely too heavily on computer simulations,
commanders will only use this information along with their experience and intuition when
implementing their battle plan.
During wartime conditions there may be more than one battlespace in which enemy forces
are being engaged. Each such battlespace will be under the command of a Commander
in Chief, such as a Fleet, Task Force or Group Commander. The totality of all these
battlespaces together is called the Theater of War.

VOLUME II
OPERATIONAL REQUIREMENTS
In each case, whether it is tactical or strategic, a Commander or Commander in Chief

will be in charge of the operation. When planning any such operation there are several
requirements a commander must consider for his mission to be successful. In the case of
battle, the following are the requirements for winning:
 Objective
 Tactics
 Technology
 Flexibility
 Ruthlessness
Each of these requirements will be discussed below and will be examined when planning
military operations. Operations are typically initiated through Rules of Engagement, or
the criteria or threshold conditions that must be met before an action or a specific set of
actions can commence.
OBJECTIVE
Objective is the essential purpose of the operation. Commanders planning and executing
operations must have a clear vision of what they intend to do in order to prevail in any
operational situation and why they are performing the operation in the chosen manner. As
such, commanders are recommended to prepare clear, uncomplicated plans and clear,
concise orders to ensure thorough understanding by those carrying-out the operation.
TACTICS
Tactics are the methods used to accomplish the objective. Tactics will also have certain
requirements in order to be successful. When developing tactics for an operation certain
fundamental considerations or rules should be applied. These are:
1. The operation should be executed with speed and surprise. Surprise is fundamental to
the success of any military mission. The rule is to strike an enemy at a time and at a
place, or in a manner for which the enemy is unprepared, and as rapidly as possible.
2. Once the operation begins, it should proceed with sufficient momentum in order to
continue. Momentum is the essential to ending a military operation quickly.
3. The operation must have plans for the resupply of the force. Logistics and support are
major keys to the success of any operation.
4. There should be a plan in place for operational security. Operational Security is the
plan and methods used to safeguard the operation, and the command and control
infrastructure.
5. Every operational plan should have a good exit strategy. Battle planners should not
only consider how to enter and sustain a battlespace, but also how to exit one as well.
An exit strategy is merely the plan to leave the battlespace upon the completion of
specific goals and objectives. Criteria for exiting are developed that map to the goals
and objectives that must be achieved in order that the operation is considered a
success.

VOLUME II
TECHNOLOGY
Technology is the equipment, weapons and assets that will be employed to accomplish the
objective. The level of technology employed by any commander will have a great impact
on the outcome of any operation. The fundamental rule is that the superior the technology
the greater the likelihood of success. Therefore, the commander that can employ superior
technology will often times prevail in any combat situation. However, this principle does
not always guarantee success, especially against some primitive technology employed by
indigenous peoples against an occupying force.
An example of the differences in technology can be illustrated by examining the Romulan

incursion incident of 2266. Although the Romulan ship had the superior weapon and an
effective cloaking device, their simple impulse propulsion system made them vulnerable.
The Starship was able to effectively outrun the strength of the Romulan plasma weapon
and quickly maneuver the vessel to greatest advantage.
FLEXIBILITY
Flexibility is the ability to change or revise the plan. During operations things will change.
As such, commanders must often modify their strategies and tactics during battle in order
to adapt to changing conditions within the battlespace. Commanders are trained to always
make secondary or contingency plans in case the primary plan requires modification.
RUTHLESSNESS
Ruthlessness is another factor that may be required in order to win. However, it does not
necessarily mean the ruthlessness of the commander, but that of the plan. That is, to win
a conflict it is sometimes necessary to attack targets where a large segment of an enemy’s
population may reside. The plan may involve the wholesale destruction of the enemy’s vital
interests, which could involve large numbers of people – combatants or civilians, either to
reduce the enemy’s capacity to wage war or to inflict such damage as to strike at the
morale of the population in order to quickly end the conflict. As such, the commander, in
making such plans, must weigh the cost of lives to achieve the objective over the cost, in
lives, that may be saved in the future. Therefore, there will always be an element of
ruthlessness involved in executing any military operation.

VOLUME II
GENERAL FEDERATION INVASION
A general invasion is a full-scale incursion of the Federation by hostile forces. Should

there be such an incursion or an indication that an invasion may be imminent, Star Fleet
has developed a special procedure to handle such cases. This procedure is somewhat
generalized, giving commanders wide latitude when dealing with such situations. However,
the specific steps of this procedure are as follows:[3]
1. Verify the situation. Typically, the most likely way in which an invasion may be
detected is via the many outposts that line the border areas between the Federation
and the hostile territories. Verification of an invasion will normally be performed using
the many sensor arrays that dot Federation space as well as any reports from the
outposts.
2. Alert the fleet. Star Fleet Command and any nearby Federation force must be
immediately informed of any incursion. For cases of general invasion, Star Fleet
Command will issue a Code 1 alert, which may place the entire Federation in
DEFCON 1.
3. Assemble a repelling force. To immediately address the situation an Emergency
Deterrent Force (EDF) will be formed by assembling nearby Star Fleet units. The
primary function of the EDF is to keep the enemy occupied and to stop any advance.
By delaying the advance of the invading force, a larger attack force will have time to
assemble and race to the affected area.
4. Repel the invasion. The objective is primarily to turn-back the intruder and not to
destroy them unless it becomes necessary. When repelling the invading force or
pursuing such force, Commanders are instructed not to enter the enemy’s space.
The Star Fleet force may pursue the force only to the boundaries of Federation
space. Only during a declared general war may Federation forces enter the territorial
space of the enemy government, and then only if authorized by the Federation
Council President as part of the conditions for successfully concluding the war.

VOLUME II
ENGAGING HOSTILE FORCES
Generally, the engagement of hostile forces will be performed through the execution of a
battle plan, except where there is a surprise attack by a hostile force. In which case the
local Star Fleet commander will engage the enemy using the information he has at hand.
The term engage not only means attacking the enemy or defending a position, but also to
communicate to Star Fleet Command and possibly withdraw if the likelihood of success
is low and the loss of the command appears likely. In general, the engagement of hostile
forces will be ordered by the commander in charge of the Star Fleet force.
When hostile forces must be engaged Star Fleet Commanding Officers must follow the
guidelines set forth in Star Fleet Regulation 4710. These guidelines, which also formed
the basis for General Order 23, specifically state:
a. Before going into battle or action the Commanding Officer will communicate to his
officers and crew, if possible, his plans for battle or action and such other information
as may be of operational value should any of them succeed to command;
b. During action, the Commanding Officer must station the Executive Officer where
he can best aid him, and if practicable, where he could probably escape the effects of
a casualty disabling the Commanding Officer, and yet be able to assume command
promptly and efficiently;
c. During action, the Commanding Officer must engage the enemy to the best of his
ability and must not, without permission, break off action to assist a disabled ship or
take possession of a captured one;
d. Immediately after a battle or action, the Commanding Officer shall repair damage
so far as possible in order to return the ship to a battle-ready condition. Once such
repairs have been completed he will exert every effort to prepare his command for
further service, and must make accurate, explicit, and detailed reports to the central
command as soon as possible;
e. At an appropriate time after a battle or action, and after repairs have reasonably been
completed, the Commanding Officer may assist a disabled ship or take possession
of a captured one.
For large-scale engagement of hostile forces the Star Fleet Office of Strategic and
Tactical Operations has developed generalized Battle Plans designed to handle specific
types of engagements for specific hostile forces in specific areas of the Federation. The
following subsections will provide an insight into several classic strategies that were used
in the past. These are provided here as examples on how forces are engaged. However,
TAC has many Battle Plans (contained within special Strategies and Tactics manuals)
that can be employed depending on the nature of the threat. However, they are highly
CLASSIFIED and will not be presented here. Star Fleet Commanders are constantly
trained on the use of such strategies.

VOLUME II
PHALANX FORMATION
The Phalanx Formation or Phalanx Battle Line is essentially a rectangular group

military formation, usually composed of capital Starships providing intense firepower and
shielding to the smaller forces, while the smaller forces directly engage the enemy force in
front and along the flanks. The word phalanx is derived from the Greek word phalangos,
meaning the finger and was the hallmark of ancient Greek warfare on Earth.
The Phalanx Battle Line, as illustrated in Figure 2a84.2, consists of four lines of
combatants: the first or front line consists of Cruiser or Heavy Cruiser Starships. Their
basic function is to put up a barrier of shields and heavy firepower against the enemy in
order that the second or attack line can maneuver into the enemy line and disperse the
force. This second line is composed primarily of Destroyer class Starships whose main
purpose it is to confuse and disperse the force. The third line is composed primarily of
Battleships to provide cover firepower and to destroy enemy ships as they approach. As
the enemy force is being dispersed, the first and third lines are continuing their heavy fire
on targets while the enemy is engaging the Destroyers.
While this dispersion tactic is taking place, the fourth attack line is maneuvering to the rear
of the enemy force. This fourth line is composed of Light Cruisers and Frigates or
Heavy Destroyers to aid the second line in their attack and to project firepower onto the
enemy’s vulnerable areas. Finally, the first and third line moves in for the kill. At this point
many of the second line Destroyers will move back to their original starting point to refit
or repair, or circle back into the Battlespace to support the larger ships.
The main point of the Phalanx Battle Line is to set up a barrier of which an enemy force
cannot cross. This maneuver is designed to hold and push an enemy back, and is typically
employed near the boundaries adjacent to enemy territory.
This particular strategy, the Phalanx Battle Line, requires extensive planning and
staging before any actual engagement. This strategy will most likely be employed during
an invasion of enemy forces where intelligence of the incursion may indicate where the
enemy force will be headed. At a point in space of maximum advantage Star Fleet
Operations will assemble a force necessary to drive the invader back. The force will
typically be a Task Force assembled using elements of the local fleet and will be headed
by a Commander in Chief with the rank of Rear Admiral.

VOLUME II
CONVERGE – DISPERSE MANEUVER
The Converge-Disperse Maneuver is used against a large formation of ships. It is

basically used for fleet-to-fleet action. The principle is that if a large formation of Star
Fleet ships encounters a large formation of enemy ships, the enemy formation can be
dispersed into smaller units and battlespaces that can be independently managed.
As illustrated in Figure 2a84.3 when encountering a large enemy force, the initial action
will be to bring the Star Fleet force closer together. This will be perceived by the enemy
as a defensive move in order to consolidate firepower. The normal reaction to this
perceived maneuver is to surround the force in order to attack the group from all sides.
However, this is the intent of this particular maneuver.
When the enemy force starts to converge onto the Star Fleet force, the Star Fleet Force
Commander will issue orders to break-up the force into Squadrons, each responsible for
attacking a selected group of enemy vessels. The Squadron forces will then charge into
their designated enemy force areas essentially cutting the force line. The enemy force, in
response, would have to attack or defend their individual positions, thus dispersing the
enemy force into smaller units.
The larger capital Starships within each Squadron will be used to directly attack the lead
or capital ships of the opposing force. These Starships will lay down cover fire for the
smaller attacking ships. Mid-sized combatants such as Frigates and Heavy Destroyers
will attack flanking positions in the enemy line. This drives a “wedge” into the line which
causes the dispersal of the enemy force. While the dispersal is taking place, the small
Destroyer class ships will attempt to infiltrate the enemy line so as to maneuver behind
the enemy ships and attack from the rear.
However, in a fleet-sized force, the Force Commander will usually have another smaller
force stationed in the rear of the main body. This constitutes the fleet’s reserve force used
to support combat action, mop-up the battlespace and provide additional combatants as
needed. The Force Commander will order in this reserve force as the battle progresses.
This particular maneuver is practiced often during Fleet Squadron exercises and the
outcome is generally the same – approximately fifty percent of the enemy ships badly
damaged or destroyed.

VOLUME II
SQUADRON BREAK MANEUVER
For smaller engagements where perhaps only a squadron of ships will be necessary, the
tactic most often used is the Squadron Break Maneuver. This maneuver was developed
to be used primarily against Klingon forces, and based upon the tactics generally employed
by Klingon ships in a group formation. Figure 2a84.4 illustrates this tactic and the various
stages used in carrying it out.
As stated, this maneuver will generally be used against a small Klingon force. A Fleet
Squadron will typically be used to engage the force. A typical Klingon squadron generally
consists of three D-7 class Battlecruisers. A Klingon Battle Group usually has at least two
squadrons or six ships. Therefore, a Fleet Squadron is sufficient to deal with this threat.
The maneuver begins with the Star Fleet squadron in Fleet Squadron formation, with
the lead ship a Cruiser or Heavy Cruiser flanked by two Light Cruisers or Frigates
and a Destroyer Division following in the rear. The primary aim of the Squadron Break
Maneuver is to divide the Klingon group into its constituent squadrons. To accomplish
this, the lead ships will advance towards the Klingon group – shown as steps 1 and 2 in
the diagram. The typical response of the Klingon force is to separate the group into three-
ship squadrons in an attempt to maneuver around the flanks of the oncoming ships. When
they have the chance, Klingons prefer to take a strategic approach rather than to engage
head on. A Klingon ship will usually attack head long only when acting singly. As such, the
Klingon group has been separated into two smaller forces.
In anticipation of the Klingon battle group breaking Port and Starboard, the Star Fleet
Squadron Commander will order the trailing Destroyer Division to come around at
high warp speed in order to intercept the Klingon squadrons. This tactic constitutes steps
3, 4 and 5 of the maneuver. As the Destroyer Division nears the Klingon squadrons, the
Klingons see this as an advantage since they will be engaging lighter combatants against
their battlecruisers. However, the heavier Starships will then break into the two distinct
battlespaces developed by the engaging Destroyers. The timing of this maneuver is such
that the heavier ships should enter the battlespace to the rear of the opposing force -
illustrated as steps 6 and 7, the most vulnerable spot on a Klingon ship.
This particular maneuver is practiced often during Fleet Squadron exercises and the
outcome is generally the same – four out of the six enemy ships badly damaged.
This same maneuver can be employed against a Romulan group as well. However, unlike
the Klingon group, a Romulan Commander will have one to two ships held back in reserve
as a part of a counter-attack plan. But the basic maneuver is the same. The Romulan
attacking force will directly engage the oncoming Starships and the Destroyer Division
will come around to engage the ships that were held back as shown in steps 3 and 4. The
Romulans will also attempt a similar maneuver to bring two or more ships to the rear of
the Star Fleet formation, but they will be met by the Destroyers.

VOLUME II
PLANETARY ASSAULT
A Planetary Assault is the full-scale invasion of a planet by ground troops – primarily by

troops of the Star Fleet Marine Corps. The sole purpose for any planetary or ground
assault is the capture and occupation of planetary or government assets. Assaults are
never used for punitive or other action that simply aims to destroy an enemy force or its
assets. However, planetary assaults may be used during special operations when Local
Forces are ineffective in handling an illegal rebellion or during an insurgency from an
outside power. In such situations the legal government of the system must request such
action to the Federation Council. The Federation Council will evaluate the impact to
the requesting system concerning the issues with the Local Force and the impact that the
use of Star Fleet forces may have on the system. If it can be demonstrated that the lack
of or ineffectuality of a Local Force may affect the peace and security of the Federation
as a whole, the Federation Council may elect to exercise its authority under ARTICLES
39 and 51 of the Articles of Federation and order the invasion of a sovereign system by
Star Fleet.
Planetary assaults typically begin with the bombardment of key military and industrial
installations using phasers and photon torpedoes, the function of which is to weaken the
offensive and defensive capability of the enemy. The general assault will commence after
the bombardment has been completed. Assault (G-class) ships containing special troop
transport vessels will launch from the ship and enter the atmosphere of the planet. These
transport vessels are essentially armed craft with attached containers holding troops and
surface vehicles.
Supporting the assault are Fighter and Attack craft that will be used primarily to protect
the transport vessels while the landing takes place, and will later be used when the troops
disembark from their transports and begin their assault.
Regarding planetary assaults, such ground operations will also have their own Theater of
Operations. A ground Theater of Operation is the term for a Battlespace, or group of
battle spaces, that have both operational and administrative control. The term "Theater
of Operations" was defined in the old Earth field manuals as the land and sea areas to be
invaded or defended, including areas necessary for administrative activities incident to the
military operations (Figure 2a84.5). In accordance with the experiences of past wars, it
was usually conceived of as a large land mass over which continuous operations would
take place and was divided into two chief areas-the combat zone, or the area of active
fighting, and the communications zone, or area required for administration of the theater.
As the armies advanced, both these zones and the areas into which they were divided
would shift forward to new geographic areas of control. The concept of theater warfare
has been used in many wars, and still serves as a linchpin of strategy for most military
organizations, both foreign and Federation.

VOLUME II
Figure 2a84.1
THEATER OF OPERATIONS
180o
Theoretical Battlespace
o o
195 165
o o
210 150
o
o 135
225
Romulan
Federation Exploration Zone o
Star Empire
o
120
240 (Theater of Operations)
o o
255 105
Romulus
Romulan Neutral Zone
270o Theater of War

90o
Qo’noS
Kazh (HD209149)
o o
285 75
Klingon Neutral Zone

o
300
Tholian Neutral Zone Klingon
Gorn Empire
Empire
HD90874 S’sgarnon o
Melkot
o Ghdar (4 Aquarii) 45
315
Tholia
o 30
o
Assembly 330 o
o 15
345
0o
Center of Galaxy

VOLUME II
Figure 2a84.2
STAR FLEET PHALANX BATTLE LINE
Legend
Starship Shields
Starship Movement
Starship Phaser Banks
Starship Main Phaser Batteries

VOLUME II
Figure 2a84.3
CONVERGE – DISPERSE MANEUVER
Legend
Starship Shields
Starship Movement
Starship Phaser Banks
Starship Main Phaser Batteries

VOLUME II
Figure 2a84.4
SQUADRON BREAK MANEUVER
Legend
Starship Movement 5
Enemy Movement
Battlespace 1
6
2
1
7
2
3
Battlespace 2

VOLUME II
Figure 2a84.5
CLASSICAL GROUND THEATER BOUNDARIES USED BY THE STAR FLEET MARINE CORPS
Front Line of Battle
Division Division Division Division Division Division Division Division Division Division Division Division
Force Force Force Force
Force Service Area Force Service Area
Advance Section
Command and Control

VOLUME II

VOLUME II
8.5 SECURITY PATROLS

Security Patrols are generally strategic operations designed to protect Federation
space or to implement a containment policy. However, Security Patrols also refer to law
enforcement tours as well. This form of patrol will usually be assigned to the two standing
flotillas tasked with keeping the peace within the Federation Treaty Zone. Therefore,
and in general, a Security Patrol is the method employed by Star Fleet to maintain the
overall peace and security of the Federation, and will be carried-out throughout the
Federation in regions of space called Patrol Areas. Figure 2a85.1 provides an illustration
on the location of such areas.
PATROL AREAS AND ZONES
A Patrol Area is a large volume of space in which Star Fleet has determined requires
particular monitoring. A Patrol Zone is a subdivision of a Patrol Area and as such, a
Patrol Area may have many Patrol Zones. Patrol Zones may be contiguous linear
areas of equal size or sectors of a volume of space enveloped by a Patrol Area, or merely
arbitrary blocks of space within a Patrol Area, depending on the need to patrol a specific
area of space. As such, the entire Federation Treaty Zone is considered as one large
Patrol Area so that Star Fleet can accomplish its law enforcement function.
The Treaty Zone is essentially divided into nine Patrol Areas covering the nine Sectors
of the Treaty Zone: Sectors 001 to 009. These areas are patrolled by the two standing
Flotillas: FLOT9 and FLOT10. Together, these two flotillas possess 34 line Starships
distributed among the nine sectors of the Treaty Zone, which allows for about four line
Starships to patrol a volume of space of approximately 38 cubic parsecs (4.7x10 42 cubic
kilometers), each within their assigned areas.
Although not specifically designated as such, the entire Federation Exploration Zone
may be considered as one large Patrol Area since it contains many small Patrol Zones,
usually established around Buffer and Neutral Zones. The function of Buffer Zones is
to limit access to and from these areas of space for the purpose of isolation or separation
as stated in Section 3.2 of this volume. These zones are legal boundaries that primarily
restrict access by private or commercial space traffic. As such, Star Fleet will patrol these
zones to enforce compliance with the laws and regulations that formed these zones.
The size of a Patrol Area will depend upon the nature and purpose for monitoring the
area. Most Buffer Zones have small Patrol Zones surrounding them. For example, the
Patrol Area surrounding a Buffer Zone will be about one AU in size as illustrated in
Figure 2a85.3. Such a small size allows Starships to easily and quickly monitor the zone
and to immediately respond to any violation.

VOLUME II
At the outer rim of Federation space may be located Neutral Zones. Neutral Zones
are a special form of military Buffer Zone used to separate Federation space from
hostile territories. As with Buffer Zones, Neutral Zones are legal boundaries usually
established by treaty or agreement. A violation of the provisions of such zones by either
side constitutes a violation of the treaty or agreement to which they were established. As
such, Star Fleet will patrol these zones to enforce compliance with the laws and treaty
stipulations that led to the formation of these zones against violation by Federation
citizens, as well as to monitor these zones for compliance by the opposing party. These
particular zones will usually have the most concentration of Star Fleet ships, not only to
patrol the zone, but also to be able to react and assemble a force sufficient in size to stop
an incursion by the hostile government.
To aid in monitoring these zones, all areas adjacent to Neutral and Buffer Zones will be
divided into Patrol Areas and Zones. Typically, these zones will be approximately seven
light years thick, which allows a Starship on patrol inside these areas to respond and
place themselves at the location of a situation within 48 hours at Warp Factor 6 or within
fourteen hours at Warp Factor 8. An illustration of the space around Patrol Zones can be
seen in Figure 2a85.4. Neutral Zones will typically be dotted with Star Fleet Outposts
as illustrated in Figure 2a85.5. Starships assigned to these areas will periodically visit
these outposts to check on their status and to cart supplies and personnel between these
stations.
Figure 2a85.2 provides an illustration of a standard maneuver within any Patrol Area
adjacent to a Neutral Zone. As part of its patrol duty, a Starship will periodically travel
to and stop at an Outpost for several days for an official visit and possibly for some Rest
and Recuperation (R&R) time for the crew. Then the ship will go back on station for
several weeks before returning to the same Outpost or to another Outpost. Starship
Commanders are trained to vary their patrol movements so as not to create or set a
predictable pattern. This is especially true around Neutral Zones where hostile forces are
constantly monitoring and observing Star Fleet forces for signs of weakness or to gain an
advantage.
Starships on patrol within these areas will perform various functions, the primary being
Federation security. Although a Starship will primarily carry out the security function, it
will also execute all the basic patrol functions required under Star Fleet General Orders.
That is, a Starship on patrol will also perform galactic surveys, colony support, scientific
investigations and any other such assignment as Star Fleet Command deems necessary.
However, Starships on patrol around hostile areas will predominantly carry out security
monitoring duties and will frequently execute combat training exercises to sharpen their
skills in defending Federation space.
Starships on five-year missions will usually be assigned large regions of space to patrol
and explore. Such regions of space may also be divided into standard Patrol Areas and
Zones. Starships operating within the region will periodically patrol within these zones,
though it may not be their primary mission.

VOLUME II
Figure 2a85.1
STAR FLEET PATROL AREAS
180o
Legend
o o
195 165
Standard Patrol Zone o
o 150
210
Standard Patrol Area
o
o 135
225
Federation Exploration Zone Romulan
o
Star Empire
o
240 120
Omega IV
o o
255 105

Neural
Treaty Patrol Area 1
270o Zone
Patrol 90o
Elba II
Area
Patrol Area 3
o
o 75
285

o
o Patrol Area 2 60
300 Klingon
Patrol Area 5
Gorn Empire
Empire
o
o 45
315 Gamma Trianguli VI
Tholian
Melkotian
Assembly Patrol Area 4
30
o
Realm 330
o
o
o 15
345
0o 0 50 100 150 200

Center of Galaxy
Light-years

VOLUME II
Figure 2a85.2
GENERAL NEUTRAL ZONE PATROL
Star Fleet
Outpost
Patrol Zone 2
Hostile
Territory
Patrol Zone 1

VOLUME II
Figure 2a85.3
STANDARD SIZE OF A PATROL AREA AROUND A BUFFER ZONE
Isolation Area Patrol Area Boundary
1,125,000 km 1,500,000 km
Buffer Zone Boundary

VOLUME II
Figure 2a85.4
STANDARD SIZE OF A PATROL AREA AROUND A NEUTRAL ZONE
PATROL ZONE 1
NEUTRAL ZONE
6.67 ly
PATROL ZONE 2
PATROL ZONE 3
PATROL ZONE 4

VOLUME II
Figure 2a85.5
PATROL AREA AROUND ROMULAN NEUTRAL ZONE

VOLUME II

SECRET
RESTRICTED DATA
NOFORN
VOLUME II
9.0 SPECIAL OPERATIONS

Special Operations are those missions and services that are outside the normal scope of
the activities and functions performed by Star Fleet forces and that usually originate from
within the Federation Council. Special Operations, however, are not always military in
nature; some are diplomatic as well. Such Special Operations are summarized in the
following table and described in more detail in the subsequent sections:
Table 2a90.1
TABLE OF SPECIAL OPERATIONS AND SERVICES
Special Service or Activity General Description
As required under Article 42 of the Articles of
Suppressing Rebellion
Federation.
As required under Articles 39 and 42 of the Articles of
Counter-revolution
Federation.
As required under Articles 39 and 42 of the Articles of
Counter-insurgency
Federation.
Peace Envoys Article 29 of the Star Fleet Charter.
As allowed under Articles 36 and 42 of the Articles of
Military Aid
Federation.
As may be required under Chapter XVII of the Articles
Transitory Security Arrangements
of Federation.
As such, the purpose of this chapter is to present some of the special operations and
intelligence functions that may be performed by Star Fleet.
SPECIAL SERVICES
Special Services are defined as those activities or functions not defined within the Star
Fleet Charter, but that may be applicable under certain provisions within the Articles of
Federation, or that the Federation Council may deem necessary. Although the basic
functions and authorities of Star Fleet are well defined within the Charter, Star Fleet still
comes under direct authority of the Federation Council, in accordance with Paragraph 2
of ARTICLE 52 of the Articles of Federation and therefore, if the Council requires some
operation to be performed by Star Fleet that may be outside of its chartered scope, it
must accommodate the request.
One such service is to support, and possibly defend, legally-recognized governments from
insurrection or to take over the military or law-enforcement function from the forces of
such governments. Although the right of sovereignty is guaranteed in the Articles of
Federation, they also allow for the Federation Council to take whatever action is
necessary in order to maintain peace and stability within the Federation, as permitted
under ARTICLE 42 and which will be exercised by Star Fleet under ARTICLE 48.
STARDATE 7305.29 UFP521-2a90.1 SECRET

VOLUME II
One example concerns the possibility that a Local Force may not have the competence or
capability to maintain peace and security within the jurisdiction they serve. When such a
Local Force becomes ineffective in its duty to maintain peace and security within its own
boundaries, the entire Federation may be affected. In such cases Star Fleet may be
called upon to augment or replace the Local Force when it can no longer perform its
duty. Such a request would typically be made by the local system government, and must
be made directly to the Federation Council in order that it would inject itself into the
functioning of that government.
The decision to use Star Fleet forces to support, augment or replace a Local Force rests
entirely with the Federation Council. The Federation Council will evaluate the impact
to the requesting system concerning the issues with the Local Force and the impact that
the use of Star Fleet may have on the system. If it can be demonstrated that the lack of
or ineffectiveness of a Local Force will affect the peace and security of the Federation
as a whole, then the Federation Council may elect to exercise its authority under
ARTICLES 39 and 51 of the Articles of Federation and take control of the security of
that government.
If the decision is made that Federation forces will be used to augment or replace a Local
Force, Star Fleet will be directed to assemble such a force as required under ARTICLE 48
of the Articles of Federation. Typically, this will involve a squadron of combatants and
support vessels, along with a contingent of troops or security personnel. The primary
mission of this Task Force will be to maintain peace and security within the system, to
enforce local system laws and to support the legally-recognized government of the system.
In this instance, ARTICLE 34 of the Charter will be temporarily suspended. Although in
command of the law enforcement agency for the local government, Star Fleet cannot
interfere in the functioning of the local system government as required under the ARTICLE
33 of the Star Fleet Charter.
In the situation where an illegal rebellion may be occurring against a lawful government of
the Federation, the Federation Council may dispatch an armed force to suppress such
insurgents or insurrection under ARTICLES 39 and 41 of the Articles of Federation when
the Local Force becomes ineffective in dealing with the revolt. In such instances the
Federation Council may direct Star Fleet to suppress the revolt in accordance with
ARTICLES 48 and 51 of the Articles of Federation.
Should Star Fleet be called upon to suppress a revolt, a Task Force will be assembled,
which will include ground troops. In addition, the Task Force Commander will be given
the authority to declare martial law throughout the entire system. This would mean that all
the citizens of the local system will come under the direct authority of Star Fleet. The
Task Force will remain in charge until the revolt is completely suppressed and the legal
government restored, or is in full control of its system.
It should be noted that Star Fleet may not necessarily become directly involved in such
revolts as described above, depending on whether the system is a member of the United
Federation of Planets or simply resides within the boundaries of Federation space.
Instead, Star Fleet may send military and diplomatic advisors to aid the legally recognized
government in retaining control of its system. In addition, in the case where an illegal
government was placed into power or that outside forces had established a government of
their own without the consent of the indigenous population, Star Fleet may send military
aid in the form of arms, equipment and advisors to rebel groups in order that they may
take back their government.

VOLUME II
FEDERATION DIPLOMATIC MISSIONS
Star Fleet has been authorized under ARTICLES 7 and 29 of the Star Fleet Charter to
assume certain diplomatic functions for the Federation. As such, Star Fleet personnel
may become involved in Federation diplomatic missions. Generally, such missions will
usually involve Star Fleet Representatives, but may also involve others as well, and
may require the use of Star Fleet assets such as ships and bases. For example, Star
Fleet ships may be used to transport a diplomatic mission, to ferry foreign ambassadors
and dignitaries to and from Federation facilities, or to escort foreign diplomatic craft to
Federation facilities for the purpose of peace negotiations or other consular purposes. In
addition, Star Fleet ships and other assets may be used in Federation government and
non-Federation ceremonial activities as directed by the Federation Council[1].
One example of the use of a Star Fleet asset for such diplomatic missions, a Starship
was selected to transport a large Federation delegation to an undisclosed planet with the
code name of “Babel.” The Starship had to transport not only the ambassadors and
delegates, but their families as well.
TRANSITORY SECURITY ARRANGEMENTS
Star Fleet has a duty and a responsibility to protect all citizens and persons within the
United Federation of Planets as specified in ARTICLE 26 of the Star Fleet Charter. As
such, Star Fleet may be required to implement special security procedures to protect
important persons and dignitaries. Such procedures are called Transitory Security
Arrangements, which are special protective services or measures guaranteed by the
Federation Council to dignitaries as they transit throughout Federation space. High-
ranking government officials of local system governments will typically use the security
services of their own Local Force to protect them. However, when outside the boundaries
of their respective system, Star Fleet will supplement the security team with Star Fleet
Security personnel. This is primarily due to the fact that a Local Force does not have
any jurisdiction outside their system.
Such arrangements are also provided to foreign officials as well. Transitory Security
Arrangements are automatically initiated when a foreign official or dignitary enters
Federation territory. High-ranking officials from foreign governments may have their own
security service to protect them, but must have Star Fleet security forces supplement the
force while in Federation territory. This has the dual security purpose of protecting the
official from harm while in Federation space, and to monitor the activities of foreign
officials and personnel while a guest of the Federation.
Some systems may not have their own Local Force or security personnel. In such cases
personal bodyguards will be supplied to them by Star Fleet Security should the official
venture beyond their system. In addition, the local government may also make a request
to the Federation Council for permanent security or law enforcement personnel. In this
case the Federation Council would direct Star Fleet to supply a special security force to
the system that would come under direct authority of that government and as such, would
become the official Local Force of the system. However, any force that is assigned to
such a system would not be detached from Star Fleet and therefore, will still be subject
to Star Fleet Regulations and the orders of the Federation Council.

VOLUME II
SECRET OPERATIONS
Special Operations also include those that are secret or covert in nature as well. Secret
Operations are those missions and functions that are performed or executed under the
cloak of secrecy, specifically for the Federation Council. Such operations will usually be
carried out in order to obtain some specific intelligence information for the Federation. In
some cases, such operations may even be performed without the knowledge of Star Fleet
Command. Therefore, only those individuals with a "Need to Know" will be informed of
such operations[2]. Therefore, Star Fleet Intelligence was created to plan and execute
such Secret Operations for Star Fleet and the Federation Council in fulfillment of
ARTICLE 8 of the Charter.
Secret or Covert Operations, in general, involve indirect action. For example, in the
case where a legally recognized government was overthrown or taken over by another
power, the Federation Council may authorize Star Fleet to train and advise counter-
revolutionaries in retaking their government. However, under ARTICLE 33 of the Charter,
Star Fleet may not depose, support or establish any form of government on any social
system within or outside the United Federation of Planets without the authorization or
direction from the Federation Council.
OPERATION DEVELOPMENT
Special operations typically begin in the Federation Council. The Federation Council
will issue Executive Orders to Star Fleet regarding the nature of a special task or
mission that it wishes to perform, or specific information that must be obtained. Such an
order will be submitted directly to the Director: Star Fleet Command, who will relay it
to the appropriate division head, or to the Deputy Chief: Star Fleet Intelligence in the
case of a secret or covert operation. It should be noted that the Director can refuse such
an Executive Order if it will violate Federation law, the Articles of Federation, or will
have a negative impact on its public image, or may have a very high probability of failure.
Typically, Executive Orders issued by the Federation Council will be somewhat vague
and general and as such, it will be up to Star Fleet to determine what will be required.
For secret or covert operations, the Star Fleet Office of Intelligence Operations
Planning will begin the process of determining the intent of the Federation Council.
After completing its analysis it will then determine what is needed and how the mission will
be accomplished. Once the operation has been planned, the mission package is handed
over to Star Fleet Intelligence Operations for implementation. Once the operation is
underway the entire mission will be monitored within the Intelligence Operations
Center.

VOLUME II
9.1 STAR FLEET INTELLIGENCE

To support its military and security role, Star Fleet was selected to be the primary source
for all military intelligence for the United Federation of Planets as specified in ARTICLE
8 of the Star Fleet Charter. As such, Executive Order 8.0, which is presented in the
following pages, was issued establishing Star Fleet Intelligence, also known as ICOR,
as the agency within the Department of the Star Fleet charged with performing all
intelligence operations. In addition, this Executive Order also directs the intelligence unit
to work with all Federation intelligence agencies in gathering intelligence information and
to disseminate this information to the Federation Council President, the Security
Council and to any other Federation intelligence agency as may be required by law.
Section 1.4 of this volume provided a detailed description of the Star Fleet Intelligence
(ICOR) subdivision and the offices and units that comprise this command. The high-level
organizational structure for ICOR is shown in Figure 2a91.1. However, the function of this
section is to describe the more secret and clandestine work performed by Star Fleet
Intelligence. As such, this section will concentrate on the unit that deals with intelligence
operations: Star Fleet Intelligence Operations or IOPS.
Star Fleet Intelligence Operations is the primary organization for the collection of
intelligence and the performance of special intelligence operations. The organizational
structure for Star Fleet Intelligence Operations is illustrated in Figures 2a91.2 through
2a91.6. This organization contains all the necessary units for the collection of information,
clandestine or “black” operations, counter-intelligence, and other forms of espionage.
These functions are organized into Units or Specialties depending on the nature of the
operation and the level of secrecy. Such organizations have names such as Spec-8, Unit-
12 or Section 31. In command of IOPS is the Commander: Star Fleet Intelligence
Operations or the COMINTOPS, who is the senior officer in charge of this office and
who has precedence over all the officers, operators and civilian contractors employed
within this office. The COMINTOPS will typically be an officer of the line with the rank of
Rear Admiral.
In the performance of its intelligence-gathering function Star Fleet Intelligence is given

wide latitude in the types of operations it can execute, but is limited in the extent to which
it can take such measures or perform such special operations. As an example, it cannot
depose any sovereign government within or outside the Federation without the direct
authorization from the Federation Council as stipulated in ARTICLE 33 of the Charter, or
perform any assassination or any other such clandestine operation without authorization.
Since the function of this chapter is to describe the more secret or clandestine operations
Star Fleet may engage in, this section will primarily be a discussion of the Clandestine
Service of Star Fleet Intelligence. The Star Fleet Clandestine Service within IOPS
manages and executes the overt and covert operations relating to intelligence for Star
Fleet and for the Federation. The Star Fleet Clandestine Service functions as the
Federation authority for the coordination, deconfliction, and evaluation of clandestine
personal intelligence operations across the intelligence community. The SFCS supports the
Federation’s security and foreign policy interests by conducting clandestine activities to
collect information that is not obtainable through other means. The SFCS also conducts
counterintelligence and special activities as authorized by the Federation Council
President.

VOLUME II

STAR FLEET EXECUTIVE ORDER 8.0: STAR FLEET INTELLIGENCE DIRECTIVE
1. Pursuant to ARTICLE 8 of the Star Fleet Charter, there shall be an agency within the Department of the
Star Fleet for the gathering, analysis and dissemination of intelligence information, herein called Star
Fleet Intelligence.
2. Pursuant to ARTICLE 35 of the Star Fleet Charter, Star Fleet Intelligence shall, at all times, come under
the cognizance of the Department of the Star Fleet, the Federation Joint Chiefs of Staff, the Federation
Council, and the civilian authority.
3. Star Fleet Intelligence shall be responsible for:
a. Monitoring the activities of the enemies of the Federation through observation and reconnaissance;
b. Carrying out operations for the collection of intelligence through personnel or other appropriate
means as directed by higher authority;
c. Correlating and analyzing the information gathered and to make such reports as required to the
Director: Star Fleet Command on the threats to the security of the Federation;
d. Disseminating intelligence information and reports to the appropriate Star Fleet and Federation
agencies;
e. Coordinating intelligence activities with other intelligence agencies within the United Federation of
Planets.
4. Star Fleet Intelligence shall be organized under the Star Fleet Division of Operations and shall develop an
organization to carry out the responsibilities to which it has been assigned.
5. Star Fleet Intelligence shall establish such procedures, methods and instructions required to carry out its
duties and functions. All such procedures shall be considered as classified information.
6. Star Fleet Intelligence shall be commanded by a Vice Admiral with the title of Deputy Chief: Star Fleet
Intelligence in accordance with ARTICLE 43 of the Star Fleet Charter.
7. The Deputy Chief: Star Fleet Intelligence shall organize his command as needed to fulfill his duties and
responsibilities in accordance with Star Fleet Regulation 3810.
8. Star Fleet Intelligence shall have the authority to:
a. Operate independently from the Operating Forces of Star Fleet;

b. Create clandestine operations and espionage units;
c. Perform secret or clandestine operations with approval from higher authority;
d. Perform espionage, counter-espionage, surveillance, demolition, deep-cover insertion or other
secret operations as directed by higher authority.
9. Personnel working for Star Fleet Intelligence shall be highly qualified in the performance of intelligence
methods. As such, Star Fleet Intelligence shall:
a. Seek and recruit highly qualified persons from within or outside Star Fleet;
b. Train its personnel in the art and science of intelligence gathering, espionage and clandestine
operations;
c. Train its operations personnel in interrogation methods and in the methods to resist interrogation;
d. Instill in its intelligence personnel a sense of secrecy and the need to conceal their activities from the
general public or from those that do not have a need to know.
- PAGE 1 OF 3 -

VOLUME II
STAR FLEET INTELLIGENCE DIRECTIVE - CONTINUED
10. Personnel working for Star Fleet Intelligence will have access to highly classified information and as such,
shall be:
a. Intensely investigated and background-checked prior to acceptance into intelligence service;

b. Given high levels of security clearance and access;
c. Continuously monitored and evaluated for the performance of their activities.
11. At all times Star Fleet Intelligence shall keep the activities of its personnel hidden from the general public
or from those that do not have a need to know.
12. At all times Star Fleet Intelligence shall keep the identities of its personnel hidden from the general public
or from those that do not have a need to know.
13. Under special conditions of secrecy or for some other approved reason, special intelligence personnel
may have their true identities altered or removed from any and all databases.
14. Star Fleet Intelligence may hire civilian assistants and other personnel as needed to perform the
administrative duties of the command. However, such personnel shall only hold a clearance level
commensurate with their duties and as such, shall not have access to highly classified or sensitive
information.
15. Star Fleet Intelligence shall issue such reports as necessary to inform higher authority on its activities and
on any results of its activities. All such reports shall be classified TOP SECRET and shall include:
a. The Daily Security Brief;

b. Reports on intelligence activities.
16. All information or assets gathered and analyzed through intelligence operations shall be classified to the
appropriate level of security as required under the regulations established in the Star Fleet Manual for
Classified Information as set forth by the Star Fleet Office of Information Security.
17. Star Fleet Intelligence shall establish the Clandestine Service for the purpose of executing secret, covert
or other operations as required to fulfill its mission.
18. The Clandestine Service may engage in such Covert Operations as:
a. Propaganda, disinformation and other forms of political subversion,
b. Training alien or foreign paramilitary forces for the purpose of political change,
c. Demolition of assets that may affect the security of the Federation,
19. The Clandestine Service may, when engaging in covert operations:

a. Establish front business for the purpose of financing covert operations,
b. Print or produce foreign currency for the purpose of financing an operation or upsetting the financial
system of a hostile power.
20. The Clandestine Service shall not, as a matter of normal course, directly engage in:
a. Political assassinations,
b. Kidnapping or abduction of innocent individuals,
c. Overthrowing governments,
d. Establishing new governments,
e. Clandestine operations in or against Federation member worlds or governments.
21. All Covert Operations shall be so planned and executed as to conceal the identity of or permit plausible
deniability of the Federation government and any of its agencies or member systems.
- PAGE 2 OF 3 -

VOLUME II
STAR FLEET INTELLIGENCE DIRECTIVE - CONTINUED
22. Whenever possible Star Fleet Operations shall support and supply Star Fleet Intelligence with whatever
resources are required to successfully execute and complete covert military operations.
23. Star Fleet Intelligence shall establish the SPEC unit within the Clandestine Service for the purpose of
performing covert military operations. Individuals of this unit shall be recruited from the Special Forces
branches of Star Fleet and of the Local Forces.
24. All individuals within the Clandestine Service performing covert operations shall be called “Operators” or
“Operatives” and shall be designated as such in all communications in accordance with Section 12 of this
Executive Order.
25. Star Fleet Intelligence shall recruit from the Operating Forces highly qualified individuals to perform covert
military operations within the Clandestine Service.
26. Where possible, Star Fleet Intelligence shall recruit citizens of foreign jurisdictions as full-time operatives
for the purpose of surveillance, reconnaissance, information gathering and covert operations. In addition
and where possible, Star Fleet Intelligence may hire or otherwise contract foreign operatives for the
performance of specific covert operations.
27. Star Fleet Intelligence shall have the authority to interrogate individuals for the purpose of obtaining
intelligence information. Any individual known to be associated with a hostile government or is an enemy
of the Federation is subject to interrogation.
28. Active Interrogation for the purpose of obtaining intelligence shall be confined to:
a. The use of chemicals or drugs or both,
b. Mind probing and sifting equipment,
c. Vulcan mind melds.
29. It shall be the policy of Star Fleet Intelligence not to interrogate individuals where no evidence is available
to support such an interrogation or where it is highly probable the individual will not be of any intelligence
benefit. There should be sufficient evidence to warrant the interrogation of individuals for the purpose of
intelligence gathering. This does not, however, preclude the use of passive questioning of persons in
order to gain useful information.
30. It shall also be the policy of Star Fleet Intelligence to work within the provisions of Star Fleet Regulation
8890 regarding the detention and interrogation of individuals for the purpose of intelligence gathering.
However, where there is a severe threat to the security of the Federation, this provision may be waived by
higher authority.
31. Under certain emergency conditions, or in matters of extreme sensitivity or in the performance of special
operations beyond the chartered scope of Star Fleet Intelligence, certain operations may be exempt from
Section 2 and any other section of this Executive Order.
By order of
Director: Star Fleet Command

United Federation of Planets
Stardate 0023.8
- PAGE 3 OF 3 -

VOLUME II
STAR FLEET CLANDESTINE SERVICE
Star Fleet Intelligence Operations contains three primary units or sections designed to
perform specific intelligence operations. These units are: the Clandestine Service, the
Star Fleet Communications Surveillance unit, and Section 31. Each unit is numbered
so as not to identify it by name or function. Specifically, the Clandestine Service will be
regarded as a special branch of the Star Fleet Service specifically created to perform the
majority of the covert operations for the Federation Council and Star Fleet Command.
The organizational structure of the Clandestine Service is shown in Figure 2a91.3, and
the subsequent sections will describe the functions of the units contained within the
Clandestine Service.
THE CLANDESTINE OPERATIONS UNIT
The Clandestine Operations unit is the primary agency within Star Fleet Intelligence
responsible for gathering field intelligence and performing any necessary clandestine or
covert operation. As such, this unit will accomplish its mission either independently or in
conjunction with Star Fleet Special Forces or alongside other Federation intelligence
agencies.
Clandestine Operations contains special Operational Units designed to carry-out any

of the covert operations in foreign or hostile space. Operational Units are special groups
employing civilian operatives under the management of an Operations Officer, who will
be described later in this chapter.
FOREIGN SERVICE
The Foreign Service is a section of the Clandestine Service delegated to train and to
equip personnel for operations within foreign and hostile worlds. Such worlds are usually
outside the boundaries of Federation space and will typically be within the territories of
governments hostile to the Federation. The primary function of the Foreign Service is
to implant operational units within hostile localities so that they can operate freely and
openly among the population.
The Foreign Service will generally involve Star Fleet Intelligence agents assigned to
Federation embassies and other facilities on non-member or foreign worlds. The Foreign
Service also involves establishing and maintaining secret branch offices operating within
non-member Federation worlds. Their primary function is to monitor and report on
activities occurring within the world, but who will not execute any clandestine operation
unless it is necessary for the security of the Federation.
COLLECTION MANAGEMENT
Collection Management is the process by which intelligence information is obtained and

transferred from a field operation to a Star Fleet Intelligence Officer. The collection
unit of an intelligence organization may attempt basic validation of that which it collects,
but is not intended to analyze its significance. In order to collect intelligence information,
the guidance is that the collection requirement will be assigned to one or more source
managers. This process will be discussed in further detail within the subsequent sections.

VOLUME II
SPECIAL OPERATIONS UNIT
Special Operations Units or SPEC Units are special teams created to perform secret
military operations. These units will be composed of selected individuals with special
qualifications, but will also employ or incorporate Special Forces units from the Star
Fleet Marine Corps to perform covert military operations. Spec Units are permanent
teams of military personnel from the fleet and Special Forces. Only the most trusted and
dedicated individuals are selected to become members of these teams and once selected,
they become permanent members of this elite force.
SPEC Teams are composed of highly skilled “operators” trained to perform a variety of
clandestine military operations. Their primary mission is surveillance, observation, advance
reconnoiter, counter-insurgency, demolition and sabotage, deep cover extraction, rescue,
communications tapping and other operations which cannot be discussed openly. In some
cases, the real identities of these operators are unknown or have been placed in the
Federation databank with false identifications and information regarding the individual.
SPEC Teams use special equipment and vessels to accomplish their mission and as such,
are classified to such an extent that the equipment can not be displayed or illustrated in
any document. Descriptions of some of this equipment may be found in Section 9.4.
Table 2a91.1
TABLE OF SPECIAL OPERATIONS UNITS
Spec
Description/Function
Unit
1 Covert Military Advisors; training of insurgents, revolutionaries, etc.
2 Covert Foreign Military Operatives
3 Deep Insertion Unit – Communications and surveillance.
4 Deep insertion Unit – Covert operations, demolition, etc.
5 Deep Insertion Unit – Advanced tactical and reconnaissance.
6 Deep Insertion Unit – Military and governmental infiltration.
7 Undercover Military Operations – non-uniformed.
8 CLASSIFIED

VOLUME II
INTELLIGENCE OPERATIVES
Intelligence Operatives are those persons directly involved in covert or clandestine

operations. Such operations can be military, technological, economic or political in nature.
Intelligence operatives are designated by a code number; for example Operator-11. No
names or other forms of identification are used and the individual holding such a number
will have his or her identity removed from all Federation databanks. Only the Star Fleet
Intelligence databank will contain true the identity of such individuals.
The person in charge of an operative or group of operatives in the field is known as an

Operations Officer, an officer of the Clandestine Service designated to manage a
specific intelligence operation, or who is assigned to gather intelligence from within a
specific location. To do this, an Operations Officer must establish and maintain personal
networks and relationships with foreign "assets" in the field. Operations Officers work
with Collection Management Officers to determine what kind of assets to search for
and what information is needed. Living under cover, many Operations Officers must
also work at their cover or "day" job, a necessary challenge that is part of their clandestine
role. These are usually long-term assignments and involve many complex operations.
The link between the Operations Officer and Star Fleet Intelligence is the Collection
Management Officer or CMO as illustrated in Figure 2a91.7. The CMO is the person
responsible for the Operations Officers assigned to him. As such, the CMO may manage
several operations, each of which will be performed by an Operations Officer and
therefore, the CMO manages several Operations Officers. In essence the CMO is the
connection between the field and the policy community and therefore, is responsible for
guiding the collection of intelligence and directing its dissemination. Managing the
collection effort usually requires determining what the policy makers and intelligence
analysts need to know, and then communicating those requirements to the Operations
Officer. To be effective, they must understand operational tradecraft and intergalactic
issues. These officers may serve or have offices at the various Starbases or Star Fleet
stations and will report directly to Star Fleet Intelligence Operations at Star Base
Central.
Overseeing the entire operation is the role of the Staff Operations Officer or SIO, the
highest ranking operations officer within Star Fleet Intelligence. SIOs are generally
assigned to a Federation Octant and therefore, there will only be nine SIOs within the
Clandestine Service, including one assigned to the Treaty Zone. These officers will
work within the Sector Intelligence Office and will support the Commander: Sector
Intelligence. The SIO has offices located at the Sector Base and in the Intelligence
Operations Center on Star Base Central. The primary function of the SIO is to provide
fast-paced research and case management in support of their colleagues in the field. This
includes monitoring counterintelligence issues and providing the support needed to deal
with foreign and alien contacts in the field. As such, the Staff Operations Officer must
be knowledgeable on both operational tradecraft and intergalactic issues so that they can
interaction with their field-based officers.
In general, Operations Officers and Collection Management Officers spend a

significant portion of their time away from their homes, on tours of two to four years.
Typically, Operations Officers will serve 60% to 70% of their careers on other worlds,
while Collection Management Officers will be in the field for 30% to 40% of their
careers. Staff Operations Officers, although based on Star Base Central, may travel
to other worlds on a temporary or as needed basis.

VOLUME II
CLANDESTINE LIFE
Officers in the Clandestine Service basically function under cover. By the very nature of
this business, officers can expect only limited external recognition for themselves and their
families. Instead, Star Fleet Intelligence has its own internal promotions, awards and
medals, and makes every effort to recognize the accomplishments of its personnel.
Officers are paid well in terms of regular income, and receive non-taxable allowances that
generally permit them to focus on their work and enjoy a decent standard of living. The
majority of these officers live comfortably well by any standard of living, make significant
contributions that impact Federation security, and generally experience a high level of
job satisfaction and camaraderie throughout their career.
Traditionally, Star Fleet has a corps of Operations Officers of considerable diversity in

terms of politics, talent, personality, temperament and background. That said, there are
some fundamental qualities common to most successful operatives, including a strong
record of academic and professional achievement, excellent writing skills, problem-solving
abilities and highly developed interpersonal skills. Alien experience and languages are
important factors as well. Operations Officers must be perennial students, in the sense
that they are required to seek answers, learn other languages and study other cultures in
order to enhance their abilities to deal effectively with foreign cultures and societies.
SECTION THIRTY-ONE[3]
Section 31 is the name of a classified intelligence and defense organization which is a

special security operation manned by Star Fleet and Federation intelligence operatives
that are not subject to the normal constraints of Star Fleet ethics or protocols. Section
31, established in 2245, is essentially an officially nonexistent agency within Star Fleet
that operates outside Star Fleet Intelligence’s influence which deals with threats to the
Federation’s security. Its operating authority stems from the liberal interpretation of
ARTICLE 26 of the Star Fleet Charter, but primarily from Directive 31 of Star Fleet
Executive Order 8 from which its name is derived. This directive makes allowances for
"bending the rules" during times of extraordinary threats.
Unlike other organizations, Section 31 does not exist to enforce government policy, but
rather to defend against internal and external threats. As a result of numerous security
leaks within other intelligence agencies, Section 31's actions are autonomous and are not
controlled by Star Fleet Command or the Federation government. Most people within
the Federation have never heard of Section 31 and will never encounter it.
An example of how independent and powerful this organization has become occurred in
2257. The Federation at the time was in the midst of a “drug war.” Many criminal
organizations were making extensive profits from the sale and distribution of illegal drugs
smuggled into Federation space with the help from the Romulan Empire. Section 31
took it upon itself to do something about it. Eventually, Section 31 infiltrated many of the
crime organizations and secretively assassinated many of their leaders. The opinion at the
time was that the deaths were attributed to strong rivalries among the various criminal
organizations, which contributed to the violence between the groups. But that was
Section 31’s plan of action all along. As a result, the flow and distribution of illegal drugs
into the Federation was reduced by 80%.

VOLUME II
Figure 2a91.1
STAR FLEET INTELLIGENCE ORGANIZATION
2400
Federation Intelligence Agency Star Fleet Intelligence
ICOR
Intelligence Office of Intelligence Office of Intelligence Office of Intelligence
IOPS Operations INAL Analysis IPER Personnel ISYN Coordination
2450 Star Fleet Member System

Office of Intelligence Intelligence
ITEK Technology Agencies

VOLUME II
Figure 2a91.2
2410 Star Fleet

Intelligence
IOPS Operations
Clandestine Intelligence Intelligence Communications
IOPS Service IOPSPLN Operations Planning IOPSCEN Operations Center IOPSURV Surveillance
****
CLASSIFIED
SECTION 31

VOLUME II
Figure 2a91.3
STAR FLEET CLANDESTINE SERVICE
2411 Star Fleet

Clandestine
IOPS Service
2411-1 2411-2 2411-3 2411-4

Clandestine Foreign Collection Special Operations
Operations Service Management Unit
IOPS IOPS IOPS SPEC
2411-1.1 2411-5 Clandestine

Interrogation Section Materials Special Forces Units
IOPS IOPS Section

VOLUME II
Figure 2a91.4
STAR FLEET INTELLIGENCE OPERATIONS PLANNING

Federation Intelligence Agency Intelligence Office of Intelligence
IOPSPLN Operations Planning ICOR Analysis
2412-1 Intelligence 2412-2 Intelligence 2412-3 Intelligence 2412-4 Intelligence

Operations Operations Operations Asset Management
IPLNSUP Logistics Section IPLNEQP Equipment Section IPLNCOM Communications IPLNPER Section
2412-5 Special Forces

Liaison
IPLNSPF Office

VOLUME II
Figure 2a91.5
STAR FLEET INTELLIGENCE OPERATIONS CENTER
2413 Star Fleet

Intelligence
IOPSCEN Operations Center
24131 Operations Center 24132 Operations Center 24133 Operations Center 24134 Operations
Equipment Operations Field Communications Maintenance Simulators
IOPSCEN Section IOPSCEN Section IOPSCEN Section IOPSCEN Section

VOLUME II
Figure 2a91.6
STAR FLEET COMMUNICATIONS SURVEILLANCE

Office of Communications
FLTCOMM Fleet Communications IOPSURV Surveillance
24141 Surveillance 24142 Surveillance 24143 Communications 24144 Surveillance

Equipment Networking, Switching Surveillance Computers
ICOR Section ICOR and Recording Section ICOR Maintenance Section ICOR Section
2420 Star Fleet

Office of Intelligence
INAL Analysis

VOLUME II
Figure 2a91.7
THE SECTOR STAFF OPERATIONS OFFICER CHAIN OF COMMAND
29<n>5 Commander: 2411-3n Staff Operations

Sector Intelligence Officer
COMSECINT SIO<n>
2411-3n1 Collection 2411-3n2 Collection 2411-3n3 Collection

Management Management Management
CMO<n>.1 Officer CMO<n>.2 Officer CMO<n>.3 Officer
2411-3n1.1 2411-3n1.2 2411-3n1.3

Operations Operations Operations
OPSO<n>.11
Officer OPSO<n>.12
Officer OPSO<n>.13
Officer
Assets
Paid Informants Recruited Operatives Intelligence Agents

VOLUME II

VOLUME II
9.2 INTELLIGENCE GATHERING METHODS

In fulfillment of ARTICLE 1 of the Star Fleet Charter to protect the Federation and
ARTICLE 8 of the Charter, which identifies Star Fleet as the primary agency for the
collection of galactic intelligence, Star Fleet Intelligence has as its disposal many
methods in which to gather intelligence information. The function of this section is to
describe the various methods in which intelligence is gathered. Some of these methods
may not be pleasant, but are very necessary.
In general, intelligence gathering is essentially non-destructive. That is, it usually does not
require harm to life or property. The main purpose of these gathering methods is to obtain
information or to understand a new or different technology, the military and political
tactics and strategies of hostile forces, the plans and policies of Federation enemies, or
simply to understand the psychological makeup of alien or hostile peoples. Usually, most of
the information collected will be used to further the technological capabilities of Star Fleet
for the protection of the Federation or to further the general technological knowledge of
the Federation. As such, most of the operations executed by Star Fleet Intelligence
will be those directed towards obtaining technical information.
In obtaining intelligence information, however, it must be noted that this process may also
involve acquiring government or industrial secrets as well. The primary aim of absconding
with such secrets is to ensure the protection of the Federation and to counter any threat
that may be imposed on the Federation due to the use of special or alien technology or
strategies. The methods used by Star Fleet Intelligence are generally clandestine and
secretive, and Star Fleet Intelligence is currently engaged in many clandestine
operations inside and outside the Federation, most of which are passive in nature.
There are essentially two types of methods of gathering intelligence: Passive and Active.
Each one of these methods will be described in the following subsections.

VOLUME II
PASSIVE METHODS
A Passive Method of intelligence gathering is one in which there is no active participation

in a mission or operation designed to gather intelligence information. Most of the passive
methods involve listening, either to social chatter or through special listening devices.
Other methods include observing, watching and taking pictures. In addition, there are
casual ways of getting the information such as asking innocuous questions or observing
certain actions. However, the most common method of intelligence gathering is with the
use of active monitoring, sensing and listening devices.
Questioning is also a common form of passive intelligence gathering. Innocuous questions

asked during social occasions or situations, such as in bars where tongues may be loose,
can yield valuable information. This form of questioning is also employed by the Star
Fleet Bureau of Investigation and the Star Fleet Investigative Service. Agents
from these services will loiter around bars, taverns and other such places to listen in on
conversations.
However, surveillance is the most common form of passive intelligence gathering as it, in
most cases, is performed continuously and automatically by listening and sensing devices.
Surveillance also includes watching and taking still and motion pictures using micro
cameras and other sensing devices. Great care is required to prevent being discovered
while in the process of taking pictures.
Communications monitoring is a major form of surveillance. Star Fleet has many hidden
"listening" stations out in deep space where all communications are monitored. High-speed
supercomputers are used to listen-in on conversations to pick-up key words or phrases
which may indicate some clandestine operation in Federation space.
In addition, Star Fleet Outposts and Communications Relay Stations are also
designed to listen in and pick up foreign communications as well. These stations are
typically located at the boundaries of Federation space and will pickup electromagnetic
and subspace signals from origins light-years away*. All such signals will be routed to Star
Fleet Intelligence for analysis.
Listening also includes the use of listening devices in order to overhear conversations from
a distance. Star Fleet Intelligence has special listening devices that do not necessarily
require picking-up sound, but can listen via the transmission of vibrations through any
substance.
Passive methods also include reading media and periodicals. Special computers are used to
scan written materials from novels to periodicals looking for possible code phrases and
patterns. Most of this work is performed by the Star Fleet Office of Intelligence
Analysis.
*The actual distances from where a Relay Station can actually pickup foreign communications is CLASSIFIED.

VOLUME II
ACTIVE METHODS
Active Methods are defined as those intelligence activities where clandestine or covert
action is necessary in order to gather intelligence information. Such operations generally
involve some form of activity such as entry into secured areas, installation of surveillance
and listening devices, etc. Some of these methods may involve criminal activity.
In most cases active intelligence gathering will require deep cover insertion. Deep-cover
Insertion (DCI) is the process by which an operator (DCIO) secretly infiltrates a world,
society or group. The function of the DCIO is to work within the societal framework as a
member of that group. The operator may openly operate or move about, or may use local,
paid recruits to work for the operator, or may seek out paid informants. Regardless, these
paid operators will become part of a special group assembled to acquire the needed
intelligence information.
Societal Infiltration is the deep-cover method by which a Star Fleet operative will be
assigned a foreign world in which to infiltrate. The operative will live among the indigenous
peoples for the purpose of gathering general or specific intelligence. Eventually, the
operative is expected to infiltrate important positions, or positions of confidence, trust or
influence for the purpose of espionage.
Societal Infiltration (commercial private businesses, military, technology, etc.) may also
involve changing one’s physical appearance in order to intermingle with the population or
environment. This may be necessary if local natives cannot be recruited as operatives to
perform the covert missions. This takes a special individual who is willing to undergo the
special surgical procedures required to change one’s physical appearance. This operation
may be required in situations where it may be impossible to recruit a local agent or where
using non-indigenous personnel would be easily recognizable and would not normally be
welcomed or in the extreme case with hostile worlds, be harmed, imprisoned or executed.
Active methods also include penetrating secured or unsecured locations for the purpose of
extricating or absconding with documents or equipment, or to take pictures of documents,
drawings or equipment. Since the operator will be working alone, since, in most cases, the
agent will not have the luxury of covertly transporting into the target facility, the operator
must use manual methods to obtain the intelligence information sought after. This is the
most dangerous form of active method.
Active methods also include interrogating high-value individuals. Such methods are used to
obtain specific information regarding plans or policies against the Federation, such as
forces, numbers, etc. This may require the abduction of a high-valued individual who will
be taken to a secured location for interrogation.
Active methods may also include the use of Star Fleet Marine Corps Special Forces
units. Their function is to execute special clandestine military operations on behalf of an
intelligence operation in places where an intelligence agent must keep his or her identity
secret and their involvement anonymous. Special Forces units will routinely execute such
operations where a high degree of risk and danger is involved.

VOLUME II
INTERROGATION
The purpose of interrogation is to acquire information from a person known or suspected

to possess intelligence information. Since the person being interrogated is often not
comfortable with the process or even willing to divulge information, the interrogation
process is different from a conversation. In a conversation information is freely exchanged
and offered. However, interrogation is a less compliant process. Interrogation can take
different forms, but these all have a similar aim: to control the subject in such a way that
he or she yields to pressure and provides the information being asked for.
Interviewing is a form of interrogation, but is a less threatening method. This method

primarily involves asking predetermined questions. The answers to these preset questions
will determine the subsequent questions the interviewer will ask. The use of special
equipment may also be used to monitor the individual on the accuracy of the information -
whether he or she is telling the truth as seen in Figure 2a92.1. Special chairs have been
developed that will monitor an individual for signs that he or she is not being truthful. An
example of such a chair can be seen in Figure 2a92.2.
The use of force, mental torture, threats, insults, or exposure to unpleasant and inhumane
treatment of any kind is prohibited by law and is neither authorized nor condoned by the
Federation government. Experience indicates that the use of force is not necessary to
gain the cooperation of sources for interrogation. Therefore, the use of force is a poor
technique as it yields unreliable results, may damage subsequent collection efforts, and
can induce the source to say whatever he thinks the interrogator wants to hear. However,
the use of force is not to be confused with psychological ploys, verbal trickery, or other
nonviolent and non-coercive ruses used by the interrogator in questioning hesitant or
uncooperative sources.
It must be noted that the behavior of the interrogator is also an important part of the
interrogation process. For example, a comforting word or supplying water and food can
make a victim grateful enough to yield to a request for information. Conversely, degrading
or demeaning behavior can cause the victim to give up. To know which method to use on
an individual requires a highly trained and skilled interrogator.
Interrogation may often involve the capture of enemy combatants, particularly during war-
time conditions. As such, prisoners captured must be treated in accordance with agreed
conventions and that Star Fleet Regulation 8890 must be strictly adhered to.
Interrogation may also involve the use of mind sifting equipment. One technique used by
Star Fleet Intelligence is the use of a Neural Neutralizer device developed by Dr.
Simon Van Gelder, as illustrated in Figure 2a92.3, or may involve the use of Vulcans to
probe the mind for such information as illustrated in Figure 2a92.4.
The following table lists most of the manual interrogation techniques opened to use by
interviewers. It compares how the Federation employs these techniques (if at all) to how
governments outside of the Federation may employ them. Many of the techniques are
forbidden by law, but as the table will show, they will be used by the enemies of the
Federation. This list is used by Star Fleet Intelligence to train their operatives in the
use of such techniques and how to withstand or endure them, should they be employed
against them.

VOLUME II
Table 2a92.1
TABLE OF MANUAL INTERROGATION TECHNIQUES
Hostile Governments
Technique Federation Romulan Klingon
Empire Empire
Indirect, deceptive, or misleading questions YES YES YES
Direct, straightforward questions YES YES YES
1
Yelling at detainee YES YES YES
Deception: multiple interrogators YES1 YES YES
Deception: Interrogator is from a world with
reputation for harsh treatment of detainees; “False YES1 YES YES
Flag”
Incentive or removal of incentive YES YES YES
Playing on a detainee’s love for a particular group YES YES YES
Playing on a detainee’s hate for a particular group YES YES YES
Significantly/ or moderately increasing fear level of
YES YES YES
detainee
Reducing fear level of detainee YES YES YES
Boosting the ego of detainee YES YES YES
Insulting the ego of detainee, not beyond the limits
YES YES YES
that would apply to a POW
Invoking feelings of futility in detainee YES YES YES
Convincing detainee interrogator knows all YES YES YES
Convincing detainee that interrogator has mistaken
YES YES YES
detainee for someone else
Continually repeating same questions to detainee
YES YES YES
during same interrogation period
Convincing detainee interrogator has
YES YES YES
damning/inaccurate file, which must be fixed
Good cop, bad cop YES YES YES
Rapid fire questioning w/ no time for answer YES YES YES
Staring at detainee to encourage discomfort YES YES YES
New interrogation environment: change of scenery 1
YES YES YES
up/down
Dietary manipulation NO YES YES
Use of stress positions (e.g. prolonged standing) NO YES YES
Notes:
1. Approved for discretionary use.

VOLUME II
Table 2a92.1
TABLE OF MANUAL INTERROGATION TECHNIQUES - CONTINUED
Hostile Governments
Technique Federation Romulan Klingon
Empire Empire
Use of falsified documents or reports in interrogation YES1 YES YES
Isolating prisoner for up to 30 days NO YES YES
New interrogation environment: better or worse YES1 YES YES
Sensory deprivation (light and auditory stimuli) NO YES YES
1
Hooding (during transportation and questioning) YES YES YES
Prolonged interrogations (e.g. 20 hours) YES YES YES
Removal of comfort items (including religious items) YES YES YES
Removal of detainee’s clothing YES YES YES
Forced grooming, including shaving of beards, etc. YES YES YES
Using detainee phobias (e.g. fear of dogs) to induce
YES YES YES
stress
Face slap or stomach slap (limited to 2 slaps per
NO YES YES
application and 2 applications per interrogation)
Physical training (forced calisthenics) NO YES YES
Sleep adjustment (adjusting sleep cycles, i.e. evening
YES1 YES YES
to morning; not sleep deprivation)
Sleep deprivation (not to exceed four days) NO YES YES
Threatening to transfer detainee to a country from
NO YES YES
which he would fear death or torture
Environmental manipulation (exposing detainee to
NO YES YES
temperature adjustment or unpleasant smell)
Exposure to cold weather or water (with appropriate
NO YES YES
medical monitoring)
Threat of imminent death to detainee or his family
NO YES YES
members
Use of wet towel and dripping water to induce
NO YES YES
misperception of suffocation
Use of mild, non-injurious physical contact such as
NO YES YES
grabbing, poking in the chest, and light pushing
Use of mind probes or mind sifting devices YES YES YES
Notes
1. Approved for discretionary use.

VOLUME II
Figure 2a92.1
ACTIVE INTERROGATION ON BOARD A STARSHIP

VOLUME II
Figure 2a92.2
DEMOSTRATING THE INTERROGATION CHAIR

VOLUME II
Figure 2a92.3
ACTIVE INTERROGATION TECHNIQUE USING A NEURAL NEUTRALIZER

VOLUME II
Figure 2a92.4
ACTIVE INTERROGATION USING THE VULCAN MIND-MELD TECHNIQUE

VOLUME II
9.3 SPECIAL SHIP MISSIONS

Special ship missions or SPECOPS, as they are called, are covert operations designed to
perform some military objective using regular Star Fleet assets instead of using special
intelligence assets. For example, Star Fleet Intelligence does not have combat vessels,
but will utilize fleet assets to perform certain clandestine military operations, as well as the
use of Intelligence (IT-class) vessels to perform special operations. These vessels are
primarily used for communication and surveillance operations in and around hostile areas.
They are equipped with stealth capabilities, which make them virtually undetectable to
sensor probes. As such, they may be used to penetrate the space of an adversarial power
for intelligence gathering purposes. In general, the use of combatant or military vessels by
Star Fleet Intelligence is solely for those special operations that are military in nature.
SPECOPS also include certain operations whereby a combatant will be used to test the
capabilities of another combatant from a hostile world such as with a Romulan ship - short
of armed conflict. These tests are designed specifically to obtain information on the target
vessel's capabilities such as maximum speed, maneuvering capability, rate of acceleration,
size, mass, sensor range, and possibly shield strength. Such information is extremely
valuable for planning the tactics required should a Star Fleet ship engage such a vessel in
combat.
The missions described herein have been declassified and are no longer TOP SECRET.

VOLUME II
SPECOPS CASE STUDY
One such SPECOPS mission involved a Star Fleet ship that entered Romulan territory in
order to abscond with a new cloaking device the Romulans had developed. The new device
was compact and with the right link to the warp engines, could easily be mounted on any
warp-driven vessel. It had only recently been known that the Romulans were purchasing
warp-driven D-7 cruisers from the Klingons since they were far behind the other worlds in
warp drive technology. However, the Klingons did not have a working cloaking device and
as such, the D-7 sold to the Romulans needed to be modified. Deep cover agents of the
Federation discovered this and sent the information to the Federation Intelligence
Agency. This caused great concern since warp-driven enemy warships can now enter
Federation space undetected. Therefore, it was decided that the Federation would need
to steal such a device in order to return the balance of power back to the Federation.
The task of performing this clandestine mission fell to the Military Staff Committee and
Star Fleet. Star Fleet Intelligence developed the mission profile and a Star Fleet ship
was chosen (the name of the ship still remains classified.) The ship was to enter Romulan
space where it was anticipated that it would immediately be intercepted by the Romulan
fleet. A capital ship was chosen so that it would not be immediately destroyed. The belief
was that such a ship would be a valuable prize to any commander who could capture a
Starship intact. The commander of the Starship would feign insanity as the reason for
the incursion into Romulan territory. The commander of the Romulan fleet in that area was
a female known to have a certain yen for Vulcan males. Therefore, a Vulcan officer would
be used to distract the commander while a member of the crew would infiltrate the ship,
locate the cloaking device, remove it and take it back to the ship undetected. The actual
method and procedure employed still remains CLASSIFIED.
It should be noted that missions involving the entry into a Neutral Zone requires special
authorization from the Federation Council. However, such authorization is usually done
in secret and any documentation regarding such approval is placed under the strictest of
security and never placed in the general archive. Therefore, no record of the mission was
ever recorded or the profile ever entered into the ship's computer. Only face-to-face
communication with the ship's Commanding Officer was performed in order to conceal
the operation and limit the exposure of the mission.
MISSION REPORTS
After each mission a detailed report is required. The reports for all classified missions will
be bound in a special red binder affixed with a special magnetic lock as illustrated in
Figures 2a93.1 and 2a93.2. These reports are stored at Central Records within a special
sealed vault where all such classified reports and documents are stored. The information is
recorded in this fashion in order to prevent accidental or purposeful exposure of the
material should it be electronically recorded. An example of such a report will be illustrated
in the subsequent pages. This example is of the recently declassified Romulan-Klingon
Technology Agreement report issued in 2268, which was used as the basis for the above
case study.

VOLUME II

VOLUME II
OFFICE OF INTELLIGENCE ANALYSIS

STAR FLEET INTELLIGENCE
TOP SECRET
INTELLIGENCE NOTICE 8123
ROMULAN-KLINGON TECHNIOLOGY AGREEMENT
EXECUTIVE SUMMARY
1. An agreement was secured between the Romulan Star Empire and the Klingon Empire relating to the
sharing of strategic technology. The Romulan Empire has always sought to upgrade their fleet with warp
drive technology, which has eluded them up to this point. The Klingon Empire, on the other hand, would
like to gain a strategic advantage over the Federation. The result was a joint agreement to share some of
their most sensitive technology.
2. Through sources inside the Klingon Empire, the agreement was ratified Stardate 21780.97 and went into
effect Stardate 21791.81. It is anticipated that the Romulan Empire will have an operational cloaked warp-
driven space cruiser within the next several months.
3. The specifics of the agreement are as follows:
a. The Klingon Empire provide to the Romulan Empire the design of their D-7 Battlecruiser;
b. To provide support to the Romulan Empire in the development of warp-driven spacecraft;
c. In return, the Romulan Empire will support the Klingon Empire in the joint development of a
cloaking device geared for warp-driven spacecraft.
4. As a result of this agreement the Romulan Star Empire is decommissioning their fleet of sublight “Bird of
Prey” warships with warp-driven battlecruisers of the Klingon D-7 design. It is also anticipated that these
new vessels will be equipped with cloaking devices to render their vessels invisible to our sensors. In
addition, the Klingon Empire is expected to develop a new class of warship utilizing cloaking technology.
This new vessel design is expected to become operational within the next ten years.
RECOMMENDATIONS
1. Maintain constant surveillance of the Neutral Zone for any unusual activity and to observe any new forms
of vessels operating within Romulan space.
2. It is recommended that the Federation appropriate, by any means possible, this new cloaking device in
order to re-establish the balance of power within the galaxy.
3. Renegotiate the terms of the Treaty of Algeron regarding the size of the Neutral Zone. It is recommended
that the zone be widened to at least 5000 AU.
Submitted: Approved:
Commander: Intelligence Analysis Deputy Chief: Star Fleet Intelligence

Stardate 21925.86

VOLUME II
Figure 2a93.1
EXAMPLE OF A CLASSIFIED REPORT BINDER

VOLUME II
Figure 2a93.2
CLASSIFIED REPORT EXAMPLE: TALOS IV REPORT

VOLUME II
9.4 SECRET OPERATIONS

Secret Operations are those planned and executed by the Clandestine Service for the
purpose of executing some specific policy, which can only be approved by the Federation
Council. However, the planning and execution of such operations will exclusively be
performed by Star Fleet Intelligence. Most of the operations that will be performed by
the Clandestine Service will be secret in nature and will either be covert or clandestine.
Covert and Clandestine action take many different forms reflecting the diverse
circumstances in which they are used. Each of these operations will be explained in more
detail in the subsequent paragraphs.
CLANDESTINE OPERATIONS
A Clandestine Operation is a military or intelligence operation carried out in such a way

that the operation goes unnoticed. Star Fleet defines a Clandestine Operation as: “An
operation sponsored or conducted by Star Fleet or by Federation agencies in such a way
as to assure secrecy or concealment.” A Clandestine Operation differs from a Covert
Operation in that emphasis is placed on concealment of the operation rather than on
concealment of the identity of the sponsor. In special operations, an activity may be both
covert and clandestine. As such, both will equally focus on operational considerations and
intelligence-related activities.
Although the bulk of clandestine operations will be related to the gathering of intelligence,
other clandestine operations may include sabotage or some other active military operation.
In such operations the military personnel involved must remain undetected at all times. As
part of their duties, military operators may be requested to direct attacks against ground
targets, or be involved in the placement of observation devices, sensors, and other such
systems that may be required in order to obtain useful information.
There are also clandestine operations that are political in nature. These will generally be
aimed at assisting groups or governments favored by the Federation, or in undermining
groups or governments opposed by the Federation. The majority of such operations will
be performed outside of Federation space, but it is possible that clandestine operations
may be performed on systems within Federation territory as well. However, it is against
Federation law to perform clandestine operations on any member system government,
which is covered under General Order Three. As such, clandestine operations such as
those which support opposition groups against a non-member government that is not
friendly to the Federation may be performed. The basic purpose for such action is to
support any action that will help shape a government friendly to the Federation, but not
to directly install one using Federation assets. The reason for this is that it is generally
counter-productive to have governments within the Federation opposing the goals of the
Federation or that is hostile to its philosophy. The goal is to make a government friendly
towards the Federation without violating the principles on which the Federation was
formed.

VOLUME II
COVERT OPERATIONS
Star Fleet defines a Covert Operation as: An operation that is so planned and executed
as to conceal the identity of or permit plausible denial by the sponsor. As such, a Covert
Operation differs from a Clandestine Operation in that the emphasis will be placed on
concealing the identity of the sponsor (Star Fleet or the Federation) rather than on the
concealment of the operation.
Covert Operations are military or political activities carried out in such a way that the
parties responsible for the action are not identifiable. Alternatively, the identity of the
parties responsible can be an open secret, but cannot be proved. Covert Operations are
typically performed in secrecy because they break specific laws or compromise policy in
another system or sovereign territory. Covert operations are frequently illegal in the target
territory and are sometimes in violation of the laws of the Federation. However, such
operations can be accomplished by having other agencies or groups covertly perform the
operation.
Covert Operations are employed in situations where operating openly against a target
would be politically or diplomatically risky, or be counterproductive to the mission's goal. In
the case of enemies, there may be issues regarding violation of neutrality, concerns over
military strength, the presence of treaties, laws, moral principles, or aversion to negative
media attention. Such operations may be directed at or conducted with allies and friends
to secure their support or to influence or assist their policy against an enemy. Covert
Operations may assist espionage efforts, or may diverge from such efforts by attempting
to influence events in another system directly.
Covert Operations have been employed by many governments and organizations for
centuries, with or without a formal intelligence agency. They are an established and often
controversial component of government policy throughout the galaxy and are often called
"active measures". A common tactic in Covert Operations is to establish a front business
or organization through which agents can operate unrecognized. In addition, such front
businesses will also be used to fund the operation.
In addition, there are also paramilitary operations, in which Star Fleet trains, supports, or
advises a military force of another system. This is where there is political subversion or the
attempt to overthrow structures of authority in which the Federation supports or where it
advises a political or military group within another system or directs propaganda at its
population, but which cannot directly be performed by the Federation government. In
disinformation operations, forged documents are provided to another government in order
to turn that government against an enemy. Some of the most controversial covert actions
are those directed against individuals, such as kidnappings, assassinations, and coups
d’état. However, such operations are not condoned by the Federation and are illegal
under Federation law, but that does not imply that they do not occur.

VOLUME II
MANAGEMENT OF COVERT AND CLANDESTINE

OPERATIONS
Covert and clandestine operations are generally managed and performed by officers of the
Clandestine Service. In terms of field operations, the Clandestine Service consists of
three different types or levels of operations management officers:
1. Staff Operations Officers: The highest operational level within the Clandestine
Service. These officers provide the various forms of fast-paced operational research
and case management support needed by their colleagues out in the field. They must
develop substantive expertise on their assigned area in order to enhance their dealings
with field-based officers, and will provide advice and counsel on events in the field.
This track requires officers who can work quickly to establish contacts throughout the
entire Service in order to meet field requirements. All of these officers will have the
rank of Captain, SFC, and have the title Star Fleet Staff Operations Officer.
2. Collection Management Officers: These officers are the connection between the
Operations Officer in the field and the Federation policy-making community, both
in Federation and non-Federation space. They guide the collection of intelligence
and direct the dissemination of that intelligence. Managing the collection effort will
require contact with Federation policymakers in order to determine what they need
to know, and then communicating those requirements to the Operations Officers in
the field for collection. They must also understand operations and local operating
environments, as well as maintain substantive knowledge about the societies, worlds
and issues against which the Service is collecting information. These officers will
typically have the rank of Commander, SFC, and will have the title of Star Fleet
Intelligence Collection Management Officer.
3. Operations Officers: These officers, also known as "Case Officers", are responsible
for the actual collection of intelligence information. Case Officers will typically recruit
local resources, in the form of active assets (agents) or paid informants, as much as
possible to do the work for them and to keep themselves hidden from the operation.
This allows a Case Officer to establish an intelligence network throughout their
operating area. Typically, they work undercover, either as a diplomatic person in an
embassy or as a private individual within the society. These officers will typically have
the rank of Lieutenant Commander, SFC, and have the title of Star Fleet
Intelligence Operations Officer.
4. Non-management officers of Star Fleet Intelligence working in the field, either
alone or under an Operations Officer, will have a title of Operator. Operators can
be local personnel, other Star Fleet Intelligence operatives or Special Forces
operators from the Star Fleet Marine Corps.
All covert and clandestine operations are managed and monitored within the Intelligence
Operations Center located at Star Base Central.

VOLUME II
CLANDESTINE OPERATIONS EQUIPMENT
In order to carry out clandestine operations, special equipment may be necessary. Such
equipment is specifically designed for clandestine operations and can only be obtained or
issued by Star Fleet Intelligence. The Star Fleet Office of Intelligence Technology
will develop the specialized equipment used in covert or secret operations, and only Star
Fleet Intelligence is licensed to produce such equipment and by law cannot lend, sell or
give away this equipment, nor is it authorized to provide other Star Fleet divisions or
forces with such equipment. Star Fleet Intelligence is fully accountable for every piece
of specialized equipment it produces and uses. A sampling of some of these devices will be
described below.
Special communications devices will be used that allow operators in the field to directly
communicate with the Intelligence Operations Center. Such special devices provide for
the two-way communications of intelligence operations and a means of tracking the
operator during the operation. Some of the special communications devices may include
subdural or brain implants as well.
Special sensors will generally be used to warn or notify a field operator of an approaching
threat – usually while in the process of performing a covert operation. This type of sensor
is usually in the form of a motion detector.
However, there are also sensing devices used to record specific information on equipment
such as the heat or radiation emissions of a piece of equipment, or a certain noise or
vibration signature. Such devices will be used to obtain information that will be used to
detect, identify and track a piece of equipment or vessel. And finally, there is special
sensing equipment that is used to make a visual picture of an object. Such devices allow
Star Fleet Intelligence to obtain real-time information through such visual and/or audio
devices.
The Clandestine Service has many listening and surveillance devices. Some are portable
and some permanent. The permanent devices are those that may be built into structures
or vessels for the purpose of listening or visually obtaining intelligence information. Such
devices are referred to as bugs, horns, flies and ears.
Clandestine operations may require the use of special weapons. Primarily, these are small
hand weapons that are difficult to detect and may not appear as a standard weapon. In
addition, special weapons also include explosives.
Though not equipment per se, intelligence operatives may also carry or use special drugs
or narcotics. Such drugs come in two forms: 1) for use against a target for the purpose of
extracting information, or 2) illegal substances that may be used to barter or bargain with
individuals in order to obtain intelligence information. However, it must also be stated that
Star Fleet does not authorize the use of or equip their operatives with suicide drugs.
The Clandestine Service also has Special Insertion Vehicles or SIVs that may be
used to infiltrate the sovereign space of another power without detection. Such vehicles
use the latest in cloaking technology and sophisticated propulsion technology to propel
them trough space undetected as they make no wave signature or leave any residual
particles or radiation behind. These vehicles are so highly classified that a picture or even
an artist’s rendering of it is prohibited.

VOLUME II
USE OF SPECIAL FORCES
Clandestine Operations may also involve the use of Special Forces as well. Special
Forces will generally be formed into SPEC units designed for a specific purpose or
mission. The function of Special Forces in clandestine operations is to:
a. To aid a Clandestine Service Operator.

b. Perform special military operations.
Special Forces operations will utilize the latest in clandestine technology. For example,
Special Forces will use SIVs to “sneak” into a planetary system undetected. In addition,
Special Forces personnel will also be equipped with special weaponry not available to the
general Star Fleet Service population.
Special Forces may be used to extract high-value individuals for intelligence purposes.
Primarily, such extractions will be executed to allow individuals to escape a particular
situation. However, there may be times when the extraction is performed on an unwilling
high-value individual. This is not a violation of Section 20 of Executive Order 8 since
such persons would not be considered an innocent victim.
During times of war or conflict, Special Forces will be used to accomplish special military
intelligence missions. Such missions include destroying key command and control centers,
working within enemy space, killing high-value military targets, performing reconnaissance
on where assault troops can be landed, and to set up listening and surveillance posts.

VOLUME II
SECTION 31 OPERATIONS
Operations performed by Section 31 are highly classified and in the majority of cases,
totally unknown to Federation or Star Fleet agencies. As previously stated, Section 31
is a virtually autonomous organization.
Due to the classified nature of such operations, the missions performed by Section 31 are
completely unknown and too highly classified to be presented in any forum and therefore,
cannot be discussed. In addition, Star Fleet does not even acknowledge the existence of
this agency. Therefore, it is Star Fleet's policy to deny the existence of any Section 31
operation.

STAR FLEET GUIDE
VOLUME II
1.0 INTRODUCTION
The function of the Star Fleet Guide is to provide a background explanation of the
reasons why the Star Fleet, as well as the United Federation of Planets, was created in
the manner presented in Star Fleet Command Manual.
The history of the Star Fleet Command Manual goes back to 1973 after the book “The
Making of Star Trek” came out. At the time this author was in the U.S. Navy Submarine
Service. Being on a nuclear submarine is very close to being in a space craft. In fact it is
the closest thing to a Starship than anything else on the planet. Living on a submarine
one gets to understand what is needed in terms of systems and resources required to
maintain operations within a closed space for an extended period of time.
The timeframe for the Star Fleet Command Manual is sometime in the year 2277. This is
after the original television series (TOS), but before the first movie. This timeframe was
selected because I wanted to take a “snapshot” of Star Fleet at a particular point in time.
The reason being is that I wanted to create a detailed description of the Star Fleet, and
to move too much through time would have diluted this effort. As such the manual would
form a basis for future expansion in order to cover the periods of the movies and the
later television versions.
The Star Fleet Command Manual is organized into volumes. We start by laying out the
foundation for the world of the Federation and of Star Fleet. This is encapsulated in
Volume I. Volumes II, III, IV and VI go into more detail regarding the operation of Star
Fleet. Now being a techie and an engineer/physicist, I cannot resist getting into the
details of how Starships are made and how they operate. As such, Volumes V and VII go
into such details – basing much on my experience as a nuclear engineer and the effort,
requirements and specifications needed to design, build and operate nuclear power
plants and submarines.
One last point I wish to make is that I believe that the Star Fleet of the TOS era was a
military organization. As such, the structure set forth in the Star Fleet Command Manual
will be based upon this belief. Many may not agree with this assessment and they are
entitled to their opinion. But all evidence in the TOS fully suggests that it is. Perhaps the
later Star Fleet of the Next Generation series may suggest otherwise, the fact remains
that in the TOS era the Star Fleet was military. However, to those that think otherwise,
you can rest in comfort with the belief that all organizations change over time and that
the original Star Fleet may evolve into a different organization.
STARDATE 7305.29 UFP521-2G.1 OFFICIAL USE ONLY

STAR FLEET GUIDE
VOLUME II
2.0 CHAPTER NOTATIONS

CHAPTER 1
1. Because of the various branches of the Star Fleet Service, the branch that deals with
Starships will use the arrowhead for its symbol. Therefore, the division known as Star
Ship Command will use this symbol. The symbol itself comes from the Star Trek
movies and from the TV show Star Trek: the Next Generation. Note that the
arrowhead is blank.
Note that this was a sore spot with me – that each ship would have its own unique
symbol within a unified “Star Fleet.” This, to me, smacked of “privateerism” and not
something one would see in an organized fleet. In addition, the idea of having
Starships identified by a unique symbol was also implemented inconsistently
throughout the show. Just examine the personnel at the bar in the TOS episode
Court Martial. Therefore, I removed this idea from my conception of the Star Fleet
and utilized the single arrowhead symbol for all ship personnel, which was also
consistent with the later movies and TV shows.
Also note that the subdivision called Star Ship Command was also referenced in the
TOS episode Court Martial.
2. The organization called Star Base Command was originally coined in Chapter 3 of
Part II of The Making of Star Trek, Reference 8.
3. The symbol for Star Base Command was derived from the badge worn by Captain
Ronald Tracey in then TOS episode The Omega Glory. This would be one way of
distinguishing the shore establishment personnel with the operating forces
personnel.
4. For those may not have already guessed, the symbol for the Star Fleet Exploration
Command was derived from the old symbol for the Explorer Scouts.
CHAPTER 2
1. The Chief of Star Fleet Operations functions much in the same way as today’s Chief
of Naval Operations, who is the operational head of the service. The Director: Star
Fleet Command, therefore, would have the same role as today’s Secretary of the
Navy – the civilian head of the service. However, in the case of the Director, this
position would also be the military head as well as the administrative head of the
Star Fleet Service.
2. Example: Commander Hanson – commander of Outpost 4 in the TOS episode
Balance of Terror. In our terminology an Outpost “commander” will have the rank of
Commander.
3. Dr. McCoy was in Retired Reserve status when he was called back into service in the
Movie Star Trek: The Motion Picture. As stated, the Retired Reserve has the same
liability for active service as those in the Standby Reserve. As such, the Federation
Council President had to have declared an emergency before Star Fleet Operations
could recall McCoy.

STAR FLEET GUIDE
VOLUME II
CHAPTER 3
1. The Prime Sector was originally thought to have come from one of the Star Trek
movies, but no reference could be found. However, I decided to keep this term. The
term Prime Sector was originally coined in the old SiFi movie This Island Earth.
2. The intent here is to show that a fleet can be moved about from one octant to
another and still retain its designation.
3. This appears to be a reasonable requirement considering the vast distances between
worlds. In current times, it is very optimistic that any force can arrive to protect an
ally within 24 hours. In deep space, arrival time in weeks would be more appropriate
considering that going to the Earth’s moon takes about four days, and it is only
about 225,000 miles. It takes about an equal amount of time to go from the west
coast of the United States to Hawaii by ship. Therefore, think what it would take for
the Navy to respond to the Pearl Harbor attack on December 7th, 1941, assuming
there was a significant fleet moored in San Diego or San Francisco.
4. One example of a Fleet Squadron Commander from the original series would be
Commodore Robert Wesley, who commanded the squadron used during the exercise
of the M-5 unit in the TOS episode The Ultimate Computer.
5. This designation came from the enhanced TOS episode The Menagerie Part I. The
shuttlecraft that Captain Kirk and Commodore Mendez were riding in came from
Starbase 11 and had a registry number of SB11-1201/1. The standard presented
here was based upon this number sequence and format.
CHAPTER 4
1. It’s quite obvious that most of the personnel in the Star Fleet Service are humans. All
the TV and movies show this to be true. Therefore, it is reasonable to expect that
most of the people entering the service come from Earth and its colonies.
2. The eighteen year operating criteria was established in Reference 8. Specifically, it is
stated in Chapter 3 (Mission and Men) of Part II of Reference 8: "Although the
assigned mission is for a five-year period, the ship itself has a self-sustaining travel
range of eighteen years."
3. This support aspect was established early in the Star Trek universe with the very first
episode that was aired: The Man Trap. In this case, it was a requirement that Star
Fleet perform a yearly medical examination of the members. As Dr. McCoy stated:
“All research personnel on alien planets are required to have their health certified by
a Starship surgeon at one year intervals.”
4. As illustrated in the TOS episode The Devil in the Dark. Kirk was obliged to supply
the mining colony with security personnel to find the cause of the murders.
5. The planning of a patrol zone is completely up to the ship’s captain. An example of
this was given to Ben Childress of Rigel XII by Captain Kirk in the TOS episode
Mudd’s Women. In that episode Kirk cautioned Ben that his Starship is the only
protection and source of supplies he has.
6. I chose the script “f” to symbolize the monetary unit of the Federation – the
Federation Credit, which was introduced in the TOS episode The Apple and later
used in the TOS episode The Trouble with Tribbles.

STAR FLEET GUIDE
VOLUME II
CHAPTER 5
1. No one has ever really defined what a Haling Frequency was. Actually, it is a group
of standardized frequencies used to make contact. This can be surmised by Lt.
Uhura’s typical command response of “Haling Frequencies Open.”
2. An example of this could be seen in the TOS episode Mudd’s Women. As Leo Walsh,
Harry Mudd’s vessel was forcibly stopped, among other things, because he failed to
answer or yield to a Starship’s signal.
3. Communications speeds of this magnitude would be essential if the Federation wants
to efficiently manage its space. For example, Reference 2 gives a maximum speed of
Warp 20.3 (8365 x lightspeed) with subspace radio, but no mention of time dilation.
As such messages would take over a week to reach the outer rim.
4. I tried as much as possible to create the General Orders so that they would match
with how they were presented in the series. However, I modified some of them so
that they can be more "general” and not specific to a situation. The following are the
notes regarding my General orders:
a. Regarding General Order Two, it is referenced as Starfleet Order 2 in the
Animated Series episode One of Our Planets Is Missing as sited in Reference 19.
b. In the TOS episode Turnabout Intruder it was mentioned that a violation of
General Order 4 could result in the death penalty. However, I tempered that a
bit and did not make it a required penalty.
c. Regarding General Order Six, I decided to make this order more generalized
concerning the protection of the command instead of merely a self-destruction
order. The self-destruction aspect would be merely a part of an overall directive
to protect the command.
d. General Order Seven presented a challenge since it was described in the TOS
episode The Menagerie as peculiar to Talos IV. But since there were a lot more
planets that should also be quarantined, I decided to generalize General Order
Seven to encompass a wide variety of isolated worlds. In addition, it gave me
the opportunity to establish the reasoning behind the “Code 710” in the TOS
episode A Taste of Armageddon.
e. General Order Eleven was created in order to formalize one of the reasons for
the Star Fleet. This particular order was alluded to by Kirk in the TOS episode
The Galileo Seven where he stated to Commissioner Ferris that he had
“standing orders to investigate all quasar and quasar-like phenomenon.”
f. General Order Twelve came from page 116 of Reference 18.
g. General Order Fifteen came from Star Trek II: The Wrath of Kahn.
h. General Order Sixteen was used by Kirk to justify the pursuit and incarceration
of Harcourt Fenton Mudd in the TOS episode Mudd’s Women.
i. General Order Nineteen is what brought the Enterprise to planet M-113 in the
TOS episode The Man Trap.
j. The language in General Order Twenty Two was established based upon the
conversation between Captain Kirk and Spock in the TOS episode Arena.
k. General Order Twenty Six was created as a result of the incident between the
Federation and the Gorn in the TOS episode Arena.

STAR FLEET GUIDE
VOLUME II
CHAPTER 6
1. The basic functions of Star Fleet ships essentially came from Chapter 2 of Volume I.
It is natural to set the basic functions of ships to that of the Star Fleet itself, for that
is why the Starships were built.
2. As illustrated in the TOS episode Mudd’s Women. As Leo Walsh, Harry Mudd’s vessel
was forcibly stopped, Harry incarcerated and a hearing on his violations convened.
He was charged with illegally operating a space vessel; specifically, charged with
traveling through space without a flight plan and without a functioning identification
beam, failure to answer or yield to a Starship’s signal, and for operating a deep
space vessel without a Master’s license; though he could have also been charged
with transporting an illegal and dangerous substance, the Venus Drug, as well.
3. An example of a survey and mapping mission is illustrated in the beginning of the
TOS episode The Corbomite Maneuver.
4. General Order 11 was specifically created to address the standing order Kirk stated
to Commissioner Ferris that he investigate all quasar-like phenomenon in the TOS
episode The Galileo Seven. It was General Order 11 that gave Kirk the justification
for investigating Murasaki 312.
5. As stated in Chapter 3 of Reference 8, and in the title scene of the original series.
6. In Section 6.2 I wanted to provide a copy of the original orders given to any Starship
commander upon assignment to a five-year mission. Note that Kirk had the rank of
Commander before being promoted to Captain of a Starship. We will assume that
Kirk was in command of a support ship or other smaller combatant before being
assigned a cruiser class Starship, or that he was an Executive Officer of a large
Starship prior to being promoted to Captain.
7. I thought it would be cool to call ships like the Enterprise Starships of the Line.
8. All warp-driven military ships within the Star Fleet would be called Starships.
However, it is the term Capital ship that will distinguish the larger cruiser class ships
from the smaller ships.
9. The Attack Carrier was created to bring combatant shuttlecraft or similar fighter craft
to the battle. These large craft would function similar to the U.S. Navy’s aircraft
carrier. This design would allow many fighter craft to be launched simultaneously
from a top launch deck, instead of via a hanger deck as some have suggested.
10. The Frigate class of ship, as defined by the navies of the world, is generally smaller
than a destroyer class. However, from the movie Star Trek II: The Wrath of Kahn,
the Frigate Intrepid had some significant armament. Therefore, the Frigate class of
Starship will be a larger ship relative to the other classes than in the current navy
and will be classified between a cruiser and a destroyer.
11. If the Federation ever went to war and required to take and occupy ground positions
with troops, a class of Assault ship will definitely be required. However, because such
future wars would not significantly involve ground operations. It was decided that
only three such Assault vessels were required.

STAR FLEET GUIDE
VOLUME II
12. Polymass is the term used to describe the matter-antimatter fuel used by the warp
engines. The term comes from the word POLYMASP, which was printed on one of the
left-side engine control panels in the Enterprise engine room. Since in my design the
warp engines use a matter and antimatter plasma, the term POLYMASP meant the
positive plasma, whereas POLYMASN stood for the negative (antimatter) plasma.
13. The Prefix Code term came from the movie Star Trek II: The Wrath of Kahn.
However, a reason for such a code was necessary and not merely a convenient
“Hollywood” device to get Kirk out of trouble. Therefore, it was decided that the
Prefix Code is a method of remote access to the ship’s computer to allow the
programming of secret missions and ship operations like what was done in the TOS
episode The Menagerie Part 1.
14. A similar facility (Qualor II) was referenced in the TNG episode Unification, Part I.
CHAPTER 7
1. It is very reasonable to have a rotational schedule especially for those outposts out
at the Romulan Neutral Zone. Imagine having to spend a long period of time in such
a remote location and within an asteroid a mile beneath its surface? Someone like
Commander Hanson would not appreciate that very much. The three month cycle on
an Outpost would be consistent with the patrol cycle of a modern Fleet Ballistic
Missile submarine.
2. The original number of Starbases as set at 17 as stated in Chapter 3 of Part II of The
Making of Star Trek, Reference 8. However, Kirk was ordered to evacuate the
colonists on Omicron Ceti 3 to Starbase 27 in the TOS episode This Side of Paradise.
Therefore, there were more than 17 Starbases. I added one more to 27 to even out
the distribution of bases in Federation space.
3. Since the Enterprise went to Starbase 11 twice in the TOS episodes (The Menagerie
and Court-Martial), we will assume that Starbase 11 was its home port.
4. An example of such a court or courtroom can be found in the TOS episode Court
Martial. As such, a Starbase would contain several courtrooms to handle both military
and civilian justice.
5. As evidenced in the TOS episode Mudd’s Women.
6. An example of such a recreation facility is the bar in deep-space station K-7. We
assume that K-7 was once a Star Fleet station, but was negotiated away from Star
Fleet as part of the Orgainian Peace Treaty. Therefore, the bar in K-7 would have
been one of the recreational facilities that may be found in any standard Star Fleet
station.
7. This is evidenced when considering the two TOS episodes: The Menagerie and Court-
Martial. In The Menagerie the base commander was Commodore Mendez, who wore
an amber uniform indicating operations, while in Court-Martial Commodore Stone
wore a red uniform indicating engineering. Therefore, to reconcile this we have
Commodore Mendez commanding the base, while Commodore Stone commanding
the repair facility at Starbase 11 – especially considering that Commodore Stone was
setting the repair schedules for the ships located at the facility.

STAR FLEET GUIDE
VOLUME II
CHAPTER 8
1. I decided to keep the DEFCON idea since everyone would understand this
designation. It is also reasonable to assume that this designation may be carried
over into the Federation from Earth or U.S. government practices since most
everything else in Star Trek was.
2. This was a method of classifying the various “Code” alerts issued by Star Fleet to the
operating forces. In the TV series there were just too many Code 1 alerts issued for
varying reasons that did not seem to be consistent. There always appeared a new
definition for a Code 1 alert. Here we define what a Code 1 alert is.
3. This particular procedure was created based upon the directions Kirk gave Lt. Sulu
when confronted with a fleet of Klingon ships in the TOS episode Errand of Mercy.
CHAPTER 9
1. An example of a ceremonial activity would be when the Enterprise was ordered to go

to Altair VI to attend the inauguration of a new head of government in the TOS
episode Amok Time.
2. As illustrated in the TOS episode The Enterprise Incident when no one, except Kirk
and later Spock, knew of the clandestine mission of the Enterprise into Romulan
space.
3. Section 31 was introduced in the Deep Space Nine (DS9) episode Inquisition, and
although there never was a mention of it in the TOS universe, I decided to adopt the
organization.

STAR FLEET GUIDE
VOLUME II
3.0 REFERENCES
1. “Federation Reference Series #3 RS480371,” David John Nielsen, Star Fleet
Printing Office, ©1985.
2. “Line Officer Requirements,” D. Schmidt, Starfleet Training Command, ©1987.
3. “Line Officer Requirements Supplement,” D. Schmidt, Starfleet Training Command,
©1987.
4. “Star Fleet Dynamics,” Starfleet Academy Training Command Press, ©2291.
5. “Star Fleet Technical Manual TM379260,” Franz Joseph, Ballantine Books, Random
House, ©1975.
6. “Star Trek Chronology – The History of the Future,” Michael & Denise Okuda,
Pocket Books, Simon & Schuster Inc., ©1996.
7. “Star Trek Encyclopedia – A Reference Guide to the Future,” Michael & Denise
Okuda and Debbie Mirek, Pocket Books, Simon & Schuster Inc., ©1994.
8. “The Making of Star Trek,” Stephen E. Whitfield & Gene Roddenberry, Ballantine
Books, Random House, Inc., ©1968.
9. “U. S. S. Enterprise Officer’s Manual,” Geoffrey Mandel, Interstellar Associates,
©1980.
10. “The Worlds of the Federation,” Shane Johnson, Pocket Books, Simon & Schuster
Inc., ©1989.
11. “The World of Star Trek,” David Gerrold, Ballantine Books, ©1973.
12. “The Physics of Star Trek,” Lawrence M. Krauss, BasicBooks, ©1995.
13. “Star Fleet Uniform Recognition Manual,” Shane Johnson and Kathy Johnson,
NORON Group, ©1985.
14. “Starfleet Academy Training Manual 000:00,” 2ND Edition, John Wetsch.
15. “From the Files of Star Fleet Command,” Adm. Heihachiro Nogura, Star Fleet
Historical Archives, ©1980.
16. “U.S.S. Enterprise Officer’s Manual OM 1701-CEC,” Geoffrey Mandel and Doug
Drexler, Interstellar Associates, ©1980.
17. “The Star Trek Guide,” Third Revision, Paramount Studios, April 17, 1967.
18. “Star Trek The Role Playing Game,” FASA Corporation, © 1983.
19. “Star Trek Concordance,” Bjo Trimble, Ballantine Books, © 1976 Paramount
Studios and Bjo Trimble.

Star Fleet Command Manual - Volume II

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Star Fleet Command Manual - Volume II

Uploaded by

Copyright:

Available Formats

STAR FLEET COMMAND

STARDATE 25201.18 UFP521-2a.i OFFICIAL USE ONLY

This Page Left Intentionally Blank

STARDATE 25201.18 UFP521-2a.ii OFFICIAL USE ONLY

Sections 5.4 and Added General Order 6; updated Table 2a54.1.

STARDATE 25201.18 UFP521-2a.iii OFFICIAL USE ONLY

This Page Left Intentionally Blank

STARDATE 25201.18 UFP521-2a.iv OFFICIAL USE ONLY

Heihachiro Nogura, Admiral, SFC

STARDATE 25201.18 UFP521-2a.v OFFICIAL USE ONLY

STAR FLEET COMMAND MANUALS

VOLUME I STAR FLEET COMMAND

VOLUME V STAR FLEET SHIPS

VOLUME VI STAR BASE COMMAND

VOLUME VII STAR FLEET BASES

VOLUME VIII STAR FLEET JUSTICE

STARDATE 25201.18 UFP521-2a.vi OFFICIAL USE ONLY

VOLUME II TABLE OF CONTENTS

1.0 Star Fleet Division of Operations 2a10

STARDATE 25201.18 UFP521-2a.vii OFFICIAL USE ONLY

VOLUME II TABLE OF CONTENTS - CONTINUED

5.0 Fleet Command Operations 2a50

STARDATE 25201.18 UFP521-2a.viii OFFICIAL USE ONLY

Throughout the manual the following typographic standards will be used:

STARDATE 25201.18 UFP521-2a.ix OFFICIAL USE ONLY

This Page Left Intentionally Blank

STARDATE 25201.18 UFP521-2a.x OFFICIAL USE ONLY

1.0 STAR FLEET DIVISION OF OPERATIONS

STAR FLEET OPERATIONS DIVISION

STARDATE 7305.29 UFP521-2a10.1 OFFICIAL USE ONLY

STARDATE 7305.29 UFP521-2a10.2 OFFICIAL USE ONLY

STARDATE 7305.29 UFP521-2a10.3 OFFICIAL USE ONLY

STAR FLEET OPERATIONS SYMBOL

• The Star Fleet Adjunct Forces Command

STARDATE 7305.29 UFP521-2a10.4 OFFICIAL USE ONLY

Metal pin worn only on the Formal Dress Blue uniform of

Metal pin worn only on the Formal Dress Blue uniform of

STARDATE 7305.29 UFP521-2a10.5 OFFICIAL USE ONLY

Division Number Division or Office

2000 Star Fleet

STARDATE 7305.29 UFP521-2a10.6 OFFICIAL USE ONLY

2000 Star Fleet

2100 2200 2300 Star Fleet 2400

STARDATE 7305.29 UFP521-2a10.7 OFFICIAL USE ONLY

This Page Left Intentionally Blank

STARDATE 7305.29 UFP521-2a10.8 OFFICIAL USE ONLY

1.1 STAR SHIP COMMAND

STARDATE 7305.29 UFP521-2a11.1 OFFICIAL USE ONLY

STAR SHIP COMMAND SYMBOL[1]

 Office of Star Fleet Ship Personnel

Each of these subdivisions will be described in the subsequent sections below.

STARDATE 7305.29 UFP521-2a11.2 OFFICIAL USE ONLY

OFFICE OF STAR FLEET SHIP PERSONNEL

STARDATE 7305.29 UFP521-2a11.3 OFFICIAL USE ONLY

OFFICE OF STAR FLEET SHIP OPERATIONS

STARDATE 7305.29 UFP521-2a11.4 OFFICIAL USE ONLY

OFFICE OF STAR FLEET SHIP MATERIEL

STARDATE 7305.29 UFP521-2a11.5 OFFICIAL USE ONLY

OFFICE OF STAR FLEET SHIP PLANNING

STARDATE 7305.29 UFP521-2a11.6 OFFICIAL USE ONLY

OFFICE OF STAR FLEET SHIP SERVICES

STARDATE 7305.29 UFP521-2a11.7 OFFICIAL USE ONLY

STAR FLEET SERVICE CRAFT COMMAND

STARDATE 7305.29 UFP521-2a11.8 OFFICIAL USE ONLY