Military Homecomings

The Name Missing from Christmas · Chapter 2 of 6

Chapter 2

By My Life Story Editorial · Published · Updated

The moment the SUV door closed, Christmas disappeared.

General Parker sat opposite me while his aide handed me a secure tablet.

The screen displayed a map of Northern Europe.

A blinking red marker sat over the Baltic Sea.

“Call sign Sentinel Six,” Parker said. “Specialized surveillance aircraft operating under a joint mission authorization.”

I scanned the data.

Last confirmed position.

Altitude.

Speed.

Communications record.

Everything stopped at nearly the same moment.

“No distress call?”

“None.”

“Transponder?”

“Gone.”

“Satellite?”

“Intermittent coverage during the disappearance.”

I enlarged the route.

“Why was it flying this corridor?”

Parker hesitated.

“You’ll get the full briefing at the Pentagon.”

“That means the answer is classified above what you’re comfortable discussing inside a vehicle.”

“Yes.”

I handed the tablet back.

“And Ethan?”

Parker studied me.

“I don’t know how much you know about your brother’s work.”

“He tells people he’s a strategic logistics consultant.”

“That’s broadly accurate.”

Broadly.

A word intelligence officers learn to distrust.

Parker continued.

“His firm has civilian contracts connected to transportation modeling, supply-chain resilience, and infrastructure consulting.”

“I know.”

“One subsidiary has recently subcontracted analytical support to a Defense Department vendor.”

My stomach tightened.

“Which vendor?”

“Valiant Meridian Systems.”

I knew the name immediately.

Not because it was famous.

Because it wasn’t.

Companies like Valiant Meridian existed in the invisible machinery between government missions and private industry.

They didn’t build aircraft.

They built pieces of systems.

Software.

Routing models.

Encrypted logistics platforms.

Things that sounded boring until somebody compromised them.

“What was Ethan’s access?”

“Supposedly limited.”

“Supposedly?”

“We found his credentials associated with a server that should never have been accessible from his network.”

I looked out the window.

Christmas lights streaked past.

“You think he leaked mission information.”

“We don’t know.”

“You think he might have.”

“Yes.”

The answer landed heavily.

I remembered Ethan’s face.

I can explain.

“Has he been detained?”

“Agents are arriving at your parents’ house now.”

That meant the dinner party was over.

I should have felt satisfaction.

After what they had done to me, maybe some small, wounded part of me should have enjoyed watching Ethan’s perfect evening collapse.

I didn’t.

He was still my brother.

And if he had done what the preliminary evidence suggested, our family humiliation was insignificant compared with what might be happening in the Baltic.

“Any signal from Sentinel Six?”

“Nothing confirmed.”

“Debris?”

“None.”

“That’s good.”

“Possibly.”

I looked at Parker.

“You think it landed.”

“We don’t know what to think.”

Thirty minutes later, we entered a secure operations center beneath layers of armed security.

Screens covered the walls.

Maps glowed across conference tables.

Officers and civilian analysts moved with controlled urgency.

Nobody mentioned Christmas.

Nobody cared that I had been standing on my parents’ porch less than an hour earlier.

That was one of the things I had always loved about the work.

Inside these rooms, personal drama had no rank.

You either contributed or you got out of the way.

A Navy captain approached.

“Admiral.”

“Status?”

“Sentinel Six remained off network. NATO partners are conducting search activity. No confirmed crash signature.”

“Crew manifest?”

He handed me a folder.

Seven names.

I read every one.

Seven people had families somewhere.

Seven families probably believed their loved ones were working an ordinary holiday rotation.

“How long before next-of-kin notification?”

“Pending confirmation.”

Parker pointed toward a separate screen.

“Show her the access logs.”

An analyst brought up a timeline.

Ethan’s consulting account had authenticated into Valiant Meridian’s logistics environment three times in the previous month.

Nothing remarkable.

Then one login appeared twelve hours earlier.

Unauthorized access.

A restricted mission-routing directory.

From Ethan’s account.

“Location?”

“His office network in Arlington.”

“Could credentials have been stolen?”

“Yes.”

“Malware?”

“Possible.”

“Physical access?”

“Still checking.”

I leaned closer.

“Why would someone use his credentials if they knew it would point directly back to him?”

The analyst nodded.

“We asked the same thing.”

Maybe Ethan was guilty.

Maybe he was careless.

Or maybe somebody wanted us to believe he was responsible.

Parker folded his arms.

“What do you see?”

“Too obvious.”

“You think he was framed.”

“I think good intelligence work begins by distrusting convenient answers.”

That earned the smallest nod from Parker.

My secure phone vibrated.

One message.

FBI liaison requesting family contact approval. Ethan Bennett asking specifically for Rear Admiral Rebecca Bennett.

