"After Flight 608, someone began changing how system exceptions were handled. The official explanation was that the airport needed to improve efficiency. More decisions were centralized, more technical permissions were delegated to contractors, and fewer manual changes required individual approval."
"Who proposed those changes?"
"Martin supported them. So did the former terminal director."
"And you?"
"I supported the efficiency program. I didn't understand how much authority the new system would give the central service account."
Jonathan studied him.
"Do you still believe the changes were necessary?"
Daniel looked toward the terminal outside his window.
"Some were. But I don't believe anyone fully understood the risks."
"Then why didn't you ask for another review?"
"Because the airport was under pressure to reduce delays and costs. Nobody wanted to reopen a failure that had supposedly been resolved."
Jonathan stood.
"Pressure is not an excuse for ignoring a safety concern."
"No," Daniel said quietly. "It isn't."
As Jonathan reached the door, Daniel called after him.
"Mr. Reed."
Jonathan turned.
"If you're going to investigate Flight 608, speak to Priya before you confront Martin. She may have kept records that nobody else has seen."
"Why?"
"Because she was the one who discovered the original discrepancy. And because she was the last person to see the complete maintenance logs before they disappeared from the archive."
Jonathan left the office carrying the folder.
In the corridor, he contacted Andrew and asked him to arrange an independent interview with Priya. He also instructed Elena to verify every document in Daniel's folder against the airport's archived records.
The investigation was becoming clearer, but the implications were growing more serious.
Northbridge had been involved in the original incident and the current network breach. Martin Hale had participated in the earlier investigation and controlled security authorizations today. Daniel Mercer had approved changes that weakened the separation between passenger processing and technical support.
None of those facts, individually, proved criminal conduct.
Together, however, they suggested that the airport had repeated a mistake it had never fully understood.
Jonathan's phone rang.
It was Elena.
"We've authenticated the first two pages of Daniel's folder," she said. "They match the archive. But the handwritten note on the maintenance discrepancy has been removed from the official version."
"Can you identify when?"
"The metadata shows the report was revised six days after the original investigation closed."
"Who revised it?"
"That's the problem. The edit was made through a shared administrative account."
Jonathan stopped walking.
"Can you recover the revision history?"
"Yes. And there's something else. The account used to make the edit was also used to restrict the records you tried to open this morning."
Jonathan stared down the corridor.
"Can you identify the person who controlled that account?"
"Not yet. But I've found a message attached to the revision history. It wasn't included in the report."
"What does it say?"
Elena paused.
"Three words."
"Tell me."
Her voice dropped.
THE SECOND VALIDATION.
Jonathan felt the same chill he had experienced when the airport system first displayed the unauthorized session.
"Is there a timestamp?"
"Yes. It was entered the night before Flight 608 departed."
"Send me the authenticated copy."
"I already have."
Jonathan ended the call and looked toward the terminal windows. Outside, aircraft moved slowly between gates while ground crews prepared the next departures.
The airport appeared orderly. Its schedules were running, its systems were reporting normal status, and thousands of people trusted the institution to move them safely from one destination to another.
Yet someone had been preparing for a second validation for three years.
And the person who sent the anonymous message had known Jonathan would arrive just in time to witness it.
He opened Elena's file.
At the bottom of the recovered record was a line that had not appeared in any previous report.
VALIDATION TWO WILL REQUIRE A LIVE EXECUTIVE CREDENTIAL.
Jonathan read it again.
Then his phone vibrated with a new message from the unknown sender.
NOW YOU UNDERSTAND WHY THEY NEEDED YOU HERE.
A second message followed.
DO NOT LET THEM RUN THE TEST AT NOON.
Jonathan checked his watch.
It was 11:48 a.m.
He turned and hurried back toward the operations room.
Whatever the second validation was, someone intended to activate it in twelve minutes.
And this time, the airport might not be able to hide the consequences.
At 11:48 a.m., Jonathan Reed returned to the operations room with Elena Morris's warning still glowing on his phone. The message was brief, but its implications were enormous. Someone intended to use a live executive credential to perform a second validation at noon, and the same person had somehow connected that plan to an incident buried in Westbridge Airport's records three years earlier.
Jonathan found Andrew Collins standing beside Priya Shah, who was examining a set of maintenance logs on a secure workstation. Martin Hale was nowhere to be seen.
"Where is Hale?" Jonathan asked.
Andrew looked up. "He said he needed to speak with the security team. That was about five minutes ago."
"Did he say where he was going?"
"No."
Jonathan showed Andrew the anonymous message.
DO NOT LET THEM RUN THE TEST AT NOON.
Andrew read it twice. "Do we know what the test is?"
"Not yet. But we have less than twelve minutes to find out."
Priya turned away from her screen. "I may know."
Jonathan approached her. "Tell me."
She opened an archived technical document that had been recovered from the original Flight 608 folder. Most of the text described an experimental synchronization process designed to verify that passenger records, departure schedules, and airport access permissions remained consistent across separate systems.
The procedure was called Executive Validation Protocol Two.
Three years earlier, the first validation had been scheduled to run in a controlled environment. Instead, the test equipment had apparently communicated with the live operations network. The resulting configuration error had delayed Flight 608 and triggered an investigation that was eventually closed without a complete explanation.
"What does the second validation do?" Jonathan asked.
"It compares the authority recorded in the airport's administrative systems with the authority recognized by the connected operational systems," Priya explained. "In simple terms, it checks whether the same person has the same permissions everywhere."
"And why would it require my credentials?"
"Because the protocol was designed to verify executive-level permissions. It needs an authenticated account with enough authority to approve the comparison."
Jonathan studied the document.
"Could it change anything?"
"It shouldn't. The original specification says the process is read-only. But that assumes the software and its permissions have not been altered."
"Have they?"
Priya hesitated.
"I don't know. The original validation failed before the final test could be completed. Afterward, the software was modified, but I never saw the final configuration."
Jonathan checked the time. Eleven fifty.