Workaround
Aurora Mk I cannot be retrieved after Alpha 4.9
Tracked since 18 Aug 2026 · Last researched 18 Aug 2026
Problem
Your pledged Aurora Mk I may fail to summon from an ASOP terminal after the Alpha 4.9 update, leaving you without the ship you normally use to enter the game.
This is an Aurora Mk I retrieval or storage failure, not a general hangar outage, a ship damaged after spawning, or every ship-retrieval error. The exact stuck state and hotfix remain unresolved.
Applies to Alpha 4.9.x LIVE · Current
Fallback only
Try another location and a stock-layout claim
Try another location and a stock-layout claim once if you can accept the loss warning. Aurora-specific recovery remains unconfirmed.
Use this once rather than cycling the same terminal; it is the one bounded retrieval route worth trying before you stop local retries.
What to do
- Reach another station or landing zone by another available ride.
- At its ASOP terminal, try the Aurora Mk I there; if the terminal offers a claim or stock-layout recovery, review the loss warning before confirming.
- Test the Aurora before repeating local retrieval attempts.
A stock-layout claim may remove aftermarket equipment or cargo.
Other options
Reverse a recent component change before a stock claim
Consider this only after a clearly recent component change. It has no Aurora-specific success, so keep it to one bounded attempt.
What to try
- Reverse only a clearly recent component or weapon change through the normal loadout path.
- Attempt a stock-layout claim at another location only if you can accept the claim warning.
- Stop if the Aurora remains unavailable or valuable equipment is at risk.
No Aurora recovery is established for this component-reversal sequence.
What not to try
Do not keep cycling the same local retrieval path
An alternate hangar attempt did not restore the Aurora, so repeating the same local retrieval cycle is not worth more time.
Data sources
RSI Known Issues · RSI Support · RSI Patch Notes · Reddit