Jammer's Review
Star Trek: The Next Generation
"Redemption, Part II"




Air date: 9/23/1991
Written by Ronald D. Moore
Directed by David Carson
Review by Jamahl Epsicokhan
TNG's fifth-season kickoff is an entertaining blend of the earnest and the absurd, highlighting the series at perhaps its most eclectically versatile — or tonally schizophrenic, depending on your point of view. With the Duras sisters making their bid against Gowron to take over the Klingon Empire — and the Romulans pulling strings behind the scenes — "Redemption II" rotates through a sprawling A/B/C-story structure.
We have energetic space opera in the form of boisterous Klingons engaging in glorious battle — and then drinking in the same hall in the evenings between engagements. Apparently civil war is a 9-to-5 job. (Amusing detail: arm-wrestling with knives thrown in for good measure.) We have a more grounded storyline where Data is put in command of a ship whose first officer does not think an android is capable of command. And we have the Enterprise on a mission to expose the Romulan involvement in the Duras' attempted takeover. Of course, the wild card here is the relative sci-fi soap opera that is the Sela situation.
Since they are all servicing the same plot, "Redemption II" finds an admirably workable balance between all of these pieces. For my money, the most engaging is Data's command story. While we've been down the road documenting the prejudices against Data before, this one is a suitably engaging retelling. Timothy Carhart as Lt. Cmdr. Christopher Hobson hits the right notes of a wrong-headed jackass whose public disrespect of Data should've landed him in the brig immediately, if not sooner. As always, Data's unflappable nature is the key here. He never gets emotional, although he raises his voice when deemed logically necessary.
As for the nature of the woman who looks exactly like Tasha Yar, that one is a little trickier. On the one hand, I appreciate the commitment of the writers in revealing Sela's backstory and the paradoxical implications that come with it, explicitly referencing "Yesterday's Enterprise" and bringing in Guinan to lend credence to the whole thing. If anything, the writers show a willingness to take a ridiculous idea and try to make it absolutely credible in TNG's sci-fi terms. On the other hand, casting Denise Crosby to play a character who looks exactly like the character's mother is just a dopey soap-opera conceit to begin with. (The paradox here: You can tell this story, but to do it with Crosby is to just remind us all that it's a conceit; but to not use Crosby means you don't have the story's WTF-baiting justification in the first place.)
In the end, the Romulan conspiracy is exposed and the Duras insurrection is put down (though Lursa and B'Etor themselves escape, naturally), thanks to the Enterprise's efforts and Data's ingenuity. Worf finds his two worlds in conflict, as he often does, and makes the choices we expect him to. Still, Worf's return to the Enterprise is handled a bit pat for my tastes. After the big deal that was made of his departure at the end of "Redemption, Part I," this feels like a swift and easy reset. As season-starting TNG cliffhanger resolutions go, this outing would become typical of the model.
Previous episode: Redemption, Part I
Next episode: Darmok

Season Index
13 comments on this review
Seriously, good work.
If you want to consider Crosby playing her own daughter as a 'soap-opera conceit,' fine, but, based on your other reviews, if this had been a DS9 episode, I have the feeling you'd have given this 4 stars for precisely that reason.
Knowing that show, we would've gotten a threesome with her, Dukat, & Nurse Ratched
Her appearance bugs the hell out of me. Are Romulan genes so recessive that she looks like she sprang direct from her mother's forehead? Couldn't they at least have given her a black wig, or a little prosthetic lump on her forehead, or sallow skin, or something? Lazy and moronic.
Then again I always felt the "unprofessional jackass won't follow Data's orders" plot was pretty dumb too - by-the-numbers and tedious. When Data ignore's Picards orders, why doesn't he just explain what he's doing? He can multitask, we know that. A dumb episode all round.
Part I essentialy had two related storylines: political turmoil in the Klingon Empire and Worf's struggle to regain his family honor. Though the episode wasn't perfect, I think it was a very good culmination of the arc that had been brewing for two years. It is anenjoyable hour, especially when put alongside its great thematic predecessors "Sins of the Father", "Reunion" and "In the Mind's Eye". Part II, though kinda OK when viewed on its own terms, inexplicably drops all this rich backstory.
Klingon political manoeuvring, scheming and backstabbing? Virtually gone, replaced for unknown reasons with Romulans. It's not even Romulan *scheming and backstabbing*, just a random and uninteresting plot involving Romulans smuggling some supplies, without the episode even trying to devote some time to fleshing out their motivation and to delving into political repercussions of this whole affair.
Worf's storyline was especially butchered. The guy spent the whole episode imprisoned; no tough choices, no impact on anything transpiring on the screen. It's obvious screenwriters didn't know what to do with him, so they just eliminated him as a player in the unfolding drama.
Basically, they abandoned the two main storylines of Part I and replaced them with unrelated material that belonged in a completely different episode -- Tash...err, Sela's reveal, Picard's blockade of the border and Data's first command. I'm not saying it's utterly uncompelling, but it simply has no thematic cohesion with the plot points set up in the previous episode.
And lastly, I just have to mention the ridicilous notion that a fleet of twenty ships can blockade (in three dimensions, remeber!) the whole Klingon-Romulan border that is probably dozens upon dozens light years long. It has a similar vibe of nonsensicality :) as the idea in "Unification" that you can conquer a planet with 2000 soldiers.
Yeah, I really didn't like this one...
Stellar cartography is always ignored. Even if the Romulans had managed to conquer Vulcan, how the hell could they hold it...Vulcan is in the hjeart of the Federation...supply lines would be nonexistent.
Even worse, on DS9, we had for a time the Klingons and the Cardassians at war, never mind the fact that the Cardassian Union and the Klingon Empire are geogr-, er, astrometrically on opposite sides of the vast bulk of the Federation.
Sigh... such is the life of a Star Trek fan... what are we to except to fanwank an explanation :)
As for the episode, I'm with Jammer, the Data command subplot was the most intriguing. But it did seem rather silly for Worf to resign, just to be captured until the end of the war!
I'm not sure why everyone are attacking Data's first officer, even today, we have people suspect of various technologies (e.g., anyone want screensavers free, that also come with malware?). Data is the ONLY sentient android in the entire federation, it would take time to get over people's misconceptions. At least Data's first officer's concerns made much more sense, than Engineer Logan abandoning his post in battle just to argue with Geordi in the episode, "Arsenal of Freedom".
Submit a comment