|
||||||||||
|
Here's a variation on defining the task ahead and identifying options for the program architecture. Breaking down the major functions of the transportation system to identify the solution space seems to be the best apporach.
1. Introduction
This study defines a plausible program architecture for regularly scheduled commercial passenger flights between Earth and the Moon. The baseline mission is daily flights leaving a single spaceport on Earth, with a single spaceport on the Moon supporting traffic at the other end.
2. Assumptions and Guidelines
3. Mission Architecture Options
The solution space encompasses:
options: 10 to 1000
baseline: 50
The solution space includes:
Fueling Options
LEO | LLO | LS | |
Single vehicle | Required | ? | Yes |
Dedicated LEO-to-LS vehicle | No | ? | Yes |
LEO-to-LLO vehicle | No | Required | No |
LLO-to-LS vehicle | No | No | Yes |
The solution space includes:
Depending on the state of lunar development, it might be economically feasible to start out with tourists using the transportation vehicle as living quarters until permanent facilities are built on the Moon. This ties up the capital resource for a longer time per flight, but it would allow the lunar tourism industry to commence operations sooner.
If lunar tourism can start several years earlier using this scenario, for many people it will mean the difference between having the opportunity to go to the Moon, and never going there at all. It is likely that the ship would fly with all seats filled, even at $500,000 per ticket.
The solution space for this mission phase is identical to the trip from LEO to the Moon.
The solution space includes:
We need another applicability table here. Obviously, if we're carrying fuel back from the Moon for the next flight out, we don't have an option of heading straight down to the surface.
The solution space includes:
In all cases, we assume the vehicle returns to its original launch site on Earth, and is immediately readied for another trip.
|
|