A young company that hoped to prove its servicing craft could work close to other satellites in orbit has lost contact with its first Otter vehicle, and with it a NASA-funded demonstration called SSPICY. The reports point to a fault in the spacecraft's bus software, the quiet core that handles power and communication, which switched off the radio and left the ground unable to reach it. How much of the planned work was finished before the silence is not yet known, but the episode arrives at a moment when many are still deciding whether small machines that repair and inspect other spacecraft can
Starfish Space Loses Contact With First Otter Servicing Spacecraft, Ending NASA Tech-Demo Mission
A bus software fault switched off the spacecraft's radio.
Mark
So what actually happened to Otter?
Mimi
Starfish Space lost contact with its first Otter servicing spacecraft. That ended the NASA-funded SSPICY demonstration.
Mark
And the reason?
Mimi
Reports point to a bus software fault that switched off the spacecraft's radio. Once the radio is off, there's no way to talk to it.
Luke
I'd keep one distinction in view. One of the headlines says only 'a software glitch,' and another gives the radio detail. The specific mechanism is attributed in reports, not laid out in a detailed company explanation we can see here.
Mark
Why does a bus fault matter so much?
Mimi
The bus runs the basics, including communications. If it fails, the whole vehicle can go quiet, however good the mission hardware is.
Luke
What we don't know is how much of the inspection mission got done before contact was lost. Nothing in the material says, and it doesn't say whether recovery was attempted either.
Mark
So what does this mean for satellite servicing generally?
Mimi
It's a setback for a young industry, and attention turns to the next Otter vehicles and NASA's follow-up.
Luke
Fair, but that's a forward look, not a finding. Whether this one failure changes confidence is something only later flights will answer.
O Pulso
- Contact with Starfish Space's first Otter spacecraft was severed, abruptly ending the NASA-funded SSPICY demonstration in orbit.
- A fault in the bus software reportedly switched off the radio, leaving operators with no way to send commands or receive data.
- The failure struck a software layer rather than the close-approach maneuvers the mission was built to prove, unsettling a fledgling industry.
- Sources available so far do not detail any recovery attempts, leaving the vehicle's fate unresolved.
- Attention now turns to the next Otter vehicles and NASA's response, where confidence in commercial satellite servicing will be tested.
A young company that hoped to prove its servicing craft could work close to other satellites in orbit has lost contact with its first Otter vehicle, and with it a NASA-funded demonstration called SSPICY. The reports point to a fault in the spacecraft's bus software, the quiet core that handles power and communication, which switched off the radio and left the ground unable to reach it. How much of the planned work was finished before the silence is not yet known, but the episode arrives at a moment when many are still deciding whether small machines that repair and inspect other spacecraft can be trusted.
Starfish Space has lost contact with Otter, the first satellite-servicing spacecraft it ever put into orbit. With that silence, the NASA-funded SSPICY demonstration has come to an end. The news spread across several outlets, including Space.com, NASA, GeekWire, Universe Space Tech and MLQ.ai, all reporting the same outcome from slightly different angles.
SSPICY was meant to show that a small servicing vehicle could drift up to another spacecraft and inspect it closely. For Starfish, Otter was the first real test of that idea in space, so its loss carries more weight than a single failed flight.
The reports point to a software fault. One version describes a glitch that interrupted the demonstration; a more specific account says a fault in the bus software switched off the radio. The bus handles a spacecraft's power, commands and communications, so when it falters the whole vehicle can go quiet. Without a radio, the ground cannot command the craft or hear from it, and the mission cannot go on.
What remains unclear is how much of the planned work was completed before contact was lost, and whether any recovery was attempted. The coverage does not say. For a young industry that must prove its machines are reliable, the attention now falls on Starfish's next Otter vehicles and NASA's follow-up, where confidence in this approach will be tested.
Starfish Space has lost contact with Otter, its first satellite-servicing spacecraft, and with that loss the NASA-funded demonstration mission it was flying has come to an end. The news surfaced through a cluster of headlines from Space.com, NASA, GeekWire, Universe Space Tech and MLQ.ai, all describing the same outcome from slightly different angles.
The mission was called SSPICY, and NASA funded it as a technology demonstration. Its purpose, as the coverage frames it, was satellite inspection: using a small servicing vehicle in orbit to examine another spacecraft up close. Otter was the first vehicle Starfish Space had put into orbit in this role, which made it the company's first real test of its servicing concept in space.
The cause, according to the reports, was a software problem. One account describes a software glitch that interrupted the demonstration. Another is more specific: a fault in the spacecraft's bus software switched off its radio. The bus is the part of a spacecraft that handles core functions such as power, command handling and communications, so a fault there can silence the entire vehicle. Without a working radio, operators on the ground cannot send commands or receive data, and the mission cannot continue.
The headlines state plainly that the loss ended the mission. They do not say how much of the planned demonstration was completed before contact was lost, and the material available does not describe what recovery attempts were made. Those details are not in the source, so they remain open.
The episode lands in a young field. Commercial satellite servicing and inspection is a business that depends on showing that small, maneuverable spacecraft can reliably do close-up work in orbit. A first-vehicle failure traced to software, rather than to the harder proximity operations the mission was designed to prove, will inevitably shape how people read the company's progress.
What to watch next is how Starfish Space and NASA respond. The coverage points toward the company's next Otter vehicles and any follow-up from NASA as the places where confidence in this approach will be tested, and toward whatever the investigation into the bus software fault eventually reveals.
Citações Notáveis
A bus software fault switched off the spacecraft's radio, ending the mission.— MLQ.ai report, as summarized
Quer a matéria completa?
Leia o original em Google News ↗
Technology