PART 4:

“Your timing file has a corrupted entry. It’s causing both navigation systems to initialize simultaneously. The safety lockout interprets that as a fault condition because, technically, it is one. But it’s not a hardware fault and it’s not a sensor fault. It’s a data fault in a file that your diagnostic scanner doesn’t look at because the file itself doesn’t generate error codes.

” Raymond stared at him. One of the other engineers, a compact man in his 40s who Ethan would later learn was part of the navigation systems vendor team, had turned and was listening. “That’s,” Raymond started. “Show me the configuration directory for the navigation initialization sequence,” Ethan said. “I’ll show you exactly where it is.

” Raymond turned to the navigation systems engineer. The engineer looked at Ethan. Then he looked at the monitor. Then he sat down next to Ethan and pulled up the directory. It took 4 minutes. The corrupted entry was exactly where Ethan had said it would be. A single malformed timestamp in the initialization timing file, invisible to automated scanners, invisible to the component level diagnostics, invisible to everyone who had been looking at engines and sensors and hydraulic lines and landing gear.

The navigation systems engineer made a sound that was not quite a word. “6 days,” he said quietly, to no one in particular. Raymond had gone very still. Ethan looked at the screen, at the corrupted data point sitting there like a splinter so small you’d never see it unless you were looking for exactly that. “Can you fix it?” Raymond said.

“It’s not complicated,” Ethan said. “Delete the corrupted file, rebuild the initialization sequence with a clean timing entry, restart the system. 40 minutes, maybe less.” Raymond looked at him for a long moment. Then he looked at the jet. Then he pulled out his phone and made a call. “Ms.

Ashford,” he said, “you need to come to monitor station four, prompt.” Victoria arrived in under 2 minutes, which told Ethan more about her than anything else he’d observed so far. Raymond explained what Ethan had found. He was precise about it. To his credit, he laid it out clearly and credited Ethan without any of the hedging or qualification that some people in his position might have been tempted to add.

Victoria listened without interrupting. She had the particular quality of attention that made you feel like every word you said was being actually processed rather than just heard. When Raymond finished, she was quiet for a moment. “You’re confident?” she said to Ethan. “I’m not a betting man,” Ethan said, “but yeah. Yeah, I’m confident.

” “What made you look at the initialization logs specifically?” He thought about how to answer that. The honest answer was that he’d seen something in the pattern of the display from 60 yards away that reminded him of something his father had written in a notebook he hadn’t opened in 2 years. That wasn’t an easy thing to explain to someone he’d met 20 minutes ago.

“My father was a military avionics tech.” he said. “He used to say that software problems hide inside hardware diagnostics because the hardware diagnostics aren’t looking for software problems. The scanner looks for what it’s programmed to look for. If the problem is somewhere the scanner isn’t programmed to look.” He shrugged.

“Nobody finds it.” Victoria looked at him for a moment longer than was comfortable. Not hostility, more like she was filing something away. “Okay.” she said. She turned to Raymond. “Let him work.” It was as simple as that. Doubt, which is not to say that everyone in that hangar felt the same way. When word moved through the floor that the new theory proposed by a civilian shop owner who had walked in off the service road 30 minutes ago was being taken seriously enough to act on, the reaction ranged from cautious skepticism

to openly stated doubt. One of the German engineers, a silver-haired man named Klaus, who had been flown in from Stuttgart specifically because of his reputation with avionics systems on high-end private aircraft, sought out Ethan at the monitor station before he started work. “You understand.

” Klaus said, not unkindly, “that we have been through every section of the avionics software on this aircraft. My team ran a complete Did you manually review the initialization timing file?” Ethan said. Klaus paused. “The automated scanner doesn’t look there. I know, that’s the point.” Klaus looked at the monitor.

He was quiet for a moment, then he pulled up a stool. “Show me.” he said. Ethan showed him. Klaus leaned in, studied the corrupted entry for a long moment, and then sat back and crossed his arms and stared at something that wasn’t in the room. “Five days I’ve been here,” Klaus said. “We looked at everything.” “You looked at everything the procedure told you to look at,” Ethan said.

He kept his voice neutral. This wasn’t a criticism. He’d done the same thing himself more times than he liked to admit before his father’s lessons had become fully embedded in his approach. Standard procedures are built for standard problems. This wasn’t a standard problem. Klaus rubbed his jaw.

“And you found this in 20 minutes?” Another silence. “Show me the full log sequence,” Klaus said. Ethan showed him. By the time they were done walking through it, three other engineers had gathered around the monitor. Not because anyone had called them over. They drifted in the way that engineers drift toward something that looks like a resolution after 6 days of nothing.

👉 [Tap here for the Next Part ] 👈