“The cabin crew is responsible for checking the passenger list before boarding.”
“Are they also responsible for diagnosing synchronization failures?”
“They're trained to recognize discrepancies.”
“And what should they do when a passenger presents a valid authorization that doesn't appear on the list?”
“Contact operations.”
“Was that procedure followed?”
Martin looked at the screen.
“Eventually.”
Victor let the silence continue.
He had learned over the years that people often revealed more when they were given enough time to hear their own incomplete answers.
Martin finally spoke.
“Look, the manifest system isn't perfect. We have occasional delays when devices lose their connection. Rebecca has a lot of experience. She believed she was working from the correct information.”
“Experience doesn't answer the question.”
“Victor, I'm not defending every word she said. But we need to keep this in perspective. No one was injured. The aircraft wasn't delayed significantly. The passenger boarded, and the flight departed.”
Victor studied him.
“Do you know who the passenger was?”
Martin looked uncomfortable.
“Monica Hayes.”
“Do you know what that means?”
“Obviously.”
“Then imagine if the passenger had been someone without access to the executive office. Imagine if she'd been an employee traveling to an important meeting, or a guest invited by one of our partners. She might not have had anyone to call. She might have left the airport believing she had made a mistake.”
Martin shrugged.
“She could have contacted the travel office.”
“She tried to get the crew to verify her authorization.”
“Rebecca was trying to maintain security.”
“Then why did she refuse to read the document?”
Martin did not answer.
Aaron cleared his throat.
“There's something else.”
Victor turned toward him.
“What?”
“The export was generated using the credentials of the operations support account.”
“Who has access to that account?”
“Four people in the department. Martin, two coordinators, and one technical administrator.”
Martin sat straighter.
“It's a shared account for routine support tasks. That doesn't mean I generated the file.”
“I didn't say it did,” Aaron replied.
“Then we shouldn't be implying anything.”
“We're not implying anything. We're examining the logs.”
Martin looked toward Victor.
“This is becoming excessive.”
Victor's expression hardened.
“No. What's excessive is treating a documented discrepancy as an inconvenience because the person affected happened to be able to reach the owner of the company.”
Martin fell silent.
Victor returned his attention to Aaron.
“Can we determine which workstation generated the export?”
“Possibly. The account is shared, but the export process records the workstation ID. I'm retrieving it now.”
Aaron entered several commands.
A list of system events appeared.
He scrolled, stopped, and leaned closer.
“Here it is.”
Victor stepped around the desk.
The event record identified a workstation in the travel operations office.
The time was 7:51:18 a.m.
Aaron opened the associated session record.
“Someone was logged into the operations support account at that workstation.”
“Can you identify the user?”
“Not from this record alone. I need the workstation's local sign-in history.”
Martin crossed his arms.
“That's probably just the morning backup process.”
“Was the backup process scheduled for 7:51?” Victor asked.
Martin hesitated.
“I'd have to check.”
“Then check.”
Martin picked up his phone.
For the next several minutes, the room filled with the sounds of typing and quiet conversation.
Aaron retrieved the local sign-in history. A named user account had accessed the workstation shortly before the manifest export.
The account belonged to a travel coordinator named Lauren Price.
Victor recognized the name.
Lauren had been with Hayes Meridian for three years. She was considered reliable, organized, and particularly good at resolving last-minute itinerary changes. She rarely complained, and her performance reviews consistently described her as conscientious.
Martin looked at the screen.
“Lauren works the early shift. She probably printed a backup copy.”
“Why would she print the outdated manifest?” Victor asked.
“Maybe the update hadn't reached her workstation.”
Aaron shook his head.
“The central record had been updated for nine minutes. The workstation was online. It had access to the revised version.”
Martin's expression changed.
“Then she may have selected the wrong file.”
“That's possible,” Victor said. “Has anyone asked her?”
“Not yet.”
“Then we should ask her.”
Martin rose.
“I'll bring her in.”
Victor held up a hand.
“Not yet.”
Martin looked annoyed.
“Why not?”
“Because I want the records preserved first. I also want the people involved interviewed separately. No one should be discussing what another person remembers before we establish what the system recorded.”
“You're treating this like a criminal investigation.”
“I'm treating it like an operational incident with an unexplained record discrepancy.”
Victor turned to Aaron.
“Make a read-only copy of the relevant logs. Preserve the original manifest, the revised manifest, the export file, the synchronization record, and the device status report.”
Aaron nodded.
“Anything else?”
“Any messages sent between travel operations and the cabin crew before boarding.”
“Understood.”
Victor looked at Martin.
“Once the records are preserved, we'll speak with Lauren. Then we'll speak with Rebecca and the ground coordinator. Separately.”
Martin's face remained tense.
“And what do we tell Monica?”
“The truth. That we're investigating.”
Martin glanced at his watch.
“She's probably already decided what happened.”
Victor shook his head.
“No. If she had decided, she wouldn't have asked us to preserve the records.”
That observation bothered him more than he wanted to admit.
Monica's patience was not a sign that she had forgotten the incident. It was a sign that she was allowing the company to establish the facts before drawing conclusions.
Victor knew she expected the same standard from herself.
He also knew that the investigation might expose failures in the department he supervised.
If the manifest system had failed, operations had not adequately managed a known technical risk.
If the file had been exported deliberately, someone might have interfered with a passenger authorization.
If the cabin crew had been trained to rely on the manifest without checking conflicting information, the problem extended beyond a single employee.
And if managers had ignored similar complaints in the past, the company could no longer pretend that the morning's incident was isolated.
Victor turned back to the screen.
“Let's find out what happened.”
Lauren Price arrived at the operations room at 9:36 a.m.
She was thirty-one, with shoulder-length brown hair and a nervous habit of twisting a silver ring around her finger. She wore a pale blue blouse and black trousers, and she carried a notebook filled with handwritten reminders.
When she entered, she looked from Victor to Martin, then to Aaron.
“Is something wrong?”
Victor gestured toward the empty chair.
“Please sit down, Lauren. We're reviewing the boarding manifest for this morning's Dallas departure.”
Her expression tightened.
“The Hayes flight?”
“Yes.”
“Did something happen?”
“We're still establishing that.”
Martin leaned forward.
“Lauren, did you generate a manifest export at 7:51 this morning?”
She looked surprised.
“I generate exports all the time.”
“Did you generate this one?”
Aaron turned the monitor toward her.
Lauren examined the event record.
After a few seconds, she nodded.
“Yes. That's my workstation.”
“Why did you export the older manifest?” Victor asked.
“I didn't know it was older.”
“The updated record was available in the central system.”
Lauren's fingers tightened around her notebook.
“I printed the list that was in the departure folder.”
“What departure folder?”
“The one Martin asked us to prepare for the morning flights.”
Martin frowned.
“I didn't ask you to use an outdated list.”
“I didn't say you did.”
“Then what exactly are you saying?”
Lauren looked between them.
“I was told to prepare a backup copy in case the tablets failed to synchronize. I opened the file in the folder and printed it.”
Victor kept his voice calm.
“Who told you to prepare the backup?”
Lauren hesitated.
Martin answered before she could.
“That is a standard task. We prepare backup copies every morning.”