Engineering & Technology · Aerospace Engineering: Flight & Space Systems

Orbits, spacecraft subsystems and mission integration

An orbiting spacecraft continues to fall while moving sideways fast enough to curve around its central body. Its path, orientation, illumination and opportunities to communicate create a connected mission problem.

Review dynamics and vibrations, fluids, electrical power and machines, control and automation, and the physics of forces, gravitation and thermodynamics. Define symbols and units before substitution; 1 Wh=3600 J and 1 rad=180/π degrees. No lesson provides a flight, launch, engine, test or maintenance procedure.

Back to the chapter

After reading, you can

Derive circular scaling and explain noncircular energy/momentum consequences, then close a supplied spacecraft energy/data schedule against its mission deadline.

An orbit is accelerated motion

For a small spacecraft around an ideal spherical central body, write gravitational acceleration magnitude as μ/r², whereμ is the central body’s gravitational parameter and r is distance from its centre. An ideal circular orbit needs centripetal acceleration v²/r. Equating them gives v=√(μ/r), with period T=2πr/v.

Radius differs from altitude above a surface. Circular and elliptical orbits have different speed histories; inclination and orientation set how the orbit lies in space. The two-body model omits drag, nonspherical gravity, other bodies, radiation pressure and manoeuvres. In practical mission work these perturbations and uncertainty can matter over time.

Changing the orbit changes the service

A higher circular orbit has a lower circular speed and longer period in this model. That does not mean a spacecraft can climb there by simply slowing down at its current position. A manoeuvre changes its velocity and subsequent trajectory; a transition between circular states needs an appropriate transfer and further mission analysis.

Altitude, inclination and timing affect observation opportunities, communication geometry and illumination. An orbit that passes over a target does not guarantee the instrument is pointed correctly, the scene is illuminated as needed or the data can reach Earth in time. Attitude control changes orientation; orbital control changes motion through space.

Supplied gravitational parameter mu=4.0e14 m³/s² gives v=sqrt(mu/r). At radius 7 million m, v=7.55929 km/s and period 5818.31 s. At 14 million m speed 5.34522 km/s and period 16456.67 s. Radius is not altitude; no other forces or real mission geometry included.

A different orbit changes energy and the schedule

Choose gravitational potential energy zero at infinite separation. For the ideal central force, specific orbital energy is ε=v²/2−μ/r, in J/kg, and angular momentum per mass is h=r v_t, where v_t is the transverse velocity component. No torque about the centre means h stays constant during unforced two-body motion. In an ellipse, the smaller pericentre radius therefore has greater transverse speed than the larger apocentre radius; at both apses the radial velocity is zero. This is the momentum explanation behind equal areas swept in equal times.

For a circle, inserting v²=μ/r gives ε=−μ/(2r). A larger circular radius has less-negative energy despite its smaller circular speed. Giving a small prograde impulse at the original radius raises speed and energy there and can make that location the pericentre of an ellipse, rather than instantly placing the craft in the larger circle. An additional circularisation change and the complete trajectory must be analysed for that service. Comparing two circular end states is different from describing the path between them.

Orbit-plane orientation changes which ground regions can be accessed; Earth/body rotation, sunlight and target or antenna pointing further constrain opportunities. Neither v=√(μ/r) nor an energy account computes an eclipse duration or a ground contact. The following planning case supplies those geometry intervals explicitly. It illustrates their resource consequences while preserving the earlier independently derived circular speed and period.

Subsystems share scarce resources

A spacecraft bus supplies structural support, power, thermal control, computing, communications and, where needed, attitude actuation and propulsion. Reaction wheels exchange angular momentum internally; external torques or thrusters can be needed to manage accumulated wheel momentum. Sensors and onboard software connect estimates to those actuators.

Solar-array output depends on illumination and orientation. Batteries bridge intervals without generation, with separate energy, power and thermal constraints. Instruments generate data that may need storage until an available ground link can transmit it. Antenna pointing, contact duration, net data rate and power compete with observation duties; a component-by-component inventory does not establish an end-to-end mission.

One timeline joins energy, observation and delivery

Use an original 97 min planning cycle, rounded from the example’s 96.972 min period. Geometry analysis is assumed to supply sunlight from minute 0 to 60, eclipse from 60 to 97 and one contact at 80–85. These intervals are inputs, not derived orbital predictions. The bus load is always 80 W; generation is 150 W in sunlight and zero in eclipse. An instrument adds 40 W during minutes 10–20; a link adds 20 W during all five contact minutes. Charging and discharge delivery efficiencies are each 0.90 at their declared boundaries.

Start with 60 Wh inside the allowed storage window, which spans 40–120 Wh. In sunlight, stored gain is 0.90×(generation−load)×duration in hours. The first 10 min adds 10.5 Wh; instrument operation then adds 4.5 Wh; the remaining 40 min adds 42 Wh, reaching 117 Wh. During eclipse, withdrawal is delivered load energy divided by 0.90. The 37 min base load withdraws 54.815 Wh and the five-minute link adds 1.852 Wh, ending at 60.333 Wh. The model stays within its window and nearly restores the initial state; that small margin merits sensitivity checks.

