The Strategic Imperative of a Space Taxi in KSP

Kerbal Space Program challenges players to master orbital mechanics, resource management, and engineering creativity. While individual missions to Mun or Minmus are straightforward, interplanetary travel to Duna, Eve, Dres, Jool, and beyond strains even veteran space agencies. Launching a separate, purpose-built vessel for every planetary expedition wastes funds, inflates part counts, and risks mission failure from design errors. A dedicated space taxi service—a reusable fleet of transfer vehicles—transforms how you explore the Kerbol system. Instead of building a new ship for each destination, you construct a modular backbone that shuttles Kerbals and cargo between planets, dramatically reducing cost per mission and opening the door to sustained colonization.

This guide provides a production-ready framework for designing, deploying, and operating a multi-planet space taxi fleet in Kerbal Space Program. We cover vehicle architecture, fuel logistics, transfer window planning, automation, and advanced mod integration. By the end, you will have a blueprint for a service that makes multiple-planet missions routine rather than heroic.

Why a Fleet Beats Single-Purpose Ships

Single-use vessels are the default approach for new players: build a rocket, fly to a planet, land or orbit, and return. But this method scales poorly. Each new destination requires a new design, new testing, new launches. Fuel costs skyrocket, and the time between missions grows because you must rebuild. A space taxi fleet addresses these inefficiencies:

  • Reusability cuts launch costs: A single taxi can fly dozens of missions. The upfront investment pays back after a few round trips.
  • Standardized docking interfaces: All taxis use the same docking port sizes (typically Clamp-O-Tron Sr. or Jr.), allowing any crew module or cargo container to hitch a ride.
  • On-orbit refueling: Taxis can rendezvous with orbital depots or mineable bodies (Minmus, Ike, Pol) to top off propellant without returning to Kerbin.
  • Operational tempo: While one taxi is en route, another can be refueling, and a third can be in the VAB getting upgrades. You can run multiple transfers per Kerbin year.

Beyond efficiency, a taxi service teaches real-world space logistics concepts. NASA and other space agencies rely on crew and cargo transfer vehicles (Dragon, Starliner, Cygnus) to service the ISS—the same principle applies, scaled to interplanetary distances. For more on the real-world parallels, consult NASA's ISS vehicle overview.

Fleet Architecture: The Three-Tier Model

A successful interplanetary taxi service uses three distinct vehicle classes, each optimized for its segment of the journey. Trying to build a single ship that does everything—atmospheric liftoff, interplanetary transfer, and planetary landing—usually results in a design that is mediocre at all three. Separate the roles.

Tier 1: Kerbin Surface-to-Orbit Shuttle

This vehicle hauls crew and cargo from the KSC launch pad to Low Kerbin Orbit (LKO). It must be cost-effective, easy to fly, and capable of delivering payloads to a docking station or directly to the waiting taxi. A simple two-stage rocket with reusable boosters (like the Kerbodyne KR-2L engine) works well. Alternatively, use a spaceplane with Rapier engines to recover the whole craft. The shuttle does not need to leave LKO—it returns to Kerbin after transfer.

  • Capacity: 6–12 Kerbals per flight, plus modular cargo containers (2.5m diameter).
  • Docking port: Clamp-O-Tron Sr. on top for crew transfer.
  • Recovery: Equip parachutes and landing legs if not using a spaceplane.
  • Optional: Add a small claw for pushing debris, or use it as a rescue vehicle.

Tier 2: Interplanetary Transfer Taxi (The Workhorse)

