The examiner asked how Elias had obtained the maintenance discrepancy before traveling. He described the anonymous package, the review office's authorization, and his decision to bring an independent copy. He explained which details were confirmed before arrival and which became known only after Nadia's live testimony and the ground test. He refused to claim that he had foreseen the precise malfunction. He had suspected record manipulation; the mechanical test supplied an independent finding.
After a recess, June testified. She wore a navy jacket she had bought for the occasion. She recounted the queue, the old ticket, the manual review warning, Victor Hale's arrival, and the tear. When asked why she did not intervene, she said she was a new employee afraid to challenge a senior executive. She did not embellish her answer. The chair thanked her for the candor.
Apex counsel showed her a screenshot of the restricted-archive access attributed to her at 12:11 a.m. on Saturday. The lawyer asked whether she had visited the archive at that hour. June said no. Ben Orlov was called to explain the duplicated session hash and delayed administrative import. He showed the panel how one event could appear as a second login in the modern directory. The access entry had not placed June at the workstation at midnight; it had preserved a misleading timestamp during reconciliation.
“Can the system generate a trustworthy chronology?” the chair asked Ben.
“Only if the raw event identifiers are preserved and interpreted correctly. The summary view alone was insufficient.”
It was the central problem of the case in miniature. A polished screen offered a clean answer. The underlying record offered a more complicated truth.
Nadia testified in the afternoon. She described the left actuator's irregular feedback, the original open discrepancy, and the closing record signed under Julian Reeve's retired identifier. Counsel asked whether the actuator fault would certainly have caused an accident.
“No,” Nadia answered. “The physical inspection found wear and inconsistent response. We cannot know what would have happened on that flight. We can know that the documented release was not supported by the required test.”
“If you cannot prove an accident was imminent, why should the delay be considered necessary?”
“Because airworthiness isn't decided by waiting to see whether a component fails in service. The rule requires evidence that a reported defect has been appropriately resolved.”
The chamber was still for a moment. June noticed an older mechanic nodding in the public seats. Nadia continued. She explained the difference between faulty data and a genuine physical indication, why an independent ground cycle mattered, and how an absent engineer's signature deprived the captain of information needed for his decision.
During a break, a reporter asked Elias whether the hearing would end with someone in handcuffs. He told the reporter that was not the purpose of the technical panel. Criminal matters were being reviewed separately by the relevant authorities. The panel was there to establish facts and issue safety measures. It would be irresponsible to turn those different processes into a promised ending.
At sunset, the chair dismissed the day's witnesses. Elias walked down the chamber steps past a cluster of microphones. In the morning he had been introduced as the man whose clearance stopped a plane. Now the transcript showed something less theatrical and more important: a traveler had raised a concern, an agent had preserved what she saw, an engineer had brought original measurements, and a pilot had acted on valid evidence. No single title had done the work.
June joined Elias at the bottom of the steps. “Were my answers enough?” she asked.
“They were accurate,” he said. “That's the standard.”
She watched people hurry along the sidewalk with their ordinary evening plans. There was relief in being judged not by the speed of her fear or the drama of the night, but by the record she had helped preserve after it mattered most.
CHAPTER 27
The Account That Signed For Everyone
On the second hearing day, the investigators projected a diagram of the Apex system. It was not beautiful. Lines ran between service accounts, maintenance reports, and old employee directories; arrows crossed in ways that made the audience squint. The lead forensic analyst, Dr. Priya Nair, spoke slowly so the panel could distinguish technical capability from proven use.
“The platform could recommend classification of a discrepancy,” she began. “It could not lawfully certify repair work on behalf of a human engineer. The disputed events occurred after a separate administrative script populated certification fields using credentials stored in a retired directory.”
She displayed the script's revision history. Damon Calder had created the first version to migrate old records. That legitimate purpose ended when the tool was modified to apply closure signatures after a human account became inactive. The modification allowed administrators to select a prior engineering identifier and write it into a current record without requiring the named engineer to authenticate the action. The corresponding event logs were marked as routine reconciliation. In Flight 706's case, the script attached Julian Reeve's identifier to a release issued while Reeve was at home sick.