Anyone who has stood in a cold field waiting for a rocket launch knows the feeling: you drove for hours, set up the folding chair, and only then discovered that the window had slipped by a day. The fix is rarely better luck. It is a short, honest list of space-viewing assumptions written down before you leave the house, each with a note on how sure you are and how you will check it.
This checklist is built for amateur spaceflight fans, backyard observers and early-career space hobbyists. Treat it as an audit you can run in about twenty minutes, whether you are planning a launch trip, a satellite-pass evening or a small student payload project.
Why a space plan needs written assumptions
Spaceflight is full of moving targets. Launch times shift, orbits drift, clouds arrive early. When your plan lives only in your head, every one of those shifts is a surprise. When the plan is a page of assumptions, each shift becomes a line you can cross out and revisit.
There is a second payoff. A week later, when someone asks why you chose that viewing spot or that lens, the page answers for you. You see what you actually believed back then, rather than a tidier story your memory builds afterwards.
Step one: split the plan into the things you are taking for granted
Open a blank note and write the heading “I am assuming that…” at the top. Then fill in five buckets, even if some stay short.
- Timing. The launch or pass happens when the schedule says it does, and your clock and the published time zone match.
- Sky and weather. The horizon in your chosen direction is open, and cloud cover will stay thin enough to see anything.
- Geometry. The object will actually rise where you think it will, and at an angle your equipment can follow.
- Gear. Batteries last through a long cold wait, the tripod is stable, and the camera settings are ones you have already tried.
- People and logistics. The road is open, parking exists, and anyone travelling with you is on the same schedule.
Step two: attach a confidence level to each line
A bare list helps, but a list with confidence marks helps far more. Use a plain three-step scale: solid, shaky, or a guess. “Camera battery lasts two hours” is solid if you have tested it in the cold. “The pad faces my viewing direction” is a guess until you have looked at a map.
You will usually find that the guesses cluster around the parts of the trip you never thought about. That is the point of the exercise. It is easier to fix a guess on a Tuesday evening than on a dark roadside.
Step three: write the cheapest check next to every shaky line
For each assumption that is not solid, note one small action that would firm it up. Keep the checks cheap enough that you will actually do them.
- For timing, look at the latest published schedule on the morning you travel and again just before you leave.
- For the sky, compare two different forecast sources and note where they disagree.
- For geometry, sketch the horizon from your spot and mark where the object should appear.
- For gear, run a ten-minute dry setup in the garden with the same settings.
- For logistics, call or message whoever is driving and read the plan back to them.
A worked example: a low-orbit pass evening
Suppose you want to watch a bright pass of a satellite in low orbit. If orbits are new to you, a beginner-friendly primer covering orbits close to Earth explains why these objects cross the sky so quickly. A written assumptions page for the evening might read like this.
- I assume the pass starts at the listed minute (solid, since the listing was refreshed today).
- I assume the object climbs high enough to clear the rooftops to my south (shaky, so I will walk to the park first).
- I assume a bright pass is possible because the object is lit by the sun while I am in darkness (guess, so I will check the lit-or-shadowed note on the listing).
- I assume my phone will not dim at the worst moment (solid, I changed the screen timeout).
A second example: a launch trip that spans two days
Longer trips carry more hidden bets. Picture a drive to watch a rocket leave the pad. The assumptions page might include the following.
- The launch will not slip past the day I booked (shaky: slips are common, so I will arrange a flexible second night).
- The public viewing area will be open (guess: I will look for an official notice before leaving).
- Sound arrives some seconds after the light (solid, and worth telling first-timers so nobody walks off thinking nothing happened).
- My phone signal will fail in the crowd (shaky: I will download the schedule in advance and agree a meeting point).
If you have ever read about parking orbits and transfer paths, the writeup on how a geostationary orbit works is a handy companion for the geometry bucket, because it reminds you that where something appears in your sky depends on the orbit it is in.
Where the training world borrows the same habit
The habit is not unique to space. In IT operations, engineers keep an assumptions log inside design notes so that later readers can see what a decision rested on. One India-based website, NoOpsSchool, which describes itself as offering certification courses, consulting and services for IT professionals, sits in that corner of the technology world. The idea carries over to a launch trip neatly: write the belief down first, then test it.
Step four: schedule a review, then cross things out
An assumptions page is a living document. Set two review moments: one the evening before, and one at the site, before the event starts. At each, go through the list and change a mark if the facts changed. A shaky line that became solid gets a tick. A solid line that cracked gets rewritten and may trigger a plan change.
After the event, add a short last section. Which assumptions held, which failed, and which did you never think to write? Keep that section for the next trip. Over a handful of outings your own page becomes a personal starter template, tuned to the way you observe.
A compact audit you can copy
- Write the date, the event and the location at the top.
- List every assumption in the five buckets, one line each.
- Mark each line solid, shaky or a guess.
- Next to each shaky or guess line, add its cheapest check.
- Run the checks and update the marks.
- Decide whether the plan still holds, needs a backup, or should be moved.
- Review again on site, then add notes for next time.
The beauty of this audit is that it costs almost nothing and travels well. You can keep it in a phone note, a pocket notebook or a shared page for a group of friends. Pick whichever format you will really open; what counts is naming each bet.
Next time a launch window or a satellite pass calls you outdoors, spend those twenty minutes first. The sky will still do whatever it does, but you will know which parts of your evening were fact and which were hope, and your notes will show exactly what you learned.