Fourteen Minutes

Chapter 39

Theme:
Font Size:
24px

Captain Mercer identified the discrepancy between the authorization and the current approval requirements. He requested confirmation, received verbal assurances that the movement had been cleared, and ultimately held the departure because the written record did not support release.

Dr. Price displayed the two timestamps.

“The fourteen-minute interval is significant,” he said. “The authorization was entered before the approval record was created. The system should not have treated that sequence as valid.”

One board member leaned forward.

“Was the system deliberately manipulated?”

“We have evidence that the legacy pathway was restored in advance. We have evidence that the pathway was used to generate the approval record. We have evidence that the authorization was routed through an administrative account connected to the transition team. We do not have a direct record showing who physically initiated the final approval action.”

“So we cannot identify the individual?”

“Not with absolute certainty from the technical evidence alone.”

Adrian folded his hands.

“Then I think we should be careful about implying misconduct. The system had a legacy function. It was restored for transition planning. A scheduling employee entered an authorization. The aircraft was not damaged, no passenger was endangered, and the departure was delayed only briefly.”

Olivia looked at him.

“The delay was not the central failure.”

“I'm aware of that.”

“Are you?”

Eleanor Grant raised a hand.

“Ms. Sterling, let the investigator finish.”

Olivia inclined her head.

Dr. Price continued.

“The central failure is that an obsolete approval pathway could produce a record that appeared valid even though the required approval had not occurred. The system also permitted the authorization to be entered before the approval existed.”

“Was that a software defect?” another board member asked.

“Partly. The system behaved according to a legacy configuration that should have been disabled. But the configuration was deliberately restored, and the control that should have prevented its use was not enforced.”

Rachel distributed the configuration report.

The board examined the document in silence.

Adrian leaned back.

“I authorized restoration of the legacy profile. I did so to prevent delays during the transition. I did not instruct anyone to falsify Olivia's signature.”

“No one has claimed that the email alone proves you did,” Rachel said. “The question is whether the control change was appropriate, whether it was properly approved, and whether it contributed to the invalid authorization.”

Adrian turned toward her.

“Rachel, you know how complicated this transition has been. The company has been operating under multiple systems for months.”

“I do. That's why the control was supposed to remain disabled.”

“Because you didn't want to risk a disruption.”

“Because it was retired for a reason.”

Eleanor looked at Dr. Price.

“Can you explain the difference between restoring the profile and approving the flight?”

“Certainly. Restoring the profile created the possibility of using an obsolete authorization route. It did not, by itself, authorize a particular flight. The flight still required a valid approval. The system's failure was that it accepted a reference to the retired profile and generated an approval record without verifying the required current authorization.”

“So restoring the profile created the vulnerability, but someone still had to use it.”

“Correct.”

Adrian seized on the distinction.

“Which means the system configuration and the scheduling action were separate matters. I approved the configuration for operational reasons. I did not create the flight authorization.”

Dr. Price nodded.

“That distinction is accurate. It does not resolve the remaining questions about who used the pathway or why.”

The board moved to the evidence concerning Martin Shaw.

Rachel explained that Martin's administrative session had been active during the relevant period. The session had also been used to modify an attachment associated with the transaction documents.

Martin had told investigators that he had restored the legacy profile under Adrian's direction. He believed the restoration was intended to allow authorized transition planning, not to bypass a current approval. He had denied generating the false approval record.

The forensic review had not found a direct command entered under Martin's named account that created the final record. However, it had established that the service account was invoked from a workstation associated with his administrative environment.

“Martin's account may have been used by another person,” Rachel explained. “It may also have been used during a session Martin controlled. We cannot establish which without further evidence.”

Thomas looked at the table.

“He should have challenged the request to restore the profile.”

“Yes,” Rachel said. “That is a separate question from whether he created the false record.”

Olivia spoke for the first time in several minutes.

“Those distinctions matter. We should not punish one person for a conclusion the evidence does not support. But we also cannot excuse a control failure because we cannot name every person involved.”

Adrian turned toward her.

“You seem determined to turn an administrative error into a referendum on the acquisition.”

News in the same category

Fourteen Minutes

45 Part