Corporal Mason, who had been working nearby and had drifted closer during the repeated scans, looked over her shoulder at the screen. He was young enough that his curiosity still showed plainly on his face, and he leaned in with the eager attention of a technician who wanted to understand what his senior had seen. "What?" he asked.
Emily did not look away from the graph. She gestured, slightly, toward the trace, toward the place where the line had broken and reformed. "Look at this," she said.
Mason stared at the graph. He studied it the way Emily had taught him to study a reading, looking for the break, the spike, the deviation. After a moment, he shook his head slightly, honestly puzzled. "I don't see anything," he said.
"Exactly," Emily said. She pointed, her finger steady just above the screen, at the interval where the interruption had been recorded and then overwritten by the resumption of normal data. "The system says there was an external command."
Mason frowned, and Emily could see him working through what that phrase meant, turning it over in his mind the way she had turned it over in hers in the seconds after the first flicker. An external command was not a term to use lightly in maintenance. It did not mean a loose wire or a tired sensor. It meant an instruction that had come from outside the aircraft's own normal systems, an input that had no business being there, a voice in a conversation that was supposed to have only two participants. "External command from where?" he asked, and his voice was quieter now, the curiosity tempered by the first edge of unease.
"I don't know," Emily said, and she said it plainly, because she did not know, and because pretending otherwise would have been worse than admitting ignorance. She had no source to name, no location to point to, no neat explanation to offer. She had only a trace, a flag, and a pattern that was beginning to form in her mind with a clarity she did not welcome.
Mason looked from the screen to her face, searching for reassurance, for the senior mechanic's calm dismissal that would make this a non-event. "Could be a software glitch," he offered, and it was a reasonable offer, the kind of explanation mechanics reached for first when electronics behaved strangely, because software did glitch, because updates did introduce quirks, because sometimes a system hiccuped and then corrected itself and never did it again.
"Maybe," Emily said. She said it because it was possible, in the narrow, technical sense that many things were possible before they were investigated. But she did not believe it, and the reason she did not believe it was already taking shape as she stared at the sequence data and thought about what she knew about this aircraft's design. This was not a single-thread system where a stray pulse could wander through unchecked. This aircraft, like every military aircraft she had maintained for twelve years, was built with multiple redundancy layers, with cross-checks and backups designed precisely to catch and contain random faults. A random glitch did not behave like this. A random glitch did not hide and then reappear at will. A random glitch, above all, did not occur at exactly the same point in the diagnostic sequence, every time.
That was the detail that changed everything, and Emily felt it settle into her understanding with a cold, professional weight. The first interruption could have been dismissed as a fluke. The second and third runs, clean, could have been used to argue that the first was an artifact. But the third repetition, the one where it happened again, at the same point, in the same way, for the same brief duration, broke the fluke theory apart. Randomness did not repeat with that kind of precision. Precision meant design. Precision meant that something in the system was waiting for a particular moment in the sequence and then acting, briefly, deliberately, and then stepping back into silence. That meant someone had built a trigger into the system, or something had been placed there that functioned like a trigger, a hidden instruction that woke only when the diagnostic reached a certain point and then went quiet again before it could be caught in the act. Emily did not know who, and she did not know how, and she would not speculate beyond what the evidence showed, but she knew what the pattern meant, and she knew that a pattern like that could not be filed away as a software quirk and forgotten.