Exercise set

Spacecraft Communications and Data Return Exercises

Solved spacecraft communications exercises for path loss, EIRP, link margin, contact volume, recorder storage, Doppler, latency and release gates.

Branch: Aerospace Engineering
Content: Exercise set
Updated: Jul 03, 2026
Revision: v1.1.0 · reviewed

These exercises focus on spacecraft communications and data return. They connect RF link budgets, EIRP, path loss, pointing loss, contact duration, protocol overhead, recorder storage, missed contacts, Doppler, command latency and release evidence.

Use the calculations as screening checks. Flight release still needs antenna patterns, ground-station masks, modulation and coding thresholds, weather rules, operations procedures, onboard software verification and ADCS pointing evidence tied to the same contact timeline.

How to use these exercises

Work the set as a release rehearsal, not as isolated radio arithmetic. Exercises 1 to 5 establish the RF closure chain from range and EIRP to margin and pointing allocation. Exercises 6 to 10 turn the closed link into a data-return plan with overhead, passes, recorder storage and compression. Exercises 11 to 16 test acquisition, latency, uplink commandability and safe-mode robustness. Exercises 17 and 18 then force the engineering decision: whether the communications mode is defensible when operations availability and missing evidence are included.

For each answer, record the assumed orbit geometry, ground station, antenna mode, data rate and spacecraft attitude. A number without those assumptions is not reusable release evidence.

Release Evidence Notes

Communications release evidence should name the mission mode, spacecraft attitude, antenna selection, range, ground station, elevation mask, data rate, coding mode, required link margin, recorder allocation, contact schedule, command path and contingency mode. A link budget that closes for one geometry is not proof that daily data return closes.

The evidence package should also connect the RF budget to the operations timeline. The same pass plan should define acquisition time, pointing availability, useful downlink duration, recorder state before contact, expected product volume, command windows, weather rules and the missed-contact recovery case. If separate teams own RF, flight software, ADCS, payload operations and ground systems, the release package must show that their assumptions match.

Engineering Boundary Notes

The exercises use first-order dB link budgets and data-volume arithmetic. They do not replace full RF analysis, antenna pattern testing, licensing review, ground network simulation, Doppler acquisition validation, protocol testing or operations rehearsal.

Treat every result as a screening value. Real missions need measured antenna patterns, polarization conventions, implementation losses, modulation and coding curves, receiver acquisition behavior, spacecraft attitude limits, thermal and power constraints during contact, regulatory frequency coordination and ground-station configuration control. The calculations are still useful because they reveal whether a release decision is limited by RF margin, contact time, recorder storage, Doppler handling, uplink commandability or missing evidence.

Common Release Mistakes

forgetting cable, pointing, polarization or implementation loss;
counting entire pass duration as payload downlink time;
sizing recorder storage for a nominal day instead of missed-contact cases;
checking downlink but not uplink command margin;
ignoring Doppler and acquisition range for narrowband links;
releasing a data mode without proving ADCS pointing availability;
mixing best-case range, best-case weather and best-case station availability in one optimistic budget;
accepting compression ratios before testing representative payload products;
treating safe-mode beacon closure as proof that nominal high-rate downlink is available;
closing the RF link while leaving command latency, recorder priority and operations procedures unresolved.

Scenario Map

The exercises move from RF power and path loss to link margin, contact data volume, recorder balance, Doppler, latency, command path and integrated release gates.

Exercise 1: Free-Space Path Loss

An X-band downlink operates at $f=8.2\ \text{GHz}$ over range $R=1200\ \text{km}$ . Use $L_{fs}=92.45+20\log_{10}(f_{GHz})+20\log_{10}(R_{km})$ .

Solution

L_{fs}=92.45+20\log_{10}(8.2)+20\log_{10}(1200)=172.3\ \text{dB}

Engineering Comment

Range and frequency dominate the RF budget. The range must match the actual pass geometry, not the best-case orbit altitude.

Plausibility Check

Space links commonly have path losses above 150 dB.

Exercise 2: Transmitter EIRP

Transmitter power is $8\ \text{W}$ , antenna gain is $12\ \text{dBi}$ and cable loss is $1.5\ \text{dB}$ . Compute EIRP in dBW.

Solution

P_{dBW}=10\log_{10}(8)=9.03\ \text{dBW}

EIRP=9.03+12-1.5=19.5\ \text{dBW}

