# So You Want To/Write a Hard Science Fiction Story With Space Travel

How-To Guide |
---|

"Did you ever notice when you're jacking off, that it's more of a turn-on to fantasize about the girl next door than it is to fantasize about a supermodel? Because with the girl next door, you're thinking, hey,this could really happen!"

Carlin's observation evokes one of the core appeals of hard science fiction. A sufficiently hard science fiction story, even if it's set in another star system, could *really happen* -- or at least, it should be very difficult for the readers to come up with ways that it *couldn't* happen.

Writing hard science fiction set in space carries with it all of the baggage of writing any other genre of literature. Your characters must be believable, your plots and descriptions must not be boring, the story must be *satisfying* to the reader in some way, etc.. Every piece of advice in the Write a Story article is just as sound when writing hard SF as it is when writing a western, a modern romance, a historical naval drama, or any other literary genre you can imagine.

However, to work as a piece of hard SF with space travel, the writer must go one big step farther: The technology, the mechanics of space travel, the planets, the aliens (if there *are* aliens), all the details of that futuristic setting *must be realistic.* You usually must take pains to follow the known laws of natural sciences, and how they apply to any areas of engineering, microeconomics and futurology that will appear in the story. This means you must *know* these sciences and areas, or have good access to someone who does. The technology, natural phenomena, biology and conduct in the story should be primitive and mundane enough relative to your knowledge of futurology, engineering, microeconomics and the natural sciences so that the aforementioned pains are very likely to succeed. While if strictly necessary the laws of your fictional universe are allowed to deviate from the natural sciences as currently known in Real Life, these deviations must be postulated by a hypothesis that does not definitely contradict any currently known experimental results. In this case it is recommended that you use a hypothesis that's being seriously considered, such as alternatives to general relativity, or physics beyond the Standard Model, such as scale relativity, CDT or causal sets. These are liberties taken, so you must be aware of each of those deviations, and you must have a reason for them that can be relied upon to be found plausible by reviewers. Even if you never explicitly tell anyone this reason, the story must never contradict this reason. The most important thing in writing this type of story is that you must take pains to *limit the damage* that future technologies and deviations can potentially do to the story, even if in-universe accidents were to happen and if people in-universe are not controlled by you. Because of all of this, you probably want to pass natural sciences, microeconomics, 20th century history and sociology classes in school or successfully work all the exercises in a few natural sciences textbooks and a microeconomics textbook before even coming up with the pitch for a franchise that uses basic hard-SF physics. If the franchise uses quantum physics or involves the details of general relativity, then you might want both all the accomplishments in the previous sentence and to earn a university physics degree before coming up with the pitch. If the franchise has aliens or unusual biology, then you might want to earn a university biology degree before coming up with the pitch for the story. If a term is important enough in your story that you should know the term's actual definition and the term is commonly used figuratively, loosely, ambiguously, or inaccurately, such as "exponential", or "quantum", then you must successfully work examples in a textbook about the relevant field, such as math for "exponential", and quantum physics or quantum computing for "quantum", depending on whether "quantum" is used in its physics sense or its computer sense.

Since space travel is involved, it's important to remember that human beings have traveled in space for over five decades now. We *know* what is involved in getting from the Earth's surface to low Earth orbit. We know what's involved in landing on a rocky world 400,000 kilometers away. We know what effect micro-gravity has on human bones and muscles. A realistic story involving space travel must take all this accumulated human knowledge into account. The cartoonish world of 1950s B-movie astronauts having a "navigational error" that sends them to an "uncharted planet" with an Earthlike ecosystem inhabited by alien women who speak English is, and should be, a Discredited Trope -- but so should portraying space travel like anything other than space travel just because it looks neater that way in your head. In many ways, you'll just have to dispense with the story making artistic sense so the story can make logical, scientific, engineering and micro-economic sense as something that could actually happen in the future, so be ready for a lot of artistic disappointments.

One of the best resources out there for realistic future space travel is the Atomic Rockets page, which covers everything from "what designs are on the drawing board for spacecraft capable of crossing interstellar distances within a human lifetime?" to "why should my female crew members not wear skirts?"

## Contents

## Outline of Artistic Disappointments and Non-recommended Tropes[edit | hide | hide all]

Sadly, the rules of realistically writing hard SF with space travel -- like the rules of realistically writing about anything -- are primarily a set of rules about what is not recommended. The more ideas you have about what you'd artistically *like* to have your characters do, the more ways reality will step in and say "No, that art stuff really is not recommended because Real Life would not work that way and if it did, writing about it would require a lot more effort and proficiency from you than it would without the art stuff."

Firstly, there is that which is Bad Writing in any genre. There are artistic, Doylist reasons why you'd want to do this, such as inexperience, not reading Allthetropes, a search for reliable, but still bad tropes out of fear of being fired from a writing job (eg. TV and movies are too expensive to treat failure as an option), being underpaid, having an Anvilicious object lesson to deliver, hating one's boss, other projects and rarely, simple laziness. Treat failure as an option, but never be satisfied with failure nor mediocrity. As a writer in hard SF, you must fully intend to succeed with flying colors, even if you have to take the risk of failure. Because you're dealing with an audience smart enough to have the basic understanding of consistency, accuracy, and natural science required to care about and more-or-less know where a work fits into the Mohs Scale of Science Fiction Hardness, and you're dealing with impersonal forces that can easily take decades or centuries that are not easily Time Skipped, such as sub-light interstellar travel, technological and social innovation and the rise and fall of civilizations, you often must write an epic. You can't get away with writing a cartoon. Hard SF audiences are intelligent and have access to works of other genres and literary award winning works of hard SF, of which there are many, so they won't stick around for mediocrity, which bores them, nor for failure, because hard SF audiences look forward to reading literary award winning works of hard SF. Viewers are Morons is not acceptable.

Secondly, here is a list of tropes that are generally considered not recommended specifically in a realistic hard SF universe, along with some works or franchises that successfully implement some of them and are still considered to be hard SF:

