star trek tng uss hood

Navigation menu

• Mission Logs
• Chronologies
• Library Computer

U.S.S. Hood NCC-42296

The Federation Starship Hood was an Excelsior class vessel commanded by Captain Robert DeSoto . Commander William Riker served as first officer aboard the Hood prior to his posting as first officer of the newly-commissioned U.S.S. Enterprise NCC-1701-D . [2]

On Stardate  41153.7 , the Hood dropped off a number of personnel at Farpoint Station for transfer to the Enterprise, including Riker. The Hood remained on station until after Admiral Leonard McCoy completed his visit to the new Enterprise. Afterward, the Hood transported McCoy back to Federation space. [2]

The Hood and the U.S.S. Merrimac NCC-61627 were dispatched to the Romulan Neutral Zone on SD 43463.7 when a Romulan defector, Alidar Jarok , warned that he had received information indicating that the Romulan Star Empire was planning to instigate a war with the Federation, though the information proved to be false. [3] The Enterprise was scheduled to join the Hood at Browder IV on SD 43714.1 , where the Hood was engaged in a terraforming mission. [4] On SD 43779.3 , the Hood rendezvoused with the Enterprise in the Hayashi system to deliver Tam Elbrun and orders to proceed to Beta Stromgren for an encounter with a living starship dubbed " Tin Man ." [5]

In 2367 , the Hood underwent a major system upgrade at Starbase 174 . [1] During the Dominion War , the Hood fought in the Battle of Chin'toka in 2374 as part of a combined allied fleet. [6]

Ships Named Hood

• Prime Timeline

U.S.S. Hood NCC-1703 ( Constitution class )  •  U.S.S. Hood NCC-42296 ( Excelsior class )

FASA Timeline

U.S.S. Hood NCC-1703 ( Constitution class )  •  U.S.S. Hood II NCC-1703 ( Enterprise class )  •  U.S.S. Hood II NCC-2017 ( Excelsior class )

Kelvin Timeline

U.S.S. Hood (Unknown class)

SFU Timeline

U.S.S. Hood NCC-1707 ( Constitution class )

Excelsior class vessels

U.S.S.  Agincourt NCC-38762  •  U.S.S.  Al-Batani NCC-42995  •  U.S.S.  Berlin NCC-14232  •  U.S.S.  Cairo NCC-42136  •  U.S.S.  Charleston NCC-42285  •  U.S.S.  Crazy Horse NCC-50446  •  U.S.S.  Crockett NCC-38955  •  U.S.S.  Enterprise NCC-1701-B  •  U.S.S.  Excelsior NCC-2000  •  U.S.S.  Farragut NCC-2582  •  U.S.S.  Fearless NCC-14598  •  U.S.S. Fredrickson NCC-42111  •  U.S.S.  Gorkon NCC-40512  •  U.S.S.  Grissom NCC-42857  •  U.S.S.  Hood NCC-42296  •  U.S.S.  Intrepid NCC-38907  •  U.S.S. Jackson  •  U.S.S.  Lakota NCC-42768  •  U.S.S.  Lexington NCC-14427  •  U.S.S.  Livingston NCC-34099  •  U.S.S.  Malinche NCC-38997  •  U.S.S.  Melbourne NCC-62043  •  U.S.S.  Okinawa NCC-13958  •  U.S.S.  Repulse NCC-2544  •  U.S.S.  Roosevelt NCC-2573  •  U.S.S.  Tecumseh NCC-14934  •  U.S.S. Thunderer  •  U.S.S.  Valley Forge NCC-43305

U.S.S.  Achilles NCC-2011  •  U.S.S.  Agincourt NCC-2014  •  U.S.S.  Ajax NCC-2010  •  U.S.S.  Alamo NCC-2035  •  U.S.S.  Aquila NCC-2028  •  U.S.S.  Arizona NCC-2012  •  U.S.S.  Bearn NCC-2027  •  U.S.S.  Brisbane NCC-2030  •  U.S.S.  Challenger NCC-2023  •  U.S.S.  Chikuma NCC-2008  •  U.S.S.  Columbia NCC-2002  •  U.S.S.  Constitution NCC-2025  •  U.S.S.  de Mayo NCC-2029  •  U.S.S.  Eagle NCC-2031  •  U.S.S.  Enterprise NCC-1701-B  •  U.S.S.  Excalibur NCC-2004  •  U.S.S.  Excelsior NX-2000  •  U.S.S.  Exeter NCC-2016  •  U.S.S.  Fearless NCC-2036  •  U.S.S.  Fuso NCC-2019  •  U.S.S.  Galacta NCC-2003  •  U.S.S.  Hancock NCC-2006  •  U.S.S.  Hood NCC-2017  •  U.S.S.  Intrepid NCC-2020  •  U.S.S.  Kitty Hawk NCC-2007  •  U.S.S.  Kongo NCC-2009  •  U.S.S.  Lexington NCC-2026  •  U.S.S.  Potemkin NCC-2005  •  U.S.S.  Proxima NCC-2001  •  U.S.S.  Royal Oak NCC-2013  •  U.S.S.  Ryujo NCC-2022  •  U.S.S.  Sussex NCC-2024  •  U.S.S. Thunderer NCC-2032  •  U.S.S.  Ticonderoga NCC-2034  •  U.S.S.  Valiant NCC-2018  •  U.S.S.  Yamashiro NCC-2015  •  U.S.S.  Yorktown NCC-2033

SFC Timeline

U.S.S. Berlin NCC-14232  •  U.S.S. Cairo NCC-42136  •  U.S.S. Charleston NCC-42285  •  U.S.S. Crazy Horse NCC-50446  •  U.S.S. Crockett NCC-38955  •  U.S.S. Excelsior NX-2000  •  U.S.S. Fearless NCC-14598  •  U.S.S. Hood NCC-42296  •  U.S.S. Intrepid NCC-38907  •  U.S.S. Livingston NCC-34099  •  U.S.S. Melbourne NCC-62043  •  U.S.S. Potemkin NCC-18253  •  U.S.S. Repulse NCC-2544  •  U.S.S. Roma NCC-2010

Mirror Universe

I.S.S.  Excelsior NCC-2000

Myriad Universes

U.S.S.  Excelsior NCC-2000  •  U.S.S.  Potemkin NCC-18253

Notes and References

• ↑ 1.0 1.1 Roddenberry, Gene et al (Executive Producers). "Brothers" . Star Trek: The Next Generation , season 4, episode 4 (Production number 177). Directed by Robert Bowman . Written by Rick Berman . Paramount Pictures . 8 October 1990 .
• ↑ 2.0 2.1 Roddenberry, Gene (Executive Producer). "Encounter at Farpoint" . Star Trek: The Next Generation , season 1, episode 1-2 (Production number 101-102). Co-Executive Producers: Rick Berman & Maurice Hurley . Directed by Corey Allen . Written by D.C. Fontana & Gene Roddenberry . Paramount Pictures . 28 September 1987 .
• ↑ Roddenberry, Gene & Rick Berman (Executive Producers). "The Defector" . Star Trek: The Next Generation , season 3, episode 10 (Production number 158). Co-Executive Producer: Michael Piller . Directed by Robert Scheerer . Written by Ronald D. Moore . Paramount Pictures . 1 January 1990 .
• ↑ Roddenberry, Gene & Rick Berman (Executive Producers). "Allegiance" . Star Trek: The Next Generation , season 3, episode 16 (Production number 166). Co-Executive Producer: Michael Piller . Directed by Winrich Kolbe . Written by Richard Manning & Hans Beimler . Paramount Pictures . 26 March 1990 .
• ↑ Roddenberry, Gene & Rick Berman (Executive Producers). "Tin Man" . Star Trek: The Next Generation , season 3, episode 15 (Production number 168). Co-Executive Producer: Michael Piller . Directed by Robert Scheerer . Written by Dennis Putman Bailey & DAvid Bischoff . Paramount Pictures . 23 April 1990 .
• ↑ Berman, Rick & Ira Steven Behr (Executive Producers). "Tears of the Prophets" . Star Trek: Deep Space Nine , season 6, episode 26 (Production number 550). Directed by Allan Kroeker . Written by Ira Steven Behr & Hans Beimler . Paramount Pictures . 15 June 1998 .
• Ships & Vehicles
• Starfleet Vessels
• Ships by Registry
• Privacy policy
• About Trekipedia
• Disclaimers
• Login / Create Account

