Give me 5 minutes under the midfuselage, Nathan said. If I'm wrong, you can have security walk me off this airfield. Robert objected immediately, warning that opening a technical access panel in front of press cameras would void the aircraft's certification status for the day. Nathan looked at Audrey. If I'm right, it lost that status the moment your people swapped the part.
Audrey did not fully believe him yet, but she understood that the only way to protect her own credibility in that moment was to let him try. She agreed to give him 3 minutes on the condition that the entire process be filmed. A murmur passed through the assembled guests. Uncertain whether to keep watching or look away, Audrey stood at the podium with her prepared remarks still open on the screen behind her, aware that whatever happened next would matter far more than any of it. Nathan walked toward the aircraft, placed his hand against a section of the fuselage with no visible handle, and said, "In 3 minutes, everyone here will know exactly who understands this jet. " Nathan reached the belly of the Stratos S12 and counted four rows of rivets from the wing edge, pressed a small seam soap, and rotated a hidden latch buried inside the structure.
A narrow metal panel popped open, one that nobody on the current maintenance team knew existed. He explained that this was a mechanical recovery bay built into the airframe to give a pilot manual access to the fuel balance system if the central computer ever failed. Robert claimed Nathan could have read about it in an old archived document. Nathan asked the lead technician standing nearby whether this compartment appeared anywhere in the aircraft's commercial documentation. The technician checked and confirmed it did not.
That was the first layer of proof. Inside the compartment sat a gravity release valve assembly stamped with an architecture code NM4. Nathan explained that the letters stood for his own name and the number marked the fourth design revision developed after three earlier prototypes had failed under testing. Robert argued that initials on a part were not legal proof of anything. Nathan agreed.
He asked an engineer to connect a diagnostic scanner to the exposed system and said that if the signal wire had been reversed the way he believed, the display would show five fault codes in a specific sequence. He recited the first two codes aloud before the scanner even finished booting. The first code appeared exactly as he described. Then the second, the third, and the fourth followed in order. This was the second layer of proof.
Nathan understood behavior inside the system that no current manual could explain. Before the fifth code appeared, Daniel Brooks stepped forward from the pilot staging area. He had been watching from a distance, and now he studied Nathan's face for a long moment before speaking his name aloud. He's not a junior engineer, Daniel said to the crowd. Nathan built the fuel balance architecture for this aircraft.
During our first prototype flight, he caught an error the entire engineering team had missed. Daniel described how Nathan's gravity release system had once saved his life during an early test flight when the central computer stopped responding entirely and the manual bay was the only reason he brought the aircraft down safely. That was the third layer of proof. An independent credible witness who had flown the program from its earliest days. Audrey turned to Robert and asked why Nathan's name appeared nowhere in current company records.