Mission Goal

Build a reliable, school-safe water-rocket launch pad that can hold a bottle rocket, pressurise it (safely), and release it cleanly on command — with a clear, repeatable process.

Why it matters

Real launch services live or die by ground systems: stability, countdown discipline, safety zones, and repeatability. A great rocket on a bad pad is still a failed mission.

Inputs from other teams

Constraints

What you must produce (deliverables)

Scaffolding Example (optional)

You are allowed to reuse structures and formats from other teams — but not their decisions.

Example: Launch Pad v0.9 (simple + repeatable)

Example: Launch roles (minimum viable ops)

  1. Launch Director (teacher): controls pressure + release.
  2. Safety Marshal: checks the line, calls “HOLD” if anyone crosses.
  3. Recorder: writes pressure/water fill and outcome in the launch log.
  4. Spotter: tracks flight and calls “ROCKET DOWN” + location.

Example: 30-second countdown script

Build & test steps

  1. Choose a pad concept: stable base + bottle retention + clean release + guide/rail.
  2. Prototype the latch (no pressure): can it hold/release the bottle smoothly?
  3. Add a guide (tube/rail) so rockets don’t tip at release.
  4. Add a hose connection to a pump (teacher-managed). Ensure it doesn’t kink.
  5. Dry-run countdown: roles, callouts, everyone knows where to stand.
  6. Low-pressure test (teacher): confirm no slipping, no wobble, no unsafe angles.
  7. Repeat 3 releases in a row without failures (no rocket required for the first few tests).

Launch-day checklist

Success criteria

Evidence checklist

Safety rules

Common failure modes

Stretch goals