"Most were resolved after the passenger's identity was confirmed through ordinary records."
"How long were they delayed?"
"That varies. Some were resolved in less than five minutes. Others took considerably longer."
Dana opened a second table.
"Nine involved delays exceeding twenty minutes. Three exceeded forty minutes."
Avery looked at the dates.
One entry was from seven months earlier.
Another was from five months earlier.
A third had been recorded only six weeks before the incident on the ramp.
"Who reviewed these?"
Dana pointed to a column.
"Regional management."
"Martin?"
"Mostly."
"Did he approve the classification?"
"In twenty-nine cases, yes."
Jonathan sat back.
"Why was this never brought to flight operations?"
Elena answered carefully.
"Because the category wasn't part of the official reporting taxonomy. It existed in a regional spreadsheet. It wasn't automatically escalated to my department."
Avery looked at her.
"Did you know about the spreadsheet?"
"No."
"Did anyone in your department receive a copy?"
"Not according to the distribution records."
Dana added another document to the screen.
"That is important. The company had an official process for recording verification exceptions. But someone created an additional informal category outside that process."
"Was it used to hide incidents?" Jonathan asked.
"We don't know yet."
Dana closed the spreadsheet.
"It may have been intended as an informal management aid. It may have been created because regional staff believed the official categories were inadequate. It may also have allowed subjective judgments to be recorded without triggering the same review requirements as formal verification exceptions."
She paused.
"We need to interview the people who used it."
Avery looked at the spreadsheet again.
Thirty-seven rows.
Thirty-seven moments when a passenger had stood beside an aircraft and been judged before the company had established whether there was a real problem.
She thought about the woman Claire had described.
Evelyn Brooks.
She wondered how many other passengers had left the aircraft believing they had somehow failed a test they had never been told they were taking.
"Please identify every passenger involved," Avery said. "But do not contact anyone until we have established the appropriate privacy procedure. We will not expose their travel information simply because we are investigating."
Dana nodded.
"Agreed."
"And I want the same standard applied to everyone. If a passenger was delayed for a legitimate reason, we should say so. If someone was treated unfairly, we should say that too."
Samuel Price closed his notebook.
"That will make the findings more credible."
Avery looked around the table.
"Then let's make them credible."
Martin Keene received the meeting invitation on Thursday morning.
The message was brief.
It informed him that an independent review team wanted to discuss regional passenger-verification practices, including the use of internal tracking categories and the handling of employee concerns.
It did not accuse him of misconduct.
It did not mention Avery's name.
It did not identify Richard Halston as the sole subject.
Martin read it twice.
Then he called his assistant.
"Who authorized this?"
"The invitation came from the external review team."
"Who requested it?"
"The audit committee."
Martin was silent.
"All right. Put it on my calendar."
After ending the call, he opened the spreadsheet he had created eleven months earlier.
He remembered why.
At the time, several captains had complained that the official verification process did not give them a practical way to record situations in which they felt a passenger did not match the information available to them.
Martin had wanted to understand whether those situations were creating delays.
He had created the category as a temporary management tool.
He had not considered it a policy.
He had not asked legal counsel to review it.
He had not submitted it to flight operations.
He had also not deleted it when the original purpose was finished.
That decision now seemed considerably more important.
He opened the file.
Thirty-seven entries.
Some of the notes were written by captains. Others had been added by his staff.
Martin began reading.
When he reached the entry involving Evelyn Brooks, he stopped.
He remembered the conversation with Claire.
She had called him after the flight, concerned that Richard had questioned a passenger whose name was clearly listed on the manifest.
Martin had been dealing with a staffing shortage and two delayed aircraft.
He remembered telling Claire that Richard was experienced and that passengers sometimes interpreted routine security questions as personal criticism.
He had thought he was calming a minor workplace disagreement.
He had not asked for the passenger's account.
He had not reviewed the manifest.
He had not checked the flight report.
He had not even asked Claire whether the captain had followed the required procedure.
He had closed the conversation.
Martin leaned back.
For the first time, he considered that the spreadsheet might not merely contain questionable classifications.
It might contain the evidence of a problem he had helped prevent the company from seeing.
The next morning, Dana and Samuel interviewed Martin.
The meeting took place in a separate office, away from the main executive floor.
Martin arrived wearing a navy suit and carrying a leather folder.
He greeted both investigators politely.
"Before we begin," he said, "I want to make sure I understand the purpose of this meeting."
Dana explained the scope.
"We are reviewing passenger-verification practices, the informal use of the category 'profile inconsistency,' and the handling of concerns raised by crew members."
Martin nodded.