I stared at it.

Parker noticed.

“Your call.”

I hated that phrase.

My call.

Ethan had spent years diminishing what I did.

Now I was supposed to decide whether to speak to him while his name sat in the middle of an international military incident.

“Put him through.”

Two minutes later, my brother’s voice entered a secure conference room through an encrypted line.

“Rebecca?”

He sounded nothing like the man who had mocked me through the glass.

“Where are you?”

“At Mom and Dad’s.”

“Agents with you?”

“Yes.”

“Then choose your next words carefully.”

Silence.

Finally he said, “I didn’t know what it was.”

Every officer in the room looked at me.

“What?”

“A project.”

“What project, Ethan?”

“I did some outside work.”

“For whom?”

“I don’t know.”

I closed my eyes.

“That is not an acceptable answer.”

“They came through an intermediary.”

“Name.”

“Daniel Cross.”

An analyst started typing immediately.

Ethan continued.

“He said he represented an overseas investment group evaluating shipping vulnerabilities.”

“When?”

“Three months ago.”

“What did you give him?”

“Nothing classified.”

“That wasn’t my question.”

“I gave him modeling data.”

“What data?”

“Transport networks. Civilian freight. Fuel infrastructure.”

My pulse sharpened.

“Military routes?”

“No.”

“You sure?”

“Yes.”

Then he hesitated.

There it was.

“Ethan.”

“He asked whether our software could predict government transportation patterns based on public procurement data.”

The room became very still.

“And you said?”

“I said theoretically.”

“What did you send?”

“A demonstration.”

One analyst swore softly.

I ignored him.

“What was in the demonstration?”

“My company’s algorithm.”

“What datasets?”

“Public information.”

“Only public information?”

Another hesitation.

“Ethan.”

“One subcontractor dataset may have been included.”

Parker’s jaw tightened.

“What subcontractor?”

“Valiant Meridian.”

I wanted to reach through the phone.

“You used defense-contractor information in a private demonstration?”

“It wasn’t marked classified.”

“That does not mean it was yours.”

“I know that now!”

His voice cracked.

For the first time, I heard fear.

Real fear.

“I thought Cross was a client.”

“How much did he pay you?”

“Rebecca—”

“How much?”

“Two hundred thousand dollars.”

My stomach turned.

Ethan had laughed at my career because he believed money proved importance.

Now his appetite for money might have helped someone track a military aircraft.

“Where is Cross?”

“I don’t know.”

“Last contact?”

“Yesterday.”

“What did he ask?”

“He wanted updated routing outputs.”

“Did you send them?”

“No.”

A pause.

“Not intentionally.”

I looked at Parker.

He looked back.

“What does that mean?” I asked.

“My laptop started syncing files after I opened something he sent.”

Malware.

There it was.

“Did you report it?”

“No.”

“Why?”

“I thought IT would handle it.”

“Did you tell IT?”

Another silence.

“No.”

Of course.

Because admitting a problem would have been embarrassing.

Ethan preferred being admired to being careful.

“Rebecca,” he said, suddenly smaller. “Did I cause this?”

I looked at the seven names on the crew manifest.

“I don’t know.”

“Are people dead?”

“I don’t know.”

“Please.”

“I said I don’t know.”

The secure room felt suffocating.

Then an analyst suddenly stood.

“Admiral.”

I turned.

“We have something.”

A waveform appeared on the main screen.

Weak.

Fragmented.

But real.

“Emergency burst transmission detected six minutes ago.”

“From Sentinel Six?”

“Encryption matches.”

My heart accelerated.

“Location?”

“Baltic coast. Eastern sector.”

“Friendly territory?”

The analyst looked uneasy.

“Not exactly.”

A second screen populated with coordinates.

Parker walked closer.

“That’s nowhere near the flight path.”

“No, sir.”

The message began decrypting.

Only fragments survived.

FORCED DESCENT

SYSTEM COMPROMISE

CREW ALIVE

Then one final line appeared.

DO NOT TRUST RECOVERY ROUTE

Nobody spoke.

Sentinel Six had not crashed.

Someone had diverted it.

And whoever had done it apparently expected us to send rescuers into a trap.

Parker turned toward me.

“Merry Christmas, Admiral.”

I stared at the coordinates.

“Let’s bring them home.”

---

✦
YOUR CHOICE

Cookie preferences

Read and listen either way. You can change your choice at any time using the link in the footer.

Essential & reading preferences

Remember this choice and the bookmarks, text size and listening settings you choose. Also supports security and publisher sign-in.

Always available

Help us understand story visits, chapter progress and listening using a random browser identifier. No advertising trackers are enabled.

Your choice lasts 180 days on this browser and this website. Read our privacy policy.