Free serialized edition

Part 015 · Chapter 7: Gateway Black | 2 of 2

THE VANISHING OF PERSEUS · N. D. Jules

Mars Gateway’s first internal fault arrived at 06:02 UTC.

The orbital platform reported a synchro­niza­tion disagree­ment between its primary clock and the commu­ni­ca­tions processor. The difference was fourteen microsec­onds.

Small for a human life.

Large for a relay network.

The onboard system corrected it auto­mat­i­cally.

Tasha watched the clocks align.

Twenty-two seconds later, they separated again.

“Radiation event?” she asked.

Space-weather data showed no solar particle increase. Gateway’s own radiation monitor remained quiet.

“Processor fault,” someone said.

“Which processor?”

“Commu­ni­ca­tions.”

“The primary clock is stable?”

“So far.”

Gateway generated a diagnostic package and began sending it to Earth.

The first half arrived intact. The second half repeated the first.

Not similar data.

The same bytes.

A loop.

“Stop automatic ingestion,” Tasha said.

The archive system froze the stream before it could overwrite the valid section.

Gateway continued trans­mit­ting.

The repeated block contained receiver gain settings, surface relay queues and the first line of the processor status. Every 1.7 seconds, it began again.

Henri remained connected from Toulouse.

“Can it hear commands?” he asked.

“We have not tested after the clock fault.”

“Test now.”

Tasha sent a non-disruptive command requesting iden­ti­fi­ca­tion from Gateway’s backup controller.

The return window opened.

Gateway kept repeating the same block.

No acknowl­edg­ment appeared.

“Use protected channel,” she said.

The protected channel operated through separate hardware and a low-gain antenna. It was intended for a spacecraft that had lost normal pointing, software control or most of its electrical system.

The command left Earth.

While they waited, Gateway’s main trans­mis­sion changed.

The repeated block stopped.

A partial event log followed.

TIME REFERENCE MISMATCH.

RECEIVER FRONT-END LIMIT.

SURFACE QUEUE INVALID.

The next line was corrupted.

The line after that read:

EXTERNAL FIELD...

The packet ended.

Nobody spoke.

Tasha opened the raw bytes.

“Do not complete the word,” she said.

The telemetry controller looked at her. “I wasn’t.”

“Good.”

External field could mean elec­tro­mag­netic field, electric field, magnetic field or a software field in the event structure. The packet was truncated before its identifier.

Within seconds, three automated summaries generated by different systems displayed EXTERNAL FIELD ANOMALY.

Tasha deleted them.

“We do not know what it says.”

A senior flight manager approached from the back of the room. “We know enough to preserve it.”

“Preserve the raw packet. Not the guess.”

The protected-channel return window opened.

A single Gateway iden­ti­fi­ca­tion burst reached Canberra.

Signal strength was high.

The iden­ti­fi­ca­tion code failed validation.

“Replay,” Tasha said.

The receiver produced the burst again.

The structure was almost correct. Gateway’s fixed identifier should have occupied thirty-two bits. Twenty-eight matched. Four had changed.

“Random bit flips?” the manager asked.

“Not with this signal strength.”

“Memory corruption.”

“The identifier is burned into the emergency controller.”

“Then receiver corruption.”

“Canberra’s chain is clean.”

The manager looked toward Madrid’s report.

Madrid had detected the same burst.

The same four bits were wrong.

That removed the ground receiver.

Tasha felt the room beginning to lean toward an answer nobody wanted to state.

She stopped it.

“Gateway hardware can corrupt its own trans­mis­sion. Keep the fault tree open.”

The platform’s carrier dropped.

A second later, the low-gain carrier appeared.

Then the main carrier returned.

Both trans­mitted at once.

Their frequen­cies were correct. Their power levels were correct. Neither carried valid data.

“Gateway is radiating,” the commu­ni­ca­tions controller said. “No useful modulation.”

“Command safe mode.”

“We cannot confirm it can hear us.”

“Send through every channel.”

Earth trans­mitted the command from Madrid, Canberra and New Norcia. The signals converged on Mars Gateway across slightly different paths and times.

The orbital platform gave no acknowl­edg­ment.

Its house­keeping stream resumed unex­pect­edly.

Power remained normal.

Battery charging normal.

Attitude control normal.

Thermal control normal.

Propellant pressure normal.

The spacecraft looked healthy in every field it could still commu­ni­cate.

Then the attitude data repeated.

The values did not change as Gateway moved through orbit.

