jaws909's Mission Reports

[jaws909]

Greetings! This is thread is a record of my attempts to take a space program from very humble beginnings, and go where no Kerbal has gone before, space! I'll be trying to keep it somewhat realistic, ex. no reverts (except for cases of catastrophic comp failure of course), no autopilots, etc. I will be using several part/aesthetic mods; NovaPunch, Procedural Fairings, Chatterer to name a few. All that aside, let's get started!

Early Spaceflight:

Skyshot I - Success First satellite

Skyshot II - Success

A-S 01(U) - Success Unmanned flight test of Atlas spacecraft

Atlas 1 - Success First manned flight

Atlas 2 - Success First manned orbit and EVA

Stepping stones to the Mun:

RLV1/TB-A - Partial failure Test of Rhea Launch Vehicle

OIV-1 - Success First orbital intercept (unmanned)

Munar 1 Failed Munar impact probe, contact lost during transit

RLV2/TB-B Success Successful test of Rhea Launch Vehicle

Rhea 1 Success Maiden flight of the 2-man Rhea orbiter

Munar 2 Success First Munar orbit (unmanned)

Rhea 2 Success First dual-EVA

Rhea 3/Artemis I Success First orbital docking

Munar 3 Success Unmanned Mun lander

Titan II Success Launch vehicle test

Munar 4 Failed Automated Munar rover, damaged during landing

Zues, the Mun and Beyond Zeus, the spacecraft intended to carry men to the Mun and Minmus, takes flight

Moving Forward After the Zeus program's success, the KSC team's focus splits between interplanetary probes and orbital space stations

Mission: Skyshot I

Type: Satellite

Objective: Place a satellite into orbit

Outcome: Success!

Status: Derelict in low-Kerbin orbit

Notes: The team at the KSC celebrated their first triumph today with the launch of Skyshot I. While not particularly large, or useful, it was a feat nonetheless never before achieved. The small craft, hurled aloft by a converted two stage ballistic missile with extra boosters welded to the base, settled into a roughly circular orbit at ~90km, where it transmitted back a simple radio message, "Hello from space!" in Korse Kode to anyone with an antenna for roughly 1.5 hours, at which time the on-board batteries were depleted and the craft became little more then a floating piece of debris. Scientists are currently working on how to make sure future satellites and/or spacecraft have ample battery life for extended missions...

Mission Photos:

On the launchpad

Liftoff!

Secondary boosters exhausted, main engine carries on to edge of atmosphere

First stage separation

Ejecting fairings at the edge of space

Successfully reaching orbit

Edited September 14, 2013 by jaws909

[jaws909]

Mission: Skyshot II

Type: Satellite

Objective: Place the Skyshot II satellite into orbit to test improved batteries and solar panel recharge systems

Outcome: Success!

Status: Active in low-Kerbin orbit

Notes: The team at the KSC were eager to build upon their success with Skyshot I, this time with a slightly larger, more complex satellite dubbed Skyshot II. Their goal was to test a new rechargeable battery pack and accompanying solar panel systems that would, in theory at least, allow the craft to recharge and remain operational indefinitely. The science team was also allowed to bolt various instruments to the hull in order to measure temperature, g-forces and the strength of Kerbin's gravity from orbit. The rocket to be used, now commonly being referred to as the SLV (Skyshot Launch Vehicle) was upgraded slightly to lift the increased weight by adding expanded external boosters with greater fuel capacity, to counter Skyshot I's problem of early burnout of the auxiliary rocket engines. This vehicle was dubbed the SLV-1A, making it the first built and designated specifically for spaceflight (the earlier Skyshot I launcher had been a re-purposed ballistic missile).

The launch was carried out in the morning, to allow for the craft to travel to orbit and complete initial testing of the solar panels before passing into the shadow of the planet. The team was surprised at the efficiency of the launcher, which carried the craft all the way to their target altitude of 100km using the primary launch stage. Once the craft was clear of the atmosphere, the first stage and protective fairings were jettisoned, allowing the solar panels to receive sunlight. After a few tense moments, ground control confirmed that the panels were in fact reading a positive charge.

The better than expected performance of the first stage also left ample fuel in the second stage to perform the final orbit insertion burn, and it was discarded with a substantial amount of fuel remaining. Final corrections were then made using the Skyshot II's on-board LV-1 engine, which again had more fuel remaining then expected. After some debate, it was decided to attempt another maneuver with the engine, to test its ability to restart in space, and measure its ability to push the craft into a higher orbit. After the second burn, the craft settled into a 500kmx102km orbit. Meanwhile, the on-board instrumentation provided scientists on the ground with a wealth of information about environment that the 1st pioneering astronauts would encounter on future manned missions...

Mission Photos:

Liftoff!

Making the turn east to climb towards orbit

Fairings released, solar panels reading positive charge

Jettisoning second stage

LV-1 carries the craft into its target orbit

Passing over the KSC after the first full orbit

LV-1 fires for a second time to push the satellite higher

Highest altitude achieved, 500km

Edited September 3, 2013 by jaws909

[jaws909]

Mission: A-S 01(U)

Type: Suborbital unmanned test

Objective: Launch Atlas capsule to 100km on suborbital trajectory, test retro-booster pack, test reentry systems

