Akshay DineshNASA has opened a new engineering competition that asks students to solve practical problems involved in living and working near the Moon’s south pole. The Moon Base Student Challenge is open to eligible teams at U.S. high schools and post-secondary institutions, with registration due January 25, 2027. NASA describes the program as a $1 million challenge, but its real value goes beyond the prize pool: teams must make design decisions under constraints, compare alternatives, and explain their reasoning in formats used by working engineers.
No previous aerospace experience is required. That does not make the problems easy. A clever sketch is only a starting point when a system must survive abrasive dust, extreme temperature swings, long periods of darkness, communication delays, and tight limits on mass and power. Strong entries will turn one of those constraints into a focused question, then show why a particular solution is more practical than the alternatives.
What the Moon Base Student Challenge asks teams to do
The competition has six technical categories: power generation and storage, habitat construction, life-support systems, surface mobility, communication networks, and astronaut safety. Together they describe the basic systems a sustained lunar outpost would need. A rover cannot travel far without reliable energy and communications. A habitat cannot protect its crew if its life-support equipment cannot recycle water, remove carbon dioxide, and control temperature. Every category connects to the others, even though each team chooses a defined problem to solve.
NASA says the challenge uses authentic environmental and mission-design parameters. Teams are expected to produce work resembling an engineering trade study, a concept proposal, and a stakeholder briefing. A trade study is a structured comparison of possible solutions. Instead of declaring that one idea is best, a team identifies criteria such as safety, mass, power use, durability, repairability, cost, and technical risk, then explains how different options perform against them.
That structure keeps the competition from becoming a science-fiction art contest. A dramatic-looking lunar settlement may be imaginative, but an engineering proposal must answer harder questions. What need does the design meet? Under what conditions must it work? What can fail? What assumptions drive the result? A modest concept with clear evidence and honest limits can be stronger than a spectacular idea that never confronts those questions.
Who can enter and which dates matter
The challenge is organized in separate high-school and post-secondary divisions. The published rules call for teams of two to five eligible students with an adult coach and an eligible U.S.-based educational organization. Post-secondary eligibility is more specific than simply attending any college, so students should check their institution against the official requirements before building a team. International students at a U.S. institution may face additional conditions. The safest first step is to read the current rules as a group and resolve eligibility questions before investing time in a proposal.
Registration takes place through NASA STEM Gateway and closes January 25, 2027. Registration is not the same as submitting the finished project. The current schedule lists an opening symposium on December 3, 2026, a technical question-and-answer session on January 14, and a second support session on February 11. Project-phase submissions are due February 22, finalists are scheduled to be announced March 11, and the final phase begins March 15.
Finalists are scheduled to submit their final materials by April 19, with awards announced at a closing symposium on May 6. Competition dates can change, so teams should rely on the current official schedule rather than an old screenshot or a calendar copied from someone else. Assigning one person to track rule updates, registration records, and deadlines is a small piece of project management that can prevent a strong technical entry from becoming ineligible.
The initial deliverable is described as a five-to-seven-page Concept Overview Paper, excluding its cover and references. Finalists advance to a recorded pitch of up to ten minutes with an accompanying slide deck. Computer-aided design and physical prototypes can help when they clarify a mechanism, but they are optional. A team can build a persuasive entry with accessible diagrams, calculations, and a well-supported comparison of choices.
Choose a problem before choosing a gadget
The strongest starting question is not “What can we build?” but “What must astronauts be able to do?” A power team might ask how essential equipment could operate through a long period without sunlight. A construction team might study how to reduce material shipped from Earth. A mobility team could focus on moving cargo across steep, dusty terrain without trapping a vehicle. Each question defines a need, a user, an operating environment, and a measurable sign of success.
From there, teams can narrow the scope. “Design lunar life support” is far too broad for a short proposal. “Compare two methods for removing carbon dioxide from a four-person habitat during a defined mission period” is manageable. The narrower version invites research, calculations, failure analysis, and a clear decision. It also leaves room to explain how the chosen subsystem would connect to the larger base.
The six categories reward different combinations of skill. Students interested in electrical systems may gravitate toward power or communications. Those studying construction, manufacturing, or materials can contribute to habitat concepts. Biology and chemistry matter in life support, while programming and robotics fit mobility and monitoring. Astronaut safety draws on human factors, medicine, sensing, procedures, and protective design. A team does not need five people with identical backgrounds; it needs people whose abilities cover different parts of the problem.
Before settling on an idea, write a one-sentence requirement. For example: “The system must provide emergency electrical power to critical habitat equipment for a specified number of hours after the primary source fails.” Then list the assumptions hidden inside it. How much power is critical? What temperature range must the system tolerate? Can astronauts repair it? Does it need redundancy? This exercise exposes vague thinking early, when changes are cheap.
Build a trade study that makes the reasoning visible
A useful trade study begins with at least two plausible approaches. If the team has already decided that its favorite idea must win, the comparison will feel staged. Research each option well enough to identify real strengths and weaknesses, then choose criteria tied to the requirement. For a lunar power system, the criteria might include energy delivered per unit mass, performance in darkness, operating temperature, maintenance needs, safety, and maturity of the technology.
Not every criterion deserves the same weight. Crew safety may matter more than manufacturing convenience, while mass may be more important for hardware launched from Earth than for material produced on the Moon. Teams should explain their weighting instead of hiding it inside a final score. A simple table can be effective, but the numbers need a defensible basis. Scoring an option “9 out of 10” means little unless the reader knows what a nine represents and what evidence supports it.
Calculations should match the maturity of the concept. An early design does not need false precision, but it should check orders of magnitude. If a battery proposal claims to power a habitat, estimate the energy demand and compare it with realistic storage capacity. If a rover must cross a certain distance, estimate travel time, energy use, and the effect of slopes or detours. If a shielding concept relies on lunar soil, estimate how much material must be moved and what equipment would handle it.
Risk deserves its own attention. Teams can identify likely failure modes, the consequence of each failure, how it might be detected, and what backup would exist. This does not weaken a proposal. It shows that the designers understand the difference between an appealing concept and a dependable system. State uncertainties plainly, especially when data about lunar operations remain limited.
Turn the analysis into a clear paper and pitch
A strong Concept Overview Paper should make its central decision easy to find. Begin with the problem and the requirement, then describe the lunar conditions that shape the design. Introduce the options considered, show the trade study, present the selected concept, and discuss risks and next steps. Diagrams should carry information that prose cannot convey efficiently: system boundaries, flows of power or material, component relationships, operating sequences, or comparisons of scale.
Citations matter because judges need to distinguish evidence from assumption. NASA technical reports, mission pages, peer-reviewed research, government data, and university engineering resources are better foundations than unsourced summaries. Keep a shared source log from the first research session. Recording the title, organization, date, useful claim, and link at the moment a source is found is much easier than reconstructing references the night before submission.
The finalist pitch requires a different kind of compression. A slide deck should not be the paper pasted onto slides. In ten minutes, the audience needs to understand the need, the constraint that makes it difficult, the alternatives considered, the reason for the choice, and the most important risk. One clear diagram or comparison can do more work than a screen full of text. Practice should include questions from people outside the project, because confusion from a fresh listener often reveals an assumption the team has stopped noticing.
Students should also be precise about what the prize means. NASA describes up to $1 million in monetary awards across the competition; it is not a guaranteed payment to every entrant, and a winning student concept is not automatically flight hardware. The practical achievement is demonstrating that a team can define a complex problem, work across disciplines, use evidence, make tradeoffs, and communicate a decision. Those skills transfer far beyond lunar engineering.
The Moon Base Student Challenge gives teams enough freedom to be inventive and enough constraint to make the work serious. The best entry will not try to solve the entire Moon base at once. It will choose one consequential problem, define it carefully, compare realistic options, and let the evidence lead to a design that can be explained with confidence.