“Frozen frame,” Tasha said.

The controller marked the data stale.

Power values froze next.

Then thermal.

The packet clock continued advancing while the measure­ments stopped.

Gateway was sending a body without motion.

Henri spoke through the Toulouse link.

“Tasha, the surface weather network just lost Utopia.”

She opened the Mars envi­ron­mental feed.

Three fixed stations near the intended Perseus landing region had stopped reporting within twelve seconds of one another. A fourth station farther west remained active but showed a broad elec­tro­mag­netic rise across its unshielded sensors.

The rise had no sharp peak.

It formed a plateau.

“Dust front?” the flight manager asked.

The atmo­spheric model showed a regional dust boundary moving east. It did not cover all four stations. Wind speeds varied. Electrical conditions could extend beyond visible dust.

Tasha placed the field data beside Gateway’s orbit.

The plateau began as the relay crossed the Utopia horizon.

“Coin­ci­dence,” someone said.

The word was not dismissive. It was a request.

Tasha checked Gateway’s other systems.

Star trackers remained locked in the last valid report. Solar arrays delivered expected power. No collision alert. No structural vibration. No thermal event.

A spacecraft with power, attitude and a func­tioning trans­mitter had become unable to send meaning.

That was not black in the ordinary sense.

It was worse.

They could still see the light and no longer trust what it carried.

At 06:19 UTC, Mars Gateway’s carrier ended.

No fade.

No drift.

It stopped between symbols.

The Deep Space Telemetry Center went quiet.

Tasha watched the receiver trace for the next pulse, the low-gain beacon, the protected iden­ti­fi­ca­tion burst.

Nothing returned.

Mars Gateway had gone silent fifteen minutes after its first clock disagree­ment.

The three rovers were already silent beneath it.

Earth had lost the platform that carried most commands to the cargo field, most high-rate data from the surface and most flexible support for any future mission entering Mars space.

The Perseus cargo habitats still sent low-rate beacons through older channels when geometry allowed. Several orbiters remained oper­a­tional. Fixed landers on the far side of the planet continued to report.

Mars had not vanished.

The part of it that mattered most had become difficult to observe.

A government repre­sen­ta­tive joined the incident conference without intro­duc­tion.

“Can Gateway have been destroyed?” he asked.

“No destruc­tion signature,” Tasha said.

“Can it be tumbling?”

“No evidence.”

“Can it be without power?”

“The last valid power data was nominal.”

“Can dust affect an orbital platform?”

“Not directly at Gateway’s altitude.”

“Elec­tro­mag­netic activity?”

“Poten­tially.”

“From Mars?”

“We do not know.”

“From the spacecraft reactor?”

“Gateway does not have one.”

“From another asset?”

“No known asset can produce the observed pattern.”

The repre­sen­ta­tive paused.

“Observed pattern,” he repeated. “Define that.”

Tasha looked at the rover timelines, the surface field measure­ments and Gateway’s corrupted event log.

“Commu­ni­ca­tion failure across several systems.”

“That is not a pattern.”

“No.”

“What would make it one?”

“Evidence that the failures share a cause.”

“Do we have that?”

“No.”

Henri’s face remained still on the Toulouse display.

The government repre­sen­ta­tive asked, “Could this be deliberate suppres­sion?”

The phrase settled over the room.

Tasha had thought the same thing.

Not in those words. Not at first.

She had thought about signal strength increasing while infor­ma­tion disap­peared. About error boundaries repeating too cleanly. About systems failing to leave their own diagnostic wreckage. About three rovers going quiet as their relay paths crossed the same uncertain region. About Gateway remaining powered and pointed while its trans­mis­sions emptied out.

A hand was an expla­na­tion.

It was not evidence.

“Suppres­sion by what?” she asked.

“That is not my question.”

“It has to be. Deliberate requires an actor and a mechanism.”

“Could a classified terres­trial system do this?”

“Not one I know.”

“That is not an answer.”

“It is the only answer I have.”

The repre­sen­ta­tive turned to the flight manager. “What will the public statement say?”

The manager looked at the commu­ni­ca­tions team.

“Multiple Mars assets expe­ri­enced telemetry failures during elevated regional dust and elec­tro­mag­netic activity. Mars Gateway commu­ni­ca­tions are inter­rupted. Recovery procedures are underway.”

Henri unmuted.

“You are linking the dust to Gateway.”

“We are providing envi­ron­mental context.”

“Gateway is in orbit.”

