Lesson 2 of 4 · Follow overlapping propulsion phases
Follow overlapping propulsion phases
6 minute lesson · 3 checks along the way
Your goal for this lessonExplain the booster, core and upper-stage sequence and use a simple force balance correctly.
In this lesson 3 sections · 3 checks
Read & understand
Parallel hardware can have different start times
LVM3 uses two S200 solid boosters, an L110 liquid core with two Vikas engines, and a C25 cryogenic upper stage powered by CE20. The boosters begin the ascent; the liquid core ignites while the boosters are still operating. The upper stage works later. Being physically attached at liftoff does not require every engine to ignite simultaneously.
The sequence is a design choice that must be supported by propulsion, guidance and structural analysis. Ignition, shutdown and separation alter the forces and mass distribution. A mission-specific timeline is more useful than a generic statement that “stage one finishes, then everything else starts.”
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Read a documented overlap
ISRO’s 2014 experiment account reports L110 ignition 120 seconds after liftoff and booster separation at 153.5 seconds. That gives 33.5 seconds between those two events. It does not mean the boosters supplied constant thrust throughout that interval, and it is not a timing specification for every later LVM3 flight.
A controller must work through transitions rather than treat each phase as isolated. When propulsion elements overlap, their combined forces and the attached structure matter. When hardware separates, the remaining vehicle has different mass and aerodynamic properties. The event order and the configuration belong beside the numerical values.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Separate upward thrust from net force
For an original vertical-force example, ignore drag and suppose a vehicle has 6 meganewtons of upward thrust and 5 meganewtons of downward weight. The net upward force is 1 meganewton, and the thrust-to-weight ratio is 1.2. Neither number is a reported LVM3 measurement. Net force and the vehicle’s mass together determine acceleration.
If the example’s upward thrust drops to 4.5 meganewtons while weight stays at 5, net force becomes 0.5 meganewton downward. An already ascending vehicle need not instantly move downward: its upward velocity can decrease first. Distinguishing force, acceleration and existing velocity helps explain why a flight timeline needs more than a list of thrust values.
Force is not the same as existing motion
Original teaching diagram. Invented vertical-force examples; not measured LVM3 flight values.
Open full-size diagram in a new tab: Force is not the same as existing motionCheck 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.