Here's how engineers plan to save the satellite sent to save NASA's Swift mission 16%

By Stephen Clark25%

8/1/2026, 11:20:11 AM

BS Summary: This article contains 17 faulty reasoning types, including Overconfidence Bias, Unattributed Quote, and Biased Writer Voice, with Optimism Bias as the most egregious example at 22.6% saturation with 241 hits. Analysis detected 713 faulty-reasoning hits from 1,067 analyzed words, generating a BS Score of 24.8% and a BS Rank of 16% (25,049 of 29,795 articles). This article is better (less manipulative) than 84.10% of the article peer group.

One week ago, more than 200 miles above the Earth, a refrigerator-size satellite making its way toward an attempted rescue of NASA’s $500 million Swift gamma-ray observatory suddenly spun out of control. 
It didn’t look good. 
The spacecraft, named Link, was rotating on multiple axes, rendering it unable to maintain a reliable communications link with the ground and complicating efforts to arrest the spin. 
Two of the satellite’s three reaction wheels, used for pointing, also stopped working. 
Through sporadic radio contact, engineers discovered a problem with some of the spacecraft’s cold gas thrusters used for finer attitude control. 
The Link satellite is built, owned, and operated by Katalyst Space Technologies, a satellite servicing startup that won a $30 million contract from NASA to fly up to the Swift observatory, grab onto it, and boost its orbit before succumbing to aerodynamic drag and burning up int he atmosphere. 
The clock is ticking. 
In a few months, Swift will be too low for Katalyst to complete the rescue. 
This is the first time NASA has contracted with a commercial company to service one of its satellites. 
The space agency gave Katalyst less than a year to put the mission together. 
The Link satellite launched July 3 to begin the pursuit of Swift, and the mission proceeded mostly according to plan until last Saturday. 
“When this happened, it was during one of the passes without comms,” said Ghonhee Lee, CEO of Katalyst, said in an interview with Ars. 
“We were, immediately prior, in a very stable configuration.” 
Katalyst’s ground team, working from a control center near Denver, hurried to find a fix and recover the Link satellite. 
The good news was the spacecraft’s other systems remained healthy, including its power supply, three xenon-fueled electric thrusters, and the rendezvous and robotics hardware the Link satellite needs to capture Swift. 
Keeping at it 
Ars spoke with Lee, Katalyst’s chief executive, on Friday afternoon as the company’s ground team worked to stabilize the spacecraft. 
The first step involves using the satellite’s plasma engines to gradually slow the spin. 
The engines are primarily designed for orbit-raising, but they’re also suitable for attitude control because they can vector their thrust with a two-axis gimbal. 
Link’s electric propulsion system is efficient but low in thrust, meaning it takes time to generate enough of an impulse to regain full control of the satellite’s pointing. 
“We’ve been able to use the thrusters to point in the opposite direction of the rotation rate and affect the attitude control that way, which has been highly effective,” Lee said. 
This has worked well so far. 
As of Friday, the spacecraft had cut its spin rate in half, from about 9 degrees per second to approximately 4 degrees per second. 
Officials hope to further reduce the spin rate, allowing Katalyst to improve communications with the spacecraft. 
“Once we are in a more stable configuration, with much more high-bandwidth comms, we’ll be able to use that to downlink all the rich data (about the condition of the spacecraft),” Lee said. 
“We do know the states of the reaction wheels and the thrusters and things like that. 
So our GNC team—guidance, navigation, and control team—has been very hard at work with NASA, essentially remapping all of the control algorithms to be able to have an updated controller ready to go for when we are able to stabilize the spacecraft.” 
A plume of plasma exhaust coming from one of the Link satellite’s xenon-fueled electric engines. 
Katalyst may eventually be able to recover the satellite’s two inoperable reaction wheels, but the team’s priority is restoring control by uplinking a new algorithm to manage its orientation through a combination of its one remaining reaction wheel and thrusters. 
Engineers aren’t sure yet what caused the emergency with the Link spacecraft last weekend. 
It could have been an internal problem with the satellite or a collision with space junk. 
Lee said two cameras on the satellite will look for signs of damage after ground teams stabilize it. 
Whatever the cause, Katalyst’s mission control team lost contact with Link for more than 24 hours after it spun out of control. 
The satellite then automatically reset itself, just as it was supposed to do. 
“This was built-in fault protection logic saying, “Hey, if I haven’t heard from anybody in 24 hours, there must be something wrong. 
I’m going to toggle the power, turn it on and off again,'” Lee said. 
“It’s just built in. 
However, that shutdown mode is ungraceful. 
It basically pulls the plug on everything, and that creates some downstream effects for sensitive systems such as the reaction wheels. 
“Basically, there was a big thermal spike that came about as a result of this that over-temperatured the upstream electronic circuits that control the reaction wheels, which ultimately led them to being inoperable,” Lee said. 
The problem with the spacecraft’s cold gas thrusters seems to be a “separate issue,” Lee said. 
But engineers don’t have all the data in hand to make a final determination. 
“These things all happened at once, so it’s hard to delineate between what contributed to creating the situation and what was the consequence of the situation, and that’s something we’ll have to investigate with all the data,” Lee said. 
Nevertheless, Lee said Katalyst still aims to move Link toward NASA’s Swift observatory, perhaps around the end of August. 
“We’re very committed to pursuing this mission,” Lee said. 
“We’re working side by side with NASA. 
I just came from a technical working meeting with their controls team, where we’re reviewing the algorithms. 
It seems like there’s nothing that is preventing us from reestablishing three-axis control of the spacecraft with the remaining reaction wheel, with the remaining thrusters, as well as the electric propulsion. 
“It’s not the original mode that we expected to control the spacecraft with, but it seems like we will have sufficient stability and controllability of the spacecraft,” Lee said. 
“With this, we believe we’ll be able to do the rendezvous with Swift. 
We believe that we’ll be able to go and do things like the inspection of Swift within a close approach of a few dozen meters. 
And as it stands right now, we have not made a formal assessment, but we believe that a capture of Swift, an attempted capture of Swift, is very much in the cards.” 
Article reasoning-pattern comparisonThis article: 0.8%Stephen Clark: 1.1%Ars Technica: 2.4%Confirmation Bias0.8%This article: 0.0%Stephen Clark: 0.8%Ars Technica: 0.9%Anchoring Bias0.0%This article: 1.5%Stephen Clark: 1.0%Ars Technica: 2.1%Availability Heuristic1.5%This article: 0.0%Stephen Clark: 0.7%Ars Technica: 0.9%Representativeness Heuristic0.0%This article: 0.0%Stephen Clark: 0.7%Ars Technica: 0.5%Hindsight Bias0.0%This article: 11.3%Stephen Clark: 1.9%Ars Technica: 2.0%Overconfidence Bias11.3%This article: 0.0%Stephen Clark: 2.4%Ars Technica: 2.9%Framing Effect0.0%This article: 0.4%Stephen Clark: 0.1%Ars Technica: 0.4%Loss Aversion0.4%This article: 0.0%Stephen Clark: 0.3%Ars Technica: 0.4%Status Quo Bias0.0%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.1%Sunk Cost Effect0.0%This article: 22.6%Stephen Clark: 7.3%Ars Technica: 3.7%Optimism Bias22.6%This article: 1.4%Stephen Clark: 0.8%Ars Technica: 1.6%Pessimism Bias1.4%This article: 0.9%Stephen Clark: 2.6%Ars Technica: 5.8%Negativity Bias0.9%This article: 3.7%Stephen Clark: 0.9%Ars Technica: 1.2%Self-Serving Bias3.7%This article: 0.0%Stephen Clark: 0.7%Ars Technica: 0.6%Fundamental Attribution Error0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%Actor-Observer Bias0.0%This article: 0.0%Stephen Clark: 0.9%Ars Technica: 0.5%In-Group Bias0.0%This article: 0.0%Stephen Clark: 0.4%Ars Technica: 0.1%Out-Group Homogeneity Bias0.0%This article: 0.0%Stephen Clark: 2.0%Ars Technica: 1.7%Halo Effect0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%Horn Effect0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.0%Dunning-Kruger Effect0.0%This article: 0.6%Stephen Clark: 0.7%Ars Technica: 0.9%Recency Bias0.6%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.2%Primacy Effect0.0%This article: 3.7%Stephen Clark: 0.1%Ars Technica: 0.1%Blind-Spot Bias3.7%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.4%Ad Hominem0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.2%Straw Man0.0%This article: 1.6%Stephen Clark: 2.4%Ars Technica: 3.5%Appeal to Authority1.6%This article: 1.5%Stephen Clark: 0.8%Ars Technica: 1.0%False Dilemma1.5%This article: 0.0%Stephen Clark: 0.7%Ars Technica: 0.7%Slippery Slope0.0%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.1%Circular Reasoning0.0%This article: 0.0%Stephen Clark: 1.9%Ars Technica: 3.2%Hasty Generalization0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.2%Red Herring0.0%This article: 0.0%Stephen Clark: 0.4%Ars Technica: 0.5%Bandwagon0.0%This article: 0.0%Stephen Clark: 1.5%Ars Technica: 2.3%Appeal to Emotion0.0%This article: 0.0%Stephen Clark: 0.2%Ars Technica: 0.5%Begging the Question0.0%This article: 3.3%Stephen Clark: 1.8%Ars Technica: 1.9%Post Hoc (False Cause)3.3%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%Tu Quoque0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.4%Burden of Proof0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.2%Appeal to Nature0.0%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.2%Composition/Division0.0%This article: 3.0%Stephen Clark: 0.4%Ars Technica: 1.4%Anecdotal3.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%No True Scotsman0.0%This article: 0.0%Stephen Clark: 0.8%Ars Technica: 1.4%Ambiguity (Equivocation)0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.1%Middle Ground0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%Personal Incredulity0.0%This article: 0.0%Stephen Clark: 0.1%Ars Technica: 0.1%Special Pleading0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.1%Genetic Fallacy0.0%This article: 4.3%Stephen Clark: 1.4%Ars Technica: 1.4%Unattributed Quote4.3%This article: 2.2%Stephen Clark: 0.2%Ars Technica: 0.8%Quote-first Misdirection2.2%This article: 3.9%Stephen Clark: 2.2%Ars Technica: 3.8%Biased Writer Voice3.9%This article: 0.0%Stephen Clark: 0.4%Ars Technica: 0.8%Indoctrination0.0%This article: 0.0%Stephen Clark: 0.0%Ars Technica: 0.5%Politically Left Leaning Bias0.0%This article: 0.0%Stephen Clark: 0.4%Ars Technica: 0.1%Politically Right Leaning Bias0.0%This article: 0.0%Stephen Clark: 0.9%Ars Technica: 1.1%Attempt to Sell a Product or S…0.0%

1067 words analyzed.

Speakers

1speaker48%attributed speech560writer words
Selected voice

Ghonhee Lee

81%flagged-word coverage
507 attributed words100% of attributed speech28% writer coverage
0%5.0%10.0%Unattributed Quote+9.1 ptsWriter: 0.0%Ghonhee Lee: 9.1%9.1%Biased Writer Voice-7.5 ptsWriter: 7.5%Ghonhee Lee: 0.0%0.0%Quote-first Misdirection+4.7 ptsWriter: 0.0%Ghonhee Lee: 4.7%4.7%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.