Inside Mission Control: The First Ten Minutes After a Rocket Launches

A rocket leaves the pad at SRIHARIKOTA doing roughly 500 kilometres per hour. By the time it clears the tower, it is already accelerating past anything a commercial aircraft will ever reach. Inside ISRO's Master Control Facility or NASA's Christopher C. Kraft Jr. Mission Control Center in Houston, the noise outside is irrelevant. The room is already working.

The flight director calls "liftoff" not as a celebration but as a timestamp. Every console in the room locks to that reference. Flight controllers, each responsible for exactly one system, not two, begin reading telemetry that arrives with a lag of milliseconds. The vehicle is already hundreds of metres up before the first data packet completes its round trip. In those opening seconds, the propulsion officer watches chamber pressure and thrust vector. A deviation of a fraction of a degree in the engine gimbal, uncorrected, compounds into a trajectory error measured in hundreds of kilometres by the time the vehicle reaches orbit. The guidance officer is already comparing the actual flight path against the nominal trajectory stored before launch. If the two lines diverge past a threshold, the conversation happens in under a second.

Roughly sixty to ninety seconds after liftoff, depending on the vehicle, the rocket hits maximum dynamic pressure, the point at which the combination of speed and atmospheric density pushes the greatest mechanical stress onto the structure. For Chandrayaan-3's LVM3 launch from Sriharikota in July 2023, this moment came at approximately 73 seconds. The vehicle was travelling fast enough that the air it was pushing through behaved almost like a solid. Controllers watch structural loads, aerodynamic pressure readings, and the health of the payload fairing simultaneously. Nothing fails at max-Q by accident. If something is going to fail, it fails here. The throttle-down that happens just before max-Q on many vehicles, including ISRO's GSLV variants, is deliberate: reduce thrust slightly, reduce the stress the structure has to absorb, then throttle back up once the vehicle punches through the thickest resistance.

The first stage burns out and separates. For a few seconds, the vehicle is coasting on momentum, unpowered, in a partial vacuum. Telemetry shows the separation event as a pressure spike followed by a drop. Controllers confirm the event against the expected timestamp. If separation comes early or late by more than a defined margin, the flight director is already being briefed. The second stage ignition, confirmation that the engine has lit in the near-vacuum of the upper atmosphere, is the moment the room exhales, briefly. Mangalyaan's Mars Orbiter Mission in 2013 required a liquid-fuelled upper stage to ignite reliably after coasting through this dead zone. When it did, the ISRO control room in Bengaluru broke into applause. The flight director let it run for four seconds, then called the room back.

A mission control room looks like a theatre facing the wrong direction. The screens face the controllers, not the audience. Each flight controller owns a narrow vertical slice of the vehicle's health. The FIDO, Flight Dynamics Officer, tracks trajectory in real time and owns the decision on whether an abort trajectory is still viable. The GUIDO watches guidance software. The propulsion officer watches engine performance. The range safety officer, in the first ninety seconds, holds authority that supersedes the flight director: if the vehicle deviates from its safety corridor in a way that threatens populated areas, the range safety officer can command flight termination. This is not a theoretical power. It has been used. The communication between controllers follows a protocol that sounds terse to an outsider: call sign, system, reading, status. No sentences. No filler. The flight director speaks last on any loop, and only to decide.

Main Engine Cutoff, MECO, marks the end of powered ascent. The vehicle is now in its target orbit or on its transfer trajectory, coasting. For a low Earth orbit mission, MECO happens somewhere between eight and twelve minutes after liftoff. For Gaganyaan, ISRO's crewed mission currently in development, MECO will be the moment the crew transitions from launch abort options to orbital abort options, a fundamentally different set of contingencies. The room does not relax at MECO. It shifts. The ascent team hands authority to the orbital operations team. Checklists close. New ones open. The first ten minutes are over, but what they protected, the vehicle, the payload, the crew if there is one, now has to survive the next several days or months. Mission control made that possible by treating ten minutes as if each one were its own mission.