RP Tools: Command Division
by Kheren » Sun Jan 13, 2013 12:25 pm
Here will be found tools useful for all officers of the fleet, but especially those in command position, not only Captains and XOs but department heads who may have to provide specific data and recommendations on sensitive topics... or sometimes remind their superiors of a few rules and regs!
Fleet XO - RP Director - Former Fleet Admiral, Operations CO, JAG and Ambassador - Former Captain of the USS Artemis and of the flagship USS Horizon - Current Captain of the USS Millennium
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
-
Kheren - Admiral
- Posts: 930
- Joined: Mon Aug 06, 2012 9:40 pm
- Location: Trois-Rivieres, Quebec, Canada
- Has thanked: 444 times
- Been thanked: 396 times
- Medals: 43
-
-
-
-
-
-
-
-
Starfleet General Orders
by Kheren » Sun Jan 13, 2013 1:25 pm
Kheren 02-14-2011 01:41 PM RP TOOLS: Starfleet General Orders
Starfleet General Orders
All species of the United Federation of Planets pledge to work together and in harmony towards common goals. By joining Starfleet, all personnel swear to follow and honor to the best of one's ability the Articles of the Federation.
These Articles are the foundation of the Federation.Following those ideals requires more than simple devotion to duty; it demands a number of guiding principles to wich Starfleet personnel can refer to
To this end, Starfleet promulgated a set of Directives, rules and regulations all crewmembers and officers must follow in the course of their duties.
STARFLEET DIRECTIVES
Starfleet General Orders detail the conduct all Starfleet personnel must follow in the course of their duties. The following are the most important rules of Starfleet and supercede all other rules and regulations and orders in the field.
Failure to obey a General Order draws forth a Court Martial on the offender, although Starfleet considers all attenuating circumstances before rendering judgment.
No Starfleet officer, regardless of rank, can order a crewmember to violate a General Order. Such order is illegal and following such illegal order is not admissible as a valid defense.
The Judge Advocate General Office investigates all General Orders violations and prosecute any and all committing blatant faults within Starfleet's doctrine.
Since their initial promulgation, number and nature of those General Orders changed. When appropriate reasons are given, Starfleet review all Directives, update them and in some cases even remove them.
For the first 57 years, Starfleet adopted General Orders as temporary directives, without any particular importance wether it was listed first or last. They were in fact all viewed on equal terms, except for the Prime Directive.
Sometimes during the course of Starfleet missions, some General Orders conflict. Interpretation and application of those orders rely on the Federation command officer's judgment; this is one of the heaviest responsibility givent to a Starfleet Commander, as often, there is no clear-cut answer. A starship captain facing a ship in distress in the Neutral Zone - conflict between Order 6 and 11 - must show good judgment in order to know wich one must be given priority.
It becomes clear that study and understanding of these General orders and their implications are of paramount importance to all Starfleet Officers, in direct proportion to the rank and responsibilities given.
STARFLEET GENERAL ORDERS
General Order 1: The Prime Directive
As the right of each sentient species to live in accordance with its normal cultural evolution is considered sacred, no Starfleet personnel may interfere with the normal and healthy development of alien life and culture. Such interference includes introducing superior knowledge, strength, or technology to a world whose society is incapable of handling such advantages wisely. Starfleet personnel may not violate this Prime Directive, even to save their lives and/or their ship, unless they are acting to right an earlier violation or an accidental contamination of said culture. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation.
Addendum to General Order One: The Temporal Prime Directive (General Order 1A)
The dispositions of the Prime Directive shall henceforth apply on the entire spectrum of space-time. No Starfleet personnel may interfere with the timeline or with people and events in a way that would alter these from the already established facts in linear time. This includes knowledge and objects or entities from the future who's presence or use could alter the unfolding events of current time and change that future. Starfleet personnel may not violate this Temporal Prime Directive, even to save their lives and/or their ship, unless they are acting to right an earlier violation or contamination of said timeline. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation.
General Order 2
No Starfleet personnel shall unnecessarily use force, either collectively or individually, against members of the United Federation of Planets, their duly authorized representatives, spokespersons, or designated leaders, or members of any sentient non-member race, for any reason whatsoever.
General Order 3
The sovereignty of each Federation member being respected in all things, Starfleet personnel shall observe any and all statutes, laws, ordinances, and rules of governance currently in effect within the jurisdiction of a member planet. Violators of such ordinances will be subject to such punishments or local governmental bodies shall determine corrections as.
General Order 4
If contact is made with hitherto undiscovered intelligent life-forms, under no circumstance shall Starfleet personnel, either by word or deed, inform said life-forms that worlds other than their own or intelligent life-forms other than their own exist outside the confines of their own space.
General Order 5
In cases of extreme emergency, Federation special representatives are empowered to assume emergency powers to deal with a condition or circumstance that is deemed hazardous to the welfare of Federation citizenry. Within the scope of these emergency powers, duly authorized civilian personnel may assume temporary command of Starfleet vessels and/or personnel to deal with the emergency. Starfleet personnel must submit to their authority for the duration of the crisis.
General Order 6
The request for emergency assistance from Federation citizenry demands unconditional priority from Starfleet personnel. Such personnel shall immediately respond to say request, postponing all other activities.
General Order 7
No Starfleet vessel shall visit the planet Talos IV under any circumstances, emergency or otherwise. This order supersedes General Order 6. Any transgression of this general order shall be punishable by death.
General Order 8
Upon sighting a warship within Federation space and identifying it as belonging to a foreign power, the commander of the Starfleet vessel shall determine the reason(s) for that craft's presence in the vicinity. If there is conclusive evidence that the vessel has hostile intentions, the Federation vessel may take appropriate action to safeguard the lives and property of Federation members. In such cases, the commander may use his discretion in deciding whether to use force to disable the hostile vessel. However, care should be taken to avoid unnecessary loss of sentient life.
General Order 9
No commander of a Starfleet vessel, military or auxiliary, may grant political asylum to any individual without first being given express permission to do so by a representative of the Federation government.
General Order 10
If there exists eyewitness testimony by senior officers or similar verifiable evidence that an individual has violated the Prime Directive, said individual may be relieved of duty by a duly sworn representative of the Federation government and placed under immediate arrest. The governmental representative shall then take such action, as he deems necessary to minimize the results of the violation.
General Order 11
Starfleet officers with the rank of captain or higher are granted full authority to negotiate conditions of agreement and/or treaties with legal representatives of non-Federation planets. In such circumstances, the acting officer carries de facto powers of a Federation Special Ambassador. Any and all agreements arranged in this manner are subject to approval by the Chief of Starfleet Operations and the Secretary of Starfleet.
General Order 12
When approaching a vessel with which communication has not been established, all Starfleet vessels are to maintain maximum safety precautions, regardless of the origin of said vessel, be it a foreign power, an hitherto unknown ship, or a Starfleet vessel.
General Order 13
Except when orders state to the contrary, Starfleet personnel will respect the territorial integrity of independent planetary systems and governments, and will not violate territorial space belonging to such worlds.
General Order 14
Starfleet personnel may intervene in local planetary affairs to restore general order and to secure the lives and property of Federation citizens only upon receiving a direct order to do so from a civilian official with the title of governor or higher.
General Order 15
No officer of flag rank shall travel into a potentially hazardous area without suitable armed escort.
General Order 16
Starfleet personnel may extend technological, medical, or other scientific assistance to a member of a previously unrecognized sentient species only if such assistance in no way compromises the Prime Directive or the security of the Federation or Starfleet.
General Order 17
Starfleet vessel captains are to consider the lives of their crew members as sacred. In any potentially hostile situation, the captain will place the lives of his crew above the fate of his ship.
General Order 18
"Upon being accused of treason against the Federation, Starfleet personnel may demand a trial conducted by the Federation judiciary". If the individual is acquitted, Starfleet Command shall have no further legal recourse against the accused in said matter.
General Order 19
Except in times of declared emergency, Starfleet personnel may under no circumstances convey personnel or material between planets or planetary systems when there is reason to believe that said personnel or material might be used to conduct aggression. This order applies to independent worlds within the Federation as well as to Federation members.
General Order 20
Officers and personnel of Starfleet Command may employ whatever means necessary to prevent the possession, transportation, sale, or commercial exchange of sentient beings held against their wishes within the boundaries of Federation space.
General Order 21
No Starfleet personnel, either officer or enlisted, may offer his services to an independent foreign government without the express authorization of the Federation Assembly.
General Order 22
As the rights of individual expression and free discourse are considered sacred, Starfleet personnel may debate the policies and decisions of their governmental representatives privately at any time, to the extent that such discussions do not violate their command oath or specific duties to the Federation per these General Orders or Starfleet regulations.
General Order 23
When verifiable proof is presented to the senior commanding officer of a Starfleet vessel or post that a Federation representative may currently be acting or have acted in the past to violate the Prime Directive, the officer may relieve said representative of office, then assume the full powers of that office pending a full investigation by governmental officials.
General Order 24
If a commanding officer deems that an individual or group of individuals pose a threat to Starfleet personnel or Federation civilians, he may take any action deemed necessary (including force) to secure the safety of those threatened.
General Order 25
Civilian and military personnel taken into custody by Starfleet personnel during times of extreme emergency shall be accorded proper treatment consistent with their rank or station, insofar as such treatment does not compromise the security of the Federation or Starfleet.
General Order 26
No member of a ship's complement or other ground-based installation can be held directly accountable for the actions of their superiors. Similarly, no member of a ship's company or other Starfleet personnel will share in disciplinary measures taken against the commanding officer(s) if said individuals were not directly involved in the actions leading to disciplinary measures. This order extends to conditions involving proven violations of the Prime Directive, where proof of such violations exist.
General Order 27
No member of Starfleet shall be required by the assignment of standard duties and responsibilities to undergo extended separation from his family, if family members can be reasonably provided for aboard ship or as a part of an existing Starfleet installation.
General Order 28
No officer of command rank shall be removed from command status unless such action has the complete and unqualified agreement of at least three senior officers present. Whenever possible, such officers shall include the ship's First Officer, Chief Medical Officer, Counselor, and one junior officer of command station.
General Order 29
The primary responsibility of the commander of any Starfleet vessel or installation is the welfare and safety of his crew, including any civilian members. No action may be taken that creates an unwarranted threat to the safety of those individuals under the officer's charge, except in the line of duty and when otherwise unavoidable.
General Order 30
Starfleet Command recognizes the right of each ship commander to interpret the specifications of the Prime Directive as he sees fit, consistent with the conditions of other existing general orders in effect, and based upon circumstances that may arise in dealing with newly discovered sentient races.
General Order 31
The conditions and specifications of the Prime Directive shall henceforth apply to all sentient life forms discovered, whether they are of natural or artificial origin.
General Order 32
Federation officers may violate Neutral Zone areas as designated by treaty only if such action is required to save the lives of Federation citizens under conditions of extreme emergency as required by General Order 6.
General Order 33
If a commanding officer deems that an individual or group of individuals pose a direct threat to the safety of Starfleet personnel, Federation citizens, or those under current Federation protection, they may take any actions necessary to safeguard the lives of those threatened. In such cases, the commander may use their discretion in deciding whether to use force. However, care should be taken to avoid unnecessary loss of sentient life.
General Order 34
All Starfleet personnel and/or Federation civilian contractors shall follow a superior's order to the best of their ability, unless said orders should conflict with the regulation laid out in these orders. Special dispensations are granted in emergency situations as per specific orders, with the exceptions of General Orders 1, 2, 3, or 7.
General Order 35
Should the entire personnel of a Starfleet vessel or installation become severely incapacitated or deceased due to an environmental or medical contaminant, said vessel is to be destroyed within a 24-hour period from initial discovery of cause to prevent spread of the epidemic agent.
General Order 36
No Federation vessel, whether civilian or Starfleet, is allowed to visit a planet or star system placed under quarantine by Starfleet or the Federation Council unless the visitation falls under the jurisdictional actions accredited by General Orders 1, 5, and 6.
General Order 37
Starfleet personnel shall respect binding contracts, agreements, and bondings made by the Federation government and/or Starfleet itself and shall operate within the boundaries & governances of said treaties, especially in matters dealing with the co-signatories of said treatise.
General Order 38
In the event of the death, absence, or incapacitation of the commanding officer of record, command of a ship or installation falls to the next highest-ranking crew member, regardless of position in the command structure. When two officers in the line of succession are of comparable rank, command first falls upon the officer with command experience; barring that requirement, command will fall upon the officer with seniority.
General Order 39
An officer or crewmember may be removed from active duty status if they are judged to be incapable of fulfilling their obligations as a member of Starfleet, whether for medical or psychological reasons, by either the Chief Medical Officer or by the two ranking command staff officers.
General Order 40
Except in the case of an extreme emergency, no Starfleet commander is authorized to order his ship to travel faster than Warp Factor Five without express permission from Starfleet Command. Ship classes officially designed and registered as proven to be able to use warp travel without damaging subspace are exempt from this directive.
THE FOLLOWING IS FOR CAPTAIN RANK AND ABOVE EYES AND KNOWLEDGE ONLY
VIOLATION OF THIS RESTRICTION IS PUNISHABLE BY LIFETIME IMPRISONNEMENT
ON A FEDERATION PENAL COLONY WITH NO POSSIBILITY OF APPEAL, REPRIEVE OR PAROLE.
STARFLEET WILL DENY ANY EXISTENCE OF THE FOLLOWING DIRECTIVE
General Order 00 : The Omega Directive
This directive supercedes and nullifies all other directives including the Prime Directive.
All Starfleet personnel and vessels, under any and all circumstances, must ensure the destruction of any Omega molecule detected, taking all the necessary precautions to ensure the safe disposal of the said substance and thus the safety of the sector where it is encountered. The use of the Omega molecule, either in research or in application, is strictly forbidden without the express permission and direct supervision of the Federation Science Council. Failure to comply with this directive will call an immediate court martial and, above and beyond the sentence of the Court, permanent demotion and expulsion from Starfleet for both the commanding officer and crew of the guilty starship or facility. The guilty party will also be liable to legal prosecution by the Federation’s Judiciary. Any non-aligned entity possessing or using the Omega molecule is hereby declared a criminal under Interstellar Law and treated accordingly by all Starfleet personnel.
Official procedure is as follow:
1- contact Starfleet Command under closed, encoded channel code Omega
2- erase any and all computer log relating to Omega event
3- return to previous assignment. Omega team will then take charge of the situation.
Written by Franz Joseph in the Starfleet Technical Manual
updated and expanded by Chris Gray, modified by Chris St. John
General Order 00 and 1A written by Andre Ouellette
Starfleet General Orders
All species of the United Federation of Planets pledge to work together and in harmony towards common goals. By joining Starfleet, all personnel swear to follow and honor to the best of one's ability the Articles of the Federation.
These Articles are the foundation of the Federation.Following those ideals requires more than simple devotion to duty; it demands a number of guiding principles to wich Starfleet personnel can refer to
To this end, Starfleet promulgated a set of Directives, rules and regulations all crewmembers and officers must follow in the course of their duties.
STARFLEET DIRECTIVES
Starfleet General Orders detail the conduct all Starfleet personnel must follow in the course of their duties. The following are the most important rules of Starfleet and supercede all other rules and regulations and orders in the field.
Failure to obey a General Order draws forth a Court Martial on the offender, although Starfleet considers all attenuating circumstances before rendering judgment.
No Starfleet officer, regardless of rank, can order a crewmember to violate a General Order. Such order is illegal and following such illegal order is not admissible as a valid defense.
The Judge Advocate General Office investigates all General Orders violations and prosecute any and all committing blatant faults within Starfleet's doctrine.
Since their initial promulgation, number and nature of those General Orders changed. When appropriate reasons are given, Starfleet review all Directives, update them and in some cases even remove them.
For the first 57 years, Starfleet adopted General Orders as temporary directives, without any particular importance wether it was listed first or last. They were in fact all viewed on equal terms, except for the Prime Directive.
Sometimes during the course of Starfleet missions, some General Orders conflict. Interpretation and application of those orders rely on the Federation command officer's judgment; this is one of the heaviest responsibility givent to a Starfleet Commander, as often, there is no clear-cut answer. A starship captain facing a ship in distress in the Neutral Zone - conflict between Order 6 and 11 - must show good judgment in order to know wich one must be given priority.
It becomes clear that study and understanding of these General orders and their implications are of paramount importance to all Starfleet Officers, in direct proportion to the rank and responsibilities given.
STARFLEET GENERAL ORDERS
General Order 1: The Prime Directive
As the right of each sentient species to live in accordance with its normal cultural evolution is considered sacred, no Starfleet personnel may interfere with the normal and healthy development of alien life and culture. Such interference includes introducing superior knowledge, strength, or technology to a world whose society is incapable of handling such advantages wisely. Starfleet personnel may not violate this Prime Directive, even to save their lives and/or their ship, unless they are acting to right an earlier violation or an accidental contamination of said culture. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation.
Addendum to General Order One: The Temporal Prime Directive (General Order 1A)
The dispositions of the Prime Directive shall henceforth apply on the entire spectrum of space-time. No Starfleet personnel may interfere with the timeline or with people and events in a way that would alter these from the already established facts in linear time. This includes knowledge and objects or entities from the future who's presence or use could alter the unfolding events of current time and change that future. Starfleet personnel may not violate this Temporal Prime Directive, even to save their lives and/or their ship, unless they are acting to right an earlier violation or contamination of said timeline. This directive takes precedence over any and all other considerations, and carries with it the highest moral obligation.
General Order 2
No Starfleet personnel shall unnecessarily use force, either collectively or individually, against members of the United Federation of Planets, their duly authorized representatives, spokespersons, or designated leaders, or members of any sentient non-member race, for any reason whatsoever.
General Order 3
The sovereignty of each Federation member being respected in all things, Starfleet personnel shall observe any and all statutes, laws, ordinances, and rules of governance currently in effect within the jurisdiction of a member planet. Violators of such ordinances will be subject to such punishments or local governmental bodies shall determine corrections as.
General Order 4
If contact is made with hitherto undiscovered intelligent life-forms, under no circumstance shall Starfleet personnel, either by word or deed, inform said life-forms that worlds other than their own or intelligent life-forms other than their own exist outside the confines of their own space.
General Order 5
In cases of extreme emergency, Federation special representatives are empowered to assume emergency powers to deal with a condition or circumstance that is deemed hazardous to the welfare of Federation citizenry. Within the scope of these emergency powers, duly authorized civilian personnel may assume temporary command of Starfleet vessels and/or personnel to deal with the emergency. Starfleet personnel must submit to their authority for the duration of the crisis.
General Order 6
The request for emergency assistance from Federation citizenry demands unconditional priority from Starfleet personnel. Such personnel shall immediately respond to say request, postponing all other activities.
General Order 7
No Starfleet vessel shall visit the planet Talos IV under any circumstances, emergency or otherwise. This order supersedes General Order 6. Any transgression of this general order shall be punishable by death.
General Order 8
Upon sighting a warship within Federation space and identifying it as belonging to a foreign power, the commander of the Starfleet vessel shall determine the reason(s) for that craft's presence in the vicinity. If there is conclusive evidence that the vessel has hostile intentions, the Federation vessel may take appropriate action to safeguard the lives and property of Federation members. In such cases, the commander may use his discretion in deciding whether to use force to disable the hostile vessel. However, care should be taken to avoid unnecessary loss of sentient life.
General Order 9
No commander of a Starfleet vessel, military or auxiliary, may grant political asylum to any individual without first being given express permission to do so by a representative of the Federation government.
General Order 10
If there exists eyewitness testimony by senior officers or similar verifiable evidence that an individual has violated the Prime Directive, said individual may be relieved of duty by a duly sworn representative of the Federation government and placed under immediate arrest. The governmental representative shall then take such action, as he deems necessary to minimize the results of the violation.
General Order 11
Starfleet officers with the rank of captain or higher are granted full authority to negotiate conditions of agreement and/or treaties with legal representatives of non-Federation planets. In such circumstances, the acting officer carries de facto powers of a Federation Special Ambassador. Any and all agreements arranged in this manner are subject to approval by the Chief of Starfleet Operations and the Secretary of Starfleet.
General Order 12
When approaching a vessel with which communication has not been established, all Starfleet vessels are to maintain maximum safety precautions, regardless of the origin of said vessel, be it a foreign power, an hitherto unknown ship, or a Starfleet vessel.
General Order 13
Except when orders state to the contrary, Starfleet personnel will respect the territorial integrity of independent planetary systems and governments, and will not violate territorial space belonging to such worlds.
General Order 14
Starfleet personnel may intervene in local planetary affairs to restore general order and to secure the lives and property of Federation citizens only upon receiving a direct order to do so from a civilian official with the title of governor or higher.
General Order 15
No officer of flag rank shall travel into a potentially hazardous area without suitable armed escort.
General Order 16
Starfleet personnel may extend technological, medical, or other scientific assistance to a member of a previously unrecognized sentient species only if such assistance in no way compromises the Prime Directive or the security of the Federation or Starfleet.
General Order 17
Starfleet vessel captains are to consider the lives of their crew members as sacred. In any potentially hostile situation, the captain will place the lives of his crew above the fate of his ship.
General Order 18
"Upon being accused of treason against the Federation, Starfleet personnel may demand a trial conducted by the Federation judiciary". If the individual is acquitted, Starfleet Command shall have no further legal recourse against the accused in said matter.
General Order 19
Except in times of declared emergency, Starfleet personnel may under no circumstances convey personnel or material between planets or planetary systems when there is reason to believe that said personnel or material might be used to conduct aggression. This order applies to independent worlds within the Federation as well as to Federation members.
General Order 20
Officers and personnel of Starfleet Command may employ whatever means necessary to prevent the possession, transportation, sale, or commercial exchange of sentient beings held against their wishes within the boundaries of Federation space.
General Order 21
No Starfleet personnel, either officer or enlisted, may offer his services to an independent foreign government without the express authorization of the Federation Assembly.
General Order 22
As the rights of individual expression and free discourse are considered sacred, Starfleet personnel may debate the policies and decisions of their governmental representatives privately at any time, to the extent that such discussions do not violate their command oath or specific duties to the Federation per these General Orders or Starfleet regulations.
General Order 23
When verifiable proof is presented to the senior commanding officer of a Starfleet vessel or post that a Federation representative may currently be acting or have acted in the past to violate the Prime Directive, the officer may relieve said representative of office, then assume the full powers of that office pending a full investigation by governmental officials.
General Order 24
If a commanding officer deems that an individual or group of individuals pose a threat to Starfleet personnel or Federation civilians, he may take any action deemed necessary (including force) to secure the safety of those threatened.
General Order 25
Civilian and military personnel taken into custody by Starfleet personnel during times of extreme emergency shall be accorded proper treatment consistent with their rank or station, insofar as such treatment does not compromise the security of the Federation or Starfleet.
General Order 26
No member of a ship's complement or other ground-based installation can be held directly accountable for the actions of their superiors. Similarly, no member of a ship's company or other Starfleet personnel will share in disciplinary measures taken against the commanding officer(s) if said individuals were not directly involved in the actions leading to disciplinary measures. This order extends to conditions involving proven violations of the Prime Directive, where proof of such violations exist.
General Order 27
No member of Starfleet shall be required by the assignment of standard duties and responsibilities to undergo extended separation from his family, if family members can be reasonably provided for aboard ship or as a part of an existing Starfleet installation.
General Order 28
No officer of command rank shall be removed from command status unless such action has the complete and unqualified agreement of at least three senior officers present. Whenever possible, such officers shall include the ship's First Officer, Chief Medical Officer, Counselor, and one junior officer of command station.
General Order 29
The primary responsibility of the commander of any Starfleet vessel or installation is the welfare and safety of his crew, including any civilian members. No action may be taken that creates an unwarranted threat to the safety of those individuals under the officer's charge, except in the line of duty and when otherwise unavoidable.
General Order 30
Starfleet Command recognizes the right of each ship commander to interpret the specifications of the Prime Directive as he sees fit, consistent with the conditions of other existing general orders in effect, and based upon circumstances that may arise in dealing with newly discovered sentient races.
General Order 31
The conditions and specifications of the Prime Directive shall henceforth apply to all sentient life forms discovered, whether they are of natural or artificial origin.
General Order 32
Federation officers may violate Neutral Zone areas as designated by treaty only if such action is required to save the lives of Federation citizens under conditions of extreme emergency as required by General Order 6.
General Order 33
If a commanding officer deems that an individual or group of individuals pose a direct threat to the safety of Starfleet personnel, Federation citizens, or those under current Federation protection, they may take any actions necessary to safeguard the lives of those threatened. In such cases, the commander may use their discretion in deciding whether to use force. However, care should be taken to avoid unnecessary loss of sentient life.
General Order 34
All Starfleet personnel and/or Federation civilian contractors shall follow a superior's order to the best of their ability, unless said orders should conflict with the regulation laid out in these orders. Special dispensations are granted in emergency situations as per specific orders, with the exceptions of General Orders 1, 2, 3, or 7.
General Order 35
Should the entire personnel of a Starfleet vessel or installation become severely incapacitated or deceased due to an environmental or medical contaminant, said vessel is to be destroyed within a 24-hour period from initial discovery of cause to prevent spread of the epidemic agent.
General Order 36
No Federation vessel, whether civilian or Starfleet, is allowed to visit a planet or star system placed under quarantine by Starfleet or the Federation Council unless the visitation falls under the jurisdictional actions accredited by General Orders 1, 5, and 6.
General Order 37
Starfleet personnel shall respect binding contracts, agreements, and bondings made by the Federation government and/or Starfleet itself and shall operate within the boundaries & governances of said treaties, especially in matters dealing with the co-signatories of said treatise.
General Order 38
In the event of the death, absence, or incapacitation of the commanding officer of record, command of a ship or installation falls to the next highest-ranking crew member, regardless of position in the command structure. When two officers in the line of succession are of comparable rank, command first falls upon the officer with command experience; barring that requirement, command will fall upon the officer with seniority.
General Order 39
An officer or crewmember may be removed from active duty status if they are judged to be incapable of fulfilling their obligations as a member of Starfleet, whether for medical or psychological reasons, by either the Chief Medical Officer or by the two ranking command staff officers.
General Order 40
Except in the case of an extreme emergency, no Starfleet commander is authorized to order his ship to travel faster than Warp Factor Five without express permission from Starfleet Command. Ship classes officially designed and registered as proven to be able to use warp travel without damaging subspace are exempt from this directive.
THE FOLLOWING IS FOR CAPTAIN RANK AND ABOVE EYES AND KNOWLEDGE ONLY
VIOLATION OF THIS RESTRICTION IS PUNISHABLE BY LIFETIME IMPRISONNEMENT
ON A FEDERATION PENAL COLONY WITH NO POSSIBILITY OF APPEAL, REPRIEVE OR PAROLE.
STARFLEET WILL DENY ANY EXISTENCE OF THE FOLLOWING DIRECTIVE
General Order 00 : The Omega Directive
This directive supercedes and nullifies all other directives including the Prime Directive.
All Starfleet personnel and vessels, under any and all circumstances, must ensure the destruction of any Omega molecule detected, taking all the necessary precautions to ensure the safe disposal of the said substance and thus the safety of the sector where it is encountered. The use of the Omega molecule, either in research or in application, is strictly forbidden without the express permission and direct supervision of the Federation Science Council. Failure to comply with this directive will call an immediate court martial and, above and beyond the sentence of the Court, permanent demotion and expulsion from Starfleet for both the commanding officer and crew of the guilty starship or facility. The guilty party will also be liable to legal prosecution by the Federation’s Judiciary. Any non-aligned entity possessing or using the Omega molecule is hereby declared a criminal under Interstellar Law and treated accordingly by all Starfleet personnel.
Official procedure is as follow:
1- contact Starfleet Command under closed, encoded channel code Omega
2- erase any and all computer log relating to Omega event
3- return to previous assignment. Omega team will then take charge of the situation.
Written by Franz Joseph in the Starfleet Technical Manual
updated and expanded by Chris Gray, modified by Chris St. John
General Order 00 and 1A written by Andre Ouellette
Fleet XO - RP Director - Former Fleet Admiral, Operations CO, JAG and Ambassador - Former Captain of the USS Artemis and of the flagship USS Horizon - Current Captain of the USS Millennium
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
-
Kheren - Admiral
- Posts: 930
- Joined: Mon Aug 06, 2012 9:40 pm
- Location: Trois-Rivieres, Quebec, Canada
- Has thanked: 444 times
- Been thanked: 396 times
- Medals: 43
-
-
-
-
-
-
-
-
Starfleet Rules of Engagement
by Kheren » Sun Jan 13, 2013 1:42 pm
Kheren 01-25-2011 12:29 AM RP TOOLS: Starfleet Rules of Engagement
These are the established Starfleet rules for deep space missions. All officers are advised to familiarize themselves thoroughly with those rules. as they will dictate how well their performance will be evaluated by their commanding officer, Lotus Fleet Command and Starfleet.
STARFLEET RULES OF ENGAGEMENT
Written by : Captain Garth of Izar
Revised by : Commodore Christopher Pike
Anotated by : Captain James T Kirk
AT FIRST SENSOR CONTACT:
The most dangerous time for two ships meeting in space is at the moment of first sensor contact when the other ship has yet to be identified. This is when the ship commander is at greatest risk of making an error in judgment… an error that could cost you your ship or open fire on a non-hostile vessel..
During this time, you must gather as much information as possible. Keep an eye open for any sign about the other ship’s intentions. Even before proper identification of the other vessel, you might be able to gather sufficient information to safeguard your ship and crew without committing yourself to a wrong course of action.
Observe first both the trajectory and speed of the other ship. An interception course is to be interpreted as a serious warning! Because of the vastness of space, such occurrences are not happening by chance - probabilties against such a random, accidental occurrence are enormous. If your trajectories intersect or just become closer, it is clear the other is looking for you. On the other hand, if the other ship is only within your sensor radius, you can not automatically assume that the other ship detected you and that his actions are related to any direct intention concerning your own ship.
( Nor the opposite - Kirk )
A sensor contact below light speed may not even be that of another ship; however, no natural phenomenon can move at the speed of light. Any speed of warp one or over, any faster than light movement, shows the definite presence of an artificial object of sentient origin
( The ‘’Lights of Zetar’’ and the ‘’Vampire Cloud’’ are two lifeforms known to move beyond the light barrier without the need of any technology. Although both are deemed destroyed, they suggest the remote but factual possibility of natural forces achieving faster than light travel. Some subatomic particles can also achieve this, a well known fact during Capt Garth’s time, so we must assume that his remark meant that no natural phenomenon can deliberately break the light barrier with a predetermined, voluntary trajectory; a statement that was true at his time, before said lifeforms were discovered to challenge this assumption. - Kirk )
A parallel trajectory, especially if it also parallels your own speed, is equally significant. Such a ship does not want immediately to approach you, mainly to observe you. It is also possible that the commander of this ship has underestimated your sensor range and beleives that you are unaware of his presence. He might also want to make himself known to you without looking for direct contact.
Observe the other ship’s trajectory and it’s speed. This will give you how much time you have to gather information before identifying it… or before it opens fire! Use this available time to learn as much as possible, even if it is only for a few seconds. At the end of this time, you will have to rapidly make your decision based on those informations. Do not act out of ignorance.
UPON IDENTIFICATION
A ship close enough to be identified will fall under one of four possible categories. Starfleet rules and regulations provide adequate procedures for each type of encounter, but they are sufficiently generalized to allow a ship commander all the necessary freedom of decision in the field. There is however one underlying philosophy behind all of these procedures*: the desire to preserve Peace.
When a conflict can be avoided without endangering the safety of the Federation, a Starfleet commander is bound by duty to apply such an option. Above all rules and laws remains one simple principle*: we have to share this galaxy with all of it’s inhabitants. The rights and privileges of all lifeforms must be acknowledged without reserve, even when considering a ship from a declared enemy of the Federation. It is up to a ship commander to judge if said vessel is exercising his rights and privileges or is committing and act of agression. The line between the two may appear very thin.
Federation policy forbids a Starfleet vessel from opening fire against any and all other vessels unless said vessel ‘’ by it’s presence or actions represents a clear and immediate danger for Federation security, the free and safe passage of it’s citizens, or otherwise does not comform itself to the legal proceedings allowed for a ship of it’s registration.’’
Regulations stipulate that any ship ‘’ with an attitude directly and openly threatening to the safety of a Starfleet vessel’’ may be targeted, but only if ‘’ according to the sound judgment of the commander, no other reasonable course of action can be adopted to avoid an armed conflict without further endangering the Federation, it’s citizens or the ship itself.’’
Despite those clear statements, the decision is mostly in the hands of the commander. When you are in command, you and you alone must make the decision; and possibly face a board of inquiry at Starfleet Command to justify your decision. This, of course, if you survive after making your decision, wich is generally not the case for your crew and yourself after making an error in judgment.
Let’s examine the four types of encounter between starships, with practical suggestions for resolving those situations under Starfleet rules, all the while keeping in mind the desire to keep friendly relations with other cultures without risking the safety of your ship or the Federation.
CONTACT WITH A FRIENDLY SHIP
When a recognized signal is received, you may relax but not let your guard fully down yet*: confirm the signal with a sensor readout and a direct communication channel, preferably with a visual identification. Even after that, proper protocol must be followed, not only for security reasons, but to give proper respect to the commander of a starship.
When meeting a friendly vessel, ask for audio-visual communication as soon as possible. Refusal of immediate compliance without valid explanation could alert you of a possible problem beforehand. Insist on establishing full communication. Do not be hasty in your approach, nor let the other ship close in if it refuses direct contact.
Starfleet regulations authorize a starship commander to stay at maximum sensor range if audio-visual communication can not or will not be established. If any ship, including an allied one, does not follow correct procedure, the commander must demand of said ship to do so, citing the present regulation. If the refusing ship still continues to approach, regulations allow the commander to call for yellow alert and raise shields; in such an instance, the said friendly ship loses it’s friendly status and should be treated as potentially hostile.
CONTACT WITH A NEUTRAL SHIP
Under Starfleet regulations, a ship identified as one belonging to a said neutral party (like the Orion Confederacy ) must be treated as ‘’friendly’’, unless it’s actions can be recognized as ‘’hostile’’. Meeting a neutral ship is especially difficult, as what may be deemed a ‘’hostile posture’’ is entirely up to the ship’s commander during the encounter. His decisions towards a neutral ship might easily find themselves under questioning before a board of inquiry.
( Study of Captain Garth’s exemplary record clearly shows that he always made his decisions with the safety of his ship and of the Federation first and foremost in mind, with the ‘’consequences before the board’’ only as an afterthought. The only proper justification for this attitude – the only one that really matters – is that, time after time, events proved him right each and every time. His record shows that he always acted ‘’ in the interest of peace’’ as much as it was possible, leaving to the other ship all the freedom of choice and the benefit of doubt, until his ship and crew were directly threatened. Each time, he made the proper decision from very little evidence. Such ‘’command instinct’’ can only come from experience. - Kirk )
CONTACT WITH A HOSTILE SHIP
A ship si considered ‘’hostile’’ when identification confirms it to belong to a known declared enemy faction (like the Romulan Star Empire) or by it’s actions (such as opening fire, refusing to maintain proper distance or to communicate*: any one of these actions are considered ‘’hostile’’).
Raising shields might be considered a preparatory act prior to a hostile action. Therefore, shields should be kept down as long as possible, as long as there is no clear and immediate danger to the ship. A vessel on an intercepting course and refusing to communicate is taking a potentially hostile posture, just like a ship coming into firing range despite repeated warnings. Despite all this, a ship’s commander should order to raise shields only if he beleives an attack is imminent.
( in rarer cases - as with the V’Ger Incident –using active sensors might also be interpreted by the other party as a hostile action. - Kirk )
Once shields are up, be ready for incoming fire! Prepare weaponry and use target lock for maximum efficiency. But do not open fire until you can confirm that you are actually under attack. Regulations do not define such a condition, but a board of Inquiry will certainly do.
If an incoming ship with shields raised maneuvers for best angle of attack, it must be considered hostile. In some rare instances, you might even be forced to fire first. In those rare instances, be very, very sure you will be able to justify your decision afterwards, but do not let hesitation handicap you! Protect your ship and act to the best of your abilities and knowledge.
If you do open fire, Starfleet policy is to neutralize as quickly as possible the other ship’s ability to cause damage. In other terms, make the other ship unable to fight. This doesn’t require the ship’s destruction and considerable loss of life, unless the mere presence of the ship represents ‘’a clear and actual security risk.’’ Inquiry boards rarely declare acceptable or justifiable the complete destruction of a ship.
When an opposing ship display it’s willingness to cease hostilties, allow the possibility, but stay in full defensive posture. Demand complete end of any threat to security, be it by leaving the area or surrendering. Do not allow a ship that committed an act of war (agression within Federation territory or against an unarmed ship identified as conducting legitimate business) the opportunity to leave; it must be made to surrender or put out of commission, wich means unable to go to warp and all offensive weapons inactive.
(certain ships identified as hostile, like those of the Romulan Star Empire, are known to refuse any form of reddition. In case of encounters violating Treaty stipulations, such ships must be destroyed if they openly attack. The ship’s commander is advised, unless otherwise ordered by Starfleet Command, to never approach a disabled Romulan ship, as it’s commander is culturally and dutifully under permanent orders to self-destruct to avoid boarding and capture.. - kirk )
CONTACT WITH AN UNKNOWN SHIP
A ship commander is walking on a wire when encountering a ship not from any known entity. He must be especially wary of initiating any kind of action that could be interpreted as hostile. Give the other time and opportunity to become a friend instead of making him an enemy. Starfleet vessels are under strict orders not to open fire or take any agressive posture towards any unknown ship, unless said ship opens fire or commit a blatant act of hostility or officially declares hostile intent.
Frankly, we could loose a lot of ships and people that way, but this is what distinguishes us from conquerers like Klingons and Romulans. Historically, this policy has brought us much more good than harm. The Andorians met Humanity for the first time with an armed ship; how history would have been different if that encounter had started in conflict? Would there even be a Federation?
You will never be sure of yourself when you will meet an unknown ship. Of course, be prudent and protect your ship! But think also about the future of the Federation. War is not a dishonorable profession. I have been a warrior all my life. But Peace is even more honorable and it is worth taking high risks to establish and preserve it.
( Historical note*: during his first command, Garth of Isar met a heavily damaged ship from a then unknown race. Before any kind of communication could have been established, the alien ship opened fire.
Garth’s ship was damaged but, although he raised shields, he did not immediately return fire. Keeping his shields at maximum between him and the other, he maintained course and speed to stop only at extreme sensor range.
The unknown ship ceased fire. When communication was finally established and computers decrypted the alien’s language, it became known that they had met a Klingon warship wich opened fire and severely damaged theirship before their vastly superior speed and maneuverability allowed them to escape The alien commander, upon detecting Garth’s ship, assumed that the Klingons were coming to finish them off and thus opened fire.
120 members of that unknown race were killed during the Klingon attack; 3 crewmembers of Garth’s ship lost their lives to the unknown vessel’s fire. But despite this tragic first encounter, this new race eventually established mutually profitable commercial and protection treaties with the Federation.
The 3 victims among the crew received posthumously the Medal of Honor and the Z-Magni Peace Prize, while a board of Inquiry commended Captain Garth for having demonstrated ‘’ exceptional restraint and a highly admirable conduct in an effort to ensure and preserve Peace, despite irrefutable evidence of hostile intent’’. Later, it was said that Garth would have commented*:’’ if I had been wrong, I would have been branded a fool and a criminal – but I wouldn’t have had to hear about it.‘’ - Kirk )
These are the established Starfleet rules for deep space missions. All officers are advised to familiarize themselves thoroughly with those rules. as they will dictate how well their performance will be evaluated by their commanding officer, Lotus Fleet Command and Starfleet.
STARFLEET RULES OF ENGAGEMENT
Written by : Captain Garth of Izar
Revised by : Commodore Christopher Pike
Anotated by : Captain James T Kirk
AT FIRST SENSOR CONTACT:
The most dangerous time for two ships meeting in space is at the moment of first sensor contact when the other ship has yet to be identified. This is when the ship commander is at greatest risk of making an error in judgment… an error that could cost you your ship or open fire on a non-hostile vessel..
During this time, you must gather as much information as possible. Keep an eye open for any sign about the other ship’s intentions. Even before proper identification of the other vessel, you might be able to gather sufficient information to safeguard your ship and crew without committing yourself to a wrong course of action.
Observe first both the trajectory and speed of the other ship. An interception course is to be interpreted as a serious warning! Because of the vastness of space, such occurrences are not happening by chance - probabilties against such a random, accidental occurrence are enormous. If your trajectories intersect or just become closer, it is clear the other is looking for you. On the other hand, if the other ship is only within your sensor radius, you can not automatically assume that the other ship detected you and that his actions are related to any direct intention concerning your own ship.
( Nor the opposite - Kirk )
A sensor contact below light speed may not even be that of another ship; however, no natural phenomenon can move at the speed of light. Any speed of warp one or over, any faster than light movement, shows the definite presence of an artificial object of sentient origin
( The ‘’Lights of Zetar’’ and the ‘’Vampire Cloud’’ are two lifeforms known to move beyond the light barrier without the need of any technology. Although both are deemed destroyed, they suggest the remote but factual possibility of natural forces achieving faster than light travel. Some subatomic particles can also achieve this, a well known fact during Capt Garth’s time, so we must assume that his remark meant that no natural phenomenon can deliberately break the light barrier with a predetermined, voluntary trajectory; a statement that was true at his time, before said lifeforms were discovered to challenge this assumption. - Kirk )
A parallel trajectory, especially if it also parallels your own speed, is equally significant. Such a ship does not want immediately to approach you, mainly to observe you. It is also possible that the commander of this ship has underestimated your sensor range and beleives that you are unaware of his presence. He might also want to make himself known to you without looking for direct contact.
Observe the other ship’s trajectory and it’s speed. This will give you how much time you have to gather information before identifying it… or before it opens fire! Use this available time to learn as much as possible, even if it is only for a few seconds. At the end of this time, you will have to rapidly make your decision based on those informations. Do not act out of ignorance.
UPON IDENTIFICATION
A ship close enough to be identified will fall under one of four possible categories. Starfleet rules and regulations provide adequate procedures for each type of encounter, but they are sufficiently generalized to allow a ship commander all the necessary freedom of decision in the field. There is however one underlying philosophy behind all of these procedures*: the desire to preserve Peace.
When a conflict can be avoided without endangering the safety of the Federation, a Starfleet commander is bound by duty to apply such an option. Above all rules and laws remains one simple principle*: we have to share this galaxy with all of it’s inhabitants. The rights and privileges of all lifeforms must be acknowledged without reserve, even when considering a ship from a declared enemy of the Federation. It is up to a ship commander to judge if said vessel is exercising his rights and privileges or is committing and act of agression. The line between the two may appear very thin.
Federation policy forbids a Starfleet vessel from opening fire against any and all other vessels unless said vessel ‘’ by it’s presence or actions represents a clear and immediate danger for Federation security, the free and safe passage of it’s citizens, or otherwise does not comform itself to the legal proceedings allowed for a ship of it’s registration.’’
Regulations stipulate that any ship ‘’ with an attitude directly and openly threatening to the safety of a Starfleet vessel’’ may be targeted, but only if ‘’ according to the sound judgment of the commander, no other reasonable course of action can be adopted to avoid an armed conflict without further endangering the Federation, it’s citizens or the ship itself.’’
Despite those clear statements, the decision is mostly in the hands of the commander. When you are in command, you and you alone must make the decision; and possibly face a board of inquiry at Starfleet Command to justify your decision. This, of course, if you survive after making your decision, wich is generally not the case for your crew and yourself after making an error in judgment.
Let’s examine the four types of encounter between starships, with practical suggestions for resolving those situations under Starfleet rules, all the while keeping in mind the desire to keep friendly relations with other cultures without risking the safety of your ship or the Federation.
CONTACT WITH A FRIENDLY SHIP
When a recognized signal is received, you may relax but not let your guard fully down yet*: confirm the signal with a sensor readout and a direct communication channel, preferably with a visual identification. Even after that, proper protocol must be followed, not only for security reasons, but to give proper respect to the commander of a starship.
When meeting a friendly vessel, ask for audio-visual communication as soon as possible. Refusal of immediate compliance without valid explanation could alert you of a possible problem beforehand. Insist on establishing full communication. Do not be hasty in your approach, nor let the other ship close in if it refuses direct contact.
Starfleet regulations authorize a starship commander to stay at maximum sensor range if audio-visual communication can not or will not be established. If any ship, including an allied one, does not follow correct procedure, the commander must demand of said ship to do so, citing the present regulation. If the refusing ship still continues to approach, regulations allow the commander to call for yellow alert and raise shields; in such an instance, the said friendly ship loses it’s friendly status and should be treated as potentially hostile.
CONTACT WITH A NEUTRAL SHIP
Under Starfleet regulations, a ship identified as one belonging to a said neutral party (like the Orion Confederacy ) must be treated as ‘’friendly’’, unless it’s actions can be recognized as ‘’hostile’’. Meeting a neutral ship is especially difficult, as what may be deemed a ‘’hostile posture’’ is entirely up to the ship’s commander during the encounter. His decisions towards a neutral ship might easily find themselves under questioning before a board of inquiry.
( Study of Captain Garth’s exemplary record clearly shows that he always made his decisions with the safety of his ship and of the Federation first and foremost in mind, with the ‘’consequences before the board’’ only as an afterthought. The only proper justification for this attitude – the only one that really matters – is that, time after time, events proved him right each and every time. His record shows that he always acted ‘’ in the interest of peace’’ as much as it was possible, leaving to the other ship all the freedom of choice and the benefit of doubt, until his ship and crew were directly threatened. Each time, he made the proper decision from very little evidence. Such ‘’command instinct’’ can only come from experience. - Kirk )
CONTACT WITH A HOSTILE SHIP
A ship si considered ‘’hostile’’ when identification confirms it to belong to a known declared enemy faction (like the Romulan Star Empire) or by it’s actions (such as opening fire, refusing to maintain proper distance or to communicate*: any one of these actions are considered ‘’hostile’’).
Raising shields might be considered a preparatory act prior to a hostile action. Therefore, shields should be kept down as long as possible, as long as there is no clear and immediate danger to the ship. A vessel on an intercepting course and refusing to communicate is taking a potentially hostile posture, just like a ship coming into firing range despite repeated warnings. Despite all this, a ship’s commander should order to raise shields only if he beleives an attack is imminent.
( in rarer cases - as with the V’Ger Incident –using active sensors might also be interpreted by the other party as a hostile action. - Kirk )
Once shields are up, be ready for incoming fire! Prepare weaponry and use target lock for maximum efficiency. But do not open fire until you can confirm that you are actually under attack. Regulations do not define such a condition, but a board of Inquiry will certainly do.
If an incoming ship with shields raised maneuvers for best angle of attack, it must be considered hostile. In some rare instances, you might even be forced to fire first. In those rare instances, be very, very sure you will be able to justify your decision afterwards, but do not let hesitation handicap you! Protect your ship and act to the best of your abilities and knowledge.
If you do open fire, Starfleet policy is to neutralize as quickly as possible the other ship’s ability to cause damage. In other terms, make the other ship unable to fight. This doesn’t require the ship’s destruction and considerable loss of life, unless the mere presence of the ship represents ‘’a clear and actual security risk.’’ Inquiry boards rarely declare acceptable or justifiable the complete destruction of a ship.
When an opposing ship display it’s willingness to cease hostilties, allow the possibility, but stay in full defensive posture. Demand complete end of any threat to security, be it by leaving the area or surrendering. Do not allow a ship that committed an act of war (agression within Federation territory or against an unarmed ship identified as conducting legitimate business) the opportunity to leave; it must be made to surrender or put out of commission, wich means unable to go to warp and all offensive weapons inactive.
(certain ships identified as hostile, like those of the Romulan Star Empire, are known to refuse any form of reddition. In case of encounters violating Treaty stipulations, such ships must be destroyed if they openly attack. The ship’s commander is advised, unless otherwise ordered by Starfleet Command, to never approach a disabled Romulan ship, as it’s commander is culturally and dutifully under permanent orders to self-destruct to avoid boarding and capture.. - kirk )
CONTACT WITH AN UNKNOWN SHIP
A ship commander is walking on a wire when encountering a ship not from any known entity. He must be especially wary of initiating any kind of action that could be interpreted as hostile. Give the other time and opportunity to become a friend instead of making him an enemy. Starfleet vessels are under strict orders not to open fire or take any agressive posture towards any unknown ship, unless said ship opens fire or commit a blatant act of hostility or officially declares hostile intent.
Frankly, we could loose a lot of ships and people that way, but this is what distinguishes us from conquerers like Klingons and Romulans. Historically, this policy has brought us much more good than harm. The Andorians met Humanity for the first time with an armed ship; how history would have been different if that encounter had started in conflict? Would there even be a Federation?
You will never be sure of yourself when you will meet an unknown ship. Of course, be prudent and protect your ship! But think also about the future of the Federation. War is not a dishonorable profession. I have been a warrior all my life. But Peace is even more honorable and it is worth taking high risks to establish and preserve it.
( Historical note*: during his first command, Garth of Isar met a heavily damaged ship from a then unknown race. Before any kind of communication could have been established, the alien ship opened fire.
Garth’s ship was damaged but, although he raised shields, he did not immediately return fire. Keeping his shields at maximum between him and the other, he maintained course and speed to stop only at extreme sensor range.
The unknown ship ceased fire. When communication was finally established and computers decrypted the alien’s language, it became known that they had met a Klingon warship wich opened fire and severely damaged theirship before their vastly superior speed and maneuverability allowed them to escape The alien commander, upon detecting Garth’s ship, assumed that the Klingons were coming to finish them off and thus opened fire.
120 members of that unknown race were killed during the Klingon attack; 3 crewmembers of Garth’s ship lost their lives to the unknown vessel’s fire. But despite this tragic first encounter, this new race eventually established mutually profitable commercial and protection treaties with the Federation.
The 3 victims among the crew received posthumously the Medal of Honor and the Z-Magni Peace Prize, while a board of Inquiry commended Captain Garth for having demonstrated ‘’ exceptional restraint and a highly admirable conduct in an effort to ensure and preserve Peace, despite irrefutable evidence of hostile intent’’. Later, it was said that Garth would have commented*:’’ if I had been wrong, I would have been branded a fool and a criminal – but I wouldn’t have had to hear about it.‘’ - Kirk )
Fleet XO - RP Director - Former Fleet Admiral, Operations CO, JAG and Ambassador - Former Captain of the USS Artemis and of the flagship USS Horizon - Current Captain of the USS Millennium
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
-
Kheren - Admiral
- Posts: 930
- Joined: Mon Aug 06, 2012 9:40 pm
- Location: Trois-Rivieres, Quebec, Canada
- Has thanked: 444 times
- Been thanked: 396 times
- Medals: 43
-
-
-
-
-
-
-
-
Starfleet Rules & Regulations
by Kheren » Sun Jan 13, 2013 1:54 pm
Useful Starfleet data by Kheren
USEFUL STARFLEET DATA
Here is a compilation of information all Starfleet officers, especially those in leading positions, must be aware of. In RP, they are as much tools for plotting stories and events as they are for describing scenes or roleplaying a Starfleet character in a wide variety of situations, even providing dialog lines and references for them in specific circumstances. GM/Captains can also use this data to help players wondering what to do next or what will happen if they do this or that, what they are allowed or not as a character or what really happens and what they are expected to know and do when a captain calls for yellow or red alert or to abandon ship.
Star Trek is a richly detailed universe. Using the available data here will help all roleplayers to give their character's actions and words that ''Trek style'' and credibility needed to look and feel as part of this wonderful setting.
The following includes:
I - STARFLEET REGULATIONS
II- STARFLEET CODES
III - SECURITY LEVELS
IV - STARSHIP MISSION TYPES
V – STARSHIP OPERATING MODES
VI - EMERGENCY OPERATIONS
I - STARFLEET REGULATIONS
These are taken out from a variety of media sources relating to Star Trek. Some are hard canon (cited on series episodes or films) while others are soft canon (all other sources) with references given when available so that the RPer can look it up in the actual source material for proper context.
Regulation 1: Starfleet General Orders are binding and supercede any other rule, regulation or orders given in the field.(Starfleet Technical Manual)
Regulation 2:Starfleet regulation against the taking of intelligent life.
Regulation 3, Paragraph 12: In the event of imminent destruction, a Starfleet Captain is authorized to preserve the lives of his crew by any justifiable means.
Regulation 7, Paragraph 4: an officer is to be placed under arrest if accused of violating the Prime Directive, unless that officer can give satisfactory answer to such charge in the presence of the most senior fellow officers available. (TOS novel Pime Directive)
Regulation 10 (Directive 010): "Before engaging alien species in battle, any and all attempts to make first contact and achieve nonmilitary resolution must be made." (VOY episode: "In the Flesh",TNGnovel: The Buried Age)
Regulation 12 (Directive 012): "When engaged in contact with an unknown alien species, all attempts must be made to resolve said combat using minimum necessary force." In the manual, there is a discussion section stressing the importance of achieving communication with the hostiles so that conflict can be understood and resolved through diplomatic means. Such a battle is often the result of a misunderstanding or an unintentional intrusion into the territory of the attacking ship. (TNG novel: The Buried Age)
Regulation 12, Chapter 4: Relates to the Captain undertaking command of an away mission.(Star Trek Nemesis)
Regulation 21, Section 6, Paragraph 4: "Federation security supersedes the rights and privileges of Federation citizens." (New Worlds, New Civilizations short story: "An Enigma Wrapped in a Puzzle")
Regulation 28 subsection D (Protocol 28 (Subsection D): "In the event of hostile alien takeover the EMH is to deactivate and wait for rescue." (VOY episode: "Message in a Bottle")
Regulation 36 (Tactical Directive 36):"The captain will not personally engage a hostile force without the protection of a security officer."
Regulation 42/15: "Pressure Variances in IRC Tank Storage" Part of the basic operational specifications for impulse engines. (TNG episode: ''Relics'')
Regulation 46: Establishes communications protocols in combat situations.
Section A states, "If transmissions are being monitored during battle, no uncoded messages are to be transmitted on an open channel." (Star Trek II: ''The Wrath of Khan'')
Regulation 72: This directive prohibits the release of enemy prisoners during wartime without authorization from*Starfleet Command. (TOS - Uchu comic: "Art of War")
Regulation 73-C, Subsection A: Required all Starfleet personnel to undergo a routine psychological scan at least once a year, or whenever deemed necessary by a physician. (TOS novel: Strangers from the Sky)
Regulation 101 (Directive 101): "Any individual accused of murder does not have to answer any questions."
Regulation 104 Establishes the chain of command on a Starship or Starbase.
Section A establishes procedures for the assumption of command by the ranking officer in even of the death or incapacitation of his superior officers.
Section B establishes procedures for a senior officer outside the chain of command to assume command of a Starship or Starbase. In the absence of a starship's assigned captain, a flag officer has the authority to assume command of the starship should he deem it necessary. (TOS episodes: ''The Doomsday Machine,'' ''The Deadly Years.'')
Section C establishes procedures for removal from command of an officer deemed medically unfit by the Chief Medical Officer of a Starship or Starbase. Should it be proven with admissible evidence that the flag officer who has assumed command is medically or psychologically unfit for command, the starship's highest ranking officer may relieve him on that basis. (TOS episode: ''The Doomsday Machine'' and Star Trek XI)
Regulation 106, Paragraph 1: Bars the chief engineer from resigning while the ship is undergoing a class-two refit. (TOS novel Prime Directive)
Regulation 121 : Establishes how a physically, psychologically or emotionally compromised officer is not fit to serve in the position of Captain. (Star Trek novelization) .
Section A (Protocol 121 (Section A) states: The Chief Medical Officer has the power to relieve an officer or crewman, including a superior one, of their duties if in the officer's professional judgment, he or she is medically unfit. ( TOS episodes: ''The Doomsday Machine,'' The Deadly Years,'' ''Obsession,'' ''Turnabout Intruder''; TNG episode: "Lonely Among Us"; VOY episode: "Year of Hell, Part II"; SCE eBook: Oaths). But said Chief medical officer is required to present a formal medical examination report to support his decision (TOS: ''The Doomsday Machine'') or under General Order 28 and 39 conditions (Starfleet technical manual).
Regulation 157 : Starfleet officers shall take all necessary precautions to minimize any participation in historical events.(DS9 episode: ''Trials and Tribble-ations'')
157-A : No contact shall be made with any planet or culture during a temporal incursion that could otherwise result in an alteration of recorded historical events. This disposition includes all members of the United Federation of Planets. Contact includes but is not limited to; audio or video contact, away team operation or any direct or indirect encounter that could provoke an interruption in the normal chain of events.
157-B :In any condition where contact could result, like assuming orbit of an inhabited planet or space encounter, all measures must be made to minimize the possibility of detection. All known camouflage measures are authorized, including the use of cloaking devices in time periods prior to the Treaty of Algeron (Gregorian Calendar 2311) and after its dissolution (Gregorian calendar 2409).
157-C : Any ship involved in a time displacement is on standing orders to self destruct in order to avoid historical-disruptive detection under the following or similar conditions:
- Loss of travel capability that could result in making accessible anachronistic data or technologies susceptible to affect the time period (known as the Narada Factor);
- Contact with higher lifeforms listed as Hostile by Starfleet which could result in unrestorable time alterations (known as the Q Factor);
- Contact with vessels and installations which could result in unrestorable time alterations (Known as the Aeon Factor).
157-D: Following the Prime Directive and the Temporal Prime Directive, no action is to be taken that will disrupt the normal developpement of any planet or culture. The following are examples of cause and effect scenarios that cannot be allowed to happen:- Removing a living organism from its natural environement affecting the food chain slightly but enough to cause and evolutionary change (known as the Voth Factor);
- Litter and forgotten gear that could be salvaged, examined or retroengineered by a culture so as to become the basis of a scientific, technological or sociocultural revolution (known as the Iotian Factor)
- Exposing Starfleet insigna, ship profile or item and person denomination that could alter cultural parameters, such as becoming the basis of a philosophy or religion (Known as the Mintakan Factor).
Regulation 191, Article 14: In a combat situation involving more than one ship, command falls to the vessel with tactical superiority.
Regulation 202 (Starfleet Directive 1-202-B): A rarely used Starfleet regulation which permitted senior officers, to commandeer private, commercial, and military spacecraft in emergency situations. (TOS Star Trek II Short Stories: "The Blaze of Glory")
Regulation 256.15: "Officers shall show professional behavior at all times." (TOS novel: Vulcan's Forge)
Regulation 342-188564.3 (Paragraph 3): A class-3 biohazard alert. All personnel not part of a Biohazard Response Team is to stay away from any site broadcasting such an alert.
Regulation 476.9: All away teams must report to the bridge at least once every 24 hours.(VOY episode: "Once Upon a Time")
Regulation 710: Establishes protocols for the restriction of space traffic in the vicinity of the sender.
Regulation 2005: Establishes protocols and procedures for the engaging of the autodestruct sequence on a Starship or Starbase. Orders the destruction of a starship by allowing matter and antimatter to mix in an uncontrolled manner. This is a last resort for a captain that allows him/her to prevent their ship or crew from falling into enemy hands. (Star Trek: The Motion Picture)
Regulation 2884.3: Substances unstable in an oxygen atmosphere must be handled with care.
Regulation 3121: Establishes the right of access to subspace communications for personnel on a Starship or Starbase.
Regulation 3194: Restricts access to subspace communications for personal messages while on duty.
Regulation 3287.0: Due to its high volatile nature, antimatter must be stored in magnetic confinement pods.
Special Regulation 66715: Federation order that states: "[Starfleet has] the authority to neutralize security threats by any means necessary". In a Section 31 holoprogram Luther Sloan initiated the order. Starfleet initiated this order following the fall of Betazed. (DS9 episode: "Inquisition", DS9 novel: Hollow Men)
Regulation Q (Procedure Q): If a state of deep hostility exists, a landing party is to beam down fully armed and ready for any kind of trouble.
Non-specified regulations
Health-Related
- "All research personnel on alien planets are required to have their health certified by a starship surgeon at one-year intervals." (TOS episode: "The Man Trap")
- "The ship's surgeon will require a full examination of any crew member that he has doubts about, including the Captain." (TOS episode: "Turnabout Intruder"). Such examination however cannot be ordered during alert condition as long as the officer is not displaying blatant acts endangering ship and crew like a suicidal order or attempt (TOS episode: ''The Doomsday machine'') and is supported by at least one officer of command grade (Commander or higher) (TOS episode: ''Obsession'')
- "Nothing shall be beamed aboard until danger of contamination has been eliminated. Beaming down to the surface (of a planet) IS permitted, if the Captain decides the mission is vital, and reasonably free of danger". (TOS movie: Star Trek III: The Search for Spock; VOY episode: "Macrocosm")
- "The Chief Medical Officer outranks the captain in health matters." (VOY*episode: "Persistence of Vision")
- A captain cannot order a doctor to violate Doctor-Patient Confidentiality, except in situations of ship security. (VOY episode: "Fury")
- "All Starfleet personnel must obtain authorization from their CO as well as clearance from their medical officer, before initiating an intimate relationship with an alien species." (VOY episode: "The Disease")
- Medical Emergency on Alien Terrain: "It is recommended to keep an open com-channel at all times." (VOY episode: "Macrocosm")
- "Specifically forbid the transport of unknown infectious agents onto a starship without establishing containment and eradication protocols." (VOY episode: "Macrocosm")
Miscellaneous
- "Ground combat personnel are to rotate off the front lines every ninety days." (DS9 episode: "The Siege of AR-558")
- "No killing of intelligent lifeforms." (TAS episode: "One of Our Planets is Missing")
-"Striking a fellow officer is a court-martial offense." (TOS episode: "This Side of Paradise"; VOY episode: "Parallax"; ENT episode: "Bound")
-"Encroaching on the territory of an alien species is prohibited." (VOY*episode: "The Swarm")
-"All ships must drop out of warp at the edge of a system before proceeding on to the inner planets" (TNGvideo game:*Bridge Commander)
-Starfleet regulations call for declaring yellow alert when a starship is targeted by laser weapons. According to Jean-Luc Picard, such regulations were "very old". (TNG: "The Outrageous Okona")
- According to Starfleet protocol, "Sir" is the proper address when responding to one's commanding officer (or possibly any superior officer) (VOY: "Caretaker"), but naval tradition dictates the use of "Captain", regardless of the CO's rank (DS9: "Behind the Lines" & Star Trek the Motion Picture).
This however does not apply to someone temporarily put in command during the assigned captain's absence such as for duty shifts or during away team missions lead by the captain, unless of actual Captain rank. The title ''Acting Captain'' is allowed only for an officer temporarily in full command of a starship during an entire operation while the assigned captain is otherwise unavailable.
-On board a starship, only the commanding officer is addressed as captain, regardless of actual rank and of actual rank of any other officer on board. To avoid confusion, any ranked captain also on board is addressed as Sir and/or could see his rank temporarily reduced to that of Commander (Star Trek the Motion Picture).
-Starfleet rules forbade dealing with outlaws and getting involved in the politics of other cultures. (VOY: "Alliances")
-Starfleet protocols included guidelines on proper punctuation of reports, such as conn reports. (VOY: "Dreadnought")
-"Interference in alien conflicts is strictly prohibited." (VOY: "Nightingale")
-Procedures pertaining to official requests for asylum to a Starfleet captain include a hearing. (VOY: "Death Wish")
-Accidents aboard Starfleet vessels were to be followed by an investigation into the cause of the accident. (VOY: "Day of Honor") including autopsies and medical and psychological examination of all involved individuals.
-An official/formal letter, written to a senior officer, must be replied to by a senior officer. (VOY: "Tinker Tenor Doctor Spy")
II- STARFLEET CODES
-Code 1: signals either a total or imminent disaster, a possible invasion, or indicates that the Federation is either currently or about to be engaged in open warfare with a hostile power. The code requires all Starfleet personnel within the affected area to immediately assume a 'war' footing or posture. It is also colloquially known as "Defense Alert", or a "Priority One Alert". (TOS episodes: "Errand of Mercy", "The Trouble with Tribbles", "The Alternative Factor")
Code 7-10: a "quarantine code". No Starfleet or Federation-registered starship is to approach a system or vessel which is broadcasting Code 7-10. (TOS episode: "A Taste of Armageddon")
Code 47: an ultra-secure communications protocol. So secure that all traces of a Code 47 transmission or communication are automatically wiped from all computer records. (TNG episode: "Conspiracy") Only personnel with a level 10 security clearance can invoke a code 47.
III - SECURITY LEVELS
Access to all Starfleet data is highly regulated. A standard set of access levels have been programmed into the computer cores of all ships in order to stop any undesired access to confidential data.
Security levels are also variable, and task-specific. Certain areas of the ship are restricted to unauthorized personnel, regardless of security level. Security levels can also be raised, lowered, or revoked by Command personnel.
Security levels are:
Level Dukovchka: a special security clearance (usually reserved to Federation Council members, Admirals and Sector Commanders) for access to top secured material like the research report on the Omega particle or the ship logs of the USS Enterprise's voyages to Talos IV. It also grants the autority to disclose said information to any non-autorized personnel under the sole responsibility of the officer.
Level 10 – Captain and Above (minimum level for access to highly restricted material like the Omega Directive or the Genesis research)
Level 9 – First Officer (only officer who's command status can shift to level 10 automatically upon official recording of the captain's permanent absence when no other officer of higher rank is present)
Level 8 – Commander (minimum level for assuming command without a direct order outside of emergencies)
Level 7 – Lt. Commander
Level 6 – Lieutenant
Level 5 – Lt. Junior Grade (minimum level for departemental head responsibility)
Level 4 – Ensign (minimum level for unrestricted access to bridge and other restricted areas like main engineering and auxilliary control)
Level 3 – Non-Commissioned Crew
Level 2 – Civilian Personnel (autorized only on starships or Starfleet installations with appropriate facilities and assigned to missions implying extended separation from a crewmember's immediate family; or to civilian mission specialists).
Level 1 – Open Access (Read Only)
Note: Security Levels beyond current rank can and are bestowed or revoked where, when and to whom they are necessary by any officer of Command Grade.
The main computer grants access based on a battery of checks to the individual user, including face and voice recognition in conjunction with a vocal code as an added level of security, and/or retina scan, DNA check etc. as appropriate and determined for any specific material.
IV - STARSHIP MISSION TYPES
Operations aboard a starship fall under one of three categories: flight operations, primary mission operations, and secondary mission operations.
Flight Operations are all operations that relate directly to the function of the starship itself, which include power generation, starship upkeep, environmental systems, and any other system that is maintained and used to keep the vessel spaceworthy.
Primary Mission Operations entail all tasks assigned and directed from the Main Bridge, and typically require full control and discretion over ship navigation and ship's resources.
Secondary Mission Operations are those operations that are not under the direct control of the Main Bridge, but do not impact Primary Mission Operations. Some examples of secondary mission operations include long-range cultural, diplomatic or scientific programs run by independent or semi-autonomous groups aboard the starship.
Despite the fact that most starship designs philosophy leaned heavily toward Exploration and Diplomatic Missions, most are still classified as a multi-role Starship, in keeping with Federation Council Policy. This offers the Federation, and Starfleet, flexibility in assigning nearly any objective within the realm of Starfleet's assigned duties.
Missions for a starship may fall into one of the following categories; the order of her strongest capable mission parameter to her weakest mission parameter is dictated by ship design and specific assignement.
Federation Policy and Diplomacy: A starship can be used as an envoy during deep-space operations just like a starfleet installation can be used as an embassy for foreign dignitaries and diplomatic or political meetings, treaty agreements and signing or first contact situations. The Federation charter is the primary guideline for those mission types.
Emergency/Search and Rescue: Typical Missions include answering standard Federation emergency beacons, extraction of Federation or Non-Federation citizens in distress, retrieval of Federation or Non-Federation spacecraft in distress, small-scale planetary evacuation - medium or large scale planetary evacuation is not feasible. Regardless of ship or installation design or purpose, this type of mission has unconditional priority over all others when such situations occurs as per Starfleet General Orders.
Exploration: interstellar survey and mapping missions, as well as the ability to explore a wide variety of planetary classifications.
Contact with New Lifeforms: Pursuant to Starfleet Policy regarding the discovery of new life, facilities aboard most starship designs and Starfleet installations include a variety of exobiology and xenobiological suites, and a small cultural anthropology staff, allowing for at least limited deep-space life form study and interaction. The Prime Directive is the key guideline during such missions.
Scientific Investigation: A starship or Starfleet installation is equipped with scientific laboratories and a variety of sensor probes and sensor arrays, giving the ability to perform a variety of ongoing scientific investigations even if the design's primary function and assignement is otherwise.
Tactical/Defensive/Peacekeeping Operations: Typical Missions include patrolling Borders and occupation zones, interdiction missions, or protecting any Federation interest from hostile intent in planetary or interstellar conflicts. Every starship design and Starfleet installation is therefore at least equipped with shields and phaser arrays, including shuttles. Starfleet Rules of Engagement are the standard regulations for such mission types and the basis of evaluation in any board of inquiry regarding events causing loss of ship or of sentient life.
V – STARSHIP OPERATING MODES
The normal flight and mission operations of a starship are conducted in accordance with a variety of Starfleet standard operating rules, determined by the current operational state of the starship. These operational states are determined by the Commanding Officer, although in certain specific cases, the Computer can automatically adjust to a higher alert status.
The major operating modes are:
Condition Green ( or Cruise mode : standard travel for transportation, patrol and interstellar charting mode)
Condition Yellow or Yellow Alert (or security alert: alpha shift on duty, second (or current) shift on standby, all security personnel on duty, emergency forcefields activated, one auxilliary craft prepared for launch, shields up, phasers pre-heated and one torpedo loaded)
Condition Red or Red Alert (or general quarters: all on board on duty, security personnel armored and heavily armed, sickbay on standby for emergency medical operations, engineering under full damage control protocols, civilians into sheltered areas or to lifepods, all offensive and defensive capabilities at maximum, emergency channels open)
Condition Blue ;(or External Support Mode: when entering a starbase or docking to a space station; navigation is taken over by the base's flight control or the ship tugged by tugshuttles.)
Reduced Power Mode ;(standard parking procedure for refit or repairs. It takes at least half an hour to reactivate a ship from this mode, excluding the time required to recall the crew or reapprovisionate the ship).
SEPARATED FLIGHT MODE
During catastrophic systems failure aboard a starship, most designs allows a Primary Saucer section to detach from their engineering hull and flee via emergency thrusters and the retained forward momentum from emergency separation. Most designs, having the impulse engine installed on the primary hull, allows impulse speeds however.
This separation is considered a permanent measure, as reattaching the engineering hull to the saucer section requires a Starbase facility or Repair Depot to completely integrate the two vessels again.
A few specific designs however have the capability to reattach themselves without such requirement (such as the Galaxy class and the Prometheus class; the Ambassador class bridge module also falls into this category).
Others do not even have this option simply due to their structural design (such as theDefiant class, the Intrepid class and the Akira class).
Typically, situations that require abandoning the engineering hull result in the destruction of the engineering hull, and upon rescue of the saucer section crew, the vessel is decommissioned.
LANDING MODE
Due to the unique shape of their hull, most ship classes cannot land within a gravity well and maintain hull integrity for Transatmospheric operations (some exceptions include the Intrepidand Defiant classes).
This does not mean that the hull of other starship designs cannot withstand a landing - quite the contrary, in an extreme emergency, all starship designs could effect a surface landing while only losing a certain percentage of hull integrity and structural members depending on the specific design and overall mass/size ratio. In those cases however, while integrity is not high enough to allow for deep-space operations, enough of the internal volume and structural members should remain to allow for a landing that is safe for her crew.
VI - EMERGENCY OPERATIONS
EMERGENCY MEDICAL OPERATIONS
Pursuant to Starfleet General Policy and Starfleet Medical Emergency Operations, a number of the officers and crew of any starship and Starfleet installation are cross-trained to serve as Emergency Medical Technicians, to serve as triage specialists, medics, and other emergency medical functions along with non-medical emergency operations in engineering or tactical departments. This set of policies was established due to the wide variety of emergencies, both medical and otherwise, that a Federation Starship could respond to on any given mission.
The recreation decks and lounges along with VIP/guest quarters can serve as emergency intensive care wards, with an estimated online timeframe of 30 minutes with maximum engineering support. Further, shuttle bays usually have mobile hospitals that can be deployed either on the flight deck, or transported to Cargo Bays for emergency overflow triage centers. All facilities are equipped with full Bio-hazard suites, to minimize and prevent crew exposure to potentially deadly diseases.
LIFEBOATS
Aside from the escape options of shuttlecraft or transporters, the primary survival craft of all starships and Starfleet installations is the escape pod or lifeboat. Each Lifeboat can support a full complement between 2 to 8 people (depending on size) for several months, longer if the lifeboats connect together. All are equipped with navigational sensors, microthrusters, plus emergency subspace communication equipment.
RESCUE AND EVAC OPERATIONS
Rescue and Evacuation Operations for a starship or Starfleet installation will fall into one of two categories – abandoning the facility or rescue and evacuation from a planetary body or another facility.
Resources are available for rescue and evacuation include:
-The ability to transport via personnel transporters.
-The availability of shuttlecrafts to be on hot-standby for immediate launch, with all additional shuttlecrafts available for launch in an hours notice. Total transport capabilities of these craft vary due to differing classifications to offload from a standard orbit to an M Class planetary surface.
-Capacity to support evacuees with conversion of the shuttle bays and cargo bays to emergency living quarters.
-Ability to convert Holosuites, Recreation Decks and the Crew Lounges to emergency triage and medical centers.
-The larger ships like the Ambassador class and properly configured Akira class have the ability to temporarily convert Cargo Bays to type H,K, or L environments, intended for non-humanoid casualties.
ABANDON SHIP OPERATION
Resources available for abandon-ship scenarios include:
-The ability to transport from the ship via personnel and emergency transporters.
-The availability of shuttlecrafts to be on hot-standby for immediate launch, with all additional shuttlecrafts available for launch in an hours notice. Total transport capabilities of these craft vary due to differing classifications to offload from a standard orbit to an M Class planetary surface.
-Protocols also include the use of Lifeboats. Each lifeboat can support a full compliment for months, longer if they connect together in "Gaggle Mode".
-Environmental Suits are available for evacuation directly into a vacuum. In such a scenario, personnel can evacuate via airlocks, the flight bay, or through exterior turbolift couplings. Environmental suits are available at all exterior egress points, along with survival lockers spaced through-out the habitable portions of a starship or Starfleet installation.
-Many exterior windows are removable, allowing for egress. However, these manual releases are only activated in the event of atmosphere loss, power loss, certain Red Alert conditions, and only if personnel in contiguous compartments have access to an environmental suit.
(OOC: references:
http://memory-alpha.org/wiki/Portal:Main
http://techspecs.startrek.acalltodut...ederation.html
USEFUL STARFLEET DATA
Here is a compilation of information all Starfleet officers, especially those in leading positions, must be aware of. In RP, they are as much tools for plotting stories and events as they are for describing scenes or roleplaying a Starfleet character in a wide variety of situations, even providing dialog lines and references for them in specific circumstances. GM/Captains can also use this data to help players wondering what to do next or what will happen if they do this or that, what they are allowed or not as a character or what really happens and what they are expected to know and do when a captain calls for yellow or red alert or to abandon ship.
Star Trek is a richly detailed universe. Using the available data here will help all roleplayers to give their character's actions and words that ''Trek style'' and credibility needed to look and feel as part of this wonderful setting.
The following includes:
I - STARFLEET REGULATIONS
II- STARFLEET CODES
III - SECURITY LEVELS
IV - STARSHIP MISSION TYPES
V – STARSHIP OPERATING MODES
VI - EMERGENCY OPERATIONS
I - STARFLEET REGULATIONS
These are taken out from a variety of media sources relating to Star Trek. Some are hard canon (cited on series episodes or films) while others are soft canon (all other sources) with references given when available so that the RPer can look it up in the actual source material for proper context.
Regulation 1: Starfleet General Orders are binding and supercede any other rule, regulation or orders given in the field.(Starfleet Technical Manual)
Regulation 2:Starfleet regulation against the taking of intelligent life.
Regulation 3, Paragraph 12: In the event of imminent destruction, a Starfleet Captain is authorized to preserve the lives of his crew by any justifiable means.
Regulation 7, Paragraph 4: an officer is to be placed under arrest if accused of violating the Prime Directive, unless that officer can give satisfactory answer to such charge in the presence of the most senior fellow officers available. (TOS novel Pime Directive)
Regulation 10 (Directive 010): "Before engaging alien species in battle, any and all attempts to make first contact and achieve nonmilitary resolution must be made." (VOY episode: "In the Flesh",TNGnovel: The Buried Age)
Regulation 12 (Directive 012): "When engaged in contact with an unknown alien species, all attempts must be made to resolve said combat using minimum necessary force." In the manual, there is a discussion section stressing the importance of achieving communication with the hostiles so that conflict can be understood and resolved through diplomatic means. Such a battle is often the result of a misunderstanding or an unintentional intrusion into the territory of the attacking ship. (TNG novel: The Buried Age)
Regulation 12, Chapter 4: Relates to the Captain undertaking command of an away mission.(Star Trek Nemesis)
Regulation 21, Section 6, Paragraph 4: "Federation security supersedes the rights and privileges of Federation citizens." (New Worlds, New Civilizations short story: "An Enigma Wrapped in a Puzzle")
Regulation 28 subsection D (Protocol 28 (Subsection D): "In the event of hostile alien takeover the EMH is to deactivate and wait for rescue." (VOY episode: "Message in a Bottle")
Regulation 36 (Tactical Directive 36):"The captain will not personally engage a hostile force without the protection of a security officer."
Regulation 42/15: "Pressure Variances in IRC Tank Storage" Part of the basic operational specifications for impulse engines. (TNG episode: ''Relics'')
Regulation 46: Establishes communications protocols in combat situations.
Section A states, "If transmissions are being monitored during battle, no uncoded messages are to be transmitted on an open channel." (Star Trek II: ''The Wrath of Khan'')
Regulation 72: This directive prohibits the release of enemy prisoners during wartime without authorization from*Starfleet Command. (TOS - Uchu comic: "Art of War")
Regulation 73-C, Subsection A: Required all Starfleet personnel to undergo a routine psychological scan at least once a year, or whenever deemed necessary by a physician. (TOS novel: Strangers from the Sky)
Regulation 101 (Directive 101): "Any individual accused of murder does not have to answer any questions."
Regulation 104 Establishes the chain of command on a Starship or Starbase.
Section A establishes procedures for the assumption of command by the ranking officer in even of the death or incapacitation of his superior officers.
Section B establishes procedures for a senior officer outside the chain of command to assume command of a Starship or Starbase. In the absence of a starship's assigned captain, a flag officer has the authority to assume command of the starship should he deem it necessary. (TOS episodes: ''The Doomsday Machine,'' ''The Deadly Years.'')
Section C establishes procedures for removal from command of an officer deemed medically unfit by the Chief Medical Officer of a Starship or Starbase. Should it be proven with admissible evidence that the flag officer who has assumed command is medically or psychologically unfit for command, the starship's highest ranking officer may relieve him on that basis. (TOS episode: ''The Doomsday Machine'' and Star Trek XI)
Regulation 106, Paragraph 1: Bars the chief engineer from resigning while the ship is undergoing a class-two refit. (TOS novel Prime Directive)
Regulation 121 : Establishes how a physically, psychologically or emotionally compromised officer is not fit to serve in the position of Captain. (Star Trek novelization) .
Section A (Protocol 121 (Section A) states: The Chief Medical Officer has the power to relieve an officer or crewman, including a superior one, of their duties if in the officer's professional judgment, he or she is medically unfit. ( TOS episodes: ''The Doomsday Machine,'' The Deadly Years,'' ''Obsession,'' ''Turnabout Intruder''; TNG episode: "Lonely Among Us"; VOY episode: "Year of Hell, Part II"; SCE eBook: Oaths). But said Chief medical officer is required to present a formal medical examination report to support his decision (TOS: ''The Doomsday Machine'') or under General Order 28 and 39 conditions (Starfleet technical manual).
Regulation 157 : Starfleet officers shall take all necessary precautions to minimize any participation in historical events.(DS9 episode: ''Trials and Tribble-ations'')
157-A : No contact shall be made with any planet or culture during a temporal incursion that could otherwise result in an alteration of recorded historical events. This disposition includes all members of the United Federation of Planets. Contact includes but is not limited to; audio or video contact, away team operation or any direct or indirect encounter that could provoke an interruption in the normal chain of events.
157-B :In any condition where contact could result, like assuming orbit of an inhabited planet or space encounter, all measures must be made to minimize the possibility of detection. All known camouflage measures are authorized, including the use of cloaking devices in time periods prior to the Treaty of Algeron (Gregorian Calendar 2311) and after its dissolution (Gregorian calendar 2409).
157-C : Any ship involved in a time displacement is on standing orders to self destruct in order to avoid historical-disruptive detection under the following or similar conditions:
- Loss of travel capability that could result in making accessible anachronistic data or technologies susceptible to affect the time period (known as the Narada Factor);
- Contact with higher lifeforms listed as Hostile by Starfleet which could result in unrestorable time alterations (known as the Q Factor);
- Contact with vessels and installations which could result in unrestorable time alterations (Known as the Aeon Factor).
157-D: Following the Prime Directive and the Temporal Prime Directive, no action is to be taken that will disrupt the normal developpement of any planet or culture. The following are examples of cause and effect scenarios that cannot be allowed to happen:- Removing a living organism from its natural environement affecting the food chain slightly but enough to cause and evolutionary change (known as the Voth Factor);
- Litter and forgotten gear that could be salvaged, examined or retroengineered by a culture so as to become the basis of a scientific, technological or sociocultural revolution (known as the Iotian Factor)
- Exposing Starfleet insigna, ship profile or item and person denomination that could alter cultural parameters, such as becoming the basis of a philosophy or religion (Known as the Mintakan Factor).
Regulation 191, Article 14: In a combat situation involving more than one ship, command falls to the vessel with tactical superiority.
Regulation 202 (Starfleet Directive 1-202-B): A rarely used Starfleet regulation which permitted senior officers, to commandeer private, commercial, and military spacecraft in emergency situations. (TOS Star Trek II Short Stories: "The Blaze of Glory")
Regulation 256.15: "Officers shall show professional behavior at all times." (TOS novel: Vulcan's Forge)
Regulation 342-188564.3 (Paragraph 3): A class-3 biohazard alert. All personnel not part of a Biohazard Response Team is to stay away from any site broadcasting such an alert.
Regulation 476.9: All away teams must report to the bridge at least once every 24 hours.(VOY episode: "Once Upon a Time")
Regulation 710: Establishes protocols for the restriction of space traffic in the vicinity of the sender.
Regulation 2005: Establishes protocols and procedures for the engaging of the autodestruct sequence on a Starship or Starbase. Orders the destruction of a starship by allowing matter and antimatter to mix in an uncontrolled manner. This is a last resort for a captain that allows him/her to prevent their ship or crew from falling into enemy hands. (Star Trek: The Motion Picture)
Regulation 2884.3: Substances unstable in an oxygen atmosphere must be handled with care.
Regulation 3121: Establishes the right of access to subspace communications for personnel on a Starship or Starbase.
Regulation 3194: Restricts access to subspace communications for personal messages while on duty.
Regulation 3287.0: Due to its high volatile nature, antimatter must be stored in magnetic confinement pods.
Special Regulation 66715: Federation order that states: "[Starfleet has] the authority to neutralize security threats by any means necessary". In a Section 31 holoprogram Luther Sloan initiated the order. Starfleet initiated this order following the fall of Betazed. (DS9 episode: "Inquisition", DS9 novel: Hollow Men)
Regulation Q (Procedure Q): If a state of deep hostility exists, a landing party is to beam down fully armed and ready for any kind of trouble.
Non-specified regulations
Health-Related
- "All research personnel on alien planets are required to have their health certified by a starship surgeon at one-year intervals." (TOS episode: "The Man Trap")
- "The ship's surgeon will require a full examination of any crew member that he has doubts about, including the Captain." (TOS episode: "Turnabout Intruder"). Such examination however cannot be ordered during alert condition as long as the officer is not displaying blatant acts endangering ship and crew like a suicidal order or attempt (TOS episode: ''The Doomsday machine'') and is supported by at least one officer of command grade (Commander or higher) (TOS episode: ''Obsession'')
- "Nothing shall be beamed aboard until danger of contamination has been eliminated. Beaming down to the surface (of a planet) IS permitted, if the Captain decides the mission is vital, and reasonably free of danger". (TOS movie: Star Trek III: The Search for Spock; VOY episode: "Macrocosm")
- "The Chief Medical Officer outranks the captain in health matters." (VOY*episode: "Persistence of Vision")
- A captain cannot order a doctor to violate Doctor-Patient Confidentiality, except in situations of ship security. (VOY episode: "Fury")
- "All Starfleet personnel must obtain authorization from their CO as well as clearance from their medical officer, before initiating an intimate relationship with an alien species." (VOY episode: "The Disease")
- Medical Emergency on Alien Terrain: "It is recommended to keep an open com-channel at all times." (VOY episode: "Macrocosm")
- "Specifically forbid the transport of unknown infectious agents onto a starship without establishing containment and eradication protocols." (VOY episode: "Macrocosm")
Miscellaneous
- "Ground combat personnel are to rotate off the front lines every ninety days." (DS9 episode: "The Siege of AR-558")
- "No killing of intelligent lifeforms." (TAS episode: "One of Our Planets is Missing")
-"Striking a fellow officer is a court-martial offense." (TOS episode: "This Side of Paradise"; VOY episode: "Parallax"; ENT episode: "Bound")
-"Encroaching on the territory of an alien species is prohibited." (VOY*episode: "The Swarm")
-"All ships must drop out of warp at the edge of a system before proceeding on to the inner planets" (TNGvideo game:*Bridge Commander)
-Starfleet regulations call for declaring yellow alert when a starship is targeted by laser weapons. According to Jean-Luc Picard, such regulations were "very old". (TNG: "The Outrageous Okona")
- According to Starfleet protocol, "Sir" is the proper address when responding to one's commanding officer (or possibly any superior officer) (VOY: "Caretaker"), but naval tradition dictates the use of "Captain", regardless of the CO's rank (DS9: "Behind the Lines" & Star Trek the Motion Picture).
This however does not apply to someone temporarily put in command during the assigned captain's absence such as for duty shifts or during away team missions lead by the captain, unless of actual Captain rank. The title ''Acting Captain'' is allowed only for an officer temporarily in full command of a starship during an entire operation while the assigned captain is otherwise unavailable.
-On board a starship, only the commanding officer is addressed as captain, regardless of actual rank and of actual rank of any other officer on board. To avoid confusion, any ranked captain also on board is addressed as Sir and/or could see his rank temporarily reduced to that of Commander (Star Trek the Motion Picture).
-Starfleet rules forbade dealing with outlaws and getting involved in the politics of other cultures. (VOY: "Alliances")
-Starfleet protocols included guidelines on proper punctuation of reports, such as conn reports. (VOY: "Dreadnought")
-"Interference in alien conflicts is strictly prohibited." (VOY: "Nightingale")
-Procedures pertaining to official requests for asylum to a Starfleet captain include a hearing. (VOY: "Death Wish")
-Accidents aboard Starfleet vessels were to be followed by an investigation into the cause of the accident. (VOY: "Day of Honor") including autopsies and medical and psychological examination of all involved individuals.
-An official/formal letter, written to a senior officer, must be replied to by a senior officer. (VOY: "Tinker Tenor Doctor Spy")
II- STARFLEET CODES
-Code 1: signals either a total or imminent disaster, a possible invasion, or indicates that the Federation is either currently or about to be engaged in open warfare with a hostile power. The code requires all Starfleet personnel within the affected area to immediately assume a 'war' footing or posture. It is also colloquially known as "Defense Alert", or a "Priority One Alert". (TOS episodes: "Errand of Mercy", "The Trouble with Tribbles", "The Alternative Factor")
Code 7-10: a "quarantine code". No Starfleet or Federation-registered starship is to approach a system or vessel which is broadcasting Code 7-10. (TOS episode: "A Taste of Armageddon")
Code 47: an ultra-secure communications protocol. So secure that all traces of a Code 47 transmission or communication are automatically wiped from all computer records. (TNG episode: "Conspiracy") Only personnel with a level 10 security clearance can invoke a code 47.
III - SECURITY LEVELS
Access to all Starfleet data is highly regulated. A standard set of access levels have been programmed into the computer cores of all ships in order to stop any undesired access to confidential data.
Security levels are also variable, and task-specific. Certain areas of the ship are restricted to unauthorized personnel, regardless of security level. Security levels can also be raised, lowered, or revoked by Command personnel.
Security levels are:
Level Dukovchka: a special security clearance (usually reserved to Federation Council members, Admirals and Sector Commanders) for access to top secured material like the research report on the Omega particle or the ship logs of the USS Enterprise's voyages to Talos IV. It also grants the autority to disclose said information to any non-autorized personnel under the sole responsibility of the officer.
Level 10 – Captain and Above (minimum level for access to highly restricted material like the Omega Directive or the Genesis research)
Level 9 – First Officer (only officer who's command status can shift to level 10 automatically upon official recording of the captain's permanent absence when no other officer of higher rank is present)
Level 8 – Commander (minimum level for assuming command without a direct order outside of emergencies)
Level 7 – Lt. Commander
Level 6 – Lieutenant
Level 5 – Lt. Junior Grade (minimum level for departemental head responsibility)
Level 4 – Ensign (minimum level for unrestricted access to bridge and other restricted areas like main engineering and auxilliary control)
Level 3 – Non-Commissioned Crew
Level 2 – Civilian Personnel (autorized only on starships or Starfleet installations with appropriate facilities and assigned to missions implying extended separation from a crewmember's immediate family; or to civilian mission specialists).
Level 1 – Open Access (Read Only)
Note: Security Levels beyond current rank can and are bestowed or revoked where, when and to whom they are necessary by any officer of Command Grade.
The main computer grants access based on a battery of checks to the individual user, including face and voice recognition in conjunction with a vocal code as an added level of security, and/or retina scan, DNA check etc. as appropriate and determined for any specific material.
IV - STARSHIP MISSION TYPES
Operations aboard a starship fall under one of three categories: flight operations, primary mission operations, and secondary mission operations.
Flight Operations are all operations that relate directly to the function of the starship itself, which include power generation, starship upkeep, environmental systems, and any other system that is maintained and used to keep the vessel spaceworthy.
Primary Mission Operations entail all tasks assigned and directed from the Main Bridge, and typically require full control and discretion over ship navigation and ship's resources.
Secondary Mission Operations are those operations that are not under the direct control of the Main Bridge, but do not impact Primary Mission Operations. Some examples of secondary mission operations include long-range cultural, diplomatic or scientific programs run by independent or semi-autonomous groups aboard the starship.
Despite the fact that most starship designs philosophy leaned heavily toward Exploration and Diplomatic Missions, most are still classified as a multi-role Starship, in keeping with Federation Council Policy. This offers the Federation, and Starfleet, flexibility in assigning nearly any objective within the realm of Starfleet's assigned duties.
Missions for a starship may fall into one of the following categories; the order of her strongest capable mission parameter to her weakest mission parameter is dictated by ship design and specific assignement.
Federation Policy and Diplomacy: A starship can be used as an envoy during deep-space operations just like a starfleet installation can be used as an embassy for foreign dignitaries and diplomatic or political meetings, treaty agreements and signing or first contact situations. The Federation charter is the primary guideline for those mission types.
Emergency/Search and Rescue: Typical Missions include answering standard Federation emergency beacons, extraction of Federation or Non-Federation citizens in distress, retrieval of Federation or Non-Federation spacecraft in distress, small-scale planetary evacuation - medium or large scale planetary evacuation is not feasible. Regardless of ship or installation design or purpose, this type of mission has unconditional priority over all others when such situations occurs as per Starfleet General Orders.
Exploration: interstellar survey and mapping missions, as well as the ability to explore a wide variety of planetary classifications.
Contact with New Lifeforms: Pursuant to Starfleet Policy regarding the discovery of new life, facilities aboard most starship designs and Starfleet installations include a variety of exobiology and xenobiological suites, and a small cultural anthropology staff, allowing for at least limited deep-space life form study and interaction. The Prime Directive is the key guideline during such missions.
Scientific Investigation: A starship or Starfleet installation is equipped with scientific laboratories and a variety of sensor probes and sensor arrays, giving the ability to perform a variety of ongoing scientific investigations even if the design's primary function and assignement is otherwise.
Tactical/Defensive/Peacekeeping Operations: Typical Missions include patrolling Borders and occupation zones, interdiction missions, or protecting any Federation interest from hostile intent in planetary or interstellar conflicts. Every starship design and Starfleet installation is therefore at least equipped with shields and phaser arrays, including shuttles. Starfleet Rules of Engagement are the standard regulations for such mission types and the basis of evaluation in any board of inquiry regarding events causing loss of ship or of sentient life.
V – STARSHIP OPERATING MODES
The normal flight and mission operations of a starship are conducted in accordance with a variety of Starfleet standard operating rules, determined by the current operational state of the starship. These operational states are determined by the Commanding Officer, although in certain specific cases, the Computer can automatically adjust to a higher alert status.
The major operating modes are:
Condition Green ( or Cruise mode : standard travel for transportation, patrol and interstellar charting mode)
Condition Yellow or Yellow Alert (or security alert: alpha shift on duty, second (or current) shift on standby, all security personnel on duty, emergency forcefields activated, one auxilliary craft prepared for launch, shields up, phasers pre-heated and one torpedo loaded)
Condition Red or Red Alert (or general quarters: all on board on duty, security personnel armored and heavily armed, sickbay on standby for emergency medical operations, engineering under full damage control protocols, civilians into sheltered areas or to lifepods, all offensive and defensive capabilities at maximum, emergency channels open)
Condition Blue ;(or External Support Mode: when entering a starbase or docking to a space station; navigation is taken over by the base's flight control or the ship tugged by tugshuttles.)
Reduced Power Mode ;(standard parking procedure for refit or repairs. It takes at least half an hour to reactivate a ship from this mode, excluding the time required to recall the crew or reapprovisionate the ship).
SEPARATED FLIGHT MODE
During catastrophic systems failure aboard a starship, most designs allows a Primary Saucer section to detach from their engineering hull and flee via emergency thrusters and the retained forward momentum from emergency separation. Most designs, having the impulse engine installed on the primary hull, allows impulse speeds however.
This separation is considered a permanent measure, as reattaching the engineering hull to the saucer section requires a Starbase facility or Repair Depot to completely integrate the two vessels again.
A few specific designs however have the capability to reattach themselves without such requirement (such as the Galaxy class and the Prometheus class; the Ambassador class bridge module also falls into this category).
Others do not even have this option simply due to their structural design (such as theDefiant class, the Intrepid class and the Akira class).
Typically, situations that require abandoning the engineering hull result in the destruction of the engineering hull, and upon rescue of the saucer section crew, the vessel is decommissioned.
LANDING MODE
Due to the unique shape of their hull, most ship classes cannot land within a gravity well and maintain hull integrity for Transatmospheric operations (some exceptions include the Intrepidand Defiant classes).
This does not mean that the hull of other starship designs cannot withstand a landing - quite the contrary, in an extreme emergency, all starship designs could effect a surface landing while only losing a certain percentage of hull integrity and structural members depending on the specific design and overall mass/size ratio. In those cases however, while integrity is not high enough to allow for deep-space operations, enough of the internal volume and structural members should remain to allow for a landing that is safe for her crew.
VI - EMERGENCY OPERATIONS
EMERGENCY MEDICAL OPERATIONS
Pursuant to Starfleet General Policy and Starfleet Medical Emergency Operations, a number of the officers and crew of any starship and Starfleet installation are cross-trained to serve as Emergency Medical Technicians, to serve as triage specialists, medics, and other emergency medical functions along with non-medical emergency operations in engineering or tactical departments. This set of policies was established due to the wide variety of emergencies, both medical and otherwise, that a Federation Starship could respond to on any given mission.
The recreation decks and lounges along with VIP/guest quarters can serve as emergency intensive care wards, with an estimated online timeframe of 30 minutes with maximum engineering support. Further, shuttle bays usually have mobile hospitals that can be deployed either on the flight deck, or transported to Cargo Bays for emergency overflow triage centers. All facilities are equipped with full Bio-hazard suites, to minimize and prevent crew exposure to potentially deadly diseases.
LIFEBOATS
Aside from the escape options of shuttlecraft or transporters, the primary survival craft of all starships and Starfleet installations is the escape pod or lifeboat. Each Lifeboat can support a full complement between 2 to 8 people (depending on size) for several months, longer if the lifeboats connect together. All are equipped with navigational sensors, microthrusters, plus emergency subspace communication equipment.
RESCUE AND EVAC OPERATIONS
Rescue and Evacuation Operations for a starship or Starfleet installation will fall into one of two categories – abandoning the facility or rescue and evacuation from a planetary body or another facility.
Resources are available for rescue and evacuation include:
-The ability to transport via personnel transporters.
-The availability of shuttlecrafts to be on hot-standby for immediate launch, with all additional shuttlecrafts available for launch in an hours notice. Total transport capabilities of these craft vary due to differing classifications to offload from a standard orbit to an M Class planetary surface.
-Capacity to support evacuees with conversion of the shuttle bays and cargo bays to emergency living quarters.
-Ability to convert Holosuites, Recreation Decks and the Crew Lounges to emergency triage and medical centers.
-The larger ships like the Ambassador class and properly configured Akira class have the ability to temporarily convert Cargo Bays to type H,K, or L environments, intended for non-humanoid casualties.
ABANDON SHIP OPERATION
Resources available for abandon-ship scenarios include:
-The ability to transport from the ship via personnel and emergency transporters.
-The availability of shuttlecrafts to be on hot-standby for immediate launch, with all additional shuttlecrafts available for launch in an hours notice. Total transport capabilities of these craft vary due to differing classifications to offload from a standard orbit to an M Class planetary surface.
-Protocols also include the use of Lifeboats. Each lifeboat can support a full compliment for months, longer if they connect together in "Gaggle Mode".
-Environmental Suits are available for evacuation directly into a vacuum. In such a scenario, personnel can evacuate via airlocks, the flight bay, or through exterior turbolift couplings. Environmental suits are available at all exterior egress points, along with survival lockers spaced through-out the habitable portions of a starship or Starfleet installation.
-Many exterior windows are removable, allowing for egress. However, these manual releases are only activated in the event of atmosphere loss, power loss, certain Red Alert conditions, and only if personnel in contiguous compartments have access to an environmental suit.
(OOC: references:
http://memory-alpha.org/wiki/Portal:Main
http://techspecs.startrek.acalltodut...ederation.html
Fleet XO - RP Director - Former Fleet Admiral, Operations CO, JAG and Ambassador - Former Captain of the USS Artemis and of the flagship USS Horizon - Current Captain of the USS Millennium
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
"In this galaxy, there is a mathematical probability of three million Earth-type planets. In all the universe, three million, million galaxies like this.
And in all of that... and perhaps more...
only one of each of us."
Dr Leonard H. McCoy
TOS Balance of Terror
-
Kheren - Admiral
- Posts: 930
- Joined: Mon Aug 06, 2012 9:40 pm
- Location: Trois-Rivieres, Quebec, Canada
- Has thanked: 444 times
- Been thanked: 396 times
- Medals: 43
-
-
-
-
-
-
-
-