Engineering Comment

EIRP is the power radiated in the intended direction after feed losses and antenna gain.

Plausibility Check

Eight watts is about 9 dBW; adding a 12 dBi antenna gives about 21 dBW before cable loss.

Exercise 3: Received Carrier Power

EIRP is $19.5\ \text{dBW}$ , path loss is $172.3\ \text{dB}$ , ground antenna gain is $32\ \text{dBi}$ and miscellaneous losses are $3.2\ \text{dB}$ . Find received carrier power.

Solution

C=19.5-172.3+32-3.2=-124.0\ \text{dBW}

Engineering Comment

The received carrier is tiny, so receiver noise, coding gain and implementation loss must be reviewed carefully.

Plausibility Check

Subtracting a huge path loss from modest EIRP should produce a power near -120 dBW.

Exercise 4: Link Margin

Required received power for the selected mode is $-129.5\ \text{dBW}$ . Received carrier power is $-124.0\ \text{dBW}$ . Compute link margin.

Solution

M=-124.0-(-129.5)=5.5\ \text{dB}

Engineering Comment

The margin should cover pointing, weather, implementation, aging and uncertainty allocations.

Plausibility Check

The received power is less negative than the threshold, so margin is positive.

Exercise 5: Pointing-Loss Allocation

A link has 5.5 dB margin before pointing loss. Required final margin is 3.0 dB. What maximum pointing loss can be accepted?

Solution

L_\mathrm{point,max}=5.5-3.0=2.5\ \text{dB}

Engineering Comment

This creates an ADCS requirement. RF margin and pointing performance must be released together.

Plausibility Check

Allowing 2.5 dB of pointing loss leaves exactly the required 3 dB final margin.

Exercise 6: Contact Data Volume

Payload data rate is $2.4\ \text{Mbit/s}$ and useful downlink time is 420 s. Estimate payload volume in Mbit.

Solution

V=2.4(420)=1008\ \text{Mbit}

Engineering Comment

Useful downlink time should exclude acquisition, mode transition, margin checks and protocol overhead.

Plausibility Check

A few megabits per second for several minutes gives about one gigabit.

Exercise 7: Protocol Overhead

The raw contact volume is 1008 Mbit and protocol efficiency is 82 percent. Estimate delivered user data.

Solution

V_\mathrm{user}=1008(0.82)=827\ \text{Mbit}

Engineering Comment

Headers, coding, retransmission and operations gaps can make raw bit rate misleading.

Plausibility Check

Eighty-two percent of about 1000 Mbit is about 820 Mbit.

Exercise 8: Daily Data Balance

The spacecraft generates 2.6 Gbit per day and downlinks 0.83 Gbit per pass. How many passes are required per day?

Solution

N=\left\lceil\dfrac{2.6}{0.83}\right\rceil=4

Engineering Comment

Rounding up matters because a fractional missing pass creates recorder growth.

Plausibility Check

Three passes provide only 2.49 Gbit, slightly below the daily generation.

Exercise 9: Recorder Fill after Missed Contacts

Recorder capacity is 18 Gbit, nominal stored data is 6 Gbit and daily generation is 2.6 Gbit. How many full missed days can be stored before exceeding capacity?

Solution

Available capacity is

18-6=12\ \text{Gbit}

Missed days:

N=\left\lfloor\dfrac{12}{2.6}\right\rfloor=4

Engineering Comment

Recorder release should define what data are overwritten, compressed or prioritized when the missed-contact case exceeds storage.

Plausibility Check

Four missed days require 10.4 Gbit, while five require 13.0 Gbit.

Exercise 10: Compression Ratio Requirement

Daily raw data are 4.8 Gbit. Available downlink capacity is 3.0 Gbit/day. What compression ratio is required?

Solution

CR=\dfrac{4.8}{3.0}=1.6

Engineering Comment

Compression must be validated for real scenes or payload products, not only ideal data.

Plausibility Check

The downlink is about five-eighths of raw data, so a 1.6:1 ratio closes the budget.

Exercise 11: Doppler Shift

A spacecraft has radial velocity $7.2\ \text{km/s}$ at carrier frequency $8.2\ \text{GHz}$ . Estimate Doppler shift using $\Delta f=(v/c)f$ and $c=3.0\times10^8\ \text{m/s}$ .

Solution

\Delta f=\dfrac{7200}{3.0\times10^8}(8.2\times10^9)=197\ \text{kHz}

Engineering Comment

Receiver acquisition range and frequency plan must cover Doppler plus oscillator error.

Plausibility Check

LEO X-band Doppler shifts of hundreds of kilohertz are plausible.

Exercise 12: One-Way Light-Time

Range is $1200\ \text{km}$ . Estimate one-way propagation delay.

Solution

t=\dfrac{1.2\times10^6}{3.0\times10^8}=0.0040\ \text{s}

The one-way delay is 4.0 ms.

Engineering Comment

Propagation delay is small for LEO but still part of command timing and ranging records.

Plausibility Check

Light travels about 300 km per millisecond, so 1200 km gives about 4 ms.

Exercise 13: Command Path Latency

One-way propagation is 4 ms, ground processing is 120 ms, uplink framing is 80 ms and onboard command validation is 60 ms. Estimate total command latency.

Solution

t_\mathrm{cmd}=4+120+80+60=264\ \text{ms}

Engineering Comment

Command latency matters for time-critical mode changes, safing and close-loop operations.

Plausibility Check

Ground and software delays dominate over LEO propagation.

Exercise 14: Uplink Command Margin

Required uplink $E_b/N_0$ is 6 dB. The computed value is 10.8 dB and implementation loss is 1.4 dB. What is final margin?

Solution

M=10.8-1.4-6.0=3.4\ \text{dB}

Engineering Comment

Uplink margin protects commandability. It should not be sacrificed entirely to downlink optimization.

Plausibility Check

The raw value is 4.8 dB above threshold, and losses leave 3.4 dB.

Exercise 15: Ground-Station Mask Loss

A pass lasts 620 s above horizon, but the station mask removes 90 s at low elevation and 70 s during handover. What useful contact time remains?

Solution

t_\mathrm{useful}=620-90-70=460\ \text{s}

Engineering Comment

Pass duration should not be confused with usable downlink duration.

Plausibility Check

Removing 160 s from a 620 s pass leaves 460 s.

Exercise 16: Beacon Safe-Mode Margin

Safe-mode beacon EIRP is 6 dB lower than nominal, but data rate is reduced enough to improve receiver threshold by 12 dB. If nominal final margin is 3 dB, estimate safe-mode margin.

Solution

M_\mathrm{safe}=3-6+12=9\ \text{dB}

Engineering Comment

Safe-mode links trade rate for robustness. The mode must still be reachable with safe-mode attitude and power.

Plausibility Check

Lower rate gives more benefit than the EIRP loss, so margin increases.

Exercise 17: Downlink Availability from Pass Success

Each planned pass has 0.92 probability of usable downlink. Four independent passes are scheduled. What is the probability at least three passes succeed?

Solution

P={4 \choose 3}(0.92)^3(0.08)+(0.92)^4=0.959

Engineering Comment

Daily data return should include weather, station conflicts, spacecraft mode and operations availability, not just link margin.

Plausibility Check

With high individual pass success, at least three out of four should be very likely.

Exercise 18: Communications Release Gate

A communications release package has 17 required items. Fifteen are complete, but Doppler acquisition test and missed-contact recorder case are missing. Should the data-return mode be released?

Solution

\mathrm{completion}=\dfrac{15}{17}=0.882

The package is 88.2 percent complete, but release should fail because the missing items affect acquisition and data continuity.

Engineering Comment

Communications release requires both RF closure and operations closure.

Plausibility Check

Two missing mission-critical items out of seventeen are not acceptable evidence gaps.

Validation Package Checklist

Before accepting a spacecraft communications or data-return mode, collect:

RF link budget with EIRP, path loss, antenna gains, losses and required margin;
ground-station pass plan, elevation mask, weather and useful contact time;
modulation, coding, receiver threshold, Doppler and acquisition evidence;
recorder capacity, compression, missed-contact and data-priority cases;
uplink command margin, latency and safe-mode beacon evidence;
release decision tied to the same attitude mode and operations timeline.

The final review should answer four practical questions. First, can the spacecraft be commanded when the downlink mode is unavailable? Second, can the mission recover science or engineering data after the worst credible contact outage? Third, do the RF, ADCS, power, thermal and operations teams use the same timeline? Fourth, are the remaining evidence gaps non-critical, explicitly waived and owned by a release authority? If any answer is unclear, the mode is not ready for flight release even when the spreadsheet margin is positive.

REF