Three days before lift-off, a launch campaign stops being an engineering problem and becomes a logistics one. The vehicle is stacked, the payload is encapsulated or nearly so, and most of what remains involves somebody signing something, somebody confirming something, and somebody deciding whether a marginal forecast is worth a hold.
That window is short, and it is unforgiving. Teams that treat the final 72 hours as a formality tend to discover otherwise. Here is what UK mission teams should be able to answer, in writing, before the countdown clock matters.
Weather: read the whole column, not just the pad
Ground-level wind speeds are the easiest number to look at and the least useful on their own. Your vehicle's limits will also cover upper-level winds, wind shear, turbulence, temperature, cloud cover, precipitation and the risk of triggered lightning. For a UK launch, add sea state and visibility if you have downrange recovery or tracking assets in the water.
By T-72 hours you should have fresh balloon soundings, not just model output, and a clear view of how much the models disagree with each other. Fast-moving Atlantic fronts can flip a forecast inside twelve hours, so decide now who has the authority to call a weather hold and how late that call can be made. If two people can make that decision, you do not have a decision-maker.
Range safety: airspace, sea lanes and the people who clear them
Range safety is a licensed activity, and its requirements do not bend because the schedule is tight. Confirm that notices to airmen and maritime warnings cover the full launch window plus margin, and that the hazard areas match the trajectory you are actually flying — not the one you filed weeks ago. That means talking to the air traffic providers, the coastguard and the relevant maritime authorities, and getting confirmation back rather than assuming silence means consent.
On the technical side, walk through the flight termination system, tracking and radar coverage, telemetry continuity and the emergency response plan agreed with local services. Also check the sea area itself. Fishing vessels, yachts and survey ships do not read your launch schedule, and a single unaccounted vessel inside the hazard area is a scrub.
Licensing: every document that needs a signature
UK launch activity sits under the Space Industry Act and its associated regulations, with the Civil Aviation Authority acting as the space regulator. Licences are typically required for launch operations, range control and, separately, for the operation of satellites in orbit. At T-72, the question is not whether you hold a licence — it is whether that licence covers the exact date, site and trajectory you intend to use. Variations exist, but they take time, and requesting one on the morning of a launch is not a plan.
Alongside the licence, confirm insurance and third-party liability cover, spectrum allocations for telemetry and command links, and any export control or customs paperwork attached to payload hardware. If you are unsure how any of this applies to your mission, take advice from a qualified regulatory or legal professional. This is general guidance, not a substitute for it.
Payload readiness: freeze it, then protect it
Configuration freeze should already be behind you, which means the mass properties, centre of gravity and separation interfaces are agreed and no one is quietly modifying software. Check battery state of charge and charging plans, remove-before-flight items, safe-and-arm status, and the full list of access restrictions on the payload. Late customer change requests have a way of arriving at exactly this moment; have a written route for assessing them, and a default answer of no.
Do a final documented walkdown with two people who did not do the previous walkdown. Fresh eyes catch the connector that is not quite seated.
Communications: test the loops you intend to use
Comms failures rarely announce themselves politely. Run through the following in the final three days, and actually place test calls rather than trusting that a line works because it did last month.
- Countdown net: primary and backup voice loops, who is on each, and who speaks when.
- Telemetry and command: ground station bookings confirmed, link budgets validated, backup path identified.
- Range and emergency services: direct numbers, not a general switchboard.
- Public and media: who is authorised to speak, what the holding statement says, and how a scrub is announced.
- Anomaly protocol: the agreed period of silence, and who breaks it.
A 72-hour sequence that works
Every campaign differs, but the shape of the final three days tends to be similar. Adapt the timings to your vehicle and site.
- T-72: all-hands readiness review. Each lead reports red, amber or green against their own checklist. Anything amber gets a named owner and a deadline.
- T-72 to T-48: regulatory and clearance confirmations in writing — licences, notices, insurance, spectrum.
- T-48: detailed weather brief and a decision on whether to proceed toward the first attempt in the window.
- T-36: ground segment and communications checks, including end-to-end telemetry with the actual payload.
- T-24: final range and weather confirmation. This is the last sensible point to stand down without burning the team.
- T-12: enter the countdown. Poll the console. Confirm hold criteria out loud so nobody has to invent them under pressure.
- T-4: propellant load, final configuration checks, range declared clear.
Keep one live list, not five documents
The most common failure in the last three days is not a technical one. It is a checklist that exists in four spreadsheets, two email threads and somebody's memory. Put every open item in one place, give each one a person's name, and review it at the same time each day.
Write your hold criteria down before you are tired and emotionally invested in flying. Rehearse the abort as carefully as you rehearse the launch. A launch team that can say no at T-30 minutes, cleanly and without argument, is a team that can be trusted to say yes.
Photo: Monstera Production / Pexels