“The surface failures are not.”

“Then separate the statements.”

The manager shook his head. “The public will connect them anyway.”

“That is not a technical reason to connect them for the public.”

The repre­sen­ta­tive said, “We are not announcing possible hostile action without evidence.”

“No one asked you to,” Henri replied.

“You are objecting to envi­ron­mental context.”

“I am objecting to using context as cause.”

Tasha watched the argument move toward language because language was the only system still under their control.

“What does the data support?” the manager asked her.

She took her time.

“The surface assets expe­ri­enced receiver timeouts, corrupted telemetry and safe-mode failures during elevated electrical conditions. Mars Gateway expe­ri­enced clock disagree­ment, receiver-limit reporting, repeated data blocks, invalid emergency iden­ti­fi­ca­tion and loss of carrier.”

“Can dust explain the rovers?”

“It can contribute.”

“Can a processor failure explain Gateway?”

“It can contribute.”

“Can the events be unrelated?”

“Yes.”

“Can we say that?”

“We can say the cause is unde­ter­mined.”

The government repre­sen­ta­tive leaned closer to his camera.

“Would you personally describe this as ordinary failure?”

Tasha looked at Gateway’s final valid packet.

A machine under ordinary failure usually produced a trail. Voltage collapse. Temper­a­ture rise. memory errors. resets. degraded pointing. It broke in directions its designers had imagined, even when the exact cause remained unknown.

Silence was different.

Silence removed the trail.

“I would describe it as unresolved,” she said.

“That was not what I asked.”

“No.”

The repre­sen­ta­tive waited.

Tasha did not add anything.

At 07:03 UTC, the joint statement was approved.

Three Mars surface assets have expe­ri­enced telemetry inter­rup­tions during a period of elevated dust and elec­tro­mag­netic activity. Mars Gateway is currently not responding to scheduled commu­ni­ca­tions. Inter­na­tional mission teams are conducting recovery operations and reviewing possible common technical and envi­ron­mental factors. There is no confirmed evidence of physical damage to any asset.

The wording was accurate.

It left out that the surface failures had occurred within seventy-three minutes.

It left out the invalid emergency identifier.

It left out the partial line beginning EXTERNAL FIELD.

It left out that Gateway had trans­mitted with normal power and no usable infor­ma­tion.

The statement reached the public before the families of several rover-team engineers had been told their missions might be over.

News services placed it beside the Perseus search.

Markets moved.

Theories multiplied.

Tasha stayed at her console.

Recovery command after recovery command went to Mars.

Orbiters were asked to image Gateway’s predicted position. Surface assets outside Utopia were ordered to preserve raw envi­ron­mental data. Ground stations widened their search around every Gateway frequency. Engineers rebuilt its software state from the final packets and searched for a fault capable of freezing measure­ments while advancing the packet clock.

They found several possi­bil­i­ties.

None explained the rovers.

By the end of August 10, Mars Gateway had missed nine scheduled contacts.

No telescope had confirmed damage.

No beacon had been detected.

No command had been acknowl­edged.

The ultra­vi­olet ancillary file from Athena-12 remained incomplete.

The five lines above the horizon stayed inside a damaged packet whose original could no longer be requested from the rover.

Tasha opened the event chronology one last time before shift change.

ATHENA-12: UNRESPONSIVE.

UTOPIA TRAVERSE: UNRESPONSIVE.

NANDINI: UNRESPONSIVE.

MARS GATEWAY: UNRESPONSIVE.

The system asked whether the incidents should be grouped under a common cause.

She selected NO.

Then she changed it to UNKNOWN.

Mars Gateway continued around the planet.

Its solar arrays tracked the Sun. Its thermal system moved heat into the radiators. Its guidance computer compared star positions to stored maps and adjusted the spacecraft by fractions of a degree.

Inside the commu­ni­ca­tions controller, a protected routine counted the time since the last valid command.

It opened the primary receiver.

No authen­ti­cated uplink entered the buffer.

It opened the low-gain receiver.

No authen­ti­cated uplink entered the buffer.

It waited through the interval defined by its safe-mode table, then trans­mitted its iden­ti­fi­ca­tion code toward Earth.

The trans­mitter reported full power.

The antenna reported correct pointing.

The routine received no acknowl­edg­ment.

It reset the receiver and began again.

AWAITING UPLINK.

The words existed only as machine state.

No one on Earth saw them.

Book Dashboard
Jump to Part ▾
All Part ranges