He checked the access policy.
The restriction had been added eighteen months earlier.
The approving account belonged to Daniel Mercer.
Jonathan leaned back in his chair.
The anonymous message had not been a random attempt to frighten him. Someone wanted him to examine an old incident, and the person who controlled access to the relevant records was the same administrator whose department had overseen the passenger-service system now under investigation.
He called Elena.
"Can you access the historical records for Flight 608?"
"Not directly," she replied. "The archive is controlled by Westbridge's administrative system. Why?"
"Three attachments have been restricted under Daniel Mercer's authority. The restrictions were added long after the incident."
"That sounds deliberate."
"It might be. I want to know whether the archive was modified or whether the documents were simply moved to a restricted category."
"I'll request an independent audit of the archive metadata. Don't try to bypass the restriction yourself. We need to preserve the access controls as evidence."
"Agreed."
After the call, Jonathan contacted Andrew and asked him to arrange a meeting with Daniel Mercer. He also requested the original Flight 608 report, including all attachments and revision histories, be preserved before anyone made further changes.
Andrew replied that Daniel was available at eleven thirty.
Jonathan arrived at the passenger-services office ten minutes early. The department occupied a bright floor overlooking the terminal, with glass-walled meeting rooms and a reception desk displaying the airport's customer-service awards.
A framed statement hung on the wall:
Every passenger deserves respect, safety, and reliable service.
Jonathan read it while waiting.
The words seemed increasingly disconnected from what he had witnessed that morning.
At eleven thirty, a receptionist led him into Daniel Mercer's office.
Daniel was in his late forties, with neatly combed hair and an expensive watch. He wore a tailored suit and spoke with the smooth confidence of a manager who knew how to make difficult questions sound unreasonable.
"Mr. Reed," he said, rising to shake Jonathan's hand. "This is an unexpected honor. I heard there was a small incident at check-in. I'm sorry you experienced an inconvenience."
"Thank you. I appreciate your time."
Daniel gestured toward a chair.
"I understand the reservation system gave you trouble. Those things happen. We're already reviewing the technical issue."
"How did you hear about my reservation?"
Daniel paused for only a moment.
"Andrew mentioned that there had been a complaint."
"Did he tell you my booking reference?"
"I don't believe so."
"Did he tell you that the system displayed my executive clearance?"
Daniel's smile became less certain.
"No. He didn't."
Jonathan placed a printed transaction record on the desk.
"Then perhaps you can explain why your department's service account applied a manual restriction to my reservation at 8:11 this morning."
Daniel glanced at the paper.
"That doesn't necessarily mean anyone in my department made the change. Automated tools sometimes process restrictions without direct employee involvement."
"That's possible. The audit record shows that the restriction was initiated through a support tool your department administers."
"Which is why the technical team should investigate it."
"They are investigating it. I'm asking you to explain the permissions."
Daniel folded his hands.
"Several years ago, we introduced a centralized support system to help resolve reservation discrepancies. It allows authorized technical personnel to flag records for review. The system is secure, and access is limited."
"Who approved the permissions granted to Northbridge Technical Services?"
Daniel's eyes moved briefly toward the document.
"Northbridge was an approved contractor."
"That wasn't my question."
"The approval would have gone through the relevant procurement and security processes."
"Do you remember authorizing it?"
Daniel shook his head.
"I approve many operational requests. I can't be expected to remember every one."
Jonathan placed a second document beside the first.
It was the authorization record showing that Northbridge's account had been granted access to the passenger-processing support tool.
The approving account was listed as executive administration, with no employee identification.
Daniel studied the page.
"That record is incomplete."
"Yes."
"Then it cannot establish who approved the access."
"Correct. Which is why I'm asking for your help identifying the person responsible."
Daniel leaned back.
"You should speak with the technology department. They manage the system configuration."
"I will. But your name appears on the historical archive restrictions associated with Flight 608. I would also like to understand why."
For the first time, Daniel's expression changed completely.
"Flight 608?"
"Three years ago. A departure delay, a contractor access issue, and several missing attachments in the final report."
Daniel's fingers tightened around the armrest.
"That incident was investigated and closed."
"The report doesn't explain why three attachments were later restricted."
"They may contain confidential information."
"The restrictions were added eighteen months after the incident. Who requested them?"
"I don't remember."
"Was the restriction connected to a legal claim?"
"Not that I recall."
"Was it connected to a security investigation?"
Daniel stared at him.
"Mr. Reed, with respect, I don't understand why we're discussing an old incident when the immediate issue concerns a reservation system."
"Because the person using my credentials may have accessed the same maintenance and passenger-processing systems involved in that incident."
Daniel said nothing.
Jonathan waited.
Finally, Daniel stood and walked toward the window.
"Flight 608 was more complicated than the summary suggests," he said.
"How?"
"There was a contractor involved in a technology trial. The contractor was testing a new way to coordinate departure data between the airport and the airline."
"Which contractor?"
"Northbridge."
Jonathan felt a knot form in his stomach.
"Was the missing network equipment connected to that trial?"
"I don't know."
"Was the trial authorized?"
"It had preliminary approval."
"Was it approved for live operations?"
Daniel turned around.
"Not initially."
"What happened?"