Satellite Services

Mission Goal

Build a simple payload that can be dropped safely from a small height and still protect its “core” (e.g., an egg, phone-sized dummy, or a fragile sensor module). Your goal is to achieve a repeatable “survives the drop” outcome with minimal parts.

Why it matters

Many space missions fail because of the boring bits: handling, deployment, vibration, shock, and landing loads. Recovery systems are “satellite services” on Earth—keeping payloads intact so the data mission can continue.

Inputs from other teams

• Payload/Data team: what must survive? (mass, dimensions, fragile parts)
• Structures team: safe materials, joints, basic reinforcement tips
• Avionics team: if using sensors, how to mount/log without damage
• Mission Control/Comms: how you will record test results and evidence

Design rules

• Capability over time: this is a Level 1 “proof & confidence” challenge.
• Single-session win: should produce a visible, rewarding success.
• Minimal dependencies: don’t wait on other teams to succeed.
• Evidence-first: record what happened, not just what you hoped would happen.

These rules reflect the shared Space.craft.ed challenge design principles. :contentReference[oaicite:1]{index=1}

Build steps

1. Define the core: pick an item to protect (egg, marshmallow tower, “sensor box”). Measure mass + size.
2. Choose a protection strategy: padding (foam/bubble wrap), crush zone (straws/cardboard), suspension (rubber bands), or a mix.
3. Create an outer shell: a box/cage that keeps the core from taking direct impact.
4. Add a “landing face”: one side designed to hit first (flat base, thicker padding).
5. Label your build: version number (v1, v2) and team name on the outside.

Test protocol

1. Safety setup: clear drop zone; one dropper; one spotter; no heads/feet under payload.
2. Drop heights: start at 0.5 m → 1.0 m → 1.5 m (only increase if it survives).
3. Three-trial rule: for each height, do 3 drops and record outcomes.
4. Record evidence: short video or 3 photos per height + a results log.
5. Post-test inspection: check shell deformation and core condition.

Success criteria

• Payload core survives 3/3 drops from 1.0 m with no functional damage (or no cracking if egg).
• Build is tidy, labeled, and can be reset quickly for repeat trials.
• Evidence includes height, trial count, and clear “pass/fail” definition.

Evidence checklist

• Photo of payload with label (team + version).
• Mass + dimensions of payload.
• Results table (height, trial 1–3, pass/fail, notes).
• Video clip or photo sequence of at least one drop.
• One paragraph: “What we changed between versions and why.”

Safety

• No drops above head height.
• Use a clear zone; keep observers behind a line.
• No glass, sharp metal, or heavy projectiles.
• If using electronics, ensure batteries are secured and not crushed.

Common failure modes

• Core contact: core touches the shell and takes direct impact.
• Bottoming out: padding compresses fully; impact transfers straight through.
• Uncontrolled tumble: weak geometry causes edge-first impacts.
• Overbuilt: too heavy; higher impact energy; fragile joints pop.

Stretch goals

• Add a simple accelerometer logger (even a phone inside with a free sensor app).
• Design for a target landing face and prove it lands that way most of the time.
• Create a quick “reset checklist” so anyone can repeat your tests reliably.