Outcome: Success!

Status: Recovered

Notes: With two successful satellite launches under their belts, the KSC team was eager to move forward with the next phase in their space exploration plans, a manned flight. However, for safety reasons and to avoid a costly law suit, not to mention insurance payments and the oh so dreaded governmental review boards that would follow any accidental loss of life, it was agreed that an unmanned test of their newly designed Atlas capsule would precede an actual manned flight. Although there was some frustration from the eager pilots who were waiting in line for their chance at spaceflight, particularly the daring Jeb, who remarked "I'm a test pilot aren't I?! Let me test it!", an unmanned, suborbital test flight under the designation A-S (Atlas-Skyshot) 01(U) was conducted.

The launch proceeded smoothly, as was to be expected from the proven SLV-1A, which carried the Atlas capsule to it's target altitude of 100km without any problems. At the edge of space, the first stage was jettisoned as planned, and the shortened second stage pushed the orbital time out to allow the craft to hang in space long enough to test the on-board systems before reentry. After release of the second stage engine, the Atlas under remote guidance coasted to its orbital apogee at 100km, where the retro-pack boosters (intended for de-orbiting the craft during a full orbital mission) were fired successfully until exhausted, and then jettisoned.

The Atlas capsule then reentered the atmosphere, with the heat-shield functioning as planned, and automatically deployed its drogue parachute at 5000m to slow its descent prior to full parachute deployment at 500m before coming down for a safe splashdown some 560km east of the KSC, where it was later recovered helicopter. The mission was a complete success, demonstrating the full functionality of the Atlas spacecraft and assuring the KSC team, and more importantly, the government, that it was safe to green-light a manned launch...

Mission Photos:

On the launchpad

Liftoff!

The turn east

First stage jettisoned

Second stage jettisoned

The retro-pack boosters fire

Expended retro-pack is jettisoned prior to reentry

The atmosphere's warm embrace

Parachute deployed

Edited September 3, 2013 by jaws909

[jaws909]

Mission: Atlas 1

Type: Suborbital manned flight

Crew: Jebediah Kerman

Objective: Launch manned flight to 100km and return safely

Outcome: Success!

Status: Recovered

Notes: The KSC team celebrated another historic milestone today with their first manned spaceflight. The pilot, Jeb, was rocketed off the launchpad in his Atlas 1 capsule, and carried aloft on the tried and true SLV-1A to a height of 100km along a north-easterly path that would out over the ocean. There he took the time to snap a quick photo, the first from a spacecraft beyond the atmosphere, before firing his retro-boosters to ensure a safe reentry. A slight miscalculation was made on his entry trajectory, and he ended up landing in a sparsely populated coastal area, instead of the intended offshore water-landing. He and the spacecraft emerged unscathed however, and the press was quick to be on scene to snap pictures and question the intrepid explorer about his journey to the stars...

Plans are now underway for a full orbital flight with Atlas 2...

Mission Photos:

Liftoff!

A quick photo from space looking out the Atlas' tiny window

The hero's return

Edited September 3, 2013 by jaws909

[jaws909]

Mission: Atlas 2

Type: Manned orbital flight

Crew: Bill Kerman

Objective: Complete full orbit of Kerbin, conduct stand-up EVA if conditions permit

Outcome: Success!

Status: Recovered

Notes: More exciting news from the KSC today, where it was just announced that the Atlas 2 mission has returned from a successful mission with its pilot, Bill Kerman. In a flight lasing just 1H, 15M, the Atlas 2 orbited the planet twice. After a careful check of the ship's systems, mission control also cleared Bill to perform the first ever EVA, or extra-vehicular activity, outside of his spacecraft. Although his "spacewalk" was brief, lasting only a few minutes, and he did little but take in the view and look over the exterior of his ship from where he held onto an exterior rail, Bill has nonetheless gone down in the history books as both the first man to orbit the planet, and the first to leave his spacecraft while doing so.

Although it was hoped the flight would be longer, due to the spacecraft's limited power reserves, Bill was forced to cut his time in space short and fire his retro-boosters to bring him down to a landing at the designated "secondary landing site", the ocean west of the KSC, rather than risk landing at the primary site with dead batteries and no way to open his parachutes. This, combined with the limited maneuvering capability of the Atlas craft, has led the KSC team to announce that it will be retired, and all future Atlas missions cancelled to make way for the new "Rhea" spacecraft now in testing. The Rhea will feature improved safety features, extended orbital flight time and maneuvering, as well as a 2-man crew capacity over the Atlas' solo-seating space.

The KSC team also announced that they are currently working on plans and designs for an unmanned mission to the Mun, to be dubbed "Munar 1", with an anticipated launch date close to their first intended manned Rhea flight.

Mission Photos:

Bill snapped this photo of sunset just before passing over the night-side of Kerbin

An on-board camera captures Bill as he hangs onto the side of Atlas 2 during the first ever EVA

View from the recovery aircraft of Atlas 2 awaiting pickup in the ocean after landing

Edited September 3, 2013 by jaws909

[SuperWeegee4000]

You probably want to use a site like http://postimage.org to host images - they're coming out small here.

[jaws909]

