He remembered checking the aircraft and seeing the passenger waiting beside the boarding stairs.
He remembered Richard approaching her.
At first, Marcus had assumed there was a documentation issue.
Then he heard the captain ask whether she was the type of passenger who normally used that aircraft.
Marcus had thought the wording was inappropriate.
He had not said anything.
"Why not?" Samuel asked.
"Because I was ground staff. I wasn't responsible for passenger verification."
"Did you believe the captain had a legitimate security concern?"
"I didn't know. I wasn't in the dispatch system. But the ground team had already checked her."
"Did you tell anyone?"
Marcus looked uncomfortable.
"No."
"Why?"
"Same reason most people don't. You don't want to be the person who creates a problem between departments."
"Did you think the passenger was treated differently because of her appearance?"
Marcus hesitated.
"I thought the captain made assumptions."
"Can you explain?"
"She was young. She was alone. She didn't look like some of the people who usually arrived with assistants and luggage. I think he expected a different kind of passenger."
"Did you see him apply the same scrutiny to passengers who arrived with assistants?"
"Not that I remember."
Samuel asked whether Marcus had ever heard the phrase "profile mismatch."
Marcus nodded.
"People said it sometimes."
"Who?"
"Some crew members. A few ground staff."
"What did they mean?"
"Usually that a passenger didn't look like the person they expected to see."
"Was that an official term?"
"No. Not that I knew."
"Did anyone tell employees to use it?"
Marcus shook his head.
"Not directly."
"Did anyone tell them not to use it?"
Marcus considered the question.
"No."
Dana wrote that down.
When the interview ended, Marcus asked whether his statement would be shared with Richard.
"Not as an unrestricted document," Dana said. "The review team will use the information according to the investigation process. If a finding requires a response from an employee, that employee will receive enough information to answer it fairly."
Marcus nodded.
"I just don't want to lose my job because I told you what I heard."
Samuel replied, "You should not have to choose between being honest and keeping your job."
Marcus looked at him.
"That's what I hope."
The passenger interviews changed the tone of the investigation.
Before them, the spreadsheet had been a collection of questionable entries.
Now it was clear that the entries represented experiences the company had failed to understand.
But Dana remained cautious.
She did not want the review to become a search for stories that confirmed an early suspicion.
She requested a broader sample.
The team examined passenger-verification events across the previous eighteen months, comparing them against flight type, route, booking method, documentation status, and the recorded reason for additional checks.
They also reviewed cases involving passengers who had arrived with assistants, corporate representatives, or visible security personnel.
The purpose was not to assume that one group should be treated as the standard.
It was to determine whether the same objective criteria had been applied consistently.
The results were incomplete but concerning.
In cases involving an actual discrepancy, additional verification was common across passenger categories.
That was expected.
But among cases without a documented discrepancy, some passengers had received additional scrutiny based on descriptions of appearance, age, or perceived status.
The team also found that the phrase "profile inconsistency" appeared disproportionately in entries involving passengers who arrived alone or without visible corporate representatives.
That did not prove discriminatory intent.
It did demonstrate that the company had allowed subjective impressions to become part of the verification process without clear safeguards.
Dana summarized the findings at a second review meeting.
"We have enough evidence to identify a systemic control weakness," she said. "We do not yet have enough evidence to determine every individual's intent."
Avery nodded.
"Explain the distinction."
"Security verification should begin with a specific concern. A name discrepancy. An expired credential. An unexpected passenger substitution. A booking authorization issue. Something that can be described and checked."
"And the problem?"
"The informal category allowed the process to begin with a subjective impression. The records then treated that impression as if it were a legitimate operational reason."
Elena looked troubled.
"So the captain could write that a passenger did not look right, and the company would record that as a verification event."
"Correct."
"Even when the booking was valid."
"Yes."
Jonathan asked, "How widespread was it?"
"We have confirmed thirty-seven entries in the informal spreadsheet. We have identified additional references in emails and local notes. We are still reviewing those."
Avery looked toward the window.
"How many passengers complained?"
"Only two formal complaints directly connected to the category have been located."
"How many informal concerns?"
"At least four employee accounts and three passenger accounts so far."
Avery turned back.
"That difference matters."
Dana nodded.
"It does. A low complaint count cannot be treated as proof of a low incident rate when the reporting system itself discouraged complaints."
Samuel added, "We have also identified employees who believed that challenging certain captains could harm their schedules or evaluations. We are still testing those claims."
Avery closed her notebook.
"Then the next step is to establish who knew what, when they knew it, and what they did."
Dana agreed.
"That's where the investigation is going."
Richard Halston was interviewed the following Monday.
He arrived without a representative but was informed that he could request one.