Why is my ship not moving in Star Citizen? Start by checking whether the ship is powered and whether you can interact with its controls, then identify what kind of movement is missing. A ship that will not accelerate presents a different symptom from one that accelerates but will not turn.
That distinction helps you avoid treating every movement problem as an engine failure. Watch what happens when you try to move forward and when you try to steer: those observations can point toward a movement limit, an engine issue, or a control issue without proving a cause on their own. Keep the game version and current conditions in mind, since the symptom may depend on both.
Describe what the ship is doing
First, ask whether the ship appears powered and whether you can interact with its controls. For example, note whether control inputs produce any response, rather than labeling every lack of movement as “the ship is dead.”
Then separate no thrust or acceleration from no steering or change of direction. If you can steer but cannot accelerate, that is a different observable pattern from a ship that accelerates but will not change direction.
Treat the symptom as a clue, not a diagnosis
These observations help distinguish a movement limit from an engine or control failure, but they do not establish one cause by themselves. Describe the result plainly—for example, “the ship responds to steering but does not accelerate”—instead of guessing what is broken.
Game conditions and version matter when you investigate a symptom. A movement behavior you remember from an earlier version may not tell you what is happening now, so use the version you are playing as context for what you observe.
Could a current mode or condition be limiting movement?
A movement limit is more likely when your ship’s controls respond but its surroundings or current mode appear to block travel; check the situation before treating the symptom as an engine or control failure. Look for a nearby obstruction, a mode that changes how the ship can move, or another visible condition that could explain why thrust or steering has no effect. Don’t assume that a familiar restriction or workaround still applies in the current game version.
Compare the ship’s response
Test a brief thrust input, then a steering input, and watch the ship’s display after each. If neither input changes anything, note that; if the display changes but the ship stays put, note exactly what changed, such as a mode indicator or warning. These observations help you tell an apparent movement limit from a missing thrust response or an input that is not registering.
For example, if steering changes the display while the ship remains stationary, record that behavior and check the ship’s current state and nearby surroundings. If the display shows no change after either input, don’t label it a movement restriction based on appearance alone; continue with the engine or controls checks that fit what you observed.
Check the current version
Verify movement behavior against current official game information for the version you are playing. A past workaround may no longer apply, and an old known-issues entry may describe a symptom that is different from yours.
The available Alpha 4.10.1 known-issues entry describes a delay in the services app being ready for use, but it does not identify a ship-movement symptom. [1] If a current official known-issues entry does describe your symptom, treat it as a possible game issue and note the version it names; don’t assume that an unrelated entry explains your ship’s behavior.
If your observations point to missing thrust or unresponsive steering, continue with the matching engine or controls checks. If neither fits and the same movement limitation is reproducible, record the conditions and report the specific symptom.
Is the problem with thrust, steering, or both?
If you can steer but get no thrust, focus on engine response; if thrust works but steering does not, focus on control response. When neither works, first confirm that the ship is in a state where movement should be possible, then use what you observe to choose the next troubleshooting path.
Thrust works, steering fails
Try a small thrust input and then a directional input separately. If the ship accelerates but does not turn or change direction when you command it, that points toward a control-response problem rather than a lack of engine thrust.
For example, if the ship moves forward but ignores your attempt to yaw or strafe, keep the diagnosis focused on steering input. Continue with the ship-controls troubleshooting guide for detailed binding and device checks; don’t start changing engine settings just because the ship feels stuck in one direction.
Controls respond, but there is no thrust
If your inputs register but the ship does not accelerate or produce thrust, investigate engine response instead of assuming you have hit a movement limit. A control response by itself does not show that the engines are supplying thrust.
For instance, you may be able to turn the ship while forward thrust produces no movement. That observation narrows the next step to the ship-engine troubleshooting guide; leave engine activation procedures to that guide.
Neither thrust nor steering works
If neither input produces the expected response, don’t assign the problem to the engines or controls yet. First check whether the ship is actually in a condition where movement should be possible, then repeat the separate thrust and steering tests.
If movement still fails and you can reproduce the same symptom, document the conditions and use the bug-report guide. If one test does respond, follow the engine or control guide that matches the missing response.
Try these movement checks in order
Write down the version, ship, location, and current state. Before changing anything, note the game version shown in the launcher or game, the ship you are flying, where it is, and what state it appears to be in. For example, record whether you are in a hangar, on a landing pad, or already clear of nearby structures. These details make it easier to compare your symptom with version-specific information and to repeat the same check later.
Test thrust and directional input separately. Give a brief thrust input and watch for a response, then test a directional input such as pitch or yaw. Keep the tests separate so you can tell whether thrust is missing, steering is missing, or neither produces a response. Note what you see, such as a movement change or no visible response; avoid jumping to an engine or control diagnosis based on one combined input.
Check for a relevant movement condition or known issue for your version. Compare your ship’s current situation with the movement conditions that seem relevant, then check the current known-issues information for the version you recorded. Known-issue entries are version-specific; for example, the Alpha 4.10.1 page lists an issue about a delay in the services app becoming ready, but that alone does not show that it causes a ship-movement symptom. [1] Don’t assume an older entry applies to your current version or explains your case.
Choose the next guide or document a repeatable symptom. If thrust is the response that is missing, continue with the engine guide; if directional input is missing, continue with the controls guide. If neither pattern fits, or the same no-movement behavior keeps happening after your checks, write down the conditions and keep the symptom reproducible. A concise record of the version, ship, location, state, and separate test results will help you describe what happened when you report it.
When should you report the problem?
Consider reporting the problem when your ship repeatedly fails to move in a situation where you expect it to, and the symptom remains after your basic checks. A single odd moment is harder to describe clearly; a repeatable pattern gives you something specific to document and follow up on.
Before you write anything, try to reproduce the same movement symptom and note what happens each time. For example, record whether the ship stays completely still or whether one kind of movement works while another does not. Keep this focused on what you can observe, rather than guessing at a cause.
What to include in your notes
Write down the game version, ship, and location where the issue occurs. Add the ship’s state at the time and whether thrust or steering responds. Those details make it easier to explain exactly what “not moving” means in your case.
For example, your note might say that a particular ship at a named location repeatedly fails to move in the same observed state, and that thrust responds while steering does not. Keep the description tied to the movement behavior you reproduced; avoid adding unrelated symptoms or speculative explanations.
If the symptom does not recur after your checks, you can keep your notes and watch for it to happen again before reporting. If it does recur under the same conditions, move on to the dedicated bug-report guide for the full reporting process. If your checks instead point to missing thrust or unresponsive steering, use the engine or control guide that matches that symptom.
Choose the next step based on what you found
If you’ve isolated the symptom, use it to choose the right focused guide—or document a repeatable problem that neither guide explains. This keeps your next step tied to what the ship actually does, rather than sending you through unrelated repairs.
No thrust or acceleration
If the ship responds to your inputs but produces no thrust or acceleration, continue with the ship-engine troubleshooting guide. For example, if steering input changes the ship’s direction but applying thrust does not move it, focus on the engine path instead of changing control bindings.
No steering or input response
If thrust works but steering or directional inputs do not produce a response, continue with the ship-controls troubleshooting guide. For instance, if the ship accelerates but will not turn when you try to steer, investigate control response rather than engine output.
Neither guide explains it
If the symptom keeps happening and neither path fits, document the conditions in which movement fails and report the issue. Be specific: note what you were doing, what input you tried, and whether thrust, steering, or both failed to respond. A clear account of the repeated behavior gives others a concrete symptom to assess without guessing at a cause.
Your next step is simple: follow the engine guide for missing thrust, the controls guide for missing steering or input response, and report a repeatable symptom if neither explains it. Keep your notes focused on what the ship did and the conditions around the failure.