Fourteen Minutes

Chapter 37

Theme:
Font Size:
24px

“Can they identify the person at the terminal?”

“Not from the service account alone. The workstation logs may help, but we haven't completed that analysis.”

“Any indication that Martin Shaw's credentials were used?”

“Yes. His administrative session was active.”

Olivia looked down at her notes.

“Was he physically present?”

“We don't know yet.”

“Find out.”

Rachel paused.

“There's another issue. The same legacy environment was accessed twice in the previous month. Both times, the activity involved operational scheduling records.”

“Were those records changed?”

“One involved a maintenance window. The other involved a charter allocation. We're examining both.”

“Could either have affected safety?”

“Nothing we've seen indicates that. But we need to check the underlying records.”

Olivia stood and walked toward the window.

“Expand the review to every use of the legacy approval system in the last six months.”

“That could delay the acquisition review.”

“Then the acquisition review will be delayed.”

“Adrian will object.”

“He may object to the weather, too. We still have to determine whether the runway is safe.”

Rachel gave a short, tired laugh.

“Understood.”

The investigation now had two distinct questions.

The first was who had created the false approval.

The second was why the company had preserved a pathway through which an obsolete authorization could be made to appear valid.

The second question was more serious.

A dishonest employee could be disciplined. A defective process could injure people long after the employee had left.

At noon, Olivia met Daniel Mercer at the airport's operations office.

He had been summoned to explain the decision to hold the aircraft, and the written review was scheduled for that afternoon. He looked as though he had slept very little.

“Captain Mercer,” Olivia said, “I wanted to speak with you before the review.”

“Am I in trouble?”

“No. I want to understand what happened from your perspective.”

Daniel sat.

“When the reassignment appeared, the schedule showed that the aircraft had been cleared for another movement. The authorization number was valid in the old system, but the signature didn't match the current approval record. I called operations. They told me the matter had been cleared.”

“Who told you?”

“Mr. Voss's office.”

“Did you speak to Adrian himself?”

“Yes.”

“What did he say?”

“He said the aircraft had been reassigned by executive authority and that the paperwork would catch up.”

Olivia folded her hands.

“Did he tell you to depart?”

“He said I should not allow a clerical discrepancy to jeopardize the company's business.”

“That is not the same thing as an order to depart.”

“No, ma'am.”

“What made you decide to hold?”

Daniel considered the question.

“My first instructor used to say that a schedule is an intention, not a condition of airworthiness. The airplane doesn't know what time the office promised to leave.”

Olivia smiled faintly.

“That's a good instructor.”

“He was an excellent one.”

Daniel continued.

“I checked the aircraft documents, the authorization, and the departure record. I couldn't reconcile them. I asked for written confirmation. Nobody could provide it.”

“And you held.”

“Yes.”

“What did you think would happen to your career?”

Daniel looked at his hands.

“I thought I'd be reassigned. Maybe suspended. I have a mortgage and two children. I wasn't pretending the decision was easy.”

“Would you make the same decision again?”

“Yes.”

He answered without hesitation.

Olivia nodded.

“Then make sure your report explains the facts clearly. Don't exaggerate the pressure, and don't soften it. Record what was said and what you did.”

“Understood.”

When Daniel left, Olivia remained at the table.

The company's procedures had been designed to protect its aircraft, passengers, crews, and employees. But procedures were only useful when people were permitted to follow them.

If a pilot could be punished for refusing to accept questionable authorization, the official policy was merely decorative.

Olivia thought of her father standing beside a hangar door, wiping grease from his hands with a rag that had once been white.

The easiest way to lose control of a machine, he had told her, is to let someone convince you that checking it is an insult.

At 3:20 p.m., Rachel sent a new message.

The forensic team has found a link between the legacy access and the acquisition transaction. We need you in the conference room.

Olivia arrived ten minutes later.

Rachel had placed three documents on the table.

The first was the aircraft authorization.

The second was a configuration report showing that the legacy approval pathway had been re-enabled six weeks earlier.

The third was an email authorizing the configuration change.

It bore Adrian Voss's name.

The message did not explicitly request that Olivia's signature be fabricated. It asked for the legacy profile to be restored “to prevent operational bottlenecks during the transition period.”

Attached to the email was a list of designated transition assets.

Olivia's aircraft was on the list.

So were two maintenance vehicles, a hangar lease, and a communications system used by the operations department.

News in the same category

Fourteen Minutes

45 Part