Alright this semester might only mostly suck, but it is time for a return to flight in the wake of
Copernicus taking a small drink and some other steps toward the next flight, so thanks to
defconh3ck for the assistance in these developments and on we go:
Chapter 6: Back in Business
Copernicus bobbed along assisted back to Port Canaveral between two tug boats and towed by
MV Freedom Star. Visitors to Jetty Park and the rest of the port looked on as the battered
Copernicus floated slowly by. The tugs pushed the stage up to a dock and cranes carefully fished it out of the water. The cranes held
Copernicus over the edge of the concrete letting all the water drain out of her before swinging her over the ground to lower her onto a set of transporters that had only just arrived.
Copernicus was hurried back to the VAB to begin inspection with no shortage of onlooker attention. NASA would maintain the accident was of little lasting concern, this was a test program after all, they would especially stated that it would be best to wait before jumping to conclusions. This didn’t stop some from beginning to doubt the system, but others would state the contrary, so far the system had only two flights, it was simply too soon to say. In any case, NASA began to work out where to go now, but it would take the partial completion of the investigation into
Copernicus to know for sure. In the meantime,
Voyager was still in the ring, so far nothing serious had arisen in the vessel and she continued her three day cruise to her short capture burn around the Moon.
Voyager’s capture burn would go as planned, placing the orbiter into a highly eccentric orbit which would bring her close to the lunar surface. The first pass would bring a photo in the works since 2005, Earthrise from
Voyager’s flight deck. Combined with
Voyager’s continued great health, the program appeared so close to returning humans to the Lunar surface already. Countering engineer’s concerns, the drop tanks were holding well and keeping the OMS engines fed for the trip so far. Also performing as hoped was the new solar-electric power system that had replaced the fuel cells, operating from a solar array mounted at the front of the payload bay in a similar arrangement to the Ku-band antenna, only on the other side. The system had functioned well on PTC-1 as well, but it was even more vital here. Over the course of a week, Voyager would help mission controllers refine lunar operations, especially communication through the Deep Space Network, a new operation in regards to a shuttle. Meanwhile, her MPLM collected data to guide mission planners in future operations. One of the many experiments aimed at future operations actually sat outside the MPLM. Dozens of swatches of potential space suit sections were placed in the payload bay where they could be exposed to the intense environment. Building on lessons learned from the suits used both around the ISS and in the Apollo missions, hoping to improve functionality and safety of the new suits with these materials.
Eventually, the time came to return and
Voyager lit her OMS engines again, sending her into a return trajectory to Earth that would involve seven passes over the course of six days to slowly bring the orbiter down to a safe speed to descend through to Edwards AFB on the final pass.
Voyager would orient herself to point towards the now oncoming Earth and sent the command to separate her, now purged, drop tanks. The tanks released their hold downs and fired their small separator motors, clearing them from the vehicle and lowering their orbit a little more and ensuring a safe disposal into the atmosphere. She would soon transition from the DSN back to TDRS as she passed under the relay network’s purview. Mission controllers would hold their breath as
Voyager closed her bay doors and made her first pass. She would soon rise back out of the atmosphere, regaining a temporarily lost connection to TDRS and reopening her payload bay doors for the first go around. After a positive health check of the orbiter,
Voyager would swing around and repeat the process five more times, slowly inching her orbit lower and lower. Eventually, the final stretch was upon her, hopefully this pass would be closer to a normal reentry now that her orbit had been dropped to a more typical altitude. One last time,
Voyager opened her payload bay to allow her radiators to function, but she would not deploy her solar array or Ku-band antenna. As she made her just over 100-minute final orbit, observation aircraft made their way to their respective places for the final time to watch the orbiter hurdle in for landing. With exception of being slightly higher energy,
Voyager made an excellent repeat of her performance on her previous mission. She lazily swung through her S-turns and brought herself closer to Edwards with the ever-familiar sonic booms, eventually bringing her legs down onto the marked runway in the desert. Her drogue chute weakly popped out and eventually deployed fully later than hoped. Thankfully with the long runway allowed the orbiter had the room to slow down safely. Later the issue would be discovered as a weak detonation of the deployment charge caused by additional resistance from trapped heat around the wiring only now arriving after slowly working through the heat tiles.
The aftermath of the mission was a mixed bag. On the one hand, the mission had been completed successfully, giving NASA plenty of data to work with. On the other, the loss of a brand new core stage and the weak drogue deploy were a bit worrying, though to very different degrees. NASA maintained that the loss, while certainly not hoped for, wasn’t entirely out of the question for the fledgling system and the lasting effects would hopefully be minimal. The parachute was also noted as being a relatively simple fix. Either way, NASA would suspend flight operations for about a month while they mulled over the data and the watered down
Copernicus. It didn’t take long for NASA, in cooperation with the other governmental agencies, to narrow down the problem, the boil off was just faster than projected, not at all assisted by this stage's prolonged direct exposure to the sun, something absent from
Polaris’s mostly night flight. Following a report that
Copernicus had done everything as correctly as she could have and the issue was out of her hands, NASA partially lifted the suspension, still keeping the hold on high energy flights until corrective measures, yet to be determined, could be implemented. Eventually, corrective measures would be found, the “chandelier” landing tanks would be moved from their place, up against the tank wall to hanging from the center. The added stability from the offset center of mass was noted from the first two flights as negligible, its help would not make up for a malfunctioning fin or otherwise. Additionally, better, and heavier, insulating materials would be used and the mass limit for high energy payloads would be somewhat lowered to provide a larger propellant buffer for boil off. By an extreme stroke of luck,
UCS Vega was entering the stage of production at Michaud where these changes could be inserted without major disruption and minimal backtracking, after a brief hold on production to design the new configuration, the altered tank would be installed. Once
Vega would arrive at KSC, NASA planned to send
Tauri back for the retrofit of the tanks, followed by
Polaris once
Tauri had returned.
The loss of
Copernicus had also managed to revive something from the initial planning stages back in 2005. So far, UCS had two “blocks”; Block 1, the “expendable” or the later “special request” version and Block 2, the primary version with propulsive landing. Besides that, however, there initially existed another option for the Block 2, a flyback stage. The current Block 2 had won out with the possibly higher payload up mass from the obvious lack of having wings to weigh it down. With the potentially permanent reduction of the capability of Block 2, however, the flyback variant, now being labeled as Block 3, was back on the table. It offered an advantage that only increased as the stage went farther away from the Earth. While Block 2 would need more and more propellant to sate the inevitable boil off, even with the boost back burn to return the stage home sooner (which itself dug into propellant margins), Block 3 would only need propellant for the boost back burn. Block 2 would still be the king of lower altitude flights, with the short flight time meaning less of a boil off buffer required and lacking the "dead weight" of wings, and, with restrictions, it could still handle some higher flights, but Block 3 would restore most of the lost up mass capacity to farther destinations. This would take time in development for certain, but thankfully the temporary solutions put in place wouldn’t suffocate the program and amended plans would soon begin to march onward.
Speaking of which,
Voyager was now getting her first partner. Drifter arrived while
Voyager was cleaned up after her long ride. While
Voyager got a heavy inspection, Drifter began preparations to carry out the grand honor of the first crewed flight of the system under the PTC-3 mission, aiming for a six day LEO free flight. Over in California, another orbiter was almost done as well. Work on
Wayfarer was winding down as the final touches were being made. Next door,
Traveler was halfway through construction herself, soon hoping to bring the Phoenix fleet up to four. Enough vehicles were arriving to set up the rapid cadence always envisioned for such a system. Also in support of this goal, the horizontal transporters had finally been completed along with the two FPF’s.
Groundwork was also starting to roll on an adjacent facility, the Emergency Call Orbiter (ECO) facility, which would be similar in style to the FPF’s, instead having bays to support two Phoenix stacks horizontally and a workspace in between. This facility would keep one stack in a “ready to go” state should an emergency ever arise, requiring the rapid launch of another orbiter. Ideally, this setup would minimize disruption to other ongoing operations in the midst of whatever chaos arises while scrambling a stack, also aiming to lower the risk of “rushing” a stack to the pad as it would already be ready. Realistically, though, the ECO program was an elaborate excuse to conduct regular maintenance on the various vehicles of the program without inconsistently scheduled maintenance interrupting an otherwise busy cadence. The processing flow would be somewhat complicated, starting with the new stack coming in for ECO service being “field stripped” having all removable sub-assemblies removed, such as engines, OMS pods, airlocks, etc. Once those were taken off, the components removed from the previous ECO stack from when it entered service, now inspected and repaired as needed, would be installed on the incoming stack. When the fresh components were installed, the former ECO stack leaves, reentering active service and the new stack goes “on duty” while its former components are inspected and repaired for the next stack.
Moving back to the FPF’s, FPF-1 was getting ready to host its first mission, UTS-1 which would be the first of the “buffer manifest”, a group of missions that NASA would need to fly and could not risk missing due to a late launcher, such as cargo resupplies or crew rotations for the ISS. These missions were slated to fly on STS or UTS, in order to either give Phoenix something to do for early flights to build confidence in the system, or keep these needed missions running on STS if Phoenix ran behind schedule as it predictably was from the landing gear redesign. There were originally a total of nine missions, with four already being taken by STS in Phoenix’s absence.
Voyager, once she had been inspected to within an inch of her life, would venture out once more for the first of these remaining flights, carrying seven crew and cargo on an ISS cargo resupply run. It would be a seemingly slow start, but among these first flights, the program would show no lack of ambition, aiming to soon take the first of many steps towards Mars.