• More to Explore
• Series & Movies

Published Aug 26, 2014

Celebrating The Ships of The Line: The USS Hood (NCC-1703)

The USS Hood (NCC-1703) was a lady without much luck. The 23rd century Constitution-class starship took a beating during a M-5 battle simulation when the computer-controlled USS Enterprise fired upon her. The event occurred in 2268, as the Hood, Enterprise, Lexington, Excalibur and Potemkin engaged in war games, only to have the games turn dangerously real when the Enterprise -- testing Dr. Richard Daystrom's M-5 multitronic computer, which was programmed using his own mental patterns -- killed the crew of the Excalibur and fired upon the unshielded Hood with full force when the M-5 went beserk.

StarTrek.com 's look at the Hood continues our ongoing celebration of the Ships of the Line, which will carry on weekly until the end of the year. The latest in the bestselling Ships of the Line calendar series is available now; visit www.Amazon.com to purchase the 2015 Ships of the Line calendar. And if you're an artist or designer, be sure to enter the Ships of the Line Design Contest, currently under way, for a chance to have your art featured in the 2016 Ships of the Line calendar. Click HERE to enter.

Get Updates By Email

USS Hood (NCC-42296)

• Edit source
• View history

The USS Hood (NCC-42296) was an Excelsior -class starship in service during the 24th century under the command of Captain Robert DeSoto . ( Star Trek: The Next Generation , Star Trek: Deep Space Nine )

• 2.1 Star Trek: Pendragon
• 2.2 Star Trek: Liberty
• 2.3 Starfleet Command (RPG)
• 4 Background information
• 5 External links

History [ ]

Upon the start of the Dominion War , while on patrol of the Federation - Cardassian border, Hood came under attack. USS Baldwin was the closest ship available, and was able to retrieve the crew and escorted Hood back to Federation Territory. ( USS Baldwin : " The Find ") Captain DeSoto was subsequently given command of the new USS Edmund Fitzgerald and passed command of Hood to James Traficant . Kelly Petrelli was the ship's second officer. She moved over to the Edmund Fitzgerald as Captain DeSoto's new XO . ( USS Baldwin : " Wartime Productions ").

Lieutenant Commander Vern , the Chief Engineer of the USS Phoenix , was transferred to the Hood in 2374 , against his own personal preference. ( Star Trek: Phoenix-X : " The Tilonian System ")

The Hood played a part several in several campaigns, including, Operation Return , the first Battle of Chin'toka , and the operation to retake Betazed . The ship was a part of the Fifth Fleet 's 10th Wing. ( DS9 : " Favor the Bold ", " Sacrifice of Angels ", " Tears of the Prophets ", USS Baldwin : " Determined Warrior ")

The Hood undertook routine patrols in space held by Khan Noonien Singh in 2376 . During one of these patrols, Hood was struck by a subspace wave, requiring field assistance from the USS Baldwin . ( USS Baldwin : " Blue Clear Sky ")

The Hood also participated in the Battle of Sol against the Vendoth in 2376. ( Star Trek: Unity : " United We Stand - Together ")

By 2378 , the Hood was a part of the Starfleet Third Fleet , under the command of Admiral Christopher Truman , and played a big part in the Coalition War . In 2381 , the Hood participated in the Battle of Minark . ( Star Trek: Pioneer , "Torment and Woe" )

In 2379 , the Hood was part of a task force dispatched to intercept the Scimitar . ( Star Trek Nemesis )

In 2381 , the Hood responded to a distress call from Outpost 76 at Jengus IV . Her Captain, Murakami, resolved the situation and as a result the Hood left orbit, leaving the USS Cerritos and the USS Carlsbad to coordinate cleanup efforts and relocate the outpost. (Star Trek Lower Decks Season 3)

Alternate realities [ ]

Star trek: pendragon [ ].

In the Pendragon timeline , the Hood participated in Operation Return , an attempt to retake Earth during the Federation Civil War .

Star Trek: Liberty [ ]

In Star Trek: Liberty , Hood had been stranded behind enemy lines at the Dominion War 's outbreak. Hood would join other stranded allied vessels to form the Thirteenth Fleet . ( Star Trek: Liberty : " Tales of the 13th Fleet ")

Starfleet Command (RPG) [ ]

In the Starfleet Command (RPG) continuity, the Hood is a part of Task Group 10-2.

See also [ ]

Background information [ ].

• In a early version of the USS Baldwin story " The Find ", the Hood was severely damaged, requiring Baldwin to torpedo Hood and leading to DeSoto being given command of the USS Edmund Fitzgerald . After later appearances in Star Trek: Deep Space Nine , the story was rewritten to salvage the ship, but DeSoto's reassignment, and the Edmund Fitzgerald , were kept.

External links [ ]

• USS Hood (Excelsior class) article at Memory Alpha , the canon Star Trek wiki.
• USS Hood (NCC-42296) article at Memory Beta , the non-canon Star Trek wiki.
• 1 USS Enterprise (NCC-1701-H) (Endurance class)
• 2 USS Enterprise (NCC-1701-G) (Excalibur class)
• 3 USS Phoenix (NCC-65420-X)

• Show Spoilers
• Night Vision
• Sticky Header
• Highlight Links

Follow TV Tropes

http://tvtropes.org/pmwiki/pmwiki.php/Recap/StarTrekTheNextGenerationS3E20TinMan

Recap / Star Trek: The Next Generation S3E20 "Tin Man"

Edit locked.

Original air date: April 23, 1990

While on a routine assignment, the Enterprise is suddenly approached by the USS Hood , captained by an old comrade of Picard's (who also happens to be Riker's former CO, as established back in "Encounter at Farpoint") who informs him that the Enterprise has received new top-secret orders involving a time-critical mission. Due to security concerns, they will be briefed by the Betazoid mission specialist, Tam Elbrun. Riker immediately bristles at the name due to Tam Elbrun's involvement in the " Ghorusda Disaster ," which resulted in the deaths of 47 Starfleet personnel, including two of Riker's former classmates. Troi knows Tam from her university days and reveals that he was once one of her patients, which does not sit well with the rest of the crew.

Tam is a gifted telepath even by Betazoid standards. Brusque and aloof, he skips to the end of every conversational exchange using his telepathy "to save time" and unceremoniously hands Picard his orders. He's much more friendly to Troi, however, but he's even more fascinated by Data. As someone whose mind he cannot read, Data offers him a unique opportunity to get to know someone. That said, he urges the crew to convene in 15 minutes for his briefing.