Mission: RLV1/TB-A (Rhea Launch Vehicle 1/Test-Block A)

Type: Launch vehicle test and unmanned orbital test vehicle

Objective: Launch test of RLV1, place TB-A into LKO for study of long-term effects on spacecraft

Outcome: Partial Failure

Status: De-orbited after 24 days

Notes: Before they could proceed with orbital testing of the new Rhea spacecraft, a suitable launch vehicle needed to be properly tested first. The newly designed lifter, dubbed the RLV1 (Rhea Launch Vehicle) would first be put through its paces by lifting the TB-A (Test Block-Alpha) to orbit for a study on the long-term effects of solar radiation, zero-g and other factors on a spacecraft in orbit as part of the process in finalizing the Rhea spacecraft, as well as the planned Mun missions. The spacecraft was designed to have roughly the same weight of the Rhea, in order to fully test the RLV1's lifting capacity. It would also be used as a target for a future mission, the OIV-1, a remote-controlled craft that would intercept it in orbit in order to conduct a visual survey of the craft.

The initial launch proceeded smoothly, with the rocket ascending in a stable flight to 6km before the first stage was exhausted and jettisoned. This however, was earlier than expected, however mission control still hoped the second stage would carry the spacecraft the rest of the way to orbit as it began the turn eastwards to make the climb to 100km. However, that hope soon faded as the second stage ran dry at just 60km. Luckily, the TB-A craft had been equipped with an on-board engine, intended for pushing the craft into a higher orbit once stabilized, and it was now pressed into service in order to perform the orbital insertion burn and place it into the target 100km orbit, depleting its fuel reserves in the process.

Despite the shortcomings of the RLV1, TB-A was placed into a high enough orbit to allow its systems to be adequately evaluated and conduct maneuvering tests using its RCS thrusters. While it was obvious that the RLV1 needed modifications, there was also a debate about whether to scrap the TB-A mission entirely and launch another before sending up OIV-1. This led to that mission being temporarily suspended while the decision over the fate of TB-A was discussed.

Mission update: TB-A would later be deoribted after OIV-1 was launched and successfully performed its intercept and visual inspection mission

Mission Photos:

RLV1/TB-A on the launchpad

Liftoff

Second stage carries on towards space before burning out at 60km

TB-A, now without its protective fairings, leaves the expended upper stage of the RLV1 behind

TB-A with solar panels deployed, prepares to fire its main engine to stabilize its orbit

Fuel exhausted, TB-A settles into its final, near 100km orbit

Edited September 4, 2013 by jaws909

[jaws909]

Mission: OIV-1

Type: Unmanned orbital intercept

Objective: Intercept TB-A and perform visual inspection of spacecraft's condition

Outcome: Success!

Status: Active in LKO

Notes: After the partial failure of the TB-A's launch, which left that craft stranded without primary fuel in a 100km orbit, there was debate on whether to proceed with the planned second phase of the mission, an unmanned intercept. However, it was ultimately decided that with the RLV (Rhea Launch Vehicle) undergoing modifications, and the Munar 1 launch delayed due to software glitch, the time was right to make an orbital intercept attempt. A SLV-1 would be used to launch the OIV (Orbital Intercept Vehicle) into orbit. The launcher had originally been designated for the Atlas 3 mission, but after that program was cancelled, two were left fully assembled at the KSC (the Atlas 4 launcher was slated for use on the Munar 1 mission).

The original workhorse of the KSC performed admirably, launching the OIV-1 into an orbit at roughly 140km. Once there, mission control instructed the craft to perform basic systems checks while they waited for their target to come in range. Once they were confident that all systems were operation normally, the OIV-1 performed a series of small corrective burns using the second stage from the SLV-1, before decoupling it to proceed under its own power to the final rendezvous.

The intercept occurred flawlessly, with the OIV-1 closing to within 1km of the TB-A just as both craft passed back into the sun. Once they had brought the craft into a matching orbit, mission control used its on-board camera to make a visual inspection of TB-A, which revealed that, aside from its lack of fuel, it was undamaged and operating normally, even after nearly 24 days in orbit. The mission achieved several firsts, being the first to send live pictures from space, the first to intercept another object in space, and the first to intentionally change its orbital inclination (since TB-A had ended up on a slightly inclined orbit during its ascent). After completing the inspection, the OIV-1 was moved to a 225km orbit and placed in standby mode, with mission control planning to make use of it in future missions. TB-A was de-orbited using its RCS thruster system, and burned up in the atmosphere over the ocean.

Mission Photos:

The trusted SLV-1 stands by to launch carrying the OIV-1

OIV-1 with the upper stage of the SLV-1 preparing to intercept its target

The discarded upper stage of the SLV-1 after separation as seen by the OIV-1's on-board camera

The first image captured by the OIV-1's camera of the TB-A

OIV-1's camera view during its close-up inspection of the TB-A

The tiny OIV-1 hovers near TB-A's now useless main engine

[jaws909]

Mission: Munar 1

Type: Impact Probe

Objective: Impact Mun

Outcome: Failed

Status: Battery failure during transfer, presumed destroyed

