PART 5:

Nobody said anything dismissive after that. Ethan worked steadily. He wasn’t a performer. He didn’t narrate what he was doing or explain each step unless someone asked. He just worked, the same way he worked at his bench back at the shop, with that particular focused quiet that Sophie sometimes interrupted by sliding a drawing under the door because she knew better than to knock when he was deep in something.

He thought about Sophie while he worked. He usually did, at some level. She was the background hum of his daily existence, present even when she wasn’t physically there. She was 8 years old and had her mother’s eyes and her grandfather’s stubbornness and a laugh that could reorganize a bad day.

She was currently at school, which meant she had no idea that her father was sitting at a monitor station in the most expensive hangar in the state attempting to fix a problem that 200 engineers had failed to solve. He thought about what he’d tell her tonight. Probably not the full story. Sophie had a way of getting serious about things and then worrying about them, and he didn’t want her worrying about whether he’d done it right.

He’d tell her something simple. I found a problem at work today. A small one. She’d ask if he’d fixed it. He’d say yes. She’d go back to whatever she was drawing, he hoped. The access to the software partition took several minutes to establish. The corrupted file was exactly where the initialization logs had indicated it would be.

Not hidden, not encrypted, just sitting in its directory being quietly catastrophic. Ethan examined it fully before doing anything. He wanted to be certain he understood the complete shape of the problem before he changed anything. His father’s rule, don’t fix something until you know what it is. Knowing what it is and knowing how to fix it are different things.

The file was corrupted at a single point, a timestamp value that had somehow been written incorrectly, probably a data transmission error during the software installation. A thing so small and random that it was almost impossible to guard against. And yet here it was. This microscopic mistake that had grounded a $75 million aircraft for 6 days and summoned 200 experts from around the world.

Ethan deleted the corrupted file. He rebuilt the initialization timing sequence from the aircraft’s backup configuration, verifying each value manually before writing it. This was the slow part. This was the part where patience mattered more than intelligence, where the tendency to rush toward the finish line could undo everything that had come before it.

He wrote the clean timing file. He verified it. He verified it again. Then he looked up and found Raymond standing nearby. “I think we’re ready,” Ethan said. Raymond relayed it to the chief technician, a lean man named Marcus, who had been with the company for 16 years and who had the expression of someone who had given up hoping a long time ago, but hadn’t yet admitted it.

Marcus looked at Ethan. You’re sure? No, Ethan said honestly. But I’ve done everything I know how to do. The rest is the aircraft’s call. Something in Marcus’s face shifted slightly. Maybe it was the honesty. He nodded once and headed for the cockpit stairs. The hangar changed in the way that large spaces change when the people inside them all shift their attention to the same thing.

The conversations tapered off. The engineers near the nose wheel stopped what they were doing. The contractors at the far end of the floor turned to look. Even the phone call that had been going badly ended. The man with the phone standing with it still pressed to his ear as he watched Marcus disappear into the cockpit.

Ethan stayed at the monitor station. He didn’t need to watch the cockpit. He’d see everything he needed to see in the system data. He watched the screens waiting for the initialization sequence to begin. Victoria appeared at his left elbow. He didn’t hear her approach. How long? She said quietly. The sequence takes about 90 seconds to complete, he said.

If the timing conflict is resolved, both nav systems should initialize in the correct order and the safety lockout won’t engage. And if it doesn’t work? He was quiet for a moment. Then we look again. She nodded. Not reassured exactly. Too honest for that. But something. The monitors flickered as Marcus initiated the startup sequence.

The initialization log began populating in real time. Phase one, nominal. Phase two, nominal. Ethan watched the screen the way he had watched his father work years ago. That kind of total attention that isn’t passive, isn’t waiting, but is a kind of active listening. The systems talking in their machine language and Ethan translating.

Phase three. Primary navigation initializing. The timing file routed the trigger. Primary navigation complete. A full beat of silence. Then, secondary navigation initializing sequential correct no conflict. Ethan let out a breath he hadn’t been aware he was holding. Phase four. Phase five. Then the sound.

Low at first, yeah, a rising whine that climbed from inaudible to present to unmistakable. The first engine spooling up. The sound of the turbines catching, building, finding their rhythm. The first engine roared. In a hangar that had been working in the shadow of six days of silence and failure, the sound was enormous. It filled the space.

👉 [Tap here for the Next Part ] 👈