Tam explains that 23 parsecs beyond any previous manned mission, deep in the Beta Stromgren system, a life form code-named "Tin Man" has been discovered orbiting a collapsing star, but all subspace attempts at communications have failed. Tam, as Starfleet's top expert in first contact with unknown life-forms, will attempt to telepathically communicate with it. Complicating matters is the fact that Tin Man is in a sector claimed by the Romulan Empire, which has sent their own ships in an attempt to get to Tin Man first, making this a race. At the end of the meeting, Tam confronts Riker about his bitter feelings over Ghorusda, but Riker is unmoved.

En route to Beta Stromgren, Picard holds a meeting with Crusher and Troi over his concerns about Tam's stability. Troi explains that Tam was born telepathic, which is unusual for a Betazoid and means he cannot turn it off at will. His unusually powerful abilities cause him to be constantly bombarded with other people's thoughts. In spite of the therapy he receives to cope, he's become a miserable recluse. Later, Tam vents to Troi about his issues and lets slip that he's already been in mental contact with Tin Man, which is why he's volunteered for this assignment against his natural inclination.

The ship's sensors have been picking up a weird "echo" matching their speed and course. At 18 minutes away from Beta Stromgren, the echo reveals itself to be a cloaked Romulan Warbird, which cripples the Enterprise as it passes. Tam reads the enemy captain's mind and reveals that the attack was solely to delay the Enterprise and get to Tin Man first. The gambit works: Picard orders that they repair their shields before continuing, surrendering first contact to the Romulans.

In the mean time, Tam visits Data, who's using the opportunity to study Tin Man further, He says that Tin Man is probably a Living Ship but lacks a crew. He wonders whether Tin Man was bred for that purpose or if it adapted itself to serve a purpose. Tam and Data then get philosophical about the purpose of anyone's life, organic or android. Tam shows great respect for Data and assures him that, even though he can't read his mind, his thoughts are no less valid than anyone else's.

When the ship finally reaches Tin Man, the Warbird is preparing to arm its weapons again. Tam realizes that they're going to destroy Tin Man to deny it to the Federation . Tan reaches his mind out to Tin Man to warn it, and it releases a pulse of energy that obliterates the Warbird and damages the Enterprise . Confronted by Picard over his actions, Tam admits that he's been in stronger contact with Tin Man than he'd admitted. Its real name is Gomtuu, and it's the Last of His Kind . It journeyed to the dying star to commit suicide. Tam claims the only way to stop Gomtuu from killing itself is to go inside it. Troi is worried that Tam is losing himself in the merger of minds, so Data volunteers to go along with Tam to "anchor" him.

Data and Tam beam aboard Gomtuu. After a moment of distress, Tam claims Gomtuu has told him the story of his entire existence. He claims the crew and Gomtuu existed in a symbiotic relationship, hence Gomtuu's anguish at their loss. "Is that the purpose of existence? To care for someone?" asks Data. Tam says it is for him—and he doesn't plan on leaving. Tam will fulfill the mission by taking the crew's place and giving Gomtuu a reason to live again. Meanwhile Gomtuu will also save Tam: he is now finally free of the deluge of thoughts that plagued him through his life. Only Gomtuu speaks to him now.

Meanwhile, the other Romulan Warbird has arrived and plans to destroy Gomtuu in retaliation for the other ship. However, Gomtuu, now merged with Tam, produces another wave that safely pushes both the Enterprise and the Warbird several billion kilometers away, just in time to witness the sun go supernova. A shocked Picard calls out for Data... who is immediately beamed safe and sound aboard the bridge.

This episode contains examples of the following tropes:

