Mission Planning & Launch

Overview

You can build a perfect satellite and still fail if mission planning and operations are weak. This module connects engineering to real-world constraints: schedule, launch integration, licensing, and ground operations. Launch is not the finish line — operations is where you earn your mission success.

Concept of Operations (ConOps)

ConOps answers how the mission runs day to day. A well-written ConOps document is the bridge between your hardware design and actual mission execution. It should include:

Mission Phases

• Commissioning — The first days and weeks after deployment, focused on system checkout and verification.
• Nominal Operations — The primary mission phase where science and payload activities occur on a regular schedule.
• Extended Mission — Continued operations beyond the primary mission lifetime, often with degraded capabilities.
• End of Life / Deorbit — Passivation, data archiving, and controlled or natural deorbit.

Operating Modes

• Safe Mode — Minimum power, beacon only. The satellite’s fallback state when something goes wrong.
• Downlink Mode — Radio TX active, antenna pointed at ground station for data transfer.
• Payload Mode — Instrument active, collecting science or mission data.
• Idle / Charge Mode — Systems quiet, battery charging from solar panels.

Additional ConOps Elements

• Ground Station Plan & Staffing — Who operates, when, and how shifts are managed.
• Data Pipeline — How raw data becomes usable results, from downlink through processing to delivery.

Student-friendly advice: Keep your ConOps simple and repeatable. Plan what happens if you only get one pass per day for a week. If your operations plan can’t survive limited contact, simplify it.

Mission Phases Summary

Phase	Duration	Primary Activity
Launch & Deploy	Day 0	Separation from deployer, 30-min quiet period
Commissioning	Weeks 1–3	System checkout, first contact, verify power positive
Nominal Ops	Months 1–6	Science/payload operations, regular downlinks
Extended Mission	Months 6+	Degraded operations, opportunistic science
End of Life	Final weeks	Passivation, data archiving, deorbit

Launch Options & Deployers

Most student CubeSats fly as secondary payloads (rideshare). NASA’s CubeSat Launch Initiative (CSLI) provides free launches for US educational institutions — they’ve launched over 160 CubeSats. The Air Force’s University Nanosat Program (UNP) is another path.

Commercial rideshare options also exist (SpaceX Transporter missions, Rocket Lab, etc.) typically starting around $300K for a 3U slot.

Deployer Compatibility

Deployer compatibility requirements shape your structure design. Common deployers include:

• P-POD — Cal Poly’s Poly Picosatellite Orbital Deployer, the original CubeSat deployer standard.
• ISIPOD — ISIS deployer, widely used in European and international missions.
• NanoRacks — ISS deployment via the station’s airlock and robotic arm.
• Nanoracks CubeSat Deployer — Standardized deployer for ISS-based launches.

Integration reality: Late design changes are expensive and risky. Testing and documentation are part of the deliverable — not just the hardware.

Launch Path Comparison

Path	Cost	Orbit Control	Timeline
NASA CSLI	Free (if selected)	Limited choice	2–4 years from proposal
UNP (DoD)	Free (if selected)	Limited choice	2–3 years
Commercial Rideshare	$300K–$1M+	More options	1–2 years
ISS Deployment	Free via CSLI or paid	~400 km, 51.6°	Varies

Regulatory & Spectrum Basics

Transmitting from space requires compliance. Frequency coordination and licensing are serious topics. Many student missions use amateur radio frequencies (UHF 435–438 MHz) which require coordination through IARU. FCC licensing (or equivalent national authority) is required before launch.

Important note: This module provides awareness and planning habits, not legal advice. Teams should engage university compliance offices and qualified spectrum experts early.

Key Points

• Start Early — Begin the licensing process 12–18 months before your target launch date.
• Amateur Radio Community — Work with amateur radio clubs and advisors for frequency coordination and operational support.
• Documentation — Document your frequency plan clearly, including power levels, modulation, and bandwidth.

Ground Segment & Operations

Your ground segment is everything on the Earth side of the radio link. Without a capable ground segment, your satellite is just a blinking light in the sky.

Ground Segment Components

• Antenna System & Rotator — Yagi antennas for UHF, dish for S-band. Rotator tracks the satellite across the sky.
• Radio & Modem — Software-defined radios like USRP or RTL-SDR for receive.
• Tracking Software — GPredict, SatNOGS for pass prediction and antenna pointing.
• Scheduling & Pass Automation — Automated scripts to prepare for upcoming passes and reduce operator workload.
• Data Decoding & Storage — Pipeline to decode raw frames into usable telemetry and payload data.
• Command Approval Process — Defined workflow for who can send commands and under what conditions.

Operations Playbook

Create a “playbook” for common scenarios so your team can respond quickly and consistently:

• First Contact Procedure — Step-by-step guide for initial beacon acquisition.
• Unexpected Reboot Response — How to diagnose and recover from an unplanned reset.
• Low Power Condition — Shed non-essential loads and prioritize battery charging.
• No Comms for 48+ Hours — Escalation plan and alternative ground station options.
• Suspected Payload Fault — Isolate the payload and verify bus health before reactivating.

Commissioning After Deployment

Commissioning is the first days or weeks on orbit. This is when you verify that your satellite survived launch, is generating power, and can communicate. A disciplined, step-by-step approach is critical.

Typical Commissioning Steps

1. First Beacon Detection — Listen for the satellite’s beacon signal and confirm basic telemetry.
2. Verify Power Positive — Confirm the battery is charging and the EPS is healthy.
3. Verify Command Uplink — Can you talk TO the satellite? Send a simple command and confirm acknowledgment.
4. Verify Stored Data Downlink — Can you get data FROM it? Download stored telemetry logs.
5. Check ADCS Behavior — Verify detumble is working and the satellite is stabilizing.
6. Start Payload Operations Gradually — Activate instruments one at a time, not all at once.

End of Life & Responsible Mission Design

Even student missions should plan for responsible end-of-life operations. Space sustainability is not optional — it’s an engineering requirement.

End-of-Life Considerations

• Deorbit Timeline — NASA and FCC require deorbit within 5 years for LEO missions. Plan your orbital altitude accordingly.
• Fault-Safe Behavior — What happens if you lose contact permanently? The satellite should not become an uncontrolled hazard.
• Passivation — Deplete batteries, disconnect solar panels, and vent any stored pressure to prevent debris-generating events.
• Data Archiving & Mission Reporting — Preserve mission data, publish results, and submit final reports to sponsors.
• Lessons Learned — Document what worked, what didn’t, and what you’d do differently. This is invaluable for future teams.

Knowledge Check

Test your understanding of mission planning and launch operations.