Launch Services

Mission Goal

Build a triple-bottle integrated rocket and run a structured test campaign: define a target (stability, straightness, repeatability), execute launches, and optimise safely.

Why it matters

At higher levels, launch services become about coordination and optimisation: pre-flight reviews, quality control, stable configuration management, and learning loops. This level is about running a programme, not just building a rocket.

Inputs from other teams

• Command & Control: risk register + go/no-go process.
• Structures: reinforcement strategies and safe build standards.
• Payload: optional payload constraints (mass placement affects stability).
• Comms: launch operations script for a larger crowd and more moving parts.
• Recovery: expanded range plan + retrieval roles.

Constraints

• Water rockets only.
• Only staff-approved pressure limits; teacher-controlled pressurisation and release.
• No hard projectiles; no metal/glass; no sharp edges.
• At most one pressurised bottle unless your school explicitly approves multi-chamber designs (default: one).
• Must use a documented inspection and launch procedure.

What you must produce (deliverables)

• Triple-bottle rocket + build sheet + version label (e.g., v1, v2).
• A test plan (what you’re measuring and why) and a log of launches.
• A pre-flight inspection checklist that includes “stop conditions”.
• A short optimisation report: what you changed between versions and what improved.

Build & test steps

1. Define your mission target: e.g., “3 stable launches in a row with minimal wobble.”
2. Design the structure: decide where bottles sit and how you maintain alignment.
3. Implement build standards: centre-lines marked, fin jig, checklist used.
4. Dry-run on pad: confirm seating and clean release with your larger airframe.
5. Test launch v1: log outcome; identify top 1–2 issues only (don’t change everything).
6. Modify to v2: one improvement at a time (e.g., fin stiffening or alignment).
7. Test v2: compare logs to v1; keep what works.
8. Lock configuration: choose your best version for “official launch day”.

Launch-day checklist

• Range expanded; safety perimeter clearly marked.
• Inspection completed and signed off (student + teacher).
• Roles assigned: Launch Director (teacher), Safety Marshal, Recorder, Spotters, Recovery Lead.
• Countdown script followed; “HOLD” call supported by everyone.
• Post-launch: confirm landing zone safe before retrieval.

Success criteria

• Triple-bottle rocket launches safely and remains intact.
• Team completes a test campaign with logged outcomes and clear iteration steps.
• Optimisation is evidence-based (you can point to the logs and explain the change).
• Launch operations run smoothly with defined roles and discipline.

Evidence checklist

• Photo set: v1 and v2 (or later) showing what changed.
• Launch video(s) showing countdown discipline and safe range control.
• Completed logs for each launch + a short comparison table (v1 vs v2).
• Inspection checklist with sign-off.

Safety rules

• Teacher-controlled pressure and release only.
• Eye protection near operations area; spectators behind the line.
• Stop if any interface peels, bottle deforms, or pad alignment shifts.
• No adding mass “because it looks cool.” Safety and stability first.
• Do not run “experimental” configurations on launch day — test first.

Common failure modes

• Too many changes at once → you can’t tell what helped.
• Alignment drift during build → unstable launches.
• Insufficient fin authority for the bigger airframe.
• Weak interfaces → separation or flapping surfaces.
• Launch roles unclear → unsafe crowd movement.

Stretch goals

• Create a “configuration control” sheet (what version, what parts, what settings).
• Build a simple fin alignment jig to improve repeatability.
• Run a mock Flight Readiness Review (FRR) with another team asking questions.