A rescue mission that needs rescuing
In a bit of tech news that feels almost too neat to be accidental, the spacecraft sent up to rescue one satellite is now the one needing a rescue plan.
That craft’s Link, built by Katalyst Space Technologies for NASA’s first commercial satellite servicing job. Its assignment sounds tidy on paper: fly up to Swift, latch on and nudge the observatory higher before thin atmospheric drag keeps pulling it lower and lower. Swift is NASA’s gamma-ray observatory, and the price tag attached to it’s close to $500 million, so this isn’t a case of salvaging a forgotten shoebox with solar panels. There’s real hardware, real money and a real deadline sitting in low Earth orbit.
The timing was fairly tight even before anything went sideways. Link launched in early July and spent the next stretch doing what it was supposed to do. For a while, the mission looked on schedule. Then trouble showed up over the weekend, and the whole plan got a lot less tidy. A vehicle sent to extend another spacecraft’s life suddenly became another spacecraft that had to be kept alive. Space has a funny way of charging extra for confidence.
The irony here is hard to miss: the rescue craft can’t rescue anything if it can’t hold itself together first.
That’s where the urgency comes in. Swift keeps losing altitude. Orbit does not wait politely for engineering teams to have a good Monday. Every day that passes trims the room Link has to work with, because the spacecraft has to be stable enough to rendezvous, way, and do delicate work before the target sinks too far. If Link stays out of control for long, the rescue window for Swift keeps getting smaller and the mission starts to look less like a repair job and more like a race against physics.
What makes this story stand out is not just the hardware failure, at least not yet. It’s the setup. NASA handed a private company a job that had never been done this way before, and Katalyst had to build the mission fast, launch it in early July and head straight into the sort of orbital choreography that leaves very little room for sloppiness. The satellite is still there, the target is still there, and the clock is still ticking. The question now is whether Link can be steadied quickly enough for the rest of the plan to matter.
That’s the part engineers are wrestling with next.
What went wrong on Link
For a spacecraft meant to babysit NASA’s Swift boost mission, Link has had a very uncooperative week.
The trouble started during a communications gap. Instead of sitting still and keeping its nose where engineers wanted it, the satellite began rotating on more than one axis. In plain terms, it lost its attitude. That matters a lot in orbit, where a vehicle can’t just “look around” the way a person would. It has to know exactly how it’s pointed so its antennas, sensors, thrusters and power system can all do their jobs without stepping on each other’s toes.
The bigger headache came from the hardware that normally keeps that orientation under control. Two of Link’s three reaction wheels failed, which left the spacecraft without the usual way to steady itself and point precisely. Reaction wheels are one of those parts nobody notices until they quit. They spin internally to nudge the spacecraft in the opposite direction, and when they’re working, the whole system feels almost boring. The spacecraft stops behaving like a machine with a plan and starts behaving like a very expensive top, when they fail.
Engineers also found a separate problem with the cold-gas thrusters used for fine attitude control. Those thrusters are the little corrections that help a spacecraft trim its position when the larger controls aren’t enough. The options narrow fast, if they’re unreliable too. At that point, Link had lost both of the usual tools for holding a steady line.
In orbit, a small control failure can snowball quickly. Once the spacecraft starts to tumble, every system that depends on pointing becomes harder to trust.
After more than a day without contact, the spacecraft finally did what it was designed to do in exactly this kind of mess: it entered safe mode and reset itself. That built-in protection cycled power through the vehicle, which can sometimes clear out bad states or stop a failure from spreading. It also bought the ground team a way back in. Without that reboot, Link might have slipped into total silence.
But the reset may have come with its own cost. Engineers think the reboot likely caused a thermal spike that overheated electronics tied to the reaction wheels. That’s a grim little chain reaction. A system trips, the spacecraft restarts, temperatures jump and the very hardware already under strain gets pushed harder. No one has called the case closed, though. The team hasn’t ruled out an impact from orbital debris, and an internal fault is still on the table as well. Space isn’t exactly a clean room.
The exact sequence matters because it tells engineers where to look next. If debris struck the spacecraft, the damage could be physical and obvious once Link can be inspected properly. The evidence may be subtler, buried in temperature data, power traces, or a component that simply gave up the ghost at the wrong time, if the problem began inside the bus. Either way, the failure didn’t happen in a vacuum, even if the setting very much is one.
Two onboard cameras should help with that diagnosis once Link is back under better control. They’ll give the team a way to inspect the spacecraft for visible damage, check whether anything’s bent, scorched, or loose, and figure out whether the trouble is a one-off or part of a larger systems problem. That kind of image can save a lot of guessing, assuming the vehicle can be steadied enough to point them where they need to look.
For NASA, this is a messy moment in a mission that had already been moving at full speed. The agency hired Katalyst Space Technologies to attempt the first commercial servicing job for one of its satellites, a move spelled out when the contract was awarded for the Swift rescue effort. Link was supposed to help preserve a working observatory, not become the patient. Yet here it is, limping through its own emergency while the clock on the NASA Swift mission keeps ticking. What happens next depends on whether the spacecraft can be brought back from the spin without making the damage worse.
The recovery plan in orbit
The odd part of this story is that the spacecraft sent out to help NASA’s Swift observatory has become the one that needs help first. Katalyst Space Technologies is now trying to calm Link down with the pieces that still answer the phone, so to speak, while its team near Denver keeps a close eye on the numbers rolling in from orbit. The original plan, which NASA lays out on its Swift Boost mission page, is still the same on paper: get to Swift, get close, and keep the observatory alive a little longer. Right now, though, the nearer problem is Link’s own spacecraft servicing hardware and whether it can be coaxed back into a stable attitude before anyone even thinks about the target.
So the team has switched to an awkward but sensible workaround. The plasma thrusters, which were built mainly to raise the orbit, are being used to counter the spin. That’s not their only trick. Because those electric engines can swivel on two axes, they can also help with pointing, which gives engineers a bit more room to improvise than they would have with a fixed nozzle and a bad day. In space, “use what still works” often becomes a full-time job.
When a spacecraft starts tumbling, the cleanest fix is rarely the one you planned for on launch day.
That approach seems to be paying off, at least so far. Link has already slowed its tumble by about half, from roughly nine degrees per second down to around four. That may not sound elegant, and it definitely isn’t elegant, but it’s the kind of progress mission controllers like to see before they try anything fancier. Every bit of spin reduction improves the odds that Link will hold a steadier line of communication, which should give the ground team richer telemetry instead of the chopped-up, frustratingly incomplete data streams they’ve had to work with so far.
Once the vehicle is calmer, the next move is software. Katalyst plans to upload a fresh control algorithm that mixes the one healthy reaction wheel with the remaining thrusters and the electric propulsion system. That sounds simple only if you ignore the part where every actuator’s its own personality and every failure changes the math. The new mode needs to do a lot at once: keep Link from drifting back into an uncontrolled roll, preserve enough pointing accuracy for contact and avoid pushing any single component into another failure. Spacecraft control is a little like trying to steer a shopping cart with one wheel locked, except the cart is moving at orbital speed and nobody gets to stand up and inspect the axle.
Katalyst’s guidance and control engineers are working directly with NASA to remap the software and make that stabilized mode possible. That collaboration matters because the system isn’t just being patched; it’s being rewritten for the reality the spacecraft actually has, not the one it was supposed to have when it left Earth. The goal is to blend hardware, software and whatever margin remains into something that can hold attitude long enough for the next phase. If the spin comes down a bit more, the signal should get cleaner, the telemetry should fill in, and the whole operation stops feeling like an emergency juggling act.
For now, the mission lives inside a narrow corridor of possibility. Link doesn’t need to be perfect. It just needs to be steady enough to keep talking, keep pointing and keep swallowing new commands without flinching. In satellite servicing, that’s often the difference between a rescue attempt and a very expensive lesson.
Why the Swift rescue still matters
The awkward part of this story is that Swift hasn’t stopped needing help just because Link started having its own bad day. And the gamma-ray observatory is still slipping lower in orbit, a little at a time and that drop doesn’t care whether the rescue spacecraft is behaving itself or not. If the altitude keeps falling, the window for a clean approach narrows fast. In a few months, the math could get ugly enough that a capture attempt stops making sense.
In orbit, the calendar is ruthless. Miss the slot, and the mission doesn’t wait around for a second invite.
Katalyst still wants to make a late-August push toward Swift if it can steady Link in time. That date isn’t just a nice target on a planning slide. It’s tied to how long the observatory can stay high enough for another spacecraft to meet it in a controlled way. A successful rendezvous could bring Link within a few dozen meters of Swift, close enough for inspection and, if everything lines up, a grab attempt. That’s a very tight dance for two spacecraft that are already moving fast and trying to avoid making a mess of one another.
The clock matters here because Swift isn’t parked in some leisurely, high-altitude graveyard orbit. It’s being nibbled on by atmospheric drag, which sounds gentle until you remember that even a thin smear of air can drag a satellite down over time. The lower it gets, the harder it becomes to line up relative speeds, attitude, and timing. Rescuing a satellite before it drops too far is a little like trying to catch a falling plate without also knocking over the rest of the kitchen.
NASA’s own public timeline for the Swift boost mission lays out that narrow path pretty plainly, and the agency also updated the launch schedule in early July as the mission prepared to fly. Those two references matter because they show how compressed the whole plan has been from the start: NASA’s Swift boost mission timeline and the launch-date update for the Swift boost mission. Katalyst had less than a year to pull the mission together from contract to launch, which is a tight turnaround by any standard, and especially tight for a first-of-its-kind servicing job.
That first matters too. This is the first time NASA’s hired a private company to service one of its satellites, so the mission is carrying a lot more than one observatory and one chaser. It’s a live test of whether a commercial space contract can be turned into actual hands-on orbital repair on a compressed schedule. There wasn’t much room for leisurely systems engineering or a leisurely parade of extra hardware reviews. The spacecraft had to be built, integrated, tested and launched fast.
For now, Link still has a decent amount going for it. The trouble’s centered on the reaction wheels and the cold-gas thrusters, but the rest of the stack looks usable. Power is still there. The rendezvous gear is still there. The robotics hardware that’d handle a close approach and possible capture hasn’t been ruled out by the recent failures. So this isn’t a case where the whole mission’s fallen apart. It’s messier than that, which is almost worse, because it means the team can still see the shape of the finish line.
That’s why the next stretch’s so tense. If Link can be stabilized, the mission doesn’t need perfection. It needs enough control to buy a close pass, a careful inspection and a shot at turning a half-billion-dollar satellite into something that keeps working a little longer. If it can’t, Swift keeps dropping while everyone watches the rescue window shrink by the day.
A high-stakes test for commercial space servicing
The next few days will tell NASA, Katalyst, and just about everyone else watching whether Link ends up as an unusually messy in-space rescue story or as the sort of cautionary tale engineers keep on a whiteboard for years. That’s the blunt reality here. A spacecraft launched to save another satellite has already needed its own save, and the whole episode’s now doing double duty as a technical crisis and a live demonstration of how unforgiving orbital work can be.
NASA will have a concrete example to point to when it argues for buying more of these services from private companies, if Link gets back under control and reaches Swift. That kind of outcome would make it easier to imagine future missions where a satellite’s life can be extended, nudged upward, or kept useful a bit longer by a commercial robot instead of by a brand-new launch. For NASA, that’s not just a nice story. It’s a test case for whether this market can actually handle real hardware, real deadlines and real money without falling apart the first time a wheel burns out.
A failure would tell a different story. It’d show how fast a rescue spacecraft can turn into a spacecraft in distress, especially when the vehicle is compact, the timeline is tight and there isn’t much room for a second mistake. Space rescue sounds neat in a briefing room. In orbit, one bad attitude control event, one stalled thruster, one missed communication window, and the whole plan can start slipping out of reach.
In low Earth orbit, the margin for error gets eaten up faster than the fuel.
That’s the part this mission keeps putting in plain view. Swift’s descending because drag never stops working on a low-orbit satellite, and Link’s racing The clock but also the physics. There’s no generous cushion here, no leisurely repair schedule, no long runway to sort things out. The timing has to work, and the hardware has to behave. The people on the ground have to make smart calls while the spacecraft keeps moving.
Which is why this story has a slightly brutal charm to it. Space hardware can change roles in a hurry. A chaser becomes a patient. A repair mission needs repairs. The satellite sent up to save NASA’s Swift mission now has to prove it can save itself first, and that alone tells you plenty about how much risk NASA’s willing to accept as commercial servicing moves from theory into actual, slightly sweaty practice.
