Skip to main content

What are all the types of colored alerts in Star Trek and what do they do?


What technically happens on a ship when a colored alert is called? For example, I recall hearing/seeing long ago (TNG Tech Manual?) that shields are automatically raised under both red and yellow alerts. The colored alerts I am aware of in canon are:



  • Double Red Alert (some sort of craziness in an episode of TOS)


  • Red Alert

  • Yellow Alert

  • Blue Alert (planetary landings---VOY)


If there are other colored alerts that I'm missing, please describe those as well. Additional EU examples, if any, are acceptable, but please identify them as such.



Answer



There are three official "Alerts" in Star Trek: Red, Yellow, and Blue. There are two additional "Operational Modes", Green and Grey. Finally, there's "Double Red Alert" which happens exactly once in TOS.


Condition Green


"Condition Green" is standard operating condition on a starship, with power distribution and generation on full, non-critical activities allowed, with requests for additional resources routed through Ops. Most episodes of Star Trek spend most of their time in "Condition Green" and it's not really seen on screen. The closest you will get is in Star Trek 3, on the bridge of the Excelsior, the light for "Situation Normal" is green.


The two battle conditions escalate in preparedness.



Yellow Alert


Yellow Alert automatically energizes the shields but not the weapons systems. It brings all tactical sensors online, and alerts the current duty shift of a dangerous situation. Yellow Alert can be left in place over long periods of time. For example, when investigating an asteroid belt or the like. Unfortunately I don't have any canon references on hand.


Red Alert


Red Alert automatically energizes the shields and weapons systems, bringing all tactical sensors online, and alerts all shifts to go to battlestations (even people who may be currently sleeping, an interesting thing to think about when you see a ship casually throw itself into Red Alert). Impulse engines go to full power generation as well as the warp core; Structural Integrity and Inertial Control fields go to full power. Transporter rooms are fully staffed. Basically, everything on the ship is turned on except for non-critical power drains, and everyone is awakened and put into a duty situation.


(As a personal side note, I often joke that there's no point in Star Trek video games to ever operate in anything but Red Alert. You're often going into a battle situation even if the story acts like you are not going to, and the extra power generation is always helpful. In "real life", though, you have to be concerned with fuel consumption, crew fatigue (you just woke everyone up to run to fire control or damage control or whatever), and "cry wolf" effects on your crew (you want them at peak alertness, not weary from hours of Red Alert with nothing happening).)


The other side effects including the above for these alert modes can be found in the Star Trek TNG Technical Manual. Some of the "automatic" features of the alert levels are features starting with the Galaxy Class; for example, Kirk orders Yellow Alert when the Reliant approaches in Star Trek 2, yet the shields are down. In TNG, the shields would have gone straight up unless countermanded by an order. "Yellow Alert, Mr. Worf, but keep the shields down."


Blue Alert


"Blue Alert" or "Condition Blue" is used for any non-standard mode on a starship, and the exact effects of "Condition Blue" depend on that starship. For example, The USS Defiant's cloaking device activated "Condition Blue" on the Defiant, letting the crew know to keep electromagnetic emissions to a limited level, reducing various power modes to the engines, etc. According to the DS9 Invasion! novel, the Defiant could pipe it's waste heat into internal heat sinks to keep it's profile down. On the other hand, Voyager's "Condition Blue" involved landing cycles, as the ship was intended to land on planets as required.


Note that some things which may be considered "Condition Blue" never show up as such; saucer separation in TNG and the Multi-Vector Assault Mode in Voyager's Prometheus class could be considered "Condition Blue" modes, except they usually happened while already at Red Alert.


Double Red Alert



Ironically, there are two stories in TOS where "Double Red Alert" existed; the one story where it may have made sense had "Double Red Alert" edited out, while the one where it was unnecessary had it left in. In "Conscience of the King" Kirk orders a "Double Red Alert" when a phaser set on overload is discovered; the idea is that a "Double Red Alert" is a regular red alert, but immediate, decisive action is required. Frankly, a "Red Alert" with an "Evacuation Order" would have worked better. In the novelization of "Court Martial," the hangup point for the Court Martial was on if Kirk ejected the pod containing an officer BEFORE or AFTER "Double Red Alert" was called. The idea was that a ship going through an Ion Storm would already be at "Red Alert", so they needed something "More Important." The episode was re-written to simply use regular "Red Alert."


