Follow TV Tropes

Following

History Recap / StarTrekTheNextGenerationS5E18CauseAndEffect

Go To

OR

Added: 183

Changed: 1

Is there an issue? Send a MessageReason:
None


The next morning, Crusher and [=LaForge=] 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 deja vu. [=LaForge=] suggests re-wiring 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. Red Alert! 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.

to:

The next morning, Crusher and [=LaForge=] 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 deja vu. [=LaForge=] suggests re-wiring 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. Red Alert! 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.


Added DiffLines:

** [[FridgeBrilliance Then again, it could be playing out (at least partially) in Data's mind]]; after all, to him, [[Film/StarTrekFirstContact 0.68 seconds is "nearly an eternity."]]
Is there an issue? Send a MessageReason:
How\'d the same trope get listed twice?


* 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.
Is there an issue? Send a MessageReason:
None



to:

* 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.
Is there an issue? Send a MessageReason:
the idea here is not In Spite Of A Nail, but You Cant Fight Fate


* InSpiteOfANail: Doctor's Crusher's water glass is destined to die no matter what.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* SelfFulfillingProphecy: Lampshaded, defied, averted, played straight, and thoroughly deconstructed.


Added DiffLines:

* 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.


Added DiffLines:

* 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.
* YouCantFightFate: Dr Crusher very deliberately tries to avoid breaking her glass in the next loop but just ends up breaking it another way.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* MagicCountdown: The last red alert scene, where Data looks around to notice Riker's rank pin, plays out significantly longer than in previous rounds.

Added: 243

Changed: 172

Removed: 476

Is there an issue? Send a MessageReason:
None


* CreatorsPet: The ''Bozeman'' is Brannon Braga's pet starship, since he's from Bozeman, Montana.

to:

* CreatorsPet: The ''Bozeman'' is Brannon Braga's pet starship, since he's from Bozeman, Montana.



* HeyItsThatGuy: Kelsey Grammar as Captain Morgan Bateson.

to:

* HeyItsThatGuy: Kelsey Grammar as Captain Morgan Bateson.HearingVoices: Caused by timelines bleeding over.



* NegativeSpaceWedgie: The cloud causing the TemporalParadox.



* RippleEffectProofMemory: Crew members experience deja vu moments which turn out to be vestiges of previous time loops.
* SpaceIsNoisy: The Enterprise explodes with a loud noise.



* WhatCouldHaveBeen: The production team had hoped to get Creator/KirstieAlley to reprise her role as Lt. Saavik from ''Film/StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.
** The Emmy Awards [[http://www.youtube.com/watch?v=q6iI1iSdXGM would feature]] the cast of ''Series/{{Frasier}}'' as members of ''Voyager''.


Added DiffLines:

----
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* CreatorsPet: The ''Bozeman'' is Brannon Braga's pet starship, since he's from Bozeman, Montana.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* CaptainMorganPose: Riker's habit of leaning on Data's console actually helps save the ''Enterprise'', reminding Data about Riker's plan.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* OhCrap: The look on the crew's face when they hear the recording of Picard screaming to abandon ship.

Added: 133

Changed: 4

Is there an issue? Send a MessageReason:
None


----

to:

----
!!Tropes featured:


Added DiffLines:

* WhatYearIsThis: Inverted. Picard asks Bateson what year he thinks he's in, with Bateson assuming it's still 2278.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* AbandonShip: Picard calls for it, but the ''Enterprise'' explodes before anyone can get off.


Added DiffLines:

* FailsafeFailure: The warp-core ejection system. As usual.

Added: 265

Changed: 115

Is there an issue? Send a MessageReason:
None


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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[Series/{{Frasier}} 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. 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.

to:

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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[Series/{{Frasier}} 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. 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.


Added DiffLines:

* TakeAThirdOption: Averted. There doesn't seem to be a reason they couldn't have both decompressed the main shuttle bay and used the tractor beam on the other ship, but nobody thinks to try this, possibly because they have so little time to think anything through.
Is there an issue? Send a MessageReason:
None


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 smashes the Enterprise's warp nacelle, and the events of the teaser play out before us again and the Enterprise is destroyed.

to:

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, nacelle. This quickly causes a series of catastrophes and the events of the teaser play out before us again and the Enterprise is destroyed.
Is there an issue? Send a MessageReason:
None


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 smashes the Enterprise's engine pod, and the events of the teaser play out before us again and the Enterprise is destroyed.

to:

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 smashes the Enterprise's engine pod, warp nacelle, and the events of the teaser play out before us again and the Enterprise is destroyed.



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 shuttlebay while Data votes for a tractor beam. Picard sides with Data, the collission occurs and the Enterprise blows up real good.

to:

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 shuttlebay while Data votes for a tractor beam. Picard sides with Data, the collission collision occurs and the Enterprise blows up real good.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* 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. At that loop's briefing, Data states that "To date, we have encountered two-thousand and eighty-five conspicuous references to the number 3." That would actually make two-thousand and eighty-''six'' references, since 2,085 is a multiple of 3!


Added DiffLines:

* 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!
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* InSpiteOfANail: Doctor's Crusher's water glass is destined to die no matter what.
Is there an issue? Send a MessageReason:
None


* WhatCouldHaveBeen: The production team had hoped to get KirstieAlley to reprise her role as Lt. Saavik from ''Film/StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.

to:

* WhatCouldHaveBeen: The production team had hoped to get KirstieAlley Creator/KirstieAlley to reprise her role as Lt. Saavik from ''Film/StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.
Is there an issue? Send a MessageReason:
None


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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[{{Frasier}} Frasier]] [[{{Cheers}} Crane]]), which was either stuck in the Loop for some 90 years or got teleported by the rift 90 years into the future. 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.

to:

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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[{{Frasier}} [[Series/{{Frasier}} Frasier]] [[{{Cheers}} [[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. 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.



* WhatCouldHaveBeen: The production team had hoped to get KirstieAlley to reprise her role as Lt. Saavik from ''StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.
** The Emmy Awards [[http://www.youtube.com/watch?v=q6iI1iSdXGM would feature]] the cast of ''{{Frasier}}'' as members of ''Voyager''.

to:

* WhatCouldHaveBeen: The production team had hoped to get KirstieAlley to reprise her role as Lt. Saavik from ''StarTrekIITheWrathOfKhan'' ''Film/StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.
** The Emmy Awards [[http://www.youtube.com/watch?v=q6iI1iSdXGM would feature]] the cast of ''{{Frasier}}'' ''Series/{{Frasier}}'' as members of ''Voyager''.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

** The Emmy Awards [[http://www.youtube.com/watch?v=q6iI1iSdXGM would feature]] the cast of ''{{Frasier}}'' as members of ''Voyager''.

Changed: 66

Removed: 332

Is there an issue? Send a MessageReason:
None


* GroundhogDayLoop

to:

* GroundhogDayLoopGroundhogDayLoop: [[OlderThanTheyThink Pre-dating]] the TropeNamer by over a year.



* OlderThanTheyThink: No, this episode wasn't inspired by ''GroundhogDay'', it predated it.
* VisualEffectsOfAwesome: The production crew took the trouble to build a crude model of the ''Enterprise'' and blow it up rather than just play an explosion over the top of the ship. The result is that the explosion counts as SceneryGorn.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

* WhatCouldHaveBeen: The production team had hoped to get KirstieAlley to reprise her role as Lt. Saavik from ''StarTrekIITheWrathOfKhan'' for a cameo appearance behind Kelsey Grammar (doubling as a CastingGag due to both having had main character roles in ''Series/{{Cheers}}'') but could not due to scheduling conflicts.
Is there an issue? Send a MessageReason:
None


* MarthDebutedInSmashBros: No, this episode wasn't inspired by ''GroundhogDay'', it predated it.

to:

* MarthDebutedInSmashBros: OlderThanTheyThink: No, this episode wasn't inspired by ''GroundhogDay'', it predated it.
Is there an issue? Send a MessageReason:
None

Added DiffLines:

----
* GroundhogDayLoop
* HeyItsThatGuy: Kelsey Grammar as Captain Morgan Bateson.
* KilledMidSentence: Picard, when he gives the order to abandon ship.
* MarthDebutedInSmashBros: No, this episode wasn't inspired by ''GroundhogDay'', it predated it.
* VisualEffectsOfAwesome: The production crew took the trouble to build a crude model of the ''Enterprise'' and blow it up rather than just play an explosion over the top of the ship. The result is that the explosion counts as SceneryGorn.
* WhamLine: Picard's "All hands, abandon ship!" - which [[KilledMidSentence gets cut off]].
Is there an issue? Send a MessageReason:
None


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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[{{Frasier}} Frasier]] [[{{Cheers}} Crane]]), stuck in the Loop for some 90 years. 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.

to:

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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[{{Frasier}} Frasier]] [[{{Cheers}} Crane]]), which was either stuck in the Loop for some 90 years.years or got teleported by the rift 90 years into the future. 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.
Is there an issue? Send a MessageReason:
None


Back in that unexplored sector, back to the poker game. Worf experiences deja vu 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 [=LaForge=] 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 -- and they hear a glass shatter.

to:

Back in that unexplored sector, back to the poker game. Worf experiences deja vu 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 [=LaForge=] 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.
shatter]].
Is there an issue? Send a MessageReason:
None


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 [=LaForge=] 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, she knocks the glass off the table, breaking it yet again. In Engineering, [=LaForge=] and Data analyze Crusher's recording and discover that the voices belong to the crew of the Enterprise.

to:

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 [=LaForge=] 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.again]]. In Engineering, [=LaForge=] and Data analyze Crusher's recording and discover that the voices belong to the crew of the Enterprise.
Is there an issue? Send a MessageReason:
None


Series: Main/StarTrekTheNextGeneration\\

to:

Series: Main/StarTrekTheNextGeneration\\Series/StarTrekTheNextGeneration\\
Is there an issue? Send a MessageReason:
Not Understatement


-->'''Data:''' "This is [[{{Understatement}} highly improbable]]."

to:

-->'''Data:''' "This is [[{{Understatement}} highly improbable]].improbable."
Is there an issue? Send a MessageReason:
re-launch!

Added DiffLines:

[floatboxright:
Series: Main/StarTrekTheNextGeneration\\
Episode: Season 5, Episode 18\\
Title: Cause And Effect\\
Previous: The Outcast\\
Next: The First Duty\\
Recapper: Tropers/{{Scooter007}}]

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 [[OhCrap really do it]]: the Enterprise vanishes in a huge [[ExplosionsInSpace space explosion]].

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 [=LaForge=] deal with a major dizzy spell -- but she experiences a bit of deja vu 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.

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 smashes the Enterprise's engine pod, and the events of the teaser play out before us again and the Enterprise is destroyed.

Act II re-re-introduces us to the Enterprise entering an unexplored sector; it's at this point that savvy viewers will recognise 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 [=LaForge=] deal with a major dizzy spell -- and again experiences deja vu; only this time, [=LaForge=] feels it as well. Later that night Crusher again hears voices in her quarters and quickly calls the captain -- breaking that glass once again.

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 shuttlebay while Data votes for a tractor beam. Picard sides with Data, the collission occurs and the Enterprise blows up real good.

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:''' "This is [[{{Understatement}} highly improbable]]."

In anticipation, Crusher calls sickbay asking after [=LaForge=], only to be told he just walked in. This time, Crusher is examining [=LaForge=]'s VISOR under Picard's supervision as they all discuss their recent deja vu episodes. Crusher finds that some TechnoBabble is affecting the VISOR, causing his dizziness.

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 [=LaForge=] 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, she knocks the glass off the table, breaking it yet again. In Engineering, [=LaForge=] and Data analyze Crusher's recording and discover that the voices belong to the crew of the Enterprise.

The next morning, Crusher and [=LaForge=] 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 deja vu. [=LaForge=] suggests re-wiring 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. Red Alert! 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.

Back in that unexplored sector, back to the poker game. Worf experiences deja vu 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 [=LaForge=] 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 -- and they hear a glass shatter.

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 [=LaForge=] 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 re-wired 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.

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 the Enterprise crew greet the crew of the U.S.S. Bozeman (commanded by none other than Captain [[{{Frasier}} Frasier]] [[{{Cheers}} Crane]]), stuck in the Loop for some 90 years. 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.

Top