Is there an issue? Send a MessageReason:
Image quality upgrade, replaced dead link.
Changed line(s) 5,6 (click to see context) from:
-->--'''Picard''', saying something viewers will get used to hearing a few times.
to:
-->--'''Picard''', saying something viewers will get used to hearing a few times.
times.co
Changed line(s) 56 (click to see context) from:
* CoversAlwaysLie: For some bizarre reason, the [[https://static.wikia.nocookie.net/memoryalpha/images/9/91/TNG_5.6_UK_VHS_cover.jpg/revision/latest?cb=20170721105025&path-prefix=en 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.
to:
* CoversAlwaysLie: For some bizarre reason, the [[https://static.wikia.nocookie.net/memoryalpha/images/9/91/TNG_5.6_UK_VHS_cover.jpg/revision/latest?cb=20170721105025&path-prefix=en [[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.
Is there an issue? Send a MessageReason:
None
Changed line(s) 51 (click to see context) from:
* 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.]]
to:
* 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 [[spoiler:Three refers to the number of pips on Riker's rank insignia, meaning his suggestion to avoid the collision should be done.]]
Is there an issue? Send a MessageReason:
None
Changed line(s) 23,24 (click to see context) from:
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 affecting the VISOR, causing his dizziness.
to:
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 affecting causing the VISOR, VISOR itself to suffer from déjà vu, causing his dizziness.
dizziness when his brain can't parse the layered images.
Is there an issue? Send a MessageReason:
Added DiffLines:
* 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.]]
Is there an issue? Send a MessageReason:
Previous link only led to the wiki page image was linked from, linked to actual image.
Changed line(s) 55 (click to see context) from:
* CoversAlwaysLie: For some bizarre reason, the [[https://memory-alpha.fandom.com/wiki/File:TNG_5.6_UK_VHS_cover.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.
to:
* CoversAlwaysLie: For some bizarre reason, the [[https://memory-alpha.fandom.com/wiki/File:TNG_5.[[https://static.wikia.nocookie.net/memoryalpha/images/9/91/TNG_5.6_UK_VHS_cover.jpg jpg/revision/latest?cb=20170721105025&path-prefix=en 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.
Is there an issue? Send a MessageReason:
None
Changed line(s) 75 (click to see context) from:
* 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.
to:
* 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.
Is there an issue? Send a MessageReason:
None
Changed line(s) 33,34 (click to see context) from:
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 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. 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.
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 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. Data explains his EurekaMoment: glancing at Riker, Data noted Picard solemnly asks the number of rank pins on his collar (3) and deduced that Captain to beam over to the various phantom 3s referred ''Enterprise'', as there's something they need 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.
discuss. The episode concludes with both ships flying off side by side.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* 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.
Is there an issue? Send a MessageReason:
Removal of GCPT
Deleted line(s) 69 (click to see context) :
%% * GettingCrapPastThe Radar: Due to overwhelming and persistent misuse, GCPTR is on-page examples only until 01 June 2021. If you are reading this in the future, please check the trope page to make sure your example fits the current definition.
Is there an issue? Send a MessageReason:
Kill Em All is no longer a trope
Changed line(s) 9,10 (click to see context) from:
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]], [[KillEmAll lost with all hands]]!
to:
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]], [[KillEmAll lost with all hands]]!
hands!
Is there an issue? Send a MessageReason:
None
Changed line(s) 85 (click to see context) from:
* ShoutOut: The ''Bozeman''[='=]s registry number, NCC-1941, is a reference to the Creator/StevenSpielberg film ''Film/NineteenFortyOne''.
to:
* ShoutOut: The ''Bozeman''[='=]s registry number, NCC-1941, is a reference to the Creator/StevenSpielberg film ''Film/NineteenFortyOne''.''Film/NineteenFortyOne1979''.
Is there an issue? Send a MessageReason:
Tidying up Natter and bad examples.
Deleted line(s) 53 (click to see context) :
** "[[Recap/StarTrekTheNextGenerationS2E9TheMeasureOfAMan The Measure of a Man]]" establishes that Data can perform 60 trillion operations per second, which explains how he can so quickly recognize the solution and act on it during the final time loop.
Deleted line(s) 56 (click to see context) :
** How any of them (who aren't Guinan, and therefore have no sense of time outside their subjective experience)--except, maybe Data (whose internal chronometer might get out of synch with ''Enterprise'''s)--do (or would) feel ''deja vu'' is unexplained.
Changed line(s) 59 (click to see context) from:
* DownerBeginning: The ship explodes, right in the teaser, killing everyone. Talk about catching the viewer's attention!
to:
* DownerBeginning: The ship explodes, right in the teaser, killing everyone. Talk about catching the viewer's attention!
Deleted line(s) 73 (click to see context) :
** OlderThanTheyThink: People tend to forget that this episode aired in 1992, the year ''before'' the film ''Film/GroundhogDay'' was released.
Deleted line(s) 90 (click to see context) :
** Except, neither Riker nor anybody else aboard could possibly know that.
Is there an issue? Send a MessageReason:
None
Changed line(s) 4 (click to see context) from:
->''"All hands abandon ship! Repeat, all hands abandon--"'' '''''[[KilledMidSentence [BOOM!] ]]'''''
to:
->''"All hands abandon ship! Repeat, all hands abandon--"'' '''''[[KilledMidSentence [BOOM!] ]]'''''
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* 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.
Is there an issue? Send a MessageReason:
None
Changed line(s) 49 (click to see context) from:
* 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 rhe ship to respond
to:
* 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 rhe the ship to respond respond.
Is there an issue? Send a MessageReason:
None
** 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.
Changed line(s) 75 (click to see context) from:
* LimitedWardrobe: After going to bed, Crusher apparently got dressed in her full Starfleet uniform to pay a brief, late-night visit to Picard.
to:
* 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.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* CoversAlwaysLie: For some bizarre reason, the [[https://memory-alpha.fandom.com/wiki/File:TNG_5.6_UK_VHS_cover.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.
Is there an issue? Send a MessageReason:
add some
Added DiffLines:
**How any of them (who aren't Guinan, and therefore have no sense of time outside their subjective experience)--except, maybe Data (whose internal chronometer might get out of synch with ''Enterprise'''s)--do (or would) feel ''deja vu'' is unexplained.
Added DiffLines:
**Except, neither Riker nor anybody else aboard could possibly know that.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
** OlderThanTheyThink: People tend to forget that this episode aired in 1992, the year ''before'' the film ''Film/GroundhogDay'' was released.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
'''Original air date:''' March 23, 1992
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* 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]]".)
Is there an issue? Send a MessageReason:
None
Changed line(s) 7,8 (click to see context) from:
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]].
to:
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]].
explosion]], [[KillEmAll lost with all hands]]!
Is there an issue? Send a MessageReason:
None
Changed line(s) 48 (click to see context) from:
** It's heavily implied that Data could be secretly stacking the playing card deck. In the final loop, he does.
to:
** It's heavily implied Riker suggests that Data could be secretly stacking the playing card deck. In the final loop, he does.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
** It's heavily implied that Data could be secretly stacking the playing card deck. In the final loop, he does.
Is there an issue? Send a MessageReason:
None
Changed line(s) 49 (click to see context) from:
** [[Recap/StarTrekTheNextGeneration S2E9TheMeasureOfAMan "The Measure of a Man"]] establishes that Data can perform 60 trillion operations per second, which explains how he can so quickly recognize the solution and act on it during the final time loop.
to:
** [[Recap/StarTrekTheNextGeneration S2E9TheMeasureOfAMan "The "[[Recap/StarTrekTheNextGenerationS2E9TheMeasureOfAMan The Measure of a Man"]] Man]]" establishes that Data can perform 60 trillion operations per second, which explains how he can so quickly recognize the solution and act on it during the final time loop.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* 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.
Is there an issue? Send a MessageReason:
None
Changed line(s) 19,22 (click to see context) from:
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:''' [[{{Understatement}} This is highly improbable.]]
->'''Data:''' [[{{Understatement}} This is highly improbable.]]
to:
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:''' [[{{Understatement}}it. Data helpfully notes, "[[{{Understatement}} This is highly improbable.]]
]]"
->'''Data:''' [[{{Understatement}}
* TheCameo: Creator/KelseyGrammer as the other captain, appearing in the last minute of the episode.
Changed line(s) 60 (click to see context) from:
** Dueing the briefing in second to last cycle, the camera lingers on Riker when Data talks about receiving the message subconsciously.
to:
** Dueing During the briefing in second to last cycle, the camera lingers on Riker when Data talks about receiving the message subconsciously.subconsciously.
** 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.
** 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.
Changed line(s) 63 (click to see context) from:
* GroundhogDayLoop: Predating the TropeNamer by over a year.
to:
* GroundhogDayLoop: Predating In this example, the TropeNamer by over victims only have a year.vague sense of deja vu about it.
Changed line(s) 65,66 (click to see context) from:
* 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!
** Each loop takes roughly a day, and they find out at the end they're out of sync by seventeen days. So the episode-opening destruction is roughly the twelfth time it was destroyed.
** Each loop takes roughly a day, and they find out at the end they're out of sync by seventeen days. So the episode-opening destruction is roughly the twelfth time it was destroyed.
to:
* 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!
** Eachdestroyed! The ship is stuck in the loop takes roughly a day, for 17 days, and they find out at the end they're out of sync by seventeen days. So the episode-opening destruction is roughly the twelfth time it was destroyed.only five days are shown.
** Each
* LimitedWardrobe: After going to bed, Crusher apparently got dressed in her full Starfleet uniform to pay a brief, late-night visit to Picard.
Deleted line(s) 69,70 (click to see context) :
** [[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."]]
** Most of the loops seem to have slightly different timing, with events happening sooner or slightly later in the various runthroughs. Could possibly be excused by the NegativeSpaceWedgie causing slight variations in the causality that sets off particular events.
** Most of the loops seem to have slightly different timing, with events happening sooner or slightly later in the various runthroughs. Could possibly be excused by the NegativeSpaceWedgie causing slight variations in the causality that sets off particular events.
* 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.
Changed line(s) 76,81 (click to see context) from:
* RippleEffectProofMemory:
** Downplayed. Crew members don't entirely remember previous loops, but do experience DejaVu moments, which grow in intensity with each new iteration.
** [[Literature/StarTrekDepartmentOfTemporalInvestigations One of the]] ExpandedUniverse novels also mentions that the ''Bozeman'' crew experienced the same effect, but didn't have the knowledge to break themselves free like the ''Enterprise'' did, resulting in [[FateWorseThanDeath 90 years of feeling trapped in a perpetual cycle of death]].
** Played straight in a different novel, where the ''Bozeman'' crew only remembers the final iteration with no knowledge of the loop until after Bateson meets with Picard.
* RuleOfThree: Data and his three spree in the final loop before it's broken.
* SelfFulfillingProphecy: Lampshaded, defied, averted, played straight, and thoroughly deconstructed.
** Downplayed. Crew members don't entirely remember previous loops, but do experience DejaVu moments, which grow in intensity with each new iteration.
** [[Literature/StarTrekDepartmentOfTemporalInvestigations One of the]] ExpandedUniverse novels also mentions that the ''Bozeman'' crew experienced the same effect, but didn't have the knowledge to break themselves free like the ''Enterprise'' did, resulting in [[FateWorseThanDeath 90 years of feeling trapped in a perpetual cycle of death]].
** Played straight in a different novel, where the ''Bozeman'' crew only remembers the final iteration with no knowledge of the loop until after Bateson meets with Picard.
* RuleOfThree: Data and his three spree in the final loop before it's broken.
* SelfFulfillingProphecy: Lampshaded, defied, averted, played straight, and thoroughly deconstructed.
to:
* RippleEffectProofMemory:
**RippleEffectProofMemory: Downplayed. Crew members don't entirely remember previous loops, loops but do experience DejaVu moments, which grow in intensity with each new iteration.
** [[Literature/StarTrekDepartmentOfTemporalInvestigations One of the]] ExpandedUniverse novels also mentions that the ''Bozeman'' crew experienced the same effect, but didn't have the knowledge to break themselves free like the ''Enterprise'' did, resulting in [[FateWorseThanDeath 90 years of feeling trapped in a perpetual cycle of death]].
** Played straight in a different novel, where the ''Bozeman'' crew only remembers the final iteration with no knowledge of the loop until after Bateson meets with Picard.
* RuleOfThree: Data and his three spree in the final loop before it's broken.
* SelfFulfillingProphecy: Lampshaded, defied, averted, played straight, and thoroughly deconstructed.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.
**
** Played straight in a different novel, where the ''Bozeman'' crew only remembers the final iteration with no knowledge of the loop until after Bateson meets with Picard.
* RuleOfThree: Data and his three spree in the final loop before it's broken.
Changed line(s) 84 (click to see context) from:
* 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.[[note]]Though it's also possible that the space-time rift was drawn to the ''Enterprise's'' position, not a static point in space, in which case it would make no difference.[[/note]]
to:
* 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.[[note]]Though it's also possible that the space-time rift was drawn to the ''Enterprise's'' position, not a static point in space, in which case it would make no difference.[[/note]]
Deleted line(s) 86 (click to see context) :
* 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
Changed line(s) 47 (click to see context) from:
* ChekhovsSkill: 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.
to:
* ChekhovsSkill: ChekhovsSkill:
** 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.
** [[Recap/StarTrekTheNextGeneration S2E9TheMeasureOfAMan "The Measure of a Man"]] establishes that Data can perform 60 trillion operations per second, which explains how he can so quickly recognize the solution and act on it during the final time loop.
** 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.
** [[Recap/StarTrekTheNextGeneration S2E9TheMeasureOfAMan "The Measure of a Man"]] establishes that Data can perform 60 trillion operations per second, which explains how he can so quickly recognize the solution and act on it during the final time loop.