Star Trek: The Original Series
"Tomorrow Is Yesterday"
Air date: 1/26/1967
Written by D.C. Fontana
Directed by Michael O'Herlihy
Review by Jamahl Epsicokhan
The Enterprise is hurled back through time to Earth of the 1960s, where they inadvertently become the subject of Air Force Captain John Christopher's (Roger Perry) UFO sighting. After beaming him aboard the ship following an accident that destroys his jet, Kirk is forced to prohibit him from returning to Earth and contaminating the timeline with knowledge from the future. The only problem: Removing Christopher from Earth would also contaminate the timeline, because his unborn son would not be able to make a vital contribution to Earth's history as the future knows it.
As Trek's first time-travel outing, "Tomorrow Is Yesterday" is a brilliantly fascinating story, beginning with its exciting opening shots of the Enterprise flying through Earth's sky, and continuing through an adventure where the crew must remove all traces of their presence in the past by breaking into an Air Force base and stealing video recordings of the Enterprise. All of this is a great deal of fun, but the subtext of "Tomorrow" is what really stands out here: Through Christopher, this becomes a story analyzing the significance of any random individual and how they can make a difference in the world. And putting Christopher in the center of the story allows us to see the Enterprise and the future through his eyes.
True, the ultimate solution to the story's problem has its share of inconsistencies and loopholes (why is it traveling back in time would only clear Christopher's memory and not the Enterprise crew's?), but who really cares? This was a pioneer time-travel outing for Trek, and a great one at that, beginning a tradition of storytelling open to limitless possibilities.
Previous episode: Arena
Next episode: Court Martial
36 comments on this review
Thu, Mar 29, 2012, 12:43am (UTC -5)
The only problem that keeps it just short of 4 stars in my opinion is the ending- it gets a little confusing and Treknobabblish, to the point where I couldn't quite understand it and it kind of snapped me out of the moment. Also, you'd think the Enterprise would have better security, or keep a closer watch on Christopher after his multiple escape attempts. But those are just small nitpicks in an otherwise awesome episode. Jammer pretty much nails it.
3.5 stars (but it comes close to a 4)
Mon, Apr 30, 2012, 11:42am (UTC -5)
Thu, May 24, 2012, 6:30pm (UTC -5)
Mon, Mar 11, 2013, 10:27pm (UTC -5)
Thu, Sep 26, 2013, 3:40pm (UTC -5)
Wed, Mar 5, 2014, 10:51pm (UTC -5)
this episode fails HORRIBLY in that regard.
(even for 1960-standards)
*WARP speed is supposed to be FASTER than light.
(the WARPING of space, thats why normal relativity does not count)
*the sling-shot effect of a star might give you fast speed, but NEVER faster than light, hence it would at best give you normal (aka impuls-speed)
*one can NOT travel back in time in normal impuls speed, only slow down time that effect at 0.5 impulsspeed (or halve the speed of light would be nearing a factor 6000 (or 1.7 hours passing relativily for ever second experienced while traveling at 0.5 impuls) The story that gravity would cause rime to go BACKWARDS is total bullshit.
*the kind of slingshot effect needed to even GET a proper time dialation effect would need something FAR more massive than our sun, like the black hole at the center of out galaxcy, one slingshot around that MIGHT give a ship 0.5 impuls.
*there IS no difference between speed and gravity, both are the same force, having the same effect on time.
*they are slingshot away from the sun, saying they travel at off the chart speeds, way faster than warp 8. given that warp-factor is compression factor. they should move out of the solar system in a blink, the distance they travel (sun to earth) should have taken them a lot shorter and at that speed they should have flows far out of the solar system in no second at all.
Here is the data :
(warp 1 = 1.00-9.99* speed of light)
(warp 2 = 10.00-99.99* speed of light)
(warp 3 = 100.00-999.99* speed of light)
(warp 4 = 1000.00-9999.99* speed of light)
(warp 5 = 10000.00-99999.99* speed of light)
(warp 6 = 100000.00-999999.99* speed of light)
(warp 7 = 1000000.00-9999999.99* speed of light)
(warp 8 = 10000000.00-99999999.99* speed of light)
(warp 9 = 100000000.00-99999999.99*speed of light)
Given that it's of the chart.. it must have been at least warp 9.0
thats at least 100 MILLION times faster than the speed of light.
the distance between the sun and earth is about 6 light-minutes.
It would have taken : 0,0000036 seconds to reach earth at warp 9.0
given that we have seen this speed activated for about 57 seconds (time between sulu saying of the chart, and the captain being beamed down)
the distance traveled would have been a little over 180 lightyears.
the only thing that MIGHT be possible is that black matter star, causing a distortion in the warp-field causing it to warp time too, into the negative.
-> getting back would just have needed them to travel a while at impuls speed. (one other common mistake in star trek, they travel WAY to much at impuls without showing any of the time-differiental problems that that would cause.
Wed, Mar 5, 2014, 11:52pm (UTC -5)
Sat, Apr 12, 2014, 10:23pm (UTC -5)
Never crazy about this one. Produced well and had its cute moments, but what really happened? What was the story? Beam pilot aboard, beam him back, go back to future. Yawn.
The whole time travel vehicle has been utilized very well in the trek universe, just not here, imho.
Thu, Oct 16, 2014, 7:53am (UTC -5)
Mon, Dec 1, 2014, 6:11am (UTC -5)
Also, I found it funny that the military people watching the skies immediately presumed, "UFO! Let's go look at it, and maybe blow it up!" Wouldn't they really have thought, "OMG, it's mysterious Russian technology sent to blow us sky high! We'd better blow it up NOW. Nuclear missiles at the ready!" In reality, the Enterprise probably wouldn't have stood a chance of survival.
Fri, Jul 10, 2015, 11:35am (UTC -5)
Fri, Jul 10, 2015, 6:22pm (UTC -5)
Sun, Aug 9, 2015, 4:39am (UTC -5)
Sat, Apr 16, 2016, 12:29pm (UTC -5)
Then, they decide to hold Christopher prisoner because of their screw up? I don't think I have ever seen such a cruel suggestion. Christopher is a man of honor--how about they just stress to him how important it is that he not reveal what he knows?
That being said, I did find this an enjoyable outing. Unlike Pam above however, i did not enjoy the fighting. We are supposed to believe Kirk is the best fighter ever, able to take on three military men by himself? He's not Superman, just from the future.
Tue, Jul 5, 2016, 6:41am (UTC -5)
Of course, we all read it the other way, that is, that superman is causing the Earth to spin backwards to reverse time. :)
Sat, Aug 6, 2016, 2:00pm (UTC -5)
Acceleration and gravity are equivalent.
Thu, Sep 15, 2016, 3:41pm (UTC -5)
Sat, Nov 26, 2016, 2:54pm (UTC -5)
True, acceleration and gravity are two words describing the same effect of force applied to an object over time, and how that changes the amount of weight we experience.
but I believe what DutchStudent82 was referring to was that Speed and Gravity have identical effects on time dilation. Extreme Increases in either and the time dilation effect is increased.
About this episode, while I am a huge fan of reading Hard Sci Fi, I am willing to give a lot of the bad Science in movies and TV shows a pass. My biggest pet peeves are when the motivations of the characters are so Out of Character, just to move the plot forward. As many here have noted, Kirk would never have just walked this pilot from the past around the Enterprise, describing all the future tech.
But as a kid, I thought this episode was fantastic.
Fri, Apr 7, 2017, 4:22pm (UTC -5)
What I liked about the episode is the unpredictability. One of the great things about TOS is the injection of humor -- its own brand of humor. What I didn't like -- aside from the treknobabble about slingshot effects etc. -- is how Kirk shows Christopher around, Uhura starts showing him stuff etc. Proper procedures with non-Enterprise personnel are simply ignored which compound Kirk's problem. Of course, then we wouldn't have a decent episode.
And then there is the loophole of returning Christopher back to before being beamed aboard the Enterprise and so he doesn't remember anything, but the Enterprise crew does.
I fully agree with the first comment (NCC-1701-Z's) although I'd give it 3/4 stars. The idea of an air base reacting to a UFO at the start of the episode is an original twist and well done with a shot of the Enterprise in the Earth's skies.
Fri, Jun 23, 2017, 1:31am (UTC -5)
I am really bad at pointing out inconsistencies in any kind of show or drama or comedy, but I do realize that to enjoy entertainment, we do have to acknowledge the inconsistencies, suspend belief comma and move on. I find it really hard to do sometimes and I can accept that others do as well. If you look at time travel in the dust on a butterfly's wing theory, you would go absolutely crazy trying to deal with the impact of time travel. Sometimes you just have to enjoy!
Mon, Jul 31, 2017, 10:21am (UTC -5)
Sat, Sep 30, 2017, 7:44pm (UTC -5)
Most Star Trek films have their origin in an episode of the series: The Motion Picture clearly comes from The Changeling; Wrath of Khan comes from Space Seed; The Search for Spock has a lot of Amok Time in it; and The Voyage Home finds its inspiration in this episode Tomorrow is Yesterday, where the Enterprise crew has to complete a mission in present-day America and travel through time by slingshotting around the sun.
The episode is obviously a more modest and simple story than Star Trek IV, but it's still got some great gags and is a strong ensemble piece. The crew's scenes with Captain Christopher, the MP, and the airbase staff are fun. Spock (love the scene where he drily tells McCoy he's working on computations while standing next to him) has good bits with Christopher, whom he realizes will say or do anything to get home rather than follow Kirk; Sulu is fun on the landing party with his judo chop and little smirks at things like the bulletin board. And McCoy has a few choice moments with Christopher. Uhura and Scotty are more window dressing in this one, but it's nice to see Transporter Chief Kyle (John Winston) make his first appearance in the series, starting a semi-recurring role that will take him all the way from good moments in episodes like "Mirror Mirror" to a cameo as the Reliant comm officer in Star Trek II.
Jammer highlighted the episode's thoughtful notion of how one seemingly insignificant individual can make a bigger impact on the world than he or she realizes. But for me, "Tomorrow" is all about the picaresque visuals (the opening sequence with the fighter jet and limiting starship remains a great shock teaser) and sense of fun we have as the crew tries to tie up loose ends and get home. Yes, we know there's not much to the main plot other than recovering photographic evidence and repairing the ship for time travel. But it doesn't matter since the fish-out-of-water view of our heroes through 20th century eyes and the moral dilemma of Captain Christopher feel compelling enough on their own.
Sat, Sep 30, 2017, 9:26pm (UTC -5)
Voyager and Enterprise start to do some unusual things with time travel; the Abrams Trek reboots suggest "the timeline can be changed" insofar as a new stream is created without obliterating the "Prime" timeline. Arguing about it feels like a pleasant but useless waste of time (pun intended) since time travel is really a story device more than a serious scientific possibility; it works when we're entertained and doesn't work when we're not.
As for Kirk showing Captain Christopher around the Enterprise, it's easy to overthink it from the perspective of later Trek shows, but we don't get any sense in "Tomorrow" that anyone has ever traveled through time before or that there are any established rules for what to do. Spock offers a number of theories in this episode, but nobody ever cites Starfleet regulations on time travel, because I think this episode is really trying to present it happening for the first time in Starfleet history. And the writers themselves haven't figured it out yet. But just because Spock foresees time travel issues doesn't mean Kirk and the others would if nobody from Starfleet has ever done it before; they've just been stranded in the past and Kirk is trying to earn Christopher's trust (Kirk's usual instinct) by showing him around the ship. It's not inconceivable that Kirk wouldn't realize the import of his actions, as he's basically doing triage in this story to hold everyone together while figuring out how to get back to the future. And in TOS, the tendency is always to trust the outsider, unlike many shows on later Trek series which relish paranoia and fear of others.
Sun, Nov 26, 2017, 3:32am (UTC -5)
Thu, Dec 14, 2017, 12:21am (UTC -5)
I know, I know, this was 1967.
Tue, May 22, 2018, 7:55pm (UTC -5)
That sassy mouthed from the past pilot would have sung a different tune if it was a few years later and "aliens" grabbed him. He made me angry even back then. >> Then there is Dr. McCoy with usual nastiness toward Spock and in front of a stranger. >> I have always failed to understand why every creature that gets aboard a Starfleet vehicle gets the run of it. Even in the 1960's in real life it would not have been done, nor would it be done today. >> I would never in the past nor now, give this episode anything but ten zeroes. AND, worse yet, the bridge crew did not have any idea how to solve their problem
because they stand there and let a prehistoric alien tell them what to do.
Sat, Nov 24, 2018, 1:16pm (UTC -5)
Mon, Mar 25, 2019, 11:16pm (UTC -5)
Just pure fun.
Sun, Apr 28, 2019, 11:39pm (UTC -5)
Tue, May 21, 2019, 11:23pm (UTC -5)
• How is Christopher’s memory wiped? They just hand-wave it away as “those things haven’t happened yet, so you won’t remember them”, but by that logic, the entire crew should be amnesiacs.
• How do they beam him back into his fighter jet? They destroyed the jet. They would have to radio the other Enterprise and tell them “hey beam this guy out, we’ll beam him back in, and for god’s sake don’t use the tractor beam”.
• The guard on the base — ditto. This one makes even less sense, since they beam the guard out/in at a point when he hadn’t yet found Kirk and Sulu. (In fact, this suggests that the poor guard is now caught in a time loop where he keeps finding Kirk and Sulu, getting beamed out, getting beamed back in a few minutes earlier, finding Kirk and Sulu again, etc.)
• The chronometers going backwards again. That’s not how chronometers work, damnit. (And I always wondered why people on Quora asked silly questions like “if I went backwards in time, what time would my watch say it was?”)
• Seriously, if time travel were this bloody easy, all wars would be time wars and things would just get very ridiculous very fast.
The entire ending of this episode made _no_ sense. I realise this is Trek, and Trek always puts the “fiction” in “science fiction”. But usually they at least try to have some basic consistency in their plots.
Even in that wacky episode with Alice and the White Rabbit and the samurai and the strafing WW2 planes, they wrapped it up nicely with “well your thoughts became real, so weird stuff happened”. This one just seems to give up and go “we’re out of time, let’s just handwave everything away”.
Mon, Jul 29, 2019, 1:47pm (UTC -5)
Sun, Sep 29, 2019, 6:34am (UTC -5)
Wed, Nov 6, 2019, 9:40am (UTC -5)
"That sounds about right"
Perfection
Wed, Jun 3, 2020, 5:26pm (UTC -5)
Sat, Jun 6, 2020, 7:06am (UTC -5)
Thu, Jul 2, 2020, 1:19am (UTC -5)
Why did the younger version of the Enterprise in the sky suddenly disappear at the end so that Christopher ended up seeing nothing? Why did that younger version of the Enterprise not lock on its tractor beam to the jet and beam him aboard again? Why did the Enterprise not beam up the Nebraska military base officer again after the older version of the Enterprise beam him back days earlier? I don't get it.
Submit a comment
◄ Season Index