For Star Citizen patrol fuel and supplies, plan for the full trip rather than only the outward leg. Estimate fuel for your route, including the return and likely detours, then identify places to refuel, repair, or resupply before departure. You may also find this useful: Long Range Patrol in Star Citizen: How It Works.
A patrol far from convenient services can become harder to manage if the route changes or a stop is unavailable. Treat carried supplies as a buffer for delays, not as a replacement for route planning; ships can receive hydrogen fuel for maneuvering and quantum fuel for quantum drives from fuel tankers or stations. [1]
Before launch, sketch the patrol as a sequence of legs: for example, outbound travel, time on station, a possible diversion, and the trip home. For each leg, ask what you will need and where you could get support if the plan changes. Keep the questions practical: does the route still work if you add a stop, and do you have a useful fallback if your preferred service is out of reach?
The aim is not to predict every encounter. It is to leave with a workable route and enough flexibility to respond to delays without turning a minor change into a scramble for support.
Estimate fuel for the whole patrol
Estimate a patrol’s fuel by separating the ship’s two fuel needs, then checking whether your full plan leaves room for changes. Hydrogen fuel supports maneuvering, while quantum fuel is used by the quantum drive for quantum travel. [1] Treat them as separate budgets: a route that looks manageable for quantum travel can still involve extra maneuvering, and vice versa.
Build the estimate around the whole trip
For each fuel type, think through the outbound leg and the return rather than judging the patrol by the first jump alone. Then account for likely route changes, such as detouring around an obstacle or changing your approach to an objective. Those choices can add quantum travel or maneuvering beyond the cleanest planned route, so consider what each change would use.
For example, if you expect to travel out, maneuver near the patrol area, and then return, consider those as distinct parts of the estimate. If the objective might move, leave room for a revised approach instead of assuming you will follow the shortest path exactly. You do not need a perfect prediction; you need a plan that does not depend on every leg going as expected.
Check your ship’s readout
Use the ship’s current fuel readout as your starting point, since your estimate needs to reflect the ship’s actual fuel state. When possible, test a comparable route in the same ship and use the result as a practical reference. A similar trip can help you judge how much fuel your planned travel and maneuvering may take, but keep the patrol’s extra route changes in mind.
Do not plan to reach the end of the patrol with almost no fuel left. Keep a reserve for an unplanned maneuver or route change, and shorten the patrol if your estimate leaves too little room. As you adjust the plan, check both fuel types again: extra quantum travel and extra maneuvering draw on different fuel needs.
Check where you can refuel or repair
Map each planned stop to a known fuel service or support point, then check whether it fits your ship and patrol objective. A station can look convenient on a route, but the useful question is whether you can reach it and use it without pulling the patrol off course.
Mark useful stops on the route
Put service points directly on your route map rather than relying on memory. Refueling can provide hydrogen fuel or quantum fuel, and fuel may come from a tanker or a station. [1] For example, label the station you expect to use and note which leg of the patrol it supports; keep repair or other support locations marked separately if you know them.
A marked point is only a candidate, not an automatic stop. Compare its position with your patrol area, the ship you are flying, and the task you need to complete. If reaching a station would take you far away from the objective, a closer support point—or a shorter patrol—may be more practical.
Keep an alternate in view
Choose a backup service point before departure, especially if your route depends on one convenient station. If the nearest option is unavailable or awkward to reach, your map should already show another place to check or a sensible point to turn back. Avoid building a plan that works only if one stop is usable.
Treat map notes as planning aids, not confirmation that a service is available right now. Check the relevant in-game location before you leave and again if the route changes. If your preferred stop is not usable, adjust the patrol around the alternate rather than pressing on as if support were guaranteed.
For example, mark a primary station near the patrol route and a second candidate outside the immediate area. If the first does not work, decide whether the alternate still fits the objective; if not, shorten or postpone the patrol.
Set aside room for repairs and delays
Damage and delays can turn a comfortable patrol into a return problem, so leave room in your plan for both. A ship that takes a hit may need to divert for repairs, while reaching that service point can consume time and fuel you had expected to use elsewhere. Think through the return leg under those less favorable conditions, not just the route you expect to fly.
Plan for a damaged ship
Before departure, consider what you would do if your ship were damaged far from support. For example, if a patrol objective leaves you with a longer trip back than planned, ask whether the remaining fuel and time still give you a safe way to reach help. If not, shorten the patrol’s reach or set a clear point where you turn back while the return remains practical.
Do not make one service stop your only recovery plan. If that stop is unavailable, inconvenient, or too far away after damage, you need another workable choice—or a reason to end the patrol before the situation gets worse. Keep the response simple enough for the whole crew to follow under pressure.
Reassess when the plan changes
A route change or new objective can change how much time and fuel you need to get back after a repair diversion. Recheck the patrol plan when the mission shifts; for instance, if an encounter sends you well off your intended route, reassess whether continuing still leaves room for repairs and a return.
Treat repair time as part of the patrol’s usable schedule, not as an afterthought. If a repair stop would leave too little time or fuel for the return, reduce the patrol’s reach rather than counting on a perfect run. That small adjustment gives you a more practical decision point when damage or delays disrupt the plan.
Pack supplies that match the patrol
Match your carried supplies to the crew, expected patrol length, and assigned tasks; pack for the work you plan to do, not every situation you can imagine. A solo patrol focused on observation may need a different personal kit from a crew expecting to board or inspect a site. Use the patrol’s actual tasks to decide what earns space aboard.
Build a role-based checklist
Start with each crew member’s job, then list the gear needed to do it. For example, someone assigned to leave the ship for an inspection should check personal gear for that task, while a pilot can focus on equipment needed at the helm. If the patrol includes several distinct jobs, group the checklist by role so you can spot gaps before launch.
Next, check the ship’s relevant equipment and each person’s gear before departure. Make the check specific: compare the equipment you have with the tasks you assigned, rather than relying on a vague “ready” call. If a planned task has no matching gear, either pack what it needs or adjust the task.
Keep frequently needed essentials easy to reach, and leave out items that have no clear purpose on this patrol. A compact, task-based loadout is easier to check than a pile of gear gathered “just in case.” If you cannot name when an item would be used, consider leaving it behind.
Verify what you can buy
Treat shop listings as a place to look for items such as FPS gear, ship components, and equipment, then confirm that a wanted item is actually available in your current game version before planning around it.[2] Inventory can affect your checklist: if the exact item you want is unavailable, choose another workable option or revise the task that depended on it. Check the current in-game shop before you count on a purchase.
Keep the final checklist short enough to use: crew roles, task-specific gear, essential items, and any planned purchases to verify. That gives everyone a clear last check without adding supplies that do not support the patrol.
Use a final departure check
Trace the route one last time. Follow the planned legs in order, then check that the return path still makes sense if the patrol takes longer than expected. Mark one alternate stop so the crew has a clear option if the intended route or service point becomes impractical. For example, agree which nearby station or other known stop you would use rather than improvising while already low on fuel.
Compare the plan with the ship’s current state. Read the fuel levels at departure and check whether each planned leg fits the ship as it is now, not as it was on a previous run. Hydrogen fuel is used for maneuvering, while quantum fuel is used for quantum drives, so check both against the kind of travel you expect. [1] If the ship has changed or you have revised the route, take another look before launch instead of relying on an old estimate.
Confirm the support options and a fallback. Check which refuel and repair choices are practical for this patrol, then identify what the crew will do if the preferred stop cannot be used. Refueling can be provided by a fuel tanker or station. [1] Keep the choice concrete: name the planned stop, the alternative, and the point at which you would turn toward either one.
Set a crew decision point. Agree in advance where you will shorten the patrol or end it if reserves fall below the level your crew considers workable. For example, decide that after a particular leg, the pilot calls the patrol early rather than continuing toward another objective. Make sure everyone knows who will call the change and what route the crew will take next.
Before departure, have one crew member read back the route, fallback, and decision point while another checks the ship. That quick handoff helps catch a mismatch before the patrol is underway.
Leave with a margin, not a guess
A dependable patrol plan connects route fuel, service access, repairs, and the supplies your crew needs; before launch, check your ship’s current readout and whether services are available in-game. [1] Refueling can provide hydrogen fuel or quantum fuel, so match your checks to the fuel your ship needs for the next leg. [1]
Treat the departure check as a decision point, not a box to tick. If the ship’s readout or available services don’t fit the plan, shorten the patrol, choose another stop, or delay departure. For example, if a planned service point is unavailable, don’t assume you can top up there—adjust the route before committing.
Keep the decision simple for the whole crew: know what would make you change course, and speak up when conditions no longer match the plan. That gives you a practical next step if a repair takes longer than expected or the patrol shifts away from its original route. Leave with a margin you can explain, rather than relying on a guess.