PART 3:

Raymond followed two steps behind, already looking like he was preparing an apology on behalf of the inconvenience. She stopped in front of Ethan and looked at him the way a person looks at a door they’re not sure is locked. “Avionics,” she said. “Small shop,” Ethan said. “Nothing like this.” He gestured toward the aircraft.

“What’s the problem?” The question landed with a kind of directness that seemed to surprise her. Most people in Ethan’s experience started conversations with pleasantries. He’d never had much patience for them. Victoria tilted her head slightly. “If 200 engineers haven’t found it in 6 days, I’m not sure.” “What are those logs showing?” Ethan said.

He was looking past her at the monitor bank. She turned to follow his gaze then looked back at him. You can read those from here? No. But I can see the structure of how they’re displaying. It looks like you’re running the automated diagnostic scan. We are, Raymond said with a tone that suggested this was the correct and obvious thing to do.

Have you read the actual initialization logs manually? A silence settled over the small group near the door. It was the kind of silence that answers a question more clearly than any words could. Ethan looked at Raymond. Raymond looked at Victoria. Victoria looked back at Ethan. Come inside, she said. Raymond showed him to the monitor station and pulled up the full initialization log sequence.

Not the automated scan results, but the raw logs themselves. Pages and pages of timestamp system data generated every time the startup sequence had been attempted over the past 6 days. Ethan pulled a stool up to the monitor and sat down. He didn’t touch the keyboard yet. He just looked. This was something his father had taught him so early that it had become instinct.

Before you do anything, before you run a test or pull a component or make a single change, you look. You observe the whole thing. You let it sit in your mind without trying to fix it yet. Around him the hangar continued its activity. Engineers moved and conferred and argued quietly in multiple languages. Someone three stations down was on a phone call that sounded like it was going badly.

A technician near the nose wheel was running the same diagnostic check for what appeared to be at least the fourth time today judging by his expression. Ethan looked at the logs. The startup sequence for an aircraft like the Meridian G9 was complex. Hundreds of individual systems initializing in a carefully choreographed order.

Each one dependent on the ones before it. Each one feeding information to the ones after it. The automated scanner looked for error codes, red flags that the system itself raised when something went wrong. If a component failed, it flagged itself. If a voltage was out of range, it logged an error. These were the things the scanner found, cataloged, and reported.

But the scanner didn’t look for the spaces between the errors. It didn’t look for the interactions between systems that were each functioning correctly, but were for some reason fighting each other. Ethan read slowly. He’d always been a slow reader, not because he had trouble with the words, but because he had trouble reading past something before he understood it completely.

Sophie teased him about it sometimes. “Daddy, you read like you’re afraid the book is going to run away.” He went back to the beginning, read through again. And there it was, small, easy to miss, easy to assign to background noise if you weren’t looking for it specifically. During the third phase of the startup sequence, the primary navigation system and the secondary navigation system were both attempting to initialize at the same moment.

This wasn’t supposed to happen. There was a timing file that governed the sequence, telling each system when to activate. The timing file existed specifically to prevent simultaneous initialization because simultaneous initialization created a data conflict that the safety systems read as a fault condition. But the timing file had a problem.

Or rather, a small piece of it did. A single corrupted configuration entry. Not a missing file, not a dead component, not anything that would throw an error code during standard diagnostics. Just a tiny piece of corrupted data inside an otherwise functional file, causing the two navigation systems to receive the same initialization trigger at the same moment every single time the startup sequence ran.

And every time that happened, the safety lockout engaged. And the engines didn’t start. Ethan sat very still for a moment. He thought about his father’s notebooks. Not a specific entry, just the notebooks themselves. The accumulated weight of years of problems solved and lessons learned. His father had written something once about software failures that disguised themselves as hardware problems.

Had written it more than once, actually. Ethan could remember seeing it in at least two separate notebooks because his father had considered it important enough to record twice. The machine will tell you it’s broken. The machine will be wrong about why. He leaned back on the stool and looked at the ceiling of the hangar for a moment. Then he found Raymond.

“I think I know what it is,” he said. Raymond was in the middle of a conversation with two other engineers. He held up a finger, finished his sentence, and then turned to Ethan with the careful expression of a man who had been presented with theories for 6 days and had learned not to react to any of them. “Okay,” Raymond said.

👉 [Tap here for the Next Part ] 👈