• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Tomorrow Is Yesterday: Another great TOS episode

Gingerbread Demon

Yelling at the Vorlons
Premium Member
Tomorrow Is Yesterday.

Such a cool episode. But when they beam the pilot back into his plane as they leave doesn't he still see the Enterprise? Doesn't the plane have cameras to record it?

What about his memories of his time onboard? I always wondered if there had been some other record of the ship being there that they didn't account for?
 
This is a commonly debated issue with this episode and I'm not even sure than the original author had a clear plan of what what supposed to be happening here. Here's a recent thread:
http://www.trekbbs.com/showthread.php?t=252382

Your point about the wing cameras is well made, as they form a significant part of the plot. I'm not sure what they would have been able to film in the (re-jigged) timeline though: During the return of Captain Christopher his intercom announces "you should be close enough now for visual contact" and 20 seconds later the Enterprise is gone from the pilot's POV. This would seem to differ from the original timeline where the Enterprise was still visible 20 seconds later (albeit in the distance). However, there is enough wiggle room for (re)interpretation, since the effects of the Transporter beam could have distracted Christopher's attention at the crucial moment, allowing Enterprise#2 to veer off into the clouds as planned; Christopher (having missed this) would have had no reason to follow a pursuit course.

As to what happened to Captain Christopher and his memories, this BBSer makes a good case IMO

At the end of the episode, when the Enterprise returns to Earth after its time-traveling trip around the sun, there are now two Christophers. The one who never got aboard the Enterprise will live on, but the one who met Kirk and Spock will be beamed to his death. When the transporter system finds that Christopher is already at the designated re-materialization point (in the fighter cockpit), it says "Okay, the job I'm doing is finished, so now I quit and wipe the pattern buffer." The Christopher that Kirk knew ceases to exist.

That would be a tough sell, as this version of him really is dying, and thus Christopher was kept in the dark about it.

Sad, but oddly convincing...
 
I don't accept that he died, him or the chicken soup guard! They were both beamed into the moment just before they first saw The Enterprise! Correcting the glitch in time travel! Plus I doubt Kirk or even Spock would condemn them to death if they had known!
JB
 
This is a commonly debated issue with this episode and I'm not even sure than the original author had a clear plan of what what supposed to be happening here. Here's a recent thread:
http://www.trekbbs.com/showthread.php?t=252382

Your point about the wing cameras is well made, as they form a significant part of the plot. I'm not sure what they would have been able to film in the (re-jigged) timeline though: During the return of Captain Christopher his intercom announces "you should be close enough now for visual contact" and 20 seconds later the Enterprise is gone from the pilot's POV. This would seem to differ from the original timeline where the Enterprise was still visible 20 seconds later (albeit in the distance). However, there is enough wiggle room for (re)interpretation, since the effects of the Transporter beam could have distracted Christopher's attention at the crucial moment, allowing Enterprise#2 to veer off into the clouds as planned; Christopher (having missed this) would have had no reason to follow a pursuit course.

As to what happened to Captain Christopher and his memories, this BBSer makes a good case IMO

At the end of the episode, when the Enterprise returns to Earth after its time-traveling trip around the sun, there are now two Christophers. The one who never got aboard the Enterprise will live on, but the one who met Kirk and Spock will be beamed to his death. When the transporter system finds that Christopher is already at the designated re-materialization point (in the fighter cockpit), it says "Okay, the job I'm doing is finished, so now I quit and wipe the pattern buffer." The Christopher that Kirk knew ceases to exist.

That would be a tough sell, as this version of him really is dying, and thus Christopher was kept in the dark about it.

Sad, but oddly convincing...


That's interesting. Thanks for the links. I shall go check that out.
 
Plus I doubt Kirk or even Spock would condemn them to death if they had known!
Indeed, they argue that the whole point of the exercise is to prevent Christopher's important son from being unborn. Supposedly, there will be no son unless the starship goes back to the past, again supposedly because Captain Christopher will "die in the crash"/be abducted to outer space before siring that kid. So the goal there is for the "second" Enterprise to stop the "first" starship from taking away the pilot, or at least to return the pilot there immediately after the abduction. There is little need to "restore history" as such - what counts is allowing Christopher to live on.

So what might really be going on is that the "second" Enterprise, safely in outer space, beams Christopher into the cockpit at the same split second when the "first" one, struggling inside the atmosphere and blind to the presence of her alternate self, beams him out of there. So there's no "superimposing one man upon another", just the filling of a sudden cavity.

Once beamed back, Christopher is confused long enough for the first starship to escape (with the earlier Christopher on board). And the heroes have already taken care of the wing camera data on the previous iteration of the loop. So everything is fine: J.S. Christopher will be born, and USAF will have no material on the UFO. Assuming, that is, that the later Christopher was rendered amnesiac when beamed into the cockpit...

...And that part is probably within the capabilities of our heroes. Only Christopher says no to induced amnesia; McCoy actually thinks it might work. We don't see him wielding the necessary hypospray, but perhaps we just missed it when we blinked? Or then he slipped something into the chicken soup (or whatever Christopher ate - he, too, must have been fed somehow). Or then there is an "AMNESIA" button in the transporter console.

That the Sergeant is also beamed back is completely unnecessary from both the POV of his future and the POV of keeping the UFO secret, though. Kirk just needs to get rid of him somehow - so the "beamed down to his death" thing still very much applies.

Timo Saloniemi
 
What plan to "veer off into the clouds"?
At the time when Captain Christopher first saw the Enterprise, she was "sluggishly" climbing higher into the sky, hoping to return to a standard orbit.