Condition Grey


Finally, "Condition Grey" is a low power mode that appears in Voyager's Year of Hell. Basically, everything that can be turned off is turned off, and strict recycling is enforced. The condition doesn't refer to specific warning lights but to the lower light levels on the ship involved. One problem I've always had with Voyager's "Condition Grey" is everyone feeding their personal objects into replicators for "Recycling." Replication is very power intensive, and the "breakdown" process isn't any less power intensive than the "construction" process. According to the TNG technical manual, waste is stored in tanks for reconstruction by the replicator, but Voyager implies that the items must be immediately broken down by Replicator, a vast waste of resources. (But then again, Voyager hasn't been known for it's logical application of the Star Trek universe rules).


Comments

Popular posts from this blog

Was the "pure soul" of Harry's what had really hurt Voldemort?

In the Order of the Phoenix, Voldemort possesses Harry, and it hurts. Greatly. I think that Dumbledore explained that it was because Voldemort's rotten soul was incapable of assimilating Harry's pure soul, that Voldemort didn't understand the love and friendship etc that Harry has in his heart. But, I think it was a lie. Remember that in Deathly Hallows, while looking for information regarding Horcruxes, it is discovered that it is in fact possible to merge a soul fragment back, but that the process was extremely painful. Now then, if Voldemort tried to possess Harry, and Harry had a fragment of Voldemort's soul, I think that it could have been the true cause of Voldemort's pain: the fact of having his soul so close of another fragment. I think that Dumbledore knew that fact, but had to lie to Harry because it was inappropriate to let him know that he had one of Voldemort's soul fragments at the moment. Is that right? Or was it truly the pure soul of Harry's...

languages - Do we ever see written English in the Star Wars films?

In Empire Strikes Back , we see a transcription of what R2's beeps and bloops mean, but it's not English (sorry for the low quality, it's from the 2004 DVDs): I'd assume it's what Basic looks like when written, but is there some point in the the Star Wars films we see written English instead? (This sort of spun off from a discussion in How do people understand astromech droids? .) Answer At one point there was English but it has been phased out in subsequent versions of the films. Chris Gould at DVD Active did a comparison of all versions of each of the Star Wars films, and in his comparison of Episode 4 , there are a couple of screenshots showing how the power gauge for the Death Star tractor beam was changed. I imagine there are probably more to be found in his other comparisons but I haven't got around to reading those yet.

star wars - What "exactly" happens when someone turns to the Dark Side?

When I saw the original Star Wars saga as a kid, the concept of the Dark Side imprinted in me was quite simple. You did a bad thing, so you're a bad person so you go to the Dark Side and keep doing bad things. Now, obviously this doesn't hold true in reality. In my mind it is perfectly reasonable for Luke to kill the Emperor and Vader and then just flee the Death Star and rejoin the Alliance. After all they are at war, those are enemy officers that have captured him and are taunting him by threatening with death of all loved ones and the whole operation was intended to kill the Emperor anyway. The same would hold true for Anakin. He could have killed Mace Windu to save the Chancellor and Padme but that doesn't mean he's going to then go mad and kill all Jedis including children. It doesn't add up from a merely psychological point of view. He had a set of objectives and that made him want to keep the Chancellor alive (quite valid by the way, Mace Windu is quite clums...

star trek - Warning regarding forward saucer section in Nemesis?

In Star Trek: Nemesis , just before the Enterprise rams into the Scimitar, Picard sends a text message from his captain's chair arm pad to Troi — who is manning the helm in lieu of the crewman who was just blown out through what was once the view screen — indicating that she should put full impulse on standby. (Literally, if you watch the scene closely, Troi's console prefaces the order with "TXT MSG" !) My question is: Did Picard also somehow warn crew members in the forward saucer section about what was about to happen? The ramming of the Scimitar was a heat of the moment decision. Considering that he also resorted to calling the auto-destruct sequence shortly after (which ended up being offline), he probably was of the mindset that any losses would be acceptable in order to hault Shinzon's march to Earth. Still, I'm curious. Answer The original script indicates that he called for the crew to " brace for impact ". Whether that call (or the comma...