Notes: Munar 1 was intended to be the first probe to the Mun. Its mission was simple, launch on a trajectory that would carry it from Kerbin into a collision with the Mun, and return various science data to mission control until impact. It was launched on the last of the SLV-1s from the cancelled Atlas program into a low-Kerbin orbit, which was modified to include a more powerful second stage engine and a small third stage for fine-tuning the probe's course after leaving LKO. The initial launch and trans-Munar injection proceeded relatively smoothly, although there was a small error in the plotted course that was later corrected using the third stage engine.

The probe returned data on temperature, g-force, gravitational fields and attempted to detect any traces of a Munar atmosphere while enroute. However, all contact was lost shortly after it passed into the Mun's SOI. The last telemetry indicated it was still nearly 3 million km above the surface and traveling at just under 500 m/s. Mission control's best guess is that the batteries failed in-flight, either due to unexpected load from the various instruments on-board, or solar radiation or micro-meteor impact. While the probe's projected course would carry it into the surface within hours of when it ceased transmission, there was no way for mission control to confirm whether it completed its journey, as ground based telescopes were unable to track the probe as it was lost to them against the backdrop of the Mun. If it did in fact hit its mark, it would have been the first man-made object to impact another world...

Mission Photos:

Munar 1 atop its modified SLV-1 rocket awaits an evening launch

Munar 1 lifts off and starts its journey towards the Mun

As Munar 1 climbs towards orbit, Minmus, the Mun's smaller sibling, appears in the sky

Performing the burn to escape LKO and head out to meet the Mun

Following a corrective burn, the third stage is jettisoned and the probe continues along its path alone (presumably to an impact)

[jaws909]

Mission: RLV2/TB-B

Type: Launch test

Objective: Test launch capability of new RLV2 rocket by launching TB-B into stable 100km orbit

Outcome: Success!

Status: Active in LKO

Notes: Following the RLV1 launch which revealed shortcomings in the design of the new Rhea spacecraft's intended launch vehicle, a redesign of both the first and second stages of the launcher was carried out. This resulted in an expansion of the lower stage's fuel capacity, while at the same time downgrading the engine to a 4-nozzel variant over the more powerful, but much more wasteful, engine of the previous version. The upper stage's fuel was unchanged, but it too received a smaller, more efficient 3-nozzel engine. The designers hoped that these changes would bring the RLV's lift capacity up to the required levels necessary to carry the Rhea, or an equivalent payload, into LKO. A second Test-Block, TB-B, was used to fully test the capacity of the new engines, and assembled with the new RLV2 for a launch following the unsuccessful Munar 1 mission.

The initial launch provided an early scare as the rocket seemed to hover for a moment, with the engines at full power. Mission controllers were within seconds of triggering the automatic abort when the rocket lumbered skyward, much to the relief of all in attendance. The first stage lifted the payload to an acceptable altitude for the start of a gravity turn before its fuel was exhausted, and after it was jettisoned, the rocket continued on an easterly course to take it into orbit. It soon became apparent that the upper stage would fulfill its mission, as the rocket cleared the upper atmosphere, and even had some fuel left for an initial adjustment to the trajectory prior to the final orbital insertion burn, and giving it enough speed that the TB-B's on-board engine had no trouble circularizing its orbit at 100km with plenty of fuel to spare.

This success provided the final puzzle piece for the Rhea's first flight, designed to build knowledge and understanding of spaceflight and technologies that would be required for exploration of the Mun, Minmus and hopefully, other planets in the solar system...

Mission Photos:

RLV2 on the launch pad

Liftoff

RLV2's second stage carries TB-B eastwards

Clearing the atmosphere

Jettisoning the expended second stage

TB-B in its final orbit

[Specialist290]

Nicely done! I like the format you've chosen for these as well. Keep up the good work!

[jaws909]

Nicely done! I like the format you've chosen for these as well. Keep up the good work!

Thanks, having fun with it so far

[jaws909]

Mission: Rhea 1

Type: Manned test and LKO mission

Crew: Lanfry (Flight Tech), Bob (Command Pilot)

Objective: Test Rhea spacecraft in LKO, perform EVA to visually inspect spacecraft in orbit and test EVA-jet pack

Outcome: Success!

Status: Recovered

Notes: With the RLV2 successfully tested, the KSC leadership decided it was time to move forward with making Rhea's first flight. Although they had originally planned an unmanned mission, mounting pressure and scrutiny over the initial failures of RLV1, and the loss of Munar 1, pushed the team to launch a manned mission for the spacecraft's maiden flight. Bob was chosen as Command Pilot, with Lanfry filling the roll of Flight Tech. The plan was to reach a stable orbit of roughly 150km, test the ships systems, after which Lanfry would perform an EVA to both test the new EVA-jet pack, as well as a visual inspection of the spacecraft's exterior to check for damage or defects caused during the ascent. To counter the risk of a catastrophic loss, an LES (Launch Escape System) was designed and mounted to the top of Rhea's ANM(Avionics Nosecone Module), which would use a set of solid-fueled rockets to carry the crew capsule away from the launch vehicle in the event of a failure during the ascent, and later be jettisoned in orbit if everything went to plan.

