He explained each step to Marcus as he performed it, not because Marcus asked him to, but because he understood that documentation mattered, and that clear documentation was the difference between a fix that held and a fix that no one could reproduce when the next problem came. He was the kind of person who thought about the next problem before the current one was resolved. Priya Sahani sat close enough to see the screen, but far enough to stay out of his way. She she had not said much in the two hours since the others left, but she was writing a separate notebook, not her company tablet, a small paper notebook with a blue cover that she kept in the inner pocket of her jacket. Amelia noticed it because she noticed everything, and she noticed that Priya was writing faster now than she had been writing an hour ago.
The first verification test completed at 7 minutes 4 in the afternoon. The startup sequence initiated. The individual systems reported readiness in the correct order and then instead of simply stopping the way it had stopped every time for nine days, the authorization command passed through the integration layer, received its confirmation from the now cleared scheduling flag and arrived at the engine control unit. The sequence paused. Everyone in the room held their breath.
Then the sequence completed. Not with the engine starting. That was the next step. Not this one. But the startup sequence completed for the first time in 9 days.
All the way through. All the way to the point where a crew would give the command to bring the engines to life. Marcus let out a breath that he had apparently been holding since the sequence began. Priya closed her notebook. Daniel looked at the screen for a long moment before he said anything.
"That is step one," he said. "We are nowhere near done. " Marcus looked at him with the particular expression of a man who had expected relief and received instead a continuation. What do you mean the sequence completed? The sequence completed once under controlled conditions with no load on the systems. That tells me the primary fix is correct.
It does not tell me whether there are secondary effects from 9 days of failed attempts in the system logs. It does not tell me whether clearing the flag created any downstream conflicts in the scheduling integration and it does not tell me the most important thing which is Daniel turned away from the screen and looked at Marcus directly. It does not tell me how this happened. Not technically I already know that. I mean how this happened inside your organization because what I found in those prior incident logs is not something that should have survived long enough to become this problem.
The room changed. It was the second time in the same day that Amelia had felt the specific atmospheric shift that came when a conversation moved from the technical to the personal, from the system to the people inside it. Explain that. She said there were three prior flag conflict events in the raw logs. Short duration, each one self-resolved before causing a full startup failure.
That is what the raw data shows. But self-resolving events in an integrated system are not nothing. They are signals. Any competent systems review should have flagged them as a pattern worth investigating before a major software update was approved. Are you saying the prior events should have been reported?
I am saying they were available to anyone who looked at the right data. Whether they were reported is a different question. Whether the person who signed off on the Vertex integration package ever looked at that data is another question. And whether the person at Vertex who delivered the package had knowledge of similar incidents in other installations and chose not to disclose. It is the question that I would be asking very seriously if I were you.
The silence this time had a different quality than the earlier silences. Earlier silences had been the silence of people absorbing technical information. This was the silence of people calculating consequences. Marcus put both hands flat on the surface in front of him, a gesture that Amelia recognized as his version of studying himself. You are describing the possibility of negligence.
I am describing data, Daniel said. What it constitutes legally is not my field. What it means practically is that your aircraft did not simply develop a problem. Your aircraft developed a problem that someone somewhere had information that could have prevented. Amelia was already reaching for her phone.
She stopped herself. The communications records she had asked Marcus to pull would take time. Acting before those records were in her hands was a mistake, and she had not built a billion-doll company by acting before she had the evidence to act on. She put the phone back in her pocket. "Continue the verification," she said to Daniel.
"All of it. Every test you would run before you would be comfortable putting a crew on that aircraft. " He nodded and turned back to the laptop. She walked to the window and she stood there and she let herself think, which was something she had not allowed herself to do properly since the problem began because thinking required accepting uncertainty. And she had been too focused on demanding resolution to accept that the uncertainty was real. What she was thinking about was not the aircraft.
The aircraft was being fixed. What she was thinking about was the way problems grew inside organizations. She had built this company carefully and she had believed that the structure she had built was one that surfaced problems early. She had believed that the people around her would tell her what she needed to know. She had believed that the reporting systems and the communication channels and the culture of accountability she had worked to create over 20 years would mean that something like this would never become the size it had become before she knew about it.
And what she was standing at the window understanding slowly and with the particular discomfort of a person whose self-image is being revised in real time was that she had been wrong. Not about the reporting systems, not about the channels, about the culture, about whether the people around her felt genuinely safe bringing her information she did not want to hear. She had spent 20 years being the person who had answers. She had spent 20 years being right more often than she was wrong. And she had not understood until this moment watching a single father with an old toolbox do in 4 hours what 11 credentialed experts had failed to do in 9 days.
That being right most of the time could itself become a kind of barrier that people who worked for someone who was always right eventually stopped bringing her the things that might make her wrong. It was not a comfortable thought. She stayed with it anyway because she had also spent 20 years believing that the most important things were rarely comfortable. Across the room, Daniel ran the second verification sequence. Outside the building, something else was already happening, though nobody in the hanger knew it yet.
Dr. Raymond Hol had left the building 3 hours ago with the particular bearing of a man who had been insulted and intended to make that insult meaningful. He had made two phone calls from the parking area. The first was to the senior partner at the consulting firm that had sent him to Sterling Aviation. The second was to a contact at a competing aviation consulting group who owed him a professional debt of long-standing.
What he had said in those calls was not recorded. What happened as a result of them would become relevant later. For now, what mattered was that 3 hours after Daniel Carter cleared the maintenance flag and began the verification sequence, an attorney representing Vertex Avionic Solutions placed a call to Sterling Aviation's legal department. The attorney's message was brief. Vertex had become aware that a non-contracted individual was accessing Sterling Aviation's aircraft management system without appropriate certification.
Vert. Ex wished to note that any conclusions drawn from raw system data by an uncertified analyst could constitute a misinterpretation of proprietary integration architecture. Vertex further wished to note that their integration package had been installed in full compliance with all contractual specifications. If Sterling Aviation had concerns about the performance of the package, those concerns should be directed through the proper contractual dispute channels. The call was logged.
The log reached Amelia's executive assistant at 4:47 in the afternoon. Her assistant, who had worked for her for 9 years, and understood the difference between information that could wait and information that could not walked directly to the hangar. Amelia read the message on her assistant's phone, standing 10 ft from Daniel Carter, and she understood immediately that the call was not about certification. The call was about the prior incident logs. Someone at Vertex had been told that Daniel had found them and Vertex was already building its defense.