- All Planets Are Earthlike (at least without Terraforming). Example: Green Mars and Blue Mars by Kim Stanley Robinson implement this in Mars' case by terraforming Mars.
- Inertial Dampening. Example: Orion's Arm, written collaboratively, implements this in the Halo Drive and the rumored Void Drive. The Halo Drive implements this by nacelles that use gravito-magnetism to harness the fuel/engines proper into the main hull of the ship, so everything and everyone in the main hull is accelerated equally, thus making nothing there feel the acceleration. The Void Drive would implement this by having the entire ship inside a space-time metric.
- Reactionless Drive (at least until the RF resonant cavity thruster, aka the EmDrive, is confirmed, if ever) Example: Orion's Arm implements this by making the space-time metric really small instead of metrics large enough to surround the ship without making the metric a lot Bigger on the Inside, apparently because making metrics that are large on the outside is too difficult.
- Single Biome Planet
- Space Is an Ocean
- Space Pirates. Example: Corsair by James L. Cambias (
*not*Minami Fuuko) implements this by making the ships into crew-less robots that are run and computer hacked from offices on the Eastern seaboard of the United States. The piracy has a sort of maritime aspect also. - Stealth in Space (and most of the other sub-tropes of Space Does Not Work That Way). Example: Orion's Arm implements this by going really fast and would implement this by making the void-ship inside a metric that's Bigger on the Inside.
- Teleporters and Transporters. Example: Orion's Arm implements this with rental bodies, which are bodies that one uses by Brain Uploading and engenerators, which copy people.
- Green-Skinned Space Babe (and Rubber Forehead Aliens in general)
- Faster-Than-Light Travel / Time Travel. Example: The Xeelee Sequence by Stephen Baxter implements this with Sufficiently Advanced Technology.
- Techno Babble. Example: Orion's Arm implements this with such phrases as "hyperdenebola collapse" to refer to the de-assimilation that tends to happen when a colony's communications with the Amalgamation are cut off. According to Wikipedia, Denebola is Beta Leonis, a star in constellation Leo about 43 light-years from Earth. What this star has to do with "hyper", "collapse", and the Amalgamation is not actually obvious.
- Clichés, especially science fiction cliches. Even if these are technically possible in a hard-SF setting - which is itself by no means whatsoever guaranteed - then they still tend to be unrealistically common in science fiction, and it is common for them to be unrealistically portrayed. And as detailed above, hard SF audiences tend to be intelligent. So no cliches.
- Inaccuracies that aren't, strictly speaking, about math, natural sciences, microeconomics or futurology, liberties that are not painstakingly Deconstructed or Reconstructed or are revealed to be just too implausible by their deconstruction or reconstruction, and breaks from reality without regard to how acceptable they are in other genres. Inaccuracies that are not about these topics are liable to be confused with inaccuracies that are about these topics, and hard SF is all about Consistency and accuracy, so even if inaccuracies are not confused topic-wise, inaccuracies are still kind of wrong for hard SF.

There are sound reasons why all of the above tropes will probably not work in Real Life. These tropes are not, strictly speaking, forbidden in this genre, but these tropes require extra painstaking labor from you and so aren't recommended.

#### Doing the Research[edit | hide]

This should go without saying, but if you're going to set your story someplace we already know something about -- like Mars or Alpha Centauri -- for goodness' sake, read up on what we know about the place before you start writing! We've sent space probes to every planet in the solar system, we've accrued reams of data on just about every star that has a name, we've even mapped out the interstellar medium in our neck of the galaxy. The data are out there, and thanks to the Internet they're not even hard to acquire any more.

You wouldn't set a story in the Sahara Desert and have your hero go swimming in one of the "numerous lakes" there. You wouldn't set a car chase in downtown Florence, Italy and then make up the street names and city layout. Similarly, don't set your story on Mars and have your hero swelter in the unbearable heat^{[1]}, or put an Earthlike planet in orbit around Alpha Centauri without at least mentioning the bright "B" star that should be visible from time to time in the sky. Making up details about places we *don't* have strong data about is okay, but making up details contradicted by data found on the Internet is not.

In other words, don't let your story turn into a Did Not Do the Research entry.

## Math[edit | hide]

If doing an arithmetic problem like "A train leaves Chicago at 8 AM going 60 miles per hour" taxes the limits of your skills, putting realistic space travel into your story is probably not for you. Space travel is *all about* doing the math, and the math can get hairy -- especially when dealing with speeds above 5-10% of the speed of light, where special relativity starts to rear its ugly head. But if you're up for the challenge, it's definitely worth doing. Even if you don't show your work to your readers, getting the numbers right (or nearly right) will go a long way toward your story's sense of realism.

Let's take as our example a rocket trip from Earth to Saturn. How long will it take to make the flight?

You could go the easy route, and look up how long it took for the Voyager 1 space probe to fly from Earth to Saturn, and just assume that you space ship flies about as fast as the Voyager probes did. But when you do look it up, you balk -- it took nearly *three years* for Voyager 1 to make this trip! You can't have your intrepid space cadets waiting around for three years just to get to Saturn, they've got important space adventures to have, space wars to fight, and space women to woo. You want them to get to Saturn a lot quicker. So, you give them a space ship that never runs out of fuel -- or uses fuel that's so efficient that it won't run out even if it runs its engines continuously between Earth and Saturn.

So, with the ability to accelerate indefinitely, *now* how long will it take to get to Saturn?

Let's say you decide to limit your space ship to a cruising acceleration of 1*g*, so that the crew will experience thrust equal to Earth's surface gravity. After all, this is a *hard* science fiction story, right? You can't just go slinging Inertial Dampening around. Any acceleration your ship undergoes will be experienced by your crew as G forces. So, if they're going to be cruising for anything longer than a few minutes, you'll probably want to keep your acceleration down to 1*g*. 1*g* works out to an acceleration of 9.8 meters per second per second -- at the end of one second, you'll be going 9.8 m/s, at the end of two seconds, you'll be going 19.6 m/s, and so forth.

At the low speeds we're dealing with in the Earth-to-Saturn example, the formulas relating speed, acceleration, time, and distance travelled while undergoing constant acceleration are pretty straightforward:

- v = a * t + v
_{0} - d = 0.5 * a * t
^{2}+ v_{0}* t - 2 * a * d = v
^{2}- v_{0}^{2}

... where d is the distance travelled in meters, v is your current velocity in m/sec, a is your acceleration in m/sec^{2}, t is the elapsed time in seconds, and v_{0} is your initial velocity at the start of your trip.

