“I was ordered not to,” she said. “That seemed like a reason to come.”
She spread the strip beside the disputed release. Under a portable magnifier, the diagnostic trace resembled a thin mountain range interrupted by a sharp white valley. At the moment the left flap actuator reached its commanded position, the feedback sensor dropped and recovered. The equipment had stored the same behavior three times.
“A single anomaly can be noise,” Nadia explained. “Three identical events demand investigation. We needed a physical inspection and a ground cycle. I signed it open.”
“Yet the release shows Reeve closing it,” Tessa said.
“He was home sick. And look at his staff identifier.” Nadia pointed to a number. “It was retired after he changed departments. The new platform should have rejected it.”
Elias compared the timestamp to the network's event ledger. “Not if the person entering it was using a service account that bypasses the ordinary checks.”
Hale straightened. “You are speculating about a contractor's software in the presence of junior employees.”
“Then we should get the contractor to explain its audit trail,” Elias replied.
Tessa called Julian Reeve on a recorded line. He answered in a rasping voice that made his illness convincing even before he denied having signed anything. He said his tablet had been collected for a routine upgrade on Monday. He had never seen the replacement. When Tessa asked whether he would provide a statement, he said yes without hesitation, then asked if Nadia was safe.
That question changed the mood of the room. This was no longer only a dispute about a faulty part. Someone had been anticipating objections, collecting devices, and assigning signatures to people who could not defend them.
Nadia reached into her pocket for a second slip of paper. “Owen Price told me seven other findings were closed this week. I have the aircraft numbers. I wrote them down because I knew I would forget one.”
Six were regional jets. The seventh was a wide-body scheduled to leave the next morning. Elias read the list and pressed the pages flat with both palms.
“Captain Lin,” he said, “we need those seven maintenance histories preserved now.”
Tessa contacted control and requested an expanded preservation order. Her voice remained calm while the legal officer on the line protested that a single discrepancy could not justify suspending an entire fleet. She agreed. She was not asking to suspend the fleet. She was asking that records be made immutable until qualified inspectors could compare original and revised entries.
Hale watched every word as if calculating its cost. Finally he spoke. “You're going to destroy an airline over a software transition.”
June asked, “If the change is innocent, why are you afraid of keeping the old records?”
For the first time, Hale did not have an answer ready. He turned his gaze toward her employee badge and memorized the name printed there. June felt the familiar desire to apologize for speaking. She did not.
A chime interrupted them. Captain Rusk's independent ground test had started. Through the service-room monitor they watched aircraft M-448 become the subject of a live technical report. The testing team had disconnected the new maintenance platform from its ordinary data feed. Any measurements would be taken directly from the aircraft and witnessed by two engineers.
Nadia remembered the first time she had signed a maintenance release. Her supervisor had made her inspect the equipment twice and asked what evidence could change her conclusion. The exercise took more time than she wanted. Later she understood why it mattered: good engineering made room for new facts. The problem with the new system was not merely that it gave quick answers. It trained people to confuse speed with confidence and confidence with proof. She thought about the engineers who would come to work tomorrow and open their dashboards. Some would be suspicious now. Others would want the inconvenience to end. Her responsibility was to give them reliable measurements and an honest explanation, even if her own career suffered. That was how technical trust was rebuilt, one open question at a time.
Nadia leaned toward the screen. “That's what should have happened three hours ago.”
Elias said nothing. His eyes stayed on the line that showed the left flap. Its displayed position was nearly stable. Nearly, in aviation, was sometimes an invitation to ask one more question.
CHAPTER 07
The Man Who Built The Warning
Elias had designed the first version of the Continuity Review system nineteen years earlier. Back then, aircraft maintenance records were spread among paper binders, isolated terminals, and engineering offices that sometimes disagreed about the same machine. A badly timed computer outage could leave people unable to prove what had been done. He wanted a fallback that no single company could quietly alter. His design was modest: signed evidence copies, independent time receipts, and an emergency procedure that alerted both operators and reviewers when a privileged record was destroyed or denied.