The Ascent

See what your students get, and why it lands.

No mockups. Every page below is real, pulled straight from the files you download. Tap any one to see it full size.

A worksheet was never going to teach this. Your students are running a launch.

Each day opens with a real mission release: vehicle specs, telemetry, and a Go or No-Go call that has to be made before the period ends. In STARFALL, teams of two or three compute a Tsiolkovsky budget for a low-orbit launch and discover the textbook velocity of 7,670 m/s leaves out gravity losses and drag, so the real requirement is 9,170 m/s. Your students are not answering questions. They are deciding whether a launch flies, whether a crew aborts, whether a Mars cargo run holds its margin. The math is the only thing standing between their decision and a catastrophic failure, so they treat it that way.

Tap to see a daily release

They are graded on the reasoning, not on whether the mission flies.

The Decision-Outcome Coherence rubric separates the process from the result. A team that runs sound analysis and loses the mission still scores 16 to 20, because the reasoning was robust and the failure was honest. A team that gets lucky with a weak process scores 12 to 16, a flagged win it cannot defend. In the ARTEMIS mission, a crew may push through a hardware anomaly carrying a 14 percent failure probability, a deliberate echo of the Challenger disaster. Even if the lucky 86 percent draw lands, the rubric still penalizes the team for violating the safety constraint. A sound process behind a failed launch beats a reckless win every time, and the grade says so.

Tap to read the grading rubric

Let the workbook hold the busywork so the energy goes to the judgment.

The student workbook is an Excel tool built for the missions. It handles telemetry integration, multi-phase delta-v bookkeeping, sensitivity analysis, and the post-mission report, so teams are not buried in arithmetic when the clock is running. During the 20-minute calculation block, the Lead Analyst owns the model, the Mission Engineer turns it into propellant loads and timing, and the Mission Communicator builds the Reasoning Record that the rubric will grade. The numbers are real, drawn from the actual rocket equation and numerical integration with nothing fudged. The workbook does the grinding, which frees your students to argue about what the numbers mean and whether the margin holds.

Tap to see the tracker

Every day is already scripted. You bring the facilitation, the simulation brings the rest.

The teacher guide is fifteen daily playbooks, one for every session. Each one runs the 50-minute period minute by minute: a 5-minute briefing, a 20-minute calculation block, a 20-minute decision and lock block, then a 5-minute submission. The Reveal days, 3, 6, 9, and 12, swap the calculation work for naming the bias and the reflection that lands it. Every playbook carries coaching notes, canonical answer keys, and the legacy archetypes that help you spot a Tight-Margin Optimist or a Streak Reasoner mid-mission. Prep is light because the day is planned. You watch the teams, ask the hard question, and let the consequences do the teaching.

Tap to read the teacher guide

The lesson plan is already written.

Every simulation comes with a fully editable, admin-ready lesson plan. Standards alignment, daily pacing, learning objectives, differentiation, and an assessment plan are already done, so you can hand it to an administrator or adapt it to your district template in minutes.

Tap to preview the lesson plan

The moment the textbook number turns out to be fatal.

On Day 1, a STARFALL team runs the Tsiolkovsky equation for a low-orbit launch and gets a clean answer. The textbook says orbital velocity is 7,670 m/s, and their fuel budget closes. They are ready to commit. Then the release reminds them that real rockets fight gravity on the way up and push through atmosphere, and those losses are not optional. They add 1,350 m/s for gravity and 150 m/s for drag, and the required velocity jumps to 9,170 m/s. The budget that closed a minute ago no longer closes. Their rocket leaves a structure mass of only 235 kg for a 500 kg payload. The launch they were about to approve would fail.

At the pivot, the team has a choice. They can trust the clean textbook figure that made their plan work, or they can trust the budget that says the plan is broken. Protecting the number is comfortable and lets them submit on time. Trusting the evidence means admitting the design does not fly and starting the margin over. When they choose the evidence, they stop chasing points and start doing the work an engineer actually does. They see that precision was never the busywork. It was the line between a mission and a crater.

Four missions, one season, no fudged numbers.

Your students join a flight program as analysts and engineers, working in teams of two or three with rotating roles. Across a 12-day season they run four missions: STARFALL launches a satellite to low orbit, LIFELINE resupplies the space station, ARTEMIS carries a crew to the Moon, and HORIZON delivers cargo to Mars. Each mission is a 3-day arc built on high-fidelity physics, the real rocket equation, and live telemetry. Every Go or No-Go call is theirs, and every call is defended in writing.

Engineering better thinkers.

In a launch program, discernment is survival. Every day pairs a named cognitive bias with the capacity that defeats it, and the bias is never named in advance. Your students fall into the trap, feel the consequence, and only then learn what caught them.

15 days of mission-critical calculus.

The three pre-simulation days build the toolkit: the rocket equation, the math tracks, and the bias definitions students research without yet knowing which mission hides which trap. Then the season runs four 3-day arcs of rising stakes, each ending in a Reveal that names the bias the team just lived through.

Standards alignment.

The Ascent maps to AP Calculus and the CCSS Mathematical Practices without content swapping. STARFALL works Units 2 and 4, deriving the rocket equation and treating acceleration as a function of time. LIFELINE covers Units 6 and 8 through multi-phase integration. ARTEMIS hits Unit 5 with constrained optimization and abort margins. HORIZON reaches Unit 8 and BC topics with numerical ODE integration using Euler and RK4. All eight Mathematical Practices are exercised, with MP1, MP3, MP4, and MP6 central: students persevere through delta-v budgeting, construct arguments in their reports, model every mission, and attend to precision in STARFALL's tight structure margins.

Turnkey, classroom-ready.