• Artistic License – Medicine : Deanna matter-of-factly reveals to the crew that their next mission specialist is a former patient of hers and later on essentially reveals said patient’s entire medical history to the entire senior staff. By present-day ethical standards around confidentiality and dual roles, that would be a severe no-no.
• Blessed with Suck : Tam's telepathy is extraordinary even by Betazoid standards. He can learn everything there is to know about a person simply by being near them, read the minds of people on other starships with ease, and is constantly aware of everyone around him. Which is the part that sucks. He can't turn it off, and therefore has severe socialization issues and exhibits schizophrenia-like symptoms, except that the voices in his head are the actual thoughts of the people in his proximity.
• Boring, but Practical : Discussed by Captain DeSoto, albeit in a jovial way. The Enterprise gets the high risk assignment of getting Tam to Gomtuu, but it was the Hood , an old Excelsior -class, that got Tam to the Enterprise in the first place, saving valuable time. DeSoto : Ah, well, you know, they send you Galaxy -class boys out here to the far reaches. Me, I just haul my butt back and forth between starbases.
• Call-Back : Data's painting appears to be of the time vortex from " Time Squared ."
• Contacting Gomtuu before the Federation could was so important for the Romulans that they burned out the warp coils of their ship overclocking their engines in order to keep up with the Enterprise .
• In order to get shields, La Forge has to redirect power from the structural integrity field, overriding the computer's warnings.
• In order to keep the Romulans from destroying Tin Man, Tam merges his mind with it and convinces it to defend itself. As a result of coming into direct contact with it, his brain goes into a brief seizure/fugue state and he's swept up in its despair.
• Desperately Looking for a Purpose in Life : After Gomtuu lost its crew in a radiation disaster, it wandered aimlessly with no reason to exist and no companions, eventually reaching a Despair Event Horizon and deciding to commit suicide at Beta Stromgren. Thankfully, merging with Tam gives it a crew and a purpose once more.
• Didn't Think This Through : Tam warns Gomtuu, whose telepathy demonstrates it to be extremely powerful, of danger without considering the safety of the ship he's on himself. The Enterprise is severely damaged as a result.
• Dolled-Up Installment : It's based on the non- Star Trek novel, Tin Woodman by Dennis Putman Bailey and David Bischoff.
• Driven to Suicide : Gomtuu, at the beginning of the episode, is attempting to commit suicide by supernova due to the loss of its crew. Tam's arrival gives it new purpose.
• "Eureka!" Moment : Before they know anything about Gomtuu besides it's location and appearance, Tam mentions how much he empathizes with it, a great intelligence lonely for so long. Troi realizes that the only way he could know the ship is independently intelligent is if he's in telepathic contact with it.
• Explosive Overclocking : The first Romulan warbird overloads their engines to beat the Enterprise to Beta Stromgren, but the damage done to them means they wouldn't be able to return to Romulan space.
• Famed In-Story : Tam Elbrun is regarded as the Federation's finest expert in First Contact with new lifeforms. Unfortunately, he's also rather infamous within Starfleet for his screw up with the Ghorusdans.
• Godzilla Threshold : Although Picard is suspicious of Tam Elbrun's judgement and Tin Man's power the threat of a Romulan attack against the damaged Enterprise leads him to agree to Tam's plan to physically transport to Gomtuu.
• If I Can't Have You… : The Romulans have been ordered to make contact with Tin Man/Gomtuu, and if they can't, to destroy it in order to deny it to the Federation.
• Jerk with a Heart of Gold : Tam. Being bombarded with others' thoughts all his life hasn't done his sanity any favors. He's much nicer to Deanna and Data, and he's certainly happy when he and his mind are alone with Gomtuu.
• Last of Its Kind : Gomtuu is speculated to be the only survivor of its species. After the death of its crew it traveled for thousands of years, never finding another of its kind.
• Line in the Sand : Even though the Enterprise is heavily damaged, Captain Picard refuses to just stand aside and let the Romulans destroy Tin Man.
• Living Emotional Crutch : When Tam boards Gomtuu, they become this for each other—Gomtuu can silence the cacophony of thoughts Tam is subjected to, and Tam gives it a "crew" again.
• Living Ship : Gomtuu. Its appearance was modeled after a peach pit.
• Loss of Identity : Deanna mentions that Tam may end up being lost in Gomtuu's mind if he comes into closer contact with it. When Tam does finally fully connect with the ship, he's more than happy to lose himself and find peace within.
• Tam Elbrun was born with his abilities active and on a level beyond other Betazoids, and thus has been assaulted by the thoughts of others since he was born. Even with early diagnosis and training, he never learned to shut them out properly. The stress sent him to hospitals throughout his life, and he mentions to Troi that the thoughts of the few thousand people on the Enterprise alone feels like a tide that might swallow him up.
• Merging minds with Gomtuu causes him to be nearly overwhelmed by its grief, nearly losing himself in it.
• Mind over Matter : Once joined with Tam, the pair send the Enterprise well away from the star as it goes supernova.
• Mood Whiplash : A Downplayed example compared to most others, but all levity in the opening conversation with Captain DeSoto vanishes when the name "Tam Elbrun" is mentioned. Riker: As in "Tam Elbrun" of the Ghorusda Disaster? DeSoto: The same. What can I say?
• My Skull Runneth Over : Gomtuu tries to convey its long, long lifetime of experiences to Tam all at once, and nearly kills him. Fortunately, they manage to adapt to each other.
• Never My Fault : Tam (and eventually Starfleet) blamed Captain Darson for what happened at Ghorusda, claiming that Darson didn't listen to his recommendations. Tam later admits that he may have been so caught up in the Ghorusdan race's minds and wanted everyone to get along so much that he neglected to warn Darson more forcefully.
• No MacGuffin, No Winner : The Romulans have orders to destroy Tin Man if they can't contact it rather than let the Federation have a go. In the end, Tin Man does leave for parts unknown.
• "No Rules" Racing : Happens as the Enterprise and the Warbird race to reach Tin Man, with the Romulans winning by attacking and disabling the Federation ship.
• No Social Skills : Tam. Due to his Power Incontinence he tends to respond to questions that aren't asked, or to criticisms that people don't say to his face.
• Power Incontinence : Tam is unable to control his telepathy, which causes him to be bombarded with people's thoughts 24/7. And seeing as his abilities are apparently powerful enough to sense a Romulan Captain's thoughts from a different ship passing by at a large fraction of the speed of light as well as to sense Tin Man's emotions from several days distance away at FTL speeds .
• Power-Strain Blackout : Tam blacks out after warning Gomtuu about the Romulan attack.
• Scenery Porn : The shot of Tin Man turning around suddenly, sending out the energy wave, was included in just about every ad for VHS episode collections early on, generally while the announcer was praising TNG's special effects.
• Scotty Time : Geordi says he needs 30 minutes to get some shield power back. Picard says, "You've got 10."
• Some Kind of Force Field : O'Brien says this when Gomtuu raises a shield, cutting off O'Brien's transporter lock on Data and Tam.
• Starfish Aliens : Tam is an expert at communicating with them, thanks to his telepathic gifts. Deanna notes that after his experiences on Ghorusda, he tended to choose assignments with non-humanoid races, as he found them easier to deal with than humanoids.
• Starship Luxurious : How Captain DeSoto describes the Enterprise . DeSoto: Will, you getting soft on that luxury liner?
• Stock Footage : Gomtuu's attack is taken from V'Ger's transformation at the end of Star Trek: The Motion Picture .
• Telepathic Spacemen : Tin Man broadcast its loneliness across light-years, but only Tam was a powerful enough telepath to pick it up. They've been in loose contact since, giving each other impressions.
• Teleportation : Gomtuu is capable of teleporting people across vast distances, and does so to put Data back on the Enterprise .
• Uncertain Doom : We never find out if Tam and Gomtuu survived the supernova explosion or not; the episode doesn't even give enough information to know if Gomtuu has the capability to outrun the explosion or not. It may have performed a Heroic Sacrifice to save the Enterprise and the second Warbird, or Tam's presence might have given it the will to live and save itself from the supernova.
• Wave-Motion Gun : Gomtuu, when convinced to defend itself by Tam, sends out a circular shockwave that immediately destroys a Romulan ship and nearly takes the Enterprise with it.
• What Happened to the Mouse? : As noted by Picard in his closing log entry, the fate of Tam, Gomtuu, and the second Romulan ship is a mystery.
• Star Trek: The Next Generation S3E19 "Captain's Holiday"
• Recap/Star Trek: The Next Generation
• Star Trek: The Next Generation S3E21 "Hollow Pursuits"

Important Links

• Action Adventure
• Commercials
• Crime & Punishment
• Professional Wrestling
• Speculative Fiction
• Sports Story
• Animation (Western)
• Music And Sound Effects
• Print Media
• Sequential Art
• Tabletop Games
• Applied Phlebotinum
• Characterization
• Characters As Device
• Narrative Devices
• British Telly
• The Contributors
• Creator Speak
• Derivative Works
• Laws And Formulas
• Show Business
• Split Personality
• Truth And Lies
• Truth In Television
• Fate And Prophecy
• Edit Reasons
• Isolated Pages
• Images List
• Recent Videos
• Crowner Activity
• Un-typed Pages
• Recent Page Type Changes
• Trope Entry
• Character Sheet
• Playing With
• Creating New Redirects
• Cross Wicking
• Tips for Editing
• Text Formatting Rules
• Handling Spoilers
• Administrivia
• Trope Repair Shop
• Image Pickin'

Advertisement:

Den of Geek

Revisiting Star Trek TNG: Tin Man

This week's Star Trek: TNG look-back comes to a trite, predictable episode that you're best off skipping...

• Share on Facebook (opens in a new tab)
• Share on Twitter (opens in a new tab)
• Share on Linkedin (opens in a new tab)
• Share on email (opens in a new tab)

This review contains spoilers.

3.20 Tin Man

The Enterprise’s mission is interrupted by the arrival of the USS Hood, which gives them a new assignment: take Tam Elbrun – a Betazoid emissary with hyper-acute telepathic abilities – into Romulan-claimed space so that he can make contact with an space-based entity known as the “Tin Man”. I’ll warn you, this sounds much more exciting than it turns out to be.

Elbrun associated with a famously botched first contact mission, which makes the crew uneasy. Especially Riker, whose friends died in the incident. It also transpires that Elbrun was one of Troi’s patients when she was studying psychiatry, so remember: everything that happens from this point on is partially her fault.

Ad – content continues below

The plan is for Elbrun to use his mind-powers to coax the Tin Man away from the star it’s orbiting, which is about to explode. Unfortunately, he’s barely-hinged and overwhelmed by the number of minds on the Enterprise. He snaps at Riker. He gets annoyed at Picard. And he punches a replicator in the face when it gives him lapsang instead of oolong (probably). He’s fascinated by Data, though, because he cannot read robo-minds.

Unfortunately, the Romulans have also noticed the Tin Man, and they’ve got the pedal to the metal trying to beat the Enterprise to it. Elbrun accidentally reveals that he’s already in psychic contact with the Tin Man, which he describes as “ancient and lonely”. So, if you’ve seen any science fiction ever, you can probably guess where this is going to end up.

Just as Riker and Picard are starting to realise that Elbrun is basically insane, a Romulan Warbird catches up with the Enterprise and a brief firefight ensues. The Enterprise is disabled and the Warbird speeds towards the Tin Man. Elbrun uses their psychic link to warn it, which makes it emit a huge burst of energy that destroys the warbird completely, and further damages the Enterprise. No-one is especially pleased about this, not least a huge number of Romulan families who are going to spend the rest of their lives wondering what happened to their relative.