I don't accept that he died, him or the chicken soup guard! They were both beamed into the moment just before they first saw The Enterprise! Correcting the glitch in time travel! Plus I doubt Kirk or even Spock would condemn them to death if they had known!
JB
I sympathise, but then they weren't really killing anyone (technically), as other versions of Christopher and the guard lived on in the extant timeline.

Even if we accept the scenes at face value (and ignore inconvenient facts like the additional mass and energy being suddenly squished into the respective bodies) then at the very least there's still the issue of the memories: Captain Christopher was on the Enterprise; he interacted with the crew and they remember him. But that individual is (it seems) gone, having ceased to exist. In other words; DEAD :wah:

So what might really be going on is that the "second" Enterprise, safely in outer space, beams Christopher into the cockpit at the same split second when the "first" one, struggling inside the atmosphere and blind to the presence of her alternate self, beams him out of there. So there's no "superimposing one man upon another", just the filling of a sudden cavity.
Nice theory! Unfortunately, the reason why they beamed Christopher on board in the first place is because he saw the Enterprise and got himself locked in a tractor beam, which in turn crushed his plane. By the time he beamed out his aircraft was beyond saving. In addition, the tractor beam was held onto the wreckage of the plane for several minutes after, until it had completely broken up (Spock says). There's really no place for a duplicate Christopher to be.
 
Very true. So there are two timelines there: one where the "first" Enterprise is forced to apply the tractor and then beam the pilot aboard, and another where the "first" starships sees the fighter approach but then suddenly and mysteriously lose interest and just keep flying straight for a couple of seconds, completely missing sighting the starship (because the pilot aboard has been concussed by having a second pilot dumped into him by the transporter of the "second" starship).

Which dodges all paradoxes because the existence of multiple timelines is antidote for those. But it raises the question of "why bother", since in an infinite number of timelines (the ones where there was no black star encounter) J.S. Christopher would have been born anyway; if picking and choosing timelines is defined as possible here, then our heroes could simply have gone into one of those timelines on their way home, skipping the history-tampering business altogether. (The same goes for all let's-restore-the-past adventures, really.)

Timo Saloniemi
 
Quite - so skipping timelines clearly isn't an option in this scenario. That isn't to say that multiple timelines don't exist in Trek, but I think they would have to be created through major disruptions in an existing one by a party not native to contemporary event (i.e. a time traveller). The notion of infinite timelines really doesn't bear close scrutiny under any circumstances, although really I think we are only dealing with two timelines here - the one where Christopher's plane crashed (which Spock fears will result in a changed history) and the one where it doesn't (and where Christopher has no memories of the Enterprise).

As I see it, the timeline created when Christopher is abducted is severed irrevocably from the original (in the branching timeline model) when Enterprise travels back and stops Christopher from observing the starship in the first place. The "plane crash" timeline may or may not continue on (depending on your POV). Job done and they can now return to the future but really, Kirk has already missed the boat on this one as he now has not one but TWO passengers who are not part of this timeline! What Kirk ought to have done was return them both before their little jaunt around the sun. Gambling on the transporter beam sorting out his problems was the only non-overtly-murderous option he had left, really!

What plan to "veer off into the clouds"?
At the time when Captain Christopher first saw the Enterprise, she was "sluggishly" climbing higher into the sky, hoping to return to a standard orbit.

Then why did you write this?
...allowing Enterprise#2 to veer off into the clouds as planned...
Since that's not what was happening.
I'm not 100% sure what you're asking here, so I'll try be clear. The veering off is what Enterprise was trying to do in relation her previous state, which was simply to maintain her altitude. Returning to orbit unnoticed was the plan, but Captain Christopher interrupted that. With that distraction negated by the time travelling Enterprise, the plan was free to continue without issue.

I made the assumption that Enterprise would pass through a few clouds on her way up to standard orbit. This is because there are often clouds in the sky, even quite high up but you're right, there's no way to absolutely prove that this is what happened. Gross misconduct on my behalf, I apologise.
 
Last edited:
However, there is enough wiggle room for (re)interpretation, since the effects of the Transporter beam could have distracted Christopher's attention at the crucial moment, allowing Enterprise#2 to veer off into the clouds as planned; Christopher (having missed this) would have had no reason to follow a pursuit course.

Pigkiller: PLAN? There ain't no plan!
--Mad Max Beyond Thunderdome, 1985.
 
This is one of those great episodes that is a lot of fun but makes no sense at all. Just enjoy it, think about it too much and it all falls apart.
 
Yup! ;)

I would love to know what DC had in mind when she wrote the time travel portions of this episode
 
A great episode, despite the confusing ending. Captain Christopher was every bit the dedicated professional officer that Kirk and Spock were. I think that had the story been a little different, and he had absolutely not been able to return to his time and place, he could have easily become a successful Starfleet officer.

My favorite bit of dialogue from the episode:

CHRISTOPHER: I never thought I'd make it into space. I was in line to be chosen for the space program, but I didn't qualify.
KIRK: Take a good look around, Captain. You made it here ahead of all of them.
 
Last edited:
Besides, it has the F-104, my favorite "Century Series" fighter..
F-104_zpshspjxfwk.jpg



here are the Genie (nuclear air to air rocket) trials of the Starfighter

https://www.youtube.com/watch?v=HyUcQbsEBrE
 
I've never liked the beaming into place of the people they'd picked up, by which I mean that I've always hated that aspect of it.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top