42. Ethan
CHAPTER FORTY-TWO
Ethan
By mid-afternoon, I've stopped pretending this is only about the gala.
The corrupted demo code is open across three monitors in the secure analysis room, stripped down to its core architecture.
Jeffrey stands beside the main console, arms folded, expression grim.
Sara is on the other side of the glass with legal, which is where I asked her to stay until we had something useful enough to say out loud.
The room is cold. Servers prefer it that way, and I’ve always found the environment clarifying. No excess or softness. Just data, trace logs, architecture maps, and the quiet hum of machinery doing exactly what it has been instructed to do.
That, of course, is the problem.
Systems don't fail emotionally.
People do.
“Run it again,” I say.
Jeffrey doesn’t move. “We’ve run it six times.”
“Then the seventh should be efficient.”
He gives me a look. “That sounded like a threat.”
“It was a request.”
“No, it wasn’t.”
I don’t answer.
He runs it again.
The structural comparison populates slowly, current demo corruption on the left, recovered stabilization framework from Megan’s aircraft on the right. Two different generations of technology. Two different platforms. Two different failures.
Except not different enough.
Four years ago, the crash investigation treated Megan’s aircraft as an isolated failure.
We were looking for mechanical instability, pilot error, weather interference, corrupted telemetry, manufacturing flaws. Singular causes. Singular faults.
Nobody was looking for behavioral architecture repetition across entirely different systems because there was nothing to compare it to.
Until now.
The software doesn’t match line by line. It was never going to. Anyone looking for a direct copy would miss it.
But once the superficial architecture is stripped away, once the variables are normalized and the dependency paths are reduced to behavioral logic, the pattern becomes impossible to ignore.
A feedback amplification loop, a masked failsafe bypass, a delayed pilot input acknowledgment, a diagnostic record showing the safety layer as intact when it was not functionally active.
I stare at the overlay.
There it is.
The ghost in the machine.
Jeffrey exhales through his nose. “Damn it.”
“Yes.”
“I really wanted this to be nothing.”
“So did I.”
He glances at me. “Did you?”
I keep my eyes on the screen. “Yes.”
He lets the silence sit for several seconds. “Because from where I’m standing, it looks like part of you has been waiting four years for this to be something.”
My jaw tightens.
“I’m not saying that to be cruel,” he adds.
“I know.”
“I’m saying it because I was there last time.”
Last time.
A useful phrase, if one wants to compress months of obsession, grief, missed dinners with my son, and entire nights spent reviewing telemetry into two syllables.
“I remember,” I say.
“Do you?”
I turn from the monitor. “Yes.”
He holds my gaze, and for once, there’s no humor in him at all. “You nearly disappeared into it.”
“I stopped.”
“Eventually.”
“For Oliver.”
“Yes.” He steps closer. “And now Addy is pregnant with triplets, your company is under attack, Bryce is acting like a rejected villain in a bad courtroom drama, and this…” He gestures to the screen. “This is exactly the kind of thing that could pull you under again.”
My first response is irritation.
My second is recognition.
Both are inconvenient.
Maybe I shouldn’t have told Jeffrey so much about what’s going on…
“I’m not unstable.”
“I didn’t say you were.”
I roll my eyes. “You implied it.”
“I implied you’re human, which I realize is offensive to your brand.”
“Jeffrey.”
“No. Listen to me for once without turning it into an operational review.”
I go still.
He rarely uses that tone.
When he does, it's usually deserved.
He points toward the screen. “If we chase this wrong, we destroy chain of custody, tip off whoever did it, hand the board a reason to sideline you, and put Addy through hell while she’s already dealing with more than enough.”
“I know that.”
“And if it's Bryce?”
“Then we prove it.”
“Not punish first, prove later.”
My voice cools. “You think I need that clarified?”
“I think you’re looking at the thing that might clear Megan’s name. So yes. I do.”
The room goes silent except for the servers.
Megan’s name does what it always does.
Changes the air.
The words leave me before caution can stop them.
“It wasn’t an accident.”
Jeffrey doesn’t answer immediately.
I hear him breathe in. “Ethan.”
“No.” I step toward the console and isolate the old failure branch. “This wasn’t weather. It wasn’t fatigue or hesitation. The aircraft entered a feedback loop because the dampening layer was bypassed under sensor conflict.”
“We think.”
“No. We know that part.” I bring up the log timing Addy identified. “Megan responded. The system accepted her input late or recorded it late. Either the aircraft was already fighting her, or the log was altered to make her response look delayed.”
Jeffrey’s face tightens.
“She didn’t ignore the warnings,” I say. “She fought the aircraft.”
He looks at the screen.
Then at me.
I see the moment he stops trying to slow me down and starts following the evidence.
“Show me the timestamp discrepancy again,” he says.
I do.
The old report displayed pilot input thirty-one seconds after the first escalation warning. Too late, according to the investigation. Enough to support pilot error.
But the raw trace, buried beneath a reconstructed maintenance file, shows a manual correction command initiated nine seconds after the warning.
Nine.
Megan would’ve been fast.
The processed report delayed the record by twenty-two seconds.
Four years ago, the official investigation relied on processed diagnostic exports because the raw aircraft telemetry was partially corrupted during impact recovery.
At the time, the discrepancy looked like sensor degradation.
Now it looks curated.
Jeffrey leans in, reading. “That’s not impact damage, and it’s not sensor noise.”
“No.”
“Someone cleaned the log.”
“Yes.”
He swears under his breath.
I bring up the current demo corruption. “The same technique appears here. Standard diagnostics show the failsafe present. Under the trigger condition, it’s bypassed. Reporting remains clean until stress simulation.”
“Which is why the patch looked stable. Because it was hiding the same way.”
“Yes.”
Jeffrey drags a hand down his face. “Jeez.”
He turns toward me. “Who had access to Megan’s aircraft system before the flight?”
“Meaningful access?”
“Meaningful.”
“Three people.”
He doesn’t make me say it.
I do anyway.
“Megan. Me. Bryce.”
Bryce never had primary oversight on Megan’s aircraft. Not operationally. His role back then was broader systems architecture, simulation modeling, and instability testing.
The kind of access that mattered technically, without placing him anywhere near the final flight investigation afterward.
At the time, that distance felt reassuring.
Now it feels dangerous.
Jeffrey closes his eyes briefly. “And Bryce had already left formal operations.”
“His formal access was supposed to be limited.”
“But legacy credentials?”
I sigh heavily. “Not fully revoked. Because back then we were idiots.”
“You were small.”
“Same thing.”
Strong AeroTech in those days wasn’t the tower it is now. It was three rooms, too many prototypes, too little sleep, and a level of trust that now seems less loyalty and more negligence.
Bryce had been brilliant then.
Erratic, yes. Ambitious. Easily bored. But brilliant.
He understood stabilization architecture intuitively. He could find vulnerabilities in systems before most engineers knew where to look. That skill built part of the company.
That same skill may have created vulnerabilities none of us understood quickly enough.
The possibility settles into me slowly, resisting shape even while the evidence keeps pushing toward it.
“Why?” Jeffrey asks quietly.
I stare at the access logs without answering immediately because that question has lived underneath every other question for four years.
I move to the table where we’ve spread everything into sequence. Current sabotage. Bryce’s patch. The gala argument. Celeste’s statements from the café, relayed by Addy. Old access logs. Megan’s crash data.
“Addy spoke with Celeste.”
“I know. You sent me the summary.”
“She said Bryce believes I stole his life.”
Jeffrey looks up. “That sounds like him.”
I pick up the access log. Remote authentication. Former admin architecture group. Masked location. Four minutes, twelve seconds.
“Eleven hours before Megan’s flight, a legacy admin key accessed the stabilization configuration.”
Jeffrey’s attention sharpens. “You didn’t have that before.”
“I had it. I didn’t understand it.”
“Because it was partial.”
“Because I wanted it to mean something, and everyone told me it didn’t.”
Including me.
Bryce had been reckless, arrogant, impossible to manage half the time, but he had also been one of us.
I spent years treating the inconsistencies as grief, looking for somewhere to land because the alternative was uglier than anything I knew how to survive.
He absorbs that.
The old frustration is still there. Not toward him, exactly. Toward everyone who told me grief was making me see patterns. Toward the investigators who relied on processed logs. Toward myself for eventually letting the question go.
Jeffrey studies the log. “Can we trace the key?”
The legacy authentication structure predates half our current security architecture,” I say. “Back then we weren’t building for forensic isolation. We were building to keep prototypes alive long enough to function.”
Jeffrey grimaces. “Meaning?”
“Meaning whoever used it understood exactly how invisible old systems could become.”
“What about old backups?”
“I’ve requested cold storage retrieval.”
“Without alerting IT too widely?”
“Yes.”
“Good.”
He looks at the screen again. “If Bryce accessed that aircraft, altered the failsafe, and then masked the log…”
“He caused the crash.”
“Maybe unintentionally.”
I look at him.
He lifts a hand. “I’m not defending him. I’m saying motive matters. Did he intend to kill Megan? Or did he intend to create a system failure that proved a point?”
The distinction is legally relevant.
Morally less so.
“If he removed a failsafe from an aircraft stabilization system,” I say, “intent becomes a narrower comfort than people pretend.”
Jeffrey nods. “Agreed.”
I turn back to the monitors. “What did he want?”
Jeffrey leans against the table. “Back then?”
“Yes.”
“Recognition. Money. A bigger role. Half the time he acted like he wanted out, the other half like he wanted us to beg him to stay.”
I remember.
He called me cautious. Megan called him reckless.
Megan was right.
I grip the edge of the table.
“He argued with Megan about the dampening layer,” I say.
Jeffrey looks at me. “When?”
“Two weeks before the crash.”
“Why didn’t you mention that?”
“Because at the time, it was one of a hundred technical arguments.”
“What did he say?”
I close my eyes briefly, reconstructing.
The conference room. Megan standing with a marker in her hand. Bryce pacing because he always thought movement made him more persuasive.
“He thought the response dampening was too conservative,” I say. “That it reduced system authority under sensor conflict and made the aircraft feel less responsive.”
“And Megan?”
“Said the entire point was to prevent overcorrection if the system misread input.”
Jeffrey’s face hardens. “Which is exactly what happened.”
“Yes.”
“Did he take it badly?”
“He always took disagreement badly.”
The memory sharpens further.
Bryce laughing. Telling Megan she was too married to caution. Megan smiling that dangerous, calm smile of hers, telling him caution was the reason pilots came home.
I sit down.
“Why would he target Megan’s aircraft?” Jeffrey asks.
I know the answer I don’t want. “Because she was flying the system he disagreed with.”
“Or because hurting her hurt you.”
I look at him sharply.
Jeffrey doesn’t back down. “It’s possible.”
I don’t want it to be. Not because it would absolve Bryce. Because it would mean Megan died as collateral in someone else’s grievance with me.
That thought's intolerable.
So I set it aside until evidence requires it.
“We don’t know enough,” I say.
“No. We don’t.”
“We need logs. Original backups. Access records. Engineering communication. Anything tied to legacy admin keys.”
The belief should be relief.
For now it’s the start of another crash, one that has been falling toward us for years.
This time, I intend to find the black box before anyone else dies in the wreckage.