This is the core of your fleet. The taxi stays in space permanently—it never lands on a planetary surface. It transfers between Kerbin orbit and the orbit of a target planet. Design it around a high-specific-impulse engine, like the LV-N "Nerv" nuclear engine, for efficiency on long burns. The taxi must have ample delta-v (at least 4,000–5,000 m/s) to perform a Hohmann transfer and capture at the destination, plus margin for plane changes and rendezvous.

  • Propellant: Liquid fuel only (Nerv engines don't use oxidizer). Consider a detachable drop tank for departure burns.
  • Crew module: A Mk1-3 Command Pod or Hitchhiker Storage Container for passenger comfort (or just a cupola for piloting).
  • Docking: One standard port at the front for crew/cargo transfer; one at the rear for refueling.
  • Refueling capability: Include docking ports and optionally a small drilling/ISRU unit if you plan to mine fuel from planet surfaces.

For maximum efficiency, equip the taxi with solar panels and radiators (nuclear engines generate heat). Research the LV-N Nerv Atomic Rocket Motor through the Nuclear Propulsion tech node.

Tier 3: Planet-to-Skylander Landers

When the taxi arrives at a target planet, it cannot land itself (unless you built a massive lander—usually inefficient). You need a dedicated lander that detaches from the taxi, descends to the surface, and returns to orbit. Each planet may require a different lander design due to varying gravity and atmosphere. Build a small fleet of specialized landers that dock with the taxi upon rendezvous.

  • Duna lander: Use parachutes and small engines (e.g., Terrier). Thin atmosphere requires chutes but still provides some drag.
  • Eve lander: Massive atmosphere demands huge heat shields, strict aerodynamic control, and high TWR. Eve ascent is extremely challenging—consider a one-way crew delivery.
  • Moho lander: No atmosphere, high gravity, and proximity to the sun require heavy heat shielding and powerful engines. Use a stageable descent/ascent design.
  • Jool moon landers (Laythe, Vall, etc.): Adapt for each moon's gravity and atmosphere. Laythe has an oxygen atmosphere that allows jet engines for short hops.

Standardize lander docking ports to match the taxi (Sr. or Jr.). Carry one or two landers on the taxi for a multi-stop itinerary.

Fuel Logistics and Interplanetary Depots

No taxi service works without a reliable fuel supply chain. Rather than launching massive tankers from Kerbin every time, exploit the game's resources.

Mining and ISRU

The most sustainable approach is to mine ore from low-gravity bodies and convert it into liquid fuel and oxidizer. Minmus is the ideal location: flat terrain, low gravity (easy landings, small dV to reach LKO), and high ore concentration. Place a mining base on Minmus that produces fuel and oxidizer, then launch tankers (autonomous drones) to ferry propellant to a LKO depot.

  • Minmus fuel depot: Orbiting at ~30 km altitude, equipped with large tanks and multiple docking ports.
  • Tanker drones: Small, uncrewed ships using Nerv or Poodle engines. They land on Minmus, fill up from the base, and deliver fuel to the depot.
  • Transfer: Taxis fuel up at the depot before each mission. This cuts Kerbin launch costs by 70% or more.

Orbital Refueling Points

Set up automated fuel depots in LKO, around the Mun, and at key interplanetary gateways (e.g., Duna orbit, Eve orbit). These depots act as gas stations. Taxis dock, refuel, and continue. You can also use a depot as a staging point for assembling large interplanetary spacecraft, but with a well-designed taxi, assembly is rarely needed.

Transfer Window Planning and Scheduling

Flying your taxi at the wrong time dramatically increases delta-v requirements. Use the game's built-in maneuver node tools with an external calculator or the Alex Moon Launch Window Planner to find optimal transfer windows. A typical Duna window occurs every 2.12 Kerbin years; for Eve, every 1.6 years. Miss the window and your taxi wastes fuel or cannot complete the trip.

Automated Transfer Execution

Manually executing multi-impulse transfers is tedious. Consider using MechJeb or Kerbal Alarm Clock mods to automate burn timing and execution. With MechJeb's "Lambert Transfer" module, the taxi can automatically plan and execute a Hohmann transfer to any target, including mid-course corrections. This frees you to manage the broader fleet.

  • MechJeb routines: Set up a standard maneuver profile: circularize in LKO, program the ejection burn, perform a mid-course plane change if needed, and capture at the target.
  • Multiple taxi missions: Use Kerbal Alarm Clock to create a mission timeline. For example, Taxi Alpha departs for Duna at Year 2 Day 100; Taxi Bravo departs for Eve at Year 3 Day 50.

Operational Procedures: Standardized Mission Profiles

To make the taxi service reliable, follow a consistent mission flow. Here’s a typical Duna round trip:

  1. Departure from Kerbin: Taxi sits in LKO (150 km) docked to the fuel depot. Crew and cargo arrive via shuttle. Taxi undocks, performs ejection burn to Duna transfer orbit.
  2. Mid-course correction: About halfway, adjust trajectory for encounter with Duna (target periapsis ~60 km for aerocapture).
  3. Duna orbital insertion: Use aerocapture if taxi has heat shields; otherwise, burn retrograde. Taxi circularizes into a 100 km orbit.
  4. Lander deployment: Duna lander undocks, descends to the surface, completes mission, returns to orbit with crew/data.
  5. Duna orbit rendezvous: Lander docks with taxi. Crew transfers to taxi. (Optionally, taxi can land on Duna if designed, but that increases fuel mass.)
  6. Return transfer: After filling from any local depot (e.g., Ike mines), taxi burns for Kerbin. If no local fuel, depart with remaining dV.
  7. Kerbin capture: Aerobrake or burn into LKO. Taxi docks with depot and refuels for its next mission.

Repeat this pattern for each destination, adjusting lander design and capture techniques (e.g., Eve requires heat shields rated for 60 km/s entry; Moho demands heavy reliance on engines).

Handling Emergencies and Redundancy

Even with careful planning, things go wrong: Kraken attacks, missed burns, fuel shortage. Plan for failure.

  • Rescue taxi: Keep one spare interplanetary taxi at the LKO depot, fully fueled. It can perform emergency rescue missions to stranded Kerbals.
  • Escape pods: Include a small return capsule on each lander that can reach Kerbin directly in a pinch (use a miniaturized pod with enough dV for direct return).
  • Multi-fleet coordination: If Taxi Alpha breaks down, Taxi Bravo can intercept it and transfer crew. Use RCS to push derelict vessels to a graveyard orbit.
  • Mod support: The Kerbal Construction Time mod adds realistic build times—plan for spare vehicles to be under construction.

Advanced Mods to Enhance Your Taxi Service

Vanilla KSP supports everything described above, but several mods simplify and enrich the experience:

  • Kerbal Alarm Clock: Manage multiple missions and transfer windows.
  • MechJeb 2: Automate docking, rendezvous, and interplanetary transfers.
  • TAC Life Support / USI Life Support: Adds resource consumption (food, water, oxygen). Your taxis must carry supplies and perhaps grow food on long journeys.
  • Kerbal Inventory System (KIS) & Kerbal Attachment System (KAS): Enable on-orbit repairs and refueling by EVA Kerbals.
  • RasterPropMonitor: Adds realistic cockpit instruments for those who like manual flying.
  • Realism Overhaul (for hardcore players): Throttles difficulty but gives real-world orbital mechanics.

For a curated list, see the KSP Mod Releases forum.

Case Study: A Round-Trip Eve Surface Mission

Eve is the ultimate test: crushing atmosphere, extreme heat, high gravity, and rare transfer windows. Here’s how a taxi service handles it:

  1. Build a specialized Eve lander: Extremely aerodynamic, with a high drag coefficient. Use a large heat shield (10m inflatable). The lander should have >12,000 m/s dV to return to orbit—this requires staged ascent with multiple engines (Vector or Dart).
  2. Transport via taxi: Carry the Eve lander (separate module) attached to the taxi. The taxi uses its own engines to push the assembly to Eve.
  3. Aerocapture at Eve: Taxi with heat shields enters at 70 km altitude, bleeding speed. After capture, taxi circularizes at 200 km.
  4. Lander descent: Detach lander, which dives through the atmosphere using chutes and engine braking. Crew lands safely.
  5. Ascent: After surface operations, the lander ascends in stages—first stage drops after boosting to 20 km, second stage to orbit. Docking with taxi.
  6. Return: Taxi burns for Kerbin. Eve’s deep gravity well means the taxi must have ample dV or refuel from a Gilly mining base.

This mission demonstrates why a single taxi cannot do everything—the Eve lander is a unique vehicle, but the taxi is the reusable backbone.

Performance Metrics: Measuring Your Fleet's Efficiency

To evaluate your space taxi service, track a few key numbers:

  • Cost per Kerbal-kilometer: Calculate total funds spent on launches, refueling, and maintenance divided by total distance traveled by all crew.
  • Turnaround time: How many days between a taxi's return and its next departure? Keep it under 30 days by having spare taxis ready.
  • Propellant efficiency: Liters of fuel consumed per mission. Aim for >80% of fuel to come from ISRU rather than Kerbin launches.
  • Part failures: If you use mods like DangIt!, track repair needs.

Optimize by retiring underperforming designs and upgrading to newer engines (like the Nerv or Wolfhound for better Isp).

Conclusion: From Single Missions to a Living Space Infrastructure

A well-run space taxi service transforms Kerbal Space Program from a series of disconnected launches into a cohesive interplanetary infrastructure. You stop asking "How do I get to Duna?" and start asking "Which taxi is available next week?" The fleet model teaches resource management, logistics planning, and system-level thinking—skills that apply beyond the game. Start small: one taxi serving Minmus, then expand to a second serving Duna. Once you master refueling depots and automated transfers, you can run simultaneous missions to four or five planets. The Kerbal Space Program becomes a bustling spacefaring civilization, and you are its traffic controller.

For further reading on orbital mechanics and space logistics, explore Orbiter Forum's Hohmann transfer guide and the KSP Wiki orbital mechanics tutorial.