Not an engineer. No. He described himself as a certified aircraft mechanic with experience in integrated avionic systems. He had some additional training. He mentioned I wrote it down.
Marcus checked his phone. He said he spent 3 years doing software integration diagnostics for a regional carrier before he transitioned to independent maintenance work. Why did he transition? Marcus hesitated. Personal reasons.
He said his wife passed away. He has a daughter. He needed a different kind of schedule. Amelia looked at the aircraft through the glass. She had been looking at it for a week and a half, and she still felt the same low-level anger every time she saw it sitting there silent and perfect and immovable.
"Send him in," she said. Daniel Carter was not what she expected, though she had stopped expecting specific things from people the day she realized that expectations were a form of assumption, and assumptions were the enemy of accurate judgment. He was 41 years old, medium height, with the kind of hands that belonged to someone who worked with them everyday. He was carrying an old toolbox, the kind with layers of stickers from trade shows and aviation conferences that had accumulated over years of use. His jacket had a company logo on the breast pocket that she did not immediately recognize.
He did not apologize for being there. He did not explain himself at length. He looked at her and said, "I heard about the reward. I am not here for the money. I am here because I think I know what nobody has found yet. " She appreciated the directness.
She had learned over 20 years that the people who spent the first 3 minutes of a conversation explaining why they deserve to be in the room almost never deserve to be in the room. All right, she said, "Tell me what you think. Before I do, I want to ask you one question. " He looked at the window at the aircraft visible through the glass. The software update that was installed before the problem started. What specific version was it?
And was it a standard manufacturer release or was it a customized package? The room shifted. Amelia noticed it immediately because she always noticed the specific quality of silence that occurred when someone asked a question that cut directly to something important. Marcus glanced at her. Two of the engineers who had been standing near the door made the particular kind of stillness that meant they were paying attention now in a way they had not been before.
She pulled up the technical file on her laptop and turned it toward him. Version 4.7.2 customized integration package. The customization was done by a third-party contractor to address specific communication requirements between the aircraft management system and our company specific scheduling and operations software. Daniel looked at the screen. He did not touch the laptop.
He read in silence for approximately 30 seconds and then he looked up. Who built the customized package? A company called Vertex Avionic Solutions. They have done contract work for us for 4 years. I know them.
Daniel said it was a simple statement without elaboration, but something in the way he said it made her pay attention. I worked on a diagnostic for a regional carrier 3 years ago. The carrier had installed a Vertex customized integration package and experienced startup failures that did not show up in standard diagnostics. The automated systems reported nominal across the board. The actual problem was a miscommunication loop in the startup command architecture.
The system was receiving conflicting instructions simultaneously and because both instructions were technically valid, neither one executed. That was resolved. Yes, but it took finding someone who was willing to stop trusting the automatic reports and go into the raw command history manually. Most of the diagnostic tools used for this kind of aircraft are built to present information in organized readable formats. The formatting itself can obscure what is actually happening in the underlying code.
You have to look at the raw data to see where the commands are breaking down. She watched him for a long moment. She had heard confident explanations before. She had heard confident explanations that turned out to be wrong before, sometimes expensively wrong. The confidence itself was not what she was evaluating.
She was evaluating the specificity of what he was saying and whether it addressed a gap that she had already identified but not yet been able to name. The gap was this. Every expert who had come into that hanger had trusted the diagnostic systems to tell them where to look. And the diagnostic systems had told them everything was fine. She had wondered lying awake at 3:00 in the morning whether the problem was not just inside the aircraft, but inside the tools being used to find it, whether the instruments they were using to search were themselves part of the same flawed system.
Daniel Carter, standing in her office with an old toolbox, had just said the same thing. "What do you need? " she asked. He told her. A direct data connection to the aircraft management system. Access to the raw command logs rather than the formatted diagnostic outputs.
Time and no one standing over his shoulder telling him what he was supposed to find. The last condition made three of the engineers in the room straighten with visible irritation. Dr. Raymond Hol, who had been the most senior of the remaining consultants and who had made clear in his first meeting with Amelia, that he had 40 years of experience in aviation systems and had personally consulted on incidents that had made international news stepped forward from the side of the room where he had been standing. I need to object to this.
Holt said he was addressing Amelia, but his eyes moved to Daniel with the particular quality of dismissal that required no words to communicate. We have highly qualified engineers who have been systematically working through this problem for days. Allowing an unlicensed technician to access the aircraft management system without oversight is not only potentially damaging to the investigation, it is a liability issue. Hi, as a certified aircraft mechanic, Amelia said with avionic systems, this complex certification as a mechanic does not qualify someone to access integrated management software. He could corrupt data.
He could introduce new errors. He could make the problem significantly worse. Amelia looked at Hol. She looked at him for long enough that the silence became its own kind of statement. Dr.
Holt, she said, in 40 years of experience, have you personally encountered a startup failure of this specific type? A pause. The type of failure is not yet confirmed. That is not what I asked. Another pause.
Shorter this time because he understood where this was going. The specific combination of factors here is unusual. So the answer is no. He said nothing. She turned back to Daniel.
You will have Marcus with you at all times for documentation purposes. You will have access to what you need. If at any point it appears that your approach is creating additional problems, I will stop you. Those are the terms. That is fair, Daniel said.