2,589
edits
Apollo-A Alert and Modes: Difference between revisions
no edit summary
mNo edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
{{Apollo-A}} | {{Apollo-A}} | ||
{{LCARS-bar-heading|Apollo-A Operating Modes|280|COLOR=Maroon}} | {{LCARS-bar-heading|Apollo-A Operating Modes|280|COLOR=Maroon}} | ||
Though most Starfleet facilities carry out their duties without difficulty, Starfleet regulations detail a variety of operating modes for dealing with special situations, as well as the procedures to follow in each. Normal flight and mission operations of the Apollo-A are conducted | Though most Starfleet facilities carry out their duties without difficulty, Starfleet regulations detail a variety of operating modes for dealing with special situations, as well as the procedures to follow in each. Normal flight and mission operations of the Apollo-A are conducted per a variety of operating rules, determined by the current operating mode of the Ship. These operating modes are specified by the Commanding Officer, although in certain cases the computer can initiate Alert status upon detection of a potentially critical situation and any senior officers on the ship can change or call the alerts. | ||
{{Sub-Heading|black|Cruise Mode}} | {{Sub-Heading|black|Cruise Mode}} | ||
Cruise Mode refers to the normal operating condition of the spacecraft. | |||
{{Sub-Heading|yellow|Yellow Alert}} | {{Sub-Heading|yellow|Yellow Alert}} | ||
A yellow alert or condition yellow was the second highest alert signal status on Starfleet vessels and starbases, one stage below red alert. It designated a ship-wide state of increased preparedness for possible crisis situations. | A yellow alert or condition yellow was the second highest alert signal status on Starfleet vessels and starbases, one stage below red alert. It designated a ship-wide state of increased preparedness for possible crisis situations. | ||
In this status, a ship's defence fields | In this status, a ship's defence fields are energised, and the deflector shields are brought to full power, but the weapons systems remained off-line. | ||
A yellow alert could either be activated manually by the commanding officer in preparation for a tactical or environmentally hazardous situation, or automatically upon detection of a Proximity alert or Perimeter alert, or upon detection of certain system malfunctions. If the situation escalated, the commanding officer or the main computer would order a red alert. | A yellow alert could either be activated manually by the commanding officer in preparation for a tactical or environmentally hazardous situation, or automatically upon detection of a Proximity alert or Perimeter alert, or upon detection of certain system malfunctions. If the situation escalated, the commanding officer or the main computer would order a red alert. | ||
{{Sub-Heading|red|Red Alert}} | {{Sub-Heading|red|Red Alert}} | ||
A Red Alert (also condition red or code red or general quarters) is the highest emergency alert on a Starfleet starship. | |||
The red alert could also be ordered during various other emergency situations, such as a ship being boarded, radiation exposure, a security alert, massive systems failure, an imminent warp core breach, and | When Red Alert is called, a loud warning klaxon begins blaring, accompanied by flashing red warning lights. All Starfleet personnel are required to report to duty stations — even those who were sleeping at the time. In addition to this, there are some things that occur once a red alert is sounded: | ||
*The ship's weapons - phasers and photon torpedoes/Quantum torpedoes - are brought to ready status. | |||
*All crew members are to report to duty, whether that be their primary duty station or a secondary duty station within five minutes. Those crew members asleep at the time are to report to duty within fifteen minutes. | |||
*Secondary stations can include medical duty. On larger ships, a good portion of the crew receives training as medical technicians. Much of the crew is used as "damage control", where the crewmembers presumably help to fix minor damage to the ship and perform basic engineering tasks, under the direction of the primary engineering team. | |||
*The deflector shields are brought to full power and raised. | |||
*On starships that can separate the saucer section, the crew prepares for possible separation. | |||
*Backup crews for the main bridge standby in the event separation is called for. | |||
*Crews for the battle bridge also go on standby status in case separation is called for. | |||
*The non-essential crew and other individuals (such as civilians and mission specialists) are moved to the saucer section. | |||
*The security division also makes some preparations. | |||
*They make sure escape pods access ways are clear so that if crewmembers and civilians need to evacuate the starship, they can get to the escape pods without any interruption. | |||
*Security teams are stationed at key areas throughout the ship. | |||
*Sensors record and track the locations of all individuals aboard the ship. This is used to determine if unauthorised access by an intruder occurs. (The ship's computer also helps with this function) | |||
*All security teams are placed on standby status. | |||
The red alert could also be ordered during various other emergency situations, such as a ship being boarded, radiation exposure, a security alert, massive systems failure, an imminent warp core breach, and evacuation order, among others. | |||
A red alert could either be activated manually by the commanding officer, the officer in charge or senior officer or automatically, as when a ship was attacked or entered a dangerous area, etc. | A red alert could either be activated manually by the commanding officer, the officer in charge or senior officer or automatically, as when a ship was attacked or entered a dangerous area, etc. | ||
| Line 55: | Line 70: | ||
*Food replicator was not used, and emergency rations were distributed | *Food replicator was not used, and emergency rations were distributed | ||
*Holodeck or holosuite usage was terminated | *Holodeck or holosuite usage was terminated | ||
*The recycling of non-essential items, which could be broken down into raw matter patterns by the replicator, was commonly practised. Preserving the replicator for | *The recycling of non-essential items, which could be broken down into raw matter patterns by the replicator, was commonly practised. Preserving the replicator for use only during critical situations (such as replicating repair tools, medicine, etc.) could help extend the energy resources of the ship. | ||
Starships were often forced into this condition, due to tactical situations or spatial phenomena, which can also coincide with a red alert. | Starships were often forced into this condition, due to tactical situations or spatial phenomena, which can also coincide with a red alert. | ||
| Line 75: | Line 90: | ||
{{Sub-Heading|black|Standby alert}} | {{Sub-Heading|black|Standby alert}} | ||
A standby alert was a type of alert signal used to prepare a starship against possible threats. | A standby alert was a type of alert signal used to prepare a starship against possible threats. | ||
{{Sub-Heading|black|Decompression Alert}} | |||
Decompression Alert is usually declared when the computer of a starship, using internal sensors, detects decompressions on a deck of a starship. This alarm usually sounds when there is a hull breach. The computer usually will alert the bridge of decompression and tell them the deck; it is then the bridge crew's responsibility to evacuate those decks. | |||
{{Sub-Heading|red|Ultimate code}} | |||
The ultimate code or ultimate override was a distress call signal in use in the United Federation of Planets that overrode all other communications and missions of a Starfleet starship and required them to respond. | |||
The code was so highly classified that starship commanding officers were forbidden to submit an ultimate code to the computer for decoding. Instead, commanders had to memorise a key which allowed them to decode the message into a coherent form. Nor could the starship commander keep a computer record of the code. | |||
The ultimate code was only to be used in the most extreme of circumstances. This included an attack by an alien force, a disaster, or an unforeseen scientific development, and also a provision for a danger that had not yet been anticipated. Misuse of the ultimate code was a crime in the Federation. Starships operating under the ultimate code were required to observe radio silence and were expected to approach at battle stations. | |||