Picard is annoyed at how Elbrun displayed no regard for the Enterprise’s safety and refuses to allow Elbrun more contact with the Tin Man until the ship is fixed. The continue to study the Tin Man from a distance, and Elbrun reveals that he knows more about it now. The being is known as Gomtuu (9 points in Scrabble) it used to be a living starship. It hasn’t encountered another of its kind in thousands of years, and it’s using the star’s supernova to commit suicide in a needlessly dramatic fashion (let it never be said that living starships don’t know how to make an exit).

Elbrun wants to be beamed to the entity, but Picard is understandably wary of this, given what happened last time Elbrun spoke to it. When a second warbird arrives, they basically force the issue and Data agrees to beam over with Elbrun as a chaperone. Once there, he realises that the ship misses its crew and is depressed over its lack of purpose in life. So Elbrun decides to give it one by being its sole occupant. The Tin Man flings the Enterprise and the Warbird out of the system and returns Data to the bridge before the pair fly off into the universe, the problem of Gomtuu’s loneliness and depression now solved forever. Wait, how long do Betazoids live for again?

TNG WTF: At least one Romulan ship is destroyed in this episode. That’s a lot of lives extinguished because they happened to turn up in the same sector as the Enterprise. Elbrun is notionally responsible, but the Federation lets him up and leave in a star-cucumber, never to be seen again. The Romulans seem awfully fine about this, and the destruction of their ship. How did it not result in interstellar war?!

TNG LOL: Elbrun arrives on a transfer from Starbase 123. Or Starbase Placeholder as it’s known in the writers room.

Get the best of Den of Geek delivered right to your inbox!

Who’s That Face?: Tam Elbrun? More like RICHARD WILKINS III, the mayor from Buffy. It’s fair to say he’s got a lot less to work with in TNG , since he’s playing Chump of the Week. I believe this gives that Harry Groener the distinction of being the only Star Trek actor to eat another Star Trek actor in another series (the Mayor eats Principal Snyder, aka Armin Shimerman/Quark). Although if you can prove me wrong on that front, please do.

Time Until Meeting: 7:23. They’ve barely even finished rolling the credits.

Captain’s Log: Here’s the big problem with this episode: you can guess the ending almost as soon as the basic set up is established. Here’s an emotionally disturbed telepath who specialises in contacting non-bipedal life and hates living with other people. Here’s a lonely space dart, built to be a starship but lacking a crew, depressed because it has nothing to live for. How could this POSSIBLY play out?

It doesn’t really help that Tam Elbun doesn’t seem like a remotely believable character. Who would willingly select this maniac for anything even approximating a delicate task? As established, Troi mentions that he was once her patient, and frankly, treatment is what he needs. If anyone else endangered the Enterprise that recklessly they’d be locked up!

Even if you forgive that, the episode doesn’t have a lot to do with the rest of the crew. There’s a lot of Geordi tweaking some minor settings in engineering while attempting to fix the ship, and those scenes feel like someone’s idea of what happens in Star Trek , rather than what actually happens in Star Trek . The final scene sort of brings it around to “Data learns that his home is on the Enterprise”, but that revelation doesn’t really spring out of the rest of the story, nor is it a question posed at any point prior to the final scenes. It’s easy to use Data as a way to give the episode the illusion of a point (ah, Data. Is there anything you can’t learn? Except how to use contractions, I mean.) but in this case it comes across as massively trite and worse still, tacked on.

Watch or Skip? Skip.

Read James’ look-back at the previous episode, Captain’s Holiday, here .

Follow our  Twitter feed for faster news and bad jokes right here . And be our  Facebook chum here .

Star Trek: 10 Best Starfleet Ships Of The 24th Century

These Starfleet ships of Star Trek's 24th century are some of the most memorable among fans.

Star Trek 's twenty-fourth century has been explored extensively in TV series, games, and books. This bounty of content results in the era being one of Star Trek 's most fleshed-out periods. From the Dominion War to Starfleet's accidental exploration of the Delta Quadrant , the twenty-fourth century saw some of the Federation's greatest challenges.

RELATED: Star Trek: Best Starfleet Medical Officers

Luckily for the Federation, the Starfleet ships of the twenty-fourth century were more than up to the task. The century saw Starfleet throwing away the rule book to develop dedicated warships, experimenting with slipstream drives, and rebuilding its forces after catastrophic losses. It wasn't just the people of the era who made history—so too did the ships they crewed.

10 USS Phoenix

