Lesson 3 of 4 · Rideshare is an integration problem
Rideshare is an integration problem
6 minute lesson · 3 checks along the way
Your goal for this lessonExplain how adapters, release order and compatible destinations turn multiple payloads into one launch mission.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Read & understand
Many satellites need a coordinated carrier
In September 2020, Vega flight VV16 deployed 53 satellites into two Sun-synchronous orbits using the Small Spacecraft Mission Service dispenser. ESA published a recording of the first releases. That is evidence of a specific deployment sequence; it does not show every later satellite operation or prove that all future rideshares will work the same way.
Rideshare is more than adding a list of spacecraft masses. A dispenser must hold the passengers through ascent and release them in a planned sequence. Designers consider physical interfaces, clearances and the delivery requirements. The upper stage and dispenser together turn a collection of payloads into a coordinated mission.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Budget the carrier as well as the passengers
Try an original mass allocation: four spacecraft each weigh 120 kg, eight each weigh 15 kg, and the carrier uses 100 kg. The total is 700 kg, not 600 kg. If the teaching allocation is 750 kg, only 50 kg remains. These invented quantities explain the arithmetic; they are not VV16 payload data.
The clean-room frame of FalconEye 1 shows spacecraft handling and an adapter during the separate VV15 campaign. It illustrates why interfaces and careful integration matter. It is not a photograph of the VV16 dispenser or evidence that FalconEye 1 reached orbit. Keep the visible preparation, the flight identity and the eventual outcome separate.
FalconEye 1 during the separate VV15 launch campaign: a frame at 170 seconds from Arianespace’s video. This is prelaunch integration, not VV16 rideshare hardware or proof of successful orbital delivery. Display image resized and compressed.
Look closely
Which part of the mission chain is visible here?
See what to notice
The frame shows physical handling and integration; separation and successful flight require evidence from later events.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Check more than total mass
Suppose the spacecraft in the example all fit by mass, but one needs a delivery plane outside the offered mission. That mismatch still prevents the proposed arrangement. Likewise, a payload arriving after integration closes can disrupt a technically compatible grouping. A useful readiness review checks destination, interfaces, testing and dates.
For a deployment exercise, write one row per passenger: intended release condition, command, confirmation and contingency. A command sent is not the same as a separation confirmed. This distinction helps explain why launch summaries should report delivery results carefully, even when every satellite began the journey aboard the same vehicle.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.