Fortunately, the LES was not needed, as the RLV2 performed perfectly, carrying Rhea 1 up to its target orbit with no difficulties. After escaping the atmosphere, the RLV2 second stage was jettisoned, and the UM(Utility Module) fairing panels, which protected the communications and RCS systems during launch, ejected. After a brief system test and ensuring the Rhea's engine was functional, Bob performed the final burn to stabilize the craft's orbit. There he and his crew-mate waited while they circled around Kerbin's dark side until they were back in full sunlight, before moving on to the EVA phase of the mission.

Lanfry carefully exited the spacecraft, and performed some initial test maneuvers with the EVA-jets, in order to get a feel for the controls. Once he was confident that he was able to move about safely without smashing into the spacecraft, or worse, shooting himself off into space, he began a 12 minute flight around Rhea 1's exterior, inspecting the hull, RCS thrusters and main engine for damage. After both he and mission control were satisfied that there was no problems, he returned to the crew module. Rhea 1 and its crew then spent the next 11 hours evaluating the ships systems and taking time to test some of the more mundane necessities of long-duration spaceflight, eating, drinking and hygiene among them.

Finally the time came to initiate the descent procedure, with a de-orbit burn followed by the jettisoning of the UM. Finally the ANM was jettisoned, reducing the spacecraft to its crew-module only reentry configuration. However, the crew, and mission control, were horrified when the spacecraft suddenly went "dark". Unable to communicate with each other due to the comm system being without power, mission control and the Rhea 1 crew were cut off during the harrowing descent that followed. Rhea 1 entered the atmosphere as planned, and, fortunately, the mechanical fail-safe system for the parachutes automatically deployed them (albeit a bit higher than normal), to control the craft's descent. Mission control would later determine that Lanfry had forgotten to switch the breakers on the power board to properly charge the crew module prior to jettisoning the UM. On all future missions' flight manuals, this text would be printed in triple sized red font, to ensure all future crews would avoid the potentially deadly mistake. Aside from crew error, however, the Rhea 1 mission was a complete success, and the program was deemed ready for further missions...

Mission Photos:

Rhea 1, ready for launch

Liftoff

Separation from the RLV2 upper stage and ejection of UM (Utility Module) protective fairings

Lanfry performs his inspection of the UM's RCS fuel tanks

Lanfry near the Rhea's main engine on the UM

Rhea 1's UM as seen from the crew module, shortly after it was jettisoned prior to reentry

Rhea 1's mechanical failsafe system automatically deploys the parachutes after detecting a loss of power in the spacecraft during reentry

[jaws909]

Mission: Munar 2

Type: Mun Orbital Satellite

Objective: Place Munar 2 into low-Mun orbit, attempt to impact trans-mun booster into surface

Outcome: Success!

Status: Active in low-Munar orbit

Notes: Munar 2 was the second unmanned mission launched to the Mun. This time, rather than an impact probe, an orbital science probe would be sent to study the Mun from above. An impact would also be attempted using the booster that carried the probe to the Mun after it was expended. The spacecraft was carried aloft using an MS-1 (Munshot) rocket, specifically designed to carry the Munar probe missions. After the initial ascent, the probe entered a temporary 135x70km parking orbit, deployed its antennas and solar panels, and tested the on-board sensors. After mission control deemed the craft to be in working order, the trans-munar burn was performed, hurling the probe on an intercept course similar to that of Munar 1, but without a direct impact trajectory.

Several hours later, as Munar 2 neared its closest approach (roughly 80km above the surface), a second burn successfully placed it into a 79x35km orbit. From there it used the on-board camera to capture the first upclose images of the Mun's surface, as well as the first from its far side. Once back on the Kerbin side, mission controllers instructed the probe to use its engine one final time to place it on an impact trajectory, then jettisoned the trans-mun booster and used the probe's RCS thrusters to reestablish orbit, this time in at 60x15km. Munar 2 then tracked the booster visually with its camera, and by radar after it passed below visual range, until it impacted into a mountain range, becoming the first object known to make contact with another celestial object (Munar 1 theoretically already accomplished this feat, but could not be confirmed). Afterwards the probe continued to examine the surface with its sensors and camera, providing valuable data for future missions...

Mission Photos:

Munar 2 and its MS-1 rocket on the launchpad

Munar 2 in LKO, performing systems tests prior to the trip out to the Mun

Munar 2 captures a shot of Kerbin to test its camera after the trans-munar burn is completed

Munar 2's first close up image of the Munar surface

The expended trans-mun booster begins its descent towards the surface

Last clear image of the trans-mun booster (a small white speck near the center of the image) from Munar 2

Area where trans-mun booster finally made contact with the surface

A large canyon taken near Munar 2's lowest orbital altitude of 15km above the surface

[jaws909]

Mission: Rhea 2

Type: Manned LKO Orbit

Crew: Jebediah (Command Pilot), Buremone (Flight Tech)

Objective: Establish inclined LKO, perform simultaneous EVA

Outcome: Success!

Status: Recovered

Notes: The Rhea 2 flight was used by both mission control and the crew to build experience in low-orbital operations, namely EVA's in which both crew members would be outside the craft, as well as determine the feasibility of launching into an inclined orbit. An RLV2 carried the spacecraft into an initial 120x70km orbit at an inclination of nearly 40 degrees. Once there, Jebediah used the Rhea's engine to increase the apoapsis to 450km, and the periapsis to 100km.

