Space
Range Safety And Why Launches Get Scrubbed
A rocket is delayed far more often by ground conditions, tracking assets and public safety rules than by any fault with the vehicle sitting on the pad.
Spectators frequently watch a countdown stop with a clear sky overhead and no visible problem. The reasons are usually invisible from the viewing site, and most of them concern what happens if the flight goes wrong.
The range protects everything the rocket could fall on
American launch sites are surrounded by controlled corridors over water, and the flight path is chosen so that debris from a failure lands where nobody is. That corridor must be verified clear before liftoff.
Boats and aircraft stray into it constantly, and a single vessel that will not respond to a radio call is enough to hold a countdown until it leaves or the window closes.
The rule is not discretionary, because the entire justification for launching over a populated coastline rests on the corridor being empty.
Flight termination has to be demonstrably ready
Every vehicle carries a system capable of ending the flight if it departs its approved path. Historically this was commanded from the ground; increasingly the vehicle decides autonomously against rules loaded before flight.
That system is tested during the count, and any ambiguity in its status stops the launch regardless of how healthy the rocket is.
Autonomous termination reduced the ground infrastructure required and shortened the interval between launches, which is one reason cadence rose without new pads being built.
Weather rules cover more than visibility
Launch weather criteria are concerned mainly with electrical activity. A vehicle climbing through certain cloud types can trigger a lightning strike that would not otherwise have occurred.
Upper-level winds matter separately, because shear imposes structural loads during the transonic phase, and the wind profile is measured by balloon within the final hours.
Conditions at the recovery zone and at abort landing sites can also block a launch even when the pad itself is clear.
Shared infrastructure creates its own delays
Tracking radars, telemetry stations and the airspace above the site are shared resources, and other users have schedules. A failure in a downrange asset can scrub a flight the vehicle would have flown perfectly.
Where a launch supports crew or a station rendezvous, the acceptable window may be minutes long, so any hold at all becomes a scrub rather than a delay.
This is why cadence at a busy range depends heavily on how quickly a vehicle can be recycled for the next attempt.
Why scrubbing is the cheap outcome
A scrub costs propellant, staff time and public disappointment. A failure costs the payload, the vehicle, potentially the pad, and months of investigation before anyone flies again.
Given that asymmetry, teams set conservative limits in advance and follow them mechanically, precisely so that no one is making a judgment call under schedule pressure in the final minutes.
