Memory Alpha
Register
Memory Alpha
m (grammar, punctuation, spelling, - duplicate link(s), formatting)
m (Bot: Automated text replacement (-\*{{[Ww]ikipedia +* {{wikipedia) !!wikia-credits fix!!)
Line 35: Line 35:
   
 
== External link ==
 
== External link ==
*{{wikipedia|Damage control}}
+
* {{wikipedia|Damage control}}
   
 
[[Category:Groups]]
 
[[Category:Groups]]

Revision as of 16:46, 29 November 2010

A damage control team (sometimes called a damage control party, repair crew, or work crew) referred to groups of Federation and Klingon starship crew organized as an adjunct to the ship's engineering staff for use in times of crisis when the ship suffered damage. Their general purpose was to fight fires and/or effect repairs as needed to keep the ship operational.

Members of damage control teams aboard Federation vessels were drawn from all three ship's divisions: Command, Sciences, and Operations.

Emergency life support and damage control systems were usually related. (DS9: "The Changing Face of Evil")

23rd century Federation starships often had a specific bridge station dedicated to coordinating damage control efforts.

Production notes and other background materials tell us about the designated damage control station on the bridges of the Template:ShipClass starship pre- and post-refit.

In 2267, Captain James T. Kirk led a boarding party including a damage control team to the wrecked USS Constellation following its encounter with the "planet killer". (TOS: "The Doomsday Machine")

In 2285, the then-Admiral Kirk and Captain Spock consulted the USS Enterprise's damage control station readouts following Khan's sneak attack in 2285. (Star Trek II: The Wrath of Khan)

In 2366, an alternate universe Geordi La Forge coordinated several damage control teams that boarded the crippled USS Enterprise-C, which had been damaged in combat with the Romulans. (TNG: "Yesterday's Enterprise")

On stardate 46154.2, a damage control team and a medical team aboard the USS Enterprise-D were ordered by La Forge to report to Cargo Bay 4 when a massive EPS explosion was detected in the area. (TNG: "Schisms")

When Captain Edward Jellico temporarily took command of the Enterprise-D on stardate 46361, he had the Science I and Science II stations on the bridge changed to Damage Control and Weapons Status. (TNG: "Chain of Command, Part I")

In 2369 the repair crew aboard Deep Space 9, including Lieutenant Jones and Chief Miles O'Brien, tried to free three Federation passengers from a malfunctioning airlock. (DS9: "Babel")

The same year the repair crews of Deep Space 9 were immediately responding to the hull breaches caused by graviton impulses of the embryonic lifeform. (DS9: "Q-Less")

During the absence of Chief Miles O'Brien in 2369 Julian Bashir joked that they should call a Romulan repair service to fix the technological problems which occurred. (DS9: "Dax")

Commander Benjamin Sisko told his son Jake that he had to perform damage control after he was informed that his son learned all about women from the Ferengi boy Nog. (DS9: "Move Along Home")

Constable Odo mentioned work crew seven as the team which did the repairs to Quark's damaged holosuites and when the Ferengi tried to trade information about the mission of a Klingon crew which previously visited his bar, Odo told him that he could use work crew seven for minor repairs in his security office. As a result, Quark told Odo what he knew about the Klingon mission. (DS9: "Dramatis Personae")

The following year, damage control parties were placed on stand-by when the Enterprise-D was preparing to enter a subspace rift to rescue the crew of the USS Fleming. (TNG: "Force of Nature")

Damage control teams were also frequently mentioned in "background chatter" and/or dialog in various episodes of the different series.
Real-life naval damage control teams are made up from the members of the ship's crew who do not already have vital duty assignments in a combat situation.
This article or section is incompleteThis page is marked as lacking essential detail, and needs attention. Information regarding expansion requirements may be found on the article's talk page. Feel free to edit this page to assist with this expansion.

External link