Once in a stable orbit, the crew performed an initial EVA with Buremone leaving the spacecraft to perform a visual survey over the UM (Utility Module) and ANM (Avionics Nosecone Module), then returned to rest before another EVA was performed, in which Jebediah took part, circling the spacecraft while Buremone hovered near the hatch in case of trouble. After spending a few more hours in orbit, the Rhea 2 crew performed their de-orbit burn and returned safely to a water landing in the ocean south of the KSC, just over 12 hours after launch. The mission successfully proved that multiple crew members could perform an EVA safely together, and that by changing the initial ascent vectors, a spacecraft could more easily determine its final orbital inclination. Rhea 3's objectives would be to build upon this and previous missions, and attempt the first manned orbital rendezvous and, hopefully, docking...

Mission Photos:

Rhea 2 burning to a 450km apoapsis

View from Rhea 2 of Kerbin at a height of 450km

Buremone performs his first EVA

Buremone and Jebediah together on the first dual-EVA

An evening landing south of the KSC

[jaws909]

Mission: Rhea 3 & Artemis I OTV (Orbital Target Vehicle)

Type: Manned LKO (Rhea 3) and unmanned target craft (Artemis I)

Crew: Bill (Command Pilot), Scott (Flight Tech)

Objective: Launch Rhea 3, launch Artemis I OTV, conduct orbital rendezvous and docking, conduct EVA to simulate spacecraft repair and other tasks for future missions

Outcome: Success!

Status: Recovered (Rhea 3), Active in LKO (Artemis I)

Notes: The Rhea 3 mission was another first for the KSC team. It would be the first attempt to intercept another spacecraft in orbit using a manned orbiter, and it would be the first docking attempt. The mission was carried out in three phases.

First, the Artemis I OTV (Orbital Target Vehicle) was launched atop a RLV2 into a 250km orbit. This launch proceeded without issue, and the craft successfully reached its target orbit. Mission control then performed basic systems checks and oriented the craft inline with Kerbin's axis, to make approach and docking easier for the Rhea 3 crew to follow.

The second phase was the launch of Rhea 3. This too went smoothly, until it came time for the planned intercept. The relatively low thrust of the Rhea's main engine meant that it had to make several long duration burns to affect the required changes in its orbit in order to meet the Artemis. The pilot, Bill, being untested, had some difficulties in plotting the intercept initially, but eventually was able to fine tune his course to bring him within 1km of his target. Once he had brought himself into a matching orbit, he was able to move Rhea 3 in closer using the RCS system, and carefully moved in and safely docked with the Artemis.

This brought the mission to phase 3, where both crew members would spend time performing an EVA, carrying out various simulated tasks on the combined spacecraft to simulate working to repair a satellite or other type of craft. This was an important test for future missions, namely the planning of the manned Mun exploration program currently under development, but also the more long-term orbital station program also on the drawing board. They also performed a burn, using the more powerful Artemis I engine to move their combined craft into a 250 x 500km orbit, as well as transferred fuel between the two craft and used the Artemis' solar panels to recharge the Rhea's batteries. Once all objectives of the mission had been met, Rhea 3 un-docked and left the Artemis in its new orbit, and returned safely to Kerbin.

Mission Photos:

The Artemis I and its RLV2 standing by to launch

Artemis I is successfully delivered to orbit

Rhea 3 prepares to meet the Artemis I OTV

Artemis I as seen from Rhea 3 during its approach

Bill and Scott performing simulated repairs on the Artemis I

Using the Artemis I engine, Bill guides the Rhea 3/Artemis I into a higher orbit

[Specialist290]

That fairing separation screenshot has a very cinematic feel to it. I could see someone using it as a wallpaper background image.

[NathanKell]

This is great stuff!

[jaws909]

Ya, I love the procedural fairings mod, it brings an awesome flavor to the game!

[Geschosskopf]

Very cool space program with elegant rockets. My own efforts lack such discipline and artistry

[jaws909]

Mission: Munar 3

Type: Unmanned Munar Lander

Objective: Land Munar 3 intact on Munar surface

Outcome: Success!

Status: Landed on Mun at 0* 14' 43" N 109* 49' 52" W, Batteries depleted

Notes: Munar 3 was the first attempt to land a probe on the Mun in a controlled fashion. The lander itself featured a small central fuel tank and accompanying engine, a communication array and scientific instrumentation, and deploy-able landing legs arrayed in a tripod configuration. It was carried by an MS-1, the same launcher design that had successfully delivered Munar 2 to its destination.

Launch proceeded smoothly, with the MS-1 easily carrying the small lander into orbit before the TMB (trans-Mun Booster), modified to carry solar panels in order to keep the Munar 3's batteries charged, took over to carry the probe to its new home. The TMB performed two burns, one to place the probe into orbit, and another to bring it within 7km of the surface. The intended landing site was near the large canyon previously sighted by Munar 2, but the uneven nature of the terrain meant that the actual landing would be too far to provide any up-close imagery of the canyon itself.