So, what value should we plug in for d? The distance from Earth to Saturn, right? Well, unfortunately, Earth and Saturn are both in orbit around the sun, which means they *move*. Their movements are more complicated than the simple equations I've written above, but for a first approximation, let's say you plan your trip to happen when Earth and Saturn are closest together, i.e. both on the same straight line from the sun (what astronomers call "opposition"). Looking up their orbital parameters on Wikipedia, we see that the average Earth-sun distance is 1.0 A.U., and the average Saturn-sun distance is 9.582 A.U., so the two will be about 8.5 A.U. apart at closest approach. (They *could* actually be closer. Saturn's orbit is rather eccentric, varying between 9 AU and 10 AU from the sun; but 9.5 A.U. is close enough for a first approximation. And waiting for Earth and Saturn to be at opposition *when* Saturn happens to be at perihelion will mean your space cadets will be sitting around tapping their toes for years.) 1 A.U. is about 150 million kilometers, so 8.5 A.U. works out to around 1,280,000,000 kilometers.

But wait -- our equations require d to be in meters, not kilometers. We have to inflate that number by a factor of a thousand. 1,280,000,000 km is 1,280,000,000,000 m. Let's hope your calculator has enough spaces for all those digits. (If not, you might need to enter it in scientific notation, as 1.28 x 10^{12}.)

Now, how long will the trip take? Let's plug our numbers into the second equation above. We know d, and we know a. We can assume v_{0} = 0, if we're taking off from Earth at a standing stop. (We won't actually be; our space ship will be taking off from Earth orbit, which means it'll be moving at about 7800 m/s, and our zero-velocity reference point here is our destination -- Saturn -- which is orbiting at a different speed as the Earth. But our overall speed is going to be so great that these little speed differences shouldn't matter much.) This is what we get:

d = 0.5 * a * t

^{2}+ v_{0}* t

1,280,000,000,000 m = 0.5 * 9.8 m/sec^{2}* t^{2}+ 0 * t

Simplifying:

1,280,000,000,000 m = 4.9 m/sec^{2}* t^{2}

Unfortunately, we're trying to solve for t here, so we need to do a little algebra. Let's divide both sides by 4.9 m/s^{2} :

1,280,000,000,000 m / 4.9 m/sec

^{2}= t^{2}

Simplifying:

260,000,000,000 sec^{2}= t^{2}

Taking the square root of both sides:

510,000 sec = t

So the trip will take 510,000 seconds. Since there are 86,400 seconds in a day, this means it'll take about 5.9 days. What will be our final velocity (v) when we reach Saturn? For that, we need the *first* equation above; luckily, since we now know t, it'll be a lot easier:

v = a * t + v

_{0}

v = 9.8 m/sec^{2}* 510,000 sec + 0

v = 5,000,000 m/sec

Woops! We arrived at Saturn in less than 6 days, but now we're whooshing past it at 5 million meters per second! (That's 5000 kilometers per second, about 1.6% of the speed of light.) At that speed, we'll only have a few seconds to have adventures on Saturn before we speed right out of the Solar system.

What we'd like to do instead is arrive at Saturn with a velocity of zero, or nearly zero. That's going to require us to fly a **brachistochrone** trajectory: We'll need to accelerate to the *half-way* point between the Earth and Saturn, then do a "skew flip" so that our engines are pointed in the opposite direction, then *decelerate* for the rest of the trip.

This adds an extra step or two to the math we'll need to do, but thankfully each step should be just as easy. First, we need to change d from the full Earth-Saturn distance (1,280,000,000,000 meters) to half that distance, and see how long it'll take to get *there*:

d = 0.5 * a * t

^{2}

640,000,000,000 m = 0.5 * 9.8 m/sec^{2}* t^{2}

Simplifying:

640,000,000,000 m = 4.9 m/sec^{2}* t^{2}

640,000,000,000 m / 4.9 m/sec^{2}= t^{2}

Simplifying:

130,000,000,000 sec^{2}= t^{2}

Taking the square root of both sides:

360,000 sec = t

So, it'll take 360,000 seconds -- a hair under 4.2 days -- to get to the half-way point. Our velocity v at this point will be:

v = a * t

v = 9.8 m/sec^{2}* 360,000 sec

v = 3,500,000 m/sec

3500 kilometers per second. Slightly more than 1% of the speed of light, but that's okay, because we're in deep space nowhere near Earth or Saturn. Now, how long will it take to decelerate from this speed to a speed of 0 at 1*g* (9.8 m/sec^{2})? For this, let's plug the numbers back into the first equation. Remember, this time, our acceleration is *negative* (a negative acceleration is the same thing as a deceleration), and we *do* have an initial velocity:

v = a * t + v

_{0}

0 = -9.8 m/sec^{2}* t + 3,500,000 m/sec

Subtracting 3,500,000 m/sec from both sides:

-3,500,000 m/sec = -9.8 m/sec^{2}* t

Dividing both sides by -9.8 m/sec^{2}:

-3,500,000 m/sec / -9.8 m/sec^{2}= t

360,000 sec = t

Hmmm! It takes 360,000 seconds to decelerate from 3500 km/sec to 0 -- exactly the same amount of time it took to accelerate from 0 to 3500 km/sec! And if we ran the numbers, we'd see that on this second leg, we covered exactly the same 640,000,000 km we covered in the first half of the trip. The two legs of the journey are *mirror images* of one another. Once we've figured out how long it takes to get to the half way point, we know that it'll take exactly as long to go the rest of the way (assuming our deceleration during the second leg is equal in magnitude to our acceleration during the first leg).

So ... using our brachistochrone trajectory, it takes 360,000 seconds to reach the half way point, and another 360,000 seconds to go the rest of the way, for a total of 720,000 seconds to get from Earth to Saturn. That's 8.3 days, a little over a week. It's still not something your space cadets can do on their day off, but it's a heck of a lot quicker than the 3 years Voyager 1 took to make the trip -- and unlike Voyager 1, your space ship ends up at rest relative to Saturn so it can stay there as long as you need it to.

### Special Relativity[edit | hide]

Now ... what if our heroes can go faster than this? Let's say we've decided we need shorter flight times, so *screw it*, we're introducing Inertial Dampening technology into our story, like in the *Honor Harrington* or *Star Trek* universe. Now our space ships can accelerate at 1,000 *g*, or 9,800 m/sec^{2}, and we should be able to get to Saturn much faster. In fact, using the first equation above, it looks like we should be able to accelerate to 30,000,000 m/sec in less than an hour -- that's a tenth of the speed of light.

And there's where we run into problems. Because above about a tenth of the speed of light, acceleration doesn't affect velocity in a straightforward manner any more. Your clock runs a little slower to a fixed observer than it does to you. Your momentum is slightly higher to a fixed observer than your acceleration history says it should be. The universe shrinks slightly in the direction you're moving. In short, you run smack-dab into *special Relativity*, and now the math gets a **lot** more complicated. For one, the change in your velocity per second, given a constant acceleration from your space ship's reference frame, now depends on your current velocity -- which turns the relationship between the two into a first-order differential equation.

The basic relativistic equation for determining your "gamma factor" -- the amount by which your mass goes up, time slows down, or distances in the direction of motion shrink -- is as follows:

- γ = 1 / sqrt (1 - v
^{2}/c^{2})

... where sqrt means square root, and c is the speed of light in a vacuum (about 300,000,000 m/sec). As you can see, it varies according to how fast you're going (that pesky v^{2} term in the denominator).

The Atomic Rockets website lists many, but not all, of the useful equations that come into play for a rocket travelling at these relativistic speeds. These include:

- T = (c/a) * ArcCosh[a*d/(c
^{2}) + 1] - t = sqrt[(d/c)
^{2}+ (2*d/a)] - v = c * Tanh[a*T/c]
- v = (a*t) / sqrt[1 + (a*t/c)
^{2}] - γ = Cosh[a*T/c]
- γ = a*d/(c
^{2}) + 1

... where T is "proper time" (the number of seconds elapsed in your space ship's frame of reference), t is the number of seconds elapsed from a fixed observer's frame of reference, d is distance travelled from a fixed observer's frame of reference, a is acceleration in the space ship's frame of reference (which is assumed to be held constant), Tanh is hyperbolic tangent (there's a button for this on most scientific calculators), and ArcCosh is inverse hyperbolic cosine.

So, let's say you want your inertial-dampener-equipped space ship to accelerate at 1,000*g*, or 9800 m/sec^{2}, and you want to follow the same course you did with your piddling little 1*g* space ship -- accelerate to the half-way point between Earth and Saturn, 640 million km away, and then decelerate for the same distance to arrive at Saturn with v = 0. How much time will that take, as far as the folks back on Earth are concerned? For that, we can use equation 2 above:

t = sqrt[(d/c)

^{2}+ (2*d/a)]

t = sqrt[(640,000,000,000 m / 300,000,000 m/sec)^{2}+ (2 * 640,000,000,000 m / 9800 m/sec^{2})]

t = sqrt[4,550,000 sec^{2}+ 130,600,000 sec^{2}]

t = 11,600 sec

The folks back on Earth measure 11,600 seconds, or about 3.2 hours, for the space ship to reach the half way point. Meanwhile, how much time has elapsed for the folks on board the space ship? For that, we need equation 1 above:

T = (c/a) * ArcCosh[a*d/(c

^{2}) + 1]

T = (300,000,000 m/sec / 9800 m/sec^{2}) * ArcCosh[9800 m/sec^{2}* 640,000,000,000 m / ((300,000,000 m/sec)^{2}) + 1]

T = (30,600 sec) * ArcCosh[0.06969 + 1]

T = 11,360 sec

Your intrepid spaceship crew measures the elapsed time as 11,360 seconds, which is only slightly less than the time t measured by the folks back on Earth. How fast will you be going at this half-way point? For that, we'll need equation 3 above:

v = c * Tanh[a*T/c]

v = 300,000,000 m/sec * Tanh[9800 m/sec^{2}* 11,360 sec / 300,000,000 m/sec]

v = 300,000,000 m/sec * 0.3549

v = 106,500,000 m/sec

... or a tad over 1/3 of the speed of light. This explains why our proper time T and our Earth time t are so close together: At 1/3 of light speed, the gamma factor is only about 1.07, and our space ship was only going this fast near the end of this leg anyway. If we'd taken a longer trip -- say, from Earth to Sedna in the Kuiper belt, or from Earth to Alpha Centauri -- we'd have more distance in which to accelerate, which would let us get closer to the speed of light, and the relativistic effects would have been more pronounced.

Unfortunately, these equations only address the situation when your space ship starts out at 0 velocity. If you want to apply these equations to a situation where you start out already moving at (say) 1/5 of light speed, they get even more complicated, and often times will not have already been derived for you. For example, the equation for the amount of time a fixed observer measures that it takes your accelerating space ship to cross a given distance, assuming you started out with a velocity that gave you an initial gamma factor of γ_{0}, is this hairy beast:

t = c/a * (sqrt [(a*d/c

^{2}+ γ_{0})^{2}-1] - sqrt[γ_{0}^{2}-1])

### Orbits[edit | hide]

If your space ship is close to a large object like a planet or a star, and is moving at a low enough speed, it isn't going to travel in a straight line. The gravity of the big object will cause your spacecraft to follow an *orbital* trajectory.

The equations for an orbit are more complicated than the equations for straight-line movement, because your acceleration is always changing; it depends on how far you are from the big object at that particular instant. Whole volumes have been written on how to calculate an orbit precisely, but there are some simple straightforward cases that are at least somewhat easier to calculate.

All orbits are shaped like *conic sections.* If your space ship is moving slower than the "escape velocity" -- or more precisely, if its total kinetic energy and gravitational potential energy is less than the gravitational potential energy it would have at an infinite altitude -- its orbit will be shaped like an ellipse. If it's moving *precisely at* the escape velocity, its orbit will be shaped like a parabola. If it's moving faster than the escape velocity, its orbit will be shaped like a hyperbola. This is assuming, however, that your space ship spends all its time from this moment forward in free-fall, without firing its engines.

Parabolic and hyperbolic orbits are basically escape trajectories. The spacecraft leaves the big object in question and never comes back. An elliptical orbit, on the other hand, is stable, and allows your space ship to go around and around the big object over and over again. It's what most people think of when they hear the word "orbit." An ellipse looks an oval-ish shape, with two points inside it called the "foci" (plural of focus). In an elliptical orbit, the *center* of the big object you're orbiting is going to be at one focus, while the other focus won't contain anything at all.

The formula for how long it takes to make one complete orbit was first deduced by Johannes Kepler when studying the motions of the planets around the sun. Sir Isaac Newton expanded on this formula so that it applied when orbiting *any* object. The formula is:

- P
^{2}M = A^{3}

.. where P is the period of the orbit *in years*, M is the total mass of all objects involved in the orbit *in solar masses*, and A is the semi-major axis of the orbit's ellipse *in Astronomical Units*.

The simplest kind of elliptical orbit is one with no eccentricity at all. We call this a *circle*. In a perfecly circular orbit, both foci are at the same point in space, which is at the center of the circle. The semi-major axis A of a circle is just its radius (half its diameter).

Suppose you want your space ship to orbit the Earth in a perfect circle 200 kilometers above the surface, like the Space Shuttle does. What will the period (P) of that orbit be? If we want to use the equation above -- P^{2}M = A^{3} -- we'll first have to find the combined *mass* of the Earth and your space ship in solar masses. The Sun's mass is about 2 x 10^{30} kg, while the Earth's mass is about 6 x 10^{24} kg. Let's say your space ship weighs in at 1000 tonnes, i.e. a million kg. Here's the mass of the Earth in solar masses:

3.003740720000000000 x 10

^{-6}

... and here's the combined mass of Earth and your space ship in solar masses:

3.003740720000000001 x 10

^{-6}

As you can see, unless the two objects involved in the orbit are of comparable mass, the mass of the teensy tinsy little orbiting object really doesn't matter for this equation. We can just use the Earth's mass by itself, and be done with it. We don't even need all those decimal digits -- the real Earth isn't a perfect sphere, so its gravity is a tiny bit "lumpy", which means that our answer for how long the orbit will take is only going to be approximate anyway. The value we need for M is 3 x 10^{-6} solar masses.

Now, we need the semi-major axis, that is, the radius of the orbit. We're at 200 kilometers altitude, so that means the orbital radius is 200 kilometers, right? *Wrong.* The radius is the distance from our space ship to the *center* of the Earth. The Earth is 6371 kilometers in radius, on average, so the orbit's radius is 6571 km. For our formula, we need this expressed in Astronomical Units. One A.U. is 149,598,000 km, so the value we need for A is:

4.39 x 10

^{-5}A.U.

Plugging those two numbers into the formula, we get:

P

^{2}* (3 x 10^{-6}) = (4.39 x 10^{-5})^{3}

P^{2}* (3 x 10^{-6}) = 8.47 x 10^{-14}

P^{2}= (8.47 x 10^{-14}) / (3 x 10^{-6})

P^{2}= 2.82 x 10^{-8}

P = 1.68 x 10^{-4}years

... which works out to 88.4 minutes. And, indeed, the space shuttle does take about this long to orbit the Earth once.

Now, let's try it with a 100 kilometer orbit above the surface of Mars:

Mass of Mars = 6.4 x 10

^{23}kg = 3.2 x 10^{-7}solar masses

Radius of orbit = 100 km (orbital altitude) + 3397 km (radius of Mars) = 3497 km = 2.3 x 10^{-5}A.U.

P^{2}* (3.2 x 10^{-7}) = (2.3 x 10^{-5}A.U.)^{3}

P^{2}= (2.3 x 10^{-5}A.U.)^{3}/ (3.2 x 10^{-7}) = 4 x 10^{-8}

P = 2 x 10^{-4}years = 105 minutes.

Not surprising that this is similar to the period for our low-Earth orbit above. Mars is only about 1/10 the mass of the Earth, but our orbital radius was about half as high as before (and 1/2 cubed is 1/8), so the two factors nearly cancel each other out.

## Why rockets are so big[edit | hide]

You've doubtlessly seen the footage of the Apollo moon mission launches. An enormous Saturn V rocket, hundreds of feet tall, lumbered off the launch pad on an enormous column of flame. Yet the actual Apollo spacecraft was just a tiny cylinder perched atop it, with an even smaller cone on top of *that* where the crew actually lived. Why was the rocket so big, and the actual usable space so small?

Cars can pull themselves along the ground by spinning rubber tires. Boats can push water through their propellers. Airplanes can push air through their propellers or turbines. Rockets, on the other hand, have none of these options. Every ounce of thrust their engines produce has to come through the expenditure of onboard propellant -- in other words, they accelerate forward by throwing material backward. (Boats and airplanes also accelerate forward by throwing material backward, but they get this material from the environment around them. Rockets have to carry all this "reaction mass" on board.) This *severely* limits the efficiency of a rocket engine when compared with a fluid-breathing or surface-friction engine, even moreso than the need to carry their own oxygen to combust with their fuel. Even worse, it means that at the start of your flight, you have to produce that much *more* thrust just to push all your unburned fuel along with you, so each kilogram of fuel you add provides progressively less and less total acceleration. This cascade effect can add up very quickly. The equation for how much *total* acceleration your rocket can undergo before it runs out of fuel -- the total "delta-v budget" of your rocket -- was derived by Tsielkovsky over a century ago:

Total delta-v = v_{e} * ln(M/M_{e})

... where v_{e} is the exhaust velocity of your engines, ln means "natural log" (there's a button for this on all scientific calculators), M is the mass of the rocket *with* fuel, and M_{e} is the mass of the rocket *without* fuel (the empty weight). M/M_{e} is sometimes called the "mass ratio" of the rocket.

The v_{e} for, say, the Space Shuttle's main engines is about 4500 meters per second. In order to orbit the Earth, the Space Shuttle must travel at 7800 meters/sec, and it must be about 300 kilometers above the Earth's surface (it requires another 1000-1500 m/s of delta-v to lift it that high and overcome atmospheric drag along the way). This means it needs a total delta-v of around 9000 m/s, which is twice its own exhaust velocity. From the rocket equation above, this means its M/M_{e} ratio must be *e*^{2}, or 7.39. The shuttle's weight with fuel must be over *seven times as high* as its weight without fuel! Discarding its spent solid rocket boosters in mid-flight (a trick similar to staging) can help a little, but not much.

With such a stultifying mass ratio *just* to get into Earth orbit, you can see why flying to other planets in a matter of days -- or worse, flying to another star within a human lifetime -- just isn't practical for modern chemically-propelled rockets. Most hard SF authors will solve this problem by using more exotic forms of rocket propulsion which have much much higher exhaust velocities, or which can derive their propellant from someplace other than the rocket's fuel tanks. These include:

- Nuclear fission (NERVA) engines
- Ion engines, such as those on the
*Dawn*and*Deep Space One*spacecraft - The Orion Drive
- Controlled nuclear fusion engines
- Ramscoops
- Space sails
- Laser propulsion

With the exception of ion engines, all of these are mere drawing-board designs at present, and all of them have practical problems. NERVA engines require shielding to protect the crew (and the ship's more delicate electronics) from their radioactivity, but saving weight is so important that there is only enough shielding to protect a cone in front of the reactor. Ion engines have extremely low thrust levels (the engines on the *Dawn* spacecraft can, at max throttle, produce about 1/3 of an ounce of thrust). Orion drive requires an enormous pusher plate that dramatically increases the dead weight the spacecraft has to carry. Controlled nuclear fusion has never been accomplished, at least not in a way that produces more energy than it consumes. Ramscoops rely not only on the controlled nuclear fusion of light hydrogen (which is even trickier than the controlled nuclear fusion of heavy hydrogen), but also on the ability to collect the extremely rarefied interstellar gas without inducing significant drag, which might not even be possible.

But even if controlled nuclear fusion *does* become a reality (allowing what Robert Heinlein called a torch), that still won't eliminate the need for big rockets if you want to get anywhere in a reasonable amount of time. Sure, your exhaust velocity might now be on the order of (say) 2% of light speed, but the rocket equation still applies. If you want to accelerate at 1*g* to the half-way point between Earth and Saturn, then decelerate at 1*g* for the rest of the trip, your total delta-v budget will be about 2% of light speed -- the same as your own exhaust velocity. You'd *still* need a mass ratio of *e*, meaning your spacecraft's fueled weight will be 2.718 times its empty weight. You're still stuck with a big rocket. And when you get to Saturn, you'll be out of fuel. You'll need to completely refill your fuel tanks if you want to make the return trip to Earth. Forget about the notion of a "ship" patrolling the "seas of interplanetary space" for months on end, hopping from planet to planet without refueling.

## World Building[edit | hide]

We humans evolved on, and (so far) all grew up on, Earth. We instinctively expect the air to be breathable, the temperature to be livable, the gravity to be 9.8 m/s^{2}, the days to last 24 hours, trees and grass, animals and plants and fungi, et cetera, et cetera.

The sad fact is, though, that no other planet we've detected thus far is even remotely habitable by human standards. The bigger ones are Jupiter-like balls of gas, while the smaller ones are almost universally airless. The few worlds we've found that *do* have both an atmosphere and a solid surface have been blanketed in gases that no human can breathe, at pressures anywhere from near-vacuum to 90 times Earth's sea level. While it's theoretically *possible* that a planet out there might harbor life as we know it, it would have to fit a long, narrow list of parameters, and even then, the kind of life that might have actually evolved there will most likely be very different from the multi-cellular-eukaryote-rich biome inhabiting Mother Terra.

In order for a planet to be able to support life as we know it on its surface *at all*, it will have to lie in a very narrow range of distances from its parent star. Too close, and any water would evaporate. Too far, and any water would freeze. Liquid water -- and life as we know it requires liquid water -- can only exist if the planet lies within that narrow zone where it's receiving just the right amount of energy from its star for the surface temperature to allow it. This is called the star's "comfort zone," or "Goldilocks Zone" (as in: not too close, not too far, but just right). The exact width of a star's Goldilocks zone is a matter of some debate, due to the fact that some atmospheres can trap heat (*cough* Venus *cough*) and some can't, and a number of other factors that astro-geologists can make whole careers out of. All we can say for sure is that, for a star as bright and hot as the sun, Venus is too close, Earth is clearly within the Goldilocks zone, and Mars is *probably* close to the tail end of it.

How far away from the star the Goldilocks zone is depends on the star's energy output. A very dim red dwarf star, like Wolf 359, would require a planet to be only about 1.5 million kilometers away from it to receive as much energy as Earth does from our sun -- that's only 0.01 A.U., 1% of the Earth-sun distance. A bright and powerful star like Sirius A, on the other hand, would require a planet to be 5 A.U. away from it to receive as much energy as the Earth does from the sun.

Interestingly, both of those distances have potentially disastrous consequences. If a planet is only 0.01 A.U. away from its star, the star's tidal influence is going to be enormous. The strength of tidal forces varies directly with the larger object's (i.e. the star's) mass, but inversely with distance *cubed*. The tidal forces on a planet only 0.01 A.U. from a star 1/10 the mass of the sun are, therefore, going to be 0.1 / 0.01^{3} = **100,000** times as strong as the tidal forces the Earth experiences from the sun. This all but guarantees that the planet will be locked in synchronous rotation with its star -- that is, its rotational period must match its orbital period, so the same side is always facing the star. One side of such a planet would be in perpetual daylight, while the other would be in perpetual night. The climate on such a world would be much different than the climate on Earth.

Dim stars also have the disadvantage that their Goldilocks Zones are going to be narrower. There is disagreement as to exactly how wide the Goldilocks Zone around the sun is -- different models compute widths anywhere from 0.5 A.U. down to 0.02 A.U. -- but however wide the zone actually is, it will be proportionally narrower with a dimmer star (and wider with a brighter star). The star 61 Cygni is about 1/10 of the sun's brightness, so its Goldilocks Zone will be (the square root of 1/10) of the sun's, or a little less than 1/3 of the sun's Goldilocks Zone distance. But this means both the *inner* edge and the *outer* edge of the Goldilocks Zone will be 1/3 of the distance compared with the sun -- and that means the zone as a whole will only be 1/3 as wide. The narrower the Goldilocks Zone, the less a chance that a planet would happen to have formed within it.

Worse, many red dwarf stars -- Wolf 359 included -- are *flare stars*, which emit semi-regular bursts of X-rays every bit as powerful as those emitted from a flare taking place on the sun. At 0.01 A.U., that much ionizing radiation can easily disassemble the organic molecules necessary for life. And X-rays can scatter (e.g. bend around corners), which is why the dental hygienist always leaves the room and closes the door when (s)he takes an X-ray picture of your teeth. Regular flare outbursts so close by probably means that any life would have to be buried underground.

A planet orbiting Sirius A at 5 A.U. wouldn't have any of these problems, of course, but it runs into another issue. Sirius is a binary system. Sirius B (a white dwarf) makes one complete orbit around Sirius A every half century, and at one point in this orbit the two stars come within 8 A.U. of each other. As any budding astrophysicist will tell you, the three-body problem is a chaotic one for which there is no solution. Any planet orbiting Sirius A farther away than 1/4 of this 8 A.U. closest-approach distance will be thrown out of the star system by Sirius B's gravity. The *farthest* a stable planetary orbit can be from Sirius A is, therefore, only 2 A.U. -- which is barely 2/5 of the Goldilocks Zone distance. Therefore, no planet can exist in the habitable, liquid water zone around Sirius A. (A planet could theoretically orbit *both* Sirius A and Sirius B as a pair, but then its *minimum* orbital distance has to be at least four times the *greatest* separation distance between the two stars in their orbit of each other. Sirius B's orbit is rather eccentric, and at one point in its orbit it's over 30 A.U. away from Sirius A. A planet orbiting both Sirius A and B would therefore need to be at least 120 A.U. away from their common center of mass, and at that distance the combined brightness of Sirius A and Sirius B would be far too weak to keep the planet from freezing.)

Even if a planet happens to lie within the Goldilocks Zone, that's no guarantee that it can harbor surface life -- let alone that life will actually arise there on its own, or that said life will have had sufficient time to evolve to the point where space-faring beings can emerge. The atmospheric pressure must both be high enough for liquid water to exist, and that can't happen unless the planet has sufficiently strong surface gravity to keep its atmosphere from escaping into space. The formula for determining the surface gravity of a planet is as follows:

- surface gravitational field strength = G * ρ * 4/3 * π * R

... where G is Newton's gravitational constant (6.6738 x 10^{-11} m^{3}/(kg s^{2}) ), ρ is the average density of the planet in kg/m^{3}, π is 3.14159, and R is the radius of the planet (half the planet's diameter) in meters. The result will be in meters per second squared.

As an example, the Earth's radius is 6,371,000 meters, and Earth's average density is 5515 kg/m^{3}. Plugging those into the formula above, we get:

Earth's surface gravity = G * ρ * 4/3 * π * R

= 6.6738 x 10^{-11}m^{3}/(kg s^{2}) * 5515 kg/m^{3}* 3.14159 * 6,371,000 m

= 9.822 m/s^{2}

... which is, in fact, how fast things accelerate downward near the surface of the Earth when you drop them. Mars, by contrast, only has a radius of 3,380,000 meters and an average density of 3930 kg/m^{3}, so its surface gravity is only 3.71 m/s^{2}, about 38% of Earth's.

You'll note that the Martian atmosphere is extremely thin, less than 1% of the surface pressure of Earth's atmosphere. One factor that contributes to Mars's thin atmosphere is this low surface gravity. Despite being *farther* from the sun than the Earth, and thus receiving *less* heat that could potentially boil its atmosphere away into space, Mars still has less of an atmosphere than the Earth does. A resonably strong surface gravity may be *required* for a planet to retain a thick atmosphere. There are exceptions in our own solar system, of course: Saturn's moon Titan has less than a sixth of Earth's surface gravity yet its surface atmospheric pressure is higher than Earth's, and while Venus is both closer to the sun *and* has only 90% of Earth's surface gravity its surface pressure is *ninety times* that of Earth's atmosphere. But you need at least *some* gravity, and possibly quite a lot of gravity, to retain an atmosphere within the Goldilocks Zone.

Another factor that can mean no life-bearing planets are possible in a given star system is the lack of heavy elements. The Milky Way galaxy is over ten billion years old. When it first formed, it consisted almost entirely of hydrogen and helium; almost no heavier elements (like carbon and the other elements necessary for organic life) existed. Several generations of stars have been born and died since then, and some of the more spectacular star deaths have peppered the interstellar medium with heavy elements synthesized by those stars' death throes. The sun, for instance, is a third-generation star -- the cloud of gas and dust out of which it formed contained material expelled by a supernova which, in turn, had formed out of an earlier cloud that contained material from an even earlier supernova. This is why there was enough carbon, oxygen, silicon, iron, etc. to form solid, rocky planets and organic molecules. Astrophysicists refer to all elements heavier than helium as "metals" (even if the element in question is oxygen or neon), and sometimes call a star system's heavy element abundance its "metallicity."

By contrast, Barnard's Star (a red dwarf approximately 6 light-years from the sun) formed in the Milky Way's first wave of star formation. It has almost no heavy elements. If the star itself is metal-poor, that means the cloud out of which it formed was also metal-poor, and therefore any planets that would have formed out of that cloud would be metal-poor as well. There might be some Jupiter-like balls of hydrogen or helium orbiting Barnard's Star, but there isn't going to be anything with a solid surface.

So, to sum up, the requirements for a given planet to be *able* to harbor life of *any kind* on its surface are:

- The planet must lie within the Goldilocks Zone for its star.
- The star cannot be too dim, since this will mean its Goldilocks Zone will be too narrow, any planet in the zone will be in synchronous rotation with the star, and the Goldilocks Zone will lie within the Danger Zone for stellar flares.
- If a binary star system, the companion star cannot come closer to the primary than 4 times the Goldilocks Zone distance.
- The star system cannot be metal-poor, or (if its metallicity isn't known) so old that it would have formed when the galactic medium was still metal-poor.
- The planet cannot be too small or light, as this will prevent it from retaining an atmosphere.

If your planet passes these five criteria, it's a candidate for surface life -- and by "life", I mean naturally-evolving microorganisms such as Earth's bacteria, or terrestrial life introduced by Terraforming. If you want your world to be home to *big* beasts, such as terrestrial trees or mushrooms or tool-making apes, which evolved there *on their own* without outside help, you're going to need one more crucial ingredient:

- The star must have been shining at roughly the same energy output for at least a couple billion years, in order to give time for complex life to have evoled.

This last requirement is a real buzzkill, as it eliminates damn near every bright star you can see in Earth's night sky. Big, bright stars like Sirius A only live for a few hundred million years before they run out of gas. (The candle that burns twice as bright lasts half as long, after all.) Red giant stars like Arcturus *had* a long, stable lifetime as a dimmer star in the past, but will only last for a couple of million years at the red giant stage -- so if they did harbor life bearing planets in the past, those ecosystems were snuffed out when the star expanded to its current red giant state, and any planets in the star's *new* Goldilocks Zone won't have long enough for evolution to run its course.

See the Useful Notes article on Local Stars if you want to pick a home for your theoretical planet from among our stellar neighbors. See the Useful Notes article on Planets if you want to put even more realism into the worlds you create.

Oh ... and if your planet has any moons, don't forget to use our old formula P^{2}M = A^{3} to calculate how long their orbital periods are!

## Aliens[edit | hide]

Two separate "So You Want To" articles now exist to deal with the realism aspects of creating your own aliens. They are:

Of particular import to any story involving space travel is the "Believable space-faring aliens" section of the first article.

## Deviation: Limiting the Damage[edit | hide]

Let's say the idea of a spaceship carying 10 times its empty weight in fuel sickens you. You want the space aboard your space ship to house your colorful characters, dazzling weapons, holo-decks, shopping malls, and other fun and excitement -- not deck after deck full of boring old propellant. And you want to allow for long patrols without having to refuel at every destination. So, you elect to go the route of the *Honorverse*, and equip your spaceship with a gravity-manipulation Reactionless Drive that allows her to accelerate without throwing material out of her tailpipe. Problem solved, right? And now that you've given your civilization gravity-manipulation technology, that also eliminates your problem of having your characters float around in zero gee; they can now spill liquids without spraying them all over the walls and play ping-pong to their heart's content while riding between the planets.

But hold on. You've also opened up a can of worms.

First, if you allow them to accelerate without pushing anything, they are now violating one of the most basic laws known to physics: the *conservation of momentum*. In the real world, you can't apply a force to an object in one direction without causing an equal-and-opposite force on some other object. Rockets fly up because their exhaust flies down. Jumping up pushes the Earth ever-so-slightly downward; falling back to the ground afterward pulls the Earth ever-so-slightly up. By letting your space ship violate this basic law, you're saying that momentum *is not always conserved.* What other circumstances in your universe will cause momentum not to be conserved? Do the laws of Newton simply get held in abeyance every time someone switches on a gravity generator? Are there natural phenomena that accomplish the same thing?

Second, are you also violating the conservation of energy? A 1000 tonne spaceship traveling 1/10 of the speed of light has a kinetic energy of 450 quintillion Joules, equal to 100,000 megatons of TNT. That energy had to come from somewhere. Did it come from burning some sort of fuel on board your space ship, to power the generators? If you used the thermonuclear fusion of hydrogen into helium as your fuel source, and you managed to Hand Wave a fusion reactor technology that's nearly 100% efficient, you'd have to burn at least 350 tonnes of hydrogen to obtain that much energy, which is a third of your spaceship's own mass. (This isn't as bad a mass-ratio situation as if you'd used a plain-old momentum-conserving fusion rocket, but it's still pretty significant.) And you'll have to burn just as much again to slow your space ship back down at the end of your trip. If this is too much for you, and you decide your reaction-less drive simply works by tapping into the magical gravity waves of the universe and surfing along them with only minimal power requirements, then your space ship's kinetic energy is being created *ex nihilo*. You've got yourself a free energy machine! Just strap your space ship to one end of a long lever, strap the other end to a huge electric generator, and fly in circles. You can generate enough energy to power your entire civilization this way, with no cost in natural resources. This will play absolute *havoc* with your fictional economy. You'll have to throw away that whole book you were going to write about your space empires' war over Space Oil.

Third, if any 1000 tonne space ship can easily accelerate to a tenth of light speed, then every two-bit spaceship owner has in his possession a weapon of mass destruction. Those 100,000 megatons of TNT-equivalent kinetic energy will act like 100,000 megatons of *actual* TNT if they strike a planet. Want a future populated by plucky tramp space-freighters and sneaky space pirates? It ain't gonna happen if every ship is a Hiroshima-on-steroids waiting to happen. Every spacecraft captain will be on too short a leash. Any spacecraft that even *looks* suspicious will be killed before it can become a threat. (And, yes, *all* fast-moving spacecraft, and even stationary spacecraft, will eventually be detected -- there ain't no Stealth in Space.) Any civilization that didn't take these precautions wouldn't *be* a civilization for very long. This might work as a setting for your future totalitarian dystopia, but is hardly the right world for romantic swashbuckling adventures.

The potential damage done to your story by a Reactionless Drive is just one example of the broader principle. *Any* technological marvel that sidesteps the Real Life roadblocks facing space travel has the potential for unintended consequences. Thermonuclear torchships? They've got the same "spaceship = weapon of mass destruction" problem that reaction-less drives do, albeit on a more manageable scale.

So what do you do when you *need* your characters to be able to move between the stars faster-than-light, or teleport, or have a Tractor Beam, or do any of the other myriad things that our current best guesses at the law of nature say are impossible? You set the technology up in such a way as to **limit the damage** to your story and your setting. Maybe your Deflector Shields are magnetic, and can only affect charged particles and ferromagnetic metals -- and your spaceship needs to open up holes in its shields to shoot iron slugs or particle beams at an enemy. Maybe the high speeds needed to traverse interplanetary distances in days or hours are imparted not by your space freighter's own engines, but by planet-side pushers that will only push it onto a predictable course, thereby eliminating the threat of rogue spaceship commanders turning their vehicles into WMDs. Maybe your transporters only let you beam between one transporter pad and another (unlike the transporters in a certain softer SF franchise). Maybe the violations of the Laws of Thermodynamics needed to make Stealth in Space work are curtailed in some way that prevents you from getting useful energy out of any warm object (which, like some types of Reactionless Drive, would have driven your Space Oil companies out of business).

## Faster-Than-Light Travel[edit | hide]

FTL Travel is one of the bigger thorns in the side of the Hard SF genre. Special Relativity makes it absolutely clear: it is physically impossible to accelerate an object with any kind of mass so that it's moving faster than the speed of light. Even accelerating an object *to* the speed of light would require an infinite amount of energy. However, we've also pretty much established that there are no other technological species on any planet in the Solar system other than Earth. If we want to have space adventures involving high-tech aliens, we'll have to travel to other star systems, and the distances involved are so enormous that it would take years to get from one star to another if you were limited to sub-light speeds. Science Fiction writers have had to compromise, and allow *some* means of travelling faster-than-light which didn't turn their universe into something totally unrecognizable to a modern reader. Therefore, the ability to move faster-than-light has received more attention in SF than any other fantastic concept as to ways to limit the damage of having it around.

The very worst problem with FTL travel (or even just FTL Radio) is a certain extremely strange consequence of Time Dilation. When travelling at any speed, even a brisk walk, relative to somebody else, you'll see his clock move slower than yours -- but he'll see *your* clock move slower than *his*. This extremely counter-intuitive state of affairs means that some distant events in the universe which are in your future are in the other guy's past, and vice-versa. Without FTL travel, though, this isn't a problem. Einstein and Minkowsky established that for any event that's in Observer A's future and Observer B's past, no matter how far in Observer A's future the event is, it will always be far enough away that any *light-speed signals* from this event would not reach Observer A until the event was also in Observer A's past. When plotted on a space-time graph, the signals from the event would stretch out in space-time in a "light cone," which guarantees that the signal will not reach any observer in the universe until the event is in that observer's past. To put it another way, let's say that in Observer A's reference frame, Event 1 occurs before Event 2, but in Observer B's reference frame, Event 2 occurs before Event 1. Light cones maintains *causality* by ensuring that, if Observer A would find out about Event 1 before Event 2, Observer B *cannot* find out about Event 2 before information about Event 1 is theoretically available to him.

Here's an example: Suppose Observer A is standing on Earth, and Observer B is in a space ship, coasting in a straight line at 86.60254% of the speed of light. This gives him a gamma (γ) factor of exactly 2. When the space ship passes by Earth, both Observer A and Observer B synchronize their clocks at 5:00 PM. In Observer A's frame of reference, when his clock reads 7:00 PM, Observer B's clock will read 6:00 PM. However, in Observer B's frame of reference, when his clock reads 7:00 PM, Observer A's clock will read 6:00 PM. At 6:20 PM on Observer A's clock, an event happens on Earth -- the winning State Lottery numbers are announced. At 7 PM on Observer A's clock, this event is 40 minutes in Observer A's past; but at 7 PM on Observer B's clock, this event is still 20 minutes in Observer B's future. It's not just that Observer B *perceives* it to be in the future, it really *is* in the future, it really hasn't happened yet. What prevents Observer B from knowing about the event before it happens in his reference frame is that it takes *time* for any information about the event to reach him. At 6:20 PM in Observer A's reference frame, Observer B's clock would only read 5:40 PM, but Observer B would be 69.282 light-minutes away from Earth; if Observer A radioed the winning lottery numbers to Observer B at this moment, they'd take 521 minutes in Observer A's reference frame to reach Observer B's space ship, at which point Observer B's clock would read 9:40 PM and the event would be 4 hours in Observer B's past. Even if Observer B magically reversed his velocity at 5:40 PM on his clock, so that he was headed *toward* Earth at 0.866*c* instead of away from it from that moment onward, the radio signal would still take 37.128 minutes in Observer A's frame of reference to reach the space ship.

But by going faster than light, even just FTL Radio, you *can* receive information about events that are in your own future. You can perceive Event 2, which was caused by Event 1, before Event 1 actually occurs in your reference frame. In our lottery-winning scenario above, suppose Observer A and Observer B had a Subspace Ansible that allowed instant communication no matter how far apart they were. Observer A could send the winning lottery numbers to Observer B's space ship at 6:20 PM on Observer A's clock. With instantaneous communication, the numbers would arrive on board the space ship at 5:40 PM on Observer B's clock. If Observer B then sent the same numbers *back to Observer A* over the same subspace ansible, they'd arrive on Earth at 5:20 PM on Observer A's clock. Observer A would have the winning lottery numbers *an hour before they were announced.*

In other words, **Time Travel**. This is the part where unless you're literally the winner of a hard-SF literary award, you have to be reminded that you're not even figuratively the winner of a hard-SF literary award. Writing a story in which time travel is even possible is definitely not recommended for those of you that haven't won a hard-SF literary award.

How do veteran SF writers handle the time travel consequences of FTL travel? Most of them don't. They simply sweep it under the rug and hope no one will notice. Those authors who do address it often end up with bizarre universes where wars are fought before they've even started, and characters can shoot their own grandfathers.

The other main problem with FTL travel is what it can do to life in your universe even *without* time travel. If your space pirates can just jump into hyperspace at the first sign of trouble, you'll never have any exciting space battles. If you can ram a planet or another spacecraft while travelling at FTL speeds, you risk turning even the tiniest FTL shuttle-craft into a planet-killer that will put even the largest, fastest slower-than-light kamikaze to shame.

Maybe faster-than-light travel only works between certain rare points in space, and your ships must maneuver in normal space to get to and from them. Maybe FTL movement is impossible within some large distance from a gravity source, requiring your space ships to leave the solar system -- or at least leave Earth orbit -- before they can go FTL. Maybe your space pirates *can* jump to hyperspace at the first sign of trouble, but so can your space cops, and they have FTL weapons they can shoot at each other while in hyperspace.

The third problem with FTL travel is more practical: *we don't know how to do it in Real Life*. Every attempt to come up with a way to do so has run into intractable problems. Quantum entanglement can occur instantaneously across vast distances, but it can't convey any actual information faster than *c*. The Alcubierre space warp has a lot of things wrong with it. What wormholes are depends on which type of wormholes they are. The wormholes that general relativity posits in uncharged, non-rotating eternal black holes are Schwarzschild wormholes. If they even exist, they will spontaneously collapse faster than it's possible to traverse them, so they don't make enough sense as a mode of travel. One candidate is Ellis drainholes^{ [dead link]} and a special case of Ellis drainhole, called an Ellis wormhole^{ [dead link]}, but you might want to follow Orion's Arm's example in this case and make sure Ellis drainholes start out with both the wormhole mouths at the same place, and that very powerful ships are required to move the mouths to a useful distance. You, as the writer, will have to *invent* a way to travel faster than light, and then cover all the repercussions of the method you come up with. But first, you might want to earn a university-level physics degree before even coming up with the pitch for the story.