The Nebula-class USS Phoenix (best known for its appearance in TNG 's "The Wounded") was under the command of Captain Benjamin Maxwell. Maxwell, a veteran of the Federation–Cardassian Wars, believed that his former enemies were planning to reopen hostilities. To preclude this, he began to attack Cardassian ships, necessitating the intervention of the USS Enterprise-D in 2367.

It is likely that the Phoenix would have been destroyed by the Enterprise if not for the intervention of Miles O'Brien. The Enterprise transporter chief had previously served under Captain Maxwell and was able to convince the rogue officer to surrender. Although Maxwell's methods were reckless, he was in fact right—the Cardassian Union was rearming, and would soon pose a major threat to the Federation.

Although starships like the USS Enterprise receive much of the credit for preserving the Federation, the contribution made by the dependable USS Hood should not be overlooked. In 2366, the Excelsior-class starship supported the Enterprise-D near the Romulan Neutral Zone. Two years later, it again joined the Enterprise to expose Romulan involvement in the Klingon Civil War.

RELATED: Star Trek: Best Episodes From Each Series

The Hood served in and survived the Dominion War, while in 2379 it formed part of a battle group designed to intercept the Scimitar, a powerful Reman warship . Although it existed in the background of the twenty-fourth century, the USS Hood nonetheless played a number of crucial roles.

8 USS Aventine

While the canon status of the USS Aventine is debatable, this Vesta-class starship represented an important technological breakthrough for the Federation. The starship, best known for its frequent appearances in the Star Trek Relaunch novels, carried an advanced slipstream drive, allowing it to travel many times faster than a regular vessel at warp .

Following the death of its captain in 2381, the Aventine was commanded by Ezri Dax. The ship joined the Enterprise-E and the Titan in finally ending the Borg threat. In later years, the Aventine was deployed to counter the Breen and other Federation enemies.

7 USS Titan

The Luna-class USS Titan was the first ship to be captained by William Riker , who took command in 2379. Although the starship's adventures were initially documented in the questionable canon Star Trek: Titan novels, the starship is likely best known to fans for its appearances in Star Trek: Lower Decks .

In 2380, the Titan assisted the USS Cerritos during an engagement with the Pakleds. It continued to defend the Federation from the Pakled threat in subsequent months. In 2381, the son of William Riker and Deanna Troi was born aboard the Titan.

6 USS Protostar

The experimental USS Protostar was intended to further explore the Delta Quadrant following the return of the USS Voyager in 2378. As such, it was put under the command of Captain Chakotay, who had served as Voyager's first officer . However, the expedition went poorly, and the ship was captured by the Vau N'Akat, who planned to use the vessel to spread a deadly weapon into Federation space.

The starship actually remained dormant until it was rediscovered in 2383. A group of prisoners used the Protostar to escape the planet on which they were being held, although its journey back to the Federation resulted in the Vau N'Akat's weapon infecting many Starfleet ships. The Protostar itself was destroyed in the fallout, but its design served as the foundation for a new class of starships.

5 USS Cerritos

Although the USS Cerritos was built to perform logistical operations for the Federation, the California-class proved that even Starfleet's lesser ships played a pivotal role in the alliance's survival. Under the command of Captain Carol Freeman, the Cerritos specialized in second contact missions—administrative check-ups on civilizations previously contacted by the Federation.

RELATED: Best Lighthearted Star Trek Storylines

Despite this less-than-exciting mission profile, the starship proved essential in discovering the Pakleds' growing strength in 2380. The following year, the Cerritos proved itself in battle against the advanced USS Aledo, an AI-powered starship designed by a rogue Starfleet admiral .

4 USS Enterprise-E

Commissioned following the destruction of the Enterprise-D in 2371, the Sovereign-class Enterprise-E was larger and more heavily armed than its predecessor. This armament proved necessary during an engagement with the Borg in 2373, during which the starship traveled over three centuries back in time.

Despite its strength, the Enterprise-E played a minimal role in the Dominion War of 2373 to 2375, although Captain Picard and his crew did intervene on behalf of the agrarian Ba'ku when the Federation Council attempted to relocate the species. Perhaps the Enterprise-E's most notable engagement was against the Scimitar in 2379, although it was heavily damaged during the battle.

3 USS Voyager

When the USS Voyager traveled to the Badlands to intercept a Maquis vessel in 2371, its crew could not imagine the fate that awaited them. Both the Intrepid-class starship and its prey were transported to the Delta Quadrant, and the two crews were forced to put their differences aside in order to make the 70,000-light-year journey home.

This seven-year journey saw Captain Janeway and her crew encounter many new alien races, including the Kazon and Species 8472 . The USS Voyager also regularly encountered the Borg, with one member of the collective joining the starship's crew. Voyager's legacy endured for centuries—the ship was still remembered, albeit inaccurately, by Kyrian historians in the year 3074.

2 USS Defiant

While the Dominion War involved many factions and was fought on several fronts, many of its key engagements involved a single ship: the USS Defiant. This experimental warship dispensed with Starfleet's standard doctrine. Rather than focusing on exploration or carrying civilians, the Defiant was built to combat the Borg—and later, of course, the Dominion.

RELATED: Best Starfleet Ships During The Dominion War

In 2371, the Defiant-class starship made first contact with the Dominion's Founders. In 2373, it joined a flotilla of Starfleet vessels in Sector 001 in an attempt to repel a Borg cube. The Defiant liberated the Deep Space Nine from Dominion forces in 2374 and participated in both battles for control of the Chin'toka system. However, it was destroyed by a Breen energy weapon during the second engagement.

1 USS Enterprise-D

The Enterprise-D was, without a doubt, one of the most significant vessels in Federation history. As well as making dozens of first contacts (including with the Borg and the Q Continuum ), the Galaxy -class starship carried out significant exploration and research during its time as the flagship of the Federation. Much of the starship's success can be attributed to its crew, including Captain Picard, Commander Riker, and Lieutenant Commander Data, key figures in Starfleet history.

Although it was extensively damaged over Veridian III in 2371, the Enterprise-D was partially rebuilt by Geordi La Forge at the Fleet Museum. This refitted vessel fought against the Borg in 2401, demonstrating that, despite its age, the Enterprise-D remained a legendary part of the Federation fleet.

MORE: Star Trek: Best Starfleet Ships Of The 23rd Century

Memory Beta, non-canon Star Trek Wiki

A friendly reminder regarding spoilers ! At present the expanded Trek universe is in a period of major upheaval with the continuations of Discovery and Prodigy , the advent of new eras in gaming with the Star Trek Adventures RPG , Star Trek: Infinite and Star Trek Online , as well as other post-57th Anniversary publications such as the ongoing IDW Star Trek comic and spin-off Star Trek: Defiant . Therefore, please be courteous to other users who may not be aware of current developments by using the {{ spoiler }}, {{ spoilers }} OR {{ majorspoiler }} tags when adding new information from sources less than six months old (even if it is minor info). Also, please do not include details in the summary bar when editing pages and do not anticipate making additions relating to sources not yet in release. THANK YOU

• Federation starships (Kelvin timeline)
• 23rd century Federation starships
• 2258 spacecraft losses
• Kelvin timeline starships

USS Hood (Kelvin timeline)

• View history

The USS Hood was a Federation starship in the Kelvin timeline .

• 1 Service History
• 2.1 Connections
• 2.2 External link

Service History [ ]

The Hood was part of a Federation fleet sent to investigate Vulcan in alternate reality 2258, while it was being attacked by the Romulan mining vessel Narada .

Upon arrival at Vulcan, the Hood , along with the rest of the fleet, except for the Enterprise , was destroyed. ( TOS novelization : Star Trek )

Appendices [ ]

Connections [ ], external link [ ].

• USS Hood (Kelvin timeline) article at Memory Alpha , the wiki for canon Star Trek .

8 Coolest Starships From Star Trek: The Next Generation

• The Galor-class cruiser introduced the brutal might of the Cardassian Union, setting itself apart with a fish-like design.
• The USS Pasteur, a hospital ship with a spherical hull, met a tragic end in a Klingon attack after being specialized for medical aid.
• The Borg cube, with its unique design, proved to be a terrifying opponent by easily defeating the Enterprise-D and annihilating Starfleet vessels.

Following the success of the Star Trek movies of the 1980s, the franchise returned to the small screen with The Next Generation , a sequel series set a century after the exploits of Captain Kirk. Under the command of the stoic Captain Jean-Luc Picard , the Enterprise -D continued Starfleet's mission to explore the galaxy, discovering a wide range of civilizations, scientific mysteries, and deadly new threats along the way.

Star Trek: The Next Generation's 'Skin of Evil' Explained

While The Next Generation favored philosophy and moral dilemmas over melodrama and technobabble, the series still delivered when it came to fascinating technology and innovative vessels. From the Enterprise -D itself to the rarely seen D'kora- class Ferengi Maurader, the show's seven seasons featured a bounty of notable starships.

Galor-class Cruiser

First appearance: "the wounded" (season 4, episode 12).

As well as being a showcase for tortured everyman Miles O'Brien , "The Wounded" introduces both the Cardassians and their iconic Galor -class cruisers. The fish-like shaping of the Galor -class (a design choice replicated in later Cardassian vessels) sets the starships of the Cardassian Union apart from other alien civilizations. However, despite its naturalistic appearance, the cruiser is a capable warship that serves as the backbone of the Cardassian military.

Indeed, while the Galor -class is less well known in popular culture than many ships from The Next Generation , it came to symbolize the brutal might of the Cardassian Union within both the series itself and in Deep Space Nine . The Cardassian cruiser may be something of a hidden gem, but it nonetheless deserves to be remembered as one of Star Trek 's coolest starships.

USS Pasteur

First appearance: "all good things..." (season 7, episodes 25 & 26).

Starfleet is no stranger to specialized starships: the USS Defiant seen in Deep Space Nine is a dedicated warship, while the USS Voyager , despite its heavy armament, is ostensibly a science vessel. Yet few Starfleet vessels are as practically focused as the USS Pasteur , an Olympic -class hospital ship under the command of Captain Beverly Crusher. In the alternate timeline glimpsed by Picard in "All Good Things", the Pasteur is assigned to help those suffering from Terrelian plague on Romulus.

Star Trek: 8 Best Book-Only Characters, Ranked

The Pasteur represents a radical departure from conventional Starfleet design doctrine , as the vessel's primary hull is spherical rather than saucer-shaped. This additional internal space no doubt provides additional room for laboratories, wards, and surgical theaters. Unfortunately, the Pastuer 's fate shows that no good deed goes unpunished, as it destroyed in a Klingon attack.

Ferengi Marauder

First appearance: "the last outpost" (season 1, episode 5).

"The Last Outpost" sees the Enterprise -D come face to face with a D'kora -class Ferengi Marauder. This multi-function vessel is capable of operating not only as a cargo ship (as per the Ferengi's mercantile ideology ) but also as a fearsome warship. Indeed, during the Enterprise- D's first encounter with a Ferengi Marauder, the alien vessel was able to greatly weaken the Galaxy -class starship's deflector shields using a powerful electromagnetic pulse.

