Launch scrubs and delays, explained

Nothing tests a launch follower's patience like a scrub. You set the alarm, opened the stream, told your friends — and the rocket stays on the pad. It feels like failure. It usually is not. Delays are a normal, even healthy, part of spaceflight: a rocket that launches only when everything is right is a rocket whose team is doing its job.

Hold vs. scrub: the distinction that matters

These two words describe completely different situations, and mixing them up is the most common source of launch-day confusion.

A hold pauses the countdown. The clock stops, the team investigates or waits out a condition, and the attempt continues. Holds can be planned — built into the timeline to allow checks and to align the count with the window — or unplanned, when something needs attention. Hearing "we are holding" means the day is still alive.

A scrub ends the attempt. The team stands down, safes the vehicle, and starts working toward another day. Hearing "scrub" means: stop watching today, start watching the schedule for a new target.

The practical rule: a hold means stay on the stream; a scrub means close it and check back tomorrow.

Why launches scrub

Scrubs fall into a few familiar categories. None of them means the rocket is broken in any dramatic sense.

Weather. The most common cause, and the least negotiable. Launch commit criteria cover not just rain at the pad but upper-level winds, lightning risk within a radius, and cloud thickness rules that exist so tracking cameras can follow the flight. A beautiful blue sky at the viewing site can hide unacceptable winds at altitude — which is why "but it looks fine here" never settles the question.

Technical issues. A sensor reading out of family, a valve behaving oddly, a ground system glitch. Modern countdowns are heavily instrumented, and the philosophy is simple: any parameter outside its expected range stops the count until it is understood. Most of these turn out to be minor. The team treats them as major until proven otherwise, and that is exactly right.

Range problems. The launch range must be clear: no boats or aircraft in the hazard zones, tracking and safety systems operational. A stray vessel wandering into the exclusion area — it happens more often than you would think — can scrub a launch as surely as a storm.

Upstream delays. Sometimes the rocket is ready and the sky is clear, but the mission is not: a payload issue, a station scheduling conflict, or a previous launch slipping and taking the pad with it.

The 24-hour turnaround (and why it is rarely 24 hours)

After a scrub, teams often target the next day — but "tomorrow" in launch terms means the next available window, which follows orbital geometry, not the clock. As explained in the launch window guide, the next opportunity may open earlier or later than today's, and for some missions the geometry only lines up every few days.

There is also the human factor: detanking propellants, safing the vehicle, reviewing what happened, and resetting for another attempt takes real work. An "instantaneous window" mission that scrubs at T-minus 30 seconds needs the full recycle process before it can try again. Respect the turnaround; it is where diligence lives.

Delays before launch day

Not all delays happen on the pad. Missions routinely slip weeks or months while still in preparation — a NET date moves, a quarter becomes "under review," a manifest reshuffles. These pre-launch delays have their own causes:

• Hardware readiness: the rocket, payload, or ground systems need more testing.
• Manifest traffic: pads and ranges are shared resources; one mission's slip cascades.
• Regulatory steps: licenses, environmental reviews, and safety approvals run on their own timelines.
• Strategic pauses: sometimes an operator stands down a fleet after an anomaly to investigate — the reason schedules occasionally go quiet across many missions at once.

When a NET date moves by months, it is usually one of these, not a countdown problem. Read distant schedule changes as planning information, not as drama.

How to follow a delay without the frustration

1. Expect scrubs. For a first-time viewer, the healthiest assumption is that any given attempt might not fly. Veterans plan backup days before they travel.
2. Listen to the broadcast, not the timer. Third-party countdown clocks cannot tell you the count is holding; the commentary can. When the clock freezes, the broadcast will say why — or say that the team is still assessing.
3. Read the new listing fresh. After a scrub, do not assume "same time tomorrow." Check the new target, the new window, and the precision as if you had never seen the mission before.
4. Distinguish a slip from a problem. A mission moving from October to December is usually manifest planning. A mission scrubbing three days in a row is usually weather or a stubborn technical issue. Different causes, different expectations.
5. Do not confuse a delay with a failure. A scrubbed launch is a launch that did not happen — the rocket is intact, the team is working, and the mission continues. Conflating caution with failure is the fastest way to misunderstand how spaceflight works.

The bottom line

Rockets are unforgiving machines operated at the edge of their margins, and the culture of stopping the count at the first sign of trouble is what makes them as reliable as they are. Every scrub you watch is the system working as designed. The launch will happen when the vehicle, the weather, the range, and the geometry all agree — and no sooner. That patience is not a bug in the schedule. It is the schedule working.