DEPLOYDatabase

Incident · Malfunction

AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost

AstroForge's second spacecraft, Odin, launched February 27, 2025 as a rideshare on Intuitive Machines' IM-2 lunar mission. The spacecraft briefly communicated via an amateur radio operator in Germany but lost contact within 24 hours due to ground station configuration issues (wrong antenna polarization, incorrect pointing coordinates).

On March 6, 2025, AstroForge officially declared Odin lost. The spacecraft cost approximately $3.5 million and was the first private deep-space mission beyond Earth orbit.

Occurred 2025-02-27 · Odin · AstroForge

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.

Machine-readable surfaces

Sources (2)

  1. Futurism · https://futurism.com/astroforge-asteroid-mining-mission-loses-contact · 2025-03-01
  2. AstroForge · https://www.astroforge.com/updates-collection/odint-mission-debrief · 2025-03-06

Common questions

What happened in AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost?
AstroForge's second spacecraft, Odin, launched February 27, 2025 as a rideshare on Intuitive Machines' IM-2 lunar mission. The spacecraft briefly communicated via an amateur radio operator in Germany but lost contact within 24 hours due to ground station configuration issues (wrong antenna polarization, incorrect pointing coordinates). On March 6, 2025, AstroForge officially declared Odin lost. The spacecraft cost approximately $3.5 million and was the first private deep-space mission beyond Earth orbit.
When did this incident occur?
The incident is recorded as occurring on February 27, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost?
Odin is the recorded robot involved in this incident.
Has anyone responded to AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-08-09

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

2
unclassified
Unclassified source

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for AstroForge's Odin deep-space spacecraft lost contact 24 hours after launch, declared lost.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.


Canonical ID 42f270e5-7fdc-4c02-8400-1c4871eb736a