The imposing D'kora -class would make several more appearances in The Next Generation and even cameoed in Voyager , albeit as a CGI recreation of the original model. Despite the prominence of the Ferengi in Deep Space Nine , this cruiser is absent from the groundbreaking series, perhaps suggesting that the Ferengi Alliance could only afford to field a few of these versatile vessels.

USS Jenolan

First appearance: "relics" (season 6, episode 4).

While attempting to respond to a distress signal from the USS Jenolan in "Relics", the Enterprise -D discovers the Sydney -class starship crash-landed on the surface of a massive Dyson sphere. Picard and his crew are 75 years late to the scene of the accident, but they are able to recover a survivor: Montgomery Scott of Captain Kirk's Enterprise , who has preserved himself in the starship's transporter pattern buffer.

However, there is more to the Jenolan than its celebrity captain. In terms of appearance, it is a deviation from the norm when it comes to Starfleet vessels, as it lacks a saucer section. That the Jenolan bears a passing resemblance to the Danube -class runabouts seen in Deep Space Nine should come as no surprise, as these auxiliary vessels were heavily influenced by the design of the Sydney -class transport.

Romulan Warbird

First appearance: "the neutral zone" (season 1, episode 26).

The D'deridex -class Romulan warbird makes its debut in the closing minutes of The Next Generation 's "The Neutral Zone". The Romulans aboard the mighty starship tell Picard and his crew that they mean business, and the sleek yet powerful design of their vessel only underlines their message. The D'deridex -class would go on to make many more appearances across the franchise, making it one of Star Trek 's most iconic villain ships.

Star Trek: Best Starships To Work On

One advantage of the Romulan warbird over its rivals is the fact that it is equipped with a cloaking device. This stealth technology, coupled with the D'deridex 's considerable firepower, makes it a dangerous threat in any military confrontation. As such, it makes sense that the starship is often deployed in intense military situations, such as during standoffs against the Enteprise -D and throughout Deep Space Nine 's Dominion War .

USS Enterprise-C

First appearance: "yesterday's enterprise" (season 3, episode 15).

Although various iterations of the Starship Enterprise play key roles throughout the Star Trek franchise, not every starship to bear the name is as prolific as The Next Generation 's Enterprise -D. Indeed, the Excelsior -class Enterprise -B makes only a brief cameo in 1994's Star Trek: Generations , while its successor, the Enterprise -C, only appears in the episode "Yesterday's Enterprise". However, despite its lack of screen-time, the Enterprise -C is involved in one of the most pivotal events in Federation history: the Battle of Narenda III.

The Ambassador -class vessel is destroyed protecting a Klingon colony from a Romulan sneak attack, impressing the Klingons and laying the groundwork for the Treaty of Alliance between the Federation and the Klingon Empire. While the Enterprise -C may resemble an awkward merging of Original Series and Next Generation aesthetics, its contribution to Federation history cannot be understated.

First Appearance: "Q Who" (Season 2, Episode 16)

The Borg are one of science fiction's most memorable villains, due in part to their relentless and single-minded push to assimilate other species. Yet much of the Borg's enduring appeal can be attributed to the excellent visual design of the Borg cube. Envisaged by writer Maurice Hurley and realized by designer Richard James, the iconic vessel is based on an architectural language that is entirely distinct from other Star Trek ships.

Star Trek: How Do Borg Nanoprobes Work?

However, the Borg cube is more than just an unusual design: it is also a terrifying opponent. The initial Borg cube seen in "Q Who" easily bests the Enterprise -D, while another cube annihilates a large flotilla of Starfleet vessels at the cataclysmic Battle of Wolf 359 in "The Best of Both Worlds". The Borg cube may look simple, but it has plenty of tricks up its sleeve.

USS Enterprise-D

First appearance: "encounter at farpoint" (season 1, episodes 1 & 2).

No discussion of The Next Generation can be complete without referring to the USS Enteprise -D, the starship that is as integral to the series as any of the show's characters. While earlier iterations of Star Trek toyed with the concept of the Enterprise as a living space as well as an exploratory vessel, The Next Generation fully embraces the idea with the Galaxy -class starship. Boasting schools, families, and a sizable civilian contingent, the ship is perhaps the best example of Gene Roddenberry's utopian future in practice—even if taking children on frequent military missions doesn't make a whole lot of sense .

As the hero ship of The Next Generation , the Enterprise -D plays a central role in shaping the Alpha and Beta Quadrants, whether through its amazing discoveries of a shared link between many of the galaxy's civilizations or its repeated battles against the Borg Collective. When it comes to Next Generation starships, the Enterprise -D is second to none.

Star Trek: The Next Generation

Release Date September 28, 1987

Genres Sci-Fi

Creator Gene Roddenberry

Number of Episodes 178

• View history

The USS Aries (NCC-45167) was a 24th century Federation Renaissance -class starship operated by Starfleet .

• 2.1 Background information
• 2.2 Apocrypha
• 2.3 External link

History [ ]

In 2365 , the captain of the Aries retired , and Starfleet Command chose William T. Riker to replace the captain. At the time, the Aries was in the Vega-Omicron sector , and had recently picked up indications of an intelligent lifeform , but nothing was yet confirmed. Riker was chosen, according to Jean-Luc Picard , " not for your military proficiency, but for your skill as an explorer and as a diplomat . "

At the time of the offer, the USS Enterprise -D was on a twelve- hour layover at Starbase Montgomery . During its layover, the ship received a civilian tactical advisor , Cmdr. Riker's father Kyle Riker , to brief Riker on the Aries' mission . Riker was later visited by Lieutenant Worf , who requested to join Riker aboard the Aries , if he took the posting. The first officer of the Aries was Commander Flaherty , an officer that Picard highly recommended for the mission to sector Vega-Omicron. Later, when Riker consulted Picard, Picard put the Aries mission in perspective to the Enterprise mission, describing it as " a relatively insignificant ship, in an obscure corner of the galaxy . But it will be your ship. " ( TNG : " The Icarus Factor ")

Ultimately, Riker turned down the position, for what he described as " Motivated self-interest. Right now, the best place for me to be is here. " ( TNG : " The Icarus Factor ") Later, when Riker told his transporter duplicate , Thomas, about turning down the offer for the Aries , Thomas inquired what their father thought of his decision, Will explained " he couldn't understand why I did it. " Thomas could not understand the decision either, stating, " for once he and I agree on something. " ( TNG : " Second Chances ")

In 2367 , the Aries was on a deep space exploration mission in Sector 21502 . The ship was named on the chart "Starfleet Operations-Sectors 21166-23079" on the Enterprise -D bridge . ( TNG : " Brothers " okudagram )

Later that year , former USS Victory Ensign Mendez served aboard the Aries . While under the effects of an exotic virus from Tarchannen III , she stole the shuttlepod Cousteau to return to that planet. ( TNG : " Identity Crisis ")

In 2368 , the Aries joined Captain Picard's fleet that blockaded the Klingon-Romulan border during the Klingon Civil War . The ship was one of twenty-three assembled for the fleet and was one of the seventeen chosen for the tachyon network . Identified by its name and registry number , the ship's position in the network was monitored from the Enterprise -D.

