Mission Goal

Design and build a parachute recovery system that reliably deploys and reduces impact. Your system must be repeatable and measurable: it should work more than once, not just “one lucky drop.”

Why it matters

Parachutes are real mission-critical hardware in sounding rockets, balloon payloads, and drop tests. They turn violent landings into recoverable landings—protecting payloads and data.

Inputs from other teams

Design rules

Shared Space.craft.ed challenge principles apply. :contentReference[oaicite:3]{index=3}

Build steps

  1. Select canopy shape: circle, hexagon, or square (start simple).
  2. Choose canopy material: bin liner, thin fabric, ripstop scraps, lightweight plastic sheet.
  3. Cut and reinforce corners/edge: tape patches where lines attach to stop tearing.
  4. Add suspension lines: 4–8 lines; equal length; attach symmetrically.
  5. Build a simple pack/deploy method: fold canopy; loosely tuck; ensure it can open (avoid tight knots).
  6. Attach to payload: central bridle point (one ring/knot) attached to the payload’s strongest point.

Test protocol

  1. Baseline: drop without parachute (3 trials from 1.5 m) to compare.
  2. Deployment check: 5 trials from 2.0 m (or safe stairwell height) focusing on “opens cleanly.”
  3. Timing: use a phone stopwatch or video frames to estimate descent time from a known height.
  4. Tangle audit: record any partial opens, line tangles, canopy collapse, or oscillation.
  5. Iteration: change one variable at a time (canopy size OR line length OR number of lines).

Success criteria

Evidence checklist

Safety

Common failure modes

Stretch goals

Scaffolding Example (optional)

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

Template: “Operations plan”

  1. What runs daily/weekly?
  2. Who checks it?
  3. What counts as failure?
  4. What do we do next?

Example failure handling