Claire considered the request.
"Would I be allowed to disagree with you?"
Avery smiled faintly.
"Especially then."
"Then yes."
Avery thanked her.
The meeting lasted less than thirty minutes.
But when Claire left, she carried something she had not possessed when she entered the aircraft hangar months earlier.
Not certainty.
Not victory.
Something smaller and more useful.
The knowledge that speaking up had not automatically ended her future.
That afternoon, Avery walked through the operations floor.
She had visited the area many times before.
Usually, she came for scheduled meetings, performance reviews, or discussions about aircraft acquisitions.
This time, she moved without an appointment.
She watched dispatchers reviewing manifests.
She watched a ground coordinator confirm passenger details.
She watched a cabin supervisor checking equipment.
The work was ordinary.
And that was what made it important.
A safe and fair operation depended on thousands of ordinary decisions being made correctly by people who might never meet the company's owner.
Avery stopped beside a dispatch station.
A young employee was reviewing a passenger profile.
He looked at the screen, then at the manifest, then back at the screen.
"Everything all right?" Avery asked.
The employee turned.
"Yes. Just confirming an updated passenger image."
"Is there a discrepancy?"
"No. The image was updated this morning. I'm making sure the current version is synchronized with the crew briefing."
Avery nodded.
"Good."
She moved on.
A few minutes later, she found Elena reviewing the new procedure draft.
"How far have you got?"
"Initial version is complete."
"Show me."
Elena opened the document.
The first section established that passenger verification must be based on objective information.
The examples included:
-
A discrepancy between the passenger's identification and the manifest.
-
An expired or invalid travel credential.
-
A booking authorization that could not be confirmed.
-
An unexpected passenger substitution.
-
A specific security alert or documented operational concern.
The next section described the process for resolving discrepancies.
Crew members were required to contact operations.
Passengers were to be informed of the specific issue whenever disclosure would not compromise a legitimate security measure.
Additional checks had to be proportionate to the concern.
The procedure also made clear that appearance, clothing, perceived wealth, age, race, accent, or the absence of an assistant were not independent grounds for refusing boarding or initiating additional verification.
Avery read the document carefully.
"Good," she said.
Elena pointed to another section.
"We've also included a rule requiring current passenger-profile data to be synchronized before dispatch. If the system cannot confirm that the crew has the latest version, operations must resolve the issue before boarding."
"Can the captain override that?"
"Only through a documented escalation process."
"Who reviews the override?"
"Flight operations."
"And if the concern involves someone in flight operations?"
"Then the matter goes to the independent compliance contact."
Avery nodded.
"That separation is important."
Elena closed the document.
"I also want to discuss training."
"Go ahead."
"We should train captains and cabin crews together. Not just tell them what the policy says. We should give them realistic scenarios and make them practice how to raise concerns."
"Why together?"
"Because the incident on the ramp wasn't only about Richard's judgment. Claire had information he needed. He dismissed it because he believed command authority meant he didn't need to listen."
Avery considered that.
"Then the training should address authority and responsibility."
"Exactly."
Avery looked again at the procedure.
"One more thing."
"What?"
"Don't make the new system so complicated that employees avoid using it."
Elena smiled.
"That was my concern too."
"Good. A reporting system that requires fifteen forms and three approvals is not a reporting system people will trust."
Elena saved the draft.
"We'll simplify it."
The following Monday, Martin Keene requested a second meeting with the investigators.
He arrived with a written statement.
He acknowledged that he had created the informal spreadsheet and that he had failed to seek formal approval for its use.
He also acknowledged that he had received Claire's concern and had not investigated it adequately.
He disputed the suggestion that he had intentionally encouraged discriminatory treatment.
But he accepted that his management decisions had allowed subjective language to become part of the regional culture.
The statement included one sentence that Dana highlighted:
I believed I was protecting operational efficiency by allowing experienced captains discretion, but I did not sufficiently examine how that discretion was being exercised.
Dana asked whether he understood why that was a problem.
"Yes," Martin replied.
"Do you understand why Claire might have felt discouraged from raising further concerns?"
"I do now."
"Did you intend to discourage her?"
"No."
"Do you accept that intent does not erase the effect of your response?"
Martin looked at the statement.
"Yes."
Dana asked about the training decision.
Martin confirmed that he had approved Claire's removal without a documented performance basis.
He said he had not intended to punish her.
But he could not identify a clear reason for the decision.
"Would you make the same decision today?" Dana asked.
"No."
"Why not?"
"Because I would require a documented evaluation."
Dana closed her notebook.
"That is useful. We will include your response in the final assessment."
Martin looked tired.
"Can I ask something?"
"Yes."
"Do you think the company will fire me?"
Dana answered carefully.
"That is not my decision."
Martin nodded.
He had spent years evaluating employees through performance reports.