Victoria pictured the enormous aircraft standing motionless in the hangar while experts congratulated themselves on a successful installation. "It thinks it already did the thing it never did," she said.
Caleb nodded. "And there's the missing piece."
For a moment she was no longer watching an aircraft record. She was thinking of a finance meeting from the previous week, where Lionel Graves had described safety training across the company as fully implemented because a central office had issued the updated training package. He had not been able to tell her how many technicians had actually received instruction or passed an assessment. The report had been green, though, and she had accepted it. Now she wondered how many other green reports concealed work that had never reached the people who needed it.
"It's the whole company," she murmured.
"Sorry?"
"Nothing. Finish telling me about the airplane."
The manufacturer's remote technical representative asked Caleb to identify the record supporting his conclusion. He did so without drama, showing the expected acknowledgment, the missing actual handoff, and the status flag that permitted the summary to call the system healthy. The representative went quiet for nearly a minute. Then he asked Noah to retrieve a supplemental service advisory that had been released for a closely related equipment configuration six months earlier, before Victoria's particular aircraft received the current update.
The advisory described a rare state-persistence problem following certain maintenance conditions. It had not been categorized as applicable to the aircraft's serial number, which was why it had never appeared in the ordinary service recommendations. Caleb read the summary and felt the final piece settle into place. The underlying failure mechanism was similar enough to justify deeper manufacturer review, but not close enough to permit an improvised repair.
"I think we found your problem," he said to Victoria. "Now we need to find an approved way to correct it."
Richard, who had insisted on remaining at the edge of the work area, spoke before the technical representative could. "That's circumstantial. You're using a different configuration to make a conclusion about this one."
"Yes," Caleb said. "Which is why nobody's touched the operating state yet. We have a hypothesis supported by the log, and now we have a manufacturer document explaining how it can happen. The next step is confirmation, not a victory speech."
Noah tried to hide a smile. Victoria noticed and let him keep it. A technician arrived with the original maintenance work order, and the remote representative began comparing installed configuration details against the advisory. For the first time since the aircraft had failed, the technical team was working toward a specific mechanism instead of collecting unrelated symptoms.
Half an hour later, the manufacturer authorized an approved recovery procedure through the aircraft's designated maintenance provider. It did not involve opening the engine, replacing flight-control hardware, or making an unauthorized edit to safety-critical software. It involved preserving the existing records, restoring the affected module's retained initialization state through a validated maintenance process, and independently verifying that the original software package remained intact. A licensed avionics specialist would perform and document the work, while Caleb and Noah monitored the records that had revealed the fault.