MissionLab Education

Let your students run a CubeSat mission.

Mission-based learning on one shared Digital Twin.

Students enter as guests, prepare a prediction, pass a local readiness check, operate a bounded spacecraft mission, inspect evidence, reflect, and keep a private local-practice record.

Digital Twin mission previewDemo
Orbit View

7.82 V

Locked

Run the software mission →

Institutional software

MissionLab is the recurring product: missions, teacher preparation, evidence and progression—not a one-off hardware purchase.

One Digital Twin

Education and university engineering use the same computational core with progressive disclosure, never a simplified physics fork.

Software-runnable missions

MissionLab missions can be completed in software. Supervised hardware can add measured evidence after separate correlation and acceptance.

Thirteen runnable software missions. One consistent journey. No student account or hardware required.

A learning journey teachers can repeat.

Every pilot mission follows seven stages: Mission, Preparation, Readiness, Operate, Evidence, Complete, and Recognition. The language and disclosure deepen from Grade 6 to university while the underlying Digital Twin does not fork.

What is included

13 Runnable Pilot Missions

Fourteen mapped experiments are available as software lessons. MLX-12 remains mapped but unavailable, and every mission awaits educator review.

Shared Digital Twin

School and university journeys use the same bounded models, adapters, and evidence endpoints at different academic depths.

Guest Mission Entry

Learners can run software missions without an account. Sign-in is reserved for institutional evidence workflows.

Teacher Delivery Guidance

Mission timing, prompts, misconceptions, evidence review, reflection, and truth boundaries follow the same seven stages.

Local Practice Records

Completion remains on the learner's device with zero measured channels and no identity, grade, public token, or verified-pass claim.

Optional Supervised Hardware

After valid software completion, a teacher and operator may add a bounded KidSAT extension. It is training evidence, not flight qualification.

What students learn

Frame a spacecraft mission objective and success criterion

Predict before operating a model

Distinguish simulated, derived, reference, and measured evidence

Compare bounded configurations and runs

Make an engineering decision from selected evidence

State a limitation and reflect on what should be tested next

Learning outcomes by area

Systems Thinking

Connect mission goals, spacecraft behaviour, constraints, and decisions.

Measurement & Data

Keep simulation truth, simulated sensors, estimator state, and measured telemetry distinct.

Physics & Mathematics

Use quantitative evidence appropriate to the selected academic depth.

Modelling & Control

Change bounded inputs and explain what caused the modeled response.

Verification & Validation

Judge whether evidence is trustworthy and sufficient for the claim being made.

Technical Communication

Make a decision, cite evidence, state a limitation, and reflect on the next test.

Software-first by design.

A school can begin with ordinary browsers and a teacher-guided mission. Accounts, paid hardware, and official competition attempts are not prerequisites for learning or completing local practice.

Why schools choose it

Clear teacher-led mission structure

Private learner work by default

Progression without a separate education physics fork

Truthful pilot and evidence status

Software-first Challenge pathway

University continuation on the same core

Designed for a real classroom session

The two recommended Grade 7 starting missions are MLX-15 and Orbit–Pass–Link. They are starting points, not the only runnable missions; teachers can choose from all thirteen based on supported level and learning goal.

Mission — role, objective, and success criterion

Preparation — diagnostic, theory, and prediction

Readiness — local formative confirmation

Operate — bounded configuration and run

Evidence — provenance, decision, limitation, assessment

Complete and Recognition — reflection and local record

Prepare once, then reuse the journey

Teachers brief the role and objective, guide preparation, confirm local readiness, facilitate the bounded run, review evidence and reflection, and explain the difference between local practice and verified recognition.

Start with a guest software mission.

Explore all thirteen pilot missions or open the teacher delivery guide.

MissionLab produces simulated and derived software evidence. Local readiness is not Challenge qualification, local completion is not a verified Mission Pass, and optional supervised hardware is not flight qualification.

Contact: info@cubestem.com