- 3,446
- 3,675
... Continued from part fifteen.
To the Mun!
Part sixteen: Home, sweet home
[Figure 234: Service module separation (1/2)]
[Figure 235: Service module separation (2/2)]
[Figure 236: Reentry (1/2)]
[Figure 237: Reentry (2/2)]
[Figure 238]
[Figure 239]
[Figure 240]
[Figure 241]
[Figure 242]
[Figure 243]
[Figure 244]
Lessons learned:
To the Mun!
Part sixteen: Home, sweet home
[Figure 234: Service module separation (1/2)]
[Figure 235: Service module separation (2/2)]
[Figure 236: Reentry (1/2)]
[Figure 237: Reentry (2/2)]
[Figure 238]
[Figure 239]
[Figure 240]
[Figure 241]
[Figure 242]
[Figure 243]
[Figure 244]
Lessons learned:
- Carrying both an Mk2 Command pod and and Mk2 Lander-can might be a bit much. Unlike the lander module in the actual Apollo missions, the Mk2 Lander-can in KSP is pretty darned heavy. In future missions/designs, I might get more bang for the buck by using the Mk2 Command pod for lander module too, and scratch carrying around the extra lander-can weight. The fuel for the return trip can still be left in orbit, but instead controlled by an unmanned, remote guidance pod. (And that allows all three Kerbals to reach the surface!) Or alternately, I might consider keeping the Mk2 Lander-can and scratching the Mk2 Command pod.
- Consider having detachable science payloads that can be discarded and left behind for the return trip, to lighten the load further. Be sure to attach ladders and grabby things to make them easily accessible though, since the Kerbals will need to get close during EVA to collect the data.
- The more advanced method of rendezvous works very well: perhaps too well. Keep an eye on the ships' relative velocity and distance, and be prepared to burn retrograde when the target ship approaches!
Last edited: