Spacecraft Data Budget

payload + housekeeping generation vs downlink capacity over ground contacts. daily data balance, storage saturation time, break-even rate / contacts. orbit-mean trade study. flight design needs a full link budget + contact-schedule simulation.

This satellite data budget calculator balances how fast a spacecraft generates data - the payload stream plus housekeeping telemetry - against how fast the ground segment can pull it down during station contacts (Space Mission Analysis and Design (SMAD), Ch. 13 communications architecture; Ch. 9 mission operations). It reports the daily data balance, the time to fill onboard storage when the link cannot keep up, and the two break-even figures - minimum downlink rate and minimum contacts per day - that close the budget. It is an orbit-mean trade study for sizing mass memory and sanity-checking a contact plan; flight design still needs a full link budget and a contact-schedule simulation.

Every Earth-observation or science satellite faces the same arithmetic. The payload generates data continuously - an imager, a radar, an RF survey receiver - while the spacecraft can only get that data to the ground during the few minutes per pass that a ground station is in view. A data budget (Space Mission Analysis and Design (SMAD), Ch. 13 - communications architecture; Ch. 9 - mission operations) checks whether the second number can keep up with the first, and sizes the onboard mass-memory that buffers the gap.

Data generation is the sum of two streams: the payload data rate (the science or imaging stream) and the housekeeping rate (bus telemetry - voltages, temperatures, attitude, fault counters). Generation runs around the clock, so data generated per day is simply (payload + housekeeping) × 86 400 s. For a 5 Mbit/s imager that is roughly 432 Gbit every day.

Downlink capacity is bounded by contact opportunities. A single ground station in low Earth orbit (LEO) sees a satellite for only a handful of passes per day, each lasting a few usable minutes. The day's downlinked data is contacts/day × usable-minutes × 60 × downlink-rate × efficiency. The efficiency factor (~0.75 nominal) discounts the channel time lost to pass acquisition, ranging, framing, and forward-error-correction overhead before useful payload bits flow. Contacts can be entered directly per day, or per orbit and scaled by the orbits-per-day the period implies.

The daily balance is generation minus downlink. A non-positive balance means the link keeps up - onboard storage never saturates. A positive balance means a backlog accumulates: onboard storage fills at the balance rate until it hits capacity, after which new data is lost or overwrites the buffer. The storage-vs-time chart plots exactly that fill curve against the capacity ceiling. Two break-even figures close the trade: the minimum downlink rate, and the minimum contacts per day, that each drive the balance to zero with the other inputs held fixed.

What this tool does not capture: per-pass elevation-angle and slant-range variation, weather outages, station scheduling conflicts, variable-rate adaptive coding, payload duty-cycling (most imagers do not run continuously), data compression, and the difference between a single station and a ground-station network. It is an orbit-mean trade study to size storage and sanity-check a contact plan early - flight design needs a full link budget and a contact-schedule simulation.