The instrument produces 2 Mbit/s for 600 s, creating 1200 Mbit by minute 20. Supplied storage capacity is 1300 Mbit. A useful link rate of 5 Mbit/s can send 1500 Mbit during the contact, and sends this dataset in 240 s, finishing at minute 84. If the mission requires delivery within 30 min of the final exposure, its deadline is minute 50: energy and buffer capacity fit while timing fails. Counting an entire orbit’s bits and watt-hours would hide this conflict.

If separate geometry/pointing evidence permits moving the contact to minutes 40–45, delivery finishes at minute 44 and meets the deadline. The 20 W link then reduces stored charging by 0.90×20×5/60=1.5 Wh instead of withdrawing 1.852 Wh during eclipse. Final stored energy becomes about 60.685 Wh. This is a conditional resource improvement, not evidence that the earlier contact exists or that the antenna and instrument can point as requested.

Constructed late-contact schedule: stored energy and retained dataset on the same clock
Minute	Stored energy, Wh	Buffered useful data, Mbit	Event
0	60.000	0	Sunlight begins
10	70.500	0	Instrument starts
20	75.000	1200	Instrument stops
60	117.000	1200	Eclipse begins
80	87.370	1200	Late contact begins
84	79.963	0	Dataset delivery completes; contact still powered
85	78.111	0	Contact ends
97	60.333	0	Planning cycle ends

At minutes 0, 10, 20, 60, 80, 84, 85 and 97, stored energy is 60, 70.5, 75, 117, 87.370, 79.963, 78.111 and 60.333 Wh. Buffer grows from 0 at minute 10 to 1200 Mbit at minute 20, stays full until minute 80, and empties at minute 84 at 5 Mbit/s. It fits the 1300 Mbit capacity but misses the minute 50 deadline. Sunlight/contact intervals are supplied; the 40–120 Wh upper axis is deliberately restricted to the allowed storage window.

Check an ideal orbit and a separate resource interval

For a constructed central body supply μ=4.0×10¹⁴ m³/s² and r=7.0×10⁶ m. The circular speed is 7559.29 m/s and period 5818.31 s, about 96.972 min. Doubling radius reduces speed by√2 and multiplies period by 2√2. No real planetary radius or actual orbit is specified.

For a separate 90 min resource cycle, supply 150 W generation for 60 min and none for 30, with constant 80 W load. Eclipse needs 40 Wh delivered; at .90 storage-to-load efficiency this withdraws 44.444 Wh from storage. Sunlight surplus is 70 Wh, of which .90 charging efficiency stores 63 Wh. The cycle adds 18.556 Wh if there is enough free storage and no other loads. A payload producing 600 Mbit cannot count on a 2 Mbit/s 300 s link having spare capacity: the nominal 600 Mbit leaves no allowance for protocol overhead, outages or additional data.

The original 90 min resource cycle above is a separate arithmetic example; it is not the illumination geometry of the 96.972 min circular case. The shared 97 min schedule supplies a more complete mission thread and explicitly includes its instrument/contact loads. Its near-zero energy margin is not a general spacecraft property. A positive unconstrained cycle balance can also be lost to storage saturation: starting this late-contact schedule at 100 Wh would reach its 120 Wh ceiling, discard 37 Wh of potential charging, and end at only 63.333 Wh, well below the initial state.

Try the reasoning

Is an orbiting vehicle unaccelerated because it feels weightless?
Show the answer and reasoning
No. Gravity curves the free-fall trajectory even without a supporting surface force.
Does orbit radius equal altitude?
Show the answer and reasoning
No. Altitude subtracts the central body’s relevant surface radius.
Why can enough nominal downlink bits still fail a data requirement?
Show the answer and reasoning
Timing, overhead, outages, storage and pointing constraints can reduce actual useful delivery.
Change the circular radius by a factor 1.44 at the same μ. Find the speed and period ratios, then assess whether the old eclipse/contact times follow automatically.
Show the answer and reasoning
The speed ratio is 1/√1.44=1/1.2≈0.8333; the period ratio is 1.44^(3/2)=1.728. The old times do not follow. Illumination, ground access, body rotation, pointing and orientation must be recalculated or supplied; circular scaling alone does not preserve the mission schedule.
Keep the late contact at 80–85, but demand delivery of 1200 Mbit by minute 50. Could raising the contact useful rate from 5 to 10 Mbit/s solve the requirement?
Show the answer and reasoning
No. Transfer would finish at minute 82 instead of 84, but the contact starts 30 min after the deadline. An earlier usable opportunity or an accepted change to the mission outcome is needed; extra rate during a late opportunity cannot send data backward in time.
Starting from 60 Wh, extend the supplied eclipse by 5 min after minute 97 with no other change. Does one extended cycle violate the 40 Wh floor, and is repeated state restoration established?
Show the answer and reasoning
The extra base-load withdrawal is 80×(5/60)/0.90≈7.407 Wh, so final energy is 60.333−7.407≈52.926 Wh. That remains above 40 Wh for this one case but is about 7.074 Wh below the initial state. Repeating such cycles without changed charging eventually depletes storage; a one-cycle floor check is different from sustained balance.

What to carry forward

Use orbital mechanics together with orientation, energy, data and ground-system constraints.

References

Teaching resources and research supporting this lesson’s explanations and examples.