Line #69 Recap/StarTrekTheNextGenerationS5E18CauseAndEffect


1	[[quoteright:350:https://static.tvtropes.org/pmwiki/pub/images/tng_cause_and_effect_hd_380.jpg]]
2	[[caption-width-right:350:''"Do you have the feeling that you've done this before?"'']]
3
4	->''"All hands abandon ship! Repeat, all hands abandon--"''
5	-->--'''Picard''', saying something viewers will get used to hearing a few times.co
6
7	'''Original air date:''' March 23, 1992
8
9	We begin this episode InMediasRes, with the ''Enterprise''[='=]s engines on fire and the ship out of control. The bridge crew is frantically trying to steady the ship long enough to launch the lifeboats as Picard orders all hands to abandon ship. And just as the audience is thinking, "LikeYouWouldReallyDoIt," they [[GutPunch really do it]]: the ''Enterprise'' [[WhamShot is blown apart in a huge]] [[ExplosionsInSpace space explosion]], lost with all hands!
10
11	Then the opening credits roll.
12
13	Act I seems to be a HowWeGotHere, as we're re-introduced to the ''Enterprise'' entering an unexplored sector. We first look in on Riker, Data, Worf and Crusher engaging in their regular poker game. After much banter (and a win for Crusher, who calls Riker's bluff), Crusher is called to sickbay to help La Forge deal with a major dizzy spell--but she experiences a bit of DejaVu whilst treating him. Later that night, in her quarters, Crusher hears what seem to be a mass of disembodied voices and, in switching on the light, breaks a glass she'd left on the night stand.
14
15	Crusher reports her experiences to the rest of the senior staff, but is interrupted when sensors detect a NegativeSpaceWedgie nearby. As the bridge crew attempt to deal with the situation, the ship begins losing power and is unable to move--just as a starship emerges from the Space Wedgie on a direct collision course. With no power to the engines, Riker (standing at Data's side for no apparent reason) suggests decompressing the main shuttlebay to provide the necessary thrust to get out of the way, while Data counter-suggests using the tractor beam to push the other ship aside. Picard goes with Data's plan, which is not entirely successful: the other ship is deflected, but not by enough, and smashes the ''Enterprise''[='=]s warp nacelle. This quickly causes a series of catastrophes, the events of the teaser play out before us again, and the ''Enterprise'' is destroyed.
16
17	Act II re-re-introduces us to the ''Enterprise'' entering an unexplored sector; it's at this point that savvy viewers will recognize the GroundhogDayLoop at play. Again we visit Riker, Data, Worf and Crusher playing poker, with much familiar banter. Crusher is about to win when Riker folds, realizing that she is going to call his bluff. Crusher is called to sickbay to help La Forge deal with a major dizzy spell, and again experiences ''déjà vu''--only this time, La Forge feels it as well. Later that night Crusher again hears voices in her quarters and quickly calls the captain--breaking that glass once again.
18
19	The next morning Crusher reports her experience, relating that others aboard ship have also heard the voices. But before they can investigate, sensors detect a NegativeSpaceWedgie nearby. As the bridge crew attempt to deal with the situation, a starship emerges from the Wedgie on a direct collision course. As before, Riker stands at Data's station and suggests decompressing the main shuttlebay while Data votes for a tractor beam. Picard sides with Data, the collision occurs and the ''Enterprise'' blows up real good.
20
21	Act III. The ''Enterprise'' enters an unexplored sector. By this time, even the characters are starting to catch on, after a fashion; at their poker game, Worf recognizes their banter, and then he, Riker and Crusher correctly call out the hand Data is dealing even before he deals it. Data helpfully notes, "[[{{Understatement}} This is highly improbable.]]"
22
23	In anticipation, Crusher calls sickbay asking after La Forge, only to be told he just walked in. This time, Crusher is examining La Forge's VISOR under Picard's supervision as they all discuss their recent ''déjà vu'' episodes. Crusher finds that some TechnoBabble is causing the VISOR itself to suffer from déjà vu, causing his dizziness when his brain can't parse the layered images.
24
25	Later that night, Crusher is ready for the disembodied voices; when they occur, she records them (she also moves the glass away from the light switch so she won't knock it over) and calls down to La Forge that she has something to report. He in turn tells her that another instance of that same TechnoBabble just happened. As she rushes out to meet him, [[YouCantFightFate she knocks the glass off the table, breaking it yet again]]. In Engineering, La Forge and Data analyze Crusher's recording and discover that the voices belong to the crew of the ''Enterprise''.
26
27	The next morning, Crusher and La Forge fill the others in on what they think is going on: a NegativeSpaceWedgie is going to entrap the ''Enterprise'' in a GroundhogDayLoop. They listen to parts of the recording which suggest the severity of the encounter's outcome, while trying to think of a way out. The problem is (unlike most instances of this trope) that if/when the Loop "loops," they all lose their memories of the previous loop, except for feelings of ''déjà vu''. La Forge suggests rewiring Data's AppliedPhlebotinum to mirror the previously established TechnoBabble so that, if/when the Loop "loops," he can send a message into the next loop--albeit an extremely short one, one word at most, which will show up only as a sort of post-hypnotic suggestion so Data won't know initially what it means. The plan is carried out, and no one feels like they've tried this before, which is a good sign. RedAlert! NegativeSpaceWedgie! Ship on collision course! The tractor beam doesn't work! ''Enterprise'' explodes! Only this time Data manages to activate the TechnoBabble message at the last second.
28
29	Back in that unexplored sector, back to the poker game. Worf experiences ''[[PardonMyKlingon nIb'poH]]'', and Crusher attempts to predict the hand that Data is about to deal. Instead, he deals all 3s, then three of a kind to each. Crusher is called to sickbay to help La Forge deal with a dizzy spell; she inspects his VISOR on a hunch and finds that it is being affected by TechnoBabble. In Engineering, Data runs a diagnostic on ship's systems, and the results come up all 3s. They get a call from Crusher, telling them she's just recorded a mass of disembodied voices in her quarters -- [[BrickJoke and they hear a glass shatter]].
30
31	The next morning, they are reporting their findings: they seem to be stuck in a GroundhogDayLoop caused by an as-yet-unencountered NegativeSpaceWedgie. The TechnoBabble which has been giving La Forge dizzy spells is also related to the Loop, and may be behind all the occurrences of the number 3 Data (and apparently the entire crew, it turns out) has been seeing. It is revealed that Data has been rewired to accept the TechnoBabble, which seems to be a way to send short messages from one Loop into the next. As they ponder over what this could mean, they are called to the bridge to deal with a NegativeSpaceWedgie.
32
33	As before, the ship is without power and unable to move as another ship emerges from the Wedgie. Riker (standing at Data's side for no apparent reason) suggests decompressing the shuttlebay, but Data counter-suggests using the tractor beam to push the other ship clear. Picard sides with Data, but Data suddenly has a EurekaMoment and goes with Riker's plan instead; the main shuttlebay decompresses, pushing the ''Enterprise'' clear and allowing the other ship to pass safely. The NegativeSpaceWedgie vanishes, power is restored, and Data explains his EurekaMoment: glancing at Riker, Data noted the number of rank pins on his collar (3) and deduced that the various phantom 3s referred to Riker, indicating that Riker's plan would be the successful one. (Good thing he didn't think it referred to himself, since he is 3rd in command of the ship behind Riker and Picard). The ''Enterprise'' crew greet the crew of the USS ''Bozeman'' (commanded by none other than Captain Series/{{Frasier}} [[Series/{{Cheers}} Crane]]), which was either stuck in the Loop for some 90 years or got teleported by the rift 90 years into the future. Picard solemnly asks the Captain to beam over to the ''Enterprise'', as there's something they need to discuss. The episode concludes with both ships flying off side by side.
34
35	----
36
37	!!Tropes featured in this episode include:
38	* AbandonShip: Picard calls for it, but the ''Enterprise'' explodes before anyone can get off.
39	* ArcNumber: ''Invoked''. As stated above, Data manages to send a message to himself in the last loop, which turns out to be the number 3.
40	* ArtisticLicenseSports: When Worf folds in the first scene, he briefly flips his hole card over before flipping over his entire hand. This is a big breach of traditional poker rules. If you show your hole cards, you're supposed to make sure all players have an equal chance to see them so that no one has an advantage.
41	* BittersweetEnding: Heavily {{Downplayed}}, as the ''Enterprise'' and crew finally escape the time loop in one piece, but the crew of the USS ''Bozeman'' have been flung 90 years into the future, ending the episode on a somber note as Picard realizes he's going to have to break the bad news to them.
42	* BottleEpisode: Sets on the ''Enterprise'' are all reused sets, the ''Bozeman'' is a retooling of the USS ''Reliant'' from ''Film/StarTrekIITheWrathOfKhan'', and the ''Bozeman'''s interior is from the recently produced ''Film/StarTrekVITheUndiscoveredCountry''. Creator/KelseyGrammer's guest appearance is the only aspect that deviates from this trope.
43	* BrickJoke:
44	** At the start of each time loop, Riker wonders aloud if Data is using his high-speed shuffling ability to stack the deck. In the final loop, that's exactly what Data does (albeit subconsciously).
45	** During Dr. Crusher's late night visit to the Captain's Ready Room, Picard mentions having the feeling he'd already read the section of the book he was reading. On a later loop the Captain is shown reading the same book with a very confused look on his face.
46	** Despite her best efforts, Crusher manages to break her wineglass in every iteration of the loop. The final time, we don't even see it, but La Forge and Data hear it shatter over the comm.
47	* CallBack: "[[Recap/StarTrekTheNextGenerationS3E15YesterdaysEnterprise Yesterday's Enterprise]]" featured a Federation ship from the past stumbling through a time rift as well.
48	* TheCameo: Creator/KelseyGrammer as the other captain, appearing in the last minute of the episode.
49	* CaptainMorganPose: Riker's habit of leaning on Data's console actually helps save the ''Enterprise'', reminding Data about Riker's plan.
50	* CardSharp: In the last time loop, Data unconsciously stacks the deck so that he deals everyone a single 3 followed by three of a kind.
51	* ClueOfFewWords: During the last time loop, the number 3 keeps popping up conspicuously. The crew figures out it was a clue they sent to themselves from the prior time loop but they need to figure out what it means. [[spoiler:Three refers to the number of pips on Riker's rank insignia, meaning his suggestion to avoid the collision should be done.]]
52	* ConvenientlyEmptyBuilding: An unusual variation occurs when the ''Enterprise'' vents the atmosphere of the main shuttlebay as an emergency means of maneuvering to avoid a collision. The main shuttlebay was never shown on-screen for budgetary reasons, but it is by all accounts a huge, busy facility; but there was absolutely no mention of the fate of the personnel who happened to be in the shuttlebay at the time—and due to the urgency of the situation, could not be warned or given time to evacuate. Given the lack of bodies seen flying into space, it is safe to assume that Red Alert had the shuttlebay personnel move to different areas of the ship to respond.
53	* ChekhovsSkill:
54	** Riker suggests that Data could be secretly stacking the playing card deck. In the final loop, he does.
55	** In [[Recap/StarTrekTheNextGenerationS5E9AMatterOfTime "A Matter of Time,"]] Data explained that he was capable of listening to and distinguishing over 150 musical works at the same time. Here, he uses the same skill to sort through the jumble of voices from the previous time loops.
56	* CoversAlwaysLie: For some bizarre reason, the [[https://files.catbox.moe/l8gb87.jpg cover of the 2002 UK VHS re-release]] containing this story features the USS ''[[Film/StarTrekIITheWrathOfKhan Reliant]]'' crashing into the ''Enterprise'' instead of the ''Bozeman''. Either there were some serious communication issues between Paramount and the artist, or someone was hoping to draw in people who might mistakenly think that Khan had somehow come BackFromTheDead.
57	* DejaVu: The crew are caught in a GroundhogDayLoop, Doctor Crusher begins to experience ''déjà vu'', and so do the other crew members when she brings up the issue. In subsequent loops, this progresses to predicting events before they happen.
58	* ADayInTheLimelight: Starts out like this, for Beverly Crusher. The episode plays with this trope, beginning by focusing on Dr. Crusher, who keeps noticing little things feeling familiar. Slowly, the focus expands to the rest of the main cast, who band together to figure out what the hell is going on.
59	* DidNotThinkThisThrough: They decide not to change course because they worry that this is what caused the destruction. However, this cannot be the case because when the very first iteration of the loop occurred, they would have no knowledge of past loops therefore originally they would not have changed course or even considered it.
60	* DownerBeginning: The ship explodes, right in the teaser, killing everyone.
61	* DutchAngle: Used frequently in the final loop, particularly where a conversation is repeated from a previous loop. In fact, this was achieved by filming the exact same take with multiple cameras.
62	* FateWorseThanDeath: It is heavily implied that the ''Bozeman'' crew have relived their own loop for the better part of a century -- though unlike the ''Enterprise'' crew, whether they were aware of it at all is left unclear.
63	* FailsafeFailure: The warp-core ejection system. As usual.
64	* FlingALightIntoTheFuture: How they end up saving the ''Enterprise''; La Forge comes up with a way for Data to send a brief message to himself in the next loop.
65	* {{Foreshadowing}}:
66	** Beverly calls Riker on a bluff in the first scene with the card game, saying she had a feeling he was bluffing. Knowing that Riker has the best poker face on the ship, it's a little clue that she's "remembering" previous iterations of the game.
67	** Riker jokes that he hopes Data isn't stacking the poker deck. He ends up doing just that during the final deal.
68	** During the briefing in second to last cycle, the camera lingers on Riker when Data talks about receiving the message subconsciously.
69	** When Picard first learns of the number-three conundrum, he asks, "What could it mean?" The camera then cuts to a close-up of Riker from his right side, so that his three collar pips are very visible.
70	* FreezeFrameBonus: When Crusher accesses La Forge's medical records, we briefly see that he has previously been treated for headaches caused by the common cold. (Evidently humans ''do'' still get colds, despite what Crusher herself implied in the episode "[[Recap/StarTrekTheNextGenerationS1E8TheBattle The Battle]]".)
71	* GivenNameReveal: Nurse Alyssa's last name was finally revealed in this episode: Ogawa.
72	* GroundhogDayLoop: In this example, the victims only have a vague sense of deja vu about it.
73	* HearingVoices: Caused by timelines bleeding over. It's not only mental, either; Crusher manages to make a recording of the voices for Data to analyze.
74	* InMediasRes: How the episode begins. When the ''Enterprise'' is first destroyed, viewers are led to believe that what happens next is HowWeGotHere, until it's revealed that the ship is trapped in a time-loop. That means that the first time the ''Enterprise'' is shown blowing up isn't necessarily the ''first'' time it was destroyed! The ship is stuck in the loop for 17 days, and only five days are shown.
75	* KilledMidSentence: "All hands, abandon ship! Repeat, all hands, abandon--"
76	* LimitedWardrobe: After going to bed, Crusher apparently got dressed in her full Starfleet uniform to pay a brief, late-night visit to Picard. She does keep her hair ribbon which was part of her pajamas in the previous scene. One can assume it's because of her visiting Picard in his ready room, rather than his quarters.
77	* MagicCountdown: The last red alert scene, where Data looks around to notice Riker's rank pin, plays out significantly longer than in previous rounds.
78	* NegativeSpaceWedgie: The cloud causing the TemporalParadox.
79	* NothingIsScarier: Done extremely effectively with the poker game that begins Act I. We've just seen the ''Enterprise'' explode and the entire main cast die... and the first scene afterwards does not address that fact in the slightest. It isn't until the next scene, with Crusher and La Forge in Sickbay, that we get any indication that anything is wrong.
80	* OhCrap: The look on the crew's face when they hear the recording of Picard screaming to abandon ship.
81	* TheOner: The first time we see Crusher's bedtime sequence, the scene starts with an extreme close-up of her hands pruning her flowers and then follows her as she sips a night-cap, lies down, hears voices, bolts upright and accidentally knocks over her glass. It's all shot in one continuous shot.
82	* ParanormalGamblingAdvantage: Generally defied by Data, as in most of the series. The episode shows that in most cases he deliberately avoids stacking the poker deck, even to his own disadvantage, but the final segment shows that he's entirely ''capable'' of doing so.
83	* PinocchioNose: After calling Riker's bluff, Crusher tells him that his left eyebrow raises when he bluffs -- except she's just kidding.
84	* RippleEffectProofMemory: Downplayed. Crew members don't entirely remember previous loops but do experience DejaVu moments, which grow in intensity with each new iteration.
85	* SelfFulfillingProphecy: Discussed. When Picard learns that the ship is being destroyed in previous time loops, the crew proposes changing directions, but Picard shoots that idea down, since they don't know ''what'' actions they took brought them to destruction. Incidentally, not changing directions takes them right back to the anomaly every time.
86	* ShoutOut: The ''Bozeman''[='=]s registry number, NCC-1941, is a reference to the Creator/StevenSpielberg film ''Film/NineteenFortyOne1979''.
87	* SpaceIsNoisy: The ''Enterprise'' explodes with a loud noise.
88	* StableTimeLoop: When Riker suggests that reversing course could be the cause of the ship's destruction, he is implying, whether he realizes it or not, that this trope is in effect. The irony is that [[AvertedTrope it isn't]], and had the crew not been overthinking the situation in this way, they might have broken free after the first loop.
89	* StartsWithTheirFuneral: The episode starts with the ''Enterprise'' getting blown up, then seemingly cuts back to show the events leading up to the explosion. It's a subversion: the ''Enterprise'' is caught in a time loop, and the crew is actually reliving the events, with slight variations each time, until they find a way out.
90	* TheTell: Crusher claims that Riker's left eyebrow raises slightly when he bluffs, but then says that she's just kidding.
91	* TooMuchInformation: When Data is summarizing his analysis of the "overlapping voices" phenomenon that Dr. Crusher recorded, Picard cuts Data off when he proceeds to listing the number of couples who he determined were engaged in "[[CoitusUninterruptus romantic encounters]]".
92	* WarmMilkHelpsYouSleep: Picard's Aunt Adele has a recipe for steamed milk which he shares with Crusher.
93	* WhamShot: The ''Enterprise''-D going kablooey in space in the cold open.
94	* WhatYearIsThis: Inverted. Picard asks Captain Bateson what year he thinks he's in, with Bateson assuming it's still 2278. The ''Enterprise'' crew also has concerns about this for themselves, but are relieved that it hasn't been ''anywhere'' near that long for them (only about 17 days) when they ring up a timebase reading.
95	* YouCantFightFate: Dr. Crusher very deliberately tries to avoid breaking her glass in the next loop but just ends up breaking it another way. It achieves BrickJoke status when Geordi contacts her on the intercom, and in the background you hear a glass breaking.

Context Recap / StarTrekTheNextGenerationS5E18CauseAndEffect