The TMB performed one final burn to reduce the probe's orbital velocity and set it on a suborbital trajectory, and was then jettisoned away. It later crashed a few KM away in a large crater. Munar 3 then made the final descent under its own power, the mission control looking on anxiously as the radar altimeter ticked down the last few hundred meters to the surface. After a few tense moments, the signal everyone had been waiting for, triggered by the engine shutting down after sensors on the probe detected contact with the surface, came over the monitors in mission control, with cheers erupting across the room. They then sent the signal to activate all the scientific equipment on board to begin collecting data, and used the on-board camera to capture the first image ever from the surface of the Mun. The probe transmitted data for about 5 hours, at which time the last of the stored battery power was exhausted, and its mission was complete...

Mission Photos:

Munar 3 prepares for launch

Munar 3 and its TMB (trans-Mun Booster) leaving LKO

Munar 3 approaching the 7km mark and the final TMB burn

The TMB discarded, Munar 3 starts its descent

Landing legs deployed

Touchdown!

First image from the surface of the Mun

[jaws909]

Mission: Titan II

Type: Launch Vehicle Test

Objective: Launch payload to 80km orbit

Outcome: Success!

Status: Deorbited

Notes: Ramping up their progress towards manned exploration of the Mun, the KSC team launched their first test of the Titan II launch vehicle. This rocket was designed to carry heavier probes to the Mun or Minmus, as well as provide a means of transporting manned spacecraft into LKO. Specifically, it was intended to carry the planned Zues spacecraft and its accompanying Munar Lander (ML) into LKO for early test missions. A larger variant, the Titan III, was also being developed for actual manned missions to the Mun. The Titan II was put to the test by mounting a large dummy payload of comparable weight to the Zues and its lander, with the goal of taking this to a stable 80km orbit. If this mission was successful, a further operational test was planned in which the Titan II would carry a robotic rover (Munar 4) to orbit for delivery to the Mun.

The launch proved successful, with the Titan II's first stage carrying the rocket to ~20km, before the second stage was ignited to carry it the rest of the way to orbit. The payload had been fitted with its own engine and fuel supply to allow it to be de-orbited, but the Titan II's engines were adequate to take the craft to 80km, establish orbit, and then perform a de-orbit burn to ensure it reentered the atmosphere and was destroyed to reduce debris in space.

Mission Photos:

Titan II on the launchpad

Liftoff

Turning east and flying over the coastal islands

First stage separation

Completing orbital insertion

[jaws909]

Mission: Munar 4

Type: Automated Rover

Objective: Explore Munar surface

Outcome: Failed (Rover damaged during landing)

Status: Landed on Mun at 1* 18' 42" N 59* 6' 10" W Disabled due to damage

Notes: Munar 4 was the KSC's first attempt to land an unmanned rover on the Mun. The mission plan called for a Titan II to carry the rover and its landing vehicle into orbit, and then on to an intercept trajectory. From there, a braking stage would slow the craft and place it on a descent trajectory before the landing stage took over to control its descent. As it neared the surface, the rover's descent speed would be slowed to near 0, and then it would be released. The descent stage would then be carried away to a crash landing clear of the landing site to prevent it falling on the rover and damaging it.

The mission was initially plagued by an instability during its ascent, likely due to poor welding in the structural components of the first stage, and experienced some gyration during the climb. This however, was overcome, and after the second stage took over vanished and allowed the craft to reach orbit safely. From there, the Titan II second stage engine was used to propel the craft onto an intercept course, before it was discarded. Ground based telescopes would later confirm that the Titan II second stage was ejected from the Kerbin system by the Mun's gravity, making it the first object to achieve heliocentric orbit.

Once it had reached the Mun, Munar 4 was placed onto a descent course by the braking stage, which was then jettisoned. Next, the descent stage took over, controlling the rate of descent and slowing its speed to allow for the rover to be safely jettisoned. However, a problem arose when the descent was found to be slightly off course, and it came down over a large crater. The sloped sides made it difficult for the computer to accurately judge when to release the rover, and it was accidentally released higher than expected, causing one of its wheels to be damaged during the landing. This meant that the rover was unable to move, and thus, the mission was deemed a failure despite all other systems working properly. Mission control placed it in standby mode and marked its landing site as a possible target for one of the Zeus missions, if it was deemed possible to repair on the Munar surface...

Mission Photos:

Munar 4 and its Titan II

First stage separation

Entering Munar orbit

Discarding the braking stage

Final descent

Photo from Munar 4, slanted due to a damage wheel

Munar 4 rover, disabled on the surface

Edited September 8, 2013 by jaws909

[jaws909]

Zeus, the Mun and beyond

Rhea and the early Munar flights, by their successes and failures, had provided the building blocks and fundamental experience the KSC team needed to move forward with their next major project. That mission, the Zeus program, aimed to put a manned mission on the Munar surface, and, after initial exploration by unmanned probes, Minmus as well. The Rhea spacecraft, reliable as it was, was too bulky and lacked the necessary equipment to make the journey (rechargeable batteries, full scale docking ports, a suitable engine). The crew capsule, however, was sound and would be incorporated into the new design with some internal modifications to allow for 3 crew members. A new service module was also designed, with a more powerful engine, solar panels, a robust stability assistance system and a long-range communication array. The Munar Lander which would carry two of the Zeus astronauts to the surface, was also entering the test phase of development, with ML-1 undergoing initial engine testing and crew training exercises at the KSC. The Titan III, intended to launch the Mun/Minmus missions, was still undergoing final design evaluations, but confidence was high that once the LKO Zeus/ML testing missions were complete using Titan IIs, it would be ready for flight...

