"Not that I know of."
Jonathan made a note.
"Did you notice anything unusual about the booking system this morning?"
Melissa looked up.
"Yes."
"What?"
"When I scanned your passport, the system froze for a second. Then it displayed a warning I hadn't seen before. It didn't look like the normal reservation screen."
"Did you tell anyone?"
"No. I thought it was a technical issue."
"Did anyone contact you after you rejected my booking?"
She hesitated.
"Yes."
"Who?"
"A person from the central service desk called me. They asked whether I had processed a passenger named Jonathan Reed."
Jonathan remained still.
"What did you say?"
"I said I had rejected the booking because the system showed a restriction."
"What did they ask you to do?"
"They told me to close the case and not make any further changes."
"Did they identify themselves?"
"They said they were calling on behalf of operations support."
"Did they provide an employee number?"
"No."
"Can you identify the voice?"
Melissa considered the question.
"I think it was a man, but I'm not certain. The line was noisy."
Jonathan thanked her and ended the interview. Melissa left the room with an independent investigator, who would document her statement and review her access history.
Andrew remained seated.
"You think I caused this?"
"I think we need to determine whether your performance instructions contributed to the problem. That is different from accusing you of deliberately compromising a security system."
Andrew rubbed his face.
"I was trying to improve the terminal's efficiency."
"Efficiency without accountability can become a mechanism for hiding mistakes."
"I didn't know anyone was manipulating bookings."
"Then help us establish how the process was abused."
Before Andrew could answer, Priya entered carrying a printed report.
"We found a link between the booking restrictions and the contractor payments."
She placed the report on the table.
A service account used by Northbridge Technical Services had been granted permission to access a passenger-processing support tool. That tool was intended for diagnosing software problems, but its configuration allowed certain users to place reservations into manual review.
The permission had been approved six months earlier.
The approving account belonged to a senior operations administrator.
Andrew looked at the name.
"That's Daniel Mercer."
"Who is he?" Jonathan asked.
"Director of Passenger Services. He oversees several terminal managers and the central service desk."
"Is he on site today?"
Andrew checked the staff directory.
"Yes. His office is on the third floor."
Jonathan studied the permission record.
"Who authorized the contractor's access?"
"The approval is recorded under the executive administration account," Priya said. "But the employee field is blank."
Another missing identity.
Another unexplained authorization.
Jonathan asked Priya to preserve the original permission configuration and identify every transaction processed through the support tool since it had been granted.
Then he turned to Andrew.
"Arrange a meeting with Daniel Mercer. Tell him we're reviewing the passenger-service system and need his help understanding the access permissions."
"Should I tell him about the unauthorized session?"
"Tell him only what he needs to know to attend the meeting. We have no reason to expose the entire investigation to someone whose role we have not yet verified."
Andrew nodded.
As he left, Jonathan's phone vibrated with an incoming message from an unknown number.
There was no greeting, no signature, and no explanation.
Only one sentence:
IF YOU QUESTION DANIEL MERCER, ASK HIM WHAT HAPPENED TO FLIGHT 608.
Jonathan read it twice.
Flight 608 had disappeared from the airport's internal departure archive three years earlier after a serious operational incident. The public report had attributed the event to a scheduling error and a communication failure.
But Jonathan remembered something the report had never explained.
The original investigation had been closed before all the relevant maintenance records were recovered.
He looked toward the operations display.
Flight 608 had been removed from the public schedule, but its historical record remained accessible to a small number of administrators.
Someone was trying to connect the current breach to an old case.
Jonathan sent the message to the independent investigation team.
Then he made a decision.
Before questioning Daniel Mercer, he would find out exactly what the airport had hidden about Flight 608.
Flight 608 had departed Westbridge Airport on a rainy evening three years earlier, carrying 184 passengers and seven crew members. It was scheduled to fly to Denver, with a brief stop in Kansas City. According to the official incident summary, the aircraft had experienced a departure delay caused by a disagreement between ground operations and the airline's scheduling department.
No passengers had been injured. The flight had eventually reached its destination. The event had been classified as a minor operational disruption, and the investigation had been closed within five days.
At the time, Jonathan had been a regional operations executive with responsibility for several airports but not Westbridge itself. He remembered the incident because it had triggered an unusual number of internal reports. Two employees had resigned shortly afterward, a contractor had lost its airport access, and a planned technology upgrade had been quietly postponed.
Yet the final report contained almost none of those details.
Jonathan sat alone in a small conference room, reading the archived summary on a secure terminal. The document had been prepared by the airport's operations department and approved by the former terminal director.
The first pages described the delay. The next pages summarized the communication failure. The final section recommended additional training and a review of departure coordination procedures.
There was no mention of missing equipment.
There was no explanation for the two resignations.
There was no record of the contractor whose access had been revoked.
Jonathan opened the attachment index.
Several files were listed, but three had been marked unavailable.
ATTACHMENT C: MAINTENANCE ACCESS LOGS.
ATTACHMENT F: EXTERNAL CONTRACTOR AUTHORIZATION.
ATTACHMENT H: PASSENGER PROCESSING EXCEPTION REPORT.
Each carried the same note: Archived under restricted administrative authority.
Jonathan attempted to open Attachment C.
A warning appeared.
ACCESS DENIED. RECORD REQUIRES SECONDARY APPROVAL.
He entered his executive credentials.
The system requested a second authorization.
That was unusual. As director of operations oversight, Jonathan had access to historical records needed for legitimate safety and compliance investigations. Certain records required additional approval because they contained sensitive personal information, but the maintenance logs should not have been restricted in the same way.