Loss of Trajectory - Mercer Terminated

Mercer stood at the back of the control room, hands loosely clasped, watching the mission unfold exactly as it had on paper. The room was dim except for the glow of the forward displays. Telemetry streamed in clean columns across multiple screens. Velocity vectors, altitude, pitch, roll, yaw. Engine chamber pressure holding steady. The guidance solution remained stable, with no oscillation in the control loop.

“Max Q passed,” one of the flight controllers said.

“Copy, Max Q,” came the response from another console.

The ascent profile tracked perfectly along the predicted curve. The rocket rose through the atmosphere and into the thinning dark, its path plotted in a clean arc across the main screen. There was no deviation, no jitter in the signal. Mercer allowed himself a small breath. This was what success looked like. Controlled. Predictable. Quiet.

“MECO confirmed.”

Main Engine Cutoff. A brief pause followed, and then separation events began to populate the telemetry stream.

“Stage separation nominal.”

“Second stage ignition confirmed.”

The room remained steady and professional. No applause yet. Not until orbit was confirmed. Mercer stepped slightly closer to the primary display. The trajectory line extended outward, approaching the expected insertion window as the numbers tightened around the planned orbital parameters. Altitude was approaching target, and velocity was nearing orbital threshold.

“Guidance, confirm insertion solution,” the flight director said.

There was a pause, longer than expected.

“Guidance… we’re not seeing convergence.”

Mercer’s eyes narrowed slightly.

“Clarify,” the flight director said.

“Vehicle velocity is exceeding predicted insertion envelope,” the guidance officer replied. “We’re not seeing the expected delta-v taper.”

On the main screen, the trajectory line did not begin to curve. It continued straight.

“Flight, we’ve passed nominal cutoff conditions,” propulsion said. “Second stage is still producing thrust.”

“That’s not possible,” someone muttered.

“Command shutdown?” another voice asked.

“No command issued,” guidance replied. “Vehicle is not responding to insertion profile.”

Mercer leaned forward now, watching the numbers as velocity continued to climb past the planned orbital velocity. Seventeen thousand five hundred miles per hour. Eighteen thousand. The expected circularization point came and went without transition.

“Guidance, where is our burn termination?”

“We don’t have one,” came the answer. “Flight computer is not executing the insertion sequence.”

“Switch to manual override.”

“Negative response,” guidance said. “Command path is not being accepted.”

A quiet tension settled across the room as the data continued to stream in clean, uninterrupted lines.

“Flight, trajectory is now hyperbolic,” guidance said after a moment. “We are no longer in an orbital solution.”

The line on the screen no longer resembled an arc around Earth. It extended outward into open space.

“Are we in a failure mode?” the flight director asked.

“No system fault flags,” propulsion said. “Engines are operating within normal parameters.”

“Then why isn’t it stopping?”

No one answered immediately.

“Telemetry shows continued forward acceleration,” guidance said. “Vehicle is maintaining thrust beyond programmed limits.”

“Flight… we’ve crossed escape velocity.”

The room went still. Mercer stared at the screen, studying the data. It was clean, almost unnervingly so. There was no corruption, no noise, no anomaly that could be dismissed as instrumentation error. The rocket had not failed. It had simply refused to follow its path.

“It’s not coming back,” someone said quietly.

No one corrected him.

Mercer stepped back, his attention still fixed on the display, then turned and left the room without drawing notice.

***

The next morning, the control room felt different. Brighter, colder, stripped of momentum. The screens now displayed static reports instead of live telemetry—charts, reconstructions, and simulations attempting to impose logic on what had happened. Mercer took a seat at the briefing table. NASA leadership filled the room alongside flight directors, systems engineers, and external oversight representatives. The tone was controlled, but urgency pressed just beneath the surface.

“Let’s begin,” one of the panel members said.

“Initial assessment,” Mercer began, his voice steady. “The vehicle performed nominally through ascent and stage separation. There were no mechanical failures, no propulsion anomalies, and no structural deviations.”

“Then explain the trajectory,” another member said.

Mercer did not hesitate. “The guidance model was compromised. We are reviewing all upstream inputs that informed the insertion profile.”

“Compromised how?”

