TL;DR: On November 3, 2026, Starfish Space and NASA said the company's first full-scale Otter spacecraft can't be recovered. Otter 24C launched on October 1 for NASA's SSPICY inspection mission, made early contact, then went silent during commissioning. The cause, according to Starfish, was an error in the fault protection software on the satellite bus supplied by Astro Digital, which kept the radio switched off. Starfish says its other Otter missions are still planned. For space companies, the story is a lesson in how to talk about a setback: fast, specific and focused on what happens next.

Key takeaways

• A single onboard software error ended a NASA-funded demonstration mission, even after a good launch and early contact.
• Starfish named the cause, the supplier involved and the fix in its public update instead of staying vague.
• NASA's own statement framed the loss as part of how technology demonstrations work, which helps the company's credibility.
• Starfish still lists several upcoming Otter missions, so the business story is about recovery, not collapse.
• Customers for high-value servicing jobs will want proof that the fix is tested before the next flight.

What happened to Starfish Space's Otter spacecraft?

Here is the news in short. According to NASA's small satellite blog, the Small Spacecraft Propulsion and Inspection Capability (SSPICY) mission launched on October 1. Starfish established initial communications with its Otter spacecraft, then lost contact during commissioning, the early phase when a spacecraft turns on its systems and gets ready for normal operations.

The key facts as reported:

• The cause. NASA and Starfish traced the problem to the spacecraft's fault protection system, the onboard software that detects and responds to problems. It kept the radio turned off by mistake.
• The supplier. GeekWire reports that Starfish said the error was in fault protection on the satellite bus provided by Astro Digital.
• The mission. SSPICY was a $15 million NASA mission, GeekWire says, meant to inspect inoperable U.S. objects in low Earth orbit and test propulsion, navigation and a robotic boom.
• The milestone it was meant to hit. NASA notes this was the first launch of Starfish's Otter and the first time the company's navigation and propulsion technologies flew together in one spacecraft.
• The fix. Starfish says it is working with Astro Digital to fix the fault protection system and update testing for future Otters.

SpaceNews also reported the failure on November 3, describing it as the company's first Otter servicing spacecraft.

What is still on Starfish Space's schedule?

This is the part with the most business lessons. GeekWire lists several Otter missions still planned: a satellite disposal job for the Space Development Agency, two commercial servicing missions in geostationary orbit and two servicing missions for the U.S. Space Force. Starfish also says it is still testing its smaller Otter Pup prototype, which recently made a close approach to a target satellite, and is preparing a docking attempt.

Starfish also said it and NASA are exploring ways to meet the SSPICY objectives on other Starfish missions. In plain terms, the company lost a spacecraft but is working to keep the customer relationship and the mission goals.

Who wins and who loses after the Otter loss?

These points are our reading of the situation, not facts from the reports.

Likely winners

• Teams that invest in software testing. A fault protection error is now a headline. Buyers will ask harder questions about software verification, and suppliers who can show their process will stand out.
• Rival servicing companies. Competitors may get a closer look from customers who want options. Any edge will be short-lived if they can't show their own flight record.
• Customers who negotiate carefully. Buyers of servicing missions now have a fresh reason to ask for test evidence and milestone terms in contracts.

Likely losers or under pressure

• Starfish's near-term schedule. The company hasn't announced a date for its next full-scale Otter. Every upcoming mission now carries extra attention.
• Bus suppliers. Astro Digital is named in the cause. Bus providers across the industry may face tougher questions about fault protection from their own customers.
• Startups pitching untested systems. Investors and agencies may push harder for flight heritage before they commit.

A fair warning: failures are common in new space hardware, and early loss doesn't predict the future of a company. How a team responds matters more than the loss itself.

What should space entrepreneurs do now?

You don't need to build a servicing spacecraft to use these lessons. Here are five practical moves.

1. Write your setback plan before you need it

Starfish's update named the cause, the supplier, the fix and the next missions. That kind of clear statement is much easier to publish when you've planned it in advance. Decide now who approves the message, who tells customers first and where you post it. Our space startup PR guide covers how to set up those basics.

2. Tell customers and investors before the press does

Partners hate learning bad news from a headline. Brief your key customers, agency contacts and investors directly, then publish. Use the same structure you'd use in a regular investor update: what happened, what it means and what you are doing next.

3. Show what you learned, not just what broke

NASA's statement framed the mission as a technology demonstration where teams test, learn and iterate. If you sell to agencies, use the same language they use. Our guide on how to sell to NASA explains why that fit matters.

4. Keep your proof pipeline full

Starfish can point to its Otter Pup tests and a list of upcoming missions. That keeps the story moving forward. Build a steady stream of proof points, such as ground tests, partial wins and customer quotes, so one bad week doesn't define you. Our post on case studies for space companies shows how to package them.

5. Ask your suppliers the hard questions now

The cause sat in a supplier's software. Ask your own vendors how they test fault protection and failure modes, and what happens if their part causes a loss. Put that in writing before launch, not after. Startups narrowing their focus, like the team in our Rendezvous Robotics funding post, face the same supplier choices.

How does this change positioning for in-space servicing companies?

Buyers of servicing missions are trusting you with assets that can be worth a lot of money. After a public loss, every servicing company will hear the same question: why should we trust your spacecraft?

Three questions are worth answering this quarter:

• What is your test and verification story? Explain it in plain words, not just a list of standards.
• What proof do you have from orbit? Even small demos count if you explain what they proved.
• What happens if a mission fails? Customers want to know how you'll make it right.

For a full framework, start with our space marketing guide. If you sell to the military too, our guide on how to sell to Space Force covers what those buyers look for.

Frequently asked questions

What happened to Starfish Space's Otter spacecraft?

Otter 24C launched on October 1, 2026, for NASA's SSPICY mission and made early contact, but lost communications during commissioning. NASA and Starfish said on November 3 that it can't be recovered.

Why did the Otter spacecraft fail?

NASA and Starfish traced the problem to the spacecraft's fault protection software, which kept the radio turned off by mistake. Starfish said the error was in fault protection on the satellite bus provided by Astro Digital.

What was the SSPICY mission?

SSPICY was a NASA-supported technology demonstration led by Starfish Space. It was designed to inspect inoperable U.S. objects in low Earth orbit and test propulsion, navigation and a robotic boom. GeekWire reports it was a $15 million mission.

Does Starfish Space still have other Otter missions planned?

Yes. GeekWire reports planned missions for the Space Development Agency, two commercial servicing missions in geostationary orbit and two for the U.S. Space Force. Starfish is also still testing its Otter Pup prototype.

What can space startups learn from the Starfish Otter failure?

Plan your setback message in advance, brief customers and investors first, show what you learned, keep a steady flow of proof points and press your suppliers on how they test for failures.

Want to work through this with other space founders?

Join Space Entrepreneurs, free. Space Entrepreneurs is the free Skool community I host for founders who are starting, marketing and growing space companies. Bring your questions, share what you are working on and learn from people building in the same industry.

Join Space Entrepreneurs free