To fix ship damage in Star Citizen, first check what looks damaged and which ship functions are affected; then use the in-game maintenance options if they fit your situation. For a landed ship, stay in the pilot seat, open mobiGlas with F1, and select Landing Services to access maintenance options. [1]
Start with what you can observe: for example, note visible damage and whether a particular function is affected. Keep those observations separate from assumptions about what caused a problem, so you have a clear symptom to check after maintenance.
Repair steps can change between game versions, so identify the version you are playing before relying on detailed instructions. Then use the Landing Services menu to see what maintenance options are available in that version, and choose your next step based on the affected function.
Is the problem caused by damage?
A ship fault is more likely damage-related when visible damage and the affected function line up, but a symptom alone does not prove the cause. Compare what you can see on the hull or ship components with any damage indicators available in your current game version, then note exactly what still works. For example, visible damage near a damaged-looking component is useful context if that component’s function has stopped, but avoid treating the visual clue as a confirmed diagnosis.
Separate damage from control and movement problems
If your ship’s controls do not respond, consider an input problem rather than assuming the ship is damaged. A control issue can look like a ship failure because your commands produce no response; keep that possibility separate and use the focused controls guide if the symptom points that way.
A ship that starts but will not move has a different symptom from visible damage. Don’t assume the lack of movement proves the hull or another component needs repair; use the focused engine or movement guide when that is the problem you need to isolate.
Keep repair expectations specific
Use the current in-game service options as your guide, and don’t assume landing services can fix every failed system. If the ship still fails after an available repair, keep the remaining symptom specific and move to the matching engine, movement, or controls guide—or report a repeatable unresolved issue through the appropriate process.
For example, if the ship moves but a control input still fails, focus on that input rather than applying unrelated repairs. If it starts but remains stationary, investigate the movement symptom instead of treating visible damage as the only explanation. Repair what the available service menu supports, then choose the next step based on the failure that remains.
Which repair option should you try?
Landing Services is the confirmed route to check for vehicle maintenance, but the repair choices you can use depend on what the current in-game menu offers. Once you are landed and still in the pilot seat, open mobiGlas with F1 and select Landing Services to see the service options. [1]
Choose from what the menu offers
Treat the menu as your guide: use a repair or maintenance choice only if it appears there. For example, if you see a repair option after taking damage, select it; if no repair choice appears, do not assume another service will fix the damage.
The available choices may depend on the game version, so check the current menu rather than relying on an older list. Do not count on a particular service being available at every landing spot, and check the menu before making plans around a repair.
Match the option to your situation
Keep the choice focused on the damage you are trying to address. If you see a relevant repair option, try it and then check whether the affected ship function works again. If the menu offers only a different kind of maintenance, do not treat that as proof it will repair the damaged part.
A ship that still fails after service may have a separate engine or control problem, rather than damage the menu can address. If the same damage-related problem remains, note the specific symptom and use the relevant troubleshooting guide or report the repeatable issue.
Before you choose, read the current service menu and confirm that it offers an option that matches your situation. That keeps your next step tied to what the game actually makes available, instead of guessing about repair services.
Repair the ship, then check it again
Land at a location with Landing Services available, and stay in the pilot seat. [1] For example, if a damaged wing is the concern, keep that damage in mind so you can check the same area after service.
Open mobiGlas with F1 and select Landing Services. [1] Use the service menu to see which maintenance or repair choices are available for your ship; don’t assume that opening the menu has repaired anything.
Choose an available maintenance or repair option that matches the damage you want addressed. The menu’s available choices are the practical guide here, so select a relevant option rather than guessing at a service that is not listed.
After the service, check the affected ship parts and retest the symptom you noticed. If a damaged wing was the concern, inspect it again and check whether the original issue changes; if the ship still will not respond as expected, the cause may be a separate engine or control fault, so use the guide for that symptom next.
If the ship remains unusable after an appropriate service, avoid treating every failure as damage-related. Keep track of the specific part and function that still fail, then try the matching symptom guide or report the issue if it keeps happening.
What if the ship still seems damaged?
If your ship still seems damaged, first confirm that a repair was actually offered and completed; opening the service menu alone does not confirm that work was done. [1] Check the result against the same symptom you noticed before, such as a damaged-looking part or a ship function that still fails.
If the problem persists, check the current service menu for another repair option, and try it only if it is available in your game version. Don’t assume that every symptom has a matching service or that a different option will fix it. Keep your notes focused on what you can observe: for example, “the repair completed, but the left engine still does not respond” is more useful than “the ship is broken.”
Follow the symptom that remains
If the remaining issue points to an engine, controls, or movement, use the troubleshooting guide for that specific symptom. For example, if the ship responds to controls but does not move, follow the movement guide; if the controls themselves fail to respond, use the controls guide. This keeps you from treating every ongoing problem as unresolved damage.
If the same damage-related failure keeps happening after you have checked the available repair options, prepare a concise bug report instead of repeatedly trying unrelated fixes. Record what you observed, what repair you selected, whether it completed, and what still fails. A clear, repeatable symptom gives you a more useful next step than another round of guesses.
When should you escalate the problem?
Escalate when a repair you can access does not restore the affected function or your ship remains unusable. Focus on the failure that is still happening rather than repeating repairs that do not address it.
If you can still use the ship but one clear function fails, move to a symptom-specific guide. For example, if the remaining problem is engine response or ship controls, follow the guide for that symptom instead of treating every failure as unresolved damage.
If the ship remains unusable after the available repair, stop and note what happened. Record the symptom before and after repair, which function failed, and whether the problem happens again under the same conditions. Keep the report focused on what you observed; do not assume damage caused the problem just because it appeared after an impact.
For an issue you can reproduce that still appears unresolved after repair, report it through the appropriate gameplay bug process. A clear account of the repeatable failure is more useful than guessing at a hidden cause. If the failure points to engines or controls, use the matching symptom guide; if it persists despite the relevant repair, document and report the issue.
Choose the next step based on the remaining symptom
Use the repair option available through Landing Services, then retest the ship function that was failing. If it still does not work, focus your next step on that specific symptom rather than repeating unrelated fixes.
After repair, try the same action that exposed the problem: if the ship would not start, test starting it; if a damaged function stopped responding, check that function again. Note whether the result changed, stayed the same, or became intermittent. That gives you a clear basis for choosing what to investigate next.
If the failure remains, use the symptom that best matches what you see. A ship that starts but will not move points you toward a movement-focused guide; an engine-start or response problem belongs in an engine guide. If controls do not respond, follow the controls guide instead. Keep the description narrow—for example, “the ship starts, but the damaged thruster still does not respond”—so you do not confuse a damage symptom with a separate fault.
If the same failure happens again after you have tried an available repair, report it as a repeatable issue through the appropriate process. Describe what the ship did before and after repair, and stick to what you observed rather than guessing at the cause. Your next move is simple: retest first, then choose the symptom guide or report the issue if the ship still fails.