Bill and Jeb take a break during a simulated Mun landing mission with ML-1

Zeus 1 - Success Unmanned test flight of Zeus spacecraft

Zeus 2/Rhea 4 - Success First operational flight of Zeus, first docking between two manned spacecraft

Munar 5 - Success First successful Mun rover

ML-3 - Success Unmanned orbital test of Mun Lander

Zeus 3 - Success Manned orbital test of Mun Lander

Titan III - Success Titan III Launch Vehicle test

Zeus 4 - Success First manned orbit of Mun

Zeus 5 - Success First manned Mun landing

Discovery 1 - Success Minmus orbiter

Discovery 2 - Success Minmus lander

Zeus 6 - Success First manned Minmus landing

-----

Mission: Zeus 1

Type: Unmanned test flight

Objective: Test Zeus flight systems in orbit

Outcome: Success!

Status: Recovered

Notes: The Zeus spacecraft's maiden flight, Zeus 1, was a standard LKO mission, intended to test all of the ship's systems in space, before it was committed to manned missions. The near disaster with Rhea 1 had precluded any manned spacecraft from being flown by a crew prior to a full evaluation for safety reasons, and the Zeus passed with flying colors. From its initial launch atop a Titan II, to its orbital insertion and systems checks, all the way to reentry and recovery, every system functioned perfectly. With this success, the KSC team had high hopes for the future of manned exploration, both to the Mun, Minmus, and beyond...

Mission Photos:

Zeus 1 prepares for a night launch

Liftoff

Flight systems testing in orbit

A flawless reentry and recovery

Edited September 14, 2013 by jaws909

[jaws909]

Mission: Zeus 2/Rhea 4

Type: Manned LKO

Crew: Zeus 2 - Jebediah (Mission Commander), Bill (CM Pilot), Bob (LM Pilot/Flight Tech); Rhea 4 - Scott (Command Pilot), Lanfry (Flight Tech)

Objective: Test ML (Mun-Lander) Shroud by carrying Rhea/Zeus Docking Adapter to LKO, dock using Rhea/Zeus docking adapter

Outcome: Success!

Status: Recovered

Notes: The Zeus/Rhea docking experiment was born out of the necessity to test various technologies. The KSC team wanted to test the viability of the ML Shroud, the protective compartment in which the Mun Lander would ride the Titan II/III to orbit beneath the Zeus spacecraft. They also wanted to test the new full size docking port of the Zeus, but ML-2, the first operational Mun Lander, was not yet ready for flight. Instead, it was decided to use one of the already assembled Rhea spacecraft, Rhea 4, which originally had been slated for a docking mission with Rhea 5, to fill the role of ML-2 by acting as an orbital docking target. This however, required either extensive modifications to the Rhea's nose structure, or the use of an adapter to allow the Zeus to dock. A small module (the Rhea/Zeus Docking Adapter) was designed and built to be carried aloft with the Zeus, riding in the ML Shroud to orbit where it would be extracted before rendezvous with Rhea. One end would have a Rhea docking port, and the other would house a full scale Zeus/ML docking port.

It was decided that Zeus 2 would launch first, carried aloft by a Titan II with the ML Shroud fitted to the top of the second stage, below the Zeus service module (SM). The launch proceeded smoothly, with the Titan II having no trouble carrying the extra weight to a 100km orbit. Once there, the Zeus pilot, Bill, separated the spacecraft from the second stage, jettisoning the ML Shroud fairings and exposing its cargo. He then turned the Zeus around and brought it in to dock with the Zeus side of the docking adapter, before it was separated from the Titan II second stage. Zeus 2 then moved into a 125km orbit to await the arrival of Rhea 4.

Rhea 4 was launched once it was assured that all systems were working properly with Zeus 2, and that it had successfully retrieved the docking adapter. It was carried aloft using the RLV2 like all previous Rhea missions, and the launch was uneventful. Once in orbit, Rhea 4's Command Pilot, Scott, intercepted the Zeus 2 and successfully performed the first docking of two manned spacecraft. Afterwards, the Zeus 2 un-docked and performed some maneuver tests before returning to dock a second time with Rhea 4.

With their mission completed, both crews prepared to return home. Zeus 2 de-orbited first, with Rhea 4 completing one more orbit before un-docking the adapter, which was left in a stable 80km orbit, and then returned as well. Both spacecraft returned safely to a splash-landing east of the KSC.

Mission Photos:

Zeus 2 with its Titan II, featuring the ML Shroud designed to carry the Mun Lander aloft in later missions

Zeus 2 lifts off

View from Zeus 2 of the Titan II upper stage and exposed docking adapter before it was extracted

Removing the docking adapter from the Titan II second stage

Rhea 4 lifts off

Zeus 2, as seen from Rhea 4 during approach

Coming in to dock

Docking successful

Zeus 2 ruins a perfectly good photo of the Sun from Rhea 4 during maneuver tests

Zeus 2 maneuvers in to dock with Rhea 4 a second time