“Faulty data,” Mercer said. “Specifically within the predictive alignment models.”

A pause followed.

“Source?”

Mercer met their eyes directly. “Dr. Christina Whiting. She provided the final adjustment set used in trajectory calculations.”

Glances moved across the table.

“You’re saying the data was wrong.”

“I’m saying the inputs did not produce a valid orbital solution,” Mercer replied.

“Did you verify the data before approval?”

“It passed all standard validation protocols,” Mercer said. “There was no indication of instability at the time.”

“Did Dr. Whiting raise any concerns?”

Mercer held their gaze. “Not in a way that would have prevented launch.”

‍ ‍The statement settled heavily into the room.

“Then this is a data integrity failure,” one of the panel members said.

“Yes,” Mercer said.

A man at the far end of the table leaned forward, his hands flat against the surface. “This is a four hundred and ninety million dollar failure,” he said, his voice controlled but tight. “Some of the nation’s most sensitive satellite equipment is now gone. Not damaged. Not recoverable. Gone.” He paused, letting that settle. “And you’re telling us this happened because of bad numbers?”

The room held still. Mercer did not respond.

The panel chairman watched him for a moment longer. “Do you have anything to add?”

Mercer kept his posture steady. “No.”

The silence lingered a second longer before the lead investigator spoke again.

The investigation moved forward from there.

***

Two days later, the panel reconvened in a smaller room. The space felt tighter, more deliberate, and the tone had shifted. A folder sat in front of each member. Mercer noticed it immediately.

“We’ve received additional material,” the lead investigator said.

Mercer remained still.

“A confidential source provided documentation from a meeting between you and Dr. Whiting.”

The room remained quiet.

“Please review page three.”

Mercer opened the folder and recognized the content of the notes instantly. The notes were from the discussion they had when he stood in her doorway. The bullet points were precise, structured the way she always organized uncertainty.

He read the line: Current alignment data does not converge to a stable orbital solution. Predictive model diverges under forward propagation. Recommend delay until variance is resolved.

He turned the page: Confidence level insufficient for launch authorization.

Mercer closed the folder.

“Did you receive this assessment prior to launch?” the investigator asked.

“Yes,” Mercer said.

“Did you understand its implications?”

“Yes.”

“Why did you proceed?”

Mercer paused before answering. “The model had been stable in prior runs. There was no evidence of systemic failure.”

“That is not what these notes indicate.”

“They indicate uncertainty,” Mercer said.

“They indicate a direct recommendation not to launch.”

Silence filled the room.

“You testified two days ago that Dr. Whiting did not raise concerns that would have prevented launch,” the investigator continued.

Mercer held his posture. “I interpreted her assessment within the context of overall system performance.”

“That is not what you told this panel.”

No one moved.

“You shifted responsibility to her,” the investigator said. “Despite documented evidence that she warned you explicitly.”

Mercer did not respond. The decision came quickly after that. They did not make him wait.

“Mr. Mercer,” the lead investigator said, “based on the findings of this panel, your authorization of the launch in the presence of known data instability constitutes a breach of duty. Effective immediately, your position is terminated.”

The words were measured and final. Mercer nodded once. There was no argument and no protest. Two security personnel were already at the door. He stood, smoothing the front of his jacket out of habit more than necessity, then walked toward the exit as the room remained silent behind him. No one met his eyes. The hallway outside was quiet, lit by steady fluorescent lights reflecting off clean floors. It was the same building he had walked through for years, now reduced to a path out.

“Sir, we’ll escort you,” one of the guards said.

Mercer gave a slight nod, and they walked together in silence. People looked up as he passed, conversations stopping mid-sentence before attention returned quickly to screens and papers. No one spoke to him. Florinda Santos was there to collect his NASA issued phone. At the end of the corridor, Mercer removed his badge and handed it over. The guard placed it in a small plastic tray.

“That’s everything?” the guard asked.

“Just the personal contents in my office,” Mercer said.

“They will be boxed and shipped to your address on file,” the guard responded.

The doors opened automatically. Outside, the air felt wider, uncontained, different from the controlled environment he had just left. Mercer paused for a moment, then stepped forward. Behind him, Goddard’s doors closed forever.