R
radarredux
Guest
> <i><font color="yellow">Rather than taking one craft to the surface that could fail as it almost did with Apollo, you have several.</font>/i><br /><br />The t/Space architecture includes travelling in pairs of CEVs to the Lunar surface (in their model, the CEV only travels between LEO and the Lunar surface -- it does not travel return to Earth's surface). If there is a problem with one CEV, the crew from the crippled one would transfer to the good one, and both crews would return in a single vehicle. It is the wagon train approach. Safety through redundancy.<br /><br />Regarding abandoning the abort directly to Earth, t/Space argues that there are not a lot of failure conditions where a spacecraft is so crippled that it can return to Earth but not perform aerobraking. Meanwhile, the ESAS introduces some additional failure modes.<br /><br />For example, suppose the Lunar liftoff stage of the ESAS cannot dock with the CEV in Lunar orbit. Can the Lunar liftoff stage return safely to the Lunar surface? Or suppose after docking with the CEV in Lunar orbit the astronauts discover something wrong with it and that it cannot return to Earth. Can they return to the Lunar surface? Or can they wait in the CEV for six months until the next Lunar mission?<br /><br />But the t/Space architecture, like the SpaceDev architecture, is focused only on going to the Moon.<br /><br />PS. As far as I can tell, the SpaceDev architecture throws away as much as the ESAS architecture does.<br /><br />PSS. The ESAS architecture does not preclude using a Bigelow inflatable as a habitat that can left on the Moon and reprovisioned in subsequent missions. When Griffin unveiled the ESAS architecture, the Lunar lander was the least defined element of the mission. He described the images as "notional only".</i>