When the network was disrupted by a high- energy burst released by the Romulans , the net was no longer effective in a radius of ten million kilometers around the USS Sutherland . Subsequently, Picard ordered the fleet to proceed to Gamma Eridon at maximum warp , where the fleet would attempt to reestablish the net before the Romulans got there. ( TNG : " Redemption II " okudagram )

In 2369 , the Aries was on a deep space exploration mission to Sector 22846 . The ship was named on the chart "Starfleet Operations-Sectors 21538-23079" on the Enterprise -D observation lounge . ( TNG : " Chain Of Command, Part I " okudagram )

Later that year, the USS Aries was on a deep space exploration mission in Sector 21602 . The ship was named on the chart "Starfleet Operations - Sectors 21538-23079" that was on display in the ops aboard Relay Station 47 . ( TNG : " Aquiel " okudagram )

In 2370 , the Aries ' point of departure was Lilliput IX . The starship arrived at Deep Space 9 on stardate 47568.2. Aries was named on the Deep Space 9 arrival roster . ( DS9 : " Whispers " okudagram )

In 2379 , the Aries was assigned to Star Fleet Battle Group Omega , which was to rendezvous with the USS Enterprise -E when it was attempting to escape from Romulan territory and the Reman warbird Scimitar . The starship was named on the Battle Group Omega roster in the Enterprise -E bridge . ( Star Trek Nemesis okudagram )

In 2364 , of the anti-time past , the Aries was named on a Starship Mission Assignments chart in the observation lounge of the Enterprise -D. ( TNG : " All Good Things... ")

Appendices [ ]

Background information [ ].

According to the Star Trek Encyclopedia  (4th ed., vol. 1, p. 44), the Aries was named for the constellation of Aries ( Latin for " Ram ") and the PanAm moon landing shuttle Aries from the movie 2001: A Space Odyssey , which ferried Dr. Heywood R. Floyd to the Moon.

The class and registry were derived from the charts seen in "Brothers" and "Chain of Command, Part I". The registry was seen again in the tachyon detection grid, on the hull of the shuttlepod Cousteau , and in the list of starships from Star Trek: Nemesis . In the script for "The Icarus Factor", the ship was called the Ares . [1] This spelling was altered for the next mention of the ship, in "Redemption II", where the ship was called the Aries . The subtitles for "The Icarus Factor" on the TNG Season 2 Blu-ray release name the ship as the Ares .

In an internal list of starships, from 26 September 1990, the Aries was identified as a scout ship . [2]

In scene cut from " Chain Of Command, Part II " in which the Cardassians threatened to invade Minos Korva , the Aries , the Sutherland , and USS Berlin were dispatched to Sector 21527 to assist the Enterprise -D. However, because the ships were three days away, the Enterprise was forced to find an alternative means of preventing the invasion . [3]

Apocrypha [ ]

The Star Fleet Technical Manual by Franz Joseph listed a Hermes -class Aries with the registry of NCC-602. Many years after the publication of this technical manual, Mike Okuda assigned this registry to the USS Oberth in a starship status display for the movie Star Trek VI: The Undiscovered Country .

External link [ ]

• USS Aries at Memory Beta , the wiki for licensed Star Trek works
• 1 Abdullah bin al-Hussein

Screen Rant

Star trek: discovery’s enterprise crossover made 1 of burnham’s crew very happy.

One member of Star Trek: Discovery's crew loves Constitution Class starships and Disco meeting the USS Enterprise must have made him happy.

Warning: SPOILERS for Star Trek: Discovery Season 5, Episode 3 - "Jinaal"

• Lt. Commander Gen Rhys, Discovery's Chief Tactical Officer, revealed his love for 23rd-century Constitution Class starships.
• The USS Discovery fought alongside the Constitution Class USS Enterprise in Star Trek: Discovery season 2, which must have thrilled Rhys.
• Star Trek: Picard's Jack Crusher is also an admirer of Captain Kirk's Constitution Class USS Enterprise.

Star Trek: Discovery season 5 reveals one of the USS Discovery's crew was very happy when the USS Enterprise crossed over. In a shocking twist, the Starship Enterprise intercepted the USS Discovery in the final moments of Star Trek: Discovery season 1's finale. This opened the door for Captain Christopher Pike (Anson Mount) to take command of the USS Discovery in Star Trek: Discovery season 2. Pike, along with Number One (Rebecca Romijn) and Lieutenant Spock (Ethan Peck) proved to be so popular, that they received their own spinoff, which became Star Trek: Strange New Worlds.

In Star Trek: Discovery season 5, Captain Michael Burnham (Sonequa Martin-Green) and the USS Discovery have left their 23rd-century lives long behind. Now living in the year 3191, Burnham and Discovery are hot on the trail of the Progenitors' ancient technology that can create life , itself, which was discovered by Captain Jean-Luc Picard (Patrick Stewart) and the USS Enterprise-D in the 24th century of Star Trek: The Next Generation . Aboard the USS Discovery, Commander Rayner (Callum Keith Rennie) is under orders to get to know his new crew, which led to a revelation about Lt. Commander Gen Rhys (Patrick Kwok-Choon) and his love for Constitution Class starships.

Star Trek: Discovery Season 5 Returning Cast & New Character Guide

Star trek: discovery's gen rhys loves strange new worlds' uss enterprise, discovery teamed up with the enterprise in season 2.

During Lt. Commander Gen Rhys' extremely brief meeting with Commander Rayner in Star Trek: Discovery season 5, episode 3, "JInaal," he was asked to describe something personal in 20 words or less. The USS Discovery's Chief Tactical Officer revealed he loves Constitution Class starships. Rhys told Rayner and Lieutenant Sylvia Tilly (Mary Wiseman:

"I'm a real ship-head. Love the Crossfield, but something about the curves of a 23rd-century Constitution Class just gets me."

Rhys was the USS Discovery's Tactical Officer throughout Star Trek: Discovery season 2, and Gen must have secretly been thrilled when the Disco teamed up with the USS Enterprise . The classic Constitution Class Enterprise, NCC-1701, was kept out of the fighting during the Klingon War, but it saw plenty of action when it joined the Crossfield Class USS Discovery in the final battle against Control. Lt. Rhys, as he was ranked at that time, likely enjoyed being so close to the most legendary Constitution Class ship in Starfleet before Discovery jumped to the 32nd century.

Star Trek: Picard's Jack Crusher Also Loves The Constitution Class USS Enterprise

"all those perfectly clean retro lines.".

Long after Starfleet retired the 23rd century Constitution Class, the USS Enterprise found another admirer in the 25th century: Star Trek: Picard' s Jack Crusher (Ed Speleers). In Star Trek: Picard season 3, episode 6, "The Bounty," Jack confessed his love of Captain James T. Kirk's (William Shatner) USS Enterprise-A to Commander Seven of Nine (Jeri Ryan) when the USS Titan-A was docked at the Fleet Museum on Athan Prime :

"Well, this one's my personal favorite. Kirk's Enterprise. All those perfectly clean retro lines. Yep, I'm definitely a Constitution Class man."

The reverence Star Trek: Discovery and Star Trek: Picard have for the 23rd-century Constitution Class isn't surprising. The Starship Enterprise boasts an iconic design, and it's one of the most distinctive and unforgettable spaceships in pop culture. Star Trek has featured numerous beautiful starships, but the Crossfield Class USS Discovery and the Constitution Class USS Titan-A are essentially variants of the original USS Enterprise design . The 23rd century Constitution Class USS Enterprise is a true classic, and Lt. Commander Gen Rhys got to see it up close in Star Trek: Discovery seasons 1 and 2.

New episodes of Star Trek: Discovery season 5 stream Thursdays on Paramount+